moved v2.0 into influxdb namespace, added aliases to all but flux docs

pull/1387/head
Scott Anderson 2020-07-28 15:59:56 -06:00
parent e15fe08919
commit 0ce7c1a38e
674 changed files with 1280 additions and 1429 deletions

View File

@ -1,13 +1,11 @@
---
title: InfluxDB v2.0 documentation
description: >
InfluxDB is an open source time series database designed to handle high write and query loads.
Learn how to use and leverage InfluxDB in use cases such as monitoring metrics, IoT data, and events.
layout: version-landing
menu:
influxdb_2_0:
name: InfluxDB 2.0 home
weight: 1
versions:
name: v2.0
aliases:
- /v2.0/
---

View File

@ -9,7 +9,7 @@ aliases:
- /v2.0/cloud/account-management/
- /v2.0/account-management
menu:
influxdb_2_0:
v2_0:
name: Account management
products: [cloud]
---

View File

@ -10,7 +10,7 @@ aliases:
- /v2.0/account-management/billing
weight: 103
menu:
influxdb_2_0:
v2_0:
parent: Account management
name: Manage billing
products: [cloud]
@ -34,16 +34,14 @@ products: [cloud]
Add your payment method and view billing information in the {{< cloud-name "short" >}} user interface (UI).
## Access billing details
1. In the {{< cloud-name "short" >}} UI, select the **user avatar** in the left
navigation menu, and select **Billing**.
{{< nav-icon "account" >}}
2. Do one of the following:
- If you subscribed to an InfluxDB Cloud 2.0 plan through [**AWS Marketplace**](https://aws.amazon.com/marketplace/pp/B08234JZPS)
or [**GCP Marketplace**](https://console.cloud.google.com/marketplace/details/influxdata-public/cloud2-gcp-marketplace-prod?pli=1), click the **AWS** or **GCP** link to access your
- If you subscribed to an InfluxDB Cloud 2.0 plan through **AWS Marketplace**
or **GCP Marketplace**, click the **AWS** or **GCP** link to access your
billing and subscription information.
- If you subscribed to an InfluxDB Cloud 2.0 plan through **InfluxData**, complete the following procedures as needed:
@ -54,7 +52,7 @@ Add your payment method and view billing information in the {{< cloud-name "shor
View information about:
- [Usage-Based Plan](#view-usage-based-plan-information)
- [Usage-based Plan](#view-usage-based-plan-information)
- [Free Plan](#view-free-plan-information)
- [Exceeded rate limits](#exceeded-rate-limits)
- [Billing cycle](#billing-cycle)

View File

@ -8,7 +8,7 @@ aliases:
- /v2.0/cloud/account-management/data-usage
- /v2.0/account-management/data-usage
menu:
influxdb_2_0:
v2_0:
parent: Account management
name: View data usage
products: [cloud]
@ -19,15 +19,17 @@ right corner of your {{< cloud-name "short" >}} user interface (UI) and select *
Find data usage information for the time frame specified in the drop-down at the top of the Usage page.
- **Data In:** Total data in MB written to your {{< cloud-name "short" >}} instance.
- **Data Out:** Total data in MB sent as responses to queries from your {{< cloud-name "short" >}} instance.
- **Query Count:** Total number of individual query operations, which include queries, tasks (alerts, notifications) and Data Explorer activity.
- **Writes:** Total data in MB written to your {{< cloud-name "short" >}} instance.
- **Reads:** Total data in MB sent as responses to queries from your {{< cloud-name "short" >}} instance.
- **Query Duration:** Total time spent processing queries in seconds.
- **Storage Usage:** Total disk usage in gigabytes.
- **API Request Count:** The total number of query and write API requests received during the specified time frame.
- **API Request Count:** The total number of query and write API requests received
during the specified time frame.
- **Usage over the specified time period:** A line graph that visualizes usage over the specified time period.
- **Rate Limits over the specified time period:** A list of rate limit events over the specified time period.
- **Rate Limits over the specified time period:** A list of rate limit events over
the specified time period.
{{< img-hd src="/img/influxdb/2-0-cloud-usage.png" />}}
{{< img-hd src="/img/2-0-cloud-usage.png" />}}
## Exceeded rate limits

View File

@ -6,7 +6,7 @@ weight: 4
aliases:
- /v2.0/account-management/multi-user
menu:
influxdb_2_0:
v2_0:
parent: Account management
name: Manage multiple users
---

View File

@ -7,7 +7,7 @@ weight: 103
aliases:
- /v2.0/account-management/multi-user/invite-user
menu:
influxdb_2_0:
v2_0:
parent: Manage multiple users
identifier: invite_user_cloud
---

View File

@ -7,7 +7,7 @@ weight: 103
aliases:
- /v2.0/account-management/multi-user/remove-user
menu:
influxdb_2_0:
v2_0:
parent: Manage multiple users
identifier: remove_user_cloud
---

View File

@ -8,7 +8,7 @@ aliases:
- /v2.0/cloud/account-management/offboarding
- /v2.0/account-management/offboarding
menu:
influxdb_2_0:
v2_0:
parent: Account management
name: Cancel InfluxDB Cloud
products: [cloud]

View File

@ -7,7 +7,7 @@ weight: 2
aliases:
- /v2.0/account-management/pricing-calculator
menu:
influxdb_2_0:
v2_0:
name: Pricing calculator
products: [cloud]
draft: true

View File

@ -9,7 +9,7 @@ aliases:
- /v2.0/account-management/pricing-plans
weight: 102
menu:
influxdb_2_0:
v2_0:
parent: Account management
name: Pricing plans
products: [cloud]
@ -19,7 +19,7 @@ v2.0/tags: [VPC]
InfluxDB Cloud 2.0 offers two pricing plans:
- [Free Plan](#free-plan)
- [Usage-Based Plan](#usage-based-plan)
- [Usage-based Plan](#usage-based-plan)
<!--To estimate your projected usage costs, use the [InfluxDB Cloud 2.0 pricing calculator](/v2.0/account-management/pricing-calculator/). -->
@ -30,7 +30,7 @@ Use this plan as much and as long as you want within the Free Plan rate limits:
#### Free Plan rate limits
- **Data In:** 5.1MB every 5 minutes
- **Writes:** 5.1MB every 5 minutes
- **Query:** 300MB every 5 minutes
- **Storage:** 30-day data retention
{{% note %}}
@ -48,24 +48,15 @@ Data retention is determined by the time at which data is written to InfluxDB; n
_To remove rate limits, [upgrade to a Usage-based Plan](/v2.0/account-management/billing/#upgrade-to-usage-based-plan)._
## Usage-Based Plan
## Usage-based Plan
The Usage-Based Plan offers more flexibility and ensures you only pay for what you [use](/v2.0/account-management/data-usage/).
The Usage-based Plan offers more flexibility and ensures you only pay for what you [use](/v2.0/account-management/data-usage/).
### Pricing vectors
#### Usage-based Plan rate limits
The following two vectors determine pricing:
To protect against any intentional or unintentional harm, Usage-based Plans include soft rate limits:
- **Data out** is the total sum of the data (measured in GB) returned to the user to answer a query, also known as data transfer costs.
- **Query count** is the total number of individual query operations. Each individual operation — including
queries, tasks, alert checks, notifications, and Data Explorer activity — is one billable query operation. Refreshing a dashboard with multiple cells counts as one query operation per cell. A query run through an API request counts as an operation. Failed query or task executions do not add to your query count.
### Usage-Based Plan rate limits
To protect against any intentional or unintentional harm, Usage-Based Plans include soft rate limits:
- **Data In:** Write 300MB every 5 minutes
- **Writes:** 300MB every 5 minutes
- **Ingest batch size:** 50MB
- **Queries:** 3000MB every 5 minutes
- **Storage:** Unlimited retention

View File

@ -4,11 +4,11 @@ seotitle: Backup and restore data with InfluxDB
description: >
InfluxDB provides tools that let you back up and restore data and metadata stored
in InfluxDB.
influxdb/v2.0/tags: [backup, restore]
v2.0/tags: [backup, restore]
aliases:
- /v2.0/backup-restore
menu:
influxdb_2_0:
v2_0:
name: Back up & restore data
weight: 9
products: [oss]

View File

@ -4,14 +4,14 @@ seotitle: Back up data in InfluxDB
description: >
Use the `influx backup` command to back up data and metadata stored in InfluxDB.
menu:
influxdb_2_0:
v2_0:
parent: Back up & restore data
weight: 101
aliases:
- /v2.0/backup-restore/backup
related:
- /influxdb/v2.0/backup-restore/restore/
- /influxdb/v2.0/reference/cli/influx/backup/
- /v2.0/backup-restore/restore/
- /v2.0/reference/cli/influx/backup/
products: [oss]
---

View File

@ -4,15 +4,15 @@ seotitle: Restore data in InfluxDB
description: >
Use the `influxd restore` command to restore backup data and metadata from InfluxDB.
menu:
influxdb_2_0:
v2_0:
parent: Back up & restore data
weight: 101
influxdb/v2.0/tags: [restore]
v2.0/tags: [restore]
aliases:
- /v2.0/backup-restore/restore
related:
- /influxdb/v2.0/backup-restore/backup/
- /influxdb/v2.0/reference/cli/influxd/restore/
- /v2.0/backup-restore/backup/
- /v2.0/reference/cli/influxd/restore/
products: [oss]
---

View File

@ -2,14 +2,14 @@
title: Example post
description: This is just an example post to show the format of new 2.0 posts
menu:
influxdb_2_0:
v2_0:
name: Example post
weight: 1
draft: true
"v2.0/tags": [influxdb, functions]
related:
- /influxdb/v2.0/write-data/
- /influxdb/v2.0/write-data/quick-start
- /v2.0/write-data/
- /v2.0/write-data/quick-start
- https://influxdata.com, This is an external link
products: [cloud, oss, enterprise]
---
@ -61,7 +61,7 @@ WHERE time > now() - 15m
### h3 This is a header3
This is a paragraph. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc rutrum, metus id scelerisque euismod, erat ante suscipit nibh, ac congue enim risus id est. Etiam tristique nisi et tristique auctor. Morbi eu bibendum erat. Sed ullamcorper, dui id lobortis efficitur, mauris odio pharetra neque, vel tempor odio dolor blandit justo.
![Test image](/img/chronograf/1-6-alerts-conditions.png)
![Test image](http://docs.influxdata.com/img/chronograf/v1.7/alerts-conditions.png)
{{< img-hd src="/img/test-image-2.png" alt="Test Image" />}}

View File

@ -2,10 +2,10 @@
title: Get started with InfluxDB
description: Download, install, and setup InfluxDB, creating a default organization, user, and bucket.
menu:
influxdb_2_0:
v2_0:
name: Get started
weight: 2
influxdb/v2.0/tags: [get-started, install]
weight: 1
v2.0/tags: [get-started, install]
aliases:
- /v2.0/cloud/get-started
- /v2.0/get-started
@ -89,7 +89,7 @@ References to the InfluxDB user interface (UI) or localhost:9999 refer to your
{{< cloud-name >}} UI.
{{% /cloud %}}
### (Optional) Download, install, and use the influx CLI
### (Optional) Download and install the influx CLI
To use the `influx` CLI to manage and interact with your InfluxDB Cloud instance, complete the following steps:
@ -102,13 +102,13 @@ To use the `influx` CLI to manage and interact with your InfluxDB Cloud instance
<!-------------------------------- BEGIN macOS -------------------------------->
{{% tab-content %}}
#### Step 1: Download influx CLI for macOS
#### Download influx CLI for macOS
Click the following button to download and install `influx` CLI for macOS.
<a class="btn download" href="https://dl.influxdata.com/influxdb/releases/influxdb_client_2.0.0-beta.16_darwin_amd64.tar.gz" download>influx CLI (macOS)</a>
#### Step 2: Unpackage the influx binary
#### Unpackage the influx binary
**Note:** The commands below are examples. Adjust the file names, paths, and utilities to your own needs.
@ -121,7 +121,7 @@ or run the following command in a macOS command prompt application such
tar zxvf ~/Downloads/influxdb_client_2.0.0-beta.16_darwin_amd64.tar.gz
```
#### Step 3: (Optional) Place the binary in your $PATH
#### (Optional) Place the binary in your $PATH
If you choose, you can place `influx` in your `$PATH` or you can
prefix the executable with `./` to run in place. If the binary is on your $PATH, you can run `influx` from any directory. Otherwise, you must specify the location of the CLI (for example, `./influx`or `path/to/influx`).
@ -137,31 +137,11 @@ sudo cp influxdb_client_2.0.0-beta.16_darwin_amd64/influx /usr/local/bin/
If you rename the binary, all references to `influx` in this documentation refer to the renamed binary.
{{% /note %}}
#### Step 4: Run influx CLI on macOS Catalina
##### Run influx CLI on macOS Catalina
If you're running `influx` on macOS Catalina, you must [manually authorize the InfluxDB binaries](/v2.0/get-started/#run-influxdb-on-macos-catalina).
#### Step 5: Set up a configuration profile
To avoid having to pass your InfluxDB [authentication token](/v2.0/users/tokens/) with each `influx` command, set up a configuration profile that stores your credentials.
In a terminal, run the following command:
```sh
# Set up a configuration profile
influx config create -n default \
-u http://localhost:9999 \
-o example-org \
-t mySuP3rS3cr3tT0keN \
-a
```
This configures a new profile named `default` and makes the profile active so your `influx` CLI commands run against this instance.
For more detail, see [influx config](/v2.0/reference/cli/influx/config/).
#### Step 6: Learn `influx` CLI commands
To see all available `influx` commands, type `influx -h` or check out [influx - InfluxDB command line interface](https://v2.docs.influxdata.com/v2.0/reference/cli/influx/).
Now, you're ready to [Use the influx CLI](#use-the-influx-cli).
{{% /tab-content %}}
<!--------------------------------- END macOS --------------------------------->
@ -169,14 +149,14 @@ To see all available `influx` commands, type `influx -h` or check out [influx -
<!-------------------------------- BEGIN Linux -------------------------------->
{{% tab-content %}}
#### Step 1: Download influx CLI for Linux
#### Download influx CLI for Linux
Click one of the following buttons to download and install the `influx` CLI appropriate for your chipset.
<a class="btn download" href="https://dl.influxdata.com/influxdb/releases/influxdb_client_2.0.0-beta.16_linux_amd64.tar.gz" download >influx CLI (amd64)</a>
<a class="btn download" href="https://dl.influxdata.com/influxdb/releases/influxdb_client_2.0.0-beta.16_linux_arm64.tar.gz" download >influx CLI (arm)</a>
#### Step 2: Unpackage the influx binary
#### Unpackage the influx binary
**Note:** The commands below are examples. Adjust the file names, paths, and utilities to your own needs.
@ -185,7 +165,7 @@ Click one of the following buttons to download and install the `influx` CLI appr
tar xvfz influxdb_client_2.0.0-beta.16_linux_amd64.tar.gz
```
#### Step 3: (Optional) Place the binary in your $PATH
#### (Optional) Place the binary in your $PATH
If you choose, you can place `influx` in your `$PATH` or you can
prefix the executable with `./` to run in place. If the binary is on your $PATH, you can run `influx` from any directory. Otherwise, you must specify the location of the CLI (for example, `./influx`or `path/to/influx`).
@ -201,27 +181,7 @@ sudo cp influxdb_client_2.0.0-beta.16_linux_amd64/influx /usr/local/bin/
If you rename the binary, all references to `influx` in this documentation refer to the renamed binary.
{{% /note %}}
#### Step 4: Set up a configuration profile
To avoid having to pass your InfluxDB [authentication token](/v2.0/users/tokens/) with each `influx` command, set up a configuration profile that stores your credentials.
In a terminal, run the following command:
```sh
# Set up a configuration profile
influx config create -n default \
-u http://localhost:9999 \
-o example-org \
-t mySuP3rS3cr3tT0keN \
-a
```
This configures a new profile named `default` and makes the profile active so your `influx` CLI commands run against this instance.
For more detail, see [influx config](/v2.0/reference/cli/influx/config/).
#### Step 5: Learn `influx` CLI commands
To see all available `influx` commands, type `influx -h` or check out [influx - InfluxDB command line interface](https://v2.docs.influxdata.com/v2.0/reference/cli/influx/).
Now, you're ready to [Use the influx CLI](#use-the-influx-cli).
{{% /tab-content %}}
<!--------------------------------- END Linux --------------------------------->
@ -537,25 +497,24 @@ the `influx` command line interface (CLI).
InfluxDB is now initialized with a primary user, organization, and bucket.
You are ready to [write or collect data](/v2.0/write-data).
### (Optional) Step up and use the influx CLI
{{% note %}}
#### Use the influx CLI
If you set up InfluxDB through the UI and want to use the [`influx` CLI](/v2.0/reference/cli/influx), we recommend setting up a configuration profile. This lets you avoid having to pass your InfluxDB [authentication token](/v2.0/users/tokens/) with each `influx` command. Complete the following steps to set up a configuration profile that stores your credentials.
To use the [`influx` CLI](/v2.0/reference/cli/influx) after setting up InfluxDB, provide your [authentication token](/v2.0/users/tokens/), which is automatically generated during the setup process. For instructions on viewing your token via CLI or UI, see [View tokens](/v2.0/security/tokens/view-tokens/).
1. In a terminal, run the following command:
Use one of the following methods to provide your authentication token to the CLI:
```sh
# Set up a configuration profile
influx config create -n default \
-u http://localhost:9999 \
-o example-org \
-t mySuP3rS3cr3tT0keN \
-a
```
- Create a new InfluxDB connection configuration using the [`influx config create` command](/v2.0/reference/cli/influx/config/create/).
- Pass your token to the `influx` CLI using the `-t` or `--token` flag.
- Set the `INFLUX_TOKEN` environment variable using your token.
This configures a new profile named `default` and makes the profile active so your `influx` CLI commands run against this instance.
For more detail, see [influx config](/v2.0/reference/cli/influx/config/).
```bash
export INFLUX_TOKEN=oOooYourAuthTokenOoooOoOO==
```
2. Learn `influx` CLI commands. To see all available `influx` commands, type `influx -h` or check out [influx - InfluxDB command line interface](/v2.0/reference/cli/influx/).
_See [View tokens](/v2.0/security/tokens/view-tokens/) for information about
retrieving authentication tokens._
{{% /note %}}
{{% /tab-content %}}
<!-------------------------------- END UI Setup ------------------------------->

View File

@ -3,11 +3,11 @@ title: InfluxDB templates
description: >
InfluxDB templates are prepackaged InfluxDB configurations that contain everything
from dashboards and Telegraf configurations to notifications and alerts.
menu: influxdb_2_0
menu: v2_0
weight: 9
aliases:
- /v2.0/influxdb-templates
influxdb/v2.0/tags: [templates]
v2.0/tags: [templates]
---
InfluxDB templates are prepackaged InfluxDB configurations that contain everything

View File

@ -5,14 +5,14 @@ description: >
Download and use the `influx` CLI to apply and manage InfluxDB templates with
your InfluxDB Cloud account.
menu:
influxdb_2_0:
v2_0:
parent: InfluxDB templates
name: Templates in Cloud
weight: 101
aliases:
- /v2.0/influxdb-templates/get_started_cloud/
- /v2.0/influxdb-templates/cloud/
influxdb/v2.0/tags: [templates]
v2.0/tags: [templates]
products: [cloud]
---

View File

@ -3,17 +3,17 @@ title: Create an InfluxDB template
description: >
Use the InfluxDB UI and the `influx export` command to create InfluxDB templates.
menu:
influxdb_2_0:
v2_0:
parent: InfluxDB templates
name: Create a template
identifier: Create an InfluxDB template
weight: 103
aliases:
- /v2.0/influxdb-templates/create/
influxdb/v2.0/tags: [templates]
v2.0/tags: [templates]
related:
- /influxdb/v2.0/reference/cli/influx/export/
- /influxdb/v2.0/reference/cli/influx/export/all/
- /v2.0/reference/cli/influx/export/
- /v2.0/reference/cli/influx/export/all/
---
Use the InfluxDB user interface (UI) and the `influx export` command to

View File

@ -6,13 +6,13 @@ description: >
when applying the same or similar templates more than once, and apply
changes to distributed instances of InfluxDB OSS or InfluxDB Cloud.
menu:
influxdb_2_0:
v2_0:
parent: InfluxDB templates
weight: 105
aliases:
- /v2.0/influxdb-templates/stacks/
related:
- /influxdb/v2.0/reference/cli/stacks/
- /v2.0/reference/cli/influx/pkg/stack/
---
**InfluxDB stacks** are **stateful [InfluxDB templates](/v2.0/influxdb-templates)**

View File

@ -6,14 +6,14 @@ description: >
**without providing a stack ID**.
To manually create or initialize a new stack, use the [`influx stacks init` command](/v2.0/reference/cli/influx/stacks/init/).
menu:
influxdb_2_0:
v2_0:
parent: InfluxDB stacks
name: Initialize a stack
weight: 201
aliases:
- /v2.0/influxdb-templates/stacks/init/
related:
- /influxdb/v2.0/reference/cli/influx/stacks/init/
- /v2.0/reference/cli/influx/stacks/init/
list_code_example: |
```sh
influx apply \

View File

@ -5,14 +5,14 @@ description: >
Use the [`influx stacks remove` command](/v2.0/reference/cli/influx/stacks/remove/)
to remove an InfluxDB stack and all its associated resources.
menu:
influxdb_2_0:
v2_0:
parent: InfluxDB stacks
name: Remove a stack
weight: 204
aliases:
- /v2.0/influxdb-templates/stacks/remove/
related:
- /influxdb/v2.0/reference/cli/influx/stacks/remove/
- /v2.0/reference/cli/influx/stacks/remove/
list_code_example: |
```sh
influx stacks remove \

View File

@ -9,15 +9,15 @@ description: >
InfluxDB updates, adds, and removes resources to resolve differences between
the current state of the stack and the newly applied template.
menu:
influxdb_2_0:
v2_0:
parent: InfluxDB stacks
name: Update a stack
weight: 202
aliases:
- /v2.0/influxdb-templates/stacks/update/
related:
- /influxdb/v2.0/reference/cli/influx/apply
- /influxdb/v2.0/reference/cli/influx/stacks/update/
- /v2.0/reference/cli/influx/apply
- /v2.0/reference/cli/influx/stacks/update/
list_code_example: |
```sh
influx apply \

View File

@ -5,14 +5,14 @@ description: >
Use the [`influx stacks` command](/v2.0/reference/cli/influx/stacks/)
to view installed InfluxDB stacks and their associated resources.
menu:
influxdb_2_0:
v2_0:
parent: InfluxDB stacks
name: View stacks
weight: 203
aliases:
- /v2.0/influxdb-templates/stacks/views/
related:
- /influxdb/v2.0/reference/cli/influx/stacks/
- /v2.0/reference/cli/influx/stacks/
list_code_example: |
```sh
influx stacks -o example-org

View File

@ -4,17 +4,17 @@ description: >
Use the `influx` command line interface (CLI) to summarize, validate, and apply
templates from your local filesystem and from URLs.
menu:
influxdb_2_0:
v2_0:
parent: InfluxDB templates
name: Use templates
weight: 102
aliases:
- /v2.0/influxdb-templates/use/
influxdb/v2.0/tags: [templates]
v2.0/tags: [templates]
related:
- /influxdb/v2.0/reference/cli/influx/apply/
- /influxdb/v2.0/reference/cli/influx/template/
- /influxdb/v2.0/reference/cli/influx/template/validate/
- /v2.0/reference/cli/influx/apply/
- /v2.0/reference/cli/influx/template/
- /v2.0/reference/cli/influx/template/validate/
---
Use the `influx` command line interface (CLI) to summarize, validate, and apply

View File

@ -5,12 +5,12 @@ description: >
Monitor your time series data and send alerts by creating checks, notification
rules, and notification endpoints. Or use community templates to monitor supported environments.
menu:
influxdb_2_0:
v2_0:
name: Monitor & alert
weight: 6
aliases:
- /v2.0/monitor-alert/
influxdb/v2.0/tags: [monitor, alert, checks, notification, endpoints]
v2.0/tags: [monitor, alert, checks, notification, endpoints]
---
Monitor your time series data and send alerts by creating checks, notification

View File

@ -4,15 +4,15 @@ seotitle: Manage monitoring checks in InfluxDB
description: >
Checks in InfluxDB query data and apply a status or level to each data point based on specified conditions.
menu:
influxdb_2_0:
v2_0:
parent: Monitor & alert
weight: 101
aliases:
- /v2.0/monitor-alert/checks/
influxdb/v2.0/tags: [monitor, checks, notifications, alert]
v2.0/tags: [monitor, checks, notifications, alert]
related:
- /influxdb/v2.0/monitor-alert/notification-rules/
- /influxdb/v2.0/monitor-alert/notification-endpoints/
- /v2.0/monitor-alert/notification-rules/
- /v2.0/monitor-alert/notification-endpoints/
---
Checks in InfluxDB query data and apply a status or level to each data point based on specified conditions.

View File

@ -4,14 +4,14 @@ seotitle: Create monitoring checks in InfluxDB
description: >
Create a check in the InfluxDB UI.
menu:
influxdb_2_0:
v2_0:
parent: Manage checks
weight: 201
aliases:
- /v2.0/monitor-alert/checks/create/
related:
- /influxdb/v2.0/monitor-alert/notification-rules/
- /influxdb/v2.0/monitor-alert/notification-endpoints/
- /v2.0/monitor-alert/notification-rules/
- /v2.0/monitor-alert/notification-endpoints/
---
Create a check in the InfluxDB user interface (UI).

View File

@ -4,14 +4,14 @@ seotitle: Delete monitoring checks in InfluxDB
description: >
Delete checks in the InfluxDB UI.
menu:
influxdb_2_0:
v2_0:
parent: Manage checks
weight: 204
aliases:
- /v2.0/monitor-alert/checks/delete/
related:
- /influxdb/v2.0/monitor-alert/notification-rules/
- /influxdb/v2.0/monitor-alert/notification-endpoints/
- /v2.0/monitor-alert/notification-rules/
- /v2.0/monitor-alert/notification-endpoints/
---
If you no longer need a check, use the InfluxDB user interface (UI) to delete it.

View File

@ -4,14 +4,14 @@ seotitle: Update monitoring checks in InfluxDB
description: >
Update, rename, enable or disable checks in the InfluxDB UI.
menu:
influxdb_2_0:
v2_0:
parent: Manage checks
weight: 203
aliases:
- /v2.0/monitor-alert/checks/update/
related:
- /influxdb/v2.0/monitor-alert/notification-rules/
- /influxdb/v2.0/monitor-alert/notification-endpoints/
- /v2.0/monitor-alert/notification-rules/
- /v2.0/monitor-alert/notification-endpoints/
---
Update checks in the InfluxDB user interface (UI).

View File

@ -4,14 +4,14 @@ seotitle: View monitoring checks in InfluxDB
description: >
View check details and statuses and notifications generated by checks in the InfluxDB UI.
menu:
influxdb_2_0:
v2_0:
parent: Manage checks
weight: 202
aliases:
- /v2.0/monitor-alert/checks/view/
related:
- /influxdb/v2.0/monitor-alert/notification-rules/
- /influxdb/v2.0/monitor-alert/notification-endpoints/
- /v2.0/monitor-alert/notification-rules/
- /v2.0/monitor-alert/notification-endpoints/
---
View check details and statuses and notifications generated by checks in the InfluxDB user interface (UI).

View File

@ -3,16 +3,16 @@ title: Manage notification endpoints
list_title: Manage notification endpoints
description: >
Create, read, update, and delete endpoints in the InfluxDB UI.
influxdb/v2.0/tags: [monitor, endpoints, notifications, alert]
v2.0/tags: [monitor, endpoints, notifications, alert]
menu:
influxdb_2_0:
v2_0:
parent: Monitor & alert
weight: 102
aliases:
- /v2.0/monitor-alert/notification-endpoints/
related:
- /influxdb/v2.0/monitor-alert/checks/
- /influxdb/v2.0/monitor-alert/notification-rules/
- /v2.0/monitor-alert/checks/
- /v2.0/monitor-alert/notification-rules/
---
Notification endpoints store information to connect to a third party service.

View File

@ -3,15 +3,15 @@ title: Create notification endpoints
description: >
Create notification endpoints to send alerts on your time series data.
menu:
influxdb_2_0:
v2_0:
name: Create endpoints
parent: Manage notification endpoints
weight: 201
aliases:
- /v2.0/monitor-alert/notification-endpoints/create/
related:
- /influxdb/v2.0/monitor-alert/checks/
- /influxdb/v2.0/monitor-alert/notification-rules/
- /v2.0/monitor-alert/checks/
- /v2.0/monitor-alert/notification-rules/
---
To send notifications about changes in your data, start by creating a notification endpoint to a third party service. After creating notification endpoints, [create notification rules](/v2.0/monitor-alert/notification-rules/create) to send alerts to third party services on [check statuses](/v2.0/monitor-alert/checks/create).

View File

@ -3,15 +3,15 @@ title: Delete notification endpoints
description: >
Delete a notification endpoint in the InfluxDB UI.
menu:
influxdb_2_0:
v2_0:
name: Delete endpoints
parent: Manage notification endpoints
weight: 204
aliases:
- /v2.0/monitor-alert/notification-endpoints/delete/
- - /v2.0/monitor-alert/notification-endpoints/delete/
related:
- /influxdb/v2.0/monitor-alert/checks/
- /influxdb/v2.0/monitor-alert/notification-rules/
- /v2.0/monitor-alert/checks/
- /v2.0/monitor-alert/notification-rules/
---
If notifications are no longer sent to an endpoint, complete the steps below to delete the endpoint, and then [update notification rules](/v2.0/monitor-alert/notification-rules/update) with a new notification endpoint as needed.

View File

@ -3,15 +3,15 @@ title: Update notification endpoints
description: >
Update notification endpoints in the InfluxDB UI.
menu:
influxdb_2_0:
v2_0:
name: Update endpoints
parent: Manage notification endpoints
weight: 203
aliases:
- /v2.0/monitor-alert/notification-endpoints/update/
related:
- /influxdb/v2.0/monitor-alert/checks/
- /influxdb/v2.0/monitor-alert/notification-rules/
- /v2.0/monitor-alert/checks/
- /v2.0/monitor-alert/notification-rules/
---
To update the notification endpoint details, complete the procedures below as needed. To update the notification endpoint selected for a notification rule, see [update notification rules](/v2.0/monitor-alert/notification-rules/update/).

View File

@ -4,15 +4,15 @@ seotitle: View notification endpoint details and history
description: >
View notification endpoint details and history in the InfluxDB UI.
menu:
influxdb_2_0:
v2_0:
name: View endpoint history
parent: Manage notification endpoints
weight: 202
aliases:
- /v2.0/monitor-alert/notification-endpoints/view/
related:
- /influxdb/v2.0/monitor-alert/checks/
- /influxdb/v2.0/monitor-alert/notification-rules/
- /v2.0/monitor-alert/checks/
- /v2.0/monitor-alert/notification-rules/
---
View notification endpoint details and history in the InfluxDB user interface (UI).

View File

@ -5,13 +5,13 @@ description: >
weight: 103
aliases:
- /v2.0/monitor-alert/notification-rules/
influxdb/v2.0/tags: [monitor, notifications, alert]
v2.0/tags: [monitor, notifications, alert]
menu:
influxdb_2_0:
v2_0:
parent: Monitor & alert
related:
- /influxdb/v2.0/monitor-alert/checks/
- /influxdb/v2.0/monitor-alert/notification-endpoints/
- /v2.0/monitor-alert/checks/
- /v2.0/monitor-alert/notification-endpoints/
---
The following articles provide information on managing your notification rules:

View File

@ -6,11 +6,11 @@ weight: 201
aliases:
- /v2.0/monitor-alert/notification-rules/create/
menu:
influxdb_2_0:
v2_0:
parent: Manage notification rules
related:
- /influxdb/v2.0/monitor-alert/checks/
- /influxdb/v2.0/monitor-alert/notification-endpoints/
- /v2.0/monitor-alert/checks/
- /v2.0/monitor-alert/notification-endpoints/
---
Once you've set up checks and notification endpoints, create notification rules to alert you.

View File

@ -6,11 +6,11 @@ weight: 204
aliases:
- /v2.0/monitor-alert/notification-rules/delete/
menu:
influxdb_2_0:
v2_0:
parent: Manage notification rules
related:
- /influxdb/v2.0/monitor-alert/checks/
- /influxdb/v2.0/monitor-alert/notification-endpoints/
- /v2.0/monitor-alert/checks/
- /v2.0/monitor-alert/notification-endpoints/
---
## Delete a notification rule in the UI

View File

@ -6,11 +6,11 @@ weight: 203
aliases:
- /v2.0/monitor-alert/notification-rules/update/
menu:
influxdb_2_0:
v2_0:
parent: Manage notification rules
related:
- /influxdb/v2.0/monitor-alert/checks/
- /influxdb/v2.0/monitor-alert/notification-endpoints/
- /v2.0/monitor-alert/checks/
- /v2.0/monitor-alert/notification-endpoints/
---
## Add a label to notification rules

View File

@ -6,11 +6,11 @@ weight: 202
aliases:
- /v2.0/monitor-alert/notification-rules/view/
menu:
influxdb_2_0:
v2_0:
parent: Manage notification rules
related:
- /influxdb/v2.0/monitor-alert/checks/
- /influxdb/v2.0/monitor-alert/notification-endpoints/
- /v2.0/monitor-alert/checks/
- /v2.0/monitor-alert/notification-endpoints/
---
View notification rule details and statuses and notifications generated by notification rules in the InfluxDB user interface (UI).

View File

@ -5,10 +5,10 @@ description: Manage organizations in InfluxDB using the InfluxDB UI or the influ
aliases:
- /v2.0/organizations/
menu:
influxdb_2_0:
v2_0:
name: Manage organizations
weight: 10
influxdb/v2.0/tags: [organizations]
v2.0/tags: [organizations]
---
An **organization** is a workspace for a group of users.

View File

@ -3,13 +3,13 @@ title: Manage buckets
seotitle: Manage buckets in InfluxDB
description: Manage buckets in InfluxDB using the InfluxDB UI or the influx CLI.
menu:
influxdb_2_0:
v2_0:
name: Manage buckets
parent: Manage organizations
weight: 105
aliases:
- /v2.0/organizations/create-org/buckets/
influxdb/v2.0/tags: [buckets]
v2.0/tags: [buckets]
---
A **bucket** is a named location where time series data is stored.

View File

@ -3,7 +3,7 @@ title: Create a bucket
seotitle: Create a bucket in InfluxDB
description: Create buckets to store time series data in InfluxDB using the InfluxDB UI or the influx CLI.
menu:
influxdb_2_0:
v2_0:
name: Create a bucket
parent: Manage buckets
weight: 201

View File

@ -3,7 +3,7 @@ title: Delete a bucket
seotitle: Delete a bucket from InfluxDB
description: Delete a bucket from InfluxDB using the InfluxDB UI or the influx CLI
menu:
influxdb_2_0:
v2_0:
name: Delete a bucket
parent: Manage buckets
weight: 203

View File

@ -3,7 +3,7 @@ title: Update a bucket
seotitle: Update a bucket in InfluxDB
description: Update a bucket's name or retention policy in InfluxDB using the InfluxDB UI or the influx CLI.
menu:
influxdb_2_0:
v2_0:
name: Update a bucket
parent: Manage buckets
weight: 202

View File

@ -3,7 +3,7 @@ title: View buckets
seotitle: View buckets in InfluxDB
description: View a list of all the buckets for an organization in InfluxDB using the InfluxDB UI or the influx CLI.
menu:
influxdb_2_0:
v2_0:
name: View buckets
parent: Manage buckets
weight: 202

View File

@ -5,7 +5,7 @@ description: Create an organization in InfluxDB using the InfluxDB UI or the inf
aliases:
- /v2.0/organizations/create-org/
menu:
influxdb_2_0:
v2_0:
name: Create an organization
parent: Manage organizations
weight: 101

View File

@ -5,7 +5,7 @@ description: Delete an existing organization from InfluxDB using the InfluxDB UI
aliases:
- /v2.0/organizations/delete-org/
menu:
influxdb_2_0:
v2_0:
name: Delete an organization
parent: Manage organizations
weight: 104

View File

@ -3,13 +3,13 @@ title: Manage organization members
seotitle: Manage members of an organization in InfluxDB
description: Manage members of an organization in InfluxDB using the InfluxDB UI or CLI.
menu:
influxdb_2_0:
v2_0:
name: Manage members
parent: Manage organizations
weight: 106
aliases:
- /v2.0/organizations/create-org/members/
influxdb/v2.0/tags: [members]
v2.0/tags: [members]
---
A **member** is a user that belongs to an organization.

View File

@ -3,7 +3,7 @@ title: Add a member
seotitle: Add a member to an organization in InfluxDB
description: Add a member to an organization.
menu:
influxdb_2_0:
v2_0:
name: Add a member
parent: Manage members
weight: 201

View File

@ -3,7 +3,7 @@ title: Remove a member
seotitle: Remove a member from an organization in InfluxDB
description: Remove a member from an organization.
menu:
influxdb_2_0:
v2_0:
name: Remove a member
parent: Manage members
weight: 203

View File

@ -3,7 +3,7 @@ title: View members
seotitle: View members of an organization in InfluxDB
description: Review a list of members for an organization.
menu:
influxdb_2_0:
v2_0:
name: View members
parent: Manage members
weight: 202

View File

@ -5,7 +5,7 @@ description: Switch from one organization to another in the InfluxDB UI
aliases:
- /v2.0/organizations/switch-org/
menu:
influxdb_2_0:
v2_0:
name: Switch organizations
parent: Manage organizations
weight: 105

View File

@ -5,7 +5,7 @@ description: Update an organization's name and assets in InfluxDB using the Infl
aliases:
- /v2.0/organizations/update-org/
menu:
influxdb_2_0:
v2_0:
name: Update an organization
parent: Manage organizations
weight: 103

View File

@ -5,7 +5,7 @@ description: Review a list of organizations in InfluxDB using the InfluxDB UI or
aliases:
- /v2.0/organizations/view-org/
menu:
influxdb_2_0:
v2_0:
name: View organizations
parent: Manage organizations
weight: 102

View File

@ -5,12 +5,12 @@ description: >
InfluxDB's task engine runs scheduled Flux tasks that process and analyze data.
This collection of articles provides information about creating and managing InfluxDB tasks.
menu:
influxdb_2_0:
v2_0:
name: Process data
weight: 4
aliases:
- /v2.0/process-data/
influxdb/v2.0/tags: [tasks]
v2.0/tags: [tasks]
---
Process and analyze your data with tasks in the InfluxDB **task engine**. Use tasks (scheduled Flux queries)

View File

@ -4,9 +4,9 @@ seotitle: Common data processing tasks performed with with InfluxDB
description: >
InfluxDB Tasks process data on specified schedules.
This collection of articles walks through common use cases for InfluxDB tasks.
influxdb/v2.0/tags: [tasks]
v2.0/tags: [tasks]
menu:
influxdb_2_0:
v2_0:
name: Common tasks
parent: Process data
weight: 104

View File

@ -5,13 +5,13 @@ description: >
How to create a task that downsamples data much like continuous queries
in previous versions of InfluxDB.
menu:
influxdb_2_0:
v2_0:
name: Downsample data
parent: Common tasks
weight: 201
aliases:
- /v2.0/process-data/common-tasks/downsample-data/
influxdb/v2.0/tags: [tasks]
v2.0/tags: [tasks]
---
One of the most common use cases for InfluxDB tasks is downsampling data to reduce

View File

@ -7,9 +7,9 @@ description: >
aliases:
- /v2.0/process-data/write-a-task/
- /v2.0/process-data/get-started/
influxdb/v2.0/tags: [tasks]
v2.0/tags: [tasks]
menu:
influxdb_2_0:
v2_0:
name: Get started with tasks
parent: Process data
weight: 101

View File

@ -5,9 +5,9 @@ list_title: Manage tasks
description: >
InfluxDB provides options for creating, reading, updating, and deleting tasks
using both the `influx` CLI and the InfluxDB UI.
influxdb/v2.0/tags: [tasks]
v2.0/tags: [tasks]
menu:
influxdb_2_0:
v2_0:
name: Manage tasks
parent: Process data
weight: 102

View File

@ -4,14 +4,14 @@ seotitle: Create a task for processing data in InfluxDB
description: >
Create a data processing task in InfluxDB using the InfluxDB UI or the `influx` CLI.
menu:
influxdb_2_0:
v2_0:
name: Create a task
parent: Manage tasks
weight: 201
aliases:
- /v2.0/process-data/manage-tasks/create-task/
related:
- /influxdb/v2.0/reference/cli/influx/task/create
- /v2.0/reference/cli/influx/task/create
---
InfluxDB provides multiple ways to create tasks both in the InfluxDB user interface (UI)

View File

@ -4,14 +4,14 @@ seotitle: Delete a task for processing data in InfluxDB
description: >
Delete a task from InfluxDB using the InfluxDB UI or the `influx` CLI.
menu:
influxdb_2_0:
v2_0:
name: Delete a task
parent: Manage tasks
weight: 206
aliases:
- /v2.0/process-data/manage-tasks/delete-task/
related:
- /influxdb/v2.0/reference/cli/influx/task/delete
- /v2.0/reference/cli/influx/task/delete
---
## Delete a task in the InfluxDB UI

View File

@ -3,7 +3,7 @@ title: Export a task
seotitle: Export an InfluxDB task
description: Export a data processing task from InfluxDB using the InfluxDB UI.
menu:
influxdb_2_0:
v2_0:
name: Export a task
parent: Manage tasks
weight: 205

View File

@ -4,15 +4,15 @@ seotitle: Run an InfluxDB task
description: >
Run a data processing task using the InfluxDB UI or the `influx` CLI.
menu:
influxdb_2_0:
v2_0:
name: Run a task
parent: Manage tasks
weight: 203
aliases:
- /v2.0/process-data/manage-tasks/run-task/
related:
- /influxdb/v2.0/reference/cli/influx/task/run
- /influxdb/v2.0/reference/cli/influx/task/retry
- /v2.0/reference/cli/influx/task/run
- /v2.0/reference/cli/influx/task/retry
---
InfluxDB data processing tasks generally run in defined intervals or at a specific time,

View File

@ -3,14 +3,14 @@ title: View task run history and logs
description: >
View task run histories and logs using the InfluxDB UI or the `influx` CLI.
menu:
influxdb_2_0:
v2_0:
name: View run history
parent: Manage tasks
weight: 203
aliases:
- /v2.0/process-data/manage-tasks/task-run-history/
related:
- /influxdb/v2.0/reference/cli/influx/task/run/find
- /v2.0/reference/cli/influx/task/run/find
---
When an InfluxDB task runs, a "run" record is created in the task's history.

View File

@ -4,14 +4,14 @@ seotitle: Update a task for processing data in InfluxDB
description: >
Update a data processing task in InfluxDB using the InfluxDB UI or the `influx` CLI.
menu:
influxdb_2_0:
v2_0:
name: Update a task
parent: Manage tasks
weight: 204
aliases:
- /v2.0/process-data/manage-tasks/update-task/
related:
- /influxdb/v2.0/reference/cli/influx/task/update
- /v2.0/reference/cli/influx/task/update
---
## Update a task in the InfluxDB UI

View File

@ -4,14 +4,14 @@ seotitle: View created tasks that process data in InfluxDB
description: >
View existing data processing tasks using the InfluxDB UI or the `influx` CLI.
menu:
influxdb_2_0:
v2_0:
name: View tasks
parent: Manage tasks
weight: 202
aliases:
- /v2.0/process-data/manage-tasks/view-tasks/
related:
- /influxdb/v2.0/reference/cli/influx/task/list
- /v2.0/reference/cli/influx/task/list
---
## View tasks in the InfluxDB UI

View File

@ -5,13 +5,13 @@ description: >
Task options define specific information about a task such as its name,
the schedule on which it runs, execution delays, and others.
menu:
influxdb_2_0:
v2_0:
name: Task options
parent: Process data
weight: 105
aliases:
- /v2.0/process-data/task-options/
influxdb/v2.0/tags: [tasks, flux]
v2.0/tags: [tasks, flux]
---
Task options define specific information about a task.

View File

@ -5,12 +5,12 @@ description: >
Learn to query data stored in InfluxDB using Flux and tools such as the InfluxDB
user interface and the 'influx' command line interface.
menu:
influxdb_2_0:
v2_0:
name: Query data
weight: 3
aliases:
- /v2.0/query-data/
influxdb/v2.0/tags: [query, flux]
v2.0/tags: [query, flux]
---
Learn to query data stored in InfluxDB using Flux and tools such as the InfluxDB

View File

@ -6,10 +6,10 @@ weight: 103
aliases:
- /v2.0/query-data/execute-queries/
menu:
influxdb_2_0:
v2_0:
name: Execute queries
parent: Query data
influxdb/v2.0/tags: [query]
v2.0/tags: [query]
---
There are multiple ways to execute queries with InfluxDB.
@ -23,7 +23,7 @@ This guide covers the different options:
## Data Explorer
Queries can be built, executed, and visualized in InfluxDB UI's Data Explorer.
![Data Explorer with Flux](/img/influxdb/2-0-data-explorer.png)
![Data Explorer with Flux](/img/data-explorer-beta-8.png)
## Influx REPL
The [`influx repl` command](/v2.0/reference/cli/influx/repl) starts an interactive

View File

@ -2,9 +2,9 @@
title: Query data with Flux
description: Guides that walk through both common and complex queries and use cases for Flux.
weight: 102
influxdb/v2.0/tags: [flux, query]
v2.0/tags: [flux, query]
menu:
influxdb_2_0:
v2_0:
name: Query with Flux
parent: Query data
alias:

View File

@ -6,7 +6,7 @@ description: >
and the [`map()` function](/v2.0/reference/flux/stdlib/built-in/transformations/map/)
to align operand values into rows and calculate a percentage.
menu:
influxdb_2_0:
v2_0:
name: Calculate percentages
parent: Query with Flux
weight: 209
@ -14,7 +14,7 @@ aliases:
- /v2.0/query-data/guides/calculate-percentages/
- /v2.0/query-data/flux/calculate-percentages/
related:
- /influxdb/v2.0/query-data/flux/mathematic-operations
- /v2.0/query-data/flux/mathematic-operations
- /v2.0/reference/flux/stdlib/built-in/transformations/map
- /v2.0/reference/flux/stdlib/built-in/transformations/pivot
- /v2.0/reference/flux/stdlib/built-in/transformations/join

View File

@ -5,9 +5,9 @@ list_title: Conditional logic
description: >
This guide describes how to use Flux conditional expressions, such as `if`,
`else`, and `then`, to query and transform data. **Flux evaluates statements from left to right and stops evaluating once a condition matches.**
influxdb/v2.0/tags: [conditionals, flux]
v2.0/tags: [conditionals, flux]
menu:
influxdb_2_0:
v2_0:
name: Conditional logic
parent: Query with Flux
weight: 220
@ -15,7 +15,7 @@ aliases:
- /v2.0/query-data/guides/conditional-logic/
- /v2.0/query-data/flux/conditional-logic/
related:
- /influxdb/v2.0/query-data/flux/query-fields/
- /v2.0/query-data/flux/query-fields/
- /v2.0/reference/flux/stdlib/built-in/transformations/filter/
- /v2.0/reference/flux/stdlib/built-in/transformations/map/
- /v2.0/reference/flux/stdlib/built-in/transformations/aggregates/reduce/

View File

@ -6,10 +6,10 @@ description: >
Use the `cumulativeSum()` function to calculate a running total of values.
weight: 210
menu:
influxdb_2_0:
v2_0:
parent: Query with Flux
name: Cumulative sum
influxdb/v2.0/tags: [query, cumulative sum]
v2.0/tags: [query, cumulative sum]
aliases:
- /v2.0/query-data/flux/cumulativesum/
related:

View File

@ -2,9 +2,9 @@
title: Create custom Flux functions
description: Create your own custom Flux functions to transform and manipulate data.
list_title: Custom functions
influxdb/v2.0/tags: [functions, custom, flux]
v2.0/tags: [functions, custom, flux]
menu:
influxdb_2_0:
v2_0:
name: Custom functions
parent: Query with Flux
weight: 220

View File

@ -1,9 +1,9 @@
---
title: Create custom aggregate functions
description: Create your own custom aggregate functions in Flux using the `reduce()` function.
influxdb/v2.0/tags: [functions, custom, flux, aggregates]
v2.0/tags: [functions, custom, flux, aggregates]
menu:
influxdb_2_0:
v2_0:
name: Custom aggregate functions
parent: Custom functions
weight: 301

View File

@ -5,9 +5,9 @@ list_title: Exists
description: >
Use the Flux `exists` operator to check if a record contains a key or if that
key's value is `null`.
influxdb/v2.0/tags: [exists]
v2.0/tags: [exists]
menu:
influxdb_2_0:
v2_0:
name: Exists
parent: Query with Flux
weight: 220
@ -15,7 +15,7 @@ aliases:
- /v2.0/query-data/guides/exists/
- /v2.0/query-data/flux/exists/
related:
- /influxdb/v2.0/query-data/flux/query-fields/
- /v2.0/query-data/flux/query-fields/
- /v2.0/reference/flux/stdlib/built-in/transformations/filter/
list_code_example: |
##### Filter null values

View File

@ -4,9 +4,9 @@ list_title: Explore your schema
description: >
Flux provides functions that let you explore the structure and schema of your
data stored in InfluxDB.
influxdb/v2.0/tags: [schema]
v2.0/tags: [schema]
menu:
influxdb_2_0:
v2_0:
name: Explore your schema
parent: Query with Flux
weight: 206

View File

@ -9,10 +9,10 @@ weight: 210
aliases:
- /v2.0/query-data/flux/fill/
menu:
influxdb_2_0:
v2_0:
parent: Query with Flux
name: Fill
influxdb/v2.0/tags: [query, fill]
v2.0/tags: [query, fill]
related:
- /v2.0/reference/flux/stdlib/built-in/transformations/fill/
list_query_example: fill_null

View File

@ -10,10 +10,10 @@ weight: 210
aliases:
- /v2.0/query-data/flux/first-last/
menu:
influxdb_2_0:
v2_0:
parent: Query with Flux
name: First & last
influxdb/v2.0/tags: [query]
v2.0/tags: [query]
related:
- /v2.0/reference/flux/stdlib/built-in/transformations/selectors/first/
- /v2.0/reference/flux/stdlib/built-in/transformations/selectors/last/

View File

@ -4,7 +4,7 @@ list_title: Geo-temporal data
description: >
Use the Flux Geo package to filter geo-temporal data and group by geographic location or track.
menu:
influxdb_2_0:
v2_0:
name: Geo-temporal data
parent: Query with Flux
weight: 220

View File

@ -3,7 +3,7 @@ title: Filter geo-temporal data by region
description: >
Use the `geo.filterRows` function to filter geo-temporal data by box-shaped, circular, or polygonal geographic regions.
menu:
influxdb_2_0:
v2_0:
name: Filter by region
parent: Geo-temporal data
weight: 302

View File

@ -4,7 +4,7 @@ description: >
Use the `geo.groupByArea()` to group geo-temporal data by area and `geo.asTracks()`
to group data into tracks or routes.
menu:
influxdb_2_0:
v2_0:
parent: Geo-temporal data
weight: 302
aliases:

View File

@ -4,7 +4,7 @@ description: >
Functions in the Flux Geo package require **lat** and **lon** fields and an **s2_cell_id** tag.
Rename latitude and longitude fields and generate S2 cell ID tokens.
menu:
influxdb_2_0:
v2_0:
name: Shape geo-temporal data
parent: Geo-temporal data
weight: 301

View File

@ -4,9 +4,9 @@ list_title: Group
description: >
Use the [`group()` function](/v2.0/reference/flux/stdlib/built-in/transformations/group)
to group data with common values in specific columns.
influxdb/v2.0/tags: [group]
v2.0/tags: [group]
menu:
influxdb_2_0:
v2_0:
name: Group
parent: Query with Flux
weight: 202
@ -164,7 +164,7 @@ Table: keys: [_start, _stop, _field, _measurement, cpu]
**Note that the group key is output with each table: `Table: keys: <group-key>`.**
![Group example data set](/img/flux/grouping-data-set.png)
![Group example data set](/img/grouping-data-set.png)
### Group by CPU
Group the `dataSet` stream by the `cpu` column.
@ -253,7 +253,7 @@ Table: keys: [cpu]
The visualization remains the same.
![Group by CPU](/img/flux/grouping-data-set.png)
![Group by CPU](/img/grouping-data-set.png)
### Group by time
Grouping data by the `_time` column is a good illustration of how grouping changes the structure of your data.
@ -378,7 +378,7 @@ Table: keys: [_time]
Because each timestamp is structured as a separate table, when visualized, all
points that share the same timestamp appear connected.
![Group by time](/img/flux/grouping-by-time.png)
![Group by time](/img/grouping-by-time.png)
{{% note %}}
With some further processing, you could calculate the average CPU usage across all CPUs per point
@ -670,7 +670,7 @@ Table: keys: [_time, cpu]
When visualized, tables appear as individual, unconnected points.
![Group by CPU and time](/img/flux/grouping-by-cpu-time.png)
![Group by CPU and time](/img/grouping-by-cpu-time.png)
Grouping by `cpu` and `_time` is a good illustration of how grouping works.

View File

@ -4,9 +4,9 @@ list_title: Histograms
description: >
Use the [`histogram()` function](/v2.0/reference/flux/stdlib/built-in/transformations/histogram/)
to create cumulative histograms with Flux.
influxdb/v2.0/tags: [histogram]
v2.0/tags: [histogram]
menu:
influxdb_2_0:
v2_0:
name: Histograms
parent: Query with Flux
weight: 210
@ -76,7 +76,7 @@ logarithmicBins(start: 1.0, factor: 2.0, count: 10, infinity: true)
The [Histogram visualization type](/v2.0/visualize-data/visualization-types/histogram/)
automatically converts query results into a binned and segmented histogram.
{{< img-hd src="/img/influxdb/2-0-visualizations-histogram-example.png" alt="Histogram visualization" />}}
{{< img-hd src="/img/2-0-visualizations-histogram-example.png" alt="Histogram visualization" />}}
Use the [Histogram visualization controls](/v2.0/visualize-data/visualization-types/histogram/#histogram-controls)
to specify the number of bins and define groups in bins.
@ -190,4 +190,4 @@ from(bucket: "example-bucket")
In the Histogram visualization options, select `_time` as the **X Column**
and `severity` as the **Group By** option:
{{< img-hd src="/img/influxdb/2-0-visualizations-histogram-errors.png" alt="Logs by severity histogram" />}}
{{< img-hd src="/img/2-0-visualizations-histogram-errors.png" alt="Logs by severity histogram" />}}

View File

@ -11,10 +11,10 @@ weight: 210
aliases:
- /v2.0/query-data/flux/increase/
menu:
influxdb_2_0:
v2_0:
parent: Query with Flux
name: Increase
influxdb/v2.0/tags: [query, increase, counters]
v2.0/tags: [query, increase, counters]
related:
- /v2.0/reference/flux/stdlib/built-in/transformations/aggregates/increase/
list_query_example: increase

View File

@ -3,9 +3,9 @@ title: Join data with Flux
seotitle: Join data in InfluxDB with Flux
list_title: Join
description: This guide walks through joining data with Flux and outlines how it shapes your data in the process.
influxdb/v2.0/tags: [join, flux]
v2.0/tags: [join, flux]
menu:
influxdb_2_0:
v2_0:
name: Join
parent: Query with Flux
weight: 210

View File

@ -4,7 +4,7 @@ list_title: Manipulate timestamps
description: >
Use Flux to process and manipulate timestamps.
menu:
influxdb_2_0:
v2_0:
name: Manipulate timestamps
parent: Query with Flux
weight: 220

View File

@ -5,9 +5,9 @@ list_title: Transform data with math
description: >
Use the [`map()` function](/v2.0/reference/flux/stdlib/built-in/transformations/map)
to remap column values and apply mathematic operations.
influxdb/v2.0/tags: [math, flux]
v2.0/tags: [math, flux]
menu:
influxdb_2_0:
v2_0:
name: Transform data with math
parent: Query with Flux
weight: 208
@ -19,7 +19,7 @@ related:
- /v2.0/reference/flux/stdlib/built-in/transformations/aggregates/reduce/
- /v2.0/reference/flux/language/operators/
- /v2.0/reference/flux/stdlib/built-in/transformations/type-conversions/
- /influxdb/v2.0/query-data/flux/calculate-percentages/
- /v2.0/query-data/flux/calculate-percentages/
list_query_example: map_math
---

View File

@ -9,12 +9,12 @@ weight: 210
aliases:
- /v2.0/query-data/flux/median/
menu:
influxdb_2_0:
v2_0:
parent: Query with Flux
name: Median
influxdb/v2.0/tags: [query, median]
v2.0/tags: [query, median]
related:
- /influxdb/v2.0/query-data/flux/percentile-quantile/
- /v2.0/query-data/flux/percentile-quantile/
- /v2.0/reference/flux/stdlib/built-in/transformations/aggregates/median/
- /v2.0/reference/flux/stdlib/built-in/transformations/aggregates/quantile/
list_query_example: median

View File

@ -2,9 +2,9 @@
title: Monitor states
seotitle: Monitor states and state changes in your events and metrics with Flux.
description: Flux provides several functions to help monitor states and state changes in your data.
influxdb/v2.0/tags: [states, monitor, flux]
v2.0/tags: [states, monitor, flux]
menu:
influxdb_2_0:
v2_0:
name: Monitor states
parent: Query with Flux
weight: 220

View File

@ -10,10 +10,10 @@ weight: 210
aliases:
- /v2.0/query-data/flux/moving-average/
menu:
influxdb_2_0:
v2_0:
parent: Query with Flux
name: Moving Average
influxdb/v2.0/tags: [query, moving average]
v2.0/tags: [query, moving average]
related:
- /v2.0/reference/flux/stdlib/built-in/transformations/movingaverage/
- /v2.0/reference/flux/stdlib/built-in/transformations/aggregates/timedmovingaverage/

View File

@ -9,12 +9,12 @@ weight: 210
aliases:
- /v2.0/query-data/flux/percentile-quantile/
menu:
influxdb_2_0:
v2_0:
parent: Query with Flux
name: Percentile & quantile
influxdb/v2.0/tags: [query, percentile, quantile]
v2.0/tags: [query, percentile, quantile]
related:
- /influxdb/v2.0/query-data/flux/query-median/
- /v2.0/query-data/flux/query-median/
- /v2.0/reference/flux/stdlib/built-in/transformations/aggregates/quantile/
list_query_example: quantile
---

View File

@ -9,13 +9,13 @@ weight: 201
aliases:
- /v2.0/query-data/flux/query-fields/
menu:
influxdb_2_0:
v2_0:
parent: Query with Flux
influxdb/v2.0/tags: [query, select, where]
v2.0/tags: [query, select, where]
related:
- /v2.0/reference/flux/stdlib/built-in/transformations/filter/
- /influxdb/v2.0/query-data/flux/conditional-logic/
- /influxdb/v2.0/query-data/flux/regular-expressions/
- /v2.0/query-data/flux/conditional-logic/
- /v2.0/query-data/flux/regular-expressions/
list_code_example: |
```js
from(bucket: "example-bucket")

View File

@ -13,10 +13,10 @@ weight: 210
aliases:
- /v2.0/query-data/flux/rate/
menu:
influxdb_2_0:
v2_0:
parent: Query with Flux
name: Rate
influxdb/v2.0/tags: [query, rate]
v2.0/tags: [query, rate]
related:
- /v2.0/reference/flux/stdlib/built-in/transformations/derivative/
- /v2.0/reference/flux/stdlib/experimental/aggregate/rate/

View File

@ -2,9 +2,9 @@
title: Use regular expressions in Flux
list_title: Regular expressions
description: This guide walks through using regular expressions in evaluation logic in Flux functions.
influxdb/v2.0/tags: [regex]
v2.0/tags: [regex]
menu:
influxdb_2_0:
v2_0:
name: Regular expressions
parent: Query with Flux
weight: 220
@ -12,7 +12,7 @@ aliases:
- /v2.0/query-data/guides/regular-expressions/
- /v2.0/query-data/flux/regular-expressions/
related:
- /influxdb/v2.0/query-data/flux/query-fields/
- /v2.0/query-data/flux/query-fields/
- /v2.0/reference/flux/stdlib/regexp/
list_query_example: regular_expressions
---

View File

@ -5,11 +5,11 @@ description: >
Use Flux stream and table functions to extract scalar values from Flux query output.
This lets you, for example, dynamically set variables using query results.
menu:
influxdb_2_0:
v2_0:
name: Extract scalar values
parent: Query with Flux
weight: 220
influxdb/v2.0/tags: [scalar]
v2.0/tags: [scalar]
related:
- /v2.0/reference/flux/stdlib/built-in/transformations/stream-table/
aliases:

View File

@ -7,9 +7,9 @@ description: >
to order records within each table by specific columns and the
[`limit()` function](/v2.0/reference/flux/stdlib/built-in/transformations/limit)
to limit the number of records in output tables to a fixed number, `n`.
influxdb/v2.0/tags: [sort, limit]
v2.0/tags: [sort, limit]
menu:
influxdb_2_0:
v2_0:
name: Sort and limit
parent: Query with Flux
weight: 203

View File

@ -6,9 +6,9 @@ description: >
The Flux `sql` package provides functions for working with SQL data sources.
Use `sql.from()` to query SQL databases like PostgreSQL, MySQL, Snowflake,
SQLite, Microsoft SQL Server, and Amazon Athena.
influxdb/v2.0/tags: [query, flux, sql]
v2.0/tags: [query, flux, sql]
menu:
influxdb_2_0:
v2_0:
parent: Query with Flux
list_title: SQL data
weight: 220
@ -184,7 +184,7 @@ sql.from(
Use the variable to manipulate queries in your dashboards.
{{< img-hd src="/img/influxdb/2-0-sql-dashboard-variable.png" alt="Dashboard variable from SQL query results" />}}
{{< img-hd src="/img/2-0-sql-dashboard-variable.png" alt="Dashboard variable from SQL query results" />}}
---

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