Skip to content

feat: Add span name conventions for MCP server spans #377

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.

Sign up for GitHub

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

Open
gggritso wants to merge 1 commit into
base: main
Choose a base branch
from
+19 −0
Open

feat: Add span name conventions for MCP server spans #377

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions model/name/mcp.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
{
"brief": "Model Context Protocol (MCP)",
"operations": [
{
"name": "Server",
"brief": "MCP server-side operations. Processing of incoming MCP requests or notifications initiated by a client, such as tool calls, prompt requests, and resource reads.",
"is_in_otel": true,
"otel_notes": "OpenTelemetry uses gen_ai.tool.name and gen_ai.prompt.name for the target in the span name. Sentry uses mcp.tool.name and mcp.prompt.name instead.",
"ops": ["mcp.server"],
"templates": [
"{{mcp.method.name}} {{mcp.tool.name}}",
"{{mcp.method.name}} {{mcp.prompt.name}}",
"{{mcp.method.name}}",
"MCP server operation"
],
"examples": ["tools/call get-weather", "prompts/get analyze-code", "resources/read", "initialize"]
}
]
}
Loading