Splunk Search

How to extract field names from an object or nested JSON field?

SwervyMcBourbon
Engager

For these following two events:

 

 

{
  "people": {
    "bob": 172,
    "maria": 161
  }
}

{
  "people": {
    "bob": 172,
    "garth": 180
  }
}

 

 

 
I want to report the number of occurrences of each person's name in the "people" object (the field name itself, not its value).  The desired result of my query against the two events above would be:

 

 

bob: 2
maria: 1
garth: 1

 

 

 

What SPL syntax/commands could I use to achieve this?  I have tried a variety of things online to no avail.

 

 

Labels (5)
0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

See if this helps.

<<your search for people events>>
| spath
```Loop over the people object and make a list of each name found```
| foreach people.* [ eval name=mvappend(name,if(isnotnull('<<FIELD>>'),"<<MATCHSTR>>", null()))]
```Break the name list into separate events```
| mvexpand name
```Count the names```
| stats count by name
---
If this reply helps you, Karma would be appreciated.

View solution in original post

SwervyMcBourbon
Engager

This worked like a charm, thank you @richgalloway !

richgalloway
SplunkTrust
SplunkTrust

See if this helps.

<<your search for people events>>
| spath
```Loop over the people object and make a list of each name found```
| foreach people.* [ eval name=mvappend(name,if(isnotnull('<<FIELD>>'),"<<MATCHSTR>>", null()))]
```Break the name list into separate events```
| mvexpand name
```Count the names```
| stats count by name
---
If this reply helps you, Karma would be appreciated.
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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...