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

[Monitoring] Pipeline cluster listing page breaks with multi-cluster monitoring #50160

Closed
chrisronline opened this issue Nov 11, 2019 · 1 comment · Fixed by #50166
Closed
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:Stack Monitoring Team:Monitoring Stack Monitoring team

Comments

@chrisronline
Copy link
Contributor

Affects 7.4.1 and beyond.

If multiple monitored clusters contain multiple sets of logstash monitoring data (sets meaning with different cluster_uuid), the pipelines listing page breaks with this error:

server   error  [10:07:38.916] [error][monitoring] TypeError: Cannot read property 'logstash_cluster_pipeline_throughput' of undefined
    at processedResponse.pipelines.forEach.pipeline (/Users/chris/dev/repos/kibana/x-pack/legacy/plugins/monitoring/server/lib/logstash/get_pipelines.js:75:19)
    at Array.forEach (<anonymous>)
    at forEach (/Users/chris/dev/repos/kibana/x-pack/legacy/plugins/monitoring/server/lib/logstash/get_pipelines.js:73:31)
    at handler (/Users/chris/dev/repos/kibana/x-pack/legacy/plugins/monitoring/server/routes/api/v1/logstash/pipelines/cluster_pipelines.js:81:32)

This is because of a bug in this PR where the clusterUuid is not passed in properly

@chrisronline chrisronline added bug Fixes for quality problems that affect the customer experience Team:Monitoring Stack Monitoring team Feature:Stack Monitoring labels Nov 11, 2019
@chrisronline chrisronline self-assigned this Nov 11, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/stack-monitoring (Team:Monitoring)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Stack Monitoring Team:Monitoring Stack Monitoring team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants