Welcome to Notification Center

Note

This feature is available in Beta. We’re continuing to improve it, so features and functionality may change over time.

Overview

Notification Center is your centralized hub for managing outbound notifications sent from Coralogix to third-party vendors like Slack or PagerDuty. It consolidates notifications across the Coralogix platform into a single interface, giving you full control over setup, management, and auditing.

With the label-based routing approach, Notification Center enables scalable and flexible notification management across large organizations.

This model decouples alert definitions from routing configurations, alerts only need to include the appropriate routing labels, and Notification Center automatically applies the correct routing rules. This simplifies configuration, improves maintainability, and makes notification management easier to scale.

Notification Center allows you to send notifications to one or more connectors, whether within the same destination type (e.g., slack-workspace-1 and slack-workspace-2) or across destination types (e.g., Slack and PagerDuty).

When a entity, such as an alert, triggers a notification, the system sends a message to your chosen connector based on connector and preset configurations. Connectors link notifications to specific destinations, while presets define the content of the messages based on the entity.

Centralize outbound integration management

Create notifications separately per notification source and consolidate them across the Coralogix platform in one UI. Store notifications for auditing and troubleshooting purposes.

Create rich notifications to send to destination types

Users can format notifications to include specific information for a notification source (e.g., Alerts) to send to third-party vendors known as destination types, such as Slack and PagerDuty.

Format notifications using schema-driven templates

As a basis for notifications, Coralogix provides fully typed schemas per entity, such as Alerts or Cases. Fully typed schemas let users extract data from an event using a variable path in the templates, so this data is included in the notifications. Users may either use the preconfigured notification templates known as presets as-is or customize them.

Route notifications intelligently

Use label-based routers to automatically send alerts to the right team or environment.

Instead of managing all routing logic in one global configuration, you can use routing labels such as group, environment, or service to direct notifications to dedicated routers.

This approach keeps alerting organized, scalable, and aligned with how your teams work. For details on how routers match alerts and evaluate routing rules, see Routing

Enjoy data-driven routing

Route notifications to different teams within the same destination type or across different destination types by defining conditions in the connector. For example, you can configure different metric alerts to be sent to specific R&D teams based on the triggered application.