Alerts are notifications related to any data event that occurrs in your system. Alerts are created based upon active queries and are triggered when predefined conditions are met. Alerts can be delivered to servers, groups, or individuals either in real-time or periodically. For example, you may define an alert every time a specific status code appears in a web server event. Or, you might set an alert to be triggered if a server's average response time over a 30 minute period exceeds a set threshold.
Alerts should be created to ensure awareness of any urgent or useful event that occurs in your business systems. Here is a list of how alerts can help you improve your day to day business:
- Troubleshoot systems
- Be aware of incidents in real-time
- Proactively discover problems
- Identify security weaknesses
- Detect potential fraud or network threats
- Dramatically reduce application downtime
- Free developers from time-consuming production support
- Respond more quickly to server crashes
- Identify unexpected and/or unwanted operations ocurring in your applications
- Detect inactivity
You can manage active alerts in the Alerts area of the application.
Devo alerts are based on search queries and they are triggered when the results of that specific search meet a specific predefined condition.
You can define two kinds of custom alerts:
- Real time - This type of alert detects when individual events occur that meet a specific condition. These trigger alerts in the moment that the condition is detected. For example, to trigger an alert each time a specific error code is recorded in a server log.
- Scheduled - This type of alert detects when a predefined threshold has been met over a given period of time. The condition can be if the number of events exceeds or does not reach the threshold value.
The types of delivery methods available for sending alerts are described in the table below.
Once defined, delivery methods are selected as part of Alert Policies, which are, in turn, associated with the individual alerts. In this way, a single alert can be distributed using multiple delivery methods.
|Configure alerts to be sent to specific email addresses. You can should set up an email delivery method for each individual user or email group address that will need to recieve alerts by email.|
|HTTP-JSON||Configure alerts to be sent to a server set up to receive JSON objects. The alert is sent by HTTP POST, and encapsulated as a JSON object. The JSON object can be sent by HTTP or HTTPS.|
|Service Desk||Configure alerts to be sent to a server running Service Desk Plus. The alert can be sent using either the REST or SERVLET API.|
|JIRA||Configure alerts to be sent to a server running JIRA.|
|Pushover||Configure alerts to be sent to a server running Pushover, which can forward the alert to iOS and Android, and to desktops via browsers.|
|PagerDuty||Configure alerts to be sent to a server running the PagerDuty platform.|
For more information, see How to set up a delivery method.
- How to set up a delivery method
- Alert policies
- Alerts dashboard
- Alerts and correlation libraries
- How to?
Have we answered your question?
If not, please contact our technical support team via email by clicking the button below.CONTACT US