Log alerts are alert conditions based on log events and log pipelines. Typically log pipelines are applied to resources or resource groups, and the associated log alert conditions set the alert criteria, for example matching text in the log message.
Log alert conditions use regular expression patterns to match ingested logs and trigger LogicMonitor alerts to send you notifications when these log events or anomalies occur.
With log alerts, you can speed up your investigation by adding alert conditions to track the logs you always want to know about or creating alerts on a detected anomaly.
Viewing Alert Conditions
On the Logs page, select the Pipeline Alerts icon to open the Alert Conditions page where you can review and manage alert conditions.
- Severity—Displays the level (Critical, Error, Warning) configured for the alert condition.
- Display As—Shows the configured display name of the alert condition.
- Logs query—Displays the regular expression pattern to match log events that will trigger the alert.
- Pipeline—Displays the pipeline that the alert condition applies to.
- Description—Provides a short explanation of the alert condition.
- Active—Lets you toggle the alert condition on and off.
- Filter alert conditions associated with a specific pipeline.
Adding Alert Conditions
You can add alert conditions directly from any log event or anomaly listed in the Logs page, or from the Pipelines and Pipeline Alerts pages.
- From a log event or anomaly on the Logs page: Open the action menu at the beginning of the log line and select “Create alert condition” to open the Add Alert Condition dialog.
- From the Pipelines page: Select the Alert Conditions icon or count to open the Alert Conditions page, and select the plus sign to add an alert condition.
Note: You need at least one pipeline to be able to add a log alert condition. For more information, see Log Processing Pipelines. Log queries for alert conditions cannot include aggregate functions.
In the Add Alert Condition dialog, enter information as follows:
- Select the type of Alert severity level (Critical, Error, Warning) to generate when conditions are met.
- Enter a Display name and a Description to be displayed in the list of alert conditions.
- Select a Pipeline to apply the alert condition (unless prefilled).
- Unless prefilled, enter a Logs query to filter the events in the pipeline. For more information see Writing a Filtering Query. Select the arrow to preview the results and refine your query before you save.
- Toggle Trigger alert to on to activate the alert condition.
- For Clear after, enter the time that the alert will persist. Default is 60 minutes.
- Toggle Auto-clear after acknowledge to on if you want the alert to be cleared after it is acknowledged.
- Select the Save icon to add the alert condition.
Note: The Clear-after setting will clear alerts after the specified time, even if the Auto-clear after acknowledge toggle is off. Alerts will only be acknowledged if the Auto-clear after acknowledge toggle is on.
When you return to the Alert Conditions page, you can review the alert you created in the table.
Windows Servers (_resource.group.name="Windows") targets a subset of logs related to a “Windows” resource group. The alert triggers on specific keywords or values (eventcode 1100 and application log files). You do not need to include the resource group name in the query for the alert condition (however it would work).
When log alerts conditions are matched, they trigger standard LogicMonitor alert notifications based on the alert settings (Critical, Warning, Error) and will route through the configured escalation chain.
You can also:
- View the log alert in the Logs graph, where it will display as a line alongside the alerting log event.
- Acknowledge or clear the alert in the Alerts list.
Each pipeline can have no more than 15 alerts per minute. If the rate of alerts exceed this limit, they will be discarded and not processed.