Alerting

Alert trigger conditions

danbutterman
Explorer

Hello Splunk community,

I have an alert setup that will trigger when a website status does not equal 200:

index=perfmon host="nameofsearchhead" sourcetype=httpstatus 
| where status!=200 
| lookup Prod-Websites.csv url AS url OUTPUTNEW server
| table _time,url,status

The results in the statistics tab show up as three columns: time, url, status code.

The alert currently triggers whenever I receive more than 4 results (which could be 5 different urls, that had a single non-200 event each).

I would like for the alert to trigger whenever I receive more than 4 results (non-200 events) for a single url, instead.

Tags (1)
0 Karma
1 Solution

somesoni2
Revered Legend

Try like this

Alert search

index=perfmon host="nameofsearchhead" sourcetype=httpstatus 
 | where status!=200 
 | lookup Prod-Websites.csv url AS url OUTPUTNEW server
 | table _time,url,status | eventstats count by url | where count>4

Alert condition

when number of results > 0

View solution in original post

somesoni2
Revered Legend

Try like this

Alert search

index=perfmon host="nameofsearchhead" sourcetype=httpstatus 
 | where status!=200 
 | lookup Prod-Websites.csv url AS url OUTPUTNEW server
 | table _time,url,status | eventstats count by url | where count>4

Alert condition

when number of results > 0

danbutterman
Explorer

Will do!

Thank you, somesoni2!

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!

Where Innovation Takes Flight: The Splunk4Aviation Flight Sim Lands at .conf26

If you hear someone at .conf26 shouting "gear down, GEAR DOWN" across the show floor, you have found us.  The ...

Turn Cisco Telemetry Into Action with Cisco Data Fabric, powered by the Splunk ...

The surge in machine data is already hitting enterprise budgets, and the agentic era will only intensify it. ...

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