plumber)
batch.info.date_human
batch.info.date_string
batch.info.request_id
batch.info.source
batch.info.date_human
field which uses ISO 8601 format.map[string]string
and if queried via Athena (instead of the dashboard), you must use the following syntax:${MODIFIER input}
Or to use multiple modifiers: ${MODIFIER input AND MODIFIER input AND ...}
ORDER_BY <field_name>
ORDER BY
in SQLSORT ASC|DESC
ORDER BY ... ASC|DESC
`LIMIT <number>`
LIMIT <number>
`UNIQUE <field_name>`
`GROUP BY ...`
AND
between the modifiers.AND
).foo
in batch.info.source
.client.payload.age
is greater than 32
AND client.payload.title
is set to "engineer".foo
when there are events with foobar
will return both foo
and foobar
. SELECT ... WHERE client.payload.field = 'foo'
foo
query is acceptable for searching for data, it cannot be used to facilitate a replay as there is nothing to indicate which field it represents.SELECT ... WHERE foo LIKE '%bar%`
?*
- the asterisk will cause the Batch query translator to use LIKE
in the query and replace the asterisks with a %
.