This blog post 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).
Don’t use ControlUp? Learn more about it here.
ControlUp Incident Triggers – Primary Use Cases
Some common incident trigger use cases include:
- 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.
- 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.
- 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.
- Monitoring specific application usage – Exposing certain metrics for particular applications (i.e. how many times the application has been opened and by who).
- 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.
1. Stress Level Settings
Before creating the trigger, we need to check our stress level and adapt it to our specific scenario.
The ControlUp Stress Level incident type applies to all record types in ControlUp (Folders, Hosts, Computers, Sessions, Processes, Executables and Accounts). With the stress level trigger, we will be able to identify performance issues, such as excessive CPU consumption.
In our example, below, we will configure the process’ CPU Stress Level.
Enter ControlUp Settings ⇒ Stress Settings ⇒ select the relevant folder (XenApp6.5 in our case) -> Processes ⇒ CPU Settings:
2. Create the Trigger
To create an incident trigger, click on the “Add Incident Trigger” button on the “ControlUp Management Console” window.
As shown below, if you are monitoring a specific application process, select the ‘Process’ record type. As for choosing a stress level, we are only interested in ‘Critical’ for the sake of our use case.
For this particular use case, we will be using a stress level incident trigger. Therefore we will select “Stress Level” and click Next.
At the end, enter a trigger name and click Finish.
3. Watching it in Action – Viewing Incidents and Email Alerts
Once a new incident occurs, the incident trigger will generate an email alert, as seen below:
In this article, we saw how a ControlUp incident trigger can track advanced performance issues. With ControlUp incident triggers, sysadmins gain a great deal of flexibility with detailed monitoring capabilities that drive transparency and control over their environment’s performance.