updated logging fluentd config to have metrics enabled (!9497) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

This MR updates Logging Operator configuration to enable the built-in Prometheus ServiceMonitor for the central Fluentd aggregation layer.

Changes Made

Updated values.yaml to set logging.fluentd.metrics.serviceMonitor: true in logging unit.
Exposed the metrics path /metrics explicitly for scraping by promtheus

After applying the changes

root@management-node-1:~  # kubectl port-forward statefulset/logging-fluentd 24231:24231 -n kube-logging
root@management-node-1:~  # curl --noproxy "*" http://localhost:24231/metrics
# TYPE fluentd_router_records_total counter
# HELP fluentd_router_records_total Total number of events routed for the flow
fluentd_router_records_total{flow="@ee12fc5b7c2966940a7fef618f02d4e4",id="clusterflow:kube-logging:all-logs"} 36727.0
fluentd_router_records_total{flow="@d2c9b680f87ff1469e2b691829106cbc",id="clusterflow:kube-logging:kubelet-logs"} 723.0
fluentd_router_records_total{flow="@eb9e47834cf5706ebcc97a4dcc515b7b",id="clusterflow:kube-logging:systemd-logs"} 7.0
# TYPE fluentd_output_status_buffer_total_bytes gauge
# HELP fluentd_output_status_buffer_total_bytes Current total size of stage and queue buffers.
fluentd_output_status_buffer_total_bytes{plugin_id="clusterflow:kube-logging:all-logs:clusteroutput:kube-logging:loki",type="loki"} 18592.0
.......

Test coverage

CI configuration

Below you can choose test deployment variants to run in this MR's CI.

Click to open to CI configuration

Legend:

Icon	Meaning	Available values
☁️	Infra Provider	`capd`, `capo`, `capm3`
🚀	Bootstrap Provider	`kubeadm` (alias `kadm`), `rke2`, `okd`, `ck8s`
🐧	Node OS	`ubuntu`, `suse`, `na`, `leapmicro`
🛠️	Deployment Options	Deployment option list and description
🎬	Pipeline Scenarios	Available scenario list and description
🟢	Enabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by `mgmt:` or `wkld:` to be applied only to a specific cluster type
🔴	Disabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by `mgmt:` or `wkld:` to be applied only to a specific cluster type
🏗️	Target platform	Can be used to select specific deployment environment Available platform list and description
⚡	Pipeline control	`autorun`, `manual` or `blocking`. Can be used to override global config and start a deployment pipeline the required way

Global config for deployment pipelines

autorun pipelines
allow failure on pipelines
record sylvactl events

Notes:

Enabling autorun will make deployment pipelines to be run automatically without human interaction
Disabling allow failure will make deployment pipelines mandatory for pipeline success.
if both autorun and allow failure are disabled, deployment pipelines will need manual triggering but will be blocking the pipeline

Be aware: after configuration change, pipeline is not triggered automatically. Please run it manually (by clicking the run pipeline button in Pipelines tab) or push new code.

Edited Oct 10, 2026 by Nitin Sharma

updated logging fluentd config to have metrics enabled

What does this MR do and why?

Changes Made

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports