Telemetry Collector Operations

This runbook tells operators how to deploy and verify the Stella Ops telemetry collector on the supported, non-Kubernetes release model. For the wider observability picture see the telemetry observability runbook and the telemetry architecture.

Audience: platform operators and on-call engineers responsible for collector rollout, health, and offline/air-gap deployments.

Supported Scope

Telemetry collector deployment follows the Stella Ops non-Kubernetes release model: Docker Compose, Offline Kit, signed release manifests, and host/service-manager operations.

Kubernetes and Helm collector deployment instructions are retired.

Deployment Checklist

  1. Verify the signed release manifest and collector image digest.
  2. Provision TLS material through the approved host secret store.
  3. Configure collector endpoints, tenant labels, and offline exporters through Compose environment files or mounted config files.
  4. Start the collector through the supported Compose profile or host service manager.
  5. Run health checks and verify local telemetry export.
  6. Record release manifest digest, config hash, certificate fingerprint, and health output.

Unsupported Legacy Paths

Do not create Kubernetes namespaces, Kubernetes Secrets, ConfigMaps, Helm values, pods, or kubectl exec checks for Stella Ops telemetry collector deployment.