Hi,
I have a problem with the Splunk timestamp.
I know that when you have a problem with timestamp, you can modify this 2 ways:
1. Add data and modify the timestamp during the steps of adding manually data on Splunk.
The problem :
For the First Way:
As we can see, Splunk recognizes the time, but not the date correctly, so I will modify the timestamp with the parameter on the left ( prefix and format)
--> I add the format and prefix, Splunk seem to recognize this correctly
(but the prefix is strange because it works also when I write d{2};
or d{1};
or d*;
... )
For the Second Way
edit props.conf
TIME_PREFIX =
... and TIME_FORMAT=
...Then after adding these parameters with the values, is there something else to modify to complete the configuration? Because even with this way, nothing happens and that doesn't work for me.
I missed something maybe, but I don't know what...
Kind Regards
Steve
In Add data wizard, add following parameters. Same things can be added to props.conf directly as well.
SHOULD_LINEMERGE = false
LINE_BREAKER = ([\r\n]+)\d+;\S+
TIME_FORMAT = %d%a%Y %H:%M:%S
TIME_PREFIX = ^\d+;
Remember to restart Indexer/Heavy forwarder where you keep this props.conf
In Add data wizard, add following parameters. Same things can be added to props.conf directly as well.
SHOULD_LINEMERGE = false
LINE_BREAKER = ([\r\n]+)\d+;\S+
TIME_FORMAT = %d%a%Y %H:%M:%S
TIME_PREFIX = ^\d+;
Remember to restart Indexer/Heavy forwarder where you keep this props.conf
Great thanks for your help guys 🙂
The props.conf file to modify is the one for the app that will process the events. If it's the Search & Reporting app then SPLUNK_HOME/etc/apps/search/local/props.conf is the correct file. You should not need TIME_PREFIX. It should be enough to set TIME_FORMAT=%d%a%Y %H:%M:%S
. Note that you must restart Splunk for the change to take effect and the change only applies to new data (nothing can be done about events that are already in Splunk).