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.
Procedência
- Digest do conteúdo
- sha256:c3497d1fd29113a0d2acdecb73b2bf1b49779fec20fcb2543fea38509145103d
- Publicado
- 2026-11-10T10:12:54Z
- Identidade de assinatura
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
Assinatura
- 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
Referência nesta versão
oci://hub.aggrega.ai/component/core/observability/fluent-bit:1.0.0Parâmetros do desenvolvedor
Valores que o desenvolvedor define no Aggregate.
| Nome | Tipo | Padrão | Obrigatório | Descrição |
|---|---|---|---|---|
| forward_match | string | * | não | 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. |
Dimensionamento do operador
Dimensionamento de infraestrutura que o operador ajusta por ambiente.
| Nome | Tipo | Padrão | Obrigatório | Descrição |
|---|---|---|---|---|
| port | integer (min 1024, max 65535) | 2020 | não | 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_interfaces | boolean | false | não | 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_version | string | 4.0.8 | não | Fluent Bit container image tag. Selects the image tag on container targets; the chart-backed realization pins its own image tag. |
| source_version | string | — | não | 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. |
| compute | object | — | não | — |
| overrides | object (open) | — | não | Provider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads. |
Contrato de saída
Valores que este componente publica para os consumidores pela topologia uses.
| Nome | Tipo | Padrão | Obrigatório | Descrição |
|---|---|---|---|---|
| host | string | — | sim | 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`. |
| port | integer | — | sim | 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. |
| protocol | string | — | não | How the published address is spoken to — `http`, so a consumer reaches the monitoring endpoint with an HTTP client. |
| metrics_endpoint | string | — | não | 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_service | string | — | não | 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_port | string | — | não | 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_path | string | — | não | 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. |
Sockets uses
Os sockets de dependência pelos quais este componente se conecta. O destino de cada conexão ligada por um socket deve satisfazer o seletor de rótulos dele, e cada conexão pode carregar um acoplamento nos slots que o socket declara. Cada conexão que o Aggregate ou a Release liga pelo socket deve preencher os slots obrigatórios.
forward_target
- Seletor
- component.aggrega.ai/type in (server, stateful-server)
- Injeção
- env
Este socket não declara slots de acoplamento, então uma conexão por ele não carrega nenhum acoplamento.
Slots de acoplamento
Pontos de vinculação nomeados nos quais uma Feature se acopla a este componente. O seletor de um slot restringe qual Feature pode preenchê-lo, e sua lista inject indica como o material da Feature pode ser entregue. Um slot obrigatório deve estar vinculado em cada instância, por um acoplamento na instância ou em um escopo acima dela, e um slot sensível é declarado para lidar com material secreto. Uma Feature também pode se acoplar com um nome que nenhum slot declara.
Nenhum slot de acoplamento declarado.
Lista de permissões de autoinjeção
env
Relações
Arestas tipadas de e para outras entidades publicadas. Uma referência sem destino publicado é exibida como uma aresta quebrada em vez de um link.
Usa
- usausa o socket «forward_target»
component.aggrega.ai/type in (server, stateful-server)
Não declara slots de acoplamento.
core/ai-agent/agenta-api v1.0.0 →core/ai-agent/agenta-runner v1.0.0 →core/ai-agent/agenta-services v1.0.0 →core/ai-agent/agenta-web v1.0.0 →core/ai-agent/agenta-web-mobile v1.0.0 →core/ai-agent/dify v1.0.0 →core/ai-agent/dify v1.1.0 →core/ai-agent/dify-plugin-daemon v1.0.0 →core/ai-agent/dify-sandbox v1.0.0 →core/ai-agent/dify-ssrf-proxy v1.0.0 →core/ai-agent/dify-web v1.0.0 →core/ai-agent/dify-web v1.1.0 →core/ai-agent/flowise v1.0.0 →core/ai-agent/flowise v1.1.0 →core/ai-agent/google-adk v1.0.0 →core/ai-agent/google-adk v1.1.0 →core/ai-agent/langflow v1.0.0 →core/ai-agent/langflow v1.1.0 →core/ai-agent/librechat v1.0.0 →core/ai-agent/librechat v1.1.0 →core/ai-agent/librechat v1.2.0 →core/ai-agent/mastra v1.0.0 →core/ai-agent/n8n v1.0.0 →core/ai-agent/n8n v1.1.0 →core/ai-agent/open-webui v1.0.0 →core/ai-model/docker-model-runner v1.0.0 →core/ai-model/litellm v1.0.0 →core/ai-model/nemoguard-content-safety v1.0.0 →core/ai-model/nvidia-nim v1.0.0 →core/ai-model/nvidia-nim-operator v1.0.0 →core/ai-model/ollama v1.0.0 →core/ai-model/tei v1.0.0 →core/ai-model/tgi v1.0.0 →core/ai-model/vllm v1.0.0 →core/ai-pipeline/argo-workflows v1.0.0 →core/ai-pipeline/temporal v1.0.0 →core/ai-tool/browser v1.0.0 →core/ai-tool/computer-use v1.0.0 →core/ai-tool/filesystem v1.0.0 →core/ai-tool/mcp v1.0.0 →core/ai-tool/mcp v1.1.0 →core/compute/keda v1.0.0 →core/compute/knative-serving v1.0.0 →core/compute/server v1.0.0 →core/compute/server v1.1.0 →core/datastore/chroma v1.0.0 →core/datastore/cognee v1.0.0 →core/datastore/documentdb v1.0.0 →core/datastore/elasticsearch v1.0.0 →core/datastore/etcd v1.0.0 →core/datastore/ferretdb v1.0.0 →core/datastore/mariadb v1.0.0 →core/datastore/mariadb-operator v1.0.0 →core/datastore/memcached v1.0.0 →core/datastore/milvus v1.0.0 →core/datastore/mysql v1.0.0 →core/datastore/mysql-innodb-cluster v1.0.0 →core/datastore/mysql-operator v1.0.0 →core/datastore/opensearch v1.0.0 →core/datastore/pgvector v1.0.0 →core/datastore/postgres v1.0.0 →core/datastore/qdrant v1.0.0 →core/datastore/redis v1.0.0 →core/datastore/timescaledb v1.0.0 →core/datastore/valkey v1.0.0 →core/datastore/weaviate v1.0.0 →core/devtool/adminer v1.0.0 →core/devtool/harbor v1.0.0 →core/gateway/agentgateway v1.0.0 →core/gateway/apisix v1.0.0 →core/gateway/contour v1.0.0 →core/gateway/envoy-ai-gateway-operator v1.0.0 →core/gateway/envoy-gateway v1.0.0 →core/gateway/higress v1.0.0 →core/gateway/kong v1.0.0 →core/gateway/kong-enterprise v1.0.0 →core/gateway/litellm v1.0.0 →core/gateway/nginx v1.0.0 →core/gateway/traefik-hub v1.0.0 →core/gateway/tyk v1.0.0 →core/messaging/kafka v1.0.0 →core/messaging/livekit-server v1.0.0 →core/messaging/livekit-sip v1.0.0 →core/messaging/nats v1.0.0 →core/messaging/rabbitmq v1.0.0 →core/observability/fluentd v1.0.0 →core/observability/grafana v1.0.0 →core/observability/jaeger v1.0.0 →core/observability/langfuse v1.0.0 →core/observability/loki v1.0.0 →core/observability/otel-collector v1.0.0 →core/observability/prometheus v1.0.0 →core/observability/tempo v1.0.0 →core/observability/thanos-query v1.0.0 →core/observability/thanos-store v1.0.0 →core/security/cert-manager v1.0.0 →core/security/external-secrets v1.0.0 →core/security/fms-guardrails-orchestrator v1.0.0 →core/security/keycloak v1.0.0 →core/security/kong-ai-pii-service v1.0.0 →core/security/nemo-guardrails v1.0.0 →core/security/nemoguard-jailbreak-detect v1.0.0 →core/security/openbao v1.0.0 →core/security/presidio-analyzer v1.0.0 →core/security/presidio-anonymizer v1.0.0 →core/security/sealed-secrets v1.0.0 →core/security/supertokens v1.0.0 →core/security/trustyai-guardrails-gateway v1.0.0 →core/security/trustyai-huggingface-detector v1.0.0 →core/storage/barman-cloud-plugin v1.0.0 →core/storage/k8up v1.0.0 →core/storage/kasten v1.0.0 →core/storage/kubestash v1.0.0 →core/storage/velero v1.0.0 →example/compute/db-reader v1.0.0 →example/compute/gcp-credentialed-service v1.0.0 →example/compute/greeter v1.0.0 →example/compute/service v1.0.0 →example/gateway/nginx-reviewed v1.0.0 →
Usado por
usa o socket «upstream»
usa o socket «scrape_target»
usa o socket «store»
aplica-se a
aplica-se a
aplica-se a
aplica-se a
aplica-se a
aplica-se a
aplica-se a
implementa
implementa
implementa