Role
Required
OpenTelemetry Collector in the Observability stack
This page explains what OpenTelemetry Collector means in the Observability stack: how it is included, which base service it uses, and how it connects to the rest of the stack.
OpenTelemetry Collector is included by default and treated as a required part of the Observability stack.
Base service
OpenTelemetry Collector
Type
service
Delivery
Prebuilt service image
Stack fit
How OpenTelemetry Collector fits into this stack
OpenTelemetry Collector is included by default and treated as a required part of the Observability stack.
This stack service is based on OpenTelemetry Collector and keeps the service-specific setup for Observability in one place.
It is linked to Grafana Tempo, Grafana Loki, and VictoriaMetrics inside the stack.
Version policy
Available versions include 0.
Inclusion
Enabled by default: Yes
Required: Yes
Primary: No
Connections
Storage
This stack service does not define persistent volume sizes.
Stack-specific technical details
Review the operational capabilities exposed by OpenTelemetry Collector inside this stack, including backups, imports, configs, settings, cron, actions, storage, and service links where they exist.
Configs
Keep service config files versioned with the stack instead of rebuilding them per environment.
Collector config
Service links
See how services are wired together so dependencies stay consistent across environments.
Upstream
Currently not linked in the default stack layout. Optional.
Traces
Linked to Grafana Tempo. Optional.
Metrics
Linked to VictoriaMetrics. Optional.
Logs
Linked to Grafana Loki. Optional.