{"componentChunkName":"component---src-templates-acg-portal-new-template-tsx","path":"/Mms8r66bk","result":{"data":{"markdownRemark":{"html":"

Codex 通过 Langfuse 插件接入百度 LLM

\n

通过 Langfuse Codex Observability Plugin 将 Codex 的对话 Trace 上报至BCM-> LLM应用性能监控。该插件以 Codex Stop Hook 机制运行，每次 Codex turn 完成后读取会话记录，转换为 Langfuse 格式的 Trace 并上报。接入后，Codex 的每次对话会在 LLM应用性能监控 中展示为一条 Trace，包含 LLM 调用、工具执行、子 Agent 等完整调用链。可参考 langfuse官方文档 了解插件的完整功能和配置选项。

\n

前提条件

\n\n

步骤1：获取接入点与 Token

\n

注：该信息因地域和用户而异，可在控制台“接入应用”页面获取，下方为示例

\n\n

步骤2：安装 Langfuse 插件

\n\n
\n
\n
\n Bash\n \n
\n
\n 
1codex plugin marketplace add langfuse/codex-observability-plugin
\n
\n
\n
\n \n

步骤3：启用插件

\n

在 ~/.codex/config.toml 中启用：（注意自己实际运行的CodeX的目录）

\n\n
\n
\n
\n TOML\n \n
\n
\n 
1[features]\n2plugin_hooks = true\n3\n4[plugins."tracing@codex-observability-plugin"]\n5enabled = true
\n
\n
\n
\n \n

步骤4：配置接入凭证

\n

在 ~/.codex/langfuse.json 中配置：

\n\n
\n
\n
\n JSON\n \n
\n
\n 
1{\n2  \"enabled\": true,\n3  \"public_key\": \"<Authentication>\",\n4  \"secret_key\": \"sk-placeholder\",\n5  \"base_url\": \"http://apm-collector.bj.baidubce.com\"\n6}
\n
\n
\n
\n \n

对应的字段说明如下：

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
参数描述示例
public_key>步骤1获取的鉴权 TokenUFSpMM*******lnFrVBqtPDK
<secret_key>任意非空字符串，服务端不校验，但必须非空sk-placeholder
<endpoint>任意非空字符串，服务端不校验，但必须非空http://apm-collector.bj.baidubce.com
<base_url>百度 APM 接入点http://apm-collector.bj.baidubce.com
\n

也可以使用环境变量配置：

\n\n
\n
\n
\n Bash\n \n
\n
\n 
1export TRACE_TO_LANGFUSE=true\n2export LANGFUSE_PUBLIC_KEY=\"<Authentication>\"\n3export LANGFUSE_SECRET_KEY=\"sk-placeholder\"\n4export LANGFUSE_BASE_URL=\"http://apm-collector.bj.baidubce.com\"
\n
\n
\n
\n \n

步骤5：设置 service.name 和 host.name（可选）

\n
\n

⚠️ Langfuse 插件 v0.1.0 使用 NodeTracerProvider 时未传入 resource 参数，导致 OTel SDK 使用 defaultResource() 硬编码 service.name = unknown_service:node，且不读取 OTEL_SERVICE_NAME、OTEL_RESOURCE_ATTRIBUTES 等标准环境变量。host.name 同理需手动注入。

\n
\n

解决方式： 设置以下环境变量，同时修改插件 bundle。

\n\n
\n
\n
\n Bash\n \n
\n
\n 
1export OTEL_SERVICE_NAME=\"<应用名>\"\n2export OTEL_RESOURCE_ATTRIBUTES=\"host.name=<主机名>\"
\n
\n
\n
\n \n

编辑以下两个文件（相同修改）：

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
文件描述
marketplace 源~/.codex/.tmp/marketplaces/codex-observability-plugin/plugins/tracing/dist/index.mjs
运行时缓存~/.codex/plugins/cache/codex-observability-plugin/tracing/<版本号>/dist/index.mjs
\n

在 setupInstrumentation 函数中，将：

\n\n
\n
\n
\n JavaScript\n \n
\n
\n 
1const provider = new import_src.NodeTracerProvider({ spanProcessors: [spanProcessor] });
\n
\n
\n
\n \n

改为：

\n\n
\n
\n
\n JavaScript\n \n
\n
\n 
1const attrs = { "service.name": process.env.OTEL_SERVICE_NAME || "codex" };\n2if (process.env.OTEL_RESOURCE_ATTRIBUTES) {\n3  process.env.OTEL_RESOURCE_ATTRIBUTES.split(",").forEach(pair => {\n4    const [k, ...v] = pair.trim().split("=");\n5    if (k) attrs[k.trim()] = v.join("=").trim();\n6  });\n7}\n8const provider = new import_src.NodeTracerProvider({\n9  spanProcessors: [spanProcessor],\n10  resource: require_src$3().defaultResource().merge(\n11    require_src$3().resourceFromAttributes(attrs)\n12  )\n13});
\n
\n
\n
\n \n

步骤6：验证接入

\n

重启 Codex 后发起一次对话，插件会在每个 turn 完成后触发。查看本地日志确认导出成功：

\n\n
\n
\n
\n Bash\n \n
\n
\n 
1sqlite3 ~/.codex/logs_2.sqlite \"\n2SELECT ts, level, feedback_log_body\n3FROM logs\n4WHERE feedback_log_body LIKE '%ExportSucceeded%'\n5ORDER BY ts DESC LIMIT 5;\"
\n
\n
\n
\n \n

看到 HttpMetricsClient.ExportSucceeded 或类似记录说明导出成功。\n然后到 LLM应用性能监控 搜索 service.name = <你设置的应用名> 查看 Trace 数据。由于数据的处理存在一定延时，如果接入后在控制台没有查询到应用，请等待 30 秒左右。

","fields":{"slug":"Mms8r66bk","title":"CodeX 通过 Langfuse 插件接入百度 LLM","date":"2026-08-03","extractedHeadings":[]},"headings":[{"value":"Codex 通过 Langfuse 插件接入百度 LLM","depth":2},{"value":"前提条件","depth":3},{"value":"步骤1：获取接入点与 Token","depth":3},{"value":"步骤2：安装 Langfuse 插件","depth":3},{"value":"步骤3：启用插件","depth":3},{"value":"步骤4：配置接入凭证","depth":3},{"value":"步骤5：设置 service.name 和 host.name（可选）","depth":3},{"value":"步骤6：验证接入","depth":3}]}},"pageContext":{"isCreatedByStatefulCreatePages":false,"slug":"Mms8r66bk","prev":{"id":"Vmoy30f2b","name":"APM与Grafana Tempo兼容","path":"Vmoy30f2b","filePath":"典型实践/APM和LLM最佳实践/APM与Grafana Tempo兼容.md","seo":null,"parentIds":["Okx7b5erv","Lmfz2ortv"],"parents":[{"id":"Okx7b5erv","documentId":"81554908-8e82-4013-8002-8672c96eb3cf","name":"典型实践","repoName":"BCM","filePath":"典型实践","disabled":false,"path":"Okx7b5erv","lastMergeTime":null,"isApiDoc":null,"httpMethod":null,"seo":null,"sourceOrgName":null,"sourceRepoName":null,"sourceDocumentId":null},{"id":"Lmfz2ortv","documentId":"09d2f373-be54-4061-8681-f91b6df2f07c","name":"APM和LLM最佳实践","repoName":"BCM","filePath":"典型实践/APM和LLM最佳实践","disabled":false,"path":"Lmfz2ortv","lastMergeTime":null,"isApiDoc":null,"httpMethod":null,"seo":null,"sourceOrgName":null,"sourceRepoName":null,"sourceDocumentId":null}]},"next":{"id":"Fme9l2djx","name":"服务等级协议SLA","path":"Fme9l2djx","filePath":"服务等级协议SLA/APM和LLM应用性能监控服务等级协议SLA.md","seo":null,"parentIds":["aldi7w3wd"],"parents":[{"id":"aldi7w3wd","documentId":"97a5b397-14e3-47a2-94d2-97bbe80870a9","name":"服务等级协议SLA","repoName":"BCM","filePath":"服务等级协议SLA","disabled":false,"path":"aldi7w3wd","lastMergeTime":null,"isApiDoc":null,"httpMethod":null,"seo":null,"sourceOrgName":null,"sourceRepoName":null,"sourceDocumentId":null}]},"parents":[{"id":"Okx7b5erv","documentId":"81554908-8e82-4013-8002-8672c96eb3cf","name":"典型实践","repoName":"BCM","filePath":"典型实践","disabled":false,"path":"Okx7b5erv","lastMergeTime":null,"isApiDoc":null,"httpMethod":null,"seo":null,"sourceOrgName":null,"sourceRepoName":null,"sourceDocumentId":null},{"id":"Lmfz2ortv","documentId":"09d2f373-be54-4061-8681-f91b6df2f07c","name":"APM和LLM最佳实践","repoName":"BCM","filePath":"典型实践/APM和LLM最佳实践","disabled":false,"path":"Lmfz2ortv","lastMergeTime":null,"isApiDoc":null,"httpMethod":null,"seo":null,"sourceOrgName":null,"sourceRepoName":null,"sourceDocumentId":null}],"specificSeo":null}}}