Add grafana mcp tooling for debugging e2e client tests#247
Merged
bisgaard-itis merged 8 commits intoMar 31, 2026
Conversation
pcrespov
approved these changes
Mar 30, 2026
Member
pcrespov
left a comment
pcrespov
left a comment
There was a problem hiding this comment.
thx. Looking forward to give it a spin.
I am curious about what you found while using it. Tell me offline.
Member
|
And come on ... write the issue description properly (took the liberty of removing all the icons you left uncommented...) ;-) |
bisgaard-itis
deleted the
add-grafana-mcp-tooling-for-debugging-e2e-client-tests
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces new documentation and configuration to support debugging of failing end-to-end (e2e) tests, particularly by leveraging Grafana Loki and the MCP server. The main changes provide a detailed workflow for analyzing pytest error logs, querying server-side logs, and using Grafana dashboards to diagnose issues. Additionally, a new VSCode configuration template for connecting to a local Grafana MCP server is included, and the Python client README is updated with instructions for running the MCP server and utilizing the new debugging workflow.
Documentation for e2e test debugging:
.github/skills/debug-e2e-tests/SKILL.mdguide detailing how to analyze pytest failures, extract key error details, query Grafana Loki logs, classify errors, and utilize the simcore/Services Grafana dashboard for root cause analysis.clients/python/README.mdwith instructions on running the Grafana MCP server via Docker and using it in conjunction with the copilot to debug client e2e test failures.Configuration for local development:
.vscode/mcp.template.jsonto configure a local SSE connection to the Grafana MCP server, streamlining local debugging workflows.What do these changes do?
Related issue/s
How to test
For internal developers