You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[FEATURE] support the backend of opentelemetry-collector #76
I have searched existing issues to avoid duplicates
I have provided a clear problem statement and solution
I understand this is a feature request and not a bug report
I am willing to help implement this feature if needed
I have submitted this feature request in English (otherwise it will not be processed)
🎯 Problem Statement
Our LLM app has already integrated the OTEL SDK and collects data through OTEL-collector by default. We intend to use Coze-loop as the observation service for the backend, but it seems that this operation is not currently supported.
💡 Proposed Solution
According to the documentation, coze-loop is fully compatible with the GENAI specification. We hope to utilize the automatic instrumentation solution here, https://opentelemetry.io/blog/2024/otel-generative-ai/, to support direct sending to coze-loop, or configure the otel-collector to directly export to coze-loop.
📋 Use Cases
Can work collaboratively with an independent OpenTelemetry collector
⚡ Priority
High - Would significantly improve my experience
🔧 Component
Observation
🔄 Alternatives Considered
Currently using langfuse, but it's not compatible with events
Activity
lsy357 commentedon Aug 28, 2025
Hi, we have supported trace reporting with OpenTelemetry in version 1.2.0. For usage instructions, please refer to: https://loop.coze.cn/open/docs/cozeloop/opentelemetry_trace_overview. Welcome your feedback!