Skip to main content

incident.io Integration

Causely can automatically create and resolve incidents in incident.io based on causal inference findings. This integration enables your team to maintain a centralized incident management workflow while leveraging Causely's deep system insights.

When Causely detects critical or high-severity issues, it can automatically create structured incidents in incident.io with relevant context, severity mapping, and resolution tracking.

incident.io can be used as an incident management destination in Causely.

All incident.io delivery runs through the Causely Mediator.

How you define incident.io destinations depends on your setup:

  • Managed Notifications (recommended)
    Routing rules and incident.io credentials are configured in the Causely UI. The UI stores configuration that the Mediator reads at runtime.

  • Mediator-based configuration (advanced)
    Define incident.io destinations programmatically with environment variables or Kubernetes secrets instead of the UI. Uses the same Mediator delivery path as managed notifications.

For routing rules and filters in the UI, see Set up notification routing in the UI.

Mediator-based configuration (advanced)​

If you prefer not to use the UI, define incident.io destinations with a Kubernetes secret in the causely namespace:

apiVersion: v1
kind: Secret
type: Opaque
metadata:
  name: incidentIO-notification-config
  namespace: causely
  labels:
    causely.ai/notif-config: IncidentIO
stringData:
  notif_config_filters: "[]"
  notif_config_filters_enabled: "true"
  notif_config_global: "false"
  notif_config_name: incidentIO
  notif_config_token: "your-incident-io-api-token"
  notif_config_type: IncidentIO
  notif_config_url: ""
note

Replace your-incident-io-api-token with your actual incident.io API token. You can generate one in your incident.io settings under API tokens.

How It Works​

Incident Creation​

  • Automatic Creation: Causely automatically creates incidents for High and Critical severity issues
  • Severity Mapping: Causely severity levels are mapped to your incident.io severity configuration
  • Rich Context: Incidents include detailed summaries, affected services, and direct links back to Causely's analysis
  • Idempotency: Uses Causely's object ID to prevent duplicate incidents for the same issue

Incident Resolution​

  • Automatic Resolution: When Causely detects that an issue is resolved, it can automatically update the incident status
  • Configurable Status: Set the target resolution status name (for example "Fixed", "Resolved")
  • Channel Notifications: Optionally notify the incident channel when incidents are resolved

Configuration Options​

Required Settings​

  • api_token: Your incident.io API token with incident creation permissions

Optional Settings​

  • incident_type_id: Specific incident type ID (auto-detected if not provided)
  • severity_id: Specific severity ID (defaults to "Critical" severity if not provided)
  • resolved_status_name: Status name for resolved incidents (enables auto-resolution)
  • notify_channel: Whether to notify the incident channel on resolution (default: false)

Advanced Configuration​

The Helm chart automatically configures the required environment variables based on your causely-values.yaml settings. The following environment variables are set automatically:

  • INCIDENT_IO_API_TOKEN: Set from the secret containing your API token
  • INCIDENT_IO_INCIDENT_TYPE_ID: Set from incident_type_id if provided
  • INCIDENT_IO_SEVERITY_ID: Set from severity_id if provided
  • INCIDENT_IO_RESOLVED_STATUS_NAME: Set from resolved_status_name if provided
  • INCIDENT_IO_NOTIFY_CHANNEL: Set from notify_channel if provided

Notification Payload Format​

Causely sends rich notification data to incident.io based on its causal inference. For an example and explanation of each field, refer to the Notification Payload Format page.