Low alert type
The low method follows the same principle as the several method except that it triggers an alert when the threshold is not exceeded after a specified period of time.
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 when the threshold number has not been exceeded at the end of the period. 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 60 minutes and it will restart after that time.
This type of alert could be useful with heartbeat events since we want to be notified when a system is not sending its heartbeat events when expected.
What data do I need to create this alert?
To create an alert using this triggering method, you can apply filters and create new columns in your query but you cannot group events. If you grouped, this alert type will not appear for you to select in the alert definition window.
Configuring the alert
After selecting this type of alert, you have to define two variables:
- Period: specifies how frequently you want the system to check for events matching the conditions of your query. You can use preset periods or create custom periods:
Preset periods: click the dropdown and select the desired option (you can use the editable field to filter them).
Custom periods: click the dropdown, write the desired period in the editable field and then click the green field that appears below to confirm it. You have to introduce a valid format, otherwise you will get an error message. The accepted format consists of a number followed by a duration code without space between them:
Duration Format Example Days (0-n)d 1 day → 1d Hours (0-24)h 15 hours → 15h Minutes (0-59)m 45 min → 45m Seconds (0-59)s 50 seconds → 50s You can stack them to create a compound → 15h45m50s
The period will not start counting from the moment of the alert creation but from a fixed division that takes the Epoch reference date as the starting point (midnight Jan 1, 1970). This means that if you created an alert past the hour with a one-hour period, the first time it will be triggered (if the conditions are met) will be when the clock strikes the hour and not after 60 minutes. In other words, if you created it at 9:37, it will be triggered at 10 and not at 10:37.
The period will be adjusted according to the timezone specified in the delivery method assigned to the alert. To know more about this check the Manage delivery methods article.
- Threshold: specifies how many events you want to use as a limit to trigger the alert. Write the desired number.
If you set the threshold to 0 you can generate a special type of alert, the inactivity alert. You can find more information in the following link.
Using column values in the Summary and Description
The $columnName command used to display column values in the Summary and Description fields can be employed with the columns and properties below. Using a different one will not activate the command and will be interpreted as plain text.
|$eventdate||You can use this column to display the moment in time at which the events that triggered the alert were received.|
|$count||Even though it is not a column, it can be used to display the number of events collected during the period.|
demo.ecommerce.data table, imagine that you want to receive an alert when you receive less than 5 events per hour from a specific client Ip address where the bytes transferred exceed 3000.
First of all, you need to filter your query data using the Greater than (gt, >) and Equal (eq, =) operations. Then you need to open the alert definition window, select the low type alert and fill in all the details (pay special attention to the specific settings of this alert type).
To save time, you can copy the following query to reproduce the aforementioned example from the
demo.ecommerce.data sample table and create a low type alert.
from demo.ecommerce.data where clientIpAddress = 220.127.116.11, bytesTransferred > 3000