Component

core/observability/otel-collector

The OpenTelemetry Collector, in its contrib distribution: a stateless server that receives traces, metrics and logs over the OpenTelemetry protocol (OTLP), on a gRPC port and an HTTP port, and runs each signal through a pipeline of its own. A producer points its OTLP exporter at the endpoint the collector publishes for the transport it speaks. Every signal always has a pipeline fed by the OTLP receiver. A backend wired to the signal's socket — `traces`, `metrics` or `logs`, each taking the components labelled `observability.aggrega.ai/<signal>` — adds one exporter to that pipeline, for the protocol the label names. A Prometheus is reached only with its `values.otlp_receiver` true; the build halts otherwise, naming that line. A signal with nothing wired ends in the collector's debug exporter at basic verbosity: what arrives is summarised in the collector's own log, one line per batch, and sent nowhere else. A producer is not refused for want of a backend, and what it sends is not dropped unseen. Realized on helm by `otel-collector-chart`, which renders the project's own Helm chart and needs its chart repository reachable at build time, and on compose by `otel-collector`, a compose service publishing nothing to the host. Both run the same image with the same configuration, written once in the OtelCollectorConfig bundle they import. With `values.metrics_enabled` true the collector serves its own telemetry metrics, at /metrics on port 8888, on every interface rather than its loopback address, and publishes that address as `metrics_endpoint`; false, that key is empty. The port checks no caller. On helm it joins a ClusterIP Service, and another Service type halts the build.

Provenance

OfficialSigned by a signing identity this catalog recognizes as an official publisher.
Content digest
sha256:b748c8c386227390ac4d0e453d5c7a2503bfaf947d2fd1fc788e6e93259be636
Published
2026-11-10T10:13:13Z
Signing identity
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Signature

  • Officialapplication/vnd.dev.sigstore.bundle.v0.3+json

    https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

    sha256:a580825d7d6000571b76adf005f363c2f9594dbe023d420552f3c24684f7f3d6

Reference at this version

oci://hub.aggrega.ai/component/core/observability/otel-collector:1.0.0

Developer parameters

Values the developer sets in the Aggregate.

NameTypeDefaultRequiredDescription
metrics_enabledbooleanfalsenoMakes the collector's own telemetry metrics, served at /metrics on port 8888, reachable on every interface rather than its loopback address alone, and publishes their address as `metrics_endpoint`; while false that key is empty. These describe the collector itself, not the metrics it forwards. The port checks no caller, so anything that reaches it can read them.

Operator sizing

Infrastructure sizing the operator tunes per environment.

NameTypeDefaultRequiredDescription
engine_versionstring0.162.0noTag of the otel/opentelemetry-collector-contrib image both Recipes run. The configuration is written for 0.162.0; another release may name a component differently.
source_versionstring—noVersion of the opentelemetry-collector Helm chart the chart-backed realization pulls. Read only by that realization; the compose realization pulls no source artifact and ignores it. Changing it away from the Recipe's default does not guarantee value-mapping compatibility with the new chart.
otlp_grpc_portinteger (min 1024, max 65535)4317noPort the OTLP receiver accepts gRPC on — the port published as `port` and in `endpoint`.
otlp_http_portinteger (min 1024, max 65535)4318noPort the OTLP receiver accepts HTTP on — the port published as `otlp_http_port` and in `otlp_http_endpoint`.
computeobject—no—
overridesobject (open)—noProvider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads.

Output contract

Values this component publishes to consumers over the uses topology.

NameTypeDefaultRequiredDescription
hoststring—yesName the collector is reached at — the in-cluster Service on helm, the service name on compose. A producer points its exporter at this name together with `port`.
portinteger—yesTCP port the OTLP receiver accepts gRPC on.
protocolstring—noHow the published address is spoken to — `grpc`, so an exporter is configured for the gRPC transport.
endpointstring—noThe OTLP gRPC endpoint as an exporter takes it — `http://<host>:<port>`, the scheme saying the connection is not encrypted.
otlp_http_portinteger—noTCP port the OTLP receiver accepts HTTP on.
otlp_http_endpointstring—noThe OTLP HTTP endpoint as an exporter takes it — `http://<host>:<otlp_http_port>`. An exporter given this base address appends the path for each signal itself, such as `/v1/traces`.
metrics_endpointstring—noThe full address Prometheus scrapes the collector's own telemetry metrics at — scheme, host, port and path, `http://<host>:8888/metrics`, the host being the one published as `host`. Empty while values.metrics_enabled is false.

Uses sockets

The dependency sockets this component connects through. The target of every connection wired through a socket must satisfy its label selector, and each connection may carry an attachment in the slots the socket declares. A required slot is owed by each connection the Aggregate or the Release wires through the socket.

traces

Selector
observability.aggrega.ai/traces
Inject
—

This socket declares no attachment slots, so a connection through it carries no attachment.

metrics

Selector
observability.aggrega.ai/metrics
Inject
—

This socket declares no attachment slots, so a connection through it carries no attachment.

logs

Selector
observability.aggrega.ai/logs
Inject
—

This socket declares no attachment slots, so a connection through it carries no attachment.

Attachment slots

Named binding points at which a Feature attaches to this component. A slot's selector constrains which Feature may fill it and its inject list names how the Feature's material may be delivered. A required slot must be bound on every instance, by an attachment on the instance or at a scope above it, and a sensitive slot is declared to handle secret material. A Feature may also attach under a name no slot declares.

No attachment slots declared.

Self-inject allowlist

No self-inject pipes declared.

Relationships

Typed edges to and from other published entities. A reference with no published target renders as a broken edge rather than a link.

Uses

Used by

Component concept reference →

The Aggrega catalog — an open index of components, features, recipes, and the plugins that render them.

Built with the shared Aggrega design system.

Privacy