OpenTelemetry Collector Contrib as the center of Sysaro’s observability pipeline
Sysaro manages a verifiable Contrib profile rather than an abstract “otelcol”: OTLP ingress, metric export and loopback Loki/Tempo routing with topology validation before apply.
How the service fits into Sysaro
Why Contrib is explicit
The managed profile uses components that cannot be assumed to exist in the core-only distribution.
The Agent therefore distinguishes a detected core-only otelcol from a Contrib installation instead of applying configuration blindly.
Distribution mismatch becomes an explicit UI state rather than a failed restart after writing YAML.
Connected typed pipeline
OTLP gRPC/HTTP receivers accept application telemetry.
The metrics exporter routes to Prometheus while logs go to Loki and traces to Tempo through loopback targets.
Target ports are part of typed desired state and the Stack view reports topology mismatches before adjacent configs are applied.
Safe apply
Native Collector validation runs before restart.
Configuration path, systemd unit and probe endpoint are fixed by the adapter rather than chosen by the browser.
Apply uses managed-file ownership and rollback; post-restart readiness verifies a health endpoint instead of relying on process state alone.
What this page does not claim
Detection, lifecycle or a typed subset is not described as complete management of every upstream capability. The canonical current scope is also published in service-evidence.json and the 18-service catalog.