-
Notifications
You must be signed in to change notification settings - Fork 63
MCP Server #1113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
MCP Server #1113
Conversation
…n MCP tools and handlers
…r live check tool
…metric, search, and span tools
…icies and preprocessor support
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1113 +/- ##
=======================================
+ Coverage 79.1% 80.4% +1.2%
=======================================
Files 102 104 +2
Lines 7943 8229 +286
=======================================
+ Hits 6284 6617 +333
+ Misses 1659 1612 -47 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
| /// - `get_entity` - Get a specific entity by type | ||
| /// - `live_check` - Validate telemetry samples against the registry | ||
| #[derive(Clone)] | ||
| pub struct WeaverMcpService { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know this may be crazy, but is there any chance we can re-use the vanilla API server and just "wrap" API methods with MCP definitions instead of having two instances of serving / application flow?
I think there's a LOT of commonality between the two pieces, and it'd be ideal if we could share it.
This PR adds
weaver registry mcpan MCP (Model Context Protocol) server that exposes the semantic conventions registry to LLMs. This enables natural language queries for finding and understanding conventions while writing instrumentation code.searchget_attributeget_metricget_spanget_eventget_entitylive_check