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

updated all existing icons with versioned style

pull/3364/head
Scott Anderson 2021-11-03 16:09:13 -06:00
parent ec43a737f1
commit 79b6cdf539
112 changed files with 630 additions and 622 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

482
assets/styles/tools/_icomoon-v2.scss
View File

@ -10,246 +10,248 @@
font-display: block; font-display: block;
} }
[class^="icon-"], [class*=" icon-"] { .v2 {
/* use !important to prevent issues with browser extensions that change fonts */ &[class^="icon-"], &[class*=" icon-"] {
font-family: 'icomoon-v2' !important; /* use !important to prevent issues with browser extensions that change fonts */
speak: never; font-family: 'icomoon-v2' !important;
font-style: normal; speak: never;
font-weight: normal; font-style: normal;
font-variant: normal; font-weight: normal;
text-transform: none; font-variant: normal;
line-height: 1; text-transform: none;
line-height: 1;
/* Better Font Rendering =========== */ /* Better Font Rendering =========== */
-webkit-font-smoothing: antialiased; -webkit-font-smoothing: antialiased;
-moz-osx-font-smoothing: grayscale; -moz-osx-font-smoothing: grayscale;
} }
.icon-bar-chart:before { &.icon-bar-chart:before {
content: "\e913"; content: "\e913";
} }
.icon-influx-logo:before { &.icon-influx-logo:before {
content: "\e900"; content: "\e900";
} }
.icon-influx-logotype:before { &.icon-influx-logotype:before {
content: "\e901"; content: "\e901";
} }
.icon-alert-triangle:before { &.icon-alert-triangle:before {
content: "\e902"; content: "\e902";
} }
.icon-arrow-down:before { &.icon-arrow-down:before {
content: "\e903"; content: "\e903";
} }
.icon-moon1:before { &.icon-moon1:before {
content: "\e904"; content: "\e904";
} }
.icon-search:before { &.icon-search:before {
content: "\e905"; content: "\e905";
} }
.icon-sun1:before { &.icon-sun1:before {
content: "\e906"; content: "\e906";
} }
.icon-arrow-down-circle:before { &.icon-arrow-down-circle:before {
content: "\e907"; content: "\e907";
} }
.icon-arrow-down-left:before { &.icon-arrow-down-left:before {
content: "\e908"; content: "\e908";
} }
.icon-arrow-down-right:before { &.icon-arrow-down-right:before {
content: "\e909"; content: "\e909";
} }
.icon-arrow-left:before { &.icon-arrow-left:before {
content: "\e90a"; content: "\e90a";
} }
.icon-arrow-left-circle:before { &.icon-arrow-left-circle:before {
content: "\e90b"; content: "\e90b";
} }
.icon-arrow-right:before { &.icon-arrow-right:before {
content: "\e90c"; content: "\e90c";
} }
.icon-arrow-right-circle:before { &.icon-arrow-right-circle:before {
content: "\e90d"; content: "\e90d";
} }
.icon-arrow-up:before { &.icon-arrow-up:before {
content: "\e90e"; content: "\e90e";
} }
.icon-arrow-up-circle:before { &.icon-arrow-up-circle:before {
content: "\e90f"; content: "\e90f";
} }
.icon-arrow-up-left:before { &.icon-arrow-up-left:before {
content: "\e910"; content: "\e910";
} }
.icon-arrow-up-right:before { &.icon-arrow-up-right:before {
content: "\e911"; content: "\e911";
} }
.icon-check:before { &.icon-check:before {
content: "\e912"; content: "\e912";
} }
.icon-heart1:before { &.icon-heart1:before {
content: "\e914"; content: "\e914";
} }
.icon-settings:before { &.icon-settings:before {
content: "\e915"; content: "\e915";
} }
.icon-zoom-in:before { &.icon-zoom-in:before {
content: "\e916"; content: "\e916";
} }
.icon-zoom-out:before { &.icon-zoom-out:before {
content: "\e917"; content: "\e917";
} }
.icon-chevron-down:before { &.icon-chevron-down:before {
content: "\e918"; content: "\e918";
} }
.icon-chevron-left:before { &.icon-chevron-left:before {
content: "\e919"; content: "\e919";
} }
.icon-chevron-right:before { &.icon-chevron-right:before {
content: "\e91a"; content: "\e91a";
} }
.icon-chevron-up:before { &.icon-chevron-up:before {
content: "\e91b"; content: "\e91b";
} }
.icon-menu:before { &.icon-menu:before {
content: "\e91c"; content: "\e91c";
} }
.icon-download:before { &.icon-download:before {
content: "\e91d"; content: "\e91d";
} }
.icon-minus:before { &.icon-minus:before {
content: "\e91e"; content: "\e91e";
} }
.icon-plus:before { &.icon-plus:before {
content: "\e91f"; content: "\e91f";
} }
.icon-add-cell:before { &.icon-add-cell:before {
content: "\e920"; content: "\e920";
} }
.icon-alert:before { &.icon-alert:before {
content: "\e921"; content: "\e921";
} }
.icon-calendar:before { &.icon-calendar:before {
content: "\e922"; content: "\e922";
} }
.icon-checkmark:before { &.icon-checkmark:before {
content: "\e923"; content: "\e923";
} }
.icon-cog-thick:before { &.icon-cog-thick:before {
content: "\e924"; content: "\e924";
} }
.icon-dashboards:before { &.icon-dashboards:before {
content: "\e925"; content: "\e925";
} }
.icon-data-explorer:before { &.icon-data-explorer:before {
content: "\e926"; content: "\e926";
} }
.icon-ui-download:before { &.icon-ui-download:before {
content: "\e927"; content: "\e927";
} }
.icon-duplicate:before { &.icon-duplicate:before {
content: "\e928"; content: "\e928";
} }
.icon-export:before { &.icon-export:before {
content: "\e929"; content: "\e929";
} }
.icon-fullscreen:before { &.icon-fullscreen:before {
content: "\e92a"; content: "\e92a";
} }
.icon-influx-icon:before { &.icon-influx-icon:before {
content: "\e92b"; content: "\e92b";
} }
.icon-note:before { &.icon-note:before {
content: "\e92c"; content: "\e92c";
} }
.icon-organizations:before { &.icon-organizations:before {
content: "\e92d"; content: "\e92d";
} }
.icon-pause:before { &.icon-pause:before {
content: "\e92e"; content: "\e92e";
} }
.icon-pencil:before { &.icon-pencil:before {
content: "\e92f"; content: "\e92f";
} }
.icon-play:before { &.icon-play:before {
content: "\e930"; content: "\e930";
} }
.icon-ui-plus:before { &.icon-ui-plus:before {
content: "\e931"; content: "\e931";
} }
.icon-refresh:before { &.icon-refresh:before {
content: "\e932"; content: "\e932";
} }
.icon-remove:before { &.icon-remove:before {
content: "\e933"; content: "\e933";
} }
.icon-alert-circle:before { &.icon-alert-circle:before {
content: "\e934"; content: "\e934";
} }
.icon-crown:before { &.icon-crown:before {
content: "\e935"; content: "\e935";
} }
.icon-trash:before { &.icon-trash:before {
content: "\e936"; content: "\e936";
} }
.icon-triangle:before { &.icon-triangle:before {
content: "\e937"; content: "\e937";
} }
.icon-x:before { &.icon-x:before {
content: "\e938"; content: "\e938";
} }
.icon-wrench-2:before { &.icon-wrench-2:before {
content: "\e939"; content: "\e939";
} }
.icon-chat:before { &.icon-chat:before {
content: "\e93a"; content: "\e93a";
} }
.icon-bell:before { &.icon-bell:before {
content: "\e93b"; content: "\e93b";
} }
.icon-disks-nav:before { &.icon-disks-nav:before {
content: "\e93c"; content: "\e93c";
} }
.icon-wrench-nav:before { &.icon-wrench-nav:before {
content: "\e93d"; content: "\e93d";
} }
.icon-user:before { &.icon-user:before {
content: "\e93e"; content: "\e93e";
} }
.icon-cloud:before { &.icon-cloud:before {
content: "\e93f"; content: "\e93f";
} }
.icon-users-trio:before { &.icon-users-trio:before {
content: "\e940"; content: "\e940";
} }
.icon-nav-chat:before { &.icon-nav-chat:before {
content: "\e941"; content: "\e941";
} }
.icon-map2:before { &.icon-map2:before {
content: "\e94c"; content: "\e94c";
} }
.icon-eye-closed:before { &.icon-eye-closed:before {
content: "\e956"; content: "\e956";
} }
.icon-eye-open:before { &.icon-eye-open:before {
content: "\e957"; content: "\e957";
} }
.icon-book-pencil:before { &.icon-book-pencil:before {
content: "\e965"; content: "\e965";
} }
.icon-heart:before { &.icon-heart:before {
content: "\e9da"; content: "\e9da";
} }
.icon-loop2:before { &.icon-loop2:before {
content: "\ea2e"; content: "\ea2e";
} }
.icon-github:before { &.icon-github:before {
content: "\eab0"; content: "\eab0";
} }
.icon-tux:before { &.icon-tux:before {
content: "\eabd"; content: "\eabd";
} }
.icon-appleinc:before { &.icon-appleinc:before {
content: "\eabe"; content: "\eabe";
} }
.icon-windows8:before { &.icon-windows8:before {
content: "\eac2"; content: "\eac2";
}
} }

2
content/chronograf/v1.9/guides/advanced-kapacitor.md
View File

@ -33,7 +33,7 @@ of the default retention policy.
Use the Chronograf **Admin page** to modify the retention policy in the `chronograf` database. Use the Chronograf **Admin page** to modify the retention policy in the `chronograf` database.
In the Databases tab: In the Databases tab:
1. Click **{{< icon "crown" >}} InfluxDB Admin** in the left navigation bar. 1. Click **{{< icon "crown" "v2" >}} InfluxDB Admin** in the left navigation bar.
2. Hover over the retention policy list of the `chronograf` database and click **Edit** 2. Hover over the retention policy list of the `chronograf` database and click **Edit**
next to the retention policy to update. next to the retention policy to update.
3. Update the **Duration** of the retention policy. 3. Update the **Duration** of the retention policy.

4
content/chronograf/v1.9/guides/analyzing-logs.md
View File

@ -94,10 +94,10 @@ To copy the complete, un-truncated log message, select the message cell and clic
## Show or hide the log status histogram ## Show or hide the log status histogram
The Chronograf Log Viewer displays a histogram of log status. The Chronograf Log Viewer displays a histogram of log status.
**To hide the log status histogram**, click the **{{< icon "hide" >}} icon** in **To hide the log status histogram**, click the **{{< icon "hide" "v2" >}} icon** in
the top right corner of the histogram. the top right corner of the histogram.
**To show the log status histogram**, click the **{{< icon "bar-chart" >}} icon** **To show the log status histogram**, click the **{{< icon "bar-chart" "v2" >}} icon**
in the top right corner of the log output. in the top right corner of the log output.
## Logs in dashboards ## Logs in dashboards

2
content/chronograf/v1.9/guides/configuring-alert-endpoints.md
View File

