Copy as Markdown[Open in ChatGPT](https://chatgpt.com/?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fuser-guides%2Fnotification-center%2Fpresets%2Fsetup-for-alerts.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)[Open in Claude](https://claude.ai/new?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fuser-guides%2Fnotification-center%2Fpresets%2Fsetup-for-alerts.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)

# Alerts use case: structured output type

Set up presets for Notification Center using alerts as the entity type.

## Preset setup[​](#preset-setup "Direct link to Preset setup")

### Step 1: Get started[​](#step-1-get-started "Direct link to Step 1: Get started")

* Select **Integrations**, then **Notification Center**, then **Presets**, then **+ New alert preset**. Select the destination type as the basis for your notification.

The [schema](https://coralogix.com/docs/docs/user-guides/notification-center/destination-types/slack/schema-structure/.md) presented in the preset is determined by destination type, entity type, and output type. In the example below, the user chooses the system preset for alert notifications sent to Slack. The output type is basic, consisting of Title, Description, and Footer.

### Step 2: Configure the general preset layer[​](#step-2-configure-the-general-preset-layer "Direct link to Step 2: Configure the general preset layer")

The general configuration layers for the selected destination type are displayed. Keep them as-is or [customize](https://coralogix.com/docs/docs/user-guides/notification-center/dynamic-templating/.md) any fields to fit your needs. Add or remove functions and insert free text in any templates as desired.

### Step 3: Configure the override preset layer[​](#step-3-configure-the-override-preset-layer "Direct link to Step 3: Configure the override preset layer")

Configure the preset layer by first selecting an option from the left-hand panel. Select **+ Add override template** to select the desired subtype.

[![Subtypes available for preset override selection](/docs/assets/images/NC-preset-subtype-ce8a3842347ff13abec776978ae4aba2.webp)](https://coralogix.com/docs/docs/assets/images/NC-preset-subtype-ce8a3842347ff13abec776978ae4aba2.webp)

As with the general layer, keep the default configuration or [customize](https://coralogix.com/docs/docs/user-guides/notification-center/dynamic-templating/.md) it to suit your needs.

In the example below, the user configures the override layer for the following alert source subtype: **Metrics Threshold Alert / Status: Triggered**.

[![Metric subtype override configuration](/docs/assets/images/NC-metric-subtype-8f396ab34eafeb8654443f9f2c2f5367.webp)](https://coralogix.com/docs/docs/assets/images/NC-metric-subtype-8f396ab34eafeb8654443f9f2c2f5367.webp)

Note

When a template is customized in either the general or override layers of a custom preset, it becomes independent of the system preset.

Implications for the use case above:

* **Title** has been customized. Future system updates to this field will not be inherited.
* **Description** has been customized. Future system updates to this field will not be inherited.
* **Footer** continues to inherit from the system preset. If Coralogix updates the **Footer** template in the system preset, the change automatically applies to this custom preset.

For details on customizing your schema and examples, see [Dynamic templating](https://coralogix.com/docs/docs/user-guides/notification-center/dynamic-templating/.md).

### Step 4: Define triggered and resolved configurations[​](#step-4-define-triggered-and-resolved-configurations "Direct link to Step 4: Define triggered and resolved configurations")

For alerts, define message configuration versions for triggered and resolved notifications in the specific entity subtype. While both structures are similar, the templates differ slightly. Navigate between the **Triggered** and **Resolved** tabs to view and modify the respective configurations as necessary. Keep in mind that customizations made to one version do not automatically carry over to the other version.

### Step 5: Validate and save the preset[​](#step-5-validate-and-save-the-preset "Direct link to Step 5: Validate and save the preset")

Select a connector and select **Send test notification** (optional). This sends a notification with hard-coded example values to the selected channel. Once saved, the new preset appears in the **Presets** tab.

## Final notification output[​](#final-notification-output "Direct link to Final notification output")

When an alert triggers, the final notification is sent based on the preset configuration, with more specific, custom configurations taking precedence over more general, system configurations.

## Next steps[​](#next-steps "Direct link to Next steps")

[Alerts preset structure](https://coralogix.com/docs/docs/user-guides/notification-center/presets/alerts-preset-structure/.md)[Raw output setup](https://coralogix.com/docs/docs/user-guides/notification-center/presets/setup-for-alerts-raw-output/.md)[Dynamic templating](https://coralogix.com/docs/docs/user-guides/notification-center/dynamic-templating/.md)