Update ingest route priorities

patch

https://{customerid}.observeinc.com/v1/ingest/routes/{type}

Beta — schema may still change; breaking changes are coordinated with affected customers. Suitable for evaluation, not production reliance.

Reorder the ingest routes for a type. Send an ordered list of route IDs
that sets the new priority order. The list must contain every route ID for
the type, with no duplicates and no other IDs.

Returns all routes for the type in the new priority order.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

type

string

enum

required

The type of the ingest route to query. These types correspond to the various source dataset schemas supported by Observe.
any refers to the "default" generic source dataset schema with the FIELDS and EXTRA columns. All of the others
correspond to direct-write source datasets. Each type is also associated with particular ingest HTTP endpoints that emit
compatible data for that type. Incoming data on a given endpoint is routable to any dataset of the corresponding type.

The following [type -> ingest path] mappings are defined:

otellogs <-> /v1/otel/v1/logs
otelmetrics <-> /v1/otel/v1/metrics
oteltraces <-> /v1/otel/v1/traces
prometheus <-> /v1/prometheus
k8sentity <-> /v1/kubernetes
any <-> /v1/*

Allowed:

Body Params

New priority order for every route of a type. Reordering is a whole-list operation; there is no way to move a single route.

ordering

array of objects

required

Route IDs in the desired priority order, highest priority first. Must contain every route ID for the type exactly once.

ordering*

Responses

200Ingest route priorities updated successfully

400Bad request

401Unauthorized

403Forbidden

404Resource not found

429Rate limit reached

5XXInternal server error