360 Secure SkillHub
360 安全技能中心

Trace Debuger

输入 trace_id 后，脚本从 Jaeger 拉取链路、从 Elasticsearch 拉取日志，按时间排序后在代码仓库根目录调用 Codex 结合代码排查 bug，输出固定结构的 Markdown 报告，并把结论摘要按要求发给用户后删除本地报告文件。

gakkiismywife
gakkiismywife
热度 62.36
最近更新 2026-05-17 13:19:20
分类：开发依赖：代码执行 / 读写文件 / 第三方 API / 内部调用大模型应用场景：调试排错 / API 集成 / 报告撰写 / 代码审查

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add trace-debuger
Metadata
name
trace-debuger
description
End-to-end trace debugging from trace_id. Fetch Jaeger trace and Elasticsearch logs, analyze possible bugs (optionally with local repository context), and generate a fixed-structure Markdown report for CI or tickets.

Trace Debuger

Use this skill to generate a self-contained Markdown trace debug report.

Inputs

  • trace_id (required)
  • jaeger_url (optional, default http://127.0.0.1:16686)
  • es_url (optional, default http://127.0.0.1:9200)
  • repo_path (optional, absolute path, default /Users/noodles/Desktop/code/go-components/examples/tracer)
  • output_path (optional, default ./trace_debug_report_{trace_id}.md)
  • es_index (optional, default filebeat-tracer-*)
  • es_size (optional, default 2000)

Run

python3 skills/trace_debuger/scripts/trace_debuger.py \
  --trace-id <TRACE_ID> \
  [--jaeger-url http://127.0.0.1:16686] \
  [--es-url http://127.0.0.1:9200] \
  [--repo-path /Users/noodles/Desktop/code/go-components/examples/tracer] \
  [--output-path ./trace_debug_report_<TRACE_ID>.md]

Output

  • Writes Markdown report to output_path
  • MUST send the generated Markdown report to the user as a file attachment via the chat window in the same session before finishing the task
  • MUST send the report as ONE chat message only: attach the Markdown file and put the strict summary block in the same message caption/body.
  • 【markdown报告文件】 is a placeholder and MUST be replaced with the real uploaded Markdown filename (example: trace_debug_report_<trace_id>.md).
  • Use exactly this format in caption/body:
<真实markdown报告文件名>
trace_id: xxxx
status: xxx
jaeger_url: xxx
es_url: xxx
代码仓库路径：仓库路径
关键结论摘要：xxxx
  • Prints fixed summary lines to stdout:
trace_id: <trace_id>
status: SUCCESS/FAIL
jaeger_url: <jaeger_url>
es_url: <es_url>
代码仓库路径：<repo_path|N/A>
关键结论摘要：<summary>

Notes

  • Keep logs sorted by timestamp ascending.
  • After fetching ES logs, run Codex in repository root (automated via codex exec equivalent to TUI paste workflow) with this prompt:
    • 这是我的日志，请根据日志结合代码帮我排查分析bug，输出bug原因及解决方案,必须保持固定的格式。
  • If repository is provided, include code-context hints and file matches for suspected bug areas.
  • If repository is not provided, base bug hypotheses on logs + spans only.
  • After analysis in chat workflow: send the generated Markdown report as a file attachment to the user through the chat window, with the strict summary block in the same message caption/body (single message only).
  • The first line must be the real Markdown filename (not placeholder text).
  • Finally, delete the local Markdown file.