Splunk Search

How to break nested objects and lists into individual events?

dasaed
Explorer

I have an event with multiple levels of nested objects and lists, that I need to break down into individual events. For example, a single event can look like:

dasaed_0-1645198215353.png

 

And I need to conver that event into a table like this:

Group_name

Sub_group

Subsubgroup

Some other info …

alpha

alpha1

beta

 

alpha

alpha1

gamma

 

alpha

alpha2

a

 

alpha

alpha2

b

 

alpha

alpha3

uno

 

 

I've tried multiple combinations of mvexpand, table, and stats, but I keep getting erroneous results. The command flatten doesn't seem to work, and I fear I might need some crazy regex to parse all the embedded objects and list of objects, not to mention this is only one event, in reality I would have multiple other groups with their corresponding subgroups and stuff. 

Labels (1)
0 Karma
1 Solution

yuanliu
SplunkTrust
SplunkTrust

First of all, please post sample data in text, not in screenshot.  It is much easier for other people to help.

Secondly, the screenshot shows invalid JSON syntax.

Assuming actual data are conformant, the following should give you the desired outcome

 

| spath path=group_name
| spath output=sub_groups path=group.sub_groups{}
| mvexpand sub_groups
| spath input=sub_groups path=subgroup
| spath input=sub_groups output=subsubgroup path=subsubgroup{}
| fields - sub_groups ``` just to clear view, not part of calculation ```
| mvexpand subsubgroup
| spath input=subsubgroup
| table group_name subgroup team "some other info"

 

In the above, I didn't bother to rename fields; for example, "team" is subsubgroup, etc.  In input data, I assumed that there is a field "some other info" under subsubgroup.

Given test data as follows (which you should have supplied in text):

 

{"event":"A",
  "group_name":"alpha",
  "group":{
    "group_name":"alpha",
    "sub_groups":[
     {"subgroup":"alpha1",
      "subsubgroup": [
        {"team":"beta"},
        {"team":"gamma", "some other info":"foo"}]
     },
     {"subgroup":"alpha2",
      "subsubgroup": [
       {"team":"a"},
       {"team":"b", "some other info":"bar"}]
     },
     {"subgroup": "alpha3",
      "subsubgroup": [
       {"team": "uno", "some other info":"baz"}]
     }
   ]
  }
}

 

output would be

group_namesubgroupteamsome other info
alphaalpha1beta 
alphaalpha1gammafoo
alphaalpha2a 
alphaalpha2bbar
alphaalpha3unobaz

View solution in original post

Tags (2)

yuanliu
SplunkTrust
SplunkTrust

First of all, please post sample data in text, not in screenshot.  It is much easier for other people to help.

Secondly, the screenshot shows invalid JSON syntax.

Assuming actual data are conformant, the following should give you the desired outcome

 

| spath path=group_name
| spath output=sub_groups path=group.sub_groups{}
| mvexpand sub_groups
| spath input=sub_groups path=subgroup
| spath input=sub_groups output=subsubgroup path=subsubgroup{}
| fields - sub_groups ``` just to clear view, not part of calculation ```
| mvexpand subsubgroup
| spath input=subsubgroup
| table group_name subgroup team "some other info"

 

In the above, I didn't bother to rename fields; for example, "team" is subsubgroup, etc.  In input data, I assumed that there is a field "some other info" under subsubgroup.

Given test data as follows (which you should have supplied in text):

 

{"event":"A",
  "group_name":"alpha",
  "group":{
    "group_name":"alpha",
    "sub_groups":[
     {"subgroup":"alpha1",
      "subsubgroup": [
        {"team":"beta"},
        {"team":"gamma", "some other info":"foo"}]
     },
     {"subgroup":"alpha2",
      "subsubgroup": [
       {"team":"a"},
       {"team":"b", "some other info":"bar"}]
     },
     {"subgroup": "alpha3",
      "subsubgroup": [
       {"team": "uno", "some other info":"baz"}]
     }
   ]
  }
}

 

output would be

group_namesubgroupteamsome other info
alphaalpha1beta 
alphaalpha1gammafoo
alphaalpha2a 
alphaalpha2bbar
alphaalpha3unobaz
Tags (2)
Get Updates on the Splunk Community!

SplunkTrust Application Period is Officially OPEN!

It's that time, folks! The application/nomination period for the 2025 SplunkTrust is officially open! If you ...

Splunk Answers Content Calendar, June Edition II

Get ready to dive into Splunk Dashboard panels this week! We'll be tackling common questions around ...

Splunk Observability Cloud's AI Assistant in Action Series: Auditing Compliance and ...

This is the third post in the Splunk Observability Cloud’s AI Assistant in Action series that digs into how to ...