I've recently started using and enjoying ES, in particular I'm keen to
exploit the new aggregations feature to report on system metrics data that
is currently being fed into ES indexes.
I'm experimenting with aggregations that fold up things like request rates
per machine or API calls (per machine, globally, etc). I was thinking that
it might be useful to store the aggregation result itself, particularly if
I set a (let's say) weekly TTL on the incoming metrics data but would like
to preserve historical aggregates (e.g. find me the average/min/max request
rate on day 17). I might want to keep the raw metrics for a week, but the
aggregates should potentially stick around for years.
Are there any recommendations/patterns in regards to dealing with these
scenarios? Are there existing means for recomputing aggregates at regular
intervals and emitting those back into ES?
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 firstname.lastname@example.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/4e9acaaf-4702-4d50-a16a-e375efe431e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.