Introduction

Overview

A preset is a collection of templated fields that define a message configuration that contains the data required to build the proper notification for the third-party vendor. Users configure presets for each destination type (e.g., Slack, PagerDuty) and notification source type (e.g., alerts).

Presets act as blueprints, structuring notification source requests into formats compatible with specific connectors. Using a predefined schema, Notification Center converts a notification source, such as a triggered alert, into a notification that the connector can process. Predefined schemas per destination type can be found here:

By enabling reusable templates across notification source types or subtypes, presets streamline notification setup, reducing configuration overhead while allowing flexible, granular customization.

System presets

For each destination type, Coralogix provides one or more predefined system presets, offering structured, out-of-the-box message configurations. These presets vary in schema structure and content depending on the notification source and destination type.

System presets are maintained by Coralogix and cannot be modified. Users may view and use them as the foundation for custom presets. Each system preset acts as a parent present to a custom preset, allowing it to inherit its configuration.

Basic

The Basic system preset is the default option, providing a concise, informative schema.

Detailed

The Detailed system preset includes comprehensive alert descriptions with multiple variables from the alert schema.

Empty

The Empty system preset contains schema fields without predefined content. Users must manually configure the desired schema fields for their notifications.

Custom presets

When a user creates a preset, it inherits a system preset and becomes a custom preset, acting as a child preset. By default, a custom preset mirrors the selected system preset, with each field inheriting its template content.

Users can retain the inherited templates or apply overrides to modify specific fields. Once a field is overridden with a new template, it is detached from the system preset. This overridden field will no longer inherit further updates to this field made in the system preset.

Preset configuration layers

Overview

All presets consist of a two-layer configuration:

The General layer applies to an entire notification source type.
The Override layer applies to a notification source subtype.

For example, if alerts are selected as the notification source type, the General layer applies to all alerts, while the Override layer applies to specific alert subtypes. This two-layer configuration applies to both system and custom presets.

For each Custom preset, the General and Override layers inherit their content from the corresponding General and Override layers in the parent system preset. This allows for template reuse, reducing duplication while offering precise customization where needed.

Once a user customizes a field in a custom preset, it is disconnected from the corresponding field in the system preset. Future updates to the system preset will not affect customized templates.

Triggered & resolved presets

When the notification source type is alerts, each preset has distinct configurations for triggered and resolved notifications. While both structures are similar, the templates differ slightly. Users may view and modify the respective configurations as necessary.

Final notification output

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

Setup and Management

Next Custom Preset Setup: Alerts Use-Case