Questa pagina è stata tradotta automaticamente. Leggi l’originale in inglese.

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.

Provenienza

UfficialeFirmato da un’identità di firma che questo catalogo riconosce come editore ufficiale.
Digest del contenuto
sha256:c3497d1fd29113a0d2acdecb73b2bf1b49779fec20fcb2543fea38509145103d
Pubblicato
2026-11-10T10:12:54Z
Identità di firma
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Firma

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

Riferimento a questa versione

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

Parametri dello sviluppatore

Valori che lo sviluppatore imposta nell’Aggregate.

NomeTipoPredefinitoObbligatorioDescrizione
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.

Dimensionamento dell’operatore

Dimensionamento dell’infrastruttura che l’operatore regola per ogni ambiente.

NomeTipoPredefinitoObbligatorioDescrizione
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.

Contratto di output

Valori che questo componente pubblica verso i consumatori attraverso la topologia uses.

NomeTipoPredefinitoObbligatorioDescrizione
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.

Socket uses

I socket di dipendenza attraverso cui questo componente si connette. La destinazione di ogni connessione collegata attraverso un socket deve soddisfare il suo selettore di etichette, e ogni connessione può portare un aggancio negli slot che il socket dichiara. Uno slot obbligatorio deve essere riempito da ogni connessione che l’Aggregate o la Release collega attraverso il socket.

forward_target

Selettore
component.aggrega.ai/type in (server, stateful-server)
Iniezione
env

Questo socket non dichiara slot di aggancio, quindi una connessione attraverso di esso non porta alcun aggancio.

Slot di aggancio

Punti di associazione con nome in cui una Feature si aggancia a questo componente. Il selettore di uno slot limita quale Feature può riempirlo e la sua lista inject indica come può essere consegnato il materiale della Feature. Uno slot obbligatorio deve essere associato su ogni istanza, da un aggancio sull’istanza o a un ambito superiore, e uno slot sensibile è dichiarato per gestire materiale segreto. Una Feature può anche agganciarsi con un nome che nessuno slot dichiara.

Nessuno slot di aggancio dichiarato.

Elenco consentito di auto-iniezione

env

Relazioni

Archi tipizzati da e verso altre entità pubblicate. Un riferimento senza una destinazione pubblicata viene mostrato come arco interrotto anziché come link.

Usa

Usato da

Riferimento al concetto Component →

Il catalogo Aggrega — un indice aperto di componenti, funzionalità, ricette e dei plugin che li renderizzano.

Realizzato con il design system condiviso di Aggrega.

Privacy