diff --git a/content/chronograf/v1.6/_index.md b/content/chronograf/v1.6/_index.md index 0ebc9fabe..0ac57bf9e 100644 --- a/content/chronograf/v1.6/_index.md +++ b/content/chronograf/v1.6/_index.md @@ -40,7 +40,7 @@ Chronograf offers a UI for [Kapacitor](https://github.com/influxdata/kapacitor), * Create and delete databases and retention policies * View currently-running queries and stop inefficient queries from overloading your system -* Create, delete, and assign permissions to users (Chronograf supports [InfluxDB OSS](/influxdb/latest/query_language/authentication_and_authorization/#authorization) and InfluxDB Enterprise user management) +* Create, delete, and assign permissions to users (Chronograf supports [InfluxDB OSS](/{{< latest "influxdb" "v1" >}}/query_language/authentication_and_authorization/#authorization) and InfluxDB Enterprise user management) ### Multi-organization and multi-user support diff --git a/content/chronograf/v1.6/about_the_project/release-notes-changelog.md b/content/chronograf/v1.6/about_the_project/release-notes-changelog.md index 2f74a4d17..b03e2d284 100644 --- a/content/chronograf/v1.6/about_the_project/release-notes-changelog.md +++ b/content/chronograf/v1.6/about_the_project/release-notes-changelog.md @@ -615,9 +615,9 @@ menu: ### UI improvements * When dashboard time range is changed, reset graphs that are zoomed in - * [Bar graph](/chronograf/latest/troubleshooting/frequently-asked-questions/#bar) option added to dashboard + * [Bar graph](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#bar) option added to dashboard * Redesign source management table to be more intuitive - * Redesign [Line + Single Stat](/chronograf/latest/troubleshooting/frequently-asked-questions/#line-stat) cells to appear more like a sparkline, and improve legibility + * Redesign [Line + Single Stat](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#line-stat) cells to appear more like a sparkline, and improve legibility ## v1.3.2.0 [2017-06-05] @@ -633,7 +633,7 @@ menu: ### Features - * Add UI to the Data Explorer for [writing data to InfluxDB](/chronograf/latest/guides/transition-web-admin-interface/#writing-data) + * Add UI to the Data Explorer for [writing data to InfluxDB](/{{< latest "chronograf" >}}/guides/transition-web-admin-interface/#writing-data) ### UI improvements @@ -653,26 +653,26 @@ In versions 1.3.1+, installing a new version of Chronograf automatically clears ### Bug fixes - * Fix infinite spinner when `/chronograf` is a [basepath](/chronograf/latest/administration/configuration/#p-basepath) + * Fix infinite spinner when `/chronograf` is a [basepath](/{{< latest "chronograf" >}}/administration/configuration/#p-basepath) * Remove the query templates dropdown from dashboard cell editor mode * Fix the backwards sort arrows in table column headers * Make the logout button consistent with design * Fix the loading spinner on graphs * Filter out any template variable values that are empty, whitespace, or duplicates - * Allow users to click the add query button after selecting singleStat as the [visualization type](/chronograf/latest/troubleshooting/frequently-asked-questions/#what-visualization-types-does-chronograf-support) + * Allow users to click the add query button after selecting singleStat as the [visualization type](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#what-visualization-types-does-chronograf-support) * Add a query for windows uptime - thank you, @brianbaker! ### Features - * Add log [event handler](/chronograf/latest/troubleshooting/frequently-asked-questions/#what-kapacitor-event-handlers-are-supported-in-chronograf) - thank you, @mpchadwick! + * Add log [event handler](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#what-kapacitor-event-handlers-are-supported-in-chronograf) - thank you, @mpchadwick! * Update Go (golang) vendoring to dep and committed vendor directory - * Add autocomplete functionality to [template variable](/chronograf/latest/guides/dashboard-template-variables/) dropdowns + * Add autocomplete functionality to [template variable](/{{< latest "chronograf" >}}/guides/dashboard-template-variables/) dropdowns ### UI improvements * Refactor scrollbars to support non-webkit browsers * Increase the query builder's default height in cell editor mode and in the data explorer - * Make the [template variables](/chronograf/latest/guides/dashboard-template-variables/) manager more space efficient + * Make the [template variables](/{{< latest "chronograf" >}}/guides/dashboard-template-variables/) manager more space efficient * Add page spinners to pages that did not have them * Denote which source is connected in the sources table * Use milliseconds in the InfluxDB dashboard instead of nanoseconds @@ -682,25 +682,25 @@ In versions 1.3.1+, installing a new version of Chronograf automatically clears ### Bug fixes - * Fix the link to home when using the [`--basepath` option](/chronograf/latest/administration/configuration/#p-basepath) + * Fix the link to home when using the [`--basepath` option](/{{< latest "chronograf" >}}/administration/configuration/#p-basepath) * Remove the notification to login on the login page * Support queries that perform math on functions * Prevent the creation of blank template variables * Ensure thresholds for Kapacitor Rule Alerts appear on page load * Update the Kapacitor configuration page when the configuration changes - * Fix Authentication when using Chronograf with a set [basepath](/chronograf/latest/administration/configuration/#p-basepath) + * Fix Authentication when using Chronograf with a set [basepath](/{{< latest "chronograf" >}}/administration/configuration/#p-basepath) * Show red indicator on Hosts Page for an offline host * Support escaping from presentation mode in Safari * Re-implement level colors on the alerts page * Fix router bug introduced by upgrading to react-router v3.0 - * Show legend on [Line+Stat](/chronograf/latest/troubleshooting/frequently-asked-questions/#line-stat) visualization type + * Show legend on [Line+Stat](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#line-stat) visualization type * Prevent queries with `:dashboardTime:` from breaking the query builder ### Features * Add line-protocol proxy for InfluxDB/InfluxDB Enterprise Cluster data sources * Add `:dashboardTime:` to support cell-specific time ranges on dashboards - * Add support for enabling and disabling [TICKscripts that were created outside Chronograf](/chronograf/latest/guides/advanced-kapacitor/#tickscript-management) + * Add support for enabling and disabling [TICKscripts that were created outside Chronograf](/{{< latest "chronograf" >}}/guides/advanced-kapacitor/#tickscript-management) * Allow users to delete Kapacitor configurations ### UI improvements diff --git a/content/chronograf/v1.6/administration/chrono-on-clusters.md b/content/chronograf/v1.6/administration/chrono-on-clusters.md index 2fae79dd0..bda55c88d 100644 --- a/content/chronograf/v1.6/administration/chrono-on-clusters.md +++ b/content/chronograf/v1.6/administration/chrono-on-clusters.md @@ -8,7 +8,7 @@ menu: parent: Administration --- -The connection details form requires additional information when connecting Chronograf to an [InfluxDB Enterprise cluster](https://docs.influxdata.com/enterprise_influxdb/latest/). +The connection details form requires additional information when connecting Chronograf to an [InfluxDB Enterprise cluster](/{{< latest "enterprise_influxdb" >}}/). When you enter the InfluxDB HTTP bind address in the `Connection String` input, Chronograf automatically checks if that InfluxDB instance is a data node. If it is a data node, Chronograf automatically adds the `Meta Service Connection URL` input to the connection details form. @@ -19,4 +19,4 @@ Enter the HTTP bind address of one of your cluster's meta nodes into that input Note that the example above assumes that you do not have authentication enabled. If you have authentication enabled, the form requires username and password information. -For details about monitoring InfluxDB Enterprise clusters, see [Monitoring InfluxDB Enterprise clusters](/chronograf/latest/guides/monitoring-influxenterprise-clusters/). +For details about monitoring InfluxDB Enterprise clusters, see [Monitoring InfluxDB Enterprise clusters](/{{< latest "chronograf" >}}/guides/monitoring-influxenterprise-clusters/). diff --git a/content/chronograf/v1.6/administration/config-options.md b/content/chronograf/v1.6/administration/config-options.md index e9347dc7c..5a3b9ade9 100644 --- a/content/chronograf/v1.6/administration/config-options.md +++ b/content/chronograf/v1.6/administration/config-options.md @@ -78,7 +78,7 @@ Environment variable: `$BOLT_PATH` #### `--canned-path=` | `-c` -The path to the directory of [canned dashboards](/chronograf/latest/guides/using-precreated-dashboards/) files. +The path to the directory of [canned dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards/) files. Default value: `/usr/share/chronograf/canned` diff --git a/content/chronograf/v1.6/administration/configuration.md b/content/chronograf/v1.6/administration/configuration.md index 51154f1e9..e7741ae8b 100644 --- a/content/chronograf/v1.6/administration/configuration.md +++ b/content/chronograf/v1.6/administration/configuration.md @@ -47,12 +47,12 @@ It is neither created nor used in macOS. ## Enabling security, multi-organization, and multi-user support -See [Managing security](/chronograf/latest/administration/managing-security) for details on configuring authentication options for Chronograf using the JWT and OAuth 2.0 authentication protocols. +See [Managing security](/{{< latest "chronograf" >}}/administration/managing-security) for details on configuring authentication options for Chronograf using the JWT and OAuth 2.0 authentication protocols. After you configure OAuth 2.0 authentication in Chronograf, you can use the multi-organization and multi-user support described in detail here: -* [Managing organizations](/chronograf/latest/administration/managing-organizations) -* [Managing Chronograf users](/chronograf/latest/administration/managing-chronograf-users) +* [Managing organizations](/{{< latest "chronograf" >}}/administration/managing-organizations) +* [Managing Chronograf users](/{{< latest "chronograf" >}}/administration/managing-chronograf-users) diff --git a/content/chronograf/v1.6/administration/creating-connections.md b/content/chronograf/v1.6/administration/creating-connections.md index 151f295c1..bf5c5a4f3 100644 --- a/content/chronograf/v1.6/administration/creating-connections.md +++ b/content/chronograf/v1.6/administration/creating-connections.md @@ -26,9 +26,9 @@ To create an InfluxDB connection in the Chronograf UI: * **Connection String**: Enter the hostname or IP address of the InfluxDB instance and the port. The field is prefilled with `http://localhost:8086`. * **Name**: Enter the name for this connection. * **Username**: Enter the username that will be shared for this connection. - *Only required if [authorization is enabled](/influxdb/latest/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.* + *Only required if [authorization is enabled](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.* * **Password**: Enter the password. - *Only required if [authorization is enabled](/influxdb/latest/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.* + *Only required if [authorization is enabled](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.* * **Telegraf Database**: Enter the name of the Telegraf database. The field is prefilled with `telegraf`. * **Default Retention Policy**: Enter the name of the default [retention policy](/influxdb/v1.6/concepts/glossary/#retention-policy-rp). If none is provided, it assumes `autogen`. * **Make this the default source**: By default, this option is selected and this InfluxDB connection will be used when Chronograf is launched. @@ -75,11 +75,11 @@ Any string you want to use as the display name of the source. #### `username` Username used to access the InfluxDB server or cluster. -*Only required if [authorization is enabled](/influxdb/latest/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.* +*Only required if [authorization is enabled](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.* #### `password` Password used to access the InfluxDB server or cluster. -*Only required if [authorization is enabled](/influxdb/latest/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.* +*Only required if [authorization is enabled](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.* #### `url` URL of the InfluxDB server or cluster. @@ -143,9 +143,9 @@ To create a Kapacitor connection using the Chronograf UI: * **Kapacitor URL**: Enter the hostname or IP address of the Kapacitor instance and the port. The field is prefilled with `http://localhost:9092`. * **Name**: Enter the name for this connection. * **Username**: Enter the username that will be shared for this connection. - *Only required if [authorization is enabled](/kapacitor/latest/administration/security/#kapacitor-authentication-and-authorization) on the Kapacitor instance or cluster to which you're connecting.* + *Only required if [authorization is enabled](/{{< latest "kapacitor" >}}/administration/security/#kapacitor-authentication-and-authorization) on the Kapacitor instance or cluster to which you're connecting.* * **Password**: Enter the password. - *Only required if [authorization is enabled](/kapacitor/latest/administration/security/#kapacitor-authentication-and-authorization) on the Kapacitor instance or cluster to which you're connecting.* + *Only required if [authorization is enabled](/{{< latest "kapacitor" >}}/administration/security/#kapacitor-authentication-and-authorization) on the Kapacitor instance or cluster to which you're connecting.* 4. Click **Connect**. If the connection is valid, the message "Kapacitor Created! Configuring endpoints is optional." appears. To configure alert endpoints, see [Configuring alert endpoints](/chronograf/v1.6/guides/configuring-alert-endpoints/). diff --git a/content/chronograf/v1.6/administration/managing-influxdb-users.md b/content/chronograf/v1.6/administration/managing-influxdb-users.md index 8156390d6..8948867e6 100644 --- a/content/chronograf/v1.6/administration/managing-influxdb-users.md +++ b/content/chronograf/v1.6/administration/managing-influxdb-users.md @@ -13,7 +13,7 @@ menu: The **Chronograf Admin** provides InfluxDB user management for InfluxDB OSS and InfluxDB Enterprise users. -> ***Note:*** For details on Chronograf user authentication and management, see [Managing security](/chronograf/latest/administration/managing-security/). +> ***Note:*** For details on Chronograf user authentication and management, see [Managing security](/{{< latest "chronograf" >}}/administration/managing-security/). **On this page:** @@ -58,7 +58,7 @@ Restart the InfluxDB service for your configuration changes to take effect: ### Step 3: Create an admin user. -Because authentication is enabled, you need to create an [admin user](/influxdb/latest/query_language/authentication_and_authorization/#user-types-and-privileges) before you can do anything else in the database. +Because authentication is enabled, you need to create an [admin user](/{{< latest "influxdb" "v1" >}}/query_language/authentication_and_authorization/#user-types-and-privileges) before you can do anything else in the database. Run the `curl` command below to create an admin user, replacing: * `localhost` with the IP or hostname of your InfluxDB OSS instance or one of your InfluxDB Enterprise data nodes @@ -77,7 +77,7 @@ A successful `CREATE USER` query returns a blank result: ### Step 4: Edit the InfluxDB source in Chronograf. -If you've already [connected your database to Chronograf](/chronograf/latest/introduction/getting-started/#3-connect-to-chronograf), update the connection configuration in Chronograf with your new username and password. +If you've already [connected your database to Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/#3-connect-to-chronograf), update the connection configuration in Chronograf with your new username and password. Edit existing InfluxDB database sources by navigating to the Chronograf configuration page and clicking on the name of the source. ## InfluxDB OSS User Management @@ -91,7 +91,7 @@ On the **Chronograf Admin** page: ![InfluxDB OSS user management](/img/chronograf/1-6-admin-usermanagement-oss.png) InfluxDB users are either admin users or non-admin users. -See InfluxDB's [authentication and authorization](/influxdb/latest/query_language/authentication_and_authorization/#user-types-and-privileges) documentation for more information about those user types. +See InfluxDB's [authentication and authorization](/{{< latest "influxdb" "v1" >}}/query_language/authentication_and_authorization/#user-types-and-privileges) documentation for more information about those user types. > ***Note:*** Note that Chronograf currently does not support assigning InfluxDB database `READ`or `WRITE` access to non-admin users. >This is a known issue. @@ -156,12 +156,12 @@ Assign permissions and roles to both admin and non-admin users. Permission to add or remove nodes from a cluster. **Relevant `influxd-ctl` arguments**: -[`add-data`](/enterprise_influxdb/latest/features/cluster-commands/#add-data), -[`add-meta`](/enterprise_influxdb/latest/features/cluster-commands/#add-meta), -[`join`](/enterprise_influxdb/latest/features/cluster-commands/#join), -[`remove-data`](/enterprise_influxdb/latest/features/cluster-commands/#remove-data), -[`remove-meta`](/enterprise_influxdb/latest/features/cluster-commands/#remove-meta), and -[`leave`](/enterprise_influxdb/latest/features/cluster-commands/#leave) +[`add-data`](/{{< latest "enterprise_influxdb" >}}/features/cluster-commands/#add-data), +[`add-meta`](/{{< latest "enterprise_influxdb" >}}/features/cluster-commands/#add-meta), +[`join`](/{{< latest "enterprise_influxdb" >}}/features/cluster-commands/#join), +[`remove-data`](/{{< latest "enterprise_influxdb" >}}/features/cluster-commands/#remove-data), +[`remove-meta`](/{{< latest "enterprise_influxdb" >}}/features/cluster-commands/#remove-meta), and +[`leave`](/{{< latest "enterprise_influxdb" >}}/features/cluster-commands/#leave) **Pages in Chronograf that require this permission**: NA @@ -169,18 +169,18 @@ Permission to add or remove nodes from a cluster. Permission to copy shards. **Relevant `influxd-ctl` arguments**: -[copy-shard](/enterprise_influxdb/latest/features/cluster-commands/#copy-shard) +[copy-shard](/{{< latest "enterprise_influxdb" >}}/features/cluster-commands/#copy-shard) **Pages in Chronograf that require this permission**: NA #### CreateDatabase -Permission to create databases, create [retention policies](/influxdb/latest/concepts/glossary/#retention-policy-rp), alter retention policies, and view retention policies. +Permission to create databases, create [retention policies](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#retention-policy-rp), alter retention policies, and view retention policies. **Relevant InfluxQL queries**: -[`CREATE DATABASE`](/influxdb/latest/query_language/database_management/#create-database), -[`CREATE RETENTION POLICY`](/influxdb/latest/query_language/database_management/#create-retention-policies-with-create-retention-policy), -[`ALTER RETENTION POLICY`](/influxdb/latest/query_language/database_management/#modify-retention-policies-with-alter-retention-policy), and -[`SHOW RETENTION POLICIES`](/influxdb/latest/query_language/schema_exploration/#show-retention-policies) +[`CREATE DATABASE`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#create-database), +[`CREATE RETENTION POLICY`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#create-retention-policies-with-create-retention-policy), +[`ALTER RETENTION POLICY`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#modify-retention-policies-with-alter-retention-policy), and +[`SHOW RETENTION POLICIES`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-retention-policies) **Pages in Chronograf that require this permission**: Dashboards, Data Explorer, and Databases on the Admin page @@ -188,25 +188,25 @@ Permission to create databases, create [retention policies](/influxdb/latest/con Permission to manage users and roles; create users, drop users, grant admin status to users, grant permissions to users, revoke admin status from users, revoke permissions from users, change user passwords, view user permissions, and view users and their admin status. **Relevant InfluxQL queries**: -[`CREATE USER`](/influxdb/latest/query_language/authentication_and_authorization/#user-management-commands), -[`DROP USER`](/influxdb/latest/query_language/authentication_and_authorization/#general-admin-and-non-admin-user-management), -[`GRANT ALL PRIVILEGES`](/influxdb/latest/query_language/authentication_and_authorization/#user-management-commands), -[`GRANT [READ,WRITE,ALL]`](/influxdb/latest/query_language/authentication_and_authorization/#non-admin-user-management), -[`REVOKE ALL PRIVILEGES`](/influxdb/latest/query_language/authentication_and_authorization/#user-management-commands), -[`REVOKE [READ,WRITE,ALL]`](/influxdb/latest/query_language/authentication_and_authorization/#non-admin-user-management), -[`SET PASSWORD`](/influxdb/latest/query_language/authentication_and_authorization/#general-admin-and-non-admin-user-management), -[`SHOW GRANTS`](/influxdb/latest/query_language/authentication_and_authorization/#non-admin-user-management), and -[`SHOW USERS`](/influxdb/latest/query_language/authentication_and_authorization/#user-management-commands) +[`CREATE USER`](/{{< latest "influxdb" "v1" >}}/query_language/authentication_and_authorization/#user-management-commands), +[`DROP USER`](/{{< latest "influxdb" "v1" >}}/query_language/authentication_and_authorization/#general-admin-and-non-admin-user-management), +[`GRANT ALL PRIVILEGES`](/{{< latest "influxdb" "v1" >}}/query_language/authentication_and_authorization/#user-management-commands), +[`GRANT [READ,WRITE,ALL]`](/{{< latest "influxdb" "v1" >}}/query_language/authentication_and_authorization/#non-admin-user-management), +[`REVOKE ALL PRIVILEGES`](/{{< latest "influxdb" "v1" >}}/query_language/authentication_and_authorization/#user-management-commands), +[`REVOKE [READ,WRITE,ALL]`](/{{< latest "influxdb" "v1" >}}/query_language/authentication_and_authorization/#non-admin-user-management), +[`SET PASSWORD`](/{{< latest "influxdb" "v1" >}}/query_language/authentication_and_authorization/#general-admin-and-non-admin-user-management), +[`SHOW GRANTS`](/{{< latest "influxdb" "v1" >}}/query_language/authentication_and_authorization/#non-admin-user-management), and +[`SHOW USERS`](/{{< latest "influxdb" "v1" >}}/query_language/authentication_and_authorization/#user-management-commands) **Pages in Chronograf that require this permission**: Data Explorer, Dashboards, Users and Roles on the Admin page #### DropData -Permission to drop data, in particular [series](/influxdb/latest/concepts/glossary/#series) and [measurements](/influxdb/latest/concepts/glossary/#measurement). +Permission to drop data, in particular [series](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#series) and [measurements](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#measurement). **Relevant InfluxQL queries**: -[`DROP SERIES`](/influxdb/latest/query_language/database_management/#drop-series-from-the-index-with-drop-series), -[`DELETE`](/influxdb/latest/query_language/database_management/#delete-series-with-delete), and -[`DROP MEASUREMENT`](/influxdb/latest/query_language/database_management/#delete-measurements-with-drop-measurement) +[`DROP SERIES`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#drop-series-from-the-index-with-drop-series), +[`DELETE`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#delete-series-with-delete), and +[`DROP MEASUREMENT`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#delete-measurements-with-drop-measurement) **Pages in Chronograf that require this permission**: NA @@ -214,8 +214,8 @@ Permission to drop data, in particular [series](/influxdb/latest/concepts/glossa Permission to drop databases and retention policies. **Relevant InfluxQL queries**: -[`DROP DATABASE`](/influxdb/latest/query_language/database_management/#delete-a-database-with-drop-database) and -[`DROP RETENTION POLICY`](/influxdb/latest/query_language/database_management/#delete-retention-policies-with-drop-retention-policy) +[`DROP DATABASE`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#delete-a-database-with-drop-database) and +[`DROP RETENTION POLICY`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#delete-retention-policies-with-drop-retention-policy) **Pages in Chronograf that require this permission**: Data Explorer, Dashboards, Databases on the Admin page @@ -231,12 +231,12 @@ Permission to access the configuration-related API calls for InfluxKapacitor Ent **Pages in Chronograf that require this permission**: NA #### ManageContinuousQuery -Permission to create, drop, and view [continuous queries](/influxdb/latest/concepts/glossary/#continuous-query-cq). +Permission to create, drop, and view [continuous queries](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#continuous-query-cq). **Relevant InfluxQL queries**: -[`CreateContinuousQueryStatement`](/influxdb/latest/query_language/continuous_queries/), +[`CreateContinuousQueryStatement`](/{{< latest "influxdb" "v1" >}}/query_language/continuous_queries/), [`DropContinuousQueryStatement`](), and -[`ShowContinuousQueriesStatement`](/influxdb/latest/query_language/continuous_queries/#list-cqs) +[`ShowContinuousQueriesStatement`](/{{< latest "influxdb" "v1" >}}/query_language/continuous_queries/#list-cqs) **Pages in Chronograf that require this permission**: Data Explorer, Dashboards @@ -244,28 +244,28 @@ Permission to create, drop, and view [continuous queries](/influxdb/latest/conce Permission to view and kill queries. **Relevant InfluxQL queries**: -[`SHOW QUERIES`](/influxdb/latest/troubleshooting/query_management/#list-currently-running-queries-with-show-queries) and -[`KILL QUERY`](/influxdb/latest/troubleshooting/query_management/#stop-currently-running-queries-with-kill-query) +[`SHOW QUERIES`](/{{< latest "influxdb" "v1" >}}/troubleshooting/query_management/#list-currently-running-queries-with-show-queries) and +[`KILL QUERY`](/{{< latest "influxdb" "v1" >}}/troubleshooting/query_management/#stop-currently-running-queries-with-kill-query) **Pages in Chronograf that require this permission**: Queries on the Admin page #### ManageShard -Permission to copy, delete, and view [shards](/influxdb/latest/concepts/glossary/#shard). +Permission to copy, delete, and view [shards](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#shard). **Relevant InfluxQL queries**: -[`DropShardStatement`](/influxdb/latest/query_language/database_management/#delete-a-shard-with-drop-shard), -[`ShowShardGroupsStatement`](/influxdb/latest/query_language/spec/#show-shard-groups), and -[`ShowShardsStatement`](/influxdb/latest/query_language/spec/#show-shards) +[`DropShardStatement`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#delete-a-shard-with-drop-shard), +[`ShowShardGroupsStatement`](/{{< latest "influxdb" "v1" >}}/query_language/spec/#show-shard-groups), and +[`ShowShardsStatement`](/{{< latest "influxdb" "v1" >}}/query_language/spec/#show-shards) **Pages in Chronograf that require this permission**: NA #### ManageSubscription -Permission to create, drop, and view [subscriptions](/influxdb/latest/concepts/glossary/#subscription). +Permission to create, drop, and view [subscriptions](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#subscription). **Relevant InfluxQL queries**: -[`CREATE SUBSCRIPTION`](/influxdb/latest/query_language/spec/#create-subscription), -[`DROP SUBSCRIPTION`](/influxdb/latest/query_language/spec/#drop-subscription), and -[`SHOW SUBSCRIPTIONS`](/influxdb/latest/query_language/spec/#show-subscriptions) +[`CREATE SUBSCRIPTION`](/{{< latest "influxdb" "v1" >}}/query_language/spec/#create-subscription), +[`DROP SUBSCRIPTION`](/{{< latest "influxdb" "v1" >}}/query_language/spec/#drop-subscription), and +[`SHOW SUBSCRIPTIONS`](/{{< latest "influxdb" "v1" >}}/query_language/spec/#show-subscriptions) **Pages in Chronograf that require this permission**: Alerting @@ -273,8 +273,8 @@ Permission to create, drop, and view [subscriptions](/influxdb/latest/concepts/g Permission to view cluster statistics and diagnostics. **Relevant InfluxQL queries**: -[`SHOW DIAGNOSTICS`](/influxdb/latest/troubleshooting/statistics/) and -[`SHOW STATS`](/influxdb/latest/troubleshooting/statistics/) +[`SHOW DIAGNOSTICS`](/{{< latest "influxdb" "v1" >}}/troubleshooting/statistics/) and +[`SHOW STATS`](/{{< latest "influxdb" "v1" >}}/troubleshooting/statistics/) **Pages in Chronograf that require this permission**: Data Explorer, Dashboards @@ -282,12 +282,12 @@ Permission to view cluster statistics and diagnostics. Permission to read data. **Relevant InfluxQL queries**: -[`SHOW FIELD KEYS`](/influxdb/latest/query_language/schema_exploration/#show-field-keys), -[`SHOW MEASUREMENTS`](/influxdb/latest/query_language/schema_exploration/#show-measurements), -[`SHOW SERIES`](/influxdb/latest/query_language/schema_exploration/#show-series), -[`SHOW TAG KEYS`](/influxdb/latest/query_language/schema_exploration/#show-tag-keys), -[`SHOW TAG VALUES`](/influxdb/latest/query_language/schema_exploration/#show-tag-values), and -[`SHOW RETENTION POLICIES`](/influxdb/latest/query_language/schema_exploration/#show-retention-policies) +[`SHOW FIELD KEYS`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-field-keys), +[`SHOW MEASUREMENTS`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-measurements), +[`SHOW SERIES`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-series), +[`SHOW TAG KEYS`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-tag-keys), +[`SHOW TAG VALUES`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-tag-values), and +[`SHOW RETENTION POLICIES`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-retention-policies) **Pages in Chronograf that require this permission**: Admin, Alerting, Dashboards, Data Explorer, Host List diff --git a/content/chronograf/v1.6/administration/managing-organizations.md b/content/chronograf/v1.6/administration/managing-organizations.md index 81e04fa7f..52c76ab81 100644 --- a/content/chronograf/v1.6/administration/managing-organizations.md +++ b/content/chronograf/v1.6/administration/managing-organizations.md @@ -22,7 +22,7 @@ menu: > ***Note:*** Support for organizations and distinct users with role-based access control is new in Chronograf 1.4. > -> For information about the new user roles and SuperAdmin status, see [Managing Chronograf users](/chronograf/latest/administration/managing-chronograf-users/). +> For information about the new user roles and SuperAdmin status, see [Managing Chronograf users](/{{< latest "chronograf" >}}/administration/managing-chronograf-users/). A Chronograf organization is a collection of Chronograf users who share common Chronograf-owned resources, including dashboards, InfluxDB connections, and Kapacitor connections. Organizations can be used to represent companies, functional units, projects, or teams. Chronograf users can be members of multiple organizations. @@ -67,8 +67,8 @@ You can configure existing and new organizations in the **Organizations** tab of See the following pages for more information about managing Chronograf users and security: -* [Managing Chronograf users](/chronograf/latest/administration/managing-chronograf-users/) -* [Managing security](/chronograf/latest/administration/managing-security/) +* [Managing Chronograf users](/{{< latest "chronograf" >}}/administration/managing-chronograf-users/) +* [Managing security](/{{< latest "chronograf" >}}/administration/managing-security/) ## Mapping organizations diff --git a/content/chronograf/v1.6/administration/transition-web-admin-interface.md b/content/chronograf/v1.6/administration/transition-web-admin-interface.md index 7294d37a9..043283212 100644 --- a/content/chronograf/v1.6/administration/transition-web-admin-interface.md +++ b/content/chronograf/v1.6/administration/transition-web-admin-interface.md @@ -8,7 +8,7 @@ aliases: - /chronograf/v1.6/guides/transition-web-admin-interface/ --- -Versions 1.3 and later of [InfluxDB](/influxdb/latest/) and [InfluxDB Enterprise](/enterprise/latest/) do not support the [web admin interface](/influxdb/latest/tools/web_admin/), the builtin user interface for writing and querying data in InfluxDB. +Versions 1.3 and later of [InfluxDB](/{{< latest "influxdb" "v1" >}}/) and [InfluxDB Enterprise](/enterprise/latest/) do not support the [web admin interface](/{{< latest "influxdb" "v1" >}}/tools/web_admin/), the builtin user interface for writing and querying data in InfluxDB. Chronograf replaces the web admin interface with improved tooling for querying data, writing data, and database management. The following sections describe the Chronograf features that relate to the web admin interface: @@ -23,7 +23,7 @@ The following sections describe the Chronograf features that relate to the web a ### Web admin interface In the web admin interface, users chose the target database in the top right corner and selected from a set of query templates in the `Query Templates` dropdown. -The templates included queries with no user-provided values (example: [`SHOW MEASUREMENTS`](/influxdb/latest/query_language/schema_exploration/#show-measurements)) and queries with user-provided values (example: [`SHOW TAG KEYS FROM ""`](/influxdb/latest/query_language/schema_exploration/#show-tag-keys)). +The templates included queries with no user-provided values (example: [`SHOW MEASUREMENTS`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-measurements)) and queries with user-provided values (example: [`SHOW TAG KEYS FROM ""`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-tag-keys)). ![WAI Query Templates](/img/chronograf/1-6-g-admin-webtemplates.png) @@ -39,7 +39,7 @@ Note that unlike the web admin interface, Chronograf does not have a database dr ### Web admin interface -To write data to InfluxDB, users selected the target database in the top right corner, clicked the `Write Data` icon, and entered their [line protocol](/influxdb/latest/concepts/glossary/#line-protocol) in the text input: +To write data to InfluxDB, users selected the target database in the top right corner, clicked the `Write Data` icon, and entered their [line protocol](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#line-protocol) in the text input: ![WAI Writing Data](/img/chronograf/1-6-g-admin-write.png) @@ -55,7 +55,7 @@ Next, enter your line protocol in the main text box and click the `Write` button ### Web admin interface -In the web admin interface, the `Query Template` dropdown was the only way to manage databases and [retention policies](/influxdb/latest/concepts/glossary/#retention-policy-rp) (RP): +In the web admin interface, the `Query Template` dropdown was the only way to manage databases and [retention policies](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#retention-policy-rp) (RP): ![WAI DBRP Management](/img/chronograf/1-6-g-admin-webdbrp.png) @@ -80,7 +80,7 @@ In the web admin interface, the `Query Template` dropdown was the only way to ma ### Chronograf In Chronograf, the `Admin` page includes a complete interface for user management. -The `Admin` page supports both InfluxDB OSS users and InfluxDB Enterprise users; see the [User Management](/chronograf/latest/administration/user-management/) page for more information. +The `Admin` page supports both InfluxDB OSS users and InfluxDB Enterprise users; see the [User Management](/{{< latest "chronograf" >}}/administration/user-management/) page for more information. The `Admin` page allows users to: * View, create, and delete users diff --git a/content/chronograf/v1.6/administration/upgrading.md b/content/chronograf/v1.6/administration/upgrading.md index 8e06c8615..522619336 100644 --- a/content/chronograf/v1.6/administration/upgrading.md +++ b/content/chronograf/v1.6/administration/upgrading.md @@ -24,4 +24,4 @@ Users can continue to use the deprecated product; documentation is available und For more information, please read the original [announcement blog](https://www.influxdata.com/announcing-the-new-chronograf-a-ui-for-the-tick-stack-and-a-complete-open-source-monitoring-solution/) by our CTO, Paul Dix. InfluxData recommends migrating to the open source Chronograf product. -See [Getting Started](/chronograf/latest/introduction/getting-started/) to get up and running! +See [Getting Started](/{{< latest "chronograf" >}}/introduction/getting-started/) to get up and running! diff --git a/content/chronograf/v1.6/guides/_index.md b/content/chronograf/v1.6/guides/_index.md index b1032ed43..5abc7167a 100644 --- a/content/chronograf/v1.6/guides/_index.md +++ b/content/chronograf/v1.6/guides/_index.md @@ -17,7 +17,7 @@ Pre-created dashboards are available when the required Telegraf input plugins ar Using the TICKscript editor in Chronograf to create, test, and debug Kapacitor TICKscripts. -## [Creating dashboards](/chronograf/latest/guides/create-a-dashboard/) +## [Creating dashboards](/{{< latest "chronograf" >}}/guides/create-a-dashboard/) Chronograf offers a complete dashboard solution for visualizing your data and monitoring your infrastructure. Learn how to create customized dashboards in Chronograf. diff --git a/content/chronograf/v1.6/guides/advanced-kapacitor.md b/content/chronograf/v1.6/guides/advanced-kapacitor.md index 2fe8aa6af..cd3d03bc6 100644 --- a/content/chronograf/v1.6/guides/advanced-kapacitor.md +++ b/content/chronograf/v1.6/guides/advanced-kapacitor.md @@ -13,16 +13,16 @@ menu: * [TICKscript management](#tickscript-management) -Chronograf provides a user interface for [Kapacitor](/kapacitor/latest/), InfluxData's processing framework for creating alerts, running ETL jobs, and detecting anomalies in your data. +Chronograf provides a user interface for [Kapacitor](/{{< latest "kapacitor" >}}/), InfluxData's processing framework for creating alerts, running ETL jobs, and detecting anomalies in your data. This guide offers insights into how Kapacitor interacts with Chronograf and introduces advanced Kapacitor usage within Chronograf. ## Alert history management Chronograf stores the information on the Alert History page as time series data in InfluxDB. -It stores it in the `chronograf` database and in the `alerts` [measurement](/influxdb/latest/concepts/glossary/#measurement). -By default, this data is subject to an infinite [retention policy](/influxdb/latest/concepts/glossary/#retention-policy-rp) (RP), that is, InfluxDB stores them forever. -Users who expect to have a large number of alerts and users who do not want to store their alert history forever may want to shorten the [duration](/influxdb/latest/concepts/glossary/#duration) of that retention policy. +It stores it in the `chronograf` database and in the `alerts` [measurement](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#measurement). +By default, this data is subject to an infinite [retention policy](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#retention-policy-rp) (RP), that is, InfluxDB stores them forever. +Users who expect to have a large number of alerts and users who do not want to store their alert history forever may want to shorten the [duration](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#duration) of that retention policy. ### Modifying the retention policy in Chronograf @@ -36,7 +36,7 @@ In the Databases tab: #### Step 2: Enter a different duration The minimum allowable duration is one hour (`1h`) and the maximum is infinite (`INF`). -See the InfluxDB documentation for the list of [acceptable duration units](/influxdb/latest/query_language/spec/#duration-units). +See the InfluxDB documentation for the list of [acceptable duration units](/{{< latest "influxdb" "v1" >}}/query_language/spec/#duration-units). #### Step 3: Click the green check mark to save your changes @@ -56,7 +56,7 @@ The fourth alert, which occurred on the same day at 16:58:50, is outside the pre Chronograf creates Kapacitor tasks using the information that you provide on the Rule Configuration page. It uses that information to communicate with Kapacitor and populate Chronograf alert pages. -Pre-existing tasks, or [TICKscripts](/kapacitor/latest/tick/), that you created and enabled on your Kapacitor instance without using Chronograf, have limited functionality in the user interface. +Pre-existing tasks, or [TICKscripts](/{{< latest "kapacitor" >}}/tick/), that you created and enabled on your Kapacitor instance without using Chronograf, have limited functionality in the user interface. In Chronograf, you can: diff --git a/content/chronograf/v1.6/guides/analyzing-logs.md b/content/chronograf/v1.6/guides/analyzing-logs.md index 8cb14dfbe..b3474cf57 100644 --- a/content/chronograf/v1.6/guides/analyzing-logs.md +++ b/content/chronograf/v1.6/guides/analyzing-logs.md @@ -11,7 +11,7 @@ Chronograf gives you the ability to view, search, filter, visualize, and analyze This helps to recognize and diagnose patterns, then quickly dive into logged events that lead up to events. ## Logging setup -Logs data is a first class citizen in InfluxDB and is populated using available log-related [Telegraf input plugins](/telegraf/latest/plugins/inputs/): +Logs data is a first class citizen in InfluxDB and is populated using available log-related [Telegraf input plugins](/{{< latest "telegraf" >}}/plugins/inputs/): [syslog](https://github.com/influxdata/telegraf/tree/release-1.7/plugins/inputs/syslog) diff --git a/content/chronograf/v1.6/guides/configuring-alert-endpoints.md b/content/chronograf/v1.6/guides/configuring-alert-endpoints.md index f32599ba5..efae94b5a 100644 --- a/content/chronograf/v1.6/guides/configuring-alert-endpoints.md +++ b/content/chronograf/v1.6/guides/configuring-alert-endpoints.md @@ -17,7 +17,7 @@ This guide offers step-by-step instructions for configuring Chronograf alert end ## Kapacitor event handlers supported in Chronograf -Chronograf integrates with [Kapacitor](/kapacitor/latest/), InfluxData's data processing platform, to send alert messages to event handlers. +Chronograf integrates with [Kapacitor](/{{< latest "kapacitor" >}}/), InfluxData's data processing platform, to send alert messages to event handlers. Chronograf supports the following event handlers: * Alerta @@ -38,7 +38,7 @@ Chronograf supports the following event handlers: * TCP * VictorOps -To configure a Kapacitor event handler in Chronograf, [install Kapacitor](/chronograf/latest/introduction/getting-started/#kapacitor-setup) and [connect it to Chronograf](/chronograf/latest/introduction/getting-started/#4-connect-chronograf-to-kapacitor). +To configure a Kapacitor event handler in Chronograf, [install Kapacitor](/{{< latest "chronograf" >}}/introduction/getting-started/#kapacitor-setup) and [connect it to Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/#4-connect-chronograf-to-kapacitor). The **Configure Kapacitor** page includes the event handler configuration options. @@ -46,10 +46,10 @@ The **Configure Kapacitor** page includes the event handler configuration option Alert endpoint configurations appear on the Chronograf Configure Kapacitor page. You must have a connected Kapacitor instance to access the configurations. -For more information, see [Kapacitor installation instructions](/chronograf/latest/introduction/getting-started/#kapacitor-setup) and how to [connect a Kapacitor instance](/chronograf/latest/introduction/getting-started/#4-connect-chronograf-to-kapacitor) to Chronograf. +For more information, see [Kapacitor installation instructions](/{{< latest "chronograf" >}}/introduction/getting-started/#kapacitor-setup) and how to [connect a Kapacitor instance](/{{< latest "chronograf" >}}/introduction/getting-started/#4-connect-chronograf-to-kapacitor) to Chronograf. Note that the configuration options in the **Configure alert endpoints** section are not all-inclusive. -Some event handlers allow users to customize event handler configurations per [alert rule](/chronograf/latest/guides/create-a-kapacitor-alert/). +Some event handlers allow users to customize event handler configurations per [alert rule](/{{< latest "chronograf" >}}/guides/create-a-kapacitor-alert/). For example, Chronograf's Slack integration allows users to specify a default channel in the **Configure alert endpoints** section and a different channel for individual alert rules. ### HipChat @@ -113,7 +113,7 @@ Your token appears in the table just above the **Create new token** section: 3. Click **Save Changes** to save the configuration settings. 4. Click **Send Test Alert** to verify the configuration. -See [Kafka event handler (Kapacitor)](/kapacitor/latest/event_handlers/kafka/) in the Kapacitor documentation for details about enabling OpsGenie services using TICKscripts. +See [Kafka event handler (Kapacitor)](/{{< latest "kapacitor" >}}/event_handlers/kafka/) in the Kapacitor documentation for details about enabling OpsGenie services using TICKscripts. ### OpsGenie @@ -140,9 +140,9 @@ Send an incident alert to OpsGenie teams and recipients using the Chronograf ale See [Alert API](https://docs.opsgenie.com/docs/alert-api) in the OpsGenie documentation for details on the OpsGenie Alert API -See [OpsGenie V2 event handler](/kapacitor/latest/event_handlers/opsgenie/v2/) in the Kapacitor documentation for details about the OpsGenie V2 event handler. +See [OpsGenie V2 event handler](/{{< latest "kapacitor" >}}/event_handlers/opsgenie/v2/) in the Kapacitor documentation for details about the OpsGenie V2 event handler. -See the [AlertNode (Kapacitor TICKscript node) - OpsGenie v2](/kapacitor/latest/nodes/alert_node/#opsgenie-v2) in the Kapacitor documentation for details about enabling OpsGenie services using TICKscripts. +See the [AlertNode (Kapacitor TICKscript node) - OpsGenie v2](/{{< latest "kapacitor" >}}/nodes/alert_node/#opsgenie-v2) in the Kapacitor documentation for details about enabling OpsGenie services using TICKscripts. ### PagerDuty @@ -166,7 +166,7 @@ Send an alerts about recognized events to PagerDuty using the Chronograf PagerDu See the [PagerDuty Events API V2 Overview](https://v2.developer.pagerduty.com/docs/events-api-v2) for details on the PagerDuty Events API and recognized event types (`trigger`, `acknowledge`, and `resolve`). -See [AlertNode (Kapacitor TICKscript node) - PagerDuty v2](/kapacitor/latest/nodes/alert_node/#pagerduty-v2) in the Kapacitor documentation for details about enabling a new "Generic API" service using TICKscripts. +See [AlertNode (Kapacitor TICKscript node) - PagerDuty v2](/{{< latest "kapacitor" >}}/nodes/alert_node/#pagerduty-v2) in the Kapacitor documentation for details about enabling a new "Generic API" service using TICKscripts. ### Slack diff --git a/content/chronograf/v1.6/guides/create-a-dashboard.md b/content/chronograf/v1.6/guides/create-a-dashboard.md index 348200137..4e766aa47 100644 --- a/content/chronograf/v1.6/guides/create-a-dashboard.md +++ b/content/chronograf/v1.6/guides/create-a-dashboard.md @@ -9,7 +9,7 @@ menu: --- Chronograf offers a complete dashboard solution for visualizing your data and monitoring your infrastructure. -Use Chronograf's [pre-created dashboards](/chronograf/latest/guides/using-precreated-dashboards) or create custom dashboards to meet your requirements. +Use Chronograf's [pre-created dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards) or create custom dashboards to meet your requirements. This guide shows you how to create custom Chronograf dashboards. By the end of this guide, you'll be aware of the tools available to you for creating dashboards similar to this example: @@ -20,7 +20,7 @@ By the end of this guide, you'll be aware of the tools available to you for crea To perform the tasks in this guide, you must have a working Chronograf instance that is connected to an InfluxDB source. Data is accessed using the Telegraf [system ](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/system) input plugins. -For more information, see [Configuring Chronograf](/chronograf/latest/administration/configuration). +For more information, see [Configuring Chronograf](/{{< latest "chronograf" >}}/administration/configuration). ## Build a Dashboard @@ -40,13 +40,13 @@ to open the cell editor mode. ### Step 3: Create your query -Click the **Add a Query** button to create an [InfluxQL](/influxdb/latest/query_language/) query. +Click the **Add a Query** button to create an [InfluxQL](/{{< latest "influxdb" "v1" >}}/query_language/) query. In query editor mode, use the builder to select from your existing data and allow Chronograf to format the query for you. Alternatively, manually enter and edit a query. Chronograf allows you to move seamlessly between using the builder and manually editing the query; when possible, the interface automatically populates the builder with the information from your raw query. For our example, the query builder is used to generate a query that shows the average idle CPU usage grouped by host (in this case, there are three hosts). -By default, Chronograf applies the [`MEAN()` function](/influxdb/latest/query_language/functions/#mean) to the data, groups averages into auto-generated time intervals (`:interval:`), and shows data for the past hour (`:dashboardTime:`). +By default, Chronograf applies the [`MEAN()` function](/{{< latest "influxdb" "v1" >}}/query_language/functions/#mean) to the data, groups averages into auto-generated time intervals (`:interval:`), and shows data for the past hour (`:dashboardTime:`). Those defaults are configurable using the query builder or by manually editing the query. In addition, the time range (`:dashboardTime:`) is [configurable on the dashboard](#step-6-configure-your-dashboard). @@ -55,7 +55,7 @@ In addition, the time range (`:dashboardTime:`) is [configurable on the dashboar ### Step 4: Choose your visualization type -Chronograf supports many different [visualization types](/chronograf/latest/guides/visualization-types/). To choose a visualization type, click **Visualization** and select **Step-Plot Graph**. +Chronograf supports many different [visualization types](/{{< latest "chronograf" >}}/guides/visualization-types/). To choose a visualization type, click **Visualization** and select **Step-Plot Graph**. ![Visualization type](/img/chronograf/1-6-g-dashboard-visualization.png) @@ -77,7 +77,7 @@ Click **Save** (the green checkmark icon) to save your cell. * **Reset** your cell by double-clicking your mouse in the cell window > Note: -These tips only apply to the line, stacked, step-plot, and line+stat [visualization types](/chronograf/latest/troubleshooting/frequently-asked-questions/#what-visualization-types-does-chronograf-support). +These tips only apply to the line, stacked, step-plot, and line+stat [visualization types](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#what-visualization-types-does-chronograf-support). #### Configure dashboard-wide settings: * You can change the dashboard's *auto-refresh interval* at the top of the page - the default interval selected is **Every 15 seconds**. @@ -93,4 +93,4 @@ To exit full screen mode, press the Esc key. ### Template variables Dashboards support template variables. -See the [Dashboard Template Variables](/chronograf/latest/guides/dashboard-template-variables/) guide for more information. +See the [Dashboard Template Variables](/{{< latest "chronograf" >}}/guides/dashboard-template-variables/) guide for more information. diff --git a/content/chronograf/v1.6/guides/create-alert-rules.md b/content/chronograf/v1.6/guides/create-alert-rules.md index 16107b21b..0b773cf0e 100644 --- a/content/chronograf/v1.6/guides/create-alert-rules.md +++ b/content/chronograf/v1.6/guides/create-alert-rules.md @@ -11,9 +11,9 @@ menu: --- -Chronograf provides a user interface for [Kapacitor](/kapacitor/latest/), InfluxData's processing framework for creating alerts, ETL jobs (running extract, transform, load), and detecting anomalies in your data. +Chronograf provides a user interface for [Kapacitor](/{{< latest "kapacitor" >}}/), InfluxData's processing framework for creating alerts, ETL jobs (running extract, transform, load), and detecting anomalies in your data. Chronograf alert rules correspond to Kapacitor tasks that trigger alerts whenever certain conditions are met. -Behind the scenes, these tasks are stored as [TICKscripts](/kapacitor/latest/tick/) that can be edited manually or through Chronograf. +Behind the scenes, these tasks are stored as [TICKscripts](/{{< latest "kapacitor" >}}/tick/) that can be edited manually or through Chronograf. Common alerting use cases that can be managed using Chronograf include: * Thresholds with static ceilings, floors, and ranges. @@ -26,13 +26,13 @@ This guide walks through creating a Chronograf alert rule that sends an alert me ## Requirements -[Getting started with Chronograf](/chronograf/latest/introduction/getting-started/) offers step-by-step instructions for each of the following requirements: +[Getting started with Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/) offers step-by-step instructions for each of the following requirements: * Downloaded and install the entire TICKstack (Telegraf, InfluxDB, Chronograf, and Kapacitor). * Configure Telegraf to collect data using the InfluxDB [system statistics](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/system) input plugin and write data to your InfluxDB instance. -* [Create a Kapacitor connection in Chronograf](/chronograf/latest/introduction/getting-started/#4-connect-chronograf-to-kapacitor). -* Slack is available and configured as an [event handler](/chronograf/latest/troubleshooting/frequently-asked-questions/#what-kapacitor-event-handlers-are-supported-in-chronograf) in Chronograf. -See the [Configuring Kapacitor Event Handlers](/chronograf/latest/guides/configuring-alert-endpoints/) guide for detailed configuration instructions. +* [Create a Kapacitor connection in Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/#4-connect-chronograf-to-kapacitor). +* Slack is available and configured as an [event handler](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#what-kapacitor-event-handlers-are-supported-in-chronograf) in Chronograf. +See the [Configuring Kapacitor Event Handlers](/{{< latest "chronograf" >}}/guides/configuring-alert-endpoints/) guide for detailed configuration instructions. ## Configuring Chronograf alert rules @@ -70,7 +70,7 @@ For this example, select the **Threshold** alert type. Choose the time series data you want the Chronograf alert rule to use. Navigate through databases, measurements, fields, and tags to select the relevant data. -In this example, select the `telegraf` [database](/influxdb/latest/concepts/glossary/#database), the `autogen` [retention policy](/influxdb/latest/concepts/glossary/#retention-policy-rp), the `cpu` [measurement](/influxdb/latest/concepts/glossary/#measurement), and the `usage_idle` [field](/influxdb/latest/concepts/glossary/#field). +In this example, select the `telegraf` [database](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#database), the `autogen` [retention policy](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#retention-policy-rp), the `cpu` [measurement](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#measurement), and the `usage_idle` [field](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#field). ![Select your data](/img/chronograf/1-6-alerts-time-series.png) @@ -113,7 +113,7 @@ In this example, use the alert message, `Your idle CPU usage is {{.Level}} at {{ ![Specify event handler and alert message](/img/chronograf/1-6-alerts-message.png) -*View the Kapacitor documentation for more information about [message template data](/kapacitor/latest/nodes/alert_node/#message).* +*View the Kapacitor documentation for more information about [message template data](/{{< latest "kapacitor" >}}/nodes/alert_node/#message).* ### Step 7: Save the alert rule diff --git a/content/chronograf/v1.6/guides/dashboard-template-variables.md b/content/chronograf/v1.6/guides/dashboard-template-variables.md index 8305d2d9b..a78f5a397 100644 --- a/content/chronograf/v1.6/guides/dashboard-template-variables.md +++ b/content/chronograf/v1.6/guides/dashboard-template-variables.md @@ -115,7 +115,7 @@ Chronograf supports the following template variable types: [Text](#text) ### Databases -Database template variables allow you to select from multiple target [databases](/influxdb/latest/concepts/glossary/#database). +Database template variables allow you to select from multiple target [databases](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#database). _**Database meta query**_ Database template variables use the following meta query to return an array of all databases in your InfluxDB instance. @@ -133,7 +133,7 @@ SELECT "purchases" FROM :databaseVar:."autogen"."customers" Database template variables are good when visualizing multiple databases with similar or identical data structures. They allow you to quickly switch between visualizations for each of your databases. ### Measurements -Vary the target [measurement](/influxdb/latest/concepts/glossary/#measurement). +Vary the target [measurement](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#measurement). _**Measurement meta query**_ Measurement template variables use the following meta query to return an array of all measurements in a given database. @@ -152,7 +152,7 @@ Measurement template variables allow you to quickly switch between measurements ### Field Keys -Vary the target [field key](/influxdb/latest/concepts/glossary/#field-key). +Vary the target [field key](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#field-key). _**Field key meta query**_ Field key template variables use the following meta query to return an array of all field keys in a given measurement from a given database. @@ -171,7 +171,7 @@ Field key template variables are great if you want to quickly switch between fie ### Tag Keys -Vary the target [tag key](/influxdb/latest/concepts/glossary/#tag-key). +Vary the target [tag key](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-key). _**Tag key meta query**_ Tag key template variables use the following meta query to return an array of all tag keys in a given measurement from a given database. @@ -190,7 +190,7 @@ Tag key template variables are great if you want to quickly switch between tag k ### Tag Values -Vary the target [tag value](/influxdb/latest/concepts/glossary/#tag-value). +Vary the target [tag value](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-value). _**Tag value meta query**_ Tag value template variables use the following meta query to return an array of all values associated with a given tag key in a specified measurement and database. @@ -222,7 +222,7 @@ value3 value4 ``` -> Since string field values [require single quotes in InfluxQL](/influxdb/latest/troubleshooting/frequently-asked-questions/#when-should-i-single-quote-and-when-should-i-double-quote-in-queries), string values should be wrapped in single quotes. +> Since string field values [require single quotes in InfluxQL](/{{< latest "influxdb" "v1" >}}/troubleshooting/frequently-asked-questions/#when-should-i-single-quote-and-when-should-i-double-quote-in-queries), string values should be wrapped in single quotes. >```csv 'string1','string2','string3','string4' @@ -253,7 +253,7 @@ key4,value4 Map variable dropdown -> If values are meant to be used as string field values, wrap them in single quote ([required by InfluxQL](/influxdb/latest/troubleshooting/frequently-asked-questions/#when-should-i-single-quote-and-when-should-i-double-quote-in-queries)). This only pertains to values. String keys do not matter. +> If values are meant to be used as string field values, wrap them in single quote ([required by InfluxQL](/{{< latest "influxdb" "v1" >}}/troubleshooting/frequently-asked-questions/#when-should-i-single-quote-and-when-should-i-double-quote-in-queries)). This only pertains to values. String keys do not matter. >```csv key1,'value1' diff --git a/content/chronograf/v1.6/guides/live_leaderboard.md b/content/chronograf/v1.6/guides/live_leaderboard.md index 0a7500d8f..d5b31e098 100644 --- a/content/chronograf/v1.6/guides/live_leaderboard.md +++ b/content/chronograf/v1.6/guides/live_leaderboard.md @@ -40,7 +40,7 @@ Add the following settings the `[[udp]]` secton in your Kapacitor configuration retention-policy = "autogen" ``` -Using this configuration, Kapacitor will listen on port `9100` for UDP packets in [Line Protocol](/influxdb/latest/write_protocols/line_protocol_tutorial/) format. +Using this configuration, Kapacitor will listen on port `9100` for UDP packets in [Line Protocol](/{{< latest "influxdb" "v1" >}}/write_protocols/line_protocol_tutorial/) format. Incoming data will be scoped to be in the `game.autogen` database and retention policy. Restart Kapacitor so that the UDP listener service starts. diff --git a/content/chronograf/v1.6/guides/monitoring-influxenterprise-clusters.md b/content/chronograf/v1.6/guides/monitoring-influxenterprise-clusters.md index 3688da390..42f0e8c04 100644 --- a/content/chronograf/v1.6/guides/monitoring-influxenterprise-clusters.md +++ b/content/chronograf/v1.6/guides/monitoring-influxenterprise-clusters.md @@ -10,20 +10,20 @@ menu: --- -[InfluxDB Enterprise](/enterprise_influxdb/latest/) offers high availability and a highly scalable clustering solution for your time series data needs. +[InfluxDB Enterprise](/{{< latest "enterprise_influxdb" >}}/) offers high availability and a highly scalable clustering solution for your time series data needs. Use Chronograf to assess your cluster's health and to monitor the infrastructure behind your project. -This guide offers step-by-step instructions for using Chronograf, [InfluxDB](/influxdb/latest/), and [Telegraf](/telegraf/latest/) to monitor data nodes in your InfluxDB Enterprise cluster. +This guide offers step-by-step instructions for using Chronograf, [InfluxDB](/{{< latest "influxdb" "v1" >}}/), and [Telegraf](/{{< latest "telegraf" >}}/) to monitor data nodes in your InfluxDB Enterprise cluster. ## Requirements You have a fully-functioning InfluxDB Enterprise cluster with authentication enabled. See the InfluxDB Enterprise documentation for -[detailed setup instructions](/enterprise_influxdb/latest/production_installation/). +[detailed setup instructions](/{{< latest "enterprise_influxdb" >}}/production_installation/). This guide uses an InfluxData Enterprise cluster with three meta nodes and three data nodes; the steps are also applicable to other cluster configurations. InfluxData recommends using a separate server to store your monitoring data. -It is possible to store the monitoring data in your cluster and [connect the cluster to Chronograf](/chronograf/latest/troubleshooting/frequently-asked-questions/#how-do-i-connect-chronograf-to-an-influxenterprise-cluster), but, in general, your monitoring data should live on a separate server. +It is possible to store the monitoring data in your cluster and [connect the cluster to Chronograf](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#how-do-i-connect-chronograf-to-an-influxenterprise-cluster), but, in general, your monitoring data should live on a separate server. You're working on an Ubuntu installation. Chronograf and the other components of the TICK stack are supported on several operating systems and hardware architectures. Check out the [downloads page](https://portal.influxdata.com/downloads) for links to the binaries of your choice. @@ -35,11 +35,11 @@ Before we begin, here's an overview of the final monitoring setup: ![Architecture diagram](/img/chronograf/1-6-cluster-diagram.png) The diagram above shows an InfluxDB Enterprise cluster that consists of three meta nodes (M) and three data nodes (D). -Each data node has its own [Telegraf](/telegraf/latest/) instance (T). +Each data node has its own [Telegraf](/{{< latest "telegraf" >}}/) instance (T). Each Telegraf instance is configured to collect node CPU, disk, and memory data using the Telegraf [system stats](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/system) input plugin. -The Telegraf instances are also configured to send those data to a single [InfluxDB OSS](/influxdb/latest/) instance that lives on a separate server. -When Telegraf sends data to InfluxDB, it automatically [tags](/influxdb/latest/concepts/glossary/#tag) the data with the hostname of the relevant data node. +The Telegraf instances are also configured to send those data to a single [InfluxDB OSS](/{{< latest "influxdb" "v1" >}}/) instance that lives on a separate server. +When Telegraf sends data to InfluxDB, it automatically [tags](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag) the data with the hostname of the relevant data node. The InfluxDB OSS instance that stores the Telegraf data is connected to Chronograf. Chronograf uses the hostnames in the Telegraf data to populate the Host List page and provide other hostname-specific information in the user interface. @@ -54,7 +54,7 @@ InfluxDB can be downloaded from the [InfluxData downloads page](https://portal.i #### Step 2: Enable authentication -For security purposes, enable authentication in the InfluxDB [configuration file (influxdb.conf)](/influxdb/latest/administration/config/), which is located in `/etc/influxdb/influxdb.conf`. +For security purposes, enable authentication in the InfluxDB [configuration file (influxdb.conf)](/{{< latest "influxdb" "v1" >}}/administration/config/), which is located in `/etc/influxdb/influxdb.conf`. In the `[http]` section of the configuration file, uncomment the `auth-enabled` option and set it to `true`: @@ -80,7 +80,7 @@ Next, start the InfluxDB process: #### Step 4: Create an admin user -Create an [admin user](/influxdb/latest/query_language/authentication_and_authorization/#user-types-and-privileges) on your InfluxDB instance. +Create an [admin user](/{{< latest "influxdb" "v1" >}}/query_language/authentication_and_authorization/#user-types-and-privileges) on your InfluxDB instance. Because you enabled authentication, you must perform this step before moving on to the next section. Run the command below to create an admin user, replacing `chronothan` and `supersecret` with your own username and password. Note that the password requires single quotes. @@ -178,7 +178,7 @@ Replace the `chronothan` and `supersecret` values with your actual username and ``` The expected output is similar to the JSON in the codeblock below. -In this case, the `telegraf` database has three different [tag values](/influxdb/latest/concepts/glossary/#tag-value) for the `host` [tag key](/influxdb/latest/concepts/glossary/#tag-key): `data-node-01`, `data-node-02`, and `data-node-03`. +In this case, the `telegraf` database has three different [tag values](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-value) for the `host` [tag key](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-key): `data-node-01`, `data-node-02`, and `data-node-03`. Those values match the hostnames of the three data nodes in the cluster; this means Telegraf is successfully writing monitoring data from those hosts to the InfluxDB OSS instance! ``` { @@ -258,6 +258,6 @@ In the image below, the Chronograf query editor is used to visualize the idle CP ![Data Explorer](/img/chronograf/1-6-cluster-de.png) Create more customized graphs and save them to a dashboard on the Dashboard page in Chronograf. -See the [Creating Chronograf dashboards](/chronograf/latest/guides/create-a-dashboard/) guide for more information. +See the [Creating Chronograf dashboards](/{{< latest "chronograf" >}}/guides/create-a-dashboard/) guide for more information. That's it! You've successfully configured Telegraf to collect and write data, InfluxDB to store those data, and Chonograf to use those data for monitoring and visualization purposes. diff --git a/content/chronograf/v1.6/guides/using-precreated-dashboards.md b/content/chronograf/v1.6/guides/using-precreated-dashboards.md index b4868639c..f8bb28236 100644 --- a/content/chronograf/v1.6/guides/using-precreated-dashboards.md +++ b/content/chronograf/v1.6/guides/using-precreated-dashboards.md @@ -11,7 +11,7 @@ menu: ## Overview -Pre-created dashboards are delivered with Chronograf and are available depending on which Telegraf input plugins you have enabled. These dashboards include cells with data visualizations for metrics that are relevant to data sources you are likely to be using. The JSON files that are delivered include headings, queries, labels, and other information that can also be useful for helping you get started in [creating custom dashboards](/chronograf/latest/guides/create-a-dashboard/). +Pre-created dashboards are delivered with Chronograf and are available depending on which Telegraf input plugins you have enabled. These dashboards include cells with data visualizations for metrics that are relevant to data sources you are likely to be using. The JSON files that are delivered include headings, queries, labels, and other information that can also be useful for helping you get started in [creating custom dashboards](/{{< latest "chronograf" >}}/guides/create-a-dashboard/). > Note that these pre-created dashboards do not appear in the Dashboards tab, which only include custom dashboards that your organization has created. @@ -33,7 +33,7 @@ Pre-created dashboards are delivered in Chronograf installations and are ready t The pre-created dashboards available for use with Chronograf are listed below as Apps and appear in the Apps listing for hosts in the Host List page. The listings for apps (pre-created dashboards) on this page include information about the required Telegraf input plugins, JSON files included in the apps, and listings of the cell titles that are included in each of the JSON files. -The JSON files for the precreated dashboards are delivered on installation in the `/usr/share/chronograf/canned` directory. Information about the configuration option `--canned-path` can be found in the [Chronograf configuration options](/chronograf/latest/administration/config-options/#) page. +The JSON files for the precreated dashboards are delivered on installation in the `/usr/share/chronograf/canned` directory. Information about the configuration option `--canned-path` can be found in the [Chronograf configuration options](/{{< latest "chronograf" >}}/administration/config-options/#) page. You can enable and disable applications in your [Telegraf configuration file](https://github.com/influxdata/telegraf/blob/master/etc/telegraf.conf). See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/docs/CONFIGURATION.md) for details. diff --git a/content/chronograf/v1.6/guides/visualization-types.md b/content/chronograf/v1.6/guides/visualization-types.md index d86f614b0..f38e02e85 100644 --- a/content/chronograf/v1.6/guides/visualization-types.md +++ b/content/chronograf/v1.6/guides/visualization-types.md @@ -179,10 +179,10 @@ The **Single Stat** view displays the most recent value of the specified time se ![Single Stat view](/img/chronograf/1-6-viz-single-stat-selector.png) -If a cell's query includes a [`GROUP BY` tag](/influxdb/latest/query_language/data_exploration/#group-by-tags) clause, Chronograf sorts the different [series](/influxdb/latest/concepts/glossary/#series) lexicographically and shows the most recent [field value](/influxdb/latest/concepts/glossary/#field-value) associated with the first series. -For example, if a query groups by the `name` [tag key](/influxdb/latest/concepts/glossary/#tag-key) and `name` has two [tag values](/influxdb/latest/concepts/glossary/#tag-value) (`chronelda` and `chronz`), Chronograf shows the most recent field value associated with the `chronelda` series. +If a cell's query includes a [`GROUP BY` tag](/{{< latest "influxdb" "v1" >}}/query_language/data_exploration/#group-by-tags) clause, Chronograf sorts the different [series](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#series) lexicographically and shows the most recent [field value](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#field-value) associated with the first series. +For example, if a query groups by the `name` [tag key](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-key) and `name` has two [tag values](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-value) (`chronelda` and `chronz`), Chronograf shows the most recent field value associated with the `chronelda` series. -If a cell's query includes more than one [field key](/influxdb/latest/concepts/glossary/#field-key) in the [`SELECT` clause](/influxdb/latest/query_language/data_exploration/#select-clause), Chronograf returns the most recent field value associated with the first field key in the `SELECT` clause. +If a cell's query includes more than one [field key](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#field-key) in the [`SELECT` clause](/{{< latest "influxdb" "v1" >}}/query_language/data_exploration/#select-clause), Chronograf returns the most recent field value associated with the first field key in the `SELECT` clause. For example, if a query's `SELECT` clause is `SELECT "chronogiraffe","chronelda"`, Chronograf shows the most recent field value associated with the `chronogiraffe` field key. #### Single Stat Controls diff --git a/content/chronograf/v1.6/introduction/_index.md b/content/chronograf/v1.6/introduction/_index.md index f02ad7c36..3028b85b3 100644 --- a/content/chronograf/v1.6/introduction/_index.md +++ b/content/chronograf/v1.6/introduction/_index.md @@ -15,11 +15,11 @@ Follow the links below to get acquainted with Chronograf: Chronograf is supported on several operating systems and hardware architectures. See the [InfluxData downloads page](https://portal.influxdata.com/downloads) page for to the available binaries. -## [Installing Chronograf](/chronograf/latest/introduction/installation/) +## [Installing Chronograf](/{{< latest "chronograf" >}}/introduction/installation/) -[Installing Chronograf](/chronograf/latest/introduction/installation/) lists the requirements for installing, starting, and configuring Chronograf. +[Installing Chronograf](/{{< latest "chronograf" >}}/introduction/installation/) lists the requirements for installing, starting, and configuring Chronograf. ## Getting Started -[Getting started with Chronograf](/chronograf/latest/introduction/getting-started/) gets you up and running with Chronograf with as little configuration and code as possible. +[Getting started with Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/) gets you up and running with Chronograf with as little configuration and code as possible. By the end of the guide, you will have downloaded, installed, and configured all four packages of the TICK stack ([Telegraf](https://github.com/influxdata/telegraf), [InfluxDB](https://github.com/influxdata/influxdb), Chronograf, and [Kapacitor](https://github.com/influxdata/kapacitor)), and you will be all set to monitor your infrastructure. diff --git a/content/chronograf/v1.6/introduction/getting-started.md b/content/chronograf/v1.6/introduction/getting-started.md index af072ff53..e30dec09a 100644 --- a/content/chronograf/v1.6/introduction/getting-started.md +++ b/content/chronograf/v1.6/introduction/getting-started.md @@ -1,7 +1,7 @@ --- title: Getting started with Chronograf aliases: - - /chronograf/latest/introduction/getting-started/ + - /{{< latest "chronograf" >}}/introduction/getting-started/ - /chronograf/v1.6/introduction/getting_started/ menu: chronograf_1_6: @@ -11,18 +11,18 @@ menu: --- ## Overview -Chronograf allows you to quickly see data you have stored in InfluxDB so you can build robust queries and alerts. After your administrator has set up Chronograf as described in [Installing Chronograf](/chronograf/latest/introduction/installation), get started with key features using the guides below. +Chronograf allows you to quickly see data you have stored in InfluxDB so you can build robust queries and alerts. After your administrator has set up Chronograf as described in [Installing Chronograf](/{{< latest "chronograf" >}}/introduction/installation), get started with key features using the guides below. ### Data visualization -* Investigate your data by building queries using [InfluxQL](/influxdb/latest/query_language/). -* Use pre-created [pre-created dashboards](/chronograf/latest/guides/using-precreated-dashboards/) to monitor your application data or [create your own dashboards](/chronograf/latest/guides/create-a-dashboard/). -* Customize dashboards using [template variables](/chronograf/latest/guides/dashboard-template-variables/). +* Investigate your data by building queries using [InfluxQL](/{{< latest "influxdb" "v1" >}}/query_language/). +* Use pre-created [pre-created dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards/) to monitor your application data or [create your own dashboards](/{{< latest "chronograf" >}}/guides/create-a-dashboard/). +* Customize dashboards using [template variables](/{{< latest "chronograf" >}}/guides/dashboard-template-variables/). ### Alerting -* [Create alert rules](/chronograf/latest/guides/create-alert-rules/) to generate threshold, relative, and deadman alerts on your data. -* [View all active alerts](/chronograf/latest/guides/create-alert-rules/#step-2-view-the-alerts) on an alert dashboard. -* Use [alert endpoints](/chronograf/latest/guides/configuring-alert-endpoints/) in Chronograf to send alert messages to specific URLs and applications. +* [Create alert rules](/{{< latest "chronograf" >}}/guides/create-alert-rules/) to generate threshold, relative, and deadman alerts on your data. +* [View all active alerts](/{{< latest "chronograf" >}}/guides/create-alert-rules/#step-2-view-the-alerts) on an alert dashboard. +* Use [alert endpoints](/{{< latest "chronograf" >}}/guides/configuring-alert-endpoints/) in Chronograf to send alert messages to specific URLs and applications. ### Infrastructure monitoring -* [View all hosts](/chronograf/latest/guides/monitoring-influxenterprise-clusters/#step-4-explore-the-monitoring-data-in-chronograf) and their statuses in your infrastructure. -* [Use pre-created dashboards](/chronograf/latest/guides/using-precreated-dashboards/) to monitor your applications. +* [View all hosts](/{{< latest "chronograf" >}}/guides/monitoring-influxenterprise-clusters/#step-4-explore-the-monitoring-data-in-chronograf) and their statuses in your infrastructure. +* [Use pre-created dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards/) to monitor your applications. diff --git a/content/chronograf/v1.6/troubleshooting/_index.md b/content/chronograf/v1.6/troubleshooting/_index.md index f6b302ceb..85c191d78 100644 --- a/content/chronograf/v1.6/troubleshooting/_index.md +++ b/content/chronograf/v1.6/troubleshooting/_index.md @@ -9,4 +9,4 @@ menu: Follow the link below to access Chronograf's FAQ. -## [Frequently Asked Questions](/chronograf/latest/troubleshooting/frequently-asked-questions/) +## [Frequently Asked Questions](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/) diff --git a/content/chronograf/v1.6/troubleshooting/frequently-asked-questions.md b/content/chronograf/v1.6/troubleshooting/frequently-asked-questions.md index 7303d7814..4316d442b 100644 --- a/content/chronograf/v1.6/troubleshooting/frequently-asked-questions.md +++ b/content/chronograf/v1.6/troubleshooting/frequently-asked-questions.md @@ -9,7 +9,7 @@ menu: ## How do I connect Chronograf to an InfluxDB Enterprise cluster? -The connection details form requires additional information when connecting Chronograf to an [InfluxDB Enterprise cluster](https://docs.influxdata.com/enterprise_influxdb/latest/). +The connection details form requires additional information when connecting Chronograf to an [InfluxDB Enterprise cluster](/{{< latest "enterprise_influxdb" >}}/). When you enter the InfluxDB HTTP bind address in the `Connection String` input, Chronograf automatically checks if that InfluxDB instance is a data node. If it is a data node, Chronograf automatically adds the `Meta Service Connection URL` input to the connection details form. @@ -19,4 +19,4 @@ Enter the HTTP bind address of one of your cluster's meta nodes into that input Note that the example above assumes that you do not have authentication enabled. If you have authentication enabled, the form requires username and password information. -For more details about monitoring an InfluxDB Enterprise cluster, see the [Monitor an InfluxDB Enterprise Cluster](/chronograf/latest/guides/monitoring-influxenterprise-clusters/) guide. +For more details about monitoring an InfluxDB Enterprise cluster, see the [Monitor an InfluxDB Enterprise Cluster](/{{< latest "chronograf" >}}/guides/monitoring-influxenterprise-clusters/) guide. diff --git a/content/chronograf/v1.7/_index.md b/content/chronograf/v1.7/_index.md index df941f3df..e2ca75519 100644 --- a/content/chronograf/v1.7/_index.md +++ b/content/chronograf/v1.7/_index.md @@ -38,12 +38,12 @@ Chronograf offers a UI for [Kapacitor](https://github.com/influxdata/kapacitor), * Create and delete databases and retention policies * View currently-running queries and stop inefficient queries from overloading your system -* Create, delete, and assign permissions to users (Chronograf supports [InfluxDB OSS](/influxdb/latest/administration/authentication_and_authorization/#authorization) and InfluxEnterprise user management) +* Create, delete, and assign permissions to users (Chronograf supports [InfluxDB OSS](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#authorization) and InfluxEnterprise user management) ### Multi-organization and multi-user support ->**Note:** To use this feature, OAuth 2.0 authentication must be configured. Once configured, the Chronograf Admin tab on the Admin menu is visible. For details, see [Managing Chronograf security](https://docs.influxdata.com/chronograf/v1.7/administration/managing-security/). +>**Note:** To use this feature, OAuth 2.0 authentication must be configured. Once configured, the Chronograf Admin tab on the Admin menu is visible. For details, see [Managing Chronograf security](/chronograf/v1.7/administration/managing-security/). * Create organizations and assign users to those organizations * Restrict access to administrative functions diff --git a/content/chronograf/v1.7/about_the_project/release-notes-changelog.md b/content/chronograf/v1.7/about_the_project/release-notes-changelog.md index 7021998b9..251bf497e 100644 --- a/content/chronograf/v1.7/about_the_project/release-notes-changelog.md +++ b/content/chronograf/v1.7/about_the_project/release-notes-changelog.md @@ -836,9 +836,9 @@ menu: ### UI improvements * When dashboard time range is changed, reset graphs that are zoomed in - * [Bar graph](/chronograf/latest/guides/visualization-types/#bar-graph) option added to dashboard + * [Bar graph](/{{< latest "chronograf" >}}/guides/visualization-types/#bar-graph) option added to dashboard * Redesign source management table to be more intuitive - * Redesign [Line + Single Stat](/chronograf/latest/guides/visualization-types/#line-graph-single-stat) cells to appear more like a sparkline, and improve legibility + * Redesign [Line + Single Stat](/{{< latest "chronograf" >}}/guides/visualization-types/#line-graph-single-stat) cells to appear more like a sparkline, and improve legibility ## v1.3.2.0 [2017-06-05] @@ -854,7 +854,7 @@ menu: ### Features - * Add UI to the Data Explorer for [writing data to InfluxDB](/chronograf/latest/guides/querying-data/) + * Add UI to the Data Explorer for [writing data to InfluxDB](/{{< latest "chronograf" >}}/guides/querying-data/) ### UI improvements @@ -874,26 +874,26 @@ In versions 1.3.1+, installing a new version of Chronograf automatically clears ### Bug fixes - * Fix infinite spinner when `/chronograf` is a [basepath](/chronograf/latest/administration/config-options/#p-basepath) + * Fix infinite spinner when `/chronograf` is a [basepath](/{{< latest "chronograf" >}}/administration/config-options/#p-basepath) * Remove the query templates dropdown from dashboard cell editor mode * Fix the backwards sort arrows in table column headers * Make the logout button consistent with design * Fix the loading spinner on graphs * Filter out any template variable values that are empty, whitespace, or duplicates - * Allow users to click the add query button after selecting singleStat as the [visualization type](/chronograf/latest/guides/visualization-types) + * Allow users to click the add query button after selecting singleStat as the [visualization type](/{{< latest "chronograf" >}}/guides/visualization-types) * Add a query for windows uptime - thank you, @brianbaker! ### Features * Add log event handler- thank you, @mpchadwick! * Update Go (golang) vendoring to dep and committed vendor directory - * Add autocomplete functionality to [template variable](/chronograf/latest/guides/dashboard-template-variables) dropdowns + * Add autocomplete functionality to [template variable](/{{< latest "chronograf" >}}/guides/dashboard-template-variables) dropdowns ### UI improvements * Refactor scrollbars to support non-webkit browsers * Increase the query builder's default height in cell editor mode and in the data explorer - * Make the [template variables](/chronograf/latest/guides/dashboard-template-variables) manager more space efficient + * Make the [template variables](/{{< latest "chronograf" >}}/guides/dashboard-template-variables) manager more space efficient * Add page spinners to pages that did not have them * Denote which source is connected in the sources table * Use milliseconds in the InfluxDB dashboard instead of nanoseconds @@ -903,25 +903,25 @@ In versions 1.3.1+, installing a new version of Chronograf automatically clears ### Bug fixes - * Fix the link to home when using the [`--basepath` option](/chronograf/latest/administration/config-options/#p-basepath) + * Fix the link to home when using the [`--basepath` option](/{{< latest "chronograf" >}}/administration/config-options/#p-basepath) * Remove the notification to login on the login page * Support queries that perform math on functions * Prevent the creation of blank template variables * Ensure thresholds for Kapacitor Rule Alerts appear on page load * Update the Kapacitor configuration page when the configuration changes - * Fix Authentication when using Chronograf with a set [basepath](/chronograf/latest/administration/config-options/#p-basepath) + * Fix Authentication when using Chronograf with a set [basepath](/{{< latest "chronograf" >}}/administration/config-options/#p-basepath) * Show red indicator on Hosts Page for an offline host * Support escaping from presentation mode in Safari * Re-implement level colors on the alerts page * Fix router bug introduced by upgrading to react-router v3.0 - * Show legend on [Line+Stat](/chronograf/latest/guides/visualization-types/#line-graph-single-stat) visualization type + * Show legend on [Line+Stat](/{{< latest "chronograf" >}}/guides/visualization-types/#line-graph-single-stat) visualization type * Prevent queries with `:dashboardTime:` from breaking the query builder ### Features * Add line-protocol proxy for InfluxDB/InfluxEnterprise Cluster data sources * Add `:dashboardTime:` to support cell-specific time ranges on dashboards - * Add support for enabling and disabling [TICKscripts that were created outside Chronograf](/chronograf/latest/guides/advanced-kapacitor/#tickscript-management) + * Add support for enabling and disabling [TICKscripts that were created outside Chronograf](/{{< latest "chronograf" >}}/guides/advanced-kapacitor/#tickscript-management) * Allow users to delete Kapacitor configurations ### UI improvements diff --git a/content/chronograf/v1.7/administration/chrono-on-clusters.md b/content/chronograf/v1.7/administration/chrono-on-clusters.md index 68b68396f..cec4d2bb4 100644 --- a/content/chronograf/v1.7/administration/chrono-on-clusters.md +++ b/content/chronograf/v1.7/administration/chrono-on-clusters.md @@ -8,7 +8,7 @@ menu: parent: Administration --- -The connection details form requires additional information when connecting Chronograf to an [InfluxDB Enterprise cluster](https://docs.influxdata.com/enterprise_influxdb/latest/). +The connection details form requires additional information when connecting Chronograf to an [InfluxDB Enterprise cluster](/{{< latest "enterprise_influxdb" >}}/). When you enter the InfluxDB HTTP bind address in the `Connection String` input, Chronograf automatically checks if that InfluxDB instance is a data node. If it is a data node, Chronograf automatically adds the `Meta Service Connection URL` input to the connection details form. @@ -19,4 +19,4 @@ Enter the HTTP bind address of one of your cluster's meta nodes into that input Note that the example above assumes that you do not have authentication enabled. If you have authentication enabled, the form requires username and password information. -For details about monitoring InfluxEnterprise clusters, see [Monitoring InfluxDB Enterprise clusters](/chronograf/latest/guides/monitoring-influxenterprise-clusters). +For details about monitoring InfluxEnterprise clusters, see [Monitoring InfluxDB Enterprise clusters](/{{< latest "chronograf" >}}/guides/monitoring-influxenterprise-clusters). diff --git a/content/chronograf/v1.7/administration/config-options.md b/content/chronograf/v1.7/administration/config-options.md index a25febda3..91c94505d 100644 --- a/content/chronograf/v1.7/administration/config-options.md +++ b/content/chronograf/v1.7/administration/config-options.md @@ -78,7 +78,7 @@ Environment variable: `$BOLT_PATH` #### `--canned-path=` | `-c` -The path to the directory of [canned dashboards](/chronograf/latest/guides/using-precreated-dashboards) files. +The path to the directory of [canned dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards) files. Default value: `/usr/share/chronograf/canned` diff --git a/content/chronograf/v1.7/administration/configuration.md b/content/chronograf/v1.7/administration/configuration.md index d8698b855..4a5920dee 100644 --- a/content/chronograf/v1.7/administration/configuration.md +++ b/content/chronograf/v1.7/administration/configuration.md @@ -13,7 +13,7 @@ However, it is also possible to set custom default configuration options in the ## Starting the Chronograf service -Start Chronograf using the default configuration options, or [customize your configuration](https://docs.influxdata.com/chronograf/v1.7/administration/configuration/) with environment variables and command line options (for example, to configure OAuth 2.0 authentication) based on your requirements. +Start Chronograf using the default configuration options, or [customize your configuration](/chronograf/v1.7/administration/configuration/) with environment variables and command line options (for example, to configure OAuth 2.0 authentication) based on your requirements. **Linux:** @@ -27,12 +27,12 @@ sudo systemctl start chronograf [OPTIONS] chronograf [OPTIONS] ``` -`[OPTIONS]` are available Chronograf command line options, separated by spaces. See the [Chronograf configuration options](https://docs.influxdata.com/chronograf/v1.7/administration/config-options) documentation for details about configuration options, including command line options and corresponding environment variables. +`[OPTIONS]` are available Chronograf command line options, separated by spaces. See the [Chronograf configuration options](/chronograf/v1.7/administration/config-options) documentation for details about configuration options, including command line options and corresponding environment variables. ## Setting custom default Chronograf config options Custom default Chronograf configuration settings can be defined in `/etc/default/chronograf`. -This file consists of key-value pairs. See keys (environment variables) for [Chronograf configuration options](https://docs.influxdata.com/chronograf/v1.7/administration/config-options), and set values for the keys you want to configure. +This file consists of key-value pairs. See keys (environment variables) for [Chronograf configuration options](/chronograf/v1.7/administration/config-options), and set values for the keys you want to configure. ```conf HOST=0.0.0.0 @@ -55,7 +55,7 @@ To set up security for Chronograf, configure: After you configure OAuth 2.0 authentication, you can set up multiple organizations, roles, and users. For details, check out the following topics: * [Managing organizations](chronograf/v1.7/administration/managing-organizations/) -* [Managing Chronograf users](https://docs.influxdata.com/chronograf/v1.7/administration/managing-chronograf-users/) +* [Managing Chronograf users](/chronograf/v1.7/administration/managing-chronograf-users/) diff --git a/content/chronograf/v1.7/administration/creating-connections.md b/content/chronograf/v1.7/administration/creating-connections.md index bc01964a2..d0904a063 100644 --- a/content/chronograf/v1.7/administration/creating-connections.md +++ b/content/chronograf/v1.7/administration/creating-connections.md @@ -31,15 +31,15 @@ To create an InfluxDB connection in the Chronograf UI: * **Connection URL**: Enter the hostname or IP address of the InfluxDB instance and the port. The field is prefilled with `http://localhost:8086`. * **Connection Name**: Enter the name for this connection. * **Username**: Enter the username that will be shared for this connection. - *Required only if [authorization is enabled](/influxdb/latest/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.* + *Required only if [authorization is enabled](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.* * **Password**: Enter the password. - *Required only if [authorization is enabled](/influxdb/latest/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.* + *Required only if [authorization is enabled](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.* * **Telegraf Database Name**: This field specifies the database that Chronograf will use for populating different parts of the application, including the Host List page. If you've changed the default retention policy in your InfluxDB instance, you may want to change it here as well. If none is provided, we will use `autogen`. You will still be able to query any database you have access to in the InfluxDB instance when building dashboards or exploring data. - * **Default Retention Policy**: Enter the name of the default [retention policy](/influxdb/latest/concepts/glossary/#retention-policy-rp). If none i s provided, it assumes `autogen`. + * **Default Retention Policy**: Enter the name of the default [retention policy](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#retention-policy-rp). If none i s provided, it assumes `autogen`. * **Make this the default connection**: When this option is selected, this InfluxDB connection will be used when Chronograf is launched. 4. Click **Add Connection** - * If the connection is valid, the Dashboards window appears, allowing you to import dashboard templates you can use to display and analyze your data. For details, see [Creating dashboards](/chronograf/latest/guides/create-a-dashboard). + * If the connection is valid, the Dashboards window appears, allowing you to import dashboard templates you can use to display and analyze your data. For details, see [Creating dashboards](/{{< latest "chronograf" >}}/guides/create-a-dashboard). * If the connection cannot be created, the following error message appears: "Unable to create source: Error contacting source." If this occurs, ensure all connection credentials are correct and that the InfluxDB instance is running and accessible. @@ -109,11 +109,11 @@ Any string you want to use as the display name of the source. #### `username` Username used to access the InfluxDB server or cluster. -*Only required if [authorization is enabled](/influxdb/latest/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.* +*Only required if [authorization is enabled](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.* #### `password` Password used to access the InfluxDB server or cluster. -*Only required if [authorization is enabled](/influxdb/latest/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.* +*Only required if [authorization is enabled](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.* #### `url` URL of the InfluxDB server or cluster. @@ -176,9 +176,9 @@ To create a Kapacitor connection using the Chronograf UI: * **Kapacitor URL**: Enter the hostname or IP address of the Kapacitor instance and the port. The field is prefilled with `http://localhost:9092`. * **Name**: Enter the name for this connection. * **Username**: Enter the username that will be shared for this connection. - *Only required if [authorization is enabled](/kapacitor/latest/administration/security/#kapacitor-authentication-and-authorization) on the Kapacitor instance or cluster to which you're connecting.* + *Only required if [authorization is enabled](/{{< latest "kapacitor" >}}/administration/security/#kapacitor-authentication-and-authorization) on the Kapacitor instance or cluster to which you're connecting.* * **Password**: Enter the password. - *Only required if [authorization is enabled](/kapacitor/latest/administration/security/#kapacitor-authentication-and-authorization) on the Kapacitor instance or cluster to which you're connecting.* + *Only required if [authorization is enabled](/{{< latest "kapacitor" >}}/administration/security/#kapacitor-authentication-and-authorization) on the Kapacitor instance or cluster to which you're connecting.* 4. Click **Continue**. If the connection is valid, the message "Kapacitor Created! Configuring endpoints is optional." appears. To configure alert endpoints, see [Configuring alert endpoints](/chronograf/v1.7/guides/configuring-alert-endpoints/). diff --git a/content/chronograf/v1.7/administration/managing-chronograf-users.md b/content/chronograf/v1.7/administration/managing-chronograf-users.md index e678e3a1f..af7c9d816 100644 --- a/content/chronograf/v1.7/administration/managing-chronograf-users.md +++ b/content/chronograf/v1.7/administration/managing-chronograf-users.md @@ -31,7 +31,7 @@ menu: ## Managing Chronograf users and roles -> ***Note:*** Support for organizations and user roles is available in Chronograf 1.4 or later. First, OAuth 2.0 authentication must be configured (if it is, you'll see the Chronograf Admin tab on the Admin menu). For more information, see [Managing security] (https://docs.influxdata.com/chronograf/v1.7/administration/managing-security/). +> ***Note:*** Support for organizations and user roles is available in Chronograf 1.4 or later. First, OAuth 2.0 authentication must be configured (if it is, you'll see the Chronograf Admin tab on the Admin menu). For more information, see [Managing security] (/chronograf/v1.7/administration/managing-security/). Chronograf includes four organization-bound user roles and one cross-organization SuperAdmin status. In an organization, admins (with the `admin` role) or users with SuperAdmin status can create, update, and assign roles to a user or remove a role assignment. diff --git a/content/chronograf/v1.7/administration/managing-influxdb-users.md b/content/chronograf/v1.7/administration/managing-influxdb-users.md index fecfafba0..72269d909 100644 --- a/content/chronograf/v1.7/administration/managing-influxdb-users.md +++ b/content/chronograf/v1.7/administration/managing-influxdb-users.md @@ -13,7 +13,7 @@ menu: The **Chronograf Admin** provides InfluxDB user management for InfluxDB OSS and InfluxDB Enterprise users. -> ***Note:*** For details on Chronograf user authentication and management, see [Managing security](/chronograf/latest/administration/managing-security/). +> ***Note:*** For details on Chronograf user authentication and management, see [Managing security](/{{< latest "chronograf" >}}/administration/managing-security/). **On this page:** @@ -58,7 +58,7 @@ Restart the InfluxDB service for your configuration changes to take effect: ### Step 3: Create an admin user. -Because authentication is enabled, you need to create an [admin user](/influxdb/latest/administration/authentication_and_authorization/#user-types-and-privileges) before you can do anything else in the database. +Because authentication is enabled, you need to create an [admin user](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#user-types-and-privileges) before you can do anything else in the database. Run the `curl` command below to create an admin user, replacing: * `localhost` with the IP or hostname of your InfluxDB OSS instance or one of your InfluxEnterprise data nodes @@ -91,7 +91,7 @@ On the **Chronograf Admin** page: ![InfluxDB OSS user management](/img/chronograf/1-6-admin-usermanagement-oss.png) InfluxDB users are either admin users or non-admin users. -See InfluxDB's [authentication and authorization](/influxdb/latest/administration/authentication_and_authorization/#user-types-and-privileges) documentation for more information about those user types. +See InfluxDB's [authentication and authorization](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#user-types-and-privileges) documentation for more information about those user types. > ***Note:*** Note that Chronograf currently does not support assigning InfluxDB database `READ`or `WRITE` access to non-admin users. >This is a known issue. @@ -156,12 +156,12 @@ Assign permissions and roles to both admin and non-admin users. Permission to add or remove nodes from a cluster. **Relevant `influxd-ctl` arguments**: -[`add-data`](/enterprise_influxdb/latest/administration/cluster-commands/#add-data), -[`add-meta`](/enterprise_influxdb/latest/administration/cluster-commands/#add-meta), -[`join`](/enterprise_influxdb/latest/administration/cluster-commands/#join), -[`remove-data`](/enterprise_influxdb/latest/administration/cluster-commands/#remove-data), -[`remove-meta`](/enterprise_influxdb/latest/administration/cluster-commands/#remove-meta), and -[`leave`](/enterprise_influxdb/latest/administration/cluster-commands/#leave) +[`add-data`](/{{< latest "enterprise_influxdb" >}}/administration/cluster-commands/#add-data), +[`add-meta`](/{{< latest "enterprise_influxdb" >}}/administration/cluster-commands/#add-meta), +[`join`](/{{< latest "enterprise_influxdb" >}}/administration/cluster-commands/#join), +[`remove-data`](/{{< latest "enterprise_influxdb" >}}/administration/cluster-commands/#remove-data), +[`remove-meta`](/{{< latest "enterprise_influxdb" >}}/administration/cluster-commands/#remove-meta), and +[`leave`](/{{< latest "enterprise_influxdb" >}}/administration/cluster-commands/#leave) **Pages in Chronograf that require this permission**: NA @@ -169,18 +169,18 @@ Permission to add or remove nodes from a cluster. Permission to copy shards. **Relevant `influxd-ctl` arguments**: -[`copy-shard`](/enterprise_influxdb/latest/administration/cluster-commands/#copy-shard) +[`copy-shard`](/{{< latest "enterprise_influxdb" >}}/administration/cluster-commands/#copy-shard) **Pages in Chronograf that require this permission**: NA #### CreateDatabase -Permission to create databases, create [retention policies](/influxdb/latest/concepts/glossary/#retention-policy-rp), alter retention policies, and view retention policies. +Permission to create databases, create [retention policies](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#retention-policy-rp), alter retention policies, and view retention policies. **Relevant InfluxQL queries**: -[`CREATE DATABASE`](/influxdb/latest/query_language/database_management/#create-database), -[`CREATE RETENTION POLICY`](/influxdb/latest/query_language/database_management/#create-retention-policies-with-create-retention-policy), -[`ALTER RETENTION POLICY`](/influxdb/latest/query_language/database_management/#modify-retention-policies-with-alter-retention-policy), and -[`SHOW RETENTION POLICIES`](/influxdb/latest/query_language/schema_exploration/#show-retention-policies) +[`CREATE DATABASE`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#create-database), +[`CREATE RETENTION POLICY`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#create-retention-policies-with-create-retention-policy), +[`ALTER RETENTION POLICY`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#modify-retention-policies-with-alter-retention-policy), and +[`SHOW RETENTION POLICIES`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-retention-policies) **Pages in Chronograf that require this permission**: Dashboards, Data Explorer, and Databases on the Admin page @@ -188,25 +188,25 @@ Permission to create databases, create [retention policies](/influxdb/latest/con Permission to manage users and roles; create users, drop users, grant admin status to users, grant permissions to users, revoke admin status from users, revoke permissions from users, change user passwords, view user permissions, and view users and their admin status. **Relevant InfluxQL queries**: -[`CREATE USER`](/influxdb/latest/administration/authentication_and_authorization/#user-management-commands), -[`DROP USER`](/influxdb/latest/administration/authentication_and_authorization/#general-admin-and-non-admin-user-management), -[`GRANT ALL PRIVILEGES`](/influxdb/latest/administration/authentication_and_authorization/#user-management-commands), -[`GRANT [READ,WRITE,ALL]`](/influxdb/latest/administration/authentication_and_authorization/#non-admin-user-management), -[`REVOKE ALL PRIVILEGES`](/influxdb/latest/administration/authentication_and_authorization/#user-management-commands), -[`REVOKE [READ,WRITE,ALL]`](/influxdb/latest/administration/authentication_and_authorization/#non-admin-user-management), -[`SET PASSWORD`](/influxdb/latest/administration/authentication_and_authorization/#general-admin-and-non-admin-user-management), -[`SHOW GRANTS`](/influxdb/latest/administration/authentication_and_authorization/#non-admin-user-management), and -[`SHOW USERS`](/influxdb/latest/administration/authentication_and_authorization/#user-management-commands) +[`CREATE USER`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#user-management-commands), +[`DROP USER`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#general-admin-and-non-admin-user-management), +[`GRANT ALL PRIVILEGES`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#user-management-commands), +[`GRANT [READ,WRITE,ALL]`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#non-admin-user-management), +[`REVOKE ALL PRIVILEGES`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#user-management-commands), +[`REVOKE [READ,WRITE,ALL]`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#non-admin-user-management), +[`SET PASSWORD`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#general-admin-and-non-admin-user-management), +[`SHOW GRANTS`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#non-admin-user-management), and +[`SHOW USERS`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#user-management-commands) **Pages in Chronograf that require this permission**: Data Explorer, Dashboards, Users and Roles on the Admin page #### DropData -Permission to drop data, in particular [series](/influxdb/latest/concepts/glossary/#series) and [measurements](/influxdb/latest/concepts/glossary/#measurement). +Permission to drop data, in particular [series](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#series) and [measurements](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#measurement). **Relevant InfluxQL queries**: -[`DROP SERIES`](/influxdb/latest/query_language/database_management/#drop-series-from-the-index-with-drop-series), -[`DELETE`](/influxdb/latest/query_language/database_management/#delete-series-with-delete), and -[`DROP MEASUREMENT`](/influxdb/latest/query_language/database_management/#delete-measurements-with-drop-measurement) +[`DROP SERIES`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#drop-series-from-the-index-with-drop-series), +[`DELETE`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#delete-series-with-delete), and +[`DROP MEASUREMENT`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#delete-measurements-with-drop-measurement) **Pages in Chronograf that require this permission**: NA @@ -214,8 +214,8 @@ Permission to drop data, in particular [series](/influxdb/latest/concepts/glossa Permission to drop databases and retention policies. **Relevant InfluxQL queries**: -[`DROP DATABASE`](/influxdb/latest/query_language/database_management/#delete-a-database-with-drop-database) and -[`DROP RETENTION POLICY`](/influxdb/latest/query_language/database_management/#delete-retention-policies-with-drop-retention-policy) +[`DROP DATABASE`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#delete-a-database-with-drop-database) and +[`DROP RETENTION POLICY`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#delete-retention-policies-with-drop-retention-policy) **Pages in Chronograf that require this permission**: Data Explorer, Dashboards, Databases on the Admin page @@ -231,12 +231,12 @@ Permission to access the configuration-related API calls for InfluxKapacitor Ent **Pages in Chronograf that require this permission**: NA #### ManageContinuousQuery -Permission to create, drop, and view [continuous queries](/influxdb/latest/concepts/glossary/#continuous-query-cq). +Permission to create, drop, and view [continuous queries](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#continuous-query-cq). **Relevant InfluxQL queries**: -[`CreateContinuousQueryStatement`](/influxdb/latest/query_language/continuous_queries/), -[`DropContinuousQueryStatement`](/influxdb/latest/query_language/continuous_queries/#deleting-continuous-queries), and -[`ShowContinuousQueriesStatement`](/influxdb/latest/query_language/continuous_queries/#listing-continuous-queries) +[`CreateContinuousQueryStatement`](/{{< latest "influxdb" "v1" >}}/query_language/continuous_queries/), +[`DropContinuousQueryStatement`](/{{< latest "influxdb" "v1" >}}/query_language/continuous_queries/#deleting-continuous-queries), and +[`ShowContinuousQueriesStatement`](/{{< latest "influxdb" "v1" >}}/query_language/continuous_queries/#listing-continuous-queries) **Pages in Chronograf that require this permission**: Data Explorer, Dashboards @@ -244,28 +244,28 @@ Permission to create, drop, and view [continuous queries](/influxdb/latest/conce Permission to view and kill queries. **Relevant InfluxQL queries**: -[`SHOW QUERIES`](/influxdb/latest/troubleshooting/query_management/#list-currently-running-queries-with-show-queries) and -[`KILL QUERY`](/influxdb/latest/troubleshooting/query_management/#stop-currently-running-queries-with-kill-query) +[`SHOW QUERIES`](/{{< latest "influxdb" "v1" >}}/troubleshooting/query_management/#list-currently-running-queries-with-show-queries) and +[`KILL QUERY`](/{{< latest "influxdb" "v1" >}}/troubleshooting/query_management/#stop-currently-running-queries-with-kill-query) **Pages in Chronograf that require this permission**: Queries on the Admin page #### ManageShard -Permission to copy, delete, and view [shards](/influxdb/latest/concepts/glossary/#shard). +Permission to copy, delete, and view [shards](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#shard). **Relevant InfluxQL queries**: -[`DropShardStatement`](/influxdb/latest/query_language/database_management/#delete-a-shard-with-drop-shard), -[`ShowShardGroupsStatement`](/influxdb/latest/query_language/spec/#show-shard-groups), and -[`ShowShardsStatement`](/influxdb/latest/query_language/spec/#show-shards) +[`DropShardStatement`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#delete-a-shard-with-drop-shard), +[`ShowShardGroupsStatement`](/{{< latest "influxdb" "v1" >}}/query_language/spec/#show-shard-groups), and +[`ShowShardsStatement`](/{{< latest "influxdb" "v1" >}}/query_language/spec/#show-shards) **Pages in Chronograf that require this permission**: NA #### ManageSubscription -Permission to create, drop, and view [subscriptions](/influxdb/latest/concepts/glossary/#subscription). +Permission to create, drop, and view [subscriptions](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#subscription). **Relevant InfluxQL queries**: -[`CREATE SUBSCRIPTION`](/influxdb/latest/query_language/spec/#create-subscription), -[`DROP SUBSCRIPTION`](/influxdb/latest/query_language/spec/#drop-subscription), and -[`SHOW SUBSCRIPTIONS`](/influxdb/latest/query_language/spec/#show-subscriptions) +[`CREATE SUBSCRIPTION`](/{{< latest "influxdb" "v1" >}}/query_language/spec/#create-subscription), +[`DROP SUBSCRIPTION`](/{{< latest "influxdb" "v1" >}}/query_language/spec/#drop-subscription), and +[`SHOW SUBSCRIPTIONS`](/{{< latest "influxdb" "v1" >}}/query_language/spec/#show-subscriptions) **Pages in Chronograf that require this permission**: Alerting @@ -282,12 +282,12 @@ Permission to view cluster statistics and diagnostics. Permission to read data. **Relevant InfluxQL queries**: -[`SHOW FIELD KEYS`](/influxdb/latest/query_language/schema_exploration/#show-field-keys), -[`SHOW MEASUREMENTS`](/influxdb/latest/query_language/schema_exploration/#show-measurements), -[`SHOW SERIES`](/influxdb/latest/query_language/schema_exploration/#show-series), -[`SHOW TAG KEYS`](/influxdb/latest/query_language/schema_exploration/#show-tag-keys), -[`SHOW TAG VALUES`](/influxdb/latest/query_language/schema_exploration/#show-tag-values), and -[`SHOW RETENTION POLICIES`](/influxdb/latest/query_language/schema_exploration/#show-retention-policies) +[`SHOW FIELD KEYS`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-field-keys), +[`SHOW MEASUREMENTS`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-measurements), +[`SHOW SERIES`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-series), +[`SHOW TAG KEYS`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-tag-keys), +[`SHOW TAG VALUES`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-tag-values), and +[`SHOW RETENTION POLICIES`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-retention-policies) **Pages in Chronograf that require this permission**: Admin, Alerting, Dashboards, Data Explorer, Host List diff --git a/content/chronograf/v1.7/administration/managing-organizations.md b/content/chronograf/v1.7/administration/managing-organizations.md index 7540ffb1b..efb9daf97 100644 --- a/content/chronograf/v1.7/administration/managing-organizations.md +++ b/content/chronograf/v1.7/administration/managing-organizations.md @@ -24,7 +24,7 @@ menu: First, OAuth 2.0 authentication must be configured (if it is, you'll see the Chronograf Admin tab on the Admin menu). For more information, see [managing security](/chronograf/v1.7/administration/managing-security/). -For information about the new user roles and SuperAdmin status, see [Managing Chronograf users](https://docs.influxdata.com/chronograf/v1.7/administration/managing-chronograf-users/). +For information about the new user roles and SuperAdmin status, see [Managing Chronograf users](/chronograf/v1.7/administration/managing-chronograf-users/). A Chronograf organization is a collection of Chronograf users who share common Chronograf-owned resources, including dashboards, InfluxDB connections, and Kapacitor connections. Organizations can be used to represent companies, functional units, projects, or teams. Chronograf users can be members of multiple organizations. diff --git a/content/chronograf/v1.7/administration/managing-security.md b/content/chronograf/v1.7/administration/managing-security.md index a092b067d..466b37a1a 100644 --- a/content/chronograf/v1.7/administration/managing-security.md +++ b/content/chronograf/v1.7/administration/managing-security.md @@ -20,8 +20,8 @@ To enhance security, configure Chronograf to authenticate and authorize with [OA ## Configure OAuth 2.0 > After configuring OAuth 2.0, the Chronograf Admin tab becomes visible. -> You can then set up [multiple organizations](https://docs.influxdata.com/chronograf/latest/administration/managing-organizations/) -> and [users](https://docs.influxdata.com/chronograf/latest/administration/managing-influxdb-users/). +> You can then set up [multiple organizations](/{{< latest "chronograf" >}}/administration/managing-organizations/) +> and [users](/{{< latest "chronograf" >}}/administration/managing-influxdb-users/). Configure Chronograf to use an OAuth 2.0 provider and JWT (JSON Web Token) to authenticate users and enable role-based access controls. diff --git a/content/chronograf/v1.7/administration/prebuilt-dashboards.md b/content/chronograf/v1.7/administration/prebuilt-dashboards.md index 2d35db99a..cc43d1c5f 100644 --- a/content/chronograf/v1.7/administration/prebuilt-dashboards.md +++ b/content/chronograf/v1.7/administration/prebuilt-dashboards.md @@ -7,7 +7,7 @@ menu: weight: 50 parent: Administration --- -Chronograf lets you import a variety of prebuilt dashboards that visualize metrics collect by specific [Telegraf input plugins](/telegraf/latest/plugins/plugin-list). The following Telegraf-related dashboards templates are available. +Chronograf lets you import a variety of prebuilt dashboards that visualize metrics collect by specific [Telegraf input plugins](/{{< latest "telegraf" >}}/plugins/plugin-list). The following Telegraf-related dashboards templates are available. For details on how to import dashboards while adding a connection in Chronograf, see [Creating connections](/chronograf/v1.7/administration/creating-connections//#managing-influxdb-connections-using-the-chronograf-ui). @@ -30,12 +30,12 @@ The Docker dashboard displays the following information: ### Plugins -- [`docker` plugin](/telegraf/latest/plugins/plugin-list/#docker) -- [`disk` plugin](/telegraf/latest/plugins/plugin-list/#disk) -- [`mem` plugin](/telegraf/latest/plugins/plugin-list/#mem) -- [`diskio` plugin](/telegraf/latest/plugins/plugin-list/#diskio) -- [`system` plugin](/telegraf/latest/plugins/plugin-list/#system) -- [`cpu` plugin](/telegraf/latest/plugins/plugin-list/#cpu) +- [`docker` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#docker) +- [`disk` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#disk) +- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#mem) +- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#diskio) +- [`system` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#system) +- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#cpu) ## Kubernetes Node The Kubernetes Node dashboard displays the following information: @@ -53,7 +53,7 @@ The Kubernetes Node dashboard displays the following information: - K8s - Kubelet Memory Bytes ### Plugins -- [kubernetes](/telegraf/latest/plugins/plugin-list/#kubernetes) +- [kubernetes](/{{< latest "telegraf" >}}/plugins/plugin-list/#kubernetes) ## Kubernetes Overview The Kubernetes Node dashboard displays the following information: @@ -72,7 +72,7 @@ The Kubernetes Node dashboard displays the following information: ### Plugins -- [kubernetes](/telegraf/latest/plugins/plugin-list/#kubernetes) +- [kubernetes](/{{< latest "telegraf" >}}/plugins/plugin-list/#kubernetes) ## Kubernetes Pod The Kubernetes Pod dashboard displays the following information: @@ -87,7 +87,7 @@ The Kubernetes Pod dashboard displays the following information: - K8s - Pod TX Bytes/Second ### Plugins -- [kubernetes](/telegraf/latest/plugins/plugin-list/#kubernetes) +- [kubernetes](/{{< latest "telegraf" >}}/plugins/plugin-list/#kubernetes) ## Riak The Riak dashboard displays the following information: @@ -101,7 +101,7 @@ The Riak dashboard displays the following information: - Riak - Read Repairs/Minute ### Plugins -- [`riak` plugin](/telegraf/latest/plugins/plugin-list/#riak) +- [`riak` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#riak) ## Consul The Consul dashboard displays the following information: @@ -110,7 +110,7 @@ The Consul dashboard displays the following information: - Consul - Number of Warning Health Checks ### Plugins -- [`consul` plugin](/telegraf/latest/plugins/plugin-list/#consul) +- [`consul` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#consul) ## Consul Telemetry The Consul Telemetry dashboard displays the following information: @@ -125,7 +125,7 @@ The Consul Telemetry dashboard displays the following information: - Consul - Number of Serf Events ### Plugins -[`consul` plugin](/telegraf/latest/plugins/plugin-list/#consul) +[`consul` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#consul) ## Mesos @@ -140,7 +140,7 @@ The Mesos dashboard displays the following information: - Mesos Master Uptime ### Plugins -- [`mesos` plugin](/telegraf/latest/plugins/plugin-list/#mesos) +- [`mesos` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#mesos) ## RabbitMQ The RabbitMQ dashboard displays the following information: @@ -151,7 +151,7 @@ The RabbitMQ dashboard displays the following information: ### Plugins -- [`rabbitmq` plugin](/telegraf/latest/plugins/plugin-list/#rabbitmq) +- [`rabbitmq` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#rabbitmq) ## System @@ -170,14 +170,14 @@ The System dashboard displays the following information: ### Plugins -- [`system` plugin](/telegraf/latest/plugins/plugin-list/#system) -- [`mem` plugin](/telegraf/latest/plugins/plugin-list/#mem) -- [`cpu` plugin](/telegraf/latest/plugins/plugin-list/#cpu) -- [`disk` plugin](/telegraf/latest/plugins/plugin-list/#disk) -- [`diskio` plugin](/telegraf/latest/plugins/plugin-list/#diskio) -- [`net` plugin](/telegraf/latest/plugins/plugin-list/#net) -- [`processes` plugin](/telegraf/latest/plugins/plugin-list/#processes) -- [`swap` plugin](/telegraf/latest/plugins/plugin-list/#swap) +- [`system` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#system) +- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#mem) +- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#cpu) +- [`disk` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#disk) +- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#diskio) +- [`net` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#net) +- [`processes` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#processes) +- [`swap` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#swap) @@ -198,7 +198,7 @@ The VMware vSphere Overview dashboard gives an overview of your VMware vSphere C - VM CPU % Ready for :clustername: ### Plugins -- [`vsphere` plugin](/telegraf/latest/plugins/plugin-list/#vmware-vsphere) +- [`vsphere` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#vmware-vsphere) ## Apache The Apache dashboard displays the following information: @@ -221,12 +221,12 @@ The Apache dashboard displays the following information: ### Plugins -- [`apache` plugin](/telegraf/latest/plugins/plugin-list/#apache) -- [`system` plugin](/telegraf/latest/plugins/plugin-list/#system) -- [`mem` plugin](/telegraf/latest/plugins/plugin-list/#mem) -- [`diskio` plugin](/telegraf/latest/plugins/plugin-list/#diskio) -- [`net` plugin](/telegraf/latest/plugins/plugin-list/#net) -- [`logparser` plugin](/telegraf/latest/plugins/plugin-list/#logparser) +- [`apache` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#apache) +- [`system` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#system) +- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#mem) +- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#diskio) +- [`net` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#net) +- [`logparser` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#logparser) ## ElasticSearch The ElasticSearch dashboard displays the following information: @@ -243,7 +243,7 @@ The ElasticSearch dashboard displays the following information: - ElasticSearch - JVM Heap Usage ### Plugins -- [`elasticsearch` plugin](/telegraf/latest/plugins/plugin-list/#elasticsearch) +- [`elasticsearch` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#elasticsearch) ## InfluxDB @@ -272,12 +272,12 @@ The InfluxDB dashboard displays the following information: ### Plugins -- [`influxdb` plugin](/telegraf/latest/plugins/plugin-list/#influxdb) -- [`cpu` plugin](/telegraf/latest/plugins/plugin-list/#cpu) -- [`system` plugin](/telegraf/latest/plugins/plugin-list/#system) -- [`mem` plugin](/telegraf/latest/plugins/plugin-list/#mem) -- [`diskio` plugin](/telegraf/latest/plugins/plugin-list/#diskio) -- [`net` plugin](/telegraf/latest/plugins/plugin-list/#net) +- [`influxdb` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#influxdb) +- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#cpu) +- [`system` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#system) +- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#mem) +- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#diskio) +- [`net` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#net) @@ -299,7 +299,7 @@ The Memcached dashboard displays the following information: - Memcached - Evictions/10 Seconds ### Plugins -- [`memcached` plugin](/telegraf/latest/plugins/plugin-list/#memcached) +- [`memcached` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#memcached) ## NSQ @@ -315,7 +315,7 @@ The NSQ dashboard displays the following information: - NSQ - Topic Egress ### Plugins -- [`nsq` plugin](/telegraf/latest/plugins/plugin-list/#nsq) +- [`nsq` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#nsq) ## PostgreSQL The PostgreSQL dashboard displays the following information: @@ -340,11 +340,11 @@ The PostgreSQL dashboard displays the following information: ### Plugins -- [`postgresql` plugin](/telegraf/latest/plugins/plugin-list/#postgresql) -- [`system` plugin](/telegraf/latest/plugins/plugin-list/#system) -- [`mem` plugin](/telegraf/latest/plugins/plugin-list/#mem) -- [`cpu` plugin](/telegraf/latest/plugins/plugin-list/#cpu) -- [`diskio` plugin](/telegraf/latest/plugins/plugin-list/#diskio) +- [`postgresql` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#postgresql) +- [`system` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#system) +- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#mem) +- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#cpu) +- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#diskio) ## HAProxy @@ -367,7 +367,7 @@ The HAProxy dashboard displays the following information: - HAProxy - Backend Error Responses/Second ### Plugins -- [`haproxy` plugin](/telegraf/latest/plugins/plugin-list/#haproxy) +- [`haproxy` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#haproxy) ## NGINX @@ -379,7 +379,7 @@ The NGINX dashboard displays the following information: - NGINX - Active Client State ### Plugins -- [`nginx` plugin](/telegraf/latest/plugins/plugin-list/#nginx) +- [`nginx` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#nginx) ## Redis The Redis dashboard displays the following information: @@ -390,7 +390,7 @@ The Redis dashboard displays the following information: - Redis - Memory ### Plugins -- [`redis` plugin](/telegraf/latest/plugins/plugin-list/#redis) +- [`redis` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#redis) ## VMware vSphere VMs @@ -406,7 +406,7 @@ The VMWare vSphere VMs dashboard gives an overview of your VMware vSphere virtua - Total Disk Latency for :vmname: ### Plugins -- [`vsphere` plugin](/telegraf/latest/plugins/plugin-list/#vsphere) +- [`vsphere` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#vsphere) ## VMware vSphere Hosts @@ -422,7 +422,7 @@ The VMWare vSphere Hosts dashboard displays the following information: - Total Disk Latency for :esxhostname: ### Plugins -- [`vsphere` plugin](/telegraf/latest/plugins/plugin-list/#vsphere) +- [`vsphere` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#vsphere) ## PHPfpm The PHPfpm dashboard displays the following information: @@ -433,7 +433,7 @@ The PHPfpm dashboard displays the following information: - PHPfpm - Max Children Reached ### Plugins -- [`phpfpm` plugin](/telegraf/latest/plugins/plugin-list/#nginx) +- [`phpfpm` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#nginx) ## Win System The Win System dashboard displays the following information: @@ -445,7 +445,7 @@ The Win System dashboard displays the following information: - System - Load ### Plugins -- [`win_services` plugin](/telegraf/latest/plugins/plugin-list/#windows-services) +- [`win_services` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#windows-services) ## MySQL @@ -472,9 +472,9 @@ The MySQL dashboard displays the following information: - InnoDB Data ### Plugins -- [`mySQL` plugin](/telegraf/latest/plugins/plugin-list/#mysql) -- [`system` plugin](/telegraf/latest/plugins/plugin-list/#system) -- [`mem` plugin](/telegraf/latest/plugins/plugin-list/#mem) +- [`mySQL` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#mysql) +- [`system` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#system) +- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#mem) ## Ping The Ping dashboard displays the following information: @@ -483,4 +483,4 @@ The Ping dashboard displays the following information: - Ping - Response Times (ms) ### Plugins -- [`ping` plugin](/telegraf/latest/plugins/plugin-list/#ping) +- [`ping` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#ping) diff --git a/content/chronograf/v1.7/administration/transition-web-admin-interface.md b/content/chronograf/v1.7/administration/transition-web-admin-interface.md index 3d851f44d..ab9d9ba13 100644 --- a/content/chronograf/v1.7/administration/transition-web-admin-interface.md +++ b/content/chronograf/v1.7/administration/transition-web-admin-interface.md @@ -8,7 +8,7 @@ aliases: - /chronograf/v1.7/guides/transition-web-admin-interface/ --- -Versions 1.3 and later of [InfluxDB](/influxdb/latest/) and [InfluxEnterprise](/enterprise/latest/) do not support the web admin interface, the previous built-in user interface for writing and querying data in InfluxDB. +Versions 1.3 and later of [InfluxDB](/{{< latest "influxdb" "v1" >}}/) and [InfluxEnterprise](/enterprise/latest/) do not support the web admin interface, the previous built-in user interface for writing and querying data in InfluxDB. Chronograf replaces the web admin interface with improved tooling for querying data, writing data, and database management. The following sections describe the Chronograf features that relate to the web admin interface: @@ -23,7 +23,7 @@ The following sections describe the Chronograf features that relate to the web a ### Web admin interface In the web admin interface, users chose the target database in the top right corner and selected from a set of query templates in the `Query Templates` dropdown. -The templates included queries with no user-provided values (example: [`SHOW MEASUREMENTS`](/influxdb/latest/query_language/schema_exploration/#show-measurements)) and queries with user-provided values (example: [`SHOW TAG KEYS FROM ""`](/influxdb/latest/query_language/schema_exploration/#show-tag-keys)). +The templates included queries with no user-provided values (example: [`SHOW MEASUREMENTS`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-measurements)) and queries with user-provided values (example: [`SHOW TAG KEYS FROM ""`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-tag-keys)). ![WAI Query Templates](/img/chronograf/1-6-g-admin-webtemplates.png) @@ -39,7 +39,7 @@ Note that unlike the web admin interface, Chronograf does not have a database dr ### Web admin interface -To write data to InfluxDB, users selected the target database in the top right corner, clicked the `Write Data` icon, and entered their [line protocol](/influxdb/latest/concepts/glossary/#influxdb-line-protocol) in the text input: +To write data to InfluxDB, users selected the target database in the top right corner, clicked the `Write Data` icon, and entered their [line protocol](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#influxdb-line-protocol) in the text input: ![WAI Writing Data](/img/chronograf/1-6-g-admin-write.png) @@ -55,7 +55,7 @@ Next, enter your line protocol in the main text box and click the `Write` button ### Web admin interface -In the web admin interface, the `Query Template` dropdown was the only way to manage databases and [retention policies](/influxdb/latest/concepts/glossary/#retention-policy-rp) (RP): +In the web admin interface, the `Query Template` dropdown was the only way to manage databases and [retention policies](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#retention-policy-rp) (RP): ![WAI DBRP Management](/img/chronograf/1-6-g-admin-webdbrp.png) @@ -80,7 +80,7 @@ In the web admin interface, the `Query Template` dropdown was the only way to ma ### Chronograf In Chronograf, the `Admin` page includes a complete interface for user management. -The `Admin` page supports both InfluxDB OSS users and InfluxDB Enterprise users; see [Managing Chronograf Users](/chronograf/latest/administration/managing-chronograf-users/) page for more information. +The `Admin` page supports both InfluxDB OSS users and InfluxDB Enterprise users; see [Managing Chronograf Users](/{{< latest "chronograf" >}}/administration/managing-chronograf-users/) page for more information. The `Admin` page allows users to: * View, create, and delete users diff --git a/content/chronograf/v1.7/administration/upgrading.md b/content/chronograf/v1.7/administration/upgrading.md index 5b73c9c9d..ff9141d8a 100644 --- a/content/chronograf/v1.7/administration/upgrading.md +++ b/content/chronograf/v1.7/administration/upgrading.md @@ -24,4 +24,4 @@ Users can continue to use the deprecated product; documentation is available und For more information, please read the original [announcement blog](https://www.influxdata.com/announcing-the-new-chronograf-a-ui-for-the-tick-stack-and-a-complete-open-source-monitoring-solution/) by our CTO, Paul Dix. InfluxData recommends migrating to the open source Chronograf product. -See [Getting Started](/chronograf/latest/introduction/getting-started/) to get up and running! +See [Getting Started](/{{< latest "chronograf" >}}/introduction/getting-started/) to get up and running! diff --git a/content/chronograf/v1.7/guides/_index.md b/content/chronograf/v1.7/guides/_index.md index 10c596467..20a8bb473 100644 --- a/content/chronograf/v1.7/guides/_index.md +++ b/content/chronograf/v1.7/guides/_index.md @@ -22,7 +22,7 @@ Pre-created dashboards are available when the required Telegraf input plugins ar Using the TICKscript editor in Chronograf to create, test, and debug Kapacitor TICKscripts. -## [Creating dashboards](/chronograf/latest/guides/create-a-dashboard/) +## [Creating dashboards](/{{< latest "chronograf" >}}/guides/create-a-dashboard/) Chronograf offers a complete dashboard solution for visualizing your data and monitoring your infrastructure. Learn how to create customized dashboards in Chronograf. diff --git a/content/chronograf/v1.7/guides/advanced-kapacitor.md b/content/chronograf/v1.7/guides/advanced-kapacitor.md index 8e0a0413f..d20dbbac8 100644 --- a/content/chronograf/v1.7/guides/advanced-kapacitor.md +++ b/content/chronograf/v1.7/guides/advanced-kapacitor.md @@ -13,16 +13,16 @@ menu: * [TICKscript management](#tickscript-management) -Chronograf provides a user interface for [Kapacitor](/kapacitor/latest/), InfluxData's processing framework for creating alerts, running ETL jobs, and detecting anomalies in your data. +Chronograf provides a user interface for [Kapacitor](/{{< latest "kapacitor" >}}/), InfluxData's processing framework for creating alerts, running ETL jobs, and detecting anomalies in your data. This guide offers insights into how Kapacitor interacts with Chronograf and introduces advanced Kapacitor usage within Chronograf. ## Alert history management Chronograf stores the information on the Alert History page as time series data in InfluxDB. -It stores it in the `chronograf` database and in the `alerts` [measurement](/influxdb/latest/concepts/glossary/#measurement). -By default, this data is subject to an infinite [retention policy](/influxdb/latest/concepts/glossary/#retention-policy-rp) (RP), that is, InfluxDB stores them forever. -Users who expect to have a large number of alerts and users who do not want to store their alert history forever may want to shorten the [duration](/influxdb/latest/concepts/glossary/#duration) of that retention policy. +It stores it in the `chronograf` database and in the `alerts` [measurement](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#measurement). +By default, this data is subject to an infinite [retention policy](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#retention-policy-rp) (RP), that is, InfluxDB stores them forever. +Users who expect to have a large number of alerts and users who do not want to store their alert history forever may want to shorten the [duration](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#duration) of that retention policy. ### Modifying the retention policy in Chronograf @@ -36,7 +36,7 @@ In the Databases tab: #### Step 2: Enter a different duration The minimum allowable duration is one hour (`1h`) and the maximum is infinite (`INF`). -See the InfluxDB documentation for the list of [acceptable duration units](/influxdb/latest/query_language/spec/#duration-units). +See the InfluxDB documentation for the list of [acceptable duration units](/{{< latest "influxdb" "v1" >}}/query_language/spec/#duration-units). #### Step 3: Click the green check mark to save your changes @@ -56,7 +56,7 @@ The fourth alert, which occurred on the same day at 16:58:50, is outside the pre Chronograf creates Kapacitor tasks using the information that you provide on the Rule Configuration page. It uses that information to communicate with Kapacitor and populate Chronograf alert pages. -Pre-existing tasks, or [TICKscripts](/kapacitor/latest/tick/), that you created and enabled on your Kapacitor instance without using Chronograf, have limited functionality in the user interface. +Pre-existing tasks, or [TICKscripts](/{{< latest "kapacitor" >}}/tick/), that you created and enabled on your Kapacitor instance without using Chronograf, have limited functionality in the user interface. In Chronograf, you can: diff --git a/content/chronograf/v1.7/guides/analyzing-logs.md b/content/chronograf/v1.7/guides/analyzing-logs.md index af4dbc67b..3f7354a77 100644 --- a/content/chronograf/v1.7/guides/analyzing-logs.md +++ b/content/chronograf/v1.7/guides/analyzing-logs.md @@ -11,7 +11,7 @@ Chronograf gives you the ability to view, search, filter, visualize, and analyze This helps to recognize and diagnose patterns, then quickly dive into logged events that lead up to events. ## Logging setup -Logs data is a first class citizen in InfluxDB and is populated using available log-related [Telegraf input plugins](/telegraf/latest/plugins/inputs/): +Logs data is a first class citizen in InfluxDB and is populated using available log-related [Telegraf input plugins](/{{< latest "telegraf" >}}/plugins/inputs/): [syslog](https://github.com/influxdata/telegraf/tree/release-1.7/plugins/inputs/syslog) diff --git a/content/chronograf/v1.7/guides/configuring-alert-endpoints.md b/content/chronograf/v1.7/guides/configuring-alert-endpoints.md index df7169a41..26f3d88bf 100644 --- a/content/chronograf/v1.7/guides/configuring-alert-endpoints.md +++ b/content/chronograf/v1.7/guides/configuring-alert-endpoints.md @@ -17,7 +17,7 @@ This guide offers step-by-step instructions for configuring Chronograf alert end ## Kapacitor event handlers supported in Chronograf -Chronograf integrates with [Kapacitor](/kapacitor/latest/), InfluxData's data processing platform, to send alert messages to event handlers. +Chronograf integrates with [Kapacitor](/{{< latest "kapacitor" >}}/), InfluxData's data processing platform, to send alert messages to event handlers. Chronograf supports the following event handlers: * Alerta @@ -39,7 +39,7 @@ Chronograf supports the following event handlers: * TCP * VictorOps -To configure a Kapacitor event handler in Chronograf, [install Kapacitor](/kapacitor/latest/introduction/installation/) and [connect it to Chronograf](/kapacitor/latest/working/kapa-and-chrono/#add-a-kapacitor-instance). +To configure a Kapacitor event handler in Chronograf, [install Kapacitor](/{{< latest "kapacitor" >}}/introduction/installation/) and [connect it to Chronograf](/{{< latest "kapacitor" >}}/working/kapa-and-chrono/#add-a-kapacitor-instance). The **Configure Kapacitor** page includes the event handler configuration options. @@ -47,10 +47,10 @@ The **Configure Kapacitor** page includes the event handler configuration option Alert endpoint configurations appear on the Chronograf Configure Kapacitor page. You must have a connected Kapacitor instance to access the configurations. -For more information, see [Kapacitor installation instructions](/kapacitor/latest/introduction/installation/) and how to [connect a Kapacitor instance](/kapacitor/latest/working/kapa-and-chrono/#add-a-kapacitor-instance) to Chronograf. +For more information, see [Kapacitor installation instructions](/{{< latest "kapacitor" >}}/introduction/installation/) and how to [connect a Kapacitor instance](/{{< latest "kapacitor" >}}/working/kapa-and-chrono/#add-a-kapacitor-instance) to Chronograf. Note that the configuration options in the **Configure alert endpoints** section are not all-inclusive. -Some event handlers allow users to customize event handler configurations per [alert rule](/chronograf/latest/guides/create-a-kapacitor-alert/). +Some event handlers allow users to customize event handler configurations per [alert rule](/{{< latest "chronograf" >}}/guides/create-a-kapacitor-alert/). For example, Chronograf's Slack integration allows users to specify a default channel in the **Configure alert endpoints** section and a different channel for individual alert rules. ### HipChat @@ -87,7 +87,7 @@ The following steps describe how to create the API access token: Your token appears in the table just above the **Create new token** section: -![HipChat token](/img/chronograf/latest/g-eventhandlers-hipchattoken.png) +![HipChat token](/img/{{< latest "chronograf" >}}/g-eventhandlers-hipchattoken.png) ### Kafka @@ -112,7 +112,7 @@ Your token appears in the table just above the **Create new token** section: 3. Click **Save Changes** to save the configuration settings. 4. Click **Send Test Alert** to verify the configuration. -See [Kafka event handler (Kapacitor)](/kapacitor/latest/event_handlers/kafka/) in the Kapacitor documentation for details about enabling OpsGenie services using TICKscripts. +See [Kafka event handler (Kapacitor)](/{{< latest "kapacitor" >}}/event_handlers/kafka/) in the Kapacitor documentation for details about enabling OpsGenie services using TICKscripts. ### OpsGenie @@ -139,9 +139,9 @@ Send an incident alert to OpsGenie teams and recipients using the Chronograf ale See [Alert API](https://docs.opsgenie.com/docs/alert-api) in the OpsGenie documentation for details on the OpsGenie Alert API -See [OpsGenie V2 event handler](/kapacitor/latest/event_handlers/opsgenie/v2/) in the Kapacitor documentation for details about the OpsGenie V2 event handler. +See [OpsGenie V2 event handler](/{{< latest "kapacitor" >}}/event_handlers/opsgenie/v2/) in the Kapacitor documentation for details about the OpsGenie V2 event handler. -See the [AlertNode (Kapacitor TICKscript node) - OpsGenie v2](/kapacitor/latest/nodes/alert_node/#opsgenie-v2) in the Kapacitor documentation for details about enabling OpsGenie services using TICKscripts. +See the [AlertNode (Kapacitor TICKscript node) - OpsGenie v2](/{{< latest "kapacitor" >}}/nodes/alert_node/#opsgenie-v2) in the Kapacitor documentation for details about enabling OpsGenie services using TICKscripts. ### PagerDuty @@ -165,7 +165,7 @@ Send an alerts about recognized events to PagerDuty using the Chronograf PagerDu See the [PagerDuty Events API V2 Overview](https://v2.developer.pagerduty.com/docs/events-api-v2) for details on the PagerDuty Events API and recognized event types (`trigger`, `acknowledge`, and `resolve`). -See [AlertNode (Kapacitor TICKscript node) - PagerDuty v2](/kapacitor/latest/nodes/alert_node/#pagerduty-v2) in the Kapacitor documentation for details about enabling a new "Generic API" service using TICKscripts. +See [AlertNode (Kapacitor TICKscript node) - PagerDuty v2](/{{< latest "kapacitor" >}}/nodes/alert_node/#pagerduty-v2) in the Kapacitor documentation for details about enabling a new "Generic API" service using TICKscripts. ### Pushover diff --git a/content/chronograf/v1.7/guides/create-a-dashboard.md b/content/chronograf/v1.7/guides/create-a-dashboard.md index 915541ec7..c6e0f8f46 100644 --- a/content/chronograf/v1.7/guides/create-a-dashboard.md +++ b/content/chronograf/v1.7/guides/create-a-dashboard.md @@ -10,7 +10,7 @@ menu: Chronograf offers a complete dashboard solution for visualizing your data and monitoring your infrastructure: -* View [pre-created dashboards](/chronograf/latest/guides/using-precreated-dashboards) from the Host List page. Dashboards are available depending on which Telegraf input plugins you have enabled. These pre-created dashboards cannot be cloned or edited. +* View [pre-created dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards) from the Host List page. Dashboards are available depending on which Telegraf input plugins you have enabled. These pre-created dashboards cannot be cloned or edited. * Create custom dashboards from scratch by building queries in the Data Explorer, as described [below](#build-a-dashboard). * Import dashboard templates when you add or update a connection in Chronograf. See [Dashboard templates](#dashboard-templates) for details. @@ -23,7 +23,7 @@ By the end of this guide, you'll be aware of the tools available to you for crea To perform the tasks in this guide, you must have a working Chronograf instance that is connected to an InfluxDB source. Data is accessed using the Telegraf [system ](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/system) input plugins. -For more information, see [Configuring Chronograf](/chronograf/latest/administration/configuration). +For more information, see [Configuring Chronograf](/{{< latest "chronograf" >}}/administration/configuration). ## Build a Dashboard @@ -43,13 +43,13 @@ to open the cell editor mode. ### Step 3: Create your query -Click the **Add a Query** button to create an [InfluxQL](/influxdb/latest/query_language/) query. +Click the **Add a Query** button to create an [InfluxQL](/{{< latest "influxdb" "v1" >}}/query_language/) query. In query editor mode, use the builder to select from your existing data and allow Chronograf to format the query for you. Alternatively, manually enter and edit a query. Chronograf allows you to move seamlessly between using the builder and manually editing the query; when possible, the interface automatically populates the builder with the information from your raw query. For our example, the query builder is used to generate a query that shows the average idle CPU usage grouped by host (in this case, there are three hosts). -By default, Chronograf applies the [`MEAN()` function](/influxdb/latest/query_language/functions/#mean) to the data, groups averages into auto-generated time intervals (`:interval:`), and shows data for the past hour (`:dashboardTime:`). +By default, Chronograf applies the [`MEAN()` function](/{{< latest "influxdb" "v1" >}}/query_language/functions/#mean) to the data, groups averages into auto-generated time intervals (`:interval:`), and shows data for the past hour (`:dashboardTime:`). Those defaults are configurable using the query builder or by manually editing the query. In addition, the time range (`:dashboardTime:`) is [configurable on the dashboard](#step-6-configure-your-dashboard). @@ -58,7 +58,7 @@ In addition, the time range (`:dashboardTime:`) is [configurable on the dashboar ### Step 4: Choose your visualization type -Chronograf supports many different [visualization types](/chronograf/latest/guides/visualization-types/). To choose a visualization type, click **Visualization** and select **Step-Plot Graph**. +Chronograf supports many different [visualization types](/{{< latest "chronograf" >}}/guides/visualization-types/). To choose a visualization type, click **Visualization** and select **Step-Plot Graph**. ![Visualization type](/img/chronograf/1-6-g-dashboard-visualization.png) @@ -80,7 +80,7 @@ Click **Save** (the green checkmark icon) to save your cell. * **Reset** your cell by double-clicking your mouse in the cell window > **Note:** - These tips only apply to the line, stacked, step-plot, and line+stat [visualization types](/chronograf/latest/guides/visualization-types/). + These tips only apply to the line, stacked, step-plot, and line+stat [visualization types](/{{< latest "chronograf" >}}/guides/visualization-types/). #### Configure dashboard-wide settings: * Change the dashboard's *selected time* at the top of the page - the default time is **Local**, which uses your browser's local time. Select **UTC** to use Coordinated Universal Time. @@ -119,4 +119,4 @@ To exit full screen mode, press the Esc key. ### Template variables Dashboards support template variables. -See the [Dashboard Template Variables](/chronograf/latest/guides/dashboard-template-variables/) guide for more information. +See the [Dashboard Template Variables](/{{< latest "chronograf" >}}/guides/dashboard-template-variables/) guide for more information. diff --git a/content/chronograf/v1.7/guides/create-alert-rules.md b/content/chronograf/v1.7/guides/create-alert-rules.md index bf517385a..219fa132f 100644 --- a/content/chronograf/v1.7/guides/create-alert-rules.md +++ b/content/chronograf/v1.7/guides/create-alert-rules.md @@ -11,9 +11,9 @@ menu: --- -Chronograf provides a user interface for [Kapacitor](/kapacitor/latest/), InfluxData's processing framework for creating alerts, ETL jobs (running extract, transform, load), and detecting anomalies in your data. +Chronograf provides a user interface for [Kapacitor](/{{< latest "kapacitor" >}}/), InfluxData's processing framework for creating alerts, ETL jobs (running extract, transform, load), and detecting anomalies in your data. Chronograf alert rules correspond to Kapacitor tasks that trigger alerts whenever certain conditions are met. -Behind the scenes, these tasks are stored as [TICKscripts](/kapacitor/latest/tick/) that can be edited manually or through Chronograf. +Behind the scenes, these tasks are stored as [TICKscripts](/{{< latest "kapacitor" >}}/tick/) that can be edited manually or through Chronograf. Common alerting use cases that can be managed using Chronograf include: * Thresholds with static ceilings, floors, and ranges. @@ -26,13 +26,13 @@ This guide walks through creating a Chronograf alert rule that sends an alert me ## Requirements -[Getting started with Chronograf](/chronograf/latest/introduction/getting-started/) offers step-by-step instructions for each of the following requirements: +[Getting started with Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/) offers step-by-step instructions for each of the following requirements: * Downloaded and install the entire TICKstack (Telegraf, InfluxDB, Chronograf, and Kapacitor). * Configure Telegraf to collect data using the InfluxDB [system statistics](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/system) input plugin and write data to your InfluxDB instance. -* [Create a Kapacitor connection in Chronograf](/chronograf/latest/introduction/getting-started/#4-connect-chronograf-to-kapacitor). -* Slack is available and configured as an [event handler](/chronograf/latest/troubleshooting/frequently-asked-questions/#what-kapacitor-event-handlers-are-supported-in-chronograf) in Chronograf. -See the [Configuring Kapacitor Event Handlers](/chronograf/latest/guides/configuring-alert-endpoints/) guide for detailed configuration instructions. +* [Create a Kapacitor connection in Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/#4-connect-chronograf-to-kapacitor). +* Slack is available and configured as an [event handler](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#what-kapacitor-event-handlers-are-supported-in-chronograf) in Chronograf. +See the [Configuring Kapacitor Event Handlers](/{{< latest "chronograf" >}}/guides/configuring-alert-endpoints/) guide for detailed configuration instructions. ## Configuring Chronograf alert rules @@ -70,7 +70,7 @@ For this example, select the **Threshold** alert type. Choose the time series data you want the Chronograf alert rule to use. Navigate through databases, measurements, fields, and tags to select the relevant data. -In this example, select the `telegraf` [database](/influxdb/latest/concepts/glossary/#database), the `autogen` [retention policy](/influxdb/latest/concepts/glossary/#retention-policy-rp), the `cpu` [measurement](/influxdb/latest/concepts/glossary/#measurement), and the `usage_idle` [field](/influxdb/latest/concepts/glossary/#field). +In this example, select the `telegraf` [database](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#database), the `autogen` [retention policy](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#retention-policy-rp), the `cpu` [measurement](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#measurement), and the `usage_idle` [field](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#field). ![Select your data](/img/chronograf/1-6-alerts-time-series.png) @@ -113,7 +113,7 @@ In this example, use the alert message, `Your idle CPU usage is {{.Level}} at {{ ![Specify event handler and alert message](/img/chronograf/1-6-alerts-message.png) -*View the Kapacitor documentation for more information about [message template data](/kapacitor/latest/nodes/alert_node/#message).* +*View the Kapacitor documentation for more information about [message template data](/{{< latest "kapacitor" >}}/nodes/alert_node/#message).* ### Step 7: Save the alert rule diff --git a/content/chronograf/v1.7/guides/dashboard-template-variables.md b/content/chronograf/v1.7/guides/dashboard-template-variables.md index 283efe99d..71656590b 100644 --- a/content/chronograf/v1.7/guides/dashboard-template-variables.md +++ b/content/chronograf/v1.7/guides/dashboard-template-variables.md @@ -115,7 +115,7 @@ Chronograf supports the following template variable types: [Text](#text) ### Databases -Database template variables allow you to select from multiple target [databases](/influxdb/latest/concepts/glossary/#database). +Database template variables allow you to select from multiple target [databases](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#database). _**Database meta query**_ Database template variables use the following meta query to return an array of all databases in your InfluxDB instance. @@ -133,7 +133,7 @@ SELECT "purchases" FROM :databaseVar:."autogen"."customers" Database template variables are good when visualizing multiple databases with similar or identical data structures. They allow you to quickly switch between visualizations for each of your databases. ### Measurements -Vary the target [measurement](/influxdb/latest/concepts/glossary/#measurement). +Vary the target [measurement](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#measurement). _**Measurement meta query**_ Measurement template variables use the following meta query to return an array of all measurements in a given database. @@ -152,7 +152,7 @@ Measurement template variables allow you to quickly switch between measurements ### Field Keys -Vary the target [field key](/influxdb/latest/concepts/glossary/#field-key). +Vary the target [field key](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#field-key). _**Field key meta query**_ Field key template variables use the following meta query to return an array of all field keys in a given measurement from a given database. @@ -171,7 +171,7 @@ Field key template variables are great if you want to quickly switch between fie ### Tag Keys -Vary the target [tag key](/influxdb/latest/concepts/glossary/#tag-key). +Vary the target [tag key](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-key). _**Tag key meta query**_ Tag key template variables use the following meta query to return an array of all tag keys in a given measurement from a given database. @@ -190,7 +190,7 @@ Tag key template variables are great if you want to quickly switch between tag k ### Tag Values -Vary the target [tag value](/influxdb/latest/concepts/glossary/#tag-value). +Vary the target [tag value](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-value). _**Tag value meta query**_ Tag value template variables use the following meta query to return an array of all values associated with a given tag key in a specified measurement and database. @@ -222,7 +222,7 @@ value3 value4 ``` -> Since string field values [require single quotes in InfluxQL](/influxdb/latest/troubleshooting/frequently-asked-questions/#when-should-i-single-quote-and-when-should-i-double-quote-in-queries), string values should be wrapped in single quotes. +> Since string field values [require single quotes in InfluxQL](/{{< latest "influxdb" "v1" >}}/troubleshooting/frequently-asked-questions/#when-should-i-single-quote-and-when-should-i-double-quote-in-queries), string values should be wrapped in single quotes. >```csv 'string1','string2','string3','string4' @@ -253,7 +253,7 @@ key4,value4 Map variable dropdown -> If values are meant to be used as string field values, wrap them in single quote ([required by InfluxQL](/influxdb/latest/troubleshooting/frequently-asked-questions/#when-should-i-single-quote-and-when-should-i-double-quote-in-queries)). This only pertains to values. String keys do not matter. +> If values are meant to be used as string field values, wrap them in single quote ([required by InfluxQL](/{{< latest "influxdb" "v1" >}}/troubleshooting/frequently-asked-questions/#when-should-i-single-quote-and-when-should-i-double-quote-in-queries)). This only pertains to values. String keys do not matter. >```csv key1,'value1' diff --git a/content/chronograf/v1.7/guides/live_leaderboard.md b/content/chronograf/v1.7/guides/live_leaderboard.md index 6b1f87bf5..fea4ba8f6 100644 --- a/content/chronograf/v1.7/guides/live_leaderboard.md +++ b/content/chronograf/v1.7/guides/live_leaderboard.md @@ -40,7 +40,7 @@ Add the following settings the `[[udp]]` secton in your Kapacitor configuration retention-policy = "autogen" ``` -Using this configuration, Kapacitor will listen on port `9100` for UDP packets in [Line Protocol](/influxdb/latest/write_protocols/line_protocol_tutorial/) format. +Using this configuration, Kapacitor will listen on port `9100` for UDP packets in [Line Protocol](/{{< latest "influxdb" "v1" >}}/write_protocols/line_protocol_tutorial/) format. Incoming data will be scoped to be in the `game.autogen` database and retention policy. Restart Kapacitor so that the UDP listener service starts. diff --git a/content/chronograf/v1.7/guides/monitoring-influxenterprise-clusters.md b/content/chronograf/v1.7/guides/monitoring-influxenterprise-clusters.md index 991eff573..6712b1198 100644 --- a/content/chronograf/v1.7/guides/monitoring-influxenterprise-clusters.md +++ b/content/chronograf/v1.7/guides/monitoring-influxenterprise-clusters.md @@ -10,20 +10,20 @@ menu: --- -[InfluxEnterprise](/enterprise_influxdb/latest/) offers high availability and a highly scalable clustering solution for your time series data needs. +[InfluxEnterprise](/{{< latest "enterprise_influxdb" >}}/) offers high availability and a highly scalable clustering solution for your time series data needs. Use Chronograf to assess your cluster's health and to monitor the infrastructure behind your project. -This guide offers step-by-step instructions for using Chronograf, [InfluxDB](/influxdb/latest/), and [Telegraf](/telegraf/latest/) to monitor data nodes in your InfluxEnterprise cluster. +This guide offers step-by-step instructions for using Chronograf, [InfluxDB](/{{< latest "influxdb" "v1" >}}/), and [Telegraf](/{{< latest "telegraf" >}}/) to monitor data nodes in your InfluxEnterprise cluster. ## Requirements You have a fully-functioning InfluxEnterprise cluster with authentication enabled. See the InfluxEnterprise documentation for -[detailed setup instructions](/enterprise_influxdb/latest/production_installation/). +[detailed setup instructions](/{{< latest "enterprise_influxdb" >}}/production_installation/). This guide uses an InfluxData Enterprise cluster with three meta nodes and three data nodes; the steps are also applicable to other cluster configurations. InfluxData recommends using a separate server to store your monitoring data. -It is possible to store the monitoring data in your cluster and [connect the cluster to Chronograf](/chronograf/latest/troubleshooting/frequently-asked-questions/#how-do-i-connect-chronograf-to-an-influxenterprise-cluster), but, in general, your monitoring data should live on a separate server. +It is possible to store the monitoring data in your cluster and [connect the cluster to Chronograf](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#how-do-i-connect-chronograf-to-an-influxenterprise-cluster), but, in general, your monitoring data should live on a separate server. You're working on an Ubuntu installation. Chronograf and the other components of the TICK stack are supported on several operating systems and hardware architectures. Check out the [downloads page](https://portal.influxdata.com/downloads) for links to the binaries of your choice. @@ -35,11 +35,11 @@ Before we begin, here's an overview of the final monitoring setup: ![Architecture diagram](/img/chronograf/1-6-cluster-diagram.png) The diagram above shows an InfluxEnterprise cluster that consists of three meta nodes (M) and three data nodes (D). -Each data node has its own [Telegraf](/telegraf/latest/) instance (T). +Each data node has its own [Telegraf](/{{< latest "telegraf" >}}/) instance (T). Each Telegraf instance is configured to collect node CPU, disk, and memory data using the Telegraf [system stats](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/system) input plugin. -The Telegraf instances are also configured to send those data to a single [InfluxDB OSS](/influxdb/latest/) instance that lives on a separate server. -When Telegraf sends data to InfluxDB, it automatically [tags](/influxdb/latest/concepts/glossary/#tag) the data with the hostname of the relevant data node. +The Telegraf instances are also configured to send those data to a single [InfluxDB OSS](/{{< latest "influxdb" "v1" >}}/) instance that lives on a separate server. +When Telegraf sends data to InfluxDB, it automatically [tags](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag) the data with the hostname of the relevant data node. The InfluxDB OSS instance that stores the Telegraf data is connected to Chronograf. Chronograf uses the hostnames in the Telegraf data to populate the Host List page and provide other hostname-specific information in the user interface. @@ -54,7 +54,7 @@ InfluxDB can be downloaded from the [InfluxData downloads page](https://portal.i #### Step 2: Enable authentication -For security purposes, enable authentication in the InfluxDB [configuration file (influxdb.conf)](/influxdb/latest/administration/config/), which is located in `/etc/influxdb/influxdb.conf`. +For security purposes, enable authentication in the InfluxDB [configuration file (influxdb.conf)](/{{< latest "influxdb" "v1" >}}/administration/config/), which is located in `/etc/influxdb/influxdb.conf`. In the `[http]` section of the configuration file, uncomment the `auth-enabled` option and set it to `true`: @@ -80,7 +80,7 @@ Next, start the InfluxDB process: #### Step 4: Create an admin user -Create an [admin user](/influxdb/latest/query_language/authentication_and_authorization/#user-types-and-privileges) on your InfluxDB instance. +Create an [admin user](/{{< latest "influxdb" "v1" >}}/query_language/authentication_and_authorization/#user-types-and-privileges) on your InfluxDB instance. Because you enabled authentication, you must perform this step before moving on to the next section. Run the command below to create an admin user, replacing `chronothan` and `supersecret` with your own username and password. Note that the password requires single quotes. @@ -178,7 +178,7 @@ Replace the `chronothan` and `supersecret` values with your actual username and ``` The expected output is similar to the JSON in the codeblock below. -In this case, the `telegraf` database has three different [tag values](/influxdb/latest/concepts/glossary/#tag-value) for the `host` [tag key](/influxdb/latest/concepts/glossary/#tag-key): `data-node-01`, `data-node-02`, and `data-node-03`. +In this case, the `telegraf` database has three different [tag values](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-value) for the `host` [tag key](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-key): `data-node-01`, `data-node-02`, and `data-node-03`. Those values match the hostnames of the three data nodes in the cluster; this means Telegraf is successfully writing monitoring data from those hosts to the InfluxDB OSS instance! ``` { @@ -258,6 +258,6 @@ In the image below, the Chronograf query editor is used to visualize the idle CP ![Data Explorer](/img/chronograf/1-6-cluster-de.png) Create more customized graphs and save them to a dashboard on the Dashboard page in Chronograf. -See the [Creating Chronograf dashboards](/chronograf/latest/guides/create-a-dashboard/) guide for more information. +See the [Creating Chronograf dashboards](/{{< latest "chronograf" >}}/guides/create-a-dashboard/) guide for more information. That's it! You've successfully configured Telegraf to collect and write data, InfluxDB to store those data, and Chonograf to use those data for monitoring and visualization purposes. diff --git a/content/chronograf/v1.7/guides/querying-data.md b/content/chronograf/v1.7/guides/querying-data.md index c4e73200f..cc22f8a98 100644 --- a/content/chronograf/v1.7/guides/querying-data.md +++ b/content/chronograf/v1.7/guides/querying-data.md @@ -7,7 +7,7 @@ menu: weight: 130 parent: Guides --- -Explore and visualize your data in the **Data Explorer**. For both InfluxQL and Flux, Chronograf allows you to move seamlessly between using the builder or templates and manually editing the query; when possible, the interface automatically populates the builder with the information from your raw query. Choose between [visualization types](/chronograf/latest/guides/visualization-types/) for your query. +Explore and visualize your data in the **Data Explorer**. For both InfluxQL and Flux, Chronograf allows you to move seamlessly between using the builder or templates and manually editing the query; when possible, the interface automatically populates the builder with the information from your raw query. Choose between [visualization types](/{{< latest "chronograf" >}}/guides/visualization-types/) for your query. To open the **Data Explorer**, click the **Explore** icon in the navigation bar: @@ -23,7 +23,7 @@ To open the **Data Explorer**, click the **Explore** icon in the navigation bar: ## Explore data with InfluxQL -InfluxQL is a SQL-like query language you can use to interact with data in InfluxDB. For detailed tutorials and reference material, see our [InfluxQL documentation](/influxdb/latest/query_language/). +InfluxQL is a SQL-like query language you can use to interact with data in InfluxDB. For detailed tutorials and reference material, see our [InfluxQL documentation](/{{< latest "influxdb" "v1" >}}/query_language/). 1. Open the Data Explorer and click **Add a Query**. 2. To the right of the source dropdown above the graph placeholder, select **InfluxQL** as the source type. @@ -66,7 +66,7 @@ Flux is InfluxData's new functional data scripting language designed for queryin ## Visualize your query -Select the **Visualization** tab at the top of the **Data Explorer**. For details about all of the available visualization options, see [Visualization types in Chronograf](/chronograf/latest/guides/visualization-types/). +Select the **Visualization** tab at the top of the **Data Explorer**. For details about all of the available visualization options, see [Visualization types in Chronograf](/{{< latest "chronograf" >}}/guides/visualization-types/). ## Add queries to dashboards diff --git a/content/chronograf/v1.7/guides/using-precreated-dashboards.md b/content/chronograf/v1.7/guides/using-precreated-dashboards.md index b36a8973b..c8e1fbf9c 100644 --- a/content/chronograf/v1.7/guides/using-precreated-dashboards.md +++ b/content/chronograf/v1.7/guides/using-precreated-dashboards.md @@ -13,7 +13,7 @@ menu: Pre-created dashboards are delivered with Chronograf depending on which Telegraf input plugins you have enabled and are available from the Host List page. These dashboards, which are built in and not editable, include cells with data visualizations for metrics that are relevant to data sources you are likely to be using. -> Note that these pre-created dashboards cannot be cloned or customized. They appear only as part of the Host List view and are associated with metrics gathered from a single host. Dashboard templates are also available and deliver a solid starting point for customizing your own unique dashboards based on the Telegraf plugins enabled and operate across one or more hosts. For details, see [Dashboard templates](/chronograf/latest/guides/create-a-dashboard/#dashboard-templates). +> Note that these pre-created dashboards cannot be cloned or customized. They appear only as part of the Host List view and are associated with metrics gathered from a single host. Dashboard templates are also available and deliver a solid starting point for customizing your own unique dashboards based on the Telegraf plugins enabled and operate across one or more hosts. For details, see [Dashboard templates](/{{< latest "chronograf" >}}/guides/create-a-dashboard/#dashboard-templates). ## Requirements @@ -33,7 +33,7 @@ Pre-created dashboards are delivered in Chronograf installations and are ready t The pre-created dashboards available for use with Chronograf are listed below as Apps and appear in the Apps listing for hosts in the Host List page. The listings for apps (pre-created dashboards) on this page include information about the required Telegraf input plugins, JSON files included in the apps, and listings of the cell titles that are included in each of the JSON files. -The JSON files for the precreated dashboards are delivered on installation in the `/usr/share/chronograf/canned` directory. Information about the configuration option `--canned-path` can be found in the [Chronograf configuration options](/chronograf/latest/administration/config-options/#) page. +The JSON files for the precreated dashboards are delivered on installation in the `/usr/share/chronograf/canned` directory. Information about the configuration option `--canned-path` can be found in the [Chronograf configuration options](/{{< latest "chronograf" >}}/administration/config-options/#) page. You can enable and disable applications in your [Telegraf configuration file](https://github.com/influxdata/telegraf/blob/master/etc/telegraf.conf). See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/docs/CONFIGURATION.md) for details. @@ -65,7 +65,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/ ## apache -**Required Telegraf plugin:** [Apache input plugin](/telegraf/latest/plugins/inputs/#apache-http-server) +**Required Telegraf plugin:** [Apache input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#apache-http-server) `apache.json` @@ -75,7 +75,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/ ## consul -**Required Telegraf plugin:** [Consul input plugin](/telegraf/latest/plugins/inputs/#consul) +**Required Telegraf plugin:** [Consul input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#consul) `consul_http.json` @@ -95,7 +95,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/ ## docker -**Required Telegraf plugin:** [Docker input plugin](/telegraf/latest/plugins/inputs/#docker) +**Required Telegraf plugin:** [Docker input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#docker) `docker.json` @@ -115,7 +115,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/ ## elasticsearch -**Required Telegraf plugin:** [Elasticsearch input plugin](/telegraf/latest/plugins/inputs/#elasticsearch) +**Required Telegraf plugin:** [Elasticsearch input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#elasticsearch) `elasticsearch.json` @@ -132,7 +132,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/ ## haproxy -**Required Telegraf plugin:** [HAProxy input plugin](/telegraf/latest/plugins/inputs/#haproxy) +**Required Telegraf plugin:** [HAProxy input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#haproxy) `haproxy.json` @@ -162,7 +162,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/ ## influxdb -**Required Telegraf plugin:** [InfluxDB input plugin](/telegraf/latest/plugins/inputs/#influxdb-v-1) +**Required Telegraf plugin:** [InfluxDB input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#influxdb-v-1) `influxdb_database.json` @@ -207,7 +207,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/ ## Memcached (`memcached`) -**Required Telegraf plugin:** [Memcached input plugin](/telegraf/latest/plugins/inputs/#memcached) +**Required Telegraf plugin:** [Memcached input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#memcached) `memcached.json` @@ -227,7 +227,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/ ## mesos -**Required Telegraf plugin:** [Mesos input plugin](/telegraf/latest/plugins/inputs/#mesos) +**Required Telegraf plugin:** [Mesos input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#mesos) `mesos.json` @@ -242,7 +242,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/ ## mongodb -**Required Telegraf plugin:** [MongoDB input plugin](/telegraf/latest/plugins/inputs/#mongodb) +**Required Telegraf plugin:** [MongoDB input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#mongodb) `mongodb.json` @@ -254,7 +254,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/ ## mysql -**Required Telegraf plugin:** [MySQL input plugin](/telegraf/latest/plugins/inputs/#mysql) +**Required Telegraf plugin:** [MySQL input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#mysql) `mysql.json` @@ -265,7 +265,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/ ## nginx -**Required Telegraf plugin:** [NGINX input plugin](/telegraf/latest/plugins/inputs/#nginx) +**Required Telegraf plugin:** [NGINX input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#nginx) `nginx.json` @@ -276,7 +276,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/ ## nsq -**Required Telegraf plugin:** [NSQ input plugin](/telegraf/latest/plugins/inputs/#nsq) +**Required Telegraf plugin:** [NSQ input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#nsq) `nsq_channel.json` @@ -297,7 +297,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/ ## phpfpm -**Required Telegraf plugin:** [PHPfpm input plugin](/telegraf/latest/plugins/inputs/#php-fpm) +**Required Telegraf plugin:** [PHPfpm input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#php-fpm) `phpfpm.json` @@ -309,7 +309,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/ ## ping -**Required Telegraf plugin:** [Ping input plugin](/telegraf/latest/plugins/inputs/#ping) +**Required Telegraf plugin:** [Ping input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#ping) `ping.json` @@ -318,7 +318,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/ ## postgresql -**Required Telegraf plugin:** [PostgreSQL input plugin](/telegraf/latest/plugins/inputs/#postgresql) +**Required Telegraf plugin:** [PostgreSQL input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#postgresql) `postgresql.json` @@ -329,7 +329,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/ ## rabbitmq -**Required Telegraf plugin:** [RabbitMQ input plugin](/telegraf/latest/plugins/inputs/#rabbitmq) +**Required Telegraf plugin:** [RabbitMQ input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#rabbitmq) `rabbitmq.json` @@ -340,7 +340,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/ ## redis -**Required Telegraf plugin:** [Redis input plugin](/telegraf/latest/plugins/inputs/#redis) +**Required Telegraf plugin:** [Redis input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#redis) `redis.json` @@ -352,7 +352,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/ ## riak -**Required Telegraf plugin:** [Riak input plugin](/telegraf/latest/plugins/inputs/#riak) +**Required Telegraf plugin:** [Riak input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#riak) `riak.json` @@ -371,7 +371,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/ ### cpu -**Required Telegraf plugin:** [CPU input plugin](/telegraf/latest/plugins/inputs/#cpu) +**Required Telegraf plugin:** [CPU input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#cpu) `cpu.json` @@ -381,13 +381,13 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/ `disk.json` -**Required Telegraf plugin:** [Disk input plugin](/telegraf/latest/plugins/inputs/#disk) +**Required Telegraf plugin:** [Disk input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#disk) * "System - Disk used %" ### diskio -**Required Telegraf plugin:** [DiskIO input plugin](/telegraf/latest/plugins/inputs/#diskio) +**Required Telegraf plugin:** [DiskIO input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#diskio) `diskio.json` @@ -396,7 +396,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/ ### mem -**Required Telegraf plugin:** [Mem input plugin](/telegraf/latest/plugins/inputs/#mem) +**Required Telegraf plugin:** [Mem input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#mem) `mem.json` @@ -404,7 +404,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/ ### net -**Required Telegraf plugin:** [Net input plugin](/telegraf/latest/plugins/inputs/#net) +**Required Telegraf plugin:** [Net input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#net) `net.json` @@ -413,7 +413,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/ ### netstat -**Required Telegraf plugin:** [Netstat input plugin](/telegraf/latest/plugins/inputs/#netstat) +**Required Telegraf plugin:** [Netstat input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#netstat) `netstat.json` @@ -422,7 +422,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/ ### processes -**Required Telegraf plugin:** [Processes input plugin](/telegraf/latest/plugins/inputs/#processes) +**Required Telegraf plugin:** [Processes input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#processes) `processes.json` @@ -430,7 +430,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/ ### procstat -**Required Telegraf plugin:** [Procstat input plugin](/telegraf/latest/plugins/inputs/#procstat) +**Required Telegraf plugin:** [Procstat input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#procstat) `procstat.json` @@ -439,7 +439,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/ ### system -**Required Telegraf plugin:** [Procstat input plugin](/telegraf/latest/plugins/inputs/#procstat) +**Required Telegraf plugin:** [Procstat input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#procstat) `load.json` @@ -447,7 +447,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/ ## varnish -**Required Telegraf plugin:** [Varnish](/telegraf/latest/plugins/inputs/#varnish) +**Required Telegraf plugin:** [Varnish](/{{< latest "telegraf" >}}/plugins/inputs/#varnish) `varnish.json` @@ -456,7 +456,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/ ## win_system -**Required Telegraf plugin:** [Windows Performance Counters input plugin](/telegraf/latest/plugins/inputs/#windows-performance-counters) +**Required Telegraf plugin:** [Windows Performance Counters input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#windows-performance-counters) `win_cpu.json` diff --git a/content/chronograf/v1.7/guides/visualization-types.md b/content/chronograf/v1.7/guides/visualization-types.md index 006062f34..592a1a1d9 100644 --- a/content/chronograf/v1.7/guides/visualization-types.md +++ b/content/chronograf/v1.7/guides/visualization-types.md @@ -8,7 +8,7 @@ menu: parent: Guides --- -Chronograf's dashboard views support the following visualization types, which can be selected in the **Visualization Type** selection view of the [Data Explorer](/chronograf/latest/querying-data) . +Chronograf's dashboard views support the following visualization types, which can be selected in the **Visualization Type** selection view of the [Data Explorer](/{{< latest "chronograf" >}}/querying-data) . [Visualization Type selector](/img/chronograf/1-6-viz-types-selector.png) @@ -180,10 +180,10 @@ The **Single Stat** view displays the most recent value of the specified time se ![Single Stat view](/img/chronograf/1-6-viz-single-stat-selector.png) -If a cell's query includes a [`GROUP BY` tag](/influxdb/latest/query_language/data_exploration/#group-by-tags) clause, Chronograf sorts the different [series](/influxdb/latest/concepts/glossary/#series) lexicographically and shows the most recent [field value](/influxdb/latest/concepts/glossary/#field-value) associated with the first series. -For example, if a query groups by the `name` [tag key](/influxdb/latest/concepts/glossary/#tag-key) and `name` has two [tag values](/influxdb/latest/concepts/glossary/#tag-value) (`chronelda` and `chronz`), Chronograf shows the most recent field value associated with the `chronelda` series. +If a cell's query includes a [`GROUP BY` tag](/{{< latest "influxdb" "v1" >}}/query_language/data_exploration/#group-by-tags) clause, Chronograf sorts the different [series](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#series) lexicographically and shows the most recent [field value](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#field-value) associated with the first series. +For example, if a query groups by the `name` [tag key](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-key) and `name` has two [tag values](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-value) (`chronelda` and `chronz`), Chronograf shows the most recent field value associated with the `chronelda` series. -If a cell's query includes more than one [field key](/influxdb/latest/concepts/glossary/#field-key) in the [`SELECT` clause](/influxdb/latest/query_language/data_exploration/#select-clause), Chronograf returns the most recent field value associated with the first field key in the `SELECT` clause. +If a cell's query includes more than one [field key](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#field-key) in the [`SELECT` clause](/{{< latest "influxdb" "v1" >}}/query_language/data_exploration/#select-clause), Chronograf returns the most recent field value associated with the first field key in the `SELECT` clause. For example, if a query's `SELECT` clause is `SELECT "chronogiraffe","chronelda"`, Chronograf shows the most recent field value associated with the `chronogiraffe` field key. #### Single Stat Controls diff --git a/content/chronograf/v1.7/introduction/_index.md b/content/chronograf/v1.7/introduction/_index.md index c0f44f0bb..cd2b2f236 100644 --- a/content/chronograf/v1.7/introduction/_index.md +++ b/content/chronograf/v1.7/introduction/_index.md @@ -15,11 +15,11 @@ Follow the links below to get acquainted with Chronograf: Chronograf is supported on several operating systems and hardware architectures. See the [InfluxData downloads page](https://portal.influxdata.com/downloads) page for to the available binaries. -## [Installing Chronograf](/chronograf/latest/introduction/installation/) +## [Installing Chronograf](/{{< latest "chronograf" >}}/introduction/installation/) -[Installing Chronograf](/chronograf/latest/introduction/installation/) lists the requirements for installing, starting, and configuring Chronograf. +[Installing Chronograf](/{{< latest "chronograf" >}}/introduction/installation/) lists the requirements for installing, starting, and configuring Chronograf. ## Getting Started -[Getting started with Chronograf](/chronograf/latest/introduction/getting-started/) gets you up and running with Chronograf with as little configuration and code as possible. +[Getting started with Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/) gets you up and running with Chronograf with as little configuration and code as possible. By the end of the guide, you will have downloaded, installed, and configured all four packages of the TICK stack ([Telegraf](https://github.com/influxdata/telegraf), [InfluxDB](https://github.com/influxdata/influxdb), Chronograf, and [Kapacitor](https://github.com/influxdata/kapacitor)), and you will be all set to monitor your infrastructure. diff --git a/content/chronograf/v1.7/introduction/getting-started.md b/content/chronograf/v1.7/introduction/getting-started.md index 2241174fc..48d0745c5 100644 --- a/content/chronograf/v1.7/introduction/getting-started.md +++ b/content/chronograf/v1.7/introduction/getting-started.md @@ -1,7 +1,7 @@ --- title: Getting started with Chronograf aliases: - - /chronograf/latest/introduction/getting-started/ + - /{{< latest "chronograf" >}}/introduction/getting-started/ - /chronograf/v1.7/introduction/getting_started/ menu: chronograf_1_7: @@ -11,18 +11,18 @@ menu: --- ## Overview -Chronograf allows you to quickly see data you have stored in InfluxDB so you can build robust queries and alerts. After your administrator has set up Chronograf as described in [Installing Chronograf](/chronograf/latest/introduction/installation), get started with key features using the guides below. +Chronograf allows you to quickly see data you have stored in InfluxDB so you can build robust queries and alerts. After your administrator has set up Chronograf as described in [Installing Chronograf](/{{< latest "chronograf" >}}/introduction/installation), get started with key features using the guides below. ### Data visualization -* Investigate your data by building queries using the [Data Explorer](/chronograf/latest/guides/querying-data/). -* Use [pre-created dashboards](/chronograf/latest/guides/using-precreated-dashboards/) to monitor your application data or [create your own dashboards](/chronograf/latest/guides/create-a-dashboard/). -* Customize dashboards using [template variables](/chronograf/latest/guides/dashboard-template-variables/). +* Investigate your data by building queries using the [Data Explorer](/{{< latest "chronograf" >}}/guides/querying-data/). +* Use [pre-created dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards/) to monitor your application data or [create your own dashboards](/{{< latest "chronograf" >}}/guides/create-a-dashboard/). +* Customize dashboards using [template variables](/{{< latest "chronograf" >}}/guides/dashboard-template-variables/). ### Alerting -* [Create alert rules](/chronograf/latest/guides/create-alert-rules/) to generate threshold, relative, and deadman alerts on your data. -* [View all active alerts](/chronograf/latest/guides/create-alert-rules/#step-2-view-the-alerts) on an alert dashboard. -* Use [alert endpoints](/chronograf/latest/guides/configuring-alert-endpoints/) in Chronograf to send alert messages to specific URLs and applications. +* [Create alert rules](/{{< latest "chronograf" >}}/guides/create-alert-rules/) to generate threshold, relative, and deadman alerts on your data. +* [View all active alerts](/{{< latest "chronograf" >}}/guides/create-alert-rules/#step-2-view-the-alerts) on an alert dashboard. +* Use [alert endpoints](/{{< latest "chronograf" >}}/guides/configuring-alert-endpoints/) in Chronograf to send alert messages to specific URLs and applications. ### Infrastructure monitoring -* [View all hosts](/chronograf/latest/guides/monitoring-influxenterprise-clusters/#step-4-explore-the-monitoring-data-in-chronograf) and their statuses in your infrastructure. -* [Use pre-created dashboards](/chronograf/latest/guides/using-precreated-dashboards/) to monitor your applications. +* [View all hosts](/{{< latest "chronograf" >}}/guides/monitoring-influxenterprise-clusters/#step-4-explore-the-monitoring-data-in-chronograf) and their statuses in your infrastructure. +* [Use pre-created dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards/) to monitor your applications. diff --git a/content/chronograf/v1.7/troubleshooting/_index.md b/content/chronograf/v1.7/troubleshooting/_index.md index af733890a..637a53ec4 100644 --- a/content/chronograf/v1.7/troubleshooting/_index.md +++ b/content/chronograf/v1.7/troubleshooting/_index.md @@ -9,4 +9,4 @@ menu: Follow the link below to access Chronograf's FAQ. -## [Frequently Asked Questions](/chronograf/latest/troubleshooting/frequently-asked-questions/) +## [Frequently Asked Questions](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/) diff --git a/content/chronograf/v1.7/troubleshooting/frequently-asked-questions.md b/content/chronograf/v1.7/troubleshooting/frequently-asked-questions.md index ea166032c..9d4bdfb9a 100644 --- a/content/chronograf/v1.7/troubleshooting/frequently-asked-questions.md +++ b/content/chronograf/v1.7/troubleshooting/frequently-asked-questions.md @@ -9,7 +9,7 @@ menu: ## How do I connect Chronograf to an InfluxEnterprise cluster? -The connection details form requires additional information when connecting Chronograf to an [InfluxEnterprise cluster](https://docs.influxdata.com/enterprise_influxdb/latest/). +The connection details form requires additional information when connecting Chronograf to an [InfluxEnterprise cluster](/{{< latest "enterprise_influxdb" >}}/). When you enter the InfluxDB HTTP bind address in the `Connection String` input, Chronograf automatically checks if that InfluxDB instance is a data node. If it is a data node, Chronograf automatically adds the `Meta Service Connection URL` input to the connection details form. @@ -19,4 +19,4 @@ Enter the HTTP bind address of one of your cluster's meta nodes into that input Note that the example above assumes that you do not have authentication enabled. If you have authentication enabled, the form requires username and password information. -For more details about monitoring an InfluxEnterprise cluster, see the [Monitor an InfluxEnterprise Cluster](/chronograf/latest/guides/monitoring-influxenterprise-clusters/) guide. +For more details about monitoring an InfluxEnterprise cluster, see the [Monitor an InfluxEnterprise Cluster](/{{< latest "chronograf" >}}/guides/monitoring-influxenterprise-clusters/) guide. diff --git a/content/chronograf/v1.8/_index.md b/content/chronograf/v1.8/_index.md index 2433d4f87..527324de9 100644 --- a/content/chronograf/v1.8/_index.md +++ b/content/chronograf/v1.8/_index.md @@ -38,7 +38,7 @@ Chronograf offers a UI for [Kapacitor](https://github.com/influxdata/kapacitor), * Create and delete databases and retention policies * View currently-running queries and stop inefficient queries from overloading your system -* Create, delete, and assign permissions to users (Chronograf supports [InfluxDB OSS](/influxdb/latest/administration/authentication_and_authorization/#authorization) and InfluxEnterprise user management) +* Create, delete, and assign permissions to users (Chronograf supports [InfluxDB OSS](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#authorization) and InfluxEnterprise user management) ### Multi-organization and multi-user support diff --git a/content/chronograf/v1.8/about_the_project/release-notes-changelog.md b/content/chronograf/v1.8/about_the_project/release-notes-changelog.md index c4872dd8c..e7f27a9dd 100644 --- a/content/chronograf/v1.8/about_the_project/release-notes-changelog.md +++ b/content/chronograf/v1.8/about_the_project/release-notes-changelog.md @@ -920,9 +920,9 @@ menu: ### UI improvements * When dashboard time range is changed, reset graphs that are zoomed in - * [Bar graph](/chronograf/latest/guides/visualization-types/#bar-graph) option added to dashboard + * [Bar graph](/{{< latest "chronograf" >}}/guides/visualization-types/#bar-graph) option added to dashboard * Redesign source management table to be more intuitive - * Redesign [Line + Single Stat](/chronograf/latest/guides/visualization-types/#line-graph-single-stat) cells to appear more like a sparkline, and improve legibility + * Redesign [Line + Single Stat](/{{< latest "chronograf" >}}/guides/visualization-types/#line-graph-single-stat) cells to appear more like a sparkline, and improve legibility ## v1.3.2.0 [2017-06-05] @@ -938,7 +938,7 @@ menu: ### Features - * Add UI to the Data Explorer for [writing data to InfluxDB](/chronograf/latest/guides/querying-data/) + * Add UI to the Data Explorer for [writing data to InfluxDB](/{{< latest "chronograf" >}}/guides/querying-data/) ### UI improvements @@ -958,26 +958,26 @@ In versions 1.3.1+, installing a new version of Chronograf automatically clears ### Bug fixes - * Fix infinite spinner when `/chronograf` is a [basepath](/chronograf/latest/administration/config-options/#p-basepath) + * Fix infinite spinner when `/chronograf` is a [basepath](/{{< latest "chronograf" >}}/administration/config-options/#p-basepath) * Remove the query templates dropdown from dashboard cell editor mode * Fix the backwards sort arrows in table column headers * Make the logout button consistent with design * Fix the loading spinner on graphs * Filter out any template variable values that are empty, whitespace, or duplicates - * Allow users to click the add query button after selecting singleStat as the [visualization type](/chronograf/latest/guides/visualization-types) + * Allow users to click the add query button after selecting singleStat as the [visualization type](/{{< latest "chronograf" >}}/guides/visualization-types) * Add a query for windows uptime - thank you, @brianbaker! ### Features * Add log event handler- thank you, @mpchadwick! * Update Go (golang) vendoring to dep and committed vendor directory - * Add autocomplete functionality to [template variable](/chronograf/latest/guides/dashboard-template-variables) dropdowns + * Add autocomplete functionality to [template variable](/{{< latest "chronograf" >}}/guides/dashboard-template-variables) dropdowns ### UI improvements * Refactor scrollbars to support non-webkit browsers * Increase the query builder's default height in cell editor mode and in the data explorer - * Make the [template variables](/chronograf/latest/guides/dashboard-template-variables) manager more space efficient + * Make the [template variables](/{{< latest "chronograf" >}}/guides/dashboard-template-variables) manager more space efficient * Add page spinners to pages that did not have them * Denote which source is connected in the sources table * Use milliseconds in the InfluxDB dashboard instead of nanoseconds @@ -987,25 +987,25 @@ In versions 1.3.1+, installing a new version of Chronograf automatically clears ### Bug fixes - * Fix the link to home when using the [`--basepath` option](/chronograf/latest/administration/config-options/#p-basepath) + * Fix the link to home when using the [`--basepath` option](/{{< latest "chronograf" >}}/administration/config-options/#p-basepath) * Remove the notification to login on the login page * Support queries that perform math on functions * Prevent the creation of blank template variables * Ensure thresholds for Kapacitor Rule Alerts appear on page load * Update the Kapacitor configuration page when the configuration changes - * Fix Authentication when using Chronograf with a set [basepath](/chronograf/latest/administration/config-options/#p-basepath) + * Fix Authentication when using Chronograf with a set [basepath](/{{< latest "chronograf" >}}/administration/config-options/#p-basepath) * Show red indicator on Hosts Page for an offline host * Support escaping from presentation mode in Safari * Re-implement level colors on the alerts page * Fix router bug introduced by upgrading to react-router v3.0 - * Show legend on [Line+Stat](/chronograf/latest/guides/visualization-types/#line-graph-single-stat) visualization type + * Show legend on [Line+Stat](/{{< latest "chronograf" >}}/guides/visualization-types/#line-graph-single-stat) visualization type * Prevent queries with `:dashboardTime:` from breaking the query builder ### Features * Add line-protocol proxy for InfluxDB/InfluxEnterprise Cluster data sources * Add `:dashboardTime:` to support cell-specific time ranges on dashboards - * Add support for enabling and disabling [TICKscripts that were created outside Chronograf](/chronograf/latest/guides/advanced-kapacitor/#tickscript-management) + * Add support for enabling and disabling [TICKscripts that were created outside Chronograf](/{{< latest "chronograf" >}}/guides/advanced-kapacitor/#tickscript-management) * Allow users to delete Kapacitor configurations ### UI improvements diff --git a/content/chronograf/v1.8/administration/chrono-on-clusters.md b/content/chronograf/v1.8/administration/chrono-on-clusters.md index 0405f8fe4..1b93297aa 100644 --- a/content/chronograf/v1.8/administration/chrono-on-clusters.md +++ b/content/chronograf/v1.8/administration/chrono-on-clusters.md @@ -8,7 +8,7 @@ menu: parent: Administration --- -The connection details form requires additional information when connecting Chronograf to an [InfluxDB Enterprise cluster](https://docs.influxdata.com/enterprise_influxdb/latest/). +The connection details form requires additional information when connecting Chronograf to an [InfluxDB Enterprise cluster](/{{< latest "enterprise_influxdb" >}}/). When you enter the InfluxDB HTTP bind address in the `Connection String` input, Chronograf automatically checks if that InfluxDB instance is a data node. If it is a data node, Chronograf automatically adds the `Meta Service Connection URL` input to the connection details form. @@ -19,4 +19,4 @@ Enter the HTTP bind address of one of your cluster's meta nodes into that input Note that the example above assumes that you do not have authentication enabled. If you have authentication enabled, the form requires username and password information. -For details about monitoring InfluxEnterprise clusters, see [Monitoring InfluxDB Enterprise clusters](/chronograf/latest/guides/monitoring-influxenterprise-clusters). +For details about monitoring InfluxEnterprise clusters, see [Monitoring InfluxDB Enterprise clusters](/{{< latest "chronograf" >}}/guides/monitoring-influxenterprise-clusters). diff --git a/content/chronograf/v1.8/administration/config-options.md b/content/chronograf/v1.8/administration/config-options.md index 2d47454c5..1a03d3ec4 100644 --- a/content/chronograf/v1.8/administration/config-options.md +++ b/content/chronograf/v1.8/administration/config-options.md @@ -94,7 +94,7 @@ Environment variable: `$BOLT_PATH` #### `--canned-path=` | `-c` -The path to the directory of [canned dashboards](/chronograf/latest/guides/using-precreated-dashboards) files. +The path to the directory of [canned dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards) files. Default value: `/usr/share/chronograf/canned` diff --git a/content/chronograf/v1.8/administration/configuration.md b/content/chronograf/v1.8/administration/configuration.md index 671e84739..d11133b7a 100644 --- a/content/chronograf/v1.8/administration/configuration.md +++ b/content/chronograf/v1.8/administration/configuration.md @@ -39,7 +39,7 @@ Use one of the following commands to start Chronograf: ## Set custom default Chronograf configuration options Custom default Chronograf configuration settings can be defined in `/etc/default/chronograf`. -This file consists of key-value pairs. See keys (environment variables) for [Chronograf configuration options](https://docs.influxdata.com/chronograf/v1.8/administration/config-options), and set values for the keys you want to configure. +This file consists of key-value pairs. See keys (environment variables) for [Chronograf configuration options](/chronograf/v1.8/administration/config-options), and set values for the keys you want to configure. ```conf HOST=0.0.0.0 diff --git a/content/chronograf/v1.8/administration/creating-connections.md b/content/chronograf/v1.8/administration/creating-connections.md index afbeeb528..bdf93a622 100644 --- a/content/chronograf/v1.8/administration/creating-connections.md +++ b/content/chronograf/v1.8/administration/creating-connections.md @@ -31,15 +31,15 @@ To create an InfluxDB connection in the Chronograf UI: * **Connection URL**: Enter the hostname or IP address of the InfluxDB instance and the port. The field is prefilled with `http://localhost:8086`. * **Connection Name**: Enter the name for this connection. * **Username**: Enter the username that will be shared for this connection. - *Required only if [authorization is enabled](/influxdb/latest/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.* + *Required only if [authorization is enabled](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.* * **Password**: Enter the password. - *Required only if [authorization is enabled](/influxdb/latest/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.* + *Required only if [authorization is enabled](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.* * **Telegraf Database Name**: This field specifies the database that Chronograf will use for populating different parts of the application, including the Host List page. If none is provided, we will use `autogen`. You will still be able to query any database you have access to in the InfluxDB instance when building dashboards or exploring data. - * **Default Retention Policy**: Enter the name of the default [retention policy](/influxdb/latest/concepts/glossary/#retention-policy-rp). If none is provided, it assumes `autogen`. If you've changed the default retention policy in your InfluxDB instance, you may want to change it here as well. + * **Default Retention Policy**: Enter the name of the default [retention policy](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#retention-policy-rp). If none is provided, it assumes `autogen`. If you've changed the default retention policy in your InfluxDB instance, you may want to change it here as well. * **Make this the default connection**: When this option is selected, this InfluxDB connection will be used when Chronograf is launched. 4. Click **Add Connection** - * If the connection is valid, the Dashboards window appears, allowing you to import dashboard templates you can use to display and analyze your data. For details, see [Creating dashboards](/chronograf/latest/guides/create-a-dashboard). + * If the connection is valid, the Dashboards window appears, allowing you to import dashboard templates you can use to display and analyze your data. For details, see [Creating dashboards](/{{< latest "chronograf" >}}/guides/create-a-dashboard). * If the connection cannot be created, the following error message appears: "Unable to create source: Error contacting source." If this occurs, ensure all connection credentials are correct and that the InfluxDB instance is running and accessible. @@ -109,11 +109,11 @@ Any string you want to use as the display name of the source. #### `username` Username used to access the InfluxDB server or cluster. -*Only required if [authorization is enabled](/influxdb/latest/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.* +*Only required if [authorization is enabled](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.* #### `password` Password used to access the InfluxDB server or cluster. -*Only required if [authorization is enabled](/influxdb/latest/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.* +*Only required if [authorization is enabled](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.* #### `url` URL of the InfluxDB server or cluster. @@ -176,9 +176,9 @@ To create a Kapacitor connection using the Chronograf UI: * **Kapacitor URL**: Enter the hostname or IP address of the Kapacitor instance and the port. The field is prefilled with `http://localhost:9092`. * **Name**: Enter the name for this connection. * **Username**: Enter the username that will be shared for this connection. - *Only required if [authorization is enabled](/kapacitor/latest/administration/security/#kapacitor-authentication-and-authorization) on the Kapacitor instance or cluster to which you're connecting.* + *Only required if [authorization is enabled](/{{< latest "kapacitor" >}}/administration/security/#kapacitor-authentication-and-authorization) on the Kapacitor instance or cluster to which you're connecting.* * **Password**: Enter the password. - *Only required if [authorization is enabled](/kapacitor/latest/administration/security/#kapacitor-authentication-and-authorization) on the Kapacitor instance or cluster to which you're connecting.* + *Only required if [authorization is enabled](/{{< latest "kapacitor" >}}/administration/security/#kapacitor-authentication-and-authorization) on the Kapacitor instance or cluster to which you're connecting.* 4. Click **Continue**. If the connection is valid, the message "Kapacitor Created! Configuring endpoints is optional." appears. To configure alert endpoints, see [Configuring alert endpoints](/chronograf/v1.8/guides/configuring-alert-endpoints/). diff --git a/content/chronograf/v1.8/administration/managing-chronograf-users.md b/content/chronograf/v1.8/administration/managing-chronograf-users.md index da1f83fcf..9f1ce8770 100644 --- a/content/chronograf/v1.8/administration/managing-chronograf-users.md +++ b/content/chronograf/v1.8/administration/managing-chronograf-users.md @@ -31,7 +31,7 @@ menu: ## Manage Chronograf users and roles -> ***Note:*** Support for organizations and user roles is available in Chronograf 1.4 or later. First, OAuth 2.0 authentication must be configured (if it is, you'll see the Chronograf Admin tab on the Admin menu). For more information, see [Managing security] (https://docs.influxdata.com/chronograf/v1.8/administration/managing-security/). +> ***Note:*** Support for organizations and user roles is available in Chronograf 1.4 or later. First, OAuth 2.0 authentication must be configured (if it is, you'll see the Chronograf Admin tab on the Admin menu). For more information, see [Managing security] (/chronograf/v1.8/administration/managing-security/). Chronograf includes four organization-bound user roles and one cross-organization SuperAdmin status. In an organization, admins (with the `admin` role) or users with SuperAdmin status can create, update, and assign roles to a user or remove a role assignment. diff --git a/content/chronograf/v1.8/administration/managing-influxdb-users.md b/content/chronograf/v1.8/administration/managing-influxdb-users.md index d7766488d..9cd41f2ec 100644 --- a/content/chronograf/v1.8/administration/managing-influxdb-users.md +++ b/content/chronograf/v1.8/administration/managing-influxdb-users.md @@ -13,7 +13,7 @@ menu: The **Chronograf Admin** provides InfluxDB user management for InfluxDB OSS and InfluxDB Enterprise users. -> ***Note:*** For details on Chronograf user authentication and management, see [Managing security](/chronograf/latest/administration/managing-security/). +> ***Note:*** For details on Chronograf user authentication and management, see [Managing security](/{{< latest "chronograf" >}}/administration/managing-security/). **On this page:** @@ -58,7 +58,7 @@ Restart the InfluxDB service for your configuration changes to take effect: ### Step 3: Create an admin user. -Because authentication is enabled, you need to create an [admin user](/influxdb/latest/administration/authentication_and_authorization/#user-types-and-privileges) before you can do anything else in the database. +Because authentication is enabled, you need to create an [admin user](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#user-types-and-privileges) before you can do anything else in the database. Run the `curl` command below to create an admin user, replacing: * `localhost` with the IP or hostname of your InfluxDB OSS instance or one of your InfluxEnterprise data nodes @@ -91,7 +91,7 @@ On the **Chronograf Admin** page: ![InfluxDB OSS user management](/img/chronograf/1-6-admin-usermanagement-oss.png) InfluxDB users are either admin users or non-admin users. -See InfluxDB's [authentication and authorization](/influxdb/latest/administration/authentication_and_authorization/#user-types-and-privileges) documentation for more information about those user types. +See InfluxDB's [authentication and authorization](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#user-types-and-privileges) documentation for more information about those user types. > ***Note:*** Note that Chronograf currently does not support assigning InfluxDB database `READ`or `WRITE` access to non-admin users. >This is a known issue. @@ -156,12 +156,12 @@ Assign permissions and roles to both admin and non-admin users. Permission to add or remove nodes from a cluster. **Relevant `influxd-ctl` arguments**: -[`add-data`](/enterprise_influxdb/latest/administration/cluster-commands/#add-data), -[`add-meta`](/enterprise_influxdb/latest/administration/cluster-commands/#add-meta), -[`join`](/enterprise_influxdb/latest/administration/cluster-commands/#join), -[`remove-data`](/enterprise_influxdb/latest/administration/cluster-commands/#remove-data), -[`remove-meta`](/enterprise_influxdb/latest/administration/cluster-commands/#remove-meta), and -[`leave`](/enterprise_influxdb/latest/administration/cluster-commands/#leave) +[`add-data`](/{{< latest "enterprise_influxdb" >}}/administration/cluster-commands/#add-data), +[`add-meta`](/{{< latest "enterprise_influxdb" >}}/administration/cluster-commands/#add-meta), +[`join`](/{{< latest "enterprise_influxdb" >}}/administration/cluster-commands/#join), +[`remove-data`](/{{< latest "enterprise_influxdb" >}}/administration/cluster-commands/#remove-data), +[`remove-meta`](/{{< latest "enterprise_influxdb" >}}/administration/cluster-commands/#remove-meta), and +[`leave`](/{{< latest "enterprise_influxdb" >}}/administration/cluster-commands/#leave) **Pages in Chronograf that require this permission**: NA @@ -169,18 +169,18 @@ Permission to add or remove nodes from a cluster. Permission to copy shards. **Relevant `influxd-ctl` arguments**: -[`copy-shard`](/enterprise_influxdb/latest/administration/cluster-commands/#copy-shard) +[`copy-shard`](/{{< latest "enterprise_influxdb" >}}/administration/cluster-commands/#copy-shard) **Pages in Chronograf that require this permission**: NA #### CreateDatabase -Permission to create databases, create [retention policies](/influxdb/latest/concepts/glossary/#retention-policy-rp), alter retention policies, and view retention policies. +Permission to create databases, create [retention policies](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#retention-policy-rp), alter retention policies, and view retention policies. **Relevant InfluxQL queries**: -[`CREATE DATABASE`](/influxdb/latest/query_language/database_management/#create-database), -[`CREATE RETENTION POLICY`](/influxdb/latest/query_language/database_management/#create-retention-policies-with-create-retention-policy), -[`ALTER RETENTION POLICY`](/influxdb/latest/query_language/database_management/#modify-retention-policies-with-alter-retention-policy), and -[`SHOW RETENTION POLICIES`](/influxdb/latest/query_language/schema_exploration/#show-retention-policies) +[`CREATE DATABASE`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#create-database), +[`CREATE RETENTION POLICY`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#create-retention-policies-with-create-retention-policy), +[`ALTER RETENTION POLICY`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#modify-retention-policies-with-alter-retention-policy), and +[`SHOW RETENTION POLICIES`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-retention-policies) **Pages in Chronograf that require this permission**: Dashboards, Data Explorer, and Databases on the Admin page @@ -188,25 +188,25 @@ Permission to create databases, create [retention policies](/influxdb/latest/con Permission to manage users and roles; create users, drop users, grant admin status to users, grant permissions to users, revoke admin status from users, revoke permissions from users, change user passwords, view user permissions, and view users and their admin status. **Relevant InfluxQL queries**: -[`CREATE USER`](/influxdb/latest/administration/authentication_and_authorization/#user-management-commands), -[`DROP USER`](/influxdb/latest/administration/authentication_and_authorization/#general-admin-and-non-admin-user-management), -[`GRANT ALL PRIVILEGES`](/influxdb/latest/administration/authentication_and_authorization/#user-management-commands), -[`GRANT [READ,WRITE,ALL]`](/influxdb/latest/administration/authentication_and_authorization/#non-admin-user-management), -[`REVOKE ALL PRIVILEGES`](/influxdb/latest/administration/authentication_and_authorization/#user-management-commands), -[`REVOKE [READ,WRITE,ALL]`](/influxdb/latest/administration/authentication_and_authorization/#non-admin-user-management), -[`SET PASSWORD`](/influxdb/latest/administration/authentication_and_authorization/#general-admin-and-non-admin-user-management), -[`SHOW GRANTS`](/influxdb/latest/administration/authentication_and_authorization/#non-admin-user-management), and -[`SHOW USERS`](/influxdb/latest/administration/authentication_and_authorization/#user-management-commands) +[`CREATE USER`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#user-management-commands), +[`DROP USER`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#general-admin-and-non-admin-user-management), +[`GRANT ALL PRIVILEGES`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#user-management-commands), +[`GRANT [READ,WRITE,ALL]`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#non-admin-user-management), +[`REVOKE ALL PRIVILEGES`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#user-management-commands), +[`REVOKE [READ,WRITE,ALL]`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#non-admin-user-management), +[`SET PASSWORD`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#general-admin-and-non-admin-user-management), +[`SHOW GRANTS`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#non-admin-user-management), and +[`SHOW USERS`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#user-management-commands) **Pages in Chronograf that require this permission**: Data Explorer, Dashboards, Users and Roles on the Admin page #### DropData -Permission to drop data, in particular [series](/influxdb/latest/concepts/glossary/#series) and [measurements](/influxdb/latest/concepts/glossary/#measurement). +Permission to drop data, in particular [series](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#series) and [measurements](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#measurement). **Relevant InfluxQL queries**: -[`DROP SERIES`](/influxdb/latest/query_language/database_management/#drop-series-from-the-index-with-drop-series), -[`DELETE`](/influxdb/latest/query_language/database_management/#delete-series-with-delete), and -[`DROP MEASUREMENT`](/influxdb/latest/query_language/database_management/#delete-measurements-with-drop-measurement) +[`DROP SERIES`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#drop-series-from-the-index-with-drop-series), +[`DELETE`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#delete-series-with-delete), and +[`DROP MEASUREMENT`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#delete-measurements-with-drop-measurement) **Pages in Chronograf that require this permission**: NA @@ -214,8 +214,8 @@ Permission to drop data, in particular [series](/influxdb/latest/concepts/glossa Permission to drop databases and retention policies. **Relevant InfluxQL queries**: -[`DROP DATABASE`](/influxdb/latest/query_language/database_management/#delete-a-database-with-drop-database) and -[`DROP RETENTION POLICY`](/influxdb/latest/query_language/database_management/#delete-retention-policies-with-drop-retention-policy) +[`DROP DATABASE`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#delete-a-database-with-drop-database) and +[`DROP RETENTION POLICY`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#delete-retention-policies-with-drop-retention-policy) **Pages in Chronograf that require this permission**: Data Explorer, Dashboards, Databases on the Admin page @@ -231,12 +231,12 @@ Permission to access the configuration-related API calls for InfluxKapacitor Ent **Pages in Chronograf that require this permission**: NA #### ManageContinuousQuery -Permission to create, drop, and view [continuous queries](/influxdb/latest/concepts/glossary/#continuous-query-cq). +Permission to create, drop, and view [continuous queries](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#continuous-query-cq). **Relevant InfluxQL queries**: -[`CreateContinuousQueryStatement`](/influxdb/latest/query_language/continuous_queries/), -[`DropContinuousQueryStatement`](/influxdb/latest/query_language/continuous_queries/#deleting-continuous-queries), and -[`ShowContinuousQueriesStatement`](/influxdb/latest/query_language/continuous_queries/#listing-continuous-queries) +[`CreateContinuousQueryStatement`](/{{< latest "influxdb" "v1" >}}/query_language/continuous_queries/), +[`DropContinuousQueryStatement`](/{{< latest "influxdb" "v1" >}}/query_language/continuous_queries/#deleting-continuous-queries), and +[`ShowContinuousQueriesStatement`](/{{< latest "influxdb" "v1" >}}/query_language/continuous_queries/#listing-continuous-queries) **Pages in Chronograf that require this permission**: Data Explorer, Dashboards @@ -244,28 +244,28 @@ Permission to create, drop, and view [continuous queries](/influxdb/latest/conce Permission to view and kill queries. **Relevant InfluxQL queries**: -[`SHOW QUERIES`](/influxdb/latest/troubleshooting/query_management/#list-currently-running-queries-with-show-queries) and -[`KILL QUERY`](/influxdb/latest/troubleshooting/query_management/#stop-currently-running-queries-with-kill-query) +[`SHOW QUERIES`](/{{< latest "influxdb" "v1" >}}/troubleshooting/query_management/#list-currently-running-queries-with-show-queries) and +[`KILL QUERY`](/{{< latest "influxdb" "v1" >}}/troubleshooting/query_management/#stop-currently-running-queries-with-kill-query) **Pages in Chronograf that require this permission**: Queries on the Admin page #### ManageShard -Permission to copy, delete, and view [shards](/influxdb/latest/concepts/glossary/#shard). +Permission to copy, delete, and view [shards](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#shard). **Relevant InfluxQL queries**: -[`DropShardStatement`](/influxdb/latest/query_language/database_management/#delete-a-shard-with-drop-shard), -[`ShowShardGroupsStatement`](/influxdb/latest/query_language/spec/#show-shard-groups), and -[`ShowShardsStatement`](/influxdb/latest/query_language/spec/#show-shards) +[`DropShardStatement`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#delete-a-shard-with-drop-shard), +[`ShowShardGroupsStatement`](/{{< latest "influxdb" "v1" >}}/query_language/spec/#show-shard-groups), and +[`ShowShardsStatement`](/{{< latest "influxdb" "v1" >}}/query_language/spec/#show-shards) **Pages in Chronograf that require this permission**: NA #### ManageSubscription -Permission to create, drop, and view [subscriptions](/influxdb/latest/concepts/glossary/#subscription). +Permission to create, drop, and view [subscriptions](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#subscription). **Relevant InfluxQL queries**: -[`CREATE SUBSCRIPTION`](/influxdb/latest/query_language/spec/#create-subscription), -[`DROP SUBSCRIPTION`](/influxdb/latest/query_language/spec/#drop-subscription), and -[`SHOW SUBSCRIPTIONS`](/influxdb/latest/query_language/spec/#show-subscriptions) +[`CREATE SUBSCRIPTION`](/{{< latest "influxdb" "v1" >}}/query_language/spec/#create-subscription), +[`DROP SUBSCRIPTION`](/{{< latest "influxdb" "v1" >}}/query_language/spec/#drop-subscription), and +[`SHOW SUBSCRIPTIONS`](/{{< latest "influxdb" "v1" >}}/query_language/spec/#show-subscriptions) **Pages in Chronograf that require this permission**: Alerting @@ -282,12 +282,12 @@ Permission to view cluster statistics and diagnostics. Permission to read data. **Relevant InfluxQL queries**: -[`SHOW FIELD KEYS`](/influxdb/latest/query_language/schema_exploration/#show-field-keys), -[`SHOW MEASUREMENTS`](/influxdb/latest/query_language/schema_exploration/#show-measurements), -[`SHOW SERIES`](/influxdb/latest/query_language/schema_exploration/#show-series), -[`SHOW TAG KEYS`](/influxdb/latest/query_language/schema_exploration/#show-tag-keys), -[`SHOW TAG VALUES`](/influxdb/latest/query_language/schema_exploration/#show-tag-values), and -[`SHOW RETENTION POLICIES`](/influxdb/latest/query_language/schema_exploration/#show-retention-policies) +[`SHOW FIELD KEYS`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-field-keys), +[`SHOW MEASUREMENTS`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-measurements), +[`SHOW SERIES`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-series), +[`SHOW TAG KEYS`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-tag-keys), +[`SHOW TAG VALUES`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-tag-values), and +[`SHOW RETENTION POLICIES`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-retention-policies) **Pages in Chronograf that require this permission**: Admin, Alerting, Dashboards, Data Explorer, Host List diff --git a/content/chronograf/v1.8/administration/managing-organizations.md b/content/chronograf/v1.8/administration/managing-organizations.md index feed2221c..6ff5aa63b 100644 --- a/content/chronograf/v1.8/administration/managing-organizations.md +++ b/content/chronograf/v1.8/administration/managing-organizations.md @@ -24,7 +24,7 @@ menu: First, OAuth 2.0 authentication must be configured (if it is, you'll see the Chronograf Admin tab on the Admin menu). For more information, see [managing security](/chronograf/v1.8/administration/managing-security/). -For information about the new user roles and SuperAdmin status, see [Managing Chronograf users](https://docs.influxdata.com/chronograf/v1.8/administration/managing-chronograf-users/). +For information about the new user roles and SuperAdmin status, see [Managing Chronograf users](/chronograf/v1.8/administration/managing-chronograf-users/). A Chronograf organization is a collection of Chronograf users who share common Chronograf-owned resources, including dashboards, InfluxDB connections, and Kapacitor connections. Organizations can be used to represent companies, functional units, projects, or teams. Chronograf users can be members of multiple organizations. diff --git a/content/chronograf/v1.8/administration/managing-security.md b/content/chronograf/v1.8/administration/managing-security.md index d3c6b8ab9..b4b7ee735 100644 --- a/content/chronograf/v1.8/administration/managing-security.md +++ b/content/chronograf/v1.8/administration/managing-security.md @@ -20,8 +20,8 @@ To enhance security, configure Chronograf to authenticate and authorize with [OA ## Configure OAuth 2.0 > After configuring OAuth 2.0, the Chronograf Admin tab becomes visible. -> You can then set up [multiple organizations](https://docs.influxdata.com/chronograf/latest/administration/managing-organizations/) -> and [users](https://docs.influxdata.com/chronograf/latest/administration/managing-influxdb-users/). +> You can then set up [multiple organizations](/{{< latest "chronograf" >}}/administration/managing-organizations/) +> and [users](/{{< latest "chronograf" >}}/administration/managing-influxdb-users/). Configure Chronograf to use an OAuth 2.0 provider and JWT (JSON Web Token) to authenticate users and enable role-based access controls. diff --git a/content/chronograf/v1.8/administration/prebuilt-dashboards.md b/content/chronograf/v1.8/administration/prebuilt-dashboards.md index b2b70738a..84dda0d7a 100644 --- a/content/chronograf/v1.8/administration/prebuilt-dashboards.md +++ b/content/chronograf/v1.8/administration/prebuilt-dashboards.md @@ -7,7 +7,7 @@ menu: weight: 50 parent: Administration --- -Chronograf lets you import a variety of prebuilt dashboards that visualize metrics collect by specific [Telegraf input plugins](/telegraf/latest/plugins/plugin-list). The following Telegraf-related dashboards templates are available. +Chronograf lets you import a variety of prebuilt dashboards that visualize metrics collect by specific [Telegraf input plugins](/{{< latest "telegraf" >}}/plugins/plugin-list). The following Telegraf-related dashboards templates are available. For details on how to import dashboards while adding a connection in Chronograf, see [Creating connections](/chronograf/v1.8/administration/creating-connections/#manage-influxdb-connections-using-the-chronograf-ui). @@ -30,12 +30,12 @@ The Docker dashboard displays the following information: ### Plugins -- [`docker` plugin](/telegraf/latest/plugins/plugin-list/#docker) -- [`disk` plugin](/telegraf/latest/plugins/plugin-list/#disk) -- [`mem` plugin](/telegraf/latest/plugins/plugin-list/#mem) -- [`diskio` plugin](/telegraf/latest/plugins/plugin-list/#diskio) -- [`system` plugin](/telegraf/latest/plugins/plugin-list/#system) -- [`cpu` plugin](/telegraf/latest/plugins/plugin-list/#cpu) +- [`docker` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#docker) +- [`disk` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#disk) +- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#mem) +- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#diskio) +- [`system` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#system) +- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#cpu) ## Kubernetes Node The Kubernetes Node dashboard displays the following information: @@ -53,7 +53,7 @@ The Kubernetes Node dashboard displays the following information: - K8s - Kubelet Memory Bytes ### Plugins -- [kubernetes](/telegraf/latest/plugins/plugin-list/#kubernetes) +- [kubernetes](/{{< latest "telegraf" >}}/plugins/plugin-list/#kubernetes) ## Kubernetes Overview The Kubernetes Node dashboard displays the following information: @@ -72,7 +72,7 @@ The Kubernetes Node dashboard displays the following information: ### Plugins -- [kubernetes](/telegraf/latest/plugins/plugin-list/#kubernetes) +- [kubernetes](/{{< latest "telegraf" >}}/plugins/plugin-list/#kubernetes) ## Kubernetes Pod The Kubernetes Pod dashboard displays the following information: @@ -87,7 +87,7 @@ The Kubernetes Pod dashboard displays the following information: - K8s - Pod TX Bytes/Second ### Plugins -- [kubernetes](/telegraf/latest/plugins/plugin-list/#kubernetes) +- [kubernetes](/{{< latest "telegraf" >}}/plugins/plugin-list/#kubernetes) ## Riak The Riak dashboard displays the following information: @@ -101,7 +101,7 @@ The Riak dashboard displays the following information: - Riak - Read Repairs/Minute ### Plugins -- [`riak` plugin](/telegraf/latest/plugins/plugin-list/#riak) +- [`riak` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#riak) ## Consul The Consul dashboard displays the following information: @@ -110,7 +110,7 @@ The Consul dashboard displays the following information: - Consul - Number of Warning Health Checks ### Plugins -- [`consul` plugin](/telegraf/latest/plugins/plugin-list/#consul) +- [`consul` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#consul) ## Consul Telemetry The Consul Telemetry dashboard displays the following information: @@ -125,7 +125,7 @@ The Consul Telemetry dashboard displays the following information: - Consul - Number of Serf Events ### Plugins -[`consul` plugin](/telegraf/latest/plugins/plugin-list/#consul) +[`consul` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#consul) ## Mesos @@ -140,7 +140,7 @@ The Mesos dashboard displays the following information: - Mesos Master Uptime ### Plugins -- [`mesos` plugin](/telegraf/latest/plugins/plugin-list/#mesos) +- [`mesos` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#mesos) ## RabbitMQ The RabbitMQ dashboard displays the following information: @@ -151,7 +151,7 @@ The RabbitMQ dashboard displays the following information: ### Plugins -- [`rabbitmq` plugin](/telegraf/latest/plugins/plugin-list/#rabbitmq) +- [`rabbitmq` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#rabbitmq) ## System @@ -170,14 +170,14 @@ The System dashboard displays the following information: ### Plugins -- [`system` plugin](/telegraf/latest/plugins/plugin-list/#system) -- [`mem` plugin](/telegraf/latest/plugins/plugin-list/#mem) -- [`cpu` plugin](/telegraf/latest/plugins/plugin-list/#cpu) -- [`disk` plugin](/telegraf/latest/plugins/plugin-list/#disk) -- [`diskio` plugin](/telegraf/latest/plugins/plugin-list/#diskio) -- [`net` plugin](/telegraf/latest/plugins/plugin-list/#net) -- [`processes` plugin](/telegraf/latest/plugins/plugin-list/#processes) -- [`swap` plugin](/telegraf/latest/plugins/plugin-list/#swap) +- [`system` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#system) +- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#mem) +- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#cpu) +- [`disk` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#disk) +- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#diskio) +- [`net` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#net) +- [`processes` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#processes) +- [`swap` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#swap) @@ -198,7 +198,7 @@ The VMware vSphere Overview dashboard gives an overview of your VMware vSphere C - VM CPU % Ready for :clustername: ### Plugins -- [`vsphere` plugin](/telegraf/latest/plugins/plugin-list/#vmware-vsphere) +- [`vsphere` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#vmware-vsphere) ## Apache The Apache dashboard displays the following information: @@ -221,12 +221,12 @@ The Apache dashboard displays the following information: ### Plugins -- [`apache` plugin](/telegraf/latest/plugins/plugin-list/#apache) -- [`system` plugin](/telegraf/latest/plugins/plugin-list/#system) -- [`mem` plugin](/telegraf/latest/plugins/plugin-list/#mem) -- [`diskio` plugin](/telegraf/latest/plugins/plugin-list/#diskio) -- [`net` plugin](/telegraf/latest/plugins/plugin-list/#net) -- [`logparser` plugin](/telegraf/latest/plugins/plugin-list/#logparser) +- [`apache` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#apache) +- [`system` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#system) +- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#mem) +- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#diskio) +- [`net` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#net) +- [`logparser` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#logparser) ## ElasticSearch The ElasticSearch dashboard displays the following information: @@ -243,7 +243,7 @@ The ElasticSearch dashboard displays the following information: - ElasticSearch - JVM Heap Usage ### Plugins -- [`elasticsearch` plugin](/telegraf/latest/plugins/plugin-list/#elasticsearch) +- [`elasticsearch` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#elasticsearch) ## InfluxDB @@ -272,12 +272,12 @@ The InfluxDB dashboard displays the following information: ### Plugins -- [`influxdb` plugin](/telegraf/latest/plugins/plugin-list/#influxdb) -- [`cpu` plugin](/telegraf/latest/plugins/plugin-list/#cpu) -- [`system` plugin](/telegraf/latest/plugins/plugin-list/#system) -- [`mem` plugin](/telegraf/latest/plugins/plugin-list/#mem) -- [`diskio` plugin](/telegraf/latest/plugins/plugin-list/#diskio) -- [`net` plugin](/telegraf/latest/plugins/plugin-list/#net) +- [`influxdb` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#influxdb) +- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#cpu) +- [`system` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#system) +- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#mem) +- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#diskio) +- [`net` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#net) @@ -299,7 +299,7 @@ The Memcached dashboard displays the following information: - Memcached - Evictions/10 Seconds ### Plugins -- [`memcached` plugin](/telegraf/latest/plugins/plugin-list/#memcached) +- [`memcached` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#memcached) ## NSQ @@ -315,7 +315,7 @@ The NSQ dashboard displays the following information: - NSQ - Topic Egress ### Plugins -- [`nsq` plugin](/telegraf/latest/plugins/plugin-list/#nsq) +- [`nsq` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#nsq) ## PostgreSQL The PostgreSQL dashboard displays the following information: @@ -340,11 +340,11 @@ The PostgreSQL dashboard displays the following information: ### Plugins -- [`postgresql` plugin](/telegraf/latest/plugins/plugin-list/#postgresql) -- [`system` plugin](/telegraf/latest/plugins/plugin-list/#system) -- [`mem` plugin](/telegraf/latest/plugins/plugin-list/#mem) -- [`cpu` plugin](/telegraf/latest/plugins/plugin-list/#cpu) -- [`diskio` plugin](/telegraf/latest/plugins/plugin-list/#diskio) +- [`postgresql` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#postgresql) +- [`system` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#system) +- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#mem) +- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#cpu) +- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#diskio) ## HAProxy @@ -367,7 +367,7 @@ The HAProxy dashboard displays the following information: - HAProxy - Backend Error Responses/Second ### Plugins -- [`haproxy` plugin](/telegraf/latest/plugins/plugin-list/#haproxy) +- [`haproxy` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#haproxy) ## NGINX @@ -379,7 +379,7 @@ The NGINX dashboard displays the following information: - NGINX - Active Client State ### Plugins -- [`nginx` plugin](/telegraf/latest/plugins/plugin-list/#nginx) +- [`nginx` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#nginx) ## Redis The Redis dashboard displays the following information: @@ -390,7 +390,7 @@ The Redis dashboard displays the following information: - Redis - Memory ### Plugins -- [`redis` plugin](/telegraf/latest/plugins/plugin-list/#redis) +- [`redis` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#redis) ## VMware vSphere VMs @@ -406,7 +406,7 @@ The VMWare vSphere VMs dashboard gives an overview of your VMware vSphere virtua - Total Disk Latency for :vmname: ### Plugins -- [`vsphere` plugin](/telegraf/latest/plugins/plugin-list/#vsphere) +- [`vsphere` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#vsphere) ## VMware vSphere Hosts @@ -422,7 +422,7 @@ The VMWare vSphere Hosts dashboard displays the following information: - Total Disk Latency for :esxhostname: ### Plugins -- [`vsphere` plugin](/telegraf/latest/plugins/plugin-list/#vsphere) +- [`vsphere` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#vsphere) ## PHPfpm The PHPfpm dashboard displays the following information: @@ -433,7 +433,7 @@ The PHPfpm dashboard displays the following information: - PHPfpm - Max Children Reached ### Plugins -- [`phpfpm` plugin](/telegraf/latest/plugins/plugin-list/#nginx) +- [`phpfpm` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#nginx) ## Win System The Win System dashboard displays the following information: @@ -445,7 +445,7 @@ The Win System dashboard displays the following information: - System - Load ### Plugins -- [`win_services` plugin](/telegraf/latest/plugins/plugin-list/#windows-services) +- [`win_services` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#windows-services) ## MySQL @@ -472,9 +472,9 @@ The MySQL dashboard displays the following information: - InnoDB Data ### Plugins -- [`mySQL` plugin](/telegraf/latest/plugins/plugin-list/#mysql) -- [`system` plugin](/telegraf/latest/plugins/plugin-list/#system) -- [`mem` plugin](/telegraf/latest/plugins/plugin-list/#mem) +- [`mySQL` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#mysql) +- [`system` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#system) +- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#mem) ## Ping The Ping dashboard displays the following information: @@ -483,4 +483,4 @@ The Ping dashboard displays the following information: - Ping - Response Times (ms) ### Plugins -- [`ping` plugin](/telegraf/latest/plugins/plugin-list/#ping) +- [`ping` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#ping) diff --git a/content/chronograf/v1.8/guides/advanced-kapacitor.md b/content/chronograf/v1.8/guides/advanced-kapacitor.md index 746b905f5..4ed6df940 100644 --- a/content/chronograf/v1.8/guides/advanced-kapacitor.md +++ b/content/chronograf/v1.8/guides/advanced-kapacitor.md @@ -13,16 +13,16 @@ menu: * [TICKscript management](#tickscript-management) -Chronograf provides a user interface for [Kapacitor](/kapacitor/latest/), InfluxData's processing framework for creating alerts, running ETL jobs, and detecting anomalies in your data. +Chronograf provides a user interface for [Kapacitor](/{{< latest "kapacitor" >}}/), InfluxData's processing framework for creating alerts, running ETL jobs, and detecting anomalies in your data. This guide offers insights into how Kapacitor interacts with Chronograf and introduces advanced Kapacitor usage within Chronograf. ## Alert history management Chronograf stores the information on the Alert History page as time series data in InfluxDB. -It stores it in the `chronograf` database and in the `alerts` [measurement](/influxdb/latest/concepts/glossary/#measurement). -By default, this data is subject to an infinite [retention policy](/influxdb/latest/concepts/glossary/#retention-policy-rp) (RP), that is, InfluxDB stores them forever. -Users who expect to have a large number of alerts and users who do not want to store their alert history forever may want to shorten the [duration](/influxdb/latest/concepts/glossary/#duration) of that retention policy. +It stores it in the `chronograf` database and in the `alerts` [measurement](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#measurement). +By default, this data is subject to an infinite [retention policy](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#retention-policy-rp) (RP), that is, InfluxDB stores them forever. +Users who expect to have a large number of alerts and users who do not want to store their alert history forever may want to shorten the [duration](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#duration) of that retention policy. ### Modifying the retention policy in Chronograf @@ -36,7 +36,7 @@ In the Databases tab: #### Step 2: Enter a different duration The minimum allowable duration is one hour (`1h`) and the maximum is infinite (`INF`). -See the InfluxDB documentation for the list of [acceptable duration units](/influxdb/latest/query_language/spec/#duration-units). +See the InfluxDB documentation for the list of [acceptable duration units](/{{< latest "influxdb" "v1" >}}/query_language/spec/#duration-units). #### Step 3: Click the green check mark to save your changes @@ -56,7 +56,7 @@ The fourth alert, which occurred on the same day at 16:58:50, is outside the pre Chronograf creates Kapacitor tasks using the information that you provide on the Rule Configuration page. It uses that information to communicate with Kapacitor and populate Chronograf alert pages. -Pre-existing tasks, or [TICKscripts](/kapacitor/latest/tick/), that you created and enabled on your Kapacitor instance without using Chronograf, have limited functionality in the user interface. +Pre-existing tasks, or [TICKscripts](/{{< latest "kapacitor" >}}/tick/), that you created and enabled on your Kapacitor instance without using Chronograf, have limited functionality in the user interface. In Chronograf, you can: diff --git a/content/chronograf/v1.8/guides/analyzing-logs.md b/content/chronograf/v1.8/guides/analyzing-logs.md index c1d1a3200..2ef6d767c 100644 --- a/content/chronograf/v1.8/guides/analyzing-logs.md +++ b/content/chronograf/v1.8/guides/analyzing-logs.md @@ -11,7 +11,7 @@ Chronograf gives you the ability to view, search, filter, visualize, and analyze This helps to recognize and diagnose patterns, then quickly dive into logged events that lead up to events. ## Logging setup -Logs data is a first class citizen in InfluxDB and is populated using available log-related [Telegraf input plugins](/telegraf/latest/plugins/inputs/): +Logs data is a first class citizen in InfluxDB and is populated using available log-related [Telegraf input plugins](/{{< latest "telegraf" >}}/plugins/inputs/): [syslog](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/syslog) diff --git a/content/chronograf/v1.8/guides/configuring-alert-endpoints.md b/content/chronograf/v1.8/guides/configuring-alert-endpoints.md index b378f41e2..8b0352b00 100644 --- a/content/chronograf/v1.8/guides/configuring-alert-endpoints.md +++ b/content/chronograf/v1.8/guides/configuring-alert-endpoints.md @@ -17,7 +17,7 @@ This guide offers step-by-step instructions for configuring Chronograf alert end ## Kapacitor event handlers supported in Chronograf -Chronograf integrates with [Kapacitor](/kapacitor/latest/), InfluxData's data processing platform, to send alert messages to event handlers. +Chronograf integrates with [Kapacitor](/{{< latest "kapacitor" >}}/), InfluxData's data processing platform, to send alert messages to event handlers. Chronograf supports the following event handlers: * Alerta @@ -39,7 +39,7 @@ Chronograf supports the following event handlers: * TCP * VictorOps -To configure a Kapacitor event handler in Chronograf, [install Kapacitor](/kapacitor/latest/introduction/installation/) and [connect it to Chronograf](/kapacitor/latest/working/kapa-and-chrono/#add-a-kapacitor-instance). +To configure a Kapacitor event handler in Chronograf, [install Kapacitor](/{{< latest "kapacitor" >}}/introduction/installation/) and [connect it to Chronograf](/{{< latest "kapacitor" >}}/working/kapa-and-chrono/#add-a-kapacitor-instance). The **Configure Kapacitor** page includes the event handler configuration options. @@ -47,10 +47,10 @@ The **Configure Kapacitor** page includes the event handler configuration option Alert endpoint configurations appear on the Chronograf Configure Kapacitor page. You must have a connected Kapacitor instance to access the configurations. -For more information, see [Kapacitor installation instructions](/kapacitor/latest/introduction/installation/) and how to [connect a Kapacitor instance](/kapacitor/latest/working/kapa-and-chrono/#add-a-kapacitor-instance) to Chronograf. +For more information, see [Kapacitor installation instructions](/{{< latest "kapacitor" >}}/introduction/installation/) and how to [connect a Kapacitor instance](/{{< latest "kapacitor" >}}/working/kapa-and-chrono/#add-a-kapacitor-instance) to Chronograf. Note that the configuration options in the **Configure alert endpoints** section are not all-inclusive. -Some event handlers allow users to customize event handler configurations per [alert rule](/chronograf/latest/guides/create-a-kapacitor-alert/). +Some event handlers allow users to customize event handler configurations per [alert rule](/{{< latest "chronograf" >}}/guides/create-a-kapacitor-alert/). For example, Chronograf's Slack integration allows users to specify a default channel in the **Configure alert endpoints** section and a different channel for individual alert rules. ### HipChat @@ -87,7 +87,7 @@ The following steps describe how to create the API access token: Your token appears in the table just above the **Create new token** section: -![HipChat token](/img/chronograf/latest/g-eventhandlers-hipchattoken.png) +![HipChat token](/img/{{< latest "chronograf" >}}/g-eventhandlers-hipchattoken.png) ### Kafka @@ -112,7 +112,7 @@ Your token appears in the table just above the **Create new token** section: 3. Click **Save Changes** to save the configuration settings. 4. Click **Send Test Alert** to verify the configuration. -See [Kafka event handler (Kapacitor)](/kapacitor/latest/event_handlers/kafka/) in the Kapacitor documentation for details about enabling OpsGenie services using TICKscripts. +See [Kafka event handler (Kapacitor)](/{{< latest "kapacitor" >}}/event_handlers/kafka/) in the Kapacitor documentation for details about enabling OpsGenie services using TICKscripts. ### OpsGenie @@ -139,9 +139,9 @@ Send an incident alert to OpsGenie teams and recipients using the Chronograf ale See [Alert API](https://docs.opsgenie.com/docs/alert-api) in the OpsGenie documentation for details on the OpsGenie Alert API -See [OpsGenie V2 event handler](/kapacitor/latest/event_handlers/opsgenie/v2/) in the Kapacitor documentation for details about the OpsGenie V2 event handler. +See [OpsGenie V2 event handler](/{{< latest "kapacitor" >}}/event_handlers/opsgenie/v2/) in the Kapacitor documentation for details about the OpsGenie V2 event handler. -See the [AlertNode (Kapacitor TICKscript node) - OpsGenie v2](/kapacitor/latest/nodes/alert_node/#opsgenie-v2) in the Kapacitor documentation for details about enabling OpsGenie services using TICKscripts. +See the [AlertNode (Kapacitor TICKscript node) - OpsGenie v2](/{{< latest "kapacitor" >}}/nodes/alert_node/#opsgenie-v2) in the Kapacitor documentation for details about enabling OpsGenie services using TICKscripts. ### PagerDuty @@ -165,7 +165,7 @@ Send an alerts about recognized events to PagerDuty using the Chronograf PagerDu See the [PagerDuty Events API V2 Overview](https://v2.developer.pagerduty.com/docs/events-api-v2) for details on the PagerDuty Events API and recognized event types (`trigger`, `acknowledge`, and `resolve`). -See [AlertNode (Kapacitor TICKscript node) - PagerDuty v2](/kapacitor/latest/nodes/alert_node/#pagerduty-v2) in the Kapacitor documentation for details about enabling a new "Generic API" service using TICKscripts. +See [AlertNode (Kapacitor TICKscript node) - PagerDuty v2](/{{< latest "kapacitor" >}}/nodes/alert_node/#pagerduty-v2) in the Kapacitor documentation for details about enabling a new "Generic API" service using TICKscripts. ### Pushover diff --git a/content/chronograf/v1.8/guides/create-a-dashboard.md b/content/chronograf/v1.8/guides/create-a-dashboard.md index 48be15156..1c2388b41 100644 --- a/content/chronograf/v1.8/guides/create-a-dashboard.md +++ b/content/chronograf/v1.8/guides/create-a-dashboard.md @@ -10,7 +10,7 @@ menu: Chronograf offers a complete dashboard solution for visualizing your data and monitoring your infrastructure: -* View [pre-created dashboards](/chronograf/latest/guides/using-precreated-dashboards) from the Host List page. Dashboards are available depending on which Telegraf input plugins you have enabled. These pre-created dashboards cannot be cloned or edited. +* View [pre-created dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards) from the Host List page. Dashboards are available depending on which Telegraf input plugins you have enabled. These pre-created dashboards cannot be cloned or edited. * Create custom dashboards from scratch by building queries in the Data Explorer, as described [below](#build-a-dashboard). * Import dashboard templates when you add or update a connection in Chronograf. See [Dashboard templates](#dashboard-templates) for details. @@ -22,7 +22,7 @@ By the end of this guide, you'll be aware of the tools available to you for crea To perform the tasks in this guide, you must have a working Chronograf instance that is connected to an InfluxDB source. Data is accessed using the Telegraf [system ](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/system) input plugins. -For more information, see [Configuring Chronograf](/chronograf/latest/administration/configuration). +For more information, see [Configuring Chronograf](/{{< latest "chronograf" >}}/administration/configuration). ## Build a dashboard @@ -42,13 +42,13 @@ to open the cell editor mode. ### Step 3: Create your query -Click the **Add a Query** button to create an [InfluxQL](/influxdb/latest/query_language/) query. +Click the **Add a Query** button to create an [InfluxQL](/{{< latest "influxdb" "v1" >}}/query_language/) query. In query editor mode, use the builder to select from your existing data and allow Chronograf to format the query for you. Alternatively, manually enter and edit a query. Chronograf allows you to move seamlessly between using the builder and manually editing the query; when possible, the interface automatically populates the builder with the information from your raw query. For our example, the query builder is used to generate a query that shows the average idle CPU usage grouped by host (in this case, there are three hosts). -By default, Chronograf applies the [`MEAN()` function](/influxdb/latest/query_language/functions/#mean) to the data, groups averages into auto-generated time intervals (`:interval:`), and shows data for the past hour (`:dashboardTime:`). +By default, Chronograf applies the [`MEAN()` function](/{{< latest "influxdb" "v1" >}}/query_language/functions/#mean) to the data, groups averages into auto-generated time intervals (`:interval:`), and shows data for the past hour (`:dashboardTime:`). Those defaults are configurable using the query builder or by manually editing the query. In addition, the time range (`:dashboardTime:` and `:upperDashboardTime:`) are [configurable on the dashboard](#step-6-configure-your-dashboard). @@ -57,7 +57,7 @@ In addition, the time range (`:dashboardTime:` and `:upperDashboardTime:`) are [ ### Step 4: Choose your visualization type -Chronograf supports many different [visualization types](/chronograf/latest/guides/visualization-types/). To choose a visualization type, click **Visualization** and select **Step-Plot Graph**. +Chronograf supports many different [visualization types](/{{< latest "chronograf" >}}/guides/visualization-types/). To choose a visualization type, click **Visualization** and select **Step-Plot Graph**. ![Visualization type](/img/chronograf/1-6-g-dashboard-visualization.png) @@ -82,7 +82,7 @@ Click **Save** (the green checkmark icon) to save your cell. * **Reset** your cell by double-clicking your mouse in the cell window > **Note:** - These tips only apply to the line, stacked, step-plot, and line+stat [visualization types](/chronograf/latest/guides/visualization-types/). + These tips only apply to the line, stacked, step-plot, and line+stat [visualization types](/{{< latest "chronograf" >}}/guides/visualization-types/). #### Configure dashboard-wide settings @@ -127,4 +127,4 @@ To exit full screen mode, press the Esc key. ### Template variables Dashboards support template variables. -See the [Dashboard Template Variables](/chronograf/latest/guides/dashboard-template-variables/) guide for more information. +See the [Dashboard Template Variables](/{{< latest "chronograf" >}}/guides/dashboard-template-variables/) guide for more information. diff --git a/content/chronograf/v1.8/guides/create-alert-rules.md b/content/chronograf/v1.8/guides/create-alert-rules.md index 8584034bc..09def2bf8 100644 --- a/content/chronograf/v1.8/guides/create-alert-rules.md +++ b/content/chronograf/v1.8/guides/create-alert-rules.md @@ -11,9 +11,9 @@ menu: --- -Chronograf provides a user interface for [Kapacitor](/kapacitor/latest/), InfluxData's processing framework for creating alerts, ETL jobs (running extract, transform, load), and detecting anomalies in your data. +Chronograf provides a user interface for [Kapacitor](/{{< latest "kapacitor" >}}/), InfluxData's processing framework for creating alerts, ETL jobs (running extract, transform, load), and detecting anomalies in your data. Chronograf alert rules correspond to Kapacitor tasks that trigger alerts whenever certain conditions are met. -Behind the scenes, these tasks are stored as [TICKscripts](/kapacitor/latest/tick/) that can be edited manually or through Chronograf. +Behind the scenes, these tasks are stored as [TICKscripts](/{{< latest "kapacitor" >}}/tick/) that can be edited manually or through Chronograf. Common alerting use cases that can be managed using Chronograf include: * Thresholds with static ceilings, floors, and ranges. @@ -26,13 +26,13 @@ This guide walks through creating a Chronograf alert rule that sends an alert me ## Requirements -[Getting started with Chronograf](/chronograf/latest/introduction/getting-started/) offers step-by-step instructions for each of the following requirements: +[Getting started with Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/) offers step-by-step instructions for each of the following requirements: * Downloaded and install the entire TICKstack (Telegraf, InfluxDB, Chronograf, and Kapacitor). * Configure Telegraf to collect data using the InfluxDB [system statistics](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/system) input plugin and write data to your InfluxDB instance. -* [Create a Kapacitor connection in Chronograf](/chronograf/latest/introduction/getting-started/#4-connect-chronograf-to-kapacitor). -* Slack is available and configured as an [event handler](/chronograf/latest/troubleshooting/frequently-asked-questions/#what-kapacitor-event-handlers-are-supported-in-chronograf) in Chronograf. -See the [Configuring Kapacitor Event Handlers](/chronograf/latest/guides/configuring-alert-endpoints/) guide for detailed configuration instructions. +* [Create a Kapacitor connection in Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/#4-connect-chronograf-to-kapacitor). +* Slack is available and configured as an [event handler](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#what-kapacitor-event-handlers-are-supported-in-chronograf) in Chronograf. +See the [Configuring Kapacitor Event Handlers](/{{< latest "chronograf" >}}/guides/configuring-alert-endpoints/) guide for detailed configuration instructions. ## Configure Chronograf alert rules @@ -70,7 +70,7 @@ For this example, select the **Threshold** alert type. Choose the time series data you want the Chronograf alert rule to use. Navigate through databases, measurements, fields, and tags to select the relevant data. -In this example, select the `telegraf` [database](/influxdb/latest/concepts/glossary/#database), the `autogen` [retention policy](/influxdb/latest/concepts/glossary/#retention-policy-rp), the `cpu` [measurement](/influxdb/latest/concepts/glossary/#measurement), and the `usage_idle` [field](/influxdb/latest/concepts/glossary/#field). +In this example, select the `telegraf` [database](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#database), the `autogen` [retention policy](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#retention-policy-rp), the `cpu` [measurement](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#measurement), and the `usage_idle` [field](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#field). ![Select your data](/img/chronograf/1-6-alerts-time-series.png) @@ -113,7 +113,7 @@ In this example, use the alert message, `Your idle CPU usage is {{.Level}} at {{ ![Specify event handler and alert message](/img/chronograf/1-6-alerts-message.png) -*View the Kapacitor documentation for more information about [message template data](/kapacitor/latest/nodes/alert_node/#message).* +*View the Kapacitor documentation for more information about [message template data](/{{< latest "kapacitor" >}}/nodes/alert_node/#message).* ### Step 7: Save the alert rule diff --git a/content/chronograf/v1.8/guides/dashboard-template-variables.md b/content/chronograf/v1.8/guides/dashboard-template-variables.md index 4590b163a..e26b19f8a 100644 --- a/content/chronograf/v1.8/guides/dashboard-template-variables.md +++ b/content/chronograf/v1.8/guides/dashboard-template-variables.md @@ -116,7 +116,7 @@ Chronograf supports the following template variable types: [Text](#text) ### Databases -Database template variables allow you to select from multiple target [databases](/influxdb/latest/concepts/glossary/#database). +Database template variables allow you to select from multiple target [databases](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#database). _**Database meta query**_ Database template variables use the following meta query to return an array of all databases in your InfluxDB instance. @@ -134,7 +134,7 @@ SELECT "purchases" FROM :databaseVar:."autogen"."customers" Database template variables are good when visualizing multiple databases with similar or identical data structures. They allow you to quickly switch between visualizations for each of your databases. ### Measurements -Vary the target [measurement](/influxdb/latest/concepts/glossary/#measurement). +Vary the target [measurement](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#measurement). _**Measurement meta query**_ Measurement template variables use the following meta query to return an array of all measurements in a given database. @@ -153,7 +153,7 @@ Measurement template variables allow you to quickly switch between measurements ### Field Keys -Vary the target [field key](/influxdb/latest/concepts/glossary/#field-key). +Vary the target [field key](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#field-key). _**Field key meta query**_ Field key template variables use the following meta query to return an array of all field keys in a given measurement from a given database. @@ -172,7 +172,7 @@ Field key template variables are great if you want to quickly switch between fie ### Tag Keys -Vary the target [tag key](/influxdb/latest/concepts/glossary/#tag-key). +Vary the target [tag key](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-key). _**Tag key meta query**_ Tag key template variables use the following meta query to return an array of all tag keys in a given measurement from a given database. @@ -191,7 +191,7 @@ Tag key template variables are great if you want to quickly switch between tag k ### Tag Values -Vary the target [tag value](/influxdb/latest/concepts/glossary/#tag-value). +Vary the target [tag value](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-value). _**Tag value meta query**_ Tag value template variables use the following meta query to return an array of all values associated with a given tag key in a specified measurement and database. @@ -223,7 +223,7 @@ value3 value4 ``` -> Since string field values [require single quotes in InfluxQL](/influxdb/latest/troubleshooting/frequently-asked-questions/#when-should-i-single-quote-and-when-should-i-double-quote-in-queries), string values should be wrapped in single quotes. +> Since string field values [require single quotes in InfluxQL](/{{< latest "influxdb" "v1" >}}/troubleshooting/frequently-asked-questions/#when-should-i-single-quote-and-when-should-i-double-quote-in-queries), string values should be wrapped in single quotes. >```csv 'string1','string2','string3','string4' @@ -254,7 +254,7 @@ key4,value4 Map variable dropdown -> If values are meant to be used as string field values, wrap them in single quote ([required by InfluxQL](/influxdb/latest/troubleshooting/frequently-asked-questions/#when-should-i-single-quote-and-when-should-i-double-quote-in-queries)). This only pertains to values. String keys do not matter. +> If values are meant to be used as string field values, wrap them in single quote ([required by InfluxQL](/{{< latest "influxdb" "v1" >}}/troubleshooting/frequently-asked-questions/#when-should-i-single-quote-and-when-should-i-double-quote-in-queries)). This only pertains to values. String keys do not matter. >```csv key1,'value1' diff --git a/content/chronograf/v1.8/guides/live_leaderboard.md b/content/chronograf/v1.8/guides/live_leaderboard.md index 81a92abbd..78e1dacbc 100644 --- a/content/chronograf/v1.8/guides/live_leaderboard.md +++ b/content/chronograf/v1.8/guides/live_leaderboard.md @@ -40,7 +40,7 @@ Add the following settings the `[[udp]]` secton in your Kapacitor configuration retention-policy = "autogen" ``` -Using this configuration, Kapacitor will listen on port `9100` for UDP packets in [Line Protocol](/influxdb/latest/write_protocols/line_protocol_tutorial/) format. +Using this configuration, Kapacitor will listen on port `9100` for UDP packets in [Line Protocol](/{{< latest "influxdb" "v1" >}}/write_protocols/line_protocol_tutorial/) format. Incoming data will be scoped to be in the `game.autogen` database and retention policy. Restart Kapacitor so that the UDP listener service starts. diff --git a/content/chronograf/v1.8/guides/monitoring-influxenterprise-clusters.md b/content/chronograf/v1.8/guides/monitoring-influxenterprise-clusters.md index f4e9a00f7..ca4b86fe2 100644 --- a/content/chronograf/v1.8/guides/monitoring-influxenterprise-clusters.md +++ b/content/chronograf/v1.8/guides/monitoring-influxenterprise-clusters.md @@ -10,20 +10,20 @@ menu: --- -[InfluxEnterprise](/enterprise_influxdb/latest/) offers high availability and a highly scalable clustering solution for your time series data needs. +[InfluxEnterprise](/{{< latest "enterprise_influxdb" >}}/) offers high availability and a highly scalable clustering solution for your time series data needs. Use Chronograf to assess your cluster's health and to monitor the infrastructure behind your project. -This guide offers step-by-step instructions for using Chronograf, [InfluxDB](/influxdb/latest/), and [Telegraf](/telegraf/latest/) to monitor data nodes in your InfluxEnterprise cluster. +This guide offers step-by-step instructions for using Chronograf, [InfluxDB](/{{< latest "influxdb" "v1" >}}/), and [Telegraf](/{{< latest "telegraf" >}}/) to monitor data nodes in your InfluxEnterprise cluster. ## Requirements You have a fully-functioning InfluxEnterprise cluster with authentication enabled. See the InfluxEnterprise documentation for -[detailed setup instructions](/enterprise_influxdb/latest/production_installation/). +[detailed setup instructions](/{{< latest "enterprise_influxdb" >}}/production_installation/). This guide uses an InfluxData Enterprise cluster with three meta nodes and three data nodes; the steps are also applicable to other cluster configurations. InfluxData recommends using a separate server to store your monitoring data. -It is possible to store the monitoring data in your cluster and [connect the cluster to Chronograf](/chronograf/latest/troubleshooting/frequently-asked-questions/#how-do-i-connect-chronograf-to-an-influxenterprise-cluster), but, in general, your monitoring data should live on a separate server. +It is possible to store the monitoring data in your cluster and [connect the cluster to Chronograf](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#how-do-i-connect-chronograf-to-an-influxenterprise-cluster), but, in general, your monitoring data should live on a separate server. You're working on an Ubuntu installation. Chronograf and the other components of the TICK stack are supported on several operating systems and hardware architectures. Check out the [downloads page](https://portal.influxdata.com/downloads) for links to the binaries of your choice. @@ -35,11 +35,11 @@ Before we begin, here's an overview of the final monitoring setup: ![Architecture diagram](/img/chronograf/1-6-cluster-diagram.png) The diagram above shows an InfluxEnterprise cluster that consists of three meta nodes (M) and three data nodes (D). -Each data node has its own [Telegraf](/telegraf/latest/) instance (T). +Each data node has its own [Telegraf](/{{< latest "telegraf" >}}/) instance (T). Each Telegraf instance is configured to collect node CPU, disk, and memory data using the Telegraf [system stats](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/system) input plugin. -The Telegraf instances are also configured to send those data to a single [InfluxDB OSS](/influxdb/latest/) instance that lives on a separate server. -When Telegraf sends data to InfluxDB, it automatically [tags](/influxdb/latest/concepts/glossary/#tag) the data with the hostname of the relevant data node. +The Telegraf instances are also configured to send those data to a single [InfluxDB OSS](/{{< latest "influxdb" "v1" >}}/) instance that lives on a separate server. +When Telegraf sends data to InfluxDB, it automatically [tags](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag) the data with the hostname of the relevant data node. The InfluxDB OSS instance that stores the Telegraf data is connected to Chronograf. Chronograf uses the hostnames in the Telegraf data to populate the Host List page and provide other hostname-specific information in the user interface. @@ -54,7 +54,7 @@ InfluxDB can be downloaded from the [InfluxData downloads page](https://portal.i #### Step 2: Enable authentication -For security purposes, enable authentication in the InfluxDB [configuration file (influxdb.conf)](/influxdb/latest/administration/config/), which is located in `/etc/influxdb/influxdb.conf`. +For security purposes, enable authentication in the InfluxDB [configuration file (influxdb.conf)](/{{< latest "influxdb" "v1" >}}/administration/config/), which is located in `/etc/influxdb/influxdb.conf`. In the `[http]` section of the configuration file, uncomment the `auth-enabled` option and set it to `true`: @@ -80,7 +80,7 @@ Next, start the InfluxDB process: #### Step 4: Create an admin user -Create an [admin user](/influxdb/latest/query_language/authentication_and_authorization/#user-types-and-privileges) on your InfluxDB instance. +Create an [admin user](/{{< latest "influxdb" "v1" >}}/query_language/authentication_and_authorization/#user-types-and-privileges) on your InfluxDB instance. Because you enabled authentication, you must perform this step before moving on to the next section. Run the command below to create an admin user, replacing `chronothan` and `supersecret` with your own username and password. Note that the password requires single quotes. @@ -204,7 +204,7 @@ Replace the `chronothan` and `supersecret` values with your actual username and ``` The expected output is similar to the JSON code block below. -In this case, the `telegraf` database has three different [tag values](/influxdb/latest/concepts/glossary/#tag-value) for the `host` [tag key](/influxdb/latest/concepts/glossary/#tag-key): `data-node-01`, `data-node-02`, and `data-node-03`. +In this case, the `telegraf` database has three different [tag values](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-value) for the `host` [tag key](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-key): `data-node-01`, `data-node-02`, and `data-node-03`. Those values match the hostnames of the three data nodes in the cluster; this means Telegraf is successfully writing monitoring data from those hosts to the InfluxDB OSS instance! ``` { @@ -284,6 +284,6 @@ In the image below, the Chronograf query editor is used to visualize the idle CP ![Data Explorer](/img/chronograf/1-6-cluster-de.png) Create more customized graphs and save them to a dashboard on the Dashboard page in Chronograf. -See the [Creating Chronograf dashboards](/chronograf/latest/guides/create-a-dashboard/) guide for more information. +See the [Creating Chronograf dashboards](/{{< latest "chronograf" >}}/guides/create-a-dashboard/) guide for more information. That's it! You've successfully configured Telegraf to collect and write data, InfluxDB to store those data, and Chonograf to use those data for monitoring and visualization purposes. diff --git a/content/chronograf/v1.8/guides/querying-data.md b/content/chronograf/v1.8/guides/querying-data.md index 3700b271b..4f0e2a296 100644 --- a/content/chronograf/v1.8/guides/querying-data.md +++ b/content/chronograf/v1.8/guides/querying-data.md @@ -7,7 +7,7 @@ menu: weight: 130 parent: Guides --- -Explore and visualize your data in the **Data Explorer**. For both InfluxQL and Flux, Chronograf allows you to move seamlessly between using the builder or templates and manually editing the query; when possible, the interface automatically populates the builder with the information from your raw query. Choose between [visualization types](/chronograf/latest/guides/visualization-types/) for your query. +Explore and visualize your data in the **Data Explorer**. For both InfluxQL and Flux, Chronograf allows you to move seamlessly between using the builder or templates and manually editing the query; when possible, the interface automatically populates the builder with the information from your raw query. Choose between [visualization types](/{{< latest "chronograf" >}}/guides/visualization-types/) for your query. To open the **Data Explorer**, click the **Explore** icon in the navigation bar: @@ -23,7 +23,7 @@ To open the **Data Explorer**, click the **Explore** icon in the navigation bar: ## Explore data with InfluxQL -InfluxQL is a SQL-like query language you can use to interact with data in InfluxDB. For detailed tutorials and reference material, see our [InfluxQL documentation](/influxdb/latest/query_language/). +InfluxQL is a SQL-like query language you can use to interact with data in InfluxDB. For detailed tutorials and reference material, see our [InfluxQL documentation](/{{< latest "influxdb" "v1" >}}/query_language/). 1. Open the Data Explorer and click **Add a Query**. 2. To the right of the source dropdown above the graph placeholder, select **InfluxQL** as the source type. @@ -66,7 +66,7 @@ Flux is InfluxData's new functional data scripting language designed for queryin ## Visualize your query -Select the **Visualization** tab at the top of the **Data Explorer**. For details about all of the available visualization options, see [Visualization types in Chronograf](/chronograf/latest/guides/visualization-types/). +Select the **Visualization** tab at the top of the **Data Explorer**. For details about all of the available visualization options, see [Visualization types in Chronograf](/{{< latest "chronograf" >}}/guides/visualization-types/). ## Add queries to dashboards diff --git a/content/chronograf/v1.8/guides/using-precreated-dashboards.md b/content/chronograf/v1.8/guides/using-precreated-dashboards.md index f729f63dc..d91253596 100644 --- a/content/chronograf/v1.8/guides/using-precreated-dashboards.md +++ b/content/chronograf/v1.8/guides/using-precreated-dashboards.md @@ -13,7 +13,7 @@ menu: Pre-created dashboards are delivered with Chronograf depending on which Telegraf input plugins you have enabled and are available from the Host List page. These dashboards, which are built in and not editable, include cells with data visualizations for metrics that are relevant to data sources you are likely to be using. -> Note that these pre-created dashboards cannot be cloned or customized. They appear only as part of the Host List view and are associated with metrics gathered from a single host. Dashboard templates are also available and deliver a solid starting point for customizing your own unique dashboards based on the Telegraf plugins enabled and operate across one or more hosts. For details, see [Dashboard templates](/chronograf/latest/guides/create-a-dashboard/#dashboard-templates). +> Note that these pre-created dashboards cannot be cloned or customized. They appear only as part of the Host List view and are associated with metrics gathered from a single host. Dashboard templates are also available and deliver a solid starting point for customizing your own unique dashboards based on the Telegraf plugins enabled and operate across one or more hosts. For details, see [Dashboard templates](/{{< latest "chronograf" >}}/guides/create-a-dashboard/#dashboard-templates). ## Requirements @@ -37,7 +37,7 @@ Find a list of apps (pre-created dashboards) available to use with Chronograf be - JSON files included in the app - Cell titles included in each JSON file -The JSON files for apps are included in the `/usr/share/chronograf/canned` directory. Find information about the configuration option `--canned-path` on the [Chronograf configuration options](/chronograf/latest/administration/config-options/) page. +The JSON files for apps are included in the `/usr/share/chronograf/canned` directory. Find information about the configuration option `--canned-path` on the [Chronograf configuration options](/{{< latest "chronograf" >}}/administration/config-options/) page. Enable and disable apps in your [Telegraf configuration file](by default, `/etc/telegraf/telegraf.conf`). See [Configuring Telegraf](/telegraf/v1.13/administration/configuration/) for details. @@ -68,7 +68,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/ ## apache -**Required Telegraf plugin:** [Apache input plugin](/telegraf/latest/plugins/inputs/#apache-http-server) +**Required Telegraf plugin:** [Apache input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#apache-http-server) `apache.json` @@ -78,7 +78,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/ ## consul -**Required Telegraf plugin:** [Consul input plugin](/telegraf/latest/plugins/inputs/#consul) +**Required Telegraf plugin:** [Consul input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#consul) `consul_http.json` @@ -98,7 +98,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/ ## docker -**Required Telegraf plugin:** [Docker input plugin](/telegraf/latest/plugins/inputs/#docker) +**Required Telegraf plugin:** [Docker input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#docker) `docker.json` @@ -118,7 +118,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/ ## elasticsearch -**Required Telegraf plugin:** [Elasticsearch input plugin](/telegraf/latest/plugins/inputs/#elasticsearch) +**Required Telegraf plugin:** [Elasticsearch input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#elasticsearch) `elasticsearch.json` @@ -135,7 +135,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/ ## haproxy -**Required Telegraf plugin:** [HAProxy input plugin](/telegraf/latest/plugins/inputs/#haproxy) +**Required Telegraf plugin:** [HAProxy input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#haproxy) `haproxy.json` @@ -165,7 +165,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/ ## influxdb -**Required Telegraf plugin:** [InfluxDB input plugin](/telegraf/latest/plugins/inputs/#influxdb-v-1) +**Required Telegraf plugin:** [InfluxDB input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#influxdb-v-1) `influxdb_database.json` @@ -210,7 +210,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/ ## Memcached (`memcached`) -**Required Telegraf plugin:** [Memcached input plugin](/telegraf/latest/plugins/inputs/#memcached) +**Required Telegraf plugin:** [Memcached input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#memcached) `memcached.json` @@ -230,7 +230,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/ ## mesos -**Required Telegraf plugin:** [Mesos input plugin](/telegraf/latest/plugins/inputs/#mesos) +**Required Telegraf plugin:** [Mesos input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#mesos) `mesos.json` @@ -245,7 +245,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/ ## mongodb -**Required Telegraf plugin:** [MongoDB input plugin](/telegraf/latest/plugins/inputs/#mongodb) +**Required Telegraf plugin:** [MongoDB input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#mongodb) `mongodb.json` @@ -257,7 +257,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/ ## mysql -**Required Telegraf plugin:** [MySQL input plugin](/telegraf/latest/plugins/inputs/#mysql) +**Required Telegraf plugin:** [MySQL input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#mysql) `mysql.json` @@ -268,7 +268,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/ ## nginx -**Required Telegraf plugin:** [NGINX input plugin](/telegraf/latest/plugins/inputs/#nginx) +**Required Telegraf plugin:** [NGINX input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#nginx) `nginx.json` @@ -279,7 +279,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/ ## nsq -**Required Telegraf plugin:** [NSQ input plugin](/telegraf/latest/plugins/inputs/#nsq) +**Required Telegraf plugin:** [NSQ input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#nsq) `nsq_channel.json` @@ -300,7 +300,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/ ## phpfpm -**Required Telegraf plugin:** [PHPfpm input plugin](/telegraf/latest/plugins/inputs/#php-fpm) +**Required Telegraf plugin:** [PHPfpm input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#php-fpm) `phpfpm.json` @@ -312,7 +312,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/ ## ping -**Required Telegraf plugin:** [Ping input plugin](/telegraf/latest/plugins/inputs/#ping) +**Required Telegraf plugin:** [Ping input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#ping) `ping.json` @@ -321,7 +321,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/ ## postgresql -**Required Telegraf plugin:** [PostgreSQL input plugin](/telegraf/latest/plugins/inputs/#postgresql) +**Required Telegraf plugin:** [PostgreSQL input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#postgresql) `postgresql.json` @@ -332,7 +332,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/ ## rabbitmq -**Required Telegraf plugin:** [RabbitMQ input plugin](/telegraf/latest/plugins/inputs/#rabbitmq) +**Required Telegraf plugin:** [RabbitMQ input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#rabbitmq) `rabbitmq.json` @@ -343,7 +343,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/ ## redis -**Required Telegraf plugin:** [Redis input plugin](/telegraf/latest/plugins/inputs/#redis) +**Required Telegraf plugin:** [Redis input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#redis) `redis.json` @@ -355,7 +355,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/ ## riak -**Required Telegraf plugin:** [Riak input plugin](/telegraf/latest/plugins/inputs/#riak) +**Required Telegraf plugin:** [Riak input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#riak) `riak.json` @@ -374,7 +374,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/ ### cpu -**Required Telegraf plugin:** [CPU input plugin](/telegraf/latest/plugins/inputs/#cpu) +**Required Telegraf plugin:** [CPU input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#cpu) `cpu.json` @@ -384,13 +384,13 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/ `disk.json` -**Required Telegraf plugin:** [Disk input plugin](/telegraf/latest/plugins/inputs/#disk) +**Required Telegraf plugin:** [Disk input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#disk) * "System - Disk used %" ### diskio -**Required Telegraf plugin:** [DiskIO input plugin](/telegraf/latest/plugins/inputs/#diskio) +**Required Telegraf plugin:** [DiskIO input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#diskio) `diskio.json` @@ -399,7 +399,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/ ### mem -**Required Telegraf plugin:** [Mem input plugin](/telegraf/latest/plugins/inputs/#mem) +**Required Telegraf plugin:** [Mem input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#mem) `mem.json` @@ -407,7 +407,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/ ### net -**Required Telegraf plugin:** [Net input plugin](/telegraf/latest/plugins/inputs/#net) +**Required Telegraf plugin:** [Net input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#net) `net.json` @@ -416,7 +416,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/ ### netstat -**Required Telegraf plugin:** [Netstat input plugin](/telegraf/latest/plugins/inputs/#netstat) +**Required Telegraf plugin:** [Netstat input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#netstat) `netstat.json` @@ -425,7 +425,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/ ### processes -**Required Telegraf plugin:** [Processes input plugin](/telegraf/latest/plugins/inputs/#processes) +**Required Telegraf plugin:** [Processes input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#processes) `processes.json` @@ -433,7 +433,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/ ### procstat -**Required Telegraf plugin:** [Procstat input plugin](/telegraf/latest/plugins/inputs/#procstat) +**Required Telegraf plugin:** [Procstat input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#procstat) `procstat.json` @@ -442,7 +442,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/ ### system -**Required Telegraf plugin:** [Procstat input plugin](/telegraf/latest/plugins/inputs/#procstat) +**Required Telegraf plugin:** [Procstat input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#procstat) `load.json` @@ -450,7 +450,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/ ## varnish -**Required Telegraf plugin:** [Varnish](/telegraf/latest/plugins/inputs/#varnish) +**Required Telegraf plugin:** [Varnish](/{{< latest "telegraf" >}}/plugins/inputs/#varnish) `varnish.json` @@ -459,7 +459,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/ ## win_system -**Required Telegraf plugin:** [Windows Performance Counters input plugin](/telegraf/latest/plugins/inputs/#windows-performance-counters) +**Required Telegraf plugin:** [Windows Performance Counters input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#windows-performance-counters) `win_cpu.json` diff --git a/content/chronograf/v1.8/guides/visualization-types.md b/content/chronograf/v1.8/guides/visualization-types.md index 29c3e7328..caa7824be 100644 --- a/content/chronograf/v1.8/guides/visualization-types.md +++ b/content/chronograf/v1.8/guides/visualization-types.md @@ -181,10 +181,10 @@ The **Single Stat** view displays the most recent value of the specified time se ![Single Stat view](/img/chronograf/1-6-viz-single-stat-selector.png) -If a cell's query includes a [`GROUP BY` tag](/influxdb/latest/query_language/data_exploration/#group-by-tags) clause, Chronograf sorts the different [series](/influxdb/latest/concepts/glossary/#series) lexicographically and shows the most recent [field value](/influxdb/latest/concepts/glossary/#field-value) associated with the first series. -For example, if a query groups by the `name` [tag key](/influxdb/latest/concepts/glossary/#tag-key) and `name` has two [tag values](/influxdb/latest/concepts/glossary/#tag-value) (`chronelda` and `chronz`), Chronograf shows the most recent field value associated with the `chronelda` series. +If a cell's query includes a [`GROUP BY` tag](/{{< latest "influxdb" "v1" >}}/query_language/data_exploration/#group-by-tags) clause, Chronograf sorts the different [series](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#series) lexicographically and shows the most recent [field value](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#field-value) associated with the first series. +For example, if a query groups by the `name` [tag key](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-key) and `name` has two [tag values](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-value) (`chronelda` and `chronz`), Chronograf shows the most recent field value associated with the `chronelda` series. -If a cell's query includes more than one [field key](/influxdb/latest/concepts/glossary/#field-key) in the [`SELECT` clause](/influxdb/latest/query_language/data_exploration/#select-clause), Chronograf returns the most recent field value associated with the first field key in the `SELECT` clause. +If a cell's query includes more than one [field key](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#field-key) in the [`SELECT` clause](/{{< latest "influxdb" "v1" >}}/query_language/data_exploration/#select-clause), Chronograf returns the most recent field value associated with the first field key in the `SELECT` clause. For example, if a query's `SELECT` clause is `SELECT "chronogiraffe","chronelda"`, Chronograf shows the most recent field value associated with the `chronogiraffe` field key. #### Single Stat Controls diff --git a/content/chronograf/v1.8/introduction/getting-started.md b/content/chronograf/v1.8/introduction/getting-started.md index d32cf446e..a52a89abf 100644 --- a/content/chronograf/v1.8/introduction/getting-started.md +++ b/content/chronograf/v1.8/introduction/getting-started.md @@ -2,7 +2,7 @@ title: Get started with Chronograf description: Get started with Chronograf. aliases: - - /chronograf/latest/introduction/getting-started/ + - /{{< latest "chronograf" >}}/introduction/getting-started/ - /chronograf/v1.8/introduction/getting_started/ menu: chronograf_1_8: @@ -12,18 +12,18 @@ menu: --- ## Overview -Chronograf allows you to quickly see data you have stored in InfluxDB so you can build robust queries and alerts. After your administrator has set up Chronograf as described in [Installing Chronograf](/chronograf/latest/introduction/installation), get started with key features using the guides below. +Chronograf allows you to quickly see data you have stored in InfluxDB so you can build robust queries and alerts. After your administrator has set up Chronograf as described in [Installing Chronograf](/{{< latest "chronograf" >}}/introduction/installation), get started with key features using the guides below. ### Data visualization -* Investigate your data by building queries using the [Data Explorer](/chronograf/latest/guides/querying-data/). -* Use [pre-created dashboards](/chronograf/latest/guides/using-precreated-dashboards/) to monitor your application data or [create your own dashboards](/chronograf/latest/guides/create-a-dashboard/). -* Customize dashboards using [template variables](/chronograf/latest/guides/dashboard-template-variables/). +* Investigate your data by building queries using the [Data Explorer](/{{< latest "chronograf" >}}/guides/querying-data/). +* Use [pre-created dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards/) to monitor your application data or [create your own dashboards](/{{< latest "chronograf" >}}/guides/create-a-dashboard/). +* Customize dashboards using [template variables](/{{< latest "chronograf" >}}/guides/dashboard-template-variables/). ### Alerting -* [Create alert rules](/chronograf/latest/guides/create-alert-rules/) to generate threshold, relative, and deadman alerts on your data. -* [View all active alerts](/chronograf/latest/guides/create-alert-rules/#step-2-view-the-alerts) on an alert dashboard. -* Use [alert endpoints](/chronograf/latest/guides/configuring-alert-endpoints/) in Chronograf to send alert messages to specific URLs and applications. +* [Create alert rules](/{{< latest "chronograf" >}}/guides/create-alert-rules/) to generate threshold, relative, and deadman alerts on your data. +* [View all active alerts](/{{< latest "chronograf" >}}/guides/create-alert-rules/#step-2-view-the-alerts) on an alert dashboard. +* Use [alert endpoints](/{{< latest "chronograf" >}}/guides/configuring-alert-endpoints/) in Chronograf to send alert messages to specific URLs and applications. ### Infrastructure monitoring -* [View all hosts](/chronograf/latest/guides/monitoring-influxenterprise-clusters/#step-4-explore-the-monitoring-data-in-chronograf) and their statuses in your infrastructure. -* [Use pre-created dashboards](/chronograf/latest/guides/using-precreated-dashboards/) to monitor your applications. +* [View all hosts](/{{< latest "chronograf" >}}/guides/monitoring-influxenterprise-clusters/#step-4-explore-the-monitoring-data-in-chronograf) and their statuses in your infrastructure. +* [Use pre-created dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards/) to monitor your applications. diff --git a/content/chronograf/v1.8/troubleshooting/_index.md b/content/chronograf/v1.8/troubleshooting/_index.md index f9beb0e44..48e9a9e9b 100644 --- a/content/chronograf/v1.8/troubleshooting/_index.md +++ b/content/chronograf/v1.8/troubleshooting/_index.md @@ -9,4 +9,4 @@ menu: Follow the link below to access Chronograf's FAQ. -## [Frequently Asked Questions](/chronograf/latest/troubleshooting/frequently-asked-questions/) +## [Frequently Asked Questions](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/) diff --git a/content/chronograf/v1.8/troubleshooting/frequently-asked-questions.md b/content/chronograf/v1.8/troubleshooting/frequently-asked-questions.md index 27bde669b..88fbe544b 100644 --- a/content/chronograf/v1.8/troubleshooting/frequently-asked-questions.md +++ b/content/chronograf/v1.8/troubleshooting/frequently-asked-questions.md @@ -9,7 +9,7 @@ menu: ## How do I connect Chronograf to an InfluxEnterprise cluster? -The connection details form requires additional information when connecting Chronograf to an [InfluxEnterprise cluster](https://docs.influxdata.com/enterprise_influxdb/latest/). +The connection details form requires additional information when connecting Chronograf to an [InfluxEnterprise cluster](/{{< latest "enterprise_influxdb" >}}/). When you enter the InfluxDB HTTP bind address in the `Connection String` input, Chronograf automatically checks if that InfluxDB instance is a data node. If it is a data node, Chronograf automatically adds the `Meta Service Connection URL` input to the connection details form. @@ -19,4 +19,4 @@ Enter the HTTP bind address of one of your cluster's meta nodes into that input Note that the example above assumes that you do not have authentication enabled. If you have authentication enabled, the form requires username and password information. -For more details about monitoring an InfluxEnterprise cluster, see the [Monitor an InfluxEnterprise Cluster](/chronograf/latest/guides/monitoring-influxenterprise-clusters/) guide. +For more details about monitoring an InfluxEnterprise cluster, see the [Monitor an InfluxEnterprise Cluster](/{{< latest "chronograf" >}}/guides/monitoring-influxenterprise-clusters/) guide. diff --git a/content/enterprise_influxdb/v1.5/about-the-project/_index.md b/content/enterprise_influxdb/v1.5/about-the-project/_index.md index 9b5f1b018..78835b345 100644 --- a/content/enterprise_influxdb/v1.5/about-the-project/_index.md +++ b/content/enterprise_influxdb/v1.5/about-the-project/_index.md @@ -23,7 +23,7 @@ Third party suppliers make no representation nor warranty with respect to such t Third party suppliers assume no liability for any claim that might arise with respect to such third party software, nor for a customer’s use of or inability to use the third party software. -In addition to [third party software incorporated in InfluxDB](http://docs.influxdata.com/influxdb/v1.5/about_the_project/#third_party), InfluxDB Enterprise incorporates the following additional third party software: +In addition to [third party software incorporated in InfluxDB](/influxdb/v1.5/about_the_project/#third_party), InfluxDB Enterprise incorporates the following additional third party software: | Third Party / Open Source Software - Description | License Type | | ---------------------------------------- | ---------------------------------------- | diff --git a/content/enterprise_influxdb/v1.5/about-the-project/release-notes-changelog.md b/content/enterprise_influxdb/v1.5/about-the-project/release-notes-changelog.md index 20d81b386..9eae77d50 100644 --- a/content/enterprise_influxdb/v1.5/about-the-project/release-notes-changelog.md +++ b/content/enterprise_influxdb/v1.5/about-the-project/release-notes-changelog.md @@ -48,7 +48,7 @@ Please see the [InfluxDB OSS release notes](/influxdb/v1.5/about_the_project/rel ## v1.5.0 [2018-03-06] > ***Note:*** This release builds off of the 1.5 release of InfluxDB OSS. Please see the [InfluxDB OSS release -> notes](https://docs.influxdata.com/influxdb/v1.5/about_the_project/releasenotes-changelog/) for more information about the InfluxDB OSS release. +> notes](/influxdb/v1.5/about_the_project/releasenotes-changelog/) for more information about the InfluxDB OSS release. For highlights of the InfluxDB 1.5 release, see [What's new in InfluxDB 1.5](/influxdb/v1.5/about_the_project/whats_new/). @@ -167,7 +167,7 @@ Please see the OSS [release notes](/influxdb/v1.3/about_the_project/releasenotes ## v1.3.4 [2017-08-23] -This release builds off of the 1.3.4 release of OSS InfluxDB. Please see the [OSS release notes](https://docs.influxdata.com/influxdb/v1.3/about_the_project/releasenotes-changelog/) for more information about the OSS releases. +This release builds off of the 1.3.4 release of OSS InfluxDB. Please see the [OSS release notes](/influxdb/v1.3/about_the_project/releasenotes-changelog/) for more information about the OSS releases. ### Bug fixes @@ -175,7 +175,7 @@ This release builds off of the 1.3.4 release of OSS InfluxDB. Please see the [OS ## v1.3.3 [2017-08-10] -This release builds off of the 1.3.3 release of OSS InfluxDB. Please see the [OSS release notes](https://docs.influxdata.com/influxdb/v1.3/about_the_project/releasenotes-changelog/) for more information about the OSS releases. +This release builds off of the 1.3.3 release of OSS InfluxDB. Please see the [OSS release notes](/influxdb/v1.3/about_the_project/releasenotes-changelog/) for more information about the OSS releases. ### Bug fixes @@ -540,4 +540,4 @@ Backup and restore has been updated to fix issues and refine existing capabiliti The Enterprise Web Console has officially been deprecated and will be eliminated entirely by the end of 2017. No additional features will be added and no additional bug fix releases are planned. -For browser-based access to InfluxDB Enterprise, [Chronograf](/chronograf/latest/introduction) is now the recommended tool to use. +For browser-based access to InfluxDB Enterprise, [Chronograf](/{{< latest "chronograf" >}}/introduction) is now the recommended tool to use. diff --git a/content/enterprise_influxdb/v1.5/concepts/clustering.md b/content/enterprise_influxdb/v1.5/concepts/clustering.md index 41abaad17..7da493082 100644 --- a/content/enterprise_influxdb/v1.5/concepts/clustering.md +++ b/content/enterprise_influxdb/v1.5/concepts/clustering.md @@ -90,7 +90,7 @@ Data nodes hold the actual time series data. The minimum number of data nodes to ## Chronograf -[Chronograf](/chronograf/latest/introduction/getting-started/) is the user interface component of InfluxData’s TICK stack. +[Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/) is the user interface component of InfluxData’s TICK stack. It makes owning the monitoring and alerting for your infrastructure easy to setup and maintain. It talks directly to the data and meta nodes over their HTTP protocols, which are bound by default to ports `8086` for data nodes and port `8091` for meta nodes. diff --git a/content/enterprise_influxdb/v1.5/concepts/glossary.md b/content/enterprise_influxdb/v1.5/concepts/glossary.md index 7660bb5ac..1783f8352 100644 --- a/content/enterprise_influxdb/v1.5/concepts/glossary.md +++ b/content/enterprise_influxdb/v1.5/concepts/glossary.md @@ -72,6 +72,6 @@ query capacity within the cluster. Legacy user interface for the InfluxEnterprise cluster. -This has been deprecated and the suggestion is to use [Chronograf](/chronograf/latest/introduction/). +This has been deprecated and the suggestion is to use [Chronograf](/{{< latest "chronograf" >}}/introduction/). -If you are transitioning from the Enterprise Web Console to Chronograf and helpful [transition guide](/chronograf/latest/guides/transition-web-admin-interface/) is available. +If you are transitioning from the Enterprise Web Console to Chronograf and helpful [transition guide](/{{< latest "chronograf" >}}/guides/transition-web-admin-interface/) is available. diff --git a/content/enterprise_influxdb/v1.5/guides/migration.md b/content/enterprise_influxdb/v1.5/guides/migration.md index 15c96b6f4..484cf02a8 100644 --- a/content/enterprise_influxdb/v1.5/guides/migration.md +++ b/content/enterprise_influxdb/v1.5/guides/migration.md @@ -208,7 +208,7 @@ You can do this with [ALTER RETENTION POLICY](/influxdb/v1.5/query_language/data Next, [rebalance](/enterprise_influxdb/v1.5/guides/rebalance/) your cluster manually to meet the desired replication factor for existing shards. -Finally, if you were using [Chronograf](/chronograf/latest/), you can +Finally, if you were using [Chronograf](/{{< latest "chronograf" >}}/), you can add your Enterprise instance as a new data source. If you were not using -[Chronograf](/chronograf/latest/introduction/installation/), we recommend going through +[Chronograf](/{{< latest "chronograf" >}}/introduction/installation/), we recommend going through the installation instructions and using it as your primary management UI for the instance. --> diff --git a/content/enterprise_influxdb/v1.5/introduction/getting-started.md b/content/enterprise_influxdb/v1.5/introduction/getting-started.md index 45e438a4d..32709bc35 100644 --- a/content/enterprise_influxdb/v1.5/introduction/getting-started.md +++ b/content/enterprise_influxdb/v1.5/introduction/getting-started.md @@ -10,9 +10,9 @@ menu: parent: Introduction --- -Now that you successfully [installed and set up](/enterprise_influxdb/v1.5/introduction/meta_node_installation/) InfluxDB Enterprise, you can configure Chronograf for [monitoring InfluxDB Enterprise clusters](/chronograf/latest/guides/monitor-an-influxenterprise-cluster/). +Now that you successfully [installed and set up](/enterprise_influxdb/v1.5/introduction/meta_node_installation/) InfluxDB Enterprise, you can configure Chronograf for [monitoring InfluxDB Enterprise clusters](/{{< latest "chronograf" >}}/guides/monitor-an-influxenterprise-cluster/). -See [Getting started with Chronograf](/chronograf/latest/introduction/getting-started/) to learn more about using Chronograf with the InfluxData time series platform. +See [Getting started with Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/) to learn more about using Chronograf with the InfluxData time series platform. ### Where to from here? diff --git a/content/enterprise_influxdb/v1.5/introduction/installation_guidelines.md b/content/enterprise_influxdb/v1.5/introduction/installation_guidelines.md index 60cf3f241..d1410eca8 100644 --- a/content/enterprise_influxdb/v1.5/introduction/installation_guidelines.md +++ b/content/enterprise_influxdb/v1.5/introduction/installation_guidelines.md @@ -3,7 +3,7 @@ title: Installation options (⏰ Please Read!) aliases: - /enterprise_influxdb/v1.5/introduction/meta_node_installation/ - /enterprise_influxdb/v1.5/introduction/data_node_installation/ - - /chronograf/latest/introduction/installation + - /{{< latest "chronograf" >}}/introduction/installation - /enterprise/v1.5/introduction/installation_guidelines/ menu: enterprise_influxdb_1_5: diff --git a/content/enterprise_influxdb/v1.5/production_installation/chrono_install.md b/content/enterprise_influxdb/v1.5/production_installation/chrono_install.md index 4f30eb3ca..c01b94966 100644 --- a/content/enterprise_influxdb/v1.5/production_installation/chrono_install.md +++ b/content/enterprise_influxdb/v1.5/production_installation/chrono_install.md @@ -12,4 +12,4 @@ menu: Now that you've installed the meta nodes and data nodes, you are ready to install Chronograf to provide you with a user interface to access the InfluxDB Enterprise instance. -[Installation instruction for Chronograf](/chronograf/latest/introduction/installation/) +[Installation instruction for Chronograf](/{{< latest "chronograf" >}}/introduction/installation/) diff --git a/content/enterprise_influxdb/v1.5/production_installation/meta_node_installation.md b/content/enterprise_influxdb/v1.5/production_installation/meta_node_installation.md index dd0d4c3e1..2924c61d8 100644 --- a/content/enterprise_influxdb/v1.5/production_installation/meta_node_installation.md +++ b/content/enterprise_influxdb/v1.5/production_installation/meta_node_installation.md @@ -10,7 +10,7 @@ menu: --- InfluxDB Enterprise offers highly scalable clusters on your infrastructure -and a management user interface ([using Chronograf](https://docs.influxdata.com/chronograf/latest)) for working with clusters. +and a management user interface ([using Chronograf](/{{< latest "chronograf" >}})) for working with clusters. The Production Installation process is designed for users looking to deploy InfluxDB Enterprise in a production environment. The following steps will get you up and running with the first essential component of diff --git a/content/enterprise_influxdb/v1.5/quickstart_installation/chrono_install.md b/content/enterprise_influxdb/v1.5/quickstart_installation/chrono_install.md index 735411538..3b50f2fd5 100644 --- a/content/enterprise_influxdb/v1.5/quickstart_installation/chrono_install.md +++ b/content/enterprise_influxdb/v1.5/quickstart_installation/chrono_install.md @@ -11,4 +11,4 @@ menu: Now that you've installed the meta nodes and data nodes, you are ready to install Chronograf to provide you with a user interface to access the InfluxDB Enterprise instance. -[Installing Chronograf](/chronograf/latest/introduction/installation/) +[Installing Chronograf](/{{< latest "chronograf" >}}/introduction/installation/) diff --git a/content/enterprise_influxdb/v1.5/quickstart_installation/cluster_installation.md b/content/enterprise_influxdb/v1.5/quickstart_installation/cluster_installation.md index 489e500a9..1835792f8 100644 --- a/content/enterprise_influxdb/v1.5/quickstart_installation/cluster_installation.md +++ b/content/enterprise_influxdb/v1.5/quickstart_installation/cluster_installation.md @@ -193,7 +193,7 @@ First, in `/etc/influxdb/influxdb.conf`, uncomment: * `shared-secret` in the `[http]` section and set it to a long pass phrase that will be used to sign tokens for intra-cluster communication. This value needs to be consistent across all data nodes. > **Note:** When you enable authentication, InfluxDB only executes HTTP requests that are sent with valid credentials. -See the [authentication section](/influxdb/latest/administration/authentication_and_authorization/#authentication) for more information. +See the [authentication section](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#authentication) for more information. Second, in `/etc/influxdb/influxdb.conf`, set: diff --git a/content/enterprise_influxdb/v1.6/about-the-project/_index.md b/content/enterprise_influxdb/v1.6/about-the-project/_index.md index f928eab11..f2e192dc2 100644 --- a/content/enterprise_influxdb/v1.6/about-the-project/_index.md +++ b/content/enterprise_influxdb/v1.6/about-the-project/_index.md @@ -22,7 +22,7 @@ Third party suppliers make no representation nor warranty with respect to such t Third party suppliers assume no liability for any claim that might arise with respect to such third party software, nor for a customer’s use of or inability to use the third party software. -In addition to [third party software incorporated in InfluxDB](http://docs.influxdata.com/influxdb/v1.6/about_the_project/#third_party), InfluxDB Enterprise incorporates the following additional third party software: +In addition to [third party software incorporated in InfluxDB](/influxdb/v1.6/about_the_project/#third_party), InfluxDB Enterprise incorporates the following additional third party software: | Third Party / Open Source Software - Description | License Type | | ---------------------------------------- | ---------------------------------------- | diff --git a/content/enterprise_influxdb/v1.6/about-the-project/release-notes-changelog.md b/content/enterprise_influxdb/v1.6/about-the-project/release-notes-changelog.md index 960c4076b..08d84e7ae 100644 --- a/content/enterprise_influxdb/v1.6/about-the-project/release-notes-changelog.md +++ b/content/enterprise_influxdb/v1.6/about-the-project/release-notes-changelog.md @@ -134,7 +134,7 @@ Please see the [InfluxDB OSS release notes](/influxdb/v1.6/about_the_project/rel ## v1.5.0 [2018-03-06] > ***Note:*** This release builds off of the 1.5 release of InfluxDB OSS. Please see the [InfluxDB OSS release -> notes](https://docs.influxdata.com/influxdb/v1.6/about_the_project/releasenotes-changelog/) for more information about the InfluxDB OSS release. +> notes](/influxdb/v1.6/about_the_project/releasenotes-changelog/) for more information about the InfluxDB OSS release. For highlights of the InfluxDB 1.5 release, see [What's new in InfluxDB 1.5](/influxdb/v1.5/about_the_project/whats_new/). @@ -253,7 +253,7 @@ Please see the OSS [release notes](/influxdb/v1.3/about_the_project/releasenotes ## v1.3.4 [2017-08-23] -This release builds off of the 1.3.4 release of OSS InfluxDB. Please see the [OSS release notes](https://docs.influxdata.com/influxdb/v1.3/about_the_project/releasenotes-changelog/) for more information about the OSS releases. +This release builds off of the 1.3.4 release of OSS InfluxDB. Please see the [OSS release notes](/influxdb/v1.3/about_the_project/releasenotes-changelog/) for more information about the OSS releases. ### Bugfixes @@ -261,7 +261,7 @@ This release builds off of the 1.3.4 release of OSS InfluxDB. Please see the [OS ## v1.3.3 [2017-08-10] -This release builds off of the 1.3.3 release of OSS InfluxDB. Please see the [OSS release notes](https://docs.influxdata.com/influxdb/v1.3/about_the_project/releasenotes-changelog/) for more information about the OSS releases. +This release builds off of the 1.3.3 release of OSS InfluxDB. Please see the [OSS release notes](/influxdb/v1.3/about_the_project/releasenotes-changelog/) for more information about the OSS releases. ### Bugfixes @@ -626,4 +626,4 @@ Backup and restore has been updated to fix issues and refine existing capabiliti The Enterprise Web Console has officially been deprecated and will be eliminated entirely by the end of 2017. No additional features will be added and no additional bug fix releases are planned. -For browser-based access to InfluxDB Enterprise, [Chronograf](/chronograf/latest/introduction) is now the recommended tool to use. +For browser-based access to InfluxDB Enterprise, [Chronograf](/{{< latest "chronograf" >}}/introduction) is now the recommended tool to use. diff --git a/content/enterprise_influxdb/v1.6/concepts/clustering.md b/content/enterprise_influxdb/v1.6/concepts/clustering.md index cbff1e76e..00e9249a0 100644 --- a/content/enterprise_influxdb/v1.6/concepts/clustering.md +++ b/content/enterprise_influxdb/v1.6/concepts/clustering.md @@ -90,7 +90,7 @@ Data nodes hold the actual time series data. The minimum number of data nodes to ## Chronograf -[Chronograf](/chronograf/latest/introduction/getting-started/) is the user interface component of InfluxData’s TICK stack. +[Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/) is the user interface component of InfluxData’s TICK stack. It makes owning the monitoring and alerting for your infrastructure easy to setup and maintain. It talks directly to the data and meta nodes over their HTTP protocols, which are bound by default to ports `8086` for data nodes and port `8091` for meta nodes. diff --git a/content/enterprise_influxdb/v1.6/concepts/glossary.md b/content/enterprise_influxdb/v1.6/concepts/glossary.md index d0ae076fc..f0a767011 100644 --- a/content/enterprise_influxdb/v1.6/concepts/glossary.md +++ b/content/enterprise_influxdb/v1.6/concepts/glossary.md @@ -71,6 +71,6 @@ query capacity within the cluster. Legacy user interface for the InfluxDB Enterprise. -This has been deprecated and the suggestion is to use [Chronograf](/chronograf/latest/introduction/). +This has been deprecated and the suggestion is to use [Chronograf](/{{< latest "chronograf" >}}/introduction/). -If you are transitioning from the Enterprise Web Console to Chronograf and helpful [transition guide](/chronograf/latest/guides/transition-web-admin-interface/) is available. +If you are transitioning from the Enterprise Web Console to Chronograf and helpful [transition guide](/{{< latest "chronograf" >}}/guides/transition-web-admin-interface/) is available. diff --git a/content/enterprise_influxdb/v1.6/features/clustering-features.md b/content/enterprise_influxdb/v1.6/features/clustering-features.md index dfb016c2b..f8e2a75b3 100644 --- a/content/enterprise_influxdb/v1.6/features/clustering-features.md +++ b/content/enterprise_influxdb/v1.6/features/clustering-features.md @@ -69,7 +69,7 @@ you should set the lease-duration to a value greater than the aggregate executio Based on the current way in which CQs are configured to execute, the way to address parallelism is by using Kapacitor for the more complex CQs that you are attempting to run. -[See Kapacitor as a continuous query engine](/kapacitor/latest/guides/continuous_queries/). +[See Kapacitor as a continuous query engine](/{{< latest "kapacitor" >}}/guides/continuous_queries/). However, you can keep the more simplistic and highly performant CQs within the database – but ensure that the lease duration is greater than their aggregate execution time to ensure that “extra” load is not being unnecessarily introduced on your cluster. diff --git a/content/enterprise_influxdb/v1.6/guides/https_setup.md b/content/enterprise_influxdb/v1.6/guides/https_setup.md index 3d2ca649b..c77d34017 100644 --- a/content/enterprise_influxdb/v1.6/guides/https_setup.md +++ b/content/enterprise_influxdb/v1.6/guides/https_setup.md @@ -312,7 +312,7 @@ enterprise-meta-03:8091 1.x.y-c1.x.z ``` -Next, verify that HTTPS is working by connecting to InfluxDB Enterprise with the [CLI tool](/influxdb/latest/tools/shell/): +Next, verify that HTTPS is working by connecting to InfluxDB Enterprise with the [CLI tool](/{{< latest "influxdb" "v1" >}}/tools/shell/): ``` influx -ssl -unsafeSsl -host .com ``` @@ -329,7 +329,7 @@ That's it! You've successfully set up HTTPS with InfluxDB Enterprise. ## Connect Telegraf to a secured InfluxDB Enterprise instance -Connecting [Telegraf](/telegraf/latest/) to an InfluxDB Enterprise instance that's using +Connecting [Telegraf](/{{< latest "telegraf" >}}/) to an InfluxDB Enterprise instance that's using HTTPS requires some additional steps. In Telegraf's configuration file (`/etc/telegraf/telegraf.conf`), under the OUTPUT PLUGINS section, edit the `urls` diff --git a/content/enterprise_influxdb/v1.6/guides/migration.md b/content/enterprise_influxdb/v1.6/guides/migration.md index cfac691a7..3a17823d5 100644 --- a/content/enterprise_influxdb/v1.6/guides/migration.md +++ b/content/enterprise_influxdb/v1.6/guides/migration.md @@ -208,7 +208,7 @@ You can do this with [ALTER RETENTION POLICY](/influxdb/v1.6/query_language/data Next, [rebalance](/enterprise_influxdb/v1.6/guides/rebalance/) your cluster manually to meet the desired replication factor for existing shards. -Finally, if you were using [Chronograf](/chronograf/latest/), you can +Finally, if you were using [Chronograf](/{{< latest "chronograf" >}}/), you can add your Enterprise instance as a new data source. If you were not using -[Chronograf](/chronograf/latest/introduction/installation/), we recommend going through +[Chronograf](/{{< latest "chronograf" >}}/introduction/installation/), we recommend going through the installation instructions and using it as your primary management UI for the instance. --> diff --git a/content/enterprise_influxdb/v1.6/install-and-deploy/production_installation/chrono_install.md b/content/enterprise_influxdb/v1.6/install-and-deploy/production_installation/chrono_install.md index f88ca7962..369f0aaf0 100644 --- a/content/enterprise_influxdb/v1.6/install-and-deploy/production_installation/chrono_install.md +++ b/content/enterprise_influxdb/v1.6/install-and-deploy/production_installation/chrono_install.md @@ -13,4 +13,4 @@ menu: Now that you've installed the meta nodes and data nodes, you are ready to install Chronograf to provide you with a user interface to access the InfluxDB Enterprise instance. -[Installation instruction for Chronograf](/chronograf/latest/introduction/installation/) +[Installation instruction for Chronograf](/{{< latest "chronograf" >}}/introduction/installation/) diff --git a/content/enterprise_influxdb/v1.6/install-and-deploy/production_installation/meta_node_installation.md b/content/enterprise_influxdb/v1.6/install-and-deploy/production_installation/meta_node_installation.md index 74ca28d61..1480f9203 100644 --- a/content/enterprise_influxdb/v1.6/install-and-deploy/production_installation/meta_node_installation.md +++ b/content/enterprise_influxdb/v1.6/install-and-deploy/production_installation/meta_node_installation.md @@ -10,7 +10,7 @@ menu: --- InfluxDB Enterprise offers highly scalable clusters on your infrastructure -and a management UI ([via Chronograf](https://docs.influxdata.com/chronograf/latest) for working with clusters. +and a management UI ([via Chronograf](/{{< latest "chronograf" >}}) for working with clusters. The Production Installation process is designed for users looking to deploy InfluxDB Enterprise in a production environment. The following steps will get you up and running with the first essential component of diff --git a/content/enterprise_influxdb/v1.6/introduction/getting-started.md b/content/enterprise_influxdb/v1.6/introduction/getting-started.md index b9a0b657c..4be7f2b22 100644 --- a/content/enterprise_influxdb/v1.6/introduction/getting-started.md +++ b/content/enterprise_influxdb/v1.6/introduction/getting-started.md @@ -10,9 +10,9 @@ menu: parent: Introduction --- -Now that you successfully [installed and set up](/enterprise_influxdb/v1.6/introduction/meta_node_installation/) InfluxDB Enterprise, use [Chronograf to setup your cluster as a data source.](/chronograf/latest/guides/monitor-an-influxenterprise-cluster/) +Now that you successfully [installed and set up](/enterprise_influxdb/v1.6/introduction/meta_node_installation/) InfluxDB Enterprise, use [Chronograf to setup your cluster as a data source.](/{{< latest "chronograf" >}}/guides/monitor-an-influxenterprise-cluster/) -More details on leveraging [Chronograf and getting started are available.](/chronograf/latest/introduction/getting-started/) +More details on leveraging [Chronograf and getting started are available.](/{{< latest "chronograf" >}}/introduction/getting-started/) ### Where to from here? diff --git a/content/enterprise_influxdb/v1.6/introduction/installation_guidelines.md b/content/enterprise_influxdb/v1.6/introduction/installation_guidelines.md index 8cec35352..e6f7cc09f 100644 --- a/content/enterprise_influxdb/v1.6/introduction/installation_guidelines.md +++ b/content/enterprise_influxdb/v1.6/introduction/installation_guidelines.md @@ -3,7 +3,7 @@ title: Installation options (⏰ Please Read!) aliases: - /enterprise_influxdb/v1.6/introduction/meta_node_installation/ - /enterprise_influxdb/v1.6/introduction/data_node_installation/ - - /chronograf/latest/introduction/installation + - /{{< latest "chronograf" >}}/introduction/installation - /enterprise/v1.6/introduction/installation_guidelines/ menu: enterprise_influxdb_1_6: diff --git a/content/enterprise_influxdb/v1.7/about-the-project/release-notes-changelog.md b/content/enterprise_influxdb/v1.7/about-the-project/release-notes-changelog.md index 2c733a471..e59339360 100644 --- a/content/enterprise_influxdb/v1.7/about-the-project/release-notes-changelog.md +++ b/content/enterprise_influxdb/v1.7/about-the-project/release-notes-changelog.md @@ -283,7 +283,7 @@ Please see the [InfluxDB OSS release notes](/influxdb/v1.7/about_the_project/rel ## v1.5.0 [2018-03-06] > ***Note:*** This release builds off of the 1.5 release of InfluxDB OSS. Please see the [InfluxDB OSS release -> notes](https://docs.influxdata.com/influxdb/v1.5/about_the_project/releasenotes-changelog/) for more information about the InfluxDB OSS release. +> notes](/influxdb/v1.5/about_the_project/releasenotes-changelog/) for more information about the InfluxDB OSS release. For highlights of the InfluxDB 1.5 release, see [What's new in InfluxDB 1.5](/influxdb/v1.5/about_the_project/whats_new/). @@ -402,7 +402,7 @@ Please see the OSS [release notes](/influxdb/v1.3/about_the_project/releasenotes ## v1.3.4 [2017-08-23] -This release builds off of the 1.3.4 release of OSS InfluxDB. Please see the [OSS release notes](https://docs.influxdata.com/influxdb/v1.3/about_the_project/releasenotes-changelog/) for more information about the OSS releases. +This release builds off of the 1.3.4 release of OSS InfluxDB. Please see the [OSS release notes](/influxdb/v1.3/about_the_project/releasenotes-changelog/) for more information about the OSS releases. ### Bugfixes @@ -410,7 +410,7 @@ This release builds off of the 1.3.4 release of OSS InfluxDB. Please see the [OS ## v1.3.3 [2017-08-10] -This release builds off of the 1.3.3 release of OSS InfluxDB. Please see the [OSS release notes](https://docs.influxdata.com/influxdb/v1.3/about_the_project/releasenotes-changelog/) for more information about the OSS releases. +This release builds off of the 1.3.3 release of OSS InfluxDB. Please see the [OSS release notes](/influxdb/v1.3/about_the_project/releasenotes-changelog/) for more information about the OSS releases. ### Bugfixes @@ -775,4 +775,4 @@ Backup and restore has been updated to fix issues and refine existing capabiliti The Enterprise Web Console has officially been deprecated and will be eliminated entirely by the end of 2017. No additional features will be added and no additional bug fix releases are planned. -For browser-based access to InfluxDB Enterprise, [Chronograf](/chronograf/latest/introduction) is now the recommended tool to use. +For browser-based access to InfluxDB Enterprise, [Chronograf](/{{< latest "chronograf" >}}/introduction) is now the recommended tool to use. diff --git a/content/enterprise_influxdb/v1.7/administration/backup-and-restore.md b/content/enterprise_influxdb/v1.7/administration/backup-and-restore.md index 5ed854ec0..0c21eeb61 100644 --- a/content/enterprise_influxdb/v1.7/administration/backup-and-restore.md +++ b/content/enterprise_influxdb/v1.7/administration/backup-and-restore.md @@ -380,13 +380,13 @@ Use the InfluxDB `influx_inspect export` and `influx -import` commands to create ### Export data -Use the [`influx_inspect export` command](/influxdb/latest/tools/influx_inspect#export) to export data in line protocol format from your InfluxDB Enterprise cluster. Options include: +Use the [`influx_inspect export` command](/{{< latest "influxdb" "v1" >}}/tools/influx_inspect#export) to export data in line protocol format from your InfluxDB Enterprise cluster. Options include: - Exporting all, or specific, databases - Filtering with starting and ending timestamps - Using gzip compression for smaller files and faster exports -For details on optional settings and usage, see [`influx_inspect export` command](/influxdb/latest/tools/influx_inspect#export). +For details on optional settings and usage, see [`influx_inspect export` command](/{{< latest "influxdb" "v1" >}}/tools/influx_inspect#export). In the following example, the database is exported filtered to include only one day and compressed for optimal speed and file size. @@ -396,7 +396,7 @@ influx_inspect export -database myDB -compress -start 2019-05-19T00:00:00.000Z - ### Import data -After exporting the data in line protocol format, you can import the data using the [`influx -import` CLI command](https://docs.influxdata.com/influxdb/latest/tools/shell/#import). +After exporting the data in line protocol format, you can import the data using the [`influx -import` CLI command](/{{< latest "influxdb" "v1" >}}/tools/shell/#import). In the following example, the compressed data file is imported into the specified database. @@ -404,7 +404,7 @@ In the following example, the compressed data file is imported into the specifie influx -import -database myDB -compress ``` -For details on using the `influx -import` command, see [Import data from a file with -import](https://docs.influxdata.com/influxdb/latest/tools/shell/#import-data-from-a-file-with-import). +For details on using the `influx -import` command, see [Import data from a file with -import](/{{< latest "influxdb" "v1" >}}/tools/shell/#import-data-from-a-file-with-import). ## Take AWS snapshots as backup diff --git a/content/enterprise_influxdb/v1.7/administration/upgrading.md b/content/enterprise_influxdb/v1.7/administration/upgrading.md index 842884298..32e6d527d 100644 --- a/content/enterprise_influxdb/v1.7/administration/upgrading.md +++ b/content/enterprise_influxdb/v1.7/administration/upgrading.md @@ -164,7 +164,7 @@ sudo yum localinstall influxdb-data-1.7.10_c1.7.10.x86_64.rpm Migrate any custom settings from your previous data node configuration file. -- To enable HTTPS, see [Enable HTTPS within the configuration file for each Data Node](https://docs.influxdata.com/enterprise_influxdb/v1.7/guides/https_setup/#step-4-enable-https-within-the-configuration-file-for-each-data-node). +- To enable HTTPS, see [Enable HTTPS within the configuration file for each Data Node](/enterprise_influxdb/v1.7/guides/https_setup/#step-4-enable-https-within-the-configuration-file-for-each-data-node). - To enable TSI, open `/etc/influxdb/influxdb.conf`, and then adjust and save the settings shown in the following table. diff --git a/content/enterprise_influxdb/v1.7/concepts/clustering.md b/content/enterprise_influxdb/v1.7/concepts/clustering.md index 053fda719..5714420aa 100644 --- a/content/enterprise_influxdb/v1.7/concepts/clustering.md +++ b/content/enterprise_influxdb/v1.7/concepts/clustering.md @@ -90,7 +90,7 @@ Data nodes hold the actual time series data. The minimum number of data nodes to ## Chronograf -[Chronograf](/chronograf/latest/introduction/getting-started/) is the user interface component of InfluxData’s TICK stack. +[Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/) is the user interface component of InfluxData’s TICK stack. It makes owning the monitoring and alerting for your infrastructure easy to setup and maintain. It talks directly to the data and meta nodes over their HTTP protocols, which are bound by default to ports `8086` for data nodes and port `8091` for meta nodes. diff --git a/content/enterprise_influxdb/v1.7/concepts/glossary.md b/content/enterprise_influxdb/v1.7/concepts/glossary.md index 4fa5ad8af..6a924c9c7 100644 --- a/content/enterprise_influxdb/v1.7/concepts/glossary.md +++ b/content/enterprise_influxdb/v1.7/concepts/glossary.md @@ -68,6 +68,6 @@ Related entries: [cluster](/influxdb/v0.10/concepts/glossary/#cluster), [duratio Legacy user interface for the InfluxDB Enterprise. -This has been deprecated and the suggestion is to use [Chronograf](/chronograf/latest/introduction/). +This has been deprecated and the suggestion is to use [Chronograf](/{{< latest "chronograf" >}}/introduction/). -If you are transitioning from the Enterprise Web Console to Chronograf and helpful [transition guide](/chronograf/latest/guides/transition-web-admin-interface/) is available. +If you are transitioning from the Enterprise Web Console to Chronograf and helpful [transition guide](/{{< latest "chronograf" >}}/guides/transition-web-admin-interface/) is available. diff --git a/content/enterprise_influxdb/v1.7/features/clustering-features.md b/content/enterprise_influxdb/v1.7/features/clustering-features.md index c6a40ccb1..9114acbb9 100644 --- a/content/enterprise_influxdb/v1.7/features/clustering-features.md +++ b/content/enterprise_influxdb/v1.7/features/clustering-features.md @@ -69,7 +69,7 @@ you should set the lease-duration to a value greater than the aggregate executio Based on the current way in which CQs are configured to execute, the way to address parallelism is by using Kapacitor for the more complex CQs that you are attempting to run. -[See Kapacitor as a continuous query engine](/kapacitor/latest/guides/continuous_queries/). +[See Kapacitor as a continuous query engine](/{{< latest "kapacitor" >}}/guides/continuous_queries/). However, you can keep the more simplistic and highly performant CQs within the database – but ensure that the lease duration is greater than their aggregate execution time to ensure that “extra” load is not being unnecessarily introduced on your cluster. diff --git a/content/enterprise_influxdb/v1.7/guides/fine-grained-authorization.md b/content/enterprise_influxdb/v1.7/guides/fine-grained-authorization.md index 6276f2da6..6f31cad66 100644 --- a/content/enterprise_influxdb/v1.7/guides/fine-grained-authorization.md +++ b/content/enterprise_influxdb/v1.7/guides/fine-grained-authorization.md @@ -159,7 +159,7 @@ curl -s -L -XPOST "http://localhost:8091/role" \ ### Remove role permissions To remove permissions from a role, use the InfluxDB Meta API `/role` endpoint with the `action` field set to `remove-permissions`. -Specify the [permissions](https://docs.influxdata.com/chronograf/latest/administration/managing-influxdb-users/#permissions) to remove from each database. +Specify the [permissions](/{{< latest "chronograf" >}}/administration/managing-influxdb-users/#permissions) to remove from each database. The following example removes read and write permissions from `db1` for the `east` role. @@ -583,7 +583,7 @@ curl -s -L -XPOST "http://localhost:8091/influxdb/v2/acl/grants" \ }' ``` -Grants for specific series also apply to [meta queries](https://docs.influxdata.com/influxdb/v1.7/query_language/schema_exploration). +Grants for specific series also apply to [meta queries](/influxdb/v1.7/query_language/schema_exploration). Results from meta queries are restricted based on series-level permissions. For example, `SHOW TAG VALUES` only returns tag values that the user is authorized to see. diff --git a/content/enterprise_influxdb/v1.7/guides/https_setup.md b/content/enterprise_influxdb/v1.7/guides/https_setup.md index d69241897..d688f24cc 100644 --- a/content/enterprise_influxdb/v1.7/guides/https_setup.md +++ b/content/enterprise_influxdb/v1.7/guides/https_setup.md @@ -245,7 +245,7 @@ With a self-signed certificate, you must also use the `-k` option to skip certif ## Connect Telegraf to a secured InfluxDB Enterprise instance -Connecting [Telegraf](/telegraf/latest/) +Connecting [Telegraf](/{{< latest "telegraf" >}}/) to an HTTPS-enabled InfluxDB Enterprise instance requires some additional steps. In Telegraf's configuration file (`/etc/telegraf/telegraf.conf`), under the OUTPUT PLUGINS section, diff --git a/content/enterprise_influxdb/v1.7/guides/migration.md b/content/enterprise_influxdb/v1.7/guides/migration.md index df9f9940b..2b9529042 100644 --- a/content/enterprise_influxdb/v1.7/guides/migration.md +++ b/content/enterprise_influxdb/v1.7/guides/migration.md @@ -42,7 +42,7 @@ InfluxDB 1.7.10 (both OSS and Enterprise) fixed an issue that prevented upgradin an InfluxDB OSS instance to InfluxDB Enterprise successfully. Upgrade to **InfluxDB 1.7.10** or later before proceeding. -- [Upgrade InfluxDB OSS](/influxdb/latest/administration/upgrading/) +- [Upgrade InfluxDB OSS](/{{< latest "influxdb" "v1" >}}/administration/upgrading/) - [Upgrade InfluxDB Enterprise](/enterprise_influxdb/v1.7/administration/upgrading/) ## Set up InfluxDB Enterprise meta nodes @@ -279,4 +279,4 @@ It may take a few minutes before the existing data is available. > **Note:** The number of data nodes in a cluster **must be** evenly divisible by the replication factor. For example, a replication factor of 2 works with 2, 4, 6, or 8 data nodes. A replication factor of 3 works with 3, 6, or 9 data nodes. 2. [Rebalance your cluster manually](/enterprise_influxdb/v1.7/guides/rebalance/) to meet the desired replication factor for existing shards. -3. If you were using [Chronograf](/chronograf/latest/), add your Enterprise instance as a new data source. +3. If you were using [Chronograf](/{{< latest "chronograf" >}}/), add your Enterprise instance as a new data source. diff --git a/content/enterprise_influxdb/v1.7/install-and-deploy/azure.md b/content/enterprise_influxdb/v1.7/install-and-deploy/azure.md index d69c88a01..ef4031073 100644 --- a/content/enterprise_influxdb/v1.7/install-and-deploy/azure.md +++ b/content/enterprise_influxdb/v1.7/install-and-deploy/azure.md @@ -54,7 +54,7 @@ To deploy InfluxDB Enterprise clusters on platforms other than Azure, see [Deplo Once the cluster is created, access the InfluxDB API at the IP address associated with the load balancer resource (`lb-influxdb`). If external access was configured during setup, the load balancer is publicly accessible. Otherwise, the load balancer is only accessible to the cluster's virtual network. -Use the load balancer IP address and the InfluxDB admin credentials entered during the cluster creation to interact with InfluxDB Enterprise via the [`influx` CLI](https://docs.influxdata.com/influxdb/v1.8/tools/shell/) or use the InfluxDB's [query](https://docs.influxdata.com/influxdb/v1.8/guides/query_data/) and [write](https://docs.influxdata.com/influxdb/v1.8/guides/write_data/) HTTP APIs. +Use the load balancer IP address and the InfluxDB admin credentials entered during the cluster creation to interact with InfluxDB Enterprise via the [`influx` CLI](/influxdb/v1.8/tools/shell/) or use the InfluxDB's [query](/influxdb/v1.8/guides/query_data/) and [write](/influxdb/v1.8/guides/write_data/) HTTP APIs. ## Access the cluster diff --git a/content/enterprise_influxdb/v1.7/install-and-deploy/google-cloud-platform.md b/content/enterprise_influxdb/v1.7/install-and-deploy/google-cloud-platform.md index 4dccdf512..513fa3cb8 100644 --- a/content/enterprise_influxdb/v1.7/install-and-deploy/google-cloud-platform.md +++ b/content/enterprise_influxdb/v1.7/install-and-deploy/google-cloud-platform.md @@ -18,7 +18,7 @@ Complete the following steps to deploy an InfluxDB Enterprise cluster on Google After deploying your cluster, see [Getting started with InfluxDB](/platform/introduction/getting-started) for an introduction to InfluxDB database and the InfluxData platform. ->**Note:** InfluxDB Enterprise on GCP is a self-managed product. For a fully managed InfluxDB experience, check out [InfluxDB Cloud 2.0](/https://v2.docs.influxdata.com/v2.0/cloud/get-started/). +>**Note:** InfluxDB Enterprise on GCP is a self-managed product. For a fully managed InfluxDB experience, check out [InfluxDB Cloud 2.0](//influxdb/v2.0/cloud/get-started/). ## Verify prerequisites diff --git a/content/enterprise_influxdb/v1.7/install-and-deploy/production_installation/chrono_install.md b/content/enterprise_influxdb/v1.7/install-and-deploy/production_installation/chrono_install.md index 191037e2d..e74965760 100644 --- a/content/enterprise_influxdb/v1.7/install-and-deploy/production_installation/chrono_install.md +++ b/content/enterprise_influxdb/v1.7/install-and-deploy/production_installation/chrono_install.md @@ -12,4 +12,4 @@ menu: Now that you've installed the meta nodes and data nodes, you are ready to install Chronograf to provide you with a user interface to access the InfluxDB Enterprise instance. -[Installation instruction for Chronograf](/chronograf/latest/introduction/installation/) +[Installation instruction for Chronograf](/{{< latest "chronograf" >}}/introduction/installation/) diff --git a/content/enterprise_influxdb/v1.7/install-and-deploy/production_installation/meta_node_installation.md b/content/enterprise_influxdb/v1.7/install-and-deploy/production_installation/meta_node_installation.md index b0d362baf..7413231e1 100644 --- a/content/enterprise_influxdb/v1.7/install-and-deploy/production_installation/meta_node_installation.md +++ b/content/enterprise_influxdb/v1.7/install-and-deploy/production_installation/meta_node_installation.md @@ -10,7 +10,7 @@ menu: --- InfluxDB Enterprise offers highly scalable clusters on your infrastructure -and a management UI ([via Chronograf](https://docs.influxdata.com/chronograf/latest) for working with clusters. +and a management UI ([via Chronograf](/{{< latest "chronograf" >}}) for working with clusters. The Production Installation process is designed for users looking to deploy InfluxDB Enterprise in a production environment. The following steps will get you up and running with the first essential component of diff --git a/content/enterprise_influxdb/v1.7/introduction/getting-started.md b/content/enterprise_influxdb/v1.7/introduction/getting-started.md index 966001239..1b1b6e7d8 100644 --- a/content/enterprise_influxdb/v1.7/introduction/getting-started.md +++ b/content/enterprise_influxdb/v1.7/introduction/getting-started.md @@ -10,9 +10,9 @@ menu: parent: Introduction --- -Now that you successfully [installed and set up](/enterprise_influxdb/v1.7/introduction/meta_node_installation/) InfluxDB Enterprise, use [Chronograf to setup your cluster as a data source.](/chronograf/latest/guides/monitor-an-influxenterprise-cluster/) +Now that you successfully [installed and set up](/enterprise_influxdb/v1.7/introduction/meta_node_installation/) InfluxDB Enterprise, use [Chronograf to setup your cluster as a data source.](/{{< latest "chronograf" >}}/guides/monitor-an-influxenterprise-cluster/) -More details on leveraging [Chronograf and getting started are available.](/chronograf/latest/introduction/getting-started/) +More details on leveraging [Chronograf and getting started are available.](/{{< latest "chronograf" >}}/introduction/getting-started/) ### Where to from here? diff --git a/content/enterprise_influxdb/v1.7/introduction/installation_requirements.md b/content/enterprise_influxdb/v1.7/introduction/installation_requirements.md index 32345ced7..dd85678b6 100644 --- a/content/enterprise_influxdb/v1.7/introduction/installation_requirements.md +++ b/content/enterprise_influxdb/v1.7/introduction/installation_requirements.md @@ -3,7 +3,7 @@ title: Installation requirements aliases: - /enterprise_influxdb/v1.7/introduction/meta_node_installation/ - /enterprise_influxdb/v1.7/introduction/data_node_installation/ - - /chronograf/latest/introduction/installation + - /{{< latest "chronograf" >}}/introduction/installation - /enterprise/v1.7/introduction/installation_guidelines/ menu: enterprise_influxdb_1_7: diff --git a/content/enterprise_influxdb/v1.8/about-the-project/release-notes-changelog.md b/content/enterprise_influxdb/v1.8/about-the-project/release-notes-changelog.md index 83bbc3df7..dd472fa1c 100644 --- a/content/enterprise_influxdb/v1.8/about-the-project/release-notes-changelog.md +++ b/content/enterprise_influxdb/v1.8/about-the-project/release-notes-changelog.md @@ -311,7 +311,7 @@ Please see the [InfluxDB OSS release notes](/influxdb/v1.7/about_the_project/rel ## v1.5.0 [2018-03-06] > ***Note:*** This release builds off of the 1.5 release of InfluxDB OSS. Please see the [InfluxDB OSS release -> notes](https://docs.influxdata.com/influxdb/v1.5/about_the_project/releasenotes-changelog/) for more information about the InfluxDB OSS release. +> notes](/influxdb/v1.5/about_the_project/releasenotes-changelog/) for more information about the InfluxDB OSS release. For highlights of the InfluxDB 1.5 release, see [What's new in InfluxDB 1.5](/influxdb/v1.5/about_the_project/whats_new/). @@ -430,7 +430,7 @@ Please see the OSS [release notes](/influxdb/v1.3/about_the_project/releasenotes ## v1.3.4 [2017-08-23] -This release builds off of the 1.3.4 release of OSS InfluxDB. Please see the [OSS release notes](https://docs.influxdata.com/influxdb/v1.3/about_the_project/releasenotes-changelog/) for more information about the OSS releases. +This release builds off of the 1.3.4 release of OSS InfluxDB. Please see the [OSS release notes](/influxdb/v1.3/about_the_project/releasenotes-changelog/) for more information about the OSS releases. ### Bugfixes @@ -438,7 +438,7 @@ This release builds off of the 1.3.4 release of OSS InfluxDB. Please see the [OS ## v1.3.3 [2017-08-10] -This release builds off of the 1.3.3 release of OSS InfluxDB. Please see the [OSS release notes](https://docs.influxdata.com/influxdb/v1.3/about_the_project/releasenotes-changelog/) for more information about the OSS releases. +This release builds off of the 1.3.3 release of OSS InfluxDB. Please see the [OSS release notes](/influxdb/v1.3/about_the_project/releasenotes-changelog/) for more information about the OSS releases. ### Bugfixes @@ -803,4 +803,4 @@ Backup and restore has been updated to fix issues and refine existing capabiliti The Enterprise Web Console has officially been deprecated and will be eliminated entirely by the end of 2017. No additional features will be added and no additional bug fix releases are planned. -For browser-based access to InfluxDB Enterprise, [Chronograf](/chronograf/latest/introduction) is now the recommended tool to use. +For browser-based access to InfluxDB Enterprise, [Chronograf](/{{< latest "chronograf" >}}/introduction) is now the recommended tool to use. diff --git a/content/enterprise_influxdb/v1.8/administration/backup-and-restore.md b/content/enterprise_influxdb/v1.8/administration/backup-and-restore.md index ec29a0053..662575a2a 100644 --- a/content/enterprise_influxdb/v1.8/administration/backup-and-restore.md +++ b/content/enterprise_influxdb/v1.8/administration/backup-and-restore.md @@ -26,7 +26,7 @@ Depending on the volume of data to be protected and your application requirement - [Backup and restore utilities](#backup-and-restore-utilities) — For most applications - [Exporting and importing data](#exporting-and-importing-data) — For large datasets -> **Note:** Use the [`backup` and `restore` utilities (InfluxDB OSS 1.5 and later)](/influxdb/latest/administration/backup_and_restore/) to: +> **Note:** Use the [`backup` and `restore` utilities (InfluxDB OSS 1.5 and later)](/{{< latest "influxdb" "v1" >}}/administration/backup_and_restore/) to: > > - Restore InfluxDB Enterprise backup files to InfluxDB OSS instances. > - Back up InfluxDB OSS data that can be restored in InfluxDB Enterprise clusters. @@ -429,13 +429,13 @@ As an alternative to the standard backup and restore utilities, use the InfluxDB ### Exporting data -Use the [`influx_inspect export` command](/influxdb/latest/tools/influx_inspect#export) to export data in line protocol format from your InfluxDB Enterprise cluster. Options include: +Use the [`influx_inspect export` command](/{{< latest "influxdb" "v1" >}}/tools/influx_inspect#export) to export data in line protocol format from your InfluxDB Enterprise cluster. Options include: - Exporting all, or specific, databases - Filtering with starting and ending timestamps - Using gzip compression for smaller files and faster exports -For details on optional settings and usage, see [`influx_inspect export` command](/influxdb/latest/tools/influx_inspect#export). +For details on optional settings and usage, see [`influx_inspect export` command](/{{< latest "influxdb" "v1" >}}/tools/influx_inspect#export). In the following example, the database is exported filtered to include only one day and compressed for optimal speed and file size. @@ -445,7 +445,7 @@ influx_inspect export -database myDB -compress -start 2019-05-19T00:00:00.000Z - ### Importing data -After exporting the data in line protocol format, you can import the data using the [`influx -import` CLI command](https://docs.influxdata.com/influxdb/latest/tools/shell/#import). +After exporting the data in line protocol format, you can import the data using the [`influx -import` CLI command](/{{< latest "influxdb" "v1" >}}/tools/shell/#import). In the following example, the compressed data file is imported into the specified database. @@ -453,7 +453,7 @@ In the following example, the compressed data file is imported into the specifie influx -import -database myDB -compress ``` -For details on using the `influx -import` command, see [Import data from a file with -import](https://docs.influxdata.com/influxdb/latest/tools/shell/#import-data-from-a-file-with-import). +For details on using the `influx -import` command, see [Import data from a file with -import](/{{< latest "influxdb" "v1" >}}/tools/shell/#import-data-from-a-file-with-import). ### Example diff --git a/content/enterprise_influxdb/v1.8/administration/upgrading.md b/content/enterprise_influxdb/v1.8/administration/upgrading.md index 98c1f37e6..6be5a99f3 100644 --- a/content/enterprise_influxdb/v1.8/administration/upgrading.md +++ b/content/enterprise_influxdb/v1.8/administration/upgrading.md @@ -165,7 +165,7 @@ sudo yum localinstall influxdb-data-1.8.0_c1.8.0.x86_64.rpm Migrate any custom settings from your previous data node configuration file. -- To enable HTTPS, see [Enable HTTPS within the configuration file for each Data Node](https://docs.influxdata.com/enterprise_influxdb/v1.8/guides/https_setup/#step-4-enable-https-within-the-configuration-file-for-each-data-node). +- To enable HTTPS, see [Enable HTTPS within the configuration file for each Data Node](/enterprise_influxdb/v1.8/guides/https_setup/#step-4-enable-https-within-the-configuration-file-for-each-data-node). - To enable TSI, open `/etc/influxdb/influxdb.conf`, and then adjust and save the settings shown in the following table. diff --git a/content/enterprise_influxdb/v1.8/concepts/clustering.md b/content/enterprise_influxdb/v1.8/concepts/clustering.md index 1bb1caeb0..b023fc211 100644 --- a/content/enterprise_influxdb/v1.8/concepts/clustering.md +++ b/content/enterprise_influxdb/v1.8/concepts/clustering.md @@ -91,7 +91,7 @@ Data nodes hold the actual time series data. The minimum number of data nodes to ## Chronograf -[Chronograf](/chronograf/latest/introduction/getting-started/) is the user interface component of InfluxData’s TICK stack. +[Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/) is the user interface component of InfluxData’s TICK stack. It makes owning the monitoring and alerting for your infrastructure easy to setup and maintain. It talks directly to the data and meta nodes over their HTTP protocols, which are bound by default to ports `8086` for data nodes and port `8091` for meta nodes. diff --git a/content/enterprise_influxdb/v1.8/concepts/glossary.md b/content/enterprise_influxdb/v1.8/concepts/glossary.md index 4e15ab21d..c5f9a1741 100644 --- a/content/enterprise_influxdb/v1.8/concepts/glossary.md +++ b/content/enterprise_influxdb/v1.8/concepts/glossary.md @@ -72,6 +72,6 @@ query capacity within the cluster. Legacy user interface for the InfluxDB Enterprise. -This has been deprecated and the suggestion is to use [Chronograf](/chronograf/latest/introduction/). +This has been deprecated and the suggestion is to use [Chronograf](/{{< latest "chronograf" >}}/introduction/). -If you are transitioning from the Enterprise Web Console to Chronograf and helpful [transition guide](/chronograf/latest/guides/transition-web-admin-interface/) is available. +If you are transitioning from the Enterprise Web Console to Chronograf and helpful [transition guide](/{{< latest "chronograf" >}}/guides/transition-web-admin-interface/) is available. diff --git a/content/enterprise_influxdb/v1.8/features/clustering-features.md b/content/enterprise_influxdb/v1.8/features/clustering-features.md index 4fcc484d6..789f4d115 100644 --- a/content/enterprise_influxdb/v1.8/features/clustering-features.md +++ b/content/enterprise_influxdb/v1.8/features/clustering-features.md @@ -70,7 +70,7 @@ you should set the lease-duration to a value greater than the aggregate executio Based on the current way in which CQs are configured to execute, the way to address parallelism is by using Kapacitor for the more complex CQs that you are attempting to run. -[See Kapacitor as a continuous query engine](/kapacitor/latest/guides/continuous_queries/). +[See Kapacitor as a continuous query engine](/{{< latest "kapacitor" >}}/guides/continuous_queries/). However, you can keep the more simplistic and highly performant CQs within the database – but ensure that the lease duration is greater than their aggregate execution time to ensure that “extra” load is not being unnecessarily introduced on your cluster. diff --git a/content/enterprise_influxdb/v1.8/guides/fine-grained-authorization.md b/content/enterprise_influxdb/v1.8/guides/fine-grained-authorization.md index 97805c623..43769366b 100644 --- a/content/enterprise_influxdb/v1.8/guides/fine-grained-authorization.md +++ b/content/enterprise_influxdb/v1.8/guides/fine-grained-authorization.md @@ -160,7 +160,7 @@ curl -s -L -XPOST "http://localhost:8091/role" \ ### Remove role permissions To remove permissions from a role, use the InfluxDB Meta API `/role` endpoint with the `action` field set to `remove-permissions`. -Specify the [permissions](https://docs.influxdata.com/chronograf/latest/administration/managing-influxdb-users/#permissions) to remove from each database. +Specify the [permissions](/{{< latest "chronograf" >}}/administration/managing-influxdb-users/#permissions) to remove from each database. The following example removes read and write permissions from `db1` for the `east` role. @@ -584,7 +584,7 @@ curl -s -L -XPOST "http://localhost:8091/influxdb/v2/acl/grants" \ }' ``` -Grants for specific series also apply to [meta queries](https://docs.influxdata.com/influxdb/v1.8/query_language/schema_exploration). +Grants for specific series also apply to [meta queries](/influxdb/v1.8/query_language/schema_exploration). Results from meta queries are restricted based on series-level permissions. For example, `SHOW TAG VALUES` only returns tag values that the user is authorized to see. diff --git a/content/enterprise_influxdb/v1.8/guides/https_setup.md b/content/enterprise_influxdb/v1.8/guides/https_setup.md index 37967293b..a3fb70c5b 100644 --- a/content/enterprise_influxdb/v1.8/guides/https_setup.md +++ b/content/enterprise_influxdb/v1.8/guides/https_setup.md @@ -245,7 +245,7 @@ With a self-signed certificate, you must also use the `-k` option to skip certif ## Connect Telegraf to a secured InfluxDB Enterprise instance -Connecting [Telegraf](/telegraf/latest/) +Connecting [Telegraf](/{{< latest "telegraf" >}}/) to an HTTPS-enabled InfluxDB Enterprise instance requires some additional steps. In Telegraf's configuration file (`/etc/telegraf/telegraf.conf`), under the OUTPUT PLUGINS section, diff --git a/content/enterprise_influxdb/v1.8/guides/migration.md b/content/enterprise_influxdb/v1.8/guides/migration.md index 6c49a2caa..317d3a254 100644 --- a/content/enterprise_influxdb/v1.8/guides/migration.md +++ b/content/enterprise_influxdb/v1.8/guides/migration.md @@ -40,7 +40,7 @@ Complete the following tasks: ## Upgrade InfluxDB to the latest version Upgrade InfluxDB to the latest stable version before proceeding. -- [Upgrade InfluxDB OSS](/influxdb/latest/administration/upgrading/) +- [Upgrade InfluxDB OSS](/{{< latest "influxdb" "v1" >}}/administration/upgrading/) - [Upgrade InfluxDB Enterprise](/enterprise_influxdb/v1.8/administration/upgrading/) ## Set up InfluxDB Enterprise meta nodes @@ -276,4 +276,4 @@ It may take a few minutes before the existing data is available. on all existing retention polices to the number of data nodes in your cluster. 2. [Rebalance your cluster manually](/enterprise_influxdb/v1.8/guides/rebalance/) to meet the desired replication factor for existing shards. -3. If you were using [Chronograf](/chronograf/latest/), add your Enterprise instance as a new data source. +3. If you were using [Chronograf](/{{< latest "chronograf" >}}/), add your Enterprise instance as a new data source. diff --git a/content/enterprise_influxdb/v1.8/install-and-deploy/deploying/azure.md b/content/enterprise_influxdb/v1.8/install-and-deploy/deploying/azure.md index 952de36d6..7b8ad38f0 100644 --- a/content/enterprise_influxdb/v1.8/install-and-deploy/deploying/azure.md +++ b/content/enterprise_influxdb/v1.8/install-and-deploy/deploying/azure.md @@ -55,7 +55,7 @@ To deploy InfluxDB Enterprise clusters on platforms other than Azure, see [Deplo Once the cluster is created, access the InfluxDB API at the IP address associated with the load balancer resource (`lb-influxdb`). If external access was configured during setup, the load balancer is publicly accessible. Otherwise, the load balancer is only accessible to the cluster's virtual network. -Use the load balancer IP address and the InfluxDB admin credentials entered during the cluster creation to interact with InfluxDB Enterprise via the [`influx` CLI](https://docs.influxdata.com/influxdb/v1.8/tools/shell/) or use the InfluxDB's [query](https://docs.influxdata.com/influxdb/v1.8/guides/query_data/) and [write](https://docs.influxdata.com/influxdb/v1.8/guides/write_data/) HTTP APIs. +Use the load balancer IP address and the InfluxDB admin credentials entered during the cluster creation to interact with InfluxDB Enterprise via the [`influx` CLI](/influxdb/v1.8/tools/shell/) or use the InfluxDB's [query](/influxdb/v1.8/guides/query_data/) and [write](/influxdb/v1.8/guides/write_data/) HTTP APIs. ## Access the cluster diff --git a/content/enterprise_influxdb/v1.8/install-and-deploy/deploying/google-cloud-platform.md b/content/enterprise_influxdb/v1.8/install-and-deploy/deploying/google-cloud-platform.md index 426d0256f..ab787d4a9 100644 --- a/content/enterprise_influxdb/v1.8/install-and-deploy/deploying/google-cloud-platform.md +++ b/content/enterprise_influxdb/v1.8/install-and-deploy/deploying/google-cloud-platform.md @@ -19,7 +19,7 @@ Complete the following steps to deploy an InfluxDB Enterprise cluster on Google After deploying your cluster, see [Getting started with InfluxDB](/platform/introduction/getting-started) for an introduction to InfluxDB database and the InfluxData platform. ->**Note:** InfluxDB Enterprise on GCP is a self-managed product. For a fully managed InfluxDB experience, check out [InfluxDB Cloud 2.0](/https://v2.docs.influxdata.com/v2.0/cloud/get-started/). +>**Note:** InfluxDB Enterprise on GCP is a self-managed product. For a fully managed InfluxDB experience, check out [InfluxDB Cloud 2.0](//influxdb/v2.0/cloud/get-started/). ## Verify prerequisites diff --git a/content/enterprise_influxdb/v1.8/install-and-deploy/production_installation/chrono_install.md b/content/enterprise_influxdb/v1.8/install-and-deploy/production_installation/chrono_install.md index eb699e764..e068b36e6 100644 --- a/content/enterprise_influxdb/v1.8/install-and-deploy/production_installation/chrono_install.md +++ b/content/enterprise_influxdb/v1.8/install-and-deploy/production_installation/chrono_install.md @@ -13,4 +13,4 @@ menu: Now that you've installed the meta nodes and data nodes, you are ready to install Chronograf to provide you with a user interface to access the InfluxDB Enterprise instance. -[Installation instruction for Chronograf](/chronograf/latest/introduction/installation/) +[Installation instruction for Chronograf](/{{< latest "chronograf" >}}/introduction/installation/) diff --git a/content/enterprise_influxdb/v1.8/install-and-deploy/production_installation/meta_node_installation.md b/content/enterprise_influxdb/v1.8/install-and-deploy/production_installation/meta_node_installation.md index c563fc2ce..7e6baa401 100644 --- a/content/enterprise_influxdb/v1.8/install-and-deploy/production_installation/meta_node_installation.md +++ b/content/enterprise_influxdb/v1.8/install-and-deploy/production_installation/meta_node_installation.md @@ -10,7 +10,7 @@ menu: --- InfluxDB Enterprise offers highly scalable clusters on your infrastructure -and a management UI ([via Chronograf](https://docs.influxdata.com/chronograf/latest) for working with clusters. +and a management UI ([via Chronograf](/{{< latest "chronograf" >}}) for working with clusters. The Production Installation process is designed for users looking to deploy InfluxDB Enterprise in a production environment. The following steps will get you up and running with the first essential component of diff --git a/content/enterprise_influxdb/v1.8/introduction/getting-started.md b/content/enterprise_influxdb/v1.8/introduction/getting-started.md index c007a20ef..c16070e92 100644 --- a/content/enterprise_influxdb/v1.8/introduction/getting-started.md +++ b/content/enterprise_influxdb/v1.8/introduction/getting-started.md @@ -11,9 +11,9 @@ menu: parent: Introduction --- -Now that you successfully [installed and set up](/enterprise_influxdb/v1.8/introduction/meta_node_installation/) InfluxDB Enterprise, use [Chronograf to setup your cluster as a data source.](/chronograf/latest/guides/monitor-an-influxenterprise-cluster/) +Now that you successfully [installed and set up](/enterprise_influxdb/v1.8/introduction/meta_node_installation/) InfluxDB Enterprise, use [Chronograf to setup your cluster as a data source.](/{{< latest "chronograf" >}}/guides/monitor-an-influxenterprise-cluster/) -More details on leveraging [Chronograf and getting started are available.](/chronograf/latest/introduction/getting-started/) +More details on leveraging [Chronograf and getting started are available.](/{{< latest "chronograf" >}}/introduction/getting-started/) ### Where to from here? diff --git a/content/enterprise_influxdb/v1.8/introduction/installation_requirements.md b/content/enterprise_influxdb/v1.8/introduction/installation_requirements.md index b7b7f2607..b7a0c644f 100644 --- a/content/enterprise_influxdb/v1.8/introduction/installation_requirements.md +++ b/content/enterprise_influxdb/v1.8/introduction/installation_requirements.md @@ -4,7 +4,7 @@ description: Requirements for installing and deploying InfluxDB Enterprise. aliases: - /enterprise_influxdb/v1.8/introduction/meta_node_installation/ - /enterprise_influxdb/v1.8/introduction/data_node_installation/ - - /chronograf/latest/introduction/installation + - /{{< latest "chronograf" >}}/introduction/installation - /enterprise/v1.8/introduction/installation_guidelines/ menu: enterprise_influxdb_1_8: diff --git a/content/influxdb/v1.3/_index.md b/content/influxdb/v1.3/_index.md index 920aa4fb0..4018b1ba2 100644 --- a/content/influxdb/v1.3/_index.md +++ b/content/influxdb/v1.3/_index.md @@ -29,4 +29,4 @@ It compiles into a single binary with no external dependencies. * Built in web admin interface. However, the open source edition of InfluxDB runs on a single node. If your requirements dictate a high-availability setup -to eliminate a single point of failure, you should explore [InfluxDB Enterprise Edition](https://docs.influxdata.com/influxdb/v1.3/high_availability/). +to eliminate a single point of failure, you should explore [InfluxDB Enterprise Edition](/influxdb/v1.3/high_availability/). diff --git a/content/influxdb/v1.3/about_the_project/releasenotes-changelog.md b/content/influxdb/v1.3/about_the_project/releasenotes-changelog.md index 8a599cc28..01c0807a3 100644 --- a/content/influxdb/v1.3/about_the_project/releasenotes-changelog.md +++ b/content/influxdb/v1.3/about_the_project/releasenotes-changelog.md @@ -123,7 +123,7 @@ Minor bug fixes were identified via Community and InfluxCloud. Version 1.3.0 marks the first official release of InfluxDB's new time series index (TSI) engine. The TSI engine is a significant technical advancement in InfluxDB. -It offers a solution to the [time-structured merge tree](https://docs.influxdata.com/influxdb/v1.2/concepts/storage_engine/) engine's [high series cardinality issue](/influxdb/v1.3/troubleshooting/frequently-asked-questions/#why-does-series-cardinality-matter). +It offers a solution to the [time-structured merge tree](/influxdb/v1.2/concepts/storage_engine/) engine's [high series cardinality issue](/influxdb/v1.3/troubleshooting/frequently-asked-questions/#why-does-series-cardinality-matter). With TSI, the number of series should be unbounded by the memory on the server hardware and the number of existing series will have a negligible impact on database startup time. See Paul Dix's blogpost [Path to 1 Billion Time Series: InfluxDB High Cardinality Indexing Ready for Testing](https://www.influxdata.com/path-1-billion-time-series-influxdb-high-cardinality-indexing-ready-testing/) for additional information. diff --git a/content/influxdb/v1.3/administration/differences.md b/content/influxdb/v1.3/administration/differences.md index 9ca17cd7c..8e047a429 100644 --- a/content/influxdb/v1.3/administration/differences.md +++ b/content/influxdb/v1.3/administration/differences.md @@ -30,7 +30,7 @@ see [InfluxDB's Changelog](/influxdb/v1.3/about_the_project/releasenotes-changel Version 1.3.0 marked the first official release of InfluxDB's new time series index (TSI) engine. The TSI engine is a significant technical advancement in InfluxDB. -It offers a solution to the [time-structured merge tree](https://docs.influxdata.com/influxdb/v1.3/concepts/storage_engine/) engine's [high series cardinality issue](https://docs.influxdata.com/influxdb/v1.3/troubleshooting/frequently-asked-questions/#why-does-series-cardinality-matter). +It offers a solution to the [time-structured merge tree](/influxdb/v1.3/concepts/storage_engine/) engine's [high series cardinality issue](/influxdb/v1.3/troubleshooting/frequently-asked-questions/#why-does-series-cardinality-matter). With TSI, the number of series should be unbounded by the memory on the server hardware and the number of existing series will have a negligible impact on database startup time. See Paul Dix's blogpost [Path to 1 Billion Time Series: InfluxDB High Cardinality Indexing Ready for Testing](https://www.influxdata.com/path-1-billion-time-series-influxdb-high-cardinality-indexing-ready-testing/) for additional information. diff --git a/content/influxdb/v1.3/concepts/glossary.md b/content/influxdb/v1.3/concepts/glossary.md index c849ab977..1ef92d640 100644 --- a/content/influxdb/v1.3/concepts/glossary.md +++ b/content/influxdb/v1.3/concepts/glossary.md @@ -253,7 +253,7 @@ The interval spanned by each shard group is the shard duration. Related entries: [database](/influxdb/v1.3/concepts/glossary/#database), [retention policy](/influxdb/v1.3/concepts/glossary/#retention-policy-rp), [series](/influxdb/v1.3/concepts/glossary/#series), [shard](/influxdb/v1.3/concepts/glossary/#shard), [shard duration](/influxdb/v1.3/concepts/glossary/#shard-duration) ## subscription -Subscriptions allow [Kapacitor](/kapacitor/latest/) to receive data from InfluxDB in a push model rather than the pull model based on querying data. +Subscriptions allow [Kapacitor](/{{< latest "kapacitor" >}}/) to receive data from InfluxDB in a push model rather than the pull model based on querying data. When Kapacitor is configured to work with InfluxDB, the subscription will automatically push every write for the subscribed database from InfluxDB to Kapacitor. Subscriptions can use TCP or UDP for transmitting the writes. @@ -302,7 +302,7 @@ See [InfluxQL Functions](/influxdb/v1.3/query_language/functions/#transformation Related entries: [aggregation](/influxdb/v1.3/concepts/glossary/#aggregation), [function](/influxdb/v1.3/concepts/glossary/#function), [selector](/influxdb/v1.3/concepts/glossary/#selector) ## tsm (Time Structured Merge tree) -The purpose-built data storage format for InfluxDB. TSM allows for greater compaction and higher write and read throughput than existing B+ or LSM tree implementations. See [Storage Engine](http://docs.influxdata.com/influxdb/v1.3/concepts/storage_engine/) for more. +The purpose-built data storage format for InfluxDB. TSM allows for greater compaction and higher write and read throughput than existing B+ or LSM tree implementations. See [Storage Engine](/influxdb/v1.3/concepts/storage_engine/) for more. ## user There are two kinds of users in InfluxDB: diff --git a/content/influxdb/v1.3/high_availability/clusters.md b/content/influxdb/v1.3/high_availability/clusters.md index df529338c..f7fa6bb71 100644 --- a/content/influxdb/v1.3/high_availability/clusters.md +++ b/content/influxdb/v1.3/high_availability/clusters.md @@ -14,4 +14,4 @@ menu: InfluxDB OSS does not support clustering. For high availability or horizontal scaling of InfluxDB, consider the InfluxData commercial clustered offering, -[InfluxDB Enterprise](/enterprise_influxdb/latest/). +[InfluxDB Enterprise](/{{< latest "enterprise_influxdb" >}}/). diff --git a/content/influxdb/v1.3/query_language/data_download.md b/content/influxdb/v1.3/query_language/data_download.md index cd9526509..c8d0b9314 100644 --- a/content/influxdb/v1.3/query_language/data_download.md +++ b/content/influxdb/v1.3/query_language/data_download.md @@ -32,7 +32,7 @@ InfluxDB shell 1.3.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/latest/tools/shell/#influx-arguments) specifies the format/precision of any returned timestamps. +* The [`-precision` argument](/{{< latest "influxdb" "v1" >}}/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.3/query_language/spec.md b/content/influxdb/v1.3/query_language/spec.md index 8a2ac5c51..1ddb9ddc3 100644 --- a/content/influxdb/v1.3/query_language/spec.md +++ b/content/influxdb/v1.3/query_language/spec.md @@ -409,7 +409,7 @@ CREATE RETENTION POLICY "10m.events" ON "somedb" DURATION 60m REPLICATION 2 SHAR ### CREATE SUBSCRIPTION -Subscriptions tell InfluxDB to send all the data it receives to [Kapacitor](https://docs.influxdata.com/kapacitor/v1.3/introduction/). +Subscriptions tell InfluxDB to send all the data it receives to [Kapacitor](/kapacitor/v1.3/introduction/). ``` create_subscription_stmt = "CREATE SUBSCRIPTION" subscription_name "ON" db_name "." retention_policy "DESTINATIONS" ("ANY"|"ALL") host { "," host} . diff --git a/content/influxdb/v1.4/_index.md b/content/influxdb/v1.4/_index.md index 4f42add9c..882df00f4 100644 --- a/content/influxdb/v1.4/_index.md +++ b/content/influxdb/v1.4/_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. However, InfluxDB OSS runs on a single node. If you require a high-availability clustering -to eliminate a single point of failure, consider the [InfluxDB Enterprise Edition](https://docs.influxdata.com/influxdb/v1.4/high_availability/). +to eliminate a single point of failure, consider the [InfluxDB Enterprise Edition](/influxdb/v1.4/high_availability/). diff --git a/content/influxdb/v1.4/about_the_project/releasenotes-changelog.md b/content/influxdb/v1.4/about_the_project/releasenotes-changelog.md index 92d3d44bc..47bdcea77 100644 --- a/content/influxdb/v1.4/about_the_project/releasenotes-changelog.md +++ b/content/influxdb/v1.4/about_the_project/releasenotes-changelog.md @@ -273,7 +273,7 @@ Minor bug fixes were identified via Community and InfluxCloud. Version 1.3.0 marks the first official release of InfluxDB's new time series index (TSI) engine. The TSI engine is a significant technical advancement in InfluxDB. -It offers a solution to the [time-structured merge tree](https://docs.influxdata.com/influxdb/v1.2/concepts/storage_engine/) engine's [high series cardinality issue](/influxdb/v1.3/troubleshooting/frequently-asked-questions/#why-does-series-cardinality-matter). +It offers a solution to the [time-structured merge tree](/influxdb/v1.2/concepts/storage_engine/) engine's [high series cardinality issue](/influxdb/v1.3/troubleshooting/frequently-asked-questions/#why-does-series-cardinality-matter). With TSI, the number of series should be unbounded by the memory on the server hardware and the number of existing series will have a negligible impact on database startup time. See Paul Dix's blogpost [Path to 1 Billion Time Series: InfluxDB High Cardinality Indexing Ready for Testing](https://www.influxdata.com/path-1-billion-time-series-influxdb-high-cardinality-indexing-ready-testing/) for additional information. diff --git a/content/influxdb/v1.4/administration/https_setup.md b/content/influxdb/v1.4/administration/https_setup.md index 1f0201683..99bbee7de 100644 --- a/content/influxdb/v1.4/administration/https_setup.md +++ b/content/influxdb/v1.4/administration/https_setup.md @@ -187,7 +187,7 @@ That's it! You've successfully set up HTTPS with InfluxDB. ## Connecting Telegraf to a secured InfluxDB instance > -Connecting [Telegraf](/telegraf/latest/) to an InfluxDB instance that's using +Connecting [Telegraf](/{{< latest "telegraf" >}}/) to an InfluxDB instance that's using HTTPS requires some additional steps. > In Telegraf's configuration file (`/etc/telegraf/telegraf.conf`), edit the `urls` diff --git a/content/influxdb/v1.4/concepts/glossary.md b/content/influxdb/v1.4/concepts/glossary.md index e3fc54d18..19427e7f8 100644 --- a/content/influxdb/v1.4/concepts/glossary.md +++ b/content/influxdb/v1.4/concepts/glossary.md @@ -253,7 +253,7 @@ The interval spanned by each shard group is the shard duration. Related entries: [database](/influxdb/v1.4/concepts/glossary/#database), [retention policy](/influxdb/v1.4/concepts/glossary/#retention-policy-rp), [series](/influxdb/v1.4/concepts/glossary/#series), [shard](/influxdb/v1.4/concepts/glossary/#shard), [shard duration](/influxdb/v1.4/concepts/glossary/#shard-duration) ## subscription -Subscriptions allow [Kapacitor](/kapacitor/latest/) to receive data from InfluxDB in a push model rather than the pull model based on querying data. +Subscriptions allow [Kapacitor](/{{< latest "kapacitor" >}}/) to receive data from InfluxDB in a push model rather than the pull model based on querying data. When Kapacitor is configured to work with InfluxDB, the subscription will automatically push every write for the subscribed database from InfluxDB to Kapacitor. Subscriptions can use TCP or UDP for transmitting the writes. @@ -302,7 +302,7 @@ See [InfluxQL Functions](/influxdb/v1.4/query_language/functions/#transformation Related entries: [aggregation](/influxdb/v1.4/concepts/glossary/#aggregation), [function](/influxdb/v1.4/concepts/glossary/#function), [selector](/influxdb/v1.4/concepts/glossary/#selector) ## tsm (Time Structured Merge tree) -The purpose-built data storage format for InfluxDB. TSM allows for greater compaction and higher write and read throughput than existing B+ or LSM tree implementations. See [Storage Engine](http://docs.influxdata.com/influxdb/v1.4/concepts/storage_engine/) for more. +The purpose-built data storage format for InfluxDB. TSM allows for greater compaction and higher write and read throughput than existing B+ or LSM tree implementations. See [Storage Engine](/influxdb/v1.4/concepts/storage_engine/) for more. ## user There are two kinds of users in InfluxDB: diff --git a/content/influxdb/v1.4/high_availability/clusters.md b/content/influxdb/v1.4/high_availability/clusters.md index 5126a754f..d06fee2e3 100644 --- a/content/influxdb/v1.4/high_availability/clusters.md +++ b/content/influxdb/v1.4/high_availability/clusters.md @@ -14,4 +14,4 @@ menu: InfluxDB OSS does not support clustering. For high availability or horizontal scaling of InfluxDB, please consider the commercial clustered offering, -[InfluxDB Enterprise](/enterprise_influxdb/latest/). +[InfluxDB Enterprise](/{{< latest "enterprise_influxdb" >}}/). diff --git a/content/influxdb/v1.4/query_language/authentication_and_authorization.md b/content/influxdb/v1.4/query_language/authentication_and_authorization.md index 098f64ef3..b890cdbef 100644 --- a/content/influxdb/v1.4/query_language/authentication_and_authorization.md +++ b/content/influxdb/v1.4/query_language/authentication_and_authorization.md @@ -152,7 +152,7 @@ password: > ## Authenticate Telegraf requests to InfluxDB > -Authenticating [Telegraf](/telegraf/latest/) requests to an InfluxDB instance with +Authenticating [Telegraf](/{{< latest "telegraf" >}}/) requests to an InfluxDB instance with authentication enabled requires some additional steps. In Telegraf's configuration file (`/etc/telegraf/telegraf.conf`), uncomment and edit the `username` and `password` settings: diff --git a/content/influxdb/v1.4/query_language/continuous_queries.md b/content/influxdb/v1.4/query_language/continuous_queries.md index a8119e35a..f1e5dca64 100644 --- a/content/influxdb/v1.4/query_language/continuous_queries.md +++ b/content/influxdb/v1.4/query_language/continuous_queries.md @@ -949,6 +949,6 @@ precision data. Kapacitor, InfluxData's data processing engine, can do the same work as InfluxDB's CQs. Check out the -[Kapacitor documentation](/kapacitor/latest/examples/continuous_queries/) for when +[Kapacitor documentation](/{{< latest "kapacitor" >}}/examples/continuous_queries/) for when to use Kapacitor instead of InfluxDB and how to perform the same CQ functionality with a TICKscript. diff --git a/content/influxdb/v1.4/query_language/data_download.md b/content/influxdb/v1.4/query_language/data_download.md index 869e79603..9bec2ad3c 100644 --- a/content/influxdb/v1.4/query_language/data_download.md +++ b/content/influxdb/v1.4/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/latest/tools/shell/#influx-arguments) specifies the format/precision of any returned timestamps. +* The [`-precision` argument](/{{< latest "influxdb" "v1" >}}/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.4/query_language/spec.md b/content/influxdb/v1.4/query_language/spec.md index f06d772ca..7dc7d7da8 100644 --- a/content/influxdb/v1.4/query_language/spec.md +++ b/content/influxdb/v1.4/query_language/spec.md @@ -419,7 +419,7 @@ CREATE RETENTION POLICY "10m.events" ON "somedb" DURATION 60m REPLICATION 2 SHAR ### CREATE SUBSCRIPTION -Subscriptions tell InfluxDB to send all the data it receives to [Kapacitor](https://docs.influxdata.com/kapacitor/v1.4/introduction/). +Subscriptions tell InfluxDB to send all the data it receives to [Kapacitor](/kapacitor/v1.4/introduction/). ``` create_subscription_stmt = "CREATE SUBSCRIPTION" subscription_name "ON" db_name "." retention_policy "DESTINATIONS" ("ANY"|"ALL") host { "," host} . diff --git a/content/influxdb/v1.4/tools/api.md b/content/influxdb/v1.4/tools/api.md index c1a93d3ee..a507d7084 100644 --- a/content/influxdb/v1.4/tools/api.md +++ b/content/influxdb/v1.4/tools/api.md @@ -497,7 +497,7 @@ POST http://localhost:8086/write | Query String Parameter | Optional/Required | Description | | :--------------------- | :---------------- | :---------- | -| consistency=[any,one,quorum,all] | Optional, available with [InfluxEnterprise clusters](/enterprise/v1.3/) only. | Sets the write consistency for the point. InfluxDB assumes that the write consistency is `one` if you do not specify `consistency`. See the [InfluxEnterprise documentation](https://docs.influxdata.com/enterprise_influxdb/v1.3/concepts/clustering#write-consistency) for detailed descriptions of each consistency option. | +| consistency=[any,one,quorum,all] | Optional, available with [InfluxEnterprise clusters](/enterprise/v1.3/) only. | Sets the write consistency for the point. InfluxDB assumes that the write consistency is `one` if you do not specify `consistency`. See the [InfluxEnterprise documentation](/enterprise_influxdb/v1.3/concepts/clustering#write-consistency) for detailed descriptions of each consistency option. | | db=\ | Required | Sets the target [database](/influxdb/v1.4/concepts/glossary/#database) for the write. | | p=\ | Optional if you haven't [enabled authentication](/influxdb/v1.4/query_language/authentication_and_authorization/#set-up-authentication). Required if you've enabled authentication.* | Sets the password for authentication if you've enabled authentication. Use with the query string parameter `u`. | | precision=[ns,u,ms,s,m,h] | Optional | Sets the precision for the supplied Unix time values. InfluxDB assumes that timestamps are in nanoseconds if you do not specify `precision`.** | diff --git a/content/influxdb/v1.4/troubleshooting/frequently-asked-questions.md b/content/influxdb/v1.4/troubleshooting/frequently-asked-questions.md index c52510d70..405e0c036 100644 --- a/content/influxdb/v1.4/troubleshooting/frequently-asked-questions.md +++ b/content/influxdb/v1.4/troubleshooting/frequently-asked-questions.md @@ -251,7 +251,7 @@ Note that you will need to fully qualify the measurement to query data in the no ``` ## How do I cancel a long-running query? -You can cancel a long-running interactive query from the CLI using `Ctrl+C`. To stop other long-running query that you see when using the [`SHOW QUERIES`](https://docs.influxdata.com/influxdb/v1.3/query_language/spec/#show-queries) command, +You can cancel a long-running interactive query from the CLI using `Ctrl+C`. To stop other long-running query that you see when using the [`SHOW QUERIES`](/influxdb/v1.3/query_language/spec/#show-queries) command, you can use the [`KILL QUERY`](/influxdb/v1.4/troubleshooting/query_management/#stop-currently-running-queries-with-kill-query) command to stop it. ## Why can't I query Boolean field values? diff --git a/content/influxdb/v1.5/_index.md b/content/influxdb/v1.5/_index.md index 4d9fb69b6..325a70636 100644 --- a/content/influxdb/v1.5/_index.md +++ b/content/influxdb/v1.5/_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](https://docs.influxdata.com/influxdb/v1.5/high_availability/). +If you require high availability to eliminate a single point of failure, consider the [InfluxDB Enterprise Edition](/influxdb/v1.5/high_availability/). diff --git a/content/influxdb/v1.5/about_the_project/releasenotes-changelog.md b/content/influxdb/v1.5/about_the_project/releasenotes-changelog.md index 9d78445fa..3781fb52c 100644 --- a/content/influxdb/v1.5/about_the_project/releasenotes-changelog.md +++ b/content/influxdb/v1.5/about_the_project/releasenotes-changelog.md @@ -366,7 +366,7 @@ Minor bug fixes were identified via Community and InfluxCloud. Version 1.3.0 marks the first official release of InfluxDB's new time series index (TSI) engine. The TSI engine is a significant technical advancement in InfluxDB. -It offers a solution to the [time-structured merge tree](https://docs.influxdata.com/influxdb/v1.2/concepts/storage_engine/) engine's [high series cardinality issue](/influxdb/v1.3/troubleshooting/frequently-asked-questions/#why-does-series-cardinality-matter). +It offers a solution to the [time-structured merge tree](/influxdb/v1.2/concepts/storage_engine/) engine's [high series cardinality issue](/influxdb/v1.3/troubleshooting/frequently-asked-questions/#why-does-series-cardinality-matter). With TSI, the number of series should be unbounded by the memory on the server hardware and the number of existing series will have a negligible impact on database startup time. See Paul Dix's blogpost [Path to 1 Billion Time Series: InfluxDB High Cardinality Indexing Ready for Testing](https://www.influxdata.com/path-1-billion-time-series-influxdb-high-cardinality-indexing-ready-testing/) for additional information. diff --git a/content/influxdb/v1.5/about_the_project/whats_new.md b/content/influxdb/v1.5/about_the_project/whats_new.md index 8c3984b95..9066de4a8 100644 --- a/content/influxdb/v1.5/about_the_project/whats_new.md +++ b/content/influxdb/v1.5/about_the_project/whats_new.md @@ -43,7 +43,7 @@ Starting with InfluxDB 1.5, InfluxDB OSS supports enterprise-compatible backup a * Option to run backup and restore functions on an online, or live, database. * Backup and restore functions for single or multiple databases with optional filtering based on data point timestamps. -* Data imports from [InfluxDB Enterprise](/enterprise_influxdb/latest/) clusters +* Data imports from [InfluxDB Enterprise](/{{< latest "enterprise_influxdb" >}}/) clusters * Backup files that can be imported into an InfluxDB Enterprise database. The online `restore` utility in InfluxDB OSS supports the new Enterprise-compatible backup format, but the the legacy backup format is still available. diff --git a/content/influxdb/v1.5/administration/backup_and_restore.md b/content/influxdb/v1.5/administration/backup_and_restore.md index c43aea746..5149c0470 100644 --- a/content/influxdb/v1.5/administration/backup_and_restore.md +++ b/content/influxdb/v1.5/administration/backup_and_restore.md @@ -16,7 +16,7 @@ Starting in version 1.5, the InfluxDB OSS `backup` utility provides: * Option to run backup and restore functions on online (live) databases. * Backup and restore functions for single or multiple databases, along with optional timestamp filtering. -* Data can be imported from [InfluxDB Enterprise](/enterprise_influxdb/latest/) clusters +* Data can be imported from [InfluxDB Enterprise](/{{< latest "enterprise_influxdb" >}}/) clusters * Backup files that can be imported into an InfluxDB Enterprise database. > **InfluxDB Enterprise users:** See [Backing up and restoring in InfluxDB Enterprise](/enterprise_influxdb/v1.5/administration/backup-and-restore/). diff --git a/content/influxdb/v1.5/administration/https_setup.md b/content/influxdb/v1.5/administration/https_setup.md index 571de9efb..210f83cfb 100644 --- a/content/influxdb/v1.5/administration/https_setup.md +++ b/content/influxdb/v1.5/administration/https_setup.md @@ -184,7 +184,7 @@ That's it! You've successfully set up HTTPS with InfluxDB. ## Connect Telegraf to a secured InfluxDB instance -Connecting [Telegraf](/telegraf/latest/) to an InfluxDB instance that's using +Connecting [Telegraf](/{{< latest "telegraf" >}}/) to an InfluxDB instance that's using HTTPS requires some additional steps. In Telegraf's configuration file (`/etc/telegraf/telegraf.conf`), edit the `urls` diff --git a/content/influxdb/v1.5/concepts/glossary.md b/content/influxdb/v1.5/concepts/glossary.md index 65ef865b7..bcdfa9539 100644 --- a/content/influxdb/v1.5/concepts/glossary.md +++ b/content/influxdb/v1.5/concepts/glossary.md @@ -253,7 +253,7 @@ The interval spanned by each shard group is the shard duration. Related entries: [database](/influxdb/v1.5/concepts/glossary/#database), [retention policy](/influxdb/v1.5/concepts/glossary/#retention-policy-rp), [series](/influxdb/v1.5/concepts/glossary/#series), [shard](/influxdb/v1.5/concepts/glossary/#shard), [shard duration](/influxdb/v1.5/concepts/glossary/#shard-duration) ## subscription -Subscriptions allow [Kapacitor](/kapacitor/latest/) to receive data from InfluxDB in a push model rather than the pull model based on querying data. +Subscriptions allow [Kapacitor](/{{< latest "kapacitor" >}}/) to receive data from InfluxDB in a push model rather than the pull model based on querying data. When Kapacitor is configured to work with InfluxDB, the subscription will automatically push every write for the subscribed database from InfluxDB to Kapacitor. Subscriptions can use TCP or UDP for transmitting the writes. @@ -302,7 +302,7 @@ See [InfluxQL Functions](/influxdb/v1.5/query_language/functions/#transformation Related entries: [aggregation](/influxdb/v1.5/concepts/glossary/#aggregation), [function](/influxdb/v1.5/concepts/glossary/#function), [selector](/influxdb/v1.5/concepts/glossary/#selector) ## tsm (Time Structured Merge tree) -The purpose-built data storage format for InfluxDB. TSM allows for greater compaction and higher write and read throughput than existing B+ or LSM tree implementations. See [Storage Engine](http://docs.influxdata.com/influxdb/v1.5/concepts/storage_engine/) for more. +The purpose-built data storage format for InfluxDB. TSM allows for greater compaction and higher write and read throughput than existing B+ or LSM tree implementations. See [Storage Engine](/influxdb/v1.5/concepts/storage_engine/) for more. ## user There are two kinds of users in InfluxDB: diff --git a/content/influxdb/v1.5/high_availability/clusters.md b/content/influxdb/v1.5/high_availability/clusters.md index 2b86a9502..c9aec3e99 100644 --- a/content/influxdb/v1.5/high_availability/clusters.md +++ b/content/influxdb/v1.5/high_availability/clusters.md @@ -15,4 +15,4 @@ menu: InfluxDB OSS does not support clustering. For high availability or horizontal scaling of InfluxDB, consider the InfluxData commercial clustered offering, -[InfluxDB Enterprise](/enterprise_influxdb/latest/). +[InfluxDB Enterprise](/{{< latest "enterprise_influxdb" >}}/). diff --git a/content/influxdb/v1.5/query_language/authentication_and_authorization.md b/content/influxdb/v1.5/query_language/authentication_and_authorization.md index a73bf9884..8c5bc2e86 100644 --- a/content/influxdb/v1.5/query_language/authentication_and_authorization.md +++ b/content/influxdb/v1.5/query_language/authentication_and_authorization.md @@ -153,7 +153,7 @@ password: > ## Authenticate Telegraf requests to InfluxDB > -Authenticating [Telegraf](/telegraf/latest/) requests to an InfluxDB instance with +Authenticating [Telegraf](/{{< latest "telegraf" >}}/) requests to an InfluxDB instance with authentication enabled requires some additional steps. In Telegraf's configuration file (`/etc/telegraf/telegraf.conf`), uncomment and edit the `username` and `password` settings: diff --git a/content/influxdb/v1.5/query_language/continuous_queries.md b/content/influxdb/v1.5/query_language/continuous_queries.md index 269aec159..a54c9ce10 100644 --- a/content/influxdb/v1.5/query_language/continuous_queries.md +++ b/content/influxdb/v1.5/query_language/continuous_queries.md @@ -949,6 +949,6 @@ precision data. Kapacitor, InfluxData's data processing engine, can do the same work as InfluxDB's CQs. -Check out [examples of continuous queries in Kapacitor](/kapacitor/latest/examples/continuous_queries/) to learn when +Check out [examples of continuous queries in Kapacitor](/{{< latest "kapacitor" >}}/examples/continuous_queries/) to learn when to use Kapacitor instead of InfluxDB and how to perform the same CQ functionality with a TICKscript. diff --git a/content/influxdb/v1.5/query_language/data_download.md b/content/influxdb/v1.5/query_language/data_download.md index b1f844002..7866c02b4 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/latest/tools/shell/#influx-arguments) specifies the format/precision of any returned timestamps. +* The [`-precision` argument](/{{< latest "influxdb" "v1" >}}/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.5/query_language/spec.md b/content/influxdb/v1.5/query_language/spec.md index 0ce8fd45d..1151eeff1 100644 --- a/content/influxdb/v1.5/query_language/spec.md +++ b/content/influxdb/v1.5/query_language/spec.md @@ -423,7 +423,7 @@ CREATE RETENTION POLICY "10m.events" ON "somedb" DURATION 60m REPLICATION 2 SHAR ### CREATE SUBSCRIPTION -Subscriptions tell InfluxDB to send all the data it receives to [Kapacitor](https://docs.influxdata.com/kapacitor/v1.5/introduction/). +Subscriptions tell InfluxDB to send all the data it receives to [Kapacitor](/kapacitor/v1.5/introduction/). ``` create_subscription_stmt = "CREATE SUBSCRIPTION" subscription_name "ON" db_name "." retention_policy "DESTINATIONS" ("ANY"|"ALL") host { "," host} . diff --git a/content/influxdb/v1.5/supported_protocols/_index.md b/content/influxdb/v1.5/supported_protocols/_index.md index 120640982..002873cd4 100644 --- a/content/influxdb/v1.5/supported_protocols/_index.md +++ b/content/influxdb/v1.5/supported_protocols/_index.md @@ -10,18 +10,18 @@ menu: InfluxData supports the following protocols for interacting with InfluxDB: -### [CollectD](/influxdb/latest/supported_protocols/collectd) +### [CollectD](/{{< latest "influxdb" "v1" >}}/supported_protocols/collectd) Using the collectd input, InfluxDB can accept data transmitted in collectd native format. This data is transmitted over UDP. -### [Graphite](/influxdb/latest/supported_protocols/graphite) +### [Graphite](/{{< latest "influxdb" "v1" >}}/supported_protocols/graphite) The Graphite plugin allows measurements to be saved using the Graphite line protocol. By default, enabling the Graphite plugin will allow you to collect metrics and store them using the metric name as the measurement. -### [OpenTSDB](/influxdb/latest/supported_protocols/opentsdb) +### [OpenTSDB](/{{< latest "influxdb" "v1" >}}/supported_protocols/opentsdb) InfluxDB supports both the telnet and HTTP OpenTSDB protocol. This means that InfluxDB can act as a drop-in replacement for your OpenTSDB system. -### [Prometheus](/influxdb/latest/supported_protocols/prometheus) +### [Prometheus](/{{< latest "influxdb" "v1" >}}/supported_protocols/prometheus) InfluxDB provides native support for the Prometheus read and write API to convert remote reads and writes to InfluxDB queries and endpoints. -### [UDP](/influxdb/latest/supported_protocols/udp) +### [UDP](/{{< latest "influxdb" "v1" >}}/supported_protocols/udp) UDP (User Datagram Protocol) can be used to write to InfluxDB. The CollectD input accepts data transmitted in collectd native format over UDP. diff --git a/content/influxdb/v1.5/supported_protocols/collectd.md b/content/influxdb/v1.5/supported_protocols/collectd.md index 79d83d1f8..f9d2b492e 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/latest/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.](/{{< latest "influxdb" "v1" >}}/supported_protocols/udp/#a-note-on-udpip-os-buffer-sizes) ## Configuration diff --git a/content/influxdb/v1.5/troubleshooting/frequently-asked-questions.md b/content/influxdb/v1.5/troubleshooting/frequently-asked-questions.md index a0d5a4057..ac41e2a63 100644 --- a/content/influxdb/v1.5/troubleshooting/frequently-asked-questions.md +++ b/content/influxdb/v1.5/troubleshooting/frequently-asked-questions.md @@ -251,7 +251,7 @@ Note that you will need to fully qualify the measurement to query data in the no ``` ## How do I cancel a long-running query? -You can cancel a long-running interactive query from the CLI using `Ctrl+C`. To stop other long-running query that you see when using the [`SHOW QUERIES`](https://docs.influxdata.com/influxdb/v1.3/query_language/spec/#show-queries) command, +You can cancel a long-running interactive query from the CLI using `Ctrl+C`. To stop other long-running query that you see when using the [`SHOW QUERIES`](/influxdb/v1.3/query_language/spec/#show-queries) command, you can use the [`KILL QUERY`](/influxdb/v1.5/troubleshooting/query_management/#stop-currently-running-queries-with-kill-query) command to stop it. ## Why can't I query Boolean field values? diff --git a/content/influxdb/v1.6/_index.md b/content/influxdb/v1.6/_index.md index f9757ad53..8b2a8bd83 100644 --- a/content/influxdb/v1.6/_index.md +++ b/content/influxdb/v1.6/_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](https://docs.influxdata.com/influxdb/v1.6/high_availability/). +If you require high availability to eliminate a single point of failure, consider the [InfluxDB Enterprise Edition](/influxdb/v1.6/high_availability/). diff --git a/content/influxdb/v1.6/about_the_project/releasenotes-changelog.md b/content/influxdb/v1.6/about_the_project/releasenotes-changelog.md index f859ffe61..17ddf6d83 100644 --- a/content/influxdb/v1.6/about_the_project/releasenotes-changelog.md +++ b/content/influxdb/v1.6/about_the_project/releasenotes-changelog.md @@ -515,7 +515,7 @@ Minor bug fixes were identified via Community and InfluxCloud. Version 1.3.0 marks the first official release of InfluxDB's new time series index (TSI) engine. The TSI engine is a significant technical advancement in InfluxDB. -It offers a solution to the [time-structured merge tree](https://docs.influxdata.com/influxdb/v1.2/concepts/storage_engine/) engine's [high series cardinality issue](/influxdb/v1.3/troubleshooting/frequently-asked-questions/#why-does-series-cardinality-matter). +It offers a solution to the [time-structured merge tree](/influxdb/v1.2/concepts/storage_engine/) engine's [high series cardinality issue](/influxdb/v1.3/troubleshooting/frequently-asked-questions/#why-does-series-cardinality-matter). With TSI, the number of series should be unbounded by the memory on the server hardware and the number of existing series will have a negligible impact on database startup time. See Paul Dix's blogpost [Path to 1 Billion Time Series: InfluxDB High Cardinality Indexing Ready for Testing](https://www.influxdata.com/path-1-billion-time-series-influxdb-high-cardinality-indexing-ready-testing/) for additional information. diff --git a/content/influxdb/v1.6/administration/authentication_and_authorization.md b/content/influxdb/v1.6/administration/authentication_and_authorization.md index f42fa7800..d94e2f695 100644 --- a/content/influxdb/v1.6/administration/authentication_and_authorization.md +++ b/content/influxdb/v1.6/administration/authentication_and_authorization.md @@ -153,7 +153,7 @@ password: > ## Authenticate Telegraf requests to InfluxDB > -Authenticating [Telegraf](/telegraf/latest/) requests to an InfluxDB instance with +Authenticating [Telegraf](/{{< latest "telegraf" >}}/) requests to an InfluxDB instance with authentication enabled requires some additional steps. In Telegraf's configuration file (`/etc/telegraf/telegraf.conf`), uncomment and edit the `username` and `password` settings: diff --git a/content/influxdb/v1.6/administration/backup_and_restore.md b/content/influxdb/v1.6/administration/backup_and_restore.md index 8707ff492..5a186a6b5 100644 --- a/content/influxdb/v1.6/administration/backup_and_restore.md +++ b/content/influxdb/v1.6/administration/backup_and_restore.md @@ -16,10 +16,10 @@ Starting in version 1.5, the InfluxDB OSS `backup` utility provides: * Option to run backup and restore functions on online (live) databases. * Backup and restore functions for single or multiple databases, along with optional timestamp filtering. -* Data can be imported from [InfluxDB Enterprise](/enterprise_influxdb/latest/) clusters +* Data can be imported from [InfluxDB Enterprise](/{{< latest "enterprise_influxdb" >}}/) clusters * Backup files that can be imported into an InfluxDB Enterprise database. -> **InfluxDB Enterprise users:** See [Backing up and restoring in InfluxDB Enterprise](/enterprise_influxdb/latest/administration/backup-and-restore/). +> **InfluxDB Enterprise users:** See [Backing up and restoring in InfluxDB Enterprise](/{{< latest "enterprise_influxdb" >}}/administration/backup-and-restore/). > ***Note:*** Prior to InfluxDB OSS 1.5, the `backup` utility created backup file formats incompatible with InfluxDB Enterprise. This legacy format is still supported in the new `backup` utility as input for the new *online* restore function. The *offline* backup and restore utilities in InfluxDB OSS versions 1.4 and earlier are deprecated, but are documented below in [Backward compatible offline backup and restore](#backward-compatible-offline-backup-and-restore-legacy-format). diff --git a/content/influxdb/v1.6/administration/https_setup.md b/content/influxdb/v1.6/administration/https_setup.md index fbae3af5b..fd7a77b34 100644 --- a/content/influxdb/v1.6/administration/https_setup.md +++ b/content/influxdb/v1.6/administration/https_setup.md @@ -171,7 +171,7 @@ Enable HTTPS in InfluxDB's the `[http]` section of the configuration file (`/etc ``` > If setting up HTTPS for [InfluxDB Enterprise](/enterprise_influxdb), you also need to configure insecure TLS connections between both meta and data nodes in your cluster. -> Instructions are provided in the [InfluxDB Enterprise HTTPS Setup guide](/enterprise_influxdb/latest/guides/https_setup/#setup-https-with-a-self-signed-certificate). +> Instructions are provided in the [InfluxDB Enterprise HTTPS Setup guide](/{{< latest "enterprise_influxdb" >}}/guides/https_setup/#setup-https-with-a-self-signed-certificate). #### Step 4: Restart InfluxDB @@ -199,7 +199,7 @@ That's it! You've successfully set up HTTPS with InfluxDB. > ## Connect Telegraf to a secured InfluxDB instance > -Connecting [Telegraf](/telegraf/latest/) to an InfluxDB instance that's using +Connecting [Telegraf](/{{< latest "telegraf" >}}/) to an InfluxDB instance that's using HTTPS requires some additional steps. > In Telegraf's configuration file (`/etc/telegraf/telegraf.conf`), edit the `urls` diff --git a/content/influxdb/v1.6/administration/subscription-management.md b/content/influxdb/v1.6/administration/subscription-management.md index 486f9dea5..3c4121ff9 100644 --- a/content/influxdb/v1.6/administration/subscription-management.md +++ b/content/influxdb/v1.6/administration/subscription-management.md @@ -82,7 +82,7 @@ CREATE SUBSCRIPTION "mysub" ON "mydb"."autogen" DESTINATIONS ANY 'http://host1.e Subscriptions can use HTTP, HTTPS, or UDP transport protocols. Which to use is determined by the protocol expected by the subscription endpoint. If creating a Kapacitor subscription, this is defined by the `subscription-protocol` -option in the `[[influxdb]]` section of your [`kapacitor.conf`](/kapacitor/latest/administration/subscription-management/#subscription-protocol). +option in the `[[influxdb]]` section of your [`kapacitor.conf`](/{{< latest "kapacitor" >}}/administration/subscription-management/#subscription-protocol). _**kapacitor.conf**_ ```toml diff --git a/content/influxdb/v1.6/concepts/glossary.md b/content/influxdb/v1.6/concepts/glossary.md index 479ba5d74..f9fc23b36 100644 --- a/content/influxdb/v1.6/concepts/glossary.md +++ b/content/influxdb/v1.6/concepts/glossary.md @@ -253,7 +253,7 @@ The interval spanned by each shard group is the shard duration. Related entries: [database](/influxdb/v1.6/concepts/glossary/#database), [retention policy](/influxdb/v1.6/concepts/glossary/#retention-policy-rp), [series](/influxdb/v1.6/concepts/glossary/#series), [shard](/influxdb/v1.6/concepts/glossary/#shard), [shard duration](/influxdb/v1.6/concepts/glossary/#shard-duration) ## subscription -Subscriptions allow [Kapacitor](/kapacitor/latest/) to receive data from InfluxDB in a push model rather than the pull model based on querying data. +Subscriptions allow [Kapacitor](/{{< latest "kapacitor" >}}/) to receive data from InfluxDB in a push model rather than the pull model based on querying data. When Kapacitor is configured to work with InfluxDB, the subscription will automatically push every write for the subscribed database from InfluxDB to Kapacitor. Subscriptions can use TCP or UDP for transmitting the writes. @@ -302,7 +302,7 @@ See [InfluxQL Functions](/influxdb/v1.6/query_language/functions/#transformation Related entries: [aggregation](/influxdb/v1.6/concepts/glossary/#aggregation), [function](/influxdb/v1.6/concepts/glossary/#function), [selector](/influxdb/v1.6/concepts/glossary/#selector) ## tsm (Time Structured Merge tree) -The purpose-built data storage format for InfluxDB. TSM allows for greater compaction and higher write and read throughput than existing B+ or LSM tree implementations. See [Storage Engine](http://docs.influxdata.com/influxdb/v1.6/concepts/storage_engine/) for more. +The purpose-built data storage format for InfluxDB. TSM allows for greater compaction and higher write and read throughput than existing B+ or LSM tree implementations. See [Storage Engine](/influxdb/v1.6/concepts/storage_engine/) for more. ## user There are two kinds of users in InfluxDB: diff --git a/content/influxdb/v1.6/high_availability/clusters.md b/content/influxdb/v1.6/high_availability/clusters.md index fada2d783..39f0d8cba 100644 --- a/content/influxdb/v1.6/high_availability/clusters.md +++ b/content/influxdb/v1.6/high_availability/clusters.md @@ -15,4 +15,4 @@ menu: InfluxDB OSS does not support clustering. For high availability or horizontal scaling of InfluxDB, consider the InfluxData commercial clustered offering, -[InfluxDB Enterprise](/enterprise_influxdb/latest/). +[InfluxDB Enterprise](/{{< latest "enterprise_influxdb" >}}/). diff --git a/content/influxdb/v1.6/query_language/continuous_queries.md b/content/influxdb/v1.6/query_language/continuous_queries.md index b9f2b501f..4c819560d 100644 --- a/content/influxdb/v1.6/query_language/continuous_queries.md +++ b/content/influxdb/v1.6/query_language/continuous_queries.md @@ -949,6 +949,6 @@ precision data. Kapacitor, InfluxData's data processing engine, can do the same work as InfluxDB's CQs. -Check out [examples of continuous queries in Kapacitor](/kapacitor/latest/examples/continuous_queries/) to learn when +Check out [examples of continuous queries in Kapacitor](/{{< latest "kapacitor" >}}/examples/continuous_queries/) to learn when to use Kapacitor instead of InfluxDB and how to perform the same CQ functionality with a TICKscript. diff --git a/content/influxdb/v1.6/query_language/data_download.md b/content/influxdb/v1.6/query_language/data_download.md index fe679058c..51e7cbe0b 100644 --- a/content/influxdb/v1.6/query_language/data_download.md +++ b/content/influxdb/v1.6/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/latest/tools/shell/#influx-arguments) specifies the format/precision of any returned timestamps. +* The [`-precision` argument](/{{< latest "influxdb" "v1" >}}/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.6/query_language/spec.md b/content/influxdb/v1.6/query_language/spec.md index d24dc3c0a..81712e6de 100644 --- a/content/influxdb/v1.6/query_language/spec.md +++ b/content/influxdb/v1.6/query_language/spec.md @@ -424,7 +424,7 @@ CREATE RETENTION POLICY "10m.events" ON "somedb" DURATION 60m REPLICATION 2 SHAR ### CREATE SUBSCRIPTION -Subscriptions tell InfluxDB to send all the data it receives to [Kapacitor](/kapacitor/latest/introduction/). +Subscriptions tell InfluxDB to send all the data it receives to [Kapacitor](/{{< latest "kapacitor" >}}/introduction/). ``` create_subscription_stmt = "CREATE SUBSCRIPTION" subscription_name "ON" db_name "." retention_policy "DESTINATIONS" ("ANY"|"ALL") host { "," host} . diff --git a/content/influxdb/v1.6/supported_protocols/_index.md b/content/influxdb/v1.6/supported_protocols/_index.md index b42ef3ee8..2591658cf 100644 --- a/content/influxdb/v1.6/supported_protocols/_index.md +++ b/content/influxdb/v1.6/supported_protocols/_index.md @@ -10,18 +10,18 @@ menu: InfluxData supports the following protocols for interacting with InfluxDB: -### [CollectD](/influxdb/latest/supported_protocols/collectd) +### [CollectD](/{{< latest "influxdb" "v1" >}}/supported_protocols/collectd) Using the collectd input, InfluxDB can accept data transmitted in collectd native format. This data is transmitted over UDP. -### [Graphite](/influxdb/latest/supported_protocols/graphite) +### [Graphite](/{{< latest "influxdb" "v1" >}}/supported_protocols/graphite) The Graphite plugin allows measurements to be saved using the Graphite line protocol. By default, enabling the Graphite plugin will allow you to collect metrics and store them using the metric name as the measurement. -### [OpenTSDB](/influxdb/latest/supported_protocols/opentsdb) +### [OpenTSDB](/{{< latest "influxdb" "v1" >}}/supported_protocols/opentsdb) InfluxDB supports both the telnet and HTTP OpenTSDB protocol. This means that InfluxDB can act as a drop-in replacement for your OpenTSDB system. -### [Prometheus](/influxdb/latest/supported_protocols/prometheus) +### [Prometheus](/{{< latest "influxdb" "v1" >}}/supported_protocols/prometheus) InfluxDB provides native support for the Prometheus read and write API to convert remote reads and writes to InfluxDB queries and endpoints. -### [UDP](/influxdb/latest/supported_protocols/udp) +### [UDP](/{{< latest "influxdb" "v1" >}}/supported_protocols/udp) UDP (User Datagram Protocol) can be used to write to InfluxDB. The CollectD input accepts data transmitted in collectd native format over UDP. diff --git a/content/influxdb/v1.6/supported_protocols/collectd.md b/content/influxdb/v1.6/supported_protocols/collectd.md index ffc2e567a..6db666522 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/latest/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.](/{{< latest "influxdb" "v1" >}}/supported_protocols/udp/#a-note-on-udpip-os-buffer-sizes) ## Configuration diff --git a/content/influxdb/v1.6/troubleshooting/frequently-asked-questions.md b/content/influxdb/v1.6/troubleshooting/frequently-asked-questions.md index 568409120..e24a633a8 100644 --- a/content/influxdb/v1.6/troubleshooting/frequently-asked-questions.md +++ b/content/influxdb/v1.6/troubleshooting/frequently-asked-questions.md @@ -251,7 +251,7 @@ Note that you will need to fully qualify the measurement to query data in the no ``` ## How do I cancel a long-running query? -You can cancel a long-running interactive query from the CLI using `Ctrl+C`. To stop other long-running query that you see when using the [`SHOW QUERIES`](https://docs.influxdata.com/influxdb/v1.3/query_language/spec/#show-queries) command, +You can cancel a long-running interactive query from the CLI using `Ctrl+C`. To stop other long-running query that you see when using the [`SHOW QUERIES`](/influxdb/v1.3/query_language/spec/#show-queries) command, you can use the [`KILL QUERY`](/influxdb/v1.6/troubleshooting/query_management/#stop-currently-running-queries-with-kill-query) command to stop it. ## Why can't I query Boolean field values? diff --git a/content/influxdb/v1.7/_index.md b/content/influxdb/v1.7/_index.md index 6e3e9a951..cb73da825 100644 --- a/content/influxdb/v1.7/_index.md +++ b/content/influxdb/v1.7/_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](https://docs.influxdata.com/influxdb/latest/high_availability/). +If you require high availability to eliminate a single point of failure, consider the [InfluxDB Enterprise Edition](/{{< latest "influxdb" "v1" >}}/high_availability/). diff --git a/content/influxdb/v1.7/administration/authentication_and_authorization.md b/content/influxdb/v1.7/administration/authentication_and_authorization.md index 5be535591..a0d577498 100644 --- a/content/influxdb/v1.7/administration/authentication_and_authorization.md +++ b/content/influxdb/v1.7/administration/authentication_and_authorization.md @@ -226,7 +226,7 @@ curl -XGET "http://localhost:8086/query?db=demodb" \ ## Authenticate Telegraf requests to InfluxDB -Authenticating [Telegraf](/telegraf/latest/) requests to an InfluxDB instance with +Authenticating [Telegraf](/{{< latest "telegraf" >}}/) requests to an InfluxDB instance with authentication enabled requires some additional steps. In the Telegraf configuration file (`/etc/telegraf/telegraf.conf`), uncomment and edit the `username` and `password` settings. diff --git a/content/influxdb/v1.7/administration/backup_and_restore.md b/content/influxdb/v1.7/administration/backup_and_restore.md index 647d7c941..c4a728b3b 100644 --- a/content/influxdb/v1.7/administration/backup_and_restore.md +++ b/content/influxdb/v1.7/administration/backup_and_restore.md @@ -16,10 +16,10 @@ The InfluxDB OSS `backup` utility provides: * Option to run backup and restore functions on online (live) databases. * Backup and restore functions for single or multiple databases, along with optional timestamp filtering. -* Data can be imported from [InfluxDB Enterprise](/enterprise_influxdb/latest/) clusters +* Data can be imported from [InfluxDB Enterprise](/{{< latest "enterprise_influxdb" >}}/) clusters * Backup files that can be imported into an InfluxDB Enterprise database. -> **InfluxDB Enterprise users:** See [Backing up and restoring in InfluxDB Enterprise](/enterprise_influxdb/latest/administration/backup-and-restore/). +> **InfluxDB Enterprise users:** See [Backing up and restoring in InfluxDB Enterprise](/{{< latest "enterprise_influxdb" >}}/administration/backup-and-restore/). > ***Note:*** Prior to InfluxDB OSS 1.5, the `backup` utility created backup file formats incompatible with InfluxDB Enterprise. This legacy format is still supported in the new `backup` utility as input for the new *online* restore function. The *offline* backup and restore utilities in InfluxDB OSS versions 1.4 and earlier are deprecated, but are documented below in [Backward compatible offline backup and restore](#backward-compatible-offline-backup-and-restore-legacy-format). diff --git a/content/influxdb/v1.7/administration/https_setup.md b/content/influxdb/v1.7/administration/https_setup.md index db9aeb784..29edefe00 100644 --- a/content/influxdb/v1.7/administration/https_setup.md +++ b/content/influxdb/v1.7/administration/https_setup.md @@ -129,7 +129,7 @@ InfluxDB supports three types of TLS certificates: ## Connect Telegraf to a secured InfluxDB instance -Connecting [Telegraf](/telegraf/latest/) to an InfluxDB instance that's using +Connecting [Telegraf](/{{< latest "telegraf" >}}/) to an InfluxDB instance that's using HTTPS requires some additional steps. In the Telegraf configuration file (`/etc/telegraf/telegraf.conf`), edit the `urls` diff --git a/content/influxdb/v1.7/administration/rebuild-tsi-index.md b/content/influxdb/v1.7/administration/rebuild-tsi-index.md index 250f53dc0..cbdd1de72 100644 --- a/content/influxdb/v1.7/administration/rebuild-tsi-index.md +++ b/content/influxdb/v1.7/administration/rebuild-tsi-index.md @@ -47,6 +47,6 @@ Restart InfluxDB by starting the `influxd` process. To rebuild the TSI index in an InfluxDB Enterprise cluster, perform the steps above on each data node in the cluster one after the other. After restarting the `influxd` process on a data node, allow the -[hinted handoff queue (HHQ)](/enterprise_influxdb/latest/concepts/clustering/#hinted-handoff) +[hinted handoff queue (HHQ)](/{{< latest "enterprise_influxdb" >}}/concepts/clustering/#hinted-handoff) to write all missed data to the updated node before moving on to the next node. {{% /note %}} diff --git a/content/influxdb/v1.7/administration/subscription-management.md b/content/influxdb/v1.7/administration/subscription-management.md index fdfb91d70..03ef3f215 100644 --- a/content/influxdb/v1.7/administration/subscription-management.md +++ b/content/influxdb/v1.7/administration/subscription-management.md @@ -99,7 +99,7 @@ CREATE SUBSCRIPTION "mysub" ON "mydb"."autogen" DESTINATIONS ANY 'http://host1.e Subscriptions can use HTTP, HTTPS, or UDP transport protocols. Which to use is determined by the protocol expected by the subscription endpoint. If creating a Kapacitor subscription, this is defined by the `subscription-protocol` -option in the `[[influxdb]]` section of your [`kapacitor.conf`](/kapacitor/latest/administration/subscription-management/#subscription-protocol). +option in the `[[influxdb]]` section of your [`kapacitor.conf`](/{{< latest "kapacitor" >}}/administration/subscription-management/#subscription-protocol). _**kapacitor.conf**_ diff --git a/content/influxdb/v1.7/concepts/glossary.md b/content/influxdb/v1.7/concepts/glossary.md index ea3959fb4..8ba1b83a1 100644 --- a/content/influxdb/v1.7/concepts/glossary.md +++ b/content/influxdb/v1.7/concepts/glossary.md @@ -290,7 +290,7 @@ Related entries: [database](/influxdb/v1.7/concepts/glossary/#database), [retent ## subscription -Subscriptions allow [Kapacitor](/kapacitor/latest/) to receive data from InfluxDB in a push model rather than the pull model based on querying data. +Subscriptions allow [Kapacitor](/{{< latest "kapacitor" >}}/) to receive data from InfluxDB in a push model rather than the pull model based on querying data. When Kapacitor is configured to work with InfluxDB, the subscription will automatically push every write for the subscribed database from InfluxDB to Kapacitor. Subscriptions can use TCP or UDP for transmitting the writes. @@ -346,7 +346,7 @@ Related entries: [aggregation](/influxdb/v1.7/concepts/glossary/#aggregation), [ ## TSM (Time Structured Merge tree) -The purpose-built data storage format for InfluxDB. TSM allows for greater compaction and higher write and read throughput than existing B+ or LSM tree implementations. See [Storage Engine](http://docs.influxdata.com/influxdb/v1.7/concepts/storage_engine/) for more. +The purpose-built data storage format for InfluxDB. TSM allows for greater compaction and higher write and read throughput than existing B+ or LSM tree implementations. See [Storage Engine](/influxdb/v1.7/concepts/storage_engine/) for more. ## user diff --git a/content/influxdb/v1.7/concepts/time-series-index.md b/content/influxdb/v1.7/concepts/time-series-index.md index 88176d2bf..c2df8b09e 100644 --- a/content/influxdb/v1.7/concepts/time-series-index.md +++ b/content/influxdb/v1.7/concepts/time-series-index.md @@ -8,7 +8,7 @@ menu: parent: Concepts --- -Find overview and background information on Time Series Index (TSI) in this topic. For detail, including how to enable and configure TSI, see [Time Series Index (TSI) details](https://docs.influxdata.com/influxdb/v1.7/concepts/tsi-details/). +Find overview and background information on Time Series Index (TSI) in this topic. For detail, including how to enable and configure TSI, see [Time Series Index (TSI) details](/influxdb/v1.7/concepts/tsi-details/). ## Overview diff --git a/content/influxdb/v1.7/concepts/tsi-details.md b/content/influxdb/v1.7/concepts/tsi-details.md index 22cb4483b..0d216961a 100644 --- a/content/influxdb/v1.7/concepts/tsi-details.md +++ b/content/influxdb/v1.7/concepts/tsi-details.md @@ -17,7 +17,7 @@ TSI uses the operating system's page cache to pull hot data into memory, leaving ## Enable TSI -- For **InfluxDB OSS**, complete step 3 and 4 of [Upgrading to InfluxDB 1.7.x](https://docs.influxdata.com/influxdb/v1.7/administration/upgrading/#upgrade-to-influxdb-1-7-x). +- For **InfluxDB OSS**, complete step 3 and 4 of [Upgrading to InfluxDB 1.7.x](/influxdb/v1.7/administration/upgrading/#upgrade-to-influxdb-1-7-x). - For **InfluxDB Enterprise**, on each data node in your cluster, complete step 2 and steps 4-7 of [Upgrade data nodes](/enterprise_influxdb/v1.7/administration/upgrading/#upgrade-data-nodes). diff --git a/content/influxdb/v1.7/high_availability/clusters.md b/content/influxdb/v1.7/high_availability/clusters.md index fcbf47ae8..654017209 100644 --- a/content/influxdb/v1.7/high_availability/clusters.md +++ b/content/influxdb/v1.7/high_availability/clusters.md @@ -15,4 +15,4 @@ menu: InfluxDB OSS does not support clustering. For high availability or horizontal scaling of InfluxDB, consider the InfluxData commercial clustered offering, -[InfluxDB Enterprise](/enterprise_influxdb/latest/). +[InfluxDB Enterprise](/{{< latest "enterprise_influxdb" >}}/). diff --git a/content/influxdb/v1.7/query_language/continuous_queries.md b/content/influxdb/v1.7/query_language/continuous_queries.md index 5348ea210..512567bf3 100644 --- a/content/influxdb/v1.7/query_language/continuous_queries.md +++ b/content/influxdb/v1.7/query_language/continuous_queries.md @@ -982,4 +982,4 @@ Kapacitor, InfluxData's data processing engine, can do the same work as continuous queries in InfluxDB databases. To learn when to use Kapacitor instead of InfluxDB and how to perform the same CQ -functionality with a TICKscript, see [examples of continuous queries in Kapacitor](/kapacitor/latest/examples/continuous_queries/). +functionality with a TICKscript, see [examples of continuous queries in Kapacitor](/{{< latest "kapacitor" >}}/examples/continuous_queries/). diff --git a/content/influxdb/v1.7/query_language/data_download.md b/content/influxdb/v1.7/query_language/data_download.md index b2715321d..44a16e694 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/latest/tools/shell/#influx-options) specifies the format/precision of any returned timestamps. +* The [`-precision` argument](/{{< latest "influxdb" "v1" >}}/tools/shell/#influx-options) 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/data_exploration.md b/content/influxdb/v1.7/query_language/data_exploration.md index a7c7a04fd..6f38c0b6d 100644 --- a/content/influxdb/v1.7/query_language/data_exploration.md +++ b/content/influxdb/v1.7/query_language/data_exploration.md @@ -1959,7 +1959,7 @@ with the most recent timestamps first. InfluxQL returns series in sorted order, which lets you limit or offset query results by series (rather than by row) using [slimit](/influxdb/v1.7/query_language/data_exploration/#the-slimit-clause) and -[soffset](https://docs.influxdata.com/influxdb/v1.7/query_language/data_exploration/#the-soffset-clause). +[soffset](/influxdb/v1.7/query_language/data_exploration/#the-soffset-clause). This is useful for paging through results by time. diff --git a/content/influxdb/v1.7/query_language/spec.md b/content/influxdb/v1.7/query_language/spec.md index ab404c0a7..78cd47331 100644 --- a/content/influxdb/v1.7/query_language/spec.md +++ b/content/influxdb/v1.7/query_language/spec.md @@ -426,7 +426,7 @@ CREATE RETENTION POLICY "10m.events" ON "somedb" DURATION 60m REPLICATION 2 SHAR ### CREATE SUBSCRIPTION -Subscriptions tell InfluxDB to send all the data it receives to [Kapacitor](/kapacitor/latest/introduction/). +Subscriptions tell InfluxDB to send all the data it receives to [Kapacitor](/{{< latest "kapacitor" >}}/introduction/). ``` create_subscription_stmt = "CREATE SUBSCRIPTION" subscription_name "ON" db_name "." retention_policy "DESTINATIONS" ("ANY"|"ALL") host { "," host} . diff --git a/content/influxdb/v1.7/supported_protocols/collectd.md b/content/influxdb/v1.7/supported_protocols/collectd.md index cd1fe153e..b6e8436f0 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/latest/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.](/{{< latest "influxdb" "v1" >}}/supported_protocols/udp/#a-note-on-udpip-os-buffer-sizes) ## Configuration diff --git a/content/influxdb/v1.7/tools/_index.md b/content/influxdb/v1.7/tools/_index.md index b3996e9e6..ae09ebc7a 100644 --- a/content/influxdb/v1.7/tools/_index.md +++ b/content/influxdb/v1.7/tools/_index.md @@ -47,7 +47,7 @@ Use the InfluxDB inch tool to test InfluxDB performance. Adjust metrics such as ## Graphs and dashboards -Use [Chronograf](/chronograf/latest/) or [Grafana](https://grafana.com/docs/grafana/latest/features/datasources/influxdb/) dashboards to visualize your time series data. +Use [Chronograf](/{{< latest "chronograf" >}}/) or [Grafana](https://grafana.com/docs/grafana/latest/features/datasources/influxdb/) dashboards to visualize your time series data. > **Tip:** Use template variables in your dashboards to filter meta query results by a specified period of time (see example below). @@ -69,4 +69,4 @@ WHERE time > now() - 1h GROUP BY time(1h), host, team, status, location END; SHOW TAG VALUES FROM "your.system"."host_info" WITH KEY = “host” ``` -> **Note:** In Chronograf, you can also filter meta query results for a specified time range by [creating a `custom meta query` template variable](/chronograf/latest/guides/dashboard-template-variables/#create-custom-template-variables) and adding a time range filter. +> **Note:** In Chronograf, you can also filter meta query results for a specified time range by [creating a `custom meta query` template variable](/{{< latest "chronograf" >}}/guides/dashboard-template-variables/#create-custom-template-variables) and adding a time range filter. diff --git a/content/influxdb/v1.7/tools/api.md b/content/influxdb/v1.7/tools/api.md index 59b4582bf..3b89efded 100644 --- a/content/influxdb/v1.7/tools/api.md +++ b/content/influxdb/v1.7/tools/api.md @@ -810,7 +810,7 @@ Errors are returned in JSON. | 400 Bad Request | Unacceptable request. Can occur with an InfluxDB line protocol syntax error or if a user attempts to write values to a field that previously accepted a different value type. The returned JSON offers further information. | | 401 Unauthorized | Unacceptable request. Can occur with invalid authentication credentials. | | 404 Not Found | Unacceptable request. Can occur if a user attempts to write to a database that does not exist. The returned JSON offers further information. | -| 413 Request Entity Too Large | Unaccetable request. It will occur if the payload of the POST request is bigger than the maximum size allowed. See [`max-body-size`](https://docs.influxdata.com/influxdb/latest/administration/config/#max-body-size-25000000) parameter for more details. +| 413 Request Entity Too Large | Unaccetable request. It will occur if the payload of the POST request is bigger than the maximum size allowed. See [`max-body-size`](/{{< latest "influxdb" "v1" >}}/administration/config/#max-body-size-25000000) parameter for more details. | 500 Internal Server Error | The system is overloaded or significantly impaired. Can occur if a user attempts to write to a retention policy that does not exist. The returned JSON offers further information. | #### Examples diff --git a/content/influxdb/v1.7/tools/influxd-cli/_index.md b/content/influxdb/v1.7/tools/influxd-cli/_index.md index ec11c25c6..20098231d 100644 --- a/content/influxdb/v1.7/tools/influxd-cli/_index.md +++ b/content/influxdb/v1.7/tools/influxd-cli/_index.md @@ -19,9 +19,9 @@ influxd [[command] [arguments]] ## Commands | Command | Description | |-------------------------------------------------------|----------------------------------------------------------| -| [backup](/influxdb/latest/tools/influxd-cli/backup) | Download a snapshot of a data node and saves it to disk. | -| [config](/influxdb/latest/tools/influxd-cli/config) | Display the default configuration. | +| [backup](/{{< latest "influxdb" "v1" >}}/tools/influxd-cli/backup) | Download a snapshot of a data node and saves it to disk. | +| [config](/{{< latest "influxdb" "v1" >}}/tools/influxd-cli/config) | Display the default configuration. | | help | Display the help message. | -| [restore](/influxdb/latest/tools/influxd-cli/restore) | Use a snapshot of a data node to rebuild a cluster. | -| [run](/influxdb/latest/tools/influxd-cli/run) | Run node with existing configuration. | -| [version](/influxdb/latest/tools/influxd-cli/version) | Display the InfluxDB version. | +| [restore](/{{< latest "influxdb" "v1" >}}/tools/influxd-cli/restore) | Use a snapshot of a data node to rebuild a cluster. | +| [run](/{{< latest "influxdb" "v1" >}}/tools/influxd-cli/run) | Run node with existing configuration. | +| [version](/{{< latest "influxdb" "v1" >}}/tools/influxd-cli/version) | Display the InfluxDB version. | diff --git a/content/influxdb/v1.7/troubleshooting/frequently-asked-questions.md b/content/influxdb/v1.7/troubleshooting/frequently-asked-questions.md index 9dfd5a9d0..d9ca032de 100644 --- a/content/influxdb/v1.7/troubleshooting/frequently-asked-questions.md +++ b/content/influxdb/v1.7/troubleshooting/frequently-asked-questions.md @@ -280,7 +280,7 @@ Note that you will need to fully qualify the measurement to query data in the no ## How do I cancel a long-running query? -You can cancel a long-running interactive query from the CLI using `Ctrl+C`. To stop other long-running query that you see when using the [`SHOW QUERIES`](https://docs.influxdata.com/influxdb/v1.3/query_language/spec/#show-queries) command, +You can cancel a long-running interactive query from the CLI using `Ctrl+C`. To stop other long-running query that you see when using the [`SHOW QUERIES`](/influxdb/v1.3/query_language/spec/#show-queries) command, you can use the [`KILL QUERY`](/influxdb/v1.7/troubleshooting/query_management/#stop-currently-running-queries-with-kill-query) command to stop it. ## Why can't I query Boolean field values? diff --git a/content/influxdb/v1.8/_index.md b/content/influxdb/v1.8/_index.md index 543abc581..e41c8475b 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](https://docs.influxdata.com/influxdb/latest/high_availability/). +If you require high availability to eliminate a single point of failure, consider the [InfluxDB Enterprise Edition](/{{< latest "influxdb" "v1" >}}/high_availability/). diff --git a/content/influxdb/v1.8/administration/authentication_and_authorization.md b/content/influxdb/v1.8/administration/authentication_and_authorization.md index 0b7a4a4a1..0c75843e0 100644 --- a/content/influxdb/v1.8/administration/authentication_and_authorization.md +++ b/content/influxdb/v1.8/administration/authentication_and_authorization.md @@ -215,7 +215,7 @@ curl -XGET "http://localhost:8086/query?db=demodb" \ ## Authenticate Telegraf requests to InfluxDB -Authenticating [Telegraf](/telegraf/latest/) requests to an InfluxDB instance with +Authenticating [Telegraf](/{{< latest "telegraf" >}}/) requests to an InfluxDB instance with authentication enabled requires some additional steps. In the Telegraf configuration file (`/etc/telegraf/telegraf.conf`), uncomment and edit the `username` and `password` settings. diff --git a/content/influxdb/v1.8/administration/backup_and_restore.md b/content/influxdb/v1.8/administration/backup_and_restore.md index aae13fff0..cc19088b4 100644 --- a/content/influxdb/v1.8/administration/backup_and_restore.md +++ b/content/influxdb/v1.8/administration/backup_and_restore.md @@ -16,10 +16,10 @@ The InfluxDB OSS `backup` utility provides: * Option to run backup and restore functions on online (live) databases. * Backup and restore functions for single or multiple databases, along with optional timestamp filtering. -* Data can be imported from [InfluxDB Enterprise](/enterprise_influxdb/latest/) clusters +* Data can be imported from [InfluxDB Enterprise](/{{< latest "enterprise_influxdb" >}}/) clusters * Backup files that can be imported into an InfluxDB Enterprise database. -> **InfluxDB Enterprise users:** See [Backing up and restoring in InfluxDB Enterprise](/enterprise_influxdb/latest/administration/backup-and-restore/). +> **InfluxDB Enterprise users:** See [Backing up and restoring in InfluxDB Enterprise](/{{< latest "enterprise_influxdb" >}}/administration/backup-and-restore/). > ***Note:*** Prior to InfluxDB OSS 1.5, the `backup` utility created backup file formats incompatible with InfluxDB Enterprise. This legacy format is still supported in the new `backup` utility as input for the new *online* restore function. The *offline* backup and restore utilities in InfluxDB OSS versions 1.4 and earlier are deprecated, but are documented below in [Backward compatible offline backup and restore](#backward-compatible-offline-backup-and-restore-legacy-format). diff --git a/content/influxdb/v1.8/administration/compact-series-file.md b/content/influxdb/v1.8/administration/compact-series-file.md index 134985a70..2ae7ad125 100644 --- a/content/influxdb/v1.8/administration/compact-series-file.md +++ b/content/influxdb/v1.8/administration/compact-series-file.md @@ -31,6 +31,6 @@ This is useful for series files that grow quickly, for example, when series are 4. **_(InfluxDB Enterprise only)_** On each data node: 1. Complete steps 1-3. - 2. Wait for the [hinted handoff queue (HHQ)](/enterprise_influxdb/latest/concepts/clustering/#hinted-handoff) + 2. Wait for the [hinted handoff queue (HHQ)](/{{< latest "enterprise_influxdb" >}}/concepts/clustering/#hinted-handoff) to write all missed data to the node. 3. Continue to the next data node. diff --git a/content/influxdb/v1.8/administration/https_setup.md b/content/influxdb/v1.8/administration/https_setup.md index 541a82b9f..8089aa03e 100644 --- a/content/influxdb/v1.8/administration/https_setup.md +++ b/content/influxdb/v1.8/administration/https_setup.md @@ -179,7 +179,7 @@ Enable HTTPS in the `[http]` section of the configuration file (`/etc/influxdb/i ``` > If setting up HTTPS for [InfluxDB Enterprise](/enterprise_influxdb), you also need to configure insecure TLS connections between both meta and data nodes in your cluster. -> Instructions are provided in the [InfluxDB Enterprise HTTPS Setup guide](/enterprise_influxdb/latest/guides/https_setup/#set-up-https-with-a-self-signed-certificate). +> Instructions are provided in the [InfluxDB Enterprise HTTPS Setup guide](/{{< latest "enterprise_influxdb" >}}/guides/https_setup/#set-up-https-with-a-self-signed-certificate). #### Step 4: Restart InfluxDB @@ -209,7 +209,7 @@ That's it! You've successfully set up HTTPS with InfluxDB. ## Connect Telegraf to a secured InfluxDB instance -Connecting [Telegraf](/telegraf/latest/) to an InfluxDB instance that's using +Connecting [Telegraf](/{{< latest "telegraf" >}}/) to an InfluxDB instance that's using HTTPS requires some additional steps. In the Telegraf configuration file (`/etc/telegraf/telegraf.conf`), edit the `urls` diff --git a/content/influxdb/v1.8/administration/rebuild-tsi-index.md b/content/influxdb/v1.8/administration/rebuild-tsi-index.md index ec26da598..c9c82d329 100644 --- a/content/influxdb/v1.8/administration/rebuild-tsi-index.md +++ b/content/influxdb/v1.8/administration/rebuild-tsi-index.md @@ -47,6 +47,6 @@ Restart InfluxDB by starting the `influxd` process. To rebuild the TSI index in an InfluxDB Enterprise cluster, perform the steps above on each data node in the cluster one after the other. After restarting the `influxd` process on a data node, allow the -[hinted handoff queue (HHQ)](/enterprise_influxdb/latest/concepts/clustering/#hinted-handoff) +[hinted handoff queue (HHQ)](/{{< latest "enterprise_influxdb" >}}/concepts/clustering/#hinted-handoff) to write all missed data to the updated node before moving on to the next node. {{% /note %}} diff --git a/content/influxdb/v1.8/administration/subscription-management.md b/content/influxdb/v1.8/administration/subscription-management.md index 89fe71964..60683c75d 100644 --- a/content/influxdb/v1.8/administration/subscription-management.md +++ b/content/influxdb/v1.8/administration/subscription-management.md @@ -99,7 +99,7 @@ CREATE SUBSCRIPTION "mysub" ON "mydb"."autogen" DESTINATIONS ANY 'http://host1.e Subscriptions can use HTTP, HTTPS, or UDP transport protocols. Which to use is determined by the protocol expected by the subscription endpoint. If creating a Kapacitor subscription, this is defined by the `subscription-protocol` -option in the `[[influxdb]]` section of your [`kapacitor.conf`](/kapacitor/latest/administration/subscription-management/#subscription-protocol). +option in the `[[influxdb]]` section of your [`kapacitor.conf`](/{{< latest "kapacitor" >}}/administration/subscription-management/#subscription-protocol). _**kapacitor.conf**_ diff --git a/content/influxdb/v1.8/administration/upgrading.md b/content/influxdb/v1.8/administration/upgrading.md index 5b6c90484..6255f5ae3 100644 --- a/content/influxdb/v1.8/administration/upgrading.md +++ b/content/influxdb/v1.8/administration/upgrading.md @@ -20,7 +20,7 @@ We recommend enabling Time Series Index (TSI) (step 3 of Upgrade to InfluxDB 1.8 ### Upgrade to InfluxDB Enterprise To upgrade from InfluxDB OSS to InfluxDB Enterprise, [contact InfluxData Sales](https://www.influxdata.com/contact-sales/) -and see [Migrate to InfluxDB Enterprise](/enterprise_influxdb/latest/guides/migration/). +and see [Migrate to InfluxDB Enterprise](/{{< latest "enterprise_influxdb" >}}/guides/migration/). {{% /note %}} ## Upgrade to InfluxDB 1.8.x diff --git a/content/influxdb/v1.8/concepts/crosswalk.md b/content/influxdb/v1.8/concepts/crosswalk.md index f1ddcc503..82e1049df 100644 --- a/content/influxdb/v1.8/concepts/crosswalk.md +++ b/content/influxdb/v1.8/concepts/crosswalk.md @@ -126,8 +126,8 @@ For those familiar with [InfluxQL](#influxql-and-sql), Flux is intended to addre 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). -Flux is the primary language for working with data in [InfluxDB 2.0 OSS](https://v2.docs.influxdata.com/v2.0/get-started) -(currently in _beta_) and [InfluxDB Cloud 2.0](https://v2.docs.influxdata.com/v2.0/cloud/get-started/), +Flux is the primary language for working with data in [InfluxDB 2.0 OSS](/influxdb/v2.0/get-started) +(currently in _beta_) and [InfluxDB Cloud 2.0](/influxdb/v2.0/cloud/get-started/), a generally available Platform as a Service (PaaS) available across multiple Cloud Service Providers. Using Flux with InfluxDB 1.8+ lets you get familiar with Flux concepts and syntax and ease the transition to InfluxDB 2.0. diff --git a/content/influxdb/v1.8/concepts/glossary.md b/content/influxdb/v1.8/concepts/glossary.md index 3aaebe5f9..794c748ec 100644 --- a/content/influxdb/v1.8/concepts/glossary.md +++ b/content/influxdb/v1.8/concepts/glossary.md @@ -292,7 +292,7 @@ Related entries: [database](/influxdb/v1.8/concepts/glossary/#database), [retent ## subscription -Subscriptions allow [Kapacitor](/kapacitor/latest/) to receive data from InfluxDB in a push model rather than the pull model based on querying data. +Subscriptions allow [Kapacitor](/{{< latest "kapacitor" >}}/) to receive data from InfluxDB in a push model rather than the pull model based on querying data. When Kapacitor is configured to work with InfluxDB, the subscription will automatically push every write for the subscribed database from InfluxDB to Kapacitor. Subscriptions can use TCP or UDP for transmitting the writes. @@ -348,7 +348,7 @@ Related entries: [aggregation](/influxdb/v1.8/concepts/glossary/#aggregation), [ ## TSM (Time Structured Merge tree) -The purpose-built data storage format for InfluxDB. TSM allows for greater compaction and higher write and read throughput than existing B+ or LSM tree implementations. See [Storage Engine](http://docs.influxdata.com/influxdb/v1.8/concepts/storage_engine/) for more. +The purpose-built data storage format for InfluxDB. TSM allows for greater compaction and higher write and read throughput than existing B+ or LSM tree implementations. See [Storage Engine](/influxdb/v1.8/concepts/storage_engine/) for more. ## user diff --git a/content/influxdb/v1.8/concepts/time-series-index.md b/content/influxdb/v1.8/concepts/time-series-index.md index f4dfa8ab4..b79b2c94c 100644 --- a/content/influxdb/v1.8/concepts/time-series-index.md +++ b/content/influxdb/v1.8/concepts/time-series-index.md @@ -8,7 +8,7 @@ menu: parent: Concepts --- -Find overview and background information on Time Series Index (TSI) in this topic. For detail, including how to enable and configure TSI, see [Time Series Index (TSI) details](https://docs.influxdata.com/influxdb/v1.8/concepts/tsi-details/). +Find overview and background information on Time Series Index (TSI) in this topic. For detail, including how to enable and configure TSI, see [Time Series Index (TSI) details](/influxdb/v1.8/concepts/tsi-details/). ## Overview diff --git a/content/influxdb/v1.8/concepts/tsi-details.md b/content/influxdb/v1.8/concepts/tsi-details.md index 6675e1ae6..891dc1ed0 100644 --- a/content/influxdb/v1.8/concepts/tsi-details.md +++ b/content/influxdb/v1.8/concepts/tsi-details.md @@ -28,13 +28,13 @@ index-version = "tsi1" ### InfluxDB Enterprise -- To convert your data nodes to support TSI, see [Upgrade InfluxDB Enterprise clusters](https://docs.influxdata.com/enterprise_influxdb/v1.8/administration/upgrading/). +- 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](https://docs.influxdata.com/enterprise_influxdb/v1.8/administration/configuration/#sidebar). +- For detail on configuration, see [Configure InfluxDB Enterprise clusters](/enterprise_influxdb/v1.8/administration/configuration/#sidebar). ### InfluxDB OSS -- For detail on configuration, see [Configuring InfluxDB OSS](https://docs.influxdata.com/influxdb/v1.8/administration/config/#sidebar). +- For detail on configuration, see [Configuring InfluxDB OSS](/influxdb/v1.8/administration/config/#sidebar). ## Tooling diff --git a/content/influxdb/v1.8/guides/downsample_and_retain.md b/content/influxdb/v1.8/guides/downsample_and_retain.md index 2998c4508..8b9cf70e3 100644 --- a/content/influxdb/v1.8/guides/downsample_and_retain.md +++ b/content/influxdb/v1.8/guides/downsample_and_retain.md @@ -11,7 +11,7 @@ aliases: InfluxDB can handle hundreds of thousands of data points per second. Working with that much data over a long period of time can create storage concerns. A natural solution is to downsample the data; keep the high precision raw data for only a limited time, and store the lower precision, summarized data longer. This guide describes how to automate the process of downsampling data and expiring old data using InfluxQL. To downsample and retain data using Flux and InfluxDB 2.0, -see [Process Data with InfluxDB tasks](https://v2.docs.influxdata.com/v2.0/process-data/). +see [Process Data with InfluxDB tasks](/influxdb/v2.0/process-data/). ### Definitions diff --git a/content/influxdb/v1.8/guides/query_data.md b/content/influxdb/v1.8/guides/query_data.md index a0a7a1696..d7e07eb04 100644 --- a/content/influxdb/v1.8/guides/query_data.md +++ b/content/influxdb/v1.8/guides/query_data.md @@ -37,7 +37,7 @@ $ curl -XPOST localhost:8086/api/v2/query -sS \ |> range(start:-5m) |> filter(fn:(r) => r._measurement == "cpu")' ``` -Flux returns [annotated CSV](https://v2.docs.influxdata.com/v2.0/reference/syntax/annotated-csv/): +Flux returns [annotated CSV](/influxdb/v2.0/reference/syntax/annotated-csv/): ``` {,result,table,_start,_stop,_time,_value,_field,_measurement,cpu,host @@ -51,7 +51,7 @@ The header row defines column labels for the table. The `cpu` [measurement](/inf ### Flux -Check out the [Get started with Flux](https://v2.docs.influxdata.com/v2.0/query-data/get-started/) to learn more about building queries with Flux. +Check out the [Get started with Flux](/influxdb/v2.0/query-data/get-started/) to learn more about building queries with Flux. For more information about querying data with the InfluxDB API using Flux, see the [API reference documentation](/influxdb/v1.8/tools/api/#influxdb-2-0-api-compatibility-endpoints). ## Query data with InfluxQL diff --git a/content/influxdb/v1.8/high_availability/_index.md b/content/influxdb/v1.8/high_availability/_index.md index 9835ecdac..01695bfd6 100644 --- a/content/influxdb/v1.8/high_availability/_index.md +++ b/content/influxdb/v1.8/high_availability/_index.md @@ -14,4 +14,4 @@ For high availability or horizontal scaling of InfluxDB, consider the InfluxData commercial clustered offering, [InfluxDB Enterprise](https://portal.influxdata.com/). -To learn more about high availability clustering, see [Clustering in InfluxDB Enterprise](/enterprise_influxdb/latest/concepts/clustering/). +To learn more about high availability clustering, see [Clustering in InfluxDB Enterprise](/{{< latest "enterprise_influxdb" >}}/concepts/clustering/). diff --git a/content/influxdb/v1.8/high_availability/clusters.md b/content/influxdb/v1.8/high_availability/clusters.md index 0ff855af7..81628f31d 100644 --- a/content/influxdb/v1.8/high_availability/clusters.md +++ b/content/influxdb/v1.8/high_availability/clusters.md @@ -15,6 +15,6 @@ menu: InfluxDB OSS does not support clustering. For high availability or horizontal scaling of InfluxDB, consider the InfluxData commercial clustered offering, -[InfluxDB Enterprise](/enterprise_influxdb/latest/). +[InfluxDB Enterprise](/{{< latest "enterprise_influxdb" >}}/). -To learn more about high availability clustering, see [Clustering in InfluxDB Enterprise](/enterprise_influxdb/latest/concepts/clustering/). +To learn more about high availability clustering, see [Clustering in InfluxDB Enterprise](/{{< latest "enterprise_influxdb" >}}/concepts/clustering/). diff --git a/content/influxdb/v1.8/query_language/continuous_queries.md b/content/influxdb/v1.8/query_language/continuous_queries.md index 7429f4136..f25b12ed6 100644 --- a/content/influxdb/v1.8/query_language/continuous_queries.md +++ b/content/influxdb/v1.8/query_language/continuous_queries.md @@ -982,4 +982,4 @@ Kapacitor, InfluxData's data processing engine, can do the same work as continuous queries in InfluxDB databases. To learn when to use Kapacitor instead of InfluxDB and how to perform the same CQ -functionality with a TICKscript, see [examples of continuous queries in Kapacitor](/kapacitor/latest/examples/continuous_queries/). +functionality with a TICKscript, see [examples of continuous queries in Kapacitor](/{{< latest "kapacitor" >}}/examples/continuous_queries/). diff --git a/content/influxdb/v1.8/query_language/sample-data.md b/content/influxdb/v1.8/query_language/sample-data.md index a2e908f2c..c5621b4d6 100644 --- a/content/influxdb/v1.8/query_language/sample-data.md +++ b/content/influxdb/v1.8/query_language/sample-data.md @@ -33,7 +33,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/latest/tools/shell/#influx-options) specifies the format/precision of any returned timestamps. +* The [`-precision` argument](/{{< latest "influxdb" "v1" >}}/tools/shell/#influx-options) 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 b7b95879a..bb10e85cd 100644 --- a/content/influxdb/v1.8/query_language/spec.md +++ b/content/influxdb/v1.8/query_language/spec.md @@ -422,7 +422,7 @@ CREATE RETENTION POLICY "10m.events" ON "somedb" DURATION 60m REPLICATION 2 SHAR ### CREATE SUBSCRIPTION -Subscriptions tell InfluxDB to send all the data it receives to [Kapacitor](/kapacitor/latest/introduction/). +Subscriptions tell InfluxDB to send all the data it receives to [Kapacitor](/{{< latest "kapacitor" >}}/introduction/). ``` create_subscription_stmt = "CREATE SUBSCRIPTION" subscription_name "ON" db_name "." retention_policy "DESTINATIONS" ("ANY"|"ALL") host { "," host} . diff --git a/content/influxdb/v1.8/supported_protocols/collectd.md b/content/influxdb/v1.8/supported_protocols/collectd.md index 44e8eac6d..859d8422d 100644 --- a/content/influxdb/v1.8/supported_protocols/collectd.md +++ b/content/influxdb/v1.8/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/latest/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.](/{{< latest "influxdb" "v1" >}}/supported_protocols/udp/#a-note-on-udpip-os-buffer-sizes) ## Configuration diff --git a/content/influxdb/v1.8/tools/_index.md b/content/influxdb/v1.8/tools/_index.md index 756b6833d..f8745d1aa 100644 --- a/content/influxdb/v1.8/tools/_index.md +++ b/content/influxdb/v1.8/tools/_index.md @@ -34,7 +34,7 @@ Use the InfluxDB inch tool to test InfluxDB performance. Adjust metrics such as ## Graphs and dashboards -Use [Chronograf](/chronograf/latest/) or [Grafana](https://grafana.com/docs/grafana/latest/features/datasources/influxdb/) dashboards to visualize your time series data. +Use [Chronograf](/{{< latest "chronograf" >}}/) or [Grafana](https://grafana.com/docs/grafana/latest/features/datasources/influxdb/) dashboards to visualize your time series data. > **Tip:** Use template variables in your dashboards to filter meta query results by a specified period of time (see example below). @@ -56,4 +56,4 @@ WHERE time > now() - 1h GROUP BY time(1h), host, team, status, location END; SHOW TAG VALUES FROM "your.system"."host_info" WITH KEY = “host” ``` -> **Note:** In Chronograf, you can also filter meta query results for a specified time range by [creating a `custom meta query` template variable](/chronograf/latest/guides/dashboard-template-variables/#create-custom-template-variables) and adding a time range filter. +> **Note:** In Chronograf, you can also filter meta query results for a specified time range by [creating a `custom meta query` template variable](/{{< latest "chronograf" >}}/guides/dashboard-template-variables/#create-custom-template-variables) and adding a time range filter. diff --git a/content/influxdb/v1.8/tools/api.md b/content/influxdb/v1.8/tools/api.md index 5bf737296..a3c11f553 100644 --- a/content/influxdb/v1.8/tools/api.md +++ b/content/influxdb/v1.8/tools/api.md @@ -46,7 +46,7 @@ The following forward compatible APIs are available: ### `/api/v2/query/` HTTP endpoint The `/api/v2/query` endpoint accepts `POST` HTTP requests. -Use this endpoint to query data using [Flux](/flux/latest/) and [InfluxDB 2.0 client libraries](https://v2.docs.influxdata.com/v2.0/reference/api/client-libraries/). +Use this endpoint to query data using [Flux](/flux/latest/) and [InfluxDB 2.0 client libraries](/influxdb/v2.0/reference/api/client-libraries/). Flux is the primary language for working with data in InfluxDB 2.0. **Include the following HTTP headers:** @@ -88,12 +88,12 @@ curl -XPOST localhost:8086/api/v2/query -sS \ ### `/api/v2/write/` HTTP endpoint The `/api/v2/write` endpoint accepts `POST` HTTP requests. -Use this endpoint to write to an InfluxDB 1.8.0+ database using [InfluxDB 2.0 client libraries](https://v2.docs.influxdata.com/v2.0/reference/api/client-libraries/). +Use this endpoint to write to an InfluxDB 1.8.0+ database using [InfluxDB 2.0 client libraries](/influxdb/v2.0/reference/api/client-libraries/). Both InfluxDB 1.x and 2.0 APIs support the same line protocol format for raw time series data. For the purposes of writing data, the APIs differ only in the URL parameters and request headers. -InfluxDB 2.0 uses [organizations](https://v2.docs.influxdata.com/v2.0/reference/glossary/#organization) -and [buckets](https://v2.docs.influxdata.com/v2.0/reference/glossary/#bucket) +InfluxDB 2.0 uses [organizations](/influxdb/v2.0/reference/glossary/#organization) +and [buckets](/influxdb/v2.0/reference/glossary/#bucket) instead of databases and retention policies. The `/api/v2/write` endpoint maps the supplied version 1.8 database and retention policy to a bucket. @@ -110,7 +110,7 @@ The `/api/v2/write` endpoint maps the supplied version 1.8 database and retentio **Include the following HTTP header:** -- `Authorization`: In InfluxDB 2.0 uses [API Tokens](https://v2.docs.influxdata.com/v2.0/security/tokens/) +- `Authorization`: In InfluxDB 2.0 uses [API Tokens](/influxdb/v2.0/security/tokens/) to access the platform and all its capabilities. InfluxDB v1.x uses a username and password combination when accessing the HTTP APIs. Use the Token schema to provide your InfluxDB 1.x username and password separated by a colon (`:`). @@ -940,7 +940,7 @@ Errors are returned in JSON. | 400 Bad Request | Unacceptable request. Can occur with an InfluxDB line protocol syntax error or if a user attempts to write values to a field that previously accepted a different value type. The returned JSON offers further information. | | 401 Unauthorized | Unacceptable request. Can occur with invalid authentication credentials. | | 404 Not Found | Unacceptable request. Can occur if a user attempts to write to a database that does not exist. The returned JSON offers further information. | -| 413 Request Entity Too Large | Unaccetable request. It will occur if the payload of the POST request is bigger than the maximum size allowed. See [`max-body-size`](https://docs.influxdata.com/influxdb/latest/administration/config/#max-body-size-25000000) parameter for more details. +| 413 Request Entity Too Large | Unaccetable request. It will occur if the payload of the POST request is bigger than the maximum size allowed. See [`max-body-size`](/{{< latest "influxdb" "v1" >}}/administration/config/#max-body-size-25000000) parameter for more details. | 500 Internal Server Error | The system is overloaded or significantly impaired. Can occur if a user attempts to write to a retention policy that does not exist. The returned JSON offers further information. | #### Examples diff --git a/content/influxdb/v1.8/tools/influxd/_index.md b/content/influxdb/v1.8/tools/influxd/_index.md index 45c70245c..e7bcc2722 100644 --- a/content/influxdb/v1.8/tools/influxd/_index.md +++ b/content/influxdb/v1.8/tools/influxd/_index.md @@ -19,9 +19,9 @@ influxd [[command] [arguments]] ## Commands | Command | Description | |-------------------------------------------------------|----------------------------------------------------------| -| [backup](/influxdb/latest/tools/influxd/backup) | Download a snapshot of a data node and saves it to disk. | -| [config](/influxdb/latest/tools/influxd/config) | Display the default configuration. | +| [backup](/{{< latest "influxdb" "v1" >}}/tools/influxd/backup) | Download a snapshot of a data node and saves it to disk. | +| [config](/{{< latest "influxdb" "v1" >}}/tools/influxd/config) | Display the default configuration. | | help | Display the help message. | -| [restore](/influxdb/latest/tools/influxd/restore) | Use a snapshot of a data node to rebuild a cluster. | -| [run](/influxdb/latest/tools/influxd/run) | Run node with existing configuration. | -| [version](/influxdb/latest/tools/influxd/version) | Display the InfluxDB version. | +| [restore](/{{< latest "influxdb" "v1" >}}/tools/influxd/restore) | Use a snapshot of a data node to rebuild a cluster. | +| [run](/{{< latest "influxdb" "v1" >}}/tools/influxd/run) | Run node with existing configuration. | +| [version](/{{< latest "influxdb" "v1" >}}/tools/influxd/version) | Display the InfluxDB version. | diff --git a/content/influxdb/v1.8/troubleshooting/frequently-asked-questions.md b/content/influxdb/v1.8/troubleshooting/frequently-asked-questions.md index 9b801785a..5427678da 100644 --- a/content/influxdb/v1.8/troubleshooting/frequently-asked-questions.md +++ b/content/influxdb/v1.8/troubleshooting/frequently-asked-questions.md @@ -271,7 +271,7 @@ Note that you will need to fully qualify the measurement to query data in the no ## How do I cancel a long-running query? -You can cancel a long-running interactive query from the CLI using `Ctrl+C`. To stop other long-running query that you see when using the [`SHOW QUERIES`](https://docs.influxdata.com/influxdb/v1.3/query_language/spec/#show-queries) command, +You can cancel a long-running interactive query from the CLI using `Ctrl+C`. To stop other long-running query that you see when using the [`SHOW QUERIES`](/influxdb/v1.3/query_language/spec/#show-queries) command, you can use the [`KILL QUERY`](/influxdb/v1.8/troubleshooting/query_management/#stop-currently-running-queries-with-kill-query) command to stop it. ## Why can't I query Boolean field values? diff --git a/content/influxdb/v2.0/_index.md b/content/influxdb/v2.0/_index.md index 70e59f78c..7dee8c207 100644 --- a/content/influxdb/v2.0/_index.md +++ b/content/influxdb/v2.0/_index.md @@ -1,4 +1,5 @@ --- +title: InfluxDB v2.0 documentation description: > InfluxDB is an open source time series database designed to handle high write and query loads. Learn how to use and leverage InfluxDB in use cases such as monitoring metrics, IoT data, and events. diff --git a/content/influxdb/v2.0/example.md b/content/influxdb/v2.0/example.md index 2d2a02f4e..e899b5d76 100644 --- a/content/influxdb/v2.0/example.md +++ b/content/influxdb/v2.0/example.md @@ -61,7 +61,7 @@ WHERE time > now() - 15m ### h3 This is a header3 This is a paragraph. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc rutrum, metus id scelerisque euismod, erat ante suscipit nibh, ac congue enim risus id est. Etiam tristique nisi et tristique auctor. Morbi eu bibendum erat. Sed ullamcorper, dui id lobortis efficitur, mauris odio pharetra neque, vel tempor odio dolor blandit justo. -![Test image](http://docs.influxdata.com/img/chronograf/1-6-alerts-conditions.png) +![Test image](/img/chronograf/1-6-alerts-conditions.png) {{< img-hd src="/img/test-image-2.png" alt="Test Image" />}} diff --git a/content/influxdb/v2.0/query-data/influxql.md b/content/influxdb/v2.0/query-data/influxql.md index 254e7728b..5d15df203 100644 --- a/content/influxdb/v2.0/query-data/influxql.md +++ b/content/influxdb/v2.0/query-data/influxql.md @@ -45,8 +45,8 @@ By default, the `/query` compatibility endpoint returns results in **JSON**. To return results as **CSV**, include the `Accept: application/csv` header. ## Database and retention policy mapping -InfluxDB 2.0 combines the 1.x concept of [databases](https://docs.influxdata.com/influxdb/v1.8/concepts/glossary/#database) -and [retention policies](https://docs.influxdata.com/influxdb/v1.8/concepts/glossary/#retention-policy-rp) +InfluxDB 2.0 combines the 1.x concept of [databases](/influxdb/v1.8/concepts/glossary/#database) +and [retention policies](/influxdb/v1.8/concepts/glossary/#retention-policy-rp) into [buckets](/v2.0/reference/glossary/#bucket). To support InfluxDB 1.x query and write patterns in InfluxDB 2.0, databases and retention policies are mapped to buckets using the **database and retention policy (DBRP) mapping service**. diff --git a/content/influxdb/v2.0/reference/api/influxdb-1x/dbrp.md b/content/influxdb/v2.0/reference/api/influxdb-1x/dbrp.md index a2ff28ad8..86087d002 100644 --- a/content/influxdb/v2.0/reference/api/influxdb-1x/dbrp.md +++ b/content/influxdb/v2.0/reference/api/influxdb-1x/dbrp.md @@ -17,8 +17,8 @@ related: - /influxdb/v2.0/api/#tag/DBRPs, InfluxDB 2.0 API /dbrps endpoint --- -The InfluxDB 1.x data model includes [databases](https://docs.influxdata.com/influxdb/v1.8/concepts/glossary/#database) -and [retention policies](https://docs.influxdata.com/influxdb/v1.8/concepts/glossary/#retention-policy-rp). +The InfluxDB 1.x data model includes [databases](/influxdb/v1.8/concepts/glossary/#database) +and [retention policies](/influxdb/v1.8/concepts/glossary/#retention-policy-rp). InfluxDB 2.0 replaces both with [buckets](/v2.0/reference/glossary/#bucket). To support InfluxDB 1.x query and write patterns in InfluxDB 2.0, databases and retention policies are mapped to buckets using the **database and retention policy (DBRP) mapping service**. diff --git a/content/influxdb/v2.0/reference/config-options.md b/content/influxdb/v2.0/reference/config-options.md index fc722effa..b6ac32419 100644 --- a/content/influxdb/v2.0/reference/config-options.md +++ b/content/influxdb/v2.0/reference/config-options.md @@ -1056,7 +1056,7 @@ store = "bolt" Path to TLS certificate file. Requires the [`tls-key`](#tls-key) to be set. -_For more information, see [Enable TLS encryption](https://v2.docs.influxdata.com/v2.0/security/enable-tls/)._ +_For more information, see [Enable TLS encryption](/influxdb/v2.0/security/enable-tls/)._ | influxd flag | Environment variable | Configuration key | |:------------ |:-------------------- |:----------------- | @@ -1104,7 +1104,7 @@ tls-cert = "/path/to/influxdb.crt" Path to TLS key file. Requires the [`tls-cert`](#tls-cert) to be set. -_For more information, see [Enable TLS encryption](https://v2.docs.influxdata.com/v2.0/security/enable-tls/)._ +_For more information, see [Enable TLS encryption](/influxdb/v2.0/security/enable-tls/)._ | influxd flag | Environment variable | Configuration key | |:------------ |:-------------------- |:----------------- | diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/inputs/from.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/inputs/from.md index 17acb8c71..ac15d5bd1 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/inputs/from.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/inputs/from.md @@ -10,7 +10,7 @@ menu: parent: built-in-inputs weight: 401 related: - - https://docs.influxdata.com/influxdb/latest/query_language/data_exploration/#from-clause, InfluxQL - FROM + - /{{< latest "influxdb" "v1" >}}/query_language/data_exploration/#from-clause, InfluxQL - FROM --- The `from()` function retrieves data from an InfluxDB data source. diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/outputs/to.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/outputs/to.md index 73b988668..b9282e9c8 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/outputs/to.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/outputs/to.md @@ -10,7 +10,7 @@ menu: parent: built-in-outputs weight: 401 related: - - https://docs.influxdata.com/influxdb/latest/query_language/data_exploration/#the-into-clause, InfluxQL – SELECT INTO + - /{{< latest "influxdb" "v1" >}}/query_language/data_exploration/#the-into-clause, InfluxQL – SELECT INTO --- The `to()` function writes data to an **InfluxDB v2.0** bucket. diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/outputs/yield.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/outputs/yield.md index 864ba3fcf..829db7db7 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/outputs/yield.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/outputs/yield.md @@ -10,7 +10,7 @@ menu: parent: built-in-outputs weight: 401 related: - - https://docs.influxdata.com/influxdb/latest/query_language/data_exploration/#the-basic-select-statement, InfluxQL – SELECT AS + - /{{< latest "influxdb" "v1" >}}/query_language/data_exploration/#the-basic-select-statement, InfluxQL – SELECT AS --- The `yield()` function indicates the input tables received should be delivered as a result of the query. diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/aggregatewindow.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/aggregatewindow.md index 3fbf280d6..680acd9b6 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/aggregatewindow.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/aggregatewindow.md @@ -11,8 +11,8 @@ menu: weight: 501 related: - /influxdb/v2.0/query-data/flux/window-aggregate/ - - https://docs.influxdata.com/influxdb/latest/query_language/functions/#aggregations, InfluxQL – Aggregate functions - - https://docs.influxdata.com/influxdb/latest/query_language/explore-data/#the-group-by-clause, InfluxQL – GROUP BY time() + - /{{< latest "influxdb" "v1" >}}/query_language/functions/#aggregations, InfluxQL – Aggregate functions + - /{{< latest "influxdb" "v1" >}}/query_language/explore-data/#the-group-by-clause, InfluxQL – GROUP BY time() --- The `aggregateWindow()` function applies an aggregate or selector function diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/count.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/count.md index e42b1c6c0..eeb91e4fc 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/count.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/count.md @@ -10,7 +10,7 @@ menu: parent: built-in-aggregates weight: 501 related: - - https://docs.influxdata.com/influxdb/latest/query_language/functions/#count, InfluxQL – COUNT() + - /{{< latest "influxdb" "v1" >}}/query_language/functions/#count, InfluxQL – COUNT() --- The `count()` function outputs the number of records in a column. diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/integral.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/integral.md index 03563a1aa..4d73b1f3e 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/integral.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/integral.md @@ -10,7 +10,7 @@ menu: parent: built-in-aggregates weight: 501 related: - - https://docs.influxdata.com/influxdb/latest/query_language/functions/#integral, InfluxQL – INTEGRAL() + - /{{< latest "influxdb" "v1" >}}/query_language/functions/#integral, InfluxQL – INTEGRAL() --- The `integral()` function computes the area under the curve per [`unit`](#unit) of time of subsequent non-null records. diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/mean.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/mean.md index 1e9ccd634..f7310e263 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/mean.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/mean.md @@ -10,7 +10,7 @@ menu: parent: built-in-aggregates weight: 501 related: - - https://docs.influxdata.com/influxdb/latest/query_language/functions/#mean, InfluxQL – MEAN() + - /{{< latest "influxdb" "v1" >}}/query_language/functions/#mean, InfluxQL – MEAN() --- The `mean()` function computes the mean or average of non-null records in the input table. diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/median.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/median.md index 1248e6e37..de7837567 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/median.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/median.md @@ -13,7 +13,7 @@ menu: weight: 501 related: - /influxdb/v2.0/query-data/flux/median/ - - https://docs.influxdata.com/influxdb/latest/query_language/functions/#median, InfluxQL – MEDIAN() + - /{{< latest "influxdb" "v1" >}}/query_language/functions/#median, InfluxQL – MEDIAN() --- The `median()` function is a special application of the [`quantile()` function](/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/quantile) diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/mode.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/mode.md index 2cc471dfa..e6a8d2bf7 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/mode.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/mode.md @@ -11,7 +11,7 @@ menu: parent: built-in-aggregates weight: 501 related: - - https://docs.influxdata.com/influxdb/latest/query_language/functions/#mode, InfluxQL – MODE() + - /{{< latest "influxdb" "v1" >}}/query_language/functions/#mode, InfluxQL – MODE() --- The `mode()` function computes the mode or value that occurs most often in a diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/quantile.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/quantile.md index f3abf5e43..08e734abe 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/quantile.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/quantile.md @@ -12,7 +12,7 @@ menu: weight: 501 related: - /influxdb/v2.0/query-data/flux/percentile-quantile/ - - https://docs.influxdata.com/influxdb/latest/query_language/functions/#percentile, InfluxQL – PERCENTILE() + - /{{< latest "influxdb" "v1" >}}/query_language/functions/#percentile, InfluxQL – PERCENTILE() --- The `quantile()` function returns records from an input table with `_value`s that fall within diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/spread.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/spread.md index d9c3aba44..e07fbf0b6 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/spread.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/spread.md @@ -10,7 +10,7 @@ menu: parent: built-in-aggregates weight: 501 related: - - https://docs.influxdata.com/influxdb/latest/query_language/functions/#spread, InfluxQL – SPREAD() + - /{{< latest "influxdb" "v1" >}}/query_language/functions/#spread, InfluxQL – SPREAD() --- The `spread()` function outputs the difference between the minimum and maximum values in a specified column. diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/stddev.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/stddev.md index 1869ad038..69fc50237 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/stddev.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/stddev.md @@ -10,7 +10,7 @@ menu: parent: built-in-aggregates weight: 501 related: - - https://docs.influxdata.com/influxdb/latest/query_language/functions/#stddev, InfluxQL – STDDEV() + - /{{< latest "influxdb" "v1" >}}/query_language/functions/#stddev, InfluxQL – STDDEV() --- The `stddev()` function computes the standard deviation of non-null records in a specified column. diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/sum.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/sum.md index 7d2550424..ac40fe0f8 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/sum.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/aggregates/sum.md @@ -10,7 +10,7 @@ menu: parent: built-in-aggregates weight: 501 related: - - https://docs.influxdata.com/influxdb/latest/query_language/functions/#sum, InfluxQL – SUM() + - /{{< latest "influxdb" "v1" >}}/query_language/functions/#sum, InfluxQL – SUM() --- The `sum()` function computes the sum of non-null records in a specified column. diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/chandemomentumoscillator.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/chandemomentumoscillator.md index 7d3f5db9b..c630b77fe 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/chandemomentumoscillator.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/chandemomentumoscillator.md @@ -12,7 +12,7 @@ menu: parent: built-in-transformations weight: 402 related: - - https://docs.influxdata.com/influxdb/latest/query_language/functions/#triple-exponential-moving-average, InfluxQL CHANDE_MOMENTUM_OSCILLATOR() + - /{{< latest "influxdb" "v1" >}}/query_language/functions/#triple-exponential-moving-average, InfluxQL CHANDE_MOMENTUM_OSCILLATOR() --- The `chandeMomentumOscillator()` function applies the technical momentum indicator diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/columns.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/columns.md index bfe583293..6f2ff1ee1 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/columns.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/columns.md @@ -13,10 +13,10 @@ menu: parent: built-in-transformations weight: 402 related: - - https://docs.influxdata.com/influxdb/latest/query_language/schema_exploration/#show-measurements, InfluxQL – SHOW MEASUREMENTS - - https://docs.influxdata.com/influxdb/latest/query_language/schema_exploration/#show-field-keys, InfluxQL – SHOW FIELD KEYS - - https://docs.influxdata.com/influxdb/latest/query_language/schema_exploration/#show-tag-keys, InfluxQL – SHOW TAG KEYS - - https://docs.influxdata.com/influxdb/latest/query_language/schema_exploration/#show-tag-keys, InfluxQL – SHOW SERIES + - /{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-measurements, InfluxQL – SHOW MEASUREMENTS + - /{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-field-keys, InfluxQL – SHOW FIELD KEYS + - /{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-tag-keys, InfluxQL – SHOW TAG KEYS + - /{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-tag-keys, InfluxQL – SHOW SERIES --- The `columns()` function lists the column labels of input tables. diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/cumulativesum.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/cumulativesum.md index bd0b818ed..e99fe71ac 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/cumulativesum.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/cumulativesum.md @@ -11,7 +11,7 @@ menu: weight: 402 related: - /influxdb/v2.0/query-data/flux/cumulativesum/ - - https://docs.influxdata.com/influxdb/latest/query_language/functions/#cumulative-sum, InfluxQL – CUMULATIVE_SUM() + - /{{< latest "influxdb" "v1" >}}/query_language/functions/#cumulative-sum, InfluxQL – CUMULATIVE_SUM() --- The `cumulativeSum()` function computes a running sum for non-null records in the table. diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/derivative.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/derivative.md index b83aae938..94b20527f 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/derivative.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/derivative.md @@ -13,7 +13,7 @@ aliases: - /v2.0/reference/flux/stdlib/built-in/transformations/aggregates/derivative related: - /influxdb/v2.0/query-data/flux/rate/ - - https://docs.influxdata.com/influxdb/latest/query_language/functions/#derivative, InfluxQL – DERIVATIVE() + - /{{< latest "influxdb" "v1" >}}/query_language/functions/#derivative, InfluxQL – DERIVATIVE() --- The `derivative()` function computes the rate of change per [`unit`](#unit) of time between subsequent non-null records. diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/difference.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/difference.md index 35d4216cf..0dac079a5 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/difference.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/difference.md @@ -12,7 +12,7 @@ weight: 402 aliases: - /v2.0/reference/flux/stdlib/built-in/transformations/aggregates/difference related: - - https://docs.influxdata.com/influxdb/latest/query_language/functions/#difference, InfluxQL – DIFFERENCE() + - /{{< latest "influxdb" "v1" >}}/query_language/functions/#difference, InfluxQL – DIFFERENCE() --- The `difference()` function computes the difference between subsequent records. diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/doubleema.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/doubleema.md index 730de379d..05e250e3a 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/doubleema.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/doubleema.md @@ -17,7 +17,7 @@ related: - /v2.0/reference/flux/stdlib/built-in/transformations/tripleema/ - /v2.0/reference/flux/stdlib/built-in/transformations/timedmovingaverage/ - /v2.0/reference/flux/stdlib/built-in/transformations/exponentialmovingaverage/ - - https://docs.influxdata.com/influxdb/latest/query_language/functions/#double-exponential-moving-average, InfluxQL DOUBLE_EXPONENTIAL_MOVING_AVERAGE() + - /{{< latest "influxdb" "v1" >}}/query_language/functions/#double-exponential-moving-average, InfluxQL DOUBLE_EXPONENTIAL_MOVING_AVERAGE() --- The `doubleEMA()` function calculates the exponential moving average of values in diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/exponentialmovingaverage.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/exponentialmovingaverage.md index 66d6db567..8a7a02b79 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/exponentialmovingaverage.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/exponentialmovingaverage.md @@ -16,7 +16,7 @@ related: - /v2.0/reference/flux/stdlib/built-in/transformations/timedmovingaverage/ - /v2.0/reference/flux/stdlib/built-in/transformations/doubleema/ - /v2.0/reference/flux/stdlib/built-in/transformations/tripleema/ - - https://docs.influxdata.com/influxdb/latest/query_language/functions/#exponential-moving-average, InfluxQL EXPONENTIAL_MOVING_AVERAGE() + - /{{< latest "influxdb" "v1" >}}/query_language/functions/#exponential-moving-average, InfluxQL EXPONENTIAL_MOVING_AVERAGE() --- The `exponentialMovingAverage()` function calculates the exponential moving average of values diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/fill.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/fill.md index 471b590c0..f61f8fbe0 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/fill.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/fill.md @@ -11,7 +11,7 @@ menu: weight: 402 related: - /influxdb/v2.0/query-data/flux/fill/ - - https://docs.influxdata.com/influxdb/latest/query_language/data_exploration/#group-by-time-intervals-and-fill, InfluxQL – FILL + - /{{< latest "influxdb" "v1" >}}/query_language/data_exploration/#group-by-time-intervals-and-fill, InfluxQL – FILL --- The `fill()` function replaces all null values in an input stream with a non-null value. diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/filter.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/filter.md index ef1eaef58..86c0417c9 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/filter.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/filter.md @@ -14,7 +14,7 @@ related: - /influxdb/v2.0/query-data/flux/query-fields/ - /influxdb/v2.0/query-data/flux/conditional-logic/ - /influxdb/v2.0/query-data/flux/exists/ - - https://docs.influxdata.com/influxdb/latest/query_language/data_exploration/#the-basic-select-statement, InfluxQL – SELECT + - /{{< latest "influxdb" "v1" >}}/query_language/data_exploration/#the-basic-select-statement, InfluxQL – SELECT --- The `filter()` function filters data based on conditions defined in a predicate function ([`fn`](#fn)). diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/group.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/group.md index 63c75ce26..e19e495db 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/group.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/group.md @@ -11,7 +11,7 @@ menu: weight: 402 related: - /influxdb/v2.0/query-data/flux/group-data/ - - https://docs.influxdata.com/influxdb/latest/query_language/data_exploration/#the-group-by-clause, InfluxQL – GROUP BY + - /{{< latest "influxdb" "v1" >}}/query_language/data_exploration/#the-group-by-clause, InfluxQL – GROUP BY --- The `group()` function groups records based on their values for specific columns. diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/holtwinters.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/holtwinters.md index d143652c4..8dcf763f1 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/holtwinters.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/holtwinters.md @@ -12,7 +12,7 @@ menu: parent: built-in-transformations weight: 402 related: - - https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters, InfluxQL HOLT_WINTERS() + - /{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters, InfluxQL HOLT_WINTERS() --- The `holtWinters()` function applies the Holt-Winters forecasting method to input tables. diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/kaufmansama.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/kaufmansama.md index b6f960188..513b9217b 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/kaufmansama.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/kaufmansama.md @@ -13,7 +13,7 @@ menu: weight: 402 related: - /v2.0/reference/flux/stdlib/built-in/transformations/kaufmanser/ - - https://docs.influxdata.com/influxdb/latest/query_language/functions/#kaufmans-adaptive-moving-average, InfluxQL KAUFMANS_ADAPTIVE_MOVING_AVERAGE() + - /{{< latest "influxdb" "v1" >}}/query_language/functions/#kaufmans-adaptive-moving-average, InfluxQL KAUFMANS_ADAPTIVE_MOVING_AVERAGE() --- The `kaufmansAMA()` function calculates the Kaufman's Adaptive Moving Average (KAMA) diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/kaufmanser.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/kaufmanser.md index b7dc331f5..a0018ad0c 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/kaufmanser.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/kaufmanser.md @@ -13,7 +13,7 @@ menu: weight: 402 related: - /v2.0/reference/flux/stdlib/built-in/transformations/kaufmansama/ - - https://docs.influxdata.com/influxdb/latest/query_language/functions/#kaufmans-efficiency-ratio, InfluxQL KAUFMANS_EFFICIENCY_RATIO() + - /{{< latest "influxdb" "v1" >}}/query_language/functions/#kaufmans-efficiency-ratio, InfluxQL KAUFMANS_EFFICIENCY_RATIO() --- The `kaufmansER()` function calculates the Kaufman's Efficiency Ratio (KER) using diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/keys.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/keys.md index 1c0a67ebc..4d3cd3e1f 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/keys.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/keys.md @@ -13,10 +13,10 @@ menu: parent: built-in-transformations weight: 402 related: - - https://docs.influxdata.com/influxdb/latest/query_language/schema_exploration/#show-measurements, InfluxQL – SHOW MEASUREMENTS - - https://docs.influxdata.com/influxdb/latest/query_language/schema_exploration/#show-field-keys, InfluxQL – SHOW FIELD KEYS - - https://docs.influxdata.com/influxdb/latest/query_language/schema_exploration/#show-tag-keys, InfluxQL – SHOW TAG KEYS - - https://docs.influxdata.com/influxdb/latest/query_language/schema_exploration/#show-tag-keys, InfluxQL – SHOW SERIES + - /{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-measurements, InfluxQL – SHOW MEASUREMENTS + - /{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-field-keys, InfluxQL – SHOW FIELD KEYS + - /{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-tag-keys, InfluxQL – SHOW TAG KEYS + - /{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-tag-keys, InfluxQL – SHOW SERIES --- The `keys()` function outputs the group key of input tables. diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/keyvalues.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/keyvalues.md index 23604cbf6..9dfa826c9 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/keyvalues.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/keyvalues.md @@ -10,11 +10,11 @@ menu: parent: built-in-transformations weight: 402 related: - - https://docs.influxdata.com/influxdb/latest/query_language/schema_exploration/#show-measurements, InfluxQL – SHOW MEASUREMENTS - - https://docs.influxdata.com/influxdb/latest/query_language/schema_exploration/#show-field-keys, InfluxQL – SHOW FIELD KEYS - - https://docs.influxdata.com/influxdb/latest/query_language/schema_exploration/#show-tag-keys, InfluxQL – SHOW TAG KEYS - - https://docs.influxdata.com/influxdb/latest/query_language/schema_exploration/#show-tag-values, InfluxQL – SHOW TAG VALUES - - https://docs.influxdata.com/influxdb/latest/query_language/schema_exploration/#show-serie, InfluxQL – SHOW SERIES + - /{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-measurements, InfluxQL – SHOW MEASUREMENTS + - /{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-field-keys, InfluxQL – SHOW FIELD KEYS + - /{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-tag-keys, InfluxQL – SHOW TAG KEYS + - /{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-tag-values, InfluxQL – SHOW TAG VALUES + - /{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-serie, InfluxQL – SHOW SERIES --- The `keyValues()` function returns a table with the input table's group key plus two columns, diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/limit.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/limit.md index f67ce8a81..ea41326f5 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/limit.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/limit.md @@ -12,7 +12,7 @@ weight: 402 related: - /influxdb/v2.0/query-data/flux/sort-limit/ - /v2.0/reference/flux/stdlib/built-in/transformations/tail/ - - https://docs.influxdata.com/influxdb/latest/query_language/data_exploration/#the-limit-and-slimit-clauses, InfluxQL LIMIT + - /{{< latest "influxdb" "v1" >}}/query_language/data_exploration/#the-limit-and-slimit-clauses, InfluxQL LIMIT --- The `limit()` function limits each output table to the first [`n`](#n) records. diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/movingaverage.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/movingaverage.md index 7ef9539f3..6b078f0e7 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/movingaverage.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/movingaverage.md @@ -16,7 +16,7 @@ related: - /v2.0/reference/flux/stdlib/built-in/transformations/exponentialmovingaverage/ - /v2.0/reference/flux/stdlib/built-in/transformations/doubleema/ - /v2.0/reference/flux/stdlib/built-in/transformations/tripleema/ - - https://docs.influxdata.com/influxdb/latest/query_language/functions/#moving-average, InfluxQL MOVING_AVERAGE() + - /{{< latest "influxdb" "v1" >}}/query_language/functions/#moving-average, InfluxQL MOVING_AVERAGE() --- The `movingAverage()` function calculates the mean of values in the `_values` column diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/range.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/range.md index 1a24eb3b3..51ac8c7c0 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/range.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/range.md @@ -10,7 +10,7 @@ menu: parent: built-in-transformations weight: 402 related: - - https://docs.influxdata.com/influxdb/latest/query_language/data_exploration/#the-where-clause, InfluxQL – WHERE + - /{{< latest "influxdb" "v1" >}}/query_language/data_exploration/#the-where-clause, InfluxQL – WHERE --- The `range()` function filters records based on time bounds. diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/relativestrengthindex.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/relativestrengthindex.md index 2040f14cd..36109aeff 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/relativestrengthindex.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/relativestrengthindex.md @@ -15,7 +15,7 @@ related: - /v2.0/reference/flux/stdlib/built-in/transformations/movingaverage/ - /v2.0/reference/flux/stdlib/built-in/transformations/timedmovingaverage/ - /v2.0/reference/flux/stdlib/built-in/transformations/exponentialmovingaverage/ - - https://docs.influxdata.com/influxdb/latest/query_language/functions/#relative-strength-index, InfluxQL RELATIVE_STRENGTH_INDEX() + - /{{< latest "influxdb" "v1" >}}/query_language/functions/#relative-strength-index, InfluxQL RELATIVE_STRENGTH_INDEX() --- The `relativeStrengthIndex()` function measures the relative speed and change of diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/selectors/bottom.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/selectors/bottom.md index 60c849c41..dba2faf54 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/selectors/bottom.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/selectors/bottom.md @@ -10,7 +10,7 @@ menu: parent: built-in-selectors weight: 501 related: - - https://docs.influxdata.com/influxdb/latest/query_language/functions/#bottom, InfluxQL – BOTTOM() + - /{{< latest "influxdb" "v1" >}}/query_language/functions/#bottom, InfluxQL – BOTTOM() --- The `bottom()` function sorts a table by columns and keeps only the bottom `n` records. diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/selectors/distinct.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/selectors/distinct.md index 2cc96b6b7..92b7a1c46 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/selectors/distinct.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/selectors/distinct.md @@ -10,7 +10,7 @@ menu: parent: built-in-selectors weight: 501 related: - - https://docs.influxdata.com/influxdb/latest/query_language/functions/#distinct, InfluxQL – DISTINCT() + - /{{< latest "influxdb" "v1" >}}/query_language/functions/#distinct, InfluxQL – DISTINCT() --- The `distinct()` function returns the unique values for a given column. diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/selectors/first.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/selectors/first.md index 96070251a..27356a88a 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/selectors/first.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/selectors/first.md @@ -11,7 +11,7 @@ menu: weight: 501 related: - /influxdb/v2.0/query-data/flux/first-last/ - - https://docs.influxdata.com/influxdb/latest/query_language/functions/#first, InfluxQL – FIRST() + - /{{< latest "influxdb" "v1" >}}/query_language/functions/#first, InfluxQL – FIRST() --- The `first()` function selects the first non-null record from an input table. diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/selectors/last.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/selectors/last.md index 02cedded6..8840a4d6f 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/selectors/last.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/selectors/last.md @@ -11,7 +11,7 @@ menu: weight: 501 related: - /influxdb/v2.0/query-data/flux/first-last/ - - https://docs.influxdata.com/influxdb/latest/query_language/functions/#last, InfluxQL – LAST() + - /{{< latest "influxdb" "v1" >}}/query_language/functions/#last, InfluxQL – LAST() --- The `last()` function selects the last non-null record from an input table. diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/selectors/max.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/selectors/max.md index 3576a0afc..552b08852 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/selectors/max.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/selectors/max.md @@ -10,7 +10,7 @@ menu: parent: built-in-selectors weight: 501 related: - - https://docs.influxdata.com/influxdb/latest/query_language/functions/#max, InfluxQL – MAX() + - /{{< latest "influxdb" "v1" >}}/query_language/functions/#max, InfluxQL – MAX() --- The `max()` function selects record with the highest `_value` from the input table. diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/selectors/min.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/selectors/min.md index 0b5c48cb0..c872b1ec3 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/selectors/min.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/selectors/min.md @@ -10,7 +10,7 @@ menu: parent: built-in-selectors weight: 501 related: - - https://docs.influxdata.com/influxdb/latest/query_language/functions/#min, InfluxQL – MIN() + - /{{< latest "influxdb" "v1" >}}/query_language/functions/#min, InfluxQL – MIN() --- The `min()` function selects record with the lowest `_value` from the input table. diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/selectors/sample.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/selectors/sample.md index f0b82e43c..f3b830643 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/selectors/sample.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/selectors/sample.md @@ -10,7 +10,7 @@ menu: parent: built-in-selectors weight: 501 related: - - https://docs.influxdata.com/influxdb/latest/query_language/functions/#sample, InfluxQL – SAMPLE() + - /{{< latest "influxdb" "v1" >}}/query_language/functions/#sample, InfluxQL – SAMPLE() --- The `sample()` function selects a subset of the records from the input table. diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/timedmovingaverage.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/timedmovingaverage.md index a0a30c1e7..8d9f1ada2 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/timedmovingaverage.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/timedmovingaverage.md @@ -16,7 +16,7 @@ related: - /v2.0/reference/flux/stdlib/built-in/transformations/exponentialmovingaverage/ - /v2.0/reference/flux/stdlib/built-in/transformations/doubleema/ - /v2.0/reference/flux/stdlib/built-in/transformations/tripleema/ - - https://docs.influxdata.com/influxdb/latest/query_language/functions/#moving-average, InfluxQL MOVING_AVERAGE() + - /{{< latest "influxdb" "v1" >}}/query_language/functions/#moving-average, InfluxQL MOVING_AVERAGE() --- The `timedMovingAverage()` function calculates the mean of values in a defined time diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/tripleema.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/tripleema.md index 84c09f594..2af55021d 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/tripleema.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/tripleema.md @@ -17,7 +17,7 @@ related: - /v2.0/reference/flux/stdlib/built-in/transformations/doubleema/ - /v2.0/reference/flux/stdlib/built-in/transformations/timedmovingaverage/ - /v2.0/reference/flux/stdlib/built-in/transformations/exponentialmovingaverage/ - - https://docs.influxdata.com/influxdb/latest/query_language/functions/#triple-exponential-moving-average, InfluxQL TRIPLE_EXPONENTIAL_MOVING_AVERAGE() + - /{{< latest "influxdb" "v1" >}}/query_language/functions/#triple-exponential-moving-average, InfluxQL TRIPLE_EXPONENTIAL_MOVING_AVERAGE() --- The `tripleEMA()` function calculates the exponential moving average of values in diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/tripleexponentialderivative.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/tripleexponentialderivative.md index 4bac9835c..366235009 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/tripleexponentialderivative.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/tripleexponentialderivative.md @@ -18,7 +18,7 @@ related: - /v2.0/reference/flux/stdlib/built-in/transformations/tripleema/ - /v2.0/reference/flux/stdlib/built-in/transformations/timedmovingaverage/ - /v2.0/reference/flux/stdlib/built-in/transformations/exponentialmovingaverage/ - - https://docs.influxdata.com/influxdb/latest/query_language/functions/#triple-exponential-derivative, InfluxQL TRIPLE_EXPONENTIAL_DERIVATIVE() + - /{{< latest "influxdb" "v1" >}}/query_language/functions/#triple-exponential-derivative, InfluxQL TRIPLE_EXPONENTIAL_DERIVATIVE() --- The `tripleExponentialDerivative()` function calculates a triple exponential diff --git a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/window.md b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/window.md index d6d0c6325..c31afe976 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/window.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/window.md @@ -12,7 +12,7 @@ weight: 402 related: - /influxdb/v2.0/query-data/flux/window-aggregate/ - /v2.0/reference/flux/stdlib/built-in/transformations/aggregates/aggregatewindow/ - - https://docs.influxdata.com/influxdb/latest/query_language/data_exploration/#the-group-by-clause, InfluxQL – GROUP BY time() + - /{{< latest "influxdb" "v1" >}}/query_language/data_exploration/#the-group-by-clause, InfluxQL – GROUP BY time() --- The `window()` function groups records based on a time value. diff --git a/content/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/databases.md b/content/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/databases.md index c030e3546..996bc5426 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/databases.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/databases.md @@ -7,7 +7,7 @@ menu: parent: InfluxDB v1 weight: 301 related: - - https://docs.influxdata.com/influxdb/latest/query_language/schema_exploration#show-databases, SHOW DATABASES in InfluxQL + - /{{< latest "influxdb" "v1" >}}/query_language/schema_exploration#show-databases, SHOW DATABASES in InfluxQL --- The `v1.databases()` function returns a list of databases in an **InfluxDB 1.7+ instance**. diff --git a/content/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/fieldkeys.md b/content/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/fieldkeys.md index 44cc1616d..d86d93c90 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/fieldkeys.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/fieldkeys.md @@ -9,7 +9,7 @@ weight: 301 influxdb/v2.0/tags: [fields] related: - /influxdb/v2.0/query-data/flux/explore-schema/ - - https://docs.influxdata.com/influxdb/latest/query_language/schema_exploration#show-field-keys, SHOW FIELD KEYS in InfluxQL + - /{{< latest "influxdb" "v1" >}}/query_language/schema_exploration#show-field-keys, SHOW FIELD KEYS in InfluxQL --- The `v1.fieldKeys()` function returns field keys in a bucket. diff --git a/content/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/measurementfieldkeys.md b/content/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/measurementfieldkeys.md index eb65e7070..8fc9e52c1 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/measurementfieldkeys.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/measurementfieldkeys.md @@ -9,7 +9,7 @@ weight: 301 influxdb/v2.0/tags: [fields] related: - /influxdb/v2.0/query-data/flux/explore-schema/ - - https://docs.influxdata.com/influxdb/latest/query_language/schema_exploration#show-field-keys, SHOW FIELD KEYS in InfluxQL + - /{{< latest "influxdb" "v1" >}}/query_language/schema_exploration#show-field-keys, SHOW FIELD KEYS in InfluxQL --- The `v1.measurementFieldKeys()` function returns a list of fields in a measurement. diff --git a/content/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/measurements.md b/content/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/measurements.md index 08e674ad8..91aa0e2ad 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/measurements.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/measurements.md @@ -11,7 +11,7 @@ weight: 301 influxdb/v2.0/tags: [measurements] related: - /influxdb/v2.0/query-data/flux/explore-schema/ - - https://docs.influxdata.com/influxdb/latest/query_language/schema_exploration#show-measurements, SHOW MEASUREMENTS in InfluxQL + - /{{< latest "influxdb" "v1" >}}/query_language/schema_exploration#show-measurements, SHOW MEASUREMENTS in InfluxQL --- The `v1.measurements()` function returns a list of measurements in a specific bucket. diff --git a/content/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/measurementtagkeys.md b/content/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/measurementtagkeys.md index 433cdadba..df27528d6 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/measurementtagkeys.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/measurementtagkeys.md @@ -11,7 +11,7 @@ weight: 301 influxdb/v2.0/tags: [tags] related: - /influxdb/v2.0/query-data/flux/explore-schema/ - - https://docs.influxdata.com/influxdb/latest/query_language/schema_exploration#show-tag-keys, SHOW TAG KEYS in InfluxQL + - /{{< latest "influxdb" "v1" >}}/query_language/schema_exploration#show-tag-keys, SHOW TAG KEYS in InfluxQL --- The `v1.measurementTagKeys()` function returns a list of tag keys for a specific measurement. diff --git a/content/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/measurementtagvalues.md b/content/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/measurementtagvalues.md index 416a5cec7..b9a74f7ab 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/measurementtagvalues.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/measurementtagvalues.md @@ -11,7 +11,7 @@ weight: 301 influxdb/v2.0/tags: [tags] related: - /influxdb/v2.0/query-data/flux/explore-schema/ - - https://docs.influxdata.com/influxdb/latest/query_language/schema_exploration#show-tag-values, SHOW TAG VALUES in InfluxQL + - /{{< latest "influxdb" "v1" >}}/query_language/schema_exploration#show-tag-values, SHOW TAG VALUES in InfluxQL --- The `v1.measurementTagValues()` function returns a list of tag values for a specific measurement. diff --git a/content/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/tagkeys.md b/content/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/tagkeys.md index c1cda5a87..4eb48645e 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/tagkeys.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/tagkeys.md @@ -11,7 +11,7 @@ weight: 301 influxdb/v2.0/tags: [tags] related: - /influxdb/v2.0/query-data/flux/explore-schema/ - - https://docs.influxdata.com/influxdb/latest/query_language/schema_exploration#show-tag-keys, SHOW TAG KEYS in InfluxQL + - /{{< latest "influxdb" "v1" >}}/query_language/schema_exploration#show-tag-keys, SHOW TAG KEYS in InfluxQL --- The `v1.tagKeys()` function returns a list of tag keys for all series that match the [`predicate`](#predicate). diff --git a/content/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/tagvalues.md b/content/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/tagvalues.md index c499976db..2417b8786 100644 --- a/content/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/tagvalues.md +++ b/content/influxdb/v2.0/reference/flux/stdlib/influxdb-v1/tagvalues.md @@ -11,7 +11,7 @@ weight: 301 influxdb/v2.0/tags: [tags] related: - /influxdb/v2.0/query-data/flux/explore-schema/ - - https://docs.influxdata.com/influxdb/latest/query_language/schema_exploration#show-tag-values, SHOW TAG VALUES in InfluxQL + - /{{< latest "influxdb" "v1" >}}/query_language/schema_exploration#show-tag-values, SHOW TAG VALUES in InfluxQL --- The `v1.tagValues()` function returns a list unique values for a given tag. diff --git a/content/influxdb/v2.0/reference/glossary.md b/content/influxdb/v2.0/reference/glossary.md index 0c94ef20b..c5ace0343 100644 --- a/content/influxdb/v2.0/reference/glossary.md +++ b/content/influxdb/v2.0/reference/glossary.md @@ -860,7 +860,7 @@ The series cardinality would remain unchanged at 6, as `firstname` is already sc | cliff@influxdata.com | start | clifford | | cliff@influxdata.com | finish | clifford | - + Related entries: [field key](#field-key),[measurement](#measurement), [tag key](#tag-key), [tag set](#tag-set) @@ -910,7 +910,7 @@ Related entries: [series](#series), [shard duration](#shard-duration), [shard gr The shard duration determines how much time each shard group spans. The specific interval is determined by the `SHARD DURATION` of the retention policy. - + The applications InfluxDB, Telegraf and Kapacitor will need to be installed in that order and on the same host. @@ -57,7 +57,7 @@ All examples will assume that Kapacitor is running on `http://localhost:9092` an InfluxDB + Telegraf ------------------- -Install [InfluxDB](https://docs.influxdata.com/influxdb/latest/introduction/installation/) using the Linux system packages (`.deb`,`.rpm`) if available. +Install [InfluxDB](/{{< latest "influxdb" "v1" >}}/introduction/installation/) using the Linux system packages (`.deb`,`.rpm`) if available. Start InfluxDB using systemctl: @@ -103,7 +103,7 @@ zář 01 14:47:44 algonquin influxd[14778]: [I] 2017-09-01T12:47:44Z Storing sta -Next install [Telegraf](https://docs.influxdata.com/telegraf/latest/introduction/installation/) using the Linux system packages (`.deb`,`.rpm`) if available. +Next install [Telegraf](/{{< latest "telegraf" >}}/introduction/installation/) using the Linux system packages (`.deb`,`.rpm`) if available. Once Telegraf is installed and started, it will, as configured by default, send system metrics to InfluxDB, which automatically creates the 'telegraf' database. diff --git a/content/kapacitor/v1.4/nodes/alert_node.md b/content/kapacitor/v1.4/nodes/alert_node.md index 74d20ab7e..ab898b064 100644 --- a/content/kapacitor/v1.4/nodes/alert_node.md +++ b/content/kapacitor/v1.4/nodes/alert_node.md @@ -28,7 +28,7 @@ menu: | **[email](#email) ( `to` `...string`)** | Email the alert data. | | **[exec](#exec) ( `executable` `string`, `args` `...string`)** | Execute a command whenever an alert is triggered and pass the alert data over STDIN in JSON format. | | **[flapping](#flapping) ( `low` `float64`, `high` `float64`)** | Perform flap detection on the alerts. The method used is similar method to Nagios: https://assets.nagios.com/downloads/nagioscore/docs/nagioscore/3/en/flapping.html | -| **[hipChat](#hipchat) ( )** | Send the alert to HipChat. For step-by-step instructions on setting up Kapacitor with HipChat, see the [Event Handler Setup Guide](https://docs.influxdata.com//kapacitor/latest/guides/event-handler-setup/#hipchat-setup). To allow Kapacitor to post to HipChat, go to the URL https://www.hipchat.com/docs/apiv2 for information on how to get your room id and tokens. | +| **[hipChat](#hipchat) ( )** | Send the alert to HipChat. For step-by-step instructions on setting up Kapacitor with HipChat, see the [Event Handler Setup Guide](//{{< latest "kapacitor" >}}/guides/event-handler-setup/#hipchat-setup). To allow Kapacitor to post to HipChat, go to the URL https://www.hipchat.com/docs/apiv2 for information on how to get your room id and tokens. | | **[history](#history) ( `value` `int64`)** | Number of previous states to remember when computing flapping levels and checking for state changes. Minimum value is 2 in order to keep track of current and previous states. | | **[id](#id) ( `value` `string`)** | Template for constructing a unique ID for a given alert. | | **[idField](#idfield) ( `value` `string`)** | Optional field key to add to the data, containing the alert ID as a string. | @@ -52,7 +52,7 @@ menu: | **[stateChangesOnly](#statechangesonly) ( `maxInterval` `...time.Duration`)** | Only sends events where the state changed. Each different alert level OK, INFO, WARNING, and CRITICAL are considered different states. | | **[talk](#talk) ( )** | Send the alert to Talk. To use Talk alerting you must first follow the steps to create a new incoming webhook. | | **[tcp](#tcp) ( `address` `string`)** | Send JSON alert data to a specified address over TCP. | -| **[telegram](#telegram) ( )** | Send the alert to Telegram. For step-by-step instructions on setting up Kapacitor with Telegram, see the [Event Handler Setup Guide](https://docs.influxdata.com//kapacitor/latest/guides/event-handler-setup/#telegram-setup). To allow Kapacitor to post to Telegram, | +| **[telegram](#telegram) ( )** | Send the alert to Telegram. For step-by-step instructions on setting up Kapacitor with Telegram, see the [Event Handler Setup Guide](//{{< latest "kapacitor" >}}/guides/event-handler-setup/#telegram-setup). To allow Kapacitor to post to Telegram, | | **[topic](#topic) ( `value` `string`)** | Topic specifies the name of an alert topic to which, alerts will be published. Alert handlers can be configured per topic, see the API documentation. | | **[victorOps](#victorops) ( )** | Send alert to VictorOps. To use VictorOps alerting you must first enable the 'Alert Ingestion API' in the 'Integrations' section of VictorOps. Then place the API key from the URL into the 'victorops' section of the Kapacitor configuration. | | **[warn](#warn) ( `value` `ast.LambdaNode`)** | Filter expression for the WARNING alert level. An empty value indicates the level is invalid and is skipped. | @@ -67,7 +67,7 @@ menu: ### Description An [AlertNode](/kapacitor/v1.4/nodes/alert_node/) can trigger an event of varying severity levels and pass the event to alert handlers. -The criteria for triggering an alert is specified using a [lambda expression](/kapacitor/latest/tick/expr/). +The criteria for triggering an alert is specified using a [lambda expression](/{{< latest "kapacitor" >}}/tick/expr/). See [AlertNode.Info,](/kapacitor/v1.4/nodes/alert_node/#info) [AlertNode.Warn,](/kapacitor/v1.4/nodes/alert_node/#warn) and [AlertNode.Crit](/kapacitor/v1.4/nodes/alert_node/#crit) below. Different event handlers can be configured for each [AlertNode.](/kapacitor/v1.4/nodes/alert_node/) @@ -608,7 +608,7 @@ alert.flapping(low float64, high float64) ### HipChat Send the alert to HipChat. -For step-by-step instructions on setting up Kapacitor with HipChat, see the [Event Handler Setup Guide](https://docs.influxdata.com//kapacitor/latest/guides/event-handler-setup/#hipchat-setup). +For step-by-step instructions on setting up Kapacitor with HipChat, see the [Event Handler Setup Guide](//{{< latest "kapacitor" >}}/guides/event-handler-setup/#hipchat-setup). To allow Kapacitor to post to HipChat, go to the URL https://www.hipchat.com/docs/apiv2 for information on how to get your room id and tokens. @@ -1925,7 +1925,7 @@ alert.tcp(address string) ### Telegram Send the alert to Telegram. -For step-by-step instructions on setting up Kapacitor with Telegram, see the [Event Handler Setup Guide](https://docs.influxdata.com//kapacitor/latest/guides/event-handler-setup/#telegram-setup). +For step-by-step instructions on setting up Kapacitor with Telegram, see the [Event Handler Setup Guide](//{{< latest "kapacitor" >}}/guides/event-handler-setup/#telegram-setup). To allow Kapacitor to post to Telegram, Example: @@ -2515,7 +2515,7 @@ Returns: [GroupByNode](/kapacitor/v1.4/nodes/group_by_node/) ### HoltWinters -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```javascript @@ -2528,7 +2528,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.4/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.4/nodes/barrier_node.md b/content/kapacitor/v1.4/nodes/barrier_node.md index a7305e0e4..a9ffc3e28 100644 --- a/content/kapacitor/v1.4/nodes/barrier_node.md +++ b/content/kapacitor/v1.4/nodes/barrier_node.md @@ -421,7 +421,7 @@ Returns: [GroupByNode](/kapacitor/v1.4/nodes/group_by_node/) ### HoltWinters -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```javascript @@ -434,7 +434,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.4/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.4/nodes/combine_node.md b/content/kapacitor/v1.4/nodes/combine_node.md index 9f448f26d..e7e26a6f5 100644 --- a/content/kapacitor/v1.4/nodes/combine_node.md +++ b/content/kapacitor/v1.4/nodes/combine_node.md @@ -485,7 +485,7 @@ Returns: [GroupByNode](/kapacitor/v1.4/nodes/group_by_node/) ### HoltWinters -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```javascript @@ -498,7 +498,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.4/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.4/nodes/default_node.md b/content/kapacitor/v1.4/nodes/default_node.md index 52b259fc5..340340004 100644 --- a/content/kapacitor/v1.4/nodes/default_node.md +++ b/content/kapacitor/v1.4/nodes/default_node.md @@ -417,7 +417,7 @@ Returns: [GroupByNode](/kapacitor/v1.4/nodes/group_by_node/) ### HoltWinters -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```javascript @@ -430,7 +430,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.4/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.4/nodes/delete_node.md b/content/kapacitor/v1.4/nodes/delete_node.md index 5eb09c075..94a4accbc 100644 --- a/content/kapacitor/v1.4/nodes/delete_node.md +++ b/content/kapacitor/v1.4/nodes/delete_node.md @@ -416,7 +416,7 @@ Returns: [GroupByNode](/kapacitor/v1.4/nodes/group_by_node/) ### HoltWinters -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```javascript @@ -429,7 +429,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.4/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.4/nodes/derivative_node.md b/content/kapacitor/v1.4/nodes/derivative_node.md index b00953043..e21316143 100644 --- a/content/kapacitor/v1.4/nodes/derivative_node.md +++ b/content/kapacitor/v1.4/nodes/derivative_node.md @@ -439,7 +439,7 @@ Returns: [GroupByNode](/kapacitor/v1.4/nodes/group_by_node/) ### HoltWinters -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```javascript @@ -452,7 +452,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.4/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.4/nodes/ec2_autoscale_node.md b/content/kapacitor/v1.4/nodes/ec2_autoscale_node.md index 1374165be..aca302811 100644 --- a/content/kapacitor/v1.4/nodes/ec2_autoscale_node.md +++ b/content/kapacitor/v1.4/nodes/ec2_autoscale_node.md @@ -584,7 +584,7 @@ Returns: [GroupByNode](/kapacitor/v1.4/nodes/group_by_node/) ### `holtWinters` -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```javascript @@ -597,7 +597,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.4/nodes/influx_q_l_node/) ### `holtWintersWithFit` -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.4/nodes/eval_node.md b/content/kapacitor/v1.4/nodes/eval_node.md index 82a670649..6c5efab37 100644 --- a/content/kapacitor/v1.4/nodes/eval_node.md +++ b/content/kapacitor/v1.4/nodes/eval_node.md @@ -519,7 +519,7 @@ Returns: [GroupByNode](/kapacitor/v1.4/nodes/group_by_node/) ### HoltWinters -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```javascript @@ -532,7 +532,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.4/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.4/nodes/flatten_node.md b/content/kapacitor/v1.4/nodes/flatten_node.md index b71142103..7c0a024f8 100644 --- a/content/kapacitor/v1.4/nodes/flatten_node.md +++ b/content/kapacitor/v1.4/nodes/flatten_node.md @@ -466,7 +466,7 @@ Returns: [GroupByNode](/kapacitor/v1.4/nodes/group_by_node/) ### HoltWinters -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```javascript @@ -479,7 +479,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.4/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.4/nodes/from_node.md b/content/kapacitor/v1.4/nodes/from_node.md index be4fc5954..e7f7cdd14 100644 --- a/content/kapacitor/v1.4/nodes/from_node.md +++ b/content/kapacitor/v1.4/nodes/from_node.md @@ -27,7 +27,7 @@ menu: | **[retentionPolicy](#retentionpolicy) ( `value` `string`)** | The retention policy name If empty any retention policy will be used. | | **[round](#round) ( `value` `time.Duration`)** | Optional duration for rounding timestamps. Helpful to ensure data points land on specific boundaries Example: stream |from() .measurement('mydata') .round(1s) | | **[truncate](#truncate) ( `value` `time.Duration`)** | Optional duration for truncating timestamps. Helpful to ensure data points land on specific boundaries Example: stream |from() .measurement('mydata') .truncate(1s) | -| **[where](#where) ( `lambda` `ast.LambdaNode`)** | Filter the current stream using the given expression. This expression is a Kapacitor expression. Kapacitor expressions are a superset of InfluxQL WHERE expressions. See the [expression](https://docs.influxdata.com/kapacitor/latest/tick/expr/) docs for more information. | +| **[where](#where) ( `lambda` `ast.LambdaNode`)** | Filter the current stream using the given expression. This expression is a Kapacitor expression. Kapacitor expressions are a superset of InfluxQL WHERE expressions. See the [expression](/{{< latest "kapacitor" >}}/tick/expr/) docs for more information. | @@ -211,7 +211,7 @@ from.truncate(value time.Duration) Filter the current stream using the given expression. This expression is a Kapacitor expression. Kapacitor expressions are a superset of InfluxQL WHERE expressions. -See the [expression](https://docs.influxdata.com/kapacitor/latest/tick/expr/) docs for more information. +See the [expression](/{{< latest "kapacitor" >}}/tick/expr/) docs for more information. Multiple calls to the Where method will `AND` together each expression. @@ -645,7 +645,7 @@ Returns: [FromNode](/kapacitor/v1.4/nodes/from_node/) ### HoltWinters -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```javascript @@ -658,7 +658,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.4/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.4/nodes/group_by_node.md b/content/kapacitor/v1.4/nodes/group_by_node.md index 523a31a82..a5618352c 100644 --- a/content/kapacitor/v1.4/nodes/group_by_node.md +++ b/content/kapacitor/v1.4/nodes/group_by_node.md @@ -438,7 +438,7 @@ Returns: [GroupByNode](/kapacitor/v1.4/nodes/group_by_node/) ### HoltWinters -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```javascript @@ -451,7 +451,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.4/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.4/nodes/http_out_node.md b/content/kapacitor/v1.4/nodes/http_out_node.md index eb79b7e6c..d292d9be4 100644 --- a/content/kapacitor/v1.4/nodes/http_out_node.md +++ b/content/kapacitor/v1.4/nodes/http_out_node.md @@ -387,7 +387,7 @@ Returns: [GroupByNode](/kapacitor/v1.4/nodes/group_by_node/) ### HoltWinters -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```javascript @@ -400,7 +400,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.4/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.4/nodes/http_post_node.md b/content/kapacitor/v1.4/nodes/http_post_node.md index 62536f065..84a22c02a 100644 --- a/content/kapacitor/v1.4/nodes/http_post_node.md +++ b/content/kapacitor/v1.4/nodes/http_post_node.md @@ -490,7 +490,7 @@ Returns: [GroupByNode](/kapacitor/v1.4/nodes/group_by_node/) ### HoltWinters -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```javascript @@ -503,7 +503,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.4/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.4/nodes/influx_q_l_node.md b/content/kapacitor/v1.4/nodes/influx_q_l_node.md index 37325b6b1..cc69edaef 100644 --- a/content/kapacitor/v1.4/nodes/influx_q_l_node.md +++ b/content/kapacitor/v1.4/nodes/influx_q_l_node.md @@ -421,7 +421,7 @@ Returns: [GroupByNode](/kapacitor/v1.4/nodes/group_by_node/) ### HoltWinters -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```javascript @@ -434,7 +434,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.4/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.4/nodes/join_node.md b/content/kapacitor/v1.4/nodes/join_node.md index 438592220..9cd7c145e 100644 --- a/content/kapacitor/v1.4/nodes/join_node.md +++ b/content/kapacitor/v1.4/nodes/join_node.md @@ -585,7 +585,7 @@ Returns: [GroupByNode](/kapacitor/v1.4/nodes/group_by_node/) ### HoltWinters -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```javascript @@ -598,7 +598,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.4/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.4/nodes/k8s_autoscale_node.md b/content/kapacitor/v1.4/nodes/k8s_autoscale_node.md index 4a2876113..1b63f2c87 100644 --- a/content/kapacitor/v1.4/nodes/k8s_autoscale_node.md +++ b/content/kapacitor/v1.4/nodes/k8s_autoscale_node.md @@ -642,7 +642,7 @@ Returns: [GroupByNode](/kapacitor/v1.4/nodes/group_by_node/) ### HoltWinters -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```javascript @@ -655,7 +655,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.4/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.4/nodes/log_node.md b/content/kapacitor/v1.4/nodes/log_node.md index bbf451b0d..56e5dd28f 100644 --- a/content/kapacitor/v1.4/nodes/log_node.md +++ b/content/kapacitor/v1.4/nodes/log_node.md @@ -413,7 +413,7 @@ Returns: [GroupByNode](/kapacitor/v1.4/nodes/group_by_node/) ### HoltWinters -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```javascript @@ -426,7 +426,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.4/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.4/nodes/no_op_node.md b/content/kapacitor/v1.4/nodes/no_op_node.md index 36e1be71b..c2ad26891 100644 --- a/content/kapacitor/v1.4/nodes/no_op_node.md +++ b/content/kapacitor/v1.4/nodes/no_op_node.md @@ -368,7 +368,7 @@ Returns: [GroupByNode](/kapacitor/v1.4/nodes/group_by_node/) ### HoltWinters -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```javascript @@ -381,7 +381,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.4/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.4/nodes/query_node.md b/content/kapacitor/v1.4/nodes/query_node.md index 6d0d86dd3..58c158e8e 100644 --- a/content/kapacitor/v1.4/nodes/query_node.md +++ b/content/kapacitor/v1.4/nodes/query_node.md @@ -601,7 +601,7 @@ Returns: [FlattenNode](/kapacitor/v1.4/nodes/flatten_node/) ### HoltWinters -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```javascript @@ -614,7 +614,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.4/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.4/nodes/sample_node.md b/content/kapacitor/v1.4/nodes/sample_node.md index 1910c0639..369054c69 100644 --- a/content/kapacitor/v1.4/nodes/sample_node.md +++ b/content/kapacitor/v1.4/nodes/sample_node.md @@ -384,7 +384,7 @@ Returns: [GroupByNode](/kapacitor/v1.4/nodes/group_by_node/) ### HoltWinters -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```javascript @@ -397,7 +397,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.4/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.4/nodes/shift_node.md b/content/kapacitor/v1.4/nodes/shift_node.md index 0cfa4b118..5d75ecba2 100644 --- a/content/kapacitor/v1.4/nodes/shift_node.md +++ b/content/kapacitor/v1.4/nodes/shift_node.md @@ -382,7 +382,7 @@ Returns: [GroupByNode](/kapacitor/v1.4/nodes/group_by_node/) ### HoltWinters -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```javascript @@ -395,7 +395,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.4/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.4/nodes/sideload_node.md b/content/kapacitor/v1.4/nodes/sideload_node.md index 40cd8df9d..f37512b84 100644 --- a/content/kapacitor/v1.4/nodes/sideload_node.md +++ b/content/kapacitor/v1.4/nodes/sideload_node.md @@ -445,7 +445,7 @@ Returns: [GroupByNode](/kapacitor/v1.4/nodes/group_by_node/) ### HoltWinters -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```javascript @@ -458,7 +458,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.4/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.4/nodes/state_count_node.md b/content/kapacitor/v1.4/nodes/state_count_node.md index 156bdb27c..9aba1f07f 100644 --- a/content/kapacitor/v1.4/nodes/state_count_node.md +++ b/content/kapacitor/v1.4/nodes/state_count_node.md @@ -412,7 +412,7 @@ Returns: [GroupByNode](/kapacitor/v1.4/nodes/group_by_node/) ### HoltWinters -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```javascript @@ -425,7 +425,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.4/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.4/nodes/state_duration_node.md b/content/kapacitor/v1.4/nodes/state_duration_node.md index 84af0320d..c837a96df 100644 --- a/content/kapacitor/v1.4/nodes/state_duration_node.md +++ b/content/kapacitor/v1.4/nodes/state_duration_node.md @@ -430,7 +430,7 @@ Returns: [GroupByNode](/kapacitor/v1.4/nodes/group_by_node/) ### HoltWinters -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```javascript @@ -443,7 +443,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.4/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.4/nodes/stats_node.md b/content/kapacitor/v1.4/nodes/stats_node.md index 194d75af2..fcdf7bd6b 100644 --- a/content/kapacitor/v1.4/nodes/stats_node.md +++ b/content/kapacitor/v1.4/nodes/stats_node.md @@ -420,7 +420,7 @@ Returns: [GroupByNode](/kapacitor/v1.4/nodes/group_by_node/) ### HoltWinters -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```javascript @@ -433,7 +433,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.4/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.4/nodes/swarm_autoscale_node.md b/content/kapacitor/v1.4/nodes/swarm_autoscale_node.md index 8ca3fc52f..319aa0155 100644 --- a/content/kapacitor/v1.4/nodes/swarm_autoscale_node.md +++ b/content/kapacitor/v1.4/nodes/swarm_autoscale_node.md @@ -580,7 +580,7 @@ Returns: [GroupByNode](/kapacitor/v1.4/nodes/group_by_node/) ### HoltWinters -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```javascript @@ -593,7 +593,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.4/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.4/nodes/u_d_f_node.md b/content/kapacitor/v1.4/nodes/u_d_f_node.md index 4fa089859..fa65da54e 100644 --- a/content/kapacitor/v1.4/nodes/u_d_f_node.md +++ b/content/kapacitor/v1.4/nodes/u_d_f_node.md @@ -424,7 +424,7 @@ Returns: [GroupByNode](/kapacitor/v1.4/nodes/group_by_node/) ### HoltWinters -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```javascript @@ -437,7 +437,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.4/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.4/nodes/union_node.md b/content/kapacitor/v1.4/nodes/union_node.md index a8bbe178b..493371e33 100644 --- a/content/kapacitor/v1.4/nodes/union_node.md +++ b/content/kapacitor/v1.4/nodes/union_node.md @@ -409,7 +409,7 @@ Returns: [GroupByNode](/kapacitor/v1.4/nodes/group_by_node/) ### HoltWinters -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```javascript @@ -422,7 +422,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.4/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.4/nodes/where_node.md b/content/kapacitor/v1.4/nodes/where_node.md index b2c2f7207..ba976d601 100644 --- a/content/kapacitor/v1.4/nodes/where_node.md +++ b/content/kapacitor/v1.4/nodes/where_node.md @@ -378,7 +378,7 @@ Returns: [GroupByNode](/kapacitor/v1.4/nodes/group_by_node/) ### HoltWinters -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```javascript @@ -391,7 +391,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.4/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.4/nodes/window_node.md b/content/kapacitor/v1.4/nodes/window_node.md index 68beda845..ccd18423e 100644 --- a/content/kapacitor/v1.4/nodes/window_node.md +++ b/content/kapacitor/v1.4/nodes/window_node.md @@ -483,7 +483,7 @@ Returns: [GroupByNode](/kapacitor/v1.4/nodes/group_by_node/) ### HoltWinters -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```javascript @@ -496,7 +496,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.4/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the holt-winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the holt-winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.4/working/api.md b/content/kapacitor/v1.4/working/api.md index 5f381c9a5..9da886f59 100644 --- a/content/kapacitor/v1.4/working/api.md +++ b/content/kapacitor/v1.4/working/api.md @@ -497,7 +497,7 @@ GET /kapacitor/v1/tasks?fields=status&fields=executing&fields=error ### Custom task HTTP endpoints -In TICKscript it is possible to expose a cache of recent data using the [HTTPOut](https://docs.influxdata.com/kapacitor/latest/nodes/http_out_node/) node. +In TICKscript it is possible to expose a cache of recent data using the [HTTPOut](/{{< latest "kapacitor" >}}/nodes/http_out_node/) node. The data is available at the path `/kapacitor/v1/tasks/TASK_ID/ENDPOINT_NAME`. ### Example @@ -542,7 +542,7 @@ GET /kapacitor/v1/tasks/TASK_ID/mycustom_endpoint } ``` -The output is the same as a query for data to [InfluxDB](https://docs.influxdata.com/influxdb/latest/guides/querying_data/). +The output is the same as a query for data to [InfluxDB](/{{< latest "influxdb" "v1" >}}/guides/querying_data/). ## Templates diff --git a/content/kapacitor/v1.5/about_the_project/releasenotes-changelog.md b/content/kapacitor/v1.5/about_the_project/releasenotes-changelog.md index 7a86b652a..11fef65bf 100644 --- a/content/kapacitor/v1.5/about_the_project/releasenotes-changelog.md +++ b/content/kapacitor/v1.5/about_the_project/releasenotes-changelog.md @@ -321,7 +321,7 @@ For example, to define the above aggregate handler on the system topic, use this kapacitor define-handler system aggregate_by_1m.yaml ``` -For more details on the alerting system, see the full documentation [here](https://docs.influxdata.com/kapacitor/v1.3/alerts). +For more details on the alerting system, see the full documentation [here](/kapacitor/v1.3/alerts). ### Breaking Change @@ -438,7 +438,7 @@ stream ``` The API exposes endpoints to query the state of each alert and endpoints for configuring alert handlers. -See the [API docs](https://docs.influxdata.com/kapacitor/latest/api/api/) for more details. +See the [API docs](/{{< latest "kapacitor" >}}/api/api/) for more details. The kapacitor CLI has been updated with commands for defining alert handlers. This release introduces a new feature where you can window based off the number of points instead of their time. @@ -466,7 +466,7 @@ As a result existing alert nodes will now remember the state of alerts after res >NOTE: The new alerting features are being released under technical preview. This means breaking changes may be made in later releases until the feature is considered complete. -See the [API docs on technical preview](https://docs.influxdata.com/kapacitor/v1.2/api/api/#technical-preview) for specifics of how this effects the API. +See the [API docs on technical preview](/kapacitor/v1.2/api/api/#technical-preview) for specifics of how this effects the API. ### Features @@ -525,7 +525,7 @@ stream New API endpoints have been added to be able to configure InfluxDB clusters and alert handlers dynamically without needing to restart the Kapacitor daemon. Along with the ability to dynamically configure a service, API endpoints have been added to test the configurable services. -See the [API docs](https://docs.influxdata.com/kapacitor/latest/api/api/) for more details. +See the [API docs](/{{< latest "kapacitor" >}}/api/api/) for more details. >NOTE: The `connect_errors` stat from the query node was removed since the client changed, all errors are now counted in the `query_errors` stat. diff --git a/content/kapacitor/v1.5/administration/subscription-management.md b/content/kapacitor/v1.5/administration/subscription-management.md index ae6b0eaf5..289b7099e 100644 --- a/content/kapacitor/v1.5/administration/subscription-management.md +++ b/content/kapacitor/v1.5/administration/subscription-management.md @@ -8,7 +8,7 @@ menu: weight: 100 --- -Kapacitor is tightly integrated with InfluxDB through the use of [InfluxDB subscriptions](/influxdb/latest/administration/subscription-management/), +Kapacitor is tightly integrated with InfluxDB through the use of [InfluxDB subscriptions](/{{< latest "influxdb" "v1" >}}/administration/subscription-management/), local or remote endpoints to which all data written to InfluxDB is copied. Kapacitor subscribes to InfluxDB allowing it to capture, manipulate, and act on your data. @@ -36,7 +36,7 @@ in the `kapacitor.conf`._ > do not persist between container stops and restarts. > If `/var/lib/kapacitor/` is not persisted, Kapacitor will create a new InfluxDB subscription > on startup, resulting in unnecessary "duplicate" subscriptions. -> You will then need to manually [drop the unnecessary subscriptions](/influxdb/latest/administration/subscription-management/#remove-subscriptions). +> You will then need to manually [drop the unnecessary subscriptions](/{{< latest "influxdb" "v1" >}}/administration/subscription-management/#remove-subscriptions). > > To avoid this, InfluxData recommends that you persist the `/var/lib/kapacitor` directory. > Many persistence strategies are available and which to use depends on your @@ -144,4 +144,4 @@ There are two ways to view your Kapacitor server or cluster ID: Duplicate Kapacitor subscriptions are often caused by the contents of `/var/lib/kapacitor` not persisting between restarts as described [above](#kapacitor-ids-in-containerized-or-ephemeral-filesystems). The solution is to ensure the contents of this director are persisted. -Any duplicate Kapacitor subscriptions already created will need to be [manually removed](/influxdb/latest/administration/subscription-management/#remove-subscriptions). +Any duplicate Kapacitor subscriptions already created will need to be [manually removed](/{{< latest "influxdb" "v1" >}}/administration/subscription-management/#remove-subscriptions). diff --git a/content/kapacitor/v1.5/administration/upgrading.md b/content/kapacitor/v1.5/administration/upgrading.md index 8ba97eb08..0dd8b1b3f 100644 --- a/content/kapacitor/v1.5/administration/upgrading.md +++ b/content/kapacitor/v1.5/administration/upgrading.md @@ -29,7 +29,7 @@ Before proceeding with the Kapacitor upgrade please ensure that InfluxDB and Tel * Telegraf 1.6 * Kapacitor 1.5 -For instructions on upgrading InfluxDB, please see the [InfluxDB upgrade](/influxdb/latest/administration/upgrading/) documentation. For instructions on upgrading Telegraf, please see the [Telegraf upgrade](/telegraf/latest/administration/upgrading/#main-nav) documentation. +For instructions on upgrading InfluxDB, please see the [InfluxDB upgrade](/{{< latest "influxdb" "v1" >}}/administration/upgrading/) documentation. For instructions on upgrading Telegraf, please see the [Telegraf upgrade](/{{< latest "telegraf" >}}/administration/upgrading/#main-nav) documentation. For information about what is new in the latest Kapacitor release, view the [Changelog](/kapacitor/v1.5/about_the_project/releasenotes-changelog/). diff --git a/content/kapacitor/v1.5/guides/continuous_queries.md b/content/kapacitor/v1.5/guides/continuous_queries.md index a825223da..052d7a148 100644 --- a/content/kapacitor/v1.5/guides/continuous_queries.md +++ b/content/kapacitor/v1.5/guides/continuous_queries.md @@ -155,7 +155,7 @@ batch Kapacitor is a powerful tool. If you need more flexibility than CQs offer, use it. -For more information and help writing TICKscripts from InfluxQL queries take a look at these [docs](https://docs.influxdata.com/kapacitor/latest/nodes/influx_q_l_node/) on the InfluxQL node in Kapacitor. +For more information and help writing TICKscripts from InfluxQL queries take a look at these [docs](/{{< latest "kapacitor" >}}/nodes/influx_q_l_node/) on the InfluxQL node in Kapacitor. Every function available in the InfluxDB query language is available in Kapacitor, so you can convert any query into a Kapacitor TICKscript. ## Important to Know diff --git a/content/kapacitor/v1.5/guides/event-handler-setup.md b/content/kapacitor/v1.5/guides/event-handler-setup.md index da621e4a9..99675b495 100644 --- a/content/kapacitor/v1.5/guides/event-handler-setup.md +++ b/content/kapacitor/v1.5/guides/event-handler-setup.md @@ -7,17 +7,17 @@ menu: parent: guides --- -Integrate Kapacitor into your monitoring system by sending [alert messages](/kapacitor/latest/nodes/alert_node/#message) +Integrate Kapacitor into your monitoring system by sending [alert messages](/{{< latest "kapacitor" >}}/nodes/alert_node/#message) to supported event handlers. Currently, Kapacitor can send alert messages to specific log files and specific URLs, as well as to applications such as [Slack](https://slack.com/) and [HipChat](https://www.hipchat.com/). This document offers step-by-step instructions for setting up event handlers with Kapacitor, -including relevant configuration options and [TICKscript](/kapacitor/latest/tick/) syntax. +including relevant configuration options and [TICKscript](/{{< latest "kapacitor" >}}/tick/) syntax. Currently, this document doesn't cover every supported event handler, but we will continue to add content to this page over time. For a complete list of the supported event handlers and for additional information, -please see the [event handler reference documentation](/kapacitor/latest/nodes/alert_node/). +please see the [event handler reference documentation](/{{< latest "kapacitor" >}}/nodes/alert_node/). [HipChat Setup](#hipchat-setup) [Telegram Setup](#telegram-setup") diff --git a/content/kapacitor/v1.5/guides/join_backfill.md b/content/kapacitor/v1.5/guides/join_backfill.md index 4375bd73c..976147db5 100644 --- a/content/kapacitor/v1.5/guides/join_backfill.md +++ b/content/kapacitor/v1.5/guides/join_backfill.md @@ -237,7 +237,7 @@ errors ### Record Query and backfill with stream To provide historical data to stream tasks that process multiple measurements, -use [multiple statements](/influxdb/latest/query_language/data_exploration/#multiple-statements) +use [multiple statements](/{{< latest "influxdb" "v1" >}}/query_language/data_exploration/#multiple-statements) when recording the data. First use `record query` following the pattern of this generic command: diff --git a/content/kapacitor/v1.5/guides/two-measurement-alert.md b/content/kapacitor/v1.5/guides/two-measurement-alert.md index 618847694..77431a3ac 100644 --- a/content/kapacitor/v1.5/guides/two-measurement-alert.md +++ b/content/kapacitor/v1.5/guides/two-measurement-alert.md @@ -16,7 +16,7 @@ As an added bonus, we'll also include a query that can be used to graph the perc difference between the two measurements. ## Comparing measurements and creating an alert -The following [TICKscript](/kapacitor/latest/tick/) streams the `m1` and `m2` measurements, +The following [TICKscript](/{{< latest "kapacitor" >}}/tick/) streams the `m1` and `m2` measurements, joins them, compares them, and triggers an alert if the two measurements are different. ```js diff --git a/content/kapacitor/v1.5/nodes/alert_node.md b/content/kapacitor/v1.5/nodes/alert_node.md index e929d68c7..b933a7c2b 100644 --- a/content/kapacitor/v1.5/nodes/alert_node.md +++ b/content/kapacitor/v1.5/nodes/alert_node.md @@ -13,7 +13,7 @@ menu: The `alert` node triggers an event of varying severity levels and passes the event to [event handlers](/kapacitor/v1.5/event_handlers/). The criteria for -triggering an alert is specified via a [lambda expression](/kapacitor/latest/tick/expr/). +triggering an alert is specified via a [lambda expression](/{{< latest "kapacitor" >}}/tick/expr/). See [AlertNode.Info](/kapacitor/v1.5/nodes/alert_node/#info), [AlertNode.Warn](/kapacitor/v1.5/nodes/alert_node/#warn), and [AlertNode.Crit](/kapacitor/v1.5/nodes/alert_node/#crit) below. @@ -1629,7 +1629,7 @@ Returns: [GroupByNode](/kapacitor/v1.5/nodes/group_by_node/) ### HoltWinters -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```js alert|holtWinters(field string, h int64, m int64, interval time.Duration) @@ -1641,7 +1641,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.5/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. ```js diff --git a/content/kapacitor/v1.5/nodes/barrier_node.md b/content/kapacitor/v1.5/nodes/barrier_node.md index e5a60a4cd..4d84fe9d2 100644 --- a/content/kapacitor/v1.5/nodes/barrier_node.md +++ b/content/kapacitor/v1.5/nodes/barrier_node.md @@ -515,7 +515,7 @@ Returns: [GroupByNode](/kapacitor/v1.5/nodes/group_by_node/) ### HoltWinters -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```js @@ -528,7 +528,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.5/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.5/nodes/change_detect_node.md b/content/kapacitor/v1.5/nodes/change_detect_node.md index 248acd85f..2e5d78187 100644 --- a/content/kapacitor/v1.5/nodes/change_detect_node.md +++ b/content/kapacitor/v1.5/nodes/change_detect_node.md @@ -449,7 +449,7 @@ Returns: [GroupByNode](/kapacitor/v1.5/nodes/group_by_node/) ### HoltWinters -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```js @@ -462,7 +462,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.5/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.5/nodes/combine_node.md b/content/kapacitor/v1.5/nodes/combine_node.md index 37deaf0d4..5924f1300 100644 --- a/content/kapacitor/v1.5/nodes/combine_node.md +++ b/content/kapacitor/v1.5/nodes/combine_node.md @@ -545,7 +545,7 @@ Returns: [GroupByNode](/kapacitor/v1.5/nodes/group_by_node/) ### HoltWinters -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```js @@ -558,7 +558,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.5/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.5/nodes/default_node.md b/content/kapacitor/v1.5/nodes/default_node.md index 412f4ec0b..2789d4e23 100644 --- a/content/kapacitor/v1.5/nodes/default_node.md +++ b/content/kapacitor/v1.5/nodes/default_node.md @@ -484,7 +484,7 @@ Returns: [GroupByNode](/kapacitor/v1.5/nodes/group_by_node/) ### HoltWinters -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```js @@ -497,7 +497,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.5/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.5/nodes/delete_node.md b/content/kapacitor/v1.5/nodes/delete_node.md index 4d9923360..194da4388 100644 --- a/content/kapacitor/v1.5/nodes/delete_node.md +++ b/content/kapacitor/v1.5/nodes/delete_node.md @@ -482,7 +482,7 @@ Returns: [GroupByNode](/kapacitor/v1.5/nodes/group_by_node/) ### HoltWinters -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```js @@ -495,7 +495,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.5/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.5/nodes/derivative_node.md b/content/kapacitor/v1.5/nodes/derivative_node.md index 542e1056f..95aa522aa 100644 --- a/content/kapacitor/v1.5/nodes/derivative_node.md +++ b/content/kapacitor/v1.5/nodes/derivative_node.md @@ -507,7 +507,7 @@ Returns: [GroupByNode](/kapacitor/v1.5/nodes/group_by_node/) ### HoltWinters -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```js @@ -520,7 +520,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.5/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.5/nodes/ec2_autoscale_node.md b/content/kapacitor/v1.5/nodes/ec2_autoscale_node.md index 4a823cf4a..41453dd13 100644 --- a/content/kapacitor/v1.5/nodes/ec2_autoscale_node.md +++ b/content/kapacitor/v1.5/nodes/ec2_autoscale_node.md @@ -646,7 +646,7 @@ Returns: [GroupByNode](/kapacitor/v1.5/nodes/group_by_node/) ### HoltWinters -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```js @@ -659,7 +659,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.5/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.5/nodes/eval_node.md b/content/kapacitor/v1.5/nodes/eval_node.md index 6529b8f18..8cc23a430 100644 --- a/content/kapacitor/v1.5/nodes/eval_node.md +++ b/content/kapacitor/v1.5/nodes/eval_node.md @@ -574,7 +574,7 @@ Returns: [GroupByNode](/kapacitor/v1.5/nodes/group_by_node/) ### HoltWinters -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```js @@ -587,7 +587,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.5/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.5/nodes/flatten_node.md b/content/kapacitor/v1.5/nodes/flatten_node.md index 26a45a9dc..5511e9bd7 100644 --- a/content/kapacitor/v1.5/nodes/flatten_node.md +++ b/content/kapacitor/v1.5/nodes/flatten_node.md @@ -542,7 +542,7 @@ Returns: [GroupByNode](/kapacitor/v1.5/nodes/group_by_node/) ### HoltWinters -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```js @@ -555,7 +555,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.5/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.5/nodes/from_node.md b/content/kapacitor/v1.5/nodes/from_node.md index cef670684..b4264c0ee 100644 --- a/content/kapacitor/v1.5/nodes/from_node.md +++ b/content/kapacitor/v1.5/nodes/from_node.md @@ -51,7 +51,7 @@ the tag `host` matches the regex `logger\d+`. | **[retentionPolicy](#retentionpolicy) ( `value` `string`)** | The retention policy name If empty any retention policy will be used. | | **[round](#round) ( `value` `time.Duration`)** | Optional duration for rounding timestamps. Helpful to ensure data points land on specific boundaries Example: stream |from() .measurement('mydata') .round(1s) | | **[truncate](#truncate) ( `value` `time.Duration`)** | Optional duration for truncating timestamps. Helpful to ensure data points land on specific boundaries Example: stream |from() .measurement('mydata') .truncate(1s) | -| **[where](#where) ( `lambda` `ast.LambdaNode`)** | Filter the current stream using the given expression. This expression is a Kapacitor expression. Kapacitor expressions are a superset of InfluxQL WHERE expressions. See the [expression](https://docs.influxdata.com/kapacitor/latest/tick/expr/) docs for more information. | +| **[where](#where) ( `lambda` `ast.LambdaNode`)** | Filter the current stream using the given expression. This expression is a Kapacitor expression. Kapacitor expressions are a superset of InfluxQL WHERE expressions. See the [expression](/{{< latest "kapacitor" >}}/tick/expr/) docs for more information. | @@ -270,7 +270,7 @@ from.truncate(value time.Duration) Filter the current stream using the given expression. This expression is a Kapacitor expression. Kapacitor expressions are a superset of InfluxQL WHERE expressions. -See the [expression](https://docs.influxdata.com/kapacitor/latest/tick/expr/) docs for more information. +See the [expression](/{{< latest "kapacitor" >}}/tick/expr/) docs for more information. Multiple calls to the Where method will `AND` together each expression. @@ -713,7 +713,7 @@ Returns: [FromNode](/kapacitor/v1.5/nodes/from_node/) ### HoltWinters -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```js @@ -726,7 +726,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.5/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.5/nodes/group_by_node.md b/content/kapacitor/v1.5/nodes/group_by_node.md index 1bf43ba35..7d6c71fb3 100644 --- a/content/kapacitor/v1.5/nodes/group_by_node.md +++ b/content/kapacitor/v1.5/nodes/group_by_node.md @@ -510,7 +510,7 @@ Returns: [GroupByNode](/kapacitor/v1.5/nodes/group_by_node/) ### HoltWinters -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```js @@ -523,7 +523,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.5/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.5/nodes/http_out_node.md b/content/kapacitor/v1.5/nodes/http_out_node.md index e83144aad..10cab74dc 100644 --- a/content/kapacitor/v1.5/nodes/http_out_node.md +++ b/content/kapacitor/v1.5/nodes/http_out_node.md @@ -465,7 +465,7 @@ Returns: [GroupByNode](/kapacitor/v1.5/nodes/group_by_node/) ### HoltWinters -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```js @@ -478,7 +478,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.5/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.5/nodes/http_post_node.md b/content/kapacitor/v1.5/nodes/http_post_node.md index c597662c2..30f0e9b3e 100644 --- a/content/kapacitor/v1.5/nodes/http_post_node.md +++ b/content/kapacitor/v1.5/nodes/http_post_node.md @@ -558,7 +558,7 @@ Returns: [GroupByNode](/kapacitor/v1.5/nodes/group_by_node/) ### HoltWinters -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```js @@ -571,7 +571,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.5/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.5/nodes/influx_q_l_node.md b/content/kapacitor/v1.5/nodes/influx_q_l_node.md index 343021513..7a5e6e0d3 100644 --- a/content/kapacitor/v1.5/nodes/influx_q_l_node.md +++ b/content/kapacitor/v1.5/nodes/influx_q_l_node.md @@ -492,7 +492,7 @@ Returns: [GroupByNode](/kapacitor/v1.5/nodes/group_by_node/) ### HoltWinters -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```js @@ -505,7 +505,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.5/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.5/nodes/join_node.md b/content/kapacitor/v1.5/nodes/join_node.md index 9e24e8573..9204a727e 100644 --- a/content/kapacitor/v1.5/nodes/join_node.md +++ b/content/kapacitor/v1.5/nodes/join_node.md @@ -265,7 +265,7 @@ Example: #### Handling null fill values in outer joins When using Kapacitor to perform an outer join, it's important to set default values for `null` fields resulting from the join and fill operations. -This is done using the [DefaultNode](/kapacitor/latest/nodes/default_node/), +This is done using the [DefaultNode](/{{< latest "kapacitor" >}}/nodes/default_node/), which replaces null values for a specific field key with a specified default value. Not doing so may result in invalid line protocol (as `null` isn't an appropriate value for all field types) causing the join to fail. @@ -740,7 +740,7 @@ Returns: [GroupByNode](/kapacitor/v1.5/nodes/group_by_node/) ### HoltWinters -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```js @@ -753,7 +753,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.5/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.5/nodes/k8s_autoscale_node.md b/content/kapacitor/v1.5/nodes/k8s_autoscale_node.md index 8831df1b5..f3a34c87b 100644 --- a/content/kapacitor/v1.5/nodes/k8s_autoscale_node.md +++ b/content/kapacitor/v1.5/nodes/k8s_autoscale_node.md @@ -708,7 +708,7 @@ Returns: [GroupByNode](/kapacitor/v1.5/nodes/group_by_node/) ### HoltWinters -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```js @@ -721,7 +721,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.5/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.5/nodes/log_node.md b/content/kapacitor/v1.5/nodes/log_node.md index c6434ba14..ccfd49aff 100644 --- a/content/kapacitor/v1.5/nodes/log_node.md +++ b/content/kapacitor/v1.5/nodes/log_node.md @@ -481,7 +481,7 @@ Returns: [GroupByNode](/kapacitor/v1.5/nodes/group_by_node/) ### HoltWinters -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```js @@ -494,7 +494,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.5/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.5/nodes/no_op_node.md b/content/kapacitor/v1.5/nodes/no_op_node.md index f941de6a7..41d135ca7 100644 --- a/content/kapacitor/v1.5/nodes/no_op_node.md +++ b/content/kapacitor/v1.5/nodes/no_op_node.md @@ -448,7 +448,7 @@ Returns: [GroupByNode](/kapacitor/v1.5/nodes/group_by_node/) ### HoltWinters -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```js @@ -461,7 +461,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.5/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.5/nodes/query_node.md b/content/kapacitor/v1.5/nodes/query_node.md index 36135743d..788a77b42 100644 --- a/content/kapacitor/v1.5/nodes/query_node.md +++ b/content/kapacitor/v1.5/nodes/query_node.md @@ -693,7 +693,7 @@ Returns: [FlattenNode](/kapacitor/v1.5/nodes/flatten_node/) ### HoltWinters -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```js @@ -706,7 +706,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.5/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.5/nodes/sample_node.md b/content/kapacitor/v1.5/nodes/sample_node.md index b8b3bbc11..5720e632f 100644 --- a/content/kapacitor/v1.5/nodes/sample_node.md +++ b/content/kapacitor/v1.5/nodes/sample_node.md @@ -462,7 +462,7 @@ Returns: [GroupByNode](/kapacitor/v1.5/nodes/group_by_node/) ### HoltWinters -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```js @@ -475,7 +475,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.5/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.5/nodes/shift_node.md b/content/kapacitor/v1.5/nodes/shift_node.md index a4238fe83..dd0bf5e6b 100644 --- a/content/kapacitor/v1.5/nodes/shift_node.md +++ b/content/kapacitor/v1.5/nodes/shift_node.md @@ -461,7 +461,7 @@ Returns: [GroupByNode](/kapacitor/v1.5/nodes/group_by_node/) ### HoltWinters -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```js @@ -474,7 +474,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.5/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.5/nodes/sideload_node.md b/content/kapacitor/v1.5/nodes/sideload_node.md index d7bcdce41..22d4439d4 100644 --- a/content/kapacitor/v1.5/nodes/sideload_node.md +++ b/content/kapacitor/v1.5/nodes/sideload_node.md @@ -514,7 +514,7 @@ Returns: [GroupByNode](/kapacitor/v1.5/nodes/group_by_node/) ### HoltWinters -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```js @@ -527,7 +527,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.5/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.5/nodes/state_count_node.md b/content/kapacitor/v1.5/nodes/state_count_node.md index 8df173b0d..1246dff87 100644 --- a/content/kapacitor/v1.5/nodes/state_count_node.md +++ b/content/kapacitor/v1.5/nodes/state_count_node.md @@ -479,7 +479,7 @@ Returns: [GroupByNode](/kapacitor/v1.5/nodes/group_by_node/) ### HoltWinters -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```js @@ -492,7 +492,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.5/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.5/nodes/state_duration_node.md b/content/kapacitor/v1.5/nodes/state_duration_node.md index 75aee01cb..7ea8710e9 100644 --- a/content/kapacitor/v1.5/nodes/state_duration_node.md +++ b/content/kapacitor/v1.5/nodes/state_duration_node.md @@ -503,7 +503,7 @@ Returns: [GroupByNode](/kapacitor/v1.5/nodes/group_by_node/) ### HoltWinters -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```js @@ -516,7 +516,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.5/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.5/nodes/stats_node.md b/content/kapacitor/v1.5/nodes/stats_node.md index 28ad4571b..aae1048d0 100644 --- a/content/kapacitor/v1.5/nodes/stats_node.md +++ b/content/kapacitor/v1.5/nodes/stats_node.md @@ -490,7 +490,7 @@ Returns: [GroupByNode](/kapacitor/v1.5/nodes/group_by_node/) ### HoltWinters -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```js @@ -503,7 +503,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.5/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.5/nodes/swarm_autoscale_node.md b/content/kapacitor/v1.5/nodes/swarm_autoscale_node.md index 7ab6b632f..7ab154a6d 100644 --- a/content/kapacitor/v1.5/nodes/swarm_autoscale_node.md +++ b/content/kapacitor/v1.5/nodes/swarm_autoscale_node.md @@ -646,7 +646,7 @@ Returns: [GroupByNode](/kapacitor/v1.5/nodes/group_by_node/) ### HoltWinters -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```js @@ -659,7 +659,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.5/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.5/nodes/u_d_f_node.md b/content/kapacitor/v1.5/nodes/u_d_f_node.md index 3b61017fc..23c32da92 100644 --- a/content/kapacitor/v1.5/nodes/u_d_f_node.md +++ b/content/kapacitor/v1.5/nodes/u_d_f_node.md @@ -494,7 +494,7 @@ Returns: [GroupByNode](/kapacitor/v1.5/nodes/group_by_node/) ### HoltWinters -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```js @@ -507,7 +507,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.5/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.5/nodes/union_node.md b/content/kapacitor/v1.5/nodes/union_node.md index b6ff615b2..1c92f026f 100644 --- a/content/kapacitor/v1.5/nodes/union_node.md +++ b/content/kapacitor/v1.5/nodes/union_node.md @@ -477,7 +477,7 @@ Returns: [GroupByNode](/kapacitor/v1.5/nodes/group_by_node/) ### HoltWinters -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```js @@ -490,7 +490,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.5/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.5/nodes/where_node.md b/content/kapacitor/v1.5/nodes/where_node.md index 2f602c577..444e1a623 100644 --- a/content/kapacitor/v1.5/nodes/where_node.md +++ b/content/kapacitor/v1.5/nodes/where_node.md @@ -457,7 +457,7 @@ Returns: [GroupByNode](/kapacitor/v1.5/nodes/group_by_node/) ### HoltWinters -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```js @@ -470,7 +470,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.5/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.5/nodes/window_node.md b/content/kapacitor/v1.5/nodes/window_node.md index a2593d44c..bb2a252b1 100644 --- a/content/kapacitor/v1.5/nodes/window_node.md +++ b/content/kapacitor/v1.5/nodes/window_node.md @@ -548,7 +548,7 @@ Returns: [GroupByNode](/kapacitor/v1.5/nodes/group_by_node/) ### HoltWinters -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. ```js @@ -561,7 +561,7 @@ Returns: [InfluxQLNode](/kapacitor/v1.5/nodes/influx_q_l_node/) ### HoltWintersWithFit -Compute the Holt-Winters (https://docs.influxdata.com/influxdb/latest/query_language/functions/#holt-winters) forecast of a data set. +Compute the Holt-Winters (/{{< latest "influxdb" "v1" >}}/query_language/functions/#holt-winters) forecast of a data set. This method also outputs all the points used to fit the data in addition to the forecasted data. diff --git a/content/kapacitor/v1.5/working/api.md b/content/kapacitor/v1.5/working/api.md index d386aa474..0d10a61ba 100644 --- a/content/kapacitor/v1.5/working/api.md +++ b/content/kapacitor/v1.5/working/api.md @@ -98,7 +98,7 @@ The technical preview endpoints are only available under the v1preview path. ## Writing data -Kapacitor accepts writing data over HTTP using InfluxData's [Line Protocol data format](/influxdb/latest/write_protocols/). +Kapacitor accepts writing data over HTTP using InfluxData's [Line Protocol data format](/{{< latest "influxdb" "v1" >}}/write_protocols/). The `kapacitor/v1/write` endpoint is identical in nature to the InfluxDB `/write` endpoint. | Query Parameter | Purpose | @@ -500,7 +500,7 @@ GET /kapacitor/v1/tasks?fields=status&fields=executing&fields=error ### Custom task HTTP endpoints -In TICKscript, it is possible to expose a cache of recent data via the [HTTPOut](https://docs.influxdata.com/kapacitor/latest/nodes/http_out_node/) node. +In TICKscript, it is possible to expose a cache of recent data via the [HTTPOut](/{{< latest "kapacitor" >}}/nodes/http_out_node/) node. The data is available at the path `/kapacitor/v1/tasks/TASK_ID/ENDPOINT_NAME`. ### Example @@ -545,7 +545,7 @@ GET /kapacitor/v1/tasks/TASK_ID/mycustom_endpoint } ``` -The output is the same as a query for data to [InfluxDB](https://docs.influxdata.com/influxdb/latest/guides/querying_data/). +The output is the same as a query for data to [InfluxDB](/{{< latest "influxdb" "v1" >}}/guides/querying_data/). ## Templates diff --git a/content/platform/_index.md b/content/platform/_index.md index c44cc127c..ca1755bae 100644 --- a/content/platform/_index.md +++ b/content/platform/_index.md @@ -30,8 +30,8 @@ The **InfluxData 1.x platform** includes the following open source components ([ The **InfluxDB 2.0 platform** consolidates components from the **InfluxData 1.x platform** into a single packaged solution, with added features and flexibility: - - [InfluxDB 2.0 OSS](https://v2.docs.influxdata.com/v2.0/get-started/): open source platform solution in a single binary - - [InfluxDB Cloud 2.0](https://v2.docs.influxdata.com/v2.0/get-started/) (**commercial offering**): hosted cloud solution + - [InfluxDB 2.0 OSS](/influxdb/v2.0/get-started/): open source platform solution in a single binary + - [InfluxDB Cloud 2.0](/influxdb/v2.0/get-started/) (**commercial offering**): hosted cloud solution InfluxDB Enterprise 2.0 is in development. @@ -40,9 +40,9 @@ InfluxDB Enterprise 2.0 is in development. ### Telegraf Telegraf is a data collection agent that captures data from a growing list of sources -and translates it into [InfluxDB line protocol format](/influxdb/latest/write_protocols/line_protocol_reference/) +and translates it into [InfluxDB line protocol format](/{{< latest "influxdb" "v1" >}}/write_protocols/line_protocol_reference/) for storage in InfluxDB. Telegraf's extensible architecture makes it easy to -create [plugins](/telegraf/latest/plugins/) that both pull data (input plugins) and push data (output plugins) +create [plugins](/{{< latest "telegraf" >}}/plugins/) that both pull data (input plugins) and push data (output plugins) to and from different sources and endpoints. ### InfluxDB @@ -86,13 +86,13 @@ InfluxDB Enterprise provides functionality necessary to run a high-availability #### Hinted handoff Data is written across nodes using an eventually consistent write model. -All writes are added to the [Hinted Handoff Queue (HHQ)](/enterprise_influxdb/latest/concepts/clustering/#hinted-handoff), +All writes are added to the [Hinted Handoff Queue (HHQ)](/{{< latest "enterprise_influxdb" >}}/concepts/clustering/#hinted-handoff), then written to other nodes in the cluster. #### Anti-Entropy InfluxDB Enterprise's -[Anti-Entropy (AE)](/enterprise_influxdb/latest/administration/anti-entropy/) +[Anti-Entropy (AE)](/{{< latest "enterprise_influxdb" >}}/administration/anti-entropy/) process ensures data shards in the cluster are in sync. When "entropy" (out-of-sync data) is detected, AE will repair the affected shards, syncing the missing data. @@ -145,4 +145,4 @@ To get started with the **InfluxData 1.x** platform, see [Installation and Configuration](/platform/installation) [Getting Started](/platform/introduction/getting-started) -To get started with the **InfluxDB 2.0** platform, see [**InfluxDB Cloud 2.0**](https://v2.docs.influxdata.com/v2.0/get-started/) or [**InfluxDB 2.0 OSS**](https://v2.docs.influxdata.com/v2.0/get-started/). +To get started with the **InfluxDB 2.0** platform, see [**InfluxDB Cloud 2.0**](/influxdb/v2.0/get-started/) or [**InfluxDB 2.0 OSS**](/influxdb/v2.0/get-started/). diff --git a/content/platform/getting-started.md b/content/platform/getting-started.md index b962bbe0c..c02bf34b3 100644 --- a/content/platform/getting-started.md +++ b/content/platform/getting-started.md @@ -24,14 +24,14 @@ The configuration file for Telegraf specifies where metrics come from and where * `[[outputs.influxdb]]` - declares how to connect to InfluxDB and the destination database, which is the default ‘telegraf’ database. * `[[inputs.cpu]]` - declares how to collect the system cpu metrics to be sent to InfluxDB. Enabled by default. -For details about the configuration file, see [Get started with Telegraf](https://docs.influxdata.com/telegraf/latest/introduction/getting-started/). +For details about the configuration file, see [Get started with Telegraf](/{{< latest "telegraf" >}}/introduction/getting-started/). ## Query data in InfluxDB As reviewed above, Telegraf is sending system data, including CPU usage, to InfluxDB. There are two ways you can query your InfluxDB data: -* [In Chronograf with the Data Explorer.](https://docs.influxdata.com/chronograf/latest/guides/create-a-dashboard/#step-3-create-your-query) Use the builder to select from your existing data and allow Chronograf to format the query for you. Alternatively, manually enter and edit a query. You can move between using the builder and manually editing the query. -* [Using the command line interface.](https://docs.influxdata.com/influxdb/latest/query_language/data_exploration/) +* [In Chronograf with the Data Explorer.](/{{< latest "chronograf" >}}/guides/create-a-dashboard/#step-3-create-your-query) Use the builder to select from your existing data and allow Chronograf to format the query for you. Alternatively, manually enter and edit a query. You can move between using the builder and manually editing the query. +* [Using the command line interface.](/{{< latest "influxdb" "v1" >}}/query_language/data_exploration/) **Query example:** @@ -44,10 +44,10 @@ WHERE time > now() - 30m ## Visualize that data in a Chronograf dashboard -Now that you've explored your data with queries, you can build a dashboard in Chronograf to visualize the data. For details, see [Create a dashboard](https://docs.influxdata.com/chronograf/latest/guides/create-a-dashboard) and [Using pre-created dashboards](https://docs.influxdata.com/chronograf/latest/guides/using-precreated-dashboards/). +Now that you've explored your data with queries, you can build a dashboard in Chronograf to visualize the data. For details, see [Create a dashboard](/{{< latest "chronograf" >}}/guides/create-a-dashboard) and [Using pre-created dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards/). ## Create an alert in Kapacitor based on that data Since InfluxDB is running on `localhost:8086`, Kapacitor finds it during start up and creates several subscriptions on InfluxDB. These subscriptions tell InfluxDB to send all the data it receives from Telegraf to Kapacitor. -For step-by-step instructions on how to set up an alert in Kapacitor based on your data, see [Creating Chronograf alert rules](https://docs.influxdata.com/chronograf/latest/guides/create-alert-rules/). +For step-by-step instructions on how to set up an alert in Kapacitor based on your data, see [Creating Chronograf alert rules](/{{< latest "chronograf" >}}/guides/create-alert-rules/). diff --git a/content/platform/install-and-deploy/install/_index.md b/content/platform/install-and-deploy/install/_index.md index 5b702edeb..85c8eaf1f 100644 --- a/content/platform/install-and-deploy/install/_index.md +++ b/content/platform/install-and-deploy/install/_index.md @@ -17,9 +17,9 @@ Install and configure the InfluxData platform (TICK stack) using one of the foll - [Install the open source version of InfluxData 1.x platform](/platform/install-and-deploy/install/oss-install) - Install InfluxData 1.x Enterprise: - a. [Install Telegraf](/telegraf/latest/introduction/installation/) + a. [Install Telegraf](/{{< latest "telegraf" >}}/introduction/installation/) - b. [Install InfluxDB Enterprise](/enterprise_influxdb/latest/install-and-deploy/) + b. [Install InfluxDB Enterprise](/{{< latest "enterprise_influxdb" >}}/install-and-deploy/) c. [Install Kapacitor Enterprise](/enterprise_kapacitor/latest/introduction/installation_guide/) diff --git a/content/platform/install-and-deploy/install/oss-install.md b/content/platform/install-and-deploy/install/oss-install.md index b815ece56..32e4ce54b 100644 --- a/content/platform/install-and-deploy/install/oss-install.md +++ b/content/platform/install-and-deploy/install/oss-install.md @@ -18,22 +18,22 @@ to be installed, configured, and started separately. ## Install Telegraf -The [Telegraf installation instructions](https://docs.influxdata.com/telegraf/latest/introduction/installation/) +The [Telegraf installation instructions](/{{< latest "telegraf" >}}/introduction/installation/) walk through installing and configuring Telegraf. ## Install InfluxDB -The [InfluxDB OSS installation instructions](https://docs.influxdata.com/influxdb/latest/introduction/installation/) +The [InfluxDB OSS installation instructions](/{{< latest "influxdb" "v1" >}}/introduction/installation/) walk through installing and configuring the open source version of InfluxDB. ## Install Chronograf -The [Chronograf installation instructions](https://docs.influxdata.com/chronograf/latest/introduction/installation/) +The [Chronograf installation instructions](/{{< latest "chronograf" >}}/introduction/installation/) walk through installing and configuring Chronograf. ## Install Kapacitor -The [Kapacitor OSS installation instructions](https://docs.influxdata.com/kapacitor/latest/introduction/installation/) +The [Kapacitor OSS installation instructions](/{{< latest "kapacitor" >}}/introduction/installation/) walk through installing and configuring the open source version of Kapacitor. ## InfluxData Sandbox diff --git a/content/platform/integrations/kubernetes.md b/content/platform/integrations/kubernetes.md index 83c0ad1f3..878d77bbe 100644 --- a/content/platform/integrations/kubernetes.md +++ b/content/platform/integrations/kubernetes.md @@ -15,7 +15,7 @@ has become a popular way to deploy and manage containers across multiple servers {{% note %}} This page is about using Kubernetes with the TICK stack and 1.x versions of InfluxDB. -To start experimenting with InfluxDB 2.0 and Kubernetes, go to the **Kubernetes** section of the [Get Started page for InfluxDB 2.0](https://v2.docs.influxdata.com/v2.0/get-started/). +To start experimenting with InfluxDB 2.0 and Kubernetes, go to the **Kubernetes** section of the [Get Started page for InfluxDB 2.0](/influxdb/v2.0/get-started/). {{% /note %}} There are several ways use the InfluxData Platform with Kubernetes: @@ -47,7 +47,7 @@ See the [kube-influxdb Getting Started guide](https://github.com/influxdata/kube ### Collect Kubernetes metrics with Telegraf -The [Telegraf metrics collection agent](/telegraf/latest/introduction/getting-started/) +The [Telegraf metrics collection agent](/{{< latest "telegraf" >}}/introduction/getting-started/) can collect many types of metrics in a Kubernetes cluster, like [Docker container metrics](https://github.com/influxdata/telegraf/blob/master/plugins/inputs/docker/README.md) and [stats from kubelets](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/kubernetes). It can even scrape [Prometheus metrics API endpoints](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/prometheus). @@ -63,7 +63,7 @@ using Prometheus for metrics collection. See the [FAQ](#frequently-asked-questions) for more information on why a more flexible time series data store is useful. -Read about [Prometheus remote read and write API support in InfluxDB](/influxdb/latest/supported_protocols/prometheus/). +Read about [Prometheus remote read and write API support in InfluxDB](/{{< latest "influxdb" "v1" >}}/supported_protocols/prometheus/). ## Deploy the TICK stack in Kubernetes Instructions for installing and configuring all components of the open source diff --git a/content/platform/monitoring/containers/kubernetes.md b/content/platform/monitoring/containers/kubernetes.md index 078d1f375..1fa1f57b5 100644 --- a/content/platform/monitoring/containers/kubernetes.md +++ b/content/platform/monitoring/containers/kubernetes.md @@ -21,7 +21,7 @@ The [kube-influxdb](https://github.com/influxdata/kube-influxdb) project is a se ### Collect Kubernetes metrics with Telegraf -The [Telegraf metrics collection agent](https://docs.influxdata.com/telegraf/v1.9/introduction/getting-started/) can collect many types of metrics in a Kubernetes cluster, like [Docker container metrics](https://github.com/influxdata/telegraf/blob/release-1.9/plugins/inputs/docker/README.md) and [stats from kubelets](https://github.com/influxdata/telegraf/tree/release-1.9/plugins/inputs/kubernetes). It can even scrape [Prometheus metrics API endpoints](https://github.com/influxdata/telegraf/tree/release-1.9/plugins/inputs/prometheus). Telegraf is used in the [kube-influxdb project](#kube-influxdb-kubernetes-monitoring-project) to collect metrics. +The [Telegraf metrics collection agent](/telegraf/v1.9/introduction/getting-started/) can collect many types of metrics in a Kubernetes cluster, like [Docker container metrics](https://github.com/influxdata/telegraf/blob/release-1.9/plugins/inputs/docker/README.md) and [stats from kubelets](https://github.com/influxdata/telegraf/tree/release-1.9/plugins/inputs/kubernetes). It can even scrape [Prometheus metrics API endpoints](https://github.com/influxdata/telegraf/tree/release-1.9/plugins/inputs/prometheus). Telegraf is used in the [kube-influxdb project](#kube-influxdb-kubernetes-monitoring-project) to collect metrics. [Read about setting up a Kubernetes monitoring architecture using Telegraf](https://www.influxdata.com/blog/monitoring-kubernetes-architecture/) @@ -29,4 +29,4 @@ The [Telegraf metrics collection agent](https://docs.influxdata.com/telegraf/v1. InfluxDB supports the Prometheus remote read and write API for clusters already using Prometheus for metrics collection, but need require a more flexible time series data store. -[Read about the Prometheus remote read and write API support in InfluxDB](https://docs.influxdata.com/influxdb/v1.7/supported_protocols/prometheus/) +[Read about the Prometheus remote read and write API support in InfluxDB](/influxdb/v1.7/supported_protocols/prometheus/) diff --git a/content/platform/monitoring/influxdata-platform/external-monitor-setup.md b/content/platform/monitoring/influxdata-platform/external-monitor-setup.md index fbfeceb23..e7ac4deb3 100644 --- a/content/platform/monitoring/influxdata-platform/external-monitor-setup.md +++ b/content/platform/monitoring/influxdata-platform/external-monitor-setup.md @@ -33,11 +33,11 @@ must be able to connect to your monitor's API endpoint via HTTP or UDP. {{% /note %}} ## Install Telegraf on each node -[Install the `telegraf` agent](/telegraf/latest/introduction/installation/#installation) +[Install the `telegraf` agent](/{{< latest "telegraf" >}}/introduction/installation/#installation) on each node in your primary InfluxDB cluster you would like to monitor. ### Send data collected by Telegraf to your monitor -[Generate a Telegraf configuration file](/telegraf/latest/introduction/installation/#configuration) +[Generate a Telegraf configuration file](/{{< latest "telegraf" >}}/introduction/installation/#configuration) and modify the InfluxDB output `url` setting to include the URL of your monitor's InfluxDB API endpoint. @@ -64,7 +64,7 @@ the host machine: - Swap - System (load, number of CPUs, number of users, uptime, etc.) -Use other [Telegraf input plugins](/telegraf/latest/plugins/inputs/) to collect +Use other [Telegraf input plugins](/{{< latest "telegraf" >}}/plugins/inputs/) to collect a variety of metrics. #### Monitor InfluxDB performance metrics @@ -156,5 +156,5 @@ telegraf -config path/to/telegraf.conf ## Create Kapacitor monitoring alerts Monitoring data should now be flowing from your primary cluster to your monitor where it can be processed by your monitor's Kapacitor component. -[Create Kapacitor alerts](/kapacitor/latest/working/alerts/) that alert you of issues +[Create Kapacitor alerts](/{{< latest "kapacitor" >}}/working/alerts/) that alert you of issues detected in any of the monitored metrics. diff --git a/content/platform/monitoring/influxdata-platform/internal-vs-external.md b/content/platform/monitoring/influxdata-platform/internal-vs-external.md index 39c03ee89..78920828f 100644 --- a/content/platform/monitoring/influxdata-platform/internal-vs-external.md +++ b/content/platform/monitoring/influxdata-platform/internal-vs-external.md @@ -31,7 +31,7 @@ _For the recommendation about `_internal` databases, see [Disable the `_internal [Monitoring dashboards](/platform/monitoring/monitoring-dashboards) are available that visualize the default metrics provided in each of these databases. -You can also [configure Kapacitor alerts](/kapacitor/latest/working/alerts/) +You can also [configure Kapacitor alerts](/{{< latest "kapacitor" >}}/working/alerts/) to monitor and alert on each of these metrics. ### Pros of internal monitoring @@ -71,7 +71,7 @@ _For information about setting up an external monitoring TICK stack, see [Setup [Monitoring dashboards](/platform/monitoring/influxdata-platform/monitoring-dashboards) are available that visualize the default metrics provided by the Telegraf agents. -You can also [configure Kapacitor alerts](/kapacitor/latest/working/alerts/) +You can also [configure Kapacitor alerts](/{{< latest "kapacitor" >}}/working/alerts/) to monitor and alert on each of these metrics. ### Pros of external monitoring @@ -96,7 +96,7 @@ It creates unnecessary overhead, particularly for busy clusters, that can overlo Metrics stored in the `_internal` database primarily measure workload performance, which should only be tested in non-production environments. -To disable the `_internal` database, set [`store-enabled`](/influxdb/latest/administration/config/#monitoring-settings-monitor) +To disable the `_internal` database, set [`store-enabled`](/{{< latest "influxdb" "v1" >}}/administration/config/#monitoring-settings-monitor) to `false` under the `[monitor]` section of your `influxdb.conf`. _**influxdb.conf**_ diff --git a/content/platform/monitoring/influxdata-platform/monitoring-dashboards.md b/content/platform/monitoring/influxdata-platform/monitoring-dashboards.md index a648ae69b..ab1291c50 100644 --- a/content/platform/monitoring/influxdata-platform/monitoring-dashboards.md +++ b/content/platform/monitoring/influxdata-platform/monitoring-dashboards.md @@ -33,7 +33,7 @@ Telegraf input plugins. To view prebuilt dashboards: ## Import monitoring dashboards Use the dashboards below to visualize and monitor key TICK stack metrics. Download the dashboard file and import it into Chronograf. -For detailed instructions, see [Importing a dashboard](/chronograf/latest/administration/import-export-dashboards/#importing-a-dashboard). +For detailed instructions, see [Importing a dashboard](/{{< latest "chronograf" >}}/administration/import-export-dashboards/#importing-a-dashboard). - [Monitor InfluxDB OSS](#monitor-influxdb-oss) - [Monitor InfluxDB Enterprise](#monitor-influxdb-enterprise) diff --git a/content/platform/monitoring/influxdata-platform/tools/kapacitor-measurements.md b/content/platform/monitoring/influxdata-platform/tools/kapacitor-measurements.md index 5af50b00f..1ddd4e5ff 100644 --- a/content/platform/monitoring/influxdata-platform/tools/kapacitor-measurements.md +++ b/content/platform/monitoring/influxdata-platform/tools/kapacitor-measurements.md @@ -92,8 +92,8 @@ Kapacitor exposes the following measurements and fields through the ### kapacitor The `kapacitor` measurement stores fields with information related to -[Kapacitor tasks](/kapacitor/latest/introduction/getting-started/#kapacitor-tasks) -and [subscriptions](/kapacitor/latest/administration/subscription-management/). +[Kapacitor tasks](/{{< latest "kapacitor" >}}/introduction/getting-started/#kapacitor-tasks) +and [subscriptions](/{{< latest "kapacitor" >}}/administration/subscription-management/). #### num_enabled_tasks The number of enabled Kapacitor tasks. @@ -108,7 +108,7 @@ The total number of Kapacitor tasks. ### kapacitor_edges The `kapacitor_edges` measurement stores fields with information related to -[edges](/kapacitor/latest/tick/introduction/#pipelines) +[edges](/{{< latest "kapacitor" >}}/tick/introduction/#pipelines) in Kapacitor TICKscripts. #### collected @@ -130,7 +130,7 @@ The number of points received by Kapacitor. ### kapacitor_load The `kapacitor_load` measurement stores fields with information related to the -[Kapacitor Load Directory service](/kapacitor/latest/guides/load_directory/). +[Kapacitor Load Directory service](/{{< latest "kapacitor" >}}/guides/load_directory/). #### errors The number of errors reported from the load directory service. @@ -225,7 +225,7 @@ The total number of bytes allocated, even if freed. ### kapacitor_nodes The `kapacitor_nodes` measurement stores fields related to events that occur in -[TICKscript nodes](/kapacitor/latest/nodes/). +[TICKscript nodes](/{{< latest "kapacitor" >}}/nodes/). #### alerts_inhibited The total number of alerts inhibited by TICKscripts. @@ -264,7 +264,7 @@ The number of errors that occurred when writing to InfluxDB or other write endpo ### kapacitor_topics The `kapacitor_topics` measurement stores fields related to -[Kapacitor topics](/kapacitor/latest/working/using_alert_topics/). +[Kapacitor topics](/{{< latest "kapacitor" >}}/working/using_alert_topics/). #### collected The number of events collected by Kapacitor topics. diff --git a/content/platform/monitoring/influxdata-platform/tools/measurements-internal.md b/content/platform/monitoring/influxdata-platform/tools/measurements-internal.md index 64de3e1a6..5635d4385 100644 --- a/content/platform/monitoring/influxdata-platform/tools/measurements-internal.md +++ b/content/platform/monitoring/influxdata-platform/tools/measurements-internal.md @@ -21,7 +21,7 @@ It creates unnecessary overhead, particularly for busy clusters, that can overlo Metrics stored in the `_internal` database primarily measure workload performance and should only be tested in non-production environments. -To disable the `_internal` database, set [`store-enabled`](/influxdb/latest/administration/config/#monitoring-settings-monitor) +To disable the `_internal` database, set [`store-enabled`](/{{< latest "influxdb" "v1" >}}/administration/config/#monitoring-settings-monitor) to `false` under the `[monitor]` section of your **InfluxDB configuration file**. ```toml @@ -365,7 +365,7 @@ The size, in bytes, of points read from the hinted handoff queue and sent to its Note that if the data node process is restarted while there is data in the HH queue, `bytesRead` may settle to a number larger than `bytesWritten`. Hinted handoff writes occur in concurrent batches as determined by the -[`retry-concurrency`](/enterprise_influxdb/latest/administration/configuration/#retry-concurrency-20) setting. +[`retry-concurrency`](/{{< latest "enterprise_influxdb" >}}/administration/configuration/#retry-concurrency-20) setting. If an individual write succeeds, the metric is incremented. If any write out of the whole batch fails, the entire batch is considered unsuccessful, and every part of the batch will be retried later. This was not the intended behavior of this stat. @@ -438,7 +438,7 @@ The size, in bytes, of points read from the hinted handoff queue and sent to its Note that if the data node process is restarted while there is data in the HH queue, `bytesRead` may settle to a number larger than `bytesWritten`. Hinted handoff writes occur in concurrent batches as determined by the -[`retry-concurrency`](/enterprise_influxdb/latest/administration/configuration/#retry-concurrency-20) setting. +[`retry-concurrency`](/{{< latest "enterprise_influxdb" >}}/administration/configuration/#retry-concurrency-20) setting. If an individual write succeeds, the metric is incremented. If any write out of the whole batch fails, the entire batch is considered unsuccessful, and every part of the batch will be retried later. diff --git a/content/platform/monitoring/influxdata-platform/tools/show-diagnostics.md b/content/platform/monitoring/influxdata-platform/tools/show-diagnostics.md index bd2c9cf69..2bdf58c84 100644 --- a/content/platform/monitoring/influxdata-platform/tools/show-diagnostics.md +++ b/content/platform/monitoring/influxdata-platform/tools/show-diagnostics.md @@ -12,7 +12,7 @@ menu: Diagnostic information includes mostly information about your InfluxDB server that is not necessarily numerical in format. This diagnostic information is not stored in the [`_internal`](/platform/monitoring/influxdata-platform/tools/measurements-internal/) database. -To see InfluxDB server or node diagnostic information, you can use the [`SHOW DIAGNOSTICS`](/influxdb/latest/query_language/spec#show-diagnostics) statement. This statement returns InfluxDB instance information, including build details, uptime, hostname, server configuration, memory usage, and Go runtime diagnostics. This information is particularly useful to InfluxData Support, so be sure to include the output of this query anytime you file a support ticket or GitHub issue. +To see InfluxDB server or node diagnostic information, you can use the [`SHOW DIAGNOSTICS`](/{{< latest "influxdb" "v1" >}}/query_language/spec#show-diagnostics) statement. This statement returns InfluxDB instance information, including build details, uptime, hostname, server configuration, memory usage, and Go runtime diagnostics. This information is particularly useful to InfluxData Support, so be sure to include the output of this query anytime you file a support ticket or GitHub issue. ## `SHOW DIAGNOSTICS` measurement details diff --git a/content/platform/monitoring/influxdata-platform/tools/show-stats.md b/content/platform/monitoring/influxdata-platform/tools/show-stats.md index 179238592..59fa7b263 100644 --- a/content/platform/monitoring/influxdata-platform/tools/show-stats.md +++ b/content/platform/monitoring/influxdata-platform/tools/show-stats.md @@ -12,7 +12,7 @@ menu: ## Using the `SHOW STATS` statement -The InfluxQL [`SHOW STATS`](https://docs.influxdata.com/influxdb/v1.6/query_language/spec#show-stats) +The InfluxQL [`SHOW STATS`](/influxdb/v1.6/query_language/spec#show-stats) statement returns detailed measurement statistics on InfluxDB servers and available (enabled) components. Each component exporting statistics exports a measurement named after the module and various series that are associated with the measurement. To monitor InfluxDB system measurements over time, you can use the `_internal` database. diff --git a/content/telegraf/v1.10/administration/troubleshooting.md b/content/telegraf/v1.10/administration/troubleshooting.md index 3d524e1af..fcca6bb23 100644 --- a/content/telegraf/v1.10/administration/troubleshooting.md +++ b/content/telegraf/v1.10/administration/troubleshooting.md @@ -23,7 +23,7 @@ The minimal Telegraf configuration required to enable a UDP output is: urls = ["udp://localhost:8089"] ``` -This setup utilizes the UDP format of the [InfluxDB output plugin](https://github.com/influxdata/telegraf/tree/master/plugins/outputs/influxdb) and emits points formatted in InfluxDB's [line protocol](/influxdb/latest/concepts/glossary/#line-protocol). +This setup utilizes the UDP format of the [InfluxDB output plugin](https://github.com/influxdata/telegraf/tree/master/plugins/outputs/influxdb) and emits points formatted in InfluxDB's [line protocol](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#line-protocol). You will need to append this section to the Telegraf configuration file and restart Telegraf for the change to take effect. Now you are ready to start listening on the destination port (`8089` in this example) using a simple tool like `netcat`: diff --git a/content/telegraf/v1.10/data_formats/input/influx.md b/content/telegraf/v1.10/data_formats/input/influx.md index 6b892c922..661219c6b 100644 --- a/content/telegraf/v1.10/data_formats/input/influx.md +++ b/content/telegraf/v1.10/data_formats/input/influx.md @@ -11,7 +11,7 @@ menu: There are no additional configuration options for InfluxDB [line protocol][]. The InfluxDB metrics are parsed directly into Telegraf metrics. -[line protocol]: /influxdb/latest/write_protocols/line/ +[line protocol]: /{{< latest "influxdb" "v1" >}}/write_protocols/line/ ### Configuration diff --git a/content/telegraf/v1.10/data_formats/output/influx.md b/content/telegraf/v1.10/data_formats/output/influx.md index 75ae077f1..794bb3495 100644 --- a/content/telegraf/v1.10/data_formats/output/influx.md +++ b/content/telegraf/v1.10/data_formats/output/influx.md @@ -38,4 +38,4 @@ The `influx` output data format outputs metrics into [InfluxDB Line Protocol][li influx_uint_support = false ``` -[line protocol]: /influxdb/latest/write_protocols/line_protocol_tutorial/ +[line protocol]: /{{< latest "influxdb" "v1" >}}/write_protocols/line_protocol_tutorial/ diff --git a/content/telegraf/v1.10/plugins/inputs.md b/content/telegraf/v1.10/plugins/inputs.md index eb545f507..c60e9ddd0 100644 --- a/content/telegraf/v1.10/plugins/inputs.md +++ b/content/telegraf/v1.10/plugins/inputs.md @@ -336,7 +336,7 @@ capturing and storing these metrics locally within the `_internal` database for Plugin ID: `influxdb_listener` The [InfluxDB Listener input plugin](https://github.com/influxdata/telegraf/blob/release-1.10/plugins/inputs/influxdb_listener/README.md) listens for requests sent -according to the [InfluxDB HTTP API](/influxdb/latest/guides/writing_data/). The intent of the +according to the [InfluxDB HTTP API](/{{< latest "influxdb" "v1" >}}/guides/writing_data/). The intent of the plugin is to allow Telegraf to serve as a proxy, or router, for the HTTP `/write` endpoint of the InfluxDB HTTP API. diff --git a/content/telegraf/v1.11/administration/troubleshooting.md b/content/telegraf/v1.11/administration/troubleshooting.md index f09dc82d2..176141308 100644 --- a/content/telegraf/v1.11/administration/troubleshooting.md +++ b/content/telegraf/v1.11/administration/troubleshooting.md @@ -23,7 +23,7 @@ The minimal Telegraf configuration required to enable a UDP output is: urls = ["udp://localhost:8089"] ``` -This setup utilizes the UDP format of the [InfluxDB output plugin](https://github.com/influxdata/telegraf/tree/master/plugins/outputs/influxdb) and emits points formatted in InfluxDB's [line protocol](/influxdb/latest/concepts/glossary/#line-protocol). +This setup utilizes the UDP format of the [InfluxDB output plugin](https://github.com/influxdata/telegraf/tree/master/plugins/outputs/influxdb) and emits points formatted in InfluxDB's [line protocol](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#line-protocol). You will need to append this section to the Telegraf configuration file and restart Telegraf for the change to take effect. Now you are ready to start listening on the destination port (`8089` in this example) using a simple tool like `netcat`: diff --git a/content/telegraf/v1.11/data_formats/input/influx.md b/content/telegraf/v1.11/data_formats/input/influx.md index ea85ed982..8f063c514 100644 --- a/content/telegraf/v1.11/data_formats/input/influx.md +++ b/content/telegraf/v1.11/data_formats/input/influx.md @@ -11,7 +11,7 @@ menu: There are no additional configuration options for InfluxDB [line protocol][]. The InfluxDB metrics are parsed directly into Telegraf metrics. -[line protocol]: /influxdb/latest/write_protocols/line/ +[line protocol]: /{{< latest "influxdb" "v1" >}}/write_protocols/line/ ### Configuration diff --git a/content/telegraf/v1.11/data_formats/output/influx.md b/content/telegraf/v1.11/data_formats/output/influx.md index 9093ca254..f182a811c 100644 --- a/content/telegraf/v1.11/data_formats/output/influx.md +++ b/content/telegraf/v1.11/data_formats/output/influx.md @@ -38,4 +38,4 @@ The `influx` output data format outputs metrics into [InfluxDB Line Protocol][li influx_uint_support = false ``` -[line protocol]: /influxdb/latest/write_protocols/line_protocol_tutorial/ +[line protocol]: /{{< latest "influxdb" "v1" >}}/write_protocols/line_protocol_tutorial/ diff --git a/content/telegraf/v1.12/administration/troubleshooting.md b/content/telegraf/v1.12/administration/troubleshooting.md index 7f699348d..356a47381 100644 --- a/content/telegraf/v1.12/administration/troubleshooting.md +++ b/content/telegraf/v1.12/administration/troubleshooting.md @@ -23,7 +23,7 @@ The minimal Telegraf configuration required to enable a UDP output is: urls = ["udp://localhost:8089"] ``` -This setup utilizes the UDP format of the [InfluxDB output plugin](https://github.com/influxdata/telegraf/tree/master/plugins/outputs/influxdb) and emits points formatted in InfluxDB's [line protocol](/influxdb/latest/concepts/glossary/#line-protocol). +This setup utilizes the UDP format of the [InfluxDB output plugin](https://github.com/influxdata/telegraf/tree/master/plugins/outputs/influxdb) and emits points formatted in InfluxDB's [line protocol](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#line-protocol). You will need to append this section to the Telegraf configuration file and restart Telegraf for the change to take effect. Now you are ready to start listening on the destination port (`8089` in this example) using a simple tool like `netcat`: diff --git a/content/telegraf/v1.12/data_formats/input/influx.md b/content/telegraf/v1.12/data_formats/input/influx.md index 796ef3b61..48193160d 100644 --- a/content/telegraf/v1.12/data_formats/input/influx.md +++ b/content/telegraf/v1.12/data_formats/input/influx.md @@ -11,7 +11,7 @@ menu: There are no additional configuration options for InfluxDB [line protocol][]. The InfluxDB metrics are parsed directly into Telegraf metrics. -[line protocol]: /influxdb/latest/write_protocols/line/ +[line protocol]: /{{< latest "influxdb" "v1" >}}/write_protocols/line/ ### Configuration diff --git a/content/telegraf/v1.12/data_formats/output/influx.md b/content/telegraf/v1.12/data_formats/output/influx.md index 4e3d344de..b3d6da1ca 100644 --- a/content/telegraf/v1.12/data_formats/output/influx.md +++ b/content/telegraf/v1.12/data_formats/output/influx.md @@ -38,4 +38,4 @@ The `influx` output data format outputs metrics into [InfluxDB Line Protocol][li influx_uint_support = false ``` -[line protocol]: /influxdb/latest/write_protocols/line_protocol_tutorial/ +[line protocol]: /{{< latest "influxdb" "v1" >}}/write_protocols/line_protocol_tutorial/ diff --git a/content/telegraf/v1.13/administration/troubleshooting.md b/content/telegraf/v1.13/administration/troubleshooting.md index 24a47dab7..e15650d38 100644 --- a/content/telegraf/v1.13/administration/troubleshooting.md +++ b/content/telegraf/v1.13/administration/troubleshooting.md @@ -23,7 +23,7 @@ The minimal Telegraf configuration required to enable a UDP output is: urls = ["udp://localhost:8089"] ``` -This setup utilizes the UDP format of the [InfluxDB output plugin](https://github.com/influxdata/telegraf/tree/master/plugins/outputs/influxdb) and emits points formatted in InfluxDB's [line protocol](/influxdb/latest/concepts/glossary/#line-protocol). +This setup utilizes the UDP format of the [InfluxDB output plugin](https://github.com/influxdata/telegraf/tree/master/plugins/outputs/influxdb) and emits points formatted in InfluxDB's [line protocol](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#line-protocol). You will need to append this section to the Telegraf configuration file and restart Telegraf for the change to take effect. Now you are ready to start listening on the destination port (`8089` in this example) using a simple tool like `netcat`: diff --git a/content/telegraf/v1.13/data_formats/input/influx.md b/content/telegraf/v1.13/data_formats/input/influx.md index 5cd33be5f..c638e2d4a 100644 --- a/content/telegraf/v1.13/data_formats/input/influx.md +++ b/content/telegraf/v1.13/data_formats/input/influx.md @@ -11,7 +11,7 @@ menu: There are no additional configuration options for InfluxDB [line protocol][]. The InfluxDB metrics are parsed directly into Telegraf metrics. -[line protocol]: /influxdb/latest/write_protocols/line/ +[line protocol]: /{{< latest "influxdb" "v1" >}}/write_protocols/line/ ### Configuration diff --git a/content/telegraf/v1.13/data_formats/output/influx.md b/content/telegraf/v1.13/data_formats/output/influx.md index 0776ee20d..2e39a21ec 100644 --- a/content/telegraf/v1.13/data_formats/output/influx.md +++ b/content/telegraf/v1.13/data_formats/output/influx.md @@ -38,4 +38,4 @@ The `influx` output data format outputs metrics into [InfluxDB Line Protocol][li influx_uint_support = false ``` -[line protocol]: /influxdb/latest/write_protocols/line_protocol_tutorial/ +[line protocol]: /{{< latest "influxdb" "v1" >}}/write_protocols/line_protocol_tutorial/ diff --git a/content/telegraf/v1.14/administration/troubleshooting.md b/content/telegraf/v1.14/administration/troubleshooting.md index 5714d4667..6036fa7c7 100644 --- a/content/telegraf/v1.14/administration/troubleshooting.md +++ b/content/telegraf/v1.14/administration/troubleshooting.md @@ -23,7 +23,7 @@ The minimal Telegraf configuration required to enable a UDP output is: urls = ["udp://localhost:8089"] ``` -This setup utilizes the UDP format of the [InfluxDB output plugin](https://github.com/influxdata/telegraf/tree/master/plugins/outputs/influxdb) and emits points formatted in InfluxDB's [line protocol](/influxdb/latest/concepts/glossary/#line-protocol). +This setup utilizes the UDP format of the [InfluxDB output plugin](https://github.com/influxdata/telegraf/tree/master/plugins/outputs/influxdb) and emits points formatted in InfluxDB's [line protocol](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#line-protocol). You will need to append this section to the Telegraf configuration file and restart Telegraf for the change to take effect. Now you are ready to start listening on the destination port (`8089` in this example) using a simple tool like `netcat`: diff --git a/content/telegraf/v1.14/data_formats/input/influx.md b/content/telegraf/v1.14/data_formats/input/influx.md index 117ba822b..498db0b08 100644 --- a/content/telegraf/v1.14/data_formats/input/influx.md +++ b/content/telegraf/v1.14/data_formats/input/influx.md @@ -11,7 +11,7 @@ menu: There are no additional configuration options for InfluxDB [line protocol][]. The InfluxDB metrics are parsed directly into Telegraf metrics. -[line protocol]: /influxdb/latest/write_protocols/line/ +[line protocol]: /{{< latest "influxdb" "v1" >}}/write_protocols/line/ ### Configuration diff --git a/content/telegraf/v1.14/data_formats/output/influx.md b/content/telegraf/v1.14/data_formats/output/influx.md index b8c3200d0..675b01edb 100644 --- a/content/telegraf/v1.14/data_formats/output/influx.md +++ b/content/telegraf/v1.14/data_formats/output/influx.md @@ -38,4 +38,4 @@ The `influx` output data format outputs metrics into [InfluxDB Line Protocol][li influx_uint_support = false ``` -[line protocol]: /influxdb/latest/write_protocols/line_protocol_tutorial/ +[line protocol]: /{{< latest "influxdb" "v1" >}}/write_protocols/line_protocol_tutorial/ diff --git a/content/telegraf/v1.15/administration/troubleshooting.md b/content/telegraf/v1.15/administration/troubleshooting.md index 3088ef4cd..f4792a342 100644 --- a/content/telegraf/v1.15/administration/troubleshooting.md +++ b/content/telegraf/v1.15/administration/troubleshooting.md @@ -23,7 +23,7 @@ The minimal Telegraf configuration required to enable a UDP output is: urls = ["udp://localhost:8089"] ``` -This setup utilizes the UDP format of the [InfluxDB output plugin](https://github.com/influxdata/telegraf/tree/master/plugins/outputs/influxdb) and emits points formatted in InfluxDB's [line protocol](/influxdb/latest/concepts/glossary/#line-protocol). +This setup utilizes the UDP format of the [InfluxDB output plugin](https://github.com/influxdata/telegraf/tree/master/plugins/outputs/influxdb) and emits points formatted in InfluxDB's [line protocol](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#line-protocol). You will need to append this section to the Telegraf configuration file and restart Telegraf for the change to take effect. Now you are ready to start listening on the destination port (`8089` in this example) using a simple tool like `netcat`: diff --git a/content/telegraf/v1.15/data_formats/input/influx.md b/content/telegraf/v1.15/data_formats/input/influx.md index c895c7fc2..3ceb0931e 100644 --- a/content/telegraf/v1.15/data_formats/input/influx.md +++ b/content/telegraf/v1.15/data_formats/input/influx.md @@ -11,7 +11,7 @@ menu: There are no additional configuration options for InfluxDB [line protocol][]. The InfluxDB metrics are parsed directly into Telegraf metrics. -[line protocol]: /influxdb/latest/write_protocols/line/ +[line protocol]: /{{< latest "influxdb" "v1" >}}/write_protocols/line/ ### Configuration diff --git a/content/telegraf/v1.15/data_formats/output/influx.md b/content/telegraf/v1.15/data_formats/output/influx.md index b56d945fe..a0b61ee2e 100644 --- a/content/telegraf/v1.15/data_formats/output/influx.md +++ b/content/telegraf/v1.15/data_formats/output/influx.md @@ -38,4 +38,4 @@ The `influx` output data format outputs metrics into [InfluxDB Line Protocol][li influx_uint_support = false ``` -[line protocol]: /influxdb/latest/write_protocols/line_protocol_tutorial/ +[line protocol]: /{{< latest "influxdb" "v1" >}}/write_protocols/line_protocol_tutorial/ diff --git a/content/telegraf/v1.9/administration/troubleshooting.md b/content/telegraf/v1.9/administration/troubleshooting.md index 983698563..d59881717 100644 --- a/content/telegraf/v1.9/administration/troubleshooting.md +++ b/content/telegraf/v1.9/administration/troubleshooting.md @@ -23,7 +23,7 @@ The minimal Telegraf configuration required to enable a UDP output is: urls = ["udp://localhost:8089"] ``` -This setup utilizes the UDP format of the [InfluxDB output plugin](https://github.com/influxdata/telegraf/tree/master/plugins/outputs/influxdb) and emits points formatted in InfluxDB's [line protocol](/influxdb/latest/concepts/glossary/#line-protocol). +This setup utilizes the UDP format of the [InfluxDB output plugin](https://github.com/influxdata/telegraf/tree/master/plugins/outputs/influxdb) and emits points formatted in InfluxDB's [line protocol](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#line-protocol). You will need to append this section to the Telegraf configuration file and restart Telegraf for the change to take effect. Now you are ready to start listening on the destination port (`8089` in this example) using a simple tool like `netcat`: diff --git a/content/telegraf/v1.9/data_formats/input/influx.md b/content/telegraf/v1.9/data_formats/input/influx.md index 90760c439..3e6c17b52 100644 --- a/content/telegraf/v1.9/data_formats/input/influx.md +++ b/content/telegraf/v1.9/data_formats/input/influx.md @@ -11,7 +11,7 @@ menu: There are no additional configuration options for InfluxDB [line protocol][]. The InfluxDB metrics are parsed directly into Telegraf metrics. -[line protocol]: /influxdb/latest/write_protocols/line/ +[line protocol]: /{{< latest "influxdb" "v1" >}}/write_protocols/line/ ### Configuration diff --git a/content/telegraf/v1.9/data_formats/output/influx.md b/content/telegraf/v1.9/data_formats/output/influx.md index e4b00641a..ac3e885ec 100644 --- a/content/telegraf/v1.9/data_formats/output/influx.md +++ b/content/telegraf/v1.9/data_formats/output/influx.md @@ -38,4 +38,4 @@ The `influx` output data format outputs metrics into [InfluxDB Line Protocol][li influx_uint_support = false ``` -[line protocol]: /influxdb/latest/write_protocols/line_protocol_tutorial/ +[line protocol]: /{{< latest "influxdb" "v1" >}}/write_protocols/line_protocol_tutorial/ diff --git a/content/telegraf/v1.9/plugins/inputs.md b/content/telegraf/v1.9/plugins/inputs.md index e312c52a3..8067d0904 100644 --- a/content/telegraf/v1.9/plugins/inputs.md +++ b/content/telegraf/v1.9/plugins/inputs.md @@ -329,7 +329,7 @@ capturing and storing these metrics locally within the `_internal` database for Plugin ID: `influxdb_listener` The [InfluxDB Listener input plugin](https://github.com/influxdata/telegraf/blob/release-1.9/plugins/inputs/influxdb_listener/README.md) listens for requests sent -according to the [InfluxDB HTTP API](/influxdb/latest/guides/writing_data/). The intent of the +according to the [InfluxDB HTTP API](/{{< latest "influxdb" "v1" >}}/guides/writing_data/). The intent of the plugin is to allow Telegraf to serve as a proxy, or router, for the HTTP `/write` endpoint of the InfluxDB HTTP API. diff --git a/layouts/partials/article/related.html b/layouts/partials/article/related.html index e1962159c..59782e2e9 100644 --- a/layouts/partials/article/related.html +++ b/layouts/partials/article/related.html @@ -4,10 +4,13 @@
    {{ range .Params.related }} + {{ if or (in . "http") (in . "/v2.0/api") }} {{ $link := replaceRE `\,\s(.*)$` "" . }} {{ $title := replaceRE `^(\S*\,\s)` "" . }}
  • {{ $title }}
    • + + {{ else if (in . "{{< latest") }} {{ $product := replaceRE `[ \"]` "" (index (findRE ` \"\w*\"` .) 0) }} {{ $majorVersion := replaceRE `[ \"]` "" (index (findRE ` \"\w*\"` .) 1) }} @@ -25,8 +28,13 @@ {{ $productLatestVersion := $scratch.Get "latestVersion" }} {{ $replaceLatest := replaceRE `\{\{\< latest \".*\" \>\}\}` (print $product "/" $productLatestVersion) . }} + {{ $scratch.Set "title" ""}} + {{ if in $replaceLatest "," }} + {{ $scratch.Set "title" (replaceRE `^.+?, ` "" $replaceLatest) }} + {{ end }} + {{ $link := replaceRE `\,\s(.*)$` "" $replaceLatest }} - {{ $title := replaceRE `^(\S*\,\s)` "" $replaceLatest }} + {{ $title := $scratch.Get "title" }} {{ if gt (len $title) 0 }}
  • {{ $title }}
    • @@ -36,6 +44,8 @@
  • {{ .Title }}
    • {{ end }} {{ end }} + + {{ else }} {{ $sanitizedPath := replaceRE `\/$` "" (print .) }} {{ with $.Page.GetPage $sanitizedPath }} diff --git a/layouts/partials/footer/influxdb-url-modal.html b/layouts/partials/footer/influxdb-url-modal.html index 9b14f0ce5..e66466b5c 100644 --- a/layouts/partials/footer/influxdb-url-modal.html +++ b/layouts/partials/footer/influxdb-url-modal.html @@ -47,7 +47,7 @@ {{ end }} -

    For more information, see InfluxDB URLs.

    +

    For more information, see InfluxDB URLs.

    diff --git a/layouts/shortcodes/latest.html b/layouts/shortcodes/latest.html index 084b34b4e..1a78638c9 100644 --- a/layouts/shortcodes/latest.html +++ b/layouts/shortcodes/latest.html @@ -11,4 +11,4 @@ {{- end -}} {{- end -}} {{- $latestVersion := $scratch.Get "latestVersion" -}} -{{ $product }}/{{ $latestVersion }} +{{ $product }}/{{ $latestVersion }} \ No newline at end of file