All Apps and Add-ons

Website Monitoring: What are the default units for the website search? milliseconds?

syjl
New Member

Our web sites seem to alert no matter what, even though it is under the 1000 ms in the macro. Is it alerting based on this search which was cloned from the default website monitoring search? If so, what needs to be changed? It appears that this statement may be at 1-3 milliseconds.

eval time_exceeded=if(response_time>`response_time_threshold`,1,0) | eval avg_time_exceeded=if(avg_response_time>`response_time_threshold`,1,0) | eval response_time=round(response_time, 3)." ms" | eval average=round(avg_response_time, 2)." ms" | eval maximum=round(max_response_time, 2)." ms" | eval range=round(min, 0)." - ".round(min+range, 0)." ms" | table title url response_code last_checked time_exceeded response_time avg_time_exceeded average range sparkline_response_time  | `timesince(last_checked,last_checked)`
0 Karma

LukeMurphey
Champion

The search that you are using doesn't filter out results that are within the threshold. For alerting, you want a search that only returns results when a problem is identified (zero results when there are zero problems).

The app comes with a search named "website_performance_problems" which is intended for this type of alerting. I recommend using or cloning that one since it filters results unless they exceed the timeout or indicate a failure (like an problematic return code).

0 Karma
Get Updates on the Splunk Community!

Observe and Secure All Apps with Splunk

  Join Us for Our Next Tech Talk: Observe and Secure All Apps with SplunkAs organizations continue to innovate ...

Splunk Decoded: Business Transactions vs Business IQ

It’s the morning of Black Friday, and your e-commerce site is handling 10x normal traffic. Orders are flowing, ...

Fastest way to demo Observability

I’ve been having a lot of fun learning about Kubernetes and Observability. I set myself an interesting ...