VictoriaTraces can accept trace spans via the OpenTelemetry protocol (OTLP) .
HTTP APIs #
Opentelemetry API #
VictoriaTraces provides the following API for OpenTelemetry data ingestion:
/insert/opentelemetry/v1/traces
See more details in this docs .
HTTP parameters #
VictoriaTraces accepts optional HTTP parameters at data ingestion HTTP API via HTTP query string parameters , or via HTTP headers .
HTTP query string parameters have priority over HTTP Headers.
HTTP Query string parameters #
All the HTTP-based data ingestion protocols support the following HTTP query string args:
extra_fields
- an optional comma-separated list of trace fields , which must be added to all the ingested traces. The format of everyextra_fields
entry isfield_name=field_value
. If the trace entry contains fields from theextra_fields
, then they are overwritten by the values specified inextra_fields
.debug
- if this arg is set to1
, then the ingested traces aren’t stored in VictoriaTraces. Instead, the ingested data is logged by VictoriaTraces, so it can be investigated later.
See also HTTP headers .
HTTP headers #
All the HTTP-based data ingestion protocols support the following HTTP Headers additionally to HTTP query args :
AccountID
- accountID of the tenant to ingest data to. See multitenancy docs for details.ProjectID
- projectID of the tenant to ingest data to. See multitenancy docs for details.VL-Extra-Fields
- an optional comma-separated list of trace fields , which must be added to all the ingested traces. The format of everyextra_fields
entry isfield_name=field_value
. If the trace entry contains fields from theextra_fields
, then they are overwritten by the values specified inextra_fields
.VL-Debug
- if this parameter is set to1
, then the ingested traces aren’t stored in VictoriaTraces. Instead, the ingested data is traceged by VictoriaTraces, so it can be investigated later.
See also HTTP Query string parameters .