Merge pull request #16375 from mlobiondo-newrelic/mlobiondo/NR-201202…

…-add-millisecond-duration

feat: Add millisecond query time duration

src/content/docs/nrql/using-nrql/query-time-range.mdx

@@ -68,7 +68,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:
 
@@ -88,6 +88,10 @@ The time is relative to the time you run the query. For example, assume that you
  <td>`NOW` (query execution time)</td>
  <td style="font-family:monospace">2023-12-18T12:34:56.789Z</td>
  </tr>
+ <tr>
+ <td>`2 milliseconds ago`</td>
+ <td style="font-family:monospace">2023-12-18T12:34:54.<DoNotTranslate>**.787**</DoNotTranslate>Z</td>
+ </tr>
  <tr>
  <td>`2 seconds ago`</td>
  <td style="font-family:monospace">2023-12-18T12:34:<DoNotTranslate>**54**</DoNotTranslate>.789Z</td>