[8.10](backport #40275) [Metricbeat/kibana/status] Add support for v8format #40287
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed commit message
Added the v8-format-compliant
status.overall.level
field in the metrics.The v8 format was the default starting... ehem... v8.0.0 😅
While I was at it, I also added
status.overall.summary
for a human-friendlier explanation of the status.Checklist
[ ] I have commented my code, particularly in hard-to-understand areas[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration filesCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Disruptive User Impact
The new field (and values) needs to be used in alerts/visualizations. Refer to elastic/kibana#76054 for more information about the breaking changes.
Related issues
Use cases
Stack Monitoring.
cc @elastic/kibana-core @elastic/stack-monitoring
This is an automatic backport of pull request #40275 done by [Mergify](https://mergify.com).