Export agent trajectories with a separated exporter

未關閉
#42,657 0 則留言 1 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
25/100
Issue 類型
功能
描述清晰度
需要釐清
活躍度
活躍
技術堆疊
typescript
領域
ai, observability

研究方向

No files, tests, or entry points are named. Start by locating the shared Logfire export path and the agent trajectory instrumentation, then clarify endpoint and ownership requirements; done is separate business-trajectory and ops-observability exports with agreed endpoints and coverage.

由索引模型根據 Issue 內容生成。

描述

💪 enhancement
Self Checks
  • I have read the Contributing Guide and Language Policy.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • Please do not modify this template :) and fill in all the required fields.
1. Is this request related to a challenge you're experiencing? Tell me about your story.

Currently, the agent and web server share a single Logfire instance. However, agent trajectories belong to the business domain, whereas system observability belongs to the ops domain. Moving forward, these should likely be exported to separate endpoints (e.g., Langfuse vs. Jaeger).

2. Additional context or comments

No response

3. Can you help us with this feature?
  • I am interested in contributing to this feature.
主要語言
TypeScript
星號
157k
分支
24.7k
平均合併
22 小時 32 分鐘
30 天內合併 PR
611

貢獻指南

開啟貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

langgenius/dify 的其他 Issue

查看 langgenius/dify 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。