MCP Academy · 课时

端到端追踪工具调用

跟踪一次请求经过整个技术栈的过程。

端到端追踪工具调用 是 CoddyKit 上的免费 MCP Academy 课时。这是第 3 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 MCP Academy 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 MCP Academy 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Following One Call

A single tool call may touch your server, a database, and an API. Tracing stitches those hops into one timeline so you see the whole journey. 🧵

Traces and Spans

A trace is the full request; a span is one step inside it. Each span records a name, a start, and a duration, and spans nest like a tree.

The Trace ID

Every span in one request shares a single trace ID. That shared id is what lets a tool reconstruct exactly which steps belonged together.

Parent and Child Spans

Spans link through a parent ID. The tool call is the parent; the database query and API call become its children, forming the timeline tree.

OpenTelemetry

The standard for this in Python is OpenTelemetry. It defines traces, spans, and context so your data works with many backends, not just one.

Start a Span

You wrap work in a span using a context manager. Everything inside it is timed and nested under the current trace automatically.

from opentelemetry import trace
tracer = trace.get_tracer("mcp")

with tracer.start_as_current_span("search_tool"):
    run_search()

Add Attributes

Decorate a span with attributes: small key-value facts like the tool name or result count. They make a trace far easier to read later.

span = trace.get_current_span()
span.set_attribute("tool.name", "search")
span.set_attribute("result.count", 3)

Spans Catch Errors

When a step fails, mark its span with the error status. The trace then shows you exactly which hop broke the request, not just that it broke.

Context Propagation

To trace across a network call, you pass the trace context along in headers. This propagation keeps the remote step under the same trace.

Link Logs to Traces

Put the trace ID into your structured logs too. Now a log line and its full trace point at each other, and debugging gets dramatically faster.

Exporting Traces

Spans are sent to a backend through an exporter, often via the OTLP protocol. The backend then draws the timeline you click through.

Quick Check

Let us confirm the trace structure.

Recap

You can now trace a call end to end with spans under one trace ID, enriched with attributes, error status, and logs that link straight back. 🗺️

常见问题解答

「端到端追踪工具调用」课时是免费的吗？

是的 — 「端到端追踪工具调用」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 MCP Academy 课程的其余内容，请升级到 CoddyKit PRO。 MCP Academy 课程共包含 4 节课。

「端到端追踪工具调用」这节课中我会学到什么？

跟踪一次请求经过整个技术栈的过程。你通过在浏览器中直接运行的动手代码来练习 MCP Academy，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 MCP Academy 需要有经验吗？

无需任何先前经验。CoddyKit 上的 MCP Academy 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 3 节课，共 4 节。

「端到端追踪工具调用」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 MCP Academy 课中编写并运行代码吗？

能。每节 MCP Academy 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 MCP Academy