* Foobar Geez <[email protected]> [20140828 12:25]: > Thanks, Jochen! > > I ran into this yesterday and wondering if the following statement is still > true about GL2 true from > http://stackoverflow.com/questions/9759298/fluentdmongo-vs-logstash: > > At present, Graylog2 uses Elasticsearch as well, but uses only a single > > index for all data. If you're periodically cleaning up old data, this means > > the equivalent of a lot of SQL "delete from table where date>YYYY.MM.DD" > > type-calls to clean out old data, where Logstash defaults to daily indexes > > (the equivalent of "drop table YYYY.MM.DD"), so clean-up is nicer. It also > > results in cleaner searches, requiring less heap space, as you can search > > over a known date because the index is named for the day's data it contains. > > > My use case is to index lot of "time-series" data and create daily/weekly > indexes so I can discard them easily when the agreed retention for that > data expires. > > I would appreciate your thoughts on this.
Size your indexes as needed to ensure that no size-based rotation will occur and trigger the rotation manually: http://support.torch.sh/help/kb/general/the-graylog2-index-model-explained qvb -- pica -- You received this message because you are subscribed to the Google Groups "graylog2" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
