Esta página se tradujo automáticamente. Leer el original en inglés.

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.

Procedencia

OficialFirmado por una identidad de firma que este catálogo reconoce como editor oficial.
Digest del contenido
sha256:b748c8c386227390ac4d0e453d5c7a2503bfaf947d2fd1fc788e6e93259be636
Publicado
2026-11-10T10:13:13Z
Identidad de firma
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Firma

  • Oficialapplication/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

Referencia en esta versión

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

Parámetros del desarrollador

Valores que el desarrollador establece en el Aggregate.

NombreTipoPredeterminadoObligatorioDescripción
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.

Dimensionamiento del operador

Dimensionamiento de la infraestructura que el operador ajusta para cada entorno.

NombreTipoPredeterminadoObligatorioDescripción
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.

Contrato de salida

Valores que este componente publica para los consumidores a través de la topología uses.

NombreTipoPredeterminadoObligatorioDescripción
hoststring—síName 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—síTCP 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.

Sockets uses

Los sockets de dependencia a través de los cuales se conecta este componente. El destino de cada conexión cableada a través de un socket debe satisfacer su selector de etiquetas, y cada conexión puede llevar un acoplamiento en los slots que declara el socket. Cada conexión que el Aggregate o la Release cablea a través del socket debe llenar los slots obligatorios.

traces

Selector
observability.aggrega.ai/traces
Inyección
—

Este socket no declara slots de acoplamiento, por lo que una conexión a través de él no lleva ningún acoplamiento.

metrics

Selector
observability.aggrega.ai/metrics
Inyección
—

Este socket no declara slots de acoplamiento, por lo que una conexión a través de él no lleva ningún acoplamiento.

logs

Selector
observability.aggrega.ai/logs
Inyección
—

Este socket no declara slots de acoplamiento, por lo que una conexión a través de él no lleva ningún acoplamiento.

Slots de acoplamiento

Puntos de enlace con nombre en los que una Feature se acopla a este componente. El selector de un slot restringe qué Feature puede llenarlo y su lista inject indica cómo puede entregarse el material de la Feature. Un slot obligatorio debe estar enlazado en cada instancia, mediante un acoplamiento en la instancia o en un ámbito superior, y un slot sensible se declara para manejar material secreto. Una Feature también puede acoplarse con un nombre que ningún slot declara.

No se declararon slots de acoplamiento.

Lista de permitidos de autoinyección

No se declararon canales de autoinyección.

Relaciones

Aristas tipadas hacia y desde otras entidades publicadas. Una referencia sin un destino publicado se muestra como una arista rota en lugar de como un enlace.

Usa

Usado por

Referencia del concepto Component →

El catálogo de Aggrega — un índice abierto de componentes, funcionalidades, recetas y los plugins que los renderizan.

Creado con el sistema de diseño compartido de Aggrega.

Privacidad