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

[Stack Monitoring] Shard size alert never fires #114356

Closed
simianhacker opened this issue Oct 7, 2021 · 2 comments · Fixed by #114357
Closed

[Stack Monitoring] Shard size alert never fires #114356

simianhacker opened this issue Oct 7, 2021 · 2 comments · Fixed by #114357
Labels
bug Fixes for quality problems that affect the customer experience Feature:Stack Monitoring Team:Monitoring Stack Monitoring team

Comments

@simianhacker
Copy link
Member

Kibana version:
master (probably more)
Elasticsearch version:
master (probably more)
Original install method (e.g. download page, yum, from source, etc.):
source
Describe the bug:
When you set the shard size threshold to zero the alert never fires.
Steps to reproduce:

  1. Start a cluster with internal monitoring
  2. Create default alerts
  3. Set the shard size threshold to zero
  4. Alert never fires

Expected behavior:
The alert should fire
Any additional context:
It looks like the source_node information is missing from the index_stats documents. This is causing the alert be skipped: https://github.com/elastic/kibana/blob/master/x-pack/plugins/monitoring/server/lib/alerts/fetch_index_shard_size.ts#L136-L143

@simianhacker simianhacker added bug Fixes for quality problems that affect the customer experience Team:Monitoring Stack Monitoring team Feature:Stack Monitoring labels Oct 7, 2021
@elasticmachine
Copy link
Contributor

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

@neptunian
Copy link
Contributor

I think from what @simianhacker and I discussed this was working with internal monitoring but NOT metricbeat monitoring due to fields possibly removed from metricbeat or never existing

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.

3 participants