Validation & monitoring
Monitoring, metrics, and SLOs (Service Level Objectives)
Metrics to monitor
| Metric | How to Measure | Alert Threshold |
|---|---|---|
| Success rate | HTTP 200 responses / total requests | Alert if < 95% over 1 hour |
| CDS sync lag | Time since last successful CDS sync | Alert if > 36 hours |
| Ingestion completeness | Properties ingested vs eligible | Alert if < 98% coverage |
| Response latency | Track p50, p95, p99 | Alert if p95 > 10 seconds |
Recommended health checks
Run the following checks periodically (e.g., hourly) to verify integration health.
- Authentication check — Make a lightweight Reference Data API call (e.g., entity=continent) and verify HTTP 200 response.
- Content freshness check — Select 5 random properties, fetch via Properties API, and compare key fields against your data store.
- Reference data consistency — Verify your stored reference data counts match the
totalCountvalues from the API.
SLOs
The following are indicative targets. Refer to your partner agreement for contractual SLAs.
| Metric | Target |
|---|---|
| API availability | 99.9% uptime |
| Response latency (Properties API) | p95 < 2.5 seconds |
| Response latency (Reference Data API) | p95 < 2 seconds |
| Data freshness | Content reflects the source of truth within 24 hours |
Updated 11 days ago
Did this page help you?