@ -253,7 +253,7 @@ To enable a new "Generic API" service using TICKscript, see [AlertNode (Kapacito
1. In the **Configure Alert Endpoints** of the **Configure Kapacitor Connection** page, 1. In the **Configure Alert Endpoints** of the **Configure Kapacitor Connection** page,
click the **Slack** tab. click the **Slack** tab.
2. Click **{{< icon "plus" >}} Add Another Config**. 2. Click **{{< icon "plus" "v2" >}} Add Another Config**.
3. Complete steps 2-4 [above](#slack). 3. Complete steps 2-4 [above](#slack).
### SMTP ### SMTP

6
content/chronograf/v1.9/guides/create-a-dashboard.md
View File

@ -32,14 +32,14 @@ For more information, see [Configuring Chronograf](/chronograf/v1.9/administrati
## Build a dashboard ## Build a dashboard
1. #### Create a new dashboard 1. #### Create a new dashboard
Click **Dashboards** in the navigation bar and then click the **{{< icon "plus" >}} Create Dashboard** button. Click **Dashboards** in the navigation bar and then click the **{{< icon "plus" "v2" >}} Create Dashboard** button.
A new dashboard is created and ready to begin adding cells. A new dashboard is created and ready to begin adding cells.
2. #### Name your dashboard 2. #### Name your dashboard
Click **Name This Dashboard** and type a new name. For example, "ChronoDash". Click **Name This Dashboard** and type a new name. For example, "ChronoDash".
3. #### Enter cell editor mode 3. #### Enter cell editor mode
In the first cell, titled "Untitled Cell", click **{{< icon "plus" >}} Add Data** In the first cell, titled "Untitled Cell", click **{{< icon "plus" "v2" >}} Add Data**
to open the cell editor mode. to open the cell editor mode.
{{< img-hd src="/img/chronograf/1-9-dashboard-cell-add-data.png" alt="Add data to a Chronograf cell" />}} {{< img-hd src="/img/chronograf/1-9-dashboard-cell-add-data.png" alt="Add data to a Chronograf cell" />}}
@ -155,7 +155,7 @@ Select from a variety of dashboard templates to import and customize based on wh
### Full screen mode ### Full screen mode
View your dashboard in full screen mode by clicking on the full screen icon (**{{< icon "fullscreen" >}}**) in the top right corner of your dashboard. View your dashboard in full screen mode by clicking on the full screen icon (**{{< icon "fullscreen" "v2" >}}**) in the top right corner of your dashboard.
To exit full screen mode, press the Esc key. To exit full screen mode, press the Esc key.
### Template variables ### Template variables

6
content/chronograf/v1.9/guides/write-to-influxdb.md
View File

@ -19,7 +19,7 @@ Choose from the following methods:
## Upload line protocol through the Chronograf UI ## Upload line protocol through the Chronograf UI
1. Select **{{< icon "data-explorer" >}} Explore** in the left navigation bar. 1. Select **{{< icon "data-explorer" "v2" >}} Explore** in the left navigation bar.
2. Click **Write Data** in the top right corner of the Data Explorer. 2. Click **Write Data** in the top right corner of the Data Explorer.
{{< img-hd src="/img/chronograf/1-9-write-data.png" alt="Write data to InfluxDB with Chronograf" />}} {{< img-hd src="/img/chronograf/1-9-write-data.png" alt="Write data to InfluxDB with Chronograf" />}}
@ -53,7 +53,7 @@ To write data back to InfluxDB with an InfluxQL query, include the
[`INTO` clause](/{{< latest "influxdb" "v1" >}}/query_language/explore-data/#the-into-clause) [`INTO` clause](/{{< latest "influxdb" "v1" >}}/query_language/explore-data/#the-into-clause)
in your query: in your query:
1. Select **{{< icon "data-explorer" >}} Explore** in the left navigation bar. 1. Select **{{< icon "data-explorer" "v2" >}} Explore** in the left navigation bar.
2. Select **InfluxQL** as your data source type. 2. Select **InfluxQL** as your data source type.
3. Write an InfluxQL query that includes the `INTO` clause. Specify the database, 3. Write an InfluxQL query that includes the `INTO` clause. Specify the database,
retention policy, and measurement to write to. For example: retention policy, and measurement to write to. For example:
@ -80,7 +80,7 @@ To write data back to InfluxDB with an InfluxQL query, include the
[`INTO` clause](/{{< latest "influxdb" "v1" >}}/query_language/explore-data/#the-into-clause) [`INTO` clause](/{{< latest "influxdb" "v1" >}}/query_language/explore-data/#the-into-clause)
in your query: in your query:
1. Select **{{< icon "data-explorer" >}} Explore** in the left navigation bar. 1. Select **{{< icon "data-explorer" "v2" >}} Explore** in the left navigation bar.
2. Select **Flux** as your data source type. 2. Select **Flux** as your data source type.
{{% note %}} {{% note %}}

6
content/enterprise_influxdb/v1.9/administration/monitor/monitor-with-cloud.md
View File

@ -145,7 +145,7 @@ To alert when data stops flowing from InfluxDB OSS instances to your InfluxDB Cl
{{< nav-icon "alerts" >}} {{< nav-icon "alerts" >}}
2. Choose a InfluxDB OSS field or create a new OSS field for your deadman alert: 2. Choose a InfluxDB OSS field or create a new OSS field for your deadman alert:
1. Click **{{< icon "plus" >}} Create** and select **Deadman Check** in the dropown menu. 1. Click **{{< icon "plus" "v2" >}} Create** and select **Deadman Check** in the dropown menu.
2. Define your query with at least one field. 2. Define your query with at least one field.
3. Click **Submit** and **Configure Check**. 3. Click **Submit** and **Configure Check**.
When metrics stop reporting, you'll receive an alert. When metrics stop reporting, you'll receive an alert.
@ -164,7 +164,7 @@ InfluxDB Cloud supports different endpoints: Slack, PagerDuty, and HTTP. Slack i
#### Send a notification to Slack #### Send a notification to Slack
1. Create a [Slack Webhooks](https://api.slack.com/messaging/webhooks). 1. Create a [Slack Webhooks](https://api.slack.com/messaging/webhooks).
2. Go to **Alerts > Notification Endpoint** and click **{{< icon "plus" >}} Create**, and enter a name and description for your Slack endpoint. 2. Go to **Alerts > Notification Endpoint** and click **{{< icon "plus" "v2" >}} Create**, and enter a name and description for your Slack endpoint.
3. Enter your Slack Webhook under **Incoming Webhook URL** and click **Create Notification Endpoint**. 3. Enter your Slack Webhook under **Incoming Webhook URL** and click **Create Notification Endpoint**.
#### Send a notification to PagerDuty or HTTP #### Send a notification to PagerDuty or HTTP
@ -175,7 +175,7 @@ Send a notification to PagerDuty or HTTP endpoints (other webhooks) by [upgradin
[Create a notification rule](/influxdb/cloud/monitor-alert/notification-rules/create/) to set rules for when to send a deadman alert message to your notification endpoint. [Create a notification rule](/influxdb/cloud/monitor-alert/notification-rules/create/) to set rules for when to send a deadman alert message to your notification endpoint.
1. Go to **Alerts > Notification Rules** and click **{{< icon "plus" >}} Create**. 1. Go to **Alerts > Notification Rules** and click **{{< icon "plus" "v2" >}} Create**.
2. Fill out the **About** and **Conditions** section then click **Create Notification Rule**. 2. Fill out the **About** and **Conditions** section then click **Create Notification Rule**.
## Monitor with InfluxDB Insights and Aware ## Monitor with InfluxDB Insights and Aware

6
content/enterprise_influxdb/v1.9/administration/monitor/monitor-with-oss.md
View File

@ -145,7 +145,7 @@ To alert when data stops flowing from InfluxDB OSS instances to your InfluxDB OS
{{< nav-icon "alerts" >}} {{< nav-icon "alerts" >}}
2. Choose a InfluxDB OSS field or create a new OSS field for your deadman alert: 2. Choose a InfluxDB OSS field or create a new OSS field for your deadman alert:
1. Click **{{< icon "plus" >}} Create** and select **Deadman Check** in the dropown menu. 1. Click **{{< icon "plus" "v2" >}} Create** and select **Deadman Check** in the dropown menu.
2. Define your query with at least one field. 2. Define your query with at least one field.
3. Click **Submit** and **Configure Check**. 3. Click **Submit** and **Configure Check**.
When metrics stop reporting, you'll receive an alert. When metrics stop reporting, you'll receive an alert.
@ -164,7 +164,7 @@ InfluxData supports different endpoints: Slack, PagerDuty, and HTTP. Slack is fr
#### Send a notification to Slack #### Send a notification to Slack
1. Create a [Slack Webhooks](https://api.slack.com/messaging/webhooks). 1. Create a [Slack Webhooks](https://api.slack.com/messaging/webhooks).
2. Go to **Alerts > Notification Endpoint** and click **{{< icon "plus" >}} Create**, and enter a name and description for your Slack endpoint. 2. Go to **Alerts > Notification Endpoint** and click **{{< icon "plus" "v2" >}} Create**, and enter a name and description for your Slack endpoint.
3. Enter your Slack Webhook under **Incoming Webhook URL** and click **Create Notification Endpoint**. 3. Enter your Slack Webhook under **Incoming Webhook URL** and click **Create Notification Endpoint**.
#### Send a notification to PagerDuty or HTTP #### Send a notification to PagerDuty or HTTP
@ -175,5 +175,5 @@ Send a notification to PagerDuty or HTTP endpoints (other webhooks) by [upgradin
[Create a notification rule](/influxdb/v2.0/monitor-alert/notification-rules/create/) to set rules for when to send a deadman alert message to your notification endpoint. [Create a notification rule](/influxdb/v2.0/monitor-alert/notification-rules/create/) to set rules for when to send a deadman alert message to your notification endpoint.
1. Go to **Alerts > Notification Rules** and click **{{< icon "plus" >}} Create**. 1. Go to **Alerts > Notification Rules** and click **{{< icon "plus" "v2" >}} Create**.
2. Fill out the **About** and **Conditions** section then click **Create Notification Rule**. 2. Fill out the **About** and **Conditions** section then click **Create Notification Rule**.

44
content/enterprise_influxdb/v1.9/flux/optimize-queries.md
View File

@ -29,29 +29,29 @@ The following pushdowns are supported in InfluxDB Enterprise 1.9+.
| Functions | Supported | | Functions | Supported |
| :----------------------------- | :------------------: | | :----------------------------- | :------------------: |
| **count()** | {{< icon "check" >}} | | **count()** | {{< icon "check" "v2" >}} |
| **drop()** | {{< icon "check" >}} | | **drop()** | {{< icon "check" "v2" >}} |
| **duplicate()** | {{< icon "check" >}} | | **duplicate()** | {{< icon "check" "v2" >}} |
| **filter()** {{% req " \*" %}} | {{< icon "check" >}} | | **filter()** {{% req " \*" %}} | {{< icon "check" "v2" >}} |
| **fill()** | {{< icon "check" >}} | | **fill()** | {{< icon "check" "v2" >}} |
| **first()** | {{< icon "check" >}} | | **first()** | {{< icon "check" "v2" >}} |
| **group()** | {{< icon "check" >}} | | **group()** | {{< icon "check" "v2" >}} |
| **keep()** | {{< icon "check" >}} | | **keep()** | {{< icon "check" "v2" >}} |
| **last()** | {{< icon "check" >}} | | **last()** | {{< icon "check" "v2" >}} |
| **max()** | {{< icon "check" >}} | | **max()** | {{< icon "check" "v2" >}} |
| **mean()** | {{< icon "check" >}} | | **mean()** | {{< icon "check" "v2" >}} |
| **min()** | {{< icon "check" >}} | | **min()** | {{< icon "check" "v2" >}} |
| **range()** | {{< icon "check" >}} | | **range()** | {{< icon "check" "v2" >}} |
| **rename()** | {{< icon "check" >}} | | **rename()** | {{< icon "check" "v2" >}} |
| **sum()** | {{< icon "check" >}} | | **sum()** | {{< icon "check" "v2" >}} |
| **window()** | {{< icon "check" >}} | | **window()** | {{< icon "check" "v2" >}} |
| _Function combinations_ | | | _Function combinations_ | |
| **window()** \|> **count()** | {{< icon "check" >}} | | **window()** \|> **count()** | {{< icon "check" "v2" >}} |
| **window()** \|> **first()** | {{< icon "check" >}} | | **window()** \|> **first()** | {{< icon "check" "v2" >}} |
| **window()** \|> **last()** | {{< icon "check" >}} | | **window()** \|> **last()** | {{< icon "check" "v2" >}} |
| **window()** \|> **max()** | {{< icon "check" >}} | | **window()** \|> **max()** | {{< icon "check" "v2" >}} |
| **window()** \|> **min()** | {{< icon "check" >}} | | **window()** \|> **min()** | {{< icon "check" "v2" >}} |
| **window()** \|> **sum()** | {{< icon "check" >}} | | **window()** \|> **sum()** | {{< icon "check" "v2" >}} |
{{% caption %}} {{% caption %}}
{{< req "\*" >}} **filter()** only pushes down when all parameter values are static. {{< req "\*" >}} **filter()** only pushes down when all parameter values are static.

126
content/example.md
View File

@ -10,7 +10,7 @@ related:
products: [cloud, oss, enterprise] products: [cloud, oss, enterprise]
--- ---
This is a paragraph. Lorem ipsum dolor ({{< icon "trash" >}}) sit amet, consectetur adipiscing elit. Nunc rutrum, metus id scelerisque euismod, erat ante suscipit nibh, ac congue enim risus id est. Etiam tristique nisi et tristique auctor. Morbi eu bibendum erat. Sed ullamcorper, dui id lobortis efficitur, mauris odio pharetra neque, vel tempor odio dolor blandit justo. This is a paragraph. Lorem ipsum dolor ({{< icon "trash" "v2" >}}) sit amet, consectetur adipiscing elit. Nunc rutrum, metus id scelerisque euismod, erat ante suscipit nibh, ac congue enim risus id est. Etiam tristique nisi et tristique auctor. Morbi eu bibendum erat. Sed ullamcorper, dui id lobortis efficitur, mauris odio pharetra neque, vel tempor odio dolor blandit justo.
[Ref link][foo] [Ref link][foo]
@ -28,68 +28,68 @@ This is **bold** text. This is _italic_ text. This is _**bold and italic**_.
{{< nav-icon "settings" >}} {{< nav-icon "settings" >}}
{{< nav-icon "notebooks" >}} {{< nav-icon "notebooks" >}}
{{< icon "add-cell" >}} add-cell {{< icon "add-cell" "v2" >}} add-cell
{{< icon "add-label" >}} add-label {{< icon "add-label" "v2" >}} add-label
{{< icon "alert" >}} alert {{< icon "alert" "v2" >}} alert
{{< icon "calendar" >}} calendar {{< icon "calendar" "v2" >}} calendar
{{< icon "chat" >}} chat {{< icon "chat" "v2" >}} chat
{{< icon "checkmark" >}} checkmark {{< icon "checkmark" "v2" >}} checkmark
{{< icon "clone" >}} clone {{< icon "clone" "v2" >}} clone
{{< icon "cloud" >}} cloud {{< icon "cloud" "v2" >}} cloud
{{< icon "cog" >}} cog {{< icon "cog" "v2" >}} cog
{{< icon "config" >}} config {{< icon "config" "v2" >}} config
{{< icon "copy" >}} copy {{< icon "copy" "v2" >}} copy
{{< icon "crown" >}} crown {{< icon "crown" "v2" >}} crown
{{< icon "dashboard" >}} dashboard {{< icon "dashboard" "v2" >}} dashboard
{{< icon "dashboards" >}} dashboards {{< icon "dashboards" "v2" >}} dashboards
{{< icon "data-explorer" >}} data-explorer {{< icon "data-explorer" "v2" >}} data-explorer
{{< icon "delete" >}} delete {{< icon "delete" "v2" >}} delete
{{< icon "download" >}} download {{< icon "download" "v2" >}} download
{{< icon "duplicate" >}} duplicate {{< icon "duplicate" "v2" >}} duplicate
{{< icon "edit" >}} edit {{< icon "edit" "v2" >}} edit
{{< icon "expand" >}} expand {{< icon "expand" "v2" >}} expand
{{< icon "export" >}} export {{< icon "export" "v2" >}} export
{{< icon "eye" >}} eye {{< icon "eye" "v2" >}} eye
{{< icon "eye-closed" >}} eye-closed {{< icon "eye-closed" "v2" >}} eye-closed
{{< icon "eye-open" >}} eye-open {{< icon "eye-open" "v2" >}} eye-open
{{< icon "feedback" >}} feedback {{< icon "feedback" "v2" >}} feedback
{{< icon "fullscreen" >}} fullscreen {{< icon "fullscreen" "v2" >}} fullscreen
{{< icon "gear" >}} gear {{< icon "gear" "v2" >}} gear
{{< icon "graph" >}} graph {{< icon "graph" "v2" >}} graph
{{< icon "hide" >}} hide {{< icon "hide" "v2" >}} hide
{{< icon "influx" >}} influx {{< icon "influx" "v2" >}} influx
{{< icon "influx-icon" >}} influx-icon {{< icon "influx-icon" "v2" >}} influx-icon
{{< icon "nav-admin" >}} nav-admin {{< icon "nav-admin" "v2" >}} nav-admin
{{< icon "nav-config" >}} nav-config {{< icon "nav-config" "v2" >}} nav-config
{{< icon "nav-configuration" >}} nav-configuration {{< icon "nav-configuration" "v2" >}} nav-configuration
{{< icon "nav-dashboards" >}} nav-dashboards {{< icon "nav-dashboards" "v2" >}} nav-dashboards
{{< icon "nav-data-explorer" >}} nav-data-explorer {{< icon "nav-data-explorer" "v2" >}} nav-data-explorer
{{< icon "nav-organizations" >}} nav-organizations {{< icon "nav-organizations" "v2" >}} nav-organizations
{{< icon "nav-orgs" >}} nav-orgs {{< icon "nav-orgs" "v2" >}} nav-orgs
{{< icon "nav-tasks" >}} nav-tasks {{< icon "nav-tasks" "v2" >}} nav-tasks
{{< icon "note" >}} note {{< icon "note" "v2" >}} note
{{< icon "notebook" >}} notebook {{< icon "notebook" "v2" >}} notebook
{{< icon "notebooks" >}} notebooks {{< icon "notebooks" "v2" >}} notebooks
{{< icon "org" >}} org {{< icon "org" "v2" >}} org
{{< icon "orgs" >}} orgs {{< icon "orgs" "v2" >}} orgs
{{< icon "pause" >}} pause {{< icon "pause" "v2" >}} pause
{{< icon "pencil" >}} pencil {{< icon "pencil" "v2" >}} pencil
{{< icon "play" >}} play {{< icon "play" "v2" >}} play
{{< icon "plus" >}} plus {{< icon "plus" "v2" >}} plus
{{< icon "refresh" >}} refresh {{< icon "refresh" "v2" >}} refresh
{{< icon "remove" >}} remove {{< icon "remove" "v2" >}} remove
{{< icon "replay" >}} replay {{< icon "replay" "v2" >}} replay
{{< icon "save-as" >}} save-as {{< icon "save-as" "v2" >}} save-as
{{< icon "search" >}} search {{< icon "search" "v2" >}} search
{{< icon "settings" >}} settings {{< icon "settings" "v2" >}} settings
{{< icon "tasks" >}} tasks {{< icon "tasks" "v2" >}} tasks
{{< icon "toggle" >}} toggle {{< icon "toggle" "v2" >}} toggle
{{< icon "trash" >}} trash {{< icon "trash" "v2" >}} trash
{{< icon "trashcan" >}} trashcan {{< icon "trashcan" "v2" >}} trashcan
{{< icon "triangle" >}} triangle {{< icon "triangle" "v2" >}} triangle
{{< icon "view" >}} view {{< icon "view" "v2" >}} view
{{< icon "wrench" >}} wrench {{< icon "wrench" "v2" >}} wrench
{{< icon "x" >}} x {{< icon "x" "v2" >}} x
## h2 This is a header2 ## h2 This is a header2
This is a paragraph. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc rutrum, metus id scelerisque euismod, erat ante suscipit nibh, ac congue enim risus id est. Etiam tristique nisi et tristique auctor. Morbi eu bibendum erat. Sed ullamcorper, dui id lobortis efficitur, mauris odio pharetra neque, vel tempor odio dolor blandit justo. This is a paragraph. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc rutrum, metus id scelerisque euismod, erat ante suscipit nibh, ac congue enim risus id est. Etiam tristique nisi et tristique auctor. Morbi eu bibendum erat. Sed ullamcorper, dui id lobortis efficitur, mauris odio pharetra neque, vel tempor odio dolor blandit justo.

2
content/influxdb/cloud/account-management/multi-user/invite-user.md
View File

@ -46,7 +46,7 @@ Accounts can have up to 50 pending invitations at one time.
{{< nav-icon "account" >}} {{< nav-icon "account" >}}
2. Click the {{< icon "delete" >}} next to the invitation you want to withdraw. 2. Click the {{< icon "delete" "v2" >}} next to the invitation you want to withdraw.
3. Confirm the withdrawl. 3. Confirm the withdrawl.
{{% warn %}} {{% warn %}}

2
content/influxdb/cloud/account-management/multi-user/remove-user.md
View File

@ -28,7 +28,7 @@ Delete a single-user organization from one of the following:
{{< nav-icon "account" >}} {{< nav-icon "account" >}}
2. Hover over the user you want to remove and then click the {{< icon "delete" >}} icon that appears. 2. Hover over the user you want to remove and then click the {{< icon "delete" "v2" >}} icon that appears.
3. Confirm the removal. 3. Confirm the removal.
#### Usage-based plan #### Usage-based plan

6
content/influxdb/cloud/get-started.md
View File

@ -34,7 +34,7 @@ This example uses InfluxDB Cloud's Website Monitoring demo data bucket. To add t
{{< nav-icon "data" >}} {{< nav-icon "data" >}}
2. Click **{{< icon "plus" >}} Add Demo Data**, and then select the **Website Monitoring** bucket. 2. Click **{{< icon "plus" "v2" >}} Add Demo Data**, and then select the **Website Monitoring** bucket.
3. The Demo Data bucket appears in your list of buckets. 3. The Demo Data bucket appears in your list of buckets.
## Add sample data ## Add sample data
@ -107,7 +107,7 @@ By default, a visualization cell appears below your initial metric selector cell
1. Use the function dropdown menu to view different functions to apply to your data. By default, the visualization is set to the mean function. 1. Use the function dropdown menu to view different functions to apply to your data. By default, the visualization is set to the mean function.
2. Use the visualization type dropdown to view different visualization types available. 2. Use the visualization type dropdown to view different visualization types available.
For a complete list of options, see [Visualization types](/influxdb/cloud/visualize-data/visualization-types/). For a complete list of options, see [Visualization types](/influxdb/cloud/visualize-data/visualization-types/).
3. Click the gear icon ({{< icon "gear" >}}) to edit specific settings for the visualization type, such as colors, orientation, and labels. 3. Click the gear icon ({{< icon "gear" "v2" >}}) to edit specific settings for the visualization type, such as colors, orientation, and labels.
### Process data ### Process data
@ -124,7 +124,7 @@ For more information on how to process data, see [here](/influxdb/cloud/process-
Get notifications every time your data crosses a threshold. Specify your alerts by time and decide how the information will be sent to you. Get notifications every time your data crosses a threshold. Specify your alerts by time and decide how the information will be sent to you.
1. In your notebook, click **{{< icon "plus" >}}** to add a cell, then select **Output > Alert**. 1. In your notebook, click **{{< icon "plus" "v2" >}}** to add a cell, then select **Output > Alert**.
2. Customize the conditions to send an alert. 2. Customize the conditions to send an alert.
3. Enter a time range to automatically check the data and enter your query offset. 3. Enter a time range to automatically check the data and enter your query offset.
4. Select an endpoint to receive an alert: 4. Select an endpoint to receive an alert:

6
content/influxdb/cloud/influxdb-templates/monitor-enterprise.md
View File

@ -144,7 +144,7 @@ To alert when data stops flowing from InfluxDB OSS instances to your InfluxDB Cl
{{< nav-icon "alerts" >}} {{< nav-icon "alerts" >}}
2. Choose a InfluxDB OSS field or create a new OSS field for your deadman alert: 2. Choose a InfluxDB OSS field or create a new OSS field for your deadman alert:
1. Click **{{< icon "plus" >}} Create** and select **Deadman Check** in the dropown menu. 1. Click **{{< icon "plus" "v2" >}} Create** and select **Deadman Check** in the dropown menu.
2. Define your query with at least one field. 2. Define your query with at least one field.
3. Click **Submit** and **Configure Check**. 3. Click **Submit** and **Configure Check**.
When metrics stop reporting, you'll receive an alert. When metrics stop reporting, you'll receive an alert.
@ -163,7 +163,7 @@ InfluxData supports different endpoints: Slack, PagerDuty, and HTTP. Slack is fr
#### Send a notification to Slack #### Send a notification to Slack
1. Create a [Slack Webhooks](https://api.slack.com/messaging/webhooks). 1. Create a [Slack Webhooks](https://api.slack.com/messaging/webhooks).
2. Go to **Alerts > Notification Endpoint** and click **{{< icon "plus" >}} Create**, and enter a name and description for your Slack endpoint. 2. Go to **Alerts > Notification Endpoint** and click **{{< icon "plus" "v2" >}} Create**, and enter a name and description for your Slack endpoint.
3. Enter your Slack Webhook under **Incoming Webhook URL** and click **Create Notification Endpoint**. 3. Enter your Slack Webhook under **Incoming Webhook URL** and click **Create Notification Endpoint**.
#### Send a notification to PagerDuty or HTTP #### Send a notification to PagerDuty or HTTP
@ -174,7 +174,7 @@ Send a notification to PagerDuty or HTTP endpoints (other webhooks) by [upgradin
[Create a notification rule](/influxdb/cloud/monitor-alert/notification-rules/create/) to set rules for when to send a deadman alert message to your notification endpoint. [Create a notification rule](/influxdb/cloud/monitor-alert/notification-rules/create/) to set rules for when to send a deadman alert message to your notification endpoint.
1. Go to **Alerts > Notification Rules** and click **{{< icon "plus" >}} Create**. 1. Go to **Alerts > Notification Rules** and click **{{< icon "plus" "v2" >}} Create**.
2. Fill out the **About** and **Conditions** section then click **Create Notification Rule**. 2. Fill out the **About** and **Conditions** section then click **Create Notification Rule**.
## Monitor with InfluxDB Insights and Aware ## Monitor with InfluxDB Insights and Aware

8
content/influxdb/cloud/monitor-alert/checks/create.md
View File

@ -47,7 +47,7 @@ in a specified amount of time.
{{< nav-icon "alerts" >}} {{< nav-icon "alerts" >}}
2. Click **{{< icon "plus" >}} Create** and select the [type of check](#check-types) to create. 2. Click **{{< icon "plus" "v2" >}} Create** and select the [type of check](#check-types) to create.
3. Click **Name this check** in the top left corner and provide a unique name for the check. 3. Click **Name this check** in the top left corner and provide a unique name for the check.
#### Configure the check query #### Configure the check query
@ -60,7 +60,7 @@ in a specified amount of time.
(for example, "Every 5 minutes") and an aggregate function from the list of functions. (for example, "Every 5 minutes") and an aggregate function from the list of functions.
3. Click **Submit** to run the query and preview the results. 3. Click **Submit** to run the query and preview the results.
To see the raw query results, click the **{{< icon "toggle" >}} View Raw Data** toggle. To see the raw query results, click the **{{< icon "toggle" "v2" >}} View Raw Data** toggle.
#### Configure the check #### Configure the check
1. Click **2. Configure Check** near the top of the window. 1. Click **2. Configure Check** near the top of the window.
@ -143,10 +143,10 @@ count = 12
3. In the **And stop checking after** field, enter the time to stop monitoring the series. 3. In the **And stop checking after** field, enter the time to stop monitoring the series.
For example, `30m`, `2h`, `3h15m`, etc. For example, `30m`, `2h`, `3h15m`, etc.
5. Click the green **{{< icon "check" >}}** in the top right corner to save the check. 5. Click the green **{{< icon "check" "v2" >}}** in the top right corner to save the check.
## Clone a check ## Clone a check
Create a new check by cloning an existing check. Create a new check by cloning an existing check.
1. In the **Checks** column, hover over the check you want to clone. 1. In the **Checks** column, hover over the check you want to clone.
2. Click the **{{< icon "clone" >}}** icon, then **Clone**. 2. Click the **{{< icon "clone" "v2" >}}** icon, then **Clone**.

2
content/influxdb/cloud/monitor-alert/checks/delete.md
View File

@ -22,7 +22,7 @@ Deleting a check cannot be undone.
{{< nav-icon "alerts" >}} {{< nav-icon "alerts" >}}
2. Hover over the check you want to delete, click the **{{< icon "delete" >}}** 2. Hover over the check you want to delete, click the **{{< icon "delete" "v2" >}}**
icon, and then **Delete**. icon, and then **Delete**.
After a check is deleted, all statuses generated by the check remain in the `_monitoring` After a check is deleted, all statuses generated by the check remain in the `_monitoring`

8
content/influxdb/cloud/monitor-alert/checks/update.md
View File

@ -34,18 +34,18 @@ To update checks, select **Alerts** in the navigation menu on the left.
_For details about using the check builder, see [Create checks](/influxdb/cloud/monitor-alert/checks/create/)._ _For details about using the check builder, see [Create checks](/influxdb/cloud/monitor-alert/checks/create/)._
## Enable or disable a check ## Enable or disable a check
Click the {{< icon "toggle" >}} toggle next to a check to enable or disable it. Click the {{< icon "toggle" "v2" >}} toggle next to a check to enable or disable it.
## Rename a check ## Rename a check
1. Hover over the name of the check you want to update. 1. Hover over the name of the check you want to update.
2. Click the **{{< icon "edit" >}}** icon that appears next to the check name. 2. Click the **{{< icon "edit" "v2" >}}** icon that appears next to the check name.
2. Enter a new name and click out of the name field or press enter to save. 2. Enter a new name and click out of the name field or press enter to save.
_You can also rename a check in the [check builder](#update-check-queries-and-logic)._ _You can also rename a check in the [check builder](#update-check-queries-and-logic)._
## Add or update a check description ## Add or update a check description
1. Hover over the check description you want to update. 1. Hover over the check description you want to update.
2. Click the **{{< icon "edit" >}}** icon that appears next to the description. 2. Click the **{{< icon "edit" "v2" >}}** icon that appears next to the description.
2. Enter a new description and click out of the name field or press enter to save. 2. Enter a new description and click out of the name field or press enter to save.
## Add a label to a check ## Add a label to a check
@ -57,4 +57,4 @@ _You can also rename a check in the [check builder](#update-check-queries-and-lo
- In the **Description** field, enter an optional description for the label. - In the **Description** field, enter an optional description for the label.
- Select a color for the label. - Select a color for the label.
- Click **Create Label**. - Click **Create Label**.
4. To remove a label, hover over the label under to a rule and click **{{< icon "x" >}}**. 4. To remove a label, hover over the label under to a rule and click **{{< icon "x" "v2" >}}**.

4
content/influxdb/cloud/monitor-alert/checks/view.md
View File

@ -32,12 +32,12 @@ The check builder appears.
Here you can view the check query and logic. Here you can view the check query and logic.
## View statuses generated by a check ## View statuses generated by a check
1. Hover over the check and click the **{{< icon "view" >}}** icon. 1. Hover over the check and click the **{{< icon "view" "v2" >}}** icon.
2. Click **View History**. 2. Click **View History**.
The Statuses History page displays statuses generated by the selected check. The Statuses History page displays statuses generated by the selected check.
## View notifications triggered by a check ## View notifications triggered by a check
1. Hover over the check, click the **{{< icon "view" >}}** 1. Hover over the check, click the **{{< icon "view" "v2" >}}**
icon, then **View History**. icon, then **View History**.
2. In the top left corner, click **Notifications**. 2. In the top left corner, click **Notifications**.
The Notifications History page displays notifications initiated by the selected check. The Notifications History page displays notifications initiated by the selected check.

2
content/influxdb/cloud/monitor-alert/custom-checks.md
View File

@ -25,7 +25,7 @@ Using a Flux task, you can create a custom check that provides a couple advantag
{{< nav-icon "tasks" >}} {{< nav-icon "tasks" >}}
2. Click **{{< icon "plus" >}} Create Task**, and then select **New Task**. 2. Click **{{< icon "plus" "v2" >}} Create Task**, and then select **New Task**.
3. In the **Name** field, enter a descriptive name, 3. In the **Name** field, enter a descriptive name,
and then enter how often to run the task in the **Every** field (for example, `10m`). and then enter how often to run the task in the **Every** field (for example, `10m`).
For more detail, such as using cron syntax or including an offset, see [Task configuration options](/influxdb/cloud/process-data/task-options/). For more detail, such as using cron syntax or including an offset, see [Task configuration options](/influxdb/cloud/process-data/task-options/).

8
content/influxdb/cloud/monitor-alert/notification-endpoints/create.md
View File

@ -21,15 +21,15 @@ To send notifications about changes in your data, start by creating a notificati
{{< nav-icon "alerts" >}} {{< nav-icon "alerts" >}}
2. Select **Notification Endpoints** near to top of the page. 2. Select **Notification Endpoints** near to top of the page.
3. Click **{{< icon "plus" >}} Create**. 3. Click **{{< icon "plus" "v2" >}} Create**.
4. From the **Destination** drop-down list, select a destination endpoint to send notifications. 4. From the **Destination** drop-down list, select a destination endpoint to send notifications.
The following endpoints are available for the InfluxDB Cloud Free Plan and Usage-based Plan: The following endpoints are available for the InfluxDB Cloud Free Plan and Usage-based Plan:
| Endpoint | Free Plan | Usage-based Plan | | Endpoint | Free Plan | Usage-based Plan |
|:-------- |:-------------------: |:----------------------------:| |:-------- |:-------------------: |:----------------------------:|
| **Slack** | **{{< icon "check" >}}** | **{{< icon "check" >}}** | | **Slack** | **{{< icon "check" "v2" >}}** | **{{< icon "check" "v2" >}}** |
| **PagerDuty** | | **{{< icon "check" >}}** | | **PagerDuty** | | **{{< icon "check" "v2" >}}** |
| **HTTP** | | **{{< icon "check" >}}** | | **HTTP** | | **{{< icon "check" "v2" >}}** |
5. In the **Name** and **Description** fields, enter a name and description for the endpoint. 5. In the **Name** and **Description** fields, enter a name and description for the endpoint.
6. Enter enter information to connect to the endpoint: 6. Enter enter information to connect to the endpoint:

2
content/influxdb/cloud/monitor-alert/notification-endpoints/delete.md
View File

@ -22,5 +22,5 @@ If notifications are no longer sent to an endpoint, complete the steps below to
2. Select **Notification Endpoints** near to top of the page. 2. Select **Notification Endpoints** near to top of the page.
find the rule you want to delete. find the rule you want to delete.
3. Hover over the endpoint you want to delete and click the **{{< icon "trash" >}}** icon. 3. Hover over the endpoint you want to delete and click the **{{< icon "trash" "v2" >}}** icon.
4. Click **Delete** to confirm. 4. Click **Delete** to confirm.

6
content/influxdb/cloud/monitor-alert/notification-endpoints/update.md
View File

@ -21,7 +21,7 @@ To update the notification endpoint details, complete the procedures below as ne
{{< nav-icon "alerts" >}} {{< nav-icon "alerts" >}}
2. Select **Notification Endpoints** near to top of the page. 2. Select **Notification Endpoints** near to top of the page.
3. Click **{{< icon "add-label" >}} Add a label** next to the endpoint you want to add a label to. 3. Click **{{< icon "add-label" "v2" >}} Add a label** next to the endpoint you want to add a label to.
The **Add Labels** box opens. The **Add Labels** box opens.
4. To add an existing label, select the label from the list. 4. To add an existing label, select the label from the list.
5. To create and add a new label: 5. To create and add a new label:
@ -41,7 +41,7 @@ To update the notification endpoint details, complete the procedures below as ne
{{< nav-icon "alerts" >}} {{< nav-icon "alerts" >}}
2. Select **Notification Endpoints** near to top of the page. 2. Select **Notification Endpoints** near to top of the page.
3. Click the {{< icon "toggle" >}} toggle to disable the notification endpoint. 3. Click the {{< icon "toggle" "v2" >}} toggle to disable the notification endpoint.
## Update the name or description for notification endpoint ## Update the name or description for notification endpoint
@ -51,7 +51,7 @@ To update the notification endpoint details, complete the procedures below as ne
2. Select **Notification Endpoints** near to top of the page. 2. Select **Notification Endpoints** near to top of the page.
3. Hover over the name or description of the endpoint and click the pencil icon 3. Hover over the name or description of the endpoint and click the pencil icon
(**{{< icon "edit" >}}**) to edit the field. (**{{< icon "edit" "v2" >}}**) to edit the field.
4. Click outside of the field to save your changes. 4. Click outside of the field to save your changes.
## Change endpoint details ## Change endpoint details

2
content/influxdb/cloud/monitor-alert/notification-endpoints/view.md
View File

@ -44,7 +44,7 @@ View notification endpoint details and history in the InfluxDB user interface (U
{{< nav-icon "alerts" >}} {{< nav-icon "alerts" >}}
2. Select **Notification Endpoints** near to top of the page. 2. Select **Notification Endpoints** near to top of the page.
3. Hover over the notification endpoint, click the **{{< icon "view" >}}** icon, then **View History**. 3. Hover over the notification endpoint, click the **{{< icon "view" "v2" >}}** icon, then **View History**.
The Check Statuses History page displays: The Check Statuses History page displays:
- Statuses generated for the selected notification endpoint - Statuses generated for the selected notification endpoint

4
content/influxdb/cloud/monitor-alert/notification-rules/create.md
View File

@ -22,7 +22,7 @@ _For details, see [Manage checks](/influxdb/cloud/monitor-alert/checks/) and
{{< nav-icon "alerts" >}} {{< nav-icon "alerts" >}}
2. Select **Notification Rules** near to top of the page. 2. Select **Notification Rules** near to top of the page.
3. Click **{{< icon "plus" >}} Create**. 3. Click **{{< icon "plus" "v2" >}} Create**.
4. Complete the **About** section: 4. Complete the **About** section:
1. In the **Name** field, enter a name for the notification rule. 1. In the **Name** field, enter a name for the notification rule.
2. In the **Schedule Every** field, enter how frequently the rule should run. 2. In the **Schedule Every** field, enter how frequently the rule should run.
@ -40,5 +40,5 @@ _For details, see [Manage checks](/influxdb/cloud/monitor-alert/checks/) and
{{< nav-icon "alerts" >}} {{< nav-icon "alerts" >}}
2. Select **Notification Rules** near to top of the page. 2. Select **Notification Rules** near to top of the page.
3. Hover over the rule you want to clone and click the **{{< icon "clone" >}}** icon and select **Clone**. 3. Hover over the rule you want to clone and click the **{{< icon "clone" "v2" >}}** icon and select **Clone**.
The cloned rule appears. The cloned rule appears.

2
content/influxdb/cloud/monitor-alert/notification-rules/delete.md
View File

@ -18,5 +18,5 @@ related:
{{< nav-icon "alerts" >}} {{< nav-icon "alerts" >}}
2. Select **Notification Rules** near to top of the page. 2. Select **Notification Rules** near to top of the page.
3. Hover over the rule you want to delete and click the **{{< icon "trash" >}}** icon. 3. Hover over the rule you want to delete and click the **{{< icon "trash" "v2" >}}** icon.
4. Click **Delete** to confirm. 4. Click **Delete** to confirm.

8
content/influxdb/cloud/monitor-alert/notification-rules/update.md
View File

@ -18,7 +18,7 @@ related:
{{< nav-icon "alerts" >}} {{< nav-icon "alerts" >}}
2. Select **Notification Rules** near to top of the page. 2. Select **Notification Rules** near to top of the page.
3. Click **{{< icon "add-label" >}} Add a label** next to the rule you want to add a label to. 3. Click **{{< icon "add-label" "v2" >}} Add a label** next to the rule you want to add a label to.
The **Add Labels** box opens. The **Add Labels** box opens.
4. To add an existing label, select the label from the list. 4. To add an existing label, select the label from the list.
5. To create and add a new label: 5. To create and add a new label:
@ -26,7 +26,7 @@ related:
- In the **Description** field, enter an optional description for the label. - In the **Description** field, enter an optional description for the label.
- Select a color for the label. - Select a color for the label.
- Click **Create Label**. - Click **Create Label**.
6. To remove a label, hover over the label under to a rule and click **{{< icon "x" >}}**. 6. To remove a label, hover over the label under to a rule and click **{{< icon "x" "v2" >}}**.
## Disable notification rules ## Disable notification rules
@ -36,7 +36,7 @@ related:
{{< nav-icon "alerts" >}} {{< nav-icon "alerts" >}}
2. Select **Notification Rules** near to top of the page. 2. Select **Notification Rules** near to top of the page.
3. Click the {{< icon "toggle" >}} toggle to disable the notification rule. 3. Click the {{< icon "toggle" "v2" >}} toggle to disable the notification rule.
## Update the name or description for notification rules ## Update the name or description for notification rules
@ -46,5 +46,5 @@ related:
2. Select **Notification Rules** near to top of the page. 2. Select **Notification Rules** near to top of the page.
3. Hover over the name or description of a rule and click the pencil icon 3. Hover over the name or description of a rule and click the pencil icon
(**{{< icon "edit" >}}**) to edit the field. (**{{< icon "edit" "v2" >}}**) to edit the field.
4. Click outside of the field to save your changes. 4. Click outside of the field to save your changes.

4
content/influxdb/cloud/monitor-alert/notification-rules/view.md
View File

@ -35,11 +35,11 @@ The check builder appears.
Here you can view the check query and logic. Here you can view the check query and logic.
## View statuses generated by a notification rule ## View statuses generated by a notification rule
Hover over the check, click the **{{< icon "view" >}}** icon, and then **View History**. Hover over the check, click the **{{< icon "view" "v2" >}}** icon, and then **View History**.
The Statuses History page displays statuses generated by the selected check. The Statuses History page displays statuses generated by the selected check.
## View notifications triggered by a notification rule ## View notifications triggered by a notification rule
1. Hover over the notification rule, click the **{{< icon "view" >}}** 1. Hover over the notification rule, click the **{{< icon "view" "v2" >}}**
icon, and then **View History**. icon, and then **View History**.
2. In the top left corner, click **Notifications**. 2. In the top left corner, click **Notifications**.
The Notifications History page displays notifications initiated by the selected notification rule. The Notifications History page displays notifications initiated by the selected notification rule.

2
content/influxdb/cloud/organizations/buckets/create-bucket.md
View File

@ -22,7 +22,7 @@ There are two places you can create a bucket in the UI.
{{< nav-icon "data" >}} {{< nav-icon "data" >}}
2. Click **{{< icon "plus" >}} Create Bucket** in the upper right. 2. Click **{{< icon "plus" "v2" >}} Create Bucket** in the upper right.
3. Enter a **Name** for the bucket. 3. Enter a **Name** for the bucket.
4. Select when to **Delete Data**: 4. Select when to **Delete Data**:
- **Never** to retain data forever. - **Never** to retain data forever.

2
content/influxdb/cloud/organizations/buckets/delete-bucket.md
View File

@ -19,7 +19,7 @@ to delete a bucket.
{{< nav-icon "data" >}} {{< nav-icon "data" >}}
2. Hover over the bucket you would like to delete. 2. Hover over the bucket you would like to delete.
3. Click **{{< icon "delete" >}} Delete Bucket** and **Confirm** to delete the bucket. 3. Click **{{< icon "delete" "v2" >}} Delete Bucket** and **Confirm** to delete the bucket.
## Delete a bucket using the influx CLI ## Delete a bucket using the influx CLI

2
content/influxdb/cloud/organizations/members/remove-member.md
View File

@ -23,7 +23,7 @@ Removing a member from an organization removes all permissions associated with t
{{< nav-icon "org" >}} {{< nav-icon "org" >}}
2. Hover over the member you would like to delete and click the **{{< icon "delete" >}}** icon. 2. Hover over the member you would like to delete and click the **{{< icon "delete" "v2" >}}** icon.
3. Click **Delete**. 3. Click **Delete**.
## Remove a member from an organization using the influx CLI ## Remove a member from an organization using the influx CLI

2
content/influxdb/cloud/organizations/update-org.md
View File

@ -27,7 +27,7 @@ If you change an organization name, be sure to update the organization in the ab
{{< img-hd src="/img/influxdb/user-icon.png" alt="User Icon" />}} {{< img-hd src="/img/influxdb/user-icon.png" alt="User Icon" />}}
2. Click **{{< icon "edit" >}} Rename**. A verification window appears. 2. Click **{{< icon "edit" "v2" >}} Rename**. A verification window appears.
3. Review the information, and then click **I understand, let's rename my organization**. 3. Review the information, and then click **I understand, let's rename my organization**.
4. Enter a new name for your organization, and then click **Change organization name**. 4. Enter a new name for your organization, and then click **Change organization name**.

2
content/influxdb/cloud/process-data/manage-tasks/export-task.md
View File

@ -18,7 +18,7 @@ Tasks are exported as downloadable JSON files.
{{< nav-icon "tasks" >}} {{< nav-icon "tasks" >}}
2. In the list of tasks, hover over the task you would like to export and click 2. In the list of tasks, hover over the task you would like to export and click
the **{{< icon "gear" >}}** icon that appears. the **{{< icon "gear" "v2" >}}** icon that appears.
3. Select **Export**. 3. Select **Export**.
4. Downloading or save the task export file using one of the following options: 4. Downloading or save the task export file using one of the following options:
- Click **Download JSON** to download the exported JSON file. - Click **Download JSON** to download the exported JSON file.

4
content/influxdb/cloud/process-data/manage-tasks/update-task.md
View File

@ -27,12 +27,12 @@ Click the name of a task to update it.
#### Update the status of a task #### Update the status of a task
In the list of tasks, click the {{< icon "toggle" >}} toggle to the left of the In the list of tasks, click the {{< icon "toggle" "v2" >}} toggle to the left of the
task you want to activate or inactivate. task you want to activate or inactivate.
#### Update a task description #### Update a task description
1. In the list of tasks, hover over the name of the task you want to update. 1. In the list of tasks, hover over the name of the task you want to update.
2. Click the pencil icon {{< icon "pencil" >}}. 2. Click the pencil icon {{< icon "pencil" "v2" >}}.
3. Click outside of the field or press `RETURN` to update. 3. Click outside of the field or press `RETURN` to update.
## Update a task with the influx CLI ## Update a task with the influx CLI

2
content/influxdb/cloud/process-data/manage-tasks/view-tasks.md
View File

@ -19,7 +19,7 @@ Click the **Tasks** icon in the left navigation to view the lists of tasks.
### Filter the list of tasks ### Filter the list of tasks
1. Click the **Show Inactive** {{< icon "toggle" >}} toggle to include or exclude 1. Click the **Show Inactive** {{< icon "toggle" "v2" >}} toggle to include or exclude
inactive tasks in the list. inactive tasks in the list.
2. Enter text in the **Filter tasks** field to search for tasks by name or label. 2. Enter text in the **Filter tasks** field to search for tasks by name or label.
3. Click the heading of any column to sort by that field. 3. Click the heading of any column to sort by that field.

2
content/influxdb/cloud/query-data/execute-queries/query-demo-data.md
View File

@ -40,7 +40,7 @@ Choose from the following demo data sets:
{{< nav-icon "data" >}} {{< nav-icon "data" >}}
2. Click **{{< icon "plus" >}} Add Demo Data**, and then select the demo data bucket to add. 2. Click **{{< icon "plus" "v2" >}} Add Demo Data**, and then select the demo data bucket to add.
3. The Demo Data bucket appears in your list of buckets. 3. The Demo Data bucket appears in your list of buckets.
## Explore demo data ## Explore demo data

2
content/influxdb/cloud/query-data/execute-queries/query-sample-data.md
View File

@ -62,7 +62,7 @@ In the navigation menu on the left, click **Explore (Data Explorer)**.
{{< nav-icon "data" >}} {{< nav-icon "data" >}}
2. Click **{{< icon "plus" >}} Create bucket**, and then name your bucket. The bucket will appear in your list of buckets. 2. Click **{{< icon "plus" "v2" >}} Create bucket**, and then name your bucket. The bucket will appear in your list of buckets.
3. View the [sample datasets document](/influxdb/cloud/reference/sample-data/#sample-datasets) and choose a sample data to query. 3. View the [sample datasets document](/influxdb/cloud/reference/sample-data/#sample-datasets) and choose a sample data to query.
4. Copy the `sample.data()` function listed underneath. 4. Copy the `sample.data()` function listed underneath.
5. Click **Explore** on the left navigation of InfluxDB Cloud and click your bucket, and then click **Script Editor**. 5. Click **Explore** on the left navigation of InfluxDB Cloud and click your bucket, and then click **Script Editor**.

2
content/influxdb/cloud/security/secrets/delete.md
View File

@ -23,7 +23,7 @@ Delete secrets using the {{< cloud-name "short" >}} UI, `influx` command line in
{{< nav-icon "settings" >}} {{< nav-icon "settings" >}}
2. Click the **Secrets** tab. 2. Click the **Secrets** tab.
3. Hover over the secret you want to delete. 3. Hover over the secret you want to delete.
4. Click the {{< icon "delete" >}} button. 4. Click the {{< icon "delete" "v2" >}} button.
## Delete a secret using the influx CLI ## Delete a secret using the influx CLI
Use the [`influx secret delete` command](/influxdb/cloud/reference/cli/influx/secret/delete/) Use the [`influx secret delete` command](/influxdb/cloud/reference/cli/influx/secret/delete/)

4
content/influxdb/cloud/upgrade/v1-to-cloud/_index.md
View File

@ -37,8 +37,8 @@ for the upgrade process.
1. Click **Data (Load Data) > Tokens** in the left navigation bar. 1. Click **Data (Load Data) > Tokens** in the left navigation bar.
{{< nav-icon "data" >}} {{< nav-icon "data" >}}
2. Click **{{< icon "plus" >}} Generate**, and then select **All-Access Token**. 2. Click **{{< icon "plus" "v2" >}} Generate**, and then select **All-Access Token**.
3. Enter a description for the token, and then click **{{< icon "check" >}} Save**. 3. Enter a description for the token, and then click **{{< icon "check" "v2" >}} Save**.
_For more information about managing tokens and token types, see [Manage tokens](/influxdb/cloud/security/tokens/)._ _For more information about managing tokens and token types, see [Manage tokens](/influxdb/cloud/security/tokens/)._

4
content/influxdb/cloud/upgrade/v2-to-cloud.md
View File

@ -47,8 +47,8 @@ for the upgrade process.
1. Click **Data (Load Data) > Tokens** in the left navigation bar. 1. Click **Data (Load Data) > Tokens** in the left navigation bar.
{{< nav-icon "data" >}} {{< nav-icon "data" >}}
2. Click **{{< icon "plus" >}} Generate**, and then select **All-Access Token**. 2. Click **{{< icon "plus" "v2" >}} Generate**, and then select **All-Access Token**.
3. Enter a description for the token, and then click **{{< icon "check" >}} Save**. 3. Enter a description for the token, and then click **{{< icon "check" "v2" >}} Save**.
{{% note %}} {{% note %}}
If you've created other tokens in your InfluxDB 2.x instance for external libraries or If you've created other tokens in your InfluxDB 2.x instance for external libraries or

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

@ -14,13 +14,13 @@ Use dashboard controls in the upper left to update your dashboard.
### Add a cell ### Add a cell
Click **{{< icon "add-cell" >}} Add Cell** to open the Data Explorer and configure a new cell for your dashboard. Click **{{< icon "add-cell" "v2" >}} Add Cell** to open the Data Explorer and configure a new cell for your dashboard.
For details on using the Data Explorer, see [Explore metrics](/influxdb/cloud/visualize-data/explore-metrics/). For details on using the Data Explorer, see [Explore metrics](/influxdb/cloud/visualize-data/explore-metrics/).
### Add a note ### Add a note
1. Click **{{< icon "note" >}} Add Note** to add a note cell to your dashboard. 1. Click **{{< icon "note" "v2" >}} Add Note** to add a note cell to your dashboard.
2. Enter your note in Markdown in the left pane. A preview appears in the right pane. 2. Enter your note in Markdown in the left pane. A preview appears in the right pane.
3. Enable the **Show note when query returns no data** option to show the note only when the query displays no data. 3. Enable the **Show note when query returns no data** option to show the note only when the query displays no data.
4. Click **Save**. 4. Click **Save**.
@ -33,12 +33,12 @@ Click the timezone dropdown to select a timezone to use for the dashboard. Selec
### Manually refresh dashboard ### Manually refresh dashboard
Click the refresh button (**{{< icon "refresh" >}}**) to manually refresh the dashboard's data. Click the refresh button (**{{< icon "refresh" "v2" >}}**) to manually refresh the dashboard's data.
#### Manually a single dashboard cell #### Manually a single dashboard cell
1. Click the **{{< icon "gear" >}}** on the dashboard cell you want to refresh. 1. Click the **{{< icon "gear" "v2" >}}** on the dashboard cell you want to refresh.
2. Click **{{< icon "refresh" >}} Refresh**. 2. Click **{{< icon "refresh" "v2" >}} Refresh**.
### Automatically refresh dashboard ### Automatically refresh dashboard
@ -64,7 +64,7 @@ Click **Variables** to display variables available for your dashboard. For detai
### Presentation mode ### Presentation mode
Click the fullscreen icon (**{{< icon "fullscreen" >}}**) to enter presentation mode. Presentation mode allows you to view [a dashboard] in full screen, hiding the left and top navigation menus so only the cells appear. This mode might be helpful, for example, for stationary screens dedicated to monitoring visualizations. Click the fullscreen icon (**{{< icon "fullscreen" "v2" >}}**) to enter presentation mode. Presentation mode allows you to view [a dashboard] in full screen, hiding the left and top navigation menus so only the cells appear. This mode might be helpful, for example, for stationary screens dedicated to monitoring visualizations.
### Toggle dark mode and light mode ### Toggle dark mode and light mode
Click the moon or sun icons to toggle your dashboard between **dark mode** and **light mode.** Click the moon or sun icons to toggle your dashboard between **dark mode** and **light mode.**

10
content/influxdb/cloud/visualize-data/dashboards/create-dashboard.md
View File

@ -17,7 +17,7 @@ weight: 201
{{< nav-icon "dashboards" >}} {{< nav-icon "dashboards" >}}
2. Click the **{{< icon "plus" >}} Create Dashboard** menu in the upper right and select **New Dashboard**. 2. Click the **{{< icon "plus" "v2" >}} Create Dashboard** menu in the upper right and select **New Dashboard**.
3. Enter a name for your dashboard in the **Name this dashboard** field in the upper left. 3. Enter a name for your dashboard in the **Name this dashboard** field in the upper left.
**To import an existing dashboard**: **To import an existing dashboard**:
@ -40,19 +40,19 @@ weight: 201
{{< nav-icon "dashboards" >}} {{< nav-icon "dashboards" >}}
2. Hover over the dashboard and click **{{< icon "copy" >}}**. 2. Hover over the dashboard and click **{{< icon "copy" "v2" >}}**.
3. Click **Clone**. The cloned dashboard opens. 3. Click **Clone**. The cloned dashboard opens.
#### Add data to your dashboard #### Add data to your dashboard
1. From your dashboard, click **{{< icon "add-cell" >}} Add Cell**. 1. From your dashboard, click **{{< icon "add-cell" "v2" >}} Add Cell**.
2. Create a query in the Data Explorer following the instructions in [Explore metrics](/influxdb/cloud/visualize-data/explore-metrics). 2. Create a query in the Data Explorer following the instructions in [Explore metrics](/influxdb/cloud/visualize-data/explore-metrics).
3. Enter a name for your cell in the upper left. 3. Enter a name for your cell in the upper left.
4. Click the checkmark icon (**{{< icon "checkmark" >}}**) to save the cell to your dashboard. 4. Click the checkmark icon (**{{< icon "checkmark" "v2" >}}**) to save the cell to your dashboard.
You can also send data to your dashboard directly from the Data Explorer. For details, [Explore metrics](/influxdb/cloud/visualize-data/explore-metrics). You can also send data to your dashboard directly from the Data Explorer. For details, [Explore metrics](/influxdb/cloud/visualize-data/explore-metrics).
#### Add a note to your dashboard #### Add a note to your dashboard
1. From your dashboard, click **{{< icon "note" >}} Add Note** in the upper left. 1. From your dashboard, click **{{< icon "note" "v2" >}} Add Note** in the upper left.
2. Enter your note in the window that appears. You can use Markdown syntax to format your note. 2. Enter your note in the window that appears. You can use Markdown syntax to format your note.
3. To preview your Markdown formatting, click the **Preview** option. 3. To preview your Markdown formatting, click the **Preview** option.
4. Click **Save**. 4. Click **Save**.

2
content/influxdb/cloud/visualize-data/dashboards/delete-dashboard.md
View File

@ -15,7 +15,7 @@ To delete a dashboard from the InfluxDB user interface (UI):
{{< nav-icon "dashboards" >}} {{< nav-icon "dashboards" >}}
2. Hover over the dashboard in the list of dashboards and click **{{< icon "trash" >}}**. 2. Hover over the dashboard in the list of dashboards and click **{{< icon "trash" "v2" >}}**.
3. Click **Delete**. 3. Click **Delete**.
{{% warn %}} {{% warn %}}

2
content/influxdb/cloud/visualize-data/dashboards/export-dashboard.md
View File

@ -17,7 +17,7 @@ InfluxDB lets you export dashboards from the InfluxDB user interface (UI).
{{< nav-icon "dashboards" >}} {{< nav-icon "dashboards" >}}
2. Hover over a dashboard and click the gear icon (**{{< icon "gear" >}}**), 2. Hover over a dashboard and click the gear icon (**{{< icon "gear" "v2" >}}**),
and then select **Export**. and then select **Export**.
3. Review the JSON in the window that appears. 3. Review the JSON in the window that appears.
4. Select one of the following options: 4. Select one of the following options:

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

@ -41,7 +41,7 @@ See [Get started with Flux](/influxdb/cloud/query-data/get-started) to learn mor
Click a function from the list to add it to your query. Click a function from the list to add it to your query.
5. Click **Submit** (or press `Control+Enter`) to run your query. You can then preview your graph in the above pane. 5. Click **Submit** (or press `Control+Enter`) to run your query. You can then preview your graph in the above pane.
To cancel your query while it's running, click **Cancel**. To cancel your query while it's running, click **Cancel**.
6. To work on multiple queries at once, click the {{< icon "plus" >}} to add another tab. 6. To work on multiple queries at once, click the {{< icon "plus" "v2" >}} to add another tab.
* Click the eye icon on a tab to hide or show a query's visualization. * Click the eye icon on a tab to hide or show a query's visualization.
* Click the name of the query in the tab to rename it. * Click the name of the query in the tab to rename it.
@ -58,7 +58,7 @@ To open the cell editor overlay, click the gear icon in the upper right of a cel
### View raw data ### View raw data
Toggle the **View Raw Data** {{< icon "toggle" >}} option to see your data in table format instead of a graph. Scroll through raw data using arrows, or click page numbers to find specific tables. [Group keys](/influxdb/cloud/reference/glossary/#group-key) and [data types](/influxdb/cloud/reference/glossary/#data-type) are easily identifiable at the top of each column underneath the headings. Use this option when data can't be visualized using a visualization type. Toggle the **View Raw Data** {{< icon "toggle" "v2" >}} option to see your data in table format instead of a graph. Scroll through raw data using arrows, or click page numbers to find specific tables. [Group keys](/influxdb/cloud/reference/glossary/#group-key) and [data types](/influxdb/cloud/reference/glossary/#data-type) are easily identifiable at the top of each column underneath the headings. Use this option when data can't be visualized using a visualization type.
{{< img-hd src="/img/influxdb/cloud-controls-view-raw-data.png" alt="View raw data" />}} {{< img-hd src="/img/influxdb/cloud-controls-view-raw-data.png" alt="View raw data" />}}
@ -68,7 +68,7 @@ Click the CSV icon to save the cells contents as a CSV file.
### Manually refresh dashboard ### Manually refresh dashboard
Click the refresh button ({{< icon "refresh" >}}) to manually refresh the dashboard's data. Click the refresh button ({{< icon "refresh" "v2" >}}) to manually refresh the dashboard's data.
### Select time range ### Select time range

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

@ -20,7 +20,7 @@ To manage labels:
#### Create a label #### Create a label
1. Click **{{< icon "plus" >}} Create Label**. 1. Click **{{< icon "plus" "v2" >}} Create Label**.
2. Enter a **Name** for the label. 2. Enter a **Name** for the label.
3. Enter a description for the label _(Optional)_. 3. Enter a description for the label _(Optional)_.
4. Select a **Color** for the label. 4. Select a **Color** for the label.
@ -33,12 +33,12 @@ To manage labels:
3. Click **Save Changes**. 3. Click **Save Changes**.
#### Delete a label #### Delete a label
1. In the label list view, hover over the label you would like to delete and click **{{< icon "trash" >}}**. 1. In the label list view, hover over the label you would like to delete and click **{{< icon "trash" "v2" >}}**.
2. Click **Delete**. 2. Click **Delete**.
### Add labels to dashboard items ### Add labels to dashboard items
1. In the list view of dashboards, tasks, or other assets, hover over the item to which you would like to add a label. 1. In the list view of dashboards, tasks, or other assets, hover over the item to which you would like to add a label.
2. Click the {{< icon "add-label" >}} icon that appears below the name. 2. Click the {{< icon "add-label" "v2" >}} icon that appears below the name.
The **Add Labels** overlay will appear. The **Add Labels** overlay will appear.
3. Type the name of the label you would like to add to filter the list of available labels. 3. Type the name of the label you would like to add to filter the list of available labels.
Click the label you would like to add. Click the label you would like to add.

2
content/influxdb/cloud/visualize-data/variables/create-variable.md
View File

@ -66,7 +66,7 @@ InfluxDB lets you import variables exported from InfluxDB in JSON format.
{{< nav-icon "settings" >}} {{< nav-icon "settings" >}}
2. Select the **Variables** tab. 2. Select the **Variables** tab.
3. Click the **{{< icon "plus" >}} Create Variable** drop-down menu and select **Import Variable**. 3. Click the **{{< icon "plus" "v2" >}} Create Variable** drop-down menu and select **Import Variable**.
4. In the window that appears: 4. In the window that appears:
- Select **Upload File** to drag and drop or select a file. - Select **Upload File** to drag and drop or select a file.
- Select **Paste JSON** to paste in JSON. - Select **Paste JSON** to paste in JSON.

2
content/influxdb/cloud/visualize-data/variables/delete-variable.md
View File

@ -18,7 +18,7 @@ Delete an existing variable in the InfluxDB user interface (UI).
{{< nav-icon "settings" >}} {{< nav-icon "settings" >}}
2. Select the **Variables** tab. 2. Select the **Variables** tab.
3. Hover over a variable, click the **{{< icon "trash" >}}** icon, and **Delete**. 3. Hover over a variable, click the **{{< icon "trash" "v2" >}}** icon, and **Delete**.
{{% warn %}} {{% warn %}}
Once deleted, any dashboards with queries that utilize the variable will no Once deleted, any dashboards with queries that utilize the variable will no

2
content/influxdb/cloud/visualize-data/variables/export-variable.md
View File

@ -18,7 +18,7 @@ Variables are exported as downloadable JSON files.
{{< nav-icon "settings" >}} {{< nav-icon "settings" >}}
2. Select the **Variables** tab. 2. Select the **Variables** tab.
3. Hover over a variable in the list, then click the gear icon (**{{< icon "gear" >}}**) 3. Hover over a variable in the list, then click the gear icon (**{{< icon "gear" "v2" >}}**)
and select **Export**. and select **Export**.
4. Review the JSON in the window that appears. 4. Review the JSON in the window that appears.
5. Select one of the following options: 5. Select one of the following options:

2
content/influxdb/cloud/visualize-data/visualization-types/band.md
View File

@ -95,7 +95,7 @@ For example, in the band chart above, the lines represent the mean `usage_system
## Band controls ## Band controls
To view **Band** controls, click **{{< icon "gear" >}} Customize** next to the visualization dropdown. To view **Band** controls, click **{{< icon "gear" "v2" >}} Customize** next to the visualization dropdown.
###### Data ###### Data

2
content/influxdb/cloud/visualize-data/visualization-types/graph-single-stat.md
View File

@ -38,7 +38,7 @@ For consistent Single Stat results, the query should return a single table.
{{% /note %}} {{% /note %}}
## Graph + Single Stat Controls ## Graph + Single Stat Controls
To view **Graph + Single Stat** controls, click **{{< icon "gear" >}} Customize** next to To view **Graph + Single Stat** controls, click **{{< icon "gear" "v2" >}} Customize** next to
the visualization dropdown. the visualization dropdown.
###### Data ###### Data

2
content/influxdb/cloud/visualize-data/visualization-types/graph.md
View File

@ -25,7 +25,7 @@ When multiple series are present, it automatically assigns colors based on the s
When using a line graph, all points within a single table are connected. When multiple series are present, it automatically assigns colors based on the selected [Line Colors option](#options). When using a line graph, all points within a single table are connected. When multiple series are present, it automatically assigns colors based on the selected [Line Colors option](#options).
## Graph controls ## Graph controls
To view **Graph** controls, click **{{< icon "gear" >}} Customize** next to To view **Graph** controls, click **{{< icon "gear" "v2" >}} Customize** next to
the visualization dropdown. the visualization dropdown.
###### Data ###### Data

6
content/influxdb/cloud/visualize-data/visualization-types/map.md
View File

@ -33,9 +33,9 @@ To view geo-temporal data on a geographic map, set up a Map visualization.
Click the name of the dashboard to update and then do one of the following: Click the name of the dashboard to update and then do one of the following:
- **To edit an existing cell**, click the **{{< icon "cog" >}}** icon on - **To edit an existing cell**, click the **{{< icon "cog" "v2" >}}** icon on
the cell and then **{{< icon "edit" >}} Configure**. the cell and then **{{< icon "edit" "v2" >}} Configure**.
- **To create a new cell**, click **{{< icon "add-cell" >}} Add Cell**. - **To create a new cell**, click **{{< icon "add-cell" "v2" >}} Add Cell**.
2. Use the **Query Builder** or the **Script Editor** to enter your query. 2. Use the **Query Builder** or the **Script Editor** to enter your query.
To determine the location of points on a geographic map, query results must To determine the location of points on a geographic map, query results must

4
content/influxdb/cloud/write-data/no-code/use-telegraf/auto-config.md
View File

@ -34,11 +34,11 @@ for using Telegraf with InfluxDB v2.0._
{{< nav-icon "load data" >}} {{< nav-icon "load data" >}}
4. Click **{{< icon "plus" >}} Create Configuration**. 4. Click **{{< icon "plus" "v2" >}} Create Configuration**.
5. In the **Bucket** dropdown, select the bucket where Telegraf will store collected data. 5. In the **Bucket** dropdown, select the bucket where Telegraf will store collected data.
6. Select one or more of the available plugin groups and click **Continue**. 6. Select one or more of the available plugin groups and click **Continue**.
7. Review the list of **Plugins to Configure** for configuration requirements. 7. Review the list of **Plugins to Configure** for configuration requirements.
Plugins listed with a <span style="color:#32B08C">{{< icon "check" >}}</span> Plugins listed with a <span style="color:#32B08C">{{< icon "check" "v2" >}}</span>
require no additional configuration. require no additional configuration.
To configure a plugin or access plugin documentation, click the plugin name. To configure a plugin or access plugin documentation, click the plugin name.

6
content/influxdb/v2.0/influxdb-templates/monitor.md
View File

@ -147,7 +147,7 @@ To alert when data stops flowing from InfluxDB OSS instances to your InfluxDB Cl
{{< img-hd src="/img/influxdb/2-0-monitor-oss-deadman.png" />}} {{< img-hd src="/img/influxdb/2-0-monitor-oss-deadman.png" />}}
2. Choose a InfluxDB OSS field or create a new OSS field for your deadman alert: 2. Choose a InfluxDB OSS field or create a new OSS field for your deadman alert:
1. Click **{{< icon "plus" >}} Create** and select **Deadman Check** in the dropown menu. 1. Click **{{< icon "plus" "v2" >}} Create** and select **Deadman Check** in the dropown menu.
2. Define your query with at least one field. 2. Define your query with at least one field.
3. Click **Submit** and **Configure Check**. 3. Click **Submit** and **Configure Check**.
When metrics stop reporting, you'll receive an alert. When metrics stop reporting, you'll receive an alert.
@ -166,7 +166,7 @@ InfluxData supports different endpoints: Slack, PagerDuty, and HTTP. Slack is fr
#### Send a notification to Slack #### Send a notification to Slack
1. Create a [Slack Webhooks](https://api.slack.com/messaging/webhooks). 1. Create a [Slack Webhooks](https://api.slack.com/messaging/webhooks).
2. Go to **Alerts > Notification Endpoint** and click **{{< icon "plus" >}} Create**, and enter a name and description for your Slack endpoint. 2. Go to **Alerts > Notification Endpoint** and click **{{< icon "plus" "v2" >}} Create**, and enter a name and description for your Slack endpoint.
3. Enter your Slack Webhook under **Incoming Webhook URL** and click **Create Notification Endpoint**. 3. Enter your Slack Webhook under **Incoming Webhook URL** and click **Create Notification Endpoint**.
#### Send a notification to PagerDuty or HTTP #### Send a notification to PagerDuty or HTTP
@ -177,5 +177,5 @@ Send a notification to PagerDuty or HTTP endpoints (other webhooks) by [upgradin
[Create a notification rule](/influxdb/cloud/monitor-alert/notification-rules/create/) to set rules for when to send a deadman alert message to your notification endpoint. [Create a notification rule](/influxdb/cloud/monitor-alert/notification-rules/create/) to set rules for when to send a deadman alert message to your notification endpoint.
1. Go to **Alerts > Notification Rules** and click **{{< icon "plus" >}} Create**. 1. Go to **Alerts > Notification Rules** and click **{{< icon "plus" "v2" >}} Create**.
2. Fill out the **About** and **Conditions** section then click **Create Notification Rule**. 2. Fill out the **About** and **Conditions** section then click **Create Notification Rule**.

8
content/influxdb/v2.0/monitor-alert/checks/create.md
View File

@ -47,7 +47,7 @@ in a specified amount of time.
{{< nav-icon "alerts" >}} {{< nav-icon "alerts" >}}
2. Click **{{< icon "plus" >}} Create** and select the [type of check](#check-types) to create. 2. Click **{{< icon "plus" "v2" >}} Create** and select the [type of check](#check-types) to create.
3. Click **Name this check** in the top left corner and provide a unique name for the check. 3. Click **Name this check** in the top left corner and provide a unique name for the check.
#### Configure the check query #### Configure the check query
@ -60,7 +60,7 @@ in a specified amount of time.
(for example, "Every 5 minutes") and an aggregate function from the list of functions. (for example, "Every 5 minutes") and an aggregate function from the list of functions.
3. Click **Submit** to run the query and preview the results. 3. Click **Submit** to run the query and preview the results.
To see the raw query results, click the **{{< icon "toggle" >}} View Raw Data** toggle. To see the raw query results, click the **{{< icon "toggle" "v2" >}} View Raw Data** toggle.
#### Configure the check #### Configure the check
1. Click **2. Configure Check** near the top of the window. 1. Click **2. Configure Check** near the top of the window.
@ -143,10 +143,10 @@ count = 12
3. In the **And stop checking after** field, enter the time to stop monitoring the series. 3. In the **And stop checking after** field, enter the time to stop monitoring the series.
For example, `30m`, `2h`, `3h15m`, etc. For example, `30m`, `2h`, `3h15m`, etc.
5. Click the green **{{< icon "check" >}}** in the top right corner to save the check. 5. Click the green **{{< icon "check" "v2" >}}** in the top right corner to save the check.
## Clone a check ## Clone a check
Create a new check by cloning an existing check. Create a new check by cloning an existing check.
1. In the **Checks** column, hover over the check you want to clone. 1. In the **Checks** column, hover over the check you want to clone.
2. Click the **{{< icon "clone" >}}** icon, then **Clone**. 2. Click the **{{< icon "clone" "v2" >}}** icon, then **Clone**.

2
content/influxdb/v2.0/monitor-alert/checks/delete.md
View File

@ -22,7 +22,7 @@ Deleting a check cannot be undone.
{{< nav-icon "alerts" >}} {{< nav-icon "alerts" >}}
2. Hover over the check you want to delete, click the **{{< icon "delete" >}}** 2. Hover over the check you want to delete, click the **{{< icon "delete" "v2" >}}**
icon, and then **Delete**. icon, and then **Delete**.
After a check is deleted, all statuses generated by the check remain in the `_monitoring` After a check is deleted, all statuses generated by the check remain in the `_monitoring`

8
content/influxdb/v2.0/monitor-alert/checks/update.md
View File

@ -34,18 +34,18 @@ To update checks, select **Alerts** in the navigation menu on the left.
_For details about using the check builder, see [Create checks](/influxdb/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 ## Enable or disable a check
Click the {{< icon "toggle" >}} toggle next to a check to enable or disable it. Click the {{< icon "toggle" "v2" >}} toggle next to a check to enable or disable it.
## Rename a check ## Rename a check
1. Hover over the name of the check you want to update. 1. Hover over the name of the check you want to update.
2. Click the **{{< icon "edit" >}}** icon that appears next to the check name. 2. Click the **{{< icon "edit" "v2" >}}** icon that appears next to the check name.
2. Enter a new name and click out of the name field or press enter to save. 2. Enter a new name and click out of the name field or press enter to save.
_You can also rename a check in the [check builder](#update-check-queries-and-logic)._ _You can also rename a check in the [check builder](#update-check-queries-and-logic)._
## Add or update a check description ## Add or update a check description
1. Hover over the check description you want to update. 1. Hover over the check description you want to update.
2. Click the **{{< icon "edit" >}}** icon that appears next to the description. 2. Click the **{{< icon "edit" "v2" >}}** icon that appears next to the description.
2. Enter a new description and click out of the name field or press enter to save. 2. Enter a new description and click out of the name field or press enter to save.
## Add a label to a check ## Add a label to a check
@ -57,4 +57,4 @@ _You can also rename a check in the [check builder](#update-check-queries-and-lo
- In the **Description** field, enter an optional description for the label. - In the **Description** field, enter an optional description for the label.
- Select a color for the label. - Select a color for the label.
- Click **Create Label**. - Click **Create Label**.
4. To remove a label, hover over the label under to a rule and click **{{< icon "x" >}}**. 4. To remove a label, hover over the label under to a rule and click **{{< icon "x" "v2" >}}**.

4
content/influxdb/v2.0/monitor-alert/checks/view.md
View File

@ -32,12 +32,12 @@ The check builder appears.
Here you can view the check query and logic. Here you can view the check query and logic.
## View statuses generated by a check ## View statuses generated by a check
1. Hover over the check and click the **{{< icon "view" >}}** icon. 1. Hover over the check and click the **{{< icon "view" "v2" >}}** icon.
2. Click **View History**. 2. Click **View History**.
The Statuses History page displays statuses generated by the selected check. The Statuses History page displays statuses generated by the selected check.
## View notifications triggered by a check ## View notifications triggered by a check
1. Hover over the check, click the **{{< icon "view" >}}** 1. Hover over the check, click the **{{< icon "view" "v2" >}}**
icon, then **View History**. icon, then **View History**.
2. In the top left corner, click **Notifications**. 2. In the top left corner, click **Notifications**.
The Notifications History page displays notifications initiated by the selected check. The Notifications History page displays notifications initiated by the selected check.

2
content/influxdb/v2.0/monitor-alert/custom-checks.md
View File

@ -25,7 +25,7 @@ Using a Flux task, you can create a custom check that provides a couple advantag
{{< nav-icon "tasks" >}} {{< nav-icon "tasks" >}}
2. Click **{{< icon "plus" >}} Create Task**, and then select **New Task**. 2. Click **{{< icon "plus" "v2" >}} Create Task**, and then select **New Task**.
3. In the **Name** field, enter a descriptive name, 3. In the **Name** field, enter a descriptive name,
and then enter how often to run the task in the **Every** field (for example, `10m`). and then enter how often to run the task in the **Every** field (for example, `10m`).
For more detail, such as using cron syntax or including an offset, see [Task configuration options](/influxdb/v2.0/process-data/task-options/). For more detail, such as using cron syntax or including an offset, see [Task configuration options](/influxdb/v2.0/process-data/task-options/).

2
content/influxdb/v2.0/monitor-alert/notification-endpoints/create.md
View File

@ -21,7 +21,7 @@ To send notifications about changes in your data, start by creating a notificati
{{< nav-icon "alerts" >}} {{< nav-icon "alerts" >}}
2. Select **Notification Endpoints** near to top of the page. 2. Select **Notification Endpoints** near to top of the page.
3. Click **{{< icon "plus" >}} Create**. 3. Click **{{< icon "plus" "v2" >}} Create**.
4. From the **Destination** drop-down list, select a destination endpoint to send notifications 4. From the **Destination** drop-down list, select a destination endpoint to send notifications
5. In the **Name** and **Description** fields, enter a name and description for the endpoint. 5. In the **Name** and **Description** fields, enter a name and description for the endpoint.
6. Enter information to connect to the endpoint: 6. Enter information to connect to the endpoint:

2
content/influxdb/v2.0/monitor-alert/notification-endpoints/delete.md
View File

@ -22,5 +22,5 @@ If notifications are no longer sent to an endpoint, complete the steps below to
2. Select **Notification Endpoints** near to top of the page. 2. Select **Notification Endpoints** near to top of the page.
find the rule you want to delete. find the rule you want to delete.
3. Hover over the endpoint you want to delete and click the **{{< icon "trash" >}}** icon. 3. Hover over the endpoint you want to delete and click the **{{< icon "trash" "v2" >}}** icon.
4. Click **Delete** to confirm. 4. Click **Delete** to confirm.

6
content/influxdb/v2.0/monitor-alert/notification-endpoints/update.md
View File

@ -21,7 +21,7 @@ To update the notification endpoint details, complete the procedures below as ne
{{< nav-icon "alerts" >}} {{< nav-icon "alerts" >}}
2. Select **Notification Endpoints** near to top of the page. 2. Select **Notification Endpoints** near to top of the page.
3. Click **{{< icon "add-label" >}} Add a label** next to the endpoint you want to add a label to. 3. Click **{{< icon "add-label" "v2" >}} Add a label** next to the endpoint you want to add a label to.
The **Add Labels** box opens. The **Add Labels** box opens.
4. To add an existing label, select the label from the list. 4. To add an existing label, select the label from the list.
5. To create and add a new label: 5. To create and add a new label:
@ -41,7 +41,7 @@ To update the notification endpoint details, complete the procedures below as ne
{{< nav-icon "alerts" >}} {{< nav-icon "alerts" >}}
2. Select **Notification Endpoints** near to top of the page. 2. Select **Notification Endpoints** near to top of the page.
3. Click the {{< icon "toggle" >}} toggle to disable the notification endpoint. 3. Click the {{< icon "toggle" "v2" >}} toggle to disable the notification endpoint.
## Update the name or description for notification endpoint ## Update the name or description for notification endpoint
@ -51,7 +51,7 @@ To update the notification endpoint details, complete the procedures below as ne
2. Select **Notification Endpoints** near to top of the page. 2. Select **Notification Endpoints** near to top of the page.
3. Hover over the name or description of the endpoint and click the pencil icon 3. Hover over the name or description of the endpoint and click the pencil icon
(**{{< icon "edit" >}}**) to edit the field. (**{{< icon "edit" "v2" >}}**) to edit the field.
4. Click outside of the field to save your changes. 4. Click outside of the field to save your changes.
## Change endpoint details ## Change endpoint details

2
content/influxdb/v2.0/monitor-alert/notification-endpoints/view.md
View File

@ -44,7 +44,7 @@ View notification endpoint details and history in the InfluxDB user interface (U
{{< nav-icon "alerts" >}} {{< nav-icon "alerts" >}}
2. Select **Notification Endpoints** near to top of the page. 2. Select **Notification Endpoints** near to top of the page.
3. Hover over the notification endpoint, click the **{{< icon "view" >}}** icon, then **View History**. 3. Hover over the notification endpoint, click the **{{< icon "view" "v2" >}}** icon, then **View History**.
The Check Statuses History page displays: The Check Statuses History page displays:
- Statuses generated for the selected notification endpoint - Statuses generated for the selected notification endpoint

4
content/influxdb/v2.0/monitor-alert/notification-rules/create.md
View File

@ -22,7 +22,7 @@ _For details, see [Manage checks](/influxdb/v2.0/monitor-alert/checks/) and
{{< nav-icon "alerts" >}} {{< nav-icon "alerts" >}}
2. Select **Notification Rules** near to top of the page. 2. Select **Notification Rules** near to top of the page.
3. Click **{{< icon "plus" >}} Create**. 3. Click **{{< icon "plus" "v2" >}} Create**.
4. Complete the **About** section: 4. Complete the **About** section:
1. In the **Name** field, enter a name for the notification rule. 1. In the **Name** field, enter a name for the notification rule.
2. In the **Schedule Every** field, enter how frequently the rule should run. 2. In the **Schedule Every** field, enter how frequently the rule should run.
@ -40,5 +40,5 @@ _For details, see [Manage checks](/influxdb/v2.0/monitor-alert/checks/) and
{{< nav-icon "alerts" >}} {{< nav-icon "alerts" >}}
2. Select **Notification Rules** near to top of the page. 2. Select **Notification Rules** near to top of the page.
3. Hover over the rule you want to clone and click the **{{< icon "clone" >}}** icon and select **Clone**. 3. Hover over the rule you want to clone and click the **{{< icon "clone" "v2" >}}** icon and select **Clone**.
The cloned rule appears. The cloned rule appears.

2
content/influxdb/v2.0/monitor-alert/notification-rules/delete.md
View File

@ -18,5 +18,5 @@ related:
{{< nav-icon "alerts" >}} {{< nav-icon "alerts" >}}
2. Select **Notification Rules** near to top of the page. 2. Select **Notification Rules** near to top of the page.
3. Hover over the rule you want to delete and click the **{{< icon "trash" >}}** icon. 3. Hover over the rule you want to delete and click the **{{< icon "trash" "v2" >}}** icon.
4. Click **Delete** to confirm. 4. Click **Delete** to confirm.

8
content/influxdb/v2.0/monitor-alert/notification-rules/update.md
View File

@ -18,7 +18,7 @@ related:
{{< nav-icon "alerts" >}} {{< nav-icon "alerts" >}}
2. Select **Notification Rules** near to top of the page. 2. Select **Notification Rules** near to top of the page.
3. Click **{{< icon "add-label" >}} Add a label** next to the rule you want to add a label to. 3. Click **{{< icon "add-label" "v2" >}} Add a label** next to the rule you want to add a label to.
The **Add Labels** box opens. The **Add Labels** box opens.
4. To add an existing label, select the label from the list. 4. To add an existing label, select the label from the list.
5. To create and add a new label: 5. To create and add a new label:
@ -26,7 +26,7 @@ related:
- In the **Description** field, enter an optional description for the label. - In the **Description** field, enter an optional description for the label.
- Select a color for the label. - Select a color for the label.
- Click **Create Label**. - Click **Create Label**.
6. To remove a label, hover over the label under to a rule and click **{{< icon "x" >}}**. 6. To remove a label, hover over the label under to a rule and click **{{< icon "x" "v2" >}}**.
## Disable notification rules ## Disable notification rules
@ -36,7 +36,7 @@ related:
{{< nav-icon "alerts" >}} {{< nav-icon "alerts" >}}
2. Select **Notification Rules** near to top of the page. 2. Select **Notification Rules** near to top of the page.
3. Click the {{< icon "toggle" >}} toggle to disable the notification rule. 3. Click the {{< icon "toggle" "v2" >}} toggle to disable the notification rule.
## Update the name or description for notification rules ## Update the name or description for notification rules
@ -46,5 +46,5 @@ related:
2. Select **Notification Rules** near to top of the page. 2. Select **Notification Rules** near to top of the page.
3. Hover over the name or description of a rule and click the pencil icon 3. Hover over the name or description of a rule and click the pencil icon
(**{{< icon "edit" >}}**) to edit the field. (**{{< icon "edit" "v2" >}}**) to edit the field.
4. Click outside of the field to save your changes. 4. Click outside of the field to save your changes.

4
content/influxdb/v2.0/monitor-alert/notification-rules/view.md
View File

@ -35,11 +35,11 @@ The check builder appears.
Here you can view the check query and logic. Here you can view the check query and logic.
## View statuses generated by a notification rule ## View statuses generated by a notification rule
Hover over the check, click the **{{< icon "view" >}}** icon, and then **View History**. Hover over the check, click the **{{< icon "view" "v2" >}}** icon, and then **View History**.
The Statuses History page displays statuses generated by the selected check. The Statuses History page displays statuses generated by the selected check.
## View notifications triggered by a notification rule ## View notifications triggered by a notification rule
1. Hover over the notification rule, click the **{{< icon "view" >}}** 1. Hover over the notification rule, click the **{{< icon "view" "v2" >}}**
icon, and then **View History**. icon, and then **View History**.
2. In the top left corner, click **Notifications**. 2. In the top left corner, click **Notifications**.
The Notifications History page displays notifications initiated by the selected notification rule. The Notifications History page displays notifications initiated by the selected notification rule.

2
content/influxdb/v2.0/monitor-alert/send-email.md
View File

@ -31,7 +31,7 @@ Send an alert email using a third-party service, such as [SendGrid](https://send
{{< nav-icon "tasks" >}} {{< nav-icon "tasks" >}}
2. Click **{{< icon "plus" >}} Create Task**, and then select **New Task**. 2. Click **{{< icon "plus" "v2" >}} Create Task**, and then select **New Task**.
3. In the **Name** field, enter a descriptive name, for example, **Send alert email**, and then enter how often to run the task in the **Every** field, for example, `10m`. For more detail, such as using cron syntax or including an offset, see [Task configuration options](/influxdb/v2.0/process-data/task-options/). 3. In the **Name** field, enter a descriptive name, for example, **Send alert email**, and then enter how often to run the task in the **Every** field, for example, `10m`. For more detail, such as using cron syntax or including an offset, see [Task configuration options](/influxdb/v2.0/process-data/task-options/).
4. In the right panel, enter the following detail in your **task script** (see [examples below](#examples)): 4. In the right panel, enter the following detail in your **task script** (see [examples below](#examples)):

2
content/influxdb/v2.0/organizations/buckets/create-bucket.md
View File

@ -29,7 +29,7 @@ There are two places you can create a bucket in the UI.
{{< nav-icon "data" >}} {{< nav-icon "data" >}}
2. Click **{{< icon "plus" >}} Create Bucket** in the upper right. 2. Click **{{< icon "plus" "v2" >}} Create Bucket** in the upper right.
3. Enter a **Name** for the bucket. 3. Enter a **Name** for the bucket.
4. Select when to **Delete Data**: 4. Select when to **Delete Data**:
- **Never** to retain data forever. - **Never** to retain data forever.

2
content/influxdb/v2.0/organizations/buckets/delete-bucket.md
View File

@ -19,7 +19,7 @@ to delete a bucket.
{{< nav-icon "data" >}} {{< nav-icon "data" >}}
2. Hover over the bucket you would like to delete. 2. Hover over the bucket you would like to delete.
3. Click **{{< icon "delete" >}} Delete Bucket** and **Confirm** to delete the bucket. 3. Click **{{< icon "delete" "v2" >}} Delete Bucket** and **Confirm** to delete the bucket.
## Delete a bucket using the influx CLI ## Delete a bucket using the influx CLI

2
content/influxdb/v2.0/organizations/members/remove-member.md
View File

@ -24,7 +24,7 @@ For information about deleting a user from InfluxDB, see [Delete a user](/influx
{{< nav-icon "org" >}} {{< nav-icon "org" >}}
2. Hover over the member you would like to delete and click the **{{< icon "delete" >}}** icon. 2. Hover over the member you would like to delete and click the **{{< icon "delete" "v2" >}}** icon.
3. Click **Delete**. 3. Click **Delete**.
## Remove a member from an organization using the influx CLI ## Remove a member from an organization using the influx CLI

2
content/influxdb/v2.0/organizations/update-org.md
View File

@ -27,7 +27,7 @@ If you change an organization name, be sure to update the organization in the ab
{{< img-hd src="/img/influxdb/user-icon.png" alt="User Icon" />}} {{< img-hd src="/img/influxdb/user-icon.png" alt="User Icon" />}}
2. Click **{{< icon "edit" >}} Rename**. A verification window appears. 2. Click **{{< icon "edit" "v2" >}} Rename**. A verification window appears.
3. Review the information, and then click **I understand, let's rename my organization**. 3. Review the information, and then click **I understand, let's rename my organization**.
4. Enter a new name for your organization, and then click **Change organization name**. 4. Enter a new name for your organization, and then click **Change organization name**.

4
content/influxdb/v2.0/process-data/manage-tasks/create-task.md
View File

@ -48,7 +48,7 @@ The InfluxDB UI provides multiple ways to create a task:
{{< nav-icon "tasks" >}} {{< nav-icon "tasks" >}}
2. Click **{{< icon "plus" >}} Create Task** in the upper right. 2. Click **{{< icon "plus" "v2" >}} Create Task** in the upper right.
3. Select **New Task**. 3. Select **New Task**.
4. In the left panel, specify the task options. 4. In the left panel, specify the task options.
See [Task options](/influxdb/v2.0/process-data/task-options) for detailed information about each option. See [Task options](/influxdb/v2.0/process-data/task-options) for detailed information about each option.
@ -92,7 +92,7 @@ fields in the left panel when you save the task.
{{< nav-icon "tasks" >}} {{< nav-icon "tasks" >}}
2. Hover over the task you would like to clone and click the **{{< icon "duplicate" >}}** icon that appears. 2. Hover over the task you would like to clone and click the **{{< icon "duplicate" "v2" >}}** icon that appears.
4. Click **Clone**. 4. Click **Clone**.
## Create a task using the influx CLI ## Create a task using the influx CLI

2
content/influxdb/v2.0/process-data/manage-tasks/export-task.md
View File

@ -18,7 +18,7 @@ Tasks are exported as downloadable JSON files.
{{< nav-icon "tasks" >}} {{< nav-icon "tasks" >}}
2. In the list of tasks, hover over the task you would like to export and click 2. In the list of tasks, hover over the task you would like to export and click
the **{{< icon "gear" >}}** icon that appears. the **{{< icon "gear" "v2" >}}** icon that appears.
3. Select **Export**. 3. Select **Export**.
4. Downloading or save the task export file using one of the following options: 4. Downloading or save the task export file using one of the following options:
- Click **Download JSON** to download the exported JSON file. - Click **Download JSON** to download the exported JSON file.

2
content/influxdb/v2.0/process-data/manage-tasks/run-task.md
View File

@ -23,7 +23,7 @@ however, you can manually run a task from the InfluxDB user interface (UI) or th
{{< nav-icon "tasks" >}} {{< nav-icon "tasks" >}}
2. Hover over the task you want to run and click the **{{< icon "gear" >}}** icon. 2. Hover over the task you want to run and click the **{{< icon "gear" "v2" >}}** icon.
3. Select **Run Task**. 3. Select **Run Task**.
## Run a task with the influx CLI ## Run a task with the influx CLI

2
content/influxdb/v2.0/process-data/manage-tasks/task-run-history.md
View File

@ -26,7 +26,7 @@ to view task run histories and associated logs.
{{< nav-icon "tasks" >}} {{< nav-icon "tasks" >}}
2. Hover over the task you want to run and click the **{{< icon "gear" >}}** icon. 2. Hover over the task you want to run and click the **{{< icon "gear" "v2" >}}** icon.
3. Select **View Task Runs**. 3. Select **View Task Runs**.
### View task run logs ### View task run logs

4
content/influxdb/v2.0/process-data/manage-tasks/update-task.md
View File

@ -27,12 +27,12 @@ Click the name of a task to update it.
#### Update the status of a task #### Update the status of a task
In the list of tasks, click the {{< icon "toggle" >}} toggle to the left of the In the list of tasks, click the {{< icon "toggle" "v2" >}} toggle to the left of the
task you want to activate or inactivate. task you want to activate or inactivate.
#### Update a task description #### Update a task description
1. In the list of tasks, hover over the name of the task you want to update. 1. In the list of tasks, hover over the name of the task you want to update.
2. Click the pencil icon {{< icon "pencil" >}}. 2. Click the pencil icon {{< icon "pencil" "v2" >}}.
3. Click outside of the field or press `RETURN` to update. 3. Click outside of the field or press `RETURN` to update.
## Update a task with the influx CLI ## Update a task with the influx CLI

2
content/influxdb/v2.0/process-data/manage-tasks/view-tasks.md
View File

@ -19,7 +19,7 @@ Click the **Tasks** icon in the left navigation to view the lists of tasks.
### Filter the list of tasks ### Filter the list of tasks
1. Click the **Show Inactive** {{< icon "toggle" >}} toggle to include or exclude 1. Click the **Show Inactive** {{< icon "toggle" "v2" >}} toggle to include or exclude
inactive tasks in the list. inactive tasks in the list.
2. Enter text in the **Filter tasks** field to search for tasks by name or label. 2. Enter text in the **Filter tasks** field to search for tasks by name or label.
3. Click the heading of any column to sort by that field. 3. Click the heading of any column to sort by that field.

6
content/influxdb/v2.0/query-data/execute-queries/data-explorer.md
View File

@ -40,7 +40,7 @@ See [Get started with Flux](/influxdb/v2.0/query-data/get-started) to learn more
Click a function from the list to add it to your query. Click a function from the list to add it to your query.
5. Click **Submit** (or press `Control+Enter`) to run your query. You can then preview your graph in the above pane. 5. Click **Submit** (or press `Control+Enter`) to run your query. You can then preview your graph in the above pane.
To cancel your query while it's running, click **Cancel**. To cancel your query while it's running, click **Cancel**.
6. To work on multiple queries at once, click the {{< icon "plus" >}} to add another tab. 6. To work on multiple queries at once, click the {{< icon "plus" "v2" >}} to add another tab.
* Click the eye icon on a tab to hide or show a query's visualization. * Click the eye icon on a tab to hide or show a query's visualization.
* Click the name of the query in the tab to rename it. * Click the name of the query in the tab to rename it.
@ -57,7 +57,7 @@ To open the cell editor overlay, click the gear icon in the upper right of a cel
### View raw data ### View raw data
Toggle the **View Raw Data** {{< icon "toggle" >}} option to see your data in table format instead of a graph. Scroll through raw data using arrows, or click page numbers to find specific tables. [Group keys](/influxdb/cloud/reference/glossary/#group-key) and [data types](/influxdb/cloud/reference/glossary/#data-type) are easily identifiable at the top of each column underneath the headings. Use this option when data can't be visualized using a visualization type. Toggle the **View Raw Data** {{< icon "toggle" "v2" >}} option to see your data in table format instead of a graph. Scroll through raw data using arrows, or click page numbers to find specific tables. [Group keys](/influxdb/cloud/reference/glossary/#group-key) and [data types](/influxdb/cloud/reference/glossary/#data-type) are easily identifiable at the top of each column underneath the headings. Use this option when data can't be visualized using a visualization type.
{{< img-hd src="/img/influxdb/cloud-controls-view-raw-data.png" alt="View raw data" />}} {{< img-hd src="/img/influxdb/cloud-controls-view-raw-data.png" alt="View raw data" />}}
@ -67,7 +67,7 @@ Click the CSV icon to save the cells contents as a CSV file.
### Manually refresh dashboard ### Manually refresh dashboard
Click the refresh button ({{< icon "refresh" >}}) to manually refresh the dashboard's data. Click the refresh button ({{< icon "refresh" "v2" >}}) to manually refresh the dashboard's data.
### Select time range ### Select time range

2
content/influxdb/v2.0/query-data/execute-queries/query-sample-data.md
View File

@ -64,7 +64,7 @@ In the navigation menu on the left, click **Explore (Data Explorer)**.
{{< nav-icon "data" >}} {{< nav-icon "data" >}}
2. Click **{{< icon "plus" >}} Create bucket**, and then name your bucket. The bucket will appear in your list of buckets. 2. Click **{{< icon "plus" "v2" >}} Create bucket**, and then name your bucket. The bucket will appear in your list of buckets.
3. View the [sample datasets document](/influxdb/cloud/reference/sample-data/#sample-datasets) and choose a sample data to query. 3. View the [sample datasets document](/influxdb/cloud/reference/sample-data/#sample-datasets) and choose a sample data to query.
4. Copy the `sample.data()` function listed underneath. 4. Copy the `sample.data()` function listed underneath.
5. Click **Explore** on the left navigation of InfluxDB Cloud and click your bucket, and then click **Script Editor**. 5. Click **Explore** on the left navigation of InfluxDB Cloud and click your bucket, and then click **Script Editor**.

54
content/influxdb/v2.0/query-data/optimize-queries.md
View File

@ -27,34 +27,34 @@ Most pushdowns are supported when querying an InfluxDB 2.0 or InfluxDB Cloud dat
| Functions | InfluxDB 2.0 | InfluxDB Cloud | | Functions | InfluxDB 2.0 | InfluxDB Cloud |
|:--------- |:------------: |:--------------: | |:--------- |:------------: |:--------------: |
| **count()** | {{< icon "check" >}} | {{< icon "check" >}} | | **count()** | {{< icon "check" "v2" >}} | {{< icon "check" "v2" >}} |
| **drop()** | {{< icon "check" >}} | {{< icon "check" >}} | | **drop()** | {{< icon "check" "v2" >}} | {{< icon "check" "v2" >}} |
| **duplicate()** | {{< icon "check" >}} | {{< icon "check" >}} | | **duplicate()** | {{< icon "check" "v2" >}} | {{< icon "check" "v2" >}} |
| **filter()** {{% req " \*" %}} | {{< icon "check" >}} | {{< icon "check" >}} | | **filter()** {{% req " \*" %}} | {{< icon "check" "v2" >}} | {{< icon "check" "v2" >}} |
| **fill()** | {{< icon "check" >}} | {{< icon "check" >}} | | **fill()** | {{< icon "check" "v2" >}} | {{< icon "check" "v2" >}} |
| **first()** | {{< icon "check" >}} | {{< icon "check" >}} | | **first()** | {{< icon "check" "v2" >}} | {{< icon "check" "v2" >}} |
| **keep()** | {{< icon "check" >}} | {{< icon "check" >}} | | **keep()** | {{< icon "check" "v2" >}} | {{< icon "check" "v2" >}} |
| **last()** | {{< icon "check" >}} | {{< icon "check" >}} | | **last()** | {{< icon "check" "v2" >}} | {{< icon "check" "v2" >}} |
| **max()** | {{< icon "check" >}} | {{< icon "check" >}} | | **max()** | {{< icon "check" "v2" >}} | {{< icon "check" "v2" >}} |
| **mean()** | {{< icon "check" >}} | {{< icon "check" >}} | | **mean()** | {{< icon "check" "v2" >}} | {{< icon "check" "v2" >}} |
| **min()** | {{< icon "check" >}} | {{< icon "check" >}} | | **min()** | {{< icon "check" "v2" >}} | {{< icon "check" "v2" >}} |
| **range()** | {{< icon "check" >}} | {{< icon "check" >}} | | **range()** | {{< icon "check" "v2" >}} | {{< icon "check" "v2" >}} |
| **rename()** | {{< icon "check" >}} | {{< icon "check" >}} | | **rename()** | {{< icon "check" "v2" >}} | {{< icon "check" "v2" >}} |
| **sum()** | {{< icon "check" >}} | {{< icon "check" >}} | | **sum()** | {{< icon "check" "v2" >}} | {{< icon "check" "v2" >}} |
| **window()** | {{< icon "check" >}} | {{< icon "check" >}} | | **window()** | {{< icon "check" "v2" >}} | {{< icon "check" "v2" >}} |
| _Function combinations_ | | | | _Function combinations_ | | |
| **group()** \|> **count()** | | {{< icon "check" >}} | | **group()** \|> **count()** | | {{< icon "check" "v2" >}} |
| **group()** \|> **first()** | | {{< icon "check" >}} | | **group()** \|> **first()** | | {{< icon "check" "v2" >}} |
| **group()** \|> **last()** | | {{< icon "check" >}} | | **group()** \|> **last()** | | {{< icon "check" "v2" >}} |
| **group()** \|> **max()** | | {{< icon "check" >}} | | **group()** \|> **max()** | | {{< icon "check" "v2" >}} |
| **group()** \|> **min()** | | {{< icon "check" >}} | | **group()** \|> **min()** | | {{< icon "check" "v2" >}} |
| **group()** \|> **sum()** | | {{< icon "check" >}} | | **group()** \|> **sum()** | | {{< icon "check" "v2" >}} |
| **window()** \|> **count()** | {{< icon "check" >}} | {{< icon "check" >}} | | **window()** \|> **count()** | {{< icon "check" "v2" >}} | {{< icon "check" "v2" >}} |
| **window()** \|> **first()** | {{< icon "check" >}} | {{< icon "check" >}} | | **window()** \|> **first()** | {{< icon "check" "v2" >}} | {{< icon "check" "v2" >}} |
| **window()** \|> **last()** | {{< icon "check" >}} | {{< icon "check" >}} | | **window()** \|> **last()** | {{< icon "check" "v2" >}} | {{< icon "check" "v2" >}} |
| **window()** \|> **max()** | {{< icon "check" >}} | {{< icon "check" >}} | | **window()** \|> **max()** | {{< icon "check" "v2" >}} | {{< icon "check" "v2" >}} |
| **window()** \|> **min()** | {{< icon "check" >}} | {{< icon "check" >}} | | **window()** \|> **min()** | {{< icon "check" "v2" >}} | {{< icon "check" "v2" >}} |
| **window()** \|> **sum()** | {{< icon "check" >}} | {{< icon "check" >}} | | **window()** \|> **sum()** | {{< icon "check" "v2" >}} | {{< icon "check" "v2" >}} |
{{% caption %}} {{% caption %}}
{{< req "\*" >}} **filter()** only pushes down when all parameter values are static. {{< req "\*" >}} **filter()** only pushes down when all parameter values are static.

2
content/influxdb/v2.0/security/tokens/create-token.md
View File

@ -25,7 +25,7 @@ Tokens are visible to the user who created the token. {{% oss-only %}} Users who
{{< nav-icon "disks" >}} {{< nav-icon "disks" >}}
2. Click **{{< icon "plus" >}} Generate** and select a token type 2. Click **{{< icon "plus" "v2" >}} Generate** and select a token type
(**Read/Write Token** or **All-Access Token**). (**Read/Write Token** or **All-Access Token**).
3. In the window that appears, enter a description for your token in the **Description** field. 3. In the window that appears, enter a description for your token in the **Description** field.
4. If generating a **read/write token**: 4. If generating a **read/write token**:

4
content/influxdb/v2.0/security/tokens/update-tokens.md
View File

@ -19,7 +19,7 @@ Update an API token's description using the InfluxDB user interface (UI).
{{< nav-icon "disks" >}} {{< nav-icon "disks" >}}
2. Click the pencil icon {{< icon "pencil" >}} next to the token's name in the **Description** column. 2. Click the pencil icon {{< icon "pencil" "v2" >}} next to the token's name in the **Description** column.
3. Update the token description, then click anywhere else to save. 3. Update the token description, then click anywhere else to save.
## Enable or disable a token ## Enable or disable a token
@ -28,4 +28,4 @@ Update an API token's description using the InfluxDB user interface (UI).
{{< nav-icon "disks" >}} {{< nav-icon "disks" >}}
2. Click the **{{< icon "toggle-green" >}} Status** toggle. 2. Click the **{{< icon "toggle-green" "v2" >}} Status** toggle.

2
content/influxdb/v2.0/telegraf-configs/clone.md
View File

@ -16,6 +16,6 @@ Use the InfluxDB user interface (UI) to clone a Telegraf configuration.
{{< nav-icon "load data" >}} {{< nav-icon "load data" >}}
2. Hover over the configuration you want to clone, click the **{{< icon "clone" >}}** 2. Hover over the configuration you want to clone, click the **{{< icon "clone" "v2" >}}**
icon, and then click **Clone**. icon, and then click **Clone**.
The clone appears in your list of Telegraf configurations. The clone appears in your list of Telegraf configurations.

2
content/influxdb/v2.0/telegraf-configs/remove.md
View File

@ -32,7 +32,7 @@ To remove a Telegraf configuration, do one of the following:
{{< nav-icon "load data" >}} {{< nav-icon "load data" >}}
2. Hover over the configuration you want to delete, click the **{{< icon "trash" >}}** 2. Hover over the configuration you want to delete, click the **{{< icon "trash" "v2" >}}**
icon, and then click **Delete**. icon, and then click **Delete**.

2
content/influxdb/v2.0/telegraf-configs/update.md
View File

@ -33,7 +33,7 @@ Telegraf doesn't detect changes to remote configurations. If you edit a remote c
{{< nav-icon "load data" >}} {{< nav-icon "load data" >}}
2. Hover over the configuration you want to edit and click **{{< icon "pencil" >}}** 2. Hover over the configuration you want to edit and click **{{< icon "pencil" "v2" >}}**
to update the name or description. to update the name or description.
3. Press **Return** or click out of the editable field to save your changes. 3. Press **Return** or click out of the editable field to save your changes.

4
content/influxdb/v2.0/tools/chronograf.md
View File

@ -22,7 +22,7 @@ Continue to use Chronograf with **InfluxDB Cloud** and **InfluxDB OSS 2.0** and
## Create an InfluxDB connection ## Create an InfluxDB connection
1. In Choronograf, click **Configuration** in the left navigation bar, 1. In Choronograf, click **Configuration** in the left navigation bar,
and then click **{{< icon "plus" >}} Add Connection**. and then click **{{< icon "plus" "v2" >}} Add Connection**.
2. Toggle the **InfluxDB v2 Auth** option at the bottom of the form. 2. Toggle the **InfluxDB v2 Auth** option at the bottom of the form.
{{< img-hd src="/img/influxdb/2-0-tools-chronograf-v2-auth.png" alt="InfluxDB v2 Auth toggle" />}} {{< img-hd src="/img/influxdb/2-0-tools-chronograf-v2-auth.png" alt="InfluxDB v2 Auth toggle" />}}
@ -83,7 +83,7 @@ For example, you **cannot** do the following:
- Kill queries - Kill queries
When connected to an InfluxDB Cloud or InfluxDB 2.0 database, functionality in the When connected to an InfluxDB Cloud or InfluxDB 2.0 database, functionality in the
**{{< icon "crown" >}} InfluxDB Admin** section of Chronograf is disabled. **{{< icon "crown" "v2" >}} InfluxDB Admin** section of Chronograf is disabled.
To complete administrative tasks, use the following: To complete administrative tasks, use the following:

12
content/influxdb/v2.0/visualize-data/dashboards/control-dashboard.md
View File

@ -16,13 +16,13 @@ Use dashboard controls in the upper left to update your dashboard.
### Add a cell ### Add a cell
Click **{{< icon "add-cell" >}} Add Cell** to open the Data Explorer and configure a new cell for your dashboard. Click **{{< icon "add-cell" "v2" >}} Add Cell** to open the Data Explorer and configure a new cell for your dashboard.
For details on using the Data Explorer, see [Explore metrics](/influxdb/v2.0/visualize-data/explore-metrics/). For details on using the Data Explorer, see [Explore metrics](/influxdb/v2.0/visualize-data/explore-metrics/).
### Add a note ### Add a note
1. Click **{{< icon "note" >}} Add Note** to add a note cell to your dashboard. 1. Click **{{< icon "note" "v2" >}} Add Note** to add a note cell to your dashboard.
2. Enter your note in Markdown in the left pane. A preview appears in the right pane. 2. Enter your note in Markdown in the left pane. A preview appears in the right pane.
3. Enable the **Show note when query returns no data** option to show the note only when the query displays no data. 3. Enable the **Show note when query returns no data** option to show the note only when the query displays no data.
4. Click **Save**. 4. Click **Save**.
@ -35,12 +35,12 @@ Click the timezone dropdown to select a timezone to use for the dashboard. Selec
### Manually refresh dashboard ### Manually refresh dashboard
Click the refresh button (**{{< icon "refresh" >}}**) to manually refresh the dashboard's data. Click the refresh button (**{{< icon "refresh" "v2" >}}**) to manually refresh the dashboard's data.
#### Manually refresh a single dashboard cell #### Manually refresh a single dashboard cell
1. Click the **{{< icon "gear" >}}** on the dashboard cell you want to refresh. 1. Click the **{{< icon "gear" "v2" >}}** on the dashboard cell you want to refresh.
2. Click **{{< icon "refresh" >}} Refresh**. 2. Click **{{< icon "refresh" "v2" >}} Refresh**.
### Select time range ### Select time range
@ -59,7 +59,7 @@ Click **Variables** to display variables available for your dashboard. For detai
### Presentation mode ### Presentation mode
Click the fullscreen icon (**{{< icon "fullscreen" >}}**) to enter presentation mode. Presentation mode allows you to view [a dashboard] in full screen, hiding the left and top navigation menus so only the cells appear. This mode might be helpful, for example, for stationary screens dedicated to monitoring visualizations. Click the fullscreen icon (**{{< icon "fullscreen" "v2" >}}**) to enter presentation mode. Presentation mode allows you to view [a dashboard] in full screen, hiding the left and top navigation menus so only the cells appear. This mode might be helpful, for example, for stationary screens dedicated to monitoring visualizations.
### Toggle dark mode and light mode ### Toggle dark mode and light mode
Click the moon or sun icons to toggle your dashboard between **dark mode** and **light mode.** Click the moon or sun icons to toggle your dashboard between **dark mode** and **light mode.**

10
content/influxdb/v2.0/visualize-data/dashboards/create-dashboard.md
View File

@ -18,7 +18,7 @@ weight: 201
{{< nav-icon "dashboards" >}} {{< nav-icon "dashboards" >}}
2. Click the **{{< icon "plus" >}} Create Dashboard** menu in the upper right and select **New Dashboard**. 2. Click the **{{< icon "plus" "v2" >}} Create Dashboard** menu in the upper right and select **New Dashboard**.
3. Enter a name for your dashboard in the **Name this dashboard** field in the upper left. 3. Enter a name for your dashboard in the **Name this dashboard** field in the upper left.
@ -40,19 +40,19 @@ weight: 201
{{< nav-icon "dashboards" >}} {{< nav-icon "dashboards" >}}
2. Hover over the dashboard and click **{{< icon "copy" >}}**. 2. Hover over the dashboard and click **{{< icon "copy" "v2" >}}**.
3. Click **Clone**. The cloned dashboard opens. 3. Click **Clone**. The cloned dashboard opens.
#### Add data to your dashboard #### Add data to your dashboard
1. From your dashboard, click **{{< icon "add-cell" >}} Add Cell**. 1. From your dashboard, click **{{< icon "add-cell" "v2" >}} Add Cell**.
2. Create a query in the Data Explorer following the instructions in [Explore metrics](/influxdb/v2.0/visualize-data/explore-metrics). 2. Create a query in the Data Explorer following the instructions in [Explore metrics](/influxdb/v2.0/visualize-data/explore-metrics).
3. Enter a name for your cell in the upper left. 3. Enter a name for your cell in the upper left.
4. Click the checkmark icon (**{{< icon "checkmark" >}}**) to save the cell to your dashboard. 4. Click the checkmark icon (**{{< icon "checkmark" "v2" >}}**) to save the cell to your dashboard.
You can also send data to your dashboard directly from the Data Explorer. For details, [Explore metrics](/influxdb/v2.0/visualize-data/explore-metrics). You can also send data to your dashboard directly from the Data Explorer. For details, [Explore metrics](/influxdb/v2.0/visualize-data/explore-metrics).
#### Add a note to your dashboard #### Add a note to your dashboard
1. From your dashboard, click **{{< icon "note" >}} Add Note** in the upper left. 1. From your dashboard, click **{{< icon "note" "v2" >}} Add Note** in the upper left.
2. Enter your note in the window that appears. You can use Markdown syntax to format your note. 2. Enter your note in the window that appears. You can use Markdown syntax to format your note.
3. To preview your Markdown formatting, click the **Preview** option. 3. To preview your Markdown formatting, click the **Preview** option.
4. Click **Save**. 4. Click **Save**.

2
content/influxdb/v2.0/visualize-data/dashboards/delete-dashboard.md
View File

@ -15,7 +15,7 @@ To delete a dashboard from the InfluxDB user interface (UI):
{{< nav-icon "dashboards" >}} {{< nav-icon "dashboards" >}}
2. Hover over the dashboard in the list of dashboards and click **{{< icon "trash" >}}**. 2. Hover over the dashboard in the list of dashboards and click **{{< icon "trash" "v2" >}}**.
3. Click **Delete**. 3. Click **Delete**.
{{% warn %}} {{% warn %}}

2
content/influxdb/v2.0/visualize-data/dashboards/export-dashboard.md
View File

@ -17,7 +17,7 @@ InfluxDB lets you export dashboards from the InfluxDB user interface (UI).
{{< nav-icon "dashboards" >}} {{< nav-icon "dashboards" >}}
2. Hover over a dashboard and click the gear icon (**{{< icon "gear" >}}**), 2. Hover over a dashboard and click the gear icon (**{{< icon "gear" "v2" >}}**),
and then select **Export**. and then select **Export**.
3. Review the JSON in the window that appears. 3. Review the JSON in the window that appears.
4. Select one of the following options: 4. Select one of the following options:

6
content/influxdb/v2.0/visualize-data/labels.md
View File

@ -20,7 +20,7 @@ To manage labels:
#### Create a label #### Create a label
1. Click **{{< icon "plus" >}} Create Label**. 1. Click **{{< icon "plus" "v2" >}} Create Label**.
2. Enter a **Name** for the label. 2. Enter a **Name** for the label.
3. Enter a description for the label _(Optional)_. 3. Enter a description for the label _(Optional)_.
4. Select a **Color** for the label. 4. Select a **Color** for the label.
@ -33,12 +33,12 @@ To manage labels:
3. Click **Save Changes**. 3. Click **Save Changes**.
#### Delete a label #### Delete a label
1. In the label list view, hover over the label you would like to delete and click **{{< icon "trash" >}}**. 1. In the label list view, hover over the label you would like to delete and click **{{< icon "trash" "v2" >}}**.
2. Click **Delete**. 2. Click **Delete**.
### Add labels to dashboard items ### Add labels to dashboard items
1. In the list view of dashboards, tasks, or other assets, hover over the item to which you would like to add a label. 1. In the list view of dashboards, tasks, or other assets, hover over the item to which you would like to add a label.
2. Click the {{< icon "add-label" >}} icon that appears below the name. 2. Click the {{< icon "add-label" "v2" >}} icon that appears below the name.
The **Add Labels** overlay will appear. The **Add Labels** overlay will appear.
3. Type the name of the label you would like to add to filter the list of available labels. 3. Type the name of the label you would like to add to filter the list of available labels.
Click the label you would like to add. Click the label you would like to add.

2
content/influxdb/v2.0/visualize-data/variables/create-variable.md
View File

@ -66,7 +66,7 @@ InfluxDB lets you import variables exported from InfluxDB in JSON format.
{{< nav-icon "settings" >}} {{< nav-icon "settings" >}}
2. Select the **Variables** tab. 2. Select the **Variables** tab.
3. Click the **{{< icon "plus" >}} Create Variable** drop-down menu and select **Import Variable**. 3. Click the **{{< icon "plus" "v2" >}} Create Variable** drop-down menu and select **Import Variable**.
4. In the window that appears: 4. In the window that appears:
- Select **Upload File** to drag and drop or select a file. - Select **Upload File** to drag and drop or select a file.
- Select **Paste JSON** to paste in JSON. - Select **Paste JSON** to paste in JSON.

2
content/influxdb/v2.0/visualize-data/variables/delete-variable.md
View File

@ -18,7 +18,7 @@ Delete an existing variable in the InfluxDB user interface (UI).
{{< nav-icon "settings" >}} {{< nav-icon "settings" >}}
2. Select the **Variables** tab. 2. Select the **Variables** tab.
3. Hover over a variable, click the **{{< icon "trash" >}}** icon, and **Delete**. 3. Hover over a variable, click the **{{< icon "trash" "v2" >}}** icon, and **Delete**.
{{% warn %}} {{% warn %}}
Once deleted, any dashboards with queries that utilize the variable will no Once deleted, any dashboards with queries that utilize the variable will no

2
content/influxdb/v2.0/visualize-data/variables/export-variable.md
View File

@ -18,7 +18,7 @@ Variables are exported as downloadable JSON files.
{{< nav-icon "settings" >}} {{< nav-icon "settings" >}}
2. Select the **Variables** tab. 2. Select the **Variables** tab.
3. Hover over a variable in the list, then click the gear icon (**{{< icon "gear" >}}**) 3. Hover over a variable in the list, then click the gear icon (**{{< icon "gear" "v2" >}}**)
and select **Export**. and select **Export**.
4. Review the JSON in the window that appears. 4. Review the JSON in the window that appears.
5. Select one of the following options: 5. Select one of the following options:

2
content/influxdb/v2.0/visualize-data/visualization-types/band.md
View File

@ -95,7 +95,7 @@ For example, in the band chart above, the lines represent the mean `usage_system
## Band controls ## Band controls
To view **Band** controls, click **{{< icon "gear" >}} Customize** next to the visualization dropdown. To view **Band** controls, click **{{< icon "gear" "v2" >}} Customize** next to the visualization dropdown.
###### Data ###### Data

2
content/influxdb/v2.0/visualize-data/visualization-types/gauge.md
View File

@ -30,7 +30,7 @@ For consistent results, the Gauge query should return a single table.
{{% /note %}} {{% /note %}}
## Gauge Controls ## Gauge Controls
To view **Gauge** controls, click **{{< icon "gear" >}} Customize** next to To view **Gauge** controls, click **{{< icon "gear" "v2" >}} Customize** next to
the visualization dropdown. the visualization dropdown.
- **Prefix**: Prefix to add to the gauge. - **Prefix**: Prefix to add to the gauge.

2
content/influxdb/v2.0/visualize-data/visualization-types/graph-single-stat.md
View File

@ -38,7 +38,7 @@ For consistent Single Stat results, the query should return a single table.
{{% /note %}} {{% /note %}}
## Graph + Single Stat Controls ## Graph + Single Stat Controls
To view **Graph + Single Stat** controls, click **{{< icon "gear" >}} Customize** next to To view **Graph + Single Stat** controls, click **{{< icon "gear" "v2" >}} Customize** next to
the visualization dropdown. the visualization dropdown.
###### Data ###### Data

2
content/influxdb/v2.0/visualize-data/visualization-types/graph.md
View File

@ -25,7 +25,7 @@ When multiple series are present, it automatically assigns colors based on the s
When using a line graph, all points within a single table are connected. When multiple series are present, it automatically assigns colors based on the selected [Line Colors option](#options). When using a line graph, all points within a single table are connected. When multiple series are present, it automatically assigns colors based on the selected [Line Colors option](#options).
## Graph controls ## Graph controls
To view **Graph** controls, click **{{< icon "gear" >}} Customize** next to To view **Graph** controls, click **{{< icon "gear" "v2" >}} Customize** next to
the visualization dropdown. the visualization dropdown.
###### Data ###### Data

2
content/influxdb/v2.0/visualize-data/visualization-types/heatmap.md
View File

@ -29,7 +29,7 @@ The total number of points that fall within a bin determine the its value and co
Warmer or brighter colors represent higher bin values or density of points within the bin. Warmer or brighter colors represent higher bin values or density of points within the bin.
## Heatmap Controls ## Heatmap Controls
To view **Heatmap** controls, click **{{< icon "gear" >}} Customize** next to To view **Heatmap** controls, click **{{< icon "gear" "v2" >}} Customize** next to
the visualization dropdown. the visualization dropdown.
###### Data ###### Data

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