Incident Triggers

 

This article will highlight ControlUp’s incident trigger and e-mail alerting feature. By exploring the ins and outs of the feature, along with its major use cases, we will demonstrate how to create a specific incident trigger using a typical use case. Covering the entire process from start to finish, we will also explain how an incident is detected, what happens after it is unearthed, and finally the resulting email alert configuration. With this information, you will be able to configure an advanced incident trigger, including email alerts, with your very own console.

ControlUp incident triggers let you know about important events in your network, whether you, specifically, indicate the events you want to be observed or ControlUp brings them to your attention. That way, whenever a specific incident is taking place, you can take proper action. Whenever a specific incident is detected, multiple follow-up actions can be carried out (i.e. email alerts, mobile push notifications to Android or IOS applications, and event logs).

Here we will walk you through defining incident triggers. Don’t skip this step, as it will enable you to get alerts for any abnormal incidents which may happen in your environment. You will want to be notified immediately when things go wrong – so you can stay on top of things even when you are not in the office.

Don’t use ControlUp? Learn more about it here.

ControlUp Incident Triggers – Primary Use Cases

Some common incident trigger use cases include:

  1. Detecting when critical Windows services are no longer available - (i.e. have crashed or stopped) – ControlUp can monitor particular Windows services so the appropriate actions can be taken.
  2. Uncovering host, server, or endpoint performance issues - (i.e. when RDS servers or VDI Endpoints exceed a stress level threshold) – ControlUp can detect when high resource usage causes increased levels of stress to be placed on systems or processes.
  3. Identifying application performance issues – ControlUp observes application stress levels and detects when an application or specific process (i.e. .exe file) is consuming too much memory, I/O, or CPU.
  4. Monitoring specific application usage – Exposing certain metrics for particular applications (i.e. how many times the application has been opened and by who).
  5. Catching specific Windows events – ControlUp triggers can detect when a specific event is created on any Windows-managed computer.

Creating an Advanced Application Performance Incident Trigger

Let’s begin our exploration into incident triggers with an application performance use case. One of our customers’ ERP applications started behaving erratically to the extent that when a user would begin performing an action, CPU usage would reach 30%. After a mere 30 seconds, this caused processes to jam up, prohibiting end users from using the application. As a result, the sysadmin wanted to be notified of this peculiar behavior as well as the accompanying information that could be saved for further analysis and troubleshooting.

ControlUp monitors specific processes and enables the detection of similar cases, including notifying sysadmins when issues occur. ControlUp triggers can be configured with advanced filters to monitor a specific process at hand with a defined threshold metric, such as CPU utilization.

For this specific use case, we will simulate an ERP.EXE application’s processes, in efforts to show exactly how to create an incident trigger with the valid parameters, as well as a follow up email alert.

Check out our User Guide to learn more about incident triggers.

Watch the video below to learn how to easily define these incident triggers:

 

 

Powered by Zendesk