Splunk Search

Why is transaction maxspan=1mon span=1mon showing results for MAX that are more than 1 month?

christopheryu
Communicator

I'm working on Juniper syslogs and trying to extract data using search below:

index=A sourcetype=B LSP_DOWN OR LSP_UP | transaction LSP startswith="LSP_DOWN" endswith="LSP_UP" maxspan=1mon | timechart span=1mon count avg(duration) AS AVG max(duration) AS MAX min(duration) AS MIN stdev(duration) AS STDEV | eval AVG=tostring(AVG, "duration"), MAX=tostring(MAX, "duration"), MIN=tostring(STDEV, "duration"), STDEV=tostring(STDEV, "duration")

The issue is some of the results being showed for MAX are more than 1 month, even though maxspan=1mon span=1mon are included in the search.

0 Karma
1 Solution

ntaylorsplunk
Explorer

The maxspan argument to the transaction command may be part of the reason you're getting incorrect results. The documentation for the transaction command doesn't show months as being a valid time specifier for the maxspan argument.

http://docs.splunk.com/Documentation/Splunk/6.4.2/SearchReference/Transaction

View solution in original post

ntaylorsplunk
Explorer

The maxspan argument to the transaction command may be part of the reason you're getting incorrect results. The documentation for the transaction command doesn't show months as being a valid time specifier for the maxspan argument.

http://docs.splunk.com/Documentation/Splunk/6.4.2/SearchReference/Transaction

Get Updates on the Splunk Community!

Index This | I am a number, but when you add ‘G’ to me, I go away. What number am I?

March 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...