Skip to main content

Opsgenie

Opsgenie Integration​

Causely can send high-context root cause alerts directly to Opsgenie, ensuring your team receives precise, actionable notifications. Alerts include diagnostic context such as impacted services, severity, and timestamps—so your on-call engineers can triage and resolve incidents faster.

Configuration​

To integrate Opsgenie with Causely, you must install the Causelybot and configure it as your Opsgenie webhook endpoint. The bot listens for alerts from the Causely platform and posts them to your desired Opsgenie teams.

  1. Follow the installation instructions for the Causelybot in the official GitHub repository: Causelybot

  2. Once deployed, update your causely-values.yaml file to include the executor and the bot's URL endpoint.

For example, if you deploy the Causelybot in the foo namespace of your cluster, you can configure the webhook endpoint in your causely-values.yaml file like this:

executor:
  enabled: true

notifications:
  webhook:
    enabled: true
    url: 'http://causelybot.foo.svc.cluster.local/opsgenie'
note

Make sure the Causelybot is accessible from your Causely deployment and properly configured to post to your Opsgenie account and target team or teams.

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

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

Notification Payload Format​

Causely sends structured alert payloads to Opsgenie with embedded root cause context and service impact data.
For an example payload and explanation of each field, refer to the Notification Payload Format page.