Skip to main content

OpenTelemetry Collector (otel-collector)

Receives OTLP traces, metrics and logs, tags them with the cluster resource attributes and exports them to OpenSearch or the Elasticsearch of the client (logs), Jaeger (traces), Prometheus and optionally Opik (LLM traces).

Generated from catalog/services/otel-collector.yaml: do not edit by hand.

Summary​

Version0.130.0
Useinstall and configure, configure and connect
Layerfunctional (AI catalog)
CategoryObservability
Installation methodsbinary, podman
External connectionno
Sandbox onlyno

Licence​

SPDX identifierApache-2.0
Licence policycore licence (MIT or Apache-2.0)
Licence exception-
Platform componentotel-collector

Packages and artifacts​

A package the project of the service publishes (its image, its binary archive, its Python or OS package) carries the licence of the service; a third-party package carries the licence written on its row, read from the official upstream metadata.

KindPackageVersionLicenceDetails
container imagedocker.io/otel/opentelemetry-collector-contrib0.130.0Apache-2.0image key otelcol-contrib, used by otel-collector, digest sha256:867d1074c2f750936fb9358ec9eefa009308053cf156b2c7ca1761ba5ef78452
binary archiveotelcol-contrib_0.130.0_linux_amd64.tar.gz0.130.0Apache-2.0https://github.com/open-telemetry/opentelemetry-collector-releases/releases/download/v0.130.0/otelcol-contrib_0.130.0_linux_amd64.tar.gz, x86_64, checksum sha256

Images are pinned by tag in the descriptor, and by digest when the descriptor declares one (the offline bundle then refuses a pulled image that does not carry it); the digest is recorded in the mirror of the Manager when the offline bundle is imported, and every pull or load is checked against it.

Supported systems and architectures​

MethodOperating systemsArchitectures
binaryRHEL family (dnf), Debian family (apt), Arch Linux (pacman)x86_64 (architecture of the artifacts of the descriptor)
podmanRHEL family (dnf), Debian family (apt), Arch Linux (pacman)x86_64, aarch64 (not restricted by the descriptor)

Certified host systems: RHEL 8/9/10, Rocky Linux 8/9/10, AlmaLinux 8/9/10, Oracle Linux 8/9, CentOS Stream 9/10, Ubuntu 22.04/24.04, Debian 12, Arch Linux (rolling). The host preflight accepts these systems (other releases of a known family give a warning, end of life releases are refused) and the x86_64 and aarch64 architectures.

Prerequisites​

Host​

The descriptor declares no host preflight check.

Programs the commands and checks of the service start on the host, outside the managed roots: add them to allowed_commands of the agent (see Security of the Navin agent), else the agent refuses them with command_not_allowed: /usr/bin/curl.

Network and ports​

ComponentPort namePortOpened in the host firewall
otel-collectorotlp_grpc4317/tcpyes
otel-collectorotlp_http4318/tcpyes
otel-collectormetrics8888/tcpyes
otel-collectorhealth13133/tcpno
otel-collectorzpages55679/tcpno

Services and connections needed​

  • opensearch: opensearch (optional).
  • elasticsearch: elasticsearch (optional).
  • jaeger: jaeger (optional).
  • prometheus: prometheus (optional).
  • llm_tracing: opik (optional).

Details and resolution: see Dependencies.

Installation methods and modes​

MethodDefaultWhat the method uses
binaryyesthe binary archives of the descriptor, unpacked under the service directory
podman-the container images of the descriptor, run by Podman under systemd

Components​

ComponentKindInstallation methodsPorts
Collector (otel-collector)masterbinary, podman4317/tcp, 4318/tcp, 8888/tcp, 13133/tcp, 55679/tcp

Agent (agent) (default)​

One collector on each host sending to the backends.

What the mode deploys:

ComponentPlacement
otel-collectormin 1, recommended 3

Gateway (gateway)​

Replicated stateless collectors behind the load balancer.

What the mode deploys:

ComponentPlacement
otel-collectormin 2, recommended 2

Install this service​

The install wizard of the Navin Manager plans, validates and runs the installation; you need the services:install permission on the cluster.

  1. Open the wizard. In Clusters, choose the row action Install services of the target cluster. The wizard opens on its first step, Service.

  2. Choose the service. On the Service step, select OpenTelemetry Collector. The card shows the licence Apache-2.0 and the dependencies the installation needs. Pick the Method among binary, podman (default binary).

  3. Choose the hosts and the mode. On the Hosts step, tick the hosts, then choose the Mode: agent (default), gateway. Each mode deploys the components listed in Installation methods and modes.

  4. Bind the dependencies. On the Bindings step, choose for each dependency (opensearch, elasticsearch, jaeger, prometheus, llm_tracing) Install with the platform or Use an existing connection; an optional dependency can stay on No binding.

  5. Configure. On the Configure step, review the parameters (see Configuration parameters). Passwords left empty with a generated default are generated and sealed by the Manager.

  6. Review and install. On the Install step the Manager validates the plan and shows the installation order; when it says "The plan is valid. Ready to install.", choose Install. A highly available mode is installed only when its HA checks pass.

  7. Verify. The operation ends when the health checks of every instance pass (see Health checks); the service then shows as running in Services.

