Monitor tracking-data health
The Pipeline Health board answers a prerequisite question for every prediction: is tracking data arriving completely and quickly enough?
Open Pipeline Health
Read the health metrics
| Metric | Meaning |
|---|---|
| Events ingested | Tracking events accepted during the selected period. |
| Feed lag p50 (min) | Median delay from carrier event time to ingestion. |
| Ingest→persist p95 (min) | Slow-tail time from ingestion to durable storage. |
| Poll yield | Useful tracking events returned relative to polling work. |
| Unknown-code rate | Events whose carrier status code is not yet mapped to the shared taxonomy. |
The ingest-to-persist chart uses five minutes as its service-level reference. Short spikes can occur; sustained p95 above the reference means downstream views may lag.
Diagnose a stale carrier
- Check Events ingested by carrier. A sudden drop to zero points to feed or polling failure.
- Check Poll yield. Low yield with active polling can mean the carrier has no new scans, requests are targeting the wrong window, or the feed is returning unusable data.
- Check Feed lag. High lag means events are arriving late even if the pipeline processes them quickly.
- Check Ingest→persist p95. High values here point to processing delay after receipt.
- Check Unknown-code rate. A rise means events arrived but could not be classified precisely.
Connect pipeline health to prediction quality
- Missing events reduce freshness and can delay alerts.
- Late events can make the model react after the best intervention window.
- Unknown codes fall back to a generic exception until taxonomy coverage is updated.
- Low-volume feeds create sparse carrier and lane metrics even when the pipeline is healthy.
Compare this board with Carrier Performance. If one carrier has high lag while the rest are healthy, investigate that feed. If all carriers degrade together, investigate shared ingestion and persistence.
If the board will not load
Click Retry, confirm the selected organization, and check Orderly status. Contact support if the problem continues.
If the board loads but shows no events, confirm an upload completed in Ingest & Scoring or that the ingest API is receiving events.