Splunk Search

Issue with Time Conversion in JSON String

leftrightleft
Explorer

Hey 👋,

I'm trying to get the time difference between when an event was received and a string representation of the time in the event.  

Here's an example of the event:

 

{
    "action": "created",
    "alert": {
        "number": 818,
        "created_at": "2021-11-16T21:52:12Z",
        "url": "https://somewebsite.com"
    }
}

 

The issue is the conversion of the time in "alert.created_at" from string to epoch.  Once I'm able to get the epoch representation, calculating the difference from _time is easy.  

I'm working off this eval statement, but cant get it to work:

 

 | eval strtime=strptime(alert.created_at, "%Y-%m-%dT%H:%M:%SZ") | table strtime

 

Any thoughts?  Thanks!

Labels (1)
0 Karma
1 Solution

kamlesh_vaghela
SplunkTrust
SplunkTrust

@leftrightleft 

 

Can you please try this?

| eval strtime=strptime('alert.created_at', "%Y-%m-%dT%H:%M:%SZ")

 

My Sample Search :

| makeresults 
| eval _raw="{\"action\": \"created\",\"alert\": {\"number\": 818,\"created_at\": \"2021-11-16T21:52:12Z\",\"url\": \"https://somewebsite.com\"}}" 
| spath 
| eval strtime=strptime('alert.created_at', "%Y-%m-%dT%H:%M:%SZ")


 KV

View solution in original post

kamlesh_vaghela
SplunkTrust
SplunkTrust

@leftrightleft 

 

Can you please try this?

| eval strtime=strptime('alert.created_at', "%Y-%m-%dT%H:%M:%SZ")

 

My Sample Search :

| makeresults 
| eval _raw="{\"action\": \"created\",\"alert\": {\"number\": 818,\"created_at\": \"2021-11-16T21:52:12Z\",\"url\": \"https://somewebsite.com\"}}" 
| spath 
| eval strtime=strptime('alert.created_at', "%Y-%m-%dT%H:%M:%SZ")


 KV

leftrightleft
Explorer

@kamlesh_vaghela, I wish I could give you more than just a thumbs up.  At a minimum, you deserve a high five.  Honestly, I would probably even give you a hug if I could 😄

Seriously though, thanks a lot.  I really was struggling with this.  I didn't realize the single quotes were what was needed.  I actually tried double quotes around the field name at one point, but it interpreted it as literally "alert.created_at".

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!

Your Feedback. Our Roadmap. Visit the PX Feedback Booth at .conf26

You use Splunk every day, come and help shape what's next.  Save Your Seat: Product-Focused Sessions at ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas

Watch Now Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas     Do you ever feel ...