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

Component

core/observability/fluent-bit

A Fluent Bit log processor and forwarder, collecting log records from its inputs and shipping them to a downstream sink wired through its `forward_target` uses-socket: the selected component's host and port arrive on the injection context and are rendered into a `forward` output, so Fluent Bit forwards to whichever sink the topology binds. That output speaks the Fluentd forward protocol, so a sink wired there that publishes a protocol other than forward, or none, halts the build; Fluentd publishes forward. Fluent Bit holds no persistent state, so it renders as a stateless server. Exports its HTTP monitoring endpoint's host and port to consumers, and where Prometheus finds the metrics served there. Realized for local development by a Compose Recipe, and on Kubernetes by two realizations the Manifest chooses between, which differ in where the records come from. `fluent-bit` synthesizes a single forwarding pod with its own declared input and fetches nothing, so it is the one to reach for where the build must complete with no chart repository reachable. `fluent-bit-chart` renders the official Fluent Helm chart in its node-collector shape — one pod per node reading that node's container logs, with the cluster read grants the record-enrichment filter needs — so reach for it where records are to be collected from the cluster itself. Both publish the same monitoring endpoint and forward to the wired sink; for its metrics the chart-backed one publishes the Service a scraper discovers every node's collector behind. With the Prometheus Operator, `core/prometheus-exporter` attached to the synthesized realization, port `http` and path `/api/v2/metrics/prometheus`, emits a ServiceMonitor for it.

Procedencia

OficialFirmado por una identidad de firma que este catálogo reconoce como editor oficial.
Digest del contenido
sha256:c3497d1fd29113a0d2acdecb73b2bf1b49779fec20fcb2543fea38509145103d
Publicado
2026-11-10T10:12:54Z
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:9a54da70794efe0378c80dd0d40c148c8df96ba944fa0cff8661130a9c37f318

Referencia en esta versión

oci://hub.aggrega.ai/component/core/observability/fluent-bit:1.0.0

Parámetros del desarrollador

Valores que el desarrollador establece en el Aggregate.

NombreTipoPredeterminadoObligatorioDescripción
forward_matchstring*noTag-match pattern selecting which log records are shipped on the forward output wired to the `forward_target` socket. Defaults to `*`, which forwards every record.

Dimensionamiento del operador

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

NombreTipoPredeterminadoObligatorioDescripción
portinteger (min 1024, max 65535)2020noHTTP port the Fluent Bit monitoring endpoint listens on. Most operators should omit this and let the Recipe assign the default (2020).
publish_on_all_interfacesbooleanfalsenoPublishes the monitoring port on every host interface rather than on the host's loopback address only. Read only by the compose realization; false publishes the port on 127.0.0.1 only, and true on every host interface, where any machine that reaches the host reaches it — the monitoring endpoint authenticates no caller and answers metrics, health, uptime and build and plugin listings. The Kubernetes realizations ignore it.
engine_versionstring4.0.8noFluent Bit container image tag. Selects the image tag on container targets; the chart-backed realization pins its own image tag.
source_versionstring—noVersion of the Helm chart the chart-backed realization pulls. Read only by that realization; the workload-synthesis and Compose realizations pull no source artifact and ignore it. Changing it away from the Recipe's default does not guarantee value-mapping compatibility with the new chart.
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íIn-cluster DNS name of the Service fronting the processor's monitoring endpoint. A consumer that scrapes or probes the processor dials this name together with `port`.
portinteger—síTCP port that monitoring endpoint answers on. It follows the port an operator set in the Release, so a consumer reads it rather than assuming a default.
protocolstring—noHow the published address is spoken to — `http`, so a consumer reaches the monitoring endpoint with an HTTP client.
metrics_endpointstring—noThe full address Prometheus scrapes this component's metrics at — scheme, host, port and path, `http://<host>:<port>/api/v2/metrics/prometheus` on the monitoring endpoint. Empty on the chart-backed realization, which publishes `metrics_service` instead.
metrics_servicestring—noName of the Service every node's collector sits behind, for a scraper that discovers each endpoint of that Service rather than scraping one address. Set by the chart-backed realization, beside `metrics_service_port` and `metrics_path`; empty on the others.
metrics_service_portstring—noName of the port of `metrics_service` that carries the metrics, `http`, the monitoring endpoint's port. Set and empty together with `metrics_service`.
metrics_pathstring—noPath the metrics are served at, `/api/v2/metrics/prometheus`, published beside `metrics_service`. Empty where the component publishes `metrics_endpoint`, which carries its own path.

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.

forward_target

Selector
component.aggrega.ai/type in (server, stateful-server)
Inyección
env

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

env

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