Hi, Ivan's advice is correct. Currently, curator is the way to go. There is also talk about building an index level TTL in elasticsearch but this is not reality yet.
As to reducing data - first question is whether your using version 1.1.X of marvel - this one has greatly reduced the data signature. If not, upgrading would be the easiest option. O.w. you can also look at the interval settings in the agent. You can get it up to 30s if you want to. At the moment there is no alerting built into Marvel. You can use the marvel data & easily write a nagios script (or similar) to add it to your monitoring data. Regarding RED status explanations - working on it - watch for the upcoming release :) Cheers, Boaz On Monday, May 12, 2014 10:30:00 PM UTC+2, Ivan Brusic wrote: > > I do not use Marvel, but another monitoring system built on top of > Elasticsearch. I use the Elasticsearch Curactor to delete old indices: > https://github.com/elasticsearch/curator > > I have a cron entry to run the curator once per day. Perhaps something > already exists in Marvel, not sure since I am not a user. > > Cheers, > > Ivan > > > > On Mon, May 12, 2014 at 7:39 AM, deepakas > <[email protected]>wrote: > >> Is there a way to set marvel to delete the marvel indices after 7 days. It >> looks like Marvel is generating around 2 GB of data everyday. Our disk >> got >> full 2 times because of Marvel data. Is there a way to reduce the amount >> of >> data generated by marvel ? >> >> Also is there any plan to add alert mechanisms in Marvel. >> For example if the Marvel status goto red it will be good to get an email >> for a specified user. I see Marvel status as red. But it doesnt show why >> it >> is causing red. It will be good to get some alerts with the details when >> the cluster status goes red. >> >> >> >> -- >> View this message in context: >> http://elasticsearch-users.115913.n3.nabble.com/Marvel-Indices-taking-lot-of-space-Can-we-specify-automatic-delete-of-marvel-indice-tp4055729.html >> Sent from the ElasticSearch Users mailing list archive at Nabble.com. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "elasticsearch" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/1399905548133-4055729.post%40n3.nabble.com >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/c446d35c-c3e5-4c5e-91e4-09f39c3e4b42%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
