Latest link fixes (#1375)

* products should not use latest references to themselves

* updated v2 links with influxdb namespace
pull/1387/head
Scott Anderson 2020-08-31 13:47:22 -06:00 committed by Scott Anderson
parent b86c16766e
commit be21841d7b
372 changed files with 1326 additions and 1326 deletions

View File

@ -615,9 +615,9 @@ menu:
### UI improvements
* When dashboard time range is changed, reset graphs that are zoomed in
* [Bar graph](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#bar) option added to dashboard
* [Bar graph](/chronograf/v1.6/troubleshooting/frequently-asked-questions/#bar) option added to dashboard
* Redesign source management table to be more intuitive
* Redesign [Line + Single Stat](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#line-stat) cells to appear more like a sparkline, and improve legibility
* Redesign [Line + Single Stat](/chronograf/v1.6/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](/{{< latest "chronograf" >}}/guides/transition-web-admin-interface/#writing-data)
* Add UI to the Data Explorer for [writing data to InfluxDB](/chronograf/v1.6/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](/{{< latest "chronograf" >}}/administration/configuration/#p-basepath)
* Fix infinite spinner when `/chronograf` is a [basepath](/chronograf/v1.6/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](/{{< latest "chronograf" >}}/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](/chronograf/v1.6/troubleshooting/frequently-asked-questions/#what-visualization-types-does-chronograf-support)
* Add a query for windows uptime - thank you, @brianbaker!
### Features
* Add log [event handler](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#what-kapacitor-event-handlers-are-supported-in-chronograf) - thank you, @mpchadwick!
* Add log [event handler](/chronograf/v1.6/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](/{{< latest "chronograf" >}}/guides/dashboard-template-variables/) dropdowns
* Add autocomplete functionality to [template variable](/chronograf/v1.6/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](/{{< latest "chronograf" >}}/guides/dashboard-template-variables/) manager more space efficient
* Make the [template variables](/chronograf/v1.6/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](/{{< latest "chronograf" >}}/administration/configuration/#p-basepath)
* Fix the link to home when using the [`--basepath` option](/chronograf/v1.6/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](/{{< latest "chronograf" >}}/administration/configuration/#p-basepath)
* Fix Authentication when using Chronograf with a set [basepath](/chronograf/v1.6/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](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/#line-stat) visualization type
* Show legend on [Line+Stat](/chronograf/v1.6/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](/{{< latest "chronograf" >}}/guides/advanced-kapacitor/#tickscript-management)
* Add support for enabling and disabling [TICKscripts that were created outside Chronograf](/chronograf/v1.6/guides/advanced-kapacitor/#tickscript-management)
* Allow users to delete Kapacitor configurations
### UI improvements

View File

@ -19,4 +19,4 @@ Enter the HTTP bind address of one of your cluster's meta nodes into that input
Note that the example above assumes that you do not have authentication enabled.
If you have authentication enabled, the form requires username and password information.
For details about monitoring InfluxDB Enterprise clusters, see [Monitoring InfluxDB Enterprise clusters](/{{< latest "chronograf" >}}/guides/monitoring-influxenterprise-clusters/).
For details about monitoring InfluxDB Enterprise clusters, see [Monitoring InfluxDB Enterprise clusters](/chronograf/v1.6/guides/monitoring-influxenterprise-clusters/).

View File

@ -78,7 +78,7 @@ Environment variable: `$BOLT_PATH`
#### `--canned-path=` | `-c`
The path to the directory of [canned dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards/) files.
The path to the directory of [canned dashboards](/chronograf/v1.6/guides/using-precreated-dashboards/) files.
Default value: `/usr/share/chronograf/canned`

View File

@ -47,12 +47,12 @@ It is neither created nor used in macOS.
## Enabling security, multi-organization, and multi-user support
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.
See [Managing security](/chronograf/v1.6/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](/{{< latest "chronograf" >}}/administration/managing-organizations)
* [Managing Chronograf users](/{{< latest "chronograf" >}}/administration/managing-chronograf-users)
* [Managing organizations](/chronograf/v1.6/administration/managing-organizations)
* [Managing Chronograf users](/chronograf/v1.6/administration/managing-chronograf-users)
<!-- TODO ## Configuring Chronograf for InfluxDB Enterprise clusters) -->

View File

@ -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](/{{< latest "chronograf" >}}/administration/managing-security/).
> ***Note:*** For details on Chronograf user authentication and management, see [Managing security](/chronograf/v1.6/administration/managing-security/).
**On this page:**
@ -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](/{{< latest "chronograf" >}}/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](/chronograf/v1.6/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

View File

@ -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](/{{< latest "chronograf" >}}/administration/managing-chronograf-users/).
> For information about the new user roles and SuperAdmin status, see [Managing Chronograf users](/chronograf/v1.6/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](/{{< latest "chronograf" >}}/administration/managing-chronograf-users/)
* [Managing security](/{{< latest "chronograf" >}}/administration/managing-security/)
* [Managing Chronograf users](/chronograf/v1.6/administration/managing-chronograf-users/)
* [Managing security](/chronograf/v1.6/administration/managing-security/)
## Mapping organizations

View File

@ -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](/{{< latest "chronograf" >}}/administration/user-management/) page for more information.
The `Admin` page supports both InfluxDB OSS users and InfluxDB Enterprise users; see the [User Management](/chronograf/v1.6/administration/user-management/) page for more information.
The `Admin` page allows users to:
* View, create, and delete users

View File

@ -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](/{{< latest "chronograf" >}}/introduction/getting-started/) to get up and running!
See [Getting Started](/chronograf/v1.6/introduction/getting-started/) to get up and running!

View File

@ -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](/{{< latest "chronograf" >}}/guides/create-a-dashboard/)
## [Creating dashboards](/chronograf/v1.6/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.

View File

@ -38,7 +38,7 @@ Chronograf supports the following event handlers:
* TCP
* VictorOps
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).
To configure a Kapacitor event handler in Chronograf, [install Kapacitor](/chronograf/v1.6/introduction/getting-started/#kapacitor-setup) and [connect it to Chronograf](/chronograf/v1.6/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](/{{< 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.
For more information, see [Kapacitor installation instructions](/chronograf/v1.6/introduction/getting-started/#kapacitor-setup) and how to [connect a Kapacitor instance](/chronograf/v1.6/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](/{{< latest "chronograf" >}}/guides/create-a-kapacitor-alert/).
Some event handlers allow users to customize event handler configurations per [alert rule](/chronograf/v1.6/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

View File

@ -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](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards) or create custom dashboards to meet your requirements.
Use Chronograf's [pre-created dashboards](/chronograf/v1.6/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](/{{< latest "chronograf" >}}/administration/configuration).
For more information, see [Configuring Chronograf](/chronograf/v1.6/administration/configuration).
## Build a 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](/{{< latest "chronograf" >}}/guides/visualization-types/). To choose a visualization type, click **Visualization** and select **Step-Plot Graph**.
Chronograf supports many different [visualization types](/chronograf/v1.6/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](/{{< latest "chronograf" >}}/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](/chronograf/v1.6/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](/{{< latest "chronograf" >}}/guides/dashboard-template-variables/) guide for more information.
See the [Dashboard Template Variables](/chronograf/v1.6/guides/dashboard-template-variables/) guide for more information.

View File

@ -26,13 +26,13 @@ This guide walks through creating a Chronograf alert rule that sends an alert me
## Requirements
[Getting started with Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/) offers step-by-step instructions for each of the following requirements:
[Getting started with Chronograf](/chronograf/v1.6/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](/{{< 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.
* [Create a Kapacitor connection in Chronograf](/chronograf/v1.6/introduction/getting-started/#4-connect-chronograf-to-kapacitor).
* Slack is available and configured as an [event handler](/chronograf/v1.6/troubleshooting/frequently-asked-questions/#what-kapacitor-event-handlers-are-supported-in-chronograf) in Chronograf.
See the [Configuring Kapacitor Event Handlers](/chronograf/v1.6/guides/configuring-alert-endpoints/) guide for detailed configuration instructions.
## Configuring Chronograf alert rules

View File

@ -23,7 +23,7 @@ See the InfluxDB Enterprise documentation for
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](/{{< 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.
It is possible to store the monitoring data in your cluster and [connect the cluster to Chronograf](/chronograf/v1.6/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.
@ -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](/{{< latest "chronograf" >}}/guides/create-a-dashboard/) guide for more information.
See the [Creating Chronograf dashboards](/chronograf/v1.6/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.

View File

@ -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](/{{< latest "chronograf" >}}/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](/chronograf/v1.6/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](/{{< latest "chronograf" >}}/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](/chronograf/v1.6/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.

View File

@ -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](/{{< latest "chronograf" >}}/introduction/installation/)
## [Installing Chronograf](/chronograf/v1.6/introduction/installation/)
[Installing Chronograf](/{{< latest "chronograf" >}}/introduction/installation/) lists the requirements for installing, starting, and configuring Chronograf.
[Installing Chronograf](/chronograf/v1.6/introduction/installation/) lists the requirements for installing, starting, and configuring Chronograf.
## Getting Started
[Getting started with Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/) gets you up and running with Chronograf with as little configuration and code as possible.
[Getting started with Chronograf](/chronograf/v1.6/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.

View File

@ -10,18 +10,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](/{{< latest "chronograf" >}}/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](/chronograf/v1.6/introduction/installation), get started with key features using the guides below.
### Data visualization
* 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/).
* Use pre-created [pre-created dashboards](/chronograf/v1.6/guides/using-precreated-dashboards/) to monitor your application data or [create your own dashboards](/chronograf/v1.6/guides/create-a-dashboard/).
* Customize dashboards using [template variables](/chronograf/v1.6/guides/dashboard-template-variables/).
### Alerting
* [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.
* [Create alert rules](/chronograf/v1.6/guides/create-alert-rules/) to generate threshold, relative, and deadman alerts on your data.
* [View all active alerts](/chronograf/v1.6/guides/create-alert-rules/#step-2-view-the-alerts) on an alert dashboard.
* Use [alert endpoints](/chronograf/v1.6/guides/configuring-alert-endpoints/) in Chronograf to send alert messages to specific URLs and applications.
### Infrastructure monitoring
* [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.
* [View all hosts](/chronograf/v1.6/guides/monitoring-influxenterprise-clusters/#step-4-explore-the-monitoring-data-in-chronograf) and their statuses in your infrastructure.
* [Use pre-created dashboards](/chronograf/v1.6/guides/using-precreated-dashboards/) to monitor your applications.

View File

@ -9,4 +9,4 @@ menu:
Follow the link below to access Chronograf's FAQ.
## [Frequently Asked Questions](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/)
## [Frequently Asked Questions](/chronograf/v1.6/troubleshooting/frequently-asked-questions/)

View File

@ -19,4 +19,4 @@ Enter the HTTP bind address of one of your cluster's meta nodes into that input
Note that the example above assumes that you do not have authentication enabled.
If you have authentication enabled, the form requires username and password information.
For more details about monitoring an InfluxDB Enterprise cluster, see the [Monitor an InfluxDB Enterprise Cluster](/{{< latest "chronograf" >}}/guides/monitoring-influxenterprise-clusters/) guide.
For more details about monitoring an InfluxDB Enterprise cluster, see the [Monitor an InfluxDB Enterprise Cluster](/chronograf/v1.6/guides/monitoring-influxenterprise-clusters/) guide.

View File

@ -836,9 +836,9 @@ menu:
### UI improvements
* When dashboard time range is changed, reset graphs that are zoomed in
* [Bar graph](/{{< latest "chronograf" >}}/guides/visualization-types/#bar-graph) option added to dashboard
* [Bar graph](/chronograf/v1.7/guides/visualization-types/#bar-graph) option added to dashboard
* Redesign source management table to be more intuitive
* Redesign [Line + Single Stat](/{{< latest "chronograf" >}}/guides/visualization-types/#line-graph-single-stat) cells to appear more like a sparkline, and improve legibility
* Redesign [Line + Single Stat](/chronograf/v1.7/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](/{{< latest "chronograf" >}}/guides/querying-data/)
* Add UI to the Data Explorer for [writing data to InfluxDB](/chronograf/v1.7/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](/{{< latest "chronograf" >}}/administration/config-options/#p-basepath)
* Fix infinite spinner when `/chronograf` is a [basepath](/chronograf/v1.7/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](/{{< latest "chronograf" >}}/guides/visualization-types)
* Allow users to click the add query button after selecting singleStat as the [visualization type](/chronograf/v1.7/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](/{{< latest "chronograf" >}}/guides/dashboard-template-variables) dropdowns
* Add autocomplete functionality to [template variable](/chronograf/v1.7/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](/{{< latest "chronograf" >}}/guides/dashboard-template-variables) manager more space efficient
* Make the [template variables](/chronograf/v1.7/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](/{{< latest "chronograf" >}}/administration/config-options/#p-basepath)
* Fix the link to home when using the [`--basepath` option](/chronograf/v1.7/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](/{{< latest "chronograf" >}}/administration/config-options/#p-basepath)
* Fix Authentication when using Chronograf with a set [basepath](/chronograf/v1.7/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](/{{< latest "chronograf" >}}/guides/visualization-types/#line-graph-single-stat) visualization type
* Show legend on [Line+Stat](/chronograf/v1.7/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](/{{< latest "chronograf" >}}/guides/advanced-kapacitor/#tickscript-management)
* Add support for enabling and disabling [TICKscripts that were created outside Chronograf](/chronograf/v1.7/guides/advanced-kapacitor/#tickscript-management)
* Allow users to delete Kapacitor configurations
### UI improvements

View File

@ -19,4 +19,4 @@ Enter the HTTP bind address of one of your cluster's meta nodes into that input
Note that the example above assumes that you do not have authentication enabled.
If you have authentication enabled, the form requires username and password information.
For details about monitoring InfluxEnterprise clusters, see [Monitoring InfluxDB Enterprise clusters](/{{< latest "chronograf" >}}/guides/monitoring-influxenterprise-clusters).
For details about monitoring InfluxEnterprise clusters, see [Monitoring InfluxDB Enterprise clusters](/chronograf/v1.7/guides/monitoring-influxenterprise-clusters).

View File

@ -78,7 +78,7 @@ Environment variable: `$BOLT_PATH`
#### `--canned-path=` | `-c`
The path to the directory of [canned dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards) files.
The path to the directory of [canned dashboards](/chronograf/v1.7/guides/using-precreated-dashboards) files.
Default value: `/usr/share/chronograf/canned`

View File

@ -39,7 +39,7 @@ To create an InfluxDB connection in the Chronograf UI:
* **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](/{{< latest "chronograf" >}}/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](/chronograf/v1.7/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.

View File

@ -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](/{{< latest "chronograf" >}}/administration/managing-security/).
> ***Note:*** For details on Chronograf user authentication and management, see [Managing security](/chronograf/v1.7/administration/managing-security/).
**On this page:**

View File

@ -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](/{{< latest "chronograf" >}}/administration/managing-organizations/)
> and [users](/{{< latest "chronograf" >}}/administration/managing-influxdb-users/).
> You can then set up [multiple organizations](/chronograf/v1.7/administration/managing-organizations/)
> and [users](/chronograf/v1.7/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.

View File

@ -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](/{{< latest "chronograf" >}}/administration/managing-chronograf-users/) page for more information.
The `Admin` page supports both InfluxDB OSS users and InfluxDB Enterprise users; see [Managing Chronograf Users](/chronograf/v1.7/administration/managing-chronograf-users/) page for more information.
The `Admin` page allows users to:
* View, create, and delete users

View File

@ -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](/{{< latest "chronograf" >}}/introduction/getting-started/) to get up and running!
See [Getting Started](/chronograf/v1.7/introduction/getting-started/) to get up and running!

View File

@ -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](/{{< latest "chronograf" >}}/guides/create-a-dashboard/)
## [Creating dashboards](/chronograf/v1.7/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.

View File

@ -50,7 +50,7 @@ You must have a connected Kapacitor instance to access the configurations.
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](/{{< latest "chronograf" >}}/guides/create-a-kapacitor-alert/).
Some event handlers allow users to customize event handler configurations per [alert rule](/chronograf/v1.7/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/{{< latest "chronograf" >}}/g-eventhandlers-hipchattoken.png)
![HipChat token](/img/chronograf/1-6-g-eventhandlers-hipchattoken.png)
### Kafka

View File

@ -10,7 +10,7 @@ menu:
Chronograf offers a complete dashboard solution for visualizing your data and monitoring your infrastructure:
* 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.
* View [pre-created dashboards](/chronograf/v1.7/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](/{{< latest "chronograf" >}}/administration/configuration).
For more information, see [Configuring Chronograf](/chronograf/v1.7/administration/configuration).
## Build a 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](/{{< latest "chronograf" >}}/guides/visualization-types/). To choose a visualization type, click **Visualization** and select **Step-Plot Graph**.
Chronograf supports many different [visualization types](/chronograf/v1.7/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](/{{< latest "chronograf" >}}/guides/visualization-types/).
These tips only apply to the line, stacked, step-plot, and line+stat [visualization types](/chronograf/v1.7/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](/{{< latest "chronograf" >}}/guides/dashboard-template-variables/) guide for more information.
See the [Dashboard Template Variables](/chronograf/v1.7/guides/dashboard-template-variables/) guide for more information.

View File

@ -26,13 +26,13 @@ This guide walks through creating a Chronograf alert rule that sends an alert me
## Requirements
[Getting started with Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/) offers step-by-step instructions for each of the following requirements:
[Getting started with Chronograf](/chronograf/v1.7/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](/{{< 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.
* [Create a Kapacitor connection in Chronograf](/chronograf/v1.7/introduction/getting-started/#4-connect-chronograf-to-kapacitor).
* Slack is available and configured as an [event handler](/chronograf/v1.7/troubleshooting/frequently-asked-questions/#what-kapacitor-event-handlers-are-supported-in-chronograf) in Chronograf.
See the [Configuring Kapacitor Event Handlers](/chronograf/v1.7/guides/configuring-alert-endpoints/) guide for detailed configuration instructions.
## Configuring Chronograf alert rules

View File

@ -23,7 +23,7 @@ See the InfluxEnterprise documentation for
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](/{{< 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.
It is possible to store the monitoring data in your cluster and [connect the cluster to Chronograf](/chronograf/v1.7/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.
@ -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](/{{< latest "chronograf" >}}/guides/create-a-dashboard/) guide for more information.
See the [Creating Chronograf dashboards](/chronograf/v1.7/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.

View File

@ -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](/{{< latest "chronograf" >}}/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](/chronograf/v1.7/guides/visualization-types/) for your query.
To open the **Data Explorer**, click the **Explore** icon in the navigation bar:
@ -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](/{{< latest "chronograf" >}}/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](/chronograf/v1.7/guides/visualization-types/).
## Add queries to dashboards

View File

@ -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](/{{< latest "chronograf" >}}/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](/chronograf/v1.7/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](/{{< latest "chronograf" >}}/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](/chronograf/v1.7/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.

View File

@ -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](/{{< latest "chronograf" >}}/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](/chronograf/v1.7/querying-data) .
[Visualization Type selector](/img/chronograf/1-6-viz-types-selector.png)

View File

@ -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](/{{< latest "chronograf" >}}/introduction/installation/)
## [Installing Chronograf](/chronograf/v1.7/introduction/installation/)
[Installing Chronograf](/{{< latest "chronograf" >}}/introduction/installation/) lists the requirements for installing, starting, and configuring Chronograf.
[Installing Chronograf](/chronograf/v1.7/introduction/installation/) lists the requirements for installing, starting, and configuring Chronograf.
## Getting Started
[Getting started with Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/) gets you up and running with Chronograf with as little configuration and code as possible.
[Getting started with Chronograf](/chronograf/v1.7/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.

View File

@ -10,18 +10,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](/{{< latest "chronograf" >}}/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](/chronograf/v1.7/introduction/installation), get started with key features using the guides below.
### Data visualization
* 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/).
* Investigate your data by building queries using the [Data Explorer](/chronograf/v1.7/guides/querying-data/).
* Use [pre-created dashboards](/chronograf/v1.7/guides/using-precreated-dashboards/) to monitor your application data or [create your own dashboards](/chronograf/v1.7/guides/create-a-dashboard/).
* Customize dashboards using [template variables](/chronograf/v1.7/guides/dashboard-template-variables/).
### Alerting
* [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.
* [Create alert rules](/chronograf/v1.7/guides/create-alert-rules/) to generate threshold, relative, and deadman alerts on your data.
* [View all active alerts](/chronograf/v1.7/guides/create-alert-rules/#step-2-view-the-alerts) on an alert dashboard.
* Use [alert endpoints](/chronograf/v1.7/guides/configuring-alert-endpoints/) in Chronograf to send alert messages to specific URLs and applications.
### Infrastructure monitoring
* [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.
* [View all hosts](/chronograf/v1.7/guides/monitoring-influxenterprise-clusters/#step-4-explore-the-monitoring-data-in-chronograf) and their statuses in your infrastructure.
* [Use pre-created dashboards](/chronograf/v1.7/guides/using-precreated-dashboards/) to monitor your applications.

View File

@ -9,4 +9,4 @@ menu:
Follow the link below to access Chronograf's FAQ.
## [Frequently Asked Questions](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/)
## [Frequently Asked Questions](/chronograf/v1.7/troubleshooting/frequently-asked-questions/)

View File

@ -19,4 +19,4 @@ Enter the HTTP bind address of one of your cluster's meta nodes into that input
Note that the example above assumes that you do not have authentication enabled.
If you have authentication enabled, the form requires username and password information.
For more details about monitoring an InfluxEnterprise cluster, see the [Monitor an InfluxEnterprise Cluster](/{{< latest "chronograf" >}}/guides/monitoring-influxenterprise-clusters/) guide.
For more details about monitoring an InfluxEnterprise cluster, see the [Monitor an InfluxEnterprise Cluster](/chronograf/v1.7/guides/monitoring-influxenterprise-clusters/) guide.

View File

@ -935,9 +935,9 @@ menu:
### UI improvements
* When dashboard time range is changed, reset graphs that are zoomed in
* [Bar graph](/{{< latest "chronograf" >}}/guides/visualization-types/#bar-graph) option added to dashboard
* [Bar graph](/chronograf/v1.8/guides/visualization-types/#bar-graph) option added to dashboard
* Redesign source management table to be more intuitive
* Redesign [Line + Single Stat](/{{< latest "chronograf" >}}/guides/visualization-types/#line-graph-single-stat) cells to appear more like a sparkline, and improve legibility
* Redesign [Line + Single Stat](/chronograf/v1.8/guides/visualization-types/#line-graph-single-stat) cells to appear more like a sparkline, and improve legibility
## v1.3.2.0 [2017-06-05]
@ -953,7 +953,7 @@ menu:
### Features
* Add UI to the Data Explorer for [writing data to InfluxDB](/{{< latest "chronograf" >}}/guides/querying-data/)
* Add UI to the Data Explorer for [writing data to InfluxDB](/chronograf/v1.8/guides/querying-data/)
### UI improvements
@ -973,26 +973,26 @@ In versions 1.3.1+, installing a new version of Chronograf automatically clears
### Bug fixes
* Fix infinite spinner when `/chronograf` is a [basepath](/{{< latest "chronograf" >}}/administration/config-options/#p-basepath)
* Fix infinite spinner when `/chronograf` is a [basepath](/chronograf/v1.8/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](/{{< latest "chronograf" >}}/guides/visualization-types)
* Allow users to click the add query button after selecting singleStat as the [visualization type](/chronograf/v1.8/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](/{{< latest "chronograf" >}}/guides/dashboard-template-variables) dropdowns
* Add autocomplete functionality to [template variable](/chronograf/v1.8/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](/{{< latest "chronograf" >}}/guides/dashboard-template-variables) manager more space efficient
* Make the [template variables](/chronograf/v1.8/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
@ -1002,25 +1002,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](/{{< latest "chronograf" >}}/administration/config-options/#p-basepath)
* Fix the link to home when using the [`--basepath` option](/chronograf/v1.8/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](/{{< latest "chronograf" >}}/administration/config-options/#p-basepath)
* Fix Authentication when using Chronograf with a set [basepath](/chronograf/v1.8/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](/{{< latest "chronograf" >}}/guides/visualization-types/#line-graph-single-stat) visualization type
* Show legend on [Line+Stat](/chronograf/v1.8/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](/{{< latest "chronograf" >}}/guides/advanced-kapacitor/#tickscript-management)
* Add support for enabling and disabling [TICKscripts that were created outside Chronograf](/chronograf/v1.8/guides/advanced-kapacitor/#tickscript-management)
* Allow users to delete Kapacitor configurations
### UI improvements

View File

@ -95,7 +95,7 @@ Environment variable: `$BOLT_PATH`
#### `--canned-path=` | `-c`
The path to the directory of [canned dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards) files.
The path to the directory of [canned dashboards](/chronograf/v1.8/guides/using-precreated-dashboards) files.
Default value: `/usr/share/chronograf/canned`

View File

@ -39,7 +39,7 @@ To create an InfluxDB connection in the Chronograf UI:
* **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](/{{< latest "chronograf" >}}/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](/chronograf/v1.8/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.

View File

@ -14,7 +14,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](/{{< latest "chronograf" >}}/administration/managing-security/).
> ***Note:*** For details on Chronograf user authentication and management, see [Managing security](/chronograf/v1.8/administration/managing-security/).
**On this page:**

View File

@ -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](/{{< latest "chronograf" >}}/administration/managing-organizations/)
> and [users](/{{< latest "chronograf" >}}/administration/managing-influxdb-users/).
> You can then set up [multiple organizations](/chronograf/v1.8/administration/managing-organizations/)
> and [users](/chronograf/v1.8/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.

View File

@ -50,7 +50,7 @@ You must have a connected Kapacitor instance to access the configurations.
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](/{{< latest "chronograf" >}}/guides/create-a-kapacitor-alert/).
Some event handlers allow users to customize event handler configurations per [alert rule](/chronograf/v1.8/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/{{< latest "chronograf" >}}/g-eventhandlers-hipchattoken.png)
![HipChat token](/img/chronograf/1-6-g-eventhandlers-hipchattoken.png)
### Kafka

View File

@ -10,7 +10,7 @@ menu:
Chronograf offers a complete dashboard solution for visualizing your data and monitoring your infrastructure:
* 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.
* View [pre-created dashboards](/chronograf/v1.8/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](/{{< latest "chronograf" >}}/administration/configuration).
For more information, see [Configuring Chronograf](/chronograf/v1.8/administration/configuration).
## Build a 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](/{{< latest "chronograf" >}}/guides/visualization-types/). To choose a visualization type, click **Visualization** and select **Step-Plot Graph**.
Chronograf supports many different [visualization types](/chronograf/v1.8/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](/{{< latest "chronograf" >}}/guides/visualization-types/).
These tips only apply to the line, stacked, step-plot, and line+stat [visualization types](/chronograf/v1.8/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](/{{< latest "chronograf" >}}/guides/dashboard-template-variables/) guide for more information.
See the [Dashboard Template Variables](/chronograf/v1.8/guides/dashboard-template-variables/) guide for more information.

View File

@ -27,13 +27,13 @@ This guide walks through creating a Chronograf alert rule that sends an alert me
## Requirements
[Getting started with Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/) offers step-by-step instructions for each of the following requirements:
[Getting started with Chronograf](/chronograf/v1.8/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](/{{< 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.
* [Create a Kapacitor connection in Chronograf](/chronograf/v1.8/introduction/getting-started/#4-connect-chronograf-to-kapacitor).
* Slack is available and configured as an [event handler](/chronograf/v1.8/troubleshooting/frequently-asked-questions/#what-kapacitor-event-handlers-are-supported-in-chronograf) in Chronograf.
See the [Configuring Kapacitor Event Handlers](/chronograf/v1.8/guides/configuring-alert-endpoints/) guide for detailed configuration instructions.
## Configure Chronograf alert rules

View File

@ -23,7 +23,7 @@ See the InfluxEnterprise documentation for
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](/{{< 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.
It is possible to store the monitoring data in your cluster and [connect the cluster to Chronograf](/chronograf/v1.8/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.
@ -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](/{{< latest "chronograf" >}}/guides/create-a-dashboard/) guide for more information.
See the [Creating Chronograf dashboards](/chronograf/v1.8/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 Chronograf to use those data for monitoring and visualization purposes.

View File

@ -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](/{{< latest "chronograf" >}}/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](/chronograf/v1.8/guides/visualization-types/) for your query.
To open the **Data Explorer**, click the **Explore** icon in the navigation bar:
@ -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](/{{< latest "chronograf" >}}/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](/chronograf/v1.8/guides/visualization-types/).
## Add queries to dashboards

View File

@ -14,7 +14,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](/{{< latest "chronograf" >}}/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](/chronograf/v1.8/guides/create-a-dashboard/#dashboard-templates).
## Requirements
@ -38,7 +38,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](/{{< latest "chronograf" >}}/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](/chronograf/v1.8/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.

View File

@ -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](/{{< latest "chronograf" >}}/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](/chronograf/v1.8/introduction/installation), get started with key features using the guides below.
### Data visualization
* 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/).
* Investigate your data by building queries using the [Data Explorer](/chronograf/v1.8/guides/querying-data/).
* Use [pre-created dashboards](/chronograf/v1.8/guides/using-precreated-dashboards/) to monitor your application data or [create your own dashboards](/chronograf/v1.8/guides/create-a-dashboard/).
* Customize dashboards using [template variables](/chronograf/v1.8/guides/dashboard-template-variables/).
### Alerting
* [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.
* [Create alert rules](/chronograf/v1.8/guides/create-alert-rules/) to generate threshold, relative, and deadman alerts on your data.
* [View all active alerts](/chronograf/v1.8/guides/create-alert-rules/#step-2-view-the-alerts) on an alert dashboard.
* Use [alert endpoints](/chronograf/v1.8/guides/configuring-alert-endpoints/) in Chronograf to send alert messages to specific URLs and applications.
### Infrastructure monitoring
* [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.
* [View all hosts](/chronograf/v1.8/guides/monitoring-influxenterprise-clusters/#step-4-explore-the-monitoring-data-in-chronograf) and their statuses in your infrastructure.
* [Use pre-created dashboards](/chronograf/v1.8/guides/using-precreated-dashboards/) to monitor your applications.

View File

@ -9,4 +9,4 @@ menu:
Follow the link below to access Chronograf's FAQ.
## [Frequently Asked Questions](/{{< latest "chronograf" >}}/troubleshooting/frequently-asked-questions/)
## [Frequently Asked Questions](/chronograf/v1.8/troubleshooting/frequently-asked-questions/)

View File

@ -20,4 +20,4 @@ Enter the HTTP bind address of one of your cluster's meta nodes into that input
Note that the example above assumes that you do not have authentication enabled.
If you have authentication enabled, the form requires username and password information.
For more details about monitoring an InfluxEnterprise cluster, see the [Monitor an InfluxEnterprise Cluster](/{{< latest "chronograf" >}}/guides/monitoring-influxenterprise-clusters/) guide.
For more details about monitoring an InfluxEnterprise cluster, see the [Monitor an InfluxEnterprise Cluster](/chronograf/v1.8/guides/monitoring-influxenterprise-clusters/) guide.

View File

@ -32,7 +32,7 @@ InfluxDB shell 1.3.x
* The InfluxDB HTTP API runs on port `8086` by default.
Therefore, `influx` will connect to port `8086` and `localhost` by default.
If you need to alter these defaults, run `influx --help`.
* The [`-precision` argument](/{{< latest "influxdb" "v1" >}}/tools/shell/#influx-arguments) specifies the format/precision of any returned timestamps.
* The [`-precision` argument](/influxdb/v1.3/tools/shell/#influx-arguments) specifies the format/precision of any returned timestamps.
In the example above, `rfc3339` tells InfluxDB to return timestamps in [RFC3339 format](https://www.ietf.org/rfc/rfc3339.txt) (`YYYY-MM-DDTHH:MM:SS.nnnnnnnnnZ`).
The command line is now ready to take input in the form of the Influx Query Language (a.k.a InfluxQL) statements.

View File

@ -32,7 +32,7 @@ InfluxDB shell 1.4.x
* The InfluxDB HTTP API runs on port `8086` by default.
Therefore, `influx` will connect to port `8086` and `localhost` by default.
If you need to alter these defaults, run `influx --help`.
* The [`-precision` argument](/{{< latest "influxdb" "v1" >}}/tools/shell/#influx-arguments) specifies the format/precision of any returned timestamps.
* The [`-precision` argument](/influxdb/v1.4/tools/shell/#influx-arguments) specifies the format/precision of any returned timestamps.
In the example above, `rfc3339` tells InfluxDB to return timestamps in [RFC3339 format](https://www.ietf.org/rfc/rfc3339.txt) (`YYYY-MM-DDTHH:MM:SS.nnnnnnnnnZ`).
The command line is now ready to take input in the form of the Influx Query Language (a.k.a InfluxQL) statements.

View File

@ -32,7 +32,7 @@ InfluxDB shell 1.4.x
* The InfluxDB HTTP API runs on port `8086` by default.
Therefore, `influx` will connect to port `8086` and `localhost` by default.
If you need to alter these defaults, run `influx --help`.
* The [`-precision` argument](/{{< latest "influxdb" "v1" >}}/tools/shell/#influx-arguments) specifies the format/precision of any returned timestamps.
* The [`-precision` argument](/influxdb/v1.5/tools/shell/#influx-arguments) specifies the format/precision of any returned timestamps.
In the example above, `rfc3339` tells InfluxDB to return timestamps in [RFC3339 format](https://www.ietf.org/rfc/rfc3339.txt) (`YYYY-MM-DDTHH:MM:SS.nnnnnnnnnZ`).
The command line is now ready to take input in the form of the Influx Query Language (a.k.a InfluxQL) statements.

View File

@ -10,18 +10,18 @@ menu:
InfluxData supports the following protocols for interacting with InfluxDB:
### [CollectD](/{{< latest "influxdb" "v1" >}}/supported_protocols/collectd)
### [CollectD](/influxdb/v1.5/supported_protocols/collectd)
Using the collectd input, InfluxDB can accept data transmitted in collectd native format. This data is transmitted over UDP.
### [Graphite](/{{< latest "influxdb" "v1" >}}/supported_protocols/graphite)
### [Graphite](/influxdb/v1.5/supported_protocols/graphite)
The Graphite plugin allows measurements to be saved using the Graphite line protocol. By default, enabling the Graphite plugin will allow you to collect metrics and store them using the metric name as the measurement.
### [OpenTSDB](/{{< latest "influxdb" "v1" >}}/supported_protocols/opentsdb)
### [OpenTSDB](/influxdb/v1.5/supported_protocols/opentsdb)
InfluxDB supports both the telnet and HTTP OpenTSDB protocol.
This means that InfluxDB can act as a drop-in replacement for your OpenTSDB system.
### [Prometheus](/{{< latest "influxdb" "v1" >}}/supported_protocols/prometheus)
### [Prometheus](/influxdb/v1.5/supported_protocols/prometheus)
InfluxDB provides native support for the Prometheus read and write API to convert remote reads and writes to InfluxDB queries and endpoints.
### [UDP](/{{< latest "influxdb" "v1" >}}/supported_protocols/udp)
### [UDP](/influxdb/v1.5/supported_protocols/udp)
UDP (User Datagram Protocol) can be used to write to InfluxDB. The CollectD input accepts data transmitted in collectd native format over UDP.

View File

@ -15,7 +15,7 @@ The [collectd](https://collectd.org) input allows InfluxDB to accept data transm
## A note on UDP/IP buffer sizes
If you're running Linux or FreeBSD, please adjust your operating system UDP buffer size limit, [see here for more details.](/{{< latest "influxdb" "v1" >}}/supported_protocols/udp/#a-note-on-udpip-os-buffer-sizes)
If you're running Linux or FreeBSD, please adjust your operating system UDP buffer size limit, [see here for more details.](/influxdb/v1.5/supported_protocols/udp/#a-note-on-udpip-os-buffer-sizes)
## Configuration

View File

@ -32,7 +32,7 @@ InfluxDB shell 1.4.x
* The InfluxDB HTTP API runs on port `8086` by default.
Therefore, `influx` will connect to port `8086` and `localhost` by default.
If you need to alter these defaults, run `influx --help`.
* The [`-precision` argument](/{{< latest "influxdb" "v1" >}}/tools/shell/#influx-arguments) specifies the format/precision of any returned timestamps.
* The [`-precision` argument](/influxdb/v1.6/tools/shell/#influx-arguments) specifies the format/precision of any returned timestamps.
In the example above, `rfc3339` tells InfluxDB to return timestamps in [RFC3339 format](https://www.ietf.org/rfc/rfc3339.txt) (`YYYY-MM-DDTHH:MM:SS.nnnnnnnnnZ`).
The command line is now ready to take input in the form of the Influx Query Language (a.k.a InfluxQL) statements.

View File

@ -10,18 +10,18 @@ menu:
InfluxData supports the following protocols for interacting with InfluxDB:
### [CollectD](/{{< latest "influxdb" "v1" >}}/supported_protocols/collectd)
### [CollectD](/influxdb/v1.6/supported_protocols/collectd)
Using the collectd input, InfluxDB can accept data transmitted in collectd native format. This data is transmitted over UDP.
### [Graphite](/{{< latest "influxdb" "v1" >}}/supported_protocols/graphite)
### [Graphite](/influxdb/v1.6/supported_protocols/graphite)
The Graphite plugin allows measurements to be saved using the Graphite line protocol. By default, enabling the Graphite plugin will allow you to collect metrics and store them using the metric name as the measurement.
### [OpenTSDB](/{{< latest "influxdb" "v1" >}}/supported_protocols/opentsdb)
### [OpenTSDB](/influxdb/v1.6/supported_protocols/opentsdb)
InfluxDB supports both the telnet and HTTP OpenTSDB protocol.
This means that InfluxDB can act as a drop-in replacement for your OpenTSDB system.
### [Prometheus](/{{< latest "influxdb" "v1" >}}/supported_protocols/prometheus)
### [Prometheus](/influxdb/v1.6/supported_protocols/prometheus)
InfluxDB provides native support for the Prometheus read and write API to convert remote reads and writes to InfluxDB queries and endpoints.
### [UDP](/{{< latest "influxdb" "v1" >}}/supported_protocols/udp)
### [UDP](/influxdb/v1.6/supported_protocols/udp)
UDP (User Datagram Protocol) can be used to write to InfluxDB. The CollectD input accepts data transmitted in collectd native format over UDP.

View File

@ -15,7 +15,7 @@ The [collectd](https://collectd.org) input allows InfluxDB to accept data transm
## A note on UDP/IP buffer sizes
If you're running Linux or FreeBSD, please adjust your operating system UDP buffer size limit, [see here for more details.](/{{< latest "influxdb" "v1" >}}/supported_protocols/udp/#a-note-on-udpip-os-buffer-sizes)
If you're running Linux or FreeBSD, please adjust your operating system UDP buffer size limit, [see here for more details.](/influxdb/v1.6/supported_protocols/udp/#a-note-on-udpip-os-buffer-sizes)
## Configuration

View File

@ -28,4 +28,4 @@ It compiles into a single binary with no external dependencies.
* Continuous queries automatically compute aggregate data to make frequent queries more efficient.
The open source edition of InfluxDB runs on a single node.
If you require high availability to eliminate a single point of failure, consider the [InfluxDB Enterprise Edition](/{{< latest "influxdb" "v1" >}}/high_availability/).
If you require high availability to eliminate a single point of failure, consider the [InfluxDB Enterprise Edition](/influxdb/v1.7/high_availability/).

View File

@ -9,7 +9,7 @@ menu:
---
Flux is a functional data scripting language designed for querying, analyzing, and acting on time series data.
Its takes the power of [InfluxQL](/{{< latest "influxdb" "v1" >}}/query_language/spec/) and the functionality of [TICKscript](/{{< latest "kapacitor" >}}/tick/introduction/) and combines them into a single, unified syntax.
Its takes the power of [InfluxQL](/influxdb/v1.7/query_language/spec/) and the functionality of [TICKscript](/{{< latest "kapacitor" >}}/tick/introduction/) and combines them into a single, unified syntax.
> Flux v0.50 is a technical preview included with [InfluxDB v1.7](/influxdb/v1.7).
> It is still in active development and many functions provided by InfluxQL and TICKscript

View File

@ -28,7 +28,7 @@ interactive Flux Read-Eval-Print-Loop (REPL) allowing you to write and run Flux
---
_For information about downloading and installing InfluxDB, see [InfluxDB installation](/{{< latest "influxdb" "v1" >}}/introduction/installation)._
_For information about downloading and installing InfluxDB, see [InfluxDB installation](/influxdb/v1.7/introduction/installation)._
---

View File

@ -32,7 +32,7 @@ InfluxDB shell 1.4.x
* The InfluxDB API runs on port `8086` by default.
Therefore, `influx` will connect to port `8086` and `localhost` by default.
If you need to alter these defaults, run `influx --help`.
* The [`-precision` argument](/{{< latest "influxdb" "v1" >}}/tools/shell/#influx-options) specifies the format/precision of any returned timestamps.
* The [`-precision` argument](/influxdb/v1.7/tools/shell/#influx-options) specifies the format/precision of any returned timestamps.
In the example above, `rfc3339` tells InfluxDB to return timestamps in [RFC3339 format](https://www.ietf.org/rfc/rfc3339.txt) (`YYYY-MM-DDTHH:MM:SS.nnnnnnnnnZ`).
The command line is now ready to take input in the form of the Influx Query Language (a.k.a InfluxQL) statements.

View File

@ -15,7 +15,7 @@ The [collectd](https://collectd.org) input allows InfluxDB to accept data transm
## A note on UDP/IP buffer sizes
If you're running Linux or FreeBSD, please adjust your operating system UDP buffer size limit, [see here for more details.](/{{< latest "influxdb" "v1" >}}/supported_protocols/udp/#a-note-on-udpip-os-buffer-sizes)
If you're running Linux or FreeBSD, please adjust your operating system UDP buffer size limit, [see here for more details.](/influxdb/v1.7/supported_protocols/udp/#a-note-on-udpip-os-buffer-sizes)
## Configuration

View File

@ -810,7 +810,7 @@ Errors are returned in JSON.
| 400 Bad Request | Unacceptable request. Can occur with an InfluxDB line protocol syntax error or if a user attempts to write values to a field that previously accepted a different value type. The returned JSON offers further information. |
| 401 Unauthorized | Unacceptable request. Can occur with invalid authentication credentials. |
| 404 Not Found | Unacceptable request. Can occur if a user attempts to write to a database that does not exist. The returned JSON offers further information. |
| 413 Request Entity Too Large | Unaccetable request. It will occur if the payload of the POST request is bigger than the maximum size allowed. See [`max-body-size`](/{{< latest "influxdb" "v1" >}}/administration/config/#max-body-size-25000000) parameter for more details.
| 413 Request Entity Too Large | Unaccetable request. It will occur if the payload of the POST request is bigger than the maximum size allowed. See [`max-body-size`](/influxdb/v1.7/administration/config/#max-body-size-25000000) parameter for more details.
| 500 Internal Server Error | The system is overloaded or significantly impaired. Can occur if a user attempts to write to a retention policy that does not exist. The returned JSON offers further information. |
#### Examples

View File

@ -19,9 +19,9 @@ influxd [[command] [arguments]]
## Commands
| Command | Description |
|-------------------------------------------------------|----------------------------------------------------------|
| [backup](/{{< latest "influxdb" "v1" >}}/tools/influxd-cli/backup) | Download a snapshot of a data node and saves it to disk. |
| [config](/{{< latest "influxdb" "v1" >}}/tools/influxd-cli/config) | Display the default configuration. |
| [backup](/influxdb/v1.7/tools/influxd-cli/backup) | Download a snapshot of a data node and saves it to disk. |
| [config](/influxdb/v1.7/tools/influxd-cli/config) | Display the default configuration. |
| help | Display the help message. |
| [restore](/{{< latest "influxdb" "v1" >}}/tools/influxd-cli/restore) | Use a snapshot of a data node to rebuild a cluster. |
| [run](/{{< latest "influxdb" "v1" >}}/tools/influxd-cli/run) | Run node with existing configuration. |
| [version](/{{< latest "influxdb" "v1" >}}/tools/influxd-cli/version) | Display the InfluxDB version. |
| [restore](/influxdb/v1.7/tools/influxd-cli/restore) | Use a snapshot of a data node to rebuild a cluster. |
| [run](/influxdb/v1.7/tools/influxd-cli/run) | Run node with existing configuration. |
| [version](/influxdb/v1.7/tools/influxd-cli/version) | Display the InfluxDB version. |

View File

@ -9,7 +9,7 @@ menu:
---
Flux is a functional data scripting language designed for querying, analyzing, and acting on time series data.
Its takes the power of [InfluxQL](/{{< latest "influxdb" "v1" >}}/query_language/spec/) and the functionality of [TICKscript](/{{< latest "kapacitor" >}}/tick/introduction/) and combines them into a single, unified syntax.
Its takes the power of [InfluxQL](/influxdb/v1.8/query_language/spec/) and the functionality of [TICKscript](/{{< latest "kapacitor" >}}/tick/introduction/) and combines them into a single, unified syntax.
> Flux v0.65 is production-ready and included with [InfluxDB v1.8](/influxdb/v1.8).
> The InfluxDB v1.8 implementation of Flux is read-only and does not support

View File

@ -28,7 +28,7 @@ interactive Flux Read-Eval-Print-Loop (REPL) allowing you to write and run Flux
---
_For information about downloading and installing InfluxDB, see [InfluxDB installation](/{{< latest "influxdb" "v1" >}}/introduction/installation)._
_For information about downloading and installing InfluxDB, see [InfluxDB installation](/influxdb/v1.8/introduction/installation)._
---

View File

@ -34,7 +34,7 @@ InfluxDB shell 1.4.x
* The InfluxDB API runs on port `8086` by default.
Therefore, `influx` will connect to port `8086` and `localhost` by default.
If you need to alter these defaults, run `influx --help`.
* The [`-precision` argument](/{{< latest "influxdb" "v1" >}}/tools/shell/#influx-options) specifies the format/precision of any returned timestamps.
* The [`-precision` argument](/influxdb/v1.8/tools/shell/#influx-options) specifies the format/precision of any returned timestamps.
In the example above, `rfc3339` tells InfluxDB to return timestamps in [RFC3339 format](https://www.ietf.org/rfc/rfc3339.txt) (`YYYY-MM-DDTHH:MM:SS.nnnnnnnnnZ`).
The command line is now ready to take input in the form of the Influx Query Language (a.k.a InfluxQL) statements.

View File

@ -17,7 +17,7 @@ The [collectd](https://collectd.org) input allows InfluxDB to accept data transm
## A note on UDP/IP buffer sizes
If you're running Linux or FreeBSD, please adjust your operating system UDP buffer size limit, [see here for more details.](/{{< latest "influxdb" "v1" >}}/supported_protocols/udp/#a-note-on-udpip-os-buffer-sizes)
If you're running Linux or FreeBSD, please adjust your operating system UDP buffer size limit, [see here for more details.](/influxdb/v1.8/supported_protocols/udp/#a-note-on-udpip-os-buffer-sizes)
## Configuration

View File

@ -941,7 +941,7 @@ Errors are returned in JSON.
| 400 Bad Request | Unacceptable request. Can occur with an InfluxDB line protocol syntax error or if a user attempts to write values to a field that previously accepted a different value type. The returned JSON offers further information. |
| 401 Unauthorized | Unacceptable request. Can occur with invalid authentication credentials. |
| 404 Not Found | Unacceptable request. Can occur if a user attempts to write to a database that does not exist. The returned JSON offers further information. |
| 413 Request Entity Too Large | Unaccetable request. It will occur if the payload of the POST request is bigger than the maximum size allowed. See [`max-body-size`](/{{< latest "influxdb" "v1" >}}/administration/config/#max-body-size-25000000) parameter for more details.
| 413 Request Entity Too Large | Unaccetable request. It will occur if the payload of the POST request is bigger than the maximum size allowed. See [`max-body-size`](/influxdb/v1.8/administration/config/#max-body-size-25000000) parameter for more details.
| 500 Internal Server Error | The system is overloaded or significantly impaired. Can occur if a user attempts to write to a retention policy that does not exist. The returned JSON offers further information. |
#### Examples

View File

@ -20,9 +20,9 @@ influxd [[command] [arguments]]
## Commands
| Command | Description |
|-------------------------------------------------------|----------------------------------------------------------|
| [backup](/{{< latest "influxdb" "v1" >}}/tools/influxd/backup) | Download a snapshot of a data node and saves it to disk. |
| [config](/{{< latest "influxdb" "v1" >}}/tools/influxd/config) | Display the default configuration. |
| [backup](/influxdb/v1.8/tools/influxd/backup) | Download a snapshot of a data node and saves it to disk. |
| [config](/influxdb/v1.8/tools/influxd/config) | Display the default configuration. |
| help | Display the help message. |
| [restore](/{{< latest "influxdb" "v1" >}}/tools/influxd/restore) | Use a snapshot of a data node to rebuild a cluster. |
| [run](/{{< latest "influxdb" "v1" >}}/tools/influxd/run) | Run node with existing configuration. |
| [version](/{{< latest "influxdb" "v1" >}}/tools/influxd/version) | Display the InfluxDB version. |
| [restore](/influxdb/v1.8/tools/influxd/restore) | Use a snapshot of a data node to rebuild a cluster. |
| [run](/influxdb/v1.8/tools/influxd/run) | Run node with existing configuration. |
| [version](/influxdb/v1.8/tools/influxd/version) | Display the InfluxDB version. |

View File

@ -100,7 +100,7 @@ On the **Billing page**, view the total limits available for the Free Plan.
## Exceeded rate limits
If you exceed your plan's [rate limits](/v2.0/account-management/pricing-plans/), {{< cloud-name >}} provides a notification in the {{< cloud-name "short" >}} user interface (UI) and adds a rate limit event to your **Usage** page for review.
If you exceed your plan's [rate limits](/influxdb/v2.0/account-management/pricing-plans/), {{< cloud-name >}} provides a notification in the {{< cloud-name "short" >}} user interface (UI) and adds a rate limit event to your **Usage** page for review.
All rate-limited requests are rejected; including both read and write requests.
_Rate-limited requests are **not** queued._

View File

@ -33,14 +33,14 @@ Find data usage information for the time frame specified in the drop-down at the
## Exceeded rate limits
If you exceed your plan's [rate limits](/v2.0/account-management/pricing-plans/), {{< cloud-name >}}
If you exceed your plan's [rate limits](/influxdb/v2.0/account-management/pricing-plans/), {{< cloud-name >}}
will provide a notification in the {{< cloud-name "short" >}} user interface (UI)
and add a rate limit event to your **Usage** page for review.
All rate-limited requests are rejected; including both read and write requests.
_Rate-limited requests are **not** queued._
_To remove rate limits, [upgrade to a Usage-based Plan](/v2.0/account-management/billing/#upgrade-to-usage-based-plan)._
_To remove rate limits, [upgrade to a Usage-based Plan](/influxdb/v2.0/account-management/billing/#upgrade-to-usage-based-plan)._
### Rate-limited HTTP response code
When a request exceeds your plan's rate limit, the InfluxDB API returns the following response:

View File

@ -34,11 +34,11 @@ Exported data and artifacts can be used in an InfluxDB OSS instance.
#### Export tasks
For details, see [Export a task](/v2.0/process-data/manage-tasks/export-task/).
For details, see [Export a task](/influxdb/v2.0/process-data/manage-tasks/export-task/).
#### Export dashboards
For details, see [Export a dashboard](/v2.0/visualize-data/dashboards/export-dashboard/).
For details, see [Export a dashboard](/influxdb/v2.0/visualize-data/dashboards/export-dashboard/).
#### Save Telegraf configurations

View File

@ -48,4 +48,4 @@ Guidelines used to estimate costs for default configurations:
- **Professional**. For teams monitoring multiple disparate systems or use cases.
- **Enterprise**. For teams monitoring multiple domains and use cases accessing a variety of dashboards.
5. Adjust the default configuration values to match your number of devices, plugins, metrics, and so on. The **Projected Usage** costs are automatically updated as you adjust your configuration.
6. Click **Get started with InfluxDB Cloud** [to get started](/v2.0/get-started/).
6. Click **Get started with InfluxDB Cloud** [to get started](/influxdb/v2.0/get-started/).

View File

@ -21,7 +21,7 @@ InfluxDB Cloud 2.0 offers two pricing plans:
- [Free Plan](#free-plan)
- [Usage-based Plan](#usage-based-plan)
<!--To estimate your projected usage costs, use the [InfluxDB Cloud 2.0 pricing calculator](/v2.0/account-management/pricing-calculator/). -->
<!--To estimate your projected usage costs, use the [InfluxDB Cloud 2.0 pricing calculator](/influxdb/v2.0/account-management/pricing-calculator/). -->
## Free Plan
@ -46,11 +46,11 @@ Data retention is determined by the time at which data is written to InfluxDB; n
- Unlimited Slack notification endpoints
_To remove rate limits, [upgrade to a Usage-based Plan](/v2.0/account-management/billing/#upgrade-to-usage-based-plan)._
_To remove rate limits, [upgrade to a Usage-based Plan](/influxdb/v2.0/account-management/billing/#upgrade-to-usage-based-plan)._
## Usage-based Plan
The Usage-based Plan offers more flexibility and ensures you only pay for what you [use](/v2.0/account-management/data-usage/).
The Usage-based Plan offers more flexibility and ensures you only pay for what you [use](/influxdb/v2.0/account-management/data-usage/).
#### Usage-based Plan rate limits

View File

@ -15,7 +15,7 @@ related:
products: [oss]
---
Use the [`influx backup` command](/v2.0/reference/cli/influx/backup/) to back up
Use the [`influx backup` command](/influxdb/v2.0/reference/cli/influx/backup/) to back up
data and metadata stored in InfluxDB.
InfluxDB copies all data and metadata to a set of files stored in a specified directory
on your local filesystem.
@ -34,7 +34,7 @@ The `influx backup` command requires:
- The directory path for where to store the backup file set
- The **root authorization token** (the token created for the first user in the
[InfluxDB setup process](/v2.0/get-started/)).
[InfluxDB setup process](/influxdb/v2.0/get-started/)).
##### Back up data with the influx CLI
```sh

View File

@ -43,12 +43,12 @@ _See [Recover from a failed restore](#recover-from-a-failed-restore)._
```
_For more information about restore options and flags, see the
[`influxd restore` documentation](/v2.0/reference/cli/influxd/restore/)._
[`influxd restore` documentation](/influxdb/v2.0/reference/cli/influxd/restore/)._
## Customize the TSI rebuild process
By default, InfluxDB rebuilds the index and [series file](/v2.0/reference/glossary/#series-file) when restoring data.
By default, InfluxDB rebuilds the index and [series file](/influxdb/v2.0/reference/glossary/#series-file) when restoring data.
When rebuilding the Time Series Index (TSI), it uses the
[default `build-tsi` options](/v2.0/reference/cli/influxd/inspect/build-tsi/).
[default `build-tsi` options](/influxdb/v2.0/reference/cli/influxd/inspect/build-tsi/).
To customize the Time Series Index (TSI) rebuild process:
1. Disable rebuilding the index and series files when restoring data:
@ -58,7 +58,7 @@ To customize the Time Series Index (TSI) rebuild process:
```
2. Manually run `influxd inspect build-tsi` with any
[custom options](/v2.0/reference/cli/influxd/inspect/build-tsi/#flags).
[custom options](/influxdb/v2.0/reference/cli/influxd/inspect/build-tsi/#flags).
```sh
influxd inspect build-tsi \
@ -67,13 +67,13 @@ To customize the Time Series Index (TSI) rebuild process:
```
{{% note %}}
Manually rebuild the TSI index to [adjust the performance](/v2.0/reference/cli/influxd/inspect/build-tsi/#adjust-performance)
Manually rebuild the TSI index to [adjust the performance](/influxdb/v2.0/reference/cli/influxd/inspect/build-tsi/#adjust-performance)
of the TSI rebuild process.
{{% /note %}}
## Recover from a failed restore
If the restoration process fails, InfluxDB preserves existing data in a `tmp`
directory in the [target engine path](/v2.0/reference/cli/influxd/restore/#flags)
directory in the [target engine path](/influxdb/v2.0/reference/cli/influxd/restore/#flags)
(default is `~/.influxdbv2/engine`).
To recover from a failed restore:

View File

@ -42,7 +42,7 @@ The `metadata.name` field in manifests uniquely identifies each resource in the
If resources in the template depend on other InfluxDB resources, all dependencies
must be included in the template.
_See [Create an InfluxDB template](/v2.0/influxdb-templates/create/) for information about
_See [Create an InfluxDB template](/influxdb/v2.0/influxdb-templates/create/) for information about
generating template manifests._
### Template resources

View File

@ -16,16 +16,16 @@ influxdb/v2.0/tags: [templates]
products: [cloud]
---
Use the [`influx` command line interface (CLI)](/v2.0/reference/cli/influx/)
Use the [`influx` command line interface (CLI)](/influxdb/v2.0/reference/cli/influx/)
to apply and manage templates in your InfluxDB Cloud account.
If you havent already, do the following:
1. [Download and install `influx` CLI](/v2.0/get-started/#optional-download-and-install-the-influx-cli).
2. [Configure the `influx` CLI](/v2.0/get-started/#set-up-influxdb) to use your
1. [Download and install `influx` CLI](/influxdb/v2.0/get-started/#optional-download-and-install-the-influx-cli).
2. [Configure the `influx` CLI](/influxdb/v2.0/get-started/#set-up-influxdb) to use your
InfluxDB Cloud instance URL, organization, and tokens.
3. [Use the `influx` CLI](/v2.0/reference/cli/influx/) to use, manage, and create
3. [Use the `influx` CLI](/influxdb/v2.0/reference/cli/influx/) to use, manage, and create
InfluxDB templates:
- [Use templates](/v2.0/influxdb-templates/use/)
- [Create templates](/v2.0/influxdb-templates/create/)
- [Use templates](/influxdb/v2.0/influxdb-templates/use/)
- [Create templates](/influxdb/v2.0/influxdb-templates/create/)

View File

@ -36,19 +36,19 @@ In **InfluxDB Cloud**, your user account is an organization.
**To create a template:**
1. [Start InfluxDB](/v2.0/get-started/).
2. [Create a new organization](/v2.0/organizations/create-org/).
1. [Start InfluxDB](/influxdb/v2.0/get-started/).
2. [Create a new organization](/influxdb/v2.0/organizations/create-org/).
3. In the InfluxDB UI add one or more of the following templatable resources:
- [buckets](/v2.0/organizations/buckets/create-bucket/)
- [checks](/v2.0/monitor-alert/checks/create/)
- [dashboards](/v2.0/visualize-data/dashboards/create-dashboard/)
- [dashboard variables](/v2.0/visualize-data/variables/create-variable/)
- [labels](/v2.0/visualize-data/labels/)
- [notification endpoints](/v2.0/monitor-alert/notification-endpoints/create/)
- [notification rules](/v2.0/monitor-alert/notification-rules/create/)
- [tasks](/v2.0/process-data/manage-tasks/create-task/)
- [Telegraf configurations](/v2.0/write-data/use-telegraf/)
- [buckets](/influxdb/v2.0/organizations/buckets/create-bucket/)
- [checks](/influxdb/v2.0/monitor-alert/checks/create/)
- [dashboards](/influxdb/v2.0/visualize-data/dashboards/create-dashboard/)
- [dashboard variables](/influxdb/v2.0/visualize-data/variables/create-variable/)
- [labels](/influxdb/v2.0/visualize-data/labels/)
- [notification endpoints](/influxdb/v2.0/monitor-alert/notification-endpoints/create/)
- [notification rules](/influxdb/v2.0/monitor-alert/notification-rules/create/)
- [tasks](/influxdb/v2.0/process-data/manage-tasks/create-task/)
- [Telegraf configurations](/influxdb/v2.0/write-data/use-telegraf/)
4. Export the template _(see [below](#export-a-template))_.
@ -108,7 +108,7 @@ influx export all \
```
For information about flags, see the
[`influx export all` documentation](/v2.0/reference/cli/influx/export/all/).
[`influx export all` documentation](/influxdb/v2.0/reference/cli/influx/export/all/).
### Export specific resources
To export specific resources within an organization to a template manifest,
@ -122,7 +122,7 @@ Provide the following:
**JSON** (`.json`) are supported.
- **Resource flags** with corresponding lists of resource IDs to include in the template.
For information about what resource flags are available, see the
[`influx export` documentation](/v2.0/reference/cli/influx/export/).
[`influx export` documentation](/influxdb/v2.0/reference/cli/influx/export/).
###### Export specific resources to a template
```sh
@ -219,7 +219,7 @@ metadata:
{{< /code-tabs-wrapper >}}
Using the example above, users are prompted to provide a value for `bucket-name-1`
when [applying the template](/v2.0/influxdb-templates/use/#apply-templates).
when [applying the template](/influxdb/v2.0/influxdb-templates/use/#apply-templates).
Users can also include the `--env-ref` flag with the appropriate key-value pair
when installing the template.

View File

@ -15,7 +15,7 @@ related:
- /influxdb/v2.0/reference/cli/stacks/
---
**InfluxDB stacks** are **stateful [InfluxDB templates](/v2.0/influxdb-templates)**
**InfluxDB stacks** are **stateful [InfluxDB templates](/influxdb/v2.0/influxdb-templates)**
that let you add, update, and remove templated resources over time, avoid
duplicating resources when applying the same or similar templates more than once,
and apply changes to distributed instances of InfluxDB OSS or InfluxDB Cloud.
@ -43,7 +43,7 @@ apply updates without creating duplicate resources.
In many cases, users have more than one instance of InfluxDB running and apply
the same template to each separate instance.
By using stacks, you can make changes to a stack on one instance,
[export the stack as a template](/v2.0/influxdb-templates/create/#export-a-stack)
[export the stack as a template](/influxdb/v2.0/influxdb-templates/create/#export-a-stack)
and then apply the changes to your other InfluxDB instances.
## Manage InfluxDB Stacks

View File

@ -2,9 +2,9 @@
title: Initialize an InfluxDB stack
list_title: Initialize a stack
description: >
InfluxDB automatically creates a new stack each time you [apply an InfluxDB template](/v2.0/influxdb-templates/use/)
InfluxDB automatically creates a new stack each time you [apply an InfluxDB template](/influxdb/v2.0/influxdb-templates/use/)
**without providing a stack ID**.
To manually create or initialize a new stack, use the [`influx stacks init` command](/v2.0/reference/cli/influx/stacks/init/).
To manually create or initialize a new stack, use the [`influx stacks init` command](/influxdb/v2.0/reference/cli/influx/stacks/init/).
menu:
influxdb_2_0:
parent: InfluxDB stacks
@ -30,12 +30,12 @@ list_code_example: |
```
---
InfluxDB automatically creates a new stack each time you [apply an InfluxDB template](/v2.0/influxdb-templates/use/)
InfluxDB automatically creates a new stack each time you [apply an InfluxDB template](/influxdb/v2.0/influxdb-templates/use/)
**without providing a stack ID**.
To manually create or initialize a new stack, use the [`influx stacks init` command](/v2.0/reference/cli/influx/stacks/init/).
To manually create or initialize a new stack, use the [`influx stacks init` command](/influxdb/v2.0/reference/cli/influx/stacks/init/).
## Initialize a stack when applying a template
To automatically create a new stack when [applying an InfluxDB template](/v2.0/influxdb-templates/use/)
To automatically create a new stack when [applying an InfluxDB template](/influxdb/v2.0/influxdb-templates/use/)
**don't provide a stack ID**.
InfluxDB applies the resources in the template to a new stack and provides the **stack ID** the output.
@ -46,7 +46,7 @@ influx apply \
```
## Manually initialize a new stack
Use the [`influx stacks init` command](/v2.0/reference/cli/influx/stacks/init/)
Use the [`influx stacks init` command](/influxdb/v2.0/reference/cli/influx/stacks/init/)
to create or initialize a new InfluxDB stack.
**Provide the following:**

View File

@ -2,7 +2,7 @@
title: Remove an InfluxDB stack
list_title: Remove a stack
description: >
Use the [`influx stacks remove` command](/v2.0/reference/cli/influx/stacks/remove/)
Use the [`influx stacks remove` command](/influxdb/v2.0/reference/cli/influx/stacks/remove/)
to remove an InfluxDB stack and all its associated resources.
menu:
influxdb_2_0:
@ -21,7 +21,7 @@ list_code_example: |
```
---
Use the [`influx stacks remove` command](/v2.0/reference/cli/influx/stacks/remove/)
Use the [`influx stacks remove` command](/influxdb/v2.0/reference/cli/influx/stacks/remove/)
to remove an InfluxDB stack and all its associated resources.
**Provide the following:**

View File

@ -2,7 +2,7 @@
title: Update an InfluxDB stack
list_title: Update a stack
description: >
Use the [`influx apply` command](/v2.0/reference/cli/influx/apply/)
Use the [`influx apply` command](/influxdb/v2.0/reference/cli/influx/apply/)
to update a stack with a modified template.
When applying a template to an existing stack, InfluxDB checks to see if the
resources in the template match existing resources.
@ -28,7 +28,7 @@ list_code_example: |
```
---
Use the [`influx apply` command](/v2.0/reference/cli/influx/apply/)
Use the [`influx apply` command](/influxdb/v2.0/reference/cli/influx/apply/)
to update a stack with a modified template.
When applying a template to an existing stack, InfluxDB checks to see if the
resources in the template match existing resources.
@ -36,7 +36,7 @@ InfluxDB updates, adds, and removes resources to resolve differences between
the current state of the stack and the newly applied template.
Each stack is uniquely identified by a **stack ID**.
For information about retrieving your stack ID, see [View stacks](/v2.0/influxdb-templates/stacks/view/).
For information about retrieving your stack ID, see [View stacks](/influxdb/v2.0/influxdb-templates/stacks/view/).
**Provide the following:**

View File

@ -2,7 +2,7 @@
title: View InfluxDB stacks
list_title: View stacks
description: >
Use the [`influx stacks` command](/v2.0/reference/cli/influx/stacks/)
Use the [`influx stacks` command](/influxdb/v2.0/reference/cli/influx/stacks/)
to view installed InfluxDB stacks and their associated resources.
menu:
influxdb_2_0:
@ -19,7 +19,7 @@ list_code_example: |
```
---
Use the [`influx stacks` command](/v2.0/reference/cli/influx/stacks/)
Use the [`influx stacks` command](/influxdb/v2.0/reference/cli/influx/stacks/)
to view installed InfluxDB stacks and their associated resources.
**Provide the following:**

View File

@ -54,7 +54,7 @@ https://raw.githubusercontent.com/influxdata/community-templates/master/docker/d
## View a template summary
To view a summary of what's included in a template before applying the template,
use the [`influx template` command](/v2.0/reference/cli/influx/template/).
use the [`influx template` command](/influxdb/v2.0/reference/cli/influx/template/).
View a summary of a template stored in your local filesystem or from a URL.
{{% code-tabs-wrapper %}}
@ -84,7 +84,7 @@ influx template -u https://raw.githubusercontent.com/influxdata/community-templa
## Validate a template
To validate a template before you install it or troubleshoot a template, use
the [`influx template validate` command](/v2.0/reference/cli/influx/template/validate/).
the [`influx template validate` command](/influxdb/v2.0/reference/cli/influx/template/validate/).
Validate a template stored in your local filesystem or from a URL.
{{% code-tabs-wrapper %}}
@ -113,7 +113,7 @@ influx template validate -u https://raw.githubusercontent.com/influxdata/communi
{{% /code-tabs-wrapper %}}
## Apply templates
Use the [`influx apply` command](/v2.0/reference/cli/influx/apply/) to install templates
Use the [`influx apply` command](/influxdb/v2.0/reference/cli/influx/apply/) to install templates
from your local filesystem or from URLs.
- [Apply a template from a file](#apply-a-template-from-a-file)
@ -128,7 +128,7 @@ from your local filesystem or from URLs.
To apply a template to an existing stack, include the stack ID when applying the template.
Any time you apply a template without a stack ID, InfluxDB initializes a new stack
and all new resources.
For more information, see [InfluxDB stacks](/v2.0/influxdb-templates/stacks/).
For more information, see [InfluxDB stacks](/influxdb/v2.0/influxdb-templates/stacks/).
{{% /note %}}
### Apply a template from a file
@ -204,7 +204,7 @@ influx apply -o example-org \
```
### Define environment references
Some templates include [environment references](/v2.0/influxdb-templates/create/#include-user-definable-resource-names) that let you provide custom resource names.
Some templates include [environment references](/influxdb/v2.0/influxdb-templates/create/#include-user-definable-resource-names) that let you provide custom resource names.
The `influx apply` command prompts you to provide a value for each environment
reference in the template.
You can also provide values for environment references by including an `--env-ref`
@ -219,7 +219,7 @@ influx apply -o example-org -f /path/to/template.yml \
```
### Include a secret when installing a template
Some templates use [secrets](/v2.0/security/secrets/) in queries.
Some templates use [secrets](/influxdb/v2.0/security/secrets/) in queries.
Secret values are not included in templates.
To define secret values when installing a template, include the `--secret` flag
with the secret key-value pair.
@ -240,4 +240,4 @@ influx apply -o example-org -f /path/to/template.yml \
--secret=BAZ=quz
```
_To add a secret after applying a template, see [Add secrets](/v2.0/security/secrets/manage-secrets/add/)._
_To add a secret after applying a template, see [Add secrets](/influxdb/v2.0/security/secrets/manage-secrets/add/)._

View File

@ -14,25 +14,25 @@ influxdb/v2.0/tags: [monitor, alert, checks, notification, endpoints]
---
Monitor your time series data and send alerts by creating checks, notification
rules, and notification endpoints. Or use [community templates to monitor](/v2.0/monitor-alert/templates/) supported environments.
rules, and notification endpoints. Or use [community templates to monitor](/influxdb/v2.0/monitor-alert/templates/) supported environments.
## Overview
1. A [check](/v2.0/reference/glossary/#check) in InfluxDB queries data and assigns a status with a `_level` based on specific conditions.
1. A [check](/influxdb/v2.0/reference/glossary/#check) in InfluxDB queries data and assigns a status with a `_level` based on specific conditions.
2. InfluxDB stores the output of a check in the `statuses` measurement in the `_monitoring` system bucket.
3. [Notification rules](/v2.0/reference/glossary/#notification-rule) check data in the `statuses`
3. [Notification rules](/influxdb/v2.0/reference/glossary/#notification-rule) check data in the `statuses`
measurement and, based on conditions set in the notification rule, send a message
to a [notification endpoint](/v2.0/reference/glossary/#notification-endpoint).
to a [notification endpoint](/influxdb/v2.0/reference/glossary/#notification-endpoint).
4. InfluxDB stores notifications in the `notifications` measurement in the `_monitoring` system bucket.
## Create an alert
To get started, do the following:
1. [Create checks](/v2.0/monitor-alert/checks/create/) to monitor data and assign a status.
2. [Add notification endpoints](/v2.0/monitor-alert/notification-endpoints/create/)
1. [Create checks](/influxdb/v2.0/monitor-alert/checks/create/) to monitor data and assign a status.
2. [Add notification endpoints](/influxdb/v2.0/monitor-alert/notification-endpoints/create/)
to send notifications to third parties.
3. [Create notification rules](/v2.0/monitor-alert/notification-rules/create) to check
3. [Create notification rules](/influxdb/v2.0/monitor-alert/notification-rules/create) to check
statuses and send notifications to your notifications endpoints.
## Manage your monitoring and alerting pipeline

View File

@ -87,16 +87,16 @@ in a specified amount of time.
Use custom tags to associate additional metadata with the check.
Common metadata tags across different checks lets you easily group and organize checks.
You can also use custom tags in [notification rules](/v2.0/monitor-alert/notification-rules/create/).
You can also use custom tags in [notification rules](/influxdb/v2.0/monitor-alert/notification-rules/create/).
3. In the **Status Message Template** column, enter the status message template for the check.
Use [Flux string interpolation](/v2.0/reference/flux/language/string-interpolation/)
Use [Flux string interpolation](/influxdb/v2.0/reference/flux/language/string-interpolation/)
to populate the message with data from the query.
{{% note %}}
#### Flux only interpolates string values
Flux currently interpolates only string values.
Use the [string() function](/v2.0/reference/flux/stdlib/built-in/transformations/type-conversions/string/)
Use the [string() function](/influxdb/v2.0/reference/flux/stdlib/built-in/transformations/type-conversions/string/)
to convert non-string values to strings.
```js

View File

@ -31,6 +31,6 @@ After a check is deleted, all statuses generated by the check remain in the `_mo
bucket until the retention period for the bucket expires.
{{% note %}}
You can also [disable a check](/v2.0/monitor-alert/checks/update/#enable-or-disable-a-check)
You can also [disable a check](/influxdb/v2.0/monitor-alert/checks/update/#enable-or-disable-a-check)
without having to delete it.
{{% /note %}}

View File

@ -33,7 +33,7 @@ To update checks, select **Alerts** in the navigation menu on the left.
2. To edit the check query, click **1. Define Query** at the top of the check builder window.
3. To edit the check logic, click **2. Configure Check** at the top of the check builder window.
_For details about using the check builder, see [Create checks](/v2.0/monitor-alert/checks/create/)._
_For details about using the check builder, see [Create checks](/influxdb/v2.0/monitor-alert/checks/create/)._
## Enable or disable a check
Click the {{< icon "toggle" >}} toggle next to a check to enable or disable it.

View File

@ -14,7 +14,7 @@ related:
- /influxdb/v2.0/monitor-alert/notification-rules/
---
To send notifications about changes in your data, start by creating a notification endpoint to a third party service. After creating notification endpoints, [create notification rules](/v2.0/monitor-alert/notification-rules/create) to send alerts to third party services on [check statuses](/v2.0/monitor-alert/checks/create).
To send notifications about changes in your data, start by creating a notification endpoint to a third party service. After creating notification endpoints, [create notification rules](/influxdb/v2.0/monitor-alert/notification-rules/create) to send alerts to third party services on [check statuses](/influxdb/v2.0/monitor-alert/checks/create).
## Create a notification endpoint in the UI

View File

@ -14,7 +14,7 @@ related:
- /influxdb/v2.0/monitor-alert/notification-rules/
---
If notifications are no longer sent to an endpoint, complete the steps below to delete the endpoint, and then [update notification rules](/v2.0/monitor-alert/notification-rules/update) with a new notification endpoint as needed.
If notifications are no longer sent to an endpoint, complete the steps below to delete the endpoint, and then [update notification rules](/influxdb/v2.0/monitor-alert/notification-rules/update) with a new notification endpoint as needed.
## Delete a notification endpoint in the UI

View File

@ -14,7 +14,7 @@ related:
- /influxdb/v2.0/monitor-alert/notification-rules/
---
To update the notification endpoint details, complete the procedures below as needed. To update the notification endpoint selected for a notification rule, see [update notification rules](/v2.0/monitor-alert/notification-rules/update/).
To update the notification endpoint details, complete the procedures below as needed. To update the notification endpoint selected for a notification rule, see [update notification rules](/influxdb/v2.0/monitor-alert/notification-rules/update/).
## Add a label to notification endpoint
@ -65,4 +65,4 @@ To update the notification endpoint details, complete the procedures below as ne
2. Select **Notification Endpoints** near to top of the page.
3. Click the endpoint to update.
4. Update details as needed, and then click **Edit Notification Endpoint**.
For details about each field, see [Create notification endpoints](/v2.0/monitor-alert/notification-endpoints/create/).
For details about each field, see [Create notification endpoints](/influxdb/v2.0/monitor-alert/notification-endpoints/create/).

View File

@ -14,8 +14,8 @@ related:
---
Once you've set up checks and notification endpoints, create notification rules to alert you.
_For details, see [Manage checks](/v2.0/monitor-alert/checks/) and
[Manage notification endpoints](/v2.0/monitor-alert/notification-endpoints/)._
_For details, see [Manage checks](/influxdb/v2.0/monitor-alert/checks/) and
[Manage notification endpoints](/influxdb/v2.0/monitor-alert/notification-endpoints/)._
## Create a new notification rule in the UI

View File

@ -13,23 +13,23 @@ Use the [AWS CloudWatch Monitoring template](https://github.com/influxdata/commu
The AWS CloudWatch Monitoring template includes the following:
- two [dashboards](/v2.0/reference/glossary/#dashboard):
- two [dashboards](/influxdb/v2.0/reference/glossary/#dashboard):
- **AWS CloudWatch NLB (Network Load Balancers) Monitoring**: Displays data from the `cloudwatch_aws_network_elb measurement`
- **AWS CloudWatch Instance Monitoring**: Displays data from the `cloudwatch_aws_ec2` measurement
- two [buckets](/v2.0/reference/glossary/#bucket): `kubernetes` and `cloudwatch`
- two [buckets](/influxdb/v2.0/reference/glossary/#bucket): `kubernetes` and `cloudwatch`
- two labels: `inputs.cloudwatch`, `AWS`
- one variable: `v.bucket`
- one [Telegraf configuration](/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/): [AWS CloudWatch input plugin](/v2.0/reference/telegraf-plugins/#cloudwatch)
- one [Telegraf configuration](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/): [AWS CloudWatch input plugin](/influxdb/v2.0/reference/telegraf-plugins/#cloudwatch)
## Apply the template
1. Use the [`influx` CLI](/v2.0/reference/cli/influx/) to run the following command:
1. Use the [`influx` CLI](/influxdb/v2.0/reference/cli/influx/) to run the following command:
```sh
influx apply -f https://raw.githubusercontent.com/influxdata/community-templates/master/aws_cloudwatch/aws_cloudwatch.yml
```
For more information, see [influx apply](/v2.0/reference/cli/influx/apply/).
2. [Install Telegraf](/{{< latest "telegraf" >}}/introduction/installation/) on a server with network access to both the CloudWatch API and [InfluxDB v2 API](/v2.0/reference/api/).
For more information, see [influx apply](/influxdb/v2.0/reference/cli/influx/apply/).
2. [Install Telegraf](/{{< latest "telegraf" >}}/introduction/installation/) on a server with network access to both the CloudWatch API and [InfluxDB v2 API](/influxdb/v2.0/reference/api/).
3. In your Telegraf configuration file (`telegraf.conf`), find the following example `influxdb_v2` output plugins, and then **replace** the `urls` to specify the servers to monitor:
```sh
@ -47,7 +47,7 @@ The AWS CloudWatch Monitoring template includes the following:
organization = "$INFLUX_ORG"
bucket = “cloudwatch"
```
4. [Start Telegraf](/v2.0/write-data/no-code/use-telegraf/auto-config/#start-telegraf).
4. [Start Telegraf](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/#start-telegraf).
## View the incoming data

View File

@ -10,41 +10,41 @@ weight: 202
---
Use the [Docker Monitoring template](https://github.com/influxdata/community-templates/tree/master/docker) to monitor your Docker containers. First, [apply the template](#apply-the-template), and then [view incoming data](#view-incoming-data).
This template uses the [Docker input plugin](/v2.0/reference/telegraf-plugins/#docker) to collect metrics stored in InfluxDB and display these metrics in a dashboard.
This template uses the [Docker input plugin](/influxdb/v2.0/reference/telegraf-plugins/#docker) to collect metrics stored in InfluxDB and display these metrics in a dashboard.
The Docker Monitoring template includes the following:
- one [dashboard](/v2.0/reference/glossary/#dashboard): **Docker**
- one [bucket](/v2.0/reference/glossary/#bucket): `docker, 7d retention`
- one [dashboard](/influxdb/v2.0/reference/glossary/#dashboard): **Docker**
- one [bucket](/influxdb/v2.0/reference/glossary/#bucket): `docker, 7d retention`
- labels: Docker input plugin labels
- one [Telegraf configuration](/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/): Docker input plugin
- one [Telegraf configuration](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/): Docker input plugin
- one variable: `bucket`
- four [checks](/v2.0/reference/glossary/#check): `Container cpu`, `mem`, `disk`, `non-zero exit`
- one [notification endpoint](/v2.0/reference/glossary/#notification-endpoint): `Http Post`
- one [notification rule](/v2.0/reference/glossary/#notification-rule): `Crit Alert`
- four [checks](/influxdb/v2.0/reference/glossary/#check): `Container cpu`, `mem`, `disk`, `non-zero exit`
- one [notification endpoint](/influxdb/v2.0/reference/glossary/#notification-endpoint): `Http Post`
- one [notification rule](/influxdb/v2.0/reference/glossary/#notification-rule): `Crit Alert`
For more information about how checks, notification endpoints, and notifications rules work together, see [monitor data and send alerts](/v2.0/monitor-alert/).
For more information about how checks, notification endpoints, and notifications rules work together, see [monitor data and send alerts](/influxdb/v2.0/monitor-alert/).
## Apply the template
1. Use the [`influx` CLI](/v2.0/reference/cli/influx/) to run the following command:
1. Use the [`influx` CLI](/influxdb/v2.0/reference/cli/influx/) to run the following command:
```sh
influx apply -f https://raw.githubusercontent.com/influxdata/community-templates/master/docker/docker.yml
```
For more information, see [influx apply](/v2.0/reference/cli/influx/apply/).
For more information, see [influx apply](/influxdb/v2.0/reference/cli/influx/apply/).
> **Note:** Ensure your `influx` CLI is configured with your account credentials and that configuration is active. For more information, see [influx config](/influxdb/v2.0/reference/cli/influx/config/).
2. [Install Telegraf](/{{< latest "telegraf" >}}/introduction/installation/) on a server with network access to both the Docker containers and [InfluxDB v2 API](/v2.0/reference/api/).
3. In your [Telegraf configuration file (`telegraf.conf`)](/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/), do the following:
- Depending on how you run Docker, you may need to customize the [Docker input plugin](/v2.0/reference/telegraf-plugins/#docker) configuration, for example, you may need to specify the `endpoint` value.
2. [Install Telegraf](/{{< latest "telegraf" >}}/introduction/installation/) on a server with network access to both the Docker containers and [InfluxDB v2 API](/influxdb/v2.0/reference/api/).
3. In your [Telegraf configuration file (`telegraf.conf`)](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/), do the following:
- Depending on how you run Docker, you may need to customize the [Docker input plugin](/influxdb/v2.0/reference/telegraf-plugins/#docker) configuration, for example, you may need to specify the `endpoint` value.
- Set the following environment variables:
- INFLUX_TOKEN: Token must have permissions to read Telegraf configurations and write data to the `telegraf` bucket. See how to [view tokens](/v2.0/security/tokens/view-tokens/).
- INFLUX_ORG: Name of your organization. See how to [view your organization](/v2.0/organizations/view-orgs/).
- INFLUX_TOKEN: Token must have permissions to read Telegraf configurations and write data to the `telegraf` bucket. See how to [view tokens](/influxdb/v2.0/security/tokens/view-tokens/).
- INFLUX_ORG: Name of your organization. See how to [view your organization](/influxdb/v2.0/organizations/view-orgs/).
- INFLUX_HOST: Your InfluxDB host URL, for example, localhost, a remote instance, or InfluxDB Cloud.
4. [Start Telegraf](/v2.0/write-data/no-code/use-telegraf/auto-config/#start-telegraf).
4. [Start Telegraf](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/#start-telegraf).
## View incoming data

View File

@ -10,32 +10,32 @@ weight: 206
---
Use the [vSphere Dashboard for InfluxDB v2 template](https://github.com/influxdata/community-templates/tree/master/vsphere) to monitor your vSphere host. First, [apply the template](#apply-the-template), and then [view incoming data](#view-incoming-data).
This template uses the [Docker input plugin](/v2.0/reference/telegraf-plugins/#docker) to collect metrics stored in InfluxDB and display these metrics in a dashboard.
This template uses the [Docker input plugin](/influxdb/v2.0/reference/telegraf-plugins/#docker) to collect metrics stored in InfluxDB and display these metrics in a dashboard.
The Docker Monitoring template includes the following:
- one [dashboard](/v2.0/reference/glossary/#dashboard): **vsphere**
- one [bucket](/v2.0/reference/glossary/#bucket): `vsphere`
- one [dashboard](/influxdb/v2.0/reference/glossary/#dashboard): **vsphere**
- one [bucket](/influxdb/v2.0/reference/glossary/#bucket): `vsphere`
- label: vsphere
- one [Telegraf configuration](/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/): InfluxDB v2 output plugin, vSphere input plugin
- one [Telegraf configuration](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/): InfluxDB v2 output plugin, vSphere input plugin
- one variable: `bucket`
## Apply the template
1. Use the [`influx` CLI](/v2.0/reference/cli/influx/) to run the following command:
1. Use the [`influx` CLI](/influxdb/v2.0/reference/cli/influx/) to run the following command:
```sh
influx apply -f https://raw.githubusercontent.com/influxdata/community-templates/master/vsphere/vsphere.yml
```
For more information, see [influx apply](/v2.0/reference/cli/influx/apply/).
For more information, see [influx apply](/influxdb/v2.0/reference/cli/influx/apply/).
> **Note:** Ensure your `influx` CLI is configured with your account credentials and that configuration is active. For more information, see [influx config](/influxdb/v2.0/reference/cli/influx/config/).
2. [Install Telegraf](/{{< latest "telegraf" >}}/introduction/installation/) on a server with network access to both the vSphere host and [InfluxDB v2 API](/v2.0/reference/api/).
3. In your [Telegraf configuration file (`telegraf.conf`)](/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/), do the following:
2. [Install Telegraf](/{{< latest "telegraf" >}}/introduction/installation/) on a server with network access to both the vSphere host and [InfluxDB v2 API](/influxdb/v2.0/reference/api/).
3. In your [Telegraf configuration file (`telegraf.conf`)](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/), do the following:
- Set the following environment variables:
- INFLUX_TOKEN: Token must have permissions to read Telegraf configurations and write data to the `telegraf` bucket. See how to [view tokens](/v2.0/security/tokens/view-tokens/).
- INFLUX_ORG: Name of your organization. See how to [view your organization](/v2.0/organizations/view-orgs/).
- INFLUX_TOKEN: Token must have permissions to read Telegraf configurations and write data to the `telegraf` bucket. See how to [view tokens](/influxdb/v2.0/security/tokens/view-tokens/).
- INFLUX_ORG: Name of your organization. See how to [view your organization](/influxdb/v2.0/organizations/view-orgs/).
- INFLUX_HOST: Your InfluxDB host URL, for example, localhost, a remote instance, or InfluxDB Cloud.
- INFLUX_BUCKET: Bucket to store data in. To use the bucket included, you must export the variable: `export INFLUX_BUCKET=vsphere`
4. - Set the host address to the vSphere and provide the `username` and `password` as variables:
@ -45,7 +45,7 @@ The Docker Monitoring template includes the following:
password = "$vsphere-password"
```
4. [Start Telegraf](/v2.0/write-data/no-code/use-telegraf/auto-config/#start-telegraf).
4. [Start Telegraf](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/#start-telegraf).
## View incoming data

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