Skip to main content

Push Causal Insights Into Your Workflow

Causely doesn’t just emit alerts, it delivers explainable, causal insight to the right people, in the right context, at the right time.

Rather than forwarding raw metrics, logs, and traces, Causely acts as a reasoning layer between telemetry and action. It continuously models cause and effect across your system to determine what matters, why it matters, and who should care, so teams can move from noise to understanding, and from understanding to action.

Causely supports multiple ways of delivering this insight, depending on how tightly you want understanding and action to be coupled.

Native Integrations​

Understand what changed and why, where engineers already work

Native integrations bring Causely’s causal explanations, including the Diagnosis, blast radius, and service impact, directly into the tools engineers use every day.

This path is optimized for human understanding and collaboration. Engineers can quickly see not just that something is wrong, but what caused it, how it propagates, and what it affects, without switching context or interpreting raw telemetry.

Use this approach when the primary goal is shared situational awareness, faster diagnosis, and better coordination during investigation and response.

Available native integrations:

Configuring Notifications​

There are two ways to configure where Causely sends notifications, and they offer the same functionality. Which one you use is simply a matter of preference for where you'd like to set things up:

  • In the UI: point-and-click configuration in the Causely product.
  • Via a Kubernetes secret: configuration as code, applied through the Mediator.

The two stay in sync automatically:

  • When you configure a notification in the UI, the backing Kubernetes secret is created for you automatically.
  • When you create a secret for notifications, it appears as a configured notification in the UI.

Pick whichever fits your workflow, both deliver the same notifications to the same destinations.

Managed Notifications (UI-Configured)​

Configure notifications directly in the Causely UI

Use the Causely UI to choose where notifications are delivered and add filters that control when they're sent, without editing configuration files. When you save a configuration, Causely creates the corresponding Kubernetes secret for you automatically.

Learn more: Managed notifications overview

Mediator-Based Notifications​

Configure notifications with a Kubernetes secret

Prefer configuration as code? You can define notification destinations by creating a Kubernetes secret (or by setting values in your values.yaml) that the Mediator reads at runtime. This is the same delivery path used by UI-configured notifications, a notification created this way also appears as a configured notification in the UI.

To configure mediator-based notifications, enable the executor and specify a webhook URL and token in the values.yaml file.

Add the following under the notifications section of your causely-values.yaml file:

executor:
  enabled: true

notifications:
  webhook:
    url: "https://webhook.example.com/notify"   # Replace with your webhook URL
    token: "your-secret-token"                  # Replace with your webhook token
    enabled: true
info

For more details on webhook payload structure and field definitions, see the Notification Payload Format.

Make sure to replace the placeholder values with your actual webhook URL and token.

Click on an integration below to view mediator-based setup instructions for receiving Causely notifications in your preferred tool.


Grafana Alertmanager
Send causal insights to Grafana Alertmanager without additional configuration.
incident.io
Automatically create and resolve incidents in incident.io from causal analysis by Causely.
Microsoft Teams
Post causal insights into Microsoft Teams to keep dev and ops teams aligned.
Prometheus Alertmanager
Push causal insights into your existing Prometheus Alertmanager pipeline.
Slack
Send causal insights directly to your team Slack channels, so critical issues are seen and acted on immediately.
Splunk On-Call
Deliver real-time causal insights into Splunk On-Call with service-level impact and ownership metadata.
Generic Webhook
Send Causely's notification payload to any HTTP endpoint using a URL and optional token.
Custom Workflows
Send causal insights to any endpoint (for example, GitHub, Linear, n8n) via CauselyBot.
GitHub
Send causal insights to GitHub issues.
GitHub Copilot
Assign issues to GitHub Copilot to get suggestions for fixes.
n8n
Send causal insights to n8n workflows.

How to Choose​

  • Want engineers to quickly understand what changed and why?
    → Native integrations

  • Prefer to configure notifications with point-and-click?
    → Managed notifications (UI-configured)

  • Prefer configuration as code / GitOps?
    → Mediator-based notifications (Kubernetes secret)

Managed and mediator-based notifications deliver the same result, choose whichever matches how you like to work.

Why This Matters​

By separating causal understanding from delivery and action, Causely ensures teams don’t just receive more alerts, they receive the right insight, in the right place, with the right context.

This turns reliability from a reactive exercise into a system of understanding, coordination, and confident action.