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

Better error messaging for Elastic stacks' metricsets #8551

Merged

Conversation

ycombinator
Copy link
Contributor

@ycombinator ycombinator commented Oct 3, 2018

This PR makes error messages better and more consistent across all metricsets for Elastic stack products, including the xpack monitoring code paths:

  • elasticsearch/ccr
  • elasticsearch/cluster_stats
  • elasticsearch/index
  • elasticsearch/index_recovery
  • elasticsearch/index_summary
  • elasticsearch/ml_job
  • elasticsearch/node
  • elasticsearch/node_stats
  • elasticsearch/pending_tasks
  • elasticsearch/shard
  • kibana/status
  • kibana/stats
  • logstash/node
  • logstash/node_stats

@ycombinator ycombinator added in progress Pull request is currently in progress. Metricbeat Metricbeat needs_backport PR is waiting to be backported to other branches. v7.0.0-alpha1 monitoring v6.5.0 labels Oct 3, 2018
@ycombinator ycombinator force-pushed the metricbeat-xpack-better-error-msgs branch 2 times, most recently from fbe4e4e to 2f8b96d Compare October 3, 2018 18:48
@ycombinator ycombinator force-pushed the metricbeat-xpack-better-error-msgs branch from cbc0606 to b250cc4 Compare October 3, 2018 20:06
@ycombinator ycombinator force-pushed the metricbeat-xpack-better-error-msgs branch from b250cc4 to f689ad9 Compare October 3, 2018 20:16
@ycombinator ycombinator force-pushed the metricbeat-xpack-better-error-msgs branch from 17d4f2d to 073d197 Compare October 3, 2018 23:22
@elastic elastic deleted a comment from houndci-bot Oct 4, 2018
@ycombinator ycombinator requested a review from ruflin October 4, 2018 00:08
@ycombinator ycombinator added review and removed in progress Pull request is currently in progress. labels Oct 4, 2018
@ycombinator ycombinator force-pushed the metricbeat-xpack-better-error-msgs branch 3 times, most recently from d08395d to 7a5554b Compare October 4, 2018 04:59
@ycombinator ycombinator force-pushed the metricbeat-xpack-better-error-msgs branch from 7a5554b to 357f9e6 Compare October 4, 2018 05:36
@ycombinator
Copy link
Contributor Author

jenkins, test this

@@ -20,6 +20,10 @@ package stats
import (
"encoding/json"

"github.com/elastic/beats/metricbeat/module/kibana"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Import mess, but no need to fix now.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in 077d919.

@ycombinator
Copy link
Contributor Author

@ruflin Cleaned up imports. Still LGTM?

@ruflin
Copy link
Contributor

ruflin commented Oct 4, 2018

@ycombinator Yes

@ycombinator ycombinator merged commit a164d7b into elastic:master Oct 4, 2018
@ycombinator ycombinator deleted the metricbeat-xpack-better-error-msgs branch October 4, 2018 19:26
@ycombinator ycombinator removed the needs_backport PR is waiting to be backported to other branches. label Oct 4, 2018
ycombinator added a commit that referenced this pull request Oct 5, 2018
…metricsets (#8577)

Cherry-pick of PR #8551 to 6.x branch. Original message: 

This PR makes error messages better and more consistent across all metricsets for Elastic stack products, including the xpack monitoring code paths:

* [x] `elasticsearch/ccr`
* [x] `elasticsearch/cluster_stats`
* [x] `elasticsearch/index`
* [x] `elasticsearch/index_recovery`
* [x] `elasticsearch/index_summary`
* [x] `elasticsearch/ml_job`
* [x] `elasticsearch/node`
* [x] `elasticsearch/node_stats`
* [x] `elasticsearch/pending_tasks`
* [x] `elasticsearch/shard`
* [x] `kibana/status`
* [x] `kibana/stats`
* [x] `logstash/node`
* [x] `logstash/node_stats`
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