Connect an existing service​

Schemeshttps, http
Default port4317
Authenticationoptional
Health checkhealth_url + /
Authentication methodFieldsDescription
none-OTLP receiver without an authenticator.
bearertokenbearertokenauth extension of the OTLP receiver: the collector checks the token only when data arrives, the Manager cannot test it beforehand.
basicusername, passwordbasicauth extension (htpasswd) of the OTLP receiver, checked by the collector when data arrives only.

Official documentation: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/extension/bearertokenauthextension

FieldTypeDefaultDescriptionNotes
Health endpoint URL (health_url)url-Health endpoint URL of the existing service.required

High availability​

Clusterreplicas (replication)
High availabilityexternal (external)
Failoverload balancer (load-balancer)
Replicationnone (none)
Quorumnone (none)
Discoverynone (none)
Entry pointload balancer (load-balancer)
Official documentationhttps://opentelemetry.io/docs/collector/deploy/gateway/

Topology per mode​

ModesHighest catalog levelDistributionQuorum componentFault domainsDescription
agentha (ha)per host (per-host)--One agent on every host: each host covers itself, the loss of a host only loses its own coverage.
gatewayha (ha)active-active (active-active)-2Replicated stateless collectors behind the load balancer.

Notes​

  • A collector keeps the data in progress in memory: a crash loses what was not yet exported. The backends (OpenSearch, Jaeger, Prometheus) need their own high availability.

Configuration parameters​

General​

ParameterTypeDefaultAllowed valuesRequiredSecretRestartDescription
OTLP gRPC port (grpc_port)port4317-nononoPort of the OTLP gRPC receiver.
OTLP HTTP port (http_port)port4318-nononoPort of the OTLP HTTP receiver.
Self metrics port (metrics_port)port8888-nononoPort of the collector own metrics.
zPages port (zpages_port)port55679-nononoPort of the zPages debug pages, bound to localhost.
Health port (health_port)port13133-nononoPort of the health check extension.
TLS (tls_enabled)boolfalse-nonoyesServe the OTLP gRPC and HTTP receivers and the own metrics over TLS with a certificate issued by the manager CA.
Internal metrics port (self_metrics_port)port4319-nononoLoopback port receiving the collector own metrics when TLS is on, before they are served in TLS on the self metrics port (the built-in Prometheus reader has no TLS). (advanced)
Memory limit (memory_limit_mib)int1024min 128, max 65536, MiBnononoLimit of the memory_limiter processor.
Environment (environment)stringproduction-nononoValue of deployment.environment added by the resource processor.

Dependencies​

For each active dependency the Manager takes the first of: the binding chosen in the wizard; a service of the same installation that provides it; a service already installed in the cluster; the only connection of the expected type. Otherwise an optional dependency stays unbound, and a required one is added to the installation in its default mode (the column below names the catalog service added).

BindingProvided byConnection typeEndpointOptionalWhen nothing is boundDescription
opensearchopensearch-httpyesstays unbound (optional)OpenSearch receiving the logs (index eai-logs-*).
elasticsearch- (versions >= 8.12, < 9)elasticsearch-yesstays unbound (optional)Elasticsearch the client already runs, declared as a connection and never installed by Navin: it receives the logs in the data stream logs-eai.otel-default (OpenTelemetry mapping, Elasticsearch 8.12 or a later 8.x), next to OpenSearch when both are bound.
jaegerjaeger-otlp_grpcyesstays unbound (optional)Jaeger receiving the traces (OTLP gRPC).
prometheusprometheus-httpyesstays unbound (optional)Prometheus receiving the metrics (remote write).
llm_tracingopik-apiyesstays unbound (optional)Opik backend receiving the LLM traces (OTLP over HTTP, /v1/private/otel).

Endpoints​

EndpointSchemeComponentPortPathTLS parameterBinding parametersBinding secretsProvisioning command
otlp_grpcgrpcotel-collector4317 (grpc_port)-tls_enabledtls--
otlp_httphttpotel-collector4318 (http_port)-tls_enabled---

Commands​

CommandComponentTargetDescription
Pipeline status (zPages) (zpages)otel-collectorevery hostReads the pipelines page of the zPages extension.

Health checks​

Liveness (per instance)​

ComponentCheckDetails
otel-collectorHTTP http://127.0.0.1:{{ config.health_port }}/Expected 200; 30 retries; interval 1 s; timeout 3 s

Preflight checks​

CheckTypeMeaningSeverityComponents
grpc_freeport_free {"param": "grpc_port"}port 4317 free on the hostblockingevery component
http_freeport_free {"param": "http_port"}port 4318 free on the hostblockingevery component

Uninstall​

Paths removed when the data is purged: {{ paths.log }}.

  • zPages (from the host only): http://127.0.0.1:{{ config.zpages_port }}/debug/servicez

Upstream documentation​