LifeRaft OSTM
← All add-ons

Operations

RLX Telemetry

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

ProductionVersion 1.0.0
Product images coming soonA closer look at RLX Telemetry.

What it does

Features at a glance

  • 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
  • Threshold and stale-heartbeat monitors
  • Automatic incident opening and recovery
  • Manual incident acknowledgement and resolution

Built for your workflow

Who it’s for

  • Teams replacing scattered records with a shared operational workflow
  • Administrators responsible for day-to-day coordination

Setup and fit

Compatibility

Requires a valid LifeRaft OS core license and a supported installation.

No additional add-on is listed as a required dependency.

Optional connections

From setup to everyday use

A straightforward starting point

  1. Activate RLX Telemetry and review its add-on settings
  2. Aggregate counters, gauges, timings, and heartbeats
  3. Hourly metric buckets with bounded dimensions

Before you choose

Common questions

What does RLX Telemetry do?

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

What does RLX Telemetry need to run?

RLX Telemetry runs on the LifeRaft OS core without another add-on listed as a required dependency. Optional integrations can be added for a broader workflow.

How ready is RLX Telemetry for deployment?

Production is this add-on’s declared release stage. The V5 platform is a development build; review the workflows, hosting, and integrations you plan to use.

Review the launch checklist
  • 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.

Make RLX Telemetry part of your build.

Discuss the fit, requirements, and next steps for your project.

Let’s talk