Important
This is a beta feature, and may not work as expected and may be removed from the product without warning
Marks the live query the function is used in as repeating.
A repeating query is a live query that is implemented by making repeated
historical queries. This can be useful when combined with functions not
supported in live queries, such as selfJoin()
,
selfJoinFilter()
, or certain applications of join
when joining on the same repository.
When the query snapshot cache is enabled, the historical queries made by a repeating query will reuse previous results and will therefore not be as much work for LogScale to execute as a regular historical query. When this happens, the update interval will be adjusted to the nearest time-bucket.
This function has no effect if used in a historical query.
This function is in beta and the behavior may change in future versions of LogScale.
The feature RepeatingQueries must be enabled for this function to be
available. This feature can be enabled by making the following GraphQL
mutation as root from the API explorer at
$YOUR_LOGSCALE_URL/docs/api-explorer
:
mutation {
enableFeature(feature: RepeatingQueries)
}
Note
If this feature is disabled, then any alert, dashboard, or saved query
using beta:repeating()
will fail.
Parameter | Type | Required | Default | Description |
---|---|---|---|---|
as | string | optional[a] | description | |
interval [b] | long | optional[a] | The time interval between successive historical queries. The time span is defined as a Relative Time Syntax. If not specified, a default interval is selected. | |
[a] Optional parameters use their default value unless explicitly set. |
Hide omitted argument names for this function
Omitted Argument NamesThe argument name for
interval
can be omitted; the following forms of this function are equivalent:logscalebeta:repeating("value")
and:
logscalebeta:repeating(interval="value")
These examples show basic structure only.