On Fri, Jan 20, 2017 at 4:46 AM, Jochen Schalanda <[email protected]> wrote:
> We already found out in IRC that there are some messages with strange > timestamps in your indices which lead to the problem that the time range of > all indices are overlapping which in turn means Graylog will always query > all indices, no matter how big or small your selected time frame is. > Surely such "strange timestamps" are corrupt and so should be ignored/dropped? If a corrupt field can lead to a crash, then stronger typing of that field should be a requirement? -- Cheers Jason Haar Information Security Manager, Trimble Navigation Ltd. Phone: +1 408 481 8171 PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1 -- You received this message because you are subscribed to the Google Groups "Graylog Users" 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/graylog2/CAFChrgJ62o_t23aWVrMWqfcsUDJg5g%2B9MpZjb%2B%3DEVfxHM-rksA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
