Splunk Search

How to create an alert for when the VPN goes down but only when the drop lasts more than 1 minute?

splunkcol
Builder

Hi

I need to create an alert for when the VPN goes down but only when the drop lasts more than 1 minute.

I would appreciate your help

 

Right now I have the alert set to report any down events and then manually check which ones last longer than 1 minute.

index=paloalto |search EventID=tunnel-status-down OR EventID=tunnel-status-up

Labels (1)
0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

My first reply would not return results if the VPN was not down for more than a minute - I believe that's the expected scenario.  Then the alert just has to be configured to trigger when the search returns results - meaning the the VPN has been down for at least one minute.

My answer also assumed events would be in reverse time order, which is the default for Splunk searches.  Since your screenshot shows that's not the case, here is an updated search.

index=paloalto EventID=tunnel-status-down OR EventID=tunnel-status-up
| sort - _time
| dedup EventID Object
| where (EventID=tunnel-status-down AND _time < relative_time(now(),"-1m"))
---
If this reply helps you, Karma would be appreciated.

View solution in original post

0 Karma

richgalloway
SplunkTrust
SplunkTrust

Look for where the last event is a status-down and it's been more than a minute since then.

index=paloalto |search EventID=tunnel-status-down OR EventID=tunnel-status-up
| dedup EventID
| where (EventID=tunnel-status-down AND _time < relative_time(now(),"-1m"))
---
If this reply helps you, Karma would be appreciated.

splunkcol
Builder

Hello, it did not bring me results.

This is the result when I only filter by the EventIDs, how can I calculate the time between the first down and the next up?

 

splunkcol_0-1652111461289.png

 

0 Karma

richgalloway
SplunkTrust
SplunkTrust

My first reply would not return results if the VPN was not down for more than a minute - I believe that's the expected scenario.  Then the alert just has to be configured to trigger when the search returns results - meaning the the VPN has been down for at least one minute.

My answer also assumed events would be in reverse time order, which is the default for Splunk searches.  Since your screenshot shows that's not the case, here is an updated search.

index=paloalto EventID=tunnel-status-down OR EventID=tunnel-status-up
| sort - _time
| dedup EventID Object
| where (EventID=tunnel-status-down AND _time < relative_time(now(),"-1m"))
---
If this reply helps you, Karma would be appreciated.
0 Karma
Get Updates on the Splunk Community!

Index This | What did the zero say to the eight?

June 2025 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with this month’s ...

Splunk Observability Cloud's AI Assistant in Action Series: Onboarding New Hires & ...

This is the fifth post in the Splunk Observability Cloud’s AI Assistant in Action series that digs into how to ...

Now Playing: Splunk Education Summer Learning Premieres

It’s premiere season, and Splunk Education is rolling out new releases you won’t want to miss. Whether you’re ...