Getting Data In

How to extract timestamp from JSON file

jwalzerpitt
Influencer

I am uploading a JSON file into a test index and I'm trying to set the timestamp for and prefix. The events in the JSON file always start as follows:

{'received': '2020-02-27 10:49:07', 'operator_id': None, 'sender':

I configured the Timestamp format as follows:

%Y-%m-%dT%H:%M:%S

and the Timestamp prefix as:

'(\d{4})-(\d{2})-(\d{2})\s(\d{2}:\d{2}:\d{2})'

and when I tab out of the field, I still get the message of, "No results found. Please change source type, adjust source type settings, or check your source file."

Is there something wrong with my format or prefix (or both)?

Thx

0 Karma

manjunathmeti
Champion

Yes, JSON is not valid. Put keys and string values in double quotes like below, change Timestamp format to %Y-%m-%d %H:%M:%S and add new setting (under Advanced dropdown) TIMESTAMP_FIELDS = received.

{"received": "2020-02-27 10:49:07", "operator_id": "None", "sender": "A"}

0 Karma

to4kawa
Ultra Champion

prefix is a word, letter, or number placed before another.

[your sourcetype]
TIME_PREFIX = received\':\s\'
TIME_FORMAT = %F %T
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!

(re)Introducing the Splunk Community Champions + 2026 – 2027 Splunk MVPs ...

This program exists as a channel to empower and recognize Splunk advocates and help supercharge initiatives to ...

Introducing the 2026 - 2027 SplunkTrust cohort!

The goal of the SplunkTrust™ membership has historically been to acknowledge and recognize those who go above ...

Pro Tips for .conf26: How to Prep Like a Splunk Veteran

There’s no shortage of incredible content lined up for .conf26 in Denver, from deep-dive technical sessions ...