LifeRaft OSTM

Operations add-on

RLX Telemetry

Self-hosted operational observability for site performance, jobs, storage, add-ons, incidents, monitors, heartbeats, and privacy-conscious aggregate metrics.

OperationsCategory
1.0.0Version
ProductionRelease stage
$64.85 · AdvancedLicense
Back to catalog
Operations add-on

About this add-on

RLX Telemetry for LifeRaft OS

RLX Telemetry is the LifeRaft OS operations control tower. It is intentionally separate from RLX Analytics, which explains audience behaviour, and RLX Telemetry Infrastructure, which normalizes signed Studio bridge events.

Self-hosted operational observability for site performance, jobs, storage, add-ons, incidents, monitors, heartbeats, and privacy-conscious aggregate metrics. Use it when staff need a controlled operating surface for reporting, approvals, planning, security, automation, and decision support instead of another spreadsheet habit. The practical win: aggregate counters, gauges, timings, and heartbeats.

At a glance
  • Admin-managed content and settings
  • Public pages with clean presentation
  • Designed to run as an optional RLX module
  • Aggregate counters, gauges, timings, and heartbeats
rlx-telemetry Version 1.0.0 $64.85 · Advanced Production

Capabilities and outcomes

How RLX Telemetry improves the build

The overview above identifies the core capability. These supporting outcomes help a project owner judge whether the add-on belongs in the package.

Aggregate counters, gauges, timings, and heartbeats

Hourly metric buckets with bounded dimensions

Turns admin work into a controlled process instead of a spreadsheet habit

Gives professional teams cleaner visibility, repeatability, and post-launch operating confidence

Background job, add-on failure, storage, database, PHP memory, and bridge-event snapshots

Operations builds that need RLX Telemetry without forcing it into every install

Standalone value

What it does by itself

RLX Telemetry can run as its own Operations workflow. By itself, it focuses on Admin-managed content and settings, Public pages with clean presentation, and Designed to run as an optional RLX module, so a customer can use the module without buying every related add-on first.

Standalone means it does not have to be cross-linked with other add-ons. It still runs inside LifeRaft OS and requires a valid core LifeRaft OS license.

Connected value

What improves when related add-ons are active

When the customer also owns and activates related modules such as RLX Analytics, RLX Telemetry Infrastructure, RLX Stats, RLX Automation, and RLX Forms, RLX Telemetry can hand off data, links, reporting, access control, content, or follow-up steps into those workflows. Those connections are optional and depend on the package being built.

Best fit

Who should care about it

  • Aggregate counters, gauges, timings, and heartbeats
  • Hourly metric buckets with bounded dimensions
  • Background job, add-on failure, storage, database, PHP memory, and bridge-event snapshots
  • Operations builds that need RLX Telemetry without forcing it into every install

Workflow

How it fits into a real build

  1. Activate RLX Telemetry and review its add-on settings
  2. Aggregate counters, gauges, timings, and heartbeats
  3. Hourly metric buckets with bounded dimensions
  4. Background job, add-on failure, storage, database, PHP memory, and bridge-event snapshots

Works well with

The strongest builds connect the right modules

RLX Telemetry becomes more valuable when it is paired with the workflows around it. Common pairings include RLX Analytics, RLX Telemetry Infrastructure, RLX Stats, RLX Automation, RLX Forms, depending on the customer package and what the site needs to accomplish.

Admin setup

Confirm settings, navigation placement, permissions, and any required starter content before launch.

Public QA

Review the public page, empty states, mobile layout, and activated/deactivated states.

Data QA

Check exports, filtering, retention, audit visibility, and staff-only permissions.

Docs and support

Add customer-facing notes, admin setup instructions, and known limitations for the module.

Customer FAQ

Common questions about RLX Telemetry

What does RLX Telemetry do?

Self-hosted operational observability for site performance, jobs, storage, add-ons, incidents, monitors, heartbeats, and privacy-conscious aggregate metrics.

Who is RLX Telemetry best for?

Aggregate counters, gauges, timings, and heartbeats. Hourly metric buckets with bounded dimensions. Background job, add-on failure, storage, database, PHP memory, and bridge-event snapshots.

Can RLX Telemetry run by itself?

RLX Telemetry can run as its own Operations workflow. By itself, it focuses on Admin-managed content and settings, Public pages with clean presentation, and Designed to run as an optional RLX module, so a customer can use the module without buying every related add-on first.

Do I need the other add-ons mentioned on this page?

No. Related add-ons are optional package pairings, not required purchases unless a project specifically needs that wider workflow. RLX Telemetry should still explain a useful standalone job before any connected modules are considered. Standalone means it does not have to be cross-linked with other add-ons. It still runs inside LifeRaft OS and requires a valid core LifeRaft OS license.

What changes when related add-ons are active?

When the customer also owns and activates related modules such as RLX Analytics, RLX Telemetry Infrastructure, RLX Stats, RLX Automation, and RLX Forms, RLX Telemetry can hand off data, links, reporting, access control, content, or follow-up steps into those workflows. Those connections are optional and depend on the package being built.

Which add-ons work well with RLX Telemetry?

RLX Telemetry commonly pairs with RLX Analytics, RLX Telemetry Infrastructure, RLX Stats, RLX Automation, RLX Forms. Active pairings depend on the package, customer workflow, and installed add-ons.

What should be decided before launching RLX Telemetry?

RLX Telemetry should be launched with its real data model and public routes in mind. Optional integrations: rlx-analytics, rlx-telemetry-infrastructure.

How much does RLX Telemetry cost?

RLX Telemetry has a $64.85 Advanced add-on license. The add-on requires a valid Personal, Professional, Creator, or separately agreed LifeRaft OS core license.

What support is included for RLX Telemetry?

Enhanced add-on support indicates a broader or more operationally involved module. Exact response scope and duration are confirmed with the licensed package and core edition. Personal includes 3 months, Professional includes 6 months, and Creator includes 12 months of core support and updates.

How ready is RLX Telemetry for deployment?

Production module: packaged for normal licensed deployment, subject to the hosting, configuration, and integration checks described in the documentation.

How does RLX Telemetry fit into a real LifeRaft OS build?

Activate RLX Telemetry and review its add-on settings. Aggregate counters, gauges, timings, and heartbeats. Hourly metric buckets with bounded dimensions. Background job, add-on failure, storage, database, PHP memory, and bridge-event snapshots.

Does the public page include implementation details?

No. The public page explains customer value, package fit, related modules, and launch expectations. Setup steps, route details, data structures, hooks, and operator-only notes stay in the licensed add-on documentation.

Coming soon

Want RLX Telemetry in your LifeRaft OS build?

RLX Telemetry is part of the modular LifeRaft OS add-on roadmap. Join the waitlist or discuss a package so the right modules can be planned around the way your community, product, studio, or business actually operates.