omni-resilience
GitHub监控提供商健康、熔断器状态及延迟指标,检查配额与预算限制。支持通过API或MCP实时获取系统快照、提供商指标和数据库健康诊断,用于运维可观测性。
Trigger Scenarios
Install
npx skills add diegosouzapw/OmniRoute --skill omni-resilience -g -y
SKILL.md
Frontmatter
{
"name": "omni-resilience",
"description": "Monitor provider health, circuit-breaker states, p50\/p95\/p99 latency metrics, and budget guard alerts. Inspect connection cooldowns and model lockouts in real time."
}
Overview
Monitor provider health, circuit-breaker states, p50/p95/p99 latency metrics, and budget guard alerts. Inspect connection cooldowns and model lockouts in real time.
Authentication
All requests require a valid Bearer token or session cookie. Obtain a token via POST /api/auth/login or configure REQUIRE_API_KEY=false for local development.
Endpoints
GET /api/monitoring/health
System health check
Returns system health including uptime, memory, circuit breakers, rate limits
curl https://localhost:20128/api/monitoring/health \
-H "Authorization: Bearer $OMNIROUTE_TOKEN"
Payloads
See the full OpenAPI specification at GET /api/openapi/spec or docs/openapi.yaml for detailed request/response schemas.
OmniRoute — Monitoring & Health
Requires OMNIROUTE_URL and OMNIROUTE_KEY. See entry-point SKILL for setup.
System health
curl $OMNIROUTE_URL/api/health \
-H "Authorization: Bearer $OMNIROUTE_KEY"
Returns: uptime, memory, active connections, circuit breaker states, rate limit status, cache stats.
Unauthenticated quick check:
curl $OMNIROUTE_URL/api/health
# → {"ok":true}
Provider circuit breakers
Circuit breakers prevent traffic from hitting failing providers.
States: CLOSED (normal), OPEN (blocked), HALF_OPEN (probe mode — auto-recovers).
curl $OMNIROUTE_URL/api/monitoring/health \
-H "Authorization: Bearer $OMNIROUTE_KEY"
Response includes circuitBreakers array with per-provider state and resetAt timestamp.
Per-provider metrics (p50/p95/p99)
curl $OMNIROUTE_URL/api/providers/metrics \
-H "Authorization: Bearer $OMNIROUTE_KEY"
Response shape per provider:
{
"provider": "anthropic",
"requests": 1247,
"successRate": 0.994,
"latency": { "p50": 820, "p95": 2100, "p99": 3800 },
"circuitState": "CLOSED",
"tokensUsed": 2847000
}
Via MCP (if OmniRoute is your MCP server)
omniroute_get_health → full system health snapshot
omniroute_get_provider_metrics → p50/p95/p99 + circuit state per provider
omniroute_get_session_snapshot → cost, tokens, errors for current session
omniroute_check_quota → quota balance + percent remaining + reset time
omniroute_db_health_check → diagnose + auto-repair database drift
Quota check
curl $OMNIROUTE_URL/api/quota \
-H "Authorization: Bearer $OMNIROUTE_KEY"
Returns used/total tokens and requests per provider/account, with resetAt timestamps.
Budget guard (spend limit)
Set a session spending limit that degrades or blocks requests when hit:
curl -X POST $OMNIROUTE_URL/api/budget/guard \
-H "Authorization: Bearer $OMNIROUTE_KEY" \
-H "Content-Type: application/json" \
-d '{
"limitUsd": 5.00,
"action": "degrade",
"degradeTo": "openai/gpt-4o-mini"
}'
action options:
degrade— switch to a cheaper model when limit is hitblock— return 429 when limit is hitalert— continue but addX-Budget-Warningheader
MCP audit log
OmniRoute logs every MCP tool call to mcp_audit table. Query via API:
curl "$OMNIROUTE_URL/api/mcp/status" \
-H "Authorization: Bearer $OMNIROUTE_KEY"
Returns: server status, heartbeat, recent audit activity summary.
Errors
503on health endpoint → OmniRoute is starting up; retry in 5s- Circuit breaker
OPEN→ provider is temporarily blocked; checkresetAtto know when it auto-recovers 429 budget_exceeded→ budget guard limit reached; raise limit or wait for reset
Version History
- 1cafd32 Current 2026-07-25 11:48


