Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[8.x] [Stack Monitoring] Do not add empty include array when retrievi…
…ng logstash pipelines (#202039) (#202101) # Backport This will backport the following commits from `main` to `8.x`: - [[Stack Monitoring] Do not add empty include array when retrieving logstash pipelines (#202039)](#202039) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Valentin Crettaz","email":"valentin.crettaz@elastic.co"},"sourceCommit":{"committedDate":"2024-11-28T04:05:51Z","message":"[Stack Monitoring] Do not add empty include array when retrieving logstash pipelines (#202039)\n\n## Summary\r\n\r\nThis PR fixes the query that retrieves Logstash pipeline stats and\r\nmetrics to be displayed in Stack Monitoring. The problem with the\r\nexisting query is that a `terms` aggregation contains an empty\r\n`\"include\": []` filtering array, but that has the nasty effect of\r\nexcluding everything and not returning anything, hence the screen is\r\nempty.\r\n\r\nThe fix is to only add the `include` array if it's not empty. The PR\r\nalso fixes a wrong field name used in a cardinality aggregation:\r\n`logstash.node.stats.logstash.uuid` instead of\r\n`logstash_stats.logstash.uuid`\r\n\r\nCloses https://github.com/elastic/kibana/issues/202020\r\n\r\n### Checklist\r\n\r\n- [X] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n\r\n---------\r\n\r\nCo-authored-by: Chris Earle <chris.earle@elastic.co>","sha":"b7e46bdae9da7ac6ea7346cd3450597796995eb5","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["backport","Team:Monitoring","release_note:skip","Feature:Stack Monitoring","v9.0.0","backport:version","v8.17.0","v8.18.0","v8.16.2","v8.15.6"],"title":"[Stack Monitoring] Do not add empty include array when retrieving logstash pipelines","number":202039,"url":"https://github.com/elastic/kibana/pull/202039","mergeCommit":{"message":"[Stack Monitoring] Do not add empty include array when retrieving logstash pipelines (#202039)\n\n## Summary\r\n\r\nThis PR fixes the query that retrieves Logstash pipeline stats and\r\nmetrics to be displayed in Stack Monitoring. The problem with the\r\nexisting query is that a `terms` aggregation contains an empty\r\n`\"include\": []` filtering array, but that has the nasty effect of\r\nexcluding everything and not returning anything, hence the screen is\r\nempty.\r\n\r\nThe fix is to only add the `include` array if it's not empty. The PR\r\nalso fixes a wrong field name used in a cardinality aggregation:\r\n`logstash.node.stats.logstash.uuid` instead of\r\n`logstash_stats.logstash.uuid`\r\n\r\nCloses https://github.com/elastic/kibana/issues/202020\r\n\r\n### Checklist\r\n\r\n- [X] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n\r\n---------\r\n\r\nCo-authored-by: Chris Earle <chris.earle@elastic.co>","sha":"b7e46bdae9da7ac6ea7346cd3450597796995eb5"}},"sourceBranch":"main","suggestedTargetBranches":["8.17","8.x","8.16","8.15"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202039","number":202039,"mergeCommit":{"message":"[Stack Monitoring] Do not add empty include array when retrieving logstash pipelines (#202039)\n\n## Summary\r\n\r\nThis PR fixes the query that retrieves Logstash pipeline stats and\r\nmetrics to be displayed in Stack Monitoring. The problem with the\r\nexisting query is that a `terms` aggregation contains an empty\r\n`\"include\": []` filtering array, but that has the nasty effect of\r\nexcluding everything and not returning anything, hence the screen is\r\nempty.\r\n\r\nThe fix is to only add the `include` array if it's not empty. The PR\r\nalso fixes a wrong field name used in a cardinality aggregation:\r\n`logstash.node.stats.logstash.uuid` instead of\r\n`logstash_stats.logstash.uuid`\r\n\r\nCloses https://github.com/elastic/kibana/issues/202020\r\n\r\n### Checklist\r\n\r\n- [X] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n\r\n---------\r\n\r\nCo-authored-by: Chris Earle <chris.earle@elastic.co>","sha":"b7e46bdae9da7ac6ea7346cd3450597796995eb5"}},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.15","label":"v8.15.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Valentin Crettaz <valentin.crettaz@elastic.co>
- Loading branch information