Overview

Organizations often start with simple, in-alert notification configuration, quick to set up when you don’t need systematic routing or reusable templates.

As alerting needs grow, patterns emerge: systematic routing logic, shared destinations, and consistent message formats. Managing these manually across hundreds or thousands of alerts creates overhead, inconsistency, and configuration drift.

Notification Center streamlines this by centralizing notification management. It separates entity definitions, such as alerts or cases, from delivery logic, so you can manage routing, templates, and destinations in one place, giving you a flexible and scalable notification workflow that grows with your organization.

Basic flow

For teams that do not need message customization:

• Use system-generated message templates (presets) automatically created for each alert.
• Notifications use standard formatting and required fields.

Advanced flow

For teams that want to customize notification messages:

• Create custom presets with reusable templates.
• Define override templates for specific entity subtypes (for example, metric threshold alerts, logs threshold alerts, or Case lifecycle events).
• Customize structure, variables, and logic to match operational needs.

flowchart TB
    Entity["Entity (Alerts / Cases)<br/><br/>Routing labels<br/>&nbsp;&nbsp;- team<br/>&nbsp;&nbsp;- environment<br/>&nbsp;&nbsp;- service"]

    NC["Notification Center engine"]

    Routers["Routers<br/>matched based on routing labels<br/>(Team, Environment, Service)"]

    Rules["Routing rules<br/>Conditions for routing notifications<br/>to different destinations"]

    Connectors["Connectors<br/>Where to send the notification"]

    Presets["Presets<br/>How the notification messages should look"]

    Outbound["Outbound notification packet"]

    Entity -->|notification request| NC
    NC --> Routers
    Routers --> Rules
    Rules --> Connectors
    Rules --> Presets
    Connectors --> Outbound
    Presets --> Outbound

    %% CLICKABLE LINKS
    click Entity "https://coralogix.com/docs/user-guides/notification-center/entity-types/introduction/" "Learn about Entity types"
    click Routers "https://coralogix.com/docs/user-guides/notification-center/routing/introduction/" "Learn about Routing"
    click Rules "https://coralogix.com/docs/user-guides/notification-center/routing/define-routing-rule/" "Learn about Routing Rules"
    click Connectors "https://coralogix.com/docs/user-guides/notification-center/connectors/" "Learn about Connectors"
    click Presets "https://coralogix.com/docs/user-guides/notification-center/presets/introduction/" "Learn about Presets"

This flow shows how Notification Center determines the correct message format and routing path.

How Notification Center processes and delivers notifications

When an alert event or case triggers, Notification Center automatically:

1. Receives the notification request.
2. Evaluates routing logic to match the connector and preset.
3. Applies the relevant template: system, general, or override.
4. Renders dynamic values and sends the message to the destination.

How it works

Notification Center operates through four core components:

Component	Description
Entity	The Coralogix component that generates notifications (for example, an alert or case).
Router	Uses labels and rules to determine which connectors and presets a notification should use.
Connector	The configured link between Coralogix and a third-party service (for example, Slack or PagerDuty).
Preset	The message template defining what information is included and how it is formatted.

When an entity triggers a notification, Notification Center evaluates routing labels, selects the correct router, evaluates routing rules, and sends the message using the configured connector and preset.

Benefits

• System presets are ready to use for both alerts and Cases, enabling faster setup.
• Create detailed message templates and logic when needed.
• One routing engine controls how notifications reach all destinations.
• Update one preset or router and apply changes across all alerts and Cases.
• Route both alert notifications and Case lifecycle events through the same routers, with separate rule sets for each entity type.

Next steps