Troubleshoot observability vs Verify observability fix
Troubleshoot observability is an open-source agent skill for cloud and infrastructure. Verify observability fix is an open-source agent skill for cloud and infrastructure.
- Troubleshoot observability is best for investigate why an azure api suddenly started returning errors.
- Verify observability fix is best for verify that azure api latency returned to normal after a rollback.
- What it is
- Troubleshoot observability is an open-source agent skill for cloud and infrastructure.Verify observability fix is an open-source agent skill for cloud and infrastructure.
- Best for
- Investigate why an Azure API suddenly started returning errorsVerify that Azure API latency returned to normal after a rollback
- Kind
- SkillSkill
- Pricing
- Open sourceOpen source
- Platforms
- Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf, GooseClaude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf, Goose
- GitHub stars
- 3.2K3.2K
- Last commit
- Nov 2026Nov 2026
- License
- MITMIT
- Open source
- Good for
- Investigate why an Azure API suddenly started returning errors; Find out why latency spiked on a service in the last hour; Review whether an Azure alert is firing for the right reasonsVerify that Azure API latency returned to normal after a rollback; Check whether a Foundry agent's error rate recovered after a model configuration change; Compare p95 latency before and after an approved web service fix
What Troubleshoot observability does
Intent-gated routing
Admits only real operational observability requests and answers conceptual questions directly without starting a journey.
Bounded affected-path investigation
Investigates a named alert, failure or slow operation within a defined UTC window and tracked budgets.
Health assessment handoff
Routes broad health checks to a separate assessment step and waits for the user to pick a finding.
Scope and permission checks
Clarifies the scope, access and approvals needed before any live read or change is attempted.
Evidence-backed next actions
Proposes supported fixes, mitigations or alert and collection improvements tied to the gathered evidence.
Recovery verification
Compares before and after evidence to judge whether a change worked and how to keep monitoring it.
What Verify observability fix does
Before and after comparison
Compares supplied original and post-change metric windows against agreed symptom thresholds.
Guardrail regression checks
Applies required quality and regression guardrails alongside the original symptom checks.
Tail latency verification
Uses source-computed percentile values such as p95 rather than averages for latency checks.
Evidence sufficiency gates
Checks sample counts, observation spans, freshness and window chronology before accepting results.
Deterministic helper script
Runs a stdlib-only Python script on a bounded local JSON file, with a tools-only fallback.
Narrow verdict reporting
Returns recovered, not recovered or inconclusive with concrete gaps and no causal claims.
Troubleshoot observability vs Verify observability fix: questions
Is Troubleshoot observability or Verify observability fix cheaper?
Both are open source. Compare current plans on each official site.
What is the difference between Troubleshoot observability and Verify observability fix?
Troubleshoot observability is an open-source agent skill for cloud and infrastructure. Verify observability fix is an open-source agent skill for cloud and infrastructure.
