Splunk Search

Table per size and error code

LCM
Contributor

Hi all,

A though one for me, but maybe an easy one for you! I want to count error messages and show it in a table per size range.

Please 'enhance' the command: index="myindex" source="mysource" host="myhost" [your-magic]

I appreciate any creative ideas as long as it looks similarish as below 🙂

Output:

Message Size (KB)   failure    debug    error    NOT failure/debug/error
0-100               13         21       0        3939 
100-200             10         16       0        3
200-500             52          6       3        0
500-1000            29          2       35       5
>1000                0          0       58       0

Cheers,
Martin

0 Karma
1 Solution

Ledion_Bitincka
Splunk Employee
Splunk Employee

you can easily create that table by following these steps:

  1. compute the Message Size field and create the ranges you like
  2. create another field for the columns you need to have (below I assume you already have it and it's name is log_level)
  3. use the chart command to generate your table

Here's an example:

.... | eval ms=len(_raw) | eval MessageSize=if(ms<100, "0-100", if(ms<200, "100-200", ">200")) | chart count over MessageSize by log_level

View solution in original post

Ledion_Bitincka
Splunk Employee
Splunk Employee

you can easily create that table by following these steps:

  1. compute the Message Size field and create the ranges you like
  2. create another field for the columns you need to have (below I assume you already have it and it's name is log_level)
  3. use the chart command to generate your table

Here's an example:

.... | eval ms=len(_raw) | eval MessageSize=if(ms<100, "0-100", if(ms<200, "100-200", ">200")) | chart count over MessageSize by log_level
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 ...