pinecall telemetry · Pinecall Docs

Where the org's calls' traces go: its own OpenTelemetry collector, set with its headers off stdin, shown by name, cleared.

Terminal

$ printf %s "$DD_API_KEY" | pinecall telemetry set https://otlp.datadoghq.eu/v1/traces --header dd-api-key
traces go to https://otlp.datadoghq.eu/v1/traces · headers dd-api-key
$ pinecall telemetry
traces go to https://otlp.datadoghq.eu/v1/traces · headers dd-api-key · words stripped

Where this org sends a copy of its calls' traces: an OpenTelemetry collector of its own — Langfuse, Datadog, Grafana, or one you run. Off until set; the console's call page, Observability, judges and monitors read the call's log, never this. Every spoken call's spans go there over OTLP (a chat has no worker and so no spans): the model's requests (gen_ai.*: provider, model, tokens, time to first token), speech in and out, every tool the agent ran, each span carrying pinecall.org, pinecall.env, pinecall.agent and pinecall.call, so one call is one trace in your tool. set takes the URL on the command line and each header's value from stdin, one per --header, in the order named — typed without echo on a terminal, or piped one line per header — never from a flag. --pii lets a span carry what was said and what a tool got; without it the words are stripped before export and the timings, tokens and names stay. The gateway keeps the headers sealed and never reads them back: the bare verb prints the URL and the headers' names. clear stops the export; the calls' logs stay on Pinecall either way. Langfuse takes two headers, piped one line each: Export traces.