本页面为机器翻译。阅读英文原文。

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.

来源

官方由本目录认定为官方发布者的签名身份签名。
内容摘要
sha256:c3497d1fd29113a0d2acdecb73b2bf1b49779fec20fcb2543fea38509145103d
发布时间
2026-11-10T10:12:54Z
签名身份
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

签名

  • 官方application/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

此版本的引用

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

开发者参数

开发者在 Aggregate 中设置的值。

名称类型默认值必需描述
forward_matchstring*否Tag-match pattern selecting which log records are shipped on the forward output wired to the `forward_target` socket. Defaults to `*`, which forwards every record.

运维规格

运维人员按环境调整的基础设施规格。

名称类型默认值必需描述
portinteger (min 1024, max 65535)2020否HTTP port the Fluent Bit monitoring endpoint listens on. Most operators should omit this and let the Recipe assign the default (2020).
publish_on_all_interfacesbooleanfalse否Publishes 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.8否Fluent Bit container image tag. Selects the image tag on container targets; the chart-backed realization pins its own image tag.
source_versionstring—否Version 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—否—
overridesobject (open)—否Provider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads.

输出契约

此组件通过 uses 拓扑向使用方发布的值。

名称类型默认值必需描述
hoststring—是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—是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—否How the published address is spoken to — `http`, so a consumer reaches the monitoring endpoint with an HTTP client.
metrics_endpointstring—否The 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—否Name 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—否Name 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—否Path 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 套接字

此组件用于建立连接的依赖套接字。通过某个套接字接入的每个连接,其目标都必须满足该套接字的标签选择器,且每个连接都可以在该套接字声明的槽位中携带附加项。必需槽位须由 Aggregate 或 Release 通过该套接字接入的每个连接来填充。

forward_target

选择器
component.aggrega.ai/type in (server, stateful-server)
注入
env

此套接字未声明附加槽位,因此经由它的连接不携带任何附加项。

附加槽位

Feature 附加到此组件时所用的命名绑定点。槽位的选择器限定哪个 Feature 可以填充该槽位,其 inject 列表则指明 Feature 的内容可以如何交付。必需槽位必须在每个实例上完成绑定,可以通过实例上的附加,也可以通过其上层作用域的附加;敏感槽位则声明为用于处理机密内容。Feature 也可以以任何槽位都未声明的名称进行附加。

未声明附加槽位。

自注入允许列表

env

关系

与其他已发布实体之间的类型化边。没有已发布目标的引用会呈现为断开的边,而不是链接。

使用

被使用

Component 概念参考 →

Aggrega 目录 — 收录组件、功能、配方以及渲染它们的插件的开放索引。

基于共享的 Aggrega 设计系统构建。

隐私