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!

2024 Splunk Career Impact Survey | Earn a $20 gift card for participating!

Hear ye, hear ye! The time has come again for Splunk's annual Career Impact Survey!  We need your help by ...

Optimize Cloud Monitoring

  TECH TALKS Optimize Cloud Monitoring Tuesday, August 13, 2024  |  11:00AM–12:00PM PST   Register to ...

What's New in Splunk Cloud Platform 9.2.2403?

Hi Splunky people! We are excited to share the newest updates in Splunk Cloud Platform 9.2.2403! Analysts can ...