LogQueryRequestDto
Log query request
{
"logQuery": "SELECT * FROM logs WHERE text='scheduling developer at in minutes from now' AND application='test_application' ORDER BY ingest_timestamp DESC",
"start": 1689143864023,
"end": 1689144164023,
"rows": 50,
"parallelizationFactor": -1,
"extractedFieldsEvaluation": {
"contentPackIdsToInclude": [
"89048dde-0445-4b36-a276-74ghy5d3f870"
],
"includeAllFields": false
}
}
Relative URI path of the service managing this document. Can be a complete link, or just a request ID.
Authorization links associated with this request
OrgId for which telemetry data is to be queried
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.
Start timestamp (milliseconds) for the query to be run
End timestamp (milliseconds) for the query to be run
Number of rows to be returned
Callback URL called when query is complete
Payload sent to callbackUrl
Dynamic fields that need to be used in the SQL query (without creating extracted fields)
Subject to filter based on specified user
Page number for current page of results, set when constructing a query during next page handling.
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