Open
Description
Description
We need to enhance the fluentbit.conf
configuration by integrating default [INPUT]
and [OUTPUT]
plugins to facilitate seamless monitoring and data forwarding for entity synthesis of Fluent Bit in host. These plugins will aid in scraping and forwarding metrics using Prometheus.
Acceptance Criteria
- Define and configure a default
[INPUT]
plugin influentbit.conf
for Prometheus scraping:- Name:
prometheus_scrape
- Alias:
fb-metrics-collector
- Host:
127.0.0.1
- Port:
2020
- Tag:
fb_metrics
- Metrics Path:
/api/v2/metrics/prometheus
- Scrape Interval:
10s
- Name:
- Define and configure a default
[OUTPUT]
plugin for Prometheus remote write:- Name:
prometheus_remote_write
- Match:
fb_metrics
- Alias:
fb-metrics-forwarder
- Host:
${METRICS_HOST}
- Port:
443
- Uri:
/prometheus/v1/write?prometheus_server=${HOSTNAME}
- Header:
Authorization Bearer ${LICENSE_KEY}
- Tls:
On
- Tls.verify:
Off
- Add user-defined labels:
app fluent-bit
,pod_name ${HOSTNAME}
,node_name ${NODE_NAME}
,source host
- Name:
Describe Alternatives
No specific alternatives were extensively considered, as the integration of Prometheus scraping and forwarding mechanisms is deemed optimal for this scenario.
For Maintainers Only or Hero Triaging this bug
- Suggested Priority: P3
This feature request will improve monitoring capabilities by default, enhancing user experience and reducing the time needed for manual configuration in Fluent Bit setups.