Monitors
Integrate monitoring and alerting into orchestration, CI/CD, and observability workflows so teams can react faster and automate responses to data issues.
The Monitors API provides the building blocks to manage monitor discovery, execution, and results retrieval across assets and tenants.
Get a monitor's test result history in reverse chronological order (most recent first). For Schema Drift and Job Failure monitors, the endpoint returns only failing test results (i.e. when an incident is present). For all other monitor types, it returns the full history of results.
Unique identifier of the monitor
110Successful Response
Validation Error
GET /api/v1/data/monitors/history?monitor_id=1 HTTP/1.1
Host: connect.<REGION>.decube.io
Accept: */*
{
"data": [
{
"status": "running",
"period": "2025-08-21T00:03:03.849Z",
"detail": {
"value": 1,
"test_type": "text",
"metric_name": "text"
},
"case_id": 1,
"incident_id": 1
}
]
}Trigger an on-demand run for a monitor. Returns a UUID that can be used to track the execution status. Only one on-demand run can be active at a time per monitor. The monitor must be of a supported type (mode = on_demand) and cannot be a schema drift or job failure monitor.
Unique identifier of the monitor
Successful Response
Validation Error
POST /api/v1/data/monitors/trigger HTTP/1.1
Host: connect.<REGION>.decube.io
Content-Type: application/json
Accept: */*
Content-Length: 16
{
"monitor_id": 1
}{
"job_id": "123e4567-e89b-12d3-a456-426614174000"
}Get the status of an on-demand monitor run. Returns the current status of the run and, if completed, the corresponding test result.
Unique identifier of monitor run
Successful Response
Validation Error
GET /api/v1/data/monitors/status?job_id=123e4567-e89b-12d3-a456-426614174000 HTTP/1.1
Host: connect.<REGION>.decube.io
Accept: */*
{
"status": "running",
"result": {
"status": "running",
"period": "2025-08-21T00:03:03.849Z",
"detail": {
"value": 1,
"test_type": "text",
"metric_name": "text"
},
"case_id": 1,
"incident_id": 1
}
}Last updated