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 should use Rollover API #30045

Closed
elasticmachine opened this issue Feb 10, 2017 · 1 comment
Closed

Monitoring should use Rollover API #30045

elasticmachine opened this issue Feb 10, 2017 · 1 comment

Comments

@elasticmachine
Copy link
Collaborator

Original comment by @skearns64:

Today, we create daily indexes for ES and Kibana, but this is often wasteful, as these tend to end up as rather small indexes/shards that take up unnecessary cluster resources to manage. Using the rollover API, we could more easily specify a reasonable target number of docs that, when exceeded, would cause a new index to be created.

Using the rollover API does have the drawback in that it is less efficient to maintain a fixed history duration, so we'd need to decide if we were comfortable with delete-by-query before undertaking this.

@jakelandis
Copy link
Contributor

closing in favor of #38470

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

No branches or pull requests

4 participants