Diese Seite wurde maschinell übersetzt. Englisches Original lesen.

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.

Herkunft

OffiziellSigniert von einer Signaturidentität, die dieser Katalog als offiziellen Herausgeber anerkennt.
Inhalts-Digest
sha256:c3497d1fd29113a0d2acdecb73b2bf1b49779fec20fcb2543fea38509145103d
Veröffentlicht
2026-11-10T10:12:54Z
Signaturidentität
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Signatur

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

Referenz zu dieser Version

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

Entwicklerparameter

Werte, die der Entwickler im Aggregate festlegt.

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

Dimensionierung durch den Operator

Infrastrukturdimensionierung, die der Operator pro Umgebung anpasst.

NameTypStandardwertErforderlichBeschreibung
portinteger (min 1024, max 65535)2020neinHTTP port the Fluent Bit monitoring endpoint listens on. Most operators should omit this and let the Recipe assign the default (2020).
publish_on_all_interfacesbooleanfalseneinPublishes 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.8neinFluent Bit container image tag. Selects the image tag on container targets; the chart-backed realization pins its own image tag.
source_versionstring—neinVersion 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—nein—
overridesobject (open)—neinProvider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads.

Ausgabevertrag

Werte, die diese Komponente über die uses-Topologie an Konsumenten veröffentlicht.

NameTypStandardwertErforderlichBeschreibung
hoststring—jaIn-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—jaTCP 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—neinHow the published address is spoken to — `http`, so a consumer reaches the monitoring endpoint with an HTTP client.
metrics_endpointstring—neinThe 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—neinName 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—neinName 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—neinPath 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.

uses-Sockets

Die Abhängigkeits-Sockets, über die sich diese Komponente verbindet. Das Ziel jeder über einen Socket verdrahteten Verbindung muss dessen Label-Selektor erfüllen, und jede Verbindung kann in den Slots, die der Socket deklariert, eine Anbindung tragen. Einen erforderlichen Slot muss jede Verbindung füllen, die das Aggregate oder das Release über den Socket verdrahtet.

forward_target

Selektor
component.aggrega.ai/type in (server, stateful-server)
Injektion
env

Dieser Socket deklariert keine Anbindungs-Slots, daher trägt eine Verbindung über ihn keine Anbindung.

Anbindungs-Slots

Benannte Bindungspunkte, an denen ein Feature an diese Komponente angebunden wird. Der Selektor eines Slots schränkt ein, welches Feature ihn füllen darf, und seine inject-Liste benennt, wie das Feature sein Material liefern darf. Ein erforderlicher Slot muss auf jeder Instanz gebunden sein, durch eine Anbindung an der Instanz oder in einem darüberliegenden Geltungsbereich, und ein sensibler Slot ist für den Umgang mit geheimem Material deklariert. Ein Feature kann auch unter einem Namen angebunden werden, den kein Slot deklariert.

Keine Anbindungs-Slots deklariert.

Zulassungsliste für Selbstinjektion

env

Beziehungen

Typisierte Kanten zu und von anderen veröffentlichten Entitäten. Eine Referenz ohne veröffentlichtes Ziel wird als unterbrochene Kante statt als Link dargestellt.

Verwendet

Verwendet von

Konzeptreferenz zu Component →

Der Aggrega-Katalog — ein offener Index von Komponenten, Funktionen, Rezepten und den Plugins, die sie rendern.

Erstellt mit dem gemeinsamen Aggrega-Designsystem.

Datenschutz