IICTPIICTP

Blog / Guides

Telemetry26 October 20265 min read

Observability for AI systems: tracing LLM calls, tokens and drift

A language-model application fails in ways ordinary monitoring does not see: the service is up and fast, yet the answers are poor. Observability for AI adds visibility of what went in, what came out and what it cost.

In this post
  1. What to trace
  2. What to measure
  3. Privacy
  4. Sources and further reading

What to trace

  • Each model call: model, settings, latency and token counts.
  • Retrieval steps: what was fetched and how relevant it was.
  • Tool calls and their results.
  • The full chain for one user request, as a single trace.

What to measure

  • Cost per request and per feature.
  • Quality signals: feedback, retries, refusals, evaluation scores.
  • Drift: quality changing after a model, prompt or data change.

Privacy

Prompts and outputs can contain personal data. Decide what to store, mask sensitive fields and limit access and retention. OpenTelemetry has emerging conventions for generative-AI telemetry; check their current status before depending on them.

Sources and further reading

  1. OpenTelemetry. Semantic conventions for generative AI. opentelemetry.io/docs/specs/semconv/gen-ai/.

IICTP is a new independent credential and is not ISO/IEC 17024 accredited.

Keep reading

← All posts

Where do you stand?

Find the credential that fits the work you do.