diff --git a/content/influxdb/v1.3/administration/config.md b/content/influxdb/v1.3/administration/config.md index 9be5bdaa0..295fb47e6 100644 --- a/content/influxdb/v1.3/administration/config.md +++ b/content/influxdb/v1.3/administration/config.md @@ -759,7 +759,7 @@ Environment variable: `INFLUXDB_GRAPHITE_PROTOCOL` The number of nodes that must confirm the write. If the requirement is not met the return value will be either `partial write` if some points in the batch fail or `write failure` if all points in the batch fail. -For more information, see the Query String Parameters for Writes section in the [Line Protocol Syntax Reference ](/influxdb/v1.3/write_protocols/write_syntax/). +For more information, see the Query String Parameters for Writes section in the [Line Protocol Syntax Reference ](/influxdb/v1.3/write_protocols/line_protocol_reference/). Environment variable: `INFLUXDB_GRAPHITE_CONSISTENCY_LEVEL` diff --git a/content/influxdb/v1.3/administration/previous_differences.md b/content/influxdb/v1.3/administration/previous_differences.md index d142b488c..9c852beb1 100644 --- a/content/influxdb/v1.3/administration/previous_differences.md +++ b/content/influxdb/v1.3/administration/previous_differences.md @@ -17,25 +17,25 @@ If you're using version 1.2, please see [Differences Between InfluxDB 1.3 and 1. Users looking to upgrade to InfluxDB 1.3 from versions prior to 1.2 should view the following pages in our documentation. ##### 1.1 users: -[Differences Between InfluxDB 1.2 and 1.1](/influxdb/v1.2/administration/differences/) +[Differences Between InfluxDB 1.2 and 1.1](https://archive.docs.influxdata.com/influxdb/v1.2/administration/differences/) ##### 1.0 users: -[Differences Between InfluxDB 1.1 and 1.0](/influxdb/v1.1/administration/differences/) +[Differences Between InfluxDB 1.1 and 1.0](https://archive.docs.influxdata.com/influxdb/v1.1/administration/differences/) ##### 0.13 users: -[Differences Between InfluxDB 1.0 and 0.13](/influxdb/v1.0/administration/013_vs_1/) +[Differences Between InfluxDB 1.0 and 0.13](https://archive.docs.influxdata.com/influxdb/v1.0/administration/013_vs_1/) ##### 0.12 users: -[Differences Between InfluxDB 0.13 and 0.12](/influxdb/v0.13/administration/012_vs_013/) +[Differences Between InfluxDB 0.13 and 0.12](https://archive.docs.influxdata.com/influxdb/v0.13/administration/012_vs_013/) ##### 0.11 users: -[Differences between InfluxDB 0.12 and InfluxDB 0.11](/influxdb/v0.12/concepts/011_vs_012/) +[Differences between InfluxDB 0.12 and InfluxDB 0.11](https://archive.docs.influxdata.com/influxdb/v0.12/concepts/011_vs_012/) ##### 0.10 users: -[Differences between InfluxDB 0.11 and InfluxDB 0.10](/influxdb/v1.3/concepts/010_vs_011/) +[Differences between InfluxDB 0.11 and InfluxDB 0.10](https://archive.docs.influxdata.com/influxdb/v0.11/concepts/010_vs_011/) ##### 0.9 users: -[Differences between InfluxDB 0.9 and InfluxDB 0.10](/influxdb/v0.10/concepts/09_vs_010/) +[Differences between InfluxDB 0.9 and InfluxDB 0.10](https://archive.docs.influxdata.com/influxdb/v0.10/concepts/09_vs_010/) ##### 0.8 users: -[Differences between InfluxDB 0.8 and InfluxDB 0.10](/influxdb/v0.10/concepts/08_vs_010/) +[Differences between InfluxDB 0.8 and InfluxDB 0.10](https://archive.docs.influxdata.com/influxdb/v0.10/concepts/08_vs_010/) diff --git a/content/influxdb/v1.3/concepts/glossary.md b/content/influxdb/v1.3/concepts/glossary.md index 1ef92d640..a40ffe53f 100644 --- a/content/influxdb/v1.3/concepts/glossary.md +++ b/content/influxdb/v1.3/concepts/glossary.md @@ -290,7 +290,7 @@ Related entries: [tag](/influxdb/v1.3/concepts/glossary/#tag), [tag key](/influx The date and time associated with a point. All time in InfluxDB is UTC. -For how to specify time when writing data, see [Write Syntax](/influxdb/v1.3/write_protocols/write_syntax/). +For how to specify time when writing data, see [Write Syntax](/influxdb/v1.3/write_protocols/line_protocol_reference/). For how to specify time when querying data, see [Data Exploration](/influxdb/v1.3/query_language/data_exploration/#time-syntax). Related entries: [point](/influxdb/v1.3/concepts/glossary/#point) diff --git a/content/influxdb/v1.3/guides/writing_data.md b/content/influxdb/v1.3/guides/writing_data.md index f8ddfcef4..695e6bbbd 100644 --- a/content/influxdb/v1.3/guides/writing_data.md +++ b/content/influxdb/v1.3/guides/writing_data.md @@ -7,7 +7,7 @@ menu: parent: Guides --- -There are many ways to write data into InfluxDB including the [command line interface](/influxdb/v1.3/tools/shell/), [client libraries](/influxdb/v1.3/clients/api/) and plugins for common data formats such as [Graphite](/influxdb/v1.3/write_protocols/graphite/). +There are many ways to write data into InfluxDB including the [command line interface](/influxdb/v1.3/tools/shell/), [client libraries](/influxdb/v1.3/tools/api_client_libraries/) and plugins for common data formats such as **Graphite**. Here we'll show you how to create a database and write data to it using the built-in HTTP API. ## Creating a database using the HTTP API @@ -62,7 +62,7 @@ cpu_load_short,direction=in,host=server01,region=us-west value=2.0 1422568543702 ### Writing points from a file --- Write points from a file by passing `@filename` to `curl`. -The data in the file should follow InfluxDB's [line protocol syntax](/influxdb/v1.3/write_protocols/write_syntax/). +The data in the file should follow InfluxDB's [line protocol syntax](/influxdb/v1.3/write_protocols/line_protocol_reference/). Example of a properly-formatted file (`cpu_data.txt`):
diff --git a/content/influxdb/v1.3/introduction/getting_started.md b/content/influxdb/v1.3/introduction/getting_started.md index 59ce64bab..7f3afc782 100644 --- a/content/influxdb/v1.3/introduction/getting_started.md +++ b/content/influxdb/v1.3/introduction/getting_started.md @@ -125,7 +125,7 @@ stock,symbol=AAPL bid=127.46,ask=127.48 temperature,machine=unit42,type=assembly external=25,internal=37 1434067467000000000 ``` -> **Note:** More information on the line protocol can be found on the [Write Syntax](/influxdb/v1.3/write_protocols/write_syntax/) page. +> **Note:** More information on the line protocol can be found on the [Write Syntax](/influxdb/v1.3/write_protocols/line_protocol_reference/) page. To insert a single time-series datapoint into InfluxDB using the CLI, enter `INSERT` followed by a point: diff --git a/content/influxdb/v1.4/administration/config.md b/content/influxdb/v1.4/administration/config.md index c93dc74d8..e8012781f 100644 --- a/content/influxdb/v1.4/administration/config.md +++ b/content/influxdb/v1.4/administration/config.md @@ -656,7 +656,7 @@ Environment variable: `INFLUXDB_GRAPHITE_PROTOCOL` The number of nodes that must confirm the write. If the requirement is not met the return value will be either `partial write` if some points in the batch fail or `write failure` if all points in the batch fail. -For more information, see the Query String Parameters for Writes section in the [Line Protocol Syntax Reference ](/influxdb/v1.4/write_protocols/write_syntax/). +For more information, see the Query String Parameters for Writes section in the [Line Protocol Syntax Reference ](/influxdb/v1.4/write_protocols/line_protocol_reference/). Environment variable: `INFLUXDB_GRAPHITE_CONSISTENCY_LEVEL` diff --git a/content/influxdb/v1.4/concepts/glossary.md b/content/influxdb/v1.4/concepts/glossary.md index 19427e7f8..61890154a 100644 --- a/content/influxdb/v1.4/concepts/glossary.md +++ b/content/influxdb/v1.4/concepts/glossary.md @@ -290,7 +290,7 @@ Related entries: [tag](/influxdb/v1.4/concepts/glossary/#tag), [tag key](/influx The date and time associated with a point. All time in InfluxDB is UTC. -For how to specify time when writing data, see [Write Syntax](/influxdb/v1.4/write_protocols/write_syntax/). +For how to specify time when writing data, see [Write Syntax](/influxdb/v1.4/write_protocols/line_protocol_reference/). For how to specify time when querying data, see [Data Exploration](/influxdb/v1.4/query_language/data_exploration/#time-syntax). Related entries: [point](/influxdb/v1.4/concepts/glossary/#point) diff --git a/content/influxdb/v1.4/guides/writing_data.md b/content/influxdb/v1.4/guides/writing_data.md index 062e53760..f61c44cd5 100644 --- a/content/influxdb/v1.4/guides/writing_data.md +++ b/content/influxdb/v1.4/guides/writing_data.md @@ -7,7 +7,7 @@ menu: parent: Guides --- -There are many ways to write data into InfluxDB including the [command line interface](/influxdb/v1.4/tools/shell/), [client libraries](/influxdb/v1.4/clients/api/) and plugins for common data formats such as [Graphite](https://github.com/influxdata/influxdb/blob/master/services/graphite/README.md). +There are many ways to write data into InfluxDB including the [command line interface](/influxdb/v1.4/tools/shell/), [client libraries](/influxdb/v1.4/tools/api_client_libraries/) and plugins for common data formats such as [Graphite](https://github.com/influxdata/influxdb/blob/master/services/graphite/README.md). Here we'll show you how to create a database and write data to it using the built-in HTTP API. ## Creating a database using the HTTP API @@ -62,7 +62,7 @@ cpu_load_short,direction=in,host=server01,region=us-west value=2.0 1422568543702 ### Writing points from a file --- Write points from a file by passing `@filename` to `curl`. -The data in the file should follow InfluxDB's [line protocol syntax](/influxdb/v1.4/write_protocols/write_syntax/). +The data in the file should follow InfluxDB's [line protocol syntax](/influxdb/v1.4/write_protocols/line_protocol_reference/). Example of a properly-formatted file (`cpu_data.txt`):
diff --git a/content/influxdb/v1.5/administration/config.md b/content/influxdb/v1.5/administration/config.md index 2b22b7b37..6f6151c80 100644 --- a/content/influxdb/v1.5/administration/config.md +++ b/content/influxdb/v1.5/administration/config.md @@ -717,7 +717,7 @@ Environment variable: `INFLUXDB_GRAPHITE_PROTOCOL` The number of nodes that must confirm the write. If the requirement is not met the return value will be either `partial write` if some points in the batch fail or `write failure` if all points in the batch fail. -For more information, see the Query String Parameters for Writes section in the [Line Protocol Syntax Reference ](/influxdb/v1.5/write_protocols/write_syntax/). +For more information, see the Query String Parameters for Writes section in the [Line Protocol Syntax Reference ](/influxdb/v1.5/write_protocols/line_protocol_reference/). Environment variable: `INFLUXDB_GRAPHITE_CONSISTENCY_LEVEL` diff --git a/content/influxdb/v1.5/administration/upgrading.md b/content/influxdb/v1.5/administration/upgrading.md index 5280e4a59..0976c7cdc 100644 --- a/content/influxdb/v1.5/administration/upgrading.md +++ b/content/influxdb/v1.5/administration/upgrading.md @@ -8,9 +8,9 @@ menu: parent: Administration --- -* [Upgrading from 1.3 / 1.4 (no TSI Preview) to 1.5.x (TSI enabled)](#upgrading-from-13-14-no-tsi-preview-to-15-tsi-enabled) -* [Upgrading from 1.4 (TSI Preview enabled) to 1.5.x (TSI enabled)](#upgrading-from-13-14-tsi-preview-enabled-to-15-tsi-enabled) -* [Upgrading from 1.3 to 1.5.x (TSI enabled)](#upgrading-from-13-to-15-tsi-enabled) +* [Upgrading from 1.3 / 1.4 (no TSI Preview) to 1.5.x (TSI enabled)](#upgrading-from-1-3-1-4-no-tsi-preview-to-1-5-x-tsi-enabled) +* [Upgrading from 1.4 (TSI Preview enabled) to 1.5.x (TSI enabled)](#upgrading-influxdb-1-3-1-4-tsi-preview-enabled-to-1-5-x-tsi-enabled) +* [Upgrading from 1.0-1.4 to 1.5.x (TSI enabled)](#upgrading-influxdb-1-0-1-4-to-1-5-x) * [Upgrading InfluxDB Enterprise clusters](#upgrading-influxdb-enterprise-clusters) ## Upgrading from 1.3 / 1.4 (no TSI Preview) to 1.5.x (TSI enabled) @@ -48,7 +48,7 @@ Follow these steps to upgrade an earlier InfluxDB instance (versions 1.0 to 1.4) 4. Convert existing TSM-based shards to TSI-supported shards. - - Use [influx_inspect buildtsi](/influxdb/v1.5/tools/influx_inspect/#influx-inspect-buildtsi) for converting your TSM-based shards to TSI-based shards. + - Use [influx_inspect buildtsi](/influxdb/v1.5/tools/influx_inspect/#buildtsi) for converting your TSM-based shards to TSI-based shards. 5. Restart the `influxdb` service. @@ -82,7 +82,7 @@ Follow these steps to upgrade an earlier InfluxDB instance (versions 1.3 and 1.4 5. Convert existing shards to support TSI. - When Time Series Index (TSI) is enabled, new shards use the TSI index. Existing shards must be converted to support TSI. - - Run the [influx_inspect buildtsi](/influxdb/v1.5/tools/influx_inspect/#influx-inspect-buildtsi) command to convert existing TSM-based shards to TSI-based shards. + - Run the [influx_inspect buildtsi](/influxdb/v1.5/tools/influx_inspect/#buildtsi) command to convert existing TSM-based shards to TSI-based shards. 5. Restart the `influxdb` service. diff --git a/content/influxdb/v1.5/concepts/glossary.md b/content/influxdb/v1.5/concepts/glossary.md index bcdfa9539..7a1fdf1be 100644 --- a/content/influxdb/v1.5/concepts/glossary.md +++ b/content/influxdb/v1.5/concepts/glossary.md @@ -290,7 +290,7 @@ Related entries: [tag](/influxdb/v1.5/concepts/glossary/#tag), [tag key](/influx The date and time associated with a point. All time in InfluxDB is UTC. -For how to specify time when writing data, see [Write Syntax](/influxdb/v1.5/write_protocols/write_syntax/). +For how to specify time when writing data, see [Write Syntax](/influxdb/v1.5/write_protocols/line_protocol_reference/). For how to specify time when querying data, see [Data Exploration](/influxdb/v1.5/query_language/data_exploration/#time-syntax). Related entries: [point](/influxdb/v1.5/concepts/glossary/#point) diff --git a/content/influxdb/v1.5/concepts/schema_and_data_layout.md b/content/influxdb/v1.5/concepts/schema_and_data_layout.md index 6526b2026..1784b3b9f 100644 --- a/content/influxdb/v1.5/concepts/schema_and_data_layout.md +++ b/content/influxdb/v1.5/concepts/schema_and_data_layout.md @@ -55,8 +55,6 @@ In no particular order, we recommend that you: [Tags](/influxdb/v1.5/concepts/glossary/#tag) containing highly variable information like UUIDs, hashes, and random strings will lead to a large number of series in the database, known colloquially as high series cardinality. High series cardinality is a primary driver of high memory usage for many database workloads. -See [Hardware sizing guidelines](/influxdb/v1.5/guides/hardware_sizing/#general-hardware-guidelines-for-a-single-node) for [series cardinality](/influxdb/v1.5/concepts/glossary/#series-cardinality) recommendations based on your hardware. If the system has memory constraints, consider storing high-cardinality data as a field rather than a tag. - ### *Don't encode data in measurement names* In general, taking this step will simplify your queries. @@ -141,7 +139,7 @@ InfluxDB stores data in shard groups. Shard groups are organized by [retention policy](/influxdb/v1.5/concepts/glossary/#retention-policy-rp) (RP) and store data with timestamps that fall within a specific time interval. The length of that time interval is called the [shard group duration](/influxdb/v1.5/concepts/glossary/#shard-duration). -If no shard group duration is provided, the shard group duration is determined by the RP's [duration](/influxdb/v1.5/concepts/glossary/#duration) at the time the RP is created. The default values are: +If no shard group duration is provided, the shard group duration is determined by the RP's [duration](/influxdb/v1.5/concepts/glossary/#duration) at the time the RP is created. The default values are: | RP Duration | Shard Group Duration | |---|---| diff --git a/content/influxdb/v1.5/concepts/tsi-details.md b/content/influxdb/v1.5/concepts/tsi-details.md index 49443e692..2810a77ed 100644 --- a/content/influxdb/v1.5/concepts/tsi-details.md +++ b/content/influxdb/v1.5/concepts/tsi-details.md @@ -29,7 +29,7 @@ If you are troubleshooting an issue with an index, you can use the `influx_inspe This command allows you to print summary statistics on an index, file, or a set of files. This command only works on one index at a time. -For details on this command, see [influx_inspect dumptsi](/influxdb/v1.5/tools/influx_inspect/#influx-inspect-dumptsi). +For details on this command, see [influx_inspect dumptsi](/influxdb/v1.5/tools/influx_inspect/#dumptsi). ### `influx_inspect buildtsi` @@ -38,7 +38,7 @@ If you have an existing TSI index that you want to rebuild, first delete the `in This command works at the server-level but you can optionally add database, retention policy and shard filters to only apply to a subset of shards. -For details on this command, see [influx inspect buildtsi](/influxdb/v1.5/tools/influx_inspect/#influx-inspect-buildtsi). +For details on this command, see [influx inspect buildtsi](/influxdb/v1.5/tools/influx_inspect/#buildtsi). ## Understanding TSI diff --git a/content/influxdb/v1.5/guides/writing_data.md b/content/influxdb/v1.5/guides/writing_data.md index 30617fd33..349e0d139 100644 --- a/content/influxdb/v1.5/guides/writing_data.md +++ b/content/influxdb/v1.5/guides/writing_data.md @@ -7,7 +7,7 @@ menu: parent: Guides --- -There are many ways to write data into InfluxDB including the [command line interface](/influxdb/v1.5/tools/shell/), [client libraries](/influxdb/v1.5/clients/api/) and plugins for common data formats such as [Graphite](/influxdb/v1.5/write_protocols/graphite/). +There are many ways to write data into InfluxDB including the [command line interface](/influxdb/v1.5/tools/shell/), [client libraries](/influxdb/v1.5/tools/api_client_libraries/) and plugins for common data formats such as [Graphite](/influxdb/v1.5/write_protocols/graphite/). Here we'll show you how to create a database and write data to it using the built-in HTTP API. ## Creating a database using the HTTP API @@ -62,7 +62,7 @@ cpu_load_short,direction=in,host=server01,region=us-west value=2.0 1422568543702 ### Writing points from a file --- Write points from a file by passing `@filename` to `curl`. -The data in the file should follow InfluxDB's [line protocol syntax](/influxdb/v1.5/write_protocols/write_syntax/). +The data in the file should follow InfluxDB's [line protocol syntax](/influxdb/v1.5/write_protocols/line_protocol_reference/). Example of a properly-formatted file (`cpu_data.txt`):
diff --git a/content/influxdb/v1.5/introduction/getting-started.md b/content/influxdb/v1.5/introduction/getting-started.md index 7bbc8f588..a38338ee7 100644 --- a/content/influxdb/v1.5/introduction/getting-started.md +++ b/content/influxdb/v1.5/introduction/getting-started.md @@ -37,7 +37,7 @@ InfluxDB shell 1.4.x * The InfluxDB HTTP API runs on port `8086` by default. Therefore, `influx` will connect to port `8086` and `localhost` by default. If you need to alter these defaults, run `influx --help`. -* The [`-precision` argument](/influxdb/v1.5/tools/shell/#influx-arguments) specifies the format/precision of any returned timestamps. +* The [`-precision` argument](/influxdb/v1.5/tools/shell/#precision-rfc3339-h-m-s-ms-u-ns) specifies the format/precision of any returned timestamps. In the example above, `rfc3339` tells InfluxDB to return timestamps in [RFC3339 format](https://www.ietf.org/rfc/rfc3339.txt) (`YYYY-MM-DDTHH:MM:SS.nnnnnnnnnZ`). The command line is now ready to take input in the form of the Influx Query Language (a.k.a InfluxQL) statements. diff --git a/content/influxdb/v1.5/query_language/data_download.md b/content/influxdb/v1.5/query_language/data_download.md index dfde44c48..852f09063 100644 --- a/content/influxdb/v1.5/query_language/data_download.md +++ b/content/influxdb/v1.5/query_language/data_download.md @@ -32,7 +32,7 @@ InfluxDB shell 1.4.x * The InfluxDB HTTP API runs on port `8086` by default. Therefore, `influx` will connect to port `8086` and `localhost` by default. If you need to alter these defaults, run `influx --help`. -* The [`-precision` argument](/influxdb/v1.5/tools/shell/#influx-arguments) specifies the format/precision of any returned timestamps. +* The [`-precision` argument](/influxdb/v1.5/tools/shell/#precision-rfc3339-h-m-s-ms-u-ns) specifies the format/precision of any returned timestamps. In the example above, `rfc3339` tells InfluxDB to return timestamps in [RFC3339 format](https://www.ietf.org/rfc/rfc3339.txt) (`YYYY-MM-DDTHH:MM:SS.nnnnnnnnnZ`). The command line is now ready to take input in the form of the Influx Query Language (a.k.a InfluxQL) statements. diff --git a/content/influxdb/v1.5/query_language/data_exploration.md b/content/influxdb/v1.5/query_language/data_exploration.md index 28142200e..dac3ec301 100644 --- a/content/influxdb/v1.5/query_language/data_exploration.md +++ b/content/influxdb/v1.5/query_language/data_exploration.md @@ -2724,7 +2724,7 @@ the lower bound to `now()` such that the query's time range is between The [CLI](/influxdb/v1.5/tools/shell/) returns timestamps in nanosecond epoch format by default. Specify alternative formats with the -[`precision ` command](/influxdb/v1.5/tools/shell/#influx-commands). +[`precision ` command](/influxdb/v1.5/tools/shell/#commands). The [HTTP API](/influxdb/v1.5/tools/api/) returns timestamps in [RFC3339](https://www.ietf.org/rfc/rfc3339.txt) format by default. Specify alternative formats with the diff --git a/content/influxdb/v1.5/query_language/spec.md b/content/influxdb/v1.5/query_language/spec.md index 1151eeff1..ef9da1129 100644 --- a/content/influxdb/v1.5/query_language/spec.md +++ b/content/influxdb/v1.5/query_language/spec.md @@ -613,7 +613,7 @@ SIZE OF BLOCKS: 931 ### EXPLAIN ANALYZE -Executes the specified SELECT statement and returns data on the query performance and storage during runtime, visualized as a tree. Use this statement to analyze query performance and storage, including [execution time](#execution_time) and [planning time](#planning_time), and the [iterator type](#iterator-type) and [cursor type](#cursor-type). +Executes the specified SELECT statement and returns data on the query performance and storage during runtime, visualized as a tree. Use this statement to analyze query performance and storage, including [execution time](#execution-time) and [planning time](#planning-time), and the [iterator type](#iterator-type) and [cursor type](#cursor-type). For example, executing the following statement: @@ -972,7 +972,6 @@ Estimates or counts exactly the cardinality of the series for the current databa [Series cardinality](/influxdb/v1.5/concepts/glossary/#series-cardinality) is the major factor that affects RAM requirements. For more information, see: -- [When do I need more RAM?](/influxdb/v1.5/guides/hardware_sizing/#when-do-i-need-more-ram) in [Hardware Sizing Guidelines](/influxdb/v1.5/guides/hardware_sizing/) - [Don't have too many series](/influxdb/v1.5/concepts/schema_and_data_layout/#don-t-have-too-many-series) > **Note:** `ON `, `FROM `, `WITH KEY = `, `WHERE `, `GROUP BY `, and `LIMIT/OFFSET` clauses are optional. diff --git a/content/influxdb/v1.5/supported_protocols/collectd.md b/content/influxdb/v1.5/supported_protocols/collectd.md index 4fc1173bb..40b786ea8 100644 --- a/content/influxdb/v1.5/supported_protocols/collectd.md +++ b/content/influxdb/v1.5/supported_protocols/collectd.md @@ -15,7 +15,7 @@ The [collectd](https://collectd.org) input allows InfluxDB to accept data transm ## A note on UDP/IP buffer sizes -If you're running Linux or FreeBSD, please adjust your operating system UDP buffer size limit, [see here for more details.](/influxdb/v1.5/supported_protocols/udp/#a-note-on-udpip-os-buffer-sizes) +If you're running Linux or FreeBSD, please adjust your operating system UDP buffer size limit, [see here for more details.](/influxdb/v1.5/supported_protocols/udp/#a-note-on-udp-ip-os-buffer-sizes) ## Configuration diff --git a/content/influxdb/v1.5/tools/_index.md b/content/influxdb/v1.5/tools/_index.md index 2debcb346..4ed296ae9 100644 --- a/content/influxdb/v1.5/tools/_index.md +++ b/content/influxdb/v1.5/tools/_index.md @@ -23,7 +23,7 @@ and view query output in different formats: Go straight to the documentation on: -* [Launching `influx`](/influxdb/v1.5/tools/shell/#launch-influx) +* [Launching `influx`](/influxdb/v1.5/tools/shell/#using-influx) * [Writing data with `influx`](/influxdb/v1.5/tools/shell/#write-data-to-influxdb-with-insert) ## [InfluxDB HTTP API Reference](/influxdb/v1.5/tools/api/) diff --git a/content/influxdb/v1.5/tools/influx_inspect.md b/content/influxdb/v1.5/tools/influx_inspect.md index 7e4ab0add..99535774b 100644 --- a/content/influxdb/v1.5/tools/influx_inspect.md +++ b/content/influxdb/v1.5/tools/influx_inspect.md @@ -32,7 +32,6 @@ The `influx_inspect` commands are summarized here, with links to detailed inform * [`dumptsi`](#dumptsi): Dump low-level details about TSI files. * [`dumptsm`](#dumptsm): Dump low-level details about TSM files. * [`export`](#export): Export raw data from a shard in Line Protocol format. -* [`help`](#help): Display this help message format. * [`report`](#report): Display a shard level report. * [`verify`](#verify): Verify the integrity of TSM files. @@ -112,7 +111,9 @@ $ influx_inspect buildtsi -database stress -shard 1 -datadir ~/.influxdb/data -w Bulk deletes a measurement from a raw TSM file. -{{% warn %}} **Warning:** Use the `deletetsm` command only when your InfluxDB instance is offline (`influxd` service is not running).{{% /warn %}} +{{% warn %}} +**Warning:** Use the `deletetsm` command only when your InfluxDB instance is offline (`influxd` service is not running). +{{% /warn %}} #### Syntax diff --git a/content/influxdb/v1.5/tools/shell.md b/content/influxdb/v1.5/tools/shell.md index 1fa1c1264..39ac4b1c6 100644 --- a/content/influxdb/v1.5/tools/shell.md +++ b/content/influxdb/v1.5/tools/shell.md @@ -12,7 +12,7 @@ The InfluxDB command line interface utility (`influx`) is an interactive shell f Use `influx` to write data (manually or from a file), query data interactively, and view query output in different formats. * [Using `influx`](/influxdb/v1.5/tools/shell/#using-influx) -* [Arguments](/influxdb/v1.5/tools/shell/#arguments) +* [Arguments](#global-options) * [Commands](/influxdb/v1.5/tools/shell/#commands) ### Using `influx` diff --git a/content/influxdb/v1.5/write_protocols/line_protocol_tutorial.md b/content/influxdb/v1.5/write_protocols/line_protocol_tutorial.md index 513a27d33..7c5a7815e 100644 --- a/content/influxdb/v1.5/write_protocols/line_protocol_tutorial.md +++ b/content/influxdb/v1.5/write_protocols/line_protocol_tutorial.md @@ -455,7 +455,7 @@ and more examples, see the [API Reference](/influxdb/v1.5/tools/api/#write). #### CLI Write data to InfluxDB using InfluxDB's Command Line Interface (CLI). -[Launch](/influxdb/v1.5/tools/shell/#launch-influx) the CLI, use the relevant +[Launch](/influxdb/v1.5/tools/shell/#using-influx) the CLI, use the relevant database, and put `INSERT` in front of your Line Protocol: @@ -474,7 +474,7 @@ on the [HTTP API](/influxdb/v1.5/tools/api/#write), the [UDP](/influxdb/v1.5/tools/udp/), [Graphite](/influxdb/v1.5/tools/graphite/), [CollectD](/influxdb/v1.5/tools/collectd/), and -[OpenTSDB](/influxdb/v1.5/tools/opentsdb/)). +[OpenTSDB](/influxdb/v1.5/supported_protocols/opentsdb/)). ### Duplicate points diff --git a/content/influxdb/v1.6/administration/config.md b/content/influxdb/v1.6/administration/config.md index 2ec31fbe2..883312e1d 100644 --- a/content/influxdb/v1.6/administration/config.md +++ b/content/influxdb/v1.6/administration/config.md @@ -744,7 +744,7 @@ Environment variable: `INFLUXDB_GRAPHITE_PROTOCOL` The number of nodes that must confirm the write. If the requirement is not met the return value will be either `partial write` if some points in the batch fail or `write failure` if all points in the batch fail. -For more information, see the Query String Parameters for Writes section in the [Line Protocol Syntax Reference ](/influxdb/v1.6/write_protocols/write_syntax/). +For more information, see the Query String Parameters for Writes section in the [Line Protocol Syntax Reference ](/influxdb/v1.6/write_protocols/line_protocol_reference/). Environment variable: `INFLUXDB_GRAPHITE_CONSISTENCY_LEVEL` diff --git a/content/influxdb/v1.6/concepts/glossary.md b/content/influxdb/v1.6/concepts/glossary.md index f9fc23b36..39bba2f39 100644 --- a/content/influxdb/v1.6/concepts/glossary.md +++ b/content/influxdb/v1.6/concepts/glossary.md @@ -290,7 +290,7 @@ Related entries: [tag](/influxdb/v1.6/concepts/glossary/#tag), [tag key](/influx The date and time associated with a point. All time in InfluxDB is UTC. -For how to specify time when writing data, see [Write Syntax](/influxdb/v1.6/write_protocols/write_syntax/). +For how to specify time when writing data, see [Write Syntax](/influxdb/v1.6/write_protocols/line_protocol_reference/). For how to specify time when querying data, see [Data Exploration](/influxdb/v1.6/query_language/data_exploration/#time-syntax). Related entries: [point](/influxdb/v1.6/concepts/glossary/#point) diff --git a/content/influxdb/v1.6/concepts/schema_and_data_layout.md b/content/influxdb/v1.6/concepts/schema_and_data_layout.md index 64fb22ad6..f8b430a3a 100644 --- a/content/influxdb/v1.6/concepts/schema_and_data_layout.md +++ b/content/influxdb/v1.6/concepts/schema_and_data_layout.md @@ -55,8 +55,6 @@ In no particular order, we recommend that you: [Tags](/influxdb/v1.6/concepts/glossary/#tag) containing highly variable information like UUIDs, hashes, and random strings will lead to a large number of series in the database, known colloquially as high series cardinality. High series cardinality is a primary driver of high memory usage for many database workloads. -See [Hardware sizing guidelines](/influxdb/v1.6/guides/hardware_sizing/#general-hardware-guidelines-for-a-single-node) for [series cardinality](/influxdb/v1.6/concepts/glossary/#series-cardinality) recommendations based on your hardware. If the system has memory constraints, consider storing high-cardinality data as a field rather than a tag. - ### *Don't encode data in measurement names* In general, taking this step will simplify your queries. @@ -141,7 +139,7 @@ InfluxDB stores data in shard groups. Shard groups are organized by [retention policy](/influxdb/v1.6/concepts/glossary/#retention-policy-rp) (RP) and store data with timestamps that fall within a specific time interval. The length of that time interval is called the [shard group duration](/influxdb/v1.6/concepts/glossary/#shard-duration). -If no shard group duration is provided, the shard group duration is determined by the RP's [duration](/influxdb/v1.6/concepts/glossary/#duration) at the time the RP is created. The default values are: +If no shard group duration is provided, the shard group duration is determined by the RP's [duration](/influxdb/v1.6/concepts/glossary/#duration) at the time the RP is created. The default values are: | RP Duration | Shard Group Duration | |---|---| diff --git a/content/influxdb/v1.6/guides/_index.md b/content/influxdb/v1.6/guides/_index.md index 764dee932..8f88c881c 100644 --- a/content/influxdb/v1.6/guides/_index.md +++ b/content/influxdb/v1.6/guides/_index.md @@ -7,10 +7,4 @@ menu: --- -## [Writing data with the HTTP API](/influxdb/v1.6/guides/writing_data/) - -## [Querying data with the HTTP API](/influxdb/v1.6/guides/querying_data/) - -## [Downsampling and data retention](/influxdb/v1.6/guides/downsampling_and_retention/) - -## [Hardware sizing guidelines](/influxdb/v1.6/guides/hardware_sizing/) +{{< children >}} diff --git a/content/influxdb/v1.6/guides/writing_data.md b/content/influxdb/v1.6/guides/writing_data.md index 91ad89e14..b5a491fd3 100644 --- a/content/influxdb/v1.6/guides/writing_data.md +++ b/content/influxdb/v1.6/guides/writing_data.md @@ -7,7 +7,7 @@ menu: parent: Guides --- -There are many ways to write data into InfluxDB including the [command line interface](/influxdb/v1.6/tools/shell/), [client libraries](/influxdb/v1.6/clients/api/) and plugins for common data formats such as [Graphite](/influxdb/v1.6/write_protocols/graphite/). +There are many ways to write data into InfluxDB including the [command line interface](/influxdb/v1.6/tools/shell/), [client libraries](/influxdb/v1.6/tools/api_client_libraries/) and plugins for common data formats such as [Graphite](/influxdb/v1.6/write_protocols/graphite/). Here we'll show you how to create a database and write data to it using the built-in HTTP API. ## Creating a database using the HTTP API @@ -62,7 +62,7 @@ cpu_load_short,direction=in,host=server01,region=us-west value=2.0 1422568543702 ### Writing points from a file --- Write points from a file by passing `@filename` to `curl`. -The data in the file should follow InfluxDB's [line protocol syntax](/influxdb/v1.6/write_protocols/write_syntax/). +The data in the file should follow InfluxDB's [line protocol syntax](/influxdb/v1.6/write_protocols/line_protocol_reference/). Example of a properly-formatted file (`cpu_data.txt`):
diff --git a/content/influxdb/v1.6/query_language/spec.md b/content/influxdb/v1.6/query_language/spec.md index 81712e6de..7f63ed7e1 100644 --- a/content/influxdb/v1.6/query_language/spec.md +++ b/content/influxdb/v1.6/query_language/spec.md @@ -614,7 +614,7 @@ SIZE OF BLOCKS: 931 ### EXPLAIN ANALYZE -Executes the specified SELECT statement and returns data on the query performance and storage during runtime, visualized as a tree. Use this statement to analyze query performance and storage, including [execution time](#execution_time) and [planning time](#planning_time), and the [iterator type](#iterator-type) and [cursor type](#cursor-type). +Executes the specified SELECT statement and returns data on the query performance and storage during runtime, visualized as a tree. Use this statement to analyze query performance and storage, including [execution time](#execution-time) and [planning time](#planning-time), and the [iterator type](#iterator-type) and [cursor type](#cursor-type). For example, executing the following statement: @@ -837,7 +837,7 @@ SHOW DATABASES ### SHOW DIAGNOSTICS -Displays node information, such as build information, uptime, hostname, server configuration, memory usage, and Go runtime diagnostics. +Displays node information, such as build information, uptime, hostname, server configuration, memory usage, and Go runtime diagnostics. For more information on using the `SHOW DIAGNOSTICS` command, see [Using the SHOW DIAGNOSTICS command for monitoring InfluxDB](/platform/monitoring/influxdata-platform/tools/show-diagnostics/). @@ -984,7 +984,6 @@ Estimates or counts exactly the cardinality of the series for the current databa [Series cardinality](/influxdb/v1.6/concepts/glossary/#series-cardinality) is the major factor that affects RAM requirements. For more information, see: -- [When do I need more RAM?](/influxdb/v1.6/guides/hardware_sizing/#when-do-i-need-more-ram) in [Hardware Sizing Guidelines](/influxdb/v1.6/guides/hardware_sizing/) - [Don't have too many series](/influxdb/v1.6/concepts/schema_and_data_layout/#don-t-have-too-many-series) > **Note:** `ON `, `FROM `, `WITH KEY = `, `WHERE `, `GROUP BY `, and `LIMIT/OFFSET` clauses are optional. diff --git a/content/influxdb/v1.6/supported_protocols/collectd.md b/content/influxdb/v1.6/supported_protocols/collectd.md index e826fb867..a2f7c0b3e 100644 --- a/content/influxdb/v1.6/supported_protocols/collectd.md +++ b/content/influxdb/v1.6/supported_protocols/collectd.md @@ -15,7 +15,7 @@ The [collectd](https://collectd.org) input allows InfluxDB to accept data transm ## A note on UDP/IP buffer sizes -If you're running Linux or FreeBSD, please adjust your operating system UDP buffer size limit, [see here for more details.](/influxdb/v1.6/supported_protocols/udp/#a-note-on-udpip-os-buffer-sizes) +If you're running Linux or FreeBSD, please adjust your operating system UDP buffer size limit, [see here for more details.](/influxdb/v1.6/supported_protocols/udp/#a-note-on-udp-ip-os-buffer-sizes) ## Configuration diff --git a/content/influxdb/v1.6/write_protocols/line_protocol_tutorial.md b/content/influxdb/v1.6/write_protocols/line_protocol_tutorial.md index d54e14a51..f40a11e07 100644 --- a/content/influxdb/v1.6/write_protocols/line_protocol_tutorial.md +++ b/content/influxdb/v1.6/write_protocols/line_protocol_tutorial.md @@ -474,7 +474,7 @@ on the [HTTP API](/influxdb/v1.6/tools/api/#write-http-endpoint), the [UDP](/influxdb/v1.6/tools/udp/), [Graphite](/influxdb/v1.6/tools/graphite/), [CollectD](/influxdb/v1.6/tools/collectd/), and -[OpenTSDB](/influxdb/v1.6/tools/opentsdb/)). +[OpenTSDB](/influxdb/v1.6/supported_protocols/opentsdb/)). ### Duplicate points diff --git a/content/influxdb/v1.7/about_the_project/releasenotes-changelog.md b/content/influxdb/v1.7/about_the_project/releasenotes-changelog.md index 147d752f2..58b636049 100644 --- a/content/influxdb/v1.7/about_the_project/releasenotes-changelog.md +++ b/content/influxdb/v1.7/about_the_project/releasenotes-changelog.md @@ -197,7 +197,7 @@ Chunked query was added into the Go client v2 interface. If you compiled against Support for the Flux language and queries has been added in this release. To begin exploring Flux 0.7 (technical preview): * Enable Flux using the new configuration setting [`[http] flux-enabled = true`](/influxdb/v1.7/administration/config/#flux-enabled-false). -* Use the new [`influx -type=flux`](/influxdb/v1.7/tools/shell/#type) option to enable the Flux REPL shell for creating Flux queries. +* Use the new [`influx -type=flux`](/influxdb/v1.7/tools/shell/) option to enable the Flux REPL shell for creating Flux queries. * Read about Flux and the Flux language, enabling Flux, or jump into the getting started and other guides. #### Time Series Index (TSI) query performance and throughputs improvements diff --git a/content/influxdb/v1.7/administration/_index.md b/content/influxdb/v1.7/administration/_index.md index df5e09e3a..3f75fcb42 100644 --- a/content/influxdb/v1.7/administration/_index.md +++ b/content/influxdb/v1.7/administration/_index.md @@ -51,6 +51,6 @@ Management of breaking changes, upgrades, and ongoing support. ## Downgrading -To revert to a prior version, complete the same steps as when [Upgrading to InfluxDB 1.7.x](/influxdb/v1.7/administration/upgrading/), replacing 1.7.x with the version you want to downgrade to. After downloading the release, migrating your configuration settings, and enabling TSI or TSM, make sure to [rebuild your index](/influxdb/v1.7/administration/rebuild-tsi-index/#sidebar). +To revert to a prior version, complete the same steps as when [Upgrading to InfluxDB 1.7.x](/influxdb/v1.7/administration/upgrading/), replacing 1.7.x with the version you want to downgrade to. After downloading the release, migrating your configuration settings, and enabling TSI or TSM, make sure to [rebuild your index](/influxdb/v1.7/administration/rebuild-tsi-index/). >**Note:** Some versions of InfluxDB may have breaking changes that impact your ability to upgrade and downgrade. For example, you cannot downgrade from InfluxDB 1.3 or later to an earlier version. Please review the applicable version of release notes to check for compatibility issues between releases. diff --git a/content/influxdb/v1.7/administration/upgrading.md b/content/influxdb/v1.7/administration/upgrading.md index 46e537b6e..ea2151f25 100644 --- a/content/influxdb/v1.7/administration/upgrading.md +++ b/content/influxdb/v1.7/administration/upgrading.md @@ -51,7 +51,7 @@ Switch index types at any time by doing one of the following: ## Downgrade InfluxDB To downgrade to an earlier version, complete the procedures above in [Upgrade to InfluxDB 1.7.x](#upgrade-to-influxdb-1-7-x), replacing the version numbers with the version that you want to downgrade to. -After downloading the release, migrating your configuration settings, and enabling TSI or TSM, make sure to [rebuild your index](/influxdb/v1.7/administration/rebuild-tsi-index/#sidebar). +After downloading the release, migrating your configuration settings, and enabling TSI or TSM, make sure to [rebuild your index](/influxdb/v1.7/administration/rebuild-tsi-index/). >**Note:** Some versions of InfluxDB may have breaking changes that impact your ability to upgrade and downgrade. For example, you cannot downgrade from InfluxDB 1.3 or later to an earlier version. Please review the applicable version of release notes to check for compatibility issues between releases. diff --git a/content/influxdb/v1.7/concepts/schema_and_data_layout.md b/content/influxdb/v1.7/concepts/schema_and_data_layout.md index bd1e53edc..f982e4784 100644 --- a/content/influxdb/v1.7/concepts/schema_and_data_layout.md +++ b/content/influxdb/v1.7/concepts/schema_and_data_layout.md @@ -55,7 +55,7 @@ In no particular order, we recommend that you: [Tags](/influxdb/v1.7/concepts/glossary/#tag) containing highly variable information like UUIDs, hashes, and random strings will lead to a large number of series in the database, known colloquially as high series cardinality. High series cardinality is a primary driver of high memory usage for many database workloads. -See [Hardware sizing guidelines](/influxdb/v1.7/guides/hardware_sizing/#general-hardware-guidelines-for-a-single-node) for [series cardinality](/influxdb/v1.7/concepts/glossary/#series-cardinality) recommendations based on your hardware. If the system has memory constraints, consider storing high-cardinality data as a field rather than a tag. +See [Hardware sizing guidelines](/influxdb/v1.7/guides/hardware_sizing/) for [series cardinality](/influxdb/v1.7/concepts/glossary/#series-cardinality) recommendations based on your hardware. If the system has memory constraints, consider storing high-cardinality data as a field rather than a tag. ### Don't use the same name for a tag and a field diff --git a/content/influxdb/v1.7/flux/flux-vs-influxql.md b/content/influxdb/v1.7/flux/flux-vs-influxql.md index 6c7bcd51a..3a3dee33e 100644 --- a/content/influxdb/v1.7/flux/flux-vs-influxql.md +++ b/content/influxdb/v1.7/flux/flux-vs-influxql.md @@ -322,7 +322,7 @@ _For a complete list of Flux functions, [view all Flux functions](/{{< latest "i | [SHOW SERIES](/influxdb/v1.7/query_language/schema_exploration/#show-series) | -- | | [CREATE DATABASE](/influxdb/v1.7/query_language/database_management/#create-database) | -- | | [DROP DATABASE](/influxdb/v1.7/query_language/database_management/#delete-a-database-with-drop-database) | -- | -| [DROP SERIES](/influxdb/v1.7/query_language/database_management/#drop-series-from-the-index-with-drop-serie) | -- | +| [DROP SERIES](/influxdb/v1.7/query_language/database_management/#drop-series-from-the-index-with-drop-series) | -- | | [DELETE](/influxdb/v1.7/query_language/database_management/#delete-series-with-delete) | -- | | [DROP MEASUREMENT](/influxdb/v1.7/query_language/database_management/#delete-measurements-with-drop-measurement) | -- | | [DROP SHARD](/influxdb/v1.7/query_language/database_management/#delete-a-shard-with-drop-shard) | -- | @@ -361,9 +361,9 @@ _For a complete list of Flux functions, [view all Flux functions](/{{< latest "i | [FLOOR](/influxdb/v1.7/query_language/functions#floor) | [math.floor()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/floor/) | | [HISTOGRAM](/influxdb/v1.7/query_language/functions#histogram) | [histogram()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/histogram/) | | [LN](/influxdb/v1.7/query_language/functions#ln) | [math.log()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/log/) | -| [LOG](/influxdb/v1.7/query_language/functions#log) | [math.logb()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/logb/) | -| [LOG2](/influxdb/v1.7/query_language/functions#log2) | [math.log2()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/log2/) | -| [LOG10](/influxdb/v1.7/query_language/functions#logt10) | [math.log10()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/log10/) | +| [LOG](/influxdb/v1.7/query_language/functions/#log) | [math.logb()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/logb/) | +| [LOG2](/influxdb/v1.7/query_language/functions/#log2) | [math.log2()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/log2/) | +| [LOG10](/influxdb/v1.7/query_language/functions/#log10) | [math.log10()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/log10/) | | [MOVING_AVERAGE](/influxdb/v1.7/query_language/functions#moving-average) | [movingAverage()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/movingaverage/) | | [NON_NEGATIVE_DERIVATIVE](/influxdb/v1.7/query_language/functions#non-negative-derivative) | [derivative(nonNegative:true)](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/derivative/) | | [NON_NEGATIVE_DIFFERENCE](/influxdb/v1.7/query_language/functions#non-negative-difference) | [difference(nonNegative:true)](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/derivative/) | diff --git a/content/influxdb/v1.7/introduction/getting-started.md b/content/influxdb/v1.7/introduction/getting-started.md index 576555f85..a411861b3 100644 --- a/content/influxdb/v1.7/introduction/getting-started.md +++ b/content/influxdb/v1.7/introduction/getting-started.md @@ -37,7 +37,7 @@ InfluxDB shell 1.7.x * The InfluxDB API runs on port `8086` by default. Therefore, `influx` will connect to port `8086` and `localhost` by default. If you need to alter these defaults, run `influx --help`. -* The [`-precision` argument](/influxdb/v1.7/tools/shell/#influx-options) specifies the format/precision of any returned timestamps. +* The [`-precision` argument](/influxdb/v1.7/tools/shell/#influx-arguments) specifies the format/precision of any returned timestamps. In the example above, `rfc3339` tells InfluxDB to return timestamps in [RFC3339 format](https://www.ietf.org/rfc/rfc3339.txt) (`YYYY-MM-DDTHH:MM:SS.nnnnnnnnnZ`). The command line is now ready to take input in the form of the Influx Query Language (a.k.a InfluxQL) statements. diff --git a/content/influxdb/v1.7/query_language/continuous_queries.md b/content/influxdb/v1.7/query_language/continuous_queries.md index 512567bf3..fb4a0b691 100644 --- a/content/influxdb/v1.7/query_language/continuous_queries.md +++ b/content/influxdb/v1.7/query_language/continuous_queries.md @@ -360,7 +360,7 @@ Note that the basic syntax does not support using to change the value reported for intervals with no data. Basic syntax CQs ignore `fill()` if it's included in the CQ query. A possible workaround is to use the -[advanced CQ syntax](#example-4-configuring-cq-time-ranges-and-filling-empty-results). +[advanced CQ syntax](#advanced-syntax). ##### Resampling previous time intervals diff --git a/content/influxdb/v1.7/query_language/data_download.md b/content/influxdb/v1.7/query_language/data_download.md index 1f860b5aa..8bc98046b 100644 --- a/content/influxdb/v1.7/query_language/data_download.md +++ b/content/influxdb/v1.7/query_language/data_download.md @@ -32,7 +32,7 @@ InfluxDB shell 1.4.x * The InfluxDB API runs on port `8086` by default. Therefore, `influx` will connect to port `8086` and `localhost` by default. If you need to alter these defaults, run `influx --help`. -* The [`-precision` argument](/influxdb/v1.7/tools/shell/#influx-options) specifies the format/precision of any returned timestamps. +* The [`-precision` argument](/influxdb/v1.7/tools/shell/#influx-arguments) specifies the format/precision of any returned timestamps. In the example above, `rfc3339` tells InfluxDB to return timestamps in [RFC3339 format](https://www.ietf.org/rfc/rfc3339.txt) (`YYYY-MM-DDTHH:MM:SS.nnnnnnnnnZ`). The command line is now ready to take input in the form of the Influx Query Language (a.k.a InfluxQL) statements. diff --git a/content/influxdb/v1.7/query_language/spec.md b/content/influxdb/v1.7/query_language/spec.md index 78cd47331..61c12a043 100644 --- a/content/influxdb/v1.7/query_language/spec.md +++ b/content/influxdb/v1.7/query_language/spec.md @@ -616,7 +616,7 @@ SIZE OF BLOCKS: 931 ### EXPLAIN ANALYZE -Executes the specified SELECT statement and returns data on the query performance and storage during runtime, visualized as a tree. Use this statement to analyze query performance and storage, including [execution time](#execution_time) and [planning time](#planning_time), and the [iterator type](#iterator-type) and [cursor type](#cursor-type). +Executes the specified SELECT statement and returns data on the query performance and storage during runtime, visualized as a tree. Use this statement to analyze query performance and storage, including [execution time](#execution-time) and [planning time](#planning-time), and the [iterator type](#iterator-type) and [cursor type](#cursor-type). For example, executing the following statement: diff --git a/content/influxdb/v1.7/supported_protocols/collectd.md b/content/influxdb/v1.7/supported_protocols/collectd.md index f739e8294..25c3283a9 100644 --- a/content/influxdb/v1.7/supported_protocols/collectd.md +++ b/content/influxdb/v1.7/supported_protocols/collectd.md @@ -15,7 +15,7 @@ The [collectd](https://collectd.org) input allows InfluxDB to accept data transm ## A note on UDP/IP buffer sizes -If you're running Linux or FreeBSD, please adjust your operating system UDP buffer size limit, [see here for more details.](/influxdb/v1.7/supported_protocols/udp/#a-note-on-udpip-os-buffer-sizes) +If you're running Linux or FreeBSD, please adjust your operating system UDP buffer size limit, [see here for more details.](/influxdb/v1.7/supported_protocols/udp/#a-note-on-udp-ip-os-buffer-sizes) ## Configuration diff --git a/content/influxdb/v1.7/tools/shell.md b/content/influxdb/v1.7/tools/shell.md index 438b3685e..9fd62b3a4 100644 --- a/content/influxdb/v1.7/tools/shell.md +++ b/content/influxdb/v1.7/tools/shell.md @@ -248,7 +248,7 @@ The import file has two sections: * **DDL (Data Definition Language)**: Contains the [InfluxQL commands](/influxdb/v1.7/query_language/database_management/) for creating the relevant [database](/influxdb/v1.7/concepts/glossary/) and managing the [retention policy](/influxdb/v1.7/concepts/glossary/#retention-policy-rp). If your database and retention policy already exist, your file can skip this section. -* **DML (Data Manipulation Language)**: Lists the relevant database and (if desired) retention policy and contains the data in [line protocol](/influxdb/v1.7/concepts/glossary/#line-protocol). +* **DML (Data Manipulation Language)**: Lists the relevant database and (if desired) retention policy and contains the data in [line protocol](/influxdb/v1.7/concepts/glossary/#influxdb-line-protocol). Example: @@ -374,7 +374,7 @@ If you do not specify the retention policy, `influx` automatically queries the ` #### Write data to InfluxDB with `insert` -Enter `insert` followed by the data in [line protocol](/influxdb/v1.7/concepts/glossary/#line-protocol) to write data to InfluxDB. +Enter `insert` followed by the data in [line protocol](/influxdb/v1.7/concepts/glossary/#influxdb-line-protocol) to write data to InfluxDB. Use `insert into ` to write data to a specific [retention policy](/influxdb/v1.7/concepts/glossary/#retention-policy-rp). Write data to a single field in the measurement `treasures` with the tag `captain_id = pirate_king`. diff --git a/content/influxdb/v1.7/troubleshooting/frequently-asked-questions.md b/content/influxdb/v1.7/troubleshooting/frequently-asked-questions.md index d9ca032de..35ccd1add 100644 --- a/content/influxdb/v1.7/troubleshooting/frequently-asked-questions.md +++ b/content/influxdb/v1.7/troubleshooting/frequently-asked-questions.md @@ -214,7 +214,7 @@ If you anticipate growing over 16TB per volume/file system, we recommend finding ## How do I manually trigger a compaction? -Trigger a full compaction after startup by adjusting the [`compact-full-write-cold-duration`](/influxdb/v1.7/administration/config/#compact-full-write-cold-duration-4h) setting in your InfluxDB configuration file. For more information, see [Using the configuration file](/influxdb/v1.7/administration/config/#using-the-configuration-file/). Consider the following items may affect the schedule for compaction: +Trigger a full compaction after startup by adjusting the [`compact-full-write-cold-duration`](/influxdb/v1.7/administration/config/#compact-full-write-cold-duration-4h) setting in your InfluxDB configuration file. For more information, see [Using the configuration file](/influxdb/v1.7/administration/config/#using-the-configuration-file). Consider the following items may affect the schedule for compaction: - Shard duration and write patterns. For example, frequently writing to old shards may affect compaction. - Number of concurrent compactions (`max-concurrent-compactions`). For example, multiple shards pending compaction may affect when a compaction is run. @@ -606,7 +606,7 @@ time sunflowers time mean The most common reasons why your query returns no data or partial data: -- [Querying the wrong retention policy](#querying-wrong-retention-policy) (no data returned) +- [Querying the wrong retention policy](#querying-the-wrong-retention-policy) (no data returned) - [No field key in the SELECT clause](#no-field-key-in-the-select-clause) (no data returned) - [SELECT query includes `GROUP BY time()`](#select-query-includes-group-by-time) (partial data before `now()` returned) - [Tag and field key with the same name](#tag-and-field-key-with-the-same-name) diff --git a/content/influxdb/v1.8/_index.md b/content/influxdb/v1.8/_index.md index 6df927c9b..43799a992 100644 --- a/content/influxdb/v1.8/_index.md +++ b/content/influxdb/v1.8/_index.md @@ -28,4 +28,4 @@ It compiles into a single binary with no external dependencies. * Continuous queries automatically compute aggregate data to make frequent queries more efficient. The open source edition of InfluxDB runs on a single node. -If you require high availability to eliminate a single point of failure, consider the [InfluxDB Enterprise Edition](/{{< latest "influxdb" "v1" >}}/high_availability/). +If you require high availability to eliminate a single point of failure, consider the [InfluxDB Enterprise Edition](/{{< latest "enterprise_influxdb" "v1" >}}/high_availability/). diff --git a/content/influxdb/v1.8/about_the_project/releasenotes-changelog.md b/content/influxdb/v1.8/about_the_project/releasenotes-changelog.md index d1d899b9f..a5c4c9bb1 100644 --- a/content/influxdb/v1.8/about_the_project/releasenotes-changelog.md +++ b/content/influxdb/v1.8/about_the_project/releasenotes-changelog.md @@ -36,7 +36,7 @@ menu: This release updates support for the Flux language and queries. To learn about Flux design principles and see how to get started with Flux, see [Introduction to Flux](/influxdb/v1.8/flux/). -* Use the new [`influx -type=flux`](/influxdb/v1.8/tools/shell/#type) option to enable the Flux REPL shell for creating Flux queries. +* Use the new [`influx -type=flux`](/influxdb/v1.8/tools/influx-cli/#flags) option to enable the Flux REPL shell for creating Flux queries. * Flux v0.65 includes the following capabilities: - Join data residing in multiple measurements, buckets, or data sources @@ -64,7 +64,7 @@ while readying your implementation for a move to InfluxDB 2.0 Cloud when you're - Add [`influx inspect verify-tombstone` command](/influxdb/v1.8/tools/influx_inspect/#verify-tombstone) - Add [offline series compaction to `influx_inspect buildtsi`](/influxdb/v1.8/administration/compact-series-file/). If you're currently using the Time Series Index [(tsi1)](/influxdb/v1.8/concepts/time-series-index/), the index files grow over time and aren't automatically compacted. This tool enables an administrator to perform a compaction while the database is offline. -- Add support for connecting to a custom HTTP endpoint using `-url-prefix` in the [`influx` CLI](/influxdb/v1.8/tools/influx-cli/_index). This allows the Influx CLI to connect to an InfluxDB instance running behind a reverse proxy with a custom subpath `/` endpoint. +- Add support for connecting to a custom HTTP endpoint using `-url-prefix` in the [`influx` CLI](/influxdb/v1.8/tools/influx-cli/). This allows the Influx CLI to connect to an InfluxDB instance running behind a reverse proxy with a custom subpath `/` endpoint. #### Security enhancements - Add support for [TLS 1.3 configuration](/influxdb/v1.8/administration/config/#transport-layer-security-tls-settings) and update current list of [Go ciphers](https://golang.org/pkg/crypto/tls/#pkg-constants). diff --git a/content/influxdb/v1.8/administration/authentication_and_authorization.md b/content/influxdb/v1.8/administration/authentication_and_authorization.md index cf3813eac..42ce030d9 100644 --- a/content/influxdb/v1.8/administration/authentication_and_authorization.md +++ b/content/influxdb/v1.8/administration/authentication_and_authorization.md @@ -258,7 +258,7 @@ Database management:    ◦   `CREATE RETENTION POLICY`, `ALTER RETENTION POLICY`, and `DROP RETENTION POLICY`    ◦   `CREATE CONTINUOUS QUERY` and `DROP CONTINUOUS QUERY` -See the [database management](/influxdb/v1.8/query_language/database_management/) and [continuous queries](/influxdb/v1.8/query_language/continuous_queries/) pages for a complete discussion of the commands listed above. +See the [database management](/influxdb/v1.8/query_language/manage-database/) and [continuous queries](/influxdb/v1.8/query_language/continuous_queries/) pages for a complete discussion of the commands listed above. User management:    ◦   Admin user management: @@ -278,7 +278,7 @@ Non-admin users can have one of the following three privileges per database:    ◦   `ALL` (both `READ` and `WRITE` access) `READ`, `WRITE`, and `ALL` privileges are controlled per user per database. A new non-admin user has no access to any database until they are specifically [granted privileges to a database](#grant-read-write-or-all-database-privileges-to-an-existing-user) by an admin user. -Non-admin users can [`SHOW`](/influxdb/v1.8/query_language/schema_exploration/#show-databases) the databases on which they have `READ` and/or `WRITE` permissions. +Non-admin users can [`SHOW`](/influxdb/v1.8/query_language/explore-schema/#show-databases) the databases on which they have `READ` and/or `WRITE` permissions. ### User management commands diff --git a/content/influxdb/v1.8/administration/backup_and_restore.md b/content/influxdb/v1.8/administration/backup_and_restore.md index 386e98d8a..9eca4103c 100644 --- a/content/influxdb/v1.8/administration/backup_and_restore.md +++ b/content/influxdb/v1.8/administration/backup_and_restore.md @@ -276,7 +276,7 @@ Optional flags also include: - `-retention ` - This flag can be used to backup a specific retention policy. For more information on retention policies, see - [Retention policy management](/influxdb/v1.8/query_language/database_management/#retention-policy-management). If unspecified, all retention policies will be backed up. + [Retention policy management](/influxdb/v1.8/query_language/manage-database/#retention-policy-management). If unspecified, all retention policies will be backed up. - `-shard ` - This flag can be used to backup a specific shard ID. To see which shards are available, you can run the command diff --git a/content/influxdb/v1.8/administration/config.md b/content/influxdb/v1.8/administration/config.md index b235679d4..e38d6896e 100644 --- a/content/influxdb/v1.8/administration/config.md +++ b/content/influxdb/v1.8/administration/config.md @@ -522,7 +522,7 @@ The `[monitor]` section settings control the InfluxDB [system self-monitoring](h By default, InfluxDB writes the data to the `_internal` database. If that database does not exist, InfluxDB creates it automatically. The `DEFAULT` retention policy on the `_internal` database is seven days. -If you want to use a retention policy other than the seven-day retention policy, you must [create](/influxdb/v1.8/query_language/database_management/#retention-policy-management) it. +If you want to use a retention policy other than the seven-day retention policy, you must [create](/influxdb/v1.8/query_language/manage-database/#retention-policy-management) it. #### `store-enabled = true` diff --git a/content/influxdb/v1.8/administration/upgrading.md b/content/influxdb/v1.8/administration/upgrading.md index e0b30ea48..6d593cbc3 100644 --- a/content/influxdb/v1.8/administration/upgrading.md +++ b/content/influxdb/v1.8/administration/upgrading.md @@ -9,7 +9,7 @@ menu: --- -We recommend enabling Time Series Index (TSI) (step 3 of Upgrade to InfluxDB 1.8.x). [Switch between TSM and TSI](#switch-between-tsm-and-tsi-indexes) as needed. To learn more about TSI, see: +We recommend enabling Time Series Index (TSI) (step 3 of Upgrade to InfluxDB 1.8.x). [Switch between TSM and TSI](#switch-index-types) as needed. To learn more about TSI, see: - [Time Series Index (TSI) overview](/influxdb/v1.8/concepts/time-series-index/) - [Time Series Index (TSI) details](/influxdb/v1.8/concepts/tsi-details/) @@ -47,13 +47,13 @@ and see [Migrate to InfluxDB Enterprise](/{{< latest "enterprise_influxdb" >}}/g Switch index types at any time by doing one of the following: -- To switch from to `inmem` to `tsi1`, complete steps 3 and 4 above in [Upgrade to InfluxDB 1.8.x](#upgrade-to-influxdb-1.8.x). -- To switch from to `tsi1` to `inmem`, change `tsi1` to `inmem` by completing steps 3a-3c and 4 above in [Upgrade to InfluxDB 1.8.x](#upgrade-to-influxdb-1.8.x). +- To switch from to `inmem` to `tsi1`, complete steps 3 and 4 above in [Upgrade to InfluxDB 1.8.x](#upgrade-to-influxdb-1-8-x). +- To switch from to `tsi1` to `inmem`, change `tsi1` to `inmem` by completing steps 3a-3c and 4 above in [Upgrade to InfluxDB 1.8.x](#upgrade-to-influxdb-1-8-x). ## Downgrade InfluxDB -To downgrade to an earlier version, complete the procedures above in [Upgrade to InfluxDB 1.8.x](#upgrade-to-influxdb-1-7-x), replacing the version numbers with the version that you want to downgrade to. -After downloading the release, migrating your configuration settings, and enabling TSI or TSM, make sure to [rebuild your index](/influxdb/v1.8/administration/rebuild-tsi-index/#sidebar). +To downgrade to an earlier version, complete the procedures above in [Upgrade to InfluxDB 1.8.x](#upgrade-to-influxdb-1-8-x), replacing the version numbers with the version that you want to downgrade to. +After downloading the release, migrating your configuration settings, and enabling TSI or TSM, make sure to [rebuild your index](/influxdb/v1.8/administration/rebuild-tsi-index/). >**Note:** Some versions of InfluxDB may have breaking changes that impact your ability to upgrade and downgrade. For example, you cannot downgrade from InfluxDB 1.3 or later to an earlier version. Please review the applicable version of release notes to check for compatibility issues between releases. diff --git a/content/influxdb/v1.8/concepts/crosswalk.md b/content/influxdb/v1.8/concepts/crosswalk.md index 029ae2fff..5538a0f07 100644 --- a/content/influxdb/v1.8/concepts/crosswalk.md +++ b/content/influxdb/v1.8/concepts/crosswalk.md @@ -123,7 +123,7 @@ InfluxDB supports multiple query languages: [Flux](/flux/latest/introduction) is a data scripting language designed for querying, analyzing, and acting on time series data. Beginning with **InfluxDB 1.8.0**, Flux is available for production use along side InfluxQL. -For those familiar with [InfluxQL](#influxql-and-sql), Flux is intended to address +For those familiar with [InfluxQL](#influxql), Flux is intended to address many of the outstanding feature requests that we've received since introducing InfluxDB 1.0. For a comparison between Flux and InfluxQL, see [Flux vs InfluxQL](/flux/latest/introduction/flux-vs-influxql). @@ -194,7 +194,7 @@ The options for specifying time durations with `now()` are: | w | weeks | InfluxQL also supports regular expressions, arithmetic in expressions, `SHOW` statements, and `GROUP BY` statements. -See our [data exploration](/influxdb/v1.8/query_language/data_exploration/) page for an in-depth discussion of those topics. +See our [data exploration](/influxdb/v1.8/query_language/explore-data/) page for an in-depth discussion of those topics. InfluxQL functions include `COUNT`, `MIN`, `MAX`, `MEDIAN`, `DERIVATIVE` and more. For a full list check out the [functions](/influxdb/v1.8/query_language/functions/) page. @@ -214,6 +214,6 @@ In addition, time series data is generally written once and rarely updated. The result is that InfluxDB is not a full CRUD database but more like a CR-ud, prioritizing the performance of creating and reading data over update and destroy, and [preventing some update and destroy behaviors](/influxdb/v1.8/concepts/insights_tradeoffs/) to make create and read more performant: * To update a point, insert one with [the same measurement, tag set, and timestamp](/influxdb/v1.8/troubleshooting/frequently-asked-questions/#how-does-influxdb-handle-duplicate-points). -* You can [drop or delete a series](/influxdb/v1.8/query_language/database_management/#drop-series-from-the-index-with-drop-series), but not individual points based on field values. As a workaround, you can search for the field value, retrieve the time, then [DELETE based on the `time` field](/influxdb/v1.8/query_language/database_management/#delete-series-with-delete). +* You can [drop or delete a series](/influxdb/v1.8/query_language/manage-database/#drop-series-from-the-index-with-drop-series), but not individual points based on field values. As a workaround, you can search for the field value, retrieve the time, then [DELETE based on the `time` field](/influxdb/v1.8/query_language/manage-database/#delete-series-with-delete). * You can't update or rename tags yet - see GitHub issue [#4157](https://github.com/influxdata/influxdb/issues/4157) for more information. To modify the tag of a series of points, find the points with the offending tag value, change the value to the desired one, write the points back, then drop the series with the old tag value. * You can't delete tags by tag key (as opposed to value) - see GitHub issue [#8604](https://github.com/influxdata/influxdb/issues/8604). diff --git a/content/influxdb/v1.8/concepts/glossary.md b/content/influxdb/v1.8/concepts/glossary.md index c9bb88a3a..358f8b2d0 100644 --- a/content/influxdb/v1.8/concepts/glossary.md +++ b/content/influxdb/v1.8/concepts/glossary.md @@ -47,7 +47,7 @@ Related entries: [continuous query](/influxdb/v1.8/concepts/glossary/#continuous The attribute of the retention policy that determines how long InfluxDB stores data. Data older than the duration are automatically dropped from the database. -See [Database Management](/influxdb/v1.8/query_language/database_management/#create-retention-policies-with-create-retention-policy) for how to set duration. +See [Database Management](/influxdb/v1.8/query_language/manage-database/#create-retention-policies-with-create-retention-policy) for how to set duration. Related entries: [retention policy](/influxdb/v1.8/concepts/glossary/#retention-policy-rp) @@ -160,7 +160,7 @@ Related entries: [point](/influxdb/v1.8/concepts/glossary/#point), [schema](/inf ## query An operation that retrieves data from InfluxDB. -See [Data Exploration](/influxdb/v1.8/query_language/data_exploration/), [Schema Exploration](/influxdb/v1.8/query_language/schema_exploration/), [Database Management](/influxdb/v1.8/query_language/database_management/). +See [Data Exploration](/influxdb/v1.8/query_language/explore-data/), [Schema Exploration](/influxdb/v1.8/query_language/explore-schema/), [Database Management](/influxdb/v1.8/query_language/manage-database/). ## replication factor @@ -177,7 +177,7 @@ Related entries: [cluster](/influxdb/v0.10/concepts/glossary/#cluster), [duratio Describes how long InfluxDB keeps data (duration), how many copies of the data to store in the cluster (replication factor), and the time range covered by shard groups (shard group duration). RPs are unique per database and along with the measurement and tag set define a series. When you create a database, InfluxDB creates a retention policy called `autogen` with an infinite duration, a replication factor set to one, and a shard group duration set to seven days. -For more information, see [Retention policy management](/influxdb/v1.8/query_language/database_management/#retention-policy-management). +For more information, see [Retention policy management](/influxdb/v1.8/query_language/manage-database/#retention-policy-management). Related entries: [duration](/influxdb/v1.8/concepts/glossary/#duration), [measurement](/influxdb/v1.8/concepts/glossary/#measurement), [replication factor](/influxdb/v1.8/concepts/glossary/#replication-factor), [series](/influxdb/v1.8/concepts/glossary/#series), [shard duration](/influxdb/v1.8/concepts/glossary/#shard-duration), [tag set](/influxdb/v1.8/concepts/glossary/#tag-set) @@ -275,7 +275,7 @@ Related entries: [series](/influxdb/v1.8/concepts/glossary/#series), [shard dura The shard duration determines how much time each shard group spans. The specific interval is determined by the `SHARD DURATION` of the retention policy. -See [Retention Policy management](/influxdb/v1.8/query_language/database_management/#retention-policy-management) for more information. +See [Retention Policy management](/influxdb/v1.8/query_language/manage-database/#retention-policy-management) for more information. For example, given a retention policy with `SHARD DURATION` set to `1w`, each shard group will span a single week and contain all points with timestamps in that week. @@ -336,7 +336,7 @@ The date and time associated with a point. All time in InfluxDB is UTC. For how to specify time when writing data, see [Write Syntax](/influxdb/v1.8/write_protocols/write_syntax/). -For how to specify time when querying data, see [Data Exploration](/influxdb/v1.8/query_language/data_exploration/#time-syntax). +For how to specify time when querying data, see [Data Exploration](/influxdb/v1.8/query_language/explore-data/#time-syntax). Related entries: [point](/influxdb/v1.8/concepts/glossary/#point) diff --git a/content/influxdb/v1.8/concepts/key_concepts.md b/content/influxdb/v1.8/concepts/key_concepts.md index 3cb725bb8..ee57bea7f 100644 --- a/content/influxdb/v1.8/concepts/key_concepts.md +++ b/content/influxdb/v1.8/concepts/key_concepts.md @@ -162,7 +162,7 @@ The name `census` tells us that the field values record the number of `butterfli A single measurement can belong to different retention policies. A _**retention policy**_ describes how long InfluxDB keeps data (`DURATION`) and how many copies of this data is stored in the cluster (`REPLICATION`). -If you're interested in reading more about retention policies, check out [Database Management](/influxdb/v1.8/query_language/database_management/#retention-policy-management). +If you're interested in reading more about retention policies, check out [Database Management](/influxdb/v1.8/query_language/manage-database/#retention-policy-management). {{% warn %}} Replication factors do not serve a purpose with single node instances. {{% /warn %}} diff --git a/content/influxdb/v1.8/concepts/schema_and_data_layout.md b/content/influxdb/v1.8/concepts/schema_and_data_layout.md index 85c39e410..593301b3c 100644 --- a/content/influxdb/v1.8/concepts/schema_and_data_layout.md +++ b/content/influxdb/v1.8/concepts/schema_and_data_layout.md @@ -62,7 +62,7 @@ We recommend that you: [Tags](/influxdb/v1.8/concepts/glossary/#tag) containing highly variable information like UUIDs, hashes, and random strings lead to a large number of [series](/influxdb/v1.8/concepts/glossary/#series) in the database, also known as high series cardinality. High series cardinality is a primary driver of high memory usage for many database workloads. -See [Hardware sizing guidelines](/influxdb/v1.8/guides/hardware_sizing/#general-hardware-guidelines-for-a-single-node) for [series cardinality](/influxdb/v1.8/concepts/glossary/#series-cardinality) recommendations based on your hardware. If the system has memory constraints, consider storing high-cardinality data as a field rather than a tag. +See [Hardware sizing guidelines](/influxdb/v1.8/guides/hardware_sizing/) for [series cardinality](/influxdb/v1.8/concepts/glossary/#series-cardinality) recommendations based on your hardware. If the system has memory constraints, consider storing high-cardinality data as a field rather than a tag. #### Avoid the same name for a tag and a field @@ -197,7 +197,7 @@ If no shard group duration is provided, the shard group duration is determined b | > 6 months | 7 days | The shard group duration is also configurable per RP. -To configure the shard group duration, see [Retention Policy Management](/influxdb/v1.8/query_language/database_management/#retention-policy-management). +To configure the shard group duration, see [Retention Policy Management](/influxdb/v1.8/query_language/manage-database/#retention-policy-management). ### Shard group duration tradeoffs @@ -219,7 +219,7 @@ A shard group will only be removed once a shard group's duration *end time* is o For example, if your RP has a duration of one day, InfluxDB will drop an hour's worth of data every hour and will always have 25 shard groups. One for each hour in the day and an extra shard group that is partially expiring, but isn't removed until the whole shard group is older than 24 hours. ->**Note:** A special use case to consider: filtering queries on schema data (such as tags, series, measurements) by time. For example, if you want to filter schema data within a one hour interval, you must set the shard group duration to 1h. For more information, see [filter schema data by time](/influxdb/v1.8/query_language/schema_exploration/#filter-meta-queries-by-time). +>**Note:** A special use case to consider: filtering queries on schema data (such as tags, series, measurements) by time. For example, if you want to filter schema data within a one hour interval, you must set the shard group duration to 1h. For more information, see [filter schema data by time](/influxdb/v1.8/query_language/explore-schema/#filter-meta-queries-by-time). ### Shard group duration recommendations @@ -234,7 +234,7 @@ Here are some recommendations for longer shard group durations: | > 3 months | 30 days | | infinite | 52 weeks or longer | -> **Note:** Note that `INF` (infinite) is not a [valid shard group duration](/influxdb/v1.8/query_language/database_management/#retention-policy-management). +> **Note:** Note that `INF` (infinite) is not a [valid shard group duration](/influxdb/v1.8/query_language/manage-database/#retention-policy-management). In extreme cases where data covers decades and will never be deleted, a long shard group duration like `1040w` (20 years) is perfectly valid. Other factors to consider before setting shard group duration: diff --git a/content/influxdb/v1.8/concepts/tsi-details.md b/content/influxdb/v1.8/concepts/tsi-details.md index 512c26d7f..eb0ba06c7 100644 --- a/content/influxdb/v1.8/concepts/tsi-details.md +++ b/content/influxdb/v1.8/concepts/tsi-details.md @@ -30,11 +30,11 @@ index-version = "tsi1" - To convert your data nodes to support TSI, see [Upgrade InfluxDB Enterprise clusters](/enterprise_influxdb/v1.8/administration/upgrading/). -- For detail on configuration, see [Configure InfluxDB Enterprise clusters](/enterprise_influxdb/v1.8/administration/configuration/#sidebar). +- For detail on configuration, see [Configure InfluxDB Enterprise clusters](/enterprise_influxdb/v1.8/administration/configuration/). ### InfluxDB OSS -- For detail on configuration, see [Configuring InfluxDB OSS](/influxdb/v1.8/administration/config/#sidebar). +- For detail on configuration, see [Configuring InfluxDB OSS](/influxdb/v1.8/administration/config/). ## Tooling diff --git a/content/influxdb/v1.8/flux/flux-vs-influxql.md b/content/influxdb/v1.8/flux/flux-vs-influxql.md index c7392f596..552440f7c 100644 --- a/content/influxdb/v1.8/flux/flux-vs-influxql.md +++ b/content/influxdb/v1.8/flux/flux-vs-influxql.md @@ -336,84 +336,84 @@ _For a complete list of Flux functions, [view all Flux functions](/{{< latest "i ### InfluxQL and Flux parity -| InfluxQL | Flux Functions | -| -------- | -------------- | -| [SELECT](/influxdb/v1.8/query_language/explore-data/#the-basic-select-statement) | [filter()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/filter/) | -| [WHERE](/influxdb/v1.8/query_language/explore-data/#the-where-clause) | [filter()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/filter/), [range()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/range/) | -| [GROUP BY](/influxdb/v1.8/query_language/explore-data/#the-group-by-clause) | [group()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/group/) | -| [INTO](/influxdb/v1.8/query_language/explore-data/#the-into-clause) | [to()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/outputs/to/) * | -| [ORDER BY](/influxdb/v1.8/query_language/explore-data/#order-by-time-desc) | [sort()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/sort/) | -| [LIMIT](/influxdb/v1.8/query_language/explore-data/#the-limit-clause) | [limit()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/limit/) | -| [SLIMIT](/influxdb/v1.8/query_language/explore-data/#the-slimit-clause) | -- | -| [OFFSET](/influxdb/v1.8/query_language/explore-data/#the-offset-clause) | -- | -| [SOFFSET](/influxdb/v1.8/query_language/explore-data/#the-soffset-clause) | -- | -| [SHOW DATABASES](/influxdb/v1.8/query_language/explore-schema/#show-databases) | [buckets()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/inputs/buckets/) | -| [SHOW MEASUREMENTS](/influxdb/v1.8/query_language/explore-schema/#show-measurements) | [v1.measurements](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/influxdb-v1/measurements) | -| [SHOW FIELD KEYS](/influxdb/v1.8/query_language/explore-schema/#show-field-keys) | [keys()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/keys/) | -| [SHOW RETENTION POLICIES](/influxdb/v1.8/query_language/explore-schema/#show-retention-policies) | [buckets()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/inputs/buckets/) | -| [SHOW TAG KEYS](/influxdb/v1.8/query_language/explore-schema/#show-tag-keys) | [v1.tagKeys()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/influxdb-v1/tagkeys), [v1.measurementTagKeys()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/influxdb-v1/measurementtagkeys) | -| [SHOW TAG VALUES](/influxdb/v1.8/query_language/explore-schema/#show-tag-values) | [v1.tagValues()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/influxdb-v1/tagvalues), [v1.measurementTagValues()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/influxdb-v1/measurementtagvalues) | -| [SHOW SERIES](/influxdb/v1.8/query_language/explore-schema/#show-series) | -- | -| [CREATE DATABASE](/influxdb/v1.8/query_language/database_management/#create-database) | -- | -| [DROP DATABASE](/influxdb/v1.8/query_language/database_management/#delete-a-database-with-drop-database) | -- | -| [DROP SERIES](/influxdb/v1.8/query_language/database_management/#drop-series-from-the-index-with-drop-serie) | -- | -| [DELETE](/influxdb/v1.8/query_language/database_management/#delete-series-with-delete) | -- | -| [DROP MEASUREMENT](/influxdb/v1.8/query_language/database_management/#delete-measurements-with-drop-measurement) | -- | -| [DROP SHARD](/influxdb/v1.8/query_language/database_management/#delete-a-shard-with-drop-shard) | -- | -| [CREATE RETENTION POLICY](/influxdb/v1.8/query_language/database_management/#create-retention-policies-with-create-retention-policy) | -- | -| [ALTER RETENTION POLICY](/influxdb/v1.8/query_language/database_management/#modify-retention-policies-with-alter-retention-policy) | -- | -| [DROP RETENTION POLICY](/influxdb/v1.8/query_language/database_management/#delete-retention-policies-with-drop-retention-policy) | -- | -| [COUNT](/influxdb/v1.8/query_language/functions#count) | [count()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/aggregates/count/) | -| [DISTINCT](/influxdb/v1.8/query_language/functions#distinct) | [distinct()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/selectors/distinct/) | -| [INTEGRAL](/influxdb/v1.8/query_language/functions#integral) | [integral()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/aggregates/integral/) | -| [MEAN](/influxdb/v1.8/query_language/functions#mean) | [mean()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/aggregates/mean/) | -| [MEDIAN](/influxdb/v1.8/query_language/functions#median) | [median()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/aggregates/median/) | -| [MODE](/influxdb/v1.8/query_language/functions#mode) | [mode()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/aggregates/mode/) | -| [SPREAD](/influxdb/v1.8/query_language/functions#spread) | [spread()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/aggregates/spread/) | -| [STDDEV](/influxdb/v1.8/query_language/functions#stddev) | [stddev()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/aggregates/stddev/) | -| [SUM](/influxdb/v1.8/query_language/functions#sum) | [sum()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/aggregates/sum/) | -| [BOTTOM](/influxdb/v1.8/query_language/functions#bottom) | [bottom()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/selectors/bottom/) | -| [FIRST](/influxdb/v1.8/query_language/functions#first) | [first()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/selectors/first/) | -| [LAST](/influxdb/v1.8/query_language/functions#last) | [last()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/selectors/last/) | -| [MAX](/influxdb/v1.8/query_language/functions#max) | [max()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/selectors/max/) | -| [MIN](/influxdb/v1.8/query_language/functions#min) | [min()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/selectors/min/) | -| [PERCENTILE](/influxdb/v1.8/query_language/functions#percentile) | [quantile()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/aggregates/quantile/) | -| [SAMPLE](/influxdb/v1.8/query_language/functions#sample) | [sample()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/selectors/sample/) | -| [TOP](/influxdb/v1.8/query_language/functions#top) | [top()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/selectors/top/) | -| [ABS](/influxdb/v1.8/query_language/functions#abs) | [math.abs()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/abs/) | -| [ACOS](/influxdb/v1.8/query_language/functions#acos) | [math.acos()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/acos/) | -| [ASIN](/influxdb/v1.8/query_language/functions#asin) | [math.asin()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/asin/) | -| [ATAN](/influxdb/v1.8/query_language/functions#atan) | [math.atan()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/atan/) | -| [ATAN2](/influxdb/v1.8/query_language/functions#atan2) | [math.atan2()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/atan2/) | -| [CEIL](/influxdb/v1.8/query_language/functions#ceil) | [math.ceil()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/ceil/) | -| [COS](/influxdb/v1.8/query_language/functions#cos) | [math.cos()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/cos/) | -| [CUMULATIVE_SUM](/influxdb/v1.8/query_language/functions#cumulative-sum) | [cumulativeSum()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/cumulativesum/) | -| [DERIVATIVE](/influxdb/v1.8/query_language/functions#derivative) | [derivative()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/derivative/) | -| [DIFFERENCE](/influxdb/v1.8/query_language/functions#difference) | [difference()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/difference/) | -| [ELAPSED](/influxdb/v1.8/query_language/functions#elapsed) | [elapsed()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/elapsed/) | -| [EXP](/influxdb/v1.8/query_language/functions#exp) | [math.exp()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/exp/) | -| [FLOOR](/influxdb/v1.8/query_language/functions#floor) | [math.floor()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/floor/) | -| [HISTOGRAM](/influxdb/v1.8/query_language/functions#histogram) | [histogram()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/histogram/) | -| [LN](/influxdb/v1.8/query_language/functions#ln) | [math.log()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/log/) | -| [LOG](/influxdb/v1.8/query_language/functions#log) | [math.logb()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/logb/) | -| [LOG2](/influxdb/v1.8/query_language/functions#log2) | [math.log2()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/log2/) | -| [LOG10](/influxdb/v1.8/query_language/functions#logt10) | [math.log10()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/log10/) | -| [MOVING_AVERAGE](/influxdb/v1.8/query_language/functions#moving-average) | [movingAverage()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/movingaverage/) | -| [NON_NEGATIVE_DERIVATIVE](/influxdb/v1.8/query_language/functions#non-negative-derivative) | [derivative(nonNegative:true)](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/derivative/) | -| [NON_NEGATIVE_DIFFERENCE](/influxdb/v1.8/query_language/functions#non-negative-difference) | [difference(nonNegative:true)](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/derivative/) | -| [POW](/influxdb/v1.8/query_language/functions#pow) | [math.pow()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/pow/) | -| [ROUND](/influxdb/v1.8/query_language/functions#round) | [math.round()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/round/) | -| [SIN](/influxdb/v1.8/query_language/functions#sin) | [math.sin()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/sin/) | -| [SQRT](/influxdb/v1.8/query_language/functions#sqrt) | [math.sqrt()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/sqrt/) | -| [TAN](/influxdb/v1.8/query_language/functions#tan) | [math.tan()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/tan/) | -| [HOLT_WINTERS](/influxdb/v1.8/query_language/functions#holt-winters) | [holtWinters()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/holtwinters/) | -| [CHANDE_MOMENTUM_OSCILLATOR](/influxdb/v1.8/query_language/functions#chande-momentum-oscillator) | [chandeMomentumOscillator()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/chandemomentumoscillator/) | -| [EXPONENTIAL_MOVING_AVERAGE](/influxdb/v1.8/query_language/functions#exponential-moving-average) | [exponentialMovingAverage()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/exponentialmovingaverage/) | -| [DOUBLE_EXPONENTIAL_MOVING_AVERAGE](/influxdb/v1.8/query_language/functions#double-exponential-moving-average) | [doubleEMA()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/doubleema/) | -| [KAUFMANS_EFFICIENCY_RATIO](/influxdb/v1.8/query_language/functions#kaufmans-efficiency-ratio) | [kaufmansER()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/kaufmanser/) | -| [KAUFMANS_ADAPTIVE_MOVING_AVERAGE](/influxdb/v1.8/query_language/functions#kaufmans-adaptive-moving-average) | [kaufmansAMA()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/kaufmansama/) | -| [TRIPLE_EXPONENTIAL_MOVING_AVERAGE](/influxdb/v1.8/query_language/functions#triple-exponential-moving-average) | [tripleEMA()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/tripleema/) | -| [TRIPLE_EXPONENTIAL_DERIVATIVE](/influxdb/v1.8/query_language/functions#triple-exponential-derivative) | [tripleExponentialDerivative()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/tripleexponentialderivative/) | -| [RELATIVE_STRENGTH_INDEX](/influxdb/v1.8/query_language/functions#relative-strength-index) | [relativeStrengthIndex()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/relativestrengthindex/) | +| InfluxQL | Flux Functions | +| -------- | -------------- | +| [SELECT](/influxdb/v1.8/query_language/explore-data/#the-basic-select-statement) | [filter()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/filter/) | +| [WHERE](/influxdb/v1.8/query_language/explore-data/#the-where-clause) | [filter()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/filter/), [range()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/range/) | +| [GROUP BY](/influxdb/v1.8/query_language/explore-data/#the-group-by-clause) | [group()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/group/) | +| [INTO](/influxdb/v1.8/query_language/explore-data/#the-into-clause) | [to()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/outputs/to/) * | +| [ORDER BY](/influxdb/v1.8/query_language/explore-data/#order-by-time-desc) | [sort()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/sort/) | +| [LIMIT](/influxdb/v1.8/query_language/explore-data/#the-limit-clause) | [limit()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/limit/) | +| [SLIMIT](/influxdb/v1.8/query_language/explore-data/#the-slimit-clause) | -- | +| [OFFSET](/influxdb/v1.8/query_language/explore-data/#the-offset-clause) | -- | +| [SOFFSET](/influxdb/v1.8/query_language/explore-data/#the-soffset-clause) | -- | +| [SHOW DATABASES](/influxdb/v1.8/query_language/explore-schema/#show-databases) | [buckets()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/inputs/buckets/) | +| [SHOW MEASUREMENTS](/influxdb/v1.8/query_language/explore-schema/#show-measurements) | [v1.measurements](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/influxdb-v1/measurements) | +| [SHOW FIELD KEYS](/influxdb/v1.8/query_language/explore-schema/#show-field-keys) | [keys()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/keys/) | +| [SHOW RETENTION POLICIES](/influxdb/v1.8/query_language/explore-schema/#show-retention-policies) | [buckets()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/inputs/buckets/) | +| [SHOW TAG KEYS](/influxdb/v1.8/query_language/explore-schema/#show-tag-keys) | [v1.tagKeys()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/influxdb-v1/tagkeys), [v1.measurementTagKeys()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/influxdb-v1/measurementtagkeys) | +| [SHOW TAG VALUES](/influxdb/v1.8/query_language/explore-schema/#show-tag-values) | [v1.tagValues()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/influxdb-v1/tagvalues), [v1.measurementTagValues()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/influxdb-v1/measurementtagvalues) | +| [SHOW SERIES](/influxdb/v1.8/query_language/explore-schema/#show-series) | -- | +| [CREATE DATABASE](/influxdb/v1.8/query_language/manage-database/#create-database) | -- | +| [DROP DATABASE](/influxdb/v1.8/query_language/manage-database/#delete-a-database-with-drop-database) | -- | +| [DROP SERIES](/influxdb/v1.8/query_language/manage-database/#drop-series-from-the-index-with-drop-series) | -- | +| [DELETE](/influxdb/v1.8/query_language/manage-database/#delete-series-with-delete) | -- | +| [DROP MEASUREMENT](/influxdb/v1.8/query_language/manage-database/#delete-measurements-with-drop-measurement) | -- | +| [DROP SHARD](/influxdb/v1.8/query_language/manage-database/#delete-a-shard-with-drop-shard) | -- | +| [CREATE RETENTION POLICY](/influxdb/v1.8/query_language/manage-database/#create-retention-policies-with-create-retention-policy) | -- | +| [ALTER RETENTION POLICY](/influxdb/v1.8/query_language/manage-database/#modify-retention-policies-with-alter-retention-policy) | -- | +| [DROP RETENTION POLICY](/influxdb/v1.8/query_language/manage-database/#delete-retention-policies-with-drop-retention-policy) | -- | +| [COUNT](/influxdb/v1.8/query_language/functions#count) | [count()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/aggregates/count/) | +| [DISTINCT](/influxdb/v1.8/query_language/functions#distinct) | [distinct()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/selectors/distinct/) | +| [INTEGRAL](/influxdb/v1.8/query_language/functions#integral) | [integral()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/aggregates/integral/) | +| [MEAN](/influxdb/v1.8/query_language/functions#mean) | [mean()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/aggregates/mean/) | +| [MEDIAN](/influxdb/v1.8/query_language/functions#median) | [median()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/aggregates/median/) | +| [MODE](/influxdb/v1.8/query_language/functions#mode) | [mode()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/aggregates/mode/) | +| [SPREAD](/influxdb/v1.8/query_language/functions#spread) | [spread()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/aggregates/spread/) | +| [STDDEV](/influxdb/v1.8/query_language/functions#stddev) | [stddev()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/aggregates/stddev/) | +| [SUM](/influxdb/v1.8/query_language/functions#sum) | [sum()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/aggregates/sum/) | +| [BOTTOM](/influxdb/v1.8/query_language/functions#bottom) | [bottom()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/selectors/bottom/) | +| [FIRST](/influxdb/v1.8/query_language/functions#first) | [first()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/selectors/first/) | +| [LAST](/influxdb/v1.8/query_language/functions#last) | [last()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/selectors/last/) | +| [MAX](/influxdb/v1.8/query_language/functions#max) | [max()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/selectors/max/) | +| [MIN](/influxdb/v1.8/query_language/functions#min) | [min()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/selectors/min/) | +| [PERCENTILE](/influxdb/v1.8/query_language/functions#percentile) | [quantile()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/aggregates/quantile/) | +| [SAMPLE](/influxdb/v1.8/query_language/functions#sample) | [sample()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/selectors/sample/) | +| [TOP](/influxdb/v1.8/query_language/functions#top) | [top()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/selectors/top/) | +| [ABS](/influxdb/v1.8/query_language/functions#abs) | [math.abs()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/abs/) | +| [ACOS](/influxdb/v1.8/query_language/functions#acos) | [math.acos()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/acos/) | +| [ASIN](/influxdb/v1.8/query_language/functions#asin) | [math.asin()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/asin/) | +| [ATAN](/influxdb/v1.8/query_language/functions#atan) | [math.atan()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/atan/) | +| [ATAN2](/influxdb/v1.8/query_language/functions#atan2) | [math.atan2()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/atan2/) | +| [CEIL](/influxdb/v1.8/query_language/functions#ceil) | [math.ceil()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/ceil/) | +| [COS](/influxdb/v1.8/query_language/functions#cos) | [math.cos()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/cos/) | +| [CUMULATIVE_SUM](/influxdb/v1.8/query_language/functions#cumulative-sum) | [cumulativeSum()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/cumulativesum/) | +| [DERIVATIVE](/influxdb/v1.8/query_language/functions#derivative) | [derivative()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/derivative/) | +| [DIFFERENCE](/influxdb/v1.8/query_language/functions#difference) | [difference()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/difference/) | +| [ELAPSED](/influxdb/v1.8/query_language/functions#elapsed) | [elapsed()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/elapsed/) | +| [EXP](/influxdb/v1.8/query_language/functions#exp) | [math.exp()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/exp/) | +| [FLOOR](/influxdb/v1.8/query_language/functions#floor) | [math.floor()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/floor/) | +| [HISTOGRAM](/influxdb/v1.8/query_language/functions#histogram) | [histogram()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/histogram/) | +| [LN](/influxdb/v1.8/query_language/functions#ln) | [math.log()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/log/) | +| [LOG](/influxdb/v1.8/query_language/functions#log) | [math.logb()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/logb/) | +| [LOG2](/influxdb/v1.8/query_language/functions#log2) | [math.log2()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/log2/) | +| [LOG10](/influxdb/v1.8/query_language/functions/#log10) | [math.log10()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/log10/) | +| [MOVING_AVERAGE](/influxdb/v1.8/query_language/functions#moving-average) | [movingAverage()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/movingaverage/) | +| [NON_NEGATIVE_DERIVATIVE](/influxdb/v1.8/query_language/functions#non-negative-derivative) | [derivative(nonNegative:true)](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/derivative/) | +| [NON_NEGATIVE_DIFFERENCE](/influxdb/v1.8/query_language/functions#non-negative-difference) | [difference(nonNegative:true)](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/derivative/) | +| [POW](/influxdb/v1.8/query_language/functions#pow) | [math.pow()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/pow/) | +| [ROUND](/influxdb/v1.8/query_language/functions#round) | [math.round()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/round/) | +| [SIN](/influxdb/v1.8/query_language/functions#sin) | [math.sin()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/sin/) | +| [SQRT](/influxdb/v1.8/query_language/functions#sqrt) | [math.sqrt()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/sqrt/) | +| [TAN](/influxdb/v1.8/query_language/functions#tan) | [math.tan()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/math/tan/) | +| [HOLT_WINTERS](/influxdb/v1.8/query_language/functions#holt-winters) | [holtWinters()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/holtwinters/) | +| [CHANDE_MOMENTUM_OSCILLATOR](/influxdb/v1.8/query_language/functions#chande-momentum-oscillator) | [chandeMomentumOscillator()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/chandemomentumoscillator/) | +| [EXPONENTIAL_MOVING_AVERAGE](/influxdb/v1.8/query_language/functions#exponential-moving-average) | [exponentialMovingAverage()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/exponentialmovingaverage/) | +| [DOUBLE_EXPONENTIAL_MOVING_AVERAGE](/influxdb/v1.8/query_language/functions#double-exponential-moving-average) | [doubleEMA()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/doubleema/) | +| [KAUFMANS_EFFICIENCY_RATIO](/influxdb/v1.8/query_language/functions#kaufmans-efficiency-ratio) | [kaufmansER()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/kaufmanser/) | +| [KAUFMANS_ADAPTIVE_MOVING_AVERAGE](/influxdb/v1.8/query_language/functions#kaufmans-adaptive-moving-average) | [kaufmansAMA()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/kaufmansama/) | +| [TRIPLE_EXPONENTIAL_MOVING_AVERAGE](/influxdb/v1.8/query_language/functions#triple-exponential-moving-average) | [tripleEMA()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/tripleema/) | +| [TRIPLE_EXPONENTIAL_DERIVATIVE](/influxdb/v1.8/query_language/functions#triple-exponential-derivative) | [tripleExponentialDerivative()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/tripleexponentialderivative/) | +| [RELATIVE_STRENGTH_INDEX](/influxdb/v1.8/query_language/functions#relative-strength-index) | [relativeStrengthIndex()](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/relativestrengthindex/) | _* The to() function only writes to InfluxDB 2.0._ diff --git a/content/influxdb/v1.8/flux/guides/sql.md b/content/influxdb/v1.8/flux/guides/sql.md index a6a731f56..214f016ce 100644 --- a/content/influxdb/v1.8/flux/guides/sql.md +++ b/content/influxdb/v1.8/flux/guides/sql.md @@ -148,7 +148,7 @@ Sample sensor information is stored in PostgreSQL. `air-sensor-data.rb` is a script that generates air sensor data and stores the data in InfluxDB. To use `air-sensor-data.rb`: -1. [Create a database](/influxdb/v1.8/introduction/getting-started/#creating-a-database) to store the data. +1. [Create a database](/influxdb/v1.8/introduction/get-started/#creating-a-database) to store the data. 2. Download the sample data generator. _This tool requires [Ruby](https://www.ruby-lang.org/en/)._ Download Air Sensor Generator diff --git a/content/influxdb/v1.8/guides/calculate_percentages.md b/content/influxdb/v1.8/guides/calculate_percentages.md index 71de95d87..def83408e 100644 --- a/content/influxdb/v1.8/guides/calculate_percentages.md +++ b/content/influxdb/v1.8/guides/calculate_percentages.md @@ -32,7 +32,7 @@ Learn how to calculate a percentage using the following examples: - [Calculate a percentage from two fields](#calculate-a-percentage-from-two-fields) - [Calculate a percentage using aggregate functions](#calculate-a-percentage-using-aggregate-functions) - [Calculate the percentage of total weight per apple variety](#calculate-the-percentage-of-total-weight-per-apple-variety) -- [Calculate the aggregate percentage per variety](#calculate-the-aggregate-percentage-per-variety) +- [Calculate the aggregate percentage per variety](#calculate-the-percentage-of-total-weight-per-apple-variety) ## Basic calculations within a query @@ -41,7 +41,7 @@ When performing any math operation in a Flux query, you must complete the follow 1. Specify the [bucket](/flux/latest/introduction/getting-started/#buckets) to query from and the time range to query. 2. Filter your data by measurements, fields, and other applicable criteria. 3. Align values in one row (required to perform math in Flux) by using one of the following functions: - - To query **from multiple** data sources, use the [`join()` function](flux/latest/stdlib/built-in/transformations/join). + - To query **from multiple** data sources, use the [`join()` function](/flux/latest/stdlib/built-in/transformations/join/). - To query **from the same** data source, use the [`pivot()` function](/flux/latest/stdlib/built-in/transformations/pivot/). For examples using the `join()` function to calculate percentages and more examples of calculating percentages, see [Calculate percentages with Flux](/flux/latest/guides/calculate-percentages/). diff --git a/content/influxdb/v1.8/guides/downsample_and_retain.md b/content/influxdb/v1.8/guides/downsample_and_retain.md index d68ec22dd..b66021efc 100644 --- a/content/influxdb/v1.8/guides/downsample_and_retain.md +++ b/content/influxdb/v1.8/guides/downsample_and_retain.md @@ -27,7 +27,7 @@ This guide doesn't go into detail about the syntax for creating and managing CQs If you're new to these concepts, we recommend reviewing the following: - [CQ documentation](/influxdb/v1.8/query_language/continuous_queries/) and -- [RP documentation](/influxdb/v1.8/query_language/database_management/#retention-policy-management). +- [RP documentation](/influxdb/v1.8/query_language/manage-database/#retention-policy-management). ### Sample data @@ -81,7 +81,7 @@ We make the `DEFAULT` RP keep data for two hours, because we want InfluxDB to automatically write the incoming ten-second resolution data to that RP. Use the -[`CREATE RETENTION POLICY`](/influxdb/v1.8/query_language/database_management/#create-retention-policies-with-create-retention-policy) +[`CREATE RETENTION POLICY`](/influxdb/v1.8/query_language/manage-database/#create-retention-policies-with-create-retention-policy) statement to create a `DEFAULT` RP: ```sql @@ -112,7 +112,7 @@ Next we want to create another retention policy that keeps data for 52 weeks and Ultimately, the 30-minute rollup data will be stored in this RP. Use the -[`CREATE RETENTION POLICY`](/influxdb/v1.8/query_language/database_management/#create-retention-policies-with-create-retention-policy) +[`CREATE RETENTION POLICY`](/influxdb/v1.8/query_language/manage-database/#create-retention-policies-with-create-retention-policy) statement to create a non-`DEFAULT` retention policy: ```sql @@ -219,5 +219,5 @@ Using a combination of RPs and CQs, we've successfully set up our database to automatically keep the high precision raw data for a limited time, create lower precision data, and store that lower precision data for a longer period of time. Now that you have a general understanding of how these features can work -together, check out the detailed documentation on [CQs](/influxdb/v1.8/query_language/continuous_queries/) and [RPs](/influxdb/v1.8/query_language/database_management/#retention-policy-management) +together, check out the detailed documentation on [CQs](/influxdb/v1.8/query_language/continuous_queries/) and [RPs](/influxdb/v1.8/query_language/manage-database/#retention-policy-management) to see all that they can do for you. diff --git a/content/influxdb/v1.8/guides/query_data.md b/content/influxdb/v1.8/guides/query_data.md index 02fb675ae..a865fd9db 100644 --- a/content/influxdb/v1.8/guides/query_data.md +++ b/content/influxdb/v1.8/guides/query_data.md @@ -106,5 +106,5 @@ While this is useful for debugging or when querying directly with tools like `cu ### InfluxQL -Check out the [Data Exploration page](/influxdb/v1.8/query_language/data_exploration/) to get acquainted with InfluxQL. +Check out the [Data Exploration page](/influxdb/v1.8/query_language/explore-data/) to get acquainted with InfluxQL. For more information about querying data with the InfluxDB API using InfluxQL, see the [API reference documentation](/influxdb/v1.8/tools/api/#influxdb-1-x-http-endpoints). diff --git a/content/influxdb/v1.8/guides/write_data.md b/content/influxdb/v1.8/guides/write_data.md index c4fe516a5..00074427a 100644 --- a/content/influxdb/v1.8/guides/write_data.md +++ b/content/influxdb/v1.8/guides/write_data.md @@ -35,7 +35,7 @@ curl -i -XPOST 'http://localhost:8086/write?db=mydb' --data-binary 'cpu_load_short,host=server01,region=us-west value=0.64 1434055562000000000' ``` -- To **write to a database using the InfluxDB 2.0 API (compatible with InfluxDB 1.8+)**, send `POST` requests to the [`/api/v2/write` endpoint](/influxdb/v1.8/tools/api/#client-libraries): +- To **write to a database using the InfluxDB 2.0 API (compatible with InfluxDB 1.8+)**, send `POST` requests to the [`/api/v2/write` endpoint](/influxdb/v1.8/tools/api/#api-v2-write-http-endpoint): ```bash curl -i -XPOST 'http://localhost:8086/api/v2/write?bucket=db/rp&precision=ns' \ diff --git a/content/influxdb/v1.8/introduction/get-started.md b/content/influxdb/v1.8/introduction/get-started.md index 3850a1ea9..a3ddf9438 100644 --- a/content/influxdb/v1.8/introduction/get-started.md +++ b/content/influxdb/v1.8/introduction/get-started.md @@ -39,7 +39,7 @@ InfluxDB shell 1.8.x * The InfluxDB API runs on port `8086` by default. Therefore, `influx` will connect to port `8086` and `localhost` by default. If you need to alter these defaults, run `influx --help`. -* The [`-precision` argument](/influxdb/v1.8/tools/shell/#influx-options) specifies the format/precision of any returned timestamps. +* The [`-precision` argument](/influxdb/v1.8/tools/shell/#influx-arguments) specifies the format/precision of any returned timestamps. In the example above, `rfc3339` tells InfluxDB to return timestamps in [RFC3339 format](https://www.ietf.org/rfc/rfc3339.txt) (`YYYY-MM-DDTHH:MM:SS.nnnnnnnnnZ`). The command line is now ready to take input in the form of the Influx Query Language (a.k.a InfluxQL) statements. diff --git a/content/influxdb/v1.8/query_language/_index.md b/content/influxdb/v1.8/query_language/_index.md index 1a287a3fe..59826f901 100644 --- a/content/influxdb/v1.8/query_language/_index.md +++ b/content/influxdb/v1.8/query_language/_index.md @@ -19,25 +19,25 @@ Feel free to download the dataset provided in [Sample Data](/influxdb/v1.8/query_language/data_download/) and follow along with the documentation. -#### [Data exploration](/influxdb/v1.8/query_language/data_exploration/) +#### [Data exploration](/influxdb/v1.8/query_language/explore-data/) Covers the query language basics for InfluxQL, including the -[`SELECT` statement](/influxdb/v1.8/query_language/data_exploration/#the-basic-select-statement), -[`GROUP BY` clauses](/influxdb/v1.8/query_language/data_exploration/#the-group-by-clause), -[`INTO` clauses](/influxdb/v1.8/query_language/data_exploration/#the-into-clause), and more. +[`SELECT` statement](/influxdb/v1.8/query_language/explore-data/#the-basic-select-statement), +[`GROUP BY` clauses](/influxdb/v1.8/query_language/explore-data/#the-group-by-clause), +[`INTO` clauses](/influxdb/v1.8/query_language/explore-data/#the-into-clause), and more. See Data Exploration to learn about -[time syntax](/influxdb/v1.8/query_language/data_exploration/#time-syntax) and -[regular expressions](/influxdb/v1.8/query_language/data_exploration/#regular-expressions) in +[time syntax](/influxdb/v1.8/query_language/explore-data/#time-syntax) and +[regular expressions](/influxdb/v1.8/query_language/explore-data/#regular-expressions) in queries. -#### [Schema exploration](/influxdb/v1.8/query_language/schema_exploration/) +#### [Schema exploration](/influxdb/v1.8/query_language/explore-schema/) Covers queries that are useful for viewing and exploring your [schema](/influxdb/v1.8/concepts/glossary/#schema). See Schema Exploration for syntax explanations and examples of InfluxQL's `SHOW` queries. -#### [Database management](/influxdb/v1.8/query_language/database_management/) +#### [Database management](/influxdb/v1.8/query_language/manage-database/) Covers InfluxQL for managing [databases](/influxdb/v1.8/concepts/glossary/#database) and diff --git a/content/influxdb/v1.8/query_language/continuous_queries.md b/content/influxdb/v1.8/query_language/continuous_queries.md index ed95cc3e6..205a90097 100644 --- a/content/influxdb/v1.8/query_language/continuous_queries.md +++ b/content/influxdb/v1.8/query_language/continuous_queries.md @@ -158,7 +158,7 @@ time mean ##### Automatically downsampling data into another retention policy -[Fully qualify](/influxdb/v1.8/query_language/data_exploration/#the-basic-select-statement) +[Fully qualify](/influxdb/v1.8/query_language/explore-data/#the-basic-select-statement) the destination measurement to store the downsampled data in a non-`DEFAULT` [retention policy](/influxdb/v1.8/concepts/glossary/#retention-policy-rp) (RP). @@ -220,7 +220,7 @@ guide for an in-depth discussion about this CQ use case. ##### Automatically downsampling a database with backreferencing Use a function with a wildcard (`*`) and `INTO` query's -[backreferencing syntax](/influxdb/v1.8/query_language/data_exploration/#the-into-clause) +[backreferencing syntax](/influxdb/v1.8/query_language/explore-data/#the-into-clause) to automatically downsample data from all measurements and numerical fields in a database. @@ -289,7 +289,7 @@ time mean_complaints mean_passengers ##### Automatically downsampling data and configuring CQ time boundaries Use an -[offset interval](/influxdb/v1.8/query_language/data_exploration/#advanced-group-by-time-syntax) +[offset interval](/influxdb/v1.8/query_language/explore-data/#advanced-group-by-time-syntax) in the `GROUP BY time()` clause to alter both the CQ's default execution time and preset time boundaries. @@ -357,11 +357,11 @@ CQs do not write any results for a time interval if no data fall within that time range. Note that the basic syntax does not support using -[`fill()`](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals-and-fill) +[`fill()`](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals-and-fill) to change the value reported for intervals with no data. Basic syntax CQs ignore `fill()` if it's included in the CQ query. A possible workaround is to use the -[advanced CQ syntax](#example-4-configuring-cq-time-ranges-and-filling-empty-results). +[advanced CQ syntax](#advanced-syntax). ##### Resampling previous time intervals @@ -375,13 +375,13 @@ time range. CQs operate on realtime data, that is, data with timestamps that occur relative to [`now()`](/influxdb/v1.8/concepts/glossary/#now). Use a basic -[`INTO` query](/influxdb/v1.8/query_language/data_exploration/#the-into-clause) +[`INTO` query](/influxdb/v1.8/query_language/explore-data/#the-into-clause) to backfill results for data with older timestamps. ##### Missing tags in the CQ results By default, all -[`INTO` queries](/influxdb/v1.8/query_language/data_exploration/#the-into-clause) +[`INTO` queries](/influxdb/v1.8/query_language/explore-data/#the-into-clause) convert any tags in the source measurement to fields in the destination measurement. @@ -887,8 +887,8 @@ InfluxQL does not support [`HAVING` clauses](https://en.wikipedia.org/wiki/Havin Get the same functionality by creating a CQ to aggregate the data and querying the CQ results to apply the `HAVING` clause. -> **Note:** InfluxQL supports [subqueries](/influxdb/v1.8/query_language/data_exploration/#subqueries) which also offer similar functionality to `HAVING` clauses. -See [Data Exploration](/influxdb/v1.8/query_language/data_exploration/#subqueries) for more information. +> **Note:** InfluxQL supports [subqueries](/influxdb/v1.8/query_language/explore-data/#subqueries) which also offer similar functionality to `HAVING` clauses. +See [Data Exploration](/influxdb/v1.8/query_language/explore-data/#subqueries) for more information. ##### Example @@ -935,8 +935,8 @@ If your function does not support nesting, you can get the same functionality us the inner-most function. Then simply query the CQ results to calculate the outer-most function. -> **Note:** InfluxQL supports [subqueries](/influxdb/v1.8/query_language/data_exploration/#subqueries) which also offer the same functionality as nested functions. -See [Data Exploration](/influxdb/v1.8/query_language/data_exploration/#subqueries) for more information. +> **Note:** InfluxQL supports [subqueries](/influxdb/v1.8/query_language/explore-data/#subqueries) which also offer the same functionality as nested functions. +See [Data Exploration](/influxdb/v1.8/query_language/explore-data/#subqueries) for more information. ##### Example diff --git a/content/influxdb/v1.8/query_language/explore-data.md b/content/influxdb/v1.8/query_language/explore-data.md index 6121437eb..cb6220db7 100644 --- a/content/influxdb/v1.8/query_language/explore-data.md +++ b/content/influxdb/v1.8/query_language/explore-data.md @@ -8,7 +8,7 @@ menu: weight: 20 parent: InfluxQL aliases: - - /influxdb/v1.8/query_language/data_exploration/ + - /influxdb/v1.8/query_language/explore-data/ --- InfluxQL is an SQL-like query language for interacting with data in InfluxDB. @@ -1735,7 +1735,7 @@ The query above writes all data in the `NOAA_water_database` and `autogen` reten The [backreference](#examples-5) syntax (`:MEASUREMENT`) maintains the source measurement names in the destination database. Note that both the `copy_NOAA_water_database` database and its `autogen` retention policy must exist prior to running the `INTO` query. -See [Database Management](/influxdb/v1.8/query_language/database_management/) +See [Database Management](/influxdb/v1.8/query_language/manage-database/) for how to manage databases and retention policies. The `GROUP BY *` clause [preserves tags](#missing-data) in the source database as tags in the destination database. @@ -1824,7 +1824,7 @@ InfluxDB writes the data to the `where_else` database and to the `autogen` retention policy. Note that both `where_else` and `autogen` must exist prior to running the `INTO` query. -See [Database Management](/influxdb/v1.8/query_language/database_management/) +See [Database Management](/influxdb/v1.8/query_language/manage-database/) for how to manage databases and retention policies. The response shows the number of points (`7605`) that InfluxDB writes to `h2o_feet_copy_2`. @@ -1911,7 +1911,7 @@ in the `FROM` clause and writes the results to measurements with the same name i `where_else` database and the `autogen` retention policy. Note that both `where_else` and `autogen` must exist prior to running the `INTO` query. -See [Database management](/influxdb/v1.8/query_language/database_management/) +See [Database management](/influxdb/v1.8/query_language/manage-database/) for how to manage databases and retention policies. The response shows the number of points (`5`) that InfluxDB writes to the `where_else` @@ -2385,7 +2385,7 @@ SELECT_clause [INTO_clause] FROM_clause [WHERE_clause] [GROUP_BY_clause] [ORDER_ By default, InfluxDB stores and returns timestamps in UTC. The `tz()` clause includes the UTC offset or, if applicable, the UTC Daylight Savings Time (DST) offset to the query's returned timestamps. -The returned timestamps must be in [RFC3339 format](/influxdb/v1.8/query_language/data_exploration/#configuring-the-returned-timestamps) for the UTC offset or UTC DST to appear. +The returned timestamps must be in [RFC3339 format](/influxdb/v1.8/query_language/explore-data/#configuring-the-returned-timestamps) for the UTC offset or UTC DST to appear. The `time_zone` parameter follows the TZ syntax in the [Internet Assigned Numbers Authority time zone database](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones#List) and it requires single quotes. ### Examples diff --git a/content/influxdb/v1.8/query_language/explore-schema.md b/content/influxdb/v1.8/query_language/explore-schema.md index 6e73415c9..1ecfe131e 100644 --- a/content/influxdb/v1.8/query_language/explore-schema.md +++ b/content/influxdb/v1.8/query_language/explore-schema.md @@ -7,7 +7,7 @@ menu: weight: 30 parent: InfluxQL aliases: - - /influxdb/v1.8/query_language/schema_exploration/ + - /influxdb/v1.8/query_language/explore-schema/ --- InfluxQL is an SQL-like query language for interacting with data in InfluxDB. @@ -200,10 +200,10 @@ Supported operators in the `WHERE` clause: `!~` doesn't match against See the Data Exploration page for documentation on the -[`FROM` clause](/influxdb/v1.8/query_language/data_exploration/#the-basic-select-statement), -[`LIMIT` clause](/influxdb/v1.8/query_language/data_exploration/#the-limit-clause), -[`OFFSET` clause](/influxdb/v1.8/query_language/data_exploration/#the-offset-clause), -and on [Regular Expressions in Queries](/influxdb/v1.8/query_language/data_exploration/#regular-expressions). +[`FROM` clause](/influxdb/v1.8/query_language/explore-data/#the-basic-select-statement), +[`LIMIT` clause](/influxdb/v1.8/query_language/explore-data/#the-limit-clause), +[`OFFSET` clause](/influxdb/v1.8/query_language/explore-data/#the-offset-clause), +and on [Regular Expressions in Queries](/influxdb/v1.8/query_language/explore-data/#regular-expressions). ### Examples @@ -432,9 +432,9 @@ Supported operators in the `WHERE` clause: `!~` doesn't match against See the Data Exploration page for documentation on the -[`LIMIT` clause](/influxdb/v1.8/query_language/data_exploration/#the-limit-clause), -[`OFFSET` clause](/influxdb/v1.8/query_language/data_exploration/#the-offset-clause), -and on [Regular expressions in queries](/influxdb/v1.8/query_language/data_exploration/#regular-expressions). +[`LIMIT` clause](/influxdb/v1.8/query_language/explore-data/#the-limit-clause), +[`OFFSET` clause](/influxdb/v1.8/query_language/explore-data/#the-offset-clause), +and on [Regular expressions in queries](/influxdb/v1.8/query_language/explore-data/#regular-expressions). ### Examples @@ -592,10 +592,10 @@ Supported operators in the `WHERE` clause: `!~` doesn't match against See the Data Exploration page for documentation on the -[`FROM` clause](/influxdb/v1.8/query_language/data_exploration/#the-basic-select-statement), -[`LIMIT` clause](/influxdb/v1.8/query_language/data_exploration/#the-limit-clause), -[`OFFSET` clause](/influxdb/v1.8/query_language/data_exploration/#the-offset-clause), -and on [Regular Expressions in Queries](/influxdb/v1.8/query_language/data_exploration/#regular-expressions). +[`FROM` clause](/influxdb/v1.8/query_language/explore-data/#the-basic-select-statement), +[`LIMIT` clause](/influxdb/v1.8/query_language/explore-data/#the-limit-clause), +[`OFFSET` clause](/influxdb/v1.8/query_language/explore-data/#the-offset-clause), +and on [Regular Expressions in Queries](/influxdb/v1.8/query_language/explore-data/#regular-expressions). ### Examples @@ -809,10 +809,10 @@ Supported operators in the `WITH` and `WHERE` clauses: `!~` doesn't match against See the Data Exploration page for documentation on the -[`FROM` clause](/influxdb/v1.8/query_language/data_exploration/#the-basic-select-statement), -[`LIMIT` clause](/influxdb/v1.8/query_language/data_exploration/#the-limit-clause), -[`OFFSET` clause](/influxdb/v1.8/query_language/data_exploration/#the-offset-clause), -and on [Regular Expressions in Queries](/influxdb/v1.8/query_language/data_exploration/#regular-expressions). +[`FROM` clause](/influxdb/v1.8/query_language/explore-data/#the-basic-select-statement), +[`LIMIT` clause](/influxdb/v1.8/query_language/explore-data/#the-limit-clause), +[`OFFSET` clause](/influxdb/v1.8/query_language/explore-data/#the-offset-clause), +and on [Regular Expressions in Queries](/influxdb/v1.8/query_language/explore-data/#regular-expressions). ### Examples @@ -940,7 +940,7 @@ string parameter in the [InfluxDB API](/influxdb/v1.8/tools/api/#query-string-pa The `FROM` clause is also optional. See the Data Exploration page for documentation on the -[`FROM` clause](/influxdb/v1.8/query_language/data_exploration/#the-basic-select-statement). +[`FROM` clause](/influxdb/v1.8/query_language/explore-data/#the-basic-select-statement). > **Note:** A field's data type [can differ](/influxdb/v1.8/troubleshooting/frequently-asked-questions/#how-does-influxdb-handle-field-type-discrepancies-across-shards) across [shards](/influxdb/v1.8/concepts/glossary/#shard). @@ -1178,7 +1178,7 @@ The example below shows how to filter `SHOW TAG KEYS` by approximately one hour #### Example filtering `SHOW TAG KEYS` by time -1. Specify a shard duration on a new database or [alter an existing shard duration](/influxdb/v1.8/query_language/database_management/#modify-retention-policies-with-alter-retention-policy). To specify a 1h shard duration when creating a new database, run the following command: +1. Specify a shard duration on a new database or [alter an existing shard duration](/influxdb/v1.8/query_language/manage-database/#modify-retention-policies-with-alter-retention-policy). To specify a 1h shard duration when creating a new database, run the following command: ```sh > CREATE database mydb with duration 7d REPLICATION 1 SHARD DURATION 1h name myRP; diff --git a/content/influxdb/v1.8/query_language/functions.md b/content/influxdb/v1.8/query_language/functions.md index 3e6165dcf..3db4ef896 100644 --- a/content/influxdb/v1.8/query_language/functions.md +++ b/content/influxdb/v1.8/query_language/functions.md @@ -100,7 +100,7 @@ SELECT COUNT(DISTINCT( [ * | | // ] )) [...] Returns the number of field values associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key). `COUNT(/regular_expression/)` -Returns the number of field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/data_exploration/#regular-expressions). +Returns the number of field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions). `COUNT(*)` Returns the number of field values associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement). @@ -168,8 +168,8 @@ time count ``` The query returns the number of non-null field values in the `water_level` field key. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2015-08-17T23:48:00Z` and `2015-08-18T00:54:00Z` and [groups](/influxdb/v1.8/query_language/data_exploration/#the-group-by-clause) results into 12-minute time intervals and per tag. -The query [fills](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals-and-fill) empty time intervals with `200` and [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points and series returned to seven and one. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2015-08-17T23:48:00Z` and `2015-08-18T00:54:00Z` and [groups](/influxdb/v1.8/query_language/explore-data/#the-group-by-clause) results into 12-minute time intervals and per tag. +The query [fills](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals-and-fill) empty time intervals with `200` and [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points and series returned to seven and one. ##### Count the distinct field values associated with a field key @@ -189,7 +189,7 @@ The query returns the number of unique field values for the `level description` #### COUNT() and fill() Most InfluxQL functions report `null` values for time intervals with no data, and -[`fill()`](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals-and-fill) +[`fill()`](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals-and-fill) replaces that `null` value with the `fill_option`. `COUNT()` reports `0` for time intervals with no data, and `fill()` replaces any `0` values with the `fill_option`. @@ -294,8 +294,8 @@ time distinct ``` The query returns a tabular list of the unique field values in the `level description` field key. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2015-08-17T23:48:00Z` and `2015-08-18T00:54:00Z` and [groups](/influxdb/v1.8/query_language/data_exploration/#the-group-by-clause) results into 12-minute time intervals and per tag. -The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of series returned to one. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2015-08-17T23:48:00Z` and `2015-08-18T00:54:00Z` and [groups](/influxdb/v1.8/query_language/explore-data/#the-group-by-clause) results into 12-minute time intervals and per tag. +The query also [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of series returned to one. ##### Count the distinct field values associated with a field key @@ -314,7 +314,7 @@ The query returns the number of unique field values in the `level description` f #### DISTINCT() and the INTO clause -Using `DISTINCT()` with the [`INTO` clause](/influxdb/v1.8/query_language/data_exploration/#the-into-clause) can cause InfluxDB to overwrite points in the destination measurement. +Using `DISTINCT()` with the [`INTO` clause](/influxdb/v1.8/query_language/explore-data/#the-into-clause) can cause InfluxDB to overwrite points in the destination measurement. `DISTINCT()` often returns several results with the same timestamp; InfluxDB assumes [points](/influxdb/v1.8/concepts/glossary/#point) with the same [series](/influxdb/v1.8/concepts/glossary/#series) and timestamp are duplicate points and simply overwrites any duplicate point with the most recent point in the destination measurement. ##### Example @@ -371,12 +371,12 @@ If the query does not specify the `unit`, the unit defaults to one second (`1s`) Returns the area under the curve for subsequent field values associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key). `INTEGRAL(/regular_expression/)` -Returns the area under the curve for subsequent field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/data_exploration/#regular-expressions). +Returns the area under the curve for subsequent field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions). `INTEGRAL(*)` Returns the average field value associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement). -`INTEGRAL()` does not support [`fill()`](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals-and-fill). `INTEGRAL()` supports int64 and float64 field value [data types](/influxdb/v1.8/write_protocols/line_protocol_reference/#data-types). +`INTEGRAL()` does not support [`fill()`](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals-and-fill). `INTEGRAL()` supports int64 and float64 field value [data types](/influxdb/v1.8/write_protocols/line_protocol_reference/#data-types). #### Examples @@ -461,7 +461,7 @@ time integral ``` The query returns the area under the curve (in minutes) for the field values associated with the `water_level` field key and in the `h2o_feet` measurement. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z`, [groups](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) results into 12-minute intervals, and [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of results returned to one. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z`, [groups](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) results into 12-minute intervals, and [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of results returned to one. ### MEAN() @@ -477,7 +477,7 @@ SELECT MEAN( [ * | | // ] ) [INTO_clause] FROM_c Returns the average field value associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key). `MEAN(/regular_expression/)` -Returns the average field value associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/data_exploration/#regular-expressions). +Returns the average field value associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions). `MEAN(*)` Returns the average field value associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement). @@ -542,8 +542,8 @@ time mean ``` The query returns the average of the values in the `water_level` field key. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2015-08-17T23:48:00Z` and `2015-08-18T00:54:00Z` and [groups](/influxdb/v1.8/query_language/data_exploration/#the-group-by-clause) results into 12-minute time intervals and per tag. -The query [fills](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals-and-fill) empty time intervals with `9.01` and [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points and series returned to seven and one. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2015-08-17T23:48:00Z` and `2015-08-18T00:54:00Z` and [groups](/influxdb/v1.8/query_language/explore-data/#the-group-by-clause) results into 12-minute time intervals and per tag. +The query [fills](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals-and-fill) empty time intervals with `9.01` and [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points and series returned to seven and one. ### MEDIAN() @@ -559,7 +559,7 @@ SELECT MEDIAN( [ * | | // ] ) [INTO_clause] FROM Returns the middle field value associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key). `MEDIAN(/regular_expression/)` -Returns the middle field value associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/data_exploration/#regular-expressions). +Returns the middle field value associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions). `MEDIAN(*)` Returns the middle field value associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement). @@ -627,8 +627,8 @@ time median ``` The query returns the middle field value in the `water_level` field key. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2015-08-17T23:48:00Z` and `2015-08-18T00:54:00Z` and [groups](/influxdb/v1.8/query_language/data_exploration/#the-group-by-clause) results into 12-minute time intervals and per tag. -The query [fills](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals-and-fill) empty time intervals with `700 `, [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points and series returned to seven and one, and [offsets](/influxdb/v1.8/query_language/data_exploration/#the-offset-and-soffset-clauses) the series returned by one. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2015-08-17T23:48:00Z` and `2015-08-18T00:54:00Z` and [groups](/influxdb/v1.8/query_language/explore-data/#the-group-by-clause) results into 12-minute time intervals and per tag. +The query [fills](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals-and-fill) empty time intervals with `700 `, [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points and series returned to seven and one, and [offsets](/influxdb/v1.8/query_language/explore-data/#the-offset-and-soffset-clauses) the series returned by one. ### MODE() @@ -644,7 +644,7 @@ SELECT MODE( [ * | | // ] ) [INTO_clause] FROM_c Returns the most frequent field value associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key). `MODE(/regular_expression/)` -Returns the most frequent field value associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/data_exploration/#regular-expressions). +Returns the most frequent field value associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions). `MODE(*)` Returns the most frequent field value associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement). @@ -710,8 +710,8 @@ time mode ``` The query returns the mode of the values associated with the `water_level` field key. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2015-08-17T23:48:00Z` and `2015-08-18T00:54:00Z` and [groups](/influxdb/v1.8/query_language/data_exploration/#the-group-by-clause) results into 12-minute time intervals and per tag. -The query [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points and series returned to three and one, and it [offsets](/influxdb/v1.8/query_language/data_exploration/#the-offset-and-soffset-clauses) the series returned by one. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2015-08-17T23:48:00Z` and `2015-08-18T00:54:00Z` and [groups](/influxdb/v1.8/query_language/explore-data/#the-group-by-clause) results into 12-minute time intervals and per tag. +The query [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points and series returned to three and one, and it [offsets](/influxdb/v1.8/query_language/explore-data/#the-offset-and-soffset-clauses) the series returned by one. ### SPREAD() @@ -727,7 +727,7 @@ SELECT SPREAD( [ * | | // ] ) [INTO_clause] FROM Returns the difference between the minimum and maximum field values associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key). `SPREAD(/regular_expression/)` -Returns the difference between the minimum and maximum field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/data_exploration/#regular-expressions). +Returns the difference between the minimum and maximum field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions). `SPREAD(*)` Returns the difference between the minimum and maximum field values associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement). @@ -791,8 +791,8 @@ time spread ``` The query returns the difference between the minimum and maximum field values in the `water_level` field key. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2015-08-17T23:48:00Z` and `2015-08-18T00:54:00Z `and [groups](/influxdb/v1.8/query_language/data_exploration/#the-group-by-clause) results into 12-minute time intervals and per tag. -The query [fills](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals-and-fill) empty time intervals with `18`, [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points and series returned to three and one, and [offsets](/influxdb/v1.8/query_language/data_exploration/#the-offset-and-soffset-clauses) the series returned by one. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2015-08-17T23:48:00Z` and `2015-08-18T00:54:00Z `and [groups](/influxdb/v1.8/query_language/explore-data/#the-group-by-clause) results into 12-minute time intervals and per tag. +The query [fills](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals-and-fill) empty time intervals with `18`, [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points and series returned to three and one, and [offsets](/influxdb/v1.8/query_language/explore-data/#the-offset-and-soffset-clauses) the series returned by one. ### STDDEV() @@ -808,7 +808,7 @@ SELECT STDDEV( [ * | | // ] ) [INTO_clause] FROM Returns the standard deviation of field values associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key). `STDDEV(/regular_expression/)` -Returns the standard deviation of field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/data_exploration/#regular-expressions). +Returns the standard deviation of field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions). `STDDEV(*)` Returns the standard deviation of field values associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement). @@ -871,8 +871,8 @@ time stddev ``` The query returns the standard deviation of the field values in the `water_level` field key. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2015-08-17T23:48:00Z` and `2015-08-18T00:54:00Z` and [groups](/influxdb/v1.8/query_language/data_exploration/#the-group-by-clause) results into 12-minute time intervals and per tag. -The query [fills](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals-and-fill) empty time intervals with `18000`, [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points and series returned to two and one, and [offsets](/influxdb/v1.8/query_language/data_exploration/#the-offset-and-soffset-clauses) the series returned by one. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2015-08-17T23:48:00Z` and `2015-08-18T00:54:00Z` and [groups](/influxdb/v1.8/query_language/explore-data/#the-group-by-clause) results into 12-minute time intervals and per tag. +The query [fills](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals-and-fill) empty time intervals with `18000`, [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points and series returned to two and one, and [offsets](/influxdb/v1.8/query_language/explore-data/#the-offset-and-soffset-clauses) the series returned by one. ### SUM() @@ -888,7 +888,7 @@ SELECT SUM( [ * | | // ] ) [INTO_clause] FROM_cl Returns the sum of field values associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key). `SUM(/regular_expression/)` -Returns the sum of field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/data_exploration/#regular-expressions). +Returns the sum of field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions). `SUM(*)` Returns the sums of field values associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement). @@ -953,7 +953,7 @@ time sum ``` The query returns the summed total of the field values in the `water_level` field key. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2015-08-17T23:48:00Z` and `2015-08-18T00:54:00Z` and [groups](/influxdb/v1.8/query_language/data_exploration/#the-group-by-clause) results into 12-minute time intervals and per tag. The query [fills](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals-and-fill) empty time intervals with 18000, and it [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points and series returned to four and one. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2015-08-17T23:48:00Z` and `2015-08-18T00:54:00Z` and [groups](/influxdb/v1.8/query_language/explore-data/#the-group-by-clause) results into 12-minute time intervals and per tag. The query [fills](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals-and-fill) empty time intervals with 18000, and it [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points and series returned to four and one. ## Selectors @@ -981,7 +981,7 @@ Returns the smallest N field values associated with the field key in the parenth > **Notes:** > * `BOTTOM()` returns the field value with the earliest timestamp if there's a tie between two or more values for the smallest value. -* `BOTTOM()` differs from other InfluxQL functions when combined with an [`INTO` clause](/influxdb/v1.8/query_language/data_exploration/#the-into-clause). See the [Common Issues](#common-issues-with-bottom) section for more information. +* `BOTTOM()` differs from other InfluxQL functions when combined with an [`INTO` clause](/influxdb/v1.8/query_language/explore-data/#the-into-clause). See the [Common Issues](#common-issues-with-bottom) section for more information. #### Examples @@ -1049,10 +1049,10 @@ time bottom location 2015-08-18T00:12:00Z 2.028 santa_monica ``` -The query returns the smallest three values in the `water_level` field key for each 24-minute [interval](/influxdb/v1.8/query_language/data_exploration/#basic-group-by-time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:54:00Z`. -It also returns results in [descending timestamp](/influxdb/v1.8/query_language/data_exploration/#order-by-time-desc) order. +The query returns the smallest three values in the `water_level` field key for each 24-minute [interval](/influxdb/v1.8/query_language/explore-data/#basic-group-by-time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:54:00Z`. +It also returns results in [descending timestamp](/influxdb/v1.8/query_language/explore-data/#order-by-time-desc) order. -Notice that the [GROUP BY time() clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) does not override the points’ original timestamps. See [Issue 1](#bottom-with-a-group-by-time-clause) in the section below for a more detailed explanation of that behavior. +Notice that the [GROUP BY time() clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) does not override the points’ original timestamps. See [Issue 1](#bottom-with-a-group-by-time-clause) in the section below for a more detailed explanation of that behavior. #### Common Issues with `BOTTOM()` @@ -1061,7 +1061,7 @@ Notice that the [GROUP BY time() clause](/influxdb/v1.8/query_language/data_expl Queries with `BOTTOM()` and a `GROUP BY time()` clause return the specified number of points per `GROUP BY time()` interval. For -[most `GROUP BY time()` queries](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals), +[most `GROUP BY time()` queries](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals), the returned timestamps mark the start of the `GROUP BY time()` interval. `GROUP BY time()` queries with the `BOTTOM()` function behave differently; they maintain the timestamp of the original data point. @@ -1110,7 +1110,7 @@ time bottom location ##### BOTTOM(), tags, and the INTO clause -When combined with an [`INTO` clause](/influxdb/v1.8/query_language/data_exploration/#the-into-clause) and no [`GROUP BY tag` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-tags), most InfluxQL functions [convert](/influxdb/v1.8/troubleshooting/frequently-asked-questions/#why-are-my-into-queries-missing-data) any tags in the initial data to fields in the newly written data. +When combined with an [`INTO` clause](/influxdb/v1.8/query_language/explore-data/#the-into-clause) and no [`GROUP BY tag` clause](/influxdb/v1.8/query_language/explore-data/#group-by-tags), most InfluxQL functions [convert](/influxdb/v1.8/troubleshooting/frequently-asked-questions/#why-are-my-into-queries-missing-data) any tags in the initial data to fields in the newly written data. This behavior also applies to the `BOTTOM()` function unless `BOTTOM()` includes a tag key as an argument: `BOTTOM(field_key,tag_key(s),N)`. In those cases, the system preserves the specified tag as a tag in the newly written data. @@ -1119,7 +1119,7 @@ In those cases, the system preserves the specified tag as a tag in the newly wri The first query in the codeblock below returns the smallest field values in the `water_level` field key for two tag values associated with the `location` tag key. It also writes those results to the `bottom_water_levels` measurement. -The second query [shows](/influxdb/v1.8/query_language/schema_exploration/#show-tag-keys) that InfluxDB preserved the `location` tag as a tag in the `bottom_water_levels` measurement. +The second query [shows](/influxdb/v1.8/query_language/explore-schema/#show-tag-keys) that InfluxDB preserved the `location` tag as a tag in the `bottom_water_levels` measurement. ```sql > SELECT BOTTOM("water_level","location",2) INTO "bottom_water_levels" FROM "h2o_feet" @@ -1151,7 +1151,7 @@ SELECT FIRST()[,|] [INTO_clause] FROM_claus Returns the oldest field value (determined by timestamp) associated with the field key. `FIRST(/regular_expression/)` -Returns the oldest field value (determined by timestamp) associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/data_exploration/#regular-expressions). +Returns the oldest field value (determined by timestamp) associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions). `FIRST(*)` Returns the oldest field value (determined by timestamp) associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement). @@ -1232,10 +1232,10 @@ time first ``` The query returns the oldest field value (determined by timestamp) in the `water_level` field key. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2015-08-17T23:48:00Z` and `2015-08-18T00:54:00Z` and [groups](/influxdb/v1.8/query_language/data_exploration/#the-group-by-clause) results into 12-minute time intervals and per tag. -The query [fills](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals-and-fill) empty time intervals with `9.01`, and it [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points and series returned to four and one. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2015-08-17T23:48:00Z` and `2015-08-18T00:54:00Z` and [groups](/influxdb/v1.8/query_language/explore-data/#the-group-by-clause) results into 12-minute time intervals and per tag. +The query [fills](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals-and-fill) empty time intervals with `9.01`, and it [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points and series returned to four and one. -Notice that the [`GROUP BY time()` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) overrides the points' original timestamps. +Notice that the [`GROUP BY time()` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) overrides the points' original timestamps. The timestamps in the results indicate the the start of each 12-minute time interval; the first point in the results covers the time interval between `2015-08-17T23:48:00Z` and just before `2015-08-18T00:00:00Z` and the last point in the results covers the time interval between `2015-08-18T00:24:00Z` and just before `2015-08-18T00:36:00Z`. @@ -1253,7 +1253,7 @@ SELECT LAST()[,|] [INTO_clause] FROM_claus Returns the newest field value (determined by timestamp) associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key). `LAST(/regular_expression/)` -Returns the newest field value (determined by timestamp) associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/data_exploration/#regular-expressions). +Returns the newest field value (determined by timestamp) associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions). `LAST(*)` Returns the newest field value (determined by timestamp) associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement). @@ -1334,10 +1334,10 @@ time last ``` The query returns the newest field value (determined by timestamp) in the `water_level` field key. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2015-08-17T23:48:00Z` and `2015-08-18T00:54:00Z` and [groups](/influxdb/v1.8/query_language/data_exploration/#the-group-by-clause) results into 12-minute time intervals and per tag. -The query [fills](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals-and-fill) empty time intervals with `9.01`, and it [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points and series returned to four and one. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2015-08-17T23:48:00Z` and `2015-08-18T00:54:00Z` and [groups](/influxdb/v1.8/query_language/explore-data/#the-group-by-clause) results into 12-minute time intervals and per tag. +The query [fills](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals-and-fill) empty time intervals with `9.01`, and it [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points and series returned to four and one. -Notice that the [`GROUP BY time()` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) overrides the points' original timestamps. +Notice that the [`GROUP BY time()` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) overrides the points' original timestamps. The timestamps in the results indicate the the start of each 12-minute time interval; the first point in the results covers the time interval between `2015-08-17T23:48:00Z` and just before `2015-08-18T00:00:00Z` and the last point in the results covers the time interval between `2015-08-18T00:24:00Z` and just before `2015-08-18T00:36:00Z`. @@ -1355,7 +1355,7 @@ SELECT MAX()[,|] [INTO_clause] FROM_clause Returns the greatest field value associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key). `MAX(/regular_expression/)` -Returns the greatest field value associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/data_exploration/#regular-expressions). +Returns the greatest field value associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions). `MAX(*)` Returns the greatest field value associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement). @@ -1436,10 +1436,10 @@ time max ``` The query returns the greatest field value in the `water_level` field key. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2015-08-17T23:48:00Z` and `2015-08-18T00:54:00Z` and [groups](/influxdb/v1.8/query_language/data_exploration/#the-group-by-clause) results in to 12-minute time intervals and per tag. -The query [fills](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals-and-fill) empty time intervals with `9.01`, and it [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points and series returned to four and one. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2015-08-17T23:48:00Z` and `2015-08-18T00:54:00Z` and [groups](/influxdb/v1.8/query_language/explore-data/#the-group-by-clause) results in to 12-minute time intervals and per tag. +The query [fills](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals-and-fill) empty time intervals with `9.01`, and it [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points and series returned to four and one. -Notice that the [`GROUP BY time()` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) overrides the points’ original timestamps. +Notice that the [`GROUP BY time()` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) overrides the points’ original timestamps. The timestamps in the results indicate the the start of each 12-minute time interval; the first point in the results covers the time interval between `2015-08-17T23:48:00Z` and just before `2015-08-18T00:00:00Z` and the last point in the results covers the time interval between `2015-08-18T00:24:00Z` and just before `2015-08-18T00:36:00Z`. @@ -1457,7 +1457,7 @@ SELECT MIN()[,|] [INTO_clause] FROM_clause Returns the lowest field value associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key). `MIN(/regular_expression/)` -Returns the lowest field value associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/data_exploration/#regular-expressions). +Returns the lowest field value associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions). `MIN(*)` Returns the lowest field value associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement). @@ -1538,10 +1538,10 @@ time min ``` The query returns the lowest field value in the `water_level` field key. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2015-08-17T23:48:00Z` and `2015-08-18T00:54:00Z` and [groups](/influxdb/v1.8/query_language/data_exploration/#the-group-by-clause) results in to 12-minute time intervals and per tag. -The query [fills](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals-and-fill) empty time intervals with `9.01`, and it [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points and series returned to four and one. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2015-08-17T23:48:00Z` and `2015-08-18T00:54:00Z` and [groups](/influxdb/v1.8/query_language/explore-data/#the-group-by-clause) results in to 12-minute time intervals and per tag. +The query [fills](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals-and-fill) empty time intervals with `9.01`, and it [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points and series returned to four and one. -Notice that the [`GROUP BY time()` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) overrides the points’ original timestamps. +Notice that the [`GROUP BY time()` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) overrides the points’ original timestamps. The timestamps in the results indicate the the start of each 12-minute time interval; the first point in the results covers the time interval between `2015-08-17T23:48:00Z` and just before `2015-08-18T00:00:00Z` and the last point in the results covers the time interval between `2015-08-18T00:24:00Z` and just before `2015-08-18T00:36:00Z`. @@ -1559,7 +1559,7 @@ SELECT PERCENTILE(, )[,|] [INTO_clause] Returns the Nth percentile field value associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key). `PERCENTILE(/regular_expression/,N)` -Returns the Nth percentile field value associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/data_exploration/#regular-expressions). +Returns the Nth percentile field value associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions). `PERCENTILE(*,N)` Returns the Nth percentile field value associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement). @@ -1638,10 +1638,10 @@ time percentile ``` The query returns the field value that is larger than 20 percent of the values in the `water_level` field key. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2015-08-17T23:48:00Z` and `2015-08-18T00:54:00Z` and [groups](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) results into 24-minute intervals. -It [fills](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals-and-fill) empty time intervals with `15` and it [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points returned to two. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2015-08-17T23:48:00Z` and `2015-08-18T00:54:00Z` and [groups](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) results into 24-minute intervals. +It [fills](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals-and-fill) empty time intervals with `15` and it [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points returned to two. -Notice that the [`GROUP BY time()` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) overrides the points’ original timestamps. +Notice that the [`GROUP BY time()` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) overrides the points’ original timestamps. The timestamps in the results indicate the the start of each 24-minute time interval; the first point in the results covers the time interval between `2015-08-17T23:36:00Z` and just before `2015-08-18T00:00:00Z` and the last point in the results covers the time interval between `2015-08-18T00:00:00Z` and just before `2015-08-18T00:24:00Z`. #### Common Issues with PERCENTILE() @@ -1667,7 +1667,7 @@ SELECT SAMPLE(, )[,|] [INTO_clause] FROM Returns N randomly selected field values associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key). `SAMPLE(/regular_expression/,N)` -Returns N randomly selected field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/data_exploration/#regular-expressions). +Returns N randomly selected field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions). `SAMPLE(*,N)` Returns N randomly selected field values associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement). @@ -1754,9 +1754,9 @@ time sample ``` The query returns one randomly selected point from the `water_level` field key. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and [groups](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) results into 18-minute intervals. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and [groups](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) results into 18-minute intervals. -Notice that the [`GROUP BY time()` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) does not override the points' original timestamps. +Notice that the [`GROUP BY time()` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) does not override the points' original timestamps. See [Issue 1](#sample-with-a-group-by-time-clause) in the section below for a more detailed explanation of that behavior. #### Common Issues with `SAMPLE()` @@ -1766,7 +1766,7 @@ See [Issue 1](#sample-with-a-group-by-time-clause) in the section below for a mo Queries with `SAMPLE()` and a `GROUP BY time()` clause return the specified number of points (`N`) per `GROUP BY time()` interval. For -[most `GROUP BY time()` queries](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals), +[most `GROUP BY time()` queries](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals), the returned timestamps mark the start of the `GROUP BY time()` interval. `GROUP BY time()` queries with the `SAMPLE()` function behave differently; they maintain the timestamp of the original data point. @@ -1818,7 +1818,7 @@ Returns the greatest N field values associated with the field key in the parenth > **Notes:** > * `TOP()` returns the field value with the earliest timestamp if there's a tie between two or more values for the greatest value. -* `TOP()` differs from other InfluxQL functions when combined with an [`INTO` clause](/influxdb/v1.8/query_language/data_exploration/#the-into-clause). +* `TOP()` differs from other InfluxQL functions when combined with an [`INTO` clause](/influxdb/v1.8/query_language/explore-data/#the-into-clause). See the [Common Issues](#common-issues-with-top) section for more information. #### Examples @@ -1887,10 +1887,10 @@ time top location 2015-08-18T00:12:00Z 7.887 coyote_creek ``` -The query returns the greatest three values in the `water_level` field key for each 24-minute [interval](/influxdb/v1.8/query_language/data_exploration/#basic-group-by-time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:54:00Z`. -It also returns results in [descending timestamp](/influxdb/v1.8/query_language/data_exploration/#order-by-time-desc) order. +The query returns the greatest three values in the `water_level` field key for each 24-minute [interval](/influxdb/v1.8/query_language/explore-data/#basic-group-by-time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:54:00Z`. +It also returns results in [descending timestamp](/influxdb/v1.8/query_language/explore-data/#order-by-time-desc) order. -Notice that the [GROUP BY time() clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) does not override the points’ original timestamps. +Notice that the [GROUP BY time() clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) does not override the points’ original timestamps. See [Issue 1](#top-with-a-group-by-time-clause) in the section below for a more detailed explanation of that behavior. #### Common Issues with `TOP()` @@ -1900,7 +1900,7 @@ See [Issue 1](#top-with-a-group-by-time-clause) in the section below for a more Queries with `TOP()` and a `GROUP BY time()` clause return the specified number of points per `GROUP BY time()` interval. For -[most `GROUP BY time()` queries](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals), +[most `GROUP BY time()` queries](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals), the returned timestamps mark the start of the `GROUP BY time()` interval. `GROUP BY time()` queries with the `TOP()` function behave differently; they maintain the timestamp of the original data point. @@ -1950,7 +1950,7 @@ time top location ##### TOP(), tags, and the INTO clause -When combined with an [`INTO` clause](/influxdb/v1.8/query_language/data_exploration/#the-into-clause) and no [`GROUP BY tag` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-tags), most InfluxQL functions [convert](/influxdb/v1.8/troubleshooting/frequently-asked-questions/#why-are-my-into-queries-missing-data) any tags in the initial data to fields in the newly written data. +When combined with an [`INTO` clause](/influxdb/v1.8/query_language/explore-data/#the-into-clause) and no [`GROUP BY tag` clause](/influxdb/v1.8/query_language/explore-data/#group-by-tags), most InfluxQL functions [convert](/influxdb/v1.8/troubleshooting/frequently-asked-questions/#why-are-my-into-queries-missing-data) any tags in the initial data to fields in the newly written data. This behavior also applies to the `TOP()` function unless `TOP()` includes a tag key as an argument: `TOP(field_key,tag_key(s),N)`. In those cases, the system preserves the specified tag as a tag in the newly written data. @@ -1959,7 +1959,7 @@ In those cases, the system preserves the specified tag as a tag in the newly wri The first query in the codeblock below returns the greatest field values in the `water_level` field key for two tag values associated with the `location` tag key. It also writes those results to the `top_water_levels` measurement. -The second query [shows](/influxdb/v1.8/query_language/schema_exploration/#show-tag-keys) that InfluxDB preserved the `location` tag as a tag in the `top_water_levels` measurement. +The second query [shows](/influxdb/v1.8/query_language/explore-schema/#show-tag-keys) that InfluxDB preserved the `location` tag as a tag in the `top_water_levels` measurement. ```sql > SELECT TOP("water_level","location",2) INTO "top_water_levels" FROM "h2o_feet" @@ -1993,14 +1993,14 @@ SELECT ABS( [ * | ] ) [INTO_clause] FROM_clause [WHERE_clause] [GROU Returns the absolute values of field values associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key). +Returns the absolute value of field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions). --> `ABS(*)` Returns the absolute values of field values associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement). `ABS()` supports int64 and float64 field value [data types](/influxdb/v1.8/write_protocols/line_protocol_reference/#data-types). -The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/data_exploration/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals). +The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/explore-data/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals). See the [Advanced Syntax](#advanced-syntax) section for how to use `ABS()` with a `GROUP BY time()` clause. ##### Examples @@ -2091,8 +2091,8 @@ time abs ``` The query returns the absolute values of field values associated with the `a` field key. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2018-06-24T12:00:00Z` and `2018-06-24T12:05:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/data_exploration/#order-by-time-desc). -The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/data_exploration/#the-offset-and-soffset-clauses) results by two points. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2018-06-24T12:00:00Z` and `2018-06-24T12:05:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/explore-data/#order-by-time-desc). +The query also [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/explore-data/#the-offset-and-soffset-clauses) results by two points. #### Advanced syntax @@ -2100,7 +2100,7 @@ The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limi SELECT ABS(( [ * | ] )) [INTO_clause] FROM_clause [WHERE_clause] GROUP_BY_clause [ORDER_BY_clause] [LIMIT_clause] [OFFSET_clause] [SLIMIT_clause] [SOFFSET_clause] ``` -The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) and a nested InfluxQL function. +The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) and a nested InfluxQL function. The query first calculates the results for the nested function at the specified `GROUP BY time()` interval and then applies the `ABS()` function to those results. `ABS()` supports the following nested functions: @@ -2168,14 +2168,14 @@ SELECT ACOS( [ * | ] ) [INTO_clause] FROM_clause [WHERE_clause] [GRO Returns the arccosine of field values associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key). +Returns the arccosine of field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions). --> `ACOS(*)` Returns the arccosine of field values associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement). `ACOS()` supports int64 and float64 field value [data types](/influxdb/v1.8/write_protocols/line_protocol_reference/#data-types) with values between -1 and 1. -The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/data_exploration/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals). +The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/explore-data/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals). See the [Advanced Syntax](#advanced-syntax) section for how to use `ACOS()` with a `GROUP BY time()` clause. ##### Examples @@ -2277,8 +2277,8 @@ time acos ``` The query returns arccosine of field values associated with the `of_capacity` field key. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2017-05-01T00:00:00Z` and `2017-05-09T00:00:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/data_exploration/#order-by-time-desc). -The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/data_exploration/#the-offset-and-soffset-clauses) results by two points. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2017-05-01T00:00:00Z` and `2017-05-09T00:00:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/explore-data/#order-by-time-desc). +The query also [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/explore-data/#the-offset-and-soffset-clauses) results by two points. #### Advanced syntax @@ -2286,7 +2286,7 @@ The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limi SELECT ACOS(( [ * | ] )) [INTO_clause] FROM_clause [WHERE_clause] GROUP_BY_clause [ORDER_BY_clause] [LIMIT_clause] [OFFSET_clause] [SLIMIT_clause] [SOFFSET_clause] ``` -The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) and a nested InfluxQL function. +The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) and a nested InfluxQL function. The query first calculates the results for the nested function at the specified `GROUP BY time()` interval and then applies the `ACOS()` function to those results. `ACOS()` supports the following nested functions: @@ -2350,14 +2350,14 @@ SELECT ASIN( [ * | ] ) [INTO_clause] FROM_clause [WHERE_clause] [GRO Returns the arcsine of field values associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key). +Returns the arcsine of field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions). --> `ASIN(*)` Returns the arcsine of field values associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement). `ASIN()` supports int64 and float64 field value [data types](/influxdb/v1.8/write_protocols/line_protocol_reference/#data-types) with values between -1 and 1. -The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/data_exploration/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals). +The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/explore-data/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals). See the [Advanced Syntax](#advanced-syntax) section for how to use `ASIN()` with a `GROUP BY time()` clause. ##### Examples @@ -2459,8 +2459,8 @@ time asin ``` The query returns arcsine of field values associated with the `of_capacity` field key. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2017-05-01T00:00:00Z` and `2017-05-09T00:00:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/data_exploration/#order-by-time-desc). -The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/data_exploration/#the-offset-and-soffset-clauses) results by two points. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2017-05-01T00:00:00Z` and `2017-05-09T00:00:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/explore-data/#order-by-time-desc). +The query also [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/explore-data/#the-offset-and-soffset-clauses) results by two points. #### Advanced syntax @@ -2468,7 +2468,7 @@ The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limi SELECT ASIN(( [ * | ] )) [INTO_clause] FROM_clause [WHERE_clause] GROUP_BY_clause [ORDER_BY_clause] [LIMIT_clause] [OFFSET_clause] [SLIMIT_clause] [SOFFSET_clause] ``` -The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) and a nested InfluxQL function. +The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) and a nested InfluxQL function. The query first calculates the results for the nested function at the specified `GROUP BY time()` interval and then applies the `ASIN()` function to those results. `ASIN()` supports the following nested functions: @@ -2532,14 +2532,14 @@ SELECT ATAN( [ * | ] ) [INTO_clause] FROM_clause [WHERE_clause] [GRO Returns the arctangent of field values associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key). +Returns the arctangent of field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions). --> `ATAN(*)` Returns the arctangent of field values associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement). `ATAN()` supports int64 and float64 field value [data types](/influxdb/v1.8/write_protocols/line_protocol_reference/#data-types) with values between -1 and 1. -The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/data_exploration/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals). +The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/explore-data/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals). See the [Advanced Syntax](#advanced-syntax) section for how to use `ATAN()` with a `GROUP BY time()` clause. ##### Examples @@ -2641,8 +2641,8 @@ time atan ``` The query returns arctangent of field values associated with the `of_capacity` field key. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2017-05-01T00:00:00Z` and `2017-05-09T00:00:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/data_exploration/#order-by-time-desc). -The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/data_exploration/#the-offset-and-soffset-clauses) results by two points. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2017-05-01T00:00:00Z` and `2017-05-09T00:00:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/explore-data/#order-by-time-desc). +The query also [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/explore-data/#the-offset-and-soffset-clauses) results by two points. #### Advanced syntax @@ -2650,7 +2650,7 @@ The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limi SELECT ATAN(( [ * | ] )) [INTO_clause] FROM_clause [WHERE_clause] GROUP_BY_clause [ORDER_BY_clause] [LIMIT_clause] [OFFSET_clause] [SLIMIT_clause] [SOFFSET_clause] ``` -The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) and a nested InfluxQL function. +The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) and a nested InfluxQL function. The query first calculates the results for the nested function at the specified `GROUP BY time()` interval and then applies the `ATAN()` function to those results. `ATAN()` supports the following nested functions: @@ -2714,7 +2714,7 @@ SELECT ATAN2( [ * | | num ], [ | num ] ) [INTO_clause] F Returns the arctangent of field values associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key), `field_key_y`, divided by field values associated with `field_key_x`. `ATAN2(*, field_key_x)` @@ -2723,7 +2723,7 @@ divided by field values associated with `field_key_x`. `ATAN2()` supports int64 and float64 field value [data types](/influxdb/v1.8/write_protocols/line_protocol_reference/#data-types). -The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/data_exploration/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals). +The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/explore-data/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals). See the [Advanced Syntax](#advanced-syntax) section for how to use `ATAN2()` with a `GROUP BY time()` clause. ##### Examples @@ -2831,8 +2831,8 @@ time atan2 ``` The query returns the arctangent of field values associated with the `altitude_ft` field key divided by the `distance_ft` field key. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2018-05-16T12:10:00Z` and `2018-05-16T12:10:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/data_exploration/#order-by-time-desc). -The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/data_exploration/#the-offset-and-soffset-clauses) results by two points. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2018-05-16T12:10:00Z` and `2018-05-16T12:10:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/explore-data/#order-by-time-desc). +The query also [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/explore-data/#the-offset-and-soffset-clauses) results by two points. #### Advanced syntax @@ -2840,7 +2840,7 @@ The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limi SELECT ATAN2(, ) [INTO_clause] FROM_clause [WHERE_clause] GROUP_BY_clause [ORDER_BY_clause] [LIMIT_clause] [OFFSET_clause] [SLIMIT_clause] [SOFFSET_clause] ``` -The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) and a nested InfluxQL function. +The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) and a nested InfluxQL function. The query first calculates the results for the nested function at the specified `GROUP BY time()` interval and then applies the `ATAN2()` function to those results. `ATAN2()` supports the following nested functions: @@ -2908,14 +2908,14 @@ SELECT CEIL( [ * | ] ) [INTO_clause] FROM_clause [WHERE_clause] [GRO Returns the field values associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key) rounded up to the nearest integer. +Returns the field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions) rounded up to the nearest integer. --> `CEIL(*)` Returns the field values associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement) rounded up to the nearest integer. `CEIL()` supports int64 and float64 field value [data types](/influxdb/v1.8/write_protocols/line_protocol_reference/#data-types). -The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/data_exploration/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals). +The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/explore-data/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals). See the [Advanced Syntax](#advanced-syntax) section for how to use `CEIL()` with a `GROUP BY time()` clause. ##### Examples @@ -3005,8 +3005,8 @@ time ceil ``` The query returns field values associated with the `water_level` field key rounded up to the nearest integer. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/data_exploration/#order-by-time-desc). -The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/data_exploration/#the-offset-and-soffset-clauses) results by two points. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/explore-data/#order-by-time-desc). +The query also [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/explore-data/#the-offset-and-soffset-clauses) results by two points. #### Advanced syntax @@ -3014,7 +3014,7 @@ The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limi SELECT CEIL(( [ * | | // ] )) [INTO_clause] FROM_clause [WHERE_clause] GROUP_BY_clause [ORDER_BY_clause] [LIMIT_clause] [OFFSET_clause] [SLIMIT_clause] [SOFFSET_clause] ``` -The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) and a nested InfluxQL function. +The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) and a nested InfluxQL function. The query first calculates the results for the nested function at the specified `GROUP BY time()` interval and then applies the `CEIL()` function to those results. `CEIL()` supports the following nested functions: @@ -3076,14 +3076,14 @@ SELECT COS( [ * | ] ) [INTO_clause] FROM_clause [WHERE_clause] [GROU Returns the cosine of field values associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key). +Returns the cosine of field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions). --> `COS(*)` Returns the cosine of field values associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement). `COS()` supports int64 and float64 field value [data types](/influxdb/v1.8/write_protocols/line_protocol_reference/#data-types). -The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/data_exploration/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals). +The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/explore-data/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals). See the [Advanced Syntax](#advanced-syntax) section for how to use `COS()` with a `GROUP BY time()` clause. ##### Examples @@ -3173,8 +3173,8 @@ time cos ``` The query returns cosine of field values associated with the `water_level` field key. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/data_exploration/#order-by-time-desc). -The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/data_exploration/#the-offset-and-soffset-clauses) results by two points. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/explore-data/#order-by-time-desc). +The query also [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/explore-data/#the-offset-and-soffset-clauses) results by two points. #### Advanced syntax @@ -3182,7 +3182,7 @@ The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limi SELECT COS(( [ * | ] )) [INTO_clause] FROM_clause [WHERE_clause] GROUP_BY_clause [ORDER_BY_clause] [LIMIT_clause] [OFFSET_clause] [SLIMIT_clause] [SOFFSET_clause] ``` -The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) and a nested InfluxQL function. +The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) and a nested InfluxQL function. The query first calculates the results for the nested function at the specified `GROUP BY time()` interval and then applies the `COS()` function to those results. `COS()` supports the following nested functions: @@ -3244,14 +3244,14 @@ SELECT CUMULATIVE_SUM( [ * | | // ] ) [INTO_clau Returns the running total of subsequent field values associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key). `CUMULATIVE_SUM(/regular_expression/)` -Returns the running total of subsequent field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/data_exploration/#regular-expressions). +Returns the running total of subsequent field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions). `CUMULATIVE_SUM(*)` Returns the running total of subsequent field values associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement). `CUMULATIVE_SUM()` supports int64 and float64 field value [data types](/influxdb/v1.8/write_protocols/line_protocol_reference/#data-types). -The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/data_exploration/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals). +The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/explore-data/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals). See the [Advanced Syntax](#advanced-syntax) section for how to use `CUMULATIVE_SUM()` with a `GROUP BY time()` clause. ##### Examples @@ -3342,8 +3342,8 @@ time cumulative_sum ``` The query returns the running total of the field values associated with the `water_level` field key. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/data_exploration/#order-by-time-desc). -The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/data_exploration/#the-offset-and-soffset-clauses) results by two points. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/explore-data/#order-by-time-desc). +The query also [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/explore-data/#the-offset-and-soffset-clauses) results by two points. #### Advanced syntax @@ -3351,7 +3351,7 @@ The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limi SELECT CUMULATIVE_SUM(( [ * | | // ] )) [INTO_clause] FROM_clause [WHERE_clause] GROUP_BY_clause [ORDER_BY_clause] [LIMIT_clause] [OFFSET_clause] [SLIMIT_clause] [SOFFSET_clause] ``` -The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) and a nested InfluxQL function. +The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) and a nested InfluxQL function. The query first calculates the results for the nested function at the specified `GROUP BY time()` interval and then applies the `CUMULATIVE_SUM()` function to those results. `CUMULATIVE_SUM()` supports the following nested functions: @@ -3419,14 +3419,14 @@ If the query does not specify the `unit` the unit defaults to one second (`1s`). Returns the rate of change between subsequent field values associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key). `DERIVATIVE(/regular_expression/)` -Returns the rate of change between subsequent field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/data_exploration/#regular-expressions). +Returns the rate of change between subsequent field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions). `DERIVATIVE(*)` Returns the rate of change between subsequent field values associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement). `DERIVATIVE()` supports int64 and float64 field value [data types](/influxdb/v1.8/write_protocols/line_protocol_reference/#data-types). -The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/data_exploration/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals). +The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/explore-data/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals). See the [Advanced Syntax](#advanced-syntax-1) section for how to use `DERIVATIVE()` with a `GROUP BY time()` clause. ##### Examples @@ -3573,8 +3573,8 @@ time derivative ``` The query returns the one-second rate of change between the field values associated with the `water_level` field key and in the `h2o_feet` measurement. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/data_exploration/#order-by-time-desc). -The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points returned to one and [offsets](/influxdb/v1.8/query_language/data_exploration/#the-offset-and-soffset-clauses) results by two points. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/explore-data/#order-by-time-desc). +The query also [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points returned to one and [offsets](/influxdb/v1.8/query_language/explore-data/#the-offset-and-soffset-clauses) results by two points. The only result (`-0.0002722222222222218`) is the one-second rate of change between the relevant subsequent field values in the raw data. InfluxDB calculates the difference between the field values and normalizes that value to the one-second rate of change: @@ -3593,7 +3593,7 @@ second field value - first field value SELECT DERIVATIVE( ([ * | | // ]) [ , ] ) [INTO_clause] FROM_clause [WHERE_clause] GROUP_BY_clause [ORDER_BY_clause] [LIMIT_clause] [OFFSET_clause] [SLIMIT_clause] [SOFFSET_clause] ``` -The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) and a nested InfluxQL function. +The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) and a nested InfluxQL function. The query first calculates the results for the nested function at the specified `GROUP BY time()` interval and then applies the `DERIVATIVE()` function to those results. The `unit` argument is an integer followed by a [duration literal](/influxdb/v1.8/query_language/spec/#literals) and it is optional. @@ -3708,14 +3708,14 @@ SELECT DIFFERENCE( [ * | | // ] ) [INTO_clause] Returns the difference between subsequent field values associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key). `DIFFERENCE(/regular_expression/)` -Returns the difference between subsequent field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/data_exploration/#regular-expressions). +Returns the difference between subsequent field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions). `DIFFERENCE(*)` Returns the difference between subsequent field values associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement). `DIFFERENCE()` supports int64 and float64 field value [data types](/influxdb/v1.8/write_protocols/line_protocol_reference/#data-types). -The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/data_exploration/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals). +The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/explore-data/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals). See the [Advanced Syntax](#advanced-syntax-2) section for how to use `DIFFERENCE()` with a `GROUP BY time()` clause. ##### Examples @@ -3801,8 +3801,8 @@ time difference ``` The query returns the difference between the subsequent field values in the `water_level` field key. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/data_exploration/#order-by-time-desc). -They query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points returned to two and [offsets](/influxdb/v1.8/query_language/data_exploration/#the-offset-and-soffset-clauses) results by two points. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/explore-data/#order-by-time-desc). +They query also [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points returned to two and [offsets](/influxdb/v1.8/query_language/explore-data/#the-offset-and-soffset-clauses) results by two points. #### Advanced syntax @@ -3810,7 +3810,7 @@ They query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-lim SELECT DIFFERENCE(( [ * | | // ] )) [INTO_clause] FROM_clause [WHERE_clause] GROUP_BY_clause [ORDER_BY_clause] [LIMIT_clause] [OFFSET_clause] [SLIMIT_clause] [SOFFSET_clause] ``` -The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) and a nested InfluxQL function. +The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) and a nested InfluxQL function. The query first calculates the results for the nested function at the specified `GROUP BY time()` interval and then applies the `DIFFERENCE()` function to those results. `DIFFERENCE()` supports the following nested functions: @@ -3876,7 +3876,7 @@ If the query does not specify the `unit` option the query returns the difference Returns the difference between subsequent timestamps associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key). `ELAPSED(/regular_expression/)` -Returns the difference between subsequent timestamps associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/data_exploration/#regular-expressions). +Returns the difference between subsequent timestamps associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions). `ELAPSED(*)` Returns the difference between subsequent timestamps associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement). @@ -3968,10 +3968,10 @@ time elapsed ``` The query returns the difference (in milliseconds) between subsequent timestamps in the `water_level` field key and in the `h2o_feet` measurement. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:12:00Z` and sorts timestamps in [descending order](/influxdb/v1.8/query_language/data_exploration/#order-by-time-desc). -The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points returned to one and [offsets](/influxdb/v1.8/query_language/data_exploration/#the-offset-and-soffset-clauses) results by one point. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:12:00Z` and sorts timestamps in [descending order](/influxdb/v1.8/query_language/explore-data/#order-by-time-desc). +The query also [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points returned to one and [offsets](/influxdb/v1.8/query_language/explore-data/#the-offset-and-soffset-clauses) results by one point. -Notice that the result is negative; the [`ORDER BY time DESC` clause](/influxdb/v1.8/query_language/data_exploration/#order-by-time-desc) sorts timestamps in descending order so `ELAPSED()` calculates the difference between timestamps in reverse order. +Notice that the result is negative; the [`ORDER BY time DESC` clause](/influxdb/v1.8/query_language/explore-data/#order-by-time-desc) sorts timestamps in descending order so `ELAPSED()` calculates the difference between timestamps in reverse order. ### Common Issues with ELAPSED() @@ -3996,7 +3996,7 @@ time elapsed #### ELAPSED() with GROUP BY time() clauses -The `ELAPSED()` function supports the [`GROUP BY time()` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) but the query results aren't particularly useful. +The `ELAPSED()` function supports the [`GROUP BY time()` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) but the query results aren't particularly useful. Currently, an `ELAPSED()` query with a nested function and a `GROUP BY time()` clause simply returns the interval specified in the `GROUP BY time()` clause. The `GROUP BY time()` clause determines the timestamps in the results; each timestamp marks the start of a time interval. @@ -4047,14 +4047,14 @@ SELECT EXP( [ * | ] ) [INTO_clause] FROM_clause [WHERE_clause] [GROU Returns the exponential of field values associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key). +Returns the exponential of field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions). --> `EXP(*)` Returns the exponential of field values associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement). `EXP()` supports int64 and float64 field value [data types](/influxdb/v1.8/write_protocols/line_protocol_reference/#data-types). -The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/data_exploration/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals). +The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/explore-data/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals). See the [Advanced Syntax](#advanced-syntax) section for how to use `EXP()` with a `GROUP BY time()` clause. ##### Examples @@ -4146,8 +4146,8 @@ time exp ``` The query returns the exponentials of field values associated with the `water_level` field key. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/data_exploration/#order-by-time-desc). -The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/data_exploration/#the-offset-and-soffset-clauses) results by two points. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/explore-data/#order-by-time-desc). +The query also [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/explore-data/#the-offset-and-soffset-clauses) results by two points. #### Advanced syntax @@ -4155,7 +4155,7 @@ The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limi SELECT EXP(( [ * | ] )) [INTO_clause] FROM_clause [WHERE_clause] GROUP_BY_clause [ORDER_BY_clause] [LIMIT_clause] [OFFSET_clause] [SLIMIT_clause] [SOFFSET_clause] ``` -The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) and a nested InfluxQL function. +The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) and a nested InfluxQL function. The query first calculates the results for the nested function at the specified `GROUP BY time()` interval and then applies the `EXP()` function to those results. `EXP()` supports the following nested functions: @@ -4217,14 +4217,14 @@ SELECT FLOOR( [ * | ] ) [INTO_clause] FROM_clause [WHERE_clause] [GR Returns the field values associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key) rounded down to the nearest integer. +Returns the field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions) rounded down to the nearest integer. --> `FLOOR(*)` Returns the field values associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement) rounded down to the nearest integer. `FLOOR()` supports int64 and float64 field value [data types](/influxdb/v1.8/write_protocols/line_protocol_reference/#data-types). -The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/data_exploration/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals). +The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/explore-data/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals). See the [Advanced Syntax](#advanced-syntax) section for how to use `FLOOR()` with a `GROUP BY time()` clause. ##### Examples @@ -4314,8 +4314,8 @@ time floor ``` The query returns field values associated with the `water_level` field key rounded down to the nearest integer. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/data_exploration/#order-by-time-desc). -The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/data_exploration/#the-offset-and-soffset-clauses) results by two points. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/explore-data/#order-by-time-desc). +The query also [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/explore-data/#the-offset-and-soffset-clauses) results by two points. #### Advanced syntax @@ -4323,7 +4323,7 @@ The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limi SELECT FLOOR(( [ * | ] )) [INTO_clause] FROM_clause [WHERE_clause] GROUP_BY_clause [ORDER_BY_clause] [LIMIT_clause] [OFFSET_clause] [SLIMIT_clause] [SOFFSET_clause] ``` -The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) and a nested InfluxQL function. +The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) and a nested InfluxQL function. The query first calculates the results for the nested function at the specified `GROUP BY time()` interval and then applies the `FLOOR()` function to those results. `FLOOR()` supports the following nested functions: @@ -4391,14 +4391,14 @@ SELECT LN( [ * | ] ) [INTO_clause] FROM_clause [WHERE_clause] [GROUP Returns the natural logarithm of field values associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key). +Returns the natural logarithm of field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions). --> `LN(*)` Returns the natural logarithm of field values associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement). `LN()` supports int64 and float64 field value [data types](/influxdb/v1.8/write_protocols/line_protocol_reference/#data-types). -The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/data_exploration/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals). +The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/explore-data/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals). See the [Advanced Syntax](#advanced-syntax) section for how to use `LN()` with a `GROUP BY time()` clause. ##### Examples @@ -4489,8 +4489,8 @@ time ln ``` The query returns the natural logarithms of field values associated with the `water_level` field key. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/data_exploration/#order-by-time-desc). -The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/data_exploration/#the-offset-and-soffset-clauses) results by two points. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/explore-data/#order-by-time-desc). +The query also [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/explore-data/#the-offset-and-soffset-clauses) results by two points. #### Advanced syntax @@ -4498,7 +4498,7 @@ The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limi SELECT LN(( [ * | ] )) [INTO_clause] FROM_clause [WHERE_clause] GROUP_BY_clause [ORDER_BY_clause] [LIMIT_clause] [OFFSET_clause] [SLIMIT_clause] [SOFFSET_clause] ``` -The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) and a nested InfluxQL function. +The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) and a nested InfluxQL function. The query first calculates the results for the nested function at the specified `GROUP BY time()` interval and then applies the `LN()` function to those results. `LN()` supports the following nested functions: @@ -4560,14 +4560,14 @@ SELECT LOG( [ * | ], ) [INTO_clause] FROM_clause [WHERE_clause] Returns the logarithm of field values associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key) with base `b`. +Returns the logarithm of field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions) with base `b`. --> `LOG(*, b)` Returns the logarithm of field values associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement) with base `b`. `LOG()` supports int64 and float64 field value [data types](/influxdb/v1.8/write_protocols/line_protocol_reference/#data-types). -The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/data_exploration/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals). +The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/explore-data/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals). See the [Advanced Syntax](#advanced-syntax) section for how to use `LOG()` with a `GROUP BY time()` clause. ##### Examples @@ -4658,8 +4658,8 @@ time log ``` The query returns the logarithm base 4 of field values associated with the `water_level` field key. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/data_exploration/#order-by-time-desc). -The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/data_exploration/#the-offset-and-soffset-clauses) results by two points. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/explore-data/#order-by-time-desc). +The query also [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/explore-data/#the-offset-and-soffset-clauses) results by two points. #### Advanced syntax @@ -4667,7 +4667,7 @@ The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limi SELECT LOG(( [ * | ] ), ) [INTO_clause] FROM_clause [WHERE_clause] GROUP_BY_clause [ORDER_BY_clause] [LIMIT_clause] [OFFSET_clause] [SLIMIT_clause] [SOFFSET_clause] ``` -The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) and a nested InfluxQL function. +The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) and a nested InfluxQL function. The query first calculates the results for the nested function at the specified `GROUP BY time()` interval and then applies the `LOG()` function to those results. `LOG()` supports the following nested functions: @@ -4729,14 +4729,14 @@ SELECT LOG2( [ * | ] ) [INTO_clause] FROM_clause [WHERE_clause] [GRO Returns the logarithm of field values associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key) to the base 2. +Returns the logarithm of field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions) to the base 2. --> `LOG2(*)` Returns the logarithm of field values associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement) to the base 2. `LOG2()` supports int64 and float64 field value [data types](/influxdb/v1.8/write_protocols/line_protocol_reference/#data-types). -The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/data_exploration/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals). +The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/explore-data/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals). See the [Advanced syntax](#advanced-syntax) section for how to use `LOG2()` with a `GROUP BY time()` clause. ##### Examples @@ -4827,8 +4827,8 @@ time log2 ``` The query returns the logarithm base 2 of field values associated with the `water_level` field key. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/data_exploration/#order-by-time-desc). -The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/data_exploration/#the-offset-and-soffset-clauses) results by two points. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/explore-data/#order-by-time-desc). +The query also [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/explore-data/#the-offset-and-soffset-clauses) results by two points. #### Advanced syntax @@ -4836,7 +4836,7 @@ The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limi SELECT LOG2(( [ * | ] )) [INTO_clause] FROM_clause [WHERE_clause] GROUP_BY_clause [ORDER_BY_clause] [LIMIT_clause] [OFFSET_clause] [SLIMIT_clause] [SOFFSET_clause] ``` -The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) and a nested InfluxQL function. +The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) and a nested InfluxQL function. The query first calculates the results for the nested function at the specified `GROUP BY time()` interval and then applies the `LOG2()` function to those results. `LOG2()` supports the following nested functions: @@ -4898,14 +4898,14 @@ SELECT LOG10( [ * | ] ) [INTO_clause] FROM_clause [WHERE_clause] [GR Returns the logarithm of field values associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key) to the base 10. +Returns the logarithm of field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions) to the base 10. --> `LOG10(*)` Returns the logarithm of field values associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement) to the base 10. `LOG10()` supports int64 and float64 field value [data types](/influxdb/v1.8/write_protocols/line_protocol_reference/#data-types). -The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/data_exploration/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals). +The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/explore-data/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals). See the [Advanced Syntax](#advanced-syntax) section for how to use `LOG10()` with a `GROUP BY time()` clause. ##### Examples @@ -4996,8 +4996,8 @@ time log10 ``` The query returns the logarithm base 10 of field values associated with the `water_level` field key. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/data_exploration/#order-by-time-desc). -The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/data_exploration/#the-offset-and-soffset-clauses) results by two points. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/explore-data/#order-by-time-desc). +The query also [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/explore-data/#the-offset-and-soffset-clauses) results by two points. #### Advanced syntax @@ -5005,7 +5005,7 @@ The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limi SELECT LOG10(( [ * | ] )) [INTO_clause] FROM_clause [WHERE_clause] GROUP_BY_clause [ORDER_BY_clause] [LIMIT_clause] [OFFSET_clause] [SLIMIT_clause] [SOFFSET_clause] ``` -The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) and a nested InfluxQL function. +The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) and a nested InfluxQL function. The query first calculates the results for the nested function at the specified `GROUP BY time()` interval and then applies the `LOG10()` function to those results. `LOG10()` supports the following nested functions: @@ -5070,14 +5070,14 @@ The `N` argument is an integer and it is required. Returns the rolling average across `N` field values associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key). `MOVING_AVERAGE(/regular_expression/,N)` -Returns the rolling average across `N` field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/data_exploration/#regular-expressions). +Returns the rolling average across `N` field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions). `MOVING_AVERAGE(*,N)` Returns the rolling average across `N` field values associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement). `MOVING_AVERAGE()` int64 and float64 field value [data types](/influxdb/v1.8/write_protocols/line_protocol_reference/#data-types). -The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/data_exploration/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals). +The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/explore-data/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals). See the [Advanced Syntax](#advanced-syntax-3) section for how to use `MOVING_AVERAGE()` with a `GROUP BY time()` clause. ##### Examples @@ -5162,8 +5162,8 @@ time moving_average ``` The query returns the rolling average across a two-field-value window for the `water_level` field key in the `h2o_feet` measurement. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/data_exploration/#order-by-time-desc). -The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points returned to two and [offsets](/influxdb/v1.8/query_language/data_exploration/#the-offset-and-soffset-clauses) results by three points. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/explore-data/#order-by-time-desc). +The query also [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points returned to two and [offsets](/influxdb/v1.8/query_language/explore-data/#the-offset-and-soffset-clauses) results by three points. #### Advanced syntax @@ -5171,7 +5171,7 @@ The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limi SELECT MOVING_AVERAGE( ([ * | | // ]) , N ) [INTO_clause] FROM_clause [WHERE_clause] GROUP_BY_clause [ORDER_BY_clause] [LIMIT_clause] [OFFSET_clause] [SLIMIT_clause] [SOFFSET_clause] ``` -The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) and a nested InfluxQL function. +The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) and a nested InfluxQL function. The query first calculates the results for the nested function at the specified `GROUP BY time()` interval and then applies the `MOVING_AVERAGE()` function to those results. `MOVING_AVERAGE()` supports the following nested functions: @@ -5239,14 +5239,14 @@ If the query does not specify the `unit`, the unit defaults to one second (`1s`) Returns the non-negative rate of change between subsequent field values associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key). `NON_NEGATIVE_DERIVATIVE(/regular_expression/)` -Returns the non-negative rate of change between subsequent field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/data_exploration/#regular-expressions). +Returns the non-negative rate of change between subsequent field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions). `NON_NEGATIVE_DERIVATIVE(*)` Returns the non-negative rate of change between subsequent field values associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement). `NON_NEGATIVE_DERIVATIVE()` supports int64 and float64 field value [data types](/influxdb/v1.8/write_protocols/line_protocol_reference/#data-types). -The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/data_exploration/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals). +The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/explore-data/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals). See the [Advanced Syntax](#advanced-syntax-4) section for how to use `NON_NEGATIVE_DERIVATIVE()` with a `GROUP BY time()` clause. ##### Examples @@ -5260,7 +5260,7 @@ See the examples in the [`DERIVATIVE()` documentation](#basic-syntax-8). SELECT NON_NEGATIVE_DERIVATIVE( ([ * | | // ]) [ , ] ) [INTO_clause] FROM_clause [WHERE_clause] GROUP_BY_clause [ORDER_BY_clause] [LIMIT_clause] [OFFSET_clause] [SLIMIT_clause] [SOFFSET_clause] ``` -The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) and a nested InfluxQL function. +The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) and a nested InfluxQL function. The query first calculates the results for the nested function at the specified `GROUP BY time()` interval and then applies the `NON_NEGATIVE_DERIVATIVE()` function to those results. The `unit` argument is an integer followed by a [duration literal](/influxdb/v1.8/query_language/spec/#literals) and it is optional. @@ -5300,14 +5300,14 @@ SELECT NON_NEGATIVE_DIFFERENCE( [ * | | // ] ) [ Returns the non-negative difference between subsequent field values associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key). `NON_NEGATIVE_DIFFERENCE(/regular_expression/)` -Returns the non-negative difference between subsequent field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/data_exploration/#regular-expressions). +Returns the non-negative difference between subsequent field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions). `NON_NEGATIVE_DIFFERENCE(*)` Returns the non-negative difference between subsequent field values associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement). `NON_NEGATIVE_DIFFERENCE()` supports int64 and float64 field value [data types](/influxdb/v1.8/write_protocols/line_protocol_reference/#data-types). -The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/data_exploration/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals). +The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/explore-data/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals). See the [Advanced Syntax](#advanced-syntax-5) section for how to use `NON_NEGATIVE_DIFFERENCE()` with a `GROUP BY time()` clause. ##### Examples @@ -5321,7 +5321,7 @@ See the examples in the [`DIFFERENCE()` documentation](#basic-syntax-9). SELECT NON_NEGATIVE_DIFFERENCE(( [ * | | // ] )) [INTO_clause] FROM_clause [WHERE_clause] GROUP_BY_clause [ORDER_BY_clause] [LIMIT_clause] [OFFSET_clause] [SLIMIT_clause] [SOFFSET_clause] ``` -The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) and a nested InfluxQL function. +The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) and a nested InfluxQL function. The query first calculates the results for the nested function at the specified `GROUP BY time()` interval and then applies the `NON_NEGATIVE_DIFFERENCE()` function to those results. `NON_NEGATIVE_DIFFERENCE()` supports the following nested functions: @@ -5355,14 +5355,14 @@ SELECT POW( [ * | ], ) [INTO_clause] FROM_clause [WHERE_clause] Returns the field values associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key) to the power of `x`. +Returns the field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions) to the power of `x`. --> `POW(*, x)` Returns the field values associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement) to the power of `x`. `POW()` supports int64 and float64 field value [data types](/influxdb/v1.8/write_protocols/line_protocol_reference/#data-types). -The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/data_exploration/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals). +The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/explore-data/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals). See the [Advanced Syntax](#advanced-syntax) section for how to use `POW()` with a `GROUP BY time()` clause. ##### Examples @@ -5453,8 +5453,8 @@ time pow ``` The query returns field values associated with the `water_level` field key multiplied to the power of 4. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/data_exploration/#order-by-time-desc). -The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/data_exploration/#the-offset-and-soffset-clauses) results by two points. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/explore-data/#order-by-time-desc). +The query also [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/explore-data/#the-offset-and-soffset-clauses) results by two points. #### Advanced syntax @@ -5462,7 +5462,7 @@ The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limi SELECT POW(( [ * | ] ), ) [INTO_clause] FROM_clause [WHERE_clause] GROUP_BY_clause [ORDER_BY_clause] [LIMIT_clause] [OFFSET_clause] [SLIMIT_clause] [SOFFSET_clause] ``` -The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) and a nested InfluxQL function. +The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) and a nested InfluxQL function. The query first calculates the results for the nested function at the specified `GROUP BY time()` interval and then applies the `POW()` function to those results. `POW()` supports the following nested functions: @@ -5524,14 +5524,14 @@ SELECT ROUND( [ * | ] ) [INTO_clause] FROM_clause [WHERE_clause] [GR Returns the field values associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key) rounded to the nearest integer. +Returns the field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions) rounded to the nearest integer. --> `ROUND(*)` Returns the field values associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement) rounded to the nearest integer. `ROUND()` supports int64 and float64 field value [data types](/influxdb/v1.8/write_protocols/line_protocol_reference/#data-types). -The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/data_exploration/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals). +The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/explore-data/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals). See the [Advanced Syntax](#advanced-syntax) section for how to use `ROUND()` with a `GROUP BY time()` clause. ##### Examples @@ -5621,8 +5621,8 @@ time round ``` The query returns field values associated with the `water_level` field key rounded to the nearest integer. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/data_exploration/#order-by-time-desc). -The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/data_exploration/#the-offset-and-soffset-clauses) results by two points. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/explore-data/#order-by-time-desc). +The query also [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/explore-data/#the-offset-and-soffset-clauses) results by two points. #### Advanced syntax @@ -5630,7 +5630,7 @@ The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limi SELECT ROUND(( [ * | ] )) [INTO_clause] FROM_clause [WHERE_clause] GROUP_BY_clause [ORDER_BY_clause] [LIMIT_clause] [OFFSET_clause] [SLIMIT_clause] [SOFFSET_clause] ``` -The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) and a nested InfluxQL function. +The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) and a nested InfluxQL function. The query first calculates the results for the nested function at the specified `GROUP BY time()` interval and then applies the `ROUND()` function to those results. `ROUND()` supports the following nested functions: @@ -5692,14 +5692,14 @@ SELECT SIN( [ * | ] ) [INTO_clause] FROM_clause [WHERE_clause] [GROU Returns the sine of field values associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key). +Returns the sine of field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions). --> `SIN(*)` Returns the sine of field values associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement). `SIN()` supports int64 and float64 field value [data types](/influxdb/v1.8/write_protocols/line_protocol_reference/#data-types). -The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/data_exploration/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals). +The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/explore-data/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals). See the [Advanced Syntax](#advanced-syntax) section for how to use `SIN()` with a `GROUP BY time()` clause. ##### Examples @@ -5789,8 +5789,8 @@ time sin ``` The query returns sine of field values associated with the `water_level` field key. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/data_exploration/#order-by-time-desc). -The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/data_exploration/#the-offset-and-soffset-clauses) results by two points. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/explore-data/#order-by-time-desc). +The query also [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/explore-data/#the-offset-and-soffset-clauses) results by two points. #### Advanced syntax @@ -5798,7 +5798,7 @@ The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limi SELECT SIN(( [ * | ] )) [INTO_clause] FROM_clause [WHERE_clause] GROUP_BY_clause [ORDER_BY_clause] [LIMIT_clause] [OFFSET_clause] [SLIMIT_clause] [SOFFSET_clause] ``` -The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) and a nested InfluxQL function. +The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) and a nested InfluxQL function. The query first calculates the results for the nested function at the specified `GROUP BY time()` interval and then applies the `SIN()` function to those results. `SIN()` supports the following nested functions: @@ -5860,14 +5860,14 @@ SELECT SQRT( [ * | ] ) [INTO_clause] FROM_clause [WHERE_clause] [GRO Returns the square root of field values associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key). +Returns the square root field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions). --> `SQRT(*)` Returns the square root field values associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement). `SQRT()` supports int64 and float64 field value [data types](/influxdb/v1.8/write_protocols/line_protocol_reference/#data-types). -The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/data_exploration/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals). +The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/explore-data/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals). See the [Advanced Syntax](#advanced-syntax) section for how to use `SQRT()` with a `GROUP BY time()` clause. ##### Examples @@ -5958,8 +5958,8 @@ time sqrt ``` The query returns the square roots of field values associated with the `water_level` field key. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/data_exploration/#order-by-time-desc). -The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/data_exploration/#the-offset-and-soffset-clauses) results by two points. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/explore-data/#order-by-time-desc). +The query also [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/explore-data/#the-offset-and-soffset-clauses) results by two points. #### Advanced syntax @@ -5967,7 +5967,7 @@ The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limi SELECT SQRT(( [ * | ] )) [INTO_clause] FROM_clause [WHERE_clause] GROUP_BY_clause [ORDER_BY_clause] [LIMIT_clause] [OFFSET_clause] [SLIMIT_clause] [SOFFSET_clause] ``` -The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) and a nested InfluxQL function. +The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) and a nested InfluxQL function. The query first calculates the results for the nested function at the specified `GROUP BY time()` interval and then applies the `SQRT()` function to those results. `SQRT()` supports the following nested functions: @@ -6029,14 +6029,14 @@ SELECT TAN( [ * | ] ) [INTO_clause] FROM_clause [WHERE_clause] [GROU Returns the tangent of field values associated with the [field key](/influxdb/v1.8/concepts/glossary/#field-key). +Returns the tangent of field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions). --> `TAN(*)` Returns the tangent of field values associated with each field key in the [measurement](/influxdb/v1.8/concepts/glossary/#measurement). `TAN()` supports int64 and float64 field value [data types](/influxdb/v1.8/write_protocols/line_protocol_reference/#data-types). -The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/data_exploration/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals). +The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/explore-data/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals). See the [Advanced Syntax](#advanced-syntax) section for how to use `TAN()` with a `GROUP BY time()` clause. ##### Examples @@ -6126,8 +6126,8 @@ time tan ``` The query returns tangent of field values associated with the `water_level` field key. -It covers the [time range](/influxdb/v1.8/query_language/data_exploration/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/data_exploration/#order-by-time-desc). -The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/data_exploration/#the-offset-and-soffset-clauses) results by two points. +It covers the [time range](/influxdb/v1.8/query_language/explore-data/#time-syntax) between `2015-08-18T00:00:00Z` and `2015-08-18T00:30:00Z` and returns results in [descending timestamp order](/influxdb/v1.8/query_language/explore-data/#order-by-time-desc). +The query also [limits](/influxdb/v1.8/query_language/explore-data/#the-limit-and-slimit-clauses) the number of points returned to four and [offsets](/influxdb/v1.8/query_language/explore-data/#the-offset-and-soffset-clauses) results by two points. #### Advanced syntax @@ -6135,7 +6135,7 @@ The query also [limits](/influxdb/v1.8/query_language/data_exploration/#the-limi SELECT TAN(( [ * | ] )) [INTO_clause] FROM_clause [WHERE_clause] GROUP_BY_clause [ORDER_BY_clause] [LIMIT_clause] [OFFSET_clause] [SLIMIT_clause] [SOFFSET_clause] ``` -The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) and a nested InfluxQL function. +The advanced syntax requires a [`GROUP BY time() ` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) and a nested InfluxQL function. The query first calculates the results for the nested function at the specified `GROUP BY time()` interval and then applies the `TAN()` function to those results. `TAN()` supports the following nested functions: @@ -6204,7 +6204,7 @@ SELECT HOLT_WINTERS[_WITH-FIT]((),,) [INTO_clause] FR `HOLT_WINTERS(function(field_key),N,S)` returns `N` seasonally adjusted predicted field values for the specified [field key](/influxdb/v1.8/concepts/glossary/#field-key). -The `N` predicted values occur at the same interval as the [`GROUP BY time()` interval](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals). +The `N` predicted values occur at the same interval as the [`GROUP BY time()` interval](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals). If your `GROUP BY time()` interval is `6m` and `N` is `3` you'll receive three predicted values that are each six minutes apart. @@ -6251,7 +6251,7 @@ SELECT FIRST("water_level") FROM "NOAA_water_database"."autogen"."h2o_feet" WHER In the `GROUP BY time()` clause, the first argument (`379m`) matches the length of time that occurs between each peak and trough in the `water_level` data. The second argument (`348m`) is the -[offset interval](/influxdb/v1.8/query_language/data_exploration/#advanced-group-by-time-syntax). +[offset interval](/influxdb/v1.8/query_language/explore-data/#advanced-group-by-time-syntax). The offset interval alters the default `GROUP BY time()` boundaries to match the time range of the raw data. @@ -6427,7 +6427,7 @@ and the default hold period and warmup type. > [aggregate function](#aggregations) in your call to the `CHANDE_MOMENTUM_OSCILLATOR()` function. `CHANDE_MOMENTUM_OSCILLATOR(/regular_expression/, 2)` -Returns the field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/data_exploration/#regular-expressions) +Returns the field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions) processed using the Chande Momentum Oscillator algorithm with a 2-value period and the default hold period and warmup type. @@ -6438,7 +6438,7 @@ and the default hold period and warmup type. `CHANDE_MOMENTUM_OSCILLATOR()` supports int64 and float64 field value [data types](/influxdb/v1.8/write_protocols/line_protocol_reference/#data-types). -The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/data_exploration/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals). +The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/explore-data/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals). See the [Advanced Syntax](#advanced-syntax) section for how to use `CHANDE_MOMENTUM_OSCILLATOR()` with a `GROUP BY time()` clause. ### EXPONENTIAL_MOVING_AVERAGE() @@ -6481,7 +6481,7 @@ and the default hold period and warmup type. > [aggregate function](#aggregations) in your call to the `EXPONENTIAL_MOVING_AVERAGE()` function. `EXPONENTIAL_MOVING_AVERAGE(/regular_expression/, 2)` -Returns the field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/data_exploration/#regular-expressions) +Returns the field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions) processed using the Exponential Moving Average algorithm with a 2-value period and the default hold period and warmup type. @@ -6492,7 +6492,7 @@ and the default hold period and warmup type. `EXPONENTIAL_MOVING_AVERAGE()` supports int64 and float64 field value [data types](/influxdb/v1.8/write_protocols/line_protocol_reference/#data-types). -The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/data_exploration/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals). +The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/explore-data/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals). See the [Advanced Syntax](#advanced-syntax) section for how to use `EXPONENTIAL_MOVING_AVERAGE()` with a `GROUP BY time()` clause. ### DOUBLE_EXPONENTIAL_MOVING_AVERAGE() @@ -6537,7 +6537,7 @@ and the default hold period and warmup type. > [aggregate function](#aggregations) in your call to the `DOUBLE_EXPONENTIAL_MOVING_AVERAGE()` function. `DOUBLE_EXPONENTIAL_MOVING_AVERAGE(/regular_expression/, 2)` -Returns the field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/data_exploration/#regular-expressions) +Returns the field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions) processed using the Double Exponential Moving Average algorithm with a 2-value period and the default hold period and warmup type. @@ -6548,7 +6548,7 @@ and the default hold period and warmup type. `DOUBLE_EXPONENTIAL_MOVING_AVERAGE()` supports int64 and float64 field value [data types](/influxdb/v1.8/write_protocols/line_protocol_reference/#data-types). -The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/data_exploration/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals). +The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/explore-data/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals). See the [Advanced Syntax](#advanced-syntax) section for how to use `DOUBLE_EXPONENTIAL_MOVING_AVERAGE()` with a `GROUP BY time()` clause. ### KAUFMANS_EFFICIENCY_RATIO() @@ -6594,7 +6594,7 @@ and the default hold period. > [aggregate function](#aggregations) in your call to the `KAUFMANS_EFFICIENCY_RATIO()` function. `KAUFMANS_EFFICIENCY_RATIO(/regular_expression/, 2)` -Returns the field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/data_exploration/#regular-expressions) +Returns the field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions) processed using the Efficiency Index algorithm with a 2-value period and the default hold period and warmup type. @@ -6605,7 +6605,7 @@ and the default hold period and warmup type. `KAUFMANS_EFFICIENCY_RATIO()` supports int64 and float64 field value [data types](/influxdb/v1.8/write_protocols/line_protocol_reference/#data-types). -The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/data_exploration/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals). +The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/explore-data/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals). See the [Advanced Syntax](#advanced-syntax) section for how to use `KAUFMANS_EFFICIENCY_RATIO()` with a `GROUP BY time()` clause. ### KAUFMANS_ADAPTIVE_MOVING_AVERAGE() @@ -6648,7 +6648,7 @@ and the default hold period. > [aggregate function](#aggregations) in your call to the `KAUFMANS_ADAPTIVE_MOVING_AVERAGE()` function. `KAUFMANS_ADAPTIVE_MOVING_AVERAGE(/regular_expression/, 2)` -Returns the field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/data_exploration/#regular-expressions) +Returns the field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions) processed using the Kaufman Adaptive Moving Average algorithm with a 2-value period and the default hold period and warmup type. @@ -6659,7 +6659,7 @@ and the default hold period and warmup type. `KAUFMANS_ADAPTIVE_MOVING_AVERAGE()` supports int64 and float64 field value [data types](/influxdb/v1.8/write_protocols/line_protocol_reference/#data-types). -The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/data_exploration/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals). +The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/explore-data/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals). See the [Advanced Syntax](#advanced-syntax) section for how to use `KAUFMANS_ADAPTIVE_MOVING_AVERAGE()` with a `GROUP BY time()` clause. ### TRIPLE_EXPONENTIAL_MOVING_AVERAGE() @@ -6704,7 +6704,7 @@ and the default hold period and warmup type. > [aggregate function](#aggregations) in your call to the `TRIPLE_EXPONENTIAL_MOVING_AVERAGE()` function. `TRIPLE_EXPONENTIAL_MOVING_AVERAGE(/regular_expression/, 2)` -Returns the field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/data_exploration/#regular-expressions) +Returns the field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions) processed using the Triple Exponential Moving Average algorithm with a 2-value period and the default hold period and warmup type. @@ -6715,7 +6715,7 @@ and the default hold period and warmup type. `TRIPLE_EXPONENTIAL_MOVING_AVERAGE()` supports int64 and float64 field value [data types](/influxdb/v1.8/write_protocols/line_protocol_reference/#data-types). -The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/data_exploration/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals). +The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/explore-data/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals). See the [Advanced Syntax](#advanced-syntax) section for how to use `TRIPLE_EXPONENTIAL_MOVING_AVERAGE()` with a `GROUP BY time()` clause. ### TRIPLE_EXPONENTIAL_DERIVATIVE() @@ -6768,7 +6768,7 @@ and the default hold period and warmup type. > [aggregate function](#aggregations) in your call to the `TRIPLE_EXPONENTIAL_DERIVATIVE()` function. `TRIPLE_EXPONENTIAL_DERIVATIVE(/regular_expression/, 2)` -Returns the field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/data_exploration/#regular-expressions) +Returns the field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions) processed using the Triple Exponential Derivative algorithm with a 2-value period and the default hold period and warmup type. @@ -6779,7 +6779,7 @@ and the default hold period and warmup type. `TRIPLE_EXPONENTIAL_DERIVATIVE()` supports int64 and float64 field value [data types](/influxdb/v1.8/write_protocols/line_protocol_reference/#data-types). -The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/data_exploration/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals). +The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/explore-data/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals). See the [Advanced Syntax](#advanced-syntax) section for how to use `TRIPLE_EXPONENTIAL_DERIVATIVE()` with a `GROUP BY time()` clause. ### RELATIVE_STRENGTH_INDEX() @@ -6819,7 +6819,7 @@ and the default hold period and warmup type. > [aggregate function](#aggregations) in your call to the `RELATIVE_STRENGTH_INDEX()` function. `RELATIVE_STRENGTH_INDEX(/regular_expression/, 2)` -Returns the field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/data_exploration/#regular-expressions) +Returns the field values associated with each field key that matches the [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions) processed using the Relative Strength Index algorithm with a 2-value period and the default hold period and warmup type. @@ -6830,7 +6830,7 @@ and the default hold period and warmup type. `RELATIVE_STRENGTH_INDEX()` supports int64 and float64 field value [data types](/influxdb/v1.8/write_protocols/line_protocol_reference/#data-types). -The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/data_exploration/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals). +The basic syntax supports `GROUP BY` clauses that [group by tags](/influxdb/v1.8/query_language/explore-data/#group-by-tags) but not `GROUP BY` clauses that [group by time](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals). See the [Advanced Syntax](#advanced-syntax) section for how to use `RELATIVE_STRENGTH_INDEX()` with a `GROUP BY time()` clause. ## Other @@ -6979,9 +6979,9 @@ time median mode #### Change the Values Reported for Intervals with no Data -By default, queries with an InfluxQL function and a [`GROUP BY time()` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) report null values for intervals with no data. +By default, queries with an InfluxQL function and a [`GROUP BY time()` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) report null values for intervals with no data. Include `fill()` at the end of the `GROUP BY` clause to change that value. -See [Data Exploration](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals-and-fill) for a complete discussion of `fill()`. +See [Data Exploration](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals-and-fill) for a complete discussion of `fill()`. ### Common Issues with Functions @@ -7000,7 +7000,7 @@ See the function-specific documentation for common issues with individual functi ##### Nesting functions -Some InfluxQL functions support nesting in the [`SELECT` clause](/influxdb/v1.8/query_language/data_exploration/#select-clause): +Some InfluxQL functions support nesting in the [`SELECT` clause](/influxdb/v1.8/query_language/explore-data/#select-clause): * [`COUNT()`](#count) with [`DISTINCT()`](#distinct) * [`CUMULATIVE_SUM()`](#cumulative-sum) @@ -7011,25 +7011,25 @@ Some InfluxQL functions support nesting in the [`SELECT` clause](/influxdb/v1.8/ * [`NON_NEGATIVE_DERIVATIVE()`](#non-negative-derivative) * [`HOLT_WINTERS()`](#holt-winters) and [`HOLT_WINTERS_WITH_FIT()`](#holt-winters) -For other functions, use InfluxQL's [subqueries](/influxdb/v1.8/query_language/data_exploration/#subqueries) to nest functions in the [`FROM` clause](/influxdb/v1.8/query_language/data_exploration/#from-clause). -See the [Data Exploration](/influxdb/v1.8/query_language/data_exploration/#subqueries) page more on using subqueries. +For other functions, use InfluxQL's [subqueries](/influxdb/v1.8/query_language/explore-data/#subqueries) to nest functions in the [`FROM` clause](/influxdb/v1.8/query_language/explore-data/#from-clause). +See the [Data Exploration](/influxdb/v1.8/query_language/explore-data/#subqueries) page more on using subqueries. ##### Querying time ranges after now() Most `SELECT` statements have a default time range between [`1677-09-21 00:12:43.145224194` and `2262-04-11T23:47:16.854775806Z` UTC](/influxdb/v1.8/troubleshooting/frequently-asked-questions/#what-are-the-minimum-and-maximum-timestamps-that-influxdb-can-store). -For `SELECT` statements with an InfluxQL function and a [`GROUP BY time()` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals), the default time +For `SELECT` statements with an InfluxQL function and a [`GROUP BY time()` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals), the default time range is between `1677-09-21 00:12:43.145224194` UTC and [`now()`](/influxdb/v1.8/concepts/glossary/#now). To query data with timestamps that occur after `now()`, `SELECT` statements with an InfluxQL function and a `GROUP BY time()` clause must provide an alternative upper bound in the -[`WHERE` clause](/influxdb/v1.8/query_language/data_exploration/#the-where-clause). +[`WHERE` clause](/influxdb/v1.8/query_language/explore-data/#the-where-clause). See the [Frequently Asked Questions](/influxdb/v1.8/troubleshooting/frequently-asked-questions/#why-don-t-my-group-by-time-queries-return-timestamps-that-occur-after-now) page for an example. #### Aggregation Functions ##### Understanding the returned timestamp -A query with an [aggregation function](#aggregations) and no time range in the [`WHERE` clause](/influxdb/v1.8/query_language/data_exploration/#the-where-clause) returns epoch 0 (`1970-01-01T00:00:00Z`) as the timestamp. +A query with an [aggregation function](#aggregations) and no time range in the [`WHERE` clause](/influxdb/v1.8/query_language/explore-data/#the-where-clause) returns epoch 0 (`1970-01-01T00:00:00Z`) as the timestamp. InfluxDB uses epoch 0 as the null timestamp equivalent. A query with an aggregate function that includes a time range in the `WHERE` clause returns the lower time bound as the timestamp. @@ -7074,11 +7074,11 @@ time sum 2015-08-18T00:12:00Z 19.802999999999997 ``` -The query returns the lower time bound for each [`GROUP BY time()`](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) interval as the timestamps. +The query returns the lower time bound for each [`GROUP BY time()`](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) interval as the timestamps. ###### Mixing aggregation functions with non-aggregates -Aggregation functions do not support specifying standalone [field keys](/influxdb/v1.8/concepts/glossary/#field-key) or [tag keys](/influxdb/v1.8/concepts/glossary/#tag-key) in the [`SELECT` clause](/influxdb/v1.8/query_language/data_exploration/#select-clause). +Aggregation functions do not support specifying standalone [field keys](/influxdb/v1.8/concepts/glossary/#field-key) or [tag keys](/influxdb/v1.8/concepts/glossary/#tag-key) in the [`SELECT` clause](/influxdb/v1.8/query_language/explore-data/#select-clause). Aggregation functions return a single calculated value and there is no obvious single value to return for any unaggregated fields or tags. Including a standalone field key or tag key with an aggregation function in the `SELECT` clause returns an error: @@ -7099,10 +7099,10 @@ InfluxDB does not sort points before it applies the aggregation function; that b The timestamps returned by [selector functions](#selectors) depend on the number of functions in the query and on the other clauses in the query: -A query with a single selector function, a single [field key](/influxdb/v1.8/concepts/glossary/#field-key) argument, and no [`GROUP BY time()` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) returns the timestamp for the point that appears in the raw data. -A query with a single selector function, multiple field key arguments, and no [`GROUP BY time()` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals) returns the timestamp for the point that appears in the raw data or the InfluxDB equivalent of a null timestamp (epoch 0: `1970-01-01T00:00:00Z`). +A query with a single selector function, a single [field key](/influxdb/v1.8/concepts/glossary/#field-key) argument, and no [`GROUP BY time()` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) returns the timestamp for the point that appears in the raw data. +A query with a single selector function, multiple field key arguments, and no [`GROUP BY time()` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals) returns the timestamp for the point that appears in the raw data or the InfluxDB equivalent of a null timestamp (epoch 0: `1970-01-01T00:00:00Z`). -A query with more than one function and no time range in the [`WHERE` clause](/influxdb/v1.8/query_language/data_exploration/#the-where-clause) returns the InfluxDB equivalent of a null timestamp (epoch 0: `1970-01-01T00:00:00Z`). +A query with more than one function and no time range in the [`WHERE` clause](/influxdb/v1.8/query_language/explore-data/#the-where-clause) returns the InfluxDB equivalent of a null timestamp (epoch 0: `1970-01-01T00:00:00Z`). A query with more than one function and a time range in the `WHERE` clause returns the lower time bound as the timestamp. A query with a selector function and a `GROUP BY time()` clause returns the lower time bound for each `GROUP BY time()` interval. diff --git a/content/influxdb/v1.8/query_language/manage-database.md b/content/influxdb/v1.8/query_language/manage-database.md index 2bbc30da8..c38374118 100644 --- a/content/influxdb/v1.8/query_language/manage-database.md +++ b/content/influxdb/v1.8/query_language/manage-database.md @@ -8,7 +8,7 @@ menu: weight: 40 parent: InfluxQL aliases: - - /influxdb/v1.8/query_language/database_management/ + - /influxdb/v1.8/query_language/manage-database/ --- InfluxQL offers a full suite of administrative commands. @@ -44,7 +44,7 @@ InfluxQL offers a full suite of administrative commands. -If you're looking for `SHOW` queries (for example, `SHOW DATABASES` or `SHOW RETENTION POLICIES`), see [Schema Exploration](/influxdb/v1.8/query_language/schema_exploration). +If you're looking for `SHOW` queries (for example, `SHOW DATABASES` or `SHOW RETENTION POLICIES`), see [Schema Exploration](/influxdb/v1.8/query_language/explore-schema). The examples in the sections below use the InfluxDB [Command Line Interface (CLI)](/influxdb/v1.8/introduction/getting-started/). You can also execute the commands using the InfluxDB API; simply send a `GET` request to the `/query` endpoint and include the command in the URL parameter `q`. @@ -72,7 +72,7 @@ CREATE DATABASE [WITH [DURATION ] [REPLICATION ] [S The `WITH`, `DURATION`, `REPLICATION`, `SHARD DURATION`, and `NAME` clauses are optional and create a single [retention policy](/influxdb/v1.8/concepts/glossary/#retention-policy-rp) associated with the created database. If you do not specify one of the clauses after `WITH`, the relevant behavior defaults to the `autogen` retention policy settings. The created retention policy automatically serves as the database's default retention policy. -For more information about those clauses, see [Retention Policy Management](/influxdb/v1.8/query_language/database_management/#retention-policy-management). +For more information about those clauses, see [Retention Policy Management](/influxdb/v1.8/query_language/manage-database/#retention-policy-management). A successful `CREATE DATABASE` query returns an empty result. If you attempt to create a database that already exists, InfluxDB does nothing and does not return an error. @@ -123,7 +123,7 @@ and it drops the series from the index. > **Note:** `DROP SERIES` does not support time intervals in the `WHERE` clause. See -[`DELETE`](/influxdb/v1.8/query_language/database_management/#delete-series-with-delete) +[`DELETE`](/influxdb/v1.8/query_language/manage-database/#delete-series-with-delete) for that functionality. The query takes the following form, where you must specify either the `FROM` clause or the `WHERE` clause: @@ -153,7 +153,7 @@ A successful `DROP SERIES` query returns an empty result. The `DELETE` query deletes all points from a [series](/influxdb/v1.8/concepts/glossary/#series) in a database. Unlike -[`DROP SERIES`](/influxdb/v1.8/query_language/database_management/#drop-series-from-the-index-with-drop-series), it does not drop the series from the index and it supports time intervals +[`DROP SERIES`](/influxdb/v1.8/query_language/manage-database/#drop-series-from-the-index-with-drop-series), it does not drop the series from the index and it supports time intervals in the `WHERE` clause. The query takes the following form where you must include either the `FROM` @@ -183,7 +183,7 @@ A successful `DELETE` query returns an empty result. Things to note about `DELETE`: * `DELETE` supports -[regular expressions](/influxdb/v1.8/query_language/data_exploration/#regular-expressions) +[regular expressions](/influxdb/v1.8/query_language/explore-data/#regular-expressions) in the `FROM` clause when specifying measurement names and in the `WHERE` clause when specifying tag values. * `DELETE` does not support [fields](/influxdb/v1.8/concepts/glossary/#field) in the `WHERE` clause. @@ -321,7 +321,7 @@ If you attempt to create a retention policy identical to one that already exists If you attempt to create a retention policy with the same name as an existing retention policy but with differing attributes, InfluxDB returns an error. > **Note:** You can also specify a new retention policy in the `CREATE DATABASE` query. -See [Create a database with CREATE DATABASE](/influxdb/v1.8/query_language/database_management/#create-database). +See [Create a database with CREATE DATABASE](/influxdb/v1.8/query_language/manage-database/#create-database). ### Modify retention policies with ALTER RETENTION POLICY diff --git a/content/influxdb/v1.8/query_language/math_operators.md b/content/influxdb/v1.8/query_language/math_operators.md index dda3d1619..f6f8c9466 100644 --- a/content/influxdb/v1.8/query_language/math_operators.md +++ b/content/influxdb/v1.8/query_language/math_operators.md @@ -211,7 +211,7 @@ SELECT * FROM "data" WHERE "bitfield" ^ 6 > 0 ### Common Issues with Mathematical Operators #### Issue 1: Mathematical operators with wildcards and regular expressions -InfluxDB does not support combining mathematical operations with a wildcard (`*`) or [regular expression](/influxdb/v1.8/query_language/data_exploration/#regular-expressions) in the `SELECT` clause. +InfluxDB does not support combining mathematical operations with a wildcard (`*`) or [regular expression](/influxdb/v1.8/query_language/explore-data/#regular-expressions) in the `SELECT` clause. The following queries are invalid and the system returns an error: Perform a mathematical operation on a wildcard. @@ -254,8 +254,8 @@ SELECT mean(10 * "value") FROM "cpu" ``` will yield a parse error. -> InfluxQL supports [subqueries](/influxdb/v1.8/query_language/data_exploration/#subqueries) which offer similar functionality to using mathematical operators inside a function call. -See [Data Exploration](/influxdb/v1.8/query_language/data_exploration/#subqueries) for more information. +> InfluxQL supports [subqueries](/influxdb/v1.8/query_language/explore-data/#subqueries) which offer similar functionality to using mathematical operators inside a function call. +See [Data Exploration](/influxdb/v1.8/query_language/explore-data/#subqueries) for more information. ## Unsupported Operators diff --git a/content/influxdb/v1.8/query_language/sample-data.md b/content/influxdb/v1.8/query_language/sample-data.md index 863dfa7ac..6f0484a87 100644 --- a/content/influxdb/v1.8/query_language/sample-data.md +++ b/content/influxdb/v1.8/query_language/sample-data.md @@ -34,7 +34,7 @@ InfluxDB shell 1.4.x * The InfluxDB API runs on port `8086` by default. Therefore, `influx` will connect to port `8086` and `localhost` by default. If you need to alter these defaults, run `influx --help`. -* The [`-precision` argument](/influxdb/v1.8/tools/shell/#influx-options) specifies the format/precision of any returned timestamps. +* The [`-precision` argument](/influxdb/v1.8/tools/shell/#influx-arguments) specifies the format/precision of any returned timestamps. In the example above, `rfc3339` tells InfluxDB to return timestamps in [RFC3339 format](https://www.ietf.org/rfc/rfc3339.txt) (`YYYY-MM-DDTHH:MM:SS.nnnnnnnnnZ`). The command line is now ready to take input in the form of the Influx Query Language (a.k.a InfluxQL) statements. diff --git a/content/influxdb/v1.8/query_language/spec.md b/content/influxdb/v1.8/query_language/spec.md index c8e81dac5..bbd97699e 100644 --- a/content/influxdb/v1.8/query_language/spec.md +++ b/content/influxdb/v1.8/query_language/spec.md @@ -26,9 +26,9 @@ Find Influx Query Language (InfluxQL) definitions and details, including: To learn more about InfluxQL, browse the following topics: -* [Explore your data with InfluxQL](/influxdb/v1.8/query_language/data_exploration/) -* [Explore your schema with InfluxQL](/influxdb/v1.8/query_language/schema_exploration/) -* [Database management](/influxdb/v1.8/query_language/database_management/) +* [Explore your data with InfluxQL](/influxdb/v1.8/query_language/explore-data/) +* [Explore your schema with InfluxQL](/influxdb/v1.8/query_language/explore-schema/) +* [Database management](/influxdb/v1.8/query_language/manage-database/) * [Authentication and authorization](/influxdb/v1.8/administration/authentication_and_authorization/). InfluxQL is a SQL-like query language for interacting with InfluxDB and providing features specific to storing and analyzing time series data. @@ -229,10 +229,10 @@ regex_lit = "/" { unicode_char } "/" . > **Note:** InfluxQL supports using regular expressions when specifying: > -* [field keys](/influxdb/v1.8/concepts/glossary/#field-key) and [tag keys](/influxdb/v1.8/concepts/glossary/#tag-key) in the [`SELECT` clause](/influxdb/v1.8/query_language/data_exploration/#the-basic-select-statement) -* [measurements](/influxdb/v1.8/concepts/glossary/#measurement) in the [`FROM` clause](/influxdb/v1.8/query_language/data_exploration/#the-basic-select-statement) -* [tag values](/influxdb/v1.8/concepts/glossary/#tag-value) and string [field values](/influxdb/v1.8/concepts/glossary/#field-value) in the [`WHERE` clause](/influxdb/v1.8/query_language/data_exploration/#the-where-clause). -* [tag keys](/influxdb/v1.8/concepts/glossary/#tag-key) in the [`GROUP BY` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-tags) +* [field keys](/influxdb/v1.8/concepts/glossary/#field-key) and [tag keys](/influxdb/v1.8/concepts/glossary/#tag-key) in the [`SELECT` clause](/influxdb/v1.8/query_language/explore-data/#the-basic-select-statement) +* [measurements](/influxdb/v1.8/concepts/glossary/#measurement) in the [`FROM` clause](/influxdb/v1.8/query_language/explore-data/#the-basic-select-statement) +* [tag values](/influxdb/v1.8/concepts/glossary/#tag-value) and string [field values](/influxdb/v1.8/concepts/glossary/#field-value) in the [`WHERE` clause](/influxdb/v1.8/query_language/explore-data/#the-where-clause). +* [tag keys](/influxdb/v1.8/concepts/glossary/#tag-key) in the [`GROUP BY` clause](/influxdb/v1.8/query_language/explore-data/#group-by-tags) > >Currently, InfluxQL does not support using regular expressions to match >non-string field values in the @@ -613,7 +613,7 @@ SIZE OF BLOCKS: 931 ### EXPLAIN ANALYZE -Executes the specified SELECT statement and returns data on the query performance and storage during runtime, visualized as a tree. Use this statement to analyze query performance and storage, including [execution time](#execution_time) and [planning time](#planning_time), and the [iterator type](#iterator-type) and [cursor type](#cursor-type). +Executes the specified SELECT statement and returns data on the query performance and storage during runtime, visualized as a tree. Use this statement to analyze query performance and storage, including [execution time](#execution-time) and [planning time](#planning-time), and the [iterator type](#iterator-type) and [cursor type](#cursor-type). For example, executing the following statement: @@ -984,7 +984,7 @@ Estimates or counts exactly the cardinality of the series for the current databa [Series cardinality](/influxdb/v1.8/concepts/glossary/#series-cardinality) is the major factor that affects RAM requirements. For more information, see: - [When do I need more RAM?](/influxdb/v1.8/guides/hardware_sizing/#when-do-i-need-more-ram) in [Hardware Sizing Guidelines](/influxdb/v1.8/guides/hardware_sizing/) -- [Don't have too many series](/influxdb/v1.8/concepts/schema_and_data_layout/#don-t-have-too-many-series) +- [Don't have too many series](/influxdb/v1.8/concepts/schema_and_data_layout/#avoid-too-many-series) > **Note:** `ON `, `FROM `, `WITH KEY = `, `WHERE `, `GROUP BY `, and `LIMIT/OFFSET` clauses are optional. > When using these query clauses, the query falls back to an exact count. diff --git a/content/influxdb/v1.8/supported_protocols/collectd.md b/content/influxdb/v1.8/supported_protocols/collectd.md index 706b1e174..3ac177a80 100644 --- a/content/influxdb/v1.8/supported_protocols/collectd.md +++ b/content/influxdb/v1.8/supported_protocols/collectd.md @@ -1,7 +1,7 @@ --- title: CollectD protocol support in InfluxDB description: > - The collectd input allows InfluxDB to accept data transmitted in collectd native format. + The collectd input allows InfluxDB to accept data transmitted in collectd native format. aliases: - /influxdb/v1.8/tools/collectd/ menu: @@ -11,13 +11,11 @@ menu: parent: Supported protocols --- -# The collectd input - The [collectd](https://collectd.org) input allows InfluxDB to accept data transmitted in collectd native format. This data is transmitted over UDP. ## A note on UDP/IP buffer sizes -If you're running Linux or FreeBSD, please adjust your operating system UDP buffer size limit, [see here for more details.](/influxdb/v1.8/supported_protocols/udp/#a-note-on-udpip-os-buffer-sizes) +If you're running Linux or FreeBSD, please adjust your operating system UDP buffer size limit, [see here for more details.](/influxdb/v1.8/supported_protocols/udp/#a-note-on-udp-ip-os-buffer-sizes) ## Configuration diff --git a/content/influxdb/v1.8/tools/api.md b/content/influxdb/v1.8/tools/api.md index 68c56050a..9c551005d 100644 --- a/content/influxdb/v1.8/tools/api.md +++ b/content/influxdb/v1.8/tools/api.md @@ -355,7 +355,7 @@ POST http://localhost:8086/query | GET | Use for all queries that start with:

[`SELECT`](/influxdb/v1.8/query_language/spec/#select)*

[`SHOW`](/influxdb/v1.8/query_language/spec/#show-continuous-queries) | | POST | Use for all queries that start with:

[`ALTER`](/influxdb/v1.8/query_language/spec/#alter-retention-policy)

[`CREATE`](/influxdb/v1.8/query_language/spec/#create-continuous-query)

[`DELETE`](/influxdb/v1.8/query_language/spec/#delete)

[`DROP`](/influxdb/v1.8/query_language/spec/#drop-continuous-query)

[`GRANT`](/influxdb/v1.8/query_language/spec/#grant)

[`KILL`](/influxdb/v1.8/query_language/spec/#kill-query)

[`REVOKE`](/influxdb/v1.8/query_language/spec/#revoke) | -\* The only exceptions are `SELECT` queries that include an [`INTO` clause](/influxdb/v1.8/query_language/data_exploration/#the-into-clause). +\* The only exceptions are `SELECT` queries that include an [`INTO` clause](/influxdb/v1.8/query_language/explore-data/#the-into-clause). Those `SELECT` queries require a `POST` request. #### Examples @@ -390,7 +390,7 @@ $ curl -XPOST 'http://localhost:8086/query?db=mydb' --data-urlencode 'q=SELECT * {"results":[{"statement_id":0,"series":[{"name":"result","columns":["time","written"],"values":[["1970-01-01T00:00:00Z",2]]}]}]} ``` -`SELECT` queries that include and [`INTO` clause](/influxdb/v1.8/query_language/data_exploration/#the-into-clause) require a `POST` request. +`SELECT` queries that include and [`INTO` clause](/influxdb/v1.8/query_language/explore-data/#the-into-clause) require a `POST` request. The response shows that InfluxDB writes two points to the `newmeas` [measurement](/influxdb/v1.8/concepts/glossary/#measurement). Note that the system uses epoch 0 (`1970-01-01T00:00:00Z`) as a [null timestamp equivalent](/influxdb/v1.8/troubleshooting/frequently-asked-questions/#why-does-my-query-return-epoch-0-as-the-timestamp). @@ -403,7 +403,7 @@ $ curl -XPOST 'http://localhost:8086/query' --data-urlencode 'q=CREATE DATABASE {"results":[{"statement_id":0}]} ``` -A successful [`CREATE DATABASE` query](/influxdb/v1.8/query_language/database_management/#create-database) returns no additional information. +A successful [`CREATE DATABASE` query](/influxdb/v1.8/query_language/manage-database/#create-database) returns no additional information. #### Query string parameters @@ -484,7 +484,7 @@ $ curl -XPOST 'http://localhost:8086/query?u=myusername&p=mypassword' --data-url {"results":[{"statement_id":0}]} ``` -A successful [`CREATE DATABASE` query](/influxdb/v1.8/query_language/database_management/#create-database) returns no additional information. +A successful [`CREATE DATABASE` query](/influxdb/v1.8/query_language/manage-database/#create-database) returns no additional information. Invalid credentials: @@ -504,7 +504,7 @@ $ curl -XPOST -u myusername:mypassword 'http://localhost:8086/query' --data-urle {"results":[{"statement_id":0}]} ``` -A successful [`CREATE DATABASE` query](/influxdb/v1.8/query_language/database_management/#create-database) returns no additional information. +A successful [`CREATE DATABASE` query](/influxdb/v1.8/query_language/manage-database/#create-database) returns no additional information. The following example uses invalid credentials. diff --git a/content/influxdb/v1.8/tools/api_client_libraries.md b/content/influxdb/v1.8/tools/api_client_libraries.md index c765ebab3..f52e4fcc9 100644 --- a/content/influxdb/v1.8/tools/api_client_libraries.md +++ b/content/influxdb/v1.8/tools/api_client_libraries.md @@ -14,7 +14,7 @@ menu: InfluxDB client libraries are language-specific packages that integrate with the InfluxDB 2.0 API and support both **InfluxDB 1.8+** and **InfluxDB 2.0**. ->**Note:** We recommend using the new client libraries on this page to leverage the new read (via Flux) and write APIs and prepare for conversion to InfluxDB 2.0 and InfluxDB Cloud 2.0. For more information, see [InfluxDB 2.0 API compatibility endpoints](/influxdb/v1.8/tools/api/#influxdb-2.0-compatibility-endpoints). Client libraries for [InfluxDB 1.7 and earlier](/influxdb/v1.7/tools/api_client_libraries/) may continue to work, but are not maintained by InfluxData. +>**Note:** We recommend using the new client libraries on this page to leverage the new read (via Flux) and write APIs and prepare for conversion to InfluxDB 2.0 and InfluxDB Cloud 2.0. For more information, see [InfluxDB 2.0 API compatibility endpoints](/influxdb/v1.8/tools/api/#influxdb-2-0-api-compatibility-endpoints). Client libraries for [InfluxDB 1.7 and earlier](/influxdb/v1.7/tools/api_client_libraries/) may continue to work, but are not maintained by InfluxData. ## Client libraries diff --git a/content/influxdb/v1.8/tools/shell.md b/content/influxdb/v1.8/tools/shell.md index f76d4dba6..3a0e62e36 100644 --- a/content/influxdb/v1.8/tools/shell.md +++ b/content/influxdb/v1.8/tools/shell.md @@ -82,7 +82,7 @@ Set the write consistency level. The database to which `influx` connects. `-execute 'command'` -Execute an [InfluxQL](/influxdb/v1.8/query_language/data_exploration/) command and quit. +Execute an [InfluxQL](/influxdb/v1.8/query_language/explore-data/) command and quit. See [-execute](/influxdb/v1.8/tools/shell/#execute-an-influxql-command-and-quit-with-execute). `-format 'json|csv|column'` @@ -245,9 +245,9 @@ $ influx -format=json -pretty The import file has two sections: -* **DDL (Data Definition Language)**: Contains the [InfluxQL commands](/influxdb/v1.8/query_language/database_management/) for creating the relevant [database](/influxdb/v1.8/concepts/glossary/) and managing the [retention policy](/influxdb/v1.8/concepts/glossary/#retention-policy-rp). +* **DDL (Data Definition Language)**: Contains the [InfluxQL commands](/influxdb/v1.8/query_language/manage-database/) for creating the relevant [database](/influxdb/v1.8/concepts/glossary/) and managing the [retention policy](/influxdb/v1.8/concepts/glossary/#retention-policy-rp). If your database and retention policy already exist, your file can skip this section. -* **DML (Data Manipulation Language)**: Lists the relevant database and (if desired) retention policy and contains the data in [line protocol](/influxdb/v1.8/concepts/glossary/#line-protocol). +* **DML (Data Manipulation Language)**: Lists the relevant database and (if desired) retention policy and contains the data in [line protocol](/influxdb/v1.8/concepts/glossary/#influxdb-line-protocol). Example: @@ -373,7 +373,7 @@ If you do not specify the retention policy, `influx` automatically queries the ` #### Write data to InfluxDB with `insert` -Enter `insert` followed by the data in [line protocol](/influxdb/v1.8/concepts/glossary/#line-protocol) to write data to InfluxDB. +Enter `insert` followed by the data in [line protocol](/influxdb/v1.8/concepts/glossary/#influxdb-line-protocol) to write data to InfluxDB. Use `insert into ` to write data to a specific [retention policy](/influxdb/v1.8/concepts/glossary/#retention-policy-rp). Write data to a single field in the measurement `treasures` with the tag `captain_id = pirate_king`. @@ -394,4 +394,4 @@ Using retention policy oneday Execute all InfluxQL queries in `influx`. -See [Data exploration](/influxdb/v1.8/query_language/data_exploration/), [Schema exploration](/influxdb/v1.8/query_language/schema_exploration/), [Database management](/influxdb/v1.8/query_language/database_management/), [Authentication and authorization](/influxdb/v1.8/administration/authentication_and_authorization/) for InfluxQL documentation. +See [Data exploration](/influxdb/v1.8/query_language/explore-data/), [Schema exploration](/influxdb/v1.8/query_language/explore-schema/), [Database management](/influxdb/v1.8/query_language/manage-database/), [Authentication and authorization](/influxdb/v1.8/administration/authentication_and_authorization/) for InfluxQL documentation. diff --git a/content/influxdb/v1.8/troubleshooting/errors.md b/content/influxdb/v1.8/troubleshooting/errors.md index f03a03338..3952c2de4 100644 --- a/content/influxdb/v1.8/troubleshooting/errors.md +++ b/content/influxdb/v1.8/troubleshooting/errors.md @@ -28,7 +28,7 @@ The relevant `SHOW` queries include `SHOW RETENTION POLICIES`, `SHOW SERIES`, `SHOW MEASUREMENTS`, `SHOW TAG KEYS`, `SHOW TAG VALUES`, and `SHOW FIELD KEYS`. **Resources:** -[Schema exploration](/influxdb/v1.8/query_language/schema_exploration/), +[Schema exploration](/influxdb/v1.8/query_language/explore-schema/), [InfluxQL reference](/influxdb/v1.8/query_language/spec/) ## `error: max series per database exceeded: < >` @@ -236,7 +236,7 @@ time water_level ``` **Resources:** -[Data Exploration](/influxdb/v1.8/query_language/data_exploration/#time-syntax) +[Data Exploration](/influxdb/v1.8/query_language/explore-data/#time-syntax) ## `unable to parse < >: bad timestamp` diff --git a/content/influxdb/v1.8/troubleshooting/frequently-asked-questions.md b/content/influxdb/v1.8/troubleshooting/frequently-asked-questions.md index b03347177..21e72a0ce 100644 --- a/content/influxdb/v1.8/troubleshooting/frequently-asked-questions.md +++ b/content/influxdb/v1.8/troubleshooting/frequently-asked-questions.md @@ -146,12 +146,12 @@ The table below outlines the default relationship between the `DURATION` of an R Users can also configure the shard group duration with the -[`CREATE RETENTION POLICY`](/influxdb/v1.8/query_language/database_management/#create-retention-policies-with-create-retention-policy) +[`CREATE RETENTION POLICY`](/influxdb/v1.8/query_language/manage-database/#create-retention-policies-with-create-retention-policy) and -[`ALTER RETENTION POLICY`](/influxdb/v1.8/query_language/database_management/#modify-retention-policies-with-alter-retention-policy) +[`ALTER RETENTION POLICY`](/influxdb/v1.8/query_language/manage-database/#modify-retention-policies-with-alter-retention-policy) statements. Check your retention policy's shard group duration with the -[`SHOW RETENTION POLICIES`](/influxdb/v1.8/query_language/schema_exploration/#show-retention-policies) +[`SHOW RETENTION POLICIES`](/influxdb/v1.8/query_language/explore-schema/#show-retention-policies) statement. ## Why aren't data dropped after I've altered a retention policy? @@ -244,7 +244,7 @@ If a non-admin user attempts to `USE` a database on which the user doesn't have ERR: Database doesn't exist. Run SHOW DATABASES for a list of existing databases. ``` -> **Note** that the [`SHOW DATABASES` query](/influxdb/v1.8/query_language/schema_exploration/#show-databases) returns only those databases on which the non-admin user has `READ` and/or `WRITE` permissions. +> **Note** that the [`SHOW DATABASES` query](/influxdb/v1.8/query_language/explore-schema/#show-databases) returns only those databases on which the non-admin user has `READ` and/or `WRITE` permissions. ## How do I write to a non-DEFAULT retention policy with the InfluxDB CLI? @@ -300,10 +300,10 @@ Field value types cannot differ within a ### The SELECT statement The -[`SELECT` statement](/influxdb/v1.8/query_language/data_exploration/#the-basic-select-statement) +[`SELECT` statement](/influxdb/v1.8/query_language/explore-data/#the-basic-select-statement) returns all field values **if** all values have the same type. If field value types differ across shards, InfluxDB first performs any -applicable [cast](/influxdb/v1.8/query_language/data_exploration/#cast-operations) +applicable [cast](/influxdb/v1.8/query_language/explore-data/#cast-operations) operations and then returns all values with the type that occurs first in the following list: float, integer, string, Boolean. @@ -385,7 +385,7 @@ Timestamps outside that range return a [parsing error](/influxdb/v1.8/troublesho ## How can I tell what type of data is stored in a field? -The [`SHOW FIELD KEYS`](/influxdb/v1.8/query_language/schema_exploration/#show-field-keys) query also returns the field's type. +The [`SHOW FIELD KEYS`](/influxdb/v1.8/query_language/explore-schema/#show-field-keys) query also returns the field's type. #### Example @@ -406,7 +406,7 @@ Currently, InfluxDB offers very limited support for changing a field's data type The `::` syntax supports casting field values from integers to floats or from floats to integers. -See [Cast Operations](/influxdb/v1.8/query_language/data_exploration/#data-types-and-cast-operations) +See [Cast Operations](/influxdb/v1.8/query_language/explore-data/#data-types-and-cast-operations) for an example. There is no way to cast a float or integer to a string or Boolean (or vice versa). @@ -437,7 +437,7 @@ For how this will affect your queries, please see ## How do I perform mathematical operations within a function? Currently, InfluxDB does not support mathematical operations within functions. -We recommend using InfluxQL's [subqueries](/influxdb/v1.8/query_language/data_exploration/#subqueries) +We recommend using InfluxQL's [subqueries](/influxdb/v1.8/query_language/explore-data/#subqueries) as a workaround. ### Example @@ -455,7 +455,7 @@ Instead, use a subquery to get the same result: ``` See the -[Data Exploration](/influxdb/v1.8/query_language/data_exploration/#subqueries) +[Data Exploration](/influxdb/v1.8/query_language/explore-data/#subqueries) page for more information. ## Why does my query return epoch 0 as the timestamp? @@ -477,12 +477,12 @@ The following InfluxQL functions support nesting: * [`HOLT_WINTERS()`](/influxdb/v1.8/query_language/functions/#holt-winters) and [`HOLT_WINTERS_WITH_FIT()`](/influxdb/v1.8/query_language/functions/#holt-winters) For information on how to use a subquery as a substitute for nested functions, see -[Data exploration](/influxdb/v1.8/query_language/data_exploration/#subqueries). +[Data exploration](/influxdb/v1.8/query_language/explore-data/#subqueries). ## What determines the time intervals returned by `GROUP BY time()` queries? The time intervals returned by `GROUP BY time()` queries conform to the InfluxDB database's preset time -buckets or to the user-specified [offset interval](/influxdb/v1.8/query_language/data_exploration/#advanced-group-by-time-syntax). +buckets or to the user-specified [offset interval](/influxdb/v1.8/query_language/explore-data/#advanced-group-by-time-syntax). #### Example @@ -556,7 +556,7 @@ WHERE time >= '2016-08-29T18:15:00Z' AND time <= '2016-08-29T19:45:00Z' GROUP BY ``` In this example, the user-specified -[offset interval](/influxdb/v1.8/query_language/data_exploration/#advanced-group-by-time-syntax) +[offset interval](/influxdb/v1.8/query_language/explore-data/#advanced-group-by-time-syntax) shifts the InfluxDB database's preset time buckets forward by `15` minutes. The average for the 6pm time bucket now includes data between 6:15pm and 7pm, and the average for the 7pm time bucket includes data between 7:15pm and 8pm. @@ -598,7 +598,7 @@ time sunflowers time mean The most common reasons why your query returns no data or partial data: -- [Querying the wrong retention policy](#querying-wrong-retention-policy) (no data returned) +- [Querying the wrong retention policy](#querying-the-wrong-retention-policy) (no data returned) - [No field key in the SELECT clause](#no-field-key-in-the-select-clause) (no data returned) - [SELECT query includes `GROUP BY time()`](#select-query-includes-group-by-time) (partial data before `now()` returned) - [Tag and field key with the same name](#tag-and-field-key-with-the-same-name) @@ -609,13 +609,13 @@ InfluxDB automatically queries data in a database’s `DEFAULT` retention policy ### No field key in the SELECT clause -A query requires at least one [field key](/influxdb/v1.8/concepts/glossary/#field-key) in the `SELECT` clause. If the `SELECT` clause includes only [tag keys](/influxdb/v1.8/concepts/glossary/#tag-key), the query returns an empty response. For more information, see [Data exploration](/influxdb/v1.8/query_language/data_exploration/#common-issues-with-the-select-statement). +A query requires at least one [field key](/influxdb/v1.8/concepts/glossary/#field-key) in the `SELECT` clause. If the `SELECT` clause includes only [tag keys](/influxdb/v1.8/concepts/glossary/#tag-key), the query returns an empty response. For more information, see [Data exploration](/influxdb/v1.8/query_language/explore-data/#common-issues-with-the-select-statement). ### SELECT query includes `GROUP BY time()` -If your `SELECT` query includes a [`GROUP BY time()` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals), only data points between `1677-09-21 00:12:43.145224194` and [`now()`](/influxdb/v1.8/concepts/glossary/#now) are returned. Therefore, if any of your data points occur after `now()`, specify [an alternative upper bound](/influxdb/v1.8/query_language/data_exploration/#time-syntax) in your time interval. +If your `SELECT` query includes a [`GROUP BY time()` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals), only data points between `1677-09-21 00:12:43.145224194` and [`now()`](/influxdb/v1.8/concepts/glossary/#now) are returned. Therefore, if any of your data points occur after `now()`, specify [an alternative upper bound](/influxdb/v1.8/query_language/explore-data/#time-syntax) in your time interval. -(By default, most [`SELECT` queries](/influxdb/v1.8/query_language/data_exploration/#the-basic-select-statement) query data with timestamps between `1677-09-21 00:12:43.145224194` and `2262-04-11T23:47:16.854775806Z` UTC.) +(By default, most [`SELECT` queries](/influxdb/v1.8/query_language/explore-data/#the-basic-select-statement) query data with timestamps between `1677-09-21 00:12:43.145224194` and `2262-04-11T23:47:16.854775806Z` UTC.) ### Tag and field key with the same name @@ -723,12 +723,12 @@ Avoid using the same name for a tag and field key. If you inadvertently add the ## Why don't my GROUP BY time() queries return timestamps that occur after now()? Most `SELECT` statements have a default time range between [`1677-09-21 00:12:43.145224194` and `2262-04-11T23:47:16.854775806Z` UTC](#what-are-the-minimum-and-maximum-timestamps-that-influxdb-can-store). -For `SELECT` statements with a [`GROUP BY time()` clause](/influxdb/v1.8/query_language/data_exploration/#group-by-time-intervals), the default time +For `SELECT` statements with a [`GROUP BY time()` clause](/influxdb/v1.8/query_language/explore-data/#group-by-time-intervals), the default time range is between `1677-09-21 00:12:43.145224194` UTC and [`now()`](/influxdb/v1.8/concepts/glossary/#now). To query data with timestamps that occur after `now()`, `SELECT` statements with a `GROUP BY time()` clause must provide an alternative upper bound in the -[`WHERE` clause](/influxdb/v1.8/query_language/data_exploration/#the-where-clause). +[`WHERE` clause](/influxdb/v1.8/query_language/explore-data/#the-where-clause). In the following example, the first query covers data with timestamps between `2015-09-18T21:30:00Z` and `now()`. @@ -750,7 +750,7 @@ the lower bound to `now()` such that the query's time range is between > ``` -For for more on time syntax in queries, see [Data Exploration](/influxdb/v1.8/query_language/data_exploration/#time-syntax). +For for more on time syntax in queries, see [Data Exploration](/influxdb/v1.8/query_language/explore-data/#time-syntax). ## Can I perform mathematical operations against timestamps? @@ -813,7 +813,7 @@ Yes: `SELECT "water_level" FROM "h2o_feet" WHERE time > '2015-08-18T23:00:01.232 No: `SELECT "water_level" FROM "h2o_feet" WHERE time > "2015-08-18T23:00:01.232000000Z" AND time < "2015-09-19"` -See [Data Exploration](/influxdb/v1.8/query_language/data_exploration/#time-syntax) for more on time syntax in queries. +See [Data Exploration](/influxdb/v1.8/query_language/explore-data/#time-syntax) for more on time syntax in queries. ## Why am I missing data after creating a new DEFAULT retention policy? @@ -833,7 +833,7 @@ time count 1970-01-01T00:00:00Z 8 ``` -We [create](/influxdb/v1.8/query_language/database_management/#create-retention-policies-with-create-retention-policy) a new `DEFAULT` RP (`two_hour`) and perform the same query: +We [create](/influxdb/v1.8/query_language/manage-database/#create-retention-policies-with-create-retention-policy) a new `DEFAULT` RP (`two_hour`) and perform the same query: ```sql > SELECT count(flounders) FROM fleeting @@ -1048,9 +1048,9 @@ InfluxDB maintains an in-memory index of every [series](/influxdb/v1.8/concepts/ ## How can I remove series from the index? To reduce series cardinality, series must be dropped from the index. -[`DROP DATABASE`](/influxdb/v1.8/query_language/database_management/#delete-a-database-with-drop-database), -[`DROP MEASUREMENT`](/influxdb/v1.8/query_language/database_management/#delete-measurements-with-drop-measurement), and -[`DROP SERIES`](/influxdb/v1.8/query_language/database_management/#drop-series-from-the-index-with-drop-series) will all remove series from the index and reduce the overall series cardinality. +[`DROP DATABASE`](/influxdb/v1.8/query_language/manage-database/#delete-a-database-with-drop-database), +[`DROP MEASUREMENT`](/influxdb/v1.8/query_language/manage-database/#delete-measurements-with-drop-measurement), and +[`DROP SERIES`](/influxdb/v1.8/query_language/manage-database/#drop-series-from-the-index-with-drop-series) will all remove series from the index and reduce the overall series cardinality. > **Note:** `DROP` commands are usually CPU-intensive, as they frequently trigger a TSM compaction. Issuing `DROP` queries at a high frequency may significantly impact write and other query throughput. @@ -1246,7 +1246,7 @@ For users who want to write sparse, historical data to InfluxDB, InfluxData reco First, lengthening your [retention policy](/influxdb/v1.8/concepts/glossary/#retention-policy-rp)‘s [shard group](/influxdb/v1.8/concepts/glossary/#shard-group) duration to cover several years. The default shard group duration is one week and if your data cover several hundred years – well, that’s a lot of shards! Having an extremely high number of shards is inefficient for InfluxDB. -Increase the shard group duration for your data’s retention policy with the [`ALTER RETENTION POLICY` query](/influxdb/v1.8/query_language/database_management/#modify-retention-policies-with-alter-retention-policy). +Increase the shard group duration for your data’s retention policy with the [`ALTER RETENTION POLICY` query](/influxdb/v1.8/query_language/manage-database/#modify-retention-policies-with-alter-retention-policy). Second, temporarily lowering the [`cache-snapshot-write-cold-duration` configuration setting](/influxdb/v1.8/administration/config/#cache-snapshot-write-cold-duration-10m). If you’re writing a lot of historical data, the default setting (`10m`) can cause the system to hold all of your data in cache for every shard. diff --git a/content/influxdb/v2.0/get-started.md b/content/influxdb/v2.0/get-started.md index 294e553d5..68165d942 100644 --- a/content/influxdb/v2.0/get-started.md +++ b/content/influxdb/v2.0/get-started.md @@ -143,7 +143,7 @@ If you're running `influx` on macOS Catalina, you must [manually authorize the I #### Step 5: Set up a configuration profile -To avoid having to pass your InfluxDB [authentication token](/influxdb/v2.0/users/tokens/) with each `influx` command, set up a configuration profile that stores your credentials. +To avoid having to pass your InfluxDB [authentication token](/influxdb/v2.0/security/tokens/) with each `influx` command, set up a configuration profile that stores your credentials. In a terminal, run the following command: @@ -203,7 +203,7 @@ If you rename the binary, all references to `influx` in this documentation refer #### Step 4: Set up a configuration profile -To avoid having to pass your InfluxDB [authentication token](/influxdb/v2.0/users/tokens/) with each `influx` command, set up a configuration profile that stores your credentials. +To avoid having to pass your InfluxDB [authentication token](/influxdb/v2.0/security/tokens/) with each `influx` command, set up a configuration profile that stores your credentials. In a terminal, run the following command: @@ -540,7 +540,7 @@ You are ready to [write or collect data](/influxdb/v2.0/write-data). ### (Optional) Set up and use the influx CLI -If you set up InfluxDB through the UI and want to use the [`influx` CLI](/influxdb/v2.0/reference/cli/influx), we recommend setting up a configuration profile. This lets you avoid having to pass your InfluxDB [authentication token](/influxdb/v2.0/users/tokens/) with each `influx` command. Complete the following steps to set up a configuration profile that stores your credentials. +If you set up InfluxDB through the UI and want to use the [`influx` CLI](/influxdb/v2.0/reference/cli/influx), we recommend setting up a configuration profile. This lets you avoid having to pass your InfluxDB [authentication token](/influxdb/v2.0/security/tokens/) with each `influx` command. Complete the following steps to set up a configuration profile that stores your credentials. 1. In a terminal, run the following command: diff --git a/content/influxdb/v2.0/influxdb-templates/cloud.md b/content/influxdb/v2.0/influxdb-templates/cloud.md index fa4cae6aa..501b35d93 100644 --- a/content/influxdb/v2.0/influxdb-templates/cloud.md +++ b/content/influxdb/v2.0/influxdb-templates/cloud.md @@ -21,7 +21,7 @@ to apply and manage templates in your InfluxDB Cloud account. If you haven’t already, do the following: -1. [Download and install `influx` CLI](/influxdb/v2.0/get-started/#optional-download-and-install-the-influx-cli). +1. [Download and install `influx` CLI](/influxdb/v2.0/get-started/#optional-download-install-and-use-the-influx-cli). 2. [Configure the `influx` CLI](/influxdb/v2.0/get-started/#set-up-influxdb) to use your InfluxDB Cloud instance URL, organization, and tokens. 3. [Use the `influx` CLI](/influxdb/v2.0/reference/cli/influx/) to use, manage, and create diff --git a/content/influxdb/v2.0/influxdb-templates/create.md b/content/influxdb/v2.0/influxdb-templates/create.md index b726a069f..40e6165ac 100644 --- a/content/influxdb/v2.0/influxdb-templates/create.md +++ b/content/influxdb/v2.0/influxdb-templates/create.md @@ -48,7 +48,7 @@ In **InfluxDB Cloud**, your user account is an organization. - [notification endpoints](/influxdb/v2.0/monitor-alert/notification-endpoints/create/) - [notification rules](/influxdb/v2.0/monitor-alert/notification-rules/create/) - [tasks](/influxdb/v2.0/process-data/manage-tasks/create-task/) - - [Telegraf configurations](/influxdb/v2.0/write-data/use-telegraf/) + - [Telegraf configurations](/influxdb/v2.0/write-data/no-code/use-telegraf/) 4. Export the template _(see [below](#export-a-template))_. diff --git a/content/influxdb/v2.0/monitor-alert/templates/infrastructure/aws.md b/content/influxdb/v2.0/monitor-alert/templates/infrastructure/aws.md index 4798ae208..e5e6b66e5 100644 --- a/content/influxdb/v2.0/monitor-alert/templates/infrastructure/aws.md +++ b/content/influxdb/v2.0/monitor-alert/templates/infrastructure/aws.md @@ -19,7 +19,7 @@ The AWS CloudWatch Monitoring template includes the following: - two [buckets](/influxdb/v2.0/reference/glossary/#bucket): `kubernetes` and `cloudwatch` - two labels: `inputs.cloudwatch`, `AWS` - one variable: `v.bucket` -- one [Telegraf configuration](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/): [AWS CloudWatch input plugin](/influxdb/v2.0/reference/telegraf-plugins/#cloudwatch) +- one [Telegraf configuration](/influxdb/v2.0/telegraf-configs/): [AWS CloudWatch input plugin](/influxdb/v2.0/reference/telegraf-plugins/#cloudwatch) ## Apply the template diff --git a/content/influxdb/v2.0/monitor-alert/templates/infrastructure/docker.md b/content/influxdb/v2.0/monitor-alert/templates/infrastructure/docker.md index d6f6679ad..bf0d2cf99 100644 --- a/content/influxdb/v2.0/monitor-alert/templates/infrastructure/docker.md +++ b/content/influxdb/v2.0/monitor-alert/templates/infrastructure/docker.md @@ -17,7 +17,7 @@ The Docker Monitoring template includes the following: - one [dashboard](/influxdb/v2.0/reference/glossary/#dashboard): **Docker** - one [bucket](/influxdb/v2.0/reference/glossary/#bucket): `docker, 7d retention` - labels: Docker input plugin labels -- one [Telegraf configuration](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/): Docker input plugin +- one [Telegraf configuration](/influxdb/v2.0/telegraf-configs/): Docker input plugin - one variable: `bucket` - four [checks](/influxdb/v2.0/reference/glossary/#check): `Container cpu`, `mem`, `disk`, `non-zero exit` - one [notification endpoint](/influxdb/v2.0/reference/glossary/#notification-endpoint): `Http Post` @@ -37,7 +37,7 @@ For more information about how checks, notification endpoints, and notifications > **Note:** Ensure your `influx` CLI is configured with your account credentials and that configuration is active. For more information, see [influx config](/influxdb/v2.0/reference/cli/influx/config/). 2. [Install Telegraf](/{{< latest "telegraf" >}}/introduction/installation/) on a server with network access to both the Docker containers and [InfluxDB v2 API](/influxdb/v2.0/reference/api/). -3. In your [Telegraf configuration file (`telegraf.conf`)](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/), do the following: +3. In your [Telegraf configuration file (`telegraf.conf`)](/influxdb/v2.0/telegraf-configs/), do the following: - Depending on how you run Docker, you may need to customize the [Docker input plugin](/influxdb/v2.0/reference/telegraf-plugins/#docker) configuration, for example, you may need to specify the `endpoint` value. - Set the following environment variables: - INFLUX_TOKEN: Token must have permissions to read Telegraf configurations and write data to the `telegraf` bucket. See how to [view tokens](/influxdb/v2.0/security/tokens/view-tokens/). diff --git a/content/influxdb/v2.0/monitor-alert/templates/infrastructure/vshpere.md b/content/influxdb/v2.0/monitor-alert/templates/infrastructure/vshpere.md index f6e7d399d..12d0389d6 100644 --- a/content/influxdb/v2.0/monitor-alert/templates/infrastructure/vshpere.md +++ b/content/influxdb/v2.0/monitor-alert/templates/infrastructure/vshpere.md @@ -17,7 +17,7 @@ The Docker Monitoring template includes the following: - one [dashboard](/influxdb/v2.0/reference/glossary/#dashboard): **vsphere** - one [bucket](/influxdb/v2.0/reference/glossary/#bucket): `vsphere` - label: vsphere -- one [Telegraf configuration](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/): InfluxDB v2 output plugin, vSphere input plugin +- one [Telegraf configuration](/influxdb/v2.0/telegraf-configs/): InfluxDB v2 output plugin, vSphere input plugin - one variable: `bucket` ## Apply the template @@ -32,7 +32,7 @@ The Docker Monitoring template includes the following: > **Note:** Ensure your `influx` CLI is configured with your account credentials and that configuration is active. For more information, see [influx config](/influxdb/v2.0/reference/cli/influx/config/). 2. [Install Telegraf](/{{< latest "telegraf" >}}/introduction/installation/) on a server with network access to both the vSphere host and [InfluxDB v2 API](/influxdb/v2.0/reference/api/). -3. In your [Telegraf configuration file (`telegraf.conf`)](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/), do the following: +3. In your [Telegraf configuration file (`telegraf.conf`)](/influxdb/v2.0/telegraf-configs/), do the following: - Set the following environment variables: - INFLUX_TOKEN: Token must have permissions to read Telegraf configurations and write data to the `telegraf` bucket. See how to [view tokens](/influxdb/v2.0/security/tokens/view-tokens/). - INFLUX_ORG: Name of your organization. See how to [view your organization](/influxdb/v2.0/organizations/view-orgs/). diff --git a/content/influxdb/v2.0/monitor-alert/templates/infrastructure/windows.md b/content/influxdb/v2.0/monitor-alert/templates/infrastructure/windows.md index ebde10b53..ca15a8683 100644 --- a/content/influxdb/v2.0/monitor-alert/templates/infrastructure/windows.md +++ b/content/influxdb/v2.0/monitor-alert/templates/infrastructure/windows.md @@ -16,7 +16,7 @@ The Windows System Monitoring template includes the following: - one [dashboard](/influxdb/v2.0/reference/glossary/#dashboard): **Windows System** - one [bucket](/influxdb/v2.0/reference/glossary/#bucket): `telegraf`, 7d retention - label: `Windows System Template`, Telegraf plugin labels: `outputs.influxdb_v2` -- one [Telegraf configuration](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/): InfluxDB v2 output plugin, Windows Performance Counters input plugin +- one [Telegraf configuration](/influxdb/v2.0/telegraf-configs/): InfluxDB v2 output plugin, Windows Performance Counters input plugin - two variables: `bucket`, `windows_host` ## Apply the template @@ -31,7 +31,7 @@ The Windows System Monitoring template includes the following: > **Note:** Ensure your `influx` CLI is configured with your account credentials and that configuration is active. For more information, see [influx config](/influxdb/v2.0/reference/cli/influx/config/). 2. [Install Telegraf](/{{< latest "telegraf" >}}/introduction/installation/) on a server with network access to both the Windows system and [InfluxDB v2 API](/influxdb/v2.0/reference/api/). -3. In your [Telegraf configuration file (`telegraf.conf`)](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/), do the following: +3. In your [Telegraf configuration file (`telegraf.conf`)](/influxdb/v2.0/telegraf-configs/), do the following: - Set the following environment variables: - INFLUX_TOKEN: Token must have permissions to read Telegraf configurations and write data to the `telegraf` bucket. See how to [view tokens](/influxdb/v2.0/security/tokens/view-tokens/). - INFLUX_ORG: Name of your organization. See how to [view your organization](/influxdb/v2.0/organizations/view-orgs/). diff --git a/content/influxdb/v2.0/monitor-alert/templates/networks/haproxy.md b/content/influxdb/v2.0/monitor-alert/templates/networks/haproxy.md index fb9afa08d..869294898 100644 --- a/content/influxdb/v2.0/monitor-alert/templates/networks/haproxy.md +++ b/content/influxdb/v2.0/monitor-alert/templates/networks/haproxy.md @@ -17,7 +17,7 @@ The HAProxy for InfluxDB v2 template includes the following: - one [dashboard](/influxdb/v2.0/reference/glossary/#dashboard): **HAProxy** - one [bucket](/influxdb/v2.0/reference/glossary/#bucket): `haproxy` - label: `haproxy` -- one [Telegraf configuration](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/): HAProxy input plugin, InfluxDB v2 output plugin +- one [Telegraf configuration](/influxdb/v2.0/telegraf-configs/): HAProxy input plugin, InfluxDB v2 output plugin - one variable: `bucket` ## Apply the template @@ -32,7 +32,7 @@ The HAProxy for InfluxDB v2 template includes the following: > **Note:** Ensure your `influx` CLI is configured with your account credentials and that configuration is active. For more information, see [influx config](/influxdb/v2.0/reference/cli/influx/config/). 2. [Install Telegraf](/{{< latest "telegraf" >}}/introduction/installation/) on a server with network access to both the HAProxy instances and [InfluxDB v2 API](/influxdb/v2.0/reference/api/). -3. In your [Telegraf configuration file (`telegraf.conf`)](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/), do the following: +3. In your [Telegraf configuration file (`telegraf.conf`)](/influxdb/v2.0/telegraf-configs/), do the following: - Set the following environment variables: - INFLUX_TOKEN: Token must have permissions to read Telegraf configurations and write data to the `haproxy` bucket. See how to [view tokens](/influxdb/v2.0/security/tokens/view-tokens/). - INFLUX_ORG: Name of your organization. See how to [view your organization](/influxdb/v2.0/organizations/view-orgs/). diff --git a/content/influxdb/v2.0/query-data/flux/custom-functions/custom-aggregate.md b/content/influxdb/v2.0/query-data/flux/custom-functions/custom-aggregate.md index f43d03140..eb6e34364 100644 --- a/content/influxdb/v2.0/query-data/flux/custom-functions/custom-aggregate.md +++ b/content/influxdb/v2.0/query-data/flux/custom-functions/custom-aggregate.md @@ -142,7 +142,7 @@ it isn't included in the output table. ## Custom aggregate function examples To create custom aggregate functions, use principles outlined in -[Creating custom functions](/influxdb/v2.0/query-data/guides/custom-functions) +[Creating custom functions](/influxdb/v2.0/query-data/flux/custom-functions) and the `reduce()` function to aggregate rows in each input table. ### Create a custom average function diff --git a/content/influxdb/v2.0/query-data/flux/mathematic-operations.md b/content/influxdb/v2.0/query-data/flux/mathematic-operations.md index 9cc45a0fa..c082cc299 100644 --- a/content/influxdb/v2.0/query-data/flux/mathematic-operations.md +++ b/content/influxdb/v2.0/query-data/flux/mathematic-operations.md @@ -77,7 +77,7 @@ For example: {{% /note %}} ## Custom mathematic functions -Flux lets you [create custom functions](/influxdb/v2.0/query-data/guides/custom-functions) that use mathematic operations. +Flux lets you [create custom functions](/influxdb/v2.0/query-data/flux/custom-functions) that use mathematic operations. View the examples below. ###### Custom multiplication function diff --git a/content/influxdb/v2.0/query-data/flux/moving-average.md b/content/influxdb/v2.0/query-data/flux/moving-average.md index f7a7f3706..7203e5297 100644 --- a/content/influxdb/v2.0/query-data/flux/moving-average.md +++ b/content/influxdb/v2.0/query-data/flux/moving-average.md @@ -4,7 +4,7 @@ seotitle: Calculate the moving average in Flux list_title: Moving Average description: > Use the [`movingAverage()`](/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/movingaverage/) - or [`timedMovingAverage()`](/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/timedmovingaverage/) + or [`timedMovingAverage()`](/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/timedmovingaverage/) functions to return the moving average of data. weight: 210 aliases: @@ -21,7 +21,7 @@ list_query_example: moving_average --- Use the [`movingAverage()`](/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/movingaverage/) -or [`timedMovingAverage()`](/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/timedmovingaverage/) +or [`timedMovingAverage()`](/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/timedmovingaverage/) functions to return the moving average of data. ```js diff --git a/content/influxdb/v2.0/query-data/flux/rate.md b/content/influxdb/v2.0/query-data/flux/rate.md index 57607c693..ed302df6b 100644 --- a/content/influxdb/v2.0/query-data/flux/rate.md +++ b/content/influxdb/v2.0/query-data/flux/rate.md @@ -3,7 +3,7 @@ title: Calculate the rate of change seotitle: Calculate the rate of change in Flux list_title: Rate description: > - Use the [`derivative()` function](/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/derivative/) + Use the [`derivative()` function](/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/derivative/) to calculate the rate of change between subsequent values or the [`aggregate.rate()` function](/influxdb/v2.0/reference/flux/stdlib/experimental/aggregate/rate/) to calculate the average rate of change per window of time. @@ -24,7 +24,7 @@ list_query_example: rate_of_change --- -Use the [`derivative()` function](/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/derivative/) +Use the [`derivative()` function](/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/derivative/) to calculate the rate of change between subsequent values or the [`aggregate.rate()` function](/influxdb/v2.0/reference/flux/stdlib/experimental/aggregate/rate/) to calculate the average rate of change per window of time. @@ -35,7 +35,7 @@ making values easily comparable. - [Average rate of change per window of time](#average-rate-of-change-per-window-of-time) ## Rate of change between subsequent values -Use the [`derivative()` function](/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/derivative/) +Use the [`derivative()` function](/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/derivative/) to calculate the rate of change per unit of time between subsequent _non-null_ values. ```js diff --git a/content/influxdb/v2.0/query-data/get-started/syntax-basics.md b/content/influxdb/v2.0/query-data/get-started/syntax-basics.md index 64cc58e41..e391e9ac6 100644 --- a/content/influxdb/v2.0/query-data/get-started/syntax-basics.md +++ b/content/influxdb/v2.0/query-data/get-started/syntax-basics.md @@ -231,7 +231,7 @@ cpuUsageUser |> topN(n:5) |> yield() This query will return the five data points with the highest user CPU usage over the last hour. -_More information about creating custom functions is available in the [Custom functions](/influxdb/v2.0/query-data/guides/custom-functions) documentation._ +_More information about creating custom functions is available in the [Custom functions](/influxdb/v2.0/query-data/flux/custom-functions) documentation._