8000 Sending metrics from node_exporter or scrapers over forward protocol · Issue #5520 · fluent/fluent-bit · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Sending metrics from node_exporter or scrapers over forward protocol #5520

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
noahbailey opened this issue May 31, 2022 · 3 comments
Closed
Assignees

Comments

@noahbailey
Copy link

Currently, metrics gathered from node_exporter or prometheus scrapers must be output via remote write within the same fluentbit instance, becuase they are part of a 'different pipeline' from regular log-formatted data. This could be a limitation for some users who prefer to relay ALL data through one set of fluentbit nodes before splitting data off into different sinks.

+--------------------+                +--------------------+
| Node A (fluentbit) |  ==forward==>  | Node B (fluentbit) |  ==remote_write output==>   Prometheus
| node_exporter      |                +--------------------+  \==s3 output==> S3 bucket
| journald, etc      |                                         \==> elastic/opensearch, etc
+--------------------+

This would help with a common use case which uses relays per zone to forward data to one centralized system which sends data to their storage back-ends.

@edsiper edsiper self-assigned this Jun 5, 2022
@edsiper
Copy link
Member
edsiper commented Jun 5, 2022

thanks for raising this ticket. This feature will be implemented shortly.

@phwissmann
Copy link
phwissmann commented Jan 5, 2023

Just wanted to express my support for this use case. Is it on any roadmap?

edit: seems to be implemented and working in 2.0.6

@agup006
Copy link
Member
agup006 commented May 16, 2025

This should be done already.

@agup006 agup006 closed this as completed May 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants
0