A push model delivers data when it becomes available: the source sends it to a central service, or an open server-initiated connection carries data back as events occur. This avoids polling calls that return no new data and can reduce delay before critical metrics are noticed. section 5.6.4
Operational choices shape how the pattern is used:
- Use streaming or push delivery when metric freshness matters more than the efficiency of periodic polling. section 5.6.4
- Use Prometheus remote write to send metrics to Prometheus-compatible time-series systems, including Thanos, Grafana Cloud, New Relic, and Logz.io. section 5.6.4
- Configure separate outputs when the same data must reach local and cloud-hosted services. section 5.6.4
Fluent Bit remote output
A Fluent Bit configuration collects internal metrics every five seconds and sends them through prometheus_remote_write. A cloud destination uses HTTPS, credentials, and an API path; a local Prometheus destination uses its write endpoint and port 9090. section 5.6.4
Listing 5.8 Prometheus writer: prometheus-remote-output.conf
[SERVICE]
flush 5
log_level trace
[INPUT]
name fluentbit_metrics
tag internal_metrics
scrape_interval 5
[OUTPUT]
name prometheus_remote_write #1
match *
host prometheus-prod-05-gb-south-0.grafana.net #2
uri /api/prom/push #3
port 443
tls on
log_response_payload on
add_label fluentbit cloud
http_user ${my-userid} #4
http_passwd ${my-password}
[OUTPUT]
name prometheus_remote_write
match *
host 192.168.0.205 #5
uri /api/v1/write #6
port 9090 #7
tls off
log_response_payload on #8
add_label fluentbit local #9
Inspect the complete configuration, including flush timing, TLS settings, authentication, endpoints, and labels. section 5.6.4
