Role
Enabled by default
OpenTelemetry Collector in the VictoriaMetrics stack
This page explains what OpenTelemetry Collector means in the VictoriaMetrics stack: how it is included, which base service it uses, and how it connects to the rest of the stack.
OpenTelemetry Collector is enabled by default in app environments created from the VictoriaMetrics stack, but it is not treated as a core required service.
Base service
OpenTelemetry Collector
Type
service
Delivery
Prebuilt service image
Stack fit
How OpenTelemetry Collector fits into this stack
OpenTelemetry Collector is enabled by default in app environments created from the VictoriaMetrics stack, but it is not treated as a core required service.
This stack service is based on OpenTelemetry Collector and keeps the service-specific setup for VictoriaMetrics in one place.
It is linked to VictoriaMetrics inside the stack.
Version policy
Available versions include 0.
Inclusion
Enabled by default: Yes
Required: No
Primary: No
Connections
victoria-metrics: VictoriaMetrics
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.
Grafana Tempo
Currently not linked in the default stack layout. Optional.
Grafana Loki
Currently not linked in the default stack layout. Optional.
VictoriaMetrics
Linked to VictoriaMetrics. Optional.