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

Backport PR #17185 to 8.18: Fix empty node stats pipelines #17202

Merged
merged 1 commit into from
Feb 28, 2025

Conversation

github-actions[bot]
Copy link
Contributor

Backport PR #17185 to 8.18 branch, original message:


Release notes

Fixed an issue where the /_node/stats API displayed empty pipeline metrics when X-Pack monitoring was enabled

What does this PR do?

When monitoring is enabled, the metrics store does not initialise data for monitoring pipeline. The api has null pointer when fetching the pipeline config like workers, batch_size.

Why is it important/What is the impact to the user?

/_node/stats gives empty pipelines: {}

Checklist

  • My code follows the style guidelines of this project
  • 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 files (and/or docker env variables)
  • I have added tests that prove my fix is effective or that my feature works

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

Fixed an issue where the `/_node/stats` API displayed empty pipeline metrics
when X-Pack monitoring was enabled

(cherry picked from commit 8678581)
Copy link

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

@kaisecheng kaisecheng merged commit d10aeef into 8.18 Feb 28, 2025
5 of 6 checks passed
@kaisecheng kaisecheng deleted the backport_17185_8.18 branch February 28, 2025 22:52
@elasticmachine
Copy link
Collaborator

💛 Build succeeded, but was flaky

Failed CI Steps

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

Successfully merging this pull request may close these issues.

2 participants