Usage statistics (telemetry)
YARMA servers can send anonymous usage statistics to the License Center once a day. They help decide what to build and support (operating systems, versions, features in use) without learning anything about customers.
What is sent
POST /lc/v1/telemetry (JSON, schema 1):
| Field | Content |
|---|---|
installation_id |
random UUID created once per server; not linked to a license, customer or tenant |
version, deployment, cloud |
server version; native, compose, kubernetes or unknown; whether it is one of the operator's cloud servers |
os, arch, cpus, memory_gb |
the server host |
organizations, devices, devices_online, users, active_users_30d |
counts |
devices_by_os, agent_versions |
devices per operating system and per agent version (top 10) |
sessions_30d |
support sessions in the last 30 days by mode (attended, agentless, unattended) |
features |
counts showing feature use: identity providers by kind, automation jobs (30 days), software packages, patch rings, alert rules, report schedules, unattended policies, MSP clients |
license_plans |
number of organizations per license plan |
Never sent: names, slugs, host names, email or IP addresses, license or customer IDs, device identifiers, or anything inside organizations. The License Center does not store the sending IP address; it keeps the latest report per installation.
Who sends
telemetry.mode |
Behavior |
|---|---|
ask (default) |
off until an administrator of a top-level organization turns it on under Settings → Usage statistics, which also shows today's exact report |
on |
always; the native installer sets it for the operator's cloud servers (--server-token) |
off |
never; the console cannot turn it on |
Reports go to telemetry.url, by default license.center_url; air-gapped servers send
nothing. The choice is audited (telemetry.update).
Viewing
Operator console → Insights → Usage statistics: installations seen in the last 30 days (self-hosted and cloud, new), total organizations, devices and active users, and breakdowns by server version, deployment type, size, operating system, agent version, session mode, feature adoption and license plan.
Documentation for Yarma 0.1.0-alpha.4. Something unclear? .