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

Advice for ElastAlert Index Lifecycle Management? #2785

Open
bowserkn opened this issue May 5, 2020 · 2 comments
Open

Advice for ElastAlert Index Lifecycle Management? #2785

bowserkn opened this issue May 5, 2020 · 2 comments

Comments

@bowserkn
Copy link

bowserkn commented May 5, 2020

Could anyone share advice on setting up ILM for ElastAlert?

I'm on 7.6 Elasticsearch. I'm very confused on how ILM is supposed to work with ElastAlert. I can't seem to enable rollover because there seems to be '_status' hardcoded to the end of ElastAlert indices, and if I try to make the index have a date or number at the end elastalert freaks out saying it can't find the index it needs.

It may be that I don't understand ILM well enough yet, but I can say it would be nice if Elastalert had a) only one index to deal with and b) you could name that index anything you wanted (i.e. no hardcoded index names, or partially hardcoded index names).

If anyone could share advice on how they are doing ILM with ElastAlert I would appreciate it.

@nsano-rururu
Copy link
Contributor

@bowserkn

I searched for an example of Index Lifecycle Management. I found that I was trying to do something similar, but there seems to be no case for Index Lifecycle Management.

Added elastalert_status index timestamping #945
Is it possible to have daily "elastalert_status-%{+YYYY.MM.dd}" indices #684
Size of ElastAlert Metadata Index #178

@vtdat
Copy link

vtdat commented Jan 18, 2021

Could anyone share advice on setting up ILM for ElastAlert?

I'm on 7.6 Elasticsearch. I'm very confused on how ILM is supposed to work with ElastAlert. I can't seem to enable rollover because there seems to be '_status' hardcoded to the end of ElastAlert indices, and if I try to make the index have a date or number at the end elastalert freaks out saying it can't find the index it needs.

It may be that I don't understand ILM well enough yet, but I can say it would be nice if Elastalert had a) only one index to deal with and b) you could name that index anything you wanted (i.e. no hardcoded index names, or partially hardcoded index names).

If anyone could share advice on how they are doing ILM with ElastAlert I would appreciate it.

I'm using current indexes as index write alias and index alias. That might need a little tweak with ElastAlert source code.

If you're willing to maintain another downstream source, then ya, that's possible.

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

No branches or pull requests

3 participants