Logging Module uses a collection of open source tools to provide a resilient and robust logging stack for the cluster.
The central piece of the stack is the open source search engine OpenSearch, combined with its analytics and visualization platform OpenSearch Dashboards. Logs are collected by a node-level data collection and enrichment agent, Fluent Bit, and pushed to OpenSearch through Fluentd. The Fluent Bit and Fluentd stack is managed by the Logging Operator. Loki is also available as an alternative log storage backend to OpenSearch.
All the components are deployed in the logging namespace in the cluster.
Logging Module is part of SIGHUP Distribution (SD) and is deployed automatically by furyctl when you create or update a cluster. You don't need to download, vendor or install its packages manually.
You configure the module under spec.distribution.modules.logging in your furyctl.yaml. The type field selects the logging stack to deploy: opensearch, loki, customOutputs, or none to disable the module. When using OpenSearch, opensearch.type selects a single or triple node deployment. The other fields are optional and fall back to sensible defaults.
To use Loki as the log storage backend instead, set type: loki and choose the Loki storage backend with loki.backend (minio for an in-cluster MinIO deployment, or externalEndpoint for an external S3-compatible object storage):