Skip to main content

Managed Notifications

Causely allows you to configure managed notifications directly in the UI, so teams can control what gets routed, where, and under which conditions, without managing configuration files or infrastructure.

Managed notifications are the recommended approach for most teams. They let you route causal insights based on impact, severity, and context.

Create a Notification Configuration​

  1. Navigate to Settings → Notifications.
  2. Click Create to add a new notification configuration.
  3. Enter a name that describes the purpose of the notification (for example, prod-critical-alerts).

The name is used only for identification within Causely and does not affect delivery. Each notification configuration must have a unique name.

Select a Notification Type​

Choose where you want to receive notifications. Supported destinations include:

  • Slack
  • Microsoft Teams
  • Prometheus Alertmanager
  • incident.io
  • Splunk On-Call (VictorOps)

The selected type determines both delivery format and required fields in the next step.

Configure Destination-Specific Fields​

Depending on the notification type, you may be asked to provide additional details, such as:

  • Endpoint URL (for webhooks or alert managers)
  • Authentication token (optional, depending on destination)

These fields control how Causely delivers notifications to the selected system.

Choose a Processing Cluster​

Select a cluster to handle notification processing.

Notifications are processed by the Causely Mediator running in the selected cluster.

Filters allow you to control which causal insights trigger notifications. You can filter by:

  • Severity: Urgent vs. Non-urgent
  • Cluster
  • Namespace
  • Root Cause: for example Code Change Regression: CPU Congestion or Database Malfunction
  • Entity type: for example Service, HTTP Path or Node

Filters help reduce noise and ensure notifications are routed only when they matter to the receiving team.

Save and Manage Notifications​

Once saved, the notification configuration appears in the Notifications list, where you can:

  • View active filters
  • Edit configuration details
  • Disable or delete notifications as needed

Changes take effect immediately and do not require redeploying agents or updating configuration files.

Test the Notification​

After saving, you can send a test notification to verify the configuration.

  • Optionally apply test-only filters to simulate specific scenarios.
  • Review the exact payload that will be sent to the destination.
  • Confirm the notification is received and formatted as expected.

Testing helps validate both routing logic and downstream integrations.

When to Use UI-Based Notifications​

Managed notifications are best suited for teams that want:

  • Centralized, product-managed routing
  • Explainable notification logic
  • Easy iteration as systems and ownership change

For programmatic or infrastructure-managed setups, notifications can also be configured through the Causely Mediator.