Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This article lists and describes the parameters you can use in Devo Query API query requests as well as the different response formats:

...

Parameter

Type

Description

Content-Type *required

String (header)

This is always application/json

Authorization

String (header)

Include this header if you want to use a token to authorize your request. When you use a token, only the Content-Type and Authorization parameters are required.

See Authorizing Query API requests for more information.

x-logtrust-apikey

String (header)

This is the Devo domain API key found in Administration → Credentials.

x-logtrust-sign

String (header)

HMAC SHA-256 using the API_SECRET to sign the concatenation of the api_key, body message and timestamp

x-logtrust-timestamp

String (header)

Timestamp in milliseconds.

query

String (body)

This is the query that you want to run, expressed in LINQ. To find the query's LINQ script, open the query in the Data Search area, then choose Query code editor from the toolbar.

The body of the request must contain either the query or the queryId parameter.

queryId

String (body)

This is the ID of the query that you want to run. To find the query ID, open the query in the Data Search area, then choose Additional Tools → Current query → Get ID.

The body of the request must contain either the query or the queryId parameter.

from *required

Number (body)

The start date as a UTC timestamp in seconds. See the Relative dates section below to learn more about this parameter.

to

Number (body)

The end date as a UTC timestamp in seconds. If this parameter is left out, the query will be continuous. See the Relative dates section below to learn more about this parameter.

mode

Object (body)

This object contains the mode.type parameter to specify the format of the response. If left out of the request body, the default response type JSON will be used.

mode.type

String (body)

The format in which you want the response to be sent. The possible values are:

  • json
  • json/compact
  • json/simple
  • json/simple/compact
  • msgpack
  • csv
  • tsv
  • xls

These response formats are fully described later in this article. When you indicate a response format other than json, you must include the dateFormat and timeZone parameters.

destination

Object (body)

This object specifies where the response should be sent. If this object is left out of the request body, the response will be sent back to the request source.

destination.type

String (body)

This is the type of system to which the response should be sent. The possible values are:

  • hdfs
  • s3
  • email
  • snmp
  • kafka

Depending on the destination.type, additional parameters will be required. See the related HDFS, S3, email, SNMP and Kafka articles.

destination.params

List (body)

Destination parameters, depend on the destination.type. Check the HDFS, KafkaS3, email and SNMP articles to see the parameters required for each destination.

dateFormat

String (body)

This is only required when you specify a mode.type other than json. The possible formats are:

  • default - yyyy-MM-dd' 'HH:mm:ss.SSS
  • sql - yyyy-MM-dd' 'HH:mm:ss.SSS
  • iso - yyyy-MM-dd'T'HH:mm:ss.SSSXX

timeZone

String (body)

Change the timezone of the query, only for mode types different from JSON. This parameter supports any positive or negative GMT timezones, like GMT-2 or GMT+1

skip/offset

Number (body)

You can use either the skip or offset parameters to skip the first X elements of the query.

limit

Number (body)

Limit the results of the query. The query will stop after returning the first X elements of the query or reaching its end.

ipAsString

Boolean (body)

Set this parameter to true (ipAsString = true)if you want to get IP addresses as dotted strings (for example, 94.2.23.1). If you don't add this parameter in your request or set it to false, IP addresses will be returned as numbers (for example, 1577195265).

progressInfo

Boolean (body)

Set this parameter to true if you want to get progress info about the requested query. You will get an entry p with the timestamp of the event that is being processed at that moment. Progress info will be sent at most once every 5s. 

This is only available if you set mode.type as json/simple/compact. See an example below.

...

OperatorDescription

h

Enter a number followed by h in the from parameter to subtract N hours from the current time. If you use it in the to field you will get the from time plus the indicated number of hours.

  • "from": "2h"
    This sets the starting date to 08-10-2018, 12:33:12 UTC

  • "from": "16h"
    This sets the starting date to 07-10-2018, 22:33:12 UTC

  • "from": 1536150131 (this timestamp corresponds to 05/09/2018, 12:22:11 UTC)

    "to": "2h"
    This sets the ending date to 05-09-2018, 14:22:11 UTC


  • "from": "5h"

    "to": "2h"
    This sets the starting date to 08-10-2018, 09:33:12 UTC and the ending date to 08-10-2018, 11:33:12 UTC

