Telemetry & Observability Strategy - Build vs. Third-Party Integration? #106
oguzserdar
started this conversation in
Ideas
Replies: 1 comment 1 reply
-
|
re: evals https://github.com/AgentDock/AgentDock/blob/evaluation-prd-v1/docs/prd/evaluation-framework.md |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello AgentDock Community,
As outlined in our Telemetry & Observability roadmap, implementing a robust system for monitoring, tracing, and evaluating agent performance is a key priority. This system will be crucial for development, debugging, production monitoring, and quality assurance (linking closely with the Evaluation Framework).
We've reached a crucial decision point regarding the implementation strategy:
Integrate Third-Party Solutions: Leverage established open-source standards and platforms like OpenTelemetry (potentially with backends like Jaeger, Prometheus, Grafana) or more LLM-specific observability platforms like Laminar.
Build a Custom Implementation: Develop a telemetry system tailored specifically for AgentDock's architecture and requirements.
Key Questions for Discussion:
We're looking for input, experiences, and opinions to help guide this decision. Please share your thoughts on the pros/cons, potential challenges, or specific tool recommendations.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions