Notification Center
Native Microsoft Teams connector
Route Coralogix alert and Case notifications to Microsoft Teams through a native connector, the replacement for the retired Office 365 incoming webhooks. A Teams administrator installs the Coralogix app in your tenant, then you pick a channel by link or by ID. Case lifecycle changes (assign, acknowledge, resolve, and close) reflect in the Teams message and on the Case timeline in near real time, with an option to keep updates in a single thread. Learn more
Dynamic field builder for connectors
Build dynamic connector routing without writing Tera. A builder mode on dynamic fields (Channel, Email addresses, Service key) lets you set conditions on alert or case priority, name, and labels, then route to the matching channel, recipients, or service. Conditions combine with AND within a row and OR across rows, with the first match applied, and a required fallback value covers anything that does not match. Define the routing once and reuse one connector across many routers, instead of creating a connector per team or channel. Learn more
Service Catalog integration for ownership labels
Set ownership labels by choosing a service from the APM Service Catalog instead of typing it as free text. Ownership labels decide which team is notified and which service an alert or Case belongs to, so picking a real catalog service (tagged Catalog) ties alerts and Cases to the correct APM entity and routes them to the right team. This avoids the typos and near-duplicate names that can leave a notification linked to the wrong service, or to none. Free text still works (tagged Custom) for services not yet in the catalog. Learn more
Cases entity type and condition templating
Cases as a notification entity type — Notification Center now supports Cases alongside Alerts as an entity type. Create routing rules that trigger on Case lifecycle events, use Ownership Tags for Case routing, and define Case-specific conditions and destinations. Learn more
Condition templating for routing rules — Write advanced routing rule conditions using Tera templates. Includes support for alert name matching, label checks, regex patterns, case status and severity conditions, and entity-type routing. Learn more
ServiceNow destination type — ServiceNow is now available as a Notification Center destination, enabling incident creation and management directly from Coralogix notifications. Learn more
JSM (Jira Service Management) configuration via HTTPS — Configure Jira Service Management as a notification destination alongside OpsGenie. Includes JSM connector setup, Atlassian API endpoints, message presets, and a migration guide reflecting OpsGenie deprecation. Learn more
notification.deliveries dataset update — The notification.deliveries dataset is now enabled by default at no cost. Alerts record delivery failures only, while Cases record both successful and failed deliveries.