observability
Skill0 starsChanged 7 months agoMITView on GitHub
Logging is re-exported from @reaatech/mcp-gateway-core (logger.ts).
87 other projects use a version of this.
Adopted by
Most recently taken up by
- juninmd/skillstheir own version, first seen Nov 8, 2026
- domengabrovsek/agent-configtheir own version, first seen Nov 8, 2026
- domengabrovsek/claudetheir own version, first seen Nov 8, 2026
- Ingvord/legendary-bassoontheir own version, first seen Nov 8, 2026
- sundaram2021/claude-code-observability-systemtheir own version, first seen Nov 8, 2026
- Mehul72/skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use gitops, background-jobs and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
kcns008Skillgitops
GitOps Agent (Flow) — manages ArgoCD applications, Helm charts, Kustomize overlays, deployment strategies (canary, blue-green, rolling), multi-cluster GitOps, and drift detection for Kubernetes and OpenShift clusters.
Also in 4 projects that use this
YepAPISkillbackground-jobs
Queue workers with BullMQ/Inngest/Trigger.dev, job retries, dead letter queues, concurrency.
Also in 4 projects that use this
Mushfiqur-Rahman-RobinSkillrag-systems
Best practices for building Retrieval-Augmented Generation systems — chunking, embedding, hybrid retrieval, reranking, indexing, caching, evaluation, observability — plus a catalog of RAG patterns and when each applies.
Also in 3 projects that use this
- YepAPISkill
data-pipelines
ETL patterns, cron scheduling, queue-based processing, and batch jobs with Inngest/BullMQ.
Also in 4 projects that use this
wpankSkillcaching
Caching strategies, invalidation, eviction policies, HTTP caching, distributed caching, and anti-patterns. Use when designing cache layers, choosing eviction policies, debugging stale data, or optimizing read-heavy workloads.
Also in 5 projects that use this
JohnJBorenSkillci-cd
CI/CD pipeline design, GitHub Actions, testing automation, and deployment strategies
Also in 13 projects that use this
Other versions87 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 87
- openai/plugins★ 7.8ksame name
- BuilderIO/agent-native★ 7.6ksame name
- brianlovin/briOS★ 2.3ksame name
- lablup/backend.ai★ 679same name
- DevelopersGlobal/ai-agent-skills★ 216same name
- kid-sid/claude-spellbook★ 190same name
- YougLin-dev/Aha-Loop★ 181same name
- proyecto26/system-design-skills★ 118same name
- TheBeardedBearSAS/claude-craft★ 108same name
- AsiaOstrich/universal-dev-standards★ 84same name
77 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- audit-trailSkill
- authSkill
- fan-outSkill
- rate-limitingSkill
- response-cachingSkill
- schema-validationSkill
- tool-allowlistSkill
The file
Files
Observability
Capability
OpenTelemetry auto-initialization, pre-built metrics, distributed tracing, health check endpoints, and structured logging.
Package
@reaatech/mcp-gateway-observability — packages/observability/src/
Logging is re-exported from @reaatech/mcp-gateway-core (logger.ts).
Components
| Component | Purpose |
otel.ts | OTel SDK auto-initialization (if OTEL_EXPORTER_OTLP_ENDPOINT set) |
otel.impl.ts | OTel implementation: NodeSDK setup, trace/metric exporters, shutdown |
metrics.ts | Counters, histograms, gauges for gateway observability |
tracing.ts | Spans for auth, rate limit, cache, validation, allowlist, upstream, fanout |
health.ts | Liveness, readiness, deep-health probes with pluggable component checks |
Metrics
| Metric | Type | Labels |
gateway.requests.total | Counter | tenant_id, status |
gateway.requests.duration_ms | Histogram | tenant_id, method |
gateway.auth.attempts | Counter | method, result |
gateway.rate_limit.exceeded | Counter | tenant_id |
gateway.cache.hits | Counter | tool |
gateway.cache.misses | Counter | tool |
gateway.upstream.errors | Counter | upstream, error_type |
gateway.fanout.upstreams | Counter | strategy |
gateway.validation.errors | Counter | type |
gateway.upstream.latency_ms | Histogram | upstream |
gateway.audit.events | Counter | event_type |
Health Endpoints
| Endpoint | Purpose |
/health | Liveness — always returns 200 if process is running |
/health/deep | Deep — runs all registered probes, per-component status |
Health Probes
| Export | Description |
registerProbe(name, fn) | Register a custom health probe |
createRedisProbe(pingFn) | Factory for Redis ping health check |
createUpstreamProbe(url) | Factory for upstream HTTP health check |
resetProbes() | Clear all probes (for testing) |
Tracing
Each request generates spans for: gateway.auth, gateway.rate_limit, gateway.cache,
gateway.validation, gateway.allowlist, gateway.upstream, gateway.fanout.
Error Handling
- OTel SDK fails gracefully if exporter unavailable
- Metrics collection continues even if OTel fails
- Health probe failures return 503 with per-component details
Security Considerations
- Logs contain no raw tokens or PII (automatic redaction via core logger)
- Request IDs included in all log lines for traceability
- Tenant IDs included in all log lines for debugging
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.