-
Notifications
You must be signed in to change notification settings - Fork 1k
Move to new Humio structered API. #1544
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
Conversation
CI checks currently failing due to apparently unrelated Atlas issue. Please advice |
@mwl if you rebase this branch on |
ee9e890
to
71853b0
Compare
Tested against upcoming Humio 1.6.0 but should also be compatible with everything from 1.2 onwards |
Documentation might need updating too. What's the process for that? |
Documentation is at https://github.com/micrometer-metrics/micrometer-docs/ |
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 the pull request. I am not very familiar with Humio, so I just want to understand how the change might affect users. For example, I want to ensure that after this change, any existing dashboards and queries will continue to work.
implementations/micrometer-registry-humio/src/main/java/io/micrometer/humio/HumioConfig.java
Show resolved
Hide resolved
...ntations/micrometer-registry-humio/src/main/java/io/micrometer/humio/HumioMeterRegistry.java
Show resolved
Hide resolved
@shakuzen I for one (as an Humio employee) do not want to break any dashboards etc. either, so I'm very carefull when I make these changes and by the end of the day these changes are just reflecting what is actually going on in the server where dataspace/repository is being ignored and resolved from the ingest token. |
Thank you for the explanation and care taken here. I've assigned this to the 1.3 milestone so we can get this change out in the next feature release. |
New structured API doesn't require a repo reference so was removed as well.
In our Spring support, we'll want to make sure that the |
In 1.3 we deprecated the `repository` parameter, see micrometer-metrics/micrometer#1544 Corrected the example query, as it already had an `avg` field. Output is the same as before so no need to update screenshot.
In 1.3 we deprecated the `repository` parameter, see micrometer-metrics/micrometer#1544 Corrected the example query, as it already had an `avg` field. Output is the same as before so no need to update screenshot.
New structured API doesn't require a repo reference so was removed as well.
References