Skip to content
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

[8.17] [Stack Monitoring] Do not add empty include array when retrieving logstash pipelines (#202039) #202100

Merged
merged 1 commit into from
Nov 28, 2024

Conversation

kibanamachine
Copy link
Contributor

Backport

This will backport the following commits from main to 8.17:

Questions ?

Please refer to the Backport tool documentation

…stash pipelines (elastic#202039)

## Summary

This PR fixes the query that retrieves Logstash pipeline stats and
metrics to be displayed in Stack Monitoring. The problem with the
existing query is that a `terms` aggregation contains an empty
`"include": []` filtering array, but that has the nasty effect of
excluding everything and not returning anything, hence the screen is
empty.

The fix is to only add the `include` array if it's not empty. The PR
also fixes a wrong field name used in a cardinality aggregation:
`logstash.node.stats.logstash.uuid` instead of
`logstash_stats.logstash.uuid`

Closes elastic#202020

### Checklist

- [X] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.

---------

Co-authored-by: Chris Earle <[email protected]>
(cherry picked from commit b7e46bd)
@kibanamachine kibanamachine merged commit 67e441f into elastic:8.17 Nov 28, 2024
8 checks passed
@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

✅ unchanged

cc @consulthys

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants