43 docs tagged with "notifications"

Configure routing labels on alerts so Notification Center can route notifications through routers.

Alerts act as a supported entity type for Notification Center.

Learn how Notification Center structures notifications using entities, routers, connectors, presets, and destinations.

Define and manage presets that control message content and formatting for Notification Center destinations.

Cases act as a supported entity type for Notification Center.

This guide presents the connector configuration for the Email destination type.

This guide presents the connector configuration for the generic HTTPS destination type.

This guide presents the connector configuration for the PagerDuty destination type, including the service-key and bi-directional paths.

This guide presents the connector configuration for the Slack destination type.

Create and manage connectors in Notification Center to send notifications to Slack, PagerDuty, and HTTPS endpoints.

Learn how system and custom presets are created and customized in Notification Center.

Learn how to create routers in Notification Center to match notifications and route them to specific destinations.

Define routing rules in Notification Center to control when notifications are sent and where they go.

Learn how destination types define where notifications are sent and how messages are formatted in Notification Center.

Use Tera expressions to customize notification messages, routing, and connector behavior in Notification Center.

Attach query results to a Case notification, so responders get the context they need without leaving Slack, Microsoft Teams, or email.

Learn how Notification Center merges preset layers and renders final notification messages.

Learn how Notification Center routes notifications using labels, rules, and destinations.

Notification Center supports the HTTPS destination type.

This guide presents the connector and message configuration for incident.io via the generic HTTPS destination type.

Install the Coralogix app in your Microsoft Teams tenant, set up the integration, and create a connector for Notification Center.

This guide describes how to configure the subject and content of Email notifications using presets.

This guide presents the schema structure for the generic HTTPS destination type.

This guide presents the schema structure for the PagerDuty destination type.

This guide presents the schema structure for the Slack destination type.

Route Coralogix alert and Case notifications to Microsoft Teams channels with the native Notification Center connector.

Move legacy alert webhooks to the Notification Center model of connectors, presets, and Case-based routing. Applies to every connector type, with Slack and Microsoft Teams examples.

Configure the generic HTTPS destination type to send alert notifications to OpsGenie or its Atlassian successor, Jira Service Management (JSM), from Coralogix Notification Center.

Notification Center is your home base for all outbound alert notifications sent from Coralogix to third-party destinations such as Slack or PagerDuty.

Notification Center supports the PagerDuty destination type, with one-way service-key and two-way bi-directional connector paths.

These permissions are required for engaging with Notification Center.

Route P1 alerts to PagerDuty using Notification Center connectors, presets, and routing rules.

Route alert notifications to Slack using Notification Center connectors, presets, routers, and routing rules.

Use Notification Center to route alert notifications from Coralogix to destinations such as Slack or PagerDuty.

Integrate Coralogix with ServiceNow to automatically create, update, and synchronize ServiceNow records from Coralogix Cases via Notification Center.

Notification Center supports the Slack destination type.

Route Slack, email, and PagerDuty connectors dynamically using the field builder or Tera templating in Notification Center.

Quick reference for Tera expressions used in Notification Center for connectors, presets, and routing rules.

Troubleshoot and optimize Tera templates for Notification Center connectors, presets, and routing rules.

Map each legacy outbound-webhook placeholder to its Notification Center Case-notification equivalent when rebuilding a custom webhook body as a Tera preset.

Decide which notifications reach which destination, and express those decisions as a small set of routers instead of one router per team per environment.

Learn how Notification Center uses entity types and subtypes for alerts and cases.

Use Tera template expressions in routing rule conditions to control which notifications are routed to which destinations based on alert names, labels, case status, and entity type.