Getting Data In

HEC timestamp parsing

PickleRick
SplunkTrust
SplunkTrust

Hello there.

I noticed lately (in a kinda painful way 😉) that if the time field is present in json sent to a HEC collector endpoint, the timestamp is not getting parsed from the message. But since the documentation differs between 8.0 and 7.x in this regard (https://docs.splunk.com/Documentation/Splunk/7.3.9/Data/HECRESTendpoints - doesn't say a word about timestamp parsing whereas 8.0.0 gives whole paragraph about optional parameter affecting the parsing) - does anyone know whether the 7.x versions behaved the same way?

I mean - did the timestamp parsing in 7.x also wasn't performed at all if the time field was present?
Did the behaviour changed or was it simply that the docs were supplemented?

Labels (3)
0 Karma

vik_splunk
Communicator

@PickleRick did you manage to figure out a solution to this, please?

0 Karma

PickleRick
SplunkTrust
SplunkTrust

No. I assume that there is simply no ?auto_extract_timestamp=true functionality for versions before 8.0.

After that - it works OK.

0 Karma

richgalloway
SplunkTrust
SplunkTrust

Submit feedback on the 7.3.9 docs asking for clarification.

---
If this reply helps you, Karma would be appreciated.

PickleRick
SplunkTrust
SplunkTrust

Well... Doesn't hurt to try 🙂

Thanks for the suggestion.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Splunk App Dev Quarterly Roundup: AI, Agents, and Innovation!

Another quarter, another wave of innovation. From complex integrations to pushing the limits ...

What’s New in Splunk AI: Volume 02

Welcome to the second edition of “What’s New in Splunk AI” where we look at the latest and greatest updates, ...

Value Insights: Now Generally Available in the CMC

Organizations are under pressure to move faster, control cost, expand AI adoption, and prove value with more ...