-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Metricbeat] Enhancement to add support for handling Openmetrics data #26308
Conversation
❕ Build Aborted
Expand to view the summary
Build stats
Trends 🧪Steps errors
Expand to view the steps failures
|
Pinging @elastic/integrations (Team:Integrations) |
Hey @premendrasingh, thanks for opening this PR! I see it adds a new metricset for openmetrics, but Metricbeat already has an I also see that this PR includes changes for other things as azure or oracle, are these changes intended? If they are, I would suggest to open different PRs for them, as they seem to be unrelated. |
@jsoriano |
This pull request is now in conflicts. Could you fix it? 🙏
|
Cancel PR |
Enhancement - Enhanced Prometheus module and added openmetrics metricset to use Openmetrics parser.
What does this PR do?
This PR adds a new metricset in Prometheus module. It handles metrics endpoints returning data with
Content-Type: application/openmetrics-text
Message processing is similar to existing prometheus/collector.
Why is it important?
Many of our customers have data exposed in OpenMetrics format, but existing Prometheus module can process metrics only in expfmt, Openmetrics data is being ignored. Hence the need for Openmetrics support also.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.How to test this PR locally
Unit tests in prometheus/openmetricscollector can be used to test the metrics locally.
Setup a http server to serve Openmetrics data with HTTP header
Content-Type: application/openmetrics-text
Change metricset in metricbeat.yml to use openmetricscollector as shown below