Notification Center
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.
Set up your first notification flow in the Quick start.
- Basic flow
- Advanced 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.
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.
To review each delivery attempt and whether it succeeded or failed, see Notification Deliveries (Early Access).
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
Two ways to send a notification: webhooks and routers
Coralogix offers two delivery paths, and they work differently.
An outbound webhook is a single destination you attach to an alert. It holds a URL and its own settings, you select it on the alert, and it sends what that webhook type sends. One webhook, one destination, configured per alert.
A router is the routing engine described above. It does not hold a destination. It holds rules, and each rule decides which connector and which preset a notification uses. One router can serve hundreds of alerts, and changing a rule changes all of them at once.
| Outbound webhook | Router | |
|---|---|---|
| What it is | A destination | A set of rules that select a destination |
| Where you configure it | On each alert | Once, then reused |
| Message format | Fixed by the webhook type | Set by the preset, which you can customize |
| Changing it | Edit every alert that uses it | Edit the router |
Both are supported. An outbound webhook is the simpler choice when one alert needs to reach one place and the standard message suits you. A router is worth the setup once you have many alerts, several destinations, or a message you want to shape.
Customizing a message requires Notification Center
An outbound webhook sends the format its type defines, and that format has no template behind it. A Slack message delivered through a Slack outbound webhook arrives as the webhook builds it, so it cannot be restyled, reworded, or given extra fields.
To change what a message says, route the alert through Notification Center instead. There the preset is the template, and you can edit it. The webhook itself has no equivalent setting, so this is a change of delivery path rather than a configuration option.
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.