Monitoring API v1
Public JSON endpoints of the monitoring, including the structured export prepared for the EOSC Federation.
All read endpoints are public, return JSON with UTC ISO-8601 timestamps and allow cross-origin requests. Base URL: https://mon.eosc.sk`.
| Endpoint | Purpose |
|---|---|
GET /api/v1 | Index of endpoints, supported periods and status vocabulary |
GET /api/v1/health | Health of the monitoring service and its collector |
GET /api/v1/status | Current status of all services and the rolled-up node status |
GET /api/v1/services | Monitored services with their check parameters |
GET /api/v1/services/{service_id} | One service: definition, status, metrics, daily series |
GET /api/v1/metrics | Availability, reliability and uptime per service |
GET /api/v1/checks | Raw probe results (the evidence behind the metrics) |
GET /api/v1/events | Status transitions |
GET /api/v1/federation/export | Full structured document for federation harvesting |
Query parameters: period = 1h, 24h, 7d, 30d (default), 90d, 365d; service = service id; daily=0 to omit per-day series.
Example – node status
{
"schema_version": "1.0",
"generated_at": "2026-09-18T12:35:05Z",
"node_id": "eosc-node-sk",
"node_status": "OK",
"services_by_status": { "OK": 8, "WARNING": 0, "CRITICAL": 0, "UNKNOWN": 0, "DOWNTIME": 0, "MISSING": 0 },
"services": [ { "service_id": "sk-eosc-portal", "name": "Landing page - EOSC Node Slovakia",
"status": "OK", "response_ms": 25, "message": "HTTP 200 in 25 ms" } ]
}Federation export
/api/v1/federation/export is self-describing: node identity, collector provenance, the reporting period, a node summary and one entry per service with its current status, metrics and per-day series. It follows the ARGO status and availability conventions so that the EOSC Federation can harvest it directly.