Documentation Index Fetch the complete documentation index at: https://developer.watson-orchestrate.ibm.com/llms.txt
Use this file to discover all available pages before exploring further.
Use the watsonx Orchestrate ADK CLI to get traces from your active environment and export their spans.
Searching traces
Use filters to search for traces.
You identify trace IDs by setting criteria such as time range, service names, agent identifiers or names, user identifiers, session identifiers, or span count.
orchestrate observability traces search --start-time < start date and time for searc h > --end-time < end date and time for searc h >
A start time for the results.
This flag cannot be used with --last flag.
An end time for the results.
This flag cannot be used with --last flag.
A service name to filter results. Can be specified multiple times.
An agent ID to filter results. Can be specified multiple times.
An agent name to filter results. Can be specified multiple times.
A user ID to filter results. Can be specified multiple times.
A session ID to filter results. Can be specified multiple times.
A minimum span count for a trace.
A maximum span count for a trace.
A field used for sorting results.
A sort direction for the results.
A limit on the number of traces returned. Configure a value from 1 to 1000.
The shorthand for setting a relative time window that ends now. You can enter:
Minutes. For example: 30m / 30 minutes
Hours. For example: 3h / 3 hours
Days. For example: 10d / 10 days
This flag cannot be used with --start-time or --end-time flags.
After you identify the trace IDs, run orchestrate observability traces export to export the full trace data.
Exporting traces spans
Export spans from the watsonx Orchestrate observability platform.
This command fetches all spans for a specific trace ID and sends them to a file or standard output in JSON format. The JSON output follows the OpenTelemetry specification.
orchestrate observability traces export --trace-id < trace I D >
A 32‑character hexadecimal trace ID to export.
A file path for the command output. When omitted, output is displayed in the CLI. Note The output file must be in JSON format. When a different file type is provided, a warning is shown.
Indented JSON output for easier readability. This flag is used only with the --output / -o flag. Default is --pretty.