updated all latest links with latest shortcode, refactored related partial
parent
d35add6294
commit
e19505e719
|
@ -40,7 +40,7 @@ Chronograf offers a UI for [Kapacitor](https://github.com/influxdata/kapacitor),
|
|||
|
||||
* Create and delete databases and retention policies
|
||||
* View currently-running queries and stop inefficient queries from overloading your system
|
||||
* Create, delete, and assign permissions to users (Chronograf supports [InfluxDB OSS](/influxdb/latest/query_language/authentication_and_authorization/#authorization) and InfluxDB Enterprise user management)
|
||||
* Create, delete, and assign permissions to users (Chronograf supports [InfluxDB OSS](/{{< latest "influxdb" "v1" >}}/query_language/authentication_and_authorization/#authorization) and InfluxDB Enterprise user management)
|
||||
|
||||
|
||||
### Multi-organization and multi-user support
|
||||
|
|
|
@ -615,9 +615,9 @@ menu:
|
|||
### UI improvements
|
||||
|
||||
* When dashboard time range is changed, reset graphs that are zoomed in
|
||||
* [Bar graph](/chronograf/latest/troubleshooting/frequently-asked-questions/#bar) option added to dashboard
|
||||
* [Bar graph](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#bar) option added to dashboard
|
||||
* Redesign source management table to be more intuitive
|
||||
* Redesign [Line + Single Stat](/chronograf/latest/troubleshooting/frequently-asked-questions/#line-stat) cells to appear more like a sparkline, and improve legibility
|
||||
* Redesign [Line + Single Stat](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#line-stat) cells to appear more like a sparkline, and improve legibility
|
||||
|
||||
|
||||
## v1.3.2.0 [2017-06-05]
|
||||
|
@ -633,7 +633,7 @@ menu:
|
|||
|
||||
### Features
|
||||
|
||||
* Add UI to the Data Explorer for [writing data to InfluxDB](/chronograf/latest/guides/transition-web-admin-interface/#writing-data)
|
||||
* Add UI to the Data Explorer for [writing data to InfluxDB](/{{< latest "chronograf" >}}/guides/transition-web-admin-interface/#writing-data)
|
||||
|
||||
### UI improvements
|
||||
|
||||
|
@ -653,26 +653,26 @@ In versions 1.3.1+, installing a new version of Chronograf automatically clears
|
|||
|
||||
### Bug fixes
|
||||
|
||||
* Fix infinite spinner when `/chronograf` is a [basepath](/chronograf/latest/administration/configuration/#p-basepath)
|
||||
* Fix infinite spinner when `/chronograf` is a [basepath](/{{< latest "chronograf" >}}/administration/configuration/#p-basepath)
|
||||
* Remove the query templates dropdown from dashboard cell editor mode
|
||||
* Fix the backwards sort arrows in table column headers
|
||||
* Make the logout button consistent with design
|
||||
* Fix the loading spinner on graphs
|
||||
* Filter out any template variable values that are empty, whitespace, or duplicates
|
||||
* Allow users to click the add query button after selecting singleStat as the [visualization type](/chronograf/latest/troubleshooting/frequently-asked-questions/#what-visualization-types-does-chronograf-support)
|
||||
* Allow users to click the add query button after selecting singleStat as the [visualization type](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#what-visualization-types-does-chronograf-support)
|
||||
* Add a query for windows uptime - thank you, @brianbaker!
|
||||
|
||||
### Features
|
||||
|
||||
* Add log [event handler](/chronograf/latest/troubleshooting/frequently-asked-questions/#what-kapacitor-event-handlers-are-supported-in-chronograf) - thank you, @mpchadwick!
|
||||
* Add log [event handler](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#what-kapacitor-event-handlers-are-supported-in-chronograf) - thank you, @mpchadwick!
|
||||
* Update Go (golang) vendoring to dep and committed vendor directory
|
||||
* Add autocomplete functionality to [template variable](/chronograf/latest/guides/dashboard-template-variables/) dropdowns
|
||||
* Add autocomplete functionality to [template variable](/{{< latest "chronograf" >}}/guides/dashboard-template-variables/) dropdowns
|
||||
|
||||
### UI improvements
|
||||
|
||||
* Refactor scrollbars to support non-webkit browsers
|
||||
* Increase the query builder's default height in cell editor mode and in the data explorer
|
||||
* Make the [template variables](/chronograf/latest/guides/dashboard-template-variables/) manager more space efficient
|
||||
* Make the [template variables](/{{< latest "chronograf" >}}/guides/dashboard-template-variables/) manager more space efficient
|
||||
* Add page spinners to pages that did not have them
|
||||
* Denote which source is connected in the sources table
|
||||
* Use milliseconds in the InfluxDB dashboard instead of nanoseconds
|
||||
|
@ -682,25 +682,25 @@ In versions 1.3.1+, installing a new version of Chronograf automatically clears
|
|||
|
||||
### Bug fixes
|
||||
|
||||
* Fix the link to home when using the [`--basepath` option](/chronograf/latest/administration/configuration/#p-basepath)
|
||||
* Fix the link to home when using the [`--basepath` option](/{{< latest "chronograf" >}}/administration/configuration/#p-basepath)
|
||||
* Remove the notification to login on the login page
|
||||
* Support queries that perform math on functions
|
||||
* Prevent the creation of blank template variables
|
||||
* Ensure thresholds for Kapacitor Rule Alerts appear on page load
|
||||
* Update the Kapacitor configuration page when the configuration changes
|
||||
* Fix Authentication when using Chronograf with a set [basepath](/chronograf/latest/administration/configuration/#p-basepath)
|
||||
* Fix Authentication when using Chronograf with a set [basepath](/{{< latest "chronograf" >}}/administration/configuration/#p-basepath)
|
||||
* Show red indicator on Hosts Page for an offline host
|
||||
* Support escaping from presentation mode in Safari
|
||||
* Re-implement level colors on the alerts page
|
||||
* Fix router bug introduced by upgrading to react-router v3.0
|
||||
* Show legend on [Line+Stat](/chronograf/latest/troubleshooting/frequently-asked-questions/#line-stat) visualization type
|
||||
* Show legend on [Line+Stat](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#line-stat) visualization type
|
||||
* Prevent queries with `:dashboardTime:` from breaking the query builder
|
||||
|
||||
### Features
|
||||
|
||||
* Add line-protocol proxy for InfluxDB/InfluxDB Enterprise Cluster data sources
|
||||
* Add `:dashboardTime:` to support cell-specific time ranges on dashboards
|
||||
* Add support for enabling and disabling [TICKscripts that were created outside Chronograf](/chronograf/latest/guides/advanced-kapacitor/#tickscript-management)
|
||||
* Add support for enabling and disabling [TICKscripts that were created outside Chronograf](/{{< latest "chronograf" >}}/guides/advanced-kapacitor/#tickscript-management)
|
||||
* Allow users to delete Kapacitor configurations
|
||||
|
||||
### UI improvements
|
||||
|
|
|
@ -8,7 +8,7 @@ menu:
|
|||
parent: Administration
|
||||
---
|
||||
|
||||
The connection details form requires additional information when connecting Chronograf to an [InfluxDB Enterprise cluster](https://docs.influxdata.com/enterprise_influxdb/latest/).
|
||||
The connection details form requires additional information when connecting Chronograf to an [InfluxDB Enterprise cluster](/{{< latest "enterprise_influxdb" >}}/).
|
||||
|
||||
When you enter the InfluxDB HTTP bind address in the `Connection String` input, Chronograf automatically checks if that InfluxDB instance is a data node.
|
||||
If it is a data node, Chronograf automatically adds the `Meta Service Connection URL` input to the connection details form.
|
||||
|
@ -19,4 +19,4 @@ Enter the HTTP bind address of one of your cluster's meta nodes into that input
|
|||
Note that the example above assumes that you do not have authentication enabled.
|
||||
If you have authentication enabled, the form requires username and password information.
|
||||
|
||||
For details about monitoring InfluxDB Enterprise clusters, see [Monitoring InfluxDB Enterprise clusters](/chronograf/latest/guides/monitoring-influxenterprise-clusters/).
|
||||
For details about monitoring InfluxDB Enterprise clusters, see [Monitoring InfluxDB Enterprise clusters](/{{< latest "chronograf" >}}/guides/monitoring-influxenterprise-clusters/).
|
||||
|
|
|
@ -78,7 +78,7 @@ Environment variable: `$BOLT_PATH`
|
|||
|
||||
#### `--canned-path=` | `-c`
|
||||
|
||||
The path to the directory of [canned dashboards](/chronograf/latest/guides/using-precreated-dashboards/) files.
|
||||
The path to the directory of [canned dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards/) files.
|
||||
|
||||
Default value: `/usr/share/chronograf/canned`
|
||||
|
||||
|
|
|
@ -47,12 +47,12 @@ It is neither created nor used in macOS.
|
|||
|
||||
## Enabling security, multi-organization, and multi-user support
|
||||
|
||||
See [Managing security](/chronograf/latest/administration/managing-security) for details on configuring authentication options for Chronograf using the JWT and OAuth 2.0 authentication protocols.
|
||||
See [Managing security](/{{< latest "chronograf" >}}/administration/managing-security) for details on configuring authentication options for Chronograf using the JWT and OAuth 2.0 authentication protocols.
|
||||
|
||||
After you configure OAuth 2.0 authentication in Chronograf, you can use the multi-organization and multi-user support described in detail here:
|
||||
|
||||
* [Managing organizations](/chronograf/latest/administration/managing-organizations)
|
||||
* [Managing Chronograf users](/chronograf/latest/administration/managing-chronograf-users)
|
||||
* [Managing organizations](/{{< latest "chronograf" >}}/administration/managing-organizations)
|
||||
* [Managing Chronograf users](/{{< latest "chronograf" >}}/administration/managing-chronograf-users)
|
||||
|
||||
|
||||
<!-- TODO ## Configuring Chronograf for InfluxDB Enterprise clusters) -->
|
||||
|
|
|
@ -26,9 +26,9 @@ To create an InfluxDB connection in the Chronograf UI:
|
|||
* **Connection String**: Enter the hostname or IP address of the InfluxDB instance and the port. The field is prefilled with `http://localhost:8086`.
|
||||
* **Name**: Enter the name for this connection.
|
||||
* **Username**: Enter the username that will be shared for this connection.
|
||||
*Only required if [authorization is enabled](/influxdb/latest/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.*
|
||||
*Only required if [authorization is enabled](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.*
|
||||
* **Password**: Enter the password.
|
||||
*Only required if [authorization is enabled](/influxdb/latest/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.*
|
||||
*Only required if [authorization is enabled](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.*
|
||||
* **Telegraf Database**: Enter the name of the Telegraf database. The field is prefilled with `telegraf`.
|
||||
* **Default Retention Policy**: Enter the name of the default [retention policy](/influxdb/v1.6/concepts/glossary/#retention-policy-rp). If none is provided, it assumes `autogen`.
|
||||
* **Make this the default source**: By default, this option is selected and this InfluxDB connection will be used when Chronograf is launched.
|
||||
|
@ -75,11 +75,11 @@ Any string you want to use as the display name of the source.
|
|||
|
||||
#### `username`
|
||||
Username used to access the InfluxDB server or cluster.
|
||||
*Only required if [authorization is enabled](/influxdb/latest/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.*
|
||||
*Only required if [authorization is enabled](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.*
|
||||
|
||||
#### `password`
|
||||
Password used to access the InfluxDB server or cluster.
|
||||
*Only required if [authorization is enabled](/influxdb/latest/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.*
|
||||
*Only required if [authorization is enabled](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.*
|
||||
|
||||
#### `url`
|
||||
URL of the InfluxDB server or cluster.
|
||||
|
@ -143,9 +143,9 @@ To create a Kapacitor connection using the Chronograf UI:
|
|||
* **Kapacitor URL**: Enter the hostname or IP address of the Kapacitor instance and the port. The field is prefilled with `http://localhost:9092`.
|
||||
* **Name**: Enter the name for this connection.
|
||||
* **Username**: Enter the username that will be shared for this connection.
|
||||
*Only required if [authorization is enabled](/kapacitor/latest/administration/security/#kapacitor-authentication-and-authorization) on the Kapacitor instance or cluster to which you're connecting.*
|
||||
*Only required if [authorization is enabled](/{{< latest "kapacitor" >}}/administration/security/#kapacitor-authentication-and-authorization) on the Kapacitor instance or cluster to which you're connecting.*
|
||||
* **Password**: Enter the password.
|
||||
*Only required if [authorization is enabled](/kapacitor/latest/administration/security/#kapacitor-authentication-and-authorization) on the Kapacitor instance or cluster to which you're connecting.*
|
||||
*Only required if [authorization is enabled](/{{< latest "kapacitor" >}}/administration/security/#kapacitor-authentication-and-authorization) on the Kapacitor instance or cluster to which you're connecting.*
|
||||
|
||||
4. Click **Connect**. If the connection is valid, the message "Kapacitor Created! Configuring endpoints is optional." appears. To configure alert endpoints, see [Configuring alert endpoints](/chronograf/v1.6/guides/configuring-alert-endpoints/).
|
||||
|
||||
|
|
|
@ -13,7 +13,7 @@ menu:
|
|||
The **Chronograf Admin** provides InfluxDB user management for InfluxDB OSS and InfluxDB Enterprise users.
|
||||
|
||||
|
||||
> ***Note:*** For details on Chronograf user authentication and management, see [Managing security](/chronograf/latest/administration/managing-security/).
|
||||
> ***Note:*** For details on Chronograf user authentication and management, see [Managing security](/{{< latest "chronograf" >}}/administration/managing-security/).
|
||||
|
||||
**On this page:**
|
||||
|
||||
|
@ -58,7 +58,7 @@ Restart the InfluxDB service for your configuration changes to take effect:
|
|||
|
||||
### Step 3: Create an admin user.
|
||||
|
||||
Because authentication is enabled, you need to create an [admin user](/influxdb/latest/query_language/authentication_and_authorization/#user-types-and-privileges) before you can do anything else in the database.
|
||||
Because authentication is enabled, you need to create an [admin user](/{{< latest "influxdb" "v1" >}}/query_language/authentication_and_authorization/#user-types-and-privileges) before you can do anything else in the database.
|
||||
Run the `curl` command below to create an admin user, replacing:
|
||||
|
||||
* `localhost` with the IP or hostname of your InfluxDB OSS instance or one of your InfluxDB Enterprise data nodes
|
||||
|
@ -77,7 +77,7 @@ A successful `CREATE USER` query returns a blank result:
|
|||
|
||||
### Step 4: Edit the InfluxDB source in Chronograf.
|
||||
|
||||
If you've already [connected your database to Chronograf](/chronograf/latest/introduction/getting-started/#3-connect-to-chronograf), update the connection configuration in Chronograf with your new username and password.
|
||||
If you've already [connected your database to Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/#3-connect-to-chronograf), update the connection configuration in Chronograf with your new username and password.
|
||||
Edit existing InfluxDB database sources by navigating to the Chronograf configuration page and clicking on the name of the source.
|
||||
|
||||
## InfluxDB OSS User Management
|
||||
|
@ -91,7 +91,7 @@ On the **Chronograf Admin** page:
|
|||
![InfluxDB OSS user management](/img/chronograf/1-6-admin-usermanagement-oss.png)
|
||||
|
||||
InfluxDB users are either admin users or non-admin users.
|
||||
See InfluxDB's [authentication and authorization](/influxdb/latest/query_language/authentication_and_authorization/#user-types-and-privileges) documentation for more information about those user types.
|
||||
See InfluxDB's [authentication and authorization](/{{< latest "influxdb" "v1" >}}/query_language/authentication_and_authorization/#user-types-and-privileges) documentation for more information about those user types.
|
||||
|
||||
> ***Note:*** Note that Chronograf currently does not support assigning InfluxDB database `READ`or `WRITE` access to non-admin users.
|
||||
>This is a known issue.
|
||||
|
@ -156,12 +156,12 @@ Assign permissions and roles to both admin and non-admin users.
|
|||
Permission to add or remove nodes from a cluster.
|
||||
|
||||
**Relevant `influxd-ctl` arguments**:
|
||||
[`add-data`](/enterprise_influxdb/latest/features/cluster-commands/#add-data),
|
||||
[`add-meta`](/enterprise_influxdb/latest/features/cluster-commands/#add-meta),
|
||||
[`join`](/enterprise_influxdb/latest/features/cluster-commands/#join),
|
||||
[`remove-data`](/enterprise_influxdb/latest/features/cluster-commands/#remove-data),
|
||||
[`remove-meta`](/enterprise_influxdb/latest/features/cluster-commands/#remove-meta), and
|
||||
[`leave`](/enterprise_influxdb/latest/features/cluster-commands/#leave)
|
||||
[`add-data`](/{{< latest "enterprise_influxdb" >}}/features/cluster-commands/#add-data),
|
||||
[`add-meta`](/{{< latest "enterprise_influxdb" >}}/features/cluster-commands/#add-meta),
|
||||
[`join`](/{{< latest "enterprise_influxdb" >}}/features/cluster-commands/#join),
|
||||
[`remove-data`](/{{< latest "enterprise_influxdb" >}}/features/cluster-commands/#remove-data),
|
||||
[`remove-meta`](/{{< latest "enterprise_influxdb" >}}/features/cluster-commands/#remove-meta), and
|
||||
[`leave`](/{{< latest "enterprise_influxdb" >}}/features/cluster-commands/#leave)
|
||||
|
||||
**Pages in Chronograf that require this permission**: NA
|
||||
|
||||
|
@ -169,18 +169,18 @@ Permission to add or remove nodes from a cluster.
|
|||
Permission to copy shards.
|
||||
|
||||
**Relevant `influxd-ctl` arguments**:
|
||||
[copy-shard](/enterprise_influxdb/latest/features/cluster-commands/#copy-shard)
|
||||
[copy-shard](/{{< latest "enterprise_influxdb" >}}/features/cluster-commands/#copy-shard)
|
||||
|
||||
**Pages in Chronograf that require this permission**: NA
|
||||
|
||||
#### CreateDatabase
|
||||
Permission to create databases, create [retention policies](/influxdb/latest/concepts/glossary/#retention-policy-rp), alter retention policies, and view retention policies.
|
||||
Permission to create databases, create [retention policies](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#retention-policy-rp), alter retention policies, and view retention policies.
|
||||
|
||||
**Relevant InfluxQL queries**:
|
||||
[`CREATE DATABASE`](/influxdb/latest/query_language/database_management/#create-database),
|
||||
[`CREATE RETENTION POLICY`](/influxdb/latest/query_language/database_management/#create-retention-policies-with-create-retention-policy),
|
||||
[`ALTER RETENTION POLICY`](/influxdb/latest/query_language/database_management/#modify-retention-policies-with-alter-retention-policy), and
|
||||
[`SHOW RETENTION POLICIES`](/influxdb/latest/query_language/schema_exploration/#show-retention-policies)
|
||||
[`CREATE DATABASE`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#create-database),
|
||||
[`CREATE RETENTION POLICY`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#create-retention-policies-with-create-retention-policy),
|
||||
[`ALTER RETENTION POLICY`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#modify-retention-policies-with-alter-retention-policy), and
|
||||
[`SHOW RETENTION POLICIES`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-retention-policies)
|
||||
|
||||
**Pages in Chronograf that require this permission**: Dashboards, Data Explorer, and Databases on the Admin page
|
||||
|
||||
|
@ -188,25 +188,25 @@ Permission to create databases, create [retention policies](/influxdb/latest/con
|
|||
Permission to manage users and roles; create users, drop users, grant admin status to users, grant permissions to users, revoke admin status from users, revoke permissions from users, change user passwords, view user permissions, and view users and their admin status.
|
||||
|
||||
**Relevant InfluxQL queries**:
|
||||
[`CREATE USER`](/influxdb/latest/query_language/authentication_and_authorization/#user-management-commands),
|
||||
[`DROP USER`](/influxdb/latest/query_language/authentication_and_authorization/#general-admin-and-non-admin-user-management),
|
||||
[`GRANT ALL PRIVILEGES`](/influxdb/latest/query_language/authentication_and_authorization/#user-management-commands),
|
||||
[`GRANT [READ,WRITE,ALL]`](/influxdb/latest/query_language/authentication_and_authorization/#non-admin-user-management),
|
||||
[`REVOKE ALL PRIVILEGES`](/influxdb/latest/query_language/authentication_and_authorization/#user-management-commands),
|
||||
[`REVOKE [READ,WRITE,ALL]`](/influxdb/latest/query_language/authentication_and_authorization/#non-admin-user-management),
|
||||
[`SET PASSWORD`](/influxdb/latest/query_language/authentication_and_authorization/#general-admin-and-non-admin-user-management),
|
||||
[`SHOW GRANTS`](/influxdb/latest/query_language/authentication_and_authorization/#non-admin-user-management), and
|
||||
[`SHOW USERS`](/influxdb/latest/query_language/authentication_and_authorization/#user-management-commands)
|
||||
[`CREATE USER`](/{{< latest "influxdb" "v1" >}}/query_language/authentication_and_authorization/#user-management-commands),
|
||||
[`DROP USER`](/{{< latest "influxdb" "v1" >}}/query_language/authentication_and_authorization/#general-admin-and-non-admin-user-management),
|
||||
[`GRANT ALL PRIVILEGES`](/{{< latest "influxdb" "v1" >}}/query_language/authentication_and_authorization/#user-management-commands),
|
||||
[`GRANT [READ,WRITE,ALL]`](/{{< latest "influxdb" "v1" >}}/query_language/authentication_and_authorization/#non-admin-user-management),
|
||||
[`REVOKE ALL PRIVILEGES`](/{{< latest "influxdb" "v1" >}}/query_language/authentication_and_authorization/#user-management-commands),
|
||||
[`REVOKE [READ,WRITE,ALL]`](/{{< latest "influxdb" "v1" >}}/query_language/authentication_and_authorization/#non-admin-user-management),
|
||||
[`SET PASSWORD`](/{{< latest "influxdb" "v1" >}}/query_language/authentication_and_authorization/#general-admin-and-non-admin-user-management),
|
||||
[`SHOW GRANTS`](/{{< latest "influxdb" "v1" >}}/query_language/authentication_and_authorization/#non-admin-user-management), and
|
||||
[`SHOW USERS`](/{{< latest "influxdb" "v1" >}}/query_language/authentication_and_authorization/#user-management-commands)
|
||||
|
||||
**Pages in Chronograf that require this permission**: Data Explorer, Dashboards, Users and Roles on the Admin page
|
||||
|
||||
#### DropData
|
||||
Permission to drop data, in particular [series](/influxdb/latest/concepts/glossary/#series) and [measurements](/influxdb/latest/concepts/glossary/#measurement).
|
||||
Permission to drop data, in particular [series](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#series) and [measurements](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#measurement).
|
||||
|
||||
**Relevant InfluxQL queries**:
|
||||
[`DROP SERIES`](/influxdb/latest/query_language/database_management/#drop-series-from-the-index-with-drop-series),
|
||||
[`DELETE`](/influxdb/latest/query_language/database_management/#delete-series-with-delete), and
|
||||
[`DROP MEASUREMENT`](/influxdb/latest/query_language/database_management/#delete-measurements-with-drop-measurement)
|
||||
[`DROP SERIES`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#drop-series-from-the-index-with-drop-series),
|
||||
[`DELETE`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#delete-series-with-delete), and
|
||||
[`DROP MEASUREMENT`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#delete-measurements-with-drop-measurement)
|
||||
|
||||
**Pages in Chronograf that require this permission**: NA
|
||||
|
||||
|
@ -214,8 +214,8 @@ Permission to drop data, in particular [series](/influxdb/latest/concepts/glossa
|
|||
Permission to drop databases and retention policies.
|
||||
|
||||
**Relevant InfluxQL queries**:
|
||||
[`DROP DATABASE`](/influxdb/latest/query_language/database_management/#delete-a-database-with-drop-database) and
|
||||
[`DROP RETENTION POLICY`](/influxdb/latest/query_language/database_management/#delete-retention-policies-with-drop-retention-policy)
|
||||
[`DROP DATABASE`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#delete-a-database-with-drop-database) and
|
||||
[`DROP RETENTION POLICY`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#delete-retention-policies-with-drop-retention-policy)
|
||||
|
||||
**Pages in Chronograf that require this permission**: Data Explorer, Dashboards, Databases on the Admin page
|
||||
|
||||
|
@ -231,12 +231,12 @@ Permission to access the configuration-related API calls for InfluxKapacitor Ent
|
|||
**Pages in Chronograf that require this permission**: NA
|
||||
|
||||
#### ManageContinuousQuery
|
||||
Permission to create, drop, and view [continuous queries](/influxdb/latest/concepts/glossary/#continuous-query-cq).
|
||||
Permission to create, drop, and view [continuous queries](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#continuous-query-cq).
|
||||
|
||||
**Relevant InfluxQL queries**:
|
||||
[`CreateContinuousQueryStatement`](/influxdb/latest/query_language/continuous_queries/),
|
||||
[`CreateContinuousQueryStatement`](/{{< latest "influxdb" "v1" >}}/query_language/continuous_queries/),
|
||||
[`DropContinuousQueryStatement`](), and
|
||||
[`ShowContinuousQueriesStatement`](/influxdb/latest/query_language/continuous_queries/#list-cqs)
|
||||
[`ShowContinuousQueriesStatement`](/{{< latest "influxdb" "v1" >}}/query_language/continuous_queries/#list-cqs)
|
||||
|
||||
**Pages in Chronograf that require this permission**: Data Explorer, Dashboards
|
||||
|
||||
|
@ -244,28 +244,28 @@ Permission to create, drop, and view [continuous queries](/influxdb/latest/conce
|
|||
Permission to view and kill queries.
|
||||
|
||||
**Relevant InfluxQL queries**:
|
||||
[`SHOW QUERIES`](/influxdb/latest/troubleshooting/query_management/#list-currently-running-queries-with-show-queries) and
|
||||
[`KILL QUERY`](/influxdb/latest/troubleshooting/query_management/#stop-currently-running-queries-with-kill-query)
|
||||
[`SHOW QUERIES`](/{{< latest "influxdb" "v1" >}}/troubleshooting/query_management/#list-currently-running-queries-with-show-queries) and
|
||||
[`KILL QUERY`](/{{< latest "influxdb" "v1" >}}/troubleshooting/query_management/#stop-currently-running-queries-with-kill-query)
|
||||
|
||||
**Pages in Chronograf that require this permission**: Queries on the Admin page
|
||||
|
||||
#### ManageShard
|
||||
Permission to copy, delete, and view [shards](/influxdb/latest/concepts/glossary/#shard).
|
||||
Permission to copy, delete, and view [shards](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#shard).
|
||||
|
||||
**Relevant InfluxQL queries**:
|
||||
[`DropShardStatement`](/influxdb/latest/query_language/database_management/#delete-a-shard-with-drop-shard),
|
||||
[`ShowShardGroupsStatement`](/influxdb/latest/query_language/spec/#show-shard-groups), and
|
||||
[`ShowShardsStatement`](/influxdb/latest/query_language/spec/#show-shards)
|
||||
[`DropShardStatement`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#delete-a-shard-with-drop-shard),
|
||||
[`ShowShardGroupsStatement`](/{{< latest "influxdb" "v1" >}}/query_language/spec/#show-shard-groups), and
|
||||
[`ShowShardsStatement`](/{{< latest "influxdb" "v1" >}}/query_language/spec/#show-shards)
|
||||
|
||||
**Pages in Chronograf that require this permission**: NA
|
||||
|
||||
#### ManageSubscription
|
||||
Permission to create, drop, and view [subscriptions](/influxdb/latest/concepts/glossary/#subscription).
|
||||
Permission to create, drop, and view [subscriptions](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#subscription).
|
||||
|
||||
**Relevant InfluxQL queries**:
|
||||
[`CREATE SUBSCRIPTION`](/influxdb/latest/query_language/spec/#create-subscription),
|
||||
[`DROP SUBSCRIPTION`](/influxdb/latest/query_language/spec/#drop-subscription), and
|
||||
[`SHOW SUBSCRIPTIONS`](/influxdb/latest/query_language/spec/#show-subscriptions)
|
||||
[`CREATE SUBSCRIPTION`](/{{< latest "influxdb" "v1" >}}/query_language/spec/#create-subscription),
|
||||
[`DROP SUBSCRIPTION`](/{{< latest "influxdb" "v1" >}}/query_language/spec/#drop-subscription), and
|
||||
[`SHOW SUBSCRIPTIONS`](/{{< latest "influxdb" "v1" >}}/query_language/spec/#show-subscriptions)
|
||||
|
||||
**Pages in Chronograf that require this permission**: Alerting
|
||||
|
||||
|
@ -273,8 +273,8 @@ Permission to create, drop, and view [subscriptions](/influxdb/latest/concepts/g
|
|||
Permission to view cluster statistics and diagnostics.
|
||||
|
||||
**Relevant InfluxQL queries**:
|
||||
[`SHOW DIAGNOSTICS`](/influxdb/latest/troubleshooting/statistics/) and
|
||||
[`SHOW STATS`](/influxdb/latest/troubleshooting/statistics/)
|
||||
[`SHOW DIAGNOSTICS`](/{{< latest "influxdb" "v1" >}}/troubleshooting/statistics/) and
|
||||
[`SHOW STATS`](/{{< latest "influxdb" "v1" >}}/troubleshooting/statistics/)
|
||||
|
||||
**Pages in Chronograf that require this permission**: Data Explorer, Dashboards
|
||||
|
||||
|
@ -282,12 +282,12 @@ Permission to view cluster statistics and diagnostics.
|
|||
Permission to read data.
|
||||
|
||||
**Relevant InfluxQL queries**:
|
||||
[`SHOW FIELD KEYS`](/influxdb/latest/query_language/schema_exploration/#show-field-keys),
|
||||
[`SHOW MEASUREMENTS`](/influxdb/latest/query_language/schema_exploration/#show-measurements),
|
||||
[`SHOW SERIES`](/influxdb/latest/query_language/schema_exploration/#show-series),
|
||||
[`SHOW TAG KEYS`](/influxdb/latest/query_language/schema_exploration/#show-tag-keys),
|
||||
[`SHOW TAG VALUES`](/influxdb/latest/query_language/schema_exploration/#show-tag-values), and
|
||||
[`SHOW RETENTION POLICIES`](/influxdb/latest/query_language/schema_exploration/#show-retention-policies)
|
||||
[`SHOW FIELD KEYS`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-field-keys),
|
||||
[`SHOW MEASUREMENTS`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-measurements),
|
||||
[`SHOW SERIES`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-series),
|
||||
[`SHOW TAG KEYS`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-tag-keys),
|
||||
[`SHOW TAG VALUES`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-tag-values), and
|
||||
[`SHOW RETENTION POLICIES`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-retention-policies)
|
||||
|
||||
**Pages in Chronograf that require this permission**: Admin, Alerting, Dashboards, Data Explorer, Host List
|
||||
|
||||
|
|
|
@ -22,7 +22,7 @@ menu:
|
|||
|
||||
> ***Note:*** Support for organizations and distinct users with role-based access control is new in Chronograf 1.4.
|
||||
>
|
||||
> For information about the new user roles and SuperAdmin status, see [Managing Chronograf users](/chronograf/latest/administration/managing-chronograf-users/).
|
||||
> For information about the new user roles and SuperAdmin status, see [Managing Chronograf users](/{{< latest "chronograf" >}}/administration/managing-chronograf-users/).
|
||||
|
||||
A Chronograf organization is a collection of Chronograf users who share common Chronograf-owned resources, including dashboards, InfluxDB connections, and Kapacitor connections. Organizations can be used to represent companies, functional units, projects, or teams. Chronograf users can be members of multiple organizations.
|
||||
|
||||
|
@ -67,8 +67,8 @@ You can configure existing and new organizations in the **Organizations** tab of
|
|||
|
||||
See the following pages for more information about managing Chronograf users and security:
|
||||
|
||||
* [Managing Chronograf users](/chronograf/latest/administration/managing-chronograf-users/)
|
||||
* [Managing security](/chronograf/latest/administration/managing-security/)
|
||||
* [Managing Chronograf users](/{{< latest "chronograf" >}}/administration/managing-chronograf-users/)
|
||||
* [Managing security](/{{< latest "chronograf" >}}/administration/managing-security/)
|
||||
|
||||
## Mapping organizations
|
||||
|
||||
|
|
|
@ -8,7 +8,7 @@ aliases:
|
|||
- /chronograf/v1.6/guides/transition-web-admin-interface/
|
||||
---
|
||||
|
||||
Versions 1.3 and later of [InfluxDB](/influxdb/latest/) and [InfluxDB Enterprise](/enterprise/latest/) do not support the [web admin interface](/influxdb/latest/tools/web_admin/), the builtin user interface for writing and querying data in InfluxDB.
|
||||
Versions 1.3 and later of [InfluxDB](/{{< latest "influxdb" "v1" >}}/) and [InfluxDB Enterprise](/enterprise/latest/) do not support the [web admin interface](/{{< latest "influxdb" "v1" >}}/tools/web_admin/), the builtin user interface for writing and querying data in InfluxDB.
|
||||
Chronograf replaces the web admin interface with improved tooling for querying data, writing data, and database management.
|
||||
|
||||
The following sections describe the Chronograf features that relate to the web admin interface:
|
||||
|
@ -23,7 +23,7 @@ The following sections describe the Chronograf features that relate to the web a
|
|||
### Web admin interface
|
||||
|
||||
In the web admin interface, users chose the target database in the top right corner and selected from a set of query templates in the `Query Templates` dropdown.
|
||||
The templates included queries with no user-provided values (example: [`SHOW MEASUREMENTS`](/influxdb/latest/query_language/schema_exploration/#show-measurements)) and queries with user-provided values (example: [`SHOW TAG KEYS FROM "<measurement_name>"`](/influxdb/latest/query_language/schema_exploration/#show-tag-keys)).
|
||||
The templates included queries with no user-provided values (example: [`SHOW MEASUREMENTS`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-measurements)) and queries with user-provided values (example: [`SHOW TAG KEYS FROM "<measurement_name>"`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-tag-keys)).
|
||||
|
||||
![WAI Query Templates](/img/chronograf/1-6-g-admin-webtemplates.png)
|
||||
|
||||
|
@ -39,7 +39,7 @@ Note that unlike the web admin interface, Chronograf does not have a database dr
|
|||
|
||||
### Web admin interface
|
||||
|
||||
To write data to InfluxDB, users selected the target database in the top right corner, clicked the `Write Data` icon, and entered their [line protocol](/influxdb/latest/concepts/glossary/#line-protocol) in the text input:
|
||||
To write data to InfluxDB, users selected the target database in the top right corner, clicked the `Write Data` icon, and entered their [line protocol](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#line-protocol) in the text input:
|
||||
|
||||
![WAI Writing Data](/img/chronograf/1-6-g-admin-write.png)
|
||||
|
||||
|
@ -55,7 +55,7 @@ Next, enter your line protocol in the main text box and click the `Write` button
|
|||
|
||||
### Web admin interface
|
||||
|
||||
In the web admin interface, the `Query Template` dropdown was the only way to manage databases and [retention policies](/influxdb/latest/concepts/glossary/#retention-policy-rp) (RP):
|
||||
In the web admin interface, the `Query Template` dropdown was the only way to manage databases and [retention policies](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#retention-policy-rp) (RP):
|
||||
|
||||
![WAI DBRP Management](/img/chronograf/1-6-g-admin-webdbrp.png)
|
||||
|
||||
|
@ -80,7 +80,7 @@ In the web admin interface, the `Query Template` dropdown was the only way to ma
|
|||
### Chronograf
|
||||
|
||||
In Chronograf, the `Admin` page includes a complete interface for user management.
|
||||
The `Admin` page supports both InfluxDB OSS users and InfluxDB Enterprise users; see the [User Management](/chronograf/latest/administration/user-management/) page for more information.
|
||||
The `Admin` page supports both InfluxDB OSS users and InfluxDB Enterprise users; see the [User Management](/{{< latest "chronograf" >}}/administration/user-management/) page for more information.
|
||||
The `Admin` page allows users to:
|
||||
|
||||
* View, create, and delete users
|
||||
|
|
|
@ -24,4 +24,4 @@ Users can continue to use the deprecated product; documentation is available und
|
|||
For more information, please read the original [announcement blog](https://www.influxdata.com/announcing-the-new-chronograf-a-ui-for-the-tick-stack-and-a-complete-open-source-monitoring-solution/) by our CTO, Paul Dix.
|
||||
|
||||
InfluxData recommends migrating to the open source Chronograf product.
|
||||
See [Getting Started](/chronograf/latest/introduction/getting-started/) to get up and running!
|
||||
See [Getting Started](/{{< latest "chronograf" >}}/introduction/getting-started/) to get up and running!
|
||||
|
|
|
@ -17,7 +17,7 @@ Pre-created dashboards are available when the required Telegraf input plugins ar
|
|||
|
||||
Using the TICKscript editor in Chronograf to create, test, and debug Kapacitor TICKscripts.
|
||||
|
||||
## [Creating dashboards](/chronograf/latest/guides/create-a-dashboard/)
|
||||
## [Creating dashboards](/{{< latest "chronograf" >}}/guides/create-a-dashboard/)
|
||||
|
||||
Chronograf offers a complete dashboard solution for visualizing your data and monitoring your infrastructure.
|
||||
Learn how to create customized dashboards in Chronograf.
|
||||
|
|
|
@ -13,16 +13,16 @@ menu:
|
|||
* [TICKscript management](#tickscript-management)
|
||||
|
||||
|
||||
Chronograf provides a user interface for [Kapacitor](/kapacitor/latest/), InfluxData's processing framework for creating alerts, running ETL jobs, and detecting anomalies in your data.
|
||||
Chronograf provides a user interface for [Kapacitor](/{{< latest "kapacitor" >}}/), InfluxData's processing framework for creating alerts, running ETL jobs, and detecting anomalies in your data.
|
||||
This guide offers insights into how Kapacitor interacts with Chronograf and introduces advanced Kapacitor usage within Chronograf.
|
||||
|
||||
|
||||
## Alert history management
|
||||
|
||||
Chronograf stores the information on the Alert History page as time series data in InfluxDB.
|
||||
It stores it in the `chronograf` database and in the `alerts` [measurement](/influxdb/latest/concepts/glossary/#measurement).
|
||||
By default, this data is subject to an infinite [retention policy](/influxdb/latest/concepts/glossary/#retention-policy-rp) (RP), that is, InfluxDB stores them forever.
|
||||
Users who expect to have a large number of alerts and users who do not want to store their alert history forever may want to shorten the [duration](/influxdb/latest/concepts/glossary/#duration) of that retention policy.
|
||||
It stores it in the `chronograf` database and in the `alerts` [measurement](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#measurement).
|
||||
By default, this data is subject to an infinite [retention policy](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#retention-policy-rp) (RP), that is, InfluxDB stores them forever.
|
||||
Users who expect to have a large number of alerts and users who do not want to store their alert history forever may want to shorten the [duration](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#duration) of that retention policy.
|
||||
|
||||
### Modifying the retention policy in Chronograf
|
||||
|
||||
|
@ -36,7 +36,7 @@ In the Databases tab:
|
|||
#### Step 2: Enter a different duration
|
||||
|
||||
The minimum allowable duration is one hour (`1h`) and the maximum is infinite (`INF`).
|
||||
See the InfluxDB documentation for the list of [acceptable duration units](/influxdb/latest/query_language/spec/#duration-units).
|
||||
See the InfluxDB documentation for the list of [acceptable duration units](/{{< latest "influxdb" "v1" >}}/query_language/spec/#duration-units).
|
||||
|
||||
#### Step 3: Click the green check mark to save your changes
|
||||
|
||||
|
@ -56,7 +56,7 @@ The fourth alert, which occurred on the same day at 16:58:50, is outside the pre
|
|||
|
||||
Chronograf creates Kapacitor tasks using the information that you provide on the Rule Configuration page.
|
||||
It uses that information to communicate with Kapacitor and populate Chronograf alert pages.
|
||||
Pre-existing tasks, or [TICKscripts](/kapacitor/latest/tick/), that you created and enabled on your Kapacitor instance without using Chronograf, have limited functionality in the user interface.
|
||||
Pre-existing tasks, or [TICKscripts](/{{< latest "kapacitor" >}}/tick/), that you created and enabled on your Kapacitor instance without using Chronograf, have limited functionality in the user interface.
|
||||
|
||||
In Chronograf, you can:
|
||||
|
||||
|
|
|
@ -11,7 +11,7 @@ Chronograf gives you the ability to view, search, filter, visualize, and analyze
|
|||
This helps to recognize and diagnose patterns, then quickly dive into logged events that lead up to events.
|
||||
|
||||
## Logging setup
|
||||
Logs data is a first class citizen in InfluxDB and is populated using available log-related [Telegraf input plugins](/telegraf/latest/plugins/inputs/):
|
||||
Logs data is a first class citizen in InfluxDB and is populated using available log-related [Telegraf input plugins](/{{< latest "telegraf" >}}/plugins/inputs/):
|
||||
|
||||
[syslog](https://github.com/influxdata/telegraf/tree/release-1.7/plugins/inputs/syslog)
|
||||
|
||||
|
|
|
@ -17,7 +17,7 @@ This guide offers step-by-step instructions for configuring Chronograf alert end
|
|||
|
||||
## Kapacitor event handlers supported in Chronograf
|
||||
|
||||
Chronograf integrates with [Kapacitor](/kapacitor/latest/), InfluxData's data processing platform, to send alert messages to event handlers.
|
||||
Chronograf integrates with [Kapacitor](/{{< latest "kapacitor" >}}/), InfluxData's data processing platform, to send alert messages to event handlers.
|
||||
Chronograf supports the following event handlers:
|
||||
|
||||
* Alerta
|
||||
|
@ -38,7 +38,7 @@ Chronograf supports the following event handlers:
|
|||
* TCP
|
||||
* VictorOps
|
||||
|
||||
To configure a Kapacitor event handler in Chronograf, [install Kapacitor](/chronograf/latest/introduction/getting-started/#kapacitor-setup) and [connect it to Chronograf](/chronograf/latest/introduction/getting-started/#4-connect-chronograf-to-kapacitor).
|
||||
To configure a Kapacitor event handler in Chronograf, [install Kapacitor](/{{< latest "chronograf" >}}/introduction/getting-started/#kapacitor-setup) and [connect it to Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/#4-connect-chronograf-to-kapacitor).
|
||||
The **Configure Kapacitor** page includes the event handler configuration options.
|
||||
|
||||
|
||||
|
@ -46,10 +46,10 @@ The **Configure Kapacitor** page includes the event handler configuration option
|
|||
|
||||
Alert endpoint configurations appear on the Chronograf Configure Kapacitor page.
|
||||
You must have a connected Kapacitor instance to access the configurations.
|
||||
For more information, see [Kapacitor installation instructions](/chronograf/latest/introduction/getting-started/#kapacitor-setup) and how to [connect a Kapacitor instance](/chronograf/latest/introduction/getting-started/#4-connect-chronograf-to-kapacitor) to Chronograf.
|
||||
For more information, see [Kapacitor installation instructions](/{{< latest "chronograf" >}}/introduction/getting-started/#kapacitor-setup) and how to [connect a Kapacitor instance](/{{< latest "chronograf" >}}/introduction/getting-started/#4-connect-chronograf-to-kapacitor) to Chronograf.
|
||||
|
||||
Note that the configuration options in the **Configure alert endpoints** section are not all-inclusive.
|
||||
Some event handlers allow users to customize event handler configurations per [alert rule](/chronograf/latest/guides/create-a-kapacitor-alert/).
|
||||
Some event handlers allow users to customize event handler configurations per [alert rule](/{{< latest "chronograf" >}}/guides/create-a-kapacitor-alert/).
|
||||
For example, Chronograf's Slack integration allows users to specify a default channel in the **Configure alert endpoints** section and a different channel for individual alert rules.
|
||||
|
||||
### HipChat
|
||||
|
@ -113,7 +113,7 @@ Your token appears in the table just above the **Create new token** section:
|
|||
3. Click **Save Changes** to save the configuration settings.
|
||||
4. Click **Send Test Alert** to verify the configuration.
|
||||
|
||||
See [Kafka event handler (Kapacitor)](/kapacitor/latest/event_handlers/kafka/) in the Kapacitor documentation for details about enabling OpsGenie services using TICKscripts.
|
||||
See [Kafka event handler (Kapacitor)](/{{< latest "kapacitor" >}}/event_handlers/kafka/) in the Kapacitor documentation for details about enabling OpsGenie services using TICKscripts.
|
||||
|
||||
|
||||
### OpsGenie
|
||||
|
@ -140,9 +140,9 @@ Send an incident alert to OpsGenie teams and recipients using the Chronograf ale
|
|||
|
||||
See [Alert API](https://docs.opsgenie.com/docs/alert-api) in the OpsGenie documentation for details on the OpsGenie Alert API
|
||||
|
||||
See [OpsGenie V2 event handler](/kapacitor/latest/event_handlers/opsgenie/v2/) in the Kapacitor documentation for details about the OpsGenie V2 event handler.
|
||||
See [OpsGenie V2 event handler](/{{< latest "kapacitor" >}}/event_handlers/opsgenie/v2/) in the Kapacitor documentation for details about the OpsGenie V2 event handler.
|
||||
|
||||
See the [AlertNode (Kapacitor TICKscript node) - OpsGenie v2](/kapacitor/latest/nodes/alert_node/#opsgenie-v2) in the Kapacitor documentation for details about enabling OpsGenie services using TICKscripts.
|
||||
See the [AlertNode (Kapacitor TICKscript node) - OpsGenie v2](/{{< latest "kapacitor" >}}/nodes/alert_node/#opsgenie-v2) in the Kapacitor documentation for details about enabling OpsGenie services using TICKscripts.
|
||||
|
||||
### PagerDuty
|
||||
|
||||
|
@ -166,7 +166,7 @@ Send an alerts about recognized events to PagerDuty using the Chronograf PagerDu
|
|||
|
||||
See the [PagerDuty Events API V2 Overview](https://v2.developer.pagerduty.com/docs/events-api-v2) for details on the PagerDuty Events API and recognized event types (`trigger`, `acknowledge`, and `resolve`).
|
||||
|
||||
See [AlertNode (Kapacitor TICKscript node) - PagerDuty v2](/kapacitor/latest/nodes/alert_node/#pagerduty-v2) in the Kapacitor documentation for details about enabling a new "Generic API" service using TICKscripts.
|
||||
See [AlertNode (Kapacitor TICKscript node) - PagerDuty v2](/{{< latest "kapacitor" >}}/nodes/alert_node/#pagerduty-v2) in the Kapacitor documentation for details about enabling a new "Generic API" service using TICKscripts.
|
||||
|
||||
|
||||
### Slack
|
||||
|
|
|
@ -9,7 +9,7 @@ menu:
|
|||
---
|
||||
|
||||
Chronograf offers a complete dashboard solution for visualizing your data and monitoring your infrastructure.
|
||||
Use Chronograf's [pre-created dashboards](/chronograf/latest/guides/using-precreated-dashboards) or create custom dashboards to meet your requirements.
|
||||
Use Chronograf's [pre-created dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards) or create custom dashboards to meet your requirements.
|
||||
This guide shows you how to create custom Chronograf dashboards.
|
||||
|
||||
By the end of this guide, you'll be aware of the tools available to you for creating dashboards similar to this example:
|
||||
|
@ -20,7 +20,7 @@ By the end of this guide, you'll be aware of the tools available to you for crea
|
|||
|
||||
To perform the tasks in this guide, you must have a working Chronograf instance that is connected to an InfluxDB source.
|
||||
Data is accessed using the Telegraf [system ](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/system) input plugins.
|
||||
For more information, see [Configuring Chronograf](/chronograf/latest/administration/configuration).
|
||||
For more information, see [Configuring Chronograf](/{{< latest "chronograf" >}}/administration/configuration).
|
||||
|
||||
## Build a Dashboard
|
||||
|
||||
|
@ -40,13 +40,13 @@ to open the cell editor mode.
|
|||
|
||||
### Step 3: Create your query
|
||||
|
||||
Click the **Add a Query** button to create an [InfluxQL](/influxdb/latest/query_language/) query.
|
||||
Click the **Add a Query** button to create an [InfluxQL](/{{< latest "influxdb" "v1" >}}/query_language/) query.
|
||||
In query editor mode, use the builder to select from your existing data and allow Chronograf to format the query for you.
|
||||
Alternatively, manually enter and edit a query.
|
||||
Chronograf allows you to move seamlessly between using the builder and manually editing the query; when possible, the interface automatically populates the builder with the information from your raw query.
|
||||
|
||||
For our example, the query builder is used to generate a query that shows the average idle CPU usage grouped by host (in this case, there are three hosts).
|
||||
By default, Chronograf applies the [`MEAN()` function](/influxdb/latest/query_language/functions/#mean) to the data, groups averages into auto-generated time intervals (`:interval:`), and shows data for the past hour (`:dashboardTime:`).
|
||||
By default, Chronograf applies the [`MEAN()` function](/{{< latest "influxdb" "v1" >}}/query_language/functions/#mean) to the data, groups averages into auto-generated time intervals (`:interval:`), and shows data for the past hour (`:dashboardTime:`).
|
||||
Those defaults are configurable using the query builder or by manually editing the query.
|
||||
|
||||
In addition, the time range (`:dashboardTime:`) is [configurable on the dashboard](#step-6-configure-your-dashboard).
|
||||
|
@ -55,7 +55,7 @@ In addition, the time range (`:dashboardTime:`) is [configurable on the dashboar
|
|||
|
||||
### Step 4: Choose your visualization type
|
||||
|
||||
Chronograf supports many different [visualization types](/chronograf/latest/guides/visualization-types/). To choose a visualization type, click **Visualization** and select **Step-Plot Graph**.
|
||||
Chronograf supports many different [visualization types](/{{< latest "chronograf" >}}/guides/visualization-types/). To choose a visualization type, click **Visualization** and select **Step-Plot Graph**.
|
||||
|
||||
![Visualization type](/img/chronograf/1-6-g-dashboard-visualization.png)
|
||||
|
||||
|
@ -77,7 +77,7 @@ Click **Save** (the green checkmark icon) to save your cell.
|
|||
* **Reset** your cell by double-clicking your mouse in the cell window
|
||||
|
||||
> Note:
|
||||
These tips only apply to the line, stacked, step-plot, and line+stat [visualization types](/chronograf/latest/troubleshooting/frequently-asked-questions/#what-visualization-types-does-chronograf-support).
|
||||
These tips only apply to the line, stacked, step-plot, and line+stat [visualization types](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#what-visualization-types-does-chronograf-support).
|
||||
|
||||
#### Configure dashboard-wide settings:
|
||||
* You can change the dashboard's *auto-refresh interval* at the top of the page - the default interval selected is **Every 15 seconds**.
|
||||
|
@ -93,4 +93,4 @@ To exit full screen mode, press the Esc key.
|
|||
|
||||
### Template variables
|
||||
Dashboards support template variables.
|
||||
See the [Dashboard Template Variables](/chronograf/latest/guides/dashboard-template-variables/) guide for more information.
|
||||
See the [Dashboard Template Variables](/{{< latest "chronograf" >}}/guides/dashboard-template-variables/) guide for more information.
|
||||
|
|
|
@ -11,9 +11,9 @@ menu:
|
|||
---
|
||||
|
||||
|
||||
Chronograf provides a user interface for [Kapacitor](/kapacitor/latest/), InfluxData's processing framework for creating alerts, ETL jobs (running extract, transform, load), and detecting anomalies in your data.
|
||||
Chronograf provides a user interface for [Kapacitor](/{{< latest "kapacitor" >}}/), InfluxData's processing framework for creating alerts, ETL jobs (running extract, transform, load), and detecting anomalies in your data.
|
||||
Chronograf alert rules correspond to Kapacitor tasks that trigger alerts whenever certain conditions are met.
|
||||
Behind the scenes, these tasks are stored as [TICKscripts](/kapacitor/latest/tick/) that can be edited manually or through Chronograf.
|
||||
Behind the scenes, these tasks are stored as [TICKscripts](/{{< latest "kapacitor" >}}/tick/) that can be edited manually or through Chronograf.
|
||||
Common alerting use cases that can be managed using Chronograf include:
|
||||
|
||||
* Thresholds with static ceilings, floors, and ranges.
|
||||
|
@ -26,13 +26,13 @@ This guide walks through creating a Chronograf alert rule that sends an alert me
|
|||
|
||||
## Requirements
|
||||
|
||||
[Getting started with Chronograf](/chronograf/latest/introduction/getting-started/) offers step-by-step instructions for each of the following requirements:
|
||||
[Getting started with Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/) offers step-by-step instructions for each of the following requirements:
|
||||
|
||||
* Downloaded and install the entire TICKstack (Telegraf, InfluxDB, Chronograf, and Kapacitor).
|
||||
* Configure Telegraf to collect data using the InfluxDB [system statistics](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/system) input plugin and write data to your InfluxDB instance.
|
||||
* [Create a Kapacitor connection in Chronograf](/chronograf/latest/introduction/getting-started/#4-connect-chronograf-to-kapacitor).
|
||||
* Slack is available and configured as an [event handler](/chronograf/latest/troubleshooting/frequently-asked-questions/#what-kapacitor-event-handlers-are-supported-in-chronograf) in Chronograf.
|
||||
See the [Configuring Kapacitor Event Handlers](/chronograf/latest/guides/configuring-alert-endpoints/) guide for detailed configuration instructions.
|
||||
* [Create a Kapacitor connection in Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/#4-connect-chronograf-to-kapacitor).
|
||||
* Slack is available and configured as an [event handler](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#what-kapacitor-event-handlers-are-supported-in-chronograf) in Chronograf.
|
||||
See the [Configuring Kapacitor Event Handlers](/{{< latest "chronograf" >}}/guides/configuring-alert-endpoints/) guide for detailed configuration instructions.
|
||||
|
||||
## Configuring Chronograf alert rules
|
||||
|
||||
|
@ -70,7 +70,7 @@ For this example, select the **Threshold** alert type.
|
|||
Choose the time series data you want the Chronograf alert rule to use.
|
||||
Navigate through databases, measurements, fields, and tags to select the relevant data.
|
||||
|
||||
In this example, select the `telegraf` [database](/influxdb/latest/concepts/glossary/#database), the `autogen` [retention policy](/influxdb/latest/concepts/glossary/#retention-policy-rp), the `cpu` [measurement](/influxdb/latest/concepts/glossary/#measurement), and the `usage_idle` [field](/influxdb/latest/concepts/glossary/#field).
|
||||
In this example, select the `telegraf` [database](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#database), the `autogen` [retention policy](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#retention-policy-rp), the `cpu` [measurement](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#measurement), and the `usage_idle` [field](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#field).
|
||||
|
||||
![Select your data](/img/chronograf/1-6-alerts-time-series.png)
|
||||
|
||||
|
@ -113,7 +113,7 @@ In this example, use the alert message, `Your idle CPU usage is {{.Level}} at {{
|
|||
|
||||
![Specify event handler and alert message](/img/chronograf/1-6-alerts-message.png)
|
||||
|
||||
*View the Kapacitor documentation for more information about [message template data](/kapacitor/latest/nodes/alert_node/#message).*
|
||||
*View the Kapacitor documentation for more information about [message template data](/{{< latest "kapacitor" >}}/nodes/alert_node/#message).*
|
||||
|
||||
### Step 7: Save the alert rule
|
||||
|
||||
|
|
|
@ -115,7 +115,7 @@ Chronograf supports the following template variable types:
|
|||
[Text](#text)
|
||||
|
||||
### Databases
|
||||
Database template variables allow you to select from multiple target [databases](/influxdb/latest/concepts/glossary/#database).
|
||||
Database template variables allow you to select from multiple target [databases](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#database).
|
||||
|
||||
_**Database meta query**_
|
||||
Database template variables use the following meta query to return an array of all databases in your InfluxDB instance.
|
||||
|
@ -133,7 +133,7 @@ SELECT "purchases" FROM :databaseVar:."autogen"."customers"
|
|||
Database template variables are good when visualizing multiple databases with similar or identical data structures. They allow you to quickly switch between visualizations for each of your databases.
|
||||
|
||||
### Measurements
|
||||
Vary the target [measurement](/influxdb/latest/concepts/glossary/#measurement).
|
||||
Vary the target [measurement](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#measurement).
|
||||
|
||||
_**Measurement meta query**_
|
||||
Measurement template variables use the following meta query to return an array of all measurements in a given database.
|
||||
|
@ -152,7 +152,7 @@ Measurement template variables allow you to quickly switch between measurements
|
|||
|
||||
|
||||
### Field Keys
|
||||
Vary the target [field key](/influxdb/latest/concepts/glossary/#field-key).
|
||||
Vary the target [field key](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#field-key).
|
||||
|
||||
_**Field key meta query**_
|
||||
Field key template variables use the following meta query to return an array of all field keys in a given measurement from a given database.
|
||||
|
@ -171,7 +171,7 @@ Field key template variables are great if you want to quickly switch between fie
|
|||
|
||||
|
||||
### Tag Keys
|
||||
Vary the target [tag key](/influxdb/latest/concepts/glossary/#tag-key).
|
||||
Vary the target [tag key](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-key).
|
||||
|
||||
_**Tag key meta query**_
|
||||
Tag key template variables use the following meta query to return an array of all tag keys in a given measurement from a given database.
|
||||
|
@ -190,7 +190,7 @@ Tag key template variables are great if you want to quickly switch between tag k
|
|||
|
||||
|
||||
### Tag Values
|
||||
Vary the target [tag value](/influxdb/latest/concepts/glossary/#tag-value).
|
||||
Vary the target [tag value](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-value).
|
||||
|
||||
_**Tag value meta query**_
|
||||
Tag value template variables use the following meta query to return an array of all values associated with a given tag key in a specified measurement and database.
|
||||
|
@ -222,7 +222,7 @@ value3
|
|||
value4
|
||||
```
|
||||
|
||||
> Since string field values [require single quotes in InfluxQL](/influxdb/latest/troubleshooting/frequently-asked-questions/#when-should-i-single-quote-and-when-should-i-double-quote-in-queries), string values should be wrapped in single quotes.
|
||||
> Since string field values [require single quotes in InfluxQL](/{{< latest "influxdb" "v1" >}}/troubleshooting/frequently-asked-questions/#when-should-i-single-quote-and-when-should-i-double-quote-in-queries), string values should be wrapped in single quotes.
|
||||
|
||||
>```csv
|
||||
'string1','string2','string3','string4'
|
||||
|
@ -253,7 +253,7 @@ key4,value4
|
|||
|
||||
<img src="/img/chronograf/1-6-template-vars-map-dropdown.png" style="width:100%;max-width:140px;" alt="Map variable dropdown"/>
|
||||
|
||||
> If values are meant to be used as string field values, wrap them in single quote ([required by InfluxQL](/influxdb/latest/troubleshooting/frequently-asked-questions/#when-should-i-single-quote-and-when-should-i-double-quote-in-queries)). This only pertains to values. String keys do not matter.
|
||||
> If values are meant to be used as string field values, wrap them in single quote ([required by InfluxQL](/{{< latest "influxdb" "v1" >}}/troubleshooting/frequently-asked-questions/#when-should-i-single-quote-and-when-should-i-double-quote-in-queries)). This only pertains to values. String keys do not matter.
|
||||
|
||||
>```csv
|
||||
key1,'value1'
|
||||
|
|
|
@ -40,7 +40,7 @@ Add the following settings the `[[udp]]` secton in your Kapacitor configuration
|
|||
retention-policy = "autogen"
|
||||
```
|
||||
|
||||
Using this configuration, Kapacitor will listen on port `9100` for UDP packets in [Line Protocol](/influxdb/latest/write_protocols/line_protocol_tutorial/) format.
|
||||
Using this configuration, Kapacitor will listen on port `9100` for UDP packets in [Line Protocol](/{{< latest "influxdb" "v1" >}}/write_protocols/line_protocol_tutorial/) format.
|
||||
Incoming data will be scoped to be in the `game.autogen` database and retention policy.
|
||||
Restart Kapacitor so that the UDP listener service starts.
|
||||
|
||||
|
|
|
@ -10,20 +10,20 @@ menu:
|
|||
|
||||
---
|
||||
|
||||
[InfluxDB Enterprise](/enterprise_influxdb/latest/) offers high availability and a highly scalable clustering solution for your time series data needs.
|
||||
[InfluxDB Enterprise](/{{< latest "enterprise_influxdb" >}}/) offers high availability and a highly scalable clustering solution for your time series data needs.
|
||||
Use Chronograf to assess your cluster's health and to monitor the infrastructure behind your project.
|
||||
|
||||
This guide offers step-by-step instructions for using Chronograf, [InfluxDB](/influxdb/latest/), and [Telegraf](/telegraf/latest/) to monitor data nodes in your InfluxDB Enterprise cluster.
|
||||
This guide offers step-by-step instructions for using Chronograf, [InfluxDB](/{{< latest "influxdb" "v1" >}}/), and [Telegraf](/{{< latest "telegraf" >}}/) to monitor data nodes in your InfluxDB Enterprise cluster.
|
||||
|
||||
## Requirements
|
||||
|
||||
You have a fully-functioning InfluxDB Enterprise cluster with authentication enabled.
|
||||
See the InfluxDB Enterprise documentation for
|
||||
[detailed setup instructions](/enterprise_influxdb/latest/production_installation/).
|
||||
[detailed setup instructions](/{{< latest "enterprise_influxdb" >}}/production_installation/).
|
||||
This guide uses an InfluxData Enterprise cluster with three meta nodes and three data nodes; the steps are also applicable to other cluster configurations.
|
||||
|
||||
InfluxData recommends using a separate server to store your monitoring data.
|
||||
It is possible to store the monitoring data in your cluster and [connect the cluster to Chronograf](/chronograf/latest/troubleshooting/frequently-asked-questions/#how-do-i-connect-chronograf-to-an-influxenterprise-cluster), but, in general, your monitoring data should live on a separate server.
|
||||
It is possible to store the monitoring data in your cluster and [connect the cluster to Chronograf](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#how-do-i-connect-chronograf-to-an-influxenterprise-cluster), but, in general, your monitoring data should live on a separate server.
|
||||
|
||||
You're working on an Ubuntu installation.
|
||||
Chronograf and the other components of the TICK stack are supported on several operating systems and hardware architectures. Check out the [downloads page](https://portal.influxdata.com/downloads) for links to the binaries of your choice.
|
||||
|
@ -35,11 +35,11 @@ Before we begin, here's an overview of the final monitoring setup:
|
|||
![Architecture diagram](/img/chronograf/1-6-cluster-diagram.png)
|
||||
|
||||
The diagram above shows an InfluxDB Enterprise cluster that consists of three meta nodes (M) and three data nodes (D).
|
||||
Each data node has its own [Telegraf](/telegraf/latest/) instance (T).
|
||||
Each data node has its own [Telegraf](/{{< latest "telegraf" >}}/) instance (T).
|
||||
|
||||
Each Telegraf instance is configured to collect node CPU, disk, and memory data using the Telegraf [system stats](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/system) input plugin.
|
||||
The Telegraf instances are also configured to send those data to a single [InfluxDB OSS](/influxdb/latest/) instance that lives on a separate server.
|
||||
When Telegraf sends data to InfluxDB, it automatically [tags](/influxdb/latest/concepts/glossary/#tag) the data with the hostname of the relevant data node.
|
||||
The Telegraf instances are also configured to send those data to a single [InfluxDB OSS](/{{< latest "influxdb" "v1" >}}/) instance that lives on a separate server.
|
||||
When Telegraf sends data to InfluxDB, it automatically [tags](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag) the data with the hostname of the relevant data node.
|
||||
|
||||
The InfluxDB OSS instance that stores the Telegraf data is connected to Chronograf.
|
||||
Chronograf uses the hostnames in the Telegraf data to populate the Host List page and provide other hostname-specific information in the user interface.
|
||||
|
@ -54,7 +54,7 @@ InfluxDB can be downloaded from the [InfluxData downloads page](https://portal.i
|
|||
|
||||
#### Step 2: Enable authentication
|
||||
|
||||
For security purposes, enable authentication in the InfluxDB [configuration file (influxdb.conf)](/influxdb/latest/administration/config/), which is located in `/etc/influxdb/influxdb.conf`.
|
||||
For security purposes, enable authentication in the InfluxDB [configuration file (influxdb.conf)](/{{< latest "influxdb" "v1" >}}/administration/config/), which is located in `/etc/influxdb/influxdb.conf`.
|
||||
|
||||
In the `[http]` section of the configuration file, uncomment the `auth-enabled` option and set it to `true`:
|
||||
|
||||
|
@ -80,7 +80,7 @@ Next, start the InfluxDB process:
|
|||
|
||||
#### Step 4: Create an admin user
|
||||
|
||||
Create an [admin user](/influxdb/latest/query_language/authentication_and_authorization/#user-types-and-privileges) on your InfluxDB instance.
|
||||
Create an [admin user](/{{< latest "influxdb" "v1" >}}/query_language/authentication_and_authorization/#user-types-and-privileges) on your InfluxDB instance.
|
||||
Because you enabled authentication, you must perform this step before moving on to the next section.
|
||||
Run the command below to create an admin user, replacing `chronothan` and `supersecret` with your own username and password.
|
||||
Note that the password requires single quotes.
|
||||
|
@ -178,7 +178,7 @@ Replace the `chronothan` and `supersecret` values with your actual username and
|
|||
```
|
||||
|
||||
The expected output is similar to the JSON in the codeblock below.
|
||||
In this case, the `telegraf` database has three different [tag values](/influxdb/latest/concepts/glossary/#tag-value) for the `host` [tag key](/influxdb/latest/concepts/glossary/#tag-key): `data-node-01`, `data-node-02`, and `data-node-03`.
|
||||
In this case, the `telegraf` database has three different [tag values](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-value) for the `host` [tag key](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-key): `data-node-01`, `data-node-02`, and `data-node-03`.
|
||||
Those values match the hostnames of the three data nodes in the cluster; this means Telegraf is successfully writing monitoring data from those hosts to the InfluxDB OSS instance!
|
||||
```
|
||||
{
|
||||
|
@ -258,6 +258,6 @@ In the image below, the Chronograf query editor is used to visualize the idle CP
|
|||
![Data Explorer](/img/chronograf/1-6-cluster-de.png)
|
||||
|
||||
Create more customized graphs and save them to a dashboard on the Dashboard page in Chronograf.
|
||||
See the [Creating Chronograf dashboards](/chronograf/latest/guides/create-a-dashboard/) guide for more information.
|
||||
See the [Creating Chronograf dashboards](/{{< latest "chronograf" >}}/guides/create-a-dashboard/) guide for more information.
|
||||
|
||||
That's it! You've successfully configured Telegraf to collect and write data, InfluxDB to store those data, and Chonograf to use those data for monitoring and visualization purposes.
|
||||
|
|
|
@ -11,7 +11,7 @@ menu:
|
|||
|
||||
## Overview
|
||||
|
||||
Pre-created dashboards are delivered with Chronograf and are available depending on which Telegraf input plugins you have enabled. These dashboards include cells with data visualizations for metrics that are relevant to data sources you are likely to be using. The JSON files that are delivered include headings, queries, labels, and other information that can also be useful for helping you get started in [creating custom dashboards](/chronograf/latest/guides/create-a-dashboard/).
|
||||
Pre-created dashboards are delivered with Chronograf and are available depending on which Telegraf input plugins you have enabled. These dashboards include cells with data visualizations for metrics that are relevant to data sources you are likely to be using. The JSON files that are delivered include headings, queries, labels, and other information that can also be useful for helping you get started in [creating custom dashboards](/{{< latest "chronograf" >}}/guides/create-a-dashboard/).
|
||||
|
||||
> Note that these pre-created dashboards do not appear in the Dashboards tab, which only include custom dashboards that your organization has created.
|
||||
|
||||
|
@ -33,7 +33,7 @@ Pre-created dashboards are delivered in Chronograf installations and are ready t
|
|||
|
||||
The pre-created dashboards available for use with Chronograf are listed below as Apps and appear in the Apps listing for hosts in the Host List page. The listings for apps (pre-created dashboards) on this page include information about the required Telegraf input plugins, JSON files included in the apps, and listings of the cell titles that are included in each of the JSON files.
|
||||
|
||||
The JSON files for the precreated dashboards are delivered on installation in the `/usr/share/chronograf/canned` directory. Information about the configuration option `--canned-path` can be found in the [Chronograf configuration options](/chronograf/latest/administration/config-options/#) page.
|
||||
The JSON files for the precreated dashboards are delivered on installation in the `/usr/share/chronograf/canned` directory. Information about the configuration option `--canned-path` can be found in the [Chronograf configuration options](/{{< latest "chronograf" >}}/administration/config-options/#) page.
|
||||
|
||||
You can enable and disable applications in your [Telegraf configuration file](https://github.com/influxdata/telegraf/blob/master/etc/telegraf.conf).
|
||||
See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/docs/CONFIGURATION.md) for details.
|
||||
|
|
|
@ -179,10 +179,10 @@ The **Single Stat** view displays the most recent value of the specified time se
|
|||
|
||||
![Single Stat view](/img/chronograf/1-6-viz-single-stat-selector.png)
|
||||
|
||||
If a cell's query includes a [`GROUP BY` tag](/influxdb/latest/query_language/data_exploration/#group-by-tags) clause, Chronograf sorts the different [series](/influxdb/latest/concepts/glossary/#series) lexicographically and shows the most recent [field value](/influxdb/latest/concepts/glossary/#field-value) associated with the first series.
|
||||
For example, if a query groups by the `name` [tag key](/influxdb/latest/concepts/glossary/#tag-key) and `name` has two [tag values](/influxdb/latest/concepts/glossary/#tag-value) (`chronelda` and `chronz`), Chronograf shows the most recent field value associated with the `chronelda` series.
|
||||
If a cell's query includes a [`GROUP BY` tag](/{{< latest "influxdb" "v1" >}}/query_language/data_exploration/#group-by-tags) clause, Chronograf sorts the different [series](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#series) lexicographically and shows the most recent [field value](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#field-value) associated with the first series.
|
||||
For example, if a query groups by the `name` [tag key](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-key) and `name` has two [tag values](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-value) (`chronelda` and `chronz`), Chronograf shows the most recent field value associated with the `chronelda` series.
|
||||
|
||||
If a cell's query includes more than one [field key](/influxdb/latest/concepts/glossary/#field-key) in the [`SELECT` clause](/influxdb/latest/query_language/data_exploration/#select-clause), Chronograf returns the most recent field value associated with the first field key in the `SELECT` clause.
|
||||
If a cell's query includes more than one [field key](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#field-key) in the [`SELECT` clause](/{{< latest "influxdb" "v1" >}}/query_language/data_exploration/#select-clause), Chronograf returns the most recent field value associated with the first field key in the `SELECT` clause.
|
||||
For example, if a query's `SELECT` clause is `SELECT "chronogiraffe","chronelda"`, Chronograf shows the most recent field value associated with the `chronogiraffe` field key.
|
||||
|
||||
#### Single Stat Controls
|
||||
|
|
|
@ -15,11 +15,11 @@ Follow the links below to get acquainted with Chronograf:
|
|||
Chronograf is supported on several operating systems and hardware architectures.
|
||||
See the [InfluxData downloads page](https://portal.influxdata.com/downloads) page for to the available binaries.
|
||||
|
||||
## [Installing Chronograf](/chronograf/latest/introduction/installation/)
|
||||
## [Installing Chronograf](/{{< latest "chronograf" >}}/introduction/installation/)
|
||||
|
||||
[Installing Chronograf](/chronograf/latest/introduction/installation/) lists the requirements for installing, starting, and configuring Chronograf.
|
||||
[Installing Chronograf](/{{< latest "chronograf" >}}/introduction/installation/) lists the requirements for installing, starting, and configuring Chronograf.
|
||||
|
||||
## Getting Started
|
||||
[Getting started with Chronograf](/chronograf/latest/introduction/getting-started/) gets you up and running with Chronograf with as little configuration and code as possible.
|
||||
[Getting started with Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/) gets you up and running with Chronograf with as little configuration and code as possible.
|
||||
By the end of the guide, you will have downloaded, installed, and configured all four packages of the
|
||||
TICK stack ([Telegraf](https://github.com/influxdata/telegraf), [InfluxDB](https://github.com/influxdata/influxdb), Chronograf, and [Kapacitor](https://github.com/influxdata/kapacitor)), and you will be all set to monitor your infrastructure.
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Getting started with Chronograf
|
||||
aliases:
|
||||
- /chronograf/latest/introduction/getting-started/
|
||||
- /{{< latest "chronograf" >}}/introduction/getting-started/
|
||||
- /chronograf/v1.6/introduction/getting_started/
|
||||
menu:
|
||||
chronograf_1_6:
|
||||
|
@ -11,18 +11,18 @@ menu:
|
|||
---
|
||||
|
||||
## Overview
|
||||
Chronograf allows you to quickly see data you have stored in InfluxDB so you can build robust queries and alerts. After your administrator has set up Chronograf as described in [Installing Chronograf](/chronograf/latest/introduction/installation), get started with key features using the guides below.
|
||||
Chronograf allows you to quickly see data you have stored in InfluxDB so you can build robust queries and alerts. After your administrator has set up Chronograf as described in [Installing Chronograf](/{{< latest "chronograf" >}}/introduction/installation), get started with key features using the guides below.
|
||||
|
||||
### Data visualization
|
||||
* Investigate your data by building queries using [InfluxQL](/influxdb/latest/query_language/).
|
||||
* Use pre-created [pre-created dashboards](/chronograf/latest/guides/using-precreated-dashboards/) to monitor your application data or [create your own dashboards](/chronograf/latest/guides/create-a-dashboard/).
|
||||
* Customize dashboards using [template variables](/chronograf/latest/guides/dashboard-template-variables/).
|
||||
* Investigate your data by building queries using [InfluxQL](/{{< latest "influxdb" "v1" >}}/query_language/).
|
||||
* Use pre-created [pre-created dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards/) to monitor your application data or [create your own dashboards](/{{< latest "chronograf" >}}/guides/create-a-dashboard/).
|
||||
* Customize dashboards using [template variables](/{{< latest "chronograf" >}}/guides/dashboard-template-variables/).
|
||||
|
||||
### Alerting
|
||||
* [Create alert rules](/chronograf/latest/guides/create-alert-rules/) to generate threshold, relative, and deadman alerts on your data.
|
||||
* [View all active alerts](/chronograf/latest/guides/create-alert-rules/#step-2-view-the-alerts) on an alert dashboard.
|
||||
* Use [alert endpoints](/chronograf/latest/guides/configuring-alert-endpoints/) in Chronograf to send alert messages to specific URLs and applications.
|
||||
* [Create alert rules](/{{< latest "chronograf" >}}/guides/create-alert-rules/) to generate threshold, relative, and deadman alerts on your data.
|
||||
* [View all active alerts](/{{< latest "chronograf" >}}/guides/create-alert-rules/#step-2-view-the-alerts) on an alert dashboard.
|
||||
* Use [alert endpoints](/{{< latest "chronograf" >}}/guides/configuring-alert-endpoints/) in Chronograf to send alert messages to specific URLs and applications.
|
||||
|
||||
### Infrastructure monitoring
|
||||
* [View all hosts](/chronograf/latest/guides/monitoring-influxenterprise-clusters/#step-4-explore-the-monitoring-data-in-chronograf) and their statuses in your infrastructure.
|
||||
* [Use pre-created dashboards](/chronograf/latest/guides/using-precreated-dashboards/) to monitor your applications.
|
||||
* [View all hosts](/{{< latest "chronograf" >}}/guides/monitoring-influxenterprise-clusters/#step-4-explore-the-monitoring-data-in-chronograf) and their statuses in your infrastructure.
|
||||
* [Use pre-created dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards/) to monitor your applications.
|
||||
|
|
|
@ -9,4 +9,4 @@ menu:
|
|||
|
||||
Follow the link below to access Chronograf's FAQ.
|
||||
|
||||
## [Frequently Asked Questions](/chronograf/latest/troubleshooting/frequently-asked-questions/)
|
||||
## [Frequently Asked Questions](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/)
|
||||
|
|
|
@ -9,7 +9,7 @@ menu:
|
|||
|
||||
## How do I connect Chronograf to an InfluxDB Enterprise cluster?
|
||||
|
||||
The connection details form requires additional information when connecting Chronograf to an [InfluxDB Enterprise cluster](https://docs.influxdata.com/enterprise_influxdb/latest/).
|
||||
The connection details form requires additional information when connecting Chronograf to an [InfluxDB Enterprise cluster](/{{< latest "enterprise_influxdb" >}}/).
|
||||
|
||||
When you enter the InfluxDB HTTP bind address in the `Connection String` input, Chronograf automatically checks if that InfluxDB instance is a data node.
|
||||
If it is a data node, Chronograf automatically adds the `Meta Service Connection URL` input to the connection details form.
|
||||
|
@ -19,4 +19,4 @@ Enter the HTTP bind address of one of your cluster's meta nodes into that input
|
|||
|
||||
Note that the example above assumes that you do not have authentication enabled.
|
||||
If you have authentication enabled, the form requires username and password information.
|
||||
For more details about monitoring an InfluxDB Enterprise cluster, see the [Monitor an InfluxDB Enterprise Cluster](/chronograf/latest/guides/monitoring-influxenterprise-clusters/) guide.
|
||||
For more details about monitoring an InfluxDB Enterprise cluster, see the [Monitor an InfluxDB Enterprise Cluster](/{{< latest "chronograf" >}}/guides/monitoring-influxenterprise-clusters/) guide.
|
||||
|
|
|
@ -38,12 +38,12 @@ Chronograf offers a UI for [Kapacitor](https://github.com/influxdata/kapacitor),
|
|||
|
||||
* Create and delete databases and retention policies
|
||||
* View currently-running queries and stop inefficient queries from overloading your system
|
||||
* Create, delete, and assign permissions to users (Chronograf supports [InfluxDB OSS](/influxdb/latest/administration/authentication_and_authorization/#authorization) and InfluxEnterprise user management)
|
||||
* Create, delete, and assign permissions to users (Chronograf supports [InfluxDB OSS](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#authorization) and InfluxEnterprise user management)
|
||||
|
||||
|
||||
### Multi-organization and multi-user support
|
||||
|
||||
>**Note:** To use this feature, OAuth 2.0 authentication must be configured. Once configured, the Chronograf Admin tab on the Admin menu is visible. For details, see [Managing Chronograf security](https://docs.influxdata.com/chronograf/v1.7/administration/managing-security/).
|
||||
>**Note:** To use this feature, OAuth 2.0 authentication must be configured. Once configured, the Chronograf Admin tab on the Admin menu is visible. For details, see [Managing Chronograf security](/chronograf/v1.7/administration/managing-security/).
|
||||
|
||||
* Create organizations and assign users to those organizations
|
||||
* Restrict access to administrative functions
|
||||
|
|
|
@ -836,9 +836,9 @@ menu:
|
|||
### UI improvements
|
||||
|
||||
* When dashboard time range is changed, reset graphs that are zoomed in
|
||||
* [Bar graph](/chronograf/latest/guides/visualization-types/#bar-graph) option added to dashboard
|
||||
* [Bar graph](/{{< latest "chronograf" >}}/guides/visualization-types/#bar-graph) option added to dashboard
|
||||
* Redesign source management table to be more intuitive
|
||||
* Redesign [Line + Single Stat](/chronograf/latest/guides/visualization-types/#line-graph-single-stat) cells to appear more like a sparkline, and improve legibility
|
||||
* Redesign [Line + Single Stat](/{{< latest "chronograf" >}}/guides/visualization-types/#line-graph-single-stat) cells to appear more like a sparkline, and improve legibility
|
||||
|
||||
|
||||
## v1.3.2.0 [2017-06-05]
|
||||
|
@ -854,7 +854,7 @@ menu:
|
|||
|
||||
### Features
|
||||
|
||||
* Add UI to the Data Explorer for [writing data to InfluxDB](/chronograf/latest/guides/querying-data/)
|
||||
* Add UI to the Data Explorer for [writing data to InfluxDB](/{{< latest "chronograf" >}}/guides/querying-data/)
|
||||
|
||||
### UI improvements
|
||||
|
||||
|
@ -874,26 +874,26 @@ In versions 1.3.1+, installing a new version of Chronograf automatically clears
|
|||
|
||||
### Bug fixes
|
||||
|
||||
* Fix infinite spinner when `/chronograf` is a [basepath](/chronograf/latest/administration/config-options/#p-basepath)
|
||||
* Fix infinite spinner when `/chronograf` is a [basepath](/{{< latest "chronograf" >}}/administration/config-options/#p-basepath)
|
||||
* Remove the query templates dropdown from dashboard cell editor mode
|
||||
* Fix the backwards sort arrows in table column headers
|
||||
* Make the logout button consistent with design
|
||||
* Fix the loading spinner on graphs
|
||||
* Filter out any template variable values that are empty, whitespace, or duplicates
|
||||
* Allow users to click the add query button after selecting singleStat as the [visualization type](/chronograf/latest/guides/visualization-types)
|
||||
* Allow users to click the add query button after selecting singleStat as the [visualization type](/{{< latest "chronograf" >}}/guides/visualization-types)
|
||||
* Add a query for windows uptime - thank you, @brianbaker!
|
||||
|
||||
### Features
|
||||
|
||||
* Add log event handler- thank you, @mpchadwick!
|
||||
* Update Go (golang) vendoring to dep and committed vendor directory
|
||||
* Add autocomplete functionality to [template variable](/chronograf/latest/guides/dashboard-template-variables) dropdowns
|
||||
* Add autocomplete functionality to [template variable](/{{< latest "chronograf" >}}/guides/dashboard-template-variables) dropdowns
|
||||
|
||||
### UI improvements
|
||||
|
||||
* Refactor scrollbars to support non-webkit browsers
|
||||
* Increase the query builder's default height in cell editor mode and in the data explorer
|
||||
* Make the [template variables](/chronograf/latest/guides/dashboard-template-variables) manager more space efficient
|
||||
* Make the [template variables](/{{< latest "chronograf" >}}/guides/dashboard-template-variables) manager more space efficient
|
||||
* Add page spinners to pages that did not have them
|
||||
* Denote which source is connected in the sources table
|
||||
* Use milliseconds in the InfluxDB dashboard instead of nanoseconds
|
||||
|
@ -903,25 +903,25 @@ In versions 1.3.1+, installing a new version of Chronograf automatically clears
|
|||
|
||||
### Bug fixes
|
||||
|
||||
* Fix the link to home when using the [`--basepath` option](/chronograf/latest/administration/config-options/#p-basepath)
|
||||
* Fix the link to home when using the [`--basepath` option](/{{< latest "chronograf" >}}/administration/config-options/#p-basepath)
|
||||
* Remove the notification to login on the login page
|
||||
* Support queries that perform math on functions
|
||||
* Prevent the creation of blank template variables
|
||||
* Ensure thresholds for Kapacitor Rule Alerts appear on page load
|
||||
* Update the Kapacitor configuration page when the configuration changes
|
||||
* Fix Authentication when using Chronograf with a set [basepath](/chronograf/latest/administration/config-options/#p-basepath)
|
||||
* Fix Authentication when using Chronograf with a set [basepath](/{{< latest "chronograf" >}}/administration/config-options/#p-basepath)
|
||||
* Show red indicator on Hosts Page for an offline host
|
||||
* Support escaping from presentation mode in Safari
|
||||
* Re-implement level colors on the alerts page
|
||||
* Fix router bug introduced by upgrading to react-router v3.0
|
||||
* Show legend on [Line+Stat](/chronograf/latest/guides/visualization-types/#line-graph-single-stat) visualization type
|
||||
* Show legend on [Line+Stat](/{{< latest "chronograf" >}}/guides/visualization-types/#line-graph-single-stat) visualization type
|
||||
* Prevent queries with `:dashboardTime:` from breaking the query builder
|
||||
|
||||
### Features
|
||||
|
||||
* Add line-protocol proxy for InfluxDB/InfluxEnterprise Cluster data sources
|
||||
* Add `:dashboardTime:` to support cell-specific time ranges on dashboards
|
||||
* Add support for enabling and disabling [TICKscripts that were created outside Chronograf](/chronograf/latest/guides/advanced-kapacitor/#tickscript-management)
|
||||
* Add support for enabling and disabling [TICKscripts that were created outside Chronograf](/{{< latest "chronograf" >}}/guides/advanced-kapacitor/#tickscript-management)
|
||||
* Allow users to delete Kapacitor configurations
|
||||
|
||||
### UI improvements
|
||||
|
|
|
@ -8,7 +8,7 @@ menu:
|
|||
parent: Administration
|
||||
---
|
||||
|
||||
The connection details form requires additional information when connecting Chronograf to an [InfluxDB Enterprise cluster](https://docs.influxdata.com/enterprise_influxdb/latest/).
|
||||
The connection details form requires additional information when connecting Chronograf to an [InfluxDB Enterprise cluster](/{{< latest "enterprise_influxdb" >}}/).
|
||||
|
||||
When you enter the InfluxDB HTTP bind address in the `Connection String` input, Chronograf automatically checks if that InfluxDB instance is a data node.
|
||||
If it is a data node, Chronograf automatically adds the `Meta Service Connection URL` input to the connection details form.
|
||||
|
@ -19,4 +19,4 @@ Enter the HTTP bind address of one of your cluster's meta nodes into that input
|
|||
Note that the example above assumes that you do not have authentication enabled.
|
||||
If you have authentication enabled, the form requires username and password information.
|
||||
|
||||
For details about monitoring InfluxEnterprise clusters, see [Monitoring InfluxDB Enterprise clusters](/chronograf/latest/guides/monitoring-influxenterprise-clusters).
|
||||
For details about monitoring InfluxEnterprise clusters, see [Monitoring InfluxDB Enterprise clusters](/{{< latest "chronograf" >}}/guides/monitoring-influxenterprise-clusters).
|
||||
|
|
|
@ -78,7 +78,7 @@ Environment variable: `$BOLT_PATH`
|
|||
|
||||
#### `--canned-path=` | `-c`
|
||||
|
||||
The path to the directory of [canned dashboards](/chronograf/latest/guides/using-precreated-dashboards) files.
|
||||
The path to the directory of [canned dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards) files.
|
||||
|
||||
Default value: `/usr/share/chronograf/canned`
|
||||
|
||||
|
|
|
@ -13,7 +13,7 @@ However, it is also possible to set custom default configuration options in the
|
|||
|
||||
## Starting the Chronograf service
|
||||
|
||||
Start Chronograf using the default configuration options, or [customize your configuration](https://docs.influxdata.com/chronograf/v1.7/administration/configuration/) with environment variables and command line options (for example, to configure OAuth 2.0 authentication) based on your requirements.
|
||||
Start Chronograf using the default configuration options, or [customize your configuration](/chronograf/v1.7/administration/configuration/) with environment variables and command line options (for example, to configure OAuth 2.0 authentication) based on your requirements.
|
||||
|
||||
**Linux:**
|
||||
|
||||
|
@ -27,12 +27,12 @@ sudo systemctl start chronograf [OPTIONS]
|
|||
chronograf [OPTIONS]
|
||||
```
|
||||
|
||||
`[OPTIONS]` are available Chronograf command line options, separated by spaces. See the [Chronograf configuration options](https://docs.influxdata.com/chronograf/v1.7/administration/config-options) documentation for details about configuration options, including command line options and corresponding environment variables.
|
||||
`[OPTIONS]` are available Chronograf command line options, separated by spaces. See the [Chronograf configuration options](/chronograf/v1.7/administration/config-options) documentation for details about configuration options, including command line options and corresponding environment variables.
|
||||
|
||||
## Setting custom default Chronograf config options
|
||||
|
||||
Custom default Chronograf configuration settings can be defined in `/etc/default/chronograf`.
|
||||
This file consists of key-value pairs. See keys (environment variables) for [Chronograf configuration options](https://docs.influxdata.com/chronograf/v1.7/administration/config-options), and set values for the keys you want to configure.
|
||||
This file consists of key-value pairs. See keys (environment variables) for [Chronograf configuration options](/chronograf/v1.7/administration/config-options), and set values for the keys you want to configure.
|
||||
|
||||
```conf
|
||||
HOST=0.0.0.0
|
||||
|
@ -55,7 +55,7 @@ To set up security for Chronograf, configure:
|
|||
After you configure OAuth 2.0 authentication, you can set up multiple organizations, roles, and users. For details, check out the following topics:
|
||||
|
||||
* [Managing organizations](chronograf/v1.7/administration/managing-organizations/)
|
||||
* [Managing Chronograf users](https://docs.influxdata.com/chronograf/v1.7/administration/managing-chronograf-users/)
|
||||
* [Managing Chronograf users](/chronograf/v1.7/administration/managing-chronograf-users/)
|
||||
|
||||
|
||||
<!-- TODO ## Configuring Chronograf for InfluxDB Enterprise clusters) -->
|
||||
|
|
|
@ -31,15 +31,15 @@ To create an InfluxDB connection in the Chronograf UI:
|
|||
* **Connection URL**: Enter the hostname or IP address of the InfluxDB instance and the port. The field is prefilled with `http://localhost:8086`.
|
||||
* **Connection Name**: Enter the name for this connection.
|
||||
* **Username**: Enter the username that will be shared for this connection.
|
||||
*Required only if [authorization is enabled](/influxdb/latest/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.*
|
||||
*Required only if [authorization is enabled](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.*
|
||||
* **Password**: Enter the password.
|
||||
*Required only if [authorization is enabled](/influxdb/latest/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.*
|
||||
*Required only if [authorization is enabled](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.*
|
||||
* **Telegraf Database Name**: This field specifies the database that Chronograf will use for populating different parts of the application, including the Host List page. If you've changed the default retention policy in your InfluxDB instance, you may want to change it here as well. If none is provided, we will use `autogen`. You will still be able to query any database you have access to in the InfluxDB instance when building dashboards or exploring data.
|
||||
* **Default Retention Policy**: Enter the name of the default [retention policy](/influxdb/latest/concepts/glossary/#retention-policy-rp). If none i s provided, it assumes `autogen`.
|
||||
* **Default Retention Policy**: Enter the name of the default [retention policy](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#retention-policy-rp). If none i s provided, it assumes `autogen`.
|
||||
* **Make this the default connection**: When this option is selected, this InfluxDB connection will be used when Chronograf is launched.
|
||||
|
||||
4. Click **Add Connection**
|
||||
* If the connection is valid, the Dashboards window appears, allowing you to import dashboard templates you can use to display and analyze your data. For details, see [Creating dashboards](/chronograf/latest/guides/create-a-dashboard).
|
||||
* If the connection is valid, the Dashboards window appears, allowing you to import dashboard templates you can use to display and analyze your data. For details, see [Creating dashboards](/{{< latest "chronograf" >}}/guides/create-a-dashboard).
|
||||
* If the connection cannot be created, the following error message appears:
|
||||
"Unable to create source: Error contacting source."
|
||||
If this occurs, ensure all connection credentials are correct and that the InfluxDB instance is running and accessible.
|
||||
|
@ -109,11 +109,11 @@ Any string you want to use as the display name of the source.
|
|||
|
||||
#### `username`
|
||||
Username used to access the InfluxDB server or cluster.
|
||||
*Only required if [authorization is enabled](/influxdb/latest/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.*
|
||||
*Only required if [authorization is enabled](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.*
|
||||
|
||||
#### `password`
|
||||
Password used to access the InfluxDB server or cluster.
|
||||
*Only required if [authorization is enabled](/influxdb/latest/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.*
|
||||
*Only required if [authorization is enabled](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.*
|
||||
|
||||
#### `url`
|
||||
URL of the InfluxDB server or cluster.
|
||||
|
@ -176,9 +176,9 @@ To create a Kapacitor connection using the Chronograf UI:
|
|||
* **Kapacitor URL**: Enter the hostname or IP address of the Kapacitor instance and the port. The field is prefilled with `http://localhost:9092`.
|
||||
* **Name**: Enter the name for this connection.
|
||||
* **Username**: Enter the username that will be shared for this connection.
|
||||
*Only required if [authorization is enabled](/kapacitor/latest/administration/security/#kapacitor-authentication-and-authorization) on the Kapacitor instance or cluster to which you're connecting.*
|
||||
*Only required if [authorization is enabled](/{{< latest "kapacitor" >}}/administration/security/#kapacitor-authentication-and-authorization) on the Kapacitor instance or cluster to which you're connecting.*
|
||||
* **Password**: Enter the password.
|
||||
*Only required if [authorization is enabled](/kapacitor/latest/administration/security/#kapacitor-authentication-and-authorization) on the Kapacitor instance or cluster to which you're connecting.*
|
||||
*Only required if [authorization is enabled](/{{< latest "kapacitor" >}}/administration/security/#kapacitor-authentication-and-authorization) on the Kapacitor instance or cluster to which you're connecting.*
|
||||
|
||||
4. Click **Continue**. If the connection is valid, the message "Kapacitor Created! Configuring endpoints is optional." appears. To configure alert endpoints, see [Configuring alert endpoints](/chronograf/v1.7/guides/configuring-alert-endpoints/).
|
||||
|
||||
|
|
|
@ -31,7 +31,7 @@ menu:
|
|||
|
||||
## Managing Chronograf users and roles
|
||||
|
||||
> ***Note:*** Support for organizations and user roles is available in Chronograf 1.4 or later. First, OAuth 2.0 authentication must be configured (if it is, you'll see the Chronograf Admin tab on the Admin menu). For more information, see [Managing security] (https://docs.influxdata.com/chronograf/v1.7/administration/managing-security/).
|
||||
> ***Note:*** Support for organizations and user roles is available in Chronograf 1.4 or later. First, OAuth 2.0 authentication must be configured (if it is, you'll see the Chronograf Admin tab on the Admin menu). For more information, see [Managing security] (/chronograf/v1.7/administration/managing-security/).
|
||||
|
||||
Chronograf includes four organization-bound user roles and one cross-organization SuperAdmin status. In an organization, admins (with the `admin` role) or users with SuperAdmin status can create, update, and assign roles to a user or remove a role assignment.
|
||||
|
||||
|
|
|
@ -13,7 +13,7 @@ menu:
|
|||
The **Chronograf Admin** provides InfluxDB user management for InfluxDB OSS and InfluxDB Enterprise users.
|
||||
|
||||
|
||||
> ***Note:*** For details on Chronograf user authentication and management, see [Managing security](/chronograf/latest/administration/managing-security/).
|
||||
> ***Note:*** For details on Chronograf user authentication and management, see [Managing security](/{{< latest "chronograf" >}}/administration/managing-security/).
|
||||
|
||||
**On this page:**
|
||||
|
||||
|
@ -58,7 +58,7 @@ Restart the InfluxDB service for your configuration changes to take effect:
|
|||
|
||||
### Step 3: Create an admin user.
|
||||
|
||||
Because authentication is enabled, you need to create an [admin user](/influxdb/latest/administration/authentication_and_authorization/#user-types-and-privileges) before you can do anything else in the database.
|
||||
Because authentication is enabled, you need to create an [admin user](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#user-types-and-privileges) before you can do anything else in the database.
|
||||
Run the `curl` command below to create an admin user, replacing:
|
||||
|
||||
* `localhost` with the IP or hostname of your InfluxDB OSS instance or one of your InfluxEnterprise data nodes
|
||||
|
@ -91,7 +91,7 @@ On the **Chronograf Admin** page:
|
|||
![InfluxDB OSS user management](/img/chronograf/1-6-admin-usermanagement-oss.png)
|
||||
|
||||
InfluxDB users are either admin users or non-admin users.
|
||||
See InfluxDB's [authentication and authorization](/influxdb/latest/administration/authentication_and_authorization/#user-types-and-privileges) documentation for more information about those user types.
|
||||
See InfluxDB's [authentication and authorization](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#user-types-and-privileges) documentation for more information about those user types.
|
||||
|
||||
> ***Note:*** Note that Chronograf currently does not support assigning InfluxDB database `READ`or `WRITE` access to non-admin users.
|
||||
>This is a known issue.
|
||||
|
@ -156,12 +156,12 @@ Assign permissions and roles to both admin and non-admin users.
|
|||
Permission to add or remove nodes from a cluster.
|
||||
|
||||
**Relevant `influxd-ctl` arguments**:
|
||||
[`add-data`](/enterprise_influxdb/latest/administration/cluster-commands/#add-data),
|
||||
[`add-meta`](/enterprise_influxdb/latest/administration/cluster-commands/#add-meta),
|
||||
[`join`](/enterprise_influxdb/latest/administration/cluster-commands/#join),
|
||||
[`remove-data`](/enterprise_influxdb/latest/administration/cluster-commands/#remove-data),
|
||||
[`remove-meta`](/enterprise_influxdb/latest/administration/cluster-commands/#remove-meta), and
|
||||
[`leave`](/enterprise_influxdb/latest/administration/cluster-commands/#leave)
|
||||
[`add-data`](/{{< latest "enterprise_influxdb" >}}/administration/cluster-commands/#add-data),
|
||||
[`add-meta`](/{{< latest "enterprise_influxdb" >}}/administration/cluster-commands/#add-meta),
|
||||
[`join`](/{{< latest "enterprise_influxdb" >}}/administration/cluster-commands/#join),
|
||||
[`remove-data`](/{{< latest "enterprise_influxdb" >}}/administration/cluster-commands/#remove-data),
|
||||
[`remove-meta`](/{{< latest "enterprise_influxdb" >}}/administration/cluster-commands/#remove-meta), and
|
||||
[`leave`](/{{< latest "enterprise_influxdb" >}}/administration/cluster-commands/#leave)
|
||||
|
||||
**Pages in Chronograf that require this permission**: NA
|
||||
|
||||
|
@ -169,18 +169,18 @@ Permission to add or remove nodes from a cluster.
|
|||
Permission to copy shards.
|
||||
|
||||
**Relevant `influxd-ctl` arguments**:
|
||||
[`copy-shard`](/enterprise_influxdb/latest/administration/cluster-commands/#copy-shard)
|
||||
[`copy-shard`](/{{< latest "enterprise_influxdb" >}}/administration/cluster-commands/#copy-shard)
|
||||
|
||||
**Pages in Chronograf that require this permission**: NA
|
||||
|
||||
#### CreateDatabase
|
||||
Permission to create databases, create [retention policies](/influxdb/latest/concepts/glossary/#retention-policy-rp), alter retention policies, and view retention policies.
|
||||
Permission to create databases, create [retention policies](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#retention-policy-rp), alter retention policies, and view retention policies.
|
||||
|
||||
**Relevant InfluxQL queries**:
|
||||
[`CREATE DATABASE`](/influxdb/latest/query_language/database_management/#create-database),
|
||||
[`CREATE RETENTION POLICY`](/influxdb/latest/query_language/database_management/#create-retention-policies-with-create-retention-policy),
|
||||
[`ALTER RETENTION POLICY`](/influxdb/latest/query_language/database_management/#modify-retention-policies-with-alter-retention-policy), and
|
||||
[`SHOW RETENTION POLICIES`](/influxdb/latest/query_language/schema_exploration/#show-retention-policies)
|
||||
[`CREATE DATABASE`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#create-database),
|
||||
[`CREATE RETENTION POLICY`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#create-retention-policies-with-create-retention-policy),
|
||||
[`ALTER RETENTION POLICY`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#modify-retention-policies-with-alter-retention-policy), and
|
||||
[`SHOW RETENTION POLICIES`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-retention-policies)
|
||||
|
||||
**Pages in Chronograf that require this permission**: Dashboards, Data Explorer, and Databases on the Admin page
|
||||
|
||||
|
@ -188,25 +188,25 @@ Permission to create databases, create [retention policies](/influxdb/latest/con
|
|||
Permission to manage users and roles; create users, drop users, grant admin status to users, grant permissions to users, revoke admin status from users, revoke permissions from users, change user passwords, view user permissions, and view users and their admin status.
|
||||
|
||||
**Relevant InfluxQL queries**:
|
||||
[`CREATE USER`](/influxdb/latest/administration/authentication_and_authorization/#user-management-commands),
|
||||
[`DROP USER`](/influxdb/latest/administration/authentication_and_authorization/#general-admin-and-non-admin-user-management),
|
||||
[`GRANT ALL PRIVILEGES`](/influxdb/latest/administration/authentication_and_authorization/#user-management-commands),
|
||||
[`GRANT [READ,WRITE,ALL]`](/influxdb/latest/administration/authentication_and_authorization/#non-admin-user-management),
|
||||
[`REVOKE ALL PRIVILEGES`](/influxdb/latest/administration/authentication_and_authorization/#user-management-commands),
|
||||
[`REVOKE [READ,WRITE,ALL]`](/influxdb/latest/administration/authentication_and_authorization/#non-admin-user-management),
|
||||
[`SET PASSWORD`](/influxdb/latest/administration/authentication_and_authorization/#general-admin-and-non-admin-user-management),
|
||||
[`SHOW GRANTS`](/influxdb/latest/administration/authentication_and_authorization/#non-admin-user-management), and
|
||||
[`SHOW USERS`](/influxdb/latest/administration/authentication_and_authorization/#user-management-commands)
|
||||
[`CREATE USER`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#user-management-commands),
|
||||
[`DROP USER`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#general-admin-and-non-admin-user-management),
|
||||
[`GRANT ALL PRIVILEGES`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#user-management-commands),
|
||||
[`GRANT [READ,WRITE,ALL]`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#non-admin-user-management),
|
||||
[`REVOKE ALL PRIVILEGES`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#user-management-commands),
|
||||
[`REVOKE [READ,WRITE,ALL]`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#non-admin-user-management),
|
||||
[`SET PASSWORD`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#general-admin-and-non-admin-user-management),
|
||||
[`SHOW GRANTS`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#non-admin-user-management), and
|
||||
[`SHOW USERS`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#user-management-commands)
|
||||
|
||||
**Pages in Chronograf that require this permission**: Data Explorer, Dashboards, Users and Roles on the Admin page
|
||||
|
||||
#### DropData
|
||||
Permission to drop data, in particular [series](/influxdb/latest/concepts/glossary/#series) and [measurements](/influxdb/latest/concepts/glossary/#measurement).
|
||||
Permission to drop data, in particular [series](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#series) and [measurements](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#measurement).
|
||||
|
||||
**Relevant InfluxQL queries**:
|
||||
[`DROP SERIES`](/influxdb/latest/query_language/database_management/#drop-series-from-the-index-with-drop-series),
|
||||
[`DELETE`](/influxdb/latest/query_language/database_management/#delete-series-with-delete), and
|
||||
[`DROP MEASUREMENT`](/influxdb/latest/query_language/database_management/#delete-measurements-with-drop-measurement)
|
||||
[`DROP SERIES`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#drop-series-from-the-index-with-drop-series),
|
||||
[`DELETE`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#delete-series-with-delete), and
|
||||
[`DROP MEASUREMENT`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#delete-measurements-with-drop-measurement)
|
||||
|
||||
**Pages in Chronograf that require this permission**: NA
|
||||
|
||||
|
@ -214,8 +214,8 @@ Permission to drop data, in particular [series](/influxdb/latest/concepts/glossa
|
|||
Permission to drop databases and retention policies.
|
||||
|
||||
**Relevant InfluxQL queries**:
|
||||
[`DROP DATABASE`](/influxdb/latest/query_language/database_management/#delete-a-database-with-drop-database) and
|
||||
[`DROP RETENTION POLICY`](/influxdb/latest/query_language/database_management/#delete-retention-policies-with-drop-retention-policy)
|
||||
[`DROP DATABASE`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#delete-a-database-with-drop-database) and
|
||||
[`DROP RETENTION POLICY`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#delete-retention-policies-with-drop-retention-policy)
|
||||
|
||||
**Pages in Chronograf that require this permission**: Data Explorer, Dashboards, Databases on the Admin page
|
||||
|
||||
|
@ -231,12 +231,12 @@ Permission to access the configuration-related API calls for InfluxKapacitor Ent
|
|||
**Pages in Chronograf that require this permission**: NA
|
||||
|
||||
#### ManageContinuousQuery
|
||||
Permission to create, drop, and view [continuous queries](/influxdb/latest/concepts/glossary/#continuous-query-cq).
|
||||
Permission to create, drop, and view [continuous queries](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#continuous-query-cq).
|
||||
|
||||
**Relevant InfluxQL queries**:
|
||||
[`CreateContinuousQueryStatement`](/influxdb/latest/query_language/continuous_queries/),
|
||||
[`DropContinuousQueryStatement`](/influxdb/latest/query_language/continuous_queries/#deleting-continuous-queries), and
|
||||
[`ShowContinuousQueriesStatement`](/influxdb/latest/query_language/continuous_queries/#listing-continuous-queries)
|
||||
[`CreateContinuousQueryStatement`](/{{< latest "influxdb" "v1" >}}/query_language/continuous_queries/),
|
||||
[`DropContinuousQueryStatement`](/{{< latest "influxdb" "v1" >}}/query_language/continuous_queries/#deleting-continuous-queries), and
|
||||
[`ShowContinuousQueriesStatement`](/{{< latest "influxdb" "v1" >}}/query_language/continuous_queries/#listing-continuous-queries)
|
||||
|
||||
**Pages in Chronograf that require this permission**: Data Explorer, Dashboards
|
||||
|
||||
|
@ -244,28 +244,28 @@ Permission to create, drop, and view [continuous queries](/influxdb/latest/conce
|
|||
Permission to view and kill queries.
|
||||
|
||||
**Relevant InfluxQL queries**:
|
||||
[`SHOW QUERIES`](/influxdb/latest/troubleshooting/query_management/#list-currently-running-queries-with-show-queries) and
|
||||
[`KILL QUERY`](/influxdb/latest/troubleshooting/query_management/#stop-currently-running-queries-with-kill-query)
|
||||
[`SHOW QUERIES`](/{{< latest "influxdb" "v1" >}}/troubleshooting/query_management/#list-currently-running-queries-with-show-queries) and
|
||||
[`KILL QUERY`](/{{< latest "influxdb" "v1" >}}/troubleshooting/query_management/#stop-currently-running-queries-with-kill-query)
|
||||
|
||||
**Pages in Chronograf that require this permission**: Queries on the Admin page
|
||||
|
||||
#### ManageShard
|
||||
Permission to copy, delete, and view [shards](/influxdb/latest/concepts/glossary/#shard).
|
||||
Permission to copy, delete, and view [shards](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#shard).
|
||||
|
||||
**Relevant InfluxQL queries**:
|
||||
[`DropShardStatement`](/influxdb/latest/query_language/database_management/#delete-a-shard-with-drop-shard),
|
||||
[`ShowShardGroupsStatement`](/influxdb/latest/query_language/spec/#show-shard-groups), and
|
||||
[`ShowShardsStatement`](/influxdb/latest/query_language/spec/#show-shards)
|
||||
[`DropShardStatement`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#delete-a-shard-with-drop-shard),
|
||||
[`ShowShardGroupsStatement`](/{{< latest "influxdb" "v1" >}}/query_language/spec/#show-shard-groups), and
|
||||
[`ShowShardsStatement`](/{{< latest "influxdb" "v1" >}}/query_language/spec/#show-shards)
|
||||
|
||||
**Pages in Chronograf that require this permission**: NA
|
||||
|
||||
#### ManageSubscription
|
||||
Permission to create, drop, and view [subscriptions](/influxdb/latest/concepts/glossary/#subscription).
|
||||
Permission to create, drop, and view [subscriptions](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#subscription).
|
||||
|
||||
**Relevant InfluxQL queries**:
|
||||
[`CREATE SUBSCRIPTION`](/influxdb/latest/query_language/spec/#create-subscription),
|
||||
[`DROP SUBSCRIPTION`](/influxdb/latest/query_language/spec/#drop-subscription), and
|
||||
[`SHOW SUBSCRIPTIONS`](/influxdb/latest/query_language/spec/#show-subscriptions)
|
||||
[`CREATE SUBSCRIPTION`](/{{< latest "influxdb" "v1" >}}/query_language/spec/#create-subscription),
|
||||
[`DROP SUBSCRIPTION`](/{{< latest "influxdb" "v1" >}}/query_language/spec/#drop-subscription), and
|
||||
[`SHOW SUBSCRIPTIONS`](/{{< latest "influxdb" "v1" >}}/query_language/spec/#show-subscriptions)
|
||||
|
||||
**Pages in Chronograf that require this permission**: Alerting
|
||||
|
||||
|
@ -282,12 +282,12 @@ Permission to view cluster statistics and diagnostics.
|
|||
Permission to read data.
|
||||
|
||||
**Relevant InfluxQL queries**:
|
||||
[`SHOW FIELD KEYS`](/influxdb/latest/query_language/schema_exploration/#show-field-keys),
|
||||
[`SHOW MEASUREMENTS`](/influxdb/latest/query_language/schema_exploration/#show-measurements),
|
||||
[`SHOW SERIES`](/influxdb/latest/query_language/schema_exploration/#show-series),
|
||||
[`SHOW TAG KEYS`](/influxdb/latest/query_language/schema_exploration/#show-tag-keys),
|
||||
[`SHOW TAG VALUES`](/influxdb/latest/query_language/schema_exploration/#show-tag-values), and
|
||||
[`SHOW RETENTION POLICIES`](/influxdb/latest/query_language/schema_exploration/#show-retention-policies)
|
||||
[`SHOW FIELD KEYS`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-field-keys),
|
||||
[`SHOW MEASUREMENTS`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-measurements),
|
||||
[`SHOW SERIES`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-series),
|
||||
[`SHOW TAG KEYS`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-tag-keys),
|
||||
[`SHOW TAG VALUES`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-tag-values), and
|
||||
[`SHOW RETENTION POLICIES`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-retention-policies)
|
||||
|
||||
**Pages in Chronograf that require this permission**: Admin, Alerting, Dashboards, Data Explorer, Host List
|
||||
|
||||
|
|
|
@ -24,7 +24,7 @@ menu:
|
|||
First, OAuth 2.0 authentication must be configured (if it is, you'll see the Chronograf Admin tab on the Admin menu).
|
||||
For more information, see [managing security](/chronograf/v1.7/administration/managing-security/).
|
||||
|
||||
For information about the new user roles and SuperAdmin status, see [Managing Chronograf users](https://docs.influxdata.com/chronograf/v1.7/administration/managing-chronograf-users/).
|
||||
For information about the new user roles and SuperAdmin status, see [Managing Chronograf users](/chronograf/v1.7/administration/managing-chronograf-users/).
|
||||
|
||||
A Chronograf organization is a collection of Chronograf users who share common Chronograf-owned resources, including dashboards, InfluxDB connections, and Kapacitor connections. Organizations can be used to represent companies, functional units, projects, or teams. Chronograf users can be members of multiple organizations.
|
||||
|
||||
|
|
|
@ -20,8 +20,8 @@ To enhance security, configure Chronograf to authenticate and authorize with [OA
|
|||
## Configure OAuth 2.0
|
||||
|
||||
> After configuring OAuth 2.0, the Chronograf Admin tab becomes visible.
|
||||
> You can then set up [multiple organizations](https://docs.influxdata.com/chronograf/latest/administration/managing-organizations/)
|
||||
> and [users](https://docs.influxdata.com/chronograf/latest/administration/managing-influxdb-users/).
|
||||
> You can then set up [multiple organizations](/{{< latest "chronograf" >}}/administration/managing-organizations/)
|
||||
> and [users](/{{< latest "chronograf" >}}/administration/managing-influxdb-users/).
|
||||
|
||||
Configure Chronograf to use an OAuth 2.0 provider and JWT (JSON Web Token) to authenticate users and enable role-based access controls.
|
||||
|
||||
|
|
|
@ -7,7 +7,7 @@ menu:
|
|||
weight: 50
|
||||
parent: Administration
|
||||
---
|
||||
Chronograf lets you import a variety of prebuilt dashboards that visualize metrics collect by specific [Telegraf input plugins](/telegraf/latest/plugins/plugin-list). The following Telegraf-related dashboards templates are available.
|
||||
Chronograf lets you import a variety of prebuilt dashboards that visualize metrics collect by specific [Telegraf input plugins](/{{< latest "telegraf" >}}/plugins/plugin-list). The following Telegraf-related dashboards templates are available.
|
||||
|
||||
For details on how to import dashboards while adding a connection in Chronograf, see [Creating connections](/chronograf/v1.7/administration/creating-connections//#managing-influxdb-connections-using-the-chronograf-ui).
|
||||
|
||||
|
@ -30,12 +30,12 @@ The Docker dashboard displays the following information:
|
|||
|
||||
### Plugins
|
||||
|
||||
- [`docker` plugin](/telegraf/latest/plugins/plugin-list/#docker)
|
||||
- [`disk` plugin](/telegraf/latest/plugins/plugin-list/#disk)
|
||||
- [`mem` plugin](/telegraf/latest/plugins/plugin-list/#mem)
|
||||
- [`diskio` plugin](/telegraf/latest/plugins/plugin-list/#diskio)
|
||||
- [`system` plugin](/telegraf/latest/plugins/plugin-list/#system)
|
||||
- [`cpu` plugin](/telegraf/latest/plugins/plugin-list/#cpu)
|
||||
- [`docker` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#docker)
|
||||
- [`disk` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#disk)
|
||||
- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#mem)
|
||||
- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#diskio)
|
||||
- [`system` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#system)
|
||||
- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#cpu)
|
||||
|
||||
## Kubernetes Node
|
||||
The Kubernetes Node dashboard displays the following information:
|
||||
|
@ -53,7 +53,7 @@ The Kubernetes Node dashboard displays the following information:
|
|||
- K8s - Kubelet Memory Bytes
|
||||
|
||||
### Plugins
|
||||
- [kubernetes](/telegraf/latest/plugins/plugin-list/#kubernetes)
|
||||
- [kubernetes](/{{< latest "telegraf" >}}/plugins/plugin-list/#kubernetes)
|
||||
|
||||
## Kubernetes Overview
|
||||
The Kubernetes Node dashboard displays the following information:
|
||||
|
@ -72,7 +72,7 @@ The Kubernetes Node dashboard displays the following information:
|
|||
|
||||
### Plugins
|
||||
|
||||
- [kubernetes](/telegraf/latest/plugins/plugin-list/#kubernetes)
|
||||
- [kubernetes](/{{< latest "telegraf" >}}/plugins/plugin-list/#kubernetes)
|
||||
|
||||
## Kubernetes Pod
|
||||
The Kubernetes Pod dashboard displays the following information:
|
||||
|
@ -87,7 +87,7 @@ The Kubernetes Pod dashboard displays the following information:
|
|||
- K8s - Pod TX Bytes/Second
|
||||
|
||||
### Plugins
|
||||
- [kubernetes](/telegraf/latest/plugins/plugin-list/#kubernetes)
|
||||
- [kubernetes](/{{< latest "telegraf" >}}/plugins/plugin-list/#kubernetes)
|
||||
|
||||
## Riak
|
||||
The Riak dashboard displays the following information:
|
||||
|
@ -101,7 +101,7 @@ The Riak dashboard displays the following information:
|
|||
- Riak - Read Repairs/Minute
|
||||
|
||||
### Plugins
|
||||
- [`riak` plugin](/telegraf/latest/plugins/plugin-list/#riak)
|
||||
- [`riak` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#riak)
|
||||
|
||||
## Consul
|
||||
The Consul dashboard displays the following information:
|
||||
|
@ -110,7 +110,7 @@ The Consul dashboard displays the following information:
|
|||
- Consul - Number of Warning Health Checks
|
||||
|
||||
### Plugins
|
||||
- [`consul` plugin](/telegraf/latest/plugins/plugin-list/#consul)
|
||||
- [`consul` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#consul)
|
||||
|
||||
## Consul Telemetry
|
||||
The Consul Telemetry dashboard displays the following information:
|
||||
|
@ -125,7 +125,7 @@ The Consul Telemetry dashboard displays the following information:
|
|||
- Consul - Number of Serf Events
|
||||
|
||||
### Plugins
|
||||
[`consul` plugin](/telegraf/latest/plugins/plugin-list/#consul)
|
||||
[`consul` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#consul)
|
||||
|
||||
|
||||
## Mesos
|
||||
|
@ -140,7 +140,7 @@ The Mesos dashboard displays the following information:
|
|||
- Mesos Master Uptime
|
||||
|
||||
### Plugins
|
||||
- [`mesos` plugin](/telegraf/latest/plugins/plugin-list/#mesos)
|
||||
- [`mesos` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#mesos)
|
||||
|
||||
## RabbitMQ
|
||||
The RabbitMQ dashboard displays the following information:
|
||||
|
@ -151,7 +151,7 @@ The RabbitMQ dashboard displays the following information:
|
|||
|
||||
### Plugins
|
||||
|
||||
- [`rabbitmq` plugin](/telegraf/latest/plugins/plugin-list/#rabbitmq)
|
||||
- [`rabbitmq` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#rabbitmq)
|
||||
|
||||
## System
|
||||
|
||||
|
@ -170,14 +170,14 @@ The System dashboard displays the following information:
|
|||
|
||||
### Plugins
|
||||
|
||||
- [`system` plugin](/telegraf/latest/plugins/plugin-list/#system)
|
||||
- [`mem` plugin](/telegraf/latest/plugins/plugin-list/#mem)
|
||||
- [`cpu` plugin](/telegraf/latest/plugins/plugin-list/#cpu)
|
||||
- [`disk` plugin](/telegraf/latest/plugins/plugin-list/#disk)
|
||||
- [`diskio` plugin](/telegraf/latest/plugins/plugin-list/#diskio)
|
||||
- [`net` plugin](/telegraf/latest/plugins/plugin-list/#net)
|
||||
- [`processes` plugin](/telegraf/latest/plugins/plugin-list/#processes)
|
||||
- [`swap` plugin](/telegraf/latest/plugins/plugin-list/#swap)
|
||||
- [`system` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#system)
|
||||
- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#mem)
|
||||
- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#cpu)
|
||||
- [`disk` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#disk)
|
||||
- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#diskio)
|
||||
- [`net` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#net)
|
||||
- [`processes` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#processes)
|
||||
- [`swap` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#swap)
|
||||
|
||||
|
||||
|
||||
|
@ -198,7 +198,7 @@ The VMware vSphere Overview dashboard gives an overview of your VMware vSphere C
|
|||
- VM CPU % Ready for :clustername:
|
||||
|
||||
### Plugins
|
||||
- [`vsphere` plugin](/telegraf/latest/plugins/plugin-list/#vmware-vsphere)
|
||||
- [`vsphere` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#vmware-vsphere)
|
||||
|
||||
## Apache
|
||||
The Apache dashboard displays the following information:
|
||||
|
@ -221,12 +221,12 @@ The Apache dashboard displays the following information:
|
|||
|
||||
### Plugins
|
||||
|
||||
- [`apache` plugin](/telegraf/latest/plugins/plugin-list/#apache)
|
||||
- [`system` plugin](/telegraf/latest/plugins/plugin-list/#system)
|
||||
- [`mem` plugin](/telegraf/latest/plugins/plugin-list/#mem)
|
||||
- [`diskio` plugin](/telegraf/latest/plugins/plugin-list/#diskio)
|
||||
- [`net` plugin](/telegraf/latest/plugins/plugin-list/#net)
|
||||
- [`logparser` plugin](/telegraf/latest/plugins/plugin-list/#logparser)
|
||||
- [`apache` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#apache)
|
||||
- [`system` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#system)
|
||||
- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#mem)
|
||||
- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#diskio)
|
||||
- [`net` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#net)
|
||||
- [`logparser` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#logparser)
|
||||
|
||||
## ElasticSearch
|
||||
The ElasticSearch dashboard displays the following information:
|
||||
|
@ -243,7 +243,7 @@ The ElasticSearch dashboard displays the following information:
|
|||
- ElasticSearch - JVM Heap Usage
|
||||
|
||||
### Plugins
|
||||
- [`elasticsearch` plugin](/telegraf/latest/plugins/plugin-list/#elasticsearch)
|
||||
- [`elasticsearch` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#elasticsearch)
|
||||
|
||||
|
||||
## InfluxDB
|
||||
|
@ -272,12 +272,12 @@ The InfluxDB dashboard displays the following information:
|
|||
|
||||
### Plugins
|
||||
|
||||
- [`influxdb` plugin](/telegraf/latest/plugins/plugin-list/#influxdb)
|
||||
- [`cpu` plugin](/telegraf/latest/plugins/plugin-list/#cpu)
|
||||
- [`system` plugin](/telegraf/latest/plugins/plugin-list/#system)
|
||||
- [`mem` plugin](/telegraf/latest/plugins/plugin-list/#mem)
|
||||
- [`diskio` plugin](/telegraf/latest/plugins/plugin-list/#diskio)
|
||||
- [`net` plugin](/telegraf/latest/plugins/plugin-list/#net)
|
||||
- [`influxdb` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#influxdb)
|
||||
- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#cpu)
|
||||
- [`system` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#system)
|
||||
- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#mem)
|
||||
- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#diskio)
|
||||
- [`net` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#net)
|
||||
|
||||
|
||||
|
||||
|
@ -299,7 +299,7 @@ The Memcached dashboard displays the following information:
|
|||
- Memcached - Evictions/10 Seconds
|
||||
|
||||
### Plugins
|
||||
- [`memcached` plugin](/telegraf/latest/plugins/plugin-list/#memcached)
|
||||
- [`memcached` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#memcached)
|
||||
|
||||
|
||||
## NSQ
|
||||
|
@ -315,7 +315,7 @@ The NSQ dashboard displays the following information:
|
|||
- NSQ - Topic Egress
|
||||
|
||||
### Plugins
|
||||
- [`nsq` plugin](/telegraf/latest/plugins/plugin-list/#nsq)
|
||||
- [`nsq` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#nsq)
|
||||
|
||||
## PostgreSQL
|
||||
The PostgreSQL dashboard displays the following information:
|
||||
|
@ -340,11 +340,11 @@ The PostgreSQL dashboard displays the following information:
|
|||
|
||||
### Plugins
|
||||
|
||||
- [`postgresql` plugin](/telegraf/latest/plugins/plugin-list/#postgresql)
|
||||
- [`system` plugin](/telegraf/latest/plugins/plugin-list/#system)
|
||||
- [`mem` plugin](/telegraf/latest/plugins/plugin-list/#mem)
|
||||
- [`cpu` plugin](/telegraf/latest/plugins/plugin-list/#cpu)
|
||||
- [`diskio` plugin](/telegraf/latest/plugins/plugin-list/#diskio)
|
||||
- [`postgresql` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#postgresql)
|
||||
- [`system` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#system)
|
||||
- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#mem)
|
||||
- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#cpu)
|
||||
- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#diskio)
|
||||
|
||||
|
||||
## HAProxy
|
||||
|
@ -367,7 +367,7 @@ The HAProxy dashboard displays the following information:
|
|||
- HAProxy - Backend Error Responses/Second
|
||||
|
||||
### Plugins
|
||||
- [`haproxy` plugin](/telegraf/latest/plugins/plugin-list/#haproxy)
|
||||
- [`haproxy` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#haproxy)
|
||||
|
||||
|
||||
## NGINX
|
||||
|
@ -379,7 +379,7 @@ The NGINX dashboard displays the following information:
|
|||
- NGINX - Active Client State
|
||||
|
||||
### Plugins
|
||||
- [`nginx` plugin](/telegraf/latest/plugins/plugin-list/#nginx)
|
||||
- [`nginx` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#nginx)
|
||||
|
||||
## Redis
|
||||
The Redis dashboard displays the following information:
|
||||
|
@ -390,7 +390,7 @@ The Redis dashboard displays the following information:
|
|||
- Redis - Memory
|
||||
|
||||
### Plugins
|
||||
- [`redis` plugin](/telegraf/latest/plugins/plugin-list/#redis)
|
||||
- [`redis` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#redis)
|
||||
|
||||
|
||||
## VMware vSphere VMs
|
||||
|
@ -406,7 +406,7 @@ The VMWare vSphere VMs dashboard gives an overview of your VMware vSphere virtua
|
|||
- Total Disk Latency for :vmname:
|
||||
|
||||
### Plugins
|
||||
- [`vsphere` plugin](/telegraf/latest/plugins/plugin-list/#vsphere)
|
||||
- [`vsphere` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#vsphere)
|
||||
|
||||
## VMware vSphere Hosts
|
||||
|
||||
|
@ -422,7 +422,7 @@ The VMWare vSphere Hosts dashboard displays the following information:
|
|||
- Total Disk Latency for :esxhostname:
|
||||
|
||||
### Plugins
|
||||
- [`vsphere` plugin](/telegraf/latest/plugins/plugin-list/#vsphere)
|
||||
- [`vsphere` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#vsphere)
|
||||
|
||||
## PHPfpm
|
||||
The PHPfpm dashboard displays the following information:
|
||||
|
@ -433,7 +433,7 @@ The PHPfpm dashboard displays the following information:
|
|||
- PHPfpm - Max Children Reached
|
||||
|
||||
### Plugins
|
||||
- [`phpfpm` plugin](/telegraf/latest/plugins/plugin-list/#nginx)
|
||||
- [`phpfpm` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#nginx)
|
||||
|
||||
## Win System
|
||||
The Win System dashboard displays the following information:
|
||||
|
@ -445,7 +445,7 @@ The Win System dashboard displays the following information:
|
|||
- System - Load
|
||||
|
||||
### Plugins
|
||||
- [`win_services` plugin](/telegraf/latest/plugins/plugin-list/#windows-services)
|
||||
- [`win_services` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#windows-services)
|
||||
|
||||
|
||||
## MySQL
|
||||
|
@ -472,9 +472,9 @@ The MySQL dashboard displays the following information:
|
|||
- InnoDB Data
|
||||
|
||||
### Plugins
|
||||
- [`mySQL` plugin](/telegraf/latest/plugins/plugin-list/#mysql)
|
||||
- [`system` plugin](/telegraf/latest/plugins/plugin-list/#system)
|
||||
- [`mem` plugin](/telegraf/latest/plugins/plugin-list/#mem)
|
||||
- [`mySQL` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#mysql)
|
||||
- [`system` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#system)
|
||||
- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#mem)
|
||||
|
||||
## Ping
|
||||
The Ping dashboard displays the following information:
|
||||
|
@ -483,4 +483,4 @@ The Ping dashboard displays the following information:
|
|||
- Ping - Response Times (ms)
|
||||
|
||||
### Plugins
|
||||
- [`ping` plugin](/telegraf/latest/plugins/plugin-list/#ping)
|
||||
- [`ping` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#ping)
|
||||
|
|
|
@ -8,7 +8,7 @@ aliases:
|
|||
- /chronograf/v1.7/guides/transition-web-admin-interface/
|
||||
---
|
||||
|
||||
Versions 1.3 and later of [InfluxDB](/influxdb/latest/) and [InfluxEnterprise](/enterprise/latest/) do not support the web admin interface, the previous built-in user interface for writing and querying data in InfluxDB.
|
||||
Versions 1.3 and later of [InfluxDB](/{{< latest "influxdb" "v1" >}}/) and [InfluxEnterprise](/enterprise/latest/) do not support the web admin interface, the previous built-in user interface for writing and querying data in InfluxDB.
|
||||
Chronograf replaces the web admin interface with improved tooling for querying data, writing data, and database management.
|
||||
|
||||
The following sections describe the Chronograf features that relate to the web admin interface:
|
||||
|
@ -23,7 +23,7 @@ The following sections describe the Chronograf features that relate to the web a
|
|||
### Web admin interface
|
||||
|
||||
In the web admin interface, users chose the target database in the top right corner and selected from a set of query templates in the `Query Templates` dropdown.
|
||||
The templates included queries with no user-provided values (example: [`SHOW MEASUREMENTS`](/influxdb/latest/query_language/schema_exploration/#show-measurements)) and queries with user-provided values (example: [`SHOW TAG KEYS FROM "<measurement_name>"`](/influxdb/latest/query_language/schema_exploration/#show-tag-keys)).
|
||||
The templates included queries with no user-provided values (example: [`SHOW MEASUREMENTS`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-measurements)) and queries with user-provided values (example: [`SHOW TAG KEYS FROM "<measurement_name>"`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-tag-keys)).
|
||||
|
||||
![WAI Query Templates](/img/chronograf/1-6-g-admin-webtemplates.png)
|
||||
|
||||
|
@ -39,7 +39,7 @@ Note that unlike the web admin interface, Chronograf does not have a database dr
|
|||
|
||||
### Web admin interface
|
||||
|
||||
To write data to InfluxDB, users selected the target database in the top right corner, clicked the `Write Data` icon, and entered their [line protocol](/influxdb/latest/concepts/glossary/#influxdb-line-protocol) in the text input:
|
||||
To write data to InfluxDB, users selected the target database in the top right corner, clicked the `Write Data` icon, and entered their [line protocol](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#influxdb-line-protocol) in the text input:
|
||||
|
||||
![WAI Writing Data](/img/chronograf/1-6-g-admin-write.png)
|
||||
|
||||
|
@ -55,7 +55,7 @@ Next, enter your line protocol in the main text box and click the `Write` button
|
|||
|
||||
### Web admin interface
|
||||
|
||||
In the web admin interface, the `Query Template` dropdown was the only way to manage databases and [retention policies](/influxdb/latest/concepts/glossary/#retention-policy-rp) (RP):
|
||||
In the web admin interface, the `Query Template` dropdown was the only way to manage databases and [retention policies](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#retention-policy-rp) (RP):
|
||||
|
||||
![WAI DBRP Management](/img/chronograf/1-6-g-admin-webdbrp.png)
|
||||
|
||||
|
@ -80,7 +80,7 @@ In the web admin interface, the `Query Template` dropdown was the only way to ma
|
|||
### Chronograf
|
||||
|
||||
In Chronograf, the `Admin` page includes a complete interface for user management.
|
||||
The `Admin` page supports both InfluxDB OSS users and InfluxDB Enterprise users; see [Managing Chronograf Users](/chronograf/latest/administration/managing-chronograf-users/) page for more information.
|
||||
The `Admin` page supports both InfluxDB OSS users and InfluxDB Enterprise users; see [Managing Chronograf Users](/{{< latest "chronograf" >}}/administration/managing-chronograf-users/) page for more information.
|
||||
The `Admin` page allows users to:
|
||||
|
||||
* View, create, and delete users
|
||||
|
|
|
@ -24,4 +24,4 @@ Users can continue to use the deprecated product; documentation is available und
|
|||
For more information, please read the original [announcement blog](https://www.influxdata.com/announcing-the-new-chronograf-a-ui-for-the-tick-stack-and-a-complete-open-source-monitoring-solution/) by our CTO, Paul Dix.
|
||||
|
||||
InfluxData recommends migrating to the open source Chronograf product.
|
||||
See [Getting Started](/chronograf/latest/introduction/getting-started/) to get up and running!
|
||||
See [Getting Started](/{{< latest "chronograf" >}}/introduction/getting-started/) to get up and running!
|
||||
|
|
|
@ -22,7 +22,7 @@ Pre-created dashboards are available when the required Telegraf input plugins ar
|
|||
|
||||
Using the TICKscript editor in Chronograf to create, test, and debug Kapacitor TICKscripts.
|
||||
|
||||
## [Creating dashboards](/chronograf/latest/guides/create-a-dashboard/)
|
||||
## [Creating dashboards](/{{< latest "chronograf" >}}/guides/create-a-dashboard/)
|
||||
|
||||
Chronograf offers a complete dashboard solution for visualizing your data and monitoring your infrastructure.
|
||||
Learn how to create customized dashboards in Chronograf.
|
||||
|
|
|
@ -13,16 +13,16 @@ menu:
|
|||
* [TICKscript management](#tickscript-management)
|
||||
|
||||
|
||||
Chronograf provides a user interface for [Kapacitor](/kapacitor/latest/), InfluxData's processing framework for creating alerts, running ETL jobs, and detecting anomalies in your data.
|
||||
Chronograf provides a user interface for [Kapacitor](/{{< latest "kapacitor" >}}/), InfluxData's processing framework for creating alerts, running ETL jobs, and detecting anomalies in your data.
|
||||
This guide offers insights into how Kapacitor interacts with Chronograf and introduces advanced Kapacitor usage within Chronograf.
|
||||
|
||||
|
||||
## Alert history management
|
||||
|
||||
Chronograf stores the information on the Alert History page as time series data in InfluxDB.
|
||||
It stores it in the `chronograf` database and in the `alerts` [measurement](/influxdb/latest/concepts/glossary/#measurement).
|
||||
By default, this data is subject to an infinite [retention policy](/influxdb/latest/concepts/glossary/#retention-policy-rp) (RP), that is, InfluxDB stores them forever.
|
||||
Users who expect to have a large number of alerts and users who do not want to store their alert history forever may want to shorten the [duration](/influxdb/latest/concepts/glossary/#duration) of that retention policy.
|
||||
It stores it in the `chronograf` database and in the `alerts` [measurement](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#measurement).
|
||||
By default, this data is subject to an infinite [retention policy](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#retention-policy-rp) (RP), that is, InfluxDB stores them forever.
|
||||
Users who expect to have a large number of alerts and users who do not want to store their alert history forever may want to shorten the [duration](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#duration) of that retention policy.
|
||||
|
||||
### Modifying the retention policy in Chronograf
|
||||
|
||||
|
@ -36,7 +36,7 @@ In the Databases tab:
|
|||
#### Step 2: Enter a different duration
|
||||
|
||||
The minimum allowable duration is one hour (`1h`) and the maximum is infinite (`INF`).
|
||||
See the InfluxDB documentation for the list of [acceptable duration units](/influxdb/latest/query_language/spec/#duration-units).
|
||||
See the InfluxDB documentation for the list of [acceptable duration units](/{{< latest "influxdb" "v1" >}}/query_language/spec/#duration-units).
|
||||
|
||||
#### Step 3: Click the green check mark to save your changes
|
||||
|
||||
|
@ -56,7 +56,7 @@ The fourth alert, which occurred on the same day at 16:58:50, is outside the pre
|
|||
|
||||
Chronograf creates Kapacitor tasks using the information that you provide on the Rule Configuration page.
|
||||
It uses that information to communicate with Kapacitor and populate Chronograf alert pages.
|
||||
Pre-existing tasks, or [TICKscripts](/kapacitor/latest/tick/), that you created and enabled on your Kapacitor instance without using Chronograf, have limited functionality in the user interface.
|
||||
Pre-existing tasks, or [TICKscripts](/{{< latest "kapacitor" >}}/tick/), that you created and enabled on your Kapacitor instance without using Chronograf, have limited functionality in the user interface.
|
||||
|
||||
In Chronograf, you can:
|
||||
|
||||
|
|
|
@ -11,7 +11,7 @@ Chronograf gives you the ability to view, search, filter, visualize, and analyze
|
|||
This helps to recognize and diagnose patterns, then quickly dive into logged events that lead up to events.
|
||||
|
||||
## Logging setup
|
||||
Logs data is a first class citizen in InfluxDB and is populated using available log-related [Telegraf input plugins](/telegraf/latest/plugins/inputs/):
|
||||
Logs data is a first class citizen in InfluxDB and is populated using available log-related [Telegraf input plugins](/{{< latest "telegraf" >}}/plugins/inputs/):
|
||||
|
||||
[syslog](https://github.com/influxdata/telegraf/tree/release-1.7/plugins/inputs/syslog)
|
||||
|
||||
|
|
|
@ -17,7 +17,7 @@ This guide offers step-by-step instructions for configuring Chronograf alert end
|
|||
|
||||
## Kapacitor event handlers supported in Chronograf
|
||||
|
||||
Chronograf integrates with [Kapacitor](/kapacitor/latest/), InfluxData's data processing platform, to send alert messages to event handlers.
|
||||
Chronograf integrates with [Kapacitor](/{{< latest "kapacitor" >}}/), InfluxData's data processing platform, to send alert messages to event handlers.
|
||||
Chronograf supports the following event handlers:
|
||||
|
||||
* Alerta
|
||||
|
@ -39,7 +39,7 @@ Chronograf supports the following event handlers:
|
|||
* TCP
|
||||
* VictorOps
|
||||
|
||||
To configure a Kapacitor event handler in Chronograf, [install Kapacitor](/kapacitor/latest/introduction/installation/) and [connect it to Chronograf](/kapacitor/latest/working/kapa-and-chrono/#add-a-kapacitor-instance).
|
||||
To configure a Kapacitor event handler in Chronograf, [install Kapacitor](/{{< latest "kapacitor" >}}/introduction/installation/) and [connect it to Chronograf](/{{< latest "kapacitor" >}}/working/kapa-and-chrono/#add-a-kapacitor-instance).
|
||||
The **Configure Kapacitor** page includes the event handler configuration options.
|
||||
|
||||
|
||||
|
@ -47,10 +47,10 @@ The **Configure Kapacitor** page includes the event handler configuration option
|
|||
|
||||
Alert endpoint configurations appear on the Chronograf Configure Kapacitor page.
|
||||
You must have a connected Kapacitor instance to access the configurations.
|
||||
For more information, see [Kapacitor installation instructions](/kapacitor/latest/introduction/installation/) and how to [connect a Kapacitor instance](/kapacitor/latest/working/kapa-and-chrono/#add-a-kapacitor-instance) to Chronograf.
|
||||
For more information, see [Kapacitor installation instructions](/{{< latest "kapacitor" >}}/introduction/installation/) and how to [connect a Kapacitor instance](/{{< latest "kapacitor" >}}/working/kapa-and-chrono/#add-a-kapacitor-instance) to Chronograf.
|
||||
|
||||
Note that the configuration options in the **Configure alert endpoints** section are not all-inclusive.
|
||||
Some event handlers allow users to customize event handler configurations per [alert rule](/chronograf/latest/guides/create-a-kapacitor-alert/).
|
||||
Some event handlers allow users to customize event handler configurations per [alert rule](/{{< latest "chronograf" >}}/guides/create-a-kapacitor-alert/).
|
||||
For example, Chronograf's Slack integration allows users to specify a default channel in the **Configure alert endpoints** section and a different channel for individual alert rules.
|
||||
|
||||
### HipChat
|
||||
|
@ -87,7 +87,7 @@ The following steps describe how to create the API access token:
|
|||
|
||||
Your token appears in the table just above the **Create new token** section:
|
||||
|
||||
![HipChat token](/img/chronograf/latest/g-eventhandlers-hipchattoken.png)
|
||||
![HipChat token](/img/{{< latest "chronograf" >}}/g-eventhandlers-hipchattoken.png)
|
||||
|
||||
|
||||
### Kafka
|
||||
|
@ -112,7 +112,7 @@ Your token appears in the table just above the **Create new token** section:
|
|||
3. Click **Save Changes** to save the configuration settings.
|
||||
4. Click **Send Test Alert** to verify the configuration.
|
||||
|
||||
See [Kafka event handler (Kapacitor)](/kapacitor/latest/event_handlers/kafka/) in the Kapacitor documentation for details about enabling OpsGenie services using TICKscripts.
|
||||
See [Kafka event handler (Kapacitor)](/{{< latest "kapacitor" >}}/event_handlers/kafka/) in the Kapacitor documentation for details about enabling OpsGenie services using TICKscripts.
|
||||
|
||||
|
||||
### OpsGenie
|
||||
|
@ -139,9 +139,9 @@ Send an incident alert to OpsGenie teams and recipients using the Chronograf ale
|
|||
|
||||
See [Alert API](https://docs.opsgenie.com/docs/alert-api) in the OpsGenie documentation for details on the OpsGenie Alert API
|
||||
|
||||
See [OpsGenie V2 event handler](/kapacitor/latest/event_handlers/opsgenie/v2/) in the Kapacitor documentation for details about the OpsGenie V2 event handler.
|
||||
See [OpsGenie V2 event handler](/{{< latest "kapacitor" >}}/event_handlers/opsgenie/v2/) in the Kapacitor documentation for details about the OpsGenie V2 event handler.
|
||||
|
||||
See the [AlertNode (Kapacitor TICKscript node) - OpsGenie v2](/kapacitor/latest/nodes/alert_node/#opsgenie-v2) in the Kapacitor documentation for details about enabling OpsGenie services using TICKscripts.
|
||||
See the [AlertNode (Kapacitor TICKscript node) - OpsGenie v2](/{{< latest "kapacitor" >}}/nodes/alert_node/#opsgenie-v2) in the Kapacitor documentation for details about enabling OpsGenie services using TICKscripts.
|
||||
|
||||
### PagerDuty
|
||||
|
||||
|
@ -165,7 +165,7 @@ Send an alerts about recognized events to PagerDuty using the Chronograf PagerDu
|
|||
|
||||
See the [PagerDuty Events API V2 Overview](https://v2.developer.pagerduty.com/docs/events-api-v2) for details on the PagerDuty Events API and recognized event types (`trigger`, `acknowledge`, and `resolve`).
|
||||
|
||||
See [AlertNode (Kapacitor TICKscript node) - PagerDuty v2](/kapacitor/latest/nodes/alert_node/#pagerduty-v2) in the Kapacitor documentation for details about enabling a new "Generic API" service using TICKscripts.
|
||||
See [AlertNode (Kapacitor TICKscript node) - PagerDuty v2](/{{< latest "kapacitor" >}}/nodes/alert_node/#pagerduty-v2) in the Kapacitor documentation for details about enabling a new "Generic API" service using TICKscripts.
|
||||
|
||||
### Pushover
|
||||
|
||||
|
|
|
@ -10,7 +10,7 @@ menu:
|
|||
|
||||
Chronograf offers a complete dashboard solution for visualizing your data and monitoring your infrastructure:
|
||||
|
||||
* View [pre-created dashboards](/chronograf/latest/guides/using-precreated-dashboards) from the Host List page. Dashboards are available depending on which Telegraf input plugins you have enabled. These pre-created dashboards cannot be cloned or edited.
|
||||
* View [pre-created dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards) from the Host List page. Dashboards are available depending on which Telegraf input plugins you have enabled. These pre-created dashboards cannot be cloned or edited.
|
||||
* Create custom dashboards from scratch by building queries in the Data Explorer, as described [below](#build-a-dashboard).
|
||||
* Import dashboard templates when you add or update a connection in Chronograf. See [Dashboard templates](#dashboard-templates) for details.
|
||||
|
||||
|
@ -23,7 +23,7 @@ By the end of this guide, you'll be aware of the tools available to you for crea
|
|||
|
||||
To perform the tasks in this guide, you must have a working Chronograf instance that is connected to an InfluxDB source.
|
||||
Data is accessed using the Telegraf [system ](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/system) input plugins.
|
||||
For more information, see [Configuring Chronograf](/chronograf/latest/administration/configuration).
|
||||
For more information, see [Configuring Chronograf](/{{< latest "chronograf" >}}/administration/configuration).
|
||||
|
||||
## Build a Dashboard
|
||||
|
||||
|
@ -43,13 +43,13 @@ to open the cell editor mode.
|
|||
|
||||
### Step 3: Create your query
|
||||
|
||||
Click the **Add a Query** button to create an [InfluxQL](/influxdb/latest/query_language/) query.
|
||||
Click the **Add a Query** button to create an [InfluxQL](/{{< latest "influxdb" "v1" >}}/query_language/) query.
|
||||
In query editor mode, use the builder to select from your existing data and allow Chronograf to format the query for you.
|
||||
Alternatively, manually enter and edit a query.
|
||||
Chronograf allows you to move seamlessly between using the builder and manually editing the query; when possible, the interface automatically populates the builder with the information from your raw query.
|
||||
|
||||
For our example, the query builder is used to generate a query that shows the average idle CPU usage grouped by host (in this case, there are three hosts).
|
||||
By default, Chronograf applies the [`MEAN()` function](/influxdb/latest/query_language/functions/#mean) to the data, groups averages into auto-generated time intervals (`:interval:`), and shows data for the past hour (`:dashboardTime:`).
|
||||
By default, Chronograf applies the [`MEAN()` function](/{{< latest "influxdb" "v1" >}}/query_language/functions/#mean) to the data, groups averages into auto-generated time intervals (`:interval:`), and shows data for the past hour (`:dashboardTime:`).
|
||||
Those defaults are configurable using the query builder or by manually editing the query.
|
||||
|
||||
In addition, the time range (`:dashboardTime:`) is [configurable on the dashboard](#step-6-configure-your-dashboard).
|
||||
|
@ -58,7 +58,7 @@ In addition, the time range (`:dashboardTime:`) is [configurable on the dashboar
|
|||
|
||||
### Step 4: Choose your visualization type
|
||||
|
||||
Chronograf supports many different [visualization types](/chronograf/latest/guides/visualization-types/). To choose a visualization type, click **Visualization** and select **Step-Plot Graph**.
|
||||
Chronograf supports many different [visualization types](/{{< latest "chronograf" >}}/guides/visualization-types/). To choose a visualization type, click **Visualization** and select **Step-Plot Graph**.
|
||||
|
||||
![Visualization type](/img/chronograf/1-6-g-dashboard-visualization.png)
|
||||
|
||||
|
@ -80,7 +80,7 @@ Click **Save** (the green checkmark icon) to save your cell.
|
|||
* **Reset** your cell by double-clicking your mouse in the cell window
|
||||
|
||||
> **Note:**
|
||||
These tips only apply to the line, stacked, step-plot, and line+stat [visualization types](/chronograf/latest/guides/visualization-types/).
|
||||
These tips only apply to the line, stacked, step-plot, and line+stat [visualization types](/{{< latest "chronograf" >}}/guides/visualization-types/).
|
||||
|
||||
#### Configure dashboard-wide settings:
|
||||
* Change the dashboard's *selected time* at the top of the page - the default time is **Local**, which uses your browser's local time. Select **UTC** to use Coordinated Universal Time.
|
||||
|
@ -119,4 +119,4 @@ To exit full screen mode, press the Esc key.
|
|||
|
||||
### Template variables
|
||||
Dashboards support template variables.
|
||||
See the [Dashboard Template Variables](/chronograf/latest/guides/dashboard-template-variables/) guide for more information.
|
||||
See the [Dashboard Template Variables](/{{< latest "chronograf" >}}/guides/dashboard-template-variables/) guide for more information.
|
||||
|
|
|
@ -11,9 +11,9 @@ menu:
|
|||
---
|
||||
|
||||
|
||||
Chronograf provides a user interface for [Kapacitor](/kapacitor/latest/), InfluxData's processing framework for creating alerts, ETL jobs (running extract, transform, load), and detecting anomalies in your data.
|
||||
Chronograf provides a user interface for [Kapacitor](/{{< latest "kapacitor" >}}/), InfluxData's processing framework for creating alerts, ETL jobs (running extract, transform, load), and detecting anomalies in your data.
|
||||
Chronograf alert rules correspond to Kapacitor tasks that trigger alerts whenever certain conditions are met.
|
||||
Behind the scenes, these tasks are stored as [TICKscripts](/kapacitor/latest/tick/) that can be edited manually or through Chronograf.
|
||||
Behind the scenes, these tasks are stored as [TICKscripts](/{{< latest "kapacitor" >}}/tick/) that can be edited manually or through Chronograf.
|
||||
Common alerting use cases that can be managed using Chronograf include:
|
||||
|
||||
* Thresholds with static ceilings, floors, and ranges.
|
||||
|
@ -26,13 +26,13 @@ This guide walks through creating a Chronograf alert rule that sends an alert me
|
|||
|
||||
## Requirements
|
||||
|
||||
[Getting started with Chronograf](/chronograf/latest/introduction/getting-started/) offers step-by-step instructions for each of the following requirements:
|
||||
[Getting started with Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/) offers step-by-step instructions for each of the following requirements:
|
||||
|
||||
* Downloaded and install the entire TICKstack (Telegraf, InfluxDB, Chronograf, and Kapacitor).
|
||||
* Configure Telegraf to collect data using the InfluxDB [system statistics](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/system) input plugin and write data to your InfluxDB instance.
|
||||
* [Create a Kapacitor connection in Chronograf](/chronograf/latest/introduction/getting-started/#4-connect-chronograf-to-kapacitor).
|
||||
* Slack is available and configured as an [event handler](/chronograf/latest/troubleshooting/frequently-asked-questions/#what-kapacitor-event-handlers-are-supported-in-chronograf) in Chronograf.
|
||||
See the [Configuring Kapacitor Event Handlers](/chronograf/latest/guides/configuring-alert-endpoints/) guide for detailed configuration instructions.
|
||||
* [Create a Kapacitor connection in Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/#4-connect-chronograf-to-kapacitor).
|
||||
* Slack is available and configured as an [event handler](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#what-kapacitor-event-handlers-are-supported-in-chronograf) in Chronograf.
|
||||
See the [Configuring Kapacitor Event Handlers](/{{< latest "chronograf" >}}/guides/configuring-alert-endpoints/) guide for detailed configuration instructions.
|
||||
|
||||
## Configuring Chronograf alert rules
|
||||
|
||||
|
@ -70,7 +70,7 @@ For this example, select the **Threshold** alert type.
|
|||
Choose the time series data you want the Chronograf alert rule to use.
|
||||
Navigate through databases, measurements, fields, and tags to select the relevant data.
|
||||
|
||||
In this example, select the `telegraf` [database](/influxdb/latest/concepts/glossary/#database), the `autogen` [retention policy](/influxdb/latest/concepts/glossary/#retention-policy-rp), the `cpu` [measurement](/influxdb/latest/concepts/glossary/#measurement), and the `usage_idle` [field](/influxdb/latest/concepts/glossary/#field).
|
||||
In this example, select the `telegraf` [database](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#database), the `autogen` [retention policy](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#retention-policy-rp), the `cpu` [measurement](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#measurement), and the `usage_idle` [field](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#field).
|
||||
|
||||
![Select your data](/img/chronograf/1-6-alerts-time-series.png)
|
||||
|
||||
|
@ -113,7 +113,7 @@ In this example, use the alert message, `Your idle CPU usage is {{.Level}} at {{
|
|||
|
||||
![Specify event handler and alert message](/img/chronograf/1-6-alerts-message.png)
|
||||
|
||||
*View the Kapacitor documentation for more information about [message template data](/kapacitor/latest/nodes/alert_node/#message).*
|
||||
*View the Kapacitor documentation for more information about [message template data](/{{< latest "kapacitor" >}}/nodes/alert_node/#message).*
|
||||
|
||||
### Step 7: Save the alert rule
|
||||
|
||||
|
|
|
@ -115,7 +115,7 @@ Chronograf supports the following template variable types:
|
|||
[Text](#text)
|
||||
|
||||
### Databases
|
||||
Database template variables allow you to select from multiple target [databases](/influxdb/latest/concepts/glossary/#database).
|
||||
Database template variables allow you to select from multiple target [databases](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#database).
|
||||
|
||||
_**Database meta query**_
|
||||
Database template variables use the following meta query to return an array of all databases in your InfluxDB instance.
|
||||
|
@ -133,7 +133,7 @@ SELECT "purchases" FROM :databaseVar:."autogen"."customers"
|
|||
Database template variables are good when visualizing multiple databases with similar or identical data structures. They allow you to quickly switch between visualizations for each of your databases.
|
||||
|
||||
### Measurements
|
||||
Vary the target [measurement](/influxdb/latest/concepts/glossary/#measurement).
|
||||
Vary the target [measurement](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#measurement).
|
||||
|
||||
_**Measurement meta query**_
|
||||
Measurement template variables use the following meta query to return an array of all measurements in a given database.
|
||||
|
@ -152,7 +152,7 @@ Measurement template variables allow you to quickly switch between measurements
|
|||
|
||||
|
||||
### Field Keys
|
||||
Vary the target [field key](/influxdb/latest/concepts/glossary/#field-key).
|
||||
Vary the target [field key](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#field-key).
|
||||
|
||||
_**Field key meta query**_
|
||||
Field key template variables use the following meta query to return an array of all field keys in a given measurement from a given database.
|
||||
|
@ -171,7 +171,7 @@ Field key template variables are great if you want to quickly switch between fie
|
|||
|
||||
|
||||
### Tag Keys
|
||||
Vary the target [tag key](/influxdb/latest/concepts/glossary/#tag-key).
|
||||
Vary the target [tag key](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-key).
|
||||
|
||||
_**Tag key meta query**_
|
||||
Tag key template variables use the following meta query to return an array of all tag keys in a given measurement from a given database.
|
||||
|
@ -190,7 +190,7 @@ Tag key template variables are great if you want to quickly switch between tag k
|
|||
|
||||
|
||||
### Tag Values
|
||||
Vary the target [tag value](/influxdb/latest/concepts/glossary/#tag-value).
|
||||
Vary the target [tag value](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-value).
|
||||
|
||||
_**Tag value meta query**_
|
||||
Tag value template variables use the following meta query to return an array of all values associated with a given tag key in a specified measurement and database.
|
||||
|
@ -222,7 +222,7 @@ value3
|
|||
value4
|
||||
```
|
||||
|
||||
> Since string field values [require single quotes in InfluxQL](/influxdb/latest/troubleshooting/frequently-asked-questions/#when-should-i-single-quote-and-when-should-i-double-quote-in-queries), string values should be wrapped in single quotes.
|
||||
> Since string field values [require single quotes in InfluxQL](/{{< latest "influxdb" "v1" >}}/troubleshooting/frequently-asked-questions/#when-should-i-single-quote-and-when-should-i-double-quote-in-queries), string values should be wrapped in single quotes.
|
||||
|
||||
>```csv
|
||||
'string1','string2','string3','string4'
|
||||
|
@ -253,7 +253,7 @@ key4,value4
|
|||
|
||||
<img src="/img/chronograf/1-6-template-vars-map-dropdown.png" style="width:100%;max-width:140px;" alt="Map variable dropdown"/>
|
||||
|
||||
> If values are meant to be used as string field values, wrap them in single quote ([required by InfluxQL](/influxdb/latest/troubleshooting/frequently-asked-questions/#when-should-i-single-quote-and-when-should-i-double-quote-in-queries)). This only pertains to values. String keys do not matter.
|
||||
> If values are meant to be used as string field values, wrap them in single quote ([required by InfluxQL](/{{< latest "influxdb" "v1" >}}/troubleshooting/frequently-asked-questions/#when-should-i-single-quote-and-when-should-i-double-quote-in-queries)). This only pertains to values. String keys do not matter.
|
||||
|
||||
>```csv
|
||||
key1,'value1'
|
||||
|
|
|
@ -40,7 +40,7 @@ Add the following settings the `[[udp]]` secton in your Kapacitor configuration
|
|||
retention-policy = "autogen"
|
||||
```
|
||||
|
||||
Using this configuration, Kapacitor will listen on port `9100` for UDP packets in [Line Protocol](/influxdb/latest/write_protocols/line_protocol_tutorial/) format.
|
||||
Using this configuration, Kapacitor will listen on port `9100` for UDP packets in [Line Protocol](/{{< latest "influxdb" "v1" >}}/write_protocols/line_protocol_tutorial/) format.
|
||||
Incoming data will be scoped to be in the `game.autogen` database and retention policy.
|
||||
Restart Kapacitor so that the UDP listener service starts.
|
||||
|
||||
|
|
|
@ -10,20 +10,20 @@ menu:
|
|||
|
||||
---
|
||||
|
||||
[InfluxEnterprise](/enterprise_influxdb/latest/) offers high availability and a highly scalable clustering solution for your time series data needs.
|
||||
[InfluxEnterprise](/{{< latest "enterprise_influxdb" >}}/) offers high availability and a highly scalable clustering solution for your time series data needs.
|
||||
Use Chronograf to assess your cluster's health and to monitor the infrastructure behind your project.
|
||||
|
||||
This guide offers step-by-step instructions for using Chronograf, [InfluxDB](/influxdb/latest/), and [Telegraf](/telegraf/latest/) to monitor data nodes in your InfluxEnterprise cluster.
|
||||
This guide offers step-by-step instructions for using Chronograf, [InfluxDB](/{{< latest "influxdb" "v1" >}}/), and [Telegraf](/{{< latest "telegraf" >}}/) to monitor data nodes in your InfluxEnterprise cluster.
|
||||
|
||||
## Requirements
|
||||
|
||||
You have a fully-functioning InfluxEnterprise cluster with authentication enabled.
|
||||
See the InfluxEnterprise documentation for
|
||||
[detailed setup instructions](/enterprise_influxdb/latest/production_installation/).
|
||||
[detailed setup instructions](/{{< latest "enterprise_influxdb" >}}/production_installation/).
|
||||
This guide uses an InfluxData Enterprise cluster with three meta nodes and three data nodes; the steps are also applicable to other cluster configurations.
|
||||
|
||||
InfluxData recommends using a separate server to store your monitoring data.
|
||||
It is possible to store the monitoring data in your cluster and [connect the cluster to Chronograf](/chronograf/latest/troubleshooting/frequently-asked-questions/#how-do-i-connect-chronograf-to-an-influxenterprise-cluster), but, in general, your monitoring data should live on a separate server.
|
||||
It is possible to store the monitoring data in your cluster and [connect the cluster to Chronograf](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#how-do-i-connect-chronograf-to-an-influxenterprise-cluster), but, in general, your monitoring data should live on a separate server.
|
||||
|
||||
You're working on an Ubuntu installation.
|
||||
Chronograf and the other components of the TICK stack are supported on several operating systems and hardware architectures. Check out the [downloads page](https://portal.influxdata.com/downloads) for links to the binaries of your choice.
|
||||
|
@ -35,11 +35,11 @@ Before we begin, here's an overview of the final monitoring setup:
|
|||
![Architecture diagram](/img/chronograf/1-6-cluster-diagram.png)
|
||||
|
||||
The diagram above shows an InfluxEnterprise cluster that consists of three meta nodes (M) and three data nodes (D).
|
||||
Each data node has its own [Telegraf](/telegraf/latest/) instance (T).
|
||||
Each data node has its own [Telegraf](/{{< latest "telegraf" >}}/) instance (T).
|
||||
|
||||
Each Telegraf instance is configured to collect node CPU, disk, and memory data using the Telegraf [system stats](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/system) input plugin.
|
||||
The Telegraf instances are also configured to send those data to a single [InfluxDB OSS](/influxdb/latest/) instance that lives on a separate server.
|
||||
When Telegraf sends data to InfluxDB, it automatically [tags](/influxdb/latest/concepts/glossary/#tag) the data with the hostname of the relevant data node.
|
||||
The Telegraf instances are also configured to send those data to a single [InfluxDB OSS](/{{< latest "influxdb" "v1" >}}/) instance that lives on a separate server.
|
||||
When Telegraf sends data to InfluxDB, it automatically [tags](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag) the data with the hostname of the relevant data node.
|
||||
|
||||
The InfluxDB OSS instance that stores the Telegraf data is connected to Chronograf.
|
||||
Chronograf uses the hostnames in the Telegraf data to populate the Host List page and provide other hostname-specific information in the user interface.
|
||||
|
@ -54,7 +54,7 @@ InfluxDB can be downloaded from the [InfluxData downloads page](https://portal.i
|
|||
|
||||
#### Step 2: Enable authentication
|
||||
|
||||
For security purposes, enable authentication in the InfluxDB [configuration file (influxdb.conf)](/influxdb/latest/administration/config/), which is located in `/etc/influxdb/influxdb.conf`.
|
||||
For security purposes, enable authentication in the InfluxDB [configuration file (influxdb.conf)](/{{< latest "influxdb" "v1" >}}/administration/config/), which is located in `/etc/influxdb/influxdb.conf`.
|
||||
|
||||
In the `[http]` section of the configuration file, uncomment the `auth-enabled` option and set it to `true`:
|
||||
|
||||
|
@ -80,7 +80,7 @@ Next, start the InfluxDB process:
|
|||
|
||||
#### Step 4: Create an admin user
|
||||
|
||||
Create an [admin user](/influxdb/latest/query_language/authentication_and_authorization/#user-types-and-privileges) on your InfluxDB instance.
|
||||
Create an [admin user](/{{< latest "influxdb" "v1" >}}/query_language/authentication_and_authorization/#user-types-and-privileges) on your InfluxDB instance.
|
||||
Because you enabled authentication, you must perform this step before moving on to the next section.
|
||||
Run the command below to create an admin user, replacing `chronothan` and `supersecret` with your own username and password.
|
||||
Note that the password requires single quotes.
|
||||
|
@ -178,7 +178,7 @@ Replace the `chronothan` and `supersecret` values with your actual username and
|
|||
```
|
||||
|
||||
The expected output is similar to the JSON in the codeblock below.
|
||||
In this case, the `telegraf` database has three different [tag values](/influxdb/latest/concepts/glossary/#tag-value) for the `host` [tag key](/influxdb/latest/concepts/glossary/#tag-key): `data-node-01`, `data-node-02`, and `data-node-03`.
|
||||
In this case, the `telegraf` database has three different [tag values](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-value) for the `host` [tag key](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-key): `data-node-01`, `data-node-02`, and `data-node-03`.
|
||||
Those values match the hostnames of the three data nodes in the cluster; this means Telegraf is successfully writing monitoring data from those hosts to the InfluxDB OSS instance!
|
||||
```
|
||||
{
|
||||
|
@ -258,6 +258,6 @@ In the image below, the Chronograf query editor is used to visualize the idle CP
|
|||
![Data Explorer](/img/chronograf/1-6-cluster-de.png)
|
||||
|
||||
Create more customized graphs and save them to a dashboard on the Dashboard page in Chronograf.
|
||||
See the [Creating Chronograf dashboards](/chronograf/latest/guides/create-a-dashboard/) guide for more information.
|
||||
See the [Creating Chronograf dashboards](/{{< latest "chronograf" >}}/guides/create-a-dashboard/) guide for more information.
|
||||
|
||||
That's it! You've successfully configured Telegraf to collect and write data, InfluxDB to store those data, and Chonograf to use those data for monitoring and visualization purposes.
|
||||
|
|
|
@ -7,7 +7,7 @@ menu:
|
|||
weight: 130
|
||||
parent: Guides
|
||||
---
|
||||
Explore and visualize your data in the **Data Explorer**. For both InfluxQL and Flux, Chronograf allows you to move seamlessly between using the builder or templates and manually editing the query; when possible, the interface automatically populates the builder with the information from your raw query. Choose between [visualization types](/chronograf/latest/guides/visualization-types/) for your query.
|
||||
Explore and visualize your data in the **Data Explorer**. For both InfluxQL and Flux, Chronograf allows you to move seamlessly between using the builder or templates and manually editing the query; when possible, the interface automatically populates the builder with the information from your raw query. Choose between [visualization types](/{{< latest "chronograf" >}}/guides/visualization-types/) for your query.
|
||||
|
||||
To open the **Data Explorer**, click the **Explore** icon in the navigation bar:
|
||||
|
||||
|
@ -23,7 +23,7 @@ To open the **Data Explorer**, click the **Explore** icon in the navigation bar:
|
|||
|
||||
## Explore data with InfluxQL
|
||||
|
||||
InfluxQL is a SQL-like query language you can use to interact with data in InfluxDB. For detailed tutorials and reference material, see our [InfluxQL documentation](/influxdb/latest/query_language/).
|
||||
InfluxQL is a SQL-like query language you can use to interact with data in InfluxDB. For detailed tutorials and reference material, see our [InfluxQL documentation](/{{< latest "influxdb" "v1" >}}/query_language/).
|
||||
|
||||
1. Open the Data Explorer and click **Add a Query**.
|
||||
2. To the right of the source dropdown above the graph placeholder, select **InfluxQL** as the source type.
|
||||
|
@ -66,7 +66,7 @@ Flux is InfluxData's new functional data scripting language designed for queryin
|
|||
|
||||
## Visualize your query
|
||||
|
||||
Select the **Visualization** tab at the top of the **Data Explorer**. For details about all of the available visualization options, see [Visualization types in Chronograf](/chronograf/latest/guides/visualization-types/).
|
||||
Select the **Visualization** tab at the top of the **Data Explorer**. For details about all of the available visualization options, see [Visualization types in Chronograf](/{{< latest "chronograf" >}}/guides/visualization-types/).
|
||||
|
||||
## Add queries to dashboards
|
||||
|
||||
|
|
|
@ -13,7 +13,7 @@ menu:
|
|||
|
||||
Pre-created dashboards are delivered with Chronograf depending on which Telegraf input plugins you have enabled and are available from the Host List page. These dashboards, which are built in and not editable, include cells with data visualizations for metrics that are relevant to data sources you are likely to be using.
|
||||
|
||||
> Note that these pre-created dashboards cannot be cloned or customized. They appear only as part of the Host List view and are associated with metrics gathered from a single host. Dashboard templates are also available and deliver a solid starting point for customizing your own unique dashboards based on the Telegraf plugins enabled and operate across one or more hosts. For details, see [Dashboard templates](/chronograf/latest/guides/create-a-dashboard/#dashboard-templates).
|
||||
> Note that these pre-created dashboards cannot be cloned or customized. They appear only as part of the Host List view and are associated with metrics gathered from a single host. Dashboard templates are also available and deliver a solid starting point for customizing your own unique dashboards based on the Telegraf plugins enabled and operate across one or more hosts. For details, see [Dashboard templates](/{{< latest "chronograf" >}}/guides/create-a-dashboard/#dashboard-templates).
|
||||
|
||||
## Requirements
|
||||
|
||||
|
@ -33,7 +33,7 @@ Pre-created dashboards are delivered in Chronograf installations and are ready t
|
|||
|
||||
The pre-created dashboards available for use with Chronograf are listed below as Apps and appear in the Apps listing for hosts in the Host List page. The listings for apps (pre-created dashboards) on this page include information about the required Telegraf input plugins, JSON files included in the apps, and listings of the cell titles that are included in each of the JSON files.
|
||||
|
||||
The JSON files for the precreated dashboards are delivered on installation in the `/usr/share/chronograf/canned` directory. Information about the configuration option `--canned-path` can be found in the [Chronograf configuration options](/chronograf/latest/administration/config-options/#) page.
|
||||
The JSON files for the precreated dashboards are delivered on installation in the `/usr/share/chronograf/canned` directory. Information about the configuration option `--canned-path` can be found in the [Chronograf configuration options](/{{< latest "chronograf" >}}/administration/config-options/#) page.
|
||||
|
||||
You can enable and disable applications in your [Telegraf configuration file](https://github.com/influxdata/telegraf/blob/master/etc/telegraf.conf).
|
||||
See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/docs/CONFIGURATION.md) for details.
|
||||
|
@ -65,7 +65,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
|
|||
|
||||
## apache
|
||||
|
||||
**Required Telegraf plugin:** [Apache input plugin](/telegraf/latest/plugins/inputs/#apache-http-server)
|
||||
**Required Telegraf plugin:** [Apache input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#apache-http-server)
|
||||
|
||||
`apache.json`
|
||||
|
||||
|
@ -75,7 +75,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
|
|||
|
||||
## consul
|
||||
|
||||
**Required Telegraf plugin:** [Consul input plugin](/telegraf/latest/plugins/inputs/#consul)
|
||||
**Required Telegraf plugin:** [Consul input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#consul)
|
||||
|
||||
`consul_http.json`
|
||||
|
||||
|
@ -95,7 +95,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
|
|||
|
||||
## docker
|
||||
|
||||
**Required Telegraf plugin:** [Docker input plugin](/telegraf/latest/plugins/inputs/#docker)
|
||||
**Required Telegraf plugin:** [Docker input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#docker)
|
||||
|
||||
`docker.json`
|
||||
|
||||
|
@ -115,7 +115,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
|
|||
|
||||
## elasticsearch
|
||||
|
||||
**Required Telegraf plugin:** [Elasticsearch input plugin](/telegraf/latest/plugins/inputs/#elasticsearch)
|
||||
**Required Telegraf plugin:** [Elasticsearch input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#elasticsearch)
|
||||
|
||||
`elasticsearch.json`
|
||||
|
||||
|
@ -132,7 +132,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
|
|||
|
||||
## haproxy
|
||||
|
||||
**Required Telegraf plugin:** [HAProxy input plugin](/telegraf/latest/plugins/inputs/#haproxy)
|
||||
**Required Telegraf plugin:** [HAProxy input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#haproxy)
|
||||
|
||||
`haproxy.json`
|
||||
|
||||
|
@ -162,7 +162,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
|
|||
|
||||
## influxdb
|
||||
|
||||
**Required Telegraf plugin:** [InfluxDB input plugin](/telegraf/latest/plugins/inputs/#influxdb-v-1)
|
||||
**Required Telegraf plugin:** [InfluxDB input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#influxdb-v-1)
|
||||
|
||||
`influxdb_database.json`
|
||||
|
||||
|
@ -207,7 +207,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
|
|||
|
||||
## Memcached (`memcached`)
|
||||
|
||||
**Required Telegraf plugin:** [Memcached input plugin](/telegraf/latest/plugins/inputs/#memcached)
|
||||
**Required Telegraf plugin:** [Memcached input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#memcached)
|
||||
|
||||
`memcached.json`
|
||||
|
||||
|
@ -227,7 +227,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
|
|||
|
||||
## mesos
|
||||
|
||||
**Required Telegraf plugin:** [Mesos input plugin](/telegraf/latest/plugins/inputs/#mesos)
|
||||
**Required Telegraf plugin:** [Mesos input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#mesos)
|
||||
|
||||
`mesos.json`
|
||||
|
||||
|
@ -242,7 +242,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
|
|||
|
||||
## mongodb
|
||||
|
||||
**Required Telegraf plugin:** [MongoDB input plugin](/telegraf/latest/plugins/inputs/#mongodb)
|
||||
**Required Telegraf plugin:** [MongoDB input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#mongodb)
|
||||
|
||||
`mongodb.json`
|
||||
|
||||
|
@ -254,7 +254,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
|
|||
|
||||
## mysql
|
||||
|
||||
**Required Telegraf plugin:** [MySQL input plugin](/telegraf/latest/plugins/inputs/#mysql)
|
||||
**Required Telegraf plugin:** [MySQL input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#mysql)
|
||||
|
||||
`mysql.json`
|
||||
|
||||
|
@ -265,7 +265,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
|
|||
|
||||
## nginx
|
||||
|
||||
**Required Telegraf plugin:** [NGINX input plugin](/telegraf/latest/plugins/inputs/#nginx)
|
||||
**Required Telegraf plugin:** [NGINX input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#nginx)
|
||||
|
||||
`nginx.json`
|
||||
|
||||
|
@ -276,7 +276,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
|
|||
|
||||
## nsq
|
||||
|
||||
**Required Telegraf plugin:** [NSQ input plugin](/telegraf/latest/plugins/inputs/#nsq)
|
||||
**Required Telegraf plugin:** [NSQ input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#nsq)
|
||||
|
||||
`nsq_channel.json`
|
||||
|
||||
|
@ -297,7 +297,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
|
|||
|
||||
## phpfpm
|
||||
|
||||
**Required Telegraf plugin:** [PHPfpm input plugin](/telegraf/latest/plugins/inputs/#php-fpm)
|
||||
**Required Telegraf plugin:** [PHPfpm input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#php-fpm)
|
||||
|
||||
`phpfpm.json`
|
||||
|
||||
|
@ -309,7 +309,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
|
|||
|
||||
## ping
|
||||
|
||||
**Required Telegraf plugin:** [Ping input plugin](/telegraf/latest/plugins/inputs/#ping)
|
||||
**Required Telegraf plugin:** [Ping input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#ping)
|
||||
|
||||
`ping.json`
|
||||
|
||||
|
@ -318,7 +318,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
|
|||
|
||||
## postgresql
|
||||
|
||||
**Required Telegraf plugin:** [PostgreSQL input plugin](/telegraf/latest/plugins/inputs/#postgresql)
|
||||
**Required Telegraf plugin:** [PostgreSQL input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#postgresql)
|
||||
|
||||
`postgresql.json`
|
||||
|
||||
|
@ -329,7 +329,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
|
|||
|
||||
## rabbitmq
|
||||
|
||||
**Required Telegraf plugin:** [RabbitMQ input plugin](/telegraf/latest/plugins/inputs/#rabbitmq)
|
||||
**Required Telegraf plugin:** [RabbitMQ input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#rabbitmq)
|
||||
|
||||
`rabbitmq.json`
|
||||
|
||||
|
@ -340,7 +340,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
|
|||
|
||||
## redis
|
||||
|
||||
**Required Telegraf plugin:** [Redis input plugin](/telegraf/latest/plugins/inputs/#redis)
|
||||
**Required Telegraf plugin:** [Redis input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#redis)
|
||||
|
||||
|
||||
`redis.json`
|
||||
|
@ -352,7 +352,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
|
|||
|
||||
## riak
|
||||
|
||||
**Required Telegraf plugin:** [Riak input plugin](/telegraf/latest/plugins/inputs/#riak)
|
||||
**Required Telegraf plugin:** [Riak input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#riak)
|
||||
|
||||
|
||||
`riak.json`
|
||||
|
@ -371,7 +371,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
|
|||
|
||||
### cpu
|
||||
|
||||
**Required Telegraf plugin:** [CPU input plugin](/telegraf/latest/plugins/inputs/#cpu)
|
||||
**Required Telegraf plugin:** [CPU input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#cpu)
|
||||
|
||||
`cpu.json`
|
||||
|
||||
|
@ -381,13 +381,13 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
|
|||
|
||||
`disk.json`
|
||||
|
||||
**Required Telegraf plugin:** [Disk input plugin](/telegraf/latest/plugins/inputs/#disk)
|
||||
**Required Telegraf plugin:** [Disk input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#disk)
|
||||
|
||||
* "System - Disk used %"
|
||||
|
||||
### diskio
|
||||
|
||||
**Required Telegraf plugin:** [DiskIO input plugin](/telegraf/latest/plugins/inputs/#diskio)
|
||||
**Required Telegraf plugin:** [DiskIO input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#diskio)
|
||||
|
||||
`diskio.json`
|
||||
|
||||
|
@ -396,7 +396,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
|
|||
|
||||
### mem
|
||||
|
||||
**Required Telegraf plugin:** [Mem input plugin](/telegraf/latest/plugins/inputs/#mem)
|
||||
**Required Telegraf plugin:** [Mem input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#mem)
|
||||
|
||||
`mem.json`
|
||||
|
||||
|
@ -404,7 +404,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
|
|||
|
||||
### net
|
||||
|
||||
**Required Telegraf plugin:** [Net input plugin](/telegraf/latest/plugins/inputs/#net)
|
||||
**Required Telegraf plugin:** [Net input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#net)
|
||||
|
||||
`net.json`
|
||||
|
||||
|
@ -413,7 +413,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
|
|||
|
||||
### netstat
|
||||
|
||||
**Required Telegraf plugin:** [Netstat input plugin](/telegraf/latest/plugins/inputs/#netstat)
|
||||
**Required Telegraf plugin:** [Netstat input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#netstat)
|
||||
|
||||
`netstat.json`
|
||||
|
||||
|
@ -422,7 +422,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
|
|||
|
||||
### processes
|
||||
|
||||
**Required Telegraf plugin:** [Processes input plugin](/telegraf/latest/plugins/inputs/#processes)
|
||||
**Required Telegraf plugin:** [Processes input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#processes)
|
||||
|
||||
`processes.json`
|
||||
|
||||
|
@ -430,7 +430,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
|
|||
|
||||
### procstat
|
||||
|
||||
**Required Telegraf plugin:** [Procstat input plugin](/telegraf/latest/plugins/inputs/#procstat)
|
||||
**Required Telegraf plugin:** [Procstat input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#procstat)
|
||||
|
||||
`procstat.json`
|
||||
|
||||
|
@ -439,7 +439,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
|
|||
|
||||
### system
|
||||
|
||||
**Required Telegraf plugin:** [Procstat input plugin](/telegraf/latest/plugins/inputs/#procstat)
|
||||
**Required Telegraf plugin:** [Procstat input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#procstat)
|
||||
|
||||
`load.json`
|
||||
|
||||
|
@ -447,7 +447,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
|
|||
|
||||
## varnish
|
||||
|
||||
**Required Telegraf plugin:** [Varnish](/telegraf/latest/plugins/inputs/#varnish)
|
||||
**Required Telegraf plugin:** [Varnish](/{{< latest "telegraf" >}}/plugins/inputs/#varnish)
|
||||
|
||||
`varnish.json`
|
||||
|
||||
|
@ -456,7 +456,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
|
|||
|
||||
## win_system
|
||||
|
||||
**Required Telegraf plugin:** [Windows Performance Counters input plugin](/telegraf/latest/plugins/inputs/#windows-performance-counters)
|
||||
**Required Telegraf plugin:** [Windows Performance Counters input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#windows-performance-counters)
|
||||
|
||||
`win_cpu.json`
|
||||
|
||||
|
|
|
@ -8,7 +8,7 @@ menu:
|
|||
parent: Guides
|
||||
---
|
||||
|
||||
Chronograf's dashboard views support the following visualization types, which can be selected in the **Visualization Type** selection view of the [Data Explorer](/chronograf/latest/querying-data) .
|
||||
Chronograf's dashboard views support the following visualization types, which can be selected in the **Visualization Type** selection view of the [Data Explorer](/{{< latest "chronograf" >}}/querying-data) .
|
||||
|
||||
[Visualization Type selector](/img/chronograf/1-6-viz-types-selector.png)
|
||||
|
||||
|
@ -180,10 +180,10 @@ The **Single Stat** view displays the most recent value of the specified time se
|
|||
|
||||
![Single Stat view](/img/chronograf/1-6-viz-single-stat-selector.png)
|
||||
|
||||
If a cell's query includes a [`GROUP BY` tag](/influxdb/latest/query_language/data_exploration/#group-by-tags) clause, Chronograf sorts the different [series](/influxdb/latest/concepts/glossary/#series) lexicographically and shows the most recent [field value](/influxdb/latest/concepts/glossary/#field-value) associated with the first series.
|
||||
For example, if a query groups by the `name` [tag key](/influxdb/latest/concepts/glossary/#tag-key) and `name` has two [tag values](/influxdb/latest/concepts/glossary/#tag-value) (`chronelda` and `chronz`), Chronograf shows the most recent field value associated with the `chronelda` series.
|
||||
If a cell's query includes a [`GROUP BY` tag](/{{< latest "influxdb" "v1" >}}/query_language/data_exploration/#group-by-tags) clause, Chronograf sorts the different [series](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#series) lexicographically and shows the most recent [field value](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#field-value) associated with the first series.
|
||||
For example, if a query groups by the `name` [tag key](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-key) and `name` has two [tag values](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-value) (`chronelda` and `chronz`), Chronograf shows the most recent field value associated with the `chronelda` series.
|
||||
|
||||
If a cell's query includes more than one [field key](/influxdb/latest/concepts/glossary/#field-key) in the [`SELECT` clause](/influxdb/latest/query_language/data_exploration/#select-clause), Chronograf returns the most recent field value associated with the first field key in the `SELECT` clause.
|
||||
If a cell's query includes more than one [field key](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#field-key) in the [`SELECT` clause](/{{< latest "influxdb" "v1" >}}/query_language/data_exploration/#select-clause), Chronograf returns the most recent field value associated with the first field key in the `SELECT` clause.
|
||||
For example, if a query's `SELECT` clause is `SELECT "chronogiraffe","chronelda"`, Chronograf shows the most recent field value associated with the `chronogiraffe` field key.
|
||||
|
||||
#### Single Stat Controls
|
||||
|
|
|
@ -15,11 +15,11 @@ Follow the links below to get acquainted with Chronograf:
|
|||
Chronograf is supported on several operating systems and hardware architectures.
|
||||
See the [InfluxData downloads page](https://portal.influxdata.com/downloads) page for to the available binaries.
|
||||
|
||||
## [Installing Chronograf](/chronograf/latest/introduction/installation/)
|
||||
## [Installing Chronograf](/{{< latest "chronograf" >}}/introduction/installation/)
|
||||
|
||||
[Installing Chronograf](/chronograf/latest/introduction/installation/) lists the requirements for installing, starting, and configuring Chronograf.
|
||||
[Installing Chronograf](/{{< latest "chronograf" >}}/introduction/installation/) lists the requirements for installing, starting, and configuring Chronograf.
|
||||
|
||||
## Getting Started
|
||||
[Getting started with Chronograf](/chronograf/latest/introduction/getting-started/) gets you up and running with Chronograf with as little configuration and code as possible.
|
||||
[Getting started with Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/) gets you up and running with Chronograf with as little configuration and code as possible.
|
||||
By the end of the guide, you will have downloaded, installed, and configured all four packages of the
|
||||
TICK stack ([Telegraf](https://github.com/influxdata/telegraf), [InfluxDB](https://github.com/influxdata/influxdb), Chronograf, and [Kapacitor](https://github.com/influxdata/kapacitor)), and you will be all set to monitor your infrastructure.
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Getting started with Chronograf
|
||||
aliases:
|
||||
- /chronograf/latest/introduction/getting-started/
|
||||
- /{{< latest "chronograf" >}}/introduction/getting-started/
|
||||
- /chronograf/v1.7/introduction/getting_started/
|
||||
menu:
|
||||
chronograf_1_7:
|
||||
|
@ -11,18 +11,18 @@ menu:
|
|||
---
|
||||
|
||||
## Overview
|
||||
Chronograf allows you to quickly see data you have stored in InfluxDB so you can build robust queries and alerts. After your administrator has set up Chronograf as described in [Installing Chronograf](/chronograf/latest/introduction/installation), get started with key features using the guides below.
|
||||
Chronograf allows you to quickly see data you have stored in InfluxDB so you can build robust queries and alerts. After your administrator has set up Chronograf as described in [Installing Chronograf](/{{< latest "chronograf" >}}/introduction/installation), get started with key features using the guides below.
|
||||
|
||||
### Data visualization
|
||||
* Investigate your data by building queries using the [Data Explorer](/chronograf/latest/guides/querying-data/).
|
||||
* Use [pre-created dashboards](/chronograf/latest/guides/using-precreated-dashboards/) to monitor your application data or [create your own dashboards](/chronograf/latest/guides/create-a-dashboard/).
|
||||
* Customize dashboards using [template variables](/chronograf/latest/guides/dashboard-template-variables/).
|
||||
* Investigate your data by building queries using the [Data Explorer](/{{< latest "chronograf" >}}/guides/querying-data/).
|
||||
* Use [pre-created dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards/) to monitor your application data or [create your own dashboards](/{{< latest "chronograf" >}}/guides/create-a-dashboard/).
|
||||
* Customize dashboards using [template variables](/{{< latest "chronograf" >}}/guides/dashboard-template-variables/).
|
||||
|
||||
### Alerting
|
||||
* [Create alert rules](/chronograf/latest/guides/create-alert-rules/) to generate threshold, relative, and deadman alerts on your data.
|
||||
* [View all active alerts](/chronograf/latest/guides/create-alert-rules/#step-2-view-the-alerts) on an alert dashboard.
|
||||
* Use [alert endpoints](/chronograf/latest/guides/configuring-alert-endpoints/) in Chronograf to send alert messages to specific URLs and applications.
|
||||
* [Create alert rules](/{{< latest "chronograf" >}}/guides/create-alert-rules/) to generate threshold, relative, and deadman alerts on your data.
|
||||
* [View all active alerts](/{{< latest "chronograf" >}}/guides/create-alert-rules/#step-2-view-the-alerts) on an alert dashboard.
|
||||
* Use [alert endpoints](/{{< latest "chronograf" >}}/guides/configuring-alert-endpoints/) in Chronograf to send alert messages to specific URLs and applications.
|
||||
|
||||
### Infrastructure monitoring
|
||||
* [View all hosts](/chronograf/latest/guides/monitoring-influxenterprise-clusters/#step-4-explore-the-monitoring-data-in-chronograf) and their statuses in your infrastructure.
|
||||
* [Use pre-created dashboards](/chronograf/latest/guides/using-precreated-dashboards/) to monitor your applications.
|
||||
* [View all hosts](/{{< latest "chronograf" >}}/guides/monitoring-influxenterprise-clusters/#step-4-explore-the-monitoring-data-in-chronograf) and their statuses in your infrastructure.
|
||||
* [Use pre-created dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards/) to monitor your applications.
|
||||
|
|
|
@ -9,4 +9,4 @@ menu:
|
|||
|
||||
Follow the link below to access Chronograf's FAQ.
|
||||
|
||||
## [Frequently Asked Questions](/chronograf/latest/troubleshooting/frequently-asked-questions/)
|
||||
## [Frequently Asked Questions](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/)
|
||||
|
|
|
@ -9,7 +9,7 @@ menu:
|
|||
|
||||
## How do I connect Chronograf to an InfluxEnterprise cluster?
|
||||
|
||||
The connection details form requires additional information when connecting Chronograf to an [InfluxEnterprise cluster](https://docs.influxdata.com/enterprise_influxdb/latest/).
|
||||
The connection details form requires additional information when connecting Chronograf to an [InfluxEnterprise cluster](/{{< latest "enterprise_influxdb" >}}/).
|
||||
|
||||
When you enter the InfluxDB HTTP bind address in the `Connection String` input, Chronograf automatically checks if that InfluxDB instance is a data node.
|
||||
If it is a data node, Chronograf automatically adds the `Meta Service Connection URL` input to the connection details form.
|
||||
|
@ -19,4 +19,4 @@ Enter the HTTP bind address of one of your cluster's meta nodes into that input
|
|||
|
||||
Note that the example above assumes that you do not have authentication enabled.
|
||||
If you have authentication enabled, the form requires username and password information.
|
||||
For more details about monitoring an InfluxEnterprise cluster, see the [Monitor an InfluxEnterprise Cluster](/chronograf/latest/guides/monitoring-influxenterprise-clusters/) guide.
|
||||
For more details about monitoring an InfluxEnterprise cluster, see the [Monitor an InfluxEnterprise Cluster](/{{< latest "chronograf" >}}/guides/monitoring-influxenterprise-clusters/) guide.
|
||||
|
|
|
@ -38,7 +38,7 @@ Chronograf offers a UI for [Kapacitor](https://github.com/influxdata/kapacitor),
|
|||
|
||||
* Create and delete databases and retention policies
|
||||
* View currently-running queries and stop inefficient queries from overloading your system
|
||||
* Create, delete, and assign permissions to users (Chronograf supports [InfluxDB OSS](/influxdb/latest/administration/authentication_and_authorization/#authorization) and InfluxEnterprise user management)
|
||||
* Create, delete, and assign permissions to users (Chronograf supports [InfluxDB OSS](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#authorization) and InfluxEnterprise user management)
|
||||
|
||||
|
||||
### Multi-organization and multi-user support
|
||||
|
|
|
@ -920,9 +920,9 @@ menu:
|
|||
### UI improvements
|
||||
|
||||
* When dashboard time range is changed, reset graphs that are zoomed in
|
||||
* [Bar graph](/chronograf/latest/guides/visualization-types/#bar-graph) option added to dashboard
|
||||
* [Bar graph](/{{< latest "chronograf" >}}/guides/visualization-types/#bar-graph) option added to dashboard
|
||||
* Redesign source management table to be more intuitive
|
||||
* Redesign [Line + Single Stat](/chronograf/latest/guides/visualization-types/#line-graph-single-stat) cells to appear more like a sparkline, and improve legibility
|
||||
* Redesign [Line + Single Stat](/{{< latest "chronograf" >}}/guides/visualization-types/#line-graph-single-stat) cells to appear more like a sparkline, and improve legibility
|
||||
|
||||
|
||||
## v1.3.2.0 [2017-06-05]
|
||||
|
@ -938,7 +938,7 @@ menu:
|
|||
|
||||
### Features
|
||||
|
||||
* Add UI to the Data Explorer for [writing data to InfluxDB](/chronograf/latest/guides/querying-data/)
|
||||
* Add UI to the Data Explorer for [writing data to InfluxDB](/{{< latest "chronograf" >}}/guides/querying-data/)
|
||||
|
||||
### UI improvements
|
||||
|
||||
|
@ -958,26 +958,26 @@ In versions 1.3.1+, installing a new version of Chronograf automatically clears
|
|||
|
||||
### Bug fixes
|
||||
|
||||
* Fix infinite spinner when `/chronograf` is a [basepath](/chronograf/latest/administration/config-options/#p-basepath)
|
||||
* Fix infinite spinner when `/chronograf` is a [basepath](/{{< latest "chronograf" >}}/administration/config-options/#p-basepath)
|
||||
* Remove the query templates dropdown from dashboard cell editor mode
|
||||
* Fix the backwards sort arrows in table column headers
|
||||
* Make the logout button consistent with design
|
||||
* Fix the loading spinner on graphs
|
||||
* Filter out any template variable values that are empty, whitespace, or duplicates
|
||||
* Allow users to click the add query button after selecting singleStat as the [visualization type](/chronograf/latest/guides/visualization-types)
|
||||
* Allow users to click the add query button after selecting singleStat as the [visualization type](/{{< latest "chronograf" >}}/guides/visualization-types)
|
||||
* Add a query for windows uptime - thank you, @brianbaker!
|
||||
|
||||
### Features
|
||||
|
||||
* Add log event handler- thank you, @mpchadwick!
|
||||
* Update Go (golang) vendoring to dep and committed vendor directory
|
||||
* Add autocomplete functionality to [template variable](/chronograf/latest/guides/dashboard-template-variables) dropdowns
|
||||
* Add autocomplete functionality to [template variable](/{{< latest "chronograf" >}}/guides/dashboard-template-variables) dropdowns
|
||||
|
||||
### UI improvements
|
||||
|
||||
* Refactor scrollbars to support non-webkit browsers
|
||||
* Increase the query builder's default height in cell editor mode and in the data explorer
|
||||
* Make the [template variables](/chronograf/latest/guides/dashboard-template-variables) manager more space efficient
|
||||
* Make the [template variables](/{{< latest "chronograf" >}}/guides/dashboard-template-variables) manager more space efficient
|
||||
* Add page spinners to pages that did not have them
|
||||
* Denote which source is connected in the sources table
|
||||
* Use milliseconds in the InfluxDB dashboard instead of nanoseconds
|
||||
|
@ -987,25 +987,25 @@ In versions 1.3.1+, installing a new version of Chronograf automatically clears
|
|||
|
||||
### Bug fixes
|
||||
|
||||
* Fix the link to home when using the [`--basepath` option](/chronograf/latest/administration/config-options/#p-basepath)
|
||||
* Fix the link to home when using the [`--basepath` option](/{{< latest "chronograf" >}}/administration/config-options/#p-basepath)
|
||||
* Remove the notification to login on the login page
|
||||
* Support queries that perform math on functions
|
||||
* Prevent the creation of blank template variables
|
||||
* Ensure thresholds for Kapacitor Rule Alerts appear on page load
|
||||
* Update the Kapacitor configuration page when the configuration changes
|
||||
* Fix Authentication when using Chronograf with a set [basepath](/chronograf/latest/administration/config-options/#p-basepath)
|
||||
* Fix Authentication when using Chronograf with a set [basepath](/{{< latest "chronograf" >}}/administration/config-options/#p-basepath)
|
||||
* Show red indicator on Hosts Page for an offline host
|
||||
* Support escaping from presentation mode in Safari
|
||||
* Re-implement level colors on the alerts page
|
||||
* Fix router bug introduced by upgrading to react-router v3.0
|
||||
* Show legend on [Line+Stat](/chronograf/latest/guides/visualization-types/#line-graph-single-stat) visualization type
|
||||
* Show legend on [Line+Stat](/{{< latest "chronograf" >}}/guides/visualization-types/#line-graph-single-stat) visualization type
|
||||
* Prevent queries with `:dashboardTime:` from breaking the query builder
|
||||
|
||||
### Features
|
||||
|
||||
* Add line-protocol proxy for InfluxDB/InfluxEnterprise Cluster data sources
|
||||
* Add `:dashboardTime:` to support cell-specific time ranges on dashboards
|
||||
* Add support for enabling and disabling [TICKscripts that were created outside Chronograf](/chronograf/latest/guides/advanced-kapacitor/#tickscript-management)
|
||||
* Add support for enabling and disabling [TICKscripts that were created outside Chronograf](/{{< latest "chronograf" >}}/guides/advanced-kapacitor/#tickscript-management)
|
||||
* Allow users to delete Kapacitor configurations
|
||||
|
||||
### UI improvements
|
||||
|
|
|
@ -8,7 +8,7 @@ menu:
|
|||
parent: Administration
|
||||
---
|
||||
|
||||
The connection details form requires additional information when connecting Chronograf to an [InfluxDB Enterprise cluster](https://docs.influxdata.com/enterprise_influxdb/latest/).
|
||||
The connection details form requires additional information when connecting Chronograf to an [InfluxDB Enterprise cluster](/{{< latest "enterprise_influxdb" >}}/).
|
||||
|
||||
When you enter the InfluxDB HTTP bind address in the `Connection String` input, Chronograf automatically checks if that InfluxDB instance is a data node.
|
||||
If it is a data node, Chronograf automatically adds the `Meta Service Connection URL` input to the connection details form.
|
||||
|
@ -19,4 +19,4 @@ Enter the HTTP bind address of one of your cluster's meta nodes into that input
|
|||
Note that the example above assumes that you do not have authentication enabled.
|
||||
If you have authentication enabled, the form requires username and password information.
|
||||
|
||||
For details about monitoring InfluxEnterprise clusters, see [Monitoring InfluxDB Enterprise clusters](/chronograf/latest/guides/monitoring-influxenterprise-clusters).
|
||||
For details about monitoring InfluxEnterprise clusters, see [Monitoring InfluxDB Enterprise clusters](/{{< latest "chronograf" >}}/guides/monitoring-influxenterprise-clusters).
|
||||
|
|
|
@ -94,7 +94,7 @@ Environment variable: `$BOLT_PATH`
|
|||
|
||||
#### `--canned-path=` | `-c`
|
||||
|
||||
The path to the directory of [canned dashboards](/chronograf/latest/guides/using-precreated-dashboards) files.
|
||||
The path to the directory of [canned dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards) files.
|
||||
|
||||
Default value: `/usr/share/chronograf/canned`
|
||||
|
||||
|
|
|
@ -39,7 +39,7 @@ Use one of the following commands to start Chronograf:
|
|||
## Set custom default Chronograf configuration options
|
||||
|
||||
Custom default Chronograf configuration settings can be defined in `/etc/default/chronograf`.
|
||||
This file consists of key-value pairs. See keys (environment variables) for [Chronograf configuration options](https://docs.influxdata.com/chronograf/v1.8/administration/config-options), and set values for the keys you want to configure.
|
||||
This file consists of key-value pairs. See keys (environment variables) for [Chronograf configuration options](/chronograf/v1.8/administration/config-options), and set values for the keys you want to configure.
|
||||
|
||||
```conf
|
||||
HOST=0.0.0.0
|
||||
|
|
|
@ -31,15 +31,15 @@ To create an InfluxDB connection in the Chronograf UI:
|
|||
* **Connection URL**: Enter the hostname or IP address of the InfluxDB instance and the port. The field is prefilled with `http://localhost:8086`.
|
||||
* **Connection Name**: Enter the name for this connection.
|
||||
* **Username**: Enter the username that will be shared for this connection.
|
||||
*Required only if [authorization is enabled](/influxdb/latest/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.*
|
||||
*Required only if [authorization is enabled](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.*
|
||||
* **Password**: Enter the password.
|
||||
*Required only if [authorization is enabled](/influxdb/latest/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.*
|
||||
*Required only if [authorization is enabled](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.*
|
||||
* **Telegraf Database Name**: This field specifies the database that Chronograf will use for populating different parts of the application, including the Host List page. If none is provided, we will use `autogen`. You will still be able to query any database you have access to in the InfluxDB instance when building dashboards or exploring data.
|
||||
* **Default Retention Policy**: Enter the name of the default [retention policy](/influxdb/latest/concepts/glossary/#retention-policy-rp). If none is provided, it assumes `autogen`. If you've changed the default retention policy in your InfluxDB instance, you may want to change it here as well.
|
||||
* **Default Retention Policy**: Enter the name of the default [retention policy](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#retention-policy-rp). If none is provided, it assumes `autogen`. If you've changed the default retention policy in your InfluxDB instance, you may want to change it here as well.
|
||||
* **Make this the default connection**: When this option is selected, this InfluxDB connection will be used when Chronograf is launched.
|
||||
|
||||
4. Click **Add Connection**
|
||||
* If the connection is valid, the Dashboards window appears, allowing you to import dashboard templates you can use to display and analyze your data. For details, see [Creating dashboards](/chronograf/latest/guides/create-a-dashboard).
|
||||
* If the connection is valid, the Dashboards window appears, allowing you to import dashboard templates you can use to display and analyze your data. For details, see [Creating dashboards](/{{< latest "chronograf" >}}/guides/create-a-dashboard).
|
||||
* If the connection cannot be created, the following error message appears:
|
||||
"Unable to create source: Error contacting source."
|
||||
If this occurs, ensure all connection credentials are correct and that the InfluxDB instance is running and accessible.
|
||||
|
@ -109,11 +109,11 @@ Any string you want to use as the display name of the source.
|
|||
|
||||
#### `username`
|
||||
Username used to access the InfluxDB server or cluster.
|
||||
*Only required if [authorization is enabled](/influxdb/latest/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.*
|
||||
*Only required if [authorization is enabled](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.*
|
||||
|
||||
#### `password`
|
||||
Password used to access the InfluxDB server or cluster.
|
||||
*Only required if [authorization is enabled](/influxdb/latest/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.*
|
||||
*Only required if [authorization is enabled](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/) on the InfluxDB instance to which you're connecting.*
|
||||
|
||||
#### `url`
|
||||
URL of the InfluxDB server or cluster.
|
||||
|
@ -176,9 +176,9 @@ To create a Kapacitor connection using the Chronograf UI:
|
|||
* **Kapacitor URL**: Enter the hostname or IP address of the Kapacitor instance and the port. The field is prefilled with `http://localhost:9092`.
|
||||
* **Name**: Enter the name for this connection.
|
||||
* **Username**: Enter the username that will be shared for this connection.
|
||||
*Only required if [authorization is enabled](/kapacitor/latest/administration/security/#kapacitor-authentication-and-authorization) on the Kapacitor instance or cluster to which you're connecting.*
|
||||
*Only required if [authorization is enabled](/{{< latest "kapacitor" >}}/administration/security/#kapacitor-authentication-and-authorization) on the Kapacitor instance or cluster to which you're connecting.*
|
||||
* **Password**: Enter the password.
|
||||
*Only required if [authorization is enabled](/kapacitor/latest/administration/security/#kapacitor-authentication-and-authorization) on the Kapacitor instance or cluster to which you're connecting.*
|
||||
*Only required if [authorization is enabled](/{{< latest "kapacitor" >}}/administration/security/#kapacitor-authentication-and-authorization) on the Kapacitor instance or cluster to which you're connecting.*
|
||||
|
||||
4. Click **Continue**. If the connection is valid, the message "Kapacitor Created! Configuring endpoints is optional." appears. To configure alert endpoints, see [Configuring alert endpoints](/chronograf/v1.8/guides/configuring-alert-endpoints/).
|
||||
|
||||
|
|
|
@ -31,7 +31,7 @@ menu:
|
|||
|
||||
## Manage Chronograf users and roles
|
||||
|
||||
> ***Note:*** Support for organizations and user roles is available in Chronograf 1.4 or later. First, OAuth 2.0 authentication must be configured (if it is, you'll see the Chronograf Admin tab on the Admin menu). For more information, see [Managing security] (https://docs.influxdata.com/chronograf/v1.8/administration/managing-security/).
|
||||
> ***Note:*** Support for organizations and user roles is available in Chronograf 1.4 or later. First, OAuth 2.0 authentication must be configured (if it is, you'll see the Chronograf Admin tab on the Admin menu). For more information, see [Managing security] (/chronograf/v1.8/administration/managing-security/).
|
||||
|
||||
Chronograf includes four organization-bound user roles and one cross-organization SuperAdmin status. In an organization, admins (with the `admin` role) or users with SuperAdmin status can create, update, and assign roles to a user or remove a role assignment.
|
||||
|
||||
|
|
|
@ -13,7 +13,7 @@ menu:
|
|||
The **Chronograf Admin** provides InfluxDB user management for InfluxDB OSS and InfluxDB Enterprise users.
|
||||
|
||||
|
||||
> ***Note:*** For details on Chronograf user authentication and management, see [Managing security](/chronograf/latest/administration/managing-security/).
|
||||
> ***Note:*** For details on Chronograf user authentication and management, see [Managing security](/{{< latest "chronograf" >}}/administration/managing-security/).
|
||||
|
||||
**On this page:**
|
||||
|
||||
|
@ -58,7 +58,7 @@ Restart the InfluxDB service for your configuration changes to take effect:
|
|||
|
||||
### Step 3: Create an admin user.
|
||||
|
||||
Because authentication is enabled, you need to create an [admin user](/influxdb/latest/administration/authentication_and_authorization/#user-types-and-privileges) before you can do anything else in the database.
|
||||
Because authentication is enabled, you need to create an [admin user](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#user-types-and-privileges) before you can do anything else in the database.
|
||||
Run the `curl` command below to create an admin user, replacing:
|
||||
|
||||
* `localhost` with the IP or hostname of your InfluxDB OSS instance or one of your InfluxEnterprise data nodes
|
||||
|
@ -91,7 +91,7 @@ On the **Chronograf Admin** page:
|
|||
![InfluxDB OSS user management](/img/chronograf/1-6-admin-usermanagement-oss.png)
|
||||
|
||||
InfluxDB users are either admin users or non-admin users.
|
||||
See InfluxDB's [authentication and authorization](/influxdb/latest/administration/authentication_and_authorization/#user-types-and-privileges) documentation for more information about those user types.
|
||||
See InfluxDB's [authentication and authorization](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#user-types-and-privileges) documentation for more information about those user types.
|
||||
|
||||
> ***Note:*** Note that Chronograf currently does not support assigning InfluxDB database `READ`or `WRITE` access to non-admin users.
|
||||
>This is a known issue.
|
||||
|
@ -156,12 +156,12 @@ Assign permissions and roles to both admin and non-admin users.
|
|||
Permission to add or remove nodes from a cluster.
|
||||
|
||||
**Relevant `influxd-ctl` arguments**:
|
||||
[`add-data`](/enterprise_influxdb/latest/administration/cluster-commands/#add-data),
|
||||
[`add-meta`](/enterprise_influxdb/latest/administration/cluster-commands/#add-meta),
|
||||
[`join`](/enterprise_influxdb/latest/administration/cluster-commands/#join),
|
||||
[`remove-data`](/enterprise_influxdb/latest/administration/cluster-commands/#remove-data),
|
||||
[`remove-meta`](/enterprise_influxdb/latest/administration/cluster-commands/#remove-meta), and
|
||||
[`leave`](/enterprise_influxdb/latest/administration/cluster-commands/#leave)
|
||||
[`add-data`](/{{< latest "enterprise_influxdb" >}}/administration/cluster-commands/#add-data),
|
||||
[`add-meta`](/{{< latest "enterprise_influxdb" >}}/administration/cluster-commands/#add-meta),
|
||||
[`join`](/{{< latest "enterprise_influxdb" >}}/administration/cluster-commands/#join),
|
||||
[`remove-data`](/{{< latest "enterprise_influxdb" >}}/administration/cluster-commands/#remove-data),
|
||||
[`remove-meta`](/{{< latest "enterprise_influxdb" >}}/administration/cluster-commands/#remove-meta), and
|
||||
[`leave`](/{{< latest "enterprise_influxdb" >}}/administration/cluster-commands/#leave)
|
||||
|
||||
**Pages in Chronograf that require this permission**: NA
|
||||
|
||||
|
@ -169,18 +169,18 @@ Permission to add or remove nodes from a cluster.
|
|||
Permission to copy shards.
|
||||
|
||||
**Relevant `influxd-ctl` arguments**:
|
||||
[`copy-shard`](/enterprise_influxdb/latest/administration/cluster-commands/#copy-shard)
|
||||
[`copy-shard`](/{{< latest "enterprise_influxdb" >}}/administration/cluster-commands/#copy-shard)
|
||||
|
||||
**Pages in Chronograf that require this permission**: NA
|
||||
|
||||
#### CreateDatabase
|
||||
Permission to create databases, create [retention policies](/influxdb/latest/concepts/glossary/#retention-policy-rp), alter retention policies, and view retention policies.
|
||||
Permission to create databases, create [retention policies](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#retention-policy-rp), alter retention policies, and view retention policies.
|
||||
|
||||
**Relevant InfluxQL queries**:
|
||||
[`CREATE DATABASE`](/influxdb/latest/query_language/database_management/#create-database),
|
||||
[`CREATE RETENTION POLICY`](/influxdb/latest/query_language/database_management/#create-retention-policies-with-create-retention-policy),
|
||||
[`ALTER RETENTION POLICY`](/influxdb/latest/query_language/database_management/#modify-retention-policies-with-alter-retention-policy), and
|
||||
[`SHOW RETENTION POLICIES`](/influxdb/latest/query_language/schema_exploration/#show-retention-policies)
|
||||
[`CREATE DATABASE`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#create-database),
|
||||
[`CREATE RETENTION POLICY`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#create-retention-policies-with-create-retention-policy),
|
||||
[`ALTER RETENTION POLICY`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#modify-retention-policies-with-alter-retention-policy), and
|
||||
[`SHOW RETENTION POLICIES`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-retention-policies)
|
||||
|
||||
**Pages in Chronograf that require this permission**: Dashboards, Data Explorer, and Databases on the Admin page
|
||||
|
||||
|
@ -188,25 +188,25 @@ Permission to create databases, create [retention policies](/influxdb/latest/con
|
|||
Permission to manage users and roles; create users, drop users, grant admin status to users, grant permissions to users, revoke admin status from users, revoke permissions from users, change user passwords, view user permissions, and view users and their admin status.
|
||||
|
||||
**Relevant InfluxQL queries**:
|
||||
[`CREATE USER`](/influxdb/latest/administration/authentication_and_authorization/#user-management-commands),
|
||||
[`DROP USER`](/influxdb/latest/administration/authentication_and_authorization/#general-admin-and-non-admin-user-management),
|
||||
[`GRANT ALL PRIVILEGES`](/influxdb/latest/administration/authentication_and_authorization/#user-management-commands),
|
||||
[`GRANT [READ,WRITE,ALL]`](/influxdb/latest/administration/authentication_and_authorization/#non-admin-user-management),
|
||||
[`REVOKE ALL PRIVILEGES`](/influxdb/latest/administration/authentication_and_authorization/#user-management-commands),
|
||||
[`REVOKE [READ,WRITE,ALL]`](/influxdb/latest/administration/authentication_and_authorization/#non-admin-user-management),
|
||||
[`SET PASSWORD`](/influxdb/latest/administration/authentication_and_authorization/#general-admin-and-non-admin-user-management),
|
||||
[`SHOW GRANTS`](/influxdb/latest/administration/authentication_and_authorization/#non-admin-user-management), and
|
||||
[`SHOW USERS`](/influxdb/latest/administration/authentication_and_authorization/#user-management-commands)
|
||||
[`CREATE USER`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#user-management-commands),
|
||||
[`DROP USER`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#general-admin-and-non-admin-user-management),
|
||||
[`GRANT ALL PRIVILEGES`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#user-management-commands),
|
||||
[`GRANT [READ,WRITE,ALL]`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#non-admin-user-management),
|
||||
[`REVOKE ALL PRIVILEGES`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#user-management-commands),
|
||||
[`REVOKE [READ,WRITE,ALL]`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#non-admin-user-management),
|
||||
[`SET PASSWORD`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#general-admin-and-non-admin-user-management),
|
||||
[`SHOW GRANTS`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#non-admin-user-management), and
|
||||
[`SHOW USERS`](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#user-management-commands)
|
||||
|
||||
**Pages in Chronograf that require this permission**: Data Explorer, Dashboards, Users and Roles on the Admin page
|
||||
|
||||
#### DropData
|
||||
Permission to drop data, in particular [series](/influxdb/latest/concepts/glossary/#series) and [measurements](/influxdb/latest/concepts/glossary/#measurement).
|
||||
Permission to drop data, in particular [series](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#series) and [measurements](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#measurement).
|
||||
|
||||
**Relevant InfluxQL queries**:
|
||||
[`DROP SERIES`](/influxdb/latest/query_language/database_management/#drop-series-from-the-index-with-drop-series),
|
||||
[`DELETE`](/influxdb/latest/query_language/database_management/#delete-series-with-delete), and
|
||||
[`DROP MEASUREMENT`](/influxdb/latest/query_language/database_management/#delete-measurements-with-drop-measurement)
|
||||
[`DROP SERIES`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#drop-series-from-the-index-with-drop-series),
|
||||
[`DELETE`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#delete-series-with-delete), and
|
||||
[`DROP MEASUREMENT`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#delete-measurements-with-drop-measurement)
|
||||
|
||||
**Pages in Chronograf that require this permission**: NA
|
||||
|
||||
|
@ -214,8 +214,8 @@ Permission to drop data, in particular [series](/influxdb/latest/concepts/glossa
|
|||
Permission to drop databases and retention policies.
|
||||
|
||||
**Relevant InfluxQL queries**:
|
||||
[`DROP DATABASE`](/influxdb/latest/query_language/database_management/#delete-a-database-with-drop-database) and
|
||||
[`DROP RETENTION POLICY`](/influxdb/latest/query_language/database_management/#delete-retention-policies-with-drop-retention-policy)
|
||||
[`DROP DATABASE`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#delete-a-database-with-drop-database) and
|
||||
[`DROP RETENTION POLICY`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#delete-retention-policies-with-drop-retention-policy)
|
||||
|
||||
**Pages in Chronograf that require this permission**: Data Explorer, Dashboards, Databases on the Admin page
|
||||
|
||||
|
@ -231,12 +231,12 @@ Permission to access the configuration-related API calls for InfluxKapacitor Ent
|
|||
**Pages in Chronograf that require this permission**: NA
|
||||
|
||||
#### ManageContinuousQuery
|
||||
Permission to create, drop, and view [continuous queries](/influxdb/latest/concepts/glossary/#continuous-query-cq).
|
||||
Permission to create, drop, and view [continuous queries](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#continuous-query-cq).
|
||||
|
||||
**Relevant InfluxQL queries**:
|
||||
[`CreateContinuousQueryStatement`](/influxdb/latest/query_language/continuous_queries/),
|
||||
[`DropContinuousQueryStatement`](/influxdb/latest/query_language/continuous_queries/#deleting-continuous-queries), and
|
||||
[`ShowContinuousQueriesStatement`](/influxdb/latest/query_language/continuous_queries/#listing-continuous-queries)
|
||||
[`CreateContinuousQueryStatement`](/{{< latest "influxdb" "v1" >}}/query_language/continuous_queries/),
|
||||
[`DropContinuousQueryStatement`](/{{< latest "influxdb" "v1" >}}/query_language/continuous_queries/#deleting-continuous-queries), and
|
||||
[`ShowContinuousQueriesStatement`](/{{< latest "influxdb" "v1" >}}/query_language/continuous_queries/#listing-continuous-queries)
|
||||
|
||||
**Pages in Chronograf that require this permission**: Data Explorer, Dashboards
|
||||
|
||||
|
@ -244,28 +244,28 @@ Permission to create, drop, and view [continuous queries](/influxdb/latest/conce
|
|||
Permission to view and kill queries.
|
||||
|
||||
**Relevant InfluxQL queries**:
|
||||
[`SHOW QUERIES`](/influxdb/latest/troubleshooting/query_management/#list-currently-running-queries-with-show-queries) and
|
||||
[`KILL QUERY`](/influxdb/latest/troubleshooting/query_management/#stop-currently-running-queries-with-kill-query)
|
||||
[`SHOW QUERIES`](/{{< latest "influxdb" "v1" >}}/troubleshooting/query_management/#list-currently-running-queries-with-show-queries) and
|
||||
[`KILL QUERY`](/{{< latest "influxdb" "v1" >}}/troubleshooting/query_management/#stop-currently-running-queries-with-kill-query)
|
||||
|
||||
**Pages in Chronograf that require this permission**: Queries on the Admin page
|
||||
|
||||
#### ManageShard
|
||||
Permission to copy, delete, and view [shards](/influxdb/latest/concepts/glossary/#shard).
|
||||
Permission to copy, delete, and view [shards](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#shard).
|
||||
|
||||
**Relevant InfluxQL queries**:
|
||||
[`DropShardStatement`](/influxdb/latest/query_language/database_management/#delete-a-shard-with-drop-shard),
|
||||
[`ShowShardGroupsStatement`](/influxdb/latest/query_language/spec/#show-shard-groups), and
|
||||
[`ShowShardsStatement`](/influxdb/latest/query_language/spec/#show-shards)
|
||||
[`DropShardStatement`](/{{< latest "influxdb" "v1" >}}/query_language/database_management/#delete-a-shard-with-drop-shard),
|
||||
[`ShowShardGroupsStatement`](/{{< latest "influxdb" "v1" >}}/query_language/spec/#show-shard-groups), and
|
||||
[`ShowShardsStatement`](/{{< latest "influxdb" "v1" >}}/query_language/spec/#show-shards)
|
||||
|
||||
**Pages in Chronograf that require this permission**: NA
|
||||
|
||||
#### ManageSubscription
|
||||
Permission to create, drop, and view [subscriptions](/influxdb/latest/concepts/glossary/#subscription).
|
||||
Permission to create, drop, and view [subscriptions](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#subscription).
|
||||
|
||||
**Relevant InfluxQL queries**:
|
||||
[`CREATE SUBSCRIPTION`](/influxdb/latest/query_language/spec/#create-subscription),
|
||||
[`DROP SUBSCRIPTION`](/influxdb/latest/query_language/spec/#drop-subscription), and
|
||||
[`SHOW SUBSCRIPTIONS`](/influxdb/latest/query_language/spec/#show-subscriptions)
|
||||
[`CREATE SUBSCRIPTION`](/{{< latest "influxdb" "v1" >}}/query_language/spec/#create-subscription),
|
||||
[`DROP SUBSCRIPTION`](/{{< latest "influxdb" "v1" >}}/query_language/spec/#drop-subscription), and
|
||||
[`SHOW SUBSCRIPTIONS`](/{{< latest "influxdb" "v1" >}}/query_language/spec/#show-subscriptions)
|
||||
|
||||
**Pages in Chronograf that require this permission**: Alerting
|
||||
|
||||
|
@ -282,12 +282,12 @@ Permission to view cluster statistics and diagnostics.
|
|||
Permission to read data.
|
||||
|
||||
**Relevant InfluxQL queries**:
|
||||
[`SHOW FIELD KEYS`](/influxdb/latest/query_language/schema_exploration/#show-field-keys),
|
||||
[`SHOW MEASUREMENTS`](/influxdb/latest/query_language/schema_exploration/#show-measurements),
|
||||
[`SHOW SERIES`](/influxdb/latest/query_language/schema_exploration/#show-series),
|
||||
[`SHOW TAG KEYS`](/influxdb/latest/query_language/schema_exploration/#show-tag-keys),
|
||||
[`SHOW TAG VALUES`](/influxdb/latest/query_language/schema_exploration/#show-tag-values), and
|
||||
[`SHOW RETENTION POLICIES`](/influxdb/latest/query_language/schema_exploration/#show-retention-policies)
|
||||
[`SHOW FIELD KEYS`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-field-keys),
|
||||
[`SHOW MEASUREMENTS`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-measurements),
|
||||
[`SHOW SERIES`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-series),
|
||||
[`SHOW TAG KEYS`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-tag-keys),
|
||||
[`SHOW TAG VALUES`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-tag-values), and
|
||||
[`SHOW RETENTION POLICIES`](/{{< latest "influxdb" "v1" >}}/query_language/schema_exploration/#show-retention-policies)
|
||||
|
||||
**Pages in Chronograf that require this permission**: Admin, Alerting, Dashboards, Data Explorer, Host List
|
||||
|
||||
|
|
|
@ -24,7 +24,7 @@ menu:
|
|||
First, OAuth 2.0 authentication must be configured (if it is, you'll see the Chronograf Admin tab on the Admin menu).
|
||||
For more information, see [managing security](/chronograf/v1.8/administration/managing-security/).
|
||||
|
||||
For information about the new user roles and SuperAdmin status, see [Managing Chronograf users](https://docs.influxdata.com/chronograf/v1.8/administration/managing-chronograf-users/).
|
||||
For information about the new user roles and SuperAdmin status, see [Managing Chronograf users](/chronograf/v1.8/administration/managing-chronograf-users/).
|
||||
|
||||
A Chronograf organization is a collection of Chronograf users who share common Chronograf-owned resources, including dashboards, InfluxDB connections, and Kapacitor connections. Organizations can be used to represent companies, functional units, projects, or teams. Chronograf users can be members of multiple organizations.
|
||||
|
||||
|
|
|
@ -20,8 +20,8 @@ To enhance security, configure Chronograf to authenticate and authorize with [OA
|
|||
## Configure OAuth 2.0
|
||||
|
||||
> After configuring OAuth 2.0, the Chronograf Admin tab becomes visible.
|
||||
> You can then set up [multiple organizations](https://docs.influxdata.com/chronograf/latest/administration/managing-organizations/)
|
||||
> and [users](https://docs.influxdata.com/chronograf/latest/administration/managing-influxdb-users/).
|
||||
> You can then set up [multiple organizations](/{{< latest "chronograf" >}}/administration/managing-organizations/)
|
||||
> and [users](/{{< latest "chronograf" >}}/administration/managing-influxdb-users/).
|
||||
|
||||
Configure Chronograf to use an OAuth 2.0 provider and JWT (JSON Web Token) to authenticate users and enable role-based access controls.
|
||||
|
||||
|
|
|
@ -7,7 +7,7 @@ menu:
|
|||
weight: 50
|
||||
parent: Administration
|
||||
---
|
||||
Chronograf lets you import a variety of prebuilt dashboards that visualize metrics collect by specific [Telegraf input plugins](/telegraf/latest/plugins/plugin-list). The following Telegraf-related dashboards templates are available.
|
||||
Chronograf lets you import a variety of prebuilt dashboards that visualize metrics collect by specific [Telegraf input plugins](/{{< latest "telegraf" >}}/plugins/plugin-list). The following Telegraf-related dashboards templates are available.
|
||||
|
||||
For details on how to import dashboards while adding a connection in Chronograf, see [Creating connections](/chronograf/v1.8/administration/creating-connections/#manage-influxdb-connections-using-the-chronograf-ui).
|
||||
|
||||
|
@ -30,12 +30,12 @@ The Docker dashboard displays the following information:
|
|||
|
||||
### Plugins
|
||||
|
||||
- [`docker` plugin](/telegraf/latest/plugins/plugin-list/#docker)
|
||||
- [`disk` plugin](/telegraf/latest/plugins/plugin-list/#disk)
|
||||
- [`mem` plugin](/telegraf/latest/plugins/plugin-list/#mem)
|
||||
- [`diskio` plugin](/telegraf/latest/plugins/plugin-list/#diskio)
|
||||
- [`system` plugin](/telegraf/latest/plugins/plugin-list/#system)
|
||||
- [`cpu` plugin](/telegraf/latest/plugins/plugin-list/#cpu)
|
||||
- [`docker` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#docker)
|
||||
- [`disk` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#disk)
|
||||
- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#mem)
|
||||
- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#diskio)
|
||||
- [`system` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#system)
|
||||
- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#cpu)
|
||||
|
||||
## Kubernetes Node
|
||||
The Kubernetes Node dashboard displays the following information:
|
||||
|
@ -53,7 +53,7 @@ The Kubernetes Node dashboard displays the following information:
|
|||
- K8s - Kubelet Memory Bytes
|
||||
|
||||
### Plugins
|
||||
- [kubernetes](/telegraf/latest/plugins/plugin-list/#kubernetes)
|
||||
- [kubernetes](/{{< latest "telegraf" >}}/plugins/plugin-list/#kubernetes)
|
||||
|
||||
## Kubernetes Overview
|
||||
The Kubernetes Node dashboard displays the following information:
|
||||
|
@ -72,7 +72,7 @@ The Kubernetes Node dashboard displays the following information:
|
|||
|
||||
### Plugins
|
||||
|
||||
- [kubernetes](/telegraf/latest/plugins/plugin-list/#kubernetes)
|
||||
- [kubernetes](/{{< latest "telegraf" >}}/plugins/plugin-list/#kubernetes)
|
||||
|
||||
## Kubernetes Pod
|
||||
The Kubernetes Pod dashboard displays the following information:
|
||||
|
@ -87,7 +87,7 @@ The Kubernetes Pod dashboard displays the following information:
|
|||
- K8s - Pod TX Bytes/Second
|
||||
|
||||
### Plugins
|
||||
- [kubernetes](/telegraf/latest/plugins/plugin-list/#kubernetes)
|
||||
- [kubernetes](/{{< latest "telegraf" >}}/plugins/plugin-list/#kubernetes)
|
||||
|
||||
## Riak
|
||||
The Riak dashboard displays the following information:
|
||||
|
@ -101,7 +101,7 @@ The Riak dashboard displays the following information:
|
|||
- Riak - Read Repairs/Minute
|
||||
|
||||
### Plugins
|
||||
- [`riak` plugin](/telegraf/latest/plugins/plugin-list/#riak)
|
||||
- [`riak` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#riak)
|
||||
|
||||
## Consul
|
||||
The Consul dashboard displays the following information:
|
||||
|
@ -110,7 +110,7 @@ The Consul dashboard displays the following information:
|
|||
- Consul - Number of Warning Health Checks
|
||||
|
||||
### Plugins
|
||||
- [`consul` plugin](/telegraf/latest/plugins/plugin-list/#consul)
|
||||
- [`consul` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#consul)
|
||||
|
||||
## Consul Telemetry
|
||||
The Consul Telemetry dashboard displays the following information:
|
||||
|
@ -125,7 +125,7 @@ The Consul Telemetry dashboard displays the following information:
|
|||
- Consul - Number of Serf Events
|
||||
|
||||
### Plugins
|
||||
[`consul` plugin](/telegraf/latest/plugins/plugin-list/#consul)
|
||||
[`consul` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#consul)
|
||||
|
||||
|
||||
## Mesos
|
||||
|
@ -140,7 +140,7 @@ The Mesos dashboard displays the following information:
|
|||
- Mesos Master Uptime
|
||||
|
||||
### Plugins
|
||||
- [`mesos` plugin](/telegraf/latest/plugins/plugin-list/#mesos)
|
||||
- [`mesos` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#mesos)
|
||||
|
||||
## RabbitMQ
|
||||
The RabbitMQ dashboard displays the following information:
|
||||
|
@ -151,7 +151,7 @@ The RabbitMQ dashboard displays the following information:
|
|||
|
||||
### Plugins
|
||||
|
||||
- [`rabbitmq` plugin](/telegraf/latest/plugins/plugin-list/#rabbitmq)
|
||||
- [`rabbitmq` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#rabbitmq)
|
||||
|
||||
## System
|
||||
|
||||
|
@ -170,14 +170,14 @@ The System dashboard displays the following information:
|
|||
|
||||
### Plugins
|
||||
|
||||
- [`system` plugin](/telegraf/latest/plugins/plugin-list/#system)
|
||||
- [`mem` plugin](/telegraf/latest/plugins/plugin-list/#mem)
|
||||
- [`cpu` plugin](/telegraf/latest/plugins/plugin-list/#cpu)
|
||||
- [`disk` plugin](/telegraf/latest/plugins/plugin-list/#disk)
|
||||
- [`diskio` plugin](/telegraf/latest/plugins/plugin-list/#diskio)
|
||||
- [`net` plugin](/telegraf/latest/plugins/plugin-list/#net)
|
||||
- [`processes` plugin](/telegraf/latest/plugins/plugin-list/#processes)
|
||||
- [`swap` plugin](/telegraf/latest/plugins/plugin-list/#swap)
|
||||
- [`system` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#system)
|
||||
- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#mem)
|
||||
- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#cpu)
|
||||
- [`disk` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#disk)
|
||||
- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#diskio)
|
||||
- [`net` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#net)
|
||||
- [`processes` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#processes)
|
||||
- [`swap` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#swap)
|
||||
|
||||
|
||||
|
||||
|
@ -198,7 +198,7 @@ The VMware vSphere Overview dashboard gives an overview of your VMware vSphere C
|
|||
- VM CPU % Ready for :clustername:
|
||||
|
||||
### Plugins
|
||||
- [`vsphere` plugin](/telegraf/latest/plugins/plugin-list/#vmware-vsphere)
|
||||
- [`vsphere` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#vmware-vsphere)
|
||||
|
||||
## Apache
|
||||
The Apache dashboard displays the following information:
|
||||
|
@ -221,12 +221,12 @@ The Apache dashboard displays the following information:
|
|||
|
||||
### Plugins
|
||||
|
||||
- [`apache` plugin](/telegraf/latest/plugins/plugin-list/#apache)
|
||||
- [`system` plugin](/telegraf/latest/plugins/plugin-list/#system)
|
||||
- [`mem` plugin](/telegraf/latest/plugins/plugin-list/#mem)
|
||||
- [`diskio` plugin](/telegraf/latest/plugins/plugin-list/#diskio)
|
||||
- [`net` plugin](/telegraf/latest/plugins/plugin-list/#net)
|
||||
- [`logparser` plugin](/telegraf/latest/plugins/plugin-list/#logparser)
|
||||
- [`apache` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#apache)
|
||||
- [`system` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#system)
|
||||
- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#mem)
|
||||
- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#diskio)
|
||||
- [`net` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#net)
|
||||
- [`logparser` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#logparser)
|
||||
|
||||
## ElasticSearch
|
||||
The ElasticSearch dashboard displays the following information:
|
||||
|
@ -243,7 +243,7 @@ The ElasticSearch dashboard displays the following information:
|
|||
- ElasticSearch - JVM Heap Usage
|
||||
|
||||
### Plugins
|
||||
- [`elasticsearch` plugin](/telegraf/latest/plugins/plugin-list/#elasticsearch)
|
||||
- [`elasticsearch` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#elasticsearch)
|
||||
|
||||
|
||||
## InfluxDB
|
||||
|
@ -272,12 +272,12 @@ The InfluxDB dashboard displays the following information:
|
|||
|
||||
### Plugins
|
||||
|
||||
- [`influxdb` plugin](/telegraf/latest/plugins/plugin-list/#influxdb)
|
||||
- [`cpu` plugin](/telegraf/latest/plugins/plugin-list/#cpu)
|
||||
- [`system` plugin](/telegraf/latest/plugins/plugin-list/#system)
|
||||
- [`mem` plugin](/telegraf/latest/plugins/plugin-list/#mem)
|
||||
- [`diskio` plugin](/telegraf/latest/plugins/plugin-list/#diskio)
|
||||
- [`net` plugin](/telegraf/latest/plugins/plugin-list/#net)
|
||||
- [`influxdb` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#influxdb)
|
||||
- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#cpu)
|
||||
- [`system` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#system)
|
||||
- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#mem)
|
||||
- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#diskio)
|
||||
- [`net` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#net)
|
||||
|
||||
|
||||
|
||||
|
@ -299,7 +299,7 @@ The Memcached dashboard displays the following information:
|
|||
- Memcached - Evictions/10 Seconds
|
||||
|
||||
### Plugins
|
||||
- [`memcached` plugin](/telegraf/latest/plugins/plugin-list/#memcached)
|
||||
- [`memcached` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#memcached)
|
||||
|
||||
|
||||
## NSQ
|
||||
|
@ -315,7 +315,7 @@ The NSQ dashboard displays the following information:
|
|||
- NSQ - Topic Egress
|
||||
|
||||
### Plugins
|
||||
- [`nsq` plugin](/telegraf/latest/plugins/plugin-list/#nsq)
|
||||
- [`nsq` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#nsq)
|
||||
|
||||
## PostgreSQL
|
||||
The PostgreSQL dashboard displays the following information:
|
||||
|
@ -340,11 +340,11 @@ The PostgreSQL dashboard displays the following information:
|
|||
|
||||
### Plugins
|
||||
|
||||
- [`postgresql` plugin](/telegraf/latest/plugins/plugin-list/#postgresql)
|
||||
- [`system` plugin](/telegraf/latest/plugins/plugin-list/#system)
|
||||
- [`mem` plugin](/telegraf/latest/plugins/plugin-list/#mem)
|
||||
- [`cpu` plugin](/telegraf/latest/plugins/plugin-list/#cpu)
|
||||
- [`diskio` plugin](/telegraf/latest/plugins/plugin-list/#diskio)
|
||||
- [`postgresql` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#postgresql)
|
||||
- [`system` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#system)
|
||||
- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#mem)
|
||||
- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#cpu)
|
||||
- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#diskio)
|
||||
|
||||
|
||||
## HAProxy
|
||||
|
@ -367,7 +367,7 @@ The HAProxy dashboard displays the following information:
|
|||
- HAProxy - Backend Error Responses/Second
|
||||
|
||||
### Plugins
|
||||
- [`haproxy` plugin](/telegraf/latest/plugins/plugin-list/#haproxy)
|
||||
- [`haproxy` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#haproxy)
|
||||
|
||||
|
||||
## NGINX
|
||||
|
@ -379,7 +379,7 @@ The NGINX dashboard displays the following information:
|
|||
- NGINX - Active Client State
|
||||
|
||||
### Plugins
|
||||
- [`nginx` plugin](/telegraf/latest/plugins/plugin-list/#nginx)
|
||||
- [`nginx` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#nginx)
|
||||
|
||||
## Redis
|
||||
The Redis dashboard displays the following information:
|
||||
|
@ -390,7 +390,7 @@ The Redis dashboard displays the following information:
|
|||
- Redis - Memory
|
||||
|
||||
### Plugins
|
||||
- [`redis` plugin](/telegraf/latest/plugins/plugin-list/#redis)
|
||||
- [`redis` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#redis)
|
||||
|
||||
|
||||
## VMware vSphere VMs
|
||||
|
@ -406,7 +406,7 @@ The VMWare vSphere VMs dashboard gives an overview of your VMware vSphere virtua
|
|||
- Total Disk Latency for :vmname:
|
||||
|
||||
### Plugins
|
||||
- [`vsphere` plugin](/telegraf/latest/plugins/plugin-list/#vsphere)
|
||||
- [`vsphere` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#vsphere)
|
||||
|
||||
## VMware vSphere Hosts
|
||||
|
||||
|
@ -422,7 +422,7 @@ The VMWare vSphere Hosts dashboard displays the following information:
|
|||
- Total Disk Latency for :esxhostname:
|
||||
|
||||
### Plugins
|
||||
- [`vsphere` plugin](/telegraf/latest/plugins/plugin-list/#vsphere)
|
||||
- [`vsphere` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#vsphere)
|
||||
|
||||
## PHPfpm
|
||||
The PHPfpm dashboard displays the following information:
|
||||
|
@ -433,7 +433,7 @@ The PHPfpm dashboard displays the following information:
|
|||
- PHPfpm - Max Children Reached
|
||||
|
||||
### Plugins
|
||||
- [`phpfpm` plugin](/telegraf/latest/plugins/plugin-list/#nginx)
|
||||
- [`phpfpm` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#nginx)
|
||||
|
||||
## Win System
|
||||
The Win System dashboard displays the following information:
|
||||
|
@ -445,7 +445,7 @@ The Win System dashboard displays the following information:
|
|||
- System - Load
|
||||
|
||||
### Plugins
|
||||
- [`win_services` plugin](/telegraf/latest/plugins/plugin-list/#windows-services)
|
||||
- [`win_services` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#windows-services)
|
||||
|
||||
|
||||
## MySQL
|
||||
|
@ -472,9 +472,9 @@ The MySQL dashboard displays the following information:
|
|||
- InnoDB Data
|
||||
|
||||
### Plugins
|
||||
- [`mySQL` plugin](/telegraf/latest/plugins/plugin-list/#mysql)
|
||||
- [`system` plugin](/telegraf/latest/plugins/plugin-list/#system)
|
||||
- [`mem` plugin](/telegraf/latest/plugins/plugin-list/#mem)
|
||||
- [`mySQL` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#mysql)
|
||||
- [`system` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#system)
|
||||
- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#mem)
|
||||
|
||||
## Ping
|
||||
The Ping dashboard displays the following information:
|
||||
|
@ -483,4 +483,4 @@ The Ping dashboard displays the following information:
|
|||
- Ping - Response Times (ms)
|
||||
|
||||
### Plugins
|
||||
- [`ping` plugin](/telegraf/latest/plugins/plugin-list/#ping)
|
||||
- [`ping` plugin](/{{< latest "telegraf" >}}/plugins/plugin-list/#ping)
|
||||
|
|
|
@ -13,16 +13,16 @@ menu:
|
|||
* [TICKscript management](#tickscript-management)
|
||||
|
||||
|
||||
Chronograf provides a user interface for [Kapacitor](/kapacitor/latest/), InfluxData's processing framework for creating alerts, running ETL jobs, and detecting anomalies in your data.
|
||||
Chronograf provides a user interface for [Kapacitor](/{{< latest "kapacitor" >}}/), InfluxData's processing framework for creating alerts, running ETL jobs, and detecting anomalies in your data.
|
||||
This guide offers insights into how Kapacitor interacts with Chronograf and introduces advanced Kapacitor usage within Chronograf.
|
||||
|
||||
|
||||
## Alert history management
|
||||
|
||||
Chronograf stores the information on the Alert History page as time series data in InfluxDB.
|
||||
It stores it in the `chronograf` database and in the `alerts` [measurement](/influxdb/latest/concepts/glossary/#measurement).
|
||||
By default, this data is subject to an infinite [retention policy](/influxdb/latest/concepts/glossary/#retention-policy-rp) (RP), that is, InfluxDB stores them forever.
|
||||
Users who expect to have a large number of alerts and users who do not want to store their alert history forever may want to shorten the [duration](/influxdb/latest/concepts/glossary/#duration) of that retention policy.
|
||||
It stores it in the `chronograf` database and in the `alerts` [measurement](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#measurement).
|
||||
By default, this data is subject to an infinite [retention policy](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#retention-policy-rp) (RP), that is, InfluxDB stores them forever.
|
||||
Users who expect to have a large number of alerts and users who do not want to store their alert history forever may want to shorten the [duration](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#duration) of that retention policy.
|
||||
|
||||
### Modifying the retention policy in Chronograf
|
||||
|
||||
|
@ -36,7 +36,7 @@ In the Databases tab:
|
|||
#### Step 2: Enter a different duration
|
||||
|
||||
The minimum allowable duration is one hour (`1h`) and the maximum is infinite (`INF`).
|
||||
See the InfluxDB documentation for the list of [acceptable duration units](/influxdb/latest/query_language/spec/#duration-units).
|
||||
See the InfluxDB documentation for the list of [acceptable duration units](/{{< latest "influxdb" "v1" >}}/query_language/spec/#duration-units).
|
||||
|
||||
#### Step 3: Click the green check mark to save your changes
|
||||
|
||||
|
@ -56,7 +56,7 @@ The fourth alert, which occurred on the same day at 16:58:50, is outside the pre
|
|||
|
||||
Chronograf creates Kapacitor tasks using the information that you provide on the Rule Configuration page.
|
||||
It uses that information to communicate with Kapacitor and populate Chronograf alert pages.
|
||||
Pre-existing tasks, or [TICKscripts](/kapacitor/latest/tick/), that you created and enabled on your Kapacitor instance without using Chronograf, have limited functionality in the user interface.
|
||||
Pre-existing tasks, or [TICKscripts](/{{< latest "kapacitor" >}}/tick/), that you created and enabled on your Kapacitor instance without using Chronograf, have limited functionality in the user interface.
|
||||
|
||||
In Chronograf, you can:
|
||||
|
||||
|
|
|
@ -11,7 +11,7 @@ Chronograf gives you the ability to view, search, filter, visualize, and analyze
|
|||
This helps to recognize and diagnose patterns, then quickly dive into logged events that lead up to events.
|
||||
|
||||
## Logging setup
|
||||
Logs data is a first class citizen in InfluxDB and is populated using available log-related [Telegraf input plugins](/telegraf/latest/plugins/inputs/):
|
||||
Logs data is a first class citizen in InfluxDB and is populated using available log-related [Telegraf input plugins](/{{< latest "telegraf" >}}/plugins/inputs/):
|
||||
|
||||
[syslog](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/syslog)
|
||||
|
||||
|
|
|
@ -17,7 +17,7 @@ This guide offers step-by-step instructions for configuring Chronograf alert end
|
|||
|
||||
## Kapacitor event handlers supported in Chronograf
|
||||
|
||||
Chronograf integrates with [Kapacitor](/kapacitor/latest/), InfluxData's data processing platform, to send alert messages to event handlers.
|
||||
Chronograf integrates with [Kapacitor](/{{< latest "kapacitor" >}}/), InfluxData's data processing platform, to send alert messages to event handlers.
|
||||
Chronograf supports the following event handlers:
|
||||
|
||||
* Alerta
|
||||
|
@ -39,7 +39,7 @@ Chronograf supports the following event handlers:
|
|||
* TCP
|
||||
* VictorOps
|
||||
|
||||
To configure a Kapacitor event handler in Chronograf, [install Kapacitor](/kapacitor/latest/introduction/installation/) and [connect it to Chronograf](/kapacitor/latest/working/kapa-and-chrono/#add-a-kapacitor-instance).
|
||||
To configure a Kapacitor event handler in Chronograf, [install Kapacitor](/{{< latest "kapacitor" >}}/introduction/installation/) and [connect it to Chronograf](/{{< latest "kapacitor" >}}/working/kapa-and-chrono/#add-a-kapacitor-instance).
|
||||
The **Configure Kapacitor** page includes the event handler configuration options.
|
||||
|
||||
|
||||
|
@ -47,10 +47,10 @@ The **Configure Kapacitor** page includes the event handler configuration option
|
|||
|
||||
Alert endpoint configurations appear on the Chronograf Configure Kapacitor page.
|
||||
You must have a connected Kapacitor instance to access the configurations.
|
||||
For more information, see [Kapacitor installation instructions](/kapacitor/latest/introduction/installation/) and how to [connect a Kapacitor instance](/kapacitor/latest/working/kapa-and-chrono/#add-a-kapacitor-instance) to Chronograf.
|
||||
For more information, see [Kapacitor installation instructions](/{{< latest "kapacitor" >}}/introduction/installation/) and how to [connect a Kapacitor instance](/{{< latest "kapacitor" >}}/working/kapa-and-chrono/#add-a-kapacitor-instance) to Chronograf.
|
||||
|
||||
Note that the configuration options in the **Configure alert endpoints** section are not all-inclusive.
|
||||
Some event handlers allow users to customize event handler configurations per [alert rule](/chronograf/latest/guides/create-a-kapacitor-alert/).
|
||||
Some event handlers allow users to customize event handler configurations per [alert rule](/{{< latest "chronograf" >}}/guides/create-a-kapacitor-alert/).
|
||||
For example, Chronograf's Slack integration allows users to specify a default channel in the **Configure alert endpoints** section and a different channel for individual alert rules.
|
||||
|
||||
### HipChat
|
||||
|
@ -87,7 +87,7 @@ The following steps describe how to create the API access token:
|
|||
|
||||
Your token appears in the table just above the **Create new token** section:
|
||||
|
||||
![HipChat token](/img/chronograf/latest/g-eventhandlers-hipchattoken.png)
|
||||
![HipChat token](/img/{{< latest "chronograf" >}}/g-eventhandlers-hipchattoken.png)
|
||||
|
||||
|
||||
### Kafka
|
||||
|
@ -112,7 +112,7 @@ Your token appears in the table just above the **Create new token** section:
|
|||
3. Click **Save Changes** to save the configuration settings.
|
||||
4. Click **Send Test Alert** to verify the configuration.
|
||||
|
||||
See [Kafka event handler (Kapacitor)](/kapacitor/latest/event_handlers/kafka/) in the Kapacitor documentation for details about enabling OpsGenie services using TICKscripts.
|
||||
See [Kafka event handler (Kapacitor)](/{{< latest "kapacitor" >}}/event_handlers/kafka/) in the Kapacitor documentation for details about enabling OpsGenie services using TICKscripts.
|
||||
|
||||
|
||||
### OpsGenie
|
||||
|
@ -139,9 +139,9 @@ Send an incident alert to OpsGenie teams and recipients using the Chronograf ale
|
|||
|
||||
See [Alert API](https://docs.opsgenie.com/docs/alert-api) in the OpsGenie documentation for details on the OpsGenie Alert API
|
||||
|
||||
See [OpsGenie V2 event handler](/kapacitor/latest/event_handlers/opsgenie/v2/) in the Kapacitor documentation for details about the OpsGenie V2 event handler.
|
||||
See [OpsGenie V2 event handler](/{{< latest "kapacitor" >}}/event_handlers/opsgenie/v2/) in the Kapacitor documentation for details about the OpsGenie V2 event handler.
|
||||
|
||||
See the [AlertNode (Kapacitor TICKscript node) - OpsGenie v2](/kapacitor/latest/nodes/alert_node/#opsgenie-v2) in the Kapacitor documentation for details about enabling OpsGenie services using TICKscripts.
|
||||
See the [AlertNode (Kapacitor TICKscript node) - OpsGenie v2](/{{< latest "kapacitor" >}}/nodes/alert_node/#opsgenie-v2) in the Kapacitor documentation for details about enabling OpsGenie services using TICKscripts.
|
||||
|
||||
### PagerDuty
|
||||
|
||||
|
@ -165,7 +165,7 @@ Send an alerts about recognized events to PagerDuty using the Chronograf PagerDu
|
|||
|
||||
See the [PagerDuty Events API V2 Overview](https://v2.developer.pagerduty.com/docs/events-api-v2) for details on the PagerDuty Events API and recognized event types (`trigger`, `acknowledge`, and `resolve`).
|
||||
|
||||
See [AlertNode (Kapacitor TICKscript node) - PagerDuty v2](/kapacitor/latest/nodes/alert_node/#pagerduty-v2) in the Kapacitor documentation for details about enabling a new "Generic API" service using TICKscripts.
|
||||
See [AlertNode (Kapacitor TICKscript node) - PagerDuty v2](/{{< latest "kapacitor" >}}/nodes/alert_node/#pagerduty-v2) in the Kapacitor documentation for details about enabling a new "Generic API" service using TICKscripts.
|
||||
|
||||
### Pushover
|
||||
|
||||
|
|
|
@ -10,7 +10,7 @@ menu:
|
|||
|
||||
Chronograf offers a complete dashboard solution for visualizing your data and monitoring your infrastructure:
|
||||
|
||||
* View [pre-created dashboards](/chronograf/latest/guides/using-precreated-dashboards) from the Host List page. Dashboards are available depending on which Telegraf input plugins you have enabled. These pre-created dashboards cannot be cloned or edited.
|
||||
* View [pre-created dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards) from the Host List page. Dashboards are available depending on which Telegraf input plugins you have enabled. These pre-created dashboards cannot be cloned or edited.
|
||||
* Create custom dashboards from scratch by building queries in the Data Explorer, as described [below](#build-a-dashboard).
|
||||
* Import dashboard templates when you add or update a connection in Chronograf. See [Dashboard templates](#dashboard-templates) for details.
|
||||
|
||||
|
@ -22,7 +22,7 @@ By the end of this guide, you'll be aware of the tools available to you for crea
|
|||
|
||||
To perform the tasks in this guide, you must have a working Chronograf instance that is connected to an InfluxDB source.
|
||||
Data is accessed using the Telegraf [system ](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/system) input plugins.
|
||||
For more information, see [Configuring Chronograf](/chronograf/latest/administration/configuration).
|
||||
For more information, see [Configuring Chronograf](/{{< latest "chronograf" >}}/administration/configuration).
|
||||
|
||||
## Build a dashboard
|
||||
|
||||
|
@ -42,13 +42,13 @@ to open the cell editor mode.
|
|||
|
||||
### Step 3: Create your query
|
||||
|
||||
Click the **Add a Query** button to create an [InfluxQL](/influxdb/latest/query_language/) query.
|
||||
Click the **Add a Query** button to create an [InfluxQL](/{{< latest "influxdb" "v1" >}}/query_language/) query.
|
||||
In query editor mode, use the builder to select from your existing data and allow Chronograf to format the query for you.
|
||||
Alternatively, manually enter and edit a query.
|
||||
Chronograf allows you to move seamlessly between using the builder and manually editing the query; when possible, the interface automatically populates the builder with the information from your raw query.
|
||||
|
||||
For our example, the query builder is used to generate a query that shows the average idle CPU usage grouped by host (in this case, there are three hosts).
|
||||
By default, Chronograf applies the [`MEAN()` function](/influxdb/latest/query_language/functions/#mean) to the data, groups averages into auto-generated time intervals (`:interval:`), and shows data for the past hour (`:dashboardTime:`).
|
||||
By default, Chronograf applies the [`MEAN()` function](/{{< latest "influxdb" "v1" >}}/query_language/functions/#mean) to the data, groups averages into auto-generated time intervals (`:interval:`), and shows data for the past hour (`:dashboardTime:`).
|
||||
Those defaults are configurable using the query builder or by manually editing the query.
|
||||
|
||||
In addition, the time range (`:dashboardTime:` and `:upperDashboardTime:`) are [configurable on the dashboard](#step-6-configure-your-dashboard).
|
||||
|
@ -57,7 +57,7 @@ In addition, the time range (`:dashboardTime:` and `:upperDashboardTime:`) are [
|
|||
|
||||
### Step 4: Choose your visualization type
|
||||
|
||||
Chronograf supports many different [visualization types](/chronograf/latest/guides/visualization-types/). To choose a visualization type, click **Visualization** and select **Step-Plot Graph**.
|
||||
Chronograf supports many different [visualization types](/{{< latest "chronograf" >}}/guides/visualization-types/). To choose a visualization type, click **Visualization** and select **Step-Plot Graph**.
|
||||
|
||||
![Visualization type](/img/chronograf/1-6-g-dashboard-visualization.png)
|
||||
|
||||
|
@ -82,7 +82,7 @@ Click **Save** (the green checkmark icon) to save your cell.
|
|||
* **Reset** your cell by double-clicking your mouse in the cell window
|
||||
|
||||
> **Note:**
|
||||
These tips only apply to the line, stacked, step-plot, and line+stat [visualization types](/chronograf/latest/guides/visualization-types/).
|
||||
These tips only apply to the line, stacked, step-plot, and line+stat [visualization types](/{{< latest "chronograf" >}}/guides/visualization-types/).
|
||||
|
||||
#### Configure dashboard-wide settings
|
||||
|
||||
|
@ -127,4 +127,4 @@ To exit full screen mode, press the Esc key.
|
|||
### Template variables
|
||||
|
||||
Dashboards support template variables.
|
||||
See the [Dashboard Template Variables](/chronograf/latest/guides/dashboard-template-variables/) guide for more information.
|
||||
See the [Dashboard Template Variables](/{{< latest "chronograf" >}}/guides/dashboard-template-variables/) guide for more information.
|
||||
|
|
|
@ -11,9 +11,9 @@ menu:
|
|||
---
|
||||
|
||||
|
||||
Chronograf provides a user interface for [Kapacitor](/kapacitor/latest/), InfluxData's processing framework for creating alerts, ETL jobs (running extract, transform, load), and detecting anomalies in your data.
|
||||
Chronograf provides a user interface for [Kapacitor](/{{< latest "kapacitor" >}}/), InfluxData's processing framework for creating alerts, ETL jobs (running extract, transform, load), and detecting anomalies in your data.
|
||||
Chronograf alert rules correspond to Kapacitor tasks that trigger alerts whenever certain conditions are met.
|
||||
Behind the scenes, these tasks are stored as [TICKscripts](/kapacitor/latest/tick/) that can be edited manually or through Chronograf.
|
||||
Behind the scenes, these tasks are stored as [TICKscripts](/{{< latest "kapacitor" >}}/tick/) that can be edited manually or through Chronograf.
|
||||
Common alerting use cases that can be managed using Chronograf include:
|
||||
|
||||
* Thresholds with static ceilings, floors, and ranges.
|
||||
|
@ -26,13 +26,13 @@ This guide walks through creating a Chronograf alert rule that sends an alert me
|
|||
|
||||
## Requirements
|
||||
|
||||
[Getting started with Chronograf](/chronograf/latest/introduction/getting-started/) offers step-by-step instructions for each of the following requirements:
|
||||
[Getting started with Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/) offers step-by-step instructions for each of the following requirements:
|
||||
|
||||
* Downloaded and install the entire TICKstack (Telegraf, InfluxDB, Chronograf, and Kapacitor).
|
||||
* Configure Telegraf to collect data using the InfluxDB [system statistics](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/system) input plugin and write data to your InfluxDB instance.
|
||||
* [Create a Kapacitor connection in Chronograf](/chronograf/latest/introduction/getting-started/#4-connect-chronograf-to-kapacitor).
|
||||
* Slack is available and configured as an [event handler](/chronograf/latest/troubleshooting/frequently-asked-questions/#what-kapacitor-event-handlers-are-supported-in-chronograf) in Chronograf.
|
||||
See the [Configuring Kapacitor Event Handlers](/chronograf/latest/guides/configuring-alert-endpoints/) guide for detailed configuration instructions.
|
||||
* [Create a Kapacitor connection in Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/#4-connect-chronograf-to-kapacitor).
|
||||
* Slack is available and configured as an [event handler](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#what-kapacitor-event-handlers-are-supported-in-chronograf) in Chronograf.
|
||||
See the [Configuring Kapacitor Event Handlers](/{{< latest "chronograf" >}}/guides/configuring-alert-endpoints/) guide for detailed configuration instructions.
|
||||
|
||||
## Configure Chronograf alert rules
|
||||
|
||||
|
@ -70,7 +70,7 @@ For this example, select the **Threshold** alert type.
|
|||
Choose the time series data you want the Chronograf alert rule to use.
|
||||
Navigate through databases, measurements, fields, and tags to select the relevant data.
|
||||
|
||||
In this example, select the `telegraf` [database](/influxdb/latest/concepts/glossary/#database), the `autogen` [retention policy](/influxdb/latest/concepts/glossary/#retention-policy-rp), the `cpu` [measurement](/influxdb/latest/concepts/glossary/#measurement), and the `usage_idle` [field](/influxdb/latest/concepts/glossary/#field).
|
||||
In this example, select the `telegraf` [database](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#database), the `autogen` [retention policy](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#retention-policy-rp), the `cpu` [measurement](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#measurement), and the `usage_idle` [field](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#field).
|
||||
|
||||
![Select your data](/img/chronograf/1-6-alerts-time-series.png)
|
||||
|
||||
|
@ -113,7 +113,7 @@ In this example, use the alert message, `Your idle CPU usage is {{.Level}} at {{
|
|||
|
||||
![Specify event handler and alert message](/img/chronograf/1-6-alerts-message.png)
|
||||
|
||||
*View the Kapacitor documentation for more information about [message template data](/kapacitor/latest/nodes/alert_node/#message).*
|
||||
*View the Kapacitor documentation for more information about [message template data](/{{< latest "kapacitor" >}}/nodes/alert_node/#message).*
|
||||
|
||||
### Step 7: Save the alert rule
|
||||
|
||||
|
|
|
@ -116,7 +116,7 @@ Chronograf supports the following template variable types:
|
|||
[Text](#text)
|
||||
|
||||
### Databases
|
||||
Database template variables allow you to select from multiple target [databases](/influxdb/latest/concepts/glossary/#database).
|
||||
Database template variables allow you to select from multiple target [databases](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#database).
|
||||
|
||||
_**Database meta query**_
|
||||
Database template variables use the following meta query to return an array of all databases in your InfluxDB instance.
|
||||
|
@ -134,7 +134,7 @@ SELECT "purchases" FROM :databaseVar:."autogen"."customers"
|
|||
Database template variables are good when visualizing multiple databases with similar or identical data structures. They allow you to quickly switch between visualizations for each of your databases.
|
||||
|
||||
### Measurements
|
||||
Vary the target [measurement](/influxdb/latest/concepts/glossary/#measurement).
|
||||
Vary the target [measurement](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#measurement).
|
||||
|
||||
_**Measurement meta query**_
|
||||
Measurement template variables use the following meta query to return an array of all measurements in a given database.
|
||||
|
@ -153,7 +153,7 @@ Measurement template variables allow you to quickly switch between measurements
|
|||
|
||||
|
||||
### Field Keys
|
||||
Vary the target [field key](/influxdb/latest/concepts/glossary/#field-key).
|
||||
Vary the target [field key](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#field-key).
|
||||
|
||||
_**Field key meta query**_
|
||||
Field key template variables use the following meta query to return an array of all field keys in a given measurement from a given database.
|
||||
|
@ -172,7 +172,7 @@ Field key template variables are great if you want to quickly switch between fie
|
|||
|
||||
|
||||
### Tag Keys
|
||||
Vary the target [tag key](/influxdb/latest/concepts/glossary/#tag-key).
|
||||
Vary the target [tag key](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-key).
|
||||
|
||||
_**Tag key meta query**_
|
||||
Tag key template variables use the following meta query to return an array of all tag keys in a given measurement from a given database.
|
||||
|
@ -191,7 +191,7 @@ Tag key template variables are great if you want to quickly switch between tag k
|
|||
|
||||
|
||||
### Tag Values
|
||||
Vary the target [tag value](/influxdb/latest/concepts/glossary/#tag-value).
|
||||
Vary the target [tag value](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-value).
|
||||
|
||||
_**Tag value meta query**_
|
||||
Tag value template variables use the following meta query to return an array of all values associated with a given tag key in a specified measurement and database.
|
||||
|
@ -223,7 +223,7 @@ value3
|
|||
value4
|
||||
```
|
||||
|
||||
> Since string field values [require single quotes in InfluxQL](/influxdb/latest/troubleshooting/frequently-asked-questions/#when-should-i-single-quote-and-when-should-i-double-quote-in-queries), string values should be wrapped in single quotes.
|
||||
> Since string field values [require single quotes in InfluxQL](/{{< latest "influxdb" "v1" >}}/troubleshooting/frequently-asked-questions/#when-should-i-single-quote-and-when-should-i-double-quote-in-queries), string values should be wrapped in single quotes.
|
||||
|
||||
>```csv
|
||||
'string1','string2','string3','string4'
|
||||
|
@ -254,7 +254,7 @@ key4,value4
|
|||
|
||||
<img src="/img/chronograf/1-6-template-vars-map-dropdown.png" style="width:100%;max-width:140px;" alt="Map variable dropdown"/>
|
||||
|
||||
> If values are meant to be used as string field values, wrap them in single quote ([required by InfluxQL](/influxdb/latest/troubleshooting/frequently-asked-questions/#when-should-i-single-quote-and-when-should-i-double-quote-in-queries)). This only pertains to values. String keys do not matter.
|
||||
> If values are meant to be used as string field values, wrap them in single quote ([required by InfluxQL](/{{< latest "influxdb" "v1" >}}/troubleshooting/frequently-asked-questions/#when-should-i-single-quote-and-when-should-i-double-quote-in-queries)). This only pertains to values. String keys do not matter.
|
||||
|
||||
>```csv
|
||||
key1,'value1'
|
||||
|
|
|
@ -40,7 +40,7 @@ Add the following settings the `[[udp]]` secton in your Kapacitor configuration
|
|||
retention-policy = "autogen"
|
||||
```
|
||||
|
||||
Using this configuration, Kapacitor will listen on port `9100` for UDP packets in [Line Protocol](/influxdb/latest/write_protocols/line_protocol_tutorial/) format.
|
||||
Using this configuration, Kapacitor will listen on port `9100` for UDP packets in [Line Protocol](/{{< latest "influxdb" "v1" >}}/write_protocols/line_protocol_tutorial/) format.
|
||||
Incoming data will be scoped to be in the `game.autogen` database and retention policy.
|
||||
Restart Kapacitor so that the UDP listener service starts.
|
||||
|
||||
|
|
|
@ -10,20 +10,20 @@ menu:
|
|||
|
||||
---
|
||||
|
||||
[InfluxEnterprise](/enterprise_influxdb/latest/) offers high availability and a highly scalable clustering solution for your time series data needs.
|
||||
[InfluxEnterprise](/{{< latest "enterprise_influxdb" >}}/) offers high availability and a highly scalable clustering solution for your time series data needs.
|
||||
Use Chronograf to assess your cluster's health and to monitor the infrastructure behind your project.
|
||||
|
||||
This guide offers step-by-step instructions for using Chronograf, [InfluxDB](/influxdb/latest/), and [Telegraf](/telegraf/latest/) to monitor data nodes in your InfluxEnterprise cluster.
|
||||
This guide offers step-by-step instructions for using Chronograf, [InfluxDB](/{{< latest "influxdb" "v1" >}}/), and [Telegraf](/{{< latest "telegraf" >}}/) to monitor data nodes in your InfluxEnterprise cluster.
|
||||
|
||||
## Requirements
|
||||
|
||||
You have a fully-functioning InfluxEnterprise cluster with authentication enabled.
|
||||
See the InfluxEnterprise documentation for
|
||||
[detailed setup instructions](/enterprise_influxdb/latest/production_installation/).
|
||||
[detailed setup instructions](/{{< latest "enterprise_influxdb" >}}/production_installation/).
|
||||
This guide uses an InfluxData Enterprise cluster with three meta nodes and three data nodes; the steps are also applicable to other cluster configurations.
|
||||
|
||||
InfluxData recommends using a separate server to store your monitoring data.
|
||||
It is possible to store the monitoring data in your cluster and [connect the cluster to Chronograf](/chronograf/latest/troubleshooting/frequently-asked-questions/#how-do-i-connect-chronograf-to-an-influxenterprise-cluster), but, in general, your monitoring data should live on a separate server.
|
||||
It is possible to store the monitoring data in your cluster and [connect the cluster to Chronograf](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#how-do-i-connect-chronograf-to-an-influxenterprise-cluster), but, in general, your monitoring data should live on a separate server.
|
||||
|
||||
You're working on an Ubuntu installation.
|
||||
Chronograf and the other components of the TICK stack are supported on several operating systems and hardware architectures. Check out the [downloads page](https://portal.influxdata.com/downloads) for links to the binaries of your choice.
|
||||
|
@ -35,11 +35,11 @@ Before we begin, here's an overview of the final monitoring setup:
|
|||
![Architecture diagram](/img/chronograf/1-6-cluster-diagram.png)
|
||||
|
||||
The diagram above shows an InfluxEnterprise cluster that consists of three meta nodes (M) and three data nodes (D).
|
||||
Each data node has its own [Telegraf](/telegraf/latest/) instance (T).
|
||||
Each data node has its own [Telegraf](/{{< latest "telegraf" >}}/) instance (T).
|
||||
|
||||
Each Telegraf instance is configured to collect node CPU, disk, and memory data using the Telegraf [system stats](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/system) input plugin.
|
||||
The Telegraf instances are also configured to send those data to a single [InfluxDB OSS](/influxdb/latest/) instance that lives on a separate server.
|
||||
When Telegraf sends data to InfluxDB, it automatically [tags](/influxdb/latest/concepts/glossary/#tag) the data with the hostname of the relevant data node.
|
||||
The Telegraf instances are also configured to send those data to a single [InfluxDB OSS](/{{< latest "influxdb" "v1" >}}/) instance that lives on a separate server.
|
||||
When Telegraf sends data to InfluxDB, it automatically [tags](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag) the data with the hostname of the relevant data node.
|
||||
|
||||
The InfluxDB OSS instance that stores the Telegraf data is connected to Chronograf.
|
||||
Chronograf uses the hostnames in the Telegraf data to populate the Host List page and provide other hostname-specific information in the user interface.
|
||||
|
@ -54,7 +54,7 @@ InfluxDB can be downloaded from the [InfluxData downloads page](https://portal.i
|
|||
|
||||
#### Step 2: Enable authentication
|
||||
|
||||
For security purposes, enable authentication in the InfluxDB [configuration file (influxdb.conf)](/influxdb/latest/administration/config/), which is located in `/etc/influxdb/influxdb.conf`.
|
||||
For security purposes, enable authentication in the InfluxDB [configuration file (influxdb.conf)](/{{< latest "influxdb" "v1" >}}/administration/config/), which is located in `/etc/influxdb/influxdb.conf`.
|
||||
|
||||
In the `[http]` section of the configuration file, uncomment the `auth-enabled` option and set it to `true`:
|
||||
|
||||
|
@ -80,7 +80,7 @@ Next, start the InfluxDB process:
|
|||
|
||||
#### Step 4: Create an admin user
|
||||
|
||||
Create an [admin user](/influxdb/latest/query_language/authentication_and_authorization/#user-types-and-privileges) on your InfluxDB instance.
|
||||
Create an [admin user](/{{< latest "influxdb" "v1" >}}/query_language/authentication_and_authorization/#user-types-and-privileges) on your InfluxDB instance.
|
||||
Because you enabled authentication, you must perform this step before moving on to the next section.
|
||||
Run the command below to create an admin user, replacing `chronothan` and `supersecret` with your own username and password.
|
||||
Note that the password requires single quotes.
|
||||
|
@ -204,7 +204,7 @@ Replace the `chronothan` and `supersecret` values with your actual username and
|
|||
```
|
||||
|
||||
The expected output is similar to the JSON code block below.
|
||||
In this case, the `telegraf` database has three different [tag values](/influxdb/latest/concepts/glossary/#tag-value) for the `host` [tag key](/influxdb/latest/concepts/glossary/#tag-key): `data-node-01`, `data-node-02`, and `data-node-03`.
|
||||
In this case, the `telegraf` database has three different [tag values](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-value) for the `host` [tag key](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-key): `data-node-01`, `data-node-02`, and `data-node-03`.
|
||||
Those values match the hostnames of the three data nodes in the cluster; this means Telegraf is successfully writing monitoring data from those hosts to the InfluxDB OSS instance!
|
||||
```
|
||||
{
|
||||
|
@ -284,6 +284,6 @@ In the image below, the Chronograf query editor is used to visualize the idle CP
|
|||
![Data Explorer](/img/chronograf/1-6-cluster-de.png)
|
||||
|
||||
Create more customized graphs and save them to a dashboard on the Dashboard page in Chronograf.
|
||||
See the [Creating Chronograf dashboards](/chronograf/latest/guides/create-a-dashboard/) guide for more information.
|
||||
See the [Creating Chronograf dashboards](/{{< latest "chronograf" >}}/guides/create-a-dashboard/) guide for more information.
|
||||
|
||||
That's it! You've successfully configured Telegraf to collect and write data, InfluxDB to store those data, and Chonograf to use those data for monitoring and visualization purposes.
|
||||
|
|
|
@ -7,7 +7,7 @@ menu:
|
|||
weight: 130
|
||||
parent: Guides
|
||||
---
|
||||
Explore and visualize your data in the **Data Explorer**. For both InfluxQL and Flux, Chronograf allows you to move seamlessly between using the builder or templates and manually editing the query; when possible, the interface automatically populates the builder with the information from your raw query. Choose between [visualization types](/chronograf/latest/guides/visualization-types/) for your query.
|
||||
Explore and visualize your data in the **Data Explorer**. For both InfluxQL and Flux, Chronograf allows you to move seamlessly between using the builder or templates and manually editing the query; when possible, the interface automatically populates the builder with the information from your raw query. Choose between [visualization types](/{{< latest "chronograf" >}}/guides/visualization-types/) for your query.
|
||||
|
||||
To open the **Data Explorer**, click the **Explore** icon in the navigation bar:
|
||||
|
||||
|
@ -23,7 +23,7 @@ To open the **Data Explorer**, click the **Explore** icon in the navigation bar:
|
|||
|
||||
## Explore data with InfluxQL
|
||||
|
||||
InfluxQL is a SQL-like query language you can use to interact with data in InfluxDB. For detailed tutorials and reference material, see our [InfluxQL documentation](/influxdb/latest/query_language/).
|
||||
InfluxQL is a SQL-like query language you can use to interact with data in InfluxDB. For detailed tutorials and reference material, see our [InfluxQL documentation](/{{< latest "influxdb" "v1" >}}/query_language/).
|
||||
|
||||
1. Open the Data Explorer and click **Add a Query**.
|
||||
2. To the right of the source dropdown above the graph placeholder, select **InfluxQL** as the source type.
|
||||
|
@ -66,7 +66,7 @@ Flux is InfluxData's new functional data scripting language designed for queryin
|
|||
|
||||
## Visualize your query
|
||||
|
||||
Select the **Visualization** tab at the top of the **Data Explorer**. For details about all of the available visualization options, see [Visualization types in Chronograf](/chronograf/latest/guides/visualization-types/).
|
||||
Select the **Visualization** tab at the top of the **Data Explorer**. For details about all of the available visualization options, see [Visualization types in Chronograf](/{{< latest "chronograf" >}}/guides/visualization-types/).
|
||||
|
||||
## Add queries to dashboards
|
||||
|
||||
|
|
|
@ -13,7 +13,7 @@ menu:
|
|||
|
||||
Pre-created dashboards are delivered with Chronograf depending on which Telegraf input plugins you have enabled and are available from the Host List page. These dashboards, which are built in and not editable, include cells with data visualizations for metrics that are relevant to data sources you are likely to be using.
|
||||
|
||||
> Note that these pre-created dashboards cannot be cloned or customized. They appear only as part of the Host List view and are associated with metrics gathered from a single host. Dashboard templates are also available and deliver a solid starting point for customizing your own unique dashboards based on the Telegraf plugins enabled and operate across one or more hosts. For details, see [Dashboard templates](/chronograf/latest/guides/create-a-dashboard/#dashboard-templates).
|
||||
> Note that these pre-created dashboards cannot be cloned or customized. They appear only as part of the Host List view and are associated with metrics gathered from a single host. Dashboard templates are also available and deliver a solid starting point for customizing your own unique dashboards based on the Telegraf plugins enabled and operate across one or more hosts. For details, see [Dashboard templates](/{{< latest "chronograf" >}}/guides/create-a-dashboard/#dashboard-templates).
|
||||
|
||||
## Requirements
|
||||
|
||||
|
@ -37,7 +37,7 @@ Find a list of apps (pre-created dashboards) available to use with Chronograf be
|
|||
- JSON files included in the app
|
||||
- Cell titles included in each JSON file
|
||||
|
||||
The JSON files for apps are included in the `/usr/share/chronograf/canned` directory. Find information about the configuration option `--canned-path` on the [Chronograf configuration options](/chronograf/latest/administration/config-options/) page.
|
||||
The JSON files for apps are included in the `/usr/share/chronograf/canned` directory. Find information about the configuration option `--canned-path` on the [Chronograf configuration options](/{{< latest "chronograf" >}}/administration/config-options/) page.
|
||||
|
||||
Enable and disable apps in your [Telegraf configuration file](by default, `/etc/telegraf/telegraf.conf`). See [Configuring Telegraf](/telegraf/v1.13/administration/configuration/) for details.
|
||||
|
||||
|
@ -68,7 +68,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/
|
|||
|
||||
## apache
|
||||
|
||||
**Required Telegraf plugin:** [Apache input plugin](/telegraf/latest/plugins/inputs/#apache-http-server)
|
||||
**Required Telegraf plugin:** [Apache input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#apache-http-server)
|
||||
|
||||
`apache.json`
|
||||
|
||||
|
@ -78,7 +78,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/
|
|||
|
||||
## consul
|
||||
|
||||
**Required Telegraf plugin:** [Consul input plugin](/telegraf/latest/plugins/inputs/#consul)
|
||||
**Required Telegraf plugin:** [Consul input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#consul)
|
||||
|
||||
`consul_http.json`
|
||||
|
||||
|
@ -98,7 +98,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/
|
|||
|
||||
## docker
|
||||
|
||||
**Required Telegraf plugin:** [Docker input plugin](/telegraf/latest/plugins/inputs/#docker)
|
||||
**Required Telegraf plugin:** [Docker input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#docker)
|
||||
|
||||
`docker.json`
|
||||
|
||||
|
@ -118,7 +118,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/
|
|||
|
||||
## elasticsearch
|
||||
|
||||
**Required Telegraf plugin:** [Elasticsearch input plugin](/telegraf/latest/plugins/inputs/#elasticsearch)
|
||||
**Required Telegraf plugin:** [Elasticsearch input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#elasticsearch)
|
||||
|
||||
`elasticsearch.json`
|
||||
|
||||
|
@ -135,7 +135,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/
|
|||
|
||||
## haproxy
|
||||
|
||||
**Required Telegraf plugin:** [HAProxy input plugin](/telegraf/latest/plugins/inputs/#haproxy)
|
||||
**Required Telegraf plugin:** [HAProxy input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#haproxy)
|
||||
|
||||
`haproxy.json`
|
||||
|
||||
|
@ -165,7 +165,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/
|
|||
|
||||
## influxdb
|
||||
|
||||
**Required Telegraf plugin:** [InfluxDB input plugin](/telegraf/latest/plugins/inputs/#influxdb-v-1)
|
||||
**Required Telegraf plugin:** [InfluxDB input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#influxdb-v-1)
|
||||
|
||||
`influxdb_database.json`
|
||||
|
||||
|
@ -210,7 +210,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/
|
|||
|
||||
## Memcached (`memcached`)
|
||||
|
||||
**Required Telegraf plugin:** [Memcached input plugin](/telegraf/latest/plugins/inputs/#memcached)
|
||||
**Required Telegraf plugin:** [Memcached input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#memcached)
|
||||
|
||||
`memcached.json`
|
||||
|
||||
|
@ -230,7 +230,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/
|
|||
|
||||
## mesos
|
||||
|
||||
**Required Telegraf plugin:** [Mesos input plugin](/telegraf/latest/plugins/inputs/#mesos)
|
||||
**Required Telegraf plugin:** [Mesos input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#mesos)
|
||||
|
||||
`mesos.json`
|
||||
|
||||
|
@ -245,7 +245,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/
|
|||
|
||||
## mongodb
|
||||
|
||||
**Required Telegraf plugin:** [MongoDB input plugin](/telegraf/latest/plugins/inputs/#mongodb)
|
||||
**Required Telegraf plugin:** [MongoDB input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#mongodb)
|
||||
|
||||
`mongodb.json`
|
||||
|
||||
|
@ -257,7 +257,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/
|
|||
|
||||
## mysql
|
||||
|
||||
**Required Telegraf plugin:** [MySQL input plugin](/telegraf/latest/plugins/inputs/#mysql)
|
||||
**Required Telegraf plugin:** [MySQL input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#mysql)
|
||||
|
||||
`mysql.json`
|
||||
|
||||
|
@ -268,7 +268,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/
|
|||
|
||||
## nginx
|
||||
|
||||
**Required Telegraf plugin:** [NGINX input plugin](/telegraf/latest/plugins/inputs/#nginx)
|
||||
**Required Telegraf plugin:** [NGINX input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#nginx)
|
||||
|
||||
`nginx.json`
|
||||
|
||||
|
@ -279,7 +279,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/
|
|||
|
||||
## nsq
|
||||
|
||||
**Required Telegraf plugin:** [NSQ input plugin](/telegraf/latest/plugins/inputs/#nsq)
|
||||
**Required Telegraf plugin:** [NSQ input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#nsq)
|
||||
|
||||
`nsq_channel.json`
|
||||
|
||||
|
@ -300,7 +300,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/
|
|||
|
||||
## phpfpm
|
||||
|
||||
**Required Telegraf plugin:** [PHPfpm input plugin](/telegraf/latest/plugins/inputs/#php-fpm)
|
||||
**Required Telegraf plugin:** [PHPfpm input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#php-fpm)
|
||||
|
||||
`phpfpm.json`
|
||||
|
||||
|
@ -312,7 +312,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/
|
|||
|
||||
## ping
|
||||
|
||||
**Required Telegraf plugin:** [Ping input plugin](/telegraf/latest/plugins/inputs/#ping)
|
||||
**Required Telegraf plugin:** [Ping input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#ping)
|
||||
|
||||
`ping.json`
|
||||
|
||||
|
@ -321,7 +321,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/
|
|||
|
||||
## postgresql
|
||||
|
||||
**Required Telegraf plugin:** [PostgreSQL input plugin](/telegraf/latest/plugins/inputs/#postgresql)
|
||||
**Required Telegraf plugin:** [PostgreSQL input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#postgresql)
|
||||
|
||||
`postgresql.json`
|
||||
|
||||
|
@ -332,7 +332,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/
|
|||
|
||||
## rabbitmq
|
||||
|
||||
**Required Telegraf plugin:** [RabbitMQ input plugin](/telegraf/latest/plugins/inputs/#rabbitmq)
|
||||
**Required Telegraf plugin:** [RabbitMQ input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#rabbitmq)
|
||||
|
||||
`rabbitmq.json`
|
||||
|
||||
|
@ -343,7 +343,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/
|
|||
|
||||
## redis
|
||||
|
||||
**Required Telegraf plugin:** [Redis input plugin](/telegraf/latest/plugins/inputs/#redis)
|
||||
**Required Telegraf plugin:** [Redis input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#redis)
|
||||
|
||||
|
||||
`redis.json`
|
||||
|
@ -355,7 +355,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/
|
|||
|
||||
## riak
|
||||
|
||||
**Required Telegraf plugin:** [Riak input plugin](/telegraf/latest/plugins/inputs/#riak)
|
||||
**Required Telegraf plugin:** [Riak input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#riak)
|
||||
|
||||
|
||||
`riak.json`
|
||||
|
@ -374,7 +374,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/
|
|||
|
||||
### cpu
|
||||
|
||||
**Required Telegraf plugin:** [CPU input plugin](/telegraf/latest/plugins/inputs/#cpu)
|
||||
**Required Telegraf plugin:** [CPU input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#cpu)
|
||||
|
||||
`cpu.json`
|
||||
|
||||
|
@ -384,13 +384,13 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/
|
|||
|
||||
`disk.json`
|
||||
|
||||
**Required Telegraf plugin:** [Disk input plugin](/telegraf/latest/plugins/inputs/#disk)
|
||||
**Required Telegraf plugin:** [Disk input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#disk)
|
||||
|
||||
* "System - Disk used %"
|
||||
|
||||
### diskio
|
||||
|
||||
**Required Telegraf plugin:** [DiskIO input plugin](/telegraf/latest/plugins/inputs/#diskio)
|
||||
**Required Telegraf plugin:** [DiskIO input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#diskio)
|
||||
|
||||
`diskio.json`
|
||||
|
||||
|
@ -399,7 +399,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/
|
|||
|
||||
### mem
|
||||
|
||||
**Required Telegraf plugin:** [Mem input plugin](/telegraf/latest/plugins/inputs/#mem)
|
||||
**Required Telegraf plugin:** [Mem input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#mem)
|
||||
|
||||
`mem.json`
|
||||
|
||||
|
@ -407,7 +407,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/
|
|||
|
||||
### net
|
||||
|
||||
**Required Telegraf plugin:** [Net input plugin](/telegraf/latest/plugins/inputs/#net)
|
||||
**Required Telegraf plugin:** [Net input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#net)
|
||||
|
||||
`net.json`
|
||||
|
||||
|
@ -416,7 +416,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/
|
|||
|
||||
### netstat
|
||||
|
||||
**Required Telegraf plugin:** [Netstat input plugin](/telegraf/latest/plugins/inputs/#netstat)
|
||||
**Required Telegraf plugin:** [Netstat input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#netstat)
|
||||
|
||||
`netstat.json`
|
||||
|
||||
|
@ -425,7 +425,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/
|
|||
|
||||
### processes
|
||||
|
||||
**Required Telegraf plugin:** [Processes input plugin](/telegraf/latest/plugins/inputs/#processes)
|
||||
**Required Telegraf plugin:** [Processes input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#processes)
|
||||
|
||||
`processes.json`
|
||||
|
||||
|
@ -433,7 +433,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/
|
|||
|
||||
### procstat
|
||||
|
||||
**Required Telegraf plugin:** [Procstat input plugin](/telegraf/latest/plugins/inputs/#procstat)
|
||||
**Required Telegraf plugin:** [Procstat input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#procstat)
|
||||
|
||||
`procstat.json`
|
||||
|
||||
|
@ -442,7 +442,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/
|
|||
|
||||
### system
|
||||
|
||||
**Required Telegraf plugin:** [Procstat input plugin](/telegraf/latest/plugins/inputs/#procstat)
|
||||
**Required Telegraf plugin:** [Procstat input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#procstat)
|
||||
|
||||
`load.json`
|
||||
|
||||
|
@ -450,7 +450,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/
|
|||
|
||||
## varnish
|
||||
|
||||
**Required Telegraf plugin:** [Varnish](/telegraf/latest/plugins/inputs/#varnish)
|
||||
**Required Telegraf plugin:** [Varnish](/{{< latest "telegraf" >}}/plugins/inputs/#varnish)
|
||||
|
||||
`varnish.json`
|
||||
|
||||
|
@ -459,7 +459,7 @@ Enable and disable apps in your [Telegraf configuration file](by default, `/etc/
|
|||
|
||||
## win_system
|
||||
|
||||
**Required Telegraf plugin:** [Windows Performance Counters input plugin](/telegraf/latest/plugins/inputs/#windows-performance-counters)
|
||||
**Required Telegraf plugin:** [Windows Performance Counters input plugin](/{{< latest "telegraf" >}}/plugins/inputs/#windows-performance-counters)
|
||||
|
||||
`win_cpu.json`
|
||||
|
||||
|
|
|
@ -181,10 +181,10 @@ The **Single Stat** view displays the most recent value of the specified time se
|
|||
|
||||
![Single Stat view](/img/chronograf/1-6-viz-single-stat-selector.png)
|
||||
|
||||
If a cell's query includes a [`GROUP BY` tag](/influxdb/latest/query_language/data_exploration/#group-by-tags) clause, Chronograf sorts the different [series](/influxdb/latest/concepts/glossary/#series) lexicographically and shows the most recent [field value](/influxdb/latest/concepts/glossary/#field-value) associated with the first series.
|
||||
For example, if a query groups by the `name` [tag key](/influxdb/latest/concepts/glossary/#tag-key) and `name` has two [tag values](/influxdb/latest/concepts/glossary/#tag-value) (`chronelda` and `chronz`), Chronograf shows the most recent field value associated with the `chronelda` series.
|
||||
If a cell's query includes a [`GROUP BY` tag](/{{< latest "influxdb" "v1" >}}/query_language/data_exploration/#group-by-tags) clause, Chronograf sorts the different [series](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#series) lexicographically and shows the most recent [field value](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#field-value) associated with the first series.
|
||||
For example, if a query groups by the `name` [tag key](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-key) and `name` has two [tag values](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#tag-value) (`chronelda` and `chronz`), Chronograf shows the most recent field value associated with the `chronelda` series.
|
||||
|
||||
If a cell's query includes more than one [field key](/influxdb/latest/concepts/glossary/#field-key) in the [`SELECT` clause](/influxdb/latest/query_language/data_exploration/#select-clause), Chronograf returns the most recent field value associated with the first field key in the `SELECT` clause.
|
||||
If a cell's query includes more than one [field key](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#field-key) in the [`SELECT` clause](/{{< latest "influxdb" "v1" >}}/query_language/data_exploration/#select-clause), Chronograf returns the most recent field value associated with the first field key in the `SELECT` clause.
|
||||
For example, if a query's `SELECT` clause is `SELECT "chronogiraffe","chronelda"`, Chronograf shows the most recent field value associated with the `chronogiraffe` field key.
|
||||
|
||||
#### Single Stat Controls
|
||||
|
|
|
@ -2,7 +2,7 @@
|
|||
title: Get started with Chronograf
|
||||
description: Get started with Chronograf.
|
||||
aliases:
|
||||
- /chronograf/latest/introduction/getting-started/
|
||||
- /{{< latest "chronograf" >}}/introduction/getting-started/
|
||||
- /chronograf/v1.8/introduction/getting_started/
|
||||
menu:
|
||||
chronograf_1_8:
|
||||
|
@ -12,18 +12,18 @@ menu:
|
|||
---
|
||||
|
||||
## Overview
|
||||
Chronograf allows you to quickly see data you have stored in InfluxDB so you can build robust queries and alerts. After your administrator has set up Chronograf as described in [Installing Chronograf](/chronograf/latest/introduction/installation), get started with key features using the guides below.
|
||||
Chronograf allows you to quickly see data you have stored in InfluxDB so you can build robust queries and alerts. After your administrator has set up Chronograf as described in [Installing Chronograf](/{{< latest "chronograf" >}}/introduction/installation), get started with key features using the guides below.
|
||||
|
||||
### Data visualization
|
||||
* Investigate your data by building queries using the [Data Explorer](/chronograf/latest/guides/querying-data/).
|
||||
* Use [pre-created dashboards](/chronograf/latest/guides/using-precreated-dashboards/) to monitor your application data or [create your own dashboards](/chronograf/latest/guides/create-a-dashboard/).
|
||||
* Customize dashboards using [template variables](/chronograf/latest/guides/dashboard-template-variables/).
|
||||
* Investigate your data by building queries using the [Data Explorer](/{{< latest "chronograf" >}}/guides/querying-data/).
|
||||
* Use [pre-created dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards/) to monitor your application data or [create your own dashboards](/{{< latest "chronograf" >}}/guides/create-a-dashboard/).
|
||||
* Customize dashboards using [template variables](/{{< latest "chronograf" >}}/guides/dashboard-template-variables/).
|
||||
|
||||
### Alerting
|
||||
* [Create alert rules](/chronograf/latest/guides/create-alert-rules/) to generate threshold, relative, and deadman alerts on your data.
|
||||
* [View all active alerts](/chronograf/latest/guides/create-alert-rules/#step-2-view-the-alerts) on an alert dashboard.
|
||||
* Use [alert endpoints](/chronograf/latest/guides/configuring-alert-endpoints/) in Chronograf to send alert messages to specific URLs and applications.
|
||||
* [Create alert rules](/{{< latest "chronograf" >}}/guides/create-alert-rules/) to generate threshold, relative, and deadman alerts on your data.
|
||||
* [View all active alerts](/{{< latest "chronograf" >}}/guides/create-alert-rules/#step-2-view-the-alerts) on an alert dashboard.
|
||||
* Use [alert endpoints](/{{< latest "chronograf" >}}/guides/configuring-alert-endpoints/) in Chronograf to send alert messages to specific URLs and applications.
|
||||
|
||||
### Infrastructure monitoring
|
||||
* [View all hosts](/chronograf/latest/guides/monitoring-influxenterprise-clusters/#step-4-explore-the-monitoring-data-in-chronograf) and their statuses in your infrastructure.
|
||||
* [Use pre-created dashboards](/chronograf/latest/guides/using-precreated-dashboards/) to monitor your applications.
|
||||
* [View all hosts](/{{< latest "chronograf" >}}/guides/monitoring-influxenterprise-clusters/#step-4-explore-the-monitoring-data-in-chronograf) and their statuses in your infrastructure.
|
||||
* [Use pre-created dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards/) to monitor your applications.
|
||||
|
|
|
@ -9,4 +9,4 @@ menu:
|
|||
|
||||
Follow the link below to access Chronograf's FAQ.
|
||||
|
||||
## [Frequently Asked Questions](/chronograf/latest/troubleshooting/frequently-asked-questions/)
|
||||
## [Frequently Asked Questions](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/)
|
||||
|
|
|
@ -9,7 +9,7 @@ menu:
|
|||
|
||||
## How do I connect Chronograf to an InfluxEnterprise cluster?
|
||||
|
||||
The connection details form requires additional information when connecting Chronograf to an [InfluxEnterprise cluster](https://docs.influxdata.com/enterprise_influxdb/latest/).
|
||||
The connection details form requires additional information when connecting Chronograf to an [InfluxEnterprise cluster](/{{< latest "enterprise_influxdb" >}}/).
|
||||
|
||||
When you enter the InfluxDB HTTP bind address in the `Connection String` input, Chronograf automatically checks if that InfluxDB instance is a data node.
|
||||
If it is a data node, Chronograf automatically adds the `Meta Service Connection URL` input to the connection details form.
|
||||
|
@ -19,4 +19,4 @@ Enter the HTTP bind address of one of your cluster's meta nodes into that input
|
|||
|
||||
Note that the example above assumes that you do not have authentication enabled.
|
||||
If you have authentication enabled, the form requires username and password information.
|
||||
For more details about monitoring an InfluxEnterprise cluster, see the [Monitor an InfluxEnterprise Cluster](/chronograf/latest/guides/monitoring-influxenterprise-clusters/) guide.
|
||||
For more details about monitoring an InfluxEnterprise cluster, see the [Monitor an InfluxEnterprise Cluster](/{{< latest "chronograf" >}}/guides/monitoring-influxenterprise-clusters/) guide.
|
||||
|
|
|
@ -23,7 +23,7 @@ Third party suppliers make no representation nor warranty with respect to such t
|
|||
Third party suppliers assume no liability for any claim that might arise with respect to such third party software, nor for a
|
||||
customer’s use of or inability to use the third party software.
|
||||
|
||||
In addition to [third party software incorporated in InfluxDB](http://docs.influxdata.com/influxdb/v1.5/about_the_project/#third_party), InfluxDB Enterprise incorporates the following additional third party software:
|
||||
In addition to [third party software incorporated in InfluxDB](/influxdb/v1.5/about_the_project/#third_party), InfluxDB Enterprise incorporates the following additional third party software:
|
||||
|
||||
| Third Party / Open Source Software - Description | License Type |
|
||||
| ---------------------------------------- | ---------------------------------------- |
|
||||
|
|
|
@ -48,7 +48,7 @@ Please see the [InfluxDB OSS release notes](/influxdb/v1.5/about_the_project/rel
|
|||
## v1.5.0 [2018-03-06]
|
||||
|
||||
> ***Note:*** This release builds off of the 1.5 release of InfluxDB OSS. Please see the [InfluxDB OSS release
|
||||
> notes](https://docs.influxdata.com/influxdb/v1.5/about_the_project/releasenotes-changelog/) for more information about the InfluxDB OSS release.
|
||||
> notes](/influxdb/v1.5/about_the_project/releasenotes-changelog/) for more information about the InfluxDB OSS release.
|
||||
|
||||
For highlights of the InfluxDB 1.5 release, see [What's new in InfluxDB 1.5](/influxdb/v1.5/about_the_project/whats_new/).
|
||||
|
||||
|
@ -167,7 +167,7 @@ Please see the OSS [release notes](/influxdb/v1.3/about_the_project/releasenotes
|
|||
|
||||
## v1.3.4 [2017-08-23]
|
||||
|
||||
This release builds off of the 1.3.4 release of OSS InfluxDB. Please see the [OSS release notes](https://docs.influxdata.com/influxdb/v1.3/about_the_project/releasenotes-changelog/) for more information about the OSS releases.
|
||||
This release builds off of the 1.3.4 release of OSS InfluxDB. Please see the [OSS release notes](/influxdb/v1.3/about_the_project/releasenotes-changelog/) for more information about the OSS releases.
|
||||
|
||||
### Bug fixes
|
||||
|
||||
|
@ -175,7 +175,7 @@ This release builds off of the 1.3.4 release of OSS InfluxDB. Please see the [OS
|
|||
|
||||
## v1.3.3 [2017-08-10]
|
||||
|
||||
This release builds off of the 1.3.3 release of OSS InfluxDB. Please see the [OSS release notes](https://docs.influxdata.com/influxdb/v1.3/about_the_project/releasenotes-changelog/) for more information about the OSS releases.
|
||||
This release builds off of the 1.3.3 release of OSS InfluxDB. Please see the [OSS release notes](/influxdb/v1.3/about_the_project/releasenotes-changelog/) for more information about the OSS releases.
|
||||
|
||||
### Bug fixes
|
||||
|
||||
|
@ -540,4 +540,4 @@ Backup and restore has been updated to fix issues and refine existing capabiliti
|
|||
The Enterprise Web Console has officially been deprecated and will be eliminated entirely by the end of 2017.
|
||||
No additional features will be added and no additional bug fix releases are planned.
|
||||
|
||||
For browser-based access to InfluxDB Enterprise, [Chronograf](/chronograf/latest/introduction) is now the recommended tool to use.
|
||||
For browser-based access to InfluxDB Enterprise, [Chronograf](/{{< latest "chronograf" >}}/introduction) is now the recommended tool to use.
|
||||
|
|
|
@ -90,7 +90,7 @@ Data nodes hold the actual time series data. The minimum number of data nodes to
|
|||
|
||||
## Chronograf
|
||||
|
||||
[Chronograf](/chronograf/latest/introduction/getting-started/) is the user interface component of InfluxData’s TICK stack.
|
||||
[Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/) is the user interface component of InfluxData’s TICK stack.
|
||||
It makes owning the monitoring and alerting for your infrastructure easy to setup and maintain.
|
||||
It talks directly to the data and meta nodes over their HTTP protocols, which are bound by default to ports `8086` for data nodes and port `8091` for meta nodes.
|
||||
|
||||
|
|
|
@ -72,6 +72,6 @@ query capacity within the cluster.
|
|||
|
||||
Legacy user interface for the InfluxEnterprise cluster.
|
||||
|
||||
This has been deprecated and the suggestion is to use [Chronograf](/chronograf/latest/introduction/).
|
||||
This has been deprecated and the suggestion is to use [Chronograf](/{{< latest "chronograf" >}}/introduction/).
|
||||
|
||||
If you are transitioning from the Enterprise Web Console to Chronograf and helpful [transition guide](/chronograf/latest/guides/transition-web-admin-interface/) is available.
|
||||
If you are transitioning from the Enterprise Web Console to Chronograf and helpful [transition guide](/{{< latest "chronograf" >}}/guides/transition-web-admin-interface/) is available.
|
||||
|
|
|
@ -208,7 +208,7 @@ You can do this with [ALTER RETENTION POLICY](/influxdb/v1.5/query_language/data
|
|||
Next, [rebalance](/enterprise_influxdb/v1.5/guides/rebalance/) your cluster manually to meet the desired
|
||||
replication factor for existing shards.
|
||||
|
||||
Finally, if you were using [Chronograf](/chronograf/latest/), you can
|
||||
Finally, if you were using [Chronograf](/{{< latest "chronograf" >}}/), you can
|
||||
add your Enterprise instance as a new data source. If you were not using
|
||||
[Chronograf](/chronograf/latest/introduction/installation/), we recommend going through
|
||||
[Chronograf](/{{< latest "chronograf" >}}/introduction/installation/), we recommend going through
|
||||
the installation instructions and using it as your primary management UI for the instance. -->
|
||||
|
|
|
@ -10,9 +10,9 @@ menu:
|
|||
parent: Introduction
|
||||
---
|
||||
|
||||
Now that you successfully [installed and set up](/enterprise_influxdb/v1.5/introduction/meta_node_installation/) InfluxDB Enterprise, you can configure Chronograf for [monitoring InfluxDB Enterprise clusters](/chronograf/latest/guides/monitor-an-influxenterprise-cluster/).
|
||||
Now that you successfully [installed and set up](/enterprise_influxdb/v1.5/introduction/meta_node_installation/) InfluxDB Enterprise, you can configure Chronograf for [monitoring InfluxDB Enterprise clusters](/{{< latest "chronograf" >}}/guides/monitor-an-influxenterprise-cluster/).
|
||||
|
||||
See [Getting started with Chronograf](/chronograf/latest/introduction/getting-started/) to learn more about using Chronograf with the InfluxData time series platform.
|
||||
See [Getting started with Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/) to learn more about using Chronograf with the InfluxData time series platform.
|
||||
|
||||
|
||||
### Where to from here?
|
||||
|
|
|
@ -3,7 +3,7 @@ title: Installation options (⏰ Please Read!)
|
|||
aliases:
|
||||
- /enterprise_influxdb/v1.5/introduction/meta_node_installation/
|
||||
- /enterprise_influxdb/v1.5/introduction/data_node_installation/
|
||||
- /chronograf/latest/introduction/installation
|
||||
- /{{< latest "chronograf" >}}/introduction/installation
|
||||
- /enterprise/v1.5/introduction/installation_guidelines/
|
||||
menu:
|
||||
enterprise_influxdb_1_5:
|
||||
|
|
|
@ -12,4 +12,4 @@ menu:
|
|||
Now that you've installed the meta nodes and data nodes, you are ready to install Chronograf
|
||||
to provide you with a user interface to access the InfluxDB Enterprise instance.
|
||||
|
||||
[Installation instruction for Chronograf](/chronograf/latest/introduction/installation/)
|
||||
[Installation instruction for Chronograf](/{{< latest "chronograf" >}}/introduction/installation/)
|
||||
|
|
|
@ -10,7 +10,7 @@ menu:
|
|||
---
|
||||
|
||||
InfluxDB Enterprise offers highly scalable clusters on your infrastructure
|
||||
and a management user interface ([using Chronograf](https://docs.influxdata.com/chronograf/latest)) for working with clusters.
|
||||
and a management user interface ([using Chronograf](/{{< latest "chronograf" >}})) for working with clusters.
|
||||
The Production Installation process is designed for users looking to
|
||||
deploy InfluxDB Enterprise in a production environment.
|
||||
The following steps will get you up and running with the first essential component of
|
||||
|
|
|
@ -11,4 +11,4 @@ menu:
|
|||
Now that you've installed the meta nodes and data nodes, you are ready to install Chronograf
|
||||
to provide you with a user interface to access the InfluxDB Enterprise instance.
|
||||
|
||||
[Installing Chronograf](/chronograf/latest/introduction/installation/)
|
||||
[Installing Chronograf](/{{< latest "chronograf" >}}/introduction/installation/)
|
||||
|
|
|
@ -193,7 +193,7 @@ First, in `/etc/influxdb/influxdb.conf`, uncomment:
|
|||
* `shared-secret` in the `[http]` section and set it to a long pass phrase that will be used to sign tokens for intra-cluster communication. This value needs to be consistent across all data nodes.
|
||||
|
||||
> **Note:** When you enable authentication, InfluxDB only executes HTTP requests that are sent with valid credentials.
|
||||
See the [authentication section](/influxdb/latest/administration/authentication_and_authorization/#authentication) for more information.
|
||||
See the [authentication section](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#authentication) for more information.
|
||||
|
||||
Second, in `/etc/influxdb/influxdb.conf`, set:
|
||||
|
||||
|
|
|
@ -22,7 +22,7 @@ Third party suppliers make no representation nor warranty with respect to such t
|
|||
Third party suppliers assume no liability for any claim that might arise with respect to such third party software, nor for a
|
||||
customer’s use of or inability to use the third party software.
|
||||
|
||||
In addition to [third party software incorporated in InfluxDB](http://docs.influxdata.com/influxdb/v1.6/about_the_project/#third_party), InfluxDB Enterprise incorporates the following additional third party software:
|
||||
In addition to [third party software incorporated in InfluxDB](/influxdb/v1.6/about_the_project/#third_party), InfluxDB Enterprise incorporates the following additional third party software:
|
||||
|
||||
| Third Party / Open Source Software - Description | License Type |
|
||||
| ---------------------------------------- | ---------------------------------------- |
|
||||
|
|
|
@ -134,7 +134,7 @@ Please see the [InfluxDB OSS release notes](/influxdb/v1.6/about_the_project/rel
|
|||
## v1.5.0 [2018-03-06]
|
||||
|
||||
> ***Note:*** This release builds off of the 1.5 release of InfluxDB OSS. Please see the [InfluxDB OSS release
|
||||
> notes](https://docs.influxdata.com/influxdb/v1.6/about_the_project/releasenotes-changelog/) for more information about the InfluxDB OSS release.
|
||||
> notes](/influxdb/v1.6/about_the_project/releasenotes-changelog/) for more information about the InfluxDB OSS release.
|
||||
|
||||
For highlights of the InfluxDB 1.5 release, see [What's new in InfluxDB 1.5](/influxdb/v1.5/about_the_project/whats_new/).
|
||||
|
||||
|
@ -253,7 +253,7 @@ Please see the OSS [release notes](/influxdb/v1.3/about_the_project/releasenotes
|
|||
|
||||
## v1.3.4 [2017-08-23]
|
||||
|
||||
This release builds off of the 1.3.4 release of OSS InfluxDB. Please see the [OSS release notes](https://docs.influxdata.com/influxdb/v1.3/about_the_project/releasenotes-changelog/) for more information about the OSS releases.
|
||||
This release builds off of the 1.3.4 release of OSS InfluxDB. Please see the [OSS release notes](/influxdb/v1.3/about_the_project/releasenotes-changelog/) for more information about the OSS releases.
|
||||
|
||||
### Bugfixes
|
||||
|
||||
|
@ -261,7 +261,7 @@ This release builds off of the 1.3.4 release of OSS InfluxDB. Please see the [OS
|
|||
|
||||
## v1.3.3 [2017-08-10]
|
||||
|
||||
This release builds off of the 1.3.3 release of OSS InfluxDB. Please see the [OSS release notes](https://docs.influxdata.com/influxdb/v1.3/about_the_project/releasenotes-changelog/) for more information about the OSS releases.
|
||||
This release builds off of the 1.3.3 release of OSS InfluxDB. Please see the [OSS release notes](/influxdb/v1.3/about_the_project/releasenotes-changelog/) for more information about the OSS releases.
|
||||
|
||||
### Bugfixes
|
||||
|
||||
|
@ -626,4 +626,4 @@ Backup and restore has been updated to fix issues and refine existing capabiliti
|
|||
The Enterprise Web Console has officially been deprecated and will be eliminated entirely by the end of 2017.
|
||||
No additional features will be added and no additional bug fix releases are planned.
|
||||
|
||||
For browser-based access to InfluxDB Enterprise, [Chronograf](/chronograf/latest/introduction) is now the recommended tool to use.
|
||||
For browser-based access to InfluxDB Enterprise, [Chronograf](/{{< latest "chronograf" >}}/introduction) is now the recommended tool to use.
|
||||
|
|
|
@ -90,7 +90,7 @@ Data nodes hold the actual time series data. The minimum number of data nodes to
|
|||
|
||||
## Chronograf
|
||||
|
||||
[Chronograf](/chronograf/latest/introduction/getting-started/) is the user interface component of InfluxData’s TICK stack.
|
||||
[Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/) is the user interface component of InfluxData’s TICK stack.
|
||||
It makes owning the monitoring and alerting for your infrastructure easy to setup and maintain.
|
||||
It talks directly to the data and meta nodes over their HTTP protocols, which are bound by default to ports `8086` for data nodes and port `8091` for meta nodes.
|
||||
|
||||
|
|
|
@ -71,6 +71,6 @@ query capacity within the cluster.
|
|||
|
||||
Legacy user interface for the InfluxDB Enterprise.
|
||||
|
||||
This has been deprecated and the suggestion is to use [Chronograf](/chronograf/latest/introduction/).
|
||||
This has been deprecated and the suggestion is to use [Chronograf](/{{< latest "chronograf" >}}/introduction/).
|
||||
|
||||
If you are transitioning from the Enterprise Web Console to Chronograf and helpful [transition guide](/chronograf/latest/guides/transition-web-admin-interface/) is available.
|
||||
If you are transitioning from the Enterprise Web Console to Chronograf and helpful [transition guide](/{{< latest "chronograf" >}}/guides/transition-web-admin-interface/) is available.
|
||||
|
|
|
@ -69,7 +69,7 @@ you should set the lease-duration to a value greater than the aggregate executio
|
|||
|
||||
Based on the current way in which CQs are configured to execute, the way to address parallelism is by using
|
||||
Kapacitor for the more complex CQs that you are attempting to run.
|
||||
[See Kapacitor as a continuous query engine](/kapacitor/latest/guides/continuous_queries/).
|
||||
[See Kapacitor as a continuous query engine](/{{< latest "kapacitor" >}}/guides/continuous_queries/).
|
||||
However, you can keep the more simplistic and highly performant CQs within the database –
|
||||
but ensure that the lease duration is greater than their aggregate execution time to ensure that
|
||||
“extra” load is not being unnecessarily introduced on your cluster.
|
||||
|
|
|
@ -312,7 +312,7 @@ enterprise-meta-03:8091 1.x.y-c1.x.z
|
|||
```
|
||||
|
||||
|
||||
Next, verify that HTTPS is working by connecting to InfluxDB Enterprise with the [CLI tool](/influxdb/latest/tools/shell/):
|
||||
Next, verify that HTTPS is working by connecting to InfluxDB Enterprise with the [CLI tool](/{{< latest "influxdb" "v1" >}}/tools/shell/):
|
||||
```
|
||||
influx -ssl -unsafeSsl -host <domain_name>.com
|
||||
```
|
||||
|
@ -329,7 +329,7 @@ That's it! You've successfully set up HTTPS with InfluxDB Enterprise.
|
|||
|
||||
## Connect Telegraf to a secured InfluxDB Enterprise instance
|
||||
|
||||
Connecting [Telegraf](/telegraf/latest/) to an InfluxDB Enterprise instance that's using
|
||||
Connecting [Telegraf](/{{< latest "telegraf" >}}/) to an InfluxDB Enterprise instance that's using
|
||||
HTTPS requires some additional steps.
|
||||
|
||||
In Telegraf's configuration file (`/etc/telegraf/telegraf.conf`), under the OUTPUT PLUGINS section, edit the `urls`
|
||||
|
|
|
@ -208,7 +208,7 @@ You can do this with [ALTER RETENTION POLICY](/influxdb/v1.6/query_language/data
|
|||
Next, [rebalance](/enterprise_influxdb/v1.6/guides/rebalance/) your cluster manually to meet the desired
|
||||
replication factor for existing shards.
|
||||
|
||||
Finally, if you were using [Chronograf](/chronograf/latest/), you can
|
||||
Finally, if you were using [Chronograf](/{{< latest "chronograf" >}}/), you can
|
||||
add your Enterprise instance as a new data source. If you were not using
|
||||
[Chronograf](/chronograf/latest/introduction/installation/), we recommend going through
|
||||
[Chronograf](/{{< latest "chronograf" >}}/introduction/installation/), we recommend going through
|
||||
the installation instructions and using it as your primary management UI for the instance. -->
|
||||
|
|
|
@ -13,4 +13,4 @@ menu:
|
|||
Now that you've installed the meta nodes and data nodes, you are ready to install Chronograf
|
||||
to provide you with a user interface to access the InfluxDB Enterprise instance.
|
||||
|
||||
[Installation instruction for Chronograf](/chronograf/latest/introduction/installation/)
|
||||
[Installation instruction for Chronograf](/{{< latest "chronograf" >}}/introduction/installation/)
|
||||
|
|
|
@ -10,7 +10,7 @@ menu:
|
|||
---
|
||||
|
||||
InfluxDB Enterprise offers highly scalable clusters on your infrastructure
|
||||
and a management UI ([via Chronograf](https://docs.influxdata.com/chronograf/latest) for working with clusters.
|
||||
and a management UI ([via Chronograf](/{{< latest "chronograf" >}}) for working with clusters.
|
||||
The Production Installation process is designed for users looking to
|
||||
deploy InfluxDB Enterprise in a production environment.
|
||||
The following steps will get you up and running with the first essential component of
|
||||
|
|
|
@ -10,9 +10,9 @@ menu:
|
|||
parent: Introduction
|
||||
---
|
||||
|
||||
Now that you successfully [installed and set up](/enterprise_influxdb/v1.6/introduction/meta_node_installation/) InfluxDB Enterprise, use [Chronograf to setup your cluster as a data source.](/chronograf/latest/guides/monitor-an-influxenterprise-cluster/)
|
||||
Now that you successfully [installed and set up](/enterprise_influxdb/v1.6/introduction/meta_node_installation/) InfluxDB Enterprise, use [Chronograf to setup your cluster as a data source.](/{{< latest "chronograf" >}}/guides/monitor-an-influxenterprise-cluster/)
|
||||
|
||||
More details on leveraging [Chronograf and getting started are available.](/chronograf/latest/introduction/getting-started/)
|
||||
More details on leveraging [Chronograf and getting started are available.](/{{< latest "chronograf" >}}/introduction/getting-started/)
|
||||
|
||||
|
||||
### Where to from here?
|
||||
|
|
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue