All Apps and Add-ons

Splunk Add-on for Box not timezone offsetting correctly

pj
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

kchen_splunk
Splunk Employee
Splunk Employee

MAX_TIMESTAMP_LOOKAHEAD 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

pj
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

mreynov_splunk
Splunk Employee
Splunk Employee

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

Get Updates on the Splunk Community!

Index This | I am a number, but when you add ‘G’ to me, I go away. What number am I?

March 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...