Skip to main content

Slack Notifications

Slack can be used as a notification destination in Causely.
How you configure Slack depends on how notifications are managed in your environment.

Causely supports two configuration paths:

  • Managed Notifications (recommended)
    Routing rules are configured in the Causely UI based on impact, severity, and context.
    Slack is used purely as a delivery destination.

  • Mediator-based Notifications (advanced)
    Notifications are configured programmatically using the Causely Mediator and Causelybot.

Routing and notification rules for Managed Notifications are configured in the Causely UI: Set up notification routing in the UI


Mediator-based Configuration

If you would like to configure the Slack integration, you can do so by enabling the executor and specifying your Slack webhook UR in the causely-values.yaml file.

For example, add the following in your causely-values.yaml file like this:

mediator:
notifications:
enabled: true

You can define a Slack notification integration through the Causely UI, or by creating a secret in your Kubernetes cluster, in the causely namespace:

apiVersion: v1
kind: Secret
type: Opaque
metadata:
name: slack-notification-config
namespace: causely
labels:
causely.ai/notif-config: Slack
stringData:
notif_config_filters: "[]"
notif_config_filters_enabled: "true"
notif_config_global: "false"
notif_config_name: slack
notif_config_token: ""
notif_config_type: Slack
notif_config_url: https://hooks.slack.com/services/XXX/YYY/ZZZ
note

Ensure the Slack channel webhook defined in the "notif_config_url" is set up to accept incoming messages.

To install the Causely agent with the Slack integration enabled, run:

causely agent install --cluster-name <cluster-name> --values ./causely-values.yaml

Notification Payload Format

Causely sends structured alert payloads to Slack, including summaries of causal insights and service impact context.
For an example payload and explanation of each field, refer to the Notification Payload Format page.