Integration Error Observability

samber/developer-platform-skills/skills/integration-error-observability

作者 samber594cf70d343eMIT3 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫10 天前更新

Design how a platform surfaces integration failures to the external developers and partners who built against it - per-integration request/event/delivery logs with replay, correlation IDs that survive from response header to support ticket, error-rate aggregation per API key or app split by 4xx/5xx/429, proactive partner notification with cooldowns against alert fatigue, and a provider-side fleet view of which integrations are breaking. Use whenever the user mentions a developer-facing error dashboard, exposing request logs to integrators, alerting partners about broken integrations, or cutting integration support tickets - even if they never say "observability". Do NOT use for platform-wide incident comms - use samber/developer-platform-skills@api-status-communication instead.

僅公開檔案列表。將技能安裝到工作區後即可檢視檔案內容。

路徑大小類型
evals/evals.json41.6 KBapplication/json
references/alerting-and-notification.md8 KBtext/markdown
references/correlation-id-conventions.md7.2 KBtext/markdown
references/fleet-view-and-health-scoring.md7.4 KBtext/markdown
references/visibility-surfaces.md7.4 KBtext/markdown
SKILL.md27.4 KBtext/markdown

來源與署名

來源:samber/developer-platform-skills位於skills/integration-error-observability提交594cf70

授權條款: MIT

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架