You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
[deep-report] Investigate MCP telemetry coverage gap (18/20 runs missing gateway.jsonl and rpc-messages.jsonl) #47100
The Observability Coverage report (discussion #46935) sampled 20 MCP-enabled runs from the last 7 days and found 18 of 20 (90%) emit neither gateway.jsonl nor rpc-messages.jsonl — MCP Gateway coverage is only 10%. The two runs with telemetry both fell back to rpc-messages.jsonl; none exposed gateway.jsonl. One failed run was also missing telemetry entirely, blocking root-cause. Investigate why the gateway is not persisting logs to artifacts on most runs (upload step gated? path mismatch? gateway not started?).
Expected Impact
Restores MCP observability so gateway/RPC failures are diagnosable; closes a fleet-wide blind spot that currently makes most MCP-enabled runs un-troubleshootable.
Suggested Agent
Observability agent / New Agent for artifact-upload wiring.
Activity
github-actions commentedon Jul 22, 2026
🍪 Issue Monster selected this for Copilot
I have identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.
If assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.
Om nom nom! 🍪