I have now parsed a lot (100GB+) of logfiles into ES and now i saw that the
timestamp from the logfile (the format is dd.MM.yyyy HH:mm:ss.SSS
11.12.2014 17:27:15.178) but ES interpreted it as string.
How can i solve this problem?
With als low as effort as possible because indexing that much data would
need a hell lot of time.
I have now parsed a lot (100GB+) of logfiles into ES and now i saw that the timestamp from the logfile (the format is dd.MM.yyyy HH:mm:ss.SSS 11.12.2014 17:27:15.178) but ES interpreted it as string.
How can i solve this problem?
With als low as effort as possible because indexing that much data would need a hell lot of time.
The things is that we don't have enought storage the generate a new index
and leave the old one as it is
Am Donnerstag, 11. Dezember 2014 17:28:52 UTC+1 schrieb Stefan:
Hello again!
I am having another problem with the ELK-Stack.
I have now parsed a lot (100GB+) of logfiles into ES and now i saw that
the timestamp from the logfile (the format is dd.MM.yyyy HH:mm:ss.SSS
11.12.2014 17:27:15.178) but ES interpreted it as string.
How can i solve this problem?
With als low as effort as possible because indexing that much data would
need a hell lot of time.
The things is that we don't have enought storage the generate a new index and leave the old one as it is
Am Donnerstag, 11. Dezember 2014 17:28:52 UTC+1 schrieb Stefan:
Hello again!
I am having another problem with the ELK-Stack.
I have now parsed a lot (100GB+) of logfiles into ES and now i saw that the timestamp from the logfile (the format is dd.MM.yyyy HH:mm:ss.SSS 11.12.2014 17:27:15.178) but ES interpreted it as string.
How can i solve this problem?
With als low as effort as possible because indexing that much data would need a hell lot of time.
Am Donnerstag, 11. Dezember 2014 17:28:52 UTC+1 schrieb Stefan:
Hello again!
I am having another problem with the ELK-Stack.
I have now parsed a lot (100GB+) of logfiles into ES and now i saw that
the timestamp from the logfile (the format is dd.MM.yyyy HH:mm:ss.SSS
11.12.2014 17:27:15.178) but ES interpreted it as string.
How can i solve this problem?
With als low as effort as possible because indexing that much data would
need a hell lot of time.
Am Donnerstag, 11. Dezember 2014 17:28:52 UTC+1 schrieb Stefan:
Hello again!
I am having another problem with the ELK-Stack.
I have now parsed a lot (100GB+) of logfiles into ES and now i saw that the timestamp from the logfile (the format is dd.MM.yyyy HH:mm:ss.SSS 11.12.2014 17:27:15.178) but ES interpreted it as string.
How can i solve this problem?
With als low as effort as possible because indexing that much data would need a hell lot of time.
Am Donnerstag, 11. Dezember 2014 17:28:52 UTC+1 schrieb Stefan:
Hello again!
I am having another problem with the ELK-Stack.
I have now parsed a lot (100GB+) of logfiles into ES and now i saw that
the timestamp from the logfile (the format is dd.MM.yyyy HH:mm:ss.SSS
11.12.2014 17:27:15.178) but ES interpreted it as string.
How can i solve this problem?
With als low as effort as possible because indexing that much data would
need a hell lot of time.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.