# Trigger Configuration
This guide explains the Trigger configuration module in the Infraon Infinity suit. Triggers are rules or configurations that trigger an alert or an event within Infraon. Infraon allows adding conditions to raise alerts or events when the specified rule is met.
There are two types of trigger configurations within Infraon. They are:
* Alerts - Alerts are based on configured thresholds (refer to Threshold module for details)
* Correlation - Infraon correlates events based on multiple conditions to trigger an action.
This functionality is crucial for automating ticket creation and sending alert notifications to users via email or SMS in response to system alarms, ensuring that users are promptly informed about any issues.
## **Navigating Trigger Configuration**
**Step 1:** To initiate trigger configuration in Infraon, access the Infraon Configuration from the left panel. From the main menu, select the **Notifications** option and locate **Trigger Configuration** within the menu.
After entering the Trigger Configuration section, a list of previously configured triggers will be displayed.
**Step 2:** Click on the **'Add Trigger'** button at the top-right corner of the page. Choose 'Event Trigger' from the dropdown menu to set up a new event-based trigger.
Follow the steps below to add the required details in the **'Add Trigger Configuration'** section.
## **Configuring Trigger Details**
**Step 3:** Assign a name to your trigger configuration. Next, set the trigger's status, choosing between 'Active' and **'Inactive.'**
{% hint style="info" %}
**Note:** Trigger actions will only execute when the status is **Active**. If the status is set to **Inactive**, no actions will be triggered.
{% endhint %}
**Step 4:** You have two main options:
* **'Alert Raises’**: The trigger activates when event data meets the specified criteria.
* **'Notify After Correlation'**: The system waits for a correlation process to complete before activating the trigger.
After making your selection, click **Next** to proceed.
## **Adding Conditions**
**Step 5:** Define specific filters to determine which events should activate the trigger.\
Additionally, you can apply a **Business Hours Profile** from the available system options.
For instance, selecting a **24/7 profile** ensures that alarms generated during these hours automatically trigger notifications or ticket creation.
{% hint style="info" %}
**Note:** You can assign a business service by configuring specific business hours. (To know more, [click here](/infraon-help/infinity-user-guide/infraon-configuration/general-settings/business-hours.md))
{% endhint %}
**Step 6:** Optionally, you can configure notifications to trigger only when the **Parent Node** is operational using a toggle button.
For example, if the parent node is active but child nodes are down, alarms will still be triggered for the non-operational links. Activating this option means alarms are only generated for the parent node if both parent and child nodes are down.
**Step 7:** Users can delay the trigger action by setting a specific time delay in seconds.
The delay option allows for a range between 300 and 3600 seconds. Toggling the option off when necessary disable the delay.
**Step 8:** To refine the trigger criteria, multiple filter conditions can be added. By default, the severity filter is set to **Critical**, but you can include additional conditions for **Major** and **Minor** severities.
To add more conditions, select **'Add Condition'** and choose **'AND'** to apply them cumulatively. Filters include **Alarm Message**, **Asset ID**, **Hostname**, **IP Address**, **Device Type**, and more, ensuring that the conditions match your requirements.
**Step 9:** Click Next to proceed to the action details after defining your conditions.
## **Defining Trigger Actions**
The action page has two main options: **Notify** or **Create a Ticket**.
### **Notify**
The system supports multiple notification protocols, including SMTP (email), SMS gateway integration, and REST API endpoints. The notification delivery mechanism is executed based on the selected protocol configuration.
Let’s see each one in detail:
#### **Notify via Email**
* **Step 1:** Select the recipient email address from a dropdown or enter it manually. Optionally, you can add a **CC** and define the email subject.
* **Step 2:** The email body supports dynamic content injection through macro implementation using double curly braces (**{{**). The system provides predefined macro variables, including network parameters (IP\_ADDRESS, HOSTNAME) for customized alert messaging.
#### **Notify via SMS**
* **Step 1:** Create a custom SMS message describing the trigger action.
* **Step 2:** Specify the recipient's phone number from the dropdown box.
#### **Notify via API**
* **Step 1:** Select the appropriate API from the list of registered APIs.
* **Step 2:** Choose the **GET** or **POST** method and enter the endpoint respected URL.
* **Step 3:** Select the content type (e.g., **application/JSON**) and provide the required data in the corresponding fields.
Once the notification channel configurations are completed for the selected protocol (email, SMS, or API), the system executes a validation sequence and confirms successful trigger deployment.
### **Create a Ticket**
Several toggles are available during ticket creation, such as **'Impact Service,' 'Resolve if Cleared,' and 'Reopen if Necessary.'** Let’s break down these options:
* **Impact Service:** If this toggle is enabled, users are prompted to choose a service impacted by the event for ticket creation. The available services will be displayed in a dropdown menu. Once a service is selected, the created ticket will be automatically linked. This optional step allows users to associate a service or leave the feature disabled.
* **Resolve if Cleared:** Enabling this option allows the system to resolve the ticket automatically when the event has been cleared. This feature is optional and should be selected if users wish the ticket to close upon resolution of the alarm.
* **Reopen on Re-alarm:** Activating this toggle ensures the system reopens the ticket if a re-alarm or event recurrence occurs. Initially, the ticket moves from an open to a resolved state, but with this option enabled, the ticket status will change to 'in progress' upon re-alarm.
## **Submitting the Configuration**
After adjusting the necessary settings, click the **Submit** button.
A confirmation message will appear, indicating that the trigger has been successfully created and is visible in the trigger list.
You can configure multiple triggers for scenarios requiring multiple actions (e.g., notifying users and creating tickets for the same event).
## **Miscellaneous**
Once configured, triggers will activate based on the predefined thresholds. You can monitor triggered events in the events module, where details like event ID and ticket ID are displayed.
Tickets can be accessed through the ticket module, and corresponding notifications are sent to designated recipients, providing full traceability of the trigger configuration process.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.infraon.io/infraon-help/explore-more/use-cases/ticket-management/ticket-creation/trigger-configuration.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.