From def4cddfea413d927707655f51a62ef02d23d21f Mon Sep 17 00:00:00 2001 From: Prajwal Tuladhar Date: Tue, 31 Mar 2015 18:19:24 -0400 Subject: [PATCH] fix doc link --- docs/content/Granularities.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/Granularities.md b/docs/content/Granularities.md index c2c6bdbb698..21e793b776e 100644 --- a/docs/content/Granularities.md +++ b/docs/content/Granularities.md @@ -14,7 +14,7 @@ Simple granularities are specified as a string and bucket timestamps by their UT Supported granularity strings are: `all`, `none`, `minute`, `fifteen_minute`, `thirty_minute`, `hour` and `day` * `all` buckets everything into a single bucket -* `none` does not bucket data (it actually uses the granularity of the index - minimum here is `none` which means millisecond granularity). Using `none` in a [TimeSeriesQuery](TimeSeriesQuery.html) is currently not recommended (the system will try to generate 0 values for all milliseconds that didn’t exist, which is often a lot). +* `none` does not bucket data (it actually uses the granularity of the index - minimum here is `none` which means millisecond granularity). Using `none` in a [TimeseriesQuery](TimeSeriesQuery.html) is currently not recommended (the system will try to generate 0 values for all milliseconds that didn’t exist, which is often a lot). ### Duration Granularities