Integration Health Monitoring

You are finding the integrations that work today and will break on a date you already know - a sunset, an SDK end of life, a credential expiry, a payload-version retirement - and getting each one's owner to move first. The deliverable is a census that names every integration at risk and the person who can fix it, a notification loop that reaches that person, and a gate that says when it is safe to turn the old surface off.

Integrations failing right now belong to samber/developer-platform-skills@integration-error-observability. The deprecation policy itself - notice windows, headers, fall-forward or hard cutoff - belongs to samber/developer-platform-skills@api-versioning-policy. This skill executes that policy one integration at a time.

The recurring failure is counting calls instead of owners. A sunset at "99% of traffic migrated" still breaks every integration in the remaining 1%, and the providers who broke them could not say who they were or how to reach them.

Interview

Ask before building anything. Batch them: this is an operational task, not a strategy interview.

1. What breaks, and when? List every dated change on the horizon: version sunsets, removed endpoints or fields, SDK end of life, auth-method removal, certificate or TLS changes, webhook payload-version retirement.
2. Is every request tagged with an integration identity - API key, OAuth client ID, app ID - at the gateway? What share of traffic carries none?
3. Who builds against you: customers' own engineers, partner apps installed across many customer accounts, or plugins and agencies whose end users never talk to you? (see "Who sits behind an integration")
4. What contact do you hold per integration, when was it last confirmed, and do you track bounces?
5. What is the longest business cycle an integration runs on? Monthly invoicing, quarterly reporting, year-end close and annual renewals all call once and go quiet.
6. Is the replacement surface stable and feature-complete for the migrating use cases? Escalation past a reminder is unfair while it is not.
7. Deadline, payoff and effort: is the date fixed by contract, security or cost, is this one sunset or a standing practice you will run for every future change, and what can you spend - engineering weeks, a partner team's hours, an account manager per top integration?