Skip to main content

Incident.io Integration

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.

Configuration​

To enable the incident.io integration, update your causely-values.yaml file to include the executor and your incident.io API configuration.

executor:
  enabled: true

notifications:
  incident_io:
    enabled: true
    api_token: 'your-incident-io-api-token'
    # Optional: Override default incident type and severity
    incident_type_id: 'your-incident-type-id' # Optional - uses default if not specified
    severity_id: 'your-severity-id' # Optional - uses "Critical" if not specified
    # Optional: Configure incident resolution
    resolved_status_name: 'Fixed' # Optional - enables auto-resolution
    notify_channel: true # Optional - notify incident channel on resolution
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.

To install the Causely agent with the incident.io integration enabled, run:

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

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.