All Apps and Add-ons
Highlighted

Splunk Add-on for Box not timezone offsetting correctly

Contributor

It seems there may be a timestamping issue in the Splunk Add-on for Box. The timestamp from Box is 26 characters long if you include the timezone. However the app is set to a MAX_TIMESTAMP_LOOKAHEAD = 20. As a result, the timezone is not taken into consideration and data is indexed at the incorrect time. The fix would be to adjust every sourcetype in props.conf to MAX_TIMESTAMP_LOOKAHEAD = 26. Thanks

0 Karma
Highlighted

Re: Splunk Add-on for Box not timezone offsetting correctly

Splunk Employee
Splunk Employee

Thanks for the feedback! We will work on integrating the fix into our codebase.

Highlighted

Re: Splunk Add-on for Box not timezone offsetting correctly

Splunk Employee
Splunk Employee

MAXTIMESTAMPLOOKAHEAD is not the length of timestamp instead it tells Splunkd how many chars at most to look at when scan the timestamp. By default, splunkd should take into timezone when it detects timestamp.

0 Karma
Highlighted

Re: Splunk Add-on for Box not timezone offsetting correctly

Contributor

Yes, indeed it does - and by not including the timezone part of the timestamp, the timezone is not accounted for, as it falls outside the current limit of 20 chars. Having implemented the fix that I advised using a local props.conf config and extending to 26 chars, I can tell you it works perfectly and the timezone is now taken into consideration. With a limit of 20, this was not the case.

0 Karma