Skip to content

feat(slo): MCP SLO Observability v2.3.4#10

Closed
SynapseLayer wants to merge 1 commit intomainfrom
feat/slo-observability-v2.3.4
Closed

feat(slo): MCP SLO Observability v2.3.4#10
SynapseLayer wants to merge 1 commit intomainfrom
feat/slo-observability-v2.3.4

Conversation

@SynapseLayer
Copy link
Copy Markdown
Owner

MCP SLO Observability & Uptime Proof Loop — v2.3.4

Changes

  • McpRequestLog Prisma model (append-only, zero PII)
  • lib/telemetry.ts — fire-and-forget request logging
  • lib/metrics.ts — SLO report engine (p50/p95/p99, 24h/7d)
  • slo_report MCP tool (admin-only, timingSafeEqual)
  • health_check upgraded to 3-tier (healthy/degraded/unhealthy)
  • All 18 POST exit paths instrumented
  • Version bumped to 2.3.4
  • Supabase comment removed (claims governance)

Security Gate: 8/8 PASS ✅

  1. McpRequestLog zero PII fields
  2. slo_report uses timingSafeEqual
  3. health_check always HTTP 200
  4. No prohibited claims
  5. ADMIN_TOKEN configured
  6. Version consistency (route.ts/smithery.yaml/server.json)
  7. ≥15 logMcpRequest calls covering all exits
  8. slo_report in AUTH_EXEMPT + TOOLS

⚠️ DO NOT MERGE — Human review required per Synapse Protocol

- McpRequestLog append-only model (zero PII)
- lib/telemetry.ts: fire-and-forget request logging
- lib/metrics.ts: SLO report engine (p50/p95/p99)
- slo_report MCP tool (admin-only, timingSafeEqual)
- health_check upgraded to 3-tier (healthy/degraded/unhealthy)
- All 18 POST exit paths instrumented
- 8/8 Security Gate tests PASS
- Supabase inline comment removed (claims governance)

DO NOT MERGE — requires human review per Synapse Protocol v2.3.4
@SynapseLayer
Copy link
Copy Markdown
Owner Author

Superseded by PR #12 (merged as ffdd11b4). C5.1 Public Surface Governance consolidates all copy, metadata, and version sync changes into a single PR. Closing as part of C5.1.2 Hard Closure Gate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant