Stacks/Python/Services/OpenTelemetry Collector

OpenTelemetry Collector in the Python stack

This page explains what OpenTelemetry Collector means in the Python stack: how it is included, which base service it uses, and how it connects to the rest of the stack.

OpenTelemetry Collector is available in the Python stack but starts disabled, so teams can turn it on only when a specific app needs it.

All Python stack servicesBack to the Python stackView base service

Role

Disabled by default

Base service

OpenTelemetry Collector

Type

service

Delivery

Prebuilt service image

Stack fit

How OpenTelemetry Collector fits into this stack

OpenTelemetry Collector is available in the Python stack but starts disabled, so teams can turn it on only when a specific app needs it.

This stack service is based on OpenTelemetry Collector and keeps the service-specific setup for Python in one place.

Version policy

Available versions include 0.

Inclusion

Enabled by default: No

Required: No

Primary: No

Connections

No explicit service links are defined for this stack service.

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

Settings

Tune service behavior per environment while keeping one reusable stack baseline.

Upstream OTLP endpoint
Upstream Authorization header