Create and Manage Log Alerts | Qntrl Log Monitoring | Qntrl Online Help |Configure Log Alerts and Notifications

Configure and Manage Alerts

Create and Manage Alerts

Alerts help you monitor log activity and receive notifications when specific conditions are met.
An alert runs a configured log query at a defined interval and triggers a notification when the query results satisfy the configured threshold.

For example, you can create an alert to monitor failed webhook executions, unsuccessful CodeX executions, or unusual API activity.

Create an Alert    

You can create an alert from any of the following locations:
  • Settings > Log Monitoring > Alerts

  • Log Monitoring > System Logs > Create Alert

  • The Log Details window by clicking Create Alert

  • The Trace Tree page by clicking Create Alert

When you create an alert from the Log Details window or the Trace Tree, the Alert Configuration page opens with the relevant query details pre-populated, allowing you to quickly configure notifications for the selected log activity.
Alerts created from the Logs page are automatically listed in the Alerts page.

To create an alert:

  1. Log in to Qntrl.
  2. Navigate to(settings) >> Log Monitoring >> Alert.
  3. Click New Alert.


Configure Alert

Alert Name  : Enter a unique name for the alert.
Query  : Configure the query that should be monitored.
  • Query creation is similar to building a query in the Logs and Monitoring page. For detailed instructions, refer to Log Monitoring.
  • If the alert is created from the Logs page, the selected query is automatically populated.
Search: Use Search to open the Logs page and:
  • Build a query
  • Modify an existing query
  • Execute a query and verify results 
After validating the query, close the Logs page using the Close button in the top-right corner to return to the Alert configuration window. 
Log Window  : Defines the time range of logs that should be evaluated during each alert execution.
Example: If the Log Window is set to Last 7 Days, the alert evaluates logs generated during the previous seven days.
Run Frequency  : Defines how often the alert should run.
Examples:
  • Every Hour
  • Every Day
  • Every Week
If the Run Frequency is set to Every Week, the alert executes once every week and evaluates logs based on the configured Log Window.
Notes

  • Log Window determines which logs are analyzed.

  • Run Frequency determines how often the alert runs.

Configure Threshold   : Define the condition that triggers an alert.
Example: Count >= 1
The alert is triggered when the query returns one or more matching log records.
Notification Channel  : Select how alert notifications should be delivered.
  • Email  : Send notifications through email.
    • Select an existing email template or create a new email template
    • Use Alert placeholders in the email subject and content to include dynamic alert information in notifications.
  • Circuit  : Send notifications through a Circuit.
    • This option allows you to integrate custom notification workflows such as:
      • Messaging applications
      • Customer notifications
      • Internal monitoring workflows
Circuit: For Circuit, select the required Circuit from the available list.
Circuit Input: When a Circuit notification channel is selected, the Alert configuration displays sample input data that can be used within the Circuit.
Alert

Ensure that the circuit schema validation accepts the provided circuit input.

The reference data includes:

  • Alert Metadata  : Contains alert configuration details such as:

    • Alert ID

    • Alert Name

    • Query

    • Log Window

    • Run Frequency

    • Configured Threshold

  • Alert Information  : Contains execution-specific details such as:

    • Start Time

    • End Time

    • Matching Log Count

This information helps process alert notifications within the Circuit.

Save: click Save.


The alert is created and displayed on the Alerts page.


Manage Alerts   

The Alerts page contains two sections:

  • Alert Details

  • Alert History


Alert Details   

Use Alert Details to review and manage configured alerts.

The following information is available:

  • Alert Name

  • Query

  • Configured Threshold

  • Notification Channel

  • Next Execution Time

  • Last Modified Time

  • Status (Active or Inactive) - Use the status toggle to enable or disable an alert. Disabled alerts do not execute or send notifications until they are re-enabled.

  

Alert History    

Use Alert History to review previously triggered alerts.

The following information is available:

  • Alert Name

  • Triggered Time

  • Configured Threshold

  • Matching Log Count

  • Log Window

Alert History helps verify whether alerts were triggered as expected and provides visibility into past alert activity.



Troubleshooting FAQ

1. Why is my alert not being triggered?   

Verify the following:

  • The alert is active.

  • The configured query returns matching logs.

  • The threshold condition is satisfied.

  • The selected notification channel is configured correctly.

  • If Circuit is selected as the notification channel, ensure that the Circuit is active and configured to handle the alert input schema (Alert Meta and Alert Info) correctly.

You can execute the query manually in Logs and Monitoring to validate the expected results.


2. What is the difference between Log Window and Run Frequency?   

  • Log Window determines which logs are analyzed.

  • Run Frequency determines how often the alert executes.

For example, an alert configured with a 7-day Log Window and a weekly Run Frequency runs once every week and evaluates logs from the previous seven days.

3. Why am I not receiving alert notifications?   

Verify that:

  • The selected notification channel is valid.

  • The email template or Circuit configuration is correct.

  • The alert has been triggered based on the configured threshold.


    • Related Articles

    • Manage Webhooks

      Webhooks Overview Webhooks facilitate automated HTTP notifications. Notifications are triggered in third-party applications as per the business requirements when a predefined action is performed by the user in the organization. Business Use Cases of ...

    • Manage Business Rules

      What is a business rule? A business rule helps you trigger an event or a chain of automated events, when a defined action occurs in a card. For example, when a card's assignee field is updated, you might want to change the card's supervisor field ...

    • Configuring Additional Components

      Early Access Circuit Templates in Qntrl Studio is not enabled for all users. If you’d like to try it out, please email our support team for early access. Webhooks Webhooks enable automated HTTP notifications that are sent to third-party applications ...

    • Manage Circuits and States

      Dashboard The Dashboard provides a centralized view to monitor and track all Circuit executions across the system. It offers a consolidated snapshot of all workflow executions and their current statuses. To access the dashboard, Navigate to Circuits ...

    • Manage Tables

      Tables help you store reference data in a tabular format within Qntrl . You can store data vital to support your business processes here. Also, the data in tables can be listed in cards using Table Lookup . For example, Zylker-- a manufacturing ...