Alerting

Alert when service stopped using perf mon

matthewcanty
Communicator

source="Perfmon*" counter="% Processor Time" | chart last(Value) by _time, host

How can I develop this search into an alert, which detects when a host has stopped sending perfmon events.

I would like it to send an email to me stating which host is no longer working.

Tags (2)
0 Karma
1 Solution

cphair
Builder

If you have an index dedicated to perfmon, you might find metadata easier:


| metadata type=hosts index=perfmon | where lastTime<now()-900

This search returns the machines that haven't reported anything in 15 minutes; I'm assuming the actual counter is irrelevant to you. You can adjust the time as required, but I wouldn't go much shorter or you'll get a bunch of false positives during reboots. Once you have the search tuned the way you want it, you can set up the alert as described in http://docs.splunk.com/Documentation/Splunk/latest/User/SchedulingSavedSearches.

View solution in original post

0 Karma

cphair
Builder

If you have an index dedicated to perfmon, you might find metadata easier:


| metadata type=hosts index=perfmon | where lastTime<now()-900

This search returns the machines that haven't reported anything in 15 minutes; I'm assuming the actual counter is irrelevant to you. You can adjust the time as required, but I wouldn't go much shorter or you'll get a bunch of false positives during reboots. Once you have the search tuned the way you want it, you can set up the alert as described in http://docs.splunk.com/Documentation/Splunk/latest/User/SchedulingSavedSearches.

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!

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

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...