L’interface est localisée ; les présentations et documents des Skills sont traduits automatiquement par IA dans votre langue. Le code, les commandes, chemins et termes techniques restent en version originale, et le document de l’auteur fait foi.
Explorer les Skills
Productivité · SKILL.md

sdk-and-tracing

sdk-and-tracing

Traceloop SDK initialization, decorator tracing, manual spans, and client-facing observability workflows.

Independent GitHub snapshot · Automated classification · Original documentation governs

Documentation de la Skill

GitHub

name: sdk-and-tracing description: "Traceloop SDK initialization, decorator tracing, manual spans, and client-facing observability workflows." disable-model-invocation: true metadata: disco-role: operating license: Apache 2.0

sdk-and-tracing

Use this sub-skill for Traceloop SDK bootstrap, offline tracing, and user-app tracing workflows.

Use it when

  • you need to initialize Traceloop
  • you need exporter or processor setup for local debugging or Traceloop/OTLP delivery
  • you need decorator-based spans from @workflow, @task, @agent, @tool, or @conversation
  • you need manual LLM spans via track_llm_call
  • you need association properties or prompt context on spans
  • you need the prompt, dataset, experiment, user-feedback, or guardrail surfaces at a high level

Install choices

  • Base SDK: traceloop-sdk
  • Dataset helpers: traceloop-sdk[datasets] when you need CSV/DataFrame helpers
  • Debug exporters: InMemorySpanExporter for assertions, ConsoleSpanExporter for inspection

Route elsewhere

Read first

Runtime helpers

Operating notes

  • use_attributes=True is the current default; use_legacy_attributes is deprecated.
  • TRACELOOP_TRACE_CONTENT=false intentionally hides decorated entity inputs/outputs and prompt content.
  • If Traceloop.init() receives both exporter and processor, the exporter is ignored; wrap the exporter inside the processor instead.
  • Traceloop.init() returns a client only when it is using the Traceloop endpoint path with an API key and no custom exporter or processor.
  • Stay at SDK/bootstrap depth here; do not descend into provider wrapper internals or exact semantic-convention tables.
Skills enregistrées