Notification Payload

Causely sends structured JSON payloads to all webhook-based integrations. Whether you're using Slack, Prometheus Alertmanager, Splunk On-Call, Microsoft Teams, or a custom system, the notification format below applies consistently.

Webhook Notification Payload Example

Here is an example of a notification payload that will be sent to your webhook:

{
   "alert":{
      "status":"firing",
      "labels":{
         "alertname":"FrequentCrashFailure",
         "instance":"6187ffff-06f6-424f-b413-10a7234f0df6_api-gateway",

         "k8s_cluster_name":"dev",
         "k8s_cluster_uid":"00fad1a6-1ff0-4c07-90ce-1db55299b180",
         "k8s_namespace_name":"cloakworks",

         "cluster":"dev",
         "namespace":"cloakworks",
         "service":"cloakworks/api-gateway/api-gateway",
         "severity":"warning",
         "source":"causely"
      },
      "annotations":{
         "details":"The non-zero exit code signifies an error during the execution of the container's process. Possible root causes include:\n\n- Application bugs (e.g., unhandled exceptions).\n- Incorrect configuration or missing environment variables.\n- External dependencies (such as a database) being unavailable or misconfigured.\n- Resource limits other than memory, such as CPU throttling, leading to process failure.\n- A failed health check configured in Kubernetes or Docker, causing container restarts.\n",
         "summary":"One or multiple containers of a workload are frequently crashing with a non-zero exit code, indicating abnormal termination. This disrupts the application’s functionality, leading to downtime or degraded performance depending on how the workload is designed."
      },
      "startsAt":"2025-12-15T04:06:17.841556129Z",
      "endsAt":"0001-01-01T00:00:00Z",
      "generatorURL":"https://portal.causely.app/rootCauses/bec5a8bd-8367-471b-97c9-3801641c7608"
   }
}

Payload fields:

• name: The event name, in this case it's the problem name.
• type: The type of notification (for example, "ProblemDetected").
• entity: The details regarding the entity for which the notification is triggered:
• Id: Id of the entity
• name: Name of the entity
• type: Type of the entity
• description: A description of the issue.
• timestamp: The timestamp when the issue was detected.
• labels: Metadata or tags that provide additional context (for example, app name, Kubernetes namespace, and cluster information).
• objectId: A unique identifier for the specific object associated with this event, in this case it's the problem Id.