telemetron setup may call POST /v1/enroll when no token source is already configured. The enroll request sends exactly:
schemainstall_idmachine_idosarchsourcetelemetron_versionpack(the configured mode, e.g.openclaw)tier(deployment tier, e.g.internal,external, ortest)
Normal OTLP metric flushes send:
- the existing OTLP metric payload produced by
telemetron install_idas an OTLP resource attributedeployment_idas an OTLP resource attribute (operator-configured identity of the deployment)tieras an OTLP resource attribute (internal,external, ortest)environmentas an OTLP resource attribute (operator-configured environment name)pack_versionas an OTLP resource attribute (version of the pack being observed)telemetron_versionas an OTLP resource attribute (version of the telemetron binary)
deployment_id, tier, environment, pack_version, and telemetron_version come from the operator's config or binary metadata, not from the host. They never contain hostnames, usernames, or paths.
telemetron does not send:
- hostname
- username
- home-directory paths
- MAC addresses
- kernel version
- session content, prompts, responses, or tool payloads
/etc/telemetron/token is written 0400 because it is a bearer secret.
/etc/telemetron/install-id is written 0644 intentionally. The install id is an anonymous UUID, not a bearer credential. Keeping it world-readable lets support scripts, diagnostics, and operators inspect or report the installation identity without requiring sudo.
Set TELEMETRON_NO_AUTO_ENROLL=1 before running telemetron setup to skip anonymous enrollment entirely. In that mode, setup exits cleanly without starting the service unless some other token source is already present.