Influxdata
/
docs-v2
mirror of https://github.com/influxdata/docs-v2.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Fix broken internal links – SEO link audit (#2189) 

* link audit, remove info about stopping influxd in restore docs, closes #2168

* fixed broken internal links for seo link audit

* updated canonical logic to be smarter

* fixed canonical links and broken images

* fixed errant find and replace

* fixed formatting of kapa event handler docs

* more link fixes

* more link fixes, support latest shortcode in telegraf plugin descriptions
pull/2196/head
Scott Anderson 2021-02-19 11:07:47 -07:00 committed by GitHub
parent 89d354a8c8
commit c1ca5c8408
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
186 changed files with 769 additions and 661 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/chronograf/v1.6/_index.md
View File

@ -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](/{{< latest "influxdb" "v1" >}}/query_language/authentication_and_authorization/#authorization) and InfluxDB Enterprise user management)
* Create, delete, and assign permissions to users (Chronograf supports [InfluxDB OSS 1.x](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#authorization) and InfluxDB Enterprise user management)
### Multi-organization and multi-user support

38
content/chronograf/v1.6/administration/managing-influxdb-users.md
View File

@ -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](/{{< latest "influxdb" "v1" >}}/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" >}}/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 InfluxDB Enterprise data nodes
@ -92,7 +92,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](/{{< latest "influxdb" "v1" >}}/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" >}}/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,13 +156,13 @@ Assign permissions and roles to both admin and non-admin users.
#### AddRemoveNode
Permission to add or remove nodes from a cluster.
**Relevant `influxd-ctl` arguments**:
[`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)
**Relevant `influxd-ctl` commands**:
[`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
@ -170,7 +170,7 @@ Permission to add or remove nodes from a cluster.
Permission to copy shards.
**Relevant `influxd-ctl` arguments**:
[copy-shard](/{{< latest "enterprise_influxdb" >}}/features/cluster-commands/#copy-shard)
[copy-shard](/{{< latest "enterprise_influxdb" >}}/administration/cluster-commands/#copy-shard)
**Pages in Chronograf that require this permission**: NA
@ -189,15 +189,15 @@ Permission to create databases, create [retention policies](/{{< latest "influxd
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`](/{{< 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)
[`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

2
content/chronograf/v1.6/administration/transition-web-admin-interface.md
View File

@ -8,7 +8,7 @@ aliases:
- /chronograf/v1.6/guides/transition-web-admin-interface/
---
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.
Versions 1.3 and later of [InfluxDB](/{{< latest "influxdb" "v1" >}}/) and [InfluxDB Enterprise](/{{< latest "enterprise_influxdb" >}}/) do not support the [web admin interface](https://archive.docs.influxdata.com/influxdb/v1.2/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:

2
content/chronograf/v1.6/guides/analyzing-logs.md
View File

@ -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](/{{< latest "telegraf" >}}/plugins/inputs/):
Logs data is a first class citizen in InfluxDB and is populated using available log-related [Telegraf input plugins](/{{< latest "telegraf" >}}/plugins/#input-plugins):
[syslog](https://github.com/influxdata/telegraf/tree/release-1.7/plugins/inputs/syslog)

2
content/chronograf/v1.6/guides/monitoring-influxenterprise-clusters.md
View File

@ -80,7 +80,7 @@ Next, start the InfluxDB process:
#### Step 4: Create an admin user
Create an [admin user](/{{< latest "influxdb" "v1" >}}/query_language/authentication_and_authorization/#user-types-and-privileges) on your InfluxDB instance.
Create an [admin user](/{{< latest "influxdb" "v1" >}}/administration/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.

2
content/chronograf/v1.7/_index.md
View File

@ -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](/{{< latest "influxdb" "v1" >}}/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 InfluxDB Enterprise user management)
### Multi-organization and multi-user support

2
content/chronograf/v1.7/about_the_project/release-notes-changelog.md
View File

@ -919,7 +919,7 @@ In versions 1.3.1+, installing a new version of Chronograf automatically clears
### Features
* Add line-protocol proxy for InfluxDB/InfluxEnterprise Cluster data sources
* 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/v1.7/guides/advanced-kapacitor/#tickscript-management)
* Allow users to delete Kapacitor configurations

2
content/chronograf/v1.7/administration/chrono-on-clusters.md
View File

@ -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/v1.7/guides/monitoring-influxenterprise-clusters).
For details about monitoring InfluxDB Enterprise clusters, see [Monitoring InfluxDB Enterprise clusters](/chronograf/v1.7/guides/monitoring-influxenterprise-clusters).

2
content/chronograf/v1.7/administration/managing-chronograf-users.md
View File

@ -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] (/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.

10
content/chronograf/v1.7/administration/managing-influxdb-users.md
View File

@ -23,9 +23,9 @@ The **Chronograf Admin** provides InfluxDB user management for InfluxDB OSS and
## Enabling authentication
Follow the steps below to enable authentication.
The steps are the same for InfluxDB OSS instances and InfluxEnterprise clusters.
The steps are the same for InfluxDB OSS instances and InfluxDB Enterprise clusters.
> ***InfluxEnterprise clusters:***
> ***InfluxDB Enterprise clusters:***
> Repeat the first three steps for each data node in a cluster.
### Step 1: Enable authentication.
@ -60,7 +60,7 @@ Restart the InfluxDB service for your configuration changes to take effect:
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
* `localhost` with the IP or hostname of your InfluxDB OSS instance or one of your InfluxDB Enterprise data nodes
* `chronothan` with your own username
* `supersecret` with your own password (note that the password requires single quotes)
@ -273,8 +273,8 @@ Permission to create, drop, and view [subscriptions](/{{< latest "influxdb" "v1"
Permission to view cluster statistics and diagnostics.
**Relevant InfluxQL queries**:
[`SHOW DIAGNOSTICS`](/influxdb/administration/server_monitoring/#show-diagnostics) and
[`SHOW STATS`](/influxdb/administration/server_monitoring/#show-stats)
[`SHOW DIAGNOSTICS`](/{{< latest "influxdb" "v1" >}}/administration/server_monitoring/#show-diagnostics) and
[`SHOW STATS`](/{{< latest "influxdb" "v1" >}}/administration/server_monitoring/#show-stats)
**Pages in Chronograf that require this permission**: Data Explorer, Dashboards

2
content/chronograf/v1.7/administration/managing-security.md
View File

@ -46,7 +46,7 @@ Chronograf will use this secret to generate the JWT Signature for all access tok
TOKEN_SECRET=<mysecret>
```
> ***InfluxEnterprise clusters:*** If you are running multiple Chronograf servers in a high availability configuration,
> ***InfluxDB Enterprise clusters:*** If you are running multiple Chronograf servers in a high availability configuration,
> set the `TOKEN_SECRET` environment variable on each server to ensure that users can stay logged in.
### JWKS Signature Verification (optional)

6
content/chronograf/v1.7/administration/transition-web-admin-interface.md
View File

@ -8,7 +8,7 @@ aliases:
- /chronograf/v1.7/guides/transition-web-admin-interface/
---
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.
Versions 1.3 and later of [InfluxDB](/{{< latest "influxdb" "v1" >}}/) and [InfluxDB Enterprise](/{{< latest "enterprise_influxdb" >}}/) 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:
@ -86,8 +86,8 @@ The `Admin` page allows users to:
* View, create, and delete users
* Change user passwords
* Assign and remove permissions to or from a user
* Create, edit, and delete roles (available in InfluxEnterprise only)
* Assign and remove roles to or from a user (available in InfluxEnterprise only)
* Create, edit, and delete roles (available in InfluxDB Enterprise only)
* Assign and remove roles to or from a user (available in InfluxDB Enterprise only)
![Chronograf User Management i](/img/chronograf/1-6-g-admin-chronousers1.png)

2
content/chronograf/v1.7/guides/analyzing-logs.md
View File

@ -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](/{{< latest "telegraf" >}}/plugins/inputs/):
Logs data is a first class citizen in InfluxDB and is populated using available log-related [Telegraf input plugins](/{{< latest "telegraf" >}}/plugins/#input-plugins):
[syslog](https://github.com/influxdata/telegraf/tree/release-1.7/plugins/inputs/syslog)

12
content/chronograf/v1.7/guides/monitoring-influxenterprise-clusters.md
View File

@ -10,15 +10,15 @@ menu:
---
[InfluxEnterprise](/{{< latest "enterprise_influxdb" >}}/) 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](/{{< latest "influxdb" "v1" >}}/), and [Telegraf](/{{< latest "telegraf" >}}/) 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 InfluxDB Enterprise cluster.
## Requirements
You have a fully-functioning InfluxEnterprise cluster with authentication enabled.
See the InfluxEnterprise documentation for
You have a fully-functioning InfluxDB Enterprise cluster with authentication enabled.
See the InfluxDB Enterprise documentation for
[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.
@ -34,7 +34,7 @@ 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).
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](/{{< 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.
@ -80,7 +80,7 @@ Next, start the InfluxDB process:
#### Step 4: Create an admin user
Create an [admin user](/{{< latest "influxdb" "v1" >}}/query_language/authentication_and_authorization/#user-types-and-privileges) on your InfluxDB instance.
Create an [admin user](/{{< latest "influxdb" "v1" >}}/administration/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.

2
content/chronograf/v1.7/guides/querying-data.md
View File

@ -33,7 +33,7 @@ InfluxQL is a SQL-like query language you can use to interact with data in Influ
## Explore data with Flux
Flux is InfluxData's new functional data scripting language designed for querying, analyzing, and acting on time series data. To learn more about Flux, see [Getting started with Flux](/flux/v0.7/introduction/getting-started).
Flux is InfluxData's new functional data scripting language designed for querying, analyzing, and acting on time series data. To learn more about Flux, see [Getting started with Flux](/{{< latest "influxdb" "v2" >}}/query-data/get-started).
> ***Note:*** Flux v0.7 is a technical preview included with [InfluxDB v1.7](/influxdb/v1.7). It is still in active development and many functions provided by InfluxQL and TICKscript have yet to be implemented.

60
content/chronograf/v1.7/guides/using-precreated-dashboards.md
View File

@ -65,7 +65,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
## apache
**Required Telegraf plugin:** [Apache input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#apache-http-server)
**Required Telegraf plugin:** [Apache input plugin](/{{< latest "telegraf" >}}/plugins/#apache)
`apache.json`
@ -75,7 +75,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
## consul
**Required Telegraf plugin:** [Consul input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#consul)
**Required Telegraf plugin:** [Consul input plugin](/{{< latest "telegraf" >}}/plugins/#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](/{{< latest "telegraf" >}}/plugins/inputs/#docker)
**Required Telegraf plugin:** [Docker input plugin](/{{< latest "telegraf" >}}/plugins/#docker)
`docker.json`
@ -115,7 +115,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
## elasticsearch
**Required Telegraf plugin:** [Elasticsearch input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#elasticsearch)
**Required Telegraf plugin:** [Elasticsearch input plugin](/{{< latest "telegraf" >}}/plugins/#elasticsearch)
`elasticsearch.json`
@ -132,7 +132,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
## haproxy
**Required Telegraf plugin:** [HAProxy input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#haproxy)
**Required Telegraf plugin:** [HAProxy input plugin](/{{< latest "telegraf" >}}/plugins/#haproxy)
`haproxy.json`
@ -154,7 +154,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
## iis
**Required Telegraf plugin:** [Windows Performance Counters input plugin](/telegraf/v1.8/plugins/inputs/#windows-performance-counters)
**Required Telegraf plugin:** [Windows Performance Counters input plugin](/{{< latest "telegraf" >}}/plugins/#win_perf_counters)
`win_websvc.json`
@ -162,7 +162,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
## influxdb
**Required Telegraf plugin:** [InfluxDB input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#influxdb-v-1)
**Required Telegraf plugin:** [InfluxDB input plugin](/{{< latest "telegraf" >}}/plugins/#influxdb)
`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](/{{< latest "telegraf" >}}/plugins/inputs/#memcached)
**Required Telegraf plugin:** [Memcached input plugin](/{{< latest "telegraf" >}}/plugins/#memcached)
`memcached.json`
@ -227,7 +227,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
## mesos
**Required Telegraf plugin:** [Mesos input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#mesos)
**Required Telegraf plugin:** [Mesos input plugin](/{{< latest "telegraf" >}}/plugins/#mesos)
`mesos.json`
@ -242,7 +242,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
## mongodb
**Required Telegraf plugin:** [MongoDB input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#mongodb)
**Required Telegraf plugin:** [MongoDB input plugin](/{{< latest "telegraf" >}}/plugins/#mongodb)
`mongodb.json`
@ -254,7 +254,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
## mysql
**Required Telegraf plugin:** [MySQL input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#mysql)
**Required Telegraf plugin:** [MySQL input plugin](/{{< latest "telegraf" >}}/plugins/#mysql)
`mysql.json`
@ -265,7 +265,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
## nginx
**Required Telegraf plugin:** [NGINX input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#nginx)
**Required Telegraf plugin:** [NGINX input plugin](/{{< latest "telegraf" >}}/plugins/#nginx)
`nginx.json`
@ -276,7 +276,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
## nsq
**Required Telegraf plugin:** [NSQ input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#nsq)
**Required Telegraf plugin:** [NSQ input plugin](/{{< latest "telegraf" >}}/plugins/#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](/{{< latest "telegraf" >}}/plugins/inputs/#php-fpm)
**Required Telegraf plugin:** [PHPfpm input plugin](/{{< latest "telegraf" >}}/plugins/#phpfpm)
`phpfpm.json`
@ -309,7 +309,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
## ping
**Required Telegraf plugin:** [Ping input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#ping)
**Required Telegraf plugin:** [Ping input plugin](/{{< latest "telegraf" >}}/plugins/#ping)
`ping.json`
@ -318,7 +318,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
## postgresql
**Required Telegraf plugin:** [PostgreSQL input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#postgresql)
**Required Telegraf plugin:** [PostgreSQL input plugin](/{{< latest "telegraf" >}}/plugins/#postgresql)
`postgresql.json`
@ -329,7 +329,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
## rabbitmq
**Required Telegraf plugin:** [RabbitMQ input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#rabbitmq)
**Required Telegraf plugin:** [RabbitMQ input plugin](/{{< latest "telegraf" >}}/plugins/#rabbitmq)
`rabbitmq.json`
@ -340,7 +340,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
## redis
**Required Telegraf plugin:** [Redis input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#redis)
**Required Telegraf plugin:** [Redis input plugin](/{{< latest "telegraf" >}}/plugins/#redis)
`redis.json`
@ -352,7 +352,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
## riak
**Required Telegraf plugin:** [Riak input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#riak)
**Required Telegraf plugin:** [Riak input plugin](/{{< latest "telegraf" >}}/plugins/#riak)
`riak.json`
@ -371,7 +371,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
### cpu
**Required Telegraf plugin:** [CPU input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#cpu)
**Required Telegraf plugin:** [CPU input plugin](/{{< latest "telegraf" >}}/plugins/#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](/{{< latest "telegraf" >}}/plugins/inputs/#disk)
**Required Telegraf plugin:** [Disk input plugin](/{{< latest "telegraf" >}}/plugins/#disk)
* "System - Disk used %"
### diskio
**Required Telegraf plugin:** [DiskIO input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#diskio)
**Required Telegraf plugin:** [DiskIO input plugin](/{{< latest "telegraf" >}}/plugins/#diskio)
`diskio.json`
@ -396,7 +396,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
### mem
**Required Telegraf plugin:** [Mem input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#mem)
**Required Telegraf plugin:** [Mem input plugin](/{{< latest "telegraf" >}}/plugins/#mem)
`mem.json`
@ -404,7 +404,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
### net
**Required Telegraf plugin:** [Net input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#net)
**Required Telegraf plugin:** [Net input plugin](/{{< latest "telegraf" >}}/plugins/#net)
`net.json`
@ -413,7 +413,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
### netstat
**Required Telegraf plugin:** [Netstat input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#netstat)
**Required Telegraf plugin:** [Netstat input plugin](/{{< latest "telegraf" >}}/plugins/#netstat)
`netstat.json`
@ -422,7 +422,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
### processes
**Required Telegraf plugin:** [Processes input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#processes)
**Required Telegraf plugin:** [Processes input plugin](/{{< latest "telegraf" >}}/plugins/#processes)
`processes.json`
@ -430,7 +430,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
### procstat
**Required Telegraf plugin:** [Procstat input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#procstat)
**Required Telegraf plugin:** [Procstat input plugin](/{{< latest "telegraf" >}}/plugins/#procstat)
`procstat.json`
@ -439,7 +439,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
### system
**Required Telegraf plugin:** [Procstat input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#procstat)
**Required Telegraf plugin:** [Procstat input plugin](/{{< latest "telegraf" >}}/plugins/#procstat)
`load.json`
@ -447,7 +447,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
## varnish
**Required Telegraf plugin:** [Varnish](/{{< latest "telegraf" >}}/plugins/inputs/#varnish)
**Required Telegraf plugin:** [Varnish](/{{< latest "telegraf" >}}/plugins/#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](/{{< latest "telegraf" >}}/plugins/inputs/#windows-performance-counters)
**Required Telegraf plugin:** [Windows Performance Counters input plugin](/{{< latest "telegraf" >}}/plugins/#win_perf_counters)
`win_cpu.json`

2
content/chronograf/v1.7/introduction/installation.md
View File

@ -72,7 +72,7 @@ sudo yum localinstall chronograf-<version#>.x86_64.rpm
2. Fill out the form with the following details:
* **Connection String**: Enter the hostname or IP of the machine that InfluxDB is running on, and be sure to include InfluxDB's default port `8086`.
* **Connection Name**: Enter a name for your connection string.
* **Username** and **Password**: These fields can remain blank unless you've [enabled authentication](/influxdb/v1.7/administration/authentication_and_authorization.md) in InfluxDB.
* **Username** and **Password**: These fields can remain blank unless you've [enabled authentication](/influxdb/v1.7/administration/authentication_and_authorization) in InfluxDB.
* **Telegraf Database Name**: Optionally, enter a name for your Telegraf database. The default name is Telegraf.
3. Click **Add Source**.

6
content/chronograf/v1.7/troubleshooting/frequently-asked-questions.md
View File

@ -7,9 +7,9 @@ menu:
parent: Troubleshooting
---
## How do I connect Chronograf to an InfluxEnterprise cluster?
## How do I connect Chronograf to an InfluxDB Enterprise cluster?
The connection details form requires additional information when connecting Chronograf to an [InfluxEnterprise cluster](/{{< latest "enterprise_influxdb" >}}/).
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 InfluxEnterprise cluster, see the [Monitor an InfluxEnterprise Cluster](/chronograf/v1.7/guides/monitoring-influxenterprise-clusters/) guide.
For more details about monitoring an InfluxDB Enterprise cluster, see the [Monitor an InfluxDB Enterprise Cluster](/chronograf/v1.7/guides/monitoring-influxenterprise-clusters/) guide.

2
content/chronograf/v1.8/_index.md
View File

@ -42,7 +42,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](/{{< latest "influxdb" "v1" >}}/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 InfluxDB Enterprise user management)
### Multi-organization and multi-user support

4
content/chronograf/v1.8/about_the_project/release-notes-changelog.md
View File

@ -155,7 +155,7 @@ TLS1.2 is now the default minimum required TLS version. If you have clients that
### Features
- Update to [Flux v0.65.0](/flux/v0.65/about_the_project/releasenotes-changelog/#v0-65-0-2020-03-27).
- Update to Flux v0.65.0.
### Bug Fixes
@ -1112,7 +1112,7 @@ In versions 1.3.1+, installing a new version of Chronograf automatically clears
### Features
* Add line-protocol proxy for InfluxDB/InfluxEnterprise Cluster data sources
* 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/v1.8/guides/advanced-kapacitor/#tickscript-management)
* Allow users to delete Kapacitor configurations

2
content/chronograf/v1.8/administration/chrono-on-clusters.md
View File

@ -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/v1.8/guides/monitoring-influxenterprise-clusters).
For details about monitoring InfluxDB Enterprise clusters, see [Monitoring InfluxDB Enterprise clusters](/chronograf/v1.8/guides/monitoring-influxenterprise-clusters).

2
content/chronograf/v1.8/administration/managing-chronograf-users.md
View File

@ -32,7 +32,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] (/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 permission. In an organization, admins (with the `admin` role) or users with SuperAdmin permission can create, update, and assign roles to a user or remove a role assignment.

10
content/chronograf/v1.8/administration/managing-influxdb-users.md
View File

@ -32,9 +32,9 @@ interfaces, CLIs, or APIs to complete administrative tasks.
## Enable authentication
Follow the steps below to enable authentication.
The steps are the same for InfluxDB OSS instances and InfluxEnterprise clusters.
The steps are the same for InfluxDB OSS instances and InfluxDB Enterprise clusters.
> ***InfluxEnterprise clusters:***
> ***InfluxDB Enterprise clusters:***
> Repeat the first three steps for each data node in a cluster.
### Step 1: Enable authentication.
@ -69,7 +69,7 @@ Restart the InfluxDB service for your configuration changes to take effect:
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
* `localhost` with the IP or hostname of your InfluxDB OSS instance or one of your InfluxDB Enterprise data nodes
* `chronothan` with your own username
* `supersecret` with your own password (note that the password requires single quotes)
@ -282,8 +282,8 @@ Permission to create, drop, and view [subscriptions](/{{< latest "influxdb" "v1"
Permission to view cluster statistics and diagnostics.
**Relevant InfluxQL queries**:
[`SHOW DIAGNOSTICS`](/influxdb/administration/server_monitoring/#show-diagnostics) and
[`SHOW STATS`](/influxdb/administration/server_monitoring/#show-stats)
[`SHOW DIAGNOSTICS`](/{{< latest "influxdb" "v1" >}}/administration/server_monitoring/#show-diagnostics) and
[`SHOW STATS`](/{{< latest "influxdb" "v1" >}}/administration/server_monitoring/#show-stats)
**Pages in Chronograf that require this permission**: Data Explorer, Dashboards

2
content/chronograf/v1.8/administration/managing-security.md
View File

@ -49,7 +49,7 @@ Chronograf will use this secret to generate the JWT Signature for all access tok
```
{{% note %}}
***InfluxEnterprise clusters:*** If you are running multiple Chronograf servers in a high availability configuration,
***InfluxDB Enterprise clusters:*** If you are running multiple Chronograf servers in a high availability configuration,
set the `TOKEN_SECRET` environment variable on each server to ensure that users can stay logged in.
{{% /note %}}

2
content/chronograf/v1.8/guides/analyzing-logs.md
View File

@ -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](/{{< latest "telegraf" >}}/plugins/inputs/):
Logs data is a first class citizen in InfluxDB and is populated using available log-related [Telegraf input plugins](/{{< latest "telegraf" >}}/plugins/#input-plugins):
[syslog](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/syslog)

12
content/chronograf/v1.8/guides/monitoring-influxenterprise-clusters.md
View File

@ -10,15 +10,15 @@ menu:
---
[InfluxEnterprise](/{{< latest "enterprise_influxdb" >}}/) 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](/{{< latest "influxdb" "v1" >}}/), and [Telegraf](/{{< latest "telegraf" >}}/) 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 InfluxDB Enterprise cluster.
## Requirements
You have a fully-functioning InfluxEnterprise cluster with authentication enabled.
See the InfluxEnterprise documentation for
You have a fully-functioning InfluxDB Enterprise cluster with authentication enabled.
See the InfluxDB Enterprise documentation for
[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.
@ -34,7 +34,7 @@ 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).
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](/{{< 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.
@ -80,7 +80,7 @@ Next, start the InfluxDB process:
#### Step 4: Create an admin user
Create an [admin user](/{{< latest "influxdb" "v1" >}}/query_language/authentication_and_authorization/#user-types-and-privileges) on your InfluxDB instance.
Create an [admin user](/{{< latest "influxdb" "v1" >}}/administration/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.

2
content/chronograf/v1.8/guides/querying-data.md
View File

@ -42,7 +42,7 @@ For more information, see [InfluxQL support](/influxdb/cloud/query-data/influxql
## Explore data with Flux
Flux is InfluxData's new functional data scripting language designed for querying, analyzing, and acting on time series data. To learn more about Flux, see [Getting started with Flux](/flux/v0.7/introduction/getting-started).
Flux is InfluxData's new functional data scripting language designed for querying, analyzing, and acting on time series data. To learn more about Flux, see [Getting started with Flux](/{{< latest "influxdb" "v2" >}}/query-data/get-started).
1. Open the Data Explorer and click **Add a Query**.
2. To the right of the source dropdown above the graph placeholder, select **Flux** as the source type.

6
content/chronograf/v1.8/troubleshooting/frequently-asked-questions.md
View File

@ -8,9 +8,9 @@ menu:
parent: Troubleshoot
---
## How do I connect Chronograf to an InfluxEnterprise cluster?
## How do I connect Chronograf to an InfluxDB Enterprise cluster?
The connection details form requires additional information when connecting Chronograf to an [InfluxEnterprise cluster](/{{< latest "enterprise_influxdb" >}}/).
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.
@ -20,4 +20,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/v1.8/guides/monitoring-influxenterprise-clusters/) guide.
For more details about monitoring an InfluxDB Enterprise cluster, see the [Monitor an InfluxDB Enterprise Cluster](/chronograf/v1.8/guides/monitoring-influxenterprise-clusters/) guide.

2
content/enterprise_influxdb/v1.5/administration/backup-and-restore.md
View File

@ -317,7 +317,7 @@ Restored from my-incremental-backup/ in 66.715524ms, transferred 588800 bytes
In this example, our `telegraf` database was mistakenly dropped, but you have a recent backup so you've only lost a small amount of data.
If [Telegraf](/telegraf/v1.5/) is still running, it will recreate the `telegraf` database shortly after the database is dropped.
If [Telegraf](/{{< latest "telegraf" >}}/) is still running, it will recreate the `telegraf` database shortly after the database is dropped.
You might try to directly restore your `telegraf` backup just to find that you can't restore.
```

12
content/enterprise_influxdb/v1.5/administration/cluster-commands.md
View File

@ -153,7 +153,7 @@ Error: authorization failed.
Adds a data node to a cluster.
By default, `influxd-ctl` adds the specified data node to the local meta node's cluster.
Use `add-data` instead of the [`join` argument](#join) when performing a [production installation](/enterprise_influxdb/v1.5/production_installation/data_node_installation/) of an InfluxEnterprise cluster.
Use `add-data` instead of the [`join` argument](#join) when performing a [production installation](/enterprise_influxdb/v1.5/production_installation/data_node_installation/) of an InfluxDB Enterprise cluster.
#### Syntax
@ -191,7 +191,7 @@ Added data node 3 at cluster-data-node:8088
Adds a meta node to a cluster.
By default, `influxd-ctl` adds the specified meta node to the local meta node's cluster.
Use `add-meta` instead of the [`join` argument](#join) when performing a [Production Installation](/enterprise_influxdb/v1.5/production_installation/meta_node_installation/) of an InfluxEnterprise cluster.
Use `add-meta` instead of the [`join` argument](#join) when performing a [Production Installation](/enterprise_influxdb/v1.5/production_installation/meta_node_installation/) of an InfluxDB Enterprise cluster.
Resources: [Production installation](/enterprise_influxdb/v1.5/production_installation/data_node_installation/)
@ -368,7 +368,7 @@ cluster-data-node-02:8088 cluster-data-node-03:8088 telegraf autogen 34
Joins a meta node and/or data node to a cluster.
By default, `influxd-ctl` joins the local meta node and/or data node into a new cluster.
Use `join` instead of the [`add-meta`](#add-meta) or [`add-data`](#add-data) arguments when performing a [QuickStart Installation](/enterprise_influxdb/v1.5/quickstart_installation/cluster_installation/) of an InfluxEnterprise cluster.
Use `join` instead of the [`add-meta`](#add-meta) or [`add-data`](#add-data) arguments when performing a [QuickStart Installation](/enterprise_influxdb/v1.5/quickstart_installation/cluster_installation/) of an InfluxDB Enterprise cluster.
#### Syntax
@ -507,7 +507,7 @@ Killed shard copy 39 from cluster-data-node-02:8088 to cluster-data-node-03:8088
### `leave`
Removes a meta node and/or data node from the cluster.
Use `leave` instead of the [`remove-meta`](#remove-meta) and [`remove-data`](#remove-data) arguments if you set up your InfluxEnterprise cluster with the [QuickStart Installation](/enterprise_influxdb/v1.5/quickstart_installation/cluster_installation/) process.
Use `leave` instead of the [`remove-meta`](#remove-meta) and [`remove-data`](#remove-data) arguments if you set up your InfluxDB Enterprise cluster with the [QuickStart Installation](/enterprise_influxdb/v1.5/quickstart_installation/cluster_installation/) process.
{{% warn %}}The `leave` argument is destructive; it erases all metastore information from meta nodes and all data from data nodes.
Use `leave` only if you want to *permanently* remove a node from a cluster.
@ -589,7 +589,7 @@ Successfully left cluster
### `remove-data`
Removes a data node from a cluster.
Use `remove-data` instead of the [`leave`](#leave) argument if you set up your InfluxEnterprise cluster with the [Production Installation](/enterprise_influxdb/v1.5/production_installation/) process.
Use `remove-data` instead of the [`leave`](#leave) argument if you set up your InfluxDB Enterprise cluster with the [Production Installation](/enterprise_influxdb/v1.5/production_installation/) process.
{{% warn %}}The `remove-data` argument is destructive; it erases all data from the specified data node.
Use `remove-data` only if you want to *permanently* remove a data node from a cluster.
@ -624,7 +624,7 @@ Removed data node at cluster-data-node-03:8088
### `remove-meta`
Removes a meta node from the cluster.
Use `remove-meta` instead of the [`leave`](#leave) command if you set up your InfluxEnterprise cluster with the [Production Installation](/enterprise_influxdb/v1.5/production_installation/) process.
Use `remove-meta` instead of the [`leave`](#leave) command if you set up your InfluxDB Enterprise cluster with the [Production Installation](/enterprise_influxdb/v1.5/production_installation/) process.
{{% warn %}}The `remove-meta` argument is destructive; it erases all metastore information from the specified meta node.
Use `remove-meta` only if you want to *permanently* remove a meta node from a cluster.

8
content/enterprise_influxdb/v1.5/administration/configuration.md
View File

@ -194,7 +194,7 @@ Environment variable: `INFLUXDB_HOSTNAME`
## [enterprise]
The `[enterprise]` section contains the parameters for the meta node's
registration with the [InfluxEnterprise License Portal](https://portal.influxdata.com/).
registration with the [InfluxDB Enterprise License Portal](https://portal.influxdata.com/).
### license-key = ""
@ -457,7 +457,7 @@ Environment variable: `INFLUXDB_GOSSIP_FREQUENCY`
## [enterprise]
The `[enterprise]` section contains the parameters for the meta node's
registration with the [InfluxEnterprise License Portal](https://portal.influxdata.com/).
registration with the [InfluxDB Enterprise License Portal](https://portal.influxdata.com/).
### license-key = ""
@ -767,7 +767,7 @@ Environment variable: `INFLUXDB_SHARD_PRECREATION_ADVANCE_PERIOD`
By default, InfluxDB writes system monitoring data to the `_internal` database. If that database does not exist, InfluxDB creates it automatically. The `DEFAULT` retention policy on the `internal` database is seven days. To change the default seven-day retention policy, you must [create](/influxdb/v1.5/query_language/database_management/#retention-policy-management) it.
For InfluxDB Enterprise production systems, InfluxData recommends including a dedicated InfluxDB (OSS) monitoring instance for monitoring InfluxEnterprise cluster nodes.
For InfluxDB Enterprise production systems, InfluxData recommends including a dedicated InfluxDB (OSS) monitoring instance for monitoring InfluxDB Enterprise cluster nodes.
* On the dedicated InfluxDB monitoring instance, set `store-enabled = false` to avoid potential performance and storage issues.
* On each InfluxDB cluster node, install a Telegraf input plugin and Telegraf output plugin configured to report data to the dedicated InfluxDB monitoring instance.
@ -909,7 +909,7 @@ Environment variable: `INFLUXDB_HTTP_MAX_CONNECTION_LIMIT`
See the [InfluxDB OSS documentation](/influxdb/v1.5/administration/config/#shared-secret).
This setting is required and must match on each data node if the cluster is using the InfluxEnterprise Web Console.
This setting is required and must match on each data node if the cluster is using the InfluxDB Enterprise Web Console.
Environment variable: `INFLUXDB_HTTP_SHARED_SECRET`

2
content/enterprise_influxdb/v1.5/administration/security.md
View File

@ -40,7 +40,7 @@ Resources:
## Secure your Host
### Ports
For InfluxEnterprise Data Nodes, close all ports on each host except for port `8086`.
For InfluxDB Enterprise Data Nodes, close all ports on each host except for port `8086`.
You can also use a proxy to port `8086`. By default, data nodes and meta nodes communicate with each other over '8088','8089',and'8091'
For InfluxDB Enterprise, [backuping and restoring](/enterprise_influxdb/v1.5/administration/backup-and-restore/) is performed from the meta nodes.

2
content/enterprise_influxdb/v1.5/administration/upgrading.md
View File

@ -231,4 +231,4 @@ rk-upgrading-03:8091 1.5.4_c1.5.4
```
If you have any issues upgrading your cluster, please do not hesitate to contact InfluxData Support at the email address
provided to you when you received your InfluxEnterprise license.
provided to you when you received your InfluxDB Enterprise license.

8
content/enterprise_influxdb/v1.5/concepts/clustering.md
View File

@ -9,11 +9,11 @@ menu:
parent: Concepts
---
This document describes in detail how clustering works in InfluxEnterprise. It starts with a high level description of the different components of a cluster and then delves into the implementation details.
This document describes in detail how clustering works in InfluxDB Enterprise. It starts with a high level description of the different components of a cluster and then delves into the implementation details.
## Architectural overview
An InfluxEnterprise installation consists of three separate software processes: Data nodes, Meta nodes, and the Enterprise Web server. To run an InfluxDB cluster, only the meta and data nodes are required. Communication within a cluster looks like this:
An InfluxDB Enterprise installation consists of three separate software processes: Data nodes, Meta nodes, and the Enterprise Web server. To run an InfluxDB cluster, only the meta and data nodes are required. Communication within a cluster looks like this:
{{< diagram >}}
flowchart TB
@ -66,7 +66,7 @@ On disk, the data is always organized by `<database>/<retention_policy>/<shard_i
## Optimal server counts
When creating a cluster you'll need to choose how meta and data nodes to configure and connect. You can think of InfluxEnterprise as two separate clusters that communicate with each other: a cluster of meta nodes and one of data nodes. The number of meta nodes is driven by the number of meta node failures they need to be able to handle, while the number of data nodes scales based on your storage and query needs.
When creating a cluster you'll need to choose how meta and data nodes to configure and connect. You can think of InfluxDB Enterprise as two separate clusters that communicate with each other: a cluster of meta nodes and one of data nodes. The number of meta nodes is driven by the number of meta node failures they need to be able to handle, while the number of data nodes scales based on your storage and query needs.
The consensus protocol requires a quorum to perform any operation, so there should always be an odd number of meta nodes. For almost all use cases, 3 meta nodes is the correct number, and such a cluster operates normally even with the permanant loss of 1 meta node.
@ -116,7 +116,7 @@ The important thing to note is how failures are handled. In the case of failures
### Hinted handoff
Hinted handoff is how InfluxEnterprise deals with data node outages while writes are happening. Hinted handoff is essentially a durable disk based queue. When writing at `any`, `one` or `quorum` consistency, hinted handoff is used when one or more replicas return an error after a success has already been returned to the client. When writing at `all` consistency, writes cannot return success unless all nodes return success. Temporarily stalled or failed writes may still go to the hinted handoff queues but the cluster would have already returned a failure response to the write. The receiving node creates a separate queue on disk for each data node (and shard) it cannot reach.
Hinted handoff is how InfluxDB Enterprise deals with data node outages while writes are happening. Hinted handoff is essentially a durable disk based queue. When writing at `any`, `one` or `quorum` consistency, hinted handoff is used when one or more replicas return an error after a success has already been returned to the client. When writing at `all` consistency, writes cannot return success unless all nodes return success. Temporarily stalled or failed writes may still go to the hinted handoff queues but the cluster would have already returned a failure response to the write. The receiving node creates a separate queue on disk for each data node (and shard) it cannot reach.
Let's again use the example of a write coming to `D` that should go to shard `1` on `A` and `B`. If we specified a consistency level of `one` and node `A` returns success, `D` immediately returns success to the client even though the write to `B` is still in progress.

4
content/enterprise_influxdb/v1.5/concepts/glossary.md
View File

@ -70,8 +70,8 @@ query capacity within the cluster.
## web console
Legacy user interface for the InfluxEnterprise cluster.
Legacy user interface for the InfluxDB Enterprise cluster.
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](/{{< latest "chronograf" >}}/guides/transition-web-admin-interface/) is available.
If you are transitioning from the Enterprise Web Console to Chronograf, see how to [transition from the InfluxDB Web Admin Interface](/chronograf/v1.7/guides/transition-web-admin-interface/).

6
content/enterprise_influxdb/v1.5/features/users.md
View File

@ -43,7 +43,7 @@ view Chronograf.
Roles are groups of permissions.
A single role can belong to several cluster accounts.
InfluxEnterprise clusters have two built-in roles:
InfluxDB Enterprise clusters have two built-in roles:
#### Global Admin
@ -60,7 +60,7 @@ permissions to:
* Rebalance
### Permissions
InfluxEnterprise clusters have 16 permissions:
InfluxDB Enterprise clusters have 16 permissions:
#### View Admin
Permission to view or edit admin screens.
@ -114,7 +114,7 @@ The following table describes permissions required to execute the associated dat
|Determined by type of select statement|SelectStatement|
### Statement to Permission
The following table describes database statements and the permissions required to execute them. It also describes whether these permissions apply just to InfluxDB (Database) or InfluxEnterprise (Cluster).
The following table describes database statements and the permissions required to execute them. It also describes whether these permissions apply just to InfluxDB (Database) or InfluxDB Enterprise (Cluster).
|Statment|Permissions|Scope|
|---|---|---|

50
content/enterprise_influxdb/v1.5/guides/https_setup.md
View File

@ -8,30 +8,30 @@ menu:
---
This guide describes how to enable HTTPS for InfluxDB Enterprise.
Setting up HTTPS secures the communication between clients and the InfluxEnterprise
Setting up HTTPS secures the communication between clients and the InfluxDB Enterprise
server,
and, in some cases, HTTPS verifies the authenticity of the InfluxEnterprise server to
and, in some cases, HTTPS verifies the authenticity of the InfluxDB Enterprise server to
clients.
If you plan on sending requests to InfluxEnterprise over a network, we
If you plan on sending requests to InfluxDB Enterprise over a network, we
[strongly recommend](/enterprise_influxdb/v1.5/administration/security/)
that you set up HTTPS.
## Requirements
To set up HTTPS with InfluxEnterprise, you'll need an existing or new InfluxEnterprise instance
To set up HTTPS with InfluxDB Enterprise, you'll need an existing or new InfluxDB Enterprise instance
and a Transport Layer Security (TLS) certificate (also known as a Secured Sockets Layer (SSL) certificate).
InfluxEnterprise supports three types of TLS/SSL certificates:
InfluxDB Enterprise supports three types of TLS/SSL certificates:
* **Single domain certificates signed by a [Certificate Authority](https://en.wikipedia.org/wiki/Certificate_authority)**
These certificates provide cryptographic security to HTTPS requests and allow clients to verify the identity of the InfluxEnterprise server.
With this certificate option, every InfluxEnterprise instance requires a unique single domain certificate.
These certificates provide cryptographic security to HTTPS requests and allow clients to verify the identity of the InfluxDB Enterprise server.
With this certificate option, every InfluxDB Enterprise instance requires a unique single domain certificate.
* **Wildcard certificates signed by a Certificate Authority**
These certificates provide cryptographic security to HTTPS requests and allow clients to verify the identity of the InfluxDB server.
Wildcard certificates can be used across multiple InfluxEnterprise instances on different servers.
Wildcard certificates can be used across multiple InfluxDB Enterprise instances on different servers.
* **Self-signed certificates**
@ -39,13 +39,13 @@ InfluxEnterprise supports three types of TLS/SSL certificates:
Unlike CA-signed certificates, self-signed certificates only provide cryptographic security to HTTPS requests.
They do not allow clients to verify the identity of the InfluxDB server.
We recommend using a self-signed certificate if you are unable to obtain a CA-signed certificate.
With this certificate option, every InfluxEnterprise instance requires a unique self-signed certificate.
With this certificate option, every InfluxDB Enterprise instance requires a unique self-signed certificate.
Regardless of your certificate's type, InfluxEnterprise supports certificates composed of
Regardless of your certificate's type, InfluxDB Enterprise supports certificates composed of
a private key file (`.key`) and a signed certificate file (`.crt`) file pair, as well as certificates
that combine the private key file and the signed certificate file into a single bundled file (`.pem`).
The following two sections outline how to set up HTTPS with InfluxEnterprise [using a CA-signed
The following two sections outline how to set up HTTPS with InfluxDB Enterprise [using a CA-signed
certificate](#setup-https-with-a-ca-signed-certificate) and [using a self-signed certificate](#setup-https-with-a-self-signed-certificate)
on Ubuntu 16.04.
Specific steps may be different for other operating systems.
@ -130,14 +130,14 @@ Second, Configure the Data Nodes to use HTTPS when communicating with the Meta N
meta-tls-enabled = true
```
#### Step 5: Restart InfluxEnterprise
#### Step 5: Restart InfluxDB Enterprise
Restart the InfluxEnterprise meta node processes for the configuration changes to take effect:
Restart the InfluxDB Enterprise meta node processes for the configuration changes to take effect:
```
sudo systemctl start influxdb-meta
```
Restart the InfluxEnterprise data node processes for the configuration changes to take effect:
Restart the InfluxDB Enterprise data node processes for the configuration changes to take effect:
```
sudo systemctl restart influxdb
```
@ -169,7 +169,7 @@ enterprise-meta-03:8091 1.x.y-c1.x.z
```
Next, verify that HTTPS is working by connecting to InfluxEnterprise with the [CLI tool](/influxdb/v1.5/tools/shell/):
Next, verify that HTTPS is working by connecting to InfluxDB Enterprise with the [CLI tool](/influxdb/v1.5/tools/shell/):
```
influx -ssl -host <domain_name>.com
```
@ -181,7 +181,7 @@ InfluxDB shell version: 1.x.y
>
```
That's it! You've successfully set up HTTPS with InfluxEnterprise.
That's it! You've successfully set up HTTPS with InfluxDB Enterprise.
## Setup HTTPS with a Self-Signed Certificate
@ -189,7 +189,7 @@ That's it! You've successfully set up HTTPS with InfluxEnterprise.
The following command generates a private key file (`.key`) and a self-signed
certificate file (`.crt`) which remain valid for the specified `NUMBER_OF_DAYS`.
It outputs those files to InfluxEnterprise's default certificate file paths and gives them
It outputs those files to InfluxDB Enterprise's default certificate file paths and gives them
the required permissions.
```
@ -273,14 +273,14 @@ Second, Configure the Data Nodes to use HTTPS when communicating with the Meta N
meta-insecure-tls = true
```
#### Step 4: Restart InfluxEnterprise
#### Step 4: Restart InfluxDB Enterprise
Restart the InfluxEnterprise meta node processes for the configuration changes to take effect:
Restart the InfluxDB Enterprise meta node processes for the configuration changes to take effect:
```
sudo systemctl restart influxdb-meta
```
Restart the InfluxEnterprise data node processes for the configuration changes to take effect:
Restart the InfluxDB Enterprise data node processes for the configuration changes to take effect:
```
sudo systemctl restart influxdb
```
@ -312,7 +312,7 @@ enterprise-meta-03:8091 1.x.y-c1.x.z
```
Next, verify that HTTPS is working by connecting to InfluxEnterprise with the [CLI tool](/influxdb/v1.5/tools/shell/):
Next, verify that HTTPS is working by connecting to InfluxDB Enterprise with the [CLI tool](/influxdb/v1.5/tools/shell/):
```
influx -ssl -unsafeSsl -host <domain_name>.com
```
@ -324,12 +324,12 @@ InfluxDB shell version: 1.x.y
>
```
That's it! You've successfully set up HTTPS with InfluxEnterprise.
That's it! You've successfully set up HTTPS with InfluxDB Enterprise.
## Connect Telegraf to a secured InfluxEnterprise instance
## Connect Telegraf to a secured InfluxDB Enterprise instance
Connecting [Telegraf](/telegraf/v1.5/) to an InfluxEnterprise 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`
@ -348,7 +348,7 @@ setting and set it to `true`.
# Configuration for influxdb server to send metrics to
[[outputs.influxdb]]
## The full HTTP or UDP endpoint URL for your InfluxEnterprise instance.
## The full HTTP or UDP endpoint URL for your InfluxDB Enterprise instance.
## Multiple urls can be specified as part of the same cluster,
## this means that only ONE of the urls will be written to each interval.
# urls = ["udp://localhost:8089"] # UDP endpoint example

8
content/enterprise_influxdb/v1.5/guides/migration.md
View File

@ -32,16 +32,16 @@ of three or more meta nodes and zero or more data nodes. If you need instruction
Please note that this migration process:
* Deletes all data from any data nodes that are already part of the InfluxDB Enterprise cluster
* Will transfer all users from the OSS instance to the InfluxEnterprise Cluster*
* Will transfer all users from the OSS instance to the InfluxDB Enterprise Cluster*
* Requires downtime for writes and reads for the OSS instance
{{% warn %}}
If you're using an InfluxDB Enterprise cluster version prior to 0.7.4, the
following steps will **not** transfer users from the OSS instance to the
InfluxEnterprise Cluster.
InfluxDB Enterprise Cluster.
{{% /warn %}}
In addition, please refrain from creating a Global Admin user in the InfluxEnterprise Web Console before implementing these steps. If you’ve already created a Global Admin user, contact InfluxData Support.
In addition, please refrain from creating a Global Admin user in the InfluxDB Enterprise Web Console before implementing these steps. If you’ve already created a Global Admin user, contact InfluxData Support.
## Modify the `/etc/hosts` file
@ -184,7 +184,7 @@ Note: it may take a few minutes before the existing data become available in the
### 1. Add any data nodes that you removed from cluster back into the cluster
From a **meta** node in the InfluxEnterprise Cluster, run:
From a **meta** node in the InfluxDB Enterprise Cluster, run:
```
influxd-ctl add-data <the-hostname>:8088
```

2
content/enterprise_influxdb/v1.5/introduction/getting-started.md
View File

@ -10,7 +10,7 @@ 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](/{{< latest "chronograf" >}}/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/monitoring-influxenterprise-cluster/monitoring-influxenterprise-cluster/monitoring-influxenterprise-cluster/).
See [Getting started with Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/) to learn more about using Chronograf with the InfluxData time series platform.

4
content/enterprise_influxdb/v1.5/introduction/installation_guidelines.md
View File

@ -46,13 +46,13 @@ If you alter the default ports in the configuration file(s), ensure the configur
#### Synchronize time between hosts
InfluxEnterprise uses hosts' local time in UTC to assign timestamps to data and for coordination purposes.
InfluxDB Enterprise uses hosts' local time in UTC to assign timestamps to data and for coordination purposes.
Use the Network Time Protocol (NTP) to synchronize time between hosts.
#### Use SSDs
Clusters require sustained availability of 1000-2000 IOPS from the attached storage.
SANs must guarantee at least 1000 IOPS is always available to InfluxEnterprise
SANs must guarantee at least 1000 IOPS is always available to InfluxDB Enterprise
nodes or they may not be sufficient.
SSDs are strongly recommended, and we have had no reports of IOPS contention from any customers running on SSDs.

6
content/enterprise_influxdb/v1.5/production_installation/_index.md
View File

@ -8,9 +8,9 @@ menu:
---
The Production Installation process is designed for users looking to deploy
InfluxEnterprise in a production environment.
InfluxDB Enterprise in a production environment.
If you wish to evaluate InfluxEnterprise in a non-production
If you wish to evaluate InfluxDB Enterprise in a non-production
environment, feel free to follow the instructions outlined in the
[QuickStart installation](/enterprise_influxdb/v1.5/quickstart_installation) section.
Please note that if you install InfluxDB Enterprise with the QuickStart Installation process you
@ -20,6 +20,6 @@ process before using the product in a production environment.
## Production installation
Follow the links below to get up and running with InfluxEnterprise.
Follow the links below to get up and running with InfluxDB Enterprise.
{{< children hlevel="h2" >}}

6
content/enterprise_influxdb/v1.5/quickstart_installation/_index.md
View File

@ -8,19 +8,19 @@ menu:
---
The QuickStart installation process is designed for users looking to quickly
get up and running with InfluxEnterprise and for users who are looking to
get up and running with InfluxDB Enterprise and for users who are looking to
evaluate the product.
The QuickStart installation process **is not** designed for use
in a production environment.
Follow the instructions outlined in the [Production installation](/enterprise_influxdb/v1.5/production_installation/) section
if you wish to use InfluxDB Enterprise in a production environment.
Please note that if you install InfluxEnterprise with the QuickStart Installation process you
Please note that if you install InfluxDB Enterprise with the QuickStart Installation process you
will need to reinstall InfluxDB Enterprise with the Production Installation
process before using the product in a production environment.
## QuickStart installation
Follow the links below to get up and running with InfluxEnterprise.
Follow the links below to get up and running with InfluxDB Enterprise.
{{< children hlevel="h2" >}}

2
content/enterprise_influxdb/v1.5/quickstart_installation/cluster_installation.md
View File

@ -55,7 +55,7 @@ setting in the meta node and data node configuration files.
#### Load balancer
InfluxEnterprise does not function as a load balancer.
InfluxDB Enterprise does not function as a load balancer.
You will need to configure your own load balancer to send client traffic to the
data nodes on port `8086` (the default port for the [HTTP API](/influxdb/v1.5/tools/api/)).

2
content/enterprise_influxdb/v1.5/troubleshooting/frequently_asked_questions.md
View File

@ -81,7 +81,7 @@ Note that for some [write consistency](/enterprise_influxdb/v1.5/concepts/cluste
[stats] 2016/10/18 10:35:21 error writing count stats for FOO_grafana: partial write
```
The `_internal` database collects per-node and also cluster-wide information about the InfluxEnterprise cluster. The cluster metrics are replicated to other nodes using `consistency=all`. For a [write consistency](/enterprise_influxdb/v1.5/concepts/clustering/#write-consistency) of `all`, InfluxDB returns a write error (500) for the write attempt even if the points are successfully queued in hinted handoff. Thus, if there are points still in hinted handoff, the `_internal` writes will fail the consistency check and log the error, even though the data is in the durable hinted handoff queue and should eventually persist.
The `_internal` database collects per-node and also cluster-wide information about the InfluxDB Enterprise cluster. The cluster metrics are replicated to other nodes using `consistency=all`. For a [write consistency](/enterprise_influxdb/v1.5/concepts/clustering/#write-consistency) of `all`, InfluxDB returns a write error (500) for the write attempt even if the points are successfully queued in hinted handoff. Thus, if there are points still in hinted handoff, the `_internal` writes will fail the consistency check and log the error, even though the data is in the durable hinted handoff queue and should eventually persist.
## Why am I seeing `queue is full` errors in my data node logs?

2
content/enterprise_influxdb/v1.6/administration/anti-entropy.md
View File

@ -86,7 +86,7 @@ A "flapping" dashboard means data visualizations changing when data is refreshed
and pulled from a node with entropy (inconsistent data).
It is the visual manifestation of getting [different results from the same query](#different-results-for-the-same-query).
<img src="/img/kapacitor/flapping-dashboard.gif" alt="Flapping dashboard" style="width:100%; max-width:800px">
<img src="/img/enterprise/1-6-flapping-dashboard.gif" alt="Flapping dashboard" style="width:100%; max-width:800px">
## Technical details

2
content/enterprise_influxdb/v1.6/administration/backup-and-restore.md
View File

@ -278,7 +278,7 @@ Restored from my-incremental-backup/ in 66.715524ms, transferred 588800 bytes
Your `telegraf` database was mistakenly dropped, but you have a recent backup so you've only lost a small amount of data.
If [Telegraf](/telegraf/v1.7/) is still running, it will recreate the `telegraf` database shortly after the database is dropped.
If [Telegraf](/{{< latest "telegraf" >}}/) is still running, it will recreate the `telegraf` database shortly after the database is dropped.
You might try to directly restore your `telegraf` backup just to find that you can't restore:
```

2
content/enterprise_influxdb/v1.6/concepts/glossary.md
View File

@ -73,4 +73,4 @@ Legacy user interface for the InfluxDB Enterprise.
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](/{{< latest "chronograf" >}}/guides/transition-web-admin-interface/) is available.
If you are transitioning from the Enterprise Web Console to Chronograf, see how to [transition from the InfluxDB Web Admin Interface](/chronograf/v1.7/guides/transition-web-admin-interface/).

2
content/enterprise_influxdb/v1.6/install-and-deploy/production_installation/_index.md
View File

@ -21,4 +21,4 @@ Learn how to deploy a cluster on the cloud provider of your choice:
- [GCP](/enterprise_influxdb/v1.7/install-and-deploy/google-cloud-platform/)
- [AWS](/enterprise_influxdb/v1.7/install-and-deploy/aws/)
- [Azure](/enterprise_influxdb/v1.7/install-and-deploy/deploying/azure/)
- [Azure](/enterprise_influxdb/v1.7/install-and-deploy/azure/)

2
content/enterprise_influxdb/v1.6/introduction/getting-started.md
View File

@ -10,7 +10,7 @@ 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.](/{{< latest "chronograf" >}}/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/monitoring-influxenterprise-cluster/monitoring-influxenterprise-cluster/monitoring-influxenterprise-cluster/)
More details on leveraging [Chronograf and getting started are available.](/{{< latest "chronograf" >}}/introduction/getting-started/)

2
content/enterprise_influxdb/v1.7/administration/anti-entropy.md
View File

@ -91,7 +91,7 @@ A "flapping" dashboard means data visualizations change when data is refreshed
and pulled from a node with entropy (inconsistent data).
It is the visual manifestation of getting [different results from the same query](#different-results-for-the-same-query).
<img src="/img/kapacitor/flapping-dashboard.gif" alt="Flapping dashboard" style="width:100%; max-width:800px">
<img src="/img/enterprise/1-6-flapping-dashboard.gif" alt="Flapping dashboard" style="width:100%; max-width:800px">
## Technical details

2
content/enterprise_influxdb/v1.7/administration/backup-and-restore.md
View File

@ -24,7 +24,7 @@ To choose a strategy that best suits your use case, we recommend considering you
- [Backup and restore utilities](#backup-and-restore-utilities) (suits **most InfluxDB Enterprise applications**)
- [Export and import commands](#export-and-import-commands) (best for **backfill or recovering shards as files**)
- [Take AWS snapshots as backup](/backup-and-restore/#take-aws-snapshots-as-backup) (optimal **convenience if budget permits**)
- [Take AWS snapshots as backup](#take-aws-snapshots-as-backup) (optimal **convenience if budget permits**)
- [Run two clusters in separate AWS regions](#run-two-clusters-in-separate-aws-regions) (also optimal **convenience if budget permits**, more custom work upfront)
> Test your backup and restore strategy for all applicable scenarios.

4
content/enterprise_influxdb/v1.7/concepts/glossary.md
View File

@ -61,7 +61,7 @@ The number of data nodes in a cluster **must be evenly divisible by the replicat
> **Important:** If the replication factor isn't evenly divisible into the number of data nodes, data may be distributed unevenly across the cluster and cause poor performance. Likewise, decreasing the replication factor (fewer copies of data in a cluster) may reduce performance.
Related entries: [cluster](/influxdb/v0.10/concepts/glossary/#cluster), [duration](/influxdb/v1.7/concepts/glossary/#duration), [node](/influxdb/v1.7/concepts/glossary/#node),
Related entries: [duration](/influxdb/v1.7/concepts/glossary/#duration), [node](/influxdb/v1.7/concepts/glossary/#node),
[retention policy](/influxdb/v1.7/concepts/glossary/#retention-policy-rp)
## web console
@ -70,4 +70,4 @@ Legacy user interface for the InfluxDB Enterprise.
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](/{{< latest "chronograf" >}}/guides/transition-web-admin-interface/) is available.
If you are transitioning from the Enterprise Web Console to Chronograf, see how to [transition from the InfluxDB Web Admin Interface](/chronograf/v1.7/guides/transition-web-admin-interface/).

2
content/enterprise_influxdb/v1.7/install-and-deploy/azure.md
View File

@ -18,7 +18,7 @@ This guide requires the following:
- Microsoft Azure account with access to the [Azure Marketplace](https://azuremarketplace.microsoft.com/).
- SSH access to cluster instances.
To deploy InfluxDB Enterprise clusters on platforms other than Azure, see [Deploy InfluxDB Enterprise](/enterprise_influxdb/v1.8/install-and-deploy/_index).
To deploy InfluxDB Enterprise clusters on platforms other than Azure, see [Deploy InfluxDB Enterprise](/enterprise_influxdb/v1.8/install-and-deploy/).
## Deploy a cluster

2
content/enterprise_influxdb/v1.7/introduction/getting-started.md
View File

@ -10,7 +10,7 @@ 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.](/{{< latest "chronograf" >}}/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/monitoring-influxenterprise-cluster/monitoring-influxenterprise-cluster/monitoring-influxenterprise-cluster/)
More details on leveraging [Chronograf and getting started are available.](/{{< latest "chronograf" >}}/introduction/getting-started/)

1
content/enterprise_influxdb/v1.8/administration/cluster-commands.md
View File

@ -4,6 +4,7 @@ description: >
Use the `influxd-ctl` and `influx` command line tools to manage InfluxDB Enterprise clusters and data.
aliases:
- /enterprise/v1.8/features/cluster-commands/
- /enterprise_influxdb/v1.8/features/cluster-commands/
menu:
enterprise_influxdb_1_8:
name: Manage clusters

2
content/enterprise_influxdb/v1.8/concepts/glossary.md
View File

@ -74,4 +74,4 @@ Legacy user interface for the InfluxDB Enterprise.
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](/{{< latest "chronograf" >}}/guides/transition-web-admin-interface/) is available.
If you are transitioning from the Enterprise Web Console to Chronograf, see how to [transition from the InfluxDB Web Admin Interface](/chronograf/v1.7/guides/transition-web-admin-interface/).

2
content/enterprise_influxdb/v1.8/install-and-deploy/deploying/azure.md
View File

@ -2,6 +2,8 @@
title: Deploy an InfluxDB Enterprise cluster on Azure Cloud Platform
description: >
Deploy an InfluxDB Enterprise cluster on Microsoft Azure cloud computing service.
aliases:
- /enterprise_influxdb/v1.8/install-and-deploy/azure/
menu:
enterprise_influxdb_1_8:
name: Azure

2
content/enterprise_influxdb/v1.8/introduction/getting-started.md
View File

@ -11,7 +11,7 @@ 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.](/{{< latest "chronograf" >}}/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/monitoring-influxenterprise-cluster/monitoring-influxenterprise-cluster/monitoring-influxenterprise-cluster/)
More details on leveraging [Chronograf and getting started are available.](/{{< latest "chronograf" >}}/introduction/getting-started/)

1
content/influxdb/cloud/account-management/multi-user/_index.md
View File

@ -9,6 +9,7 @@ menu:
name: Manage multiple users
aliases:
- /influxdb/v2.0/account-management/multi-user/
- /influxdb/cloud/users/
---
{{< cloud-name >}} accounts support multiple users in an organization.

4
content/influxdb/cloud/query-data/get-started/_index.md
View File

@ -87,6 +87,6 @@ The [Execute queries](/influxdb/cloud/query-data/execute-queries) guide walks th
the different tools available for querying InfluxDB with Flux.
<div class="page-nav-btns">
<a class="btn prev" href="/v2.0/query-data/">Introduction to Flux</a>
<a class="btn next" href="/v2.0/query-data/get-started/query-influxdb/">Query InfluxDB with Flux</a>
<a class="btn prev" href="/influxdb/cloud/query-data/">Introduction to Flux</a>
<a class="btn next" href="/influxdb/cloud/query-data/get-started/query-influxdb/">Query InfluxDB with Flux</a>
</div>

66
content/influxdb/cloud/reference/cli/influx/restore/index.md
View File

@ -19,4 +19,68 @@ For information about restoring data in InfluxDB Cloud, see
[contact InfluxData Support](mailto:support@influxdata.com).
{{% /note %}}
{{< duplicate-oss >}}
The `influx restore` command restores backup data and metadata from an InfluxDB OSS backup directory.
### The restore process
When restoring data from a backup file set, InfluxDB temporarily moves existing
data and metadata while `restore` runs.
After `restore` completes, the temporary data is deleted.
If the restore process fails, InfluxDB preserves the data in the temporary location.
_For information about recovering from a failed restore process, see
[Restore data](/influxdb/v2.0/backup-restore/restore/#recover-from-a-failed-restore)._
## Usage
```
influx restore [flags]
```
## Flags
| Flag | | Description | Input type | {{< cli/mapped >}} |
|:---- |:--- |:----------- |:----------: |:------------------ |
| `-c` | `--active-config` | CLI configuration to use for command | string | |
| `-b` | `--bucket` | Name of the bucket to restore (mutually exclusive with `--bucket-id`) | string | |
| | `--bucket-id` | ID of the bucket to restore (mutually exclusive with `--bucket`) | string | |
| | `--configs-path` | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string |`INFLUX_CONFIGS_PATH` |
| | `--full` | Fully restore and replace all data on server | | |
| `-h` | `--help` | Help for the `restore` command | | |
| | `--hide-headers` | Hide table headers (default `false`) | | `INFLUX_HIDE_HEADERS` |
| | `--host` | HTTP address of InfluxDB (default `http://localhost:8086`) | string | `INFLUX_HOST` |
| | `--input` | ({{< req >}}) Path to local backup directory | string | |
| | `--json` | Output data as JSON (default `false`) | | `INFLUX_OUTPUT_JSON` |
| | `--new-bucket` | Name of the bucket to restore to | string | |
| | `--new-org` | Name of the organization to restore to | string | |
| `-o` | `--org` | Organization name (mutually exclusive with `--org-id`) | string | |
| | `--org-id` | Organization ID (mutually exclusive with `--org`) | string | |
| | `--skip-verify` | Skip TLS certificate verification | | |
| `-t` | `--token` | Authentication token | string | `INFLUX_TOKEN` |
## Examples
{{< cli/influx-creds-note >}}
- [Restore and replace all data](#restore-and-replace-all-data)
- [Restore backup data to an existing bucket](#restore-backup-data-to-an-existing-bucket)
- [Create a bucket and restore data to it](#create-a-bucket-and-restore-data-to-it)
##### Restore and replace all data
```sh
influx restore --full --input /path/to/backup/dir/
```
##### Restore backup data to an existing bucket
```sh
influx restore \
--bucket example-bucket \
--input /path/to/backup/dir/
```
##### Create a bucket and restore data to it
```sh
influx restore \
--new-bucket new-example-bucket \
--input /path/to/backup/dir/
```

2
content/influxdb/cloud/reference/flux/stdlib/contrib/sensu/endpoint.md
View File

@ -85,7 +85,7 @@ following fields:
- `text`
- `status`
_For more information, see [`sensu.event()` parameters](/v2.0/reference/flux/stdlib/contrib/sensu/event/#parameters)._
_For more information, see [`sensu.event()` parameters](/influxdb/cloud/reference/flux/stdlib/contrib/sensu/event/#parameters)._
## Examples

2
content/influxdb/cloud/reference/flux/stdlib/contrib/teams/endpoint.md
View File

@ -47,7 +47,7 @@ following fields:
- `text`
- `summary`
_For more information, see [`teams.message()` parameters](/v2.0/reference/flux/stdlib/contrib/teams/message/#parameters)._
_For more information, see [`teams.message()` parameters](/influxdb/v2.0/reference/flux/stdlib/contrib/teams/message/#parameters)._
## Examples

4
content/influxdb/cloud/reference/flux/stdlib/contrib/telegram/endpoint.md
View File

@ -28,7 +28,7 @@ telegram.endpoint(
{{% note %}}
For information about retrieving your Telegram **bot token** and **channel ID**,
see [Set up a Telegram bot](/v2.0/reference/flux/stdlib/contrib/telegram/#set-up-a-telegram-bot).
see [Set up a Telegram bot](/influxdb/v2.0/reference/flux/stdlib/contrib/telegram/#set-up-a-telegram-bot).
{{% /note %}}
## Parameters
@ -74,7 +74,7 @@ following fields:
- `text`
- `silent`
_For more information, see [`telegram.message()` parameters](/v2.0/reference/flux/stdlib/contrib/telegram/message/#parameters)._
_For more information, see [`telegram.message()` parameters](/influxdb/v2.0/reference/flux/stdlib/contrib/telegram/message/#parameters)._
## Examples

2
content/influxdb/cloud/reference/flux/stdlib/contrib/telegram/message.md
View File

@ -31,7 +31,7 @@ telegram.message(
{{% note %}}
For information about retrieving your Telegram **bot token** and **channel ID**,
see [Set up a Telegram bot](/v2.0/reference/flux/stdlib/contrib/telegram/#set-up-a-telegram-bot).
see [Set up a Telegram bot](/influxdb/v2.0/reference/flux/stdlib/contrib/telegram/#set-up-a-telegram-bot).
{{% /note %}}
## Parameters

5
content/influxdb/cloud/tools/chronograf.md
View File

@ -1,9 +1,8 @@
---
title: Use Chronograf with InfluxDB Cloud
description: >
[Chronograf](/{{< latest "chronograf" >}}/) is a data visualization and dashboarding
tool designed to visualize data in InfluxDB 1.x. It is part of the [TICKstack](/platform/)
that provides an InfluxQL data explorer, Kapacitor integrations, and more.
Chronograf is a data visualization and dashboarding tool designed to visualize data in InfluxDB 1.x.
It is part of the [TICKstack](/platform/) that provides an InfluxQL data explorer, Kapacitor integrations, and more.
Continue to use Chronograf with **InfluxDB Cloud** and **InfluxDB OSS 2.0** and the
[1.x compatibility API](/influxdb/v2.0/reference/api/influxdb-1x/).
menu:

6
content/influxdb/cloud/visualize-data/dashboards/control-dashboard.md
View File

@ -33,12 +33,6 @@ Click the timezone dropdown to select a timezone to use for the dashboard. Selec
{{< img-hd src="/img/influxdb/2-0-controls-timezone.png" alt="Select timezone" />}}
### Select auto-refresh interval
Select how frequently to refresh the dashboard's data. By default, refreshing is paused.
{{< img-hd src="/img/influxdb/2-0-controls-refresh-interval.png" alt="Select refresh interval" />}}
### Manually refresh dashboard
Click the refresh button (**{{< icon "refresh" >}}**) to manually refresh the dashboard's data.

6
content/influxdb/cloud/visualize-data/explore-metrics.md
View File

@ -66,12 +66,6 @@ Toggle the **View Raw Data** {{< icon "toggle" >}} option to see your data in ta
Click the CSV icon to save the cells contents as a CSV file.
### Select auto-refresh interval
Select how frequently to refresh the dashboard's data. By default, refreshing is paused.
{{< img-hd src="/img/influxdb-influxdb/2-0-controls-refresh-interval.png" alt="Select refresh interval" />}}
### Manually refresh dashboard
Click the refresh button ({{< icon "refresh" >}}) to manually refresh the dashboard's data.

6
content/influxdb/cloud/visualize-data/variables/common-variables.md
View File

@ -64,7 +64,7 @@ v1.tagValues(bucket: "bucket-name", tag: "host")
## List Docker containers
List all Docker containers when using the Docker Telegraf plugin.
_**Telegraf plugin:** [Docker](/{{< latest "telegraf" >}}/plugins/inputs/#docker)_
_**Telegraf plugin:** [Docker](/{{< latest "telegraf" >}}/plugins/#docker)_
_**Flux package:** [InfluxDB v1](/influxdb/cloud/reference/flux/stdlib/influxdb-v1/)_
_**Flux functions:** [v1.tagValues()](/influxdb/cloud/reference/flux/stdlib/influxdb-v1/tagvalues/)_
@ -76,7 +76,7 @@ v1.tagValues(bucket: "bucket-name", tag: "container_name")
## List Kubernetes pods
List all Kubernetes pods when using the Kubernetes Telegraf plugin.
_**Telegraf plugin:** [Kubernetes](/{{< latest "telegraf" >}}/plugins/inputs/#kubernetes)_
_**Telegraf plugin:** [Kubernetes](/{{< latest "telegraf" >}}/plugins/#kubernetes)_
_**Flux package:** [InfluxDB v1](/influxdb/cloud/reference/flux/stdlib/influxdb-v1/)_
_**Flux functions:** [v1.measurementTagValues()](/influxdb/cloud/reference/flux/stdlib/influxdb-v1/measurementtagvalues/)_
@ -92,7 +92,7 @@ v1.measurementTagValues(
## List Kubernetes nodes
List all Kubernetes nodes when using the Kubernetes Telegraf plugin.
_**Telegraf plugin:** [Kubernetes](/{{< latest "telegraf" >}}/plugins/inputs/#kubernetes)_
_**Telegraf plugin:** [Kubernetes](/{{< latest "telegraf" >}}/plugins/#kubernetes)_
_**Flux package:** [InfluxDB v1](/influxdb/cloud/reference/flux/stdlib/influxdb-v1/)_
_**Flux functions:** [v1.measurementTagValues()](/influxdb/cloud/reference/flux/stdlib/influxdb-v1/measurementtagvalues/)_

2
content/influxdb/v1.3/_index.md
View File

@ -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](/influxdb/v1.3/high_availability/).
to eliminate a single point of failure, you should explore [InfluxDB Enterprise Edition](/{{< latest "enterprise_influxdb" >}}/).

12
content/influxdb/v1.3/administration/backup_and_restore.md
View File

@ -16,13 +16,13 @@ There are two types of data to backup, the metastore and the metrics themselves.
The [metastore](/influxdb/v1.3/concepts/glossary/#metastore) is backed up in its entirety.
The metrics are backed up per-database in a separate operation from the metastore backup.
> **Note:** Backups are not interchangeable between InfluxDB OSS and [InfluxEnterprise](/enterprise/v1.3/).
You cannot restore an OSS backup to an InfluxEnterprise data node, nor can you restore
an InfluxEnterprise backup to an OSS instance.
> **Note:** Backups are not interchangeable between InfluxDB OSS and [InfluxDB Enterprise](https://archive.docs.influxdata.com/enterprise_influxdb/v1.3/).
You cannot restore an OSS backup to an InfluxDB Enterprise data node, nor can you restore
an InfluxDB Enterprise backup to an OSS instance.
>
If you are working with an InfluxEnterprise cluster, please see the [Backup
and Restore Guide](/enterprise/v1.3/guides/backup-and-restore/) in the
InfluxEnterprise documentation.
If you are working with an InfluxDB Enterprise cluster, please see the [Backup
and Restore Guide](https://archive.docs.influxdata.com/enterprise_influxdb/v1.3/guides/backup-and-restore/) in the
InfluxDB Enterprise documentation.
### Backing up the Metastore

4
content/influxdb/v1.3/administration/config.md
View File

@ -560,8 +560,8 @@ Environment variable: `INFLUXDB_MONITOR_STORE_INTERVAL`
{{% warn %}} In version 1.3, the web admin interface is no longer available in InfluxDB.
The interface does not run on port `8083` and InfluxDB ignores the `[admin]` section in the configuration file if that section is present.
[Chronograf](/chronograf/v1.3/) replaces the web admin interface with improved tooling for querying data, writing data, and database management.
See [Chronograf's transition guide](/chronograf/v1.3/guides/transition-web-admin-interface/) for more information.
[Chronograf](/{{< latest "chronograf" >}}/) replaces the web admin interface with improved tooling for querying data, writing data, and database management.
See [Chronograf's transition guide](/chronograf/v1.7/guides/transition-web-admin-interface/) for more information.
{{% /warn %}}
## [http]

4
content/influxdb/v1.3/administration/differences.md
View File

@ -49,8 +49,8 @@ Next, restart your InfluxDB instance.
In version 1.3, the web admin interface is no longer available in InfluxDB.
The interface does not run on port `8083` and InfluxDB ignores the `[admin]` section in the configuration file if that section is present.
[Chronograf](/chronograf/v1.3/) replaces the web admin interface with improved tooling for querying data, writing data, and database management.
See [Chronograf's transition guide](/chronograf/v1.3/guides/transition-web-admin-interface/) for more information.
[Chronograf](/{{< latest "chronograf" >}}/) replaces the web admin interface with improved tooling for querying data, writing data, and database management.
See [Chronograf's transition guide](/chronograf/v1.7/guides/transition-web-admin-interface/) for more information.
## Duration Unit Updates

2
content/influxdb/v1.3/administration/https_setup.md
View File

@ -186,7 +186,7 @@ That's it! You've successfully set up HTTPS with InfluxDB.
>
## Connect Telegraf to a secured InfluxDB instance
>
Connecting [Telegraf](/telegraf/v1.3/) 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`

14
content/influxdb/v1.3/administration/previous_differences.md
View File

@ -17,25 +17,25 @@ If you're using version 1.2, please see [Differences Between InfluxDB 1.3 and 1.
Users looking to upgrade to InfluxDB 1.3 from versions prior to 1.2 should view the following pages in our documentation.
##### 1.1 users:
[Differences Between InfluxDB 1.2 and 1.1](https://archive.docs.influxdata.com/influxdb/v1.2/administration/differences/)
[Differences Between InfluxDB 1.2 and 1.1](https://archive.docs.influxdata.comhttps://archive.docs.influxdata.com/influxdb/v1.2/administration/differences/)
##### 1.0 users:
[Differences Between InfluxDB 1.1 and 1.0](https://archive.docs.influxdata.com/influxdb/v1.1/administration/differences/)
[Differences Between InfluxDB 1.1 and 1.0](https://archive.docs.influxdata.comhttps://archive.docs.influxdata.com/influxdb/v1.1/administration/differences/)
##### 0.13 users:
[Differences Between InfluxDB 1.0 and 0.13](https://archive.docs.influxdata.com/influxdb/v1.0/administration/013_vs_1/)
[Differences Between InfluxDB 1.0 and 0.13](https://archive.docs.influxdata.comhttps://archive.docs.influxdata.com/influxdb/v1.0/administration/013_vs_1/)
##### 0.12 users:
[Differences Between InfluxDB 0.13 and 0.12](https://archive.docs.influxdata.com/influxdb/v0.13/administration/012_vs_013/)
[Differences Between InfluxDB 0.13 and 0.12](https://archive.docs.influxdata.comhttps://archive.docs.influxdata.com/influxdb/v0.13/administration/012_vs_013/)
##### 0.11 users:
[Differences between InfluxDB 0.12 and InfluxDB 0.11](https://archive.docs.influxdata.com/influxdb/v0.12/concepts/011_vs_012/)
[Differences between InfluxDB 0.12 and InfluxDB 0.11](https://archive.docs.influxdata.comhttps://archive.docs.influxdata.com/influxdb/v0.12/concepts/011_vs_012/)
##### 0.10 users:
[Differences between InfluxDB 0.11 and InfluxDB 0.10](https://archive.docs.influxdata.com/influxdb/v0.11/concepts/010_vs_011/)
##### 0.9 users:
[Differences between InfluxDB 0.9 and InfluxDB 0.10](https://archive.docs.influxdata.com/influxdb/v0.10/concepts/09_vs_010/)
[Differences between InfluxDB 0.9 and InfluxDB 0.10](https://archive.docs.influxdata.comhttps://archive.docs.influxdata.com/influxdb/v0.10/concepts/09_vs_010/)
##### 0.8 users:
[Differences between InfluxDB 0.8 and InfluxDB 0.10](https://archive.docs.influxdata.com/influxdb/v0.10/concepts/08_vs_010/)
[Differences between InfluxDB 0.8 and InfluxDB 0.10](https://archive.docs.influxdata.comhttps://archive.docs.influxdata.com/influxdb/v0.10/concepts/08_vs_010/)

4
content/influxdb/v1.3/administration/upgrading.md
View File

@ -33,7 +33,7 @@ This page outlines process for upgrading from:
## Upgrade from 0.10 or 0.11 to 1.3
> **Note:** 0.10 users will need to
[convert](/influxdb/v0.10/administration/upgrading/#convert-b1-and-bz1-shards-to-tsm1)
[convert](https://archive.docs.influxdata.com/influxdb/v0.10/administration/upgrading/#convert-b1-and-bz1-shards-to-tsm1)
any remaining `b1` and `bz1` shards to `TSM` format before following the
instructions below.
InfluxDB 1.3 cannot read non-`TSM` shards.
@ -55,7 +55,7 @@ new configuration file.
To start out, you must be working with version 0.10 or 0.11 (don't upgrade the
`influxd` binary yet!).
If you've already upgraded the binary to 1.3, [reinstall 0.11.1](/influxdb/v0.12/administration/upgrading/#urls-for-influxdb-0-11);
If you've already upgraded the binary to 1.3, [reinstall 0.11.1](https://archive.docs.influxdata.com/influxdb/v0.12/administration/upgrading/#urls-for-influxdb-0-11);
InfluxDB 1.3 will yield an error
(`run: create server: detected /var/lib/influxdb/meta/raft.db. [...]`) if you
attempt to start the process without completing the steps below.

4
content/influxdb/v1.3/guides/hardware_sizing.md
View File

@ -6,7 +6,7 @@ menu:
parent: Guides
---
This guide offers general hardware recommendations for InfluxDB and addresses some frequently asked questions about hardware sizing. The recommendations are only for the [Time Structured Merge](/influxdb/v1.3/concepts/storage_engine/#the-new-influxdb-storage-engine-from-lsm-tree-to-b-tree-and-back-again-to-create-the-time-structured-merge-tree) tree (`TSM`) storage engine, the only storage engine available with InfluxDB 1.3. Users running older versions of InfluxDB with [unconverted](/influxdb/v0.10/administration/upgrading/#convert-b1-and-bz1-shards-to-tsm1) `b1` or `bz1` shards may have different performance characteristics. See the [InfluxDB 0.9 sizing guide](/influxdb/v0.9/guides/hardware_sizing/) for more detail.
This guide offers general hardware recommendations for InfluxDB and addresses some frequently asked questions about hardware sizing. The recommendations are only for the [Time Structured Merge](/influxdb/v1.3/concepts/storage_engine/#the-new-influxdb-storage-engine-from-lsm-tree-to-b-tree-and-back-again-to-create-the-time-structured-merge-tree) tree (`TSM`) storage engine, the only storage engine available with InfluxDB 1.3. Users running older versions of InfluxDB with [unconverted](https://archive.docs.influxdata.com/influxdb/v0.10/administration/upgrading/#convert-b1-and-bz1-shards-to-tsm1) `b1` or `bz1` shards may have different performance characteristics. See the [InfluxDB 0.9 sizing guide](https://archive.docs.influxdata.com/influxdb/v0.9/guides/hardware_sizing/) for more detail.
* [Single node or Cluster?](/influxdb/v1.3/guides/hardware_sizing/#single-node-or-cluster)
* [General hardware guidelines for a single node](/influxdb/v1.3/guides/hardware_sizing/#general-hardware-guidelines-for-a-single-node)
@ -93,7 +93,7 @@ Meta nodes do not need very much computing power. Regardless of the cluster load
* IOPS: 50
## Data Nodes
A cluster with only one data node is valid but has no data redundancy. The redundancy is set by the [replication factor](/influxdb/v0.13/concepts/glossary/#replication-factor) on the retention policy to which the data is written. A cluster can lose `n - 1` data nodes and still return complete query results, where `n` is the replication factor. For optimal data distribution within the cluster, InfluxData recommends using an even number of data nodes.
A cluster with only one data node is valid but has no data redundancy. The redundancy is set by the [replication factor](/influxdb/v1.3/concepts/glossary/#replication-factor) on the retention policy to which the data is written. A cluster can lose `n - 1` data nodes and still return complete query results, where `n` is the replication factor. For optimal data distribution within the cluster, InfluxData recommends using an even number of data nodes.
The hardware recommendations for cluster data nodes are similar to the standalone instance recommendations. Data nodes should always have at least 2 CPU cores, as they must handle regular read and write traffic, as well as intra-cluster read and write traffic. Due to the cluster communication overhead, data nodes in a cluster handle less throughput than a standalone instance on the same hardware.

2
content/influxdb/v1.3/query_language/authentication_and_authorization.md
View File

@ -152,7 +152,7 @@ password:
>
## Authenticate Telegraf requests to InfluxDB
>
Authenticating [Telegraf](/telegraf/v1.3/) 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:

2
content/influxdb/v1.3/query_language/spec.md
View File

@ -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](/kapacitor/v1.3/introduction/).
Subscriptions tell InfluxDB to send all the data it receives to [Kapacitor](/{{< latest "kapacitor" >}}/).
```
create_subscription_stmt = "CREATE SUBSCRIPTION" subscription_name "ON" db_name "." retention_policy "DESTINATIONS" ("ANY"|"ALL") host { "," host} .

6
content/influxdb/v1.3/tools/_index.md
View File

@ -46,8 +46,8 @@ The list of [client libraries](/influxdb/v1.3/tools/api_client_libraries/) for i
In version 1.3, the web admin interface is no longer available in InfluxDB.
The interface does not run on port `8083` and InfluxDB ignores the `[admin]` section in the configuration file if that section is present.
[Chronograf](/chronograf/v1.3/) replaces the web admin interface with improved tooling for querying data, writing data, and database management.
See [Chronograf's transition guide](/chronograf/v1.3/guides/transition-web-admin-interface/) for more information.
[Chronograf](/{{< latest "chronograf" >}}/) replaces the web admin interface with improved tooling for querying data, writing data, and database management.
See [Chronograf's transition guide](/chronograf/v1.7/guides/transition-web-admin-interface/) for more information.
## Influx Inspect
@ -60,7 +60,7 @@ is a convenient dashboard tool for visualizing time series data.
It was originally built for Graphite, modeled after Kibana, and since been updated to support InfluxDB.
{{% warn %}}
Because of the [changes](/influxdb/v0.11/concepts/010_vs_011/#breaking-api-changes) to the `SHOW SERIES` and `SHOW TAG VALUES` formats in InfluxDB 0.11, InfluxDB 1.3 will not work with the Query Editor in Grafana 2.6.
Because of the [changes](https://archive.docs.influxdata.com/influxdb/v0.11/concepts/010_vs_011/#breaking-api-changes) to the `SHOW SERIES` and `SHOW TAG VALUES` formats in InfluxDB 0.11, InfluxDB 1.3 will not work with the Query Editor in Grafana 2.6.
This issue does not affect existing queries and dashboards or users working with Grafana 3.0.
{{% /warn %}}

4
content/influxdb/v1.3/tools/web_admin.md
View File

@ -10,6 +10,6 @@ menu:
{{% warn %}}
In version 1.3, the web admin interface is no longer available in InfluxDB.
The interface does not run on port `8083` and InfluxDB ignores the `[admin]` section in the configuration file if that section is present.
[Chronograf](/chronograf/v1.3/) replaces the web admin interface with improved tooling for querying data, writing data, and database management.
See [Chronograf's transition guide](/chronograf/v1.3/guides/transition-web-admin-interface/) for more information.
[Chronograf](/{{< latest "chronograf" >}}/) replaces the web admin interface with improved tooling for querying data, writing data, and database management.
See [Chronograf's transition guide](/chronograf/v1.7/guides/transition-web-admin-interface/) for more information.
{{% /warn %}}

6
content/influxdb/v1.3/troubleshooting/query_management.md
View File

@ -23,7 +23,7 @@ and prevent and halt the execution of inefficient queries with several configura
## List currently-running queries with `SHOW QUERIES`
`SHOW QUERIES` lists the query ID, query text, relevant database, and duration
of all currently-running queries on your InfluxDB instance.
For InfluxEnterprise clusters, the `SHOW QUERIES` output also includes the TCP host.
For InfluxDB Enterprise clusters, the `SHOW QUERIES` output also includes the TCP host.
#### Syntax:
```
@ -57,7 +57,7 @@ Where `qid` is the query ID, displayed in the [`SHOW QUERIES`](/influxdb/v1.3/tr
```
KILL QUERY <qid>
```
***InfluxEnterprise clusters:*** To kill queries on a cluster, you need to specify the query ID (qid) and the TCP host (for example, `myhost:8088`),
***InfluxDB Enterprise clusters:*** To kill queries on a cluster, you need to specify the query ID (qid) and the TCP host (for example, `myhost:8088`),
available in the `SHOW QUERIES` output.
```
@ -74,7 +74,7 @@ A successful `KILL QUERY` query returns no results.
>
```
```
-- kill query on InfluxEnterprise cluster
-- kill query on InfluxDB Enterprise cluster
> KILL QUERY 53 ON "myhost:8088"
>
```

2
content/influxdb/v1.4/_index.md
View File

@ -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](/influxdb/v1.4/high_availability/).
to eliminate a single point of failure, consider the [InfluxDB Enterprise Edition](/{{< latest "enterprise_influxdb" >}}/).

12
content/influxdb/v1.4/administration/backup_and_restore.md
View File

@ -14,13 +14,13 @@ The [metastore](/influxdb/v1.4/concepts/glossary/#metastore) is backed up in its
The metrics are backed up per-database in a separate operation from the metastore backup.
Per-database backups can be full, incremental (since a RFC3339 formatted time), or for a specific shard ID.
> **Note:** Backups are not interchangeable between InfluxDB OSS and [InfluxEnterprise](/enterprise/latest/).
You cannot restore an OSS backup to an InfluxEnterprise data node, nor can you restore
an InfluxEnterprise backup to an OSS instance.
> **Note:** Backups are not interchangeable between InfluxDB OSS and [InfluxDB Enterprise](/{{< latest "enterprise_influxdb" >}}/).
You cannot restore an OSS backup to an InfluxDB Enterprise data node, nor can you restore
an InfluxDB Enterprise backup to an OSS instance.
>
If you are working with an InfluxEnterprise cluster, please see the [Backup
and Restore Guide](/enterprise/latest/guides/backup-and-restore/) in the
InfluxEnterprise documentation.
If you are working with an InfluxDB Enterprise cluster, please see the [Backup
and Restore Guide](/{{< latest "enterprise_influxdb" >}}/administration/backup-and-restore/) in the
InfluxDB Enterprise documentation.
### Backing up the metastore

16
content/influxdb/v1.4/administration/previous_differences.md
View File

@ -20,25 +20,25 @@ Users looking to upgrade to InfluxDB 1.4 from versions prior to 1.3 should view
[Differences Between InfluxDB 1.3 and 1.2](/influxdb/v1.3/administration/differences/)
##### 1.1 users:
[Differences Between InfluxDB 1.2 and 1.1](/influxdb/v1.2/administration/differences/)
[Differences Between InfluxDB 1.2 and 1.1](https://archive.docs.influxdata.com/influxdb/v1.2/administration/differences/)
##### 1.0 users:
[Differences Between InfluxDB 1.1 and 1.0](/influxdb/v1.1/administration/differences/)
[Differences Between InfluxDB 1.1 and 1.0](https://archive.docs.influxdata.com/influxdb/v1.1/administration/differences/)
##### 0.13 users:
[Differences Between InfluxDB 1.0 and 0.13](/influxdb/v1.0/administration/013_vs_1/)
[Differences Between InfluxDB 1.0 and 0.13](https://archive.docs.influxdata.com/influxdb/v1.0/administration/013_vs_1/)
##### 0.12 users:
[Differences Between InfluxDB 0.13 and 0.12](/influxdb/v0.13/administration/012_vs_013/)
[Differences Between InfluxDB 0.13 and 0.12](https://archive.docs.influxdata.com/influxdb/v0.13/administration/012_vs_013/)
##### 0.11 users:
[Differences between InfluxDB 0.12 and InfluxDB 0.11](/influxdb/v0.12/concepts/011_vs_012/)
[Differences between InfluxDB 0.12 and InfluxDB 0.11](https://archive.docs.influxdata.com/influxdb/v0.12/concepts/011_vs_012/)
##### 0.10 users:
[Differences between InfluxDB 0.11 and InfluxDB 0.10](/influxdb/v1.3/concepts/010_vs_011/)
[Differences between InfluxDB 0.11 and InfluxDB 0.10](/influxdb/v1.3/administration/previous_differences/)
##### 0.9 users:
[Differences between InfluxDB 0.9 and InfluxDB 0.10](/influxdb/v0.10/concepts/09_vs_010/)
[Differences between InfluxDB 0.9 and InfluxDB 0.10](https://archive.docs.influxdata.com/influxdb/v0.10/concepts/09_vs_010/)
##### 0.8 users:
[Differences between InfluxDB 0.8 and InfluxDB 0.10](/influxdb/v0.10/concepts/08_vs_010/)
[Differences between InfluxDB 0.8 and InfluxDB 0.10](https://archive.docs.influxdata.com/influxdb/v0.10/concepts/08_vs_010/)

4
content/influxdb/v1.4/administration/upgrading.md
View File

@ -34,7 +34,7 @@ This page outlines process for upgrading from:
## Upgrade from 0.10 or 0.11 to 1.4
> **Note:** 0.10 users will need to
[convert](/influxdb/v0.10/administration/upgrading/#convert-b1-and-bz1-shards-to-tsm1)
[convert](https://archive.docs.influxdata.com/influxdb/v0.10/administration/upgrading/#convert-b1-and-bz1-shards-to-tsm1)
any remaining `b1` and `bz1` shards to `TSM` format before following the
instructions below.
InfluxDB 1.4 cannot read non-`TSM` shards.
@ -56,7 +56,7 @@ new configuration file.
To start out, you must be working with version 0.10 or 0.11 (don't upgrade the
`influxd` binary yet!).
If you've already upgraded the binary to 1.4, [reinstall 0.11.1](/influxdb/v0.12/administration/upgrading/#urls-for-influxdb-0-11);
If you've already upgraded the binary to 1.4, [reinstall 0.11.1](https://archive.docs.influxdata.com/influxdb/v0.12/administration/upgrading/#urls-for-influxdb-0-11);
InfluxDB 1.4 will yield an error
(`run: create server: detected /var/lib/influxdb/meta/raft.db. [...]`) if you
attempt to start the process without completing the steps below.

4
content/influxdb/v1.4/guides/hardware_sizing.md
View File

@ -6,7 +6,7 @@ menu:
parent: Guides
---
This guide offers general hardware recommendations for InfluxDB and addresses some frequently asked questions about hardware sizing. The recommendations are only for the [Time Structured Merge](/influxdb/v1.4/concepts/storage_engine/#the-new-influxdb-storage-engine-from-lsm-tree-to-b-tree-and-back-again-to-create-the-time-structured-merge-tree) tree (`TSM`) storage engine, the only storage engine available with InfluxDB 1.4. Users running older versions of InfluxDB with [unconverted](/influxdb/v0.10/administration/upgrading/#convert-b1-and-bz1-shards-to-tsm1) `b1` or `bz1` shards may have different performance characteristics. See the [InfluxDB 0.9 sizing guide](/influxdb/v0.9/guides/hardware_sizing/) for more detail.
This guide offers general hardware recommendations for InfluxDB and addresses some frequently asked questions about hardware sizing. The recommendations are only for the [Time Structured Merge](/influxdb/v1.4/concepts/storage_engine/#the-new-influxdb-storage-engine-from-lsm-tree-to-b-tree-and-back-again-to-create-the-time-structured-merge-tree) tree (`TSM`) storage engine, the only storage engine available with InfluxDB 1.4. Users running older versions of InfluxDB with [unconverted](https://archive.docs.influxdata.com/influxdb/v0.10/administration/upgrading/#convert-b1-and-bz1-shards-to-tsm1) `b1` or `bz1` shards may have different performance characteristics. See the [InfluxDB 0.9 sizing guide](https://archive.docs.influxdata.com/influxdb/v0.9/guides/hardware_sizing/) for more detail.
* [Single node or Cluster?](/influxdb/v1.4/guides/hardware_sizing/#single-node-or-cluster)
* [General hardware guidelines for a single node](/influxdb/v1.4/guides/hardware_sizing/#general-hardware-guidelines-for-a-single-node)
@ -93,7 +93,7 @@ Meta nodes do not need very much computing power. Regardless of the cluster load
* IOPS: 50
## Data Nodes
A cluster with only one data node is valid but has no data redundancy. The redundancy is set by the [replication factor](/influxdb/v0.13/concepts/glossary/#replication-factor) on the retention policy to which the data is written. A cluster can lose `n - 1` data nodes and still return complete query results, where `n` is the replication factor. For optimal data distribution within the cluster, InfluxData recommends using an even number of data nodes.
A cluster with only one data node is valid but has no data redundancy. The redundancy is set by the [replication factor](/influxdb/v1.3/concepts/glossary/#replication-factor) on the retention policy to which the data is written. A cluster can lose `n - 1` data nodes and still return complete query results, where `n` is the replication factor. For optimal data distribution within the cluster, InfluxData recommends using an even number of data nodes.
The hardware recommendations for cluster data nodes are similar to the standalone instance recommendations. Data nodes should always have at least 2 CPU cores, as they must handle regular read and write traffic, as well as intra-cluster read and write traffic. Due to the cluster communication overhead, data nodes in a cluster handle less throughput than a standalone instance on the same hardware.

2
content/influxdb/v1.4/query_language/continuous_queries.md
View File

@ -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](/{{< latest "kapacitor" >}}/examples/continuous_queries/) for when
[Kapacitor documentation](/{{< latest "kapacitor" >}}/guides/continuous_queries/) for when
to use Kapacitor instead of InfluxDB and how to perform the same CQ
functionality with a TICKscript.

2
content/influxdb/v1.4/query_language/spec.md
View File

@ -714,7 +714,7 @@ KILL QUERY <qid> ON "<host>"
KILL QUERY 36
```
```sql
-- kill query on InfluxEnterprise cluster
-- kill query on InfluxDB Enterprise cluster
KILL QUERY 53 ON "myhost:8088"
```

2
content/influxdb/v1.4/tools/_index.md
View File

@ -54,5 +54,5 @@ line protocol that can be inserted back into the database.
is a convenient dashboard tool for visualizing time series data.
It was originally built for Graphite, modeled after Kibana, and since been updated to support InfluxDB.
{{% warn %}} Because of the [changes](/influxdb/v0.11/concepts/010_vs_011/#breaking-api-changes) to the `SHOW SERIES` and `SHOW TAG VALUES` formats in InfluxDB 0.11, InfluxDB 1.3+ will not work with the Query Editor in Grafana 2.6.
{{% warn %}} Because of the [changes](https://archive.docs.influxdata.com/influxdb/v0.11/concepts/010_vs_011/#breaking-api-changes) to the `SHOW SERIES` and `SHOW TAG VALUES` formats in InfluxDB 0.11, InfluxDB 1.3+ will not work with the Query Editor in Grafana 2.6.
This issue does not affect existing queries and dashboards or users working with Grafana 3.0. {{% /warn %}}

2
content/influxdb/v1.4/tools/api.md
View File

@ -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](/enterprise_influxdb/v1.3/concepts/clustering#write-consistency) for detailed descriptions of each consistency option. |
| consistency=[any,one,quorum,all] | Optional, available with [InfluxDB Enterprise clusters](/enterprise_influxdb/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 [InfluxDB Enterprise documentation](/enterprise_influxdb/v1.3/concepts/clustering#write-consistency) for detailed descriptions of each consistency option. |
| db=\<database> | Required | Sets the target [database](/influxdb/v1.4/concepts/glossary/#database) for the write. |
| p=\<password> | 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`.** |

2
content/influxdb/v1.4/troubleshooting/errors.md
View File

@ -318,4 +318,4 @@ It will be in the `killed` state, which means the signal has been sent, but the
query itself has not hit an interrupt point.
**Resources:**
[Query Management](/influxdb/v1.0/troubleshooting/query_management/)
[Query Management](/influxdb/v1.4/troubleshooting/query_management/)

4
content/influxdb/v1.4/troubleshooting/query_management.md
View File

@ -55,7 +55,7 @@ Where `qid` is the query ID, displayed in the [`SHOW QUERIES`](/influxdb/v1.3/tr
```
KILL QUERY <qid>
```
***InfluxEnterprise clusters:*** To kill queries on a cluster, you need to specify the query ID (qid) and the TCP host (for example, `myhost:8088`),
***InfluxDB Enterprise clusters:*** To kill queries on a cluster, you need to specify the query ID (qid) and the TCP host (for example, `myhost:8088`),
available in the `SHOW QUERIES` output.
```
@ -72,7 +72,7 @@ A successful `KILL QUERY` query returns no results.
>
```
```
-- kill query on InfluxEnterprise cluster
-- kill query on InfluxDB Enterprise cluster
> KILL QUERY 53 ON "myhost:8088"
>
```

2
content/influxdb/v1.5/_index.md
View File

@ -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](/influxdb/v1.5/high_availability/).
If you require high availability to eliminate a single point of failure, consider the [InfluxDB Enterprise Edition](/enterprise_influxdb/v1.5/).

4
content/influxdb/v1.5/guides/calculating_percentages.md
View File

@ -80,7 +80,7 @@ FROM "apple_stand"."autogen"."variety"
FROM "apple_stand"."autogen"."variety"'>
\*</div>
If visualized as a [stacked graph](/chronograf/v1.5/guides/visualization-types/#stacked-graph)
If visualized as a [stacked graph](/{{< latest "chronograf" >}}/guides/visualization-types/#stacked-graph)
in Chronograf, it would look like:
![Percentage of total per apple variety](/img/influxdb/1-5-calc-percentage-apple-variety.png)
@ -109,7 +109,7 @@ _**Note the following about this query:**_
- It includes an explicitly limited time window. Without it, aggregate functions
are very resource-intensive.
If visualized as a [stacked graph](/chronograf/v1.5/guides/visualization-types/#stacked-graph)
If visualized as a [stacked graph](/{{< latest "chronograf" >}}/guides/visualization-types/#stacked-graph)
in Chronograf, it would look like:
![Hourly average percentage of total per apple variety](/img/influxdb/1-5-calc-percentage-hourly-apple-variety.png)

2
content/influxdb/v1.5/query_language/continuous_queries.md
View File

@ -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](/{{< latest "kapacitor" >}}/examples/continuous_queries/) to learn when
Check out [examples of continuous queries in Kapacitor](/{{< latest "kapacitor" >}}/guides/continuous_queries/) to learn when
to use Kapacitor instead of InfluxDB and how to perform the same CQ
functionality with a TICKscript.

2
content/influxdb/v1.5/query_language/spec.md
View File

@ -750,7 +750,7 @@ KILL QUERY 36
```
```sql
-- kill query on InfluxEnterprise cluster
-- kill query on InfluxDB Enterprise cluster
KILL QUERY 53 ON "myhost:8088"
```

2
content/influxdb/v1.5/tools/_index.md
View File

@ -54,6 +54,6 @@ is a convenient dashboard tool for visualizing time series data.
It was originally built for Graphite, modeled after Kibana, and since been updated to support InfluxDB.
{{% warn %}}
Because of the [changes](/influxdb/v0.11/concepts/010_vs_011/#breaking-api-changes) to the `SHOW SERIES` and `SHOW TAG VALUES` formats in InfluxDB 0.11, InfluxDB 1.3+ will not work with the Query Editor in Grafana 2.6.
Because of the [changes](https://archive.docs.influxdata.com/influxdb/v0.11/concepts/010_vs_011/#breaking-api-changes) to the `SHOW SERIES` and `SHOW TAG VALUES` formats in InfluxDB 0.11, InfluxDB 1.3+ will not work with the Query Editor in Grafana 2.6.
This issue does not affect existing queries and dashboards or users working with Grafana 3.0.
{{% /warn %}}

2
content/influxdb/v1.5/troubleshooting/errors.md
View File

@ -320,4 +320,4 @@ It will be in the `killed` state, which means the signal has been sent, but the
query itself has not hit an interrupt point.
**Resources:**
[Query Management](/influxdb/v1.0/troubleshooting/query_management/)
[Query Management](/influxdb/v1.5/troubleshooting/query_management/)

4
content/influxdb/v1.5/troubleshooting/query_management.md
View File

@ -56,7 +56,7 @@ Where `qid` is the query ID, displayed in the [`SHOW QUERIES`](/influxdb/v1.3/tr
```
KILL QUERY <qid>
```
***InfluxEnterprise clusters:*** To kill queries on a cluster, you need to specify the query ID (qid) and the TCP host (for example, `myhost:8088`),
***InfluxDB Enterprise clusters:*** To kill queries on a cluster, you need to specify the query ID (qid) and the TCP host (for example, `myhost:8088`),
available in the `SHOW QUERIES` output.
```
@ -73,7 +73,7 @@ A successful `KILL QUERY` query returns no results.
>
```
```
-- kill query on InfluxEnterprise cluster
-- kill query on InfluxDB Enterprise cluster
> KILL QUERY 53 ON "myhost:8088"
>
```

Some files were not shown because too many files have changed in this diff Show More