victoriatraces-query

You can query traces from the Jaeger API using curl by sending HTTP requests to the $VM_TRACES_URL/api endpoint to discover services, operations, and retrieve specific traces by ID. The API supports searching by service, operation, duration, and tags.

To find service dependencies and call graphs in VictoriaTraces, query the Jaeger-compatible HTTP API via curl to map service dependencies. This maps the call graph structure to help you understand service relationships during incident investigations.

Yes, you can search Jaeger traces by duration and tags using curl commands against the VictoriaTraces API. The API supports filtering traces by service name, operation, duration limits, and custom tags for targeted root-cause analysis.

No special dependencies are required to search traces in VictoriaTraces beyond having curl installed and access to a Jaeger-compatible endpoint. You simply query the $VM_TRACES_URL/api paths directly without additional libraries.

The best way to investigate latency issues using trace searches is to query the VictoriaTraces Jaeger API via curl. You can discover available services, search traces by operation and duration, and retrieve full traces by ID to quickly surface latency anomalies.

Your VictoriaTraces curl query requires specific time formats because the Jaeger-compatible HTTP API expects documented time formats under the $VM_TRACES_URL/api path. Using the correct time format ensures accurate trace search results and service dependency mapping.