Component

core/observability/fluentd

A Fluentd log aggregator. Fluentd is the receiving end of a log pipeline: it listens on the `forward` input protocol and accepts log records shipped to it by upstream forwarders (a Fluent Bit or Fluentd forwarder), then processes and routes them to its output. Because it is a sink rather than a forwarder, Fluentd declares no downstream uses-socket; instead it exports the host and port of its forward endpoint through `provides`, so any forwarder that binds this component on its forward socket ships records to it. The aggregator buffers records in memory by default and renders as a stateful server; an optional data volume can back the buffer when durable buffering is requested. Realized for local development by a Compose Recipe, and on Kubernetes by two realizations the Manifest chooses between, which run the same image, configuration, port and buffer. `fluentd` synthesizes the aggregator as native Kubernetes resources and fetches nothing, so it is the one to reach for where the build must complete with no chart repository reachable. `fluentd-chart` renders the Fluent project's own Helm chart configured as that aggregator, so reach for it where a chart repository is reachable at build time. The Fluentd server is Apache-2.0.

Provenance

OfficialSigned by a signing identity this catalog recognizes as an official publisher.
Content digest
sha256:a9bedf68584d8e28254cdf52d773fe97cf168d2e11fdd0719f8f124d2e07a5d1
Published
2026-11-10T10:12:57Z
Signing identity
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Signature

  • Officialapplication/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:2d0cae0a495ba99403c86316c9eeb021e8a12f5d61ed5b73551cdf02a5974a3b

Reference at this version

oci://hub.aggrega.ai/component/core/observability/fluentd:1.0.0

Developer parameters

Values the developer sets in the Aggregate.

NameTypeDefaultRequiredDescription
output_matchstring**noTag-match pattern selecting which received log records are routed to the aggregator's output. Defaults to `**`, which routes every received record. This is the receiving-side counterpart to a forwarder's forward match.

Operator sizing

Infrastructure sizing the operator tunes per environment.

NameTypeDefaultRequiredDescription
portinteger (min 1024, max 65535)24224noTCP port the Fluentd forward input listens on for incoming log records. Most operators should omit this and let the Recipe assign the default (24224, the conventional Fluentd forward port).
engine_versionstringv1.19.3-debian-2.1noFluentd container image tag. Selects the image tag on container targets.
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—
storageobject—no—
overridesobject (open)—noProvider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads.

Output contract

Values this component publishes to consumers over the uses topology.

NameTypeDefaultRequiredDescription
hoststring—yesIn-cluster DNS name of the Service the aggregator receives log records on. A forwarder shipping records upstream points its output at this name together with `port`.
portinteger—yesTCP port the aggregator accepts incoming log records on. It follows the port an operator set in the Release, so a forwarder reads it rather than assuming a default.
protocolstring—noWire protocol the published address speaks — `forward`, the shipping protocol a forwarder's output plugin must be configured for.

Uses sockets

The dependency sockets this component connects through. The target of every connection wired through a socket must satisfy its label selector, and each connection may carry an attachment in the slots the socket declares. A required slot is owed by each connection the Aggregate or the Release wires through the socket.

No uses sockets declared.

Attachment slots

Named binding points at which a Feature attaches to this component. A slot's selector constrains which Feature may fill it and its inject list names how the Feature's material may be delivered. A required slot must be bound on every instance, by an attachment on the instance or at a scope above it, and a sensitive slot is declared to handle secret material. A Feature may also attach under a name no slot declares.

No attachment slots declared.

Self-inject allowlist

No self-inject pipes declared.

Relationships

Typed edges to and from other published entities. A reference with no published target renders as a broken edge rather than a link.

Uses

This entity uses nothing in the catalog.

Used by

Component concept reference →

The Aggrega catalog — an open index of components, features, recipes, and the plugins that render them.

Built with the shared Aggrega design system.

Privacy