- The Devo data operations platform
- Getting started
- Domain administration
- Sending data to Devo
- Supported technologies
-
Querying your data
- Accessing data tables
-
Working in the query window
- Setting up a data table
- Building a query
-
Generate charts
- Affinity chord diagram
- Availability timeline
- Bipartite chord diagram
- Bubble chart
- Chart aggregation
- Custom date chart aggregation
- Flame graph
- Flat world map by coordinates
- Flat world map by country
- Google animated heat map
- Google area map
- Google heat map
- Graph diagram
- Histogram
- Pie chart
- Pie layered chart
- Punch card
- Sankey diagram
- Scatter plot
- Time heatmap
- Voronoi treemap
- Data enrichment
- Advanced data operations
- Managing your queries
- Best practices for data search
-
Dashboards
- Setup a data source
- Create a new dashboard
-
Working with dashboard widgets
- Availability timeline widget
- Chord diagram widget
- Circle world map widget
- Color key value widget
- Color world map widget
- Column chart widget
- Comparative chart widget
- Funnel widget
- Gauge meter widget
- Google heatmap widget
- Heat calendar widget
- Line chart widget
- Monitoring widget
- Pie chart widget
- Punch card widget
- Sectored pie chart widget
- Table widget
- Time heatmap widget
- Tree diagram widget
- Voronoi tree widget
- Configuring and sharing dashboards
- Panels
-
Alerts and notifications
- Configuring alerts
- Managing triggered alerts
- Pre-installed alert reference
- Notifications
- Applications
- Social Intelligence
- API reference
Alerts and notifications / Configuring alerts / Create a new alert / Alert trigger methods
Download as PDFAlert trigger methods
There are several methods available for triggering alerts in Devo. Here we describe the six methods and offer examples for each.
Each
The each method triggers an alert for each new event that meets the query conditions.
To create a query that can be used to trigger a simple alert, you can apply filters to data and create new columns, but groups and aggregated values are optional.
The threshold for this kind of alert is defined by the filters you have applied in the query. So, each time that an event is written to the data table and meets the conditions of your query, an alert will be triggered.
An example of a simple alert based on firewall log data might be to trigger an alert whenever there is a connection attempt from a blacklisted IP address. In this case, the query should be filtered to include only events where the source IP addresses are confirmed to also appear on a blacklist lookup table.
Several
The several method triggers an alert when a given number of events occur within a given time period.
To create a query that can feed an alert using this trigger method, you can apply filters and create new columns, but do not group the table's events.
The threshold for this kind of alert is defined by the time period and the threshold number of events you specify. So, the alert process will maintain a count of events that meet the conditions of your query over the last time period and, trigger an alert with the threshold number has been exceeded. The time period is rolling, that is to say that if your chosen time period is 1 hour, the alert will maintain a running count of events over the last 60 minutes.
An example of this trigger method based on firewall log data might be to trigger an alert whenever there are more than 500 connection attempts from a single IP address within a 1-minute period.
Low
The low method follows the same principle as the several method except that it triggers an alert when the threshold is not met.
An example might be an alert set to trigger based on heartbeat events since we want to be notified when a system is not sending it's heartbeat events when expected.
Rolling
Based on a user-defined schedule, this method triggers an alert for each event that matches the query conditions. This is essentially the same as the each method except that this alert only checks for the trigger conditions at user-specified intervals and over a configurable time period. This is useful for informative alerts and not recommended for urgent alert conditions.
An example of this kind of alert can be to check, every hour, for events in the last 30 minutes that meet the criteria of the query.
Deviation
The deviation method triggers an alert every time the aggregated value of a single grouped element is significantly higher or lower than the group's median value.
To create a query that can be used to trigger a deviation alert, you can apply filters to data and create new columns as usual. But you must group table events by at least two elements (usually by time, then by other table fields) and add just one aggregated value.
You can express the threshold for this kind of alert by either the absolute deviation or a percentage. So, each time that the aggregated value of a grouped element varies significantly from the median value of all the elements within the same grouping period, an alert will be triggered.
Calculating the deviation
The following formulas describe how the absolute deviation or percentage is calculated. In both cases, i
represents each of the values of the grouping period.
- Absolute Deviation: a
bs(
median of values in group) - value(i) > threshold
Percentage: abs(median of values in group) - value(i) > threshold / 100 * median of values in group
Let's use an example. Say we want to trigger an alert when the response time of a server within a balanced architecture is significantly higher (or lower) than the average. In this example, we group the events by a time period and server name, then add the aggregated value of average response time.
Gradient
The gradient method triggers an alert every time the aggregated value of a grouped element varies significantly from one grouping period/set to the next.
To create a query that can use the gradient trigger method, apply filters to the data and create new columns as needed. But you must group table events by at least two elements (usually by time, then by other table fields) and add just one aggregated value.
You can express the threshold for this kind of alert by either the absolute deviation or a percentage. So each time that the aggregated value of a grouped element varies significantly from one grouping period to the next, an alert will be triggered.
Calculating the gradient
The following formulas describe how the absolute deviation or percentage is calculated.
- Absolute Deviation:
abs(current value - previous value) > threshold
- Percentage:
abs(current value - previous value) > threshold / 100 * previous value
Let's use an example. Say we want to be alerted when the average response time of any server is significantly longer or shorter than in the previous grouped period. As is the previous example, we group the query data by a time period and server name, then add the aggregated value of average response time.