incident.io Integration
Overview
Causely can automatically ingest alerts from incident.io and map them to symptoms and entities in your system with minimal configuration required.
The integration automatically processes incident.io alerts by:
- Detecting symptoms from alert titles and descriptions
- Using Kubernetes labels (namespace, pod, service) for entity mapping
Configuration
Basic Setup
To enable the incident.io integration, add the following to your causely-values.yaml file:
causely-values.yaml
scrapers:
incident:
enabled: true
instances:
- secretName: 'incident-io-credentials'
namespace: 'causely'
Create a Kubernetes Secret with the incident.io API token:
kubectl create secret generic incident-io-credentials \
--namespace causely \
--from-literal=token=your-incident-io-api-token
Alternative: Enable Credentials Autodiscovery
Causely also supports credentials autodiscovery. This feature allows you to add new scraping targets without updating the Causely configuration.
First, enable autodiscovery in your configuration:
causely-values.yaml
scrapers:
incident:
enabled: true
auto_discovery:
enabled: true
Then create a Kubernetes secret with the required label:
kubectl create secret generic incident-io-credentials \
--namespace causely \
--from-literal=token=your-incident-io-api-token
kubectl label secret incident-io-credentials \
--namespace causely \
"causely.ai/scraper=Incident"