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

Error thrown by elasticsearch/index_summary metricset when xpack.enabled is set to true #12487

Closed
ycombinator opened this issue Jun 10, 2019 · 1 comment · Fixed by #12489
Closed

Comments

@ycombinator
Copy link
Contributor

Observed with Metricbeat built from master and Elasticsearch built from master.

Steps to reproduce

  1. Make sure Elasticsearch API is accessible on http://localhost:9200.
  2. Enable the elasticsearch-xpack Metricbeat module.
    ./metricbeat modules enable elasticsearch-xpack
    
  3. Run Metricbeat.
    ./metricbeat -e
    

Observed behavior

The Metricbeat logs have the following error message:

2019-06-10T03:00:47.439-0700    ERROR   [elasticsearch.index_summary]   index_summary/index_summary.go:92       failure applying stats schema: 8 errors: key `total.docs` not found; key `total.store` not found; key `total.indexing` not found; key `total.search` not found; key `primaries.docs` not found; key `primaries.store` not found; key `primaries.indexing` not found; key `primaries.search` not found

No .monitoring-es-*mb* indices are created.

Expected behavior

No error in the Metricbeat logs and .monitoring-es-*mb* indices are created.

@elasticmachine
Copy link
Collaborator

Pinging @elastic/stack-monitoring

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

Successfully merging a pull request may close this issue.

2 participants