4 ms·
The second link helps It's interesting to wonder if 80% of the question answering can be achieved as a prompts/otel.md over MCPs connected to Claude Code and l
by lmeyerov 1y ago
The second link helps
It's interesting to wonder if 80% of the question answering can be achieved as a prompts/otel.md over MCPs connected to Claude Code and let agentic reasoning do the rest
Ex:
* When investigating errors, only query for error-level logs
* When investigating performance, only query spans (skip logs unless required) and keep only name, time. Linearize as ... .
* When querying both logs & traces, inline logs near relevant trace as part of an llm-friendly stored artifact jobs/abc123/context.txt
Are there aspects of the question answering (not ui widgets) you think are too hard there?
- zecheng 1y agoYes, we can connect for example CC with MCPs. But this may not work well for example if user wants to check the latency for previous 10 days error log on function A. By using MCP the agent needs to get 10 days error logs at first and then somehow get the latency and correlates them, apply filters for function A. IMO it will hallucinate a lot if there are too many tools, logs and traces. But on TraceRoot platform we "mixed" all necessary data at first, and based on user's query apply filters on structured data, which is more accurate, straightforward and efficient. Here is the README of the general design https://github.com/traceroot-ai/traceroot/tree/main/rest/agent https://github.com/traceroot-ai/traceroot/tree/main/rest/age...