Alerting

Splunk Alerting Rule for Recaptcha Served

brewster88
New Member

Afternoon All,

Just wanted to raise a question and get some ideas for a potential Splunk Alert that would trigger once a certain amount of recapture challenge requests per minute are served. Please note we ingest these logs from our WAF which in turns goes into an index labelled 'incapsula'

So Im currently using the below query.

index=incapsula AND site="Example*" AND act=REQ_CHALLENGE_CAPTCHA AND action=blocked | bucket span=1m _time | stats first(site) as site, count(request) as requests by _time |  where requests > 80 | dedup site

This gives decent information however its not really clear from the visualization or statistics if the results are the amount of times that requests per minute have gone over 80 in which case I need to add another column showing a count? or is this the actual data where number of requests has gone over 80 and thus gives me back information on any figure that went above 80 for that site?

Happy to provide more context/details if i can!

Tags (2)
0 Karma
1 Solution

sduff_splunk
Splunk Employee
Splunk Employee

I think what you are after is
index=incapsula AND site="Example*" AND act=REQ_CHALLENGE_CAPTCHA AND action=blocked
| bucket span=1m _time
| stats count(request) as requests by _time, site
| where requests > 80

This should tell you every minute where the number of requests for a particular site were greater than 80.

What is the purpose of the last |dedup site?

View solution in original post

0 Karma

sduff_splunk
Splunk Employee
Splunk Employee

I think what you are after is
index=incapsula AND site="Example*" AND act=REQ_CHALLENGE_CAPTCHA AND action=blocked
| bucket span=1m _time
| stats count(request) as requests by _time, site
| where requests > 80

This should tell you every minute where the number of requests for a particular site were greater than 80.

What is the purpose of the last |dedup site?

0 Karma

brewster88
New Member

Super useful! We were able to build something on this.

We have multiple websites labelled as 'site' in our Incapsula index and this was so we could see try to see where the stem of the issue was.

Took the dedup away as well and gave us the content we needed.

Thanks Kindly 🙂

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