title: "How It Works" date: "2024-08-07" description: "Notification Center is your home base for all outbound alert notifications sent from Coralogix to a third-party destination such as Slack or PagerDuty." search: exclude: true noindex: true

How It Works

Overview

Outbound notifications are sent to a connector (e.g., “slack-workspace-1”, slack-workspace-2”) within a certain connector type or third-party destination (e.g., Slack, Pa gerDuty) based on two schemas: connector configuration and message configuration. The connector configuration is needed to configure how to connect to the relevant connector type, while the message configuration is needed to send a message to the connector.

The message configuration consists of two layers:

A general layer for the chosen entity type, the general data serving as the source of the notification (e.g., alerts);
A layer specific to the entity subtype, consisting of three elements: an alert type, a condition, and a triggered or resolved status (e.g., metricThresholdMoreThanTriggered).

Integration definitions use the entity type and subtype to configure templates for different types of outbound notifications.

User flow

A user sets up a metricThresholdMoreThanTriggered alert definition to notify their team when the remaining CPU for your prod subsystem is less than a particular threshold.
When the conditions for the alert definition are met, an instance of the alert definition is fired, triggering an alert. Notification Center sends a notification request to trigger an external integration to a connector within a connector type; in this case, the#RnD-internal workspace within Slack. The notification request comprises of data relevant to the entity type ALERTS and entity subtypemetricThresholdMoreThanTriggered.
Based on connector configuration and message configuration created by the user, Notification Center sends the contextualized notification to the target within Slack.