-
Notifications
You must be signed in to change notification settings - Fork 474
[Azure Metrics] Move container_registry metrics from beats to integrations #3629
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
[Azure Metrics] Move container_registry metrics from beats to integrations #3629
Conversation
🌐 Coverage report
|
We're probably good to go; it just needs some testing. |
Switch from "container_registry" to "monitor" metricset, add the metrics configuration from beats, and add an ingest pipeline to set the expected field names (`container_registry.*` instead of `azure.metrics.*`).
6a0ecf6
to
5f659dc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Could you also update the sample_event.json file please?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for updating the sample_event.json!! LGTM!
@tommyers-elastic, thank you, I missed that one 🤦 |
What does this PR do?
This PR is to move lightweight module configuration from Metricbeat into integrations.
Switch from "container_registry" to "monitor" metricset, add the metrics configuration from beats, and add an ingest pipeline to set the expected field names (
azure. container_registry.*
instead ofazure.metrics.*
).Checklist
changelog.yml
file.Related issues
Screenshots