-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Add a Prometheus Remote-Write input plugin #7526
Comments
Ah I like this I assume HTTP/2 input is needed @leonardo-albertovich as FYI |
Based on the spec I think HTTP/1.1 is valid. |
Yes, HTTP/1.1 should be good enough, there are no blockers as far as I know. |
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the |
/not-stale |
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the |
/not-stale |
I assume that #8725 is related or potentially delivers this functionality? |
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the |
It looks like the Prometheus Remote Write functionality has been delivered so I'll close this issue. |
Is your feature request related to a problem? Please describe.
When running Fluent Bit as an OTEL aggregator (multiple replicas) and wanting to aggregate metrics from Prometheus there isn't currently a way to do this without duplicating the metrics across all of the replicas. This is because Prometheus can't currently push metrics in OTEL format.
Describe the solution you'd like
I'd like Fluent Bit to support the Prometheus Remote-Write specification so prometheus can push metrics to a Fluent Bit Aggregator service without duplicating the metrics.
Describe alternatives you've considered
Not aggregating metrics and pushing straight from Prometheus, but this isn't as reliable or consistent.
Additional context
The text was updated successfully, but these errors were encountered: