Integrations
Connect KubeWatch to databases and external notification services.
KubeWatch integrations fall into two categories: monitoring integrations (databases and services you want to observe) and notification integrations (channels where alerts are delivered).
Monitoring integrations
Supported services
| Integration | What KubeWatch monitors |
|---|---|
| PostgreSQL | Connection count, active queries, query rate, replication lag, cache hit ratio |
| MySQL / MariaDB | Connections, queries/sec, slow queries, replication status |
| Redis | Connected clients, memory usage, hit rate, evictions/sec, keyspace |
| Kafka | Consumer group lag, broker throughput, partition count, under-replicated partitions |
Adding a monitoring integration
- Navigate to Integrations → Add Integration
- Select the service type
- Enter the connection string (e.g.,
postgresql://user:password@host:5432/dbname) - Click Test Connection to verify KubeWatch can reach the service
- Click Save
The integration will appear in the Integrations list with a connection status indicator. Metrics begin appearing within one push interval (15 seconds by default).
Using integration metrics in alerts
Integration metrics follow the naming convention {integration_type}.{metric_name}, for example:
postgres.active_connections > 100 for 2m
redis.memory_used_percent > 85 for 5m
kafka.consumer_group_lag > 10000 for 10m
Create these as alert rules just like container metrics, go to Alerts → New Rule and type the metric name manually.
Connection string security
Connection strings are encrypted at rest using AES-256 and are never exposed in API responses or logs. You can rotate a connection string by editing the integration.
Notification integrations
Slack
- Create an Incoming Webhook in your Slack workspace: api.slack.com/messaging/webhooks
- Go to Integrations → Notifications → Add Slack
- Paste the webhook URL
- Optionally set a default channel override
- Click Test to send a test message
Alert notifications include the rule name, current metric value, threshold, container/agent name, and a deep link to the dashboard.
PagerDuty
- In PagerDuty, create a new integration on a service (Events API v2)
- Copy the Integration Key
- Go to Integrations → Notifications → Add PagerDuty
- Paste the Integration Key
- Click Test
KubeWatch creates a PagerDuty incident when an alert fires and resolves it automatically when the alert resolves.
On the hosted SaaS plan, KubeWatch sends email via its own mail relay, no SMTP configuration needed. Just add recipient addresses.
On the self-hosted plan, configure your SMTP server:
- Go to Integrations → Notifications → Add Email
- Enter: SMTP host, port, username, password, TLS setting
- Enter recipient addresses (comma-separated)
- Click Test
Generic Webhook
Send alert payloads to any HTTP endpoint:
- Go to Integrations → Notifications → Add Webhook
- Enter the URL
- Optionally add custom headers (e.g.,
Authorization: Bearer ...) - Click Test, KubeWatch sends a sample payload
Webhook payload format:
{
"alert": {
"id": "alert_abc123",
"ruleName": "High CPU on prod-web",
"state": "firing",
"metric": "cpu_percent",
"value": 94.2,
"threshold": 90,
"operator": ">",
"firedAt": "2026-06-12T10:00:00Z"
},
"container": {
"name": "web-app",
"id": "container_xyz",
"agentName": "prod-k8s"
}
}