Repository navigation
Release 1.6.0
Immutable
release. Only release title and notes can be modified.
Added
observability-builder: OneUptime's AI / LLM views as an LLM-monitoring destination.genai.content.destination(langfuseorops) sends prompts and answers to one tool per service, never both, andbackends/oneuptime.mddescribes what the views read: call kinds, problems, conversations, usage and pricing.observability-builder: who spent what. The spender, the team and the conversation come from the app's own verified context, decided per entry point; on the ops path AI spans carryuser.id,team.idandgen_ai.conversation.id, where OneUptime attributes spend.observability-builder: MCP servers and clients (workloads/mcp.md): a span per message on each side, context throughparams._meta, the JSON-RPC status rules, one span per tool call, and themcp_server_operation_duration_secondsandmcp_client_operation_duration_secondsmetrics.observability-builder: thegenai-langfuse-two-sendersaudit rule; validate checks for the content destination; the receiver's--genai-content-destinationflag and summary lines for who spent what, AI keys on other spans, retrieval steps, MCP and Langfuse span senders.
Changed
observability-builder: retrieval steps carrygen_ai.operation.name=retrievalandgen_ai.retrieval.top_k; memory, planning and agent-creation step kinds are added; a sub-agent call is oneinvoke_agentspan; the turn's input and output go on the Langfuse trace; no cost is written unless the provider reports one.observability-builder: the ops allow-list keeps the MCP keys, the OpenInference and OpenLLMetry model and usage keys, anduser.idandteam.id; spans that aren't AI calls lose theirgen_ai.*,llm.*andtraceloop.*keys, which OneUptime would count as AI calls. The collector's GenAI routing does the same.observability-builder: one span sender to Langfuse per service is a stated rule; all three Langfuse modes stay, withhybridthe default.observability-builder: SDK notes foropenai3 andmcp2 overhttpx2, the MCP Python SDK 2.x client spans and protocol probe, OTLP exporter errors fed back into the log export,ExceptionGroupon FastAPI SERVER spans and the JavaScript exporters' warning on JSON replies. Direct export to OneUptime: ops metrics need a scraper, and the yml addsdeployment.environmentfor exceptions. Path exclusions are decided when the response ends.- README and COMPATIBILITY list the
1.6.0release.
1.6.0
Required
No migration required. genai.content.destination defaults to langfuse, the 1.5.0 behaviour,
so existing observability.yml files validate and behave unchanged.
Recommended
- Re-run
observability instrumenton services that call a model, to add the user, team and
conversation to their AI spans (OneUptime's Usage shows their spend as Unattributed without
them), the retrieval operation, the new allow-list keys, and the removal of AI keys from spans
that aren't AI calls. - Where prompts and answers should be read in OneUptime instead of Langfuse, set
genai.content.destination: ops, with Langfuse modehybridorotel, or Langfuse off. - Instrument MCP servers and clients with
references/workloads/mcp.md, including the server
and client MCP metrics. - Collectors with GenAI routing: update the ops branch from
references/collector/README.md
(identity on AI spans, AI keys off other spans, the new allow-list) and list the services whose
content destination isopsin both branches (^$while there are none). - Services exporting straight to OneUptime: add
deployment.environment: "${OBS_ENVIRONMENT}"
underresource.attributes, arrange a scraper for/metrics, and add OneUptime prices for
self-hosted or aliased models.
Verify
python3 -m unittest discover -s observability-builder/scripts/testspasses, and the receiver
tests pass withuv run --no-project --with grpcio --with opentelemetry-proto --with protobuf --with pyyaml python -m unittest discover -s scripts/tests -p "test_receive.py"from
observability-builder/.- A re-instrumented AI service's receiver summary shows the user, team and conversation on its AI
calls and noAI KEYS ON OTHER SPANSalarm.