LogQueryRequestDto

End timestamp (milliseconds) for the query to be run

Start timestamp (milliseconds) for the query to be run

It represents the SQL query to be executed. All queries are run on and filtered by ingest_timestamp by default, but you can query logs on log_timestamp also. To run any query on log_timestamp, add the keyword log_timestamp in the ORDER BY clause.

For example:

Below query returns results filtered by ingest_timestamp:

SELECT * FROM logs WHERE text=‘error’ ORDER BY ingest_timestamp DESC

Below query returns results filtered by log_timestamp:

SELECT * FROM logs WHERE text=‘error’ ORDER BY log_timestamp DESC

Note: Query by log_timestamp is only valid for indexed partitions.

Temporary to support low cost queries till archive configs are added as partitions in lint-control-plane

Page number for current page of results, set when constructing a query during next page handling.

Relative URI path of the service managing this document. Can be a complete link, or just a request ID.

Dynamic fields that need to be used in the SQL query (without creating extracted fields)

OrgId for which telemetry data is to be queried

Default extracted field evaluation

Callback URL called when query is complete

Only used for low cost queries. Strictly for internal use (Will not be exposed to the user) Number of data planes the query should run on

PartitionIds from where we need the response. This might be removed once we figure out an intelligent way to distinguish the partitions from the query constraints. This is done for testing the partition flow for query

Number of rows to be returned

Payload sent to callbackUrl

Subject to filter based on specified user

Authorization links associated with this request