Create

Sign in to ReadmeX

or

How we handle your data: Privacy Policy

ReadmeX

Your AI reading companion

What would you like to catch up on?

Pick a briefing, or ask your own question.

Your community and people briefings stay personal to you.

OTLP

AI overview

Sign in and the AI will write an overview from our coverage.

Headlines · 1

  1. Agent observability: tracing a wrong number across four handoffs

    A technical article uses a teaching scenario in which an agent cites the correct announcement but reports an incorrect number, with no API error and an all-green tracing page. It proposes four checkpoints: source to tool result, tool result to actual model request, request to generated answer, and generated answer to user-visible text. The article also draws on the authors’ own Langfuse observability records, covering a 256 KiB body-capture limit, a double-slash URL that redirected requests and caused a background export error, an isolated ClickHouse recovery drill, and de-duplication of cost records representing the same physical request. The opening scenario is explicitly a teaching exercise; possible causes such as missing units, omitted footnotes, incomplete input and model misunderstanding are branches rather than a confirmed root cause.

    掘金 · 人工智能 · 🔥 0

Experience and discussion from the community

Share my OTLP experienceAsk about OTLP

jaeger: A distributed tracing system for collecting, storing, and querying application traces.

What problem it solves Distributed applications need a way to collect, store, and inspect traces across their components. The project addresses this with an all-in-one distribution, an OTLP ingestion path, and separate collector, query, UI, and storage components. Key features All-in-one deployment — The Docker distribution combines the UI, collector, query service, and in-memory storage so traces…

github.comhttps://github.com/jaegertracing/jaeger