Skip to content

microsoft/azure-observability

v1.0.0MIT

Guide read-only Azure web/API and Foundry-agent troubleshooting, approved fixes, and evidence-based recovery validation.

assess-observability-health

Assess operational Azure application/resource or Foundry-agent health from supplied evidence or authorized telemetry: failed requests, runtime/tool errors and application latency. Return ranked findings and gaps read-only. Not resource creation, general coding fixes or deployment readiness. Direct health requests do not require the coordinator; conceptual health/monitoring questions need no journey.

connect-observability

Find or connect an Azure application's or Foundry agent's telemetry for an explicit observability, monitoring, alerting, health or operational diagnosis request. Confirm source scope and task-specific telemetry access; not generic app connection, resource creation or deployment readiness. Instrumentation/collection design can precede deployment; answer conceptual questions directly. No automatic provisioning or changes.

troubleshoot-observability

Coordinate Azure observability troubleshooting for application or agent health, runtime failures, operational latency, telemetry, monitoring, alerts, evidence-backed fixes and recovery. Use for an end-to-end observability investigation or explicit instrumentation, collection or alerting guidance. Not general resource/app/agent creation, model deployment, RBAC, cost or coding. Conceptual questions need no journey; explicit specialist requests stay direct. Actions require applicable approval.

verify-observability-fix

Verify operational incident recovery for Azure web/API or Foundry agents after an actual approved change, using supplied original/post-change evidence and agreed symptom/guardrail thresholds. Not generic code-fix validation, deployment readiness or resource creation. Conceptual questions need no journey. Never deploy, diagnose, run evaluations or infer causation.