At a glance
Share of calls to the DHL Geschaftskundenportal API that failed in the last 24 hours, expressed as a percentage of total requests. It is the early-warning gauge for the Deutsche Post connection: a healthy link sits near zero, while a sustained climb means bookings, label generation or tracking ingestion are starting to fail before the despatch team notices missing parcels. The alert fires above 2 percent.
What it tracks
The card counts failed DHL API responses (HTTP 4xx and 5xx) against total requests over a rolling 24-hour window, grounded in thedetail: “API Error Rate for the selected period.” The mix of error codes points at the cause. A spike in 401 / 403 usually means a credential problem, so check Days to Token Expiry first. A spike in 5xx points at DHL-side instability rather than anything in your account. A spike in 422 / 400 points at malformed booking or label payloads, often a bad address or weight field, which surfaces downstream on Label Generation Success. Sustained errors above the >2% threshold mean some despatch actions are silently not completing, so treat a tripped alert as a despatch risk, not just a technical one.