Skip to content

[deep-report] Investigate MCP telemetry coverage gap (18/20 runs missing gateway.jsonl and rpc-messages.jsonl) #47100

Closed

Description

@github-actions

Description

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.

Estimated Effort

Medium (1-4 hours).

Data Source

DeepReport analysis 2026-07-21; discussion #46935.

Generated by 🔬 Deep Report · age00 200.9 AIC · ⌖ 17.2 AIC · ⊞ 9.9K · ◷

  • expires on Jul 23, 2026, 7:27 AM UTC-08:00

Activity

  1. github-actions commented on Jul 22, 2026

    @github-actions
    ContributorAuthor

    🍪 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! 🍪

    🍪 Om nom nom by Issue Monster · gpt54 4.37 AIC · ⌖ 7.38 AIC · ⊞ 8K · ◷

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

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions