From dbac8358899dbdbe063de85afe2b6078796e69e8 Mon Sep 17 00:00:00 2001 From: Melissa LoBiondo Date: Fri, 1 Mar 2024 07:40:14 -0600 Subject: [PATCH] feat: Add millisecond query time duration --- src/content/docs/nrql/using-nrql/query-time-range.mdx | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/src/content/docs/nrql/using-nrql/query-time-range.mdx b/src/content/docs/nrql/using-nrql/query-time-range.mdx index 31365948d1d..bc0325036d2 100644 --- a/src/content/docs/nrql/using-nrql/query-time-range.mdx +++ b/src/content/docs/nrql/using-nrql/query-time-range.mdx @@ -71,7 +71,7 @@ These timestamp values resolve to a time range starting at `2023-12-18T11:34:56. ### Relative time (n \[time units] ago) [#relative-time-n-units-ago] Relative time can be referenced as `n [time units] ago` with the following components: * `n`: A positive integer value. - * `[time units]`: Available time units include `seconds`, `minutes`, `hours`, `days`, `weeks`, `months` (defined as 30 days), `quarters` (defined as 91 days), or `years` (defined as 365 days). Time unit pluralization is optional, so you can leave the "s" off the end of the unit. `2 day ago` and `2 days ago` have the same meaning. + * `[time units]`: Available time units include `milliseconds`, `seconds`, `minutes`, `hours`, `days`, `weeks`, `months` (defined as 30 days), `quarters` (defined as 91 days), or `years` (defined as 365 days). Time unit pluralization is optional, so you can leave the "s" off the end of the unit. `2 day ago` and `2 days ago` have the same meaning. The time is relative to the time you run the query. For example, assume that you ran a query at `2023-12-18T12:34:56.789Z`. You would get different results depending on what relative time value you used: @@ -90,6 +90,10 @@ The time is relative to the time you run the query. For example, assume that you + + + +
`NOW` (query execution time) 2023-12-18T12:34:56.789Z
`2 milliseconds ago`2023-12-18T12:34:54.**.787**Z
`2 seconds ago` 2023-12-18T12:34:**54**.789Z