ah

Enter a number followed by ah in the from parameter to subtract N hours from the current date at 00:00:00. If you use it in the to field you will add the indicated number of hours to the from date at 00:00:00. Note that the timeZone parameter affects the date settings.

  • "from": "2ah"
    This sets the starting date to 07-10-2018, 22:00:00 UTC

  • "from": "2ah"
    "timeZone": "GMT+2"
    This sets the starting date to 07-10-2018, 22:00:00 GMT+2 (07-10-2018, 20:00:00 UTC)


  • "from": 1536114131 (this timestamp corresponds to 05-09-2018, 02:22:11 UTC)
    "to": "12ah"
    This sets the starting date to 07-10-2018, 22:00:00 GMT+2 (07-10-2018, 20:00:00 UTC)


  • "from": 1536106931 (this timestamp corresponds to 05-09-2018, 12:22:11 GMT+2)
    "to": "12aH"

    "timeZone": "GMT+2"
    This sets the ending date to 05-09-2018, 12:00:00 GMT+2 (05-09-2018, 10:00:00 UTC)

    .

  • "from": "5ah"
    "to": "21ah"
    This sets the starting date to 07-10-2018, 19:00:00 UTC and the ending date to 07-10-2018, 21:00:00 UTC

Anchor
Query response formats
Query response formats
Query response formats

Responses to your queries can be either returned to the source of the request, forwarded to an HDFSS3, SNMP, or Kafka type system, or sent via email.

...

The JSON response will include the following fields: 

Field name

Type

Description

msg/error

String

This describes the error in the case that the request was not successful. This field will be named msg or error depending on the type of error returned.

The corresponding error code will be shown in the status field. Check the possible codes and corresponding messages below.

status

Integer

Numeric value that specifies the error code. When it shows 0, it means no error occured.

These are the possible error codes that you may get. The corresponding error descriptions will be displayed in the msg/error field.

  • 400
  • 401
  • 403
  • 404
  • 500

Also, when you get a 400 status code and the error Bad parameters, the object field will include more information about the specific error returned, as in the following example:

{
    "error": "Bad parameters",
    "status": 400,
    "timestamp": 1584033078759,
    "cid": "XXXX",
    "object": [
        "405: Date from not valid or not found"
    ]
}

object

JSON Object

This object contains the query result. The format of the object's content depends on the query data.

cid

String

An ID value to uniquely identify yourself across multiple systems.

timestamp

String

Indicates the moment when a certain event occurred.

Example

Here is a response in JSON format that occurred without error. 

...

  • The m object lists the fields included in each query result along with their type and index metadata.
Field nameDescription
typeThe data type of the value returned. This will be one of:

timestamp - epoch value in milliseconds

str - string

int8 - 8-byte integer

int4 - 4-byte integer

bool - boolean

float8 - 8-byte floating point

indexAn integer value that indicates the position of the field's value in the arrays returned in the object.d object.
  • The metadata object gives information about the fields as an array, and includes the following fields:
Field nameDescription
nameName of the field.
typeThe data type of the value returned. This will be one of:

timestamp - epoch value in milliseconds

str - string

int8 - 8-byte integer

int4 - 4-byte integer

bool - boolean

float8 - 8-byte floating point

  • The object d includes lightweight event info.

Example

Here is an example of a response in JSON/compact format that occurred without error:

...

  • The m object lists the fields included in each query result along with their type and index metadata.
Field nameDescription
typeThe data type of the value returned. This will be one of:
  • timestamp - epoch value in milliseconds
  • str - string
  • int8 - 8-byte integer
  • int4 - 4-byte integer
  • bool - boolean
  • float8 - 8-byte floating point
indexAn integer value that indicates the position of the field's value in the arrays returned in the object.d object.
  • The metadata object gives information about the fields as an array, and includes the following fields:
Field nameDescription
nameName of the field.
typeThe data type of the value returned. This will be one of:
  • timestamp - epoch value in milliseconds
  • str - string
  • int8 - 8-byte integer
  • int4 - 4-byte integer
  • bool - boolean
  • float8 - 8-byte floating point
  • The object d includes the array of values with the returned events data. Every row is a valid JSON object.

...