Right now there are no documented conventions for MCP spans. This means that span name inference wouldn't work correctly, and we have no reference for what the correct name would be. This already caused us to make incorrect decisions when making pre-built MCP dashboards which rely on the incorrect name "mcp.server".
Right now there are no documented conventions for MCP spans. This means that span name inference wouldn't work correctly, and we have no reference for what the correct name would be. This already caused us to make incorrect decisions when making pre-built MCP dashboards which rely on the incorrect name
"mcp.server".