Introduction
Overview
A preset is a collection of templated fields that define a message configuration containing 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 entity type (e.g., Alerts).
Presets act as blueprints, structuring entity requests into formats compatible with specific connectors. Using a predefined schema, Notification Center converts an entity, 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 entity types and subtypes, presets streamline notification setup, reducing configuration overhead while allowing flexible, granular customization.
System presets
For each destination type, Coralogix provides a System preset, offering structured, out-of-the-box message configurations. These presets vary in schema structure and content depending on the entity 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.
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 entity type.
The Override layer applies to an entity subtype.
For example, if Alerts are selected as the entity 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 System preset acting as the parent. 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 Custom templates.