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 signals, 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—root cause, 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:

Managed Notifications (UI-Configured)​

Decide what gets routed, when, and to whom

Managed routing allows teams to control how causal insights are delivered downstream based on impact, severity, and context, rather than static alert conditions.

Instead of encoding behavior in brittle alert rules, routing decisions are made at the product level, informed by Causely’s understanding of how the system behaves and changes over time.

Use this approach when you want consistent, governed, and explainable delivery of reliability insights as systems evolve, ownership shifts, and reliability practices mature.

Learn more: Managed notifications overview

Mediator-Based Notifications​

Embed Causely into automation and internal systems

For advanced use cases, Causely exposes its reasoning outputs as structured, machine-consumable insights through the Mediator.

This enables custom automation, internal tooling, and infrastructure-as-code workflows where Causely functions as a reasoning component inside broader operational pipelines.

Use mediator-based notifications when you want to automate responses, power internal systems, or deeply customize how causal insight drives downstream behavior.

If you would like to configure mediator-based notifications, you can do so by enabling the executor and specifying 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.


How to Choose​

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

  • Want consistent, governed routing of reliability insights?
    → Managed notifications

  • Want to automate or deeply customize downstream behavior?
    → Mediator-based notifications

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.