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.
Ready to get started?
Set up your first notification flow in the Quick start.
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.
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.
How Notification Center processes and delivers notifications
When an alert event or case triggers, Notification Center automatically:
- Receives the notification request.
- Evaluates routing logic to match the connector and preset.
- Applies the relevant template: system, general, or override.
- 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.
How a notification flows through the system
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
Set up your first notification flow in the Quick start.