Getting Data In

How to extract sum totals for data in a nested JSON object?

stephenmelrose
Engager

Hi there,

I have the following log line format (slightly edited for anonymity),

2013-08-14T08:54:10.098+0100 [INFO] {process-0.1735} spin-processor - [TIMER] some.request.complete {"id":"a1b2c3d4e5","sequenceNo":2,"fooId":"f6g7h8i9j0","duration":2.981,"totalActions":170,"actions":{"Foo.UPDATED":1,"Bar.UPDATED":169}}

The bit my question relates to is the actions key in the JSON object. Ultimately what I want is to get a table containing the sum total for each action type over a given time period, e.g.

+----------------------+
| Action       | Total |
+----------------------+
| Foo.INSERTED | 2     |
| Foo.UPDATED  | 56    |
| Bar.INSERTED | 169   |
| Bar.UPDATED  | 5678  |
+----------------------+

Any idea how I would do this?

The closest I've got so far is to manually do a sum() on each type (as I'm already SPATHing the JSON), but the table it gives me is the wrong way round to what I want, e.g.

+-----------------------------------------------------+
| sum(actions.Foo.UPDATED) | sum(actions.Bar.UPDATED) |
+-----------------------------------------------------+
| 56                       | 5678                     |
+-----------------------------------------------------+

Thanks.

Tags (3)

russellliss
Path Finder

I was sort of able to do this myself. You may want to try

Based on your example above:

| spath input=some.request.complete actions{} | mvexpand actions{} | spath input=actions{} | stats sum("Bar.UPDATED") by "Foo.UPDATED"

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!

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 ...