Checkmk
xyva.ai integrates with Checkmk to correlate infrastructure monitoring data with test execution, helping you distinguish test failures caused by application bugs from those caused by environment issues.
API Connection Setup
Open Settings > Integrations > Checkmk and enter:
| Field | Example |
|---|---|
| Checkmk URL | https://monitor.example.com/mysite |
| Username | automation |
| API Secret | Secret string from the automation user |
| Site Name | mysite |
TIP
Use a dedicated automation user rather than a personal account. Create one under Setup > Users in Checkmk with the automation role.
Service Health Status
The Checkmk panel displays monitored services relevant to your test environment:
| Status | Icon | Meaning |
|---|---|---|
| OK | Green | Service is healthy |
| WARN | Yellow | Performance threshold exceeded |
| CRIT | Red | Service is down or failing |
| UNKNOWN | Grey | Monitoring data unavailable |
Services are grouped by host. Click any service row to see the full check output, performance graphs, and recent state transitions.
Alert Correlation
When xyva detects test failures, it cross-references the failure timestamp against active Checkmk alerts:
Test Failed: login.spec.ts > should redirect after login
Time: 2026-03-21 14:32:07
Checkmk Alert: Host web-app-01 / Service HTTPS
CRIT since 14:30:55 — Connection refused
Correlation: Environment issue (infrastructure)INFO
Correlation uses a configurable time window (default: 5 minutes). Adjust this under Settings > Integrations > Checkmk > Correlation Window.
This helps teams triage faster by flagging failures that are likely caused by infrastructure problems rather than code defects.
Monitored Hosts
You can select which Checkmk hosts and services are relevant to your test environment. Only selected services participate in alert correlation:
- Open the Checkmk integration panel.
- Click Configure Hosts.
- Check the hosts and service groups you want to monitor.
- Save -- xyva polls these services on the same interval as your monitoring site.
WARNING
Polling frequency matches your Checkmk check interval (typically 60 seconds). xyva does not issue additional load beyond the standard REST API calls.
What To Read Next
- Ops Portal -- broader infrastructure health dashboard
- Swarm QA -- automated scanning that benefits from alert correlation