Splunk Search

Filtering out values and keeping the rest. How?

robertwatkins
Engager

I have a log file that shows times to complete certain tasks and I want to create a table of values. Unfortunately, there are some that show that no time has elapsed and I'd like to ignore them. (certainly, this ideas is suspect, but bear with me 🙂 )

Here is a sample of the data I have:

duration= 0:00:00
duration= 1:00:00
duration= 0:01:00
duration= 0:00:00

Here is the way I had considered capturing this, but I'm still getting the 0:00:00 values in my table.

rex field=_raw "duration= (?!0:00:00)(?<MyTime>.*) | table MyTime

What am I missing?

Tags (3)
1 Solution

BenjaminWyatt
Communicator

Perhaps there is a simpler way to accomplish this. Have you tried adding a "where" clause like:

| where NOT duration="0:00:00" | table MyTime

I do a lot of reporting where I use clauses like this to exclude zero-duration events from my charts and graphs.

Note that my method keeps the zero-duration field values in the data set, it just tells Splunk to exclude them from the reporting commands. Your method would actually remove the zero-duration field values altogether (though keeping the underlying events in the data set). So in that sense, your method is more thorough, but it may be more than you need for this use case. Does that make sense?

View solution in original post

BenjaminWyatt
Communicator

Perhaps there is a simpler way to accomplish this. Have you tried adding a "where" clause like:

| where NOT duration="0:00:00" | table MyTime

I do a lot of reporting where I use clauses like this to exclude zero-duration events from my charts and graphs.

Note that my method keeps the zero-duration field values in the data set, it just tells Splunk to exclude them from the reporting commands. Your method would actually remove the zero-duration field values altogether (though keeping the underlying events in the data set). So in that sense, your method is more thorough, but it may be more than you need for this use case. Does that make sense?

BenjaminWyatt
Communicator

Yay! I find that happens a lot with Splunk. I have a Splunk t-shirt that says, "See your world...maybe wish you hadn't."

0 Karma

robertwatkins
Engager

Yay! That fixed one problem (and exposed another for me to solve that I didn't know I had) 🙂

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