Splunk Search

Need help on how to alert if daily count exceed 30 days average

acesolar
Engager

Hi all,

   Need some advice here. I have some logs that has the URL and the HTTP  response code.

   Sample here 

POST /abc/xyz 200
POST /abc/xyz 401
POST /abc/xyz 500

  Is there a way for me to do a search so that I can compare today count by response code, and alert if the count exceeds the 30 days average count of the response code?

 

Thanks

Labels (2)
0 Karma
1 Solution

ITWhisperer
SplunkTrust
SplunkTrust

Do a count by day for the last 30 days, then use eventstats to add a column with the average to every event, then reduce your events to just cover the day (or days) you are interested in, and compare the daily count to the average. Something like this

| bin span=1d _time
| stats count by _time response_code
| eventstats avg(count) as average by response_code
| where _time >= relative_time(now,"@d")
| where count>average

 

View solution in original post

0 Karma

acesolar
Engager

Thank you. It worked like a charm

0 Karma

ITWhisperer
SplunkTrust
SplunkTrust

Do a count by day for the last 30 days, then use eventstats to add a column with the average to every event, then reduce your events to just cover the day (or days) you are interested in, and compare the daily count to the average. Something like this

| bin span=1d _time
| stats count by _time response_code
| eventstats avg(count) as average by response_code
| where _time >= relative_time(now,"@d")
| where count>average

 

0 Karma
Get Updates on the Splunk Community!

Enterprise Security Content Update (ESCU) | New Releases

In December, the Splunk Threat Research Team had 1 release of new security content via the Enterprise Security ...

Why am I not seeing the finding in Splunk Enterprise Security Analyst Queue?

(This is the first of a series of 2 blogs). Splunk Enterprise Security is a fantastic tool that offers robust ...

Index This | What are the 12 Days of Splunk-mas?

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