diff --git a/.github/ISSUE_TEMPLATE/new-feature.md b/.github/ISSUE_TEMPLATE/new-feature.md
index 299510091..fd89b149e 100644
--- a/.github/ISSUE_TEMPLATE/new-feature.md
+++ b/.github/ISSUE_TEMPLATE/new-feature.md
@@ -6,6 +6,7 @@ labels: ''
 assignees: ''
 ---
 
+**ETA:** _Provide an estimated completion date for the feature (if available)_
 **PR:** _Provide PR URL(s) for this feature (if available)_
 
 _Describe the new feature here._
diff --git a/api-docs/README.md b/api-docs/README.md
index ecd1d2b56..fb1095529 100755
--- a/api-docs/README.md
+++ b/api-docs/README.md
@@ -1,43 +1,85 @@
-## Generate InfluxDB API docs
-InfluxDB uses [Redoc](https://github.com/Redocly/redoc/),
+# How to generate InfluxDB API docs
+
+InfluxData uses [Redoc](https://github.com/Redocly/redoc/),
 [redoc-cli](https://github.com/Redocly/redoc/blob/master/cli/README.md),
 and Redocly's [OpenApi CLI](https://redoc.ly/docs/cli/) to generate
-API documentation from the InfluxDB openapi contracts.
+API documentation from the [InfluxDB OpenAPI (aka Swagger) contracts](https://github.com/influxdata/openapi).
 
-To minimize repo size, the generated API documentation HTML is gitignored, therefore
-not committed directly to the docs repo.
-The InfluxDB docs deployment process uses swagger files in the `api-docs` directory
-to generate version-specific API documentation.
+To minimize the size of the `docs-v2` repository, the generated API documentation HTML is gitignored, therefore
+not committed to the docs repo.
+The InfluxDB docs deployment process uses OpenAPI specification files in the `api-docs` directory
+to generate version-specific (Cloud, OSS v2.1, OSS v2.0, etc.) API documentation.
 
-### Versioned swagger files
-The structure versions swagger files using the following pattern:
+## How we version OpenAPI contracts
 
-```
+The `api-docs` directory structure versions OpenAPI files using the following pattern:
+
+```md
 api-docs/
   ├── v2.0/
   │     └── ref.yml
+  │     └── swaggerV1Compat.yml
   ├── v2.1/
   │     └── ref.yml
+  │     └── swaggerV1Compat.yml
   ├── v2.2/
   │     └── ref.yml
+  │     └── swaggerV1Compat.yml
   └── etc...
 ```
 
-### Configure OpenAPI CLI linting and bundling
-`.redoc.yaml` sets linting and bundling options for `openapi` CLI.
-`./openapi/plugins` contains custom OpenAPI CLI plugins composed of *rules* (for linting) and *decorators* (for bundle customization).
+### InfluxDB Cloud version
 
-### Custom content
-`./openapi/content` contains custom OAS (OpenAPI Spec) content in YAML files. The content structure and Markdown must be valid OAS.
+Because InfluxDB Cloud releases are frequent, we make no effort to version the
+Cloud API spec. We regenerate API reference docs from `influxdata/openapi`
+**master** as features are released.
 
-`./openapi/plugins` use `./openapi/plugins/decorators` to apply the content to the contracts.
-`.yml` files in `./openapi/content/` set content for sections (nodes) in the contract. To update the content for those nodes, you only need to update the YAML files.
+### InfluxDB OSS version
 
-To add new YAML files for other nodes in the openapi contracts, configure the new content YAML file in `./openapi/content/content.js`. Then, write a decorator module for the node and configure the decorator in the plugin, e.g. `./openapi/plugins/docs-plugin.js`. See the [complete list of OAS v3.0 nodes](https://github.com/Redocly/openapi-cli/blob/master/packages/core/src/types/oas3.ts#L529).
+ Given that
+ `influxdata/openapi` **master** may contain OSS spec changes not implemented
+ in the current OSS release, we (Docs team) maintain a release branch, `influxdata/openapi`
+**docs-release/influxdb-oss**, used to generate OSS reference docs.
 
-`openapi` CLI requires that modules use CommonJS `require` syntax for imports. 
+To update this branch to a new OSS release, (re)base on the commit or tag for the [latest release of InfluxDB OSS](#how-to-find-the-api-spec-used-by-an-influxdb-oss-version).
+
+```sh
+git checkout docs-release/influxdb-oss
+git rebase -i influxdb-oss-v2.2.0
+git push -f origin docs-release/influxdb-oss
+```
+
+To update this branch with documentation changes between OSS releases, cherry-pick your documentation commits into the release branch.
+
+```sh
+git checkout docs-release/influxdb-oss
+git cherry-pick <commit hashes>
+git push -f origin docs-release/influxdb-oss
+```
+
+### How to find the API spec used by an InfluxDB OSS version
+
+`influxdata/openapi` does not version the InfluxData API.
+To find the `influxdata/openapi` commit SHA used in a specific version of InfluxDB OSS,
+see `/scripts/fetch-swagger.sh` in `influxdata/influxdb`--for example,
+for the `influxdata/openapi` commit used in OSS v2.2.0, see https://github.com/influxdata/influxdb/blob/v2.2.0/scripts/fetch-swagger.sh#L13=.
+For convenience, we tag `influxdata/influxdb` (OSS) release points in `influxdata/openapi` as
+`influxdb-oss-v[OSS_VERSION]`. See <https://github.com/influxdata/openapi/tags>.
+
+## How to fetch and process influxdata/openapi contracts
+
+Update the contracts in `api-docs` to the latest from `influxdata/openapi`.
+
+```sh
+# In your terminal, go to the `docs-v2/api-docs` directory:
+cd api-docs
+
+# Fetch the contracts and run @redocly/openapi-cli to customize and bundle them.
+sh getswagger.sh oss; sh getswagger.sh cloud
+```
+
+## How to generate API docs locally
 
-### Generate API docs locally
 Because the API documentation HTML is gitignored, you must manually generate it
 to view the API docs locally.
 
@@ -50,11 +92,71 @@ npx --version
 
 If `npx` returns errors, [download](https://nodejs.org/en/) and run a recent version of the Node.js installer for your OS.
 
-In your terminal, from the root of the docs repo, run:
-
 ```sh
+# In your terminal, go to the `docs-v2/api-docs` directory:
 cd api-docs
 
-# Generate the API docs
+# Generate the API docs with Redocly
 sh generate-api-docs.sh
 ```
+
+## How to use custom OpenAPI spec processing
+
+Generally, you should manage API content in `influxdata/openapi`.
+In some cases, however, you may want custom processing (e.g. collecting all Tags)
+or additional content (e.g. describing the reference documentation)
+specifically for the docs.
+
+When you run `getswagger.sh`, it executes `@redocly/openapi-cli` and the plugins listed in `.redocly.yaml`.
+[`./openapi/plugins`](./openapi/plugins) use
+[`./openapi/plugins/decorators`](./openapi/plugins/decorators) to apply custom
+processing to OpenAPI specs.
+
+`.yml` files in [`./openapi/content`](./openapi/content) set content for sections (nodes) in the contract.
+To update the content for those nodes, you only need to update the YAML files.
+To add new YAML files for other nodes in the contracts,
+configure the new content YAML file in [`./openapi/content/content.js`](./openapi/content/content.js).
+The content structure and Markdown must be valid OAS.
+
+Then, you'll need to write or update a decorator module for the node and configure the decorator in the plugin,
+e.g. [`./openapi/plugins/docs-plugin.js`](`./openapi/plugins/docs-plugin.js).
+See the [complete list of OAS v3.0 nodes](https://github.com/Redocly/openapi-cli/blob/master/packages/core/src/types/oas3.ts#L529).
+
+`@redocly/openapi-cli` requires that modules use CommonJS `require` syntax for imports.
+
+### How to add tag content or describe a group of paths
+
+In API reference docs, we use OpenAPI `tags` elements for navigation and the
+`x-traitTag` vendor extension to define custom content.
+
+| Example                                                                                                | OpenAPI field                                         |                                            |
+|:-------------------------------------------------------------------------------------------------------|-------------------------------------------------------|--------------------------------------------|
+| [Add supplementary documentation](https://docs.influxdata.com/influxdb/cloud/api/#tag/Quick-start)     | `tags: [ { name: 'Quick start', x-traitTag: true } ]` | [Source](https://github.com/influxdata/openapi/master/src/cloud/tags.yml) |
+| [Group and describe related paths](https://docs.influxdata.com/influxdb/cloud/api/#tag/Authorizations) | `tags: [ { name: 'Buckets', description: '...' } ]`   | [Source](https://github.com/influxdata/openapi/master/src/cloud/tags-groups.yml)) |
+
+## How to test your spec or API reference changes
+
+You can use `getswagger.sh` to fetch contracts from any URL.
+For example, if you've made changes to spec files and generated new contracts in your local `openapi` repo, run `getswagger.sh` to fetch and process them.
+
+To fetch contracts from your own `openapi` repo, pass the
+`-b` `base_url` option and the full path to your `openapi` directory.
+
+```sh
+# Use the file:/// protocol to pass your openapi directory.
+sh getswagger.sh oss -b file:///Users/me/github/openapi
+```
+
+After you fetch them, run the linter or generate HTML to test your changes before you commit them to `influxdata/openapi`.
+By default, `getswagger.sh` doesn't run the linter when bundling
+the specs.
+Manually run the [linter rules](https://redoc.ly/docs/cli/resources/built-in-rules/) to get a report of errors and warnings.
+
+```sh
+npx @redocly/openapi-cli lint v2.1/ref.yml
+```
+
+### Configure OpenAPI CLI linting and bundling
+
+The `.redoc.yaml` configuration file sets options for the `@redocly/openapi-cli` [`lint`](https://redoc.ly/docs/cli/commands/lint/) and [`bundle`](https://redoc.ly/docs/cli/commands/bundle/) commands.
+`./openapi/plugins` contains custom InfluxData Docs plugins composed of *rules* (for validating and linting) and *decorators* (for customizing). For more configuration options, see `@redocly/openapi-cli` [configuration file documentation](https://redoc.ly/docs/cli/configuration/configuration-file/).
diff --git a/api-docs/cloud/ref.yml b/api-docs/cloud/ref.yml
index eaa8b7811..76a133627 100644
--- a/api-docs/cloud/ref.yml
+++ b/api-docs/cloud/ref.yml
@@ -2,8 +2,8 @@ components:
   parameters:
     After:
       description: >
-        The last resource ID from which to seek from (but not including). This
-        is to be used instead of `offset`.
+        Resource ID to seek from. Results are not inclusive of this ID. Use
+        `after` instead of `offset`.
       in: query
       name: after
       required: false
@@ -169,8 +169,8 @@ components:
         status:
           default: active
           description: >-
-            If inactive the token is inactive and requests using the token will
-            be rejected.
+            Status of the token. If `inactive`, requests using the token will be
+            rejected.
           enum:
             - active
             - inactive
@@ -197,10 +197,10 @@ components:
         - 'y'
       type: object
     Axis:
-      description: The description of a particular axis for a visualization.
+      description: Axis used in a visualization.
       properties:
         base:
-          description: Base represents the radix for formatting axis values.
+          description: Radix for formatting axis values.
           enum:
             - ''
             - '2'
@@ -208,23 +208,23 @@ components:
           type: string
         bounds:
           description: >-
-            The extents of an axis in the form [lower, upper]. Clients determine
-            whether bounds are to be inclusive or exclusive of their limits
+            The extents of the axis in the form [lower, upper]. Clients
+            determine whether bounds are inclusive or exclusive of their limits.
           items:
             type: string
           maxItems: 2
           minItems: 0
           type: array
         label:
-          description: Label is a description of this Axis
+          description: Description of the axis.
           type: string
         prefix:
-          description: Prefix represents a label prefix for formatting axis values.
+          description: Label prefix for formatting axis values.
           type: string
         scale:
           $ref: '#/components/schemas/AxisScale'
         suffix:
-          description: Suffix represents a label suffix for formatting axis values.
+          description: Label suffix for formatting axis values.
           type: string
       type: object
     AxisScale:
@@ -391,22 +391,22 @@ components:
           properties:
             labels:
               $ref: '#/components/schemas/Link'
-              description: URL to retrieve labels for this bucket
+              description: URL to retrieve labels for this bucket.
             members:
               $ref: '#/components/schemas/Link'
-              description: URL to retrieve members that can read this bucket
+              description: URL to retrieve members that can read this bucket.
             org:
               $ref: '#/components/schemas/Link'
-              description: URL to retrieve parent organization for this bucket
+              description: URL to retrieve parent organization for this bucket.
             owners:
               $ref: '#/components/schemas/Link'
               description: URL to retrieve owners that can read and write to this bucket.
             self:
               $ref: '#/components/schemas/Link'
-              description: URL for this bucket
+              description: URL for this bucket.
             write:
               $ref: '#/components/schemas/Link'
-              description: URL to write line protocol for this bucket
+              description: URL to write line protocol to this bucket.
           readOnly: true
           type: object
         name:
@@ -596,7 +596,10 @@ components:
           readOnly: true
           type: string
         latestCompleted:
-          description: Timestamp of latest scheduled, completed run, RFC3339.
+          description: >-
+            Timestamp (in RFC3339 date/time
+            format](https://datatracker.ietf.org/doc/html/rfc3339)) of the
+            latest scheduled and completed run.
           format: date-time
           readOnly: true
           type: string
@@ -828,24 +831,24 @@ components:
     DBRP:
       properties:
         bucketID:
-          description: the bucket ID used as target for the translation.
+          description: ID of the bucket used as the target for the translation.
           type: string
         database:
           description: InfluxDB v1 database
           type: string
         default:
           description: >-
-            Specify if this mapping represents the default retention policy for
-            the database specificed.
+            Mapping represents the default retention policy for the database
+            specified.
           type: boolean
         id:
-          description: the mapping identifier
+          description: ID of the DBRP mapping.
           readOnly: true
           type: string
         links:
           $ref: '#/components/schemas/Links'
         orgID:
-          description: the organization ID that owns this mapping.
+          description: ID of the organization that owns this mapping.
           type: string
         retention_policy:
           description: InfluxDB v1 retention policy
@@ -861,21 +864,21 @@ components:
     DBRPCreate:
       properties:
         bucketID:
-          description: the bucket ID used as target for the translation.
+          description: ID of the bucket used as the target for the translation.
           type: string
         database:
           description: InfluxDB v1 database
           type: string
         default:
           description: >-
-            Specify if this mapping represents the default retention policy for
-            the database specificed.
+            Mapping represents the default retention policy for the database
+            specified.
           type: boolean
         org:
-          description: the organization that owns this mapping.
+          description: Name of the organization that owns this mapping.
           type: string
         orgID:
-          description: the organization ID that owns this mapping.
+          description: ID of the organization that owns this mapping.
           type: string
         retention_policy:
           description: InfluxDB v1 retention policy
@@ -1134,80 +1137,6 @@ components:
         - start
         - stop
       type: object
-    DemoDataBucket:
-      properties:
-        createdAt:
-          format: date-time
-          readOnly: true
-          type: string
-        description:
-          type: string
-        id:
-          readOnly: true
-          type: string
-        labels:
-          $ref: '#/components/schemas/Labels'
-        links:
-          example:
-            labels: /api/v2/buckets/1/labels
-            members: /api/v2/buckets/1/members
-            org: /api/v2/orgs/2
-            owners: /api/v2/buckets/1/owners
-            self: /api/v2/buckets/1
-            write: /api/v2/write?org=2&bucket=1
-          properties:
-            labels:
-              $ref: '#/components/schemas/Link'
-              description: URL to retrieve labels for this bucket
-            members:
-              $ref: '#/components/schemas/Link'
-              description: URL to retrieve members that can read this bucket
-            org:
-              $ref: '#/components/schemas/Link'
-              description: URL to retrieve parent organization for this bucket
-            owners:
-              $ref: '#/components/schemas/Link'
-              description: URL to retrieve owners that can read and write to this bucket.
-            self:
-              $ref: '#/components/schemas/Link'
-              description: URL for this bucket
-            write:
-              $ref: '#/components/schemas/Link'
-              description: URL to write line protocol for this bucket
-          readOnly: true
-          type: object
-        name:
-          type: string
-        orgID:
-          type: string
-        retentionRules:
-          $ref: '#/components/schemas/RetentionRules'
-        rp:
-          type: string
-        schemaType:
-          $ref: '#/components/schemas/SchemaType'
-          default: implicit
-        type:
-          default: demodata
-          readOnly: true
-          type: string
-        updatedAt:
-          format: date-time
-          readOnly: true
-          type: string
-      required:
-        - name
-        - retentionRules
-    DemoDataBuckets:
-      properties:
-        buckets:
-          items:
-            $ref: '#/components/schemas/DemoDataBucket'
-          type: array
-        links:
-          $ref: '#/components/schemas/Links'
-          readOnly: true
-      type: object
     Dialect:
       description: >-
         Dialect are options to change the default CSV output format;
@@ -1315,23 +1244,22 @@ components:
           type: string
         err:
           description: >-
-            err is a stack of errors that occurred during processing of the
-            request. Useful for debugging.
+            Stack of errors that occurred during processing of the request.
+            Useful for debugging.
           readOnly: true
           type: string
         message:
-          description: message is a human-readable message.
+          description: Human-readable message.
           readOnly: true
           type: string
         op:
           description: >-
-            op describes the logical code operation during error. Useful for
-            debugging.
+            Describes the logical code operation when the error occurred. Useful
+            for debugging.
           readOnly: true
           type: string
       required:
         - code
-        - message
     Expression:
       oneOf:
         - $ref: '#/components/schemas/ArrayExpression'
@@ -2232,6 +2160,9 @@ components:
             deleteRequestsPerSecond:
               description: Allowed organization delete request rate.
               type: integer
+            queryTime:
+              description: Query Time in nanoseconds
+              type: integer
             readKBs:
               description: Query limit in kb/sec. 0 is unlimited.
               type: integer
@@ -2240,6 +2171,7 @@ components:
               type: integer
           required:
             - readKBs
+            - queryTime
             - concurrentReadRequests
             - writeKBs
             - concurrentWriteRequests
@@ -2376,30 +2308,27 @@ components:
           type: string
         err:
           description: >-
-            Err is a stack of errors that occurred during processing of the
-            request. Useful for debugging.
+            Stack of errors that occurred during processing of the request.
+            Useful for debugging.
           readOnly: true
           type: string
         line:
-          description: First line within sent body containing malformed data
+          description: First line in the request body that contains malformed data.
           format: int32
           readOnly: true
           type: integer
         message:
-          description: Message is a human-readable message.
+          description: Human-readable message.
           readOnly: true
           type: string
         op:
           description: >-
-            Op describes the logical code operation during error. Useful for
-            debugging.
+            Describes the logical code operation when the error occurred. Useful
+            for debugging.
           readOnly: true
           type: string
       required:
         - code
-        - message
-        - op
-        - err
     LineProtocolLengthError:
       properties:
         code:
@@ -2409,7 +2338,7 @@ components:
           readOnly: true
           type: string
         message:
-          description: Message is a human-readable message.
+          description: Human-readable message.
           readOnly: true
           type: string
       required:
@@ -2498,12 +2427,13 @@ components:
         - note
       type: object
     MeasurementSchema:
-      description: The schema definition for a single measurement
+      description: Definition of a measurement schema.
       example:
         bucketID: ba3c5e7f9b0a0010
         columns:
-          - name: time
-            type: timestamp
+          - format: unix timestamp
+            name: time
+            type: integer
           - name: host
             type: tag
           - name: region
@@ -2514,17 +2444,17 @@ components:
           - dataType: float
             name: usage_user
             type: field
-        createdAt: 2021-01-21T00:48:40.993Z
+        createdAt: '2021-01-21T00:48:40.993Z'
         id: 1a3c5e7f9b0a8642
         name: cpu
         orgID: 0a3c5e7f9b0a0001
-        updatedAt: 2021-01-21T00:48:40.993Z
+        updatedAt: '2021-01-21T00:48:40.993Z'
       properties:
         bucketID:
           description: ID of the bucket that the measurement schema is associated with.
           type: string
         columns:
-          description: An ordered collection of column definitions
+          description: Ordered collection of column definitions.
           items:
             $ref: '#/components/schemas/MeasurementSchemaColumn'
           type: array
@@ -2539,7 +2469,9 @@ components:
           nullable: false
           type: string
         orgID:
-          description: ID of organization that the measurement schema is associated with.
+          description: >-
+            ID of the organization that the measurement schema is associated
+            with.
           type: string
         updatedAt:
           format: date-time
@@ -2553,10 +2485,11 @@ components:
         - updatedAt
       type: object
     MeasurementSchemaColumn:
-      description: Definition of a measurement column
+      description: Definition of a measurement schema column.
       example:
+        format: unix timestamp
         name: time
-        type: timestamp
+        type: integer
       properties:
         dataType:
           $ref: '#/components/schemas/ColumnDataType'
@@ -2569,11 +2502,12 @@ components:
         - type
       type: object
     MeasurementSchemaCreateRequest:
-      description: Create a new measurement schema
+      description: Create a new measurement schema.
       example:
         columns:
-          - name: time
-            type: timestamp
+          - format: unix timestamp
+            name: time
+            type: integer
           - name: host
             type: tag
           - name: region
@@ -2587,7 +2521,7 @@ components:
         name: cpu
       properties:
         columns:
-          description: An ordered collection of column definitions
+          description: Ordered collection of column definitions.
           items:
             $ref: '#/components/schemas/MeasurementSchemaColumn'
           type: array
@@ -2602,23 +2536,23 @@ components:
       example:
         measurementSchemas:
           - bucketID: ba3c5e7f9b0a0010
-            createdAt: 2021-01-21T00:48:40.993Z
+            createdAt: '2021-01-21T00:48:40.993Z'
             id: 1a3c5e7f9b0a8642
             name: cpu
             orgID: 0a3c5e7f9b0a0001
-            updatedAt: 2021-01-21T00:48:40.993Z
+            updatedAt: '2021-01-21T00:48:40.993Z'
           - bucketID: ba3c5e7f9b0a0010
-            createdAt: 2021-01-21T00:48:40.993Z
+            createdAt: '2021-01-21T00:48:40.993Z'
             id: 1a3c5e7f9b0a8643
             name: memory
             orgID: 0a3c5e7f9b0a0001
-            updatedAt: 2021-01-21T00:48:40.993Z
+            updatedAt: '2021-01-21T00:48:40.993Z'
           - bucketID: ba3c5e7f9b0a0010
-            createdAt: 2021-01-21T00:48:40.993Z
+            createdAt: '2021-01-21T00:48:40.993Z'
             id: 1a3c5e7f9b0a8644
             name: disk
             orgID: 0a3c5e7f9b0a0001
-            updatedAt: 2021-01-21T00:48:40.993Z
+            updatedAt: '2021-01-21T00:48:40.993Z'
       properties:
         measurementSchemas:
           items:
@@ -2631,8 +2565,9 @@ components:
       description: Update an existing measurement schema
       example:
         columns:
-          - name: time
-            type: timestamp
+          - format: unix timestamp
+            name: time
+            type: integer
           - name: host
             type: tag
           - name: region
@@ -2923,7 +2858,10 @@ components:
           readOnly: true
           type: string
         latestCompleted:
-          description: Timestamp of latest scheduled, completed run, RFC3339.
+          description: >-
+            Timestamp (in RFC3339 date/time
+            format](https://datatracker.ietf.org/doc/html/rfc3339)) of the
+            latest scheduled and completed run.
           format: date-time
           readOnly: true
           type: string
@@ -3337,6 +3275,13 @@ components:
           type: string
         name:
           type: string
+        users:
+          description: >-
+            An optional list of email address's to be invited to the
+            organization
+          items:
+            type: string
+          type: array
       required:
         - name
       type: object
@@ -3428,7 +3373,7 @@ components:
     Ready:
       properties:
         started:
-          example: 2019-03-13T10:09:33.891196-04:00
+          example: '2019-03-13T10:09:33.891196-04:00'
           format: date-time
           type: string
         status:
@@ -3958,6 +3903,7 @@ components:
     ScriptInvocationParams:
       properties:
         params:
+          additionalProperties: true
           type: object
       type: object
     ScriptLanguage:
@@ -4319,8 +4265,8 @@ components:
       properties:
         authorizationID:
           description: >-
-            The ID of the authorization used when this task communicates with
-            the query engine.
+            ID of the authorization used when the task communicates with the
+            query engine.
           type: string
         createdAt:
           format: date-time
@@ -4328,17 +4274,27 @@ components:
           type: string
         cron:
           description: >-
-            A task repetition schedule in the form '* * * * * *'; parsed from
-            Flux.
+            [Cron expression](https://en.wikipedia.org/wiki/Cron#Overview) that
+            defines the schedule on which the task runs. Cron scheduling is
+            based on system time.
+
+            Value is a [Cron
+            expression](https://en.wikipedia.org/wiki/Cron#Overview).
           type: string
         description:
-          description: An optional description of the task.
+          description: Description of the task.
           type: string
         every:
-          description: A simple task repetition schedule; parsed from Flux.
+          description: >-
+            Interval at which the task runs. `every` also determines when the
+            task first runs, depending on the specified time.
+
+            Value is a [duration
+            literal](https://docs.influxdata.com/flux/v0.x/spec/lexical-elements/#duration-literals)).
+          format: duration
           type: string
         flux:
-          description: The Flux script to run for this task.
+          description: Flux script to run for this task.
           type: string
         id:
           readOnly: true
@@ -4356,7 +4312,11 @@ components:
           readOnly: true
           type: string
         latestCompleted:
-          description: Timestamp of latest scheduled, completed run, RFC3339.
+          description: >-
+            Timestamp of the latest scheduled and completed run.
+
+            Value is a timestamp in [RFC3339 date/time
+            format](https://docs.influxdata.com/flux/v0.x/data-types/basic/time/#time-syntax).
           format: date-time
           readOnly: true
           type: string
@@ -4384,29 +4344,31 @@ components:
           readOnly: true
           type: object
         name:
-          description: The name of the task.
+          description: Name of the task.
           type: string
         offset:
           description: >-
-            Duration to delay after the schedule, before executing the task;
-            parsed from flux, if set to zero it will remove this option and use
-            0 as the default.
+            [Duration](https://docs.influxdata.com/flux/v0.x/spec/lexical-elements/#duration-literals)
+            to delay execution of the task after the scheduled time has elapsed.
+            `0` removes the offset.
+
+            The value is a [duration
+            literal](https://docs.influxdata.com/flux/v0.x/spec/lexical-elements/#duration-literals).
+          format: duration
           type: string
         org:
-          description: The name of the organization that owns this Task.
+          description: Name of the organization that owns the task.
           type: string
         orgID:
-          description: The ID of the organization that owns this Task.
+          description: ID of the organization that owns the task.
           type: string
         ownerID:
-          description: The ID of the user who owns this Task.
+          description: ID of the user who owns this Task.
           type: string
         status:
           $ref: '#/components/schemas/TaskStatusType'
         type:
-          description: >-
-            The type of task, this can be used for filtering tasks on list
-            actions.
+          description: Type of the task, useful for filtering a task list.
           type: string
         updatedAt:
           format: date-time
@@ -5829,6 +5791,8 @@ components:
         - stacked
         - bar
         - monotoneX
+        - stepBefore
+        - stepAfter
       type: string
     XYViewProperties:
       properties:
@@ -5992,7 +5956,7 @@ info:
     with InfluxDB. Access the InfluxDB API using the `/api/v2/` endpoint.
 openapi: 3.0.0
 paths:
-  /api/v2/:
+  /api/v2:
     get:
       operationId: GetRoutes
       parameters:
@@ -7272,9 +7236,7 @@ paths:
           required: true
           schema:
             type: string
-        - description: >-
-            Includes the cell view properties in the response if set to
-            `properties`
+        - description: If `properties`, includes the cell view properties in the response.
           in: query
           name: include
           required: false
@@ -7303,7 +7265,7 @@ paths:
               schema:
                 $ref: '#/components/schemas/Error'
           description: Unexpected error
-      summary: Retrieve a Dashboard
+      summary: Retrieve a dashboard
       tags:
         - Dashboards
     patch:
@@ -8181,69 +8143,6 @@ paths:
       summary: Delete data
       tags:
         - Delete
-  /api/v2/experimental/sampledata/buckets:
-    get:
-      operationId: GetDemoDataBuckets
-      responses:
-        '200':
-          content:
-            application/json:
-              schema:
-                $ref: '#/components/schemas/DemoDataBuckets'
-          description: A list of demo data buckets
-        default:
-          $ref: '#/components/responses/ServerError'
-          description: Unexpected error
-      summary: List of Demo Data Buckets
-      tags:
-        - DemoDataBuckets
-  /api/v2/experimental/sampledata/buckets/{bucketID}/members:
-    delete:
-      operationId: DeleteDemoDataBucketMembers
-      parameters:
-        - description: bucket id
-          in: path
-          name: bucketID
-          required: true
-          schema:
-            type: string
-      responses:
-        '200':
-          description: if sampledata route is not available gateway responds with 200
-        '204':
-          description: A list of demo data buckets
-        default:
-          content:
-            application/json:
-              schema:
-                $ref: '#/components/schemas/Error'
-          description: Unexpected error
-      summary: List of Demo Data Buckets
-      tags:
-        - DemoDataBuckets
-    post:
-      operationId: GetDemoDataBucketMembers
-      parameters:
-        - description: bucket id
-          in: path
-          name: bucketID
-          required: true
-          schema:
-            type: string
-      responses:
-        '200':
-          description: if sampledata route is not available gateway responds with 200
-        '204':
-          description: A list of demo data buckets
-        default:
-          content:
-            application/json:
-              schema:
-                $ref: '#/components/schemas/Error'
-          description: Unexpected error
-      summary: List of Demo Data Buckets
-      tags:
-        - DemoDataBuckets
   /api/v2/flags:
     get:
       operationId: GetFlags
@@ -8419,13 +8318,14 @@ paths:
             application/json:
               schema:
                 $ref: '#/components/schemas/Token'
-          description: A temp token for Mapbox
+          description: Temporary token for Mapbox.
         '401':
           $ref: '#/components/responses/ServerError'
         '500':
           $ref: '#/components/responses/ServerError'
         default:
           $ref: '#/components/responses/ServerError'
+      summary: Get a mapbox token
   /api/v2/me:
     get:
       operationId: GetMe
@@ -9250,8 +9150,9 @@ paths:
         - Organizations
   /api/v2/orgs/{orgID}/limits:
     get:
+      operationId: GetOrgLimitsID
       parameters:
-        - description: The identifier of the organization.
+        - description: ID of the organization.
           in: path
           name: orgID
           required: true
@@ -9269,7 +9170,7 @@ paths:
                   links:
                     $ref: '#/components/schemas/Links'
                 type: object
-          description: The Limits defined for the organization.
+          description: Limits defined for the organization.
         default:
           $ref: '#/components/responses/ServerError'
           description: unexpected error
@@ -9581,25 +9482,38 @@ paths:
         - Secrets
   /api/v2/orgs/{orgID}/usage:
     get:
+      operationId: GetOrgUsageID
       parameters:
-        - description: The identifier of the organization.
+        - description: ID of the organization.
           in: path
           name: orgID
           required: true
           schema:
             type: string
-        - description: start time
+        - description: >
+            Earliest time to include in results.
+
+            For more information about timestamps, see [Manipulate timestamps
+            with
+            Flux](https://docs.influxdata.com/influxdb/cloud/query-data/flux/manipulate-timestamps/).
           in: query
           name: start
           required: true
           schema:
-            type: timestamp
-        - description: stop time
+            format: unix timestamp
+            type: integer
+        - description: >
+            Latest time to include in results.
+
+            For more information about timestamps, see [Manipulate timestamps
+            with
+            Flux](https://docs.influxdata.com/influxdb/cloud/query-data/flux/manipulate-timestamps/).
           in: query
           name: stop
           required: false
           schema:
-            type: timestamp
+            format: unix timestamp
+            type: integer
         - description: return raw usage data
           in: query
           name: raw
@@ -9643,10 +9557,13 @@ paths:
         - Usage
   /ping:
     get:
+      description: Returns the status and InfluxDB version of the instance.
       operationId: GetPing
       responses:
         '204':
-          description: OK
+          description: |
+            OK.
+            Headers contain InfluxDB version information.
           headers:
             X-Influxdb-Build:
               description: The type of InfluxDB build.
@@ -9656,16 +9573,18 @@ paths:
               description: The version of InfluxDB.
               schema:
                 type: integer
-      servers:
-        - url: ''
-      summary: Checks the status of InfluxDB instance and version of InfluxDB.
+      servers: []
+      summary: Get the status and version of the instance
       tags:
         - Ping
     head:
+      description: Returns the status and InfluxDB version of the instance.
       operationId: HeadPing
       responses:
         '204':
-          description: OK
+          description: |
+            OK.
+            Headers contain InfluxDB version information.
           headers:
             X-Influxdb-Build:
               description: The type of InfluxDB build.
@@ -9675,9 +9594,8 @@ paths:
               description: The version of InfluxDB.
               schema:
                 type: integer
-      servers:
-        - url: ''
-      summary: Checks the status of InfluxDB instance and version of InfluxDB.
+      servers: []
+      summary: Get the status and version of the instance
       tags:
         - Ping
   /api/v2/query:
@@ -9728,16 +9646,16 @@ paths:
               - application/vnd.flux
             type: string
         - description: >-
-            Specifies the name of the organization executing the query. Takes
-            either the ID or Name. If both `orgID` and `org` are specified,
-            `org` takes precedence.
+            Name of the organization executing the query. Accepts either the ID
+            or Name. If you provide both `orgID` and `org`, `org` takes
+            precedence.
           in: query
           name: org
           schema:
             type: string
         - description: >-
-            Specifies the ID of the organization executing the query. If both
-            `orgID` and `org` are specified, `org` takes precedence.
+            ID of the organization executing the query. If you provide both
+            `orgID` and `org`, `org` takes precedence.
           in: query
           name: orgID
           schema:
@@ -9758,10 +9676,6 @@ paths:
       responses:
         '200':
           content:
-            application/vnd.influx.arrow:
-              schema:
-                format: binary
-                type: string
             text/csv:
               schema:
                 example: >
@@ -9779,28 +9693,33 @@ paths:
               schema:
                 default: identity
                 description: >
-                  The content coding: `gzip` for compressed data or `identity`
-                  for unmodified, uncompressed data.
+                  Content coding: `gzip` for compressed data or `identity` for
+                  unmodified, uncompressed data.
                 enum:
                   - gzip
                   - identity
                 type: string
             Trace-Id:
-              description: >-
-                The Trace-Id header reports the request's trace ID, if one was
-                generated.
+              description: If generated, trace ID of the request.
               schema:
-                description: Specifies the request's trace ID.
+                description: Trace ID of a request.
                 type: string
         '429':
-          description: >-
-            Token is temporarily over quota. The Retry-After header describes
-            when to try the read again.
+          description: |
+            #### InfluxDB Cloud:
+              - returns this error if a **read** or **write** request exceeds your
+                plan's [adjustable service quotas](https://docs.influxdata.com/influxdb/cloud/account-management/limits/#adjustable-service-quotas)
+                or if a **delete** request exceeds the maximum
+                [global limit](https://docs.influxdata.com/influxdb/cloud/account-management/limits/#global-limits)
+              - returns `Retry-After` header that describes when to try the write again.
+
+            #### InfluxDB OSS:
+              - doesn't return this error.
           headers:
             Retry-After:
               description: >-
-                A non-negative decimal integer indicating the seconds to delay
-                after the response is received.
+                Non-negative decimal integer indicating seconds to wait before
+                retrying the request.
               schema:
                 format: int32
                 type: integer
@@ -9988,7 +9907,7 @@ paths:
           description: Unexpected error
       summary: List scripts
       tags:
-        - Invocable Scripts
+        - Invokable Scripts
     post:
       operationId: PostScripts
       requestBody:
@@ -10010,7 +9929,7 @@ paths:
           description: Unexpected error
       summary: Create a script
       tags:
-        - Invocable Scripts
+        - Invokable Scripts
   /api/v2/scripts/{scriptID}:
     delete:
       description: Deletes a script and all associated records.
@@ -10030,9 +9949,9 @@ paths:
           description: Unexpected error
       summary: Delete a script
       tags:
-        - Invocable Scripts
+        - Invokable Scripts
     get:
-      description: Uses script ID to retrieve details of an invocable script.
+      description: Uses script ID to retrieve details of an invokable script.
       operationId: GetScriptsID
       parameters:
         - description: The script ID.
@@ -10053,10 +9972,10 @@ paths:
           description: Unexpected error
       summary: Retrieve a script
       tags:
-        - Invocable Scripts
+        - Invokable Scripts
     patch:
       description: >
-        Updates properties (`name`, `description`, and `script`) of an invocable
+        Updates properties (`name`, `description`, and `script`) of an invokable
         script.
       operationId: PatchScriptsID
       parameters:
@@ -10085,7 +10004,7 @@ paths:
           description: Unexpected error
       summary: Update a script
       tags:
-        - Invocable Scripts
+        - Invokable Scripts
   /api/v2/scripts/{scriptID}/invoke:
     post:
       description: >-
@@ -10115,7 +10034,7 @@ paths:
           description: Unexpected error
       summary: Invoke a script
       tags:
-        - Invocable Scripts
+        - Invokable Scripts
   /api/v2/setup:
     get:
       description: >-
@@ -11653,6 +11572,22 @@ paths:
             summary of the run. The summary contains newly created resources.
             The diff compares the initial state to the state after the package
             applied. This corresponds to `"dryRun": true`.
+        '422':
+          content:
+            application/json:
+              schema:
+                allOf:
+                  - $ref: '#/components/schemas/TemplateSummary'
+                  - properties:
+                      code:
+                        type: string
+                      message:
+                        type: string
+                    required:
+                      - message
+                      - code
+                    type: object
+          description: Template failed validation
         default:
           content:
             application/json:
@@ -12104,108 +12039,129 @@ paths:
         Writes data to a bucket.
 
 
-        To write data into InfluxDB, you need the following:
+        Use this endpoint to send data in [line
+        protocol](https://docs.influxdata.com/influxdb/cloud/reference/syntax/line-protocol/)
+        format to InfluxDB.
+
+        InfluxDB parses and validates line protocol in the request body,
+
+        responds with success or failure, and then handles the write
+        asynchronously.
 
 
-        - **organization name or ID** – _See [View
-        organizations](https://docs.influxdata.com/influxdb/cloud/organizations/view-orgs/#view-your-organization-id)
-        for instructions on viewing your organization ID._
-
-        - **bucket** – _See [View
-        buckets](https://docs.influxdata.com/influxdb/cloud/organizations/buckets/view-buckets/)
-        for
-         instructions on viewing your bucket ID._
-        - **API token** – _See [View
-        tokens](https://docs.influxdata.com/influxdb/cloud/security/tokens/view-tokens/)
-         for instructions on viewing your API token._
-        - **InfluxDB URL** – _See [InfluxDB
-        URLs](https://docs.influxdata.com/influxdb/cloud/reference/urls/)_.
-
-        - data in [line
-        protocol](https://docs.influxdata.com/influxdb/cloud/reference/syntax/line-protocol)
-        format.
+        #### Required permissions
 
 
-        InfluxDB Cloud enforces rate and size limits different from InfluxDB
-        OSS. For details, see Responses.
+        - `write-buckets` or `write-bucket BUCKET_ID`
 
 
-        For more information and examples, see the following:
+        `BUCKET_ID` is the ID of the destination bucket.
+
+
+        #### Rate limits (with InfluxDB Cloud)
+
+
+        `write` rate limits apply.
+
+        For more information, see [limits and adjustable
+        quotas](https://docs.influxdata.com/influxdb/cloud/account-management/limits/).
+
+
+        #### Related guides
+
 
         - [Write data with the InfluxDB
         API](https://docs.influxdata.com/influxdb/cloud/write-data/developer-tools/api).
 
         - [Optimize writes to
         InfluxDB](https://docs.influxdata.com/influxdb/cloud/write-data/best-practices/optimize-writes/).
+
+        - [Troubleshoot issues writing
+        data](https://docs.influxdata.com/influxdb/cloud/write-data/troubleshoot/)
       operationId: PostWrite
       parameters:
         - $ref: '#/components/parameters/TraceSpan'
-        - description: >
-            The value tells InfluxDB what compression is applied to the line
-            protocol in the request payload.
-
-            To make an API request with a GZIP payload, send `Content-Encoding:
-            gzip` as a request header.
+        - description: |
+            The compression applied to the line protocol in the request payload.
+            To send a GZIP payload, pass `Content-Encoding: gzip` header.
           in: header
           name: Content-Encoding
           schema:
             default: identity
-            description: >-
-              The content coding. Use `gzip` for compressed data or `identity`
-              for unmodified, uncompressed data.
+            description: >
+              Content coding.
+
+              Use `gzip` for compressed data or `identity` for unmodified,
+              uncompressed data.
             enum:
               - gzip
               - identity
             type: string
-        - description: >-
-            The header value indicates the format of the data in the request
-            body.
+        - description: >
+            The format of the data in the request body.
+
+            To send a line protocol payload, pass `Content-Type: text/plain;
+            charset=utf-8`.
           in: header
           name: Content-Type
           schema:
             default: text/plain; charset=utf-8
             description: >
-              `text/plain` specifies line protocol. `UTF-8` is the default
-              character set.
+              `text/plain` is the content type for line protocol. `UTF-8` is the
+              default character set.
             enum:
               - text/plain
               - text/plain; charset=utf-8
-              - application/vnd.influx.arrow
             type: string
-        - description: >-
-            The header value indicates the size of the entity-body, in bytes,
-            sent to the database. If the length is greater than the database's
-            `max body` configuration option, the server responds with status
-            code `413`.
+        - description: |
+            The size of the entity-body, in bytes, sent to InfluxDB.
+            If the length is greater than the `max body` configuration option,
+            the server responds with status code `413`.
           in: header
           name: Content-Length
           schema:
             description: The length in decimal number of octets.
             type: integer
-        - description: The header value specifies the response format.
+        - description: |
+            The content type that the client can understand.
+            Writes only return a response body if they fail--for example,
+            due to a formatting problem or quota limit.
+
+            #### InfluxDB Cloud
+
+              - Returns only `application/json` for format and limit errors.
+              - Returns only `text/html` for some quota limit errors.
+
+            #### InfluxDB OSS
+
+              - Returns only `application/json` for format and limit errors.
+
+            #### Related guides
+              - [Troubleshoot issues writing data](https://docs.influxdata.com/influxdb/cloud/write-data/troubleshoot/).
           in: header
           name: Accept
           schema:
             default: application/json
-            description: The response format for errors.
+            description: Error content type.
             enum:
               - application/json
             type: string
-        - description: >-
-            The parameter value specifies the destination organization for
-            writes. The database writes all points in the batch to this
-            organization. If you provide both `orgID` and `org` parameters,
-            `org` takes precedence.
+        - description: >
+            The destination organization for writes.
+
+            The database writes all points in the batch to this organization.
+
+            If you provide both `orgID` and `org` parameters, `org` takes
+            precedence.
           in: query
           name: org
           required: true
           schema:
-            description: Organization name or ID.
+            description: The organization name or ID.
             type: string
-        - description: >-
-            The parameter value specifies the ID of the destination organization
-            for writes. If both `orgID` and `org` are specified, `org` takes
-            precedence.
+        - description: |
+            The ID of the destination organization for writes.
+            If both `orgID` and `org` are specified, `org` takes precedence.
           in: query
           name: orgID
           schema:
@@ -12215,9 +12171,9 @@ paths:
           name: bucket
           required: true
           schema:
-            description: All points within batch are written to this bucket.
+            description: InfluxDB writes all points in the batch to this bucket.
             type: string
-        - description: The precision for the unix timestamps within the body line-protocol.
+        - description: The precision for unix timestamps in the line protocol batch.
           in: query
           name: precision
           schema:
@@ -12225,24 +12181,59 @@ paths:
       requestBody:
         content:
           text/plain:
+            examples:
+              plain-utf8:
+                value: >
+                  airSensors,sensor_id=TLM0201
+                  temperature=73.97038159354763,humidity=35.23103248356096,co=0.48445310567793615
+                  1630424257000000000
+
+                  airSensors,sensor_id=TLM0202
+                  temperature=75.30007505999716,humidity=35.651929918691714,co=0.5141876544505826
+                  1630424257000000000
             schema:
               format: byte
               type: string
-        description: Data in line protocol format.
+        description: >
+          Data in line protocol format.
+
+
+          To send compressed data, do the following:
+
+            1. Use [GZIP](https://www.gzip.org/) to compress the line protocol data.
+            2. In your request, send the compressed data and the
+               `Content-Encoding: gzip` header.
+
+          #### Related guides
+
+
+          - [Best practices for optimizing
+          writes](https://docs.influxdata.com/influxdb/cloud/write-data/best-practices/optimize-writes/).
         required: true
       responses:
         '204':
-          description: >-
-            InfluxDB validated the request data format and accepted the data for
-            writing to the bucket. `204` doesn't indicate a successful write
-            operation since writes are asynchronous. See [how to check for write
+          description: >
+            Success. InfluxDB validated the request and the data format and
+
+            accepted the data for writing to the bucket.
+
+            Because data is written to InfluxDB asynchronously, data may not yet
+            be written to a bucket.
+
+
+            #### Related guides
+
+
+            - [How to check for write
             errors](https://docs.influxdata.com/influxdb/cloud/write-data/troubleshoot/).
         '400':
           content:
             application/json:
               examples:
                 measurementSchemaFieldTypeConflict:
-                  summary: Field type conflict thrown by an explicit bucket schema
+                  summary: >-
+                    InfluxDB Cloud field type conflict thrown by an explicit
+                    bucket schema
                   value:
                     code: invalid
                     message: >-
@@ -12253,9 +12244,9 @@ paths:
                       schema; got String but expected Float
               schema:
                 $ref: '#/components/schemas/LineProtocolError'
-          description: >-
-            Bad request. The line protocol data in the request is malformed. The
-            response body contains the first malformed line in the data.
+          description: |
+            Bad request. The line protocol data in the request is malformed.
+            The response body contains the first malformed line in the data.
             InfluxDB rejected the batch and did not write any data.
         '401':
           content:
@@ -12316,26 +12307,39 @@ paths:
                     </html>
               schema:
                 type: string
-          description: >
-            The request payload is too large. InfluxDB rejected the batch and
-            did not write any data.
+          description: |
+            The request payload is too large.
+            InfluxDB rejected the batch and did not write any data.
 
             #### InfluxDB Cloud:
-             - returns this error if the payload exceeds the 50MB size limit.
-             - returns `Content-Type: text/html` for this error.
+
+             - Returns this error if the payload exceeds the 50MB size limit.
+             - Returns `Content-Type: text/html` for this error.
 
             #### InfluxDB OSS:
-             - returns this error only if the [Go (golang) `ioutil.ReadAll()`](https://pkg.go.dev/io/ioutil#ReadAll) function raises an error.
-             - returns `Content-Type: application/json` for this error.
+
+             - Returns this error only if the [Go (golang) `ioutil.ReadAll()`](https://pkg.go.dev/io/ioutil#ReadAll) function raises an error.
+             - Returns `Content-Type: application/json` for this error.
         '429':
-          description: >-
-            InfluxDB Cloud only. The token is temporarily over quota. The
-            Retry-After header describes when to try the write again.
+          description: |
+            Too many requests.
+
+            #### InfluxDB Cloud
+
+              - Returns this error if a **read** or **write** request exceeds your
+                plan's [adjustable service quotas](https://docs.influxdata.com/influxdb/cloud/account-management/limits/#adjustable-service-quotas)
+                or if a **delete** request exceeds the maximum
+                [global limit](https://docs.influxdata.com/influxdb/cloud/account-management/limits/#global-limits).
+              - Returns `Retry-After` header that describes when to try the write again.
+
+            #### InfluxDB OSS
+
+              - Doesn't return this error.
           headers:
             Retry-After:
               description: >-
-                A non-negative decimal integer indicating the seconds to delay
-                after the response is received.
+                Non-negative decimal integer indicating seconds to wait before
+                retrying the request.
               schema:
                 format: int32
                 type: integer
@@ -12351,14 +12355,25 @@ paths:
                 $ref: '#/components/schemas/Error'
           description: Internal server error.
         '503':
-          description: >-
-            The server is temporarily unavailable to accept writes. The
-            `Retry-After` header describes when to try the write again.
+          description: |
+            Service unavailable.
+
+            #### InfluxDB Cloud
+
+              - Returns this error if series cardinality exceeds your plan's
+                [adjustable service quotas](https://docs.influxdata.com/influxdb/cloud/account-management/limits/#adjustable-service-quotas).
+                See [how to resolve high series cardinality](https://docs.influxdata.com/influxdb/cloud/write-data/best-practices/resolve-high-cardinality/).
+
+            #### InfluxDB OSS
+
+              - Returns this error if
+                the server is temporarily unavailable to accept writes.
+              - Returns `Retry-After` header that describes when to try the write again.
           headers:
             Retry-After:
               description: >-
-                A non-negative decimal integer indicating the seconds to delay
-                after the response is received.
+                Non-negative decimal integer indicating seconds to wait before
+                retrying the request.
               schema:
                 format: int32
                 type: integer
@@ -12372,44 +12387,111 @@ security:
 servers:
   - url: /
 tags:
-  - description: |
-      The InfluxDB `/api/v2` API requires authentication for all requests.
-      Use InfluxDB API tokens to authenticate requests to the `/api/v2` API.
+  - description: >
+      Use one of the following schemes to authenticate to the InfluxDB API:
 
 
-      For more information, see
-      [Token authentication](#section/Authentication/TokenAuthentication)
+      - [Token authentication](#section/Authentication/TokenAuthentication)
+
+      - [Basic authentication](#section/Authentication/BasicAuthentication)
+
+      - [Querystring
+      authentication](#section/Authentication/QuerystringAuthentication)
 
       <!-- ReDoc-Inject: <security-definitions> -->
     name: Authentication
     x-traitTag: true
   - description: >
-      Create and manage API tokens. An **authorization** associates a list of
-      permissions to an **organization** and provides a token for API access.
+      Create and manage API tokens.
+
+      An **authorization** associates a list of permissions to an
+
+      **organization** and provides a token for API access.
+
       Optionally, you can restrict an authorization and its token to a specific
       user.
 
 
-      For more information and examples, see the following:
+      ### Related guides
+
         - [Authorize API requests](/influxdb/cloud/api-guide/api_intro/#authentication).
         - [Manage API tokens](/influxdb/cloud/security/tokens/).
         - [Assign a token to a specific user](/influxdb/cloud/security/tokens/create-token/).
     name: Authorizations
-  - Bucket Schemas
-  - Buckets
-  - Cells
-  - Checks
-  - Dashboards
-  - DBRPs
-  - Delete
-  - DemoDataBuckets
-  - Invocable Scripts
-  - Labels
-  - Limits
-  - NotificationEndpoints
-  - NotificationRules
-  - Organizations
-  - Ping
+  - name: Bucket Schemas
+  - name: Buckets
+  - name: Cells
+  - name: Checks
+  - name: Dashboards
+  - name: DBRPs
+  - name: Delete
+  - description: >
+      InfluxDB API endpoints use standard HTTP request and response headers.
+
+
+      **Note**: Not all operations support all headers.
+
+
+      ### Request headers
+
+
+      | Header                   | Value type            |
+      Description                                |
+
+      |:------------------------ |:---------------------
+      |:-------------------------------------------|
+
+      | `Accept`                 | string                | The content type that
+      the client can understand. |
+
+      | `Authorization`          | string                | The authorization
+      scheme and credential. |
+
+      | `Content-Encoding`       | string                | The compression
+      applied to the line protocol in the request payload. |
+
+      | `Content-Length`         | integer               | The size of the
+      entity-body, in bytes, sent to the database. |
+
+      | `Content-Type`           | string                | The format of the
+      data in the request body. |
+    name: Headers
+    x-traitTag: true
+  - description: >
+      Manage and execute scripts as API endpoints in InfluxDB.
+
+
+      An API Invokable Script assigns your custom Flux script to a new
+
+      InfluxDB API endpoint for your organization.
+
+      Invokable scripts let you execute your script as an HTTP request to the
+      endpoint.
+
+
+      Invokable scripts accept parameters.
+
+      Add parameter references in your script as `params.myparameter`.
+
+      When you `invoke` your script, you send parameters as key-value pairs in
+      the `params` object.
+
+      Then, InfluxDB executes your script with the key-value pairs as arguments,
+      and returns the result.
+
+
+      ### Related guides
+
+
+      - [Invoke custom
+      scripts](/influxdb/cloud/api-guide/api-invokable-scripts/).
+    name: Invokable Scripts
+  - name: Labels
+  - name: Limits
+  - name: NotificationEndpoints
+  - name: NotificationRules
+  - name: Organizations
+  - name: Ping
   - description: |
       Retrieve data, analyze queries, and get query suggestions.
     name: Query
@@ -12424,7 +12506,7 @@ tags:
       for popular languages and ready to import into your application.
     name: Quick start
     x-traitTag: true
-  - Resources
+  - name: Resources
   - description: >
       The InfluxDB API uses standard HTTP status codes for success and failure
       responses.
@@ -12479,20 +12561,20 @@ tags:
       when to try the request again. |
     name: Response codes
     x-traitTag: true
-  - Routes
-  - Rules
-  - Secrets
-  - Setup
-  - Signin
-  - Signout
-  - Tasks
-  - Telegraf Plugins
-  - Telegrafs
-  - Templates
-  - Usage
-  - Users
-  - Variables
-  - Views
+  - name: Routes
+  - name: Rules
+  - name: Secrets
+  - name: Setup
+  - name: Signin
+  - name: Signout
+  - name: Tasks
+  - name: Telegraf Plugins
+  - name: Telegrafs
+  - name: Templates
+  - name: Usage
+  - name: Users
+  - name: Variables
+  - name: Views
   - description: |
       Write time series data to buckets.
     name: Write
@@ -12501,11 +12583,14 @@ x-tagGroups:
     tags:
       - Quick start
       - Authentication
+      - Headers
       - Response codes
   - name: Data I/O endpoints
     tags:
       - Write
       - Query
+      - Invokable Scripts
+      - Tasks
   - name: Resource endpoints
     tags:
       - Buckets
@@ -12531,8 +12616,7 @@ x-tagGroups:
       - Dashboards
       - DBRPs
       - Delete
-      - DemoDataBuckets
-      - Invocable Scripts
+      - Invokable Scripts
       - Labels
       - Limits
       - NotificationEndpoints
diff --git a/api-docs/cloud/swaggerV1Compat.yml b/api-docs/cloud/swaggerV1Compat.yml
index 1a2cdaef3..b06e5956c 100644
--- a/api-docs/cloud/swaggerV1Compat.yml
+++ b/api-docs/cloud/swaggerV1Compat.yml
@@ -36,7 +36,7 @@ paths:
             type: string
           required: true
           description: >-
-            Bucket to write to. If none exists, a bucket will be created with a
+            Bucket to write to. If none exists, InfluxDB creates a bucket with a
             default 3-day retention policy.
         - in: query
           name: rp
@@ -486,8 +486,8 @@ tags:
 
       <!-- ReDoc-Inject: <security-definitions> -->
     x-traitTag: true
-  - Query
-  - Write
+  - name: Query
+  - name: Write
 x-tagGroups:
   - name: Overview
     tags:
diff --git a/api-docs/generate-api-docs.sh b/api-docs/generate-api-docs.sh
index 6c92284bb..3c6b240ad 100755
--- a/api-docs/generate-api-docs.sh
+++ b/api-docs/generate-api-docs.sh
@@ -46,17 +46,12 @@ weight: 304
   # npm_config_yes=true npx overrides the prompt
   # and (vs. npx --yes) is compatible with npm@6 and npm@7.
 
-  openapiCLI="@redocly/openapi-cli"
   redocCLI="redoc-cli@0.12.3"
 
-  npm --version
-
-  # Use Redoc's openapi-cli to regenerate the spec with custom decorations.
-  INFLUXDB_VERSION=$version npm_config_yes=true npx $openapiCLI bundle $version/ref.yml \
-    --config=./.redocly.yaml \
-    -o $version/ref.yml
+  npx --version
 
   # Use Redoc to generate the v2 API html
+  echo "Bundling ${version}/ref.yml"
   npm_config_yes=true npx $redocCLI bundle $version/ref.yml \
     -t template.hbs \
     --title="InfluxDB $titleVersion API documentation" \
@@ -67,12 +62,8 @@ weight: 304
     --templateOptions.version="$version" \
     --templateOptions.titleVersion="$titleVersion" \
 
-  # Use Redoc's openapi-cli to regenerate the v1-compat spec with custom decorations.
-  INFLUXDB_API_VERSION=v1compat INFLUXDB_VERSION=$version npm_config_yes=true npx $openapiCLI bundle $version/swaggerV1Compat.yml \
-    --config=./.redocly.yaml \
-    -o $version/swaggerV1Compat.yml
-
   # Use Redoc to generate the v1 compatibility API html
+  echo "Bundling ${version}/swaggerV1Compat.yml"
   npm_config_yes=true npx $redocCLI bundle $version/swaggerV1Compat.yml \
     -t template.hbs \
     --title="InfluxDB $titleVersion v1 compatibility API documentation" \
diff --git a/api-docs/getswagger.sh b/api-docs/getswagger.sh
index 3d43a8671..eaa2d7560 100755
--- a/api-docs/getswagger.sh
+++ b/api-docs/getswagger.sh
@@ -11,12 +11,14 @@
 # - a base URL using the -b flag.
 #   The baseURL specifies where to retrieve the openapi files from.
 #   The default baseUrl is the master branch of the influxdata/openapi repo.
+#   The default baseUrl for OSS is the tag for the latest InfluxDB release.
+#   When a new OSS version is released, update baseUrlOSS to with the tag (/influxdb-oss-[SEMANTIC_VERSION]).
 #   For local development, pass your openapi directory using the file:/// protocol.
 #
 # Syntax:
 #   sh ./getswagger.sh <context>
 #   sh ./getswagger.sh <context> -b <baseUrl>
-#   sh .getswagger.sh -c <context> -o <version> -b <baseUrl>
+#   sh ./getswagger.sh -c <context> -o <version> -b <baseUrl>
 #
 # Examples:
 #   sh ./getswagger.sh cloud
@@ -25,6 +27,7 @@
 versionDirs=($(ls -d */))
 latestOSS=${versionDirs[${#versionDirs[@]}-1]}
 baseUrl="https://raw.githubusercontent.com/influxdata/openapi/master"
+baseUrlOSS="https://raw.githubusercontent.com/influxdata/openapi/docs-release/influxdb-oss"
 ossVersion=${latestOSS%/}
 verbose=""
 context=""
@@ -63,6 +66,7 @@ case "$subcommand" in
         ;;
       b)
         baseUrl=$OPTARG
+        baseUrlOSS=$OPTARG
         ;;
       o)
         ossVersion=$OPTARG
@@ -87,20 +91,43 @@ function showArgs {
   echo "ossVersion: $ossVersion";
 }
 
+function postProcess() {
+  # Use npx to install and run the specified version of openapi-cli.
+  # npm_config_yes=true npx overrides the prompt
+  # and (vs. npx --yes) is compatible with npm@6 and npm@7.
+  specPath=$1
+  version="$2"
+  apiVersion="$3"
+
+  openapiCLI="@redocly/openapi-cli"
+
+  npx --version
+
+  # Use Redoc's openapi-cli to regenerate the spec with custom decorations.
+  INFLUXDB_API_VERSION=$apiVersion \
+  INFLUXDB_VERSION=$version \
+  npm_config_yes=true \
+  npx $openapiCLI bundle $specPath \
+    --config=./.redocly.yaml \
+    -o $specPath
+}
+
 function updateCloud {
-  echo "Updating Cloud openapi..."
   curl ${verbose} ${baseUrl}/contracts/ref/cloud.yml -s -o cloud/ref.yml
+  postProcess $_ cloud
 }
 
 function updateOSS {
-  echo "Updating OSS ${ossVersion} openapi..."
-  mkdir -p ${ossVersion} && curl ${verbose} ${baseUrl}/contracts/ref/oss.yml -s -o $_/ref.yml
+  mkdir -p ${ossVersion} && curl ${verbose} ${baseUrlOSS}/contracts/ref/oss.yml -s -o $_/ref.yml
+  postProcess $_ $ossVersion
 }
 
 function updateV1Compat {
-  echo "Updating Cloud and ${ossVersion} v1 compatibility openapi..."
   curl ${verbose} ${baseUrl}/contracts/swaggerV1Compat.yml -s -o cloud/swaggerV1Compat.yml
+  postProcess $_ cloud v1compat
+
   mkdir -p ${ossVersion} && cp cloud/swaggerV1Compat.yml $_/swaggerV1Compat.yml
+  postProcess $_ $ossVersion v1compat
 }
 
 if [ ! -z ${verbose} ];
diff --git a/api-docs/openapi/content/cloud/security-schemes.yml b/api-docs/openapi/content/cloud/security-schemes.yml
deleted file mode 100644
index 8bb0bcd7e..000000000
--- a/api-docs/openapi/content/cloud/security-schemes.yml
+++ /dev/null
@@ -1,56 +0,0 @@
-TokenAuthentication:
-  type: http
-  scheme: token
-  bearerFormat: InfluxDB Token String
-  description: |
-    ### Token authentication scheme
-
-    InfluxDB API tokens ensure secure interaction between users and data. A token belongs to an organization and identifies InfluxDB permissions within the organization.
-
-    Include your API token in an `Authorization: Token YOUR_API_TOKEN` HTTP header with each request.
-
-    ### Example
-
-    `curl https://us-east-1-1.aws.cloud2.influxdata.com/
-          --header "Authorization: Token YOUR_API_TOKEN"`
-
-    For more information and examples, see the following:
-      - [Use tokens in API requests](https://docs.influxdata.com/influxdb/cloud/api-guide/api_intro/#authentication).
-      - [Manage API tokens](https://docs.influxdata.com/influxdb/cloud/security/tokens).
-      - [`/authorizations`](#tag/Authorizations) endpoint.
-BasicAuthentication:
-  type: http
-  scheme: basic
-  description: |
-    ### Basic authentication scheme
-
-    Use HTTP Basic Auth with clients that support the InfluxDB 1.x convention of username and password (that don't support the `Authorization: Token` scheme):
-      - **username**: InfluxDB Cloud username
-      - **password**: InfluxDB Cloud API token
-
-    ### Example
-
-    `curl --get "https://europe-west1-1.gcp.cloud2.influxdata.com/query"
-          --user "YOUR_USERNAME":"YOUR_TOKEN_OR_PASSWORD"`
-
-    For more information and examples, see how to [authenticate with a username and password scheme](https://docs.influxdata.com/influxdb/cloud/reference/api/influxdb-1x/).
-QuerystringAuthentication:
-  type: apiKey
-  in: query
-  name: u=&p=
-  description: |
-    ### Querystring authentication scheme
-
-    Use InfluxDB 1.x API parameters to provide credentials through the query string.
-
-    Username and password schemes require the following credentials:
-    - **username**: InfluxDB Cloud username
-    - **password**: InfluxDB Cloud API token
-
-    ### Example
-
-    `curl --get "https://europe-west1-1.gcp.cloud2.influxdata.com/query"
-          --data-urlencode "u=YOUR_USERNAME"
-          --data-urlencode "p=YOUR_TOKEN_OR_PASSWORD"`
-
-    For more information and examples, see how to [authenticate with a username and password scheme](https://docs.influxdata.com/influxdb/cloud/reference/api/influxdb-1x/).
diff --git a/api-docs/openapi/content/cloud/tag-groups.yml b/api-docs/openapi/content/cloud/tag-groups.yml
deleted file mode 100644
index 975b8831a..000000000
--- a/api-docs/openapi/content/cloud/tag-groups.yml
+++ /dev/null
@@ -1,26 +0,0 @@
-- name: Overview
-  tags:
-    - Quick start
-    - Authentication
-    - Response codes
-- name: Data I/O endpoints
-  tags:
-    - Write
-    - Query
-- name: Resource endpoints
-  tags:
-    - Buckets
-    - Dashboards
-    - Tasks
-    - Resources
-- name: Security and access endpoints
-  tags:
-    - Authorizations
-    - Organizations
-    - Users
-- name: System information endpoints
-  tags:
-    - Ping
-    - Routes
-- name: All endpoints
-  tags: []
diff --git a/api-docs/openapi/content/cloud/tags.yml b/api-docs/openapi/content/cloud/tags.yml
deleted file mode 100644
index 99031e526..000000000
--- a/api-docs/openapi/content/cloud/tags.yml
+++ /dev/null
@@ -1,55 +0,0 @@
-- name: Authentication
-  description: |
-    Use one of the following schemes to authenticate to the InfluxDB API:
-    - [Token authentication](#section/Authentication/TokenAuthentication)
-    - [Basic authentication](#section/Authentication/BasicAuthentication)
-    - [Querystring authentication](#section/Authentication/QuerystringAuthentication)
-    <!-- ReDoc-Inject: <security-definitions> -->
-  x-traitTag: true
-- name: Invokable Scripts
-  description: |
-    Manage and execute scripts as API endpoints in InfluxDB.
-
-    An API Invokable Script assigns your custom Flux script to a new InfluxDB API endpoint for your organization.
-    Invokable scripts let you execute your script as an HTTP request to the endpoint.
-
-    Invokable scripts accept parameters. Add parameter references in your script as `params.myparameter`.
-    When you `invoke` your script, you send parameters as key-value pairs in the `params` object.
-    Then, InfluxDB executes your script with the key-value pairs as arguments, and returns the result.
-
-    For more information and examples, see [Invoke custom scripts](https://docs.influxdata.com/influxdb/cloud/api-guide/api-invokable-scripts).
-- name: Quick start
-  x-traitTag: true
-  description: |
-    See the [**API Quick Start**](https://docs.influxdata.com/influxdb/cloud/api-guide/api_intro/) to get up and running authenticating with tokens, writing to buckets, and querying data.
-
-    [**InfluxDB API client libraries**](https://docs.influxdata.com/influxdb/cloud/api-guide/client-libraries/) are available for popular languages and ready to import into your application.
-- name: Response codes
-  x-traitTag: true
-  description: |
-    The InfluxDB API uses standard HTTP status codes for success and failure responses.
-    The response body may include additional details. For details about a specific operation's response, see **Responses** and **Response Samples** for that operation.
-
-    API operations may return the following HTTP status codes:
-
-    | &nbsp;Code&nbsp; | Status                   | Description      |
-    |:-----------:|:------------------------ |:--------------------- |
-    | `200`       | Success                  |                       |
-    | `204`       | No content               | For a `POST` request, `204` indicates that InfluxDB accepted the request and request data is valid. Asynchronous operations, such as `write`, might not have completed yet. |
-    | `400`       | Bad request              | `Authorization` header is missing or malformed or the API token does not have permission for the operation. |
-    | `401`       | Unauthorized             | May indicate one of the following: <li>`Authorization: Token` header is missing or malformed</li><li>API token value is missing from the header</li><li>API token does not have permission. For more information about token types and permissions, see [Manage API tokens](https://docs.influxdata.com/influxdb/cloud/security/tokens/)</li> |
-    | `404`       | Not found                | Requested resource was not found. `message` in the response body provides details about the requested resource. |
-    | `413`       | Request entity too large | Request payload exceeds the size limit. |
-    | `422`       | Unprocessible entity     | Request data is invalid. `code` and `message` in the response body provide details about the problem. |
-    | `429`       | Too many requests        | API token is temporarily over the request quota. The `Retry-After` header describes when to try the request again. |
-    | `500`       | Internal server error    |                       |
-    | `503`       | Service unavailable      | Server is temporarily unavailable to process the request. The `Retry-After` header describes when to try the request again. |
-- name: Query
-  description: |
-    Retrieve data, analyze queries, and get query suggestions.
-- name: Write
-  description: |
-    Write time series data to buckets.
-- name: Authorizations
-  description: |
-    Create and manage API tokens. An **authorization** associates a list of permissions to an **organization** and provides a token for API access. To assign a token to a specific user, scope the authorization to the user ID.
diff --git a/api-docs/openapi/content/content.js b/api-docs/openapi/content/content.js
index f9045476d..131f045a9 100644
--- a/api-docs/openapi/content/content.js
+++ b/api-docs/openapi/content/content.js
@@ -2,18 +2,20 @@ const path = require('path');
 const { toJSON } = require('../plugins/helpers/content-helper');
 
 function getVersion(filename) {
-  return path.join(__dirname, process.env.INFLUXDB_VERSION, (process.env.INFLUXDB_API_VERSION || ''), filename);
+  return path.join(__dirname, process.env.INFLUXDB_VERSION,
+     (process.env.INFLUXDB_API_VERSION || ''), 
+     filename);
 }
 
-const info = toJSON(getVersion('info.yml'));
+const info = () => toJSON(getVersion('info.yml'));
 
-const securitySchemes = toJSON(getVersion('security-schemes.yml'));
+const securitySchemes = () => toJSON(getVersion('security-schemes.yml'));
 
-const servers = toJSON(path.join(__dirname, 'servers.yml'));
+const servers = () => toJSON(path.join(__dirname, 'servers.yml'));
 
-const tags = toJSON(getVersion('tags.yml'));
+const tags = () => toJSON(getVersion('tags.yml'));
 
-const tagGroups = toJSON(getVersion('tag-groups.yml'));
+const tagGroups = () => toJSON(getVersion('tag-groups.yml'));
 
 module.exports = {
   info,
@@ -22,4 +24,3 @@ module.exports = {
   tagGroups,
   tags,
 }
-
diff --git a/api-docs/openapi/content/v2.0/info.yml b/api-docs/openapi/content/v2.0/info.yml
index de7a5cc2c..ece63acba 100644
--- a/api-docs/openapi/content/v2.0/info.yml
+++ b/api-docs/openapi/content/v2.0/info.yml
@@ -1,3 +1,4 @@
 title: InfluxDB OSS API Service
+version: 2.0.0
 description: |
     The InfluxDB v2 API provides a programmatic interface for all interactions with InfluxDB. Access the InfluxDB API using the `/api/v2/` endpoint.
diff --git a/api-docs/openapi/content/v2.0/security-schemes.yml b/api-docs/openapi/content/v2.0/security-schemes.yml
deleted file mode 100644
index bc9504cca..000000000
--- a/api-docs/openapi/content/v2.0/security-schemes.yml
+++ /dev/null
@@ -1,58 +0,0 @@
-TokenAuthentication:
-  type: http
-  scheme: token
-  bearerFormat: InfluxDB Token String
-  description: |
-    ### Token authentication scheme
-
-    InfluxDB API tokens ensure secure interaction between users and data. A token belongs to an organization and identifies InfluxDB permissions within the organization.
-
-    Include your API token in an `Authorization: Token YOUR_API_TOKEN` HTTP header with each request.
-
-    ### Example
-
-      `curl http://localhost:8086/ping
-          --header "Authorization: Token YOUR_API_TOKEN"`
-
-    For more information and examples, see the following:
-      - [Use tokens in API requests](https://docs.influxdata.com/influxdb/v2.0/api-guide/api_intro/#authentication).
-      - [Manage API tokens](https://docs.influxdata.com/influxdb/v2.0/security/tokens).
-      - [`/authorizations`](#tag/Authorizations) endpoint.
-BasicAuthentication:
-  type: http
-  scheme: basic
-  description: |
-    ### Basic authentication scheme
-
-    Use HTTP Basic Auth with clients that support the InfluxDB 1.x convention of username and password (that don't support the `Authorization: Token` scheme).
-
-    Username and password schemes require the following credentials:
-      - **username**: 1.x username (this is separate from the UI login username)
-      - **password**: 1.x password or InfluxDB API token
-
-    ### Example
-
-    `curl --get "http://localhost:8086/query"
-          --user "YOUR_1.x_USERNAME":"YOUR_TOKEN_OR_PASSWORD"`
-
-    For more information and examples, see how to [authenticate with a username and password scheme](https://docs.influxdata.com/influxdb/v2.0/reference/api/influxdb-1x/)
-QuerystringAuthentication:
-  type: apiKey
-  in: query
-  name: u=&p=
-  description: |
-    ### Querystring authentication scheme
-
-    Use InfluxDB 1.x API parameters to provide credentials through the query string.
-
-    Username and password schemes require the following credentials:
-      - **username**: 1.x username (this is separate from the UI login username)
-      - **password**: 1.x password or InfluxDB API token
-
-    ### Example
-
-    `curl --get "http://localhost:8086/query"
-          --data-urlencode "u=YOUR_1.x_USERNAME"
-          --data-urlencode "p=YOUR_TOKEN_OR_PASSWORD"`
-
-    For more information and examples, see how to [authenticate with a username and password scheme](https://docs.influxdata.com/influxdb/v2.0/reference/api/influxdb-1x/)
diff --git a/api-docs/openapi/content/v2.0/tag-groups.yml b/api-docs/openapi/content/v2.0/tag-groups.yml
deleted file mode 100644
index da30ad692..000000000
--- a/api-docs/openapi/content/v2.0/tag-groups.yml
+++ /dev/null
@@ -1,28 +0,0 @@
-- name: Overview
-  tags:
-    - Quick start
-    - Authentication
-    - Response codes
-- name: Data I/O endpoints
-  tags:
-    - Write
-    - Query
-- name: Resource endpoints
-  tags:
-    - Buckets
-    - Dashboards
-    - Tasks
-    - Resources
-- name: Security and access endpoints
-  tags:
-    - Authorizations
-    - Organizations
-    - Users
-- name: System information endpoints
-  tags:
-    - Health
-    - Ping
-    - Ready
-    - Routes
-- name: All endpoints
-  tags: []
diff --git a/api-docs/openapi/content/v2.0/tags.yml b/api-docs/openapi/content/v2.0/tags.yml
deleted file mode 100644
index 80c9055dd..000000000
--- a/api-docs/openapi/content/v2.0/tags.yml
+++ /dev/null
@@ -1,43 +0,0 @@
-- name: Authentication
-  description: |
-    Use one of the following schemes to authenticate to the InfluxDB API:
-    - [Token authentication](#section/Authentication/TokenAuthentication)
-    - [Basic authentication](#section/Authentication/BasicAuthentication)
-    - [Querystring authentication](#section/Authentication/QuerystringAuthentication)
-    <!-- ReDoc-Inject: <security-definitions> -->
-  x-traitTag: true
-- name: Quick start
-  x-traitTag: true
-  description: |
-    See the [**API Quick Start**](https://docs.influxdata.com/influxdb/v2.0/api-guide/api_intro/) to get up and running authenticating with tokens, writing to buckets, and querying data.
-
-    [**InfluxDB API client libraries**](https://docs.influxdata.com/influxdb/v2.0/api-guide/client-libraries/) are available for popular languages and ready to import into your application.
-- name: Response codes
-  x-traitTag: true
-  description: |
-    The InfluxDB API uses standard HTTP status codes for success and failure responses.
-    The response body may include additional details. For details about a specific operation's response, see **Responses** and **Response Samples** for that operation.
-
-    API operations may return the following HTTP status codes:
-
-    | &nbsp;Code&nbsp; | Status                   | Description      |
-    |:-----------:|:------------------------ |:--------------------- |
-    | `200`       | Success                  |                       |
-    | `204`       | No content               | For a `POST` request, `204` indicates that InfluxDB accepted the request and request data is valid. Asynchronous operations, such as `write`, might not have completed yet. |
-    | `400`       | Bad request              | `Authorization` header is missing or malformed or the API token does not have permission for the operation. |
-    | `401`       | Unauthorized             | May indicate one of the following: <li>`Authorization: Token` header is missing or malformed</li><li>API token value is missing from the header</li><li>API token does not have permission. For more information about token types and permissions, see [Manage API tokens](https://docs.influxdata.com/influxdb/v2.0/security/tokens/)</li> |
-    | `404`       | Not found                | Requested resource was not found. `message` in the response body provides details about the requested resource. |
-    | `413`       | Request entity too large | Request payload exceeds the size limit. |
-    | `422`       | Unprocessible entity     | Request data is invalid. `code` and `message` in the response body provide details about the problem. |
-    | `429`       | Too many requests        | API token is temporarily over the request quota. The `Retry-After` header describes when to try the request again. |
-    | `500`       | Internal server error    |                       |
-    | `503`       | Service unavailable      | Server is temporarily unavailable to process the request. The `Retry-After` header describes when to try the request again. |
-- name: Query
-  description: |
-    Retrieve data, analyze queries, and get query suggestions.
-- name: Write
-  description: |
-    Write time series data to buckets.
-- name: Authorizations
-  description: |
-    Create and manage API tokens. An **authorization** associates a list of permissions to an **organization** and provides a token for API access. To assign a token to a specific user, scope the authorization to the user ID.
diff --git a/api-docs/openapi/content/v2.1/info.yml b/api-docs/openapi/content/v2.1/info.yml
index de7a5cc2c..ece63acba 100644
--- a/api-docs/openapi/content/v2.1/info.yml
+++ b/api-docs/openapi/content/v2.1/info.yml
@@ -1,3 +1,4 @@
 title: InfluxDB OSS API Service
+version: 2.0.0
 description: |
     The InfluxDB v2 API provides a programmatic interface for all interactions with InfluxDB. Access the InfluxDB API using the `/api/v2/` endpoint.
diff --git a/api-docs/openapi/content/v2.1/security-schemes.yml b/api-docs/openapi/content/v2.1/security-schemes.yml
deleted file mode 100644
index c12659c01..000000000
--- a/api-docs/openapi/content/v2.1/security-schemes.yml
+++ /dev/null
@@ -1,58 +0,0 @@
-TokenAuthentication:
-  type: http
-  scheme: token
-  bearerFormat: InfluxDB Token String
-  description: |
-    ### Token authentication scheme
-
-    InfluxDB API tokens ensure secure interaction between users and data. A token belongs to an organization and identifies InfluxDB permissions within the organization.
-
-    Include your API token in an `Authentication: Token YOUR_API_TOKEN` HTTP header with each request.
-
-    ### Example
-
-      `curl http://localhost:8086/ping
-          --header "Authentication: Token YOUR_API_TOKEN"`
-
-    For more information and examples, see the following:
-      - [Use tokens in API requests](https://docs.influxdata.com/influxdb/v2.1/api-guide/api_intro/#authentication).
-      - [Manage API tokens](https://docs.influxdata.com/influxdb/v2.1/security/tokens).
-      - [`/authorizations`](#tag/Authorizations) endpoint.
-BasicAuthentication:
-  type: http
-  scheme: basic
-  description: |
-    ### Basic authentication scheme
-
-    Use HTTP Basic Auth with clients that support the InfluxDB 1.x convention of username and password (that don't support the `Authorization: Token` scheme).
-
-    Username and password schemes require the following credentials:
-      - **username**: 1.x username (this is separate from the UI login username)
-      - **password**: 1.x password or InfluxDB API token
-
-    ### Example
-
-    `curl --get "http://localhost:8086/query"
-          --user "YOUR_1.x_USERNAME":"YOUR_TOKEN_OR_PASSWORD"`
-
-    For more information and examples, see how to [authenticate with a username and password scheme](https://docs.influxdata.com/influxdb/v2.1/reference/api/influxdb-1x/)
-QuerystringAuthentication:
-  type: apiKey
-  in: query
-  name: u=&p=
-  description: |
-    ### Querystring authentication scheme
-
-    Use InfluxDB 1.x API parameters to provide credentials through the query string.
-
-    Username and password schemes require the following credentials:
-      - **username**: 1.x username (this is separate from the UI login username)
-      - **password**: 1.x password or InfluxDB API token
-
-    ### Example
-
-    `curl --get "http://localhost:8086/query"
-          --data-urlencode "u=YOUR_1.x_USERNAME"
-          --data-urlencode "p=YOUR_TOKEN_OR_PASSWORD"`
-
-    For more information and examples, see how to [authenticate with a username and password scheme](https://docs.influxdata.com/influxdb/v2.1/reference/api/influxdb-1x/)
diff --git a/api-docs/openapi/content/v2.1/tag-groups.yml b/api-docs/openapi/content/v2.1/tag-groups.yml
deleted file mode 100644
index da30ad692..000000000
--- a/api-docs/openapi/content/v2.1/tag-groups.yml
+++ /dev/null
@@ -1,28 +0,0 @@
-- name: Overview
-  tags:
-    - Quick start
-    - Authentication
-    - Response codes
-- name: Data I/O endpoints
-  tags:
-    - Write
-    - Query
-- name: Resource endpoints
-  tags:
-    - Buckets
-    - Dashboards
-    - Tasks
-    - Resources
-- name: Security and access endpoints
-  tags:
-    - Authorizations
-    - Organizations
-    - Users
-- name: System information endpoints
-  tags:
-    - Health
-    - Ping
-    - Ready
-    - Routes
-- name: All endpoints
-  tags: []
diff --git a/api-docs/openapi/content/v2.1/tags.yml b/api-docs/openapi/content/v2.1/tags.yml
deleted file mode 100644
index 7659f4e77..000000000
--- a/api-docs/openapi/content/v2.1/tags.yml
+++ /dev/null
@@ -1,43 +0,0 @@
-- name: Authentication
-  description: |
-    Use one of the following schemes to authenticate to the InfluxDB API:
-    - [Token authentication](#section/Authentication/TokenAuthentication)
-    - [Basic authentication](#section/Authentication/BasicAuthentication)
-    - [Querystring authentication](#section/Authentication/QuerystringAuthentication)
-    <!-- ReDoc-Inject: <security-definitions> -->
-  x-traitTag: true
-- name: Quick start
-  x-traitTag: true
-  description: |
-    See the [**API Quick Start**](https://docs.influxdata.com/influxdb/v2.1/api-guide/api_intro/) to get up and running authenticating with tokens, writing to buckets, and querying data.
-
-    [**InfluxDB API client libraries**](https://docs.influxdata.com/influxdb/v2.1/api-guide/client-libraries/) are available for popular languages and ready to import into your application.
-- name: Response codes
-  x-traitTag: true
-  description: |
-    The InfluxDB API uses standard HTTP status codes for success and failure responses.
-    The response body may include additional details. For details about a specific operation's response, see **Responses** and **Response Samples** for that operation.
-
-    API operations may return the following HTTP status codes:
-
-    | &nbsp;Code&nbsp; | Status                   | Description      |
-    |:-----------:|:------------------------ |:--------------------- |
-    | `200`       | Success                  |                       |
-    | `204`       | No content               | For a `POST` request, `204` indicates that InfluxDB accepted the request and request data is valid. Asynchronous operations, such as `write`, might not have completed yet. |
-    | `400`       | Bad request              | `Authorization` header is missing or malformed or the API token does not have permission for the operation. |
-    | `401`       | Unauthorized             | May indicate one of the following: <li>`Authorization: Token` header is missing or malformed</li><li>API token value is missing from the header</li><li>API token does not have permission. For more information about token types and permissions, see [Manage API tokens](https://docs.influxdata.com/influxdb/v2.1/security/tokens/)</li> |
-    | `404`       | Not found                | Requested resource was not found. `message` in the response body provides details about the requested resource. |
-    | `413`       | Request entity too large | Request payload exceeds the size limit. |
-    | `422`       | Unprocessible entity     | Request data is invalid. `code` and `message` in the response body provide details about the problem. |
-    | `429`       | Too many requests        | API token is temporarily over the request quota. The `Retry-After` header describes when to try the request again. |
-    | `500`       | Internal server error    |                       |
-    | `503`       | Service unavailable      | Server is temporarily unavailable to process the request. The `Retry-After` header describes when to try the request again. |
-- name: Query
-  description: |
-    Retrieve data, analyze queries, and get query suggestions.
-- name: Write
-  description: |
-    Write time series data to buckets.
-- name: Authorizations
-  description: |
-    Create and manage API tokens. An **authorization** associates a list of permissions to an **organization** and provides a token for API access. To assign a token to a specific user, scope the authorization to the user ID.
diff --git a/api-docs/openapi/content/v2.2/info.yml b/api-docs/openapi/content/v2.2/info.yml
new file mode 100644
index 000000000..ece63acba
--- /dev/null
+++ b/api-docs/openapi/content/v2.2/info.yml
@@ -0,0 +1,4 @@
+title: InfluxDB OSS API Service
+version: 2.0.0
+description: |
+    The InfluxDB v2 API provides a programmatic interface for all interactions with InfluxDB. Access the InfluxDB API using the `/api/v2/` endpoint.
diff --git a/api-docs/openapi/content/v2.2/v1compat/info.yml b/api-docs/openapi/content/v2.2/v1compat/info.yml
new file mode 100644
index 000000000..3ef1f3cda
--- /dev/null
+++ b/api-docs/openapi/content/v2.2/v1compat/info.yml
@@ -0,0 +1 @@
+title: InfluxDB OSS v1 compatibility API documentation
diff --git a/api-docs/openapi/content/v2.2/v1compat/tag-groups.yml b/api-docs/openapi/content/v2.2/v1compat/tag-groups.yml
new file mode 100644
index 000000000..22cf0f916
--- /dev/null
+++ b/api-docs/openapi/content/v2.2/v1compat/tag-groups.yml
@@ -0,0 +1,9 @@
+- name: Overview
+  tags:
+    - Authentication
+- name: Data I/O endpoints
+  tags:
+    - Write
+    - Query
+- name: All endpoints
+  tags: []
diff --git a/api-docs/openapi/plugins/decorators/paths/strip-trailing-slash.js b/api-docs/openapi/plugins/decorators/paths/strip-trailing-slash.js
new file mode 100644
index 000000000..cc9bdad3f
--- /dev/null
+++ b/api-docs/openapi/plugins/decorators/paths/strip-trailing-slash.js
@@ -0,0 +1,18 @@
+module.exports = StripVersionPrefix;
+
+/** @type {import('@redocly/openapi-cli').OasDecorator} */
+function StripVersionPrefix() {
+  return {
+    PathMap: {
+      leave(paths, ctx) {
+        Object.keys(paths).forEach(function(p) {
+          if(p.length > 1 && p.endsWith('/')) {
+            const props = JSON.stringify(paths[p]);
+            paths[p.slice(0, -1)] = JSON.parse(props);
+            delete paths[p];
+          }
+        });
+      }
+    }
+  }
+}
\ No newline at end of file
diff --git a/api-docs/openapi/plugins/decorators/paths/strip-version-prefix.js b/api-docs/openapi/plugins/decorators/paths/strip-version-prefix.js
index 407893f98..77ca0b6d7 100644
--- a/api-docs/openapi/plugins/decorators/paths/strip-version-prefix.js
+++ b/api-docs/openapi/plugins/decorators/paths/strip-version-prefix.js
@@ -6,6 +6,7 @@ function StripVersionPrefix() {
     PathMap: {
       leave(paths, ctx) {
         const nonversioned = [
+          '/debug',
           '/health',
           '/legacy/authorizations',
           '/legacy/authorizations/{authID}',
diff --git a/api-docs/openapi/plugins/decorators/replace-shortcodes.js b/api-docs/openapi/plugins/decorators/replace-shortcodes.js
index 9591431f2..586d147b5 100644
--- a/api-docs/openapi/plugins/decorators/replace-shortcodes.js
+++ b/api-docs/openapi/plugins/decorators/replace-shortcodes.js
@@ -1,37 +1,41 @@
 module.exports = ReplaceShortcodes;
 
-function replaceDocsUrl(node) {
-  const shortcode = /\{\{\% INFLUXDB_DOCS_URL \%\}\}/g;
+function replaceDocsUrl(field) {
+  if(!field) { return }
+  const shortcode = '{{% INFLUXDB_DOCS_URL %}}';
   let replacement = `/influxdb/${process.env.INFLUXDB_VERSION}`;
-  let description = node.description?.replace(shortcode, replacement);
-  const fullUrl = /https:\/\/docs\.influxdata\.com\/influxdb\//g;
+  let replaced = field.replaceAll(shortcode, replacement);
+  const fullUrl = 'https://docs.influxdata.com/influxdb/';
   replacement = "/influxdb/";
-  return description?.replace(fullUrl, replacement);
+  return replaced.replaceAll(fullUrl, replacement);
 }
 
 /** @type {import('@redocly/openapi-cli').OasDecorator} */
 function docsUrl() {
   return {
-    Info: {
-      leave(info, ctx) {
-        info.description = replaceDocsUrl(info);
-      }
-    },
-    PathItem: {
-      leave(pathItem, ctx) {
-        pathItem.description = replaceDocsUrl(pathItem);
-      }
-    },
-    Tag: {
-      leave(tag, ctx) {
-        tag.description = replaceDocsUrl(tag);
-      }
-    },
-    SecurityScheme: {
-      leave(scheme, ctx) {
-        scheme.description = replaceDocsUrl(scheme);
+    DefinitionRoot: {
+      Info: {
+        leave(info, ctx) {
+          info.description = replaceDocsUrl(info.description);
+        },
+      },
+      PathItem: {
+        leave(pathItem, ctx) {
+          pathItem.description = replaceDocsUrl(pathItem.description);
+        }
+      },
+      Tag: {
+        leave(tag, ctx) {
+            tag.description = replaceDocsUrl(tag.description);
+          }
+        },
+      SecurityScheme: {
+        leave(scheme, ctx) {
+            scheme.description = replaceDocsUrl(scheme.description);
+        }
       }
     }
+
   }
 }
 
diff --git a/api-docs/openapi/plugins/decorators/security/set-security-schemes.js b/api-docs/openapi/plugins/decorators/security/set-security-schemes.js
deleted file mode 100644
index 78e2b362d..000000000
--- a/api-docs/openapi/plugins/decorators/security/set-security-schemes.js
+++ /dev/null
@@ -1,18 +0,0 @@
-module.exports = SetSecuritySchemes;
-
-/** @type {import('@redocly/openapi-cli').OasDecorator} */
-function SetSecuritySchemes(options) {
-  return {
-    Components: {
-      leave(comps, ctx) {
-	if(options.data) {
-	  comps.securitySchemes = comps.securitySchemes || {};
-	  Object.keys(options.data).forEach(
-	    function(scheme) {
-              comps.securitySchemes[scheme] = options.data[scheme];
-            })
-	}
-      }
-    }
-  }
-}
diff --git a/api-docs/openapi/plugins/decorators/servers/delete-servers.js b/api-docs/openapi/plugins/decorators/servers/delete-servers.js
new file mode 100644
index 000000000..563d22d2f
--- /dev/null
+++ b/api-docs/openapi/plugins/decorators/servers/delete-servers.js
@@ -0,0 +1,21 @@
+module.exports = DeleteServers;
+
+/** @type {import('@redocly/openapi-cli').OasDecorator} */
+
+/**
+ * Returns an object with keys in [node type, any, ref].
+ * The key instructs openapi when to invoke the key's Visitor object.
+ * Object key "Server" is an OAS 3.0 node type.
+ */
+function DeleteServers() {
+  return {
+    Operation: {
+      leave(op) {
+        /** Delete servers with empty url. **/
+        if(Array.isArray(op.servers)) {
+          op.servers = op.servers.filter(server => server.url);
+        }
+      }
+    }
+  }
+};
diff --git a/api-docs/openapi/plugins/decorators/servers/set-servers.js b/api-docs/openapi/plugins/decorators/servers/set-servers.js
index 27f988793..ae2c5a162 100644
--- a/api-docs/openapi/plugins/decorators/servers/set-servers.js
+++ b/api-docs/openapi/plugins/decorators/servers/set-servers.js
@@ -1,17 +1,20 @@
 module.exports = SetServers;
 
+const { servers } = require('../../../content/content')
+
 /** @type {import('@redocly/openapi-cli').OasDecorator} */
 
 /**
  * Returns an object with keys in [node type, any, ref].
- * The key instructs openapi when to invoke the key's Visitor object. 
+ * The key instructs openapi when to invoke the key's Visitor object.
  * Object key "Server" is an OAS 3.0 node type.
  */
-function SetServers(options) {
+function SetServers() {
+  const data = servers();
   return {
     DefinitionRoot: {
       leave(root) {
-        root.servers = options.data;
+        root.servers = data;
       }
     },
   }
diff --git a/api-docs/openapi/plugins/decorators/set-info.js b/api-docs/openapi/plugins/decorators/set-info.js
index 8ec217a36..5efda6491 100644
--- a/api-docs/openapi/plugins/decorators/set-info.js
+++ b/api-docs/openapi/plugins/decorators/set-info.js
@@ -1,16 +1,24 @@
 module.exports = SetInfo;
 
+const { info } = require('../../content/content')
+
 /** @type {import('@redocly/openapi-cli').OasDecorator} */
-function SetInfo(options) {
+function SetInfo() {
+  const data = info();
+
   return {
     Info: {
       leave(info, ctx) {
-        if(options.data) {
-          if(options.data.hasOwnProperty('title')) {
-             info.title =  options.data.title;
+        if(data) {
+          if(data.hasOwnProperty('title')) {
+             info.title =  data.title;
           }
-	        if(options.data.hasOwnProperty('description')) {
-             info.description = options.data.description;
+	        if(data.hasOwnProperty('version')) {
+
+             info.version = data.version;
+          }
+          if(data.hasOwnProperty('description')) {
+             info.description = data.description;
           }
 	      }
       }
diff --git a/api-docs/openapi/plugins/decorators/tags/set-tag-groups.js b/api-docs/openapi/plugins/decorators/tags/set-tag-groups.js
index 3a0d84a9c..91fac505f 100644
--- a/api-docs/openapi/plugins/decorators/tags/set-tag-groups.js
+++ b/api-docs/openapi/plugins/decorators/tags/set-tag-groups.js
@@ -1,43 +1,60 @@
 module.exports = SetTagGroups;
 
+const { tagGroups } = require('../../../content/content')
 const { collect, getName, sortName } = require('../../helpers/content-helper.js')
 /**
  * Returns an object that defines handler functions for:
  * - Operation nodes
  * - DefinitionRoot (the root openapi) node
  * The order of the two functions is significant.
- * The Operation handler collects tags from the 
+ * The Operation handler collects tags from the
  * operation ('get', 'post', etc.) in every path.
  * The DefinitionRoot handler, executed when
  * the parser is leaving the root node,
- * sets `x-tagGroups` to the provided `data`
+ * adds custom `tagGroups` content to `x-tagGroups`
  * and sets the value of `All Endpoints` to the collected tags.
  */
 /** @type {import('@redocly/openapi-cli').OasDecorator} */
-function SetTagGroups(options) {
+function SetTagGroups() {
+  let data = tagGroups();
+  if(!Array.isArray(data)) {
+    data = [];
+  }
+
   let tags = [];
+  /** Collect tags for each operation and convert string tags to object tags. **/
   return {
-    Operation: {
-      leave(op, ctx, parents) {
-        tags = collect(tags, op.tags);
-      }
-    },
     DefinitionRoot: {
+      Operation: {
+        leave(op) {
+          let opTags = op.tags?.map(
+            function(t) {
+              return typeof t === 'string' ? { name: t } : t;
+            }
+          ) || [];
+          tags = collect(tags, opTags);
+        }
+      },
       leave(root) {
-	root.tags = root.tags || [];
-	root.tags = collect(root.tags, tags)
-	  .sort((a, b) => sortName(a, b));
+        root.tags = root.tags || [];
+        root.tags = collect(root.tags, tags)
+          .sort((a, b) => sortName(a, b));
 
-	if(!options.data) { return; }
+        endpointTags = root.tags
+          .filter(t => !t['x-traitTag'])
+          .map(t => getName(t));
 
-	endpointTags = root.tags
-	  .filter(t => !t['x-traitTag'])
-	  .map(t => getName(t));
-	root['x-tagGroups'] = options.data
-	  .map(function(grp) {
-	    grp.tags = grp.name === 'All endpoints' ? endpointTags : grp.tags;
-	    return grp;
-	  });
+        if(Array.isArray(root['x-tagGroups'])) {
+          root['x-tagGroups'].concat(data);
+        } else {
+          root['x-tagGroups'] = data;
+        }
+
+        root['x-tagGroups'].map(
+          function(grp) {
+            grp.tags = grp.name === 'All endpoints' ? endpointTags : grp.tags;
+            return grp;
+          });
       }
     }
   }
diff --git a/api-docs/openapi/plugins/decorators/tags/set-tags.js b/api-docs/openapi/plugins/decorators/tags/set-tags.js
index de9eef03a..7369eeea6 100644
--- a/api-docs/openapi/plugins/decorators/tags/set-tags.js
+++ b/api-docs/openapi/plugins/decorators/tags/set-tags.js
@@ -1,21 +1,24 @@
 module.exports = SetTags;
 
+const { tags } = require('../../../content/content')
 /**
  * Returns an object that defines handler functions for:
  * - DefinitionRoot (the root openapi) node
  * The DefinitionRoot handler, executed when
  * the parser is leaving the root node,
- * sets the root `tags` list to the provided `data`. 
+ * sets the root `tags` list to the provided `data`.
  */
 /** @type {import('@redocly/openapi-cli').OasDecorator} */
-function SetTags(options) {
-  let tags = [];
+function SetTags() {
+  const data = tags();
+
   return {
     DefinitionRoot: {
-      leave(root) {
-	if(options.data) {
-          root.tags = options.data;
-	}
+      /** Set tags from custom tags when visitor enters root. */
+      enter(root) {
+	      if(data) {
+          root.tags = data;
+      	}
       }
     }
   }
diff --git a/api-docs/openapi/plugins/docs-plugin.js b/api-docs/openapi/plugins/docs-plugin.js
index cfa1113c7..8d2ed8275 100644
--- a/api-docs/openapi/plugins/docs-plugin.js
+++ b/api-docs/openapi/plugins/docs-plugin.js
@@ -3,12 +3,11 @@ const ValidateServersUrl = require('./rules/validate-servers-url');
 const RemovePrivatePaths = require('./decorators/paths/remove-private-paths');
 const ReplaceShortcodes = require('./decorators/replace-shortcodes');
 const SetInfo = require('./decorators/set-info');
+const DeleteServers = require('./decorators/servers/delete-servers');
 const SetServers = require('./decorators/servers/set-servers');
-const SetSecuritySchemes = require('./decorators/security/set-security-schemes');
-const SetTags = require('./decorators/tags/set-tags');
 const SetTagGroups = require('./decorators/tags/set-tag-groups');
 const StripVersionPrefix = require('./decorators/paths/strip-version-prefix');
-const {info, securitySchemes, servers, tags, tagGroups } = require('../content/content')
+const StripTrailingSlash = require('./decorators/paths/strip-trailing-slash');
 
 const id = 'docs';
 
@@ -23,15 +22,14 @@ const rules = {
 /** @type {import('@redocly/openapi-cli').CustomRulesConfig} */
 const decorators = {
   oas3: {
-    'set-servers': () => SetServers({data: servers}),
+    'set-servers': SetServers,
+    'delete-servers': DeleteServers,
     'remove-private-paths': RemovePrivatePaths,
-    'replace-docs-url-shortcode': ReplaceShortcodes().docsUrl,
     'strip-version-prefix': StripVersionPrefix,
-    'set-info': () => SetInfo({data: info}),
-    'set-security': () => SetSecurity({data: security}),
-    'set-security-schemes': () => SetSecuritySchemes({data: securitySchemes}),
-    'set-tags': () => SetTags({data: tags}),
-    'set-tag-groups': () => SetTagGroups({data: tagGroups}),
+    'strip-trailing-slash': StripTrailingSlash,
+    'set-info': SetInfo,
+    'set-tag-groups': SetTagGroups,
+    'replace-docs-url-shortcode': ReplaceShortcodes().docsUrl,
   }
 };
 
@@ -40,16 +38,18 @@ module.exports = {
   configs: {
     all: {
       rules: {
-	'no-server-trailing-slash': 'off',
+      	'no-server-trailing-slash': 'off',
         'docs/validate-servers-url': 'error',
       },
       decorators: {
         'docs/set-servers': 'error',
-	'docs/remove-private-paths': 'error',
-	'docs/replace-docs-url-shortcode': 'error',
-	'docs/strip-version-prefix': 'error',
-	'docs/set-info': 'error',
-	'docs/set-tag-groups': 'error',
+        'docs/delete-servers': 'error',
+      	'docs/remove-private-paths': 'error',
+      	'docs/strip-version-prefix': 'error',
+        'docs/strip-trailing-slash': 'error',
+      	'docs/set-info': 'error',
+      	'docs/set-tag-groups': 'error',
+        'docs/replace-docs-url-shortcode': 'error',
       },
     },
   },
diff --git a/api-docs/v2.0/ref.yml b/api-docs/v2.0/ref.yml
index ad502060b..fa6f30576 100644
--- a/api-docs/v2.0/ref.yml
+++ b/api-docs/v2.0/ref.yml
@@ -3188,7 +3188,7 @@ components:
     Ready:
       properties:
         started:
-          example: 2019-03-13T10:09:33.891196-04:00
+          example: '2019-03-13T10:09:33.891196-04:00'
           format: date-time
           type: string
         status:
diff --git a/api-docs/v2.1/ref.yml b/api-docs/v2.1/ref.yml
index 3e83b7739..0b35456e4 100644
--- a/api-docs/v2.1/ref.yml
+++ b/api-docs/v2.1/ref.yml
@@ -2,8 +2,8 @@ components:
   parameters:
     After:
       description: >
-        The last resource ID from which to seek from (but not including). This
-        is to be used instead of `offset`.
+        Resource ID to seek from. Results are not inclusive of this ID. Use
+        `after` instead of `offset`.
       in: query
       name: after
       required: false
@@ -125,24 +125,22 @@ components:
               readOnly: true
               type: object
             org:
-              description: Name of the org token is scoped to.
+              description: Name of the organization that the token is scoped to.
               readOnly: true
               type: string
             orgID:
-              description: ID of org that authorization is scoped to.
+              description: ID of the organization that the authorization is scoped to.
               type: string
             permissions:
               description: >-
-                List of permissions for an auth.  An auth must have at least one
-                Permission.
+                List of permissions for an authorization.  An authorization must
+                have at least one permission.
               items:
                 $ref: '#/components/schemas/Permission'
               minItems: 1
               type: array
             token:
-              description: >-
-                Passed via the Authorization Header and Token Authentication
-                type.
+              description: Token used to authenticate API requests.
               readOnly: true
               type: string
             updatedAt:
@@ -150,11 +148,11 @@ components:
               readOnly: true
               type: string
             user:
-              description: Name of user that created and owns the token.
+              description: Name of the user that created and owns the token.
               readOnly: true
               type: string
             userID:
-              description: ID of user that created and owns the token.
+              description: ID of the user that created and owns the token.
               readOnly: true
               type: string
           type: object
@@ -191,8 +189,8 @@ components:
         status:
           default: active
           description: >-
-            If inactive the token is inactive and requests using the token will
-            be rejected.
+            Status of the token. If `inactive`, requests using the token will be
+            rejected.
           enum:
             - active
             - inactive
@@ -219,10 +217,10 @@ components:
         - 'y'
       type: object
     Axis:
-      description: The description of a particular axis for a visualization.
+      description: Axis used in a visualization.
       properties:
         base:
-          description: Base represents the radix for formatting axis values.
+          description: Radix for formatting axis values.
           enum:
             - ''
             - '2'
@@ -230,23 +228,23 @@ components:
           type: string
         bounds:
           description: >-
-            The extents of an axis in the form [lower, upper]. Clients determine
-            whether bounds are to be inclusive or exclusive of their limits
+            The extents of the axis in the form [lower, upper]. Clients
+            determine whether bounds are inclusive or exclusive of their limits.
           items:
             type: string
           maxItems: 2
           minItems: 0
           type: array
         label:
-          description: Label is a description of this Axis
+          description: Description of the axis.
           type: string
         prefix:
-          description: Prefix represents a label prefix for formatting axis values.
+          description: Label prefix for formatting axis values.
           type: string
         scale:
           $ref: '#/components/schemas/AxisScale'
         suffix:
-          description: Suffix represents a label suffix for formatting axis values.
+          description: Label suffix for formatting axis values.
           type: string
       type: object
     AxisScale:
@@ -413,22 +411,22 @@ components:
           properties:
             labels:
               $ref: '#/components/schemas/Link'
-              description: URL to retrieve labels for this bucket
+              description: URL to retrieve labels for this bucket.
             members:
               $ref: '#/components/schemas/Link'
-              description: URL to retrieve members that can read this bucket
+              description: URL to retrieve members that can read this bucket.
             org:
               $ref: '#/components/schemas/Link'
-              description: URL to retrieve parent organization for this bucket
+              description: URL to retrieve parent organization for this bucket.
             owners:
               $ref: '#/components/schemas/Link'
               description: URL to retrieve owners that can read and write to this bucket.
             self:
               $ref: '#/components/schemas/Link'
-              description: URL for this bucket
+              description: URL for this bucket.
             write:
               $ref: '#/components/schemas/Link'
-              description: URL to write line protocol for this bucket
+              description: URL to write line protocol to this bucket.
           readOnly: true
           type: object
         name:
@@ -662,10 +660,12 @@ components:
           readOnly: true
           type: string
         latestCompleted:
-          description: Timestamp of latest scheduled, completed run, RFC3339.
+          description: >-
+            Timestamp (in RFC3339 date/time
+            format](https://datatracker.ietf.org/doc/html/rfc3339)) of the
+            latest scheduled and completed run.
           format: date-time
           readOnly: true
-          type: string
         links:
           example:
             labels: /api/v2/checks/1/labels
@@ -821,6 +821,11 @@ components:
         type:
           $ref: '#/components/schemas/NodeType'
       type: object
+    Config:
+      properties:
+        config:
+          type: object
+      type: object
     ConstantVariableProperties:
       properties:
         type:
@@ -879,24 +884,24 @@ components:
     DBRP:
       properties:
         bucketID:
-          description: the bucket ID used as target for the translation.
+          description: ID of the bucket used as the target for the translation.
           type: string
         database:
           description: InfluxDB v1 database
           type: string
         default:
           description: >-
-            Specify if this mapping represents the default retention policy for
-            the database specificed.
+            Mapping represents the default retention policy for the database
+            specified.
           type: boolean
         id:
-          description: the mapping identifier
+          description: ID of the DBRP mapping.
           readOnly: true
           type: string
         links:
           $ref: '#/components/schemas/Links'
         orgID:
-          description: the organization ID that owns this mapping.
+          description: ID of the organization that owns this mapping.
           type: string
         retention_policy:
           description: InfluxDB v1 retention policy
@@ -912,21 +917,21 @@ components:
     DBRPCreate:
       properties:
         bucketID:
-          description: the bucket ID used as target for the translation.
+          description: ID of the bucket used as the target for the translation.
           type: string
         database:
           description: InfluxDB v1 database
           type: string
         default:
           description: >-
-            Specify if this mapping represents the default retention policy for
-            the database specificed.
+            Mapping represents the default retention policy for the database
+            specified.
           type: boolean
         org:
-          description: the organization that owns this mapping.
+          description: Name of the organization that owns this mapping.
           type: string
         orgID:
-          description: the organization ID that owns this mapping.
+          description: ID of the organization that owns this mapping.
           type: string
         retention_policy:
           description: InfluxDB v1 retention policy
@@ -1292,23 +1297,22 @@ components:
           type: string
         err:
           description: >-
-            err is a stack of errors that occurred during processing of the
-            request. Useful for debugging.
+            Stack of errors that occurred during processing of the request.
+            Useful for debugging.
           readOnly: true
           type: string
         message:
-          description: message is a human-readable message.
+          description: Human-readable message.
           readOnly: true
           type: string
         op:
           description: >-
-            op describes the logical code operation during error. Useful for
-            debugging.
+            Describes the logical code operation when the error occurred. Useful
+            for debugging.
           readOnly: true
           type: string
       required:
         - code
-        - message
     Expression:
       oneOf:
         - $ref: '#/components/schemas/ArrayExpression'
@@ -2275,30 +2279,27 @@ components:
           type: string
         err:
           description: >-
-            Err is a stack of errors that occurred during processing of the
-            request. Useful for debugging.
+            Stack of errors that occurred during processing of the request.
+            Useful for debugging.
           readOnly: true
           type: string
         line:
-          description: First line within sent body containing malformed data
+          description: First line in the request body that contains malformed data.
           format: int32
           readOnly: true
           type: integer
         message:
-          description: Message is a human-readable message.
+          description: Human-readable message.
           readOnly: true
           type: string
         op:
           description: >-
-            Op describes the logical code operation during error. Useful for
-            debugging.
+            Describes the logical code operation when the error occurred. Useful
+            for debugging.
           readOnly: true
           type: string
       required:
         - code
-        - message
-        - op
-        - err
     LineProtocolLengthError:
       properties:
         code:
@@ -2308,7 +2309,7 @@ components:
           readOnly: true
           type: string
         message:
-          description: Message is a human-readable message.
+          description: Human-readable message.
           readOnly: true
           type: string
       required:
@@ -2682,7 +2683,10 @@ components:
           readOnly: true
           type: string
         latestCompleted:
-          description: Timestamp of latest scheduled, completed run, RFC3339.
+          description: >-
+            Timestamp (in RFC3339 date/time
+            format](https://datatracker.ietf.org/doc/html/rfc3339)) of the
+            latest scheduled and completed run.
           format: date-time
           readOnly: true
           type: string
@@ -3195,7 +3199,7 @@ components:
     Ready:
       properties:
         started:
-          example: 2019-03-13T10:09:33.891196-04:00
+          example: '2019-03-13T10:09:33.891196-04:00'
           format: date-time
           type: string
         status:
@@ -3216,6 +3220,82 @@ components:
         value:
           type: string
       type: object
+    RemoteConnection:
+      properties:
+        allowInsecureTLS:
+          default: false
+          type: boolean
+        description:
+          type: string
+        id:
+          type: string
+        name:
+          type: string
+        orgID:
+          type: string
+        remoteOrgID:
+          type: string
+        remoteURL:
+          format: uri
+          type: string
+      required:
+        - id
+        - name
+        - orgID
+        - remoteURL
+        - remoteOrgID
+        - allowInsecureTLS
+      type: object
+    RemoteConnectionCreationRequest:
+      properties:
+        allowInsecureTLS:
+          default: false
+          type: boolean
+        description:
+          type: string
+        name:
+          type: string
+        orgID:
+          type: string
+        remoteAPIToken:
+          type: string
+        remoteOrgID:
+          type: string
+        remoteURL:
+          format: uri
+          type: string
+      required:
+        - name
+        - orgID
+        - remoteURL
+        - remoteAPIToken
+        - remoteOrgID
+        - allowInsecureTLS
+      type: object
+    RemoteConnectionUpdateRequest:
+      properties:
+        allowInsecureTLS:
+          default: false
+          type: boolean
+        description:
+          type: string
+        name:
+          type: string
+        remoteAPIToken:
+          type: string
+        remoteOrgID:
+          type: string
+        remoteURL:
+          format: uri
+          type: string
+      type: object
+    RemoteConnections:
+      properties:
+        remotes:
+          items:
+            $ref: '#/components/schemas/RemoteConnection'
+          type: array
+      type: object
     RenamableField:
       description: Describes a field that can be renamed and made visible or invisible.
       properties:
@@ -3230,6 +3310,98 @@ components:
           description: Indicates whether this field should be visible on the table.
           type: boolean
       type: object
+    Replication:
+      properties:
+        currentQueueSizeBytes:
+          format: int64
+          type: integer
+        description:
+          type: string
+        dropNonRetryableData:
+          type: boolean
+        id:
+          type: string
+        latestErrorMessage:
+          type: string
+        latestResponseCode:
+          type: integer
+        localBucketID:
+          type: string
+        maxQueueSizeBytes:
+          format: int64
+          type: integer
+        name:
+          type: string
+        orgID:
+          type: string
+        remoteBucketID:
+          type: string
+        remoteID:
+          type: string
+      required:
+        - id
+        - name
+        - remoteID
+        - orgID
+        - localBucketID
+        - remoteBucketID
+        - maxQueueSizeBytes
+        - currentQueueSizeBytes
+      type: object
+    ReplicationCreationRequest:
+      properties:
+        description:
+          type: string
+        dropNonRetryableData:
+          default: false
+          type: boolean
+        localBucketID:
+          type: string
+        maxQueueSizeBytes:
+          default: 67108860
+          format: int64
+          minimum: 33554430
+          type: integer
+        name:
+          type: string
+        orgID:
+          type: string
+        remoteBucketID:
+          type: string
+        remoteID:
+          type: string
+      required:
+        - name
+        - orgID
+        - remoteID
+        - localBucketID
+        - remoteBucketID
+        - maxQueueSizeBytes
+      type: object
+    ReplicationUpdateRequest:
+      properties:
+        description:
+          type: string
+        dropNonRetryableData:
+          type: boolean
+        maxQueueSizeBytes:
+          format: int64
+          minimum: 33554430
+          type: integer
+        name:
+          type: string
+        remoteBucketID:
+          type: string
+        remoteID:
+          type: string
+      type: object
+    Replications:
+      properties:
+        replications:
+          items:
+            $ref: '#/components/schemas/Replication'
+          type: array
+      type: object
     Resource:
       properties:
         id:
@@ -4257,8 +4429,8 @@ components:
       properties:
         authorizationID:
           description: >-
-            The ID of the authorization used when this task communicates with
-            the query engine.
+            ID of the authorization used when the task communicates with the
+            query engine.
           type: string
         createdAt:
           format: date-time
@@ -4266,17 +4438,27 @@ components:
           type: string
         cron:
           description: >-
-            A task repetition schedule in the form '* * * * * *'; parsed from
-            Flux.
+            [Cron expression](https://en.wikipedia.org/wiki/Cron#Overview) that
+            defines the schedule on which the task runs. Cron scheduling is
+            based on system time.
+
+            Value is a [Cron
+            expression](https://en.wikipedia.org/wiki/Cron#Overview).
           type: string
         description:
-          description: An optional description of the task.
+          description: Description of the task.
           type: string
         every:
-          description: A simple task repetition schedule; parsed from Flux.
+          description: >-
+            Interval at which the task runs. `every` also determines when the
+            task first runs, depending on the specified time.
+
+            Value is a [duration
+            literal](https://docs.influxdata.com/flux/v0.x/spec/lexical-elements/#duration-literals)).
+          format: duration
           type: string
         flux:
-          description: The Flux script to run for this task.
+          description: Flux script to run for this task.
           type: string
         id:
           readOnly: true
@@ -4294,7 +4476,11 @@ components:
           readOnly: true
           type: string
         latestCompleted:
-          description: Timestamp of latest scheduled, completed run, RFC3339.
+          description: >-
+            Timestamp of the latest scheduled and completed run.
+
+            Value is a timestamp in [RFC3339 date/time
+            format](https://docs.influxdata.com/flux/v0.x/data-types/basic/time/#time-syntax).
           format: date-time
           readOnly: true
           type: string
@@ -4322,29 +4508,31 @@ components:
           readOnly: true
           type: object
         name:
-          description: The name of the task.
+          description: Name of the task.
           type: string
         offset:
           description: >-
-            Duration to delay after the schedule, before executing the task;
-            parsed from flux, if set to zero it will remove this option and use
-            0 as the default.
+            [Duration](https://docs.influxdata.com/flux/v0.x/spec/lexical-elements/#duration-literals)
+            to delay execution of the task after the scheduled time has elapsed.
+            `0` removes the offset.
+
+            The value is a [duration
+            literal](https://docs.influxdata.com/flux/v0.x/spec/lexical-elements/#duration-literals).
+          format: duration
           type: string
         org:
-          description: The name of the organization that owns this Task.
+          description: Name of the organization that owns the task.
           type: string
         orgID:
-          description: The ID of the organization that owns this Task.
+          description: ID of the organization that owns the task.
           type: string
         ownerID:
-          description: The ID of the user who owns this Task.
+          description: ID of the user who owns this Task.
           type: string
         status:
           $ref: '#/components/schemas/TaskStatusType'
         type:
-          description: >-
-            The type of task, this can be used for filtering tasks on list
-            actions.
+          description: Type of the task, useful for filtering a task list.
           type: string
         updatedAt:
           format: date-time
@@ -5907,7 +6095,7 @@ info:
     with InfluxDB. Access the InfluxDB API using the `/api/v2/` endpoint.
 openapi: 3.0.0
 paths:
-  /api/v2/:
+  /api/v2:
     get:
       operationId: GetRoutes
       parameters:
@@ -8372,13 +8560,14 @@ paths:
             application/json:
               schema:
                 $ref: '#/components/schemas/Token'
-          description: A temp token for Mapbox
+          description: Temporary token for Mapbox.
         '401':
           $ref: '#/components/responses/ServerError'
         '500':
           $ref: '#/components/responses/ServerError'
         default:
           $ref: '#/components/responses/ServerError'
+      summary: Get a mapbox token
   /api/v2/me:
     get:
       operationId: GetMe
@@ -8462,7 +8651,8 @@ paths:
                 externalDocs:
                   description: Prometheus exposition formats
                   url: https://prometheus.io/docs/instrumenting/exposition_formats
-                type: Prometheus text-based exposition
+                format: Prometheus text-based exposition
+                type: string
           description: >
             Payload body contains metrics about the InfluxDB instance.
 
@@ -9885,6 +10075,308 @@ paths:
       summary: Get the readiness of an instance at startup
       tags:
         - Ready
+  /api/v2/remotes:
+    get:
+      operationId: GetRemoteConnections
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The organization ID.
+          in: query
+          name: orgID
+          required: true
+          schema:
+            type: string
+        - in: query
+          name: name
+          schema:
+            type: string
+        - in: query
+          name: remoteURL
+          schema:
+            format: uri
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/RemoteConnections'
+          description: List of remote connections
+        '404':
+          $ref: '#/components/responses/ServerError'
+        default:
+          $ref: '#/components/responses/ServerError'
+      summary: List all remote connections
+      tags:
+        - RemoteConnections
+    post:
+      operationId: PostRemoteConnection
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/RemoteConnectionCreationRequest'
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/RemoteConnection'
+          description: Remote connection saved
+        '400':
+          $ref: '#/components/responses/ServerError'
+        default:
+          $ref: '#/components/responses/ServerError'
+      summary: Register a new remote connection
+      tags:
+        - RemoteConnections
+  /api/v2/remotes/{remoteID}:
+    delete:
+      operationId: DeleteRemoteConnectionByID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - in: path
+          name: remoteID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Remote connection info deleted.
+        '404':
+          $ref: '#/components/responses/ServerError'
+        default:
+          $ref: '#/components/responses/ServerError'
+      summary: Delete a remote connection
+      tags:
+        - RemoteConnections
+    get:
+      operationId: GetRemoteConnectionByID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - in: path
+          name: remoteID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/RemoteConnection'
+          description: Remote connection
+        '404':
+          $ref: '#/components/responses/ServerError'
+        default:
+          $ref: '#/components/responses/ServerError'
+      summary: Retrieve a remote connection
+      tags:
+        - RemoteConnections
+    patch:
+      operationId: PatchRemoteConnectionByID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - in: path
+          name: remoteID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/RemoteConnectionUpdateRequest'
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/RemoteConnection'
+          description: Updated information saved
+        '400':
+          $ref: '#/components/responses/ServerError'
+        '404':
+          $ref: '#/components/responses/ServerError'
+        default:
+          $ref: '#/components/responses/ServerError'
+      summary: Update a remote connection
+      tags:
+        - RemoteConnections
+  /api/v2/replications:
+    get:
+      operationId: GetReplications
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The organization ID.
+          in: query
+          name: orgID
+          required: true
+          schema:
+            type: string
+        - in: query
+          name: name
+          schema:
+            type: string
+        - in: query
+          name: remoteID
+          schema:
+            type: string
+        - in: query
+          name: localBucketID
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Replications'
+          description: List of replications
+        '404':
+          $ref: '#/components/responses/ServerError'
+        default:
+          $ref: '#/components/responses/ServerError'
+      summary: List all replications
+      tags:
+        - Replications
+    post:
+      operationId: PostReplication
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: If true, validate the replication, but don't save it.
+          in: query
+          name: validate
+          schema:
+            default: false
+            type: boolean
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/ReplicationCreationRequest'
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Replication'
+          description: Replication saved
+        '204':
+          description: Replication validated, but not saved
+        '400':
+          $ref: '#/components/responses/ServerError'
+        default:
+          $ref: '#/components/responses/ServerError'
+      summary: Register a new replication
+      tags:
+        - Replications
+  /api/v2/replications/{replicationID}:
+    delete:
+      operationId: DeleteReplicationByID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - in: path
+          name: replicationID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Replication deleted.
+        '404':
+          $ref: '#/components/responses/ServerError'
+        default:
+          $ref: '#/components/responses/ServerError'
+      summary: Delete a replication
+      tags:
+        - Replications
+    get:
+      operationId: GetReplicationByID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - in: path
+          name: replicationID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Replication'
+          description: Replication
+        '404':
+          $ref: '#/components/responses/ServerError'
+        default:
+          $ref: '#/components/responses/ServerError'
+      summary: Retrieve a replication
+      tags:
+        - Replications
+    patch:
+      operationId: PatchReplicationByID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - in: path
+          name: replicationID
+          required: true
+          schema:
+            type: string
+        - description: If true, validate the updated information, but don't save it.
+          in: query
+          name: validate
+          schema:
+            default: false
+            type: boolean
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/ReplicationUpdateRequest'
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Replication'
+          description: Updated information saved
+        '204':
+          description: Updated replication validated, but not saved
+        '400':
+          $ref: '#/components/responses/ServerError'
+        '404':
+          $ref: '#/components/responses/ServerError'
+        default:
+          $ref: '#/components/responses/ServerError'
+      summary: Update a replication
+      tags:
+        - Replications
+  /api/v2/replications/{replicationID}/validate:
+    post:
+      operationId: PostValidateReplicationByID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - in: path
+          name: replicationID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Replication is valid
+        '400':
+          $ref: '#/components/responses/ServerError'
+          description: Replication failed validation
+        default:
+          $ref: '#/components/responses/ServerError'
+      summary: Validate a replication
+      tags:
+        - Replications
   /api/v2/resources:
     get:
       operationId: GetResources
@@ -12287,6 +12779,22 @@ paths:
             summary of the run. The summary contains newly created resources.
             The diff compares the initial state to the state after the package
             applied. This corresponds to `"dryRun": true`.
+        '422':
+          content:
+            application/json:
+              schema:
+                allOf:
+                  - $ref: '#/components/schemas/TemplateSummary'
+                  - properties:
+                      code:
+                        type: string
+                      message:
+                        type: string
+                    required:
+                      - message
+                      - code
+                    type: object
+          description: Template failed validation
         default:
           content:
             application/json:
@@ -13044,6 +13552,7 @@ tags:
   - Buckets
   - Cells
   - Checks
+  - Config
   - Dashboards
   - DBRPs
   - Delete
@@ -13070,6 +13579,8 @@ tags:
     name: Quick start
     x-traitTag: true
   - Ready
+  - RemoteConnections
+  - Replications
   - Resources
   - description: >
       The InfluxDB API uses standard HTTP status codes for success and failure
@@ -13168,6 +13679,7 @@ x-tagGroups:
   - name: System information endpoints
     tags:
       - Health
+      - Metrics
       - Ping
       - Ready
       - Routes
@@ -13191,6 +13703,8 @@ x-tagGroups:
       - Ping
       - Query
       - Ready
+      - RemoteConnections
+      - Replications
       - Resources
       - Restore
       - Routes
diff --git a/api-docs/v2.1/swaggerV1Compat.yml b/api-docs/v2.1/swaggerV1Compat.yml
index 6ebeeb9f3..e5b1a9eec 100644
--- a/api-docs/v2.1/swaggerV1Compat.yml
+++ b/api-docs/v2.1/swaggerV1Compat.yml
@@ -3,7 +3,7 @@ info:
   title: InfluxDB OSS v1 compatibility API documentation
   version: 0.1.0
   description: |
-    The InfluxDB 1.x compatibility /write and /query endpoints work with
+    The InfluxDB 1.x compatibility `/write` and `/query` endpoints work with
     InfluxDB 1.x client libraries and third-party integrations like Grafana
     and others.
 
diff --git a/api-docs/v2.2/ref.yml b/api-docs/v2.2/ref.yml
new file mode 100644
index 000000000..5c764c1b7
--- /dev/null
+++ b/api-docs/v2.2/ref.yml
@@ -0,0 +1,14788 @@
+components:
+  parameters:
+    After:
+      description: >
+        Resource ID to seek from. Results are not inclusive of this ID. Use
+        `after` instead of `offset`.
+      in: query
+      name: after
+      required: false
+      schema:
+        type: string
+    Descending:
+      in: query
+      name: descending
+      required: false
+      schema:
+        default: false
+        type: boolean
+    Limit:
+      in: query
+      name: limit
+      required: false
+      schema:
+        default: 20
+        maximum: 100
+        minimum: 1
+        type: integer
+    Offset:
+      in: query
+      name: offset
+      required: false
+      schema:
+        minimum: 0
+        type: integer
+    SortBy:
+      in: query
+      name: sortBy
+      required: false
+      schema:
+        type: string
+    TraceSpan:
+      description: OpenTracing span context
+      example:
+        baggage:
+          key: value
+        span_id: '1'
+        trace_id: '1'
+      in: header
+      name: Zap-Trace-Span
+      required: false
+      schema:
+        type: string
+  responses:
+    ServerError:
+      content:
+        application/json:
+          schema:
+            $ref: '#/components/schemas/Error'
+      description: Non 2XX error response from server.
+  schemas:
+    ASTResponse:
+      description: Contains the AST for the supplied Flux query
+      properties:
+        ast:
+          $ref: '#/components/schemas/Package'
+      type: object
+    AddResourceMemberRequestBody:
+      properties:
+        id:
+          type: string
+        name:
+          type: string
+      required:
+        - id
+      type: object
+    AnalyzeQueryResponse:
+      properties:
+        errors:
+          items:
+            properties:
+              character:
+                type: integer
+              column:
+                type: integer
+              line:
+                type: integer
+              message:
+                type: string
+            type: object
+          type: array
+      type: object
+    ArrayExpression:
+      description: Used to create and directly specify the elements of an array object
+      properties:
+        elements:
+          description: Elements of the array
+          items:
+            $ref: '#/components/schemas/Expression'
+          type: array
+        type:
+          $ref: '#/components/schemas/NodeType'
+      type: object
+    Authorization:
+      allOf:
+        - $ref: '#/components/schemas/AuthorizationUpdateRequest'
+        - properties:
+            createdAt:
+              format: date-time
+              readOnly: true
+              type: string
+            id:
+              readOnly: true
+              type: string
+            links:
+              example:
+                self: /api/v2/authorizations/1
+                user: /api/v2/users/12
+              properties:
+                self:
+                  $ref: '#/components/schemas/Link'
+                  readOnly: true
+                user:
+                  $ref: '#/components/schemas/Link'
+                  readOnly: true
+              readOnly: true
+              type: object
+            org:
+              description: Name of the organization that the token is scoped to.
+              readOnly: true
+              type: string
+            orgID:
+              description: ID of the organization that the authorization is scoped to.
+              type: string
+            permissions:
+              description: >-
+                List of permissions for an authorization.  An authorization must
+                have at least one permission.
+              items:
+                $ref: '#/components/schemas/Permission'
+              minItems: 1
+              type: array
+            token:
+              description: Token used to authenticate API requests.
+              readOnly: true
+              type: string
+            updatedAt:
+              format: date-time
+              readOnly: true
+              type: string
+            user:
+              description: Name of the user that created and owns the token.
+              readOnly: true
+              type: string
+            userID:
+              description: ID of the user that created and owns the token.
+              readOnly: true
+              type: string
+          type: object
+      required:
+        - orgID
+        - permissions
+    AuthorizationPostRequest:
+      allOf:
+        - $ref: '#/components/schemas/AuthorizationUpdateRequest'
+        - properties:
+            orgID:
+              description: ID of org that authorization is scoped to.
+              type: string
+            permissions:
+              description: >-
+                List of permissions for an auth.  An auth must have at least one
+                Permission.
+              items:
+                $ref: '#/components/schemas/Permission'
+              minItems: 1
+              type: array
+            userID:
+              description: ID of user that authorization is scoped to.
+              type: string
+          type: object
+      required:
+        - orgID
+        - permissions
+    AuthorizationUpdateRequest:
+      properties:
+        description:
+          description: A description of the token.
+          type: string
+        status:
+          default: active
+          description: >-
+            Status of the token. If `inactive`, requests using the token will be
+            rejected.
+          enum:
+            - active
+            - inactive
+          type: string
+    Authorizations:
+      properties:
+        authorizations:
+          items:
+            $ref: '#/components/schemas/Authorization'
+          type: array
+        links:
+          $ref: '#/components/schemas/Links'
+          readOnly: true
+      type: object
+    Axes:
+      description: The viewport for a View's visualizations
+      properties:
+        x:
+          $ref: '#/components/schemas/Axis'
+        'y':
+          $ref: '#/components/schemas/Axis'
+      required:
+        - x
+        - 'y'
+      type: object
+    Axis:
+      description: Axis used in a visualization.
+      properties:
+        base:
+          description: Radix for formatting axis values.
+          enum:
+            - ''
+            - '2'
+            - '10'
+          type: string
+        bounds:
+          description: >-
+            The extents of the axis in the form [lower, upper]. Clients
+            determine whether bounds are inclusive or exclusive of their limits.
+          items:
+            type: string
+          maxItems: 2
+          minItems: 0
+          type: array
+        label:
+          description: Description of the axis.
+          type: string
+        prefix:
+          description: Label prefix for formatting axis values.
+          type: string
+        scale:
+          $ref: '#/components/schemas/AxisScale'
+        suffix:
+          description: Label suffix for formatting axis values.
+          type: string
+      type: object
+    AxisScale:
+      description: 'Scale is the axis formatting scale. Supported: "log", "linear"'
+      enum:
+        - log
+        - linear
+      type: string
+    BadStatement:
+      description: >-
+        A placeholder for statements for which no correct statement nodes can be
+        created
+      properties:
+        text:
+          description: Raw source text
+          type: string
+        type:
+          $ref: '#/components/schemas/NodeType'
+      type: object
+    BandViewProperties:
+      properties:
+        axes:
+          $ref: '#/components/schemas/Axes'
+        colors:
+          description: Colors define color encoding of data into a visualization
+          items:
+            $ref: '#/components/schemas/DashboardColor'
+          type: array
+        generateXAxisTicks:
+          items:
+            type: string
+          type: array
+        generateYAxisTicks:
+          items:
+            type: string
+          type: array
+        geom:
+          $ref: '#/components/schemas/XYGeom'
+        hoverDimension:
+          enum:
+            - auto
+            - x
+            - 'y'
+            - xy
+          type: string
+        legendColorizeRows:
+          type: boolean
+        legendHide:
+          type: boolean
+        legendOpacity:
+          format: float
+          type: number
+        legendOrientationThreshold:
+          type: integer
+        lowerColumn:
+          type: string
+        mainColumn:
+          type: string
+        note:
+          type: string
+        queries:
+          items:
+            $ref: '#/components/schemas/DashboardQuery'
+          type: array
+        shape:
+          enum:
+            - chronograf-v2
+          type: string
+        showNoteWhenEmpty:
+          description: If true, will display note when empty
+          type: boolean
+        staticLegend:
+          $ref: '#/components/schemas/StaticLegend'
+        timeFormat:
+          type: string
+        type:
+          enum:
+            - band
+          type: string
+        upperColumn:
+          type: string
+        xColumn:
+          type: string
+        xTickStart:
+          format: float
+          type: number
+        xTickStep:
+          format: float
+          type: number
+        xTotalTicks:
+          type: integer
+        yColumn:
+          type: string
+        yTickStart:
+          format: float
+          type: number
+        yTickStep:
+          format: float
+          type: number
+        yTotalTicks:
+          type: integer
+      required:
+        - type
+        - geom
+        - queries
+        - shape
+        - axes
+        - colors
+        - note
+        - showNoteWhenEmpty
+      type: object
+    BinaryExpression:
+      description: uses binary operators to act on two operands in an expression
+      properties:
+        left:
+          $ref: '#/components/schemas/Expression'
+        operator:
+          type: string
+        right:
+          $ref: '#/components/schemas/Expression'
+        type:
+          $ref: '#/components/schemas/NodeType'
+      type: object
+    Block:
+      description: A set of statements
+      properties:
+        body:
+          description: Block body
+          items:
+            $ref: '#/components/schemas/Statement'
+          type: array
+        type:
+          $ref: '#/components/schemas/NodeType'
+      type: object
+    BooleanLiteral:
+      description: Represents boolean values
+      properties:
+        type:
+          $ref: '#/components/schemas/NodeType'
+        value:
+          type: boolean
+      type: object
+    Bucket:
+      properties:
+        createdAt:
+          format: date-time
+          readOnly: true
+          type: string
+        description:
+          type: string
+        id:
+          readOnly: true
+          type: string
+        labels:
+          $ref: '#/components/schemas/Labels'
+        links:
+          example:
+            labels: /api/v2/buckets/1/labels
+            members: /api/v2/buckets/1/members
+            org: /api/v2/orgs/2
+            owners: /api/v2/buckets/1/owners
+            self: /api/v2/buckets/1
+            write: /api/v2/write?org=2&bucket=1
+          properties:
+            labels:
+              $ref: '#/components/schemas/Link'
+              description: URL to retrieve labels for this bucket.
+            members:
+              $ref: '#/components/schemas/Link'
+              description: URL to retrieve members that can read this bucket.
+            org:
+              $ref: '#/components/schemas/Link'
+              description: URL to retrieve parent organization for this bucket.
+            owners:
+              $ref: '#/components/schemas/Link'
+              description: URL to retrieve owners that can read and write to this bucket.
+            self:
+              $ref: '#/components/schemas/Link'
+              description: URL for this bucket.
+            write:
+              $ref: '#/components/schemas/Link'
+              description: URL to write line protocol to this bucket.
+          readOnly: true
+          type: object
+        name:
+          type: string
+        orgID:
+          type: string
+        retentionRules:
+          $ref: '#/components/schemas/RetentionRules'
+        rp:
+          type: string
+        schemaType:
+          $ref: '#/components/schemas/SchemaType'
+          default: implicit
+        type:
+          default: user
+          enum:
+            - user
+            - system
+          readOnly: true
+          type: string
+        updatedAt:
+          format: date-time
+          readOnly: true
+          type: string
+      required:
+        - name
+        - retentionRules
+    BucketMetadataManifest:
+      properties:
+        bucketID:
+          type: string
+        bucketName:
+          type: string
+        defaultRetentionPolicy:
+          type: string
+        description:
+          type: string
+        organizationID:
+          type: string
+        organizationName:
+          type: string
+        retentionPolicies:
+          $ref: '#/components/schemas/RetentionPolicyManifests'
+      required:
+        - organizationID
+        - organizationName
+        - bucketID
+        - bucketName
+        - defaultRetentionPolicy
+        - retentionPolicies
+      type: object
+    BucketMetadataManifests:
+      items:
+        $ref: '#/components/schemas/BucketMetadataManifest'
+      type: array
+    BucketShardMapping:
+      properties:
+        newId:
+          format: int64
+          type: integer
+        oldId:
+          format: int64
+          type: integer
+      required:
+        - oldId
+        - newId
+      type: object
+    BucketShardMappings:
+      items:
+        $ref: '#/components/schemas/BucketShardMapping'
+      type: array
+    Buckets:
+      properties:
+        buckets:
+          items:
+            $ref: '#/components/schemas/Bucket'
+          type: array
+        links:
+          $ref: '#/components/schemas/Links'
+          readOnly: true
+      type: object
+    BuilderAggregateFunctionType:
+      enum:
+        - filter
+        - group
+      type: string
+    BuilderConfig:
+      properties:
+        aggregateWindow:
+          properties:
+            fillValues:
+              type: boolean
+            period:
+              type: string
+          type: object
+        buckets:
+          items:
+            type: string
+          type: array
+        functions:
+          items:
+            $ref: '#/components/schemas/BuilderFunctionsType'
+          type: array
+        tags:
+          items:
+            $ref: '#/components/schemas/BuilderTagsType'
+          type: array
+      type: object
+    BuilderFunctionsType:
+      properties:
+        name:
+          type: string
+      type: object
+    BuilderTagsType:
+      properties:
+        aggregateFunctionType:
+          $ref: '#/components/schemas/BuilderAggregateFunctionType'
+        key:
+          type: string
+        values:
+          items:
+            type: string
+          type: array
+      type: object
+    BuiltinStatement:
+      description: Declares a builtin identifier and its type
+      properties:
+        id:
+          $ref: '#/components/schemas/Identifier'
+        type:
+          $ref: '#/components/schemas/NodeType'
+      type: object
+    CallExpression:
+      description: Represents a function call
+      properties:
+        arguments:
+          description: Function arguments
+          items:
+            $ref: '#/components/schemas/Expression'
+          type: array
+        callee:
+          $ref: '#/components/schemas/Expression'
+        type:
+          $ref: '#/components/schemas/NodeType'
+      type: object
+    Cell:
+      properties:
+        h:
+          format: int32
+          type: integer
+        id:
+          type: string
+        links:
+          properties:
+            self:
+              type: string
+            view:
+              type: string
+          type: object
+        viewID:
+          description: The reference to a view from the views API.
+          type: string
+        w:
+          format: int32
+          type: integer
+        x:
+          format: int32
+          type: integer
+        'y':
+          format: int32
+          type: integer
+      type: object
+    CellUpdate:
+      properties:
+        h:
+          format: int32
+          type: integer
+        w:
+          format: int32
+          type: integer
+        x:
+          format: int32
+          type: integer
+        'y':
+          format: int32
+          type: integer
+      type: object
+    CellWithViewProperties:
+      allOf:
+        - $ref: '#/components/schemas/Cell'
+        - properties:
+            name:
+              type: string
+            properties:
+              $ref: '#/components/schemas/ViewProperties'
+          type: object
+      type: object
+    Cells:
+      items:
+        $ref: '#/components/schemas/Cell'
+      type: array
+    CellsWithViewProperties:
+      items:
+        $ref: '#/components/schemas/CellWithViewProperties'
+      type: array
+    Check:
+      allOf:
+        - $ref: '#/components/schemas/CheckDiscriminator'
+    CheckBase:
+      properties:
+        createdAt:
+          format: date-time
+          readOnly: true
+          type: string
+        description:
+          description: An optional description of the check.
+          type: string
+        id:
+          readOnly: true
+          type: string
+        labels:
+          $ref: '#/components/schemas/Labels'
+        lastRunError:
+          readOnly: true
+          type: string
+        lastRunStatus:
+          enum:
+            - failed
+            - success
+            - canceled
+          readOnly: true
+          type: string
+        latestCompleted:
+          description: >-
+            Timestamp (in RFC3339 date/time
+            format](https://datatracker.ietf.org/doc/html/rfc3339)) of the
+            latest scheduled and completed run.
+          format: date-time
+          readOnly: true
+        links:
+          example:
+            labels: /api/v2/checks/1/labels
+            members: /api/v2/checks/1/members
+            owners: /api/v2/checks/1/owners
+            query: /api/v2/checks/1/query
+            self: /api/v2/checks/1
+          properties:
+            labels:
+              $ref: '#/components/schemas/Link'
+              description: URL to retrieve labels for this check
+            members:
+              $ref: '#/components/schemas/Link'
+              description: URL to retrieve members for this check
+            owners:
+              $ref: '#/components/schemas/Link'
+              description: URL to retrieve owners for this check
+            query:
+              $ref: '#/components/schemas/Link'
+              description: URL to retrieve flux script for this check
+            self:
+              $ref: '#/components/schemas/Link'
+              description: URL for this check
+          readOnly: true
+          type: object
+        name:
+          type: string
+        orgID:
+          description: The ID of the organization that owns this check.
+          type: string
+        ownerID:
+          description: The ID of creator used to create this check.
+          readOnly: true
+          type: string
+        query:
+          $ref: '#/components/schemas/DashboardQuery'
+        status:
+          $ref: '#/components/schemas/TaskStatusType'
+        taskID:
+          description: The ID of the task associated with this check.
+          type: string
+        updatedAt:
+          format: date-time
+          readOnly: true
+          type: string
+      required:
+        - name
+        - orgID
+        - query
+    CheckDiscriminator:
+      discriminator:
+        mapping:
+          custom: '#/components/schemas/CustomCheck'
+          deadman: '#/components/schemas/DeadmanCheck'
+          threshold: '#/components/schemas/ThresholdCheck'
+        propertyName: type
+      oneOf:
+        - $ref: '#/components/schemas/DeadmanCheck'
+        - $ref: '#/components/schemas/ThresholdCheck'
+        - $ref: '#/components/schemas/CustomCheck'
+    CheckPatch:
+      properties:
+        description:
+          type: string
+        name:
+          type: string
+        status:
+          enum:
+            - active
+            - inactive
+          type: string
+      type: object
+    CheckStatusLevel:
+      description: The state to record if check matches a criteria.
+      enum:
+        - UNKNOWN
+        - OK
+        - INFO
+        - CRIT
+        - WARN
+      type: string
+    CheckViewProperties:
+      properties:
+        check:
+          $ref: '#/components/schemas/Check'
+        checkID:
+          type: string
+        colors:
+          description: Colors define color encoding of data into a visualization
+          items:
+            $ref: '#/components/schemas/DashboardColor'
+          type: array
+        legendColorizeRows:
+          type: boolean
+        legendHide:
+          type: boolean
+        legendOpacity:
+          format: float
+          type: number
+        legendOrientationThreshold:
+          type: integer
+        queries:
+          items:
+            $ref: '#/components/schemas/DashboardQuery'
+          type: array
+        shape:
+          enum:
+            - chronograf-v2
+          type: string
+        type:
+          enum:
+            - check
+          type: string
+      required:
+        - type
+        - shape
+        - checkID
+        - queries
+        - colors
+      type: object
+    Checks:
+      properties:
+        checks:
+          items:
+            $ref: '#/components/schemas/Check'
+          type: array
+        links:
+          $ref: '#/components/schemas/Links'
+    ColorMapping:
+      additionalProperties:
+        type: string
+      description: >-
+        A color mapping is an object that maps time series data to a UI color
+        scheme to allow the UI to render graphs consistent colors across
+        reloads.
+      example:
+        configcat_deployments-autopromotionblocker: '#663cd0'
+        measurement_birdmigration_europe: '#663cd0'
+        series_id_1: '#edf529'
+        series_id_2: '#edf529'
+      type: object
+    ConditionalExpression:
+      description: >-
+        Selects one of two expressions, `Alternate` or `Consequent`, depending
+        on a third boolean expression, `Test`
+      properties:
+        alternate:
+          $ref: '#/components/schemas/Expression'
+        consequent:
+          $ref: '#/components/schemas/Expression'
+        test:
+          $ref: '#/components/schemas/Expression'
+        type:
+          $ref: '#/components/schemas/NodeType'
+      type: object
+    Config:
+      properties:
+        config:
+          type: object
+      type: object
+    ConstantVariableProperties:
+      properties:
+        type:
+          enum:
+            - constant
+          type: string
+        values:
+          items:
+            type: string
+          type: array
+    CreateCell:
+      properties:
+        h:
+          format: int32
+          type: integer
+        name:
+          type: string
+        usingView:
+          description: Makes a copy of the provided view.
+          type: string
+        w:
+          format: int32
+          type: integer
+        x:
+          format: int32
+          type: integer
+        'y':
+          format: int32
+          type: integer
+      type: object
+    CreateDashboardRequest:
+      properties:
+        description:
+          description: The user-facing description of the dashboard.
+          type: string
+        name:
+          description: The user-facing name of the dashboard.
+          type: string
+        orgID:
+          description: The ID of the organization that owns the dashboard.
+          type: string
+      required:
+        - orgID
+        - name
+    CustomCheck:
+      allOf:
+        - $ref: '#/components/schemas/CheckBase'
+        - properties:
+            type:
+              enum:
+                - custom
+              type: string
+          required:
+            - type
+          type: object
+    DBRP:
+      properties:
+        bucketID:
+          description: ID of the bucket used as the target for the translation.
+          type: string
+        database:
+          description: InfluxDB v1 database
+          type: string
+        default:
+          description: >-
+            Mapping represents the default retention policy for the database
+            specified.
+          type: boolean
+        id:
+          description: ID of the DBRP mapping.
+          readOnly: true
+          type: string
+        links:
+          $ref: '#/components/schemas/Links'
+        orgID:
+          description: ID of the organization that owns this mapping.
+          type: string
+        retention_policy:
+          description: InfluxDB v1 retention policy
+          type: string
+      required:
+        - id
+        - orgID
+        - bucketID
+        - database
+        - retention_policy
+        - default
+      type: object
+    DBRPCreate:
+      properties:
+        bucketID:
+          description: ID of the bucket used as the target for the translation.
+          type: string
+        database:
+          description: InfluxDB v1 database
+          type: string
+        default:
+          description: >-
+            Mapping represents the default retention policy for the database
+            specified.
+          type: boolean
+        org:
+          description: Name of the organization that owns this mapping.
+          type: string
+        orgID:
+          description: ID of the organization that owns this mapping.
+          type: string
+        retention_policy:
+          description: InfluxDB v1 retention policy
+          type: string
+      required:
+        - bucketID
+        - database
+        - retention_policy
+      type: object
+    DBRPGet:
+      properties:
+        content:
+          $ref: '#/components/schemas/DBRP'
+          required: true
+      type: object
+    DBRPUpdate:
+      properties:
+        default:
+          type: boolean
+        retention_policy:
+          description: InfluxDB v1 retention policy
+          type: string
+    DBRPs:
+      properties:
+        content:
+          items:
+            $ref: '#/components/schemas/DBRP'
+          type: array
+    Dashboard:
+      allOf:
+        - $ref: '#/components/schemas/CreateDashboardRequest'
+        - properties:
+            cells:
+              $ref: '#/components/schemas/Cells'
+            id:
+              readOnly: true
+              type: string
+            labels:
+              $ref: '#/components/schemas/Labels'
+            links:
+              example:
+                cells: /api/v2/dashboards/1/cells
+                labels: /api/v2/dashboards/1/labels
+                members: /api/v2/dashboards/1/members
+                org: /api/v2/labels/1
+                owners: /api/v2/dashboards/1/owners
+                self: /api/v2/dashboards/1
+              properties:
+                cells:
+                  $ref: '#/components/schemas/Link'
+                labels:
+                  $ref: '#/components/schemas/Link'
+                members:
+                  $ref: '#/components/schemas/Link'
+                org:
+                  $ref: '#/components/schemas/Link'
+                owners:
+                  $ref: '#/components/schemas/Link'
+                self:
+                  $ref: '#/components/schemas/Link'
+              type: object
+            meta:
+              properties:
+                createdAt:
+                  format: date-time
+                  type: string
+                updatedAt:
+                  format: date-time
+                  type: string
+              type: object
+          type: object
+      type: object
+    DashboardColor:
+      description: Defines an encoding of data value into color space.
+      properties:
+        hex:
+          description: The hex number of the color
+          maxLength: 7
+          minLength: 7
+          type: string
+        id:
+          description: The unique ID of the view color.
+          type: string
+        name:
+          description: The user-facing name of the hex color.
+          type: string
+        type:
+          description: Type is how the color is used.
+          enum:
+            - min
+            - max
+            - threshold
+            - scale
+            - text
+            - background
+          type: string
+        value:
+          description: The data value mapped to this color.
+          format: float
+          type: number
+      required:
+        - id
+        - type
+        - hex
+        - name
+        - value
+      type: object
+    DashboardQuery:
+      properties:
+        builderConfig:
+          $ref: '#/components/schemas/BuilderConfig'
+        editMode:
+          $ref: '#/components/schemas/QueryEditMode'
+        name:
+          type: string
+        text:
+          description: The text of the Flux query.
+          type: string
+      type: object
+    DashboardWithViewProperties:
+      allOf:
+        - $ref: '#/components/schemas/CreateDashboardRequest'
+        - properties:
+            cells:
+              $ref: '#/components/schemas/CellsWithViewProperties'
+            id:
+              readOnly: true
+              type: string
+            labels:
+              $ref: '#/components/schemas/Labels'
+            links:
+              example:
+                cells: /api/v2/dashboards/1/cells
+                labels: /api/v2/dashboards/1/labels
+                members: /api/v2/dashboards/1/members
+                org: /api/v2/labels/1
+                owners: /api/v2/dashboards/1/owners
+                self: /api/v2/dashboards/1
+              properties:
+                cells:
+                  $ref: '#/components/schemas/Link'
+                labels:
+                  $ref: '#/components/schemas/Link'
+                members:
+                  $ref: '#/components/schemas/Link'
+                org:
+                  $ref: '#/components/schemas/Link'
+                owners:
+                  $ref: '#/components/schemas/Link'
+                self:
+                  $ref: '#/components/schemas/Link'
+              type: object
+            meta:
+              properties:
+                createdAt:
+                  format: date-time
+                  type: string
+                updatedAt:
+                  format: date-time
+                  type: string
+              type: object
+          type: object
+      type: object
+    Dashboards:
+      properties:
+        dashboards:
+          items:
+            $ref: '#/components/schemas/Dashboard'
+          type: array
+        links:
+          $ref: '#/components/schemas/Links'
+      type: object
+    DateTimeLiteral:
+      description: >-
+        Represents an instant in time with nanosecond precision using the syntax
+        of golang's RFC3339 Nanosecond variant
+      properties:
+        type:
+          $ref: '#/components/schemas/NodeType'
+        value:
+          format: date-time
+          type: string
+      type: object
+    DeadmanCheck:
+      allOf:
+        - $ref: '#/components/schemas/CheckBase'
+        - properties:
+            every:
+              description: Check repetition interval.
+              type: string
+            level:
+              $ref: '#/components/schemas/CheckStatusLevel'
+            offset:
+              description: Duration to delay after the schedule, before executing check.
+              type: string
+            reportZero:
+              description: If only zero values reported since time, trigger an alert
+              type: boolean
+            staleTime:
+              description: >-
+                String duration for time that a series is considered stale and
+                should not trigger deadman.
+              type: string
+            statusMessageTemplate:
+              description: The template used to generate and write a status message.
+              type: string
+            tags:
+              description: List of tags to write to each status.
+              items:
+                properties:
+                  key:
+                    type: string
+                  value:
+                    type: string
+                type: object
+              type: array
+            timeSince:
+              description: String duration before deadman triggers.
+              type: string
+            type:
+              enum:
+                - deadman
+              type: string
+          required:
+            - type
+          type: object
+    DecimalPlaces:
+      description: >-
+        Indicates whether decimal places should be enforced, and how many digits
+        it should show.
+      properties:
+        digits:
+          description: The number of digits after decimal to display
+          format: int32
+          type: integer
+        isEnforced:
+          description: Indicates whether decimal point setting should be enforced
+          type: boolean
+      type: object
+    DeletePredicateRequest:
+      description: The delete predicate request.
+      properties:
+        predicate:
+          description: InfluxQL-like delete statement
+          example: tag1="value1" and (tag2="value2" and tag3!="value3")
+          type: string
+        start:
+          description: RFC3339Nano
+          format: date-time
+          type: string
+        stop:
+          description: RFC3339Nano
+          format: date-time
+          type: string
+      required:
+        - start
+        - stop
+      type: object
+    Dialect:
+      description: >-
+        Dialect are options to change the default CSV output format;
+        https://www.w3.org/TR/2015/REC-tabular-metadata-20151217/#dialect-descriptions
+      properties:
+        annotations:
+          description: https://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#columns
+          items:
+            enum:
+              - group
+              - datatype
+              - default
+            type: string
+          type: array
+          uniqueItems: true
+        commentPrefix:
+          default: '#'
+          description: Character prefixed to comment strings
+          maxLength: 1
+          minLength: 0
+          type: string
+        dateTimeFormat:
+          default: RFC3339
+          description: Format of timestamps
+          enum:
+            - RFC3339
+            - RFC3339Nano
+          type: string
+        delimiter:
+          default: ','
+          description: Separator between cells; the default is ,
+          maxLength: 1
+          minLength: 1
+          type: string
+        header:
+          default: true
+          description: If true, the results will contain a header row
+          type: boolean
+      type: object
+    DictExpression:
+      description: Used to create and directly specify the elements of a dictionary
+      properties:
+        elements:
+          description: Elements of the dictionary
+          items:
+            $ref: '#/components/schemas/DictItem'
+          type: array
+        type:
+          $ref: '#/components/schemas/NodeType'
+      type: object
+    DictItem:
+      description: A key/value pair in a dictionary
+      properties:
+        key:
+          $ref: '#/components/schemas/Expression'
+        type:
+          $ref: '#/components/schemas/NodeType'
+        val:
+          $ref: '#/components/schemas/Expression'
+      type: object
+    Duration:
+      description: >-
+        A pair consisting of length of time and the unit of time measured. It is
+        the atomic unit from which all duration literals are composed.
+      properties:
+        magnitude:
+          type: integer
+        type:
+          $ref: '#/components/schemas/NodeType'
+        unit:
+          type: string
+      type: object
+    DurationLiteral:
+      description: >-
+        Represents the elapsed time between two instants as an int64 nanosecond
+        count with syntax of golang's time.Duration
+      properties:
+        type:
+          $ref: '#/components/schemas/NodeType'
+        values:
+          description: Duration values
+          items:
+            $ref: '#/components/schemas/Duration'
+          type: array
+      type: object
+    Error:
+      properties:
+        code:
+          description: code is the machine-readable error code.
+          enum:
+            - internal error
+            - not found
+            - conflict
+            - invalid
+            - unprocessable entity
+            - empty value
+            - unavailable
+            - forbidden
+            - too many requests
+            - unauthorized
+            - method not allowed
+            - request too large
+            - unsupported media type
+          readOnly: true
+          type: string
+        err:
+          description: >-
+            Stack of errors that occurred during processing of the request.
+            Useful for debugging.
+          readOnly: true
+          type: string
+        message:
+          description: Human-readable message.
+          readOnly: true
+          type: string
+        op:
+          description: >-
+            Describes the logical code operation when the error occurred. Useful
+            for debugging.
+          readOnly: true
+          type: string
+      required:
+        - code
+    Expression:
+      oneOf:
+        - $ref: '#/components/schemas/ArrayExpression'
+        - $ref: '#/components/schemas/DictExpression'
+        - $ref: '#/components/schemas/FunctionExpression'
+        - $ref: '#/components/schemas/BinaryExpression'
+        - $ref: '#/components/schemas/CallExpression'
+        - $ref: '#/components/schemas/ConditionalExpression'
+        - $ref: '#/components/schemas/LogicalExpression'
+        - $ref: '#/components/schemas/MemberExpression'
+        - $ref: '#/components/schemas/IndexExpression'
+        - $ref: '#/components/schemas/ObjectExpression'
+        - $ref: '#/components/schemas/ParenExpression'
+        - $ref: '#/components/schemas/PipeExpression'
+        - $ref: '#/components/schemas/UnaryExpression'
+        - $ref: '#/components/schemas/BooleanLiteral'
+        - $ref: '#/components/schemas/DateTimeLiteral'
+        - $ref: '#/components/schemas/DurationLiteral'
+        - $ref: '#/components/schemas/FloatLiteral'
+        - $ref: '#/components/schemas/IntegerLiteral'
+        - $ref: '#/components/schemas/PipeLiteral'
+        - $ref: '#/components/schemas/RegexpLiteral'
+        - $ref: '#/components/schemas/StringLiteral'
+        - $ref: '#/components/schemas/UnsignedIntegerLiteral'
+        - $ref: '#/components/schemas/Identifier'
+    ExpressionStatement:
+      description: >-
+        May consist of an expression that does not return a value and is
+        executed solely for its side-effects
+      properties:
+        expression:
+          $ref: '#/components/schemas/Expression'
+        type:
+          $ref: '#/components/schemas/NodeType'
+      type: object
+    Field:
+      properties:
+        alias:
+          description: >-
+            Alias overrides the field name in the returned response.  Applies
+            only if type is `func`
+          type: string
+        args:
+          description: Args are the arguments to the function
+          items:
+            $ref: '#/components/schemas/Field'
+          type: array
+        type:
+          description: >-
+            `type` describes the field type. `func` is a function. `field` is a
+            field reference.
+          enum:
+            - func
+            - field
+            - integer
+            - number
+            - regex
+            - wildcard
+          type: string
+        value:
+          description: >-
+            value is the value of the field.  Meaning of the value is implied by
+            the `type` key
+          type: string
+      type: object
+    File:
+      description: Represents a source from a single file
+      properties:
+        body:
+          description: List of Flux statements
+          items:
+            $ref: '#/components/schemas/Statement'
+          type: array
+        imports:
+          description: A list of package imports
+          items:
+            $ref: '#/components/schemas/ImportDeclaration'
+          type: array
+        name:
+          description: The name of the file.
+          type: string
+        package:
+          $ref: '#/components/schemas/PackageClause'
+        type:
+          $ref: '#/components/schemas/NodeType'
+      type: object
+    Flags:
+      additionalProperties: true
+      type: object
+    FloatLiteral:
+      description: >-
+        Represents floating point numbers according to the double
+        representations defined by the IEEE-754-1985
+      properties:
+        type:
+          $ref: '#/components/schemas/NodeType'
+        value:
+          type: number
+      type: object
+    FluxResponse:
+      description: Rendered flux that backs the check or notification.
+      properties:
+        flux:
+          type: string
+    FluxSuggestion:
+      properties:
+        name:
+          type: string
+        params:
+          additionalProperties:
+            type: string
+          type: object
+      type: object
+    FluxSuggestions:
+      properties:
+        funcs:
+          items:
+            $ref: '#/components/schemas/FluxSuggestion'
+          type: array
+      type: object
+    FunctionExpression:
+      description: Function expression
+      properties:
+        body:
+          $ref: '#/components/schemas/Node'
+        params:
+          description: Function parameters
+          items:
+            $ref: '#/components/schemas/Property'
+          type: array
+        type:
+          $ref: '#/components/schemas/NodeType'
+      type: object
+    GaugeViewProperties:
+      properties:
+        colors:
+          description: Colors define color encoding of data into a visualization
+          items:
+            $ref: '#/components/schemas/DashboardColor'
+          type: array
+        decimalPlaces:
+          $ref: '#/components/schemas/DecimalPlaces'
+        note:
+          type: string
+        prefix:
+          type: string
+        queries:
+          items:
+            $ref: '#/components/schemas/DashboardQuery'
+          type: array
+        shape:
+          enum:
+            - chronograf-v2
+          type: string
+        showNoteWhenEmpty:
+          description: If true, will display note when empty
+          type: boolean
+        suffix:
+          type: string
+        tickPrefix:
+          type: string
+        tickSuffix:
+          type: string
+        type:
+          enum:
+            - gauge
+          type: string
+      required:
+        - type
+        - queries
+        - colors
+        - shape
+        - note
+        - showNoteWhenEmpty
+        - prefix
+        - tickPrefix
+        - suffix
+        - tickSuffix
+        - decimalPlaces
+      type: object
+    GeoCircleViewLayer:
+      allOf:
+        - $ref: '#/components/schemas/GeoViewLayerProperties'
+        - properties:
+            colorDimension:
+              $ref: '#/components/schemas/Axis'
+            colorField:
+              description: Circle color field
+              type: string
+            colors:
+              description: Colors define color encoding of data into a visualization
+              items:
+                $ref: '#/components/schemas/DashboardColor'
+              type: array
+            interpolateColors:
+              description: Interpolate circle color based on displayed value
+              type: boolean
+            radius:
+              description: Maximum radius size in pixels
+              type: integer
+            radiusDimension:
+              $ref: '#/components/schemas/Axis'
+            radiusField:
+              description: Radius field
+              type: string
+          required:
+            - radiusField
+            - radiusDimension
+            - colorField
+            - colorDimension
+            - colors
+          type: object
+    GeoHeatMapViewLayer:
+      allOf:
+        - $ref: '#/components/schemas/GeoViewLayerProperties'
+        - properties:
+            blur:
+              description: Blur for heatmap points
+              type: integer
+            colors:
+              description: Colors define color encoding of data into a visualization
+              items:
+                $ref: '#/components/schemas/DashboardColor'
+              type: array
+            intensityDimension:
+              $ref: '#/components/schemas/Axis'
+            intensityField:
+              description: Intensity field
+              type: string
+            radius:
+              description: Radius size in pixels
+              type: integer
+          required:
+            - intensityField
+            - intensityDimension
+            - radius
+            - blur
+            - colors
+          type: object
+    GeoPointMapViewLayer:
+      allOf:
+        - $ref: '#/components/schemas/GeoViewLayerProperties'
+        - properties:
+            colorDimension:
+              $ref: '#/components/schemas/Axis'
+            colorField:
+              description: Marker color field
+              type: string
+            colors:
+              description: Colors define color encoding of data into a visualization
+              items:
+                $ref: '#/components/schemas/DashboardColor'
+              type: array
+            isClustered:
+              description: Cluster close markers together
+              type: boolean
+            tooltipColumns:
+              description: An array for which columns to display in tooltip
+              items:
+                type: string
+              type: array
+          required:
+            - colorField
+            - colorDimension
+            - colors
+          type: object
+    GeoTrackMapViewLayer:
+      allOf:
+        - $ref: '#/components/schemas/GeoViewLayerProperties'
+        - required:
+            - trackWidth
+            - speed
+            - randomColors
+            - trackPointVisualization
+          type: object
+      properties:
+        colors:
+          description: Colors define color encoding of data into a visualization
+          items:
+            $ref: '#/components/schemas/DashboardColor'
+          type: array
+        randomColors:
+          description: Assign different colors to different tracks
+          type: boolean
+        speed:
+          description: Speed of the track animation
+          type: integer
+        trackWidth:
+          description: Width of the track
+          type: integer
+    GeoViewLayer:
+      oneOf:
+        - $ref: '#/components/schemas/GeoCircleViewLayer'
+        - $ref: '#/components/schemas/GeoHeatMapViewLayer'
+        - $ref: '#/components/schemas/GeoPointMapViewLayer'
+        - $ref: '#/components/schemas/GeoTrackMapViewLayer'
+      type: object
+    GeoViewLayerProperties:
+      properties:
+        type:
+          enum:
+            - heatmap
+            - circleMap
+            - pointMap
+            - trackMap
+          type: string
+      required:
+        - type
+      type: object
+    GeoViewProperties:
+      properties:
+        allowPanAndZoom:
+          default: true
+          description: If true, map zoom and pan controls are enabled on the dashboard view
+          type: boolean
+        center:
+          description: Coordinates of the center of the map
+          properties:
+            lat:
+              description: Latitude of the center of the map
+              format: double
+              type: number
+            lon:
+              description: Longitude of the center of the map
+              format: double
+              type: number
+          required:
+            - lat
+            - lon
+          type: object
+        colors:
+          description: Colors define color encoding of data into a visualization
+          items:
+            $ref: '#/components/schemas/DashboardColor'
+          type: array
+        detectCoordinateFields:
+          default: true
+          description: >-
+            If true, search results get automatically regroupped so that lon,lat
+            and value are treated as columns
+          type: boolean
+        latLonColumns:
+          $ref: '#/components/schemas/LatLonColumns'
+        layers:
+          description: List of individual layers shown in the map
+          items:
+            $ref: '#/components/schemas/GeoViewLayer'
+          type: array
+        mapStyle:
+          description: Define map type - regular, satellite etc.
+          type: string
+        note:
+          type: string
+        queries:
+          items:
+            $ref: '#/components/schemas/DashboardQuery'
+          type: array
+        s2Column:
+          description: String to define the column
+          type: string
+        shape:
+          enum:
+            - chronograf-v2
+          type: string
+        showNoteWhenEmpty:
+          description: If true, will display note when empty
+          type: boolean
+        type:
+          enum:
+            - geo
+          type: string
+        useS2CellID:
+          description: If true, S2 column is used to calculate lat/lon
+          type: boolean
+        zoom:
+          description: Zoom level used for initial display of the map
+          format: double
+          maximum: 28
+          minimum: 1
+          type: number
+      required:
+        - type
+        - shape
+        - queries
+        - note
+        - showNoteWhenEmpty
+        - center
+        - zoom
+        - allowPanAndZoom
+        - detectCoordinateFields
+        - layers
+      type: object
+    GreaterThreshold:
+      allOf:
+        - $ref: '#/components/schemas/ThresholdBase'
+        - properties:
+            type:
+              enum:
+                - greater
+              type: string
+            value:
+              format: float
+              type: number
+          required:
+            - type
+            - value
+          type: object
+    HTTPNotificationEndpoint:
+      allOf:
+        - $ref: '#/components/schemas/NotificationEndpointBase'
+        - properties:
+            authMethod:
+              enum:
+                - none
+                - basic
+                - bearer
+              type: string
+            contentTemplate:
+              type: string
+            headers:
+              additionalProperties:
+                type: string
+              description: Customized headers.
+              type: object
+            method:
+              enum:
+                - POST
+                - GET
+                - PUT
+              type: string
+            password:
+              type: string
+            token:
+              type: string
+            url:
+              type: string
+            username:
+              type: string
+          required:
+            - url
+            - authMethod
+            - method
+          type: object
+      type: object
+    HTTPNotificationRule:
+      allOf:
+        - $ref: '#/components/schemas/NotificationRuleBase'
+        - $ref: '#/components/schemas/HTTPNotificationRuleBase'
+    HTTPNotificationRuleBase:
+      properties:
+        type:
+          enum:
+            - http
+          type: string
+        url:
+          type: string
+      required:
+        - type
+      type: object
+    HealthCheck:
+      properties:
+        checks:
+          items:
+            $ref: '#/components/schemas/HealthCheck'
+          type: array
+        commit:
+          type: string
+        message:
+          type: string
+        name:
+          type: string
+        status:
+          enum:
+            - pass
+            - fail
+          type: string
+        version:
+          type: string
+      required:
+        - name
+        - status
+      type: object
+    HeatmapViewProperties:
+      properties:
+        binSize:
+          type: number
+        colors:
+          description: Colors define color encoding of data into a visualization
+          items:
+            type: string
+          type: array
+        generateXAxisTicks:
+          items:
+            type: string
+          type: array
+        generateYAxisTicks:
+          items:
+            type: string
+          type: array
+        legendColorizeRows:
+          type: boolean
+        legendHide:
+          type: boolean
+        legendOpacity:
+          format: float
+          type: number
+        legendOrientationThreshold:
+          type: integer
+        note:
+          type: string
+        queries:
+          items:
+            $ref: '#/components/schemas/DashboardQuery'
+          type: array
+        shape:
+          enum:
+            - chronograf-v2
+          type: string
+        showNoteWhenEmpty:
+          description: If true, will display note when empty
+          type: boolean
+        timeFormat:
+          type: string
+        type:
+          enum:
+            - heatmap
+          type: string
+        xAxisLabel:
+          type: string
+        xColumn:
+          type: string
+        xDomain:
+          items:
+            type: number
+          maxItems: 2
+          type: array
+        xPrefix:
+          type: string
+        xSuffix:
+          type: string
+        xTickStart:
+          format: float
+          type: number
+        xTickStep:
+          format: float
+          type: number
+        xTotalTicks:
+          type: integer
+        yAxisLabel:
+          type: string
+        yColumn:
+          type: string
+        yDomain:
+          items:
+            type: number
+          maxItems: 2
+          type: array
+        yPrefix:
+          type: string
+        ySuffix:
+          type: string
+        yTickStart:
+          format: float
+          type: number
+        yTickStep:
+          format: float
+          type: number
+        yTotalTicks:
+          type: integer
+      required:
+        - type
+        - queries
+        - colors
+        - shape
+        - note
+        - showNoteWhenEmpty
+        - xColumn
+        - yColumn
+        - xDomain
+        - yDomain
+        - xAxisLabel
+        - yAxisLabel
+        - xPrefix
+        - yPrefix
+        - xSuffix
+        - ySuffix
+        - binSize
+      type: object
+    HistogramViewProperties:
+      properties:
+        binCount:
+          type: integer
+        colors:
+          description: Colors define color encoding of data into a visualization
+          items:
+            $ref: '#/components/schemas/DashboardColor'
+          type: array
+        fillColumns:
+          items:
+            type: string
+          type: array
+        legendColorizeRows:
+          type: boolean
+        legendHide:
+          type: boolean
+        legendOpacity:
+          format: float
+          type: number
+        legendOrientationThreshold:
+          type: integer
+        note:
+          type: string
+        position:
+          enum:
+            - overlaid
+            - stacked
+          type: string
+        queries:
+          items:
+            $ref: '#/components/schemas/DashboardQuery'
+          type: array
+        shape:
+          enum:
+            - chronograf-v2
+          type: string
+        showNoteWhenEmpty:
+          description: If true, will display note when empty
+          type: boolean
+        type:
+          enum:
+            - histogram
+          type: string
+        xAxisLabel:
+          type: string
+        xColumn:
+          type: string
+        xDomain:
+          items:
+            format: float
+            type: number
+          type: array
+      required:
+        - type
+        - queries
+        - colors
+        - shape
+        - note
+        - showNoteWhenEmpty
+        - xColumn
+        - fillColumns
+        - xDomain
+        - xAxisLabel
+        - position
+        - binCount
+      type: object
+    Identifier:
+      description: A valid Flux identifier
+      properties:
+        name:
+          type: string
+        type:
+          $ref: '#/components/schemas/NodeType'
+      type: object
+    ImportDeclaration:
+      description: Declares a package import
+      properties:
+        as:
+          $ref: '#/components/schemas/Identifier'
+        path:
+          $ref: '#/components/schemas/StringLiteral'
+        type:
+          $ref: '#/components/schemas/NodeType'
+      type: object
+    IndexExpression:
+      description: Represents indexing into an array
+      properties:
+        array:
+          $ref: '#/components/schemas/Expression'
+        index:
+          $ref: '#/components/schemas/Expression'
+        type:
+          $ref: '#/components/schemas/NodeType'
+      type: object
+    IntegerLiteral:
+      description: Represents integer numbers
+      properties:
+        type:
+          $ref: '#/components/schemas/NodeType'
+        value:
+          type: string
+      type: object
+    IsOnboarding:
+      properties:
+        allowed:
+          description: >-
+            True means that the influxdb instance has NOT had initial setup;
+            false means that the database has been setup.
+          type: boolean
+      type: object
+    Label:
+      properties:
+        id:
+          readOnly: true
+          type: string
+        name:
+          type: string
+        orgID:
+          readOnly: true
+          type: string
+        properties:
+          additionalProperties:
+            type: string
+          description: >-
+            Key/Value pairs associated with this label. Keys can be removed by
+            sending an update with an empty value.
+          example:
+            color: ffb3b3
+            description: this is a description
+          type: object
+      type: object
+    LabelCreateRequest:
+      properties:
+        name:
+          type: string
+        orgID:
+          type: string
+        properties:
+          additionalProperties:
+            type: string
+          description: >-
+            Key/Value pairs associated with this label. Keys can be removed by
+            sending an update with an empty value.
+          example:
+            color: ffb3b3
+            description: this is a description
+          type: object
+      required:
+        - orgID
+        - name
+      type: object
+    LabelMapping:
+      properties:
+        labelID:
+          type: string
+      type: object
+    LabelResponse:
+      properties:
+        label:
+          $ref: '#/components/schemas/Label'
+        links:
+          $ref: '#/components/schemas/Links'
+      type: object
+    LabelUpdate:
+      properties:
+        name:
+          type: string
+        properties:
+          additionalProperties:
+            type: string
+          description: >-
+            Key/Value pairs associated with this label. Keys can be removed by
+            sending an update with an empty value.
+          example:
+            color: ffb3b3
+            description: this is a description
+          type: object
+      type: object
+    Labels:
+      items:
+        $ref: '#/components/schemas/Label'
+      type: array
+    LabelsResponse:
+      properties:
+        labels:
+          $ref: '#/components/schemas/Labels'
+        links:
+          $ref: '#/components/schemas/Links'
+      type: object
+    LanguageRequest:
+      description: Flux query to be analyzed.
+      properties:
+        query:
+          description: Flux query script to be analyzed
+          type: string
+      required:
+        - query
+      type: object
+    LatLonColumn:
+      description: Object type for key and column definitions
+      properties:
+        column:
+          description: Column to look up Lat/Lon
+          type: string
+        key:
+          description: Key to determine whether the column is tag/field
+          type: string
+      required:
+        - key
+        - column
+      type: object
+    LatLonColumns:
+      description: Object type to define lat/lon columns
+      properties:
+        lat:
+          $ref: '#/components/schemas/LatLonColumn'
+        lon:
+          $ref: '#/components/schemas/LatLonColumn'
+      required:
+        - lat
+        - lon
+      type: object
+    LegacyAuthorizationPostRequest:
+      allOf:
+        - $ref: '#/components/schemas/AuthorizationUpdateRequest'
+        - properties:
+            orgID:
+              description: ID of org that authorization is scoped to.
+              type: string
+            permissions:
+              description: >-
+                List of permissions for an auth.  An auth must have at least one
+                Permission.
+              items:
+                $ref: '#/components/schemas/Permission'
+              minItems: 1
+              type: array
+            token:
+              description: Token (name) of the authorization
+              type: string
+            userID:
+              description: ID of user that authorization is scoped to.
+              type: string
+          type: object
+      required:
+        - orgID
+        - permissions
+    LesserThreshold:
+      allOf:
+        - $ref: '#/components/schemas/ThresholdBase'
+        - properties:
+            type:
+              enum:
+                - lesser
+              type: string
+            value:
+              format: float
+              type: number
+          required:
+            - type
+            - value
+          type: object
+    LinePlusSingleStatProperties:
+      properties:
+        axes:
+          $ref: '#/components/schemas/Axes'
+        colors:
+          description: Colors define color encoding of data into a visualization
+          items:
+            $ref: '#/components/schemas/DashboardColor'
+          type: array
+        decimalPlaces:
+          $ref: '#/components/schemas/DecimalPlaces'
+        generateXAxisTicks:
+          items:
+            type: string
+          type: array
+        generateYAxisTicks:
+          items:
+            type: string
+          type: array
+        hoverDimension:
+          enum:
+            - auto
+            - x
+            - 'y'
+            - xy
+          type: string
+        legendColorizeRows:
+          type: boolean
+        legendHide:
+          type: boolean
+        legendOpacity:
+          format: float
+          type: number
+        legendOrientationThreshold:
+          type: integer
+        note:
+          type: string
+        position:
+          enum:
+            - overlaid
+            - stacked
+          type: string
+        prefix:
+          type: string
+        queries:
+          items:
+            $ref: '#/components/schemas/DashboardQuery'
+          type: array
+        shadeBelow:
+          type: boolean
+        shape:
+          enum:
+            - chronograf-v2
+          type: string
+        showNoteWhenEmpty:
+          description: If true, will display note when empty
+          type: boolean
+        staticLegend:
+          $ref: '#/components/schemas/StaticLegend'
+        suffix:
+          type: string
+        timeFormat:
+          type: string
+        type:
+          enum:
+            - line-plus-single-stat
+          type: string
+        xColumn:
+          type: string
+        xTickStart:
+          format: float
+          type: number
+        xTickStep:
+          format: float
+          type: number
+        xTotalTicks:
+          type: integer
+        yColumn:
+          type: string
+        yTickStart:
+          format: float
+          type: number
+        yTickStep:
+          format: float
+          type: number
+        yTotalTicks:
+          type: integer
+      required:
+        - type
+        - queries
+        - shape
+        - axes
+        - colors
+        - note
+        - showNoteWhenEmpty
+        - prefix
+        - suffix
+        - decimalPlaces
+        - position
+      type: object
+    LineProtocolError:
+      properties:
+        code:
+          description: Code is the machine-readable error code.
+          enum:
+            - internal error
+            - not found
+            - conflict
+            - invalid
+            - empty value
+            - unavailable
+          readOnly: true
+          type: string
+        err:
+          description: >-
+            Stack of errors that occurred during processing of the request.
+            Useful for debugging.
+          readOnly: true
+          type: string
+        line:
+          description: First line in the request body that contains malformed data.
+          format: int32
+          readOnly: true
+          type: integer
+        message:
+          description: Human-readable message.
+          readOnly: true
+          type: string
+        op:
+          description: >-
+            Describes the logical code operation when the error occurred. Useful
+            for debugging.
+          readOnly: true
+          type: string
+      required:
+        - code
+    LineProtocolLengthError:
+      properties:
+        code:
+          description: Code is the machine-readable error code.
+          enum:
+            - invalid
+          readOnly: true
+          type: string
+        message:
+          description: Human-readable message.
+          readOnly: true
+          type: string
+      required:
+        - code
+        - message
+    Link:
+      description: URI of resource.
+      format: uri
+      readOnly: true
+      type: string
+    Links:
+      properties:
+        next:
+          $ref: '#/components/schemas/Link'
+        prev:
+          $ref: '#/components/schemas/Link'
+        self:
+          $ref: '#/components/schemas/Link'
+      required:
+        - self
+      type: object
+    LogEvent:
+      properties:
+        message:
+          description: A description of the event that occurred.
+          example: Halt and catch fire
+          readOnly: true
+          type: string
+        runID:
+          description: the ID of the task that logged
+          readOnly: true
+          type: string
+        time:
+          description: Time event occurred, RFC3339Nano.
+          format: date-time
+          readOnly: true
+          type: string
+      type: object
+    LogicalExpression:
+      description: >-
+        Represents the rule conditions that collectively evaluate to either true
+        or false
+      properties:
+        left:
+          $ref: '#/components/schemas/Expression'
+        operator:
+          type: string
+        right:
+          $ref: '#/components/schemas/Expression'
+        type:
+          $ref: '#/components/schemas/NodeType'
+      type: object
+    Logs:
+      properties:
+        events:
+          items:
+            $ref: '#/components/schemas/LogEvent'
+          readOnly: true
+          type: array
+      type: object
+    MapVariableProperties:
+      properties:
+        type:
+          enum:
+            - map
+          type: string
+        values:
+          additionalProperties:
+            type: string
+          type: object
+    MarkdownViewProperties:
+      properties:
+        note:
+          type: string
+        shape:
+          enum:
+            - chronograf-v2
+          type: string
+        type:
+          enum:
+            - markdown
+          type: string
+      required:
+        - type
+        - shape
+        - note
+      type: object
+    MemberAssignment:
+      description: Object property assignment
+      properties:
+        init:
+          $ref: '#/components/schemas/Expression'
+        member:
+          $ref: '#/components/schemas/MemberExpression'
+        type:
+          $ref: '#/components/schemas/NodeType'
+      type: object
+    MemberExpression:
+      description: Represents accessing a property of an object
+      properties:
+        object:
+          $ref: '#/components/schemas/Expression'
+        property:
+          $ref: '#/components/schemas/PropertyKey'
+        type:
+          $ref: '#/components/schemas/NodeType'
+      type: object
+    MetadataBackup:
+      properties:
+        buckets:
+          $ref: '#/components/schemas/BucketMetadataManifests'
+        kv:
+          format: binary
+          type: string
+        sql:
+          format: binary
+          type: string
+      required:
+        - kv
+        - sql
+        - buckets
+      type: object
+    MosaicViewProperties:
+      properties:
+        colors:
+          description: Colors define color encoding of data into a visualization
+          items:
+            type: string
+          type: array
+        fillColumns:
+          items:
+            type: string
+          type: array
+        generateXAxisTicks:
+          items:
+            type: string
+          type: array
+        hoverDimension:
+          enum:
+            - auto
+            - x
+            - 'y'
+            - xy
+          type: string
+        legendColorizeRows:
+          type: boolean
+        legendHide:
+          type: boolean
+        legendOpacity:
+          format: float
+          type: number
+        legendOrientationThreshold:
+          type: integer
+        note:
+          type: string
+        queries:
+          items:
+            $ref: '#/components/schemas/DashboardQuery'
+          type: array
+        shape:
+          enum:
+            - chronograf-v2
+          type: string
+        showNoteWhenEmpty:
+          description: If true, will display note when empty
+          type: boolean
+        timeFormat:
+          type: string
+        type:
+          enum:
+            - mosaic
+          type: string
+        xAxisLabel:
+          type: string
+        xColumn:
+          type: string
+        xDomain:
+          items:
+            type: number
+          maxItems: 2
+          type: array
+        xPrefix:
+          type: string
+        xSuffix:
+          type: string
+        xTickStart:
+          format: float
+          type: number
+        xTickStep:
+          format: float
+          type: number
+        xTotalTicks:
+          type: integer
+        yAxisLabel:
+          type: string
+        yDomain:
+          items:
+            type: number
+          maxItems: 2
+          type: array
+        yLabelColumnSeparator:
+          type: string
+        yLabelColumns:
+          items:
+            type: string
+          type: array
+        yPrefix:
+          type: string
+        ySeriesColumns:
+          items:
+            type: string
+          type: array
+        ySuffix:
+          type: string
+      required:
+        - type
+        - queries
+        - colors
+        - shape
+        - note
+        - showNoteWhenEmpty
+        - xColumn
+        - ySeriesColumns
+        - fillColumns
+        - xDomain
+        - yDomain
+        - xAxisLabel
+        - yAxisLabel
+        - xPrefix
+        - yPrefix
+        - xSuffix
+        - ySuffix
+      type: object
+    Node:
+      oneOf:
+        - $ref: '#/components/schemas/Expression'
+        - $ref: '#/components/schemas/Block'
+    NodeType:
+      description: Type of AST node
+      type: string
+    NotificationEndpoint:
+      allOf:
+        - $ref: '#/components/schemas/NotificationEndpointDiscriminator'
+    NotificationEndpointBase:
+      properties:
+        createdAt:
+          format: date-time
+          readOnly: true
+          type: string
+        description:
+          description: An optional description of the notification endpoint.
+          type: string
+        id:
+          type: string
+        labels:
+          $ref: '#/components/schemas/Labels'
+        links:
+          example:
+            labels: /api/v2/notificationEndpoints/1/labels
+            members: /api/v2/notificationEndpoints/1/members
+            owners: /api/v2/notificationEndpoints/1/owners
+            self: /api/v2/notificationEndpoints/1
+          properties:
+            labels:
+              $ref: '#/components/schemas/Link'
+              description: URL to retrieve labels for this endpoint.
+            members:
+              $ref: '#/components/schemas/Link'
+              description: URL to retrieve members for this endpoint.
+            owners:
+              $ref: '#/components/schemas/Link'
+              description: URL to retrieve owners for this endpoint.
+            self:
+              $ref: '#/components/schemas/Link'
+              description: URL for this endpoint.
+          readOnly: true
+          type: object
+        name:
+          type: string
+        orgID:
+          type: string
+        status:
+          default: active
+          description: The status of the endpoint.
+          enum:
+            - active
+            - inactive
+          type: string
+        type:
+          $ref: '#/components/schemas/NotificationEndpointType'
+        updatedAt:
+          format: date-time
+          readOnly: true
+          type: string
+        userID:
+          type: string
+      required:
+        - type
+        - name
+      type: object
+    NotificationEndpointDiscriminator:
+      discriminator:
+        mapping:
+          http: '#/components/schemas/HTTPNotificationEndpoint'
+          pagerduty: '#/components/schemas/PagerDutyNotificationEndpoint'
+          slack: '#/components/schemas/SlackNotificationEndpoint'
+          telegram: '#/components/schemas/TelegramNotificationEndpoint'
+        propertyName: type
+      oneOf:
+        - $ref: '#/components/schemas/SlackNotificationEndpoint'
+        - $ref: '#/components/schemas/PagerDutyNotificationEndpoint'
+        - $ref: '#/components/schemas/HTTPNotificationEndpoint'
+        - $ref: '#/components/schemas/TelegramNotificationEndpoint'
+    NotificationEndpointType:
+      enum:
+        - slack
+        - pagerduty
+        - http
+        - telegram
+      type: string
+    NotificationEndpointUpdate:
+      properties:
+        description:
+          type: string
+        name:
+          type: string
+        status:
+          enum:
+            - active
+            - inactive
+          type: string
+      type: object
+    NotificationEndpoints:
+      properties:
+        links:
+          $ref: '#/components/schemas/Links'
+        notificationEndpoints:
+          items:
+            $ref: '#/components/schemas/NotificationEndpoint'
+          type: array
+    NotificationRule:
+      allOf:
+        - $ref: '#/components/schemas/NotificationRuleDiscriminator'
+    NotificationRuleBase:
+      properties:
+        createdAt:
+          format: date-time
+          readOnly: true
+          type: string
+        description:
+          description: An optional description of the notification rule.
+          type: string
+        endpointID:
+          type: string
+        every:
+          description: The notification repetition interval.
+          type: string
+        id:
+          readOnly: true
+          type: string
+        labels:
+          $ref: '#/components/schemas/Labels'
+        lastRunError:
+          readOnly: true
+          type: string
+        lastRunStatus:
+          enum:
+            - failed
+            - success
+            - canceled
+          readOnly: true
+          type: string
+        latestCompleted:
+          description: >-
+            Timestamp (in RFC3339 date/time
+            format](https://datatracker.ietf.org/doc/html/rfc3339)) of the
+            latest scheduled and completed run.
+          format: date-time
+          readOnly: true
+          type: string
+        limit:
+          description: >-
+            Don't notify me more than <limit> times every <limitEvery> seconds.
+            If set, limitEvery cannot be empty.
+          type: integer
+        limitEvery:
+          description: >-
+            Don't notify me more than <limit> times every <limitEvery> seconds.
+            If set, limit cannot be empty.
+          type: integer
+        links:
+          example:
+            labels: /api/v2/notificationRules/1/labels
+            members: /api/v2/notificationRules/1/members
+            owners: /api/v2/notificationRules/1/owners
+            query: /api/v2/notificationRules/1/query
+            self: /api/v2/notificationRules/1
+          properties:
+            labels:
+              $ref: '#/components/schemas/Link'
+              description: URL to retrieve labels for this notification rule.
+            members:
+              $ref: '#/components/schemas/Link'
+              description: URL to retrieve members for this notification rule.
+            owners:
+              $ref: '#/components/schemas/Link'
+              description: URL to retrieve owners for this notification rule.
+            query:
+              $ref: '#/components/schemas/Link'
+              description: URL to retrieve flux script for this notification rule.
+            self:
+              $ref: '#/components/schemas/Link'
+              description: URL for this endpoint.
+          readOnly: true
+          type: object
+        name:
+          description: Human-readable name describing the notification rule.
+          type: string
+        offset:
+          description: Duration to delay after the schedule, before executing check.
+          type: string
+        orgID:
+          description: The ID of the organization that owns this notification rule.
+          type: string
+        ownerID:
+          description: The ID of creator used to create this notification rule.
+          readOnly: true
+          type: string
+        runbookLink:
+          type: string
+        sleepUntil:
+          type: string
+        status:
+          $ref: '#/components/schemas/TaskStatusType'
+        statusRules:
+          description: List of status rules the notification rule attempts to match.
+          items:
+            $ref: '#/components/schemas/StatusRule'
+          minItems: 1
+          type: array
+        tagRules:
+          description: List of tag rules the notification rule attempts to match.
+          items:
+            $ref: '#/components/schemas/TagRule'
+          type: array
+        taskID:
+          description: The ID of the task associated with this notification rule.
+          type: string
+        updatedAt:
+          format: date-time
+          readOnly: true
+          type: string
+      required:
+        - orgID
+        - status
+        - name
+        - statusRules
+        - endpointID
+      type: object
+    NotificationRuleDiscriminator:
+      discriminator:
+        mapping:
+          http: '#/components/schemas/HTTPNotificationRule'
+          pagerduty: '#/components/schemas/PagerDutyNotificationRule'
+          slack: '#/components/schemas/SlackNotificationRule'
+          smtp: '#/components/schemas/SMTPNotificationRule'
+          telegram: '#/components/schemas/TelegramNotificationRule'
+        propertyName: type
+      oneOf:
+        - $ref: '#/components/schemas/SlackNotificationRule'
+        - $ref: '#/components/schemas/SMTPNotificationRule'
+        - $ref: '#/components/schemas/PagerDutyNotificationRule'
+        - $ref: '#/components/schemas/HTTPNotificationRule'
+        - $ref: '#/components/schemas/TelegramNotificationRule'
+    NotificationRuleUpdate:
+      properties:
+        description:
+          type: string
+        name:
+          type: string
+        status:
+          enum:
+            - active
+            - inactive
+          type: string
+      type: object
+    NotificationRules:
+      properties:
+        links:
+          $ref: '#/components/schemas/Links'
+        notificationRules:
+          items:
+            $ref: '#/components/schemas/NotificationRule'
+          type: array
+    ObjectExpression:
+      description: Allows the declaration of an anonymous object within a declaration
+      properties:
+        properties:
+          description: Object properties
+          items:
+            $ref: '#/components/schemas/Property'
+          type: array
+        type:
+          $ref: '#/components/schemas/NodeType'
+      type: object
+    OnboardingRequest:
+      properties:
+        bucket:
+          type: string
+        org:
+          type: string
+        password:
+          type: string
+        retentionPeriodHrs:
+          deprecated: true
+          description: >
+            Retention period *in nanoseconds* for the new bucket. This key's
+            name has been misleading since OSS 2.0 GA, please transition to use
+            `retentionPeriodSeconds`
+          type: integer
+        retentionPeriodSeconds:
+          format: int64
+          type: integer
+        token:
+          description: >
+            Authentication token to set on the initial user. If not specified,
+            the server will generate a token.
+          type: string
+        username:
+          type: string
+      required:
+        - username
+        - org
+        - bucket
+      type: object
+    OnboardingResponse:
+      properties:
+        auth:
+          $ref: '#/components/schemas/Authorization'
+        bucket:
+          $ref: '#/components/schemas/Bucket'
+        org:
+          $ref: '#/components/schemas/Organization'
+        user:
+          $ref: '#/components/schemas/UserResponse'
+      type: object
+    OptionStatement:
+      description: A single variable declaration
+      properties:
+        assignment:
+          oneOf:
+            - $ref: '#/components/schemas/VariableAssignment'
+            - $ref: '#/components/schemas/MemberAssignment'
+        type:
+          $ref: '#/components/schemas/NodeType'
+      type: object
+    Organization:
+      properties:
+        createdAt:
+          format: date-time
+          readOnly: true
+          type: string
+        description:
+          type: string
+        id:
+          readOnly: true
+          type: string
+        links:
+          example:
+            buckets: /api/v2/buckets?org=myorg
+            dashboards: /api/v2/dashboards?org=myorg
+            labels: /api/v2/orgs/1/labels
+            members: /api/v2/orgs/1/members
+            owners: /api/v2/orgs/1/owners
+            secrets: /api/v2/orgs/1/secrets
+            self: /api/v2/orgs/1
+            tasks: /api/v2/tasks?org=myorg
+          properties:
+            buckets:
+              $ref: '#/components/schemas/Link'
+            dashboards:
+              $ref: '#/components/schemas/Link'
+            labels:
+              $ref: '#/components/schemas/Link'
+            members:
+              $ref: '#/components/schemas/Link'
+            owners:
+              $ref: '#/components/schemas/Link'
+            secrets:
+              $ref: '#/components/schemas/Link'
+            self:
+              $ref: '#/components/schemas/Link'
+            tasks:
+              $ref: '#/components/schemas/Link'
+          readOnly: true
+          type: object
+        name:
+          type: string
+        status:
+          default: active
+          description: If inactive the organization is inactive.
+          enum:
+            - active
+            - inactive
+          type: string
+        updatedAt:
+          format: date-time
+          readOnly: true
+          type: string
+      required:
+        - name
+    Organizations:
+      properties:
+        links:
+          $ref: '#/components/schemas/Links'
+        orgs:
+          items:
+            $ref: '#/components/schemas/Organization'
+          type: array
+      type: object
+    Package:
+      description: Represents a complete package source tree.
+      properties:
+        files:
+          description: Package files
+          items:
+            $ref: '#/components/schemas/File'
+          type: array
+        package:
+          description: Package name
+          type: string
+        path:
+          description: Package import path
+          type: string
+        type:
+          $ref: '#/components/schemas/NodeType'
+      type: object
+    PackageClause:
+      description: Defines a package identifier
+      properties:
+        name:
+          $ref: '#/components/schemas/Identifier'
+        type:
+          $ref: '#/components/schemas/NodeType'
+      type: object
+    PagerDutyNotificationEndpoint:
+      allOf:
+        - $ref: '#/components/schemas/NotificationEndpointBase'
+        - properties:
+            clientURL:
+              type: string
+            routingKey:
+              type: string
+          required:
+            - routingKey
+          type: object
+      type: object
+    PagerDutyNotificationRule:
+      allOf:
+        - $ref: '#/components/schemas/NotificationRuleBase'
+        - $ref: '#/components/schemas/PagerDutyNotificationRuleBase'
+    PagerDutyNotificationRuleBase:
+      properties:
+        messageTemplate:
+          type: string
+        type:
+          enum:
+            - pagerduty
+          type: string
+      required:
+        - type
+        - messageTemplate
+      type: object
+    ParenExpression:
+      description: Represents an expression wrapped in parenthesis
+      properties:
+        expression:
+          $ref: '#/components/schemas/Expression'
+        type:
+          $ref: '#/components/schemas/NodeType'
+      type: object
+    PasswordResetBody:
+      properties:
+        password:
+          type: string
+      required:
+        - password
+    PatchBucketRequest:
+      description: Updates to an existing bucket resource.
+      properties:
+        description:
+          type: string
+        name:
+          type: string
+        retentionRules:
+          $ref: '#/components/schemas/PatchRetentionRules'
+      type: object
+    PatchOrganizationRequest:
+      properties:
+        description:
+          description: New description to set on the organization
+          type: string
+        name:
+          description: New name to set on the organization
+          type: string
+      type: object
+    PatchRetentionRule:
+      description: Updates to a rule to expire or retain data.
+      properties:
+        everySeconds:
+          description: >-
+            Duration in seconds for how long data will be kept in the database.
+            0 means infinite.
+          example: 86400
+          format: int64
+          minimum: 0
+          type: integer
+        shardGroupDurationSeconds:
+          description: Shard duration measured in seconds.
+          format: int64
+          type: integer
+        type:
+          default: expire
+          enum:
+            - expire
+          type: string
+      required:
+        - type
+      type: object
+    PatchRetentionRules:
+      description: Updates to rules to expire or retain data. No rules means no updates.
+      items:
+        $ref: '#/components/schemas/PatchRetentionRule'
+      type: array
+    Permission:
+      properties:
+        action:
+          enum:
+            - read
+            - write
+          type: string
+        resource:
+          $ref: '#/components/schemas/Resource'
+      required:
+        - action
+        - resource
+    PipeExpression:
+      description: Call expression with pipe argument
+      properties:
+        argument:
+          $ref: '#/components/schemas/Expression'
+        call:
+          $ref: '#/components/schemas/CallExpression'
+        type:
+          $ref: '#/components/schemas/NodeType'
+      type: object
+    PipeLiteral:
+      description: >-
+        Represents a specialized literal value, indicating the left hand value
+        of a pipe expression
+      properties:
+        type:
+          $ref: '#/components/schemas/NodeType'
+      type: object
+    PostBucketRequest:
+      properties:
+        description:
+          type: string
+        name:
+          type: string
+        orgID:
+          type: string
+        retentionRules:
+          $ref: '#/components/schemas/RetentionRules'
+        rp:
+          type: string
+        schemaType:
+          $ref: '#/components/schemas/SchemaType'
+          default: implicit
+      required:
+        - orgID
+        - name
+        - retentionRules
+    PostCheck:
+      allOf:
+        - $ref: '#/components/schemas/CheckDiscriminator'
+    PostNotificationEndpoint:
+      allOf:
+        - $ref: '#/components/schemas/NotificationEndpointDiscriminator'
+    PostNotificationRule:
+      allOf:
+        - $ref: '#/components/schemas/NotificationRuleDiscriminator'
+    PostOrganizationRequest:
+      properties:
+        description:
+          type: string
+        name:
+          type: string
+      required:
+        - name
+      type: object
+    Property:
+      description: The value associated with a key
+      properties:
+        key:
+          $ref: '#/components/schemas/PropertyKey'
+        type:
+          $ref: '#/components/schemas/NodeType'
+        value:
+          $ref: '#/components/schemas/Expression'
+      type: object
+    PropertyKey:
+      oneOf:
+        - $ref: '#/components/schemas/Identifier'
+        - $ref: '#/components/schemas/StringLiteral'
+    Query:
+      description: Query influx using the Flux language
+      properties:
+        dialect:
+          $ref: '#/components/schemas/Dialect'
+        extern:
+          $ref: '#/components/schemas/File'
+        now:
+          description: >-
+            Specifies the time that should be reported as "now" in the query.
+            Default is the server's now time.
+          format: date-time
+          type: string
+        params:
+          additionalProperties: true
+          description: >
+            Enumeration of key/value pairs that respresent parameters to be
+            injected into query (can only specify either this field or extern
+            and not both)
+          type: object
+        query:
+          description: Query script to execute.
+          type: string
+        type:
+          description: The type of query. Must be "flux".
+          enum:
+            - flux
+          type: string
+      required:
+        - query
+      type: object
+    QueryEditMode:
+      enum:
+        - builder
+        - advanced
+      type: string
+    QueryVariableProperties:
+      properties:
+        type:
+          enum:
+            - query
+          type: string
+        values:
+          properties:
+            language:
+              type: string
+            query:
+              type: string
+          type: object
+    RangeThreshold:
+      allOf:
+        - $ref: '#/components/schemas/ThresholdBase'
+        - properties:
+            max:
+              format: float
+              type: number
+            min:
+              format: float
+              type: number
+            type:
+              enum:
+                - range
+              type: string
+            within:
+              type: boolean
+          required:
+            - type
+            - min
+            - max
+            - within
+          type: object
+    Ready:
+      properties:
+        started:
+          example: '2019-03-13T10:09:33.891196-04:00'
+          format: date-time
+          type: string
+        status:
+          enum:
+            - ready
+          type: string
+        up:
+          example: 14m45.911966424s
+          type: string
+      type: object
+    RegexpLiteral:
+      description: >-
+        Expressions begin and end with `/` and are regular expressions with
+        syntax accepted by RE2
+      properties:
+        type:
+          $ref: '#/components/schemas/NodeType'
+        value:
+          type: string
+      type: object
+    RemoteConnection:
+      properties:
+        allowInsecureTLS:
+          default: false
+          type: boolean
+        description:
+          type: string
+        id:
+          type: string
+        name:
+          type: string
+        orgID:
+          type: string
+        remoteOrgID:
+          type: string
+        remoteURL:
+          format: uri
+          type: string
+      required:
+        - id
+        - name
+        - orgID
+        - remoteURL
+        - remoteOrgID
+        - allowInsecureTLS
+      type: object
+    RemoteConnectionCreationRequest:
+      properties:
+        allowInsecureTLS:
+          default: false
+          type: boolean
+        description:
+          type: string
+        name:
+          type: string
+        orgID:
+          type: string
+        remoteAPIToken:
+          type: string
+        remoteOrgID:
+          type: string
+        remoteURL:
+          format: uri
+          type: string
+      required:
+        - name
+        - orgID
+        - remoteURL
+        - remoteAPIToken
+        - remoteOrgID
+        - allowInsecureTLS
+      type: object
+    RemoteConnectionUpdateRequest:
+      properties:
+        allowInsecureTLS:
+          default: false
+          type: boolean
+        description:
+          type: string
+        name:
+          type: string
+        remoteAPIToken:
+          type: string
+        remoteOrgID:
+          type: string
+        remoteURL:
+          format: uri
+          type: string
+      type: object
+    RemoteConnections:
+      properties:
+        remotes:
+          items:
+            $ref: '#/components/schemas/RemoteConnection'
+          type: array
+      type: object
+    RenamableField:
+      description: Describes a field that can be renamed and made visible or invisible.
+      properties:
+        displayName:
+          description: The name that a field is renamed to by the user.
+          type: string
+        internalName:
+          description: The calculated name of a field.
+          readOnly: true
+          type: string
+        visible:
+          description: Indicates whether this field should be visible on the table.
+          type: boolean
+      type: object
+    Replication:
+      properties:
+        currentQueueSizeBytes:
+          format: int64
+          type: integer
+        description:
+          type: string
+        dropNonRetryableData:
+          type: boolean
+        id:
+          type: string
+        latestErrorMessage:
+          type: string
+        latestResponseCode:
+          type: integer
+        localBucketID:
+          type: string
+        maxQueueSizeBytes:
+          format: int64
+          type: integer
+        name:
+          type: string
+        orgID:
+          type: string
+        remoteBucketID:
+          type: string
+        remoteID:
+          type: string
+      required:
+        - id
+        - name
+        - remoteID
+        - orgID
+        - localBucketID
+        - remoteBucketID
+        - maxQueueSizeBytes
+        - currentQueueSizeBytes
+      type: object
+    ReplicationCreationRequest:
+      properties:
+        description:
+          type: string
+        dropNonRetryableData:
+          default: false
+          type: boolean
+        localBucketID:
+          type: string
+        maxQueueSizeBytes:
+          default: 67108860
+          format: int64
+          minimum: 33554430
+          type: integer
+        name:
+          type: string
+        orgID:
+          type: string
+        remoteBucketID:
+          type: string
+        remoteID:
+          type: string
+      required:
+        - name
+        - orgID
+        - remoteID
+        - localBucketID
+        - remoteBucketID
+        - maxQueueSizeBytes
+      type: object
+    ReplicationUpdateRequest:
+      properties:
+        description:
+          type: string
+        dropNonRetryableData:
+          type: boolean
+        maxQueueSizeBytes:
+          format: int64
+          minimum: 33554430
+          type: integer
+        name:
+          type: string
+        remoteBucketID:
+          type: string
+        remoteID:
+          type: string
+      type: object
+    Replications:
+      properties:
+        replications:
+          items:
+            $ref: '#/components/schemas/Replication'
+          type: array
+      type: object
+    Resource:
+      properties:
+        id:
+          description: >-
+            If ID is set that is a permission for a specific resource. if it is
+            not set it is a permission for all resources of that resource type.
+          type: string
+        name:
+          description: Optional name of the resource if the resource has a name field.
+          type: string
+        org:
+          description: Optional name of the organization of the organization with orgID.
+          type: string
+        orgID:
+          description: >-
+            If orgID is set that is a permission for all resources owned my that
+            org. if it is not set it is a permission for all resources of that
+            resource type.
+          type: string
+        type:
+          enum:
+            - authorizations
+            - buckets
+            - dashboards
+            - orgs
+            - sources
+            - tasks
+            - telegrafs
+            - users
+            - variables
+            - scrapers
+            - secrets
+            - labels
+            - views
+            - documents
+            - notificationRules
+            - notificationEndpoints
+            - checks
+            - dbrp
+            - notebooks
+            - annotations
+            - remotes
+            - replications
+          type: string
+      required:
+        - type
+      type: object
+    ResourceMember:
+      allOf:
+        - $ref: '#/components/schemas/UserResponse'
+        - properties:
+            role:
+              default: member
+              enum:
+                - member
+              type: string
+          type: object
+    ResourceMembers:
+      properties:
+        links:
+          properties:
+            self:
+              format: uri
+              type: string
+          type: object
+        users:
+          items:
+            $ref: '#/components/schemas/ResourceMember'
+          type: array
+      type: object
+    ResourceOwner:
+      allOf:
+        - $ref: '#/components/schemas/UserResponse'
+        - properties:
+            role:
+              default: owner
+              enum:
+                - owner
+              type: string
+          type: object
+    ResourceOwners:
+      properties:
+        links:
+          properties:
+            self:
+              format: uri
+              type: string
+          type: object
+        users:
+          items:
+            $ref: '#/components/schemas/ResourceOwner'
+          type: array
+      type: object
+    RestoredBucketMappings:
+      properties:
+        id:
+          description: New ID of the restored bucket
+          type: string
+        name:
+          type: string
+        shardMappings:
+          $ref: '#/components/schemas/BucketShardMappings'
+      required:
+        - id
+        - name
+        - shardMappings
+      type: object
+    RetentionPolicyManifest:
+      properties:
+        duration:
+          format: int64
+          type: integer
+        name:
+          type: string
+        replicaN:
+          type: integer
+        shardGroupDuration:
+          format: int64
+          type: integer
+        shardGroups:
+          $ref: '#/components/schemas/ShardGroupManifests'
+        subscriptions:
+          $ref: '#/components/schemas/SubscriptionManifests'
+      required:
+        - name
+        - replicaN
+        - duration
+        - shardGroupDuration
+        - shardGroups
+        - subscriptions
+      type: object
+    RetentionPolicyManifests:
+      items:
+        $ref: '#/components/schemas/RetentionPolicyManifest'
+      type: array
+    RetentionRule:
+      properties:
+        everySeconds:
+          description: >-
+            Duration in seconds for how long data will be kept in the database.
+            0 means infinite.
+          example: 86400
+          format: int64
+          minimum: 0
+          type: integer
+        shardGroupDurationSeconds:
+          description: Shard duration measured in seconds.
+          format: int64
+          type: integer
+        type:
+          default: expire
+          enum:
+            - expire
+          type: string
+      required:
+        - type
+        - everySeconds
+      type: object
+    RetentionRules:
+      description: Rules to expire or retain data.  No rules means data never expires.
+      items:
+        $ref: '#/components/schemas/RetentionRule'
+      type: array
+    ReturnStatement:
+      description: Defines an expression to return
+      properties:
+        argument:
+          $ref: '#/components/schemas/Expression'
+        type:
+          $ref: '#/components/schemas/NodeType'
+      type: object
+    Routes:
+      properties:
+        authorizations:
+          format: uri
+          type: string
+        buckets:
+          format: uri
+          type: string
+        dashboards:
+          format: uri
+          type: string
+        external:
+          properties:
+            statusFeed:
+              format: uri
+              type: string
+          type: object
+        flags:
+          format: uri
+          type: string
+        me:
+          format: uri
+          type: string
+        orgs:
+          format: uri
+          type: string
+        query:
+          properties:
+            analyze:
+              format: uri
+              type: string
+            ast:
+              format: uri
+              type: string
+            self:
+              format: uri
+              type: string
+            suggestions:
+              format: uri
+              type: string
+          type: object
+        setup:
+          format: uri
+          type: string
+        signin:
+          format: uri
+          type: string
+        signout:
+          format: uri
+          type: string
+        sources:
+          format: uri
+          type: string
+        system:
+          properties:
+            debug:
+              format: uri
+              type: string
+            health:
+              format: uri
+              type: string
+            metrics:
+              format: uri
+              type: string
+          type: object
+        tasks:
+          format: uri
+          type: string
+        telegrafs:
+          format: uri
+          type: string
+        users:
+          format: uri
+          type: string
+        variables:
+          format: uri
+          type: string
+        write:
+          format: uri
+          type: string
+    RuleStatusLevel:
+      description: The state to record if check matches a criteria.
+      enum:
+        - UNKNOWN
+        - OK
+        - INFO
+        - CRIT
+        - WARN
+        - ANY
+      type: string
+    Run:
+      properties:
+        finishedAt:
+          description: Time run finished executing, RFC3339Nano.
+          format: date-time
+          readOnly: true
+          type: string
+        id:
+          readOnly: true
+          type: string
+        links:
+          example:
+            retry: /api/v2/tasks/1/runs/1/retry
+            self: /api/v2/tasks/1/runs/1
+            task: /api/v2/tasks/1
+          properties:
+            retry:
+              format: uri
+              type: string
+            self:
+              format: uri
+              type: string
+            task:
+              format: uri
+              type: string
+          readOnly: true
+          type: object
+        log:
+          description: An array of logs associated with the run.
+          items:
+            $ref: '#/components/schemas/LogEvent'
+          readOnly: true
+          type: array
+        requestedAt:
+          description: Time run was manually requested, RFC3339Nano.
+          format: date-time
+          readOnly: true
+          type: string
+        scheduledFor:
+          description: Time used for run's "now" option, RFC3339.
+          format: date-time
+          type: string
+        startedAt:
+          description: Time run started executing, RFC3339Nano.
+          format: date-time
+          readOnly: true
+          type: string
+        status:
+          enum:
+            - scheduled
+            - started
+            - failed
+            - success
+            - canceled
+          readOnly: true
+          type: string
+        taskID:
+          readOnly: true
+          type: string
+    RunManually:
+      properties:
+        scheduledFor:
+          description: >-
+            Time used for run's "now" option, RFC3339.  Default is the server's
+            now time.
+          format: date-time
+          nullable: true
+          type: string
+    Runs:
+      properties:
+        links:
+          $ref: '#/components/schemas/Links'
+        runs:
+          items:
+            $ref: '#/components/schemas/Run'
+          type: array
+      type: object
+    SMTPNotificationRule:
+      allOf:
+        - $ref: '#/components/schemas/NotificationRuleBase'
+        - $ref: '#/components/schemas/SMTPNotificationRuleBase'
+    SMTPNotificationRuleBase:
+      properties:
+        bodyTemplate:
+          type: string
+        subjectTemplate:
+          type: string
+        to:
+          type: string
+        type:
+          enum:
+            - smtp
+          type: string
+      required:
+        - type
+        - subjectTemplate
+        - to
+      type: object
+    ScatterViewProperties:
+      properties:
+        colors:
+          description: Colors define color encoding of data into a visualization
+          items:
+            type: string
+          type: array
+        fillColumns:
+          items:
+            type: string
+          type: array
+        generateXAxisTicks:
+          items:
+            type: string
+          type: array
+        generateYAxisTicks:
+          items:
+            type: string
+          type: array
+        legendColorizeRows:
+          type: boolean
+        legendHide:
+          type: boolean
+        legendOpacity:
+          format: float
+          type: number
+        legendOrientationThreshold:
+          type: integer
+        note:
+          type: string
+        queries:
+          items:
+            $ref: '#/components/schemas/DashboardQuery'
+          type: array
+        shape:
+          enum:
+            - chronograf-v2
+          type: string
+        showNoteWhenEmpty:
+          description: If true, will display note when empty
+          type: boolean
+        symbolColumns:
+          items:
+            type: string
+          type: array
+        timeFormat:
+          type: string
+        type:
+          enum:
+            - scatter
+          type: string
+        xAxisLabel:
+          type: string
+        xColumn:
+          type: string
+        xDomain:
+          items:
+            type: number
+          maxItems: 2
+          type: array
+        xPrefix:
+          type: string
+        xSuffix:
+          type: string
+        xTickStart:
+          format: float
+          type: number
+        xTickStep:
+          format: float
+          type: number
+        xTotalTicks:
+          type: integer
+        yAxisLabel:
+          type: string
+        yColumn:
+          type: string
+        yDomain:
+          items:
+            type: number
+          maxItems: 2
+          type: array
+        yPrefix:
+          type: string
+        ySuffix:
+          type: string
+        yTickStart:
+          format: float
+          type: number
+        yTickStep:
+          format: float
+          type: number
+        yTotalTicks:
+          type: integer
+      required:
+        - type
+        - queries
+        - colors
+        - shape
+        - note
+        - showNoteWhenEmpty
+        - xColumn
+        - yColumn
+        - fillColumns
+        - symbolColumns
+        - xDomain
+        - yDomain
+        - xAxisLabel
+        - yAxisLabel
+        - xPrefix
+        - yPrefix
+        - xSuffix
+        - ySuffix
+      type: object
+    SchemaType:
+      enum:
+        - implicit
+        - explicit
+      type: string
+    ScraperTargetRequest:
+      properties:
+        allowInsecure:
+          default: false
+          description: Skip TLS verification on endpoint.
+          type: boolean
+        bucketID:
+          description: The ID of the bucket to write to.
+          type: string
+        name:
+          description: The name of the scraper target.
+          type: string
+        orgID:
+          description: The organization ID.
+          type: string
+        type:
+          description: The type of the metrics to be parsed.
+          enum:
+            - prometheus
+          type: string
+        url:
+          description: The URL of the metrics endpoint.
+          example: http://localhost:9090/metrics
+          type: string
+      type: object
+    ScraperTargetResponse:
+      allOf:
+        - $ref: '#/components/schemas/ScraperTargetRequest'
+        - properties:
+            bucket:
+              description: The bucket name.
+              type: string
+            id:
+              readOnly: true
+              type: string
+            links:
+              example:
+                bucket: /api/v2/buckets/1
+                members: /api/v2/scrapers/1/members
+                organization: /api/v2/orgs/1
+                owners: /api/v2/scrapers/1/owners
+                self: /api/v2/scrapers/1
+              properties:
+                bucket:
+                  $ref: '#/components/schemas/Link'
+                members:
+                  $ref: '#/components/schemas/Link'
+                organization:
+                  $ref: '#/components/schemas/Link'
+                owners:
+                  $ref: '#/components/schemas/Link'
+                self:
+                  $ref: '#/components/schemas/Link'
+              readOnly: true
+              type: object
+            org:
+              description: The name of the organization.
+              type: string
+          type: object
+      type: object
+    ScraperTargetResponses:
+      properties:
+        configurations:
+          items:
+            $ref: '#/components/schemas/ScraperTargetResponse'
+          type: array
+      type: object
+    SecretKeys:
+      properties:
+        secrets:
+          items:
+            type: string
+          type: array
+      type: object
+    SecretKeysResponse:
+      allOf:
+        - $ref: '#/components/schemas/SecretKeys'
+        - properties:
+            links:
+              properties:
+                org:
+                  type: string
+                self:
+                  type: string
+              readOnly: true
+              type: object
+          type: object
+    Secrets:
+      additionalProperties:
+        type: string
+      example:
+        apikey: abc123xyz
+    ShardGroupManifest:
+      properties:
+        deletedAt:
+          format: date-time
+          type: string
+        endTime:
+          format: date-time
+          type: string
+        id:
+          format: int64
+          type: integer
+        shards:
+          $ref: '#/components/schemas/ShardManifests'
+        startTime:
+          format: date-time
+          type: string
+        truncatedAt:
+          format: date-time
+          type: string
+      required:
+        - id
+        - startTime
+        - endTime
+        - shards
+      type: object
+    ShardGroupManifests:
+      items:
+        $ref: '#/components/schemas/ShardGroupManifest'
+      type: array
+    ShardManifest:
+      properties:
+        id:
+          format: int64
+          type: integer
+        shardOwners:
+          $ref: '#/components/schemas/ShardOwners'
+      required:
+        - id
+        - shardOwners
+      type: object
+    ShardManifests:
+      items:
+        $ref: '#/components/schemas/ShardManifest'
+      type: array
+    ShardOwner:
+      properties:
+        nodeID:
+          description: ID of the node that owns a shard.
+          format: int64
+          type: integer
+      required:
+        - nodeID
+      type: object
+    ShardOwners:
+      items:
+        $ref: '#/components/schemas/ShardOwner'
+      type: array
+    SimpleTableViewProperties:
+      properties:
+        note:
+          type: string
+        queries:
+          items:
+            $ref: '#/components/schemas/DashboardQuery'
+          type: array
+        shape:
+          enum:
+            - chronograf-v2
+          type: string
+        showAll:
+          type: boolean
+        showNoteWhenEmpty:
+          description: If true, will display note when empty
+          type: boolean
+        type:
+          enum:
+            - simple-table
+          type: string
+      required:
+        - type
+        - showAll
+        - queries
+        - shape
+        - note
+        - showNoteWhenEmpty
+      type: object
+    SingleStatViewProperties:
+      properties:
+        colors:
+          description: Colors define color encoding of data into a visualization
+          items:
+            $ref: '#/components/schemas/DashboardColor'
+          type: array
+        decimalPlaces:
+          $ref: '#/components/schemas/DecimalPlaces'
+        note:
+          type: string
+        prefix:
+          type: string
+        queries:
+          items:
+            $ref: '#/components/schemas/DashboardQuery'
+          type: array
+        shape:
+          enum:
+            - chronograf-v2
+          type: string
+        showNoteWhenEmpty:
+          description: If true, will display note when empty
+          type: boolean
+        staticLegend:
+          $ref: '#/components/schemas/StaticLegend'
+        suffix:
+          type: string
+        tickPrefix:
+          type: string
+        tickSuffix:
+          type: string
+        type:
+          enum:
+            - single-stat
+          type: string
+      required:
+        - type
+        - queries
+        - colors
+        - shape
+        - note
+        - showNoteWhenEmpty
+        - prefix
+        - tickPrefix
+        - suffix
+        - tickSuffix
+        - decimalPlaces
+      type: object
+    SlackNotificationEndpoint:
+      allOf:
+        - $ref: '#/components/schemas/NotificationEndpointBase'
+        - properties:
+            token:
+              description: Specifies the API token string. Specify either `URL` or `Token`.
+              type: string
+            url:
+              description: >-
+                Specifies the URL of the Slack endpoint. Specify either `URL` or
+                `Token`.
+              type: string
+          type: object
+      type: object
+    SlackNotificationRule:
+      allOf:
+        - $ref: '#/components/schemas/NotificationRuleBase'
+        - $ref: '#/components/schemas/SlackNotificationRuleBase'
+    SlackNotificationRuleBase:
+      properties:
+        channel:
+          type: string
+        messageTemplate:
+          type: string
+        type:
+          enum:
+            - slack
+          type: string
+      required:
+        - type
+        - messageTemplate
+      type: object
+    Source:
+      properties:
+        default:
+          type: boolean
+        defaultRP:
+          type: string
+        id:
+          type: string
+        insecureSkipVerify:
+          type: boolean
+        languages:
+          items:
+            enum:
+              - flux
+              - influxql
+            type: string
+          readOnly: true
+          type: array
+        links:
+          properties:
+            buckets:
+              type: string
+            health:
+              type: string
+            query:
+              type: string
+            self:
+              type: string
+          type: object
+        metaUrl:
+          format: uri
+          type: string
+        name:
+          type: string
+        orgID:
+          type: string
+        password:
+          type: string
+        sharedSecret:
+          type: string
+        telegraf:
+          type: string
+        token:
+          type: string
+        type:
+          enum:
+            - v1
+            - v2
+            - self
+          type: string
+        url:
+          format: uri
+          type: string
+        username:
+          type: string
+      type: object
+    Sources:
+      properties:
+        links:
+          properties:
+            self:
+              format: uri
+              type: string
+          type: object
+        sources:
+          items:
+            $ref: '#/components/schemas/Source'
+          type: array
+      type: object
+    Stack:
+      properties:
+        createdAt:
+          format: date-time
+          readOnly: true
+          type: string
+        events:
+          items:
+            properties:
+              description:
+                type: string
+              eventType:
+                type: string
+              name:
+                type: string
+              resources:
+                items:
+                  properties:
+                    apiVersion:
+                      type: string
+                    associations:
+                      items:
+                        properties:
+                          kind:
+                            $ref: '#/components/schemas/TemplateKind'
+                          metaName:
+                            type: string
+                        type: object
+                      type: array
+                    kind:
+                      $ref: '#/components/schemas/TemplateKind'
+                    links:
+                      properties:
+                        self:
+                          type: string
+                      type: object
+                    resourceID:
+                      type: string
+                    templateMetaName:
+                      type: string
+                  type: object
+                type: array
+              sources:
+                items:
+                  type: string
+                type: array
+              updatedAt:
+                format: date-time
+                readOnly: true
+                type: string
+              urls:
+                items:
+                  type: string
+                type: array
+            type: object
+          type: array
+        id:
+          type: string
+        orgID:
+          type: string
+      type: object
+    Statement:
+      oneOf:
+        - $ref: '#/components/schemas/BadStatement'
+        - $ref: '#/components/schemas/VariableAssignment'
+        - $ref: '#/components/schemas/MemberAssignment'
+        - $ref: '#/components/schemas/ExpressionStatement'
+        - $ref: '#/components/schemas/ReturnStatement'
+        - $ref: '#/components/schemas/OptionStatement'
+        - $ref: '#/components/schemas/BuiltinStatement'
+        - $ref: '#/components/schemas/TestStatement'
+    StaticLegend:
+      description: StaticLegend represents the options specific to the static legend
+      properties:
+        colorizeRows:
+          type: boolean
+        heightRatio:
+          format: float
+          type: number
+        opacity:
+          format: float
+          type: number
+        orientationThreshold:
+          type: integer
+        show:
+          type: boolean
+        valueAxis:
+          type: string
+        widthRatio:
+          format: float
+          type: number
+      type: object
+    StatusRule:
+      properties:
+        count:
+          type: integer
+        currentLevel:
+          $ref: '#/components/schemas/RuleStatusLevel'
+        period:
+          type: string
+        previousLevel:
+          $ref: '#/components/schemas/RuleStatusLevel'
+      type: object
+    StringLiteral:
+      description: Expressions begin and end with double quote marks
+      properties:
+        type:
+          $ref: '#/components/schemas/NodeType'
+        value:
+          type: string
+      type: object
+    SubscriptionManifest:
+      properties:
+        destinations:
+          items:
+            type: string
+          type: array
+        mode:
+          type: string
+        name:
+          type: string
+      required:
+        - name
+        - mode
+        - destinations
+      type: object
+    SubscriptionManifests:
+      items:
+        $ref: '#/components/schemas/SubscriptionManifest'
+      type: array
+    TableViewProperties:
+      properties:
+        colors:
+          description: Colors define color encoding of data into a visualization
+          items:
+            $ref: '#/components/schemas/DashboardColor'
+          type: array
+        decimalPlaces:
+          $ref: '#/components/schemas/DecimalPlaces'
+        fieldOptions:
+          description: >-
+            fieldOptions represent the fields retrieved by the query with
+            customization options
+          items:
+            $ref: '#/components/schemas/RenamableField'
+          type: array
+        note:
+          type: string
+        queries:
+          items:
+            $ref: '#/components/schemas/DashboardQuery'
+          type: array
+        shape:
+          enum:
+            - chronograf-v2
+          type: string
+        showNoteWhenEmpty:
+          description: If true, will display note when empty
+          type: boolean
+        tableOptions:
+          properties:
+            fixFirstColumn:
+              description: >-
+                fixFirstColumn indicates whether the first column of the table
+                should be locked
+              type: boolean
+            sortBy:
+              $ref: '#/components/schemas/RenamableField'
+            verticalTimeAxis:
+              description: >-
+                verticalTimeAxis describes the orientation of the table by
+                indicating whether the time axis will be displayed vertically
+              type: boolean
+            wrapping:
+              description: >-
+                Wrapping describes the text wrapping style to be used in table
+                views
+              enum:
+                - truncate
+                - wrap
+                - single-line
+              type: string
+          type: object
+        timeFormat:
+          description: >-
+            timeFormat describes the display format for time values according to
+            moment.js date formatting
+          type: string
+        type:
+          enum:
+            - table
+          type: string
+      required:
+        - type
+        - queries
+        - colors
+        - shape
+        - note
+        - showNoteWhenEmpty
+        - tableOptions
+        - fieldOptions
+        - timeFormat
+        - decimalPlaces
+      type: object
+    TagRule:
+      properties:
+        key:
+          type: string
+        operator:
+          enum:
+            - equal
+            - notequal
+            - equalregex
+            - notequalregex
+          type: string
+        value:
+          type: string
+      type: object
+    Task:
+      properties:
+        authorizationID:
+          description: >-
+            ID of the authorization used when the task communicates with the
+            query engine.
+          type: string
+        createdAt:
+          format: date-time
+          readOnly: true
+          type: string
+        cron:
+          description: >-
+            [Cron expression](https://en.wikipedia.org/wiki/Cron#Overview) that
+            defines the schedule on which the task runs. Cron scheduling is
+            based on system time.
+
+            Value is a [Cron
+            expression](https://en.wikipedia.org/wiki/Cron#Overview).
+          type: string
+        description:
+          description: Description of the task.
+          type: string
+        every:
+          description: >-
+            Interval at which the task runs. `every` also determines when the
+            task first runs, depending on the specified time.
+
+            Value is a [duration
+            literal](https://docs.influxdata.com/flux/v0.x/spec/lexical-elements/#duration-literals)).
+          format: duration
+          type: string
+        flux:
+          description: Flux script to run for this task.
+          type: string
+        id:
+          readOnly: true
+          type: string
+        labels:
+          $ref: '#/components/schemas/Labels'
+        lastRunError:
+          readOnly: true
+          type: string
+        lastRunStatus:
+          enum:
+            - failed
+            - success
+            - canceled
+          readOnly: true
+          type: string
+        latestCompleted:
+          description: >-
+            Timestamp of the latest scheduled and completed run.
+
+            Value is a timestamp in [RFC3339 date/time
+            format](https://docs.influxdata.com/flux/v0.x/data-types/basic/time/#time-syntax).
+          format: date-time
+          readOnly: true
+          type: string
+        links:
+          example:
+            labels: /api/v2/tasks/1/labels
+            logs: /api/v2/tasks/1/logs
+            members: /api/v2/tasks/1/members
+            owners: /api/v2/tasks/1/owners
+            runs: /api/v2/tasks/1/runs
+            self: /api/v2/tasks/1
+          properties:
+            labels:
+              $ref: '#/components/schemas/Link'
+            logs:
+              $ref: '#/components/schemas/Link'
+            members:
+              $ref: '#/components/schemas/Link'
+            owners:
+              $ref: '#/components/schemas/Link'
+            runs:
+              $ref: '#/components/schemas/Link'
+            self:
+              $ref: '#/components/schemas/Link'
+          readOnly: true
+          type: object
+        name:
+          description: Name of the task.
+          type: string
+        offset:
+          description: >-
+            [Duration](https://docs.influxdata.com/flux/v0.x/spec/lexical-elements/#duration-literals)
+            to delay execution of the task after the scheduled time has elapsed.
+            `0` removes the offset.
+
+            The value is a [duration
+            literal](https://docs.influxdata.com/flux/v0.x/spec/lexical-elements/#duration-literals).
+          format: duration
+          type: string
+        org:
+          description: Name of the organization that owns the task.
+          type: string
+        orgID:
+          description: ID of the organization that owns the task.
+          type: string
+        ownerID:
+          description: ID of the user who owns this Task.
+          type: string
+        status:
+          $ref: '#/components/schemas/TaskStatusType'
+        type:
+          description: Type of the task, useful for filtering a task list.
+          type: string
+        updatedAt:
+          format: date-time
+          readOnly: true
+          type: string
+      required:
+        - id
+        - name
+        - orgID
+        - flux
+      type: object
+    TaskCreateRequest:
+      properties:
+        description:
+          description: An optional description of the task.
+          type: string
+        flux:
+          description: The Flux script to run for this task.
+          type: string
+        org:
+          description: The name of the organization that owns this Task.
+          type: string
+        orgID:
+          description: The ID of the organization that owns this Task.
+          type: string
+        status:
+          $ref: '#/components/schemas/TaskStatusType'
+      required:
+        - flux
+      type: object
+    TaskStatusType:
+      enum:
+        - active
+        - inactive
+      type: string
+    TaskUpdateRequest:
+      properties:
+        cron:
+          description: Override the 'cron' option in the flux script.
+          type: string
+        description:
+          description: An optional description of the task.
+          type: string
+        every:
+          description: Override the 'every' option in the flux script.
+          type: string
+        flux:
+          description: The Flux script to run for this task.
+          type: string
+        name:
+          description: Override the 'name' option in the flux script.
+          type: string
+        offset:
+          description: Override the 'offset' option in the flux script.
+          type: string
+        status:
+          $ref: '#/components/schemas/TaskStatusType'
+      type: object
+    Tasks:
+      properties:
+        links:
+          $ref: '#/components/schemas/Links'
+          readOnly: true
+        tasks:
+          items:
+            $ref: '#/components/schemas/Task'
+          type: array
+      type: object
+    Telegraf:
+      allOf:
+        - $ref: '#/components/schemas/TelegrafRequest'
+        - properties:
+            id:
+              readOnly: true
+              type: string
+            labels:
+              $ref: '#/components/schemas/Labels'
+              readOnly: true
+            links:
+              example:
+                lables: /api/v2/telegrafs/1/labels
+                members: /api/v2/telegrafs/1/members
+                owners: /api/v2/telegrafs/1/owners
+                self: /api/v2/telegrafs/1
+              properties:
+                labels:
+                  $ref: '#/components/schemas/Link'
+                members:
+                  $ref: '#/components/schemas/Link'
+                owners:
+                  $ref: '#/components/schemas/Link'
+                self:
+                  $ref: '#/components/schemas/Link'
+              readOnly: true
+              type: object
+          type: object
+      type: object
+    TelegrafPlugin:
+      properties:
+        config:
+          type: string
+        description:
+          type: string
+        name:
+          type: string
+        type:
+          type: string
+      type: object
+    TelegrafPluginRequest:
+      properties:
+        config:
+          type: string
+        description:
+          type: string
+        metadata:
+          properties:
+            buckets:
+              items:
+                type: string
+              type: array
+          type: object
+        name:
+          type: string
+        orgID:
+          type: string
+        plugins:
+          items:
+            properties:
+              alias:
+                type: string
+              config:
+                type: string
+              description:
+                type: string
+              name:
+                type: string
+              type:
+                type: string
+            type: object
+          type: array
+      type: object
+    TelegrafPlugins:
+      properties:
+        os:
+          type: string
+        plugins:
+          items:
+            $ref: '#/components/schemas/TelegrafPlugin'
+          type: array
+        version:
+          type: string
+      type: object
+    TelegrafRequest:
+      properties:
+        config:
+          type: string
+        description:
+          type: string
+        metadata:
+          properties:
+            buckets:
+              items:
+                type: string
+              type: array
+          type: object
+        name:
+          type: string
+        orgID:
+          type: string
+      type: object
+    Telegrafs:
+      properties:
+        configurations:
+          items:
+            $ref: '#/components/schemas/Telegraf'
+          type: array
+      type: object
+    TelegramNotificationEndpoint:
+      allOf:
+        - $ref: '#/components/schemas/NotificationEndpointBase'
+        - properties:
+            channel:
+              description: >-
+                ID of the telegram channel, a chat_id in
+                https://core.telegram.org/bots/api#sendmessage .
+              type: string
+            token:
+              description: >-
+                Specifies the Telegram bot token. See
+                https://core.telegram.org/bots#creating-a-new-bot .
+              type: string
+          required:
+            - token
+            - channel
+          type: object
+      type: object
+    TelegramNotificationRule:
+      allOf:
+        - $ref: '#/components/schemas/NotificationRuleBase'
+        - $ref: '#/components/schemas/TelegramNotificationRuleBase'
+    TelegramNotificationRuleBase:
+      properties:
+        disableWebPagePreview:
+          description: >-
+            Disables preview of web links in the sent messages when "true".
+            Defaults to "false" .
+          type: boolean
+        messageTemplate:
+          description: The message template as a flux interpolated string.
+          type: string
+        parseMode:
+          description: >-
+            Parse mode of the message text per
+            https://core.telegram.org/bots/api#formatting-options . Defaults to
+            "MarkdownV2" .
+          enum:
+            - MarkdownV2
+            - HTML
+            - Markdown
+          type: string
+        type:
+          description: >-
+            The discriminator between other types of notification rules is
+            "telegram".
+          enum:
+            - telegram
+          type: string
+      required:
+        - type
+        - messageTemplate
+        - channel
+      type: object
+    Template:
+      items:
+        properties:
+          apiVersion:
+            type: string
+          kind:
+            $ref: '#/components/schemas/TemplateKind'
+          meta:
+            properties:
+              name:
+                type: string
+            type: object
+          spec:
+            type: object
+        type: object
+      type: array
+    TemplateApply:
+      properties:
+        actions:
+          items:
+            oneOf:
+              - properties:
+                  action:
+                    enum:
+                      - skipKind
+                    type: string
+                  properties:
+                    properties:
+                      kind:
+                        $ref: '#/components/schemas/TemplateKind'
+                    required:
+                      - kind
+                    type: object
+                type: object
+              - properties:
+                  action:
+                    enum:
+                      - skipResource
+                    type: string
+                  properties:
+                    properties:
+                      kind:
+                        $ref: '#/components/schemas/TemplateKind'
+                      resourceTemplateName:
+                        type: string
+                    required:
+                      - kind
+                      - resourceTemplateName
+                    type: object
+                type: object
+          type: array
+        dryRun:
+          type: boolean
+        envRefs:
+          additionalProperties:
+            oneOf:
+              - type: string
+              - type: integer
+              - type: number
+              - type: boolean
+          type: object
+        orgID:
+          type: string
+        remotes:
+          items:
+            properties:
+              contentType:
+                type: string
+              url:
+                type: string
+            required:
+              - url
+            type: object
+          type: array
+        secrets:
+          additionalProperties:
+            type: string
+          type: object
+        stackID:
+          type: string
+        template:
+          properties:
+            contentType:
+              type: string
+            contents:
+              $ref: '#/components/schemas/Template'
+            sources:
+              items:
+                type: string
+              type: array
+          type: object
+        templates:
+          items:
+            properties:
+              contentType:
+                type: string
+              contents:
+                $ref: '#/components/schemas/Template'
+              sources:
+                items:
+                  type: string
+                type: array
+            type: object
+          type: array
+      type: object
+    TemplateChart:
+      properties:
+        height:
+          type: integer
+        properties:
+          $ref: '#/components/schemas/ViewProperties'
+        width:
+          type: integer
+        xPos:
+          type: integer
+        yPos:
+          type: integer
+      type: object
+    TemplateEnvReferences:
+      items:
+        properties:
+          defaultValue:
+            description: >-
+              Default value that will be provided for the reference when no
+              value is provided
+            nullable: true
+            oneOf:
+              - type: string
+              - type: integer
+              - type: number
+              - type: boolean
+          envRefKey:
+            description: >-
+              Key identified as environment reference and is the key identified
+              in the template
+            type: string
+          resourceField:
+            description: Field the environment reference corresponds too
+            type: string
+          value:
+            description: Value provided to fulfill reference
+            nullable: true
+            oneOf:
+              - type: string
+              - type: integer
+              - type: number
+              - type: boolean
+        required:
+          - resourceField
+          - envRefKey
+        type: object
+      type: array
+    TemplateExportByID:
+      properties:
+        orgIDs:
+          items:
+            properties:
+              orgID:
+                type: string
+              resourceFilters:
+                properties:
+                  byLabel:
+                    items:
+                      type: string
+                    type: array
+                  byResourceKind:
+                    items:
+                      $ref: '#/components/schemas/TemplateKind'
+                    type: array
+                type: object
+            type: object
+          type: array
+        resources:
+          items:
+            properties:
+              id:
+                type: string
+              kind:
+                $ref: '#/components/schemas/TemplateKind'
+              name:
+                description: >-
+                  if defined with id, name is used for resource exported by id.
+                  if defined independently, resources strictly matching name are
+                  exported
+                type: string
+            required:
+              - id
+              - kind
+            type: object
+          type: array
+        stackID:
+          type: string
+      type: object
+    TemplateExportByName:
+      properties:
+        orgIDs:
+          items:
+            properties:
+              orgID:
+                type: string
+              resourceFilters:
+                properties:
+                  byLabel:
+                    items:
+                      type: string
+                    type: array
+                  byResourceKind:
+                    items:
+                      $ref: '#/components/schemas/TemplateKind'
+                    type: array
+                type: object
+            type: object
+          type: array
+        resources:
+          items:
+            properties:
+              kind:
+                $ref: '#/components/schemas/TemplateKind'
+              name:
+                type: string
+            required:
+              - name
+              - kind
+            type: object
+          type: array
+        stackID:
+          type: string
+      type: object
+    TemplateKind:
+      enum:
+        - Bucket
+        - Check
+        - CheckDeadman
+        - CheckThreshold
+        - Dashboard
+        - Label
+        - NotificationEndpoint
+        - NotificationEndpointHTTP
+        - NotificationEndpointPagerDuty
+        - NotificationEndpointSlack
+        - NotificationRule
+        - Task
+        - Telegraf
+        - Variable
+      type: string
+    TemplateSummary:
+      properties:
+        diff:
+          properties:
+            buckets:
+              items:
+                properties:
+                  id:
+                    type: string
+                  kind:
+                    $ref: '#/components/schemas/TemplateKind'
+                  new:
+                    properties:
+                      description:
+                        type: string
+                      name:
+                        type: string
+                      retentionRules:
+                        $ref: '#/components/schemas/RetentionRules'
+                    type: object
+                  old:
+                    properties:
+                      description:
+                        type: string
+                      name:
+                        type: string
+                      retentionRules:
+                        $ref: '#/components/schemas/RetentionRules'
+                    type: object
+                  stateStatus:
+                    type: string
+                  templateMetaName:
+                    type: string
+                type: object
+              type: array
+            checks:
+              items:
+                properties:
+                  id:
+                    type: string
+                  kind:
+                    $ref: '#/components/schemas/TemplateKind'
+                  new:
+                    $ref: '#/components/schemas/CheckDiscriminator'
+                  old:
+                    $ref: '#/components/schemas/CheckDiscriminator'
+                  stateStatus:
+                    type: string
+                  templateMetaName:
+                    type: string
+                type: object
+              type: array
+            dashboards:
+              items:
+                properties:
+                  id:
+                    type: string
+                  kind:
+                    $ref: '#/components/schemas/TemplateKind'
+                  new:
+                    properties:
+                      charts:
+                        items:
+                          $ref: '#/components/schemas/TemplateChart'
+                        type: array
+                      description:
+                        type: string
+                      name:
+                        type: string
+                    type: object
+                  old:
+                    properties:
+                      charts:
+                        items:
+                          $ref: '#/components/schemas/TemplateChart'
+                        type: array
+                      description:
+                        type: string
+                      name:
+                        type: string
+                    type: object
+                  stateStatus:
+                    type: string
+                  templateMetaName:
+                    type: string
+                type: object
+              type: array
+            labelMappings:
+              items:
+                properties:
+                  labelID:
+                    type: string
+                  labelName:
+                    type: string
+                  labelTemplateMetaName:
+                    type: string
+                  resourceID:
+                    type: string
+                  resourceName:
+                    type: string
+                  resourceTemplateMetaName:
+                    type: string
+                  resourceType:
+                    type: string
+                  status:
+                    type: string
+                type: object
+              type: array
+            labels:
+              items:
+                properties:
+                  id:
+                    type: string
+                  kind:
+                    $ref: '#/components/schemas/TemplateKind'
+                  new:
+                    properties:
+                      color:
+                        type: string
+                      description:
+                        type: string
+                      name:
+                        type: string
+                    type: object
+                  old:
+                    properties:
+                      color:
+                        type: string
+                      description:
+                        type: string
+                      name:
+                        type: string
+                    type: object
+                  stateStatus:
+                    type: string
+                  templateMetaName:
+                    type: string
+                type: object
+              type: array
+            notificationEndpoints:
+              items:
+                properties:
+                  id:
+                    type: string
+                  kind:
+                    $ref: '#/components/schemas/TemplateKind'
+                  new:
+                    $ref: '#/components/schemas/NotificationEndpointDiscriminator'
+                  old:
+                    $ref: '#/components/schemas/NotificationEndpointDiscriminator'
+                  stateStatus:
+                    type: string
+                  templateMetaName:
+                    type: string
+                type: object
+              type: array
+            notificationRules:
+              items:
+                properties:
+                  id:
+                    type: string
+                  kind:
+                    $ref: '#/components/schemas/TemplateKind'
+                  new:
+                    properties:
+                      description:
+                        type: string
+                      endpointID:
+                        type: string
+                      endpointName:
+                        type: string
+                      endpointType:
+                        type: string
+                      every:
+                        type: string
+                      messageTemplate:
+                        type: string
+                      name:
+                        type: string
+                      offset:
+                        type: string
+                      status:
+                        type: string
+                      statusRules:
+                        items:
+                          properties:
+                            currentLevel:
+                              type: string
+                            previousLevel:
+                              type: string
+                          type: object
+                        type: array
+                      tagRules:
+                        items:
+                          properties:
+                            key:
+                              type: string
+                            operator:
+                              type: string
+                            value:
+                              type: string
+                          type: object
+                        type: array
+                    type: object
+                  old:
+                    properties:
+                      description:
+                        type: string
+                      endpointID:
+                        type: string
+                      endpointName:
+                        type: string
+                      endpointType:
+                        type: string
+                      every:
+                        type: string
+                      messageTemplate:
+                        type: string
+                      name:
+                        type: string
+                      offset:
+                        type: string
+                      status:
+                        type: string
+                      statusRules:
+                        items:
+                          properties:
+                            currentLevel:
+                              type: string
+                            previousLevel:
+                              type: string
+                          type: object
+                        type: array
+                      tagRules:
+                        items:
+                          properties:
+                            key:
+                              type: string
+                            operator:
+                              type: string
+                            value:
+                              type: string
+                          type: object
+                        type: array
+                    type: object
+                  stateStatus:
+                    type: string
+                  templateMetaName:
+                    type: string
+                type: object
+              type: array
+            tasks:
+              items:
+                properties:
+                  id:
+                    type: string
+                  kind:
+                    $ref: '#/components/schemas/TemplateKind'
+                  new:
+                    properties:
+                      cron:
+                        type: string
+                      description:
+                        type: string
+                      every:
+                        type: string
+                      name:
+                        type: string
+                      offset:
+                        type: string
+                      query:
+                        type: string
+                      status:
+                        type: string
+                    type: object
+                  old:
+                    properties:
+                      cron:
+                        type: string
+                      description:
+                        type: string
+                      every:
+                        type: string
+                      name:
+                        type: string
+                      offset:
+                        type: string
+                      query:
+                        type: string
+                      status:
+                        type: string
+                    type: object
+                  stateStatus:
+                    type: string
+                  templateMetaName:
+                    type: string
+                type: object
+              type: array
+            telegrafConfigs:
+              items:
+                properties:
+                  id:
+                    type: string
+                  kind:
+                    $ref: '#/components/schemas/TemplateKind'
+                  new:
+                    $ref: '#/components/schemas/TelegrafRequest'
+                  old:
+                    $ref: '#/components/schemas/TelegrafRequest'
+                  stateStatus:
+                    type: string
+                  templateMetaName:
+                    type: string
+                type: object
+              type: array
+            variables:
+              items:
+                properties:
+                  id:
+                    type: string
+                  kind:
+                    $ref: '#/components/schemas/TemplateKind'
+                  new:
+                    properties:
+                      args:
+                        $ref: '#/components/schemas/VariableProperties'
+                      description:
+                        type: string
+                      name:
+                        type: string
+                    type: object
+                  old:
+                    properties:
+                      args:
+                        $ref: '#/components/schemas/VariableProperties'
+                      description:
+                        type: string
+                      name:
+                        type: string
+                    type: object
+                  stateStatus:
+                    type: string
+                  templateMetaName:
+                    type: string
+                type: object
+              type: array
+          type: object
+        errors:
+          items:
+            properties:
+              fields:
+                items:
+                  type: string
+                type: array
+              indexes:
+                items:
+                  type: integer
+                type: array
+              kind:
+                $ref: '#/components/schemas/TemplateKind'
+              reason:
+                type: string
+            type: object
+          type: array
+        sources:
+          items:
+            type: string
+          type: array
+        stackID:
+          type: string
+        summary:
+          properties:
+            buckets:
+              items:
+                properties:
+                  description:
+                    type: string
+                  envReferences:
+                    $ref: '#/components/schemas/TemplateEnvReferences'
+                  id:
+                    type: string
+                  kind:
+                    $ref: '#/components/schemas/TemplateKind'
+                  labelAssociations:
+                    items:
+                      $ref: '#/components/schemas/TemplateSummaryLabel'
+                    type: array
+                  name:
+                    type: string
+                  orgID:
+                    type: string
+                  retentionPeriod:
+                    type: integer
+                  templateMetaName:
+                    type: string
+                type: object
+              type: array
+            checks:
+              items:
+                allOf:
+                  - $ref: '#/components/schemas/CheckDiscriminator'
+                  - properties:
+                      envReferences:
+                        $ref: '#/components/schemas/TemplateEnvReferences'
+                      kind:
+                        $ref: '#/components/schemas/TemplateKind'
+                      labelAssociations:
+                        items:
+                          $ref: '#/components/schemas/TemplateSummaryLabel'
+                        type: array
+                      templateMetaName:
+                        type: string
+                    type: object
+              type: array
+            dashboards:
+              items:
+                properties:
+                  charts:
+                    items:
+                      $ref: '#/components/schemas/TemplateChart'
+                    type: array
+                  description:
+                    type: string
+                  envReferences:
+                    $ref: '#/components/schemas/TemplateEnvReferences'
+                  id:
+                    type: string
+                  kind:
+                    $ref: '#/components/schemas/TemplateKind'
+                  labelAssociations:
+                    items:
+                      $ref: '#/components/schemas/TemplateSummaryLabel'
+                    type: array
+                  name:
+                    type: string
+                  orgID:
+                    type: string
+                  templateMetaName:
+                    type: string
+                type: object
+              type: array
+            labelMappings:
+              items:
+                properties:
+                  labelID:
+                    type: string
+                  labelName:
+                    type: string
+                  labelTemplateMetaName:
+                    type: string
+                  resourceID:
+                    type: string
+                  resourceName:
+                    type: string
+                  resourceTemplateMetaName:
+                    type: string
+                  resourceType:
+                    type: string
+                  status:
+                    type: string
+                type: object
+              type: array
+            labels:
+              items:
+                $ref: '#/components/schemas/TemplateSummaryLabel'
+              type: array
+            missingEnvRefs:
+              items:
+                type: string
+              type: array
+            missingSecrets:
+              items:
+                type: string
+              type: array
+            notificationEndpoints:
+              items:
+                allOf:
+                  - $ref: '#/components/schemas/NotificationEndpointDiscriminator'
+                  - properties:
+                      envReferences:
+                        $ref: '#/components/schemas/TemplateEnvReferences'
+                      kind:
+                        $ref: '#/components/schemas/TemplateKind'
+                      labelAssociations:
+                        items:
+                          $ref: '#/components/schemas/TemplateSummaryLabel'
+                        type: array
+                      templateMetaName:
+                        type: string
+                    type: object
+              type: array
+            notificationRules:
+              items:
+                properties:
+                  description:
+                    type: string
+                  endpointID:
+                    type: string
+                  endpointTemplateMetaName:
+                    type: string
+                  endpointType:
+                    type: string
+                  envReferences:
+                    $ref: '#/components/schemas/TemplateEnvReferences'
+                  every:
+                    type: string
+                  kind:
+                    $ref: '#/components/schemas/TemplateKind'
+                  labelAssociations:
+                    items:
+                      $ref: '#/components/schemas/TemplateSummaryLabel'
+                    type: array
+                  messageTemplate:
+                    type: string
+                  name:
+                    type: string
+                  offset:
+                    type: string
+                  status:
+                    type: string
+                  statusRules:
+                    items:
+                      properties:
+                        currentLevel:
+                          type: string
+                        previousLevel:
+                          type: string
+                      type: object
+                    type: array
+                  tagRules:
+                    items:
+                      properties:
+                        key:
+                          type: string
+                        operator:
+                          type: string
+                        value:
+                          type: string
+                      type: object
+                    type: array
+                  templateMetaName:
+                    type: string
+                type: object
+              type: array
+            tasks:
+              items:
+                properties:
+                  cron:
+                    type: string
+                  description:
+                    type: string
+                  envReferences:
+                    $ref: '#/components/schemas/TemplateEnvReferences'
+                  every:
+                    type: string
+                  id:
+                    type: string
+                  kind:
+                    $ref: '#/components/schemas/TemplateKind'
+                  name:
+                    type: string
+                  offset:
+                    type: string
+                  query:
+                    type: string
+                  status:
+                    type: string
+                  templateMetaName:
+                    type: string
+                type: object
+              type: array
+            telegrafConfigs:
+              items:
+                allOf:
+                  - $ref: '#/components/schemas/TelegrafRequest'
+                  - properties:
+                      envReferences:
+                        $ref: '#/components/schemas/TemplateEnvReferences'
+                      kind:
+                        $ref: '#/components/schemas/TemplateKind'
+                      labelAssociations:
+                        items:
+                          $ref: '#/components/schemas/TemplateSummaryLabel'
+                        type: array
+                      templateMetaName:
+                        type: string
+                    type: object
+              type: array
+            variables:
+              items:
+                properties:
+                  arguments:
+                    $ref: '#/components/schemas/VariableProperties'
+                  description:
+                    type: string
+                  envReferences:
+                    $ref: '#/components/schemas/TemplateEnvReferences'
+                  id:
+                    type: string
+                  kind:
+                    $ref: '#/components/schemas/TemplateKind'
+                  labelAssociations:
+                    items:
+                      $ref: '#/components/schemas/TemplateSummaryLabel'
+                    type: array
+                  name:
+                    type: string
+                  orgID:
+                    type: string
+                  templateMetaName:
+                    type: string
+                type: object
+              type: array
+          type: object
+      type: object
+    TemplateSummaryLabel:
+      properties:
+        envReferences:
+          $ref: '#/components/schemas/TemplateEnvReferences'
+        id:
+          type: string
+        kind:
+          $ref: '#/components/schemas/TemplateKind'
+        name:
+          type: string
+        orgID:
+          type: string
+        properties:
+          properties:
+            color:
+              type: string
+            description:
+              type: string
+          type: object
+        templateMetaName:
+          type: string
+      type: object
+    TestStatement:
+      description: Declares a Flux test case
+      properties:
+        assignment:
+          $ref: '#/components/schemas/VariableAssignment'
+        type:
+          $ref: '#/components/schemas/NodeType'
+      type: object
+    Threshold:
+      discriminator:
+        mapping:
+          greater: '#/components/schemas/GreaterThreshold'
+          lesser: '#/components/schemas/LesserThreshold'
+          range: '#/components/schemas/RangeThreshold'
+        propertyName: type
+      oneOf:
+        - $ref: '#/components/schemas/GreaterThreshold'
+        - $ref: '#/components/schemas/LesserThreshold'
+        - $ref: '#/components/schemas/RangeThreshold'
+    ThresholdBase:
+      properties:
+        allValues:
+          description: If true, only alert if all values meet threshold.
+          type: boolean
+        level:
+          $ref: '#/components/schemas/CheckStatusLevel'
+    ThresholdCheck:
+      allOf:
+        - $ref: '#/components/schemas/CheckBase'
+        - properties:
+            every:
+              description: Check repetition interval.
+              type: string
+            offset:
+              description: Duration to delay after the schedule, before executing check.
+              type: string
+            statusMessageTemplate:
+              description: The template used to generate and write a status message.
+              type: string
+            tags:
+              description: List of tags to write to each status.
+              items:
+                properties:
+                  key:
+                    type: string
+                  value:
+                    type: string
+                type: object
+              type: array
+            thresholds:
+              items:
+                $ref: '#/components/schemas/Threshold'
+              type: array
+            type:
+              enum:
+                - threshold
+              type: string
+          required:
+            - type
+          type: object
+    Token:
+      properties:
+        token:
+          type: string
+      type: object
+    UnaryExpression:
+      description: Uses operators to act on a single operand in an expression
+      properties:
+        argument:
+          $ref: '#/components/schemas/Expression'
+        operator:
+          type: string
+        type:
+          $ref: '#/components/schemas/NodeType'
+      type: object
+    UnsignedIntegerLiteral:
+      description: Represents integer numbers
+      properties:
+        type:
+          $ref: '#/components/schemas/NodeType'
+        value:
+          type: string
+      type: object
+    User:
+      properties:
+        id:
+          readOnly: true
+          type: string
+        name:
+          type: string
+        oauthID:
+          type: string
+        status:
+          default: active
+          description: If inactive the user is inactive.
+          enum:
+            - active
+            - inactive
+          type: string
+      required:
+        - name
+    UserResponse:
+      properties:
+        id:
+          readOnly: true
+          type: string
+        links:
+          example:
+            self: /api/v2/users/1
+          properties:
+            self:
+              format: uri
+              type: string
+          readOnly: true
+          type: object
+        name:
+          type: string
+        oauthID:
+          type: string
+        status:
+          default: active
+          description: If inactive the user is inactive.
+          enum:
+            - active
+            - inactive
+          type: string
+      required:
+        - name
+    Users:
+      properties:
+        links:
+          properties:
+            self:
+              format: uri
+              type: string
+          type: object
+        users:
+          items:
+            $ref: '#/components/schemas/UserResponse'
+          type: array
+      type: object
+    Variable:
+      properties:
+        arguments:
+          $ref: '#/components/schemas/VariableProperties'
+        createdAt:
+          format: date-time
+          type: string
+        description:
+          type: string
+        id:
+          readOnly: true
+          type: string
+        labels:
+          $ref: '#/components/schemas/Labels'
+        links:
+          properties:
+            labels:
+              format: uri
+              type: string
+            org:
+              format: uri
+              type: string
+            self:
+              format: uri
+              type: string
+          readOnly: true
+          type: object
+        name:
+          type: string
+        orgID:
+          type: string
+        selected:
+          items:
+            type: string
+          type: array
+        updatedAt:
+          format: date-time
+          type: string
+      required:
+        - name
+        - orgID
+        - arguments
+      type: object
+    VariableAssignment:
+      description: Represents the declaration of a variable
+      properties:
+        id:
+          $ref: '#/components/schemas/Identifier'
+        init:
+          $ref: '#/components/schemas/Expression'
+        type:
+          $ref: '#/components/schemas/NodeType'
+      type: object
+    VariableProperties:
+      oneOf:
+        - $ref: '#/components/schemas/QueryVariableProperties'
+        - $ref: '#/components/schemas/ConstantVariableProperties'
+        - $ref: '#/components/schemas/MapVariableProperties'
+      type: object
+    Variables:
+      example:
+        variables:
+          - arguments:
+              type: constant
+              values:
+                - howdy
+                - hello
+                - hi
+                - yo
+                - oy
+            id: '1221432'
+            name: ':ok:'
+            selected:
+              - hello
+          - arguments:
+              type: map
+              values:
+                a: fdjaklfdjkldsfjlkjdsa
+                b: dfaksjfkljekfajekdljfas
+                c: fdjksajfdkfeawfeea
+            id: '1221432'
+            name: ':ok:'
+            selected:
+              - c
+          - arguments:
+              language: flux
+              query: 'from(bucket: "foo") |> showMeasurements()'
+              type: query
+            id: '1221432'
+            name: ':ok:'
+            selected:
+              - host
+      properties:
+        variables:
+          items:
+            $ref: '#/components/schemas/Variable'
+          type: array
+      type: object
+    View:
+      properties:
+        id:
+          readOnly: true
+          type: string
+        links:
+          properties:
+            self:
+              type: string
+          readOnly: true
+          type: object
+        name:
+          type: string
+        properties:
+          $ref: '#/components/schemas/ViewProperties'
+      required:
+        - name
+        - properties
+    ViewProperties:
+      oneOf:
+        - $ref: '#/components/schemas/LinePlusSingleStatProperties'
+        - $ref: '#/components/schemas/XYViewProperties'
+        - $ref: '#/components/schemas/SingleStatViewProperties'
+        - $ref: '#/components/schemas/HistogramViewProperties'
+        - $ref: '#/components/schemas/GaugeViewProperties'
+        - $ref: '#/components/schemas/TableViewProperties'
+        - $ref: '#/components/schemas/SimpleTableViewProperties'
+        - $ref: '#/components/schemas/MarkdownViewProperties'
+        - $ref: '#/components/schemas/CheckViewProperties'
+        - $ref: '#/components/schemas/ScatterViewProperties'
+        - $ref: '#/components/schemas/HeatmapViewProperties'
+        - $ref: '#/components/schemas/MosaicViewProperties'
+        - $ref: '#/components/schemas/BandViewProperties'
+        - $ref: '#/components/schemas/GeoViewProperties'
+    Views:
+      properties:
+        links:
+          properties:
+            self:
+              type: string
+          type: object
+        views:
+          items:
+            $ref: '#/components/schemas/View'
+          type: array
+      type: object
+    WritePrecision:
+      enum:
+        - ms
+        - s
+        - us
+        - ns
+      type: string
+    XYGeom:
+      enum:
+        - line
+        - step
+        - stacked
+        - bar
+        - monotoneX
+      type: string
+    XYViewProperties:
+      properties:
+        axes:
+          $ref: '#/components/schemas/Axes'
+        colorMapping:
+          $ref: '#/components/schemas/ColorMapping'
+          description: An object that contains information about the color mapping
+        colors:
+          description: Colors define color encoding of data into a visualization
+          items:
+            $ref: '#/components/schemas/DashboardColor'
+          type: array
+        generateXAxisTicks:
+          items:
+            type: string
+          type: array
+        generateYAxisTicks:
+          items:
+            type: string
+          type: array
+        geom:
+          $ref: '#/components/schemas/XYGeom'
+        hoverDimension:
+          enum:
+            - auto
+            - x
+            - 'y'
+            - xy
+          type: string
+        legendColorizeRows:
+          type: boolean
+        legendHide:
+          type: boolean
+        legendOpacity:
+          format: float
+          type: number
+        legendOrientationThreshold:
+          type: integer
+        note:
+          type: string
+        position:
+          enum:
+            - overlaid
+            - stacked
+          type: string
+        queries:
+          items:
+            $ref: '#/components/schemas/DashboardQuery'
+          type: array
+        shadeBelow:
+          type: boolean
+        shape:
+          enum:
+            - chronograf-v2
+          type: string
+        showNoteWhenEmpty:
+          description: If true, will display note when empty
+          type: boolean
+        staticLegend:
+          $ref: '#/components/schemas/StaticLegend'
+        timeFormat:
+          type: string
+        type:
+          enum:
+            - xy
+          type: string
+        xColumn:
+          type: string
+        xTickStart:
+          format: float
+          type: number
+        xTickStep:
+          format: float
+          type: number
+        xTotalTicks:
+          type: integer
+        yColumn:
+          type: string
+        yTickStart:
+          format: float
+          type: number
+        yTickStep:
+          format: float
+          type: number
+        yTotalTicks:
+          type: integer
+      required:
+        - type
+        - geom
+        - queries
+        - shape
+        - axes
+        - colors
+        - note
+        - showNoteWhenEmpty
+        - position
+      type: object
+  securitySchemes:
+    BasicAuthentication:
+      description: >
+        Use the HTTP Basic authentication scheme for InfluxDB `/api/v2` API
+        operations that support it.
+
+
+        Username and password schemes require the following credentials:
+          - **username**
+          - **password**
+      scheme: basic
+      type: http
+    TokenAuthentication:
+      description: >
+        Use the [Token
+        authentication](#section/Authentication/TokenAuthentication)
+
+        scheme to authenticate to the InfluxDB API.
+
+
+
+        In your API requests, send an `Authorization` header.
+
+        For the header value, provide the word `Token` followed by a space and
+        an InfluxDB API token.
+
+        The word `Token` is case-sensitive.
+
+
+
+        ### Syntax
+
+
+        `Authorization: Token YOUR_INFLUX_TOKEN`
+
+
+
+        For more information and examples, see the following:
+          - [`/authorizations`](#tag/Authorizations) endpoint.
+          - [Authorize API requests](/influxdb/v2.2/api-guide/api_intro/#authentication).
+          - [Manage API tokens](/influxdb/v2.2/security/tokens/).
+      in: header
+      name: Authorization
+      type: apiKey
+info:
+  title: InfluxDB OSS API Service
+  version: 2.0.0
+  description: >
+    The InfluxDB v2 API provides a programmatic interface for all interactions
+    with InfluxDB. Access the InfluxDB API using the `/api/v2/` endpoint.
+openapi: 3.0.0
+paths:
+  /api/v2:
+    get:
+      operationId: GetRoutes
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+      responses:
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Routes'
+          description: All routes
+      summary: List all top level routes
+      tags:
+        - Routes
+  /api/v2/authorizations:
+    get:
+      operationId: GetAuthorizations
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: Only show authorizations that belong to a user ID.
+          in: query
+          name: userID
+          schema:
+            type: string
+        - description: Only show authorizations that belong to a user name.
+          in: query
+          name: user
+          schema:
+            type: string
+        - description: Only show authorizations that belong to an organization ID.
+          in: query
+          name: orgID
+          schema:
+            type: string
+        - description: Only show authorizations that belong to a organization name.
+          in: query
+          name: org
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Authorizations'
+          description: A list of authorizations
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      summary: List all authorizations
+      tags:
+        - Authorizations
+    post:
+      operationId: PostAuthorizations
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/AuthorizationPostRequest'
+        description: Authorization to create
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Authorization'
+          description: Authorization created
+        '400':
+          $ref: '#/components/responses/ServerError'
+          description: Invalid request
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      summary: Create an authorization
+      tags:
+        - Authorizations
+  /api/v2/authorizations/{authID}:
+    delete:
+      operationId: DeleteAuthorizationsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the authorization to delete.
+          in: path
+          name: authID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Authorization deleted
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      summary: Delete an authorization
+      tags:
+        - Authorizations
+    get:
+      operationId: GetAuthorizationsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the authorization to get.
+          in: path
+          name: authID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Authorization'
+          description: Authorization details
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      summary: Retrieve an authorization
+      tags:
+        - Authorizations
+    patch:
+      operationId: PatchAuthorizationsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the authorization to update.
+          in: path
+          name: authID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/AuthorizationUpdateRequest'
+        description: Authorization to update
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Authorization'
+          description: The active or inactive authorization
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      summary: Update an authorization to be active or inactive
+      tags:
+        - Authorizations
+  /api/v2/backup/kv:
+    get:
+      deprecated: true
+      operationId: GetBackupKV
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+      responses:
+        '200':
+          content:
+            application/octet-stream:
+              schema:
+                format: binary
+                type: string
+          description: Snapshot of KV metadata
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      summary: >-
+        Download snapshot of metadata stored in the server's embedded KV store.
+        Should not be used in versions greater than 2.1.x, as it doesn't include
+        metadata stored in embedded SQL.
+      tags:
+        - Backup
+  /api/v2/backup/metadata:
+    get:
+      operationId: GetBackupMetadata
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: >-
+            Indicates the content encoding (usually a compression algorithm)
+            that the client can understand.
+          in: header
+          name: Accept-Encoding
+          schema:
+            default: identity
+            description: >-
+              The content coding.  Use `gzip` for compressed data or `identity`
+              for unmodified, uncompressed data.
+            enum:
+              - gzip
+              - identity
+            type: string
+      responses:
+        '200':
+          content:
+            multipart/mixed:
+              schema:
+                $ref: '#/components/schemas/MetadataBackup'
+          description: Snapshot of metadata
+          headers:
+            Content-Encoding:
+              description: >-
+                Lists any encodings (usually compression algorithms) that have
+                been applied to the response payload.
+              schema:
+                default: identity
+                description: >
+                  The content coding: `gzip` for compressed data or `identity`
+                  for unmodified, uncompressed data.
+                enum:
+                  - gzip
+                  - identity
+                type: string
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      summary: Download snapshot of all metadata in the server
+      tags:
+        - Backup
+  /api/v2/backup/shards/{shardID}:
+    get:
+      operationId: GetBackupShardId
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: >-
+            Indicates the content encoding (usually a compression algorithm)
+            that the client can understand.
+          in: header
+          name: Accept-Encoding
+          schema:
+            default: identity
+            description: >-
+              The content coding.  Use `gzip` for compressed data or `identity`
+              for unmodified, uncompressed data.
+            enum:
+              - gzip
+              - identity
+            type: string
+        - description: The shard ID.
+          in: path
+          name: shardID
+          required: true
+          schema:
+            format: int64
+            type: integer
+        - description: Earliest time to include in the snapshot. RFC3339 format.
+          in: query
+          name: since
+          schema:
+            format: date-time
+            type: string
+      responses:
+        '200':
+          content:
+            application/octet-stream:
+              schema:
+                format: binary
+                type: string
+          description: TSM snapshot.
+          headers:
+            Content-Encoding:
+              description: >-
+                Lists any encodings (usually compression algorithms) that have
+                been applied to the response payload.
+              schema:
+                default: identity
+                description: >
+                  The content coding: `gzip` for compressed data or `identity`
+                  for unmodified, uncompressed data.
+                enum:
+                  - gzip
+                  - identity
+                type: string
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Shard not found.
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      summary: Download snapshot of all TSM data in a shard
+      tags:
+        - Backup
+  /api/v2/buckets:
+    get:
+      operationId: GetBuckets
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - $ref: '#/components/parameters/Offset'
+        - $ref: '#/components/parameters/Limit'
+        - $ref: '#/components/parameters/After'
+        - description: The name of the organization.
+          in: query
+          name: org
+          schema:
+            type: string
+        - description: The organization ID.
+          in: query
+          name: orgID
+          schema:
+            type: string
+        - description: Only returns buckets with a specific name.
+          in: query
+          name: name
+          schema:
+            type: string
+        - description: Only returns buckets with a specific ID.
+          in: query
+          name: id
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Buckets'
+          description: A list of buckets
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List all buckets
+      tags:
+        - Buckets
+    post:
+      operationId: PostBuckets
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/PostBucketRequest'
+        description: Bucket to create
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Bucket'
+          description: Bucket created
+        '422':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Request body failed validation
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Create a bucket
+      tags:
+        - Buckets
+  /api/v2/buckets/{bucketID}:
+    delete:
+      operationId: DeleteBucketsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the bucket to delete.
+          in: path
+          name: bucketID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Delete has been accepted
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Bucket not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Delete a bucket
+      tags:
+        - Buckets
+    get:
+      operationId: GetBucketsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The bucket ID.
+          in: path
+          name: bucketID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Bucket'
+          description: Bucket details
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Retrieve a bucket
+      tags:
+        - Buckets
+    patch:
+      operationId: PatchBucketsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The bucket ID.
+          in: path
+          name: bucketID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/PatchBucketRequest'
+        description: Bucket update to apply
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Bucket'
+          description: An updated bucket
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Update a bucket
+      tags:
+        - Buckets
+  /api/v2/buckets/{bucketID}/labels:
+    get:
+      operationId: GetBucketsIDLabels
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The bucket ID.
+          in: path
+          name: bucketID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/LabelsResponse'
+          description: A list of all labels for a bucket
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List all labels for a bucket
+      tags:
+        - Buckets
+    post:
+      operationId: PostBucketsIDLabels
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The bucket ID.
+          in: path
+          name: bucketID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/LabelMapping'
+        description: Label to add
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/LabelResponse'
+          description: The newly added label
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Add a label to a bucket
+      tags:
+        - Buckets
+  /api/v2/buckets/{bucketID}/labels/{labelID}:
+    delete:
+      operationId: DeleteBucketsIDLabelsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The bucket ID.
+          in: path
+          name: bucketID
+          required: true
+          schema:
+            type: string
+        - description: The ID of the label to delete.
+          in: path
+          name: labelID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Delete has been accepted
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Bucket not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Delete a label from a bucket
+      tags:
+        - Buckets
+  /api/v2/buckets/{bucketID}/members:
+    get:
+      operationId: GetBucketsIDMembers
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The bucket ID.
+          in: path
+          name: bucketID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ResourceMembers'
+          description: A list of bucket members
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List all users with member privileges for a bucket
+      tags:
+        - Buckets
+    post:
+      operationId: PostBucketsIDMembers
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The bucket ID.
+          in: path
+          name: bucketID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/AddResourceMemberRequestBody'
+        description: User to add as member
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ResourceMember'
+          description: Member added to bucket
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Add a member to a bucket
+      tags:
+        - Buckets
+  /api/v2/buckets/{bucketID}/members/{userID}:
+    delete:
+      operationId: DeleteBucketsIDMembersID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the member to remove.
+          in: path
+          name: userID
+          required: true
+          schema:
+            type: string
+        - description: The bucket ID.
+          in: path
+          name: bucketID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Member removed
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Remove a member from a bucket
+      tags:
+        - Buckets
+  /api/v2/buckets/{bucketID}/owners:
+    get:
+      operationId: GetBucketsIDOwners
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The bucket ID.
+          in: path
+          name: bucketID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ResourceOwners'
+          description: A list of bucket owners
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List all owners of a bucket
+      tags:
+        - Buckets
+    post:
+      operationId: PostBucketsIDOwners
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The bucket ID.
+          in: path
+          name: bucketID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/AddResourceMemberRequestBody'
+        description: User to add as owner
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ResourceOwner'
+          description: Bucket owner added
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Add an owner to a bucket
+      tags:
+        - Buckets
+  /api/v2/buckets/{bucketID}/owners/{userID}:
+    delete:
+      operationId: DeleteBucketsIDOwnersID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the owner to remove.
+          in: path
+          name: userID
+          required: true
+          schema:
+            type: string
+        - description: The bucket ID.
+          in: path
+          name: bucketID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Owner removed
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Remove an owner from a bucket
+      tags:
+        - Buckets
+  /api/v2/checks:
+    get:
+      operationId: GetChecks
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - $ref: '#/components/parameters/Offset'
+        - $ref: '#/components/parameters/Limit'
+        - description: Only show checks that belong to a specific organization ID.
+          in: query
+          name: orgID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Checks'
+          description: A list of checks
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List all checks
+      tags:
+        - Checks
+    post:
+      operationId: CreateCheck
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/PostCheck'
+        description: Check to create
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Check'
+          description: Check created
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Add new check
+      tags:
+        - Checks
+  /api/v2/checks/{checkID}:
+    delete:
+      operationId: DeleteChecksID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The check ID.
+          in: path
+          name: checkID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Delete has been accepted
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: The check was not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Delete a check
+      tags:
+        - Checks
+    get:
+      operationId: GetChecksID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The check ID.
+          in: path
+          name: checkID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Check'
+          description: The check requested
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Retrieve a check
+      tags:
+        - Checks
+    patch:
+      operationId: PatchChecksID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The check ID.
+          in: path
+          name: checkID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/CheckPatch'
+        description: Check update to apply
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Check'
+          description: An updated check
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: The check was not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Update a check
+      tags:
+        - Checks
+    put:
+      operationId: PutChecksID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The check ID.
+          in: path
+          name: checkID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/Check'
+        description: Check update to apply
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Check'
+          description: An updated check
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: The check was not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Update a check
+      tags:
+        - Checks
+  /api/v2/checks/{checkID}/labels:
+    get:
+      operationId: GetChecksIDLabels
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The check ID.
+          in: path
+          name: checkID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/LabelsResponse'
+          description: A list of all labels for a check
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List all labels for a check
+      tags:
+        - Checks
+    post:
+      operationId: PostChecksIDLabels
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The check ID.
+          in: path
+          name: checkID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/LabelMapping'
+        description: Label to add
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/LabelResponse'
+          description: The label was added to the check
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Add a label to a check
+      tags:
+        - Checks
+  /api/v2/checks/{checkID}/labels/{labelID}:
+    delete:
+      operationId: DeleteChecksIDLabelsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The check ID.
+          in: path
+          name: checkID
+          required: true
+          schema:
+            type: string
+        - description: The ID of the label to delete.
+          in: path
+          name: labelID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Delete has been accepted
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Check or label not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Delete label from a check
+      tags:
+        - Checks
+  /api/v2/checks/{checkID}/query:
+    get:
+      operationId: GetChecksIDQuery
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The check ID.
+          in: path
+          name: checkID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/FluxResponse'
+          description: The check query requested
+        '400':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Invalid request
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Check not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Retrieve a check query
+      tags:
+        - Checks
+  /api/v2/config:
+    get:
+      description: >
+        Returns the active runtime configuration of the InfluxDB instance.
+
+
+        In InfluxDB v2.2+, use this endpoint to view your active runtime
+        configuration,
+
+        including flags and environment variables.
+
+
+        #### Related guides
+
+
+        - [View your runtime server
+        configuration](https://docs.influxdata.com/influxdb/v2.2/reference/config-options/#view-your-runtime-server-configuration)
+      operationId: GetConfig
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Config'
+          description: >
+            Success.
+
+            The response body contains the active runtime configuration of the
+            InfluxDB instance.
+        '401':
+          $ref: '#/components/responses/ServerError'
+        default:
+          $ref: '#/components/responses/ServerError'
+      summary: Retrieve runtime configuration
+      tags:
+        - Config
+  /api/v2/dashboards:
+    get:
+      operationId: GetDashboards
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - $ref: '#/components/parameters/Offset'
+        - $ref: '#/components/parameters/Limit'
+        - $ref: '#/components/parameters/Descending'
+        - description: >-
+            A user identifier. Returns only dashboards where this user has the
+            `owner` role.
+          in: query
+          name: owner
+          schema:
+            type: string
+        - description: The column to sort by.
+          in: query
+          name: sortBy
+          schema:
+            enum:
+              - ID
+              - CreatedAt
+              - UpdatedAt
+            type: string
+        - description: >-
+            A list of dashboard identifiers. Returns only the listed dashboards.
+            If both `id` and `owner` are specified, only `id` is used.
+          in: query
+          name: id
+          schema:
+            items:
+              type: string
+            type: array
+        - description: The identifier of the organization.
+          in: query
+          name: orgID
+          schema:
+            type: string
+        - description: The name of the organization.
+          in: query
+          name: org
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Dashboards'
+          description: All dashboards
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List all dashboards
+      tags:
+        - Dashboards
+    post:
+      operationId: PostDashboards
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/CreateDashboardRequest'
+        description: Dashboard to create
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                oneOf:
+                  - $ref: '#/components/schemas/Dashboard'
+                  - $ref: '#/components/schemas/DashboardWithViewProperties'
+          description: Added dashboard
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Create a dashboard
+      tags:
+        - Dashboards
+  /api/v2/dashboards/{dashboardID}:
+    delete:
+      operationId: DeleteDashboardsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the dashboard to update.
+          in: path
+          name: dashboardID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Delete has been accepted
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Dashboard not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Delete a dashboard
+      tags:
+        - Dashboards
+    get:
+      operationId: GetDashboardsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the dashboard to update.
+          in: path
+          name: dashboardID
+          required: true
+          schema:
+            type: string
+        - description: If `properties`, includes the cell view properties in the response.
+          in: query
+          name: include
+          required: false
+          schema:
+            enum:
+              - properties
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                oneOf:
+                  - $ref: '#/components/schemas/Dashboard'
+                  - $ref: '#/components/schemas/DashboardWithViewProperties'
+          description: Retrieve a single dashboard
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Dashboard not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Retrieve a dashboard
+      tags:
+        - Dashboards
+    patch:
+      operationId: PatchDashboardsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the dashboard to update.
+          in: path
+          name: dashboardID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              properties:
+                cells:
+                  $ref: '#/components/schemas/CellWithViewProperties'
+                  description: >-
+                    optional, when provided will replace all existing cells with
+                    the cells provided
+                description:
+                  description: optional, when provided will replace the description
+                  type: string
+                name:
+                  description: optional, when provided will replace the name
+                  type: string
+              title: PatchDashboardRequest
+              type: object
+        description: Patching of a dashboard
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Dashboard'
+          description: Updated dashboard
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Dashboard not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Update a dashboard
+      tags:
+        - Dashboards
+  /api/v2/dashboards/{dashboardID}/cells:
+    post:
+      operationId: PostDashboardsIDCells
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the dashboard to update.
+          in: path
+          name: dashboardID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/CreateCell'
+        description: Cell that will be added
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Cell'
+          description: Cell successfully added
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Dashboard not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Create a dashboard cell
+      tags:
+        - Cells
+        - Dashboards
+    put:
+      description: >-
+        Replaces all cells in a dashboard. This is used primarily to update the
+        positional information of all cells.
+      operationId: PutDashboardsIDCells
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the dashboard to update.
+          in: path
+          name: dashboardID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/Cells'
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Dashboard'
+          description: Replaced dashboard cells
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Dashboard not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Replace cells in a dashboard
+      tags:
+        - Cells
+        - Dashboards
+  /api/v2/dashboards/{dashboardID}/cells/{cellID}:
+    delete:
+      operationId: DeleteDashboardsIDCellsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the dashboard to delete.
+          in: path
+          name: dashboardID
+          required: true
+          schema:
+            type: string
+        - description: The ID of the cell to delete.
+          in: path
+          name: cellID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Cell successfully deleted
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Cell or dashboard not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Delete a dashboard cell
+      tags:
+        - Cells
+        - Dashboards
+    patch:
+      description: >-
+        Updates the non positional information related to a cell. Updates to a
+        single cell's positional data could cause grid conflicts.
+      operationId: PatchDashboardsIDCellsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the dashboard to update.
+          in: path
+          name: dashboardID
+          required: true
+          schema:
+            type: string
+        - description: The ID of the cell to update.
+          in: path
+          name: cellID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/CellUpdate'
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Cell'
+          description: Updated dashboard cell
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Cell or dashboard not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Update the non-positional information related to a cell
+      tags:
+        - Cells
+        - Dashboards
+  /api/v2/dashboards/{dashboardID}/cells/{cellID}/view:
+    get:
+      operationId: GetDashboardsIDCellsIDView
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The dashboard ID.
+          in: path
+          name: dashboardID
+          required: true
+          schema:
+            type: string
+        - description: The cell ID.
+          in: path
+          name: cellID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/View'
+          description: A dashboard cells view
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Cell or dashboard not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Retrieve the view for a cell
+      tags:
+        - Cells
+        - Dashboards
+        - Views
+    patch:
+      operationId: PatchDashboardsIDCellsIDView
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the dashboard to update.
+          in: path
+          name: dashboardID
+          required: true
+          schema:
+            type: string
+        - description: The ID of the cell to update.
+          in: path
+          name: cellID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/View'
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/View'
+          description: Updated cell view
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Cell or dashboard not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Update the view for a cell
+      tags:
+        - Cells
+        - Dashboards
+        - Views
+  /api/v2/dashboards/{dashboardID}/labels:
+    get:
+      operationId: GetDashboardsIDLabels
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The dashboard ID.
+          in: path
+          name: dashboardID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/LabelsResponse'
+          description: A list of all labels for a dashboard
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List all labels for a dashboard
+      tags:
+        - Dashboards
+    post:
+      operationId: PostDashboardsIDLabels
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The dashboard ID.
+          in: path
+          name: dashboardID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/LabelMapping'
+        description: Label to add
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/LabelResponse'
+          description: The label added to the dashboard
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Add a label to a dashboard
+      tags:
+        - Dashboards
+  /api/v2/dashboards/{dashboardID}/labels/{labelID}:
+    delete:
+      operationId: DeleteDashboardsIDLabelsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The dashboard ID.
+          in: path
+          name: dashboardID
+          required: true
+          schema:
+            type: string
+        - description: The ID of the label to delete.
+          in: path
+          name: labelID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Delete has been accepted
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Dashboard not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Delete a label from a dashboard
+      tags:
+        - Dashboards
+  /api/v2/dashboards/{dashboardID}/members:
+    get:
+      operationId: GetDashboardsIDMembers
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The dashboard ID.
+          in: path
+          name: dashboardID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ResourceMembers'
+          description: A list of users who have member privileges for a dashboard
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List all dashboard members
+      tags:
+        - Dashboards
+    post:
+      operationId: PostDashboardsIDMembers
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The dashboard ID.
+          in: path
+          name: dashboardID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/AddResourceMemberRequestBody'
+        description: User to add as member
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ResourceMember'
+          description: Added to dashboard members
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Add a member to a dashboard
+      tags:
+        - Dashboards
+  /api/v2/dashboards/{dashboardID}/members/{userID}:
+    delete:
+      operationId: DeleteDashboardsIDMembersID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the member to remove.
+          in: path
+          name: userID
+          required: true
+          schema:
+            type: string
+        - description: The dashboard ID.
+          in: path
+          name: dashboardID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Member removed
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Remove a member from a dashboard
+      tags:
+        - Dashboards
+  /api/v2/dashboards/{dashboardID}/owners:
+    get:
+      operationId: GetDashboardsIDOwners
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The dashboard ID.
+          in: path
+          name: dashboardID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ResourceOwners'
+          description: A list of users who have owner privileges for a dashboard
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List all dashboard owners
+      tags:
+        - Dashboards
+    post:
+      operationId: PostDashboardsIDOwners
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The dashboard ID.
+          in: path
+          name: dashboardID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/AddResourceMemberRequestBody'
+        description: User to add as owner
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ResourceOwner'
+          description: Added to dashboard owners
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Add an owner to a dashboard
+      tags:
+        - Dashboards
+  /api/v2/dashboards/{dashboardID}/owners/{userID}:
+    delete:
+      operationId: DeleteDashboardsIDOwnersID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the owner to remove.
+          in: path
+          name: userID
+          required: true
+          schema:
+            type: string
+        - description: The dashboard ID.
+          in: path
+          name: dashboardID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Owner removed
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Remove an owner from a dashboard
+      tags:
+        - Dashboards
+  /api/v2/dbrps:
+    get:
+      operationId: GetDBRPs
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: Specifies the organization ID to filter on
+          in: query
+          name: orgID
+          schema:
+            type: string
+        - description: Specifies the organization name to filter on
+          in: query
+          name: org
+          schema:
+            type: string
+        - description: Specifies the mapping ID to filter on
+          in: query
+          name: id
+          schema:
+            type: string
+        - description: Specifies the bucket ID to filter on
+          in: query
+          name: bucketID
+          schema:
+            type: string
+        - description: Specifies filtering on default
+          in: query
+          name: default
+          schema:
+            type: boolean
+        - description: Specifies the database to filter on
+          in: query
+          name: db
+          schema:
+            type: string
+        - description: Specifies the retention policy to filter on
+          in: query
+          name: rp
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/DBRPs'
+          description: Success. Returns a list of database retention policy mappings.
+        '400':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Bad request. The request has one or more invalid parameters.
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List database retention policy mappings
+      tags:
+        - DBRPs
+    post:
+      operationId: PostDBRP
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/DBRPCreate'
+        description: The database retention policy mapping to add
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/DBRP'
+          description: Created. Returns the created database retention policy mapping.
+        '400':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Bad request. The mapping in the request has one or more invalid IDs.
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Add a database retention policy mapping
+      tags:
+        - DBRPs
+  /api/v2/dbrps/{dbrpID}:
+    delete:
+      operationId: DeleteDBRPID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: Specifies the organization ID of the mapping
+          in: query
+          name: orgID
+          schema:
+            type: string
+        - description: Specifies the organization name of the mapping
+          in: query
+          name: org
+          schema:
+            type: string
+        - description: The database retention policy mapping
+          in: path
+          name: dbrpID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Delete has been accepted
+        '400':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: if any of the IDs passed is invalid
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Delete a database retention policy
+      tags:
+        - DBRPs
+    get:
+      operationId: GetDBRPsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: Specifies the organization ID of the mapping
+          in: query
+          name: orgID
+          schema:
+            type: string
+        - description: Specifies the organization name of the mapping
+          in: query
+          name: org
+          schema:
+            type: string
+        - description: The database retention policy mapping ID
+          in: path
+          name: dbrpID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/DBRPGet'
+          description: The database retention policy requested
+        '400':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: if any of the IDs passed is invalid
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Retrieve a database retention policy mapping
+      tags:
+        - DBRPs
+    patch:
+      operationId: PatchDBRPID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: Specifies the organization ID of the mapping
+          in: query
+          name: orgID
+          schema:
+            type: string
+        - description: Specifies the organization name of the mapping
+          in: query
+          name: org
+          schema:
+            type: string
+        - description: The database retention policy mapping.
+          in: path
+          name: dbrpID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/DBRPUpdate'
+        description: Database retention policy update to apply
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/DBRPGet'
+          description: An updated mapping
+        '400':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: if any of the IDs passed is invalid
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: The mapping was not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Update a database retention policy mapping
+      tags:
+        - DBRPs
+  /debug/pprof/all:
+    get:
+      description: >
+        Collects samples and returns reports for the following [Go runtime
+        profiles](https://pkg.go.dev/runtime/pprof):
+
+
+        - **allocs**: All past memory allocations
+
+        - **block**: Stack traces that led to blocking on synchronization
+        primitives
+
+        - **cpu**: (Optional) Program counters sampled from the executing stack.
+          Include by passing the `cpu` query parameter with a [duration](https://docs.influxdata.com/influxdb/v2.2/reference/glossary/#duration) value.
+          Equivalent to the report from [`GET /debug/pprof/profile?seconds=NUMBER_OF_SECONDS`](#operation/GetDebugPprofProfile).
+        - **goroutine**: All current goroutines
+
+        - **heap**: Memory allocations for live objects
+
+        - **mutex**: Holders of contended mutexes
+
+        - **threadcreate**: Stack traces that led to the creation of new OS
+        threads
+      operationId: GetDebugPprofAllProfiles
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: >
+            Collects and returns CPU profiling data for the specified
+            [duration](https://docs.influxdata.com/influxdb/v2.2/reference/glossary/#duration).
+          in: query
+          name: cpu
+          schema:
+            externalDocs:
+              description: InfluxDB duration
+              url: >-
+                https://docs.influxdata.com/influxdb/v2.1/reference/glossary/#duration
+            format: duration
+            type: string
+      responses:
+        '200':
+          content:
+            application/octet-stream:
+              schema:
+                description: >
+                  GZIP compressed TAR file (`.tar.gz`) that contains
+
+                  [Go runtime profile](https://pkg.go.dev/runtime/pprof)
+                  reports.
+                externalDocs:
+                  description: Golang pprof package
+                  url: https://pkg.go.dev/net/http/pprof
+                format: binary
+                type: string
+          description: |
+            [Go runtime profile](https://pkg.go.dev/runtime/pprof) reports.
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      servers: []
+      summary: Retrieve all runtime profiles
+      tags:
+        - Debug
+      x-codeSamples:
+        - label: 'Shell: Get all profiles'
+          lang: Shell
+          source: >
+            # Download and extract a `tar.gz` of all profiles after 10 seconds
+            of CPU sampling.
+
+
+            curl "http://localhost:8086/debug/pprof/all?cpu=10s" | tar -xz
+
+
+            # x profiles/cpu.pb.gz
+
+            # x profiles/goroutine.pb.gz
+
+            # x profiles/block.pb.gz
+
+            # x profiles/mutex.pb.gz
+
+            # x profiles/heap.pb.gz
+
+            # x profiles/allocs.pb.gz
+
+            # x profiles/threadcreate.pb.gz
+
+
+            # Analyze a profile.
+
+
+            go tool pprof profiles/heap.pb.gz
+        - label: 'Shell: Get all profiles except CPU'
+          lang: Shell
+          source: |
+            # Download and extract a `tar.gz` of all profiles except CPU.
+
+            curl http://localhost:8086/debug/pprof/all | tar -xz
+
+            # x profiles/goroutine.pb.gz
+            # x profiles/block.pb.gz
+            # x profiles/mutex.pb.gz
+            # x profiles/heap.pb.gz
+            # x profiles/allocs.pb.gz
+            # x profiles/threadcreate.pb.gz
+
+            # Analyze a profile.
+
+            go tool pprof profiles/heap.pb.gz
+  /debug/pprof/allocs:
+    get:
+      description: >
+        Returns a [Go runtime profile](https://pkg.go.dev/runtime/pprof) report
+        of
+
+        all past memory allocations.
+
+        **allocs** is the same as the **heap** profile,
+
+        but changes the default [pprof](https://pkg.go.dev/runtime/pprof)
+
+        display to __-alloc_space__,
+
+        the total number of bytes allocated since the program began (including
+        garbage-collected bytes).
+      operationId: GetDebugPprofAllocs
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: >
+            - `0`: (Default) Return the report as a gzip-compressed protocol
+            buffer.
+
+            - `1`: Return a response body with the report formatted as
+            human-readable text.
+              The report contains comments that translate addresses to function names and line numbers for debugging.
+
+            `debug=1` is mutually exclusive with the `seconds` query parameter.
+          in: query
+          name: debug
+          schema:
+            enum:
+              - 0
+              - 1
+            format: int64
+            type: integer
+        - description: |
+            Number of seconds to collect statistics.
+
+            `seconds` is mutually exclusive with `debug=1`.
+          in: query
+          name: seconds
+          schema:
+            format: int64
+            type: string
+      responses:
+        '200':
+          content:
+            application/octet-stream:
+              schema:
+                description: >
+                  [Go runtime profile](https://pkg.go.dev/runtime/pprof) report
+                  in protocol buffer format.
+                externalDocs:
+                  description: Golang pprof package
+                  url: https://pkg.go.dev/net/http/pprof
+                format: binary
+                type: string
+            text/plain:
+              schema:
+                description: |
+                  Response body contains a report formatted in plain text.
+                  The report contains comments that translate addresses to
+                  function names and line numbers for debugging.
+                externalDocs:
+                  description: Golang pprof package
+                  url: https://pkg.go.dev/net/http/pprof
+                format: Go runtime profile
+                type: string
+          description: >
+            [Go runtime profile](https://pkg.go.dev/runtime/pprof) report
+            compatible
+
+            with [pprof](https://github.com/google/pprof) analysis and
+            visualization tools.
+
+            If debug is enabled (`?debug=1`), response body contains a
+            human-readable profile.
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      servers: []
+      summary: Retrieve the memory allocations runtime profile
+      tags:
+        - Debug
+      x-codeSamples:
+        - label: 'Shell: go tool pprof'
+          lang: Shell
+          source: >
+            # Analyze the profile in interactive mode.
+
+
+            go tool pprof http://localhost:8086/debug/pprof/allocs
+
+
+            # `pprof` returns the following prompt:
+
+            #   Entering interactive mode (type "help" for commands, "o" for
+            options)
+
+            #   (pprof)
+
+
+            # At the prompt, get the top N memory allocations.
+
+
+            (pprof) top10
+  /debug/pprof/block:
+    get:
+      description: >
+        Collects samples and returns a [Go runtime
+        profile](https://pkg.go.dev/runtime/pprof)
+
+        report of stack traces that led to blocking on synchronization
+        primitives.
+      operationId: GetDebugPprofBlock
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: >
+            - `0`: (Default) Return the report as a gzip-compressed protocol
+            buffer.
+
+            - `1`: Return a response body with the report formatted as
+            human-readable text.
+              The report contains comments that translate addresses to function names and line numbers for debugging.
+
+            `debug=1` is mutually exclusive with the `seconds` query parameter.
+          in: query
+          name: debug
+          schema:
+            enum:
+              - 0
+              - 1
+            format: int64
+            type: integer
+        - description: |
+            Number of seconds to collect statistics.
+
+            `seconds` is mutually exclusive with `debug=1`.
+          in: query
+          name: seconds
+          schema:
+            format: int64
+            type: string
+      responses:
+        '200':
+          content:
+            application/octet-stream:
+              schema:
+                description: >
+                  [Go runtime profile](https://pkg.go.dev/runtime/pprof) report
+                  in protocol buffer format.
+                externalDocs:
+                  description: Golang pprof package
+                  url: https://pkg.go.dev/net/http/pprof
+                format: binary
+                type: string
+            text/plain:
+              schema:
+                description: |
+                  Response body contains a report formatted in plain text.
+                  The report contains comments that translate addresses to
+                  function names and line numbers for debugging.
+                externalDocs:
+                  description: Golang pprof package
+                  url: https://pkg.go.dev/net/http/pprof
+                format: Go runtime profile
+                type: string
+          description: >
+            [Go runtime profile](https://pkg.go.dev/runtime/pprof) report
+            compatible
+
+            with [pprof](https://github.com/google/pprof) analysis and
+            visualization tools.
+
+            If debug is enabled (`?debug=1`), response body contains a
+            human-readable profile.
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      servers: []
+      summary: Retrieve the block runtime profile
+      tags:
+        - Debug
+      x-codeSamples:
+        - label: 'Shell: go tool pprof'
+          lang: Shell
+          source: >
+            # Analyze the profile in interactive mode.
+
+
+            go tool pprof http://localhost:8086/debug/pprof/block
+
+
+            # `pprof` returns the following prompt:
+
+            #   Entering interactive mode (type "help" for commands, "o" for
+            options)
+
+            #   (pprof)
+
+
+            #  At the prompt, get the top N entries.
+
+
+            (pprof) top10
+  /debug/pprof/cmdline:
+    get:
+      description: |
+        Returns the command line that invoked InfluxDB.
+      operationId: GetDebugPprofCmdline
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+      responses:
+        '200':
+          content:
+            text/plain:
+              schema:
+                format: Command line
+                type: string
+          description: Command line invocation.
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      servers: []
+      summary: Retrieve the command line invocation
+      tags:
+        - Debug
+  /debug/pprof/goroutine:
+    get:
+      description: >
+        Collects statistics and returns a [Go runtime
+        profile](https://pkg.go.dev/runtime/pprof)
+
+        report of all current goroutines.
+      operationId: GetDebugPprofGoroutine
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: >
+            - `0`: (Default) Return the report as a gzip-compressed protocol
+            buffer.
+
+            - `1`: Return a response body with the report formatted as
+                   human-readable text with comments that translate addresses to
+                   function names and line numbers for debugging.
+
+            `debug=1` is mutually exclusive with the `seconds` query parameter.
+          in: query
+          name: debug
+          schema:
+            enum:
+              - 0
+              - 1
+            format: int64
+            type: integer
+        - description: |
+            Number of seconds to collect statistics.
+
+            `seconds` is mutually exclusive with `debug=1`.
+          in: query
+          name: seconds
+          schema:
+            format: int64
+            type: string
+      responses:
+        '200':
+          content:
+            application/octet-stream:
+              schema:
+                description: >
+                  [Go runtime profile](https://pkg.go.dev/runtime/pprof) report
+                  in protocol buffer format.
+                externalDocs:
+                  description: Golang pprof package
+                  url: https://pkg.go.dev/net/http/pprof
+                format: binary
+                type: string
+            text/plain:
+              schema:
+                description: |
+                  Response body contains a report formatted in plain text.
+                  The report contains comments that translate addresses to
+                  function names and line numbers for debugging.
+                externalDocs:
+                  description: Golang pprof package
+                  url: https://pkg.go.dev/net/http/pprof
+                format: Go runtime profile
+                type: string
+          description: >
+            [Go runtime profile](https://pkg.go.dev/runtime/pprof) report
+            compatible
+
+            with [pprof](https://github.com/google/pprof) analysis and
+            visualization tools.
+
+            If debug is enabled (`?debug=1`), response body contains a
+            human-readable profile.
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      servers: []
+      summary: Retrieve the goroutines runtime profile
+      tags:
+        - Debug
+      x-codeSamples:
+        - label: 'Shell: go tool pprof'
+          lang: Shell
+          source: >
+            # Analyze the profile in interactive mode.
+
+
+            go tool pprof http://localhost:8086/debug/pprof/goroutine
+
+
+            # `pprof` returns the following prompt:
+
+            #   Entering interactive mode (type "help" for commands, "o" for
+            options)
+
+            #   (pprof)
+
+
+            #  At the prompt, get the top N entries.
+
+
+            (pprof) top10
+  /debug/pprof/heap:
+    get:
+      description: >
+        Collects statistics and returns a [Go runtime
+        profile](https://pkg.go.dev/runtime/pprof)
+
+        report of memory allocations for live objects.
+
+
+        To run **garbage collection** before sampling,
+
+        pass the `gc` query parameter with a value of `1`.
+      operationId: GetDebugPprofHeap
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: >
+            - `0`: (Default) Return the report as a gzip-compressed protocol
+            buffer.
+
+            - `1`: Return a response body with the report formatted as
+            human-readable text.
+              The report contains comments that translate addresses to function names and line numbers for debugging.
+
+            `debug=1` is mutually exclusive with the `seconds` query parameter.
+          in: query
+          name: debug
+          schema:
+            enum:
+              - 0
+              - 1
+            format: int64
+            type: integer
+        - description: |
+            Number of seconds to collect statistics.
+
+            `seconds` is mutually exclusive with `debug=1`.
+          in: query
+          name: seconds
+          schema:
+            format: int64
+            type: string
+        - description: |
+            - `0`: (Default) don't force garbage collection before sampling.
+            - `1`: Force garbage collection before sampling.
+          in: query
+          name: gc
+          schema:
+            enum:
+              - 0
+              - 1
+            format: int64
+            type: integer
+      responses:
+        '200':
+          content:
+            application/octet-stream:
+              schema:
+                description: >
+                  [Go runtime profile](https://pkg.go.dev/runtime/pprof) report
+                  in protocol buffer format.
+                externalDocs:
+                  description: Golang pprof package
+                  url: https://pkg.go.dev/net/http/pprof
+                format: binary
+                type: string
+            text/plain:
+              examples:
+                profileDebugResponse:
+                  summary: Profile in plain text
+                  value: "heap profile: 12431: 137356528 [149885081: 846795139976] @ heap/8192\n23: 17711104 [46: 35422208] @ 0x4c6df65 0x4ce03ec 0x4cdf3c5 0x4c6f4db 0x4c9edbc 0x4bdefb3 0x4bf822a 0x567d158 0x567ced9 0x406c0a1\n#\t0x4c6df64\tgithub.com/influxdata/influxdb/v2/tsdb/engine/tsm1.(*entry).add+0x1a4\t\t\t\t\t/Users/me/github/influxdb/tsdb/engine/tsm1/cache.go:97\n#\t0x4ce03eb\tgithub.com/influxdata/influxdb/v2/tsdb/engine/tsm1.(*partition).write+0x2ab\t\t\t\t/Users/me/github/influxdb/tsdb/engine/tsm1/ring.go:229\n#\t0x4cdf3c4\tgithub.com/influxdata/influxdb/v2/tsdb/engine/tsm1.(*ring).write+0xa4\t\t\t\t\t/Users/me/github/influxdb/tsdb/engine/tsm1/ring.go:95\n#\t0x4c6f4da\tgithub.com/influxdata/influxdb/v2/tsdb/engine/tsm1.(*Cache).WriteMulti+0x31a\t\t\t\t/Users/me/github/influxdb/tsdb/engine/tsm1/cache.go:343\n"
+              schema:
+                description: |
+                  Response body contains a report formatted in plain text.
+                  The report contains comments that translate addresses to
+                  function names and line numbers for debugging.
+                externalDocs:
+                  description: Golang pprof package
+                  url: https://pkg.go.dev/net/http/pprof
+                format: Go runtime profile
+                type: string
+          description: >
+            [Go runtime profile](https://pkg.go.dev/runtime/pprof) report
+            compatible
+
+            with [pprof](https://github.com/google/pprof) analysis and
+            visualization tools.
+
+            If debug is enabled (`?debug=1`), response body contains a
+            human-readable profile.
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      servers: []
+      summary: Retrieve the heap runtime profile
+      tags:
+        - Debug
+      x-codeSamples:
+        - label: 'Shell: go tool pprof'
+          lang: Shell
+          source: >
+            # Analyze the profile in interactive mode.
+
+
+            go tool pprof http://localhost:8086/debug/pprof/heap
+
+
+            # `pprof` returns the following prompt:
+
+            #   Entering interactive mode (type "help" for commands, "o" for
+            options)
+
+            #   (pprof)
+
+
+            # At the prompt, get the top N memory-intensive nodes.
+
+
+            (pprof) top10
+
+
+            # pprof displays the list:
+
+            #   Showing nodes accounting for 142.46MB, 85.43% of 166.75MB total
+
+            #   Dropped 895 nodes (cum <= 0.83MB)
+
+            #   Showing top 10 nodes out of 143
+  /debug/pprof/mutex:
+    get:
+      description: >
+        Collects statistics and returns a [Go runtime
+        profile](https://pkg.go.dev/runtime/pprof) report of
+
+        lock contentions.
+
+        The profile contains stack traces of holders of contended mutual
+        exclusions (mutexes).
+      operationId: GetDebugPprofMutex
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: >
+            - `0`: (Default) Return the report as a gzip-compressed protocol
+            buffer.
+
+            - `1`: Return a response body with the report formatted as
+            human-readable text.
+              The report contains comments that translate addresses to function names and line numbers for debugging.
+
+            `debug=1` is mutually exclusive with the `seconds` query parameter.
+          in: query
+          name: debug
+          schema:
+            enum:
+              - 0
+              - 1
+            format: int64
+            type: integer
+        - description: |
+            Number of seconds to collect statistics.
+
+            `seconds` is mutually exclusive with `debug=1`.
+          in: query
+          name: seconds
+          schema:
+            format: int64
+            type: string
+      responses:
+        '200':
+          content:
+            application/octet-stream:
+              schema:
+                description: >
+                  [Go runtime profile](https://pkg.go.dev/runtime/pprof) report
+                  in protocol buffer format.
+                externalDocs:
+                  description: Golang pprof package
+                  url: https://pkg.go.dev/net/http/pprof
+                format: binary
+                type: string
+            text/plain:
+              schema:
+                description: |
+                  Response body contains a report formatted in plain text.
+                  The report contains comments that translate addresses to
+                  function names and line numbers for debugging.
+                externalDocs:
+                  description: Golang pprof package
+                  url: https://pkg.go.dev/net/http/pprof
+                format: Go runtime profile
+                type: string
+          description: >
+            [Go runtime profile](https://pkg.go.dev/runtime/pprof) report
+            compatible
+
+            with [pprof](https://github.com/google/pprof) analysis and
+            visualization tools.
+
+            If debug is enabled (`?debug=1`), response body contains a
+            human-readable profile.
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      servers: []
+      summary: Retrieve the mutual exclusion (mutex) runtime profile
+      tags:
+        - Debug
+      x-codeSamples:
+        - label: 'Shell: go tool pprof'
+          lang: Shell
+          source: >
+            # Analyze the profile in interactive mode.
+
+
+            go tool pprof http://localhost:8086/debug/pprof/mutex
+
+
+            # `pprof` returns the following prompt:
+
+            #   Entering interactive mode (type "help" for commands, "o" for
+            options)
+
+            #   (pprof)
+
+
+            #  At the prompt, get the top N entries.
+
+
+            (pprof) top10
+  /debug/pprof/profile:
+    get:
+      description: >
+        Collects statistics and returns a [Go runtime
+        profile](https://pkg.go.dev/runtime/pprof)
+
+        report of program counters on the executing stack.
+      operationId: GetDebugPprofProfile
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: Number of seconds to collect profile data. Default is `30` seconds.
+          in: query
+          name: seconds
+          schema:
+            format: int64
+            type: string
+      responses:
+        '200':
+          content:
+            application/octet-stream:
+              schema:
+                description: >
+                  [Go runtime profile](https://pkg.go.dev/runtime/pprof) report
+                  in protocol buffer format.
+                externalDocs:
+                  description: Golang pprof package
+                  url: https://pkg.go.dev/net/http/pprof
+                format: binary
+                type: string
+          description: >
+            [Go runtime profile](https://pkg.go.dev/runtime/pprof) report
+            compatible
+
+            with [pprof](https://github.com/google/pprof) analysis and
+            visualization tools.
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      servers: []
+      summary: Retrieve the CPU runtime profile
+      tags:
+        - Debug
+      x-codeSamples:
+        - label: 'Shell: go tool pprof'
+          lang: Shell
+          source: |
+            # Download the profile report.
+
+            curl http://localhost:8086/debug/pprof/profile -o cpu
+
+            # Analyze the profile in interactive mode.
+
+            go tool pprof ./cpu
+
+            # At the prompt, get the top N functions most often running
+            # or waiting during the sample period.
+
+            (pprof) top10
+  /debug/pprof/threadcreate:
+    get:
+      description: >
+        Collects statistics and returns a [Go runtime
+        profile](https://pkg.go.dev/runtime/pprof)
+
+        report of stack traces that led to the creation of new OS threads.
+      operationId: GetDebugPprofThreadCreate
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: >
+            - `0`: (Default) Return the report as a gzip-compressed protocol
+            buffer.
+
+            - `1`: Return a response body with the report formatted as
+            human-readable text.
+              The report contains comments that translate addresses to function names and line numbers for debugging.
+
+            `debug=1` is mutually exclusive with the `seconds` query parameter.
+          in: query
+          name: debug
+          schema:
+            enum:
+              - 0
+              - 1
+            format: int64
+            type: integer
+        - description: |
+            Number of seconds to collect statistics.
+
+            `seconds` is mutually exclusive with `debug=1`.
+          in: query
+          name: seconds
+          schema:
+            format: int64
+            type: string
+      responses:
+        '200':
+          content:
+            application/octet-stream:
+              schema:
+                description: >
+                  [Go runtime profile](https://pkg.go.dev/runtime/pprof) report
+                  in protocol buffer format.
+                externalDocs:
+                  description: Golang pprof package
+                  url: https://pkg.go.dev/net/http/pprof
+                format: binary
+                type: string
+            text/plain:
+              examples:
+                profileDebugResponse:
+                  summary: Profile in plain text
+                  value: "threadcreate profile: total 26\n25 @\n#\t0x0\n\n1 @ 0x403dda8 0x403e54b 0x403e810 0x403a90c 0x406c0a1\n#\t0x403dda7\truntime.allocm+0xc7\t\t\t/Users/me/.gvm/gos/go1.17/src/runtime/proc.go:1877\n#\t0x403e54a\truntime.newm+0x2a\t\t\t/Users/me/.gvm/gos/go1.17/src/runtime/proc.go:2201\n#\t0x403e80f\truntime.startTemplateThread+0x8f\t/Users/me/.gvm/gos/go1.17/src/runtime/proc.go:2271\n#\t0x403a90b\truntime.main+0x1cb\t\t\t/Users/me/.gvm/gos/go1.17/src/runtime/proc.go:234\n"
+              schema:
+                description: |
+                  Response body contains a report formatted in plain text.
+                  The report contains comments that translate addresses to
+                  function names and line numbers for debugging.
+                externalDocs:
+                  description: Golang pprof package
+                  url: https://pkg.go.dev/net/http/pprof
+                format: Go runtime profile
+                type: string
+          description: >
+            [Go runtime profile](https://pkg.go.dev/runtime/pprof) report
+            compatible
+
+            with [pprof](https://github.com/google/pprof) analysis and
+            visualization tools.
+
+            If debug is enabled (`?debug=1`), response body contains a
+            human-readable profile.
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      servers: []
+      summary: Retrieve the threadcreate runtime profile
+      tags:
+        - Debug
+      x-codeSamples:
+        - label: 'Shell: go tool pprof'
+          lang: Shell
+          source: >
+            # Analyze the profile in interactive mode.
+
+
+            go tool pprof http://localhost:8086/debug/pprof/threadcreate
+
+
+            # `pprof` returns the following prompt:
+
+            #   Entering interactive mode (type "help" for commands, "o" for
+            options)
+
+            #   (pprof)
+
+
+            #  At the prompt, get the top N entries.
+
+
+            (pprof) top10
+  /debug/pprof/trace:
+    get:
+      description: >
+        Collects profile data and returns trace execution events for the current
+        program.
+      operationId: GetDebugPprofTrace
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: Number of seconds to collect profile data.
+          in: query
+          name: seconds
+          schema:
+            format: int64
+            type: string
+      responses:
+        '200':
+          content:
+            application/octet-stream:
+              schema:
+                externalDocs:
+                  description: Golang trace package
+                  url: https://pkg.go.dev/runtime/trace
+                format: binary
+                type: string
+          description: |
+            [Trace file](https://pkg.go.dev/runtime/trace) compatible
+            with the [Golang `trace` command](https://pkg.go.dev/cmd/trace).
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      servers: []
+      summary: Retrieve the runtime execution trace
+      tags:
+        - Debug
+      x-codeSamples:
+        - label: 'Shell: go tool trace'
+          lang: Shell
+          source: |
+            # Download the trace file.
+
+            curl http://localhost:8086/debug/pprof/trace -o trace
+
+            # Analyze the trace.
+
+            go tool trace ./trace
+  /api/v2/delete:
+    post:
+      operationId: PostDelete
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: Specifies the organization to delete data from.
+          in: query
+          name: org
+          schema:
+            description: Only points from this organization are deleted.
+            type: string
+        - description: Specifies the bucket to delete data from.
+          in: query
+          name: bucket
+          schema:
+            description: Only points from this bucket are deleted.
+            type: string
+        - description: Specifies the organization ID of the resource.
+          in: query
+          name: orgID
+          schema:
+            type: string
+        - description: Specifies the bucket ID to delete data from.
+          in: query
+          name: bucketID
+          schema:
+            description: Only points from this bucket ID are deleted.
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/DeletePredicateRequest'
+        description: Deletes data from an InfluxDB bucket.
+        required: true
+      responses:
+        '204':
+          description: delete has been accepted
+        '400':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Invalid request.
+        '403':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: no token was sent or does not have sufficient permissions.
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: the bucket or organization is not found.
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: internal server error
+      summary: Delete data
+      tags:
+        - Delete
+  /api/v2/flags:
+    get:
+      operationId: GetFlags
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Flags'
+          description: Feature flags for the currently authenticated user
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Return the feature flags for the currently authenticated user
+      tags:
+        - Users
+  /health:
+    get:
+      description: Returns the health of the instance.
+      operationId: GetHealth
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/HealthCheck'
+          description: |
+            The instance is healthy.
+            The response body contains the health check items and status.
+        '503':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/HealthCheck'
+          description: The instance is unhealthy.
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      servers: []
+      summary: Retrieve the health of the instance
+      tags:
+        - Health
+  /api/v2/labels:
+    get:
+      operationId: GetLabels
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The organization ID.
+          in: query
+          name: orgID
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/LabelsResponse'
+          description: A list of labels
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List all labels
+      tags:
+        - Labels
+    post:
+      operationId: PostLabels
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/LabelCreateRequest'
+        description: Label to create
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/LabelResponse'
+          description: Added label
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Create a label
+      tags:
+        - Labels
+  /api/v2/labels/{labelID}:
+    delete:
+      operationId: DeleteLabelsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the label to delete.
+          in: path
+          name: labelID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Delete has been accepted
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Label not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Delete a label
+      tags:
+        - Labels
+    get:
+      operationId: GetLabelsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the label to update.
+          in: path
+          name: labelID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/LabelResponse'
+          description: A label
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Retrieve a label
+      tags:
+        - Labels
+    patch:
+      operationId: PatchLabelsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the label to update.
+          in: path
+          name: labelID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/LabelUpdate'
+        description: Label update
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/LabelResponse'
+          description: Updated label
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Label not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Update a label
+      tags:
+        - Labels
+  /legacy/authorizations:
+    get:
+      operationId: GetLegacyAuthorizations
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: Only show legacy authorizations that belong to a user ID.
+          in: query
+          name: userID
+          schema:
+            type: string
+        - description: Only show legacy authorizations that belong to a user name.
+          in: query
+          name: user
+          schema:
+            type: string
+        - description: Only show legacy authorizations that belong to an organization ID.
+          in: query
+          name: orgID
+          schema:
+            type: string
+        - description: Only show legacy authorizations that belong to a organization name.
+          in: query
+          name: org
+          schema:
+            type: string
+        - description: Only show legacy authorizations with a specified token (auth name).
+          in: query
+          name: token
+          schema:
+            type: string
+        - description: Only show legacy authorizations with a specified auth ID.
+          in: query
+          name: authID
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Authorizations'
+          description: A list of legacy authorizations
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      summary: List all legacy authorizations
+      tags:
+        - Legacy Authorizations
+    post:
+      operationId: PostLegacyAuthorizations
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/LegacyAuthorizationPostRequest'
+        description: Legacy authorization to create
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Authorization'
+          description: Legacy authorization created
+        '400':
+          $ref: '#/components/responses/ServerError'
+          description: Invalid request
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      summary: Create a legacy authorization
+      tags:
+        - Legacy Authorizations
+    servers:
+      - url: /private
+  /legacy/authorizations/{authID}:
+    delete:
+      operationId: DeleteLegacyAuthorizationsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the legacy authorization to delete.
+          in: path
+          name: authID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Legacy authorization deleted
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      summary: Delete a legacy authorization
+      tags:
+        - Legacy Authorizations
+    get:
+      operationId: GetLegacyAuthorizationsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the legacy authorization to get.
+          in: path
+          name: authID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Authorization'
+          description: Legacy authorization details
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      summary: Retrieve a legacy authorization
+      tags:
+        - Legacy Authorizations
+    patch:
+      operationId: PatchLegacyAuthorizationsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the legacy authorization to update.
+          in: path
+          name: authID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/AuthorizationUpdateRequest'
+        description: Legacy authorization to update
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Authorization'
+          description: The active or inactive legacy authorization
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      summary: Update a legacy authorization to be active or inactive
+      tags:
+        - Legacy Authorizations
+    servers:
+      - url: /private
+  /legacy/authorizations/{authID}/password:
+    post:
+      operationId: PostLegacyAuthorizationsIDPassword
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the legacy authorization to update.
+          in: path
+          name: authID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/PasswordResetBody'
+        description: New password
+        required: true
+      responses:
+        '204':
+          description: Legacy authorization password set
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      summary: Set a legacy authorization password
+      tags:
+        - Legacy Authorizations
+    servers:
+      - url: /private
+  /api/v2/maps/mapToken:
+    get:
+      operationId: getMapboxToken
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Token'
+          description: Temporary token for Mapbox.
+        '401':
+          $ref: '#/components/responses/ServerError'
+        '500':
+          $ref: '#/components/responses/ServerError'
+        default:
+          $ref: '#/components/responses/ServerError'
+      summary: Get a mapbox token
+  /api/v2/me:
+    get:
+      operationId: GetMe
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/UserResponse'
+          description: The currently authenticated user.
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Retrieve the currently authenticated user
+      tags:
+        - Users
+  /api/v2/me/password:
+    put:
+      operationId: PutMePassword
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/PasswordResetBody'
+        description: New password
+        required: true
+      responses:
+        '204':
+          description: Password successfully updated
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unsuccessful authentication
+      security:
+        - BasicAuthentication: []
+      summary: Update a password
+      tags:
+        - Users
+  /metrics:
+    get:
+      description: >
+        Returns metrics about the workload performance of an InfluxDB instance.
+
+
+        Use this endpoint to get performance, resource, and usage metrics.
+
+
+        #### Related guides
+
+
+        - For the list of metrics categories, see [InfluxDB OSS
+        metrics](https://docs.influxdata.com/influxdb/v2.2/reference/internals/metrics/).
+
+        - Learn how to use InfluxDB to [scrape Prometheus
+        metrics](https://docs.influxdata.com/influxdb/v2.2write-data/developer-tools/scrape-prometheus-metrics/).
+
+        - Learn how InfluxDB [parses the Prometheus exposition
+        format](https://docs.influxdata.com/influxdb/v2.2/reference/prometheus-metrics/).
+      operationId: GetMetrics
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+      responses:
+        '200':
+          content:
+            text/plain:
+              examples:
+                expositionResponse:
+                  summary: Metrics in plain text
+                  value: >
+                    # HELP go_threads Number of OS threads created.
+
+                    # TYPE go_threads gauge
+
+                    go_threads 19
+
+                    # HELP http_api_request_duration_seconds Time taken to
+                    respond to HTTP request
+
+                    # TYPE http_api_request_duration_seconds histogram
+
+                    http_api_request_duration_seconds_bucket{handler="platform",method="GET",path="/:fallback_path",response_code="200",status="2XX",user_agent="curl",le="0.005"}
+                    4
+
+                    http_api_request_duration_seconds_bucket{handler="platform",method="GET",path="/:fallback_path",response_code="200",status="2XX",user_agent="curl",le="0.01"}
+                    4
+
+                    http_api_request_duration_seconds_bucket{handler="platform",method="GET",path="/:fallback_path",response_code="200",status="2XX",user_agent="curl",le="0.025"}
+                    5
+              schema:
+                externalDocs:
+                  description: Prometheus exposition formats
+                  url: https://prometheus.io/docs/instrumenting/exposition_formats
+                format: Prometheus text-based exposition
+                type: string
+          description: >
+            Success. The response body contains metrics in
+
+            [Prometheus plain-text exposition
+            format](https://prometheus.io/docs/instrumenting/exposition_formats)
+
+            Metrics contain a name, an optional set of key-value pairs, and a
+            value.
+
+
+            The following descriptors precede each metric:
+
+
+            - `HELP`: description of the metric
+
+            - `TYPE`: [Prometheus metric
+            type](https://prometheus.io/docs/concepts/metric_types/) (`counter`,
+            `gauge`, `histogram`, or `summary`)
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      servers: []
+      summary: Retrieve workload performance metrics
+      tags:
+        - Metrics
+  /api/v2/notificationEndpoints:
+    get:
+      operationId: GetNotificationEndpoints
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - $ref: '#/components/parameters/Offset'
+        - $ref: '#/components/parameters/Limit'
+        - description: >-
+            Only show notification endpoints that belong to specific
+            organization ID.
+          in: query
+          name: orgID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/NotificationEndpoints'
+          description: A list of notification endpoints
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List all notification endpoints
+      tags:
+        - NotificationEndpoints
+    post:
+      operationId: CreateNotificationEndpoint
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/PostNotificationEndpoint'
+        description: Notification endpoint to create
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/NotificationEndpoint'
+          description: Notification endpoint created
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Add a notification endpoint
+      tags:
+        - NotificationEndpoints
+  /api/v2/notificationEndpoints/{endpointID}:
+    delete:
+      operationId: DeleteNotificationEndpointsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The notification endpoint ID.
+          in: path
+          name: endpointID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Delete has been accepted
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: The endpoint was not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Delete a notification endpoint
+      tags:
+        - NotificationEndpoints
+    get:
+      operationId: GetNotificationEndpointsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The notification endpoint ID.
+          in: path
+          name: endpointID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/NotificationEndpoint'
+          description: The notification endpoint requested
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Retrieve a notification endpoint
+      tags:
+        - NotificationEndpoints
+    patch:
+      operationId: PatchNotificationEndpointsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The notification endpoint ID.
+          in: path
+          name: endpointID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/NotificationEndpointUpdate'
+        description: Check update to apply
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/NotificationEndpoint'
+          description: An updated notification endpoint
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: The notification endpoint was not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Update a notification endpoint
+      tags:
+        - NotificationEndpoints
+    put:
+      operationId: PutNotificationEndpointsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The notification endpoint ID.
+          in: path
+          name: endpointID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/NotificationEndpoint'
+        description: A new notification endpoint to replace the existing endpoint with
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/NotificationEndpoint'
+          description: An updated notification endpoint
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: The notification endpoint was not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Update a notification endpoint
+      tags:
+        - NotificationEndpoints
+  /api/v2/notificationEndpoints/{endpointID}/labels:
+    get:
+      operationId: GetNotificationEndpointsIDLabels
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The notification endpoint ID.
+          in: path
+          name: endpointID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/LabelsResponse'
+          description: A list of all labels for a notification endpoint
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List all labels for a notification endpoint
+      tags:
+        - NotificationEndpoints
+    post:
+      operationId: PostNotificationEndpointIDLabels
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The notification endpoint ID.
+          in: path
+          name: endpointID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/LabelMapping'
+        description: Label to add
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/LabelResponse'
+          description: The label was added to the notification endpoint
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Add a label to a notification endpoint
+      tags:
+        - NotificationEndpoints
+  /api/v2/notificationEndpoints/{endpointID}/labels/{labelID}:
+    delete:
+      operationId: DeleteNotificationEndpointsIDLabelsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The notification endpoint ID.
+          in: path
+          name: endpointID
+          required: true
+          schema:
+            type: string
+        - description: The ID of the label to delete.
+          in: path
+          name: labelID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Delete has been accepted
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Endpoint or label not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Delete a label from a notification endpoint
+      tags:
+        - NotificationEndpoints
+  /api/v2/notificationRules:
+    get:
+      operationId: GetNotificationRules
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - $ref: '#/components/parameters/Offset'
+        - $ref: '#/components/parameters/Limit'
+        - description: >-
+            Only show notification rules that belong to a specific organization
+            ID.
+          in: query
+          name: orgID
+          required: true
+          schema:
+            type: string
+        - description: Only show notifications that belong to the specific check ID.
+          in: query
+          name: checkID
+          schema:
+            type: string
+        - description: >-
+            Only return notification rules that "would match" statuses which
+            contain the tag key value pairs provided.
+          in: query
+          name: tag
+          schema:
+            example: env:prod
+            pattern: ^[a-zA-Z0-9_]+:[a-zA-Z0-9_]+$
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/NotificationRules'
+          description: A list of notification rules
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List all notification rules
+      tags:
+        - NotificationRules
+    post:
+      operationId: CreateNotificationRule
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/PostNotificationRule'
+        description: Notification rule to create
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/NotificationRule'
+          description: Notification rule created
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Add a notification rule
+      tags:
+        - NotificationRules
+  /api/v2/notificationRules/{ruleID}:
+    delete:
+      operationId: DeleteNotificationRulesID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The notification rule ID.
+          in: path
+          name: ruleID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Delete has been accepted
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: The check was not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Delete a notification rule
+      tags:
+        - NotificationRules
+    get:
+      operationId: GetNotificationRulesID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The notification rule ID.
+          in: path
+          name: ruleID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/NotificationRule'
+          description: The notification rule requested
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Retrieve a notification rule
+      tags:
+        - NotificationRules
+    patch:
+      operationId: PatchNotificationRulesID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The notification rule ID.
+          in: path
+          name: ruleID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/NotificationRuleUpdate'
+        description: Notification rule update to apply
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/NotificationRule'
+          description: An updated notification rule
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: The notification rule was not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Update a notification rule
+      tags:
+        - NotificationRules
+    put:
+      operationId: PutNotificationRulesID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The notification rule ID.
+          in: path
+          name: ruleID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/NotificationRule'
+        description: Notification rule update to apply
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/NotificationRule'
+          description: An updated notification rule
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: The notification rule was not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Update a notification rule
+      tags:
+        - NotificationRules
+  /api/v2/notificationRules/{ruleID}/labels:
+    get:
+      operationId: GetNotificationRulesIDLabels
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The notification rule ID.
+          in: path
+          name: ruleID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/LabelsResponse'
+          description: A list of all labels for a notification rule
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List all labels for a notification rule
+      tags:
+        - NotificationRules
+    post:
+      operationId: PostNotificationRuleIDLabels
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The notification rule ID.
+          in: path
+          name: ruleID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/LabelMapping'
+        description: Label to add
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/LabelResponse'
+          description: The label was added to the notification rule
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Add a label to a notification rule
+      tags:
+        - NotificationRules
+  /api/v2/notificationRules/{ruleID}/labels/{labelID}:
+    delete:
+      operationId: DeleteNotificationRulesIDLabelsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The notification rule ID.
+          in: path
+          name: ruleID
+          required: true
+          schema:
+            type: string
+        - description: The ID of the label to delete.
+          in: path
+          name: labelID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Delete has been accepted
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Rule or label not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Delete label from a notification rule
+      tags:
+        - NotificationRules
+  /api/v2/notificationRules/{ruleID}/query:
+    get:
+      operationId: GetNotificationRulesIDQuery
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The notification rule ID.
+          in: path
+          name: ruleID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/FluxResponse'
+          description: The notification rule query requested
+        '400':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Invalid request
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Notification rule not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Retrieve a notification rule query
+      tags:
+        - Rules
+  /api/v2/orgs:
+    get:
+      operationId: GetOrgs
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - $ref: '#/components/parameters/Offset'
+        - $ref: '#/components/parameters/Limit'
+        - $ref: '#/components/parameters/Descending'
+        - description: Filter organizations to a specific organization name.
+          in: query
+          name: org
+          schema:
+            type: string
+        - description: Filter organizations to a specific organization ID.
+          in: query
+          name: orgID
+          schema:
+            type: string
+        - description: Filter organizations to a specific user ID.
+          in: query
+          name: userID
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Organizations'
+          description: A list of organizations
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List all organizations
+      tags:
+        - Organizations
+    post:
+      operationId: PostOrgs
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/PostOrganizationRequest'
+        description: Organization to create
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Organization'
+          description: Organization created
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Create an organization
+      tags:
+        - Organizations
+  /api/v2/orgs/{orgID}:
+    delete:
+      operationId: DeleteOrgsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the organization to delete.
+          in: path
+          name: orgID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Delete has been accepted
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Organization not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Delete an organization
+      tags:
+        - Organizations
+    get:
+      operationId: GetOrgsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the organization to get.
+          in: path
+          name: orgID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Organization'
+          description: Organization details
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Retrieve an organization
+      tags:
+        - Organizations
+    patch:
+      operationId: PatchOrgsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the organization to get.
+          in: path
+          name: orgID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/PatchOrganizationRequest'
+        description: Organization update to apply
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Organization'
+          description: Organization updated
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Update an organization
+      tags:
+        - Organizations
+  /api/v2/orgs/{orgID}/members:
+    get:
+      operationId: GetOrgsIDMembers
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The organization ID.
+          in: path
+          name: orgID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ResourceMembers'
+          description: A list of organization members
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Organization not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List all members of an organization
+      tags:
+        - Organizations
+    post:
+      operationId: PostOrgsIDMembers
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The organization ID.
+          in: path
+          name: orgID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/AddResourceMemberRequestBody'
+        description: User to add as member
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ResourceMember'
+          description: Added to organization created
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Add a member to an organization
+      tags:
+        - Organizations
+  /api/v2/orgs/{orgID}/members/{userID}:
+    delete:
+      operationId: DeleteOrgsIDMembersID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the member to remove.
+          in: path
+          name: userID
+          required: true
+          schema:
+            type: string
+        - description: The organization ID.
+          in: path
+          name: orgID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Member removed
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Remove a member from an organization
+      tags:
+        - Organizations
+  /api/v2/orgs/{orgID}/owners:
+    get:
+      operationId: GetOrgsIDOwners
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The organization ID.
+          in: path
+          name: orgID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ResourceOwners'
+          description: A list of organization owners
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Organization not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List all owners of an organization
+      tags:
+        - Organizations
+    post:
+      operationId: PostOrgsIDOwners
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The organization ID.
+          in: path
+          name: orgID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/AddResourceMemberRequestBody'
+        description: User to add as owner
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ResourceOwner'
+          description: Organization owner added
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Add an owner to an organization
+      tags:
+        - Organizations
+  /api/v2/orgs/{orgID}/owners/{userID}:
+    delete:
+      operationId: DeleteOrgsIDOwnersID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the owner to remove.
+          in: path
+          name: userID
+          required: true
+          schema:
+            type: string
+        - description: The organization ID.
+          in: path
+          name: orgID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Owner removed
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Remove an owner from an organization
+      tags:
+        - Organizations
+  /api/v2/orgs/{orgID}/secrets:
+    get:
+      operationId: GetOrgsIDSecrets
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The organization ID.
+          in: path
+          name: orgID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/SecretKeysResponse'
+          description: A list of all secret keys
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List all secret keys for an organization
+      tags:
+        - Secrets
+    patch:
+      operationId: PatchOrgsIDSecrets
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The organization ID.
+          in: path
+          name: orgID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/Secrets'
+        description: Secret key value pairs to update/add
+        required: true
+      responses:
+        '204':
+          description: Keys successfully patched
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Update secrets in an organization
+      tags:
+        - Secrets
+  /api/v2/orgs/{orgID}/secrets/{secretID}:
+    delete:
+      operationId: DeleteOrgsIDSecretsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The organization ID.
+          in: path
+          name: orgID
+          required: true
+          schema:
+            type: string
+        - description: The secret ID.
+          in: path
+          name: secretID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Keys successfully deleted
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      summary: Delete a secret from an organization
+      tags:
+        - Secrets
+  /api/v2/orgs/{orgID}/secrets/delete:
+    post:
+      deprecated: true
+      operationId: PostOrgsIDSecrets
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The organization ID.
+          in: path
+          name: orgID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/SecretKeys'
+        description: Secret key to delete
+        required: true
+      responses:
+        '204':
+          description: Keys successfully patched
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Delete secrets from an organization
+      tags:
+        - Secrets
+  /ping:
+    get:
+      description: Returns the status and InfluxDB version of the instance.
+      operationId: GetPing
+      responses:
+        '204':
+          description: |
+            OK.
+            Headers contain InfluxDB version information.
+          headers:
+            X-Influxdb-Build:
+              description: The type of InfluxDB build.
+              schema:
+                type: string
+            X-Influxdb-Version:
+              description: The version of InfluxDB.
+              schema:
+                type: integer
+      servers: []
+      summary: Get the status and version of the instance
+      tags:
+        - Ping
+    head:
+      description: Returns the status and InfluxDB version of the instance.
+      operationId: HeadPing
+      responses:
+        '204':
+          description: |
+            OK.
+            Headers contain InfluxDB version information.
+          headers:
+            X-Influxdb-Build:
+              description: The type of InfluxDB build.
+              schema:
+                type: string
+            X-Influxdb-Version:
+              description: The version of InfluxDB.
+              schema:
+                type: integer
+      servers: []
+      summary: Get the status and version of the instance
+      tags:
+        - Ping
+  /api/v2/query:
+    post:
+      description: >
+        Retrieves data from InfluxDB buckets.
+
+
+        To query data, you need the following:
+
+        - **organization** – _See [View
+        organizations](https://docs.influxdata.com/influxdb/v2.2/organizations/view-orgs/#view-your-organization-id)
+        for instructions on viewing your organization ID._
+
+        - **API token** – _See [View
+        tokens](https://docs.influxdata.com/influxdb/v2.2/security/tokens/view-tokens/)
+         for instructions on viewing your API token._
+        - **InfluxDB URL** – _See [InfluxDB
+        URLs](https://docs.influxdata.com/influxdb/v2.2/reference/urls/)_.
+
+        - **Flux query** – _See [Flux](https://docs.influxdata.com/flux/v0.x/)._
+
+
+        For more information and examples, see [Query with the InfluxDB
+        API](https://docs.influxdata.com/influxdb/v2.2/query-data/execute-queries/influx-api/).
+      operationId: PostQuery
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: >-
+            Indicates the content encoding (usually a compression algorithm)
+            that the client can understand.
+          in: header
+          name: Accept-Encoding
+          schema:
+            default: identity
+            description: >-
+              The content coding.  Use `gzip` for compressed data or `identity`
+              for unmodified, uncompressed data.
+            enum:
+              - gzip
+              - identity
+            type: string
+        - in: header
+          name: Content-Type
+          schema:
+            enum:
+              - application/json
+              - application/vnd.flux
+            type: string
+        - description: >-
+            Name of the organization executing the query. Accepts either the ID
+            or Name. If you provide both `orgID` and `org`, `org` takes
+            precedence.
+          in: query
+          name: org
+          schema:
+            type: string
+        - description: >-
+            ID of the organization executing the query. If you provide both
+            `orgID` and `org`, `org` takes precedence.
+          in: query
+          name: orgID
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/Query'
+          application/vnd.flux:
+            example: |
+              from(bucket: "example-bucket")
+                  |> range(start: -5m)
+                  |> filter(fn: (r) => r._measurement == "example-measurement")
+            schema:
+              type: string
+        description: Flux query or specification to execute
+      responses:
+        '200':
+          content:
+            text/csv:
+              schema:
+                example: >
+                  result,table,_start,_stop,_time,region,host,_value
+                  mean,0,2018-05-08T20:50:00Z,2018-05-08T20:51:00Z,2018-05-08T20:50:00Z,east,A,15.43
+                  mean,0,2018-05-08T20:50:00Z,2018-05-08T20:51:00Z,2018-05-08T20:50:20Z,east,B,59.25
+                  mean,0,2018-05-08T20:50:00Z,2018-05-08T20:51:00Z,2018-05-08T20:50:40Z,east,C,52.62
+                type: string
+          description: Success. Returns query results.
+          headers:
+            Content-Encoding:
+              description: >-
+                Lists any encodings (usually compression algorithms) that have
+                been applied to the response payload.
+              schema:
+                default: identity
+                description: >
+                  Content coding: `gzip` for compressed data or `identity` for
+                  unmodified, uncompressed data.
+                enum:
+                  - gzip
+                  - identity
+                type: string
+            Trace-Id:
+              description: If generated, trace ID of the request.
+              schema:
+                description: Trace ID of a request.
+                type: string
+        '429':
+          description: |
+            #### InfluxDB Cloud:
+              - returns this error if a **read** or **write** request exceeds your
+                plan's [adjustable service quotas](https://docs.influxdata.com/influxdb/v2.2/account-management/limits/#adjustable-service-quotas)
+                or if a **delete** request exceeds the maximum
+                [global limit](https://docs.influxdata.com/influxdb/v2.2/account-management/limits/#global-limits)
+              - returns `Retry-After` header that describes when to try the write again.
+
+            #### InfluxDB OSS:
+              - doesn't return this error.
+          headers:
+            Retry-After:
+              description: >-
+                Non-negative decimal integer indicating seconds to wait before
+                retrying the request.
+              schema:
+                format: int32
+                type: integer
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Error processing query
+      summary: Query data
+      tags:
+        - Query
+  /api/v2/query/analyze:
+    post:
+      operationId: PostQueryAnalyze
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - in: header
+          name: Content-Type
+          schema:
+            enum:
+              - application/json
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/Query'
+        description: Flux query to analyze
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/AnalyzeQueryResponse'
+          description: Query analyze results. Errors will be empty if the query is valid.
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Internal server error
+          headers:
+            X-Influx-Error:
+              description: Error string describing the problem
+              schema:
+                type: string
+            X-Influx-Reference:
+              description: Reference code unique to the error type
+              schema:
+                type: integer
+      summary: Analyze a Flux query
+      tags:
+        - Query
+  /api/v2/query/ast:
+    post:
+      description: Analyzes flux query and generates a query specification.
+      operationId: PostQueryAst
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - in: header
+          name: Content-Type
+          schema:
+            enum:
+              - application/json
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/LanguageRequest'
+        description: Analyzed Flux query to generate abstract syntax tree.
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ASTResponse'
+          description: Abstract syntax tree of the flux query.
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Any response other than 200 is an internal server error
+      summary: Generate an Abstract Syntax Tree (AST) from a query
+      tags:
+        - Query
+  /api/v2/query/suggestions:
+    get:
+      operationId: GetQuerySuggestions
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/FluxSuggestions'
+          description: Suggestions for next functions in call chain
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Any response other than 200 is an internal server error
+      summary: Retrieve query suggestions
+      tags:
+        - Query
+  /api/v2/query/suggestions/{name}:
+    get:
+      operationId: GetQuerySuggestionsName
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The name of the branching suggestion.
+          in: path
+          name: name
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/FluxSuggestion'
+          description: Suggestions for next functions in call chain
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Any response other than 200 is an internal server error
+      summary: Retrieve query suggestions for a branching suggestion
+      tags:
+        - Query
+  /ready:
+    get:
+      operationId: GetReady
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Ready'
+          description: The instance is ready
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      servers: []
+      summary: Get the readiness of an instance at startup
+      tags:
+        - Ready
+  /api/v2/remotes:
+    get:
+      operationId: GetRemoteConnections
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The organization ID.
+          in: query
+          name: orgID
+          required: true
+          schema:
+            type: string
+        - in: query
+          name: name
+          schema:
+            type: string
+        - in: query
+          name: remoteURL
+          schema:
+            format: uri
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/RemoteConnections'
+          description: List of remote connections
+        '404':
+          $ref: '#/components/responses/ServerError'
+        default:
+          $ref: '#/components/responses/ServerError'
+      summary: List all remote connections
+      tags:
+        - RemoteConnections
+    post:
+      operationId: PostRemoteConnection
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/RemoteConnectionCreationRequest'
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/RemoteConnection'
+          description: Remote connection saved
+        '400':
+          $ref: '#/components/responses/ServerError'
+        default:
+          $ref: '#/components/responses/ServerError'
+      summary: Register a new remote connection
+      tags:
+        - RemoteConnections
+  /api/v2/remotes/{remoteID}:
+    delete:
+      operationId: DeleteRemoteConnectionByID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - in: path
+          name: remoteID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Remote connection info deleted.
+        '404':
+          $ref: '#/components/responses/ServerError'
+        default:
+          $ref: '#/components/responses/ServerError'
+      summary: Delete a remote connection
+      tags:
+        - RemoteConnections
+    get:
+      operationId: GetRemoteConnectionByID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - in: path
+          name: remoteID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/RemoteConnection'
+          description: Remote connection
+        '404':
+          $ref: '#/components/responses/ServerError'
+        default:
+          $ref: '#/components/responses/ServerError'
+      summary: Retrieve a remote connection
+      tags:
+        - RemoteConnections
+    patch:
+      operationId: PatchRemoteConnectionByID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - in: path
+          name: remoteID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/RemoteConnectionUpdateRequest'
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/RemoteConnection'
+          description: Updated information saved
+        '400':
+          $ref: '#/components/responses/ServerError'
+        '404':
+          $ref: '#/components/responses/ServerError'
+        default:
+          $ref: '#/components/responses/ServerError'
+      summary: Update a remote connection
+      tags:
+        - RemoteConnections
+  /api/v2/replications:
+    get:
+      operationId: GetReplications
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The organization ID.
+          in: query
+          name: orgID
+          required: true
+          schema:
+            type: string
+        - in: query
+          name: name
+          schema:
+            type: string
+        - in: query
+          name: remoteID
+          schema:
+            type: string
+        - in: query
+          name: localBucketID
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Replications'
+          description: List of replications
+        '404':
+          $ref: '#/components/responses/ServerError'
+        default:
+          $ref: '#/components/responses/ServerError'
+      summary: List all replications
+      tags:
+        - Replications
+    post:
+      operationId: PostReplication
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: If true, validate the replication, but don't save it.
+          in: query
+          name: validate
+          schema:
+            default: false
+            type: boolean
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/ReplicationCreationRequest'
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Replication'
+          description: Replication saved
+        '204':
+          description: Replication validated, but not saved
+        '400':
+          $ref: '#/components/responses/ServerError'
+        default:
+          $ref: '#/components/responses/ServerError'
+      summary: Register a new replication
+      tags:
+        - Replications
+  /api/v2/replications/{replicationID}:
+    delete:
+      operationId: DeleteReplicationByID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - in: path
+          name: replicationID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Replication deleted.
+        '404':
+          $ref: '#/components/responses/ServerError'
+        default:
+          $ref: '#/components/responses/ServerError'
+      summary: Delete a replication
+      tags:
+        - Replications
+    get:
+      operationId: GetReplicationByID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - in: path
+          name: replicationID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Replication'
+          description: Replication
+        '404':
+          $ref: '#/components/responses/ServerError'
+        default:
+          $ref: '#/components/responses/ServerError'
+      summary: Retrieve a replication
+      tags:
+        - Replications
+    patch:
+      operationId: PatchReplicationByID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - in: path
+          name: replicationID
+          required: true
+          schema:
+            type: string
+        - description: If true, validate the updated information, but don't save it.
+          in: query
+          name: validate
+          schema:
+            default: false
+            type: boolean
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/ReplicationUpdateRequest'
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Replication'
+          description: Updated information saved
+        '204':
+          description: Updated replication validated, but not saved
+        '400':
+          $ref: '#/components/responses/ServerError'
+        '404':
+          $ref: '#/components/responses/ServerError'
+        default:
+          $ref: '#/components/responses/ServerError'
+      summary: Update a replication
+      tags:
+        - Replications
+  /api/v2/replications/{replicationID}/validate:
+    post:
+      operationId: PostValidateReplicationByID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - in: path
+          name: replicationID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Replication is valid
+        '400':
+          $ref: '#/components/responses/ServerError'
+          description: Replication failed validation
+        default:
+          $ref: '#/components/responses/ServerError'
+      summary: Validate a replication
+      tags:
+        - Replications
+  /api/v2/resources:
+    get:
+      operationId: GetResources
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                items:
+                  type: string
+                type: array
+          description: All resources targets
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Internal server error
+      summary: List all known resources
+      tags:
+        - Resources
+  /api/v2/restore/bucket/{bucketID}:
+    post:
+      deprecated: true
+      operationId: PostRestoreBucketID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The bucket ID.
+          in: path
+          name: bucketID
+          required: true
+          schema:
+            type: string
+        - in: header
+          name: Content-Type
+          schema:
+            default: application/octet-stream
+            enum:
+              - application/octet-stream
+            type: string
+      requestBody:
+        content:
+          text/plain:
+            schema:
+              format: byte
+              type: string
+        description: Database info serialized as protobuf.
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                format: byte
+                type: string
+          description: ID mappings for shards in bucket.
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      summary: Overwrite storage metadata for a bucket with shard info from a backup.
+      tags:
+        - Restore
+  /api/v2/restore/bucketMetadata:
+    post:
+      operationId: PostRestoreBucketMetadata
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/BucketMetadataManifest'
+        description: Metadata manifest for a bucket.
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/RestoredBucketMappings'
+          description: ID mappings for shards in new bucket.
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      summary: Create a new bucket pre-seeded with shard info from a backup.
+      tags:
+        - Restore
+  /api/v2/restore/kv:
+    post:
+      operationId: PostRestoreKV
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: >
+            The value tells InfluxDB what compression is applied to the line
+            protocol in the request payload.
+
+            To make an API request with a GZIP payload, send `Content-Encoding:
+            gzip` as a request header.
+          in: header
+          name: Content-Encoding
+          schema:
+            default: identity
+            description: >-
+              The content coding.  Use `gzip` for compressed data or `identity`
+              for unmodified, uncompressed data.
+            enum:
+              - gzip
+              - identity
+            type: string
+        - in: header
+          name: Content-Type
+          schema:
+            default: application/octet-stream
+            enum:
+              - application/octet-stream
+            type: string
+      requestBody:
+        content:
+          text/plain:
+            schema:
+              format: binary
+              type: string
+        description: Full KV snapshot.
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                properties:
+                  token:
+                    description: >-
+                      token is the root token for the instance after restore
+                      (this is overwritten during the restore)
+                    type: string
+                type: object
+          description: KV store successfully overwritten.
+        '204':
+          description: KV store successfully overwritten.
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      summary: Overwrite the embedded KV store on the server with a backed-up snapshot.
+      tags:
+        - Restore
+  /api/v2/restore/shards/{shardID}:
+    post:
+      operationId: PostRestoreShardId
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: >
+            The value tells InfluxDB what compression is applied to the line
+            protocol in the request payload.
+
+            To make an API request with a GZIP payload, send `Content-Encoding:
+            gzip` as a request header.
+          in: header
+          name: Content-Encoding
+          schema:
+            default: identity
+            description: >-
+              Specifies that the line protocol in the body is encoded with gzip
+              or not encoded with identity.
+            enum:
+              - gzip
+              - identity
+            type: string
+        - in: header
+          name: Content-Type
+          schema:
+            default: application/octet-stream
+            enum:
+              - application/octet-stream
+            type: string
+        - description: The shard ID.
+          in: path
+          name: shardID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          text/plain:
+            schema:
+              format: binary
+              type: string
+        description: TSM snapshot.
+        required: true
+      responses:
+        '204':
+          description: TSM snapshot successfully restored.
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      summary: Restore a TSM snapshot into a shard.
+      tags:
+        - Restore
+  /api/v2/restore/sql:
+    post:
+      operationId: PostRestoreSQL
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: >
+            The value tells InfluxDB what compression is applied to the line
+            protocol in the request payload.
+
+            To make an API request with a GZIP payload, send `Content-Encoding:
+            gzip` as a request header.
+          in: header
+          name: Content-Encoding
+          schema:
+            default: identity
+            description: >-
+              Specifies that the line protocol in the body is encoded with gzip
+              or not encoded with identity.
+            enum:
+              - gzip
+              - identity
+            type: string
+        - in: header
+          name: Content-Type
+          schema:
+            default: application/octet-stream
+            enum:
+              - application/octet-stream
+            type: string
+      requestBody:
+        content:
+          text/plain:
+            schema:
+              format: binary
+              type: string
+        description: Full SQL snapshot.
+        required: true
+      responses:
+        '204':
+          description: SQL store successfully overwritten.
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      summary: >-
+        Overwrite the embedded SQL store on the server with a backed-up
+        snapshot.
+      tags:
+        - Restore
+  /api/v2/scrapers:
+    get:
+      operationId: GetScrapers
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: Specifies the name of the scraper target.
+          in: query
+          name: name
+          schema:
+            type: string
+        - description: >-
+            List of scraper target IDs to return. If both `id` and `owner` are
+            specified, only `id` is used.
+          in: query
+          name: id
+          schema:
+            items:
+              type: string
+            type: array
+        - description: Specifies the organization ID of the scraper target.
+          in: query
+          name: orgID
+          schema:
+            type: string
+        - description: Specifies the organization name of the scraper target.
+          in: query
+          name: org
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ScraperTargetResponses'
+          description: All scraper targets
+      summary: List all scraper targets
+      tags:
+        - Scraper Targets
+    post:
+      operationId: PostScrapers
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/ScraperTargetRequest'
+        description: Scraper target to create
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ScraperTargetResponse'
+          description: Scraper target created
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Internal server error
+      summary: Create a scraper target
+      tags:
+        - Scraper Targets
+  /api/v2/scrapers/{scraperTargetID}:
+    delete:
+      operationId: DeleteScrapersID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The identifier of the scraper target.
+          in: path
+          name: scraperTargetID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Scraper target deleted
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Internal server error
+      summary: Delete a scraper target
+      tags:
+        - Scraper Targets
+    get:
+      operationId: GetScrapersID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The identifier of the scraper target.
+          in: path
+          name: scraperTargetID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ScraperTargetResponse'
+          description: The scraper target
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Internal server error
+      summary: Retrieve a scraper target
+      tags:
+        - Scraper Targets
+    patch:
+      operationId: PatchScrapersID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The identifier of the scraper target.
+          in: path
+          name: scraperTargetID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/ScraperTargetRequest'
+        description: Scraper target update to apply
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ScraperTargetResponse'
+          description: Scraper target updated
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Internal server error
+      summary: Update a scraper target
+      tags:
+        - Scraper Targets
+  /api/v2/scrapers/{scraperTargetID}/labels:
+    get:
+      operationId: GetScrapersIDLabels
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The scraper target ID.
+          in: path
+          name: scraperTargetID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/LabelsResponse'
+          description: A list of labels for a scraper target.
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List all labels for a scraper target
+      tags:
+        - Scraper Targets
+    post:
+      operationId: PostScrapersIDLabels
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The scraper target ID.
+          in: path
+          name: scraperTargetID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/LabelMapping'
+        description: Label to add
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/LabelResponse'
+          description: The newly added label
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Add a label to a scraper target
+      tags:
+        - Scraper Targets
+  /api/v2/scrapers/{scraperTargetID}/labels/{labelID}:
+    delete:
+      operationId: DeleteScrapersIDLabelsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The scraper target ID.
+          in: path
+          name: scraperTargetID
+          required: true
+          schema:
+            type: string
+        - description: The label ID.
+          in: path
+          name: labelID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Delete has been accepted
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Scraper target not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Delete a label from a scraper target
+      tags:
+        - Scraper Targets
+  /api/v2/scrapers/{scraperTargetID}/members:
+    get:
+      operationId: GetScrapersIDMembers
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The scraper target ID.
+          in: path
+          name: scraperTargetID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ResourceMembers'
+          description: A list of scraper target members
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List all users with member privileges for a scraper target
+      tags:
+        - Scraper Targets
+    post:
+      operationId: PostScrapersIDMembers
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The scraper target ID.
+          in: path
+          name: scraperTargetID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/AddResourceMemberRequestBody'
+        description: User to add as member
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ResourceMember'
+          description: Member added to scraper targets
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Add a member to a scraper target
+      tags:
+        - Scraper Targets
+  /api/v2/scrapers/{scraperTargetID}/members/{userID}:
+    delete:
+      operationId: DeleteScrapersIDMembersID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of member to remove.
+          in: path
+          name: userID
+          required: true
+          schema:
+            type: string
+        - description: The scraper target ID.
+          in: path
+          name: scraperTargetID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Member removed
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Remove a member from a scraper target
+      tags:
+        - Scraper Targets
+  /api/v2/scrapers/{scraperTargetID}/owners:
+    get:
+      operationId: GetScrapersIDOwners
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The scraper target ID.
+          in: path
+          name: scraperTargetID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ResourceOwners'
+          description: A list of scraper target owners
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List all owners of a scraper target
+      tags:
+        - Scraper Targets
+    post:
+      operationId: PostScrapersIDOwners
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The scraper target ID.
+          in: path
+          name: scraperTargetID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/AddResourceMemberRequestBody'
+        description: User to add as owner
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ResourceOwner'
+          description: Scraper target owner added
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Add an owner to a scraper target
+      tags:
+        - Scraper Targets
+  /api/v2/scrapers/{scraperTargetID}/owners/{userID}:
+    delete:
+      operationId: DeleteScrapersIDOwnersID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of owner to remove.
+          in: path
+          name: userID
+          required: true
+          schema:
+            type: string
+        - description: The scraper target ID.
+          in: path
+          name: scraperTargetID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Owner removed
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Remove an owner from a scraper target
+      tags:
+        - Scraper Targets
+  /api/v2/setup:
+    get:
+      description: >-
+        Returns `true` if no default user, organization, or bucket has been
+        created.
+      operationId: GetSetup
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/IsOnboarding'
+          description: allowed true or false
+      summary: Check if database has default user, org, bucket
+      tags:
+        - Setup
+    post:
+      description: Post an onboarding request to set up initial user, org and bucket.
+      operationId: PostSetup
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/OnboardingRequest'
+        description: Source to create
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/OnboardingResponse'
+          description: Created default user, bucket, org
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      summary: Set up initial user, org and bucket
+      tags:
+        - Setup
+  /api/v2/signin:
+    post:
+      description: >-
+        Authenticates ***Basic Auth*** credentials for a user. If successful,
+        creates a new UI session for the user.
+      operationId: PostSignin
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+      responses:
+        '204':
+          description: Success. User authenticated.
+        '401':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unauthorized access.
+        '403':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: User account is disabled.
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unsuccessful authentication.
+      security:
+        - BasicAuthentication: []
+      summary: Create a user session.
+      tags:
+        - Signin
+  /api/v2/signout:
+    post:
+      description: Expires the current UI session for the user.
+      operationId: PostSignout
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+      responses:
+        '204':
+          description: Session successfully expired
+        '401':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unauthorized access
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unsuccessful session expiry
+      summary: Expire the current UI session
+      tags:
+        - Signout
+  /api/v2/sources:
+    get:
+      operationId: GetSources
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The name of the organization.
+          in: query
+          name: org
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Sources'
+          description: A list of sources
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List all sources
+      tags:
+        - Sources
+    post:
+      operationId: PostSources
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/Source'
+        description: Source to create
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Source'
+          description: Created Source
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Create a source
+      tags:
+        - Sources
+  /api/v2/sources/{sourceID}:
+    delete:
+      operationId: DeleteSourcesID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The source ID.
+          in: path
+          name: sourceID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Delete has been accepted
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: View not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Delete a source
+      tags:
+        - Sources
+    get:
+      operationId: GetSourcesID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The source ID.
+          in: path
+          name: sourceID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Source'
+          description: A source
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Source not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Retrieve a source
+      tags:
+        - Sources
+    patch:
+      operationId: PatchSourcesID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The source ID.
+          in: path
+          name: sourceID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/Source'
+        description: Source update
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Source'
+          description: Created Source
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Source not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Update a Source
+      tags:
+        - Sources
+  /api/v2/sources/{sourceID}/buckets:
+    get:
+      operationId: GetSourcesIDBuckets
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The source ID.
+          in: path
+          name: sourceID
+          required: true
+          schema:
+            type: string
+        - description: The name of the organization.
+          in: query
+          name: org
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Buckets'
+          description: A source
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Source not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Get buckets in a source
+      tags:
+        - Sources
+        - Buckets
+  /api/v2/sources/{sourceID}/health:
+    get:
+      operationId: GetSourcesIDHealth
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The source ID.
+          in: path
+          name: sourceID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/HealthCheck'
+          description: The source is healthy
+        '503':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/HealthCheck'
+          description: The source is not healthy
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Get the health of a source
+      tags:
+        - Sources
+  /api/v2/stacks:
+    get:
+      operationId: ListStacks
+      parameters:
+        - description: The organization ID of the stacks
+          in: query
+          name: orgID
+          required: true
+          schema:
+            type: string
+        - description: A collection of names to filter the list by.
+          in: query
+          name: name
+          schema:
+            type: string
+        - description: A collection of stackIDs to filter the list by.
+          in: query
+          name: stackID
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                properties:
+                  stacks:
+                    items:
+                      $ref: '#/components/schemas/Stack'
+                    type: array
+                type: object
+          description: Success. Returns the list of stacks.
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List installed templates
+      tags:
+        - Templates
+    post:
+      operationId: CreateStack
+      requestBody:
+        content:
+          application/json:
+            schema:
+              properties:
+                description:
+                  type: string
+                name:
+                  type: string
+                orgID:
+                  type: string
+                urls:
+                  items:
+                    type: string
+                  type: array
+              title: PostStackRequest
+              type: object
+        description: The stack to create.
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Stack'
+          description: Success. Returns the newly created stack.
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Create a new stack
+      tags:
+        - Templates
+  /api/v2/stacks/{stack_id}:
+    delete:
+      operationId: DeleteStack
+      parameters:
+        - description: The identifier of the stack.
+          in: path
+          name: stack_id
+          required: true
+          schema:
+            type: string
+        - description: The identifier of the organization.
+          in: query
+          name: orgID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: The stack and its associated resources were deleted.
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Delete a stack and associated resources
+      tags:
+        - Templates
+    get:
+      operationId: ReadStack
+      parameters:
+        - description: The identifier of the stack.
+          in: path
+          name: stack_id
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Stack'
+          description: Returns the stack.
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Retrieve a stack
+      tags:
+        - Templates
+    patch:
+      operationId: UpdateStack
+      parameters:
+        - description: The identifier of the stack.
+          in: path
+          name: stack_id
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              properties:
+                additionalResources:
+                  items:
+                    properties:
+                      kind:
+                        type: string
+                      resourceID:
+                        type: string
+                      templateMetaName:
+                        type: string
+                    required:
+                      - kind
+                      - resourceID
+                    type: object
+                  type: array
+                description:
+                  nullable: true
+                  type: string
+                name:
+                  nullable: true
+                  type: string
+                templateURLs:
+                  items:
+                    type: string
+                  nullable: true
+                  type: array
+              title: PatchStackRequest
+              type: object
+        description: The stack to update.
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Stack'
+          description: Returns the updated stack.
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Update a stack
+      tags:
+        - Templates
+  /api/v2/stacks/{stack_id}/uninstall:
+    post:
+      operationId: UninstallStack
+      parameters:
+        - description: The identifier of the stack.
+          in: path
+          name: stack_id
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Stack'
+          description: Returns the uninstalled stack.
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Uninstall a stack
+      tags:
+        - Templates
+  /api/v2/tasks:
+    get:
+      operationId: GetTasks
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: Returns task with a specific name.
+          in: query
+          name: name
+          schema:
+            type: string
+        - description: Return tasks after a specified ID.
+          in: query
+          name: after
+          schema:
+            type: string
+        - description: Filter tasks to a specific user ID.
+          in: query
+          name: user
+          schema:
+            type: string
+        - description: Filter tasks to a specific organization name.
+          in: query
+          name: org
+          schema:
+            type: string
+        - description: Filter tasks to a specific organization ID.
+          in: query
+          name: orgID
+          schema:
+            type: string
+        - description: Filter tasks by a status--"inactive" or "active".
+          in: query
+          name: status
+          schema:
+            enum:
+              - active
+              - inactive
+            type: string
+        - description: The number of tasks to return
+          in: query
+          name: limit
+          schema:
+            default: 100
+            maximum: 500
+            minimum: 1
+            type: integer
+        - description: Type of task, unset by default.
+          in: query
+          name: type
+          required: false
+          schema:
+            default: ''
+            enum:
+              - basic
+              - system
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Tasks'
+          description: A list of tasks
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List all tasks
+      tags:
+        - Tasks
+    post:
+      operationId: PostTasks
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/TaskCreateRequest'
+        description: Task to create
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Task'
+          description: Task created
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Create a new task
+      tags:
+        - Tasks
+  /api/v2/tasks/{taskID}:
+    delete:
+      description: Deletes a task and all associated records
+      operationId: DeleteTasksID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the task to delete.
+          in: path
+          name: taskID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Task deleted
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Delete a task
+      tags:
+        - Tasks
+    get:
+      operationId: GetTasksID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The task ID.
+          in: path
+          name: taskID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Task'
+          description: Task details
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Retrieve a task
+      tags:
+        - Tasks
+    patch:
+      description: Update a task. This will cancel all queued runs.
+      operationId: PatchTasksID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The task ID.
+          in: path
+          name: taskID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/TaskUpdateRequest'
+        description: Task update to apply
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Task'
+          description: Task updated
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Update a task
+      tags:
+        - Tasks
+  /api/v2/tasks/{taskID}/labels:
+    get:
+      operationId: GetTasksIDLabels
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The task ID.
+          in: path
+          name: taskID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/LabelsResponse'
+          description: A list of all labels for a task
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List all labels for a task
+      tags:
+        - Tasks
+    post:
+      operationId: PostTasksIDLabels
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The task ID.
+          in: path
+          name: taskID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/LabelMapping'
+        description: Label to add
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/LabelResponse'
+          description: A list of all labels for a task
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Add a label to a task
+      tags:
+        - Tasks
+  /api/v2/tasks/{taskID}/labels/{labelID}:
+    delete:
+      operationId: DeleteTasksIDLabelsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The task ID.
+          in: path
+          name: taskID
+          required: true
+          schema:
+            type: string
+        - description: The label ID.
+          in: path
+          name: labelID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Delete has been accepted
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Task not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Delete a label from a task
+      tags:
+        - Tasks
+  /api/v2/tasks/{taskID}/logs:
+    get:
+      operationId: GetTasksIDLogs
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The task ID.
+          in: path
+          name: taskID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Logs'
+          description: All logs for a task
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Retrieve all logs for a task
+      tags:
+        - Tasks
+  /api/v2/tasks/{taskID}/members:
+    get:
+      operationId: GetTasksIDMembers
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The task ID.
+          in: path
+          name: taskID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ResourceMembers'
+          description: A list of users who have member privileges for a task
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List all task members
+      tags:
+        - Tasks
+    post:
+      operationId: PostTasksIDMembers
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The task ID.
+          in: path
+          name: taskID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/AddResourceMemberRequestBody'
+        description: User to add as member
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ResourceMember'
+          description: Added to task members
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Add a member to a task
+      tags:
+        - Tasks
+  /api/v2/tasks/{taskID}/members/{userID}:
+    delete:
+      operationId: DeleteTasksIDMembersID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the member to remove.
+          in: path
+          name: userID
+          required: true
+          schema:
+            type: string
+        - description: The task ID.
+          in: path
+          name: taskID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Member removed
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Remove a member from a task
+      tags:
+        - Tasks
+  /api/v2/tasks/{taskID}/owners:
+    get:
+      operationId: GetTasksIDOwners
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The task ID.
+          in: path
+          name: taskID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ResourceOwners'
+          description: A list of users who have owner privileges for a task
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List all owners of a task
+      tags:
+        - Tasks
+    post:
+      operationId: PostTasksIDOwners
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The task ID.
+          in: path
+          name: taskID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/AddResourceMemberRequestBody'
+        description: User to add as owner
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ResourceOwner'
+          description: Added to task owners
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Add an owner to a task
+      tags:
+        - Tasks
+  /api/v2/tasks/{taskID}/owners/{userID}:
+    delete:
+      operationId: DeleteTasksIDOwnersID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the owner to remove.
+          in: path
+          name: userID
+          required: true
+          schema:
+            type: string
+        - description: The task ID.
+          in: path
+          name: taskID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Owner removed
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Remove an owner from a task
+      tags:
+        - Tasks
+  /api/v2/tasks/{taskID}/runs:
+    get:
+      operationId: GetTasksIDRuns
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the task to get runs for.
+          in: path
+          name: taskID
+          required: true
+          schema:
+            type: string
+        - description: Returns runs after a specific ID.
+          in: query
+          name: after
+          schema:
+            type: string
+        - description: The number of runs to return
+          in: query
+          name: limit
+          schema:
+            default: 100
+            maximum: 500
+            minimum: 1
+            type: integer
+        - description: Filter runs to those scheduled after this time, RFC3339
+          in: query
+          name: afterTime
+          schema:
+            format: date-time
+            type: string
+        - description: Filter runs to those scheduled before this time, RFC3339
+          in: query
+          name: beforeTime
+          schema:
+            format: date-time
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Runs'
+          description: A list of task runs
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List runs for a task
+      tags:
+        - Tasks
+    post:
+      operationId: PostTasksIDRuns
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - in: path
+          name: taskID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/RunManually'
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Run'
+          description: Run scheduled to start
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Manually start a task run, overriding the current schedule
+      tags:
+        - Tasks
+  /api/v2/tasks/{taskID}/runs/{runID}:
+    delete:
+      operationId: DeleteTasksIDRunsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The task ID.
+          in: path
+          name: taskID
+          required: true
+          schema:
+            type: string
+        - description: The run ID.
+          in: path
+          name: runID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Delete has been accepted
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Cancel a running task
+      tags:
+        - Tasks
+    get:
+      operationId: GetTasksIDRunsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The task ID.
+          in: path
+          name: taskID
+          required: true
+          schema:
+            type: string
+        - description: The run ID.
+          in: path
+          name: runID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Run'
+          description: The run record
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Retrieve a single run for a task
+      tags:
+        - Tasks
+  /api/v2/tasks/{taskID}/runs/{runID}/logs:
+    get:
+      operationId: GetTasksIDRunsIDLogs
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: ID of task to get logs for.
+          in: path
+          name: taskID
+          required: true
+          schema:
+            type: string
+        - description: ID of run to get logs for.
+          in: path
+          name: runID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Logs'
+          description: All logs for a run
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Retrieve all logs for a run
+      tags:
+        - Tasks
+  /api/v2/tasks/{taskID}/runs/{runID}/retry:
+    post:
+      operationId: PostTasksIDRunsIDRetry
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The task ID.
+          in: path
+          name: taskID
+          required: true
+          schema:
+            type: string
+        - description: The run ID.
+          in: path
+          name: runID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json; charset=utf-8:
+            schema:
+              type: object
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Run'
+          description: Run that has been queued
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Retry a task run
+      tags:
+        - Tasks
+  /api/v2/telegraf/plugins:
+    get:
+      operationId: GetTelegrafPlugins
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The type of plugin desired.
+          in: query
+          name: type
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/TelegrafPlugins'
+          description: A list of Telegraf plugins.
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List all Telegraf plugins
+      tags:
+        - Telegraf Plugins
+  /api/v2/telegrafs:
+    get:
+      operationId: GetTelegrafs
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The organization ID the Telegraf config belongs to.
+          in: query
+          name: orgID
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Telegrafs'
+          description: A list of Telegraf configurations
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List all Telegraf configurations
+      tags:
+        - Telegrafs
+    post:
+      operationId: PostTelegrafs
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/TelegrafPluginRequest'
+        description: Telegraf configuration to create
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Telegraf'
+          description: Telegraf configuration created
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Create a Telegraf configuration
+      tags:
+        - Telegrafs
+  /api/v2/telegrafs/{telegrafID}:
+    delete:
+      operationId: DeleteTelegrafsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The Telegraf configuration ID.
+          in: path
+          name: telegrafID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Delete has been accepted
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Delete a Telegraf configuration
+      tags:
+        - Telegrafs
+    get:
+      operationId: GetTelegrafsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The Telegraf configuration ID.
+          in: path
+          name: telegrafID
+          required: true
+          schema:
+            type: string
+        - in: header
+          name: Accept
+          required: false
+          schema:
+            default: application/toml
+            enum:
+              - application/toml
+              - application/json
+              - application/octet-stream
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Telegraf'
+            application/octet-stream:
+              example: |-
+                [agent]
+                interval = "10s"
+              schema:
+                type: string
+            application/toml:
+              example: |-
+                [agent]
+                interval = "10s"
+              schema:
+                type: string
+          description: Telegraf configuration details
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Retrieve a Telegraf configuration
+      tags:
+        - Telegrafs
+    put:
+      operationId: PutTelegrafsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The Telegraf config ID.
+          in: path
+          name: telegrafID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/TelegrafPluginRequest'
+        description: Telegraf configuration update to apply
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Telegraf'
+          description: An updated Telegraf configurations
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Update a Telegraf configuration
+      tags:
+        - Telegrafs
+  /api/v2/telegrafs/{telegrafID}/labels:
+    get:
+      operationId: GetTelegrafsIDLabels
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The Telegraf config ID.
+          in: path
+          name: telegrafID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/LabelsResponse'
+          description: A list of all labels for a Telegraf config
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List all labels for a Telegraf config
+      tags:
+        - Telegrafs
+    post:
+      operationId: PostTelegrafsIDLabels
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The Telegraf config ID.
+          in: path
+          name: telegrafID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/LabelMapping'
+        description: Label to add
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/LabelResponse'
+          description: The label added to the Telegraf config
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Add a label to a Telegraf config
+      tags:
+        - Telegrafs
+  /api/v2/telegrafs/{telegrafID}/labels/{labelID}:
+    delete:
+      operationId: DeleteTelegrafsIDLabelsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The Telegraf config ID.
+          in: path
+          name: telegrafID
+          required: true
+          schema:
+            type: string
+        - description: The label ID.
+          in: path
+          name: labelID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Delete has been accepted
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Telegraf config not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Delete a label from a Telegraf config
+      tags:
+        - Telegrafs
+  /api/v2/telegrafs/{telegrafID}/members:
+    get:
+      operationId: GetTelegrafsIDMembers
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The Telegraf config ID.
+          in: path
+          name: telegrafID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ResourceMembers'
+          description: A list of Telegraf config members
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List all users with member privileges for a Telegraf config
+      tags:
+        - Telegrafs
+    post:
+      operationId: PostTelegrafsIDMembers
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The Telegraf config ID.
+          in: path
+          name: telegrafID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/AddResourceMemberRequestBody'
+        description: User to add as member
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ResourceMember'
+          description: Member added to Telegraf config
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Add a member to a Telegraf config
+      tags:
+        - Telegrafs
+  /api/v2/telegrafs/{telegrafID}/members/{userID}:
+    delete:
+      operationId: DeleteTelegrafsIDMembersID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the member to remove.
+          in: path
+          name: userID
+          required: true
+          schema:
+            type: string
+        - description: The Telegraf config ID.
+          in: path
+          name: telegrafID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Member removed
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Remove a member from a Telegraf config
+      tags:
+        - Telegrafs
+  /api/v2/telegrafs/{telegrafID}/owners:
+    get:
+      operationId: GetTelegrafsIDOwners
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The Telegraf configuration ID.
+          in: path
+          name: telegrafID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ResourceOwners'
+          description: Returns Telegraf configuration owners as a ResourceOwners list
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List all owners of a Telegraf configuration
+      tags:
+        - Telegrafs
+    post:
+      operationId: PostTelegrafsIDOwners
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The Telegraf configuration ID.
+          in: path
+          name: telegrafID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/AddResourceMemberRequestBody'
+        description: User to add as owner
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ResourceOwner'
+          description: >-
+            Telegraf configuration owner was added. Returns a ResourceOwner that
+            references the User.
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Add an owner to a Telegraf configuration
+      tags:
+        - Telegrafs
+  /api/v2/telegrafs/{telegrafID}/owners/{userID}:
+    delete:
+      operationId: DeleteTelegrafsIDOwnersID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the owner to remove.
+          in: path
+          name: userID
+          required: true
+          schema:
+            type: string
+        - description: The Telegraf config ID.
+          in: path
+          name: telegrafID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Owner removed
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Remove an owner from a Telegraf config
+      tags:
+        - Telegrafs
+  /api/v2/templates/apply:
+    post:
+      description: Applies or performs a dry-run of template in an organization.
+      operationId: ApplyTemplate
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/TemplateApply'
+          application/x-jsonnet:
+            schema:
+              $ref: '#/components/schemas/TemplateApply'
+          text/yml:
+            schema:
+              $ref: '#/components/schemas/TemplateApply'
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/TemplateSummary'
+          description: >
+            Success. The package dry-run succeeded. No new resources were
+            created. Returns a diff and summary of the dry-run. The diff and
+            summary won't contain IDs for resources that didn't exist at the
+            time of the dry-run.
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/TemplateSummary'
+          description: >
+            Success. The package applied successfully. Returns a diff and
+            summary of the run. The summary contains newly created resources.
+            The diff compares the initial state to the state after the package
+            applied. This corresponds to `"dryRun": true`.
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Apply or dry-run a template
+      tags:
+        - Templates
+  /api/v2/templates/export:
+    post:
+      operationId: ExportTemplate
+      requestBody:
+        content:
+          application/json:
+            schema:
+              oneOf:
+                - $ref: '#/components/schemas/TemplateExportByID'
+                - $ref: '#/components/schemas/TemplateExportByName'
+        description: Export resources as an InfluxDB template.
+        required: false
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Template'
+            application/x-yaml:
+              schema:
+                $ref: '#/components/schemas/Template'
+          description: >-
+            The template was created successfully. Returns the newly created
+            template.
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Export a new template
+      tags:
+        - Templates
+  /api/v2/users:
+    get:
+      operationId: GetUsers
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - $ref: '#/components/parameters/Offset'
+        - $ref: '#/components/parameters/Limit'
+        - $ref: '#/components/parameters/After'
+        - in: query
+          name: name
+          schema:
+            type: string
+        - in: query
+          name: id
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Users'
+          description: A list of users
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      summary: List all users
+      tags:
+        - Users
+    post:
+      operationId: PostUsers
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/User'
+        description: User to create
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/UserResponse'
+          description: User created
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      summary: Create a user
+      tags:
+        - Users
+  /api/v2/users/{userID}:
+    delete:
+      operationId: DeleteUsersID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the user to delete.
+          in: path
+          name: userID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: User deleted
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      summary: Delete a user
+      tags:
+        - Users
+    get:
+      operationId: GetUsersID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The user ID.
+          in: path
+          name: userID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/UserResponse'
+          description: User details
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      summary: Retrieve a user
+      tags:
+        - Users
+    patch:
+      operationId: PatchUsersID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The ID of the user to update.
+          in: path
+          name: userID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/User'
+        description: User update to apply
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/UserResponse'
+          description: User updated
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Unexpected error
+      summary: Update a user
+      tags:
+        - Users
+  /api/v2/users/{userID}/password:
+    post:
+      operationId: PostUsersIDPassword
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The user ID.
+          in: path
+          name: userID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/PasswordResetBody'
+        description: New password
+        required: true
+      responses:
+        '204':
+          description: Password successfully updated
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unsuccessful authentication
+      security:
+        - BasicAuthentication: []
+      summary: Update a password
+      tags:
+        - Users
+  /api/v2/variables:
+    get:
+      operationId: GetVariables
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The name of the organization.
+          in: query
+          name: org
+          schema:
+            type: string
+        - description: The organization ID.
+          in: query
+          name: orgID
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Variables'
+          description: A list of variables for an organization
+        '400':
+          $ref: '#/components/responses/ServerError'
+          description: Invalid request
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Internal server error
+      summary: List all variables
+      tags:
+        - Variables
+    post:
+      operationId: PostVariables
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/Variable'
+        description: Variable to create
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Variable'
+          description: Variable created
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Internal server error
+      summary: Create a variable
+      tags:
+        - Variables
+  /api/v2/variables/{variableID}:
+    delete:
+      operationId: DeleteVariablesID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The variable ID.
+          in: path
+          name: variableID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Variable deleted
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Internal server error
+      summary: Delete a variable
+      tags:
+        - Variables
+    get:
+      operationId: GetVariablesID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The variable ID.
+          in: path
+          name: variableID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Variable'
+          description: Variable found
+        '404':
+          $ref: '#/components/responses/ServerError'
+          description: Variable not found
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Internal server error
+      summary: Retrieve a variable
+      tags:
+        - Variables
+    patch:
+      operationId: PatchVariablesID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The variable ID.
+          in: path
+          name: variableID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/Variable'
+        description: Variable update to apply
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Variable'
+          description: Variable updated
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Internal server error
+      summary: Update a variable
+      tags:
+        - Variables
+    put:
+      operationId: PutVariablesID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The variable ID.
+          in: path
+          name: variableID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/Variable'
+        description: Variable to replace
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Variable'
+          description: Variable updated
+        default:
+          $ref: '#/components/responses/ServerError'
+          description: Internal server error
+      summary: Replace a variable
+      tags:
+        - Variables
+  /api/v2/variables/{variableID}/labels:
+    get:
+      operationId: GetVariablesIDLabels
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The variable ID.
+          in: path
+          name: variableID
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/LabelsResponse'
+          description: A list of all labels for a variable
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: List all labels for a variable
+      tags:
+        - Variables
+    post:
+      operationId: PostVariablesIDLabels
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The variable ID.
+          in: path
+          name: variableID
+          required: true
+          schema:
+            type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/LabelMapping'
+        description: Label to add
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/LabelResponse'
+          description: The newly added label
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Add a label to a variable
+      tags:
+        - Variables
+  /api/v2/variables/{variableID}/labels/{labelID}:
+    delete:
+      operationId: DeleteVariablesIDLabelsID
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: The variable ID.
+          in: path
+          name: variableID
+          required: true
+          schema:
+            type: string
+        - description: The label ID to delete.
+          in: path
+          name: labelID
+          required: true
+          schema:
+            type: string
+      responses:
+        '204':
+          description: Delete has been accepted
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Variable not found
+        default:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Unexpected error
+      summary: Delete a label from a variable
+      tags:
+        - Variables
+  /api/v2/write:
+    post:
+      description: >
+        Writes data to a bucket.
+
+
+        Use this endpoint to send data in [line
+        protocol](https://docs.influxdata.com/influxdb/v2.2/reference/syntax/line-protocol/)
+        format to InfluxDB.
+
+        InfluxDB parses and validates line protocol in the request body,
+
+        responds with success or failure, and then handles the write
+        asynchronously.
+
+
+        #### Required permissions
+
+
+        - `write-buckets` or `write-bucket BUCKET_ID`
+
+
+        `BUCKET_ID` is the ID of the destination bucket.
+
+
+        #### Rate limits (with InfluxDB Cloud)
+
+
+        `write` rate limits apply.
+
+        For more information, see [limits and adjustable
+        quotas](https://docs.influxdata.com/influxdb/cloud/account-management/limits/).
+
+
+        #### Related guides
+
+
+        - [Write data with the InfluxDB
+        API](https://docs.influxdata.com/influxdb/v2.2/write-data/developer-tools/api).
+
+        - [Optimize writes to
+        InfluxDB](https://docs.influxdata.com/influxdb/v2.2/write-data/best-practices/optimize-writes/).
+
+        - [Troubleshoot issues writing
+        data](https://docs.influxdata.com/influxdb/v2.2/write-data/troubleshoot/)
+      operationId: PostWrite
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - description: |
+            The compression applied to the line protocol in the request payload.
+            To send a GZIP payload, pass `Content-Encoding: gzip` header.
+          in: header
+          name: Content-Encoding
+          schema:
+            default: identity
+            description: >
+              Content coding.
+
+              Use `gzip` for compressed data or `identity` for unmodified,
+              uncompressed data.
+            enum:
+              - gzip
+              - identity
+            type: string
+        - description: >
+            The format of the data in the request body.
+
+            To send a line protocol payload, pass `Content-Type: text/plain;
+            charset=utf-8`.
+          in: header
+          name: Content-Type
+          schema:
+            default: text/plain; charset=utf-8
+            description: >
+              `text/plain` is the content type for line protocol. `UTF-8` is the
+              default character set.
+            enum:
+              - text/plain
+              - text/plain; charset=utf-8
+            type: string
+        - description: |
+            The size of the entity-body, in bytes, sent to InfluxDB.
+            If the length is greater than the `max body` configuration option,
+            the server responds with status code `413`.
+          in: header
+          name: Content-Length
+          schema:
+            description: The length in decimal number of octets.
+            type: integer
+        - description: |
+            The content type that the client can understand.
+            Writes only return a response body if they fail--for example,
+            due to a formatting problem or quota limit.
+
+            #### InfluxDB Cloud
+
+              - Returns only `application/json` for format and limit errors.
+              - Returns only `text/html` for some quota limit errors.
+
+            #### InfluxDB OSS
+
+              - Returns only `application/json` for format and limit errors.
+
+            #### Related guides
+              - [Troubleshoot issues writing data](https://docs.influxdata.com/influxdb/v2.2/write-data/troubleshoot/).
+          in: header
+          name: Accept
+          schema:
+            default: application/json
+            description: Error content type.
+            enum:
+              - application/json
+            type: string
+        - description: >
+            The destination organization for writes.
+
+            The database writes all points in the batch to this organization.
+
+            If you provide both `orgID` and `org` parameters, `org` takes
+            precedence.
+          in: query
+          name: org
+          required: true
+          schema:
+            description: The organization name or ID.
+            type: string
+        - description: |
+            The ID of the destination organization for writes.
+            If both `orgID` and `org` are specified, `org` takes precedence.
+          in: query
+          name: orgID
+          schema:
+            type: string
+        - description: The destination bucket for writes.
+          in: query
+          name: bucket
+          required: true
+          schema:
+            description: InfluxDB writes all points in the batch to this bucket.
+            type: string
+        - description: The precision for unix timestamps in the line protocol batch.
+          in: query
+          name: precision
+          schema:
+            $ref: '#/components/schemas/WritePrecision'
+      requestBody:
+        content:
+          text/plain:
+            examples:
+              plain-utf8:
+                value: >
+                  airSensors,sensor_id=TLM0201
+                  temperature=73.97038159354763,humidity=35.23103248356096,co=0.48445310567793615
+                  1630424257000000000
+
+                  airSensors,sensor_id=TLM0202
+                  temperature=75.30007505999716,humidity=35.651929918691714,co=0.5141876544505826
+                  1630424257000000000
+            schema:
+              format: byte
+              type: string
+        description: >
+          Data in line protocol format.
+
+
+          To send compressed data, do the following:
+
+            1. Use [GZIP](https://www.gzip.org/) to compress the line protocol data.
+            2. In your request, send the compressed data and the
+               `Content-Encoding: gzip` header.
+
+          #### Related guides
+
+
+          - [Best practices for optimizing
+          writes](https://docs.influxdata.com/influxdb/v2.2/write-data/best-practices/optimize-writes/).
+        required: true
+      responses:
+        '204':
+          description: >
+            Success. InfluxDB validated the request and the data format and
+
+            accepted the data for writing to the bucket.
+
+            Because data is written to InfluxDB asynchronously, data may not yet
+            be written to a bucket.
+
+
+            #### Related guides
+
+
+            - [How to check for write
+            errors](https://docs.influxdata.com/influxdb/v2.2/write-data/troubleshoot/).
+        '400':
+          content:
+            application/json:
+              examples:
+                measurementSchemaFieldTypeConflict:
+                  summary: >-
+                    InfluxDB Cloud field type conflict thrown by an explicit
+                    bucket schema
+                  value:
+                    code: invalid
+                    message: >-
+                      partial write error (2 written): unable to parse
+                      'air_sensor,service=S1,sensor=L1
+                      temperature="90.5",humidity=70.0 1632850122': schema:
+                      field type for field "temperature" not permitted by
+                      schema; got String but expected Float
+              schema:
+                $ref: '#/components/schemas/LineProtocolError'
+          description: |
+            Bad request. The line protocol data in the request is malformed.
+            The response body contains the first malformed line in the data.
+            InfluxDB rejected the batch and did not write any data.
+        '401':
+          content:
+            application/json:
+              examples:
+                tokenNotAuthorized:
+                  summary: >-
+                    Token is not authorized to access the organization or
+                    resource
+                  value:
+                    code: unauthorized
+                    message: unauthorized access
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: |
+            Unauthorized. The error may indicate one of the following:
+              * The `Authorization: Token` header is missing or malformed.
+              * The API token value is missing from the header.
+              * The token does not have sufficient permissions to write to this organization and bucket.
+        '404':
+          content:
+            application/json:
+              examples:
+                resource-not-found:
+                  summary: Not found error
+                  value:
+                    code: not found
+                    message: bucket "air_sensor" not found
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: >-
+            Not found. A requested resource was not found. The response body
+            contains the requested resource type, e.g. `organization name` or
+            `bucket`, and name.
+        '413':
+          content:
+            application/json:
+              examples:
+                dataExceedsSizeLimitOSS:
+                  summary: InfluxDB OSS response
+                  value: >
+                    {"code":"request too large","message":"unable to read data:
+                    points batch is too large"}
+              schema:
+                $ref: '#/components/schemas/LineProtocolLengthError'
+            text/html:
+              examples:
+                dataExceedsSizeLimit:
+                  summary: InfluxDB Cloud response
+                  value: |
+                    <html>
+                      <head><title>413 Request Entity Too Large</title></head>
+                      <body>
+                        <center><h1>413 Request Entity Too Large</h1></center>
+                        <hr>
+                        <center>nginx</center>
+                      </body>
+                    </html>
+              schema:
+                type: string
+          description: |
+            The request payload is too large.
+            InfluxDB rejected the batch and did not write any data.
+
+            #### InfluxDB Cloud:
+
+             - Returns this error if the payload exceeds the 50MB size limit.
+             - Returns `Content-Type: text/html` for this error.
+
+            #### InfluxDB OSS:
+
+             - Returns this error only if the [Go (golang) `ioutil.ReadAll()`](https://pkg.go.dev/io/ioutil#ReadAll) function raises an error.
+             - Returns `Content-Type: application/json` for this error.
+        '429':
+          description: |
+            Too many requests.
+
+            #### InfluxDB Cloud
+
+              - Returns this error if a **read** or **write** request exceeds your
+                plan's [adjustable service quotas](https://docs.influxdata.com/influxdb/cloud/account-management/limits/#adjustable-service-quotas)
+                or if a **delete** request exceeds the maximum
+                [global limit](https://docs.influxdata.com/influxdb/cloud/account-management/limits/#global-limits).
+              - Returns `Retry-After` header that describes when to try the write again.
+
+            #### InfluxDB OSS
+
+              - Doesn't return this error.
+          headers:
+            Retry-After:
+              description: >-
+                Non-negative decimal integer indicating seconds to wait before
+                retrying the request.
+              schema:
+                format: int32
+                type: integer
+        '500':
+          content:
+            application/json:
+              examples:
+                internalError:
+                  summary: Internal error example
+                  value:
+                    code: internal error
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Internal server error.
+        '503':
+          description: |
+            Service unavailable.
+
+            #### InfluxDB Cloud
+
+              - Returns this error if series cardinality exceeds your plan's
+                [adjustable service quotas](https://docs.influxdata.com/influxdb/cloud/account-management/limits/#adjustable-service-quotas).
+                See [how to resolve high series cardinality](https://docs.influxdata.com/influxdb/v2.2/write-data/best-practices/resolve-high-cardinality/).
+
+            #### InfluxDB OSS
+
+              - Returns this error if
+                the server is temporarily unavailable to accept writes.
+              - Returns `Retry-After` header that describes when to try the write again.
+          headers:
+            Retry-After:
+              description: >-
+                Non-negative decimal integer indicating seconds to wait before
+                retrying the request.
+              schema:
+                format: int32
+                type: integer
+        default:
+          $ref: '#/components/responses/ServerError'
+      summary: Write data
+      tags:
+        - Write
+security:
+  - TokenAuthentication: []
+servers:
+  - url: /
+tags:
+  - description: >
+      Use one of the following schemes to authenticate to the InfluxDB API:
+
+
+      - [Token authentication](#section/Authentication/TokenAuthentication)
+
+      - [Basic authentication](#section/Authentication/BasicAuthentication)
+
+      - [Querystring
+      authentication](#section/Authentication/QuerystringAuthentication)
+
+      <!-- ReDoc-Inject: <security-definitions> -->
+    name: Authentication
+    x-traitTag: true
+  - description: >
+      Create and manage API tokens.
+
+      An **authorization** associates a list of permissions to an
+
+      **organization** and provides a token for API access.
+
+      Optionally, you can restrict an authorization and its token to a specific
+      user.
+
+
+      ### Related guides
+
+        - [Authorize API requests](/influxdb/v2.2/api-guide/api_intro/#authentication).
+        - [Manage API tokens](/influxdb/v2.2/security/tokens/).
+        - [Assign a token to a specific user](/influxdb/v2.2/security/tokens/create-token/).
+    name: Authorizations
+  - name: Backup
+  - name: Buckets
+  - name: Cells
+  - name: Checks
+  - name: Config
+  - name: Dashboards
+  - name: DBRPs
+  - description: >
+      Generates profiling and trace reports.
+
+
+      Use routes under `/debug/pprof` to analyze the Go runtime of InfluxDB.
+
+      These endpoints generate [Go runtime
+      profiles](https://pkg.go.dev/runtime/pprof)
+
+      and **trace** reports.
+
+      **Profiles** are collections of stack traces that show call sequences
+
+      leading to instances of a particular event, such as allocation.
+
+
+      For more information about **pprof profile** and **trace** reports,
+
+      see the following resources:
+        - [Google pprof tool](https://github.com/google/pprof)
+        - [Golang diagnostics](https://go.dev/doc/diagnostics)
+    name: Debug
+  - name: Delete
+  - description: >
+      InfluxDB API endpoints use standard HTTP request and response headers.
+
+
+      **Note**: Not all operations support all headers.
+
+
+      ### Request headers
+
+
+      | Header                   | Value type            |
+      Description                                |
+
+      |:------------------------ |:---------------------
+      |:-------------------------------------------|
+
+      | `Accept`                 | string                | The content type that
+      the client can understand. |
+
+      | `Authorization`          | string                | The authorization
+      scheme and credential. |
+
+      | `Content-Encoding`       | string                | The compression
+      applied to the line protocol in the request payload. |
+
+      | `Content-Length`         | integer               | The size of the
+      entity-body, in bytes, sent to the database. |
+
+      | `Content-Type`           | string                | The format of the
+      data in the request body. |
+    name: Headers
+    x-traitTag: true
+  - name: Health
+  - name: Labels
+  - name: Legacy Authorizations
+  - name: Metrics
+  - name: NotificationEndpoints
+  - name: NotificationRules
+  - name: Organizations
+  - name: Ping
+  - description: |
+      Retrieve data, analyze queries, and get query suggestions.
+    name: Query
+  - description: >
+      See the [**API Quick Start**](/influxdb/v2.2/api-guide/api_intro/)
+
+      to get up and running authenticating with tokens, writing to buckets, and
+      querying data.
+
+
+      [**InfluxDB API client
+      libraries**](/influxdb/v2.2/api-guide/client-libraries/)
+
+      are available for popular languages and ready to import into your
+      application.
+    name: Quick start
+    x-traitTag: true
+  - name: Ready
+  - name: RemoteConnections
+  - name: Replications
+  - name: Resources
+  - description: >
+      InfluxDB API endpoints use standard HTTP status codes for success and
+      failure responses.
+
+      The response body may include additional details.
+
+      For details about a specific operation's response,
+
+      see **Responses** and **Response Samples** for that operation.
+
+
+      API operations may return the following HTTP status codes:
+
+
+      | &nbsp;Code&nbsp; | Status                   | Description      |
+
+      |:-----------:|:------------------------ |:--------------------- |
+
+      | `200`       | Success                  |                       |
+
+      | `204`       | No content               | For a `POST` request, `204`
+      indicates that InfluxDB accepted the request and request data is valid.
+      Asynchronous operations, such as `write`, might not have completed yet. |
+
+      | `400`       | Bad request              | `Authorization` header is
+      missing or malformed or the API token does not have permission for the
+      operation. |
+
+      | `401`       | Unauthorized             | May indicate one of the
+      following: <li>`Authorization: Token` header is missing or
+      malformed</li><li>API token value is missing from the header</li><li>API
+      token does not have permission. For more information about token types and
+      permissions, see [Manage API tokens](/influxdb/v2.1/security/tokens/)</li>
+      |
+
+      | `404`       | Not found                | Requested resource was not
+      found. `message` in the response body provides details about the requested
+      resource. |
+
+      | `413`       | Request entity too large | Request payload exceeds the
+      size limit. |
+
+      | `422`       | Unprocessible entity     | Request data is invalid. `code`
+      and `message` in the response body provide details about the problem. |
+
+      | `429`       | Too many requests        | API token is temporarily over
+      the request quota. The `Retry-After` header describes when to try the
+      request again. |
+
+      | `500`       | Internal server error    |                       |
+
+      | `503`       | Service unavailable      | Server is temporarily
+      unavailable to process the request. The `Retry-After` header describes
+      when to try the request again. |
+    name: Response codes
+    x-traitTag: true
+  - name: Restore
+  - name: Routes
+  - name: Rules
+  - name: Scraper Targets
+  - name: Secrets
+  - name: Setup
+  - name: Signin
+  - name: Signout
+  - name: Sources
+  - name: Tasks
+  - name: Telegraf Plugins
+  - name: Telegrafs
+  - name: Templates
+  - name: Users
+  - name: Variables
+  - name: Views
+  - description: |
+      Write time series data to buckets.
+    name: Write
+x-tagGroups:
+  - name: Overview
+    tags:
+      - Quick start
+      - Authentication
+      - Headers
+      - Response codes
+  - name: Data I/O endpoints
+    tags:
+      - Write
+      - Query
+      - Tasks
+  - name: Resource endpoints
+    tags:
+      - Buckets
+      - Dashboards
+      - Tasks
+      - Resources
+  - name: Security and access endpoints
+    tags:
+      - Authorizations
+      - Organizations
+      - Users
+  - name: System information endpoints
+    tags:
+      - Config
+      - Debug
+      - Health
+      - Metrics
+      - Ping
+      - Ready
+      - Routes
+  - name: All endpoints
+    tags:
+      - Authorizations
+      - Backup
+      - Buckets
+      - Cells
+      - Checks
+      - Config
+      - Dashboards
+      - DBRPs
+      - Debug
+      - Delete
+      - Health
+      - Labels
+      - Legacy Authorizations
+      - Metrics
+      - NotificationEndpoints
+      - NotificationRules
+      - Organizations
+      - Ping
+      - Query
+      - Ready
+      - RemoteConnections
+      - Replications
+      - Resources
+      - Restore
+      - Routes
+      - Rules
+      - Scraper Targets
+      - Secrets
+      - Setup
+      - Signin
+      - Signout
+      - Sources
+      - Tasks
+      - Telegraf Plugins
+      - Telegrafs
+      - Templates
+      - Users
+      - Variables
+      - Views
+      - Write
diff --git a/api-docs/v2.2/swaggerV1Compat.yml b/api-docs/v2.2/swaggerV1Compat.yml
new file mode 100644
index 000000000..3b8926c1a
--- /dev/null
+++ b/api-docs/v2.2/swaggerV1Compat.yml
@@ -0,0 +1,502 @@
+openapi: 3.0.0
+info:
+  title: InfluxDB OSS v1 compatibility API documentation
+  version: 0.1.0
+  description: |
+    The InfluxDB 1.x compatibility `/write` and `/query` endpoints work with
+    InfluxDB 1.x client libraries and third-party integrations like Grafana
+    and others.
+
+
+    If you want to use the latest InfluxDB `/api/v2` API instead,
+    see the [InfluxDB v2 API documentation](/influxdb/cloud/api/).
+servers:
+  - url: /
+paths:
+  /write:
+    post:
+      operationId: PostWriteV1
+      tags:
+        - Write
+      summary: Write time series data into InfluxDB in a V1-compatible format
+      requestBody:
+        description: Line protocol body
+        required: true
+        content:
+          text/plain:
+            schema:
+              type: string
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - $ref: '#/components/parameters/AuthUserV1'
+        - $ref: '#/components/parameters/AuthPassV1'
+        - in: query
+          name: db
+          schema:
+            type: string
+          required: true
+          description: >-
+            Bucket to write to. If none exists, InfluxDB creates a bucket with a
+            default 3-day retention policy.
+        - in: query
+          name: rp
+          schema:
+            type: string
+          description: Retention policy name.
+        - in: query
+          name: precision
+          schema:
+            type: string
+          description: Write precision.
+        - in: header
+          name: Content-Encoding
+          description: >-
+            When present, its value indicates to the database that compression
+            is applied to the line protocol body.
+          schema:
+            type: string
+            description: >-
+              Specifies that the line protocol in the body is encoded with gzip
+              or not encoded with identity.
+            default: identity
+            enum:
+              - gzip
+              - identity
+      responses:
+        '204':
+          description: >-
+            Write data is correctly formatted and accepted for writing to the
+            bucket.
+        '400':
+          description: >-
+            Line protocol poorly formed and no points were written.  Response
+            can be used to determine the first malformed line in the body
+            line-protocol. All data in body was rejected and not written.
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/LineProtocolError'
+        '401':
+          description: >-
+            Token does not have sufficient permissions to write to this
+            organization and bucket or the organization and bucket do not exist.
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+        '403':
+          description: No token was sent and they are required.
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+        '413':
+          description: >-
+            Write has been rejected because the payload is too large. Error
+            message returns max size supported. All data in body was rejected
+            and not written.
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/LineProtocolLengthError'
+        '429':
+          description: >-
+            Token is temporarily over quota. The Retry-After header describes
+            when to try the write again.
+          headers:
+            Retry-After:
+              description: >-
+                A non-negative decimal integer indicating the seconds to delay
+                after the response is received.
+              schema:
+                type: integer
+                format: int32
+        '503':
+          description: >-
+            Server is temporarily unavailable to accept writes.  The Retry-After
+            header describes when to try the write again.
+          headers:
+            Retry-After:
+              description: >-
+                A non-negative decimal integer indicating the seconds to delay
+                after the response is received.
+              schema:
+                type: integer
+                format: int32
+        default:
+          description: Internal server error
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+  /query:
+    post:
+      operationId: PostQueryV1
+      tags:
+        - Query
+      summary: Query InfluxDB in a V1 compatible format
+      requestBody:
+        description: InfluxQL query to execute.
+        content:
+          text/plain:
+            schema:
+              type: string
+      parameters:
+        - $ref: '#/components/parameters/TraceSpan'
+        - $ref: '#/components/parameters/AuthUserV1'
+        - $ref: '#/components/parameters/AuthPassV1'
+        - in: header
+          name: Accept
+          schema:
+            type: string
+            description: >-
+              Specifies how query results should be encoded in the response.
+              **Note:** With `application/csv`, query results include epoch
+              timestamps instead of RFC3339 timestamps.
+            default: application/json
+            enum:
+              - application/json
+              - application/csv
+              - text/csv
+              - application/x-msgpack
+        - in: header
+          name: Accept-Encoding
+          description: >-
+            The Accept-Encoding request HTTP header advertises which content
+            encoding, usually a compression algorithm, the client is able to
+            understand.
+          schema:
+            type: string
+            description: >-
+              Specifies that the query response in the body should be encoded
+              with gzip or not encoded with identity.
+            default: identity
+            enum:
+              - gzip
+              - identity
+        - in: header
+          name: Content-Type
+          schema:
+            type: string
+            enum:
+              - application/vnd.influxql
+        - in: query
+          name: db
+          schema:
+            type: string
+          required: true
+          description: Bucket to query.
+        - in: query
+          name: rp
+          schema:
+            type: string
+          description: Retention policy name.
+        - in: query
+          name: q
+          description: Defines the influxql query to run.
+          schema:
+            type: string
+      responses:
+        '200':
+          description: Query results
+          headers:
+            Content-Encoding:
+              description: >-
+                The Content-Encoding entity header is used to compress the
+                media-type.  When present, its value indicates which encodings
+                were applied to the entity-body
+              schema:
+                type: string
+                description: >-
+                  Specifies that the response in the body is encoded with gzip
+                  or not encoded with identity.
+                default: identity
+                enum:
+                  - gzip
+                  - identity
+            Trace-Id:
+              description: >-
+                The Trace-Id header reports the request's trace ID, if one was
+                generated.
+              schema:
+                type: string
+                description: Specifies the request's trace ID.
+          content:
+            application/csv:
+              schema:
+                $ref: '#/components/schemas/InfluxQLCSVResponse'
+            text/csv:
+              schema:
+                $ref: '#/components/schemas/InfluxQLCSVResponse'
+            application/json:
+              schema:
+                $ref: '#/components/schemas/InfluxQLResponse'
+            application/x-msgpack:
+              schema:
+                type: string
+                format: binary
+        '429':
+          description: >-
+            Token is temporarily over quota. The Retry-After header describes
+            when to try the read again.
+          headers:
+            Retry-After:
+              description: >-
+                A non-negative decimal integer indicating the seconds to delay
+                after the response is received.
+              schema:
+                type: integer
+                format: int32
+        default:
+          description: Error processing query
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+components:
+  parameters:
+    TraceSpan:
+      in: header
+      name: Zap-Trace-Span
+      description: OpenTracing span context
+      example:
+        trace_id: '1'
+        span_id: '1'
+        baggage:
+          key: value
+      required: false
+      schema:
+        type: string
+    AuthUserV1:
+      in: query
+      name: u
+      required: false
+      schema:
+        type: string
+      description: Username.
+    AuthPassV1:
+      in: query
+      name: p
+      required: false
+      schema:
+        type: string
+      description: User token.
+  schemas:
+    InfluxQLResponse:
+      properties:
+        results:
+          type: array
+          items:
+            type: object
+            properties:
+              statement_id:
+                type: integer
+              series:
+                type: array
+                items:
+                  type: object
+                  properties:
+                    name:
+                      type: string
+                    columns:
+                      type: array
+                      items:
+                        type: integer
+                    values:
+                      type: array
+                      items:
+                        type: array
+                        items: {}
+    InfluxQLCSVResponse:
+      type: string
+      example: >
+        name,tags,time,test_field,test_tag
+        test_measurement,,1603740794286107366,1,tag_value
+        test_measurement,,1603740870053205649,2,tag_value
+        test_measurement,,1603741221085428881,3,tag_value
+    Error:
+      properties:
+        code:
+          description: Code is the machine-readable error code.
+          readOnly: true
+          type: string
+          enum:
+            - internal error
+            - not found
+            - conflict
+            - invalid
+            - unprocessable entity
+            - empty value
+            - unavailable
+            - forbidden
+            - too many requests
+            - unauthorized
+            - method not allowed
+        message:
+          readOnly: true
+          description: Message is a human-readable message.
+          type: string
+      required:
+        - code
+        - message
+    LineProtocolError:
+      properties:
+        code:
+          description: Code is the machine-readable error code.
+          readOnly: true
+          type: string
+          enum:
+            - internal error
+            - not found
+            - conflict
+            - invalid
+            - empty value
+            - unavailable
+        message:
+          readOnly: true
+          description: Message is a human-readable message.
+          type: string
+        op:
+          readOnly: true
+          description: >-
+            Op describes the logical code operation during error. Useful for
+            debugging.
+          type: string
+        err:
+          readOnly: true
+          description: >-
+            Err is a stack of errors that occurred during processing of the
+            request. Useful for debugging.
+          type: string
+        line:
+          readOnly: true
+          description: First line within sent body containing malformed data
+          type: integer
+          format: int32
+      required:
+        - code
+        - message
+        - op
+        - err
+    LineProtocolLengthError:
+      properties:
+        code:
+          description: Code is the machine-readable error code.
+          readOnly: true
+          type: string
+          enum:
+            - invalid
+        message:
+          readOnly: true
+          description: Message is a human-readable message.
+          type: string
+        maxLength:
+          readOnly: true
+          description: Max length in bytes for a body of line-protocol.
+          type: integer
+          format: int32
+      required:
+        - code
+        - message
+        - maxLength
+  securitySchemes:
+    TokenAuthentication:
+      type: apiKey
+      name: Authorization
+      in: header
+      description: >
+        Use the [Token
+        authentication](#section/Authentication/TokenAuthentication)
+
+        scheme to authenticate to the InfluxDB API.
+
+
+
+        In your API requests, send an `Authorization` header.
+
+        For the header value, provide the word `Token` followed by a space and
+        an InfluxDB API token.
+
+        The word `Token` is case-sensitive.
+
+
+
+        ### Syntax
+
+
+        `Authorization: Token YOUR_INFLUX_TOKEN`
+
+
+
+        For examples and more information, see the following:
+          - [`/authorizations`](#tag/Authorizations) endpoint.
+          - [Authorize API requests](/influxdb/cloud/api-guide/api_intro/#authentication).
+          - [Manage API tokens](/influxdb/cloud/security/tokens/).
+    BasicAuthentication:
+      type: http
+      scheme: basic
+      description: >
+        Use the HTTP [Basic
+        authentication](#section/Authentication/BasicAuthentication)
+
+        scheme with clients that support the InfluxDB 1.x convention of username
+        and password (that don't support the `Authorization: Token` scheme):
+
+
+
+        For examples and more information, see how to [authenticate with a
+        username and password](/influxdb/cloud/reference/api/influxdb-1x/).
+    QuerystringAuthentication:
+      type: apiKey
+      in: query
+      name: u=&p=
+      description: >
+        Use the [Querystring
+        authentication](#section/Authentication/QuerystringAuthentication)
+
+        scheme with InfluxDB 1.x API parameters to provide credentials through
+        the query string.
+
+
+
+        For examples and more information, see how to [authenticate with a
+        username and password](/influxdb/cloud/reference/api/influxdb-1x/).
+security:
+  - TokenAuthentication: []
+  - BasicAuthentication: []
+  - QuerystringAuthentication: []
+tags:
+  - name: Authentication
+    description: >
+      The InfluxDB 1.x API requires authentication for all requests.
+
+      InfluxDB Cloud uses InfluxDB API tokens to authenticate requests.
+
+
+
+      For more information, see the following:
+
+      - [Token authentication](#section/Authentication/TokenAuthentication)
+
+      - [Basic authentication](#section/Authentication/BasicAuthentication)
+
+      - [Querystring
+      authentication](#section/Authentication/QuerystringAuthentication)
+
+
+      <!-- ReDoc-Inject: <security-definitions> -->
+    x-traitTag: true
+  - name: Query
+  - name: Write
+x-tagGroups:
+  - name: Overview
+    tags:
+      - Authentication
+  - name: Data I/O endpoints
+    tags:
+      - Write
+      - Query
+  - name: All endpoints
+    tags:
+      - Query
+      - Write
diff --git a/assets/js/content-interactions.js b/assets/js/content-interactions.js
index 22e50b7d3..04662df32 100644
--- a/assets/js/content-interactions.js
+++ b/assets/js/content-interactions.js
@@ -17,7 +17,8 @@ var elementWhiteList = [
   ".truncate-toggle",
   ".children-links a",
   ".list-links a",
-  "a.url-trigger"
+  "a.url-trigger",
+  "a.fullscreen-close"
 ]
 
 function scrollToAnchor(target) {
@@ -28,6 +29,15 @@ function scrollToAnchor(target) {
     }, 400, 'swing', function () {
       window.location.hash = target;
     });
+
+    // Unique accordion functionality
+    // If the target is an accordion element, open the accordion after scrolling
+    if ($target.hasClass('expand')) {
+      if ($(target + ' .expand-label .expand-toggle').hasClass('open')) {}
+      else {
+        $(target + '> .expand-label').trigger('click');
+      };
+    };
   }
 }
 
@@ -85,7 +95,7 @@ tabbedContent('.tabs-wrapper', '.tabs p a', '.tab-content');
 
 // Retrieve the user's programming language (client library) preference.
 function getApiLibPreference() {
-  return Cookies.get('influx-docs-api-lib');
+  return Cookies.get('influx-docs-api-lib') || '';
 }
 
 function getTabQueryParam() {
@@ -139,13 +149,36 @@ $(".truncate-toggle").click(function(e) {
   $(this).closest('.truncate').toggleClass('closed');
 })
 
-////////////////////////////// Expand Accordians ///////////////////////////////
+////////////////////////////// Expand Accordions ///////////////////////////////
 
 $('.expand-label').click(function() {
   $(this).children('.expand-toggle').toggleClass('open')
   $(this).next('.expand-content').slideToggle(200)
 })
 
+// Expand accordions on load based on URL anchor
+function openAccordionByHash() {
+  var anchor = window.location.hash;
+
+  function expandElement() {
+    if ($(anchor).parents('.expand').length > 0) {
+      return $(anchor).closest('.expand').children('.expand-label');
+    } else if ($(anchor).hasClass('expand')){
+      return $(anchor).children('.expand-label');
+    }
+  };
+
+  if (expandElement() != null) {
+    if (expandElement().children('.expand-toggle').hasClass('open')) {}
+    else {
+      expandElement().children('.expand-toggle').trigger('click');
+    };
+  };
+};
+
+// Open accordions by hash on page load.
+openAccordionByHash()
+
 ////////////////////////// Inject tooltips on load //////////////////////////////
 
 $('.tooltip').each( function(){
diff --git a/assets/js/fullscreen-code.js b/assets/js/fullscreen-code.js
new file mode 100644
index 000000000..7d15dd6f2
--- /dev/null
+++ b/assets/js/fullscreen-code.js
@@ -0,0 +1,48 @@
+var codeBlockSelector = ".article--content pre";
+var codeBlocks = $(codeBlockSelector);
+
+// Check if codeblock content requires scrolling (overflow)
+function hasOverflow(element) {
+  if (element.offsetHeight < element.scrollHeight || element.offsetWidth < element.scrollWidth) {
+    return true
+  } else {
+    return false
+  }
+}
+
+// Wrap codeblocks that overflow with a new 'codeblock' div
+$(codeBlocks).each(function() {
+  if (hasOverflow( $(this)[0] )) {
+    $(this).wrap("<div class='codeblock'></div>");
+  } else {}
+});
+
+// Append a clickable fullscreen toggle button to all codeblock divs
+$('.codeblock').append("<a class='fullscreen-toggle'><span class='cf-icon expand-new'></span></a>");
+
+/*
+On click, open the fullscreen code modal and append a clone of the selected codeblock.
+Disable scrolling on the body.
+Disable user selection on everything but the fullscreen codeblock.
+*/
+$('.fullscreen-toggle').click(function() {
+  var code = $(this).prev('pre').clone();
+  
+  $('#fullscreen-code-placeholder').replaceWith(code[0]);
+  $('body').css('overflow', 'hidden');
+  $('body > div:not(.fullscreen-code)').css('user-select', 'none');
+  $('.fullscreen-code').fadeIn();
+})
+
+/*
+On click, close the fullscreen code block.
+Reenable scrolling on the body.
+Reenable user selection on everything.
+Close the modal and replace the code block with the placeholder element.
+*/
+$('.fullscreen-close').click(function() {
+  $('body').css('overflow', 'auto');
+  $('body > div:not(.fullscreen-code)').css('user-select', '');
+  $('.fullscreen-code').fadeOut();
+  $('.fullscreen-code pre').replaceWith('<div id="fullscreen-code-placeholder"></div>')
+});
diff --git a/assets/js/home-interactions.js b/assets/js/home-interactions.js
new file mode 100644
index 000000000..a90df14cd
--- /dev/null
+++ b/assets/js/home-interactions.js
@@ -0,0 +1,22 @@
+$('.exp-btn').click(function() {
+  var targetBtnElement = $(this).parent()
+  $('.exp-btn > p', targetBtnElement).fadeOut(100);
+  setTimeout(function() {
+    $('.exp-btn-links', targetBtnElement).fadeIn(200)
+    $('.exp-btn', targetBtnElement).addClass('open');
+    $('.close-btn', targetBtnElement).fadeIn(200);
+  }, 100);
+})
+
+$('.close-btn').click(function() {
+  var targetBtnElement = $(this).parent().parent()
+  $('.exp-btn-links', targetBtnElement).fadeOut(100)
+  $('.exp-btn', targetBtnElement).removeClass('open');
+  $(this).fadeOut(100);
+  setTimeout(function() {
+    $('p', targetBtnElement).fadeIn(100);
+  }, 100);
+})
+
+/////////////////////////////// EXPANDING BUTTONS //////////////////////////////
+
diff --git a/assets/js/influxdb-url.js b/assets/js/influxdb-url.js
index cc09b030c..81be1af65 100644
--- a/assets/js/influxdb-url.js
+++ b/assets/js/influxdb-url.js
@@ -139,21 +139,21 @@ function updateUrls(prevUrls, newUrls) {
     oss: {}
   }
 
-    Object.keys(prevUrls).forEach(function(k) {
-      try {
-        prevUrlsParsed[k] = new URL(prevUrls[k])
-      } catch {
-        prevUrlsParsed[k] = { host: prevUrls[k] }
-      }
-    })
+  Object.keys(prevUrls).forEach(function(k) {
+    try {
+      prevUrlsParsed[k] = new URL(prevUrls[k])
+    } catch {
+      prevUrlsParsed[k] = { host: prevUrls[k] }
+    }
+  })
 
-    Object.keys(newUrls).forEach(function(k) {
-      try {
-        newUrlsParsed[k] = new URL(newUrls[k])
-      } catch {
-        newUrlsParsed[k] = { host: newUrls[k] }
-      }
-    })
+  Object.keys(newUrls).forEach(function(k) {
+    try {
+      newUrlsParsed[k] = new URL(newUrls[k])
+    } catch {
+      newUrlsParsed[k] = { host: newUrls[k] }
+    }
+  })
 
   /**
     * Match and replace <prev> host with <new> host
@@ -175,37 +175,43 @@ function updateUrls(prevUrls, newUrls) {
 
   replacements.forEach(function (o) {
     if (o.replace.origin != o.with.origin) {
+      var fuzzyOrigin = new RegExp(o.replace.origin + "(:[0-9]+)?", "g");
       $(elementSelector).each(function() {
         $(this).html(
-          $(this).html().replace(RegExp(o.replace.origin, "g"), function(match){
-            return o.with.origin || match;
+          $(this).html().replace(fuzzyOrigin, function(m){
+            return o.with.origin || m;
           })
         );
       })
     }
   });
+
+  function replaceWholename(startStr, endStr, replacement) {
+    var startsWithSeparator = new RegExp('[/.]');
+    var endsWithSeparator = new RegExp('[-.:]');
+    if(!startsWithSeparator.test(startStr) && !endsWithSeparator.test(endStr)) {
+      var newHost = startStr + replacement + endStr
+      return startStr + replacement + endStr;
+    }
+  }
+
   replacements
   .map(function(o) {
      return {replace: o.replace.host, with: o.with.host}
    })
   .forEach(function (o) {
-     if (o.replace != o.with) {
+    if (o.replace != o.with) {
+        var fuzzyHost = new RegExp("(.?)" + o.replace + "(.?)", "g");
        $(elementSelector).each(function() {
-         /**
-	  * Hostname pattern
-	  * 1. Lookbehind (?<!) matches if o.replace is not preceded by :[/.].
-	  * 2. Match 1 or no slashes following the hostname.
-	  * 3. Negative lookahead (?!) matches if not followed by word char, dash, or dot.
-	  */
-         var hostnameOnly = new RegExp("(?<![/.])" + o.replace + "\/?(?![/w/-/.])", "g")
-         $(this).html(
-           $(this).html().replace(hostnameOnly, function(match) {
-             return o.with.host || o.with;
-           })
-         );
-       })
-     }
-   })
+        $(this).html(
+          $(this).html().replace(fuzzyHost, function(m, p1, p2) {
+            var r = replaceWholename(p1, p2, o.with) || m;
+            return r
+          })
+        );
+      })
+    }
+  });
 }
 
 // Append the URL selector button to each codeblock with an InfluxDB Cloud or OSS URL
@@ -276,6 +282,29 @@ $("#modal-close, .modal-overlay, .url-trigger").click(function(e) {
   toggleModal()
 })
 
+
+// Add checked to fake-radio if cluster is selected on page load
+if ($("ul.clusters label input").is(":checked")) {
+  var group = $("ul.clusters label input:checked").parent().parent().parent().siblings();
+  $(".fake-radio", group).addClass("checked");
+};
+
+// Select first cluster when region is clicked
+$("p.region").click(function () {
+  if (!$(".fake-radio", this).hasClass("checked")) {
+    $(".fake-radio", this).addClass("checked");
+    $("+ ul.clusters li:first label", this).trigger("click");
+  };
+});
+
+// Remove checked class from fake-radio when another region is selected
+$(".region-group").click(function () {
+  if (!$(".fake-radio", this).hasClass("checked")) {
+    $(".fake-radio", !this).removeClass("checked");
+    $(".fake-radio", this).addClass("checked");
+  }
+})
+
 // Update URLs and URL preference when selected/clicked in the modal
 $('input[name="influxdb-cloud-url"]').change(function() {
   var newUrl = $(this).val()
@@ -325,17 +354,25 @@ showPreference()
 
 // Validate custom URLs
 function validateUrl(url) {
-  var validProtocol = /^http(s?)/
-  var invalidDomain =/[A-Z\s\!\@\#\$\%\^\&\*\(\)\_\+\=\[\]\{\}\\\|\;\'\"\,\<\>\/\?]/
-  var protocol = url.match(/http(s?):\/\//) ? url.match(/http(s?):\/\//)[0] : "";
-  var domain = url.replace(protocol, "")
-
-  if (validProtocol.test(protocol) == false) {
-    return {valid: false, error: "Invalid protocol, use http[s]"}
-  } else if (domain.length == 0 || invalidDomain.test(domain) == true) {
-    return {valid: false, error: "Invalid domain"}
-  } else {
+  try {
+    new URL(url);
     return {valid: true, error: ""}
+  } catch(e) {
+    var validProtocol = /^http(s?)/
+    var protocol = url.match(/http(s?):\/\//) ? url.match(/http(s?):\/\//)[0] : "";
+    var domain = url.replace(protocol, "")
+    /** validDomain = (Named host | IPv6 host | IPvFuture host)(:Port)? **/
+    var validDomain = new RegExp(`([a-z0-9\-._~%]+`
+                               + `|\[[a-f0-9:.]+\]`
+                               + `|\[v[a-f0-9][a-z0-9\-._~%!$&'()*+,;=:]+\])`
+                               + `(:[0-9]+)?`);
+    if (validProtocol.test(protocol) == false) {
+      return {valid: false, error: "Invalid protocol, use http[s]"}
+    } else if (validDomain.test(domain) == false) {
+      return {valid: false, error: "Invalid domain"}
+    } else if (e) {
+      return {valid: false, error: "Invalid URL"}
+    }
   }
 }
 
@@ -396,17 +433,28 @@ $('#custom-url-field').blur(function() {
   applyCustomUrl()
 })
 
+/** Delay execution of a function `fn` for a number of milliseconds `ms`
+  * e.g., delay a validation handler to avoid annoying the user.
+  */
+function delay(fn, ms) {
+  let timer = 0
+  return function(...args) {
+    clearTimeout(timer)
+    timer = setTimeout(fn.bind(this, ...args), ms || 0)
+  }
+}
+
+function handleUrlValidation() {
+  let url = $('#custom-url-field').val()
+  let urlValidation = validateUrl(url)
+  if (urlValidation.valid) {
+    hideValidationMessage()
+  } else {
+    showValidationMessage(urlValidation)
+  }
+}
 // When in erred state, revalidate custom URL on keyup
-$(document).on("keyup", ".error #custom-url-field", function() {
-    console.log("keyed up")
-    let url = $('#custom-url-field').val()
-    let urlValidation = validateUrl(url)
-    if (urlValidation.valid) {
-      hideValidationMessage()
-    } else {
-      showValidationMessage(urlValidation)
-    }
-})
+$(document).on("keyup", "#custom-url-field", delay(handleUrlValidation, 500));
 
 // Populate the custom InfluxDB URL field on page load
 if ( Cookies.get('influxdb_custom_url') != undefined ) {
diff --git a/assets/js/search-interactions.js b/assets/js/search-interactions.js
index 4628111bd..4f8fdd8ac 100644
--- a/assets/js/search-interactions.js
+++ b/assets/js/search-interactions.js
@@ -1,10 +1,10 @@
 // Fade content wrapper when focusing on search input
 $('#algolia-search-input').focus(function() {
-  $('.content-wrapper, .group-wrapper').fadeTo(300, .35);
+  $('.content-wrapper').fadeTo(300, .35);
 })
 
 // Hide search dropdown when leaving search input
 $('#algolia-search-input').blur(function() {
-  $('.content-wrapper, .group-wrapper').fadeTo(200, 1);
+  $('.content-wrapper').fadeTo(200, 1);
   $('.ds-dropdown-menu').hide();
 })
diff --git a/assets/styles/layouts/_algolia-search-overrides.scss b/assets/styles/layouts/_algolia-search-overrides.scss
index 1603da86c..e9e7e7dfa 100644
--- a/assets/styles/layouts/_algolia-search-overrides.scss
+++ b/assets/styles/layouts/_algolia-search-overrides.scss
@@ -1,6 +1,11 @@
 .algolia-autocomplete {
   width: 100%;
 
+  /* Search input field */
+  #algolia-search-input {
+    background: $sidebar-search-bg !important;
+  }
+
   /* Main dropdown wrapper */
   .ds-dropdown-menu {
     width: 74vw;
diff --git a/assets/styles/layouts/_api-overrides.scss b/assets/styles/layouts/_api-overrides.scss
index ac99fc5d4..a1e9ed530 100644
--- a/assets/styles/layouts/_api-overrides.scss
+++ b/assets/styles/layouts/_api-overrides.scss
@@ -1,5 +1,5 @@
 @import "tools/color-palette";
-@import "tools/icomoon-v2";
+@import "tools/fonts";
 
 // Fonts
 $rubik: 'Rubik', sans-serif;
@@ -103,7 +103,7 @@ $bold: 700;
 }
 
 #redoc {
-  h1,h2,h3,h4,h5,h6 {
+  h1,h2,h3 {
     font-weight: $medium !important;
   }
 }
diff --git a/assets/styles/layouts/_article.scss b/assets/styles/layouts/_article.scss
index a6ff04ce6..cab6b380e 100644
--- a/assets/styles/layouts/_article.scss
+++ b/assets/styles/layouts/_article.scss
@@ -5,7 +5,9 @@
 }
 
 .article--content{
-  max-width: 820px;
+  max-width: 850px;
+  font-size: 1.1rem;
+
   h1,h2,h3,h4,h5,h6 {
     color: $article-heading;
     a {
@@ -24,24 +26,24 @@
   }
   h1 {
     font-weight: normal;
-    font-size: 2.65rem;
+    font-size: 2.75rem;
     margin: .4em 0 .2em;
   }
   h2 {
-    font-size: 2rem;
+    font-size: 2.1rem;
     margin: -.25rem 0 .5rem;
     padding-top: 1.75rem;
     font-weight: $medium;
     color: $article-heading-alt;
   }
   h3 {
-    font-size: 1.65rem;
+    font-size: 1.75rem;
     font-weight: $medium;
     margin: -1rem 0 .5rem;
     padding-top: 1.75rem;
   }
   h4 {
-    font-size: 1.25rem;
+    font-size: 1.35rem;
     font-style: italic;
     font-weight: $medium;
     margin: -1.25rem 0 .5rem;
@@ -49,12 +51,12 @@
     color: $article-heading-alt;
   }
   h5 {
-    font-size: 1rem;
+    font-size: 1.1rem;
     margin: -1.25rem 0 .25rem;
     padding-top: 1.75rem;
   }
   h6 {
-    font-size: 1rem;
+    font-size: 1.1rem;
     font-style: italic;
     margin: -1.25rem 0 .25rem;
     padding-top: 1.75rem;
@@ -62,7 +64,7 @@
 
   p,li {
     color: $article-text;
-    line-height: 1.7rem;
+    line-height: 1.8rem;
   }
 
   p {
@@ -187,8 +189,8 @@
   .nowrap { white-space: nowrap }
   .all-caps {
     text-transform: uppercase;
-    font-size: .95rem;
-    letter-spacing: .07em;
+    font-size: 1.05rem;
+    letter-spacing: .1em;
     font-weight: $medium !important;
   }
 
diff --git a/assets/styles/layouts/_fullscreen-code.scss b/assets/styles/layouts/_fullscreen-code.scss
new file mode 100644
index 000000000..23dab82db
--- /dev/null
+++ b/assets/styles/layouts/_fullscreen-code.scss
@@ -0,0 +1,40 @@
+////////////////////////// Fullscreen codeblock styles /////////////////////////
+.fullscreen-code {
+  display: none;
+  z-index: 1000;
+  position: fixed;
+  top: 0;
+  left: 0;
+  height: 100vh;
+  width: 100vw;
+  padding: 2rem;
+  background: $article-code-bg;
+  overflow: scroll !important;
+
+  .fullscreen-close {
+    position: fixed;
+    padding: .1rem;
+    right: .75rem;
+    top: .5rem;
+    display: block;
+    color: $article-code;
+    font-size: 2rem;
+    text-decoration: none;
+    background: $article-code-bg;
+    border-radius: $radius;
+
+    span {
+      opacity: 0.5;
+      transition: opacity 0.2s;
+    }    
+
+    &:hover span {opacity: 1};
+  }
+
+  pre {
+    display: block;
+    line-height: 1.75rem;
+
+    @import "article/code-api-methods";
+  }
+}
diff --git a/assets/styles/layouts/_global.scss b/assets/styles/layouts/_global.scss
index 786a5adb9..f7c642605 100644
--- a/assets/styles/layouts/_global.scss
+++ b/assets/styles/layouts/_global.scss
@@ -1,21 +1,11 @@
-$rubik: 'Rubik', sans-serif;
-$code: 'IBM Plex Mono', monospace;;
-
-// Font weights
-$medium: 500;
-$bold: 700;
-
-
 html {
   height: 100%;
 }
 
 body {
   min-height: 100%;
-  font-family: 'Rubik', sans-serif;
+  font-family: $proxima;
   background: $body-bg;
-  -webkit-font-smoothing: antialiased;
-  -moz-osx-font-smoothing: grayscale;
 }
 
 * {
diff --git a/assets/styles/layouts/_homepage.scss b/assets/styles/layouts/_homepage.scss
index 10e73ed14..09f76efa9 100644
--- a/assets/styles/layouts/_homepage.scss
+++ b/assets/styles/layouts/_homepage.scss
@@ -1,120 +1,67 @@
+////////////////////////////// HOMEPAGE VARIABLES //////////////////////////////
+
+$home-body-width: 1300px;
+
 //////////////////////////////// HOMEPAGE STYLES ///////////////////////////////
 
+body.home {
+  background-image: url('/img/hero-bg-light-1-diamond.png');
+  background-size: 65%;
+  background-repeat: no-repeat;
+}
+
 .home {
-  display: flex;
-  flex-direction: column;
-  align-items: flex-start;
+  color: $article-bold;
 
-  .section {
-    display: flex;
+  .section{
     width: 100%;
-    padding: 0rem 3rem;
-    flex-grow: 1;
-
-    .row{
-      flex-direction: row;
-    }
-
-    .half { width: 50%; }
-    .third { width: 33.33%; }
-    .quarter { width: 25%; }
-    .two-thirds { width: 66.67%; }
-    .three-quarters { width: 75%; }
-  }
-
-  ///////////////////////////// HERO SECTION STYLES ////////////////////////////
-
-  .hero {
+    margin: 0 auto;
+    padding: 2rem 2rem 0;
+    max-width: $home-body-width;
+    display: block;
     position: relative;
-    padding-top: 3.5rem;
-    padding-bottom: 4.5rem;
-    @include gradient($grad-WarpSpeed)
-    color: $g20-white;
-    z-index: 0;
-    // overflow: hidden;
-
-    h2 {
-      margin: 1.25rem 0 .5rem;
-      font-weight: 300;
-      font-size: 3rem;
-    }
-    p {
-      font-size: 1.1rem;
-      line-height: 1.85rem;
-    }
-
-    #hero-img {
-      position: absolute;
-      max-width: 50%;
-      max-height: 135%;
-      bottom: -25%;
-      right: 0;
-    }
-
-    .actions {
-      display: flex;
-      margin: 1.25rem 0 .75rem 0;
-    }
-
-    a.btn {
-      position: relative;
-      display: inline-block;
-      flex: 1 0;
-      margin: 0 .5rem .5rem 0;
-      padding: 1.25rem 2.25rem;
-      color: $article-btn-text !important;
-      border-radius: $radius;
-      font-weight: $medium;
-      font-size: 1.1rem;
-      text-decoration: none;
-      text-align: center;
-      z-index: 1;
-      @include gradient($home-btn-gradient);
-
-      &:after {
-        content: "";
-        position: absolute;
-        display: block;
-        top: 0;
-        right: 0;
-        width: 100%;
-        height: 100%;
-        border-radius: $radius;
-        @include gradient($home-btn-gradient-hover, 270deg);
-        opacity: 0;
-        transition: opacity .2s;
-        z-index: -1;
-      }
-
-      &:hover {
-        cursor: pointer;
-
-        &:after {
-          opacity: 1;
-        }
-      }
-    }
   }
 
   //////////////////////////// SEARCH SECTION STYLES ///////////////////////////
   .search {
-    padding-top: 2rem;
-    padding-bottom: 2.25rem;
-
     .sidebar--search {
-      max-width: 55%;
       font-size: 1.1rem;
 
       input {
-        padding: .75em 2.35rem .75rem 1rem
+        padding: .75em 2.35rem .75rem 1rem;
+        border-radius: 6px;
+        position: relative;
+        box-shadow: none;
+
+        &::placeholder  {color: rgba($sidebar-search-text, .65);}
       }
 
       &:after {
         font-size: 2rem;
-        top: .35rem;
+        top: .45rem;
         right: .45rem;
       }
+
+      .algolia-autocomplete {  
+        position: relative;      
+
+        &:after {
+          content: "";
+          position: absolute;
+          display: block;
+          border-radius: 6px;
+          top: 0;
+          left: 0;
+          box-shadow: 2px 2px 6px $sidebar-search-shadow;
+          height: 100%;
+          width: 100%;
+          mix-blend-mode: multiply;
+          z-index: -1;
+        }
+      }
+
       .algolia-autocomplete.algolia-autocomplete-left, .algolia-autocomplete.algolia-autocomplete-right {
+
         .ds-dropdown-menu {
           top: auto !important;
           left: 0 !important;
@@ -122,7 +69,7 @@
 
           &:after {
             content: "";
-            box-shadow: 2px 2px 10px $sidebar-search-shadow;
+            box-shadow: 2px 2px 6px $sidebar-search-shadow;
             height: 100%;
             width: 100%;
             mix-blend-mode: multiply;
@@ -132,283 +79,547 @@
     }
   }
 
-  /////////////////////////////// PRODUCT CARDS ////////////////////////////////
+  ///////////////////////////////// SPAN STYLES ////////////////////////////////
 
-  .group-wrapper {
-    display: flex;
-    flex-grow: 1;
-    width: 100%;
-    border-radius: $radius;
-    background-color: $sidebar-search-bg;
-    box-shadow: 2px 2px 10px $sidebar-search-shadow;
-    overflow: hidden;
-    color: $article-text;
-
-    h2 {
-      margin-top: .5rem;
-      font-weight: $medium;
-      color: $article-heading-alt;
-      a {color: inherit; &:hover{color: inherit;}}
-    }
-    p {
-      line-height: 1.45rem;
-      max-width: 700px;
-    }
-    a {
-      color: $article-link;
-      text-decoration: none;
-      font-weight: $medium;
-      &:hover{ color: $article-link-hover; }
-    }
+  span {
+    &.magenta {color: $br-new-magenta;}
+    &.orange {color: $r-dreamsicle;}
+    &.blue {color: $b-pool;}
   }
 
-  .card {
-    display: flex;
-    flex-direction: column;
-    justify-content: space-between;
-    padding: 1.25rem 1.5rem .75rem;
-    flex: 1 0;
+  ///////////////////////////// EXPANDABLE BUTTONS /////////////////////////////
 
-    .card-content p { margin-bottom: 0; }
+  .exp-btn-wrapper {
+    position: relative;
+    display: block;
 
-    span.version {
-      font-size: 1.15rem;
-      opacity: .65;
-    }
-  }
-
-  #flux, #resources {
-    padding-bottom: 2.5rem;
-    .card .card-content {
-      h2 {margin-bottom: .5rem;}
-      p {margin: 0 0 1rem;}
-    }
-    .card.cta-btns {
-      flex-direction: row;
-      margin-bottom: .75rem;
-      justify-content: flex-end;
+    .exp-btn {
+      background: $br-dark-blue;
+      border-radius: 6px;
+      color: $br-teal;
+      padding: 1.5rem 2rem;
+      font-weight: $medium;
       align-items: center;
-      a.btn {
-        position: relative;
-        display: inline-block;
+      min-width: 340px;
+      min-height: 70px;
+      cursor: pointer;
+      transition: color .2s, background .2s, padding .2s;
+
+      &:hover, &.open {
+        background: $br-teal;
+        color: $br-dark-blue;
+      }
+
+      p {
+        margin: 0 !important;
         text-align: center;
-        margin: .5rem .5rem .5rem 0;
-        padding: .75rem 1.5rem;
-        color: $article-btn-text !important;
-        border-radius: $radius;
-        font-size: .95rem;
-        z-index: 1;
-        @include gradient($article-btn-gradient);
+      }
+      & > * {width: 100%;}
 
-        &:after {
-          content: "";
-          position: absolute;
-          display: block;
-          top: 0;
-          right: 0;
-          width: 100%;
-          height: 100%;
-          border-radius: $radius;
-          @include gradient($article-btn-gradient-hover);
-          opacity: 0;
-          transition: opacity .2s;
-          z-index: -1;
+      &.open {
+        padding: 0;        
+        li a {padding: 1rem 2rem;}
+      }
+    }
+
+    .exp-btn-links { 
+      border-radius: 6px;
+      color: $br-dark-blue;
+      margin: 0;
+      padding: 0;
+      list-style: none;
+      width: 100%;
+      height: 100%;
+      display: none;
+      
+      li {
+        background: $br-teal;
+  
+        &:first-child {
+          border-radius: 6px 6px 0 0;
+          border-bottom: 1px solid rgba($br-dark-blue, .5);
         }
+        &:last-child {
+          border-radius: 0 0 6px 6px;
+          border-bottom: none;
+        }
+        a {
+          display: block;
+          padding: 0rem 2rem;
+          color: $br-dark-blue;
+          text-decoration: none;
+          text-align: center;
+          transition: padding .2s;
+        }
+      }
+    }
+  
+    .close-btn {
+      position: absolute;
+      top: 38%;
+      right: -32px;
+      color: rgba($br-teal, .6);
+      font-size: 1.5rem;
+      display: none;
+      cursor: pointer;
+      transition: color .2s;
+  
+      &:hover {
+        opacity: 1;
+        color: $br-teal;
+      }
+    }
+  }
 
-        &:hover {
-          cursor: pointer;
+  //////////////////////////////// PRODUCT CARDS ///////////////////////////////
 
+  .product-cards {
+    display: flex;
+    flex-direction: row;
+
+    .card {
+      padding: 3rem;
+      background: $sidebar-search-bg;
+      border-radius: 30px;
+      box-shadow: 1px 1px 7px $sidebar-search-shadow;
+      flex: 1 1 0;
+      display: flex;
+      flex-direction: column;
+
+      &:first-child {margin-right: 1rem}
+      &:last-child {margin-left: 1rem}
+
+      h3 {
+        margin: 0 0 1.5rem;
+        line-height: 1.1em;
+        font-size: 2.75rem;
+      }
+
+      p {
+        margin-bottom: 2rem;
+      };
+
+      .card-links {
+        margin-top: auto;
+        
+        a {
+          position: relative;
+          display: block;
+          color: $article-text;
+          font-weight: $medium;
+          text-decoration: none;
+          margin-bottom: .3rem;
+          
           &:after {
-            opacity: 1;
+            content: "";
+            display: block;
+            margin-top: .15rem;
+            border-top: 2px solid $br-new-magenta;
+            width: 0;
+            transition: width .2s;
+          }
+
+          &:hover{
+            color: $br-new-magenta;
+            &:after {width: 30%}
           }
         }
       }
     }
   }
 
-  #tick-cards {
+  ///////////////////////// GENERAL BLUE SECTION STYLES ////////////////////////
+
+  .section.blue {
+
+    h2, h3, h4 {
+      color: $br-teal;
+    }
+
+    .padding-wrapper {
+      width: 100%;
+      max-width: $home-body-width;
+      color: $g20-white;
+      background: $br-dark-blue;
+      background-size: cover;
+      border-radius: 30px;
+    }
+
+    &.flush-left .padding-wrapper {
+      padding: 2rem;
+      background-image: url('/svgs/home-bg-circle-right.svg')}
+    &.flush-right .padding-wrapper {
+      padding: 2rem;
+      background-image: url('/svgs/home-bg-circle-left.svg');
+    }
+  }
+
+  ////////////////////////////// INFLUXDB SECTION //////////////////////////////
+
+  #influxdb {
+    
+    padding-top: .5rem;
     display: flex;
-    flex-wrap: wrap;
-    position: relative;
-    color: $g20-white;
-    @include gradient($home-tick-bg-gradient, 45deg)
 
-    h2 { color: $article-heading-alt; }
+    .actions {
+      display: flex;
+      justify-content: center;
+      align-items: center;
+      max-width: 50%;
+      padding: 0 3rem 3rem;
+      flex: 1 1 0;
+    }
 
-    a {
-      display: inline-block;
-      position: relative;
-      &:after{
-        content: "";
-        margin-top: .15rem;
-        width: 0;
-        display: block;
-        height: 2px;
-        @include gradient($grad-whiteFade)
-        transition: width .2s;
-      }
-      &:hover{
-        &:after { width: 100%; }
+    h2 {
+      margin: 0;
+      font-size: 3.5rem;
+      line-height: 1.1em;
+      & + p {
+        font-size: 1.2rem;
+        margin: .5rem 0 2rem;
       }
     }
 
-    .card {
+    h3 {
+      margin: 0;
+      color: $g20-white;
+      font-size: 2.25rem;
+
+      & + p {margin: .5rem 0;}
+    }
+
+    .hero-img {
+      background-image: url('/img/wind-turbine.jpg');
+      background-size: cover;
+      margin: -.5rem .75rem 0 1rem;
+      z-index: -1;
+      min-height: 600px;
+      border-radius: 0 0 30px 30px;
+      flex: 1 1 0;
+    }
+  }
+
+  #influxdb-btn {  
+    .exp-btn {
+      @include gradient($grad-burningDusk, 270deg);
+      color: $g20-white;
       position: relative;
       z-index: 1;
-      color: $article-text;
-      transition: color .2s;
 
       &:after {
         content: "";
-        position: absolute;
-        display: block;
-        bottom: 0;
+        top: 0;
         left: 0;
+        position: absolute;
         width: 100%;
         height: 100%;
-        opacity: 0;
+        @include gradient($grad-coolDusk);
+        border-radius: 6px;
         z-index: -1;
-        transition: opacity .4s;
+        opacity: 0;
+        transition: opacity .2s;
       }
 
-      &.telegraf:after {@include gradient($telegraf-home-card-gradient);}
-      &.influxdb:after {@include gradient($default-home-card-gradient);}
-      &.chronograf:after {@include gradient($chronograf-home-card-gradient);}
-      &.kapacitor:after {@include gradient($kapacitor-home-card-gradient);}
-
-      &:hover {
-        color: $g20-white;
-        h2, a {color: $g20-white;}
-        &:after { opacity: 1; }
+      &:hover, &.open {
+        &:after {opacity: 1;}  
       }
 
+      &.open {
+        padding: 0;        
+        li a {padding: 1rem 2rem;}
+      }
+    }
 
+    .exp-btn-links { 
+      color: $g20-white;      
+      li {
+        @include gradient($grad-coolDusk);
+  
+        &:first-child {
+          border-bottom: 1px solid rgba($body-bg, .5);
+          a:after {border-radius: 6px 6px 0 0;}
+        }
+
+        &:last-child a:after {border-radius: 0 0 6px 6px;}
+
+        a {
+          color: $g20-white;
+          position: relative;
+          z-index: 1;
+          
+          &:after {
+            content: "";
+            top: 0;
+            left: 0;
+            position: absolute;
+            width: 100%;
+            height: 100%;
+            @include gradient($grad-burningDusk, 270deg);
+            border-radius: 6px;
+            z-index: -1;
+            opacity: 0;
+            transition: opacity .2s;
+          }
+
+          &:hover:after {opacity: 1}
+        }
+      }
+    }
+  
+    .close-btn {
+      color: rgba($br-new-magenta, .6);  
+      &:hover {color: $br-new-magenta;}
     }
   }
 
-  #enterprise {
-    padding-top: 2.5rem;
-    padding-bottom: 2.5rem;
-  }
+  ///////////////////////////////// API SECTION ////////////////////////////////
 
-  //////////////////////////// HOMEPAGE MEDIA QUERIES ////////////////////////////
+  #api-guides {
+    .padding-wrapper {
+      display: flex;
+      justify-content: space-between;
+      align-items: center;
+      padding: 3.5rem;
 
-  @include media(large) {
-    overflow-x: hidden;
-    .hero #hero-img{
-      max-height: 130%;
-      max-width: 70%;
-      right: -20%;
-      bottom: -30%;
+      .text {margin-right: 2rem;}
+
+      h3 {
+        margin: 0;
+        font-size: 1.8rem;
+      }
+
+      p {
+        margin: .5rem 0;
+        line-height: 1.5rem;
+      }
     }
   }
 
-  @media (max-width: 1020px) {
-    #tick-stack #tick-cards .card { width: 50%; flex: none;}
-    .section {
-      .quarter { width: 33.33%; }
-      .three-quarters { width: 66.64%; }
+  ///////////////////////////////// LEARN ITEMS ////////////////////////////////
+
+  #learn-more {
+    margin-bottom: 2rem;
+
+    h4 {
+      font-size: 1.8rem;
+      margin: 1rem 0 2rem;
     }
-    #flux .card.flux-btns {
+
+    .learn-items {
+      display: flex;
+      flex-direction: row;
+      justify-content: flex-start;
+
+      .item {
+        max-width: 25%;
+        flex: 1 1 0;
+        display: flex;
+        flex-direction: column;
+        margin: 0 .75rem;
+
+        .icon {
+          svg {max-height: 60px; max-width: 60px}
+          .c1 {fill: $home-icon-c1;}
+          .c2 {fill: $home-icon-c2;}
+          .magenta {fill: $br-new-magenta;}
+        }
+
+        h5 {
+          font-size: 1.4rem;
+          margin: 1rem 0 0;
+        }
+
+        p {
+          margin: .5rem 0 1.5rem;
+          line-height: 1.7rem;
+        }
+        a {
+          position: relative;
+          color: $br-new-magenta;
+          font-weight: $medium;
+          text-decoration: none;
+          
+          &:after {
+            content: "";
+            display: block;
+            margin-top: .25rem;
+            border-top: 2px solid $br-new-magenta;
+            width: 0;
+            transition: width .2s;
+          }
+
+          &:hover:after {width: 30%}
+        }
+
+        & > *:last-child {margin-top: auto}
+      }
+    }
+  }
+
+  ////////////////////////////// TICK STACK STYLES /////////////////////////////
+
+  #tick {
+    padding-bottom: 0;
+
+    .padding-wrapper {
+      display: flex;
+      flex-direction: row;
+      align-items: center;
+      padding: 2rem 3rem;
+
+      h4 {
+        margin: 0;
+        font-size: 1.5rem;
+        & > a {color: inherit; text-decoration: none;}
+        & + p {margin: .5rem 0;}
+      }
+      h5 {
+        margin: 0 0 .5rem;
+        text-transform: uppercase;
+        letter-spacing: .06rem;
+        // font-weight: $medium;
+      }
+
+      .tick-title {
+        padding-right: 3rem;
+      }
+
+      .tick-links {
+        border-left: 1px solid rgba($br-teal, .3);
+        padding-left: 3rem;
+        display: flex;
+
+        ul {
+          padding: 0;
+          margin-right: 4rem;
+          list-style: none;
+
+          &:last-child {margin-right: 0;}
+    
+          li a {
+            color: $g20-white;
+            line-height: 1.6rem;
+            text-decoration: none;
+    
+            &:hover {color: $br-teal;}
+            span {
+              font-size: .75em;
+              opacity: .5;
+            }
+          }
+        }
+      }    
+    }
+  }
+
+  #copyright {
+    width: 100vw;
+    max-width: $home-body-width;
+    padding: 1rem 3rem;
+    color: rgba($article-text, .5);
+
+    p {
+      margin: 0;
+      text-align: right;
+      font-size: .9rem;      
+    }
+  }
+
+  /////////////////////////// HOMEPAGE MEDIA QUERIES ///////////////////////////
+
+  @media (max-width: 900px) {
+    #tick .padding-wrapper{
       flex-direction: column;
-      align-items: flex-end;
-    }
-  }
+      align-items: flex-start;
+      padding-top: 3rem;
 
-  @media (max-width: 920px) {
-    .section {
-      padding-left: 1.5rem;
-      padding-right: 1.5rem;
-      &.hero { padding-top: 2rem; padding-bottom: 3rem;}
-      &.search,
-      &#enterprise, &#flux { padding-top: 1.5rem; padding-bottom: 1.5rem; }
-    }
-    .hero {
-      #hero-img{ display: none; }
-      .half { width: 100%; }
-    }
-    .search {
-      .sidebar--search { max-width: 100%; }
+      .tick-links {
+        padding-left: 0;
+        border: none;
+      }
     }
   }
 
   @include media(medium) {
-    .search .algolia-autocomplete.algolia-autocomplete-right, .algolia-autocomplete.algolia-autocomplete-right {
-      .ds-dropdown-menu {
+    #influxdb {
+      .actions {
+        max-width: 100%;
+        padding-top: 3rem;
+        text-align: center;
+      }
+      .hero-img {display: none}
+    }
+    #api-guides {
+      .padding-wrapper{
+        flex-direction: column;
+        align-items: flex-start;
+        padding: 3rem;
+      }
+      .exp-btn-wrapper {width: 100%;}
+      .exp-btn {
+        margin-top: 2rem;
         width: 100%;
+        background: $br-teal;
+        color: $br-dark-blue;
       }
     }
+    .product-cards {
+      flex-direction: column;
+      .card {
+        margin-bottom: 2rem;
+        &:first-child {margin-right: 0;}
+        &:last-child {margin-left: 0;}
+      }
+    }
+    #learn-more {
+      margin-bottom: 0;
+      
+      h4 {margin-top: 0;}
+    
+      .learn-items {
+        flex-wrap: wrap;
+        .item {
+          max-width: 45%;
+          flex: 1 1 50%;
+          margin-bottom: 2rem;
+        }
+      }
+    }
+
   }
 
   @include media(small) {
-    .section {
+    .section {padding: 1rem 1rem 0;}
+    .search.section {padding-top: .25rem;}
+    .exp-btn-wrapper .exp-btn {min-width: revert;}
+    .product-cards .card {
+      padding: 2rem;
+      margin-bottom: 1rem;
 
-      .quarter, .three-quarters { width: 100%; }
-
-      &.hero {
-        order: 2;
-        padding-top: 1.5rem;
-        padding-bottom: 2rem;
-        h2 { font-size: 2rem; margin-top: .5rem; }
-        p { font-size: 1rem; line-height: 1.5rem; }
-        .actions { flex-direction: column; }
-      }
-      &.search {
-        order: 1;
-        padding: 0 1rem .5rem;
-        width: 100%;
-
-        .sidebar--search {
-          max-width: 100%;
-          font-size: 1rem;
-
-          input {
-            padding: .5em 2.15rem .5rem .75rem
-          }
-
-          &:after {
-            top: .15rem;
-            right: .25rem;
-            font-size: 1.75rem;
-          }
-          .algolia-autocomplete.algolia-autocomplete-right, .algolia-autocomplete.algolia-autocomplete-right {
-            .ds-dropdown-menu {
-              width: 100vw;
-              left: -1rem !important;
-              right: inherit;
-            }
-          }
-        }
-      }
-      &#flux, &#resources {
-        order: 3; padding-left: 0; padding-right: 0;
-        .card.cta-btns {
-          padding-top: 0;
-          a.btn {
-            display: block;
-            width: 100%;
-            margin: 0 0 .5rem;
-          }
-        }
-      }
-      &#tick-stack {
-        order: 4;
-        padding-left: 0;
-        padding-right: 0;
-        #tick-cards {
-          flex-direction: column;
-          .card {
-            width: 100%;
-            border-top: 1px solid rgba($article-text, .15);
-          }
-        }
-      }
-      &#enterprise { order: 5; padding-left: 0; padding-right: 0; }
+      h3 {font-size: 2rem;}
     }
-    .group-wrapper {flex-direction: column;}
-    .row {
-      flex-direction: column;
+    #influxdb {
+      .actions {padding: 2rem;}
+      h2 {font-size: 2.65rem;}
     }
+    #api-guides {
+      .padding-wrapper {
+        padding: 2rem;
+        h3 {font-size: 1.6rem;}
+        p {font-size: 1.1rem;}
+      }
+    }
+    #learn-more {
+      h4 {margin-left: 1rem;}
+      .learn-items {
+        flex-direction: column;
+        .item {max-width: 100%;}
+      }
+    }
+    #tick .padding-wrapper {padding: 2rem;}
   }
 
+  @media (max-width: 480px) {
+    #tick .padding-wrapper .tick-links {flex-direction: column;}
+  }
 }
diff --git a/assets/styles/layouts/_inline-icons.scss b/assets/styles/layouts/_inline-icons.scss
index 2ad92f07b..125450623 100644
--- a/assets/styles/layouts/_inline-icons.scss
+++ b/assets/styles/layouts/_inline-icons.scss
@@ -311,6 +311,7 @@
     display: inline-block;
     margin: 0;
     padding: 0;
+    font-family: $rubik;
     font-weight: 500;
     font-size: 1.15rem;
     min-width: 225px;
diff --git a/assets/styles/layouts/_sidebar.scss b/assets/styles/layouts/_sidebar.scss
index 85cbeb8b3..5df83d687 100644
--- a/assets/styles/layouts/_sidebar.scss
+++ b/assets/styles/layouts/_sidebar.scss
@@ -13,15 +13,16 @@
       display: block;
       font-family: 'icomoon-v2';
       position: absolute;
-      top: .15rem;
+      top: .25rem;
       right: .25rem;
       color: $article-text;
-      font-size: 1.75rem;
+      font-size: 1.8rem;
     }
 
     input {
-      font-family: $rubik;
-        font-weight: $medium;
+      font-family: $proxima;
+      font-weight: $medium;
+      font-size: 1.1rem;
       background: $sidebar-search-bg;
       border-radius: $radius;
       border: 1px solid $sidebar-search-bg;
@@ -38,9 +39,8 @@
         border-radius: $radius;
       }
       &::placeholder {
-        color: rgba($sidebar-search-text, .45);
+        color: rgba($sidebar-search-text, .35);
         font-weight: normal;
-        font-style: italic;
       }
     }
   }
@@ -117,7 +117,7 @@
 
     ul {
       list-style: none;
-      padding-left: 2rem;
+      padding-left: 2.3rem;
       border-left: 2px solid $nav-border;
     }
 
@@ -171,7 +171,7 @@
 
     .nav-category > a {
       color: $nav-category;
-      font-size: 1.1rem;
+      font-size: 1.2rem;
       &:hover {
         color: $nav-category-hover;
       }
@@ -192,11 +192,11 @@
     }
 
     .children-toggle {
-      width: 1rem;
-      height: 1rem;
+      width: 1.12rem;
+      height: 1.12rem;
       position: absolute;
-      top: .05rem;
-      left: -1.4rem;
+      top: .1rem;
+      left: -1.6rem;
       display: block;
       background: $nav-border;
       border-radius: 50%;
@@ -210,15 +210,15 @@
       }
       &:before {
         top: 4px;
-        left: 7px;
-        height: 8px;
+        left: 8px;
+        height: 10px;
         width: 2px;
       }
       &:after {
-        top: 7px;
+        top: 8px;
         left: 4px;
         height: 2px;
-        width: 8px;
+        width: 10px;
       }
 
       &:hover {
@@ -239,10 +239,9 @@
     h4 {
       margin: 2rem 0 0 -1rem;
       color: rgba($article-heading-alt, .5);
-      font-style: italic;
       font-weight: 700;
       text-transform: uppercase;
-      font-size: .85rem;
+      font-size: .95rem;
       letter-spacing: .08rem;
 
       &.platform, &.flux {
diff --git a/assets/styles/layouts/_top-nav.scss b/assets/styles/layouts/_top-nav.scss
index 2e65bde15..fe2299ff3 100644
--- a/assets/styles/layouts/_top-nav.scss
+++ b/assets/styles/layouts/_top-nav.scss
@@ -8,7 +8,7 @@
 
   .influx-home {
     font-family: 'icomoon-v2';
-    font-size: 1.9rem;
+    font-size: 1.4rem;
     color: $topnav-link;
     text-decoration: none;
     vertical-align: middle;
@@ -16,7 +16,7 @@
       color: $topnav-link-hover;
     }
     .icon-influx-logotype {
-      margin-left: .15rem;
+      margin-left: .6rem;
     }
   }
 
@@ -28,7 +28,6 @@
   .docs-home {
     display: inline-block;
     vertical-align: text-top;
-    font-style: italic;
     font-weight: $medium;
     font-size: 1.1rem;
     color: $topnav-link;
@@ -39,6 +38,8 @@
   }
 
   .topnav-left {
+    margin-right: .15rem;
+    padding: .25rem .15rem;
     z-index: 1;
   }
 
@@ -65,6 +66,7 @@
   @include gradient($default-dropdown-gradient);
   background-attachment: local !important;
   font-weight: $medium;
+  font-size: 1.05rem;
   border-radius: $radius;
   overflow: hidden;
   cursor: pointer;
@@ -103,10 +105,11 @@
         li {
           &:before {
             display: inline-block;
-            font-size: .8rem;
+            font-size: .85rem;
             color: $g2-kevlar;
-            font-style: italic;
+            text-transform: uppercase;
             font-weight: bold;
+            letter-spacing: .04rem;
             opacity: .65;
             mix-blend-mode: multiply;
           }
diff --git a/assets/styles/layouts/_url-selector.scss b/assets/styles/layouts/_url-selector.scss
index fcbd9e83e..3f5a53c04 100644
--- a/assets/styles/layouts/_url-selector.scss
+++ b/assets/styles/layouts/_url-selector.scss
@@ -131,6 +131,45 @@
         margin: .5rem .5rem .5rem 0;
         padding: 0;
         list-style: none;
+
+        &.clusters {
+          padding-left: 1.75rem;
+        }
+      }
+
+      p.region {
+
+        .fake-radio  {
+          position: relative;
+          display: inline-block;
+          height: 1.15em;
+          width: 1.15em;
+          margin: 0 0.3rem 0 0.1rem;
+          border-radius: $radius;
+          border: 1.5px solid transparent;
+          background: rgba($article-text, 0.05);
+          border: 1.5px solid rgba($article-text, 0.2);
+          vertical-align: text-top;
+          cursor: pointer;
+
+          &:after {
+            content: "";
+            position: absolute;
+            display: block;
+            height: .5rem;
+            width: .5rem;
+            top: .23rem;
+            left: .23rem;
+            border-radius: 50%;
+            background: rgba($article-text, .3);
+            opacity: 0;
+            transition: opacity .2s;
+          }
+
+          &.checked:after {
+            opacity: 1;
+          }
+        }
       }
     }
   }
diff --git a/assets/styles/layouts/article/_blocks.scss b/assets/styles/layouts/article/_blocks.scss
index dc522c755..4992b7014 100644
--- a/assets/styles/layouts/article/_blocks.scss
+++ b/assets/styles/layouts/article/_blocks.scss
@@ -7,7 +7,7 @@ blockquote,
   border-width: 0 0 0 4px;
   border-style: solid;
   border-radius: 0 $radius $radius 0;
-  font-size: .95rem;
+  font-size: 1.05rem;
 
   ul,ol {
     &:last-child { margin-bottom: 1.85rem; }
diff --git a/assets/styles/layouts/article/_buttons.scss b/assets/styles/layouts/article/_buttons.scss
index bb99b0872..3c2f0e27b 100644
--- a/assets/styles/layouts/article/_buttons.scss
+++ b/assets/styles/layouts/article/_buttons.scss
@@ -7,7 +7,7 @@ a.btn {
   padding: 0.85rem 1.5rem;
   color: $article-btn-text !important;
   border-radius: $radius;
-  font-size: .95rem;
+  font-size: 1.05rem;
   z-index: 1;
   @include gradient($article-btn-gradient);
 
diff --git a/assets/styles/layouts/article/_captions.scss b/assets/styles/layouts/article/_captions.scss
index e01397b0d..4c8276ead 100644
--- a/assets/styles/layouts/article/_captions.scss
+++ b/assets/styles/layouts/article/_captions.scss
@@ -1,19 +1,14 @@
 .caption {
   margin: -2rem 0 2rem;
   padding-left: .25rem;
-  font-size: .85rem;
+  font-size: .95rem;
   font-style: italic;
   opacity: .8;
+  color: $article-text;
 
   p { line-height: 1.25rem; }
 }
 
-.code-tabs-wrapper, .code-tab-content {
-  & + .caption {
-    margin-top: -2.75rem;
-  }
-}
-
 p {
   & + .caption {
     padding: 0;
diff --git a/assets/styles/layouts/article/_code-api-methods.scss b/assets/styles/layouts/article/_code-api-methods.scss
new file mode 100644
index 000000000..67d30d0e9
--- /dev/null
+++ b/assets/styles/layouts/article/_code-api-methods.scss
@@ -0,0 +1,14 @@
+.api {
+  margin-right: .35rem;
+  padding: .15rem .5rem .25rem;
+  border-radius: $radius;
+  color: $g20-white;
+  font-weight: bold;
+  font-size: 1rem;
+
+  &.get { background: $gr-viridian; }
+  &.post { background: $b-ocean; }
+  &.patch { background: $y-topaz; }
+  &.delete { background: $r-ruby; }
+  &.put {background: $br-pulsar; }
+}
\ No newline at end of file
diff --git a/assets/styles/layouts/article/_code.scss b/assets/styles/layouts/article/_code.scss
index b88fe081e..8bfd7b09c 100644
--- a/assets/styles/layouts/article/_code.scss
+++ b/assets/styles/layouts/article/_code.scss
@@ -12,7 +12,7 @@ p,li,table {
     border-radius: $radius;
     color: $article-code;
     white-space: nowrap;
-    font-size: .95rem;
+    font-size: 1rem;
     font-style: normal;
   }
 }
@@ -66,25 +66,33 @@ pre {
   overflow-y: hidden;
   code {
     padding: 0;
-    font-size: .95rem;
-    line-height: 1.5rem;
+    font-size: 1rem;
+    line-height: 1.7rem;
     white-space: pre;
   }
+
+  @import "code-api-methods";
 }
 
-pre .api {
-  margin-right: .35rem;
-  padding: .15rem .5rem .25rem;
-  border-radius: $radius;
-  color: $g20-white;
-  font-weight: bold;
-  font-size: .9rem;
+///////////////////////// Codeblocks fullscreen toggle /////////////////////////
+
+.codeblock {
+  position: relative;
+  
+  .fullscreen-toggle {
+    cursor: pointer;
+    position: absolute;
+    top: .5rem;
+    right: .5rem;
+    line-height: 0;
+    font-size: 1.15rem;
+    color: $article-code;
+    opacity: .5;
+    transition: opacity .2s;
+
+    &:hover {opacity: 1}
+  }
 
-  &.get { background: $gr-viridian; }
-  &.post { background: $b-ocean; }
-  &.patch { background: $y-topaz; }
-  &.delete { background: $r-ruby; }
-  &.put {background: $br-pulsar; }
 }
 
 ////////////////////////////////////////////////////////////////////////////////
diff --git a/assets/styles/layouts/article/_feedback.scss b/assets/styles/layouts/article/_feedback.scss
index 7d9f5c1bc..771f268da 100644
--- a/assets/styles/layouts/article/_feedback.scss
+++ b/assets/styles/layouts/article/_feedback.scss
@@ -31,8 +31,8 @@
       &.community:before {
         content: "\e900";
         color: $article-heading-alt;
-        margin: 0 .25rem 0 -.25rem;
-        font-size: 1.65rem;
+        margin: 0 .5rem 0 -.25rem;
+        font-size: 1.2rem;
         font-family: 'icomoon-v2';
         vertical-align: middle;
       }
@@ -55,7 +55,7 @@
   a {
     display: block;
     padding-left: 1rem;
-    font-size: .85rem;
+    font-size: .95rem;
 
     &.btn {
       color: $article-text !important;
@@ -75,12 +75,11 @@
 
     &.edit:before {
       content: "\e92f";
-      font-size: .75rem;
-      vertical-align: top;
+      font-size: .85rem;
     }
     &.issue:before {
       content: "\e934";
-      font-size: .95rem;
+      font-size: 1rem;
     }
   }
 }
diff --git a/assets/styles/layouts/article/_html-diagrams.scss b/assets/styles/layouts/article/_html-diagrams.scss
index c467e1f7f..af17df69b 100644
--- a/assets/styles/layouts/article/_html-diagrams.scss
+++ b/assets/styles/layouts/article/_html-diagrams.scss
@@ -43,7 +43,7 @@
 }
 
 ///////////////////////////////// Shard diagram ////////////////////////////////
-#shard-diagram {
+#shard-diagram, #data-retention {
   display: flex;
   flex-direction: column;
   max-width: 550px;
@@ -71,6 +71,26 @@
         border-left: 1px solid $article-text;
       }
     }
+
+    .one-quarter {width: 25%; height: .75rem;}
+    .three-quarters {width: 75%; height: .75rem;}
+    .border-left {border-left: 1px solid $article-text;}
+    .retention-label {
+      position: relative;
+      &:before {
+        content: "";
+        display: inline-block;
+        width: .65rem;
+        margin-right: .5rem;
+        border-top: 1px solid $article-text;
+        vertical-align: middle;
+      }
+    }
+    .deleted-label {
+      color: $r-ruby;
+      text-align: center;
+      font-size: .9rem;
+    }
   }
   .shard-groups {
     display: flex;
@@ -96,9 +116,14 @@
         padding: .65rem 1rem;
         color: #fff;
         border-radius: .25rem;
-        @include gradient($article-table-header, 90deg)
+        @include gradient($article-table-header, 90deg);
         background-attachment: fixed;
       }
+
+      &.deleted {
+        opacity: .3;
+        .shard {@include gradient($grad-red-dark)}
+      }
     }
   }
 }
diff --git a/assets/styles/layouts/article/_tabbed-content.scss b/assets/styles/layouts/article/_tabbed-content.scss
index 3be7ebb48..f47001bb5 100644
--- a/assets/styles/layouts/article/_tabbed-content.scss
+++ b/assets/styles/layouts/article/_tabbed-content.scss
@@ -12,7 +12,7 @@
     flex-grow: 1;
     margin: 2px;
     position: relative;
-    font-size: 0.875rem;
+    font-size: 1rem;
     font-weight: $medium;
     padding: .65rem 1.25rem;
     display: inline-block;
@@ -72,7 +72,7 @@
     margin: 0;
     border-radius: $radius $radius 0 0;
     display: inline-block;
-    font-size: 0.875rem;
+    font-size: 1rem;
     background: $article-bg;
     color: rgba($article-tab-code-text, .5);
     &:hover {
@@ -97,7 +97,7 @@
   margin: .75rem 0 3rem;
   width: 100%;
 
-  & > :not(table, .fs-diagram) {
+  & > :not(table, .fs-diagram, img) {
     width: 100%;
     margin-left: 0;
   }
diff --git a/assets/styles/layouts/article/_tables.scss b/assets/styles/layouts/article/_tables.scss
index 6d043b0ca..a52b34008 100644
--- a/assets/styles/layouts/article/_tables.scss
+++ b/assets/styles/layouts/article/_tables.scss
@@ -31,8 +31,9 @@ table {
   }
 
   td {
-    font-size: .95rem;
+    font-size: 1.05rem;
     line-height: 1.5em;
+    code {font-size: .95rem;}
   }
 
   tr{
@@ -49,6 +50,15 @@ table {
   }
 
   img { margin-bottom: 0; }
+
+  &.cloud-urls {
+    a { white-space: nowrap; }
+    p {
+      margin: 0 0 .5rem 0;
+      &:last-child { margin-bottom: 0 }
+    }
+    .cluster-name { font-weight: $medium; color: $article-bold; }
+  }
 }
 
 table + table {
@@ -64,5 +74,5 @@ table + table {
 p.table-group-key {
   margin: 1rem 0 -.75rem;
   font-weight: $medium;
-  font-size: .87rem;
+  font-size: .95rem;
 }
diff --git a/assets/styles/layouts/article/_tags.scss b/assets/styles/layouts/article/_tags.scss
index cb5e96bfd..6f4235e82 100644
--- a/assets/styles/layouts/article/_tags.scss
+++ b/assets/styles/layouts/article/_tags.scss
@@ -8,11 +8,11 @@
   .tag {
     background: $body-bg;
     margin: .12rem 0;
-    padding: .35rem .6rem;
+    padding: .4rem .65rem;
     font-style: italic;
     font-weight: $medium;
     color: rgba($article-text, .75) !important;
-    font-size: .8rem;
+    font-size: .9rem;
     border-radius: 1rem;
 
     &:after {
diff --git a/assets/styles/layouts/article/_title.scss b/assets/styles/layouts/article/_title.scss
index 37c575719..b54a64008 100644
--- a/assets/styles/layouts/article/_title.scss
+++ b/assets/styles/layouts/article/_title.scss
@@ -13,7 +13,7 @@
       padding: 0 .65em 0 .75em;
       color: $article-heading;
       background: rgba($article-heading, .07);
-      font-size: .9rem;
+      font-size: .95rem;
       font-weight: $medium;
       border-radius: 1em;
       display: inline-block;
diff --git a/assets/styles/styles-default.scss b/assets/styles/styles-default.scss
index 7be4055d3..899646c58 100644
--- a/assets/styles/styles-default.scss
+++ b/assets/styles/styles-default.scss
@@ -1,8 +1,7 @@
 // InfluxData Docs Default Theme (Light) 
 
 // Import Tools
-@import "tools/icomoon-v2",
-        "tools/icon",
+@import "tools/fonts",
         "tools/media-queries.scss",
         "tools/mixins.scss",
         "tools/tooltips",
@@ -27,7 +26,8 @@
         "layouts/url-selector",
         "layouts/feature-callouts",
         "layouts/v1-overrides",
-        "layouts/notifications";
+        "layouts/notifications",
+        "layouts/fullscreen-code";
 
 // Import Product-specifc color schemes
 @import "product-overrides/telegraf",
diff --git a/assets/styles/themes/_theme-dark.scss b/assets/styles/themes/_theme-dark.scss
index df9c6ec21..3d0b42b26 100644
--- a/assets/styles/themes/_theme-dark.scss
+++ b/assets/styles/themes/_theme-dark.scss
@@ -25,7 +25,7 @@ $theme-switch-dark: none;
 
 // Search
 $sidebar-search-bg: $grey15;
-$sidebar-search-shadow: rgba($g0-obsidian, .05);
+$sidebar-search-shadow: rgba($g0-obsidian, .5);
 $sidebar-search-highlight: $b-pool;
 $sidebar-search-text: $g20-white;
 
@@ -179,10 +179,8 @@ $landing-btn-grad: $grad-blue;
 $landing-btn-grad-hover: $grad-blue-light;
 
 // Home page colors
-$home-btn-gradient: $grad-NineteenEightyFour;
-$home-btn-gradient-hover: $grad-PastelGothic;
-$home-tick-bg-gradient: $grad-cool-grey-abyss;
-$default-home-card-gradient: $grad-Miyazakisky;
+$home-icon-c1: $g20-white;
+$home-icon-c2: $body-bg;
 
 // Tooltip colors
 $tooltip-color: $br-chartreuse;
diff --git a/assets/styles/themes/_theme-light.scss b/assets/styles/themes/_theme-light.scss
index 06dfe4497..16c4a116f 100644
--- a/assets/styles/themes/_theme-light.scss
+++ b/assets/styles/themes/_theme-light.scss
@@ -18,7 +18,7 @@ $body-bg: #f3f4fb !default;
 $radius: 2px !default;
 
 // TopNav Colors
-$topnav-link: $g8-storm !default;
+$topnav-link: #020a47 !default;
 $topnav-link-hover: $b-dodger !default;
 $default-dropdown-gradient: $grad-PastelGothic !default;
 $theme-switch-light: none !default;
@@ -28,7 +28,7 @@ $theme-switch-dark: inline-block !default;
 $sidebar-search-bg: $g20-white !default;
 $sidebar-search-shadow: #cfd1e5 !default;
 $sidebar-search-highlight: $b-pool !default;
-$sidebar-search-text: $g8-storm !default;
+$sidebar-search-text: $g6-smoke !default;
 
 // Left Navigation
 $nav-category: $b-dodger !default;
@@ -50,8 +50,8 @@ $product-enterprise: $br-pulsar !default;
 $article-bg: $g20-white !default;
 $article-heading: $br-pulsar !default;
 $article-heading-alt: $g5-pepper !default;
-$article-text: $g6-smoke !default;
-$article-bold: $g6-smoke !default;
+$article-text: $br-dark-blue !default;
+$article-bold: $br-dark-blue !default;
 $article-link: $b-pool !default;
 $article-link-hover: $br-magenta !default;
 $article-shadow: #cfd1e5 !default;
@@ -179,10 +179,8 @@ $landing-btn-grad: $grad-blue !default;
 $landing-btn-grad-hover: $grad-blue-light !default;
 
 // Home page colors
-$home-btn-gradient: $grad-NineteenEightyFour !default;
-$home-btn-gradient-hover: $grad-PastelGothic !default;
-$home-tick-bg-gradient: $grad-grey-mist !default;
-$default-home-card-gradient: $grad-PastelGothic !default;
+$home-icon-c1: $br-dark-blue !default;
+$home-icon-c2: $g20-white !default;
 
 // Tooltip colors
 $tooltip-color: $p-amethyst !default;
diff --git a/assets/styles/tools/_color-palette.scss b/assets/styles/tools/_color-palette.scss
index 15f437560..5eca3ad52 100644
--- a/assets/styles/tools/_color-palette.scss
+++ b/assets/styles/tools/_color-palette.scss
@@ -1,5 +1,11 @@
 // Influx Color Palette
 
+// Brand Colors 2022
+$br-dark-blue: #020a47;
+$br-new-magenta: #d30971;
+$br-new-purple: #9b2aff;
+$br-teal: #5ee4e4;
+
 // Brand Colors
 $br-chartreuse: #D6F622;
 $br-deeppurple: #13002D;
@@ -165,4 +171,10 @@ $grey85: #D5D5DD;
 $grey95: #F1F1F3;
 $white: #FFFFFF;
 
-$grad-cool-grey-abyss: $grey10, $grey15;
\ No newline at end of file
+$grad-cool-grey-abyss: $grey10, $grey15;
+
+////////////////////////////// NEW BRAND GRADIENTS /////////////////////////////
+$grad-burningDusk: $br-new-magenta, $br-new-purple;
+$grad-coolDusk: #771cc7, #b2025b;
+$grad-tealDream: $b-pool, $br-teal;
+$grad-tealDeepSleep: $b-ocean, #0ab8b8;
diff --git a/assets/styles/tools/_fonts.scss b/assets/styles/tools/_fonts.scss
new file mode 100644
index 000000000..71a44c09e
--- /dev/null
+++ b/assets/styles/tools/_fonts.scss
@@ -0,0 +1,38 @@
+$rubik: 'Rubik', sans-serif;
+$proxima: 'Proxima Nova', sans-serif;
+$code: 'IBM Plex Mono', monospace;;
+
+// Font weights
+$medium: 500;
+$bold: 700;
+
+// Global font size and rendering
+body {
+  font-size: 18px;
+  -webkit-font-smoothing: antialiased;
+  -moz-osx-font-smoothing: grayscale;
+}
+
+@font-face {
+  font-family: "Proxima Nova";
+  src: url("fonts/proxima-nova.otf") format("opentype");
+  font-weight: 300;
+}
+@font-face {
+  font-family: 'Proxima Nova';
+  src: url('fonts/proxima-nova-medium.otf') format('opentype');
+  font-weight: 400;
+}
+@font-face {
+  font-family: 'Proxima Nova';
+  src: url('fonts/proxima-nova-semibold.otf') format('opentype');
+  font-weight: 500 600;
+}
+@font-face {
+  font-family: 'Proxima Nova';
+  src: url('fonts/proxima-nova-bold.otf') format('opentype');
+  font-weight: 700;
+}
+
+@import "tools/icon-fonts/icomoon-v2";
+@import "tools/icon-fonts/icon";
\ No newline at end of file
diff --git a/assets/styles/tools/_icomoon-v2.scss b/assets/styles/tools/icon-fonts/_icomoon-v2.scss
similarity index 100%
rename from assets/styles/tools/_icomoon-v2.scss
rename to assets/styles/tools/icon-fonts/_icomoon-v2.scss
diff --git a/assets/styles/tools/_icon.scss b/assets/styles/tools/icon-fonts/_icon.scss
similarity index 100%
rename from assets/styles/tools/_icon.scss
rename to assets/styles/tools/icon-fonts/_icon.scss
diff --git a/config.staging.toml b/config.staging.toml
index dca5748bd..927cbdd71 100644
--- a/config.staging.toml
+++ b/config.staging.toml
@@ -25,6 +25,7 @@ hrefTargetBlank = true
 smartDashes = false
 
 [taxonomies]
+  "influxdb/v2.2/tag" = "influxdb/v2.1/tags"
   "influxdb/v2.1/tag" = "influxdb/v2.1/tags"
   "influxdb/v2.0/tag" = "influxdb/v2.0/tags"
   "influxdb/cloud/tag" = "influxdb/cloud/tags"
diff --git a/config.toml b/config.toml
index 0867ca62f..49cd97863 100644
--- a/config.toml
+++ b/config.toml
@@ -21,6 +21,7 @@ hrefTargetBlank = true
 smartDashes = false
 
 [taxonomies]
+  "influxdb/v2.2/tag" = "influxdb/v2.1/tags"
   "influxdb/v2.1/tag" = "influxdb/v2.1/tags"
   "influxdb/v2.0/tag" = "influxdb/v2.0/tags"
   "influxdb/cloud/tag" = "influxdb/cloud/tags"
diff --git a/content/chronograf/v1.6/about_the_project/cla.md b/content/chronograf/v1.6/about_the_project/cla.md
index e8329ed42..6805d670b 100644
--- a/content/chronograf/v1.6/about_the_project/cla.md
+++ b/content/chronograf/v1.6/about_the_project/cla.md
@@ -5,7 +5,8 @@ menu:
   chronograf_1_6:
     weight: 30
     parent: About the project
-    url: https://www.influxdata.com/legal/cla/
+    params:
+      url: https://www.influxdata.com/legal/cla/
 ---
 
 Before you can contribute to the Chronograf project, you need to submit the [InfluxData Contributor License Agreement (CLA)](https://www.influxdata.com/legal/cla/) available on the InfluxData main site.
diff --git a/content/chronograf/v1.6/about_the_project/contributing.md b/content/chronograf/v1.6/about_the_project/contributing.md
index 5cdfc6ec5..f6f143d89 100644
--- a/content/chronograf/v1.6/about_the_project/contributing.md
+++ b/content/chronograf/v1.6/about_the_project/contributing.md
@@ -5,7 +5,8 @@ menu:
     name: Contributing
     weight: 20
     parent: About the project
-    url: https://github.com/influxdata/chronograf/blob/master/CONTRIBUTING.md
+    params:
+      url: https://github.com/influxdata/chronograf/blob/master/CONTRIBUTING.md
 ---
 
 See [Contributing to Chronograf](https://github.com/influxdata/chronograf/blob/master/CONTRIBUTING.md) in the Chronograf GitHub project to learn how you can contribute to the Chronograf project.
diff --git a/content/chronograf/v1.6/about_the_project/licenses.md b/content/chronograf/v1.6/about_the_project/licenses.md
index bbc830bd7..951057d94 100644
--- a/content/chronograf/v1.6/about_the_project/licenses.md
+++ b/content/chronograf/v1.6/about_the_project/licenses.md
@@ -5,7 +5,8 @@ menu:
     Name: Open source license
     weight: 40
     parent: About the project
-    url: https://github.com/influxdata/chronograf/blob/master/LICENSE
+    params:
+      url: https://github.com/influxdata/chronograf/blob/master/LICENSE
 ---
 
 The [open source license for Chronograf](https://github.com/influxdata/chronograf/blob/master/LICENSE) is available in the Chronograf GitHub project.
diff --git a/content/chronograf/v1.7/about_the_project/cla.md b/content/chronograf/v1.7/about_the_project/cla.md
index b5cc29262..bfec0fe28 100644
--- a/content/chronograf/v1.7/about_the_project/cla.md
+++ b/content/chronograf/v1.7/about_the_project/cla.md
@@ -5,7 +5,8 @@ menu:
   chronograf_1_7:
     weight: 30
     parent: About the project
-    url: https://www.influxdata.com/legal/cla/
+    params:
+      url: https://www.influxdata.com/legal/cla/
 ---
 
 Before you can contribute to the Chronograf project, you need to submit the [InfluxData Contributor License Agreement (CLA)](https://www.influxdata.com/legal/cla/) available on the InfluxData main site.
diff --git a/content/chronograf/v1.7/about_the_project/contributing.md b/content/chronograf/v1.7/about_the_project/contributing.md
index 5ac5823f4..5fa0aa9b6 100644
--- a/content/chronograf/v1.7/about_the_project/contributing.md
+++ b/content/chronograf/v1.7/about_the_project/contributing.md
@@ -5,7 +5,8 @@ menu:
     name: Contribute
     weight: 20
     parent: About the project
-    url: https://github.com/influxdata/chronograf/blob/master/CONTRIBUTING.md
+    params:
+      url: https://github.com/influxdata/chronograf/blob/master/CONTRIBUTING.md
 ---
 
 See [Contributing to Chronograf](https://github.com/influxdata/chronograf/blob/master/CONTRIBUTING.md) in the Chronograf GitHub project to learn how you can contribute to the Chronograf project.
diff --git a/content/chronograf/v1.7/about_the_project/licenses.md b/content/chronograf/v1.7/about_the_project/licenses.md
index 714c93116..c9ced67ae 100644
--- a/content/chronograf/v1.7/about_the_project/licenses.md
+++ b/content/chronograf/v1.7/about_the_project/licenses.md
@@ -5,7 +5,8 @@ menu:
     Name: Open source license
     weight: 40
     parent: About the project
-    url: https://github.com/influxdata/chronograf/blob/master/LICENSE
+    params:
+      url: https://github.com/influxdata/chronograf/blob/master/LICENSE
 ---
 
 The [open source license for Chronograf](https://github.com/influxdata/chronograf/blob/master/LICENSE) is available in the Chronograf GitHub project.
diff --git a/content/chronograf/v1.7/administration/prebuilt-dashboards.md b/content/chronograf/v1.7/administration/prebuilt-dashboards.md
index eefd25fc3..0503e5927 100644
--- a/content/chronograf/v1.7/administration/prebuilt-dashboards.md
+++ b/content/chronograf/v1.7/administration/prebuilt-dashboards.md
@@ -30,12 +30,12 @@ The Docker dashboard displays the following information:
 
 ### Plugins
 
-- [`docker` plugin](/{{< latest "telegraf" >}}/plugins/#docker)
-- [`disk` plugin](/{{< latest "telegraf" >}}/plugins/#disk)
-- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#mem)
-- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/#diskio)
-- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#system)
-- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/#cpu)
+- [`docker` plugin](/{{< latest "telegraf" >}}/plugins/#input-docker)
+- [`disk` plugin](/{{< latest "telegraf" >}}/plugins/#input-disk)
+- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#input-mem)
+- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/#input-diskio)
+- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#input-system)
+- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/#input-cpu)
 
 ## Kubernetes Node
 The Kubernetes Node dashboard displays the following information:
@@ -53,7 +53,7 @@ The Kubernetes Node dashboard displays the following information:
 - K8s - Kubelet Memory Bytes
 
 ### Plugins
-- [kubernetes](/{{< latest "telegraf" >}}/plugins/#kubernetes)
+- [kubernetes](/{{< latest "telegraf" >}}/plugins/#input-kubernetes)
 
 ## Kubernetes Overview
 The Kubernetes Node dashboard displays the following information:
@@ -72,7 +72,7 @@ The Kubernetes Node dashboard displays the following information:
 
 ### Plugins
 
-- [kubernetes](/{{< latest "telegraf" >}}/plugins/#kubernetes)
+- [kubernetes](/{{< latest "telegraf" >}}/plugins/#input-kubernetes)
 
 ## Kubernetes Pod
 The Kubernetes Pod dashboard displays the following information:
@@ -87,7 +87,7 @@ The Kubernetes Pod dashboard displays the following information:
 - K8s - Pod TX Bytes/Second
 
 ### Plugins
-- [kubernetes](/{{< latest "telegraf" >}}/plugins/#kubernetes)
+- [kubernetes](/{{< latest "telegraf" >}}/plugins/#input-kubernetes)
 
 ## Riak
 The Riak dashboard displays the following information:
@@ -101,7 +101,7 @@ The Riak dashboard displays the following information:
 - Riak - Read Repairs/Minute
 
 ### Plugins
-- [`riak` plugin](/{{< latest "telegraf" >}}/plugins/#riak)
+- [`riak` plugin](/{{< latest "telegraf" >}}/plugins/#input-riak)
 
 ## Consul
 The Consul dashboard displays the following information:
@@ -110,7 +110,7 @@ The Consul dashboard displays the following information:
 - Consul - Number of Warning Health Checks
 
 ### Plugins
-- [`consul` plugin](/{{< latest "telegraf" >}}/plugins/#consul)
+- [`consul` plugin](/{{< latest "telegraf" >}}/plugins/#input-consul)
 
 ## Consul Telemetry
 The Consul Telemetry dashboard displays the following information:
@@ -125,7 +125,7 @@ The Consul Telemetry dashboard displays the following information:
 - Consul - Number of Serf Events
 
 ### Plugins
-[`consul` plugin](/{{< latest "telegraf" >}}/plugins/#consul)
+[`consul` plugin](/{{< latest "telegraf" >}}/plugins/#input-consul)
 
 
 ## Mesos
@@ -140,7 +140,7 @@ The Mesos dashboard displays the following information:
 - Mesos Master Uptime
 
 ### Plugins
-- [`mesos` plugin](/{{< latest "telegraf" >}}/plugins/#mesos)
+- [`mesos` plugin](/{{< latest "telegraf" >}}/plugins/#input-mesos)
 
 ## RabbitMQ
 The RabbitMQ dashboard displays the following information:
@@ -151,7 +151,7 @@ The RabbitMQ dashboard displays the following information:
 
 ### Plugins
 
-- [`rabbitmq` plugin](/{{< latest "telegraf" >}}/plugins/#rabbitmq)
+- [`rabbitmq` plugin](/{{< latest "telegraf" >}}/plugins/#input-rabbitmq)
 
 ## System
 
@@ -170,14 +170,14 @@ The System dashboard displays the following information:
 
 ### Plugins
 
-- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#system)
-- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#mem)
-- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/#cpu)
-- [`disk` plugin](/{{< latest "telegraf" >}}/plugins/#disk)
-- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/#diskio)
-- [`net` plugin](/{{< latest "telegraf" >}}/plugins/#net)
-- [`processes` plugin](/{{< latest "telegraf" >}}/plugins/#processes)
-- [`swap` plugin](/{{< latest "telegraf" >}}/plugins/#swap)
+- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#input-system)
+- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#input-mem)
+- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/#input-cpu)
+- [`disk` plugin](/{{< latest "telegraf" >}}/plugins/#input-disk)
+- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/#input-diskio)
+- [`net` plugin](/{{< latest "telegraf" >}}/plugins/#input-net)
+- [`processes` plugin](/{{< latest "telegraf" >}}/plugins/#input-processes)
+- [`swap` plugin](/{{< latest "telegraf" >}}/plugins/#input-swap)
 
 
 
@@ -198,7 +198,7 @@ The VMware vSphere Overview dashboard gives an overview of your VMware vSphere C
   - VM CPU % Ready for :clustername:
 
 ### Plugins
-- [`vsphere` plugin](/{{< latest "telegraf" >}}/plugins/#vmware-vsphere)
+- [`vsphere` plugin](/{{< latest "telegraf" >}}/plugins/#input-vmware-vsphere)
 
 ## Apache
 The Apache dashboard displays the following information:
@@ -221,12 +221,12 @@ The Apache dashboard displays the following information:
 
 ### Plugins
 
-- [`apache` plugin](/{{< latest "telegraf" >}}/plugins/#apache)
-- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#system)
-- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#mem)
-- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/#diskio)
-- [`net` plugin](/{{< latest "telegraf" >}}/plugins/#net)
-- [`logparser` plugin](/{{< latest "telegraf" >}}/plugins/#logparser)
+- [`apache` plugin](/{{< latest "telegraf" >}}/plugins/#input-apache)
+- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#input-system)
+- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#input-mem)
+- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/#input-diskio)
+- [`net` plugin](/{{< latest "telegraf" >}}/plugins/#input-net)
+- [`logparser` plugin](/{{< latest "telegraf" >}}/plugins/#input-logparser)
 
 ## ElasticSearch
 The ElasticSearch dashboard displays the following information:
@@ -243,7 +243,7 @@ The ElasticSearch dashboard displays the following information:
 - ElasticSearch - JVM Heap Usage
 
 ### Plugins
-- [`elasticsearch` plugin](/{{< latest "telegraf" >}}/plugins/#elasticsearch)
+- [`elasticsearch` plugin](/{{< latest "telegraf" >}}/plugins/#input-elasticsearch)
 
 
 ## InfluxDB
@@ -272,12 +272,12 @@ The InfluxDB dashboard displays the following information:
 
 ### Plugins
 
-- [`influxdb` plugin](/{{< latest "telegraf" >}}/plugins/#influxdb)
-- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/#cpu)
-- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#system)
-- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#mem)
-- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/#diskio)
-- [`net` plugin](/{{< latest "telegraf" >}}/plugins/#net)
+- [`influxdb` plugin](/{{< latest "telegraf" >}}/plugins/#input-influxdb)
+- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/#input-cpu)
+- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#input-system)
+- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#input-mem)
+- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/#input-diskio)
+- [`net` plugin](/{{< latest "telegraf" >}}/plugins/#input-net)
 
 
 
@@ -299,7 +299,7 @@ The Memcached dashboard displays the following information:
 - Memcached - Evictions/10 Seconds
 
 ### Plugins
-- [`memcached` plugin](/{{< latest "telegraf" >}}/plugins/#memcached)
+- [`memcached` plugin](/{{< latest "telegraf" >}}/plugins/#input-memcached)
 
 
 ## NSQ
@@ -315,7 +315,7 @@ The NSQ dashboard displays the following information:
 - NSQ - Topic Egress
 
 ### Plugins
-- [`nsq` plugin](/{{< latest "telegraf" >}}/plugins/#nsq)
+- [`nsq` plugin](/{{< latest "telegraf" >}}/plugins/#input-nsq)
 
 ## PostgreSQL
 The PostgreSQL dashboard displays the following information:
@@ -340,11 +340,11 @@ The PostgreSQL dashboard displays the following information:
 
 ### Plugins
 
-- [`postgresql` plugin](/{{< latest "telegraf" >}}/plugins/#postgresql)
-- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#system)
-- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#mem)
-- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/#cpu)
-- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/#diskio)
+- [`postgresql` plugin](/{{< latest "telegraf" >}}/plugins/#input-postgresql)
+- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#input-system)
+- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#input-mem)
+- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/#input-cpu)
+- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/#input-diskio)
 
 
 ## HAProxy
@@ -367,7 +367,7 @@ The HAProxy dashboard displays the following information:
 - HAProxy - Backend Error Responses/Second
 
 ### Plugins
-- [`haproxy` plugin](/{{< latest "telegraf" >}}/plugins/#haproxy)
+- [`haproxy` plugin](/{{< latest "telegraf" >}}/plugins/#input-haproxy)
 
 
 ## NGINX
@@ -379,7 +379,7 @@ The NGINX dashboard displays the following information:
 - NGINX - Active Client State
 
 ### Plugins
-- [`nginx` plugin](/{{< latest "telegraf" >}}/plugins/#nginx)
+- [`nginx` plugin](/{{< latest "telegraf" >}}/plugins/#input-nginx)
 
 ## Redis
 The Redis dashboard displays the following information:
@@ -390,7 +390,7 @@ The Redis dashboard displays the following information:
 - Redis - Memory
 
 ### Plugins
-- [`redis` plugin](/{{< latest "telegraf" >}}/plugins/#redis)
+- [`redis` plugin](/{{< latest "telegraf" >}}/plugins/#input-redis)
 
 
 ## VMware vSphere VMs
@@ -406,7 +406,7 @@ The VMWare vSphere VMs dashboard gives an overview of your VMware vSphere virtua
 - Total Disk Latency for :vmname:
 
 ### Plugins
-- [`vsphere` plugin](/{{< latest "telegraf" >}}/plugins/#vsphere)
+- [`vsphere` plugin](/{{< latest "telegraf" >}}/plugins/#input-vsphere)
 
 ## VMware vSphere Hosts
 
@@ -422,7 +422,7 @@ The VMWare vSphere Hosts dashboard displays the following information:
 - Total Disk Latency for :esxhostname:
 
 ### Plugins
-- [`vsphere` plugin](/{{< latest "telegraf" >}}/plugins/#vsphere)
+- [`vsphere` plugin](/{{< latest "telegraf" >}}/plugins/#input-vsphere)
 
 ## PHPfpm
 The PHPfpm dashboard displays the following information:
@@ -433,7 +433,7 @@ The PHPfpm dashboard displays the following information:
 - PHPfpm - Max Children Reached
 
 ### Plugins
-- [`phpfpm` plugin](/{{< latest "telegraf" >}}/plugins/#nginx)
+- [`phpfpm` plugin](/{{< latest "telegraf" >}}/plugins/#input-nginx)
 
 ## Win System
 The Win System dashboard displays the following information:
@@ -445,7 +445,7 @@ The Win System dashboard displays the following information:
 - System - Load
 
 ### Plugins
-- [`win_services` plugin](/{{< latest "telegraf" >}}/plugins/#windows-services)
+- [`win_services` plugin](/{{< latest "telegraf" >}}/plugins/#input-windows-services)
 
 
 ## MySQL
@@ -472,9 +472,9 @@ The MySQL dashboard displays the following information:
 - InnoDB Data
 
 ### Plugins
-- [`mySQL` plugin](/{{< latest "telegraf" >}}/plugins/#mysql)
-- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#system)
-- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#mem)
+- [`mySQL` plugin](/{{< latest "telegraf" >}}/plugins/#input-mysql)
+- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#input-system)
+- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#input-mem)
 
 ## Ping
 The Ping dashboard displays the following information:
@@ -483,4 +483,4 @@ The Ping dashboard displays the following information:
 - Ping - Response Times (ms)
 
 ### Plugins
-- [`ping` plugin](/{{< latest "telegraf" >}}/plugins/#ping)
+- [`ping` plugin](/{{< latest "telegraf" >}}/plugins/#input-ping)
diff --git a/content/chronograf/v1.7/guides/using-precreated-dashboards.md b/content/chronograf/v1.7/guides/using-precreated-dashboards.md
index 5c1724843..828c5c009 100644
--- a/content/chronograf/v1.7/guides/using-precreated-dashboards.md
+++ b/content/chronograf/v1.7/guides/using-precreated-dashboards.md
@@ -65,7 +65,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
 
 ## apache
 
-**Required Telegraf plugin:** [Apache input plugin](/{{< latest "telegraf" >}}/plugins/#apache)
+**Required Telegraf plugin:** [Apache input plugin](/{{< latest "telegraf" >}}/plugins/#input-apache)
 
 `apache.json`
 
@@ -75,7 +75,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
 
 ## consul
 
-**Required Telegraf plugin:** [Consul input plugin](/{{< latest "telegraf" >}}/plugins/#consul)
+**Required Telegraf plugin:** [Consul input plugin](/{{< latest "telegraf" >}}/plugins/#input-consul)
 
 `consul_http.json`
 
@@ -95,7 +95,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
 
 ## docker
 
-**Required Telegraf plugin:** [Docker input plugin](/{{< latest "telegraf" >}}/plugins/#docker)
+**Required Telegraf plugin:** [Docker input plugin](/{{< latest "telegraf" >}}/plugins/#input-docker)
 
 `docker.json`
 
@@ -115,7 +115,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
 
 ## elasticsearch
 
-**Required Telegraf plugin:** [Elasticsearch input plugin](/{{< latest "telegraf" >}}/plugins/#elasticsearch)
+**Required Telegraf plugin:** [Elasticsearch input plugin](/{{< latest "telegraf" >}}/plugins/#input-elasticsearch)
 
 `elasticsearch.json`
 
@@ -132,7 +132,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
 
 ## haproxy
 
-**Required Telegraf plugin:** [HAProxy input plugin](/{{< latest "telegraf" >}}/plugins/#haproxy)
+**Required Telegraf plugin:** [HAProxy input plugin](/{{< latest "telegraf" >}}/plugins/#input-haproxy)
 
 `haproxy.json`
 
@@ -154,7 +154,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
 
 ## iis
 
-**Required Telegraf plugin:** [Windows Performance Counters input plugin](/{{< latest "telegraf" >}}/plugins/#win_perf_counters)
+**Required Telegraf plugin:** [Windows Performance Counters input plugin](/{{< latest "telegraf" >}}/plugins/#input-win_perf_counters)
 
 `win_websvc.json`
 
@@ -162,7 +162,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
 
 ## influxdb
 
-**Required Telegraf plugin:** [InfluxDB input plugin](/{{< latest "telegraf" >}}/plugins/#influxdb)
+**Required Telegraf plugin:** [InfluxDB input plugin](/{{< latest "telegraf" >}}/plugins/#input-influxdb)
 
 `influxdb_database.json`
 
@@ -207,7 +207,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
 
 ## Memcached (`memcached`)
 
-**Required Telegraf plugin:** [Memcached input plugin](/{{< latest "telegraf" >}}/plugins/#memcached)
+**Required Telegraf plugin:** [Memcached input plugin](/{{< latest "telegraf" >}}/plugins/#input-memcached)
 
 `memcached.json`
 
@@ -227,7 +227,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
 
 ## mesos
 
-**Required Telegraf plugin:** [Mesos input plugin](/{{< latest "telegraf" >}}/plugins/#mesos)
+**Required Telegraf plugin:** [Mesos input plugin](/{{< latest "telegraf" >}}/plugins/#input-mesos)
 
 `mesos.json`
 
@@ -242,7 +242,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
 
 ## mongodb
 
-**Required Telegraf plugin:** [MongoDB input plugin](/{{< latest "telegraf" >}}/plugins/#mongodb)
+**Required Telegraf plugin:** [MongoDB input plugin](/{{< latest "telegraf" >}}/plugins/#input-mongodb)
 
 `mongodb.json`
 
@@ -254,7 +254,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
 
 ## mysql
 
-**Required Telegraf plugin:** [MySQL input plugin](/{{< latest "telegraf" >}}/plugins/#mysql)
+**Required Telegraf plugin:** [MySQL input plugin](/{{< latest "telegraf" >}}/plugins/#input-mysql)
 
 `mysql.json`
 
@@ -265,7 +265,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
 
 ## nginx
 
-**Required Telegraf plugin:** [NGINX input plugin](/{{< latest "telegraf" >}}/plugins/#nginx)
+**Required Telegraf plugin:** [NGINX input plugin](/{{< latest "telegraf" >}}/plugins/#input-nginx)
 
 `nginx.json`
 
@@ -276,7 +276,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
 
 ## nsq
 
-**Required Telegraf plugin:** [NSQ input plugin](/{{< latest "telegraf" >}}/plugins/#nsq)
+**Required Telegraf plugin:** [NSQ input plugin](/{{< latest "telegraf" >}}/plugins/#input-nsq)
 
 `nsq_channel.json`
 
@@ -297,7 +297,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
 
 ## phpfpm
 
-**Required Telegraf plugin:** [PHPfpm input plugin](/{{< latest "telegraf" >}}/plugins/#phpfpm)
+**Required Telegraf plugin:** [PHPfpm input plugin](/{{< latest "telegraf" >}}/plugins/#input-phpfpm)
 
 `phpfpm.json`
 
@@ -309,7 +309,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
 
 ## ping
 
-**Required Telegraf plugin:** [Ping input plugin](/{{< latest "telegraf" >}}/plugins/#ping)
+**Required Telegraf plugin:** [Ping input plugin](/{{< latest "telegraf" >}}/plugins/#input-ping)
 
 `ping.json`
 
@@ -318,7 +318,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
 
 ## postgresql
 
-**Required Telegraf plugin:** [PostgreSQL input plugin](/{{< latest "telegraf" >}}/plugins/#postgresql)
+**Required Telegraf plugin:** [PostgreSQL input plugin](/{{< latest "telegraf" >}}/plugins/#input-postgresql)
 
 `postgresql.json`
 
@@ -329,7 +329,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
 
 ## rabbitmq
 
-**Required Telegraf plugin:** [RabbitMQ input plugin](/{{< latest "telegraf" >}}/plugins/#rabbitmq)
+**Required Telegraf plugin:** [RabbitMQ input plugin](/{{< latest "telegraf" >}}/plugins/#input-rabbitmq)
 
 `rabbitmq.json`
 
@@ -340,7 +340,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
 
 ## redis
 
-**Required Telegraf plugin:** [Redis input plugin](/{{< latest "telegraf" >}}/plugins/#redis)
+**Required Telegraf plugin:** [Redis input plugin](/{{< latest "telegraf" >}}/plugins/#input-redis)
 
 
 `redis.json`
@@ -352,7 +352,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
 
 ## riak
 
-**Required Telegraf plugin:** [Riak input plugin](/{{< latest "telegraf" >}}/plugins/#riak)
+**Required Telegraf plugin:** [Riak input plugin](/{{< latest "telegraf" >}}/plugins/#input-riak)
 
 
 `riak.json`
@@ -371,7 +371,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
 
 ### cpu
 
-**Required Telegraf plugin:** [CPU input plugin](/{{< latest "telegraf" >}}/plugins/#cpu)
+**Required Telegraf plugin:** [CPU input plugin](/{{< latest "telegraf" >}}/plugins/#input-cpu)
 
 `cpu.json`
 
@@ -381,13 +381,13 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
 
 `disk.json`
 
-**Required Telegraf plugin:** [Disk input plugin](/{{< latest "telegraf" >}}/plugins/#disk)
+**Required Telegraf plugin:** [Disk input plugin](/{{< latest "telegraf" >}}/plugins/#input-disk)
 
   * "System - Disk used %"
 
 ### diskio
 
-**Required Telegraf plugin:** [DiskIO input plugin](/{{< latest "telegraf" >}}/plugins/#diskio)
+**Required Telegraf plugin:** [DiskIO input plugin](/{{< latest "telegraf" >}}/plugins/#input-diskio)
 
 `diskio.json`
 
@@ -396,7 +396,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
 
 ### mem
 
-**Required Telegraf plugin:** [Mem input plugin](/{{< latest "telegraf" >}}/plugins/#mem)
+**Required Telegraf plugin:** [Mem input plugin](/{{< latest "telegraf" >}}/plugins/#input-mem)
 
 `mem.json`
 
@@ -404,7 +404,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
 
 ### net
 
-**Required Telegraf plugin:** [Net input plugin](/{{< latest "telegraf" >}}/plugins/#net)
+**Required Telegraf plugin:** [Net input plugin](/{{< latest "telegraf" >}}/plugins/#input-net)
 
 `net.json`
 
@@ -413,7 +413,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
 
 ### netstat
 
-**Required Telegraf plugin:** [Netstat input plugin](/{{< latest "telegraf" >}}/plugins/#netstat)
+**Required Telegraf plugin:** [Netstat input plugin](/{{< latest "telegraf" >}}/plugins/#input-netstat)
 
 `netstat.json`
 
@@ -422,7 +422,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
 
 ### processes
 
-**Required Telegraf plugin:** [Processes input plugin](/{{< latest "telegraf" >}}/plugins/#processes)
+**Required Telegraf plugin:** [Processes input plugin](/{{< latest "telegraf" >}}/plugins/#input-processes)
 
 `processes.json`
 
@@ -430,7 +430,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
 
 ### procstat
 
-**Required Telegraf plugin:** [Procstat input plugin](/{{< latest "telegraf" >}}/plugins/#procstat)
+**Required Telegraf plugin:** [Procstat input plugin](/{{< latest "telegraf" >}}/plugins/#input-procstat)
 
 `procstat.json`
 
@@ -439,7 +439,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
 
 ### system
 
-**Required Telegraf plugin:** [Procstat input plugin](/{{< latest "telegraf" >}}/plugins/#procstat)
+**Required Telegraf plugin:** [Procstat input plugin](/{{< latest "telegraf" >}}/plugins/#input-procstat)
 
 `load.json`
 
@@ -447,7 +447,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
 
 ## varnish
 
-**Required Telegraf plugin:** [Varnish](/{{< latest "telegraf" >}}/plugins/#varnish)
+**Required Telegraf plugin:** [Varnish](/{{< latest "telegraf" >}}/plugins/#input-varnish)
 
 `varnish.json`
 
@@ -456,7 +456,7 @@ See [Telegraf configuration](https://github.com/influxdata/telegraf/blob/master/
 
 ## win_system
 
-**Required Telegraf plugin:** [Windows Performance Counters input plugin](/{{< latest "telegraf" >}}/plugins/#win_perf_counters)
+**Required Telegraf plugin:** [Windows Performance Counters input plugin](/{{< latest "telegraf" >}}/plugins/#input-win_perf_counters)
 
 `win_cpu.json`
 
diff --git a/content/chronograf/v1.8/about_the_project/cla.md b/content/chronograf/v1.8/about_the_project/cla.md
index 4be7081b5..b921f30e4 100644
--- a/content/chronograf/v1.8/about_the_project/cla.md
+++ b/content/chronograf/v1.8/about_the_project/cla.md
@@ -6,7 +6,8 @@ menu:
   chronograf_1_8:
     weight: 30
     parent: About the project
-    url: https://www.influxdata.com/legal/cla/
+    params:
+      url: https://www.influxdata.com/legal/cla/
 ---
 
 Before you can contribute to the Chronograf project, you need to submit the [InfluxData Contributor License Agreement (CLA)](https://www.influxdata.com/legal/cla/) available on the InfluxData main site.
diff --git a/content/chronograf/v1.8/about_the_project/contributing.md b/content/chronograf/v1.8/about_the_project/contributing.md
index efcb17698..8de232445 100644
--- a/content/chronograf/v1.8/about_the_project/contributing.md
+++ b/content/chronograf/v1.8/about_the_project/contributing.md
@@ -6,7 +6,8 @@ menu:
     name: Contribute
     weight: 20
     parent: About the project
-    url: https://github.com/influxdata/chronograf/blob/master/CONTRIBUTING.md
+    params:
+      url: https://github.com/influxdata/chronograf/blob/master/CONTRIBUTING.md
 ---
 
 See [Contributing to Chronograf](https://github.com/influxdata/chronograf/blob/master/CONTRIBUTING.md) in the Chronograf GitHub project to learn how you can contribute to the Chronograf project.
diff --git a/content/chronograf/v1.8/about_the_project/licenses.md b/content/chronograf/v1.8/about_the_project/licenses.md
index 0db15ab52..886d7ade2 100644
--- a/content/chronograf/v1.8/about_the_project/licenses.md
+++ b/content/chronograf/v1.8/about_the_project/licenses.md
@@ -6,7 +6,8 @@ menu:
     Name: Open source license
     weight: 40
     parent: About the project
-    url: https://github.com/influxdata/chronograf/blob/master/LICENSE
+    params:
+      url: https://github.com/influxdata/chronograf/blob/master/LICENSE
 ---
 
 The [open source license for Chronograf](https://github.com/influxdata/chronograf/blob/master/LICENSE) is available in the Chronograf GitHub project.
diff --git a/content/chronograf/v1.8/administration/prebuilt-dashboards.md b/content/chronograf/v1.8/administration/prebuilt-dashboards.md
index f8a8c0b76..6eec669bb 100644
--- a/content/chronograf/v1.8/administration/prebuilt-dashboards.md
+++ b/content/chronograf/v1.8/administration/prebuilt-dashboards.md
@@ -30,12 +30,12 @@ The Docker dashboard displays the following information:
 
 ### Plugins
 
-- [`docker` plugin](/{{< latest "telegraf" >}}/plugins/#docker)
-- [`disk` plugin](/{{< latest "telegraf" >}}/plugins/#disk)
-- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#mem)
-- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/#diskio)
-- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#system)
-- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/#cpu)
+- [`docker` plugin](/{{< latest "telegraf" >}}/plugins/#input-docker)
+- [`disk` plugin](/{{< latest "telegraf" >}}/plugins/#input-disk)
+- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#input-mem)
+- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/#input-diskio)
+- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#input-system)
+- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/#input-cpu)
 
 ## Kubernetes Node
 The Kubernetes Node dashboard displays the following information:
@@ -53,7 +53,7 @@ The Kubernetes Node dashboard displays the following information:
 - K8s - Kubelet Memory Bytes
 
 ### Plugins
-- [kubernetes](/{{< latest "telegraf" >}}/plugins/#kubernetes)
+- [kubernetes](/{{< latest "telegraf" >}}/plugins/#input-kubernetes)
 
 ## Kubernetes Overview
 The Kubernetes Node dashboard displays the following information:
@@ -72,7 +72,7 @@ The Kubernetes Node dashboard displays the following information:
 
 ### Plugins
 
-- [kubernetes](/{{< latest "telegraf" >}}/plugins/#kubernetes)
+- [kubernetes](/{{< latest "telegraf" >}}/plugins/#input-kubernetes)
 
 ## Kubernetes Pod
 The Kubernetes Pod dashboard displays the following information:
@@ -87,7 +87,7 @@ The Kubernetes Pod dashboard displays the following information:
 - K8s - Pod TX Bytes/Second
 
 ### Plugins
-- [kubernetes](/{{< latest "telegraf" >}}/plugins/#kubernetes)
+- [kubernetes](/{{< latest "telegraf" >}}/plugins/#input-kubernetes)
 
 ## Riak
 The Riak dashboard displays the following information:
@@ -101,7 +101,7 @@ The Riak dashboard displays the following information:
 - Riak - Read Repairs/Minute
 
 ### Plugins
-- [`riak` plugin](/{{< latest "telegraf" >}}/plugins/#riak)
+- [`riak` plugin](/{{< latest "telegraf" >}}/plugins/#input-riak)
 
 ## Consul
 The Consul dashboard displays the following information:
@@ -110,7 +110,7 @@ The Consul dashboard displays the following information:
 - Consul - Number of Warning Health Checks
 
 ### Plugins
-- [`consul` plugin](/{{< latest "telegraf" >}}/plugins/#consul)
+- [`consul` plugin](/{{< latest "telegraf" >}}/plugins/#input-consul)
 
 ## Consul Telemetry
 The Consul Telemetry dashboard displays the following information:
@@ -125,7 +125,7 @@ The Consul Telemetry dashboard displays the following information:
 - Consul - Number of Serf Events
 
 ### Plugins
-[`consul` plugin](/{{< latest "telegraf" >}}/plugins/#consul)
+[`consul` plugin](/{{< latest "telegraf" >}}/plugins/#input-consul)
 
 
 ## Mesos
@@ -140,7 +140,7 @@ The Mesos dashboard displays the following information:
 - Mesos Master Uptime
 
 ### Plugins
-- [`mesos` plugin](/{{< latest "telegraf" >}}/plugins/#mesos)
+- [`mesos` plugin](/{{< latest "telegraf" >}}/plugins/#input-mesos)
 
 ## RabbitMQ
 The RabbitMQ dashboard displays the following information:
@@ -151,7 +151,7 @@ The RabbitMQ dashboard displays the following information:
 
 ### Plugins
 
-- [`rabbitmq` plugin](/{{< latest "telegraf" >}}/plugins/#rabbitmq)
+- [`rabbitmq` plugin](/{{< latest "telegraf" >}}/plugins/#input-rabbitmq)
 
 ## System
 
@@ -170,14 +170,14 @@ The System dashboard displays the following information:
 
 ### Plugins
 
-- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#system)
-- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#mem)
-- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/#cpu)
-- [`disk` plugin](/{{< latest "telegraf" >}}/plugins/#disk)
-- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/#diskio)
-- [`net` plugin](/{{< latest "telegraf" >}}/plugins/#net)
-- [`processes` plugin](/{{< latest "telegraf" >}}/plugins/#processes)
-- [`swap` plugin](/{{< latest "telegraf" >}}/plugins/#swap)
+- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#input-system)
+- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#input-mem)
+- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/#input-cpu)
+- [`disk` plugin](/{{< latest "telegraf" >}}/plugins/#input-disk)
+- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/#input-diskio)
+- [`net` plugin](/{{< latest "telegraf" >}}/plugins/#input-net)
+- [`processes` plugin](/{{< latest "telegraf" >}}/plugins/#input-processes)
+- [`swap` plugin](/{{< latest "telegraf" >}}/plugins/#input-swap)
 
 
 
@@ -198,7 +198,7 @@ The VMware vSphere Overview dashboard gives an overview of your VMware vSphere C
   - VM CPU % Ready for :clustername:
 
 ### Plugins
-- [`vsphere` plugin](/{{< latest "telegraf" >}}/plugins/#vmware-vsphere)
+- [`vsphere` plugin](/{{< latest "telegraf" >}}/plugins/#input-vmware-vsphere)
 
 ## Apache
 The Apache dashboard displays the following information:
@@ -221,12 +221,12 @@ The Apache dashboard displays the following information:
 
 ### Plugins
 
-- [`apache` plugin](/{{< latest "telegraf" >}}/plugins/#apache)
-- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#system)
-- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#mem)
-- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/#diskio)
-- [`net` plugin](/{{< latest "telegraf" >}}/plugins/#net)
-- [`logparser` plugin](/{{< latest "telegraf" >}}/plugins/#logparser)
+- [`apache` plugin](/{{< latest "telegraf" >}}/plugins/#input-apache)
+- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#input-system)
+- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#input-mem)
+- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/#input-diskio)
+- [`net` plugin](/{{< latest "telegraf" >}}/plugins/#input-net)
+- [`logparser` plugin](/{{< latest "telegraf" >}}/plugins/#input-logparser)
 
 ## ElasticSearch
 The ElasticSearch dashboard displays the following information:
@@ -243,7 +243,7 @@ The ElasticSearch dashboard displays the following information:
 - ElasticSearch - JVM Heap Usage
 
 ### Plugins
-- [`elasticsearch` plugin](/{{< latest "telegraf" >}}/plugins/#elasticsearch)
+- [`elasticsearch` plugin](/{{< latest "telegraf" >}}/plugins/#input-elasticsearch)
 
 
 ## InfluxDB
@@ -272,12 +272,12 @@ The InfluxDB dashboard displays the following information:
 
 ### Plugins
 
-- [`influxdb` plugin](/{{< latest "telegraf" >}}/plugins/#influxdb)
-- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/#cpu)
-- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#system)
-- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#mem)
-- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/#diskio)
-- [`net` plugin](/{{< latest "telegraf" >}}/plugins/#net)
+- [`influxdb` plugin](/{{< latest "telegraf" >}}/plugins/#input-influxdb)
+- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/#input-cpu)
+- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#input-system)
+- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#input-mem)
+- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/#input-diskio)
+- [`net` plugin](/{{< latest "telegraf" >}}/plugins/#input-net)
 
 
 
@@ -299,7 +299,7 @@ The Memcached dashboard displays the following information:
 - Memcached - Evictions/10 Seconds
 
 ### Plugins
-- [`memcached` plugin](/{{< latest "telegraf" >}}/plugins/#memcached)
+- [`memcached` plugin](/{{< latest "telegraf" >}}/plugins/#input-memcached)
 
 
 ## NSQ
@@ -315,7 +315,7 @@ The NSQ dashboard displays the following information:
 - NSQ - Topic Egress
 
 ### Plugins
-- [`nsq` plugin](/{{< latest "telegraf" >}}/plugins/#nsq)
+- [`nsq` plugin](/{{< latest "telegraf" >}}/plugins/#input-nsq)
 
 ## PostgreSQL
 The PostgreSQL dashboard displays the following information:
@@ -340,11 +340,11 @@ The PostgreSQL dashboard displays the following information:
 
 ### Plugins
 
-- [`postgresql` plugin](/{{< latest "telegraf" >}}/plugins/#postgresql)
-- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#system)
-- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#mem)
-- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/#cpu)
-- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/#diskio)
+- [`postgresql` plugin](/{{< latest "telegraf" >}}/plugins/#input-postgresql)
+- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#input-system)
+- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#input-mem)
+- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/#input-cpu)
+- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/#input-diskio)
 
 
 ## HAProxy
@@ -367,7 +367,7 @@ The HAProxy dashboard displays the following information:
 - HAProxy - Backend Error Responses/Second
 
 ### Plugins
-- [`haproxy` plugin](/{{< latest "telegraf" >}}/plugins/#haproxy)
+- [`haproxy` plugin](/{{< latest "telegraf" >}}/plugins/#input-haproxy)
 
 
 ## NGINX
@@ -379,7 +379,7 @@ The NGINX dashboard displays the following information:
 - NGINX - Active Client State
 
 ### Plugins
-- [`nginx` plugin](/{{< latest "telegraf" >}}/plugins/#nginx)
+- [`nginx` plugin](/{{< latest "telegraf" >}}/plugins/#input-nginx)
 
 ## Redis
 The Redis dashboard displays the following information:
@@ -390,7 +390,7 @@ The Redis dashboard displays the following information:
 - Redis - Memory
 
 ### Plugins
-- [`redis` plugin](/{{< latest "telegraf" >}}/plugins/#redis)
+- [`redis` plugin](/{{< latest "telegraf" >}}/plugins/#input-redis)
 
 
 ## VMware vSphere VMs
@@ -406,7 +406,7 @@ The VMWare vSphere VMs dashboard gives an overview of your VMware vSphere virtua
 - Total Disk Latency for :vmname:
 
 ### Plugins
-- [`vsphere` plugin](/{{< latest "telegraf" >}}/plugins/#vsphere)
+- [`vsphere` plugin](/{{< latest "telegraf" >}}/plugins/#input-vsphere)
 
 ## VMware vSphere Hosts
 
@@ -422,7 +422,7 @@ The VMWare vSphere Hosts dashboard displays the following information:
 - Total Disk Latency for :esxhostname:
 
 ### Plugins
-- [`vsphere` plugin](/{{< latest "telegraf" >}}/plugins/#vsphere)
+- [`vsphere` plugin](/{{< latest "telegraf" >}}/plugins/#input-vsphere)
 
 ## PHPfpm
 The PHPfpm dashboard displays the following information:
@@ -433,7 +433,7 @@ The PHPfpm dashboard displays the following information:
 - PHPfpm - Max Children Reached
 
 ### Plugins
-- [`phpfpm` plugin](/{{< latest "telegraf" >}}/plugins/#nginx)
+- [`phpfpm` plugin](/{{< latest "telegraf" >}}/plugins/#input-nginx)
 
 ## Win System
 The Win System dashboard displays the following information:
@@ -445,7 +445,7 @@ The Win System dashboard displays the following information:
 - System - Load
 
 ### Plugins
-- [`win_services` plugin](/{{< latest "telegraf" >}}/plugins/#windows-services)
+- [`win_services` plugin](/{{< latest "telegraf" >}}/plugins/#input-windows-services)
 
 
 ## MySQL
@@ -472,9 +472,9 @@ The MySQL dashboard displays the following information:
 - InnoDB Data
 
 ### Plugins
-- [`mySQL` plugin](/{{< latest "telegraf" >}}/plugins/#mysql)
-- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#system)
-- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#mem)
+- [`mySQL` plugin](/{{< latest "telegraf" >}}/plugins/#input-mysql)
+- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#input-system)
+- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#input-mem)
 
 ## Ping
 The Ping dashboard displays the following information:
@@ -483,4 +483,4 @@ The Ping dashboard displays the following information:
 - Ping - Response Times (ms)
 
 ### Plugins
-- [`ping` plugin](/{{< latest "telegraf" >}}/plugins/#ping)
+- [`ping` plugin](/{{< latest "telegraf" >}}/plugins/#input-ping)
diff --git a/content/chronograf/v1.8/guides/using-precreated-dashboards.md b/content/chronograf/v1.8/guides/using-precreated-dashboards.md
index 779ba37ff..3b2118f4e 100644
--- a/content/chronograf/v1.8/guides/using-precreated-dashboards.md
+++ b/content/chronograf/v1.8/guides/using-precreated-dashboards.md
@@ -69,7 +69,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## apache
 
-**Required Telegraf plugin:** [Apache input plugin](/{{< latest "telegraf" >}}/plugins/#apache-http-server)
+**Required Telegraf plugin:** [Apache input plugin](/{{< latest "telegraf" >}}/plugins/#input-apache)
 
 `apache.json`
 
@@ -79,7 +79,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## consul
 
-**Required Telegraf plugin:** [Consul input plugin](/{{< latest "telegraf" >}}/plugins/#consul)
+**Required Telegraf plugin:** [Consul input plugin](/{{< latest "telegraf" >}}/plugins/#input-consul)
 
 `consul_http.json`
 
@@ -99,7 +99,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## docker
 
-**Required Telegraf plugin:** [Docker input plugin](/{{< latest "telegraf" >}}/plugins/#docker)
+**Required Telegraf plugin:** [Docker input plugin](/{{< latest "telegraf" >}}/plugins/#input-docker)
 
 `docker.json`
 
@@ -119,7 +119,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## elasticsearch
 
-**Required Telegraf plugin:** [Elasticsearch input plugin](/{{< latest "telegraf" >}}/plugins/#elasticsearch)
+**Required Telegraf plugin:** [Elasticsearch input plugin](/{{< latest "telegraf" >}}/plugins/#input-elasticsearch)
 
 `elasticsearch.json`
 
@@ -136,7 +136,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## haproxy
 
-**Required Telegraf plugin:** [HAProxy input plugin](/{{< latest "telegraf" >}}/plugins/#haproxy)
+**Required Telegraf plugin:** [HAProxy input plugin](/{{< latest "telegraf" >}}/plugins/#input-haproxy)
 
 `haproxy.json`
 
@@ -158,7 +158,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## iis
 
-**Required Telegraf plugin:** [Windows Performance Counters input plugin](/{{< latest "telegraf" >}}/plugins/#windows-performance-counters)
+**Required Telegraf plugin:** [Windows Performance Counters input plugin](/{{< latest "telegraf" >}}/plugins/#input-windows-performance-counters)
 
 `win_websvc.json`
 
@@ -166,7 +166,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## influxdb
 
-**Required Telegraf plugin:** [InfluxDB input plugin](/{{< latest "telegraf" >}}/plugins/#influxdb)
+**Required Telegraf plugin:** [InfluxDB input plugin](/{{< latest "telegraf" >}}/plugins/#input-influxdb)
 
 `influxdb_database.json`
 
@@ -211,7 +211,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## Memcached (`memcached`)
 
-**Required Telegraf plugin:** [Memcached input plugin](/{{< latest "telegraf" >}}/plugins/#memcached)
+**Required Telegraf plugin:** [Memcached input plugin](/{{< latest "telegraf" >}}/plugins/#input-memcached)
 
 `memcached.json`
 
@@ -231,7 +231,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## mesos
 
-**Required Telegraf plugin:** [Mesos input plugin](/{{< latest "telegraf" >}}/plugins/#mesos)
+**Required Telegraf plugin:** [Mesos input plugin](/{{< latest "telegraf" >}}/plugins/#input-mesos)
 
 `mesos.json`
 
@@ -246,7 +246,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## mongodb
 
-**Required Telegraf plugin:** [MongoDB input plugin](/{{< latest "telegraf" >}}/plugins/#mongodb)
+**Required Telegraf plugin:** [MongoDB input plugin](/{{< latest "telegraf" >}}/plugins/#input-mongodb)
 
 `mongodb.json`
 
@@ -258,7 +258,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## mysql
 
-**Required Telegraf plugin:** [MySQL input plugin](/{{< latest "telegraf" >}}/plugins/#mysql)
+**Required Telegraf plugin:** [MySQL input plugin](/{{< latest "telegraf" >}}/plugins/#input-mysql)
 
 `mysql.json`
 
@@ -269,7 +269,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## nginx
 
-**Required Telegraf plugin:** [NGINX input plugin](/{{< latest "telegraf" >}}/plugins/#nginx)
+**Required Telegraf plugin:** [NGINX input plugin](/{{< latest "telegraf" >}}/plugins/#input-nginx)
 
 `nginx.json`
 
@@ -280,7 +280,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## nsq
 
-**Required Telegraf plugin:** [NSQ input plugin](/{{< latest "telegraf" >}}/plugins/#nsq)
+**Required Telegraf plugin:** [NSQ input plugin](/{{< latest "telegraf" >}}/plugins/#input-nsq)
 
 `nsq_channel.json`
 
@@ -301,7 +301,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## phpfpm
 
-**Required Telegraf plugin:** [PHPfpm input plugin](/{{< latest "telegraf" >}}/plugins/#php-fpm)
+**Required Telegraf plugin:** [PHPfpm input plugin](/{{< latest "telegraf" >}}/plugins/#input-php-fpm)
 
 `phpfpm.json`
 
@@ -313,7 +313,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## ping
 
-**Required Telegraf plugin:** [Ping input plugin](/{{< latest "telegraf" >}}/plugins/#ping)
+**Required Telegraf plugin:** [Ping input plugin](/{{< latest "telegraf" >}}/plugins/#input-ping)
 
 `ping.json`
 
@@ -322,7 +322,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## postgresql
 
-**Required Telegraf plugin:** [PostgreSQL input plugin](/{{< latest "telegraf" >}}/plugins/#postgresql)
+**Required Telegraf plugin:** [PostgreSQL input plugin](/{{< latest "telegraf" >}}/plugins/#input-postgresql)
 
 `postgresql.json`
 
@@ -333,7 +333,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## rabbitmq
 
-**Required Telegraf plugin:** [RabbitMQ input plugin](/{{< latest "telegraf" >}}/plugins/#rabbitmq)
+**Required Telegraf plugin:** [RabbitMQ input plugin](/{{< latest "telegraf" >}}/plugins/#input-rabbitmq)
 
 `rabbitmq.json`
 
@@ -344,7 +344,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## redis
 
-**Required Telegraf plugin:** [Redis input plugin](/{{< latest "telegraf" >}}/plugins/#redis)
+**Required Telegraf plugin:** [Redis input plugin](/{{< latest "telegraf" >}}/plugins/#input-redis)
 
 
 `redis.json`
@@ -356,7 +356,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## riak
 
-**Required Telegraf plugin:** [Riak input plugin](/{{< latest "telegraf" >}}/plugins/#riak)
+**Required Telegraf plugin:** [Riak input plugin](/{{< latest "telegraf" >}}/plugins/#input-riak)
 
 
 `riak.json`
@@ -375,7 +375,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ### cpu
 
-**Required Telegraf plugin:** [CPU input plugin](/{{< latest "telegraf" >}}/plugins/#cpu)
+**Required Telegraf plugin:** [CPU input plugin](/{{< latest "telegraf" >}}/plugins/#input-cpu)
 
 `cpu.json`
 
@@ -385,13 +385,13 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 `disk.json`
 
-**Required Telegraf plugin:** [Disk input plugin](/{{< latest "telegraf" >}}/plugins/#disk)
+**Required Telegraf plugin:** [Disk input plugin](/{{< latest "telegraf" >}}/plugins/#input-disk)
 
   * "System - Disk used %"
 
 ### diskio
 
-**Required Telegraf plugin:** [DiskIO input plugin](/{{< latest "telegraf" >}}/plugins/#diskio)
+**Required Telegraf plugin:** [DiskIO input plugin](/{{< latest "telegraf" >}}/plugins/#input-diskio)
 
 `diskio.json`
 
@@ -400,7 +400,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ### mem
 
-**Required Telegraf plugin:** [Mem input plugin](/{{< latest "telegraf" >}}/plugins/#mem)
+**Required Telegraf plugin:** [Mem input plugin](/{{< latest "telegraf" >}}/plugins/#input-mem)
 
 `mem.json`
 
@@ -408,7 +408,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ### net
 
-**Required Telegraf plugin:** [Net input plugin](/{{< latest "telegraf" >}}/plugins/#net)
+**Required Telegraf plugin:** [Net input plugin](/{{< latest "telegraf" >}}/plugins/#input-net)
 
 `net.json`
 
@@ -417,7 +417,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ### netstat
 
-**Required Telegraf plugin:** [Netstat input plugin](/{{< latest "telegraf" >}}/plugins/#netstat)
+**Required Telegraf plugin:** [Netstat input plugin](/{{< latest "telegraf" >}}/plugins/#input-netstat)
 
 `netstat.json`
 
@@ -426,7 +426,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ### processes
 
-**Required Telegraf plugin:** [Processes input plugin](/{{< latest "telegraf" >}}/plugins/#processes)
+**Required Telegraf plugin:** [Processes input plugin](/{{< latest "telegraf" >}}/plugins/#input-processes)
 
 `processes.json`
 
@@ -434,7 +434,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ### procstat
 
-**Required Telegraf plugin:** [Procstat input plugin](/{{< latest "telegraf" >}}/plugins/#procstat)
+**Required Telegraf plugin:** [Procstat input plugin](/{{< latest "telegraf" >}}/plugins/#input-procstat)
 
 `procstat.json`
 
@@ -443,7 +443,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ### system
 
-**Required Telegraf plugin:** [Procstat input plugin](/{{< latest "telegraf" >}}/plugins/#procstat)
+**Required Telegraf plugin:** [Procstat input plugin](/{{< latest "telegraf" >}}/plugins/#input-procstat)
 
 `load.json`
 
@@ -451,7 +451,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## varnish
 
-**Required Telegraf plugin:** [Varnish](/{{< latest "telegraf" >}}/plugins/#varnish)
+**Required Telegraf plugin:** [Varnish](/{{< latest "telegraf" >}}/plugins/#input-varnish)
 
 `varnish.json`
 
@@ -460,7 +460,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## win_system
 
-**Required Telegraf plugin:** [Windows Performance Counters input plugin](/{{< latest "telegraf" >}}/plugins/#windows-performance-counters)
+**Required Telegraf plugin:** [Windows Performance Counters input plugin](/{{< latest "telegraf" >}}/plugins/#input-windows-performance-counters)
 
 `win_cpu.json`
 
diff --git a/content/chronograf/v1.9/about_the_project/cla.md b/content/chronograf/v1.9/about_the_project/cla.md
index 6e52e85d0..ea6d53e32 100644
--- a/content/chronograf/v1.9/about_the_project/cla.md
+++ b/content/chronograf/v1.9/about_the_project/cla.md
@@ -6,7 +6,8 @@ menu:
   chronograf_1_9:
     weight: 30
     parent: About the project
-    url: https://www.influxdata.com/legal/cla/
+    params:
+      url: https://www.influxdata.com/legal/cla/
 ---
 
 Before you can contribute to the Chronograf project, you need to submit the [InfluxData Contributor License Agreement (CLA)](https://www.influxdata.com/legal/cla/) available on the InfluxData main site.
diff --git a/content/chronograf/v1.9/about_the_project/contributing.md b/content/chronograf/v1.9/about_the_project/contributing.md
index 506455300..44e9cc21b 100644
--- a/content/chronograf/v1.9/about_the_project/contributing.md
+++ b/content/chronograf/v1.9/about_the_project/contributing.md
@@ -6,7 +6,8 @@ menu:
     name: Contribute
     weight: 20
     parent: About the project
-    url: https://github.com/influxdata/chronograf/blob/master/CONTRIBUTING.md
+    params:
+      url: https://github.com/influxdata/chronograf/blob/master/CONTRIBUTING.md
 ---
 
 See [Contributing to Chronograf](https://github.com/influxdata/chronograf/blob/master/CONTRIBUTING.md) in the Chronograf GitHub project to learn how you can contribute to the Chronograf project.
diff --git a/content/chronograf/v1.9/about_the_project/licenses.md b/content/chronograf/v1.9/about_the_project/licenses.md
index c5d14d69a..4215cbd96 100644
--- a/content/chronograf/v1.9/about_the_project/licenses.md
+++ b/content/chronograf/v1.9/about_the_project/licenses.md
@@ -6,7 +6,8 @@ menu:
     Name: Open source license
     weight: 40
     parent: About the project
-    url: https://github.com/influxdata/chronograf/blob/master/LICENSE
+    params:
+      url: https://github.com/influxdata/chronograf/blob/master/LICENSE
 ---
 
 The [open source license for Chronograf](https://github.com/influxdata/chronograf/blob/master/LICENSE) is available in the Chronograf GitHub project.
diff --git a/content/chronograf/v1.9/about_the_project/release-notes-changelog.md b/content/chronograf/v1.9/about_the_project/release-notes-changelog.md
index e15d25d6b..806e4121d 100644
--- a/content/chronograf/v1.9/about_the_project/release-notes-changelog.md
+++ b/content/chronograf/v1.9/about_the_project/release-notes-changelog.md
@@ -8,6 +8,68 @@ menu:
     parent: About the project
 ---
 
+## v1.9.4 [2022-03-28]
+
+### Features
+
+This release renames the Flux `Query Builder` to the Flux `Script Builder` (and adds improvements), and improves on Kapacitor integration.
+
+#### Flux Builder improvements
+
+- Rename the Flux `Query Builder` to the Flux `Script Builder`, and add new functionality including:
+  - Ability to load truncated tags and keys into the Flux Script Builder when connected to InfluxDB Cloud.
+  - Script Builder tag keys and tag values depend on a selected time range.
+- Make aggregation function selection optional.
+- Autocomplete builtin v object in Flux editor.
+- Add a warning before overriding the existing Flux Editor script.
+
+#### Kapacitor integration improvements
+
+Improved pagination and performance of the UI when you have large numbers of TICKscripts and Flux tasks.
+
+- Move Flux Tasks to a separate page under Alerting menu.
+- Add `TICKscripts Page` under Alerting menu.
+- Optimize Alert Rules API.
+- Open `Alert Rule Builder` from the TICKscripts page.
+- Remove `Manage Tasks` page, add `Alert Rules` page.
+- Add alert rule options to not send alert on state recovery and send regardless of state change.
+
+### Bug fixes
+
+- Respect `BASE_PATH` when serving API docs.
+- Propagate InfluxQL errors to UI.
+- Rename Flux Query to Flux Script.
+- Repair time zone selector on Host page.
+- Report correct Chronograf version.
+- Show failure reason on Queries page.
+- Reorder Alerting side menu.
+
+## v1.9.3 [2022-02-02]
+
+{{% note %}} **NOTE:** We did not release version 1.9.2 due to a bug that impacted communication between the browser’s main thread and background workers.  This bug has been fixed in the 1.9.3 release.
+{{% /note %}}
+
+### Features
+- Add ability to rename TICKscripts.
+- Add the following enhancements to the `InfluxDB Admin - Queries` tab:
+  - `CSV download` button. 
+  - Rename `Running` column to `Duration`.
+  - Add `Status` column. When hovering over the `Duration` column, status shows `Kill` confirmation button.
+  - Modify the `CSV` export to include the `Status` column.
+- Upgrade to use new `google.golang protobuf` library.
+
+### Bug Fixes
+- Ability to log the InfluxDB instance URL when a ping fails, making connection issues easier to identify.
+- Repair enforcement of one organization between multiple tabs.
+- Configure HTTP proxy from environment variables in HTTP clients. Improvements were made to:
+  - Token command within `chronoctl` 
+  - OAuth client
+  - Kapacitor client 
+  - Flux client
+
+#### Security
+- Upgrade `github.com/microcosm-cc/bluemonday` to resolve CVE-2021-42576.
+
 ## v1.9.1 [2021-10-08]
 
 ### Features
diff --git a/content/chronograf/v1.9/administration/prebuilt-dashboards.md b/content/chronograf/v1.9/administration/prebuilt-dashboards.md
index 2d7ed3000..606651a20 100644
--- a/content/chronograf/v1.9/administration/prebuilt-dashboards.md
+++ b/content/chronograf/v1.9/administration/prebuilt-dashboards.md
@@ -30,12 +30,12 @@ The Docker dashboard displays the following information:
 
 ### Plugins
 
-- [`docker` plugin](/{{< latest "telegraf" >}}/plugins/#docker)
-- [`disk` plugin](/{{< latest "telegraf" >}}/plugins/#disk)
-- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#mem)
-- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/#diskio)
-- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#system)
-- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/#cpu)
+- [`docker` plugin](/{{< latest "telegraf" >}}/plugins/#input-docker)
+- [`disk` plugin](/{{< latest "telegraf" >}}/plugins/#input-disk)
+- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#input-mem)
+- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/#input-diskio)
+- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#input-system)
+- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/#input-cpu)
 
 ## Kubernetes Node
 The Kubernetes Node dashboard displays the following information:
@@ -53,7 +53,7 @@ The Kubernetes Node dashboard displays the following information:
 - K8s - Kubelet Memory Bytes
 
 ### Plugins
-- [kubernetes](/{{< latest "telegraf" >}}/plugins/#kubernetes)
+- [kubernetes](/{{< latest "telegraf" >}}/plugins/#input-kubernetes)
 
 ## Kubernetes Overview
 The Kubernetes Node dashboard displays the following information:
@@ -72,7 +72,7 @@ The Kubernetes Node dashboard displays the following information:
 
 ### Plugins
 
-- [kubernetes](/{{< latest "telegraf" >}}/plugins/#kubernetes)
+- [kubernetes](/{{< latest "telegraf" >}}/plugins/#input-kubernetes)
 
 ## Kubernetes Pod
 The Kubernetes Pod dashboard displays the following information:
@@ -87,7 +87,7 @@ The Kubernetes Pod dashboard displays the following information:
 - K8s - Pod TX Bytes/Second
 
 ### Plugins
-- [kubernetes](/{{< latest "telegraf" >}}/plugins/#kubernetes)
+- [kubernetes](/{{< latest "telegraf" >}}/plugins/#input-kubernetes)
 
 ## Riak
 The Riak dashboard displays the following information:
@@ -101,7 +101,7 @@ The Riak dashboard displays the following information:
 - Riak - Read Repairs/Minute
 
 ### Plugins
-- [`riak` plugin](/{{< latest "telegraf" >}}/plugins/#riak)
+- [`riak` plugin](/{{< latest "telegraf" >}}/plugins/#input-riak)
 
 ## Consul
 The Consul dashboard displays the following information:
@@ -110,7 +110,7 @@ The Consul dashboard displays the following information:
 - Consul - Number of Warning Health Checks
 
 ### Plugins
-- [`consul` plugin](/{{< latest "telegraf" >}}/plugins/#consul)
+- [`consul` plugin](/{{< latest "telegraf" >}}/plugins/#input-consul)
 
 ## Consul Telemetry
 The Consul Telemetry dashboard displays the following information:
@@ -125,7 +125,7 @@ The Consul Telemetry dashboard displays the following information:
 - Consul - Number of Serf Events
 
 ### Plugins
-[`consul` plugin](/{{< latest "telegraf" >}}/plugins/#consul)
+[`consul` plugin](/{{< latest "telegraf" >}}/plugins/#input-consul)
 
 
 ## Mesos
@@ -140,7 +140,7 @@ The Mesos dashboard displays the following information:
 - Mesos Master Uptime
 
 ### Plugins
-- [`mesos` plugin](/{{< latest "telegraf" >}}/plugins/#mesos)
+- [`mesos` plugin](/{{< latest "telegraf" >}}/plugins/#input-mesos)
 
 ## RabbitMQ
 The RabbitMQ dashboard displays the following information:
@@ -151,7 +151,7 @@ The RabbitMQ dashboard displays the following information:
 
 ### Plugins
 
-- [`rabbitmq` plugin](/{{< latest "telegraf" >}}/plugins/#rabbitmq)
+- [`rabbitmq` plugin](/{{< latest "telegraf" >}}/plugins/#input-rabbitmq)
 
 ## System
 
@@ -170,14 +170,14 @@ The System dashboard displays the following information:
 
 ### Plugins
 
-- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#system)
-- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#mem)
-- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/#cpu)
-- [`disk` plugin](/{{< latest "telegraf" >}}/plugins/#disk)
-- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/#diskio)
-- [`net` plugin](/{{< latest "telegraf" >}}/plugins/#net)
-- [`processes` plugin](/{{< latest "telegraf" >}}/plugins/#processes)
-- [`swap` plugin](/{{< latest "telegraf" >}}/plugins/#swap)
+- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#input-system)
+- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#input-mem)
+- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/#input-cpu)
+- [`disk` plugin](/{{< latest "telegraf" >}}/plugins/#input-disk)
+- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/#input-diskio)
+- [`net` plugin](/{{< latest "telegraf" >}}/plugins/#input-net)
+- [`processes` plugin](/{{< latest "telegraf" >}}/plugins/#input-processes)
+- [`swap` plugin](/{{< latest "telegraf" >}}/plugins/#input-swap)
 
 
 
@@ -198,7 +198,7 @@ The VMware vSphere Overview dashboard gives an overview of your VMware vSphere C
   - VM CPU % Ready for :clustername:
 
 ### Plugins
-- [`vsphere` plugin](/{{< latest "telegraf" >}}/plugins/#vmware-vsphere)
+- [`vsphere` plugin](/{{< latest "telegraf" >}}/plugins/#input-vmware-vsphere)
 
 ## Apache
 The Apache dashboard displays the following information:
@@ -221,12 +221,12 @@ The Apache dashboard displays the following information:
 
 ### Plugins
 
-- [`apache` plugin](/{{< latest "telegraf" >}}/plugins/#apache)
-- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#system)
-- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#mem)
-- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/#diskio)
-- [`net` plugin](/{{< latest "telegraf" >}}/plugins/#net)
-- [`logparser` plugin](/{{< latest "telegraf" >}}/plugins/#logparser)
+- [`apache` plugin](/{{< latest "telegraf" >}}/plugins/#input-apache)
+- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#input-system)
+- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#input-mem)
+- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/#input-diskio)
+- [`net` plugin](/{{< latest "telegraf" >}}/plugins/#input-net)
+- [`logparser` plugin](/{{< latest "telegraf" >}}/plugins/#input-logparser)
 
 ## ElasticSearch
 The ElasticSearch dashboard displays the following information:
@@ -243,7 +243,7 @@ The ElasticSearch dashboard displays the following information:
 - ElasticSearch - JVM Heap Usage
 
 ### Plugins
-- [`elasticsearch` plugin](/{{< latest "telegraf" >}}/plugins/#elasticsearch)
+- [`elasticsearch` plugin](/{{< latest "telegraf" >}}/plugins/#input-elasticsearch)
 
 
 ## InfluxDB
@@ -272,12 +272,12 @@ The InfluxDB dashboard displays the following information:
 
 ### Plugins
 
-- [`influxdb` plugin](/{{< latest "telegraf" >}}/plugins/#influxdb)
-- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/#cpu)
-- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#system)
-- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#mem)
-- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/#diskio)
-- [`net` plugin](/{{< latest "telegraf" >}}/plugins/#net)
+- [`influxdb` plugin](/{{< latest "telegraf" >}}/plugins/#input-influxdb)
+- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/#input-cpu)
+- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#input-system)
+- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#input-mem)
+- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/#input-diskio)
+- [`net` plugin](/{{< latest "telegraf" >}}/plugins/#input-net)
 
 
 
@@ -299,7 +299,7 @@ The Memcached dashboard displays the following information:
 - Memcached - Evictions/10 Seconds
 
 ### Plugins
-- [`memcached` plugin](/{{< latest "telegraf" >}}/plugins/#memcached)
+- [`memcached` plugin](/{{< latest "telegraf" >}}/plugins/#input-memcached)
 
 
 ## NSQ
@@ -315,7 +315,7 @@ The NSQ dashboard displays the following information:
 - NSQ - Topic Egress
 
 ### Plugins
-- [`nsq` plugin](/{{< latest "telegraf" >}}/plugins/#nsq)
+- [`nsq` plugin](/{{< latest "telegraf" >}}/plugins/#input-nsq)
 
 ## PostgreSQL
 The PostgreSQL dashboard displays the following information:
@@ -340,11 +340,11 @@ The PostgreSQL dashboard displays the following information:
 
 ### Plugins
 
-- [`postgresql` plugin](/{{< latest "telegraf" >}}/plugins/#postgresql)
-- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#system)
-- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#mem)
-- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/#cpu)
-- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/#diskio)
+- [`postgresql` plugin](/{{< latest "telegraf" >}}/plugins/#input-postgresql)
+- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#input-system)
+- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#input-mem)
+- [`cpu` plugin](/{{< latest "telegraf" >}}/plugins/#input-cpu)
+- [`diskio` plugin](/{{< latest "telegraf" >}}/plugins/#input-diskio)
 
 
 ## HAProxy
@@ -367,7 +367,7 @@ The HAProxy dashboard displays the following information:
 - HAProxy - Backend Error Responses/Second
 
 ### Plugins
-- [`haproxy` plugin](/{{< latest "telegraf" >}}/plugins/#haproxy)
+- [`haproxy` plugin](/{{< latest "telegraf" >}}/plugins/#input-haproxy)
 
 
 ## NGINX
@@ -379,7 +379,7 @@ The NGINX dashboard displays the following information:
 - NGINX - Active Client State
 
 ### Plugins
-- [`nginx` plugin](/{{< latest "telegraf" >}}/plugins/#nginx)
+- [`nginx` plugin](/{{< latest "telegraf" >}}/plugins/#input-nginx)
 
 ## Redis
 The Redis dashboard displays the following information:
@@ -390,7 +390,7 @@ The Redis dashboard displays the following information:
 - Redis - Memory
 
 ### Plugins
-- [`redis` plugin](/{{< latest "telegraf" >}}/plugins/#redis)
+- [`redis` plugin](/{{< latest "telegraf" >}}/plugins/#input-redis)
 
 
 ## VMware vSphere VMs
@@ -406,7 +406,7 @@ The VMWare vSphere VMs dashboard gives an overview of your VMware vSphere virtua
 - Total Disk Latency for :vmname:
 
 ### Plugins
-- [`vsphere` plugin](/{{< latest "telegraf" >}}/plugins/#vsphere)
+- [`vsphere` plugin](/{{< latest "telegraf" >}}/plugins/#input-vsphere)
 
 ## VMware vSphere Hosts
 
@@ -422,7 +422,7 @@ The VMWare vSphere Hosts dashboard displays the following information:
 - Total Disk Latency for :esxhostname:
 
 ### Plugins
-- [`vsphere` plugin](/{{< latest "telegraf" >}}/plugins/#vsphere)
+- [`vsphere` plugin](/{{< latest "telegraf" >}}/plugins/#input-vsphere)
 
 ## PHPfpm
 The PHPfpm dashboard displays the following information:
@@ -433,7 +433,7 @@ The PHPfpm dashboard displays the following information:
 - PHPfpm - Max Children Reached
 
 ### Plugins
-- [`phpfpm` plugin](/{{< latest "telegraf" >}}/plugins/#nginx)
+- [`phpfpm` plugin](/{{< latest "telegraf" >}}/plugins/#input-nginx)
 
 ## Win System
 The Win System dashboard displays the following information:
@@ -445,7 +445,7 @@ The Win System dashboard displays the following information:
 - System - Load
 
 ### Plugins
-- [`win_services` plugin](/{{< latest "telegraf" >}}/plugins/#windows-services)
+- [`win_services` plugin](/{{< latest "telegraf" >}}/plugins/#input-windows-services)
 
 
 ## MySQL
@@ -472,9 +472,9 @@ The MySQL dashboard displays the following information:
 - InnoDB Data
 
 ### Plugins
-- [`mySQL` plugin](/{{< latest "telegraf" >}}/plugins/#mysql)
-- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#system)
-- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#mem)
+- [`mySQL` plugin](/{{< latest "telegraf" >}}/plugins/#input-mysql)
+- [`system` plugin](/{{< latest "telegraf" >}}/plugins/#input-system)
+- [`mem` plugin](/{{< latest "telegraf" >}}/plugins/#input-mem)
 
 ## Ping
 The Ping dashboard displays the following information:
@@ -483,4 +483,4 @@ The Ping dashboard displays the following information:
 - Ping - Response Times (ms)
 
 ### Plugins
-- [`ping` plugin](/{{< latest "telegraf" >}}/plugins/#ping)
+- [`ping` plugin](/{{< latest "telegraf" >}}/plugins/#input-ping)
diff --git a/content/chronograf/v1.9/guides/advanced-kapacitor.md b/content/chronograf/v1.9/guides/advanced-kapacitor.md
index dfc723f79..b49c4f9f0 100644
--- a/content/chronograf/v1.9/guides/advanced-kapacitor.md
+++ b/content/chronograf/v1.9/guides/advanced-kapacitor.md
@@ -7,7 +7,10 @@ menu:
     weight: 100
     parent: Guides
 related:
+  - /{{< latest "kapacitor" >}}/introduction/getting-started/
+  - /{{< latest "kapacitor" >}}/working/kapa-and-chrono/
   - /{{< latest "kapacitor" >}}/working/flux/
+
 ---
 
 Chronograf provides a user interface for [Kapacitor](/{{< latest "kapacitor" >}}/),
@@ -41,6 +44,7 @@ In the Databases tab:
     _See [supported duration units](/{{< latest "influxdb" "v1" >}}/query_language/spec/#duration-units)._
 4.  Click **Save**.
 
+
 If you set the retention policy's duration to one hour (`1h`), InfluxDB
 automatically deletes any alerts that occurred before the past hour.
 
@@ -51,29 +55,33 @@ automatically deletes any alerts that occurred before the past hour.
 
 ### Manage Kapacitor TICKscripts
 
-Chronograf lets you manage Kapacitor TICKscript tasks created in Kapacitor or in
-Chronograf when [creating a Chronograf alert rule](/chronograf/v1.9/guides/create-alert-rules/).
+Chronograf lets you view and manage all Kapacitor TICKscripts for a selected Kapacitor subscription using the **TICKscripts** page.  
 
-To manage Kapacitor TICKscript tasks in Chronograf, click
-**{{< icon "alert" "v2">}} Alerts** in the left navigation bar.
-On this page, you can:
+1. To manage Kapacitor TICKscripts in Chronograf, click
+**{{< icon "alert" "v2">}} Alerting** in the left navigation bar and select **TICKscripts**. 
+Do one or more of the following:
 
-- View Kapacitor TICKscript tasks.
-- View TICKscript task activity.
-- Create new TICKscript tasks.
-- Update TICKscript tasks.
-- Enable and disable TICKscript tasks.
-- Delete TICKscript tasks.
+    - View Kapacitor TICKscript tasks. You can view up to 100 TICKscripts at a time. If you have more than 100 TICKscripts, the list will be paginated at the bottom of the page. You can also filter your TICKscripts by name.  
+    - View TICKscript task type.
+    - Enable and disable TICKscript tasks.
+    - Create new TICKscript tasks. 
+    - Update TICKscript tasks.
+    - Rename a TICKscript. Note, renaming a TICKscript updates the `var name` variable within the TICKscript.
+    - Delete TICKscript tasks.
+    - Create alerts using the Alert Rule Builder.  See [Configure Chronograf alert rules](/chronograf/v1.9/guides/create-alert-rules/#configure-chronograf-alert-rules).
+
+2. Click **Exit** when finished.
 
 ### Manage Kapacitor Flux tasks
 **Kapacitor 1.6+** supports Flux tasks.
-Chronograf lets you view and manage [Kapacitor Flux tasks](/{{< latest "kapacitor" >}}/working/flux/).
+Chronograf lets you view and manage Flux tasks for a selected Kapacitor subscription using the **Flux Tasks** page.  
 
 To manage Kapacitor Flux tasks in Chronograf, click
-**{{< icon "alert" "v2">}} Alerts** in the left navigation bar.
-On this page, you can:
+**{{< icon "alert" "v2">}} Alerting** in the left navigation bar and select the **Flux Tasks** option. Do one or more of the following:
 
-- View Kapacitor Flux tasks.
-- View Kapacitor Flux task activity.
-- Enable and disable Kapacitor Flux tasks.
-- Delete Kapacitor Flux tasks.
+  - View and filter Kapacitor Flux tasks by name.
+  - View Kapacitor Flux task activity.
+  - Enable and disable Kapacitor Flux tasks.
+  - Delete Kapacitor Flux tasks.
+
+For more information on Flux tasks and Kapacitor see [Use Flux tasks with Kapacitor](/{{< latest "kapacitor" >}}/working/flux/).
\ No newline at end of file
diff --git a/content/chronograf/v1.9/guides/create-alert-rules.md b/content/chronograf/v1.9/guides/create-alert-rules.md
index 3a0e3e629..27fe05bc4 100644
--- a/content/chronograf/v1.9/guides/create-alert-rules.md
+++ b/content/chronograf/v1.9/guides/create-alert-rules.md
@@ -22,141 +22,74 @@ Common alerting use cases that can be managed using Chronograf include:
 * Deadman switches.
 
 Complex alerts and other tasks can be defined directly in Kapacitor as TICKscripts, but can be viewed and managed within Chronograf.
-
-This guide walks through creating a Chronograf alert rule that sends an alert message to an existing [Slack](https://slack.com/) channel whenever your idle CPU usage crosses the 80% threshold.
+To learn about managing Kapacitor TICKscripts in Chronograf, see [Manage Kapacitor TICKscripts](/{{< latest "chronograf" >}}/guides/advanced-kapacitor/#manage-kapacitor-tickscripts).
 
 ## Requirements
 
-[Getting started with Chronograf](/chronograf/v1.9/introduction/getting-started/) offers step-by-step instructions for each of the following requirements:
+[Get started with Chronograf](/{{< latest "chronograf" >}}/introduction/getting-started/) offers step-by-step instructions for each of the following requirements:
 
-* Downloaded and install the entire TICKstack (Telegraf, InfluxDB, Chronograf, and Kapacitor).
-* Configure Telegraf to collect data using the InfluxDB [system statistics](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/system) input plugin and write data to your InfluxDB instance.
-* [Create a Kapacitor connection in Chronograf](/chronograf/v1.9/introduction/installation/#connect-chronograf-to-kapacitor).
-* Slack is available and configured as an event handler in Chronograf. See [Configuring Chronograf alert endpoints](/chronograf/v1.9/guides/configuring-alert-endpoints/) for detailed configuration instructions.
+* Download and install the entire TICKstack (Telegraf, InfluxDB, Chronograf, and Kapacitor).
+* [Create a Kapacitor connection in Chronograf](/{{< latest "chronograf" >}}/introduction/installation/#connect-chronograf-to-kapacitor).
 
-## Configure Chronograf alert rules
+## Manage Chronograf alert rules
 
-Navigate to the **Manage Tasks** page under **Alerting** in the left navigation, then click **+ Build Alert Rule** in the top right corner.
+Chronograf lets you create and manage Kapacitor alert rules. To manage alert rules:
 
-![Navigate to Manage Tasks](/img/chronograf/1-6-alerts-manage-tasks-nav.png)
+1. Click on  **{{< icon "alert" "v2">}} Alerting** in the left navigation bar and select **Alert Rules**.
+2. Do one of the following:
+    - [Create an alert rule](#create-an-alert-rule)
+    - [View alert history](#view-alert-history)
+    - [Enable and disable alert rules](#enable-and-disable-alert-rules)
+    - [Delete alert rules](#delete-alert-rules)
 
-The **Manage Tasks** page is used to create and edit your Chronograf alert rules.
-The steps below guide you through the process of creating a Chronograf alert rule.
+To create and manage alert rules in Chronograf, click on
+**{{< icon "alert" "v2">}} Alerting** in the left navigation bar and select **Alert Rules**.
+Do one of the following:
 
-![Empty Rule Configuration](/img/chronograf/1-6-alerts-rule-builder.png)
+  - View alert rules.
+  - Enable and disable alert rules.
+  - Delete alert rules.
+  - Create new alert rules using the **Alert Rule Builder**.
 
-### Step 1: Name the alert rule
+## Create an alert rule
 
-Under **Name this Alert Rule** provide a name for the alert.
-For this example, use "Idle CPU Usage" as your alert name.
+From the **Alert Rules** page in Chronograf:
 
-### Step 2: Select the alert type
+1. Click **+ Build Alert Rule**. 
 
-Choose from three alert types under the **Alert Types** section of the Rule Configuration page:
+1. Name the alert rule.
 
-_**Threshold**_  
-Alert if data crosses a boundary.
+2. Choose the alert type:
+    -  `Threshold` - alert if data crosses a boundary.
+    -  `Relative` - alert if data changes relative to data in a different time range.
+    -  `Deadman` - alert if InfluxDB receives no relevant data for a specified time duration.
 
-_**Relative**_  
-Alert if data changes relative to data in a different time range.
+3. Select the time series data to use in the alert rule.
+    - Navigate through databases, measurements, tags, and fields to select all relevant data.
 
-_**Deadman**_  
-Alert if InfluxDB receives no relevant data for a specified time duration.
+4. Define the rule conditions. Condition options are determined by the alert type.
 
-For this example, select the **Threshold** alert type.
+5. Select and configure the alert handler.
+    - The alert handler determines where the system sends the alert (the event handler).
+    - Chronograf supports several event handlers and each handler has unique configurable options.
+    - Multiple alert handlers can be added to send alerts to multiple endpoints.
 
-### Step 3: Select the time series data
+6. Configure the alert message.
+    - The alert message is the text that accompanies an alert.
+    - Alert messages are templates that have access to alert data.
+    - Available templates appear below the message text field.
+    - As you type your alert message, clicking the data templates will insert them at the end of whatever text has been entered.
 
-Choose the time series data you want the Chronograf alert rule to use.
-Navigate through databases, measurements, fields, and tags to select the relevant data.
+7. Click **Save Rule**.
 
-In this example, select the `telegraf` [database](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#database), the `autogen` [retention policy](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#retention-policy-rp), the `cpu` [measurement](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#measurement), and the `usage_idle` [field](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#field).
+## View alert history
 
-![Select your data](/img/chronograf/1-6-alerts-time-series.png)
+Chronograf lets you view your alert history on the **Alert History** page.
 
-### Step 4: Define the rule condition
+To view a history of your alerts, click on
+**{{< icon "alert" "v2">}} Alerting** in the left navigation bar and select **Alert History**. 
+Do one of the following:
 
-Define the threshold condition.
-Condition options are determined by the [alert type](#step-2-select-the-alert-type).
-For this example, the alert conditions are if `usage_idle` is less than `80`.
-
-![Create a condition](/img/chronograf/1-6-alerts-conditions.png)
-
-The graph shows a preview of the relevant data and the threshold number.
-By default, the graph shows data from the past 15 minutes.
-Adjusting the graph's time range is helpful when determining a reasonable threshold number based on your data.
-
-{{% note %}}
-We set the threshold number to `80` for demonstration purposes.
-Setting the threshold for idle CPU usage to a high number ensures that we'll be able to see the alert in action.
-In practice, you'd set the threshold number to better match the patterns in your data and your alerting needs.
-{{% /note %}}
-
-### Step 5: Select and configure the alert handler
-
-The **Alert Handler** section determines where the system sends the alert (the event handler)
-Chronograf supports several event handlers.
-Each handler has unique configurable options.
-
-For this example, choose the **slack** alert handler and enter the desired options.
-
-![Select the alert handler](/img/chronograf/1-6-alerts-configure-handlers.png)
-
-{{% note %}}
-Multiple alert handlers can be added to send alerts to multiple endpoints.
-{{% /note %}}
-
-### Step 6: Configure the alert message
-
-The alert message is the text that accompanies an alert.
-Alert messages are templates that have access to alert data.
-Available data templates appear below the message text field.
-As you type your alert message, clicking the data templates will insert them at end of whatever text has been entered.
-
-In this example, use the alert message, `Your idle CPU usage is {{.Level}} at {{ index .Fields "value" }}.`.
-
-![Specify event handler and alert message](/img/chronograf/1-6-alerts-message.png)
-
-*View the Kapacitor documentation for more information about [message template data](/{{< latest "kapacitor" >}}/nodes/alert_node/#message).*
-
-### Step 7: Save the alert rule
-
-Click **Save Rule** in the top right corner and navigate to the **Manage Tasks** page to see your rule.
-Notice that you can easily enable and disable the rule by toggling the checkbox in the **Enabled** column.
-
-![See the alert rule](/img/chronograf/1-6-alerts-view-rules.png)
-
-Next, move on to the section below to experience your alert rule in action.
-
-## View alerts in practice
-
-### Step 1: Create some load on your system
-
-The purpose of this step is to generate enough load on your system to trigger an alert.
-More specifically, your idle CPU usage must dip below `80%`.
-On the machine that's running Telegraf, enter the following command in the terminal to start some `while` loops:
-
-```
-while true; do i=0; done
-```
-
-Let it run for a few seconds or minutes before terminating it.
-On most systems, kill the script by using `Ctrl+C`.
-
-### Step 2: View the alerts
-
-Go to the Slack channel that you specified in the previous section.
-In this example, it's the `#chronocats` channel.
-
-Assuming the first step was successful, `#ohnos` should reveal at least two alert messages:
-
-* The first alert message indicates that your idle CPU usage was `CRITICAL`, meaning it dipped below `80%`.
-* The second alert message indicates that your idle CPU usage returned to an `OK` level of `80%` or above.
-
-![See the alerts](/img/chronograf/1-6-alerts-slack-notifications.png)
-
-You can also see alerts on the **Alert History** page available under **Alerting** in the left navigation.
-
-![Chronograf alert history](/img/chronograf/1-6-alerts-history.png)
-
-That's it! You've successfully used Chronograf to configure an alert rule to monitor your idle CPU usage and send notifications to Slack.
+  - View a history of all triggered alerts.
+  - Filter alert history by type.  
+  - View alert history for a specified time range.  
diff --git a/content/chronograf/v1.9/guides/querying-data.md b/content/chronograf/v1.9/guides/querying-data.md
index 8e82c8bad..d6e63bfc0 100644
--- a/content/chronograf/v1.9/guides/querying-data.md
+++ b/content/chronograf/v1.9/guides/querying-data.md
@@ -48,33 +48,20 @@ For more information, see [InfluxQL support](/influxdb/cloud/query-data/influxql
 
 Flux is InfluxData's new functional data scripting language designed for querying, analyzing, and acting on time series data. To learn more about Flux, see [Getting started with Flux](/{{< latest "influxdb" "v2" >}}/query-data/get-started).
 
-1. Open the Data Explorer and click **Add a Query**.
-2. To the right of the source dropdown above the graph placeholder, select **Flux** as the source type.
- The **Schema**, **Functions**, and **Script** panes appear.
-3. Use the **Schema** pane to explore your available data. Click the **+** sign next to a bucket name to expand its content.
-4. Use the **Functions** pane to view details about the available Flux functions.
-5. Use the **Script** pane to enter your Flux query.
+1. Open the Data Explorer by clicking **Explore** in the left navigation bar.
+2. Select **Flux** as the source type.
+3. Click **Script Builder**.
+4. The **Schema**, **Script**, and **Flux Functions** panes appear.
+    - Use the **Schema** pane to explore your available data. Click the **{{< icon "plus" >}}** sign next to a bucket name to expand its content. 
+    - Use the **Script** pane to enter and view your Flux script.
+    - Use the **Flux Functions** pane to view details about the available Flux functions.
+5. To get started building a new script, click **Script Builder**. Using the Flux script builder, you can select a bucket, measurements and tags, fields and an aggregate function. Click **{{< icon "plus" >}} Load More** to expand any truncated lists.  You can also choose a variety of time ranges on your schema data.
+6. When you are finished creating your script, click **Submit**.
+7. Click **Script Editor** to view and edit your query.
+8. If you make changes to the script using the **Script Builder**, you will receive a message when clicking **Submit** warning you
+that submitting changes will override the script in the Flux editor, and that the script cannot be recovered.
 
-    * To get started with your query, click the **Script Wizard**. In the wizard, you can select a bucket, measurement, fields and an aggregate.
-
-      <img src="/img/chronograf/1-7-flux-script-wizard.png" style="width:100%; max-width:400px; margin:2em 0; display:block;">
-
-    For example, if you make the above selections, the wizard inserts the following script:
-
-    ```js
-    from(bucket: "telegraf/autogen")
-      |> range(start: dashboardTime)
-      |> filter(fn: (r) => r._measurement == "cpu" and (r._field == "usage_system"))
-      |> window(every: autoInterval)
-      |> toFloat()
-      |> percentile(percentile: 0.95)
-      |> group(except: ["_time", "_start", "_stop", "_value"])
-    ```
-    * Alternatively, you can enter your entire script manually.
-
-6. Click **Run Script** in the top bar of the **Script** pane. You can then preview your graph in the above pane.
-
-## Visualize your query
+ ## Visualize your query
 
 Select the **Visualization** tab at the top of the **Data Explorer**. For details about all of the available visualization options, see [Visualization types in Chronograf](/chronograf/v1.9/guides/visualization-types/).
 
diff --git a/content/chronograf/v1.9/guides/using-precreated-dashboards.md b/content/chronograf/v1.9/guides/using-precreated-dashboards.md
index 4826a4a88..956495a62 100644
--- a/content/chronograf/v1.9/guides/using-precreated-dashboards.md
+++ b/content/chronograf/v1.9/guides/using-precreated-dashboards.md
@@ -71,7 +71,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## apache
 
-**Required Telegraf plugin:** [Apache input plugin](/{{< latest "telegraf" >}}/plugins/#apache-http-server)
+**Required Telegraf plugin:** [Apache input plugin](/{{< latest "telegraf" >}}/plugins/#input-apache)
 
 `apache.json`
 
@@ -81,7 +81,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## consul
 
-**Required Telegraf plugin:** [Consul input plugin](/{{< latest "telegraf" >}}/plugins/#consul)
+**Required Telegraf plugin:** [Consul input plugin](/{{< latest "telegraf" >}}/plugins/#input-consul)
 
 `consul_http.json`
 
@@ -101,7 +101,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## docker
 
-**Required Telegraf plugin:** [Docker input plugin](/{{< latest "telegraf" >}}/plugins/#docker)
+**Required Telegraf plugin:** [Docker input plugin](/{{< latest "telegraf" >}}/plugins/#input-docker)
 
 `docker.json`
 
@@ -121,7 +121,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## elasticsearch
 
-**Required Telegraf plugin:** [Elasticsearch input plugin](/{{< latest "telegraf" >}}/plugins/#elasticsearch)
+**Required Telegraf plugin:** [Elasticsearch input plugin](/{{< latest "telegraf" >}}/plugins/#input-elasticsearch)
 
 `elasticsearch.json`
 
@@ -138,7 +138,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## haproxy
 
-**Required Telegraf plugin:** [HAProxy input plugin](/{{< latest "telegraf" >}}/plugins/#haproxy)
+**Required Telegraf plugin:** [HAProxy input plugin](/{{< latest "telegraf" >}}/plugins/#input-haproxy)
 
 `haproxy.json`
 
@@ -160,7 +160,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## iis
 
-**Required Telegraf plugin:** [Windows Performance Counters input plugin](/{{< latest "telegraf" >}}/plugins/#windows-performance-counters)
+**Required Telegraf plugin:** [Windows Performance Counters input plugin](/{{< latest "telegraf" >}}/plugins/#input-windows-performance-counters)
 
 `win_websvc.json`
 
@@ -168,7 +168,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## influxdb
 
-**Required Telegraf plugin:** [InfluxDB input plugin](/{{< latest "telegraf" >}}/plugins/#influxdb)
+**Required Telegraf plugin:** [InfluxDB input plugin](/{{< latest "telegraf" >}}/plugins/#input-influxdb)
 
 `influxdb_database.json`
 
@@ -213,7 +213,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## Memcached (`memcached`)
 
-**Required Telegraf plugin:** [Memcached input plugin](/{{< latest "telegraf" >}}/plugins/#memcached)
+**Required Telegraf plugin:** [Memcached input plugin](/{{< latest "telegraf" >}}/plugins/#input-memcached)
 
 `memcached.json`
 
@@ -233,7 +233,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## mesos
 
-**Required Telegraf plugin:** [Mesos input plugin](/{{< latest "telegraf" >}}/plugins/#mesos)
+**Required Telegraf plugin:** [Mesos input plugin](/{{< latest "telegraf" >}}/plugins/#input-mesos)
 
 `mesos.json`
 
@@ -248,7 +248,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## mongodb
 
-**Required Telegraf plugin:** [MongoDB input plugin](/{{< latest "telegraf" >}}/plugins/#mongodb)
+**Required Telegraf plugin:** [MongoDB input plugin](/{{< latest "telegraf" >}}/plugins/#input-mongodb)
 
 `mongodb.json`
 
@@ -260,7 +260,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## mysql
 
-**Required Telegraf plugin:** [MySQL input plugin](/{{< latest "telegraf" >}}/plugins/#mysql)
+**Required Telegraf plugin:** [MySQL input plugin](/{{< latest "telegraf" >}}/plugins/#input-mysql)
 
 `mysql.json`
 
@@ -271,7 +271,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## nginx
 
-**Required Telegraf plugin:** [NGINX input plugin](/{{< latest "telegraf" >}}/plugins/#nginx)
+**Required Telegraf plugin:** [NGINX input plugin](/{{< latest "telegraf" >}}/plugins/#input-nginx)
 
 `nginx.json`
 
@@ -282,7 +282,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## nsq
 
-**Required Telegraf plugin:** [NSQ input plugin](/{{< latest "telegraf" >}}/plugins/#nsq)
+**Required Telegraf plugin:** [NSQ input plugin](/{{< latest "telegraf" >}}/plugins/#input-nsq)
 
 `nsq_channel.json`
 
@@ -303,7 +303,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## phpfpm
 
-**Required Telegraf plugin:** [PHPfpm input plugin](/{{< latest "telegraf" >}}/plugins/#php-fpm)
+**Required Telegraf plugin:** [PHPfpm input plugin](/{{< latest "telegraf" >}}/plugins/#input-php-fpm)
 
 `phpfpm.json`
 
@@ -315,7 +315,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## ping
 
-**Required Telegraf plugin:** [Ping input plugin](/{{< latest "telegraf" >}}/plugins/#ping)
+**Required Telegraf plugin:** [Ping input plugin](/{{< latest "telegraf" >}}/plugins/#input-ping)
 
 `ping.json`
 
@@ -324,7 +324,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## postgresql
 
-**Required Telegraf plugin:** [PostgreSQL input plugin](/{{< latest "telegraf" >}}/plugins/#postgresql)
+**Required Telegraf plugin:** [PostgreSQL input plugin](/{{< latest "telegraf" >}}/plugins/#input-postgresql)
 
 `postgresql.json`
 
@@ -335,7 +335,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## rabbitmq
 
-**Required Telegraf plugin:** [RabbitMQ input plugin](/{{< latest "telegraf" >}}/plugins/#rabbitmq)
+**Required Telegraf plugin:** [RabbitMQ input plugin](/{{< latest "telegraf" >}}/plugins/#input-rabbitmq)
 
 `rabbitmq.json`
 
@@ -346,7 +346,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## redis
 
-**Required Telegraf plugin:** [Redis input plugin](/{{< latest "telegraf" >}}/plugins/#redis)
+**Required Telegraf plugin:** [Redis input plugin](/{{< latest "telegraf" >}}/plugins/#input-redis)
 
 
 `redis.json`
@@ -358,7 +358,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## riak
 
-**Required Telegraf plugin:** [Riak input plugin](/{{< latest "telegraf" >}}/plugins/#riak)
+**Required Telegraf plugin:** [Riak input plugin](/{{< latest "telegraf" >}}/plugins/#input-riak)
 
 
 `riak.json`
@@ -377,7 +377,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ### cpu
 
-**Required Telegraf plugin:** [CPU input plugin](/{{< latest "telegraf" >}}/plugins/#cpu)
+**Required Telegraf plugin:** [CPU input plugin](/{{< latest "telegraf" >}}/plugins/#input-cpu)
 
 `cpu.json`
 
@@ -387,13 +387,13 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 `disk.json`
 
-**Required Telegraf plugin:** [Disk input plugin](/{{< latest "telegraf" >}}/plugins/#disk)
+**Required Telegraf plugin:** [Disk input plugin](/{{< latest "telegraf" >}}/plugins/#input-disk)
 
   * "System - Disk used %"
 
 ### diskio
 
-**Required Telegraf plugin:** [DiskIO input plugin](/{{< latest "telegraf" >}}/plugins/#diskio)
+**Required Telegraf plugin:** [DiskIO input plugin](/{{< latest "telegraf" >}}/plugins/#input-diskio)
 
 `diskio.json`
 
@@ -402,7 +402,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ### mem
 
-**Required Telegraf plugin:** [Mem input plugin](/{{< latest "telegraf" >}}/plugins/#mem)
+**Required Telegraf plugin:** [Mem input plugin](/{{< latest "telegraf" >}}/plugins/#input-mem)
 
 `mem.json`
 
@@ -410,7 +410,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ### net
 
-**Required Telegraf plugin:** [Net input plugin](/{{< latest "telegraf" >}}/plugins/#net)
+**Required Telegraf plugin:** [Net input plugin](/{{< latest "telegraf" >}}/plugins/#input-net)
 
 `net.json`
 
@@ -419,7 +419,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ### netstat
 
-**Required Telegraf plugin:** [Netstat input plugin](/{{< latest "telegraf" >}}/plugins/#netstat)
+**Required Telegraf plugin:** [Netstat input plugin](/{{< latest "telegraf" >}}/plugins/#input-netstat)
 
 `netstat.json`
 
@@ -428,7 +428,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ### processes
 
-**Required Telegraf plugin:** [Processes input plugin](/{{< latest "telegraf" >}}/plugins/#processes)
+**Required Telegraf plugin:** [Processes input plugin](/{{< latest "telegraf" >}}/plugins/#input-processes)
 
 `processes.json`
 
@@ -436,7 +436,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ### procstat
 
-**Required Telegraf plugin:** [Procstat input plugin](/{{< latest "telegraf" >}}/plugins/#procstat)
+**Required Telegraf plugin:** [Procstat input plugin](/{{< latest "telegraf" >}}/plugins/#input-procstat)
 
 `procstat.json`
 
@@ -445,7 +445,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ### system
 
-**Required Telegraf plugin:** [Procstat input plugin](/{{< latest "telegraf" >}}/plugins/#procstat)
+**Required Telegraf plugin:** [Procstat input plugin](/{{< latest "telegraf" >}}/plugins/#input-procstat)
 
 `load.json`
 
@@ -453,7 +453,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## varnish
 
-**Required Telegraf plugin:** [Varnish](/{{< latest "telegraf" >}}/plugins/#varnish)
+**Required Telegraf plugin:** [Varnish](/{{< latest "telegraf" >}}/plugins/#input-varnish)
 
 `varnish.json`
 
@@ -462,7 +462,7 @@ Enable and disable apps in your Telegraf configuration file (by default, `/etc/t
 
 ## win_system
 
-**Required Telegraf plugin:** [Windows Performance Counters input plugin](/{{< latest "telegraf" >}}/plugins/#windows-performance-counters)
+**Required Telegraf plugin:** [Windows Performance Counters input plugin](/{{< latest "telegraf" >}}/plugins/#input-windows-performance-counters)
 
 `win_cpu.json`
 
diff --git a/content/enterprise_influxdb/v1.7/administration/backup-and-restore.md b/content/enterprise_influxdb/v1.7/administration/backup-and-restore.md
index cf57a1354..a6bee77ef 100644
--- a/content/enterprise_influxdb/v1.7/administration/backup-and-restore.md
+++ b/content/enterprise_influxdb/v1.7/administration/backup-and-restore.md
@@ -380,31 +380,35 @@ Use the InfluxDB `influx_inspect export` and `influx -import` commands to create
 
 ### Export data
 
-Use the [`influx_inspect export` command](/{{< latest "influxdb" "v1" >}}/tools/influx_inspect#export) to export data in line protocol format from your InfluxDB Enterprise cluster. Options include:
+Use the [`influx_inspect export` command](/influxdb/v1.7/tools/influx_inspect#export) to export data in line protocol format from your InfluxDB Enterprise cluster. Options include:
 
 - Exporting all, or specific, databases
 - Filtering with starting and ending timestamps
 - Using gzip compression for smaller files and faster exports
 
-For details on optional settings and usage, see [`influx_inspect export` command](/{{< latest "influxdb" "v1" >}}/tools/influx_inspect#export).
+For details on optional settings and usage, see [`influx_inspect export` command](/influxdb/v1.7/tools/influx_inspect#export).
 
 In the following example, the database is exported filtered to include only one day and compressed for optimal speed and file size.
 
 ```bash
-influx_inspect export -database myDB -compress -start 2019-05-19T00:00:00.000Z -end 2019-05-19T23:59:59.999Z
+influx_inspect export \
+  -database myDB \
+  -compress \
+  -start 2019-05-19T00:00:00.000Z \
+  -end 2019-05-19T23:59:59.999Z
 ```
 
 ### Import data
 
-After exporting the data in line protocol format, you can import the data using the [`influx -import` CLI command](/{{< latest "influxdb" "v1" >}}/tools/shell/#import).
+After exporting the data in line protocol format, you can import the data using the [`influx -import` CLI command](/influxdb/v1.7/tools/shell/#import).
 
 In the following example, the compressed data file is imported into the specified database.
 
 ```bash
-influx -import -database myDB -compress
+influx -import -database myDB -compressed
 ```
 
-For details on using the `influx -import` command, see [Import data from a file with -import](/{{< latest "influxdb" "v1" >}}/tools/shell/#import-data-from-a-file-with-import).
+For details on using the `influx -import` command, see [Import data from a file with -import](/influxdb/v1.7/tools/shell/#import-data-from-a-file-with-import).
 
 ## Take AWS snapshots as backup
 
diff --git a/content/enterprise_influxdb/v1.8/administration/backup-and-restore.md b/content/enterprise_influxdb/v1.8/administration/backup-and-restore.md
index c876579b6..49155ad01 100644
--- a/content/enterprise_influxdb/v1.8/administration/backup-and-restore.md
+++ b/content/enterprise_influxdb/v1.8/administration/backup-and-restore.md
@@ -27,7 +27,7 @@ Depending on the volume of data to be protected and your application requirement
 - [Backup and restore utilities](#backup-and-restore-utilities) — For most applications
 - [Exporting and importing data](#exporting-and-importing-data) — For large datasets
 
-> **Note:** Use the [`backup` and `restore` utilities (InfluxDB OSS 1.5 and later)](/{{< latest "influxdb" "v1" >}}/administration/backup_and_restore/) to:
+> **Note:** Use the [`backup` and `restore` utilities (InfluxDB OSS 1.5 and later)](/influxdb/v1.8/administration/backup_and_restore/) to:
 >
 > - Restore InfluxDB Enterprise backup files to InfluxDB OSS instances.
 > - Back up InfluxDB OSS data that can be restored in InfluxDB Enterprise clusters.
@@ -434,31 +434,35 @@ As an alternative to the standard backup and restore utilities, use the InfluxDB
 
 ### Exporting data
 
-Use the [`influx_inspect export` command](/{{< latest "influxdb" "v1" >}}/tools/influx_inspect#export) to export data in line protocol format from your InfluxDB Enterprise cluster. Options include:
+Use the [`influx_inspect export` command](/influxdb/v1.8/tools/influx_inspect#export) to export data in line protocol format from your InfluxDB Enterprise cluster. Options include:
 
 - Exporting all, or specific, databases
 - Filtering with starting and ending timestamps
 - Using gzip compression for smaller files and faster exports
 
-For details on optional settings and usage, see [`influx_inspect export` command](/{{< latest "influxdb" "v1" >}}/tools/influx_inspect#export).
+For details on optional settings and usage, see [`influx_inspect export` command](/influxdb/v1.8/tools/influx_inspect#export).
 
 In the following example, the database is exported filtered to include only one day and compressed for optimal speed and file size.
 
 ```bash
-influx_inspect export -database myDB -compress -start 2019-05-19T00:00:00.000Z -end 2019-05-19T23:59:59.999Z
+influx_inspect export \
+  -database myDB \
+  -compress \
+  -start 2019-05-19T00:00:00.000Z \
+  -end 2019-05-19T23:59:59.999Z
 ```
 
 ### Importing data
 
-After exporting the data in line protocol format, you can import the data using the [`influx -import` CLI command](/{{< latest "influxdb" "v1" >}}/tools/shell/#import).
+After exporting the data in line protocol format, you can import the data using the [`influx -import` CLI command](/influxdb/v1.8/tools/shell/#import).
 
 In the following example, the compressed data file is imported into the specified database.
 
 ```bash
-influx -import -database myDB -compress
+influx -import -database myDB -compressed
 ```
 
-For details on using the `influx -import` command, see [Import data from a file with -import](/{{< latest "influxdb" "v1" >}}/tools/shell/#import-data-from-a-file-with-import).
+For details on using the `influx -import` command, see [Import data from a file with -import](/influxdb/v1.8/tools/shell/#import-data-from-a-file-with-import).
 
 ### Example
 
diff --git a/content/enterprise_influxdb/v1.8/install-and-deploy/production_installation/_index.md b/content/enterprise_influxdb/v1.8/install-and-deploy/production_installation/_index.md
index d10d3461f..bcab1bfb3 100644
--- a/content/enterprise_influxdb/v1.8/install-and-deploy/production_installation/_index.md
+++ b/content/enterprise_influxdb/v1.8/install-and-deploy/production_installation/_index.md
@@ -15,5 +15,3 @@ Complete the following steps to install an InfluxDB Enterprise cluster in your o
 1. [Install InfluxDB Enterprise meta nodes](/enterprise_influxdb/v1.8/install-and-deploy/production_installation/meta_node_installation/)
 2. [Install InfluxDB data nodes](/enterprise_influxdb/v1.8/install-and-deploy/production_installation/data_node_installation/)
 3. [Install Chronograf](/enterprise_influxdb/v1.8/install-and-deploy/production_installation/chrono_install/)
-
-> **Note:** If you're looking for cloud infrastructure and services, check out how to deploy InfluxDB Enterprise (production-ready) on a cloud provider of your choice: [Azure](/enterprise_influxdb/v1.8/install-and-deploy/deploying/azure/), [GCP](/enterprise_influxdb/v1.8/install-and-deploy/deploying/google-cloud-platform/), or [AWS](/enterprise_influxdb/v1.8/install-and-deploy/deploying/aws/).
diff --git a/content/enterprise_influxdb/v1.9/_index.md b/content/enterprise_influxdb/v1.9/_index.md
index ba842d182..5bc11bfd9 100644
--- a/content/enterprise_influxdb/v1.9/_index.md
+++ b/content/enterprise_influxdb/v1.9/_index.md
@@ -30,7 +30,7 @@ and get started!
 
 ## Next steps
 
-- [Install and deploy](/enterprise_influxdb/v1.9/install-and-deploy/)
+- [Install and deploy](/enterprise_influxdb/v1.9/introduction/installation/)
 - Review key [concepts](/enterprise_influxdb/v1.9/concepts/)
 - [Get started](/enterprise_influxdb/v1.9/introduction/getting-started/)
 
diff --git a/content/enterprise_influxdb/v1.9/about-the-project/release-notes-changelog.md b/content/enterprise_influxdb/v1.9/about-the-project/release-notes-changelog.md
index 2c062dad3..4c8c16880 100644
--- a/content/enterprise_influxdb/v1.9/about-the-project/release-notes-changelog.md
+++ b/content/enterprise_influxdb/v1.9/about-the-project/release-notes-changelog.md
@@ -9,6 +9,52 @@ menu:
     parent: About the project
 ---
 
+## 1.9.6 [2022-02-16]
+
+{{% note %}} InfluxDB Enterprise offerings are no longer available on AWS, Azure, and GCP marketplaces. Please [contact Sales](https://www.influxdata.com/contact-sales/) to request an license key to [install InfluxDB Enterprise in your own environment](/enterprise_influxdb/v1.9/introduction/installation/).
+{{% /note %}}
+
+### Features
+
+#### Backup enhancements
+
+- **Revert damaged meta nodes to a previous state**: Add the `-meta-only-overwrite-force` option to [`influxd-ctl restore`](/enterprise_influxdb/v1.9/tools/influxd-ctl/#restore) to revert damaged meta nodes in an existing cluster to a previous state when restoring an InfluxDB Enterprise database.
+
+- **Estimate the size of a backup** (full or incremental) and provide progress messages. Add `-estimate` option to [`influxd-ctl backup`](/enterprise_influxdb/v1.9/tools/influxd-ctl/#backup) to estimate the size of a backup (full or incremental) and provide progress messages. Prints the number of files to back up, the percentage of bytes transferred for each file (organized by shard), and the estimated time remaining to complete the backup.
+
+#### Logging enhancements
+
+- **Log active queries when a process is terminated**: Add the [`termination-query-log`](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes/#termination-query-log--false) configuration option. When set to `true` all running queries are printed to the log when a data node process receives a `SIGTERM` (for example, a Kubernetes process exceeds the container memory limit or the process is terminated).
+
+- **Log details of HTTP calls to meta nodes**. When [`cluster-tracing`](/enterprise_influxdb/v1.9/administration/configure/config-meta-nodes/#cluster-tracing--false) is enabled, all API calls to meta nodes are now logged with details providing an audit trail including IP address of caller, specific API being invoked, action being invoked, and more.
+
+### Maintenance updates
+
+- Update to [Flux v0.140](/flux/v0.x/release-notes/#v01400-2021-11-22).
+- Upgrade to Go 1.17.
+- Upgrade `protobuf` library.
+
+### Bug fixes
+
+#### Data
+
+-  Adjust shard start and end times to avoid overlaps in existing shards. This resolves issues with existing shards (truncated or not) that have a different shard duration than the current default.
+- `DROP SHARD` now successfully ignores "shard not found errors."
+
+#### Errors
+
+- Fix panic when running `influxd config`.
+- Ensure `influxd-ctl entropy` commands use the correct TLS settings.
+
+#### Profiling
+
+- Resolve issue to enable [mutex profiling](/enterprise_influxdb/v1.9/tools/api/#debugpprof-http-endpoint).
+
+#### influx-ctl updates
+
+- Improve [`influxd-ctl join`](/enterprise_influxdb/v1.9/tools/influxd-ctl/#join) robustness and provide better error messages on failure.
+- Add user friendly error message when accessing a TLS-enabled server without TLS enabled on client.
+
 ## v1.9.5 [2021-10-11]
 
 {{% note %}}
@@ -67,7 +113,7 @@ Changes below are included in InfluxDB Enterprise 1.9.5.
 - Add [configurable password hashing](/enterprise_influxdb/v1.9/administration/configure-password-hashing/) with `bcrypt` and `pbkdf2` support.
 - Add retry with exponential back-off to anti-entropy repair.
 - Add logging to compaction.
-- Add [`total-buffer-bytes`](/enterprise_influxdb/v1.9/administration/config-data-nodes/#total-buffer-bytes--0) configuration parameter to subscriptions.
+- Add [`total-buffer-bytes`](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes/#total-buffer-bytes) configuration parameter to subscriptions.
   This option is intended to help alleviate out-of-memory errors.
 - Update to [Flux v0.120.1.](/influxdb/v2.0/reference/release-notes/flux/#v01201-2021-07-06)
 
@@ -99,7 +145,7 @@ in that there is no corresponding InfluxDB OSS release.
   These queries now return a `cardinality estimation` column header where before they returned `count`.
 - Improve diagnostics for license problems.
   Add [license expiration date](/enterprise_influxdb/v1.9/features/clustering-features/#entitlements) to `debug/vars` metrics.
-- Add improved [ingress metrics](/enterprise_influxdb/v1.9/administration/config-data-nodes/#ingress-metric-by-measurement-enabled--false) to track points written by measurement and by login.
+- Add improved [ingress metrics](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes/#ingress-metric-by-measurement-enabled) to track points written by measurement and by login.
   Allow for collection of statistics regarding points, values, and new series written per measurement and by login.
   This data is collected and exposed at the data node level.
   With these metrics you can, for example:
@@ -107,7 +153,7 @@ in that there is no corresponding InfluxDB OSS release.
   monitor the growth of series within a measurement,
   and track what user credentials are being used to write data.
 - Support authentication for Kapacitor via LDAP.
-- Support for [configuring Flux query resource usage](/enterprise_influxdb/v1.9/administration/config-data-nodes/#flux-controller) (concurrency, memory, etc.).
+- Support for [configuring Flux query resource usage](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes/#flux-controller) (concurrency, memory, etc.).
 - Upgrade to [Flux v0.113.0](/influxdb/v2.0/reference/release-notes/flux/#v01130-2021-04-21).
 - Update Prometheus remote protocol to allow streamed reading.
 - Improve performance of sorted merge iterator.
diff --git a/content/enterprise_influxdb/v1.9/administration/backup-and-restore.md b/content/enterprise_influxdb/v1.9/administration/backup-and-restore.md
index 8e0441e1b..8d2d139d4 100644
--- a/content/enterprise_influxdb/v1.9/administration/backup-and-restore.md
+++ b/content/enterprise_influxdb/v1.9/administration/backup-and-restore.md
@@ -91,7 +91,7 @@ for a complete list of the global `influxd-ctl` options.
       databases, continuous queries, retention policies. Shards are not exported.
 - `-full`: perform a full backup. Deprecated in favour of `-strategy=full`
 - `-rp <string>`: the name of the single retention policy to back up (must specify `-db` with `-rp`)
-- `-shard <unit>`: the ID of the single shard to back up
+- `-shard <unit>`: the ID of the single shard to back up (cannot be used with `-db`)
 
 ### Backup examples
 
@@ -176,9 +176,9 @@ $ ls ./telegrafbackup
 20160803T222811Z.manifest  20160803T222811Z.meta  20160803T222811Z.s4.tar.gz
 ```
 
-#### Perform a metastore only backup
+#### Perform a metadata only backup
 
-Perform a meta store only backup into a specific directory with the command below.
+Perform a metadata only backup into a specific directory with the command below.
 The directory must already exist.
 
 ```bash
@@ -316,8 +316,8 @@ Restored from my-incremental-backup/ in 83.892591ms, transferred 588800 bytes
 
 ##### Restore from a metadata backup
 
-In this example, the `restore` command restores an metadata backup stored
-in the `metadata-backup/` directory.
+In this example, the `restore` command restores a [metadata backup](#perform-a-metadata-only-backup)
+stored in the `metadata-backup/` directory.
 
 ```bash
 # Syntax
@@ -402,6 +402,29 @@ time                  written
 1970-01-01T00:00:00Z  471
 ```
 
+##### Restore (overwrite) metadata from a full or incremental backup to fix damaged metadata
+
+1. Identify a backup with uncorrupted metadata from which to restore.
+2. Restore from backup with `-meta-only-overwrite-force`.
+
+   {{% warn %}}
+   Only use the `-meta-only-overwrite-force` flag to restore from backups of the target cluster.
+   If you use this flag with metadata from a different cluster, you will lose data.
+   (since metadata includes shard assignments to data nodes).
+   {{% /warn %}}
+
+   ```bash
+   # Syntax
+   influxd-ctl restore -meta-only-overwrite-force <path-to-backup-directory>
+
+   # Example
+   $ influxd-ctl restore -meta-only-overwrite-force my-incremental-backup/
+   Using backup directory: my-incremental-backup/
+   Using meta backup: 20200101T000000Z.meta
+   Restoring meta data... Done. Restored in 21.373019ms, 1 shards mapped
+   Restored from my-incremental-backup/ in 19.2311ms, transferred 588 bytes
+   ```
+
 #### Common issues with restore
 
 ##### Restore writes information not part of the original backup
@@ -446,7 +469,11 @@ For details on optional settings and usage, see [`influx_inspect export` command
 In the following example, the database is exported filtered to include only one day and compressed for optimal speed and file size.
 
 ```bash
-influx_inspect export -database myDB -compress -start 2019-05-19T00:00:00.000Z -end 2019-05-19T23:59:59.999Z
+influx_inspect export \
+  -database myDB \
+  -compress \
+  -start 2019-05-19T00:00:00.000Z \
+  -end 2019-05-19T23:59:59.999Z
 ```
 
 ### Importing data
@@ -456,7 +483,7 @@ After exporting the data in line protocol format, you can import the data using
 In the following example, the compressed data file is imported into the specified database.
 
 ```bash
-influx -import -database myDB -compress
+influx -import -database myDB -compressed
 ```
 
 For details on using the `influx -import` command, see [Import data from a file with -import](/enterprise_influxdb/v1.9/tools/influx-cli/use-influx/#import-data-from-a-file-with--import).
diff --git a/content/enterprise_influxdb/v1.9/administration/configure/anti-entropy/_index.md b/content/enterprise_influxdb/v1.9/administration/configure/anti-entropy/_index.md
index eab4bb7ef..3f8bb3b87 100644
--- a/content/enterprise_influxdb/v1.9/administration/configure/anti-entropy/_index.md
+++ b/content/enterprise_influxdb/v1.9/administration/configure/anti-entropy/_index.md
@@ -34,7 +34,7 @@ If data inconsistencies are detected among shards in a shard group, [invoke the
 In the repair process, the Anti-Entropy service will sync the necessary updates from other shards
 within a shard group.
 
-By default, the service performs consistency checks every 5 minutes. This interval can be modified in the [`anti-entropy.check-interval`](/enterprise_influxdb/v1.9/administration/config-data-nodes/#check-interval-5m) configuration setting.
+By default, the service performs consistency checks every 5 minutes. This interval can be modified in the [`anti-entropy.check-interval`](/enterprise_influxdb/v1.9/administration/config-data-nodes/#check-interval) configuration setting.
 
 The Anti-Entropy service can only address missing or inconsistent shards when
 there is at least one copy of the shard available.
@@ -178,7 +178,7 @@ until it either shows as being in the queue, being repaired, or no longer in the
 
 ## Configuration
 
-The configuration settings for the Anti-Entropy service are described in [Anti-Entropy settings](/enterprise_influxdb/v1.9/administration/config-data-nodes#anti-entropy) section of the data node configuration.
+The configuration settings for the Anti-Entropy service are described in [Anti-Entropy settings](/enterprise_influxdb/v1.9/administration/config-data-nodes/#anti-entropy-ae-settings) section of the data node configuration.
 
 To enable the Anti-Entropy service, change the default value of the `[anti-entropy].enabled = false` setting to `true` in the `influxdb.conf` file of each of your data nodes.
 
diff --git a/content/enterprise_influxdb/v1.9/administration/configure/config-data-nodes.md b/content/enterprise_influxdb/v1.9/administration/configure/config-data-nodes.md
index 1eb0dc409..1ed1d8fd7 100644
--- a/content/enterprise_influxdb/v1.9/administration/configure/config-data-nodes.md
+++ b/content/enterprise_influxdb/v1.9/administration/configure/config-data-nodes.md
@@ -49,25 +49,33 @@ All commented-out settings will be determined by the internal defaults.
 
 ## Global settings
 
-#### `reporting-disabled = false`
+#### `reporting-disabled`
+
+Default is `false`.
 
 Once every 24 hours InfluxDB Enterprise will report usage data to usage.influxdata.com.
 The data includes a random ID, os, arch, version, the number of series and other usage data. No data from user databases is ever transmitted.
 Change this option to true to disable reporting.
 
-#### `bind-address = ":8088"`
+#### `bind-address`
+
+Default is `":8088"`.
 
 The TCP bind address used by the RPC service for inter-node communication and [backup and restore](/enterprise_influxdb/v1.9/administration/backup-and-restore/).
 
 Environment variable: `INFLUXDB_BIND_ADDRESS`
 
-#### `hostname = "localhost"`
+#### `hostname`
+
+Default is `"localhost"`.
 
 The hostname of the [data node](/enterprise_influxdb/v1.9/concepts/glossary/#data-node). This must be resolvable by all other nodes in the cluster.
 
 Environment variable: `INFLUXDB_HOSTNAME`
 
-#### `gossip-frequency = "3s"`
+#### `gossip-frequency`
+
+Default is `"3s"`.
 
 How often to update the cluster with this node's internal status.
 
@@ -81,7 +89,9 @@ Environment variable: `INFLUXDB_GOSSIP_FREQUENCY`
 
 The `[enterprise]` section contains the parameters for the meta node's registration with the [InfluxDB Enterprise License Portal](https://portal.influxdata.com/).
 
-#### `license-key = ""`
+#### `license-key`
+
+Default is `""`.
 
 The license key created for you on [InfluxPortal](https://portal.influxdata.com). The meta node transmits the license key to [portal.influxdata.com](https://portal.influxdata.com) over port 80 or port 443 and receives a temporary JSON license file in return.
 The server caches the license file locally.
@@ -98,7 +108,9 @@ mutually exclusive and one must remain set to the empty string.
 
 Environment variable: `INFLUXDB_ENTERPRISE_LICENSE_KEY`
 
-#### `license-path = ""`
+#### `license-path`
+
+Default is `""`.
 
 The local path to the permanent JSON license file that you received from InfluxData for instances that do not have access to the internet.
 The data process will only function for a limited time without a valid license file.
@@ -124,7 +136,9 @@ Environment variable: `INFLUXDB_ENTERPRISE_LICENSE_PATH`
 
 Settings related to how the data nodes interact with the meta nodes.
 
-#### `dir = "/var/lib/influxdb/meta"`
+#### `dir`
+
+Default is `"/var/lib/influxdb/meta"`.
 
 The directory where the cluster metadata is stored.
 
@@ -132,39 +146,50 @@ The directory where the cluster metadata is stored.
 
 Environment variable: `INFLUXDB_META_DIR`
 
-#### `meta-tls-enabled = false`
+#### `meta-tls-enabled`
+
+Default is `false`.
 
 Whether to use TLS when connecting to meta nodes.
-Set to `true` to if [`https-enabled`](#https-enabled-false) is set to `true`.
+Set to `true` to if [`https-enabled`](#https-enabled) is set to `true`.
 
 Environment variable: `INFLUXDB_META_META_TLS_ENABLED`
 
-#### `meta-insecure-tls = false`
+#### `meta-insecure-tls`
+
+Default is `false`.
 
 Allows insecure TLS connections to meta nodes.
 This is useful when testing with self-signed certificates.
 
-Set to `true` to allow the data node to accept self-signed certificates if [`https-enabled`](#https-enabled-false) is set to `true`.
+Set to `true` to allow the data node to accept self-signed certificates if [`https-enabled`](#https-enabled) is set to `true`.
 
 Environment variable: `INFLUXDB_META_META_INSECURE_TLS`
 
-#### `meta-auth-enabled = false`
+#### `meta-auth-enabled`
+
+Default is `false`.
 
 This setting must have the same value as the meta nodes' `[meta] auth-enabled` configuration.
 
-Set to `true` if [`auth-enabled`](#auth-enabled-false) is set to `true` in the meta node configuration files.
+Set to `true` if [`auth-enabled`](#auth-enabled) is set to `true` in the meta node configuration files.
 For JWT authentication, also see the [`meta-internal-shared-secret`](#meta-internal-shared-secret) configuration option.
 
 Environment variable: `INFLUXDB_META_META_AUTH_ENABLED`
 
-#### `meta-internal-shared-secret = ""`
+#### `meta-internal-shared-secret`
+
+Default is `""`.
 
 The shared secret used by the internal API for JWT authentication between InfluxDB nodes.
-This value must be the same as the [`internal-shared-secret`](/enterprise_influxdb/v1.9/administration/config-meta-nodes/#internal-shared-secret) specified in the meta node configuration file.
+This value must be the same as the [`internal-shared-secret`](/enterprise_influxdb/v1.9/administration/configure/config-meta-nodes/#internal-shared-secret)
+specified in the meta node configuration file.
 
 Environment variable: `INFLUXDB_META_META_INTERNAL_SHARED_SECRET`
 
-#### `retention-autocreate = true`
+#### `retention-autocreate`
+
+Default is `true`.
 
 Automatically creates a default [retention policy](/enterprise_influxdb/v1.9/concepts/glossary/#retention-policy-rp) (RP) when the system creates a database.
 The default RP (`autogen`) has an infinite duration, a shard group duration of seven days, and a replication factor set to the number of data nodes in the cluster.
@@ -173,28 +198,34 @@ Set this option to `false` to prevent the system from creating the `autogen` RP
 
 Environment variable: `INFLUXDB_META_RETENTION_AUTOCREATE`
 
-#### `logging-enabled = true`
+#### `logging-enabled`
+
+Default is `true`.
 
 Whether log messages are printed for the meta service.
 
 Environment variable: `INFLUXDB_META_LOGGING_ENABLED`
 
-#### `password-hash = bcrypt`
+#### `password-hash`
+
+Default is `bcrypt`.
 
 Configures password hashing algorithm.
 Supported options are: `bcrypt` (the default), `pbkdf2-sha256`, and `pbkdf2-sha512`
-This setting must have the same value as the meta node option [`meta.password-hash`](/enterprise_influxdb/v1.9/administration/config-meta-nodes/#password-hash--bcrypt).
+This setting must have the same value as the meta node option [`meta.password-hash`](/enterprise_influxdb/v1.9/administration/configure/config-meta-nodes/#password-hash).
 
-For detailed configuration information, see [`meta.password-hash`](/enterprise_influxdb/v1.9/administration/config-meta-nodes/#password-hash--bcrypt).
+For detailed configuration information, see [`meta.password-hash`](/enterprise_influxdb/v1.9/administration/configure/config-meta-nodes/#password-hash).
 
 Environment variable: `INFLUXDB_META_PASSWORD_HASH`
 
-#### `ensure-fips = false`
+#### `ensure-fips`
+
+Default is `false`.
 
 When `true`, enables a FIPS-readiness check on startup.
 Default is `false`.
 
-For detailed configuration information, see [`meta.ensure-fips`](/enterprise_influxdb/v1.9/administration/config-meta-nodes/#ensure-fips--false).
+For detailed configuration information, see [`meta.ensure-fips`](/enterprise_influxdb/v1.9/administration/configure/config-meta-nodes/#ensure-fips).
 
 Environment variable: `INFLUXDB_META_ENSURE_FIPS`
 
@@ -208,33 +239,43 @@ Controls where the actual shard data for InfluxDB lives and how it is compacted
 "dir" may need to be changed to a suitable place for your system.
 The defaults should work for most systems.
 
-#### `dir = "/var/lib/influxdb/data"`
+#### `dir`
+
+Default is `"/var/lib/influxdb/data"`.
 
 The directory where the TSM storage engine stores TSM (read-optimized) files.
 
 Environment variable: `INFLUXDB_DATA_DIR`
 
-#### `wal-dir = "/var/lib/influxdb/wal"`
+#### `wal-dir`
+
+Default is `"/var/lib/influxdb/wal"`.
 
 The directory where the TSM storage engine stores WAL (write-optimized) files.
 
 Environment variable: `INFLUXDB_DATA_WAL_DIR`
 
-#### `trace-logging-enabled = false`
+#### `trace-logging-enabled`
+
+Default is `false`.
 
 Trace logging provides more verbose output around the TSM engine.
 Turning this on can provide more useful output for debugging TSM engine issues.
 
 Environmental variable: `INFLUXDB_DATA_TRACE_LOGGING_ENABLED`
 
-#### `query-log-enabled = true`
+#### `query-log-enabled`
+
+Default is `true`.
 
 Whether queries should be logged before execution.
 Very useful for troubleshooting, but will log any sensitive data contained within a query.
 
 Environment variable: `INFLUXDB_DATA_QUERY_LOG_ENABLED`
 
-#### `wal-fsync-delay = "0s"`
+#### `wal-fsync-delay`
+
+Default is `"0s"`.
 
 The amount of time that a write waits before fsyncing.
 Use a duration greater than 0 to batch up multiple fsync calls.
@@ -244,14 +285,18 @@ InfluxData recommends values ranging from `0ms` to `100ms` for non-SSD disks.
 
 Environment variable: `INFLUXDB_DATA_WAL_FSYNC_DELAY`
 
-#### `ingress-metric-by-measurement-enabled = false`
+#### `ingress-metric-by-measurement-enabled`
+
+Default is `false`.
 
 When `true`, collect statistics of points, values and new series written per-measurement. Metrics are gathered per data node. 
 These can be accessed via the `/debug/vars` endpoint and in the `_internal` database if enabled.
 
 Environment variable: `INFLUXDB_DATA_INGRESS_METRIC_BY_MEASUREMENT_ENABLED`
 
-#### `ingress-metric-by-login-enabled = false`
+#### `ingress-metric-by-login-enabled`
+
+Default is `false`.
 
 When `true`, collect statistics of points, values and new series written per-login. Metrics are gathered per data node.
 These can be accessed via the `/debug/vars` endpoint and in the `_internal` database if enabled.
@@ -260,25 +305,35 @@ Environment variable: `INFLUXDB_DATA_INGRESS_METRIC_BY_LOGIN_ENABLED`
 
 ### Data settings for the TSM engine
 
-#### `cache-max-memory-size = "1g"`
+#### `cache-max-memory-size`
 
-The maximum size a shard cache can reach before it starts rejecting writes.
+Default is `1000000000`.
+
+The maximum size in bytes that a shard cache can reach before it starts rejecting writes.
+
+Consider increasing this value if encountering `cache maximum memory size exceeded` errors.
 
 Environment variable: `INFLUXDB_DATA_CACHE_MAX_MEMORY_SIZE`
 
-#### `cache-snapshot-memory-size = "25m"`
+#### `cache-snapshot-memory-size`
 
-The size at which the TSM engine will snapshot the cache and write it to a TSM file, freeing up memory.
+Default is `26214400`.
+
+The size in bytes at which the TSM engine will snapshot the cache and write it to a TSM file, freeing up memory.
 
 Environment variable: `INFLUXDB_DATA_CACHE_SNAPSHOT_MEMORY_SIZE`
 
-#### `cache-snapshot-write-cold-duration = "10m"`
+#### `cache-snapshot-write-cold-duration`
+
+Default is `"10m"`.
 
 The length of time at which the TSM engine will snapshot the cache and write it to a new TSM file if the shard hasn't received writes or deletes.
 
 Environment variable: `INFLUXDB_DATA_CACHE_SNAPSHOT_WRITE_COLD_DURATION`
 
-#### `max-concurrent-compactions = 0`
+#### `max-concurrent-compactions`
+
+Default is `0`.
 
 The maximum number of concurrent full and level compactions that can run at one time.  
 A value of `0` (unlimited compactions) results in 50% of `runtime.GOMAXPROCS(0)` used at runtime,
@@ -288,26 +343,35 @@ This setting does not apply to cache snapshotting.
 
 Environmental variable: `INFLUXDB_DATA_CACHE_MAX_CONCURRENT_COMPACTIONS`
 
-#### `compact-throughput = "48m"`
+#### `compact-throughput`
+
+Default is `50331648`.
 
 The maximum number of bytes per seconds TSM compactions write to disk. Default is `"48m"` (48 million).
 Note that short bursts are allowed to happen at a possibly larger value, set by `compact-throughput-burst`.
 
 Environment variable: `INFLUXDB_DATA_COMPACT_THROUGHPUT`  
 
-#### `compact-throughput-burst = "48m"`
+
+#### `compact-throughput-burst`
+
+Default is `50331648`.
 
 The maximum number of bytes per seconds TSM compactions write to disk during brief bursts. Default is `"48m"` (48 million).
 
 Environment variable: `INFLUXDB_DATA_COMPACT_THROUGHPUT_BURST`  
 
-#### `compact-full-write-cold-duration = "4h"`
+#### `compact-full-write-cold-duration`
+
+Default is `"4h"`.
 
 The duration at which to compact all TSM and TSI files in a shard if it has not received a write or delete.
 
 Environment variable: `INFLUXDB_DATA_COMPACT_FULL_WRITE_COLD_DURATION`
 
-#### `index-version = "inmem"`
+#### `index-version`
+
+Default is `"inmem"`.
 
 The type of shard index to use for new shards.
 The default (`inmem`) is to use an in-memory index that is recreated at startup.
@@ -318,7 +382,9 @@ Environment variable: `INFLUXDB_DATA_INDEX_VERSION`
 
 ### In-memory (`inmem`) index settings
 
-#### `max-series-per-database = 1000000`
+#### `max-series-per-database`
+
+Default is `1000000`.
 
 The maximum number of [series](/enterprise_influxdb/v1.9/concepts/glossary/#series) allowed per database before writes are dropped.
 The default setting is `1000000` (one million).
@@ -338,7 +404,9 @@ If a point causes the number of series in a database to exceed
 
 Environment variable: `INFLUXDB_DATA_MAX_SERIES_PER_DATABASE`
 
-#### `max-values-per-tag = 100000`
+#### `max-values-per-tag`
+
+Default is `100000`.
 
 The maximum number of [tag values](/enterprise_influxdb/v1.9/concepts/glossary/#tag-value) allowed per [tag key](/enterprise_influxdb/v1.9/concepts/glossary/#tag-key).
 The default value is `100000` (one hundred thousand).
@@ -356,7 +424,9 @@ Environment variable: `INFLUXDB_DATA_MAX_VALUES_PER_TAG`
 
 ### TSI (`tsi1`) index settings
 
-#### `max-index-log-file-size = "1m"`
+#### `max-index-log-file-size`
+
+Default is `1048576`.
 
 The threshold, in bytes, when an index write-ahead log (WAL) file will compact
 into an index file. Lower sizes will cause log files to be compacted more
@@ -368,7 +438,9 @@ Values without a size suffix are in bytes.
 
 Environment variable: `INFLUXDB_DATA_MAX_INDEX_LOG_FILE_SIZE`
 
-#### `series-id-set-cache-size = 100`
+#### `series-id-set-cache-size`
+
+Default is `100`.
 
 The size of the internal cache used in the TSI index to store previously
 calculated series results. Cached results will be returned quickly from the cache rather
@@ -400,14 +472,18 @@ a single-use TCP connection may be used.
 For information on InfluxDB `_internal` measurement statistics related to clusters, RPCs, and shards,
 see [Measurements for monitoring InfluxDB Enterprise (`_internal`)](/platform/monitoring/influxdata-platform/tools/measurements-internal/#cluster-enterprise-only).
 
-#### `dial-timeout = "1s"`
+#### `dial-timeout`
+
+Default is `"1s"`.
 
 The duration for which the meta node waits for a connection to a remote data node before the meta node attempts to connect to a different remote data node.
 This setting applies to queries only.
 
 Environment variable: `INFLUXDB_CLUSTER_DIAL_TIMEOUT`
 
-#### `pool-max-idle-time = "60s"`
+#### `pool-max-idle-time`
+
+Default is `"60s"`.
 
 The maximum time that a TCP connection to another data node remains idle in the connection pool.
 When the connection is idle longer than the specified duration, the inactive connection is reaped —
@@ -416,7 +492,9 @@ idle connections minimizes inactive connections, decreases system load, and prev
 
 Environment variable: `INFLUXDB_CLUSTER_POOL_MAX_IDLE_TIME`
 
-#### `pool-max-idle-streams = 100`
+#### `pool-max-idle-streams`
+
+Default is `100`.
 
 The maximum number of idle RPC stream connections to retain in an idle pool between two nodes.
 When a new RPC request is issued, a connection is temporarily pulled from the idle pool, used, and then returned.
@@ -428,7 +506,9 @@ so it is unlikely that changing this value will measurably improve performance b
 
 Environment variable: `INFLUXDB_CLUSTER_POOL_MAX_IDLE_STREAMS`
 
-#### `allow-out-of-order-writes = false`
+#### `allow-out-of-order-writes`
+
+Default is `false`.
 
 By default, this option is set to false and writes are processed in the order that they are received. This means if any points are in the hinted handoff (HH) queue for a shard, all incoming points must go into the HH queue.
 
@@ -442,33 +522,45 @@ Point 1 (`cpu v=1.0 1234`) arrives at `node1`, attempts to replicate on `node2`,
 
 Environment variable: `INFLUXDB_CLUSTER_ALLOW_OUT_OF_ORDER`
 
-#### `shard-reader-timeout = "0"`
+#### `shard-reader-timeout`
+
+Default is `"0"`.
 
 The default timeout set on shard readers.
 The time in which a query connection must return its response after which the system returns an error.
 
 Environment variable: `INFLUXDB_CLUSTER_SHARD_READER_TIMEOUT`
 
-#### `https-enabled = false`
+#### `https-enabled`
+
+Default is `false`.
 
 Determines whether data nodes use HTTPS to communicate with each other.
 
-#### `https-certificate = ""`
+#### `https-certificate`
+
+Default is `""`.
 
 The SSL certificate to use when HTTPS is enabled.  
 The certificate should be a PEM-encoded bundle of the certificate and key.  
 If it is just the certificate, a key must be specified in `https-private-key`.
 
-#### `https-private-key = ""`
+#### `https-private-key`
+
+Default is `""`.
 
 Use a separate private key location.
 
-#### `https-insecure-tls = false`
+#### `https-insecure-tls`
+
+Default is `false`.
 
 Whether data nodes will skip certificate validation communicating with each other over HTTPS.
 This is useful when testing with self-signed certificates.
 
-#### `cluster-tracing = false`
+#### `cluster-tracing`
+
+Default is `false`.
 
 Enables cluster trace logging.
 Set to `true` to enable logging of cluster communications.
@@ -476,13 +568,17 @@ Enable this setting to verify connectivity issues between data nodes.
 
 Environment variable: `INFLUXDB_CLUSTER_CLUSTER_TRACING`
 
-#### `write-timeout = "10s"`
+#### `write-timeout`
+
+Default is `"10s"`.
 
 The duration a write request waits until a "timeout" error is returned to the caller. The default value is 10 seconds.
 
 Environment variable: `INFLUXDB_CLUSTER_WRITE_TIMEOUT`
 
-#### `max-concurrent-queries = 0`
+#### `max-concurrent-queries`
+
+Default is `0`.
 
 The maximum number of concurrent queries allowed to be executing at one time.  
 If a query is executed and exceeds this limit, an error is returned to the caller.  
@@ -490,14 +586,26 @@ This limit can be disabled by setting it to `0`.
 
 Environment variable: `INFLUXDB_CLUSTER_MAX_CONCURRENT_QUERIES`
 
-#### `query-timeout = "0s"`
+#### `max-concurrent-deletes`
+
+The default is `1`.
+
+The maximum number of allowed simultaneous `DELETE` calls on a shard.
+
+Environment variable: `INFLUXDB_CLUSTER_MAX_CONCURRENT_DELETES`
+
+#### `query-timeout`
+
+Default is `"0s"`.
 
 The maximum time a query is allowed to execute before being killed by the system.
 This limit can help prevent run away queries.  Setting the value to `0` disables the limit.
 
 Environment variable: `INFLUXDB_CLUSTER_QUERY_TIMEOUT`
 
-#### `log-queries-after = "0s"`
+#### `log-queries-after`
+
+Default is `"0s"`.
 
 The time threshold when a query will be logged as a slow query.  
 This limit can be set to help discover slow or resource intensive queries.  
@@ -505,27 +613,39 @@ Setting the value to `0` disables the slow query logging.
 
 Environment variable: `INFLUXDB_CLUSTER_LOG_QUERIES_AFTER`
 
-#### `max-select-point = 0`
+#### `max-select-point`
+
+Default is `0`.
 
 The maximum number of points a SELECT statement can process.  
 A value of `0` will make the maximum point count unlimited.
 
 Environment variable: `INFLUXDB_CLUSTER_MAX_SELECT_POINT`
 
-#### `max-select-series = 0`
+#### `max-select-series`
+
+Default is `0`.
 
 The maximum number of series a SELECT can run.
 A value of `0` will make the maximum series count unlimited.
 
 Environment variable: `INFLUXDB_CLUSTER_MAX_SELECT_SERIES`
 
-#### `max-select-buckets = 0`
+#### `max-select-buckets`
+
+Default is `0`.
 
 The maximum number of group by time buckets a SELECT can create.  
 A value of `0` will make the maximum number of buckets unlimited.
 
 Environment variable: `INFLUXDB_CLUSTER_MAX_SELECT_BUCKETS`
 
+#### `termination-query-log = false`
+
+Set to `true` to print all running queries to the log when a data node process receives a `SIGTERM` (for example, a k8s process exceeds the container memory limit or the process is terminated).
+
+Environment variable: `INFLUXDB_CLUSTER_TERMINATION_QUERY_LOG`
+
 -----
 
 ## Hinted Handoff settings
@@ -534,32 +654,42 @@ Environment variable: `INFLUXDB_CLUSTER_MAX_SELECT_BUCKETS`
 
 Controls the hinted handoff (HH) queue, which allows data nodes to temporarily cache writes destined for another data node when that data node is unreachable.
 
-#### `batch-size = 512000`
+#### `batch-size`
+
+Default is `512000`.
 
 The maximum number of bytes to write to a shard in a single request.
 
 Environment variable: `INFLUXDB_HINTED_HANDOFF_BATCH_SIZE`
 
-#### `max-pending-writes = 1024`
+#### `max-pending-writes`
+
+Default is `1024`.
 
 The maximum number of incoming pending writes allowed in the hinted handoff queue.
 
 Environment variable: `INFLUXDB_HINTED_HANDOFF_MAX_PENDING_WRITES`
 
-#### `dir = "/var/lib/influxdb/hh"`
+#### `dir`
+
+Default is `"/var/lib/influxdb/hh"`.
 
 The hinted handoff directory where the durable queue will be stored on disk.
 
 Environment variable: `INFLUXDB_HINTED_HANDOFF_DIR`
 
-#### `enabled = true`
+#### `enabled`
+
+Default is `true`.
 
 Set to `false` to disable hinted handoff.
 Disabling hinted handoff is not recommended and can lead to data loss if another data node is unreachable for any length of time.
 
 Environment variable: `INFLUXDB_HINTED_HANDOFF_ENABLED`
 
-#### `max-size = 10737418240`
+#### `max-size`
+
+Default is `10737418240`.
 
 The maximum size of the hinted handoff queue in bytes.
 Each queue is for one and only one other data node in the cluster.
@@ -567,7 +697,9 @@ If there are N data nodes in the cluster, each data node may have up to N-1 hint
 
 Environment variable: `INFLUXDB_HINTED_HANDOFF_MAX_SIZE`
 
-#### `max-age = "168h0m0s"`
+#### `max-age`
+
+Default is `"168h0m0s"`.
 
 The time interval that writes sit in the queue before they are purged.
 The time is determined by how long the batch has been in the queue, not by the timestamps in the data.
@@ -575,7 +707,9 @@ If another data node is unreachable for more than the `max-age` it can lead to d
 
 Environment variable: `INFLUXDB_HINTED_HANDOFF_MAX_AGE`
 
-#### `retry-concurrency = 20`
+#### `retry-concurrency`
+
+Default is `20`.
 
 The maximum number of hinted handoff blocks that the source data node attempts to write to each destination data node.
 Hinted handoff blocks are sets of data that belong to the same shard and have the same destination data node.
@@ -590,19 +724,25 @@ Note that increasing `retry-concurrency` also increases network traffic.
 
 Environment variable: `INFLUXDB_HINTED_HANDOFF_RETRY_CONCURRENCY`
 
-#### `retry-rate-limit = 0`
+#### `retry-rate-limit`
+
+Default is `0`.
 
 The rate limit (in bytes per second) that hinted handoff retries hints. A value of `0` disables the rate limit.
 
 Environment variable: `INFLUXDB_HINTED_HANDOFF_RETRY_RATE_LIMIT`
 
-#### `retry-interval = "1s"`
+#### `retry-interval`
+
+Default is `"1s"`.
 
 The time period after which the hinted handoff retries a write after the write fails.
 
 Environment variable: `INFLUXDB_HINTED_HANDOFF_RETRY_INTERVAL`
 
-#### `retry-max-interval = "10s"`
+#### `retry-max-interval`
+
+Default is `"10s"`.
 
 The maximum interval after which the hinted handoff retries a write after the write fails.
 The `retry-max-interval` option is no longer in use and will be removed from the configuration file in a future release.
@@ -610,7 +750,9 @@ Changing the `retry-max-interval` setting has no effect on your cluster.
 
 Environment variable: `INFLUXDB_HINTED_HANDOFF_RETRY_MAX_INTERVAL`
 
-#### `purge-interval = "1m0s"`
+#### `purge-interval`
+
+Default is `"1m0s"`.
 
 The interval at which InfluxDB checks to purge data that are above `max-age`.
 
@@ -626,20 +768,26 @@ For information about the Anti-Entropy service, see [Anti-entropy service in Inf
 
 Controls the copying and repairing of shards to ensure that data nodes contain the shard data they are supposed to.
 
-#### `enabled = false`
+#### `enabled`
+
+Default is `false`.
 
 Enables the anti-entropy service.
 Default value is `false`.
 
 Environment variable: `INFLUXDB_ANTI_ENTROPY_ENABLED`
 
-#### `check-interval = "5m"`
+#### `check-interval`
+
+Default is `"5m"`.
 
 The interval of time when anti-entropy checks run on each data node.
 
 Environment variable: `INFLUXDB_ANTI_ENTROPY_CHECK_INTERVAL`
 
-#### `max-fetch = 10`
+#### `max-fetch`
+
+Default is `10`.
 
 The maximum number of shards that a single data node will copy or repair in parallel.
 
@@ -653,14 +801,18 @@ higher CPU load as new shard digest files are created.
 The added load drops off after shard digests are completed for existing shards.
 {{% /note %}}
 
-#### `max-sync = 1`
+#### `max-sync`
+
+Default is `1`.
 
 The maximum number of concurrent sync operations that should be performed.
 Modify this setting only when requested by InfluxData support.
 
 Environment variable: `INFLUXDB_ANTI_ENTROPY_MAX_SYNC`
 
-#### `auto-repair-missing = true`
+#### `auto-repair-missing`
+
+Default is `true`.
 
 Enables missing shards to automatically be repaired.
 
@@ -674,14 +826,18 @@ Environment variable: `INFLUXDB_ANTI_ENTROPY_AUTO_REPAIR_MISSING`
 
 Controls the enforcement of retention policies for evicting old data.
 
-#### `enabled = true`
+#### `enabled`
+
+Default is `true`.
 
 Enables retention policy enforcement.
 Default value is `true`.
 
 Environment variable: `INFLUXDB_RETENTION_ENABLED`
 
-#### `check-interval = "30m0s"`
+#### `check-interval`
+
+Default is `"30m0s"`.
 
 The interval of time when retention policy enforcement checks run.
 
@@ -696,19 +852,25 @@ Environment variable: `INFLUXDB_RETENTION_CHECK_INTERVAL`
 Controls the precreation of shards, so they are available before data arrives.
 Only shards that, after creation, will have both a start- and end-time in the future, will ever be created. Shards are never precreated that would be wholly or partially in the past.
 
-#### `enabled = true`
+#### `enabled`
+
+Default is `true`.
 
 Enables the shard precreation service.
 
 Environment variable: `INFLUXDB_SHARD_PRECREATION_ENABLED`
 
-#### `check-interval = "10m"`
+#### `check-interval`
+
+Default is `"10m"`.
 
 The interval of time when the check to precreate new shards runs.
 
 Environment variable: `INFLUXDB_SHARD_PRECREATION_CHECK_INTERVAL`
 
-#### `advance-period = "30m"`
+#### `advance-period`
+
+Default is `"30m"`.
 
 The default period ahead of the end time of a shard group that its successor group is created.
 
@@ -730,25 +892,33 @@ For InfluxDB Enterprise production systems, InfluxData recommends including a de
 * On the dedicated InfluxDB monitoring instance, set `store-enabled = false` to avoid potential performance and storage issues.
 * On each InfluxDB cluster node, install a Telegraf input plugin and Telegraf output plugin configured to report data to the dedicated InfluxDB monitoring instance.
 
-#### `store-enabled = true`
+#### `store-enabled`
+
+Default is `true`.
 
 Enables the internal storage of statistics.
 
 Environment variable: `INFLUXDB_MONITOR_STORE_ENABLED`
 
-#### `store-database = "_internal"`
+#### `store-database`
+
+Default is `"_internal"`.
 
 The destination database for recorded statistics.
 
 Environment variable: `INFLUXDB_MONITOR_STORE_DATABASE`
 
-#### `store-interval = "10s"`
+#### `store-interval`
+
+Default is `"10s"`.
 
 The interval at which to record statistics.
 
 Environment variable: `INFLUXDB_MONITOR_STORE_INTERVAL`
 
-#### `remote-collect-interval = "10s"`
+#### `remote-collect-interval`
+
+Default is `"10s"`.
 
 The time interval to poll other data nodes' stats when aggregating cluster stats.
 
@@ -762,47 +932,63 @@ Environment variable: `INFLUXDB_MONITOR_REMOTE_COLLECT_INTERVAL`
 
 Controls how the HTTP endpoints are configured. These are the primary mechanism for getting data into and out of InfluxDB.
 
-#### `enabled = true`
+#### `enabled`
+
+Default is `true`.
 
 Enables HTTP endpoints.
 
 Environment variable: `INFLUXDB_HTTP_ENABLED`
 
-#### `flux-enabled = false`
+#### `flux-enabled`
+
+Default is `false`.
 
 Determines whether the Flux query endpoint is enabled. To enable the use of Flux queries, set the value to `true`.
 
 Environment variable: `INFLUXDB_HTTP_FLUX_ENABLED`
 
-#### `bind-address = ":8086"`
+#### `bind-address`
+
+Default is `":8086"`.
 
 The bind address used by the HTTP service.
 
 Environment variable: `INFLUXDB_HTTP_BIND_ADDRESS`
 
-#### `auth-enabled = false`
+#### `auth-enabled`
+
+Default is `false`.
 
 Enables HTTP authentication.
 
 Environment variable: `INFLUXDB_HTTP_AUTH_ENABLED`
 
-#### `realm = "InfluxDB"`
+#### `realm`
+
+Default is `"InfluxDB"`.
 
 The default realm sent back when issuing a basic authorization challenge.
 
 Environment variable: `INFLUXDB_HTTP_REALM`
 
-#### `log-enabled = true`
+#### `log-enabled`
+
+Default is `true`.
 
 Enables HTTP request logging.
 
 Environment variable: `INFLUXDB_HTTP_LOG_ENABLED`
 
-#### `suppress-write-log = false`
+#### `suppress-write-log`
+
+Default is `false`.
 
 Determines whether the HTTP write request logs should be suppressed when the log is enabled.
 
-#### `access-log-path = ""`
+#### `access-log-path`
+
+Default is `""`.
 
 The path to the access log, which determines whether detailed write logging is enabled using `log-enabled = true`.
 Specifies whether HTTP request logging is written to the specified path when enabled.
@@ -813,7 +999,9 @@ If `influxd` is unable to access the specified path, it will log an error and fa
 
 Environment variable: `INFLUXDB_HTTP_ACCESS_LOG_PATH`
 
-#### `access-log-status-filters = []`
+#### `access-log-status-filters`
+
+Default is `[]`.
 
 Filters which requests should be logged. Each filter is of the pattern `nnn`, `nnx`, or `nxx` where `n` is
 a number and `x` is the wildcard for any number.
@@ -843,26 +1031,34 @@ When using environment variables, the values can be supplied as follows.
 
 The `_n` at the end of the environment variable represents the array position of the entry.
 
-#### `write-tracing = false`
+#### `write-tracing`
+
+Default is `false`.
 
 Enables detailed write logging.
 
 Environment variable: `INFLUXDB_HTTP_WRITE_TRACING`
 
-#### `pprof-enabled = true`
+#### `pprof-enabled`
+
+Default is `true`.
 
 Determines whether the `/pprof` endpoint is enabled.  
 This endpoint is used for troubleshooting and monitoring.
 
 Environment variable: `INFLUXDB_HTTP_PPROF_ENABLED`
 
-#### `https-enabled = false`
+#### `https-enabled`
+
+Default is `false`.
 
 Enables HTTPS.
 
 Environment variable: `INFLUXDB_HTTP_HTTPS_ENABLED`
 
-#### `https-certificate = "/etc/ssl/influxdb.pem"`
+#### `https-certificate`
+
+Default is `"/etc/ssl/influxdb.pem"`.
 
 The SSL certificate to use when HTTPS is enabled.  
 The certificate should be a PEM-encoded bundle of the certificate and key.  
@@ -870,19 +1066,25 @@ If it is just the certificate, a key must be specified in `https-private-key`.
 
 Environment variable: `INFLUXDB_HTTP_HTTPS_CERTIFICATE`
 
-#### `https-private-key = ""`
+#### `https-private-key`
+
+Default is `""`.
 
 The location of the separate private key.
 
 Environment variable: `INFLUXDB_HTTP_HTTPS_PRIVATE_KEY`
 
-#### `shared-secret = ""`
+#### `shared-secret`
+
+Default is `""`.
 
 The JWT authorization shared secret used to validate requests using JSON web tokens (JWTs).
 
 Environment variable: `INFLUXDB_HTTP_SHARED_SECRET`
 
-#### `max-body-size = 25000000`
+#### `max-body-size`
+
+Default is `25000000`.
 
 The maximum size, in bytes, of a client request body.
 When a HTTP client sends data that exceeds the configured maximum size, a `413 Request Entity Too Large` HTTP response is returned.
@@ -890,7 +1092,9 @@ To disable the limit, set the value to `0`.
 
 Environment variable: `INFLUXDB_HTTP_MAX_BODY_SIZE`
 
-#### `max-row-limit = 0`
+#### `max-row-limit`
+
+Default is `0`.
 
 The default chunk size for result sets that should be chunked.
 The maximum number of rows that can be returned in a non-chunked query.
@@ -899,7 +1103,9 @@ InfluxDB includes a `"partial":true` tag in the response body if query results e
 
 Environment variable: `INFLUXDB_HTTP_MAX_ROW_LIMIT`
 
-#### `max-connection-limit = 0`
+#### `max-connection-limit`
+
+Default is `0`.
 
 The maximum number of HTTP connections that may be open at once.  
 New connections that would exceed this limit are dropped.  
@@ -907,33 +1113,43 @@ The default value of `0` disables the limit.
 
 Environment variable: `INFLUXDB_HTTP_MAX_CONNECTION_LIMIT`
 
-#### `unix-socket-enabled = false`
+#### `unix-socket-enabled`
+
+Default is `false`.
 
 Enables the HTTP service over the UNIX domain socket.
 
 Environment variable: `INFLUXDB_HTTP_UNIX_SOCKET_ENABLED`
 
-#### `bind-socket = "/var/run/influxdb.sock"`
+#### `bind-socket`
+
+Default is `"/var/run/influxdb.sock"`.
 
 The path of the UNIX domain socket.
 
 Environment variable: `INFLUXDB_HTTP_BIND_SOCKET`
 
-#### `max-concurrent-write-limit = 0`
+#### `max-concurrent-write-limit`
+
+Default is `0`.
 
 The maximum number of writes processed concurrently.
 The default value of `0` disables the limit.
 
 Environment variable: `INFLUXDB_HTTP_MAX_CONCURRENT_WRITE_LIMIT`
 
-#### `max-enqueued-write-limit = 0`
+#### `max-enqueued-write-limit`
+
+Default is `0`.
 
 The maximum number of writes queued for processing.
 The default value of `0` disables the limit.
 
 Environment variable: `INFLUXDB_HTTP_MAX_ENQUEUED_WRITE_LIMIT`
 
-#### `enqueued-write-timeout = 0`
+#### `enqueued-write-timeout`
+
+Default is `0`.
 
 The maximum duration for a write to wait in the queue to be processed.
 Setting this to `0` or setting `max-concurrent-write-limit` to `0` disables the limit.
@@ -944,7 +1160,9 @@ Setting this to `0` or setting `max-concurrent-write-limit` to `0` disables the
 
 ### `[logging]`
 
-#### `format = "logfmt"`
+#### `format`
+
+Default is `"logfmt"`.
 
 Determines which log encoder to use for logs.
 Valid options are `auto`, `logfmt`, and `json`.
@@ -953,13 +1171,17 @@ When the output is a non-TTY, `auto` will use `logfmt`.
 
 Environment variable: `INFLUXDB_LOGGING_FORMAT`
 
-#### `level = "info"`
+#### `level`
+
+Default is `"info"`.
 
 Determines which level of logs will be emitted.
 
 Environment variable: `INFLUXDB_LOGGING_LEVEL`
 
-#### `suppress-logo = false`
+#### `suppress-logo`
+
+Default is `false`.
 
 Suppresses the logo output that is printed when the program is started.
 
@@ -973,45 +1195,59 @@ Environment variable: `INFLUXDB_LOGGING_SUPPRESS_LOGO`
 
 Controls the subscriptions, which can be used to fork a copy of all data received by the InfluxDB host.
 
-#### `enabled = true`
+#### `enabled`
+
+Default is `true`.
 
 Determines whether the subscriber service is enabled.
 
 Environment variable: `INFLUXDB_SUBSCRIBER_ENABLED`
 
-#### `http-timeout = "30s"`
+#### `http-timeout`
+
+Default is `"30s"`.
 
 The default timeout for HTTP writes to subscribers.
 
 Environment variable: `INFLUXDB_SUBSCRIBER_HTTP_TIMEOUT`
 
-#### `insecure-skip-verify = false`
+#### `insecure-skip-verify`
+
+Default is `false`.
 
 Allows insecure HTTPS connections to subscribers.
 This option is useful when testing with self-signed certificates.
 
 Environment variable: `INFLUXDB_SUBSCRIBER_INSECURE_SKIP_VERIFY`
 
-#### `ca-certs = ""`
+#### `ca-certs`
+
+Default is `""`.
 
 The path to the PEM-encoded CA certs file.
 If the set to the empty string (`""`), the default system certs will used.
 
 Environment variable: `INFLUXDB_SUBSCRIBER_CA_CERTS`
 
-#### `write-concurrency = 40`
+#### `write-concurrency`
+
+Default is `40`.
 
 The number of writer Goroutines processing the write channel.
 
 Environment variable: `INFLUXDB_SUBSCRIBER_WRITE_CONCURRENCY`
 
-#### `write-buffer-size = 1000`
+#### `write-buffer-size`
+
+Default is `1000`.
 
 The number of in-flight writes buffered in the write channel.
 
 Environment variable: `INFLUXDB_SUBSCRIBER_WRITE_BUFFER_SIZE`
 
-#### `total-buffer-bytes = 0`
+#### `total-buffer-bytes`
+
+Default is `0`.
 
 Total number of bytes allocated to buffering across all subscriptions.
 Each named subscription receives an equal share of the total.
@@ -1029,7 +1265,9 @@ Environment variable: `INFLUXDB_SUBSCRIBER_TOTAL_BUFFER_BYTES`
 This section controls one or many listeners for Graphite data.
 For more information, see [Graphite protocol support in InfluxDB](/enterprise_influxdb/v1.9/supported_protocols/graphite/).
 
-#### `enabled = false`
+#### `enabled`
+
+Default is `false`.
 
 Determines whether the graphite endpoint is enabled.
 
@@ -1045,27 +1283,39 @@ Batching will buffer points in memory if you have many coming in.
 # consistency-level = "one"
 ```
 
-#### `batch-size = 5000`
+#### `batch-size`
+
+Default is `5000`.
 
 Flush if this many points get buffered.
 
-#### `batch-pending = 10`
+#### `batch-pending`
+
+Default is `10`.
 
 The number of batches that may be pending in memory.
 
-#### `batch-timeout = "1s"`
+#### `batch-timeout`
+
+Default is `"1s"`.
 
 Flush at least this often even if we haven't hit buffer limit.
 
-#### `udp-read-buffer = 0`
+#### `udp-read-buffer`
+
+Default is `0`.
 
 UDP Read buffer size, `0` means OS default. UDP listener will fail if set above OS max.
 
-#### `separator = "."`
+#### `separator`
+
+Default is `"."`.
 
 This string joins multiple matching 'measurement' values providing more control over the final measurement name.
 
-#### `tags = ["region=us-east", "zone=1c"]`
+#### `tags`
+
+Default is `["region=us-east", "zone=1c"]`.
 
 Default tags that will be added to all metrics.  
 These can be overridden at the template level or by tags extracted from metric.
@@ -1096,18 +1346,24 @@ For more information, see [CollectD protocol support in InfluxDB](/enterprise_in
 ### `[[collectd]]`
 
 ```toml
-# enabled = false
+# enabled`
+
+Default is `false.
 # bind-address = ":25826"
 # database = "collectd"
 # retention-policy = ""
 # typesdb = "/usr/share/collectd/types.db"
 ```
 
-#### `security-level = ""`
+#### `security-level`
+
+Default is `""`.
 
 The collectd security level can be "" (or "none"), "sign", or "encrypt".
 
-#### `auth-file = ""`
+#### `auth-file`
+
+Default is `""`.
 
 The path to the `collectd` authorization file.
 Must be set if security level is sign or encrypt.
@@ -1117,19 +1373,27 @@ These next lines control how batching works.
 You should have this enabled otherwise you could get dropped metrics or poor performance.
 Batching will buffer points in memory if you have many coming in.
 
-#### `batch-size = 5000`
+#### `batch-size`
+
+Default is `5000`.
 
 Flush if this many points get buffered.
 
-#### `batch-pending = 10`
+#### `batch-pending`
+
+Default is `10`.
 
 The number of batches that may be pending in memory.
 
-#### `batch-timeout = "10s"`
+#### `batch-timeout`
+
+Default is `"10s"`.
 
 Flush at least this often even if we haven't hit buffer limit.
 
-#### `read-buffer = 0`
+#### `read-buffer`
+
+Default is `0`.
 
 UDP Read buffer size, 0 means OS default. UDP listener will fail if set above OS max.
 
@@ -1152,7 +1416,9 @@ For more information, see [OpenTSDB protocol support in InfluxDB](/enterprise_in
 # certificate= "/etc/ssl/influxdb.pem"
 ```
 
-#### `log-point-errors = true`
+#### `log-point-errors`
+
+Default is `true`.
 
 Log an error for every malformed point.
 
@@ -1162,15 +1428,21 @@ These next lines control how batching works.
 You should have this enabled otherwise you could get dropped metrics or poor performance.
 Only points metrics received over the telnet protocol undergo batching.
 
-#### `batch-size = 1000`
+#### `batch-size`
+
+Default is `1000`.
 
 Flush if this many points get buffered.
 
-#### `batch-pending = 5`
+#### `batch-pending`
+
+Default is `5`.
 
 The number of batches that may be pending in memory.
 
-#### `batch-timeout = "1s"`
+#### `batch-timeout`
+
+Default is `"1s"`.
 
 Flush at least this often even if we haven't hit buffer limit.
 
@@ -1190,26 +1462,36 @@ For more information, see [UDP protocol support in InfluxDB](/enterprise_influxd
 # retention-policy = ""
 ```
 
-#### `precision = ""`
+#### `precision`
+
+Default is `""`.
 
 InfluxDB precision for timestamps on received points ("" or "n", "u", "ms", "s", "m", "h")
 
 These next lines control how batching works. You should have this enabled otherwise you could get dropped metrics or poor performance.
 Batching will buffer points in memory if you have many coming in.
 
-#### `batch-size = 5000`
+#### `batch-size`
+
+Default is `5000`.
 
 Flush if this many points get buffered.
 
-#### `batch-pending = 10`
+#### `batch-pending`
+
+Default is `10`.
 
 The number of batches that may be pending in memory.
 
-#### `batch-timeout = "1s"`
+#### `batch-timeout`
+
+Default is `"1s"`.
 
 Will flush at least this often even if we haven't hit buffer limit.
 
-#### `read-buffer = 0`
+#### `read-buffer`
+
+Default is `0`.
 
 UDP Read buffer size, 0 means OS default. UDP listener will fail if set above OS max.
 
@@ -1221,25 +1503,33 @@ UDP Read buffer size, 0 means OS default. UDP listener will fail if set above OS
 
 Controls how continuous queries are run within InfluxDB.
 
-#### `enabled = true`
+#### `enabled`
+
+Default is `true`.
 
 Determines whether the continuous query service is enabled.
 
 Environment variable: `INFLUXDB_CONTINUOUS_QUERIES_ENABLED`
 
-#### `log-enabled = true`
+#### `log-enabled`
+
+Default is `true`.
 
 Controls whether queries are logged when executed by the CQ service.
 
 Environment variable: `INFLUXDB_CONTINUOUS_QUERIES_LOG_ENABLED`
 
-#### `query-stats-enabled = false`
+#### `query-stats-enabled`
+
+Default is `false`.
 
 Write continuous query execution statistics to the default monitor store.
 
 Environment variable: `INFLUXDB_CONTINUOUS_QUERIES_QUERY_STATS_ENABLED`
 
-#### `run-interval = "1s"`
+#### `run-interval`
+
+Default is `"1s"`.
 
 The interval for how often continuous queries will be checked whether they need to run.
 
@@ -1281,7 +1571,9 @@ max-version = "tls1.3"
 
 ```
 
-#### `min-version = "tls1.3"`
+#### `min-version`
+
+Default is `"tls1.3"`.
 
 Minimum version of the TLS protocol that will be negotiated.
 Valid values include: `tls1.0`, `tls1.1`, and `tls1.3`.
@@ -1290,7 +1582,9 @@ In this example, `tls1.3` specifies the minimum version as TLS 1.3.
 
 Environment variable: `INFLUXDB_TLS_MIN_VERSION`
 
-#### `max-version = "tls1.3"`
+#### `max-version`
+
+Default is `"tls1.3"`.
 
 The maximum version of the TLS protocol that will be negotiated.
 Valid values include: `tls1.0`, `tls1.1`, and `tls1.3`.
@@ -1306,27 +1600,28 @@ Environment variable: `INFLUXDB_TLS_MAX_VERSION`
 This section contains configuration settings for Flux query management.
 For more on managing queries, see [Query Management](/enterprise_influxdb/v1.9/troubleshooting/query_management/).
 
-#### query-concurrency
+#### `query-concurrency`
+
 Number of queries allowed to execute concurrently.
 `0` means unlimited.
 Default is `0`.
 
-#### query-initial-memory-bytes
+#### `query-initial-memory-bytes`
 Initial bytes of memory allocated for a query.
 `0` means unlimited.
 Default is `0`.
 
-#### query-max-memory-bytes
+#### `query-max-memory-bytes`
 Maximum total bytes of memory allowed for an individual query.
 `0` means unlimited.
 Default is `0`.
 
-#### total-max-memory-bytes
+#### `total-max-memory-bytes`
 Maximum total bytes of memory allowed for all running Flux queries.
 `0` means unlimited.
 Default is `0`.
 
-#### query-queue-size
+#### `query-queue-size`
 Maximum number of queries allowed in execution queue.
 When queue limit is reached, new queries are rejected.
 `0` means unlimited.
diff --git a/content/enterprise_influxdb/v1.9/administration/configure/config-meta-nodes.md b/content/enterprise_influxdb/v1.9/administration/configure/config-meta-nodes.md
index f1da803fe..0479edaeb 100644
--- a/content/enterprise_influxdb/v1.9/administration/configure/config-meta-nodes.md
+++ b/content/enterprise_influxdb/v1.9/administration/configure/config-meta-nodes.md
@@ -21,7 +21,9 @@ aliases:
 
 ### Global options
 
-#### `reporting-disabled = false`
+#### `reporting-disabled`
+
+Default is `false`.
 
 InfluxData, the company, relies on reported data from running nodes primarily to
 track the adoption rates of different InfluxDB versions.
@@ -35,12 +37,16 @@ To disable reporting, set this option to `true`.
 
 > **Note:** No data from user databases are ever transmitted.
 
-#### `bind-address = ""`
+#### `bind-address`
+
+Default is `""`.
 
 This setting is not intended for use.
 It will be removed in future versions.
 
-#### `hostname = ""`
+#### `hostname`
+
+Default is `""`.
 
 The hostname of the [meta node](/enterprise_influxdb/v1.9/concepts/glossary/#meta-node).
 This must be resolvable and reachable by all other members of the cluster.
@@ -55,7 +61,9 @@ Environment variable: `INFLUXDB_HOSTNAME`
 The `[enterprise]` section contains the parameters for the meta node's
 registration with the [InfluxData portal](https://portal.influxdata.com/).
 
-#### `license-key = ""`
+#### `license-key`
+
+Default is `""`.
 
 The license key created for you on [InfluxData portal](https://portal.influxdata.com).
 The meta node transmits the license key to
@@ -72,7 +80,9 @@ Use the same key for all nodes in the same cluster.
 
 Environment variable: `INFLUXDB_ENTERPRISE_LICENSE_KEY`
 
-#### `license-path = ""`
+#### `license-path`
+
+Default is `""`.
 
 The local path to the permanent JSON license file that you received from InfluxData
 for instances that do not have access to the internet.
@@ -96,13 +106,17 @@ Environment variable: `INFLUXDB_ENTERPRISE_LICENSE_PATH`
 
 #### `[meta]`
 
-#### `dir = "/var/lib/influxdb/meta"`
+#### `dir`
+
+Default is `"/var/lib/influxdb/meta"`.
 
 The directory where cluster meta data is stored.
 
 Environment variable: `INFLUXDB_META_DIR`
 
-#### `bind-address = ":8089"`
+#### `bind-address`
+
+Default is `":8089"`.
 
 The bind address(port) for meta node communication.
 For simplicity, InfluxData recommends using the same port on all meta nodes,
@@ -110,13 +124,17 @@ but this is not necessary.
 
 Environment variable: `INFLUXDB_META_BIND_ADDRESS`
 
-#### `http-bind-address = ":8091"`
+#### `http-bind-address`
+
+Default is `":8091"`.
 
 The default address to bind the API to.
 
 Environment variable: `INFLUXDB_META_HTTP_BIND_ADDRESS`
 
-#### `https-enabled = false`
+#### `https-enabled`
+
+Default is `false`.
 
 Determines whether meta nodes use HTTPS to communicate with each other. By default, HTTPS is disabled. We strongly recommend enabling HTTPS.
 
@@ -124,7 +142,9 @@ To enable HTTPS, set https-enabled to `true`, specify the path to the SSL certif
 
 Environment variable: `INFLUXDB_META_HTTPS_ENABLED`
 
-#### `https-certificate = ""`
+#### `https-certificate`
+
+Default is `""`.
 
 If HTTPS is enabled, specify the path to the SSL certificate.  
 Use either:
@@ -134,7 +154,9 @@ Use either:
 
 Environment variable: `INFLUXDB_META_HTTPS_CERTIFICATE`
 
-#### `https-private-key = ""`
+#### `https-private-key`
+
+Default is `""`.
 
 If HTTPS is enabled, specify the path to the SSL private key.
 Use either:
@@ -144,43 +166,61 @@ Use either:
 
 Environment variable: `INFLUXDB_META_HTTPS_PRIVATE_KEY`
 
-#### `https-insecure-tls = false`
+#### `https-insecure-tls`
+
+Default is `false`.
 
 Whether meta nodes will skip certificate validation communicating with each other over HTTPS.
 This is useful when testing with self-signed certificates.
 
 Environment variable: `INFLUXDB_META_HTTPS_INSECURE_TLS`
 
-#### `data-use-tls = false`
+#### `data-use-tls`
+
+Default is `false`.
 
 Whether to use TLS to communicate with data nodes.
 
-#### `data-insecure-tls = false`
+#### `data-insecure-tls`
+
+Default is `false`.
 
 Whether meta nodes will skip certificate validation communicating with data nodes over TLS.
 This is useful when testing with self-signed certificates.
 
-#### `gossip-frequency = "5s"`
+#### `gossip-frequency`
+
+Default is `"5s"`.
 
 The default frequency with which the node will gossip its known announcements.
 
-#### `announcement-expiration = "30s"`
+#### `announcement-expiration`
+
+Default is `"30s"`.
 
 The default length of time an announcement is kept before it is considered too old.
 
-#### `retention-autocreate = true`
+#### `retention-autocreate`
+
+Default is `true`.
 
 Automatically create a default retention policy when creating a database.
 
-#### `election-timeout = "1s"`
+#### `election-timeout`
+
+Default is `"1s"`.
 
 The amount of time in candidate state without a leader before we attempt an election.
 
-#### `heartbeat-timeout = "1s"`
+#### `heartbeat-timeout`
+
+Default is `"1s"`.
 
 The amount of time in follower state without a leader before we attempt an election.
 
-#### `leader-lease-timeout = "500ms"`
+#### `leader-lease-timeout`
+
+Default is `"500ms"`.
 
 The leader lease timeout is the amount of time a Raft leader will remain leader
  if it does not hear from a majority of nodes.
@@ -190,7 +230,9 @@ Clusters with high latency between nodes may want to increase this parameter to
 
 Environment variable: `INFLUXDB_META_LEADER_LEASE_TIMEOUT`
 
-#### `commit-timeout = "50ms"`
+#### `commit-timeout`
+
+Default is `"50ms"`.
 
 The commit timeout is the amount of time a Raft node will tolerate between
 commands before issuing a heartbeat to tell the leader it is alive.
@@ -198,33 +240,53 @@ The default setting should work for most systems.
 
 Environment variable: `INFLUXDB_META_COMMIT_TIMEOUT`
 
-#### `consensus-timeout = "30s"`
+#### `consensus-timeout`
+
+Default is `"30s"`.
 
 Timeout waiting for consensus before getting the latest Raft snapshot.
 
 Environment variable: `INFLUXDB_META_CONSENSUS_TIMEOUT`
 
-#### `cluster-tracing = false`
+#### `cluster-tracing`
 
-Cluster tracing toggles the logging of Raft logs on Raft nodes.
-Enable this setting when debugging Raft consensus issues.
+Default is `false`.
+
+Log all HTTP requests made to meta nodes.
+Prints sanitized POST request information to show actual commands.
+
+**Sample log output:**
+
+```
+ts=2021-12-08T02:00:54.864731Z lvl=info msg=weblog log_id=0YHxBFZG001 service=meta-http host=172.18.0.1 user-id= username=admin method=POST uri=/user protocol=HTTP/1.1 command="{'{\"action\":\"create\",\"user\":{\"name\":\"fipple\",\"password\":[REDACTED]}}': ''}" status=307 size=0 referrer= user-agent=curl/7.68.0 request-id=ad87ce47-57ca-11ec-8026-0242ac120004 execution-time=63.571ms execution-time-readable=63.570738ms
+ts=2021-12-08T02:01:00.070137Z lvl=info msg=weblog log_id=0YHxBEhl001 service=meta-http host=172.18.0.1 user-id= username=admin method=POST uri=/user protocol=HTTP/1.1 command="{'{\"action\":\"create\",\"user\":{\"name\":\"fipple\",\"password\":[REDACTED]}}': ''}" status=200 size=0 referrer= user-agent=curl/7.68.0 request-id=b09eb13a-57ca-11ec-800d-0242ac120003 execution-time=85.823ms execution-time-readable=85.823406ms
+ts=2021-12-08T02:01:29.062313Z lvl=info msg=weblog log_id=0YHxBEhl001 service=meta-http host=172.18.0.1 user-id= username=admin method=POST uri=/user protocol=HTTP/1.1 command="{'{\"action\":\"create\",\"user\":{\"name\":\"gremch\",\"hash\":[REDACTED]}}': ''}" status=200 size=0 referrer= user-agent=curl/7.68.0 request-id=c1f3614a-57ca-11ec-8015-0242ac120003 execution-time=1.722ms execution-time-readable=1.722089ms
+ts=2021-12-08T02:01:47.457607Z lvl=info msg=weblog log_id=0YHxBEhl001 service=meta-http host=172.18.0.1 user-id= username=admin method=POST uri=/user protocol=HTTP/1.1 command="{'{\"action\":\"create\",\"user\":{\"name\":\"gremchy\",\"hash\":[REDACTED]}}': ''}" status=400 size=37 referrer= user-agent=curl/7.68.0 request-id=ccea84b7-57ca-11ec-8019-0242ac120003 execution-time=0.154ms execution-time-readable=154.417µs
+ts=2021-12-08T02:02:05.522571Z lvl=info msg=weblog log_id=0YHxBEhl001 service=meta-http host=172.18.0.1 user-id= username=admin method=POST uri=/user protocol=HTTP/1.1 command="{'{\"action\":\"create\",\"user\":{\"name\":\"thimble\",\"password\":[REDACTED]}}': ''}" status=400 size=37 referrer= user-agent=curl/7.68.0 request-id=d7af0082-57ca-11ec-801f-0242ac120003 execution-time=0.227ms execution-time-readable=227.853µs
+```
 
 Environment variable: `INFLUXDB_META_CLUSTER_TRACING`
 
-#### `logging-enabled = true`
+#### `logging-enabled`
+
+Default is `true`.
 
 Meta logging toggles the logging of messages from the meta service.
 
 Environment variable: `INFLUXDB_META_LOGGING_ENABLED`
 
-#### `pprof-enabled = true`
+#### `pprof-enabled`
+
+Default is `true`.
 
 Enables the `/debug/pprof` endpoint for troubleshooting.
 To disable, set the value to `false`.
 
 Environment variable: `INFLUXDB_META_PPROF_ENABLED`
 
-#### `lease-duration = "1m0s"`
+#### `lease-duration`
+
+Default is `"1m0s"`.
 
 The default duration of the leases that data nodes acquire from the meta nodes.
 Leases automatically expire after the `lease-duration` is met.
@@ -238,35 +300,45 @@ For more details about `lease-duration` and its impact on continuous queries, se
 
 Environment variable: `INFLUXDB_META_LEASE_DURATION`
 
-#### `auth-enabled = false`
+#### `auth-enabled`
+
+Default is `false`.
 
 If true, HTTP endpoints require authentication.
 This setting must have the same value as the data nodes' meta.meta-auth-enabled configuration.
 
-#### `ldap-allowed = false`
+#### `ldap-allowed`
+
+Default is `false`.
 
 Whether LDAP is allowed to be set.
 If true, you will need to use `influxd ldap set-config` and set enabled=true to use LDAP authentication.
 
-#### `shared-secret = ""`
+#### `shared-secret`
+
+Default is `""`.
 
 The shared secret to be used by the public API for creating custom JWT authentication.
-If you use this setting, set [`auth-enabled`](#auth-enabled-false) to `true`.
+If you use this setting, set [`auth-enabled`](#auth-enabled) to `true`.
 
 Environment variable: `INFLUXDB_META_SHARED_SECRET`
 
-#### `internal-shared-secret = ""`
+#### `internal-shared-secret`
+
+Default is `""`.
 
 The shared secret used by the internal API for JWT authentication for
 inter-node communication within the cluster.
 Set this to a long pass phrase.
 This value must be the same value as the
 [`[meta] meta-internal-shared-secret`](/enterprise_influxdb/v1.9/administration/config-data-nodes#meta-internal-shared-secret) in the data node configuration file.
-To use this option, set [`auth-enabled`](#auth-enabled-false) to `true`.
+To use this option, set [`auth-enabled`](#auth-enabled) to `true`.
 
 Environment variable: `INFLUXDB_META_INTERNAL_SHARED_SECRET`
 
-#### `password-hash = "bcrypt"`
+#### `password-hash`
+
+Default is `"bcrypt"`.
 
 Specifies the password hashing scheme and its configuration.
 
@@ -279,7 +351,7 @@ Optional sections after this are `key=value` password hash configuration options
 Each scheme has its own set of options.
 Any options not specified default to reasonable values as specified below.
 
-This setting must have the same value as the data node option [`meta.password-hash`](/enterprise_influxdb/v1.9/administration/config-data-nodes/#password-hash--bcrypt).
+This setting must have the same value as the data node option [`meta.password-hash`](/enterprise_influxdb/v1.9/administration/config-data-nodes/#password-hash).
 
 Environment variable: `INFLUXDB_META_PASSWORD_HASH`
 
@@ -352,7 +424,9 @@ when used with appropriate `rounds` and `salt_len` options.
   * Must be greater than or equal to `16`
     for FIPS-readiness according to [NIST Special Publication 800-132] § 5.1.
 
-#### `ensure-fips = false`
+#### `ensure-fips`
+
+Default is `false`.
 
 If `ensure-fips` is set to `true`, then `influxd` and `influxd-meta`
 will refuse to start if they are not configured in a FIPS-ready manner.
diff --git a/content/enterprise_influxdb/v1.9/administration/configure/ports.md b/content/enterprise_influxdb/v1.9/administration/configure/ports.md
index 407593027..5ae29a6b9 100644
--- a/content/enterprise_influxdb/v1.9/administration/configure/ports.md
+++ b/content/enterprise_influxdb/v1.9/administration/configure/ports.md
@@ -20,7 +20,7 @@ aliases:
 The default port that runs the InfluxDB HTTP service.
 It is used for the primary public write and query API.
 Clients include the CLI, Chronograf, InfluxDB client libraries, Grafana, curl, or anything that wants to write and read time series data to and from InfluxDB.
-[Configure this port](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes/#bind-address--8086)
+[Configure this port](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes/#bind-address)
 in the data node configuration file.
 
 _See also: [API Reference](/enterprise_influxdb/v1.9/tools/api/)._
@@ -34,7 +34,7 @@ It's also used by meta nodes for cluster-type operations (e.g., tell a data node
 
 This is the default port used for RPC calls used for inter-node communication and by the CLI for backup and restore operations
 (`influxdb backup` and `influxd restore`).
-[Configure this port](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes/#bind-address--8088)
+[Configure this port](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes/#bind-address)
 in the configuration file.
 
 This port should not be exposed outside the cluster.
diff --git a/content/enterprise_influxdb/v1.9/administration/configure/security/authentication.md b/content/enterprise_influxdb/v1.9/administration/configure/security/authentication.md
index 7cef96fcd..e37ae1c39 100644
--- a/content/enterprise_influxdb/v1.9/administration/configure/security/authentication.md
+++ b/content/enterprise_influxdb/v1.9/administration/configure/security/authentication.md
@@ -47,7 +47,7 @@ For a more secure alternative to using passwords, include JWT tokens in requests
 
    InfluxDB Enterprise uses the shared secret to encode the JWT signature.
    By default, `shared-secret` is set to an empty string (no JWT authentication).
-   Add a custom shared secret in your [InfluxDB configuration file](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes/#shared-secret--)
+   Add a custom shared secret in your [InfluxDB configuration file](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes/#shared-secret)
    for each meta and data node.
    Longer strings are more secure:
 
diff --git a/content/enterprise_influxdb/v1.9/administration/configure/security/configure-password-hashing.md b/content/enterprise_influxdb/v1.9/administration/configure/security/configure-password-hashing.md
index 2e27a86a1..8e1e7c343 100644
--- a/content/enterprise_influxdb/v1.9/administration/configure/security/configure-password-hashing.md
+++ b/content/enterprise_influxdb/v1.9/administration/configure/security/configure-password-hashing.md
@@ -83,5 +83,5 @@ run: create server: passwordhash: not FIPS-ready: config: 'bcrypt'
 ```
 
 [FIPS]: https://csrc.nist.gov/publications/detail/fips/140/3/final
-[`password-hash`]: /enterprise_influxdb/v1.9/administration/config-meta-nodes/#password-hash--bcrypt
-[`ensure-fips`]: /enterprise_influxdb/v1.9/administration/config-meta-nodes/#ensure-fips--false
+[`password-hash`]: /enterprise_influxdb/v1.9/administration/config-meta-nodes/#password-hash
+[`ensure-fips`]: /enterprise_influxdb/v1.9/administration/config-meta-nodes/#ensure-fips
diff --git a/content/enterprise_influxdb/v1.9/administration/configure/security/enable_tls.md b/content/enterprise_influxdb/v1.9/administration/configure/security/enable_tls.md
index 783f36067..651af58cc 100644
--- a/content/enterprise_influxdb/v1.9/administration/configure/security/enable_tls.md
+++ b/content/enterprise_influxdb/v1.9/administration/configure/security/enable_tls.md
@@ -264,6 +264,7 @@ Also change `localhost` to the relevant domain name.
 The best practice in terms of security is to transfer the certificate to the client and make it trusted
 (either by putting in the operating system's trusted certificate system or using the `ssl_ca` option).
 The alternative is to sign the certificate using an internal CA and then trust the CA certificate.
+Provide the file paths of your key and certificate to the InfluxDB output plugin as shown below.
 
 If you're using a self-signed certificate,
 uncomment the `insecure_skip_verify` setting and set it to `true`.
@@ -284,7 +285,8 @@ uncomment the `insecure_skip_verify` setting and set it to `true`.
 [...]
 
   ## Optional SSL Config
-  [...]
+  tls_cert = "/etc/telegraf/cert.pem"
+  tls_key = "/etc/telegraf/key.pem"
   insecure_skip_verify = true # <-- Update only if you're using a self-signed certificate
 ```
 
diff --git a/content/enterprise_influxdb/v1.9/administration/monitor/_index.md b/content/enterprise_influxdb/v1.9/administration/monitor/_index.md
index 13043f909..975fde693 100644
--- a/content/enterprise_influxdb/v1.9/administration/monitor/_index.md
+++ b/content/enterprise_influxdb/v1.9/administration/monitor/_index.md
@@ -24,7 +24,7 @@ InfluxDB Aware and Influx Insights is a free Enterprise service that sends your
 Aware assists you in monitoring your data by yourself.
 Insights assists you in monitoring your data with the help of the support team.
 
-To apply for this service, please contact the [support team](support@influxdata.com).
+To apply for this service, please contact the [support team](https://support.influxdata.com/s/login/).
 {{% /note %}}
 
 {{< children >}}
diff --git a/content/enterprise_influxdb/v1.9/administration/monitor/monitor-with-cloud.md b/content/enterprise_influxdb/v1.9/administration/monitor/monitor-with-cloud.md
index e9647bf86..73c19f5a4 100644
--- a/content/enterprise_influxdb/v1.9/administration/monitor/monitor-with-cloud.md
+++ b/content/enterprise_influxdb/v1.9/administration/monitor/monitor-with-cloud.md
@@ -32,7 +32,7 @@ Before you begin, make sure you have access to the following:
  - An InfluxDB Cloud account. ([Sign up for free here](https://cloud2.influxdata.com/signup)).
  - Command line access to a machine [running InfluxDB Enterprise 1.x](/enterprise_influxdb/v1.9/introduction/install-and-deploy/) and permissions to install Telegraf on this machine.
  - Internet connectivity from the machine running InfluxDB Enterprise 1.x and Telegraf to InfluxDB Cloud.
- - Sufficient resource availability to install the template. (InfluxDB Cloud Free Plan accounts include [resource limits](/influxdb/cloud/account-management/pricing-plans/#resource-limits/influxdb/cloud/account-management/pricing-plans/#resource-limits).)
+ - Sufficient resource availability to install the template. (InfluxDB Cloud Free Plan accounts include a finite number of [available resources](/influxdb/cloud/account-management/limits/#free-plan-limits).)
 
 ## Install the InfluxDB Enterprise Monitoring template
 
diff --git a/content/enterprise_influxdb/v1.9/administration/monitor/monitor-with-oss.md b/content/enterprise_influxdb/v1.9/administration/monitor/monitor-with-oss.md
index add587b44..4290509f2 100644
--- a/content/enterprise_influxdb/v1.9/administration/monitor/monitor-with-oss.md
+++ b/content/enterprise_influxdb/v1.9/administration/monitor/monitor-with-oss.md
@@ -8,6 +8,8 @@ menu:
     name: Monitor with OSS
     parent: Monitor
 weight: 101
+related:
+  - /platform/monitoring/influxdata-platform/tools/measurements-internal
 aliases:
   - /enterprise_influxdb/v1.9/administration/monitor-enterprise/monitor-with-oss/
 ---
diff --git a/content/enterprise_influxdb/v1.9/concepts/file-system-layout.md b/content/enterprise_influxdb/v1.9/concepts/file-system-layout.md
index 9ba97ed33..8ee209f71 100644
--- a/content/enterprise_influxdb/v1.9/concepts/file-system-layout.md
+++ b/content/enterprise_influxdb/v1.9/concepts/file-system-layout.md
@@ -28,19 +28,19 @@ The InfluxDB file structure includes the following:
 ### Data directory
 (**Data nodes only**)
 Directory path where InfluxDB Enterprise stores time series data (TSM files).
-To customize this path, use the [`[data].dir`](/enterprise_influxdb/v1.9/administration/config-data-nodes/#dir--varlibinfluxdbdata)
+To customize this path, use the [`[data].dir`](/enterprise_influxdb/v1.9/administration/config-data-nodes/#dir)
 configuration option.
 
 ### WAL directory
 (**Data nodes only**)
 Directory path where InfluxDB Enterprise stores Write Ahead Log (WAL) files.
-To customize this path, use the [`[data].wal-dir`](/enterprise_influxdb/v1.9/administration/config-data-nodes/#wal-dir--varlibinfluxdbwal)
+To customize this path, use the [`[data].wal-dir`](/enterprise_influxdb/v1.9/administration/config-data-nodes/#wal-dir)
 configuration option.
 
 ### Hinted handoff directory
 (**Data nodes only**)
 Directory path where hinted handoff (HH) queues are stored.
-To customize this path, use the [`[hinted-handoff].dir`](/enterprise_influxdb/v1.9/administration/config-data-nodes/#dir--varlibinfluxdbhh)
+To customize this path, use the [`[hinted-handoff].dir`](/enterprise_influxdb/v1.9/administration/config-data-nodes/#dir)
 configuration option.
 
 ### Metastore directory
@@ -48,10 +48,10 @@ Directory path of the InfluxDB Enterprise metastore, which stores information
 about the cluster, users, databases, retention policies, shards, and continuous queries.
 
 **On data nodes**, the metastore contains information about InfluxDB Enterprise meta nodes.
-To customize this path, use the [`[meta].dir` configuration option in your data node configuration file](/enterprise_influxdb/v1.9/administration/config-data-nodes/#dir--varlibinfluxdbmeta).
+To customize this path, use the [`[meta].dir` configuration option in your data node configuration file](/enterprise_influxdb/v1.9/administration/config-data-nodes/#dir).
 
 **On meta nodes**, the metastore contains information about the InfluxDB Enterprise RAFT cluster.
-To customize this path, use the [`[meta].dir` configuration option in your meta node configuration file](/enterprise_influxdb/v1.9/administration/config-meta-nodes/#dir--varlibinfluxdbmeta).
+To customize this path, use the [`[meta].dir` configuration option in your meta node configuration file](/enterprise_influxdb/v1.9/administration/config-meta-nodes/#dir).
 
 ### InfluxDB Enterprise configuration files
 InfluxDB Enterprise stores default data and meta node configuration file on disk.
diff --git a/content/enterprise_influxdb/v1.9/concepts/schema_and_data_layout.md b/content/enterprise_influxdb/v1.9/concepts/schema_and_data_layout.md
index 0d8e2ef4b..7b68d0570 100644
--- a/content/enterprise_influxdb/v1.9/concepts/schema_and_data_layout.md
+++ b/content/enterprise_influxdb/v1.9/concepts/schema_and_data_layout.md
@@ -126,9 +126,9 @@ The [Flux](/{{< latest "flux" >}}/) queries calculate the average `temp` for blu
 ```js
 // Query *Good Measurements*, data stored in separate tags (recommended)
 from(bucket: "<database>/<retention_policy>")
-  |> range(start:2016-08-30T00:00:00Z)
-  |> filter(fn: (r) =>  r._measurement == "weather_sensor" and r.region == "north" and r._field == "temp")
-  |> mean()
+    |> range(start:2016-08-30T00:00:00Z)
+    |> filter(fn: (r) =>  r._measurement == "weather_sensor" and r.region == "north" and r._field == "temp")
+    |> mean()
 ```
 
 **Difficult to query**: [_Bad Measurements_](#bad-measurements-schema) requires regular expressions to extract `plot` and `region` from the measurement, as in the following example.
@@ -136,9 +136,9 @@ from(bucket: "<database>/<retention_policy>")
 ```js
 // Query *Bad Measurements*, data encoded in the measurement (not recommended)
 from(bucket: "<database>/<retention_policy>")
-  |> range(start:2016-08-30T00:00:00Z)
-  |> filter(fn: (r) =>  r._measurement =~ /\.north$/ and r._field == "temp")
-  |> mean()
+    |> range(start:2016-08-30T00:00:00Z)
+    |> filter(fn: (r) =>  r._measurement =~ /\.north$/ and r._field == "temp")
+    |> mean()
 ```
 
 Complex measurements make some queries impossible. For example, calculating the average temperature of both plots is not possible with the [_Bad Measurements_](#bad-measurements-schema) schema.
@@ -188,15 +188,15 @@ Schema 2 is preferable because using multiple tags, you don't need a regular exp
 ```js
 // Schema 1 -  Query for multiple data encoded in a single tag
 from(bucket:"<database>/<retention_policy>")
-  |> range(start:2016-08-30T00:00:00Z)
-  |> filter(fn: (r) =>  r._measurement == "weather_sensor" and r.location =~ /\.north$/ and r._field == "temp")
-  |> mean()
+    |> range(start:2016-08-30T00:00:00Z)
+    |> filter(fn: (r) =>  r._measurement == "weather_sensor" and r.location =~ /\.north$/ and r._field == "temp")
+    |> mean()
 
 // Schema 2 - Query for data encoded in multiple tags
 from(bucket:"<database>/<retention_policy>")
-  |> range(start:2016-08-30T00:00:00Z)
-  |> filter(fn: (r) =>  r._measurement == "weather_sensor" and r.region == "north" and r._field == "temp")
-  |> mean()
+    |> range(start:2016-08-30T00:00:00Z)
+    |> filter(fn: (r) =>  r._measurement == "weather_sensor" and r.region == "north" and r._field == "temp")
+    |> mean()
 ```
 
 #### InfluxQL example to query schemas
diff --git a/content/enterprise_influxdb/v1.9/concepts/storage_engine.md b/content/enterprise_influxdb/v1.9/concepts/storage_engine.md
index f7cf01d5b..6c129482b 100644
--- a/content/enterprise_influxdb/v1.9/concepts/storage_engine.md
+++ b/content/enterprise_influxdb/v1.9/concepts/storage_engine.md
@@ -65,13 +65,13 @@ Deletes sent to the Cache will clear out the given key or the specific time rang
 
 The Cache exposes a few controls for snapshotting behavior.
 The two most important controls are the memory limits.
-There is a lower bound, [`cache-snapshot-memory-size`](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes/#cache-snapshot-memory-size--25m), which when exceeded will trigger a snapshot to TSM files and remove the corresponding WAL segments.
+There is a lower bound, [`cache-snapshot-memory-size`](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes/#cache-snapshot-memory-size), which when exceeded will trigger a snapshot to TSM files and remove the corresponding WAL segments.
 There is also an upper bound, [`cache-max-memory-size`](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes#cache-max-memory-size-1g), which when exceeded will cause the Cache to reject new writes.
 These configurations are useful to prevent out of memory situations and to apply back pressure to clients writing data faster than the instance can persist it.
 The checks for memory thresholds occur on every write.
 
 The other snapshot controls are time based.
-The idle threshold, [`cache-snapshot-write-cold-duration`](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes#cache-snapshot-write-cold-duration--10m), forces the Cache to snapshot to TSM files if it hasn't received a write within the specified interval.
+The idle threshold, [`cache-snapshot-write-cold-duration`](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes#cache-snapshot-write-cold-duration), forces the Cache to snapshot to TSM files if it hasn't received a write within the specified interval.
 
 The in-memory Cache is recreated on restart by re-reading the WAL files on disk.
 
diff --git a/content/enterprise_influxdb/v1.9/features/clustering-features.md b/content/enterprise_influxdb/v1.9/features/clustering-features.md
index 714b41277..cbed7323c 100644
--- a/content/enterprise_influxdb/v1.9/features/clustering-features.md
+++ b/content/enterprise_influxdb/v1.9/features/clustering-features.md
@@ -14,8 +14,7 @@ menu:
 _For an overview of InfluxDB Enterprise security features,
 see ["InfluxDB Enterprise features - Security"](/enterprise_influxdb/v1.9/features/#security).
 To secure your InfluxDB Enterprise cluster, see
-["Configure security"](/enterprise_influxdb/v1.9/administration/configure/security/)
-and ["Manage security"](/enterprise_influxdb/v1.9/administration/manage/security/)_.
+["Configure security"](/enterprise_influxdb/v1.9/administration/configure/security/).
 {{% /note %}}
 
 ## Entitlements
@@ -59,11 +58,11 @@ Subscriptions used by Kapacitor work in a cluster. Writes to any node will be fo
 It is important to understand how to configure InfluxDB Enterprise and how this impacts the continuous queries (CQ) engine’s behavior:
 
 - **Data node configuration** `[continuous queries]`
-[run-interval](/enterprise_influxdb/v1.9/administration/config-data-nodes#run-interval-1s)
+[run-interval](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes/#run-interval)
 -- The interval at which InfluxDB checks to see if a CQ needs to run. Set this option to the lowest interval
 at which your CQs run. For example, if your most frequent CQ runs every minute, set run-interval to 1m.
 - **Meta node configuration** `[meta]`
-[lease-duration](/enterprise_influxdb/v1.9/administration/config-meta-nodes#lease-duration-1m0s)
+[lease-duration](/enterprise_influxdb/v1.9/administration/configure/config-meta-nodes/#lease-duration)
 -- The default duration of the leases that data nodes acquire from the meta nodes. Leases automatically expire after the
 lease-duration is met.  Leases ensure that only one data node is running something at a given time. For example, Continuous
 Queries use a lease so that all data nodes aren’t running the same CQs at once.
diff --git a/content/enterprise_influxdb/v1.9/flux/_index.md b/content/enterprise_influxdb/v1.9/flux/_index.md
index 2c74b958f..fa15e8668 100644
--- a/content/enterprise_influxdb/v1.9/flux/_index.md
+++ b/content/enterprise_influxdb/v1.9/flux/_index.md
@@ -26,13 +26,10 @@ filtering that data by the `cpu` measurement and the `cpu=cpu-total` tag, window
 and calculating the average of each window:
 
 ```js
-from(bucket:"telegraf/autogen")
-  |> range(start:-1h)
-  |> filter(fn:(r) =>
-    r._measurement == "cpu" and
-    r.cpu == "cpu-total"
-  )
-  |> aggregateWindow(every: 1m, fn: mean)
+from(bucket: "telegraf/autogen")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "cpu" and r.cpu == "cpu-total")
+    |> aggregateWindow(every: 1m, fn: mean)
 ```
 
 {{< children >}}
diff --git a/content/enterprise_influxdb/v1.9/flux/flux-vs-influxql.md b/content/enterprise_influxdb/v1.9/flux/flux-vs-influxql.md
index c7ee8915a..a449f95a6 100644
--- a/content/enterprise_influxdb/v1.9/flux/flux-vs-influxql.md
+++ b/content/enterprise_influxdb/v1.9/flux/flux-vs-influxql.md
@@ -41,23 +41,14 @@ This opens the door for really powerful and useful operations.
 
 ```js
 dataStream1 = from(bucket: "bucket1")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "network" and
-    r._field == "bytes-transferred"
-  )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "network" and r._field == "bytes-transferred")
 
 dataStream2 = from(bucket: "bucket1")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "httpd" and
-    r._field == "requests-per-sec"
-    )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "httpd" and r._field == "requests-per-sec")
 
-join(
-    tables: {d1:dataStream1, d2:dataStream2},
-    on: ["_time", "_stop", "_start", "host"]
-  )
+join(tables: {d1: dataStream1, d2: dataStream2}, on: ["_time", "_stop", "_start", "host"])
 ```
 
 
@@ -76,31 +67,18 @@ joins them, then calculates the average amount of memory used per running proces
 ```js
 // Memory used (in bytes)
 memUsed = from(bucket: "telegraf/autogen")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "mem" and
-    r._field == "used"
-  )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used")
 
 // Total processes running
 procTotal = from(bucket: "telegraf/autogen")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "processes" and
-    r._field == "total"
-    )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "processes" and r._field == "total")
 
 // Join memory used with total processes and calculate
 // the average memory (in MB) used for running processes.
-join(
-    tables: {mem:memUsed, proc:procTotal},
-    on: ["_time", "_stop", "_start", "host"]
-  )
-  |> map(fn: (r) => ({
-    _time: r._time,
-    _value: (r._value_mem / r._value_proc) / 1000000
-  })
-)
+join(tables: {mem: memUsed, proc: procTotal}, on: ["_time", "_stop", "_start", "host"])
+    |> map(fn: (r) => ({_time: r._time, _value: r._value_mem / r._value_proc / 1000000}))
 ```
 
 ### Sort by tags
@@ -110,13 +88,10 @@ Flux's [`sort()` function](/{{< latest "flux" >}}/stdlib/universe/sort) sorts re
 Depending on the column type, records are sorted lexicographically, numerically, or chronologically.
 
 ```js
-from(bucket:"telegraf/autogen")
-  |> range(start:-12h)
-  |> filter(fn: (r) =>
-    r._measurement == "system" and
-    r._field == "uptime"
-  )
-  |> sort(columns:["region", "host", "_value"])
+from(bucket: "telegraf/autogen")
+    |> range(start: -12h)
+    |> filter(fn: (r) => r._measurement == "system" and r._field == "uptime")
+    |> sort(columns: ["region", "host", "_value"])
 ```
 
 ### Group by any column
@@ -127,9 +102,9 @@ to define which columns to group data by.
 
 ```js
 from(bucket:"telegraf/autogen")
-  |> range(start:-12h)
-  |> filter(fn: (r) => r._measurement == "system" and r._field == "uptime" )
-  |> group(columns:["host", "_value"])
+    |> range(start:-12h)
+    |> filter(fn: (r) => r._measurement == "system" and r._field == "uptime" )
+    |> group(columns:["host", "_value"])
 ```
 
 ### Window by calendar months and years
@@ -139,9 +114,9 @@ window and aggregate data by calendar month and year.
 
 ```js
 from(bucket:"telegraf/autogen")
-  |> range(start:-1y)
-  |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent" )
-  |> aggregateWindow(every: 1mo, fn: mean)
+    |> range(start:-1y)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent" )
+    |> aggregateWindow(every: 1mo, fn: mean)
 ```
 
 ### Work with multiple data sources
@@ -160,19 +135,19 @@ import "sql"
 
 csvData = csv.from(csv: rawCSV)
 sqlData = sql.from(
-  driverName: "postgres",
-  dataSourceName: "postgresql://user:password@localhost",
-  query:"SELECT * FROM example_table"
+    driverName: "postgres",
+    dataSourceName: "postgresql://user:password@localhost",
+    query: "SELECT * FROM example_table",
 )
 data = from(bucket: "telegraf/autogen")
-  |> range(start: -24h)
-  |> filter(fn: (r) => r._measurement == "sensor")
+    |> range(start: -24h)
+    |> filter(fn: (r) => r._measurement == "sensor")
 
 auxData = join(tables: {csv: csvData, sql: sqlData}, on: ["sensor_id"])
 enrichedData = join(tables: {data: data, aux: auxData}, on: ["sensor_id"])
 
 enrichedData
-  |> yield(name: "enriched_data")
+    |> yield(name: "enriched_data")
 ```
 
 ---
@@ -188,12 +163,9 @@ returns only data with time values in a specified hour range.
 
 ```js
 from(bucket: "telegraf/autogen")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "cpu" and
-    r.cpu == "cpu-total"
-  )
-  |> hourSelection(start: 9, stop: 17)
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "cpu" and r.cpu == "cpu-total")
+    |> hourSelection(start: 9, stop: 17)
 ```
 
 ### Pivot
@@ -203,16 +175,9 @@ to pivot data tables by specifying `rowKey`, `columnKey`, and `valueColumn` para
 
 ```js
 from(bucket: "telegraf/autogen")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "cpu" and
-    r.cpu == "cpu-total"
-  )
-  |> pivot(
-    rowKey:["_time"],
-    columnKey: ["_field"],
-    valueColumn: "_value"
-  )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "cpu" and r.cpu == "cpu-total")
+    |> pivot(rowKey: ["_time"], columnKey: ["_field"], valueColumn: "_value")
 ```
 
 ### Histograms
@@ -222,14 +187,9 @@ data to generate a cumulative histogram with support for other histogram types c
 
 ```js
 from(bucket: "telegraf/autogen")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "mem" and
-    r._field == "used_percent"
-  )
-  |> histogram(
-    buckets: [10, 20, 30, 40, 50, 60, 70, 80, 90, 100]
-  )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+    |> histogram(buckets: [10, 20, 30, 40, 50, 60, 70, 80, 90, 100,])
 ```
 
 ---
@@ -247,23 +207,19 @@ calculates the covariance between two data streams.
 ###### Covariance between two columns
 ```js
 from(bucket: "telegraf/autogen")
-  |> range(start:-5m)
-  |> covariance(columns: ["x", "y"])
+    |> range(start: -5m)
+    |> covariance(columns: ["x", "y"])
 ```
 
 ###### Covariance between two streams of data
 ```js
 table1 = from(bucket: "telegraf/autogen")
-  |> range(start: -15m)
-  |> filter(fn: (r) =>
-    r._measurement == "measurement_1"
-  )
+    |> range(start: -15m)
+    |> filter(fn: (r) => r._measurement == "measurement_1")
 
 table2 = from(bucket: "telegraf/autogen")
-  |> range(start: -15m)
-  |> filter(fn: (r) =>
-    r._measurement == "measurement_2"
-  )
+    |> range(start: -15m)
+    |> filter(fn: (r) => r._measurement == "measurement_2")
 
 cov(x: table1, y: table2, on: ["_time", "_field"])
 ```
@@ -277,12 +233,9 @@ operations like casting a boolean values to integers.
 ##### Cast boolean field values to integers
 ```js
 from(bucket: "telegraf/autogen")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "m" and
-    r._field == "bool_field"
-  )
-  |> toInt()
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "m" and r._field == "bool_field")
+    |> toInt()
 ```
 
 ### String manipulation and data shaping
@@ -295,17 +248,16 @@ functions in the string package allow for operations like string sanitization an
 import "strings"
 
 from(bucket: "telegraf/autogen")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "weather" and
-    r._field == "temp"
-  )
-  |> map(fn: (r) => ({
-    r with
-    location: strings.toTitle(v: r.location),
-    sensor: strings.replaceAll(v: r.sensor, t: " ", u: "-"),
-    status: strings.substring(v: r.status, start: 0, end: 8)
-  }))
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "weather" and r._field == "temp")
+    |> map(
+        fn: (r) => ({
+            r with
+            location: strings.toTitle(v: r.location),
+            sensor: strings.replaceAll(v: r.sensor, t: " ", u: "-"),
+            status: strings.substring(v: r.status, start: 0, end: 8),
+        })
+    )
 ```
 
 ### Work with geo-temporal data
@@ -317,14 +269,11 @@ let you shape, filter, and group geo-temporal data.
 import "experimental/geo"
 
 from(bucket: "geo/autogen")
-  |> range(start: -1w)
-  |> filter(fn: (r) => r._measurement == "taxi")
-  |> geo.shapeData(latField: "latitude", lonField: "longitude", level: 20)
-  |> geo.filterRows(
-    region: {lat: 40.69335938, lon: -73.30078125, radius: 20.0},
-    strict: true
-  )
-  |> geo.asTracks(groupBy: ["fare-id"])
+    |> range(start: -1w)
+    |> filter(fn: (r) => r._measurement == "taxi")
+    |> geo.shapeData(latField: "latitude", lonField: "longitude", level: 20)
+    |> geo.filterRows(region: {lat: 40.69335938, lon: -73.30078125, radius: 20.0}, strict: true)
+    |> geo.asTracks(groupBy: ["fare-id"])
 ```
 
 
diff --git a/content/enterprise_influxdb/v1.9/flux/get-started/query-influxdb.md b/content/enterprise_influxdb/v1.9/flux/get-started/query-influxdb.md
index c113e09a7..6132de337 100644
--- a/content/enterprise_influxdb/v1.9/flux/get-started/query-influxdb.md
+++ b/content/enterprise_influxdb/v1.9/flux/get-started/query-influxdb.md
@@ -47,11 +47,11 @@ or **absolute** using [timestamps](/{{< latest "flux" >}}/spec/lexical-elements#
 ```js
 // Relative time range with start only. Stop defaults to now.
 from(bucket:"telegraf/autogen")
-  |> range(start: -1h)
+    |> range(start: -1h)
 
 // Relative time range with start and stop
 from(bucket:"telegraf/autogen")
-  |> range(start: -1h, stop: -10m)
+    |> range(start: -1h, stop: -10m)
 ```
 
 > Relative ranges are relative to "now."
@@ -59,7 +59,7 @@ from(bucket:"telegraf/autogen")
 ###### Example absolute time range
 ```js
 from(bucket:"telegraf/autogen")
-  |> range(start: 2018-11-05T23:30:00Z, stop: 2018-11-06T00:00:00Z)
+    |> range(start: 2018-11-05T23:30:00Z, stop: 2018-11-06T00:00:00Z)
 ```
 
 #### Use the following:
@@ -67,7 +67,7 @@ For this guide, use the relative time range, `-15m`, to limit query results to d
 
 ```js
 from(bucket:"telegraf/autogen")
-  |> range(start: -15m)
+    |> range(start: -15m)
 ```
 
 ## 3. Filter your data
@@ -95,27 +95,19 @@ Use the `AND` relational operator to chain multiple filters.
 For this example, filter by the `cpu` measurement, the `usage_system` field, and the `cpu-total` tag value:
 
 ```js
-from(bucket:"telegraf/autogen")
-  |> range(start: -15m)
-  |> filter(fn: (r) =>
-    r._measurement == "cpu" and
-    r._field == "usage_system" and
-    r.cpu == "cpu-total"
-  )
+from(bucket: "telegraf/autogen")
+    |> range(start: -15m)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_system" and r.cpu == "cpu-total")
 ```
 
 ## 4. Yield your queried data
 Use Flux's `yield()` function to output the filtered tables as the result of the query.
 
 ```js
-from(bucket:"telegraf/autogen")
-  |> range(start: -15m)
-  |> filter(fn: (r) =>
-    r._measurement == "cpu" and
-    r._field == "usage_system" and
-    r.cpu == "cpu-total"
-  )
-  |> yield()
+from(bucket: "telegraf/autogen")
+    |> range(start: -15m)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_system" and r.cpu == "cpu-total")
+    |> yield()
 ```
 
 > Chronograf and the `influx` CLI automatically assume a `yield()` function at
diff --git a/content/enterprise_influxdb/v1.9/flux/get-started/syntax-basics.md b/content/enterprise_influxdb/v1.9/flux/get-started/syntax-basics.md
index 36c983beb..c4d98048a 100644
--- a/content/enterprise_influxdb/v1.9/flux/get-started/syntax-basics.md
+++ b/content/enterprise_influxdb/v1.9/flux/get-started/syntax-basics.md
@@ -132,22 +132,13 @@ or more input data streams.
 ```js
 timeRange = -1h
 
-cpuUsageUser =
-  from(bucket:"telegraf/autogen")
+cpuUsageUser = from(bucket: "telegraf/autogen")
     |> range(start: timeRange)
-    |> filter(fn: (r) =>
-      r._measurement == "cpu" and
-      r._field == "usage_user" and
-      r.cpu == "cpu-total"
-    )
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_user" and r.cpu == "cpu-total")
 
-memUsagePercent =
-  from(bucket:"telegraf/autogen")
+memUsagePercent = from(bucket: "telegraf/autogen")
     |> range(start: timeRange)
-    |> filter(fn: (r) =>
-      r._measurement == "mem" and
-      r._field == "used_percent"
-    )
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
 ```
 
 These variables can be used in other functions, such as  `join()`, while keeping the syntax minimal and flexible.
@@ -158,8 +149,7 @@ To do this, pass the input stream (`tables`) and the number of results to return
 Then using Flux's `sort()` and `limit()` functions to find the top `n` results in the data set.
 
 ```js
-topN = (tables=<-, n) =>
-  tables
+topN = (tables=<-, n) => tables
     |> sort(desc: true)
     |> limit(n: n)
 ```
@@ -171,8 +161,8 @@ find the top five data points and yield the results.
 
 ```js
 cpuUsageUser
-  |> topN(n:5)
-  |> yield()
+    |> topN(n: 5)
+    |> yield()
 ```
 {{% /tab-content %}}
 
@@ -182,8 +172,14 @@ A common use case for variable assignments in Flux is creating variables for mul
 
 ```js
 timeRange = -1h
-cpuUsageUser = from(bucket:"telegraf/autogen") |> range(start: timeRange) |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_user" and r.cpu == "cpu-total")
-memUsagePercent = from(bucket:"telegraf/autogen") |> range(start: timeRange) |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+
+cpuUsageUser = from(bucket: "telegraf/autogen")
+    |> range(start: timeRange)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_user" and r.cpu == "cpu-total")
+
+memUsagePercent = from(bucket: "telegraf/autogen")
+    |> range(start: timeRange)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
 ```
 
 These variables can be used in other functions, such as  `join()`, while keeping the syntax minimal and flexible.
diff --git a/content/enterprise_influxdb/v1.9/flux/get-started/transform-data.md b/content/enterprise_influxdb/v1.9/flux/get-started/transform-data.md
index 810da2057..25f8bf766 100644
--- a/content/enterprise_influxdb/v1.9/flux/get-started/transform-data.md
+++ b/content/enterprise_influxdb/v1.9/flux/get-started/transform-data.md
@@ -27,13 +27,9 @@ Use the query built in the previous [Query data from InfluxDB](/enterprise_influ
 guide, but update the range to pull data from the last hour:
 
 ```js
-from(bucket:"telegraf/autogen")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "cpu" and
-    r._field == "usage_system" and
-    r.cpu == "cpu-total"
-  )
+from(bucket: "telegraf/autogen")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_system" and r.cpu == "cpu-total")
 ```
 
 ## Flux functions
@@ -65,14 +61,10 @@ including **calendar months (`1mo`)** and **years (`1y`)**.
 For this example, window data in five minute intervals (`5m`).
 
 ```js
-from(bucket:"telegraf/autogen")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "cpu" and
-    r._field == "usage_system" and
-    r.cpu == "cpu-total"
-  )
-  |> window(every: 5m)
+from(bucket: "telegraf/autogen")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_system" and r.cpu == "cpu-total")
+    |> window(every: 5m)
 ```
 
 As data is gathered into windows of time, each window is output as its own table.
@@ -85,15 +77,11 @@ Flux aggregate functions take the `_value`s in each table and aggregate them in
 Use the [`mean()` function](/{{< latest "flux" >}}/stdlib/universe/mean) to average the `_value`s of each table.
 
 ```js
-from(bucket:"telegraf/autogen")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "cpu" and
-    r._field == "usage_system" and
-    r.cpu == "cpu-total"
-  )
-  |> window(every: 5m)
-  |> mean()
+from(bucket: "telegraf/autogen")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_system" and r.cpu == "cpu-total")
+    |> window(every: 5m)
+    |> mean()
 ```
 
 As rows in each window are aggregated, their output table contains only a single row with the aggregate value.
@@ -112,16 +100,12 @@ To add one, use the [`duplicate()` function](/{{< latest "flux" >}}/stdlib/unive
 to duplicate the `_stop` column as the `_time` column for each windowed table.
 
 ```js
-from(bucket:"telegraf/autogen")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "cpu" and
-    r._field == "usage_system" and
-    r.cpu == "cpu-total"
-  )
-  |> window(every: 5m)
-  |> mean()
-  |> duplicate(column: "_stop", as: "_time")
+from(bucket: "telegraf/autogen")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_system" and r.cpu == "cpu-total")
+    |> window(every: 5m)
+    |> mean()
+    |> duplicate(column: "_stop", as: "_time")
 ```
 
 ## Unwindow aggregate tables
@@ -130,17 +114,13 @@ Use the `window()` function with the `every: inf` parameter to gather all points
 into a single, infinite window.
 
 ```js
-from(bucket:"telegraf/autogen")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "cpu" and
-    r._field == "usage_system" and
-    r.cpu == "cpu-total"
-  )
-  |> window(every: 5m)
-  |> mean()
-  |> duplicate(column: "_stop", as: "_time")
-  |> window(every: inf)
+from(bucket: "telegraf/autogen")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_system" and r.cpu == "cpu-total")
+    |> window(every: 5m)
+    |> mean()
+    |> duplicate(column: "_stop", as: "_time")
+    |> window(every: inf)
 ```
 
 Once ungrouped and combined into a single table, the aggregate data points will appear connected in your visualization.
@@ -156,14 +136,10 @@ The same operation performed in this guide can be accomplished using the
 [`aggregateWindow()` function](/{{< latest "flux" >}}/stdlib/universe/aggregatewindow).
 
 ```js
-from(bucket:"telegraf/autogen")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "cpu" and
-    r._field == "usage_system" and
-    r.cpu == "cpu-total"
-  )
-  |> aggregateWindow(every: 5m, fn: mean)
+from(bucket: "telegraf/autogen")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_system" and r.cpu == "cpu-total")
+    |> aggregateWindow(every: 5m, fn: mean)
 ```
 
 ## Congratulations!
diff --git a/content/enterprise_influxdb/v1.9/flux/guides/_index.md b/content/enterprise_influxdb/v1.9/flux/guides/_index.md
index 58127501c..0cb506e17 100644
--- a/content/enterprise_influxdb/v1.9/flux/guides/_index.md
+++ b/content/enterprise_influxdb/v1.9/flux/guides/_index.md
@@ -23,11 +23,8 @@ which represents a basic query that filters data by measurement and field.
 
 ```js
 data = from(bucket: "db/rp")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "example-measurement" and
-    r._field == "example-field"
-  )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement" and r._field == "example-field")
 ```
 {{% /note %}}
 
diff --git a/content/enterprise_influxdb/v1.9/flux/guides/calculate-percentages.md b/content/enterprise_influxdb/v1.9/flux/guides/calculate-percentages.md
index ece9acba0..25acb37c9 100644
--- a/content/enterprise_influxdb/v1.9/flux/guides/calculate-percentages.md
+++ b/content/enterprise_influxdb/v1.9/flux/guides/calculate-percentages.md
@@ -36,10 +36,10 @@ _See [Pivot vs join](/enterprise_influxdb/v1.9/flux/guides/mathematic-operations
 
 ```js
 from(bucket: "db/rp")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "m1" and r._field =~ /field[1-2]/ )
-  |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
-  |> map(fn: (r) => ({ r with _value: r.field1 / r.field2 * 100.0 }))
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "m1" and r._field =~ /field[1-2]/)
+    |> pivot(rowKey: ["_time"], columnKey: ["_field"], valueColumn: "_value")
+    |> map(fn: (r) => ({r with _value: r.field1 / r.field2 * 100.0}))
 ```
 
 ## GPU monitoring example
@@ -54,8 +54,8 @@ Data includes the following:
 ### Query mem_used and mem_total fields
 ```js
 from(bucket: "gpu-monitor")
-  |> range(start: 2020-01-01T00:00:00Z)
-  |> filter(fn: (r) => r._measurement == "gpu" and r._field =~ /mem_/)
+    |> range(start: 2020-01-01T00:00:00Z)
+    |> filter(fn: (r) => r._measurement == "gpu" and r._field =~ /mem_/)
 ```
 
 ###### Returns the following stream of tables:
@@ -86,7 +86,7 @@ Output includes `mem_used` and `mem_total` columns with values for each correspo
 
 ```js
 // ...
-  |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
+    |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
 ```
 
 ###### Returns the following:
@@ -112,12 +112,14 @@ below casts integer field values to floats and multiplies by a float value (`100
 
 ```js
 // ...
-  |> map(fn: (r) => ({
-    _time: r._time,
-    _measurement: r._measurement,
-    _field: "mem_used_percent",
-    _value: float(v: r.mem_used) / float(v: r.mem_total) * 100.0
-  }))
+    |> map(
+        fn: (r) => ({
+            _time: r._time,
+            _measurement: r._measurement,
+            _field: "mem_used_percent",
+            _value: float(v: r.mem_used) / float(v: r.mem_total) * 100.0
+        })
+    )
 ```
 ##### Query results:
 
@@ -133,15 +135,17 @@ below casts integer field values to floats and multiplies by a float value (`100
 ### Full query
 ```js
 from(bucket: "gpu-monitor")
-  |> range(start: 2020-01-01T00:00:00Z)
-  |> filter(fn: (r) => r._measurement == "gpu" and r._field =~ /mem_/ )
-  |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
-  |> map(fn: (r) => ({
-    _time: r._time,
-    _measurement: r._measurement,
-    _field: "mem_used_percent",
-    _value: float(v: r.mem_used) / float(v: r.mem_total) * 100.0
-  }))
+    |> range(start: 2020-01-01T00:00:00Z)
+    |> filter(fn: (r) => r._measurement == "gpu" and r._field =~ /mem_/ )
+    |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
+    |> map(
+        fn: (r) => ({
+            _time: r._time,
+            _measurement: r._measurement,
+            _field: "mem_used_percent",
+            _value: float(v: r.mem_used) / float(v: r.mem_total) * 100.0
+        })
+    )
 ```
 
 ## Examples
@@ -149,17 +153,11 @@ from(bucket: "gpu-monitor")
 #### Calculate percentages using multiple fields
 ```js
 from(bucket: "db/rp")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "example-measurement")
-  |> filter(fn: (r) =>
-    r._field == "used_system" or
-    r._field == "used_user" or
-    r._field == "total"
-  )
-  |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
-  |> map(fn: (r) => ({ r with
-    _value: float(v: r.used_system + r.used_user) / float(v: r.total) * 100.0
-  }))
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> filter(fn: (r) => r._field == "used_system" or r._field == "used_user" or r._field == "total")
+    |> pivot(rowKey: ["_time"], columnKey: ["_field"], valueColumn: "_value")
+    |> map(fn: (r) => ({r with _value: float(v: r.used_system + r.used_user) / float(v: r.total) * 100.0}))
 ```
 
 #### Calculate percentages using multiple measurements
@@ -173,14 +171,11 @@ from(bucket: "db/rp")
 <!-- -->
 ```js
 from(bucket: "db/rp")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    (r._measurement == "m1" or r._measurement == "m2") and
-    (r._field == "field1" or r._field == "field2")    
-  )
-  |> group()
-  |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
-  |> map(fn: (r) => ({ r with  _value: r.field1 / r.field2 * 100.0 }))
+    |> range(start: -1h)
+    |> filter(fn: (r) => (r._measurement == "m1" or r._measurement == "m2") and (r._field == "field1" or r._field == "field2"))
+    |> group()
+    |> pivot(rowKey: ["_time"], columnKey: ["_field"], valueColumn: "_value")
+    |> map(fn: (r) => ({r with _value: r.field1 / r.field2 * 100.0}))
 ```
 
 #### Calculate percentages using multiple data sources
@@ -193,18 +188,15 @@ pgPass = secrets.get(key: "POSTGRES_PASSWORD")
 pgHost = secrets.get(key: "POSTGRES_HOST")
 
 t1 = sql.from(
-  driverName: "postgres",
-  dataSourceName: "postgresql://${pgUser}:${pgPass}@${pgHost}",
-  query:"SELECT id, name, available FROM exampleTable"
+    driverName: "postgres",
+    dataSourceName: "postgresql://${pgUser}:${pgPass}@${pgHost}",
+    query: "SELECT id, name, available FROM exampleTable",
 )
 
 t2 = from(bucket: "db/rp")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "example-measurement" and
-    r._field == "example-field"
-  )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement" and r._field == "example-field")
 
 join(tables: {t1: t1, t2: t2}, on: ["id"])
-  |> map(fn: (r) => ({ r with _value: r._value_t2 / r.available_t1 * 100.0 }))
+    |> map(fn: (r) => ({r with _value: r._value_t2 / r.available_t1 * 100.0}))
 ```
diff --git a/content/enterprise_influxdb/v1.9/flux/guides/conditional-logic.md b/content/enterprise_influxdb/v1.9/flux/guides/conditional-logic.md
index 11bfbfc67..0f207b8b9 100644
--- a/content/enterprise_influxdb/v1.9/flux/guides/conditional-logic.md
+++ b/content/enterprise_influxdb/v1.9/flux/guides/conditional-logic.md
@@ -44,10 +44,14 @@ Flux evaluates statements in order and stops evaluating once a condition matches
 For example, given the following statement:
 
 ```js
-if r._value > 95.0000001 and r._value <= 100.0 then "critical"
-else if r._value > 85.0000001 and r._value <= 95.0 then "warning"
-else if r._value > 70.0000001 and r._value <= 85.0 then "high"
-else "normal"
+if r._value > 95.0000001 and r._value <= 100.0 then
+    "critical"
+else if r._value > 85.0000001 and r._value <= 95.0 then
+    "warning"
+else if r._value > 70.0000001 and r._value <= 85.0 then
+    "high"
+else
+    "normal"
 ```
 
 When `r._value` is 96, the output is "critical" and the remaining conditions are not evaluated.
@@ -64,7 +68,7 @@ The following example sets the `overdue` variable based on the
 `dueDate` variable's relation to `now()`.
 
 ```js
-dueDate = 2019-05-01
+dueDate = 2019-05-01T00:00:00Z
 overdue = if dueDate < now() then true else false
 ```
 
@@ -80,16 +84,17 @@ The following example uses an example `metric` variable to change how the query
 metric = "Memory"
 
 from(bucket: "telegraf/autogen")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-      if v.metric == "Memory"
-        then r._measurement == "mem" and r._field == "used_percent"
-      else if v.metric == "CPU"
-        then r._measurement == "cpu" and r._field == "usage_user"
-      else if v.metric == "Disk"
-        then r._measurement == "disk" and r._field == "used_percent"
-      else r._measurement != ""
-  )
+    |> range(start: -1h)
+    |> filter(
+        fn: (r) => if v.metric == "Memory" then
+            r._measurement == "mem" and r._field == "used_percent"
+        else if v.metric == "CPU" then
+            r._measurement == "cpu" and r._field == "usage_user"
+        else if v.metric == "Disk" then
+            r._measurement == "disk" and r._field == "used_percent"
+        else
+            r._measurement != "",
+    )
 ```
 
 ### Conditionally transform column values with map()
@@ -105,35 +110,42 @@ It sets the `level` column to a specific string based on `_value` column.
 {{% code-tab-content %}}
 ```js
 from(bucket: "telegraf/autogen")
-  |> range(start: -5m)
-  |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent" )
-  |> map(fn: (r) => ({
-    r with
-    level:
-      if r._value >= 95.0000001 and r._value <= 100.0 then "critical"
-      else if r._value >= 85.0000001 and r._value <= 95.0 then "warning"
-      else if r._value >= 70.0000001 and r._value <= 85.0 then "high"
-      else "normal"
-    })
-  )
+    |> range(start: -5m)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+    |> map(
+        fn: (r) => ({r with
+            level: if r._value >= 95.0000001 and r._value <= 100.0 then
+                "critical"
+            else if r._value >= 85.0000001 and r._value <= 95.0 then
+                "warning"
+            else if r._value >= 70.0000001 and r._value <= 85.0 then
+                "high"
+            else
+                "normal",
+        }),
+    )
 ```
 {{% /code-tab-content %}}
 {{% code-tab-content %}}
 ```js
 from(bucket: "telegraf/autogen")
-  |> range(start: -5m)
-  |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent" )
-  |> map(fn: (r) => ({
-    // Retain all existing columns in the mapped row
-    r with
-    // Set the level column value based on the _value column
-    level:
-      if r._value >= 95.0000001 and r._value <= 100.0 then "critical"
-      else if r._value >= 85.0000001 and r._value <= 95.0 then "warning"
-      else if r._value >= 70.0000001 and r._value <= 85.0 then "high"
-      else "normal"
-    })
-  )
+    |> range(start: -5m)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+    |> map(
+        fn: (r) => ({
+            // Retain all existing columns in the mapped row
+            r with
+            // Set the level column value based on the _value column
+            level: if r._value >= 95.0000001 and r._value <= 100.0 then
+                "critical"
+            else if r._value >= 85.0000001 and r._value <= 95.0 then
+                "warning"
+            else if r._value >= 70.0000001 and r._value <= 85.0 then
+                "high"
+            else
+                "normal",
+        }),
+    )
 ```
 
 {{% /code-tab-content %}}
@@ -154,18 +166,20 @@ functions to count the number of records in every five minute window that exceed
 threshold = 65.0
 
 from(bucket: "telegraf/autogen")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent" )
-  |> aggregateWindow(
-      every: 5m,
-      fn: (column, tables=<-) => tables |> reduce(
-            identity: {above_threshold_count: 0.0},
-            fn: (r, accumulator) => ({
-              above_threshold_count:
-                if r._value >= threshold then accumulator.above_threshold_count + 1.0
-                else accumulator.above_threshold_count + 0.0
-            })
-        )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+    |> aggregateWindow(
+        every: 5m,
+        fn: (column, tables=<-) => tables
+            |> reduce(
+                identity: {above_threshold_count: 0.0},
+                fn: (r, accumulator) => ({
+                    above_threshold_count: if r._value >= threshold then
+                        accumulator.above_threshold_count + 1.0
+                    else
+                        accumulator.above_threshold_count + 0.0,
+                }),
+            ),
     )
 ```
 {{% /code-tab-content %}}
@@ -174,23 +188,25 @@ from(bucket: "telegraf/autogen")
 threshold = 65.0
 
 from(bucket: "telegraf/autogen")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent" )
-  // Aggregate data into 5 minute windows using a custom reduce() function
-  |> aggregateWindow(
-      every: 5m,
-      // Use a custom function in the fn parameter.
-      // The aggregateWindow fn parameter requires 'column' and 'tables' parameters.
-      fn: (column, tables=<-) => tables |> reduce(
-            identity: {above_threshold_count: 0.0},
-            fn: (r, accumulator) => ({
-              // Conditionally increment above_threshold_count if
-              // r.value exceeds the threshold
-              above_threshold_count:
-                if r._value >= threshold then accumulator.above_threshold_count + 1.0
-                else accumulator.above_threshold_count + 0.0
-            })
-        )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+    // Aggregate data into 5 minute windows using a custom reduce() function
+    |> aggregateWindow(
+        every: 5m,
+        // Use a custom function in the fn parameter.
+        // The aggregateWindow fn parameter requires 'column' and 'tables' parameters.
+        fn: (column, tables=<-) => tables
+            |> reduce(
+                identity: {above_threshold_count: 0.0},
+                fn: (r, accumulator) => ({
+                    // Conditionally increment above_threshold_count if
+                    // r.value exceeds the threshold
+                    above_threshold_count: if r._value >= threshold then
+                        accumulator.above_threshold_count + 1.0
+                    else
+                        accumulator.above_threshold_count + 0.0,
+                }),
+            ),
     )
 ```
 {{% /code-tab-content %}}
diff --git a/content/enterprise_influxdb/v1.9/flux/guides/cumulativesum.md b/content/enterprise_influxdb/v1.9/flux/guides/cumulativesum.md
index 7bf66f48d..78e4872b8 100644
--- a/content/enterprise_influxdb/v1.9/flux/guides/cumulativesum.md
+++ b/content/enterprise_influxdb/v1.9/flux/guides/cumulativesum.md
@@ -48,7 +48,7 @@ The examples below use the [example data variable](/enterprise_influxdb/v1.9/flu
 ##### Calculate the running total of values
 ```js
 data
-  |> cumulativeSum()
+    |> cumulativeSum()
 ```
 
 ## Use cumulativeSum() with aggregateWindow()
@@ -64,6 +64,6 @@ then calculate the running total of the aggregate values with `cumulativeSum()`.
 <!-- -->
 ```js
 data
-  |> aggregateWindow(every: 5m, fn: sum)
-  |> cumulativeSum()
+    |> aggregateWindow(every: 5m, fn: sum)
+    |> cumulativeSum()
 ```
diff --git a/content/enterprise_influxdb/v1.9/flux/guides/execute-queries.md b/content/enterprise_influxdb/v1.9/flux/guides/execute-queries.md
index 88f58b70f..bd9a5c030 100644
--- a/content/enterprise_influxdb/v1.9/flux/guides/execute-queries.md
+++ b/content/enterprise_influxdb/v1.9/flux/guides/execute-queries.md
@@ -31,6 +31,69 @@ on your InfluxDB instance, use the `-username` flag to provide your InfluxDB use
 the `-password` flag to provide your password.
 {{% /note %}}
 
+## Influx CLI
+To start an interactive Flux read-eval-print-loop (REPL) with the InfluxDB Enterprise 1.9+
+`influx` CLI, run the `influx` command with the following flags:
+
+- `-type=flux`
+- `-path-prefix=/api/v2/query`
+
+{{% note %}}
+If [authentication is enabled](/enterprise_influxdb/v1.9/administration/authentication_and_authorization)
+on your InfluxDB instance, use the `-username` flag to provide your InfluxDB username and
+the `-password` flag to provide your password.
+{{% /note %}}
+
+##### Enter an interactive Flux REPL
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[No Auth](#)
+[Auth Enabled](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```bash
+influx -type=flux -path-prefix=/api/v2/query
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```bash
+influx -type=flux \
+  -path-prefix=/api/v2/query \
+  -username myuser \
+  -password PasSw0rd
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+Any Flux query can be executed within the REPL.
+
+### Submit a Flux query via parameter
+Flux queries can also be passed to the Flux REPL as a parameter using the `influx` CLI's `-type=flux` option and the `-execute` parameter.
+The accompanying string is executed as a Flux query and results are output in your terminal.
+
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[No Auth](#)
+[Auth Enabled](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```bash
+influx -type=flux \
+  -path-prefix=/api/v2/query \
+  -execute '<flux query>'
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```bash
+influx -type=flux \
+  -path-prefix=/api/v2/query \
+  -username myuser \
+  -password PasSw0rd \
+  -execute '<flux query>'
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
 ### Submit a Flux query via via STDIN
 Flux queries an be piped into the `influx` CLI via STDIN.
 Query results are otuput in your terminal.
@@ -42,12 +105,15 @@ Query results are otuput in your terminal.
 {{% /code-tabs %}}
 {{% code-tab-content %}}
 ```bash
-echo '<flux query>' | influx -type=flux
+echo '<flux query>' | influx -type=flux -path-prefix=/api/v2/query
 ```
 {{% /code-tab-content %}}
 {{% code-tab-content %}}
 ```bash
-echo '<flux query>' | influx -type=flux -username myuser -password PasSw0rd
+echo '<flux query>' | influx -type=flux \
+  -path-prefix=/api/v2/query \
+  -username myuser \
+  -password PasSw0rd
 ```
 {{% /code-tab-content %}}
 {{< /code-tabs-wrapper >}}
@@ -78,8 +144,8 @@ curl -XPOST localhost:8086/api/v2/query -sS \
   -H 'Accept:application/csv' \
   -H 'Content-type:application/vnd.flux' \
   -d 'from(bucket:"telegraf")
-        |> range(start:-5m)
-        |> filter(fn:(r) => r._measurement == "cpu")'
+          |> range(start:-5m)
+          |> filter(fn:(r) => r._measurement == "cpu")'
 ```
 {{% /code-tab-content %}}
 {{% code-tab-content %}}
@@ -89,8 +155,8 @@ curl -XPOST localhost:8086/api/v2/query -sS \
   -H 'Content-type:application/vnd.flux' \
   -H 'Authorization: Token <username>:<password>' \
   -d 'from(bucket:"telegraf")
-        |> range(start:-5m)
-        |> filter(fn:(r) => r._measurement == "cpu")'
+          |> range(start:-5m)
+          |> filter(fn:(r) => r._measurement == "cpu")'
 ```
 {{% /code-tab-content %}}
 {{< /code-tabs-wrapper >}}
diff --git a/content/enterprise_influxdb/v1.9/flux/guides/exists.md b/content/enterprise_influxdb/v1.9/flux/guides/exists.md
index 24bcf4db0..3cd971ea6 100644
--- a/content/enterprise_influxdb/v1.9/flux/guides/exists.md
+++ b/content/enterprise_influxdb/v1.9/flux/guides/exists.md
@@ -47,36 +47,38 @@ to check if a row includes a column or if the value for that column is `null`.
 #### Filter null values
 ```js
 from(bucket: "db/rp")
-  |> range(start: -5m)
-  |> filter(fn: (r) => exists r._value)
+    |> range(start: -5m)
+    |> filter(fn: (r) => exists r._value)
 ```
 
 #### Map values based on existence
 ```js
 from(bucket: "default")
-  |> range(start: -30s)
-  |> map(fn: (r) => ({
-      r with
-      human_readable:
-        if exists r._value then "${r._field} is ${string(v:r._value)}."
-        else "${r._field} has no value."
-  }))
+    |> range(start: -30s)
+    |> map(
+        fn: (r) => ({r with
+            human_readable: if exists r._value then
+                "${r._field} is ${string(v: r._value)}."
+            else
+                "${r._field} has no value.",
+        }),
+    )
 ```
 
 #### Ignore null values in a custom aggregate function
 ```js
-customSumProduct = (tables=<-) =>
-  tables
+customSumProduct = (tables=<-) => tables
     |> reduce(
-      identity: {sum: 0.0, product: 1.0},
-      fn: (r, accumulator) => ({
-        r with
-        sum:
-          if exists r._value then r._value + accumulator.sum
-          else accumulator.sum,
-        product:
-          if exists r._value then r.value * accumulator.product
-          else accumulator.product
-      })
+        identity: {sum: 0.0, product: 1.0},
+        fn: (r, accumulator) => ({r with
+            sum: if exists r._value then
+                r._value + accumulator.sum
+            else
+                accumulator.sum,
+            product: if exists r._value then
+                r.value * accumulator.product
+            else
+                accumulator.product,
+        }),
     )
 ```
diff --git a/content/enterprise_influxdb/v1.9/flux/guides/fill.md b/content/enterprise_influxdb/v1.9/flux/guides/fill.md
index 243e432da..f4f5cbba6 100644
--- a/content/enterprise_influxdb/v1.9/flux/guides/fill.md
+++ b/content/enterprise_influxdb/v1.9/flux/guides/fill.md
@@ -23,12 +23,12 @@ to replace _null_ values with:
 <!-- -->
 ```js
 data
-  |> fill(usePrevious: true)
+    |> fill(usePrevious: true)
 
 // OR
 
 data
-  |> fill(value: 0.0)
+    |> fill(value: 0.0)
 ```
 
 {{% note %}}
@@ -48,7 +48,7 @@ Values remain _null_ if there is no previous non-null value in the table.
 
 ```js
 data
-  |> fill(usePrevious: true)
+    |> fill(usePrevious: true)
 ```
 
 {{< flex >}}
@@ -83,7 +83,7 @@ of the [column](/{{< latest "flux" >}}/stdlib/universe/fill/#column)._
 
 ```js
 data
-  |> fill(value: 0.0)
+    |> fill(value: 0.0)
 ```
 
 {{< flex >}}
diff --git a/content/enterprise_influxdb/v1.9/flux/guides/first-last.md b/content/enterprise_influxdb/v1.9/flux/guides/first-last.md
index 23b878d76..7a76078fd 100644
--- a/content/enterprise_influxdb/v1.9/flux/guides/first-last.md
+++ b/content/enterprise_influxdb/v1.9/flux/guides/first-last.md
@@ -20,12 +20,12 @@ to return the first or last record in an input table.
 
 ```js
 data
-  |> first()
+    |> first()
 
 // OR
 
 data
-  |> last()
+    |> last()
 ```
 
 {{% note %}}
@@ -120,8 +120,8 @@ point using aggregate or selector functions, and then removes the time-based seg
 {{% code-tab-content %}}
 ```js
 |> aggregateWindow(
-  every: 1h,
-  fn: first
+    every: 1h,
+    fn: first,
 )
 ```
 | _time                | _value |
@@ -133,8 +133,8 @@ point using aggregate or selector functions, and then removes the time-based seg
 {{% code-tab-content %}}
 ```js
 |> aggregateWindow(
-  every: 1h,
-  fn: last
+    every: 1h,
+    fn: last,
 )
 ```
 
diff --git a/content/enterprise_influxdb/v1.9/flux/guides/flux-in-dashboards.md b/content/enterprise_influxdb/v1.9/flux/guides/flux-in-dashboards.md
index f3b8d7e19..712fcb943 100644
--- a/content/enterprise_influxdb/v1.9/flux/guides/flux-in-dashboards.md
+++ b/content/enterprise_influxdb/v1.9/flux/guides/flux-in-dashboards.md
@@ -85,12 +85,9 @@ The following example uses Chronograf's [predefined template variables](#predefi
 
 ```js
 from(bucket: "telegraf/autogen")
-  |> filter(fn: (r) => r._measurement == "cpu")
-  |> range(
-    start: dashboardTime,
-    stop: upperDashboardTime
-  )
-  window(every: autoInterval)
+    |> filter(fn: (r) => r._measurement == "cpu")
+    |> range(start: dashboardTime, stop: upperDashboardTime)
+    |> window(every: autoInterval)
 ```
 
 ### Predefined template variables
@@ -102,9 +99,7 @@ It should be used to define the `start` parameter of the `range()` function.
 
 ```js
 dataSet
-  |> range(
-    start: dashboardTime
-  )
+    |> range(start: dashboardTime)
 ```
 
 #### upperDashboardTime
@@ -114,10 +109,7 @@ It should be used to define the `stop` parameter of the `range()` function.
 
 ```js
 dataSet
-  |> range(
-    start: dashboardTime,
-    stop: upperDashboardTime
-  )
+    |> range(start: dashboardTime, stop: upperDashboardTime)
 ```
 > As a best practice, always set the `stop` parameter of the `range()` function to `upperDashboardTime` in cell queries.
 > Without it, `stop` defaults to "now" and the absolute upper range bound selected in the time dropdown is not honored,
@@ -131,14 +123,8 @@ It's typically used to align window intervals created in
 
 ```js
 dataSet
-  |> range(
-    start: dashboardTime,
-    stop: upperDashboardTime
-  )
-  |> aggregateWindow(
-    every: autoInterval,
-    fn: mean
-  )
+    |> range(start: dashboardTime, stop: upperDashboardTime)
+    |> aggregateWindow(every: autoInterval, fn: mean)
 ```
 
 ### Custom template variables
diff --git a/content/enterprise_influxdb/v1.9/flux/guides/geo/_index.md b/content/enterprise_influxdb/v1.9/flux/guides/geo/_index.md
index 43ed26e22..6cd580026 100644
--- a/content/enterprise_influxdb/v1.9/flux/guides/geo/_index.md
+++ b/content/enterprise_influxdb/v1.9/flux/guides/geo/_index.md
@@ -86,6 +86,6 @@ Use Flux to query the bird migration data and assign it to the `sampleGeoData` v
 
 ```js
 sampleGeoData = from(bucket: "db/rp")
-  |> range(start: 2019-01-01T00:00:00Z, stop: 2019-12-31T23:59:59Z)
-  |> filter(fn: (r) => r._measurement == "migration")
+    |> range(start: 2019-01-01T00:00:00Z, stop: 2019-12-31T23:59:59Z)
+    |> filter(fn: (r) => r._measurement == "migration")
 ```
diff --git a/content/enterprise_influxdb/v1.9/flux/guides/geo/filter-by-region.md b/content/enterprise_influxdb/v1.9/flux/guides/geo/filter-by-region.md
index 9c62cf7dc..3868b6d51 100644
--- a/content/enterprise_influxdb/v1.9/flux/guides/geo/filter-by-region.md
+++ b/content/enterprise_influxdb/v1.9/flux/guides/geo/filter-by-region.md
@@ -37,10 +37,7 @@ and queries data points **within 200km of Cairo, Egypt**:
 import "experimental/geo"
 
 sampleGeoData
-  |> geo.filterRows(
-    region: {lat: 30.04, lon: 31.23, radius: 200.0},
-    strict: true
-  )
+    |> geo.filterRows(region: {lat: 30.04, lon: 31.23, radius: 200.0}, strict: true)
 ```
 
 ## Define a geographic region
@@ -62,10 +59,10 @@ Define a box-shaped region by specifying a record containing the following prope
 ##### Example box-shaped region
 ```js
 {
-  minLat: 40.51757813,
-  maxLat: 40.86914063,
-  minLon: -73.65234375,
-  maxLon: -72.94921875
+    minLat: 40.51757813,
+    maxLat: 40.86914063,
+    minLon: -73.65234375,
+    maxLon: -72.94921875,
 }
 ```
 
@@ -79,9 +76,9 @@ Define a circular region by specifying a record containing the following propert
 ##### Example circular region
 ```js
 {
-  lat: 40.69335938,
-  lon: -73.30078125,
-  radius: 20.0
+    lat: 40.69335938,
+    lon: -73.30078125,
+    radius: 20.0,
 }
 ```
 
@@ -99,11 +96,11 @@ each point in the polygon:
 ##### Example polygonal region
 ```js
 {
-  points: [
-    {lat: 40.671659, lon: -73.936631},
-    {lat: 40.706543, lon: -73.749177},
-    {lat: 40.791333, lon: -73.880327}
-  ]
+    points: [
+        {lat: 40.671659, lon: -73.936631},
+        {lat: 40.706543, lon: -73.749177},
+        {lat: 40.791333, lon: -73.880327},
+    ]
 }
 ```
 
diff --git a/content/enterprise_influxdb/v1.9/flux/guides/geo/group-geo-data.md b/content/enterprise_influxdb/v1.9/flux/guides/geo/group-geo-data.md
index 46b5a86c5..6fc55b102 100644
--- a/content/enterprise_influxdb/v1.9/flux/guides/geo/group-geo-data.md
+++ b/content/enterprise_influxdb/v1.9/flux/guides/geo/group-geo-data.md
@@ -45,11 +45,8 @@ to query data points within 200km of Cairo, Egypt and group them by geographic a
 import "experimental/geo"
 
 sampleGeoData
-  |> geo.filterRows(region: {lat: 30.04, lon: 31.23, radius: 200.0})
-  |> geo.groupByArea(
-    newColumn: "geoArea",
-    level: 5
-  )
+    |> geo.filterRows(region: {lat: 30.04, lon: 31.23, radius: 200.0})
+    |> geo.groupByArea(newColumn: "geoArea", level: 5)
 ```
 
 ### Group data by track or route
@@ -68,9 +65,6 @@ to each bird:
 import "experimental/geo"
 
 sampleGeoData
-  |> geo.filterRows(region: {lat: 30.04, lon: 31.23, radius: 200.0})
-  |> geo.asTracks(
-    groupBy: ["id"],
-    sortBy: ["_time"]
-  )
+    |> geo.filterRows(region: {lat: 30.04, lon: 31.23, radius: 200.0})
+    |> geo.asTracks(groupBy: ["id"], sortBy: ["_time"])
 ```
diff --git a/content/enterprise_influxdb/v1.9/flux/guides/geo/shape-geo-data.md b/content/enterprise_influxdb/v1.9/flux/guides/geo/shape-geo-data.md
index eabb6e0c6..dfb937202 100644
--- a/content/enterprise_influxdb/v1.9/flux/guides/geo/shape-geo-data.md
+++ b/content/enterprise_influxdb/v1.9/flux/guides/geo/shape-geo-data.md
@@ -39,13 +39,9 @@ into row-wise sets, and generate S2 cell ID tokens for each point.
 import "experimental/geo"
 
 from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "example-measurement")
-  |> geo.shapeData(
-    latField: "latitude",
-    lonField: "longitude",
-    level: 10
-  )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> geo.shapeData(latField: "latitude", lonField: "longitude", level: 10)
 ```
 
 ## Generate S2 cell ID tokens
@@ -108,12 +104,10 @@ to pivot **lat** and **lon** fields into row-wise sets:
 import "experimental/geo"
 
 from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "example-measurement")
-  |> geo.toRows()
-  |> map(fn: (r) => ({ r with
-    s2_cell_id: geo.s2CellIDToken(point: {lon: r.lon, lat: r.lat}, level: 10)
-  }))
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> geo.toRows()
+    |> map(fn: (r) => ({r with s2_cell_id: geo.s2CellIDToken(point: {lon: r.lon, lat: r.lat}, level: 10)}))
 ```
 
 {{% note %}}
diff --git a/content/enterprise_influxdb/v1.9/flux/guides/group-data.md b/content/enterprise_influxdb/v1.9/flux/guides/group-data.md
index 5a9d9660b..bfded2f7b 100644
--- a/content/enterprise_influxdb/v1.9/flux/guides/group-data.md
+++ b/content/enterprise_influxdb/v1.9/flux/guides/group-data.md
@@ -43,7 +43,7 @@ group key for output tables, i.e. grouping records based on values for specific
 ###### group() example
 ```js
 dataStream
-  |> group(columns: ["cpu", "host"])
+    |> group(columns: ["cpu", "host"])
 ```
 
 ###### Resulting group key
@@ -72,12 +72,9 @@ It uses a regular expression to filter only numbered cores.
 
 ```js
 dataSet = from(bucket: "db/rp")
-  |> range(start: -2m)
-  |> filter(fn: (r) =>
-    r._field == "usage_system" and
-    r.cpu =~ /cpu[0-9*]/
-  )
-  |> drop(columns: ["host"])
+    |> range(start: -2m)
+    |> filter(fn: (r) => r._field == "usage_system" and r.cpu =~ /cpu[0-9*]/)
+    |> drop(columns: ["host"])
 ```
 
 {{% note %}}
@@ -167,7 +164,7 @@ Group the `dataSet` stream by the `cpu` column.
 
 ```js
 dataSet
-  |> group(columns: ["cpu"])
+    |> group(columns: ["cpu"])
 ```
 
 This won't actually change the structure of the data since it already has `cpu`
@@ -256,7 +253,7 @@ Grouping data by the `_time` column is a good illustration of how grouping chang
 
 ```js
 dataSet
-  |> group(columns: ["_time"])
+    |> group(columns: ["_time"])
 ```
 
 When grouping by `_time`, all records that share a common `_time` value are grouped into individual tables.
@@ -383,9 +380,9 @@ If you're interested in running and visualizing this yourself, here's what the q
 
 ```js
 dataSet
-  |> group(columns: ["_time"])
-  |> mean()
-  |> group(columns: ["_value", "_time"], mode: "except")
+    |> group(columns: ["_time"])
+    |> mean()
+    |> group(columns: ["_value", "_time"], mode: "except")
 ```
 {{% /note %}}
 
@@ -394,7 +391,7 @@ Group by the `cpu` and `_time` columns.
 
 ```js
 dataSet
-  |> group(columns: ["cpu", "_time"])
+    |> group(columns: ["cpu", "_time"])
 ```
 
 This outputs a table for every unique `cpu` and `_time` combination:
diff --git a/content/enterprise_influxdb/v1.9/flux/guides/histograms.md b/content/enterprise_influxdb/v1.9/flux/guides/histograms.md
index a0c3ac66e..47da6ee77 100644
--- a/content/enterprise_influxdb/v1.9/flux/guides/histograms.md
+++ b/content/enterprise_influxdb/v1.9/flux/guides/histograms.md
@@ -25,13 +25,10 @@ In the histogram output, a column is added (le) that represents the upper bounds
 Bin counts are cumulative.
 
 ```js
-from(bucket:"telegraf/autogen")
-  |> range(start: -5m)
-  |> filter(fn: (r) =>
-    r._measurement == "mem" and
-    r._field == "used_percent"
-  )
-  |> histogram(bins: [0.0, 10.0, 20.0, 30.0])
+from(bucket: "telegraf/autogen")
+    |> range(start: -5m)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+    |> histogram(bins: [0.0, 10.0, 20.0, 30.0])
 ```
 
 > Values output by the `histogram` function represent points of data aggregated over time.
@@ -63,20 +60,10 @@ logarithmicBins(start: 1.0, factor: 2.0, count: 10, infinty: true)
 
 ### Generating a histogram with linear bins
 ```js
-from(bucket:"telegraf/autogen")
-  |> range(start: -5m)
-  |> filter(fn: (r) =>
-    r._measurement == "mem" and
-    r._field == "used_percent"
-  )
-  |> histogram(
-    bins: linearBins(
-      start:65.5,
-      width: 0.5,
-      count: 20,
-      infinity:false
-    )
-  )
+from(bucket: "telegraf/autogen")
+    |> range(start: -5m)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+    |> histogram(bins: linearBins(start: 65.5, width: 0.5, count: 20, infinity: false))
 ```
 
 ###### Output table
@@ -108,20 +95,10 @@ Table: keys: [_start, _stop, _field, _measurement, host]
 
 ### Generating a histogram with logarithmic bins
 ```js
-from(bucket:"telegraf/autogen")
-  |> range(start: -5m)
-  |> filter(fn: (r) =>
-    r._measurement == "mem" and
-    r._field == "used_percent"
-  )
-  |> histogram(
-    bins: logarithmicBins(
-      start:0.5,
-      factor: 2.0,
-      count: 10,
-      infinity:false
-    )
-  )
+from(bucket: "telegraf/autogen")
+    |> range(start: -5m)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+    |> histogram(bins: logarithmicBins(start: 0.5, factor: 2.0, count: 10, infinity: false))
 ```
 
 ###### Output table
diff --git a/content/enterprise_influxdb/v1.9/flux/guides/increase.md b/content/enterprise_influxdb/v1.9/flux/guides/increase.md
index 233347915..e8cc5efd9 100644
--- a/content/enterprise_influxdb/v1.9/flux/guides/increase.md
+++ b/content/enterprise_influxdb/v1.9/flux/guides/increase.md
@@ -23,7 +23,7 @@ wrap over time or periodically reset.
 
 ```js
 data
-  |> increase()
+    |> increase()
 ```
 
 `increase()` returns a cumulative sum of **non-negative** differences between rows in a table.
diff --git a/content/enterprise_influxdb/v1.9/flux/guides/join.md b/content/enterprise_influxdb/v1.9/flux/guides/join.md
index d99f1b84a..ce9fcc4e2 100644
--- a/content/enterprise_influxdb/v1.9/flux/guides/join.md
+++ b/content/enterprise_influxdb/v1.9/flux/guides/join.md
@@ -40,11 +40,8 @@ This returns the amount of memory (in bytes) used.
 ###### memUsed stream definition
 ```js
 memUsed = from(bucket: "db/rp")
-  |> range(start: -5m)
-  |> filter(fn: (r) =>
-    r._measurement == "mem" and
-    r._field == "used"
-  )
+    |> range(start: -5m)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used")
 ```
 
 {{% truncate %}}
@@ -94,11 +91,8 @@ This returns the number of running processes.
 ###### procTotal stream definition
 ```js
 procTotal = from(bucket: "db/rp")
-  |> range(start: -5m)
-  |> filter(fn: (r) =>
-    r._measurement == "processes" and
-    r._field == "total"
-  )
+    |> range(start: -5m)
+    |> filter(fn: (r) => r._measurement == "processes" and r._field == "total")
 ```
 
 {{% truncate %}}
@@ -154,10 +148,7 @@ An array of strings defining the columns on which the tables will be joined.
 _**Both tables must have all columns specified in this list.**_
 
 ```js
-join(
-  tables: {mem:memUsed, proc:procTotal},
-  on: ["_time", "_stop", "_start", "host"]
-)
+join(tables: {mem: memUsed, proc: procTotal}, on: ["_time", "_stop", "_start", "host"])
 ```
 
 {{% truncate %}}
@@ -219,12 +210,8 @@ column and dividing `_value_mem` by `_value_proc` and mapping it to a
 new `_value` column.
 
 ```js
-join(tables: {mem:memUsed, proc:procTotal}, on: ["_time", "_stop", "_start", "host"])
-  |> map(fn: (r) => ({
-      _time: r._time,
-      _value: r._value_mem / r._value_proc
-    })
-  )
+join(tables: {mem: memUsed, proc: procTotal}, on: ["_time", "_stop", "_start", "host"])
+    |> map(fn: (r) => ({_time: r._time, _value: r._value_mem / r._value_proc}))
 ```
 
 {{% truncate %}}
@@ -277,35 +264,21 @@ The results are grouped by cluster ID so you can make comparisons across cluster
 
 ```js
 batchSize = (cluster_id, start=-1m, interval=10s) => {
-  httpd = from(bucket:"telegraf")
-    |> range(start:start)
-    |> filter(fn:(r) =>
-      r._measurement == "influxdb_httpd" and
-      r._field == "writeReq" and
-      r.cluster_id == cluster_id
-    )
-    |> aggregateWindow(every: interval, fn: mean)
-    |> derivative(nonNegative:true,unit:60s)
+    httpd = from(bucket: "telegraf")
+        |> range(start: start)
+        |> filter(fn: (r) => r._measurement == "influxdb_httpd" and r._field == "writeReq" and r.cluster_id == cluster_id)
+        |> aggregateWindow(every: interval, fn: mean)
+        |> derivative(nonNegative: true, unit: 60s)
 
-  write = from(bucket:"telegraf")
-    |> range(start:start)
-    |> filter(fn:(r) =>
-      r._measurement == "influxdb_write" and
-      r._field == "pointReq" and
-      r.cluster_id == cluster_id
-    )
-    |> aggregateWindow(every: interval, fn: max)
-    |> derivative(nonNegative:true,unit:60s)
+    write = from(bucket: "telegraf")
+        |> range(start: start)
+        |> filter(fn: (r) => r._measurement == "influxdb_write" and r._field == "pointReq" and r.cluster_id == cluster_id)
+        |> aggregateWindow(every: interval, fn: max)
+        |> derivative(nonNegative: true, unit: 60s)
 
-  return join(
-      tables:{httpd:httpd, write:write},
-      on:["_time","_stop","_start","host"]
-    )
-    |> map(fn:(r) => ({
-        _time: r._time,
-        _value: r._value_httpd / r._value_write,
-    }))
-    |> group(columns: cluster_id)
+    return join(tables: {httpd: httpd, write: write}, on: ["_time", "_stop", "_start", "host"])
+        |> map(fn: (r) => ({_time: r._time, _value: r._value_httpd / r._value_write}))
+        |> group(columns: cluster_id)
 }
 
 batchSize(cluster_id: "enter cluster id here")
diff --git a/content/enterprise_influxdb/v1.9/flux/guides/manipulate-timestamps.md b/content/enterprise_influxdb/v1.9/flux/guides/manipulate-timestamps.md
index 96a046102..132b4740d 100644
--- a/content/enterprise_influxdb/v1.9/flux/guides/manipulate-timestamps.md
+++ b/content/enterprise_influxdb/v1.9/flux/guides/manipulate-timestamps.md
@@ -116,7 +116,7 @@ operations where points should align by time, but timestamps vary slightly.
 
 ```js
 data
-  |> truncateTimeColumn(unit: 1m)
+    |> truncateTimeColumn(unit: 1m)
 ```
 
 {{< flex >}}
@@ -160,10 +160,7 @@ By using `experimental.addDuration()`, you accept the
 ```js
 import "experimental"
 
-experimental.addDuration(
-  d: 6h,
-  to: 2019-09-16T12:00:00Z,
-)
+experimental.addDuration(d: 6h, to: 2019-09-16T12:00:00Z)
 
 // Returns 2019-09-16T18:00:00.000000000Z
 ```
@@ -180,10 +177,7 @@ By using `experimental.subDuration()`, you accept the
 ```js
 import "experimental"
 
-experimental.subDuration(
-  d: 6h,
-  from: 2019-09-16T12:00:00Z,
-)
+experimental.subDuration(d: 6h, from: 2019-09-16T12:00:00Z)
 
 // Returns 2019-09-16T06:00:00.000000000Z
 ```
diff --git a/content/enterprise_influxdb/v1.9/flux/guides/mathematic-operations.md b/content/enterprise_influxdb/v1.9/flux/guides/mathematic-operations.md
index 1b2f421d8..489587bb4 100644
--- a/content/enterprise_influxdb/v1.9/flux/guides/mathematic-operations.md
+++ b/content/enterprise_influxdb/v1.9/flux/guides/mathematic-operations.md
@@ -102,16 +102,11 @@ The example `multiplyByX()` function below includes:
   It also multiples the `_value` column by `x`.
 
 ```js
-multiplyByX = (x, tables=<-) =>
-  tables
-    |> map(fn: (r) => ({
-        r with
-        _value: r._value * x
-      })
-    )
+multiplyByX = (x, tables=<-) => tables
+    |> map(fn: (r) => ({r with _value: r._value * x}))
 
 data
-  |> multiplyByX(x: 10)
+    |> multiplyByX(x: 10)
 ```
 
 ## Examples
@@ -125,31 +120,19 @@ a new `_value` by dividing the original `_value` by 1073741824.
 
 ```js
 from(bucket: "db/rp")
-  |> range(start: -10m)
-  |> filter(fn: (r) =>
-    r._measurement == "mem" and
-    r._field == "active"
-  )
-  |> map(fn: (r) => ({
-      r with
-      _value: r._value / 1073741824
-    })
-  )
+    |> range(start: -10m)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "active")
+    |> map(fn: (r) => ({r with _value: r._value / 1073741824}))
 ```
 
 You could turn that same calculation into a function:
 
 ```js
-bytesToGB = (tables=<-) =>
-  tables
-    |> map(fn: (r) => ({
-        r with
-        _value: r._value / 1073741824
-      })
-    )
+bytesToGB = (tables=<-) => tables
+    |> map(fn: (r) => ({r with _value: r._value / 1073741824}))
 
 data
-  |> bytesToGB()
+    |> bytesToGB()
 ```
 
 #### Include partial gigabytes
@@ -159,13 +142,8 @@ To calculate partial GBs, convert the `_value` column and its values to floats u
 and format the denominator in the division operation as a float.
 
 ```js
-bytesToGB = (tables=<-) =>
-  tables
-    |> map(fn: (r) => ({
-        r with
-        _value: float(v: r._value) / 1073741824.0
-      })
-    )
+bytesToGB = (tables=<-) => tables
+    |> map(fn: (r) => ({r with _value: float(v: r._value) / 1073741824.0}))
 ```
 
 ### Calculate a percentage
@@ -194,10 +172,8 @@ Use `join()` when querying data from different buckets or data sources.
 ##### Pivot fields into columns for mathematic calculations
 ```js
 data
-  |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
-  |> map(fn: (r) => ({ r with
-    _value: (r.field1 + r.field2) / r.field3 * 100.0
-  }))
+    |> pivot(rowKey: ["_time"], columnKey: ["_field"], valueColumn: "_value")
+    |> map(fn: (r) => ({r with _value: (r.field1 + r.field2) / r.field3 * 100.0}))
 ```
 
 ##### Join multiple data sources for mathematic calculations
@@ -210,18 +186,15 @@ pgPass = secrets.get(key: "POSTGRES_PASSWORD")
 pgHost = secrets.get(key: "POSTGRES_HOST")
 
 t1 = sql.from(
-  driverName: "postgres",
-  dataSourceName: "postgresql://${pgUser}:${pgPass}@${pgHost}",
-  query:"SELECT id, name, available FROM exampleTable"
+    driverName: "postgres",
+    dataSourceName: "postgresql://${pgUser}:${pgPass}@${pgHost}",
+    query: "SELECT id, name, available FROM exampleTable",
 )
 
 t2 = from(bucket: "db/rp")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "example-measurement" and
-    r._field == "example-field"
-  )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement" and r._field == "example-field")
 
 join(tables: {t1: t1, t2: t2}, on: ["id"])
-  |> map(fn: (r) => ({ r with _value: r._value_t2 / r.available_t1 * 100.0 }))
+    |> map(fn: (r) => ({r with _value: r._value_t2 / r.available_t1 * 100.0}))
 ```
diff --git a/content/enterprise_influxdb/v1.9/flux/guides/median.md b/content/enterprise_influxdb/v1.9/flux/guides/median.md
index 30b7d10d4..922bef8c7 100644
--- a/content/enterprise_influxdb/v1.9/flux/guides/median.md
+++ b/content/enterprise_influxdb/v1.9/flux/guides/median.md
@@ -107,7 +107,7 @@ contain values in the 50th percentile of data in the table.
 
 ```js
 data
-  |> median()
+    |> median()
 ```
 
 ## Find the average of values closest to the median
@@ -116,7 +116,7 @@ average of the two values closest to the mathematical median of data in the tabl
 
 ```js
 data
-  |> median(method: "exact_mean")
+    |> median(method: "exact_mean")
 ```
 
 ## Find the point with the median value
@@ -125,7 +125,7 @@ value that 50% of values in the table are less than.
 
 ```js
 data
-  |> median(method: "exact_selector")
+    |> median(method: "exact_selector")
 ```
 
 ## Use median() with aggregateWindow()
@@ -139,8 +139,5 @@ To specify the [median calculation method](#select-a-method-for-calculating-the-
 
 ```js
 data
-  |> aggregateWindow(
-    every: 5m,
-    fn: (tables=<-, column) => tables |> median(method: "exact_selector")
-  )
+    |> aggregateWindow(every: 5m, fn: (tables=<-, column) => tables |> median(method: "exact_selector"))
 ```
diff --git a/content/enterprise_influxdb/v1.9/flux/guides/monitor-states.md b/content/enterprise_influxdb/v1.9/flux/guides/monitor-states.md
index bc96f3ba4..33a22916d 100644
--- a/content/enterprise_influxdb/v1.9/flux/guides/monitor-states.md
+++ b/content/enterprise_influxdb/v1.9/flux/guides/monitor-states.md
@@ -33,12 +33,12 @@ If you're just getting started with Flux queries, check out the following:
 
     <!-- -->
     ```js
-    |> stateDuration(
-      fn: (r) =>
-      r._column_to_search == "value_to_search_for",
-      column: "state_duration",
-      unit: 1s
-    )
+    data
+        |> stateDuration(
+            fn: (r) => r._column_to_search == "value_to_search_for",
+            column: "state_duration",
+            unit: 1s,
+        )
     ```
 
 2. Use `stateDuration()` to search each point for the specified value:
@@ -52,13 +52,12 @@ The following query searches the `doors` bucket over the past 5 minutes to find
 
 ```js
 from(bucket: "doors")
-  |> range(start: -5m)
-  |> stateDuration(
-    fn: (r) =>
-    r._value == "closed",
-    column: "door_closed",
-    unit: 1s
-  )
+    |> range(start: -5m)
+    |> stateDuration(
+        fn: (r) => r._value == "closed",
+        column: "door_closed",
+        unit: 1s,
+    )
 ```
 
 In this example, `door_closed` is the **State duration** column. If you write data to the `doors` bucket every minute, the state duration increases by `60s` for each consecutive point where `_value` is `closed`. If `_value` is not `closed`, the state duration is reset to `0`.
@@ -87,11 +86,11 @@ _time                   _value        door_closed
 
     <!--  -->
     ```js
-    |> stateCount
-       (fn: (r) =>
-        r._column_to_search == "value_to_search_for",
-        column: "state_count"
-      )
+    data
+        |> stateCount(
+            fn: (r) => r._column_to_search == "value_to_search_for",
+            column: "state_count"
+        )
     ```
 
 2. Use `stateCount()` to search each point for the specified value:
@@ -106,11 +105,8 @@ calculates how many points have `closed` as their `_value`.
 
 ```js
 from(bucket: "doors")
-  |> range(start: -5m)
-  |> stateDuration(
-    fn: (r) =>
-    r._value == "closed",
-    column: "door_closed")
+    |> range(start: -5m)
+    |> stateDuration(fn: (r) => r._value == "closed", column: "door_closed")
 ```
 
 This example stores the **state count** in the `door_closed` column.
@@ -139,13 +135,9 @@ InfluxDB searches the `servers` bucket over the past hour and counts records wit
 
 ```js
 from(bucket: "servers")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-     r.machine_state == "idle" or
-     r.machine_state == "assigned" or
-     r.machine_state == "busy"
-  )
-  |> stateCount(fn: (r) => r.machine_state == "busy", column: "_count")
-  |> stateCount(fn: (r) => r.machine_state == "assigned", column: "_count")
-  |> stateCount(fn: (r) => r.machine_state == "idle", column: "_count")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r.machine_state == "idle" or r.machine_state == "assigned" or r.machine_state == "busy")
+    |> stateCount(fn: (r) => r.machine_state == "busy", column: "_count")
+    |> stateCount(fn: (r) => r.machine_state == "assigned", column: "_count")
+    |> stateCount(fn: (r) => r.machine_state == "idle", column: "_count")
 ```
diff --git a/content/enterprise_influxdb/v1.9/flux/guides/moving-average.md b/content/enterprise_influxdb/v1.9/flux/guides/moving-average.md
index 893e9e91a..ad91dfb17 100644
--- a/content/enterprise_influxdb/v1.9/flux/guides/moving-average.md
+++ b/content/enterprise_influxdb/v1.9/flux/guides/moving-average.md
@@ -20,12 +20,12 @@ functions to return the moving average of data.
 
 ```js
 data
-  |> movingAverage(n: 5)
+    |> movingAverage(n: 5)
 
 // OR
 
 data
-  |> timedMovingAverage(every: 5m, period: 10m)
+    |> timedMovingAverage(every: 5m, period: 10m)
 ```
 
 ### movingAverage()
@@ -99,10 +99,7 @@ If `every = 30m` and `period = 1h`:
 **The following would return:**
 
 ```js
-|> timedMovingAverage(
-  every: 2m,
-  period: 4m
-)
+|> timedMovingAverage(every: 2m, period: 4m)
 ```  
 
 | _time                | _value |
diff --git a/content/enterprise_influxdb/v1.9/flux/guides/percentile-quantile.md b/content/enterprise_influxdb/v1.9/flux/guides/percentile-quantile.md
index 18a264d02..01d122ded 100644
--- a/content/enterprise_influxdb/v1.9/flux/guides/percentile-quantile.md
+++ b/content/enterprise_influxdb/v1.9/flux/guides/percentile-quantile.md
@@ -120,7 +120,7 @@ contain values in the 99th percentile of data in the table.
 
 ```js
 data
-  |> quantile(q: 0.99)
+    |> quantile(q: 0.99)
 ```
 
 ## Find the average of values closest to the quantile
@@ -130,7 +130,7 @@ For example, to calculate the `0.99` quantile:
 
 ```js
 data
-  |> quantile(q: 0.99, method: "exact_mean")
+    |> quantile(q: 0.99, method: "exact_mean")
 ```
 
 ## Find the point with the quantile value
@@ -140,7 +140,7 @@ For example, to calculate the `0.99` quantile:
 
 ```js
 data
-  |> quantile(q: 0.99, method: "exact_selector")
+    |> quantile(q: 0.99, method: "exact_selector")
 ```
 
 ## Use quantile() with aggregateWindow()
@@ -154,10 +154,9 @@ To specify the [quantile calculation method](#select-a-method-for-calculating-th
 
 ```js
 data
-  |> aggregateWindow(
-    every: 5m,
-    fn: (tables=<-, column) =>
-      tables
-        |> quantile(q: 0.99, method: "exact_selector")
-  )
+    |> aggregateWindow(
+        every: 5m,
+        fn: (tables=<-, column) => tables
+            |> quantile(q: 0.99, method: "exact_selector"),
+    )
 ```
diff --git a/content/enterprise_influxdb/v1.9/flux/guides/query-fields.md b/content/enterprise_influxdb/v1.9/flux/guides/query-fields.md
index 74ca57f70..aec322d78 100644
--- a/content/enterprise_influxdb/v1.9/flux/guides/query-fields.md
+++ b/content/enterprise_influxdb/v1.9/flux/guides/query-fields.md
@@ -37,7 +37,7 @@ Rows that evaluate to `false` are **excluded** from the output data.
 
 ```js
 // ...
-  |> filter(fn: (r) => r._measurement == "example-measurement" )
+    |> filter(fn: (r) => r._measurement == "example-measurement" )
 ```
 
 The `fn` predicate function requires an `r` argument, which represents each row
@@ -69,10 +69,7 @@ and `filter()` represent the most basic Flux query:
 
 ```js
 from(bucket: "db/rp")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-      r._measurement == "example-measurement" and
-      r._field == "example-field" and
-      r.tag == "example-tag"
-  )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement" and r.tag == "example-tag")
+    |> filter(fn: (r) => r._field == "example-field")
 ```
diff --git a/content/enterprise_influxdb/v1.9/flux/guides/rate.md b/content/enterprise_influxdb/v1.9/flux/guides/rate.md
index ca676f267..9c3de71b9 100644
--- a/content/enterprise_influxdb/v1.9/flux/guides/rate.md
+++ b/content/enterprise_influxdb/v1.9/flux/guides/rate.md
@@ -34,7 +34,7 @@ to calculate the rate of change per unit of time between subsequent _non-null_ v
 
 ```js
 data
-  |> derivative(unit: 1s)
+    |> derivative(unit: 1s)
 ```
 
 By default, `derivative()` returns only positive derivative values and replaces negative values with _null_.
@@ -93,10 +93,7 @@ To return negative derivative values, set the `nonNegative` parameter to `false`
 **The following returns:**
 
 ```js
-|> derivative(
-  unit: 1m,
-  nonNegative: false
-)
+|> derivative(unit: 1m, nonNegative: false)
 ```
 
 | _time                | _value |
@@ -122,11 +119,7 @@ to calculate the average rate of change per window of time.
 import "experimental/aggregate"
 
 data
-  |> aggregate.rate(
-    every: 1m,
-    unit: 1s,
-    groupColumns: ["tag1", "tag2"]
-  )
+    |> aggregate.rate(every: 1m, unit: 1s, groupColumns: ["tag1", "tag2"])
 ```
 
 `aggregate.rate()` returns the average rate of change (as a [float](/{{< latest "flux" >}}/language/types/#numeric-types))
@@ -155,10 +148,7 @@ Negative values are replaced with _null_.
 **The following returns:**
 
 ```js
-|> aggregate.rate(
-  every: 20m,
-  unit: 1m
-)
+|> aggregate.rate(every: 20m, unit: 1m)
 ```
 
 | _time                | _value |
diff --git a/content/enterprise_influxdb/v1.9/flux/guides/regular-expressions.md b/content/enterprise_influxdb/v1.9/flux/guides/regular-expressions.md
index 91d1e1865..c5a24dca0 100644
--- a/content/enterprise_influxdb/v1.9/flux/guides/regular-expressions.md
+++ b/content/enterprise_influxdb/v1.9/flux/guides/regular-expressions.md
@@ -52,12 +52,8 @@ It only keeps records for which the `cpu` is either `cpu0`, `cpu1`, or `cpu2`.
 
 ```js
 from(bucket: "db/rp")
-  |> range(start: -15m)
-  |> filter(fn: (r) =>
-    r._measurement == "cpu" and
-    r._field == "usage_user" and
-    r.cpu =~ /cpu[0-2]/
-  )
+    |> range(start: -15m)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_user" and r.cpu =~ /cpu[0-2]/)
 ```
 
 ### Use a regex to filter by field key
@@ -65,11 +61,8 @@ The following example excludes records that do not have `_percent` in a field ke
 
 ```js
 from(bucket: "db/rp")
-  |> range(start: -15m)
-  |> filter(fn: (r) =>
-    r._measurement == "mem" and
-    r._field =~ /_percent/
-  )
+    |> range(start: -15m)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field =~ /_percent/)
 ```
 
 ### Drop columns matching a regex
@@ -77,9 +70,9 @@ The following example drops columns whose names do not being with `_`.
 
 ```js
 from(bucket: "db/rp")
-  |> range(start: -15m)
-  |> filter(fn: (r) => r._measurement == "mem")
-  |> drop(fn: (column) => column !~ /_.*/)
+    |> range(start: -15m)
+    |> filter(fn: (r) => r._measurement == "mem")
+    |> drop(fn: (column) => column !~ /_.*/)
 ```
 
 ## Helpful links
diff --git a/content/enterprise_influxdb/v1.9/flux/guides/scalar-values.md b/content/enterprise_influxdb/v1.9/flux/guides/scalar-values.md
index f756260fb..f8e4a3c07 100644
--- a/content/enterprise_influxdb/v1.9/flux/guides/scalar-values.md
+++ b/content/enterprise_influxdb/v1.9/flux/guides/scalar-values.md
@@ -64,10 +64,7 @@ each table.
 
 ```js
 sampleData
-  |> tableFind(fn: (key) =>
-      key._field == "temp" and
-      key.location == "sfo"
-  )
+    |> tableFind(fn: (key) => key._field == "temp" and key.location == "sfo")
 ```
 
 The example above returns a single table:
@@ -95,11 +92,8 @@ to output an array of values from a specific column in the extracted table.
 
 ```js
 sampleData
-  |> tableFind(fn: (key) =>
-      key._field == "temp"  and
-      key.location == "sfo"
-  )
-  |> getColumn(column: "_value")
+    |> tableFind(fn: (key) => key._field == "temp" and key.location == "sfo")
+    |> getColumn(column: "_value")
 
 // Returns [65.1, 66.2, 66.3, 66.8]
 ```
@@ -112,11 +106,8 @@ value at that index.
 
 ```js
 SFOTemps = sampleData
-  |> tableFind(fn: (key) =>
-      key._field == "temp" and
-      key.location == "sfo"
-  )
-  |> getColumn(column: "_value")
+    |> tableFind(fn: (key) => key._field == "temp" and key.location == "sfo")
+    |> getColumn(column: "_value")
 
 SFOTemps
 // Returns [65.1, 66.2, 66.3, 66.8]
@@ -136,11 +127,8 @@ The function outputs a record with key-value pairs for each column.
 
 ```js
 sampleData
-  |> tableFind(fn: (key) =>
-      key._field == "temp" and
-      key.location == "sfo"
-  )
-  |> getRecord(idx: 0)
+    |> tableFind(fn: (key) => key._field == "temp" and key.location == "sfo")
+    |> getRecord(idx: 0)
 
 // Returns {
 //   _time:2019-11-11T12:00:00Z,
@@ -158,11 +146,8 @@ keys in the record.
 
 ```js
 tempInfo = sampleData
-  |> tableFind(fn: (key) =>
-      key._field == "temp" and
-      key.location == "sfo"
-  )
-  |> getRecord(idx: 0)
+    |> tableFind(fn: (key) => key._field == "temp" and key.location == "sfo")
+    |> getRecord(idx: 0)
 
 tempInfo
 // Returns {
@@ -186,17 +171,18 @@ Create custom helper functions to extract scalar values from query output.
 ```js
 // Define a helper function to extract field values
 getFieldValue = (tables=<-, field) => {
-  extract = tables
-    |> tableFind(fn: (key) => key._field == field)
-    |> getColumn(column: "_value")
-  return extract[0]
+    extract = tables
+        |> tableFind(fn: (key) => key._field == field)
+        |> getColumn(column: "_value")
+
+    return extract[0]
 }
 
 // Use the helper function to define a variable
 lastJFKTemp = sampleData
-  |> filter(fn: (r) => r.location == "kjfk")
-  |> last()
-  |> getFieldValue(field: "temp")
+    |> filter(fn: (r) => r.location == "kjfk")
+    |> last()
+    |> getFieldValue(field: "temp")
 
 lastJFKTemp
 // Returns 71.2
@@ -206,16 +192,17 @@ lastJFKTemp
 ```js
 // Define a helper function to extract a row as a record
 getRow = (tables=<-, field, idx=0) => {
-  extract = tables
-    |> tableFind(fn: (key) => true)
-    |> getRecord(idx: idx)
-  return extract
+    extract = tables
+        |> tableFind(fn: (key) => true)
+        |> getRecord(idx: idx)
+
+    return extract
 }
 
 // Use the helper function to define a variable
 lastReported = sampleData
-  |> last()
-  |> getRow(idx: 0)
+    |> last()
+    |> getRow(field: "temp")
 
 "The last location to report was ${lastReported.location}.
 The temperature was ${string(v: lastReported._value)}°F."
diff --git a/content/enterprise_influxdb/v1.9/flux/guides/sort-limit.md b/content/enterprise_influxdb/v1.9/flux/guides/sort-limit.md
index 8fab30494..1b7ba229d 100644
--- a/content/enterprise_influxdb/v1.9/flux/guides/sort-limit.md
+++ b/content/enterprise_influxdb/v1.9/flux/guides/sort-limit.md
@@ -30,13 +30,10 @@ If you're just getting started with Flux queries, check out the following:
 The following example orders system uptime first by region, then host, then value.
 
 ```js
-from(bucket:"db/rp")
-  |> range(start:-12h)
-  |> filter(fn: (r) =>
-    r._measurement == "system" and
-    r._field == "uptime"
-  )
-  |> sort(columns:["region", "host", "_value"])
+from(bucket: "db/rp")
+    |> range(start: -12h)
+    |> filter(fn: (r) => r._measurement == "system" and r._field == "uptime")
+    |> sort(columns: ["region", "host", "_value"])
 ```
 
 The [`limit()` function](/{{< latest "flux" >}}/stdlib/universe/limit)
@@ -45,8 +42,8 @@ The following example shows up to 10 records from the past hour.
 
 ```js
 from(bucket:"db/rp")
-  |> range(start:-1h)
-  |> limit(n:10)
+    |> range(start:-1h)
+    |> limit(n:10)
 ```
 
 You can use `sort()` and `limit()` together to show the top N records.
@@ -54,14 +51,11 @@ The example below returns the 10 top system uptime values sorted first by
 region, then host, then value.
 
 ```js
-from(bucket:"db/rp")
-  |> range(start:-12h)
-  |> filter(fn: (r) =>
-    r._measurement == "system" and
-    r._field == "uptime"
-  )
-  |> sort(columns:["region", "host", "_value"])
-  |> limit(n:10)
+from(bucket: "db/rp")
+    |> range(start: -12h)
+    |> filter(fn: (r) => r._measurement == "system" and r._field == "uptime")
+    |> sort(columns: ["region", "host", "_value"])
+    |> limit(n: 10)
 ```
 
 You now have created a Flux query that sorts and limits data.
diff --git a/content/enterprise_influxdb/v1.9/flux/guides/sql.md b/content/enterprise_influxdb/v1.9/flux/guides/sql.md
index 2e8c61935..f4857fc0f 100644
--- a/content/enterprise_influxdb/v1.9/flux/guides/sql.md
+++ b/content/enterprise_influxdb/v1.9/flux/guides/sql.md
@@ -17,9 +17,9 @@ list_code_example: |
   import "sql"
 
   sql.from(
-    driverName: "postgres",
-    dataSourceName: "postgresql://user:password@localhost",
-    query: "SELECT * FROM example_table"
+      driverName: "postgres",
+      dataSourceName: "postgresql://user:password@localhost",
+      query: "SELECT * FROM example_table",
   )
   ```
 ---
@@ -53,9 +53,9 @@ To query a SQL data source:
 import "sql"
 
 sql.from(
-  driverName: "postgres",
-  dataSourceName: "postgresql://user:password@localhost",
-  query: "SELECT * FROM example_table"
+    driverName: "postgres",
+    dataSourceName: "postgresql://user:password@localhost",
+    query: "SELECT * FROM example_table",
 )
 ```
 {{% /code-tab-content %}}
@@ -65,9 +65,9 @@ sql.from(
 import "sql"
 
 sql.from(
-  driverName: "mysql",
-  dataSourceName: "user:password@tcp(localhost:3306)/db",
-  query: "SELECT * FROM example_table"
+    driverName: "mysql",
+    dataSourceName: "user:password@tcp(localhost:3306)/db",
+    query: "SELECT * FROM example_table",
 )
 ```
 {{% /code-tab-content %}}
@@ -80,9 +80,9 @@ sql.from(
 
 import "sql"
 sql.from(
-  driverName: "sqlite3",
-  dataSourceName: "file:/path/to/test.db?cache=shared&mode=ro",
-  query: "SELECT * FROM example_table"
+    driverName: "sqlite3",
+    dataSourceName: "file:/path/to/test.db?cache=shared&mode=ro",
+    query: "SELECT * FROM example_table",
 )
 ```
 {{% /code-tab-content %}}
@@ -106,15 +106,15 @@ import "sql"
 
 // Query data from PostgreSQL
 sensorInfo = sql.from(
-  driverName: "postgres",
-  dataSourceName: "postgresql://localhost?sslmode=disable",
-  query: "SELECT * FROM sensors"
+    driverName: "postgres",
+    dataSourceName: "postgresql://localhost?sslmode=disable",
+    query: "SELECT * FROM sensors",
 )
 
 // Query data from InfluxDB
 sensorMetrics = from(bucket: "telegraf/autogen")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "airSensors")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "airSensors")
 
 // Join InfluxDB query results with PostgreSQL query results
 join(tables: {metric: sensorMetrics, info: sensorInfo}, on: ["sensor_id"])
diff --git a/content/enterprise_influxdb/v1.9/flux/guides/window-aggregate.md b/content/enterprise_influxdb/v1.9/flux/guides/window-aggregate.md
index 25ef0fdd1..4fb3168e8 100644
--- a/content/enterprise_influxdb/v1.9/flux/guides/window-aggregate.md
+++ b/content/enterprise_influxdb/v1.9/flux/guides/window-aggregate.md
@@ -37,12 +37,9 @@ The following example queries the memory usage of the host machine.
 
 ```js
 dataSet = from(bucket: "db/rp")
-  |> range(start: -5m)
-  |> filter(fn: (r) =>
-    r._measurement == "mem" and
-    r._field == "used_percent"
-  )
-  |> drop(columns: ["host"])
+    |> range(start: -5m)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+    |> drop(columns: ["host"])
 ```
 
 {{% note %}}
@@ -103,7 +100,7 @@ set into one minute windows.
 
 ```js
 dataSet
-  |> window(every: 1m)
+    |> window(every: 1m)
 ```
 
 {{% note %}}
@@ -195,8 +192,8 @@ to output the average of each window:
 
 ```js
 dataSet
-  |> window(every: 1m)
-  |> mean()
+    |> window(every: 1m)
+    |> mean()
 ```
 
 {{% truncate %}}
@@ -259,9 +256,9 @@ duplicate either the `_start` or `_stop` column as a new `_time` column.
 
 ```js
 dataSet
-  |> window(every: 1m)
-  |> mean()
-  |> duplicate(column: "_stop", as: "_time")
+    |> window(every: 1m)
+    |> mean()
+    |> duplicate(column: "_stop", as: "_time")
 ```
 
 {{% truncate %}}
@@ -310,10 +307,10 @@ Use the `window()` function to "unwindow" your data into a single infinite (`inf
 
 ```js
 dataSet
-  |> window(every: 1m)
-  |> mean()
-  |> duplicate(column: "_stop", as: "_time")
-  |> window(every: inf)
+    |> window(every: 1m)
+    |> mean()
+    |> duplicate(column: "_stop", as: "_time")
+    |> window(every: inf)
 ```
 
 {{% note %}}
@@ -350,5 +347,5 @@ The following Flux query will return the same results:
 ###### aggregateWindow function
 ```js
 dataSet
-  |> aggregateWindow(every: 1m, fn: mean)
+    |> aggregateWindow(every: 1m, fn: mean)
 ```
diff --git a/content/enterprise_influxdb/v1.9/flux/optimize-queries.md b/content/enterprise_influxdb/v1.9/flux/optimize-queries.md
index be44bb903..a0dfbd141 100644
--- a/content/enterprise_influxdb/v1.9/flux/optimize-queries.md
+++ b/content/enterprise_influxdb/v1.9/flux/optimize-queries.md
@@ -65,13 +65,13 @@ subsequent operations there.
 ##### Pushdown functions in use
 ```js
 from(bucket: "db/rp")
-  |> range(start: -1h)                       //
-  |> filter(fn: (r) => r.sensor == "abc123") //
-  |> group(columns: ["_field", "host"])      // Pushed to the data source
-  |> aggregateWindow(every: 5m, fn: max)     //
-  |> filter(fn: (r) => r._value >= 90.0)     //
+    |> range(start: -1h)                       //
+    |> filter(fn: (r) => r.sensor == "abc123") //
+    |> group(columns: ["_field", "host"])      // Pushed to the data source
+    |> aggregateWindow(every: 5m, fn: max)     //
+    |> filter(fn: (r) => r._value >= 90.0)     //
 
-  |> top(n: 10)                              // Run in memory
+    |> top(n: 10)                              // Run in memory
 ```
 
 ### Avoid processing filters inline
@@ -88,8 +88,8 @@ to the underlying data source and loads all data returned from `range()` into me
 
 ```js
 from(bucket: "db/rp")
-  |> range(start: -1h)                      
-  |> filter(fn: (r) => r.region == v.provider + v.region)
+    |> range(start: -1h)                      
+    |> filter(fn: (r) => r.region == v.provider + v.region)
 ```
 
 To dynamically set filters and maintain the pushdown ability of the `filter()` function,
@@ -99,8 +99,8 @@ use variables to define filter values outside of `filter()`:
 region = v.provider + v.region
 
 from(bucket: "db/rp")
-  |> range(start: -1h)                      
-  |> filter(fn: (r) => r.region == region)
+    |> range(start: -1h)                      
+    |> filter(fn: (r) => r.region == region)
 ```
 
 ## Avoid short window durations
@@ -136,17 +136,17 @@ The following queries are functionally the same, but using `set()` is more perfo
 
 ```js
 data
-  |> map(fn: (r) => ({ r with foo: "bar" }))
+    |> map(fn: (r) => ({ r with foo: "bar" }))
 
 // Recommended
 data
-  |> set(key: "foo", value: "bar")
+    |> set(key: "foo", value: "bar")
 ```
 
 #### Dynamically set a column value using existing row data
 ```js
 data
-  |> map(fn: (r) => ({ r with foo: r.bar }))
+    |> map(fn: (r) => ({ r with foo: r.bar }))
 ```
 
 ## Balance time range and data precision
diff --git a/content/enterprise_influxdb/v1.9/guides/authenticate.md b/content/enterprise_influxdb/v1.9/guides/authenticate.md
index 49fad2a00..106cd990c 100644
--- a/content/enterprise_influxdb/v1.9/guides/authenticate.md
+++ b/content/enterprise_influxdb/v1.9/guides/authenticate.md
@@ -110,7 +110,7 @@ This is currently only possible through the [InfluxDB HTTP API](/enterprise_infl
    InfluxDB Enterprise uses the shared secret to encode the JWT signature.
    By default, `shared-secret` is set to an empty string, in which case no JWT authentication takes place.
    <!-- TODO: meta, data, or both? -->
-   Add a custom shared secret in your [InfluxDB configuration file](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes/#shared-secret--).
+   Add a custom shared secret in your [InfluxDB configuration file](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes/#shared-secret).
    The longer the secret string, the more secure it is:
 
    ```toml
diff --git a/content/enterprise_influxdb/v1.9/guides/calculate_percentages.md b/content/enterprise_influxdb/v1.9/guides/calculate_percentages.md
index 4cd821d4b..5e9c099f7 100644
--- a/content/enterprise_influxdb/v1.9/guides/calculate_percentages.md
+++ b/content/enterprise_influxdb/v1.9/guides/calculate_percentages.md
@@ -56,17 +56,17 @@ Here's how that looks in Flux:
 ```js
 // Query data from the past 15 minutes pivot fields into columns so each row
 // contains values for each field
-data = from(bucket:"your_db/your_retention_policy")
-  |> range(start: -15m)
-  |> filter(fn: (r) =>  r._measurement == "measurement_name" and r._field =~ /field[1-2]/)
-  |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
+data = from(bucket: "your_db/your_retention_policy")
+    |> range(start: -15m)
+    |> filter(fn: (r) => r._measurement == "measurement_name" and r._field =~ /field[1-2]/)
+    |> pivot(rowKey: ["_time"], columnKey: ["_field"], valueColumn: "_value")
 ```
 
 Each row now contains the values necessary to perform a math operation. For example, to add two field keys, start with the `data` variable created above, and then use `map()` to re-map values in each row.
 
 ```js
 data
- |> map(fn: (r) => ({ r with _value: r.field1 + r.field2}))
+    |> map(fn: (r) => ({ r with _value: r.field1 + r.field2}))
 ```
 
 > **Note:** Flux supports basic math operators such as `+`,`-`,`/`, `*`, and `()`. For example, to subtract `field2` from `field1`, change `+` to `-`.
@@ -77,12 +77,14 @@ Use the `data` variable created above, and then use the [`map()` function](/{{<
 
 ```js
 data
-   |> map(fn: (r) => ({
-    _time: r._time,
-    _measurement: r._measurement,
-    _field: "percent",
-    _value: field1 / field2 * 100.0
-  }))
+    |> map(
+        fn: (r) => ({
+            _time: r._time,
+            _measurement: r._measurement,
+            _field: "percent",
+            _value: field1 / field2 * 100.0
+        })
+    )
 ```
 
 >**Note:** In this example, `field1` and `field2` are float values, hence multiplied by 100.0. For integer values, multiply by 100 or use the `float()` function to cast integers to floats.
@@ -92,12 +94,12 @@ data
 Use [`aggregateWindow()`](/{{< latest "flux" >}}/stdlib/universe/aggregatewindow) to window data by time and perform an aggregate function on each window.
 
 ```js
-from(bucket:"<database>/<retention_policy>")
-  |> range(start: -15m)
-  |> filter(fn: (r) =>  r._measurement == "measurement_name" and r._field =~ /fieldkey[1-2]/)
-  |> aggregateWindow(every: 1m, fn:sum)
-  |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
-  |> map(fn: (r) => ({ r with _value: r.field1 / r.field2 * 100.0 }))
+from(bucket: "<database>/<retention_policy>")
+    |> range(start: -15m)
+    |> filter(fn: (r) => r._measurement == "measurement_name" and r._field =~ /fieldkey[1-2]/)
+    |> aggregateWindow(every: 1m, fn: sum)
+    |> pivot(rowKey: ["_time"], columnKey: ["_field"], valueColumn: "_value")
+    |> map(fn: (r) => ({r with _value: r.field1 / r.field2 * 100.0}))
 ```
 
 ## Calculate the percentage of total weight per apple variety
@@ -115,16 +117,19 @@ Use the following query to calculate the percentage of the total weight each var
 accounts for at each given point in time.
 
 ```js
-from(bucket:"apple_stand/autogen")
+from(bucket: "apple_stand/autogen")
     |> range(start: 2018-06-18T12:00:00Z, stop: 2018-06-19T04:35:00Z)
-    |> filter(fn: (r) =>  r._measurement == "variety")
-    |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
-    |> map(fn: (r) => ({ r with
-      granny_smith: r.granny_smith / r.total_weight * 100.0 ,
-      golden_delicious: r.golden_delicious / r.total_weight * 100.0 ,
-      fuji: r.fuji / r.total_weight * 100.0 ,
-      gala: r.gala / r.total_weight * 100.0 ,
-      braeburn: r.braeburn / r.total_weight * 100.0 ,}))
+    |> filter(fn: (r) => r._measurement == "variety")
+    |> pivot(rowKey: ["_time"], columnKey: ["_field"], valueColumn: "_value")
+    |> map(
+        fn: (r) => ({r with
+            granny_smith: r.granny_smith / r.total_weight * 100.0,
+            golden_delicious: r.golden_delicious / r.total_weight * 100.0,
+            fuji: r.fuji / r.total_weight * 100.0,
+            gala: r.gala / r.total_weight * 100.0,
+            braeburn: r.braeburn / r.total_weight * 100.0,
+        }),
+    )
 ```
 
 ## Calculate the average percentage of total weight per variety each hour
@@ -132,18 +137,20 @@ from(bucket:"apple_stand/autogen")
 With the apple stand data from the prior example, use the following query to calculate the average percentage of the total weight each variety accounts for per hour.
 
 ```js
-from(bucket:"apple_stand/autogen")
-  |> range(start: 2018-06-18T00:00:00.00Z, stop: 2018-06-19T16:35:00.00Z)
-  |> filter(fn: (r) => r._measurement == "variety")
-  |> aggregateWindow(every:1h, fn: mean)
-  |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
-  |> map(fn: (r) => ({ r with
-    granny_smith: r.granny_smith / r.total_weight * 100.0,
-    golden_delicious: r.golden_delicious / r.total_weight * 100.0,
-    fuji: r.fuji / r.total_weight * 100.0,
-    gala: r.gala / r.total_weight * 100.0,
-    braeburn: r.braeburn / r.total_weight * 100.0
-  }))
+from(bucket: "apple_stand/autogen")
+    |> range(start: 2018-06-18T00:00:00Z, stop: 2018-06-19T16:35:00Z)
+    |> filter(fn: (r) => r._measurement == "variety")
+    |> aggregateWindow(every: 1h, fn: mean)
+    |> pivot(rowKey: ["_time"], columnKey: ["_field"], valueColumn: "_value")
+    |> map(
+        fn: (r) => ({r with
+            granny_smith: r.granny_smith / r.total_weight * 100.0,
+            golden_delicious: r.golden_delicious / r.total_weight * 100.0,
+            fuji: r.fuji / r.total_weight * 100.0,
+            gala: r.gala / r.total_weight * 100.0,
+            braeburn: r.braeburn / r.total_weight * 100.0,
+        }),
+    )
 ```
 
 {{% /tab-content %}}
diff --git a/content/enterprise_influxdb/v1.9/guides/downsample_and_retain.md b/content/enterprise_influxdb/v1.9/guides/downsample_and_retain.md
index 3fcd19824..4587fe898 100644
--- a/content/enterprise_influxdb/v1.9/guides/downsample_and_retain.md
+++ b/content/enterprise_influxdb/v1.9/guides/downsample_and_retain.md
@@ -214,7 +214,7 @@ data that reside in an RP other than the `DEFAULT` RP.
 Between checks, `orders` may have data that are older than two hours.
 The rate at which InfluxDB checks to enforce an RP is a configurable setting,
 see
-[Database Configuration](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes/#check-interval--30m0s).
+[Database Configuration](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes/#check-interval).
 
 Using a combination of RPs and CQs, we've successfully set up our database to
 automatically keep the high precision raw data for a limited time, create lower
diff --git a/content/enterprise_influxdb/v1.9/introduction/download.md b/content/enterprise_influxdb/v1.9/introduction/download.md
index e95d38028..c65977815 100644
--- a/content/enterprise_influxdb/v1.9/introduction/download.md
+++ b/content/enterprise_influxdb/v1.9/introduction/download.md
@@ -18,5 +18,5 @@ If you have purchased a license or already obtained a demo license,
 log in to the [InfluxDB Enterprise portal](https://portal.influxdata.com/users/sign_in)
 to get your license key and download URLs.
 
-See the [installation documentation](/enterprise_influxdb/v1.9/install-and-deploy/)
+See the [installation documentation](/enterprise_influxdb/v1.9/introduction/installation/)
 for more information about getting started.
diff --git a/content/enterprise_influxdb/v1.9/introduction/getting-started.md b/content/enterprise_influxdb/v1.9/introduction/getting-started.md
index 3af569497..b5fc29ac4 100644
--- a/content/enterprise_influxdb/v1.9/introduction/getting-started.md
+++ b/content/enterprise_influxdb/v1.9/introduction/getting-started.md
@@ -11,7 +11,7 @@ menu:
     parent: Introduction
 ---
 
-After you successfully [install and set up](/enterprise_influxdb/v1.9/install-and-deploy/installation/) InfluxDB Enterprise, learn how to [monitor your InfluxDB Enterprise clusters](/{{< latest "chronograf" >}}/guides/monitoring-influxenterprise-clusters) with Chronograf, InfluxDB, and Telegraf.
+After you successfully [install and set up](/enterprise_influxdb/v1.9/introduction/installation/installation/) InfluxDB Enterprise, learn how to [monitor your InfluxDB Enterprise clusters](/{{< latest "chronograf" >}}/guides/monitoring-influxenterprise-clusters) with Chronograf, InfluxDB, and Telegraf.
 
 ### Where to from here?
 
diff --git a/content/enterprise_influxdb/v1.9/introduction/install-and-deploy/_index.md b/content/enterprise_influxdb/v1.9/introduction/install-and-deploy/_index.md
deleted file mode 100644
index e842680d4..000000000
--- a/content/enterprise_influxdb/v1.9/introduction/install-and-deploy/_index.md
+++ /dev/null
@@ -1,33 +0,0 @@
----
-title: Install and deploy InfluxDB Enterprise
-description: Install InfluxDB Enterprise to on-premise or cloud providers, including Google Cloud Platform, Amazon Web Services, and Azure.
-aliases:
-- /enterprise_influxdb/v1.9/install-and-deploy/deploying/
-- /enterprise_influxdb/v1.9/install-and-deploy/
-- /enterprise_influxdb/v1.9/introduction/get-started/
-- /enterprise_influxdb/v1.9/production_installation/
-- /enterprise_influxdb/v1.9/introduction/installation/
-
-menu:
-  enterprise_influxdb_1_9:
-    name: Install and deploy
-    weight: 30
-    parent: Introduction
----
-
-Install or deploy your InfluxDB Enterprise cluster in the environment of your choice:
-
-- Your own environment
-- Your cloud provider
-
-## Your own environment
-
-Learn how to [install a cluster in your own environment](/enterprise_influxdb/v1.9/install-and-deploy/installation/).
-
-## Your cloud provider
-
-Learn how to deploy a cluster on the cloud provider of your choice:
-
-   - [GCP](/enterprise_influxdb/v1.9/install-and-deploy/deploying/google-cloud-platform/)
-   - [AWS](/enterprise_influxdb/v1.9/install-and-deploy/deploying/aws/)
-   - [Azure](/enterprise_influxdb/v1.9/install-and-deploy/deploying/azure/)
diff --git a/content/enterprise_influxdb/v1.9/introduction/install-and-deploy/deploying/_index.md b/content/enterprise_influxdb/v1.9/introduction/install-and-deploy/deploying/_index.md
deleted file mode 100644
index eee062c65..000000000
--- a/content/enterprise_influxdb/v1.9/introduction/install-and-deploy/deploying/_index.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: Deploy InfluxDB Enterprise clusters
-description: >
-  Install InfluxDB Enterprise to a cloud provider of your choice, including Google Cloud Platform, Amazon Web Services, and Azure.
-aliases:
-    - /enterprise_influxdb/v1.9/other-options/
-    - /enterprise_influxdb/v1.9/install-and-deploy/deploying/index/
-menu:
-  enterprise_influxdb_1_9:
-    name: Deploy in cloud
-    identifier: deploy-in-cloud-enterprise
-    weight: 30
-    parent: Install and deploy
----
-
-Deploy InfluxDB Enterprise clusters on the cloud provider of your choice.
-
-> **Note:** To install in your own environment, see [Install an InfluxDB Enterprise cluster in your own environment](/enterprise_influxdb/v1.9/install-and-deploy/installation/).
-
-{{< children hlevel="h2" >}}
diff --git a/content/enterprise_influxdb/v1.9/introduction/install-and-deploy/deploying/aws/_index.md b/content/enterprise_influxdb/v1.9/introduction/install-and-deploy/deploying/aws/_index.md
deleted file mode 100644
index 3031ff526..000000000
--- a/content/enterprise_influxdb/v1.9/introduction/install-and-deploy/deploying/aws/_index.md
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: Deploy InfluxDB Enterprise clusters on Amazon Web Services
-description: Deploy InfluxDB Enterprise clusters on Amazon Web Services (AWS).
-aliases:
-    - /enterprise_influxdb/v1.9/other-options/
-    - /enterprise_influxdb/v1.9/install-and-deploy/aws/
-    - /enterprise_influxdb/v1.9/install-and-deploy/deploying/aws/
-menu:
-  enterprise_influxdb_1_9:
-    name: AWS
-    identifier: deploy-on-aws
-    weight: 30
-    parent: deploy-in-cloud-enterprise
----
-
-The following articles detail how to deploy InfluxDB clusters in AWS:
-
-- [Deploy an InfluxDB Enterprise cluster on Amazon Web Services](/enterprise_influxdb/v1.9/install-and-deploy/deploying/aws/setting-up-template)
-- [AWS configuration options](/enterprise_influxdb/v1.9/install-and-deploy/deploying/aws/config-options)
diff --git a/content/enterprise_influxdb/v1.9/introduction/install-and-deploy/deploying/aws/config-options.md b/content/enterprise_influxdb/v1.9/introduction/install-and-deploy/deploying/aws/config-options.md
deleted file mode 100644
index 088faadce..000000000
--- a/content/enterprise_influxdb/v1.9/introduction/install-and-deploy/deploying/aws/config-options.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: AWS configuration options
-description: >
-  Configuration options when deploying InfluxDB Enterprise on Amazon Web Services (AWS).
-aliases:
-    - /enterprise_influxdb/v1.9/install-and-deploy/aws/config-options/
-    - /enterprise_influxdb/v1.9/install-and-deploy/aws/config-options/
-    - /enterprise_influxdb/v1.9/install-and-deploy/deploying/aws/config-options/
-menu:
-  enterprise_influxdb_1_9:
-    name: AWS configuration options
-    weight: 30
-    parent: deploy-on-aws
----
-When deploying InfluxDB Enterprise on AWS using the template described in [Deploy an InfluxDB Enterprise cluster on Amazon Web Services](/enterprise_influxdb/v1.9/install-and-deploy/aws/setting-up-template), the following configuration options are available:
-
-- **VPC ID**: The VPC ID of your existing Virtual Private Cloud (VPC).
-- **Subnets**: A list of SubnetIds in your Virtual Private Cloud (VPC) where nodes will be created. The subnets must be in the same order as the availability zones they reside in. For a list of which availability zones correspond to which subnets, see the [Subnets section of your VPC dashboard](https://console.aws.amazon.com/vpc/home?region=us-east-1#subnets:sort=SubnetId).
-- **Availability Zones**: Availability zones to correspond with your subnets above. The availability zones must be in the same order as their related subnets. For a list of which availability zones correspond to which subnets, see the [Subnets section of your VPC dashboard](https://console.aws.amazon.com/vpc/home?region=us-east-1#subnets:sort=SubnetId).
-- **SSH Key Name**: An existing key pair to enable SSH access for the instances. For details on how to create a key pair, see [Creating a Key Pair Using Amazon EC2](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html#having-ec2-create-your-key-pair).
-- **InfluxDB ingress CIDR**: The IP address range that can be used to connect to the InfluxDB API endpoint. To allow all traffic, enter 0.0.0.0/0.
-- **SSH Access CIDR**: The IP address range that can be used to SSH into the EC2 instances. To allow all traffic, enter 0.0.0.0/0.
-- **InfluxDB Enterprise License Key**: Your InfluxDB Enterprise license key. Applies only to BYOL.
-- **InfluxDB Administrator Username**: Your InfluxDB administrator username. Applies only to BYOL.
-- **InfluxDB Administrator Password**: Your InfluxDB administrator password. Applies only to BYOL.
-- **InfluxDB Enterprise Version**: The version of InfluxDB. Defaults to current version. <!--Is this going to be taken out?-->
-- **Telegraf Version**: The version of Telegraf. Defaults to current version.
-- **InfluxDB Data Node Disk Size**: The size in GB of the EBS io1 volume each data node. Defaults to 250.
-- **InfluxDB Data Node Disk IOPS**: The IOPS of the EBS io1 volume on each data node. Defaults to 1000.
-- **DataNodeInstanceType**: The instance type of the data node. Defaults to m5.large.
-- **MetaNodeInstanceType**: The instance type of the meta node. Defaults to t3.small.
-- **MonitorInstanceType**: The instance type of the monitor node. Defaults to t3.large.
diff --git a/content/enterprise_influxdb/v1.9/introduction/install-and-deploy/deploying/aws/setting-up-template.md b/content/enterprise_influxdb/v1.9/introduction/install-and-deploy/deploying/aws/setting-up-template.md
deleted file mode 100644
index 6ff0f6583..000000000
--- a/content/enterprise_influxdb/v1.9/introduction/install-and-deploy/deploying/aws/setting-up-template.md
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: Deploy an InfluxDB Enterprise cluster on Amazon Web Services
-description: Deploy an InfluxDB Enterprise cluster on Amazon Web Services (AWS).
-aliases:
-    - /enterprise_influxdb/v1.9/install-and-deploy/aws/setting-up-template/
-    - /enterprise_influxdb/v1.9/install-and-deploy/deploying/aws/setting-up-template/
-menu:
-  enterprise_influxdb_1_9:
-    name: Deploy on Amazon Web Services
-    weight: 20
-    parent: deploy-on-aws
----
-
-Follow these steps to deploy an InfluxDB Enterprise cluster on AWS.
-
-## Step 1: Specify template
-
-After you complete the marketplace flow, you'll be directed to the Cloud Formation Template.
-
-1. In the Prepare template section, select **Template is ready**.
-2. In the Specify template section, the **Amazon S3 URL** field is automatically populated with either the BYOL or integrated billing template, depending on the option you selected in the marketplace.
-3. Click **Next**.
-
-## Step 2: Specify stack details
-
-1. In the Stack name section, enter a name for your stack.
-2. Complete the Network Configuration section:
-   - **VPC ID**: Click the dropdown menu to fill in your VPC.
-   - **Subnets**: Select three subnets.
-   - **Availability Zones**: Select three availability zones to correspond with your subnets above. The availability zones must be in the same order as their related subnets. For a list of which availability zones correspond to which subnets, see the [Subnets section of your VPC dashboard](https://console.aws.amazon.com/vpc/home?region=us-east-1#subnets:sort=SubnetId).
-   - **SSH Key Name**: Select an existing key pair to enable SSH access for the instances. For details on how to create a key pair, see [Creating a Key Pair Using Amazon EC2](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html#having-ec2-create-your-key-pair).
-   - **InfluxDB ingress CIDR**: Enter the IP address range that can be used to connect to the InfluxDB API endpoint. To allow all traffic, enter 0.0.0.0/0.
-   - **SSH Access CIDR**: Enter the IP address range that can be used to SSH into the EC2 instances. To allow all traffic, enter 0.0.0.0/0.
-3. Complete the **InfluxDB Configuration** section:
-   - **InfluxDB Enterprise License Key**: Applies only to BYOL. Enter your InfluxDB Enterprise license key.
-   - **InfluxDB Administrator Username**: Applies only to BYOL. Enter your InfluxDB administrator username.
-   - **InfluxDB Administrator Password**: Applies only to BYOL. Enter your InfluxDB administrator password.
-   - **InfluxDB Enterprise Version**: Defaults to current version. <!--IS this going to be taken out?-->
-   - **Telegraf Version**: Defaults to current version.
-   - **InfluxDB Data Node Disk Size**: The size in GB of the EBS io1 volume each data node. Defaults to 250.
-   - **InfluxDB Data Node Disk IOPS**: The IOPS of the EBS io1 volume on each data node. Defaults to 1000.
-4. Review the **Other Parameters** section and modify if needed. The fields in this section are all automatically populated and shouldn't require changes.
-   - **DataNodeInstanceType**: Defaults to m5.large.
-   - **MetaNodeInstanceType**: Defaults to t3.small.
-   - **MonitorInstanceType**: Defaults to t3.large.
-5. Click **Next**.
-
-## Step 3: Configure stack options
-
-1. In the **Tags** section, enter any key-value pairs you want to apply to resources in the stack.
-2. Review the **Permissions** and **Advanced options** sections. In most cases, there's no need to modify anything in these sections.
-3. Click **Next**.
-
-## Step 4: Review
-
-1. Review the configuration options for all of the above sections.
-2. In the **Capabilities** section, check the box acknowledging that AWS CloudFormation might create IAM resources.
-3. Click **Create stack**.
diff --git a/content/enterprise_influxdb/v1.9/introduction/install-and-deploy/deploying/azure.md b/content/enterprise_influxdb/v1.9/introduction/install-and-deploy/deploying/azure.md
deleted file mode 100644
index fecc7dff7..000000000
--- a/content/enterprise_influxdb/v1.9/introduction/install-and-deploy/deploying/azure.md
+++ /dev/null
@@ -1,76 +0,0 @@
----
-title: Deploy an InfluxDB Enterprise cluster on Azure Cloud Platform
-description: >
-  Deploy an InfluxDB Enterprise cluster on Microsoft Azure cloud computing service.
-aliases:
-  - /enterprise_influxdb/v1.9/install-and-deploy/azure/
-  - /enterprise_influxdb/v1.9/install-and-deploy/deploying/azure/
-menu:
-  enterprise_influxdb_1_9:
-    name: Azure
-    weight: 20
-    parent: deploy-in-cloud-enterprise
----
-
-For deploying InfluxDB Enterprise clusters on Microsoft Azure cloud computing service, InfluxData provides an [InfluxDB Enterprise application](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/influxdata.influxdb-enterprise-cluster) on the [Azure Marketplace](https://azuremarketplace.microsoft.com/) that makes the installation and setup process easy and straightforward. Clusters are deployed through an Azure Marketplace subscription and are ready for production. Billing occurs through your Azure subscription.
-
-> Please submit issues and feature requests for the Azure Marketplace deployment [through the related GitHub repository](https://github.com/influxdata/azure-resource-manager-influxdb-enterprise/issues/new) (requires a GitHub account) or by contacting [InfluxData Support](mailto:support@influxdata.com).
-
-## Prerequisites
-
-This guide requires the following:
-
-- Microsoft Azure account with access to the [Azure Marketplace](https://azuremarketplace.microsoft.com/).
-- SSH access to cluster instances.
-
-To deploy InfluxDB Enterprise clusters on platforms other than Azure, see [Deploy InfluxDB Enterprise](/enterprise_influxdb/v1.9/install-and-deploy/).
-
-## Deploy a cluster
-
-1. Log in to your Azure Cloud Platform account and navigate to [InfluxData's InfluxDB Enterprise (Official Version) application](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/influxdata.influxdb-enterprise-cluster) on Azure Marketplace.
-
-2. Click **Get It Now**, read and agree to the terms of use, and then click **Continue**. Once in the Azure Portal, click **Create**.
-
-3. Select the subscription to use for your InfluxDB Enterprise cluster. Then select a resource group and region where the cluster resources will be deployed.
-
-    > **Tip:** If you do not know which resource group to use, we recommend creating a new one for the InfluxDB Enterprise cluster.
-
-4. In the Instance Details section, set the OS username and SSH authentication type you will use to access the cluster VMs. For password authentication, enter a username and password. For SSH public key authentication, copy an SSH public key. The cluster VMs are built from an Ubuntu base image.
-
-5. Click **Next: Cluster Configuration**, and then enter details including the InfluxDB admin username and password, the number of meta and data nodes, and the VM size for both meta and data nodes. We recommend using the default VM sizes and increasing the data node VM size if you anticipate needing more resources for your workload.
-
-    > **Note:** Make sure to save the InfluxDB admin credentials. They will be required to access InfluxDB.
-
-6. Click **Next: External Access & Chronograf**, and then do the following:
-
-   - To create a separate instance to monitor the cluster and run [Chronograf](https://www.influxdata.com/time-series-platform/chronograf/), select **Yes**. Otherwise, select **No**.
-
-          > **Note:** Adding a Chronograf instance will also configure that instance as an SSH bastion. All cluster instances will only be accessible through the Chronograf instance.
-
-   - Select the appropriate access for the InfluxDB load balancer: **External** to allow external Internet access; otherwise, select **Internal**.
-
-        {{% warn %}}The cluster uses HTTP by default. You must configure HTTPS after the cluster has been deployed.{{% /warn %}}
-
-7. Click **Next: Review + create** to validate your cluster configuration details. If validation passes, your InfluxDB Enterprise cluster is deployed.
-
-    > **Note:** Some Azure accounts may have vCPU quotas limited to 10 vCPUs available in certain regions. Selecting VM sizes larger than the default can cause a validation error for exceeding the vCPU limit for the region.
-
-## Access InfluxDB
-
-Once the cluster is created, access the InfluxDB API at the IP address associated with the load balancer resource (`lb-influxdb`). If external access was configured during setup, the load balancer is publicly accessible. Otherwise, the load balancer is only accessible to the cluster's virtual network.
-
-Use the load balancer IP address and the InfluxDB admin credentials entered during the cluster creation to interact with InfluxDB Enterprise via the [`influx` CLI](/enterprise_influxdb/v1.9/tools/influx-cli/use-influx/) or use the InfluxDB's [query](/enterprise_influxdb/v1.9/guides/query_data/) and [write](/enterprise_influxdb/v1.9/guides/write_data/) HTTP APIs.
-
-## Access the cluster
-
-The InfluxDB Enterprise cluster's VMs are only reachable within the virtual network using the SSH credentails provided during setup.
-
-If a Chronograf instance has been added to the cluster, the Chronograf instance is publically accessible via SSH. The other VMs can then be reached from the Chronograf VM.
-
-## Testing
-
-Azure Resource Manager (ARM) templates used in the InfluxDB Enterprise offering on Azure Marketplace are [available for testing purposes](https://github.com/influxdata/azure-resource-manager-influxdb-enterprise). **Please note, these templates are under active development and not recommended for production.**
-
-### Next steps
-
-For an introduction to the InfluxDB database and the InfluxData Platform, see [Getting started with InfluxDB](/platform/introduction/getting-started).
diff --git a/content/enterprise_influxdb/v1.9/introduction/install-and-deploy/deploying/google-cloud-platform.md b/content/enterprise_influxdb/v1.9/introduction/install-and-deploy/deploying/google-cloud-platform.md
deleted file mode 100644
index cd457f5c8..000000000
--- a/content/enterprise_influxdb/v1.9/introduction/install-and-deploy/deploying/google-cloud-platform.md
+++ /dev/null
@@ -1,103 +0,0 @@
----
-title: Deploy an InfluxDB Enterprise cluster on Google Cloud Platform
-description: >
-  Deploy an InfluxDB Enterprise cluster on Google Cloud Platform (GCP).
-aliases:
-    - /enterprise_influxdb/v1.9/other-options/google-cloud/
-    - /enterprise_influxdb/v1.9/install-and-deploy/google-cloud-platform/
-    - /enterprise_influxdb/v1.9/install-and-deploy/deploying/google-cloud-platform/
-menu:
-  enterprise_influxdb_1_9:
-    name: GCP
-    weight: 30
-    parent: deploy-in-cloud-enterprise
----
-
-Complete the following steps to deploy an InfluxDB Enterprise cluster on Google Cloud Platform (GCP):
-
-1. [Verify prerequistes](#verify-prerequisites).
-2. [Deploy a cluster](#deploy-a-cluster).
-3. [Access the cluster](#access-the-cluster).
-
-After deploying your cluster, see [Getting started with InfluxDB](/platform/introduction/getting-started) for an introduction to InfluxDB database and the InfluxData platform.
-
->**Note:** InfluxDB Enterprise on GCP is a self-managed product. For a fully managed InfluxDB experience, check out [InfluxDB Cloud](/influxdb/cloud/sign-up/).
-
-## Verify prerequisites
-
-Before deploying an InfluxDB Enterprise cluster on GCP, verify you have the following prerequisites:
-
-- A [Google Cloud Platform (GCP)](https://cloud.google.com/) account with access to the [GCP Marketplace](https://cloud.google.com/marketplace/).
-- Access to [GCP Cloud Shell](https://cloud.google.com/shell/) or the [`gcloud` SDK and command line tools](https://cloud.google.com/sdk/).
-
-## Deploy a cluster
-
-1. Log in to your Google Cloud Platform account and go to [InfluxDB Enterprise](https://console.cloud.google.com/marketplace/details/influxdata-public/influxdb-enterprise-vm).
-
-2. Click **Launch** to create or select a project to open up your cluster's configuration page.
-
-3. Adjust cluster fields as needed, including:
-
-  - Deployment name: Enter a name for the InfluxDB Enterprise cluster.
-  - InfluxDB Enterprise admin username: Enter the username of your cluster administrator.
-  - Zone: Select a region for your cluster.
-  - Network: Select a network for your cluster.
-  - Subnetwork: Select a subnetwork for your cluster, if applicable.
-
-        > **Note:** The cluster is only accessible within the network (or subnetwork, if specified) where it's deployed.
-
-4. Adjust data node fields as needed, including:
-
-  - Data node instance count: Enter the number of data nodes to include in your cluster (we recommend starting with the default, 2).
-  - Data node machine type: Select the virtual machine type to use for data nodes (by default, 4 vCPUs). Use the down arrow to scroll through list. Notice the amount of memory available for the selected machine. To alter the number of cores and memory for your selected machine type, click the **Customize** link.
-
-  <!-- For detail, see our recommended [hardware sizing guidelines](/enterprise_influxdb/v1.9/reference/hardware_sizing/). -->
-
-  - (Optional) By default, the data node disk type is SSD Persistent Disk and the disk size is 250 GB. To alter these defaults, click More and update if needed.
-
-        > **Note:** Typically, fields in collapsed sections don't need to be altered.
-
-5. Adjust meta node fields as needed, including:
-
-  - Meta node instance count: Enter the number of meta nodes to include in your cluster (we recommend using the default, 3).
-  - Meta node machine type: Select the virtual machine type to use for meta nodes (by default, 1 vCPUs). Use the down arrow to scroll through list. Notice the amount of memory available for the selected machine. To alter the number of cores and memory for your selected machine type, click the **Customize** link.
-  - By default, the meta node disk type is SSD Persistent Disk and the disk size is 10 GB. Alter these defaults if needed.
-
-6. (Optional) Adjust boot disk options fields is needed. By default the boot disk type is Standard Persistent disk and boot disk is 10 GB .
-
-7. Accept terms and conditions by selecting both check boxes, and then click **Deploy** to launch the InfluxDB Enterprise cluster.
-
-The cluster may take a few minutes to fully deploy. If the deployment does not complete or reports an error, read through the list of [common deployment errors](https://cloud.google.com/marketplace/docs/troubleshooting).
-
-> **Important:** Make sure you save the "Admin username", "Admin password", and "Connection internal IP" values displayed on the screen. They are required to access the cluster.
-
-## Access the cluster
-
-Access the cluster's IP address from the GCP network (or subnetwork) specified when you deployed the cluster. A cluster can only be reached from instances or services in the same GCP network or subnetwork.
-
-1. In the GCP Cloud Shell or `gcloud` CLI, create a new instance to access the InfluxDB Enterprise cluster.
-
-    ```
-    gcloud compute instances create influxdb-access --image-family ubuntu-1804-lts --image-project ubuntu-os-cloud
-    ```
-
-2. SSH into the instance.
-
-    ```
-    gcloud compute ssh influxdb-access
-    ```
-
-3. On the instance, install the `influx` command line tool via the InfluxDB open source package.
-
-    ```
-    wget https://dl.influxdata.com/influxdb/releases/influxdb_{{< latest-patch >}}_amd64.deb
-    sudo dpkg -i influxdb_{{< latest-patch >}}_amd64.deb
-    ```
-
-4. Access the InfluxDB Enterprise cluster using the following command with "Admin username", "Admin password", and "Connection internal IP" values from the deployment screen substituted for `<value>`.
-
-    ```
-    influx -username <Admin username> -password <Admin password> -host <Connection internal IP> -execute "CREATE DATABASE test"
-
-    influx -username <Admin username> -password <Admin password> -host <Connection internal IP> -execute "SHOW DATABASES"
-    ```
diff --git a/content/enterprise_influxdb/v1.9/introduction/install-and-deploy/installation/_index.md b/content/enterprise_influxdb/v1.9/introduction/install-and-deploy/installation/_index.md
deleted file mode 100644
index 7fa21d69a..000000000
--- a/content/enterprise_influxdb/v1.9/introduction/install-and-deploy/installation/_index.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: Install an InfluxDB Enterprise cluster in your own environment
-description: Install InfluxDB Enterprise in your own on-premise environment.
-aliases:
-    - /enterprise_influxdb/v1.9/installation/
-    - /enterprise_influxdb/v1.9/install-and-deploy/installation/
-menu:
-  enterprise_influxdb_1_9:
-    name: Install in your environment
-    weight: 10
-    parent: Install and deploy
----
-
-Complete the following steps to install an InfluxDB Enterprise cluster in your own environment:
-
-1. [Install InfluxDB Enterprise meta nodes](/enterprise_influxdb/v1.9/install-and-deploy/installation/meta_node_installation/)
-2. [Install InfluxDB data nodes](/enterprise_influxdb/v1.9/install-and-deploy/installation/data_node_installation/)
-3. [Install Chronograf](/enterprise_influxdb/v1.9/install-and-deploy/installation/chrono_install/)
-
-> **Note:** If you're looking for cloud infrastructure and services, check out how to deploy InfluxDB Enterprise (production-ready) on a cloud provider of your choice: [Azure](/enterprise_influxdb/v1.9/install-and-deploy/deploying/azure/), [GCP](/enterprise_influxdb/v1.9/install-and-deploy/deploying/google-cloud-platform/), or [AWS](/enterprise_influxdb/v1.9/install-and-deploy/deploying/aws/).
diff --git a/content/enterprise_influxdb/v1.9/introduction/installation/_index.md b/content/enterprise_influxdb/v1.9/introduction/installation/_index.md
new file mode 100644
index 000000000..533102d72
--- /dev/null
+++ b/content/enterprise_influxdb/v1.9/introduction/installation/_index.md
@@ -0,0 +1,20 @@
+---
+title: Install an InfluxDB Enterprise cluster
+description: Install InfluxDB Enterprise in your own on-premise environment.
+aliases:
+    - /enterprise_influxdb/v1.9/installation/
+    - /enterprise_influxdb/v1.9/introduction/installation/installation/
+    - /enterprise_influxdb/v1.9/introduction/install-and-deploy/
+    - /enterprise_influxdb/v1.9/install-and-deploy/
+menu:
+  enterprise_influxdb_1_9:
+    name: Install
+    weight: 103
+    parent: Introduction
+---
+
+Complete the following steps to install an InfluxDB Enterprise cluster in your own environment:
+
+1. [Install InfluxDB Enterprise meta nodes](/enterprise_influxdb/v1.9/introduction/installation/installation/meta_node_installation/)
+2. [Install InfluxDB data nodes](/enterprise_influxdb/v1.9/introduction/installation/installation/data_node_installation/)
+3. [Install Chronograf](/enterprise_influxdb/v1.9/introduction/installation/installation/chrono_install/)
diff --git a/content/enterprise_influxdb/v1.9/introduction/install-and-deploy/installation/chrono_install.md b/content/enterprise_influxdb/v1.9/introduction/installation/chrono_install.md
similarity index 80%
rename from content/enterprise_influxdb/v1.9/introduction/install-and-deploy/installation/chrono_install.md
rename to content/enterprise_influxdb/v1.9/introduction/installation/chrono_install.md
index 1c9eb2e0d..792297272 100644
--- a/content/enterprise_influxdb/v1.9/introduction/install-and-deploy/installation/chrono_install.md
+++ b/content/enterprise_influxdb/v1.9/introduction/installation/chrono_install.md
@@ -2,12 +2,12 @@
 title: Install Chronograf
 aliases:
     - /enterprise_influxdb/v1.9/installation/chrono_install/
-    - /enterprise_influxdb/v1.9/install-and-deploy/installation/chrono_install/
+    - /enterprise_influxdb/v1.9/introduction/installation/installation/chrono_install/
 menu:
   enterprise_influxdb_1_9:
     name: Install Chronograf
     weight: 30
-    parent: Install in your environment
+    parent: Install
     identifier: chrono_install
 ---
 
diff --git a/content/enterprise_influxdb/v1.9/introduction/install-and-deploy/installation/data_node_installation.md b/content/enterprise_influxdb/v1.9/introduction/installation/data_node_installation.md
similarity index 96%
rename from content/enterprise_influxdb/v1.9/introduction/install-and-deploy/installation/data_node_installation.md
rename to content/enterprise_influxdb/v1.9/introduction/installation/data_node_installation.md
index 98495bab0..534ecce7b 100644
--- a/content/enterprise_influxdb/v1.9/introduction/install-and-deploy/installation/data_node_installation.md
+++ b/content/enterprise_influxdb/v1.9/introduction/installation/data_node_installation.md
@@ -2,12 +2,12 @@
 title: Install InfluxDB Enterprise data nodes
 aliases:
     - /enterprise_influxdb/v1.9/installation/data_node_installation/
-    - /enterprise_influxdb/v1.9/install-and-deploy/installation/data_node_installation/
+    - /enterprise_influxdb/v1.9/introduction/installation/installation/data_node_installation/
 menu:
   enterprise_influxdb_1_9:
     name: Install data nodes
     weight: 20
-    parent: Install in your environment
+    parent: Install
 ---
 
 InfluxDB Enterprise offers highly scalable clusters on your infrastructure
@@ -17,7 +17,7 @@ your InfluxDB Enterprise cluster: the data nodes.
 
 {{% warn %}}
 If you have not set up your meta nodes, please visit
-[Installing meta nodes](/enterprise_influxdb/v1.9/install-and-deploy/installation/meta_node_installation/).
+[Installing meta nodes](/enterprise_influxdb/v1.9/introduction/installation/installation/meta_node_installation/).
 Bad things can happen if you complete the following steps without meta nodes.
 {{% /warn %}}
 
@@ -316,7 +316,7 @@ Once your data nodes are part of your cluster, do the following:
 - Set up [authentication](/enterprise_influxdb/v1.9/administration/configure/security/authentication/).
   Once you cluster is configured for authentication,
   if you want to add more users in addition to admin user,
-  see [Manage users and permissions](/enterprise_influxdb/v1.9/administration/manage/security/).
+  see [Manage users and permissions](/enterprise_influxdb/v1.9/administration/manage/users-and-permissions/).
 - [Enable TLS](/enterprise_influxdb/v1.9/guides/enable-tls/).
-- [Set up Chronograf](/enterprise_influxdb/v1.9/install-and-deploy/installation/chrono_install)
+- [Set up Chronograf](/enterprise_influxdb/v1.9/introduction/installation/installation/chrono_install)
   for UI visualization, dashboards, and management.
diff --git a/content/enterprise_influxdb/v1.9/introduction/install-and-deploy/installation/meta_node_installation.md b/content/enterprise_influxdb/v1.9/introduction/installation/meta_node_installation.md
similarity index 97%
rename from content/enterprise_influxdb/v1.9/introduction/install-and-deploy/installation/meta_node_installation.md
rename to content/enterprise_influxdb/v1.9/introduction/installation/meta_node_installation.md
index 2affd5c2c..bd5362a12 100644
--- a/content/enterprise_influxdb/v1.9/introduction/install-and-deploy/installation/meta_node_installation.md
+++ b/content/enterprise_influxdb/v1.9/introduction/installation/meta_node_installation.md
@@ -2,12 +2,12 @@
 title: Install InfluxDB Enterprise meta nodes
 aliases:
     - /enterprise_influxdb/v1.9/installation/meta_node_installation/
-    - /enterprise_influxdb/v1.9/install-and-deploy/installation/meta_node_installation/
+    - /enterprise_influxdb/v1.9/introduction/installation/installation/meta_node_installation/
 menu:
   enterprise_influxdb_1_9:
     name: Install meta nodes
     weight: 10
-    parent: Install in your environment
+    parent: Install
 ---
 
 InfluxDB Enterprise offers highly scalable clusters on your infrastructure
@@ -257,4 +257,4 @@ Note that your cluster must have at least three meta nodes.
 If you do not see your meta nodes in the output, retry adding them to
 the cluster.
 
-After your meta nodes are part of your cluster, [install data nodes](/enterprise_influxdb/v1.9/install-and-deploy/installation/data_node_installation/).
+After your meta nodes are part of your cluster, [install data nodes](/enterprise_influxdb/v1.9/introduction/installation/installation/data_node_installation/).
diff --git a/content/enterprise_influxdb/v1.9/introduction/installation_requirements.md b/content/enterprise_influxdb/v1.9/introduction/installation_requirements.md
index d94c8a71d..8a26c0dab 100644
--- a/content/enterprise_influxdb/v1.9/introduction/installation_requirements.md
+++ b/content/enterprise_influxdb/v1.9/introduction/installation_requirements.md
@@ -12,7 +12,7 @@ menu:
     parent: Introduction
 ---
 
-Review the installation requirements below, and then check out available options to [install and deploy InfluxDB Enterprise](/enterprise_influxdb/v1.9/install-and-deploy/). For an overview of the architecture and concepts in an InfluxDB Enterprise cluster, review [Clustering in InfluxDB Enterprise](/enterprise_influxdb/v1.9/concepts/clustering/).
+Review the installation requirements below, and then check out available options to [install and deploy InfluxDB Enterprise](/enterprise_influxdb/v1.9/introduction/installation/). For an overview of the architecture and concepts in an InfluxDB Enterprise cluster, review [Clustering in InfluxDB Enterprise](/enterprise_influxdb/v1.9/concepts/clustering/).
 
 ## Requirements for InfluxDB Enterprise clusters
 
diff --git a/content/enterprise_influxdb/v1.9/query_language/explore-schema.md b/content/enterprise_influxdb/v1.9/query_language/explore-schema.md
index 0e37f47ac..5ec905aab 100644
--- a/content/enterprise_influxdb/v1.9/query_language/explore-schema.md
+++ b/content/enterprise_influxdb/v1.9/query_language/explore-schema.md
@@ -188,6 +188,8 @@ SHOW SERIES [ON <database_name>] [FROM_clause] [WHERE <tag_key> <operator> [ '<t
 If the query does not include `ON <database_name>`, you must specify the
 database with `USE <database_name>` in the [CLI](/enterprise_influxdb/v1.9/tools/influx-cli/use-influx/) or with the `db` query
 string parameter in the [InfluxDB API](/enterprise_influxdb/v1.9/tools/api/#query-string-parameters) request.
+`SHOW SERIES` only returns series in the database's default retention policy,
+and fails if there is no default retention policy.
 
 The `FROM`, `WHERE`, `LIMIT`, and `OFFSET` clauses are optional.
 The `WHERE` clause supports tag comparisons; field comparisons are not
@@ -211,7 +213,7 @@ and on [Regular Expressions in Queries](/enterprise_influxdb/v1.9/query_language
 #### Run a `SHOW SERIES` query with the `ON` clause
 
 ```sql
-// Returns series for all shards in the database
+// Returns series for all shards in the database and default retention policy
 > SHOW SERIES ON NOAA_water_database
 
 key
diff --git a/content/enterprise_influxdb/v1.9/query_language/manage-database.md b/content/enterprise_influxdb/v1.9/query_language/manage-database.md
index ad52cf8d1..6b9c22ab0 100644
--- a/content/enterprise_influxdb/v1.9/query_language/manage-database.md
+++ b/content/enterprise_influxdb/v1.9/query_language/manage-database.md
@@ -87,7 +87,7 @@ If you attempt to create a database that already exists, InfluxDB does nothing a
 ```
 
 The query creates a database called `NOAA_water_database`.
-[By default](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes/#retention-autocreate--true), InfluxDB also creates the `autogen` retention policy and associates it with the `NOAA_water_database`.
+[By default](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes/#retention-autocreate), InfluxDB also creates the `autogen` retention policy and associates it with the `NOAA_water_database`.
 
 ##### Create a database with a specific retention policy
 
@@ -229,7 +229,7 @@ exist.
 
 The following sections cover how to create, alter, and delete retention policies.
 Note that when you create a database, InfluxDB automatically creates a retention policy named `autogen` which has infinite retention.
-You may disable its auto-creation in the [configuration file](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes/#retention-autocreate--true).
+You may disable its auto-creation in the [configuration file](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes/#retention-autocreate).
 
 ### Create retention policies with CREATE RETENTION POLICY
 
diff --git a/content/enterprise_influxdb/v1.9/query_language/spec.md b/content/enterprise_influxdb/v1.9/query_language/spec.md
index 4b1608854..85935c4eb 100644
--- a/content/enterprise_influxdb/v1.9/query_language/spec.md
+++ b/content/enterprise_influxdb/v1.9/query_language/spec.md
@@ -988,8 +988,7 @@ Estimates or counts exactly the cardinality of the series for the current databa
 
 [Series cardinality](/enterprise_influxdb/v1.9/concepts/glossary/#series-cardinality) is the major factor that affects RAM requirements. For more information, see:
 
--<!-- [When do I need more RAM?](/enterprise_influxdb/v1.9/reference/hardware_sizing/#when-do-i-need-more-ram) in [Hardware Sizing Guidelines](/enterprise_influxdb/v1.9/reference/hardware_sizing/) -->
-
+- [When do I need more RAM?](/enterprise_influxdb/v1.9/guides/hardware_sizing/#when-do-i-need-more-ram) in [Hardware Sizing Guidelines](/enterprise_influxdb/v1.9/guides/hardware_sizing/)
 - [Don't have too many series](/enterprise_influxdb/v1.9/concepts/schema_and_data_layout/#avoid-too-many-series)
 
 > **Note:** `ON <database>`, `FROM <sources>`, `WITH KEY = <key>`, `WHERE <condition>`, `GROUP BY <dimensions>`, and `LIMIT/OFFSET` clauses are optional.
@@ -1037,8 +1036,24 @@ show_shards_stmt = "SHOW SHARDS" .
 
 ```sql
 SHOW SHARDS
+
+name: telegraf
+id  database   retention_policy shard_group start_time           end_time             expiry_time          owners
+--  --------   ---------------- ----------- ----------           --------             -----------          ------
+16  telegraf   autogen          6           2020-10-19T00:00:00Z 2020-10-26T00:00:00Z 2020-10-26T00:00:00Z 6,7,8
+17  telegraf   autogen          6           2020-10-19T00:00:00Z 2020-10-26T00:00:00Z 2020-10-26T00:00:00Z 9,4,5
+21  telegraf   autogen          8           2020-10-26T00:00:00Z 2020-11-02T00:00:00Z 2020-11-02T00:00:00Z 8,9,4
+22  telegraf   autogen          8           2020-10-26T00:00:00Z 2020-11-02T00:00:00Z 2020-11-02T00:00:00Z 5,6,7
+26  telegraf   autogen          10          2020-11-02T00:00:00Z 2020-11-09T00:00:00Z 2020-11-09T00:00:00Z 9,4,5
+27  telegraf   autogen          10          2020-11-02T00:00:00Z 2020-11-09T00:00:00Z 2020-11-09T00:00:00Z 6,7,8
+31  telegraf   autogen          12          2020-11-09T00:00:00Z 2020-11-16T00:00:00Z 2020-11-16T00:00:00Z 6,7,8
 ```
 
+`SHOW SHARDS` outputs the following data:
+- `id` column: Shard IDs that belong to the specified `database` and `retention policy`.
+- `shard_group` column: Group number that a shard belongs to. Shards in the same shard group have the same `start_time` and `end_time`. This interval indicates how long the shard is active, and the `expiry_time` columns shows when the shard group expires. No timestamps will show under `expiry_time` if the retention policy duration is set to infinite.
+- `owners` column: Shows the data nodes that own a shard. The number of nodes that own a shard is equal to the replication factor. In this example, the replication factor is 3, so 3 nodes own each shard.
+  
 ### SHOW STATS
 
 Returns detailed statistics on available components of an InfluxDB node and available (enabled) components.
diff --git a/content/enterprise_influxdb/v1.9/supported_protocols/prometheus.md b/content/enterprise_influxdb/v1.9/supported_protocols/prometheus.md
index 668def969..cb1dd915c 100644
--- a/content/enterprise_influxdb/v1.9/supported_protocols/prometheus.md
+++ b/content/enterprise_influxdb/v1.9/supported_protocols/prometheus.md
@@ -89,7 +89,7 @@ made to match the InfluxDB data structure:
 * Prometheus labels become InfluxDB tags.
 * All `# HELP` and `# TYPE` lines are ignored.
 * [v1.8.6 and later] Prometheus remote write endpoint drops unsupported Prometheus values (`NaN`,`-Inf`, and `+Inf`) rather than reject the entire batch.
-  * If [write trace logging is enabled (`[http] write-tracing = true`)](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes/#write-tracing--false), then summaries of dropped values are logged.
+  * If [write trace logging is enabled (`[http] write-tracing = true`)](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes/#write-tracing), then summaries of dropped values are logged.
   * If a batch of values contains values that are subsequently dropped, HTTP status code `204` is returned.
 
 ### Example: Parse Prometheus to InfluxDB
diff --git a/content/enterprise_influxdb/v1.9/tools/api.md b/content/enterprise_influxdb/v1.9/tools/api.md
index af3027f4a..b6eacf8fb 100644
--- a/content/enterprise_influxdb/v1.9/tools/api.md
+++ b/content/enterprise_influxdb/v1.9/tools/api.md
@@ -427,7 +427,7 @@ A successful [`CREATE DATABASE` query](/enterprise_influxdb/v1.9/query_language/
 | u=\<username> | Optional if you haven't [enabled authentication](/enterprise_influxdb/v1.9/administration/authentication_and_authorization/#set-up-authentication). Required if you've enabled authentication.* | Sets the username for authentication if you've enabled authentication. The user must have read access to the database. Use with the query string parameter `p`. |
 
 \* InfluxDB does not truncate the number of rows returned for requests without the `chunked` parameter.
-That behavior is configurable; see the [`max-row-limit`](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes/#max-row-limit--0)
+That behavior is configurable; see the [`max-row-limit`](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes/#max-row-limit)
 configuration option for more information.
 
 \** The InfluxDB API also supports basic authentication.
@@ -951,7 +951,7 @@ Errors are returned in JSON.
 | 400 Bad Request  | Unacceptable request. Can occur with an InfluxDB line protocol syntax error or if a user attempts to write values to a field that previously accepted a different value type. The returned JSON offers further information. |
 | 401 Unauthorized | Unacceptable request. Can occur with invalid authentication credentials.  |
 | 404 Not Found    | Unacceptable request. Can occur if a user attempts to write to a database that does not exist. The returned JSON offers further information. |
-| 413 Request Entity Too Large | Unaccetable request. It will occur if the payload of the POST request is bigger than the maximum size allowed. See [`max-body-size`](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes/#max-body-size--25000000) parameter for more details.
+| 413 Request Entity Too Large | Unaccetable request. It will occur if the payload of the POST request is bigger than the maximum size allowed. See [`max-body-size`](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes/#max-body-size) parameter for more details.
 | 500 Internal Server Error  | The system is overloaded or significantly impaired. Can occur if a user attempts to write to a retention policy that does not exist. The returned JSON offers further information. |
 
 #### Examples
diff --git a/content/enterprise_influxdb/v1.9/tools/grafana.md b/content/enterprise_influxdb/v1.9/tools/grafana.md
index c217c4434..3569d8c0b 100644
--- a/content/enterprise_influxdb/v1.9/tools/grafana.md
+++ b/content/enterprise_influxdb/v1.9/tools/grafana.md
@@ -23,7 +23,7 @@ to visualize data from your **InfluxDB Enterprise v1.8** instance.
   in your InfluxDB data node configuration file.
 {{% /note %}}
 
-1. [Set up an InfluxDB Enterprise cluster](/enterprise_influxdb/v1.9/install-and-deploy/).
+1. [Set up an InfluxDB Enterprise cluster](/enterprise_influxdb/v1.9/introduction/installation/).
 2. [Sign up for Grafana Cloud](https://grafana.com/products/cloud/) or
    [download and install Grafana](https://grafana.com/grafana/download).
 3. Visit your **Grafana Cloud user interface** (UI) or, if running Grafana locally,
diff --git a/content/enterprise_influxdb/v1.9/tools/influxd-ctl.md b/content/enterprise_influxdb/v1.9/tools/influxd-ctl.md
index ff09fecde..15ed1ce05 100644
--- a/content/enterprise_influxdb/v1.9/tools/influxd-ctl.md
+++ b/content/enterprise_influxdb/v1.9/tools/influxd-ctl.md
@@ -110,7 +110,9 @@ influxd-ctl -auth-type jwt -secret oatclusters show
 
 The `influxd-ctl` utility uses JWT authentication with the shared secret `oatclusters`.
 
-If authentication is enabled in the cluster's [meta node configuration files](/enterprise_influxdb/v1.9/administration/config-meta-nodes#auth-enabled-false) and [data node configuration files](/enterprise_influxdb/v1.9/administration/config-data-nodes#meta-auth-enabled-false) and the `influxd-ctl` command does not include authentication details, the system returns:
+If authentication is enabled in the cluster's [meta node configuration files](/enterprise_influxdb/v1.9/administration/configure/config-meta-nodes/#auth-enabled)
+and [data node configuration files](/enterprise_influxdb/v1.9/administration/config-data-nodes/#meta-auth-enabled)
+and the `influxd-ctl` command does not include authentication details, the system returns:
 
 ```bash
 Error: unable to parse authentication credentials.
@@ -132,7 +134,10 @@ In the following example, the `influxd-ctl` utility uses basic authentication fo
 influxd-ctl -auth-type basic -user admini -pwd mouse show
 ```
 
-If authentication is enabled in the cluster's [meta node configuration files](/enterprise_influxdb/v1.9/administration/config-meta-nodes#auth-enabled-false) and [data node configuration files](/enterprise_influxdb/v1.9/administration/config-data-nodes#meta-auth-enabled-false) and the `influxd-ctl` command does not include authentication details, the system returns:
+If authentication is enabled in the cluster's
+[meta node configuration files](/enterprise_influxdb/v1.9/administration/config-meta-nodes/#auth-enabled-false)
+and [data node configuration files](/enterprise_influxdb/v1.9/administration/configure/config-data-nodes/#meta-auth-enabled)
+and the `influxd-ctl` command does not include authentication details, the system returns:
 
 ```bash
 Error: unable to parse authentication credentials.
@@ -246,6 +251,20 @@ Optional arguments are in brackets.
 
 Name of the single database to back up.
 
+###### [ `-estimate` ]
+
+Provide estimated backup size and progress messages during backup.
+
+**Sample output:**
+
+```
+Backing up node backup_data_0_1:8088, db stress, rp autogen, shard 14
+Files: 8 / 9 Bytes: 189543424 / 231921095 Completed: 82% in 22s Estimated remaining: 3s
+Files: 8 / 9 Bytes: 189543424 / 231921095 Completed: 82% in 23s Estimated remaining: 2s
+Files: 9 / 9 Bytes: 231736320 / 231921095 Completed: 100% in 24s Estimated remaining: 447µs
+Done backing up node backup_data_0_1:8088, db stress, rp autogen, shard 14 in 67ms: 42192896 bytes transferred
+```
+
 ###### [ `-from <data-node-TCP-address>` ]
 
 TCP address of the target data node.
@@ -351,7 +370,10 @@ Copied shard 22 from cluster-data-node-01:8088 to cluster-data-node-02:8088
 
 ### `copy-shard-status`
 
-Shows all in-progress [copy shard](#copy-shard) operations, including the shard's source node, destination node, database, [retention policy](/enterprise_influxdb/v1.9/concepts/glossary/#retention-policy-rp), shard ID, total size, current size, and the operation's start time.
+Shows all in-progress [copy shard](#copy-shard) operations,
+including the shard's source node, destination node, database,
+[retention policy](/enterprise_influxdb/v1.9/concepts/glossary/#retention-policy-rp),
+shard ID, total size, current size, and the operation's start time.
 
 #### Syntax
 
@@ -935,6 +957,19 @@ To restore metadata, [restore a metadata backup](#restore-from-a-metadata-backup
 
 Show the contents of the backup.
 
+###### [ `-meta-only-overwrite-force` ]
+
+Restore *metadata only* from a backup.
+
+{{% warn %}}
+Only use this flag to restore from backups of the target cluster.
+If you use this flag with metadata from a different cluster, you will lose data
+(since metadata includes shard assignments to data nodes).
+
+See ["Back up and restore"](/enterprise_influxdb/v1.9/administration/backup-and-restore/#restore-overwrite-metadata-from-a-full-or-incremental-backup-to-fix-damaged-metadata)
+for instructions on using this flag.
+{{% /warn %}}
+
 ###### [ `-newdb <newdb_name>` ]
 
 Name of the new database to restore to.
diff --git a/content/enterprise_influxdb/v1.9/troubleshooting/frequently-asked-questions.md b/content/enterprise_influxdb/v1.9/troubleshooting/frequently-asked-questions.md
index a429ba366..6f1807971 100644
--- a/content/enterprise_influxdb/v1.9/troubleshooting/frequently-asked-questions.md
+++ b/content/enterprise_influxdb/v1.9/troubleshooting/frequently-asked-questions.md
@@ -89,6 +89,7 @@ Where applicable, it links to outstanding issues on GitHub.
 * [Why am I seeing `error writing count stats ...: partial write` errors in my data node logs?](#why-am-i-seeing-error-writing-count-stats--partial-write-errors-in-my-data-node-logs)
 * [Why am I seeing `queue is full` errors in my data node logs?](#why-am-i-seeing-queue-is-full-errors-in-my-data-node-logs)
 * [Why am I seeing `unable to determine if "hostname" is a meta node` when I try to add a meta node with `influxd-ctl join`?](#why-am-i-seeing-unable-to-determine-if-hostname-is-a-meta-node-when-i-try-to-add-a-meta-node-with-influxd-ctl-join)
+* [Why is InfluxDB reporting an out of memory (OOM) exception when my system has free memory?](#why-is-influxdb-reporting-an-out-of-memory-oom-exception-when-my-system-has-free-memory)
 
 ---
 
@@ -177,7 +178,7 @@ an RP every 30 minutes.
 You may need to wait for the next RP check for InfluxDB to drop data that are
 outside the RP's new `DURATION` setting.
 The 30 minute interval is
-[configurable](/enterprise_influxdb/v1.9/administration/config-data-nodes/#check-interval--30m0s).
+[configurable](/enterprise_influxdb/v1.9/administration/config-data-nodes/#check-interval).
 
 Second, altering both the `DURATION` and `SHARD DURATION` of an RP can result in
 unexpected data retention.
@@ -1282,7 +1283,7 @@ The `journalctl` output can be redirected to print the logs to a text file. With
 This is the expected behavior if you haven't joined the meta node to the
 cluster.
 The `503` errors should stop showing up in the logs once you
-[join the meta node to the cluster](/enterprise_influxdb/v1.9/install-and-deploy/installation/meta_node_installation/#step-3-join-the-meta-nodes-to-the-cluster).
+[join the meta node to the cluster](/enterprise_influxdb/v1.9/introduction/installation/installation/meta_node_installation/#step-3-join-the-meta-nodes-to-the-cluster).
 
 ## Why am I seeing a `409` error in some of my data node logs?
 
@@ -1333,3 +1334,35 @@ Meta nodes use the `/status` endpoint to determine the current state of another
 `"nodeType":"meta","leader":"","httpAddr":"<hostname>:8091","raftAddr":"<hostname>:8089","peers":null}`
 
 If you are getting an error message while attempting to `influxd-ctl join` a new meta node, it means that the JSON string returned from the `/status` endpoint is incorrect. This generally indicates that the meta node configuration file is incomplete or incorrect. Inspect the HTTP response with `curl -v "http://<hostname>:8091/status"` and make sure that the `hostname`, the `bind-address`, and the `http-bind-address` are correctly populated. Also check the `license-key` or `license-path` in the configuration file of the meta nodes. Finally, make sure that you specify the `http-bind-address` port in the join command, e.g. `influxd-ctl join hostname:8091`.
+
+## Why is InfluxDB reporting an out of memory (OOM) exception when my system has free memory?
+
+`mmap` is a Unix system call that maps files into memory.
+As the number of shards in an InfluxDB Enterprise cluster increases, the number of memory maps increase.
+If the number of maps exceeds the configured maximum limit, the node reports that it is out of memory.
+
+To check the current number of maps the `influxd` process is using:
+
+```sh
+# Get the influxd process ID (PID)
+PID=$(ps aux | awk '/influxd/ ${print 2}' 
+
+# Count the number of maps associated with the influxd process
+wc -l /proc/$PID/maps
+```
+
+The `max_map_count` file contains the maximum number of memory map areas a process may have.
+The default limit is `65536`.
+We recommend increasing this to `262144` (four times the default) by running the following:
+
+```sh
+echo vm.max_map_count=262144 > /etc/sysctl.d/90-vm.max_map_count.conf
+```
+
+To make the changes permanent:
+
+```sh
+sysctl --system
+```
+
+Restart the `influxd` process and repeat on each node in your cluster.
diff --git a/content/flux/v0.x/data-types/basic/bool.md b/content/flux/v0.x/data-types/basic/bool.md
index f008c6458..4f91e8473 100644
--- a/content/flux/v0.x/data-types/basic/bool.md
+++ b/content/flux/v0.x/data-types/basic/bool.md
@@ -71,7 +71,7 @@ and convert columns to booleans.
 
 ```js
 data
-  |> toBool()
+    |> toBool()
 ```
 
 {{< flex >}}
@@ -103,7 +103,7 @@ data
 
 ```js
 data
-  |> map(fn: (r) => ({ r with running: bool(v: r.running) }))
+    |> map(fn: (r) => ({ r with running: bool(v: r.running) }))
 ```
 
 {{< flex >}}
diff --git a/content/flux/v0.x/data-types/basic/bytes.md b/content/flux/v0.x/data-types/basic/bytes.md
index e77eb6c5a..13a91949f 100644
--- a/content/flux/v0.x/data-types/basic/bytes.md
+++ b/content/flux/v0.x/data-types/basic/bytes.md
@@ -21,6 +21,7 @@ A **bytes** type represents a sequence of byte values.
 
 - [Bytes syntax](#bytes-syntax)
 - [Convert a column to bytes](#convert-a-column-to-bytes)
+- [Include the string representation of bytes in a table](#include-the-string-representation-of-bytes-in-a-table)
 
 ## Bytes syntax
 Flux does not provide a bytes literal syntax.
@@ -49,3 +50,37 @@ import "contrib/bonitoo-io/hex"
 hex.bytes(v: "FF5733")
 // Returns [255 87 51] (bytes)
 ```
+
+## Include the string representation of bytes in a table
+
+Use [`display()`](/flux/v0.x/stdlib/universe/display/) to return the string
+representation of bytes and include it as a column value.
+`display()` represents bytes types as a string of lowercase hexadecimal
+characters prefixed with `0x`.
+
+```js
+import "sampledata"
+
+sampledata.string()
+    |> map(fn: (r) => ({r with _value: display(v: bytes(v: r._value))}))
+```
+
+#### Output
+
+| tag | _time                | _value <em style="opacity:.5">(string)</em> |
+| --- | :------------------- | ------------------------------------------: |
+| t1  | 2021-01-01T00:00:00Z |                    0x736d706c5f673971637a73 |
+| t1  | 2021-01-01T00:00:10Z |                    0x736d706c5f306d6776396e |
+| t1  | 2021-01-01T00:00:20Z |                    0x736d706c5f706877363634 |
+| t1  | 2021-01-01T00:00:30Z |                    0x736d706c5f6775767a7934 |
+| t1  | 2021-01-01T00:00:40Z |                    0x736d706c5f357633636365 |
+| t1  | 2021-01-01T00:00:50Z |                    0x736d706c5f7339666d6779 |
+
+| tag | _time                | _value <em style="opacity:.5">(string)</em> |
+| --- | :------------------- | ------------------------------------------: |
+| t2  | 2021-01-01T00:00:00Z |                    0x736d706c5f623565696461 |
+| t2  | 2021-01-01T00:00:10Z |                    0x736d706c5f6575346f7870 |
+| t2  | 2021-01-01T00:00:20Z |                    0x736d706c5f356737747a34 |
+| t2  | 2021-01-01T00:00:30Z |                    0x736d706c5f736f78317574 |
+| t2  | 2021-01-01T00:00:40Z |                    0x736d706c5f77666d373537 |
+| t2  | 2021-01-01T00:00:50Z |                    0x736d706c5f64746e326276 |
diff --git a/content/flux/v0.x/data-types/basic/duration.md b/content/flux/v0.x/data-types/basic/duration.md
index d0a9a80c2..9020fc9a5 100644
--- a/content/flux/v0.x/data-types/basic/duration.md
+++ b/content/flux/v0.x/data-types/basic/duration.md
@@ -59,6 +59,18 @@ Flux supports the following unit specifiers:
 3d12h4m25s // 3 days, 12 hours, 4 minutes, and 25 seconds
 ```
 
+{{% note %}}
+#### Do not include leading zeros in duration literals
+The integer part of a duration literal should not contain leading zeros.
+Leading zeros are parsed as separate integer literals.
+For example:
+
+```js
+01m // parsed as 0 (integer literal) and 1m (duration literal)
+02h05m // parsed as 0 (integer literal), 2h (duration literal), 0 (integer literal), and 5m (duration literal)
+```
+{{% /note %}}
+
 ## Convert data types to durations
 Use the [`duration()` function](/flux/v0.x/stdlib/universe/duration/) to convert
 the following [basic types](/flux/v0.x/data-types/basic/) to durations:
diff --git a/content/flux/v0.x/data-types/basic/float.md b/content/flux/v0.x/data-types/basic/float.md
index 6d9b1976c..71826dba4 100644
--- a/content/flux/v0.x/data-types/basic/float.md
+++ b/content/flux/v0.x/data-types/basic/float.md
@@ -115,7 +115,7 @@ and convert columns to floats.
 
 ```js
 data
-  |> toFloat()
+    |> toFloat()
 ```
 
 {{< flex >}}
@@ -147,7 +147,7 @@ data
 
 ```js
 data
-  |> map(fn: (r) => ({ r with index: float(v: r.index) }))
+    |> map(fn: (r) => ({ r with index: float(v: r.index) }))
 ```
 
 {{< flex >}}
diff --git a/content/flux/v0.x/data-types/basic/int.md b/content/flux/v0.x/data-types/basic/int.md
index 74f70c532..048d4ae8c 100644
--- a/content/flux/v0.x/data-types/basic/int.md
+++ b/content/flux/v0.x/data-types/basic/int.md
@@ -119,7 +119,7 @@ and convert columns to integers.
 
 ```js
 data
-  |> toInt()
+    |> toInt()
 ```
 
 {{< flex >}}
@@ -151,7 +151,7 @@ data
 
 ```js
 data
-  |> map(fn: (r) => ({ r with uid: int(v: r.uid) }))
+    |> map(fn: (r) => ({ r with uid: int(v: r.uid) }))
 ```
 
 {{< flex >}}
diff --git a/content/flux/v0.x/data-types/basic/null.md b/content/flux/v0.x/data-types/basic/null.md
index 2425d5fc3..e319a793b 100644
--- a/content/flux/v0.x/data-types/basic/null.md
+++ b/content/flux/v0.x/data-types/basic/null.md
@@ -37,7 +37,7 @@ if a column value is _null_.
 ##### Filter out rows with null values
 ```js
 data
-  |> filter(fn: (r) => exists r._value)
+    |> filter(fn: (r) => exists r._value)
 ```
 
 {{< flex >}}
diff --git a/content/flux/v0.x/data-types/basic/string.md b/content/flux/v0.x/data-types/basic/string.md
index 79a72fa34..687016891 100644
--- a/content/flux/v0.x/data-types/basic/string.md
+++ b/content/flux/v0.x/data-types/basic/string.md
@@ -111,7 +111,7 @@ use the [`toString()` function](/flux/v0.x/stdlib/universe/tostring/).
 
 ```js
 data
-  |> toString()
+    |> toString()
 ```
 
 {{< flex >}}
@@ -143,7 +143,7 @@ data
 
 ```js
 data
-  |> map(fn: (r) => ({ r with level: string(v: r.level) }))
+    |> map(fn: (r) => ({ r with level: string(v: r.level) }))
 ```
 {{< flex >}}
 {{% flex-content %}}
diff --git a/content/flux/v0.x/data-types/basic/time.md b/content/flux/v0.x/data-types/basic/time.md
index 58cf39642..1135de4bb 100644
--- a/content/flux/v0.x/data-types/basic/time.md
+++ b/content/flux/v0.x/data-types/basic/time.md
@@ -72,7 +72,7 @@ and convert columns to time.
 
 ```js
 data
-  |> toTime()
+    |> toTime()
 ```
 
 {{< flex >}}
@@ -104,7 +104,7 @@ data
 
 ```js
 data
-  |> map(fn: (r) => ({ r with epoch_ns: time(v: r.epoch_ns) }))
+    |> map(fn: (r) => ({ r with epoch_ns: time(v: r.epoch_ns) }))
 ```
 
 {{< flex >}}
@@ -171,7 +171,7 @@ date.truncate(t: t0, unit: 1mo)
 
 ```js
 data
-  |> truncateTimeColumn(unit: 1m)
+    |> truncateTimeColumn(unit: 1m)
 ```
 
 {{< flex >}}
diff --git a/content/flux/v0.x/data-types/basic/uint.md b/content/flux/v0.x/data-types/basic/uint.md
index 55970c4e1..adeaa22c4 100644
--- a/content/flux/v0.x/data-types/basic/uint.md
+++ b/content/flux/v0.x/data-types/basic/uint.md
@@ -117,7 +117,7 @@ and convert columns to uintegers.
 
 ```js
 data
-  |> toUInt()
+    |> toUInt()
 ```
 
 {{< flex >}}
@@ -149,7 +149,7 @@ data
 
 ```js
 data
-  |> map(fn: (r) => ({ r with uid: uint(v: r.uid) }))
+    |> map(fn: (r) => ({ r with uid: uint(v: r.uid) }))
 ```
 
 {{< flex >}}
diff --git a/content/flux/v0.x/data-types/composite/array.md b/content/flux/v0.x/data-types/composite/array.md
index adb5a1453..60f84223e 100644
--- a/content/flux/v0.x/data-types/composite/array.md
+++ b/content/flux/v0.x/data-types/composite/array.md
@@ -66,11 +66,35 @@ arr[2]
 - [Get the length of an array](#get-the-length-of-an-array)
 - [Create a stream of tables from an array](#create-a-stream-of-tables-from-an-array)
 - [Compare arrays](#compare-arrays)
+- [Filter an array](#filter-an-array)
+- [Merge two arrays](#merge-two-arrays)
+- [Return the string representation of an array](#return-the-string-representation-of-an-array)
+- [Include the string representation of an array in a table](#include-the-string-representation-of-an-array-in-a-table)
 
 ### Iterate over an array
-{{% note %}}
-Flux currently does not provide a way to iterate over an array.
-{{% /note %}}
+1. Import the [`experimental/array` package](/flux/v0.x/stdlib/experimental/array/).
+2. Use [`array.map`](/flux/v0.x/stdlib/experimental/array/map/) to iterate over
+   elements in an array, apply a function to each element, and then return a new
+   array.
+
+```js
+import "experimental/array"
+
+a = [
+    {fname: "John", lname: "Doe", age: 42},
+    {fname: "Jane", lname: "Doe", age: 40},
+    {fname: "Jacob", lname: "Dozer", age: 21},
+]
+
+a |> array.map(fn: (x) => ({statement: "${x.fname} ${x.lname} is ${x.age} years old."}))
+
+// Returns
+// [
+//     {statement: "John Doe is 42 years old."},
+//     {statement: "Jane Doe is 40 years old."},
+//     {statement: "Jacob Dozer is 21 years old."}
+// ]
+```
 
 ### Check if a value exists in an array
 Use the [`contains` function](/flux/v0.x/stdlib/universe/contains/) to check if
@@ -105,9 +129,9 @@ length(arr: names)
 import "array"
 
 arr = [
-  {fname: "John", lname: "Doe", age: "37"},
-  {fname: "Jane", lname: "Doe", age: "32"},
-  {fname: "Jack", lname: "Smith", age: "56"}
+    {fname: "John", lname: "Doe", age: "37"},
+    {fname: "Jane", lname: "Doe", age: "32"},
+    {fname: "Jack", lname: "Smith", age: "56"},
 ]
 
 array.from(rows: arr)
@@ -120,7 +144,6 @@ array.from(rows: arr)
 | Jane  | Doe   |  32 |
 | Jack  | Smith |  56 |
 
-
 ### Compare arrays
 Use the `==` [comparison operator](/flux/v0.x/spec/operators/#comparison-operators)
 to check if two arrays are equal.
@@ -132,4 +155,73 @@ Equality is based on values, their type, and order.
 
 [12300.0, 34500.0] == [float(v: "1.23e+04"), float(v: "3.45e+04")]
 // Returns true
-```
\ No newline at end of file
+```
+
+### Filter an array
+1. Import the [`experimental/array` package](/flux/v0.x/stdlib/experimental/array/).
+2. Use [`array.filter`](/flux/v0.x/stdlib/experimental/array/filter/) to iterate
+   over and evaluate elements in an array with a predicate function and then
+   return a new array with only elements that match the predicate.
+
+```js
+import "experimental/array"
+
+a = [1, 2, 3, 4, 5]
+
+a |> array.filter(fn: (x) => x >= 3)
+// Returns [3, 4, 5]
+```
+
+### Merge two arrays
+1. Import the [`experimental/array` package](/flux/v0.x/stdlib/experimental/array/).
+2. Use [`array.concat`](/flux/v0.x/stdlib/experimental/array/concat/) to merge 
+   two arrays.
+
+```js
+import "experimental/array"
+
+a = [1, 2, 3]
+b = [4, 5, 6]
+
+a |> array.concat(v: b)
+// Returns [1, 2, 3, 4, 5, 6]
+```
+
+### Return the string representation of an array
+Use [`display()`](/flux/v0.x/stdlib/universe/display/) to return Flux literal 
+representation of an array as a string.
+
+```js
+arr = [1, 2, 3]
+
+display(v: arr)
+
+// Returns "[1, 2, 3]"
+```
+
+### Include the string representation of an array in a table
+Use [`display()`](/flux/v0.x/stdlib/universe/display/) to return Flux literal
+representation of an array as a string and include it as a column value.
+
+```js
+import "sampledata"
+
+sampledata.string()
+    |> map(fn: (r) => ({_time: r._time, exampleArray: display(v: [r.tag, r._value])}))
+```
+
+#### Output
+| _time <em style="opacity:.5">(time)</em> | exampleArray <em style="opacity:.5">(string)</em> |
+| :--------------------------------------- | :----------------------------------------------- |
+| 2021-01-01T00:00:00Z                     | [t1, smpl_g9qczs]                                |
+| 2021-01-01T00:00:10Z                     | [t1, smpl_0mgv9n]                                |
+| 2021-01-01T00:00:20Z                     | [t1, smpl_phw664]                                |
+| 2021-01-01T00:00:30Z                     | [t1, smpl_guvzy4]                                |
+| 2021-01-01T00:00:40Z                     | [t1, smpl_5v3cce]                                |
+| 2021-01-01T00:00:50Z                     | [t1, smpl_s9fmgy]                                |
+| 2021-01-01T00:00:00Z                     | [t2, smpl_b5eida]                                |
+| 2021-01-01T00:00:10Z                     | [t2, smpl_eu4oxp]                                |
+| 2021-01-01T00:00:20Z                     | [t2, smpl_5g7tz4]                                |
+| 2021-01-01T00:00:30Z                     | [t2, smpl_sox1ut]                                |
+| 2021-01-01T00:00:40Z                     | [t2, smpl_wfm757]                                |
+| 2021-01-01T00:00:50Z                     | [t2, smpl_dtn2bv]                                |
diff --git a/content/flux/v0.x/data-types/composite/dict.md b/content/flux/v0.x/data-types/composite/dict.md
index 28269d63e..09367932a 100644
--- a/content/flux/v0.x/data-types/composite/dict.md
+++ b/content/flux/v0.x/data-types/composite/dict.md
@@ -62,11 +62,12 @@ To reference values in a dictionary:
 ```js
 import "dict"
 
-positions = [
-  "Manager": "Jane Doe",
-  "Asst. Manager": "Jack Smith",
-  "Clerk": "John Doe"
-]
+positions =
+    [
+        "Manager": "Jane Doe",
+        "Asst. Manager": "Jack Smith",
+        "Clerk": "John Doe",
+    ]
 
 dict.get(dict: positions, key: "Manager", default: "Unknown position")
 // Returns Jane Doe
@@ -80,6 +81,8 @@ dict.get(dict: positions, key: "Teller", default: "Unknown position")
 - [Create a dictionary from a list](#create-a-dictionary-from-a-list)
 - [Insert a key-value pair into a dictionary](#insert-a-key-value-pair-into-a-dictionary)
 - [Remove a key-value pair from a dictionary](#remove-a-key-value-pair-from-a-dictionary)
+- [Return the string representation of a dictionary](#return-the-string-representation-of-a-dictionary)
+- [Include the string representation of a dictionary in a table](#include-the-string-representation-of-a-dictionary-in-a-table)
 
 ### Create a dictionary from a list
 1. Import the [`dict` package](/flux/v0.x/stdlib/dict/).
@@ -90,10 +93,7 @@ dict.get(dict: positions, key: "Teller", default: "Unknown position")
 ```js
 import "dict"
 
-list = [
-  {key: "k1", value: "v1"},
-  {key: "k2", value: "v2"}
-]
+list = [{key: "k1", value: "v1"}, {key: "k2", value: "v2"}]
 
 dict.fromList(pairs: list)
 // Returns [k1: v1, k2: v2]
@@ -109,11 +109,7 @@ import "dict"
 
 exampleDict = ["k1": "v1", "k2": "v2"]
 
-dict.insert(
-  dict: exampleDict,
-  key: "k3",
-  value: "v3"
-)
+dict.insert(dict: exampleDict, key: "k3", value: "v3")
 // Returns [k1: v1, k2: v2, k3: v3]
 ```
 
@@ -127,9 +123,46 @@ import "dict"
 
 exampleDict = ["k1": "v1", "k2": "v2"]
 
-dict.remove(
-  dict: exampleDict,
-  key: "k2"
-)
+dict.remove(dict: exampleDict, key: "k2")
 // Returns [k1: v1]
 ```
+
+### Return the string representation of a dictionary
+Use [`display()`](/flux/v0.x/stdlib/universe/display/) to return Flux literal
+representation of a dictionary as a string.
+
+```js
+x = ["a": 1, "b": 2, "c": 3]
+
+display(v: x)
+
+// Returns "[a: 1, b: 2, c: 3]"
+```
+
+### Include the string representation of a dictionary in a table
+Use [`display()`](/flux/v0.x/stdlib/universe/display/) to return Flux literal
+representation of a dictionary as a string and include it as a column value.
+
+```js
+import "sampledata"
+
+sampledata.string()
+    |> map(fn: (r) => ({_time: r._time, exampleDict: display(v: ["tag": r.tag, "value":r._value])}))
+```
+
+#### Output
+
+| \_time <em style="opacity:.5">(time)</em> | exampleDict <em style="opacity:.5">(string)</em> |
+| :---------------------------------------- | :----------------------------------------------- |
+| 2021-01-01T00:00:00Z                      | [tag: t1, value: smpl_g9qczs]                    |
+| 2021-01-01T00:00:10Z                      | [tag: t1, value: smpl_0mgv9n]                    |
+| 2021-01-01T00:00:20Z                      | [tag: t1, value: smpl_phw664]                    |
+| 2021-01-01T00:00:30Z                      | [tag: t1, value: smpl_guvzy4]                    |
+| 2021-01-01T00:00:40Z                      | [tag: t1, value: smpl_5v3cce]                    |
+| 2021-01-01T00:00:50Z                      | [tag: t1, value: smpl_s9fmgy]                    |
+| 2021-01-01T00:00:00Z                      | [tag: t2, value: smpl_b5eida]                    |
+| 2021-01-01T00:00:10Z                      | [tag: t2, value: smpl_eu4oxp]                    |
+| 2021-01-01T00:00:20Z                      | [tag: t2, value: smpl_5g7tz4]                    |
+| 2021-01-01T00:00:30Z                      | [tag: t2, value: smpl_sox1ut]                    |
+| 2021-01-01T00:00:40Z                      | [tag: t2, value: smpl_wfm757]                    |
+| 2021-01-01T00:00:50Z                      | [tag: t2, value: smpl_dtn2bv]                    |
diff --git a/content/flux/v0.x/data-types/composite/function.md b/content/flux/v0.x/data-types/composite/function.md
index c06ade7c9..171075af2 100644
--- a/content/flux/v0.x/data-types/composite/function.md
+++ b/content/flux/v0.x/data-types/composite/function.md
@@ -63,6 +63,3 @@ A Flux **function** literal contains the following:
 
 ## Define functions
 _For information about defining custom functions, see [Define custom functions](/flux/v0.x/define-functions/)._
-
-
-
diff --git a/content/flux/v0.x/data-types/composite/record.md b/content/flux/v0.x/data-types/composite/record.md
index 3b7767533..9e02b96dd 100644
--- a/content/flux/v0.x/data-types/composite/record.md
+++ b/content/flux/v0.x/data-types/composite/record.md
@@ -58,11 +58,7 @@ and specify the key to reference.
 Specify the record to access followed by a period (`.`) and the property key.
 
 ```js
-c = {
-  name: "John Doe",
-  address: "123 Main St.",
-  id: 1123445
-}
+c = {name: "John Doe", address: "123 Main St.", id: 1123445}
 
 c.name
 // Returns John Doe
@@ -80,11 +76,7 @@ Use bracket notation to access keys with special or whitespace characters.
 {{% /note %}}
 
 ```js
-c = {
-  "Company Name": "ACME",
-  "Street Address": "123 Main St.",
-  id: 1123445
-}
+c = {"Company Name": "ACME", "Street Address": "123 Main St.", id: 1123445}
 
 c["Company Name"]
 // Returns ACME
@@ -97,14 +89,15 @@ c["id"]
 To reference nested records, use chained dot or bracket notation for each nested level.
 
 ```js
-customer = {
-  name: "John Doe",
-  address: {
-    street: "123 Main St.",
-    city: "Pleasantville",
-    state: "New York"
-  }
-}
+customer = 
+    {
+        name: "John Doe",
+        address: {
+            street: "123 Main St.",
+            city: "Pleasantville",
+            state: "New York"
+        }
+    }
 
 customer.address.street
 // Returns 123 Main St.
@@ -136,6 +129,8 @@ _To dynamically reference keys in a composite type, consider using a
 - [Extend a record](#extend-a-record)
 - [List keys in a record](#list-keys-in-a-record)
 - [Compare records](#compare-records)
+- [Return the string representation of a record](#return-the-string-representation-of-a-record)
+- [Include the string representation of a record in a table](#include-the-string-representation-of-a-record-in-a-table)
 
 ### Extend a record
 Use the **`with` operator** to extend a record.
@@ -143,10 +138,7 @@ The `with` operator overwrites record properties if the specified keys exists or
 adds the new properties if the keys do not exist.
 
 ```js
-c = {
-  name: "John Doe",
-  id: 1123445
-}
+c = {name: "John Doe", id: 1123445}
 
 {c with spouse: "Jane Doe", pet: "Spot"}
 // Returns {id: 1123445, name: John Doe, pet: Spot, spouse: Jane Doe}
@@ -160,10 +152,7 @@ c = {
 ```js
 import "experimental"
 
-c = {
-  name: "John Doe",
-  id: 1123445
-}
+c = {name: "John Doe", id: 1123445}
 
 experimental.objectKeys(o: c)
 // Returns [name, id]
@@ -181,3 +170,43 @@ Equality is based on keys, their values, and types.
 {foo: 12300.0, bar: 34500.0} == {bar: float(v: "3.45e+04"), foo: float(v: "1.23e+04")}
 // Returns true
 ```
+
+### Return the string representation of a record
+Use [`display()`](/flux/v0.x/stdlib/universe/display/) to return the Flux literal
+representation of a record as a string.
+
+```js
+x = {a: 1, b: 2, c: 3}
+
+display(v: x)
+
+// Returns "{a: 1, b: 2, c: 3}"
+```
+
+### Include the string representation of a record in a table
+Use [`display()`](/flux/v0.x/stdlib/universe/display/) to return the Flux literal
+representation of a record as a string and include it as a column value.
+
+```js
+import "sampledata"
+
+sampledata.string()
+    |> map(fn: (r) => ({_time: r._time, exampleRecord: display(v: {tag: r.tag, value:r._value})}))
+```
+
+#### Output
+
+| \_time <em style="opacity:.5">(time)</em> | exampleRecord <em style="opacity:.5">(string)</em> |
+| :---------------------------------------- | :----------------------------------------------- |
+| 2021-01-01T00:00:00Z                      | {tag: t1, value: smpl_g9qczs}                    |
+| 2021-01-01T00:00:10Z                      | {tag: t1, value: smpl_0mgv9n}                    |
+| 2021-01-01T00:00:20Z                      | {tag: t1, value: smpl_phw664}                    |
+| 2021-01-01T00:00:30Z                      | {tag: t1, value: smpl_guvzy4}                    |
+| 2021-01-01T00:00:40Z                      | {tag: t1, value: smpl_5v3cce}                    |
+| 2021-01-01T00:00:50Z                      | {tag: t1, value: smpl_s9fmgy}                    |
+| 2021-01-01T00:00:00Z                      | {tag: t2, value: smpl_b5eida}                    |
+| 2021-01-01T00:00:10Z                      | {tag: t2, value: smpl_eu4oxp}                    |
+| 2021-01-01T00:00:20Z                      | {tag: t2, value: smpl_5g7tz4}                    |
+| 2021-01-01T00:00:30Z                      | {tag: t2, value: smpl_sox1ut}                    |
+| 2021-01-01T00:00:40Z                      | {tag: t2, value: smpl_wfm757}                    |
+| 2021-01-01T00:00:50Z                      | {tag: t2, value: smpl_dtn2bv}                    |
diff --git a/content/flux/v0.x/data-types/regexp.md b/content/flux/v0.x/data-types/regexp.md
index 95b77ba92..8bf4ce0ea 100644
--- a/content/flux/v0.x/data-types/regexp.md
+++ b/content/flux/v0.x/data-types/regexp.md
@@ -100,11 +100,7 @@ regexp.compile(v: "^- [a-z0-9]{7}")
 ```js
 import "regexp"
 
-regexp.replaceAllString(
-  r: /a(x*)b/,
-  v: "-ab-axxb-",
-  t: "T"
-)
+regexp.replaceAllString(r: /a(x*)b/, v: "-ab-axxb-", t: "T")
 // Returns "-T-T-"
 ```
 
@@ -120,10 +116,7 @@ regexp.replaceAllString(
 ```js
 import "regexp"
 
-regexp.findString(
-  r: /foo.?/,
-  v: "seafood fool"
-)
+regexp.findString(r: /foo.?/, v: "seafood fool")
 // Returns "food"
 ```
 
diff --git a/content/flux/v0.x/define-functions.md b/content/flux/v0.x/define-functions.md
index 438c445d8..1e082710a 100644
--- a/content/flux/v0.x/define-functions.md
+++ b/content/flux/v0.x/define-functions.md
@@ -107,14 +107,14 @@ each row, modify the `_value`, and then return the updated row.
 ##### Function definition
 ```js
 multByX = (tables=<-, x) =>
-  tables
-    |> map(fn: (r) => ({ r with _value: r._value * x }))
+    tables
+        |> map(fn: (r) => ({r with _value: r._value * x}))
 ```
 
 ##### Example usage 
 ```js
 data
-  |> multByX(x: 2.0)
+    |> multByX(x: 2.0)
 ```
 
 {{< flex >}}
@@ -162,20 +162,22 @@ the updated row with a new `speed` column.
 ##### Function definition
 ```js
 speed = (tables=<-, unit="m") =>
-  tables
-    |> map(fn: (r) => {
-      elapsedHours = float(v: int(v: duration(v: r.elapsed))) / float(v: int(v: 1h))
-      distance = float(v: r.distance)
-      speed = distance / elapsedHours
-      
-      return { r with speed: "${speed} ${unit}ph" }
-    })
+    tables
+        |> map(
+            fn: (r) => {
+                elapsedHours = float(v: int(v: duration(v: r.elapsed))) / float(v: int(v: 1h))
+                distance = float(v: r.distance)
+                speed = distance / elapsedHours
+
+                return {r with speed: "${speed} ${unit}ph"}
+            },
+        )
 ```
 
 ##### Example usage
 ```js
 data
-  |> speed()
+    |> speed()
 ```
 
 {{< flex >}}
@@ -212,9 +214,9 @@ To create custom functions with variables scoped to the function,
 
 ```js
 functionName = (param) => {
-  exampleVar = "foo"
+    exampleVar = "foo"
 
-  return exampleVar
+    return exampleVar
 }
 ```
 
@@ -229,12 +231,17 @@ a numeric input value:
 
 ```js
 alertLevel = (v) => {
-  level = if float(v:v) >= 90.0 then "crit"
-          else if float(v:v) >= 80.0 then "warn"
-          else if float(v:v) >= 65.0 then "info"
-          else "ok"
-  
-  return level
+    level =
+        if float(v: v) >= 90.0 then
+            "crit"
+        else if float(v: v) >= 80.0 then
+            "warn"
+        else if float(v: v) >= 65.0 then
+            "info"
+        else
+            "ok"
+
+    return level
 }
 
 alertLevel(v: 87.3)
@@ -252,27 +259,30 @@ to create a dictionary of HEX codes and their corresponding names.
 import "dict"
 
 hexName = (hex) => {
-  hexNames = dict.fromList(pairs: [
-    {key: "#00ffff", value: "Aqua"},
-    {key: "#000000", value: "Black"},
-    {key: "#0000ff", value: "Blue"},
-    {key: "#ff00ff", value: "Fuchsia"},
-    {key: "#808080", value: "Gray"},
-    {key: "#008000", value: "Green"},
-    {key: "#00ff00", value: "Lime"},
-    {key: "#800000", value: "Maroon"},
-    {key: "#000080", value: "Navy"},
-    {key: "#808000", value: "Olive"},
-    {key: "#800080", value: "Purple"},
-    {key: "#ff0000", value: "Red"},
-    {key: "#c0c0c0", value: "Silver"},
-    {key: "#008080", value: "Teal"},
-    {key: "#ffffff", value: "White"},
-    {key: "#ffff00", value: "Yellow"},
-  ])  
-  name = dict.get(dict: hexNames, key: hex, default: "No known name")
-  
-  return name
+    hexNames =
+        dict.fromList(
+            pairs: [
+                {key: "#00ffff", value: "Aqua"},
+                {key: "#000000", value: "Black"},
+                {key: "#0000ff", value: "Blue"},
+                {key: "#ff00ff", value: "Fuchsia"},
+                {key: "#808080", value: "Gray"},
+                {key: "#008000", value: "Green"},
+                {key: "#00ff00", value: "Lime"},
+                {key: "#800000", value: "Maroon"},
+                {key: "#000080", value: "Navy"},
+                {key: "#808000", value: "Olive"},
+                {key: "#800080", value: "Purple"},
+                {key: "#ff0000", value: "Red"},
+                {key: "#c0c0c0", value: "Silver"},
+                {key: "#008080", value: "Teal"},
+                {key: "#ffffff", value: "White"},
+                {key: "#ffff00", value: "Yellow"},
+            ],
+        )
+    name = dict.get(dict: hexNames, key: hex, default: "No known name")
+
+    return name
 }
 
 hexName(hex: "#000000")
diff --git a/content/flux/v0.x/get-started/_index.md b/content/flux/v0.x/get-started/_index.md
index a74165c95..5d32d96e3 100644
--- a/content/flux/v0.x/get-started/_index.md
+++ b/content/flux/v0.x/get-started/_index.md
@@ -39,10 +39,10 @@ To see how to retrieve data from a source, select the data source: InfluxDB, CSV
 {{% code-tab-content %}}
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -1d)
-  |> filter(fn: (r) => r._measurement == "example-measurement")
-  |> mean()
-  |> yield(name: "_results")
+    |> range(start: -1d)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> mean()
+    |> yield(name: "_results")
 ```
 {{% /code-tab-content %}}
 {{% code-tab-content %}}
@@ -50,10 +50,10 @@ from(bucket: "example-bucket")
 import "csv"
 
 csv.from(file: "path/to/example/data.csv")
-  |> range(start: -1d)
-  |> filter(fn: (r) => r._measurement == "example-measurement")
-  |> mean()
-  |> yield(name: "_results")
+    |> range(start: -1d)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> mean()
+    |> yield(name: "_results")
 ```
 {{% /code-tab-content %}}
 {{% code-tab-content %}}
@@ -63,11 +63,11 @@ import "sql"
 sql.from(
     driverName: "postgres",
     dataSourceName: "postgresql://user:password@localhost",
-    query:"SELECT * FROM TestTable"
-  )
-  |> filter(fn: (r) => r.UserID == "123ABC456DEF")
-  |> mean(column: "purchase_total")
-  |> yield(name: "_results")
+    query: "SELECT * FROM TestTable",
+)
+    |> filter(fn: (r) => r.UserID == "123ABC456DEF")
+    |> mean(column: "purchase_total")
+    |> yield(name: "_results")
 ```
 {{% /code-tab-content %}}
 {{< /code-tabs-wrapper >}}
diff --git a/content/flux/v0.x/get-started/data-model.md b/content/flux/v0.x/get-started/data-model.md
index 2b23d642a..a528b047e 100644
--- a/content/flux/v0.x/get-started/data-model.md
+++ b/content/flux/v0.x/get-started/data-model.md
@@ -89,7 +89,7 @@ to modify group keys in a stream of tables.
 
 ```js
 data
-  |> group(columns: ["foo", "bar"], mode: "by")
+    |> group(columns: ["foo", "bar"], mode: "by")
 ```
 
 ### Table grouping example
diff --git a/content/flux/v0.x/get-started/query-basics.md b/content/flux/v0.x/get-started/query-basics.md
index 2cd1aabb1..48c256775 100644
--- a/content/flux/v0.x/get-started/query-basics.md
+++ b/content/flux/v0.x/get-started/query-basics.md
@@ -27,11 +27,11 @@ The majority of basic Flux queries include the following steps:
 - [Process](#process)
 
 ```js
-from(bucket: "example-bucket")            // ── Source
-  |> range(start: -1d)                    // ── Filter on time
-  |> filter(fn: (r) => r._field == "foo") // ── Filter on column values
-  |> group(columns: ["sensorID"])         // ── Shape
-  |> mean()                               // ── Process
+from(bucket: "example-bucket")              // ── Source
+    |> range(start: -1d)                    // ── Filter on time
+    |> filter(fn: (r) => r._field == "foo") // ── Filter on column values
+    |> group(columns: ["sensorID"])         // ── Shape
+    |> mean()                               // ── Process
 ```
 
 ### Source
@@ -135,7 +135,7 @@ To actually query data from InfluxDB, replace `sample.data()` with the
     import "influxdata/influxdb/sample"
 
     sample.data(set: "airSensor")
-      |> range(start: -1h)
+        |> range(start: -1h)
     ```
 
 3.  Use [`filter()`](/flux/v0.x/stdlib/universe/filter/) to filter rows based on
@@ -147,8 +147,8 @@ To actually query data from InfluxDB, replace `sample.data()` with the
     import "influxdata/influxdb/sample"
 
     sample.data(set: "airSensor")
-      |> range(start: -1h)
-      |> filter(fn: (r) => r._field == "co")
+        |> range(start: -1h)
+        |> filter(fn: (r) => r._field == "co")
     ```
 
 4.  Use [`mean()`](/flux/v0.x/stdlib/universe/mean/) to calculate the average value
@@ -161,9 +161,9 @@ To actually query data from InfluxDB, replace `sample.data()` with the
     import "influxdata/influxdb/sample"
 
     sample.data(set: "airSensor")
-      |> range(start: -1h)
-      |> filter(fn: (r) => r._field == "co")
-      |> mean()
+        |> range(start: -1h)
+        |> filter(fn: (r) => r._field == "co")
+        |> mean()
     ```
 
 5.  Use [`group()`](/flux/v0.x/stdlib/universe/group) to [restructure tables](/flux/v0.x/get-started/data-model/#restructure-tables)
@@ -173,10 +173,10 @@ To actually query data from InfluxDB, replace `sample.data()` with the
     import "influxdata/influxdb/sample"
 
     sample.data(set: "airSensor")
-      |> range(start: -1h)
-      |> filter(fn: (r) => r._field == "co")
-      |> mean()
-      |> group()
+        |> range(start: -1h)
+        |> filter(fn: (r) => r._field == "co")
+        |> mean()
+        |> group()
     ```
 
 Results from this basic query should be similar to the following:
diff --git a/content/flux/v0.x/get-started/syntax-basics.md b/content/flux/v0.x/get-started/syntax-basics.md
index e3e5c595c..8f4b59d3b 100644
--- a/content/flux/v0.x/get-started/syntax-basics.md
+++ b/content/flux/v0.x/get-started/syntax-basics.md
@@ -28,6 +28,7 @@ This guide walks through how Flux handles a few simple expressions.
     - [Dictionaries](#dictionaries)
     - [Functions](#functions)
   - [Regular expression types](#regular-expression-types)
+  - [View the string representation of any Flux type](#view-the-string-representation-of-any-flux-type)
 - [Packages](#packages)
 - [Examples of basic syntax](#examples-of-basic-syntax)
   - [Define data stream variables](#define-data-stream-variables)
@@ -149,6 +150,7 @@ The following basic types do not have a literal syntax, but can be created in ot
 ### Composite Types
 Flux [composite types](/flux/v0.x/data-types/composite/) are constructed from
 Flux [basic types](#basic-types).
+All composite types have a Flux literal representation.
 
 - [Records](#records)
 - [Arrays](#arrays)
@@ -281,6 +283,17 @@ regex = /^foo/
 // Returns false
 ```
 
+### View the string representation of any Flux type
+Use [`display()`](/flux/v0.x/stdlib/universe/display) to output the Flux literal
+representation of any value as a string.
+
+```js
+x = bytes(v: "foo")
+
+display(v: x)
+// Returns "0x666f6f"
+```
+
 ## Packages
 The [Flux standard library](/flux/v0.x/stdlib/) is organized into [packages](/flux/v0.x/spec/packages/)
 that contain functions and package-specific options.
@@ -310,17 +323,18 @@ to query sample air sensor data and assigns different streams of data to unique
 ```js
 import "influxdata/influxdb/sample"
 
-data = sample.data(set: "airSensor")
-    |> range(start: -15m)
-    |> filter(fn: (r) => r._measurement == "airSensors")
+data =
+    sample.data(set: "airSensor")
+        |> range(start: -15m)
+        |> filter(fn: (r) => r._measurement == "airSensors")
 
 temperature =
-  data
-    |> filter(fn: (r) => r._field == "temperature")
+    data
+        |> filter(fn: (r) => r._field == "temperature")
 
 humidity =
-  data
-    |> filter(fn: (r) => r._field == "humidity")
+    data
+        |> filter(fn: (r) => r._field == "humidity")
 ```
 
 These variables can be used in other functions, such as  `join()`, while keeping
@@ -334,9 +348,9 @@ to find the top `n` results in the data set.
 
 ```js
 topN = (tables=<-, n) =>
-  tables
-    |> sort(desc: true)
-    |> limit(n: n)
+    tables
+        |> sort(desc: true)
+        |> limit(n: n)
 ```
 
 Use the custom function `topN` and the `humidity` data stream variable defined
@@ -344,7 +358,7 @@ above to return the top three data points in each input table.
 
 ```js
 humidity
-  |> topN(n:3)
+    |> topN(n:3)
 ```
 
 _For more information about creating custom functions, see [Define custom functions](/flux/v0.x/define-functions)._
diff --git a/content/flux/v0.x/prometheus/metric-types/counter.md b/content/flux/v0.x/prometheus/metric-types/counter.md
index c179c51d2..95c3bafcd 100644
--- a/content/flux/v0.x/prometheus/metric-types/counter.md
+++ b/content/flux/v0.x/prometheus/metric-types/counter.md
@@ -71,12 +71,9 @@ On counter reset, `increase()` assumes no increase.
 
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> filter(fn: (r) =>
-    r._measurement == "prometheus" and
-    r._field == "http_query_request_bytes"
-  )
-  |> increase()
+    |> range(start: -1m)
+    |> filter(fn: (r) => r._measurement == "prometheus" and r._field == "http_query_request_bytes")
+    |> increase()
 ```
 
 {{< flex >}}
@@ -130,12 +127,9 @@ On counter reset, `increase()` assumes no increase.
 
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> filter(fn: (r) =>
-    r._measurement == "http_query_request_bytes" and
-    r._field == "counter"
-  )
-  |> increase()
+    |> range(start: -1m)
+    |> filter(fn: (r) => r._measurement == "http_query_request_bytes" and r._field == "counter")
+    |> increase()
 ```
 
 {{< flex >}}
@@ -191,13 +185,10 @@ between subsequent values.
 
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> filter(fn: (r) =>
-    r._measurement == "prometheus" and
-    r._field == "http_query_request_bytes"
-  )
-  |> increase()
-  |> difference()
+    |> range(start: -1m)
+    |> filter(fn: (r) => r._measurement == "prometheus" and r._field == "http_query_request_bytes")
+    |> increase()
+    |> difference()
 ```
 
 {{< flex >}}
@@ -240,13 +231,10 @@ from(bucket: "example-bucket")
 
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> filter(fn: (r) =>
-    r._measurement == "http_query_request_bytes" and
-    r._field == "counter"
-  )
-  |> increase()
-  |> difference()
+    |> range(start: -1m)
+    |> filter(fn: (r) => r._measurement == "http_query_request_bytes" and r._field == "counter")
+    |> increase()
+    |> difference()
 ```
 
 {{< flex >}}
@@ -303,13 +291,10 @@ customize the rate unit.
 
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> filter(fn: (r) =>
-    r._measurement == "prometheus" and
-    r._field == "http_query_request_bytes"
-  )
-  |> increase()
-  |> derivative()
+    |> range(start: -1m)
+    |> filter(fn: (r) => r._measurement == "prometheus" and r._field == "http_query_request_bytes")
+    |> increase()
+    |> derivative()
 ```
 
 {{< flex >}}
@@ -352,13 +337,10 @@ from(bucket: "example-bucket")
 
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> filter(fn: (r) =>
-    r._measurement == "http_query_request_bytes" and
-    r._field == "counter"
-  )
-  |> increase()
-  |> derivative()
+    |> range(start: -1m)
+    |> filter(fn: (r) => r._measurement == "http_query_request_bytes" and r._field == "counter")
+    |> increase()
+    |> derivative()
 ```
 
 {{< flex >}}
@@ -427,13 +409,10 @@ in specified time windows:
 import "experimental/aggregate"
 
 from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> filter(fn: (r) =>
-    r._measurement == "prometheus" and
-    r._field == "http_query_request_bytes"
-  )
-  |> increase()
-  |> aggregate.rate(every: 15s, unit: 1s)
+    |> range(start: -1m)
+    |> filter(fn: (r) => r._measurement == "prometheus" and r._field == "http_query_request_bytes")
+    |> increase()
+    |> aggregate.rate(every: 15s, unit: 1s)
 ```
 
 {{< flex >}}
@@ -479,13 +458,10 @@ from(bucket: "example-bucket")
 import "experimental/aggregate"
 
 from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> filter(fn: (r) =>
-    r._measurement == "http_query_request_bytes" and
-    r._field == "counter"
-  )
-  |> increase()
-  |> aggregate.rate(every: 15s, unit: 1s)
+    |> range(start: -1m)
+    |> filter(fn: (r) => r._measurement == "http_query_request_bytes" and r._field == "counter")
+    |> increase()
+    |> aggregate.rate(every: 15s, unit: 1s)
 ```
 
 {{< flex >}}
diff --git a/content/flux/v0.x/prometheus/metric-types/gauge.md b/content/flux/v0.x/prometheus/metric-types/gauge.md
index c83e1237e..2faf6fda2 100644
--- a/content/flux/v0.x/prometheus/metric-types/gauge.md
+++ b/content/flux/v0.x/prometheus/metric-types/gauge.md
@@ -65,12 +65,9 @@ Select the appropriate metric format version below.
 
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> filter(fn: (r) =>
-    r._measurement == "prometheus" and
-    r._field == "go_goroutines"
-  )
-  |> derivative(nonNegative: true)
+    |> range(start: -1m)
+    |> filter(fn: (r) => r._measurement == "prometheus" and r._field == "go_goroutines")
+    |> derivative(nonNegative: true)
 ```
 
 {{< flex >}}
@@ -122,12 +119,9 @@ from(bucket: "example-bucket")
 
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> filter(fn: (r) =>
-    r._measurement == "go_goroutines" and
-    r._field == "gauge"
-  )
-  |> derivative(nonNegative: true)
+    |> range(start: -1m)
+    |> filter(fn: (r) => r._measurement == "go_goroutines" and r._field == "gauge")
+    |> derivative(nonNegative: true)
 ```
 
 {{< flex >}}
@@ -194,12 +188,9 @@ from(bucket: "example-bucket")
 import "experimental/aggregate"
 
 from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> filter(fn: (r) =>
-    r._measurement == "prometheus" and
-    r._field == "go_goroutines"
-  )
-  |> aggregate.rate(every: 10s, unit: 1s)
+    |> range(start: -1m)
+    |> filter(fn: (r) => r._measurement == "prometheus" and r._field == "go_goroutines")
+    |> aggregate.rate(every: 10s, unit: 1s)
 ```
 
 {{< flex >}}
@@ -262,12 +253,9 @@ from(bucket: "example-bucket")
 import "experimental/aggregate"
 
 from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> filter(fn: (r) =>
-    r._measurement == "go_goroutines" and
-    r._field == "gauge"
-  )
-  |> aggregate.rate(every: 10s, unit: 1s)
+    |> range(start: -1m)
+    |> filter(fn: (r) => r._measurement == "go_goroutines" and r._field == "gauge")
+    |> aggregate.rate(every: 10s, unit: 1s)
 ```
 
 {{< flex >}}
diff --git a/content/flux/v0.x/prometheus/metric-types/histogram.md b/content/flux/v0.x/prometheus/metric-types/histogram.md
index 0507d959c..a1f260629 100644
--- a/content/flux/v0.x/prometheus/metric-types/histogram.md
+++ b/content/flux/v0.x/prometheus/metric-types/histogram.md
@@ -78,11 +78,11 @@ is **not compatible** with the format of Prometheus histogram data stored in Inf
 import "experimental/prometheus"
 
 from(bucket: "example-bucket")
-  |> start(range: -1h)
-  |> filter(fn: (r) => r._measurement == "prometheus")
-  |> filter(fn: (r) => r._field == "qc_all_duration_seconds")
-  |> aggregateWindow(every: 1m, fn: mean, createEmpty: false)
-  |> prometheus.histogramQuantile(quantile: 0.99)
+    |> start(range: -1h)
+    |> filter(fn: (r) => r._measurement == "prometheus")
+    |> filter(fn: (r) => r._field == "qc_all_duration_seconds")
+    |> aggregateWindow(every: 1m, fn: mean, createEmpty: false)
+    |> prometheus.histogramQuantile(quantile: 0.99)
 ```
 {{% /tab-content %}}
 
@@ -99,10 +99,10 @@ from(bucket: "example-bucket")
 import "experimental/prometheus"
 
 from(bucket: "example-bucket")
-  |> start(range: -1h)
-  |> filter(fn: (r) => r._measurement == "qc_all_duration_seconds")
-  |> aggregateWindow(every: 1m, fn: mean, createEmpty: false)
-  |> prometheus.histogramQuantile(quantile: 0.99, metricVersion: 1)
+    |> start(range: -1h)
+    |> filter(fn: (r) => r._measurement == "qc_all_duration_seconds")
+    |> aggregateWindow(every: 1m, fn: mean, createEmpty: false)
+    |> prometheus.histogramQuantile(quantile: 0.99, metricVersion: 1)
 ```
 {{% /tab-content %}}
 {{< /tabs-wrapper >}}
@@ -135,17 +135,20 @@ histogramQuantile: unexpected null in the countColumn
 ```js
 import "experimental/prometheus"
 
-data = from(bucket: "example-bucket")
-  |> start(range: -1h)
-  |> filter(fn: (r) => r._measurement == "prometheus")
-  |> filter(fn: (r) => r._field == "qc_all_duration_seconds")
-  |> aggregateWindow(every: 1m, fn: mean, createEmpty: false)
-  
-union(tables: [
-  data |> prometheus.histogramQuantile(quantile: 0.99),
-  data |> prometheus.histogramQuantile(quantile: 0.5),
-  data |> prometheus.histogramQuantile(quantile: 0.25)
-])
+data =
+    from(bucket: "example-bucket")
+        |> start(range: -1h)
+        |> filter(fn: (r) => r._measurement == "prometheus")
+        |> filter(fn: (r) => r._field == "qc_all_duration_seconds")
+        |> aggregateWindow(every: 1m, fn: mean, createEmpty: false)
+
+union(
+    tables: [
+        data |> prometheus.histogramQuantile(quantile: 0.99),
+        data |> prometheus.histogramQuantile(quantile: 0.5),
+        data |> prometheus.histogramQuantile(quantile: 0.25),
+    ],
+)
 ```
 {{% /code-tab-content %}}
 
@@ -153,17 +156,19 @@ union(tables: [
 ```js
 import "experimental/prometheus"
 
-data = from(bucket: "example-bucket")
-  |> start(range: -1h)
-  |> filter(fn: (r) => r._measurement == "qc_all_duration_seconds")
-  |> aggregateWindow(every: 1m, fn: mean, createEmpty: false)
+data =
+    from(bucket: "example-bucket")
+        |> start(range: -1h)
+        |> filter(fn: (r) => r._measurement == "qc_all_duration_seconds")
+        |> aggregateWindow(every: 1m, fn: mean, createEmpty: false)
 
-union(tables: [
-  data |> prometheus.histogramQuantile(quantile: 0.99, metricVersion: 1),
-  data |> prometheus.histogramQuantile(quantile: 0.5, metricVersion: 1),
-  data |> prometheus.histogramQuantile(quantile: 0.25, metricVersion: 1)
-])
-  
+union(
+    tables: [
+        data |> prometheus.histogramQuantile(quantile: 0.99, metricVersion: 1),
+        data |> prometheus.histogramQuantile(quantile: 0.5, metricVersion: 1),
+        data |> prometheus.histogramQuantile(quantile: 0.25, metricVersion: 1),
+    ],
+)
 ```
 {{% /code-tab-content %}}
 {{< /code-tabs-wrapper >}}
diff --git a/content/flux/v0.x/prometheus/metric-types/summary.md b/content/flux/v0.x/prometheus/metric-types/summary.md
index 857d828c5..d79f4cf1d 100644
--- a/content/flux/v0.x/prometheus/metric-types/summary.md
+++ b/content/flux/v0.x/prometheus/metric-types/summary.md
@@ -64,9 +64,9 @@ Prometheus summary metrics provide quantile values that can be visualized withou
 
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> filter(fn: (r) => r._measurement == "prometheus")
-  |> filter(fn: (r) => r._field == "go_gc_duration_seconds")
+    |> range(start: -1m)
+    |> filter(fn: (r) => r._measurement == "prometheus")
+    |> filter(fn: (r) => r._field == "go_gc_duration_seconds")
 ```
 {{% /tab-content %}}
 {{% tab-content %}}
@@ -76,9 +76,9 @@ from(bucket: "example-bucket")
 
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> filter(fn: (r) => r._measurement == "go_gc_duration_seconds")
-  |> filter(fn: (r) => r._field != "count" and r._field != "sum")
+    |> range(start: -1m)
+    |> filter(fn: (r) => r._measurement == "go_gc_duration_seconds")
+    |> filter(fn: (r) => r._field != "count" and r._field != "sum")
 ```
 {{% /tab-content %}}
 {{< /tabs-wrapper >}}
@@ -106,16 +106,11 @@ derive an average summary value.
 
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> filter(fn: (r) => r._measurement == "prometheus")
-  |> filter(fn: (r) =>
-    r._field == "go_gc_duration_seconds_count" or
-    r._field == "go_gc_duration_seconds_sum"
-  )
-  |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
-  |> map(fn: (r) => ({ r with
-    _value: r.go_gc_duration_seconds_sum / r.go_gc_duration_seconds_count
-  }))
+    |> range(start: -1m)
+    |> filter(fn: (r) => r._measurement == "prometheus")
+    |> filter(fn: (r) => r._field == "go_gc_duration_seconds_count" or r._field == "go_gc_duration_seconds_sum")
+    |> pivot(rowKey: ["_time"], columnKey: ["_field"], valueColumn: "_value")
+    |> map(fn: (r) => ({r with _value: r.go_gc_duration_seconds_sum / r.go_gc_duration_seconds_count}))
 ```
 {{% /tab-content %}}
 {{% tab-content %}}
@@ -128,11 +123,11 @@ from(bucket: "example-bucket")
 
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> filter(fn: (r) => r._measurement == "go_gc_duration_seconds")
-  |> filter(fn: (r) => r._field == "count" or r._field == "sum")
-  |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
-  |> map(fn: (r) => ({ r with _value: r.sum / r.count }))
+    |> range(start: -1m)
+    |> filter(fn: (r) => r._measurement == "go_gc_duration_seconds")
+    |> filter(fn: (r) => r._field == "count" or r._field == "sum")
+    |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
+    |> map(fn: (r) => ({ r with _value: r.sum / r.count }))
 ```
 {{% /tab-content %}}
 {{< /tabs-wrapper >}}
\ No newline at end of file
diff --git a/content/flux/v0.x/prometheus/scrape-prometheus.md b/content/flux/v0.x/prometheus/scrape-prometheus.md
index 40d5722c1..023c89515 100644
--- a/content/flux/v0.x/prometheus/scrape-prometheus.md
+++ b/content/flux/v0.x/prometheus/scrape-prometheus.md
@@ -166,14 +166,9 @@ To write scraped Prometheus metrics to InfluxDB:
 
 ```js
 import "experimental/prometheus"
-  
+
 prometheus.scrape(url: "http://example.com/metrics")
-  |> to(
-    bucket: "example-bucket",
-    host: "http://localhost:8086",
-    org: "example-org",
-    token: "mYsuP3R5eCR37t0K3n"  
-  )
+    |> to(bucket: "example-bucket", host: "http://localhost:8086", org: "example-org", token: "mYsuP3R5eCR37t0K3n")
 ```
 
 ### Write Prometheus metrics to InfluxDB at regular intervals
@@ -183,11 +178,8 @@ scrape Prometheus metrics in an [InfluxDB task](/influxdb/cloud/process-data/get
 ```js
 import "experimental/prometheus"
 
-option task = {
-  name: "Scrape Prometheus metrics",
-  every: 10s
-}
-  
+option task = {name: "Scrape Prometheus metrics", every: 10s}
+
 prometheus.scrape(url: "http://example.com/metrics")
-  |> to(bucket: "example-bucket")
+    |> to(bucket: "example-bucket")
 ```
diff --git a/content/flux/v0.x/query-data/bigtable.md b/content/flux/v0.x/query-data/bigtable.md
index 25f4d4442..54c637748 100644
--- a/content/flux/v0.x/query-data/bigtable.md
+++ b/content/flux/v0.x/query-data/bigtable.md
@@ -37,10 +37,10 @@ To query [Google Cloud Bigtable](https://cloud.google.com/bigtable/) with Flux:
 import "experimental/bigtable"
 
 bigtable.from(
-  token: "mySuPeRseCretTokEn",
-  project: "exampleProjectID",
-  instance: "exampleInstanceID",
-  table: "example-table"
+    token: "mySuPeRseCretTokEn",
+    project: "exampleProjectID",
+    instance: "exampleInstanceID",
+    table: "example-table",
 )
 ```
 
@@ -65,9 +65,9 @@ bigtable_project = secrets.get(key: "BIGTABLE_PROJECT_ID")
 bigtable_instance = secrets.get(key: "BIGTABLE_INSTANCE_ID")
 
 bigtable.from(
-  token: bigtable_token,
-  project: bigtable_project,
-  instance: bigtable_instance,
-  table: "example-table"
+    token: bigtable_token,
+    project: bigtable_project,
+    instance: bigtable_instance,
+    table: "example-table"
 )
 ```
diff --git a/content/flux/v0.x/query-data/csv.md b/content/flux/v0.x/query-data/csv.md
index bda267776..588fac421 100644
--- a/content/flux/v0.x/query-data/csv.md
+++ b/content/flux/v0.x/query-data/csv.md
@@ -19,7 +19,8 @@ list_code_example: |
   ```js
   import "csv"
 
-  csvData = "
+  csvData =
+      "
   #group,false,false,true,true,true,false,false
   #datatype,string,long,string,string,string,long,double
   #default,_result,,,,,,
@@ -29,7 +30,7 @@ list_code_example: |
   ,,1,air-sensors,humidity,TLM0200,1627049400000000000,35.64
   ,,1,air-sensors,humidity,TLM0200,1627049700000000000,35.67
   "
-  
+
   csv.from(csv: csvData)
   ```
 ---
@@ -91,7 +92,8 @@ to execute Flux queries._
 ```js
 import "csv"
 
-csvData = "
+csvData =
+    "
 #group,false,false,true,true,true,false,false
 #datatype,string,long,string,string,string,long,double
 #default,_result,,,,,,
@@ -143,7 +145,8 @@ csv.from(csv: csvData)
 ```js
 import "csv"
 
-csvData = "
+csvData =
+    "
 dataset,metric,sensorID,timestamp,value
 air-sensors,humidity,TLM0100,1627049400000000000,34.79
 air-sensors,humidity,TLM0100,1627049700000000000,34.65
diff --git a/content/flux/v0.x/query-data/influxdb.md b/content/flux/v0.x/query-data/influxdb.md
index 1db11ad6e..be9f5b46a 100644
--- a/content/flux/v0.x/query-data/influxdb.md
+++ b/content/flux/v0.x/query-data/influxdb.md
@@ -34,11 +34,9 @@ InfluxDB requires queries to be time-bound, so `from()` must always be followed
 
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -1h)
+    |> range(start: -1h)
 ```
 
-
-
 ## Query InfluxDB Cloud or 2.x remotely
 To query InfluxDB Cloud or 2.x remotely, provide the following parameters
 in addition to **bucket** or **bucketID**.
@@ -50,10 +48,10 @@ in addition to **bucket** or **bucketID**.
 
 ```js
 from(
-  bucket: "example-bucket",
-  host: "http://localhost:8086",
-  org: "example-org",
-  token: "mYSup3r5Ecr3T70keN"
+    bucket: "example-bucket",
+    host: "http://localhost:8086",
+    org: "example-org",
+    token: "mYSup3r5Ecr3T70keN",
 )
 ```
 
@@ -64,7 +62,7 @@ For example, to query data from the `autogen` retention policy in the `telegraf`
 
 ```js
 from(bucket: "telegraf/autogen")
-  |> range(start: -30m)
+    |> range(start: -30m)
 ```
 
 To query the [default retention policy](/{{< latest "influxdb" "v1" >}}/query_language/manage-database/#create-a-retention-policy) in a database, use the same bucket naming
@@ -72,7 +70,7 @@ convention, but do not provide a retention policy:
 
 ```js
 from(bucket: "telegraf/")
-  |> range(start: -30m)
+    |> range(start: -30m)
 ```
 
 
diff --git a/content/flux/v0.x/query-data/prometheus.md b/content/flux/v0.x/query-data/prometheus.md
deleted file mode 100644
index da643a946..000000000
--- a/content/flux/v0.x/query-data/prometheus.md
+++ /dev/null
@@ -1,119 +0,0 @@
----
-title: Scrape Prometheus metrics
-list_title: Prometheus
-description: >
-  Use [`prometheus.scrape`](/flux/v0.x/stdlib/experimental/prometheus/scrape) to
-  scrape Prometheus-formatted metrics from an HTTP-accessible endpoint using Flux.
-menu:
-  flux_0_x:
-    name: Prometheus
-    parent: Query data sources
-weight: 104
-list_code_example: |
-  ```js
-  import "experimental/prometheus"
-  
-  prometheus.scrape(url: "http://example.com/metrics")
-  ```
-draft: true
----
-
-To scrape Prometheus-formatted metrics from an HTTP-accessible endpoint using Flux:
-
-1. Import the [`experimental/prometheus` package](/flux/v0.x/stdlib/experimental/prometheus/).
-2. Use [`prometheus.scrape`](/flux/v0.x/stdlib/experimental/prometheus/scrape).
-   Use the **url** parameter to provide the URL to scrape metrics from.
-
-{{< keep-url >}}
-```js
-import "experimental/prometheus"
-
-prometheus.scrape(url: "http://localhost:8086/metrics")
-```
-
-## Results structure
-`prometheus.scrape()` returns a [stream of tables](/flux/v0.x/get-started/data-model/#stream-of-tables)
-with the following columns:
-
-- **_time**: Data timestamp
-- **_measurement**: `prometheus`
-- **_field**: [Prometheus metric name](https://prometheus.io/docs/concepts/data_model/#metric-names-and-labels)
-- **_value**: [Prometheus metric value](https://prometheus.io/docs/concepts/data_model/#metric-names-and-labels)
-- **url**: URL metrics were scraped from
-- **Label columns**: A column for each [Prometheus label](https://prometheus.io/docs/concepts/data_model/#metric-names-and-labels).
-  The column label is the label name and the column value is the label value.
-
-Tables are grouped by **_measurement**, **_field**, and **Label columns**.
-
-{{% note %}}
-#### Columns with the underscore prefix
-Columns with the underscore (`_`) prefix are considered "system" columns.
-Some Flux functions require these columns to function properly.
-{{% /note %}}
-
-### Example Prometheus query results
-The following are example Prometheus metrics scraped from the InfluxDB OSS 2.x `/metrics` endpoint:
-
-```sh
-# HELP go_goroutines Number of goroutines that currently exist.
-# TYPE go_goroutines gauge
-go_goroutines 1263
-# HELP go_info Information about the Go environment.
-# TYPE go_info gauge
-go_info{version="go1.16.3"} 1
-# HELP go_memstats_alloc_bytes Number of bytes allocated and still in use.
-# TYPE go_memstats_alloc_bytes gauge
-go_memstats_alloc_bytes 2.6598832e+07
-# HELP go_memstats_alloc_bytes_total Total number of bytes allocated, even if freed.
-# TYPE go_memstats_alloc_bytes_total counter
-go_memstats_alloc_bytes_total 1.42276424e+09
-# HELP go_memstats_buck_hash_sys_bytes Number of bytes used by the profiling bucket hash table.
-# TYPE go_memstats_buck_hash_sys_bytes gauge
-go_memstats_buck_hash_sys_bytes 5.259247e+06
-```
-
-When scraped by Flux, these metrics return the following stream of tables:
-
-| _time                | _measurement | _field        | _value | url                           |
-| :------------------- | :----------- | :------------ | -----: | :---------------------------- |
-| 2021-01-01T00:00:00Z | prometheus   | go_goroutines |   1263 | http://localhost:8086/metrics |
-
-| _time                | _measurement | _field  | _value | url                           | version  |
-| :------------------- | :----------- | :------ | -----: | :---------------------------- | -------- |
-| 2021-01-01T00:00:00Z | prometheus   | go_info |      1 | http://localhost:8086/metrics | go1.16.3 |
-
-| _time                | _measurement | _field                  |   _value | url                           |
-| :------------------- | :----------- | :---------------------- | -------: | :---------------------------- |
-| 2021-01-01T00:00:00Z | prometheus   | go_memstats_alloc_bytes | 26598832 | http://localhost:8086/metrics |
-
-| _time                | _measurement | _field                        |     _value | url                           |
-| :------------------- | :----------- | :---------------------------- | ---------: | :---------------------------- |
-| 2021-01-01T00:00:00Z | prometheus   | go_memstats_alloc_bytes_total | 1422764240 | http://localhost:8086/metrics |
-
-| _time                | _measurement | _field                          |  _value | url                           |
-| :------------------- | :----------- | :------------------------------ | ------: | :---------------------------- |
-| 2021-01-01T00:00:00Z | prometheus   | go_memstats_buck_hash_sys_bytes | 5259247 | http://localhost:8086/metrics |
-
-{{% note %}}
-#### Write Prometheus metrics to InfluxDB
-To write scraped Prometheus metrics to InfluxDB:
-
-1. Use `prometheus.scrape()` to scrape Prometheus metrics.
-2. Use [`to()`](/flux/v0.x/stdlib/influxdata/influxdb/to/) to write the scraped
-   metrics to InfluxDB.
-
-```js
-import "experimental/prometheus"
-  
-prometheus.scrape(url: "http://example.com/metrics")
-  |> to(
-    bucket: "example-bucket",
-    host: "http://localhost:8086",
-    org: "example-org",
-    token: "mYsuP3R5eCR37t0K3n"  
-  )
-```
-
-To scrape Prometheus metrics and write them to InfluxDB at regular intervals,
-use the example above to [create an InfluxDB task](/influxdb/cloud/process-data/get-started/).
-{{% /note %}}
diff --git a/content/flux/v0.x/query-data/sql/_index.md b/content/flux/v0.x/query-data/sql/_index.md
index 56ce7b438..a32b9081c 100644
--- a/content/flux/v0.x/query-data/sql/_index.md
+++ b/content/flux/v0.x/query-data/sql/_index.md
@@ -15,9 +15,9 @@ list_code_example: |
   import "sql"
   
   sql.from(
-    driverName: "postgres",
-    dataSourceName: "postgresql://user:password@localhost",
-    query:"SELECT * FROM TestTable"
+      driverName: "postgres",
+      dataSourceName: "postgresql://user:password@localhost",
+      query:"SELECT * FROM TestTable",
   )
   ```
 ---
@@ -70,9 +70,9 @@ username = secrets.get(key: "POSTGRES_USER")
 password = secrets.get(key: "POSTGRES_PASS")
 
 sql.from(
-  driverName: "postgres",
-  dataSourceName: "postgresql://${username}:${password}@localhost:5432",
-  query: "SELECT * FROM example_table"
+    driverName: "postgres",
+    dataSourceName: "postgresql://${username}:${password}@localhost:5432",
+    query: "SELECT * FROM example_table",
 )
 ```
 
@@ -105,9 +105,9 @@ Given the following **example_table** in a MySQL database:
 import "sql"
 
 sql.from(
-  driver: "mysql",
-  dataSourceName: "username:passwOrd@tcp(localhost:3306)/db",
-  query: "SELECT ID, Name FROM example_table"
+    driver: "mysql",
+    dataSourceName: "username:passwOrd@tcp(localhost:3306)/db",
+    query: "SELECT ID, Name FROM example_table",
 )
 ```
 
diff --git a/content/flux/v0.x/query-data/sql/amazon-rds.md b/content/flux/v0.x/query-data/sql/amazon-rds.md
index 6bee10cc3..6c35911b1 100644
--- a/content/flux/v0.x/query-data/sql/amazon-rds.md
+++ b/content/flux/v0.x/query-data/sql/amazon-rds.md
@@ -14,11 +14,11 @@ related:
 list_code_example: |
   ```js
   import "sql"
-  
+
   sql.from(
-    driverName: "postgres",
-    dataSourceName: "postgresql://my-instance.123456789012.us-east-1.rds.amazonaws.com:5432",
-    query: "SELECT * FROM example_table"
+      driverName: "postgres",
+      dataSourceName: "postgresql://my-instance.123456789012.us-east-1.rds.amazonaws.com:5432",
+      query: "SELECT * FROM example_table",
   )
   ```
 ---
@@ -39,9 +39,9 @@ with Flux:
 import "sql"
 
 sql.from(
-  driverName: "postgres",
-  dataSourceName: "postgresql://my-instance.123456789012.us-east-1.rds.amazonaws.com:5432",
-  query: "SELECT * FROM example_table"
+    driverName: "postgres",
+    dataSourceName: "postgresql://my-instance.123456789012.us-east-1.rds.amazonaws.com:5432",
+    query: "SELECT * FROM example_table",
 )
 ```
 
diff --git a/content/flux/v0.x/query-data/sql/athena.md b/content/flux/v0.x/query-data/sql/athena.md
index 1975daf76..8a408fb38 100644
--- a/content/flux/v0.x/query-data/sql/athena.md
+++ b/content/flux/v0.x/query-data/sql/athena.md
@@ -15,9 +15,10 @@ list_code_example: |
   import "sql"
 
   sql.from(
-    driverName: "awsathena",
-    dataSourceName: "s3://myorgqueryresults/?accessID=12ab34cd56ef&region=region-name&secretAccessKey=y0urSup3rs3crEtT0k3n",
-    query: "GO SELECT * FROM Example.Table"
+      driverName: "awsathena",
+      dataSourceName:
+          "s3://myorgqueryresults/?accessID=12ab34cd56ef&region=region-name&secretAccessKey=y0urSup3rs3crEtT0k3n",
+      query: "GO SELECT * FROM Example.Table",
   )
   ```
 ---
@@ -35,9 +36,10 @@ To query [Amazon Athena](https://aws.amazon.com/athena) with Flux:
 import "sql"
 
 sql.from(
-  driverName: "awsathena",
-  dataSourceName: "s3://myorgqueryresults/?accessID=12ab34cd56ef&region=region-name&secretAccessKey=y0urSup3rs3crEtT0k3n",
-  query: "GO SELECT * FROM Example.Table"
+    driverName: "awsathena",
+    dataSourceName:
+        "s3://myorgqueryresults/?accessID=12ab34cd56ef&region=region-name&secretAccessKey=y0urSup3rs3crEtT0k3n",
+    query: "GO SELECT * FROM Example.Table",
 )
 ```
 
diff --git a/content/flux/v0.x/query-data/sql/bigquery.md b/content/flux/v0.x/query-data/sql/bigquery.md
index 30f62fa90..b7d7debd3 100644
--- a/content/flux/v0.x/query-data/sql/bigquery.md
+++ b/content/flux/v0.x/query-data/sql/bigquery.md
@@ -15,9 +15,9 @@ list_code_example: |
   import "sql"
 
   sql.from(
-    driverName: "bigquery",
-    dataSourceName: "bigquery://projectid/?apiKey=mySuP3r5ecR3tAP1K3y",
-    query: "SELECT * FROM exampleTable"
+      driverName: "bigquery",
+      dataSourceName: "bigquery://projectid/?apiKey=mySuP3r5ecR3tAP1K3y",
+      query: "SELECT * FROM exampleTable",
   )
   ```
 ---
@@ -35,9 +35,9 @@ To query [Google BigQuery](https://cloud.google.com/bigquery) with Flux:
 import "sql"
 
 sql.from(
-  driverName: "bigquery",
-  dataSourceName: "bigquery://projectid/?apiKey=mySuP3r5ecR3tAP1K3y",
-  query: "SELECT * FROM exampleTable"
+    driverName: "bigquery",
+    dataSourceName: "bigquery://projectid/?apiKey=mySuP3r5ecR3tAP1K3y",
+    query: "SELECT * FROM exampleTable",
 )
 ```
 
diff --git a/content/flux/v0.x/query-data/sql/cockroachdb.md b/content/flux/v0.x/query-data/sql/cockroachdb.md
index 803cf7879..fdccf4bfe 100644
--- a/content/flux/v0.x/query-data/sql/cockroachdb.md
+++ b/content/flux/v0.x/query-data/sql/cockroachdb.md
@@ -13,11 +13,12 @@ related:
 list_code_example: |
   ```js
   import "sql"
-  
+
   sql.from(
-    driverName: "postgres",
-    dataSourceName: "postgresql://username:password@localhost:26257/cluster_name.defaultdb?sslmode=verify-full&sslrootcert=certs_dir/cc-ca.crt",
-    query: "SELECT * FROM example_table"
+      driverName: "postgres",
+      dataSourceName:
+          "postgresql://username:password@localhost:26257/cluster_name.defaultdb?sslmode=verify-full&sslrootcert=certs_dir/cc-ca.crt",
+      query: "SELECT * FROM example_table",
   )
   ```
 ---
@@ -35,9 +36,10 @@ To query [CockroachDB](https://www.cockroachlabs.com/) with Flux:
 import "sql"
 
 sql.from(
-  driverName: "postgres",
-  dataSourceName: "postgresql://username:password@localhost:26257/cluster_name.defaultdb?sslmode=verify-full&sslrootcert=certs_dir/cc-ca.crt",
-  query: "SELECT * FROM example_table"
+    driverName: "postgres",
+    dataSourceName:
+        "postgresql://username:password@localhost:26257/cluster_name.defaultdb?sslmode=verify-full&sslrootcert=certs_dir/cc-ca.crt",
+    query: "SELECT * FROM example_table",
 )
 ```
 
diff --git a/content/flux/v0.x/query-data/sql/mariadb.md b/content/flux/v0.x/query-data/sql/mariadb.md
index 3d9937ed7..2e18f4024 100644
--- a/content/flux/v0.x/query-data/sql/mariadb.md
+++ b/content/flux/v0.x/query-data/sql/mariadb.md
@@ -13,11 +13,11 @@ related:
 list_code_example: |
   ```js
   import "sql"
-  
+
   sql.from(
-    driverName: "mysql",
-    dataSourceName: "user:password@tcp(localhost:3306)/db",
-    query: "SELECT * FROM example_table"
+      driverName: "mysql",
+      dataSourceName: "user:password@tcp(localhost:3306)/db",
+      query: "SELECT * FROM example_table",
   )
   ```
 ---
@@ -35,9 +35,9 @@ To query [MariaDB](https://mariadb.org/) with Flux:
 import "sql"
 
 sql.from(
-  driverName: "mysql",
-  dataSourceName: "user:password@tcp(localhost:3306)/db",
-  query: "SELECT * FROM example_table"
+    driverName: "mysql",
+    dataSourceName: "user:password@tcp(localhost:3306)/db",
+    query: "SELECT * FROM example_table",
 )
 ```
 
diff --git a/content/flux/v0.x/query-data/sql/mysql.md b/content/flux/v0.x/query-data/sql/mysql.md
index d7279c148..00c609d3d 100644
--- a/content/flux/v0.x/query-data/sql/mysql.md
+++ b/content/flux/v0.x/query-data/sql/mysql.md
@@ -15,9 +15,9 @@ list_code_example: |
   import "sql"
   
   sql.from(
-    driverName: "mysql",
-    dataSourceName: "user:password@tcp(localhost:3306)/db",
-    query: "SELECT * FROM example_table"
+      driverName: "mysql",
+      dataSourceName: "user:password@tcp(localhost:3306)/db",
+      query: "SELECT * FROM example_table",
   )
   ```
 ---
@@ -35,9 +35,9 @@ To query [MySQL](https://www.mysql.com/) with Flux:
 import "sql"
 
 sql.from(
-  driverName: "mysql",
-  dataSourceName: "user:password@tcp(localhost:3306)/db",
-  query: "SELECT * FROM example_table"
+    driverName: "mysql",
+    dataSourceName: "user:password@tcp(localhost:3306)/db",
+    query: "SELECT * FROM example_table",
 )
 ```
 
diff --git a/content/flux/v0.x/query-data/sql/percona.md b/content/flux/v0.x/query-data/sql/percona.md
index 39f8d12d3..1bbff3ff1 100644
--- a/content/flux/v0.x/query-data/sql/percona.md
+++ b/content/flux/v0.x/query-data/sql/percona.md
@@ -15,9 +15,9 @@ list_code_example: |
   import "sql"
   
   sql.from(
-    driverName: "mysql",
-    dataSourceName: "user:password@tcp(localhost:3306)/db",
-    query: "SELECT * FROM example_table"
+      driverName: "mysql",
+      dataSourceName: "user:password@tcp(localhost:3306)/db",
+      query: "SELECT * FROM example_table",
   )
   ```
 ---
@@ -35,9 +35,9 @@ To query [Percona](https://www.percona.com/) with Flux:
 import "sql"
 
 sql.from(
-  driverName: "mysql",
-  dataSourceName: "user:password@tcp(localhost:3306)/db",
-  query: "SELECT * FROM example_table"
+    driverName: "mysql",
+    dataSourceName: "user:password@tcp(localhost:3306)/db",
+    query: "SELECT * FROM example_table",
 )
 ```
 
diff --git a/content/flux/v0.x/query-data/sql/postgresql.md b/content/flux/v0.x/query-data/sql/postgresql.md
index 581362e73..6c17b7c0c 100644
--- a/content/flux/v0.x/query-data/sql/postgresql.md
+++ b/content/flux/v0.x/query-data/sql/postgresql.md
@@ -15,9 +15,9 @@ list_code_example: |
   import "sql"
   
   sql.from(
-    driverName: "postgres",
-    dataSourceName: "postgresql://username:password@localhost:5432",
-    query: "SELECT * FROM example_table"
+      driverName: "postgres",
+      dataSourceName: "postgresql://username:password@localhost:5432",
+      query: "SELECT * FROM example_table",
   )
   ```
 ---
@@ -35,9 +35,9 @@ To query [PostgreSQL](https://www.postgresql.org/) with Flux:
 import "sql"
 
 sql.from(
-  driverName: "postgres",
-  dataSourceName: "postgresql://username:password@localhost:5432",
-  query: "SELECT * FROM example_table"
+    driverName: "postgres",
+    dataSourceName: "postgresql://username:password@localhost:5432",
+    query: "SELECT * FROM example_table",
 )
 ```
 
diff --git a/content/flux/v0.x/query-data/sql/sap-hana.md b/content/flux/v0.x/query-data/sql/sap-hana.md
index 9f3664966..a55aca492 100644
--- a/content/flux/v0.x/query-data/sql/sap-hana.md
+++ b/content/flux/v0.x/query-data/sql/sap-hana.md
@@ -15,9 +15,9 @@ list_code_example: |
   import "sql"
   
   sql.from(
-    driverName: "hdb",
-    dataSourceName: "hdb://username:password@myserver:30015",
-    query: "SELECT * FROM SCHEMA.TABLE"
+      driverName: "hdb",
+      dataSourceName: "hdb://username:password@myserver:30015",
+      query: "SELECT * FROM SCHEMA.TABLE",
   )
   ```
 ---
@@ -35,9 +35,9 @@ To query [SAP HANA](https://www.sap.com/products/hana.html) with Flux:
 import "sql"
 
 sql.from(
-  driverName: "hdb",
-  dataSourceName: "hdb://username:password@myserver:30015",
-  query: "SELECT * FROM SCHEMA.TABLE"
+    driverName: "hdb",
+    dataSourceName: "hdb://username:password@myserver:30015",
+    query: "SELECT * FROM SCHEMA.TABLE",
 )
 ```
 
diff --git a/content/flux/v0.x/query-data/sql/snowflake.md b/content/flux/v0.x/query-data/sql/snowflake.md
index 282413f2b..466abd418 100644
--- a/content/flux/v0.x/query-data/sql/snowflake.md
+++ b/content/flux/v0.x/query-data/sql/snowflake.md
@@ -15,9 +15,9 @@ list_code_example: |
   import "sql"
   
   sql.from(
-    driverName: "snowflake",
-    dataSourceName: "user:password@account/db/exampleschema?warehouse=wh",
-    query: "SELECT * FROM example_table"
+      driverName: "snowflake",
+      dataSourceName: "user:password@account/db/exampleschema?warehouse=wh",
+      query: "SELECT * FROM example_table",
   )
   ```
 ---
@@ -35,9 +35,9 @@ To query [Snowflake](https://www.snowflake.com/) with Flux:
 import "sql"
 
 sql.from(
-  driverName: "snowflake",
-  dataSourceName: "user:password@account/db/exampleschema?warehouse=wh",
-  query: "SELECT * FROM example_table"
+    driverName: "snowflake",
+    dataSourceName: "user:password@account/db/exampleschema?warehouse=wh",
+    query: "SELECT * FROM example_table",
 )
 ```
 
diff --git a/content/flux/v0.x/query-data/sql/sql-server.md b/content/flux/v0.x/query-data/sql/sql-server.md
index 417eb328c..15f0f6457 100644
--- a/content/flux/v0.x/query-data/sql/sql-server.md
+++ b/content/flux/v0.x/query-data/sql/sql-server.md
@@ -16,9 +16,9 @@ list_code_example: |
   import "sql"
 
   sql.from(
-    driverName: "sqlserver",
-    dataSourceName: "sqlserver://user:password@localhost:1433?database=examplebdb",
-    query: "GO SELECT * FROM Example.Table"
+      driverName: "sqlserver",
+      dataSourceName: "sqlserver://user:password@localhost:1433?database=examplebdb",
+      query: "GO SELECT * FROM Example.Table",
   )
   ```
 ---
@@ -36,9 +36,9 @@ To query [Microsoft SQL Server](https://www.microsoft.com/sql-server/) with Flux
 import "sql"
 
 sql.from(
-  driverName: "sqlserver",
-  dataSourceName: "sqlserver://user:password@localhost:1433?database=examplebdb",
-  query: "GO SELECT * FROM Example.Table"
+    driverName: "sqlserver",
+    dataSourceName: "sqlserver://user:password@localhost:1433?database=examplebdb",
+    query: "GO SELECT * FROM Example.Table",
 )
 ```
 
diff --git a/content/flux/v0.x/query-data/sql/sqlite.md b/content/flux/v0.x/query-data/sql/sqlite.md
index 8b557c9b6..5c3d7e17f 100644
--- a/content/flux/v0.x/query-data/sql/sqlite.md
+++ b/content/flux/v0.x/query-data/sql/sqlite.md
@@ -15,9 +15,9 @@ list_code_example: |
   import "sql"
 
   sql.from(
-    driverName: "sqlite3",
-    dataSourceName: "file:/path/to/example.db?cache=shared&mode=ro",
-    query: "SELECT * FROM example_table"
+      driverName: "sqlite3",
+      dataSourceName: "file:/path/to/example.db?cache=shared&mode=ro",
+      query: "SELECT * FROM example_table",
   )
   ```
 ---
@@ -35,9 +35,9 @@ To query [SQLite](https://www.sqlite.org/index.html) with Flux:
 import "sql"
 
 sql.from(
-  driverName: "sqlite3",
-  dataSourceName: "file:/path/to/example.db?cache=shared&mode=ro",
-  query: "SELECT * FROM example_table"
+    driverName: "sqlite3",
+    dataSourceName: "file:/path/to/example.db?cache=shared&mode=ro",
+    query: "SELECT * FROM example_table",
 )
 ```
 
diff --git a/content/flux/v0.x/query-data/sql/vertica.md b/content/flux/v0.x/query-data/sql/vertica.md
index 6b973d24a..42e00a1c5 100644
--- a/content/flux/v0.x/query-data/sql/vertica.md
+++ b/content/flux/v0.x/query-data/sql/vertica.md
@@ -16,9 +16,9 @@ list_code_example: |
   import "sql"
   
   sql.from(
-    driverName: "vertica",
-    dataSourceName: "vertica://username:password@localhost:5432",
-    query: "SELECT * FROM public.example_table"
+      driverName: "vertica",
+      dataSourceName: "vertica://username:password@localhost:5432",
+      query: "SELECT * FROM public.example_table",
   )
   ```
 ---
@@ -36,9 +36,9 @@ To query [Vertica](https://www.vertica.com/) with Flux:
 import "sql"
 
 sql.from(
-  driverName: "vertica",
-  dataSourceName: "vertica://username:password@localhost:5433/dbname",
-  query: "SELECT * FROM public.example_table"
+    driverName: "vertica",
+    dataSourceName: "vertica://username:password@localhost:5433/dbname",
+    query: "SELECT * FROM public.example_table",
 )
 ```
 
diff --git a/content/flux/v0.x/release-notes.md b/content/flux/v0.x/release-notes.md
index 6fb15a0f3..5cb77ed60 100644
--- a/content/flux/v0.x/release-notes.md
+++ b/content/flux/v0.x/release-notes.md
@@ -10,6 +10,269 @@ aliases:
   - /influxdb/cloud/reference/release-notes/flux/
 ---
 
+## v0.165.0 [2022-04-25]
+
+### Features
+- Add support for options in the `testcase` extension.
+- Vectorize addition operations in `map()`.
+- Add location support to `date.truncate()`.
+- Accept string literals in properties of a record type.
+- Add trace option to the `flux` CLI.
+- Add `EquiJoinPredicateRule`.
+
+### Bug fixes
+- Update `map()` test case to include a range.
+- Don't set `BaseLocation.file` to `Some("")`.
+- Fix `strings.joinStr` panic when it receives a null value.
+- Remove 64bit misalignment.
+- Fix memory releases and add checked allocator to the end of tests.
+
+---
+
+## v0.164.1 [2022-04-18]
+
+### Bug fixes
+- Remove an extraneous `go generate` statement.
+
+---
+
+## v0.164.0 [2022-04-13]
+
+### Features
+- Allow Go to pass compilation options to Rust.
+
+### Bug fixes
+- Do not assume integers are 64bit integers.
+- Update `prometheus.scrape` type signature to correctly return a stream.
+
+---
+
+## v0.163.0 [2022-04-07]
+
+### Features
+- Report skipped tests.
+
+### Bug fixes
+- Update transformation transport adapter to always invoke `finish`.
+- Add support for "soft paragraphs" (paragraphs that contain single newline
+  characters) in inline Flux documentation.
+
+---
+
+## v0.162.0 [2022-04-05]
+
+### Features
+- Add [OpenTracing spans](https://opentracing.io/docs/overview/spans/) to the Flux runtime.
+- Add the `cffi` feature to reduce WASM binary size.
+- Replace the main `flux` CLI with a new `flux` CLI that starts a Flux REPL by
+  default or executes a Flux script via stdin.
+- Track freed memory with `SetFinalizer`.
+- Move [`addDuration()`](/flux/v0.x/stdlib/date/addduration/) and
+  [`subDuration()`](/flux/v0.x/stdlib/date/subduration/) from the `experimental`
+  package to the `date` package.
+
+### Bug fixes
+- Improve error messages for column conflicts in pivot operations.
+- Create OpenTracing spans for transformations using the proper context.
+- Add errors to OpenTracing spans created for transformations.
+- Restore required features hidden behind the `cffi` feature.
+
+---
+
+## v0.161.0 [2022-03-24]
+
+### Features
+- Re-enable the dialer pool and update dependency injection.
+
+### Bug fixes
+- Check length boundary for lower bound of [`strings.substring()`](/flux/v0.x/stdlib/strings/substring/).
+
+---
+
+## v0.160.0 [2022-03-22]
+
+### Features
+- Remove the `concurrencyLimit` feature flag and keep it in the dependencies.
+- Add MQTT Docker integration test.
+- Enable dialer pool.
+- Add an IOx-specific unpivot function to the `internal` package.
+
+### Bug fixes
+- Update [`join()`](/flux/v0.x/stdlib/universe/join/) to properly handle divergent schemas.
+- Fix line endings in the `testcase` format to prevent unnecessarily nesting the
+  body of a test case.
+- Make [`strings.substring()`](/flux/v0.x/stdlib/strings/substring/) check bounds correctly.
+- Fix duration and integer literal scanning.
+- Make `testcase` a semantic check instead of an error.
+- Skip parallel merge when selecting the result name based on side effects.
+- Add metadata headers to inline documentation.
+
+---
+
+## v0.159.0 [2022-03-14]
+
+### Features
+- Added a `finish` state to parallel-merge and always protect with a mutex lock.
+
+### Bug fixes
+- Use a fork of the `gosnowflake` library to prevent file transfers.
+- When encoding Flux types as JSON, encode dictionary types as JSON objects.
+- Upgrade Apache Arrow to v7.
+
+---
+
+## v0.158.0 [2022-03-09]
+
+### Features
+- Add inline documentation to the `universe` package.
+- Factor parallel execution into the concurrency quota calculation.
+
+### Bug fixes
+- Add parallel merges with no successors to the results set.
+- Correctly use range in an updated `map()` test.
+
+---
+
+## v0.157.0 [2022-03-03]
+
+### Features
+- Update `fill()` to use narrow transformation.
+- Add an attribute-based instantiation of parallel execution nodes.
+- Expose the `Record::fields` iterator.
+- Allow the `estimate_tdigest` method in `quantile()` to process any numeric value.
+- Optimize `aggregateWindow()` for specific aggregate transformations.
+
+### Bug fixes
+- Update vectorized `map()` to handle missing columns.
+- Remove duplicate line in `Makefile`.
+- Fix `cargo doc` build errors.
+- Reclassify CSV-decoding errors as user errors.
+- Update `iox.from()` and `generate.from()` to use proper stream annotation.
+
+---
+
+## v0.156.0 [2022-02-22]
+
+### Features
+- Add second pass to physical planner for parallelization rules.
+- Separate streams from arrays in the type system.
+- Add function to internal/debug to check feature flag values.
+- Allow feature flags to record metrics if configured.
+- Add extra verbose level to dump AST of test.
+- Explain what `[A], [A:B]` etc means in errors.
+
+### Bug fixes
+- Make `buckets()` function return a stream.
+- Remove unnecessary `TableObject` guards.
+- Copy `TagColumns` in `to()` that may get modified into the transformation.
+- Update tests to use explicit yields.
+
+---
+
+## v0.155.1 [2022-02-15]
+
+### Bug fixes
+- Update tests to use an explicit yield.
+
+---
+
+## v0.155.0 [2022-02-14]
+
+### Features
+- Add new [experimental array functions](/flux/v0.x/stdlib/experimental/array/)
+  for operating on arrays.
+
+### Bug fixes
+- Add `stop` parameter to [InfluxDB schema functions](/flux/v0.x/stdlib/influxdata/influxdb/schema/).
+- Remove `os.Exit` calls and allow `defer executor.Close` to run.
+- Properly handle time zone transitions when there is no daylight savings time
+  in the specified time zone.
+
+---
+
+## v0.154.0 [2022-02-09]
+
+### Features
+- Add [`requests.peek()`](/flux/v0.x/stdlib/experimental/http/requests/peek/) to
+  return HTTP response data in a table.
+- Add [`display()`](/flux/v0.x/stdlib/universe/display/) to represent any value as a string.
+- Create a version of `map()` that is columnar and supports vectorization.
+- Support vectorized functions.
+
+### Bug fixes
+- Add time vector to the `values` package.
+- Set the correct type for vectorized functions.
+
+---
+
+## v0.153.0 [2022-02-07]
+
+### Features
+- Connect language server protocol (LSP) features through the Flux crate.
+- Add conversion from `flux.Bounds` to `plan/execute.Bounds`.
+- Re-index all bound variables to start from 0.
+
+### Bug fixes
+- Int feature flags work properly when returned as floats.
+
+---
+
+## v0.152.0 [2022-01-31]
+
+### Features
+- Add the [`experimental/http/requests` package](/flux/v0.x/stdlib/experimental/http/requests/)
+  to support generic HTTP requests.
+- Add [`experimental/iox` package](/flux/v0.x/stdlib/experimental/iox/) and a
+  placeholder for the `iox.from()` function.
+- Add dependency hooks to the dependency subsystem.
+- Remove unneeded feature flags.
+
+### Bug fixes
+- Revert update to the dependencies package.
+- Return false if contains gets invalid value.
+
+---
+
+## v0.151.1 [2022-01-24]
+
+### Features
+- Update to Rust 1.58.1.
+
+---
+
+## v0.151.0 [2022-01-20]
+
+### Features
+- Expose `MonoType::parameter` and `MonoType::field`.
+
+### Bug fixes
+- Support writing unsigned integers with the `http` provider.
+
+---
+
+## v0.150.1 [2022-01-19]
+
+### Bug fixes
+- Remove duplicate `die` builtin in the `universe` package.
+
+---
+
+## v0.150.0 [2022-01-19]
+
+### Features
+- Update inline documentation in the following packages:
+  - date
+  - experimental
+  - testing
+  - timezone
+  - types
+
+### Bug fixes
+- Make iterating the hashmap deterministic.
+- Quote SQL identifiers to mitigate the risk of SQL injection.
+
+---
+
 ## v0.149.0 [2022-01-12]
 
 ### Features
diff --git a/content/flux/v0.x/spec/lexical-elements.md b/content/flux/v0.x/spec/lexical-elements.md
index 65c2630a5..be90705c1 100644
--- a/content/flux/v0.x/spec/lexical-elements.md
+++ b/content/flux/v0.x/spec/lexical-elements.md
@@ -144,6 +144,7 @@ decimals  = decimal_digit { decimal_digit } .
 
 A _duration literal_ is a representation of a length of time.
 It has an integer part and a duration unit part.
+The integer part must be a valid Flux integer and should not contain leading zeros.
 Multiple durations may be specified together and the resulting duration is the sum of each smaller part.
 When several durations are specified together, larger units must appear before smaller ones, and there can be no repeated units.
 
diff --git a/content/flux/v0.x/stdlib/array/_index.md b/content/flux/v0.x/stdlib/array/_index.md
index 781b633a8..67664fe54 100644
--- a/content/flux/v0.x/stdlib/array/_index.md
+++ b/content/flux/v0.x/stdlib/array/_index.md
@@ -9,7 +9,6 @@ aliases:
   - /influxdb/cloud/reference/flux/stdlib/experimental/array/
   - /influxdb/v2.0/reference/flux/stdlib/array/
   - /influxdb/cloud/reference/flux/stdlib/array/
-  - /flux/v0.x/stdlib/experimental/array/
 menu:
   flux_0_x_ref:
     name: array
diff --git a/content/flux/v0.x/stdlib/array/from.md b/content/flux/v0.x/stdlib/array/from.md
index ad442af6c..8d87e4bb9 100644
--- a/content/flux/v0.x/stdlib/array/from.md
+++ b/content/flux/v0.x/stdlib/array/from.md
@@ -25,11 +25,13 @@ All records must have the same keys and data types.
 ```js
 import "array"
 
-array.from(rows: [
-  {_time: 2020-01-01T00:00:00Z, _field: "exampleField", _value: 3, foo: "bar"},
-  {_time: 2020-01-01T00:01:00Z, _field: "exampleField", _value: 4, foo: "bar"},
-  {_time: 2020-01-01T00:02:00Z, _field: "exampleField", _value: 1, foo: "bar"}
-])
+array.from(
+    rows: [
+        {_time: 2020-01-01T00:00:00Z, _field: "exampleField", _value: 3, foo: "bar"},
+        {_time: 2020-01-01T00:01:00Z, _field: "exampleField", _value: 4, foo: "bar"},
+        {_time: 2020-01-01T00:02:00Z, _field: "exampleField", _value: 1, foo: "bar"},
+    ],
+)
 ```
 
 ## Parameters
@@ -43,10 +45,7 @@ Array of records to construct a table with.
 ```js
 import "array"
 
-rows = [
-  {foo: "bar", baz: 21.2},
-  {foo: "bar", baz: 23.8}
-]
+rows = [{foo: "bar", baz: 21.2}, {foo: "bar", baz: 23.8}]
 
 array.from(rows: rows)
 ```
@@ -56,12 +55,9 @@ array.from(rows: rows)
 import "influxdata/influxdb/v1"
 import "array"
 
-tags = v1.tagValues(
-  bucket: "example-bucket",
-  tag: "host"
-)
-
+tags = v1.tagValues(bucket: "example-bucket", tag: "host")
 wildcard_tag = array.from(rows: [{_value: "*"}])
 
 union(tables: [tags, wildcard_tag])
+
 ```
diff --git a/content/flux/v0.x/stdlib/contrib/bonitoo-io/alerta/alert.md b/content/flux/v0.x/stdlib/contrib/bonitoo-io/alerta/alert.md
index ec599402c..45132337f 100644
--- a/content/flux/v0.x/stdlib/contrib/bonitoo-io/alerta/alert.md
+++ b/content/flux/v0.x/stdlib/contrib/bonitoo-io/alerta/alert.md
@@ -19,21 +19,21 @@ The `alerta.alert()` function sends an alert to [Alerta](https://www.alerta.io/)
 import "contrib/bonitoo-io/alerta"
 
 alerta.alert(
-  url: "https://alerta.io:8080/alert",
-  apiKey: "0Xx00xxXx00Xxx0x0X",
-  resource: "example-resource",
-  event: "Example event",
-  environment: "",
-  severity: "critical",
-  service: [],
-  group: "",
-  value: "",
-  text: "",
-  tags: [],
-  attributes: {},
-  origin: "InfluxDB",
-  type: "",
-  timestamp: now(),
+    url: "https://alerta.io:8080/alert",
+    apiKey: "0Xx00xxXx00Xxx0x0X",
+    resource: "example-resource",
+    event: "Example event",
+    environment: "",
+    severity: "critical",
+    service: [],
+    group: "",
+    value: "",
+    text: "",
+    tags: [],
+    attributes: {},
+    origin: "InfluxDB",
+    type: "",
+    timestamp: now(),
 )
 ```
 
@@ -116,32 +116,29 @@ import "influxdata/influxdb/secrets"
 apiKey = secrets.get(key: "ALERTA_API_KEY")
 
 lastReported =
-  from(bucket: "example-bucket")
-    |> range(start: -1m)
-    |> filter(fn: (r) =>
-      r._measurement == "example-measurement" and
-      r._field == "level"
-    )
-    |> last()
-    |> findRecord(fn: (key) => true, idx: 0)
+    from(bucket: "example-bucket")
+        |> range(start: -1m)
+        |> filter(fn: (r) => r._measurement == "example-measurement" and r._field == "level")
+        |> last()
+        |> findRecord(fn: (key) => true, idx: 0)
 
 severity = if lastReported._value > 50 then "warning" else "ok"
 
 alerta.alert(
-  url: "https://alerta.io:8080/alert",
-  apiKey: apiKey,
-  resource: "example-resource",
-  event: "Example event",
-  environment: "Production",
-  severity: severity,
-  service: ["example-service"],
-  group: "example-group",
-  value: string(v: lastReported._value),
-  text: "Service is ${severity}. The last reported value was ${string(v: lastReported._value)}.",
-  tags: ["ex1", "ex2"],
-  attributes: {},
-  origin: "InfluxDB",
-  type: "exampleAlertType",
-  timestamp: now(),
+    url: "https://alerta.io:8080/alert",
+    apiKey: apiKey,
+    resource: "example-resource",
+    event: "Example event",
+    environment: "Production",
+    severity: severity,
+    service: ["example-service"],
+    group: "example-group",
+    value: string(v: lastReported._value),
+    text: "Service is ${severity}. The last reported value was ${string(v: lastReported._value)}.",
+    tags: ["ex1", "ex2"],
+    attributes: {},
+    origin: "InfluxDB",
+    type: "exampleAlertType",
+    timestamp: now(),
 )
 ```
diff --git a/content/flux/v0.x/stdlib/contrib/bonitoo-io/alerta/endpoint.md b/content/flux/v0.x/stdlib/contrib/bonitoo-io/alerta/endpoint.md
index 080b1f2d5..01ec85e8e 100644
--- a/content/flux/v0.x/stdlib/contrib/bonitoo-io/alerta/endpoint.md
+++ b/content/flux/v0.x/stdlib/contrib/bonitoo-io/alerta/endpoint.md
@@ -23,10 +23,10 @@ _**Function type:** Output_
 import "contrib/bonitoo-io/alerta"
 
 alerta.endpoint(
-  url: "https://alerta.io:8080/alert,
-  apiKey: "0Xx00xxXx00Xxx0x0X",
-  environment: "",
-  origin: "InfluxDB"
+    url: "https://alerta.io:8080/alert",
+    apiKey: "0Xx00xxXx00Xxx0x0X",
+    environment: "",
+    origin: "InfluxDB"
 )
 ```
 
@@ -87,31 +87,30 @@ import "contrib/bonitoo-io/alerta"
 import "influxdata/influxdb/secrets"
 
 apiKey = secrets.get(key: "ALERTA_API_KEY")
-endpoint = alerta.endpoint(
-  url: "https://alerta.io:8080/alert",
-  apiKey: apiKey,
-  environment: "Production",
-  origin: "InfluxDB"
-)
+endpoint =
+    alerta.endpoint(url: "https://alerta.io:8080/alert", apiKey: apiKey, environment: "Production", origin: "InfluxDB")
 
-crit_events = from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> filter(fn: (r) => r._measurement == "statuses" and status == "crit")
+crit_events =
+    from(bucket: "example-bucket")
+        |> range(start: -1m)
+        |> filter(fn: (r) => r._measurement == "statuses" and status == "crit")
 
 crit_events
-  |> endpoint(mapFn: (r) => {
-    return { r with
-      resource: "example-resource",
-      event: "example-event",
-      severity: "critical",
-      service: r.service,
-      group: "example-group",
-      value: r.status,
-      text: "Status is critical.",
-      tags: ["ex1", "ex2"],
-      attributes: {},
-      type: "exampleAlertType",
-      timestamp: now(),
-    }
-  })()
+    |> endpoint(
+        mapFn: (r) => {
+            return {r with
+                resource: "example-resource",
+                event: "example-event",
+                severity: "critical",
+                service: r.service,
+                group: "example-group",
+                value: r.status,
+                text: "Status is critical.",
+                tags: ["ex1", "ex2"],
+                attributes: {},
+                type: "exampleAlertType",
+                timestamp: now(),
+            }
+        },
+    )()
 ```
diff --git a/content/flux/v0.x/stdlib/contrib/bonitoo-io/hex/int.md b/content/flux/v0.x/stdlib/contrib/bonitoo-io/hex/int.md
index 446087173..0e82f9a03 100644
--- a/content/flux/v0.x/stdlib/contrib/bonitoo-io/hex/int.md
+++ b/content/flux/v0.x/stdlib/contrib/bonitoo-io/hex/int.md
@@ -51,11 +51,12 @@ _The following example uses data provided by the [`sampledata` package](/flux/v0
 ```js
 import "sampledata"
 
-data = sampledata.int()
-  |> map(fn: (r) => ({ r with _value: hex.string(v: r._value) }))
+data =
+    sampledata.int()
+        |> map(fn: (r) => ({r with _value: hex.string(v: r._value)}))
 
 data
-  |> map(fn:(r) => ({ r with _value: hex.int(v: r._value) }))
+    |> map(fn: (r) => ({r with _value: hex.int(v: r._value)}))
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/contrib/bonitoo-io/hex/string.md b/content/flux/v0.x/stdlib/contrib/bonitoo-io/hex/string.md
index 02d92ac3a..5a265d8c2 100644
--- a/content/flux/v0.x/stdlib/contrib/bonitoo-io/hex/string.md
+++ b/content/flux/v0.x/stdlib/contrib/bonitoo-io/hex/string.md
@@ -114,11 +114,12 @@ _The following example uses data provided by the [`sampledata` package](/flux/v0
 import "sampledata"
 import "contrib/bonitoo-io/hex"
 
-data = sampledata.int()
-  |> map(fn: (r) => ({ r with _value: r._value * 1000 }))
+data =
+    sampledata.int()
+        |> map(fn: (r) => ({r with _value: r._value * 1000}))
 
 data
-  |> map(fn:(r) => ({ r with _value: hex.string(v: r.foo) }))
+    |> map(fn: (r) => ({r with _value: hex.string(v: r.foo)}))
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/contrib/bonitoo-io/hex/uint.md b/content/flux/v0.x/stdlib/contrib/bonitoo-io/hex/uint.md
index 4cc90faf0..135f44530 100644
--- a/content/flux/v0.x/stdlib/contrib/bonitoo-io/hex/uint.md
+++ b/content/flux/v0.x/stdlib/contrib/bonitoo-io/hex/uint.md
@@ -49,13 +49,15 @@ hex.uint(v: "-d431")
 _The following example uses data provided by the [`sampledata` package](/flux/v0.x/stdlib/sampledata/)._
 
 ```js
+import "contrib/bonitoo-io/hex"
 import "sampledata"
 
-data = sampledata.uint()
-  |> map(fn: (r) => ({ r with _value: hex.string(v: r._value) }))
+data =
+    sampledata.uint()
+        |> map(fn: (r) => ({r with _value: hex.string(v: r._value)}))
 
 data
-  |> map(fn:(r) => ({ r with _value: hex.uint(v: r._value) }))
+    |> map(fn: (r) => ({r with _value: hex.uint(v: r._value)}))
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/contrib/bonitoo-io/servicenow/endpoint.md b/content/flux/v0.x/stdlib/contrib/bonitoo-io/servicenow/endpoint.md
index 0fadf90a1..46ca80942 100644
--- a/content/flux/v0.x/stdlib/contrib/bonitoo-io/servicenow/endpoint.md
+++ b/content/flux/v0.x/stdlib/contrib/bonitoo-io/servicenow/endpoint.md
@@ -71,24 +71,28 @@ import "influxdata/influxdb/secrets"
 username = secrets.get(key: "SERVICENOW_USERNAME")
 password = secrets.get(key: "SERVICENOW_PASSWORD")
 
-endpoint = servicenow.endpoint(
-    url: "https://example-tenant.service-now.com/api/global/em/jsonv2",
-    username: username,
-    password: password
-)
+endpoint =
+    servicenow.endpoint(
+        url: "https://example-tenant.service-now.com/api/global/em/jsonv2",
+        username: username,
+        password: password,
+    )
 
-crit_events = from(bucket: "example-bucket")
-    |> range(start: -1m)
-    |> filter(fn: (r) => r._measurement == "statuses" and status == "crit")
+crit_events =
+    from(bucket: "example-bucket")
+        |> range(start: -1m)
+        |> filter(fn: (r) => r._measurement == "statuses" and status == "crit")
 
 crit_events
-    |> endpoint(mapFn: (r) => ({
-        node: r.host,
-        metricType: r._measurement,
-        resource: r.instance,
-        metricName: r._field,
-        severity: "critical",
-        additionalInfo: { "devId": r.dev_id }
-      })
+    |> endpoint(
+        mapFn: (r) =>
+            ({
+                node: r.host,
+                metricType: r._measurement,
+                resource: r.instance,
+                metricName: r._field,
+                severity: "critical",
+                additionalInfo: {"devId": r.dev_id},
+            }),
     )()
 ```
diff --git a/content/flux/v0.x/stdlib/contrib/bonitoo-io/servicenow/event.md b/content/flux/v0.x/stdlib/contrib/bonitoo-io/servicenow/event.md
index fe7dc0361..60cd242c8 100644
--- a/content/flux/v0.x/stdlib/contrib/bonitoo-io/servicenow/event.md
+++ b/content/flux/v0.x/stdlib/contrib/bonitoo-io/servicenow/event.md
@@ -27,7 +27,7 @@ servicenow.event(
     resource: "",
     metricName: "",
     messageKey: "",
-    additionalInfo: {}
+    additionalInfo: {},
 )
 ```
 
@@ -103,11 +103,11 @@ username = secrets.get(key: "SERVICENOW_USERNAME")
 password = secrets.get(key: "SERVICENOW_PASSWORD")
 
 lastReported =
-  from(bucket: "example-bucket")
-    |> range(start: -1m)
-    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_idle")
-    |> last()
-    |> findRecord(fn: (key) => true, idx: 0)
+    from(bucket: "example-bucket")
+        |> range(start: -1m)
+        |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_idle")
+        |> last()
+        |> findRecord(fn: (key) => true, idx: 0)
 
 servicenow.event(
     url: "https://tenant.service-now.com/api/global/em/jsonv2",
@@ -118,9 +118,12 @@ servicenow.event(
     resource: lastReported.instance,
     metricName: lastReported._field,
     severity:
-        if lastReported._value < 1.0 then "critical"
-        else if lastReported._value < 5.0 then "warning"
-        else "info",
-    additionalInfo: {"devId": r.dev_id}
+        if lastReported._value < 1.0 then
+            "critical"
+        else if lastReported._value < 5.0 then
+            "warning"
+        else
+            "info",
+    additionalInfo: {"devId": r.dev_id},
 )
 ```
diff --git a/content/flux/v0.x/stdlib/contrib/bonitoo-io/tickscript/alert.md b/content/flux/v0.x/stdlib/contrib/bonitoo-io/tickscript/alert.md
index a533c5b40..370afa650 100644
--- a/content/flux/v0.x/stdlib/contrib/bonitoo-io/tickscript/alert.md
+++ b/content/flux/v0.x/stdlib/contrib/bonitoo-io/tickscript/alert.md
@@ -36,7 +36,7 @@ tickscript.alert(
     warn: (r) => false,
     info: (r) => false,
     ok: (r) => true,
-    topic: ""
+    topic: "",
 )
 ```
 
@@ -92,28 +92,24 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 [TICKscript](#)
 {{% /code-tabs %}}
 {{% code-tab-content %}}
-```javascript
+```js
 import "contrib/bonitoo-io/tickscript"
 
-option task = {name: "Example task", every: 1m;}
+option task = {name: "Example task", every: 1m}
 
-check = tickscript.defineCheck(
-  id: "000000000000",
-  name: "Errors",
-  type: "threshold"
-)
+check = tickscript.defineCheck(id: "000000000000", name: "Errors", type: "threshold")
 
 from(bucket: "example-bucket")
-  |> range(start: -task.every)
-  |> filter(fn: (r) => r._measurement == "errors" and r._field == "value")
-  |> count()
-  |> tickscript.alert(
-    check: {check with _check_id: "task/${r.service}"},
-    message: "task/${r.service} is ${r._level} value: ${r._value}",
-    crit: (r) => r._value > 30,
-    warn: (r) => r._value > 20,
-    info: (r) => r._value > 10    
-  )
+    |> range(start: -task.every)
+    |> filter(fn: (r) => r._measurement == "errors" and r._field == "value")
+    |> count()
+    |> tickscript.alert(
+        check: {check with _check_id: "task/${r.service}"},
+        message: "task/${r.service} is ${r._level} value: ${r._value}",
+        crit: (r) => r._value > 30,
+        warn: (r) => r._value > 20,
+        info: (r) => r._value > 10,
+    )
 ```
 {{% /code-tab-content %}}
 {{% code-tab-content %}}
diff --git a/content/flux/v0.x/stdlib/contrib/bonitoo-io/tickscript/compute.md b/content/flux/v0.x/stdlib/contrib/bonitoo-io/tickscript/compute.md
index 3586fe5d2..4635209c5 100644
--- a/content/flux/v0.x/stdlib/contrib/bonitoo-io/tickscript/compute.md
+++ b/content/flux/v0.x/stdlib/contrib/bonitoo-io/tickscript/compute.md
@@ -26,9 +26,9 @@ that changes a column's name and optionally applies an aggregate or selector fun
 import "contrib/bonitoo-io/tickscript"
 
 tickscript.compute(
-  column: "_value",
-  fn: sum,
-  as: "example-name"
+    column: "_value",
+    fn: sum,
+    as: "example-name",
 )
 ```
 
diff --git a/content/flux/v0.x/stdlib/contrib/bonitoo-io/tickscript/deadman.md b/content/flux/v0.x/stdlib/contrib/bonitoo-io/tickscript/deadman.md
index bcffa61ca..d0547910e 100644
--- a/content/flux/v0.x/stdlib/contrib/bonitoo-io/tickscript/deadman.md
+++ b/content/flux/v0.x/stdlib/contrib/bonitoo-io/tickscript/deadman.md
@@ -28,12 +28,12 @@ _This function is comparable to the [Kapacitor AlertNode deadman](/{{< latest "k
 import "contrib/bonitoo-io/tickscript"
 
 tickscript.deadman(
-  check: {},
-  measurement: "example-measurement",
-  threshold: 0,
-  id: (r)=>"${r._check_id}",
-  message: (r) => "Deadman Check: ${r._check_name} is: " + (if r.dead then "dead" else "alive"),
-  topic: ""
+    check: {},
+    measurement: "example-measurement",
+    threshold: 0,
+    id: (r) => "${r._check_id}",
+    message: (r) => "Deadman Check: ${r._check_name} is: " + (if r.dead then "dead" else "alive"),
+    topic: "",
 )
 ```
 
@@ -82,16 +82,16 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 ```javascript
 import "contrib/bonitoo-io/tickscript"
 
-option task = {name: "Example task", every: 1m;}
+option task = {name: "Example task", every: 1m}
 
 from(bucket: "example-bucket")
-  |> range(start: -task.every)
-  |> filter(fn: (r) => r._measurement == "pulse" and r._field == "value")
-  |> tickscript.deadman(
-    check: tickscript.defineCheck(id: "000000000000", name: "task/${r.service}"),
-    measurement: "pulse",
-    threshold: 2
-  )
+    |> range(start: -task.every)
+    |> filter(fn: (r) => r._measurement == "pulse" and r._field == "value")
+    |> tickscript.deadman(
+        check: tickscript.defineCheck(id: "000000000000", name: "task/${r.service}"),
+        measurement: "pulse",
+        threshold: 2,
+    )
 ```
 {{% /code-tab-content %}}
 {{% code-tab-content %}}
diff --git a/content/flux/v0.x/stdlib/contrib/bonitoo-io/tickscript/definecheck.md b/content/flux/v0.x/stdlib/contrib/bonitoo-io/tickscript/definecheck.md
index 48b23e83a..3c4ca35e3 100644
--- a/content/flux/v0.x/stdlib/contrib/bonitoo-io/tickscript/definecheck.md
+++ b/content/flux/v0.x/stdlib/contrib/bonitoo-io/tickscript/definecheck.md
@@ -23,9 +23,9 @@ This check data specifies information about the check in the InfluxDB monitoring
 import "contrib/bonitoo-io/tickscript"
 
 tickscript.defineCheck(
-  id: "000000000000",
-  name: "Example check name",
-  type: "custom"
+    id: "000000000000",
+    name: "Example check name",
+    type: "custom",
 )
 ```
 
@@ -55,10 +55,7 @@ Default is `custom`.
 ```javascript
 import "contrib/bonitoo-io/tickscript"
 
-tickscript.defineCheck(
-  id: "000000000000",
-  name: "Example check name",
-)
+tickscript.defineCheck(id: "000000000000", name: "Example check name")
 
 // The function above returns: {
 //   _check_id: "000000000000",
diff --git a/content/flux/v0.x/stdlib/contrib/bonitoo-io/tickscript/groupby.md b/content/flux/v0.x/stdlib/contrib/bonitoo-io/tickscript/groupby.md
index 44f256092..791e6e553 100644
--- a/content/flux/v0.x/stdlib/contrib/bonitoo-io/tickscript/groupby.md
+++ b/content/flux/v0.x/stdlib/contrib/bonitoo-io/tickscript/groupby.md
@@ -29,9 +29,7 @@ or [`tickscript.selectWindow()`](/flux/v0.x/stdlib/contrib/bonitoo-io/tickscript
 ```js
 import "contrib/bonitoo-io/tickscript"
 
-tickscript.groupBy(
-  columns: ["exampleColumn"]
-)
+tickscript.groupBy(columns: ["exampleColumn"])
 ```
 
 ## Parameters
@@ -51,7 +49,5 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "contrib/bonitoo-io/tickscript"
 
 data
-  |> tickscript.groupBy(
-    columns: ["host", "region"]
-  )
+    |> tickscript.groupBy(columns: ["host", "region"])
 ```
diff --git a/content/flux/v0.x/stdlib/contrib/bonitoo-io/tickscript/join.md b/content/flux/v0.x/stdlib/contrib/bonitoo-io/tickscript/join.md
index a81e2bc2f..1977c59c9 100644
--- a/content/flux/v0.x/stdlib/contrib/bonitoo-io/tickscript/join.md
+++ b/content/flux/v0.x/stdlib/contrib/bonitoo-io/tickscript/join.md
@@ -26,9 +26,9 @@ _This function is comparable to the [Kapacitor JoinNode](/{{< latest "kapacitor"
 import "contrib/bonitoo-io/tickscript"
 
 tickscript.join(
-  tables: {t1: example1, t2: example2}
-  on: ["_time"],
-  measurement: "example-measurement"
+    tables: {t1: example1, t2: example2},
+    on: ["_time"],
+    measurement: "example-measurement",
 )
 ```
 
@@ -91,9 +91,9 @@ metrics = //...
 states = //...
 
 tickscript.join(
-  tables: {metric: metrics, state: states},
-  on: ["_time", "host"],
-  measurement: "example-m"
+    tables: {metric: metrics, state: states},
+    on: ["_time", "host"],
+    measurement: "example-m",
 )
 ```
 
diff --git a/content/flux/v0.x/stdlib/contrib/bonitoo-io/tickscript/select.md b/content/flux/v0.x/stdlib/contrib/bonitoo-io/tickscript/select.md
index 19bc145cd..f1a8af1b4 100644
--- a/content/flux/v0.x/stdlib/contrib/bonitoo-io/tickscript/select.md
+++ b/content/flux/v0.x/stdlib/contrib/bonitoo-io/tickscript/select.md
@@ -25,9 +25,9 @@ an aggregate or selector function to values in the column.
 import "contrib/bonitoo-io/tickscript"
 
 tickscript.select(
-  column: "_value",
-  fn: sum,
-  as: "example-name"
+    column: "_value",
+    fn: sum,
+    as: "example-name",
 )
 ```
 
@@ -74,7 +74,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "contrib/bonitoo-io/tickscript"
 
 data
-  |> tickscript.select(as: "example-name")
+    |> tickscript.select(as: "example-name")
 ```
 
 {{< flex >}}
@@ -103,10 +103,7 @@ data
 import "contrib/bonitoo-io/tickscript"
 
 data
-  |> tickscript.select(
-    as: "sum",
-    fn: sum
-  )
+    |> tickscript.select(as: "sum", fn: sum)
 ```
 
 {{< flex >}}
@@ -133,10 +130,7 @@ data
 import "contrib/bonitoo-io/tickscript"
 
 data
-  |> tickscript.select(
-    as: "max",
-    fn: max
-  )
+    |> tickscript.select(as: "max", fn: max)
 ```
 
 {{< flex >}}
diff --git a/content/flux/v0.x/stdlib/contrib/bonitoo-io/tickscript/selectwindow.md b/content/flux/v0.x/stdlib/contrib/bonitoo-io/tickscript/selectwindow.md
index 5f4606800..0587fc1da 100644
--- a/content/flux/v0.x/stdlib/contrib/bonitoo-io/tickscript/selectwindow.md
+++ b/content/flux/v0.x/stdlib/contrib/bonitoo-io/tickscript/selectwindow.md
@@ -25,11 +25,11 @@ and applies an aggregate or selector function the specified column for each wind
 import "contrib/bonitoo-io/tickscript"
 
 tickscript.selectWindow(
-  column: "_value",
-  fn: sum,
-  as: "example-name",
-  every: 1m,
-  defaultValue: 0.0,
+    column: "_value",
+    fn: sum,
+    as: "example-name",
+    every: 1m,
+    defaultValue: 0.0,
 )
 ```
 
@@ -81,12 +81,12 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "contrib/bonitoo-io/tickscript"
 
 data
-  |> tickscript.selectWindow(
-    fn: sum,
-    as: "example-name",
-    every: 1h,
-    defaultValue: 0.0
-  )
+    |> tickscript.selectWindow(
+        fn: sum,
+        as: "example-name",
+        every: 1h,
+        defaultValue: 0.0,
+    )
 ```
 
 {{< flex >}}
diff --git a/content/flux/v0.x/stdlib/contrib/bonitoo-io/victorops/alert.md b/content/flux/v0.x/stdlib/contrib/bonitoo-io/victorops/alert.md
index 6bc3e1380..a5cbf0dcd 100644
--- a/content/flux/v0.x/stdlib/contrib/bonitoo-io/victorops/alert.md
+++ b/content/flux/v0.x/stdlib/contrib/bonitoo-io/victorops/alert.md
@@ -26,13 +26,13 @@ Splunk acquired VictorOps and VictorOps is now
 import "contrib/bonitoo-io/victorops"
 
 victorops.alert(
-  url: "https://alert.victorops.com/integrations/generic/00000000/alert/${api_key}/${routing_key}",
-  monitoringTool: "",
-  messageType: "CRITICAL",
-  entityID: "",
-  entityDisplayName: "",
-  stateMessage: "",
-  timestamp: now()
+    url: "https://alert.victorops.com/integrations/generic/00000000/alert/${api_key}/${routing_key}",
+    monitoringTool: "",
+    messageType: "CRITICAL",
+    entityID: "",
+    entityDisplayName: "",
+    stateMessage: "",
+    timestamp: now(),
 )
 ```
 
@@ -91,20 +91,23 @@ apiKey = secrets.get(key: "VICTOROPS_API_KEY")
 routingKey = secrets.get(key: "VICTOROPS_ROUTING_KEY")
 
 lastReported =
-  from(bucket: "example-bucket")
-    |> range(start: -1m)
-    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_idle")
-    |> last()
-    |> findRecord(fn: (key) => true, idx: 0)
+    from(bucket: "example-bucket")
+        |> range(start: -1m)
+        |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_idle")
+        |> last()
+        |> findRecord(fn: (key) => true, idx: 0)
 
 victorops.alert(
-  url: "https://alert.victorops.com/integrations/generic/00000000/alert/${apiKey}/${routingKey}",
-  messageType:
-    if lastReported._value < 1.0 then "CRITICAL"
-    else if lastReported._value < 5.0 then "WARNING"
-    else "INFO",
-  entityID: "example-alert-1",
-  entityDisplayName: "Example Alert 1",
-  stateMessage: "Last reported cpu_idle was ${string(v: r._value)}."
+    url: "https://alert.victorops.com/integrations/generic/00000000/alert/${apiKey}/${routingKey}",
+    messageType:
+        if lastReported._value < 1.0 then
+            "CRITICAL"
+        else if lastReported._value < 5.0 then
+            "WARNING"
+        else
+            "INFO",
+    entityID: "example-alert-1",
+    entityDisplayName: "Example Alert 1",
+    stateMessage: "Last reported cpu_idle was ${string(v: r._value)}.",
 )
 ```
diff --git a/content/flux/v0.x/stdlib/contrib/bonitoo-io/victorops/endpoint.md b/content/flux/v0.x/stdlib/contrib/bonitoo-io/victorops/endpoint.md
index c9edc2ae4..7b139b8e2 100644
--- a/content/flux/v0.x/stdlib/contrib/bonitoo-io/victorops/endpoint.md
+++ b/content/flux/v0.x/stdlib/contrib/bonitoo-io/victorops/endpoint.md
@@ -26,7 +26,7 @@ Splunk acquired VictorOps and VictorOps is now
 import "contrib/bonitoo-io/victorops"
 
 victorops.endpoint(
-  url: "https://alert.victorops.com/integrations/generic/00000000/alert${apiKey}/${routingKey}",
+    url: "https://alert.victorops.com/integrations/generic/00000000/alert${apiKey}/${routingKey}",
 )
 ```
 
@@ -75,18 +75,21 @@ routingKey = secrets.get(key: "VICTOROPS_ROUTING_KEY")
 url = "https://alert.victorops.com/integrations/generic/00000000/alert/${apiKey}/${routingKey}"
 endpoint = victorops.endpoint(url: url)
 
-crit_events = from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> filter(fn: (r) => r._measurement == "statuses" and status == "crit")
+crit_events =
+    from(bucket: "example-bucket")
+        |> range(start: -1m)
+        |> filter(fn: (r) => r._measurement == "statuses" and status == "crit")
 
 crit_events
-  |> endpoint(mapFn: (r) => ({
-      monitoringTool: "InfluxDB"
-      messageType: "CRITICAL",
-      entityID: "${r.host}-${r._field)-critical",
-      entityDisplayName: "Critical alert for ${r.host}",
-      stateMessage: "${r.host} is in a critical state. ${r._field} is ${string(v: r._value)}.",
-      timestamp: now()
-    })
-  )()
+    |> endpoint(
+        mapFn: (r) =>
+            ({
+                monitoringTool: "InfluxDB",
+                messageType: "CRITICAL",
+                entityID: "${r.host}-${r._field}-critical",
+                entityDisplayName: "Critical alert for ${r.host}",
+                stateMessage: "${r.host} is in a critical state. ${r._field} is ${string(v: r._value)}.",
+                timestamp: now(),
+            }),
+    )()
 ```
diff --git a/content/flux/v0.x/stdlib/contrib/bonitoo-io/zenoss/endpoint.md b/content/flux/v0.x/stdlib/contrib/bonitoo-io/zenoss/endpoint.md
index aa02b0a9d..a893d368e 100644
--- a/content/flux/v0.x/stdlib/contrib/bonitoo-io/zenoss/endpoint.md
+++ b/content/flux/v0.x/stdlib/contrib/bonitoo-io/zenoss/endpoint.md
@@ -20,13 +20,13 @@ The `zenoss.endpoint()` function sends events to Zenoss using data from input ro
 import "contrib/bonitoo-io/zenoss"
 
 zenoss.endpoint(
-  url: "https://example.zenoss.io:8080/zport/dmd/evconsole_router",
-  username: "example-user",
-  password: "example-password",
-  action: "EventsRouter",
-  method: "add_event",
-  type: "rpc",
-  tid: 1
+    url: "https://example.zenoss.io:8080/zport/dmd/evconsole_router",
+    username: "example-user",
+    password: "example-password",
+    action: "EventsRouter",
+    method: "add_event",
+    type: "rpc",
+    tid: 1,
 )
 ```
 
@@ -94,26 +94,25 @@ import "influxdata/influxdb/secrets"
 url = "https://tenant.zenoss.io:8080/zport/dmd/evconsole_router"
 username = secrets.get(key: "ZENOSS_USERNAME")
 password = secrets.get(key: "ZENOSS_PASSWORD")
-endpoint = zenoss.endpoint(
-  url: url,
-  username: username,
-  password: password
-)
+endpoint = zenoss.endpoint(url: url, username: username, password: password)
 
-crit_events = from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> filter(fn: (r) => r._measurement == "statuses" and status == "crit")
+crit_events =
+    from(bucket: "example-bucket")
+        |> range(start: -1m)
+        |> filter(fn: (r) => r._measurement == "statuses" and status == "crit")
 
 crit_events
-  |> endpoint(mapFn: (r) => ({
-      summary: "Critical event for ${r.host}",
-      device: r.deviceID,
-      component: r.host,
-      severity: "Critical",
-      eventClass: "/App",
-      eventClassKey: "",
-      collector: "",
-      message: "${r.host} is in a critical state.",
-    })
-  )()
+    |> endpoint(
+        mapFn: (r) =>
+            ({
+                summary: "Critical event for ${r.host}",
+                device: r.deviceID,
+                component: r.host,
+                severity: "Critical",
+                eventClass: "/App",
+                eventClassKey: "",
+                collector: "",
+                message: "${r.host} is in a critical state.",
+            }),
+    )()
 ```
diff --git a/content/flux/v0.x/stdlib/contrib/bonitoo-io/zenoss/event.md b/content/flux/v0.x/stdlib/contrib/bonitoo-io/zenoss/event.md
index 1b7aacddd..4ca055cdc 100644
--- a/content/flux/v0.x/stdlib/contrib/bonitoo-io/zenoss/event.md
+++ b/content/flux/v0.x/stdlib/contrib/bonitoo-io/zenoss/event.md
@@ -19,21 +19,21 @@ The `zenoss.event()` function sends an event to [Zenoss](https://www.zenoss.com/
 import "contrib/bonitoo-io/zenoss"
 
 zenoss.event(
-  url: "https://example.zenoss.io:8080/zport/dmd/evconsole_router",
-  username: "example-user",
-  password: "example-password",
-  action: "EventsRouter",
-  method: "add_event",
-  type: "rpc",
-  tid: 1,
-  summary: "",
-  device: "",
-  component: "",
-  severity: "Critical",
-  eventClass: "",
-  eventClassKey: "",
-  collector: "",
-  message: ""
+    url: "https://example.zenoss.io:8080/zport/dmd/evconsole_router",
+    username: "example-user",
+    password: "example-password",
+    action: "EventsRouter",
+    method: "add_event",
+    type: "rpc",
+    tid: 1,
+    summary: "",
+    device: "",
+    component: "",
+    severity: "Critical",
+    eventClass: "",
+    eventClassKey: "",
+    collector: "",
+    message: "",
 )
 ```
 
@@ -119,11 +119,11 @@ username = secrets.get(key: "ZENOSS_USERNAME")
 password = secrets.get(key: "ZENOSS_PASSWORD")
 
 lastReported =
-  from(bucket: "example-bucket")
-    |> range(start: -1m)
-    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_idle")
-    |> last()
-    |> findRecord(fn: (key) => true, idx: 0)
+    from(bucket: "example-bucket")
+        |> range(start: -1m)
+        |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_idle")
+        |> last()
+        |> findRecord(fn: (key) => true, idx: 0)
 
 zenoss.event(
     url: "https://tenant.zenoss.io:8080/zport/dmd/evconsole_router",
@@ -133,9 +133,13 @@ zenoss.event(
     component: "CPU",
     eventClass: "/App",
     severity:
-      if lastReported._value < 1.0 then "Critical"
-      else if lastReported._value < 5.0 then "Warning"
-      else if lastReported._value < 20.0 then "Info"
-      else "Clear"
+        if lastReported._value < 1.0 then
+            "Critical"
+        else if lastReported._value < 5.0 then
+            "Warning"
+        else if lastReported._value < 20.0 then
+            "Info"
+        else
+            "Clear",
 )
 ```
diff --git a/content/flux/v0.x/stdlib/contrib/chobbs/discord/endpoint.md b/content/flux/v0.x/stdlib/contrib/chobbs/discord/endpoint.md
index fbd6de869..e970fd856 100644
--- a/content/flux/v0.x/stdlib/contrib/chobbs/discord/endpoint.md
+++ b/content/flux/v0.x/stdlib/contrib/chobbs/discord/endpoint.md
@@ -24,10 +24,10 @@ and data from table rows.
 import "contrib/chobbs/discord"
 
 discord.endpoint(
-  webhookToken: "mySuPerSecRetTokEn",
-  webhookID: "123456789",
-  username: "username",
-  avatar_url: "https://example.com/avatar_pic.jpg"
+    webhookToken: "mySuPerSecRetTokEn",
+    webhookID: "123456789",
+    username: "username",
+    avatar_url: "https://example.com/avatar_pic.jpg",
 )
 ```
 
@@ -68,19 +68,13 @@ import "influxdata/influxdb/secrets"
 import "contrib/chobbs/discord"
 
 discordToken = secrets.get(key: "DISCORD_TOKEN")
-endpoint = telegram.endpoint(
-  webhookToken: discordToken,
-  webhookID: "123456789",
-  username: "critBot"
-)
+endpoint = telegram.endpoint(webhookToken: discordToken, webhookID: "123456789", username: "critBot")
 
-crit_statuses = from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> filter(fn: (r) => r._measurement == "statuses" and status == "crit")
+crit_statuses =
+    from(bucket: "example-bucket")
+        |> range(start: -1m)
+        |> filter(fn: (r) => r._measurement == "statuses" and status == "crit")
 
 crit_statuses
-  |> endpoint(mapFn: (r) => ({
-      content: "The status is critical!",
-    })
-  )()
+    |> endpoint(mapFn: (r) => ({content: "The status is critical!"}))()
 ```
diff --git a/content/flux/v0.x/stdlib/contrib/chobbs/discord/send.md b/content/flux/v0.x/stdlib/contrib/chobbs/discord/send.md
index f302cd3e5..1df4846d7 100644
--- a/content/flux/v0.x/stdlib/contrib/chobbs/discord/send.md
+++ b/content/flux/v0.x/stdlib/contrib/chobbs/discord/send.md
@@ -21,11 +21,11 @@ a [Discord webhook](https://support.discord.com/hc/en-us/articles/228383668-Intr
 import "contrib/chobbs/discord"
 
 discord.send(
-  webhookToken: "mySuPerSecRetTokEn",
-  webhookID: "123456789",
-  username: "username",
-  content: "This is an example message",
-  avatar_url: "https://example.com/avatar_pic.jpg"
+    webhookToken: "mySuPerSecRetTokEn",
+    webhookID: "123456789",
+    username: "username",
+    content: "This is an example message",
+    avatar_url: "https://example.com/avatar_pic.jpg",
 )
 ```
 
@@ -50,24 +50,23 @@ Override the Discord webhook's default avatar.
 
 ##### Send the last reported status to Discord
 ```js
-import "contrib/chobbs/discord"
 import "influxdata/influxdb/secrets"
 
 token = secrets.get(key: "DISCORD_TOKEN")
 
 lastReported =
-  from(bucket: "example-bucket")
-    |> range(start: -1m)
-    |> filter(fn: (r) => r._measurement == "statuses")
-    |> last()
-    |> findRecord(fn: (key) => true, idx: 0)
+    from(bucket: "example-bucket")
+        |> range(start: -1m)
+        |> filter(fn: (r) => r._measurement == "statuses")
+        |> last()
+        |> findRecord(fn: (key) => true, idx: 0)
 
 discord.send(
-  webhookToken:token,
-  webhookID: "1234567890",
-  username: "chobbs",
-  content: "The current status is \"${lastReported.status}\".",
-  avatar_url: "https://staff-photos.net/pic.jpg"
+    webhookToken: token,
+    webhookID: "1234567890",
+    username: "chobbs",
+    content: "The current status is \"${lastReported.status}\".",
+    avatar_url: "https://staff-photos.net/pic.jpg",
 )
 ```
 
diff --git a/content/flux/v0.x/stdlib/contrib/jsternberg/influxdb/select.md b/content/flux/v0.x/stdlib/contrib/jsternberg/influxdb/select.md
index 36bf6b4c1..9d5f7b754 100644
--- a/content/flux/v0.x/stdlib/contrib/jsternberg/influxdb/select.md
+++ b/content/flux/v0.x/stdlib/contrib/jsternberg/influxdb/select.md
@@ -30,15 +30,15 @@ Results are similar to those returned by InfluxQL `SELECT` statements.
 import "contrib/jsternberg/influxdb"
 
 influxdb.select(
-  from: "example-bucket",
-  start: -1d,
-  stop: now(),
-  m: "example-measurement",
-  fields: [],
-  where: (r) => true,
-  host: "https://example.com",
-  org: "example-org",
-  token: "MySuP3rSecr3Tt0k3n"
+    from: "example-bucket",
+    start: -1d,
+    stop: now(),
+    m: "example-measurement",
+    fields: [],
+    where: (r) => true,
+    host: "https://example.com",
+    org: "example-org",
+    token: "MySuP3rSecr3Tt0k3n",
 )
 ```
 
@@ -109,24 +109,14 @@ InfluxDB [API token](/{{< latest "influxdb" >}}/security/tokens/).
 ```js
 import "contrib/jsternberg/influxdb"
 
-influxdb.select(
-  from: "example-bucket",
-  start: -1d,
-  m: "example-measurement",
-  fields: ["field1"]
-)
+influxdb.select(from: "example-bucket", start: -1d, m: "example-measurement", fields: ["field1"])
 ```
 
 ##### Query multiple fields
 ```js
 import "contrib/jsternberg/influxdb"
 
-influxdb.select(
-  from: "example-bucket",
-  start: -1d,
-  m: "example-measurement",
-  fields: ["field1", "field2", "field3"]
-)
+influxdb.select(from: "example-bucket", start: -1d, m: "example-measurement", fields: ["field1", "field2", "field3"])
 ```
 
 ##### Query all fields and filter by tags
@@ -134,10 +124,10 @@ influxdb.select(
 import "contrib/jsternberg/influxdb"
 
 influxdb.select(
-  from: "example-bucket",
-  start: -1d,
-  m: "example-measurement",
-  where: (r) => r.host == "host1" and r.region == "us-west"
+    from: "example-bucket",
+    start: -1d,
+    m: "example-measurement",
+    where: (r) => r.host == "host1" and r.region == "us-west",
 )
 ```
 
@@ -149,12 +139,12 @@ import "influxdata/influxdb/secrets"
 token = secrets.get(key: "INFLUXDB_CLOUD_TOKEN")
 
 influxdb.select(
-  from: "example-bucket",
-  start: -1d,
-  m: "example-measurement",
-  fields: ["field1", "field2"],
-  host: "https://cloud2.influxdata.com",
-  org: "example-org",
-  token: token
+    from: "example-bucket",
+    start: -1d,
+    m: "example-measurement",
+    fields: ["field1", "field2"],
+    host: "https://cloud2.influxdata.com",
+    org: "example-org",
+    token: token,
 )
 ```
diff --git a/content/flux/v0.x/stdlib/contrib/jsternberg/rows/_index.md b/content/flux/v0.x/stdlib/contrib/jsternberg/rows/_index.md
deleted file mode 100644
index 1dea372bf..000000000
--- a/content/flux/v0.x/stdlib/contrib/jsternberg/rows/_index.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: Flux rows package
-list_title: rows package
-description: >
-  The Flux `rows` package provides additional functions for remapping values in rows.
-  Import the `contrib/jsternberg/rows` package.
-aliases:
-  - /influxdb/v2.0/reference/flux/stdlib/contrib/rows/
-  - /influxdb/cloud/reference/flux/stdlib/contrib/rows/
-menu:
-  flux_0_x_ref:
-    name: rows
-    parent: jsternberg
-weight: 201
-flux/v0.x/tags: [functions, package]
-introduced: 0.77.0
----
-
-The Flux `rows` package provides additional functions for remapping values in rows.
-Import the `contrib/jsternberg/rows` package:
-
-```js
-import "contrib/jsternberg/rows"
-```
-
-{{< children type="functions" show="pages" >}}
diff --git a/content/flux/v0.x/stdlib/contrib/jsternberg/rows/map.md b/content/flux/v0.x/stdlib/contrib/jsternberg/rows/map.md
deleted file mode 100644
index 9751d8a9e..000000000
--- a/content/flux/v0.x/stdlib/contrib/jsternberg/rows/map.md
+++ /dev/null
@@ -1,224 +0,0 @@
----
-title: rows.map() function
-description: >
-  The `rows.map()` function is an alternate implementation of [`map()`](/flux/v0.x/stdlib/universe/map/)
-  that is faster, but more limited than `map()`.
-aliases:
-  - /influxdb/v2.0/reference/flux/stdlib/contrib/rows/map/
-  - /influxdb/cloud/reference/flux/stdlib/contrib/rows/map/
-menu:
-  flux_0_x_ref:
-    name: rows.map
-    parent: rows
-weight: 301
-flux/v0.x/tags: [transformations]
-related:
-  - /flux/v0.x/stdlib/universe/map/
-introduced: 0.77.0
----
-
-The `rows.map()` function is an alternate implementation of [`map()`](/flux/v0.x/stdlib/universe/map/)
-that is faster, but more limited than `map()`.
-`rows.map()` cannot modify [groups keys](/flux/v0.x/get-started/data-model/#group-key) and,
-therefore, does not need to regroup tables.
-**Attempts to change columns in the group key are ignored.**
-
-
-```js
-import "contrib/jsternberg/rows"
-
-rows.map( fn: (r) => ({_value: r._value * 100.0}))
-```
-
-## Parameters
-
-### fn {data-type="function"}
-
-A single argument function to apply to each record.
-The return value must be a record.
-
-{{% note %}}
-Use the `with` operator to preserve columns **not** in the group and **not**
-explicitly mapped in the operation.
-{{% /note %}}
-
-### tables {data-type="stream of tables"}
-Input data.
-Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressions)).
-
-## Examples
-
-- [Perform mathemtical operations on column values](#perform-mathemtical-operations-on-column-values)
-- [Preserve all columns in the operation](#preserve-all-columns-in-the-operation)
-- [Attempt to remap columns in the group key](#attempt-to-remap-columns-in-the-group-key)
-
----
-
-### Perform mathemtical operations on column values
-The following example returns the square of each value in the `_value` column:
-
-```js
-import "contrib/jsternberg/rows"
-
-data
-  |> rows.map(fn: (r) => ({ _value: r._value * r._value }))
-```
-
-{{% note %}}
-#### Important notes
-The `_time` column is dropped because:
-
-- It's not in the group key.
-- It's not explicitly mapped in the operation.
-- The `with` operator was not used to include existing columns.
-{{% /note %}}
-
-{{< flex >}}
-{{% flex-content %}}
-#### Input tables
-
-**Group key:** `tag,_field`
-
-| tag  | _field | _time | _value |
-| ---  |:------ |:----- | ------:|
-| tag1 | foo    | 0001  | 1.9    |
-| tag1 | foo    | 0002  | 2.4    |
-| tag1 | foo    | 0003  | 2.1    |
-
-| tag  | _field | _time | _value |
-|:---  |:------ |:----- | ------:|
-| tag2 | bar    | 0001  | 3.1    |
-| tag2 | bar    | 0002  | 3.8    |
-| tag2 | bar    | 0003  | 1.7    |
-{{% /flex-content %}}
-
-{{% flex-content %}}
-#### Output tables
-
-**Group key:** `tag,_field`
-
-| tag  | _field | _value |
-| ---  |:------ | ------:|
-| tag1 | foo    | 3.61   |
-| tag1 | foo    | 5.76   |
-| tag1 | foo    | 4.41   |
-
-| tag  | _field | _value |
-|:---  |:------ | ------:|
-| tag2 | bar    | 9.61   |
-| tag2 | bar    | 14.44  |
-| tag2 | bar    | 2.89   |
-{{% /flex-content %}}
-{{< /flex >}}
-
----
-
-### Preserve all columns in the operation
-Use the `with` operator in your mapping operation to preserve all columns,
-including those not in the group key, without explicitly remapping them.
-
-```js
-import "contrib/jsternberg/rows"
-
-data
-  |> rows.map(fn: (r) => ({ r with _value: r._value * r._value }))
-```
-
-{{% note %}}
-#### Important notes
-- The mapping operation remaps the `_value` column.
-- The `with` operator preserves all other columns not in the group key (`_time`).
-{{% /note %}}
-
-{{< flex >}}
-{{% flex-content %}}
-#### Input tables
-
-**Group key:** `tag,_field`
-
-| tag  | _field | _time | _value |
-|:---  |:------ |:----- | ------:|
-| tag1 | foo    | 0001  | 1.9    |
-| tag1 | foo    | 0002  | 2.4    |
-| tag1 | foo    | 0003  | 2.1    |
-
-| tag  | _field | _time | _value |
-| ---  |:------ |:----- | ------:|
-| tag2 | bar    | 0001  | 3.1    |
-| tag2 | bar    | 0002  | 3.8    |
-| tag2 | bar    | 0003  | 1.7    |
-{{% /flex-content %}}
-
-{{% flex-content %}}
-#### Output tables
-
-**Group key:** `tag,_field`
-
-| tag  | _field | _time | _value |
-|:---  |:------ |:----- | ------:|
-| tag1 | foo    | 0001  | 3.61   |
-| tag1 | foo    | 0002  | 5.76   |
-| tag1 | foo    | 0003  | 4.41   |
-
-| tag  | _field | _time | _value |
-| ---  |:------ |:----- | ------:|
-| tag2 | bar    | 0001  | 9.61   |
-| tag2 | bar    | 0002  | 14.44  |
-| tag2 | bar    | 0003  | 2.89   |
-{{% /flex-content %}}
-{{< /flex >}}
-
----
-
-### Attempt to remap columns in the group key
-
-```js
-import "contrib/jsternberg/rows"
-
-data
-  |> rows.map(fn: (r) => ({ r with tag: "tag3" }))
-```
-
-{{% note %}}
-#### Important notes
-- Remapping the `tag` column to `"tag3"` is ignored because `tag` is part of the group key.
-- The `with` operator preserves columns not in the group key (`_time` and `_value`).
-{{% /note %}}
-
-{{< flex >}}
-{{% flex-content %}}
-#### Input tables
-
-**Group key:** `tag,_field`
-
-| tag  | _field | _time | _value |
-| ---  |:------ |:----- | ------:|
-| tag1 | foo    | 0001  | 1.9    |
-| tag1 | foo    | 0002  | 2.4    |
-| tag1 | foo    | 0003  | 2.1    |
-
-| tag  | _field | _time | _value |
-|:---  |:------ |:----- | ------:|
-| tag2 | bar    | 0001  | 3.1    |
-| tag2 | bar    | 0002  | 3.8    |
-| tag2 | bar    | 0003  | 1.7    |
-{{% /flex-content %}}
-
-{{% flex-content %}}
-#### Output tables
-
-**Group key:** `tag,_field`
-
-| tag  | _field | _time | _value |
-| ---  |:------ |:----- | ------:|
-| tag1 | foo    | 0001  | 1.9    |
-| tag1 | foo    | 0002  | 2.4    |
-| tag1 | foo    | 0003  | 2.1    |
-
-| tag  | _field | _time | _value |
-|:---  |:------ |:----- | ------:|
-| tag2 | bar    | 0001  | 3.1    |
-| tag2 | bar    | 0002  | 3.8    |
-| tag2 | bar    | 0003  | 1.7    |
-{{% /flex-content %}}
-{{< /flex >}}
diff --git a/content/flux/v0.x/stdlib/contrib/rhajek/bigpanda/_index.md b/content/flux/v0.x/stdlib/contrib/rhajek/bigpanda/_index.md
index 8102143b8..20e1ab368 100644
--- a/content/flux/v0.x/stdlib/contrib/rhajek/bigpanda/_index.md
+++ b/content/flux/v0.x/stdlib/contrib/rhajek/bigpanda/_index.md
@@ -53,6 +53,6 @@ Sending alert timestamps to BigPanda is optional, but if you choose to send them
 convert timestamps to **epoch second timestamps**:
 
 ```js
-//
-  |> map(fn: (r) => ({ r with secTime: int(v: r._time) / 1000000000 }))
+data
+    |> map(fn: (r) => ({ r with secTime: int(v: r._time) / 1000000000 }))
 ```
diff --git a/content/flux/v0.x/stdlib/contrib/rhajek/bigpanda/endpoint.md b/content/flux/v0.x/stdlib/contrib/rhajek/bigpanda/endpoint.md
index 1d9bceddc..172259413 100644
--- a/content/flux/v0.x/stdlib/contrib/rhajek/bigpanda/endpoint.md
+++ b/content/flux/v0.x/stdlib/contrib/rhajek/bigpanda/endpoint.md
@@ -21,9 +21,9 @@ using data from input rows.
 import "contrib/rhajek/bigpanda"
 
 bigpanda.endpoint(
-  url: "https://api.bigpanda.io/data/v2/alerts",
-  token: "my5uP3rS3cRe7t0k3n",
-  appKey: "example-app-key"
+    url: "https://api.bigpanda.io/data/v2/alerts",
+    token: "my5uP3rS3cRe7t0k3n",
+    appKey: "example-app-key",
 )
 ```
 
@@ -67,22 +67,21 @@ import "influxdata/influxdb/secrets"
 import "json"
 
 token = secrets.get(key: "BIGPANDA_API_KEY")
-endpoint = bigpanda.endpoint(
-  token: token,
-  appKey: "example-app-key"
-)
+endpoint = bigpanda.endpoint(token: token, appKey: "example-app-key")
 
-crit_events = from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> filter(fn: (r) => r._measurement == "statuses" and status == "crit")
+crit_events =
+    from(bucket: "example-bucket")
+        |> range(start: -1m)
+        |> filter(fn: (r) => r._measurement == "statuses" and status == "crit")
 
 crit_events
-  |> endpoint(mapFn: (r) => {
-    return { r with
-      status: "critical",
-      check: "critical-status-check",
-      description: "${r._field} is critical: ${string(v: r._value)}"
-      tags: json.encode(v: [{"name": "host", "value": r.host}]),
-    }
-  })()
+    |> endpoint(
+        mapFn: (r) => {
+            return {r with status: "critical",
+                check: "critical-status-check",
+                description: "${r._field} is critical: ${string(v: r._value)}",
+                tags: json.encode(v: [{"name": "host", "value": r.host}]),
+            }
+        },
+    )()
 ```
diff --git a/content/flux/v0.x/stdlib/contrib/rhajek/bigpanda/sendalert.md b/content/flux/v0.x/stdlib/contrib/rhajek/bigpanda/sendalert.md
index 7bc3c1f35..75e3f466a 100644
--- a/content/flux/v0.x/stdlib/contrib/rhajek/bigpanda/sendalert.md
+++ b/content/flux/v0.x/stdlib/contrib/rhajek/bigpanda/sendalert.md
@@ -19,11 +19,11 @@ The `bigpanda.sendAlert()` function sends an alert to [BigPanda](https://www.big
 import "contrib/rhajek/bigpanda"
 
 bigpanda.sendAlert(
-  url: "https://api.bigpanda.io/data/v2/alerts",
-  token: "my5uP3rS3cRe7t0k3n",
-  appKey: "example-app-key",
-  status: "critical",
-  rec: {},
+    url: "https://api.bigpanda.io/data/v2/alerts",
+    token: "my5uP3rS3cRe7t0k3n",
+    appKey: "example-app-key",
+    status: "critical",
+    rec: {},
 )
 ```
 
@@ -68,23 +68,20 @@ import "json"
 token = secrets.get(key: "BIGPANDA_API_KEY")
 
 lastReported =
-  from(bucket: "example-bucket")
-    |> range(start: -1m)
-    |> filter(fn: (r) =>
-      r._measurement == "example-measurement" and
-      r._field == "level"
-    )
-    |> last()
-    |> findRecord(fn: (key) => true, idx: 0)
+    from(bucket: "example-bucket")
+        |> range(start: -1m)
+        |> filter(fn: (r) => r._measurement == "example-measurement" and r._field == "level")
+        |> last()
+        |> findRecord(fn: (key) => true, idx: 0)
 
 bigpanda.sendAlert(
-  token: token,
-  appKey: "example-app-key",
-  status: bigpanda.statusFromLevel(level: "${lastReported.status}"),
-  rec: {
-    tags: json.encode(v: [{"name": "host", "value": "my-host"}]),
-    check: "my-check",
-    description: "${lastReported._field} is ${lastReported.status}: ${string(v: lastReported._value)}"
-  }
+    token: token,
+    appKey: "example-app-key",
+    status: bigpanda.statusFromLevel(level: "${lastReported.status}"),
+    rec: {
+        tags: json.encode(v: [{"name": "host", "value": "my-host"}]),
+        check: "my-check",
+        description: "${lastReported._field} is ${lastReported.status}: ${string(v: lastReported._value)}",
+    },
 )
 ```
diff --git a/content/flux/v0.x/stdlib/contrib/sranka/opsgenie/endpoint.md b/content/flux/v0.x/stdlib/contrib/sranka/opsgenie/endpoint.md
index 9c499fedf..5952e1bf3 100644
--- a/content/flux/v0.x/stdlib/contrib/sranka/opsgenie/endpoint.md
+++ b/content/flux/v0.x/stdlib/contrib/sranka/opsgenie/endpoint.md
@@ -20,9 +20,9 @@ The `opsgenie.endpoint()` function sends an alert message to Opsgenie using data
 import "contrib/sranka/opsgenie"
 
 opsgenie.endpoint(
-  url: "https://api.opsgenie.com/v2/alerts",
-  apiKey: "YoUrSup3R5ecR37AuThK3y",
-  entity: "example-entity"
+    url: "https://api.opsgenie.com/v2/alerts",
+    apiKey: "YoUrSup3R5ecR37AuThK3y",
+    entity: "example-entity",
 )
 ```
 
@@ -72,22 +72,25 @@ import "contrib/sranka/opsgenie"
 apiKey = secrets.get(key: "OPSGENIE_APIKEY")
 endpoint = opsgenie.endpoint(apiKey: apiKey)
 
-crit_statuses = from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> filter(fn: (r) => r._measurement == "statuses" and status == "crit")
+crit_statuses =
+    from(bucket: "example-bucket")
+        |> range(start: -1m)
+        |> filter(fn: (r) => r._measurement == "statuses" and status == "crit")
 
 crit_statuses
-  |> endpoint(mapFn: (r) => ({
-    message: "Great Scott!- Disk usage is: ${r.status}.",
-      alias: "disk-usage-${r.status}",
-      description: "",
-      priority: "P3",
-      responders: ["user:john@example.com", "team:itcrowd"],
-      tags: [],
-      entity: "my-lab",
-      actions: [],
-      details: "{}",
-      visibleTo: []
-    })
-  )()
+    |> endpoint(
+        mapFn: (r) =>
+            ({
+                message: "Great Scott!- Disk usage is: ${r.status}.",
+                alias: "disk-usage-${r.status}",
+                description: "",
+                priority: "P3",
+                responders: ["user:john@example.com", "team:itcrowd"],
+                tags: [],
+                entity: "my-lab",
+                actions: [],
+                details: "{}",
+                visibleTo: [],
+            }),
+    )()
 ```
diff --git a/content/flux/v0.x/stdlib/contrib/sranka/opsgenie/responderstojson.md b/content/flux/v0.x/stdlib/contrib/sranka/opsgenie/responderstojson.md
index 412c17dc2..95d24afa3 100644
--- a/content/flux/v0.x/stdlib/contrib/sranka/opsgenie/responderstojson.md
+++ b/content/flux/v0.x/stdlib/contrib/sranka/opsgenie/responderstojson.md
@@ -19,13 +19,10 @@ strings to a string-encoded JSON array that can be embedded in an alert message.
 ```js
 import "contrib/sranka/opsgenie"
 
+import "contrib/sranka/opsgenie"
+
 opsgenie.respondersToJSON(
-  v: [
-    "user:example-user",
-    "team:example-team",
-    "escalation:example-escalation",
-    "schedule:example-schedule"
-  ]
+    v: ["user:example-user", "team:example-team", "escalation:example-escalation", "schedule:example-schedule"],
 )
 
 // Returns "[
diff --git a/content/flux/v0.x/stdlib/contrib/sranka/opsgenie/sendalert.md b/content/flux/v0.x/stdlib/contrib/sranka/opsgenie/sendalert.md
index dca105119..7e6581476 100644
--- a/content/flux/v0.x/stdlib/contrib/sranka/opsgenie/sendalert.md
+++ b/content/flux/v0.x/stdlib/contrib/sranka/opsgenie/sendalert.md
@@ -19,18 +19,18 @@ The `opsgenie.sendAlert()` function sends an alert message to Opsgenie.
 import "contrib/sranka/opsgenie"
 
 opsgenie.sendAlert(
-  url: "https://api.opsgenie.com/v2/alerts",
-  apiKey: "YoUrSup3R5ecR37AuThK3y",
-  message: "Example message",
-  alias: "Example alias",
-  description: "Example description",
-  priority: "P3",
-  responders: ["user:john@example.com", "team:itcrowd"],
-  tags: ["tag1", "tag2"],
-  entity: "example-entity",
-  actions: ["action1", "action2"],
-  details: "{}",
-  visibleTo: []
+    url: "https://api.opsgenie.com/v2/alerts",
+    apiKey: "YoUrSup3R5ecR37AuThK3y",
+    message: "Example message",
+    alias: "Example alias",
+    description: "Example description",
+    priority: "P3",
+    responders: ["user:john@example.com", "team:itcrowd"],
+    tags: ["tag1", "tag2"],
+    entity: "example-entity",
+    actions: ["action1", "action2"],
+    details: "{}",
+    visibleTo: [],
 )
 ```
 
@@ -99,16 +99,16 @@ import "contrib/sranka/opsgenie"
 apiKey = secrets.get(key: "OPSGENIE_APIKEY")
 
 lastReported =
-  from(bucket: "example-bucket")
-    |> range(start: -1m)
-    |> filter(fn: (r) => r._measurement == "statuses")
-    |> last()
-    |> findRecord(fn: (key) => true, idx: 0)
+    from(bucket: "example-bucket")
+        |> range(start: -1m)
+        |> filter(fn: (r) => r._measurement == "statuses")
+        |> last()
+        |> findRecord(fn: (key) => true, idx: 0)
 
-    opsgenie.sendAlert(
-      apiKey: apiKey,
-      message: "Disk usage is: ${lastReported.status}.",
-      alias: "example-disk-usage",
-      responders: ["user:john@example.com", "team:itcrowd"]
-    )
+opsgenie.sendAlert(
+    apiKey: apiKey,
+    message: "Disk usage is: ${lastReported.status}.",
+    alias: "example-disk-usage",
+    responders: ["user:john@example.com", "team:itcrowd"],
+)
 ```
diff --git a/content/flux/v0.x/stdlib/contrib/sranka/sensu/endpoint.md b/content/flux/v0.x/stdlib/contrib/sranka/sensu/endpoint.md
index 90da236e7..a21529a3c 100644
--- a/content/flux/v0.x/stdlib/contrib/sranka/sensu/endpoint.md
+++ b/content/flux/v0.x/stdlib/contrib/sranka/sensu/endpoint.md
@@ -28,11 +28,11 @@ using data from table rows.
 import "contrib/sranka/sensu"
 
 sensu.endpoint(
-  url: "http://localhost:8080",
-  apiKey: "mYSuP3rs3cREtApIK3Y",
-  handlers: [],
-  namespace: "default",
-  entityName: "influxdb"
+    url: "http://localhost:8080",
+    apiKey: "mYSuP3rs3cREtApIK3Y",
+    handlers: [],
+    namespace: "default",
+    entityName: "influxdb",
 )
 ```
 
@@ -86,20 +86,13 @@ import "influxdata/influxdb/secrets"
 import "contrib/sranka/sensu"
 
 token = secrets.get(key: "TELEGRAM_TOKEN")
-endpoint = sensu.endpoint(
-  url: "http://localhost:8080",
-  apiKey: apiKey
-)
+endpoint = sensu.endpoint(url: "http://localhost:8080", apiKey: apiKey)
 
-crit_statuses = from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> filter(fn: (r) => r._measurement == "statuses" and status == "crit")
+crit_statuses =
+    from(bucket: "example-bucket")
+        |> range(start: -1m)
+        |> filter(fn: (r) => r._measurement == "statuses" and status == "crit")
 
 crit_statuses
-  |> endpoint(mapFn: (r) => ({
-      checkName: "critStatus",
-      text: "Status is critical",
-      status: 2
-    })
-  )()
+    |> endpoint(mapFn: (r) => ({checkName: "critStatus", text: "Status is critical", status: 2}))()
 ```
diff --git a/content/flux/v0.x/stdlib/contrib/sranka/sensu/event.md b/content/flux/v0.x/stdlib/contrib/sranka/sensu/event.md
index 16816e195..6727c9b9b 100644
--- a/content/flux/v0.x/stdlib/contrib/sranka/sensu/event.md
+++ b/content/flux/v0.x/stdlib/contrib/sranka/sensu/event.md
@@ -25,15 +25,15 @@ The `sensu.event()` function sends a single event to the
 import "contrib/sranka/sensu"
 
 sensu.event(
-  url: "http://localhost:8080",
-  apiKey: "mYSuP3rs3cREtApIK3Y",
-  checkName: "checkName",
-  text: "Event output text",
-  handlers: [],
-  status: 0,
-  state: "passing",
-  namespace: "default",
-  entityName: "influxdb"
+    url: "http://localhost:8080",
+    apiKey: "mYSuP3rs3cREtApIK3Y",
+    checkName: "checkName",
+    text: "Event output text",
+    handlers: [],
+    status: 0,
+    state: "passing",
+    namespace: "default",
+    entityName: "influxdb",
 )
 ```
 
@@ -104,16 +104,16 @@ import "contrib/sranka/sensu"
 apiKey = secrets.get(key: "SENSU_API_KEY")
 
 lastReported =
-  from(bucket: "example-bucket")
-    |> range(start: -1m)
-    |> filter(fn: (r) => r._measurement == "statuses")
-    |> last()
-    |> findRecord(fn: (key) => true, idx: 0)
+    from(bucket: "example-bucket")
+        |> range(start: -1m)
+        |> filter(fn: (r) => r._measurement == "statuses")
+        |> last()
+        |> findRecord(fn: (key) => true, idx: 0)
 
-    sensu.event(
-      url: "http://localhost:8080",
-      apiKey: apiKey,
-      checkName: "diskUsage",
-      text: "Disk usage is **${lastReported.status}**.",
-    )
+sensu.event(
+    url: "http://localhost:8080",
+    apiKey: apiKey,
+    checkName: "diskUsage",
+    text: "Disk usage is **${lastReported.status}**.",
+)
 ```
diff --git a/content/flux/v0.x/stdlib/contrib/sranka/teams/endpoint.md b/content/flux/v0.x/stdlib/contrib/sranka/teams/endpoint.md
index f83690d1c..52944788e 100644
--- a/content/flux/v0.x/stdlib/contrib/sranka/teams/endpoint.md
+++ b/content/flux/v0.x/stdlib/contrib/sranka/teams/endpoint.md
@@ -21,9 +21,7 @@ using data from table rows.
 ```js
 import "contrib/sranka/teams"
 
-teams.endpoint(
- url: "https://outlook.office.com/webhook/example-webhook"
-)
+teams.endpoint(url: "https://outlook.office.com/webhook/example-webhook")
 ```
 
 ## Parameters
@@ -57,15 +55,14 @@ import "contrib/sranka/teams"
 url = "https://outlook.office.com/webhook/example-webhook"
 endpoint = teams.endpoint(url: url)
 
-crit_statuses = from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> filter(fn: (r) => r._measurement == "statuses" and status == "crit")
+crit_statuses =
+    from(bucket: "example-bucket")
+        |> range(start: -1m)
+        |> filter(fn: (r) => r._measurement == "statuses" and status == "crit")
 
 crit_statuses
-  |> endpoint(mapFn: (r) => ({
-      title: "Disk Usage"
-      text: "Disk usage is: **${r.status}**.",
-      summary: "Disk usage is ${r.status}"
-    })
-  )()
+    |> endpoint(
+        mapFn: (r) =>
+            ({title: "Disk Usage", text: "Disk usage is: **${r.status}**.", summary: "Disk usage is ${r.status}"}),
+    )()
 ```
diff --git a/content/flux/v0.x/stdlib/contrib/sranka/teams/message.md b/content/flux/v0.x/stdlib/contrib/sranka/teams/message.md
index eb48bc5ab..08a0f65f1 100644
--- a/content/flux/v0.x/stdlib/contrib/sranka/teams/message.md
+++ b/content/flux/v0.x/stdlib/contrib/sranka/teams/message.md
@@ -21,10 +21,10 @@ an [incoming webhook](https://docs.microsoft.com/microsoftteams/platform/webhook
 import "contrib/sranka/teams"
 
 teams.message(
-  url: "https://outlook.office.com/webhook/example-webhook",
-  title: "Example message title",
-  text: "Example message text",
-  summary: "",
+    url: "https://outlook.office.com/webhook/example-webhook",
+    title: "Example message title",
+    text: "Example message text",
+    summary: "",
 )
 ```
 
@@ -51,16 +51,16 @@ If no summary is provided, Flux generates the summary from the message text.
 import "contrib/sranka/teams"
 
 lastReported =
-  from(bucket: "example-bucket")
-    |> range(start: -1m)
-    |> filter(fn: (r) => r._measurement == "statuses")
-    |> last()
-    |> findRecord(fn: (key) => true, idx: 0)
+    from(bucket: "example-bucket")
+        |> range(start: -1m)
+        |> filter(fn: (r) => r._measurement == "statuses")
+        |> last()
+        |> findRecord(fn: (key) => true, idx: 0)
 
 teams.message(
-  url: "https://outlook.office.com/webhook/example-webhook",
-  title: "Disk Usage"
-  text: "Disk usage is: *${lastReported.status}*.",
-  summary: "Disk usage is ${lastReported.status}"
+    url: "https://outlook.office.com/webhook/example-webhook",
+    title: "Disk Usage",
+    text: "Disk usage is: *${lastReported.status}*.",
+    summary: "Disk usage is ${lastReported.status}",
 )
 ```
diff --git a/content/flux/v0.x/stdlib/contrib/sranka/telegram/endpoint.md b/content/flux/v0.x/stdlib/contrib/sranka/telegram/endpoint.md
index 58d715d3e..fd99eae82 100644
--- a/content/flux/v0.x/stdlib/contrib/sranka/telegram/endpoint.md
+++ b/content/flux/v0.x/stdlib/contrib/sranka/telegram/endpoint.md
@@ -22,10 +22,10 @@ using data from table rows.
 import "contrib/sranka/telegram"
 
 telegram.endpoint(
-  url: "https://api.telegram.org/bot",
-  token: "S3crEtTel3gRamT0k3n",
-  parseMode: "MarkdownV2",
-  disableWebPagePreview: false,
+    url: "https://api.telegram.org/bot",
+    token: "S3crEtTel3gRamT0k3n",
+    parseMode: "MarkdownV2",
+    disableWebPagePreview: false,
 )
 ```
 
@@ -79,15 +79,11 @@ import "contrib/sranka/telegram"
 token = secrets.get(key: "TELEGRAM_TOKEN")
 endpoint = telegram.endpoint(token: token)
 
-crit_statuses = from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> filter(fn: (r) => r._measurement == "statuses" and status == "crit")
+crit_statuses =
+    from(bucket: "example-bucket")
+        |> range(start: -1m)
+        |> filter(fn: (r) => r._measurement == "statuses" and status == "crit")
 
 crit_statuses
-  |> endpoint(mapFn: (r) => ({
-      channel: "-12345",
-      text: "Disk usage is **${r.status}**.",
-      silent: true
-    })
-  )()
+    |> endpoint(mapFn: (r) => ({channel: "-12345", text: "Disk usage is **${r.status}**.", silent: true}))()
 ```
diff --git a/content/flux/v0.x/stdlib/contrib/sranka/telegram/message.md b/content/flux/v0.x/stdlib/contrib/sranka/telegram/message.md
index 138f3fd3f..431ac7678 100644
--- a/content/flux/v0.x/stdlib/contrib/sranka/telegram/message.md
+++ b/content/flux/v0.x/stdlib/contrib/sranka/telegram/message.md
@@ -21,13 +21,13 @@ the [`sendMessage` method of the Telegram Bot API](https://core.telegram.org/bot
 import "contrib/sranka/telegram"
 
 telegram.message(
-  url: "https://api.telegram.org/bot",
-  token: "S3crEtTel3gRamT0k3n",
-  channel: "-12345",
-  text: "Example message text",
-  parseMode: "MarkdownV2",
-  disableWebPagePreview: false,
-  silent: true
+    url: "https://api.telegram.org/bot",
+    token: "S3crEtTel3gRamT0k3n",
+    channel: "-12345",
+    text: "Example message text",
+    parseMode: "MarkdownV2",
+    disableWebPagePreview: false,
+    silent: true,
 )
 ```
 
@@ -75,15 +75,11 @@ import "contrib/sranka/telegram"
 token = secrets.get(key: "TELEGRAM_TOKEN")
 
 lastReported =
-  from(bucket: "example-bucket")
-    |> range(start: -1m)
-    |> filter(fn: (r) => r._measurement == "statuses")
-    |> last()
-    |> findRecord(fn: (key) => true, idx: 0)
+    from(bucket: "example-bucket")
+        |> range(start: -1m)
+        |> filter(fn: (r) => r._measurement == "statuses")
+        |> last()
+        |> findRecord(fn: (key) => true, idx: 0)
 
-    telegram.message(
-      token: token,
-      channel: "-12345"
-      text: "Disk usage is **${lastReported.status}**.",
-    )
+telegram.message(token: token, channel: "-12345", text: "Disk usage is **${lastReported.status}**.")
 ```
diff --git a/content/flux/v0.x/stdlib/contrib/sranka/webexteams/endpoint.md b/content/flux/v0.x/stdlib/contrib/sranka/webexteams/endpoint.md
index 09fb721c7..2f55c76ec 100644
--- a/content/flux/v0.x/stdlib/contrib/sranka/webexteams/endpoint.md
+++ b/content/flux/v0.x/stdlib/contrib/sranka/webexteams/endpoint.md
@@ -21,8 +21,8 @@ includes data from input rows to a Webex room.
 import "contrib/sranka/webexteams"
 
 webexteams.endpoint(
-  url: "https://webexapis.com",
-  token: "token"
+    url: "https://webexapis.com",
+    token: "token",
 )
 ```
 
@@ -63,13 +63,16 @@ import "influxdata/influxdb/secrets"
 token = secrets.get(key: "WEBEX_API_KEY")
 
 from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> filter(fn: (r) => r._measurement == "statuses")
-  |> last()
-  |> tableFind(fn: (key) => true)
-  |> webexteams.endpoint(token: token)(mapFn: (r) => ({
-      roomId: "Y2lzY29zcGFyazovL3VzL1JPT00vYmJjZWIxYWQtNDNmMS0zYjU4LTkxNDctZjE0YmIwYzRkMTU0",
-      text: "",
-      markdown: "Disk usage is **${r.status}**.", 
-  })
+    |> range(start: -1m)
+    |> filter(fn: (r) => r._measurement == "statuses")
+    |> last()
+    |> tableFind(fn: (key) => true)
+    |> webexteams.endpoint(token: token)(
+        mapFn: (r) =>
+            ({
+                roomId: "Y2lzY29zcGFyazovL3VzL1JPT00vYmJjZWIxYWQtNDNmMS0zYjU4LTkxNDctZjE0YmIwYzRkMTU0",
+                text: "",
+                markdown: "Disk usage is **${r.status}**.",
+            }),
+    )
 ```
\ No newline at end of file
diff --git a/content/flux/v0.x/stdlib/contrib/sranka/webexteams/message.md b/content/flux/v0.x/stdlib/contrib/sranka/webexteams/message.md
index b623de3c9..33c0f0545 100644
--- a/content/flux/v0.x/stdlib/contrib/sranka/webexteams/message.md
+++ b/content/flux/v0.x/stdlib/contrib/sranka/webexteams/message.md
@@ -20,11 +20,11 @@ The `webexteams.message()` function sends a single message to Webex using the
 import "contrib/sranka/webexteams"
 
 webexteams.message(,
-  url: "https://webexapis.com"
-  token: "My5uP3rs3cRe7T0k3n",
-  roomId: "Y2lzY29zcGFyazovL3VzL1JPT00vYmJjZWIxYWQtNDNmMS0zYjU4LTkxNDctZjE0YmIwYzRkMTU0",
-  text: "Example plain text message",
-  markdown: "Example [markdown message](https://developer.webex.com/docs/api/basics)." 
+    url: "https://webexapis.com"
+    token: "My5uP3rs3cRe7T0k3n",
+    roomId: "Y2lzY29zcGFyazovL3VzL1JPT00vYmJjZWIxYWQtNDNmMS0zYjU4LTkxNDctZjE0YmIwYzRkMTU0",
+    text: "Example plain text message",
+    markdown: "Example [markdown message](https://developer.webex.com/docs/api/basics).",
 )
 ```
 
@@ -60,16 +60,16 @@ import "influxdata/influxdb/secrets"
 apiToken = secrets.get(key: "WEBEX_API_TOKEN")
 
 lastReported =
-  from(bucket: "example-bucket")
-    |> range(start: -1m)
-    |> filter(fn: (r) => r._measurement == "statuses")
-    |> last()
-    |> findRecord(fn: (key) => true, idx: 0)
+    from(bucket: "example-bucket")
+        |> range(start: -1m)
+        |> filter(fn: (r) => r._measurement == "statuses")
+        |> last()
+        |> findRecord(fn: (key) => true, idx: 0)
 
 webexteams.message(
-  token: apiToken,
-  roomId: "Y2lzY29zcGFyazovL3VzL1JPT00vYmJjZWIxYWQtNDNmMS0zYjU4LTkxNDctZjE0YmIwYzRkMTU0",
-  text: "Disk usage is ${lastReported.status}.",
-  markdown: "Disk usage is **${lastReported.status}**."
+    token: apiToken,
+    roomId: "Y2lzY29zcGFyazovL3VzL1JPT00vYmJjZWIxYWQtNDNmMS0zYjU4LTkxNDctZjE0YmIwYzRkMTU0",
+    text: "Disk usage is ${lastReported.status}.",
+    markdown: "Disk usage is **${lastReported.status}**.",
 )
 ```
diff --git a/content/flux/v0.x/stdlib/contrib/tomhollingworth/events/duration.md b/content/flux/v0.x/stdlib/contrib/tomhollingworth/events/duration.md
index 767496e3d..a3e50a904 100644
--- a/content/flux/v0.x/stdlib/contrib/tomhollingworth/events/duration.md
+++ b/content/flux/v0.x/stdlib/contrib/tomhollingworth/events/duration.md
@@ -29,11 +29,11 @@ specified [`stop`](#stop) time.
 import "contrib/tomhollingworth/events"
 
 events.duration(
-  unit: 1ns,
-  columnName: "duration",
-  timeColumn: "_time",
-  stopColumn: "_stop",
-  stop: 2020-01-01T00:00:00Z
+    unit: 1ns,
+    columnName: "duration",
+    timeColumn: "_time",
+    stopColumn: "_stop",
+    stop: 2020-01-01T00:00:00Z,
 )
 ```
 
@@ -83,10 +83,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "contrib/tomhollingworth/events"
 
 data
-  |> events.duration(
-    unit: 1m,
-    stop: 2020-01-02T00:00:00Z
-  )
+    |> events.duration(unit: 1m, stop: 2020-01-02T00:00:00Z)
 ```
 
 {{< flex >}}
@@ -133,19 +130,11 @@ The example below includes output values of `events.duration()`, `elapsed()`, an
 {{% flex-content %}}
 ##### Functions
 ```js
-data |> events.duration(
-  unit: 1m,
-  stop: 2020-01-02T00:00:00Z
-)
+data |> events.duration(unit: 1m, stop: 2020-01-02T00:00:00Z)
 
-data |> elapsed(
-  unit: 1m
-)
+data |> elapsed(unit: 1m)
 
-data |> stateDuration(
-  unit: 1m,
-  fn: (r) => true
-)
+data |> stateDuration(unit: 1m, fn: (r) => true)
 ```
 {{% /flex-content %}}
 {{< /flex >}}
diff --git a/content/flux/v0.x/stdlib/csv/from.md b/content/flux/v0.x/stdlib/csv/from.md
index a2efd97c7..49799069c 100644
--- a/content/flux/v0.x/stdlib/csv/from.md
+++ b/content/flux/v0.x/stdlib/csv/from.md
@@ -25,15 +25,15 @@ Each record in the table represents a single point in the series.
 import "csv"
 
 csv.from(
-  csv: csvData,
-  mode: "annotations"
+    csv: csvData,
+    mode: "annotations",
 )
 
 // OR
 
 csv.from(
-  file: "/path/to/data-file.csv",
-  mode: "annotations"
+    file: "/path/to/data-file.csv",
+    mode: "annotations",
 )
 ```
 
@@ -87,17 +87,16 @@ csv.from(file: "/path/to/data-file.csv")
 ##### Query raw CSV data from a file
 ```js
 import "csv"
-csv.from(
-  file: "/path/to/data-file.csv",
-  mode: "raw"
-)
+
+csv.from(file: "/path/to/data-file.csv", mode: "raw")
 ```
 
 ##### Query an annotated CSV string
 ```js
 import "csv"
 
-csvData = "
+csvData =
+    "
 #datatype,string,long,dateTime:RFC3339,dateTime:RFC3339,dateTime:RFC3339,string,string,double
 #group,false,false,false,false,false,false,false,false
 #default,,,,,,,,
@@ -109,22 +108,25 @@ csvData = "
 
 csv.from(csv: csvData)
 ```
+
 ##### Query a raw CSV string
 ```js
 import "csv"
-csvData = "
+
+csvData =
+    "
 _start,_stop,_time,region,host,_value
 2018-05-08T20:50:00Z,2018-05-08T20:51:00Z,2018-05-08T20:50:00Z,east,A,15.43
 2018-05-08T20:50:00Z,2018-05-08T20:51:00Z,2018-05-08T20:50:20Z,east,B,59.25
 2018-05-08T20:50:00Z,2018-05-08T20:51:00Z,2018-05-08T20:50:40Z,east,C,52.62
 "
-csv.from(
-  csv: csvData,
-  mode: "raw"
-)
+
+csv.from(csv: csvData, mode: "raw")
 ```
 
+{{< expand-wrapper >}}
 {{% expand "Function updates" %}}
 #### v0.109.0
 - Add `mode` parameter to support querying raw CSV data.
 {{% /expand %}}
+{{< /expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/date/addduration.md b/content/flux/v0.x/stdlib/date/addduration.md
new file mode 100644
index 000000000..35d99e8d3
--- /dev/null
+++ b/content/flux/v0.x/stdlib/date/addduration.md
@@ -0,0 +1,54 @@
+---
+title: date.addDuration() function
+description: >
+  `date.addDuration()` adds a duration to a time value and returns the resulting time.
+menu:
+  flux_0_x_ref:
+    name: date.addDuration
+    parent: date
+weight: 302
+flux/v0.x/tags: [date/time]
+related:
+  - /flux/v0.x/stdlib/date/subduration/
+introduced: 0.162.0
+---
+
+`date.addDuration()` adds a duration to a time value and returns the resulting time.
+
+```js
+import "date"
+
+date.addDuration(d: 12h, to: now())
+```
+
+## Parameters
+
+### d {data-type="duration"}
+Duration to add.
+
+### to {data-type="time, duration"}
+Time to add the [duration](#d) to.
+Use an absolute time or a relative duration.
+Durations are relative to [`now()`](/flux/v0.x/stdlib/universe/now/).
+
+## Examples
+
+### Add six hours to a timestamp
+```js
+import "date"
+
+date.addDuration(d: 6h, to: 2019-09-16T12:00:00Z)
+
+// Returns 2019-09-16T18:00:00.000000000Z
+```
+
+### Add six hours to a relative duration
+```js
+import "date"
+
+option now = () => 2022-01-01T12:00:00Z
+
+date.addDuration(d: 6h, to: 3h)
+
+// Returns 2022-01-01T21:00:00.000000000Z
+```
diff --git a/content/flux/v0.x/stdlib/date/subduration.md b/content/flux/v0.x/stdlib/date/subduration.md
new file mode 100644
index 000000000..354314131
--- /dev/null
+++ b/content/flux/v0.x/stdlib/date/subduration.md
@@ -0,0 +1,56 @@
+---
+title: date.subDuration() function
+description: >
+  `date.subDuration()` subtracts a duration from a time value and returns the
+  resulting time value.
+menu:
+  flux_0_x_ref:
+    name: date.subDuration
+    parent: date
+weight: 302
+flux/v0.x/tags: [date/time]
+related:
+  - /flux/v0.x/stdlib/date/addduration/
+introduced: 0.162.0
+---
+
+`date.subDuration()` subtracts a duration from a time value and returns the
+resulting time value.
+
+```js
+import "date"
+
+date.subDuration(d: 12h, from: now())
+```
+
+## Parameters
+
+### d {data-type="duration"}
+Duration to subtract.
+
+### from {data-type="time, duration"}
+Time to subtract the [duration](#d) from.
+Use an absolute time or a relative duration.
+Durations are relative to [`now()`](/flux/v0.x/stdlib/universe/now/).
+
+## Examples
+
+### Subtract six hours from a timestamp
+```js
+import "date"
+
+date.subDuration(d: 6h, from: 2019-09-16T12:00:00Z)
+
+// Returns 2019-09-16T06:00:00.000000000Z
+```
+
+### Subtract six hours from a relative duration
+```js
+import "date"
+
+option now = () => 2022-01-01T12:00:00Z
+
+date.subDuration(d: 6h, from: -3h)
+
+// Returns 2022-01-01T03:00:00.000000000Z
+```
diff --git a/content/flux/v0.x/stdlib/dict/fromlist.md b/content/flux/v0.x/stdlib/dict/fromlist.md
index 3e2f2797a..21df68bed 100644
--- a/content/flux/v0.x/stdlib/dict/fromlist.md
+++ b/content/flux/v0.x/stdlib/dict/fromlist.md
@@ -20,12 +20,7 @@ The `dict.fromList()` function creates a dictionary from a list of records with
 ```js
 import "dict"
 
-dict.fromList(
-  pairs: [
-    {key: 1, value: "foo"},
-    {key: 2, value: "bar"}
-  ]
-)
+dict.fromList(pairs: [{key: 1, value: "foo"},{key: 2, value: "bar"}])
 ```
 
 ## Parameters
@@ -40,12 +35,7 @@ dict.fromList(
 import "dict"
 
 // Define a new dictionary using an array of records
-d = dict.fromList(
-  pairs: [
-    {key: 1, value: "foo"},
-    {key: 2, value: "bar"}
-  ]
-)
+d = dict.fromList(pairs: [{key: 1, value: "foo"}, {key: 2, value: "bar"}])
 
 // Return a property of the dictionary
 dict.get(dict: d, key: 1, default: "")
diff --git a/content/flux/v0.x/stdlib/dict/get.md b/content/flux/v0.x/stdlib/dict/get.md
index 48a6fde57..dd89bffca 100644
--- a/content/flux/v0.x/stdlib/dict/get.md
+++ b/content/flux/v0.x/stdlib/dict/get.md
@@ -21,9 +21,9 @@ or a default value if the key does not exist.
 import "dict"
 
 dict.get(
-  dict: [1: "foo", 2: "bar"],
-  key: 1,
-  default: ""
+    dict: [1: "foo", 2: "bar"],
+    key: 1,
+    default: "",
 )
 ```
 
@@ -51,11 +51,7 @@ import "dict"
 
 d = [1: "foo", 2: "bar"]
 
-dict.get(
-  dict: d,
-  key: 1,
-  default: ""
-)
+dict.get(dict: d, key: 1, default: "")
 
 // Returns foo
 ```
diff --git a/content/flux/v0.x/stdlib/dict/insert.md b/content/flux/v0.x/stdlib/dict/insert.md
index 16f8d7949..f9cb3d1e6 100644
--- a/content/flux/v0.x/stdlib/dict/insert.md
+++ b/content/flux/v0.x/stdlib/dict/insert.md
@@ -23,9 +23,9 @@ If the key already exists in the dictionary, the function overwrites the existin
 import "dict"
 
 dict.insert(
-  dict: [1: "foo", 2: "bar"],
-  key: 3,
-  value: "baz"
+    dict: [1: "foo", 2: "bar"],
+    key: 3,
+    value: "baz",
 )
 ```
 
@@ -54,11 +54,7 @@ import "dict"
 
 d = [1: "foo", 2: "bar"]
 
-dNew = dict.insert(
-  dict: d,
-  key: 3,
-  value: "baz"
-)
+dNew = dict.insert(dict: d, key: 3, value: "baz")
 
 // Verify the new key-value pair was inserted
 dict.get(dict: dNew, key: 3, default: "")
@@ -72,11 +68,7 @@ import "dict"
 
 d = [1: "foo", 2: "bar"]
 
-dNew = dict.insert(
-  dict: d,
-  key: 2,
-  value: "baz"
-)
+dNew = dict.insert(dict: d, key: 2, value: "baz")
 
 // Verify the new key-value pair was overwritten
 dict.get(dict: dNew, key: 2, default: "")
diff --git a/content/flux/v0.x/stdlib/dict/remove.md b/content/flux/v0.x/stdlib/dict/remove.md
index b8310b4bd..683fe2d00 100644
--- a/content/flux/v0.x/stdlib/dict/remove.md
+++ b/content/flux/v0.x/stdlib/dict/remove.md
@@ -20,10 +20,7 @@ an updated dictionary.
 ```js
 import "dict"
 
-dict.remove(
-  dict: [1: "foo", 2: "bar"],
-  key: 1
-)
+dict.remove(dict: [1: "foo", 2: "bar"], key: 1)
 ```
 
 ## Parameters
@@ -47,10 +44,7 @@ import "dict"
 
 d = [1: "foo", 2: "bar"]
 
-dNew = dict.remove(
-  dict: d,
-  key: 1
-)
+dNew = dict.remove(dict: d, key: 1)
 
 // Verify the key-value pairs was removed
 
diff --git a/content/flux/v0.x/stdlib/experimental/addduration.md b/content/flux/v0.x/stdlib/experimental/addduration.md
index 3d038ca9c..694198952 100644
--- a/content/flux/v0.x/stdlib/experimental/addduration.md
+++ b/content/flux/v0.x/stdlib/experimental/addduration.md
@@ -15,16 +15,17 @@ flux/v0.x/tags: [date/time]
 related:
   - /flux/v0.x/stdlib/experimental/subduration/
 introduced: 0.39.0
+deprecated: 0.162.0
 ---
 
+{{% warn %}}
+This function was promoted to the [`date` package](/flux/v0.x/stdlib/date/addduration/)
+in **Flux v0.162.0**. This experimental version has been deprecated.
+{{% /warn %}}
+
 The `experimental.addDuration()` function adds a duration to a time value and
 returns the resulting time value.
 
-{{% warn %}}
-This function will be removed once duration vectors are implemented.
-See [influxdata/flux#413](https://github.com/influxdata/flux/issues/413).
-{{% /warn %}}
-
 ```js
 import "experimental"
 
diff --git a/content/flux/v0.x/stdlib/experimental/aggregate/rate.md b/content/flux/v0.x/stdlib/experimental/aggregate/rate.md
index ca4f38519..9243e0048 100644
--- a/content/flux/v0.x/stdlib/experimental/aggregate/rate.md
+++ b/content/flux/v0.x/stdlib/experimental/aggregate/rate.md
@@ -23,9 +23,9 @@ for each input table.
 import "experimental/aggregate"
 
 aggregate.rate(
-  every: 1m,
-  groupColumns: ["column1", "column2"],
-  unit: 1s
+    every: 1m,
+    groupColumns: ["column1", "column2"],
+    unit: 1s,
 )
 ```
 
@@ -57,15 +57,12 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "experimental/aggregate"
 import "sampledata"
 
-data = sampledata.int()
-  |> range(start: sampledata.start, stop: sampledata.stop)
+data =
+    sampledata.int()
+        |> range(start: sampledata.start, stop: sampledata.stop)
 
-data  
-  |> aggregate.rate(
-    every: 30s,
-    unit: 1s,
-    groupColumns: ["tag"]
-  )
+data
+    |> aggregate.rate(every: 30s, unit: 1s, groupColumns: ["tag"])
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/experimental/aligntime.md b/content/flux/v0.x/stdlib/experimental/aligntime.md
index 55914babb..45927bfb0 100644
--- a/content/flux/v0.x/stdlib/experimental/aligntime.md
+++ b/content/flux/v0.x/stdlib/experimental/aligntime.md
@@ -20,7 +20,7 @@ The `experimental.alignTime()` function aligns input tables to a common start ti
 import "experimental"
 
 experimental.alignTime(
-  alignTo: 1970-01-01T00:00:00.000000000Z
+    alignTo: 1970-01-01T00:00:00.000000000Z
 )
 ```
 
@@ -41,10 +41,10 @@ Default is piped-forward data (`<-`).
 import "experimental"
 
 from(bucket: "example-bucket")
-  |> range(start: -12mo)
-  |> filter(fn: (r) => r._measurement == "example-measurement")
-  |> window(every: 1mo)
-  |> experimental.alignTime()
+    |> range(start: -12mo)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> window(every: 1mo)
+    |> experimental.alignTime()
 ```
 
 **Given the following input:**
@@ -67,8 +67,8 @@ from(bucket: "example-bucket")
 
 ```js
 //...
-  |> window(every: 1mo)
-  |> alignTime(alignTo: 2020-01-01T00:00:00Z)
+    |> window(every: 1mo)
+    |> alignTime(alignTo: 2020-01-01T00:00:00Z)
 ```
 
 **And output:**
diff --git a/content/flux/v0.x/stdlib/experimental/array/_index.md b/content/flux/v0.x/stdlib/experimental/array/_index.md
new file mode 100644
index 000000000..dc8ae2bb0
--- /dev/null
+++ b/content/flux/v0.x/stdlib/experimental/array/_index.md
@@ -0,0 +1,35 @@
+---
+title: Flux experimental array package
+list_title: array package
+description: >
+  The Flux experimental `array` package provides functions for operating on Flux arrays.
+  Import the `experimental/array` package.
+aliases:
+  - /influxdb/v2.0/reference/flux/stdlib/experimental/array/
+  - /influxdb/cloud/reference/flux/stdlib/experimental/array/
+  - /influxdb/v2.0/reference/flux/stdlib/array/
+  - /influxdb/cloud/reference/flux/stdlib/array/
+menu:
+  flux_0_x_ref:
+    name: array
+    identifier: exp-array
+    parent: experimental
+weight: 11
+flux/v0.x/tags: [functions, array, package]
+cascade:
+  related:
+    - /flux/v0.x/data-types/composite/array/
+introduced: 0.79.0
+---
+
+The experimental `array` package provides functions for operating on Flux
+[arrays](/flux/v0.x/data-types/composite/array/).
+Import the `experimental/array` package:
+
+```js
+import "experimental/array"
+```
+
+## Functions
+
+{{< children type="functions" show="pages" >}}
diff --git a/content/flux/v0.x/stdlib/experimental/array/concat.md b/content/flux/v0.x/stdlib/experimental/array/concat.md
new file mode 100644
index 000000000..728554071
--- /dev/null
+++ b/content/flux/v0.x/stdlib/experimental/array/concat.md
@@ -0,0 +1,53 @@
+---
+title: array.concat() function
+description: >
+  `array.concat` appends two arrays and returns a new array.
+menu:
+  flux_0_x_ref:
+    name: array.concat
+    parent: exp-array
+weight: 301
+flux/v0.x/tags: [array]
+introduced: 0.155.0
+---
+
+`array.concat()` appends two arrays and returns a new array.
+
+```js
+import "experimental/array"
+
+array.concat(
+    arr: [1,2],
+    v: [3,4],
+)
+
+// Returns [1, 2, 3, 4]
+```
+
+## Parameters
+
+### arr {data-type="array"}
+First array. Default is the piped-forward array (`<-`).
+
+### v {data-type="array"}
+Array to append to the first array.
+
+{{% note %}}
+Neither input array is mutated and a new array is returned.
+{{% /note %}}
+
+## Examples
+
+### Merge two arrays
+```js
+import "experimental/array"
+
+a = [1, 2, 3]
+b = [4, 5, 6]
+
+c = a |> array.concat(v: b)
+// Returns [1, 2, 3, 4, 5, 6]
+
+// Output each value in the array as a row in a table
+array.from(rows: c |> array.map(fn: (x) => ({_value: x})))
+```
diff --git a/content/flux/v0.x/stdlib/experimental/array/filter.md b/content/flux/v0.x/stdlib/experimental/array/filter.md
new file mode 100644
index 000000000..0f7279f35
--- /dev/null
+++ b/content/flux/v0.x/stdlib/experimental/array/filter.md
@@ -0,0 +1,71 @@
+---
+title: array.filter() function
+description: >
+  `array.filter` iterates over an array, evaluates each element with a predicate
+  function, and then returns a new array with only elements that match the predicate.
+menu:
+  flux_0_x_ref:
+    name: array.filter
+    parent: exp-array
+weight: 301
+flux/v0.x/tags: [array]
+introduced: 0.155.0
+---
+
+`array.filter()` iterates over an array, evaluates each element with a predicate
+function, and then returns a new array with only elements that match the predicate.
+
+```js
+import "experimental/array"
+
+array.filter(
+    arr: [1, 2, 3, 4, 5],
+    fn: (x) => x >= 3,
+)
+
+// Returns [3, 4, 5]
+```
+
+## Parameters
+
+### arr {data-type="array"}
+Array to filter. Default is the piped-forward array (`<-`).
+
+### fn {data-type="function"}
+Predicate function to evaluate on each element.
+The element is represented by `x` in the predicate function.
+
+## Examples
+
+### Filter an array of integers
+```js
+import "experimental/array"
+
+a = [1, 2, 3, 4, 5]
+b = a |> array.filter(fn: (x) => x >= 3)
+// b returns [3, 4, 5]
+
+// Output the filtered array as a table
+array.from(rows: b |> array.map(fn: (x) => ({_value: x})))
+```
+
+### Filter an array of records
+```js
+import "experimental/array"
+
+a = 
+    [
+        {a: 1, b: 2, c: 3},
+        {a: 4, b: 5, c: 6},
+        {a: 7, b: 8, c: 9}
+    ]
+
+b = a |> array.filter(fn: (x) => x.b >= 3)
+// b returns [
+//    {a: 4, b: 5, c: 6},
+//    {a: 7, b: 8, c: 9},
+// ]
+
+// Output the filtered array as a table
+array.from(rows: b)
+```
diff --git a/content/flux/v0.x/stdlib/experimental/array/map.md b/content/flux/v0.x/stdlib/experimental/array/map.md
new file mode 100644
index 000000000..3ba8363de
--- /dev/null
+++ b/content/flux/v0.x/stdlib/experimental/array/map.md
@@ -0,0 +1,70 @@
+---
+title: array.map() function
+description: >
+  `array.map` iterates over an array, applies a function to each element to
+  produce a new element, and then returns a new array.
+menu:
+  flux_0_x_ref:
+    name: array.map
+    parent: exp-array
+weight: 301
+flux/v0.x/tags: [array]
+introduced: 0.155.0
+---
+
+`array.map()` iterates over an array, applies a function to each element to
+produce a new element, and then returns a new array.
+
+```js
+import "experimental/array"
+
+array.map(
+    arr: [1, 2, 3, 4],
+    fn: (x) => x * 2,
+)
+
+// Returns [2, 4, 6, 8]
+```
+
+## Parameters
+
+### arr {data-type="array"}
+Array to operate on. Default is the piped-forward array (`<-`).
+
+### fn {data-type="function"}
+Function to apply to elements. The element is represented by `x` in the function.
+
+## Examples
+
+### Convert an array of integers to an array of records
+```js
+import "experimental/array"
+
+a = [1, 2, 3, 4, 5]
+b = a |> array.map(fn: (x) => ({_value: x}))
+// b returns [{_value: 1}, {_value: 2}, {_value: 3}, {_value: 4}, {_value: 5}]
+
+// Output the array of records as a table
+> array.from(rows: b)
+```
+
+### Iterate over and modify an array of records
+```js
+a = 
+    [
+        {a: 1, b: 2, c: 3},
+        {a: 4, b: 5, c: 6},
+        {a: 7, b: 8, c: 9},
+    ]
+
+b = a |> array.map(fn: (x) => ({x with a: x.a * x.a, d: x.b + x.c}))
+// b returns:
+// [
+//     {a: 1, b: 2, c: 3, d: 5},
+//     {a: 16, b: 5, c: 6, d: 11},
+//     {a: 49, b: 8, c: 9, d: 17}
+// ]
+
+// Output the modified array of records as a table
+array.from(rows: b)
+```
diff --git a/content/flux/v0.x/stdlib/experimental/bigtable/from.md b/content/flux/v0.x/stdlib/experimental/bigtable/from.md
index 89e4c6d04..afc2a217f 100644
--- a/content/flux/v0.x/stdlib/experimental/bigtable/from.md
+++ b/content/flux/v0.x/stdlib/experimental/bigtable/from.md
@@ -21,10 +21,10 @@ data source.
 import "experimental/bigtable"
 
 bigtable.from(
-  token: "mySuPeRseCretTokEn",
-  project: "exampleProjectID",
-  instance: "exampleInstanceID",
-  table: "example-table"
+    token: "mySuPeRseCretTokEn",
+    project: "exampleProjectID",
+    instance: "exampleInstanceID",
+    table: "example-table",
 )
 ```
 
@@ -64,9 +64,9 @@ bigtable_project = secrets.get(key: "BIGTABLE_PROJECT_ID")
 bigtable_instance = secrets.get(key: "BIGTABLE_INSTANCE_ID")
 
 bigtable.from(
-  token: bigtable_token,
-  project: bigtable_project,
-  instance: bigtable_instance,
-  table: "example-table"
+    token: bigtable_token,
+    project: bigtable_project,
+    instance: bigtable_instance,
+    table: "example-table"
 )
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/bitwise/sand.md b/content/flux/v0.x/stdlib/experimental/bitwise/sand.md
index 81050692d..7e6121878 100644
--- a/content/flux/v0.x/stdlib/experimental/bitwise/sand.md
+++ b/content/flux/v0.x/stdlib/experimental/bitwise/sand.md
@@ -19,10 +19,7 @@ flux/v0.x/tags: [bitwise]
 ```js
 import "experimental/bitwise"
 
-bitwise.sand(
-  a: 12,
-  b: 21
-)
+bitwise.sand(a: 12, b: 21)
 
 // Returns 4
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/bitwise/sclear.md b/content/flux/v0.x/stdlib/experimental/bitwise/sclear.md
index e562f9eda..1042efe35 100644
--- a/content/flux/v0.x/stdlib/experimental/bitwise/sclear.md
+++ b/content/flux/v0.x/stdlib/experimental/bitwise/sclear.md
@@ -19,10 +19,7 @@ flux/v0.x/tags: [bitwise]
 ```js
 import "experimental/bitwise"
 
-bitwise.sclear(
-  a: 12,
-  b: 21
-)
+bitwise.sclear(a: 12, b: 21)
 
 // Returns 8
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/bitwise/slshift.md b/content/flux/v0.x/stdlib/experimental/bitwise/slshift.md
index 95369a9e8..4a525b0a2 100644
--- a/content/flux/v0.x/stdlib/experimental/bitwise/slshift.md
+++ b/content/flux/v0.x/stdlib/experimental/bitwise/slshift.md
@@ -19,10 +19,7 @@ Both `a` and `b` are [integers](/flux/v0.x/data-types/basic/int/).
 ```js
 import "experimental/bitwise"
 
-bitwise.slshift(
-  a: 12,
-  b: 21
-)
+bitwise.slshift(a: 12, b: 21)
 
 // Returns 25165824
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/bitwise/sor.md b/content/flux/v0.x/stdlib/experimental/bitwise/sor.md
index 2c95b3b81..81c9efaf1 100644
--- a/content/flux/v0.x/stdlib/experimental/bitwise/sor.md
+++ b/content/flux/v0.x/stdlib/experimental/bitwise/sor.md
@@ -19,10 +19,7 @@ flux/v0.x/tags: [bitwise]
 ```js
 import "experimental/bitwise"
 
-bitwise.sor(
-  a: 12,
-  b: 21
-)
+bitwise.sor(a: 12, b: 21)
 
 // Returns 29
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/bitwise/srshift.md b/content/flux/v0.x/stdlib/experimental/bitwise/srshift.md
index 3b3eec84b..47d8cdd10 100644
--- a/content/flux/v0.x/stdlib/experimental/bitwise/srshift.md
+++ b/content/flux/v0.x/stdlib/experimental/bitwise/srshift.md
@@ -19,10 +19,7 @@ Both `a` and `b` are [integers](/flux/v0.x/data-types/basic/int/).
 ```js
 import "experimental/bitwise"
 
-bitwise.srshift(
-  a: 21,
-  b: 4
-)
+bitwise.srshift(a: 21, b: 4)
 
 // Returns 1
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/bitwise/sxor.md b/content/flux/v0.x/stdlib/experimental/bitwise/sxor.md
index 58348918a..9419f65af 100644
--- a/content/flux/v0.x/stdlib/experimental/bitwise/sxor.md
+++ b/content/flux/v0.x/stdlib/experimental/bitwise/sxor.md
@@ -19,10 +19,7 @@ flux/v0.x/tags: [bitwise]
 ```js
 import "experimental/bitwise"
 
-bitwise.sxor(
-  a: 12,
-  b: 21
-)
+bitwise.sxor(a: 12, b: 21)
 
 // Returns 25
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/bitwise/uand.md b/content/flux/v0.x/stdlib/experimental/bitwise/uand.md
index 9490f90e1..21f4f79fa 100644
--- a/content/flux/v0.x/stdlib/experimental/bitwise/uand.md
+++ b/content/flux/v0.x/stdlib/experimental/bitwise/uand.md
@@ -19,10 +19,7 @@ flux/v0.x/tags: [bitwise]
 ```js
 import "experimental/bitwise"
 
-bitwise.uand(
-  a: uint(v: 12),
-  b: uint(v: 21)
-)
+bitwise.uand(a: uint(v: 12), b: uint(v: 21))
 
 // Returns 4 (uint)
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/bitwise/uclear.md b/content/flux/v0.x/stdlib/experimental/bitwise/uclear.md
index 7a84a917f..14d1e7dd3 100644
--- a/content/flux/v0.x/stdlib/experimental/bitwise/uclear.md
+++ b/content/flux/v0.x/stdlib/experimental/bitwise/uclear.md
@@ -19,10 +19,7 @@ flux/v0.x/tags: [bitwise]
 ```js
 import "experimental/bitwise"
 
-bitwise.uclear(
-  a: uint(v: 12),
-  b: uint(v: 21)
-)
+bitwise.uclear(a: uint(v: 12), b: uint(v: 21))
 
 // Returns 8 (uint)
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/bitwise/ulshift.md b/content/flux/v0.x/stdlib/experimental/bitwise/ulshift.md
index 0d447d2c9..8ff36cbcf 100644
--- a/content/flux/v0.x/stdlib/experimental/bitwise/ulshift.md
+++ b/content/flux/v0.x/stdlib/experimental/bitwise/ulshift.md
@@ -19,10 +19,7 @@ Both `a` and `b` are [unsigned integers](/flux/v0.x/data-types/basic/uint/).
 ```js
 import "experimental/bitwise"
 
-bitwise.ulshift(
-  a: uint(v: 12),
-  b: uint(v: 21)
-)
+bitwise.ulshift(a: uint(v: 12), b: uint(v: 21))
 
 // Returns 25165824 (uint)
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/bitwise/uor.md b/content/flux/v0.x/stdlib/experimental/bitwise/uor.md
index a2347a303..904de179c 100644
--- a/content/flux/v0.x/stdlib/experimental/bitwise/uor.md
+++ b/content/flux/v0.x/stdlib/experimental/bitwise/uor.md
@@ -19,10 +19,7 @@ flux/v0.x/tags: [bitwise]
 ```js
 import "experimental/bitwise"
 
-bitwise.uor(
-  a: uint(v: 12),
-  b: uint(v: 21)
-)
+bitwise.uor(a: uint(v: 12), b: uint(v: 21))
 
 // Returns 29 (uint)
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/bitwise/urshift.md b/content/flux/v0.x/stdlib/experimental/bitwise/urshift.md
index b751a6cc6..78ff29c0c 100644
--- a/content/flux/v0.x/stdlib/experimental/bitwise/urshift.md
+++ b/content/flux/v0.x/stdlib/experimental/bitwise/urshift.md
@@ -19,10 +19,7 @@ Both `a` and `b` are [unsigned integers](/flux/v0.x/data-types/basic/uint/).
 ```js
 import "experimental/bitwise"
 
-bitwise.urshift(
-  a: uint(v: 21),
-  b: uint(v: 4)
-)
+bitwise.urshift(a: uint(v: 21), b: uint(v: 4))
 
 // Returns 1 (uint)
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/bitwise/uxor.md b/content/flux/v0.x/stdlib/experimental/bitwise/uxor.md
index 7ded84782..e362a4fc0 100644
--- a/content/flux/v0.x/stdlib/experimental/bitwise/uxor.md
+++ b/content/flux/v0.x/stdlib/experimental/bitwise/uxor.md
@@ -19,10 +19,7 @@ flux/v0.x/tags: [bitwise]
 ```js
 import "experimental/bitwise"
 
-bitwise.uxor(
-  a: uint(v: 12),
-  b: uint(v: 21)
-)
+bitwise.uxor(a: uint(v: 12), b: uint(v: 21))
 
 // Returns 25 (uint)
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/chain.md b/content/flux/v0.x/stdlib/experimental/chain.md
index b29c334d7..5c1e4e02d 100644
--- a/content/flux/v0.x/stdlib/experimental/chain.md
+++ b/content/flux/v0.x/stdlib/experimental/chain.md
@@ -29,8 +29,8 @@ the results of the first query are met.
 import "experimental"
 
 experimental.chain(
-  first: query1,
-  second: query2
+    first: query1,
+    second: query2,
 )
 ```
 
@@ -49,18 +49,15 @@ The second query to execute.
 import "experimental"
 
 downsampled_max = from(bucket: "example-bucket-1")
-  |> range(start: -1d)
-  |> filter(fn: (r) => r._measurement == "example-measurement")
-  |> aggregateWindow(every: 1h, fn: max)
-  |> to(bucket: "downsample-1h-max", org: "example-org")
+    |> range(start: -1d)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> aggregateWindow(every: 1h, fn: max)
+    |> to(bucket: "downsample-1h-max", org: "example-org")
 
 average_max = from(bucket: "downsample-1h-max")
-  |> range(start: -1d)
-  |> filter(fn: (r) => r.measurement == "example-measurement")
-  |> mean()
+    |> range(start: -1d)
+    |> filter(fn: (r) => r.measurement == "example-measurement")
+    |> mean()
 
-experimental.chain(
-  first: downsampled_max,
-  second: average_max
-)
+experimental.chain(first: downsampled_max, second: average_max)
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/count.md b/content/flux/v0.x/stdlib/experimental/count.md
index 9b09ffbfa..95563a663 100644
--- a/content/flux/v0.x/stdlib/experimental/count.md
+++ b/content/flux/v0.x/stdlib/experimental/count.md
@@ -52,6 +52,6 @@ Default is piped-forward data (`<-`).
 import "experimental"
 
 from(bucket: "example-bucket")
-  |> range(start: -5m)
-  |> experimental.count()
+    |> range(start: -5m)
+    |> experimental.count()
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/csv/from.md b/content/flux/v0.x/stdlib/experimental/csv/from.md
index e19d02b3b..65ee82ccf 100644
--- a/content/flux/v0.x/stdlib/experimental/csv/from.md
+++ b/content/flux/v0.x/stdlib/experimental/csv/from.md
@@ -43,15 +43,5 @@ The URL to retrieve annotated CSV from.
 import "experimental/csv"
 
 csv.from(url: "http://example.com/csv/example.csv")
-  |> filter(fn: (r) => r._measurement == "example-measurement")
-```
-
-## Function definition
-```js
-package csv
-
-import c "csv"
-import "experimental/http"
-
-from = (url) => c.from(csv: string(v: http.get(url: url).body))
+    |> filter(fn: (r) => r._measurement == "example-measurement")
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/distinct.md b/content/flux/v0.x/stdlib/experimental/distinct.md
index 5b9572b82..5d439dfca 100644
--- a/content/flux/v0.x/stdlib/experimental/distinct.md
+++ b/content/flux/v0.x/stdlib/experimental/distinct.md
@@ -53,7 +53,7 @@ Default is piped-forward data (`<-`).
 import "experimental"
 
 data
-	|> experimental.distinct()
+    |> experimental.distinct()
 ```
 
 {{< flex >}}
diff --git a/content/flux/v0.x/stdlib/experimental/fill.md b/content/flux/v0.x/stdlib/experimental/fill.md
index c0dc94d2e..b0426f952 100644
--- a/content/flux/v0.x/stdlib/experimental/fill.md
+++ b/content/flux/v0.x/stdlib/experimental/fill.md
@@ -61,7 +61,7 @@ Default is piped-forward data (`<-`).
 import "experimental"
 
 data
-  |> experimental.fill(value: 0.0)
+    |> experimental.fill(value: 0.0)
 ```
 
 {{< flex >}}
@@ -96,7 +96,7 @@ data
 import "experimental"
 
 data
-  |> experimental.fill(usePrevious: true)
+    |> experimental.fill(usePrevious: true)
 ```
 
 {{< flex >}}
diff --git a/content/flux/v0.x/stdlib/experimental/first.md b/content/flux/v0.x/stdlib/experimental/first.md
index 6f22eab9d..5a0f420bf 100644
--- a/content/flux/v0.x/stdlib/experimental/first.md
+++ b/content/flux/v0.x/stdlib/experimental/first.md
@@ -47,7 +47,7 @@ Default is piped-forward data (`<-`).
 import "experimental"
 
 data
-  |> experimental.first()
+    |> experimental.first()
 ```
 
 {{< flex >}}
diff --git a/content/flux/v0.x/stdlib/experimental/geo/_index.md b/content/flux/v0.x/stdlib/experimental/geo/_index.md
index 56544565d..3bb01fa45 100644
--- a/content/flux/v0.x/stdlib/experimental/geo/_index.md
+++ b/content/flux/v0.x/stdlib/experimental/geo/_index.md
@@ -88,11 +88,11 @@ to add `s2_cell_id` tags to data that includes fields with latitude and longitud
 
 ```js
 //...
-  |> shapeData(
-    latField: "latitude",
-    lonField: "longitude",
-    level: 10
-  )
+    |> shapeData(
+        latField: "latitude",
+        lonField: "longitude",
+        level: 10,
+    )
 ```
 
 ## Latitude and longitude values
@@ -123,10 +123,10 @@ Define a box-shaped region by specifying a record containing the following prope
 ##### Example box-shaped region
 ```js
 {
-  minLat: 40.51757813,
-  maxLat: 40.86914063,
-  minLon: -73.65234375,
-  maxLon: -72.94921875
+    minLat: 40.51757813,
+    maxLat: 40.86914063,
+    minLon: -73.65234375,
+    maxLon: -72.94921875,
 }
 ```
 
@@ -140,9 +140,9 @@ Define a circular region by specifying a record containing the following propert
 ##### Example circular region
 ```js
 {
-  lat: 40.69335938,
-  lon: -73.30078125,
-  radius: 20.0
+    lat: 40.69335938,
+    lon: -73.30078125,
+    radius: 20.0,
 }
 ```
 
@@ -155,8 +155,8 @@ Define a point region by specifying a record containing the following properties
 ##### Example point region
 ```js
 {
-  lat: 40.671659,
-  lon: -73.936631
+    lat: 40.671659,
+    lon: -73.936631,
 }
 ```
 
@@ -173,11 +173,11 @@ Define a custom polygon region using a record containing the following propertie
 ##### Example polygonal region
 ```js
 {
-  points: [
-    {lat: 40.671659, lon: -73.936631},
-    {lat: 40.706543, lon: -73.749177},
-    {lat: 40.791333, lon: -73.880327}
-  ]
+    points: [
+        {lat: 40.671659, lon: -73.936631},
+        {lat: 40.706543, lon: -73.749177},
+        {lat: 40.791333, lon: -73.880327},
+    ],
 }
 ```
 
@@ -195,9 +195,7 @@ Define a geographic linestring path using a record containing the following prop
   coordinate pairs (`lon lat,`):
 
 ```js
-{
-  linestring: "39.7515 14.01433, 38.3527 13.9228, 36.9978 15.08433"
-}
+{linestring: "39.7515 14.01433, 38.3527 13.9228, 36.9978 15.08433"}
 ```
 
 ## Distance units
diff --git a/content/flux/v0.x/stdlib/experimental/geo/astracks.md b/content/flux/v0.x/stdlib/experimental/geo/astracks.md
index 4e98719b8..d1a8023d6 100644
--- a/content/flux/v0.x/stdlib/experimental/geo/astracks.md
+++ b/content/flux/v0.x/stdlib/experimental/geo/astracks.md
@@ -22,8 +22,8 @@ The `geo.asTracks()` function groups rows into tracks (sequential, related data
 import "experimental/geo"
 
 geo.asTracks(
-  groupBy: ["id","tid"],
-  orderBy: ["_time"]
+    groupBy: ["id","tid"],
+    orderBy: ["_time"],
 )
 ```
 
@@ -46,27 +46,13 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 
 ##### Group tracks in a box-shaped region
 ```js
-import "experimental/geo"
 
-region = {
-  minLat: 40.51757813,
-  maxLat: 40.86914063,
-  minLon: -73.65234375,
-  maxLon: -72.94921875
-}
+region = {minLat: 40.51757813, maxLat: 40.86914063, minLon: -73.65234375, maxLon: -72.94921875}
 
 from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "example-measurement")
-  |> geo.gridFilter(region: region)
-  |> geo.toRows(correlationKey: ["_time", "id"])
-  |> geo.asTracks()
-```
-
-## Function definition
-```js
-asTracks = (tables=<-, groupBy=["id","tid"], orderBy=["_time"]) =>
-  tables
-    |> group(columns: groupBy)
-    |> sort(columns: orderBy)
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> geo.gridFilter(region: region)
+    |> geo.toRows(correlationKey: ["_time", "id"])
+    |> geo.asTracks()
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/geo/filterrows.md b/content/flux/v0.x/stdlib/experimental/geo/filterrows.md
index fcf602ffa..1889b3ccf 100644
--- a/content/flux/v0.x/stdlib/experimental/geo/filterrows.md
+++ b/content/flux/v0.x/stdlib/experimental/geo/filterrows.md
@@ -28,13 +28,13 @@ and [`geo.strictFilter()`](/flux/v0.x/stdlib/experimental/geo/strictfilter/).
 import "experimental/geo"
 
 geo.filterRows(
-  region: {lat: 40.69335938, lon: -73.30078125, radius: 20.0},
-  minSize: 24,
-  maxSize: -1,
-  level: -1,
-  s2cellIDLevel: -1,
-  correlationKey: ["_time"],
-  strict: true
+    region: {lat: 40.69335938, lon: -73.30078125, radius: 20.0},
+    minSize: 24,
+    maxSize: -1,
+    level: -1,
+    s2cellIDLevel: -1,
+    correlationKey: ["_time"],
+    strict: true,
 )
 ```
 
@@ -48,7 +48,7 @@ To add `s2_cell_id` to the group key, use [`experimental.group`](/flux/v0.x/stdl
 import "experimental"
 
 // ...
-  |> experimental.group(columns: ["s2_cell_id"], mode: "extend")
+    |> experimental.group(columns: ["s2_cell_id"], mode: "extend")
 ```
 {{% /note %}}
 
@@ -123,21 +123,20 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 
 ## Examples
 
+- [Strictly filter data in a box-shaped region](#strictly-filter-data-in-a-box-shaped-region)
+- [Approximately filter data in a circular region](#approximately-filter-data-in-a-circular-region)
+- [Filter data in a polygonal region](#filter-data-in-a-polygonal-region)
+
 ##### Strictly filter data in a box-shaped region
 ```js
 import "experimental/geo"
 
+region = {minLat: 40.51757813, maxLat: 40.86914063, minLon: -73.65234375, maxLon: -72.94921875}
+
 from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "example-measurement")
-  |> geo.filterRows(
-    region: {
-      minLat: 40.51757813,
-      maxLat: 40.86914063,
-      minLon: -73.65234375,
-      maxLon: -72.94921875
-    }
-  )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> geo.filterRows(region: region)
 ```
 
 ##### Approximately filter data in a circular region
@@ -147,78 +146,24 @@ covered by the defined region even though some points my be located outside of t
 ```js
 import "experimental/geo"
 
+region = {lat: 40.69335938, lon: -73.30078125, radius: 20.0}
+
 from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "example-measurement")
-  |> geo.filterRows(
-    region: {
-      lat: 40.69335938,
-      lon: -73.30078125,
-      radius: 20.0
-    }
-    strict: false
-  )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> geo.filterRows(region: region, strict: false)
 ```
 
 ##### Filter data in a polygonal region
 ```js
 import "experimental/geo"
 
-from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "example-measurement")
-  |> geo.filterRows(
-    region: {
-      points: [
-        {lat: 40.671659, lon: -73.936631},
-        {lat: 40.706543, lon: -73.749177},
-        {lat: 40.791333, lon: -73.880327}
-      ]
-    }
-  )
-```
-
-## Function definition
-{{% truncate %}}
-```js
-filterRows = (
-  tables=<-,
-  region,
-  minSize=24,
-  maxSize=-1,
-  level=-1,
-  s2cellIDLevel=-1,
-  strict=true
-) => {
-  _columns =
-    |> columns(column: "_value")
-    |> tableFind(fn: (key) => true )
-    |> getColumn(column: "_value")
-  _rows =
-    if contains(value: "lat", set: _columns) then
-      tables
-        |> gridFilter(
-          region: region,
-          minSize: minSize,
-          maxSize: maxSize,
-          level: level,
-          s2cellIDLevel: s2cellIDLevel)
-    else
-      tables
-        |> gridFilter(
-          region: region,
-          minSize: minSize,
-          maxSize: maxSize,
-          level: level,
-          s2cellIDLevel: s2cellIDLevel)
-        |> toRows()
-  _result =
-    if strict then
-      _rows
-        |> strictFilter(region)
-    else
-      _rows
-  return _result
+region = {
+    points: [{lat: 40.671659, lon: -73.936631}, {lat: 40.706543, lon: -73.749177}, {lat: 40.791333, lon: -73.880327}],
 }
+
+from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> geo.filterRows(region: region)
 ```
-{{% /truncate %}}
diff --git a/content/flux/v0.x/stdlib/experimental/geo/gridfilter.md b/content/flux/v0.x/stdlib/experimental/geo/gridfilter.md
index f683072b7..8722458c0 100644
--- a/content/flux/v0.x/stdlib/experimental/geo/gridfilter.md
+++ b/content/flux/v0.x/stdlib/experimental/geo/gridfilter.md
@@ -34,11 +34,11 @@ _See [Non-strict and strict filtering](#non-strict-and-strict-filtering) below._
 import "experimental/geo"
 
 geo.gridFilter(
-  region: {lat: 40.69335938, lon: -73.30078125, radius: 20.0}
-  minSize: 24,
-  maxSize: -1,
-  level: -1,
-  s2cellIDLevel: -1
+    region: {lat: 40.69335938, lon: -73.30078125, radius: 20.0}
+    minSize: 24,
+    maxSize: -1,
+    level: -1,
+    s2cellIDLevel: -1,
 )
 ```
 
@@ -52,7 +52,7 @@ To add `s2_cell_id` to the group key, use [`experimental.group`](/flux/v0.x/stdl
 import "experimental"
 
 // ...
-  |> experimental.group(columns: ["s2_cell_id"], mode: "extend")
+    |> experimental.group(columns: ["s2_cell_id"], mode: "extend")
 ```
 {{% /note %}}
 
@@ -116,53 +116,44 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 
 ## Examples
 
+- [Filter data in a box-shaped region](#filter-data-in-a-box-shaped-region)
+- [Filter data in a circular region](#filter-data-in-a-circular-region)
+- [Filter data in a custom polygon region](#filter-data-in-a-custom-polygon-region)
+
 ##### Filter data in a box-shaped region
 ```js
 import "experimental/geo"
 
+region = {minLat: 40.51757813, maxLat: 40.86914063, minLon: -73.65234375, maxLon: -72.94921875}
+
 from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "example-measurement")
-  |> geo.gridFilter(
-    region: {
-      minLat: 40.51757813,
-      maxLat: 40.86914063,
-      minLon: -73.65234375,
-      maxLon: -72.94921875
-    }
-  )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> geo.gridFilter(region: region)
 ```
 
 ##### Filter data in a circular region
 ```js
 import "experimental/geo"
 
+region = {lat: 40.69335938, lon: -73.30078125, radius: 20.0}
+
 from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "example-measurement")
-  |> geo.gridFilter(
-    region: {
-      lat: 40.69335938,
-      lon: -73.30078125,
-      radius: 20.0
-    }
-  )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> geo.gridFilter(region: region)
 ```
 
 ##### Filter data in a custom polygon region
 ```js
 import "experimental/geo"
 
+region = {
+    points: [{lat: 40.671659, lon: -73.936631}, {lat: 40.706543, lon: -73.749177}, {lat: 40.791333, lon: -73.880327}],
+}
+
 from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "example-measurement")
-  |> geo.gridFilter(
-    region: {
-      points: [
-        {lat: 40.671659, lon: -73.936631},
-        {lat: 40.706543, lon: -73.749177},
-        {lat: 40.791333, lon: -73.880327}
-      ]
-    }
-  )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> geo.gridFilter(region: region)
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/geo/groupbyarea.md b/content/flux/v0.x/stdlib/experimental/geo/groupbyarea.md
index f1c7ee22a..1d94fc576 100644
--- a/content/flux/v0.x/stdlib/experimental/geo/groupbyarea.md
+++ b/content/flux/v0.x/stdlib/experimental/geo/groupbyarea.md
@@ -25,9 +25,9 @@ Results are grouped by `newColumn`.
 import "experimental/geo"
 
 geo.groupByArea(
-  newColumn: "geoArea",
-  level: 3,
-  s2cellIDLevel: -1
+    newColumn: "geoArea",
+    level: 3,
+    s2cellIDLevel: -1,
 )
 ```
 
@@ -56,17 +56,12 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 ```js
 import "experimental/geo"
 
-region = {
-  minLat: 40.51757813,
-  maxLat: 40.86914063,
-  minLon: -73.65234375,
-  maxLon: -72.94921875
-}
+region = {minLat: 40.51757813, maxLat: 40.86914063, minLon: -73.65234375, maxLon: -72.94921875}
 
 from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "example-measurement")
-  |> geo.gridFilter(region: region)
-  |> geo.toRows()
-  |> geo.groupByArea(newColumn: "geoArea", level: 3)
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> geo.gridFilter(region: region)
+    |> geo.toRows()
+    |> geo.groupByArea(newColumn: "geoArea", level: 3)
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/geo/s2cellidtoken.md b/content/flux/v0.x/stdlib/experimental/geo/s2cellidtoken.md
index 1f94b5b78..ec0631b2c 100644
--- a/content/flux/v0.x/stdlib/experimental/geo/s2cellidtoken.md
+++ b/content/flux/v0.x/stdlib/experimental/geo/s2cellidtoken.md
@@ -22,8 +22,8 @@ The `geo.s2CellIDToken()` function returns an S2 cell ID token.
 import "experimental/geo"
 
 geo.s2CellIDToken(
-  point: {lat: 37.7858229, lon: -122.4058124},
-  level: 10
+    point: {lat: 37.7858229, lon: -122.4058124},
+    level: 10,
 )
 ```
 
@@ -53,15 +53,9 @@ when generating the S2 cell ID token.
 import "experimental/geo"
 
 from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "example-measurement")
-  |> map(fn: (r) => ({
-    r with
-    s2_cell_id: geo.s2CellIDToken(
-      point: {lat: r.lat, lon: r.lon},
-      level: 10
-    )})
-  )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> map(fn: (r) => ({r with s2_cell_id: geo.s2CellIDToken(point: {lat: r.lat, lon: r.lon}, level: 10)}))
 ```
 
 ##### Update S2 cell ID token level
@@ -69,13 +63,7 @@ from(bucket: "example-bucket")
 import "experimental/geo"
 
 from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "example-measurement")
-  |> map(fn: (r) => ({
-    r with
-    s2_cell_id: geo.s2CellIDToken(
-      token: r.s2_cell_id,
-      level: 10
-    )})
-  )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> map(fn: (r) => ({r with s2_cell_id: geo.s2CellIDToken(token: r.s2_cell_id, level: 10)}))
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/geo/s2celllatlon.md b/content/flux/v0.x/stdlib/experimental/geo/s2celllatlon.md
index 3f76c25b2..2a982491b 100644
--- a/content/flux/v0.x/stdlib/experimental/geo/s2celllatlon.md
+++ b/content/flux/v0.x/stdlib/experimental/geo/s2celllatlon.md
@@ -23,9 +23,7 @@ center of an S2 cell.
 ```js
 import "experimental/geo"
 
-geo.s2CellLatLon(
-  token: "89c284"
-)
+geo.s2CellLatLon(token: "89c284")
 
 // Returns {lat: 40.812535546624574, lon: -73.55941282728273}
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/geo/shapedata.md b/content/flux/v0.x/stdlib/experimental/geo/shapedata.md
index 9a1e23760..c503d633d 100644
--- a/content/flux/v0.x/stdlib/experimental/geo/shapedata.md
+++ b/content/flux/v0.x/stdlib/experimental/geo/shapedata.md
@@ -32,9 +32,9 @@ Use `geo.shapeData()` to ensure geo-temporal data meets the
 import "experimental/geo"
 
 geo.shapeData(
-  latField: "latitude",
-  lonField: "longitude",
-  level: 10
+    latField: "latitude",
+    lonField: "longitude",
+    level: 10,
 )
 ```
 
@@ -63,13 +63,9 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "experimental/geo"
 
 from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "example-measurement")
-  |> geo.shapeData(
-    latField: "latitude",
-    lonField: "longitude",
-    level: 10
-  )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> geo.shapeData(latField: "latitude", lonField: "longitude", level: 10)
 ```
 
 ### geo.shapeData input and output
@@ -92,14 +88,15 @@ from(bucket: "example-bucket")
 {{% /flex-content %}}
 {{% flex-content %}}
 
-**The following function would output:**
+**The following would output:**
 
 ```js
-|> geo.shapeData(
-  latField: "latitude",
-  lonField: "longitude",
-  level: 5
-)
+data
+    |> geo.shapeData(
+        latField: "latitude",
+        lonField: "longitude",
+        level: 5,
+    )
 ```
 
 | _time | lat      | lon       | s2_cell_id |
diff --git a/content/flux/v0.x/stdlib/experimental/geo/st_contains.md b/content/flux/v0.x/stdlib/experimental/geo/st_contains.md
index 1602b1934..b7260e593 100644
--- a/content/flux/v0.x/stdlib/experimental/geo/st_contains.md
+++ b/content/flux/v0.x/stdlib/experimental/geo/st_contains.md
@@ -24,8 +24,8 @@ geographic information system (GIS) geometry and returns `true` or `false`.
 import "experimental/geo"
 
 geo.ST_Contains(
-  region: {lat: 40.7, lon: -73.3, radius: 20.0},
-  geometry: {lon: 39.7515, lat: 15.08433}
+    region: {lat: 40.7, lon: -73.3, radius: 20.0},
+    geometry: {lon: 39.7515, lat: 15.08433},
 )
 
 // Returns false
@@ -47,38 +47,24 @@ _See [GIS geometry definitions](/flux/v0.x/stdlib/experimental/geo/#gis-geometry
 
 ##### Test if geographic points are inside of a region
 ```js
-import "experimental/geo"
+iimport "experimental/geo"
 
-region = {
-  minLat: 40.51757813,
-  maxLat: 40.86914063,
-  minLon: -73.65234375,
-  maxLon: -72.94921875
-}
+region = {minLat: 40.51757813, maxLat: 40.86914063, minLon: -73.65234375, maxLon: -72.94921875}
 
 data
-  |> geo.toRows()
-  |> map(fn: (r) => ({
-    r with st_contains: geo.ST_Contains(region: region, geometry: {lat: r.lat, lon: r.lon})
-  }))
+    |> geo.toRows()
+    |> map(fn: (r) => ({r with st_contains: geo.ST_Contains(region: region, geometry: {lat: r.lat, lon: r.lon})}))
 ```
 
 ##### Test if tracks are inside of a region
 ```js
 import "experimental/geo"
 
-region = {
-  minLat: 40.51757813,
-  maxLat: 40.86914063,
-  minLon: -73.65234375,
-  maxLon: -72.94921875
-}
+region = {minLat: 40.51757813, maxLat: 40.86914063, minLon: -73.65234375, maxLon: -72.94921875}
 
 data
-  |> geo.toRows()
-  |> geo.asTracks()
-  |> geo.ST_LineString()
-  |> map(fn: (r) => ({
-    r with st_contains: geo.ST_Contains(region: region, geometry: {linestring: r.st_linestring})
-  }))
+    |> geo.toRows()
+    |> geo.asTracks()
+    |> geo.ST_LineString()
+    |> map(fn: (r) => ({r with st_contains: geo.ST_Contains(region: region, geometry: {linestring: r.st_linestring})}))
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/geo/st_distance.md b/content/flux/v0.x/stdlib/experimental/geo/st_distance.md
index 5aeaaf99d..5cc637306 100644
--- a/content/flux/v0.x/stdlib/experimental/geo/st_distance.md
+++ b/content/flux/v0.x/stdlib/experimental/geo/st_distance.md
@@ -25,8 +25,8 @@ Define distance units with the [`geo.units` option](/flux/v0.x/stdlib/experiment
 import "experimental/geo"
 
 geo.ST_Distance(
-  region: {lat: 40.7, lon: -73.3, radius: 20.0},
-  geometry: {lon: 39.7515, lat: 15.08433}
+    region: {lat: 40.7, lon: -73.3, radius: 20.0},
+    geometry: {lon: 39.7515, lat: 15.08433},
 )
 
 // Returns 10734.184618677662 (km)
@@ -50,18 +50,11 @@ _See [GIS geometry definitions](/flux/v0.x/stdlib/experimental/geo/#gis-geometry
 ```js
 import "experimental/geo"
 
-region = {
-  minLat: 40.51757813,
-  maxLat: 40.86914063,
-  minLon: -73.65234375,
-  maxLon: -72.94921875
-}
+region = {minLat: 40.51757813, maxLat: 40.86914063, minLon: -73.65234375, maxLon: -72.94921875}
 
 data
-  |> geo.toRows()
-  |> map(fn: (r) => ({
-    r with st_distance: ST_Distance(region: region, geometry: {lat: r.lat, lon: r.lon})
-  }))
+    |> geo.toRows()
+    |> map(fn: (r) => ({r with st_distance: ST_Distance(region: region, geometry: {lat: r.lat, lon: r.lon})}))
 ```
 
 ##### Find the point nearest to a geographic location
@@ -71,9 +64,7 @@ import "experimental/geo"
 fixedLocation = {lat: 40.7, lon: -73.3}
 
 data
-  |> geo.toRows()
-  |> map(fn: (r) => ({ r with
-    _value: geo.ST_Distance(region: {lat: r.lat, lon: r.lon}, geometry: fixedLocation)
-  }))
-  |> min()
+    |> geo.toRows()
+    |> map(fn: (r) => ({r with _value: geo.ST_Distance(region: {lat: r.lat, lon: r.lon}, geometry: fixedLocation)}))
+    |> min()
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/geo/st_dwithin.md b/content/flux/v0.x/stdlib/experimental/geo/st_dwithin.md
index c7827a7c3..26ae6ff5c 100644
--- a/content/flux/v0.x/stdlib/experimental/geo/st_dwithin.md
+++ b/content/flux/v0.x/stdlib/experimental/geo/st_dwithin.md
@@ -26,9 +26,9 @@ returns `true` or `false`.
 import "experimental/geo"
 
 geo.ST_DWithin(
-  region: {lat: 40.7, lon: -73.3, radius: 20.0},
-  geometry: {lon: 39.7515, lat: 15.08433},
-  distance: 1000.0
+    region: {lat: 40.7, lon: -73.3, radius: 20.0},
+    geometry: {lon: 39.7515, lat: 15.08433},
+    distance: 1000.0,
 )
 
 // Returns false
@@ -56,16 +56,12 @@ _Define distance units with the [`geo.units` option](/flux/v0.x/stdlib/experimen
 ```js
 import "experimental/geo"
 
-region = {
-  minLat: 40.51757813,
-  maxLat: 40.86914063,
-  minLon: -73.65234375,
-  maxLon: -72.94921875
-}
+region = {minLat: 40.51757813, maxLat: 40.86914063, minLon: -73.65234375, maxLon: -72.94921875}
 
 data
-  |> geo.toRows()
-  |> map(fn: (r) => ({
-    r with st_within: geo.ST_DWithin(region: box, geometry: {lat: r.lat, lon: r.lon}, distance: 15.0)
-  }))
+    |> geo.toRows()
+    |> map(
+        fn: (r) =>
+            ({r with st_within: geo.ST_DWithin(region: box, geometry: {lat: r.lat, lon: r.lon}, distance: 15.0)}),
+    )
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/geo/st_intersects.md b/content/flux/v0.x/stdlib/experimental/geo/st_intersects.md
index 06faa952b..e3478eb54 100644
--- a/content/flux/v0.x/stdlib/experimental/geo/st_intersects.md
+++ b/content/flux/v0.x/stdlib/experimental/geo/st_intersects.md
@@ -24,8 +24,8 @@ system (GIS) geometry intersects with the specified region and returns `true` or
 import "experimental/geo"
 
 geo.ST_Intersects(
-  region: {lat: 40.7, lon: -73.3, radius: 20.0},
-  geometry: {linestring: "39.7515 14.01433, 38.3527 13.9228, 36.9978 15.08433"}
+    region: {lat: 40.7, lon: -73.3, radius: 20.0},
+    geometry: {linestring: "39.7515 14.01433, 38.3527 13.9228, 36.9978 15.08433"},
 )
 
 // Returns false
@@ -49,16 +49,9 @@ _See [GIS geometry definitions](/flux/v0.x/stdlib/experimental/geo/#gis-geometry
 ```js
 import "experimental/geo"
 
-region = {
-  minLat: 40.51757813,
-  maxLat: 40.86914063,
-  minLon: -73.65234375,
-  maxLon: -72.94921875
-}
+region = {minLat: 40.51757813, maxLat: 40.86914063, minLon: -73.65234375, maxLon: -72.94921875}
 
 data
-  |> geo.toRows()
-  |> map(fn: (r) => ({
-    r with st_within: geo.ST_Intersects(region: box, geometry: {lat: r.lat, lon: r.lon})
-  }))
+    |> geo.toRows()
+    |> map(fn: (r) => ({r with st_within: geo.ST_Intersects(region: box, geometry: {lat: r.lat, lon: r.lon})}))
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/geo/st_length.md b/content/flux/v0.x/stdlib/experimental/geo/st_length.md
index f22288091..4af99385d 100644
--- a/content/flux/v0.x/stdlib/experimental/geo/st_length.md
+++ b/content/flux/v0.x/stdlib/experimental/geo/st_length.md
@@ -25,7 +25,7 @@ Define distance units with the [`geo.units` option](/flux/v0.x/stdlib/experiment
 import "experimental/geo"
 
 geo.ST_Length(
-  geometry: {linestring: "39.7515 14.01433, 38.3527 13.9228, 36.9978 15.08433"}
+    geometry: {linestring: "39.7515 14.01433, 38.3527 13.9228, 36.9978 15.08433"},
 )
 
 // Returns 346.1023974652474 (km)
@@ -45,18 +45,11 @@ _See [GIS geometry definitions](/flux/v0.x/stdlib/experimental/geo/#gis-geometry
 ```js
 import "experimental/geo"
 
-region = {
-  minLat: 40.51757813,
-  maxLat: 40.86914063,
-  minLon: -73.65234375,
-  maxLon: -72.94921875
-}
+region = {minLat: 40.51757813, maxLat: 40.86914063, minLon: -73.65234375, maxLon: -72.94921875}
 
 data
-  |> geo.toRows()
-  |> geo.asTracks()
-  |> geo.ST_LineString()
-  |> map(fn: (r) => ({
-    r with st_length: geo.ST_Length(geometry: {linestring: r.st_linestring})
-  }))
+    |> geo.toRows()
+    |> geo.asTracks()
+    |> geo.ST_LineString()
+    |> map(fn: (r) => ({r with st_length: geo.ST_Length(geometry: {linestring: r.st_linestring})}))
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/geo/st_linestring.md b/content/flux/v0.x/stdlib/experimental/geo/st_linestring.md
index 95ddd20a3..7d12dd928 100644
--- a/content/flux/v0.x/stdlib/experimental/geo/st_linestring.md
+++ b/content/flux/v0.x/stdlib/experimental/geo/st_linestring.md
@@ -47,7 +47,7 @@ geo.ST_LineString()
 import "experimental/geo"
 
 data
-  |> geo.ST_LineString()
+    |> geo.ST_LineString()
 ```
 
 ##### Output data
@@ -55,18 +55,3 @@ data
 | id    | st_linestring                                       |
 |:--    |:-------------                                       |
 | a213b | 39.7515 14.01433, 38.3527 13.9228, 36.9978 15.08433 |
-
-## Function definition
-```js
-ST_LineString = (tables=<-) =>
-  tables
-    |> reduce(fn: (r, accumulator) => ({
-        __linestring: accumulator.__linestring + (if accumulator.__count > 0 then ", " else "") + string(v: r.lat) + " " + string(v: r.lon),
-        __count: accumulator.__count + 1
-      }), identity: {
-        __linestring: "",
-        __count: 0
-      }
-    )
-    |> rename(columns: {__linestring: "st_linestring"})
-```
diff --git a/content/flux/v0.x/stdlib/experimental/geo/strictfilter.md b/content/flux/v0.x/stdlib/experimental/geo/strictfilter.md
index 945804f06..e39482870 100644
--- a/content/flux/v0.x/stdlib/experimental/geo/strictfilter.md
+++ b/content/flux/v0.x/stdlib/experimental/geo/strictfilter.md
@@ -28,7 +28,7 @@ _See [Strict and non-strict filtering](#strict-and-non-strict-filtering) below._
 import "experimental/geo"
 
 geo.strictFilter(
-  region: {lat: 40.69335938, lon: -73.30078125, radius: 20.0}
+    region: {lat: 40.69335938, lon: -73.30078125, radius: 20.0},
 )
 ```
 
@@ -77,52 +77,39 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 ```js
 import "experimental/geo"
 
+region = {minLat: 40.51757813, maxLat: 40.86914063, minLon: -73.65234375, maxLon: -72.94921875}
+
 from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "example-measurement")
-  |> geo.toRows()
-  |> geo.strictFilter(
-    region: {
-      minLat: 40.51757813,
-      maxLat: 40.86914063,
-      minLon: -73.65234375,
-      maxLon: -72.94921875
-    }
-  )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> geo.toRows()
+    |> geo.strictFilter(region: region)
 ```
 
 ##### Filter data in a circular region
 ```js
 import "experimental/geo"
 
+region = {lat: 40.69335938, lon: -73.30078125, radius: 20.0}
+
 from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "example-measurement")
-  |> geo.toRows()
-  |> geo.strictFilter(
-    region: {
-      lat: 40.69335938,
-      lon: -73.30078125,
-      radius: 20.0
-    }
-  )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> geo.toRows()
+    |> geo.strictFilter(region: region)
 ```
 
 ##### Filter data in a custom polygon region
 ```js
 import "experimental/geo"
 
+region = {
+    points: [{lat: 40.671659, lon: -73.936631}, {lat: 40.706543, lon: -73.749177}, {lat: 40.791333, lon: -73.880327}],
+}
+
 from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "example-measurement")
-  |> geo.toRows()
-  |> geo.strictFilter(
-    region: {
-      points: [
-        {lat: 40.671659, lon: -73.936631},
-        {lat: 40.706543, lon: -73.749177},
-        {lat: 40.791333, lon: -73.880327}
-      ]
-    }
-  )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> geo.toRows()
+    |> geo.strictFilter(region: region)
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/geo/torows.md b/content/flux/v0.x/stdlib/experimental/geo/torows.md
index 80071dbda..2cdd5653d 100644
--- a/content/flux/v0.x/stdlib/experimental/geo/torows.md
+++ b/content/flux/v0.x/stdlib/experimental/geo/torows.md
@@ -38,14 +38,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "experimental/geo"
 
 from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "example-measurement")
-  |> geo.toRows()
-```
-
-## Function definition
-```js
-toRows = (tables=<-) =>
-  tables
-    |> v1.fieldsAsCols()
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> geo.toRows()
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/group.md b/content/flux/v0.x/stdlib/experimental/group.md
index 0a1d51f75..655b772b6 100644
--- a/content/flux/v0.x/stdlib/experimental/group.md
+++ b/content/flux/v0.x/stdlib/experimental/group.md
@@ -58,6 +58,6 @@ Default is piped-forward data (`<-`).
 import "experimental"
 
 from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> experimental.group(columns: ["_value"], mode: "extend")
+    |> range(start: -1m)
+    |> experimental.group(columns: ["_value"], mode: "extend")
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/histogram.md b/content/flux/v0.x/stdlib/experimental/histogram.md
index fc6e7f7fd..e687de929 100644
--- a/content/flux/v0.x/stdlib/experimental/histogram.md
+++ b/content/flux/v0.x/stdlib/experimental/histogram.md
@@ -28,8 +28,8 @@ Bin counts are cumulative.
 import "experimental"
 
 experimental.histogram(
-  bins: [50.0, 75.0, 90.0],
-  normalize: false
+    bins: [50.0, 75.0, 90.0],
+    normalize: false,
 )
 ```
 
@@ -76,9 +76,7 @@ Default is piped-forward data (`<-`).
 import "experimental"
 
 data
-  |> experimental.histogram(
-    bins: linearBins(start:0.0, width:20.0, count:5)
-  )
+    |> experimental.histogram(bins: linearBins(start: 0.0, width: 20.0, count: 5))
 ```
 
 ##### Input data
diff --git a/content/flux/v0.x/stdlib/experimental/histogramquantile.md b/content/flux/v0.x/stdlib/experimental/histogramquantile.md
index 7b2262b13..a5f1b07ea 100644
--- a/content/flux/v0.x/stdlib/experimental/histogramquantile.md
+++ b/content/flux/v0.x/stdlib/experimental/histogramquantile.md
@@ -41,8 +41,8 @@ The function returns the value of the specified quantile from the histogram in t
 import "experimental"
 
 experimental.histogramQuantile(
-  quantile: 0.5,
-  minValue: 0.0
+    quantile: 0.5,
+    minValue: 0.0,
 )
 ```
 
@@ -76,10 +76,7 @@ Default is piped-forward data (`<-`).
 import "experimental"
 
 from(bucket: "example-bucket")
-  |> range(start: -1d)
-  |> filter(fn: (r) =>
-    r._meausrement == "example-measurement" and
-    r._field == "example-field"
-  )
-  |> experimental.histogramQuantile(quantile: 0.9)
+    |> range(start: -1d)
+    |> filter(fn: (r) => r._meausrement == "example-measurement" and r._field == "example-field")
+    |> experimental.histogramQuantile(quantile: 0.9)
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/http/get.md b/content/flux/v0.x/stdlib/experimental/http/get.md
index ea4c94cab..aec5d314d 100644
--- a/content/flux/v0.x/stdlib/experimental/http/get.md
+++ b/content/flux/v0.x/stdlib/experimental/http/get.md
@@ -21,9 +21,9 @@ returns the HTTP status code, response body, and response headers.
 import "experimental/http"
 
 http.get(
-  url: "http://localhost:8086/",
-  headers: {x:"a", y:"b", z:"c"},
-  timeout: 30s
+    url: "http://localhost:8086/",
+    headers: {x:"a", y:"b", z:"c"},
+    timeout: 30s
 )
 ```
 
@@ -66,10 +66,7 @@ import "csv"
 
 token = secrets.get(key: "READONLY_TOKEN")
 
-response = http.get(
-    url: "http://localhost:8086/health",
-    headers: {Authorization: "Token ${token}"}
-  )
+response = http.get(url: "http://localhost:8086/health", headers: {Authorization: "Token ${token}"})
 
 httpStatus = response.statusCode
 responseBody = string(v: response.body)
@@ -87,12 +84,15 @@ csvData = "#datatype,string,long,string
 ,result,table,column
 ,,0,*
 "
+
 csv.from(csv: csvData)
-  |> map(fn: (r) => ({
-    httpStatus: httpStatus,
-    responseBody: responseBody,
-    date: date,
-    contentLenth: contentLenth,
-    contentType: contentType,
-  }))
+    |> map(
+        fn: (r) => ({
+            httpStatus: httpStatus,
+            responseBody: responseBody,
+            date: date,
+            contentLenth: contentLenth,
+            contentType: contentType,
+        }),
+    )
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/http/requests/_index.md b/content/flux/v0.x/stdlib/experimental/http/requests/_index.md
new file mode 100644
index 000000000..cf8965d70
--- /dev/null
+++ b/content/flux/v0.x/stdlib/experimental/http/requests/_index.md
@@ -0,0 +1,91 @@
+---
+title: Flux experimental http requests package
+list_title: requests package
+description: >
+  The Flux experimental HTTP requests package provides functions for transferring data
+  using HTTP protocol.
+  Import the `experimental/http/requests` package.
+menu:
+  flux_0_x_ref:
+    name: requests
+    parent: http-exp
+weight: 301
+flux/v0.x/tags: [functions, http, package]
+introduced: 0.152.0
+---
+
+The Flux experimental HTTP requests package provides functions for transferring data
+using HTTP protocol.
+Import the `experimental/http/requests` package:
+
+```js
+import "experimental/http/requests"
+```
+
+## Options
+The `experimental/http/requests` package includes the following options:
+
+```js
+import "experimental/http/requests"
+
+option requests.defaultConfig = {
+    insecureSkipVerify: false,
+    timeout: 0ns,
+}
+```
+
+### defaultConfig
+Global default for all HTTP requests using the `experimental/http/requests` package.
+Changing this option affects all other packages using the `experimental/http/requests` package.
+To change configuration options for a single request, pass a new configuration
+record directly into the corresponding function.
+
+The `requests.defaultConfig` record contains the following properties:
+
+- **insecureSkipVerify**: Skip TLS verification _(boolean)_. Default is `false`.
+- **timeout**: HTTP request timeout _(duration)_. Default is `0ns` (no timeout).
+
+_See examples [below](#examples)._
+
+## Functions
+
+{{< children type="functions" show="pages" >}}
+
+## Examples
+
+### Change HTTP configuration options globally
+Modify the `requests.defaultConfig` option to change all consumers of the
+`experimental/http/requests` package.
+
+```js
+import "experimental/http/requests"
+
+option requests.defaultConfig = {
+    // Set a default timeout of 5s for all requests
+    timeout: 0ns,
+    insecureSkipVerify: true,
+}
+```
+
+### Change configuration for a single request
+To change the configuration for a single request, extending the default
+configuration with only the configuration values you need to customize.
+
+```js
+import "experimental/http/requests"
+
+// NOTE: Flux syntax does not yet let you specify anything but an identifier as
+// the record to extend. As a workaround, this example rebinds the default
+// configuration to a new name, "config".
+// See https://github.com/influxdata/flux/issues/3655
+defaultConfig = requests.defaultConfig
+config = {defaultConfig with
+     // Change the timeout to 60s for this request
+     // NOTE: We don't have to specify any other properites of the config because we're
+     // extending the default.
+     timeout: 60s,
+}
+response = requests.get(url:"http://example.com", config: config)
+
+requests.peek(response: response)
+```
\ No newline at end of file
diff --git a/content/flux/v0.x/stdlib/experimental/http/requests/do.md b/content/flux/v0.x/stdlib/experimental/http/requests/do.md
new file mode 100644
index 000000000..c4ff02280
--- /dev/null
+++ b/content/flux/v0.x/stdlib/experimental/http/requests/do.md
@@ -0,0 +1,163 @@
+---
+title: requests.do() function
+description: >
+  `requests.do()` makes an HTTP request using the specified request method.
+menu:
+  flux_0_x_ref:
+    name: requests.do
+    parent: requests
+weight: 401
+flux/v0.x/tags: [http, inputs, outputs]
+introduced: 0.152.0
+---
+
+`requests.do()` makes an HTTP request using the specified request method.
+
+```js
+import "experimental/http/requests"
+
+requests.do(
+    method: "GET",
+    url: "http://example.com",
+    params: ["example-param": ["example-param-value"]],
+    headers: ["Example-Header": "example-header-value"],
+    body: bytes(v: ""),
+    config: requests.defaultConfig,
+)
+```
+
+`requests.do()` returns a record with the following properties:
+
+- **statusCode**: HTTP status code of the request _(as an [integer](/flux/v0.x/data-types/basic/int/))_.
+- **body**: Response body _(as [bytes](/flux/v0.x/data-types/basic/bytes/))_.
+  A maximum size of 100MB is read from the response body.
+- **headers**: Response headers _(as a [dictionary](/flux/v0.x/data-types/composite/dict/))_.
+- **duration**: Request duration _(as a [duration](/flux/v0.x/data-types/basic/duration/))_.
+
+## Parameters
+
+### method {data-type="string"}
+HTTP request method.
+
+**Supported methods**:
+- DELETE
+- GET
+- HEAD
+- PATCH
+- POST
+- PUT
+
+### url {data-type="string"}
+URL to send the request to.
+
+{{% note %}}
+The URL should not include any query parameters.
+Use [`params`](#params) to specify query parameters.
+{{% /note %}}
+
+### params {data-type="dict"}
+Set of key-value pairs to add to the URL as query parameters.
+Query parameters are URL-encoded.
+All values for a key are appended to the query.
+
+### headers {data-type="dict"}
+Set of key values pairs to include as request headers.
+
+### body {data-type="bytes"}
+Data to send with the request.
+
+### config {data-type="record"}
+Set of request configuration options.
+_See [HTTP configuration option examples](/flux/v0.x/stdlib/experimental/http/requests/#examples)._
+
+## Examples
+
+- [Make a GET request](#make-a-get-request)
+- [Make a GET request with authorization](#make-a-get-request-with-authorization)
+- [Make a GET request with query parameters](#make-a-get-request-with-query-parameters)
+- [Make a GET request and decode the JSON response](#make-a-get-request-and-decode-the-json-response)
+- [Make a POST request with a JSON body](#make-a-post-request-with-a-json-body)
+- [Output HTTP response data in a table](#output-http-response-data-in-a-table)
+
+### Make a GET request
+```js
+import "experimental/http/requests"
+
+requests.do(url:"http://example.com", method: "GET")
+```
+
+### Make a GET request with authorization
+```js
+import "experimental/http/requests"
+import "influxdata/influxdb/secrets"
+
+token = secrets.get(key:"TOKEN")
+
+requests.do(
+    method: "GET",
+    url: "http://example.com",
+    headers: ["Authorization": "Token ${token}"],
+)
+```
+
+### Make a GET request with query parameters
+```js
+import "experimental/http/requests"
+
+requests.do(method: "GET", url: "http://example.com", params: ["start": ["100"]])
+```
+
+### Make a GET request and decode the JSON response
+To decode a JSON response, import the [`experimental/json` package](/flux/v0.x/stdlib/experimental/json/)
+and use [`json.parse()`](/flux/v0.x/stdlib/experimental/json/parse/) to parse
+the response into a [Flux type](/flux/v0.x/data-types/).
+
+```js
+import "experimental/http/requests"
+import "experimental/json"
+import "array"
+
+response = requests.do(method: "GET", url: "https://api.agify.io", params: ["name": ["nathaniel"]])
+
+// api.agify.io returns JSON with the form
+//
+// {
+//    name: string,
+//    age: number,
+//    count: number,
+// }
+//
+// Define a data variable that parses the JSON response body into a Flux record.
+data = json.parse(data: response.body)
+
+// Use array.from() to construct a table with one row containing our response data.
+array.from(rows: [{name: data.name, age: data.age, count: data.count}])
+```
+
+### Make a POST request with a JSON body
+Use [`json.encode()`](/flux/v0.x/stdlib/json/encode/) to encode a Flux record as
+a JSON object.
+
+```js
+import "experimental/http/requests"
+import "json"
+
+requests.do(
+    method: "POST",
+    url: "https://goolnk.com/api/v1/shorten",
+    body: json.encode(v: {url: "http://www.influxdata.com"}),
+    headers: ["Content-Type": "application/json"],
+)
+```
+
+### Output HTTP response data in a table
+To quickly inspect HTTP response data, use [`requests.peek()`](/flux/v0.x/stdlib/experimental/http/requests/peek/)
+to output HTTP response data in a table.
+
+```js
+import "experimental/http/requests"
+
+response = requests.do(method: "GET", url: "http://example.com")
+
+requests.peek(response: response)
+```
\ No newline at end of file
diff --git a/content/flux/v0.x/stdlib/experimental/http/requests/get.md b/content/flux/v0.x/stdlib/experimental/http/requests/get.md
new file mode 100644
index 000000000..db7fef574
--- /dev/null
+++ b/content/flux/v0.x/stdlib/experimental/http/requests/get.md
@@ -0,0 +1,120 @@
+---
+title: requests.get() function
+description: >
+  `requests.get()` makes an HTTP request using the GET request method.
+menu:
+  flux_0_x_ref:
+    name: requests.get
+    parent: requests
+weight: 401
+flux/v0.x/tags: [http, inputs, outputs]
+introduced: 0.152.0
+---
+
+`requests.get()` makes an HTTP request using the GET request method.
+
+```js
+import "experimental/http/requests"
+
+requests.get(
+    url: "http://example.com",
+    params: ["example-param": ["example-param-value"]],
+    headers: ["Example-Header": "example-header-value"],
+    body: bytes(v: ""),
+    config: requests.defaultConfig,
+)
+```
+
+`requests.get()` returns a record with the following properties:
+
+- **statusCode**: HTTP status code of the request.
+- **body**: Response body. A maximum size of 100MB is read from the response body.
+- **headers**: Response headers.
+
+## Parameters
+
+### url {data-type="string"}
+URL to send the request to.
+
+{{% note %}}
+The URL should not include any query parameters.
+Use [`params`](#params) to specify query parameters.
+{{% /note %}}
+
+### params {data-type="dict"}
+Set of key-value pairs to add to the URL as query parameters.
+Query parameters are URL-encoded.
+All values for a key are appended to the query.
+
+### headers {data-type="dict"}
+Set of key values pairs to include as request headers.
+
+### body {data-type="bytes"}
+Data to send with the request.
+
+### config {data-type="record"}
+Set of request configuration options.
+_See [HTTP configuration option examples](/flux/v0.x/stdlib/experimental/http/requests/#examples)._
+
+## Examples
+
+- [Make a GET request](#make-a-get-request)
+- [Make a GET request with authorization](#make-a-get-request-with-authorization)
+- [Make a GET request and decode the JSON response](#make-a-get-request-and-decode-the-json-response)
+- [Output HTTP response data in a table](#output-http-response-data-in-a-table)
+
+### Make a GET request
+```js
+import "experimental/http/requests"
+
+requests.get(url:"http://example.com")
+```
+
+### Make a GET request with authorization
+```js
+import "experimental/http/requests"
+import "influxdata/influxdb/secrets"
+
+token = secrets.get(key: "TOKEN")
+
+requests.get(url: "http://example.com", headers: ["Authorization": "Bearer ${token}"])
+```
+
+### Make a GET request and decode the JSON response
+To decode a JSON response, import the [`experimental/json` package](/flux/v0.x/stdlib/experimental/json/)
+and use [`json.parse()`](/flux/v0.x/stdlib/experimental/json/parse/) to parse
+the response into a [Flux type](/flux/v0.x/data-types/).
+
+```js
+import "experimental/http/requests"
+import "experimental/json"
+import "array"
+
+response = requests.get(url: "https://api.agify.io", params: ["name": ["john"]])
+
+// api.agify.io returns JSON with the form
+//
+// {
+//    name: string,
+//    age: number,
+//    count: number,
+// }
+//
+// Define a data variable that parses the JSON response body into a Flux record.
+data = json.parse(data: response.body)
+
+// Use array.from() to construct a table with one row containing our response data.
+array.from(rows: [{name: data.name, age: data.age, count: data.count}])
+```
+
+### Output HTTP response data in a table
+To quickly inspect HTTP response data, use [`requests.peek()`](/flux/v0.x/stdlib/experimental/http/requests/peek/)
+to output HTTP response data in a table.
+
+```js
+import "experimental/http/requests"
+
+response = requests.get(url: "http://example.com")
+
+requests.peek(response: response)
+```
diff --git a/content/flux/v0.x/stdlib/experimental/http/requests/peek.md b/content/flux/v0.x/stdlib/experimental/http/requests/peek.md
new file mode 100644
index 000000000..950df2b45
--- /dev/null
+++ b/content/flux/v0.x/stdlib/experimental/http/requests/peek.md
@@ -0,0 +1,74 @@
+---
+title: requests.peek() function
+description: >
+  `requests.peek()` converts an HTTP response into a table for easy inspection.
+menu:
+  flux_0_x_ref:
+    name: requests.peek
+    parent: requests
+weight: 401
+flux/v0.x/tags: [http]
+introduced: 0.154.0
+---
+
+`requests.peek()` converts an HTTP response into a table for easy inspection.
+
+```js
+import "experimental/http/requests"
+
+requests.peek(
+    response: requests.get(url: "http://example.com")
+)
+```
+
+The output table includes the following columns:
+
+- **body**: response body as a string
+- **statusCode**: returned status code as an integer
+- **headers**: string representation of response headers
+- **duration**: request duration in nanoseconds
+
+{{% note %}}
+To customize how the response data is structured in a table, use `array.from()`
+with a function like `json.parse()`. Parse the response body into a set of values
+and then use `array.from()` to construct a table from those values.
+{{% /note %}}
+
+
+## Parameters
+
+### response {data-type="record"}
+Response data from an HTTP request.
+
+## Examples
+
+### Inspect the response of an HTTP request
+```js
+import "experimental/http/requests"
+
+response = requests.get(url: "https://api.agify.io", params: ["name": ["natalie"]])
+
+requests.peek(response: response)
+```
+
+| statusCode | body | headers | duration |
+| :--------- | :--- | :------ | -------: |
+| 200 | {"name":"natalie","age":34,"count":20959} | _See [returned headers](#returned-headers) string below_ | 1212263875 |
+
+##### Returned headers
+```
+[
+    Access-Control-Allow-Headers: Content-Type, X-Genderize-Source,
+    Access-Control-Allow-Methods: GET,
+    Access-Control-Allow-Origin: *,
+    Connection: keep-alive,
+    Content-Length: 41,
+    Content-Type: application/json; charset=utf-8,
+    Date: Wed, 09 Feb 2022 20:00:00 GMT,
+    Etag: W/"29-klDahUESBLxHyQ7NiaetCn2CvCI",
+    Server: nginx/1.16.1,
+    X-Rate-Limit-Limit: 1000,
+    X-Rate-Limit-Remaining: 999,
+    X-Rate-Reset: 12203
+]
+```
diff --git a/content/flux/v0.x/stdlib/experimental/http/requests/post.md b/content/flux/v0.x/stdlib/experimental/http/requests/post.md
new file mode 100644
index 000000000..cbac6fbf8
--- /dev/null
+++ b/content/flux/v0.x/stdlib/experimental/http/requests/post.md
@@ -0,0 +1,114 @@
+---
+title: requests.post() function
+description: >
+  `requests.post()` makes an HTTP request using the POST request method.
+menu:
+  flux_0_x_ref:
+    name: requests.post
+    parent: requests
+weight: 401
+flux/v0.x/tags: [http, inputs, outputs]
+introduced: 0.152.0
+---
+
+`requests.post()` makes an HTTP request using the POST request method.
+
+```js
+import "experimental/http/requests"
+
+requests.post(
+    url: "http://example.com",
+    params: ["example-param": ["example-param-value"]],
+    headers: ["Example-Header": "example-header-value"],
+    body: bytes(v: ""),
+    config: requests.defaultConfig,
+)
+```
+
+`requests.post()` returns a record with the following properties:
+
+- **statusCode**: HTTP status code of the request.
+- **body**: Response body. A maximum size of 100MB is read from the response body.
+- **headers**: Response headers.
+
+## Parameters
+
+### url {data-type="string"}
+URL to send the request to.
+
+{{% note %}}
+The URL should not include any query parameters.
+Use [`params`](#params) to specify query parameters.
+{{% /note %}}
+
+### params {data-type="dict"}
+Set of key-value pairs to add to the URL as query parameters.
+Query parameters are URL-encoded.
+All values for a key are appended to the query.
+
+### headers {data-type="dict"}
+Set of key values pairs to include as request headers.
+
+### body {data-type="bytes"}
+Data to send with the request.
+
+### config {data-type="record"}
+Set of request configuration options.
+_See [HTTP configuration option examples](/flux/v0.x/stdlib/experimental/http/requests/#examples)._
+
+## Examples
+
+- [Make a POST request](#make-a-post-request)
+- [Make a POST request with authorization](#make-a-post-request-with-authorization)
+- [Make a POST request with a JSON body](#make-a-post-request-with-a-json-body)
+- [Output HTTP POST response data in a table](#output-http-post-response-data-in-a-table)
+
+### Make a POST request
+```js
+import "json"
+import "experimental/http/requests"
+
+requests.post(url:"http://example.com", body: json.encode(v: {data: {x:1, y: 2, z:3}))
+```
+
+### Make a POST request with authorization
+```js
+import "json"
+import "experimental/http/requests"
+import "influxdata/influxdb/secrets"
+
+token = secrets.get(key: "TOKEN")
+
+requests.post(
+    url: "http://example.com",
+    body: json.encode(v: {data: {x: 1, y: 2, z: 3}}),
+    headers: ["Authorization": "Bearer ${token}"],
+)
+```
+
+### Make a POST request with a JSON body
+Use [`json.encode()`](/flux/v0.x/stdlib/json/encode/) to encode a Flux record as
+a JSON object.
+
+```js
+import "experimental/http/requests"
+import "json"
+
+requests.post(
+    url: "https://goolnk.com/api/v1/shorten",
+    body: json.encode(v: {url: "http://www.influxdata.com"}),
+    headers: ["Content-Type": "application/json"],
+)
+```
+
+### Output HTTP POST response data in a table
+To quickly inspect HTTP response data, use [`requests.peek()`](/flux/v0.x/stdlib/experimental/http/requests/peek/)
+to output HTTP response data in a table.
+
+```js
+import "experimental/http/requests"
+
+response = requests.post(url: "http://example.com")
+
+requests.peek(response: response)
+```
diff --git a/content/flux/v0.x/stdlib/experimental/influxdb/api.md b/content/flux/v0.x/stdlib/experimental/influxdb/api.md
index ea01a17e2..28be6eebe 100644
--- a/content/flux/v0.x/stdlib/experimental/influxdb/api.md
+++ b/content/flux/v0.x/stdlib/experimental/influxdb/api.md
@@ -26,14 +26,14 @@ Authorization permissions and limits apply to each request.
 import "experimental/influxdb"
 
 influxdb.api(
-  method: "get",
-  path: "/example",
-  host: "http://localhost:8086",
-  token: "mySupeR53cre7t0k3n",
-  headers: ["header1": "header1Value", "header2": "header2Value"],
-  query: ["ex1": "example1", "ex2": "example2"],
-  timeout: 30s,
-  body: bytes(v: "Example body")
+    method: "get",
+    path: "/example",
+    host: "http://localhost:8086",
+    token: "mySupeR53cre7t0k3n",
+    headers: ["header1": "header1Value", "header2": "header2Value"],
+    query: ["ex1": "example1", "ex2": "example2"],
+    timeout: 30s,
+    body: bytes(v: "Example body"),
 )
 ```
 
@@ -41,9 +41,9 @@ influxdb.api(
 {{% expand "View response record schema" %}}
 ```js
 {
-  statusCode: int,
-  headers: dict,
-  body: bytes
+    statusCode: int,
+    headers: dict,
+    body: bytes,
 }
 ```
 {{% /expand %}}
@@ -90,15 +90,9 @@ import "influxdata/influxdb/secrets"
 
 token = secrets.get(key: "INFLUX_TOKEN")
 
-response = influxdb.api(
-  method: "get",
-  path: "/health",
-  host: "http://localhost:8086",
-  token: token,
-)
+response = influxdb.api(method: "get", path: "/health", host: "http://localhost:8086", token: token)
 
 string(v: response.body)
-
 // Returns something similar to:
 // {
 //   "name":"influxdb",
@@ -118,15 +112,17 @@ import "influxdata/influxdb/secrets"
 token = secrets.get(key: "INFLUX_TOKEN")
 
 influxdb.api(
-  method: "post",
-  path: "/api/v2/buckets",
-  host: "http://localhost:8086",
-  token: token,
-  body: bytes(v: "{
-    \"name\": \"example-bucket\",
-    \"description\": \"This is an example bucket.\",
-    \"orgID\": \"x000X0x0xx0X00x0\",
-    \"retentionRules\": []
-  }")
+    method: "post",
+    path: "/api/v2/buckets",
+    host: "http://localhost:8086",
+    token: token,
+    body: bytes(
+        v: "{
+          \"name\": \"example-bucket\",
+          \"description\": \"This is an example bucket.\",
+          \"orgID\": \"x000X0x0xx0X00x0\",
+          \"retentionRules\": []
+        }",
+    ),
 )
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/integral.md b/content/flux/v0.x/stdlib/experimental/integral.md
index 6c9426d6e..b2a81821e 100644
--- a/content/flux/v0.x/stdlib/experimental/integral.md
+++ b/content/flux/v0.x/stdlib/experimental/integral.md
@@ -26,8 +26,8 @@ _`integral()` is an [aggregate function](/flux/v0.x/function-types/#aggregates).
 
 ```js
 integral(
-  unit: 10s,
-  interpolate: ""
+    unit: 10s,
+    interpolate: "",
 )
 ```
 
@@ -55,21 +55,15 @@ Default is piped-forward data (`<-`).
 ##### Calculate the integral
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -5m)
-  |> filter(fn: (r) =>
-    r._measurement == "cpu" and
-    r._field == "usage_system"
-  )
-  |> integral(unit:10s)
+    |> range(start: -5m)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_system")
+    |> integral(unit: 10s)
 ```
 
 ##### Calculate the integral with linear interpolation
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -5m)
-  |> filter(fn: (r) =>
-    r._measurement == "cpu" and
-    r._field == "usage_system"
-  )
-  |> integral(unit:10s, interpolate: "linear")
+    |> range(start: -5m)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_system")
+    |> integral(unit: 10s, interpolate: "linear")
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/iox/_index.md b/content/flux/v0.x/stdlib/experimental/iox/_index.md
new file mode 100644
index 000000000..eec189f86
--- /dev/null
+++ b/content/flux/v0.x/stdlib/experimental/iox/_index.md
@@ -0,0 +1,25 @@
+---
+title: Flux Experimental IOx package
+list_title: iox package
+description: >
+  The Flux experimental `iox` package provides functions for querying data from IOx.
+  Import the `experimental/iox` package.
+menu:
+  flux_0_x_ref:
+    name: iox
+    parent: experimental
+weight: 301
+flux/v0.x/tags: [functions, iox, package]
+introduced: 0.152.0
+---
+
+The experimental `iox` package provides functions for querying data from [IOx](https://github.com/influxdata/influxdb_iox).
+Import the `experimental/iox` package:
+
+```js
+import 'experimental/iox';
+```
+
+## Functions
+
+{{< children type="functions" show="pages" >}}
diff --git a/content/flux/v0.x/stdlib/experimental/iox/from.md b/content/flux/v0.x/stdlib/experimental/iox/from.md
new file mode 100644
index 000000000..9df1bb1f6
--- /dev/null
+++ b/content/flux/v0.x/stdlib/experimental/iox/from.md
@@ -0,0 +1,42 @@
+---
+title: iox.from() function
+description: >
+  `iox.from()` queries data from the specified bucket and measurement in an IOx
+  storage node.
+menu:
+  flux_0_x_ref:
+    name: iox.from
+    parent: iox
+weight: 401
+flux/v0.x/tags: [iox, inputs]
+introduced: 0.152.0
+---
+
+{{% warn %}}
+`iox.from()` is in active development and has not been fully implemented.
+This function acts as a placeholder as the implementation is completed.
+{{% /warn %}}
+
+`iox.from()` queries data from the specified bucket and measurement in an
+[IOx](https://github.com/influxdata/influxdb_iox) storage node.
+
+```js
+import "experimental/iox"
+
+iox.from(
+    bucket: "example-bucket",
+    measurement: "example-measurement",
+)
+```
+
+Output data is "pivoted" on the time column and includes columns for each
+returned tag and field per time value.
+
+## Parameters
+
+### bucket {data-type="string"}
+IOx bucket to read data from.
+
+### measurement {data-type="string"}
+Measurement to read data from.
+
diff --git a/content/flux/v0.x/stdlib/experimental/join.md b/content/flux/v0.x/stdlib/experimental/join.md
index e00da9c75..2902ca9b5 100644
--- a/content/flux/v0.x/stdlib/experimental/join.md
+++ b/content/flux/v0.x/stdlib/experimental/join.md
@@ -32,9 +32,9 @@ import "experimental"
 // ...
 
 experimental.join(
-  left: left,
-  right: right,
-  fn: (left, right) => ({left with lv: left._value, rv: right._value })
+    left: left,
+    right: right,
+    fn: (left, right) => ({left with lv: left._value, rv: right._value }),
 )
 ```
 
@@ -83,14 +83,13 @@ The return value must be a record.
 import "experimental"
 
 experimental.join(
-  left: left,
-  right: right,
-  fn: (left, right) => ({
-    left with
-    lv: left._value,
-    rv: right._value,
-    diff: left._value - right._value
-  })
+    left: left,
+    right: right,
+    fn: (left, right) => ({ left with
+        lv: left._value,
+        rv: right._value,
+        diff: left._value - right._value,
+    })
 )
 ```
 
@@ -108,22 +107,14 @@ experimental.join(
 import "experimental"
 
 s1 = from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "foo")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "foo")
 
 s2 = from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "bar")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "bar")
 
-experimental.join(
-  left: s1,
-  right: s2,
-  fn: (left, right) => ({
-    left with
-    s1_value: left._value,
-    s2_value: right._value
-  })
-)
+experimental.join(left: s1, right: s2, fn: (left, right) => ({left with s1_value: left._value, s2_value: right._value}))
 ```
 
 ###### Join two streams of tables with different fields and measurements
@@ -131,22 +122,14 @@ experimental.join(
 import "experimental"
 
 s1 = from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "foo" and r._field == "bar")
-  |> group(columns: ["_time", "_measurement", "_field", "_value"], mode: "except")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "foo" and r._field == "bar")
+    |> group(columns: ["_time", "_measurement", "_field", "_value"], mode: "except")
 
 s2 = from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "baz" and r._field == "quz")
-  |> group(columns: ["_time", "_measurement", "_field", "_value"], mode: "except")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "baz" and r._field == "quz")
+    |> group(columns: ["_time", "_measurement", "_field", "_value"], mode: "except")
 
-experimental.join(
-  left: s1,
-  right: s2,
-  fn: (left, right) => ({
-    left with
-    bar_value: left._value,
-    quz_value: right._value
-  })
-)
+experimental.join(left: s1, right: s2, fn: (left, right) => ({left with bar_value: left._value, quz_value: right._value}))
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/json/parse.md b/content/flux/v0.x/stdlib/experimental/json/parse.md
index a167eb6af..a77f322cd 100644
--- a/content/flux/v0.x/stdlib/experimental/json/parse.md
+++ b/content/flux/v0.x/stdlib/experimental/json/parse.md
@@ -38,15 +38,17 @@ JSON data to parse.
 import "experimental/json"
 
 data
-  |> map(fn: (r) => {
-      jsonData = json.parse(data: bytes(v: r._value))
-
-      return {
-        _time: r._time,
-        _field: r._field,
-        a: jsonData.a,
-        b: jsonData.b,
-        c: jsonData.c,
-      }
-    })
+    |> map(
+        fn: (r) => {
+            jsonData = json.parse(data: bytes(v: r._value))
+    
+            return {
+                _time: r._time,
+                _field: r._field,
+                a: jsonData.a,
+                b: jsonData.b,
+                c: jsonData.c,
+            }
+        },
+    )
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/kaufmansama.md b/content/flux/v0.x/stdlib/experimental/kaufmansama.md
index d2632139f..1e580ca09 100644
--- a/content/flux/v0.x/stdlib/experimental/kaufmansama.md
+++ b/content/flux/v0.x/stdlib/experimental/kaufmansama.md
@@ -45,6 +45,6 @@ Default is piped-forward data (`<-`).
 import "experimental"
 
 from(bucket: "example-bucket"):
-  |> range(start: -7d)
-  |> experimental.kaufmansAMA(n: 10)
+    |> range(start: -7d)
+    |> experimental.kaufmansAMA(n: 10)
 ```
\ No newline at end of file
diff --git a/content/flux/v0.x/stdlib/experimental/last.md b/content/flux/v0.x/stdlib/experimental/last.md
index cf2c18d74..bfb820999 100644
--- a/content/flux/v0.x/stdlib/experimental/last.md
+++ b/content/flux/v0.x/stdlib/experimental/last.md
@@ -47,7 +47,7 @@ Default is piped-forward data (`<-`).
 import "experimental"
 
 data
-  |> experimental.last()
+    |> experimental.last()
 ```
 
 {{< flex >}}
diff --git a/content/flux/v0.x/stdlib/experimental/max.md b/content/flux/v0.x/stdlib/experimental/max.md
index 60fca8f48..d91b82273 100644
--- a/content/flux/v0.x/stdlib/experimental/max.md
+++ b/content/flux/v0.x/stdlib/experimental/max.md
@@ -44,7 +44,7 @@ Default is piped-forward data (`<-`).
 import "experimental"
 
 data
-  |> experimental.max()
+    |> experimental.max()
 ```
 
 {{< flex >}}
diff --git a/content/flux/v0.x/stdlib/experimental/mean.md b/content/flux/v0.x/stdlib/experimental/mean.md
index b5680b7a3..febc97c2f 100644
--- a/content/flux/v0.x/stdlib/experimental/mean.md
+++ b/content/flux/v0.x/stdlib/experimental/mean.md
@@ -39,10 +39,8 @@ Default is piped-forward data (`<-`).
 ```js
 import "experimental"
 
-from(bucket:"example-bucket")
-  |> filter(fn: (r) =>
-    r._measurement == "example-measurement" and
-    r._field == "example-field")
-  |> range(start:-1h)
-  |> experimental.mean()
+from(bucket: "example-bucket")
+    |> filter(fn: (r) => r._measurement == "example-measurement" and r._field == "example-field")
+    |> range(start: -1h)
+    |> experimental.mean()
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/min.md b/content/flux/v0.x/stdlib/experimental/min.md
index 1d968e12f..14cf72cc1 100644
--- a/content/flux/v0.x/stdlib/experimental/min.md
+++ b/content/flux/v0.x/stdlib/experimental/min.md
@@ -44,7 +44,7 @@ Default is piped-forward data (`<-`).
 import "experimental"
 
 data
-  |> experimental.min()
+    |> experimental.min()
 ```
 
 {{< flex >}}
diff --git a/content/flux/v0.x/stdlib/experimental/mode.md b/content/flux/v0.x/stdlib/experimental/mode.md
index 046d68018..b663d276e 100644
--- a/content/flux/v0.x/stdlib/experimental/mode.md
+++ b/content/flux/v0.x/stdlib/experimental/mode.md
@@ -59,11 +59,8 @@ Default is piped-forward data (`<-`).
 import "experimental"
 
 from(bucket: "example-bucket")
-  |> filter(fn: (r) =>
-    r._measurement == "example-measurement" and
-    r._field == "example-field"
-  )
-  |> range(start:-12h)
-  |> window(every:10m)
-  |> experimental.mode()
+    |> filter(fn: (r) => r._measurement == "example-measurement" and r._field == "example-field")
+    |> range(start: -12h)
+    |> window(every: 10m)
+    |> experimental.mode()
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/mqtt/publish.md b/content/flux/v0.x/stdlib/experimental/mqtt/publish.md
index 31aa1777d..cf3a55fea 100644
--- a/content/flux/v0.x/stdlib/experimental/mqtt/publish.md
+++ b/content/flux/v0.x/stdlib/experimental/mqtt/publish.md
@@ -16,15 +16,15 @@ The `mqtt.publish()` function outputs data to an MQTT broker using MQTT protocol
 import "experimental/mqtt"
 
 mqtt.publish(
-  broker: "tcp://localhost:8883",
-  topic: "example-topic",
-  message: "Example message",
-  qos: 0,
-  retain: false,
-  clientid: "flux-mqtt",
-  username: "username",
-  password: "password",
-  timeout: 1s
+    broker: "tcp://localhost:8883",
+    topic: "example-topic",
+    message: "Example message",
+    qos: 0,
+    retain: false,
+    clientid: "flux-mqtt",
+    username: "username",
+    password: "password",
+    timeout: 1s,
 )
 ```
 
@@ -72,11 +72,11 @@ Default is `1s`.
 import "experimental/mqtt"
 
 mqtt.publish(
-  broker: "tcp://localhost:8883",
-  topic: "alerts",
-  message: "wake up",
-  clientid: "alert-watcher",
-  retain: true
+    broker: "tcp://localhost:8883",
+    topic: "alerts",
+    message: "wake up",
+    clientid: "alert-watcher",
+    retain: true,
 )
 ```
 
@@ -86,15 +86,16 @@ import "experimental/mqtt"
 import "influxdata/influxdb/sample"
 
 sample.data(set: "airSensor")
-  |> range(start: -20m)
-  |> last()
-  |> map(fn: (r) => ({
-    r with
-      sent: mqtt.publish(
-        broker: "tcp://localhost:8883",
-        topic: "air-sensors/last/${r.sensorID}",
-        message: string(v: r._value),
-        clientid: "sensor-12a4"
-      )
-  }))
+    |> range(start: -20m)
+    |> last()
+    |> map(fn: (r) => ({
+        r with
+            sent: mqtt.publish(
+                broker: "tcp://localhost:8883",
+                topic: "air-sensors/last/${r.sensorID}",
+                message: string(v: r._value),
+                clientid: "sensor-12a4",
+            )
+        })
+    )
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/mqtt/to.md b/content/flux/v0.x/stdlib/experimental/mqtt/to.md
index 7db098fa1..a5b1ce540 100644
--- a/content/flux/v0.x/stdlib/experimental/mqtt/to.md
+++ b/content/flux/v0.x/stdlib/experimental/mqtt/to.md
@@ -20,17 +20,17 @@ The `mqtt.to()` function outputs data to an MQTT broker using MQTT protocol.
 import "experimental/mqtt"
 
 mqtt.to(
-  broker: "tcp://localhost:8883",
-  topic: "example-topic",
-  qos: 0,
-  clientid: "flux-mqtt",
-  username: "username",
-  password: "password",
-  name: "name-example",
-  timeout: 1s,
-  timeColumn: "_time",
-  tagColumns: ["tag1", "tag2"],
-  valueColumns: ["_value"]
+    broker: "tcp://localhost:8883",
+    topic: "example-topic",
+    qos: 0,
+    clientid: "flux-mqtt",
+    username: "username",
+    password: "password",
+    name: "name-example",
+    timeout: 1s,
+    timeColumn: "_time",
+    tagColumns: ["tag1", "tag2"],
+    valueColumns: ["_value"],
 )
 ```
 
@@ -90,13 +90,13 @@ Default is `["_value"]`.
 import "experimental/mqtt"
 
 from(bucket: "example-bucket")
-  |> range(start: -5m)
-  |> filter(fn: (r) => r._measurement == "airSensor")
-  |> mqtt.to(
-    broker: "tcp://localhost:8883",
-    topic: "air-sensors",
-    clientid: "sensor-12a4",
-    tagColumns: ["sensorID"],
-    valueColumns: ["_value"]
-  )
+    |> range(start: -5m)
+    |> filter(fn: (r) => r._measurement == "airSensor")
+    |> mqtt.to(
+        broker: "tcp://localhost:8883",
+        topic: "air-sensors",
+        clientid: "sensor-12a4",
+        tagColumns: ["sensorID"],
+        valueColumns: ["_value"],
+    )
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/objectkeys.md b/content/flux/v0.x/stdlib/experimental/objectkeys.md
index a77cf7cd3..878948bb1 100644
--- a/content/flux/v0.x/stdlib/experimental/objectkeys.md
+++ b/content/flux/v0.x/stdlib/experimental/objectkeys.md
@@ -19,7 +19,7 @@ The `experimental.objectKeys()` function returns an array of keys in a specified
 import "experimental"
 
 experimental.objectKeys(
-  o: {key1: "value1", key2: "value2"}
+    o: {key1: "value1", key2: "value2"}
 )
 
 // Returns [key1, key2]
@@ -36,13 +36,8 @@ The record to return keys from.
 ```js
 import "experimental"
 
-user = {
-  firstName: "John",
-  lastName: "Doe",
-  age: 42
-}
+user = {firstName: "John", lastName: "Doe", age: 42}
 
 experimental.objectKeys(o: user)
-
 // Returns [firstName, lastName, age]
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/oee/apq.md b/content/flux/v0.x/stdlib/experimental/oee/apq.md
index 97a725610..06a24acf7 100644
--- a/content/flux/v0.x/stdlib/experimental/oee/apq.md
+++ b/content/flux/v0.x/stdlib/experimental/oee/apq.md
@@ -23,9 +23,9 @@ _`oee.APQ()` is an [aggregate function](/flux/v0.x/function-types/#aggregates)._
 import "experimental/oee"
 
 oee.APQ(
-  runningState: "running",
-  plannedTime: 8h,
-  idealCycleTime: 2m
+    runningState: "running",
+    plannedTime: 8h,
+    idealCycleTime: 2m,
 )
 ```
 
@@ -98,12 +98,8 @@ import "experimental/oee"
 productionData = // ...
 
 productionData
-  |> oee.APQ(
-    runningState: "running",
-    plannedTime: 8h,
-    idealCycleTime: 21s
-  )
-  |> drop(columns: ["_start","_stop"])
+    |> oee.APQ(runningState: "running", plannedTime: 8h, idealCycleTime: 21s)
+    |> drop(columns: ["_start", "_stop"])
 ```
 
 #### Output data
diff --git a/content/flux/v0.x/stdlib/experimental/oee/computeapq.md b/content/flux/v0.x/stdlib/experimental/oee/computeapq.md
index ff4408a0e..05bc0d93b 100644
--- a/content/flux/v0.x/stdlib/experimental/oee/computeapq.md
+++ b/content/flux/v0.x/stdlib/experimental/oee/computeapq.md
@@ -23,11 +23,11 @@ _`oee.computeAPQ()` is an [aggregate function](/flux/v0.x/function-types/#aggreg
 import "experimental/oee"
 
 oee.computeAPQ(
-  productionEvents: exampleProductionScheme,
-  partEvents: examplePartsStream,
-  runningState: "running",
-  plannedTime: 8h,
-  idealCycleTime: 2m,
+    productionEvents: exampleProductionScheme,
+    partEvents: examplePartsStream,
+    runningState: "running",
+    plannedTime: 8h,
+    idealCycleTime: 2m,
 )
 ```
 
@@ -120,13 +120,13 @@ productionData = // ...
 partsData = // ...
 
 oee.computeAPQ(
-  productionEvents: productionData,
-  partEvents: partsData,
-  runningState: "running",
-  plannedTime: 8h,
-  idealCycleTime: 21s
+    productionEvents: productionData,
+    partEvents: partsData,
+    runningState: "running",
+    plannedTime: 8h,
+    idealCycleTime: 21s,
 )
-|> drop(columns: ["_start","_stop"])
+    |> drop(columns: ["_start", "_stop"])
 ```
 
 #### Output data
diff --git a/content/flux/v0.x/stdlib/experimental/prometheus/histogramquantile.md b/content/flux/v0.x/stdlib/experimental/prometheus/histogramquantile.md
index 7230032a0..0bdf37c3b 100644
--- a/content/flux/v0.x/stdlib/experimental/prometheus/histogramquantile.md
+++ b/content/flux/v0.x/stdlib/experimental/prometheus/histogramquantile.md
@@ -23,8 +23,8 @@ _`prometheus.histogramQuantile()` is an [aggregate function](/flux/v0.x/function
 import "experimental/prometheus"
 
 prometheus.histogramQuantile(
-  quantile: 0.99,
-  metricVersion: 2
+    quantile: 0.99,
+    metricVersion: 2,
 )
 ```
 
diff --git a/content/flux/v0.x/stdlib/experimental/prometheus/scrape.md b/content/flux/v0.x/stdlib/experimental/prometheus/scrape.md
index 5db0dddb4..07b347611 100644
--- a/content/flux/v0.x/stdlib/experimental/prometheus/scrape.md
+++ b/content/flux/v0.x/stdlib/experimental/prometheus/scrape.md
@@ -26,7 +26,7 @@ The function groups metrics (including histogram and summary values) into indivi
 import "experimental/prometheus"
 
 prometheus.scrape(
-  url: "http://localhost:8086/metrics"
+    url: "http://localhost:8086/metrics"
 )
 ```
 
@@ -42,8 +42,5 @@ The URL to scrape Prometheus-formatted metrics from.
 import "experimental/prometheus"
 
 prometheus.scrape(url: "https://example-url.com/metrics")
-  |> to(
-    org: "example-org",
-    bucket: "example-bucket"
-  )
+    |> to(org: "example-org", bucket: "example-bucket")
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/quantile.md b/content/flux/v0.x/stdlib/experimental/quantile.md
index d61654cab..780d85a5f 100644
--- a/content/flux/v0.x/stdlib/experimental/quantile.md
+++ b/content/flux/v0.x/stdlib/experimental/quantile.md
@@ -33,9 +33,9 @@ the [`method`](#method) used._
 import "experimental"
 
 experimental.quantile(
-  q: 0.99,
-  method: "estimate_tdigest",
-  compression: 1000.0
+    q: 0.99,
+    method: "estimate_tdigest",
+    compression: 1000.0,
 )
 ```
 
@@ -86,15 +86,9 @@ Default is piped-forward data (`<-`).
 import "experimental"
 
 from(bucket: "example-bucket")
-	|> range(start: -5m)
-	|> filter(fn: (r) =>
-    r._measurement == "example-measurement" and
-    r._field == "example-field")
-	|> experimental.quantile(
-    q: 0.99,
-    method: "estimate_tdigest",
-    compression: 1000.0
-  )
+    |> range(start: -5m)
+    |> filter(fn: (r) => r._measurement == "example-measurement" and r._field == "example-field")
+    |> experimental.quantile(q: 0.99, method: "estimate_tdigest", compression: 1000.0)
 ```
 
 ###### Quantile as a selector
@@ -102,12 +96,7 @@ from(bucket: "example-bucket")
 import "experimental"
 
 from(bucket: "example-bucket")
-	|> range(start: -5m)
-	|> filter(fn: (r) =>
-    r._measurement == "example-measurement" and
-    r._field == "example-field")
-	|> experimental.quantile(
-    q: 0.99,
-    method: "exact_selector"
-  )
+    |> range(start: -5m)
+    |> filter(fn: (r) => r._measurement == "example-measurement" and r._field == "example-field")
+    |> experimental.quantile(q: 0.99, method: "exact_selector")
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/query/_index.md b/content/flux/v0.x/stdlib/experimental/query/_index.md
index f16f2d0bb..1135df811 100644
--- a/content/flux/v0.x/stdlib/experimental/query/_index.md
+++ b/content/flux/v0.x/stdlib/experimental/query/_index.md
@@ -34,11 +34,11 @@ which uses all other functions in this package.
 import "experimental/query"
 
 query.inBucket(
-  bucket: "example-bucket",
-  start: -1h,
-  stop: now(),
-  measurement: "example-measurement",
-  fields: ["exampleField1", "exampleField2"],
-  predicate: (r) => r.tagA == "foo" and r.tagB != "bar"
+    bucket: "example-bucket",
+    start: -1h,
+    stop: now(),
+    measurement: "example-measurement",
+    fields: ["exampleField1", "exampleField2"],
+    predicate: (r) => r.tagA == "foo" and r.tagB != "bar",
 )
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/query/filterfields.md b/content/flux/v0.x/stdlib/experimental/query/filterfields.md
index c9f72ea1e..053773396 100644
--- a/content/flux/v0.x/stdlib/experimental/query/filterfields.md
+++ b/content/flux/v0.x/stdlib/experimental/query/filterfields.md
@@ -20,7 +20,7 @@ The `query.filterFields()` function filters input data by field.
 import "experimental/query"
 
 query.filterFields(
-  fields: ["exampleField1", "exampleField2"]
+    fields: ["exampleField1", "exampleField2"]
 )
 ```
 
@@ -40,24 +40,5 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "experimental/query"
 
 query.fromRange(bucket: "telegraf", start: -1h)
-  |> query.filterFields(
-    fields: ["used_percent", "available_percent"]
-  )
+    |> query.filterFields(fields: ["used_percent", "available_percent"])
 ```
-
-## Function definition
-```js
-package query
-
-filterFields = (tables=<-, fields=[]) =>
-  if length(arr: fields) == 0 then
-    tables
-  else
-    tables
-      |> filter(fn: (r) => contains(value: r._field, set: fields))
-```
-
-_**Used functions:**_  
-[contains()](/flux/v0.x/stdlib/universe/contains/)  
-[filter()](/flux/v0.x/stdlib/universe/filter/)  
-[length()](/flux/v0.x/stdlib/universe/length/)  
diff --git a/content/flux/v0.x/stdlib/experimental/query/filtermeasurement.md b/content/flux/v0.x/stdlib/experimental/query/filtermeasurement.md
index b6a19ebcf..7d5c57be2 100644
--- a/content/flux/v0.x/stdlib/experimental/query/filtermeasurement.md
+++ b/content/flux/v0.x/stdlib/experimental/query/filtermeasurement.md
@@ -20,7 +20,7 @@ The `query.filterMeasurement()` function filters input data by measurement.
 import "experimental/query"
 
 query.filterMeasurement(
-  measurement: "example-measurement"
+    measurement: "example-measurement"
 )
 ```
 
@@ -40,19 +40,5 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "experimental/query"
 
 query.fromRange(bucket: "example-bucket", start: -1h)
-  |> query.filterMeasurement(
-    measurement: "example-measurement"
-  )
+    |> query.filterMeasurement(measurement: "example-measurement")
 ```
-
-## Function definition
-```js
-package query
-
-filterMeasurement = (tables=<-, measurement) =>
-  tables
-    |> filter(fn: (r) => r._measurement == measurement)
-```
-
-_**Used functions:**_  
-[filter()](/flux/v0.x/stdlib/universe/filter/)
diff --git a/content/flux/v0.x/stdlib/experimental/query/fromrange.md b/content/flux/v0.x/stdlib/experimental/query/fromrange.md
index d74dc2c86..9710debf8 100644
--- a/content/flux/v0.x/stdlib/experimental/query/fromrange.md
+++ b/content/flux/v0.x/stdlib/experimental/query/fromrange.md
@@ -23,9 +23,9 @@ given time bounds.
 import "experimental/query"
 
 query.fromRange(
-  bucket: "example-bucket",
-  start: -1h,
-  stop: now()
+    bucket: "example-bucket",
+    start: -1h,
+    stop: now(),
 )
 ```
 
@@ -54,17 +54,5 @@ Defaults to `now()`.
 ```js
 import "experimental/query"
 
-query.fromRange(
-  bucket: "example-bucket",
-  start: 2020-01-01T00:00:00Z
-)
-```
-
-## Function definition
-```js
-package query
-
-fromRange = (bucket, start, stop=now()) =>
-  from(bucket: bucket)
-    |> range(start: start, stop: stop)
+query.fromRange(bucket: "example-bucket", start: 2020-01-01T00:00:00Z)
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/query/inbucket.md b/content/flux/v0.x/stdlib/experimental/query/inbucket.md
index 8159f6928..6c184de9d 100644
--- a/content/flux/v0.x/stdlib/experimental/query/inbucket.md
+++ b/content/flux/v0.x/stdlib/experimental/query/inbucket.md
@@ -23,12 +23,12 @@ time bounds, filters data by measurement, field, and optional predicate expressi
 import "experimental/query"
 
 query.inBucket(
-  bucket: "example-bucket",
-  start: -1h,
-  stop: now(),
-  measurement: "example-measurement",
-  fields: ["exampleField1", "exampleField2"],
-  predicate: (r) => true
+    bucket: "example-bucket",
+    start: -1h,
+    stop: now(),
+    measurement: "example-measurement",
+    fields: ["exampleField1", "exampleField2"],
+    predicate: (r) => true,
 )
 ```
 
@@ -74,34 +74,10 @@ Default is `(r) => true`.
 import "experimental/query"
 
 query.inBucket(
-  bucket: "telegraf",
-  start: -1h,
-  measurement: "mem",
-  fields: ["used_percent", "available_percent"],
-  predicate: (r) => r.host == "host1"
+    bucket: "telegraf",
+    start: -1h,
+    measurement: "mem",
+    fields: ["used_percent", "available_percent"],
+    predicate: (r) => r.host == "host1",
 )
 ```
-
-## Function definition
-```js
-package query
-
-inBucket = (
-  bucket,
-  start,
-  stop=now(),
-  measurement,  
-  fields=[],
-  predicate=(r) => true
-) =>
-  fromRange(bucket: bucket, start: start, stop: stop)
-    |> filterMeasurement(measurement)
-    |> filter(fn: predicate)
-    |> filterFields(fields)
-```
-
-_**Used functions:**_  
-[filter()](/flux/v0.x/stdlib/universe/filter/)  
-[query.filterFields()](/flux/v0.x/stdlib/experimental/query/filterfields/)  
-[query.filterMeasurement()](/flux/v0.x/stdlib/experimental/query/filtermeasurement/)  
-[query.fromRange()](/flux/v0.x/stdlib/experimental/query/fromrange/)  
diff --git a/content/flux/v0.x/stdlib/experimental/record/get.md b/content/flux/v0.x/stdlib/experimental/record/get.md
index 210fce6ea..e759188c0 100644
--- a/content/flux/v0.x/stdlib/experimental/record/get.md
+++ b/content/flux/v0.x/stdlib/experimental/record/get.md
@@ -25,9 +25,9 @@ For more information, see [influxdata/flux#4073](https://github.com/influxdata/f
 import "experimental/record"
 
 record.get(
-  r: {foo, "bar"},
-  key: "foo",
-  default: "quz"  
+    r: {foo, "bar"},
+    key: "foo",
+    default: "quz",
 )
 ```
 
@@ -54,11 +54,6 @@ import "experimental/record"
 key = "foo"
 exampleRecord = {foo: 1.0, bar: "hello"}
 
-record.get(
-  r: exampleRecord,
-  key: key,
-  default: ""
-)
-
+record.get(r: exampleRecord, key: key, default: "")
 // Returns 1.0
 ```
\ No newline at end of file
diff --git a/content/flux/v0.x/stdlib/experimental/set.md b/content/flux/v0.x/stdlib/experimental/set.md
index 76e1a48ba..300e77b54 100644
--- a/content/flux/v0.x/stdlib/experimental/set.md
+++ b/content/flux/v0.x/stdlib/experimental/set.md
@@ -27,7 +27,7 @@ _Once sufficiently vetted, `experimental.set()` will replace the existing
 import "experimental"
 
 experimental.set(
-  o: {column1: "value1", column2: "value2"}
+    o: {column1: "value1", column2: "value2"}
 )
 ```
 
@@ -58,13 +58,13 @@ Default is piped-forward data (`<-`).
 import "experimental"
 
 data
-  |> experimental.set(
-    o: {
-      _field: "temperature",
-      unit: "°F",
-      location: "San Francisco"
-    }
-  )
+    |> experimental.set(o:
+        {
+            _field: "temperature",
+            unit: "°F",
+            location: "San Francisco"
+        }
+    )
 ```
 
 ##### Example output table
diff --git a/content/flux/v0.x/stdlib/experimental/skew.md b/content/flux/v0.x/stdlib/experimental/skew.md
index df4f822f3..f0a6836ff 100644
--- a/content/flux/v0.x/stdlib/experimental/skew.md
+++ b/content/flux/v0.x/stdlib/experimental/skew.md
@@ -38,10 +38,7 @@ Default is piped-forward data (`<-`).
 import "experimental"
 
 from(bucket: "example-bucket")
-  |> range(start: -5m)
-  |> filter(fn: (r) =>
-    r._measurement == "example-measurement" and
-    r._field == "example-field"
-  )
-  |> experimental.skew()
+    |> range(start: -5m)
+    |> filter(fn: (r) => r._measurement == "example-measurement" and r._field == "example-field")
+    |> experimental.skew()
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/spread.md b/content/flux/v0.x/stdlib/experimental/spread.md
index 72799fa2f..57188b1f8 100644
--- a/content/flux/v0.x/stdlib/experimental/spread.md
+++ b/content/flux/v0.x/stdlib/experimental/spread.md
@@ -45,10 +45,7 @@ Default is piped-forward data (`<-`).
 import "experimental"
 
 from(bucket: "example-bucket")
-  |> range(start: -5m)
-  |> filter(fn: (r) =>
-    r._measurement == "example-measurement" and
-    r._field == "example-field"
-  )
-  |> experimental.spread()
+    |> range(start: -5m)
+    |> filter(fn: (r) => r._measurement == "example-measurement" and r._field == "example-field")
+    |> experimental.spread()
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/stddev.md b/content/flux/v0.x/stdlib/experimental/stddev.md
index 382be9873..a10180b90 100644
--- a/content/flux/v0.x/stdlib/experimental/stddev.md
+++ b/content/flux/v0.x/stdlib/experimental/stddev.md
@@ -54,10 +54,7 @@ Default is piped-forward data (`<-`).
 import "experimental"
 
 from(bucket: "example-bucket")
-  |> range(start: -5m)
-  |> filter(fn: (r) =>
-    r._measurement == "cpu" and
-    r._field == "usage_system"
-  )
-  |> experimental.stddev()
+    |> range(start: -5m)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_system")
+    |> experimental.stddev()
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/subduration.md b/content/flux/v0.x/stdlib/experimental/subduration.md
index 6d53bf5ed..74fda166b 100644
--- a/content/flux/v0.x/stdlib/experimental/subduration.md
+++ b/content/flux/v0.x/stdlib/experimental/subduration.md
@@ -15,16 +15,17 @@ flux/v0.x/tags: [date/time]
 related:
   - /flux/v0.x/stdlib/experimental/addduration/
 introduced: 0.39.0
+deprecated: 0.162.0
 ---
 
+{{% warn %}}
+This function was promoted to the [`date` package](/flux/v0.x/stdlib/date/subduration/)
+in **Flux v0.162.0**. This experimental version has been deprecated.
+{{% /warn %}}
+
 The `experimental.subDuration()` function subtracts a duration from a time value and
 returns the resulting time value.
 
-{{% warn %}}
-This function will be removed once duration vectors are implemented.
-See [influxdata/flux#413](https://github.com/influxdata/flux/issues/413).
-{{% /warn %}}
-
 ```js
 import "experimental"
 
@@ -37,10 +38,10 @@ experimental.subDuration(
 ## Parameters
 
 ### d {data-type="duration"}
-The duration to subtract.
+Duration to subtract.
 
 ### from {data-type="time, duration"}
-The time to subtract the [duration](#d) from.
+Time to subtract the [duration](#d) from.
 Use an absolute time or a relative duration.
 Durations are relative to [`now()`](/flux/v0.x/stdlib/universe/now/).
 
diff --git a/content/flux/v0.x/stdlib/experimental/sum.md b/content/flux/v0.x/stdlib/experimental/sum.md
index bcc7e630c..84364b397 100644
--- a/content/flux/v0.x/stdlib/experimental/sum.md
+++ b/content/flux/v0.x/stdlib/experimental/sum.md
@@ -40,10 +40,7 @@ Default is piped-forward data (`<-`).
 import "experimental"
 
 from(bucket: "example-bucket")
-  |> range(start: -5m)
-  |> filter(fn: (r) =>
-    r._measurement == "example-measurement" and
-    r._field == "example-field"
-  )
-  |> experimental.sum()
+    |> range(start: -5m)
+    |> filter(fn: (r) => r._measurement == "example-measurement" and r._field == "example-field")
+    |> experimental.sum()
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/table/fill.md b/content/flux/v0.x/stdlib/experimental/table/fill.md
index d8677b429..f887c9af9 100644
--- a/content/flux/v0.x/stdlib/experimental/table/fill.md
+++ b/content/flux/v0.x/stdlib/experimental/table/fill.md
@@ -35,7 +35,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "experimental/table"
 
 data
-  |> table.fill()
+    |> table.fill()
 ```
 
 {{< flex >}}
diff --git a/content/flux/v0.x/stdlib/experimental/to.md b/content/flux/v0.x/stdlib/experimental/to.md
index 0e2de00d6..0ef74565a 100644
--- a/content/flux/v0.x/stdlib/experimental/to.md
+++ b/content/flux/v0.x/stdlib/experimental/to.md
@@ -25,19 +25,19 @@ a [different structure](#expected-data-structure) than the
 import "experimental"
 
 experimental.to(
-  bucket: "my-bucket",
-  org: "my-org",
-  host: "http://localhost:8086",
-  token: "mY5uPeRs3Cre7tok3N"
+    bucket: "my-bucket",
+    org: "my-org",
+    host: "http://localhost:8086",
+    token: "mY5uPeRs3Cre7tok3N",
 )
 
 // OR
 
 experimental.to(
-  bucketID: "1234567890",
-  orgID: "0987654321",
-  host: "http://localhost:8086",
-  token: "mY5uPeRs3Cre7tok3N"
+    bucketID: "1234567890",
+    orgID: "0987654321",
+    host: "http://localhost:8086",
+    token: "mY5uPeRs3Cre7tok3N",
 )
 ```
 
@@ -118,13 +118,7 @@ Default is piped-forward data (`<-`).
 import "experimental"
 
 from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> pivot(
-      rowKey:["_time"],
-      columnKey: ["_field"],
-      valueColumn: "_value")
-  |> experimental.to(
-      bucket: "bucket-name",
-      org: "org-name"
-  )
+    |> range(start: -1h)
+    |> pivot(rowKey: ["_time"], columnKey: ["_field"], valueColumn: "_value")
+    |> experimental.to(bucket: "bucket-name", org: "org-name")
 ```
diff --git a/content/flux/v0.x/stdlib/experimental/unique.md b/content/flux/v0.x/stdlib/experimental/unique.md
index 00bda0f29..10710b44f 100644
--- a/content/flux/v0.x/stdlib/experimental/unique.md
+++ b/content/flux/v0.x/stdlib/experimental/unique.md
@@ -24,6 +24,7 @@ _`experimental.unique()` is a [selector function](/flux/v0.x/function-types/#sel
 
 ```js
 import "experimental"
+
 experimental.unique()
 ```
 
@@ -48,8 +49,9 @@ Default is piped-forward data (`<-`).
 ## Examples
 ```js
 import "experimental"
+
 data
- |> experimental.unique()
+    |> experimental.unique()
 ```
 
 {{< flex >}}
diff --git a/content/flux/v0.x/stdlib/experimental/usage/from.md b/content/flux/v0.x/stdlib/experimental/usage/from.md
index fb18cab33..063f1fa0d 100644
--- a/content/flux/v0.x/stdlib/experimental/usage/from.md
+++ b/content/flux/v0.x/stdlib/experimental/usage/from.md
@@ -11,6 +11,9 @@ aliases:
   - /influxdb/cloud/reference/flux/stdlib/experimental/usage/from/
 weight: 401
 flux/v0.x/tags: [inputs]
+related:
+  - /influxdb/cloud/account-management/data-usage/
+  - /influxdb/cloud/account-management/limits/
 ---
 
 `usage.from()` returns usage data from an **InfluxDB Cloud** organization.
@@ -21,12 +24,12 @@ anomalies or rate limiting.
 import "experimental/usage"
 
 usage.from(
-  start: -30d,
-  stop: now(),
-  host: "",
-  orgID: "",
-  token: "",
-  raw: false
+    start: -30d,
+    stop: now(),
+    host: "",
+    orgID: "",
+    token: "",
+    raw: false,
 )
 ```
 
@@ -123,7 +126,7 @@ usage.from(
     stop: now(),
     host: "https://cloud2.influxdata.com",
     orgID: "x000X0x0xx0X00x0",
-    token: token
+    token: token,
 )
 ```
 
@@ -158,8 +161,8 @@ usage.from(start: -30d, stop: now())
 import "experimental/usage"
 
 checkLimit = (tables=<-, limit) => tables
-    |> map(fn: (r) => ({ r with _value: r._value / 1000, limit: int(v: limit) * 60 * 5 }))
-    |> map(fn: (r) => ({ r with limitReached: r._value > r.limit}))
+    |> map(fn: (r) => ({r with _value: r._value / 1000, limit: int(v: limit) * 60 * 5}))
+    |> map(fn: (r) => ({r with limitReached: r._value > r.limit}))
 
 read = usage.from(start: -30d, stop: now())
     |> filter(fn: (r) => r._measurement == "http_request")
diff --git a/content/flux/v0.x/stdlib/experimental/usage/limits.md b/content/flux/v0.x/stdlib/experimental/usage/limits.md
index 37f46baff..266270e87 100644
--- a/content/flux/v0.x/stdlib/experimental/usage/limits.md
+++ b/content/flux/v0.x/stdlib/experimental/usage/limits.md
@@ -13,6 +13,8 @@ aliases:
 weight: 401
 related:
   - /flux/v0.x/stdlib/influxdata/influxdb/cardinality/
+  - /influxdb/cloud/account-management/data-usage/
+  - /influxdb/cloud/account-management/limits/
 ---
 
 The `usage.limits()` function returns a record containing usage limits for an
@@ -23,9 +25,9 @@ The `usage.limits()` function returns a record containing usage limits for an
 import "experimental/usage"
 
 usage.limits(
-  host: "",
-  orgID: "",
-  token: ""
+    host: "",
+    orgID: "",
+    token: "",
 )
 ```
 
@@ -33,34 +35,34 @@ usage.limits(
 {{% expand "View example usage limits record" %}}
 ```js
 {
-  orgID: "123",
-  rate: {
-    readKBs: 1000,
-    concurrentReadRequests: 0,
-    writeKBs: 17,
-    concurrentWriteRequests: 0,
-    cardinality: 10000
-  },
-  bucket: {
-    maxBuckets: 2,
-    maxRetentionDuration: 2592000000000000
-  },
-  task: {
-    maxTasks: 5
-  },
-  dashboard: {
-    maxDashboards: 5
-  },
-  check: {
-    maxChecks: 2
-  },
-  notificationRule: {
-    maxNotifications: 2,
-    blockedNotificationRules: "comma, delimited, list"
-  },
-  notificationEndpoint: {
-    blockedNotificationEndpoints: "comma, delimited, list"
-  }
+    orgID: "123",
+    rate: {
+        readKBs: 1000,
+        concurrentReadRequests: 0,
+        writeKBs: 17,
+        concurrentWriteRequests: 0,
+        cardinality: 10000
+    },
+    bucket: {
+        maxBuckets: 2,
+        maxRetentionDuration: 2592000000000000
+    },
+    task: {
+        maxTasks: 5
+    },
+    dashboard: {
+        maxDashboards: 5
+    },
+    check: {
+        maxChecks: 2
+    },
+    notificationRule: {
+        maxNotifications: 2,
+        blockedNotificationRules: "comma, delimited, list"
+    },
+    notificationEndpoint: {
+        blockedNotificationEndpoints: "comma, delimited, list"
+    }
 }
 ```
 {{% /expand %}}
@@ -137,12 +139,8 @@ import "experimental/usage"
 import "influxdata/influxdb"
 
 limits = usage.limits()
-bucketCardinality = (bucket) =>
-    (influxdb.cardinality(
-        bucket: bucket,
-        start: time(v: 0),
-    )
-        |> findColumn(fn: (key) => true, column: "_value"))[0]
+bucketCardinality = (bucket) => (influxdb.cardinality(bucket: bucket, start: time(v: 0))
+    |> findColumn(fn: (key) => true, column: "_value"))[0]
 
 buckets()
     |> filter(fn: (r) => not r.name =~ /^_/)
diff --git a/content/flux/v0.x/stdlib/experimental/window.md b/content/flux/v0.x/stdlib/experimental/window.md
index 5e27d9e2d..243fa2e59 100644
--- a/content/flux/v0.x/stdlib/experimental/window.md
+++ b/content/flux/v0.x/stdlib/experimental/window.md
@@ -17,7 +17,7 @@ flux/v0.x/tags: [transformations]
 introduced: 0.106.0
 ---
 
-The `window()` function groups records based on a time value.
+The `experimental.window()` function groups records based on a time value.
 New columns are added to uniquely identify each window.
 Those columns are added to the group key of the output tables.
 **Input tables must have `_start`, `_stop`, and `_time` columns.**
@@ -28,12 +28,14 @@ By default the start boundary of a window will align with the Unix epoch (zero t
 modified by the offset of the `location` option.
 
 ```js
-window(
-  every: 5m,
-  period: 5m,
-  offset: 12h,
-  location: "UTC",
-  createEmpty: false
+import "experimental"
+
+experimental.window(
+    every: 5m,
+    period: 5m,
+    offset: 12h,
+    location: "UTC",
+    createEmpty: false,
 )
 ```
 
@@ -80,16 +82,20 @@ Default is piped-forward data (`<-`).
 
 #### Window data into 10 minute intervals
 ```js
+import "experimental"
+
 from(bucket:"example-bucket")
   |> range(start: -12h)
-  |> window(every: 10m)
+  |> experimental.window(every: 10m)
   // ...
 ```
 
 #### Window by calendar month
 ```js
+import "experimental"
+
 from(bucket:"example-bucket")
   |> range(start: -1y)
-  |> window(every: 1mo)
+  |> experimental.window(every: 1mo)
   // ...
 ```
diff --git a/content/flux/v0.x/stdlib/generate/from.md b/content/flux/v0.x/stdlib/generate/from.md
index 7d6cc1ff6..bd99ccfba 100644
--- a/content/flux/v0.x/stdlib/generate/from.md
+++ b/content/flux/v0.x/stdlib/generate/from.md
@@ -16,10 +16,10 @@ weight: 202
 import "generate"
 
 generate.from(
-  count: 5,
-  fn: (n) => n,
-  start: 2021-01-01T00:00:00Z,
-  stop: 2021-01-02T00:00:00Z
+    count: 5,
+    fn: (n) => n,
+    start: 2021-01-01T00:00:00Z,
+    stop: 2021-01-02T00:00:00Z,
 )
 ```
 
@@ -51,10 +51,10 @@ End of the time range to generate values in.
 import "generate"
 
 generate.from(
-  count: 6,
-  fn: (n) => (n + 1) * (n + 2),
-  start: 2021-01-01T00:00:00Z,
-  stop: 2021-01-02T00:00:00Z,
+    count: 6,
+    fn: (n) => (n + 1) * (n + 2),
+    start: 2021-01-01T00:00:00Z,
+    stop: 2021-01-02T00:00:00Z,
 )
 ```
 
diff --git a/content/flux/v0.x/stdlib/http/basicauth.md b/content/flux/v0.x/stdlib/http/basicauth.md
index 7a03351f5..e74004e39 100644
--- a/content/flux/v0.x/stdlib/http/basicauth.md
+++ b/content/flux/v0.x/stdlib/http/basicauth.md
@@ -21,10 +21,7 @@ header using a specified username and password combination.
 ```js
 import "http"
 
-http.basicAuth(
-  u: "username",
-  p: "passw0rd"
-)
+http.basicAuth(u: "username", p: "passw0rd")
 
 // Returns "Basic dXNlcm5hbWU6cGFzc3cwcmQ="
 ```
@@ -48,8 +45,8 @@ username = "myawesomeuser"
 password = "mySupErSecRetPasSW0rD"
 
 http.post(
-  url: "http://myawesomesite.com/api/",
-  headers: {Authorization: http.basicAuth(u:username, p:password)},
-  data: bytes(v: "something I want to send.")
+    url: "http://myawesomesite.com/api/",
+    headers: {Authorization: http.basicAuth(u:username, p:password)},
+    data: bytes(v: "something I want to send."),
 )
 ```
diff --git a/content/flux/v0.x/stdlib/http/endpoint.md b/content/flux/v0.x/stdlib/http/endpoint.md
index 2c477bea3..961bf267e 100644
--- a/content/flux/v0.x/stdlib/http/endpoint.md
+++ b/content/flux/v0.x/stdlib/http/endpoint.md
@@ -21,7 +21,7 @@ The `http.endpoint()` function sends output data to an HTTP URL using the POST r
 import "http"
 
 http.endpoint(
-  url: "http://localhost:1234/"
+    url: "http://localhost:1234/"
 )
 ```
 
diff --git a/content/flux/v0.x/stdlib/http/pathescape.md b/content/flux/v0.x/stdlib/http/pathescape.md
index c7b2868e8..f5bbff57f 100644
--- a/content/flux/v0.x/stdlib/http/pathescape.md
+++ b/content/flux/v0.x/stdlib/http/pathescape.md
@@ -21,7 +21,7 @@ and replaces non-ASCII characters with hexadecimal representations (`%XX`).
 import "http"
 
 http.pathEscape(
-  inputString: "/this/is/an/example-path.html"
+    inputString: "/this/is/an/example-path.html"
 )
 
 // Returns %2Fthis%2Fis%2Fan%2Fexample-path.html
@@ -39,7 +39,5 @@ The string to escape.
 import "http"
 
 data
-  |> map(fn: (r) => ({ r with
-    path: http.pathEscape(inputString: r.path)
-  }))
+    |> map(fn: (r) => ({r with path: http.pathEscape(inputString: r.path)}))
 ```
diff --git a/content/flux/v0.x/stdlib/http/post.md b/content/flux/v0.x/stdlib/http/post.md
index 613db7b7a..49df50bb9 100644
--- a/content/flux/v0.x/stdlib/http/post.md
+++ b/content/flux/v0.x/stdlib/http/post.md
@@ -22,9 +22,9 @@ headers and data and returns the HTTP status code.
 import "http"
 
 http.post(
-  url: "http://localhost:8086/",
-  headers: {x:"a", y:"b", z:"c"},
-  data: bytes(v: "body")
+    url: "http://localhost:8086/",
+    headers: {x:"a", y:"b", z:"c"},
+    data: bytes(v: "body"),
 )
 ```
 
@@ -55,19 +55,18 @@ The data body to include with the POST request.
 import "json"
 import "http"
 
-lastReported =
-  from(bucket: "example-bucket")
+lastReported = from(bucket: "example-bucket")
     |> range(start: -1m)
     |> filter(fn: (r) => r._measurement == "statuses")
     |> last()
     |> findColumn(fn: (key) => true, column: "_level")
 
 http.post(
-  url: "http://myawsomeurl.com/api/notify",
-  headers: {
-    Authorization: "Bearer mySuPerSecRetTokEn",
-    "Content-type": "application/json"
-  },
-  data: json.encode(v: lastReported[0])
+    url: "http://myawsomeurl.com/api/notify",
+    headers: {
+        Authorization: "Bearer mySuPerSecRetTokEn",
+        "Content-type": "application/json"
+    },
+    data: json.encode(v: lastReported[0]),
 )
 ```
diff --git a/content/flux/v0.x/stdlib/influxdata/influxdb/cardinality.md b/content/flux/v0.x/stdlib/influxdata/influxdb/cardinality.md
index e5de731de..0745a70a3 100644
--- a/content/flux/v0.x/stdlib/influxdata/influxdb/cardinality.md
+++ b/content/flux/v0.x/stdlib/influxdata/influxdb/cardinality.md
@@ -1,6 +1,6 @@
 ---
 title: influxdb.cardinality() function
-description: The `influxdb.cardinality()` function returns the series cardinality of data stored in InfluxDB Cloud.
+description: The `influxdb.cardinality()` function returns the series cardinality of data stored in InfluxDB.
 menu:
   flux_0_x_ref:
     name: influxdb.cardinality
@@ -17,31 +17,31 @@ related:
 introduced: 0.92.0
 ---
 
-The `influxdb.cardinality()` function returns the [series cardinality](/{{< latest "influxdb" "v2" >}}/reference/glossary#series-cardinality) of a specified dataset.
+The `influxdb.cardinality()` function returns the [series cardinality](/{{< latest "influxdb" "v2" >}}/reference/glossary#series-cardinality) of a specified dataset in InfluxDB.
 
 ```js
 import "influxdata/influxdb"
 
 influxdb.cardinality(
-  bucket: "example-bucket",
-  org: "example-org",
-  host: "https://cloud2.influxdata.com",
-  token: "MySuP3rSecr3Tt0k3n",
-  start: -30d,
-  stop: now(),
-  predicate: (r) => true
+    bucket: "example-bucket",
+    org: "example-org",
+    host: "https://cloud2.influxdata.com",
+    token: "MySuP3rSecr3Tt0k3n",
+    start: -30d,
+    stop: now(),
+    predicate: (r) => true,
 )
 
 // OR
 
 influxdb.cardinality(
-  bucketID: "00xXx0x00xXX0000",
-  orgID: "00xXx0x00xXX0000",
-  host: "https://cloud2.influxdata.com",
-  token: "MySuP3rSecr3Tt0k3n",
-  start: -30d,
-  stop: now(),
-  predicate: (r) => true
+    bucketID: "00xXx0x00xXX0000",
+    orgID: "00xXx0x00xXX0000",
+    host: "https://cloud2.influxdata.com",
+    token: "MySuP3rSecr3Tt0k3n",
+    start: -30d,
+    stop: now(),
+    predicate: (r) => true,
 )
 ```
 
@@ -97,10 +97,7 @@ _Default is `(r) => true`_.
 ```js
 import "influxdata/influxdb"
 
-influxdb.cardinality(
-  bucket: "example-bucket",
-  start: -1y
-)
+influxdb.cardinality(bucket: "example-bucket", start: -1y)
 ```
 
 ##### Query series cardinality in a measurement
@@ -108,9 +105,9 @@ influxdb.cardinality(
 import "influxdata/influxdb"
 
 influxdb.cardinality(
-  bucket: "example-bucket",
-  start: -1y,
-  predicate: (r) => r._measurement == "example-measurement"
+    bucket: "example-bucket",
+    start: -1y,
+    predicate: (r) => r._measurement == "example-measurement",
 )
 ```
 
@@ -119,9 +116,9 @@ influxdb.cardinality(
 import "influxdata/influxdb"
 
 influxdb.cardinality(
-  bucket: "example-bucket",
-  start: -1y,
-  predicate: (r) => r.exampleTag == "foo"
+    bucket: "example-bucket",
+    start: -1y,
+    predicate: (r) => r.exampleTag == "foo",
 )
 ```
 
@@ -129,12 +126,8 @@ influxdb.cardinality(
 ```js
 import "influxdata/influxdb"
 
-bucketCardinality = (bucket) =>
-    (influxdb.cardinality(
-        bucket: bucket,
-        start: time(v: 0),
-    )
-        |> findColumn(fn: (key) => true, column: "_value"))[0]
+bucketCardinality = (bucket) => (influxdb.cardinality(bucket: bucket, start: time(v: 0))
+    |> findColumn(fn: (key) => true, column: "_value"))[0]
 
 buckets()
     |> filter(fn: (r) => not r.name =~ /^_/)
diff --git a/content/flux/v0.x/stdlib/influxdata/influxdb/from.md b/content/flux/v0.x/stdlib/influxdata/influxdb/from.md
index 8bb780a30..911b8aecb 100644
--- a/content/flux/v0.x/stdlib/influxdata/influxdb/from.md
+++ b/content/flux/v0.x/stdlib/influxdata/influxdb/from.md
@@ -25,19 +25,19 @@ Each record in the table represents a single point in the series.
 
 ```js
 from(
-  bucket: "example-bucket",
-  host: "https://example.com",
-  org: "example-org",
-  token: "MySuP3rSecr3Tt0k3n"
+    bucket: "example-bucket",
+    host: "https://example.com",
+    org: "example-org",
+    token: "MySuP3rSecr3Tt0k3n",
 )
 
 // OR
 
 from(
-  bucketID: "0261d8287f4d6000",
-  host: "https://example.com",
-  orgID: "867f3fcf1846f11f",
-  token: "MySuP3rSecr3Tt0k3n"
+    bucketID: "0261d8287f4d6000",
+    host: "https://example.com",
+    orgID: "867f3fcf1846f11f",
+    token: "MySuP3rSecr3Tt0k3n",
 )
 ```
 
@@ -90,11 +90,86 @@ If authentication is _disabled_, provide an empty string (`""`).
 If authentication is _enabled_, provide your InfluxDB username and password
 using the `<username>:<password>` syntax.
 
+## Push down optimizations
+
+Some transformations called after `from()` trigger performance optimizations called pushdowns.
+These optimizations are "pushed down" from Flux into the InfluxDB storage layer and where they utilize code in storage to apply the transformation.
+Pushdowns happen automatically, but it is helpful understand how these optimizations work so you can better optimize your Flux queries.
+
+Pushdowns require an unbroken and exclusive chain between transformations.
+A `from()` call stored in a variable that then goes to multiple pushdowns will
+cause none of the pushdowns to be applied. For example:
+
+```js
+// Pushdowns are NOT applied
+data = from(bucket: "example-bucket")
+    |> range(start: -1h)
+
+data |> filter(fn: (r) => r._measurement == "m0") |> yield(name: "m0")
+data |> filter(fn: (r) => r._measurement == "m1") |> yield(name: "m1")
+```
+
+To reuse code and still apply pushdowns, invoke `from()` in a function and pipe-forward the output of the function into subsequent pushdowns:
+
+```js
+// Pushdowns ARE applied
+data = () => from(bucket: "example-bucket")
+    |> range(start: -1h)
+
+data() |> filter(fn: (r) => r._measurement == "m0") |> yield(name: "m0")
+data() |> filter(fn: (r) => r._measurement == "m1") |> yield(name: "m1")
+```
+
+### Filter
+
+`filter()` transformations that compare `r._measurement`, `r._field`, `r._value`
+or any tag value are pushed down to the storage layer.
+Comparisons that use functions do not.
+If the function produces a static value, evaluate the function outside of `filter()`.
+For example:
+
+```js
+import "strings"
+
+// filter() is NOT pushed down
+data
+    |> filter(fn: (r) => r.example == strings.joinStr(arr: ["foo", "bar"], v: ""))
+
+// filter() is pushed down
+exVar = strings.joinStr(arr: ["foo", "bar"], v: ""))
+
+data
+    |> filter(fn: (r) => r.example == exVar)
+```
+
+Multiple consecutive `filter()` transformations that can be pushed down are
+merged together into a single filter that gets pushed down.
+
+### Aggregates
+
+The following aggregate transformations are pushed down:
+
+- `min()`
+- `max()`
+- `sum()`
+- `count()`
+- `mean()` (except when used with `group()`)
+
+Aggregates will also be pushed down if they are preceded by a `group()`.
+The only exception is `mean()` which cannot be pushed down to the storage layer with `group()`.
+
+### Aggregate Window
+
+Aggregates used with `aggregateWindow()` are pushed down.
+Aggregates pushed down with `aggregateWindow()` are not compatible with `group()`.
+
 ## Examples
 
 - [Query InfluxDB using the bucket name](#query-using-the-bucket-name)
 - [Query InfluxDB using the bucket ID](#query-using-the-bucket-id)
 - [Query a remote InfluxDB Cloud instance](#query-a-remote-influxdb-cloud-instance)
+- [Query push downs](#query-push-downs)
+- [Query from the same bucket to multiple push downs](#query-multiple-push-downs)
 
 #### Query using the bucket name
 ```js
@@ -113,9 +188,66 @@ import "influxdata/influxdb/secrets"
 token = secrets.get(key: "INFLUXDB_CLOUD_TOKEN")
 
 from(
-  bucket: "example-bucket",
-  host: "https://cloud2.influxdata.com",
-  org: "example-org",
-  token: token
+    bucket: "example-bucket",
+    host: "https://cloud2.influxdata.com",
+    org: "example-org",
+    token: token,
 )
 ```
+
+### Utilize pushdowns in multiple queries
+
+```js
+from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "m0")
+    |> filter(fn: (r) => r._field == "f0")
+    |> yield(name: "filter-only")
+
+from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "m0")
+    |> filter(fn: (r) => r._field == "f0")
+    |> max()
+    |> yield(name: "max")
+
+from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "m0")
+    |> filter(fn: (r) => r._field == "f0")
+    |> group(columns: ["t0"])
+    |> max()
+    |> yield(name: "grouped-max")
+
+from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "m0")
+    |> filter(fn: (r) => r._field == "f0")
+    |> aggregateWindow(every: 5m, fn: max)
+    |> yield(name: "windowed-max")
+```
+
+### Query from the same bucket to multiple pushdowns
+
+```js
+// Use a function. If you use a variable, this will stop
+// Flux from pushing down the operation.
+data = () => from(bucket: "example-bucket")
+    |> range(start: -1h)
+
+data() |> filter(fn: (r) => r._measurement == "m0")
+data() |> filter(fn: (r) => r._measurement == "m1")
+```
+
+### Query from the same bucket to multiple transformations
+
+```js
+// The push down chain is not broken until after the push down
+// is complete. In this case, it is more efficient to use a variable.
+data = from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "m0")
+
+data |> derivative() |> yield(name: "derivative")
+data |> movingAverage(n: 5) |> yield(name: "movingAverage")
+```
diff --git a/content/flux/v0.x/stdlib/influxdata/influxdb/monitor/check.md b/content/flux/v0.x/stdlib/influxdata/influxdb/monitor/check.md
index 7b30efea7..3513ed00c 100644
--- a/content/flux/v0.x/stdlib/influxdata/influxdb/monitor/check.md
+++ b/content/flux/v0.x/stdlib/influxdata/influxdb/monitor/check.md
@@ -23,12 +23,12 @@ The `monitor.check()` function checks input data and assigns a level
 import "influxdata/influxdb/monitor"
 
 monitor.check(
-  crit: (r) => r._value > 90.0,
-  warn: (r) => r._value > 80.0,
-  info: (r) => r._value > 60.0,
-  ok:   (r) => r._value <= 20.0,
-  messageFn: (r) => "The current level is ${r._level}",
-  data: {}
+    crit: (r) => r._value > 90.0,
+    warn: (r) => r._value > 80.0,
+    info: (r) => r._value > 60.0,
+    ok: (r) => r._value <= 20.0,
+    messageFn: (r) => "The current level is ${r._level}",
+    data: {},
 )
 ```
 
@@ -71,27 +71,27 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "influxdata/influxdb/monitor"
 
 from(bucket: "telegraf")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-      r._measurement == "disk" and
-      r._field == "used_percent"
-  )
-  |> group(columns: ["_measurement"])
-  |> monitor.check(
-    crit: (r) => r._value > 90.0,
-    warn: (r) => r._value > 80.0,
-    info: (r) => r._value > 70.0,
-    ok:   (r) => r._value <= 60.0,
-    messageFn: (r) =>
-      if r._level == "crit" then "Critical alert!! Disk usage is at ${r._value}%!"
-      else if r._level == "warn" then "Warning! Disk usage is at ${r._value}%."
-      else if r._level == "info" then "Disk usage is at ${r._value}%."
-      else "Things are looking good.",
-    data: {
-      _check_name: "Disk Utilization (Used Percentage)",
-      _check_id: "disk_used_percent",
-      _type: "threshold",
-      tags: {}
-    }
-  )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "disk" and r._field == "used_percent")
+    |> group(columns: ["_measurement"])
+    |> monitor.check(
+        crit: (r) => r._value > 90.0,
+        warn: (r) => r._value > 80.0,
+        info: (r) => r._value > 70.0,
+        ok: (r) => r._value <= 60.0,
+        messageFn: (r) => if r._level == "crit" then
+            "Critical alert!! Disk usage is at ${r._value}%!"
+        else if r._level == "warn" then
+            "Warning! Disk usage is at ${r._value}%."
+        else if r._level == "info" then
+            "Disk usage is at ${r._value}%."
+        else
+            "Things are looking good.",
+        data: {
+            _check_name: "Disk Utilization (Used Percentage)",
+            _check_id: "disk_used_percent",
+            _type: "threshold",
+            tags: {}
+        },
+    )
 ```
diff --git a/content/flux/v0.x/stdlib/influxdata/influxdb/monitor/deadman.md b/content/flux/v0.x/stdlib/influxdata/influxdb/monitor/deadman.md
index 9db8c0c2d..5442fbf36 100644
--- a/content/flux/v0.x/stdlib/influxdata/influxdb/monitor/deadman.md
+++ b/content/flux/v0.x/stdlib/influxdata/influxdb/monitor/deadman.md
@@ -45,9 +45,9 @@ import "influxdata/influxdb/monitor"
 import "experimental"
 
 from(bucket: "example-bucket")
-  |> range(start: -10m)
-  |> group(columns: ["host"])
-  |> monitor.deadman(t: experimental.subDuration(d: 30s, from: now() ))
+    |> range(start: -10m)
+    |> group(columns: ["host"])
+    |> monitor.deadman(t: experimental.subDuration(d: 5m, from: now()))
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/influxdata/influxdb/monitor/from.md b/content/flux/v0.x/stdlib/influxdata/influxdb/monitor/from.md
index c230cbc36..59c2d7dd9 100644
--- a/content/flux/v0.x/stdlib/influxdata/influxdb/monitor/from.md
+++ b/content/flux/v0.x/stdlib/influxdata/influxdb/monitor/from.md
@@ -23,13 +23,12 @@ measurement in the `_monitoring` bucket.
 import "influxdata/influxdb/monitor"
 
 monitor.from(
-  start: -1h,
-  stop: now(),
-  fn: (r) => true
+    start: -1h,
+    stop: now(),
+    fn: (r) => true,
 )
 ```
 
-
 ## Parameters
 
 ### start {data-type="duration, time, int"}
@@ -60,8 +59,5 @@ Records that evaluate to _null_ or `false` are not included in output tables.
 ```js
 import "influxdata/influxdb/monitor"
 
-monitor.from(
-  start: -1h,
-  fn: (r) => r._level == "crit"
-)
+monitor.from(start: -1h, fn: (r) => r._level == "crit")
 ```
diff --git a/content/flux/v0.x/stdlib/influxdata/influxdb/monitor/logs.md b/content/flux/v0.x/stdlib/influxdata/influxdb/monitor/logs.md
index e2b0b35c5..d99d61b97 100644
--- a/content/flux/v0.x/stdlib/influxdata/influxdb/monitor/logs.md
+++ b/content/flux/v0.x/stdlib/influxdata/influxdb/monitor/logs.md
@@ -23,9 +23,9 @@ measurement in the `_monitoring` bucket.
 import "influxdata/influxdb/monitor"
 
 monitor.logs(
-  start: -1h,
-  stop: now(),
-  fn: (r) => true
+    start: -1h,
+    stop: now(),
+    fn: (r) => true,
 )
 ```
 
diff --git a/content/flux/v0.x/stdlib/influxdata/influxdb/monitor/notify.md b/content/flux/v0.x/stdlib/influxdata/influxdb/monitor/notify.md
index 8f75fd129..648562676 100644
--- a/content/flux/v0.x/stdlib/influxdata/influxdb/monitor/notify.md
+++ b/content/flux/v0.x/stdlib/influxdata/influxdb/monitor/notify.md
@@ -22,8 +22,8 @@ in the `notifications` measurement in the [`_monitoring` bucket](/influxdb/cloud
 import "influxdata/influxdb/monitor"
 
 monitor.notify(
-  endpoint: endpoint,
-  data: {}
+    endpoint: endpoint,
+    data: {},
 )
 ```
 
@@ -66,25 +66,18 @@ import "slack"
 
 token = secrets.get(key: "SLACK_TOKEN")
 
-endpoint = slack.endpoint(token: token)(mapFn: (r) => ({
-    channel: "Alerts",
-    text: r._message,
-    color: "danger"
-  }))
+endpoint = slack.endpoint(token: token)(mapFn: (r) => ({channel: "Alerts", text: r._message, color: "danger"}))
 
 notification_data = {
-	_notification_rule_id: "0000000000000001",
-	_notification_rule_name: "example-rule-name",
-	_notification_endpoint_id: "0000000000000002",
-	_notification_endpoint_name: "example-endpoint-name",
+    _notification_rule_id: "0000000000000001",
+    _notification_rule_name: "example-rule-name",
+    _notification_endpoint_id: "0000000000000002",
+    _notification_endpoint_name: "example-endpoint-name"
 }
 
 from(bucket: "system")
-	|> range(start: -5m)
-	|> monitor.notify(
-    endpoint: endpoint,
-    data: notification_data
-  )
+    |> range(start: -5m)
+    |> monitor.notify(endpoint: endpoint, data: notification_data)
 ```
 
 ### Send a notification to PagerDuty
@@ -95,30 +88,29 @@ import "pagerduty"
 
 routingKey = secrets.get(key: "PAGERDUTY_ROUTING_KEY")
 
-endpoint = pagerduty.endpoint()(mapFn: (r) => ({
-    routingKey: routingKey,
-    client: "ExampleClient",
-    clientURL: "http://examplepagerdutyclient.com",
-    dedupkey: "ExampleDedupKey",
-    class: "cpu usage",
-    group: "app-stack",
-    severity: "ok",
-    eventAction: "trigger",
-    source: "monitoringtool:vendor:region",
-    timestamp: r._source_timestamp
-  }))
+endpoint = pagerduty.endpoint()(
+    mapFn: (r) => ({
+        routingKey: routingKey,
+        client: "ExampleClient",
+        clientURL: "http://examplepagerdutyclient.com",
+        dedupkey: "ExampleDedupKey",
+        class: "cpu usage",
+        group: "app-stack",
+        severity: "ok",
+        eventAction: "trigger",
+        source: "monitoringtool:vendor:region",
+        timestamp: r._source_timestamp,
+    }),
+)
 
 notification_data = {
-	_notification_rule_id: "0000000000000001",
-	_notification_rule_name: "example-rule-name",
-	_notification_endpoint_id: "0000000000000002",
-	_notification_endpoint_name: "example-endpoint-name",
+    _notification_rule_id: "0000000000000001",
+    _notification_rule_name: "example-rule-name",
+    _notification_endpoint_id: "0000000000000002",
+    _notification_endpoint_name: "example-endpoint-name"
 }
 
 from(bucket: "system")
-	|> range(start: -5m)
-	|> monitor.notify(
-    endpoint: endpoint,
-    data: notification_data
-  )
+    |> range(start: -5m)
+    |> monitor.notify(endpoint: endpoint, data: notification_data)
 ```
diff --git a/content/flux/v0.x/stdlib/influxdata/influxdb/monitor/statechanges.md b/content/flux/v0.x/stdlib/influxdata/influxdb/monitor/statechanges.md
index aecc04168..11eb257a0 100644
--- a/content/flux/v0.x/stdlib/influxdata/influxdb/monitor/statechanges.md
+++ b/content/flux/v0.x/stdlib/influxdata/influxdb/monitor/statechanges.md
@@ -23,8 +23,8 @@ a `_level` column and outputs records that change from `fromLevel` to `toLevel`.
 import "influxdata/influxdb/monitor"
 
 monitor.stateChanges(
-  fromLevel: "any",
-  toLevel: "any"
+    fromLevel: "any",
+    toLevel: "any",
 )
 ```
 
@@ -50,7 +50,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "influxdata/influxdb/monitor"
 
 monitor.from(start: -1h)
-  |> monitor.stateChanges(toLevel: "crit")
+    |> monitor.stateChanges(toLevel: "crit")
 ```
 
 {{< flex >}}
@@ -72,12 +72,3 @@ monitor.from(start: -1h)
 | 2021-01-01T00:30:00Z |  crit  |
 {{% /flex-content %}}
 {{< /flex >}}
-
-## Function definition
-```js
-stateChanges = (fromLevel="any", toLevel="any", tables=<-) => {
-  return
-    if fromLevel == "any" and toLevel == "any" then tables |> stateChangesOnly()
-    else tables |> _stateChanges(fromLevel: fromLevel, toLevel: toLevel)
-}
-```
diff --git a/content/flux/v0.x/stdlib/influxdata/influxdb/monitor/statechangesonly.md b/content/flux/v0.x/stdlib/influxdata/influxdb/monitor/statechangesonly.md
index 3965f626e..45f1cd20b 100644
--- a/content/flux/v0.x/stdlib/influxdata/influxdb/monitor/statechangesonly.md
+++ b/content/flux/v0.x/stdlib/influxdata/influxdb/monitor/statechangesonly.md
@@ -38,7 +38,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "influxdata/influxdb/monitor"
 
 monitor.from(start: -1h)
-  |> monitor.stateChangesOnly()
+    |> monitor.stateChangesOnly()
 ```
 
 {{< flex >}}
diff --git a/content/flux/v0.x/stdlib/influxdata/influxdb/sample/aligntonow.md b/content/flux/v0.x/stdlib/influxdata/influxdb/sample/aligntonow.md
index 8ed7727bc..d56f21b34 100644
--- a/content/flux/v0.x/stdlib/influxdata/influxdb/sample/aligntonow.md
+++ b/content/flux/v0.x/stdlib/influxdata/influxdb/sample/aligntonow.md
@@ -30,15 +30,11 @@ import "influxdata/influxdb/sample"
 option now = () => 2021-01-01T00:00:00Z
 
 data = sample.data(set: "birdMigration")
-  |> filter(fn: (r) =>
-    r._field == "lon" and
-    r.s2_cell_id == "471ed2c" and
-    r.id == "91916A"
-  )
-  |> tail(n: 3)
+    |> filter(fn: (r) => r._field == "lon" and r.s2_cell_id == "471ed2c" and r.id == "91916A")
+    |> tail(n: 3)
 
 data
-  |> sample.alignToNow()
+    |> sample.alignToNow()
 ```
 
 {{% expand "View input and output" %}}
diff --git a/content/flux/v0.x/stdlib/influxdata/influxdb/sample/data.md b/content/flux/v0.x/stdlib/influxdata/influxdb/sample/data.md
index edd3d4263..1869be938 100644
--- a/content/flux/v0.x/stdlib/influxdata/influxdb/sample/data.md
+++ b/content/flux/v0.x/stdlib/influxdata/influxdb/sample/data.md
@@ -21,9 +21,7 @@ The `sample.data()` function downloads and outputs an InfluxDB sample dataset.
 ```js
 import "influxdata/influxdb/sample"
 
-sample.data(
-  set: "airSensor"
-)
+sample.data(set: "airSensor")
 ```
 
 {{% note %}}
diff --git a/content/flux/v0.x/stdlib/influxdata/influxdb/schema/_index.md b/content/flux/v0.x/stdlib/influxdata/influxdb/schema/_index.md
index d803220ed..e01f71b3b 100644
--- a/content/flux/v0.x/stdlib/influxdata/influxdb/schema/_index.md
+++ b/content/flux/v0.x/stdlib/influxdata/influxdb/schema/_index.md
@@ -17,11 +17,11 @@ flux/v0.x/tags: [functions, schema, package]
 cascade:
   introduced: 0.88.0
   append:
-    block: cloud
+    block: warn
     content: |
-      #### Supported in the InfluxDB Cloud UI
-      The `schema` package can retrieve schema information from the InfluxDB
-      Cloud user interface (UI), but **not** from the [Flux REPL](/influxdb/cloud/tools/repl/).
+      #### Not supported in the Flux REPL
+      `schema` functions can retrieve schema information when executed within
+      the context of InfluxDB, but not from the [Flux REPL](/influxdb/cloud/tools/repl/).
 ---
 
 The Flux InfluxDB `schema` package provides functions for exploring your InfluxDB data schema.
diff --git a/content/flux/v0.x/stdlib/influxdata/influxdb/schema/fieldkeys.md b/content/flux/v0.x/stdlib/influxdata/influxdb/schema/fieldkeys.md
index cf227af53..e6221ecdb 100644
--- a/content/flux/v0.x/stdlib/influxdata/influxdb/schema/fieldkeys.md
+++ b/content/flux/v0.x/stdlib/influxdata/influxdb/schema/fieldkeys.md
@@ -24,43 +24,64 @@ The return value is always a single table with a single column, `_value`.
 import "influxdata/influxdb/schema"
 
 schema.fieldKeys(
-  bucket: "example-bucket",
-  predicate: (r) => true,
-  start: -30d
+    bucket: "example-bucket",
+    predicate: (r) => true,
+    start: -30d,
 )
 ```
 
+{{% note %}}
+#### Deleted fields
+Fields [deleted from InfluxDB Cloud using the `/api/v2/delete` endpoint or the `influx delete` command](/influxdb/cloud/write-data/delete-data/)
+**do not** appear in results.
+
+#### Expired fields
+- **InfluxDB Cloud**: field keys associated with points outside of the bucket's
+  retention policy **may** appear in results up to an hour after expiring.
+- **InfluxDB OSS**: field keys associated with points outside of the bucket's
+  retention policy **may** appear in results.
+  For more information, see [Data retention in InfluxDB OSS](/{{< latest "influxdb" >}}/reference/internals/data-retention/).
+{{% /note %}}
+
 ## Parameters
 
 ### bucket {data-type="string"}
-The bucket to list field keys from.
+Bucket to list field keys from.
 
 ### predicate {data-type="function"}
-The predicate function that filters field keys.
+Predicate function that filters field keys.
 _Default is `(r) => true`._
 
 ### start {data-type="duration, time"}
-The oldest time to include in results.
+Earliest time to include in results.
 _Default is `-30d`._
 
 Relative start times are defined using negative durations.
 Negative durations are relative to now.
 Absolute start times are defined using [time values](/flux/v0.x/spec/types/#time-types).
 
+### stop {data-type="duration, time"}
+Latest time to include in results.
+_Default is `now()`._
+
+The `stop` time is exclusive, meaning values with a time equal to stop time are
+excluded from results.
+Relative start times are defined using negative durations.
+Negative durations are relative to `now()`.
+Absolute start times are defined using [time values](/flux/v0.x/spec/types/#time-types).
+
 ## Examples
+
+### Return all field keys in a bucket
 ```js
 import "influxdata/influxdb/schema"
 
-schema.fieldKeys(bucket: "my-bucket")
+schema.fieldKeys(bucket: "example-bucket")
 ```
 
-## Function definition
+### Return all field keys in a bucket from a non-default time range
 ```js
-package schema
+import "influxdata/influxdb/schema"
 
-fieldKeys = (bucket, predicate=(r) => true, start=-30d) =>
-  tagValues(bucket: bucket, tag: "_field", predicate: predicate, start: start)
+schema.fieldKeys(bucket: "example-bucket", start: -90d, stop: -60d)
 ```
-
-_**Used functions:**
-[schema.tagValues](/flux/v0.x/stdlib/influxdata/influxdb/schema/tagvalues/)_
diff --git a/content/flux/v0.x/stdlib/influxdata/influxdb/schema/fieldsascols.md b/content/flux/v0.x/stdlib/influxdata/influxdb/schema/fieldsascols.md
index 203243658..f1c5b0b79 100644
--- a/content/flux/v0.x/stdlib/influxdata/influxdb/schema/fieldsascols.md
+++ b/content/flux/v0.x/stdlib/influxdata/influxdb/schema/fieldsascols.md
@@ -39,9 +39,9 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "influxdata/influxdb/schema"
 
 from(bucket:"example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "cpu")
-  |> schema.fieldsAsCols()
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "cpu")
+    |> schema.fieldsAsCols()
 ```
 
 {{< expand-wrapper >}}
@@ -74,16 +74,3 @@ _`_start` and `_stop` columns have been omitted._
 
 {{% /expand %}}
 {{< /expand-wrapper >}}
-
-## Function definition
-```js
-package schema
-
-fieldsAsCols = (tables=<-) =>
-  tables
-    |> pivot(
-      rowKey:["_time"],
-      columnKey: ["_field"],
-      valueColumn: "_value"
-    )
-```
diff --git a/content/flux/v0.x/stdlib/influxdata/influxdb/schema/measurementfieldkeys.md b/content/flux/v0.x/stdlib/influxdata/influxdb/schema/measurementfieldkeys.md
index 6aea3e611..5191ea780 100644
--- a/content/flux/v0.x/stdlib/influxdata/influxdb/schema/measurementfieldkeys.md
+++ b/content/flux/v0.x/stdlib/influxdata/influxdb/schema/measurementfieldkeys.md
@@ -24,12 +24,25 @@ The return value is always a single table with a single column, `_value`.
 import "influxdata/influxdb/schema"
 
 schema.measurementFieldKeys(
-  bucket: "example-bucket",
-  measurement: "example-measurement",
-  start: -30d
+    bucket: "example-bucket",
+    measurement: "example-measurement",
+    start: -30d,
 )
 ```
 
+{{% note %}}
+#### Deleted fields
+Fields [explicitly deleted from InfluxDB Cloud](/influxdb/cloud/write-data/delete-data/)
+**do not** appear in results.
+
+#### Expired fields
+- **InfluxDB Cloud**: field keys associated with points outside of the bucket's
+  retention policy **may** appear in results up to an hour after expiring.
+- **InfluxDB OSS**: field keys associated with points outside of the bucket's
+  retention policy **may** appear in results.
+  For more information, see [Data retention in InfluxDB OSS](/{{< latest "influxdb" >}}/reference/internals/data-retention/).
+{{% /note %}}
+
 ## Parameters
 
 ### bucket {data-type="string"}
@@ -39,30 +52,35 @@ Bucket to retrieve field keys from.
 Measurement to list field keys from.
 
 ### start {data-type="duration, time"}
-Oldest time to include in results.
+Earliest time to include in results.
 _Defaults to `-30d`._
 
 Relative start times are defined using negative durations.
 Negative durations are relative to now.
 Absolute start times are defined using [time values](/flux/v0.x/spec/types/#time-types).
 
+### stop {data-type="duration, time"}
+Latest time to include in results.
+_Default is `now()`._
+
+The `stop` time is exclusive, meaning values with a time equal to stop time are
+excluded from results.
+Relative start times are defined using negative durations.
+Negative durations are relative to `now()`.
+Absolute start times are defined using [time values](/flux/v0.x/spec/types/#time-types).
+
 ## Examples
+
+### Return all field keys in a measurement
 ```js
 import "influxdata/influxdb/schema"
 
-schema.measurementFieldKeys(
-  bucket: "telegraf",
-  measurement: "cpu",
-)
+schema.measurementFieldKeys(bucket: "example-bucket",  measurement: "example-measurement")
 ```
 
-## Function definition
+### Return all field keys in a measurement from a non-default time range
 ```js
-package schema
+import "influxdata/influxdb/schema"
 
-measurementFieldKeys = (bucket, measurement, start=-30d) =>
-  fieldKeys(bucket: bucket, predicate: (r) => r._measurement == measurement, start: start)
+schema.measurementFieldKeys(bucket: "example-bucket",  measurement: "example-measurement", start: -90d, stop: -60d)
 ```
-
-_**Used functions:**
-[schema.fieldKeys](/flux/v0.x/stdlib/influxdata/influxdb/schema/fieldkeys/)_
diff --git a/content/flux/v0.x/stdlib/influxdata/influxdb/schema/measurements.md b/content/flux/v0.x/stdlib/influxdata/influxdb/schema/measurements.md
index de4142cf6..001988e50 100644
--- a/content/flux/v0.x/stdlib/influxdata/influxdb/schema/measurements.md
+++ b/content/flux/v0.x/stdlib/influxdata/influxdb/schema/measurements.md
@@ -31,13 +31,36 @@ schema.measurements(bucket: "example-bucket")
 ### bucket {data-type="string"}
 Bucket to retrieve measurements from.
 
-## Function definition
-```js
-package schema
+### start {data-type="duration, time"}
+Earliest time to include in results.
+_Default is `-30d`._
 
-measurements = (bucket) =>
-  tagValues(bucket: bucket, tag: "_measurement")
+Relative start times are defined using negative durations.
+Negative durations are relative to now.
+Absolute start times are defined using [time values](/flux/v0.x/spec/types/#time-types).
+
+### stop {data-type="duration, time"}
+Latest time to include in results.
+_Default is `now()`._
+
+The `stop` time is exclusive, meaning values with a time equal to stop time are
+excluded from results.
+Relative start times are defined using negative durations.
+Negative durations are relative to `now()`.
+Absolute start times are defined using [time values](/flux/v0.x/spec/types/#time-types).
+
+## Examples
+
+### Return all measurements in a bucket
+```js
+import "influxdata/influxdb/schema"
+
+measurements(bucket: "example-bucket")
 ```
 
-_**Used functions:**
-[schema.tagValues()](/flux/v0.x/stdlib/influxdata/influxdb/schema/tagvalues)_
+### Return all measurements in a bucket from a non-default time range
+```js
+import "influxdata/influxdb/schema"
+
+measurements(bucket: "example-bucket", start: -90d, stop: -60d)
+```
diff --git a/content/flux/v0.x/stdlib/influxdata/influxdb/schema/measurementtagkeys.md b/content/flux/v0.x/stdlib/influxdata/influxdb/schema/measurementtagkeys.md
index 977c5dd22..8010e2408 100644
--- a/content/flux/v0.x/stdlib/influxdata/influxdb/schema/measurementtagkeys.md
+++ b/content/flux/v0.x/stdlib/influxdata/influxdb/schema/measurementtagkeys.md
@@ -24,11 +24,24 @@ The return value is always a single table with a single column, `_value`.
 import "influxdata/influxdb/schema"
 
 schema.measurementTagKeys(
-  bucket: "example-bucket",
-  measurement: "cpu"
+    bucket: "example-bucket",
+    measurement: "cpu",
 )
 ```
 
+{{% note %}}
+#### Deleted tags
+Tags [explicitly deleted from InfluxDB](/{{< latest "influxdb" >}}/write-data/delete-data/)
+**do not** appear in results.
+
+#### Expired tags
+- **InfluxDB Cloud**: tags associated with points outside of the bucket's
+  retention policy **may** appear in results up to an hour after expiring.
+- **InfluxDB OSS**: tags associated with points outside of the bucket's
+  retention policy **may** appear in results.
+  For more information, see [Data retention in InfluxDB OSS](/{{< latest "influxdb" >}}/reference/internals/data-retention/).
+{{% /note %}}
+
 ## Parameters
 
 ### bucket {data-type="string"}
@@ -37,16 +50,36 @@ Bucket to return tag keys from for a specific measurement.
 ### measurement {data-type="string"}
 Measurement to return tag keys from.
 
-## Function definition
-```js
-package schema
+### start {data-type="duration, time"}
+Earliest time to include in results.
+_Default is `-30d`._
 
-measurementTagKeys = (bucket, measurement) =>
-  tagKeys(
-    bucket: bucket,
-    predicate: (r) => r._measurement == measurement
-  )
+Relative start times are defined using negative durations.
+Negative durations are relative to now.
+Absolute start times are defined using [time values](/flux/v0.x/spec/types/#time-types).
+
+### stop {data-type="duration, time"}
+Latest time to include in results.
+_Default is `now()`._
+
+The `stop` time is exclusive, meaning values with a time equal to stop time are
+excluded from results.
+Relative start times are defined using negative durations.
+Negative durations are relative to `now()`.
+Absolute start times are defined using [time values](/flux/v0.x/spec/types/#time-types).
+
+## Examples
+
+### Return all tag keys in a measurement
+```js
+import "influxdata/influxdb/schema"
+
+schema.measurementTagKeys(bucket: "example-bucket", measurement: "example-measurement")
 ```
 
-_**Used functions:**
-[schema.tagKeys()](/flux/v0.x/stdlib/influxdata/influxdb/schema/tagkeys)_
+### Return all tag keys in a measurement during a non-default time range
+```js
+import "influxdata/influxdb/schema"
+
+schema.measurementTagKeys(bucket: "example-bucket", measurement: "example-measurement", start: -90d, stop: -60d)
+```
diff --git a/content/flux/v0.x/stdlib/influxdata/influxdb/schema/measurementtagvalues.md b/content/flux/v0.x/stdlib/influxdata/influxdb/schema/measurementtagvalues.md
index b3f70992d..8482fd6b1 100644
--- a/content/flux/v0.x/stdlib/influxdata/influxdb/schema/measurementtagvalues.md
+++ b/content/flux/v0.x/stdlib/influxdata/influxdb/schema/measurementtagvalues.md
@@ -26,12 +26,25 @@ The return value is always a single table with a single column, `_value`.
 import "influxdata/influxdb/schema"
 
 schema.measurementTagValues(
-  bucket: "example-bucket",
-  measurement: "cpu",
-  tag: "host"
+    bucket: "example-bucket",
+    measurement: "cpu",
+    tag: "host",
 )
 ```
 
+{{% note %}}
+#### Deleted tags
+Tags [explicitly deleted from InfluxDB](/{{< latest "influxdb" >}}/write-data/delete-data/)
+**do not** appear in results.
+
+#### Expired tags
+- **InfluxDB Cloud**: tags associated with points outside of the bucket's
+  retention policy **may** appear in results up to an hour after expiring.
+- **InfluxDB OSS**: tags associated with points outside of the bucket's
+  retention policy **may** appear in results.
+  For more information, see [Data retention in InfluxDB OSS](/{{< latest "influxdb" >}}/reference/internals/data-retention/).
+{{% /note %}}
+
 ## Parameters
 
 ### bucket {data-type="string"}
@@ -43,17 +56,42 @@ Measurement to return tag values from.
 ### tag {data-type="string"}
 Tag to return all unique values from.
 
-## Function definition
-```js
-package schema
+### start {data-type="duration, time"}
+Earliest time to include in results.
+_Default is `-30d`._
 
-measurementTagValues = (bucket, measurement, tag) =>
-  tagValues(
-    bucket: bucket,
-    tag: tag,
-    predicate: (r) => r._measurement == measurement
-  )
+Relative start times are defined using negative durations.
+Negative durations are relative to now.
+Absolute start times are defined using [time values](/flux/v0.x/spec/types/#time-types).
+
+### stop {data-type="duration, time"}
+Latest time to include in results.
+_Default is `now()`._
+
+The `stop` time is exclusive, meaning values with a time equal to stop time are
+excluded from results.
+Relative start times are defined using negative durations.
+Negative durations are relative to `now()`.
+Absolute start times are defined using [time values](/flux/v0.x/spec/types/#time-types).
+
+## Examples
+
+### Return all values for a tag in a measurement
+```js
+import "influxdata/influxdb/schema"
+
+schema.measurementTagValues(bucket: "example-bucket", measurement: "example-measurement", tag: "host")
 ```
 
-_**Used functions:**
-[schema.tagValues()](/flux/v0.x/stdlib/influxdata/influxdb/schema/tagvalues)_
+### Return all tag values in a measurement during a non-default time range
+```js
+import "influxdata/influxdb/schema"
+
+schema.measurementTagValues(
+    bucket: "example-bucket",
+    measurement: "example-measurement",
+    tag: "host",
+    start: -90d,
+    stop: -60d,
+)
+```
diff --git a/content/flux/v0.x/stdlib/influxdata/influxdb/schema/tagkeys.md b/content/flux/v0.x/stdlib/influxdata/influxdb/schema/tagkeys.md
index c141830d3..5535837b5 100644
--- a/content/flux/v0.x/stdlib/influxdata/influxdb/schema/tagkeys.md
+++ b/content/flux/v0.x/stdlib/influxdata/influxdb/schema/tagkeys.md
@@ -24,12 +24,25 @@ The return value is always a single table with a single column, `_value`.
 import "influxdata/influxdb/schema"
 
 schema.tagKeys(
-  bucket: "example-bucket",
-  predicate: (r) => true,
-  start: -30d
+    bucket: "example-bucket",
+    predicate: (r) => true,
+    start: -30d,
 )
 ```
 
+{{% note %}}
+#### Deleted tags
+Tags [explicitly deleted from InfluxDB](/{{< latest "influxdb" >}}/write-data/delete-data/)
+**do not** appear in results.
+
+#### Expired tags
+- **InfluxDB Cloud**: tags associated with points outside of the bucket's
+  retention policy **may** appear in results up to an hour after expiring.
+- **InfluxDB OSS**: tags associated with points outside of the bucket's
+  retention policy **may** appear in results.
+  For more information, see [Data retention in InfluxDB OSS](/{{< latest "influxdb" >}}/reference/internals/data-retention/).
+{{% /note %}}
+
 ## Parameters
 
 ### bucket {data-type="string"}
@@ -40,30 +53,35 @@ Predicate function that filters tag keys.
 _Default is `(r) => true`._
 
 ### start {data-type="duration, time"}
-Oldest time to include in results.
+Earliest time to include in results.
 _Default is `-30d`._
 
 Relative start times are defined using negative durations.
 Negative durations are relative to now.
 Absolute start times are defined using [time values](/flux/v0.x/spec/types/#time-types).
 
+### stop {data-type="duration, time"}
+Latest time to include in results.
+_Default is `now()`._
+
+The `stop` time is exclusive, meaning values with a time equal to stop time are
+excluded from results.
+Relative start times are defined using negative durations.
+Negative durations are relative to `now()`.
+Absolute start times are defined using [time values](/flux/v0.x/spec/types/#time-types).
+
 ## Examples
+
+### Return all tag keys in a bucket
 ```js
 import "influxdata/influxdb/schema"
 
-schema.tagKeys(bucket: "my-bucket")
+schema.tagKeys(bucket: "example-bucket")
 ```
 
-
-## Function definition
+### Return all tag keys in a bucket during a non-default time range
 ```js
-package schema
+import "influxdata/influxdb/schema"
 
-tagKeys = (bucket, predicate=(r) => true, start=-30d) =>
-  from(bucket: bucket)
-    |> range(start: start)
-    |> filter(fn: predicate)
-    |> keys()
-    |> keep(columns: ["_value"])
-    |> distinct()
+schema.tagKeys(bucket: "example-bucket", start: -90d, stop: -60d)
 ```
diff --git a/content/flux/v0.x/stdlib/influxdata/influxdb/schema/tagvalues.md b/content/flux/v0.x/stdlib/influxdata/influxdb/schema/tagvalues.md
index b3f119736..f062d30cb 100644
--- a/content/flux/v0.x/stdlib/influxdata/influxdb/schema/tagvalues.md
+++ b/content/flux/v0.x/stdlib/influxdata/influxdb/schema/tagvalues.md
@@ -24,13 +24,26 @@ The return value is always a single table with a single column, `_value`.
 import "influxdata/influxdb/schema"
 
 schema.tagValues(
-  bucket: "example-bucket",
-  tag: "host",
-  predicate: (r) => true,
-  start: -30d
+    bucket: "example-bucket",
+    tag: "host",
+    predicate: (r) => true,
+    start: -30d,
 )
 ```
 
+{{% note %}}
+#### Deleted tags
+Tags [explicitly deleted from InfluxDB](/{{< latest "influxdb" >}}/write-data/delete-data/)
+**do not** appear in results.
+
+#### Expired tags
+- **InfluxDB Cloud**: tags associated with points outside of the bucket's
+  retention policy **may** appear in results up to an hour after expiring.
+- **InfluxDB OSS**: tags associated with points outside of the bucket's
+  retention policy **may** appear in results.
+  For more information, see [Data retention in InfluxDB OSS](/{{< latest "influxdb" >}}/reference/internals/data-retention/).
+{{% /note %}}
+
 ## Parameters
 
 ### bucket {data-type="string"}
@@ -44,32 +57,35 @@ Predicate function that filters tag values.
 _Default is `(r) => true`._
 
 ### start {data-type="duration, time"}
-Oldest time to include in results.
+Earliest time to include in results.
 _Default is `-30d`._
 
 Relative start times are defined using negative durations.
-Negative durations are relative to now.
+Negative durations are relative to `now()`.
+Absolute start times are defined using [time values](/flux/v0.x/spec/types/#time-types).
+
+### stop {data-type="duration, time"}
+Latest time to include in results.
+_Default is `now()`._
+
+The `stop` time is exclusive, meaning values with a time equal to stop time are
+excluded from results.
+Relative start times are defined using negative durations.
+Negative durations are relative to `now()`.
 Absolute start times are defined using [time values](/flux/v0.x/spec/types/#time-types).
 
 ## Examples
+
+### Return all values for a tag in a bucket
 ```js
 import "influxdata/influxdb/schema"
 
-schema.tagValues(
-  bucket: "my-bucket",
-  tag: "host",
-)
+schema.tagValues(bucket: "example-bucket", tag: "host")
 ```
 
-## Function definition
+### Return all tag values in a bucket during a non-default time range
 ```js
-package schema
+import "influxdata/influxdb/schema"
 
-tagValues = (bucket, tag, predicate=(r) => true, start=-30d) =>
-  from(bucket: bucket)
-    |> range(start: start)
-    |> filter(fn: predicate)
-    |> keep(columns: [tag])
-    |> group()
-    |> distinct(column: tag)
+schema.tagValues(bucket: "example-bucket", tag: "host", start: -90d, stop: -60d)
 ```
diff --git a/content/flux/v0.x/stdlib/influxdata/influxdb/secrets/get.md b/content/flux/v0.x/stdlib/influxdata/influxdb/secrets/get.md
index a7e16a37a..792dc5116 100644
--- a/content/flux/v0.x/stdlib/influxdata/influxdb/secrets/get.md
+++ b/content/flux/v0.x/stdlib/influxdata/influxdb/secrets/get.md
@@ -40,8 +40,8 @@ username = secrets.get(key: "POSTGRES_USERNAME")
 password = secrets.get(key: "POSTGRES_PASSWORD")
 
 sql.from(
-  driverName: "postgres",
-  dataSourceName: "postgresql://${username}:${password}@localhost",
-  query:"SELECT * FROM example-table"
+    driverName: "postgres",
+    dataSourceName: "postgresql://${username}:${password}@localhost",
+    query:"SELECT * FROM example-table",
 )
 ```
diff --git a/content/flux/v0.x/stdlib/influxdata/influxdb/tasks/lastsuccess.md b/content/flux/v0.x/stdlib/influxdata/influxdb/tasks/lastsuccess.md
index 90b74ab24..b051208d4 100644
--- a/content/flux/v0.x/stdlib/influxdata/influxdb/tasks/lastsuccess.md
+++ b/content/flux/v0.x/stdlib/influxdata/influxdb/tasks/lastsuccess.md
@@ -35,12 +35,9 @@ The default time value returned if the task has never successfully run.
 ```js
 import "influxdata/influxdb/tasks"
 
-options task = {
-  name: "Example task",
-  every: 30m
-}
+option task = {name: "Example task", every: 30m}
 
 from(bucket: "example-bucket")
-  |> range(start: tasks.lastSuccess(orTime: -task.every))
-  // ...
+    |> range(start: tasks.lastSuccess(orTime: -task.every))
+    // ...
 ```
diff --git a/content/flux/v0.x/stdlib/influxdata/influxdb/to.md b/content/flux/v0.x/stdlib/influxdata/influxdb/to.md
index f17389492..54884f55d 100644
--- a/content/flux/v0.x/stdlib/influxdata/influxdb/to.md
+++ b/content/flux/v0.x/stdlib/influxdata/influxdb/to.md
@@ -1,6 +1,8 @@
 ---
 title: to() function
-description: The `to()` function writes data to an InfluxDB v2.0 bucket.
+description: >
+  `to()` writes data to an **InfluxDB Cloud or v2.x** bucket and outputs the
+  written data.
 aliases:
   - /flux/v0.x/stdlib/universe/to
   - /influxdb/v2.0/reference/flux/functions/outputs/to
@@ -19,29 +21,30 @@ related:
 introduced: 0.7.0
 ---
 
-The `to()` function writes data to an **InfluxDB v2.0** bucket.
+`to()` writes data to an **InfluxDB Cloud or v2.x** bucket and outputs the
+written data.
 
 ```js
 to(
-  bucket: "my-bucket",
-  org: "my-org",
-  host: "localhost:8086",
-  token: "mY5uP3rS3cRe7t0k3n",
-  timeColumn: "_time",
-  tagColumns: ["tag1", "tag2", "tag3"],
-  fieldFn: (r) => ({ r._field: r._value })
+    bucket: "my-bucket",
+    org: "my-org",
+    host: "http://localhost:8086",
+    token: "mY5uP3rS3cRe7t0k3n",
+    timeColumn: "_time",
+    tagColumns: ["tag1", "tag2", "tag3"],
+    fieldFn: (r) => ({ r._field: r._value }),
 )
 
 // OR
 
 to(
-  bucketID: "1234567890",
-  orgID: "0987654321",
-  host: "localhost:8086",
-  token: "mY5uP3rS3cRe7t0k3n",
-  timeColumn: "_time",
-  tagColumns: ["tag1", "tag2", "tag3"],
-  fieldFn: (r) => ({ r._field: r._value })
+    bucketID: "1234567890",
+    orgID: "0987654321",
+    host: "http://localhost:8086",
+    token: "mY5uP3rS3cRe7t0k3n",
+    timeColumn: "_time",
+    tagColumns: ["tag1", "tag2", "tag3"],
+    fieldFn: (r) => ({ r._field: r._value }),
 )
 ```
 
@@ -65,8 +68,7 @@ that includes, at a minimum, the following columns:
 _All other columns are written to InfluxDB as [tags](/{{< latest "influxdb" >}}/reference/key-concepts/data-elements/#tags)._
 
 {{% note %}}
-The `to()` function ignores rows with a null `_time` value and does not write
-them to InfluxDB.
+`to()` drops rows with a null `_time` value and does not write them to InfluxDB.
 {{% /note %}}
 
 ## Parameters
@@ -134,6 +136,10 @@ To learn why, see [Match parameter names](/flux/v0.x/spec/data-model/#match-para
 
 ## Examples
 
+- [Default to() operation](#default-to-operation)
+- [Custom to() operation](#custom-to-operation)
+- [Write to multiple buckets](#write-to-multiple-buckets)
+
 ### Default to() operation
 
 Given the following table:
@@ -144,11 +150,11 @@ Given the following table:
 | 0006  | 0000   | 0009  | "a"          | "temp" | 99.3   |
 | 0007  | 0000   | 0009  | "a"          | "temp" | 99.9   |
 
-The default `to` operation:
+The default `to()` operation:
 
 ```js
-// ...
-|> to(bucket:"my-bucket", org:"my-org")
+data
+    |> to(bucket:"my-bucket", org:"my-org")
 ```
 
 is equivalent to writing the above data using the following line protocol:
@@ -161,7 +167,8 @@ _measurement=a temp=99.9 0007
 
 ### Custom to() operation
 
-The `to()` functions default operation can be overridden. For example, given the following table:
+The default `to()` operation can be overridden.
+For example, given the following table:
 
 | _time | _start | _stop | tag1 | tag2 | hum  | temp  |
 | ----- | ------ | ----- | ---- | ---- | ---- | ----- |
@@ -172,13 +179,13 @@ The `to()` functions default operation can be overridden. For example, given the
 The operation:
 
 ```js
-// ...
-|> to(
-  bucket:"my-bucket",
-  org:"my-org",
-  tagColumns:["tag1"],
-  fieldFn: (r) => ({"hum": r.hum, "temp": r.temp})
-)
+data
+    |> to(
+        bucket:"my-bucket",
+        org:"my-org",
+        tagColumns:["tag1"],
+        fieldFn: (r) => ({"hum": r.hum, "temp": r.temp}),
+    )
 ```
 
 is equivalent to writing the above data using the following line protocol:
@@ -188,3 +195,21 @@ _tag1=a hum=55.3,temp=100.1 0005
 _tag1=a hum=55.4,temp=99.3 0006
 _tag1=a hum=55.5,temp=99.9 0007
 ```
+
+### Write to multiple buckets
+The example below does the following:
+
+1. Writes data to `bucket1` and returns the data as it is written.
+2. Ungroups the returned data.
+3. Counts the number of rows.
+4. Maps columns required to write to InfluxDB.
+5. Writes the modified data to `bucket2`.
+
+```js
+data
+    |> to(bucket: "bucket1")
+    |> group()
+    |> count()
+    |> map(fn: (r) => ({r with _time: now(), _measurement: "writeStats", _field: "numPointsWritten"}))
+    |> to(bucket: "bucket2")
+```
diff --git a/content/flux/v0.x/stdlib/influxdata/influxdb/v1/fieldkeys.md b/content/flux/v0.x/stdlib/influxdata/influxdb/v1/fieldkeys.md
index 3abcebc33..f8b3257b0 100644
--- a/content/flux/v0.x/stdlib/influxdata/influxdb/v1/fieldkeys.md
+++ b/content/flux/v0.x/stdlib/influxdata/influxdb/v1/fieldkeys.md
@@ -30,9 +30,9 @@ The return value is always a single table with a single column, `_value`.
 import "influxdata/influxdb/v1"
 
 v1.fieldKeys(
-  bucket: "example-bucket",
-  predicate: (r) => true,
-  start: -30d
+    bucket: "example-bucket",
+    predicate: (r) => true,
+    start: -30d,
 )
 ```
 
diff --git a/content/flux/v0.x/stdlib/influxdata/influxdb/v1/fieldsascols.md b/content/flux/v0.x/stdlib/influxdata/influxdb/v1/fieldsascols.md
index ef113cca6..000c8d371 100644
--- a/content/flux/v0.x/stdlib/influxdata/influxdb/v1/fieldsascols.md
+++ b/content/flux/v0.x/stdlib/influxdata/influxdb/v1/fieldsascols.md
@@ -45,9 +45,9 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "influxdata/influxdb/v1"
 
 from(bucket:"example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "cpu")
-  |> v1.fieldsAsCols()
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "cpu")
+    |> v1.fieldsAsCols()
 ```
 
 {{< expand-wrapper >}}
@@ -80,16 +80,3 @@ _`_start` and `_stop` columns have been omitted._
 
 {{% /expand %}}
 {{< /expand-wrapper >}}
-
-## Function definition
-```js
-package v1
-
-fieldsAsCols = (tables=<-) =>
-  tables
-    |> pivot(
-      rowKey:["_time"],
-      columnKey: ["_field"],
-      valueColumn: "_value"
-    )
-```
diff --git a/content/flux/v0.x/stdlib/influxdata/influxdb/v1/measurementfieldkeys.md b/content/flux/v0.x/stdlib/influxdata/influxdb/v1/measurementfieldkeys.md
index 6e5ed8df1..8a91a7a82 100644
--- a/content/flux/v0.x/stdlib/influxdata/influxdb/v1/measurementfieldkeys.md
+++ b/content/flux/v0.x/stdlib/influxdata/influxdb/v1/measurementfieldkeys.md
@@ -30,9 +30,9 @@ The return value is always a single table with a single column, `_value`.
 import "influxdata/influxdb/v1"
 
 v1.measurementFieldKeys(
-  bucket: "example-bucket",
-  measurement: "example-measurement",
-  start: -30d
+    bucket: "example-bucket",
+    measurement: "example-measurement",
+    start: -30d,
 )
 ```
 
@@ -56,19 +56,5 @@ Absolute start times are defined using [time values](/flux/v0.x/spec/types/#time
 ```js
 import "influxdata/influxdb/v1"
 
-v1.measurementFieldKeys(
-  bucket: "telegraf",
-  measurement: "cpu",
-)
+v1.measurementFieldKeys(bucket: "telegraf", measurement: "cpu")
 ```
-
-## Function definition
-```js
-package v1
-
-measurementFieldKeys = (bucket, measurement, start=-30d) =>
-  fieldKeys(bucket: bucket, predicate: (r) => r._measurement == measurement, start: start)
-```
-
-_**Used functions:**
-[v1.fieldKeys](/flux/v0.x/stdlib/influxdata/influxdb/schema/fieldkeys/)_
diff --git a/content/flux/v0.x/stdlib/influxdata/influxdb/v1/measurements.md b/content/flux/v0.x/stdlib/influxdata/influxdb/v1/measurements.md
index 07f2bfcd1..318cffce0 100644
--- a/content/flux/v0.x/stdlib/influxdata/influxdb/v1/measurements.md
+++ b/content/flux/v0.x/stdlib/influxdata/influxdb/v1/measurements.md
@@ -36,14 +36,3 @@ v1.measurements(bucket: "example-bucket")
 
 ### bucket {data-type="string"}
 Bucket to retrieve measurements from.
-
-## Function definition
-```js
-package v1
-
-measurements = (bucket) =>
-  tagValues(bucket: bucket, tag: "_measurement")
-```
-
-_**Used functions:**
-[v1.tagValues()](/flux/v0.x/stdlib/influxdata/influxdb/schema/tagvalues)_
diff --git a/content/flux/v0.x/stdlib/influxdata/influxdb/v1/measurementtagkeys.md b/content/flux/v0.x/stdlib/influxdata/influxdb/v1/measurementtagkeys.md
index 3235737a9..1de146d7c 100644
--- a/content/flux/v0.x/stdlib/influxdata/influxdb/v1/measurementtagkeys.md
+++ b/content/flux/v0.x/stdlib/influxdata/influxdb/v1/measurementtagkeys.md
@@ -30,8 +30,8 @@ The return value is always a single table with a single column, `_value`.
 import "influxdata/influxdb/v1"
 
 v1.measurementTagKeys(
-  bucket: "example-bucket",
-  measurement: "cpu"
+    bucket: "example-bucket",
+    measurement: "cpu",
 )
 ```
 
@@ -42,17 +42,3 @@ Bucket to return tag keys from for a specific measurement.
 
 ### measurement {data-type="string"}
 Measurement to return tag keys from.
-
-## Function definition
-```js
-package v1
-
-measurementTagKeys = (bucket, measurement) =>
-  tagKeys(
-    bucket: bucket,
-    predicate: (r) => r._measurement == measurement
-  )
-```
-
-_**Used functions:**
-[v1.tagKeys()](/flux/v0.x/stdlib/influxdata/influxdb/schema/tagkeys)_
diff --git a/content/flux/v0.x/stdlib/influxdata/influxdb/v1/measurementtagvalues.md b/content/flux/v0.x/stdlib/influxdata/influxdb/v1/measurementtagvalues.md
index d4d2c491b..f5dc090ce 100644
--- a/content/flux/v0.x/stdlib/influxdata/influxdb/v1/measurementtagvalues.md
+++ b/content/flux/v0.x/stdlib/influxdata/influxdb/v1/measurementtagvalues.md
@@ -30,9 +30,9 @@ The return value is always a single table with a single column, `_value`.
 import "influxdata/influxdb/v1"
 
 v1.measurementTagValues(
-  bucket: "example-bucket",
-  measurement: "cpu",
-  tag: "host"
+    bucket: "example-bucket",
+    measurement: "cpu",
+    tag: "host",
 )
 ```
 
@@ -46,18 +46,3 @@ Measurement to return tag values from.
 
 ### tag {data-type="string"}
 Tag to return all unique values from.
-
-## Function definition
-```js
-package v1
-
-measurementTagValues = (bucket, measurement, tag) =>
-  tagValues(
-    bucket: bucket,
-    tag: tag,
-    predicate: (r) => r._measurement == measurement
-  )
-```
-
-_**Used functions:**
-[v1.tagValues()](/flux/v0.x/stdlib/influxdata/influxdb/schema/tagvalues)_
diff --git a/content/flux/v0.x/stdlib/influxdata/influxdb/v1/tagkeys.md b/content/flux/v0.x/stdlib/influxdata/influxdb/v1/tagkeys.md
index f7da29d5a..a1f3c5a1c 100644
--- a/content/flux/v0.x/stdlib/influxdata/influxdb/v1/tagkeys.md
+++ b/content/flux/v0.x/stdlib/influxdata/influxdb/v1/tagkeys.md
@@ -30,9 +30,9 @@ The return value is always a single table with a single column, `_value`.
 import "influxdata/influxdb/v1"
 
 v1.tagKeys(
-  bucket: "example-bucket",
-  predicate: (r) => true,
-  start: -30d
+    bucket: "example-bucket",
+    predicate: (r) => true,
+    start: -30d,
 )
 ```
 
@@ -59,17 +59,3 @@ import "influxdata/influxdb/v1"
 
 v1.tagKeys(bucket: "my-bucket")
 ```
-
-
-## Function definition
-```js
-package v1
-
-tagKeys = (bucket, predicate=(r) => true, start=-30d) =>
-  from(bucket: bucket)
-    |> range(start: start)
-    |> filter(fn: predicate)
-    |> keys()
-    |> keep(columns: ["_value"])
-    |> distinct()
-```
diff --git a/content/flux/v0.x/stdlib/influxdata/influxdb/v1/tagvalues.md b/content/flux/v0.x/stdlib/influxdata/influxdb/v1/tagvalues.md
index d1aa317c8..2acad48ac 100644
--- a/content/flux/v0.x/stdlib/influxdata/influxdb/v1/tagvalues.md
+++ b/content/flux/v0.x/stdlib/influxdata/influxdb/v1/tagvalues.md
@@ -30,10 +30,10 @@ The return value is always a single table with a single column, `_value`.
 import "influxdata/influxdb/v1"
 
 v1.tagValues(
-  bucket: "example-bucket",
-  tag: "host",
-  predicate: (r) => true,
-  start: -30d
+    bucket: "example-bucket",
+    tag: "host",
+    predicate: (r) => true,
+    start: -30d,
 )
 ```
 
@@ -61,21 +61,5 @@ Absolute start times are defined using [time values](/flux/v0.x/spec/types/#time
 ```js
 import "influxdata/influxdb/v1"
 
-v1.tagValues(
-  bucket: "my-bucket",
-  tag: "host",
-)
-```
-
-## Function definition
-```js
-package v1
-
-tagValues = (bucket, tag, predicate=(r) => true, start=-30d) =>
-  from(bucket: bucket)
-    |> range(start: start)
-    |> filter(fn: predicate)
-    |> group(columns: [tag])
-    |> distinct(column: tag)
-    |> keep(columns: ["_value"])
+v1.tagValues(bucket: "my-bucket", tag: "host")
 ```
diff --git a/content/flux/v0.x/stdlib/interpolate/linear.md b/content/flux/v0.x/stdlib/interpolate/linear.md
index 00caa8a72..3e36fa0d5 100644
--- a/content/flux/v0.x/stdlib/interpolate/linear.md
+++ b/content/flux/v0.x/stdlib/interpolate/linear.md
@@ -46,7 +46,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "interpolate"
 
 data
-  |> interpolate.linear(every: 1d)
+    |> interpolate.linear(every: 1d)
 ```
 
 {{< flex >}}
diff --git a/content/flux/v0.x/stdlib/pagerduty/actionfromseverity.md b/content/flux/v0.x/stdlib/pagerduty/actionfromseverity.md
index d0f28d662..a999b8bdc 100644
--- a/content/flux/v0.x/stdlib/pagerduty/actionfromseverity.md
+++ b/content/flux/v0.x/stdlib/pagerduty/actionfromseverity.md
@@ -21,9 +21,7 @@ All other severities convert to `trigger`.
 ```js
 import "pagerduty"
 
-pagerduty.actionFromSeverity(
-  severity: "ok"
-)
+pagerduty.actionFromSeverity(severity: "ok")
 
 // Returns "resolve"
 ```
@@ -32,12 +30,3 @@ pagerduty.actionFromSeverity(
 
 ### severity {data-type="float"}
 The severity to convert to a PagerDuty action.
-
-## Function definition
-```js
-import "strings"
-
-actionFromSeverity = (severity) =>
-  if strings.toLower(v: severity) == "ok" then "resolve"
-  else "trigger"
-```
diff --git a/content/flux/v0.x/stdlib/pagerduty/dedupkey.md b/content/flux/v0.x/stdlib/pagerduty/dedupkey.md
index f4f1b5bb0..ee80c2151 100644
--- a/content/flux/v0.x/stdlib/pagerduty/dedupkey.md
+++ b/content/flux/v0.x/stdlib/pagerduty/dedupkey.md
@@ -24,7 +24,7 @@ the group key to create a unique deduplication key for each input table.
 import "pagerduty"
 
 pagerduty.dedupKey(
-  exclude: ["_start", "_stop", "_level"]
+    exclude: ["_start", "_stop", "_level"],
 )
 ```
 
@@ -41,9 +41,9 @@ Default is `["_start", "_stop", "_level"]`.
 import "pagerduty"
 
 from(bucket: "default")
-  |> range(start: -5m)
-  |> filter(fn: (r) => r._measurement == "mem")
-  |> pagerduty.dedupKey()
+    |> range(start: -5m)
+    |> filter(fn: (r) => r._measurement == "mem")
+    |> pagerduty.dedupKey()
 ```
 
 {{% expand "View function updates" %}}
diff --git a/content/flux/v0.x/stdlib/pagerduty/endpoint.md b/content/flux/v0.x/stdlib/pagerduty/endpoint.md
index 398c2e2c6..55431b79b 100644
--- a/content/flux/v0.x/stdlib/pagerduty/endpoint.md
+++ b/content/flux/v0.x/stdlib/pagerduty/endpoint.md
@@ -22,7 +22,7 @@ a message to PagerDuty that includes output data.
 import "pagerduty"
 
 pagerduty.endpoint(
-  url: "https://events.pagerduty.com/v2/enqueue"
+    url: "https://events.pagerduty.com/v2/enqueue"
 )
 ```
 
@@ -71,27 +71,25 @@ routingKey = secrets.get(key: "PAGERDUTY_ROUTING_KEY")
 toPagerDuty = pagerduty.endpoint()
 
 crit_statuses = from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> filter(fn: (r) => r._measurement == "statuses" and r.status == "crit")
+    |> range(start: -1m)
+    |> filter(fn: (r) => r._measurement == "statuses" and r.status == "crit")
 
 crit_statuses
-  |> toPagerDuty(mapFn: (r) => ({ r with
-      routingKey: routingKey,
-      client: r.client,
-      clientURL: r.clientURL,
-      class: r.class,
-      eventAction: r.eventAction,
-      group: r.group,
-      severity: r.severity,
-      component: r.component,
-      source: r.source,
-      summary: r.summary,
-      component: r.component,
-      timestamp: r._time,
-      customDetails: {
-        "ping time": lastReported.ping,
-        load: lastReported.load
-      }
-    })
-  )()
+    |> toPagerDuty(
+        mapFn: (r) => ({r with
+            routingKey: routingKey,
+            client: r.client,
+            clientURL: r.clientURL,
+            class: r.class,
+            eventAction: r.eventAction,
+            group: r.group,
+            severity: r.severity,
+            component: r.component,
+            source: r.source,
+            summary: r.summary,
+            component: r.component,
+            timestamp: r._time,
+            customDetails: {"ping time": lastReported.ping, load: lastReported.load},
+        }),
+    )()
 ```
diff --git a/content/flux/v0.x/stdlib/pagerduty/sendevent.md b/content/flux/v0.x/stdlib/pagerduty/sendevent.md
index c4f1b8b71..b1edd1ea4 100644
--- a/content/flux/v0.x/stdlib/pagerduty/sendevent.md
+++ b/content/flux/v0.x/stdlib/pagerduty/sendevent.md
@@ -20,20 +20,20 @@ The `pagerduty.sendEvent()` function sends an event to PagerDuty.
 import "pagerduty"
 
 pagerduty.sendEvent(
-  pagerdutyURL: "https://events.pagerduty.com/v2/enqueue",
-  routingKey: "ExampleRoutingKey",
-  client: "ExampleClient",
-  clientURL: "http://examplepagerdutyclient.com",
-  dedupkey: "ExampleDedupKey",
-  class: "cpu usage",
-  group: "app-stack",
-  severity: "ok",
-  eventAction: "trigger",
-  source: "monitoringtool:vendor:region",
-  component: "example-component",
-  summary: "This is an example summary.",
-  timestamp: "2016-07-17T08:42:58.315+0000",
-  customDetails: {exampleDetail: "Details"}
+    pagerdutyURL: "https://events.pagerduty.com/v2/enqueue",
+    routingKey: "ExampleRoutingKey",
+    client: "ExampleClient",
+    clientURL: "http://examplepagerdutyclient.com",
+    dedupKey: "ExampleDedupKey",
+    class: "cpu usage",
+    group: "app-stack",
+    severity: "ok",
+    eventAction: "trigger",
+    source: "monitoringtool:vendor:region",
+    component: "example-component",
+    summary: "This is an example summary.",
+    timestamp: "2016-07-17T08:42:58.315+0000",
+    customDetails: {exampleDetail: "Details"},
 )
 ```
 
@@ -52,14 +52,14 @@ The name of the client sending the alert.
 ### clientURL {data-type="string"}
 The URL of the client sending the alert.
 
-### dedupkey {data-type="string"}
+### dedupKey {data-type="string"}
 A per-alert ID that acts as deduplication key and allows you to acknowledge or
 change the severity of previous messages.
 Supports a maximum of 255 characters.
 
 {{% note %}}
 When using [`pagerduty.endpoint()`](/flux/v0.x/stdlib/pagerduty/endpoint/)
-to send data to PagerDuty, the function uses the [`pagerduty.dedupKey()` function](/flux/v0.x/stdlib/pagerduty/dedupkey/) to populate the `dedupkey` parameter.
+to send data to PagerDuty, the function uses the [`pagerduty.dedupKey()` function](/flux/v0.x/stdlib/pagerduty/dedupkey/) to populate the `dedupKey` parameter.
 {{% /note %}}
 
 ### class {data-type="string"}
@@ -115,29 +115,25 @@ Additional event details.
 import "pagerduty"
 import "influxdata/influxdb/secrets"
 
-lastReported =
-  from(bucket: "example-bucket")
+lastReported = from(bucket: "example-bucket")
     |> range(start: -1m)
     |> filter(fn: (r) => r._measurement == "statuses")
     |> last()
     |> findRecord(fn: (key) => true, idx: 0)
 
 pagerduty.sendEvent(
-  routingKey: "example-routing-key",
-  client: lastReported.client,
-  clientURL: lastReported.clientURL,
-  class: lastReported.class,
-  eventAction: lastReported.eventAction,
-  group: lastReported.group,
-  severity: lastReported.severity,
-  component: lastReported.component,
-  source: lastReported.source,
-  component: lastReported.component,
-  summary: lastReported.summary,
-  timestamp: lastReported._time,
-  customDetails: {
-    "ping time": lastReported.ping,
-    load: lastReported.load
-  }
+    routingKey: "example-routing-key",
+    client: lastReported.client,
+    clientURL: lastReported.clientURL,
+    class: lastReported.class,
+    eventAction: lastReported.eventAction,
+    group: lastReported.group,
+    severity: lastReported.severity,
+    component: lastReported.component,
+    source: lastReported.source,
+    component: lastReported.component,
+    summary: lastReported.summary,
+    timestamp: lastReported._time,
+    customDetails: {"ping time": lastReported.ping, load: lastReported.load},
 )
 ```
\ No newline at end of file
diff --git a/content/flux/v0.x/stdlib/pagerduty/severityfromlevel.md b/content/flux/v0.x/stdlib/pagerduty/severityfromlevel.md
index ab6fe9e48..f2d14e932 100644
--- a/content/flux/v0.x/stdlib/pagerduty/severityfromlevel.md
+++ b/content/flux/v0.x/stdlib/pagerduty/severityfromlevel.md
@@ -21,9 +21,7 @@ a PagerDuty severity.
 ```js
 import "pagerduty"
 
-pagerduty.severityFromLevel(
-  level: "crit"
-)
+pagerduty.severityFromLevel(level: "crit")
 
 // Returns "critical"
 ```
@@ -39,18 +37,3 @@ pagerduty.severityFromLevel(
 
 ### level {data-type="string"}
 The InfluxDB status level to convert to a PagerDuty severity.
-
-## Function definition
-```js
-import "strings"
-
-severityFromLevel = (level) => {
-  lvl = strings.toLower(v:level)
-  sev = if lvl == "warn" then "warning"
-      else if lvl == "crit" then "critical"
-      else if lvl == "info" then "info"
-      else if lvl == "ok" then "info"
-      else "error"
-  return sev
-}
-```
diff --git a/content/flux/v0.x/stdlib/pushbullet/endpoint.md b/content/flux/v0.x/stdlib/pushbullet/endpoint.md
index 5d4cf2671..dcb4fd55c 100644
--- a/content/flux/v0.x/stdlib/pushbullet/endpoint.md
+++ b/content/flux/v0.x/stdlib/pushbullet/endpoint.md
@@ -22,8 +22,8 @@ and sends a notification of type `note`.
 import "pushbullet"
 
 pushbullet.endpoint(
-  url: "https://api.pushbullet.com/v2/pushes",
-  token: ""
+    url: "https://api.pushbullet.com/v2/pushes",
+    token: "",
 )
 ```
 
@@ -62,17 +62,11 @@ import "influxdata/influxdb/secrets"
 token = secrets.get(key: "PUSHBULLET_TOKEN")
 e = pushbullet.endpoint(token: token)
 
-lastReported =
-  from(bucket: "example-bucket")
+lastReported = from(bucket: "example-bucket")
     |> range(start: -10m)
     |> filter(fn: (r) => r._measurement == "statuses")
     |> last()
 
 lastReported
-  |> e(mapFn: (r) => ({
-      r with
-      title: r.title,
-      text: "${string(v: r._time)}: ${r.status}."
-    })
-  )()
+    |> e(mapFn: (r) => ({r with title: r.title, text: "${string(v: r._time)}: ${r.status}."}))()
 ```
diff --git a/content/flux/v0.x/stdlib/pushbullet/pushdata.md b/content/flux/v0.x/stdlib/pushbullet/pushdata.md
index 7acfb110e..c22ac7c32 100644
--- a/content/flux/v0.x/stdlib/pushbullet/pushdata.md
+++ b/content/flux/v0.x/stdlib/pushbullet/pushdata.md
@@ -20,15 +20,15 @@ The `pushbullet.pushData()` function sends a push notification to the
 import "pushbullet"
 
 pushbullet.pushData(
-  url: "https://api.pushbullet.com/v2/pushes",
-  token: "",
-  data: {
-    "type": "link",
-    "title": "This is a notification!",
-    "body": "This notification came from Flux.",
-    "url": "http://example.com"
-  }
-)
+    url: "https://api.pushbullet.com/v2/pushes",
+    token: "",
+    data: {
+        "type": "link",
+        "title": "This is a notification!",
+        "body": "This notification came from Flux.",
+        "url": "http://example.com"
+    },
+  )
 ```
 
 ## Parameters
@@ -56,8 +56,7 @@ import "influxdata/influxdb/secrets"
 
 token = secrets.get(key: "PUSHBULLET_TOKEN")
 
-lastReported =
-  from(bucket: "example-bucket")
+lastReported = from(bucket: "example-bucket")
     |> range(start: -1m)
     |> filter(fn: (r) => r._measurement == "statuses")
     |> last()
@@ -65,12 +64,12 @@ lastReported =
     |> getRecord(idx: 0)
 
 pushbullet.pushData(
-  token: token,
-  data: {
-    "type": "link",
-    "title": "Last reported status",
-    "body": "${lastReported._time}: ${lastReported.status}."
-    "url": "${lastReported.statusURL}"
-  }
+    token: token,
+    data: {
+        "type": "link",
+        "title": "Last reported status",
+        "body": "${lastReported._time}: ${lastReported.status}.",
+        "url": "${lastReported.statusURL}",
+    }
 )
 ```
diff --git a/content/flux/v0.x/stdlib/pushbullet/pushnote.md b/content/flux/v0.x/stdlib/pushbullet/pushnote.md
index 4ae7ce18f..4aa1bd695 100644
--- a/content/flux/v0.x/stdlib/pushbullet/pushnote.md
+++ b/content/flux/v0.x/stdlib/pushbullet/pushnote.md
@@ -21,10 +21,10 @@ to the Pushbullet API.
 import "pushbullet"
 
 pushbullet.pushNote(
-  url: "https://api.pushbullet.com/v2/pushes",
-  token: "",
-  title: "This is a push notification!",
-  text: "This push notification came from Flux."
+    url: "https://api.pushbullet.com/v2/pushes",
+    token: "",
+    title: "This is a push notification!",
+    text: "This push notification came from Flux.",
 )
 ```
 
@@ -56,8 +56,7 @@ import "influxdata/influxdb/secrets"
 
 token = secrets.get(key: "PUSHBULLET_TOKEN")
 
-lastReported =
-  from(bucket: "example-bucket")
+lastReported = from(bucket: "example-bucket")
     |> range(start: -1m)
     |> filter(fn: (r) => r._measurement == "statuses")
     |> last()
@@ -65,8 +64,8 @@ lastReported =
     |> getRecord(idx: 0)
 
 pushbullet.pushNote(
-  token: token,
-  title: "Last reported status",
-  text: "${lastReported._time}: ${lastReported.status}."
+    token: token,
+    title: "Last reported status",
+    text: "${lastReported._time}: ${lastReported.status}.",
 )
 ```
diff --git a/content/flux/v0.x/stdlib/regexp/compile.md b/content/flux/v0.x/stdlib/regexp/compile.md
index 70ba88852..d18ff8581 100644
--- a/content/flux/v0.x/stdlib/regexp/compile.md
+++ b/content/flux/v0.x/stdlib/regexp/compile.md
@@ -40,14 +40,9 @@ The string value to parse into a regular expression.
 import "regexp"
 
 data
-  |> map(fn: (r) => ({
-      r with
-      regexStr: r.regexStr,
-      _value: r._value,
-      firstRegexMatch: findString(
-        r: regexp.compile(v: regexStr),
-        v: r._value
-      )
-    })
-  )
+    |> map(fn: (r) => ({r with
+        regexStr: r.regexStr,
+        _value: r._value,
+        firstRegexMatch: findString(r: regexp.compile(v: regexStr), v: r._value)
+    }))
 ```
diff --git a/content/flux/v0.x/stdlib/regexp/findstring.md b/content/flux/v0.x/stdlib/regexp/findstring.md
index 8a81d371f..048f75ee3 100644
--- a/content/flux/v0.x/stdlib/regexp/findstring.md
+++ b/content/flux/v0.x/stdlib/regexp/findstring.md
@@ -43,11 +43,10 @@ The string value to search.
 import "regexp"
 
 data
-  |> map(fn: (r) => ({
-      r with
-      message: r.message,
-      regexp: r.regexp,
-      match: regexp.findString(r: r.regexp, v: r.message)
-    })
-  )
+    |> map(fn: (r) => ({r with
+          message: r.message,
+          regexp: r.regexp,
+          match: regexp.findString(r: r.regexp, v: r.message)
+        })
+    )
 ```
diff --git a/content/flux/v0.x/stdlib/regexp/findstringindex.md b/content/flux/v0.x/stdlib/regexp/findstringindex.md
index 69deb8e75..f1f6d2444 100644
--- a/content/flux/v0.x/stdlib/regexp/findstringindex.md
+++ b/content/flux/v0.x/stdlib/regexp/findstringindex.md
@@ -46,14 +46,13 @@ The string value to search.
 import "regexp"
 
 data
-  |> map(fn: (r) => ({
-      r with
-      regexStr: r.regexStr,
-      _value: r._value,
-      matchIndex: regexp.findStringIndex(
-        r: regexp.compile(r.regexStr),
-        v: r._value
-      )
-    })
-  )
+    |> map(fn: (r) => ({r with
+            regexStr: r.regexStr,
+            _value: r._value,
+            matchIndex: regexp.findStringIndex(
+                r: regexp.compile(r.regexStr),
+                v: r._value
+            )
+        })
+    )
 ```
diff --git a/content/flux/v0.x/stdlib/regexp/getstring.md b/content/flux/v0.x/stdlib/regexp/getstring.md
index 5fddac744..a4ca95fab 100644
--- a/content/flux/v0.x/stdlib/regexp/getstring.md
+++ b/content/flux/v0.x/stdlib/regexp/getstring.md
@@ -37,13 +37,6 @@ The regular expression object to convert to a string.
 
 ###### Convert regular expressions into strings in each row
 ```js
-import "regexp"
-
 data
-  |> map(fn: (r) => ({
-      r with
-      regex: r.regex,
-      regexStr: regexp.getString(r: r.regex)
-    })
-  )
+    |> map(fn: (r) => ({r with regex: r.regex, regexStr: regexp.getString(r: r.regex)}))
 ```
diff --git a/content/flux/v0.x/stdlib/regexp/matchregexpstring.md b/content/flux/v0.x/stdlib/regexp/matchregexpstring.md
index f8295e538..cb359a6df 100644
--- a/content/flux/v0.x/stdlib/regexp/matchregexpstring.md
+++ b/content/flux/v0.x/stdlib/regexp/matchregexpstring.md
@@ -43,10 +43,5 @@ The string value to search.
 import "regexp"
 
 data
-  |> filter(fn: (r) =>
-    regexp.matchRegexpString(
-      r: /Alert\:/,
-      v: r.message
-    )
-  )
+    |> filter(fn: (r) => regexp.matchRegexpString(r: /Alert:/, v: r.message))
 ```
diff --git a/content/flux/v0.x/stdlib/regexp/quotemeta.md b/content/flux/v0.x/stdlib/regexp/quotemeta.md
index b8c894076..bde846d1a 100644
--- a/content/flux/v0.x/stdlib/regexp/quotemeta.md
+++ b/content/flux/v0.x/stdlib/regexp/quotemeta.md
@@ -38,10 +38,5 @@ The string that contains regular expression metacharacters to escape.
 import "regexp"
 
 data
-  |> map(fn: (r) => ({
-      r with
-      notes: r.notes,
-      notes_escaped: regexp.quoteMeta(v: r.notes)
-    })
-  )
+    |> map(fn: (r) => ({r with notes: r.notes, notes_escaped: regexp.quoteMeta(v: r.notes)}))
 ```
diff --git a/content/flux/v0.x/stdlib/regexp/replaceallstring.md b/content/flux/v0.x/stdlib/regexp/replaceallstring.md
index e61c57377..8cea33325 100644
--- a/content/flux/v0.x/stdlib/regexp/replaceallstring.md
+++ b/content/flux/v0.x/stdlib/regexp/replaceallstring.md
@@ -46,13 +46,12 @@ The replacement for matches to `r`.
 import "regexp"
 
 data
-  |> map(fn: (r) => ({
-      r with
-      message: r.message,
-      updated_message: regexp.replaceAllString(
-        r: /cat|bird|ferret/,
-        v: r.message,
-        t: "dog"
-      )
-  }))
+    |> map(fn: (r) => ({r with
+        message: r.message,
+        updated_message: regexp.replaceAllString(
+            r: /cat|bird|ferret/,
+            v: r.message,
+            t: "dog",
+        )
+    }))
 ```
diff --git a/content/flux/v0.x/stdlib/sampledata/bool.md b/content/flux/v0.x/stdlib/sampledata/bool.md
index e0eb23c6a..c759e4a6b 100644
--- a/content/flux/v0.x/stdlib/sampledata/bool.md
+++ b/content/flux/v0.x/stdlib/sampledata/bool.md
@@ -15,9 +15,7 @@ flux/v0.x/tags: [inputs, sample data]
 ```js
 import "sampledata"
 
-sampledata.bool(
-  includeNull: false
-)
+sampledata.bool(includeNull: false)
 ```
 
 ## Parameters
@@ -39,6 +37,7 @@ import "sampledata"
 
 sampledata.bool()
 ```
+
 ##### Output tables
 {{% flux/sample "bool" %}}
 
@@ -50,5 +49,6 @@ import "sampledata"
 
 sampledata.bool(includeNull: true)
 ```
+
 ##### Output tables
 {{% flux/sample "bool" true %}}
\ No newline at end of file
diff --git a/content/flux/v0.x/stdlib/sampledata/float.md b/content/flux/v0.x/stdlib/sampledata/float.md
index 2d3a81360..cfaa2a4ad 100644
--- a/content/flux/v0.x/stdlib/sampledata/float.md
+++ b/content/flux/v0.x/stdlib/sampledata/float.md
@@ -15,9 +15,7 @@ flux/v0.x/tags: [inputs, sample data]
 ```js
 import "sampledata"
 
-sampledata.float(
-  includeNull: false
-)
+sampledata.float(includeNull: false)
 ```
 
 ## Parameters
@@ -39,6 +37,7 @@ import "sampledata"
 
 sampledata.float()
 ```
+
 ##### Output tables
 {{% flux/sample "float" %}}
 
@@ -50,5 +49,6 @@ import "sampledata"
 
 sampledata.float(includeNull: true)
 ```
+
 ##### Output tables
 {{% flux/sample "float" true %}}
\ No newline at end of file
diff --git a/content/flux/v0.x/stdlib/sampledata/int.md b/content/flux/v0.x/stdlib/sampledata/int.md
index a91e1e1d6..bf27bd578 100644
--- a/content/flux/v0.x/stdlib/sampledata/int.md
+++ b/content/flux/v0.x/stdlib/sampledata/int.md
@@ -15,9 +15,7 @@ flux/v0.x/tags: [inputs, sample data]
 ```js
 import "sampledata"
 
-sampledata.int(
-  includeNull: false
-)
+sampledata.int(includeNull: false)
 ```
 
 ## Parameters
@@ -39,6 +37,7 @@ import "sampledata"
 
 sampledata.int()
 ```
+
 ##### Output tables
 {{% flux/sample "int" %}}
 
@@ -50,5 +49,6 @@ import "sampledata"
 
 sampledata.int(includeNull: true)
 ```
+
 ##### Output tables
 {{% flux/sample "int" true %}}
\ No newline at end of file
diff --git a/content/flux/v0.x/stdlib/sampledata/numericbool.md b/content/flux/v0.x/stdlib/sampledata/numericbool.md
index 5cc0a5ae6..96fcbf76a 100644
--- a/content/flux/v0.x/stdlib/sampledata/numericbool.md
+++ b/content/flux/v0.x/stdlib/sampledata/numericbool.md
@@ -15,9 +15,7 @@ flux/v0.x/tags: [inputs, sample data]
 ```js
 import "sampledata"
 
-sampledata.numericBool(
-  includeNull: false
-)
+sampledata.numericBool(includeNull: false)
 ```
 
 ## Parameters
@@ -39,6 +37,7 @@ import "sampledata"
 
 sampledata.numericBool()
 ```
+
 ##### Output tables
 {{% flux/sample "numericBool" %}}
 
@@ -50,5 +49,6 @@ import "sampledata"
 
 sampledata.numericBool(includeNull: true)
 ```
+
 ##### Output tables
 {{% flux/sample "numericBool" true %}}
\ No newline at end of file
diff --git a/content/flux/v0.x/stdlib/sampledata/string.md b/content/flux/v0.x/stdlib/sampledata/string.md
index 434db3fcd..3f96ad87b 100644
--- a/content/flux/v0.x/stdlib/sampledata/string.md
+++ b/content/flux/v0.x/stdlib/sampledata/string.md
@@ -15,9 +15,7 @@ flux/v0.x/tags: [inputs, sample data]
 ```js
 import "sampledata"
 
-sampledata.string(
-  includeNull: false
-)
+sampledata.string(includeNull: false)
 ```
 
 ## Parameters
@@ -39,6 +37,7 @@ import "sampledata"
 
 sampledata.string()
 ```
+
 ##### Output tables
 {{% flux/sample "string" %}}
 
@@ -50,5 +49,6 @@ import "sampledata"
 
 sampledata.string(includeNull: true)
 ```
+
 ##### Output tables
 {{% flux/sample "string" true %}}
\ No newline at end of file
diff --git a/content/flux/v0.x/stdlib/sampledata/uint.md b/content/flux/v0.x/stdlib/sampledata/uint.md
index 8fb780244..ff0c92128 100644
--- a/content/flux/v0.x/stdlib/sampledata/uint.md
+++ b/content/flux/v0.x/stdlib/sampledata/uint.md
@@ -15,9 +15,7 @@ flux/v0.x/tags: [inputs, sample data]
 ```js
 import "sampledata"
 
-sampledata.uint(
-  includeNull: false
-)
+sampledata.uint(includeNull: false)
 ```
 
 ## Parameters
@@ -50,5 +48,6 @@ import "sampledata"
 
 sampledata.uint(includeNull: true)
 ```
+
 ##### Output tables
 {{% flux/sample "uint" true %}}
\ No newline at end of file
diff --git a/content/flux/v0.x/stdlib/slack/endpoint.md b/content/flux/v0.x/stdlib/slack/endpoint.md
index 6f3a39717..0063d8836 100644
--- a/content/flux/v0.x/stdlib/slack/endpoint.md
+++ b/content/flux/v0.x/stdlib/slack/endpoint.md
@@ -21,8 +21,8 @@ The `slack.endpoint()` function sends a message to Slack that includes output da
 import "slack"
 
 slack.endpoint(
-  url: "https://slack.com/api/chat.postMessage",
-  token: "mySuPerSecRetTokEn"
+    url: "https://slack.com/api/chat.postMessage",
+    token: "mySuPerSecRetTokEn",
 )
 ```
 
@@ -73,14 +73,9 @@ token = secrets.get(key: "SLACK_TOKEN")
 toSlack = slack.endpoint(token: token)
 
 crit_statuses = from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> filter(fn: (r) => r._measurement == "statuses" and r.status == "crit")
+    |> range(start: -1m)
+    |> filter(fn: (r) => r._measurement == "statuses" and r.status == "crit")
 
 crit_statuses
-  |> toSlack(mapFn: (r) => ({
-      channel: "Alerts",
-      text: r._message,
-      color: "danger",
-    })
-  )()
+    |> toSlack(mapFn: (r) => ({channel: "Alerts", text: r._message, color: "danger"}))()
 ```
diff --git a/content/flux/v0.x/stdlib/slack/message.md b/content/flux/v0.x/stdlib/slack/message.md
index 689bf18a2..0cc101e3d 100644
--- a/content/flux/v0.x/stdlib/slack/message.md
+++ b/content/flux/v0.x/stdlib/slack/message.md
@@ -23,11 +23,11 @@ or with a [Slack webhook](https://api.slack.com/incoming-webhooks).
 import "slack"
 
 slack.message(
-  url: "https://slack.com/api/chat.postMessage",
-  token: "mySuPerSecRetTokEn",
-  channel: "#flux",,
-  text: "This is a message from the Flux slack.message() function.",
-  color: "good"
+    url: "https://slack.com/api/chat.postMessage",
+    token: "mySuPerSecRetTokEn",
+    channel: "#flux",
+    text: "This is a message from the Flux slack.message() function.",
+    color: "good",
 )
 ```
 
@@ -73,8 +73,7 @@ A token is only required if using the Slack chat.postMessage API.
 ```js
 import "slack"
 
-lastReported =
-  from(bucket: "example-bucket")
+lastReported = from(bucket: "example-bucket")
     |> range(start: -1m)
     |> filter(fn: (r) => r._measurement == "statuses")
     |> last()
@@ -82,10 +81,10 @@ lastReported =
     |> getRecord(idx: 0)
 
 slack.message(
-  url: "https://slack.com/api/chat.postMessage",
-  token: "mySuPerSecRetTokEn",
-  channel: "#system-status",
-  text: "The last reported status was \"${lastReported.status}\"."
-  color: "warning"
+    url: "https://slack.com/api/chat.postMessage",
+    token: "mySuPerSecRetTokEn",
+    channel: "#system-status",
+    text: "The last reported status was \"${lastReported.status}\".",
+    color: "warning",
 )
 ```
diff --git a/content/flux/v0.x/stdlib/sql/from.md b/content/flux/v0.x/stdlib/sql/from.md
index 4b80c0694..627db869f 100644
--- a/content/flux/v0.x/stdlib/sql/from.md
+++ b/content/flux/v0.x/stdlib/sql/from.md
@@ -22,9 +22,9 @@ The `sql.from()` function retrieves data from a SQL data source.
 import "sql"
 
 sql.from(
-  driverName: "postgres",
-  dataSourceName: "postgresql://user:password@localhost",
-  query:"SELECT * FROM TestTable"
+    driverName: "postgres",
+    dataSourceName: "postgresql://user:password@localhost",
+    query:"SELECT * FROM TestTable",
 )
 ```
 
diff --git a/content/flux/v0.x/stdlib/sql/to.md b/content/flux/v0.x/stdlib/sql/to.md
index 05df65cae..a6e0a09ed 100644
--- a/content/flux/v0.x/stdlib/sql/to.md
+++ b/content/flux/v0.x/stdlib/sql/to.md
@@ -20,10 +20,10 @@ The `sql.to()` function writes data to a SQL database.
 import "sql"
 
 sql.to(
-  driverName: "mysql",
-  dataSourceName: "username:password@tcp(localhost:3306)/dbname?param=value",
-  table: "example_table",
-  batchSize: 10000
+    driverName: "mysql",
+    dataSourceName: "username:password@tcp(localhost:3306)/dbname?param=value",
+    table: "example_table",
+    batchSize: 10000,
 )
 ```
 
diff --git a/content/flux/v0.x/stdlib/strings/compare.md b/content/flux/v0.x/stdlib/strings/compare.md
index dbea9a993..ae6732cc6 100644
--- a/content/flux/v0.x/stdlib/strings/compare.md
+++ b/content/flux/v0.x/stdlib/strings/compare.md
@@ -47,9 +47,5 @@ The string value to compare against.
 import "strings"
 
 data
-  |> map(fn: (r) => ({
-      r with
-      _value: strings.compare(v: r.tag1, t: r.tag2)
-    })
-  )  
+    |> map(fn: (r) => ({r with _value: strings.compare(v: r.tag1, t: r.tag2)}))
 ```
diff --git a/content/flux/v0.x/stdlib/strings/containsany.md b/content/flux/v0.x/stdlib/strings/containsany.md
index c1bddf18e..4ec418fe7 100644
--- a/content/flux/v0.x/stdlib/strings/containsany.md
+++ b/content/flux/v0.x/stdlib/strings/containsany.md
@@ -45,9 +45,5 @@ Characters to search for.
 import "strings"
 
 data
-  |> map(fn: (r) => ({
-      r with
-      _value: strings.containsAny(v: r.price, chars: "£$¢")
-    })
-  )
+    |> map(fn: (r) => ({r with _value: strings.containsAny(v: r.price, chars: "£$¢")}))
 ```
diff --git a/content/flux/v0.x/stdlib/strings/containsstr.md b/content/flux/v0.x/stdlib/strings/containsstr.md
index f706d8b74..172eb29dc 100644
--- a/content/flux/v0.x/stdlib/strings/containsstr.md
+++ b/content/flux/v0.x/stdlib/strings/containsstr.md
@@ -42,9 +42,5 @@ The substring value to search for.
 import "strings"
 
 data
-  |> map(fn: (r) => ({
-      r with
-      _value: strings.containsStr(v: r.author, substr: "John")
-    })
-  )
+    |> map(fn: (r) => ({r with _value: strings.containsStr(v: r.author, substr: "John")}))
 ```
diff --git a/content/flux/v0.x/stdlib/strings/countstr.md b/content/flux/v0.x/stdlib/strings/countstr.md
index 2eec1074f..2d811b119 100644
--- a/content/flux/v0.x/stdlib/strings/countstr.md
+++ b/content/flux/v0.x/stdlib/strings/countstr.md
@@ -54,9 +54,5 @@ strings.coutnStr(v: "ooooo", substr: "oo")
 import "strings"
 
 data
-  |> map(fn: (r) => ({
-      r with
-      _value: strings.countStr(v: r.message, substr: "uh")
-    })
-  )
+    |> map(fn: (r) => ({r with _value: strings.countStr(v: r.message, substr: "uh")}))
 ```
diff --git a/content/flux/v0.x/stdlib/strings/equalfold.md b/content/flux/v0.x/stdlib/strings/equalfold.md
index d1fd1a964..fb2d1a172 100644
--- a/content/flux/v0.x/stdlib/strings/equalfold.md
+++ b/content/flux/v0.x/stdlib/strings/equalfold.md
@@ -43,11 +43,10 @@ The string value to compare against.
 import "strings"
 
 data
-  |> map(fn: (r) => ({
-      r with
-      string1: r.string1,
-      string2: r.string2,
-      same: strings.equalFold(v: r.string1, t: r.string2)
-    })
-  )
+    |> map(fn: (r) => ({r with
+            string1: r.string1,
+            string2: r.string2,
+            same: strings.equalFold(v: r.string1, t: r.string2)
+        })
+    )
 ```
diff --git a/content/flux/v0.x/stdlib/strings/hasprefix.md b/content/flux/v0.x/stdlib/strings/hasprefix.md
index 114364ff4..ffb6ce18e 100644
--- a/content/flux/v0.x/stdlib/strings/hasprefix.md
+++ b/content/flux/v0.x/stdlib/strings/hasprefix.md
@@ -40,5 +40,5 @@ The prefix to search for.
 import "strings"
 
 data
-  |> filter(fn:(r) => strings.hasPrefix(v: r.metric, prefix: "int_" ))
+    |> filter(fn:(r) => strings.hasPrefix(v: r.metric, prefix: "int_" ))
 ```
diff --git a/content/flux/v0.x/stdlib/strings/hassuffix.md b/content/flux/v0.x/stdlib/strings/hassuffix.md
index 053c99705..413df06f0 100644
--- a/content/flux/v0.x/stdlib/strings/hassuffix.md
+++ b/content/flux/v0.x/stdlib/strings/hassuffix.md
@@ -41,5 +41,5 @@ The suffix to search for.
 import "strings"
 
 data
-  |> filter(fn:(r) => strings.hasSuffix(v: r.metric, suffix: "_count" ))
+    |> filter(fn:(r) => strings.hasSuffix(v: r.metric, suffix: "_count" ))
 ```
diff --git a/content/flux/v0.x/stdlib/strings/index-func.md b/content/flux/v0.x/stdlib/strings/index-func.md
index 5cdcf3d6e..6d9ab1271 100644
--- a/content/flux/v0.x/stdlib/strings/index-func.md
+++ b/content/flux/v0.x/stdlib/strings/index-func.md
@@ -47,9 +47,5 @@ The substring to search for.
 import "strings"
 
 data
-  |> map(fn: (r) => ({
-      r with
-      the_index: strings.index(v: r.pageTitle, substr: "the")
-    })
-  )
+    |> map(fn: (r) => ({r with the_index: strings.index(v: r.pageTitle, substr: "the")}))
 ```
diff --git a/content/flux/v0.x/stdlib/strings/indexany.md b/content/flux/v0.x/stdlib/strings/indexany.md
index d2c16cdce..6ef4ee5d7 100644
--- a/content/flux/v0.x/stdlib/strings/indexany.md
+++ b/content/flux/v0.x/stdlib/strings/indexany.md
@@ -46,9 +46,5 @@ Characters to search for.
 import "strings"
 
 data
-  |> map(fn: (r) => ({
-      r with
-      charIndex: strings.indexAny(v: r._field, chars: "_-")
-    })
-  )
+    |> map(fn: (r) => ({r with charIndex: strings.indexAny(v: r._field, chars: "_-")}))
 ```
diff --git a/content/flux/v0.x/stdlib/strings/isdigit.md b/content/flux/v0.x/stdlib/strings/isdigit.md
index 6c5a76c26..771cdfe9b 100644
--- a/content/flux/v0.x/stdlib/strings/isdigit.md
+++ b/content/flux/v0.x/stdlib/strings/isdigit.md
@@ -40,5 +40,5 @@ The single-character string to test.
 import "strings"
 
 data
-  |> filter(fn: (r) => strings.isDigit(v: r.serverRef))
+    |> filter(fn: (r) => strings.isDigit(v: r.serverRef))
 ```
diff --git a/content/flux/v0.x/stdlib/strings/isletter.md b/content/flux/v0.x/stdlib/strings/isletter.md
index e3b3c535e..54b217ef5 100644
--- a/content/flux/v0.x/stdlib/strings/isletter.md
+++ b/content/flux/v0.x/stdlib/strings/isletter.md
@@ -40,5 +40,5 @@ The single character string to test.
 import "strings"
 
 data
-  |> filter(fn: (r) => strings.isLetter(v: r.serverRef))
+    |> filter(fn: (r) => strings.isLetter(v: r.serverRef))
 ```
diff --git a/content/flux/v0.x/stdlib/strings/islower.md b/content/flux/v0.x/stdlib/strings/islower.md
index 6c5fc9673..138b72638 100644
--- a/content/flux/v0.x/stdlib/strings/islower.md
+++ b/content/flux/v0.x/stdlib/strings/islower.md
@@ -40,5 +40,5 @@ The single-character string value to test.
 import "strings"
 
 data
-  |> filter(fn: (r) => strings.isLower(v: r.host))
+    |> filter(fn: (r) => strings.isLower(v: r.host))
 ```
diff --git a/content/flux/v0.x/stdlib/strings/isupper.md b/content/flux/v0.x/stdlib/strings/isupper.md
index d34b7de67..315e3f632 100644
--- a/content/flux/v0.x/stdlib/strings/isupper.md
+++ b/content/flux/v0.x/stdlib/strings/isupper.md
@@ -40,5 +40,5 @@ The single-character string value to test.
 import "strings"
 
 data
-  |> filter(fn: (r) => strings.isUpper(v: r.host))
+    |> filter(fn: (r) => strings.isUpper(v: r.host))
 ```
diff --git a/content/flux/v0.x/stdlib/strings/lastindex.md b/content/flux/v0.x/stdlib/strings/lastindex.md
index a25fc7429..afcc33cf4 100644
--- a/content/flux/v0.x/stdlib/strings/lastindex.md
+++ b/content/flux/v0.x/stdlib/strings/lastindex.md
@@ -47,9 +47,5 @@ The substring to search for.
 import "strings"
 
 data
-  |> map(fn: (r) => ({
-      r with
-      the_index: strings.lastIndex(v: r.pageTitle, substr: "the")
-    })
-  )
+    |> map(fn: (r) => ({r with the_index: strings.lastIndex(v: r.pageTitle, substr: "the")}))
 ```
diff --git a/content/flux/v0.x/stdlib/strings/lastindexany.md b/content/flux/v0.x/stdlib/strings/lastindexany.md
index 4ba7d002f..6f14fc381 100644
--- a/content/flux/v0.x/stdlib/strings/lastindexany.md
+++ b/content/flux/v0.x/stdlib/strings/lastindexany.md
@@ -45,9 +45,5 @@ Characters to search for.
 import "strings"
 
 data
-  |> map(fn: (r) => ({
-      r with
-      charLastIndex: strings.lastIndexAny(v: r._field, chars: "_-")
-    })
-  )
+    |> map(fn: (r) => ({r with charLastIndex: strings.lastIndexAny(v: r._field, chars: "_-")}))
 ```
diff --git a/content/flux/v0.x/stdlib/strings/repeat.md b/content/flux/v0.x/stdlib/strings/repeat.md
index 1661acb7a..5b2a88498 100644
--- a/content/flux/v0.x/stdlib/strings/repeat.md
+++ b/content/flux/v0.x/stdlib/strings/repeat.md
@@ -40,10 +40,10 @@ The number of times to repeat `v`.
 import "strings"
 
 data
-  |> map(fn: (r) => ({
-      laugh: r.laugh
-      intensity: r.intensity
-      laughter: strings.repeat(v: r.laugh, i: r.intensity)
-    })
-  )
+    |> map(fn: (r) => ({
+            laugh: r.laugh,
+            intensity: r.intensity,
+            laughter: strings.repeat(v: r.laugh, i: r.intensity),
+        })
+    )
 ```
diff --git a/content/flux/v0.x/stdlib/strings/replace.md b/content/flux/v0.x/stdlib/strings/replace.md
index dfaf75811..ab39c25ca 100644
--- a/content/flux/v0.x/stdlib/strings/replace.md
+++ b/content/flux/v0.x/stdlib/strings/replace.md
@@ -51,9 +51,5 @@ The number of non-overlapping `t` matches to replace.
 import "strings"
 
 data
-  |> map(fn: (r) => ({
-      r with
-      content: strings.replace(v: r.content, t: "he", u: "her", i: 3)
-    })
-  )
+    |> map(fn: (r) => ({r with content: strings.replace(v: r.content, t: "he", u: "her", i: 3)}))
 ```
diff --git a/content/flux/v0.x/stdlib/strings/replaceall.md b/content/flux/v0.x/stdlib/strings/replaceall.md
index 5157d8232..e7f3a7d49 100644
--- a/content/flux/v0.x/stdlib/strings/replaceall.md
+++ b/content/flux/v0.x/stdlib/strings/replaceall.md
@@ -48,9 +48,5 @@ The replacement for all instances of `t`.
 import "strings"
 
 data
-  |> map(fn: (r) => ({
-      r with
-      content: strings.replaceAll(v: r.content, t: "he", u: "her")
-    })
-  )
+    |> map(fn: (r) => ({r with content: strings.replaceAll(v: r.content, t: "he", u: "her")}))
 ```
diff --git a/content/flux/v0.x/stdlib/strings/split.md b/content/flux/v0.x/stdlib/strings/split.md
index e8aaf289d..1e5e5c9e6 100644
--- a/content/flux/v0.x/stdlib/strings/split.md
+++ b/content/flux/v0.x/stdlib/strings/split.md
@@ -47,5 +47,5 @@ The string value that acts as the separator.
 import "strings"
 
 data
-  |> map (fn:(r) => strings.split(v: r.searchTags, t: ","))
+    |> map (fn:(r) => strings.split(v: r.searchTags, t: ","))
 ```
diff --git a/content/flux/v0.x/stdlib/strings/splitafter.md b/content/flux/v0.x/stdlib/strings/splitafter.md
index 2ce2c0735..0a44a65a1 100644
--- a/content/flux/v0.x/stdlib/strings/splitafter.md
+++ b/content/flux/v0.x/stdlib/strings/splitafter.md
@@ -48,5 +48,5 @@ The string value that acts as the separator.
 import "strings"
 
 data
-  |> map (fn:(r) => strings.splitAfter(v: r.searchTags, t: ","))
+    |> map (fn:(r) => strings.splitAfter(v: r.searchTags, t: ","))
 ```
diff --git a/content/flux/v0.x/stdlib/strings/splitaftern.md b/content/flux/v0.x/stdlib/strings/splitaftern.md
index 3ac5c22c7..2894ec4c5 100644
--- a/content/flux/v0.x/stdlib/strings/splitaftern.md
+++ b/content/flux/v0.x/stdlib/strings/splitaftern.md
@@ -53,5 +53,5 @@ The last substring is the unsplit remainder.
 import "strings"
 
 data
-  |> map (fn:(r) => strings.splitAfterN(v: r.searchTags, t: ","))
+    |> map (fn:(r) => strings.splitAfterN(v: r.searchTags, t: ","))
 ```
diff --git a/content/flux/v0.x/stdlib/strings/splitn.md b/content/flux/v0.x/stdlib/strings/splitn.md
index 81037529c..f9984c2b9 100644
--- a/content/flux/v0.x/stdlib/strings/splitn.md
+++ b/content/flux/v0.x/stdlib/strings/splitn.md
@@ -52,5 +52,5 @@ The last substring is the unsplit remainder.
 import "strings"
 
 data
-  |> map (fn:(r) => strings.splitN(v: r.searchTags, t: ","))
+    |> map (fn:(r) => strings.splitN(v: r.searchTags, t: ","))
 ```
diff --git a/content/flux/v0.x/stdlib/strings/strlen.md b/content/flux/v0.x/stdlib/strings/strlen.md
index 192b8bef9..1cbbe7684 100644
--- a/content/flux/v0.x/stdlib/strings/strlen.md
+++ b/content/flux/v0.x/stdlib/strings/strlen.md
@@ -48,9 +48,5 @@ data
 import "strings"
 
 data
-  |> map(fn: (r) => ({
-      r with
-      length: strings.strlen(v: r._value)
-    })
-  )
+    |> map(fn: (r) => ({r with length: strings.strlen(v: r._value)}))
 ```
diff --git a/content/flux/v0.x/stdlib/strings/substring.md b/content/flux/v0.x/stdlib/strings/substring.md
index 15f5e2f0d..5aeefa5cc 100644
--- a/content/flux/v0.x/stdlib/strings/substring.md
+++ b/content/flux/v0.x/stdlib/strings/substring.md
@@ -43,12 +43,6 @@ The ending exclusive index of the substring.
 
 ###### Store the first four characters of a string
 ```js
-import "strings"
-
 data
-  |> map(fn: (r) => ({
-      r with
-      abbr: strings.substring(v: r.name, start: 0, end: 4)
-    })
-  )
+    |> map(fn: (r) => ({r with abbr: strings.substring(v: r.name, start: 0, end: 4)}))
 ```
diff --git a/content/flux/v0.x/stdlib/strings/title.md b/content/flux/v0.x/stdlib/strings/title.md
index d17926410..22c13b3bf 100644
--- a/content/flux/v0.x/stdlib/strings/title.md
+++ b/content/flux/v0.x/stdlib/strings/title.md
@@ -41,5 +41,5 @@ The string value to convert.
 import "strings"
 
 data
-  |> map(fn: (r) => ({ r with pageTitle: strings.title(v: r.pageTitle) }))
+    |> map(fn: (r) => ({ r with pageTitle: strings.title(v: r.pageTitle) }))
 ```
diff --git a/content/flux/v0.x/stdlib/strings/tolower.md b/content/flux/v0.x/stdlib/strings/tolower.md
index 84f0fd904..a2f7df272 100644
--- a/content/flux/v0.x/stdlib/strings/tolower.md
+++ b/content/flux/v0.x/stdlib/strings/tolower.md
@@ -41,8 +41,5 @@ The string value to convert.
 import "strings"
 
 data
-  |> map(fn: (r) => ({
-      r with exclamation: strings.toLower(v: r.exclamation)
-    })
-  )
+    |> map(fn: (r) => ({r with exclamation: strings.toLower(v: r.exclamation)}))
 ```
diff --git a/content/flux/v0.x/stdlib/strings/totitle.md b/content/flux/v0.x/stdlib/strings/totitle.md
index 0f967dd2f..56b487056 100644
--- a/content/flux/v0.x/stdlib/strings/totitle.md
+++ b/content/flux/v0.x/stdlib/strings/totitle.md
@@ -41,7 +41,7 @@ The string value to convert.
 import "strings"
 
 data
-  |> map(fn: (r) => ({ r with pageTitle: strings.toTitle(v: r.pageTitle) }))
+    |> map(fn: (r) => ({ r with pageTitle: strings.toTitle(v: r.pageTitle) }))
 ```
 
 {{% note %}}
diff --git a/content/flux/v0.x/stdlib/strings/toupper.md b/content/flux/v0.x/stdlib/strings/toupper.md
index cb125ee46..9870aea3c 100644
--- a/content/flux/v0.x/stdlib/strings/toupper.md
+++ b/content/flux/v0.x/stdlib/strings/toupper.md
@@ -41,7 +41,7 @@ The string value to convert.
 import "strings"
 
 data
-  |> map(fn: (r) => ({ r with envVars: strings.toUpper(v: r.envVars) }))
+    |> map(fn: (r) => ({ r with envVars: strings.toUpper(v: r.envVars) }))
 ```
 
 {{% note %}}
diff --git a/content/flux/v0.x/stdlib/strings/trim.md b/content/flux/v0.x/stdlib/strings/trim.md
index 8fc589b04..20a3c0f56 100644
--- a/content/flux/v0.x/stdlib/strings/trim.md
+++ b/content/flux/v0.x/stdlib/strings/trim.md
@@ -50,9 +50,5 @@ Only characters that match the `cutset` string exactly are trimmed.
 import "strings"
 
 data
-  |> map(fn: (r) => ({
-      r with
-      variables: strings.trim(v: r.variables, cutset: ".")
-    })
-  )
+    |> map(fn: (r) => ({r with variables: strings.trim(v: r.variables, cutset: ".")}))
 ```
diff --git a/content/flux/v0.x/stdlib/strings/trimleft.md b/content/flux/v0.x/stdlib/strings/trimleft.md
index 7e5f6fb47..a020f217d 100644
--- a/content/flux/v0.x/stdlib/strings/trimleft.md
+++ b/content/flux/v0.x/stdlib/strings/trimleft.md
@@ -48,9 +48,5 @@ Only characters that match the `cutset` string exactly are removed.
 import "strings"
 
 data
-  |> map(fn: (r) => ({
-      r with
-      variables: strings.trimLeft(v: r.variables, cutset: ".")
-    })
-  )
+    |> map(fn: (r) => ({r with variables: strings.trimLeft(v: r.variables, cutset: ".")}))
 ```
diff --git a/content/flux/v0.x/stdlib/strings/trimprefix.md b/content/flux/v0.x/stdlib/strings/trimprefix.md
index 7815f86af..5048ebcc9 100644
--- a/content/flux/v0.x/stdlib/strings/trimprefix.md
+++ b/content/flux/v0.x/stdlib/strings/trimprefix.md
@@ -49,9 +49,5 @@ The prefix to remove.
 import "strings"
 
 data
-  |> map(fn: (r) => ({
-      r with
-      sensorID: strings.trimPrefix(v: r.sensorId, prefix: "s12_")
-    })
-  )
+    |> map(fn: (r) => ({r with sensorID: strings.trimPrefix(v: r.sensorId, prefix: "s12_")}))
 ```
diff --git a/content/flux/v0.x/stdlib/strings/trimright.md b/content/flux/v0.x/stdlib/strings/trimright.md
index 5c592b959..4d1779a39 100644
--- a/content/flux/v0.x/stdlib/strings/trimright.md
+++ b/content/flux/v0.x/stdlib/strings/trimright.md
@@ -49,9 +49,5 @@ Only characters that match the `cutset` string exactly are trimmed.
 import "strings"
 
 data
-  |> map(fn: (r) => ({
-      r with
-      variables: strings.trimRight(v: r.variables, cutset: ".")
-    })
-  )
+    |> map(fn: (r) => ({r with variables: strings.trimRight(v: r.variables, cutset: ".")}))
 ```
diff --git a/content/flux/v0.x/stdlib/strings/trimspace.md b/content/flux/v0.x/stdlib/strings/trimspace.md
index 7c5d2a6a3..c56a7462e 100644
--- a/content/flux/v0.x/stdlib/strings/trimspace.md
+++ b/content/flux/v0.x/stdlib/strings/trimspace.md
@@ -43,5 +43,5 @@ String to remove spaces from.
 import "strings"
 
 data
-  |> map(fn: (r) => ({ r with userInput: strings.trimSpace(v: r.userInput) }))
+    |> map(fn: (r) => ({ r with userInput: strings.trimSpace(v: r.userInput) }))
 ```
diff --git a/content/flux/v0.x/stdlib/strings/trimsuffix.md b/content/flux/v0.x/stdlib/strings/trimsuffix.md
index ba5eeb12e..287b3bc04 100644
--- a/content/flux/v0.x/stdlib/strings/trimsuffix.md
+++ b/content/flux/v0.x/stdlib/strings/trimsuffix.md
@@ -49,9 +49,5 @@ The suffix to remove.
 import "strings"
 
 data
-  |> map(fn: (r) => ({
-      r with
-      sensorID: strings.trimSuffix(v: r.sensorId, suffix: "_s12")
-    })
-  )
+    |> map(fn: (r) => ({r with sensorID: strings.trimSuffix(v: r.sensorId, suffix: "_s12")}))
 ```
diff --git a/content/flux/v0.x/stdlib/system/time.md b/content/flux/v0.x/stdlib/system/time.md
index b1940a952..bccfa99bd 100644
--- a/content/flux/v0.x/stdlib/system/time.md
+++ b/content/flux/v0.x/stdlib/system/time.md
@@ -32,7 +32,7 @@ system.time()
 import "system"
 
 data
-  |> set(key: "processed_at", value: string(v: system.time() ))
+    |> set(key: "processed_at", value: string(v: system.time() ))
 ```
 
 {{% note %}}
diff --git a/content/flux/v0.x/stdlib/testing/assertempty.md b/content/flux/v0.x/stdlib/testing/assertempty.md
index 5505c687d..300de2543 100644
--- a/content/flux/v0.x/stdlib/testing/assertempty.md
+++ b/content/flux/v0.x/stdlib/testing/assertempty.md
@@ -42,10 +42,11 @@ The `.testing.assertEmpty()` function checks to see if the diff is empty.
 import "testing"
 
 got = from(bucket: "example-bucket")
-  |> range(start: -15m)
+    |> range(start: -15m)
 want = from(bucket: "backup_example-bucket")
-  |> range(start: -15m)
+    |> range(start: -15m)
+
 got
-  |> testing.diff(want: want)
-  |> testing.assertEmpty()
+    |> testing.diff(want: want)
+    |> testing.assertEmpty()
 ```
diff --git a/content/flux/v0.x/stdlib/testing/assertequals.md b/content/flux/v0.x/stdlib/testing/assertequals.md
index 45c04ce4b..2693c5689 100644
--- a/content/flux/v0.x/stdlib/testing/assertequals.md
+++ b/content/flux/v0.x/stdlib/testing/assertequals.md
@@ -23,9 +23,9 @@ If unequal, the function returns an error.
 import "testing"
 
 testing.assertEquals(
-  name: "streamEquality",
-  got: got,
-  want: want
+    name: "streamEquality",
+    got: got,
+    want: want,
 )
 ```
 
@@ -50,10 +50,10 @@ The stream that contains the expected data to test against.
 import "testing"
 
 want = from(bucket: "backup-example-bucket")
-  |> range(start: -5m)
+    |> range(start: -5m)
 
 got = from(bucket: "example-bucket")
-  |> range(start: -5m)
+    |> range(start: -5m)
 
 testing.assertEquals(got: got, want: want)
 ```
@@ -63,9 +63,9 @@ testing.assertEquals(got: got, want: want)
 import "testing"
 
 want = from(bucket: "backup-example-bucket")
-  |> range(start: -5m)
+    |> range(start: -5m)
 
 from(bucket: "example-bucket")
-  |> range(start: -5m)
-  |> testing.assertEquals(want: want)
+    |> range(start: -5m)
+    |> testing.assertEquals(want: want)
 ```
diff --git a/content/flux/v0.x/stdlib/testing/benchmark.md b/content/flux/v0.x/stdlib/testing/benchmark.md
index 3236371c7..32a64259a 100644
--- a/content/flux/v0.x/stdlib/testing/benchmark.md
+++ b/content/flux/v0.x/stdlib/testing/benchmark.md
@@ -23,9 +23,7 @@ test output that occurs in [`testing.run()`](/flux/v0.x/stdlib/testing/run/).
 ```js
 import "testing"
 
-testing.benchmark(
-  case: exampleTestCase
-)
+testing.benchmark(case: exampleTestCase)
 ```
 
 ## Parameters
@@ -63,13 +61,11 @@ outData = "
 ,,0,2021-01-01T00:00:00Z,2021-01-03T01:00:00Z,m,t,4.8
 "
 
-t_sum = (table=<-) =>
-  (table
-    |> range(start:2021-01-01T00:00:00Z, stop:2021-01-03T01:00:00Z)
-    |> sum())
+t_sum = (table=<-) => table
+    |> range(start: 2021-01-01T00:00:00Z, stop: 2021-01-03T01:00:00Z)
+    |> sum()
 
-test _sum = () =>
-  ({input: testing.loadStorage(csv: inData), want: testing.loadMem(csv: outData), fn: t_sum})
+test _sum = () => ({input: testing.loadStorage(csv: inData), want: testing.loadMem(csv: outData), fn: t_sum})
 
 testing.benchmark(case: _sum)
 ```
diff --git a/content/flux/v0.x/stdlib/testing/diff.md b/content/flux/v0.x/stdlib/testing/diff.md
index f41a3ece2..001a2f821 100644
--- a/content/flux/v0.x/stdlib/testing/diff.md
+++ b/content/flux/v0.x/stdlib/testing/diff.md
@@ -20,11 +20,11 @@ The `testing.diff()` function produces a diff between two streams.
 import "testing"
 
 testing.diff(
-  got: stream2,
-  want: stream1,
-  epsilon: 0.000001,
-  nansEqual: false,
-  verbose: false  
+    got: stream2,
+    want: stream1,
+    epsilon: 0.000001,
+    nansEqual: false,
+    verbose: false,
 )
 ```
 
@@ -67,18 +67,20 @@ Default is `false`.
 import "testing"
 
 want = from(bucket: "backup-example-bucket")
-  |> range(start: -5m)
+    |> range(start: -5m)
 got = from(bucket: "example-bucket")
-  |> range(start: -5m)
+    |> range(start: -5m)
+
 testing.diff(got: got, want: want)
 ```
 
 ##### Inline diff
 ```js
-import "testing"
+iimport "testing"
 
 want = from(bucket: "backup-example-bucket") |> range(start: -5m)
+
 from(bucket: "example-bucket")
-  |> range(start: -5m)
-  |> testing.diff(want: want)
+    |> range(start: -5m)
+    |> testing.diff(want: want)
 ```
diff --git a/content/flux/v0.x/stdlib/testing/inspect.md b/content/flux/v0.x/stdlib/testing/inspect.md
index 57d014ccc..a609cfd29 100644
--- a/content/flux/v0.x/stdlib/testing/inspect.md
+++ b/content/flux/v0.x/stdlib/testing/inspect.md
@@ -19,9 +19,7 @@ The `testing.inspect()` function returns information about a test case.
 ```js
 import "testing"
 
-testing.inspect(
-  case: exampleTestCase
-)
+testing.inspect(case: exampleTestCase)
 ```
 
 ## Parameters
@@ -53,13 +51,11 @@ outData = "
 ,,0,2021-01-01T00:00:00Z,2021-01-03T01:00:00Z,m,t,4.8
 "
 
-t_sum = (table=<-) =>
-  (table
-    |> range(start:2021-01-01T00:00:00Z, stop:2021-01-03T01:00:00Z)
-    |> sum())
+t_sum = (table=<-) => table
+    |> range(start: 2021-01-01T00:00:00Z, stop: 2021-01-03T01:00:00Z)
+    |> sum()
 
-test _sum = () =>
-  ({input: testing.loadStorage(csv: inData), want: testing.loadMem(csv: outData), fn: t_sum})
+test _sum = () => ({input: testing.loadStorage(csv: inData), want: testing.loadMem(csv: outData), fn: t_sum})
 
 testing.inpsect(case: _sum)
 
diff --git a/content/flux/v0.x/stdlib/testing/load.md b/content/flux/v0.x/stdlib/testing/load.md
index b4d173c2c..8c04e32c1 100644
--- a/content/flux/v0.x/stdlib/testing/load.md
+++ b/content/flux/v0.x/stdlib/testing/load.md
@@ -38,20 +38,21 @@ to create two streams of tables to compare in the test.
 import "testing"
 import "array"
 
-got = array.from(rows: [
-  {_time: 2021-01-01T00:00:00Z, _measurement: "m", _field: "t", _value: 1.2},
-  {_time: 2021-01-01T01:00:00Z, _measurement: "m", _field: "t", _value: 0.8},
-  {_time: 2021-01-01T02:00:00Z, _measurement: "m", _field: "t", _value: 3.2}
-])
-
-want = array.from(rows: [
-  {_time: 2021-01-01T00:00:00Z, _measurement: "m", _field: "t", _value: 1.2},
-  {_time: 2021-01-01T01:00:00Z, _measurement: "m", _field: "t", _value: 0.8},
-  {_time: 2021-01-01T02:00:00Z, _measurement: "m", _field: "t", _value: 3.1}
-])
-
-testing.diff(
-  got: testing.load(tables: got),
-  want: testing.load(tables: want)
+got = array.from(
+    rows: [
+        {_time: 2021-01-01T00:00:00Z, _measurement: "m", _field: "t", _value: 1.2},
+        {_time: 2021-01-01T01:00:00Z, _measurement: "m", _field: "t", _value: 0.8},
+        {_time: 2021-01-01T02:00:00Z, _measurement: "m", _field: "t", _value: 3.2},
+    ]
 )
+
+want = array.from(
+    rows: [
+        {_time: 2021-01-01T00:00:00Z, _measurement: "m", _field: "t", _value: 1.2},
+        {_time: 2021-01-01T01:00:00Z, _measurement: "m", _field: "t", _value: 0.8},
+        {_time: 2021-01-01T02:00:00Z, _measurement: "m", _field: "t", _value: 3.1},
+    ]
+)
+
+testing.diff(got: testing.load(tables: got), want: testing.load(tables: want))
 ```
diff --git a/content/flux/v0.x/stdlib/testing/loadmem.md b/content/flux/v0.x/stdlib/testing/loadmem.md
index 33731740e..a41b7e5e7 100644
--- a/content/flux/v0.x/stdlib/testing/loadmem.md
+++ b/content/flux/v0.x/stdlib/testing/loadmem.md
@@ -21,9 +21,7 @@ test data from memory to emulate query results returned by Flux.
 ```js
 import "testing"
 
-testing.loadMem(
-  csv: csvData
-)
+testing.loadMem(csv: csvData)
 ```
 
 ## Parameters
diff --git a/content/flux/v0.x/stdlib/testing/loadstorage.md b/content/flux/v0.x/stdlib/testing/loadstorage.md
index 6f530ac47..918694beb 100644
--- a/content/flux/v0.x/stdlib/testing/loadstorage.md
+++ b/content/flux/v0.x/stdlib/testing/loadstorage.md
@@ -27,9 +27,7 @@ Test data requires the following columns:
 ```js
 import "testing"
 
-testing.loadStorage(
-  csv: csvData
-)
+testing.loadStorage(csv: csvData)
 ```
 
 ## Parameters
diff --git a/content/flux/v0.x/stdlib/testing/run.md b/content/flux/v0.x/stdlib/testing/run.md
index fc8f12e5b..c15e963ae 100644
--- a/content/flux/v0.x/stdlib/testing/run.md
+++ b/content/flux/v0.x/stdlib/testing/run.md
@@ -18,9 +18,7 @@ The `testing.run()` function executes a specified test case.
 ```js
 import "testing"
 
-testing.run(
-  case: exampleTestCase
-)
+testing.run(case: exampleTestCase)
 ```
 
 ## Parameters
@@ -52,13 +50,11 @@ outData = "
 ,,0,2021-01-01T00:00:00Z,2021-01-03T01:00:00Z,m,t,4.8
 "
 
-t_sum = (table=<-) =>
-  (table
-    |> range(start:2021-01-01T00:00:00Z, stop:2021-01-03T01:00:00Z)
-    |> sum())
+t_sum = (table=<-) => table
+    |> range(start: 2021-01-01T00:00:00Z, stop: 2021-01-03T01:00:00Z)
+    |> sum()
 
-test _sum = () =>
-  ({input: testing.loadStorage(csv: inData), want: testing.loadMem(csv: outData), fn: t_sum})
+test _sum = () => ({input: testing.loadStorage(csv: inData), want: testing.loadMem(csv: outData), fn: t_sum})
 
 testing.run(case: _sum)
 ```
diff --git a/content/flux/v0.x/stdlib/timezone/fixed.md b/content/flux/v0.x/stdlib/timezone/fixed.md
index 5e6a68aa2..3a9d65b88 100644
--- a/content/flux/v0.x/stdlib/timezone/fixed.md
+++ b/content/flux/v0.x/stdlib/timezone/fixed.md
@@ -38,11 +38,13 @@ import "timezone"
 
 option location = timezone.fixed(offset: -8h)
 
-data = array.from(rows: [
+data = array.from(
+    rows: [
         {_time: 2021-01-01T00:06:00Z, _value: 1},
         {_time: 2021-01-02T00:06:00Z, _value: 2},
-        {_time: 2021-01-03T00:06:00Z, _value: 3}
-    ])
+        {_time: 2021-01-03T00:06:00Z, _value: 3},
+    ],
+)
     |> range(start: 2021-01-01T00:00:00Z, stop: 2021-01-04T00:00:00Z)
 
 data
diff --git a/content/flux/v0.x/stdlib/timezone/location.md b/content/flux/v0.x/stdlib/timezone/location.md
index da7086192..3db41a721 100644
--- a/content/flux/v0.x/stdlib/timezone/location.md
+++ b/content/flux/v0.x/stdlib/timezone/location.md
@@ -14,6 +14,10 @@ flux/v0.x/tags: [timezone, location, data/time]
 Setting the timezone by location accounts for location-based time shifts in the
 clock such as daylight savings time or summertime.
 
+Flux uses the timezone database provided by the underlying operating system (OS).
+Timezones and timezone names depend on your OS.
+For a general list of timezone names, see [tz database time zones](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones).
+
 ```js
 import "timezone"
 
diff --git a/content/flux/v0.x/stdlib/types/_index.md b/content/flux/v0.x/stdlib/types/_index.md
index cef9f3902..7132a1c37 100644
--- a/content/flux/v0.x/stdlib/types/_index.md
+++ b/content/flux/v0.x/stdlib/types/_index.md
@@ -12,7 +12,7 @@ menu:
 weight: 11
 flux/v0.x/tags: [types, functions, package]
 cascade:
-  introduced: 0.140.0
+  introduced: 0.141.0
 ---
 
 The Flux `types` package provides functions for working with
diff --git a/content/flux/v0.x/stdlib/types/istype.md b/content/flux/v0.x/stdlib/types/istype.md
index adbf7ccde..a5d8345fe 100644
--- a/content/flux/v0.x/stdlib/types/istype.md
+++ b/content/flux/v0.x/stdlib/types/istype.md
@@ -90,3 +90,85 @@ data
 {{< /flex >}}
 {{% /expand %}}
 {{< /expand-wrapper >}}
+
+
+### Aggregate or select data based on type
+```javascript
+data = () => from(bucket: "example-bucket")
+    |> range(start: -1m)
+
+nonNumericData = data()
+    |> filter(fn: (r) => types.isType(v: r._value, type: "string") or types.isType(v: r._value, type: "bool"))
+    |> aggregateWindow(every: 30s, fn: last)
+
+numericData = data()
+    |> filter(fn: (r) => types.isType(v: r._value, type: "int") or types.isType(v: r._value, type: "float"))
+    |> aggregateWindow(every: 30s, fn: mean)
+
+> union(tables: [nonNumericData, numericData])
+```
+
+{{< expand-wrapper >}}
+{{% expand "View example input and output" %}}
+
+#### Input data
+| _start               | _stop                | _time                | type  | _value |
+| :------------------- | :------------------- | :------------------- | :---- | -----: |
+| 2021-01-01T00:00:00Z | 2021-01-01T00:01:00Z | 2021-01-01T00:00:00Z | float |  -2.18 |
+| 2021-01-01T00:00:00Z | 2021-01-01T00:01:00Z | 2021-01-01T00:00:10Z | float |  10.92 |
+| 2021-01-01T00:00:00Z | 2021-01-01T00:01:00Z | 2021-01-01T00:00:20Z | float |   7.35 |
+| 2021-01-01T00:00:00Z | 2021-01-01T00:01:00Z | 2021-01-01T00:00:30Z | float |  17.53 |
+| 2021-01-01T00:00:00Z | 2021-01-01T00:01:00Z | 2021-01-01T00:00:40Z | float |  15.23 |
+| 2021-01-01T00:00:00Z | 2021-01-01T00:01:00Z | 2021-01-01T00:00:50Z | float |   4.43 |
+
+| _start               | _stop                | _time                | type | _value |
+| :------------------- | :------------------- | :------------------- | :--- | -----: |
+| 2021-01-01T00:00:00Z | 2021-01-01T00:01:00Z | 2021-01-01T00:00:00Z | bool |   true |
+| 2021-01-01T00:00:00Z | 2021-01-01T00:01:00Z | 2021-01-01T00:00:10Z | bool |   true |
+| 2021-01-01T00:00:00Z | 2021-01-01T00:01:00Z | 2021-01-01T00:00:20Z | bool |  false |
+| 2021-01-01T00:00:00Z | 2021-01-01T00:01:00Z | 2021-01-01T00:00:30Z | bool |   true |
+| 2021-01-01T00:00:00Z | 2021-01-01T00:01:00Z | 2021-01-01T00:00:40Z | bool |  false |
+| 2021-01-01T00:00:00Z | 2021-01-01T00:01:00Z | 2021-01-01T00:00:50Z | bool |  false |
+
+| _start               | _stop                | _time                | type   |      _value |
+| :------------------- | :------------------- | :------------------- | :----- | ----------: |
+| 2021-01-01T00:00:00Z | 2021-01-01T00:01:00Z | 2021-01-01T00:00:00Z | string | smpl_g9qczs |
+| 2021-01-01T00:00:00Z | 2021-01-01T00:01:00Z | 2021-01-01T00:00:10Z | string | smpl_0mgv9n |
+| 2021-01-01T00:00:00Z | 2021-01-01T00:01:00Z | 2021-01-01T00:00:20Z | string | smpl_phw664 |
+| 2021-01-01T00:00:00Z | 2021-01-01T00:01:00Z | 2021-01-01T00:00:30Z | string | smpl_guvzy4 |
+| 2021-01-01T00:00:00Z | 2021-01-01T00:01:00Z | 2021-01-01T00:00:40Z | string | smpl_5v3cce |
+| 2021-01-01T00:00:00Z | 2021-01-01T00:01:00Z | 2021-01-01T00:00:50Z | string | smpl_s9fmgy |
+
+| _start               | _stop                | _time                | type | _value |
+| :------------------- | :------------------- | :------------------- | :--- | -----: |
+| 2021-01-01T00:00:00Z | 2021-01-01T00:01:00Z | 2021-01-01T00:00:00Z | int  |     -2 |
+| 2021-01-01T00:00:00Z | 2021-01-01T00:01:00Z | 2021-01-01T00:00:10Z | int  |     10 |
+| 2021-01-01T00:00:00Z | 2021-01-01T00:01:00Z | 2021-01-01T00:00:20Z | int  |      7 |
+| 2021-01-01T00:00:00Z | 2021-01-01T00:01:00Z | 2021-01-01T00:00:30Z | int  |     17 |
+| 2021-01-01T00:00:00Z | 2021-01-01T00:01:00Z | 2021-01-01T00:00:40Z | int  |     15 |
+| 2021-01-01T00:00:00Z | 2021-01-01T00:01:00Z | 2021-01-01T00:00:50Z | int  |      4 |
+
+#### Output data
+
+| _start               | _stop                | _time                | type | _value |
+| :------------------- | :------------------- | :------------------- | :--- | -----: |
+| 2021-01-01T00:00:00Z | 2021-01-01T00:01:00Z | 2021-01-01T00:00:30Z | bool |  false |
+| 2021-01-01T00:00:00Z | 2021-01-01T00:01:00Z | 2021-01-01T00:01:00Z | bool |  false |
+
+| _start               | _stop                | _time                | type  |             _value |
+| :------------------- | :------------------- | :------------------- | :---- | -----------------: |
+| 2021-01-01T00:00:00Z | 2021-01-01T00:01:00Z | 2021-01-01T00:00:30Z | float |  5.363333333333333 |
+| 2021-01-01T00:00:00Z | 2021-01-01T00:01:00Z | 2021-01-01T00:01:00Z | float | 12.396666666666668 |
+
+| _start               | _stop                | _time                | type | _value |
+| :------------------- | :------------------- | :------------------- | :--- | -----: |
+| 2021-01-01T00:00:00Z | 2021-01-01T00:01:00Z | 2021-01-01T00:00:30Z | int  |      5 |
+| 2021-01-01T00:00:00Z | 2021-01-01T00:01:00Z | 2021-01-01T00:01:00Z | int  |     12 |
+
+| _start               | _stop                | _time                | type   |      _value |
+| :------------------- | :------------------- | :------------------- | :----- | ----------: |
+| 2021-01-01T00:00:00Z | 2021-01-01T00:01:00Z | 2021-01-01T00:00:30Z | string | smpl_phw664 |
+| 2021-01-01T00:00:00Z | 2021-01-01T00:01:00Z | 2021-01-01T00:01:00Z | string | smpl_s9fmgy |
+
+{{% /expand %}}
+{{< /expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/universe/aggregatewindow.md b/content/flux/v0.x/stdlib/universe/aggregatewindow.md
index c45ebb582..a7701b46f 100644
--- a/content/flux/v0.x/stdlib/universe/aggregatewindow.md
+++ b/content/flux/v0.x/stdlib/universe/aggregatewindow.md
@@ -24,14 +24,14 @@ introduced: 0.7.0
 
 ```js
 aggregateWindow(
-  every: 1m,
-  period: 1m,
-  fn: mean,
-  column: "_value",
-  timeSrc: "_stop",
-  timeDst: "_time",
-  location: "UTC",
-  createEmpty: true
+    every: 1m,
+    period: 1m,
+    fn: mean,
+    column: "_value",
+    timeSrc: "_stop",
+    timeDst: "_time",
+    location: "UTC",
+    createEmpty: true,
 )
 ```
 
@@ -138,13 +138,10 @@ to aggregate time-based windows:
 import "sampledata"
 
 data = sampledata.float()
-  |> range(start: sampledata.start, stop: sampledata.stop)
+    |> range(start: sampledata.start, stop: sampledata.stop)
 
 data
-  |> aggregateWindow(
-    every: 20s,
-    fn: mean
-  )
+    |> aggregateWindow(every: 20s, fn: mean)
 ```
 
 {{< expand-wrapper >}}
@@ -177,14 +174,14 @@ tables into the aggregate or selector function with all required parameters defi
 import "sampledata"
 
 data = sampledata.float()
-  |> range(start: sampledata.start, stop: sampledata.stop)
+    |> range(start: sampledata.start, stop: sampledata.stop)
 
 data
-  |> aggregateWindow(
-    column: "_value",
-    every: 20s,
-    fn: (column, tables=<-) => tables |> quantile(q: 0.99, column:column)
-  )
+    |> aggregateWindow(
+        column: "_value",
+        every: 20s,
+        fn: (column, tables=<-) => tables |> quantile(q: 0.99, column: column),
+    )
 ```
 
 {{< expand-wrapper >}}
@@ -212,10 +209,10 @@ data
 import "sampledata"
 
 data = sampledata.float()
-  |> range(start: sampledata.start, stop: sampledata.stop)
+    |> range(start: sampledata.start, stop: sampledata.stop)
 
 data
-  |> aggregateWindow(every: 1mo, fn: mean)
+    |> aggregateWindow(every: 1mo, fn: mean)
 ```
 
 {{% expand "View input and output" %}}
diff --git a/content/flux/v0.x/stdlib/universe/bool.md b/content/flux/v0.x/stdlib/universe/bool.md
index 7d4729b74..0d527807f 100644
--- a/content/flux/v0.x/stdlib/universe/bool.md
+++ b/content/flux/v0.x/stdlib/universe/bool.md
@@ -33,7 +33,7 @@ The value to convert.
 ## Examples
 ```js
 from(bucket: "sensor-data")
-  |> range(start: -1m)
-  |> filter(fn:(r) => r._measurement == "system" )
-  |> map(fn:(r) => ({ r with responsive: bool(v: r.responsive) }))
+    |> range(start: -1m)
+    |> filter(fn: (r) => r._measurement == "system")
+    |> map(fn: (r) => ({r with responsive: bool(v: r.responsive)}))
 ```
diff --git a/content/flux/v0.x/stdlib/universe/bottom.md b/content/flux/v0.x/stdlib/universe/bottom.md
index cb9b46fae..26acf8c31 100644
--- a/content/flux/v0.x/stdlib/universe/bottom.md
+++ b/content/flux/v0.x/stdlib/universe/bottom.md
@@ -51,7 +51,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> bottom(n:2)
+    |> bottom(n:2)
 ```
 
 {{< expand-wrapper >}}
@@ -80,15 +80,3 @@ sampledata.int()
 {{< /flex >}}
 {{% /expand %}}
 {{< /expand-wrapper >}}
-
-## Function definition
-```js
-// _sortLimit is a helper function, which sorts and limits a table.
-_sortLimit = (n, desc, columns=["_value"], tables=<-) =>
-  tables
-    |> sort(columns:columns, desc:desc)
-    |> limit(n:n)
-
-bottom = (n, columns=["_value"], tables=<-) =>
-  _sortLimit(n:n, columns:columns, desc:false)
-```
diff --git a/content/flux/v0.x/stdlib/universe/bytes.md b/content/flux/v0.x/stdlib/universe/bytes.md
index a68983664..dfac974f1 100644
--- a/content/flux/v0.x/stdlib/universe/bytes.md
+++ b/content/flux/v0.x/stdlib/universe/bytes.md
@@ -32,6 +32,6 @@ The value to convert.
 ## Examples
 ```js
 from(bucket: "sensor-data")
-  |> range(start: -1m)
-  |> map(fn:(r) => ({ r with _value: bytes(v: r._value) }))
+    |> range(start: -1m)
+    |> map(fn: (r) => ({r with _value: bytes(v: r._value)}))
 ```
diff --git a/content/flux/v0.x/stdlib/universe/chandemomentumoscillator.md b/content/flux/v0.x/stdlib/universe/chandemomentumoscillator.md
index 30863411e..2eeb31d5f 100644
--- a/content/flux/v0.x/stdlib/universe/chandemomentumoscillator.md
+++ b/content/flux/v0.x/stdlib/universe/chandemomentumoscillator.md
@@ -24,8 +24,8 @@ developed by Tushar Chande.
 
 ```js
 chandeMomentumOscillator(
-  n: 10,
-  columns: ["_value"]
+    n: 10,
+    columns: ["_value"],
 )
 ```
 
@@ -61,7 +61,7 @@ with `x - n` rows.
 import "sampledata"
 
 sampledata.int()
-  |> chandeMomentumOscillator(n: 2)
+    |> chandeMomentumOscillator(n: 2)
 ```
 
 {{% expand "View input and output" %}}
diff --git a/content/flux/v0.x/stdlib/universe/columns.md b/content/flux/v0.x/stdlib/universe/columns.md
index 840206c77..d3ad962dc 100644
--- a/content/flux/v0.x/stdlib/universe/columns.md
+++ b/content/flux/v0.x/stdlib/universe/columns.md
@@ -51,7 +51,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.string()
-  |> columns(column: "labels")
+    |> columns(column: "labels")
 ```
 
 {{% expand "View input and output" %}}
diff --git a/content/flux/v0.x/stdlib/universe/contains.md b/content/flux/v0.x/stdlib/universe/contains.md
index e08bab6b4..6c6494736 100644
--- a/content/flux/v0.x/stdlib/universe/contains.md
+++ b/content/flux/v0.x/stdlib/universe/contains.md
@@ -22,8 +22,8 @@ If the value is not a member of the set, the functions returns `false`.
 
 ```js
 contains(
-  value: 1,
-  set: [1,2,3]
+    value: 1,
+    set: [1,2,3],
 )
 ```
 
@@ -44,8 +44,8 @@ import "influxdata/influxdb/sample"
 fields = ["temperature", "humidity"]
 
 sample.data(set: "airSensor")
-  |> range(start: -30m)
-  |> filter(fn: (r) => contains(value: r._field, set: fields))
+    |> range(start: -30m)
+    |> filter(fn: (r) => contains(value: r._field, set: fields))
 ```
 
 {{% expand "View example input and output" %}}
diff --git a/content/flux/v0.x/stdlib/universe/count.md b/content/flux/v0.x/stdlib/universe/count.md
index bc9ab0106..27fa60761 100644
--- a/content/flux/v0.x/stdlib/universe/count.md
+++ b/content/flux/v0.x/stdlib/universe/count.md
@@ -33,10 +33,10 @@ count(column: "_value")
 `count()` returns `0` for empty tables.
 To keep empty tables in your data, set the following parameters for the following functions:
 
-| Function                                                                                              | Parameter           |
-|:--------                                                                                              |:---------           |
-| [filter()](/flux/v0.x/stdlib/universe/filter/)                              | `onEmpty: "keep"`   |
-| [window()](/flux/v0.x/stdlib/universe/window/)                              | `createEmpty: true` |
+| Function                                                         | Parameter           |
+| :--------------------------------------------------------------- | :------------------ |
+| [filter()](/flux/v0.x/stdlib/universe/filter/)                   | `onEmpty: "keep"`   |
+| [window()](/flux/v0.x/stdlib/universe/window/)                   | `createEmpty: true` |
 | [aggregateWindow()](/flux/v0.x/stdlib/universe/aggregatewindow/) | `createEmpty: true` |
 {{% /note %}}
 
@@ -58,7 +58,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.string()
-  |> count()
+    |> count()
 ```
 
 {{% expand "View input and output" %}}
diff --git a/content/flux/v0.x/stdlib/universe/cov.md b/content/flux/v0.x/stdlib/universe/cov.md
index e2b78e471..a483d3f33 100644
--- a/content/flux/v0.x/stdlib/universe/cov.md
+++ b/content/flux/v0.x/stdlib/universe/cov.md
@@ -52,18 +52,20 @@ to generate sample data and show how `cov()` transforms data.
 import "generate"
 
 stream1 = generate.from(
-  count: 5,
-  fn: (n) => n * n,
-  start: 2021-01-01T00:00:00Z,
-  stop: 2021-01-01T00:01:00Z
-) |> toFloat()
+    count: 5,
+    fn: (n) => n * n,
+    start: 2021-01-01T00:00:00Z,
+    stop: 2021-01-01T00:01:00Z,
+)
+    |> toFloat()
 
 stream2 = generate.from(
-  count: 5,
-  fn: (n) => n * n * n / 2,
-  start: 2021-01-01T00:00:00Z,
-  stop: 2021-01-01T00:01:00Z
-) |> toFloat()
+    count: 5,
+    fn: (n) => n * n * n / 2,
+    start: 2021-01-01T00:00:00Z,
+    stop: 2021-01-01T00:01:00Z,
+)
+    |> toFloat()
 
 cov(x: stream1, y: stream2, on: ["_time"])
 ```
@@ -102,10 +104,3 @@ cov(x: stream1, y: stream2, on: ["_time"])
 
 {{% /expand %}}
 {{< /expand-wrapper >}}
-
-## Function definition
-```js
-cov = (x,y,on,pearsonr=false) =>
-  join( tables:{x:x, y:y}, on:on )
-    |> covariance(pearsonr:pearsonr, columns:["_value_x","_value_y"])
-```
diff --git a/content/flux/v0.x/stdlib/universe/covariance.md b/content/flux/v0.x/stdlib/universe/covariance.md
index a4c079dea..5c17f6b06 100644
--- a/content/flux/v0.x/stdlib/universe/covariance.md
+++ b/content/flux/v0.x/stdlib/universe/covariance.md
@@ -50,12 +50,12 @@ to generate sample data and show how `covariance()` transforms data.
 ```js
 import "generate"
 
-data = generate.from(count: 5, fn: (n) => n * n, start: 2021-01-01T00:00:00Z,stop: 2021-01-01T00:01:00Z  ) 
-  |> toFloat()
-  |> map(fn: (r) => ({_time: r._time, x: r._value, y: r._value * r._value / 2.0}))
- 
+data = generate.from(count: 5, fn: (n) => n * n, start: 2021-01-01T00:00:00Z, stop: 2021-01-01T00:01:00Z)
+    |> toFloat()
+    |> map(fn: (r) => ({_time: r._time, x: r._value, y: r._value * r._value / 2.0}))
+
 data
-  |> covariance(columns: ["x", "y"])
+    |> covariance(columns: ["x", "y"])
 ```
 
 {{% expand "View input and output" %}}
diff --git a/content/flux/v0.x/stdlib/universe/cumulativesum.md b/content/flux/v0.x/stdlib/universe/cumulativesum.md
index 7c255f09e..2fb92cc8c 100644
--- a/content/flux/v0.x/stdlib/universe/cumulativesum.md
+++ b/content/flux/v0.x/stdlib/universe/cumulativesum.md
@@ -44,7 +44,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.string()
-  |> cumulativeSum()
+    |> cumulativeSum()
 ```
 {{% expand "View input and output" %}}
 {{< flex >}}
diff --git a/content/flux/v0.x/stdlib/universe/derivative.md b/content/flux/v0.x/stdlib/universe/derivative.md
index 090e7ca29..22b248fce 100644
--- a/content/flux/v0.x/stdlib/universe/derivative.md
+++ b/content/flux/v0.x/stdlib/universe/derivative.md
@@ -26,10 +26,10 @@ _**Output data type:** Float_
 
 ```js
 derivative(
-  unit: 1s,
-  nonNegative: true,
-  columns: ["_value"],
-  timeColumn: "_time"
+    unit: 1s,
+    nonNegative: false,
+    columns: ["_value"],
+    timeColumn: "_time",
 )
 ```
 
@@ -40,7 +40,7 @@ The time duration used when creating the derivative.
 Default is `1s`.
 
 ### nonNegative {data-type="bool"}
-Indicates if the derivative is allowed to be negative. Default is `true`.
+Indicates if the derivative is allowed to be negative. Default is `false`.
 When `true`, if a value is less than the previous value, it is assumed the
 previous value should have been a zero.
 
@@ -71,7 +71,7 @@ For each input table with `n` rows, `derivative()` outputs a table with `n - 1`
 import "sampledata"
 
 sampledata.int()
-  |> derivative()
+    |> derivative()
 ```
 
 {{< expand-wrapper >}}
@@ -112,7 +112,7 @@ sampledata.int()
 import "sampledata"
 
 sampledata.int()
-  |> derivative(nonNegative: true)
+    |> derivative(nonNegative: true)
 ```
 
 {{< expand-wrapper >}}
@@ -153,7 +153,7 @@ sampledata.int()
 import "sampledata"
 
 sampledata.int(includeNull: true)
-  |> derivative()
+    |> derivative()
 ```
 {{% expand "View input and output" %}}
 {{< flex >}}
diff --git a/content/flux/v0.x/stdlib/universe/display.md b/content/flux/v0.x/stdlib/universe/display.md
new file mode 100644
index 000000000..efd71e565
--- /dev/null
+++ b/content/flux/v0.x/stdlib/universe/display.md
@@ -0,0 +1,128 @@
+---
+title: display() function
+description: >
+  `display()` returns the Flux literal representation of any value as a string.
+menu:
+  flux_0_x_ref:
+    name: display
+    parent: universe
+weight: 102
+introduced: 0.154.0
+---
+
+`display()` returns the Flux literal representation of any value as a string.
+
+```js
+display(v: "example value")
+```
+
+[Basic types](/flux/v0.x/data-types/basic/) are converted directly to a string.
+[Bytes types](/flux/v0.x/data-types/basic/bytes/) are represented as a string of
+lowercase hexadecimal characters prefixed with `0x`.
+[Composite types](/flux/v0.x/data-types/composite/) (arrays, dictionaries, and records)
+are represented in a syntax similar to their equivalent Flux literal representation.
+
+Note the following about the resulting string representation:
+
+- It cannot always be parsed back into the original value.
+- It may span multiple lines.
+- It may change between Flux versions.
+
+{{% note %}}
+`display()` differs from [`string()`](/flux/v0.x/stdlib/universe/string/) in
+that `display()` recursively converts values inside composite types to strings.
+`string()` does not operate on composite types.
+{{% /note %}}
+
+## Parameters
+
+### v
+Value to convert for display.
+
+## Examples
+
+- [Display composite values as part of a table](#display-composite-values-as-part-of-a-table)
+- [Display a record](#display-a-record)
+- [Display an array](#display-an-array)
+- [Display a dictionary](#display-a-dictionary)
+- [Display bytes](#display-bytes)
+- [Display a composite value](#display-a-composite-value)
+
+### Display composite values as part of a table
+Use [`array.from()`](/flux/v0.x/stdlib/array/from/) and `display()` to quickly
+observe any value.
+
+```js
+import "array"
+
+array.from(
+    rows: [
+        {
+            dict: display(v: ["a":1, "b": 2]),
+            record: display(v:{x: 1, y: 2}),
+            array: display(v: [5,6,7])
+        }
+    ]
+)
+```
+
+#### Output data
+| dict         | record       | array     |
+| :----------- | :----------- | :-------- |
+| [a: 1, b: 2] | {x: 1, y: 2} | [5, 6, 7] |
+
+### Display a record
+```js
+x = {a: 1, b: 2, c: 3}
+
+display(v: x)
+
+// Returns {a: 1, b: 2, c: 3}
+```
+
+### Display an array
+```js
+x = [1, 2, 3]
+
+display(v: x)
+
+// Returns [1, 2, 3]
+```
+
+### Display a dictionary
+```js
+x = ["a": 1, "b": 2, "c": 3]
+
+display(v: x)
+
+// Returns [a: 1, b: 2, c: 3]
+```
+
+### Display bytes
+```js
+x = bytes(v:"abc")
+
+display(v: x)
+
+// Returns 0x616263
+```
+
+### Display a composite value
+```js
+x = {
+    bytes: bytes(v: "abc"),
+    string: "str",
+    array: [1,2,3],
+    dict: ["a": 1, "b": 2, "c": 3],
+}
+
+display(v: x)
+
+// Returns
+// {
+//    array: [1, 2, 3],
+//    bytes: 0x616263,
+//    dict: [a: 1, b: 2, c: 3],
+//    string: str
+// }
+```
\ No newline at end of file
diff --git a/content/flux/v0.x/stdlib/universe/distinct.md b/content/flux/v0.x/stdlib/universe/distinct.md
index 9e618190f..e424d0386 100644
--- a/content/flux/v0.x/stdlib/universe/distinct.md
+++ b/content/flux/v0.x/stdlib/universe/distinct.md
@@ -51,7 +51,7 @@ import "sampledata"
 data = sampledata.int()
 
 data
-  |> distinct()
+    |> distinct()
 ```
 
 {{< expand-wrapper >}}
@@ -93,7 +93,7 @@ data
 import "sampledata"
 
 sampledata.int()
-  |> distinct(column: "tag")
+    |> distinct(column: "tag")
 ```
 
 {{< expand-wrapper >}}
@@ -126,7 +126,7 @@ sampledata.int()
 import "sampledata"
 
 sampledata.int(includeNull: true)
-  |> distinct()
+    |> distinct()
 ```
 
 {{% expand "View input and output" %}}
diff --git a/content/flux/v0.x/stdlib/universe/doubleema.md b/content/flux/v0.x/stdlib/universe/doubleema.md
index 7eb4829e7..a86db8caa 100644
--- a/content/flux/v0.x/stdlib/universe/doubleema.md
+++ b/content/flux/v0.x/stdlib/universe/doubleema.md
@@ -57,7 +57,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> doubleEMA(n: 3)
+    |> doubleEMA(n: 3)
 ```
 
 {{< expand-wrapper >}}
@@ -86,14 +86,3 @@ sampledata.int()
 {{< /flex >}}
 {{% /expand %}}
 {{< /expand-wrapper >}}
-
-## Function definition
-```js
-doubleEMA = (n, tables=<-) =>
-  tables
-    |> exponentialMovingAverage(n:n)
-    |> duplicate(column:"_value", as:"ema")
-    |> exponentialMovingAverage(n:n)
-    |> map(fn: (r) => ({r with _value: 2.0 * r.ema - r._value}))
-    |> drop(columns: ["ema"])
-```
diff --git a/content/flux/v0.x/stdlib/universe/drop.md b/content/flux/v0.x/stdlib/universe/drop.md
index 411f1a0a3..500bb2e69 100644
--- a/content/flux/v0.x/stdlib/universe/drop.md
+++ b/content/flux/v0.x/stdlib/universe/drop.md
@@ -62,7 +62,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> drop(columns: ["_time", "tid"])
+    |> drop(columns: ["_time", "tid"])
 ```
 
 {{< expand-wrapper >}}
@@ -103,7 +103,7 @@ sampledata.int()
 import "sampledata"
 
 sampledata.int()
-  |> drop(fn: (column) => column =~ /^t/)
+    |> drop(fn: (column) => column =~ /^t/)
 ```
 
 {{% expand "View input and output" %}}
diff --git a/content/flux/v0.x/stdlib/universe/duplicate.md b/content/flux/v0.x/stdlib/universe/duplicate.md
index bf3a4a58f..98b80b0de 100644
--- a/content/flux/v0.x/stdlib/universe/duplicate.md
+++ b/content/flux/v0.x/stdlib/universe/duplicate.md
@@ -48,7 +48,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-	|> duplicate(column: "tag", as: "tag_dup")
+    |> duplicate(column: "tag", as: "tag_dup")
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/universe/duration.md b/content/flux/v0.x/stdlib/universe/duration.md
index 06badc300..c5928753e 100644
--- a/content/flux/v0.x/stdlib/universe/duration.md
+++ b/content/flux/v0.x/stdlib/universe/duration.md
@@ -67,14 +67,14 @@ This example converts an integer to a duration and stores the value as a string.
 import "generate"
 
 data = generate.from(
-  count: 5,
-  fn: (n) => (n + 1) * 3600000000000,
-  start: 2021-01-01T00:00:00Z,
-  stop: 2021-01-01T05:00:00Z,
+    count: 5,
+    fn: (n) => (n + 1) * 3600000000000,
+    start: 2021-01-01T00:00:00Z,
+    stop: 2021-01-01T05:00:00Z,
 )
 
 data
-  |> map(fn:(r) => ({ r with _value: string(v: duration(v: r._value)) }))
+    |> map(fn:(r) => ({ r with _value: string(v: duration(v: r._value)) }))
 ```
 
 {{% expand "View input and output" %}}
diff --git a/content/flux/v0.x/stdlib/universe/elapsed.md b/content/flux/v0.x/stdlib/universe/elapsed.md
index 71273fde0..fbac65fca 100644
--- a/content/flux/v0.x/stdlib/universe/elapsed.md
+++ b/content/flux/v0.x/stdlib/universe/elapsed.md
@@ -22,9 +22,9 @@ Given an input table, `elapsed()` returns the same table without the first recor
 
 ```js
 elapsed(
-  unit: 1s,
-  timeColumn: "_time",
-  columnName: "elapsed"
+    unit: 1s,
+    timeColumn: "_time",
+    columnName: "elapsed",
 )
 ```
 
@@ -56,7 +56,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-	|> elapsed(unit: 1s)
+    |> elapsed(unit: 1s)
 ```
 
 {{% expand "View input and output" %}}
diff --git a/content/flux/v0.x/stdlib/universe/exponentialmovingaverage.md b/content/flux/v0.x/stdlib/universe/exponentialmovingaverage.md
index aab2afc7f..9a0bd8403 100644
--- a/content/flux/v0.x/stdlib/universe/exponentialmovingaverage.md
+++ b/content/flux/v0.x/stdlib/universe/exponentialmovingaverage.md
@@ -60,7 +60,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> exponentialMovingAverage(n: 3)
+    |> exponentialMovingAverage(n: 3)
 ```
 
 {{< expand-wrapper >}}
@@ -100,7 +100,7 @@ sampledata.int()
 import "sampledata"
 
 sampledata.int(includeNull: true)
-  |> exponentialMovingAverage(n: 3)
+    |> exponentialMovingAverage(n: 3)
 ```
 
 {{% expand "View input and output" %}}
diff --git a/content/flux/v0.x/stdlib/universe/fill.md b/content/flux/v0.x/stdlib/universe/fill.md
index 6d1241edf..ae3a2374e 100644
--- a/content/flux/v0.x/stdlib/universe/fill.md
+++ b/content/flux/v0.x/stdlib/universe/fill.md
@@ -60,7 +60,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.float(includeNull: true)
-  |> fill(value: 0.0)
+    |> fill(value: 0.0)
 ```
 
 {{< expand-wrapper >}}
@@ -103,7 +103,7 @@ sampledata.float(includeNull: true)
 import "sampledata"
 
 sampledata.float(includeNull: true)
-  |> fill(usePrevious: true)
+    |> fill(usePrevious: true)
 ```
 
 {{% expand "View input and output" %}}
diff --git a/content/flux/v0.x/stdlib/universe/filter.md b/content/flux/v0.x/stdlib/universe/filter.md
index 83cde4a88..634d97670 100644
--- a/content/flux/v0.x/stdlib/universe/filter.md
+++ b/content/flux/v0.x/stdlib/universe/filter.md
@@ -25,8 +25,8 @@ The output tables have the same schema as the corresponding input tables.
 
 ```js
 filter(
-  fn: (r) => r._measurement == "cpu",
-  onEmpty: "drop"
+    fn: (r) => r._measurement == "cpu",
+    onEmpty: "drop",
 )
 ```
 
@@ -79,13 +79,9 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 
 #### Filter based on InfluxDB measurement, field, and tag
 ```js
-from(bucket:"example-bucket")
-  |> range(start:-1h)
-  |> filter(fn: (r) =>
-    r._measurement == "cpu" and
-    r._field == "usage_system" and
-    r.cpu == "cpu-total"
-  )
+from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_system" and r.cpu == "cpu-total")
 ```
 
 #### Keep empty tables when filtering
@@ -96,7 +92,7 @@ import "sampledata"
 import "experimental/table"
 
 sampledata.int()
-  |> filter(fn: (r) => r._value > 18, onEmpty: "keep")
+    |> filter(fn: (r) => r._value > 18, onEmpty: "keep")
 ```
 
 {{% note %}}
@@ -135,7 +131,7 @@ The following example uses data provided by the [`sampledata` package](/flux/v0.
 import "sampledata"
 
 sampledata.int(includeNull: true)
-  |> filter(fn: (r) => exists r._value )
+    |> filter(fn: (r) => exists r._value )
 ```
 
 {{< expand-wrapper >}}
@@ -175,7 +171,7 @@ The following example uses data provided by the [`sampledata` package](/flux/v0.
 import "sampledata"
 
 sampledata.int()
-  |> filter(fn: (r) => r._value > 0 and r._value < 10 )
+    |> filter(fn: (r) => r._value > 0 and r._value < 10 )
 ```
 
 {{% expand "View input and output" %}}
diff --git a/content/flux/v0.x/stdlib/universe/findcolumn.md b/content/flux/v0.x/stdlib/universe/findcolumn.md
index 2579c7fa6..a47bd6fbf 100644
--- a/content/flux/v0.x/stdlib/universe/findcolumn.md
+++ b/content/flux/v0.x/stdlib/universe/findcolumn.md
@@ -24,8 +24,8 @@ is not present in the set of columns.
 
 ```js
 findColumn(
-  fn: (key) => key._field == "fieldName",
-  column: "_value"
+    fn: (key) => key._field == "fieldName",
+    column: "_value",
 )
 ```
 
@@ -49,10 +49,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> findColumn(
-    fn: (key) => key.tag == "t1",
-    column: "_value"
-  )
-
+    |> findColumn(fn: (key) => key.tag == "t1", column: "_value")
+    
 // Returns [-2, 10, 7, 17, 15, 4]
 ```
diff --git a/content/flux/v0.x/stdlib/universe/findrecord.md b/content/flux/v0.x/stdlib/universe/findrecord.md
index c2f41729f..a4b17dc0c 100644
--- a/content/flux/v0.x/stdlib/universe/findrecord.md
+++ b/content/flux/v0.x/stdlib/universe/findrecord.md
@@ -23,8 +23,8 @@ The function returns an empty record if no table is found or if the index is out
 
 ```js
 findRecord(
-  fn: (key) => key._field == "fieldName"),
-  idx: 0
+    fn: (key) => key._field == "fieldName",
+    idx: 0,
 )
 ```
 
@@ -48,10 +48,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> findRecord(
-    fn: (key) => key.tag == "t1",
-    idx: 0
-  )
-
+    |> findRecord(fn: (key) => key.tag == "t1", idx: 0)
+    
 // Returns {_time: 2021-01-01T00:00:00.000000000Z, _value: -2, tag: t1}
 ```
diff --git a/content/flux/v0.x/stdlib/universe/first.md b/content/flux/v0.x/stdlib/universe/first.md
index c977d7be9..470aae521 100644
--- a/content/flux/v0.x/stdlib/universe/first.md
+++ b/content/flux/v0.x/stdlib/universe/first.md
@@ -43,7 +43,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> first()
+    |> first()
 ```
 
 {{% expand "View input and output" %}}
diff --git a/content/flux/v0.x/stdlib/universe/float.md b/content/flux/v0.x/stdlib/universe/float.md
index 33756a462..413035dee 100644
--- a/content/flux/v0.x/stdlib/universe/float.md
+++ b/content/flux/v0.x/stdlib/universe/float.md
@@ -71,10 +71,10 @@ _The following example uses data provided by the [`sampledata` package](/flux/v0
 import "sampledata"
 
 data = sampledata.int()
-  |> rename(columns: {_value: "foo"})
+    |> rename(columns: {_value: "foo"})
 
 data
-  |> map(fn:(r) => ({ r with foo: float(v: r.foo) }))
+    |> map(fn: (r) => ({r with foo: float(v: r.foo)}))
 ```
 
 {{% expand "View input and output" %}}
diff --git a/content/flux/v0.x/stdlib/universe/getcolumn.md b/content/flux/v0.x/stdlib/universe/getcolumn.md
index 3eb2094b8..d6effcb30 100644
--- a/content/flux/v0.x/stdlib/universe/getcolumn.md
+++ b/content/flux/v0.x/stdlib/universe/getcolumn.md
@@ -48,8 +48,8 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> tableFind(fn: (key) => key.tag == "t1")
-  |> getColumn(column: "_value")
-
+    |> tableFind(fn: (key) => key.tag == "t1")
+    |> getColumn(column: "_value")
+    
 // Returns [-2, 10, 7, 17, 15, 4]
 ```
diff --git a/content/flux/v0.x/stdlib/universe/getrecord.md b/content/flux/v0.x/stdlib/universe/getrecord.md
index 58e682a9a..e4d212c29 100644
--- a/content/flux/v0.x/stdlib/universe/getrecord.md
+++ b/content/flux/v0.x/stdlib/universe/getrecord.md
@@ -48,8 +48,8 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> tableFind(fn: (key) => key.tag == "t1")
-  |> getRecord(idx: 0)
-
+    |> tableFind(fn: (key) => key.tag == "t1")
+    |> getRecord(idx: 0)
+    
 // Returns {_time: 2021-01-01T00:00:00.000000000Z, _value: -2, tag: t1}
 ```
diff --git a/content/flux/v0.x/stdlib/universe/group.md b/content/flux/v0.x/stdlib/universe/group.md
index ff8c4f6d0..ed97ccd94 100644
--- a/content/flux/v0.x/stdlib/universe/group.md
+++ b/content/flux/v0.x/stdlib/universe/group.md
@@ -46,8 +46,8 @@ after `group()`.
 
 ```js
 data
-  |> group()
-  |> sort(columns: ["_time"])
+    |> group()
+    |> sort(columns: ["_time"])
 ```
 {{% /warn %}}
 
@@ -80,7 +80,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> group(columns: ["_time", "tag"])
+    |> group(columns: ["_time", "tag"])
 ```
 
 {{< expand-wrapper >}}
@@ -156,7 +156,7 @@ sampledata.int()
 import "sampledata"
 
 sampledata.int()
-  |> group(columns: ["_time"], mode: "except")
+    |> group(columns: ["_time"], mode: "except")
 ```
 
 {{< expand-wrapper >}}
@@ -231,7 +231,7 @@ import "sampledata"
 
 // Merge all tables into a single table
 sampledata.int()
-  |> group()
+    |> group()
 ```
 
 {{% expand "View input and output" %}}
diff --git a/content/flux/v0.x/stdlib/universe/highestaverage.md b/content/flux/v0.x/stdlib/universe/highestaverage.md
index caf2038a5..7f82b7047 100644
--- a/content/flux/v0.x/stdlib/universe/highestaverage.md
+++ b/content/flux/v0.x/stdlib/universe/highestaverage.md
@@ -21,9 +21,9 @@ _`highestAverage()` is a [selector function](/flux/v0.x/function-types/#selector
 
 ```js
 highestAverage(
-  n:10,
-  column: "_value",
-  groupColumns: []
+    n:10,
+    column: "_value",
+    groupColumns: [],
 )
 ```
 
@@ -56,7 +56,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> highestAverage(n: 2, groupColumns: ["tag"])
+    |> highestAverage(n: 2, groupColumns: ["tag"])
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/universe/highestcurrent.md b/content/flux/v0.x/stdlib/universe/highestcurrent.md
index c53810c7c..e66878b1c 100644
--- a/content/flux/v0.x/stdlib/universe/highestcurrent.md
+++ b/content/flux/v0.x/stdlib/universe/highestcurrent.md
@@ -21,9 +21,9 @@ _`highestCurrent()` is a [selector function](/flux/v0.x/function-types/#selector
 
 ```js
 highestCurrent(
-  n:10,
-  column: "_value",
-  groupColumns: []
+    n:10,
+    column: "_value",
+    groupColumns: [],
 )
 ```
 
@@ -56,7 +56,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> highestCurrent(n: 2, groupColumns: ["tag"])
+    |> highestCurrent(n: 2, groupColumns: ["tag"])
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/universe/highestmax.md b/content/flux/v0.x/stdlib/universe/highestmax.md
index 81f5214a5..e39278310 100644
--- a/content/flux/v0.x/stdlib/universe/highestmax.md
+++ b/content/flux/v0.x/stdlib/universe/highestmax.md
@@ -21,9 +21,9 @@ _`highestMax()` is a [selector function](/flux/v0.x/function-types/#selectors)._
 
 ```js
 highestMax(
-  n:10,
-  column: "_value",
-  groupColumns: []
+    n:10,
+    column: "_value",
+    groupColumns: [],
 )
 ```
 
@@ -56,7 +56,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> highestMax(n: 2, groupColumns: ["tag"])
+    |> highestMax(n: 2, groupColumns: ["tag"])
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/universe/histogram.md b/content/flux/v0.x/stdlib/universe/histogram.md
index 4525dbd0a..7e6ba3800 100644
--- a/content/flux/v0.x/stdlib/universe/histogram.md
+++ b/content/flux/v0.x/stdlib/universe/histogram.md
@@ -27,12 +27,12 @@ Columns not part of the group key are removed and an upper bound column and a co
 
 ```js
 histogram(
-  column: "_value",
-  upperBoundColumn: "le",
-  countColumn: "_value",
-  bins: [50.0, 75.0, 90.0],
-  normalize: false
-  )
+    column: "_value",
+    upperBoundColumn: "le",
+    countColumn: "_value",
+    bins: [50.0, 75.0, 90.0],
+    normalize: false,
+)
 ```
 
 ## Parameters
@@ -84,7 +84,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.float()
-  |> histogram(bins: [0.0, 5.0, 10.0, 20.0])
+    |> histogram(bins: [0.0, 5.0, 10.0, 20.0])
 ```
 
 {{< expand-wrapper >}}
@@ -123,9 +123,7 @@ sampledata.float()
 import "sampledata"
 
 sampledata.float()
-  |> histogram(
-    bins: linearBins(start:0.0, width:4.0, count:3)
-  )
+    |> histogram(bins: linearBins(start: 0.0, width: 4.0, count: 3))
 ```
 
 {{% expand "View input and output" %}}
diff --git a/content/flux/v0.x/stdlib/universe/histogramquantile.md b/content/flux/v0.x/stdlib/universe/histogramquantile.md
index 529e2819b..2e8dc151e 100644
--- a/content/flux/v0.x/stdlib/universe/histogramquantile.md
+++ b/content/flux/v0.x/stdlib/universe/histogramquantile.md
@@ -42,11 +42,11 @@ _**Output data type:** Float_
 
 ```js
 histogramQuantile(
-  quantile: 0.5,
-  countColumn: "_value",
-  upperBoundColumn: "le",
-  valueColumn: "_value",
-  minValue: 0.0
+    quantile: 0.5,
+    countColumn: "_value",
+    upperBoundColumn: "le",
+    valueColumn: "_value",
+    minValue: 0.0,
 )
 ```
 
@@ -95,10 +95,10 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 data = sampledata.float()
-  |> histogram(bins: [0.0, 5.0, 10.0, 20.0])
+    |> histogram(bins: [0.0, 5.0, 10.0, 20.0])
 
 data
-  |> histogramQuantile(quantile: 0.9)
+    |> histogramQuantile(quantile: 0.9)
 ```
 
 {{% expand "View input and output" %}}
diff --git a/content/flux/v0.x/stdlib/universe/holtwinters.md b/content/flux/v0.x/stdlib/universe/holtwinters.md
index 1a2b7e7b0..47e5a9864 100644
--- a/content/flux/v0.x/stdlib/universe/holtwinters.md
+++ b/content/flux/v0.x/stdlib/universe/holtwinters.md
@@ -25,12 +25,12 @@ _**Output data type:** Float_
 
 ```js
 holtWinters(
-  n: 10,
-  seasonality: 4,
-  interval: 30d,
-  withFit: false,
-  timeColumn: "_time",
-  column: "_value",
+    n: 10,
+    seasonality: 4,
+    interval: 30d,
+    withFit: false,
+    timeColumn: "_time",
+    column: "_value",
 )
 ```
 
@@ -119,7 +119,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> holtWinters(n: 6, interval: 10s)
+    |> holtWinters(n: 6, interval: 10s)
 ```
 
 {{< expand-wrapper >}}
@@ -162,11 +162,7 @@ sampledata.int()
 import "sampledata"
 
 sampledata.int()
-  |> holtWinters(
-    n: 4,
-    interval: 10s,
-    seasonality: 4
-  )
+    |> holtWinters(n: 4, interval: 10s, seasonality: 4)
 ```
 
 {{< expand-wrapper >}}
@@ -205,11 +201,7 @@ sampledata.int()
 import "sampledata"
 
 sampledata.int()
-  |> holtWinters(
-    n: 3,
-    interval: 10s,
-    withFit: true
-  )
+    |> holtWinters(n: 3, interval: 10s, withFit: true)
 ```
 
 {{% expand "View input and output" %}}
diff --git a/content/flux/v0.x/stdlib/universe/hourselection.md b/content/flux/v0.x/stdlib/universe/hourselection.md
index 6c1f6d3d8..1cfb65276 100644
--- a/content/flux/v0.x/stdlib/universe/hourselection.md
+++ b/content/flux/v0.x/stdlib/universe/hourselection.md
@@ -21,9 +21,9 @@ The `hourSelection()` function retains all rows with time values in a specified
 
 ```js
 hourSelection(
-  start: 9,
-  stop: 17,
-  timeColumn: "_time"
+    start: 9,
+    stop: 17,
+    timeColumn: "_time",
 )
 ```
 
@@ -56,14 +56,14 @@ to generate sample data and show how `covariance()` transforms data.
 import "generate"
 
 data = generate.from(
-  count: 8,
-  fn: (n) => n * n,
-  start: 2021-01-01T00:00:00Z,
-  stop: 2021-01-02T00:00:00Z
+    count: 8,
+    fn: (n) => n * n,
+    start: 2021-01-01T00:00:00Z,
+    stop: 2021-01-02T00:00:00Z,
 )
   
 data 
-  |> hourSelection(start: 9, stop: 17)
+    |> hourSelection(start: 9, stop: 17)
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/universe/increase.md b/content/flux/v0.x/stdlib/universe/increase.md
index 27c0ed2c1..9ca615339 100644
--- a/content/flux/v0.x/stdlib/universe/increase.md
+++ b/content/flux/v0.x/stdlib/universe/increase.md
@@ -27,8 +27,6 @@ when they hit a threshold or are reset.
 In the case of a wrap/reset, we can assume that the absolute delta between two
 points will be at least their non-negative difference.
 
-_**Output data type:** Float_
-
 ```js
 increase(columns: ["_value"])
 ```
@@ -54,7 +52,7 @@ For each input table with `n` rows, `increase()` outputs a table with `n - 1` ro
 import "sampledata"
 
 sampledata.int()
-  |> increase()
+    |> increase()
 ```
 
 {{< expand-wrapper >}}
@@ -92,10 +90,3 @@ sampledata.int()
 {{< /flex >}}
 {{% /expand %}}
 {{< /expand-wrapper >}}
-
-## Function definition
-```js
-increase = (tables=<-, columns=["_value"]) => tables
-    |> difference(nonNegative: true, columns: column, keepFirst: true, initialZero: true)
-    |> cumulativeSum()
-```
diff --git a/content/flux/v0.x/stdlib/universe/int.md b/content/flux/v0.x/stdlib/universe/int.md
index 09d52eed6..eacf7f2b4 100644
--- a/content/flux/v0.x/stdlib/universe/int.md
+++ b/content/flux/v0.x/stdlib/universe/int.md
@@ -19,8 +19,6 @@ introduced: 0.7.0
 
 The `int()` function converts a single value to an integer.
 
-_**Output data type:** Integer_
-
 ```js
 int(v: "4")
 ```
@@ -98,10 +96,10 @@ _The following example uses data provided by the [`sampledata` package](/flux/v0
 import "sampledata"
 
 data = sampledata.float()
-  |> rename(columns: {_value: "foo"})
+    |> rename(columns: {_value: "foo"})
 
 data
-  |> map(fn:(r) => ({ r with foo: int(v: r.foo) }))
+    |> map(fn: (r) => ({r with foo: int(v: r.foo)}))
 ```
 
 {{% expand "View input and output" %}}
diff --git a/content/flux/v0.x/stdlib/universe/integral.md b/content/flux/v0.x/stdlib/universe/integral.md
index 77a3cdf0b..9202248c5 100644
--- a/content/flux/v0.x/stdlib/universe/integral.md
+++ b/content/flux/v0.x/stdlib/universe/integral.md
@@ -27,10 +27,10 @@ _**Output data type:** Float_
 
 ```js
 integral(
-  unit: 10s,
-  column: "_value",
-  timeColumn: "_time",
-  interpolate: ""
+    unit: 10s,
+    column: "_value",
+    timeColumn: "_time",
+    interpolate: "",
 )
 ```
 
@@ -69,8 +69,8 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> range(start: sampledata.start, stop: sampledata.stop)
-  |> integral(unit:10s)
+    |> range(start: sampledata.start, stop: sampledata.stop)
+    |> integral(unit:10s)
 ```
 
 {{< expand-wrapper >}}
@@ -97,8 +97,8 @@ sampledata.int()
 import "sampledata"
 
 sampledata.int(includeNull: true)
-  |> range(start: sampledata.start, stop: sampledata.stop)
-  |> integral(unit:10s, interpolate: "linear")
+    |> range(start: sampledata.start, stop: sampledata.stop)
+    |> integral(unit:10s, interpolate: "linear")
 ```
 
 {{% expand "View input and output" %}}
diff --git a/content/flux/v0.x/stdlib/universe/intervals.md b/content/flux/v0.x/stdlib/universe/intervals.md
index 4d955bf93..df3ee4e5e 100644
--- a/content/flux/v0.x/stdlib/universe/intervals.md
+++ b/content/flux/v0.x/stdlib/universe/intervals.md
@@ -85,23 +85,23 @@ intervals(every:1mo, period:-1d)
 ```js
 // 1 day intervals excluding weekends
 intervals(
-  every:1d,
-  filter: (interval) => !(weekday(time: interval.start) in [Sunday, Saturday]),
+    every: 1d,
+    filter: (interval) => !(weekday(time: interval.start) in [Sunday, Saturday]),
 )
 
 // Work hours from 9AM - 5PM on work days.
 intervals(
-  every:1d,
-  period:8h,
-  offset:9h,
-  filter:(interval) => !(weekday(time: interval.start) in [Sunday, Saturday]),
+    every: 1d,
+    period: 8h,
+    offset: 9h,
+    filter: (interval) => !(weekday(time: interval.start) in [Sunday, Saturday]),
 )
 ```
 
 ##### Using known start and stop dates
 ```js
 // Every hour for six hours on Sep 5th.
-intervals(every:1h)(start:2018-09-05T00:00:00-07:00, stop: 2018-09-05T06:00:00-07:00)
+intervals(every: 1h)(start: 2018-09-05T00:00:00-07:00, stop: 2018-09-05T06:00:00-07:00)
 
 // Generates
 // [2018-09-05T00:00:00-07:00, 2018-09-05T01:00:00-07:00)
@@ -112,7 +112,7 @@ intervals(every:1h)(start:2018-09-05T00:00:00-07:00, stop: 2018-09-05T06:00:00-0
 // [2018-09-05T05:00:00-07:00, 2018-09-05T06:00:00-07:00)
 
 // Every hour for six hours with 1h30m periods on Sep 5th
-intervals(every:1h, period:1h30m)(start:2018-09-05T00:00:00-07:00, stop: 2018-09-05T06:00:00-07:00)
+intervals(every: 1h, period: 1h30m)(start: 2018-09-05T00:00:00-07:00, stop: 2018-09-05T06:00:00-07:00)
 
 // Generates
 // [2018-09-05T00:00:00-07:00, 2018-09-05T01:30:00-07:00)
@@ -123,7 +123,7 @@ intervals(every:1h, period:1h30m)(start:2018-09-05T00:00:00-07:00, stop: 2018-09
 // [2018-09-05T05:00:00-07:00, 2018-09-05T06:30:00-07:00)
 
 // Every hour for six hours using the previous hour on Sep 5th
-intervals(every:1h, period:-1h)(start:2018-09-05T12:00:00-07:00, stop: 2018-09-05T18:00:00-07:00)
+intervals(every: 1h, period: -1h)(start: 2018-09-05T12:00:00-07:00, stop: 2018-09-05T18:00:00-07:00)
 
 // Generates
 // [2018-09-05T11:00:00-07:00, 2018-09-05T12:00:00-07:00)
@@ -135,7 +135,7 @@ intervals(every:1h, period:-1h)(start:2018-09-05T12:00:00-07:00, stop: 2018-09-0
 // [2018-09-05T17:00:00-07:00, 2018-09-05T18:00:00-07:00)
 
 // Every month for 4 months starting on Jan 1st
-intervals(every:1mo)(start:2018-01-01, stop: 2018-05-01)
+intervals(every: 1mo)(start: 2018-01-01T00:00:00Z, stop: 2018-05-01T00:00:00Z)
 
 // Generates
 // [2018-01-01, 2018-02-01)
@@ -144,7 +144,7 @@ intervals(every:1mo)(start:2018-01-01, stop: 2018-05-01)
 // [2018-04-01, 2018-05-01)
 
 // Every month for 4 months starting on Jan 15th
-intervals(every:1mo)(start:2018-01-15, stop: 2018-05-15)
+intervals(every: 1mo)(start: 2018-01-15T00:00:00Z, stop: 2018-05-15T00:00:00Z)
 
 // Generates
 // [2018-01-15, 2018-02-15)
diff --git a/content/flux/v0.x/stdlib/universe/join.md b/content/flux/v0.x/stdlib/universe/join.md
index 77a49ed6d..960bdd14b 100644
--- a/content/flux/v0.x/stdlib/universe/join.md
+++ b/content/flux/v0.x/stdlib/universe/join.md
@@ -28,9 +28,9 @@ The resulting group key is the union of the input group keys.
 
 ```js
 join(
-  tables: {key1: table1, key2: table2},
-  on: ["_time", "_field"],
-  method: "inner"
+    tables: {key1: table1, key2: table2},
+    on: ["_time", "_field"],
+    method: "inner",
 )
 ```
 
@@ -95,13 +95,10 @@ import "generate"
 t1 = generate.from(count: 4, fn: (n) => n + 1, start: 2021-01-01T00:00:00Z, stop: 2021-01-05T00:00:00Z)
     |> set(key: "tag", value: "foo")
 
-t2 = generate.from(count: 4, fn: (n) => n * -1, start: 2021-01-01T00:00:00Z, stop: 2021-01-05T00:00:00Z)
+t2 = generate.from(count: 4, fn: (n) => n * (-1), start: 2021-01-01T00:00:00Z, stop: 2021-01-05T00:00:00Z)
     |> set(key: "tag", value: "foo")
 
-join(
-    tables: {t1: t1, t2: t2},
-    on: ["_time", "tag"],
-)
+join(tables: {t1: t1, t2: t2}, on: ["_time", "tag"])
 ```
 
 #### Input data streams
@@ -145,24 +142,15 @@ The following example shows how data in different InfluxDB measurements can be
 joined with Flux.
 
 ```js
-data_1 = from(bucket:"example-bucket")
-    |> range(start:-15m)
-    |> filter(fn: (r) =>
-        r._measurement == "cpu" and
-        r._field == "usage_system"
-    )
+data_1 = from(bucket: "example-bucket")
+    |> range(start: -15m)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_system")
 
-data_2 = from(bucket:"example-bucket")
-    |> range(start:-15m)
-    |> filter(fn: (r) =>
-        r._measurement == "mem" and
-        r._field == "used_percent"
-    )
+data_2 = from(bucket: "example-bucket")
+    |> range(start: -15m)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
 
-join(
-    tables: {d1: data_1, d2: data_2},
-    on: ["_time", "host"],
-)
+join(tables: {d1: data_1, d2: data_2}, on: ["_time", "host"])
 ```
 
 ## join() versus union()
@@ -204,10 +192,7 @@ are illustrated below:
 
 #### join() output
 ```js
-join(
-    tables: {t1: t1, t2: t2},
-    on: ["_time", "tag"],
-)
+join(tables: {t1: t1, t2: t2}, on: ["_time", "tag"])
 ```
 
 | _time                | tag | _value_t1 | _value_t2 |
@@ -233,3 +218,4 @@ union(tables: [t1, t2])
 | 2021-01-03T00:00:00Z | foo |      3 |
 | 2021-01-04T00:00:00Z | foo |      4 |
 {{% /expand %}}
+
diff --git a/content/flux/v0.x/stdlib/universe/kaufmansama.md b/content/flux/v0.x/stdlib/universe/kaufmansama.md
index 93cc37236..0b87fa895 100644
--- a/content/flux/v0.x/stdlib/universe/kaufmansama.md
+++ b/content/flux/v0.x/stdlib/universe/kaufmansama.md
@@ -26,8 +26,8 @@ using values in an input table.
 
 ```js
 kaufmansAMA(
-  n: 10,
-  column: "_value"
+    n: 10,
+    column: "_value",
 )
 ```
 
@@ -55,7 +55,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> kaufmansAMA(n: 3)
+    |> kaufmansAMA(n: 3)
 ```
 
 {{% expand "View input and output" %}}
diff --git a/content/flux/v0.x/stdlib/universe/kaufmanser.md b/content/flux/v0.x/stdlib/universe/kaufmanser.md
index 6fc30f9bc..80dcbe629 100644
--- a/content/flux/v0.x/stdlib/universe/kaufmanser.md
+++ b/content/flux/v0.x/stdlib/universe/kaufmanser.md
@@ -49,7 +49,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> kaufmansER(n: 3)
+    |> kaufmansER(n: 3)
 ```
 
 {{% expand "View input and output" %}}
diff --git a/content/flux/v0.x/stdlib/universe/keep.md b/content/flux/v0.x/stdlib/universe/keep.md
index 76ad4ff8d..89274683a 100644
--- a/content/flux/v0.x/stdlib/universe/keep.md
+++ b/content/flux/v0.x/stdlib/universe/keep.md
@@ -60,7 +60,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> keep(columns: ["_time", "_value"])
+    |> keep(columns: ["_time", "_value"])
 ```
 
 {{< expand-wrapper >}}
@@ -101,7 +101,7 @@ sampledata.int()
 import "sampledata"
 
 sampledata.int()
-  |> keep(fn: (column) => column =~ /^_?t/)
+    |> keep(fn: (column) => column =~ /^_?t/)
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/universe/keys.md b/content/flux/v0.x/stdlib/universe/keys.md
index 3939ee9d5..e18a86223 100644
--- a/content/flux/v0.x/stdlib/universe/keys.md
+++ b/content/flux/v0.x/stdlib/universe/keys.md
@@ -55,12 +55,12 @@ to simulate data queried from InfluxDB and illustrate how `keys()` transforms da
 ```js
 import "influxdata/influxdb/sample"
 
-data = sample.data(set: "airSensor") 
-  |> range(start: -30m)
-  |> filter(fn: (r) => r.sensor_id == "TLM0100")
+data = sample.data(set: "airSensor")
+    |> range(start: -30m)
+    |> filter(fn: (r) => r.sensor_id == "TLM0100")
 
 data
-  |> keys()
+    |> keys()
 ```
 
 {{< expand-wrapper >}}
@@ -122,14 +122,14 @@ data
 ```js
 import "influxdata/influxdb/sample"
 
-data = sample.data(set: "airSensor") 
-  |> range(start: -30m)
-  |> filter(fn: (r) => r.sensor_id == "TLM0100")
+data = sample.data(set: "airSensor")
+    |> range(start: -30m)
+    |> filter(fn: (r) => r.sensor_id == "TLM0100")
 
 data
-  |> keys()
-  |> keep(columns: ["_value"])
-  |> distinct()
+    |> keys()
+    |> keep(columns: ["_value"])
+    |> distinct()
 ```
 
 {{< expand-wrapper >}}
@@ -182,13 +182,13 @@ To return group key columns as an array:
 ```js
 import "influxdata/influxdb/sample"
 
-data = sample.data(set: "airSensor") 
-  |> range(start: -30m)
-  |> filter(fn: (r) => r.sensor_id == "TLM0100")
+data = sample.data(set: "airSensor")
+    |> range(start: -30m)
+    |> filter(fn: (r) => r.sensor_id == "TLM0100")
 
 data
-  |> keys()
-  |> findColumn(fn: (key) => true, column: "_value")
+    |> keys()
+    |> findColumn(fn: (key) => true, column: "_value")
 
 // Returns [_start, _stop, _field, _measurement, sensor_id]
 ```
diff --git a/content/flux/v0.x/stdlib/universe/keyvalues.md b/content/flux/v0.x/stdlib/universe/keyvalues.md
index a71689d85..c24698c2d 100644
--- a/content/flux/v0.x/stdlib/universe/keyvalues.md
+++ b/content/flux/v0.x/stdlib/universe/keyvalues.md
@@ -83,11 +83,11 @@ to simulate data queried from InfluxDB and illustrate how `keys()` transforms da
 ```js
 import "influxdata/influxdb/sample"
 
-data = sample.data(set: "airSensor") 
-  |> filter(fn: (r) => r.sensor_id == "TLM0100")
+data = sample.data(set: "airSensor")
+    |> filter(fn: (r) => r.sensor_id == "TLM0100")
 
 data
-  |> keyValues(keyColumns: ["sensor_id", "_field"])
+    |> keyValues(keyColumns: ["sensor_id", "_field"])
 ```
 
 {{< expand-wrapper >}}
@@ -145,16 +145,16 @@ data
 ```js
 import "influxdata/influxdb/sample"
 
-data = sample.data(set: "airSensor") 
-  |> filter(fn: (r) => r.sensor_id == "TLM0100")
+data = sample.data(set: "airSensor")
+    |> filter(fn: (r) => r.sensor_id == "TLM0100")
 
 keyColumns = data
-  |> keys()
-  |> findColumn(fn: (key) => true, column: "_value")
-  // Returns [_field, _measurement, sensor_id]
+    |> keys()
+    |> findColumn(fn: (key) => true, column: "_value")
+// Returns [_field, _measurement, sensor_id]
 
 data
-  |> keyValues(keyColumns: keyColumns)
+    |> keyValues(keyColumns: keyColumns)
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/universe/last.md b/content/flux/v0.x/stdlib/universe/last.md
index 3304f79b7..3d3881a31 100644
--- a/content/flux/v0.x/stdlib/universe/last.md
+++ b/content/flux/v0.x/stdlib/universe/last.md
@@ -49,7 +49,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> last()
+    |> last()
 ```
 
 {{% expand "View input and output" %}}
diff --git a/content/flux/v0.x/stdlib/universe/limit.md b/content/flux/v0.x/stdlib/universe/limit.md
index 27b563932..5579705ea 100644
--- a/content/flux/v0.x/stdlib/universe/limit.md
+++ b/content/flux/v0.x/stdlib/universe/limit.md
@@ -26,10 +26,7 @@ If the input table has less than `offset + n` records, `limit()` outputs all rec
 _`limit()` is a [selector function](/flux/v0.x/function-types/#selectors)._
 
 ```js
-limit(
-  n:10,
-  offset: 0
-)
+limit(n:10, offset: 0)
 ```
 
 ## Parameters
@@ -57,7 +54,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> limit(n: 3)
+    |> limit(n: 3)
 ```
 
 {{< expand-wrapper >}}
@@ -94,7 +91,7 @@ sampledata.int()
 import "sampledata"
 
 sampledata.int()
-  |> limit(n: 3, offset: 2)
+    |> limit(n: 3, offset: 2)
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/universe/linearbins.md b/content/flux/v0.x/stdlib/universe/linearbins.md
index 21f4bf4dd..18f31984e 100644
--- a/content/flux/v0.x/stdlib/universe/linearbins.md
+++ b/content/flux/v0.x/stdlib/universe/linearbins.md
@@ -21,10 +21,10 @@ _**Output data type:** Array of floats_
 
 ```js
 linearBins(
-  start: 0.0,
-  width: 5.0,
-  count: 20,
-  infinity: true
+    start: 0.0,
+    width: 5.0,
+    count: 20,
+    infinity: true,
 )
 ```
 
diff --git a/content/flux/v0.x/stdlib/universe/logarithmicbins.md b/content/flux/v0.x/stdlib/universe/logarithmicbins.md
index ae33a1157..b22722ff4 100644
--- a/content/flux/v0.x/stdlib/universe/logarithmicbins.md
+++ b/content/flux/v0.x/stdlib/universe/logarithmicbins.md
@@ -21,10 +21,10 @@ _**Output data type:** Array of floats_
 
 ```js
 logarithmicBins(
-  start:1.0, 
-  factor: 2.0, 
-  count: 10, 
-  infinity: true
+    start:1.0, 
+    factor: 2.0, 
+    count: 10, 
+    infinity: true,
 )
 ```
 
diff --git a/content/flux/v0.x/stdlib/universe/lowestaverage.md b/content/flux/v0.x/stdlib/universe/lowestaverage.md
index 5f1f4f193..cfbd9d0ae 100644
--- a/content/flux/v0.x/stdlib/universe/lowestaverage.md
+++ b/content/flux/v0.x/stdlib/universe/lowestaverage.md
@@ -21,9 +21,9 @@ _`lowestAverage()` is a [selector function](/flux/v0.x/function-types/#selectors
 
 ```js
 lowestAverage(
-  n:10,
-  column: "_value",
-  groupColumns: []
+    n:10,
+    column: "_value",
+    groupColumns: [],
 )
 ```
 
@@ -56,7 +56,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> lowestAverage(n: 2, groupColumns: ["tag"])
+    |> lowestAverage(n: 2, groupColumns: ["tag"])
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/universe/lowestcurrent.md b/content/flux/v0.x/stdlib/universe/lowestcurrent.md
index e487bf744..4c34d5114 100644
--- a/content/flux/v0.x/stdlib/universe/lowestcurrent.md
+++ b/content/flux/v0.x/stdlib/universe/lowestcurrent.md
@@ -21,9 +21,9 @@ _`lowestCurrent()` is a [selector function](/flux/v0.x/function-types/#selectors
 
 ```js
 lowestCurrent(
-  n:10,
-  column: "_value",
-  groupColumns: []
+    n:10,
+    column: "_value",
+    groupColumns: [],
 )
 ```
 
@@ -56,7 +56,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> lowestCurrent(n: 2, groupColumns: ["tag"])
+    |> lowestCurrent(n: 2, groupColumns: ["tag"])
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/universe/lowestmin.md b/content/flux/v0.x/stdlib/universe/lowestmin.md
index 7a6d39cee..fdfbaa540 100644
--- a/content/flux/v0.x/stdlib/universe/lowestmin.md
+++ b/content/flux/v0.x/stdlib/universe/lowestmin.md
@@ -21,9 +21,9 @@ _`lowestMin()` is a [selector function](/flux/v0.x/function-types/#selectors)._
 
 ```js
 lowestMin(
-  n:10,
-  column: "_value",
-  groupColumns: []
+    n:10,
+    column: "_value",
+    groupColumns: [],
 )
 ```
 
@@ -56,7 +56,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> lowestMin(n: 2, groupColumns: ["tag"])
+    |> lowestMin(n: 2, groupColumns: ["tag"])
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/universe/map.md b/content/flux/v0.x/stdlib/universe/map.md
index afa7d2fed..cdc390665 100644
--- a/content/flux/v0.x/stdlib/universe/map.md
+++ b/content/flux/v0.x/stdlib/universe/map.md
@@ -126,11 +126,13 @@ sampledata.int()
 import "sampledata"
 
 sampledata.int()
-  |> map(fn: (r) => ({
-    time: r._time,
-    source: r.tag,
-    alert: if r._value > 10 then true else false
-  }))
+    |> map(
+        fn: (r) => ({
+            time: r._time,
+            source: r.tag,
+            alert: if r._value > 10 then true else false
+        })
+    )
 ```
 
 {{< expand-wrapper >}}
@@ -173,11 +175,13 @@ operated on by the map operation.
 import "sampledata"
 
 sampledata.int()
-  |> map(fn: (r) => ({
-    r with
-    server: "server-${r.tag}",
-    valueFloat: float(v: r._value)
-  }))
+  |> map(
+      fn: (r) => ({
+          r with
+          server: "server-${r.tag}",
+          valueFloat: float(v: r._value)
+      })
+  )
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/universe/max.md b/content/flux/v0.x/stdlib/universe/max.md
index 4b9576500..d8c994fe5 100644
--- a/content/flux/v0.x/stdlib/universe/max.md
+++ b/content/flux/v0.x/stdlib/universe/max.md
@@ -46,7 +46,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> max()
+    |> max()
 ```
 
 {{% expand "View input and output" %}}
diff --git a/content/flux/v0.x/stdlib/universe/mean.md b/content/flux/v0.x/stdlib/universe/mean.md
index abf188bda..9bd016886 100644
--- a/content/flux/v0.x/stdlib/universe/mean.md
+++ b/content/flux/v0.x/stdlib/universe/mean.md
@@ -44,7 +44,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> mean()
+    |> mean()
 ```
 
 {{% expand "View input and output" %}}
diff --git a/content/flux/v0.x/stdlib/universe/median.md b/content/flux/v0.x/stdlib/universe/median.md
index f14355225..6387e5d3f 100644
--- a/content/flux/v0.x/stdlib/universe/median.md
+++ b/content/flux/v0.x/stdlib/universe/median.md
@@ -30,9 +30,9 @@ the [`method`](#method) used._
 
 ```js
 median(
-  column: "_value",
-  method: "estimate_tdigest",
-  compression: 0.0
+    column: "_value",
+    method: "estimate_tdigest",
+    compression: 0.0,
 )
 ```
 
@@ -91,7 +91,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.float()
-  |> median()
+    |> median()
 ```
 
 {{< expand-wrapper >}}
@@ -124,7 +124,7 @@ sampledata.float()
 import "sampledata"
 
 sampledata.float()
-  |> median(method: "exact_selector")
+    |> median(method: "exact_selector")
 ```
 
 {{< expand-wrapper >}}
@@ -151,13 +151,3 @@ sampledata.float()
 {{< /flex >}}
 {{% /expand %}}
 {{< /expand-wrapper >}}
-
-## Function definition
-```js
-median = (method="estimate_tdigest", compression=0.0, tables=<-) =>
-  quantile(
-    q:0.5,
-    method:method,
-    compression:compression
-  )
-```
diff --git a/content/flux/v0.x/stdlib/universe/min.md b/content/flux/v0.x/stdlib/universe/min.md
index 8e0f22877..93ac6495e 100644
--- a/content/flux/v0.x/stdlib/universe/min.md
+++ b/content/flux/v0.x/stdlib/universe/min.md
@@ -46,7 +46,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> min()
+    |> min()
 ```
 
 {{% expand "View input and output" %}}
diff --git a/content/flux/v0.x/stdlib/universe/mode.md b/content/flux/v0.x/stdlib/universe/mode.md
index 9f0cb29c0..c63db4e41 100644
--- a/content/flux/v0.x/stdlib/universe/mode.md
+++ b/content/flux/v0.x/stdlib/universe/mode.md
@@ -62,7 +62,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> mode()
+    |> mode()
 ```
 
 {{% expand "View input and output" %}}
diff --git a/content/flux/v0.x/stdlib/universe/movingaverage.md b/content/flux/v0.x/stdlib/universe/movingaverage.md
index 697f16147..f4b3dbfd6 100644
--- a/content/flux/v0.x/stdlib/universe/movingaverage.md
+++ b/content/flux/v0.x/stdlib/universe/movingaverage.md
@@ -58,7 +58,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> movingAverage(n: 3)
+    |> movingAverage(n: 3)
 ```
 
 {{% expand-wrapper %}}
@@ -97,7 +97,7 @@ sampledata.int()
 import "sampledata"
 
 sampledata.int(includeNull: true)
-  |> movingAverage(n: 3)
+    |> movingAverage(n: 3)
 ```
 
 {{% expand-wrapper %}}
diff --git a/content/flux/v0.x/stdlib/universe/now.md b/content/flux/v0.x/stdlib/universe/now.md
index 09babc72f..cf05b8d3c 100644
--- a/content/flux/v0.x/stdlib/universe/now.md
+++ b/content/flux/v0.x/stdlib/universe/now.md
@@ -28,7 +28,7 @@ now()
 ##### Use the current UTC time as a query boundary
 ```js
 data
-  |> range(start: -10h, stop: now())
+    |> range(start: -10h, stop: now())
 ```
 
 ##### Return the now option time
diff --git a/content/flux/v0.x/stdlib/universe/pearsonr.md b/content/flux/v0.x/stdlib/universe/pearsonr.md
index 1e2aab23f..542699fa6 100644
--- a/content/flux/v0.x/stdlib/universe/pearsonr.md
+++ b/content/flux/v0.x/stdlib/universe/pearsonr.md
@@ -44,18 +44,20 @@ to generate sample data and show how `pearsonr()` transforms data.
 import "generate"
 
 stream1 = generate.from(
-  count: 5,
-  fn: (n) => n * n,
-  start: 2021-01-01T00:00:00Z,
-  stop: 2021-01-01T00:01:00Z
-) |> toFloat()
+    count: 5,
+    fn: (n) => n * n,
+    start: 2021-01-01T00:00:00Z,
+    stop: 2021-01-01T00:01:00Z,
+)
+    |> toFloat()
 
 stream2 = generate.from(
-  count: 5,
-  fn: (n) => n * n * n / 2,
-  start: 2021-01-01T00:00:00Z,
-  stop: 2021-01-01T00:01:00Z
-) |> toFloat()
+    count: 5,
+    fn: (n) => n * n * n / 2,
+    start: 2021-01-01T00:00:00Z,
+    stop: 2021-01-01T00:01:00Z,
+)
+    |> toFloat()
 
 pearsonr(x: stream1, y: stream2, on: ["_time"])
 ```
@@ -94,9 +96,3 @@ pearsonr(x: stream1, y: stream2, on: ["_time"])
 
 {{% /expand %}}
 {{< /expand-wrapper >}}
-
-## Function definition
-```js
-pearsonr = (x,y,on) =>
-  cov(x:x, y:y, on:on, pearsonr:true)
-```
diff --git a/content/flux/v0.x/stdlib/universe/pivot.md b/content/flux/v0.x/stdlib/universe/pivot.md
index 523ef6444..68ee84331 100644
--- a/content/flux/v0.x/stdlib/universe/pivot.md
+++ b/content/flux/v0.x/stdlib/universe/pivot.md
@@ -70,11 +70,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 
 ```js
 data
-  |> pivot(
-    rowKey:["_time"],
-    columnKey: ["_field"],
-    valueColumn: "_value"
-  )
+    |> pivot(rowKey: ["_time"], columnKey: ["_field"], valueColumn: "_value")
 ```
 
 {{< expand-wrapper >}}
@@ -116,11 +112,7 @@ data
 
 ```js
 data
-  |> pivot(
-    rowKey:["_time"],
-    columnKey: ["_measurement", "_field"],
-    valueColumn: "_value"
-  )
+    |> pivot(rowKey: ["_time"], columnKey: ["_measurement", "_field"], valueColumn: "_value")
 ```
 
 {{< expand-wrapper >}}
@@ -161,11 +153,7 @@ data
 import "sampledata"
 
 sampledata.int()
-  |> pivot(
-    rowKey: ["_time"],
-    columnKey: ["tag"],
-    valueColumn: "_value"
-  )
+    |> pivot(rowKey: ["_time"], columnKey: ["tag"], valueColumn: "_value")
 ```
 
 {{< expand-wrapper >}}
@@ -193,3 +181,4 @@ sampledata.int()
 {{< /flex >}}
 {{% /expand %}}
 {{< /expand-wrapper >}}
+
diff --git a/content/flux/v0.x/stdlib/universe/quantile.md b/content/flux/v0.x/stdlib/universe/quantile.md
index 29b7259b0..1b7ddf75f 100644
--- a/content/flux/v0.x/stdlib/universe/quantile.md
+++ b/content/flux/v0.x/stdlib/universe/quantile.md
@@ -31,10 +31,10 @@ the [`method`](#method) used._
 
 ```js
 quantile(
-  column: "_value",
-  q: 0.99,
-  method: "estimate_tdigest",
-  compression: 1000.0
+    column: "_value",
+    q: 0.99,
+    method: "estimate_tdigest",
+    compression: 1000.0,
 )
 ```
 
@@ -90,11 +90,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.float()
-  |> quantile(
-    q: 0.99,
-    method: "estimate_tdigest",
-    compression: 1000.0
-  )
+    |> quantile(q: 0.99, method: "estimate_tdigest", compression: 1000.0)
 ```
 
 {{< expand-wrapper >}}
@@ -127,10 +123,7 @@ sampledata.float()
 import "sampledata"
 
 sampledata.float()
-  |> quantile(
-    q: 0.5,
-    method: "exact_selector"
-  )
+    |> quantile(q: 0.5, method: "exact_selector")
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/universe/range.md b/content/flux/v0.x/stdlib/universe/range.md
index 539590ede..c42c74545 100644
--- a/content/flux/v0.x/stdlib/universe/range.md
+++ b/content/flux/v0.x/stdlib/universe/range.md
@@ -24,10 +24,7 @@ Each input table's group key value is modified to fit within the time bounds.
 Tables where all records exists outside the time bounds are filtered entirely.
 
 ```js
-range(
-  start: -15m,
-  stop: now()
-)
+range(start: -15m, stop: now())
 ```
 
 #### Behavior of start and stop times
@@ -72,28 +69,28 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 
 #### Time range relative to now
 ```js
-from(bucket:"example-bucket")
-  |> range(start: -12h)
-  // ...
+from(bucket: "example-bucket")
+    |> range(start: -12h)
+    // ...
 ```
 
 #### Relative time range
 ```js
-from(bucket:"example-bucket")
-  |> range(start: -12h, stop: -15m)
-  // ...
+from(bucket: "example-bucket")
+    |> range(start: -12h, stop: -15m)
+    // ...
 ```
 
 #### Absolute time range
 ```js
-from(bucket:"example-bucket")
-  |> range(start: 2018-05-22T23:30:00Z, stop: 2018-05-23T00:00:00Z)
-  // ...
+from(bucket: "example-bucket")
+    |> range(start: 2018-05-22T23:30:00Z, stop: 2018-05-23T00:00:00Z)
+    // ...
 ```
 
 #### Absolute time range with Unix timestamps
 ```js
-from(bucket:"example-bucket")
-  |> range(start: 1527031800, stop: 1527033600)
-  // ...
+from(bucket: "example-bucket")
+    |> range(start: 1527031800, stop: 1527033600)
+    // ...
 ```
diff --git a/content/flux/v0.x/stdlib/universe/reduce.md b/content/flux/v0.x/stdlib/universe/reduce.md
index 9c3ad1bea..26a5d1d2b 100644
--- a/content/flux/v0.x/stdlib/universe/reduce.md
+++ b/content/flux/v0.x/stdlib/universe/reduce.md
@@ -28,7 +28,7 @@ _`reduce()` is an [aggregate function](/flux/v0.x/function-types/#aggregates)._
 ```js
 reduce(
     fn: (r, accumulator) => ({ sum: r._value + accumulator.sum }),
-    identity: {sum: 0.0}
+    identity: {sum: 0.0},
 )
 ```
 
@@ -109,7 +109,7 @@ import "sampledata"
 sampledata.int()
     |> reduce(
         fn: (r, accumulator) => ({sum: r._value + accumulator.sum}),
-        identity: {sum: 0}
+        identity: {sum: 0},
     )
 ```
 
@@ -182,10 +182,7 @@ sampledata.int()
 import "sampledata"
 
 sampledata.int()
-    |> reduce(
-        fn: (r, accumulator) => ({prod: r._value * accumulator.prod}),
-        identity: {prod: 1}        
-    )
+    |> reduce(fn: (r, accumulator) => ({prod: r._value * accumulator.prod}), identity: {prod: 1})
 ```
 
 {{< expand-wrapper >}}
@@ -219,12 +216,12 @@ import "sampledata"
 
 sampledata.int()
     |> reduce(
-      fn: (r, accumulator) => ({
-        count: accumulator.count + 1,
-        total: accumulator.total + r._value,
-        avg: float(v: (accumulator.total + r._value)) / float(v: accumulator.count + 1)
-      }),
-      identity: {count: 0, total: 0, avg: 0.0}
+        fn: (r, accumulator) => ({
+            count: accumulator.count + 1,
+            total: accumulator.total + r._value,
+            avg: float(v: (accumulator.total + r._value)) / float(v: accumulator.count + 1)
+        }),
+        identity: {count: 0, total: 0, avg: 0.0},
     )
 ```
 
diff --git a/content/flux/v0.x/stdlib/universe/relativestrengthindex.md b/content/flux/v0.x/stdlib/universe/relativestrengthindex.md
index 5c582e391..33fbcfc1d 100644
--- a/content/flux/v0.x/stdlib/universe/relativestrengthindex.md
+++ b/content/flux/v0.x/stdlib/universe/relativestrengthindex.md
@@ -27,8 +27,8 @@ values in an input table.
 
 ```js
 relativeStrengthIndex(
-  n: 5,
-  columns: ["_value"]
+    n: 5,
+    columns: ["_value"],
 )
 ```
 
@@ -67,7 +67,7 @@ with `x - n` rows.
 import "sampledata"
 
 sampledata.int()
-  |> relativeStrengthIndex(n: 3)
+    |> relativeStrengthIndex(n: 3)
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/universe/rename.md b/content/flux/v0.x/stdlib/universe/rename.md
index 9daa938f4..a25a56ae5 100644
--- a/content/flux/v0.x/stdlib/universe/rename.md
+++ b/content/flux/v0.x/stdlib/universe/rename.md
@@ -63,7 +63,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> rename(columns: {tag: "uid", _value: "val"})
+    |> rename(columns: {tag: "uid", _value: "val"})
 ```
 
 {{< expand-wrapper >}}
@@ -107,7 +107,7 @@ sampledata.int()
 import "sampledata"
 
 sampledata.int()
-  |> rename(fn: (column) => "${column}_new")
+    |> rename(fn: (column) => "${column}_new")
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/universe/sample.md b/content/flux/v0.x/stdlib/universe/sample.md
index d3ac0ef36..2e9b4bd51 100644
--- a/content/flux/v0.x/stdlib/universe/sample.md
+++ b/content/flux/v0.x/stdlib/universe/sample.md
@@ -52,7 +52,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> sample(n: 2, pos: 1)
+    |> sample(n: 2, pos: 1)
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/universe/set.md b/content/flux/v0.x/stdlib/universe/set.md
index 03320a50a..2cfe24b27 100644
--- a/content/flux/v0.x/stdlib/universe/set.md
+++ b/content/flux/v0.x/stdlib/universe/set.md
@@ -44,7 +44,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> set(key: "host", value: "prod1")
+    |> set(key: "host", value: "prod1")
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/universe/skew.md b/content/flux/v0.x/stdlib/universe/skew.md
index 312d78a31..c6247f9a3 100644
--- a/content/flux/v0.x/stdlib/universe/skew.md
+++ b/content/flux/v0.x/stdlib/universe/skew.md
@@ -43,7 +43,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> skew()
+    |> skew()
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/universe/sleep.md b/content/flux/v0.x/stdlib/universe/sleep.md
index 02a908c75..0f94c3c42 100644
--- a/content/flux/v0.x/stdlib/universe/sleep.md
+++ b/content/flux/v0.x/stdlib/universe/sleep.md
@@ -17,10 +17,7 @@ The `sleep()` function was removed in **Flux 0.123.0**.
 The `sleep()` function delays execution by a specified duration.
 
 ```js
-sleep(
-  v: x,
-  duration: 10s
-)
+sleep(v: x, duration: 10s)
 ```
 
 ## Parameters
@@ -40,8 +37,8 @@ Length of time to delay execution.
 ### Delay execution in a chained query
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> sleep(duration: 10s)
+    |> range(start: -1h)
+    |> sleep(duration: 10s)
 ```
 
 ### Delay execution using a stream variable
diff --git a/content/flux/v0.x/stdlib/universe/sort.md b/content/flux/v0.x/stdlib/universe/sort.md
index 47d38d537..c02402d2c 100644
--- a/content/flux/v0.x/stdlib/universe/sort.md
+++ b/content/flux/v0.x/stdlib/universe/sort.md
@@ -57,7 +57,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> sort()
+    |> sort()
 ```
 
 {{< expand-wrapper >}}
@@ -99,7 +99,7 @@ sampledata.int()
 import "sampledata"
 
 sampledata.int()
-  |> sort(desc: true)
+    |> sort(desc: true)
 ```
 
 {{< expand-wrapper >}}
@@ -141,7 +141,7 @@ sampledata.int()
 import "sampledata"
 
 sampledata.int()
-  |> sort(columns: ["tag", "_value"])
+    |> sort(columns: ["tag", "_value"])
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/universe/spread.md b/content/flux/v0.x/stdlib/universe/spread.md
index 5ad364e15..777f3baad 100644
--- a/content/flux/v0.x/stdlib/universe/spread.md
+++ b/content/flux/v0.x/stdlib/universe/spread.md
@@ -48,7 +48,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> spread()
+    |> spread()
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/universe/statecount.md b/content/flux/v0.x/stdlib/universe/statecount.md
index 3b2d561bb..65f418cc1 100644
--- a/content/flux/v0.x/stdlib/universe/statecount.md
+++ b/content/flux/v0.x/stdlib/universe/statecount.md
@@ -59,7 +59,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> stateCount(fn: (r) => r._value > 10)
+    |> stateCount(fn: (r) => r._value > 10)
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/universe/stateduration.md b/content/flux/v0.x/stdlib/universe/stateduration.md
index 6e76ff8c4..fa544e4e8 100644
--- a/content/flux/v0.x/stdlib/universe/stateduration.md
+++ b/content/flux/v0.x/stdlib/universe/stateduration.md
@@ -18,12 +18,17 @@ related:
 introduced: 0.7.0
 ---
 
-The `stateDuration()` function computes the duration of a given state.
-The state is defined via the function `fn`.
-For each consecutive point for that evaluates as `true`, the state duration will be
-incremented by the duration between points.
-When a point evaluates as `false`, the state duration is reset.
+`stateDuration()` returns the cumulative duration of a given state.
+
+The state is defined by the `fn` predicate function. For each consecutive
+record that evaluates to `true`, the state duration is incremented by the
+duration of time between records using the specified `unit`. When a record
+evaluates to `false`, the value is set to `-1` and the state duration is reset.
+If the record generates an error during evaluation, the point is discarded,
+and does not affect the state duration.
+
 The state duration is added as an additional column to each record.
+The duration is represented as an integer in the units specified.
 
 {{% note %}}
 As the first point in the given state has no previous point, its
@@ -71,7 +76,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> stateDuration(fn: (r) => r._value > 10)
+    |> stateDuration(fn: (r) => r._value > 10)
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/universe/stddev.md b/content/flux/v0.x/stdlib/universe/stddev.md
index 8f06f42ab..1c8df9fb9 100644
--- a/content/flux/v0.x/stdlib/universe/stddev.md
+++ b/content/flux/v0.x/stdlib/universe/stddev.md
@@ -24,10 +24,7 @@ _`stddev()` is an [aggregate function](/flux/v0.x/function-types/#aggregates)._
 _**Output data type:** Float_
 
 ```js
-stddev(
-  column: "_value",
-  mode: "sample"
-)
+stddev(column: "_value", mode: "sample")
 ```
 
 ## Parameters
@@ -59,7 +56,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> stddev()
+    |> stddev()
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/universe/string.md b/content/flux/v0.x/stdlib/universe/string.md
index 7bbda8558..7fa3466ec 100644
--- a/content/flux/v0.x/stdlib/universe/string.md
+++ b/content/flux/v0.x/stdlib/universe/string.md
@@ -18,8 +18,6 @@ introduced: 0.7.0
 
 The `string()` function converts a single value to a string.
 
-_**Output data type:** String_
-
 ```js
 string(v: 123456789)
 ```
@@ -78,10 +76,10 @@ _The following example uses data provided by the [`sampledata` package](/flux/v0
 import "sampledata"
 
 data = sampledata.int()
-  |> rename(columns: {_value: "foo"})
+    |> rename(columns: {_value: "foo"})
 
 data
-  |> map(fn:(r) => ({ r with foo: string(v: r.foo) }))
+    |> map(fn: (r) => ({r with foo: string(v: r.foo)}))
 ```
 
 {{% expand "View input and output" %}}
diff --git a/content/flux/v0.x/stdlib/universe/sum.md b/content/flux/v0.x/stdlib/universe/sum.md
index b628e0d68..2b8023c4a 100644
--- a/content/flux/v0.x/stdlib/universe/sum.md
+++ b/content/flux/v0.x/stdlib/universe/sum.md
@@ -42,7 +42,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> sum()
+    |> sum()
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/universe/tail.md b/content/flux/v0.x/stdlib/universe/tail.md
index 7021e008b..a27622aa2 100644
--- a/content/flux/v0.x/stdlib/universe/tail.md
+++ b/content/flux/v0.x/stdlib/universe/tail.md
@@ -22,10 +22,7 @@ Each output table contains the last `n` records before the [`offset`](#offset).
 If the input table has less than `offset + n` records, `tail()` outputs all records before the `offset`.
 
 ```js
-tail(
-  n:10,
-  offset: 0
-)
+tail(n: 10, offset: 0)
 ```
 
 ## Parameters
@@ -53,7 +50,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> tail(n: 3)
+    |> tail(n: 3)
 ```
 
 {{< expand-wrapper >}}
@@ -89,7 +86,7 @@ sampledata.int()
 import "sampledata"
 
 sampledata.int()
-  |> tail(n: 3, offset: 1)
+    |> tail(n: 3, offset: 1)
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/universe/time.md b/content/flux/v0.x/stdlib/universe/time.md
index e69b8eb27..65a6a94d8 100644
--- a/content/flux/v0.x/stdlib/universe/time.md
+++ b/content/flux/v0.x/stdlib/universe/time.md
@@ -66,11 +66,11 @@ To update values in columns other than `_value`:
 import "sampledata"
 
 data = sampledata.int()
-  |> map(fn: (r) => ({ r with _value: r._value * 1000000000 }))
-  |> rename(columns: {_value: "foo"})
+    |> map(fn: (r) => ({r with _value: r._value * 1000000000}))
+    |> rename(columns: {_value: "foo"})
 
 data
-  |> map(fn:(r) => ({ r with foo: time(v: r.foo) }))
+    |> map(fn: (r) => ({r with foo: time(v: r.foo)}))
 ```
 
 {{% expand "View input and output" %}}
diff --git a/content/flux/v0.x/stdlib/universe/timedmovingaverage.md b/content/flux/v0.x/stdlib/universe/timedmovingaverage.md
index c78f4073b..17330bec9 100644
--- a/content/flux/v0.x/stdlib/universe/timedmovingaverage.md
+++ b/content/flux/v0.x/stdlib/universe/timedmovingaverage.md
@@ -29,9 +29,9 @@ range at a specified frequency.
 
 ```js
 timedMovingAverage(
-  every: 1d,
-  period: 5d,
-  column: "_value"
+    every: 1d,
+    period: 5d,
+    column: "_value",
 )
 ```
 
@@ -81,20 +81,13 @@ to generate sample data and illustrate how `timedMovingAverage()` transforms dat
 
 #### Calculate a five year moving average every year
 ```js
-import "generate"
-
 timeRange = {start: 2015-01-01T00:00:00Z, stop: 2021-01-01T00:00:00Z}
 
-data = generate.from(
-    count: 6,
-    fn: (n) => n * n,
-    start: timeRange.start,
-    stop: timeRange.stop
-  )
-  |> range(start: timeRange.start, stop: timeRange.stop)
+data = generate.from(count: 6, fn: (n) => n * n, start: timeRange.start, stop: timeRange.stop)
+    |> range(start: timeRange.start, stop: timeRange.stop)
 
 data
-  |> timedMovingAverage(every: 1y, period: 5y)
+    |> timedMovingAverage(every: 1y, period: 5y)
 ```
 
 {{< expand-wrapper >}}
@@ -132,16 +125,11 @@ import "generate"
 
 timeRange = {start: 2021-01-01T00:00:00Z, stop: 2021-01-08T00:00:00Z}
 
-data = generate.from(
-    count: 7,
-    fn: (n) => n + n,
-    start: timeRange.start,
-    stop: timeRange.stop
-  )
-  |> range(start: timeRange.start, stop: timeRange.stop)
+data = generate.from(count: 7, fn: (n) => n + n, start: timeRange.start, stop: timeRange.stop)
+    |> range(start: timeRange.start, stop: timeRange.stop)
 
 data
-  |> timedMovingAverage(every: 1d, period: 7d)
+    |> timedMovingAverage(every: 1d, period: 7d)
 ```
 
 {{< expand-wrapper >}}
@@ -176,13 +164,3 @@ data
 
 {{% /expand %}}
 {{< /expand-wrapper >}}
-
-## Function definition
-```js
-timedMovingAverage = (every, period, column="_value", tables=<-) =>
-  tables
-    |> window(every: every, period: period)
-    |> mean(column:column)
-    |> duplicate(column: "_stop", as: "_time")
-    |> window(every: inf)
-```
diff --git a/content/flux/v0.x/stdlib/universe/timeshift.md b/content/flux/v0.x/stdlib/universe/timeshift.md
index 82780a20c..0d2d39a65 100644
--- a/content/flux/v0.x/stdlib/universe/timeshift.md
+++ b/content/flux/v0.x/stdlib/universe/timeshift.md
@@ -50,7 +50,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> timeShift(duration: 12h)
+    |> timeShift(duration: 12h)
 ```
 
 {{< expand-wrapper >}}
@@ -92,7 +92,7 @@ sampledata.int()
 import "sampledata"
 
 sampledata.int()
-  |> timeShift(duration: -12h)
+    |> timeShift(duration: -12h)
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/universe/timeweightedavg.md b/content/flux/v0.x/stdlib/universe/timeweightedavg.md
index 8c4194f3a..052a08120 100644
--- a/content/flux/v0.x/stdlib/universe/timeweightedavg.md
+++ b/content/flux/v0.x/stdlib/universe/timeweightedavg.md
@@ -42,12 +42,12 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 data = sampledata.int(includeNull: true)
-  |> range(start: sampledata.start, stop: sampledata.stop)
-  |> fill(usePrevious: true)
-  |> unique()
+    |> range(start: sampledata.start, stop: sampledata.stop)
+    |> fill(usePrevious: true)
+    |> unique()
 
 data
-  |> timeWeightedAvg(unit: 1s)
+    |> timeWeightedAvg(unit: 1s)
 ```
 
 {{< expand-wrapper >}}
@@ -78,16 +78,3 @@ data
 
 {{% /expand %}}
 {{< /expand-wrapper >}}
-
-## Function definition
-```js
-timeWeightedAvg = (tables=<-, unit) => tables
-  |> integral(
-    unit: unit,
-    interpolate: "linear"
-  )
-  |> map(fn: (r) => ({
-    r with
-    _value: (r._value * float(v: uint(v: unit))) / float(v: int(v: r._stop) - int(v: r._start))
-  }))
-```
diff --git a/content/flux/v0.x/stdlib/universe/tobool.md b/content/flux/v0.x/stdlib/universe/tobool.md
index ead850931..9591c4d7f 100644
--- a/content/flux/v0.x/stdlib/universe/tobool.md
+++ b/content/flux/v0.x/stdlib/universe/tobool.md
@@ -51,7 +51,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.numericBool()
-  |> toBool()
+    |> toBool()
 ```
 
 {{< expand-wrapper >}}
@@ -87,10 +87,3 @@ sampledata.numericBool()
 {{< /flex >}}
 {{% /expand %}}
 {{< /expand-wrapper >}}
-
-## Function definition
-```js
-toBool = (tables=<-) =>
-  tables
-    |> map(fn:(r) => ({ r with _value: bool(v: r._value) }))
-```
diff --git a/content/flux/v0.x/stdlib/universe/today.md b/content/flux/v0.x/stdlib/universe/today.md
index ce36c7d44..e17fc1a94 100644
--- a/content/flux/v0.x/stdlib/universe/today.md
+++ b/content/flux/v0.x/stdlib/universe/today.md
@@ -37,5 +37,5 @@ today()
 ##### Query data from today
 ```js
 from(bucket: "example-bucket")
-  |> range(start: today())
+    |> range(start: today())
 ```
diff --git a/content/flux/v0.x/stdlib/universe/tofloat.md b/content/flux/v0.x/stdlib/universe/tofloat.md
index d2effe351..f254a0e8a 100644
--- a/content/flux/v0.x/stdlib/universe/tofloat.md
+++ b/content/flux/v0.x/stdlib/universe/tofloat.md
@@ -55,7 +55,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> toFloat()
+    |> toFloat()
 ```
 
 {{< expand-wrapper >}}
@@ -97,7 +97,7 @@ sampledata.int()
 import "sampledata"
 
 sampledata.bool()
-  |> toFloat()
+    |> toFloat()
 ```
 
 {{< expand-wrapper >}}
@@ -133,10 +133,3 @@ sampledata.bool()
 {{< /flex >}}
 {{% /expand %}}
 {{< /expand-wrapper >}}
-
-## Function definition
-```js
-toFloat = (tables=<-) =>
-  tables
-    |> map(fn:(r) => ({ r with _value: float(v: r._value) }))
-```
diff --git a/content/flux/v0.x/stdlib/universe/toint.md b/content/flux/v0.x/stdlib/universe/toint.md
index 2b3ab6132..884abb273 100644
--- a/content/flux/v0.x/stdlib/universe/toint.md
+++ b/content/flux/v0.x/stdlib/universe/toint.md
@@ -68,7 +68,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.float()
-  |> toInt()
+    |> toInt()
 ```
 
 {{< expand-wrapper >}}
@@ -110,7 +110,7 @@ sampledata.float()
 import "sampledata"
 
 sampledata.bool()
-  |> toInt()
+    |> toInt()
 ```
 
 {{< expand-wrapper >}}
@@ -137,7 +137,7 @@ sampledata.bool()
 import "sampledata"
 
 sampledata.uint()
-  |> toInt()
+    |> toInt()
 ```
 
 {{< expand-wrapper >}}
@@ -173,10 +173,3 @@ sampledata.uint()
 {{< /flex >}}
 {{% /expand %}}
 {{< /expand-wrapper >}}
-
-## Function definition
-```js
-toInt = (tables=<-) =>
-  tables
-    |> map(fn:(r) => ({ r with _value: int(v: r._value) }))
-```
diff --git a/content/flux/v0.x/stdlib/universe/top.md b/content/flux/v0.x/stdlib/universe/top.md
index 2b6e4b9dd..c80c336c5 100644
--- a/content/flux/v0.x/stdlib/universe/top.md
+++ b/content/flux/v0.x/stdlib/universe/top.md
@@ -50,7 +50,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> top(n: 3)
+    |> top(n: 3)
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/universe/tostring.md b/content/flux/v0.x/stdlib/universe/tostring.md
index 534b17a8e..7e66cadc8 100644
--- a/content/flux/v0.x/stdlib/universe/tostring.md
+++ b/content/flux/v0.x/stdlib/universe/tostring.md
@@ -51,7 +51,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.float()
-  |> toString()
+    |> toString()
 ```
 
 {{< expand-wrapper >}}
@@ -87,10 +87,3 @@ sampledata.float()
 {{< /flex >}}
 {{% /expand %}}
 {{< /expand-wrapper >}}
-
-## Function definition
-```js
-toString = (tables=<-) =>
-  tables
-    |> map(fn:(r) => ({ r with _value: string(v: r._value) }))
-```
diff --git a/content/flux/v0.x/stdlib/universe/totime.md b/content/flux/v0.x/stdlib/universe/totime.md
index 20419f704..84da81cd9 100644
--- a/content/flux/v0.x/stdlib/universe/totime.md
+++ b/content/flux/v0.x/stdlib/universe/totime.md
@@ -54,10 +54,10 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 data = sampledata.int()
-  |> map(fn: (r) => ({ r with _value: r._value * 1000000000 }))
+    |> map(fn: (r) => ({r with _value: r._value * 1000000000}))
 
 data
-  |> toTime()
+    |> toTime()
 ```
 
 {{< expand-wrapper >}}
@@ -107,10 +107,3 @@ data
 {{< /flex >}}
 {{% /expand %}}
 {{< /expand-wrapper >}}
-
-## Function definition
-```js
-toTime = (tables=<-) =>
-  tables
-    |> map(fn:(r) => ({ r with _value: time(v:r._value) }))
-```
diff --git a/content/flux/v0.x/stdlib/universe/touint.md b/content/flux/v0.x/stdlib/universe/touint.md
index e3d63c6bb..501924652 100644
--- a/content/flux/v0.x/stdlib/universe/touint.md
+++ b/content/flux/v0.x/stdlib/universe/touint.md
@@ -68,7 +68,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.float()
-  |> toUInt()
+    |> toUInt()
 ```
 
 {{< expand-wrapper >}}
@@ -95,7 +95,7 @@ sampledata.float()
 import "sampledata"
 
 sampledata.bool()
-  |> toUInt()
+    |> toUInt()
 ```
 
 {{< expand-wrapper >}}
@@ -122,7 +122,7 @@ sampledata.bool()
 import "sampledata"
 
 sampledata.uint()
-  |> toUInt()
+    |> toUInt()
 ```
 
 {{< expand-wrapper >}}
@@ -143,9 +143,3 @@ sampledata.uint()
 {{< /flex >}}
 {{% /expand %}}
 {{< /expand-wrapper >}}
-
-## Function definition
-```js
-toUInt = (tables=<-) => tables
-  |> map(fn:(r) => ({ r with _value: uint(v:r._value) }))
-```
diff --git a/content/flux/v0.x/stdlib/universe/tripleema.md b/content/flux/v0.x/stdlib/universe/tripleema.md
index af2cc71ad..d2a16daac 100644
--- a/content/flux/v0.x/stdlib/universe/tripleema.md
+++ b/content/flux/v0.x/stdlib/universe/tripleema.md
@@ -61,7 +61,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> tripleEMA(n: 3)
+    |> tripleEMA(n: 3)
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/universe/tripleexponentialderivative.md b/content/flux/v0.x/stdlib/universe/tripleexponentialderivative.md
index f58799738..0de7f3194 100644
--- a/content/flux/v0.x/stdlib/universe/tripleexponentialderivative.md
+++ b/content/flux/v0.x/stdlib/universe/tripleexponentialderivative.md
@@ -72,7 +72,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.float()
-  |> tripleExponentialDerivative(n: 2)
+    |> tripleExponentialDerivative(n: 2)
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/universe/truncatetimecolumn.md b/content/flux/v0.x/stdlib/universe/truncatetimecolumn.md
index 478101881..8ab9781bc 100644
--- a/content/flux/v0.x/stdlib/universe/truncatetimecolumn.md
+++ b/content/flux/v0.x/stdlib/universe/truncatetimecolumn.md
@@ -52,10 +52,10 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 data = sampledata.int()
-  |> range(start: sampledata.start, stop: sampledata.stop)
+    |> range(start: sampledata.start, stop: sampledata.stop)
 
 data
-  |> truncateTimeColumn(unit: 1m)
+    |> truncateTimeColumn(unit: 1m)
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/universe/uint.md b/content/flux/v0.x/stdlib/universe/uint.md
index a2c5b773f..54ab3b0ce 100644
--- a/content/flux/v0.x/stdlib/universe/uint.md
+++ b/content/flux/v0.x/stdlib/universe/uint.md
@@ -19,8 +19,6 @@ introduced: 0.7.0
 
 The `uint()` function converts a single value to a UInteger.
 
-_**Output data type:** UInteger_
-
 ```js
 uint(v: "4")
 ```
@@ -98,10 +96,10 @@ _The following example uses data provided by the [`sampledata` package](/flux/v0
 import "sampledata"
 
 data = sampledata.float()
-  |> rename(columns: {_value: "foo"})
+    |> rename(columns: {_value: "foo"})
 
 data
-  |> map(fn:(r) => ({ r with foo: uint(v: r.foo) }))
+    |> map(fn: (r) => ({r with foo: uint(v: r.foo)}))
 ```
 
 {{% expand "View input and output" %}}
diff --git a/content/flux/v0.x/stdlib/universe/union.md b/content/flux/v0.x/stdlib/universe/union.md
index c37a4ad71..ad7797a92 100644
--- a/content/flux/v0.x/stdlib/universe/union.md
+++ b/content/flux/v0.x/stdlib/universe/union.md
@@ -247,10 +247,7 @@ union(tables: [t1, t2])
 
 #### join() output
 ```js
-join(
-    tables: {t1: t1, t2: t2},
-    on: ["_time", "tag"],
-)
+join(tables: {t1: t1, t2: t2}, on: ["_time", "tag"])
 ```
 
 | _time                | tag | _value_t1 | _value_t2 |
diff --git a/content/flux/v0.x/stdlib/universe/unique.md b/content/flux/v0.x/stdlib/universe/unique.md
index d97dde979..b365e0a2f 100644
--- a/content/flux/v0.x/stdlib/universe/unique.md
+++ b/content/flux/v0.x/stdlib/universe/unique.md
@@ -45,7 +45,7 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 sampledata.int()
-  |> unique()
+    |> unique()
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/universe/window.md b/content/flux/v0.x/stdlib/universe/window.md
index 2dbcbc09e..c35e179e5 100644
--- a/content/flux/v0.x/stdlib/universe/window.md
+++ b/content/flux/v0.x/stdlib/universe/window.md
@@ -29,14 +29,14 @@ the parameters passed into the `window()` function.
 
 ```js
 window(
-  every: 5m,
-  period: 5m,
-  offset: 12h,
-  timeColumn: "_time",
-  startColumn: "_start",
-  stopColumn: "_stop",
-  location: "UTC",
-  createEmpty: false
+    every: 5m,
+    period: 5m,
+    offset: 12h,
+    timeColumn: "_time",
+    startColumn: "_start",
+    stopColumn: "_stop",
+    location: "UTC",
+    createEmpty: false,
 )
 ```
 
@@ -107,10 +107,10 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 import "sampledata"
 
 data = sampledata.int()
-  |> range(start: sampledata.start, stop: sampledata.stop)
- 
-data 
-  |> window(every: 30s)
+    |> range(start: sampledata.start, stop: sampledata.stop)
+
+data
+    |> window(every: 30s)
 ```
 
 {{< expand-wrapper >}}
@@ -152,10 +152,10 @@ data
 import "sampledata"
 
 data = sampledata.int()
-  |> range(start: sampledata.start, stop: sampledata.stop)
- 
-data 
-  |> window(every: 20s, period: 40s)
+    |> range(start: sampledata.start, stop: sampledata.stop)
+
+data
+    |> window(every: 20s, period: 40s)
 ```
 
 {{< expand-wrapper >}}
@@ -225,16 +225,11 @@ import "generate"
 
 timeRange = {start: 2021-01-01T00:00:00Z, stop: 2021-04-01T00:00:00Z}
 
-data = generate.from(
-    count: 6,
-    fn: (n) => n + n,
-    start: timeRange.start,
-    stop: timeRange.stop
-  )
-  |> range(start: timeRange.start, stop: timeRange.stop)
+data = generate.from(count: 6, fn: (n) => n + n, start: timeRange.start, stop: timeRange.stop)
+    |> range(start: timeRange.start, stop: timeRange.stop)
 
 data
-  |> window(every: 1mo)
+    |> window(every: 1mo)
 ```
 
 {{< expand-wrapper >}}
diff --git a/content/flux/v0.x/stdlib/universe/yield.md b/content/flux/v0.x/stdlib/universe/yield.md
index e7bff9241..3a49daf26 100644
--- a/content/flux/v0.x/stdlib/universe/yield.md
+++ b/content/flux/v0.x/stdlib/universe/yield.md
@@ -43,6 +43,6 @@ Default is piped-forward data ([`<-`](/flux/v0.x/spec/expressions/#pipe-expressi
 ## Examples
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -5m)
-  |> yield(name: "1")
+    |> range(start: -5m)
+    |> yield(name: "result-name")
 ```
diff --git a/content/flux/v0.x/write-data/influxdb.md b/content/flux/v0.x/write-data/influxdb.md
index 94fc19e57..d74c9a4af 100644
--- a/content/flux/v0.x/write-data/influxdb.md
+++ b/content/flux/v0.x/write-data/influxdb.md
@@ -16,7 +16,7 @@ related:
 list_code_example: |
   ```js
   data
-    |> to(bucket: "example-bucket")
+      |> to(bucket: "example-bucket")
   ```
 ---
 
@@ -82,30 +82,24 @@ m,id=001,loc=SF temp=71.2,hum=52.8 1609466400000000000
 {{% code-tab-content %}}
 ```js
 data
-  |> to(
-    bucket: "example-bucket"
-  )
+    |> to(bucket: "example-bucket")
 ```
 {{% /code-tab-content %}}
 {{% code-tab-content %}}
 ```js
 data
-  |> to(
-    bucket: "example-bucket",
-    org: "example-org",
-    token: "mY5uPeRs3Cre7tok3N"
-  )
+    |> to(bucket: "example-bucket", org: "example-org", token: "mY5uPeRs3Cre7tok3N")
 ```
 {{% /code-tab-content %}}
 {{% code-tab-content %}}
 ```js
 data
-  |> to(
-    bucket: "example-bucket",
-    org: "example-org",
-    token: "mY5uPeRs3Cre7tok3N",
-    host: "https://myinfluxdbdomain.com/8086"
-  )
+    |> to(
+        bucket: "example-bucket",
+        org: "example-org",
+        token: "mY5uPeRs3Cre7tok3N",
+        host: "https://myinfluxdbdomain.com/8086",
+    )
 ```
 {{% /code-tab-content %}}
 {{< /code-tabs-wrapper >}}
@@ -137,7 +131,7 @@ Columns **not in the group key** are written to InfluxDB as [fields](/{{< latest
 import "experimental"
 
 data
-  |> experimental.to(bucket: "example-bucket")
+    |> experimental.to(bucket: "example-bucket")
 ```
 
 Given the following input [stream of tables](/flux/v0.x/get-started/data-model/#stream-of-tables):
@@ -181,9 +175,7 @@ m,id=001,loc=BK min=5i,max=3i,mean=6.5 1609466400000000000
 import "experimental"
 
 data
-  |> experimental.to(
-    bucket: "example-bucket"
-  )
+    |> experimental.to(bucket: "example-bucket")
 ```
 {{% /code-tab-content %}}
 {{% code-tab-content %}}
@@ -191,11 +183,7 @@ data
 import "experimental"
 
 data
-  |> experimental.to(
-    bucket: "example-bucket",
-    org: "example-org",
-    token: "mY5uPeRs3Cre7tok3N"
-  )
+    |> experimental.to(bucket: "example-bucket", org: "example-org", token: "mY5uPeRs3Cre7tok3N")
 ```
 {{% /code-tab-content %}}
 {{% code-tab-content %}}
@@ -203,12 +191,12 @@ data
 import "experimental"
 
 data
-  |> experimental.to(
-    bucket: "example-bucket",
-    org: "example-org",
-    token: "mY5uPeRs3Cre7tok3N",
-    host: "https://myinfluxdbdomain.com/8086"
-  )
+    |> experimental.to(
+        bucket: "example-bucket",
+        org: "example-org",
+        token: "mY5uPeRs3Cre7tok3N",
+        host: "https://myinfluxdbdomain.com/8086",
+    )
 ```
 {{% /code-tab-content %}}
 {{< /code-tabs-wrapper >}}
diff --git a/content/flux/v0.x/write-data/sql/_index.md b/content/flux/v0.x/write-data/sql/_index.md
index 2c9dcf2c9..506e0f7a6 100644
--- a/content/flux/v0.x/write-data/sql/_index.md
+++ b/content/flux/v0.x/write-data/sql/_index.md
@@ -14,12 +14,12 @@ related:
 list_code_example: |
   ```js
   import "sql"
-  
+
   sql.to(
-    driverName: "postgres",
-    dataSourceName: "postgresql://user:password@localhost",
-    table: "ExampleTable",
-    batchSize: 10000
+      driverName: "postgres",
+      dataSourceName: "postgresql://user:password@localhost",
+      table: "ExampleTable",
+      batchSize: 10000,
   )
   ```
 ---
@@ -71,9 +71,9 @@ username = secrets.get(key: "POSTGRES_USER")
 password = secrets.get(key: "POSTGRES_PASS")
 
 sql.to(
-  driverName: "postgres",
-  dataSourceName: "postgresql://${username}:${password}@localhost:5432",
-  table: "example_table"
+    driverName: "postgres",
+    dataSourceName: "postgresql://${username}:${password}@localhost:5432",
+    table: "example_table",
 )
 ```
 
@@ -106,21 +106,16 @@ Given the following following [stream of tables](/flux/v0.x/get-started/data-mod
 | 2021-01-01T00:00:10Z | t2  |      4 |
 | 2021-01-01T00:00:20Z | t2  |     -3 |
 
-##### Flux query
+##### Flux script
 ```js
 import "sql"
 
 data
-  |> sql.from(
-    driver: "mysql",
-    dataSourceName: "username:passwOrd@tcp(localhost:3306)/db",
-    table: "exampleTable"
-  )
-```
-
-##### SQL Query
-```sql
-SELECT * FROM exampleTable
+    |> sql.to(
+        driver: "mysql",
+        dataSourceName: "username:passwOrd@tcp(localhost:3306)/db",
+        table: "exampleTable"
+    )
 ```
 
 ##### SQL output
diff --git a/content/flux/v0.x/write-data/sql/amazon-rds.md b/content/flux/v0.x/write-data/sql/amazon-rds.md
index a3fc10f40..80934627d 100644
--- a/content/flux/v0.x/write-data/sql/amazon-rds.md
+++ b/content/flux/v0.x/write-data/sql/amazon-rds.md
@@ -15,13 +15,13 @@ related:
 list_code_example: |
   ```js
   import "sql"
-  
+
   data
-    |> sql.to(
-      driverName: "snowflake",
-      dataSourceName: "postgresql://my-instance.123456789012.us-east-1.rds.amazonaws.com:5432",
-      query: "SELECT * FROM example_table"
-    )
+      |> sql.to(
+          driverName: "postgres",
+          dataSourceName: "postgresql://my-instance.123456789012.us-east-1.rds.amazonaws.com:5432",
+          table: "example_table",
+      )
   ```
 ---
 
@@ -43,11 +43,11 @@ with Flux:
 import "sql"
 
 data
-  |> sql.to(
-    driverName: "postgres",
-    dataSourceName: "postgresql://my-instance.123456789012.us-east-1.rds.amazonaws.com:5432",
-    table: "example_table"
-  )
+    |> sql.to(
+        driverName: "postgres",
+        dataSourceName: "postgresql://my-instance.123456789012.us-east-1.rds.amazonaws.com:5432",
+        table: "example_table",
+    )
 ```
 
 ## Supported database engines
diff --git a/content/flux/v0.x/write-data/sql/bigquery.md b/content/flux/v0.x/write-data/sql/bigquery.md
index fd5589e87..99cc6caec 100644
--- a/content/flux/v0.x/write-data/sql/bigquery.md
+++ b/content/flux/v0.x/write-data/sql/bigquery.md
@@ -17,11 +17,11 @@ list_code_example: |
   import "sql"
 
   data
-    |> sql.from(
-      driverName: "bigquery",
-      dataSourceName: "bigquery://projectid/?apiKey=mySuP3r5ecR3tAP1K3y",
-      query: "SELECT * FROM exampleTable"
-    )
+      |> sql.to(
+          driverName: "bigquery",
+          dataSourceName: "bigquery://projectid/?apiKey=mySuP3r5ecR3tAP1K3y",
+          table: "exampleTable",
+      )
   ```
 ---
 
@@ -41,11 +41,11 @@ To write data to [Google BigQuery](https://cloud.google.com/bigquery) with Flux:
 import "sql"
 
 data
-  |> sql.to(
-    driverName: "bigquery",
-    dataSourceName: "bigquery://projectid/?apiKey=mySuP3r5ecR3tAP1K3y",
-    table: "exampleTable"
-  )
+    |> sql.to(
+        driverName: "bigquery",
+        dataSourceName: "bigquery://projectid/?apiKey=mySuP3r5ecR3tAP1K3y",
+        table: "exampleTable",
+    )
 ```
 
 ---
diff --git a/content/flux/v0.x/write-data/sql/cockroachdb.md b/content/flux/v0.x/write-data/sql/cockroachdb.md
index b0b50a9be..7a3cefeef 100644
--- a/content/flux/v0.x/write-data/sql/cockroachdb.md
+++ b/content/flux/v0.x/write-data/sql/cockroachdb.md
@@ -15,13 +15,14 @@ related:
 list_code_example: |
   ```js
   import "sql"
-  
+
   data
-    |> sql.to(
-      driverName: "postgres",
-      dataSourceName: "postgresql://username:password@localhost:26257/cluster_name.defaultdb?sslmode=verify-full&sslrootcert=certs_dir/cc-ca.crt",
-      table: "example_table"
-    )
+      |> sql.to(
+          driverName: "postgres",
+          dataSourceName:
+              "postgresql://username:password@localhost:26257/cluster_name.defaultdb?sslmode=verify-full&sslrootcert=certs_dir/cc-ca.crt",
+          table: "example_table",
+      )
   ```
 ---
 
@@ -41,11 +42,12 @@ To write data to [CockroachDB](https://www.cockroachlabs.com/) with Flux:
 import "sql"
 
 data
-  |> sql.to(
-    driverName: "postgres",
-    dataSourceName: "postgresql://username:password@localhost:26257/cluster_name.defaultdb?sslmode=verify-full&sslrootcert=certs_dir/cc-ca.crt",
-    table: "example_table"
-  )
+    |> sql.to(
+        driverName: "postgres",
+        dataSourceName:
+            "postgresql://username:password@localhost:26257/cluster_name.defaultdb?sslmode=verify-full&sslrootcert=certs_dir/cc-ca.crt",
+        table: "example_table",
+    )
 ```
 
 ---
diff --git a/content/flux/v0.x/write-data/sql/mariadb.md b/content/flux/v0.x/write-data/sql/mariadb.md
index 47180d600..5597e80cb 100644
--- a/content/flux/v0.x/write-data/sql/mariadb.md
+++ b/content/flux/v0.x/write-data/sql/mariadb.md
@@ -17,11 +17,11 @@ list_code_example: |
   import "sql"
   
   data
-    |> sql.to(
-      driverName: "mysql",
-      dataSourceName: "user:password@tcp(localhost:3306)/db",
-      table: "example_table"
-    )
+      |> sql.to(
+          driverName: "mysql",
+          dataSourceName: "user:password@tcp(localhost:3306)/db",
+          table: "example_table",
+      )
   ```
 ---
 
@@ -41,11 +41,11 @@ To write data to [MariaDB](https://mariadb.org/) with Flux:
 import "sql"
 
 data
-  |> sql.to(
-    driverName: "mysql",
-    dataSourceName: "user:password@tcp(localhost:3306)/db",
-    query: "SELECT * FROM example_table"
-  )
+    |> sql.to(
+        driverName: "mysql",
+        dataSourceName: "user:password@tcp(localhost:3306)/db",
+        query: "SELECT * FROM example_table",
+    )
 ```
 
 ---
diff --git a/content/flux/v0.x/write-data/sql/mysql.md b/content/flux/v0.x/write-data/sql/mysql.md
index 3da933471..fa21f6c9c 100644
--- a/content/flux/v0.x/write-data/sql/mysql.md
+++ b/content/flux/v0.x/write-data/sql/mysql.md
@@ -17,11 +17,11 @@ list_code_example: |
   import "sql"
   
   data
-    |> sql.to(
-      driverName: "mysql",
-      dataSourceName: "user:password@tcp(localhost:3306)/db",
-      table: "example_table"
-    )
+      |> sql.to(
+          driverName: "mysql",
+          dataSourceName: "user:password@tcp(localhost:3306)/db",
+          table: "example_table",
+      )
   ```
 ---
 
@@ -41,11 +41,11 @@ To write data to [MySQL](https://www.mysql.com/) with Flux:
 import "sql"
 
 data
-  |> sql.to(
-    driverName: "mysql",
-    dataSourceName: "user:password@tcp(localhost:3306)/db",
-    table: "example_table"
-  )
+    |> sql.to(
+        driverName: "mysql",
+        dataSourceName: "user:password@tcp(localhost:3306)/db",
+        table: "example_table",
+    )
 ```
 
 ---
diff --git a/content/flux/v0.x/write-data/sql/percona.md b/content/flux/v0.x/write-data/sql/percona.md
index 8d23c516d..db041182e 100644
--- a/content/flux/v0.x/write-data/sql/percona.md
+++ b/content/flux/v0.x/write-data/sql/percona.md
@@ -17,11 +17,11 @@ list_code_example: |
   import "sql"
   
   data
-    |> sql.to(
-      driverName: "mysql",
-      dataSourceName: "user:password@tcp(localhost:3306)/db",
-      table: "example_table"
-    )
+      |> sql.to(
+          driverName: "mysql",
+          dataSourceName: "user:password@tcp(localhost:3306)/db",
+          table: "example_table",
+      )
   ```
 ---
 
@@ -41,11 +41,11 @@ To write data to [Percona](https://www.percona.com/) with Flux:
 import "sql"
   
 data
-  |> sql.to(
-    driverName: "mysql",
-    dataSourceName: "user:password@tcp(localhost:3306)/db",
-    table: "example_table"
-  )
+    |> sql.to(
+        driverName: "mysql",
+        dataSourceName: "user:password@tcp(localhost:3306)/db",
+        table: "example_table",
+    )
 ```
 
 ---
diff --git a/content/flux/v0.x/write-data/sql/postgresql.md b/content/flux/v0.x/write-data/sql/postgresql.md
index b1d255a0e..58f65f826 100644
--- a/content/flux/v0.x/write-data/sql/postgresql.md
+++ b/content/flux/v0.x/write-data/sql/postgresql.md
@@ -41,11 +41,11 @@ To write data to [PostgreSQL](https://www.postgresql.org/) with Flux:
 import "sql"
   
 data
-  |> sql.to(
-    driverName: "postgres",
-    dataSourceName: "postgresql://username:password@localhost:5432",
-    table: "example_table"
-  )
+    |> sql.to(
+        driverName: "postgres",
+        dataSourceName: "postgresql://username:password@localhost:5432",
+        table: "example_table",
+    )
 ```
 
 ---
diff --git a/content/flux/v0.x/write-data/sql/sap-hana.md b/content/flux/v0.x/write-data/sql/sap-hana.md
index a43bc5d66..6d567f096 100644
--- a/content/flux/v0.x/write-data/sql/sap-hana.md
+++ b/content/flux/v0.x/write-data/sql/sap-hana.md
@@ -17,11 +17,11 @@ list_code_example: |
   import "sql"
   
   data
-    |> sql.to(
-      driverName: "hdb",
-      dataSourceName: "hdb://username:password@myserver:30015",
-      table: "SCHEMA.TABLE"
-    )
+      |> sql.to(
+          driverName: "hdb",
+          dataSourceName: "hdb://username:password@myserver:30015",
+          table: "SCHEMA.TABLE",
+      )
   ```
 ---
 
@@ -41,11 +41,11 @@ To write data to [SAP HANA](https://www.sap.com/products/hana.html) with Flux:
 import "sql"
   
 data
-  |> sql.to(
-    driverName: "hdb",
-    dataSourceName: "hdb://username:password@myserver:30015",
-    table: "SCHEMA.TABLE"
-  )
+    |> sql.to(
+        driverName: "hdb",
+        dataSourceName: "hdb://username:password@myserver:30015",
+        table: "SCHEMA.TABLE",
+    )
 ```
 
 ---
diff --git a/content/flux/v0.x/write-data/sql/snowflake.md b/content/flux/v0.x/write-data/sql/snowflake.md
index 35c4e494b..0cb92aa52 100644
--- a/content/flux/v0.x/write-data/sql/snowflake.md
+++ b/content/flux/v0.x/write-data/sql/snowflake.md
@@ -17,11 +17,11 @@ list_code_example: |
   import "sql"
   
   data
-    |> sql.to(
-      driverName: "snowflake",
-      dataSourceName: "user:password@account/db/exampleschema?warehouse=wh",
-      table: "example_table"
-    )
+      |> sql.to(
+          driverName: "snowflake",
+          dataSourceName: "user:password@account/db/exampleschema?warehouse=wh",
+          table: "example_table",
+      )
   ```
 ---
 
@@ -41,11 +41,11 @@ To write data to [Snowflake](https://www.snowflake.com/) with Flux:
 import "sql"
   
 data
-  |> sql.to(
-    driverName: "snowflake",
-    dataSourceName: "user:password@account/db/exampleschema?warehouse=wh",
-    table: "example_table"
-  )
+    |> sql.to(
+        driverName: "snowflake",
+        dataSourceName: "user:password@account/db/exampleschema?warehouse=wh",
+        table: "example_table",
+    )
 ```
 
 ---
diff --git a/content/flux/v0.x/write-data/sql/sql-server.md b/content/flux/v0.x/write-data/sql/sql-server.md
index c713235e4..5da8f57bf 100644
--- a/content/flux/v0.x/write-data/sql/sql-server.md
+++ b/content/flux/v0.x/write-data/sql/sql-server.md
@@ -17,11 +17,11 @@ list_code_example: |
   import "sql"
 
   data
-    |> sql.to(
-      driverName: "sqlserver",
-      dataSourceName: "sqlserver://user:password@localhost:1433?database=examplebdb",
-      table: "Example.Table"
-    )
+      |> sql.to(
+          driverName: "sqlserver",
+          dataSourceName: "sqlserver://user:password@localhost:1433?database=examplebdb",
+          table: "Example.Table",
+      )
   ```
 ---
 
@@ -41,11 +41,11 @@ To write data to [Microsoft SQL Server](https://www.microsoft.com/sql-server/) w
 import "sql"
 
 data
-  |> sql.to(
-    driverName: "sqlserver",
-    dataSourceName: "sqlserver://user:password@localhost:1433?database=examplebdb",
-    table: "Example.Table"
-  )
+    |> sql.to(
+        driverName: "sqlserver",
+        dataSourceName: "sqlserver://user:password@localhost:1433?database=examplebdb",
+        table: "Example.Table",
+    )
 ```
 
 ---
diff --git a/content/flux/v0.x/write-data/sql/sqlite.md b/content/flux/v0.x/write-data/sql/sqlite.md
index 1da730a58..4b723a36f 100644
--- a/content/flux/v0.x/write-data/sql/sqlite.md
+++ b/content/flux/v0.x/write-data/sql/sqlite.md
@@ -17,11 +17,11 @@ list_code_example: |
   import "sql"
 
   data
-    |> sql.to(
-      driverName: "sqlite3",
-      dataSourceName: "file:/path/to/example.db?cache=shared&mode=ro",
-      table: "example_table"
-    )
+      |> sql.to(
+          driverName: "sqlite3",
+          dataSourceName: "file:/path/to/example.db?cache=shared&mode=ro",
+          table: "example_table",
+      )
   ```
 ---
 
@@ -41,11 +41,11 @@ To write data to [SQLite](https://www.sqlite.org/index.html) with Flux:
 import "sql"
 
 data
-  |> sql.to(
-    driverName: "sqlite3",
-    dataSourceName: "file:/path/to/example.db?cache=shared&mode=ro",
-    table: "example_table"
-  )
+    |> sql.to(
+        driverName: "sqlite3",
+        dataSourceName: "file:/path/to/example.db?cache=shared&mode=ro",
+        table: "example_table",
+    )
 ```
 
 {{% note %}}
diff --git a/content/flux/v0.x/write-data/sql/vertica.md b/content/flux/v0.x/write-data/sql/vertica.md
index eadd06cf1..7bc6a8a5b 100644
--- a/content/flux/v0.x/write-data/sql/vertica.md
+++ b/content/flux/v0.x/write-data/sql/vertica.md
@@ -16,13 +16,13 @@ related:
 list_code_example: |
   ```js
   import "sql"
-  
+
   data
-    |> sql.to(
-      driverName: "vertica",
-      dataSourceName: "vertica://username:password@localhost:5433/dbname",
-      table: "public.example_table"
-    )
+      |> sql.to(
+          driverName: "vertica",
+          dataSourceName: "vertica://username:password@localhost:5433/dbname",
+          table: "public.example_table",
+      )
   ```
 ---
 
@@ -40,13 +40,13 @@ To write data to [Vertica](https://www.vertica.com/) with Flux:
 
 ```js
 import "sql"
-  
+
 data
-  |> sql.to(
-    driverName: "vertica",
-    dataSourceName: "vertica://username:password@localhost:5433/dbname",
-    table: "public.example_table"
-  )
+    |> sql.to(
+        driverName: "vertica",
+        dataSourceName: "vertica://username:password@localhost:5433/dbname",
+        table: "public.example_table",
+    )
 ```
 
 ---
diff --git a/content/influxdb/cloud/account-management/_index.md b/content/influxdb/cloud/account-management/_index.md
index ce4e5efc7..cb48c56f0 100644
--- a/content/influxdb/cloud/account-management/_index.md
+++ b/content/influxdb/cloud/account-management/_index.md
@@ -4,14 +4,12 @@ description: >
   View and manage information related to your InfluxDB Cloud account such as
   pricing plans, data usage, account cancelation, etc.
 weight: 10
-products: [cloud]
 aliases:
   - /influxdb/v2.0/cloud/account-management/
   - /influxdb/v2.0/account-management
 menu:
   influxdb_cloud:
     name: Account management
-products: [cloud]
 ---
 
 {{< children >}}
diff --git a/content/influxdb/cloud/account-management/billing.md b/content/influxdb/cloud/account-management/billing.md
index 4785ce212..27e54fe68 100644
--- a/content/influxdb/cloud/account-management/billing.md
+++ b/content/influxdb/cloud/account-management/billing.md
@@ -13,7 +13,6 @@ menu:
   influxdb_cloud:
     parent: Account management
     name: Manage billing
-products: [cloud]
 ---
 
 Learn how to upgrade your plan, access billing details, and review and resolve plan limit overages:
@@ -31,33 +30,34 @@ Learn how to upgrade your plan, access billing details, and review and resolve p
 
 ## Upgrade to Usage-Based Plan
 
-1. Click **Upgrade Now** in the lower left corner of the {{< cloud-name "short" >}} user interface (UI).
+1. Click **Upgrade Now** in the upper right corner of the {{< cloud-name "short" >}} user interface (UI).
 2. Set your limits (opt to receive an email when your usage exceeds the amount you enter in the **Limit ($1 minimum)** field). All service updates, security notifications, and other important information are sent to the email address you provide.
 3. Enter your payment information and billing address, and then click **Upgrade**. A Ready To Rock confirmation appears; click **Start building your team**. Your plan will be upgraded and {{< cloud-name >}} opens with a default organization and bucket (both created from your email address).
 
 ## Access billing details
 
 1. In the {{< cloud-name "short" >}} UI, select the **user avatar** in the left
-   navigation menu, and select **Billing**.
+   navigation menu, and select **Account** >
+   **Billing**.
 
     {{< nav-icon "account" >}}
 
 2. Do one of the following:
     - If you subscribed to an InfluxDB Cloud plan through [**AWS Marketplace**](https://aws.amazon.com/marketplace/pp/B08234JZPS), [**Azure Marketplace**](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/influxdata.influxdb-cloud), or [**GCP Marketplace**](https://console.cloud.google.com/marketplace/details/influxdata-public/cloud2-gcp-marketplace-prod?pli=1), click the **AWS**, **Microsoft**, or **GCP** link to access your billing and subscription information.
 
-  - If you subscribed to an InfluxDB Cloud plan through **InfluxData**, complete the following procedures as needed:
+   - If you subscribed to an InfluxDB Cloud plan through **InfluxData**, complete the following procedures as needed:
 
-        - [Add or update your payment method](#add-or-update-your-payment-method)
-        - [Add or update your contact information](#add-or-update-your-contact-information)
-        - [Send notifications when usage exceeds an amount](#send-notifications-when-usage-exceeds-an-amount)
+       - [Add or update your payment method](#add-or-update-your-payment-method)
+       - [Add or update your contact information](#add-or-update-your-contact-information)
+       - [Send notifications when usage exceeds an amount](#send-notifications-when-usage-exceeds-an-amount)
 
-        View information about:
+3. View information about:
 
-        - [Usage-Based Plan](#view-usage-based-plan-information)
-        - [Free Plan](#view-free-plan-information)
-        - [Exceeded rate limits](#exceeded-rate-limits)
-        - [Billing cycle](#billing-cycle)
-        - [Declined or late payments](#declined-or-late-payments)
+    - [Usage-Based Plan](#view-usage-based-plan-information)
+    - [Free Plan](#view-free-plan-information)
+    - [Exceeded rate limits](#review-and-resolve-plan-limit-overages)
+    - [Billing cycle](#billing-cycle)
+    - [Declined or late payments](#declined-or-late-payments)
 
 ### Add or update your payment method
 
@@ -98,9 +98,9 @@ On the **Billing page**, view the total limits available for the Free Plan.
 
 ## Review and resolve plan limit overages
 
-If you exceed your plan's [limits](/influxdb/cloud/account-management/pricing-plans), you'll receive a notification in the {{< cloud-name "short" >}} user interface (UI) **Usage** page.
+If you exceed your plan's [adjustable quotas or limits](/influxdb/cloud/account-management/limits/), you'll receive a notification in the {{< cloud-name "short" >}} user interface (UI) **Usage** page.
 
-If exceed the series cardinality limit, InfluxDB adds a rate limit event to your **Usage** page for review, and begins to reject write requests. To start processing write requests again, do the following as needed:
+If you exceed the series cardinality limit, InfluxDB adds a rate limit event warning on the **Usage** page, and begins to reject write requests with new series. To start processing write requests again, do the following as needed:
 
 - **Usage-Based plan**: To request higher rate limits, contact [InfluxData Support](mailto:support@influxdata.com).
 - **Series cardinality limits**: If you exceed the series cardinality limit, see how to [resolve high series cardinality](https://docs.influxdata.com/influxdb/v2.0/write-data/best-practices/resolve-high-cardinality/).
@@ -127,4 +127,3 @@ Billing occurs on the first day of the month for the previous month. For example
 | **One week later**          | Account disabled except data writes. Update your payment method to successfully process your payment and enable your account. |
 | **10-14 days later**        | Account completely disabled. During this period, you must contact us at support@influxdata.com to process your payment and enable your account. |
 | **21 days later**           | Account suspended. Contact support@influxdata.com to settle your final bill and retrieve a copy of your data or access to InfluxDB Cloud dashboards, tasks, Telegraf configurations, and so on.|
-
diff --git a/content/influxdb/cloud/account-management/data-usage.md b/content/influxdb/cloud/account-management/data-usage.md
index 92053a7b4..315183d0a 100644
--- a/content/influxdb/cloud/account-management/data-usage.md
+++ b/content/influxdb/cloud/account-management/data-usage.md
@@ -11,10 +11,12 @@ menu:
   influxdb_cloud:
     parent: Account management
     name: View data usage
-products: [cloud]
+related:
+  - /flux/v0.x/stdlib/experimental/usage/from/
+  - /flux/v0.x/stdlib/experimental/usage/limits/
 ---
 
-View the statistics of your data usage and rate limits (reads, writes, and delete limits) on the Usage page. Some usage data affects monthly costs (pricing vectors) and other usage data, including delete limits, does not affect pricing. For more information about costs and limits, see the [pricing plans](/influxdb/cloud/account-management/pricing-plans/).
+View the statistics of your data usage and rate limits (reads, writes, and delete limits) on the Usage page. Some usage data affects monthly costs ([pricing vectors](/influxdb/cloud/account-management/pricing-plans/#pricing-vectors)) and other usage data (for example, delete limits), does not affect pricing. For more information, see the [InfluxDB Cloud limits and adjustable quotas](/influxdb/cloud/account-management/limits/).
 
 To view your {{< cloud-name >}} data usage, do the following:
 
@@ -28,34 +30,3 @@ To view your {{< cloud-name >}} data usage, do the following:
    - **Data Out:** Total data in MB sent as responses to queries from your {{< cloud-name "short" >}} instance.
 
 A line graph displays usage for the selected vector for the specified time period.
-
-## Exceeded rate limits
-
-If you exceed your [plan's data limits](/influxdb/cloud/account-management/pricing-plans/), {{< cloud-name >}} UI displays a notification message, and the following occurs:
-
-- When **write or read requests or series cardinality exceed** the specified limit within a five-minute window, the request is rejected and the following events appears under **Limit Events** on the Usage page as applicable: `event_type_limited_query` or `event_type_limited_write` or `event_type_limited_cardinality`
-
-  _To raise these rate limits, [upgrade to a Usage-based Plan](/influxdb/cloud/account-management/billing/#upgrade-to-usage-based-plan)._
-
-- When **delete requests exceed** the specified limit within a five-minute window, the request is rejected and `event_type_limited_delete_rate` appears under **Limit Events** on the Usage page.
-  {{% note %}}
-**Tip:**
-Combine predicate expressions (if possible) into a single request. InfluxDB rate limits per number of requests (not points in request).
-{{% /note %}}
-
-### InfluxDB API: HTTP rate limit responses
-
-The InfluxDB API returns the following responses:
-
-- When a **read or write or delete request exceeds** limits:
-
-  ```
-  HTTP 429 “Too Many Requests”
-  Retry-After: xxx (seconds to wait before retrying the request)
-  ```
-
-- When **series cardinality exceeds** your plan's limit:
-
-  ```
-  HTTP 503 “Series cardinality exceeds your plan's limit”
-  ```
diff --git a/content/influxdb/cloud/account-management/limits.md b/content/influxdb/cloud/account-management/limits.md
new file mode 100644
index 000000000..9da3e2e4f
--- /dev/null
+++ b/content/influxdb/cloud/account-management/limits.md
@@ -0,0 +1,105 @@
+---
+title: InfluxDB Cloud limits and adjustable quotas
+description: >
+  InfluxDB Cloud has adjustable service quotas and global (non-adjustable) system limits.
+weight: 110
+menu:
+  influxdb_cloud:
+    parent: Account management
+    name: Adjustable quotas and limits
+related:
+  - /flux/v0.x/stdlib/experimental/usage/from/
+  - /flux/v0.x/stdlib/experimental/usage/limits/
+  - /influxdb/cloud/write-data/best-practices/resolve-high-cardinality/
+---
+
+InfluxDB Cloud applies (non-adjustable) global system limits and adjustable service quotas on a per organization basis. Currently, InfluxDB Cloud supports one organization per account.
+
+{{% warn %}}
+All __rates__ (data-in (writes), queries (reads), and deletes) are accrued within a fixed five-minute window. Once a rate is exceeded, an error response is returned until the current five-minute window resets.
+{{% /warn %}}
+
+Review adjustable service quotas and global limits to plan for your bandwidth needs:
+
+- [Adjustable service quotas](#adjustable-service-quotas)
+- [Global limits](#global-limits)
+- [UI error messages](#ui-error-messages)
+- [API error responses](#api-error-responses)
+
+## Adjustable service quotas
+
+To reduce the chance of unexpected charges and protect the service for all users, InfluxDB Cloud has adjustable service quotas applied per account.
+
+_To request higher service quotas, reach out to [InfluxData Support](https://support.influxdata.com/)._
+
+### Free Plan
+
+- **Data-in**: Rate of 5 MB per 5 minutes (average of 17 kb/s)
+  - Uncompressed bytes of normalized [line protocol](/influxdb/cloud/reference/syntax/line-protocol/)
+- **Read**: Rate of 300 MB per 5 minutes (average of 1000 kb/s)
+  - Bytes in HTTP in response payload
+- **Cardinality**: 10k series (see [how to measure and resolve high cardinality](/influxdb/cloud/write-data/best-practices/resolve-high-cardinality/))
+- **Available resources**:
+  - 2 buckets (excluding `_monitoring` and `_tasks` buckets)
+  - 5 dashboards
+  - 5 tasks
+- **Alerts**:
+  - 2 checks
+  - 2 notification rules
+  - Unlimited Slack notification endpoints
+- **Storage**: 30 days of data retention (see [retention period](/influxdb/cloud/reference/glossary/#retention-period))
+
+{{% note %}}
+To write historical data older than 30 days, retain data for more than 30 days, or increase rate limits, upgrade to the Cloud [Usage-Based Plan](/influxdb/cloud/account-management/pricing-plans/#usage-based-plan).
+{{% /note %}}
+
+### Usage-Based Plan
+
+- **Data-in**: Rate of 3 GB per 5 minutes
+  - Uncompressed bytes of normalized [line protocol](/influxdb/cloud/reference/syntax/line-protocol/)
+- **Read**: Rate of 3 GB data per 5 minutes
+  - Bytes in HTTP in response payload
+- **Cardinality**: 1M series (see [how to measure and resolve high cardinality](/influxdb/cloud/write-data/best-practices/resolve-high-cardinality/))
+- **Unlimited resources**
+  - dashboards
+  - tasks
+  - buckets
+  - users
+- **Alerts**
+  - Unlimited checks
+  - Unlimited notification rules
+  - Unlimited notification endpoints for [all endpoints](/flux/v0.x/tags/notification-endpoints/)
+- **Storage**: Set your retention period to unlimited or up to 1 year by [updating a bucket’s retention period in the InfluxDB UI](/influxdb/cloud/organizations/buckets/update-bucket/#update-a-buckets-retention-period-in-the-influxdb-ui), or [set a custom retention period](/influxdb/cloud/organizations/buckets/update-bucket/#update-a-buckets-retention-period) using the [`influx` CLI](influxdb/cloud/reference/cli/influx/).
+
+## Global limits
+
+InfluxDB Cloud applies global (non-adjustable) system limits to all accounts, which protects the InfluxDB Cloud infrastructure for all users. As the service continues to evolve, we'll continue to review these global limits and adjust them as appropriate.
+
+Limits include:
+
+- Write request limits:
+  - 50 MB maximum HTTP request batch size (compressed or uncompressed--defined in the `Content-Encoding` header)
+  - 250 MB maximum HTTP request batch size after decompression
+- Query processing time: 90 seconds
+- Task processing time: 150 seconds
+- Delete request limit: Rate of 300 every 5 minutes
+  {{% note %}}
+**Tip:**
+Combine predicate expressions (if possible) into a single request. InfluxDB limits delete requests by number of requests (not points in request).
+{{% /note %}}
+
+## UI error messages
+
+The {{< cloud-name >}} UI displays a notification message when service quotas or limits are exceeded. The error messages correspond with the relevant [API error responses](#api-error-responses).
+
+Errors can also be viewed in the [Usage page](/influxdb/cloud/account-management/data-usage/) under **Limit Events**, e.g. `event_type_limited_query`, `event_type_limited_write`,`event_type_limited_cardinality`, or `event_type_limited_delete_rate`.
+
+## API error responses
+
+The following API error responses occur when your plan's service quotas are exceeded.
+
+| HTTP response code              | Error message                               | Description  |
+| :-----------------------------  | :-----------------------------------------  | :----------- |
+| `HTTP 413 "Request Too Large"`  | cannot read data: points in batch is too large | If a **write** request exceeds the maximum [global limit](/influxdb/cloud/account-management/limits/#global-limits) |  
+| `HTTP 429 "Too Many Requests"`  | Retry-After: xxx (seconds to wait before retrying the request) | If a **read** or **write** request exceeds your plan's [adjustable service quotas](/influxdb/cloud/account-management/limits/#adjustable-service-quotas) or if a **delete** request exceeds the maximum [global limit](/influxdb/cloud/account-management/limits/#global-limits) |
+| `HTTP 429 "Too Many Requests"` | Series cardinality exceeds your plan's service quota | If **series cardinality** exceeds your plan's [adjustable service quotas](/influxdb/cloud/account-management/limits/#adjustable-service-quotas) |
diff --git a/content/influxdb/cloud/account-management/offboarding.md b/content/influxdb/cloud/account-management/offboarding.md
index c2e3d4261..fb0fc3805 100644
--- a/content/influxdb/cloud/account-management/offboarding.md
+++ b/content/influxdb/cloud/account-management/offboarding.md
@@ -11,7 +11,6 @@ menu:
   influxdb_cloud:
     parent: Account management
     name: Cancel InfluxDB Cloud
-products: [cloud]
 ---
 
 To cancel your {{< cloud-name >}} subscription, complete the following steps:
diff --git a/content/influxdb/cloud/account-management/pricing-calculator.md b/content/influxdb/cloud/account-management/pricing-calculator.md
index 714b55d9b..f372cdfe3 100644
--- a/content/influxdb/cloud/account-management/pricing-calculator.md
+++ b/content/influxdb/cloud/account-management/pricing-calculator.md
@@ -7,7 +7,6 @@ weight: 2
 menu:
   influxdb_cloud:
     name: Pricing calculator
-products: [cloud]
 draft: true
 ---
 
diff --git a/content/influxdb/cloud/account-management/pricing-plans.md b/content/influxdb/cloud/account-management/pricing-plans.md
index 0e881c676..83d2b5e1e 100644
--- a/content/influxdb/cloud/account-management/pricing-plans.md
+++ b/content/influxdb/cloud/account-management/pricing-plans.md
@@ -1,5 +1,5 @@
 ---
-title: InfluxDB Cloud pricing plans
+title: InfluxDB Cloud plans
 description: >
   InfluxDB Cloud provides two pricing plans to fit your needs – the Free Plan and the Usage-based Plan.
 aliases:
@@ -11,62 +11,21 @@ menu:
   influxdb_cloud:
     parent: Account management
     name: Pricing plans
-products: [cloud]
 ---
 
-InfluxDB Cloud offers two plans, which provide different data and resource usage limits:
-
-- [Free Plan](#free-plan)
-- [Usage-Based Plan](#usage-based-plan)
+InfluxDB Cloud offers a [Free Plan](#free-plan), a [Usage-Based Plan](#usage-based-plan) to pay as you go, and a discounted [Annual Plan](#annual-plan).
 
 <!--To estimate your projected usage costs, use the [InfluxDB Cloud pricing calculator](/influxdb/cloud/account-management/pricing-calculator/). -->
 
 ## Free Plan
 
-All new {{< cloud-name >}} accounts start with Free Plan that limits data and resource usage.
-Use this plan as much and as long as you want within the Free Plan limits below.
-
-### Data limits
-
-- **Data In:** 5.1MB every 5 minutes
-- **Query:** 300MB every 5 minutes
-- **Series cardinality:** 10,000
-- **Storage:** 30-day data retention
-{{% note %}}
-To write historical data older than 30 days or retain data for more than 30 days, upgrade to the Cloud [Usage-Based plan](/influxdb/cloud/account-management/pricing-plans/#usage-based-plan).
-{{% /note %}}
-
-### Resource limits
-
-  - 5 dashboards
-  - 5 tasks
-  - 2 buckets
-  - 2 checks
-  - 2 notification rules
-  - Unlimited Slack notification endpoints
-
-_To raise rate limits, [upgrade to a Usage-based Plan](/influxdb/cloud/account-management/billing/#upgrade-to-usage-based-plan)._
+All new {{< cloud-name >}} accounts start with Free Plan that provides a limited number of resources and data usage. See [plan limits](/influxdb/cloud/account-management/limits/).
 
 ## Usage-Based Plan
 
-The Usage-based Plan offers more flexibility and ensures you only pay for what you [use](/influxdb/cloud/account-management/data-usage/).
+The Usage-Based Plan offers more flexibility and ensures you only pay for what you [use](/influxdb/cloud/account-management/data-usage/). Usage-Based Plans are based on consumption as measured by usage on the [pricing vectors](#pricing-vectors).
 
-### Data limit
-
-- **Ingest batch size:** 50MB
-
-### Soft data limits
-
-To protect against any intentional or unintentional harm, the Usage-Based Plan includes soft limits.
-_To request higher soft data limits, contact [InfluxData Support](mailto:support@influxdata.com)._
-
-- **Data In:** 300MB every 5 minutes
-- **Query:** 3000MB every 5 minutes
-- **Series cardinality:** 1,000,000 initial limit (higher limits available; [contact InfluxData Support](mailto:support@influxdata.com))
-- **Storage:** Unlimited retention
-{{% note %}}
-Set your retention period to unlimited or up to 1 year by [updating a bucket’s retention period in the InfluxDB UI](/influxdb/cloud/organizations/buckets/update-bucket/#update-a-buckets-retention-period-in-the-influxdb-ui), or [set a custom retention period](/influxdb/cloud/organizations/buckets/update-bucket/#update-a-buckets-retention-period) using the [`influx` CLI](/influxdb/cloud/reference/cli/influx/).
-{{% /note %}}
+Usage-Based Plans also offer access to all notification endpoints such as PagerDuty, Slack, HTTP, and [endpoints available in Flux](/flux/v0.x/tags/notification-endpoints/).
 
 ### Pricing vectors
 
@@ -82,12 +41,11 @@ The Usage-Based Plan uses the following pricing vectors to calculate InfluxDB Cl
 
 Discover how to [manage InfluxDB Cloud billing](/influxdb/cloud/account-management/billing/).
 
-### Unlimited resources
+## Annual Plan
+<!-- Maybe this should be "annual commitment"? -->
 
-  - Dashboards
-  - Tasks
-  - Buckets
-  - Users
-  - Checks
-  - Notification rules
-  - PagerDuty, Slack, and HTTP notification endpoints
+An Annual Plan offers a discount for a commitment to a specific amount of usage over set period of time. This plan uses the same pricing vectors and calculation methodology as Usage-Based Plans.
+
+__Interested in an Annual Plan? Reach out to [InfluxData Sales](https://www.influxdata.com/contact-sales/).__
+
+<!-- ## Pricing FAQs -->
diff --git a/content/influxdb/cloud/account-management/switch-account.md b/content/influxdb/cloud/account-management/switch-account.md
new file mode 100644
index 000000000..2cab9717b
--- /dev/null
+++ b/content/influxdb/cloud/account-management/switch-account.md
@@ -0,0 +1,23 @@
+---
+title: Switch InfluxDB Cloud accounts
+seotitle: Switch between InfluxDB Cloud accounts
+description: >
+  Switch from one InfluxDB Cloud account to another and set a default account.  
+menu:
+  influxdb_cloud:
+    name: Switch InfluxDB accounts
+    parent: Account management
+weight: 105
+---
+If you belong to more than one {{< cloud-name >}} account with the same email address, you can switch from one account to another while staying logged in. An account can contain multiple organizations. 
+
+You can also set a default account. The default account is the account automatically used when the user logs in.
+
+To switch {{< cloud-name "short" >}} accounts:
+
+1. In the {{< cloud-name "short" >}} UI, select the **user avatar** in the left
+   navigation menu, and select **Account** > **Settings**.
+2. Click **Switch Account**. If this option doesn't appear, your email address is only associated with one account.
+3. Select the account you want to switch to or set as the default in the window that appears.
+4. To switch to the account, select **Switch Account**.
+5. To set an account as the default, select **Set Default Account**.
diff --git a/content/influxdb/cloud/api-guide/client-libraries/arduino.md b/content/influxdb/cloud/api-guide/client-libraries/arduino.md
index a411af4f9..05bcc9508 100644
--- a/content/influxdb/cloud/api-guide/client-libraries/arduino.md
+++ b/content/influxdb/cloud/api-guide/client-libraries/arduino.md
@@ -9,6 +9,7 @@ menu:
   influxdb_cloud:
     name: Arduino
     parent: Client libraries
-    url: https://github.com/tobiasschuerg/InfluxDB-Client-for-Arduino
+    params:
+      url: https://github.com/tobiasschuerg/InfluxDB-Client-for-Arduino
 weight: 201
 ---
diff --git a/content/influxdb/cloud/api-guide/client-libraries/csharp.md b/content/influxdb/cloud/api-guide/client-libraries/csharp.md
index b60f1b120..4d57259bd 100644
--- a/content/influxdb/cloud/api-guide/client-libraries/csharp.md
+++ b/content/influxdb/cloud/api-guide/client-libraries/csharp.md
@@ -8,6 +8,7 @@ menu:
   influxdb_cloud:
     name: C#
     parent: Client libraries
-    url: https://github.com/influxdata/influxdb-client-csharp
+    params:
+      url: https://github.com/influxdata/influxdb-client-csharp
 weight: 201
 ---
diff --git a/content/influxdb/cloud/api-guide/client-libraries/dart.md b/content/influxdb/cloud/api-guide/client-libraries/dart.md
index 30bc56337..b54431fd8 100644
--- a/content/influxdb/cloud/api-guide/client-libraries/dart.md
+++ b/content/influxdb/cloud/api-guide/client-libraries/dart.md
@@ -8,6 +8,7 @@ menu:
   influxdb_cloud:
     name: Dart
     parent: Client libraries
-    url: https://github.com/influxdata/influxdb-client-dart
+    params:
+      url: https://github.com/influxdata/influxdb-client-dart
 weight: 201
 ---
diff --git a/content/influxdb/cloud/api-guide/client-libraries/java.md b/content/influxdb/cloud/api-guide/client-libraries/java.md
index 350ad971e..9d5ae02fc 100644
--- a/content/influxdb/cloud/api-guide/client-libraries/java.md
+++ b/content/influxdb/cloud/api-guide/client-libraries/java.md
@@ -8,6 +8,7 @@ menu:
   influxdb_cloud:
     name: Java
     parent: Client libraries
-    url: https://github.com/influxdata/influxdb-client-java
+    params:
+      url: https://github.com/influxdata/influxdb-client-java
 weight: 201
 ---
diff --git a/content/influxdb/cloud/api-guide/client-libraries/kotlin.md b/content/influxdb/cloud/api-guide/client-libraries/kotlin.md
index c47846680..bf3c6489c 100644
--- a/content/influxdb/cloud/api-guide/client-libraries/kotlin.md
+++ b/content/influxdb/cloud/api-guide/client-libraries/kotlin.md
@@ -8,6 +8,7 @@ menu:
   influxdb_cloud:
     name: Kotlin
     parent: Client libraries
-    url: https://github.com/influxdata/influxdb-client-java/tree/master/client-kotlin
+    params:
+      url: https://github.com/influxdata/influxdb-client-java/tree/master/client-kotlin
 weight: 201
 ---
diff --git a/content/influxdb/cloud/api-guide/client-libraries/php.md b/content/influxdb/cloud/api-guide/client-libraries/php.md
index ca70c3a03..1ce4c2180 100644
--- a/content/influxdb/cloud/api-guide/client-libraries/php.md
+++ b/content/influxdb/cloud/api-guide/client-libraries/php.md
@@ -8,6 +8,7 @@ menu:
   influxdb_cloud:
     name: PHP
     parent: Client libraries
-    url: https://github.com/influxdata/influxdb-client-php
+    params:
+      url: https://github.com/influxdata/influxdb-client-php
 weight: 201
 ---
diff --git a/content/influxdb/cloud/api-guide/client-libraries/r.md b/content/influxdb/cloud/api-guide/client-libraries/r.md
index f7681bedd..34bd2bad2 100644
--- a/content/influxdb/cloud/api-guide/client-libraries/r.md
+++ b/content/influxdb/cloud/api-guide/client-libraries/r.md
@@ -8,6 +8,7 @@ menu:
   influxdb_cloud:
     name: R
     parent: Client libraries
-    url: https://github.com/influxdata/influxdb-client-r
+    params:
+      url: https://github.com/influxdata/influxdb-client-r
 weight: 201
 ---
diff --git a/content/influxdb/cloud/api-guide/client-libraries/ruby.md b/content/influxdb/cloud/api-guide/client-libraries/ruby.md
index 198e74cf7..8f7e25302 100644
--- a/content/influxdb/cloud/api-guide/client-libraries/ruby.md
+++ b/content/influxdb/cloud/api-guide/client-libraries/ruby.md
@@ -8,6 +8,7 @@ menu:
   influxdb_cloud:
     name: Ruby
     parent: Client libraries
-    url: https://github.com/influxdata/influxdb-client-ruby
+    params:
+      url: https://github.com/influxdata/influxdb-client-ruby
 weight: 201
 ---
diff --git a/content/influxdb/cloud/api-guide/client-libraries/scala.md b/content/influxdb/cloud/api-guide/client-libraries/scala.md
index d6bc90ea9..96af468fa 100644
--- a/content/influxdb/cloud/api-guide/client-libraries/scala.md
+++ b/content/influxdb/cloud/api-guide/client-libraries/scala.md
@@ -8,6 +8,7 @@ menu:
   influxdb_cloud:
     name: Scala
     parent: Client libraries
-    url: https://github.com/influxdata/influxdb-client-java/tree/master/client-scala
+    params:
+      url: https://github.com/influxdata/influxdb-client-java/tree/master/client-scala
 weight: 201
 ---
diff --git a/content/influxdb/cloud/api-guide/client-libraries/swift.md b/content/influxdb/cloud/api-guide/client-libraries/swift.md
index f0ccbc96d..273ab9811 100644
--- a/content/influxdb/cloud/api-guide/client-libraries/swift.md
+++ b/content/influxdb/cloud/api-guide/client-libraries/swift.md
@@ -8,6 +8,7 @@ menu:
   influxdb_cloud:
     name: Swift
     parent: Client libraries
-    url: https://github.com/influxdata/influxdb-client-swift
+    params:
+      url: https://github.com/influxdata/influxdb-client-swift
 weight: 201
 ---
diff --git a/content/influxdb/cloud/get-started.md b/content/influxdb/cloud/get-started.md
index 4b38b7a7f..a08d9cc23 100644
--- a/content/influxdb/cloud/get-started.md
+++ b/content/influxdb/cloud/get-started.md
@@ -65,12 +65,11 @@ Add the following as an [InfluxDB task](/influxdb/cloud/process-data/manage-task
 
 ```js
 import "influxdata/influxdb/sample"
-option task = {
-  name: "Collect NOAA NDBC data"
-  every: 15m,
-}
+
+option task = {name: "Collect NOAA NDBC data", every: 15m}
+
 sample.data(set: "noaa")
-  |> to(bucket: "noaa"  )
+    |> to(bucket: "noaa")
  ```
 
 For more information about this and other InfluxDB sample datasets, see [InfluxDB sample data](/influxdb/cloud/reference/sample-data/).
diff --git a/content/influxdb/cloud/influxdb-templates/cloud.md b/content/influxdb/cloud/influxdb-templates/cloud.md
index 1f50e1126..8ebde2517 100644
--- a/content/influxdb/cloud/influxdb-templates/cloud.md
+++ b/content/influxdb/cloud/influxdb-templates/cloud.md
@@ -12,7 +12,6 @@ weight: 101
 aliases:
   - /influxdb/cloud/influxdb-templates/get_started_cloud/
 influxdb/cloud/tags: [templates]
-products: [cloud]
 ---
 
 To use templates in InfluxDB Cloud, you have a couple options:
diff --git a/content/influxdb/cloud/influxdb-templates/create.md b/content/influxdb/cloud/influxdb-templates/create.md
index 03835cb30..08195eefa 100644
--- a/content/influxdb/cloud/influxdb-templates/create.md
+++ b/content/influxdb/cloud/influxdb-templates/create.md
@@ -54,7 +54,7 @@ Provide the following:
 ###### Export all resources to a template
 ```sh
 # Syntax
-influx export all -o <org-name> -f <file-path> -t <token>
+influx export all -o <INFLUX_ORG> -f <FILE_PATH> -t <INFLUX_TOKEN>
 
 # Example
 influx export all \
@@ -108,7 +108,7 @@ Provide the following:
 ###### Export specific resources to a template
 ```sh
 # Syntax
-influx export all -o <org-name> -f <file-path> -t <token> [resource-flags]
+influx export all -o <INFLUX_ORG> -f <FILE_PATH> -t <INFLUX_TOKEN> [resource-flags]
 
 # Example
 influx export all \
@@ -136,10 +136,10 @@ Provide the following:
 ```sh
 # Syntax
 influx export stack \
-  -o <org-name> \
-  -t <token> \
-  -f <file-path> \
-  <stack-id>
+  -o <INFLUX_ORG> \
+  -t <INFLUX_TOKEN> \
+  -f <FILE_PATH> \
+  <STACK_ID>
 
 # Example
 influx export stack \
diff --git a/content/influxdb/cloud/influxdb-templates/monitor-enterprise.md b/content/influxdb/cloud/influxdb-templates/monitor-enterprise.md
index dc10bfc41..b75a416b1 100644
--- a/content/influxdb/cloud/influxdb-templates/monitor-enterprise.md
+++ b/content/influxdb/cloud/influxdb-templates/monitor-enterprise.md
@@ -31,7 +31,7 @@ Before you begin, make sure you have access to the following:
  - InfluxDB Cloud account ([sign up for free here](https://cloud2.influxdata.com/signup))
  - Command line access to a machine [running InfluxDB Enterprise 1.x](/enterprise_influxdb/v1.9/introduction/install-and-deploy/) and permissions to install Telegraf on this machine
  - Internet connectivity from the machine running InfluxDB Enterprise 1.x and Telegraf to InfluxDB Cloud
- - Sufficient resource availability to install the template. InfluxDB Cloud Free Plan accounts include [resource limits](/influxdb/cloud/account-management/pricing-plans/#resource-limits/influxdb/cloud/account-management/pricing-plans/#resource-limits)
+ - Sufficient resource availability to install the template. InfluxDB Cloud Free Plan accounts include [resource limits](/influxdb/cloud/account-management/limits/#free-plan-limits)
 
 ## Install the InfluxDB Enterprise Monitoring template
 
diff --git a/content/influxdb/cloud/migrate-data/_index.md b/content/influxdb/cloud/migrate-data/_index.md
new file mode 100644
index 000000000..d3cc29a0f
--- /dev/null
+++ b/content/influxdb/cloud/migrate-data/_index.md
@@ -0,0 +1,14 @@
+---
+title: Migrate data to InfluxDB
+description: >
+  Migrate data from InfluxDB OSS (open source) to InfluxDB Cloud or other InfluxDB OSS instances--or from InfluxDB Cloud to InfluxDB OSS.
+menu:
+  influxdb_cloud:
+    name: Migrate data
+weight: 9
+---
+
+Migrate data to InfluxDB from other InfluxDB instances including by InfluxDB OSS
+and InfluxDB Cloud.
+
+{{< children >}}
diff --git a/content/influxdb/cloud/migrate-data/migrate-cloud-to-cloud.md b/content/influxdb/cloud/migrate-data/migrate-cloud-to-cloud.md
new file mode 100644
index 000000000..eb1fdee51
--- /dev/null
+++ b/content/influxdb/cloud/migrate-data/migrate-cloud-to-cloud.md
@@ -0,0 +1,380 @@
+---
+title: Migrate data between InfluxDB Cloud organizations
+description: >
+  To migrate data from one InfluxDB Cloud organization to another, query the
+  data from time-based batches and write the queried data to a bucket in another
+  InfluxDB Cloud organization.
+menu:
+  influxdb_cloud:
+    name: Migrate from Cloud to Cloud
+    parent: Migrate data
+weight: 102
+---
+
+To migrate data from one InfluxDB Cloud organization to another, query the
+data from time-based batches and write the queried data to a bucket in another
+InfluxDB Cloud organization.
+Because full data migrations will likely exceed your organizations' limits and
+adjustable quotas, migrate your data in batches.
+
+The following guide provides instructions for setting up an InfluxDB task
+that queries data from an InfluxDB Cloud bucket in time-based batches and writes
+each batch to another InfluxDB Cloud bucket in another organization.
+
+{{% cloud %}}
+All query and write requests are subject to your InfluxDB Cloud organization's
+[rate limits and adjustable quotas](/influxdb/cloud/account-management/limits/).
+{{% /cloud %}}
+
+- [Set up the migration](#set-up-the-migration)
+- [Migration task](#migration-task)
+  - [Configure the migration](#configure-the-migration)
+  - [Migration Flux script](#migration-flux-script)
+  - [Configuration help](#configuration-help)
+- [Monitor the migration progress](#monitor-the-migration-progress)
+- [Troubleshoot migration task failures](#troubleshoot-migration-task-failures)
+
+## Set up the migration
+
+{{% note %}}
+The migration process requires two buckets in your destination InfluxDB
+organization—one bucket to store the migrated data and another bucket to store migration metadata.
+If the destination organization uses the [InfluxDB Cloud Free Plan](/influxdb/cloud/account-management/limits/#free-plan),
+any buckets in addition to these two will exceed the your plan's bucket limit.
+{{% /note %}}
+
+1.  **In the InfluxDB Cloud organization you're migrating data _from_**,
+    [create an API token](/influxdb/cloud/security/tokens/create-token/)
+    with **read access** to the bucket you want to migrate.
+
+2.  **In the InfluxDB Cloud organization you're migrating data _to_**:
+    1.  Add the **InfluxDB Cloud API token from the source organization** as a
+        secret using the key, `INFLUXDB_CLOUD_TOKEN`.
+        _See [Add secrets](/influxdb/cloud/security/secrets/add/) for more information._
+    2.  [Create a bucket](/influxdb/cloud/organizations/buckets/create-bucket/)
+        **to migrate data to**.
+    3.  [Create a bucket](/influxdb/cloud/organizations/buckets/create-bucket/)
+        **to store temporary migration metadata**.
+    4.  [Create a new task](/influxdb/cloud/process-data/manage-tasks/create-task/)
+        using the provided [migration task](#migration-task).
+        Update the necessary [migration configuration options](#configure-the-migration).
+    5.  _(Optional)_ Set up [migration monitoring](#monitor-the-migration-progress).
+    6.  Save the task.
+
+        {{% note %}}
+Newly-created tasks are enabled by default, so the data migration begins when you save the task.
+        {{% /note %}}
+
+**After the migration is complete**, each subsequent migration task execution
+will fail with the following error:
+
+```
+error exhausting result iterator: error calling function "die" @41:9-41:86:
+Batch range is beyond the migration range. Migration is complete.
+```
+
+## Migration task
+
+### Configure the migration
+1.  Specify how often you want the task to run using the `task.every` option.
+    _See [Determine your task interval](#determine-your-task-interval)._
+
+2.  Define the following properties in the `migration`
+    [record](/{{< latest "flux" >}}/data-types/composite/record/):
+
+    ##### migration
+    - **start**: Earliest time to include in the migration.
+      _See [Determine your migration start time](#determine-your-migration-start-time)._
+    - **stop**: Latest time to include in the migration.
+    - **batchInterval**: Duration of each time-based batch.
+      _See [Determine your batch interval](#determine-your-batch-interval)._
+    - **batchBucket**: InfluxDB bucket to store migration batch metadata in.
+    - **sourceHost**: [InfluxDB Cloud region URL](/influxdb/cloud/reference/regions)
+      to migrate data from.
+    - **sourceOrg**: InfluxDB Cloud organization to migrate data from.
+    - **sourceToken**: InfluxDB Cloud API token. To keep the API token secure, store
+      it as a secret in InfluxDB OSS.
+    - **sourceBucket**: InfluxDB Cloud bucket to migrate data from.
+    - **destinationBucket**: InfluxDB OSS bucket to migrate data to.
+
+### Migration Flux script
+
+```js
+import "array"
+import "experimental"
+import "influxdata/influxdb/secrets"
+
+// Configure the task
+option task = {every: 5m, name: "Migrate data from InfluxDB Cloud"}
+
+// Configure the migration
+migration = {
+    start: 2022-01-01T00:00:00Z,
+    stop: 2022-02-01T00:00:00Z,
+    batchInterval: 1h,
+    batchBucket: "migration",
+    sourceHost: "https://cloud2.influxdata.com",
+    sourceOrg: "example-cloud-org",
+    sourceToken: secrets.get(key: "INFLUXDB_CLOUD_TOKEN"),
+    sourceBucket: "example-cloud-bucket",
+    destinationBucket: "example-oss-bucket",
+}
+
+// batchRange dynamically returns a record with start and stop properties for
+// the current batch. It queries migration metadata stored in the
+// `migration.batchBucket` to determine the stop time of the previous batch.
+// It uses the previous stop time as the new start time for the current batch
+// and adds the `migration.batchInterval` to determine the current batch stop time.
+batchRange = () => {
+    _lastBatchStop =
+        (from(bucket: migration.batchBucket)
+            |> range(start: migration.start)
+            |> filter(fn: (r) => r._field == "batch_stop")
+            |> filter(fn: (r) => r.srcOrg == migration.sourceOrg)
+            |> filter(fn: (r) => r.srcBucket == migration.sourceBucket)
+            |> last()
+            |> findRecord(fn: (key) => true, idx: 0))._value
+    _batchStart =
+        if exists _lastBatchStop then
+            time(v: _lastBatchStop)
+        else
+            migration.start
+
+    return {start: _batchStart, stop: experimental.addDuration(d: migration.batchInterval, to: _batchStart)}
+}
+
+// Define a static record with batch start and stop time properties
+batch = {start: batchRange().start, stop: batchRange().stop}
+
+// Check to see if the current batch start time is beyond the migration.stop
+// time and exit with an error if it is.
+finished =
+    if batch.start >= migration.stop then
+        die(msg: "Batch range is beyond the migration range. Migration is complete.")
+    else
+        "Migration in progress"
+
+// Query all data from the specified source bucket within the batch-defined time
+// range. To limit migrated data by measurement, tag, or field, add a `filter()`
+// function after `range()` with the appropriate predicate fn.
+data = () =>
+    from(host: migration.sourceHost, org: migration.sourceOrg, token: migration.sourceToken, bucket: migration.sourceBucket)
+        |> range(start: batch.start, stop: batch.stop)
+
+// rowCount is a stream of tables that contains the number of rows returned in
+// the batch and is used to generate batch metadata.
+rowCount =
+    data()
+        |> group(columns: ["_start", "_stop"])
+        |> count()
+
+// emptyRange is a stream of tables that acts as filler data if the batch is
+// empty. This is used to generate batch metadata for empty batches and is
+// necessary to correctly increment the time range for the next batch.
+emptyRange = array.from(rows: [{_start: batch.start, _stop: batch.stop, _value: 0}])
+
+// metadata returns a stream of tables representing batch metadata.
+metadata = () => {
+    _input =
+        if exists (rowCount |> findRecord(fn: (key) => true, idx: 0))._value then
+            rowCount
+        else
+            emptyRange
+
+    return
+        _input
+            |> map(
+                fn: (r) =>
+                    ({
+                        _time: now(),
+                        _measurement: "batches",
+                        srcOrg: migration.sourceOrg,
+                        srcBucket: migration.sourceBucket,
+                        dstBucket: migration.destinationBucket,
+                        batch_start: string(v: batch.start),
+                        batch_stop: string(v: batch.stop),
+                        rows: r._value,
+                        percent_complete:
+                            float(v: int(v: r._stop) - int(v: migration.start)) / float(
+                                    v: int(v: migration.stop) - int(v: migration.start),
+                                ) * 100.0,
+                    }),
+            )
+            |> group(columns: ["_measurement", "srcOrg", "srcBucket", "dstBucket"])
+}
+
+// Write the queried data to the specified InfluxDB OSS bucket.
+data()
+    |> to(bucket: migration.destinationBucket)
+
+// Generate and store batch metadata in the migration.batchBucket.
+metadata()
+    |> experimental.to(bucket: migration.batchBucket)
+```
+
+### Configuration help
+
+{{< expand-wrapper >}}
+
+<!----------------------- BEGIN Determine task interval ----------------------->
+{{% expand "Determine your task interval" %}}
+
+The task interval determines how often the migration task runs and is defined by
+the [`task.every` option](/influxdb/cloud/process-data/task-options/#every).
+InfluxDB Cloud rate limits and quotas reset every five minutes, so
+**we recommend a `5m` task interval**.
+
+You can do shorter task intervals and execute the migration task more often,
+but you need to balance the task interval with your [batch interval](#determine-your-batch-interval) 
+and the amount of data returned in each batch.
+If the total amount of data queried in each five-minute interval exceeds your
+InfluxDB Cloud organization's [rate limits and quotas](/influxdb/cloud/account-management/limits/),
+the batch will fail until rate limits and quotas reset.
+
+{{% /expand %}}
+<!------------------------ END Determine task interval ------------------------>
+
+<!---------------------- BEGIN Determine migration start ---------------------->
+{{% expand "Determine your migration start time" %}}
+
+The `migration.start` time should be at or near the same time as the earliest
+data point you want to migrate.
+All migration batches are determined using the `migration.start` time and
+`migration.batchInterval` settings.
+
+To find time of the earliest point in your bucket, run the following query:
+
+```js
+from(bucket: "example-cloud-bucket")
+    |> range(start: 0)
+    |> group()
+    |> first()
+    |> keep(columns: ["_time"])
+```
+
+{{% /expand %}}
+<!----------------------- END Determine migration start ----------------------->
+
+<!----------------------- BEGIN Determine batch interval ---------------------->
+{{% expand "Determine your batch interval" %}}
+
+The `migration.batchInterval` setting controls the time range queried by each batch.
+The "density" of the data in your InfluxDB Cloud bucket and your InfluxDB Cloud
+organization's [rate limits and quotas](/influxdb/cloud/account-management/limits/)
+determine what your batch interval should be.
+
+For example, if you're migrating data collected from hundreds of sensors with
+points recorded every second, your batch interval will need to be shorter.
+If you're migrating data collected from five sensors with points recorded every
+minute, your batch interval can be longer.
+It all depends on how much data gets returned in a single batch.
+
+If points occur at regular intervals, you can get a fairly accurate estimate of
+how much data will be returned in a given time range by using the `/api/v2/query`
+endpoint to execute a query for the time range duration and then measuring the
+size of the response body.
+
+The following `curl` command queries an InfluxDB Cloud bucket for the last day
+and returns the size of the response body in bytes.
+You can customize the range duration to match your specific use case and
+data density.
+
+```sh
+INFLUXDB_CLOUD_ORG=<your_influxdb_cloud_org>
+INFLUXDB_CLOUD_TOKEN=<your_influxdb_cloud_token>
+INFLUXDB_CLOUD_BUCKET=<your_influxdb_cloud_bucket>
+
+curl -so /dev/null --request POST \
+  https://cloud2.influxdata.com/api/v2/query?org=$INFLUXDB_CLOUD_ORG  \
+  --header "Authorization: Token $INFLUXDB_CLOUD_TOKEN" \
+  --header "Accept: application/csv" \
+  --header "Content-type: application/vnd.flux" \
+  --data "from(bucket:\"$INFLUXDB_CLOUD_BUCKET\") |> range(start: -1d, stop: now())" \
+  --write-out '%{size_download}'
+```
+
+{{% note %}}
+You can also use other HTTP API tools like [Postman](https://www.postman.com/)
+that provide the size of the response body.
+{{% /note %}}
+
+Divide the output of this command by 1000000 to convert it to megabytes (MB).
+
+```
+batchInterval = (write-rate-limit-mb / response-body-size-mb) * range-duration
+```
+
+For example, if the response body of your query that returns data from one day 
+is 1 MB and you're using the InfluxDB Cloud Free Plan with a write limit of
+5 MB per five minutes:
+
+```js
+batchInterval = (5 / 1) * 1d
+// batchInterval = 5d
+```
+
+You _could_ query 5 days of data before hitting your write limit, but this is just an estimate.
+We recommend setting the `batchInterval` slightly lower than the calculated interval
+to allow for variation between batches.
+
+So in this example, **it would be best to set your `batchInterval` to `4d`**.
+
+##### Important things to note
+- This assumes no other queries are running in your source InfluxDB Cloud organization.
+- This assumes no other writes are happening in your destination InfluxDB Cloud organization.
+{{% /expand %}}
+<!------------------------ END Determine batch interval ----------------------->
+{{< /expand-wrapper >}}
+
+## Monitor the migration progress
+The [InfluxDB Cloud Migration Community template](https://github.com/influxdata/community-templates/tree/master/influxdb-cloud-oss-migration/)
+installs the migration task outlined in this guide as well as a dashboard
+for monitoring running data migrations.
+
+{{< img-hd src="/img/influxdb/2-1-migration-dashboard.png" alt="InfluxDB Cloud migration dashboard" />}}
+
+<a class="btn" href="https://github.com/influxdata/community-templates/tree/master/influxdb-cloud-oss-migration/#quick-install">Install the InfluxDB Cloud Migration template</a>
+
+## Troubleshoot migration task failures
+If the migration task fails, [view your task logs](/influxdb/cloud/process-data/manage-tasks/task-run-history/)
+to identify the specific error. Below are common causes of migration task failures.
+
+- [Exceeded rate limits](#exceeded-rate-limits)
+- [Invalid API token](#invalid-api-token)
+- [Query timeout](#query-timeout)
+
+### Exceeded rate limits
+If your data migration causes you to exceed your InfluxDB Cloud organization's
+limits and quotas, the task will return an error similar to:
+
+```
+too many requests
+```
+
+**Possible solutions**:
+- Update the `migration.batchInterval` setting in your migration task to use
+  a smaller interval. Each batch will then query less data.
+
+### Invalid API token
+If the API token you add as the `INFLUXDB_CLOUD_SECRET` doesn't have read access to
+your InfluxDB Cloud bucket, the task will return an error similar to:
+
+```
+unauthorized access
+```
+
+**Possible solutions**:
+- Ensure the API token has read access to your InfluxDB Cloud bucket.
+- Generate a new InfluxDB Cloud API token with read access to the bucket you
+  want to migrate. Then, update the `INFLUXDB_CLOUD_TOKEN` secret in your
+  InfluxDB OSS instance with the new token.
+
+### Query timeout
+The InfluxDB Cloud query timeout is 90 seconds. If it takes longer than this to
+return the data from the batch interval, the query will time out and the
+task will fail.
+
+**Possible solutions**:
+- Update the `migration.batchInterval` setting in your migration task to use
+  a smaller interval. Each batch will then query less data and take less time
+  to return results.
diff --git a/content/influxdb/cloud/migrate-data/migrate-cloud-to-oss.md b/content/influxdb/cloud/migrate-data/migrate-cloud-to-oss.md
new file mode 100644
index 000000000..b1336208d
--- /dev/null
+++ b/content/influxdb/cloud/migrate-data/migrate-cloud-to-oss.md
@@ -0,0 +1,13 @@
+---
+title: Migrate data from InfluxDB Cloud to InfluxDB OSS
+description: >
+  To migrate data from InfluxDB Cloud to InfluxDB OSS, query the data from
+  InfluxDB Cloud in time-based batches and write the data to InfluxDB OSS.
+menu:
+  influxdb_cloud:
+    name: Migrate from Cloud to OSS
+    parent: Migrate data
+weight: 103
+---
+
+{{< duplicate-oss >}}
diff --git a/content/influxdb/cloud/migrate-data/migrate-oss.md b/content/influxdb/cloud/migrate-data/migrate-oss.md
new file mode 100644
index 000000000..bb3fcc962
--- /dev/null
+++ b/content/influxdb/cloud/migrate-data/migrate-oss.md
@@ -0,0 +1,13 @@
+---
+title: Migrate data from InfluxDB OSS to InfluxDB Cloud
+description: >
+  To migrate data from an InfluxDB OSS bucket to an InfluxDB Cloud bucket, export
+  your data as line protocol and then write it to your InfluxDB Cloud bucket.
+menu:
+  influxdb_cloud:
+    name: Migrate data from OSS
+    parent: Migrate data
+weight: 101
+---
+
+{{< duplicate-oss >}}
diff --git a/content/influxdb/cloud/organizations/buckets/create-bucket.md b/content/influxdb/cloud/organizations/buckets/create-bucket.md
index 3f9e8975a..c7eb1b938 100644
--- a/content/influxdb/cloud/organizations/buckets/create-bucket.md
+++ b/content/influxdb/cloud/organizations/buckets/create-bucket.md
@@ -59,9 +59,13 @@ to create a new bucket. A bucket requires the following:
   - days (`d`)
   - weeks (`w`)
 
+  {{% note %}}
+  The minimum retention period is **one hour**.
+  {{% /note %}}
+
 ```sh
 # Syntax
-influx bucket create -n <bucket-name> -o <org-name> -r <retention-period-duration>
+influx bucket create -n <BUCKET_NAME> -o <INFLUX_ORG> -r <RETENTION_PERIOD_DURATION>
 
 # Example
 influx bucket create -n my-bucket -o my-org -r 72h
diff --git a/content/influxdb/cloud/organizations/buckets/delete-bucket.md b/content/influxdb/cloud/organizations/buckets/delete-bucket.md
index b6de8c85b..d95d74550 100644
--- a/content/influxdb/cloud/organizations/buckets/delete-bucket.md
+++ b/content/influxdb/cloud/organizations/buckets/delete-bucket.md
@@ -49,7 +49,7 @@ influx bucket delete -n my-bucket -o my-org
 <!-- -->
 ```sh
 # Syntax
-influx bucket delete -i <bucket-id>
+influx bucket delete -i <BUCKET_ID>
 
 # Example
 influx bucket delete -i 034ad714fdd6f000
diff --git a/content/influxdb/cloud/organizations/buckets/update-bucket.md b/content/influxdb/cloud/organizations/buckets/update-bucket.md
index 791137682..676fa2ec8 100644
--- a/content/influxdb/cloud/organizations/buckets/update-bucket.md
+++ b/content/influxdb/cloud/organizations/buckets/update-bucket.md
@@ -71,7 +71,20 @@ influx bucket update -i 034ad714fdd6f000 -n my-new-bucket
 
 ##### Update a bucket's retention period
 
-Valid retention period duration units are nanoseconds (`ns`), microseconds (`us` or `µs`), milliseconds (`ms`), seconds (`s`), minutes (`m`), hours (`h`), days (`d`), or weeks (`w`).
+Valid retention period duration units:
+
+- nanoseconds (`ns`)
+- microseconds (`us` or `µs`)
+- milliseconds (`ms`)
+- seconds (`s`)
+- minutes (`m`)
+- hours (`h`)
+- days (`d`)
+- weeks (`w`)
+
+{{% note %}}
+The minimum retention period is **one hour**.
+{{% /note %}}
 
 ```sh
 # Syntax
diff --git a/content/influxdb/cloud/organizations/users.md b/content/influxdb/cloud/organizations/users.md
index 4969f783e..ee4c53b66 100644
--- a/content/influxdb/cloud/organizations/users.md
+++ b/content/influxdb/cloud/organizations/users.md
@@ -7,7 +7,7 @@ weight: 106
 menu:
   influxdb_cloud:
     parent: Manage organizations
-    name: Manage Users
+    name: Manage users
 aliases:
   - /influxdb/v2.0/account-management/multi-user/
   - /influxdb/cloud/account-management/multi-user/
@@ -16,7 +16,7 @@ aliases:
   - /influxdb/cloud/users/
 ---
 
-{{< cloud-name >}} lets you invite and collaborate with multiple users in your organization. 
+{{< cloud-name >}} lets you invite and collaborate with multiple users in your organization.
 By default, each user has full permissions on resources in your organization.
 
 - [Users management page](#users-management-page)
@@ -26,16 +26,16 @@ By default, each user has full permissions on resources in your organization.
 - [Remove a user from your organization](#remove-a-user-from-your-organization)
   - [Remove yourself from an organization](#remove-yourself-from-an-organization)
 
-## Users management page
-Manage your organization's users from your organization's **Users management page**.
+## Members page
+Manage your organization's users from your organization's **Members page**.
 In the {{< cloud-name "short" >}} user interface (UI), click your user avatar in the left
-navigation menu, and select **Users**.
+navigation menu, and select **Organization** > **Members**.
 
 {{< nav-icon "account" >}}
 
 ## Invite a user to your organization
 
-1.  Navigate to your organization's [Users management page](#users-management-page).
+1.  Navigate to your organization's [Members page](#members-page).
 2.  Under **Add a new user to your organization**, enter the email address of
     the user to invite and select their role in your organization.
 
@@ -57,22 +57,17 @@ Accounts can have up to 50 pending invitations at one time.
 
 ### Resend an invitation
 
-1.  Navigate to your organization's [Users management page](#users-management-page).
+1.  Navigate to your organization's [Members page](#members-page).
 2.  Click the **{{< icon "refresh" >}}** icon next to the invitation you want to resend.
 
 ### Withdraw an invitation
 
-1.  Navigate to your organization's [Users management page](#users-management-page).
+1.  Navigate to your organization's [Members page](#members-page).
 2.  Click the **{{< icon "delete" >}}** icon next to the invitation you want to withdraw.
 3.  Click **{{< caps >}}Withdraw Invitation{{< /caps >}}**.
 
 ## Remove a user from your organization
 
-1.  Navigate to your organization's [Users management page](#users-management-page).
+1.  Navigate to your organization's [Members page](#members-page).
 2.  Click the **{{< icon "delete" >}}** icon next to the user you want to remove.
 3.  Click **{{< caps >}}Remove user access{{< /caps >}}**.
-
-### Remove yourself from an organization 
-
-You cannot remove yourself from an organization.
-Have another member of your organization remove you. 
diff --git a/content/influxdb/cloud/process-data/common-tasks/downsample-data.md b/content/influxdb/cloud/process-data/common-tasks/downsample-data.md
index 8c3b14441..1fc48d5e8 100644
--- a/content/influxdb/cloud/process-data/common-tasks/downsample-data.md
+++ b/content/influxdb/cloud/process-data/common-tasks/downsample-data.md
@@ -48,21 +48,19 @@ The example task script below is a very basic form of data downsampling that doe
 
 ```js
 // Task Options
-option task = {
-  name: "cq-mem-data-1w",
-  every: 1w,
-}
+// Task Options
+option task = {name: "cq-mem-data-1w", every: 1w}
 
 // Defines a data source
 data = from(bucket: "system-data")
-  |> range(start: -duration(v: int(v: task.every) * 2))
-  |> filter(fn: (r) => r._measurement == "mem")
+    |> range(start: -duration(v: int(v: task.every) * 2))
+    |> filter(fn: (r) => r._measurement == "mem")
 
 data
-  // Windows and aggregates the data in to 1h averages
-  |> aggregateWindow(fn: mean, every: 1h)
-  // Stores the aggregated data in a new bucket
-  |> to(bucket: "system-data-downsampled", org: "my-org")
+    // Windows and aggregates the data in to 1h averages
+    |> aggregateWindow(fn: mean, every: 1h)
+    // Stores the aggregated data in a new bucket
+    |> to(bucket: "system-data-downsampled", org: "my-org")
 ```
 
 Again, this is a very basic example, but it should provide you with a foundation
diff --git a/content/influxdb/cloud/query-data/execute-queries/query-demo-data.md b/content/influxdb/cloud/query-data/execute-queries/query-demo-data.md
index c86742747..87186a701 100644
--- a/content/influxdb/cloud/query-data/execute-queries/query-demo-data.md
+++ b/content/influxdb/cloud/query-data/execute-queries/query-demo-data.md
@@ -25,7 +25,7 @@ types of demo data that let you explore and familiarize yourself with InfluxDB C
 {{% note %}}
 #### Free to use and read-only
 - InfluxDB Cloud demo data buckets are **free to use** and are **_not_ subject to
-  [Free Plan](/influxdb/cloud/account-management/pricing-plans/#free-plan) rate limits**.
+  [Free Plan rate limits](influxdb/cloud/account-management/limits/#free-plan-rate-limits) rate limits**.
 - Demo data buckets are **read-only**. You cannot write data into demo data buckets.
 {{% /note %}}
 
diff --git a/content/influxdb/cloud/query-data/flux/custom-functions/_index.md b/content/influxdb/cloud/query-data/flux/custom-functions/_index.md
index 689a1f73b..19bc72ffd 100644
--- a/content/influxdb/cloud/query-data/flux/custom-functions/_index.md
+++ b/content/influxdb/cloud/query-data/flux/custom-functions/_index.md
@@ -10,12 +10,11 @@ menu:
 weight: 220
 list_code_example: |
   ```js
-  multByX = (tables=<-, x) =>
-    tables
-      |> map(fn: (r) => ({ r with _value: r._value * x}))
+  multByX = (tables=<-, x) => tables
+      |> map(fn: (r) => ({r with _value: r._value * x}))
 
   data
-    |> multByX(x: 2.0)
+      |> multByX(x: 2.0)
   ```
 ---
 
diff --git a/content/influxdb/cloud/query-data/flux/exists.md b/content/influxdb/cloud/query-data/flux/exists.md
index e3acb0326..3a30f6e8a 100644
--- a/content/influxdb/cloud/query-data/flux/exists.md
+++ b/content/influxdb/cloud/query-data/flux/exists.md
@@ -18,7 +18,7 @@ list_code_example: |
   ##### Filter null values
   ```js
   data
-    |> filter(fn: (r) => exists r._value)
+      |> filter(fn: (r) => exists r._value)
   ```
 ---
 
diff --git a/content/influxdb/cloud/query-data/flux/geo/_index.md b/content/influxdb/cloud/query-data/flux/geo/_index.md
index e049882b4..f13d116c4 100644
--- a/content/influxdb/cloud/query-data/flux/geo/_index.md
+++ b/content/influxdb/cloud/query-data/flux/geo/_index.md
@@ -15,8 +15,8 @@ list_code_example: |
   import "experimental/geo"
 
   sampleGeoData
-    |> geo.filterRows(region: {lat: 30.04, lon: 31.23, radius: 200.0})
-    |> geo.groupByArea(newColumn: "geoArea", level: 5)
+      |> geo.filterRows(region: {lat: 30.04, lon: 31.23, radius: 200.0})
+      |> geo.groupByArea(newColumn: "geoArea", level: 5)
   ```
 ---
 
diff --git a/content/influxdb/cloud/query-data/flux/geo/filter-by-region.md b/content/influxdb/cloud/query-data/flux/geo/filter-by-region.md
index a076d7f7b..94d515eae 100644
--- a/content/influxdb/cloud/query-data/flux/geo/filter-by-region.md
+++ b/content/influxdb/cloud/query-data/flux/geo/filter-by-region.md
@@ -15,10 +15,7 @@ list_code_example: |
   import "experimental/geo"
 
   sampleGeoData
-    |> geo.filterRows(
-      region: {lat: 30.04, lon: 31.23, radius: 200.0},
-      strict: true
-    )
+      |> geo.filterRows(region: {lat: 30.04, lon: 31.23, radius: 200.0}, strict: true)
   ```
 ---
 
diff --git a/content/influxdb/cloud/query-data/flux/geo/group-geo-data.md b/content/influxdb/cloud/query-data/flux/geo/group-geo-data.md
index 598e2272c..b2359d0b4 100644
--- a/content/influxdb/cloud/query-data/flux/geo/group-geo-data.md
+++ b/content/influxdb/cloud/query-data/flux/geo/group-geo-data.md
@@ -16,8 +16,8 @@ list_code_example: |
   import "experimental/geo"
 
   sampleGeoData
-    |> geo.groupByArea(newColumn: "geoArea", level: 5)
-    |> geo.asTracks(groupBy: ["id"],sortBy: ["_time"])
+      |> geo.groupByArea(newColumn: "geoArea", level: 5)
+      |> geo.asTracks(groupBy: ["id"],sortBy: ["_time"])
   ```
 ---
 
diff --git a/content/influxdb/cloud/query-data/flux/geo/shape-geo-data.md b/content/influxdb/cloud/query-data/flux/geo/shape-geo-data.md
index e5c73b561..fc97a3dcc 100644
--- a/content/influxdb/cloud/query-data/flux/geo/shape-geo-data.md
+++ b/content/influxdb/cloud/query-data/flux/geo/shape-geo-data.md
@@ -17,15 +17,17 @@ list_code_example: |
   import "experimental/geo"
 
   sampleGeoData
-    |> map(fn: (r) => ({ r with
-      _field:
-        if r._field == "latitude" then "lat"
-        else if r._field == "longitude" then "lon"
-        else r._field
-      }))
-    |> map(fn: (r) => ({ r with
-      s2_cell_id: geo.s2CellIDToken(point: {lon: r.lon, lat: r.lat}, level: 10)
-    }))  
+      |> map(
+          fn: (r) => ({r with
+              _field: if r._field == "latitude" then
+                  "lat"
+              else if r._field == "longitude" then
+                  "lon"
+              else
+                  r._field,
+          }),
+      )
+      |> map(fn: (r) => ({r with s2_cell_id: geo.s2CellIDToken(point: {lon: r.lon, lat: r.lat}, level: 10)}))
   ```
 ---
 
diff --git a/content/influxdb/cloud/query-data/flux/query-fields.md b/content/influxdb/cloud/query-data/flux/query-fields.md
index 0a194d259..8d65fb94e 100644
--- a/content/influxdb/cloud/query-data/flux/query-fields.md
+++ b/content/influxdb/cloud/query-data/flux/query-fields.md
@@ -17,12 +17,8 @@ related:
 list_code_example: |
   ```js
   from(bucket: "example-bucket")
-    |> range(start: -1h)
-    |> filter(fn: (r) =>
-        r._measurement == "example-measurement" and
-        r._field == "example-field" and
-        r.tag == "example-tag"
-    )
+      |> range(start: -1h)
+      |> filter(fn: (r) => r._measurement == "example-measurement" and r._field == "example-field" and r.tag == "example-tag")
   ```
 ---
 
diff --git a/content/influxdb/cloud/query-data/flux/scalar-values.md b/content/influxdb/cloud/query-data/flux/scalar-values.md
index 1c549022b..cb89eb9e9 100644
--- a/content/influxdb/cloud/query-data/flux/scalar-values.md
+++ b/content/influxdb/cloud/query-data/flux/scalar-values.md
@@ -14,11 +14,11 @@ related:
   - /{{< latest "flux" >}}/function-types/#dynamic-queries, Flux dynamic query functions
 list_code_example: |
   ```js
-  scalarValue = {
-    _record =
-      data
-        |> findRecord(fn: key => true, idx: 0)
-    return _record._value
+  scalarValue = (tables=<-) => {
+      _record = tables
+          |> findRecord(fn: (key) => true, idx: 0)
+
+      return _record._value
   }
   ```
 ---
diff --git a/content/influxdb/cloud/query-data/flux/sql.md b/content/influxdb/cloud/query-data/flux/sql.md
index 9c9083c8d..3ec223700 100644
--- a/content/influxdb/cloud/query-data/flux/sql.md
+++ b/content/influxdb/cloud/query-data/flux/sql.md
@@ -19,9 +19,9 @@ list_code_example: |
   import "sql"
 
   sql.from(
-    driverName: "postgres",
-    dataSourceName: "postgresql://user:password@localhost",
-    query: "SELECT * FROM example_table"
+      driverName: "postgres",
+      dataSourceName: "postgresql://user:password@localhost",
+      query: "SELECT * FROM example_table",
   )
   ```
 ---
diff --git a/content/influxdb/cloud/query-data/parameterized-queries.md b/content/influxdb/cloud/query-data/parameterized-queries.md
index eb0455b6e..07fb7e48b 100644
--- a/content/influxdb/cloud/query-data/parameterized-queries.md
+++ b/content/influxdb/cloud/query-data/parameterized-queries.md
@@ -43,16 +43,16 @@ For example, using the example `params` JSON above, the following query
 
 ```js
 from(bucket: params.ex1)
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == params.ex2)
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == params.ex2)
 ```
 
 would execute as
 
 ```js
 from(bucket: "foo")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "bar")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "bar")
 ```
 
 ## Example
@@ -67,8 +67,8 @@ To use a parameterized query, do the following:
 
     ```js
     from(bucket: params.mybucket)
-      |> range(start: -7d)
-      |> limit(n:2)
+        |> range(start: -7d)
+        |> limit(n:2)
     ```
 2. Use the InfluxDB Cloud `/api/v2/query` API endpoint to execute your query.
    Provide the following in your request body:
@@ -103,8 +103,8 @@ For example, to define the `start` parameter of the `range()` function using a p
     
     ```js
     from(bucket:"example-bucket")
-      |> range(start: duration(v: params.mystart))
-      |> limit(n:2)
+        |> range(start: duration(v: params.mystart))
+        |> limit(n:2)
     ```
 
 2. In the `param` field of your query request body, format the duration parameter as a string:
diff --git a/content/influxdb/cloud/reference/api/influxdb-1x/_index.md b/content/influxdb/cloud/reference/api/influxdb-1x/_index.md
index 5b5bb0552..cd7c0d34b 100644
--- a/content/influxdb/cloud/reference/api/influxdb-1x/_index.md
+++ b/content/influxdb/cloud/reference/api/influxdb-1x/_index.md
@@ -9,9 +9,8 @@ menu:
     parent: InfluxDB v2 API
 weight: 104
 influxdb/cloud/tags: [influxql, query, write]
-products: [cloud]
 related:
   - /influxdb/cloud/query-data/influxql
 ---
 
-{{% duplicate-oss %}}
+{{< duplicate-oss >}}
diff --git a/content/influxdb/cloud/reference/api/influxdb-1x/query.md b/content/influxdb/cloud/reference/api/influxdb-1x/query.md
index d45905cb0..d1f91a5ed 100644
--- a/content/influxdb/cloud/reference/api/influxdb-1x/query.md
+++ b/content/influxdb/cloud/reference/api/influxdb-1x/query.md
@@ -9,7 +9,6 @@ menu:
     parent: 1.x compatibility
 weight: 301
 influxdb/cloud/tags: [influxql, query]
-products: [cloud]
 list_code_example: |
   <pre>
   <span class="api get">GET</span> https://cloud2.influxdata.com/query
diff --git a/content/influxdb/cloud/reference/api/influxdb-1x/write.md b/content/influxdb/cloud/reference/api/influxdb-1x/write.md
index db7fcddee..ee3cc2ee5 100644
--- a/content/influxdb/cloud/reference/api/influxdb-1x/write.md
+++ b/content/influxdb/cloud/reference/api/influxdb-1x/write.md
@@ -10,7 +10,6 @@ menu:
     parent: 1.x compatibility
 weight: 301
 influxdb/cloud/tags: [write]
-products: [cloud]
 list_code_example: |
   <pre>
   <span class="api post">POST</span> https://cloud2.influxdata.com/write
diff --git a/content/influxdb/cloud/reference/cli/influx/remote/_index.md b/content/influxdb/cloud/reference/cli/influx/remote/_index.md
new file mode 100644
index 000000000..6875564b8
--- /dev/null
+++ b/content/influxdb/cloud/reference/cli/influx/remote/_index.md
@@ -0,0 +1,15 @@
+---
+title: influx remote
+description: Manage remote InfluxDB connections for replicating data.
+menu:
+  influxdb_cloud_ref:
+    name: influx remote
+    parent: influx
+weight: 101
+influxdb/cloud/tags: [write, replication]
+related:
+  - /influxdb/cloud/reference/cli/influx/replication
+  - /influxdb/cloud/write-data/replication
+---
+
+{{< duplicate-oss >}}
diff --git a/content/influxdb/cloud/reference/cli/influx/remote/create.md b/content/influxdb/cloud/reference/cli/influx/remote/create.md
new file mode 100644
index 000000000..b4bcd6755
--- /dev/null
+++ b/content/influxdb/cloud/reference/cli/influx/remote/create.md
@@ -0,0 +1,14 @@
+---
+title: influx remote create
+description: Create a new remote InfluxDB connection for replicating data.
+menu:
+  influxdb_cloud_ref:
+    name: influx remote create
+    parent: influx remote
+weight: 101
+influxdb/cloud/tags: [write, replication]
+related:
+  - /influxdb/cloud/reference/cli/influx/replication
+---
+
+{{< duplicate-oss >}}
diff --git a/content/influxdb/cloud/reference/cli/influx/remote/delete.md b/content/influxdb/cloud/reference/cli/influx/remote/delete.md
new file mode 100644
index 000000000..c58ee6401
--- /dev/null
+++ b/content/influxdb/cloud/reference/cli/influx/remote/delete.md
@@ -0,0 +1,14 @@
+---
+title: influx remote delete
+description: Delete remote InfluxDB connections used for replicating data.
+menu:
+  influxdb_cloud_ref:
+    name: influx remote delete
+    parent: influx remote
+weight: 102
+influxdb/cloud/tags: [write, replication]
+related:
+  - /influxdb/cloud/reference/cli/influx/replication
+---
+
+{{< duplicate-oss >}}
diff --git a/content/influxdb/cloud/reference/cli/influx/remote/list.md b/content/influxdb/cloud/reference/cli/influx/remote/list.md
new file mode 100644
index 000000000..b689a60ee
--- /dev/null
+++ b/content/influxdb/cloud/reference/cli/influx/remote/list.md
@@ -0,0 +1,14 @@
+---
+title: influx remote list
+description: List remote InfluxDB connections sued for replicating data.
+menu:
+  influxdb_cloud_ref:
+    name: influx remote list
+    parent: influx remote
+weight: 102
+influxdb/cloud/tags: [write, replication]
+related:
+  - /influxdb/cloud/reference/cli/influx/replication
+---
+
+{{< duplicate-oss >}}
diff --git a/content/influxdb/cloud/reference/cli/influx/remote/update.md b/content/influxdb/cloud/reference/cli/influx/remote/update.md
new file mode 100644
index 000000000..277855c78
--- /dev/null
+++ b/content/influxdb/cloud/reference/cli/influx/remote/update.md
@@ -0,0 +1,14 @@
+---
+title: influx remote update
+description: Update remote InfluxDB connections used for for replicating data.
+menu:
+  influxdb_cloud_ref:
+    name: influx remote update
+    parent: influx remote
+weight: 102
+influxdb/cloud/tags: [write, replication]
+related:
+  - /influxdb/cloud/reference/cli/influx/replication
+---
+
+{{< duplicate-oss >}}
diff --git a/content/influxdb/cloud/reference/cli/influx/replication/_index.md b/content/influxdb/cloud/reference/cli/influx/replication/_index.md
new file mode 100644
index 000000000..9351f6da6
--- /dev/null
+++ b/content/influxdb/cloud/reference/cli/influx/replication/_index.md
@@ -0,0 +1,14 @@
+---
+title: influx replication
+description: Use the `influx` CLI to manage InfluxDB replication streams.
+menu:
+  influxdb_cloud_ref:
+    name: influx replication
+    parent: influx
+weight: 101
+influxdb/cloud/tags: [write, replication]
+related:
+  - /influxdb/cloud/reference/cli/influx/remote
+---
+
+{{< duplicate-oss >}}
diff --git a/content/influxdb/cloud/reference/cli/influx/replication/create.md b/content/influxdb/cloud/reference/cli/influx/replication/create.md
new file mode 100644
index 000000000..54105343d
--- /dev/null
+++ b/content/influxdb/cloud/reference/cli/influx/replication/create.md
@@ -0,0 +1,14 @@
+---
+title: influx replication create
+description: Create a new InfluxDB replication stream.
+menu:
+  influxdb_cloud_ref:
+    name: influx replication create
+    parent: influx replication
+weight: 101
+influxdb/cloud/tags: [write]
+related:
+  - /influxdb/cloud/reference/cli/influx/replication
+---
+
+{{< duplicate-oss >}}
diff --git a/content/influxdb/cloud/reference/cli/influx/replication/delete.md b/content/influxdb/cloud/reference/cli/influx/replication/delete.md
new file mode 100644
index 000000000..18ee2c99c
--- /dev/null
+++ b/content/influxdb/cloud/reference/cli/influx/replication/delete.md
@@ -0,0 +1,14 @@
+---
+title: influx replication delete
+description: Delete an InfluxDB replication stream.
+menu:
+  influxdb_cloud_ref:
+    name: influx replication delete
+    parent: influx replication
+weight: 102
+influxdb/cloud/tags: [write, replication]
+related:
+  - /influxdb/cloud/reference/cli/influx/replication
+---
+
+{{< duplicate-oss >}}
diff --git a/content/influxdb/cloud/reference/cli/influx/replication/list.md b/content/influxdb/cloud/reference/cli/influx/replication/list.md
new file mode 100644
index 000000000..020fa3d89
--- /dev/null
+++ b/content/influxdb/cloud/reference/cli/influx/replication/list.md
@@ -0,0 +1,14 @@
+---
+title: influx replication list
+description: List InfluxDB replication streams and corresponding metrics.
+menu:
+  influxdb_cloud_ref:
+    name: influx replication list
+    parent: influx replication
+weight: 102
+influxdb/cloud/tags: [write, replication]
+related:
+  - /influxdb/cloud/reference/cli/influx/replication
+---
+
+{{< duplicate-oss >}}
diff --git a/content/influxdb/cloud/reference/cli/influx/replication/update.md b/content/influxdb/cloud/reference/cli/influx/replication/update.md
new file mode 100644
index 000000000..839e21f06
--- /dev/null
+++ b/content/influxdb/cloud/reference/cli/influx/replication/update.md
@@ -0,0 +1,14 @@
+---
+title: influx replication update
+description: Update InfluxDB replication streams.
+menu:
+  influxdb_cloud_ref:
+    name: influx replication update
+    parent: influx replication
+weight: 102
+influxdb/cloud/tags: [write, replication]
+related:
+  - /influxdb/cloud/reference/cli/influx/replication
+---
+
+{{< duplicate-oss >}}
diff --git a/content/influxdb/cloud/reference/internals/data-retention.md b/content/influxdb/cloud/reference/internals/data-retention.md
new file mode 100644
index 000000000..2c11923c7
--- /dev/null
+++ b/content/influxdb/cloud/reference/internals/data-retention.md
@@ -0,0 +1,42 @@
+---
+title: Data retention in InfluxDB Cloud
+description: >
+  The InfluxDB Cloud retention service checks for and removes data with timestamps
+  beyond the defined retention period of the bucket the data is stored in.
+weight: 103
+menu:
+  influxdb_cloud_ref:
+    name: Data retention
+    parent: InfluxDB Cloud internals
+influxdb/cloud/tags: [internals]
+---
+
+The **InfluxDB Cloud retention enforcement service** checks for and removes data
+with timestamps beyond the defined retention period of the
+[bucket](/influxdb/cloud/reference/glossary/#bucket) the data is stored in.
+This service is designed to automatically delete "expired" data and optimize disk
+usage without any user intervention.
+
+- [Bucket retention period](#bucket-retention-period)
+- [When does data actually get deleted?](#when-does-data-actually-get-deleted)
+
+## Bucket retention period
+A **bucket retention period** is the duration of time that a bucket retains data.
+Retention periods can be as short as an hour or infinite.
+[Points](/influxdb/cloud/reference/glossary/#point) in a bucket with timestamps
+beyond the defined retention period (relative to now) are flagged for deletion
+(also known as "tombstoned").
+
+{{% note %}}
+#### View bucket retention periods
+Use the [`influx bucket list` command](/influxdb/cloud/reference/cli/influx/bucket/list/)
+to view the retention period buckets in your organization.
+{{% /note %}}
+
+## When does data actually get deleted?
+The InfluxDB Cloud retention enforcement service **runs hourly** and tombstones
+all points with timestamps beyond the bucket retention period.
+Tombstoned points persist on disk, but are filtered from all query results until
+the next [compaction](/influxdb/cloud/reference/glossary/#compaction) cycle,
+when they are removed from disk.
+Compaction cycle intervals vary.
diff --git a/content/influxdb/cloud/reference/internals/durability.md b/content/influxdb/cloud/reference/internals/durability.md
index 020460fa9..99281da31 100644
--- a/content/influxdb/cloud/reference/internals/durability.md
+++ b/content/influxdb/cloud/reference/internals/durability.md
@@ -18,12 +18,13 @@ data is consistent and readable.
 
 ##### On this page
 
-- [Data replication](#data-replication)
+<!-- [Data replication](#data-replication)
+-->
 - [Backup processes](#backup-processes)
 - [Recovery](#recovery)
 - [Data verification](#data-verification)
 
-## Data replication
+<!-- ## Data replication
 InfluxDB Cloud replicates data in both the write tier and the storage tier.
 
 - **Write tier:** all data written to InfluxDB is processed by a durable message queue.
@@ -31,12 +32,14 @@ InfluxDB Cloud replicates data in both the write tier and the storage tier.
   replicates each partition across other physical nodes in the message queue.
 - **Storage tier:** all data in the underlying storage tier is replicated across
   two availability zones in a cloud region.
+-->
 
 ## Backup processes
 InfluxDB Cloud backs up all data in the following way:
 
 - [Backup on write](#backup-on-write)
 - [Backup after compaction](#backup-after-compaction)
+- [Periodic TSM snapshots](#periodic-tsm-snapshots)
 
 ### Backup on write
 All inbound write requests to InfluxDB Cloud are added to a durable message queue.
@@ -63,17 +66,22 @@ When each compaction cycle completes, InfluxDB Cloud stores compressed
 [TSM](/influxdb/cloud/reference/glossary/#tsm-time-structured-merge-tree) files
 in object storage.
 
+### Periodic TSM snapshots
+To provide multiple data recovery points, InfluxDB Cloud takes weekly snapshots of TSM files uploaded to object storage. The TSM snapshot includes a copy of all (non-deleted) data when the snapshot is created.
+These snapshots are preserved for 100 days.
+
 ## Recovery
 InfluxDB Cloud uses the following out-of-band backups stored in object storage to recover data:
 
 - **Message queue backup:** line protocol from inbound write requests within the last 96 hours
-- **Historic backup:** compressed TSM files
+- **Compaction backup:** TSM files
+- **TSM snapshots:** Weekly snapshots of TSM files in objectstore
 
 The Recovery Point Objective (RPO) is any accepted write.
 The Recovery Time Objective (RTO) is harder to definitively predict as potential failure modes can vary.
 While most common failure modes can be resolved within minutes or hours,
 critical failure modes may take longer.
-For example, if we need to rebuild all data from the message queue backup,
+For example, if we need to rebuild all data from the TSM snapshots and message queue backup,
 it could take 24 hours or longer.
 
 ## Data verification
diff --git a/content/influxdb/cloud/reference/internals/security.md b/content/influxdb/cloud/reference/internals/security.md
index c618c02f0..a01c41d8d 100644
--- a/content/influxdb/cloud/reference/internals/security.md
+++ b/content/influxdb/cloud/reference/internals/security.md
@@ -242,4 +242,4 @@ For users needing stricter security around data access and risk mitigation measu
 ## Compliance and auditing
 
 InfluxDB Cloud is **SOC2 Type II** certified.
-To request a copy of our SOC2 Type II report, please email <security@influxdata.com>.
+To request a copy of our SOC2 Type II report, please email <sales@influxdata.com>.
diff --git a/content/influxdb/cloud/reference/prometheus-metrics.md b/content/influxdb/cloud/reference/prometheus-metrics.md
index 3449e0f9a..f1a3885db 100644
--- a/content/influxdb/cloud/reference/prometheus-metrics.md
+++ b/content/influxdb/cloud/reference/prometheus-metrics.md
@@ -12,7 +12,7 @@ related:
   - https://prometheus.io/docs/concepts/data_model/, Prometheus data model
   - /influxdb/cloud/write-data/developer-tools/scrape-prometheus-metrics/
   - /{{< latest "flux" >}}/prometheus/, Work with Prometheus in Flux
-  - /{{< latest "telegraf" >}}/plugins/#prometheus, Telegraf Prometheus input plugin
+  - /{{< latest "telegraf" >}}/input-prometheus, Telegraf Prometheus input plugin
   - /{{< latest "flux" >}}/stdlib/experimental/prometheus/scrape/
 ---
 
diff --git a/content/influxdb/cloud/reference/regions.md b/content/influxdb/cloud/reference/regions.md
index e2555b575..5049dc568 100644
--- a/content/influxdb/cloud/reference/regions.md
+++ b/content/influxdb/cloud/reference/regions.md
@@ -19,4 +19,16 @@ Use the URLs below to interact with your InfluxDB Cloud instances with the
 
 <a href="https://www.influxdata.com/influxdb-cloud-2-0-provider-region/" target="_blank" class="btn">Request a cloud region</a>
 
+{{% note %}}
+#### Regions with multiple clusters
+Some InfluxDB Cloud regions have multiple Cloud clusters, each with a unique URL.
+To find your cluster URL, [log in to your InfluxDB Cloud organization](https://cloud2.influxdata.com)
+and review your organization URL. The first subdomain identifies your 
+InfluxDB Cloud cluster. For example:
+
+<pre class="highlight">
+https://<span class="bp" style="font-weight:bold;margin:0 .15rem">us-west-2-1</span>.aws.cloud2.influxdata.com/orgs/03a2bbf46249a000/...
+</pre>
+{{% /note %}}
+
 {{< cloud_regions >}}
diff --git a/content/influxdb/cloud/reference/release-notes/cloud-updates.md b/content/influxdb/cloud/reference/release-notes/cloud-updates.md
index cb147efe5..8e64e8a0a 100644
--- a/content/influxdb/cloud/reference/release-notes/cloud-updates.md
+++ b/content/influxdb/cloud/reference/release-notes/cloud-updates.md
@@ -14,10 +14,35 @@ aliases:
 InfluxDB Cloud updates occur frequently. Find a compilation of recent updates below.
 To find information about the latest Flux updates in InfluxDB Cloud, see [Flux release notes](/influxdb/cloud/reference/release-notes/flux/).
 
-<!-- ## January 2022
+## March 2022
+
+### Deep linking
+
+Navigate to UI pages without having to enter your organization ID in the URL using deep links. For example, `cloud2.influxdata.com/me/billing` redirects to your organization's billing page.
+
+## February 2022
+
+### Remove yourself from an organization
+
+You can now remove yourself as a member of an organization in the Cloud UI. For details, see [Remove a user from your organization](/influxdb/cloud/organizations/users/#remove-a-user-from-your-organization/).
+
+### Add auto-refresh functionality to Notebooks
+
+Automatically refresh Notebooks data. For details, see [Create a notebook](/influxdb/cloud/notebooks/create-notebook/).
+
+## Performance improvements to dashboards and queries
+
+Previously, InfluxDB loaded all variables on the client side, even those not included in a dashboard or query. Now, InfluxDB only loads variables used by queries or dashboards.
+
+## January 2022
+
 ### Update Tokens UI
 
-To enhance security, the Token UI will only display an InfluxDB Cloud token when it's first created. If you return to the Token page later, you will not be able to view or copy the token. -->
+To enhance security, the Tokens UI will only display an InfluxDB Cloud token when it's [first created](/influxdb/cloud/security/tokens/create-token/). If you return to the Token page later, you won't be able to view or copy the token. To learn more about token access restrictions, see [Create an API token](/influxdb/cloud/security/tokens/create-token/).
+
+### Multi-account support
+
+You can now invite a user to join an organization using the same email they've used in another InfluxDB Cloud account. Users [can switch between accounts in the UI](/influxdb/cloud/account-management/switch-account/).
 
 ## December 2021
 
diff --git a/content/influxdb/cloud/reference/sample-data.md b/content/influxdb/cloud/reference/sample-data.md
index ed38e96e0..10e7b6c98 100644
--- a/content/influxdb/cloud/reference/sample-data.md
+++ b/content/influxdb/cloud/reference/sample-data.md
@@ -142,16 +142,15 @@ To do so, run the following:
 ```js
 import "experimental/csv"
 
-relativeToNow = (tables=<-) =>
-  tables
+relativeToNow = (tables=<-) => tables
     |> elapsed()
     |> sort(columns: ["_time"], desc: true)
     |> cumulativeSum(columns: ["elapsed"])
-    |> map(fn: (r) => ({ r with _time: time(v: int(v: now()) - (r.elapsed * 1000000000))}))
+    |> map(fn: (r) => ({r with _time: time(v: int(v: now()) - r.elapsed * 1000000000)}))
 
 csv.from(url: "https://influx-testdata.s3.amazonaws.com/noaa.csv")
-  |> relativeToNow()
-  |> to(bucket: "noaa", org: "example-org")
+    |> relativeToNow()
+    |> to(bucket: "noaa", org: "example-org")
 ```
 {{% /note %}}
 
@@ -186,10 +185,9 @@ Add the following as an [InfluxDB task](/influxdb/cloud/process-data/manage-task
 
 ```js
 import "influxdata/influxdb/sample"
-option task = {
-  name: "Collect NOAA NDBC data"
-  every: 15m,
-}
+
+option task = {name: "Collect NOAA NDBC data", every: 15m}
+
 sample.data(set: "noaa")
-  |> to(bucket: "noaa"  )
+    |> to(bucket: "noaa")
  ```
diff --git a/content/influxdb/cloud/security/secrets/use.md b/content/influxdb/cloud/security/secrets/use.md
index 119935f31..8adb814bf 100644
--- a/content/influxdb/cloud/security/secrets/use.md
+++ b/content/influxdb/cloud/security/secrets/use.md
@@ -23,8 +23,8 @@ username = secrets.get(key: "POSTGRES_USERNAME")
 password = secrets.get(key: "POSTGRES_PASSWORD")
 
 sql.from(
-  driverName: "postgres",
-  dataSourceName: "postgresql://${username}:${password}@localhost",
-  query:"SELECT * FROM example-table"
+    driverName: "postgres",
+    dataSourceName: "postgresql://${username}:${password}@localhost",
+    query:"SELECT * FROM example-table",
 )
 ```
diff --git a/content/influxdb/cloud/sign-up.md b/content/influxdb/cloud/sign-up.md
index 815b8cec2..65d3e0811 100644
--- a/content/influxdb/cloud/sign-up.md
+++ b/content/influxdb/cloud/sign-up.md
@@ -30,10 +30,10 @@ The primary differences between InfluxDB OSS 2.0 and InfluxDB Cloud are:
 
 Start using {{< cloud-name >}} at no cost with the [Free Plan](/influxdb/cloud/account-management/pricing-plans/#free-plan).
 Use it as much and as long as you like within the plan's rate-limits.
-Limits are designed to let you monitor 5-10 sensors, stacks or servers comfortably.
+[Limits](/influxdb/cloud/account-management/limits/) are designed to let you monitor 5-10 sensors, stacks or servers comfortably.
 
 {{% note %}}
-Users on the Free Plan are limited to one organization. 
+Users on the Free Plan are limited to one organization.
 {{% /note %}}
 
 ## Sign up
diff --git a/content/influxdb/cloud/tools/grafana.md b/content/influxdb/cloud/tools/grafana.md
index f54f633f1..71eea89e5 100644
--- a/content/influxdb/cloud/tools/grafana.md
+++ b/content/influxdb/cloud/tools/grafana.md
@@ -60,10 +60,11 @@ configure your InfluxDB connection:
     - **Default Bucket**: The default [bucket](/influxdb/cloud/organizations/buckets/) to use in Flux queries.
     - **Min time interval**: The [Grafana minimum time interval](https://grafana.com/docs/grafana/latest/features/datasources/influxdb/#min-time-interval).
 
-    {{< img-hd src="/img/influxdb/cloud-tools-grafana.png" />}}
-
 2. Click **Save & Test**. Grafana attempts to connect to the InfluxDB datasource
    and returns the results of the test.
+
+{{< img-hd src="/img/influxdb/cloud-tools-grafana.png" />}}
+
 {{% /tab-content %}}
 <!----------------------------- END FLUX CONTENT ----------------------------->
 <!-------------------------- BEGIN INFLUXQL CONTENT -------------------------->
@@ -194,11 +195,11 @@ With **InfluxQL** selected as the query language in your InfluxDB data source se
     - **Password**: Leave empty
     - **HTTP Method**: Select **GET**
 
-    <!--  -->
-    {{< img-hd src="/img/influxdb/cloud-tools-grafana-influxql.png" />}}
-
 3. Click **Save & Test**. Grafana attempts to connect to the InfluxDB Cloud data source
    and returns the results of the test.
+
+{{< img-hd src="/img/influxdb/cloud-tools-grafana-influxql.png" />}}
+
 {{% /tab-content %}}
 <!--------------------------- END INFLUXQL CONTENT --------------------------->
 {{< /tabs-wrapper >}}
diff --git a/content/influxdb/cloud/tools/repl.md b/content/influxdb/cloud/tools/repl.md
index 07fc66ab2..08fcf9776 100644
--- a/content/influxdb/cloud/tools/repl.md
+++ b/content/influxdb/cloud/tools/repl.md
@@ -43,10 +43,10 @@ to the [`from()` function](/influxdb/cloud/reference/flux/stdlib/built-in/inputs
 
 ```js
 from(
-  bucket: "example-bucket",
-  host: "https://cloud2.influxdata.com",
-  org: "example-org",
-  token: "My5uP3rS3cRetT0k3n"
+    bucket: "example-bucket",
+    host: "https://cloud2.influxdata.com",
+    org: "example-org",
+    token: "My5uP3rS3cRetT0k3n"
 )
 ```
 
diff --git a/content/influxdb/cloud/upgrade/v1-to-cloud/_index.md b/content/influxdb/cloud/upgrade/v1-to-cloud/_index.md
index f3c3ba95b..3c40e1f4c 100644
--- a/content/influxdb/cloud/upgrade/v1-to-cloud/_index.md
+++ b/content/influxdb/cloud/upgrade/v1-to-cloud/_index.md
@@ -238,8 +238,8 @@ See [Required InfluxDB Cloud credentials](#required-influxdb-cloud-credentials)
 
 {{% note %}}
 #### InfluxDB Cloud write rate limits
-Write requests are subject to rate limits associated with your
-[InfluxDB Cloud pricing plan](/influxdb/cloud/account-management/pricing-plans/).
+Read and write requests are subject to [rate limits](/influxdb/cloud/account-management/limits/#rate-limits) associated with your
+InfluxDB Cloud plan.
 If your exported line protocol size potentially exceeds your rate limits,
 include the `--rate-limit` flag with `influx write` to rate limit written data.
 
diff --git a/content/influxdb/cloud/upgrade/v1-to-cloud/migrate-cqs.md b/content/influxdb/cloud/upgrade/v1-to-cloud/migrate-cqs.md
index 1e687348f..d012c235e 100644
--- a/content/influxdb/cloud/upgrade/v1-to-cloud/migrate-cqs.md
+++ b/content/influxdb/cloud/upgrade/v1-to-cloud/migrate-cqs.md
@@ -58,21 +58,15 @@ END
 
 ##### Equivalent Flux task
 ```js
-option task = {
-  name: "downsample-daily",
-  every: 1d
-}
+option task = {name: "downsample-daily", every: 1d}
 
 from(bucket: "my-db/")
-  |> range(start: -task.every)
-  |> filter(fn: (r) => r._measurement == "example-measurement")
-  |> filter(fn: (r) => r._field == "example-field")
-  |> aggregateWindow(every: 1h, fn: mean)
-  |> set(key: "_measurement", value: "average-example-measurement")
-  |> to(
-    org: "example-org",
-    bucket: "my-db/example-rp"
-  )
+    |> range(start: -task.every)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> filter(fn: (r) => r._field == "example-field")
+    |> aggregateWindow(every: 1h, fn: mean)
+    |> set(key: "_measurement", value: "average-example-measurement")
+    |> to(org: "example-org", bucket: "my-db/example-rp")
 ```
 
 ### Convert InfluxQL continuous queries to Flux
@@ -142,15 +136,15 @@ INTO "example-db"."example-rp"."example-measurement"
 {{% code-tab-content %}}
 ```js
 // ...
-  |> set(key: "_measurement", value: "example-measurement")
-  |> to(bucket: "example-db/example-rp")
+    |> set(key: "_measurement", value: "example-measurement")
+    |> to(bucket: "example-db/example-rp")
 ```
 {{% /code-tab-content %}}
 {{% code-tab-content %}}
 ```js
 // ...
-  |> map(fn: (r) => ({ r with _measurement: "example-measurement"}))
-  |> to(bucket: "example-db/example-rp")
+    |> map(fn: (r) => ({ r with _measurement: "example-measurement"}))
+    |> to(bucket: "example-db/example-rp")
 ```
 {{% /code-tab-content %}}
 {{< /code-tabs-wrapper >}}
@@ -181,12 +175,12 @@ END
 // ...
 
 from(bucket: "my-db/")
-  |> range(start: -task.every)
-  |> filter(fn: (r) => r._measurement == "example-measurement")
-  |> filter(fn: (r) => r._field == "example-field-1" or r._field == "example-field-2")
-  |> aggregateWindow(every: task.every, fn: mean)
-  |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
-  |> experimental.to(bucket: "example-db/example-rp")
+    |> range(start: -task.every)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> filter(fn: (r) => r._field == "example-field-1" or r._field == "example-field-2")
+    |> aggregateWindow(every: task.every, fn: mean)
+    |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
+    |> experimental.to(bucket: "example-db/example-rp")
 ```
 
 #### FROM clause
@@ -204,7 +198,7 @@ FROM "example-measurement"
 ###### Flux
 ```js
 // ...
-  |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> filter(fn: (r) => r._measurement == "example-measurement")
 ```
 
 #### AS clause
@@ -229,13 +223,13 @@ AS newfield
 {{% code-tab-content %}}
 ```js
 // ...
-  |> set(key: "_field", value: "newfield")
+    |> set(key: "_field", value: "newfield")
 ```
 {{% /code-tab-content %}}
 {{% code-tab-content %}}
 ```js
 // ...
-  |> map(fn: (r) => ({ r with _field: "newfield"}))
+    |> map(fn: (r) => ({ r with _field: "newfield"}))
 ```
 {{% /code-tab-content %}}
 {{< /code-tabs-wrapper >}}
@@ -256,8 +250,8 @@ WHERE "example-tag" = "foo" AND time > now() - 7d
 ###### Flux
 ```js
 // ...
-  |> range(start: -7d)
-  |> filter(fn: (r) => r["example-tag"] == "foo")
+    |> range(start: -7d)
+    |> filter(fn: (r) => r["example-tag"] == "foo")
 ```
 
 #### GROUP BY clause
@@ -277,7 +271,7 @@ GROUP BY "location"
 ###### Flux
 ```js
 // ...
-  |> group(columns: ["location"])
+    |> group(columns: ["location"])
 ```
 
 ##### Group by time
@@ -296,17 +290,11 @@ GROUP BY time(1h)
 
 ###### Flux
 ```js
-option task = {
-  name: "task-name",
-  every: 1h
-}
+option task = {name: "task-name", every: 1h}
 
 // ...
-  |> filter(fn: (r) =>
-    r._measurement == "example-measurement" and
-    r._field == "example-field"
-  )
-  |> aggregateWindow(every: task.every, fn: mean)
+    |> filter(fn: (r) => r._measurement == "example-measurement" and r._field == "example-field")
+    |> aggregateWindow(every: task.every, fn: mean)
 ```
 
 #### RESAMPLE clause
@@ -335,22 +323,15 @@ END
 
 ###### Flux
 ```js
-option task = {
-  name: "resample-example",
-  every: 1m
-}
+option task = {name: "resample-example", every: 1m}
 
 from(bucket: "my-db/")
-  |> range(start: -30m)
-  |> filter(fn: (r) =>
-    r._measurement == "example-measurement" and
-    r._field == "example-field" and
-    r.region == "example-region"
-  )
-  |> aggregateWindow(every: 1m, fn: mean)
-  |> exponentialMovingAverage(n: 30)
-  |> set(key: "_measurement", value: "resample-average-example-measurement")
-  |> to(bucket: "my-db/")
+    |> range(start: -30m)
+    |> filter(fn: (r) => r._measurement == "example-measurement" and r._field == "example-field" and r.region == "example-region")
+    |> aggregateWindow(every: 1m, fn: mean)
+    |> exponentialMovingAverage(n: 30)
+    |> set(key: "_measurement", value: "resample-average-example-measurement")
+    |> to(bucket: "my-db/")
 ```
 
 ## Create new InfluxDB tasks
diff --git a/content/influxdb/cloud/upgrade/v2-to-cloud.md b/content/influxdb/cloud/upgrade/v2-to-cloud.md
index db40e713c..fa68c85b2 100644
--- a/content/influxdb/cloud/upgrade/v2-to-cloud.md
+++ b/content/influxdb/cloud/upgrade/v2-to-cloud.md
@@ -112,8 +112,7 @@ your **InfluxDB Cloud** instance.
 
 {{% note %}}
 #### InfluxDB Cloud Free Plan resource limits
-If upgrading to an [InfluxDB Cloud Free Plan](/influxdb/cloud/account-management/pricing-plans/#free-plan),
-you are only able to create a limited number of resources.
+If upgrading to an InfluxDB Cloud Free Plan, you are only able to create a [limited number of resources](/influxdb/cloud/account-management/limits/#free-plan-limits).
 If your exported template exceeds these limits, the resource migration will fail.
 {{% /note %}}
 
diff --git a/content/influxdb/cloud/visualize-data/variables/_index.md b/content/influxdb/cloud/visualize-data/variables/_index.md
index 9185ffcd8..1551a1214 100644
--- a/content/influxdb/cloud/visualize-data/variables/_index.md
+++ b/content/influxdb/cloud/visualize-data/variables/_index.md
@@ -23,9 +23,9 @@ Reference each variable using dot-notation (e.g. `v.variableName`).
 
 ```js
 from(bucket: v.bucket)
-  |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
-  |> filter(fn: (r) => r._measurement == v.measurement and r._field == v.field)
-  |> aggregateWindow(every: v.windowPeriod, fn: mean)
+    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
+    |> filter(fn: (r) => r._measurement == v.measurement and r._field == v.field)
+    |> aggregateWindow(every: v.windowPeriod, fn: mean)
 ```
 
 When building Flux queries for dashboard cells, view available dashboard variables
diff --git a/content/influxdb/cloud/visualize-data/variables/common-variables.md b/content/influxdb/cloud/visualize-data/variables/common-variables.md
index 2238491cf..69c36bbb7 100644
--- a/content/influxdb/cloud/visualize-data/variables/common-variables.md
+++ b/content/influxdb/cloud/visualize-data/variables/common-variables.md
@@ -19,8 +19,8 @@ _**Flux functions:**
 
 ```js
 buckets()
-  |> rename(columns: {"name": "_value"})
-  |> keep(columns: ["_value"])
+    |> rename(columns: {"name": "_value"})
+    |> keep(columns: ["_value"])
 ```
 
 ## List measurements
@@ -31,6 +31,7 @@ _**Flux package:** [InfluxDB v1](/influxdb/cloud/reference/flux/stdlib/influxdb-
 
 ```js
 import "influxdata/influxdb/v1"
+
 v1.measurements(bucket: "bucket-name")
 ```
 
@@ -42,10 +43,11 @@ _**Flux package:** [InfluxDB v1](/influxdb/cloud/reference/flux/stdlib/influxdb-
 
 ```js
 import "influxdata/influxdb/v1"
+
 v1.measurementTagValues(
-  bucket: "bucket-name",
-  measurement: "measurment-name",
-  tag: "_field"
+    bucket: "bucket-name",
+    measurement: "measurment-name",
+    tag: "_field",
 )
 ```
 
@@ -58,49 +60,53 @@ _**Flux functions:** [v1.tagValues()](/influxdb/cloud/reference/flux/stdlib/infl
 
 ```js
 import "influxdata/influxdb/v1"
+
 v1.tagValues(bucket: "bucket-name", tag: "host")
 ```
 
 ## List Docker containers
 List all Docker containers when using the Docker Telegraf plugin.
 
-_**Telegraf plugin:** [Docker](/{{< latest "telegraf" >}}/plugins/#docker)_  
+_**Telegraf plugin:** [Docker](/{{< latest "telegraf" >}}/plugins/#input-docker)_  
 _**Flux package:** [InfluxDB v1](/influxdb/cloud/reference/flux/stdlib/influxdb-v1/)_  
 _**Flux functions:** [v1.tagValues()](/influxdb/cloud/reference/flux/stdlib/influxdb-v1/tagvalues/)_
 
 ```js
 import "influxdata/influxdb/v1"
+
 v1.tagValues(bucket: "bucket-name", tag: "container_name")
 ```
 
 ## List Kubernetes pods
 List all Kubernetes pods when using the Kubernetes Telegraf plugin.
 
-_**Telegraf plugin:** [Kubernetes](/{{< latest "telegraf" >}}/plugins/#kubernetes)_  
+_**Telegraf plugin:** [Kubernetes](/{{< latest "telegraf" >}}/plugins/#input-kubernetes)_  
 _**Flux package:** [InfluxDB v1](/influxdb/cloud/reference/flux/stdlib/influxdb-v1/)_  
 _**Flux functions:** [v1.measurementTagValues()](/influxdb/cloud/reference/flux/stdlib/influxdb-v1/measurementtagvalues/)_
 
 ```js
 import "influxdata/influxdb/v1"
+
 v1.measurementTagValues(
-  bucket: "bucket-name",
-  measurement: "kubernetes_pod_container",
-  tag: "pod_name"
+    bucket: "bucket-name",
+    measurement: "kubernetes_pod_container",
+    tag: "pod_name",
 )
 ```
 
 ## List Kubernetes nodes
 List all Kubernetes nodes when using the Kubernetes Telegraf plugin.
 
-_**Telegraf plugin:** [Kubernetes](/{{< latest "telegraf" >}}/plugins/#kubernetes)_  
+_**Telegraf plugin:** [Kubernetes](/{{< latest "telegraf" >}}/plugins/#input-kubernetes)_  
 _**Flux package:** [InfluxDB v1](/influxdb/cloud/reference/flux/stdlib/influxdb-v1/)_  
 _**Flux functions:** [v1.measurementTagValues()](/influxdb/cloud/reference/flux/stdlib/influxdb-v1/measurementtagvalues/)_
 
 ```js
 import "influxdata/influxdb/v1"
+
 v1.measurementTagValues(
-  bucket: "bucket-name",
-  measurement: "kubernetes_node",
-  tag: "node_name"
+    bucket: "bucket-name",
+    measurement: "kubernetes_node",
+    tag: "node_name",
 )
 ```
diff --git a/content/influxdb/cloud/visualize-data/variables/variable-types.md b/content/influxdb/cloud/visualize-data/variables/variable-types.md
index 68b814b90..7c28b358b 100644
--- a/content/influxdb/cloud/visualize-data/variables/variable-types.md
+++ b/content/influxdb/cloud/visualize-data/variables/variable-types.md
@@ -39,8 +39,8 @@ Query variable values are populated using the `_value` column of a Flux query.
 ```js
 // List all buckets
 buckets()
-  |> rename(columns: {"name": "_value"})
-  |> keep(columns: ["_value"])
+    |> rename(columns: {"name": "_value"})
+    |> keep(columns: ["_value"])
 ```
 
 _For examples of dashboard variable queries, see [Common variable queries](/influxdb/cloud/visualize-data/variables/common-variables)._
diff --git a/content/influxdb/cloud/visualize-data/visualization-types/map.md b/content/influxdb/cloud/visualize-data/visualization-types/map.md
index 0ae9ba9a0..d7f64e293 100644
--- a/content/influxdb/cloud/visualize-data/visualization-types/map.md
+++ b/content/influxdb/cloud/visualize-data/visualization-types/map.md
@@ -84,11 +84,11 @@ to display the migration path of a specific bird.
 
 ```js
 from(bucket: "migration")
-  |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
-  |> filter(fn: (r) => r._measurement == "migration")
-  |> filter(fn: (r) => r._field == "lat" or r._field == "lon")
-  |> filter(fn: (r) => r.id == "91864A")  
-  |> aggregateWindow(every: v.windowPeriod, fn: last)
+    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
+    |> filter(fn: (r) => r._measurement == "migration")
+    |> filter(fn: (r) => r._field == "lat" or r._field == "lon")
+    |> filter(fn: (r) => r.id == "91864A")  
+    |> aggregateWindow(every: v.windowPeriod, fn: last)
 ```
 
 ### View earthquakes reported by USGS
@@ -96,8 +96,8 @@ The following query uses the [United States Geological Survey (USGS) earthquake
 
 ```js
 from(bucket: "usgs")
-  |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
-  |> filter(fn: (r) => r._measurement == "earthquakes")
-  |> filter(fn: (r) => r._field == "lat" or r._field == "lon")
+    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
+    |> filter(fn: (r) => r._measurement == "earthquakes")
+    |> filter(fn: (r) => r._field == "lat" or r._field == "lon")
 ```
 
diff --git a/content/influxdb/cloud/write-data/bulk-ingest-cloud.md b/content/influxdb/cloud/write-data/bulk-ingest-cloud.md
index d6287822c..ecc6586bc 100644
--- a/content/influxdb/cloud/write-data/bulk-ingest-cloud.md
+++ b/content/influxdb/cloud/write-data/bulk-ingest-cloud.md
@@ -9,7 +9,6 @@ menu:
   influxdb_cloud:
     name: Bulk ingest
     parent: Write data
-products: [cloud]
 alias:
   - /influxdb/v2.0/write-data/bulk-ingest-cloud
 ---
diff --git a/content/influxdb/cloud/write-data/delete-data.md b/content/influxdb/cloud/write-data/delete-data.md
index 39714aee9..d4ccba6c3 100644
--- a/content/influxdb/cloud/write-data/delete-data.md
+++ b/content/influxdb/cloud/write-data/delete-data.md
@@ -2,7 +2,8 @@
 title: Delete data
 list_title: Delete data
 description: >
-  Delete data in the InfluxDB CLI and API.
+  Use the `influx` CLI or the InfluxDB API `/api/v2/delete` endpoint to delete
+  data from an InfluxDB Bucket.
 menu:
   influxdb_cloud:
     name: Delete data
diff --git a/content/influxdb/cloud/write-data/developer-tools/scrape-prometheus-metrics.md b/content/influxdb/cloud/write-data/developer-tools/scrape-prometheus-metrics.md
index c34ce2527..01f5c0ae9 100644
--- a/content/influxdb/cloud/write-data/developer-tools/scrape-prometheus-metrics.md
+++ b/content/influxdb/cloud/write-data/developer-tools/scrape-prometheus-metrics.md
@@ -10,7 +10,7 @@ menu:
     name: Scrape Prometheus metrics
     parent: Developer tools
 related:
-  - /{{< latest "telegraf" >}}/plugins/#prometheus, Telegraf Prometheus input plugin
+  - /{{< latest "telegraf" >}}/plugins/#input-prometheus, Telegraf Prometheus input plugin
   - /{{< latest "flux" >}}/prometheus/scrape-prometheus/
   - /{{< latest "flux" >}}/stdlib/experimental/prometheus/scrape/
   - /{{< latest "flux" >}}/prometheus/metric-types/
diff --git a/content/influxdb/cloud/write-data/no-code/use-telegraf/auto-config.md b/content/influxdb/cloud/write-data/no-code/use-telegraf/auto-config.md
index b96c25985..0b796ab3e 100644
--- a/content/influxdb/cloud/write-data/no-code/use-telegraf/auto-config.md
+++ b/content/influxdb/cloud/write-data/no-code/use-telegraf/auto-config.md
@@ -29,7 +29,7 @@ for using Telegraf with InfluxDB v2.0._
 
 ## Create a Telegraf configuration
 
-1. Open the InfluxDB Clou UI.
+1. Open the InfluxDB Cloud UI.
 2. In the navigation menu on the left, select **Data** (**Load Data**) > **Telegraf**.
 
     {{< nav-icon "load data" >}}
diff --git a/content/influxdb/cloud/write-data/replication.md b/content/influxdb/cloud/write-data/replication.md
new file mode 100644
index 000000000..371f8ff3f
--- /dev/null
+++ b/content/influxdb/cloud/write-data/replication.md
@@ -0,0 +1,17 @@
+---
+title: Replicate data from InfluxDB OSS to InfluxDB Cloud
+weight: 106
+description: >
+  Use InfluxDB replication streams to replicate all data written to an InfluxDB OSS
+  instance to InfluxDB Cloud.
+menu:
+  influxdb_cloud:
+    name: Replicate data
+    parent: Write data
+influxdb/cloud/tags: [write, replication]
+related:
+  - /influxdb/cloud/reference/cli/influx/remote
+  - /influxdb/cloud/reference/cli/influx/replication
+---
+
+{{< duplicate-oss >}}
diff --git a/content/influxdb/cloud/write-data/troubleshoot.md b/content/influxdb/cloud/write-data/troubleshoot.md
index baa60c5a0..2a8642254 100644
--- a/content/influxdb/cloud/write-data/troubleshoot.md
+++ b/content/influxdb/cloud/write-data/troubleshoot.md
@@ -14,6 +14,7 @@ related:
   - /influxdb/cloud/api/#tag/Write, InfluxDB API /write endpoint
   - /influxdb/cloud/reference/internals
   - /influxdb/cloud/reference/cli/influx/write
+  - influxdb/cloud/account-management/limits
 ---
 
 Learn how to handle and recover from errors when writing to InfluxDB.
@@ -29,8 +30,8 @@ Write requests made to InfluxDB may fail for a number of reasons.
 Common failure scenarios that return an HTTP `4xx` or `5xx` error status code include the following:
 
 - API token was invalid. See how to [manage API tokens](/influxdb/cloud/security/tokens/).
-- Exceeded a rate limit.
-- Payload size was too large.
+- Requests exceeded [service quotas](/influxdb/cloud/account-management/limits/#adjustable-service-quotas).
+- Payload size exceeded [global limits](/influxdb/cloud/account-management/limits/#global-limits).
 - Client or server reached a timeout threshold.
 - Data was not formatted correctly. See how to [find parsing errors](#find-parsing-errors)
 - Data did not conform to the [explicit bucket schema](/influxdb/cloud/organizations/buckets/bucket-schema/).
@@ -46,28 +47,25 @@ To resolve partial writes and rejected points, see [troubleshoot failures](#trou
 ## Review HTTP status codes
 
 InfluxDB uses conventional HTTP status codes to indicate the success or failure of a request.
+
+{{% warn %}}
+#### Asynchronous writes
+
+`204` indicates InfluxDB validated the request data format. Because data is written to InfluxDB asynchronously, data may not yet be written to a bucket. If some of your data didn't write to the bucket, see how to [check for rejected points](#review-rejected-points).
+{{% /warn %}}
+
 Write requests return the following status codes:
 
-- `204` **Success**: InfluxDB validated the request data format and accepted the data for writing to the bucket.
-    {{% note %}}
-  `204` doesn't indicate a successful write operation given writes are asynchronous. If some of your data did not write to the bucket, see how to [check for rejected points](#review-rejected-points).
-    {{% /note %}}
-- `400` **Bad request**: InfluxDB rejected some or all of the request data.
-  `code` and `message` in the response body provide details about the problem.
-  For more information, see how to [troubleshoot rejected points](#troubleshoot-rejected-points).
-- `401` **Unauthorized**: May indicate one of the following:
-  -  [`Authorization: Token` header](/influxdb/cloud/api-guide/api_intro/#authentication) is missing or malformed.
-  - [API token](/influxdb/cloud/api-guide/api_intro/#authentication) value is missing from the header.
-  - API token does not have sufficient permissions to write to the organization and bucket.
-    For more information about token types and permissions, see [Manage API tokens](/influxdb/cloud/security/tokens/)
-- `404` **Not found**: A requested resource (e.g. an organization or bucket) was not found.
-  The response body contains the requested resource type, e.g. "organization", and resource name.
-- `413` **Request entity too large**: Occurs in the following cases:
-   - The write request payload exceeds the size limit **50 MB** (compressed or uncompressed).
-   - A compressed payload attempts to uncompress more than **250 MB** of data.
-- `429` **Too many requests**: API token is temporarily over quota. The `Retry-After` header describes when to try the write request again.
-- `500` **Internal server error**: Default HTTP status for an error.
-- `503` **Service unavailable**: Server is temporarily unavailable to accept writes. The `Retry-After` header describes when to try the write again.
+| HTTP response code              | Message                                                                 | Description    |
+| :-------------------------------| :---------------------------------------------------------------        | :------------- |
+| `204 "Success"`                 |                                                                         | If InfluxDB validated the request data format and accepted the data for writing to the bucket |
+| `400 "Bad request"`             | `message` contains the first malformed line                             | If data is malformed    |
+| `401 "Unauthorized"`            |                                                                         | If the [`Authorization: Token` header](/influxdb/cloud/api-guide/api_intro/#authentication) is missing or malformed or if the [API token](/influxdb/cloud/api-guide/api_intro/#authentication) doesn't have [permission](/influxdb/cloud/security/tokens/) to write to the bucket |
+| `404 "Not found"`               | requested **resource type**, e.g. "organization", and **resource name**     | If a requested resource (e.g. organization or bucket) wasn't found. |
+| `413 “Request too large”`       | cannot read data: points in batch is too large                          | If a **write** request exceeds the maximum [global limit](/influxdb/cloud/account-management/limits/#global-limits) |  
+| `429 “Too many requests”`       | `Retry-After` header: xxx (seconds to wait before retrying the request) | If a **read** or **write** request exceeds your plan's [adjustable service quotas](/influxdb/cloud/account-management/limits/#adjustable-service-quotas) or if a **delete** request exceeds the maximum [global limit](/influxdb/cloud/account-management/limits/#global-limits) |
+| `500 "Internal server error"`   |                                                                         | Default status for an error |
+| `503 “Service unavailable“` | Series cardinality exceeds your plan's service quota                        | If **series cardinality** exceeds your plan's [adjustable service quotas](/influxdb/cloud/account-management/limits/#adjustable-service-quotas) |
 
 The `message` property of the response body may contain additional details about the error.
 
@@ -125,9 +123,9 @@ To find parsing error details, query `rejected_points` entries that contain the
 
 ```js
 from(bucket: "_monitoring")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "rejected_points")
-  |> filter(fn: (r) => r._field == "error")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "rejected_points")
+    |> filter(fn: (r) => r._field == "error")
 ```
 
 #### Find data type conflicts and schema rejections
@@ -137,9 +135,9 @@ query for the `count` field.
 
 ```js
 from(bucket: "_monitoring")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "rejected_points")
-  |> filter(fn: (r) => r._field == "count")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "rejected_points")
+    |> filter(fn: (r) => r._field == "count")
 ```
 
 ### Resolve data type conflicts
diff --git a/content/influxdb/v1.3/tools/collectd.md b/content/influxdb/v1.3/tools/collectd.md
index 437f7ff47..a351157d6 100644
--- a/content/influxdb/v1.3/tools/collectd.md
+++ b/content/influxdb/v1.3/tools/collectd.md
@@ -6,7 +6,8 @@ menu:
   influxdb_1_3:
     weight: 80
     parent: Tools
-    url: https://github.com/influxdata/influxdb/blob/master/services/collectd/README.md
+    params:
+      url: https://github.com/influxdata/influxdb/blob/master/services/collectd/README.md
 ---
 
 See the [README](https://github.com/influxdata/influxdb/blob/master/services/collectd/README.md) on GitHub.
diff --git a/content/influxdb/v1.3/tools/graphite.md b/content/influxdb/v1.3/tools/graphite.md
index 15a8cd2ee..364889f1a 100644
--- a/content/influxdb/v1.3/tools/graphite.md
+++ b/content/influxdb/v1.3/tools/graphite.md
@@ -6,7 +6,8 @@ menu:
   influxdb_1_3:
     weight: 70
     parent: Tools
-    url: https://github.com/influxdata/influxdb/blob/master/services/graphite/README.md
+    params:
+      url: https://github.com/influxdata/influxdb/blob/master/services/graphite/README.md
 ---
 
 See the [README](https://github.com/influxdata/influxdb/blob/master/services/graphite/README.md) on GitHub.
diff --git a/content/influxdb/v1.3/tools/opentsdb.md b/content/influxdb/v1.3/tools/opentsdb.md
index aa716d836..e8932225d 100644
--- a/content/influxdb/v1.3/tools/opentsdb.md
+++ b/content/influxdb/v1.3/tools/opentsdb.md
@@ -6,7 +6,8 @@ menu:
   influxdb_1_3:
     weight: 90
     parent: Tools
-    url: https://github.com/influxdb/influxdb/blob/1.3/services/opentsdb/README.md
+    params:
+      url: https://github.com/influxdb/influxdb/blob/1.3/services/opentsdb/README.md
 ---
 
 See the [README](https://github.com/influxdata/influxdb/blob/master/services/opentsdb/README.md) on GitHub.
diff --git a/content/influxdb/v1.3/tools/udp.md b/content/influxdb/v1.3/tools/udp.md
index e4ccd4c80..44e4a4d82 100644
--- a/content/influxdb/v1.3/tools/udp.md
+++ b/content/influxdb/v1.3/tools/udp.md
@@ -6,7 +6,8 @@ menu:
   influxdb_1_3:
     weight: 60
     parent: Tools
-    url: https://github.com/influxdata/influxdb/blob/master/services/udp/README.md
+    params:
+      url: https://github.com/influxdata/influxdb/blob/master/services/udp/README.md
 ---
 
 See the [README](https://github.com/influxdata/influxdb/blob/master/services/udp/README.md) on GitHub.
diff --git a/content/influxdb/v1.6/troubleshooting/frequently-asked-questions.md b/content/influxdb/v1.6/troubleshooting/frequently-asked-questions.md
index 6d91d6bd8..4108575a2 100644
--- a/content/influxdb/v1.6/troubleshooting/frequently-asked-questions.md
+++ b/content/influxdb/v1.6/troubleshooting/frequently-asked-questions.md
@@ -15,66 +15,66 @@ Where applicable, it links to outstanding issues on GitHub.
 
 **Administration**
 
-* [How do I include a single quote in a password?](#how-do-i-include-a-single-quote-in-a-password)
-* [How can I identify my version of InfluxDB?](#how-can-i-identify-my-version-of-influxdb)
-* [Where can I find InfluxDB logs?](#where-can-i-find-influxdb-logs)
-* [What is the relationship between shard group durations and retention policies?](#what-is-the-relationship-between-shard-group-durations-and-retention-policies)
-* [Why aren't data dropped after I've altered a retention policy?](#why-aren-t-data-dropped-after-i-ve-altered-a-retention-policy)
-* [Why does InfluxDB fail to parse microsecond units in the configuration file?](#why-does-influxdb-fail-to-parse-microsecond-units-in-the-configuration-file)
+- [How do I include a single quote in a password?](#how-do-i-include-a-single-quote-in-a-password)
+- [How can I identify my version of InfluxDB?](#how-can-i-identify-my-version-of-influxdb)
+- [Where can I find InfluxDB logs?](#where-can-i-find-influxdb-logs)
+- [What is the relationship between shard group durations and retention policies?](#what-is-the-relationship-between-shard-group-durations-and-retention-policies)
+- [Why aren't data dropped after I've altered a retention policy?](#why-aren-t-data-dropped-after-i-ve-altered-a-retention-policy)
+- [Why does InfluxDB fail to parse microsecond units in the configuration file?](#why-does-influxdb-fail-to-parse-microsecond-units-in-the-configuration-file)
 
 **Command Line Interface (CLI)**
 
-* [How do I make InfluxDB’s CLI return human readable timestamps?](#how-do-i-make-influxdb-s-cli-return-human-readable-timestamps)
-* [How can a non-admin user `USE` a database in InfluxDB's CLI?](#how-can-a-non-admin-user-use-a-database-in-influxdb-s-cli)
-* [How do I write to a non-`DEFAULT` retention policy with InfluxDB's CLI?](#how-do-i-write-to-a-non-default-retention-policy-with-influxdb-s-cli)
-* [How do I cancel a long-running query?](#how-do-i-cancel-a-long-running-query)
+- [How do I make InfluxDB’s CLI return human readable timestamps?](#how-do-i-make-influxdb-s-cli-return-human-readable-timestamps)
+- [How can a non-admin user `USE` a database in InfluxDB's CLI?](#how-can-a-non-admin-user-use-a-database-in-influxdb-s-cli)
+- [How do I write to a non-`DEFAULT` retention policy with InfluxDB's CLI?](#how-do-i-write-to-a-non-default-retention-policy-with-influxdb-s-cli)
+- [How do I cancel a long-running query?](#how-do-i-cancel-a-long-running-query)
 
 **Data Types**
 
-* [Why can't I query Boolean field values?](#why-can-t-i-query-boolean-field-values)
-* [How does InfluxDB handle field type discrepancies across shards?](#how-does-influxdb-handle-field-type-discrepancies-across-shards)
-* [What are the minimum and maximum integers that InfluxDB can store?](#what-are-the-minimum-and-maximum-integers-that-influxdb-can-store)
-* [What are the minimum and maximum timestamps that InfluxDB can store?](#what-are-the-minimum-and-maximum-timestamps-that-influxdb-can-store)
-* [How can I tell what type of data is stored in a field?](#how-can-i-tell-what-type-of-data-is-stored-in-a-field)
-* [Can I change a field's data type?](#can-i-change-a-field-s-data-type)
+- [Why can't I query Boolean field values?](#why-can-t-i-query-boolean-field-values)
+- [How does InfluxDB handle field type discrepancies across shards?](#how-does-influxdb-handle-field-type-discrepancies-across-shards)
+- [What are the minimum and maximum integers that InfluxDB can store?](#what-are-the-minimum-and-maximum-integers-that-influxdb-can-store)
+- [What are the minimum and maximum timestamps that InfluxDB can store?](#what-are-the-minimum-and-maximum-timestamps-that-influxdb-can-store)
+- [How can I tell what type of data is stored in a field?](#how-can-i-tell-what-type-of-data-is-stored-in-a-field)
+- [Can I change a field's data type?](#can-i-change-a-field-s-data-type)
 
 **InfluxQL Functions**
 
-* [How do I perform mathematical operations within a function?](#how-do-i-perform-mathematical-operations-within-a-function)
-* [Why does my query return epoch 0 as the timestamp?](#why-does-my-query-return-epoch-0-as-the-timestamp)
-* [Which InfluxQL functions support nesting?](#which-influxql-functions-support-nesting)
+- [How do I perform mathematical operations within a function?](#how-do-i-perform-mathematical-operations-within-a-function)
+- [Why does my query return epoch 0 as the timestamp?](#why-does-my-query-return-epoch-0-as-the-timestamp)
+- [Which InfluxQL functions support nesting?](#which-influxql-functions-support-nesting)
 
 **Querying Data**
 
-* [What determines the time intervals returned by `GROUP BY time()` queries?](#what-determines-the-time-intervals-returned-by-group-by-time-queries)
-* [Why do my queries return no data or partial data?](#why-do-my-queries-return-no-data-or-partial-data)
-* [Why don't my `GROUP BY time()` queries return timestamps that occur after `now()`?](#why-don-t-my-group-by-time-queries-return-timestamps-that-occur-after-now)
-* [Can I perform mathematical operations against timestamps?](#can-i-perform-mathematical-operations-against-timestamps)
-* [Can I identify write precision from returned timestamps?](#can-i-identify-write-precision-from-returned-timestamps)
-* [When should I single quote and when should I double quote in queries?](#when-should-i-single-quote-and-when-should-i-double-quote-in-queries)
-* [Why am I missing data after creating a new `DEFAULT` retention policy?](#why-am-i-missing-data-after-creating-a-new-default-retention-policy)
-* [Why is my query with a `WHERE OR` time clause returning empty results?](#why-is-my-query-with-a-where-or-time-clause-returning-empty-results)
-* [Why does `fill(previous)` return empty results?](#why-does-fill-previous-return-empty-results)
-* [Why are my `INTO` queries missing data?](#why-are-my-into-queries-missing-data)
-* [How do I query data with an identical tag key and field key?](#how-do-i-query-data-with-an-identical-tag-key-and-field-key)
-* [How do I query data across measurements?](#how-do-i-query-data-across-measurements)
-* [Does the order of the timestamps matter?](#does-the-order-of-the-timestamps-matter)
-* [How do I `SELECT` data with a tag that has no value?](#how-do-i-select-data-with-a-tag-that-has-no-value)
+- [What determines the time intervals returned by `GROUP BY time()` queries?](#what-determines-the-time-intervals-returned-by-group-by-time-queries)
+- [Why do my queries return no data or partial data?](#why-do-my-queries-return-no-data-or-partial-data)
+- [Why don't my `GROUP BY time()` queries return timestamps that occur after `now()`?](#why-don-t-my-group-by-time-queries-return-timestamps-that-occur-after-now)
+- [Can I perform mathematical operations against timestamps?](#can-i-perform-mathematical-operations-against-timestamps)
+- [Can I identify write precision from returned timestamps?](#can-i-identify-write-precision-from-returned-timestamps)
+- [When should I single quote and when should I double quote in queries?](#when-should-i-single-quote-and-when-should-i-double-quote-in-queries)
+- [Why am I missing data after creating a new `DEFAULT` retention policy?](#why-am-i-missing-data-after-creating-a-new-default-retention-policy)
+- [Why is my query with a `WHERE OR` time clause returning empty results?](#why-is-my-query-with-a-where-or-time-clause-returning-empty-results)
+- [Why does `fill(previous)` return empty results?](#why-does-fill-previous-return-empty-results)
+- [Why are my `INTO` queries missing data?](#why-are-my-into-queries-missing-data)
+- [How do I query data with an identical tag key and field key?](#how-do-i-query-data-with-an-identical-tag-key-and-field-key)
+- [How do I query data across measurements?](#how-do-i-query-data-across-measurements)
+- [Does the order of the timestamps matter?](#does-the-order-of-the-timestamps-matter)
+- [How do I `SELECT` data with a tag that has no value?](#how-do-i-select-data-with-a-tag-that-has-no-value)
 
 **Series and Series Cardinality**
 
-* [Why does series cardinality matter?](#why-does-series-cardinality-matter)
-* [How can I remove series from the index?](#how-can-i-remove-series-from-the-index)
+- [Why does series cardinality matter?](#why-does-series-cardinality-matter)
+- [How can I remove series from the index?](#how-can-i-remove-series-from-the-index)
 
 **Writing Data**
 
-* [How do I write integer field values?](#how-do-i-write-integer-field-values)
-* [How does InfluxDB handle duplicate points?](#how-does-influxdb-handle-duplicate-points)
-* [What newline character does the HTTP API require?](#what-newline-character-does-the-http-api-require)
-* [What words and characters should I avoid when writing data to InfluxDB?](#what-words-and-characters-should-i-avoid-when-writing-data-to-influxdb)
-* [When should I single quote and when should I double quote when writing data?](#when-should-i-single-quote-and-when-should-i-double-quote-when-writing-data)
-* [Does the precision of the timestamp matter?](#does-the-precision-of-the-timestamp-matter)
-* [What are the configuration recommendations and schema guidelines for writing sparse, historical data?](#what-are-the-configuration-recommendations-and-schema-guidelines-for-writing-sparse-historical-data)
+- [How do I write integer field values?](#how-do-i-write-integer-field-values)
+- [How does InfluxDB handle duplicate points?](#how-does-influxdb-handle-duplicate-points)
+- [What newline character does the HTTP API require?](#what-newline-character-does-the-http-api-require)
+- [What words and characters should I avoid when writing data to InfluxDB?](#what-words-and-characters-should-i-avoid-when-writing-data-to-influxdb)
+- [When should I single quote and when should I double quote when writing data?](#when-should-i-single-quote-and-when-should-i-double-quote-when-writing-data)
+- [Does the precision of the timestamp matter?](#does-the-precision-of-the-timestamp-matter)
+- [What are the configuration recommendations and schema guidelines for writing sparse, historical data?](#what-are-the-configuration-recommendations-and-schema-guidelines-for-writing-sparse-historical-data)
 
 ## How do I include a single quote in a password?
 Escape the single quote with a backslash (`\`) both when creating the password
@@ -606,9 +606,9 @@ a `GROUP BY time()` clause must provide an alternative upper bound in the
 In the following example, the first query covers data with timestamps between
 `2015-09-18T21:30:00Z` and `now()`.
 The second query covers data with timestamps between `2015-09-18T21:30:00Z` and 180 weeks from `now()`.
-```
-> SELECT MEAN("boards") FROM "hillvalley" WHERE time >= '2015-09-18T21:30:00Z' GROUP BY time(12m) fill(none)
 
+```sql
+> SELECT MEAN("boards") FROM "hillvalley" WHERE time >= '2015-09-18T21:30:00Z' GROUP BY time(12m) fill(none)
 
 > SELECT MEAN("boards") FROM "hillvalley" WHERE time >= '2015-09-18T21:30:00Z' AND time <= now() + 180w GROUP BY time(12m) fill(none)
 ```
@@ -617,6 +617,7 @@ Note that the `WHERE` clause must provide an alternative **upper** bound to
 override the default `now()` upper bound. The following query merely resets
 the lower bound to `now()` such that the query's time range is between
 `now()` and `now()`:
+
 ```
 > SELECT MEAN("boards") FROM "hillvalley" WHERE time >= now() GROUP BY time(12m) fill(none)
 >
@@ -651,7 +652,9 @@ time                  value	 precision_supplied  timestamp_supplied
 1970-01-01T02:00:00Z  6      h                   2
 ```
 
-{{% warn %}} [GitHub Issue #2977](https://github.com/influxdb/influxdb/issues/2977) {{% /warn %}}
+{{% warn %}}
+[GitHub Issue #2977](https://github.com/influxdb/influxdb/issues/2977)
+{{% /warn %}}
 
 ## When should I single quote and when should I double quote in queries?
 
diff --git a/content/influxdb/v1.7/flux/get-started/_index.md b/content/influxdb/v1.7/flux/get-started/_index.md
index c5b40bfec..ff86bb7bd 100644
--- a/content/influxdb/v1.7/flux/get-started/_index.md
+++ b/content/influxdb/v1.7/flux/get-started/_index.md
@@ -113,10 +113,11 @@ The Functions pane provides a list of functions available in your Flux queries.
 
 ### 2. influx CLI
 The `influx` CLI is an interactive shell for querying InfluxDB.
-With InfluxDB v1.7+, use the `-type=flux` option to open a Flux REPL where you write and run Flux queries.
+With InfluxDB v1.7+, use the `-type=flux` and `-path-prefix=/api/v2/query` options
+to open a Flux REPL where you write and run Flux queries.
 
 ```bash
-influx -type=flux
+influx -type=flux -path-prefix=/api/v2/query
 ```
 
 <div class="page-nav-btns">
diff --git a/content/influxdb/v1.7/flux/get-started/syntax-basics.md b/content/influxdb/v1.7/flux/get-started/syntax-basics.md
index ac496c384..5ee413818 100644
--- a/content/influxdb/v1.7/flux/get-started/syntax-basics.md
+++ b/content/influxdb/v1.7/flux/get-started/syntax-basics.md
@@ -18,11 +18,12 @@ This guide walks through a handful of simple expressions and how they are handle
 
 ## Use the influx CLI
 Use the `influx` CLI in "Flux mode" as you follow this guide.
-When started with `-type=flux`, the `influx` CLI is an interactive read-eval-print-loop (REPL) that supports Flux syntax.
+When started with `-type=flux` and `-path-prefix=/api/v2/query`, the `influx`
+CLI is an interactive read-eval-print-loop (REPL) that supports Flux syntax.
 
 ##### Start in the influx CLI in Flux mode
 ```bash
-influx -type=flux
+influx -type=flux -path-prefix=/api/v2/query
 ```
 
 > If using the [InfluxData Sandbox](/platform/install-and-deploy/deploying/sandbox-install), use the `./sandbox enter`
@@ -32,7 +33,7 @@ influx -type=flux
 ```bash
 ./sandbox enter influxdb
 
-root@9bfc3c08579c:/# influx -host influxdb -type=flux
+root@9bfc3c08579c:/# influx -host influxdb -type=flux -path-prefix=/api/v2/query
 ```
 
 ## Basic Flux syntax
diff --git a/content/influxdb/v1.7/flux/guides/execute-queries.md b/content/influxdb/v1.7/flux/guides/execute-queries.md
index 6bfd352fa..8605b19d1 100644
--- a/content/influxdb/v1.7/flux/guides/execute-queries.md
+++ b/content/influxdb/v1.7/flux/guides/execute-queries.md
@@ -26,9 +26,11 @@ Chronograf v1.7+ supports Flux in its Data Explorer.
 Flux queries can be built, executed, and visualized from within the Chronograf user interface.
 
 ## Influx CLI
-InfluxDB v1.7+'s `influx` CLI includes a `-type` option which allows you specify
-what type of interactive session to start.
-`-type=flux` will start an interactive read-eval-print-loop (REPL) that supports Flux.
+To start an interactive Flux read-eval-print-loop (REPL) with the InfluxDB 1.7+
+`influx` CLI, run the `influx` command with the following flags:
+
+- `-type=flux`
+- `-path-prefix=/api/v2/query`
 
 {{% note %}}
 If [authentication is enabled](/influxdb/v1.7/administration/authentication_and_authorization)
@@ -44,12 +46,15 @@ the `-password` flag to provide your password.
 {{% /code-tabs %}}
 {{% code-tab-content %}}
 ```bash
-influx -type=flux
+influx -type=flux -path-prefix=/api/v2/query
 ```
 {{% /code-tab-content %}}
 {{% code-tab-content %}}
 ```bash
-influx -type=flux -username myuser -password PasSw0rd
+influx -type=flux \
+  -path-prefix=/api/v2/query \
+  -username myuser \
+  -password PasSw0rd
 ```
 {{% /code-tab-content %}}
 {{< /code-tabs-wrapper >}}
@@ -67,12 +72,18 @@ The accompanying string is executed as a Flux query and results are output in yo
 {{% /code-tabs %}}
 {{% code-tab-content %}}
 ```bash
-influx -type=flux -execute '<flux query>'
+influx -type=flux \
+  -path-prefix=/api/v2/query \
+  -execute '<flux query>'
 ```
 {{% /code-tab-content %}}
 {{% code-tab-content %}}
 ```bash
-influx -type=flux -username myuser -password PasSw0rd -execute '<flux query>'
+influx -type=flux \
+  -path-prefix=/api/v2/query \
+  -username myuser \
+  -password PasSw0rd \
+  -execute '<flux query>'
 ```
 {{% /code-tab-content %}}
 {{< /code-tabs-wrapper >}}
@@ -88,12 +99,15 @@ Query results are otuput in your terminal.
 {{% /code-tabs %}}
 {{% code-tab-content %}}
 ```bash
-echo '<flux query>' | influx -type=flux
+echo '<flux query>' | influx -type=flux -path-prefix=/api/v2/query
 ```
 {{% /code-tab-content %}}
 {{% code-tab-content %}}
 ```bash
-echo '<flux query>' | influx -type=flux -username myuser -password PasSw0rd
+echo '<flux query>' | influx -type=flux \
+  -path-prefix=/api/v2/query \
+  -username myuser \
+  -password PasSw0rd
 ```
 {{% /code-tab-content %}}
 {{< /code-tabs-wrapper >}}
diff --git a/content/influxdb/v1.7/flux/guides/scalar-values.md b/content/influxdb/v1.7/flux/guides/scalar-values.md
index c6ab4181e..d6c9570c1 100644
--- a/content/influxdb/v1.7/flux/guides/scalar-values.md
+++ b/content/influxdb/v1.7/flux/guides/scalar-values.md
@@ -215,7 +215,7 @@ getRow = (tables=<-, field, idx=0) => {
 // Use the helper function to define a variable
 lastReported = sampleData
   |> last()
-  |> getRow(idx: 0)
+  |> getRow(field: "temp")
 
 "The last location to report was ${lastReported.location}.
 The temperature was ${string(v: lastReported._value)}°F."
diff --git a/content/influxdb/v1.7/troubleshooting/frequently-asked-questions.md b/content/influxdb/v1.7/troubleshooting/frequently-asked-questions.md
index cb60a61ff..a7540a5d3 100644
--- a/content/influxdb/v1.7/troubleshooting/frequently-asked-questions.md
+++ b/content/influxdb/v1.7/troubleshooting/frequently-asked-questions.md
@@ -15,68 +15,68 @@ Where applicable, it links to outstanding issues on GitHub.
 
 **Administration**
 
-* [How do I include a single quote in a password?](#how-do-i-include-a-single-quote-in-a-password)
-* [How can I identify my version of InfluxDB?](#how-can-i-identify-my-version-of-influxdb)
-* [Where can I find InfluxDB logs?](#where-can-i-find-influxdb-logs)
-* [What is the relationship between shard group durations and retention policies?](#what-is-the-relationship-between-shard-group-durations-and-retention-policies)
-* [Why aren't data dropped after I've altered a retention policy?](#why-aren-t-data-dropped-after-i-ve-altered-a-retention-policy)
-* [Why does InfluxDB fail to parse microsecond units in the configuration file?](#why-does-influxdb-fail-to-parse-microsecond-units-in-the-configuration-file)
-* [Does InfluxDB have a file system size limit?](#does-influxdb-have-a-file-system-size-limit)
-* [How do I manually trigger a compaction?](#how-do-i-manually-trigger-a-compaction)
+- [How do I include a single quote in a password?](#how-do-i-include-a-single-quote-in-a-password)
+- [How can I identify my version of InfluxDB?](#how-can-i-identify-my-version-of-influxdb)
+- [Where can I find InfluxDB logs?](#where-can-i-find-influxdb-logs)
+- [What is the relationship between shard group durations and retention policies?](#what-is-the-relationship-between-shard-group-durations-and-retention-policies)
+- [Why aren't data dropped after I've altered a retention policy?](#why-aren-t-data-dropped-after-i-ve-altered-a-retention-policy)
+- [Why does InfluxDB fail to parse microsecond units in the configuration file?](#why-does-influxdb-fail-to-parse-microsecond-units-in-the-configuration-file)
+- [Does InfluxDB have a file system size limit?](#does-influxdb-have-a-file-system-size-limit)
+- [How do I manually trigger a compaction?](#how-do-i-manually-trigger-a-compaction)
 
 **Command line interface (CLI)**
 
-* [How do I make InfluxDB’s CLI return human readable timestamps?](#how-do-i-use-the-influxdb-cli-to-return-human-readable-timestamps)
-* [How can a non-admin user `USE` a database in the InfluxDB CLI?](#how-can-a-non-admin-user-use-a-database-in-the-influxdb-cli)
-* [How do I write to a non-`DEFAULT` retention policy with the InfluxDB CLI?](#how-do-i-write-to-a-non-default-retention-policy-with-the-influxdb-cli)
-* [How do I cancel a long-running query?](#how-do-i-cancel-a-long-running-query)
+- [How do I make InfluxDB’s CLI return human readable timestamps?](#how-do-i-use-the-influxdb-cli-to-return-human-readable-timestamps)
+- [How can a non-admin user `USE` a database in the InfluxDB CLI?](#how-can-a-non-admin-user-use-a-database-in-the-influxdb-cli)
+- [How do I write to a non-`DEFAULT` retention policy with the InfluxDB CLI?](#how-do-i-write-to-a-non-default-retention-policy-with-the-influxdb-cli)
+- [How do I cancel a long-running query?](#how-do-i-cancel-a-long-running-query)
 
 **Data types**
 
-* [Why can't I query Boolean field values?](#why-can-t-i-query-boolean-field-values)
-* [How does InfluxDB handle field type discrepancies across shards?](#how-does-influxdb-handle-field-type-discrepancies-across-shards)
-* [What are the minimum and maximum integers that InfluxDB can store?](#what-are-the-minimum-and-maximum-integers-that-influxdb-can-store)
-* [What are the minimum and maximum timestamps that InfluxDB can store?](#what-are-the-minimum-and-maximum-timestamps-that-influxdb-can-store)
-* [How can I tell what type of data is stored in a field?](#how-can-i-tell-what-type-of-data-is-stored-in-a-field)
-* [Can I change a field's data type?](#can-i-change-a-field-s-data-type)
+- [Why can't I query Boolean field values?](#why-can-t-i-query-boolean-field-values)
+- [How does InfluxDB handle field type discrepancies across shards?](#how-does-influxdb-handle-field-type-discrepancies-across-shards)
+- [What are the minimum and maximum integers that InfluxDB can store?](#what-are-the-minimum-and-maximum-integers-that-influxdb-can-store)
+- [What are the minimum and maximum timestamps that InfluxDB can store?](#what-are-the-minimum-and-maximum-timestamps-that-influxdb-can-store)
+- [How can I tell what type of data is stored in a field?](#how-can-i-tell-what-type-of-data-is-stored-in-a-field)
+- [Can I change a field's data type?](#can-i-change-a-field-s-data-type)
 
 **InfluxQL functions**
 
-* [How do I perform mathematical operations within a function?](#how-do-i-perform-mathematical-operations-within-a-function)
-* [Why does my query return epoch 0 as the timestamp?](#why-does-my-query-return-epoch-0-as-the-timestamp)
-* [Which InfluxQL functions support nesting?](#which-influxql-functions-support-nesting)
+- [How do I perform mathematical operations within a function?](#how-do-i-perform-mathematical-operations-within-a-function)
+- [Why does my query return epoch 0 as the timestamp?](#why-does-my-query-return-epoch-0-as-the-timestamp)
+- [Which InfluxQL functions support nesting?](#which-influxql-functions-support-nesting)
 
 **Querying data**
 
-* [What determines the time intervals returned by `GROUP BY time()` queries?](#what-determines-the-time-intervals-returned-by-group-by-time-queries)
-* [Why do my queries return no data or partial data?](#why-do-my-queries-return-no-data-or-partial-data)
-* [Why don't my `GROUP BY time()` queries return timestamps that occur after `now()`?](#why-don-t-my-group-by-time-queries-return-timestamps-that-occur-after-now)
-* [Can I perform mathematical operations against timestamps?](#can-i-perform-mathematical-operations-against-timestamps)
-* [Can I identify write precision from returned timestamps?](#can-i-identify-write-precision-from-returned-timestamps)
-* [When should I single quote and when should I double quote in queries?](#when-should-i-single-quote-and-when-should-i-double-quote-in-queries)
-* [Why am I missing data after creating a new `DEFAULT` retention policy?](#why-am-i-missing-data-after-creating-a-new-default-retention-policy)
-* [Why is my query with a `WHERE OR` time clause returning empty results?](#why-is-my-query-with-a-where-or-time-clause-returning-empty-results)
-* [Why does `fill(previous)` return empty results?](#why-does-fill-previous-return-empty-results)
-* [Why are my `INTO` queries missing data?](#why-are-my-into-queries-missing-data)
-* [How do I query data with an identical tag key and field key?](#how-do-i-query-data-with-an-identical-tag-key-and-field-key)
-* [How do I query data across measurements?](#how-do-i-query-data-across-measurements)
-* [Does the order of the timestamps matter?](#does-the-order-of-the-timestamps-matter)
-* [How do I `SELECT` data with a tag that has no value?](#how-do-i-select-data-with-a-tag-that-has-no-value)
+- [What determines the time intervals returned by `GROUP BY time()` queries?](#what-determines-the-time-intervals-returned-by-group-by-time-queries)
+- [Why do my queries return no data or partial data?](#why-do-my-queries-return-no-data-or-partial-data)
+- [Why don't my `GROUP BY time()` queries return timestamps that occur after `now()`?](#why-don-t-my-group-by-time-queries-return-timestamps-that-occur-after-now)
+- [Can I perform mathematical operations against timestamps?](#can-i-perform-mathematical-operations-against-timestamps)
+- [Can I identify write precision from returned timestamps?](#can-i-identify-write-precision-from-returned-timestamps)
+- [When should I single quote and when should I double quote in queries?](#when-should-i-single-quote-and-when-should-i-double-quote-in-queries)
+- [Why am I missing data after creating a new `DEFAULT` retention policy?](#why-am-i-missing-data-after-creating-a-new-default-retention-policy)
+- [Why is my query with a `WHERE OR` time clause returning empty results?](#why-is-my-query-with-a-where-or-time-clause-returning-empty-results)
+- [Why does `fill(previous)` return empty results?](#why-does-fill-previous-return-empty-results)
+- [Why are my `INTO` queries missing data?](#why-are-my-into-queries-missing-data)
+- [How do I query data with an identical tag key and field key?](#how-do-i-query-data-with-an-identical-tag-key-and-field-key)
+- [How do I query data across measurements?](#how-do-i-query-data-across-measurements)
+- [Does the order of the timestamps matter?](#does-the-order-of-the-timestamps-matter)
+- [How do I `SELECT` data with a tag that has no value?](#how-do-i-select-data-with-a-tag-that-has-no-value)
 
 **Series and series cardinality**
 
-* [Why does series cardinality matter?](#why-does-series-cardinality-matter)
-* [How can I remove series from the index?](#how-can-i-remove-series-from-the-index)
+- [Why does series cardinality matter?](#why-does-series-cardinality-matter)
+- [How can I remove series from the index?](#how-can-i-remove-series-from-the-index)
 
 **Writing data**
 
-* [How do I write integer field values?](#how-do-i-write-integer-field-values)
-* [How does InfluxDB handle duplicate points?](#how-does-influxdb-handle-duplicate-points)
-* [What newline character does the InfluxDB API require?](#what-newline-character-does-the-influxdb-api-require)
-* [What words and characters should I avoid when writing data to InfluxDB?](#what-words-and-characters-should-i-avoid-when-writing-data-to-influxdb)
-* [When should I single quote and when should I double quote when writing data?](#when-should-i-single-quote-and-when-should-i-double-quote-when-writing-data)
-* [Does the precision of the timestamp matter?](#does-the-precision-of-the-timestamp-matter)
-* [What are the configuration recommendations and schema guidelines for writing sparse, historical data?](#what-are-the-configuration-recommendations-and-schema-guidelines-for-writing-sparse-historical-data)
+- [How do I write integer field values?](#how-do-i-write-integer-field-values)
+- [How does InfluxDB handle duplicate points?](#how-does-influxdb-handle-duplicate-points)
+- [What newline character does the InfluxDB API require?](#what-newline-character-does-the-influxdb-api-require)
+- [What words and characters should I avoid when writing data to InfluxDB?](#what-words-and-characters-should-i-avoid-when-writing-data-to-influxdb)
+- [When should I single quote and when should I double quote when writing data?](#when-should-i-single-quote-and-when-should-i-double-quote-when-writing-data)
+- [Does the precision of the timestamp matter?](#does-the-precision-of-the-timestamp-matter)
+- [What are the configuration recommendations and schema guidelines for writing sparse, historical data?](#what-are-the-configuration-recommendations-and-schema-guidelines-for-writing-sparse-historical-data)
 
 ## How do I include a single quote in a password?
 
@@ -661,7 +661,7 @@ Avoid using the same name for a tag and field key. If you inadvertently add the
     fieldKey   fieldType
     ------     ---------
     leaves     float
-```
+    ```
 
 4. If you query the `grape` measurement, you'll see the `leaves` tag key has an appended `_1`:
 
@@ -741,9 +741,9 @@ a `GROUP BY time()` clause must provide an alternative upper bound in the
 In the following example, the first query covers data with timestamps between
 `2015-09-18T21:30:00Z` and `now()`.
 The second query covers data with timestamps between `2015-09-18T21:30:00Z` and 180 weeks from `now()`.
-```
-> SELECT MEAN("boards") FROM "hillvalley" WHERE time >= '2015-09-18T21:30:00Z' GROUP BY time(12m) fill(none)
 
+```sql
+> SELECT MEAN("boards") FROM "hillvalley" WHERE time >= '2015-09-18T21:30:00Z' GROUP BY time(12m) fill(none)
 
 > SELECT MEAN("boards") FROM "hillvalley" WHERE time >= '2015-09-18T21:30:00Z' AND time <= now() + 180w GROUP BY time(12m) fill(none)
 ```
@@ -787,7 +787,9 @@ time                  value	 precision_supplied  timestamp_supplied
 1970-01-01T02:00:00Z  6      h                   2
 ```
 
-{{% warn %}} [GitHub Issue #2977](https://github.com/influxdb/influxdb/issues/2977) {{% /warn %}}
+{{% warn %}}
+[GitHub Issue #2977](https://github.com/influxdb/influxdb/issues/2977)
+{{% /warn %}}
 
 ## When should I single quote and when should I double quote in queries?
 
diff --git a/content/influxdb/v1.8/administration/config.md b/content/influxdb/v1.8/administration/config.md
index 0eac3434a..1ffeb0c1d 100644
--- a/content/influxdb/v1.8/administration/config.md
+++ b/content/influxdb/v1.8/administration/config.md
@@ -292,6 +292,8 @@ The maximum size that a shard cache can reach before it starts rejecting writes.
 Valid memory size suffixes are: `k`, `m`, or `g` (case-insensitive, 1024 = 1k).
 Values without a size suffix are in bytes.
 
+Consider increasing this value if encountering `cache maximum memory size exceeded` errors.
+
 Environment variable: `INFLUXDB_DATA_CACHE_MAX_MEMORY_SIZE`
 
 #### `cache-snapshot-memory-size = "25m"`
diff --git a/content/influxdb/v1.8/flux/get-started/_index.md b/content/influxdb/v1.8/flux/get-started/_index.md
index 136ddb03c..1644672c8 100644
--- a/content/influxdb/v1.8/flux/get-started/_index.md
+++ b/content/influxdb/v1.8/flux/get-started/_index.md
@@ -114,10 +114,11 @@ The Functions pane provides a list of functions available in your Flux queries.
 
 ### 2. influx CLI
 The `influx` CLI is an interactive shell for querying InfluxDB.
-With InfluxDB v1.8+, use the `-type=flux` option to open a Flux REPL where you write and run Flux queries.
+With InfluxDB v1.8+, use the `-type=flux` and `-path-prefix=/api/v2/query` options
+to open a Flux REPL where you write and run Flux queries.
 
 ```bash
-influx -type=flux
+influx -type=flux -path-prefix=/api/v2/query
 ```
 
 <div class="page-nav-btns">
diff --git a/content/influxdb/v1.8/flux/get-started/syntax-basics.md b/content/influxdb/v1.8/flux/get-started/syntax-basics.md
index 14c9a34ae..f2e943710 100644
--- a/content/influxdb/v1.8/flux/get-started/syntax-basics.md
+++ b/content/influxdb/v1.8/flux/get-started/syntax-basics.md
@@ -18,11 +18,12 @@ This guide walks through a handful of simple expressions and how they are handle
 
 ## Use the influx CLI
 Use the `influx` CLI in "Flux mode" as you follow this guide.
-When started with `-type=flux`, the `influx` CLI is an interactive read-eval-print-loop (REPL) that supports Flux syntax.
+When started with `-type=flux` and `-path-prefix=/api/v2/query`, the `influx`
+CLI is an interactive read-eval-print-loop (REPL) that supports Flux syntax.
 
 ##### Start in the influx CLI in Flux mode
 ```bash
-influx -type=flux
+influx -type=flux -path-prefix=/api/v2/query
 ```
 
 > If using the [InfluxData Sandbox](/platform/install-and-deploy/deploying/sandbox-install), use the `./sandbox enter`
@@ -32,7 +33,7 @@ influx -type=flux
 ```bash
 ./sandbox enter influxdb
 
-root@9bfc3c08579c:/# influx -host influxdb -type=flux
+root@9bfc3c08579c:/# influx -host influxdb -type=flux -path-prefix=/api/v2/query
 ```
 
 ## Basic Flux syntax
diff --git a/content/influxdb/v1.8/flux/guides/execute-queries.md b/content/influxdb/v1.8/flux/guides/execute-queries.md
index 5a2ffe0bb..906fd0ae0 100644
--- a/content/influxdb/v1.8/flux/guides/execute-queries.md
+++ b/content/influxdb/v1.8/flux/guides/execute-queries.md
@@ -26,9 +26,11 @@ Chronograf v1.8+ supports Flux in its Data Explorer.
 Flux queries can be built, executed, and visualized from within the Chronograf user interface.
 
 ## Influx CLI
-InfluxDB v1.8+'s `influx` CLI includes a `-type` option which allows you specify
-what type of interactive session to start.
-`-type=flux` will start an interactive read-eval-print-loop (REPL) that supports Flux.
+To start an interactive Flux read-eval-print-loop (REPL) with the InfluxDB 1.8+
+`influx` CLI, run the `influx` command with the following flags:
+
+- `-type=flux`
+- `-path-prefix=/api/v2/query`
 
 {{% note %}}
 If [authentication is enabled](/influxdb/v1.8/administration/authentication_and_authorization)
@@ -44,12 +46,15 @@ the `-password` flag to provide your password.
 {{% /code-tabs %}}
 {{% code-tab-content %}}
 ```bash
-influx -type=flux
+influx -type=flux -path-prefix=/api/v2/query
 ```
 {{% /code-tab-content %}}
 {{% code-tab-content %}}
 ```bash
-influx -type=flux -username myuser -password PasSw0rd
+influx -type=flux \
+  -path-prefix=/api/v2/query \
+  -username myuser \
+  -password PasSw0rd
 ```
 {{% /code-tab-content %}}
 {{< /code-tabs-wrapper >}}
@@ -67,12 +72,18 @@ The accompanying string is executed as a Flux query and results are output in yo
 {{% /code-tabs %}}
 {{% code-tab-content %}}
 ```bash
-influx -type=flux -execute '<flux query>'
+influx -type=flux \
+  -path-prefix=/api/v2/query \
+  -execute '<flux query>'
 ```
 {{% /code-tab-content %}}
 {{% code-tab-content %}}
 ```bash
-influx -type=flux -username myuser -password PasSw0rd -execute '<flux query>'
+influx -type=flux \
+  -path-prefix=/api/v2/query \
+  -username myuser \
+  -password PasSw0rd \
+  -execute '<flux query>'
 ```
 {{% /code-tab-content %}}
 {{< /code-tabs-wrapper >}}
@@ -88,12 +99,15 @@ Query results are otuput in your terminal.
 {{% /code-tabs %}}
 {{% code-tab-content %}}
 ```bash
-echo '<flux query>' | influx -type=flux
+echo '<flux query>' | influx -type=flux -path-prefix=/api/v2/query
 ```
 {{% /code-tab-content %}}
 {{% code-tab-content %}}
 ```bash
-echo '<flux query>' | influx -type=flux -username myuser -password PasSw0rd
+echo '<flux query>' | influx -type=flux \
+  -path-prefix=/api/v2/query \
+  -username myuser \
+  -password PasSw0rd
 ```
 {{% /code-tab-content %}}
 {{< /code-tabs-wrapper >}}
diff --git a/content/influxdb/v1.8/flux/guides/scalar-values.md b/content/influxdb/v1.8/flux/guides/scalar-values.md
index 67765ac6d..9e63c476a 100644
--- a/content/influxdb/v1.8/flux/guides/scalar-values.md
+++ b/content/influxdb/v1.8/flux/guides/scalar-values.md
@@ -215,7 +215,7 @@ getRow = (tables=<-, field, idx=0) => {
 // Use the helper function to define a variable
 lastReported = sampleData
   |> last()
-  |> getRow(idx: 0)
+  |> getRow(field: "temp")
 
 "The last location to report was ${lastReported.location}.
 The temperature was ${string(v: lastReported._value)}°F."
diff --git a/content/influxdb/v1.8/query_language/explore-schema.md b/content/influxdb/v1.8/query_language/explore-schema.md
index 46c8723ba..b5f7f68b7 100644
--- a/content/influxdb/v1.8/query_language/explore-schema.md
+++ b/content/influxdb/v1.8/query_language/explore-schema.md
@@ -189,6 +189,8 @@ SHOW SERIES [ON <database_name>] [FROM_clause] [WHERE <tag_key> <operator> [ '<t
 If the query does not include `ON <database_name>`, you must specify the
 database with `USE <database_name>` in the [CLI](/influxdb/v1.8/tools/shell/) or with the `db` query
 string parameter in the [InfluxDB API](/influxdb/v1.8/tools/api/#query-string-parameters) request.
+`SHOW SERIES` only returns series in the database's default retention policy,
+and fails if there is no default retention policy.
 
 The `FROM`, `WHERE`, `LIMIT`, and `OFFSET` clauses are optional.
 The `WHERE` clause supports tag comparisons; field comparisons are not
@@ -212,7 +214,7 @@ and on [Regular Expressions in Queries](/influxdb/v1.8/query_language/explore-da
 #### Run a `SHOW SERIES` query with the `ON` clause
 
 ```sql
-// Returns series for all shards in the database
+// Returns series for all shards in the database and default retention policy
 > SHOW SERIES ON NOAA_water_database
 
 key
diff --git a/content/influxdb/v1.8/query_language/spec.md b/content/influxdb/v1.8/query_language/spec.md
index b7e8d6c8a..6c88b60d5 100644
--- a/content/influxdb/v1.8/query_language/spec.md
+++ b/content/influxdb/v1.8/query_language/spec.md
@@ -1034,8 +1034,24 @@ show_shards_stmt = "SHOW SHARDS" .
 
 ```sql
 SHOW SHARDS
+
+name: telegraf
+id  database   retention_policy shard_group start_time           end_time             expiry_time          owners
+--  --------   ---------------- ----------- ----------           --------             -----------          ------
+16  telegraf   autogen          6           2020-10-19T00:00:00Z 2020-10-26T00:00:00Z 2020-10-26T00:00:00Z 6,7,8
+17  telegraf   autogen          6           2020-10-19T00:00:00Z 2020-10-26T00:00:00Z 2020-10-26T00:00:00Z 9,4,5
+21  telegraf   autogen          8           2020-10-26T00:00:00Z 2020-11-02T00:00:00Z 2020-11-02T00:00:00Z 8,9,4
+22  telegraf   autogen          8           2020-10-26T00:00:00Z 2020-11-02T00:00:00Z 2020-11-02T00:00:00Z 5,6,7
+26  telegraf   autogen          10          2020-11-02T00:00:00Z 2020-11-09T00:00:00Z 2020-11-09T00:00:00Z 9,4,5
+27  telegraf   autogen          10          2020-11-02T00:00:00Z 2020-11-09T00:00:00Z 2020-11-09T00:00:00Z 6,7,8
+31  telegraf   autogen          12          2020-11-09T00:00:00Z 2020-11-16T00:00:00Z 2020-11-16T00:00:00Z 6,7,8
 ```
 
+`SHOW SHARDS` outputs the following data:
+- `id` column: Shard IDs that belong to the specified `database` and `retention policy`.
+- `shard_group` column: Group number that a shard belongs to. Shards in the same shard group have the same `start_time` and `end_time`. This interval indicates how long the shard is active, and the `expiry_time` columns shows when the shard group expires. No timestamps will show under `expiry_time` if the retention policy duration is set to infinite.
+- `owners` column: Shows the data nodes that own a shard. The number of nodes that own a shard is equal to the replication factor. In this example, the replication factor is 3, so 3 nodes own each shard.
+
 ### SHOW STATS
 
 Returns detailed statistics on available components of an InfluxDB node and available (enabled) components.
diff --git a/content/influxdb/v1.8/troubleshooting/frequently-asked-questions.md b/content/influxdb/v1.8/troubleshooting/frequently-asked-questions.md
index 92b1ef33c..e014b9f5d 100644
--- a/content/influxdb/v1.8/troubleshooting/frequently-asked-questions.md
+++ b/content/influxdb/v1.8/troubleshooting/frequently-asked-questions.md
@@ -16,68 +16,68 @@ Where applicable, it links to outstanding issues on GitHub.
 
 **Administration**
 
-* [How do I include a single quote in a password?](#how-do-i-include-a-single-quote-in-a-password)
-* [How can I identify my version of InfluxDB?](#how-can-i-identify-my-version-of-influxdb)
-* [Where can I find InfluxDB logs?](#where-can-i-find-influxdb-logs)
-* [What is the relationship between shard group durations and retention policies?](#what-is-the-relationship-between-shard-group-durations-and-retention-policies)
-* [Why aren't data dropped after I've altered a retention policy?](#why-aren-t-data-dropped-after-i-ve-altered-a-retention-policy)
-* [Why does InfluxDB fail to parse microsecond units in the configuration file?](#why-does-influxdb-fail-to-parse-microsecond-units-in-the-configuration-file)
-* [Does InfluxDB have a file system size limit?](#does-influxdb-have-a-file-system-size-limit)
+- [How do I include a single quote in a password?](#how-do-i-include-a-single-quote-in-a-password)
+- [How can I identify my version of InfluxDB?](#how-can-i-identify-my-version-of-influxdb)
+- [Where can I find InfluxDB logs?](#where-can-i-find-influxdb-logs)
+- [What is the relationship between shard group durations and retention policies?](#what-is-the-relationship-between-shard-group-durations-and-retention-policies)
+- [Why aren't data dropped after I've altered a retention policy?](#why-aren-t-data-dropped-after-i-ve-altered-a-retention-policy)
+- [Why does InfluxDB fail to parse microsecond units in the configuration file?](#why-does-influxdb-fail-to-parse-microsecond-units-in-the-configuration-file)
+- [Does InfluxDB have a file system size limit?](#does-influxdb-have-a-file-system-size-limit)
 
 
 **Command line interface (CLI)**
 
-* [How do I make InfluxDB’s CLI return human readable timestamps?](#how-do-i-use-the-influxdb-cli-to-return-human-readable-timestamps)
-* [How can a non-admin user `USE` a database in the InfluxDB CLI?](#how-can-a-non-admin-user-use-a-database-in-the-influxdb-cli)
-* [How do I write to a non-`DEFAULT` retention policy with the InfluxDB CLI?](#how-do-i-write-to-a-non-default-retention-policy-with-the-influxdb-cli)
-* [How do I cancel a long-running query?](#how-do-i-cancel-a-long-running-query)
+- [How do I make InfluxDB’s CLI return human readable timestamps?](#how-do-i-use-the-influxdb-cli-to-return-human-readable-timestamps)
+- [How can a non-admin user `USE` a database in the InfluxDB CLI?](#how-can-a-non-admin-user-use-a-database-in-the-influxdb-cli)
+- [How do I write to a non-`DEFAULT` retention policy with the InfluxDB CLI?](#how-do-i-write-to-a-non-default-retention-policy-with-the-influxdb-cli)
+- [How do I cancel a long-running query?](#how-do-i-cancel-a-long-running-query)
 
 **Data types**
 
-* [Why can't I query Boolean field values?](#why-can-t-i-query-boolean-field-values)
-* [How does InfluxDB handle field type discrepancies across shards?](#how-does-influxdb-handle-field-type-discrepancies-across-shards)
-* [What are the minimum and maximum integers that InfluxDB can store?](#what-are-the-minimum-and-maximum-integers-that-influxdb-can-store)
-* [What are the minimum and maximum timestamps that InfluxDB can store?](#what-are-the-minimum-and-maximum-timestamps-that-influxdb-can-store)
-* [How can I tell what type of data is stored in a field?](#how-can-i-tell-what-type-of-data-is-stored-in-a-field)
-* [Can I change a field's data type?](#can-i-change-a-field-s-data-type)
+- [Why can't I query Boolean field values?](#why-can-t-i-query-boolean-field-values)
+- [How does InfluxDB handle field type discrepancies across shards?](#how-does-influxdb-handle-field-type-discrepancies-across-shards)
+- [What are the minimum and maximum integers that InfluxDB can store?](#what-are-the-minimum-and-maximum-integers-that-influxdb-can-store)
+- [What are the minimum and maximum timestamps that InfluxDB can store?](#what-are-the-minimum-and-maximum-timestamps-that-influxdb-can-store)
+- [How can I tell what type of data is stored in a field?](#how-can-i-tell-what-type-of-data-is-stored-in-a-field)
+- [Can I change a field's data type?](#can-i-change-a-field-s-data-type)
 
 **InfluxQL functions**
 
-* [How do I perform mathematical operations within a function?](#how-do-i-perform-mathematical-operations-within-a-function)
-* [Why does my query return epoch 0 as the timestamp?](#why-does-my-query-return-epoch-0-as-the-timestamp)
-* [Which InfluxQL functions support nesting?](#which-influxql-functions-support-nesting)
+- [How do I perform mathematical operations within a function?](#how-do-i-perform-mathematical-operations-within-a-function)
+- [Why does my query return epoch 0 as the timestamp?](#why-does-my-query-return-epoch-0-as-the-timestamp)
+- [Which InfluxQL functions support nesting?](#which-influxql-functions-support-nesting)
 
 **Querying data**
 
-* [What determines the time intervals returned by `GROUP BY time()` queries?](#what-determines-the-time-intervals-returned-by-group-by-time-queries)
-* [Why do my queries return no data or partial data?](#why-do-my-queries-return-no-data-or-partial-data)
-* [Why don't my `GROUP BY time()` queries return timestamps that occur after `now()`?](#why-don-t-my-group-by-time-queries-return-timestamps-that-occur-after-now)
-* [Can I perform mathematical operations against timestamps?](#can-i-perform-mathematical-operations-against-timestamps)
-* [Can I identify write precision from returned timestamps?](#can-i-identify-write-precision-from-returned-timestamps)
-* [When should I single quote and when should I double quote in queries?](#when-should-i-single-quote-and-when-should-i-double-quote-in-queries)
-* [Why am I missing data after creating a new `DEFAULT` retention policy?](#why-am-i-missing-data-after-creating-a-new-default-retention-policy)
-* [Why is my query with a `WHERE OR` time clause returning empty results?](#why-is-my-query-with-a-where-or-time-clause-returning-empty-results)
-* [Why does `fill(previous)` return empty results?](#why-does-fill-previous-return-empty-results)
-* [Why are my `INTO` queries missing data?](#why-are-my-into-queries-missing-data)
-* [How do I query data with an identical tag key and field key?](#how-do-i-query-data-with-an-identical-tag-key-and-field-key)
-* [How do I query data across measurements?](#how-do-i-query-data-across-measurements)
-* [Does the order of the timestamps matter?](#does-the-order-of-the-timestamps-matter)
-* [How do I `SELECT` data with a tag that has no value?](#how-do-i-select-data-with-a-tag-that-has-no-value)
+- [What determines the time intervals returned by `GROUP BY time()` queries?](#what-determines-the-time-intervals-returned-by-group-by-time-queries)
+- [Why do my queries return no data or partial data?](#why-do-my-queries-return-no-data-or-partial-data)
+- [Why don't my `GROUP BY time()` queries return timestamps that occur after `now()`?](#why-don-t-my-group-by-time-queries-return-timestamps-that-occur-after-now)
+- [Can I perform mathematical operations against timestamps?](#can-i-perform-mathematical-operations-against-timestamps)
+- [Can I identify write precision from returned timestamps?](#can-i-identify-write-precision-from-returned-timestamps)
+- [When should I single quote and when should I double quote in queries?](#when-should-i-single-quote-and-when-should-i-double-quote-in-queries)
+- [Why am I missing data after creating a new `DEFAULT` retention policy?](#why-am-i-missing-data-after-creating-a-new-default-retention-policy)
+- [Why is my query with a `WHERE OR` time clause returning empty results?](#why-is-my-query-with-a-where-or-time-clause-returning-empty-results)
+- [Why does `fill(previous)` return empty results?](#why-does-fill-previous-return-empty-results)
+- [Why are my `INTO` queries missing data?](#why-are-my-into-queries-missing-data)
+- [How do I query data with an identical tag key and field key?](#how-do-i-query-data-with-an-identical-tag-key-and-field-key)
+- [How do I query data across measurements?](#how-do-i-query-data-across-measurements)
+- [Does the order of the timestamps matter?](#does-the-order-of-the-timestamps-matter)
+- [How do I `SELECT` data with a tag that has no value?](#how-do-i-select-data-with-a-tag-that-has-no-value)
 
 **Series and series cardinality**
 
-* [Why does series cardinality matter?](#why-does-series-cardinality-matter)
-* [How can I remove series from the index?](#how-can-i-remove-series-from-the-index)
+- [Why does series cardinality matter?](#why-does-series-cardinality-matter)
+- [How can I remove series from the index?](#how-can-i-remove-series-from-the-index)
 
 **Writing data**
 
-* [How do I write integer field values?](#how-do-i-write-integer-field-values)
-* [How does InfluxDB handle duplicate points?](#how-does-influxdb-handle-duplicate-points)
-* [What newline character does the InfluxDB API require?](#what-newline-character-does-the-influxdb-api-require)
-* [What words and characters should I avoid when writing data to InfluxDB?](#what-words-and-characters-should-i-avoid-when-writing-data-to-influxdb)
-* [When should I single quote and when should I double quote when writing data?](#when-should-i-single-quote-and-when-should-i-double-quote-when-writing-data)
-* [Does the precision of the timestamp matter?](#does-the-precision-of-the-timestamp-matter)
-* [What are the configuration recommendations and schema guidelines for writing sparse, historical data?](#what-are-the-configuration-recommendations-and-schema-guidelines-for-writing-sparse-historical-data)
+- [How do I write integer field values?](#how-do-i-write-integer-field-values)
+- [How does InfluxDB handle duplicate points?](#how-does-influxdb-handle-duplicate-points)
+- [What newline character does the InfluxDB API require?](#what-newline-character-does-the-influxdb-api-require)
+- [What words and characters should I avoid when writing data to InfluxDB?](#what-words-and-characters-should-i-avoid-when-writing-data-to-influxdb)
+- [When should I single quote and when should I double quote when writing data?](#when-should-i-single-quote-and-when-should-i-double-quote-when-writing-data)
+- [Does the precision of the timestamp matter?](#does-the-precision-of-the-timestamp-matter)
+- [What are the configuration recommendations and schema guidelines for writing sparse, historical data?](#what-are-the-configuration-recommendations-and-schema-guidelines-for-writing-sparse-historical-data)
 
 ## How do I include a single quote in a password?
 
@@ -653,7 +653,7 @@ Avoid using the same name for a tag and field key. If you inadvertently add the
     fieldKey   fieldType
     ------     ---------
     leaves     float
-```
+    ```
 
 4. If you query the `grape` measurement, you'll see the `leaves` tag key has an appended `_1`:
 
@@ -733,9 +733,9 @@ a `GROUP BY time()` clause must provide an alternative upper bound in the
 In the following example, the first query covers data with timestamps between
 `2015-09-18T21:30:00Z` and `now()`.
 The second query covers data with timestamps between `2015-09-18T21:30:00Z` and 180 weeks from `now()`.
-```
-> SELECT MEAN("boards") FROM "hillvalley" WHERE time >= '2015-09-18T21:30:00Z' GROUP BY time(12m) fill(none)
 
+```sql
+> SELECT MEAN("boards") FROM "hillvalley" WHERE time >= '2015-09-18T21:30:00Z' GROUP BY time(12m) fill(none)
 
 > SELECT MEAN("boards") FROM "hillvalley" WHERE time >= '2015-09-18T21:30:00Z' AND time <= now() + 180w GROUP BY time(12m) fill(none)
 ```
@@ -779,7 +779,9 @@ time                  value	 precision_supplied  timestamp_supplied
 1970-01-01T02:00:00Z  6      h                   2
 ```
 
-{{% warn %}} [GitHub Issue #2977](https://github.com/influxdb/influxdb/issues/2977) {{% /warn %}}
+{{% warn %}}
+[GitHub Issue #2977](https://github.com/influxdb/influxdb/issues/2977)
+{{% /warn %}}
 
 ## When should I single quote and when should I double quote in queries?
 
diff --git a/content/influxdb/v2.0/api-guide/client-libraries/arduino.md b/content/influxdb/v2.0/api-guide/client-libraries/arduino.md
index a00a2b1d6..e6ed15eeb 100644
--- a/content/influxdb/v2.0/api-guide/client-libraries/arduino.md
+++ b/content/influxdb/v2.0/api-guide/client-libraries/arduino.md
@@ -9,6 +9,7 @@ menu:
   influxdb_2_0:
     name: Arduino
     parent: Client libraries
-    url: https://github.com/tobiasschuerg/InfluxDB-Client-for-Arduino
+    params:
+      url: https://github.com/tobiasschuerg/InfluxDB-Client-for-Arduino
 weight: 201
 ---
diff --git a/content/influxdb/v2.0/api-guide/client-libraries/csharp.md b/content/influxdb/v2.0/api-guide/client-libraries/csharp.md
index 0ae51b58e..5b9ae2191 100644
--- a/content/influxdb/v2.0/api-guide/client-libraries/csharp.md
+++ b/content/influxdb/v2.0/api-guide/client-libraries/csharp.md
@@ -8,6 +8,7 @@ menu:
   influxdb_2_0:
     name: C#
     parent: Client libraries
-    url: https://github.com/influxdata/influxdb-client-csharp
+    params:
+      url: https://github.com/influxdata/influxdb-client-csharp
 weight: 201
 ---
diff --git a/content/influxdb/v2.0/api-guide/client-libraries/dart.md b/content/influxdb/v2.0/api-guide/client-libraries/dart.md
index c2dad9c35..03ffddba7 100644
--- a/content/influxdb/v2.0/api-guide/client-libraries/dart.md
+++ b/content/influxdb/v2.0/api-guide/client-libraries/dart.md
@@ -8,6 +8,7 @@ menu:
   influxdb_2_0:
     name: Dart
     parent: Client libraries
-    url: https://github.com/influxdata/influxdb-client-dart
+    params:
+      url: https://github.com/influxdata/influxdb-client-dart
 weight: 201
 ---
diff --git a/content/influxdb/v2.0/api-guide/client-libraries/java.md b/content/influxdb/v2.0/api-guide/client-libraries/java.md
index 57b0324e9..736da8c3f 100644
--- a/content/influxdb/v2.0/api-guide/client-libraries/java.md
+++ b/content/influxdb/v2.0/api-guide/client-libraries/java.md
@@ -8,6 +8,7 @@ menu:
   influxdb_2_0:
     name: Java
     parent: Client libraries
-    url: https://github.com/influxdata/influxdb-client-java
+    params:
+      url: https://github.com/influxdata/influxdb-client-java
 weight: 201
 ---
diff --git a/content/influxdb/v2.0/api-guide/client-libraries/kotlin.md b/content/influxdb/v2.0/api-guide/client-libraries/kotlin.md
index 47fc45e4d..d447d201f 100644
--- a/content/influxdb/v2.0/api-guide/client-libraries/kotlin.md
+++ b/content/influxdb/v2.0/api-guide/client-libraries/kotlin.md
@@ -8,6 +8,7 @@ menu:
   influxdb_2_0:
     name: Kotlin
     parent: Client libraries
-    url: https://github.com/influxdata/influxdb-client-java/tree/master/client-kotlin
+    params:
+      url: https://github.com/influxdata/influxdb-client-java/tree/master/client-kotlin
 weight: 201
 ---
diff --git a/content/influxdb/v2.0/api-guide/client-libraries/php.md b/content/influxdb/v2.0/api-guide/client-libraries/php.md
index 7f4098d2b..30a69b4da 100644
--- a/content/influxdb/v2.0/api-guide/client-libraries/php.md
+++ b/content/influxdb/v2.0/api-guide/client-libraries/php.md
@@ -8,6 +8,7 @@ menu:
   influxdb_2_0:
     name: PHP
     parent: Client libraries
-    url: https://github.com/influxdata/influxdb-client-php
+    params:
+      url: https://github.com/influxdata/influxdb-client-php
 weight: 201
 ---
diff --git a/content/influxdb/v2.0/api-guide/client-libraries/r.md b/content/influxdb/v2.0/api-guide/client-libraries/r.md
index d4a98a2e8..abf876827 100644
--- a/content/influxdb/v2.0/api-guide/client-libraries/r.md
+++ b/content/influxdb/v2.0/api-guide/client-libraries/r.md
@@ -8,6 +8,7 @@ menu:
   influxdb_2_0:
     name: R
     parent: Client libraries
-    url: https://github.com/influxdata/influxdb-client-r
+    params:
+      url: https://github.com/influxdata/influxdb-client-r
 weight: 201
 ---
diff --git a/content/influxdb/v2.0/api-guide/client-libraries/ruby.md b/content/influxdb/v2.0/api-guide/client-libraries/ruby.md
index f17e5cafe..225f8d524 100644
--- a/content/influxdb/v2.0/api-guide/client-libraries/ruby.md
+++ b/content/influxdb/v2.0/api-guide/client-libraries/ruby.md
@@ -8,6 +8,7 @@ menu:
   influxdb_2_0:
     name: Ruby
     parent: Client libraries
-    url: https://github.com/influxdata/influxdb-client-ruby
+    params:
+      url: https://github.com/influxdata/influxdb-client-ruby
 weight: 201
 ---
diff --git a/content/influxdb/v2.0/api-guide/client-libraries/scala.md b/content/influxdb/v2.0/api-guide/client-libraries/scala.md
index 235c617c2..584b27cf5 100644
--- a/content/influxdb/v2.0/api-guide/client-libraries/scala.md
+++ b/content/influxdb/v2.0/api-guide/client-libraries/scala.md
@@ -8,6 +8,7 @@ menu:
   influxdb_2_0:
     name: Scala
     parent: Client libraries
-    url: https://github.com/influxdata/influxdb-client-java/tree/master/client-scala
+    params:
+      url: https://github.com/influxdata/influxdb-client-java/tree/master/client-scala
 weight: 201
 ---
diff --git a/content/influxdb/v2.0/api-guide/client-libraries/swift.md b/content/influxdb/v2.0/api-guide/client-libraries/swift.md
index 1433227f0..a1bda2223 100644
--- a/content/influxdb/v2.0/api-guide/client-libraries/swift.md
+++ b/content/influxdb/v2.0/api-guide/client-libraries/swift.md
@@ -8,6 +8,7 @@ menu:
   influxdb_2_0:
     name: Swift
     parent: Client libraries
-    url: https://github.com/influxdata/influxdb-client-swift
+    params:
+      url: https://github.com/influxdata/influxdb-client-swift
 weight: 201
 ---
diff --git a/content/influxdb/v2.0/influxdb-templates/monitor.md b/content/influxdb/v2.0/influxdb-templates/monitor.md
index 4c3079129..8f2fc2c63 100644
--- a/content/influxdb/v2.0/influxdb-templates/monitor.md
+++ b/content/influxdb/v2.0/influxdb-templates/monitor.md
@@ -33,7 +33,7 @@ Before you begin, make sure you have access to the following:
  - InfluxDB Cloud account ([sign up for free here](https://cloud2.influxdata.com/signup))
  - Command line access to a machine [running InfluxDB OSS 2.x](/influxdb/v2.0/install/) and permissions to install Telegraf on this machine
  - Internet connectivity from the machine running InfluxDB OSS 2.x and Telegraf to InfluxDB Cloud
- - Sufficient resource availability to install the template. InfluxDB Cloud Free Plan accounts include [resource limits](/influxdb/cloud/account-management/pricing-plans/#resource-limits/influxdb/cloud/account-management/pricing-plans/#resource-limits)
+ - Sufficient resource availability to install the template. InfluxDB Cloud Free Plan accounts include [resource limits](/influxdb/cloud/account-management/limits/#free-plan-limits)
 
 ## Install the InfluxDB OSS Monitoring template
 
diff --git a/content/influxdb/v2.0/install.md b/content/influxdb/v2.0/install.md
index a435eb391..fd185d6a0 100644
--- a/content/influxdb/v2.0/install.md
+++ b/content/influxdb/v2.0/install.md
@@ -574,8 +574,8 @@ If you have a 32-bit Raspberry Pi, [use Telegraf](/{{< latest "telegraf" >}}/)
 to collect and send data to:
 
 - [InfluxDB OSS](/influxdb/v2.0/), running on a 64-bit system
-- InfluxDB Cloud with a [**Free Tier**](/influxdb/cloud/account-management/pricing-plans/#free-plan) account
-- InfluxDB Cloud with a paid [**Usage-Based**](/influxdb/cloud/account-management/pricing-plans/#usage-based-plan) account with relaxed resource restrictions.
+- InfluxDB Cloud [Free Plan](/influxdb/cloud/account-management/pricing-plans/#free-plan)
+- InfluxDB Cloud [Usage-Based Plan](/influxdb/cloud/account-management/pricing-plans/#usage-based-plan)
 
 {{% /tab-content %}}
 <!--------------------------------- END Rasberry Pi --------------------------->
diff --git a/content/influxdb/v2.0/query-data/flux/monitor-states.md b/content/influxdb/v2.0/query-data/flux/monitor-states.md
index a4523ca68..116ef148f 100644
--- a/content/influxdb/v2.0/query-data/flux/monitor-states.md
+++ b/content/influxdb/v2.0/query-data/flux/monitor-states.md
@@ -24,81 +24,79 @@ Flux helps you monitor states in your metrics and events:
 If you're just getting started with Flux queries, check out the following:
 
 - [Get started with Flux](/{{< latest "flux" >}}/get-started/) for a conceptual overview of Flux.
-- [Execute queries](/influxdb/v2.0/query-data/execute-queries/) to discover a variety of ways to run your queries.
+- [Execute queries](/influxdb/v2.2/query-data/execute-queries/) to discover a variety of ways to run your queries.
 
 ## Find how long a state persists
 
-1. Use the [`stateDuration()`](/{{< latest "flux" >}}/stdlib/universe/stateduration/) function to calculate how long a column value has remained the same value (or state). Include the following information:
+Use [`stateDuration()`](/{{< latest "flux" >}}/stdlib/universe/stateduration/)
+to calculate the duration of consecutive rows with a specified state.
+For each consecutive point that matches the specified state, `stateDuration()`
+increments and stores the duration (in the specified unit) in a user-defined column.
 
-  - **Column to search:** any tag key, tag value, field key, field value, or measurement.
-  - **Value:** the value (or state) to search for in the specified column.
-  - **State duration column:** a new column to store the state duration─the length of time that the specified value persists.
-  - **Unit:** the unit of time (`1s` (by default), `1m`, `1h`) used to increment the state duration.
+Include the following information:
 
-        ```js
-        |> stateDuration(
-           fn: (r) => r._column_to_search == "value_to_search_for",
-           column: "state_duration",
-           unit: 1s
-         )
-        ```
+- **Column to search:** any tag key, tag value, field key, field value, or measurement.
+- **Value:** the value (or state) to search for in the specified column.
+- **State duration column:** a new column to store the state duration─the length of time that the specified value persists.
+- **Unit:** the unit of time (`1s` (by default), `1m`, `1h`) used to increment the state duration.
 
-2. Use `stateDuration()` to search each point for the specified value:
+```js
+data
+    |> stateDuration(fn: (r) => r.column_to_search == "value_to_search_for", column: "state_duration", unit: 1s)
+```
 
-    - For the first point that evaluates `true`, the state duration is set to `0`. For each consecutive point that evaluates `true`, the state duration increases by the time interval between each consecutive point (in specified units).
-    - If the state is `false`, the state duration is reset to `-1`.
+- For the first point that evaluates `true`, the state duration is set to `0`.
+  For each consecutive point that evaluates `true`, the state duration
+  increases by the time interval between each consecutive point (in specified units).
+- If the state is `false`, the state duration is reset to `-1`.
 
 ### Example query with stateDuration()
 
 The following query searches the `doors` bucket over the past 5 minutes to find how many seconds a door has been `closed`.
 
 ```js
-  from(bucket: "doors")
-   |> range(start: -5m)
-   |> stateDuration(
-      fn: (r) =>
-      r._value == "closed",
-      column: "door_closed",
-      unit: 1s)
+from(bucket: "doors")
+    |> range(start: -5m)
+    |> stateDuration(fn: (r) => r._value == "closed", column: "door_closed", unit: 1s)
 ```
 
-In this example, `door_closed` is the **State duration** column. If you write data to the `doors` bucket every minute, the state duration increases by `60s` for each consecutive point where `_value` is `closed`. If `_value` is not `closed`, the state duration is reset to `0`.
+In this example, `door_closed` is the **State duration** column.
+If you write data to the `doors` bucket every minute, the state duration
+increases by `60s` for each consecutive point where `_value` is `closed`.
+If `_value` is not `closed`, the state duration is reset to `0`.
 
 #### Query results
 
 Results for the example query above may look like this (for simplicity, we've omitted the measurement, tag, and field columns):
 
-```sh
-_time                   _value        door_closed
-2019-10-26T17:39:16Z    closed        0
-2019-10-26T17:40:16Z    closed        60
-2019-10-26T17:41:16Z    closed        120
-2019-10-26T17:42:16Z    open          -1
-2019-10-26T17:43:16Z    closed        0
-2019-10-26T17:44:27Z    closed        60
-```
+| _time                | _value | door_closed |
+| :------------------- | :----: | ----------: |
+| 2019-10-26T17:39:16Z | closed |           0 |
+| 2019-10-26T17:40:16Z | closed |          60 |
+| 2019-10-26T17:41:16Z | closed |         120 |
+| 2019-10-26T17:42:16Z |  open  |          -1 |
+| 2019-10-26T17:43:16Z | closed |           0 |
+| 2019-10-26T17:44:27Z | closed |          60 |
 
 ## Count the number of consecutive states
 
-1. Use the [`stateCount()` function](/{{< latest "flux" >}}/stdlib/universe/statecount/)
-   and include the following information:
+Use the [`stateCount()` function](/{{< latest "flux" >}}/stdlib/universe/statecount/)
+and include the following information:
 
-  - **Column to search:** any tag key, tag value, field key, field value, or measurement.
-  - **Value:** to search for in the specified column.
-  - **State count column:** a new column to store the state count─the number of
-    consecutive records in which the specified value exists.
+- **Column to search:** any tag key, tag value, field key, field value, or measurement.
+- **Value:** to search for in the specified column.
+- **State count column:** a new column to store the state count─the number of
+  consecutive records in which the specified value exists.
 
-        ```js
-        |> stateCount(
-          fn: (r) => r._column_to_search == "value_to_search_for",
-          column: "state_count"
-        )
-        ```
+```js
+|> stateCount(
+    fn: (r) => r.column_to_search == "value_to_search_for",
+    column: "state_count",
+)
+```
 
-2. Use `stateCount()` to search each point for the specified value:
-
-    - For the first point that evaluates `true`, the state count is set to `1`. For each consecutive point that evaluates `true`, the state count increases by 1.
-    - If the state is `false`, the state count is reset to `-1`.
+- For the first point that evaluates `true`, the state count is set to `1`. For each consecutive point that evaluates `true`, the state count increases by 1.
+- If the state is `false`, the state count is reset to `-1`.
 
 ### Example query with stateCount()
 
@@ -106,11 +104,8 @@ The following query searches the `doors` bucket over the past 5 minutes and calc
 
 ```js
 from(bucket: "doors")
-  |> range(start: -5m)
-  |> stateDuration(
-    fn: (r) => r._value == "closed",
-    column: "door_closed"
-  )
+    |> range(start: -5m)
+    |> stateDuration(fn: (r) => r._value == "closed", column: "door_closed")
 ```
 
 This example stores the **state count** in the `door_closed` column. If you write data to the `doors` bucket every minute, the state count increases by `1` for each consecutive point where `_value` is `closed`. If `_value` is not `closed`, the state count is reset to `-1`.
@@ -119,15 +114,14 @@ This example stores the **state count** in the `door_closed` column. If you writ
 
 Results for the example query above may look like this (for simplicity, we've omitted the measurement, tag, and field columns):
 
-```bash
-_time                   _value        door_closed
-2019-10-26T17:39:16Z    closed        1
-2019-10-26T17:40:16Z    closed        2
-2019-10-26T17:41:16Z    closed        3
-2019-10-26T17:42:16Z    open          -1
-2019-10-26T17:43:16Z    closed        1
-2019-10-26T17:44:27Z    closed        2
-```
+| _time                | _value | door_closed |
+| :------------------- | :----: | ----------: |
+| 2019-10-26T17:39:16Z | closed |           1 |
+| 2019-10-26T17:40:16Z | closed |           2 |
+| 2019-10-26T17:41:16Z | closed |           3 |
+| 2019-10-26T17:42:16Z |  open  |          -1 |
+| 2019-10-26T17:43:16Z | closed |           1 |
+| 2019-10-26T17:44:27Z | closed |           2 |
 
 #### Example query to count machine state
 
@@ -135,15 +129,11 @@ The following query checks the machine state every minute (idle, assigned, or bu
 
 ```js
 from(bucket: "servers")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-     r.machine_state == "idle" or
-     r.machine_state == "assigned" or
-     r.machine_state == "busy"
-  )
-  |> stateCount(fn: (r) => r.machine_state == "busy", column: "_count")
-  |> stateCount(fn: (r) => r.machine_state == "assigned", column: "_count")
-  |> stateCount(fn: (r) => r.machine_state == "idle", column: "_count")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r.machine_state == "idle" or r.machine_state == "assigned" or r.machine_state == "busy")
+    |> stateCount(fn: (r) => r.machine_state == "busy", column: "_count")
+    |> stateCount(fn: (r) => r.machine_state == "assigned", column: "_count")
+    |> stateCount(fn: (r) => r.machine_state == "idle", column: "_count")
 ```
 
 <!--## Detect state changes
diff --git a/content/influxdb/v2.0/query-data/flux/scalar-values.md b/content/influxdb/v2.0/query-data/flux/scalar-values.md
index 359127a3b..155f8e11a 100644
--- a/content/influxdb/v2.0/query-data/flux/scalar-values.md
+++ b/content/influxdb/v2.0/query-data/flux/scalar-values.md
@@ -189,7 +189,7 @@ getRow = (tables=<-, field, idx=0) => {
 // Use the helper function to define a variable
 lastReported = sampleData
   |> last()
-  |> getRow(idx: 0)
+  |> getRow(field: "temp")
 
 "The last location to report was ${lastReported.location}.
 The temperature was ${string(v: lastReported._value)}°F."
diff --git a/content/influxdb/v2.0/query-data/optimize-queries.md b/content/influxdb/v2.0/query-data/optimize-queries.md
index 99cda5f06..7a60307fc 100644
--- a/content/influxdb/v2.0/query-data/optimize-queries.md
+++ b/content/influxdb/v2.0/query-data/optimize-queries.md
@@ -28,12 +28,10 @@ Most pushdowns are supported when querying an InfluxDB 2.0 or InfluxDB Cloud dat
 | Functions                      | InfluxDB 2.0         | InfluxDB Cloud       |
 |:---------                      |:------------:        |:--------------:      |
 | **count()**                    | {{< icon "check" "v2" >}} | {{< icon "check" "v2" >}} |
-| **drop()**                     | {{< icon "check" "v2" >}} | {{< icon "check" "v2" >}} |
 | **duplicate()**                | {{< icon "check" "v2" >}} | {{< icon "check" "v2" >}} |
 | **filter()** {{% req " \*" %}} | {{< icon "check" "v2" >}} | {{< icon "check" "v2" >}} |
 | **fill()**                     | {{< icon "check" "v2" >}} | {{< icon "check" "v2" >}} |
 | **first()**                    | {{< icon "check" "v2" >}} | {{< icon "check" "v2" >}} |
-| **keep()**                     | {{< icon "check" "v2" >}} | {{< icon "check" "v2" >}} |
 | **last()**                     | {{< icon "check" "v2" >}} | {{< icon "check" "v2" >}} |
 | **max()**                      | {{< icon "check" "v2" >}} | {{< icon "check" "v2" >}} |
 | **mean()**                     | {{< icon "check" "v2" >}} | {{< icon "check" "v2" >}} |
diff --git a/content/influxdb/v2.0/reference/prometheus-metrics.md b/content/influxdb/v2.0/reference/prometheus-metrics.md
index aefd422a0..3c8ae5d4a 100644
--- a/content/influxdb/v2.0/reference/prometheus-metrics.md
+++ b/content/influxdb/v2.0/reference/prometheus-metrics.md
@@ -12,7 +12,7 @@ related:
   - https://prometheus.io/docs/concepts/data_model/, Prometheus data model
   - /influxdb/v2.0/write-data/developer-tools/scrape-prometheus-metrics/
   - /{{< latest "flux" >}}/prometheus/, Work with Prometheus in Flux
-  - /{{< latest "telegraf" >}}/plugins/#prometheus, Telegraf Prometheus input plugin
+  - /{{< latest "telegraf" >}}/plugins/#input-prometheus, Telegraf Prometheus input plugin
   - /influxdb/v2.0/write-data/no-code/scrape-data/
   - /{{< latest "flux" >}}/stdlib/experimental/prometheus/scrape/
 ---
@@ -28,7 +28,7 @@ are parsed and written to InfluxDB in one of two formats, depending on the scrap
 
 | Scraping tool                                                                              |                               InfluxDB Metric version |
 | :----------------------------------------------------------------------------------------- | ----------------------------------------------------: |
-| [Telegraf Prometheus plugin](/{{< latest "telegraf" >}}/plugins/#prometheus)               | _Determined by `metric_version` configuration option_ |
+| [Telegraf Prometheus plugin](/{{< latest "telegraf" >}}/plugins/#input-prometheus)         | _Determined by `metric_version` configuration option_ |
 | [InfluxDB scraper](/influxdb/v2.0/write-data/no-code/scrape-data/)                         |                                                     1 |
 | Flux [`prometheus.scrape()`]({{< latest "flux" >}}/stdlib/experimental/prometheus/scrape/) |                                                     2 |
 
@@ -37,7 +37,7 @@ are parsed and written to InfluxDB in one of two formats, depending on the scrap
 
 | Scraping tool                                                                              |                               InfluxDB Metric version |
 | :----------------------------------------------------------------------------------------- | ----------------------------------------------------: |
-| [Telegraf Prometheus plugin](/{{< latest "telegraf" >}}/plugins/#prometheus)               | _Determined by `metric_version` configuration option_ |
+| [Telegraf Prometheus plugin](/{{< latest "telegraf" >}}/plugins/#input-prometheus)         | _Determined by `metric_version` configuration option_ |
 | Flux [`prometheus.scrape()`]({{< latest "flux" >}}/stdlib/experimental/prometheus/scrape/) |                                                     2 |
 
 {{% /cloud-only %}}
diff --git a/content/influxdb/v2.0/tools/kapacitor.md b/content/influxdb/v2.0/tools/kapacitor.md
index 180a2b047..017310c50 100644
--- a/content/influxdb/v2.0/tools/kapacitor.md
+++ b/content/influxdb/v2.0/tools/kapacitor.md
@@ -95,7 +95,7 @@ see [Write back to InfluxDB](#write-back-to-influxdb) below.
 InfluxDB Cloud and OSS 2.0 do not have subscription APIs and do not support Kapacitor stream tasks directly.
 To use Kapacitor stream tasks, write data directly to Kapacitor using the [Kapcitior `write` API](/{{< latest "kapacitor" >}}/working/api/#writing-data).
 
-We recommend using [Telegraf InfluxDB output plugin](/{{< latest "telegraf" >}}/plugins/#influxdb)
+We recommend using [Telegraf InfluxDB output plugin](/{{< latest "telegraf" >}}/plugins/#output-influxdb)
 to write data to both InfluxDB Cloud or OSS and Kapacitor.
 The following example Telegraf configuration writes data to both InfluxDB and Kapacitor:
 
diff --git a/content/influxdb/v2.0/upgrade/v1-to-v2/automatic-upgrade.md b/content/influxdb/v2.0/upgrade/v1-to-v2/automatic-upgrade.md
index 3a6174a37..0e752f345 100644
--- a/content/influxdb/v2.0/upgrade/v1-to-v2/automatic-upgrade.md
+++ b/content/influxdb/v2.0/upgrade/v1-to-v2/automatic-upgrade.md
@@ -77,8 +77,8 @@ You can continue to use Kapacitor with InfluxDB OSS 2.0 under the following scen
   Existing Kapacitor user credentials should continue to work using the [1.x compatibility API](/influxdb/v2.0/reference/api/influxdb-1x/).
 - InfluxDB 2.0 has no subscriptions API and does not support Kapacitor stream tasks.
   To continue using stream tasks, write data directly to both InfluxDB and Kapacitor.
-  Use **Telegraf** and its [InfluxDB output plugin](/{{< latest "telegraf" >}}/plugins/#influxdb)
-  to write to Kapacitor and the [InfluxDB v2 output plugin](/{{< latest "telegraf" >}}/plugins/#influxdb_v2) to write to InfluxDB v2.
+  Use **Telegraf** and its [InfluxDB output plugin](/{{< latest "telegraf" >}}/plugins/#output-influxdb)
+  to write to Kapacitor and the [InfluxDB v2 output plugin](/{{< latest "telegraf" >}}/plugins/#output-influxdb_v2) to write to InfluxDB v2.
 
 ##### Example Telegraf configuration
 ```toml
diff --git a/content/influxdb/v2.0/visualize-data/variables/common-variables.md b/content/influxdb/v2.0/visualize-data/variables/common-variables.md
index 4ebee2fb9..81f073b69 100644
--- a/content/influxdb/v2.0/visualize-data/variables/common-variables.md
+++ b/content/influxdb/v2.0/visualize-data/variables/common-variables.md
@@ -67,7 +67,7 @@ schema.tagValues(bucket: "bucket-name", tag: "host")
 ## List Docker containers
 List all Docker containers when using the Docker Telegraf plugin.
 
-_**Telegraf plugin:** [Docker](/{{< latest "telegraf" >}}/plugins/#docker)_  
+_**Telegraf plugin:** [Docker](/{{< latest "telegraf" >}}/plugins/#input-docker)_  
 _**Flux package:** [InfluxDB schema](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/)_  
 _**Flux functions:** [schema.tagValues()](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/tagvalues/)_
 
@@ -80,7 +80,7 @@ schema.tagValues(bucket: "bucket-name", tag: "container_name")
 ## List Kubernetes pods
 List all Kubernetes pods when using the Kubernetes Telegraf plugin.
 
-_**Telegraf plugin:** [Kubernetes](/{{< latest "telegraf" >}}/plugins/#kubernetes)_  
+_**Telegraf plugin:** [Kubernetes](/{{< latest "telegraf" >}}/plugins/#input-kubernetes)_  
 _**Flux package:** [InfluxDB schema](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/)_  
 _**Flux functions:** [schema.measurementTagValues()](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/measurementtagvalues/)_
 
@@ -97,7 +97,7 @@ schema.measurementTagValues(
 ## List Kubernetes nodes
 List all Kubernetes nodes when using the Kubernetes Telegraf plugin.
 
-_**Telegraf plugin:** [Kubernetes](/{{< latest "telegraf" >}}/plugins/#kubernetes)_  
+_**Telegraf plugin:** [Kubernetes](/{{< latest "telegraf" >}}/plugins/#input-kubernetes)_  
 _**Flux package:** [InfluxDB schema](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/)_  
 _**Flux functions:** [schema.measurementTagValues()](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/measurementtagvalues/)_
 
diff --git a/content/influxdb/v2.0/write-data/developer-tools/scrape-prometheus-metrics.md b/content/influxdb/v2.0/write-data/developer-tools/scrape-prometheus-metrics.md
index 0f69e4fd8..8589b891c 100644
--- a/content/influxdb/v2.0/write-data/developer-tools/scrape-prometheus-metrics.md
+++ b/content/influxdb/v2.0/write-data/developer-tools/scrape-prometheus-metrics.md
@@ -11,7 +11,7 @@ menu:
     name: Scrape Prometheus metrics
     parent: Developer tools
 related:
-  - /{{< latest "telegraf" >}}/plugins/#prometheus, Telegraf Prometheus input plugin
+  - /{{< latest "telegraf" >}}/plugins/#input-prometheus, Telegraf Prometheus input plugin
   - /{{< latest "flux" >}}/prometheus/scrape-prometheus/, Scrape Prometheus metrics with Flux
   - /{{< latest "flux" >}}/stdlib/experimental/prometheus/scrape/
   - /{{< latest "flux" >}}/prometheus/metric-types/
@@ -42,12 +42,12 @@ to scrape Prometheus-formatted metrics from an HTTP-accessible endpoint and stor
 To use Telegraf to scrape Prometheus-formatted metrics from an HTTP-accessible
 endpoint and write them to InfluxDB{{% cloud-only %}} Cloud{{% /cloud-only %}}, follow these steps:
 
-1. Add the [Prometheus input plugin](/{{< latest "telegraf" >}}/plugins/#prometheus) to your Telegraf configuration file.
+1. Add the [Prometheus input plugin](/{{< latest "telegraf" >}}/plugins/#input-prometheus) to your Telegraf configuration file.
     1. Set the `urls` to scrape metrics from.
     2. Set the `metric_version` configuration option to specify which
       [metric parsing version](/influxdb/v2.0/reference/prometheus-metrics/) to use
       _(version `2` is recommended)_.
-2. Add the [InfluxDB v2 output plugin](/{{< latest "telegraf" >}}/plugins/#influxdb_v2)
+2. Add the [InfluxDB v2 output plugin](/{{< latest "telegraf" >}}/plugins/#output-influxdb_v2)
    to your Telegraf configuration file and configure it to to write to
    InfluxDB{{% cloud-only %}} Cloud{{% /cloud-only %}}.
   
diff --git a/content/influxdb/v2.1/api-guide/client-libraries/arduino.md b/content/influxdb/v2.1/api-guide/client-libraries/arduino.md
index 222e7c38b..f4e2f1cbd 100644
--- a/content/influxdb/v2.1/api-guide/client-libraries/arduino.md
+++ b/content/influxdb/v2.1/api-guide/client-libraries/arduino.md
@@ -9,6 +9,7 @@ menu:
   influxdb_2_1:
     name: Arduino
     parent: Client libraries
-    url: https://github.com/tobiasschuerg/InfluxDB-Client-for-Arduino
+    params:
+      url: https://github.com/tobiasschuerg/InfluxDB-Client-for-Arduino
 weight: 201
 ---
diff --git a/content/influxdb/v2.1/api-guide/client-libraries/csharp.md b/content/influxdb/v2.1/api-guide/client-libraries/csharp.md
index cc1926510..8e134e496 100644
--- a/content/influxdb/v2.1/api-guide/client-libraries/csharp.md
+++ b/content/influxdb/v2.1/api-guide/client-libraries/csharp.md
@@ -8,6 +8,7 @@ menu:
   influxdb_2_1:
     name: C#
     parent: Client libraries
-    url: https://github.com/influxdata/influxdb-client-csharp
+    params:
+      url: https://github.com/influxdata/influxdb-client-csharp
 weight: 201
 ---
diff --git a/content/influxdb/v2.1/api-guide/client-libraries/dart.md b/content/influxdb/v2.1/api-guide/client-libraries/dart.md
index b581e7204..33570854e 100644
--- a/content/influxdb/v2.1/api-guide/client-libraries/dart.md
+++ b/content/influxdb/v2.1/api-guide/client-libraries/dart.md
@@ -8,6 +8,7 @@ menu:
   influxdb_2_1:
     name: Dart
     parent: Client libraries
-    url: https://github.com/influxdata/influxdb-client-dart
+    params:
+      url: https://github.com/influxdata/influxdb-client-dart
 weight: 201
 ---
diff --git a/content/influxdb/v2.1/api-guide/client-libraries/go.md b/content/influxdb/v2.1/api-guide/client-libraries/go.md
index 2d83f6996..5b2035bbc 100644
--- a/content/influxdb/v2.1/api-guide/client-libraries/go.md
+++ b/content/influxdb/v2.1/api-guide/client-libraries/go.md
@@ -124,11 +124,11 @@ Use the Go library to query data to InfluxDB.
 
 1. Create a Flux query and supply your `bucket` parameter.
 
-   ```js
-   from(bucket:"<bucket>")
-    |> range(start: -1h)
-    |> filter(fn: (r) => r._measurement == "stat")
-   ```
+    ```js
+    from(bucket:"<bucket>")
+        |> range(start: -1h)
+        |> filter(fn: (r) => r._measurement == "stat")
+    ```
 
    The query client sends the Flux query to InfluxDB and returns the results as a FluxRecord object with a table structure.
 
diff --git a/content/influxdb/v2.1/api-guide/client-libraries/java.md b/content/influxdb/v2.1/api-guide/client-libraries/java.md
index 05181f1dd..a17a0829e 100644
--- a/content/influxdb/v2.1/api-guide/client-libraries/java.md
+++ b/content/influxdb/v2.1/api-guide/client-libraries/java.md
@@ -8,6 +8,7 @@ menu:
   influxdb_2_1:
     name: Java
     parent: Client libraries
-    url: https://github.com/influxdata/influxdb-client-java
+    params:
+      url: https://github.com/influxdata/influxdb-client-java
 weight: 201
 ---
diff --git a/content/influxdb/v2.1/api-guide/client-libraries/kotlin.md b/content/influxdb/v2.1/api-guide/client-libraries/kotlin.md
index abb94d250..7848a64b6 100644
--- a/content/influxdb/v2.1/api-guide/client-libraries/kotlin.md
+++ b/content/influxdb/v2.1/api-guide/client-libraries/kotlin.md
@@ -8,6 +8,7 @@ menu:
   influxdb_2_1:
     name: Kotlin
     parent: Client libraries
-    url: https://github.com/influxdata/influxdb-client-java/tree/master/client-kotlin
+    params:
+      url: https://github.com/influxdata/influxdb-client-java/tree/master/client-kotlin
 weight: 201
 ---
diff --git a/content/influxdb/v2.1/api-guide/client-libraries/nodejs/install.md b/content/influxdb/v2.1/api-guide/client-libraries/nodejs/install.md
index 5396d40f1..ca3aa2dab 100644
--- a/content/influxdb/v2.1/api-guide/client-libraries/nodejs/install.md
+++ b/content/influxdb/v2.1/api-guide/client-libraries/nodejs/install.md
@@ -14,7 +14,7 @@ aliases:
 ---
 
 
-## Install Node.js 
+## Install Node.js
 
 1. Install [Node.js](https://nodejs.org/en/download/package-manager/).
 
@@ -25,7 +25,8 @@ aliases:
    The `npm` package manager is included with Node.js.
 
    ```sh
-   npm init -y influx-node-app
+   mkdir influx-node-app && cd influx-node-app
+   npm init -y
    ```
 
 ## Install TypeScript
@@ -69,7 +70,7 @@ Add both as dependencies of your project.
 
 Once you've installed the Javascript client library, you're ready to [write data](/influxdb/v2.1/api-guide/client-libraries/nodejs/write/) to InfluxDB or [get started](#get-started-with-examples) with other examples from the client library.
 
-## Get started with examples 
+## Get started with examples
 
 {{% note %}}
 The client examples include an [`env`](https://github.com/influxdata/influxdb-client-js/blob/master/examples/env.js) module for accessing your InfluxDB properties from environment variables or from `env.js`.
diff --git a/content/influxdb/v2.1/api-guide/client-libraries/nodejs/query.md b/content/influxdb/v2.1/api-guide/client-libraries/nodejs/query.md
index 3bf47bc7c..1e0186b41 100644
--- a/content/influxdb/v2.1/api-guide/client-libraries/nodejs/query.md
+++ b/content/influxdb/v2.1/api-guide/client-libraries/nodejs/query.md
@@ -51,8 +51,8 @@ The following example sends a Flux query to an InfluxDB bucket and outputs rows
    ```js
    const fluxQuery =
      'from(bucket: "YOUR_BUCKET")
-     |> range(start: 0)
-     |> filter(fn: (r) => r._measurement == "temperature")'
+      |> range(start: 0)
+      |> filter(fn: (r) => r._measurement == "temperature")'
    ```
    Replace *`YOUR_BUCKET`* with the name of your InfluxDB bucket.
 
diff --git a/content/influxdb/v2.1/api-guide/client-libraries/php.md b/content/influxdb/v2.1/api-guide/client-libraries/php.md
index cf263dcb5..0ad65c5b4 100644
--- a/content/influxdb/v2.1/api-guide/client-libraries/php.md
+++ b/content/influxdb/v2.1/api-guide/client-libraries/php.md
@@ -8,6 +8,7 @@ menu:
   influxdb_2_1:
     name: PHP
     parent: Client libraries
-    url: https://github.com/influxdata/influxdb-client-php
+    params:
+      url: https://github.com/influxdata/influxdb-client-php
 weight: 201
 ---
diff --git a/content/influxdb/v2.1/api-guide/client-libraries/r.md b/content/influxdb/v2.1/api-guide/client-libraries/r.md
index 20685100e..256687516 100644
--- a/content/influxdb/v2.1/api-guide/client-libraries/r.md
+++ b/content/influxdb/v2.1/api-guide/client-libraries/r.md
@@ -8,6 +8,7 @@ menu:
   influxdb_2_1:
     name: R
     parent: Client libraries
-    url: https://github.com/influxdata/influxdb-client-r
+    params:
+      url: https://github.com/influxdata/influxdb-client-r
 weight: 201
 ---
diff --git a/content/influxdb/v2.1/api-guide/client-libraries/ruby.md b/content/influxdb/v2.1/api-guide/client-libraries/ruby.md
index e38ff2082..1b09ae655 100644
--- a/content/influxdb/v2.1/api-guide/client-libraries/ruby.md
+++ b/content/influxdb/v2.1/api-guide/client-libraries/ruby.md
@@ -8,6 +8,7 @@ menu:
   influxdb_2_1:
     name: Ruby
     parent: Client libraries
-    url: https://github.com/influxdata/influxdb-client-ruby
+    params:
+      url: https://github.com/influxdata/influxdb-client-ruby
 weight: 201
 ---
diff --git a/content/influxdb/v2.1/api-guide/client-libraries/scala.md b/content/influxdb/v2.1/api-guide/client-libraries/scala.md
index 96c22f7be..4960e90e7 100644
--- a/content/influxdb/v2.1/api-guide/client-libraries/scala.md
+++ b/content/influxdb/v2.1/api-guide/client-libraries/scala.md
@@ -8,6 +8,7 @@ menu:
   influxdb_2_1:
     name: Scala
     parent: Client libraries
-    url: https://github.com/influxdata/influxdb-client-java/tree/master/client-scala
+    params:
+      url: https://github.com/influxdata/influxdb-client-java/tree/master/client-scala
 weight: 201
 ---
diff --git a/content/influxdb/v2.1/api-guide/client-libraries/swift.md b/content/influxdb/v2.1/api-guide/client-libraries/swift.md
index 420a2f228..8d0b13b24 100644
--- a/content/influxdb/v2.1/api-guide/client-libraries/swift.md
+++ b/content/influxdb/v2.1/api-guide/client-libraries/swift.md
@@ -8,6 +8,7 @@ menu:
   influxdb_2_1:
     name: Swift
     parent: Client libraries
-    url: https://github.com/influxdata/influxdb-client-swift
+    params:
+      url: https://github.com/influxdata/influxdb-client-swift
 weight: 201
 ---
diff --git a/content/influxdb/v2.1/influxdb-templates/_index.md b/content/influxdb/v2.1/influxdb-templates/_index.md
index 7dfde83ad..71f2e3886 100644
--- a/content/influxdb/v2.1/influxdb-templates/_index.md
+++ b/content/influxdb/v2.1/influxdb-templates/_index.md
@@ -4,7 +4,7 @@ description: >
   InfluxDB templates are prepackaged InfluxDB configurations that contain everything
   from dashboards and Telegraf configurations to notifications and alerts.
 menu: influxdb_2_1
-weight: 9
+weight: 10
 influxdb/v2.1/tags: [templates]
 ---
 
diff --git a/content/influxdb/v2.1/influxdb-templates/create.md b/content/influxdb/v2.1/influxdb-templates/create.md
index 3a3c2e581..87ac5c8f2 100644
--- a/content/influxdb/v2.1/influxdb-templates/create.md
+++ b/content/influxdb/v2.1/influxdb-templates/create.md
@@ -172,10 +172,10 @@ Provide the following:
 ```sh
 # Syntax
 influx export stack \
-  -o <org-name> \
-  -t <token> \
-  -f <file-path> \
-  <stack-id>
+  -o <INFLUX_ORG> \
+  -t <INFLUX_TOKEN> \
+  -f <FILE_PATH> \
+  <STACK_ID>
 
 # Example
 influx export stack \
diff --git a/content/influxdb/v2.1/install.md b/content/influxdb/v2.1/install.md
index f8f6ec58d..65bb7fd44 100644
--- a/content/influxdb/v2.1/install.md
+++ b/content/influxdb/v2.1/install.md
@@ -59,7 +59,7 @@ To download the InfluxDB v{{< current-version >}} binaries for macOS directly,
 do the following:
 
 1. **Download the InfluxDB package.**
-    
+
     <a class="btn download" href="https://dl.influxdata.com/influxdb/releases/influxdb2-{{< latest-patch >}}-darwin-amd64.tar.gz" download>InfluxDB v{{< current-version >}} (macOS)</a>
 
 
@@ -732,8 +732,33 @@ influx setup
    nanoseconds (`ns`), microseconds (`us` or `µs`), milliseconds (`ms`),
    seconds (`s`), minutes (`m`), hours (`h`), days (`d`), and weeks (`w`).
    Enter nothing for an infinite retention period.
+
 7. Confirm the details for your primary user, organization, and bucket.
 
+    ```sh
+    $ influx setup --name kube1
+    > Welcome to InfluxDB 2.0!
+    ? Please type your primary username kube1-owner
+    ? Please type your password ********
+    ? Please type your password again ********
+    ? Please type your primary organization name kube1-org1
+    ? Please type your primary bucket name airSensor
+    ? Please type your retention period in hours, or 0 for infinite 0
+    ? Setup with these parameters?
+      Username:          kube1-owner
+      Organization:      kube1-org1
+      Bucket:            airSensor
+      Retention Period:  infinite
+     (y/N)
+    ```
+
+8. Once you confirm the setup, InfluxDB outputs a table of the configuration.
+
+    ```sh
+    User            Organization    Bucket
+    kube1-owner     kube1-org1      airSensor
+    ```
+
 InfluxDB is now initialized with a primary user, organization, bucket, and API token.
 InfluxDB also creates a configuration profile for you so that you don't have to
 add your InfluxDB host, organization, and token to every command.
diff --git a/content/influxdb/v2.1/migrate-data/_index.md b/content/influxdb/v2.1/migrate-data/_index.md
new file mode 100644
index 000000000..7509d0345
--- /dev/null
+++ b/content/influxdb/v2.1/migrate-data/_index.md
@@ -0,0 +1,15 @@
+---
+title: Migrate data to InfluxDB
+description: >
+  Migrate data to InfluxDB from other InfluxDB instances including by InfluxDB OSS
+  and InfluxDB Cloud.
+menu:
+  influxdb_2_1:
+    name: Migrate data
+weight: 9
+---
+
+Migrate data to InfluxDB from other InfluxDB instances including by InfluxDB OSS
+and InfluxDB Cloud.
+
+{{< children >}}
diff --git a/content/influxdb/v2.1/migrate-data/migrate-cloud-to-oss.md b/content/influxdb/v2.1/migrate-data/migrate-cloud-to-oss.md
new file mode 100644
index 000000000..b2373ffc4
--- /dev/null
+++ b/content/influxdb/v2.1/migrate-data/migrate-cloud-to-oss.md
@@ -0,0 +1,372 @@
+---
+title: Migrate data from InfluxDB Cloud to InfluxDB OSS
+description: >
+  To migrate data from InfluxDB Cloud to InfluxDB OSS, query the data from
+  InfluxDB Cloud in time-based batches and write the data to InfluxDB OSS.
+menu:
+  influxdb_2_1:
+    name: Migrate from Cloud to OSS
+    parent: Migrate data
+weight: 102
+---
+
+To migrate data from InfluxDB Cloud to InfluxDB OSS, query the data
+from InfluxDB Cloud and write the data to InfluxDB OSS.
+Because full data migrations will likely exceed your organization's limits and
+adjustable quotas, migrate your data in batches.
+
+The following guide provides instructions for setting up an InfluxDB OSS task
+that queries data from an InfluxDB Cloud bucket in time-based batches and writes
+each batch to an InfluxDB OSS bucket.
+
+{{% cloud %}}
+All queries against data in InfluxDB Cloud are subject to your organization's
+[rate limits and adjustable quotas](/influxdb/cloud/account-management/limits/).
+{{% /cloud %}}
+
+- [Set up the migration](#set-up-the-migration)
+- [Migration task](#migration-task)
+  - [Configure the migration](#configure-the-migration)
+  - [Migration Flux script](#migration-flux-script)
+  - [Configuration help](#configuration-help)
+- [Monitor the migration progress](#monitor-the-migration-progress)
+- [Troubleshoot migration task failures](#troubleshoot-migration-task-failures)
+
+## Set up the migration
+1.  [Install and set up InfluxDB OSS](/influxdb/{{< current-version-link >}}/install/).
+
+2.  **In InfluxDB Cloud**, [create an API token](/influxdb/cloud/security/tokens/create-token/)
+        with **read access** to the bucket you want to migrate.
+
+3.  **In InfluxDB OSS**:
+    1.  Add your **InfluxDB Cloud API token** as a secret using the key,
+        `INFLUXDB_CLOUD_TOKEN`.
+        _See [Add secrets](/influxdb/{{< current-version-link >}}/security/secrets/add/) for more information._
+    2.  [Create a bucket](/influxdb/{{< current-version-link >}}/organizations/buckets/create-bucket/)
+        **to migrate data to**.
+    3.  [Create a bucket](/influxdb/{{< current-version-link >}}/organizations/buckets/create-bucket/)
+        **to store temporary migration metadata**.
+    4.  [Create a new task](/influxdb/{{< current-version-link >}}/process-data/manage-tasks/create-task/)
+        using the provided [migration task](#migration-task).
+        Update the necessary [migration configuration options](#configure-the-migration).
+    5.  _(Optional)_ Set up [migration monitoring](#monitor-the-migration-progress).
+    6.  Save the task.
+
+        {{% note %}}
+Newly-created tasks are enabled by default, so the data migration begins when you save the task.
+        {{% /note %}}
+
+**After the migration is complete**, each subsequent migration task execution
+will fail with the following error:
+
+```
+error exhausting result iterator: error calling function "die" @41:9-41:86:
+Batch range is beyond the migration range. Migration is complete.
+```
+
+## Migration task
+
+### Configure the migration
+1.  Specify how often you want the task to run using the `task.every` option.
+    _See [Determine your task interval](#determine-your-task-interval)._
+
+2.  Define the following properties in the `migration`
+    [record](/{{< latest "flux" >}}/data-types/composite/record/):
+
+    ##### migration
+    - **start**: Earliest time to include in the migration.
+      _See [Determine your migration start time](#determine-your-migration-start-time)._
+    - **stop**: Latest time to include in the migration.
+    - **batchInterval**: Duration of each time-based batch.
+      _See [Determine your batch interval](#determine-your-batch-interval)._
+    - **batchBucket**: InfluxDB OSS bucket to store migration batch metadata in.
+    - **sourceHost**: [InfluxDB Cloud region URL](/influxdb/cloud/reference/regions)
+      to migrate data from.
+    - **sourceOrg**: InfluxDB Cloud organization to migrate data from.
+    - **sourceToken**: InfluxDB Cloud API token. To keep the API token secure, store
+      it as a secret in InfluxDB OSS.
+    - **sourceBucket**: InfluxDB Cloud bucket to migrate data from.
+    - **destinationBucket**: InfluxDB OSS bucket to migrate data to.
+
+### Migration Flux script
+
+```js
+import "array"
+import "experimental"
+import "influxdata/influxdb/secrets"
+
+// Configure the task
+option task = {every: 5m, name: "Migrate data from InfluxDB Cloud"}
+
+// Configure the migration
+migration = {
+    start: 2022-01-01T00:00:00Z,
+    stop: 2022-02-01T00:00:00Z,
+    batchInterval: 1h,
+    batchBucket: "migration",
+    sourceHost: "https://cloud2.influxdata.com",
+    sourceOrg: "example-cloud-org",
+    sourceToken: secrets.get(key: "INFLUXDB_CLOUD_TOKEN"),
+    sourceBucket: "example-cloud-bucket",
+    destinationBucket: "example-oss-bucket",
+}
+
+// batchRange dynamically returns a record with start and stop properties for
+// the current batch. It queries migration metadata stored in the
+// `migration.batchBucket` to determine the stop time of the previous batch.
+// It uses the previous stop time as the new start time for the current batch
+// and adds the `migration.batchInterval` to determine the current batch stop time.
+batchRange = () => {
+    _lastBatchStop =
+        (from(bucket: migration.batchBucket)
+            |> range(start: migration.start)
+            |> filter(fn: (r) => r._field == "batch_stop")
+            |> filter(fn: (r) => r.srcOrg == migration.sourceOrg)
+            |> filter(fn: (r) => r.srcBucket == migration.sourceBucket)
+            |> last()
+            |> findRecord(fn: (key) => true, idx: 0))._value
+    _batchStart =
+        if exists _lastBatchStop then
+            time(v: _lastBatchStop)
+        else
+            migration.start
+
+    return {start: _batchStart, stop: experimental.addDuration(d: migration.batchInterval, to: _batchStart)}
+}
+
+// Define a static record with batch start and stop time properties
+batch = {start: batchRange().start, stop: batchRange().stop}
+
+// Check to see if the current batch start time is beyond the migration.stop
+// time and exit with an error if it is.
+finished =
+    if batch.start >= migration.stop then
+        die(msg: "Batch range is beyond the migration range. Migration is complete.")
+    else
+        "Migration in progress"
+
+// Query all data from the specified source bucket within the batch-defined time
+// range. To limit migrated data by measurement, tag, or field, add a `filter()`
+// function after `range()` with the appropriate predicate fn.
+data = () =>
+    from(host: migration.sourceHost, org: migration.sourceOrg, token: migration.sourceToken, bucket: migration.sourceBucket)
+        |> range(start: batch.start, stop: batch.stop)
+
+// rowCount is a stream of tables that contains the number of rows returned in
+// the batch and is used to generate batch metadata.
+rowCount =
+    data()
+        |> group(columns: ["_start", "_stop"])
+        |> count()
+
+// emptyRange is a stream of tables that acts as filler data if the batch is
+// empty. This is used to generate batch metadata for empty batches and is
+// necessary to correctly increment the time range for the next batch.
+emptyRange = array.from(rows: [{_start: batch.start, _stop: batch.stop, _value: 0}])
+
+// metadata returns a stream of tables representing batch metadata.
+metadata = () => {
+    _input =
+        if exists (rowCount |> findRecord(fn: (key) => true, idx: 0))._value then
+            rowCount
+        else
+            emptyRange
+
+    return
+        _input
+            |> map(
+                fn: (r) =>
+                    ({
+                        _time: now(),
+                        _measurement: "batches",
+                        srcOrg: migration.sourceOrg,
+                        srcBucket: migration.sourceBucket,
+                        dstBucket: migration.destinationBucket,
+                        batch_start: string(v: batch.start),
+                        batch_stop: string(v: batch.stop),
+                        rows: r._value,
+                        percent_complete:
+                            float(v: int(v: r._stop) - int(v: migration.start)) / float(
+                                    v: int(v: migration.stop) - int(v: migration.start),
+                                ) * 100.0,
+                    }),
+            )
+            |> group(columns: ["_measurement", "srcOrg", "srcBucket", "dstBucket"])
+}
+
+// Write the queried data to the specified InfluxDB OSS bucket.
+data()
+    |> to(bucket: migration.destinationBucket)
+
+// Generate and store batch metadata in the migration.batchBucket.
+metadata()
+    |> experimental.to(bucket: migration.batchBucket)
+```
+
+### Configuration help
+
+{{< expand-wrapper >}}
+
+<!----------------------- BEGIN Determine task interval ----------------------->
+{{% expand "Determine your task interval" %}}
+
+The task interval determines how often the migration task runs and is defined by
+the [`task.every` option](/influxdb/v2.1/process-data/task-options/#every).
+InfluxDB Cloud rate limits and quotas reset every five minutes, so
+**we recommend a `5m` task interval**.
+
+You can do shorter task intervals and execute the migration task more often,
+but you need to balance the task interval with your [batch interval](#determine-your-batch-interval) 
+and the amount of data returned in each batch.
+If the total amount of data queried in each five-minute interval exceeds your
+InfluxDB Cloud organization's [rate limits and quotas](/influxdb/cloud/account-management/limits/),
+the batch will fail until rate limits and quotas reset.
+
+{{% /expand %}}
+<!------------------------ END Determine task interval ------------------------>
+
+<!---------------------- BEGIN Determine migration start ---------------------->
+{{% expand "Determine your migration start time" %}}
+
+The `migration.start` time should be at or near the same time as the earliest
+data point you want to migrate.
+All migration batches are determined using the `migration.start` time and
+`migration.batchInterval` settings.
+
+To find time of the earliest point in your bucket, run the following query:
+
+```js
+from(bucket: "example-cloud-bucket")
+    |> range(start: 0)
+    |> group()
+    |> first()
+    |> keep(columns: ["_time"])
+```
+
+{{% /expand %}}
+<!----------------------- END Determine migration start ----------------------->
+
+<!----------------------- BEGIN Determine batch interval ---------------------->
+{{% expand "Determine your batch interval" %}}
+
+The `migration.batchInterval` setting controls the time range queried by each batch.
+The "density" of the data in your InfluxDB Cloud bucket and your InfluxDB Cloud
+organization's [rate limits and quotas](/influxdb/cloud/account-management/limits/)
+determine what your batch interval should be.
+
+For example, if you're migrating data collected from hundreds of sensors with
+points recorded every second, your batch interval will need to be shorter.
+If you're migrating data collected from five sensors with points recorded every
+minute, your batch interval can be longer.
+It all depends on how much data gets returned in a single batch.
+
+If points occur at regular intervals, you can get a fairly accurate estimate of
+how much data will be returned in a given time range by using the `/api/v2/query`
+endpoint to execute a query for the time range duration and then measuring the
+size of the response body.
+
+The following `curl` command queries an InfluxDB Cloud bucket for the last day
+and returns the size of the response body in bytes.
+You can customize the range duration to match your specific use case and
+data density.
+
+```sh
+INFLUXDB_CLOUD_ORG=<your_influxdb_cloud_org>
+INFLUXDB_CLOUD_TOKEN=<your_influxdb_cloud_token>
+INFLUXDB_CLOUD_BUCKET=<your_influxdb_cloud_bucket>
+
+curl -so /dev/null --request POST \
+  https://cloud2.influxdata.com/api/v2/query?org=$INFLUXDB_CLOUD_ORG  \
+  --header "Authorization: Token $INFLUXDB_CLOUD_TOKEN" \
+  --header "Accept: application/csv" \
+  --header "Content-type: application/vnd.flux" \
+  --data "from(bucket:\"$INFLUXDB_CLOUD_BUCKET\") |> range(start: -1d, stop: now())" \
+  --write-out '%{size_download}'
+```
+
+{{% note %}}
+You can also use other HTTP API tools like [Postman](https://www.postman.com/)
+that provide the size of the response body.
+{{% /note %}}
+
+Divide the output of this command by 1000000 to convert it to megabytes (MB).
+
+```
+batchInterval = (read-rate-limit-mb / response-body-size-mb) * range-duration
+```
+
+For example, if the response body of your query that returns data from one day 
+is 8 MB and you're using the InfluxDB Cloud Free Plan with a read limit of
+300 MB per five minutes:
+
+```js
+batchInterval = (300 / 8) * 1d
+// batchInterval = 37d
+```
+
+You could query 37 days of data before hitting your read limit, but this is just an estimate.
+We recommend setting the `batchInterval` slightly lower than the calculated interval
+to allow for variation between batches.
+So in this example, **it would be best to set your `batchInterval` to `35d`**.
+
+##### Important things to note
+- This assumes no other queries are running in your InfluxDB Cloud organization.
+- You should also consider your network speeds and whether a batch can be fully
+  downloaded within the [task interval](#determine-your-task-interval).
+
+{{% /expand %}}
+<!------------------------ END Determine batch interval ----------------------->
+{{< /expand-wrapper >}}
+
+## Monitor the migration progress
+The [InfluxDB Cloud Migration Community template](https://github.com/influxdata/community-templates/tree/master/influxdb-cloud-oss-migration/)
+installs the migration task outlined in this guide as well as a dashboard
+for monitoring running data migrations.
+
+{{< img-hd src="/img/influxdb/2-1-migration-dashboard.png" alt="InfluxDB Cloud migration dashboard" />}}
+
+<a class="btn" href="https://github.com/influxdata/community-templates/tree/master/influxdb-cloud-oss-migration/#quick-install">Install the InfluxDB Cloud Migration template</a>
+
+## Troubleshoot migration task failures
+If the migration task fails, [view your task logs](/influxdb/v2.1/process-data/manage-tasks/task-run-history/)
+to identify the specific error. Below are common causes of migration task failures.
+
+- [Exceeded rate limits](#exceeded-rate-limits)
+- [Invalid API token](#invalid-api-token)
+- [Query timeout](#query-timeout)
+
+### Exceeded rate limits
+If your data migration causes you to exceed your InfluxDB Cloud organization's
+limits and quotas, the task will return an error similar to:
+
+```
+too many requests
+```
+
+**Possible solutions**:
+- Update the `migration.batchInterval` setting in your migration task to use
+  a smaller interval. Each batch will then query less data.
+
+### Invalid API token
+If the API token you add as the `INFLUXDB_CLOUD_SECRET` doesn't have read access to
+your InfluxDB Cloud bucket, the task will return an error similar to:
+
+```
+unauthorized access
+```
+
+**Possible solutions**:
+- Ensure the API token has read access to your InfluxDB Cloud bucket.
+- Generate a new InfluxDB Cloud API token with read access to the bucket you
+  want to migrate. Then, update the `INFLUXDB_CLOUD_TOKEN` secret in your
+  InfluxDB OSS instance with the new token.
+
+### Query timeout
+The InfluxDB Cloud query timeout is 90 seconds. If it takes longer than this to
+return the data from the batch interval, the query will time out and the
+task will fail.
+
+**Possible solutions**:
+- Update the `migration.batchInterval` setting in your migration task to use
+  a smaller interval. Each batch will then query less data and take less time
+  to return results.
diff --git a/content/influxdb/v2.1/migrate-data/migrate-oss.md b/content/influxdb/v2.1/migrate-data/migrate-oss.md
new file mode 100644
index 000000000..f6febc2a5
--- /dev/null
+++ b/content/influxdb/v2.1/migrate-data/migrate-oss.md
@@ -0,0 +1,64 @@
+---
+title: Migrate data from InfluxDB OSS to other InfluxDB instances
+description: >
+  To migrate data from an InfluxDB OSS bucket to another InfluxDB OSS or InfluxDB
+  Cloud bucket, export your data as line protocol and write it to your other
+  InfluxDB bucket.
+menu:
+  influxdb_2_1:
+    name: Migrate data from OSS
+    parent: Migrate data
+weight: 101
+---
+
+To migrate data from an InfluxDB OSS bucket to another InfluxDB OSS or InfluxDB
+Cloud bucket, export your data as line protocol and write it to your other
+InfluxDB bucket.
+
+{{% cloud %}}
+#### InfluxDB Cloud write limits
+If migrating data from InfluxDB OSS to InfluxDB Cloud, you are subject to your
+[InfluxDB Cloud organization's rate limits and adjustable quotas](/influxdb/cloud/account-management/limits/).
+Consider exporting your data in time-based batches to limit the file size
+of exported line protocol to match your InfluxDB Cloud organization's limits.
+{{% /cloud %}}
+
+1.  [Find the InfluxDB OSS bucket ID](/influxdb/v2.1/organizations/buckets/view-buckets/)
+    that contains data you want to migrate.
+2.  Use the `influxd inspect export-lp` command to export data in your bucket as
+    [line protocol](/influxdb/v2.1/reference/syntax/line-protocol/).
+    Provide the following:
+
+    - **bucket ID**: ({{< req >}}) ID of the bucket to migrate.
+    - **engine path**: ({{< req >}}) Path to the TSM storage files on disk.
+      The default engine path [depends on your operating system](/influxdb/v2.1/reference/internals/file-system-layout/#file-system-layout),
+      If using a [custom engine-path](/influxdb/v2.1/reference/config-options/#engine-path)
+      provide your custom path.
+    - **output path**: ({{< req >}}) File path to output line protocol to.
+    - **start time**: Earliest time to export.
+    - **end time**: Latest time to export.
+    - **measurement**: Export a specific measurement. By default, the command
+      exports all measurements.
+    - **compression**: ({{< req text="Recommended" color="magenta" >}})
+      Use Gzip compression to compress the output line protocol file.
+
+    ```sh
+    influxd inspect export-lp \
+      --bucket-id 12ab34cd56ef \
+      --engine-path ~/.influxdbv2/engine \
+      --output-path path/to/export.lp
+      --start 2022-01-01T00:00:00Z \
+      --end 2022-01-31T23:59:59Z \
+      --compress
+    ```
+
+3.  Write the exported line protocol to your InfluxDB OSS or InfluxDB Cloud instance.
+    
+    Do any of the following:
+
+    - Write line protocol in the **InfluxDB UI**:
+        - [InfluxDB Cloud UI](/influxdb/cloud/write-data/no-code/load-data/#load-csv-or-line-protocol-in-ui)
+        - [InfluxDB OSS {{< current-version >}} UI](/influxdb/v2.1/write-data/no-code/load-data/#load-csv-or-line-protocol-in-ui)
+    - [Write line protocol using the `influx write` command](/influxdb/v2.1/reference/cli/influx/write/)
+    - [Write line protocol using the InfluxDB API](/influxdb/v2.1/write-data/developer-tools/api/)
+    - [Bulk ingest data (InfluxDB Cloud)](/influxdb/cloud/write-data/bulk-ingest-cloud/)
diff --git a/content/influxdb/v2.1/monitor-alert/custom-checks.md b/content/influxdb/v2.1/monitor-alert/custom-checks.md
index cd3285896..d65e38a01 100644
--- a/content/influxdb/v2.1/monitor-alert/custom-checks.md
+++ b/content/influxdb/v2.1/monitor-alert/custom-checks.md
@@ -70,11 +70,11 @@ task_data = from(bucket: "_tasks")
     |> last()
 
 check = {
-		// 16 characters, alphanumeric
+    // 16 characters, alphanumeric
     _check_id: "0000000000000001",
-		// Name string
+    // Name string
     _check_name: "Failed Tasks Check",
-		// Check type (threshold, deadman, or custom)
+    // Check type (threshold, deadman, or custom)
     _type: "custom",
     tags: {},
 }
@@ -84,12 +84,7 @@ messageFn = (r) => "The task: ${r.taskID} - ${r.name} has a status of ${r.status
 
 task_data
     |> schema["fieldsAsCols"]()
-    |> monitor["check"](
-        data: check,
-        messageFn: messageFn,
-        ok: ok,
-        crit: crit,
-    )
+    |> monitor["check"](data: check, messageFn: messageFn, ok: ok, crit: crit)
 ```
 
 {{% note %}}
diff --git a/content/influxdb/v2.1/monitor-alert/send-email.md b/content/influxdb/v2.1/monitor-alert/send-email.md
index 788995ee6..a585ad955 100644
--- a/content/influxdb/v2.1/monitor-alert/send-email.md
+++ b/content/influxdb/v2.1/monitor-alert/send-email.md
@@ -65,7 +65,6 @@ The example below uses the SendGrid API to send an alert email when more than 3
 ```js
 import "http"
 import "json"
-
 // Import the Secrets package if you store your API key as a secret.
 // For detail on how to do this, see Step 4 above.
 import "influxdata/influxdb/secrets"
@@ -75,39 +74,43 @@ import "influxdata/influxdb/secrets"
 SENDGRID_APIKEY = secrets.get(key: "SENDGRID_APIKEY")
 
 numberOfCrits = from(bucket: "_monitoring")
-	|> range(start: -task.every)
-	|> filter(fn: (r) => r._measurement == "statuses" and r._level == "crit")
-	|> count()
+    |> range(start: -task.every)
+    |> filter(fn: (r) => r._measurement == "statuses" and r._level == "crit")
+    |> count()
 
 numberOfCrits
-  |> map(fn: (r) => (if r._value > 3 then {
-    r with _value: http.post(
-      url: "https://api.sendgrid.com/v3/mail/send",
-      headers: {
-        "Content-Type": "application/json",
-        "Authorization": "Bearer ${SENDGRID_APIKEY}"
-      },
-      data: json.encode(v: {
-        "personalizations": [
-          {
-            "to": [
-              {
-                "email": "jane.doe@example.com"
-              }
-            ]
-          }
-        ],
-        "from": {
-          "email": "john.doe@example.com"
-        },
-        "subject": "InfluxDB critical alert",
-        "content": [
-          {
-            "type": "text/plain",
-            "value": "There have been ${r._value} critical statuses."
-          }
-        ]
-      }))} else {r with _value: 0}))
+    |> map(
+        fn: (r) => if r._value > 3 then
+            {r with _value: http.post(
+                url: "https://api.sendgrid.com/v3/mail/send",
+                headers: {"Content-Type": "application/json", "Authorization": "Bearer ${SENDGRID_APIKEY}"},
+                data: json.encode(
+                    v: {
+                        "personalizations": [
+                            {
+                                "to": [
+                                    {
+                                        "email": "jane.doe@example.com"
+                                    }
+                                ]
+                            }
+                        ],
+                        "from": {
+                            "email": "john.doe@example.com"
+                        },
+                        "subject": "InfluxDB critical alert",
+                        "content": [
+                            {
+                                "type": "text/plain",
+                                "value": "There have been ${r._value} critical statuses."
+                            }
+                        ]
+                    }
+                )
+            )}
+        else
+            {r with _value: 0},
+    )
 ```
 
 {{% /tab-content %}}
@@ -124,7 +127,6 @@ Your AWS SES request, including the `url` (endpoint), authentication, and the st
 ```js
 import "http"
 import "json"
-
 // Import the Secrets package if you store your API credentials as secrets.
 // For detail on how to do this, see Step 4 above.
 import "influxdata/influxdb/secrets"
@@ -137,39 +139,44 @@ AWS_SIGNED_HEADERS = secrets.get(key: "AWS_SIGNED_HEADERS")
 AWS_CALCULATED_SIGNATURE = secrets.get(key: "AWS_CALCULATED_SIGNATURE")
 
 numberOfCrits = from(bucket: "_monitoring")
-	|> range(start: -task.every)
-	|> filter(fn: (r) => r.measurement == "statuses" and r._level == "crit")
-	|> count()
+    |> range(start: -task.every)
+    |> filter(fn: (r) => r.measurement == "statuses" and r._level == "crit")
+    |> count()
 
 numberOfCrits
-  |> map(fn: (r) => (if r._value > 3 then {
-      r with _value: http.post(
-        url: "https://email.your-aws-region.amazonaws.com/sendemail/v2/email/outbound-emails",
-        headers: {
-          "Content-Type": "application/json",
-          "Authorization": "Bearer ${AWS_AUTH_ALGORITHM}${AWS_CREDENTIAL}${AWS_SIGNED_HEADERS}${AWS_CALCULATED_SIGNATURE}"
-        },
-        data: json.encode(v: {
-          "Content": {
-            "Simple": {
-              "Body": {
-                "Text": {
-                  "Charset": "UTF-8",
-                  "Data": "There have been ${r._value} critical statuses."
-                }
-              },
-              "Subject": {
-                "Charset": "UTF-8",
-                "Data": "InfluxDB critical alert"
-              }
-            }
-          },
-          "Destination": {
-            "ToAddresses": [
-              "john.doe@example.com"
-            ]
-          }
-        }))} else {r with _value: 0}))
+    |> map(
+        fn: (r) => if r._value > 3 then
+            {r with _value: http.post(
+                url: "https://email.your-aws-region.amazonaws.com/sendemail/v2/email/outbound-emails",
+                headers: {
+                    "Content-Type": "application/json",
+                    "Authorization": "Bearer ${AWS_AUTH_ALGORITHM}${AWS_CREDENTIAL}${AWS_SIGNED_HEADERS}${AWS_CALCULATED_SIGNATURE}"},
+                data: json.encode(v: {
+                        "Content": {
+                            "Simple": {
+                                "Body": {
+                                    "Text": {
+                                        "Charset": "UTF-8",
+                                        "Data": "There have been ${r._value} critical statuses."
+                                    }
+                                },
+                                "Subject": {
+                                    "Charset": "UTF-8",
+                                    "Data": "InfluxDB critical alert"
+                                }
+                            }
+                        },
+                        "Destination": {
+                            "ToAddresses": [
+                                "john.doe@example.com"
+                            ]
+                        }
+                    }
+                )
+            )}
+        else
+            {r with _value: 0},
+    )
 ```
 
 For details on the request syntax, see [SendEmail API v2 reference](https://docs.aws.amazon.com/ses/latest/APIReference-V2/API_SendEmail.html).
@@ -188,7 +195,6 @@ To view your Mailjet API credentials, sign in to Mailjet and open the [API Key M
 ```js
 import "http"
 import "json"
-
 // Import the Secrets package if you store your API keys as secrets.
 // For detail on how to do this, see Step 4 above.
 import "influxdata/influxdb/secrets"
@@ -199,31 +205,38 @@ MAILJET_APIKEY = secrets.get(key: "MAILJET_APIKEY")
 MAILJET_SECRET_APIKEY = secrets.get(key: "MAILJET_SECRET_APIKEY")
 
 numberOfCrits = from(bucket: "_monitoring")
-	|> range(start: -task.every)
-	|> filter(fn: (r) => r.measurement == "statuses" and "r.level" == "crit")
-	|> count()
+    |> range(start: -task.every)
+    |> filter(fn: (r) => r.measurement == "statuses" and "r.level" == "crit")
+    |> count()
 
 numberOfCrits
-	|> map(fn: (r) => (if r._value > 3 then {
-    r with _value: http.post(
-      url: "https://api.mailjet.com/v3.1/send",
-      headers: {
-        "Content-type": "application/json",
-        "Authorization": "Basic ${MAILJET_APIKEY}:${MAILJET_SECRET_APIKEY}"
-      },
-      data: json.encode(v: {
-      	"Messages": [{
-      		"From": {
-      			"Email": "jane.doe@example.com"
-      		},
-      		"To": [{
-      			"Email": "john.doe@example.com"
-      		}],
-      		"Subject": "InfluxDB critical alert",
-      		"TextPart": "There have been ${r._value} critical statuses.",
-      		"HTMLPart": "<h3>${r._value} critical statuses</h3><p>There have been ${r._value} critical statuses."
-      	}]
-      }))} else {r with _value: 0}))
+    |> map(
+        fn: (r) => if r._value > 3 then
+            {r with
+                _value: http.post(
+                    url: "https://api.mailjet.com/v3.1/send",
+                    headers: {
+                        "Content-type": "application/json",
+                        "Authorization": "Basic ${MAILJET_APIKEY}:${MAILJET_SECRET_APIKEY}"
+                    },
+                    data: json.encode(
+                        v: {
+                            "Messages": [
+                                {
+                                    "From": {"Email": "jane.doe@example.com"},
+                                    "To": [{"Email": "john.doe@example.com"}],
+                                    "Subject": "InfluxDB critical alert",
+                                    "TextPart": "There have been ${r._value} critical statuses.",
+                                    "HTMLPart": "<h3>${r._value} critical statuses</h3><p>There have been ${r._value} critical statuses.",
+                                },
+                            ],
+                        },
+                    ),
+                ),
+            }
+        else
+            {r with _value: 0},
+    )
 ```
 
 {{% /tab-content %}}
@@ -241,7 +254,6 @@ To view your Mailgun API keys, sign in to Mailjet and open [Account Security - A
 ```js
 import "http"
 import "json"
-
 // Import the Secrets package if you store your API key as a secret.
 // For detail on how to do this, see Step 4 above.
 import "influxdata/influxdb/secrets"
@@ -251,25 +263,31 @@ import "influxdata/influxdb/secrets"
 MAILGUN_APIKEY = secrets.get(key: "MAILGUN_APIKEY")
 
 numberOfCrits = from(bucket: "_monitoring")
-	|> range(start: -task.every)
-	|> filter(fn: (r) => (r["_measurement"] == "statuses"))
-	|> filter(fn: (r) => (r["_level"] == "crit"))
-	|> count()
+    |> range(start: -task.every)
+    |> filter(fn: (r) => r["_measurement"] == "statuses")
+    |> filter(fn: (r) => r["_level"] == "crit")
+    |> count()
 
 numberOfCrits
-	|> map(fn: (r) =>
-		(if r._value > 1 then {r with _value: http.post(
-      url: "https://api.mailgun.net/v3/YOUR_DOMAIN/messages",
-      headers: {
-        "Content-type": "application/json",
-        "Authorization": "Basic api:${MAILGUN_APIKEY}"
-      },
-      data: json.encode(v: {
-        "from": "Username <mailgun@YOUR_DOMAIN_NAME>",
-        "to": "email@example.com",
-        "subject": "InfluxDB critical alert",
-        "text": "There have been ${r._value} critical statuses."
-      }))} else {r with _value: 0}))
+    |> map(
+        fn: (r) => if r._value > 1 then
+            {r with _value: http.post(
+                url: "https://api.mailgun.net/v3/YOUR_DOMAIN/messages",
+                headers: {
+                    "Content-type": "application/json",
+                    "Authorization": "Basic api:${MAILGUN_APIKEY}"
+                },
+                data: json.encode(v: {
+                        "from": "Username <mailgun@YOUR_DOMAIN_NAME>",
+                        "to": "email@example.com",
+                        "subject": "InfluxDB critical alert",
+                        "text": "There have been ${r._value} critical statuses."
+                    }                
+                )
+            )}
+        else
+            {r with _value: 0},
+    )
 ```
 
 {{% /tab-content %}}
diff --git a/content/influxdb/v2.1/monitor-alert/templates/monitor.md b/content/influxdb/v2.1/monitor-alert/templates/monitor.md
index 95aab24e3..00d120eda 100644
--- a/content/influxdb/v2.1/monitor-alert/templates/monitor.md
+++ b/content/influxdb/v2.1/monitor-alert/templates/monitor.md
@@ -14,6 +14,9 @@ aliases:
 related:
   - /influxdb/v2.1/reference/cli/influx/apply/
   - /influxdb/v2.1/reference/cli/influx/template/
+  - /influxdb/v2.1/reference/internals/metrics/
+  - /flux/v0.x/prometheus/scrape-prometheus/
+  - /influxdb/v2.1/reference/prometheus-metrics/
 ---
 
 Use [InfluxDB Cloud](/influxdb/cloud/), the [InfluxDB Open Source (OSS) Metrics template](https://github.com/influxdata/community-templates/tree/master/influxdb2_oss_metrics),
@@ -28,6 +31,7 @@ Do the following:
 5. [View the Monitoring dashboard](#view-the-monitoring-dashboard)
 6. (Optional) [Alert when metrics stop reporting](#alert-when-metrics-stop-reporting)
 7. (Optional) [Create a notification endpoint and rule](#create-a-notification-endpoint-and-rule)
+8. (Optional) [Write metrics to InfluxDB OSS at regular intervals](#write-metrics-to-influxdb-oss-at-regular-intervals)
 
 ## Review requirements
 
@@ -45,7 +49,7 @@ The InfluxDB OSS Monitoring template includes a Telegraf configuration that send
 InfluxDB OSS metrics to an InfluxDB endpoint and a dashboard that visualizes the metrics.
 
 1.  [Log into your InfluxDB Cloud account](https://cloud2.influxdata.com/).
-2.  Go to **Settings > Templates** in the navigation bar on the left
+2.  Go to **Settings > Templates** in the navigation bar on the left.
 
     {{< nav-icon "Settings" >}}
 
@@ -67,13 +71,14 @@ InfluxDB OSS metrics to an InfluxDB endpoint and a dashboard that visualizes the
 
 ## Set up InfluxDB OSS for monitoring
 
-By default, InfluxDB OSS 2.x has a `/metrics` endpoint available, which exports 
-internal InfluxDB metrics in [Prometheus format](https://prometheus.io/docs/concepts/data_model/).
+InfluxDB OSS 2.x has a `/metrics` endpoint that exports [internal InfluxDB metrics](/{{< latest "influxdb" >}}/reference/internals/metrics/) in [Prometheus exposition format](https://prometheus.io/docs/concepts/data_model/).
+
+[{{< api-endpoint method="GET" endpoint="http://localhost:8086/metrics" >}}](/influxdb/v2.1/api/#operation/GetMetrics)
 
 1. Ensure the `/metrics` endpoint is [enabled](/{{< latest "influxdb" >}}/reference/config-options/#metrics-disabled).
    If you've changed the default settings to disable the `/metrics` endpoint,
    [re-enable these settings](/{{< latest "influxdb" >}}/reference/config-options/#metrics-disabled).
-2. Navigate to the `/metrics` endpoint of your InfluxDB OSS instance to view the InfluxDB OSS system metrics in your browser: 
+2. To preview `/metrics` data, use your browser to navigate to the endpoint.
 
 ## Set up Telegraf
 
@@ -83,7 +88,7 @@ On each InfluxDB OSS instance you want to monitor, do the following:
 
 1. [Install Telegraf](/{{< latest "telegraf" >}}/introduction/installation/).
 2. Set the following environment variables in your Telegraf environment:
-    
+
     - `INFLUX_URL`: Your [InfluxDB Cloud region URL](/influxdb/cloud/reference/regions/)
     - `INFLUX_ORG`: Your InfluxDB Cloud organization name
 
@@ -91,7 +96,7 @@ On each InfluxDB OSS instance you want to monitor, do the following:
 
     {{< nav-icon "load-data" >}}
 
-2. Click **Setup Instructions** under **Scrape InfluxDB OSS Metrics**. 
+2. In the **Telegraf** page, find the **Scrape InfluxDB OSS Metrics** configuration and click **Setup Instructions**.
 3. Complete the Telegraf Setup instructions to start Telegraf using the Scrape InfluxDB OSS Metrics
    Telegraf configuration stored in InfluxDB Cloud.
 
@@ -142,34 +147,38 @@ To alert when data stops flowing from InfluxDB OSS instances to your InfluxDB Cl
 
 ## Create a notification endpoint and rule
 
-To receive a notification message when your deadman check is triggered, create a [notification endpoint](#create-a-notification-endpoint) and [rule](#create-a-notification-rule). 
+To receive a notification message when your deadman check is triggered, create a [notification endpoint](#create-a-notification-endpoint) and [rule](#create-a-notification-rule).
 
-### Create a notification endpoint 
+### Create a notification endpoint
 
-InfluxData supports different endpoints: Slack, PagerDuty, and HTTP. Slack is free for all users, while PagerDuty and HTTP are exclusive to the Usage-Based Plan. 
+InfluxData supports different endpoints: Slack, PagerDuty, and HTTP. Slack is free for all users, while PagerDuty and HTTP are exclusive to the Usage-Based Plan.
 
 #### 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 > Alerts** in the left navigation menu and then click **{{< caps >}}Notification Endpoints{{< /caps >}}**.
 
     {{< nav-icon "alerts" >}}
 
-4.  Click **{{< caps >}}{{< icon "plus" >}} Create{{< /caps >}}**, and enter a name and description for your Slack endpoint. 
-3.  Enter your Slack Webhook under **Incoming Webhook URL** and click **{{< caps >}}Create Notification Endpoint{{< /caps >}}**. 
+4.  Click **{{< caps >}}{{< icon "plus" >}} Create{{< /caps >}}**, and enter a name and description for your Slack endpoint.
+3.  Enter your Slack Webhook under **Incoming Webhook URL** and click **{{< caps >}}Create Notification Endpoint{{< /caps >}}**.
 
-#### Send a notification to PagerDuty or HTTP 
+#### Send a notification to PagerDuty or HTTP
 
 Send a notification to PagerDuty or HTTP endpoints (other webhooks) by [upgrading your InfluxDB Cloud account](/influxdb/cloud/account-management/billing/#upgrade-to-usage-based-plan).
 
-### Create a notification rule 
+### Create a notification rule
 
-[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 > Alerts** in the left navigation menu and then click **{{< caps >}}Notification Rules{{< /caps >}}**.
 
     {{< nav-icon "alerts" >}}
 
 4.  Click **{{< caps >}}{{< icon "plus" >}} Create{{< /caps >}}**, and then provide
-    the required information. 
-3.  Click **{{< caps >}}Create Notification Rule{{< /caps >}}**. 
+    the required information.
+3.  Click **{{< caps >}}Create Notification Rule{{< /caps >}}**.
+
+## Write metrics to InfluxDB OSS at regular intervals
+
+See how to [scrape InfluxDB OSS metrics and write them to InfluxDB at regular intervals](/flux/v0.x/prometheus/scrape-prometheus/#write-prometheus-metrics-to-influxdb-at-regular-intervals).
diff --git a/content/influxdb/v2.1/notebooks/create-notebook.md b/content/influxdb/v2.1/notebooks/create-notebook.md
index 25165cc94..2c53c9d19 100644
--- a/content/influxdb/v2.1/notebooks/create-notebook.md
+++ b/content/influxdb/v2.1/notebooks/create-notebook.md
@@ -38,6 +38,10 @@ To create a new notebook, do the following:
 4. Do the following at the top of the page:
    - Select your local time zone or UTC.
    - Choose a time [range](/{{% latest "flux" %}}/stdlib/universe/range/) for your data.
+   - Select an auto-refresh interval. Click **Enable Auto Refresh**. In the window that appears, configure the following options:
+     - **Until**: Select **Indefinite** to automatically refresh continuously. Select **Custom** to set a time to stop automatically refreshing.
+     - **Inactivity Timeout**: Set how long the user should be inactive for the dashboard to time out and stop automatically refreshing.
+     - **Refresh Interval**: Enter how frequently the dashboard should refresh.
 5. Your notebook should have a **Data Source** cell as the first cell. **Data Source** cells provide data to subsequent cells. The presets (listed in step 2) include either a **Query Builder** or a **Flux Script** as the first cell.
 6. To define your data source query, do one of the following:
    - If your notebook uses a **Query Builder** cell, select your bucket and any additional filters for your query.
diff --git a/content/influxdb/v2.1/notebooks/manage-notebooks.md b/content/influxdb/v2.1/notebooks/manage-notebooks.md
index b2cb6ec91..36a45fb11 100644
--- a/content/influxdb/v2.1/notebooks/manage-notebooks.md
+++ b/content/influxdb/v2.1/notebooks/manage-notebooks.md
@@ -12,6 +12,8 @@ menu:
 Manage your notebooks in the UI:
 
 - [View or update a notebook](#view-or-update-notebooks)
+- {{% cloud-only %}}[Save a notebook version](#save-a-notebook){{% /cloud-only %}}
+- {{% cloud-only %}}[Manage notebook version history](#manage-notebook-version-history){{% /cloud-only %}}
 - {{% cloud-only %}}[Share a notebook](#share-a-notebook){{% /cloud-only %}}
 - {{% cloud-only %}}[Unshare a notebook](#unshare-a-notebook){{% /cloud-only %}}
 - [Delete a notebook](#delete-a-notebook)
@@ -28,6 +30,28 @@ Manage your notebooks in the UI:
 
 {{% cloud-only %}}
 
+## Save a notebook version
+
+1.  In the navigation menu on the left, click **Notebooks**.
+
+    {{< nav-icon "notebooks" >}}
+
+2. Click the notebook to open it.
+3. Click the **{{< icon "..." >}}** icon, then select **Save to version history**.
+
+## Manage notebook version history
+
+1. In the navigation menu on the left, click **Notebooks**.
+
+    {{< nav-icon "notebooks" >}}
+
+2. Click the notebook to open it.
+3. Click the **{{< icon "..." >}}** icon, then select **Version History**.
+4. A timestamped list of all saved versions appears in the right panel.
+  - To preview a previous version, click the version and then click **Run** in the upper left.
+  - To restore a previous version, click the version and then click **Restore This Version** in the upper right. Alternatively, click the **{{< icon "..." >}}** icon next to the version and select **Restore this version**.
+  - To clone a previous version to a new notebook, click the **{{< icon "..." >}}** icon next to the version and select **Clone version to new notebook**.
+
 ## Share a notebook
 
 1.  In the navigation menu on the left, click **Notebooks**.
diff --git a/content/influxdb/v2.1/notebooks/overview.md b/content/influxdb/v2.1/notebooks/overview.md
index 39e31a26a..15a566c28 100644
--- a/content/influxdb/v2.1/notebooks/overview.md
+++ b/content/influxdb/v2.1/notebooks/overview.md
@@ -42,16 +42,16 @@ The following options appear at the top of each notebook.
 
 Select {{< caps >}}Run{{< /caps >}} (or press **Control+Enter**) to display results of each cell and write data to the selected bucket.
 
+### Save to version history
+
+Click the **{{< icon "..." >}}** icon, then select **Save to version history**.
+
+### Version history (appears after first save)
+
+Click the **{{< icon "..." >}}** icon, then select **Version history** to open the version history panel. Each saved version of the notebook appears. For details, see [Manage notebook version history](/influxdb/cloud/notebooks/manage-notebooks/#manage-notebook-version-history/).
+
 {{% /cloud-only %}}
 
-### Save Notebook (appears before first save)
-
-Select {{< caps >}}Save Notebook{{< /caps >}} to save all notebook cells. Once you've saved the notebook, this button disappears and the notebook automatically saves as subsequent changes are made.
-
-{{% note %}}
-Saving the notebook does not save cell results. When you open a saved notebook, click {{< caps >}}**Run**{{< /caps >}} to update cell results.
-{{% /note %}}
-
 ### Local or UTC timezone
 
 Click the timezone drop-down list to select a timezone to use for the notebook. Select either the local time (default) or UTC.
diff --git a/content/influxdb/v2.1/organizations/buckets/create-bucket.md b/content/influxdb/v2.1/organizations/buckets/create-bucket.md
index 85b1173ae..bc765224d 100644
--- a/content/influxdb/v2.1/organizations/buckets/create-bucket.md
+++ b/content/influxdb/v2.1/organizations/buckets/create-bucket.md
@@ -66,6 +66,10 @@ to create a new bucket. A bucket requires the following:
   - days (`d`)
   - weeks (`w`)
 
+  {{% note %}}
+  The minimum retention period is **one hour**.
+  {{% /note %}}
+
 ```sh
 # Syntax
 influx bucket create -n <bucket-name> -o <org-name> -r <retention-period-duration>
diff --git a/content/influxdb/v2.1/organizations/buckets/update-bucket.md b/content/influxdb/v2.1/organizations/buckets/update-bucket.md
index 7839bf8d8..7b1170413 100644
--- a/content/influxdb/v2.1/organizations/buckets/update-bucket.md
+++ b/content/influxdb/v2.1/organizations/buckets/update-bucket.md
@@ -64,7 +64,20 @@ influx bucket update -i 034ad714fdd6f000 -n my-new-bucket
 
 ##### Update a bucket's retention period
 
-Valid retention period duration units are nanoseconds (`ns`), microseconds (`us` or `µs`), milliseconds (`ms`), seconds (`s`), minutes (`m`), hours (`h`), days (`d`), or weeks (`w`).
+Valid retention period duration units:
+
+- nanoseconds (`ns`)
+- microseconds (`us` or `µs`)
+- milliseconds (`ms`)
+- seconds (`s`)
+- minutes (`m`)
+- hours (`h`)
+- days (`d`)
+- weeks (`w`)
+
+{{% note %}}
+The minimum retention period is **one hour**.
+{{% /note %}}
 
 ```sh
 # Syntax
diff --git a/content/influxdb/v2.1/process-data/common-tasks/calculate_weekly_mean.md b/content/influxdb/v2.1/process-data/common-tasks/calculate_weekly_mean.md
index 0ca0a1aef..fe17d8afb 100644
--- a/content/influxdb/v2.1/process-data/common-tasks/calculate_weekly_mean.md
+++ b/content/influxdb/v2.1/process-data/common-tasks/calculate_weekly_mean.md
@@ -23,16 +23,13 @@ The following query:
   - Sends the weekly mean to a new bucket (`weekly_means`)
 
 ```js
-option task = {
-  name: "weekly-means",
-  every: 1w,
-}
+option task = {name: "weekly-means", every: 1w}
 
 from(bucket: "noaa")
-  |> filter(fn: (r) => r._measurement == "average_temperature")
-  |> range(start: 2019-09-01T11:24:00Z)
-  |> aggregateWindow(every:  1w, fn: mean)
-  |> to(bucket: "weekly_means")
+    |> filter(fn: (r) => r._measurement == "average_temperature")
+    |> range(start: 2019-09-01T11:24:00Z)
+    |> aggregateWindow(every: 1w, fn: mean)
+    |> to(bucket: "weekly_means")
 ```
 ### Example results
 
diff --git a/content/influxdb/v2.1/process-data/common-tasks/convert_results_to_json.md b/content/influxdb/v2.1/process-data/common-tasks/convert_results_to_json.md
index 3dc65ab08..9b0d8c6ec 100644
--- a/content/influxdb/v2.1/process-data/common-tasks/convert_results_to_json.md
+++ b/content/influxdb/v2.1/process-data/common-tasks/convert_results_to_json.md
@@ -29,15 +29,16 @@ import "http"
 import "json"
 
 from(bucket: "noaa")
-  |> filter(fn: (r) => r._measurement == "average_temperature")
-  |> mean()
-  |> map(fn: (r) => ({ r with
-    jsonStr: string(v: json.encode(v: {"location":r.location,"mean":r._value}))}))
-  |> map(fn: (r) => ({r with
-    status_code: http.post(
-      url: "http://somehost.com/",
-      headers: {x:"a", y:"b"},
-      data: bytes(v: r.jsonStr)
+    |> filter(fn: (r) => r._measurement == "average_temperature")
+    |> mean()
+    |> map(fn: (r) => ({r with jsonStr: string(v: json.encode(v: {"location": r.location, "mean": r._value}))}))
+    |> map(
+        fn: (r) => ({
+            r with
+            status_code: http.post(url: "http://somehost.com/",
+                headers: {x: "a", y: "b"},
+                data: bytes(v: r.jsonStr),
+            ),
+        })
     )
-  }))
 ```
diff --git a/content/influxdb/v2.1/process-data/common-tasks/downsample-data.md b/content/influxdb/v2.1/process-data/common-tasks/downsample-data.md
index f27c5f795..dc131f80c 100644
--- a/content/influxdb/v2.1/process-data/common-tasks/downsample-data.md
+++ b/content/influxdb/v2.1/process-data/common-tasks/downsample-data.md
@@ -48,21 +48,18 @@ The example task script below is a very basic form of data downsampling that doe
 
 ```js
 // Task Options
-option task = {
-  name: "cq-mem-data-1w",
-  every: 1w,
-}
+option task = {name: "cq-mem-data-1w", every: 1w}
 
 // Defines a data source
 data = from(bucket: "system-data")
-  |> range(start: -duration(v: int(v: task.every) * 2))
-  |> filter(fn: (r) => r._measurement == "mem")
+    |> range(start: -duration(v: int(v: task.every) * 2))
+    |> filter(fn: (r) => r._measurement == "mem")
 
 data
-  // Windows and aggregates the data in to 1h averages
-  |> aggregateWindow(fn: mean, every: 1h)
-  // Stores the aggregated data in a new bucket
-  |> to(bucket: "system-data-downsampled", org: "my-org")
+    // Windows and aggregates the data in to 1h averages
+    |> aggregateWindow(fn: mean, every: 1h)
+    // Stores the aggregated data in a new bucket
+    |> to(bucket: "system-data-downsampled", org: "my-org")
 ```
 
 Again, this is a very basic example, but it should provide you with a foundation
diff --git a/content/influxdb/v2.1/process-data/get-started.md b/content/influxdb/v2.1/process-data/get-started.md
index eedbafde6..a326e9d6a 100644
--- a/content/influxdb/v2.1/process-data/get-started.md
+++ b/content/influxdb/v2.1/process-data/get-started.md
@@ -18,15 +18,16 @@ related:
   - /resources/videos/influxdb-tasks/
 ---
 
-An **InfluxDB task** is a scheduled Flux script that takes a stream of input data, modifies or analyzes
-it in some way, then stores the modified data in a new bucket or performs other actions.
+An **InfluxDB task** is a scheduled Flux script that takes a stream of input data,
+modifies or analyzes it in some way, then writes the modified data back to InfluxDB
+or performs other actions.
 
 This article walks through writing a basic InfluxDB task that downsamples
 data and stores it in a new bucket.
 
 ## Components of a task
 
-Every InfluxDB task needs the following four components.
+Every InfluxDB task needs the following components.
 Their form and order can vary, but they are all essential parts of a task.
 
 - [Task options](#define-task-options)
@@ -42,42 +43,39 @@ Task options define specific information about the task.
 The example below illustrates how task options are defined in your Flux script:
 
 ```js
-option task = {
-    name: "cqinterval15m",
-    every: 1h,
-    offset: 0m,
-    concurrency: 1,
-}
+option task = {name: "downsample_5m_precision", every: 1h, offset: 0m}
 ```
 
-_See [Task configuration options](/influxdb/v2.1/process-data/task-options) for detailed information
+_See [Task configuration options](/influxdb/v2.2/process-data/task-options) for detailed information
 about each option._
 
 {{% note %}}
-When creating a task in the InfluxDB user interface (UI), task options are defined in form fields.
+The InfluxDB UI provides a form for defining task options.
 {{% /note %}}
 
 ## Define a data source
 
-Define a data source using Flux's [`from()` function](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/from/)
-or any other [Flux input functions](/{{< latest "flux" >}}/function-types/#inputs).
-
-For convenience, consider creating a variable that includes the sourced data with
-the required time range and any relevant filters.
+1.  Use [`from()`](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/from/)
+    to query data from InfluxDB {{% cloud-only %}}Cloud{{% /cloud-only %}}.
+    Use
+    other [Flux input functions](/{{< latest "flux" >}}/function-types/#inputs)
+    to retrieve data from other sources.
+2.  Use [`range()`](/{{< latest "flux" >}}/stdlib/universe/range/) to define the time
+    range to return data from.
+3.  Use [`filter()`](/{{< latest "flux" >}}/stdlib/universe/filter/) to filter
+    data based on column values.
 
 ```js
 data = from(bucket: "example-bucket")
-  |> range(start: -task.every)
-  |> filter(fn: (r) =>
-    r._measurement == "mem" and
-    r.host == "myHost"
-  )
+    |> range(start: -task.every)
+    |> filter(fn: (r) => r._measurement == "mem" and r.host == "myHost")
 ```
 
 {{% note %}}
-#### Using task options in your Flux script
 
-Task options are passed as part of a `task` option record and can be referenced in your Flux script.
+#### Use task options in your Flux script
+
+Task options are defined in a `task` option record and can be referenced in your Flux script.
 In the example above, the time range is defined as `-task.every`.
 
 `task.every` is dot notation that references the `every` property of the `task` option record.
@@ -88,48 +86,58 @@ Using task options to define values in your Flux script can make reusing your ta
 
 ## Process or transform your data
 
-The purpose of tasks is to process or transform data in some way.
-What exactly happens and what form the output data takes is up to you and your
-specific use case.
+Tasks automatically process or transform data in some way
+at regular intervals.
+Data processing can include operations such as downsampling data, detecting
+anomalies, sending notifications, and more.
 
 {{% note %}}
-#### Account for latent data with an offset
 
-To account for latent data (like data streaming from your edge devices), use an offset in your task. For example, if you set a task interval on the hour with the options `every: 1h` and `offset: 5m`, a task executes 5 minutes after the task interval but the query [`now()`](/{{< latest "flux" >}}/stdlib/universe/now/) time is on the exact hour.
+#### Use offset to account for latent data
 
+Use the `offset` task option to account for potentially latent data (like data from edge devices).
+A task that runs at one hour intervals (`every: 1h`) with an offset of five minutes (`offset: 5m`)
+executes 5 minutes after the hour, but queries data from the original one hour interval.
 {{% /note %}}
 
-The example below illustrates a task that downsamples data by calculating the average of set intervals.
-It uses the `data` variable defined [above](#define-a-data-source) as the data source.
-It then windows the data into 5 minute intervals and calculates the average of each
-window using the [`aggregateWindow()` function](/{{< latest "flux" >}}/stdlib/universe/aggregatewindow/).
+The task example below downsamples data by calculating the average of set intervals.
+It uses [`aggregateWindow()`](/{{< latest "flux" >}}/stdlib/universe/aggregatewindow/)
+to group points into 5 minute windows and calculate the average of each
+window with [`mean()`](/{{< latest "flux" >}}/stdlib/universe/mean/).
 
 ```js
-data
-  |> aggregateWindow(
-    every: 5m,
-    fn: mean
-  )
+option task = {name: "downsample_5m_precision", every: 1h, offset: 5m}
+
+from(bucket: "example-bucket")
+    |> range(start: -task.every)
+    |> filter(fn: (r) => r._measurement == "mem" and r.host == "myHost")
+    |> aggregateWindow(every: 5m, fn: mean)
 ```
 
-_See [Common tasks](/influxdb/v2.1/process-data/common-tasks) for examples of tasks commonly used with InfluxDB._
+_See [Common tasks](/influxdb/v2.2/process-data/common-tasks) for examples of tasks commonly used with InfluxDB._
 
 ## Define a destination
 
-In the vast majority of task use cases, once data is transformed, it needs to be sent and stored somewhere.
-This could be a separate bucket or another measurement.
+In most cases, you'll want to send and store data after the task has transformed it.
+The destination could be a separate InfluxDB measurement or bucket.
 
-The example below uses Flux's [`to()` function](/{{< latest "flux" >}}/stdlib/universe/to)
-to send the transformed data to another bucket:
+The example below uses [`to()`](/{{< latest "flux" >}}/stdlib/universe/to)
+to write the transformed data back to another InfluxDB bucket:
 
 ```js
 // ...
-|> to(bucket: "example-downsampled", org: "my-org")
+    |> to(bucket: "example-downsampled", org: "my-org")
 ```
 
-{{% note %}}
-In order to write data into InfluxDB, you must have `_time`, `_measurement`, `_field`, and `_value` columns.
-{{% /note %}}
+To write data into InfluxDB, `to()` requires the following columns:
+
+- `_time`
+- `_measurement`
+- `_field`
+- `_value`
+
+You can also write data to other destinations using
+[Flux output functions](/{{< latest "flux" >}}/function-types/#outputs).
 
 ## Full example task script
 
@@ -137,33 +145,18 @@ Below is a task script that combines all of the components described above:
 
 ```js
 // Task options
-option task = {
-    name: "cqinterval15m",
-    every: 1h,
-    offset: 0m,
-    concurrency: 1,
-}
+option task = {name: "downsample_5m_precision", every: 1h, offset: 0m}
 
 // Data source
-data = from(bucket: "example-bucket")
-  |> range(start: -task.every)
-  |> filter(fn: (r) =>
-    r._measurement == "mem" and
-    r.host == "myHost"
-  )
-
-data
-  // Data transformation
-  |> aggregateWindow(
-    every: 5m,
-    fn: mean
-  )
-  // Data destination
-  |> to(bucket: "example-downsampled")
-
+from(bucket: "example-bucket")
+    |> range(start: -task.every)
+    |> filter(fn: (r) => r._measurement == "mem" and r.host == "myHost")
+    // Data processing
+    |> aggregateWindow(every: 5m, fn: mean)
+    // Data destination
+    |> to(bucket: "example-downsampled")
 ```
 
 To learn more about InfluxDB tasks and how they work, watch the following video:
 
 {{< youtube zgCmdtZaH9M >}}
-
diff --git a/content/influxdb/v2.1/process-data/task-options.md b/content/influxdb/v2.1/process-data/task-options.md
index dc8278292..71dc6180a 100644
--- a/content/influxdb/v2.1/process-data/task-options.md
+++ b/content/influxdb/v2.1/process-data/task-options.md
@@ -33,8 +33,8 @@ _**Data type:** String_
 
 ```js
 option task = {
-  name: "taskName",
-  // ...
+    name: "taskName",
+    // ...
 }
 ```
 
@@ -46,8 +46,8 @@ _**Data type:** Duration_
 
 ```js
 option task = {
-  // ...
-  every: 1h,
+    // ...
+    every: 1h,
 }
 ```
 
@@ -70,8 +70,8 @@ _**Data type:** String_
 
 ```js
 option task = {
-  // ...
-  cron: "0 * * * *",
+    // ...
+    cron: "0 * * * *",
 }
 ```
 
@@ -87,8 +87,8 @@ _**Data type:** Duration_
 
 ```js
 option task = {
-  // ...
-  offset: 10m,
+    // ...
+    offset: 10m,
 }
 ```
 
@@ -101,7 +101,7 @@ _**Data type:** Integer_
 
 ```js
 option task = {
-  // ...
-  concurrency: 2,
+    // ...
+    concurrency: 2,
 }
 ```
diff --git a/content/influxdb/v2.1/query-data/common-queries/compare-values.md b/content/influxdb/v2.1/query-data/common-queries/compare-values.md
index 1aa5bf6ac..c424791d6 100644
--- a/content/influxdb/v2.1/query-data/common-queries/compare-values.md
+++ b/content/influxdb/v2.1/query-data/common-queries/compare-values.md
@@ -19,26 +19,26 @@ This example compares the value from the latest point to an average value stored
 
 The following query:
 
-  - Uses [`range()`](/{{< latest "flux" >}}/stdlib/universe/range/) to define a time range.
-  - Gets the last value in the `means` bucket and compares it to the last value in the `noaa` bucket using [`last()`](/{{< latest "flux" >}}/stdlib/universe/last/).
-  - Uses [`join()`](/{{< latest "flux" >}}/stdlib/universe/join/) to combine the results
-  - Uses [`map()`](/{{< latest "flux" >}}/stdlib/universe/map/) to calculate the differences
+- Uses [`range()`](/{{< latest "flux" >}}/stdlib/universe/range/) to define a time range.
+- Gets the last value in the `means` bucket and compares it to the last value in the `noaa` bucket using [`last()`](/{{< latest "flux" >}}/stdlib/universe/last/).
+- Uses [`join()`](/{{< latest "flux" >}}/stdlib/universe/join/) to combine the results
+- Uses [`map()`](/{{< latest "flux" >}}/stdlib/universe/map/) to calculate the differences
 
-  ```js
-  means = from(bucket: "weekly_means")
+```js
+means = from(bucket: "weekly_means")
     |> range(start: 2019-09-01T00:00:00Z)
     |> last()
     |> keep(columns: ["_value", "location"])
 
-  latest = from(bucket: "noaa")
+latest = from(bucket: "noaa")
     |> range(start: 2019-09-01T00:00:00Z)
     |> filter(fn: (r) => r._measurement == "average_temperature")
     |> last()
     |> keep(columns: ["_value", "location"])
 
-  join(tables: {mean: means, reading: latest}, on: ["location"])
+join(tables: {mean: means, reading: latest}, on: ["location"])
     |> map(fn: (r) => ({r with deviation: r._value_reading - r._value_mean}))
-  ```
+```
 
 ### Example results
 
diff --git a/content/influxdb/v2.1/query-data/common-queries/iot-common-queries.md b/content/influxdb/v2.1/query-data/common-queries/iot-common-queries.md
index e85ce7815..2dc8e82e9 100644
--- a/content/influxdb/v2.1/query-data/common-queries/iot-common-queries.md
+++ b/content/influxdb/v2.1/query-data/common-queries/iot-common-queries.md
@@ -38,19 +38,22 @@ To visualize the time in state, see the [Mosaic visualization](#mosaic-visualiza
 
 ```js
 import "contrib/tomhollingworth/events"
- 
+
 from(bucket: "machine")
-  |> range(start: 2021-08-01T00:00:00Z, stop: 2021-08-02T00:30:00Z)
-  |> filter(fn: (r) => r["_measurement"] == "machinery")
-  |> filter(fn: (r) => r["_field"] == "state")
-  |> events.duration(unit: 1h, columnName: "duration",)
-  |> group(columns: ["_value", "_start", "_stop", "station_id"])
-  |> sum(column: "duration")
-  |> pivot(rowKey:["_stop"], columnKey: ["_value"], valueColumn: "duration")
-  |> map(fn: (r) => {
-    totalTime = float(v: r.NOK + r.OK)
-    return {r with NOK: float(v: r.NOK) / totalTime * 100.0, OK: float(v: r.OK) / totalTime * 100.0}
-  })
+    |> range(start: 2021-08-01T00:00:00Z, stop: 2021-08-02T00:30:00Z)
+    |> filter(fn: (r) => r["_measurement"] == "machinery")
+    |> filter(fn: (r) => r["_field"] == "state")
+    |> events.duration(unit: 1h, columnName: "duration")
+    |> group(columns: ["_value", "_start", "_stop", "station_id"])
+    |> sum(column: "duration")
+    |> pivot(rowKey: ["_stop"], columnKey: ["_value"], valueColumn: "duration")
+    |> map(
+        fn: (r) => {
+            totalTime = float(v: r.NOK + r.OK)
+    
+            return {r with NOK: float(v: r.NOK) / totalTime * 100.0, OK: float(v: r.OK) / totalTime * 100.0}
+        },
+    )
 ```
 
 The query above focuses on a specific time range of state changes reported in the production line.
@@ -98,10 +101,10 @@ The [mosaic visualization](/influxdb/v2.1/visualize-data/visualization-types/mos
 
 ```js
 from(bucket: "machine")
-  |> range(start: 2021-08-01T00:00:00Z, stop: 2021-08-02T00:30:00Z)
-  |> filter(fn: (r) => r._measurement == "machinery")
-  |> filter(fn: (r) => r._field == "state")
-  |> aggregateWindow(every: v.windowPeriod, fn: last, createEmpty: false)
+    |> range(start: 2021-08-01T00:00:00Z, stop: 2021-08-02T00:30:00Z)
+    |> filter(fn: (r) => r._measurement == "machinery")
+    |> filter(fn: (r) => r._field == "state")
+    |> aggregateWindow(every: v.windowPeriod, fn: last, createEmpty: false)
 ```
 
 When visualizing data, it is possible to have more data points than available pixels. To divide data into time windows that span a single pixel, use `aggregateWindow` with the `every` parameter set to `v.windowPeriod`.
@@ -117,11 +120,9 @@ The example below queries the `oil_temp` field in the `machinery` measurement. T
 
 ```js
 from(bucket: "machine")
-  |> range(start: 2021-08-01T00:00:00Z, stop: 2021-08-01T00:00:30Z)
-  |> filter(fn: (r) =>
-    r._measurement == "machinery" and r._field == "oil_temp"
-  )
-  |> timeWeightedAvg(unit: 5s)
+    |> range(start: 2021-08-01T00:00:00Z, stop: 2021-08-01T00:00:30Z)
+    |> filter(fn: (r) => r._measurement == "machinery" and r._field == "oil_temp")
+    |> timeWeightedAvg(unit: 5s)
 ```
 
 ##### Output data
@@ -146,12 +147,9 @@ batchStart = 2021-08-01T00:00:00Z
 batchStop = 2021-08-01T00:00:20Z
 
 from(bucket: "machine")
-  |> range(start: batchStart, stop: batchStop)
-  |> filter(fn: (r) =>
-    r._measurement == "machinery" and
-    r._field == "oil_temp"
-  )
-  |> mean()
+    |> range(start: batchStart, stop: batchStop)
+    |> filter(fn: (r) => r._measurement == "machinery" and r._field == "oil_temp")
+    |> mean()
 ```
 
 ##### Output
@@ -181,13 +179,13 @@ To determine a state by comparing existing fields:
 import "math"
 
 from(bucket: "machine")
-  |> range(start: 2021-08-01T00:00:00Z, stop: 2021-08-02T00:00:00Z)
-  |> filter(fn: (r) => r["_measurement"] == "machinery")
-  |> filter(fn: (r) => r["_field"] == "pressure" or r["_field"] == "pressure_target")
-  |> aggregateWindow(every: 12h, fn: mean)
-  |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
-  |> map(fn: (r) => ({ r with pressureDiff: r.pressure - r.pressure_target }))
-  |> map(fn: (r) => ({ r with needsMaintenance: if math.abs(x: r.pressureDiff) >= 15.0 then true else false }))
+    |> range(start: 2021-08-01T00:00:00Z, stop: 2021-08-02T00:00:00Z)
+    |> filter(fn: (r) => r["_measurement"] == "machinery")
+    |> filter(fn: (r) => r["_field"] == "pressure" or r["_field"] == "pressure_target")
+    |> aggregateWindow(every: 12h, fn: mean)
+    |> pivot(rowKey: ["_time"], columnKey: ["_field"], valueColumn: "_value")
+    |> map(fn: (r) => ({r with pressureDiff: r.pressure - r.pressure_target}))
+    |> map(fn: (r) => ({r with needsMaintenance: if math.abs(x: r.pressureDiff) >= 15.0 then true else false}))
 ```
 
 ##### Output
diff --git a/content/influxdb/v2.1/query-data/common-queries/multiple-fields-in-calculations.md b/content/influxdb/v2.1/query-data/common-queries/multiple-fields-in-calculations.md
index 8e676ebda..ad6bb348b 100644
--- a/content/influxdb/v2.1/query-data/common-queries/multiple-fields-in-calculations.md
+++ b/content/influxdb/v2.1/query-data/common-queries/multiple-fields-in-calculations.md
@@ -26,8 +26,8 @@ The following example queries two fields, `A` and `B`:
 
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> filter(fn: (r) => r._field == "A" or r._field == "B")
+    |> range(start: -1m)
+    |> filter(fn: (r) => r._field == "A" or r._field == "B")
 ```
 
 This query returns one or more tables for each field. For example:
@@ -63,11 +63,7 @@ If timestamps are irregular or do not align perfectly, see
 
 ```js
 // ...
-  |> pivot(
-    rowKey:["_time"],
-    columnKey: ["_field"],
-    valueColumn: "_value"
-  )
+    |> pivot(rowKey: ["_time"], columnKey: ["_field"], valueColumn: "_value")
 ```
 
 Using the queried data [above](#filter-by-fields), this `pivot()` function returns:
@@ -87,8 +83,8 @@ The following example uses values in the `A` and `B` columns to calculate a new
 
 ```js
 // ...
-  |> map(fn: (r) => ({ r with _value: r.A * r.B }))
-```
+    |> map(fn: (r) => ({ r with _value: r.A * r.B }))
+  ```
 
 Using the pivoted data above, this `map()` function returns:
 
@@ -103,8 +99,8 @@ Using the pivoted data above, this `map()` function returns:
 
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> filter(fn: (r) => r._field == "A" or r._field == "B")
-  |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
-  |> map(fn: (r) => ({ r with _value: r.A * r.B }))
+    |> range(start: -1m)
+    |> filter(fn: (r) => r._field == "A" or r._field == "B")
+    |> pivot(rowKey: ["_time"], columnKey: ["_field"], valueColumn: "_value")
+    |> map(fn: (r) => ({r with _value: r.A * r.B}))
 ```
diff --git a/content/influxdb/v2.1/query-data/common-queries/operate-on-columns.md b/content/influxdb/v2.1/query-data/common-queries/operate-on-columns.md
index 9c24c1745..520048eca 100644
--- a/content/influxdb/v2.1/query-data/common-queries/operate-on-columns.md
+++ b/content/influxdb/v2.1/query-data/common-queries/operate-on-columns.md
@@ -38,10 +38,10 @@ This query:
 
 ```js
 from(bucket: "noaa")
-  |> range(start: -30d)
-  |> group()
-  |> keep(columns: ["location"])
-  |> unique(column: "location")
+    |> range(start: -30d)
+    |> group()
+    |> keep(columns: ["location"])
+    |> unique(column: "location")
 ```
 
 #### Example results
@@ -59,9 +59,9 @@ This query:
 
 ```js
 from(bucket: "noaa")
-  |> group()
-  |> unique(column: "location")
-  |> count(column: "location")
+    |> group()
+    |> unique(column: "location")
+    |> count(column: "location")
 ```
 
 #### Example results
@@ -83,9 +83,9 @@ The following query:
 ```js
 
 from(bucket: "noaa")
-  |> filter(fn: (r) => r._measurement == "average_temperature")
-  |> range(start: -30d)
-  |> map(fn: (r) => ({r with _value: (float(v: r._value) - 32.0) * 5.0 / 9.0} ))
+    |> filter(fn: (r) => r._measurement == "average_temperature")
+    |> range(start: -30d)
+    |> map(fn: (r) => ({r with _value: (float(v: r._value) - 32.0) * 5.0 / 9.0} ))
 ```
 
 | _field  | _measurement        | _start               | _stop                | _time                | location     | _value             |
@@ -115,12 +115,9 @@ The following query:
 
 ```js
 from(bucket: "noaa")
-  |> filter(fn: (r) => r._measurement == "average_temperature")
-  |> range(start: -30d)
-  |> map(fn: (r) => ({r with
-      celsius: ((r._value - 32.0) * 5.0 / 9.0)
-    })
-  )
+    |> filter(fn: (r) => r._measurement == "average_temperature")
+    |> range(start: -30d)
+    |> map(fn: (r) => ({r with celsius: (r._value - 32.0) * 5.0 / 9.0}))
 ```
 
 #### Example results
diff --git a/content/influxdb/v2.1/query-data/execute-queries/influx-api.md b/content/influxdb/v2.1/query-data/execute-queries/influx-api.md
index 50338e902..43aeb1184 100644
--- a/content/influxdb/v2.1/query-data/execute-queries/influx-api.md
+++ b/content/influxdb/v2.1/query-data/execute-queries/influx-api.md
@@ -43,8 +43,8 @@ Below is an example `curl` request that sends a Flux query to InfluxDB {{< curre
 {{% code-tab-content %}}
 ```bash
 curl --request POST \
-  http://localhost:8086/api/v2/query?org=my-org  \
-  --header 'Authorization: Token YOURAUTHTOKEN' \
+  http://localhost:8086/api/v2/query?orgID=INFLUX_ORG_ID  \
+  --header 'Authorization: Token INFLUX_TOKEN' \
   --header 'Accept: application/csv' \
   --header 'Content-type: application/vnd.flux' \
   --data 'from(bucket:"example-bucket")
@@ -57,8 +57,8 @@ curl --request POST \
 {{% code-tab-content %}}
 ```bash
 curl --request POST \
-  http://localhost:8086/api/v2/query?org=my-org \
-  --header 'Authorization: Token YOURAUTHTOKEN' \
+  http://localhost:8086/api/v2/query?orgID=INFLUX_ORG_ID \
+  --header 'Authorization: Token INFLUX_TOKEN' \
   --header 'Accept: application/csv' \
   --header 'Content-type: application/vnd.flux' \
   --header 'Accept-Encoding: gzip' \
@@ -82,8 +82,8 @@ Below is an example `curl` request that sends an InfluxQL query to InfluxDB {{<
 
 {{% code-tab-content %}}
 ```bash
-curl --request -G http://localhost:8086/query?org=my-org?database=MyDB&retention_policy=MyRP \
-  --header 'Authorization: Token YOURAUTHTOKEN' \
+curl --request -G http://localhost:8086/query?orgID=INFLUX_ORG_ID&database=MyDB&retention_policy=MyRP \
+  --header 'Authorization: Token INFLUX_TOKEN' \
   --header 'Accept: application/csv' \
   --header 'Content-type: application/json' \
   --data-urlencode "q=SELECT used_percent FROM example-db.example-rp.example-measurement WHERE host=host1"
@@ -92,8 +92,8 @@ curl --request -G http://localhost:8086/query?org=my-org?database=MyDB&retention
 
 {{% code-tab-content %}}
 ```bash
-curl --request -G http://localhost:8086/query?org=my-org?database=MyDB&retention_policy=MyRP \
-  --header 'Authorization: Token YOURAUTHTOKEN' \
+curl --request -G http://localhost:8086/query?orgID=INFLUX_ORG_ID&database=MyDB&retention_policy=MyRP \
+  --header 'Authorization: Token INFLUX_TOKEN' \
   --header 'Accept: application/csv' \
   --header 'Content-type: application/json' \
   --header 'Accept-Encoding: gzip' \
diff --git a/content/influxdb/v2.1/query-data/execute-queries/influx-query.md b/content/influxdb/v2.1/query-data/execute-queries/influx-query.md
index c3b1da39b..ae3817e89 100644
--- a/content/influxdb/v2.1/query-data/execute-queries/influx-query.md
+++ b/content/influxdb/v2.1/query-data/execute-queries/influx-query.md
@@ -36,6 +36,6 @@ drop columns such as `_start` and `_stop` to optimize the download file size.
 
 ```js
 // ...
-  |> drop(columns: ["_start", "_stop"])
+    |> drop(columns: ["_start", "_stop"])
 ```
 {{% /note %}}
diff --git a/content/influxdb/v2.1/query-data/flux/_index.md b/content/influxdb/v2.1/query-data/flux/_index.md
index c640d26f5..9c6655e6f 100644
--- a/content/influxdb/v2.1/query-data/flux/_index.md
+++ b/content/influxdb/v2.1/query-data/flux/_index.md
@@ -21,11 +21,8 @@ which represents a basic query that filters data by measurement and field.
 
 ```js
 data = from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "example-measurement" and
-    r._field == "example-field"
-  )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement" and r._field == "example-field")
 ```
 {{% /note %}}
 
diff --git a/content/influxdb/v2.1/query-data/flux/calculate-percentages.md b/content/influxdb/v2.1/query-data/flux/calculate-percentages.md
index ed380beea..cd77265d4 100644
--- a/content/influxdb/v2.1/query-data/flux/calculate-percentages.md
+++ b/content/influxdb/v2.1/query-data/flux/calculate-percentages.md
@@ -41,10 +41,10 @@ _See [Pivot vs join](/influxdb/v2.1/query-data/flux/mathematic-operations/#pivot
 
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "m1" and r._field =~ /field[1-2]/ )
-  |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
-  |> map(fn: (r) => ({ r with _value: r.field1 / r.field2 * 100.0 }))
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "m1" and r._field =~ /field[1-2]/ )
+    |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
+    |> map(fn: (r) => ({ r with _value: r.field1 / r.field2 * 100.0 }))
 ```
 
 ## GPU monitoring example
@@ -59,8 +59,8 @@ Data includes the following:
 ### Query mem_used and mem_total fields
 ```js
 from(bucket: "gpu-monitor")
-  |> range(start: 2020-01-01T00:00:00Z)
-  |> filter(fn: (r) => r._measurement == "gpu" and r._field =~ /mem_/)
+    |> range(start: 2020-01-01T00:00:00Z)
+    |> filter(fn: (r) => r._measurement == "gpu" and r._field =~ /mem_/)
 ```
 
 ###### Returns the following stream of tables:
@@ -91,7 +91,7 @@ Output includes `mem_used` and `mem_total` columns with values for each correspo
 
 ```js
 // ...
-  |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
+    |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
 ```
 
 ###### Returns the following:
@@ -117,12 +117,14 @@ below casts integer field values to floats and multiplies by a float value (`100
 
 ```js
 // ...
-  |> map(fn: (r) => ({
-    _time: r._time,
-    _measurement: r._measurement,
-    _field: "mem_used_percent",
-    _value: float(v: r.mem_used) / float(v: r.mem_total) * 100.0
-  }))
+    |> map(
+        fn: (r) => ({
+            _time: r._time,
+            _measurement: r._measurement,
+            _field: "mem_used_percent",
+            _value: float(v: r.mem_used) / float(v: r.mem_total) * 100.0
+        })
+    )
 ```
 ##### Query results:
 
@@ -138,15 +140,17 @@ below casts integer field values to floats and multiplies by a float value (`100
 ### Full query
 ```js
 from(bucket: "gpu-monitor")
-  |> range(start: 2020-01-01T00:00:00Z)
-  |> filter(fn: (r) => r._measurement == "gpu" and r._field =~ /mem_/ )
-  |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
-  |> map(fn: (r) => ({
-    _time: r._time,
-    _measurement: r._measurement,
-    _field: "mem_used_percent",
-    _value: float(v: r.mem_used) / float(v: r.mem_total) * 100.0
-  }))
+    |> range(start: 2020-01-01T00:00:00Z)
+    |> filter(fn: (r) => r._measurement == "gpu" and r._field =~ /mem_/)
+    |> pivot(rowKey: ["_time"], columnKey: ["_field"], valueColumn: "_value")
+    |> map(
+        fn: (r) => ({
+            _time: r._time,
+            _measurement: r._measurement,
+            _field: "mem_used_percent",
+            _value: float(v: r.mem_used) / float(v: r.mem_total) * 100.0
+        })
+    )
 ```
 
 ## Examples
@@ -154,17 +158,11 @@ from(bucket: "gpu-monitor")
 #### Calculate percentages using multiple fields
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "example-measurement")
-  |> filter(fn: (r) =>
-    r._field == "used_system" or
-    r._field == "used_user" or
-    r._field == "total"
-  )
-  |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
-  |> map(fn: (r) => ({ r with
-    _value: float(v: r.used_system + r.used_user) / float(v: r.total) * 100.0
-  }))
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> filter(fn: (r) => r._field == "used_system" or r._field == "used_user" or r._field == "total")
+    |> pivot(rowKey: ["_time"], columnKey: ["_field"], valueColumn: "_value")
+    |> map(fn: (r) => ({r with _value: float(v: r.used_system + r.used_user) / float(v: r.total) * 100.0}))
 ```
 
 #### Calculate percentages using multiple measurements
@@ -178,14 +176,11 @@ from(bucket: "example-bucket")
 <!-- -->
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    (r._measurement == "m1" or r._measurement == "m2") and
-    (r._field == "field1" or r._field == "field2")    
-  )
-  |> group()
-  |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
-  |> map(fn: (r) => ({ r with  _value: r.field1 / r.field2 * 100.0 }))
+    |> range(start: -1h)
+    |> filter(fn: (r) => (r._measurement == "m1" or r._measurement == "m2") and (r._field == "field1" or r._field == "field2"))
+    |> group()
+    |> pivot(rowKey: ["_time"], columnKey: ["_field"], valueColumn: "_value")
+    |> map(fn: (r) => ({r with _value: r.field1 / r.field2 * 100.0}))
 ```
 
 #### Calculate percentages using multiple data sources
@@ -198,18 +193,15 @@ pgPass = secrets.get(key: "POSTGRES_PASSWORD")
 pgHost = secrets.get(key: "POSTGRES_HOST")
 
 t1 = sql.from(
-  driverName: "postgres",
-  dataSourceName: "postgresql://${pgUser}:${pgPass}@${pgHost}",
-  query:"SELECT id, name, available FROM example_table"
+    driverName: "postgres",
+    dataSourceName: "postgresql://${pgUser}:${pgPass}@${pgHost}",
+    query: "SELECT id, name, available FROM example_table",
 )
 
 t2 = from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "example-measurement" and
-    r._field == "example-field"
-  )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement" and r._field == "example-field")
 
 join(tables: {t1: t1, t2: t2}, on: ["id"])
-  |> map(fn: (r) => ({ r with _value: r._value_t2 / r.available_t1 * 100.0 }))
+    |> map(fn: (r) => ({r with _value: r._value_t2 / r.available_t1 * 100.0}))
 ```
diff --git a/content/influxdb/v2.1/query-data/flux/conditional-logic.md b/content/influxdb/v2.1/query-data/flux/conditional-logic.md
index 691cdd373..befc72dc8 100644
--- a/content/influxdb/v2.1/query-data/flux/conditional-logic.md
+++ b/content/influxdb/v2.1/query-data/flux/conditional-logic.md
@@ -55,10 +55,14 @@ Flux evaluates statements in order and stops evaluating once a condition matches
 For example, given the following statement:
 
 ```js
-if r._value > 95.0000001 and r._value <= 100.0 then "critical"
-else if r._value > 85.0000001 and r._value <= 95.0 then "warning"
-else if r._value > 70.0000001 and r._value <= 85.0 then "high"
-else "normal"
+if r._value > 95.0000001 and r._value <= 100.0 then
+    "critical"
+else if r._value > 85.0000001 and r._value <= 95.0 then
+    "warning"
+else if r._value > 70.0000001 and r._value <= 85.0 then
+    "high"
+else
+    "normal"
 ```
 
 When `r._value` is 96, the output is "critical" and the remaining conditions are not evaluated.
@@ -90,16 +94,17 @@ to change how the query filters data.
 
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-      if v.metric == "Memory"
-        then r._measurement == "mem" and r._field == "used_percent"
-      else if v.metric == "CPU"
-        then r._measurement == "cpu" and r._field == "usage_user"
-      else if v.metric == "Disk"
-        then r._measurement == "disk" and r._field == "used_percent"
-      else r._measurement != ""
-  )
+    |> range(start: -1h)
+    |> filter(
+        fn: (r) => if v.metric == "Memory" then
+            r._measurement == "mem" and r._field == "used_percent"
+        else if v.metric == "CPU" then
+            r._measurement == "cpu" and r._field == "usage_user"
+        else if v.metric == "Disk" then
+            r._measurement == "disk" and r._field == "used_percent"
+        else
+            r._measurement != "",
+    )
 ```
 
 
@@ -116,35 +121,42 @@ It sets the `level` column to a specific string based on `_value` column.
 {{% code-tab-content %}}
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -5m)
-  |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent" )
-  |> map(fn: (r) => ({
-    r with
-    level:
-      if r._value >= 95.0000001 and r._value <= 100.0 then "critical"
-      else if r._value >= 85.0000001 and r._value <= 95.0 then "warning"
-      else if r._value >= 70.0000001 and r._value <= 85.0 then "high"
-      else "normal"
-    })
-  )
+    |> range(start: -5m)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+    |> map(
+        fn: (r) => ({r with
+            level: if r._value >= 95.0000001 and r._value <= 100.0 then
+                "critical"
+            else if r._value >= 85.0000001 and r._value <= 95.0 then
+                "warning"
+            else if r._value >= 70.0000001 and r._value <= 85.0 then
+                "high"
+            else
+                "normal",
+        }),
+    )
 ```
 {{% /code-tab-content %}}
 {{% code-tab-content %}}
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -5m)
-  |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent" )
-  |> map(fn: (r) => ({
-    // Retain all existing columns in the mapped row
-    r with
-    // Set the level column value based on the _value column
-    level:
-      if r._value >= 95.0000001 and r._value <= 100.0 then "critical"
-      else if r._value >= 85.0000001 and r._value <= 95.0 then "warning"
-      else if r._value >= 70.0000001 and r._value <= 85.0 then "high"
-      else "normal"
-    })
-  )
+    |> range(start: -5m)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+    |> map(
+        fn: (r) => ({
+            // Retain all existing columns in the mapped row
+            r with
+            // Set the level column value based on the _value column
+            level: if r._value >= 95.0000001 and r._value <= 100.0 then
+                "critical"
+            else if r._value >= 85.0000001 and r._value <= 95.0 then
+                "warning"
+            else if r._value >= 70.0000001 and r._value <= 85.0 then
+                "high"
+            else
+                "normal",
+        }),
+    )
 ```
 
 {{% /code-tab-content %}}
@@ -165,18 +177,20 @@ functions to count the number of records in every five minute window that exceed
 threshold = 65.0
 
 data = from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent" )
-  |> aggregateWindow(
-      every: 5m,
-      fn: (column, tables=<-) => tables |> reduce(
-            identity: {above_threshold_count: 0.0},
-            fn: (r, accumulator) => ({
-              above_threshold_count:
-                if r._value >= threshold then accumulator.above_threshold_count + 1.0
-                else accumulator.above_threshold_count + 0.0
-            })
-        )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+    |> aggregateWindow(
+        every: 5m,
+        fn: (column, tables=<-) => tables
+            |> reduce(
+                identity: {above_threshold_count: 0.0},
+                fn: (r, accumulator) => ({
+                    above_threshold_count: if r._value >= threshold then
+                        accumulator.above_threshold_count + 1.0
+                    else
+                        accumulator.above_threshold_count + 0.0,
+                }),
+            ),
     )
 ```
 {{% /code-tab-content %}}
@@ -185,23 +199,25 @@ data = from(bucket: "example-bucket")
 threshold = 65.0
 
 from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent" )
-  // Aggregate data into 5 minute windows using a custom reduce() function
-  |> aggregateWindow(
-      every: 5m,
-      // Use a custom function in the fn parameter.
-      // The aggregateWindow fn parameter requires 'column' and 'tables' parameters.
-      fn: (column, tables=<-) => tables |> reduce(
-            identity: {above_threshold_count: 0.0},
-            fn: (r, accumulator) => ({
-              // Conditionally increment above_threshold_count if
-              // r.value exceeds the threshold
-              above_threshold_count:
-                if r._value >= threshold then accumulator.above_threshold_count + 1.0
-                else accumulator.above_threshold_count + 0.0
-            })
-        )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+    // Aggregate data into 5 minute windows using a custom reduce() function
+    |> aggregateWindow(
+        every: 5m,
+        // Use a custom function in the fn parameter.
+        // The aggregateWindow fn parameter requires 'column' and 'tables' parameters.
+        fn: (column, tables=<-) => tables
+            |> reduce(
+                identity: {above_threshold_count: 0.0},
+                fn: (r, accumulator) => ({
+                    // Conditionally increment above_threshold_count if
+                    // r.value exceeds the threshold
+                    above_threshold_count: if r._value >= threshold then
+                        accumulator.above_threshold_count + 1.0
+                    else
+                        accumulator.above_threshold_count + 0.0,
+                }),
+            ),
     )
 ```
 {{% /code-tab-content %}}
diff --git a/content/influxdb/v2.1/query-data/flux/cumulativesum.md b/content/influxdb/v2.1/query-data/flux/cumulativesum.md
index 7d12c4d80..2ceed90c3 100644
--- a/content/influxdb/v2.1/query-data/flux/cumulativesum.md
+++ b/content/influxdb/v2.1/query-data/flux/cumulativesum.md
@@ -49,7 +49,7 @@ The examples below use the [example data variable](/influxdb/v2.1/query-data/flu
 ##### Calculate the running total of values
 ```js
 data
-  |> cumulativeSum()
+    |> cumulativeSum()
 ```
 
 ## Use cumulativeSum() with aggregateWindow()
@@ -65,6 +65,6 @@ then calculate the running total of the aggregate values with `cumulativeSum()`.
 <!-- -->
 ```js
 data
-  |> aggregateWindow(every: 5m, fn: sum)
-  |> cumulativeSum()
+    |> aggregateWindow(every: 5m, fn: sum)
+    |> cumulativeSum()
 ```
diff --git a/content/influxdb/v2.1/query-data/flux/custom-functions/_index.md b/content/influxdb/v2.1/query-data/flux/custom-functions/_index.md
index 5457b6378..6c9278837 100644
--- a/content/influxdb/v2.1/query-data/flux/custom-functions/_index.md
+++ b/content/influxdb/v2.1/query-data/flux/custom-functions/_index.md
@@ -12,12 +12,11 @@ aliases:
   - /influxdb/v2.1/query-data/guides/custom-functions/
 list_code_example: |
   ```js
-  multByX = (tables=<-, x) =>
-    tables
-      |> map(fn: (r) => ({ r with _value: r._value * x}))
+  multByX = (tables=<-, x) => tables
+      |> map(fn: (r) => ({r with _value: r._value * x}))
 
   data
-    |> multByX(x: 2.0)
+      |> multByX(x: 2.0)
   ```
 ---
 
@@ -92,18 +91,14 @@ to modify each `_value`.
 
 ```js
 // Function definition
-multByX = (tables=<-, x) =>
-  tables
-    |> map(fn: (r) => ({ r with _value: r._value * x}))
+multByX = (tables=<-, x) => tables
+    |> map(fn: (r) => ({r with _value: r._value * x}))
 
 // Function usage
 from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> filter(fn: (r) =>
-    r._measurement == "mem" and
-    r._field == "used_percent"
-  )
-  |> multByX(x:2.0)
+    |> range(start: -1m)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+    |> multByX(x: 2.0)
 ```
 
 ## Define parameter defaults
@@ -128,29 +123,22 @@ to return a specified number of records from the sorted table.
 
 ```js
 // Function definition
-leaderBoard = (tables=<-, limit=4, columns=["_value"], desc=true) =>
-  tables
+leaderBoard = (tables=<-, limit=4, columns=["_value"], desc=true) => tables
     |> sort(columns: columns, desc: desc)
     |> limit(n: limit)
 
 // Function usage
 // Get the 4 highest scoring players
 from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> filter(fn: (r) =>
-    r._measurement == "player-stats" and
-    r._field == "total-points"
-  )
-  |> leaderBoard()
+    |> range(start: -1m)
+    |> filter(fn: (r) => r._measurement == "player-stats" and r._field == "total-points")
+    |> leaderBoard()
 
 // Get the 10 shortest race times
 from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> filter(fn: (r) =>
-    r._measurement == "race-times" and
-    r._field == "elapsed-time"
-  )
-  |> leaderBoard(limit: 10, desc: false)
+    |> range(start: -1m)
+    |> filter(fn: (r) => r._measurement == "race-times" and r._field == "elapsed-time")
+    |> leaderBoard(limit: 10, desc: false)
 ```
 
 ## Define functions with scoped variables
@@ -160,8 +148,9 @@ and use a `return` statement to return a specific variable.
 
 ```js
 functionName = (functionParameters) => {
-  exampleVar = "foo"
-  return exampleVar
+    exampleVar = "foo"
+
+    return exampleVar
 }
 ```
 
@@ -176,11 +165,16 @@ a numeric input value:
 
 ```js
 alertLevel = (v) => {
-  level = if float(v:v) >= 90.0 then "crit"
-          else if float(v:v) >= 80.0 then "warn"
-          else if float(v:v) >= 65.0 then "info"
-          else "ok"
-  return level
+    level = if float(v: v) >= 90.0 then
+        "crit"
+    else if float(v: v) >= 80.0 then
+        "warn"
+    else if float(v: v) >= 65.0 then
+        "info"
+    else
+        "ok"
+
+    return level
 }
 
 alertLevel(v: 87.3)
@@ -196,26 +190,27 @@ to create a dictionary of HEX codes and their corresponding names.
 import "dict"
 
 hexName = (hex) => {
-  hexNames = dict.fromList(pairs: [
-    {key: "#00ffff", value: "Aqua"},
-    {key: "#000000", value: "Black"},
-    {key: "#0000ff", value: "Blue"},
-    {key: "#ff00ff", value: "Fuchsia"},
-    {key: "#808080", value: "Gray"},
-    {key: "#008000", value: "Green"},
-    {key: "#00ff00", value: "Lime"},
-    {key: "#800000", value: "Maroon"},
-    {key: "#000080", value: "Navy"},
-    {key: "#808000", value: "Olive"},
-    {key: "#800080", value: "Purple"},
-    {key: "#ff0000", value: "Red"},
-    {key: "#c0c0c0", value: "Silver"},
-    {key: "#008080", value: "Teal"},
-    {key: "#ffffff", value: "White"},
-    {key: "#ffff00", value: "Yellow"},
-  ])  
-  name = dict.get(dict: hexNames, key: hex, default: "No known name")
-  return name
+    hexNames = dict.fromList(pairs: [
+        {key: "#00ffff", value: "Aqua"},
+        {key: "#000000", value: "Black"},
+        {key: "#0000ff", value: "Blue"},
+        {key: "#ff00ff", value: "Fuchsia"},
+        {key: "#808080", value: "Gray"},
+        {key: "#008000", value: "Green"},
+        {key: "#00ff00", value: "Lime"},
+        {key: "#800000", value: "Maroon"},
+        {key: "#000080", value: "Navy"},
+        {key: "#808000", value: "Olive"},
+        {key: "#800080", value: "Purple"},
+        {key: "#ff0000", value: "Red"},
+        {key: "#c0c0c0", value: "Silver"},
+        {key: "#008080", value: "Teal"},
+        {key: "#ffffff", value: "White"},
+        {key: "#ffff00", value: "Yellow"},
+    ])  
+    name = dict.get(dict: hexNames, key: hex, default: "No known name")
+    
+    return name
 }
 
 hexName(hex: "#000000")
diff --git a/content/influxdb/v2.1/query-data/flux/custom-functions/custom-aggregate.md b/content/influxdb/v2.1/query-data/flux/custom-functions/custom-aggregate.md
index 79c824441..392a7e6b7 100644
--- a/content/influxdb/v2.1/query-data/flux/custom-functions/custom-aggregate.md
+++ b/content/influxdb/v2.1/query-data/flux/custom-functions/custom-aggregate.md
@@ -45,11 +45,12 @@ The following example `reduce()` function produces a sum and product of all valu
 in an input table.
 
 ```js
-|> reduce(fn: (r, accumulator) => ({
-    sum: r._value + accumulator.sum,
-    product: r._value * accumulator.product
-  }),
-  identity: {sum: 0.0, product: 1.0}
+|> reduce(
+    fn: (r, accumulator) => ({
+        sum: r._value + accumulator.sum,
+        product: r._value * accumulator.product
+    }),
+    identity: {sum: 0.0, product: 1.0},
 )
 ```
 
@@ -238,7 +239,6 @@ profitSummary = (tables=<-) => tables
         fn: (r, accumulator) => ({
             gross: accumulator.gross + r.profit,
             net: accumulator.net + r.profit - r.expenses
-            }
-        )
+        })
     )
 ```
diff --git a/content/influxdb/v2.1/query-data/flux/exists.md b/content/influxdb/v2.1/query-data/flux/exists.md
index 028f2d963..2af8d69c2 100644
--- a/content/influxdb/v2.1/query-data/flux/exists.md
+++ b/content/influxdb/v2.1/query-data/flux/exists.md
@@ -20,7 +20,7 @@ list_code_example: |
   ##### Filter null values
   ```js
   data
-    |> filter(fn: (r) => exists r._value)
+      |> filter(fn: (r) => exists r._value)
   ```
 ---
 
@@ -51,36 +51,38 @@ to check if a row includes a column or if the value for that column is `null`.
 #### Filter null values
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -5m)
-  |> filter(fn: (r) => exists r._value)
+    |> range(start: -5m)
+    |> filter(fn: (r) => exists r._value)
 ```
 
 #### Map values based on existence
 ```js
 from(bucket: "default")
-  |> range(start: -30s)
-  |> map(fn: (r) => ({
-      r with
-      human_readable:
-        if exists r._value then "${r._field} is ${string(v:r._value)}."
-        else "${r._field} has no value."
-  }))
+    |> range(start: -30s)
+    |> map(
+        fn: (r) => ({r with
+            human_readable: if exists r._value then
+                "${r._field} is ${string(v: r._value)}."
+            else
+                "${r._field} has no value.",
+        }),
+    )
 ```
 
 #### Ignore null values in a custom aggregate function
 ```js
-customSumProduct = (tables=<-) =>
-  tables
+customSumProduct = (tables=<-) => tables
     |> reduce(
-      identity: {sum: 0.0, product: 1.0},
-      fn: (r, accumulator) => ({
-        r with
-        sum:
-          if exists r._value then r._value + accumulator.sum
-          else accumulator.sum,
-        product:
-          if exists r._value then r.value * accumulator.product
-          else accumulator.product
-      })
+        identity: {sum: 0.0, product: 1.0},
+        fn: (r, accumulator) => ({r with
+            sum: if exists r._value then
+                r._value + accumulator.sum
+            else
+                accumulator.sum,
+            product: if exists r._value then
+                r.value * accumulator.product
+            else
+                accumulator.product,
+        }),
     )
 ```
diff --git a/content/influxdb/v2.1/query-data/flux/explore-schema.md b/content/influxdb/v2.1/query-data/flux/explore-schema.md
index d0cd8711b..fe5ecd1c9 100644
--- a/content/influxdb/v2.1/query-data/flux/explore-schema.md
+++ b/content/influxdb/v2.1/query-data/flux/explore-schema.md
@@ -85,8 +85,8 @@ to list **field keys in a measurement**.
 import "influxdata/influxdb/schema"
 
 schema.measurementFieldKeys(
-  bucket: "example-bucket",
-  measurement: "example-measurement"
+    bucket: "example-bucket",
+    measurement: "example-measurement",
 )
 ```
 
@@ -109,8 +109,8 @@ _This function returns results from the last 30 days._
 import "influxdata/influxdb/schema"
 
 schema.measurementTagKeys(
-  bucket: "example-bucket",
-  measurement: "example-measurement"
+    bucket: "example-bucket",
+    measurement: "example-measurement",
 )
 ```
 
@@ -133,8 +133,8 @@ _This function returns results from the last 30 days._
 import "influxdata/influxdb/schema"
 
 schema.measurementTagValues(
-  bucket: "example-bucket",
-  tag: "example-tag",
-  measurement: "example-measurement"
+    bucket: "example-bucket",
+    tag: "example-tag",
+    measurement: "example-measurement",
 )
 ```
diff --git a/content/influxdb/v2.1/query-data/flux/fill.md b/content/influxdb/v2.1/query-data/flux/fill.md
index f966dbc1d..8722c6236 100644
--- a/content/influxdb/v2.1/query-data/flux/fill.md
+++ b/content/influxdb/v2.1/query-data/flux/fill.md
@@ -24,12 +24,12 @@ to replace _null_ values with:
 <!-- -->
 ```js
 data
-  |> fill(usePrevious: true)
+    |> fill(usePrevious: true)
 
 // OR
 
 data
-  |> fill(value: 0.0)
+    |> fill(value: 0.0)
 ```
 
 {{% note %}}
@@ -49,7 +49,7 @@ Values remain _null_ if there is no previous non-null value in the table.
 
 ```js
 data
-  |> fill(usePrevious: true)
+    |> fill(usePrevious: true)
 ```
 
 {{< flex >}}
@@ -84,7 +84,7 @@ of the [column](/{{< latest "flux" >}}/stdlib/universe/fill/#column)._
 
 ```js
 data
-  |> fill(value: 0.0)
+    |> fill(value: 0.0)
 ```
 
 {{< flex >}}
diff --git a/content/influxdb/v2.1/query-data/flux/first-last.md b/content/influxdb/v2.1/query-data/flux/first-last.md
index 16e5b697f..9273a1ffe 100644
--- a/content/influxdb/v2.1/query-data/flux/first-last.md
+++ b/content/influxdb/v2.1/query-data/flux/first-last.md
@@ -22,12 +22,12 @@ last record in an input table.
 
 ```js
 data
-  |> first()
+    |> first()
 
 // OR
 
 data
-  |> last()
+    |> last()
 ```
 
 {{% note %}}
@@ -121,10 +121,7 @@ point using aggregate or selector functions, and then removes the time-based seg
 {{% /code-tabs %}}
 {{% code-tab-content %}}
 ```js
-|> aggregateWindow(
-  every: 1h,
-  fn: first
-)
+|> aggregateWindow(every: 1h, fn: first)
 ```
 | _time                | _value |
 |:-----                | ------:|
@@ -134,10 +131,7 @@ point using aggregate or selector functions, and then removes the time-based seg
 {{% /code-tab-content %}}
 {{% code-tab-content %}}
 ```js
-|> aggregateWindow(
-  every: 1h,
-  fn: last
-)
+|> aggregateWindow(every: 1h, fn: last)
 ```
 
 | _time                | _value |
diff --git a/content/influxdb/v2.1/query-data/flux/geo/_index.md b/content/influxdb/v2.1/query-data/flux/geo/_index.md
index 2ad12e7fa..b12ae200b 100644
--- a/content/influxdb/v2.1/query-data/flux/geo/_index.md
+++ b/content/influxdb/v2.1/query-data/flux/geo/_index.md
@@ -13,8 +13,8 @@ list_code_example: |
   import "experimental/geo"
 
   sampleGeoData
-    |> geo.filterRows(region: {lat: 30.04, lon: 31.23, radius: 200.0})
-    |> geo.groupByArea(newColumn: "geoArea", level: 5)
+      |> geo.filterRows(region: {lat: 30.04, lon: 31.23, radius: 200.0})
+      |> geo.groupByArea(newColumn: "geoArea", level: 5)
   ```
 ---
 
diff --git a/content/influxdb/v2.1/query-data/flux/geo/filter-by-region.md b/content/influxdb/v2.1/query-data/flux/geo/filter-by-region.md
index 71de64b38..3c6fa8635 100644
--- a/content/influxdb/v2.1/query-data/flux/geo/filter-by-region.md
+++ b/content/influxdb/v2.1/query-data/flux/geo/filter-by-region.md
@@ -35,10 +35,7 @@ and queries data points **within 200km of Cairo, Egypt**:
 import "experimental/geo"
 
 sampleGeoData
-  |> geo.filterRows(
-    region: {lat: 30.04, lon: 31.23, radius: 200.0},
-    strict: true
-  )
+    |> geo.filterRows(region: {lat: 30.04, lon: 31.23, radius: 200.0}, strict: true)
 ```
 
 ## Define a geographic region
@@ -60,10 +57,10 @@ Define a box-shaped region by specifying a record containing the following prope
 ##### Example box-shaped region
 ```js
 {
-  minLat: 40.51757813,
-  maxLat: 40.86914063,
-  minLon: -73.65234375,
-  maxLon: -72.94921875
+    minLat: 40.51757813,
+    maxLat: 40.86914063,
+    minLon: -73.65234375,
+    maxLon: -72.94921875,
 }
 ```
 
@@ -77,9 +74,9 @@ Define a circular region by specifying a record containing the following propert
 ##### Example circular region
 ```js
 {
-  lat: 40.69335938,
-  lon: -73.30078125,
-  radius: 20.0
+    lat: 40.69335938,
+    lon: -73.30078125,
+    radius: 20.0,
 }
 ```
 
@@ -97,11 +94,11 @@ each point in the polygon:
 ##### Example polygonal region
 ```js
 {
-  points: [
-    {lat: 40.671659, lon: -73.936631},
-    {lat: 40.706543, lon: -73.749177},
-    {lat: 40.791333, lon: -73.880327}
-  ]
+    points: [
+        {lat: 40.671659, lon: -73.936631},
+        {lat: 40.706543, lon: -73.749177},
+        {lat: 40.791333, lon: -73.880327},
+    ]
 }
 ```
 
diff --git a/content/influxdb/v2.1/query-data/flux/geo/group-geo-data.md b/content/influxdb/v2.1/query-data/flux/geo/group-geo-data.md
index ebbf25980..437587a1e 100644
--- a/content/influxdb/v2.1/query-data/flux/geo/group-geo-data.md
+++ b/content/influxdb/v2.1/query-data/flux/geo/group-geo-data.md
@@ -16,8 +16,8 @@ list_code_example: |
   import "experimental/geo"
 
   sampleGeoData
-    |> geo.groupByArea(newColumn: "geoArea", level: 5)
-    |> geo.asTracks(groupBy: ["id"],sortBy: ["_time"])
+      |> geo.groupByArea(newColumn: "geoArea", level: 5)
+      |> geo.asTracks(groupBy: ["id"],sortBy: ["_time"])
   ```
 ---
 
@@ -48,11 +48,8 @@ to query data points within 200km of Cairo, Egypt and group them by geographic a
 import "experimental/geo"
 
 sampleGeoData
-  |> geo.filterRows(region: {lat: 30.04, lon: 31.23, radius: 200.0})
-  |> geo.groupByArea(
-    newColumn: "geoArea",
-    level: 5
-  )
+    |> geo.filterRows(region: {lat: 30.04, lon: 31.23, radius: 200.0})
+    |> geo.groupByArea(newColumn: "geoArea", level: 5)
 ```
 
 ### Group data by track or route
@@ -71,9 +68,6 @@ to each bird:
 import "experimental/geo"
 
 sampleGeoData
-  |> geo.filterRows(region: {lat: 30.04, lon: 31.23, radius: 200.0})
-  |> geo.asTracks(
-    groupBy: ["id"],
-    orderBy: ["_time"]
-  )
+    |> geo.filterRows(region: {lat: 30.04, lon: 31.23, radius: 200.0})
+    |> geo.asTracks(groupBy: ["id"], orderBy: ["_time"])
 ```
diff --git a/content/influxdb/v2.1/query-data/flux/geo/shape-geo-data.md b/content/influxdb/v2.1/query-data/flux/geo/shape-geo-data.md
index a85950395..921022b37 100644
--- a/content/influxdb/v2.1/query-data/flux/geo/shape-geo-data.md
+++ b/content/influxdb/v2.1/query-data/flux/geo/shape-geo-data.md
@@ -16,7 +16,7 @@ list_code_example: |
   import "experimental/geo"
 
   sampleGeoData
-    |> geo.shapeData(latField: "latitude", lonField: "longitude", level: 10)
+      |> geo.shapeData(latField: "latitude", lonField: "longitude", level: 10)
   ```
 ---
 
@@ -37,13 +37,9 @@ into row-wise sets, and generate S2 cell ID tokens for each point.
 import "experimental/geo"
 
 from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "example-measurement")
-  |> geo.shapeData(
-    latField: "latitude",
-    lonField: "longitude",
-    level: 10
-  )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> geo.shapeData(latField: "latitude", lonField: "longitude", level: 10)
 ```
 
 ## Generate S2 cell ID tokens
@@ -107,12 +103,14 @@ to pivot **lat** and **lon** fields into row-wise sets:
 import "experimental/geo"
 
 from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "example-measurement")
-  |> geo.toRows()
-  |> map(fn: (r) => ({ r with
-    s2_cell_id: geo.s2CellIDToken(point: {lon: r.lon, lat: r.lat}, level: 10)
-  }))
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> geo.toRows()
+    |> map(
+        fn: (r) => ({ r with
+            s2_cell_id: geo.s2CellIDToken(point: {lon: r.lon, lat: r.lat}, level: 10)
+        })
+    )
 ```
 
 {{% note %}}
diff --git a/content/influxdb/v2.1/query-data/flux/group-data.md b/content/influxdb/v2.1/query-data/flux/group-data.md
index 2fe629922..3dcc175a9 100644
--- a/content/influxdb/v2.1/query-data/flux/group-data.md
+++ b/content/influxdb/v2.1/query-data/flux/group-data.md
@@ -46,7 +46,7 @@ group key for output tables, i.e. grouping records based on values for specific
 ###### group() example
 ```js
 dataStream
-  |> group(columns: ["cpu", "host"])
+    |> group(columns: ["cpu", "host"])
 ```
 
 ###### Resulting group key
@@ -75,12 +75,9 @@ It uses a regular expression to filter only numbered cores.
 
 ```js
 dataSet = from(bucket: "example-bucket")
-  |> range(start: -2m)
-  |> filter(fn: (r) =>
-    r._field == "usage_system" and
-    r.cpu =~ /cpu[0-9*]/
-  )
-  |> drop(columns: ["host"])
+    |> range(start: -2m)
+    |> filter(fn: (r) => r._field == "usage_system" and r.cpu =~ /cpu[0-9*]/)
+    |> drop(columns: ["host"])
 ```
 
 {{% note %}}
@@ -170,7 +167,7 @@ Group the `dataSet` stream by the `cpu` column.
 
 ```js
 dataSet
-  |> group(columns: ["cpu"])
+    |> group(columns: ["cpu"])
 ```
 
 This won't actually change the structure of the data since it already has `cpu`
@@ -259,7 +256,7 @@ Grouping data by the `_time` column is a good illustration of how grouping chang
 
 ```js
 dataSet
-  |> group(columns: ["_time"])
+    |> group(columns: ["_time"])
 ```
 
 When grouping by `_time`, all records that share a common `_time` value are grouped into individual tables.
@@ -386,9 +383,9 @@ If you're interested in running and visualizing this yourself, here's what the q
 
 ```js
 dataSet
-  |> group(columns: ["_time"])
-  |> mean()
-  |> group(columns: ["_value", "_time"], mode: "except")
+    |> group(columns: ["_time"])
+    |> mean()
+    |> group(columns: ["_value", "_time"], mode: "except")
 ```
 {{% /note %}}
 
@@ -397,7 +394,7 @@ Group by the `cpu` and `_time` columns.
 
 ```js
 dataSet
-  |> group(columns: ["cpu", "_time"])
+    |> group(columns: ["cpu", "_time"])
 ```
 
 This outputs a table for every unique `cpu` and `_time` combination:
diff --git a/content/influxdb/v2.1/query-data/flux/histograms.md b/content/influxdb/v2.1/query-data/flux/histograms.md
index cf1bdb962..31c2af74c 100644
--- a/content/influxdb/v2.1/query-data/flux/histograms.md
+++ b/content/influxdb/v2.1/query-data/flux/histograms.md
@@ -35,13 +35,10 @@ In the histogram output, a column is added (`le`) that represents the upper boun
 Bin counts are cumulative.
 
 ```js
-from(bucket:"example-bucket")
-  |> range(start: -5m)
-  |> filter(fn: (r) =>
-    r._measurement == "mem" and
-    r._field == "used_percent"
-  )
-  |> histogram(bins: [0.0, 10.0, 20.0, 30.0])
+from(bucket: "example-bucket")
+    |> range(start: -5m)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+    |> histogram(bins: [0.0, 10.0, 20.0, 30.0])
 ```
 
 {{% note %}}
@@ -94,20 +91,10 @@ View the example [below](#visualize-errors-by-severity).
 
 ### Generate a histogram with linear bins
 ```js
-from(bucket:"example-bucket")
-  |> range(start: -5m)
-  |> filter(fn: (r) =>
-    r._measurement == "mem" and
-    r._field == "used_percent"
-  )
-  |> histogram(
-    bins: linearBins(
-      start:65.5,
-      width: 0.5,
-      count: 20,
-      infinity:false
-    )
-  )
+from(bucket: "example-bucket")
+    |> range(start: -5m)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+    |> histogram(bins: linearBins(start: 65.5, width: 0.5, count: 20, infinity: false))
 ```
 
 ###### Output table
@@ -139,20 +126,10 @@ Table: keys: [_start, _stop, _field, _measurement, host]
 
 ### Generate a histogram with logarithmic bins
 ```js
-from(bucket:"example-bucket")
-  |> range(start: -5m)
-  |> filter(fn: (r) =>
-    r._measurement == "mem" and
-    r._field == "used_percent"
-  )
-  |> histogram(
-    bins: logarithmicBins(
-      start:0.5,
-      factor: 2.0,
-      count: 10,
-      infinity:false
-    )
-  )
+from(bucket: "example-bucket")
+    |> range(start: -5m)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+    |> histogram(bins: logarithmicBins(start: 0.5, factor: 2.0, count: 10, infinity: false))
 ```
 
 ###### Output table
@@ -179,11 +156,8 @@ Query the `severity_code` field in the `syslog` measurement:
 
 ```js
 from(bucket: "example-bucket")
-  |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
-  |> filter(fn: (r) =>
-      r._measurement == "syslog" and
-      r._field == "severity_code"
-  )
+    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
+    |> filter(fn: (r) => r._measurement == "syslog" and r._field == "severity_code")
 ```
 
 In the Histogram visualization options, select `_time` as the **X Column**
diff --git a/content/influxdb/v2.1/query-data/flux/increase.md b/content/influxdb/v2.1/query-data/flux/increase.md
index 238499a3e..6b92a13ec 100644
--- a/content/influxdb/v2.1/query-data/flux/increase.md
+++ b/content/influxdb/v2.1/query-data/flux/increase.md
@@ -24,7 +24,7 @@ wrap over time or periodically reset.
 
 ```js
 data
-  |> increase()
+    |> increase()
 ```
 
 `increase()` returns a cumulative sum of **non-negative** differences between rows in a table.
diff --git a/content/influxdb/v2.1/query-data/flux/join.md b/content/influxdb/v2.1/query-data/flux/join.md
index 7b641de86..8d0418aa9 100644
--- a/content/influxdb/v2.1/query-data/flux/join.md
+++ b/content/influxdb/v2.1/query-data/flux/join.md
@@ -43,11 +43,8 @@ This returns the amount of memory (in bytes) used.
 ###### memUsed stream definition
 ```js
 memUsed = from(bucket: "example-bucket")
-  |> range(start: -5m)
-  |> filter(fn: (r) =>
-    r._measurement == "mem" and
-    r._field == "used"
-  )
+    |> range(start: -5m)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used")
 ```
 
 {{% truncate %}}
@@ -97,11 +94,8 @@ This returns the number of running processes.
 ###### procTotal stream definition
 ```js
 procTotal = from(bucket: "example-bucket")
-  |> range(start: -5m)
-  |> filter(fn: (r) =>
-    r._measurement == "processes" and
-    r._field == "total"
-  )
+    |> range(start: -5m)
+    |> filter(fn: (r) => r._measurement == "processes" and r._field == "total")
 ```
 
 {{% truncate %}}
@@ -158,8 +152,8 @@ _**Both tables must have all columns specified in this list.**_
 
 ```js
 join(
-  tables: {mem:memUsed, proc:procTotal},
-  on: ["_time", "_stop", "_start", "host"]
+    tables: {mem:memUsed, proc:procTotal},
+    on: ["_time", "_stop", "_start", "host"],
 )
 ```
 
@@ -222,12 +216,8 @@ column and dividing `_value_mem` by `_value_proc` and mapping it to a
 new `_value` column.
 
 ```js
-join(tables: {mem:memUsed, proc:procTotal}, on: ["_time", "_stop", "_start", "host"])
-  |> map(fn: (r) => ({
-      _time: r._time,
-      _value: r._value_mem / r._value_proc
-    })
-  )
+join(tables: {mem: memUsed, proc: procTotal}, on: ["_time", "_stop", "_start", "host"])
+    |> map(fn: (r) => ({_time: r._time, _value: r._value_mem / r._value_proc}))
 ```
 
 {{% truncate %}}
@@ -280,36 +270,27 @@ The results are grouped by cluster ID so you can make comparisons across cluster
 
 ```js
 batchSize = (cluster_id, start=-1m, interval=10s) => {
-  httpd = from(bucket:"telegraf")
-    |> range(start:start)
-    |> filter(fn:(r) =>
-      r._measurement == "influxdb_httpd" and
-      r._field == "writeReq" and
-      r.cluster_id == cluster_id
-    )
-    |> aggregateWindow(every: interval, fn: mean)
-    |> derivative(nonNegative:true,unit:60s)
+    httpd = from(bucket: "telegraf")
+        |> range(start: start)
+        |> filter(fn: (r) => r._measurement == "influxdb_httpd" and r._field == "writeReq" and r.cluster_id == cluster_id)
+        |> aggregateWindow(every: interval, fn: mean)
+        |> derivative(nonNegative: true, unit: 60s)
 
-  write = from(bucket:"telegraf")
-    |> range(start:start)
-    |> filter(fn:(r) =>
-      r._measurement == "influxdb_write" and
-      r._field == "pointReq" and
-      r.cluster_id == cluster_id
-    )
-    |> aggregateWindow(every: interval, fn: max)
-    |> derivative(nonNegative:true,unit:60s)
+    write = from(bucket: "telegraf")
+        |> range(start: start)
+        |> filter(fn: (r) => r._measurement == "influxdb_write" and r._field == "pointReq" and r.cluster_id == cluster_id)
+        |> aggregateWindow(every: interval, fn: max)
+        |> derivative(nonNegative: true, unit: 60s)
 
-  return join(
-      tables:{httpd:httpd, write:write},
-      on:["_time","_stop","_start","host"]
-    )
-    |> map(fn:(r) => ({
-        _time: r._time,
-        _value: r._value_httpd / r._value_write,
-    }))
-    |> group(columns: cluster_id)
+    return join(tables: {httpd: httpd, write: write}, on: ["_time", "_stop", "_start", "host"])
+        |> map(fn: (r) => ({_time: r._time, _value: r._value_httpd / r._value_write}))
+        |> group(columns: cluster_id)
 }
 
 batchSize(cluster_id: "enter cluster id here")
 ```
+
+To see how join works in InfluxDB, watch the following video:
+
+{{< youtube g-HY1Q11iGg >}}
+
diff --git a/content/influxdb/v2.1/query-data/flux/manipulate-timestamps.md b/content/influxdb/v2.1/query-data/flux/manipulate-timestamps.md
index c51e4e7fe..d321eda5a 100644
--- a/content/influxdb/v2.1/query-data/flux/manipulate-timestamps.md
+++ b/content/influxdb/v2.1/query-data/flux/manipulate-timestamps.md
@@ -126,7 +126,7 @@ operations where points should align by time, but timestamps vary slightly.
 
 ```js
 data
-  |> truncateTimeColumn(unit: 1m)
+    |> truncateTimeColumn(unit: 1m)
 ```
 
 {{< flex >}}
@@ -170,10 +170,7 @@ By using `experimental.addDuration()`, you accept the
 ```js
 import "experimental"
 
-experimental.addDuration(
-  d: 6h,
-  to: 2019-09-16T12:00:00Z,
-)
+experimental.addDuration(d: 6h, to: 2019-09-16T12:00:00Z)
 
 // Returns 2019-09-16T18:00:00.000000000Z
 ```
@@ -190,10 +187,7 @@ By using `experimental.subDuration()`, you accept the
 ```js
 import "experimental"
 
-experimental.subDuration(
-  d: 6h,
-  from: 2019-09-16T12:00:00Z,
-)
+experimental.subDuration(d: 6h, from: 2019-09-16T12:00:00Z)
 
 // Returns 2019-09-16T06:00:00.000000000Z
 ```
@@ -206,13 +200,13 @@ Shift forward in time:
 
 ```js
 from(bucket: "example-bucket")
-	|> range(start: -5m)
-	|> timeShift(duration: 12h)
+    |> range(start: -5m)
+    |> timeShift(duration: 12h)
 ```
 Shift backward in time:
 
 ```js
 from(bucket: "example-bucket")
-	|> range(start: -5m)
-	|> timeShift(duration: -12h)
+    |> range(start: -5m)
+    |> timeShift(duration: -12h)
 ```
diff --git a/content/influxdb/v2.1/query-data/flux/mathematic-operations.md b/content/influxdb/v2.1/query-data/flux/mathematic-operations.md
index e3a149906..8f37d3730 100644
--- a/content/influxdb/v2.1/query-data/flux/mathematic-operations.md
+++ b/content/influxdb/v2.1/query-data/flux/mathematic-operations.md
@@ -110,16 +110,11 @@ The example `multiplyByX()` function below includes:
   It also multiples the `_value` column by `x`.
 
 ```js
-multiplyByX = (x, tables=<-) =>
-  tables
-    |> map(fn: (r) => ({
-        r with
-        _value: r._value * x
-      })
-    )
+multiplyByX = (x, tables=<-) => tables
+    |> map(fn: (r) => ({r with _value: r._value * x}))
 
 data
-  |> multiplyByX(x: 10)
+    |> multiplyByX(x: 10)
 ```
 
 ## Examples
@@ -133,31 +128,19 @@ a new `_value` by dividing the original `_value` by 1073741824.
 
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -10m)
-  |> filter(fn: (r) =>
-    r._measurement == "mem" and
-    r._field == "active"
-  )
-  |> map(fn: (r) => ({
-      r with
-      _value: r._value / 1073741824
-    })
-  )
+    |> range(start: -10m)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "active")
+    |> map(fn: (r) => ({r with _value: r._value / 1073741824}))
 ```
 
 You could turn that same calculation into a function:
 
 ```js
-bytesToGB = (tables=<-) =>
-  tables
-    |> map(fn: (r) => ({
-        r with
-        _value: r._value / 1073741824
-      })
-    )
+bytesToGB = (tables=<-) => tables
+    |> map(fn: (r) => ({r with _value: r._value / 1073741824}))
 
 data
-  |> bytesToGB()
+    |> bytesToGB()
 ```
 
 #### Include partial gigabytes
@@ -167,13 +150,8 @@ To calculate partial GBs, convert the `_value` column and its values to floats u
 and format the denominator in the division operation as a float.
 
 ```js
-bytesToGB = (tables=<-) =>
-  tables
-    |> map(fn: (r) => ({
-        r with
-        _value: float(v: r._value) / 1073741824.0
-      })
-    )
+bytesToGB = (tables=<-) => tables
+    |> map(fn: (r) => ({r with _value: float(v: r._value) / 1073741824.0}))
 ```
 
 ### Calculate a percentage
@@ -202,10 +180,8 @@ Use `join()` when querying data from different buckets or data sources.
 ##### Pivot fields into columns for mathematic calculations
 ```js
 data
-  |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
-  |> map(fn: (r) => ({ r with
-    _value: (r.field1 + r.field2) / r.field3 * 100.0
-  }))
+    |> pivot(rowKey: ["_time"], columnKey: ["_field"], valueColumn: "_value")
+    |> map(fn: (r) => ({r with _value: (r.field1 + r.field2) / r.field3 * 100.0}))
 ```
 
 ##### Join multiple data sources for mathematic calculations
@@ -218,18 +194,15 @@ pgPass = secrets.get(key: "POSTGRES_PASSWORD")
 pgHost = secrets.get(key: "POSTGRES_HOST")
 
 t1 = sql.from(
-  driverName: "postgres",
-  dataSourceName: "postgresql://${pgUser}:${pgPass}@${pgHost}",
-  query:"SELECT id, name, available FROM example_table"
+    driverName: "postgres",
+    dataSourceName: "postgresql://${pgUser}:${pgPass}@${pgHost}",
+    query: "SELECT id, name, available FROM example_table",
 )
 
 t2 = from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "example-measurement" and
-    r._field == "example-field"
-  )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement" and r._field == "example-field")
 
 join(tables: {t1: t1, t2: t2}, on: ["id"])
-  |> map(fn: (r) => ({ r with _value: r._value_t2 / r.available_t1 * 100.0 }))
+    |> map(fn: (r) => ({r with _value: r._value_t2 / r.available_t1 * 100.0}))
 ```
diff --git a/content/influxdb/v2.1/query-data/flux/median.md b/content/influxdb/v2.1/query-data/flux/median.md
index aa44f8eeb..3620d7cf3 100644
--- a/content/influxdb/v2.1/query-data/flux/median.md
+++ b/content/influxdb/v2.1/query-data/flux/median.md
@@ -110,7 +110,7 @@ contain values in the 50th percentile of data in the table.
 
 ```js
 data
-  |> median()
+    |> median()
 ```
 
 ## Find the average of values closest to the median
@@ -119,7 +119,7 @@ average of the two values closest to the mathematical median of data in the tabl
 
 ```js
 data
-  |> median(method: "exact_mean")
+    |> median(method: "exact_mean")
 ```
 
 ## Find the point with the median value
@@ -128,7 +128,7 @@ value that 50% of values in the table are less than.
 
 ```js
 data
-  |> median(method: "exact_selector")
+    |> median(method: "exact_selector")
 ```
 
 ## Use median() with aggregateWindow()
@@ -142,8 +142,8 @@ To specify the [median calculation method](#select-a-method-for-calculating-the-
 
 ```js
 data
-  |> aggregateWindow(
-    every: 5m,
-    fn: (tables=<-, column) => tables |> median(method: "exact_selector")
-  )
+    |> aggregateWindow(
+        every: 5m,
+        fn: (tables=<-, column) => tables |> median(method: "exact_selector")
+    )
 ```
diff --git a/content/influxdb/v2.1/query-data/flux/monitor-states.md b/content/influxdb/v2.1/query-data/flux/monitor-states.md
index af01694ef..92268788a 100644
--- a/content/influxdb/v2.1/query-data/flux/monitor-states.md
+++ b/content/influxdb/v2.1/query-data/flux/monitor-states.md
@@ -24,81 +24,79 @@ Flux helps you monitor states in your metrics and events:
 If you're just getting started with Flux queries, check out the following:
 
 - [Get started with Flux](/{{< latest "flux" >}}/get-started/) for a conceptual overview of Flux.
-- [Execute queries](/influxdb/v2.1/query-data/execute-queries/) to discover a variety of ways to run your queries.
+- [Execute queries](/influxdb/v2.2/query-data/execute-queries/) to discover a variety of ways to run your queries.
 
 ## Find how long a state persists
 
-1. Use the [`stateDuration()`](/{{< latest "flux" >}}/stdlib/universe/stateduration/) function to calculate how long a column value has remained the same value (or state). Include the following information:
+Use [`stateDuration()`](/{{< latest "flux" >}}/stdlib/universe/stateduration/)
+to calculate the duration of consecutive rows with a specified state.
+For each consecutive point that matches the specified state, `stateDuration()`
+increments and stores the duration (in the specified unit) in a user-defined column.
 
-  - **Column to search:** any tag key, tag value, field key, field value, or measurement.
-  - **Value:** the value (or state) to search for in the specified column.
-  - **State duration column:** a new column to store the state duration─the length of time that the specified value persists.
-  - **Unit:** the unit of time (`1s` (by default), `1m`, `1h`) used to increment the state duration.
+Include the following information:
 
-        ```js
-        |> stateDuration(
-           fn: (r) => r._column_to_search == "value_to_search_for",
-           column: "state_duration",
-           unit: 1s
-         )
-        ```
+- **Column to search:** any tag key, tag value, field key, field value, or measurement.
+- **Value:** the value (or state) to search for in the specified column.
+- **State duration column:** a new column to store the state duration─the length of time that the specified value persists.
+- **Unit:** the unit of time (`1s` (by default), `1m`, `1h`) used to increment the state duration.
 
-2. Use `stateDuration()` to search each point for the specified value:
+```js
+data
+    |> stateDuration(fn: (r) => r.column_to_search == "value_to_search_for", column: "state_duration", unit: 1s)
+```
 
-    - For the first point that evaluates `true`, the state duration is set to `0`. For each consecutive point that evaluates `true`, the state duration increases by the time interval between each consecutive point (in specified units).
-    - If the state is `false`, the state duration is reset to `-1`.
+- For the first point that evaluates `true`, the state duration is set to `0`.
+  For each consecutive point that evaluates `true`, the state duration
+  increases by the time interval between each consecutive point (in specified units).
+- If the state is `false`, the state duration is reset to `-1`.
 
 ### Example query with stateDuration()
 
 The following query searches the `doors` bucket over the past 5 minutes to find how many seconds a door has been `closed`.
 
 ```js
-  from(bucket: "doors")
-   |> range(start: -5m)
-   |> stateDuration(
-      fn: (r) =>
-      r._value == "closed",
-      column: "door_closed",
-      unit: 1s)
+from(bucket: "doors")
+    |> range(start: -5m)
+    |> stateDuration(fn: (r) => r._value == "closed", column: "door_closed", unit: 1s)
 ```
 
-In this example, `door_closed` is the **State duration** column. If you write data to the `doors` bucket every minute, the state duration increases by `60s` for each consecutive point where `_value` is `closed`. If `_value` is not `closed`, the state duration is reset to `0`.
+In this example, `door_closed` is the **State duration** column.
+If you write data to the `doors` bucket every minute, the state duration
+increases by `60s` for each consecutive point where `_value` is `closed`.
+If `_value` is not `closed`, the state duration is reset to `0`.
 
 #### Query results
 
 Results for the example query above may look like this (for simplicity, we've omitted the measurement, tag, and field columns):
 
-```sh
-_time                   _value        door_closed
-2019-10-26T17:39:16Z    closed        0
-2019-10-26T17:40:16Z    closed        60
-2019-10-26T17:41:16Z    closed        120
-2019-10-26T17:42:16Z    open          -1
-2019-10-26T17:43:16Z    closed        0
-2019-10-26T17:44:27Z    closed        60
-```
+| _time                | _value | door_closed |
+| :------------------- | :----: | ----------: |
+| 2019-10-26T17:39:16Z | closed |           0 |
+| 2019-10-26T17:40:16Z | closed |          60 |
+| 2019-10-26T17:41:16Z | closed |         120 |
+| 2019-10-26T17:42:16Z |  open  |          -1 |
+| 2019-10-26T17:43:16Z | closed |           0 |
+| 2019-10-26T17:44:27Z | closed |          60 |
 
 ## Count the number of consecutive states
 
-1. Use the [`stateCount()` function](/{{< latest "flux" >}}/stdlib/universe/statecount/)
-   and include the following information:
+Use the [`stateCount()` function](/{{< latest "flux" >}}/stdlib/universe/statecount/)
+and include the following information:
 
-  - **Column to search:** any tag key, tag value, field key, field value, or measurement.
-  - **Value:** to search for in the specified column.
-  - **State count column:** a new column to store the state count─the number of
-    consecutive records in which the specified value exists.
+- **Column to search:** any tag key, tag value, field key, field value, or measurement.
+- **Value:** to search for in the specified column.
+- **State count column:** a new column to store the state count─the number of
+  consecutive records in which the specified value exists.
 
-        ```js
-        |> stateCount(
-          fn: (r) => r._column_to_search == "value_to_search_for",
-          column: "state_count"
-        )
-        ```
+```js
+|> stateCount(
+    fn: (r) => r.column_to_search == "value_to_search_for",
+    column: "state_count",
+)
+```
 
-2. Use `stateCount()` to search each point for the specified value:
-
-    - For the first point that evaluates `true`, the state count is set to `1`. For each consecutive point that evaluates `true`, the state count increases by 1.
-    - If the state is `false`, the state count is reset to `-1`.
+- For the first point that evaluates `true`, the state count is set to `1`. For each consecutive point that evaluates `true`, the state count increases by 1.
+- If the state is `false`, the state count is reset to `-1`.
 
 ### Example query with stateCount()
 
@@ -106,11 +104,8 @@ The following query searches the `doors` bucket over the past 5 minutes and calc
 
 ```js
 from(bucket: "doors")
-  |> range(start: -5m)
-  |> stateDuration(
-    fn: (r) => r._value == "closed",
-    column: "door_closed"
-  )
+    |> range(start: -5m)
+    |> stateDuration(fn: (r) => r._value == "closed", column: "door_closed")
 ```
 
 This example stores the **state count** in the `door_closed` column. If you write data to the `doors` bucket every minute, the state count increases by `1` for each consecutive point where `_value` is `closed`. If `_value` is not `closed`, the state count is reset to `-1`.
@@ -119,15 +114,14 @@ This example stores the **state count** in the `door_closed` column. If you writ
 
 Results for the example query above may look like this (for simplicity, we've omitted the measurement, tag, and field columns):
 
-```bash
-_time                   _value        door_closed
-2019-10-26T17:39:16Z    closed        1
-2019-10-26T17:40:16Z    closed        2
-2019-10-26T17:41:16Z    closed        3
-2019-10-26T17:42:16Z    open          -1
-2019-10-26T17:43:16Z    closed        1
-2019-10-26T17:44:27Z    closed        2
-```
+| _time                | _value | door_closed |
+| :------------------- | :----: | ----------: |
+| 2019-10-26T17:39:16Z | closed |           1 |
+| 2019-10-26T17:40:16Z | closed |           2 |
+| 2019-10-26T17:41:16Z | closed |           3 |
+| 2019-10-26T17:42:16Z |  open  |          -1 |
+| 2019-10-26T17:43:16Z | closed |           1 |
+| 2019-10-26T17:44:27Z | closed |           2 |
 
 #### Example query to count machine state
 
@@ -135,15 +129,11 @@ The following query checks the machine state every minute (idle, assigned, or bu
 
 ```js
 from(bucket: "servers")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-     r.machine_state == "idle" or
-     r.machine_state == "assigned" or
-     r.machine_state == "busy"
-  )
-  |> stateCount(fn: (r) => r.machine_state == "busy", column: "_count")
-  |> stateCount(fn: (r) => r.machine_state == "assigned", column: "_count")
-  |> stateCount(fn: (r) => r.machine_state == "idle", column: "_count")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r.machine_state == "idle" or r.machine_state == "assigned" or r.machine_state == "busy")
+    |> stateCount(fn: (r) => r.machine_state == "busy", column: "_count")
+    |> stateCount(fn: (r) => r.machine_state == "assigned", column: "_count")
+    |> stateCount(fn: (r) => r.machine_state == "idle", column: "_count")
 ```
 
 <!--## Detect state changes
diff --git a/content/influxdb/v2.1/query-data/flux/moving-average.md b/content/influxdb/v2.1/query-data/flux/moving-average.md
index 1f7102625..3e0639125 100644
--- a/content/influxdb/v2.1/query-data/flux/moving-average.md
+++ b/content/influxdb/v2.1/query-data/flux/moving-average.md
@@ -22,12 +22,12 @@ to return the moving average of data.
 
 ```js
 data
-  |> movingAverage(n: 5)
+    |> movingAverage(n: 5)
 
 // OR
 
 data
-  |> timedMovingAverage(every: 5m, period: 10m)
+    |> timedMovingAverage(every: 5m, period: 10m)
 ```
 
 ### movingAverage()
@@ -102,10 +102,7 @@ If `every = 30m` and `period = 1h`:
 **The following would return:**
 
 ```js
-|> timedMovingAverage(
-  every: 30m,
-  period: 1h
-)
+|> timedMovingAverage(every: 30m, period: 1h)
 ```  
 
 | _time                | _value |
diff --git a/content/influxdb/v2.1/query-data/flux/percentile-quantile.md b/content/influxdb/v2.1/query-data/flux/percentile-quantile.md
index a49fecb89..367724e54 100644
--- a/content/influxdb/v2.1/query-data/flux/percentile-quantile.md
+++ b/content/influxdb/v2.1/query-data/flux/percentile-quantile.md
@@ -122,7 +122,7 @@ contain values in the 99th percentile of data in the table.
 
 ```js
 data
-  |> quantile(q: 0.99)
+    |> quantile(q: 0.99)
 ```
 
 ## Find the average of values closest to the quantile
@@ -132,7 +132,7 @@ For example, to calculate the `0.99` quantile:
 
 ```js
 data
-  |> quantile(q: 0.99, method: "exact_mean")
+    |> quantile(q: 0.99, method: "exact_mean")
 ```
 
 ## Find the point with the quantile value
@@ -142,7 +142,7 @@ For example, to calculate the `0.99` quantile:
 
 ```js
 data
-  |> quantile(q: 0.99, method: "exact_selector")
+    |> quantile(q: 0.99, method: "exact_selector")
 ```
 
 ## Use quantile() with aggregateWindow()
@@ -156,10 +156,9 @@ To specify the [quantile calculation method](#select-a-method-for-calculating-th
 
 ```js
 data
-  |> aggregateWindow(
-    every: 5m,
-    fn: (tables=<-, column) =>
-      tables
-        |> quantile(q: 0.99, method: "exact_selector")
-  )
+    |> aggregateWindow(
+        every: 5m,
+        fn: (tables=<-, column) => tables
+            |> quantile(q: 0.99, method: "exact_selector"),
+    )
 ```
diff --git a/content/influxdb/v2.1/query-data/flux/query-fields.md b/content/influxdb/v2.1/query-data/flux/query-fields.md
index b68e8c5d4..8114b7af3 100644
--- a/content/influxdb/v2.1/query-data/flux/query-fields.md
+++ b/content/influxdb/v2.1/query-data/flux/query-fields.md
@@ -17,12 +17,9 @@ related:
 list_code_example: |
   ```js
   from(bucket: "example-bucket")
-    |> range(start: -1h)
-    |> filter(fn: (r) =>
-        r._measurement == "example-measurement" and
-        r._field == "example-field" and
-        r.tag == "example-tag"
-    )
+      |> range(start: -1h)
+      |> filter(fn: (r) => r._measurement == "example-measurement" and r.tag == "example-tag")
+      |> filter(fn: (r) => r._field == "example-field")
   ```
 ---
 
@@ -40,7 +37,7 @@ Rows that evaluate to `false` are **excluded** from the output data.
 
 ```js
 // ...
-  |> filter(fn: (r) => r._measurement == "example-measurement" )
+    |> filter(fn: (r) => r._measurement == "example-measurement" )
 ```
 
 The `fn` predicate function requires an `r` argument, which represents each row
@@ -73,10 +70,7 @@ and `filter()` represent the most basic Flux query:
 
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-      r._measurement == "example-measurement" and
-      r._field == "example-field" and
-      r.tag == "example-tag"
-  )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement" and r.tag == "example-tag")
+    |> filter(fn: (r) => r._field == "example-field")
 ```
diff --git a/content/influxdb/v2.1/query-data/flux/rate.md b/content/influxdb/v2.1/query-data/flux/rate.md
index d930c6a36..32483ad17 100644
--- a/content/influxdb/v2.1/query-data/flux/rate.md
+++ b/content/influxdb/v2.1/query-data/flux/rate.md
@@ -36,7 +36,7 @@ to calculate the rate of change per unit of time between subsequent _non-null_ v
 
 ```js
 data
-  |> derivative(unit: 1s)
+    |> derivative(unit: 1s)
 ```
 
 By default, `derivative()` returns only positive derivative values and replaces negative values with _null_.
@@ -94,10 +94,7 @@ To return negative derivative values, set the `nonNegative` parameter to `false`
 **The following returns:**
 
 ```js
-|> derivative(
-  unit: 1m,
-  nonNegative: false
-)
+|> derivative(unit: 1m, nonNegative: false)
 ```
 
 | _time                | _value |
@@ -123,11 +120,7 @@ to calculate the average rate of change per window of time.
 import "experimental/aggregate"
 
 data
-  |> aggregate.rate(
-    every: 1m,
-    unit: 1s,
-    groupColumns: ["tag1", "tag2"]
-  )
+    |> aggregate.rate(every: 1m, unit: 1s, groupColumns: ["tag1", "tag2"])
 ```
 
 `aggregate.rate()` returns the average rate of change (as a [float](/{{< latest "flux" >}}/spec/types/#numeric-types))
@@ -156,10 +149,7 @@ Negative values are replaced with _null_.
 **The following returns:**
 
 ```js
-|> aggregate.rate(
-  every: 20m,
-  unit: 1m
-)
+|> aggregate.rate(every: 20m, unit: 1m)
 ```
 
 | _time                | _value |
diff --git a/content/influxdb/v2.1/query-data/flux/regular-expressions.md b/content/influxdb/v2.1/query-data/flux/regular-expressions.md
index b50287218..286e5afe8 100644
--- a/content/influxdb/v2.1/query-data/flux/regular-expressions.md
+++ b/content/influxdb/v2.1/query-data/flux/regular-expressions.md
@@ -56,24 +56,17 @@ It only keeps records for which the `cpu` is either `cpu0`, `cpu1`, or `cpu2`.
 
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -15m)
-  |> filter(fn: (r) =>
-    r._measurement == "cpu" and
-    r._field == "usage_user" and
-    r.cpu =~ /cpu[0-2]$/
-  )
+    |> range(start: -15m)
+    |> filter(fn: (r) => r._measurement == "cpu" and r.cpu =~ /cpu[0-2]$/)
 ```
 
 ### Use a regex to filter by field key
-The following example excludes records that do not have `_percent` in a field key.
+The following example includes records that have `_percent` in a field key.
 
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -15m)
-  |> filter(fn: (r) =>
-    r._measurement == "mem" and
-    r._field =~ /_percent/
-  )
+    |> range(start: -15m)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field =~ /_percent/)
 ```
 
 ### Drop columns matching a regex
@@ -81,9 +74,9 @@ The following example drops columns whose names do not being with `_`.
 
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -15m)
-  |> filter(fn: (r) => r._measurement == "mem")
-  |> drop(fn: (column) => column !~ /_.*/)
+    |> range(start: -15m)
+    |> filter(fn: (r) => r._measurement == "mem")
+    |> drop(fn: (column) => column !~ /_.*/)
 ```
 
 ## Helpful links
diff --git a/content/influxdb/v2.1/query-data/flux/scalar-values.md b/content/influxdb/v2.1/query-data/flux/scalar-values.md
index fbd785656..c258152e9 100644
--- a/content/influxdb/v2.1/query-data/flux/scalar-values.md
+++ b/content/influxdb/v2.1/query-data/flux/scalar-values.md
@@ -16,11 +16,11 @@ aliases:
   - /influxdb/v2.1/query-data/guides/scalar-values/
 list_code_example: |
   ```js
-  scalarValue = {
-    _record =
-      data
-        |> findRecord(fn: key => true, idx: 0)
-    return _record._value
+  scalarValue = (tables=<-) => {
+      _record = tables
+          |> findRecord(fn: (key) => true, idx: 0)
+
+      return _record._value
   }
   ```
 ---
@@ -67,10 +67,10 @@ _See [Sample data](#sample-data) below._
 
 ```js
 sampleData
-  |> findColumn(
-    fn: (key) => key._field == "temp" and key.location == "sfo",
-    column: "_value"
-  )
+    |> findColumn(
+        fn: (key) => key._field == "temp" and key.location == "sfo",
+        column: "_value",
+    )
 
 // Returns [65.1, 66.2, 66.3, 66.8]
 ```
@@ -85,10 +85,10 @@ _See [Sample data](#sample-data) below._
 
 ```js
 SFOTemps = sampleData
-  |> findColumn(
-    fn: (key) => key._field == "temp" and key.location == "sfo",
-    column: "_value"
-  )
+    |> findColumn(
+        fn: (key) => key._field == "temp" and key.location == "sfo",
+        column: "_value",
+    )
 
 SFOTemps
 // Returns [65.1, 66.2, 66.3, 66.8]
@@ -108,10 +108,10 @@ The function outputs a record with key-value pairs for each column.
 
 ```js
 sampleData
-  |> findRecord(
-    fn: (key) => key._field == "temp" and key.location == "sfo",
-    idx: 0
-  )
+    |> findRecord(
+        fn: (key) => key._field == "temp" and key.location == "sfo",
+        idx: 0,
+    )
 
 // Returns {
 //   _time:2019-11-11T12:00:00Z,
@@ -129,10 +129,10 @@ to reference keys in the record.
 
 ```js
 tempInfo = sampleData
-  |> findRecord(
-    fn: (key) => key._field == "temp" and key.location == "sfo",
-    idx: 0
-  )
+    |> findRecord(
+        fn: (key) => key._field == "temp" and key.location == "sfo",
+        idx: 0,
+    )
 
 tempInfo
 // Returns {
@@ -156,19 +156,17 @@ Create custom helper functions to extract scalar values from query output.
 ```js
 // Define a helper function to extract field values
 getFieldValue = (tables=<-, field) => {
-  extract = tables
-    |> findColumn(
-      fn: (key) => key._field == field,
-      column: "_value"
-    )
-  return extract[0]
+    extract = tables
+        |> findColumn(fn: (key) => key._field == field, column: "_value")
+
+    return extract[0]
 }
 
 // Use the helper function to define a variable
 lastJFKTemp = sampleData
-  |> filter(fn: (r) => r.location == "kjfk")
-  |> last()
-  |> getFieldValue(field: "temp")
+    |> filter(fn: (r) => r.location == "kjfk")
+    |> last()
+    |> getFieldValue(field: "temp")
 
 lastJFKTemp
 // Returns 71.2
@@ -178,18 +176,16 @@ lastJFKTemp
 ```js
 // Define a helper function to extract a row as a record
 getRow = (tables=<-, field, idx=0) => {
-  extract = tables
-    |> findRecord(
-      fn: (key) => true,
-      idx: idx
-    )
-  return extract
+    extract = tables
+        |> findRecord(fn: (key) => true, idx: idx)
+
+    return extract
 }
 
 // Use the helper function to define a variable
 lastReported = sampleData
-  |> last()
-  |> getRow(idx: 0)
+    |> last()
+    |> getRow(field: "temp")
 
 "The last location to report was ${lastReported.location}.
 The temperature was ${string(v: lastReported._value)}°F."
diff --git a/content/influxdb/v2.1/query-data/flux/sort-limit.md b/content/influxdb/v2.1/query-data/flux/sort-limit.md
index a03789ef0..7598bad11 100644
--- a/content/influxdb/v2.1/query-data/flux/sort-limit.md
+++ b/content/influxdb/v2.1/query-data/flux/sort-limit.md
@@ -34,13 +34,10 @@ If you're just getting started with Flux queries, check out the following:
 The following example orders system uptime first by region, then host, then value.
 
 ```js
-from(bucket:"example-bucket")
-  |> range(start:-12h)
-  |> filter(fn: (r) =>
-    r._measurement == "system" and
-    r._field == "uptime"
-  )
-  |> sort(columns:["region", "host", "_value"])
+from(bucket: "example-bucket")
+    |> range(start: -12h)
+    |> filter(fn: (r) => r._measurement == "system" and r._field == "uptime")
+    |> sort(columns: ["region", "host", "_value"])
 ```
 
 The [`limit()` function](/{{< latest "flux" >}}/stdlib/universe/limit)
@@ -49,8 +46,8 @@ The following example shows up to 10 records from the past hour.
 
 ```js
 from(bucket:"example-bucket")
-  |> range(start:-1h)
-  |> limit(n:10)
+    |> range(start:-1h)
+    |> limit(n:10)
 ```
 
 You can use `sort()` and `limit()` together to show the top N records.
@@ -58,14 +55,11 @@ The example below returns the 10 top system uptime values sorted first by
 region, then host, then value.
 
 ```js
-from(bucket:"example-bucket")
-  |> range(start:-12h)
-  |> filter(fn: (r) =>
-    r._measurement == "system" and
-    r._field == "uptime"
-  )
-  |> sort(columns:["region", "host", "_value"])
-  |> limit(n:10)
+from(bucket: "example-bucket")
+    |> range(start: -12h)
+    |> filter(fn: (r) => r._measurement == "system" and r._field == "uptime")
+    |> sort(columns: ["region", "host", "_value"])
+    |> limit(n: 10)
 ```
 
 You now have created a Flux query that sorts and limits data.
diff --git a/content/influxdb/v2.1/query-data/flux/sql.md b/content/influxdb/v2.1/query-data/flux/sql.md
index 540481c08..c10221eb9 100644
--- a/content/influxdb/v2.1/query-data/flux/sql.md
+++ b/content/influxdb/v2.1/query-data/flux/sql.md
@@ -21,9 +21,9 @@ list_code_example: |
   import "sql"
 
   sql.from(
-    driverName: "postgres",
-    dataSourceName: "postgresql://user:password@localhost",
-    query: "SELECT * FROM example_table"
+      driverName: "postgres",
+      dataSourceName: "postgresql://user:password@localhost",
+      query: "SELECT * FROM example_table",
   )
   ```
 ---
@@ -70,9 +70,9 @@ To query a SQL data source:
 import "sql"
 
 sql.from(
-  driverName: "postgres",
-  dataSourceName: "postgresql://user:password@localhost",
-  query: "SELECT * FROM example_table"
+    driverName: "postgres",
+    dataSourceName: "postgresql://user:password@localhost",
+    query: "SELECT * FROM example_table",
 )
 ```
 {{% /code-tab-content %}}
@@ -82,9 +82,9 @@ sql.from(
 import "sql"
 
 sql.from(
-  driverName: "mysql",
-  dataSourceName: "user:password@tcp(localhost:3306)/db",
-  query: "SELECT * FROM example_table"
+    driverName: "mysql",
+    dataSourceName: "user:password@tcp(localhost:3306)/db",
+    query: "SELECT * FROM example_table",
 )
 ```
 {{% /code-tab-content %}}
@@ -94,9 +94,9 @@ sql.from(
 import "sql"
 
 sql.from(
-  driverName: "snowflake",
-  dataSourceName: "user:password@account/db/exampleschema?warehouse=wh",
-  query: "SELECT * FROM example_table"
+    driverName: "snowflake",
+    dataSourceName: "user:password@account/db/exampleschema?warehouse=wh",
+    query: "SELECT * FROM example_table",
 )
 ```
 {{% /code-tab-content %}}
@@ -110,9 +110,9 @@ sql.from(
 import "sql"
 
 sql.from(
-  driverName: "sqlite3",
-  dataSourceName: "file:/path/to/test.db?cache=shared&mode=ro",
-  query: "SELECT * FROM example_table"
+    driverName: "sqlite3",
+    dataSourceName: "file:/path/to/test.db?cache=shared&mode=ro",
+    query: "SELECT * FROM example_table",
 )
 ```
 {{% /code-tab-content %}}
@@ -122,9 +122,9 @@ sql.from(
 import "sql"
 
 sql.from(
-  driverName: "sqlserver",
-  dataSourceName: "sqlserver://user:password@localhost:1234?database=examplebdb",
-  query: "GO SELECT * FROM Example.Table"
+    driverName: "sqlserver",
+    dataSourceName: "sqlserver://user:password@localhost:1234?database=examplebdb",
+    query: "GO SELECT * FROM Example.Table",
 )
 ```
 
@@ -136,9 +136,9 @@ see [SQL Server ADO authentication](/{{< latest "flux" >}}/stdlib/sql/from/#sql-
 ```js
 import "sql"
 sql.from(
-  driverName: "awsathena",
-  dataSourceName: "s3://myorgqueryresults/?accessID=12ab34cd56ef&region=region-name&secretAccessKey=y0urSup3rs3crEtT0k3n",
-  query: "GO SELECT * FROM Example.Table"
+    driverName: "awsathena",
+    dataSourceName: "s3://myorgqueryresults/?accessID=12ab34cd56ef&region=region-name&secretAccessKey=y0urSup3rs3crEtT0k3n",
+    query: "GO SELECT * FROM Example.Table",
 )
 ```
 
@@ -149,9 +149,9 @@ see [Athena connection string](/{{< latest "flux" >}}/stdlib/sql/from/#athena-co
 ```js
 import "sql"
 sql.from(
-  driverName: "bigquery",
-  dataSourceName: "bigquery://projectid/?apiKey=mySuP3r5ecR3tAP1K3y",
-  query: "SELECT * FROM exampleTable"
+    driverName: "bigquery",
+    dataSourceName: "bigquery://projectid/?apiKey=mySuP3r5ecR3tAP1K3y",
+    query: "SELECT * FROM exampleTable",
 )
 ```
 
@@ -178,15 +178,15 @@ import "sql"
 
 // Query data from PostgreSQL
 sensorInfo = sql.from(
-  driverName: "postgres",
-  dataSourceName: "postgresql://localhost?sslmode=disable",
-  query: "SELECT * FROM sensors"
+    driverName: "postgres",
+    dataSourceName: "postgresql://localhost?sslmode=disable",
+    query: "SELECT * FROM sensors",
 )
 
 // Query data from InfluxDB
 sensorMetrics = from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) => r._measurement == "airSensors")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "airSensors")
 
 // Join InfluxDB query results with PostgreSQL query results
 join(tables: {metric: sensorMetrics, info: sensorInfo}, on: ["sensor_id"])
@@ -205,9 +205,9 @@ sql.from(
     driverName: "postgres",
     dataSourceName: "postgresql://localhost?sslmode=disable",
     query: "SELECT * FROM sensors"
-  )
-  |> rename(columns: {location: "_value"})
-  |> keep(columns: ["_value"])
+)
+    |> rename(columns: {location: "_value"})
+    |> keep(columns: ["_value"])
 ```
 
 Use the variable to manipulate queries in your dashboards.
@@ -283,9 +283,9 @@ POSTGRES_USER = secrets.get(key: "POSTGRES_USER")
 POSTGRES_PASS = secrets.get(key: "POSTGRES_PASS")
 
 sql.from(
-  driverName: "postgres",
-  dataSourceName: "postgresql://${POSTGRES_USER}:${POSTGRES_PASS}@${POSTGRES_HOST}",
-  query: "SELECT * FROM sensors"
+    driverName: "postgres",
+    dataSourceName: "postgresql://${POSTGRES_USER}:${POSTGRES_PASS}@${POSTGRES_HOST}",
+    query: "SELECT * FROM sensors",
 )
 ```
 
@@ -324,16 +324,10 @@ Sample sensor information is stored in PostgreSQL.
     ```js
     import "influxdata/influxdb/sample"
 
-    option task = {
-      name: "Collect sample air sensor data",
-      every: 15m
-    }
+    option task = {name: "Collect sample air sensor data", every: 15m}
 
     sample.data(set: "airSensor")
-      |> to(
-        org: "example-org",
-        bucket: "example-bucket"
-      )
+        |> to(org: "example-org", bucket: "example-bucket")
     ```
 
 3.  [Query your target bucket](/influxdb/v2.1/query-data/execute-queries/) after
@@ -341,8 +335,8 @@ Sample sensor information is stored in PostgreSQL.
 
     ```js
     from(bucket: "example-bucket")
-       |> range(start: -1m)
-       |> filter(fn: (r) => r._measurement == "airSensors")
+        |> range(start: -1m)
+        |> filter(fn: (r) => r._measurement == "airSensors")
     ```
 
 #### Import the sample sensor information
diff --git a/content/influxdb/v2.1/query-data/flux/window-aggregate.md b/content/influxdb/v2.1/query-data/flux/window-aggregate.md
index 559699d20..2d8a7c2c4 100644
--- a/content/influxdb/v2.1/query-data/flux/window-aggregate.md
+++ b/content/influxdb/v2.1/query-data/flux/window-aggregate.md
@@ -44,12 +44,9 @@ The following example queries the memory usage of the host machine.
 
 ```js
 dataSet = from(bucket: "example-bucket")
-  |> range(start: -5m)
-  |> filter(fn: (r) =>
-    r._measurement == "mem" and
-    r._field == "used_percent"
-  )
-  |> drop(columns: ["host"])
+    |> range(start: -5m)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+    |> drop(columns: ["host"])
 ```
 
 {{% note %}}
@@ -110,7 +107,7 @@ set into one minute windows.
 
 ```js
 dataSet
-  |> window(every: 1m)
+    |> window(every: 1m)
 ```
 
 {{% note %}}
@@ -202,8 +199,8 @@ to output the average of each window:
 
 ```js
 dataSet
-  |> window(every: 1m)
-  |> mean()
+    |> window(every: 1m)
+    |> mean()
 ```
 
 {{% truncate %}}
@@ -266,9 +263,9 @@ duplicate either the `_start` or `_stop` column as a new `_time` column.
 
 ```js
 dataSet
-  |> window(every: 1m)
-  |> mean()
-  |> duplicate(column: "_stop", as: "_time")
+    |> window(every: 1m)
+    |> mean()
+    |> duplicate(column: "_stop", as: "_time")
 ```
 
 {{% truncate %}}
@@ -317,10 +314,10 @@ Use the `window()` function to "unwindow" your data into a single infinite (`inf
 
 ```js
 dataSet
-  |> window(every: 1m)
-  |> mean()
-  |> duplicate(column: "_stop", as: "_time")
-  |> window(every: inf)
+    |> window(every: 1m)
+    |> mean()
+    |> duplicate(column: "_stop", as: "_time")
+    |> window(every: inf)
 ```
 
 {{% note %}}
@@ -357,5 +354,5 @@ The following Flux query will return the same results:
 ###### aggregateWindow function
 ```js
 dataSet
-  |> aggregateWindow(every: 1m, fn: mean)
+    |> aggregateWindow(every: 1m, fn: mean)
 ```
diff --git a/content/influxdb/v2.1/query-data/get-started/query-influxdb.md b/content/influxdb/v2.1/query-data/get-started/query-influxdb.md
index 1b7d7c26a..076249914 100644
--- a/content/influxdb/v2.1/query-data/get-started/query-influxdb.md
+++ b/content/influxdb/v2.1/query-data/get-started/query-influxdb.md
@@ -48,11 +48,11 @@ or **absolute** using [timestamps](/{{< latest "flux" >}}/data-types/basic/time/
 ```js
 // Relative time range with start only. Stop defaults to now.
 from(bucket:"example-bucket")
-  |> range(start: -1h)
+    |> range(start: -1h)
 
 // Relative time range with start and stop
 from(bucket:"example-bucket")
-  |> range(start: -1h, stop: -10m)
+    |> range(start: -1h, stop: -10m)
 ```
 
 {{% note %}}
@@ -62,7 +62,7 @@ Relative ranges are relative to "now."
 ###### Example absolute time range
 ```js
 from(bucket:"example-bucket")
-  |> range(start: 2021-01-01T00:00:00Z, stop: 2021-01-01T12:00:00Z)
+    |> range(start: 2021-01-01T00:00:00Z, stop: 2021-01-01T12:00:00Z)
 ```
 
 #### Use the following:
@@ -70,7 +70,7 @@ For this guide, use the relative time range, `-15m`, to limit query results to d
 
 ```js
 from(bucket:"example-bucket")
-  |> range(start: -15m)
+    |> range(start: -15m)
 ```
 
 ## 3. Filter your data
@@ -103,27 +103,19 @@ For this example, filter by the `cpu` measurement, `usage_system` field, and
 `cpu-total` tag value:
 
 ```js
-from(bucket:"example-bucket")
-  |> range(start: -15m)
-  |> filter(fn: (r) =>
-    r._measurement == "cpu" and
-    r._field == "usage_system" and
-    r.cpu == "cpu-total"
-  )
+from(bucket: "example-bucket")
+    |> range(start: -15m)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_system" and r.cpu == "cpu-total")
 ```
 
 ## 4. Yield your queried data
 [`yield()`](/{{< latest "flux" >}}/stdlib/universe/yield/) outputs the result of the query.
 
 ```js
-from(bucket:"example-bucket")
-  |> range(start: -15m)
-  |> filter(fn: (r) =>
-    r._measurement == "cpu" and
-    r._field == "usage_system" and
-    r.cpu == "cpu-total"
-  )
-  |> yield()
+from(bucket: "example-bucket")
+    |> range(start: -15m)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_system" and r.cpu == "cpu-total")
+    |> yield()
 ```
 
 Flux automatically assumes a `yield()` function at
diff --git a/content/influxdb/v2.1/query-data/get-started/transform-data.md b/content/influxdb/v2.1/query-data/get-started/transform-data.md
index 76ddfaadf..e2d756191 100644
--- a/content/influxdb/v2.1/query-data/get-started/transform-data.md
+++ b/content/influxdb/v2.1/query-data/get-started/transform-data.md
@@ -30,13 +30,9 @@ Use the query built in the previous [Query data from InfluxDB](/influxdb/v2.1/qu
 guide, but update the range to pull data from the last hour:
 
 ```js
-from(bucket:"example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "cpu" and
-    r._field == "usage_system" and
-    r.cpu == "cpu-total"
-  )
+from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_system" and r.cpu == "cpu-total")
 ```
 
 ## Flux functions
@@ -70,14 +66,10 @@ including **calendar months (`1mo`)** and **years (`1y`)**.
 For this example, window data in five minute intervals (`5m`).
 
 ```js
-from(bucket:"example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "cpu" and
-    r._field == "usage_system" and
-    r.cpu == "cpu-total"
-  )
-  |> window(every: 5m)
+from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_system" and r.cpu == "cpu-total")
+    |> window(every: 5m)
 ```
 
 As data is gathered into windows of time, each window is output as its own table.
@@ -90,15 +82,11 @@ Flux aggregate functions take the `_value`s in each table and aggregate them in
 Use the [`mean()` function](/{{< latest "flux" >}}/stdlib/universe/mean) to average the `_value`s of each table.
 
 ```js
-from(bucket:"example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "cpu" and
-    r._field == "usage_system" and
-    r.cpu == "cpu-total"
-  )
-  |> window(every: 5m)
-  |> mean()
+from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_system" and r.cpu == "cpu-total")
+    |> window(every: 5m)
+    |> mean()
 ```
 
 As rows in each window are aggregated, their output table contains only a single row with the aggregate value.
@@ -117,16 +105,12 @@ To add one, use the [`duplicate()` function](/{{< latest "flux" >}}/stdlib/unive
 to duplicate the `_stop` column as the `_time` column for each windowed table.
 
 ```js
-from(bucket:"example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "cpu" and
-    r._field == "usage_system" and
-    r.cpu == "cpu-total"
-  )
-  |> window(every: 5m)
-  |> mean()
-  |> duplicate(column: "_stop", as: "_time")
+from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_system" and r.cpu == "cpu-total")
+    |> window(every: 5m)
+    |> mean()
+    |> duplicate(column: "_stop", as: "_time")
 ```
 
 ## Unwindow aggregate tables
@@ -135,17 +119,13 @@ Use the `window()` function with the `every: inf` parameter to gather all points
 into a single, infinite window.
 
 ```js
-from(bucket:"example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "cpu" and
-    r._field == "usage_system" and
-    r.cpu == "cpu-total"
-  )
-  |> window(every: 5m)
-  |> mean()
-  |> duplicate(column: "_stop", as: "_time")
-  |> window(every: inf)
+from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_system" and r.cpu == "cpu-total")
+    |> window(every: 5m)
+    |> mean()
+    |> duplicate(column: "_stop", as: "_time")
+    |> window(every: inf)
 ```
 
 Once ungrouped and combined into a single table, the aggregate data points will appear connected in your visualization.
@@ -161,14 +141,10 @@ The same operation performed in this guide can be accomplished using
 [`aggregateWindow()`](/{{< latest "flux" >}}/stdlib/universe/aggregatewindow).
 
 ```js
-from(bucket:"example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "cpu" and
-    r._field == "usage_system" and
-    r.cpu == "cpu-total"
-  )
-  |> aggregateWindow(every: 5m, fn: mean)
+from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_system" and r.cpu == "cpu-total")
+    |> aggregateWindow(every: 5m, fn: mean)
 ```
 
 ## Congratulations!
diff --git a/content/influxdb/v2.1/query-data/optimize-queries.md b/content/influxdb/v2.1/query-data/optimize-queries.md
index b967cdac7..53ba48582 100644
--- a/content/influxdb/v2.1/query-data/optimize-queries.md
+++ b/content/influxdb/v2.1/query-data/optimize-queries.md
@@ -31,37 +31,35 @@ subsequent operations there.
 Most pushdowns are supported when querying an InfluxDB {{< current-version >}} or InfluxDB Cloud data source.
 As shown in the following table, a handful of pushdowns are not supported in InfluxDB {{< current-version >}}.
 
-| Functions                      | InfluxDB {{< current-version >}} | InfluxDB Cloud       |
-|:---------                      |:------------:                    |:--------------:      |
-| **count()**                    | {{< icon "check" >}}             | {{< icon "check" >}} |
-| **drop()**                     | {{< icon "check" >}}             | {{< icon "check" >}} |
-| **duplicate()**                | {{< icon "check" >}}             | {{< icon "check" >}} |
-| **filter()** {{% req " \*" %}} | {{< icon "check" >}}             | {{< icon "check" >}} |
-| **fill()**                     | {{< icon "check" >}}             | {{< icon "check" >}} |
-| **first()**                    | {{< icon "check" >}}             | {{< icon "check" >}} |
-| **keep()**                     | {{< icon "check" >}}             | {{< icon "check" >}} |
-| **last()**                     | {{< icon "check" >}}             | {{< icon "check" >}} |
-| **max()**                      | {{< icon "check" >}}             | {{< icon "check" >}} |
-| **mean()**                     | {{< icon "check" >}}             | {{< icon "check" >}} |
-| **min()**                      | {{< icon "check" >}}             | {{< icon "check" >}} |
-| **range()**                    | {{< icon "check" >}}             | {{< icon "check" >}} |
-| **rename()**                   | {{< icon "check" >}}             | {{< icon "check" >}} |
-| **sum()**                      | {{< icon "check" >}}             | {{< icon "check" >}} |
-| **window()**                   | {{< icon "check" >}}             | {{< icon "check" >}} |
-| _Function combinations_        |                                  |                      |
-| **group()** \|> **count()**    |                                  | {{< icon "check" >}} |
-| **group()** \|> **first()**    |                                  | {{< icon "check" >}} |
-| **group()** \|> **last()**     |                                  | {{< icon "check" >}} |
-| **group()** \|> **max()**      |                                  | {{< icon "check" >}} |
-| **group()** \|> **min()**      |                                  | {{< icon "check" >}} |
-| **group()** \|> **sum()**      |                                  | {{< icon "check" >}} |
-| **sort()** \|> **limit()**     |                                  | {{< icon "check" >}} |
-| **window()** \|> **count()**   | {{< icon "check" >}}             | {{< icon "check" >}} |
-| **window()** \|> **first()**   | {{< icon "check" >}}             | {{< icon "check" >}} |
-| **window()** \|> **last()**    | {{< icon "check" >}}             | {{< icon "check" >}} |
-| **window()** \|> **max()**     | {{< icon "check" >}}             | {{< icon "check" >}} |
-| **window()** \|> **min()**     | {{< icon "check" >}}             | {{< icon "check" >}} |
-| **window()** \|> **sum()**     | {{< icon "check" >}}             | {{< icon "check" >}} |
+| Functions                      | InfluxDB {{< current-version keep=true >}} |    InfluxDB Cloud    |
+| :----------------------------- | :----------------------------------------: | :------------------: |
+| **count()**                    |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| **duplicate()**                |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| **filter()** {{% req " \*" %}} |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| **fill()**                     |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| **first()**                    |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| **last()**                     |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| **max()**                      |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| **mean()**                     |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| **min()**                      |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| **range()**                    |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| **rename()**                   |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| **sum()**                      |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| **window()**                   |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| _Function combinations_        |                                            |                      |
+| **group()** \|> **count()**    |                                            | {{< icon "check" >}} |
+| **group()** \|> **first()**    |                                            | {{< icon "check" >}} |
+| **group()** \|> **last()**     |                                            | {{< icon "check" >}} |
+| **group()** \|> **max()**      |                                            | {{< icon "check" >}} |
+| **group()** \|> **min()**      |                                            | {{< icon "check" >}} |
+| **group()** \|> **sum()**      |                                            | {{< icon "check" >}} |
+| **sort()** \|> **limit()**     |                                            | {{< icon "check" >}} |
+| **window()** \|> **count()**   |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| **window()** \|> **first()**   |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| **window()** \|> **last()**    |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| **window()** \|> **max()**     |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| **window()** \|> **min()**     |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| **window()** \|> **sum()**     |            {{< icon "check" >}}            | {{< icon "check" >}} |
 
 {{% caption %}}
 {{< req "\*" >}} **filter()** only pushes down when all parameter values are static.
@@ -75,13 +73,13 @@ subsequent operations there.
 ##### Pushdown functions in use
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -1h)                       //
-  |> filter(fn: (r) => r.sensor == "abc123") //
-  |> group(columns: ["_field", "host"])      // Pushed to the data source
-  |> aggregateWindow(every: 5m, fn: max)     //
-  |> filter(fn: (r) => r._value >= 90.0)     //
+    |> range(start: -1h)                       //
+    |> filter(fn: (r) => r.sensor == "abc123") //
+    |> group(columns: ["_field", "host"])      // Pushed to the data source
+    |> aggregateWindow(every: 5m, fn: max)     //
+    |> filter(fn: (r) => r._value >= 90.0)     //
 
-  |> top(n: 10)                              // Run in memory
+    |> top(n: 10)                              // Run in memory
 ```
 
 ### Avoid processing filters inline
@@ -98,8 +96,8 @@ to the underlying data source and loads all data returned from `range()` into me
 
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -1h)                      
-  |> filter(fn: (r) => r.region == v.provider + v.region)
+    |> range(start: -1h)                      
+    |> filter(fn: (r) => r.region == v.provider + v.region)
 ```
 
 To dynamically set filters and maintain the pushdown ability of the `filter()` function,
@@ -109,8 +107,8 @@ use variables to define filter values outside of `filter()`:
 region = v.provider + v.region
 
 from(bucket: "example-bucket")
-  |> range(start: -1h)                      
-  |> filter(fn: (r) => r.region == region)
+    |> range(start: -1h)                      
+    |> filter(fn: (r) => r.region == region)
 ```
 
 ## Avoid short window durations
@@ -150,17 +148,17 @@ The following queries are functionally the same, but using `set()` is more perfo
 
 ```js
 data
-  |> map(fn: (r) => ({ r with foo: "bar" }))
+    |> map(fn: (r) => ({ r with foo: "bar" }))
 
 // Recommended
 data
-  |> set(key: "foo", value: "bar")
+    |> set(key: "foo", value: "bar")
 ```
 
 #### Dynamically set a column value using existing row data
 ```js
 data
-  |> map(fn: (r) => ({ r with foo: r.bar }))
+    |> map(fn: (r) => ({ r with foo: r.bar }))
 ```
 
 ## Balance time range and data precision
diff --git a/content/influxdb/v2.1/reference/cli/influx/_index.md b/content/influxdb/v2.1/reference/cli/influx/_index.md
index 8267a3c0c..ef281b7eb 100644
--- a/content/influxdb/v2.1/reference/cli/influx/_index.md
+++ b/content/influxdb/v2.1/reference/cli/influx/_index.md
@@ -61,7 +61,7 @@ influx [command]
 ## Commands
 
 | Command                                                             | Description                                                                |
-| :------------------------------------------------------------------ | :------------------------------------------------------------------------- |
+|:--------------------------------------------------------------------|:---------------------------------------------------------------------------|
 | [apply](/influxdb/v2.1/reference/cli/influx/apply/)                 | Apply an InfluxDB template                                                 |
 | [auth](/influxdb/v2.1/reference/cli/influx/auth/)                   | API token management commands                                              |
 | [backup](/influxdb/v2.1/reference/cli/influx/backup/)               | Back up data _(InfluxDB OSS only)_                                         |
@@ -76,6 +76,8 @@ influx [command]
 | [org](/influxdb/v2.1/reference/cli/influx/org/)                     | Organization management commands                                           |
 | [ping](/influxdb/v2.1/reference/cli/influx/ping/)                   | Check the InfluxDB `/health` endpoint                                      |
 | [query](/influxdb/v2.1/reference/cli/influx/query/)                 | Execute a Flux query                                                       |
+| [remote](/influxdb/v2.1/reference/cli/influx/remote/)               | Manage remote InfluxDB connections                                         |
+| [replicate](/influxdb/v2.1/reference/cli/influx/resplicate/)        | Manage InfluxDB replication streams                                        |
 | [restore](/influxdb/v2.1/reference/cli/influx/restore/)             | Restore backup data _(InfluxDB OSS only)_                                  |
 | [secret](/influxdb/v2.1/reference/cli/influx/secret/)               | Manage secrets                                                             |
 | [setup](/influxdb/v2.1/reference/cli/influx/setup/)                 | Create default username, password, org, bucket, etc. _(InfluxDB OSS only)_ |
diff --git a/content/influxdb/v2.1/reference/cli/influx/bucket/create.md b/content/influxdb/v2.1/reference/cli/influx/bucket/create.md
index 0228ba0d7..e17bca387 100644
--- a/content/influxdb/v2.1/reference/cli/influx/bucket/create.md
+++ b/content/influxdb/v2.1/reference/cli/influx/bucket/create.md
@@ -46,8 +46,17 @@ influx bucket create [flags]
 | `-t` | `--token`                | API token                                                                                                                                                                   |   string   | `INFLUX_TOKEN`        |
 
 {{% note %}}
-Valid `--retention` units are nanoseconds (`ns`), microseconds (`us` or `µs`),
-milliseconds (`ms`), seconds (`s`), minutes (`m`), hours (`h`), days (`d`), and weeks (`w`).
+#### Retention periods
+The minimum retention period is **one hour**. Valid `--retention` units:
+
+- nanoseconds (`ns`)
+- microseconds (`us` or `µs`)
+- milliseconds (`ms`)
+- seconds (`s`)
+- minutes (`m`)
+- hours (`h`)
+- days (`d`)
+- weeks (`w`)
 {{% /note %}}
 
 ## Examples
diff --git a/content/influxdb/v2.1/reference/cli/influx/bucket/update.md b/content/influxdb/v2.1/reference/cli/influx/bucket/update.md
index 836c68ca3..9d3030cfb 100644
--- a/content/influxdb/v2.1/reference/cli/influx/bucket/update.md
+++ b/content/influxdb/v2.1/reference/cli/influx/bucket/update.md
@@ -41,8 +41,17 @@ influx bucket update [flags]
 | `-t` | `--token`                | API token                                                             | string     | `INFLUX_TOKEN`        |
 
 {{% note %}}
-Valid `--retention` units are nanoseconds (`ns`), microseconds (`us` or `µs`),
-milliseconds (`ms`), seconds (`s`), minutes (`m`), hours (`h`), days (`d`), and weeks (`w`).
+#### Retention periods
+The minimum retention period is **one hour**. Valid `--retention` units:
+
+- nanoseconds (`ns`)
+- microseconds (`us` or `µs`)
+- milliseconds (`ms`)
+- seconds (`s`)
+- minutes (`m`)
+- hours (`h`)
+- days (`d`)
+- weeks (`w`)
 {{% /note %}}
 
 ## Examples
diff --git a/content/influxdb/v2.1/reference/cli/influx/query/_index.md b/content/influxdb/v2.1/reference/cli/influx/query/_index.md
index d5b4248f3..ae275ca63 100644
--- a/content/influxdb/v2.1/reference/cli/influx/query/_index.md
+++ b/content/influxdb/v2.1/reference/cli/influx/query/_index.md
@@ -33,7 +33,7 @@ drop columns such as `_start` and `_stop` to optimize the download file size.
 
 ```js
 // ...
-  |> drop(columns: ["_start", "_stop"])
+    |> drop(columns: ["_start", "_stop"])
 ```
 {{% /note %}}
 
diff --git a/content/influxdb/v2.1/reference/cli/influx/restore/index.md b/content/influxdb/v2.1/reference/cli/influx/restore/_index.md
similarity index 100%
rename from content/influxdb/v2.1/reference/cli/influx/restore/index.md
rename to content/influxdb/v2.1/reference/cli/influx/restore/_index.md
diff --git a/content/influxdb/v2.1/reference/cli/influxd/recovery/auth/list.md b/content/influxdb/v2.1/reference/cli/influxd/recovery/auth/list.md
index f6c2fe605..0a79f0e57 100644
--- a/content/influxdb/v2.1/reference/cli/influxd/recovery/auth/list.md
+++ b/content/influxdb/v2.1/reference/cli/influxd/recovery/auth/list.md
@@ -9,7 +9,7 @@ menu:
 weight: 401
 ---
 
-The `influxd recovery org list` command lists authorizations stored on disk and 
+The `influxd recovery auth list` command lists authorizations stored on disk and 
 outputs data associated with each authorization.
 
 {{% note %}}
@@ -25,4 +25,4 @@ influxd recovery auth list [flags]
 | Flag |               | Description                                                    | Input Type |
 | :--- | :------------ | :------------------------------------------------------------- | :--------: |
 |      | `--bolt-path` | Path to the BoltDB file (default `~/.influxdbv2/influxd.bolt`) |   string   |
-| `-h` | `--help`      | Help for `list`                                                |            |
\ No newline at end of file
+| `-h` | `--help`      | Help for `list`                                                |            |
diff --git a/content/influxdb/v2.1/reference/glossary.md b/content/influxdb/v2.1/reference/glossary.md
index f555e527d..c421c1aa5 100644
--- a/content/influxdb/v2.1/reference/glossary.md
+++ b/content/influxdb/v2.1/reference/glossary.md
@@ -804,8 +804,9 @@ In a batch of data, points that InfluxDB couldn't write to a bucket.
 Field type conflicts are a common cause of rejected points.
 
 ### retention period
-The duration of time that a bucket retains data.
-Points with timestamps older than their bucket's retention period are dropped.
+The [duration](#duration) of time that a bucket retains data.
+InfluxDB drops points with timestamps older than their bucket's retention period.
+The minimum retention period is **one hour**.
 
 Related entries: [bucket](#bucket), [shard group duration](#shard-group-duration)
 
@@ -1065,6 +1066,11 @@ For more information, see [Process Data with InfluxDB tasks](/influxdb/v2.1/proc
 
 Related entries: [function](#function)
 
+### technical preview
+
+A new feature released to gather feedback from customers and the InfluxDB community. Send feedback to InfluxData via 
+[Community Slack](https://influxcommunity.slack.com/) or our [Community Site](https://community.influxdata.com/).
+
 ### Telegraf
 
 A plugin-driven agent that collects, processes, aggregates, and writes metrics.
diff --git a/content/influxdb/v2.1/reference/internals/data-retention.md b/content/influxdb/v2.1/reference/internals/data-retention.md
new file mode 100644
index 000000000..898feeecb
--- /dev/null
+++ b/content/influxdb/v2.1/reference/internals/data-retention.md
@@ -0,0 +1,80 @@
+---
+title: Data retention in InfluxDB
+description: >
+  The InfluxDB retention service checks for and removes data with timestamps beyond
+  the defined retention period of the bucket the data is stored in.
+weight: 103
+menu:
+  influxdb_2_1_ref:
+    name: Data retention
+    parent: InfluxDB internals
+influxdb/v2.1/tags: [storage, internals]
+related: 
+  - /influxdb/v2.1/reference/internals/shards/
+  - /influxdb/v2.1/reference/internals/storage-engine/
+---
+
+The **InfluxDB retention enforcement service** checks for and removes data with
+timestamps beyond the defined retention period of the
+[bucket](/influxdb/v2.1/reference/glossary/#bucket) the data is stored in.
+This service is designed to automatically delete "expired" data and optimize disk
+usage without any user intervention.
+
+By default, the retention enforcement service runs every 30 minutes.
+You can
+configure this interval with the
+[`storage-retention-check-interval`](/influxdb/v2.1/reference/config-options/#storage-retention-check-interval)
+configuration option.
+
+- [Bucket retention period](#bucket-retention-period)
+- [Shard group duration](#shard-group-duration)
+- [When does data actually get deleted?](#when-does-data-actually-get-deleted)
+
+## Bucket retention period
+A **bucket retention period** is the duration of time that a bucket retains data.
+Retention periods can be as short as an hour or infinite.
+[Points](/influxdb/v2.1/reference/glossary/#point) in a bucket with timestamps
+beyond the defined retention period (relative to now) are _eligible_ for deletion.
+
+## Shard group duration
+InfluxDB stores data on disk in [shards](/influxdb/v2.1/reference/glossary/#shard).
+Each shard belongs to a shard group and each shard group has a shard group duration.
+The **shard group duration** defines the duration of time that each
+shard in the shard group covers.
+Each shard contains only points with timestamps in specific a time range defined
+by the shard group duration.
+
+By default, shard group durations are set automatically based on the bucket retention
+period, but can also be explicitly defined when creating or updating a bucket.
+
+_For more information, see [InfluxDB shard group duration](/influxdb/v2.1/reference/internals/shards/#shard-group-duration)._
+
+{{% note %}}
+#### View bucket retention periods and shard group durations
+Use the [`influx bucket list` command](/influxdb/v2.1/reference/cli/influx/bucket/list/)
+to view the retention period and shard group duration of buckets in your organization.
+{{% /note %}}
+
+## When does data actually get deleted?
+The InfluxDB retention enforcement service runs at regular intervals and deletes
+[shard groups](/influxdb/v2.1/reference/internals/shards/#shard-groups), not individual points.
+The service will only delete a shard group when the entire time range covered by
+the shard group is beyond the bucket retention period.
+
+{{% note %}}
+#### Data is queryable until deleted
+Even though data may be older than the specified bucket retention period,
+it is queryable until removed by the retention enforcement service.
+{{% /note %}}
+
+To calculate the possible time data will persist before being deleted:
+
+- **minimum**: `bucket-retention-period`
+- **maximum** `bucket-retention-period + shard-group-duration`
+
+For example, if your bucket retention period is three days (`3d`) and your 
+shard group duration is one day (`1d`), the retention enforcement service
+deletes all shard groups with data that is **three to four days old** the next
+time the service runs.
+
+{{< html-diagram/data-retention >}}
diff --git a/content/influxdb/v2.1/reference/internals/metrics.md b/content/influxdb/v2.1/reference/internals/metrics.md
new file mode 100644
index 000000000..07c8bf64c
--- /dev/null
+++ b/content/influxdb/v2.1/reference/internals/metrics.md
@@ -0,0 +1,1262 @@
+---
+title: InfluxDB OSS metrics
+description: >
+ Get metrics about the workload performance of an InfluxDB OSS instance.
+menu:
+ influxdb_2_1_ref:
+   parent: InfluxDB internals
+   name: Metrics
+influxdb/v2.1/tags: [cpu, memory, metrics, performance, Prometheus, usage]
+---
+Get metrics about the workload performance of an InfluxDB OSS instance.
+
+InfluxDB OSS exposes a `/metrics` endpoint that returns
+performance, resource, and usage metrics formatted in the [Prometheus plain-text exposition format](https://prometheus.io/docs/instrumenting/exposition_formats).
+
+[{{< api-endpoint method="GET" endpoint="http://localhost:8086/metrics" >}}](/influxdb/v2.1/api/#operation/GetMetrics)
+
+Metrics contain a name, an optional set of key-value pairs, and a value.
+
+The following descriptors precede each metric:
+
+- `HELP`: description of the metric
+- `TYPE`: [Prometheus metric type](https://prometheus.io/docs/concepts/metric_types/) (`counter`, `gauge`, `histogram`, or `summary`)
+
+#### Example
+
+```sh
+# HELP go_info Information about the Go environment.
+# TYPE go_info gauge
+go_info{version="go1.17"} 1
+# HELP go_memstats_alloc_bytes Number of bytes allocated and still in use.
+# TYPE go_memstats_alloc_bytes gauge
+go_memstats_alloc_bytes 2.27988488e+08
+# HELP go_memstats_alloc_bytes_total Total number of bytes allocated, even if freed.
+# TYPE go_memstats_alloc_bytes_total counter
+go_memstats_alloc_bytes_total 9.68016566648e+11
+```
+
+The InfluxDB `/metrics` endpoint returns metrics associated with the following categories:
+
+- [Boltdb](#boltdb-statistics)
+- [Go runtime](#go-runtime-statistics)
+- [HTTP API](#http-api-statistics)
+- [InfluxDB objects and queries](#influxdb-object-and-query-statistics)
+  - [QC (query controller)](#qc-query-controller-statistics)
+- [InfluxDB services](#influxdb-service-statistics)
+- [InfluxDB tasks](#influxdb-task-statistics)
+
+## Boltdb statistics
+
+### Reads total
+
+Total number of boltdb reads.
+
+#### Example
+
+```sh
+# HELP boltdb_reads_total Total number of boltdb reads
+# TYPE boltdb_reads_total counter
+boltdb_reads_total 75129
+```
+### Writes total
+
+Total number of boltdb writes.
+
+#### Example
+
+```sh
+# HELP boltdb_writes_total Total number of boltdb writes
+# TYPE boltdb_writes_total counter
+boltdb_writes_total 201591
+```
+
+## Go runtime statistics
+
+For more detail about Go runtime statistics, see the following:
+- [Go diagostics documentation](https://go.dev/doc/diagnostics)
+- [Go mstats](https://github.com/golang/go/blob/master/src/runtime/mstats.go)
+
+### GC (garbage collection) duration seconds
+
+Summary of the pause duration of garbage collection cycles.
+
+#### Example
+
+```sh
+# HELP go_gc_duration_seconds A summary of the pause duration of garbage collection cycles.
+# TYPE go_gc_duration_seconds summary
+go_gc_duration_seconds{quantile="0"} 5.1467e-05
+--
+```
+
+### Goroutines
+
+Number of goroutines that currently exist.
+
+#### Example
+
+```sh
+# HELP go_goroutines Number of goroutines that currently exist.
+# TYPE go_goroutines gauge
+go_goroutines 1566
+```
+
+### Info
+
+Information about the Go environment.
+
+#### Example
+
+```sh
+# HELP go_info Information about the Go environment.
+# TYPE go_info gauge
+go_info{version="go1.17"} 1
+```
+
+### Memory allocated bytes
+
+Number of bytes allocated and still in use.
+
+#### Example
+
+```sh
+# HELP go_memstats_alloc_bytes Number of bytes allocated and still in use.
+# TYPE go_memstats_alloc_bytes gauge
+go_memstats_alloc_bytes 2.27988488e+08
+```
+
+### Memory allocated bytes total
+
+Total number of bytes allocated, even if freed.
+
+#### Example
+
+```sh
+# HELP go_memstats_alloc_bytes_total Total number of bytes allocated, even if freed.
+# TYPE go_memstats_alloc_bytes_total counter
+go_memstats_alloc_bytes_total 9.68016566648e+11
+```
+
+### Memory bucket hash system bytes
+
+Number of bytes used by the profiling bucket hash table.
+
+#### Example
+
+```sh
+# HELP go_memstats_buck_hash_sys_bytes Number of bytes used by the profiling bucket hash table.
+# TYPE go_memstats_buck_hash_sys_bytes gauge
+go_memstats_buck_hash_sys_bytes 1.0067613e+07
+```
+
+### Memory frees total
+
+Total number of frees.
+
+#### Example
+
+```sh
+# HELP go_memstats_frees_total Total number of frees.
+# TYPE go_memstats_frees_total counter
+go_memstats_frees_total 1.3774541795e+10
+```
+
+### Memory GC (garbage collection) CPU fraction
+
+Fraction of this program's available CPU time used by the GC since the program started.
+
+#### Example
+
+```sh
+# HELP go_memstats_gc_cpu_fraction The fraction of this program's available CPU time used by the GC since the program started.
+# TYPE go_memstats_gc_cpu_fraction gauge
+go_memstats_gc_cpu_fraction 0.011634918451016558
+```
+
+### Memory GC (garbage collection) system bytes
+
+Number of bytes used for garbage collection system metadata.
+
+#### Example
+
+```sh
+# HELP go_memstats_gc_sys_bytes Number of bytes used for garbage collection system metadata.
+# TYPE go_memstats_gc_sys_bytes gauge
+go_memstats_gc_sys_bytes 4.63048016e+08
+```
+
+### Memory heap allocated bytes
+
+Number of heap bytes allocated and still in use.
+
+#### Example
+
+```sh
+# HELP go_memstats_heap_alloc_bytes Number of heap bytes allocated and still in use.
+# TYPE go_memstats_heap_alloc_bytes gauge
+go_memstats_heap_alloc_bytes 2.27988488e+08
+```
+
+### Memory heap idle bytes
+
+Number of heap bytes waiting to be used.
+
+#### Example
+
+```sh
+# HELP go_memstats_heap_idle_bytes Number of heap bytes waiting to be used.
+# TYPE go_memstats_heap_idle_bytes gauge
+go_memstats_heap_idle_bytes 1.0918273024e+10
+```
+
+### Memory heap in use bytes
+
+Number of heap bytes that are in use.
+
+#### Example
+
+```sh
+# HELP go_memstats_heap_inuse_bytes Number of heap bytes that are in use.
+# TYPE go_memstats_heap_inuse_bytes gauge
+go_memstats_heap_inuse_bytes 3.5975168e+08
+```
+
+### Memory heap objects
+
+Number of allocated objects.
+_Allocated_ heap objects include all reachable objects, as
+well as unreachable objects that the garbage collector has not yet freed.
+
+#### Example
+
+```sh
+# HELP go_memstats_heap_objects Number of allocated objects.
+# TYPE go_memstats_heap_objects gauge
+go_memstats_heap_objects 2.404017e+06
+```
+
+### Memory heap released bytes
+
+Number of heap bytes released to the OS.
+
+#### Example
+
+```sh
+# HELP go_memstats_heap_released_bytes Number of heap bytes released to OS.
+# TYPE go_memstats_heap_released_bytes gauge
+go_memstats_heap_released_bytes 2.095038464e+09
+```
+
+### Memory heap system bytes
+
+Number of heap bytes obtained from the system.
+
+#### Example
+
+```sh
+# HELP go_memstats_heap_sys_bytes Number of heap bytes obtained from system.
+# TYPE go_memstats_heap_sys_bytes gauge
+go_memstats_heap_sys_bytes 1.1278024704e+10
+```
+
+### Memory last GC (garbage collection) time seconds
+
+Number of seconds since 1970 of the last garbage collection.
+
+#### Example
+
+```sh
+# HELP go_memstats_last_gc_time_seconds Number of seconds since 1970 of last garbage collection.
+# TYPE go_memstats_last_gc_time_seconds gauge
+go_memstats_last_gc_time_seconds 1.64217120199452e+09
+```
+
+### Memory lookups total
+
+Total number of pointer lookups.
+
+#### Example
+
+```sh
+# HELP go_memstats_lookups_total Total number of pointer lookups.
+# TYPE go_memstats_lookups_total counter
+go_memstats_lookups_total 0
+```
+
+### Memory allocations total
+
+Cumulative count of heap objects allocated.
+
+#### Example
+
+```sh
+# HELP go_memstats_mallocs_total Total number of mallocs.
+# TYPE go_memstats_mallocs_total counter
+go_memstats_mallocs_total 1.3776945812e+10
+```
+
+### Memory mcache in use bytes
+
+Number of bytes in use by mcache structures.
+
+#### Example
+
+```sh
+# HELP go_memstats_mcache_inuse_bytes Number of bytes in use by mcache structures.
+# TYPE go_memstats_mcache_inuse_bytes gauge
+go_memstats_mcache_inuse_bytes 9600
+```
+
+### Memory mcache system bytes
+
+Number of bytes used for mcache structures obtained from system.
+
+#### Example
+
+```sh
+# HELP go_memstats_mcache_sys_bytes Number of bytes used for mcache structures obtained from system.
+# TYPE go_memstats_mcache_sys_bytes gauge
+go_memstats_mcache_sys_bytes 16384
+```
+
+### Memory mspan in use bytes
+
+Number of bytes of allocated mspan structures.
+
+#### Example
+
+```sh
+# HELP go_memstats_mspan_inuse_bytes Number of bytes in use by mspan structures.
+# TYPE go_memstats_mspan_inuse_bytes gauge
+go_memstats_mspan_inuse_bytes 4.199e+06
+```
+
+### Memory mspan system bytes
+
+Bytes of memory obtained from the OS for mspan structures.
+
+#### Example
+
+```sh
+# HELP go_memstats_mspan_sys_bytes Number of bytes used for mspan structures obtained from system.
+# TYPE go_memstats_mspan_sys_bytes gauge
+go_memstats_mspan_sys_bytes 1.65609472e+08
+```
+
+### Memory next GC (garbage collection) bytes
+
+Number of heap bytes when next garbage collection will take place.
+
+#### Example
+
+```sh
+# HELP go_memstats_next_gc_bytes Number of heap bytes when next garbage collection will take place.
+# TYPE go_memstats_next_gc_bytes gauge
+go_memstats_next_gc_bytes 4.45628016e+08
+```
+
+### Memory other system bytes
+
+Number of bytes used for other system allocations.
+
+#### Example
+
+```sh
+# HELP go_memstats_other_sys_bytes Number of bytes used for other system allocations.
+# TYPE go_memstats_other_sys_bytes gauge
+go_memstats_other_sys_bytes 8.1917722e+07
+```
+
+### Memory stack in use bytes
+
+Number of bytes in use by the stack allocator.
+
+#### Example
+
+```sh
+# HELP go_memstats_stack_inuse_bytes Number of bytes in use by the stack allocator.
+# TYPE go_memstats_stack_inuse_bytes gauge
+go_memstats_stack_inuse_bytes 8.84736e+06
+```
+
+### Memory stack system bytes
+
+Number of bytes obtained from system for stack allocator.
+
+#### Example
+
+```sh
+# HELP go_memstats_stack_sys_bytes Number of bytes obtained from system for stack allocator.
+# TYPE go_memstats_stack_sys_bytes gauge
+go_memstats_stack_sys_bytes 8.84736e+06
+```
+
+### Memory system bytes
+
+Number of bytes obtained from system.
+
+#### Example
+
+```sh
+# HELP go_memstats_sys_bytes Number of bytes obtained from system.
+# TYPE go_memstats_sys_bytes gauge
+go_memstats_sys_bytes 1.2007531271e+10
+```
+
+### Threads
+
+Number of OS threads created.
+
+#### Example
+
+```sh
+# HELP go_threads Number of OS threads created.
+# TYPE go_threads gauge
+go_threads 27
+```
+
+## HTTP API statistics
+
+### API request duration seconds
+
+How long InfluxDB took to respond to the HTTP request.
+
+#### Example
+
+```sh
+# HELP http_api_request_duration_seconds Time taken to respond to HTTP request
+# TYPE http_api_request_duration_seconds histogram
+http_api_request_duration_seconds_bucket{handler="platform",method="DELETE",path="/api/v2/authorizations/:id",response_code="204",status="2XX",user_agent="Chrome",le="0.005"} 0
+--
+```
+
+### API requests total
+
+Number of HTTP requests received.
+
+#### Example
+
+```sh
+# HELP http_api_requests_total Number of http requests received
+# TYPE http_api_requests_total counter
+http_api_requests_total{handler="platform",method="DELETE",path="/api/v2/authorizations/:id",response_code="204",status="2XX",user_agent="Chrome"} 1
+--
+```
+
+### Query request bytes
+
+Count of bytes received.
+
+#### Example
+
+```sh
+# HELP http_query_request_bytes Count of bytes received
+# TYPE http_query_request_bytes counter
+http_query_request_bytes{endpoint="/api/v2/query",org_id="48c88459ee424a04",status="200"} 727
+```
+
+### Query request count
+
+Total number of query requests.
+
+#### Example
+
+```sh
+# HELP http_query_request_count Total number of query requests
+# TYPE http_query_request_count counter
+http_query_request_count{endpoint="/api/v2/query",org_id="48c88459ee424a04",status="200"} 2
+```
+
+### Query response bytes
+
+Count of bytes returned by the query endpoint.
+
+#### Example
+
+```sh
+# HELP http_query_response_bytes Count of bytes returned
+# TYPE http_query_response_bytes counter
+http_query_response_bytes{endpoint="/api/v2/query",org_id="48c88459ee424a04",status="200"} 103
+```
+
+## InfluxDB object and query statistics
+
+### Buckets total
+
+Total number of buckets on the server.
+
+#### Example
+
+```sh
+# HELP influxdb_buckets_total Number of total buckets on the server
+# TYPE influxdb_buckets_total counter
+influxdb_buckets_total 9
+```
+
+### Dashboards total
+
+Total number of dashboards on the server.
+
+#### Example
+
+```sh
+# HELP influxdb_dashboards_total Number of total dashboards on the server
+# TYPE influxdb_dashboards_total counter
+influxdb_dashboards_total 2
+```
+
+### Info
+
+Information about the InfluxDB environment.
+
+#### Example
+
+```sh
+# HELP influxdb_info Information about the influxdb environment.
+# TYPE influxdb_info gauge
+influxdb_info{arch="amd64",build_date="2021-12-28T22:12:40Z",commit="657e1839de",cpus="8",os="darwin",version="v2.1.1"} 1
+```
+
+### Organizations total
+
+Total number of organizations on the server.
+
+#### Example
+
+```sh
+# HELP influxdb_organizations_total Number of total organizations on the server
+# TYPE influxdb_organizations_total counter
+influxdb_organizations_total 2
+```
+
+### Scrapers total
+
+Total number of scrapers on the server.
+
+#### Example
+
+```sh
+# HELP influxdb_scrapers_total Number of total scrapers on the server
+# TYPE influxdb_scrapers_total counter
+influxdb_scrapers_total 0
+```
+
+### Telegrafs total
+
+Total number of Telegraf configurations on the server.
+
+#### Example
+
+```sh
+# HELP influxdb_telegrafs_total Number of total telegraf configurations on the server
+# TYPE influxdb_telegrafs_total counter
+influxdb_telegrafs_total 0
+```
+
+### Token services total
+
+Total number of API tokens on the server.
+
+#### Example
+
+```sh
+# HELP influxdb_tokens_total Number of total tokens on the server
+# TYPE influxdb_tokens_total counter
+influxdb_tokens_total 23
+```
+
+### Uptime seconds
+
+InfluxDB process uptime in seconds.
+
+#### Example
+
+```sh
+# HELP influxdb_uptime_seconds influxdb process uptime in seconds
+# TYPE influxdb_uptime_seconds gauge
+influxdb_uptime_seconds{id="077238f9ca108000"} 343354.914499305
+```
+
+### Users total
+
+Total number of users on the server.
+
+#### Example
+
+```sh
+# HELP influxdb_users_total Number of total users on the server
+# TYPE influxdb_users_total counter
+influxdb_users_total 84
+```
+
+## QC (query controller) statistics
+
+### All active
+
+Number of queries in all states.
+
+#### Example
+
+```sh
+# HELP qc_all_active Number of queries in all states
+# TYPE qc_all_active gauge
+qc_all_active{org="48c88459ee424a04"} 0
+--
+```
+
+### All duration seconds
+
+Total time spent in all query states.
+
+#### Example
+
+```sh
+# HELP qc_all_duration_seconds Histogram of total times spent in all query states
+# TYPE qc_all_duration_seconds histogram
+qc_all_duration_seconds_bucket{org="48c88459ee424a04",le="0.001"} 0
+--
+```
+
+### Compiling active
+
+Number of queries actively compiling.
+
+#### Example
+
+```sh
+# HELP qc_compiling_active Number of queries actively compiling
+# TYPE qc_compiling_active gauge
+qc_compiling_active{compiler_type="ast",org="ed32b47572a0137b"} 0
+--
+```
+
+### Compiling duration seconds
+
+Histogram of times spent compiling queries.
+
+#### Example
+
+```sh
+# HELP qc_compiling_duration_seconds Histogram of times spent compiling queries
+# TYPE qc_compiling_duration_seconds histogram
+qc_compiling_duration_seconds_bucket{compiler_type="ast",org="ed32b47572a0137b",le="0.001"} 999
+--
+```
+
+### Executing active
+
+Number of queries actively executing.
+
+#### Example
+
+```sh
+# HELP qc_executing_active Number of queries actively executing
+# TYPE qc_executing_active gauge
+qc_executing_active{org="48c88459ee424a04"} 0
+--
+```
+
+### Executing duration seconds
+
+Histogram of times spent executing queries.
+
+#### Example
+
+```sh
+# HELP qc_executing_duration_seconds Histogram of times spent executing queries
+# TYPE qc_executing_duration_seconds histogram
+qc_executing_duration_seconds_bucket{org="48c88459ee424a04",le="0.001"} 0
+--
+```
+
+### Memory unused bytes
+
+Free memory as seen by the internal memory manager.
+
+#### Example
+
+```sh
+# HELP qc_memory_unused_bytes The free memory as seen by the internal memory manager
+# TYPE qc_memory_unused_bytes gauge
+qc_memory_unused_bytes{org="48c88459ee424a04"} 0
+--
+```
+
+### Queueing active
+
+Number of queries actively queueing.
+
+#### Example
+
+```sh
+# HELP qc_queueing_active Number of queries actively queueing
+# TYPE qc_queueing_active gauge
+qc_queueing_active{org="48c88459ee424a04"} 0
+--
+```
+
+### Queueing duration seconds
+
+Histogram of times spent queueing queries.
+
+#### Example
+
+```sh
+# HELP qc_queueing_duration_seconds Histogram of times spent queueing queries
+# TYPE qc_queueing_duration_seconds histogram
+qc_queueing_duration_seconds_bucket{org="48c88459ee424a04",le="0.001"} 2
+--
+```
+
+### Requests total
+
+Count of the query requests.
+
+#### Example
+
+```sh
+# HELP qc_requests_total Count of the query requests
+# TYPE qc_requests_total counter
+qc_requests_total{org="48c88459ee424a04",result="success"} 2
+--
+```
+
+### Read request duration
+
+Histogram of times spent in read requests.
+
+#### Example
+
+```sh
+# HELP query_influxdb_source_read_request_duration_seconds Histogram of times spent in read requests
+# TYPE query_influxdb_source_read_request_duration_seconds histogram
+query_influxdb_source_read_request_duration_seconds_bucket{op="readTagKeys",org="48c88459ee424a04",le="0.001"} 0
+--
+```
+
+## InfluxDB service statistics
+
+### Bucket service new call total
+
+Number of calls to the bucket creation service.
+
+#### Example
+
+```sh
+# HELP service_bucket_new_call_total Number of calls
+# TYPE service_bucket_new_call_total counter
+service_bucket_new_call_total{method="find_bucket"} 6177
+--
+```
+
+### Bucket service new duration
+
+Duration of calls to the bucket creation service.
+
+#### Example
+
+```sh
+# HELP service_bucket_new_duration Duration of calls
+# TYPE service_bucket_new_duration histogram
+service_bucket_new_duration_bucket{method="find_bucket",le="0.005"} 5876
+--
+```
+
+### Bucket service new error total
+
+Number of errors encountered by the bucket creation service.
+
+#### Example
+
+```sh
+# HELP service_bucket_new_error_total Number of errors encountered
+# TYPE service_bucket_new_error_total counter
+service_bucket_new_error_total{code="not found",method="find_bucket_by_id"} 76
+```
+
+### Onboard service new call total
+
+Number of calls to the onboarding service.
+
+#### Example
+
+```sh
+# HELP service_onboard_new_call_total Number of calls
+# TYPE service_onboard_new_call_total counter
+service_onboard_new_call_total{method="is_onboarding"} 11
+```
+
+### Onboard service new duration
+
+Duration of calls to the onboarding service.
+
+#### Example
+
+```sh
+# HELP service_onboard_new_duration Duration of calls
+# TYPE service_onboard_new_duration histogram
+service_onboard_new_duration_bucket{method="is_onboarding",le="0.005"} 11
+--
+```
+
+### Organization service call total
+
+Number of calls to the organization service.
+
+#### Example
+
+```sh
+# HELP service_org_call_total Number of calls
+# TYPE service_org_call_total counter
+service_org_call_total{method="find_labels_for_resource"} 10
+```
+
+### Organization service duration
+
+Duration of calls to the organization service.
+
+#### Example
+
+```sh
+# HELP service_org_duration Duration of calls
+# TYPE service_org_duration histogram
+service_org_duration_bucket{method="find_labels_for_resource",le="0.005"} 10
+--
+```
+
+### Organization service new call total
+
+Number of calls to the organization creation service.
+
+#### Example
+
+```sh
+# HELP service_org_new_call_total Number of calls
+# TYPE service_org_new_call_total counter
+service_org_new_call_total{method="find_org"} 1572
+--
+```
+
+### Organization service new duration
+
+Duration of calls to the organization creation service.
+
+#### Example
+
+```sh
+# HELP service_org_new_duration Duration of calls
+# TYPE service_org_new_duration histogram
+service_org_new_duration_bucket{method="find_org",le="0.005"} 1475
+--
+```
+
+### Organization service new error total
+
+Number of errors encountered by the organization creation service.
+
+#### Example
+
+```sh
+# HELP service_org_new_error_total Number of errors encountered
+# TYPE service_org_new_error_total counter
+service_org_new_error_total{code="not found",method="find_orgs"} 1
+```
+
+### Password service new call total
+
+Number of calls to the password creation service.
+
+#### Example
+
+```sh
+# HELP service_password_new_call_total Number of calls
+# TYPE service_password_new_call_total counter
+service_password_new_call_total{method="compare_password"} 4
+```
+
+### Password service new duration
+
+Duration of calls to the password creation service.
+
+#### Example
+
+```sh
+# HELP service_password_new_duration Duration of calls
+# TYPE service_password_new_duration histogram
+service_password_new_duration_bucket{method="compare_password",le="0.005"} 0
+--
+```
+
+### Password service new error total
+
+Number of errors encountered by the password creation service.
+
+#### Example
+
+```sh
+# HELP service_password_new_error_total Number of errors encountered
+# TYPE service_password_new_error_total counter
+service_password_new_error_total{code="forbidden",method="compare_password"} 1
+```
+
+### Pkger service call total
+
+Number of calls to the `pkger` service.
+
+#### Example
+
+```sh
+# HELP service_pkger_call_total Number of calls
+# TYPE service_pkger_call_total counter
+service_pkger_call_total{method="export"} 3
+```
+
+### Pkger service duration
+
+Duration of calls to the `pkger` service.
+
+#### Example
+
+```sh
+# HELP service_pkger_duration Duration of calls
+# TYPE service_pkger_duration histogram
+service_pkger_duration_bucket{method="export",le="0.005"} 0
+--
+```
+
+### Pkger service template export
+
+Metrics for exported resources.
+
+#### Example
+
+```sh
+# HELP service_pkger_template_export Metrics for resources being exported
+# TYPE service_pkger_template_export counter
+service_pkger_template_export{buckets="0",by_stack="false",checks="0",dashboards="0",endpoints="0",label_mappings="0",labels="0",method="export",num_org_ids="1",rules="0",tasks="0",telegraf_configs="0",variables="0"} 3
+```
+
+### Session service call total
+
+Number of calls to the session service.
+
+#### Example
+
+```sh
+# HELP service_session_call_total Number of calls
+# TYPE service_session_call_total counter
+service_session_call_total{method="create_session"} 3
+--
+```
+
+### Session service duration
+
+Duration of calls to the session service.
+
+#### Example
+
+```sh
+# HELP service_session_duration Duration of calls
+# TYPE service_session_duration histogram
+service_session_duration_bucket{method="create_session",le="0.005"} 3
+--
+```
+
+### Session service error total
+
+Number of errors encountered by the session service.
+
+#### Example
+
+```sh
+# HELP service_session_error_total Number of errors encountered
+# TYPE service_session_error_total counter
+service_session_error_total{code="not found",method="find_session"} 4
+```
+
+### Token service call total
+
+Number of calls to the token service.
+
+#### Example
+
+```sh
+# HELP service_token_call_total Number of calls
+# TYPE service_token_call_total counter
+service_token_call_total{method="delete_authorization"} 3
+--
+```
+
+### Token service duration
+
+Duration of calls to the token service.
+
+#### Example
+
+```sh
+# HELP service_token_duration Duration of calls
+# TYPE service_token_duration histogram
+service_token_duration_bucket{method="delete_authorization",le="0.005"} 1
+--
+```
+
+### Token service error total
+
+Number of errors encountered by the token service.
+
+#### Example
+
+```sh
+# HELP service_token_error_total Number of errors encountered
+# TYPE service_token_error_total counter
+service_token_error_total{code="not found",method="delete_authorization"} 1
+```
+
+### URM new call total
+Number of calls to the URM (unified resource management) creation service.
+
+#### Example
+
+```sh
+# HELP service_urm_new_call_total Number of calls
+# TYPE service_urm_new_call_total counter
+service_urm_new_call_total{method="find_urms"} 6451
+```
+
+### urm new duration
+Duration of calls to the URM creation service.
+
+#### Example
+
+```sh
+# HELP service_urm_new_duration Duration of calls
+# TYPE service_urm_new_duration histogram
+service_urm_new_duration_bucket{method="find_urms",le="0.005"} 6198
+--
+```
+
+### User new call total
+Number of calls to the user creation service.
+
+#### Example
+
+```sh
+# HELP service_user_new_call_total Number of calls
+# TYPE service_user_new_call_total counter
+service_user_new_call_total{method="find_permission_for_user"} 4806
+--
+```
+
+### User new duration
+Duration of calls  to the user creation service.
+
+#### Example
+
+```sh
+# HELP service_user_new_duration Duration of calls
+# TYPE service_user_new_duration histogram
+service_user_new_duration_bucket{method="find_permission_for_user",le="0.005"} 4039
+--
+```
+
+## InfluxDB task statistics
+
+### Task executor errors counter
+
+Number of errors thrown by the executor with the type of error (ex. Invalid, Internal, etc.)
+
+#### Example
+
+```sh
+# HELP task_executor_errors_counter The number of errors thrown by the executor with the type of error (ex. Invalid, Internal, etc.)
+# TYPE task_executor_errors_counter counter
+task_executor_errors_counter{errorType="internal error",task_type="system"} 1183
+--
+```
+
+### Task executor promise queue usage
+
+Percent of the promise queue that is currently full.
+
+#### Example
+
+```sh
+# HELP task_executor_promise_queue_usage Percent of the promise queue that is currently full
+# TYPE task_executor_promise_queue_usage gauge
+task_executor_promise_queue_usage 0
+```
+
+### Task executor run duration
+
+Duration (in seconds) between a task run starting and finishing.
+
+#### Example
+
+```sh
+# HELP task_executor_run_duration The duration in seconds between a run starting and finishing.
+# TYPE task_executor_run_duration summary
+task_executor_run_duration{taskID="08017725990f6000",task_type="",quantile="0.5"} NaN
+--
+```
+
+### Task executor run latency seconds
+
+Latency between the task run's scheduled start time and the execution time, by task type.
+
+#### Example
+
+```sh
+# HELP task_executor_run_latency_seconds Records the latency between the time the run was due to run and the time the task started execution, by task type
+# TYPE task_executor_run_latency_seconds histogram
+task_executor_run_latency_seconds_bucket{task_type="system",le="0.005"} 0
+--
+```
+
+### Task executor run queue delta
+
+Duration (in seconds) between the task run's scheduled start time and the execution time.
+
+#### Example
+
+```sh
+# HELP task_executor_run_queue_delta The duration in seconds between a run being due to start and actually starting.
+# TYPE task_executor_run_queue_delta summary
+task_executor_run_queue_delta{taskID="08017725990f6000",task_type="",quantile="0.5"} NaN
+--
+```
+
+### Task executor total runs active
+
+Total number of workers currently running tasks.
+
+#### Example
+
+```sh
+# HELP task_executor_total_runs_active Total number of workers currently running tasks
+# TYPE task_executor_total_runs_active gauge
+task_executor_total_runs_active 0
+```
+
+### Task executor total runs complete
+
+Total number of task runs completed across all tasks, split out by success or failure.
+
+#### Example
+
+```sh
+# HELP task_executor_total_runs_complete Total number of runs completed across all tasks, split out by success or failure.
+# TYPE task_executor_total_runs_complete counter
+task_executor_total_runs_complete{status="failed",task_type="system"} 1384
+--
+```
+
+### Task executor workers busy
+
+Percent of total available workers that are currently busy.
+
+#### Example
+
+```sh
+# HELP task_executor_workers_busy Percent of total available workers that are currently busy
+# TYPE task_executor_workers_busy gauge
+task_executor_workers_busy 0
+```
+
+### Task scheduler current execution
+
+Number of tasks currently being executed.
+
+#### Example
+
+```sh
+# HELP task_scheduler_current_execution Number of tasks currently being executed
+# TYPE task_scheduler_current_execution gauge
+task_scheduler_current_execution 128
+```
+
+### Task scheduler execute delta
+
+Duration (in seconds) between a task run starting and finishing.
+
+#### Example
+
+```sh
+# HELP task_scheduler_execute_delta The duration in seconds between a run starting and finishing.
+# TYPE task_scheduler_execute_delta summary
+task_scheduler_execute_delta{quantile="0.5"} NaN
+--
+```
+
+### Task scheduler schedule delay
+
+Delay between when a task is scheduled to run and when it is told to execute.
+
+#### Example
+
+```sh
+# HELP task_scheduler_schedule_delay The duration between when a Item should be scheduled and when it is told to execute.
+# TYPE task_scheduler_schedule_delay summary
+task_scheduler_schedule_delay{quantile="0.5"} NaN
+--
+```
+
+### Task scheduler total execute failure
+
+Total number of times a scheduled task execution has failed.
+
+#### Example
+
+```sh
+# HELP task_scheduler_total_execute_failure Total number of times an execution has failed.
+# TYPE task_scheduler_total_execute_failure counter
+task_scheduler_total_execute_failure 0
+```
+
+### Task scheduler total execution calls
+
+Total number of scheduled executions across all tasks.
+
+#### Example
+
+```sh
+# HELP task_scheduler_total_execution_calls Total number of executions across all tasks.
+# TYPE task_scheduler_total_execution_calls counter
+task_scheduler_total_execution_calls 4806
+```
+
+### Task scheduler total release calls
+
+Total number of release requests.
+
+#### Example
+
+```sh
+# HELP task_scheduler_total_release_calls Total number of release requests.
+# TYPE task_scheduler_total_release_calls counter
+task_scheduler_total_release_calls 0
+```
+
+### Task scheduler total schedule calls
+
+Total number of schedule requests.
+
+#### Example
+
+```sh
+# HELP task_scheduler_total_schedule_calls Total number of schedule requests.
+# TYPE task_scheduler_total_schedule_calls counter
+task_scheduler_total_schedule_calls 6
+```
+
+### Task scheduler total schedule fails
+
+Total number of schedule requests that fail to schedule.
+
+#### Example
+
+```sh
+# HELP task_scheduler_total_schedule_fails Total number of schedule requests that fail to schedule.
+# TYPE task_scheduler_total_schedule_fails counter
+task_scheduler_total_schedule_fails 0
+```
diff --git a/content/influxdb/v2.1/reference/internals/runtime.md b/content/influxdb/v2.1/reference/internals/runtime.md
new file mode 100644
index 000000000..c7a57dacb
--- /dev/null
+++ b/content/influxdb/v2.1/reference/internals/runtime.md
@@ -0,0 +1,347 @@
+---
+title: InfluxDB runtime
+description: >
+  Learn how to collect Go runtime profiling and tracing information to help with InfluxDB performance analysis and debugging.
+menu:
+  influxdb_2_1_ref:
+    name: Runtime
+    parent: InfluxDB internals
+weight: 103
+influxdb/v2.1/tags: [go, internals, performance]
+---
+
+InfluxDB provides Go runtime profiles, trace, and other information
+useful for analyzing and debugging the server runtime execution.
+
+- [Overview of Go runtime profiles](#overview-of-go-runtime-profiles)
+- [Analyze Go runtime profiles](#analyze-go-runtime-profiles)
+- [Analyze the Go runtime trace](#analyze-the-go-runtime-trace)
+- [View the command line that invoked InfluxDB](#view-the-command-line-that-invoked-influxdb)
+
+## Overview of Go runtime profiles
+
+A **Go runtime profile** is a collection of stack traces showing call sequences that led to instances of a particular event. InfluxDB provides profile data for the following events:
+
+- blocks
+- CPU usage
+- memory allocation
+- mutual exclusion (mutex)
+- OS thread creation
+
+When you send a profile request to InfluxDB, the [Golang runtime pprof package](https://pkg.go.dev/runtime/pprof) samples the events on the runtime to collect stack traces and statistics (e.g., number of bytes of memory for heap allocation events). For some profiles, you can set the number of seconds that InfluxDB will collect profile data.
+
+Once data collection is complete, InfluxDB returns the profile data. The default response format is a compressed protocol buffer in
+[profile.proto](https://github.com/google/pprof/blob/master/proto/profile.proto) format. **profile.proto** files are compatible with the [pprof](https://github.com/google/pprof) and [`go tool pprof`](https://go.dev/blog/pprof) analysis tools. For some profiles, InfluxDB provides an alternative human-readable plain text format with comments that translate to function calls and line numbers, but the `pprof` tools and **profile.proto** format offer the following advantages:
+
+- Read profiles from disk or HTTP.
+- Aggregate and compare multiple profiles of the same type.
+- Analyze and filter profile data.
+- Generate visualizations and reports.
+
+## Analyze Go runtime profiles
+
+Use the `/debug/pprof` InfluxDB endpoints to download all the profiles at once or request them individually.
+
+- [Get all runtime profiles](#get-all-runtime-profiles)
+- [Profile all memory allocations](#profile-all-memory-allocations)
+- [Profile blocking operations](#profile-blocking-operations)
+- [Profile CPU](#profile-cpu)
+- [Profile goroutines](#profile-goroutines)
+- [Profile heap memory allocations](#profile-heap-memory-allocations)
+- [Profile mutual exclusions](#profile-mutual-exclusions-mutexes)
+- [Profile thread creation](#profile-thread-creation)
+
+### Get all runtime profiles
+
+To download all runtime profiles at once, use an HTTP client to send a `GET` request to the `/debug/pprof/all` endpoint. `go tool pprof` can't fetch profiles directly from `/debug/pprof/all`.
+
+{{% api-endpoint method="GET" endpoint="http://localhost:8086/debug/pprof/all" %}}
+
+InfluxDB returns a gzipped tar file that contains the following profiles in the **profile.proto** format:
+
+- `profiles/allocs.pb.gz`: [profile all memory allocations](#profile-all-memory-allocations)
+- `profiles/block.pb.gz`: [profile blocking operations](#profile-blocking-operations)
+- `profiles/cpu.pb.gz`: _(Optional)_ [profile CPU](#profile-cpu).
+- `profiles/goroutine.pb.gz`: [profile goroutines](#profile-goroutines)
+- `profiles/heap.pb.gz`: [profile heap memory allocations](#profile-heap-memory-allocations)
+- `profiles/mutex.pb.gz`: [profile mutual exclusions](#profile-mutual-exclusions-mutexes)
+- `profiles/threadcreate.pb.gz`: [profile thread creation](#profile-thread-creation)
+
+| Option  | Include by |
+|:--------|:-----------|
+| Profile CPU | Pass a [duration of seconds](/influxdb/v2.1/reference/glossary/#duration) with the `cpu` query parameter in your request URL |
+
+Use an HTTP client like `curl` or `wget` to download profiles from `/debug/pprof/all`.
+
+#### Example
+
+```sh
+# Use `curl` to download a `.tar.gz` of all profiles after 10 seconds of CPU sampling.
+# Use `tar` to extract the profiles folder.
+
+curl "http://localhost:8086/debug/pprof/all?cpu=10s" | tar -xz
+
+# Analyze an extracted profile.
+
+go tool pprof profiles/heap.pb.gz
+```
+
+### Profile all memory allocations
+
+Profiles memory allocations and sets the default profile display to __alloc_space__,
+the total number of bytes allocated since the program began (including garbage-collected bytes).
+
+{{% api-endpoint method="GET" endpoint="http://localhost:8086/debug/pprof/allocs" %}}
+
+| Option  | Include by |
+|:--------|:-----------|
+| Seconds to sample | Pass an [unsigned integer](/influxdb/v2.1/reference/glossary/#unsigned-integer) with the `seconds` query parameter in your request URL |
+| Output plain text (mutually exclusive with `seconds`) | Pass `1` with the `debug` query parameter in your request URL |
+
+```sh
+# Analyze the profile in interactive mode.
+
+go tool pprof http://localhost:8086/debug/pprof/allocs
+
+# `pprof` returns the following prompt:
+#   Entering interactive mode (type "help" for commands, "o" for options)
+#   (pprof)
+
+# At the prompt, get the top N memory allocations.
+
+(pprof) top10
+```
+
+### Profile blocking operations
+
+Profiles operations that led to blocking on synchronization primitives and caused Go to suspend goroutine's execution.
+
+{{% api-endpoint method="GET" endpoint="http://localhost:8086/debug/pprof/block" %}}
+
+| Option  | Include by |
+|:--------|:-----------|
+| Output plain text | Pass `1` with the `debug` query parameter in your request URL |
+
+```sh
+# Analyze the profile in interactive mode.
+
+go tool pprof http://localhost:8086/debug/pprof/block
+
+# `pprof` returns the following prompt:
+#   Entering interactive mode (type "help" for commands, "o" for options)
+#   (pprof)
+
+#  At the prompt, get the top N entries.
+
+(pprof) top10
+```
+
+### Profile CPU
+
+Profiles program counters sampled from the execution stack. To download the profile, use an HTTP client to send a `GET` request to the `/debug/pprof/profile` endpoint. `go tool pprof` can't fetch the CPU profile directly.
+
+{{% api-endpoint method="GET" endpoint="http://localhost:8086/debug/pprof/profile" %}}
+
+| Option  | Include by |
+|:--------|:-----------|
+| Seconds to sample (default `30`) | Pass an [unsigned integer](/influxdb/v2.1/reference/glossary/#unsigned-integer) with the `seconds` query parameter in your request URL |
+
+Use an HTTP client like `curl` or `wget` to download the profile.
+
+#### Example
+
+```sh
+# Get the profile.
+
+curl http://localhost:8086/debug/pprof/profile -o cpu
+
+# Analyze the profile in interactive mode.
+
+go tool pprof ./cpu
+
+# At the prompt, get the top N functions most often running
+# or waiting during the sample period.
+
+(pprof) top10
+```
+
+Use the `seconds` query parameter to control the sampling duration.
+
+{{% note %}}
+
+`/debug/pprof/profile?seconds=SECONDS` returns the same CPU profile as `/debug/pprof/all?cpu=DURATION`.
+
+{{% /note %}}
+
+#### Example
+
+```sh
+# Get the CPU profile after 10 seconds of sampling.
+
+curl "http://localhost:8086/debug/pprof/profile?seconds=10" -o cpu
+
+# Get all profiles after 10 seconds of CPU sampling.
+
+curl "http://localhost:8086/debug/pprof/all?cpu=10s" -o all.tar.gz
+```
+
+### Profile goroutines
+
+Profiles all current goroutines.
+
+{{% api-endpoint method="GET" endpoint="http://localhost:8086/debug/pprof/goroutine" %}}
+
+| Option  | Include by |
+|:--------|:-----------|
+| Seconds to sample | Pass an [unsigned integer](/influxdb/v2.1/reference/glossary/#unsigned-integer) with the `seconds` query parameter in your request URL |
+| Output plain text (mutually exclusive with `seconds`) | Pass `1` with the `debug` query parameter in your request URL |
+
+#### Example
+
+```sh
+# Analyze the profile in interactive mode.
+
+go tool pprof http://localhost:8086/debug/pprof/goroutine
+
+# `pprof` returns the following prompt:
+#   Entering interactive mode (type "help" for commands, "o" for options)
+#   (pprof)
+
+#  At the prompt, get the top N entries.
+
+(pprof) top10
+```
+
+### Profile heap memory allocations
+
+Profiles heap, or memory allocations for live objects.
+
+{{% api-endpoint method="GET" endpoint="http://localhost:8086/debug/pprof/heap" %}}
+
+| Option  | Include by |
+|:--------|:-----------|
+| Run garbage control before sampling | Pass `1` with the `gc` query parameter in your request URL |
+| Seconds to sample | Pass an [unsigned integer](/influxdb/v2.1/reference/glossary/#unsigned-integer) with the `seconds` query parameter in your request URL |
+| Output plain text (mutually exclusive with `seconds`) | Pass `1` with the `debug` query parameter in your request URL |
+
+#### Example
+
+```sh
+# Analyze the profile in interactive mode.
+
+go tool pprof http://localhost:8086/debug/pprof/heap
+
+# `pprof` returns the following prompt:
+#   Entering interactive mode (type "help" for commands, "o" for options)
+#   (pprof)
+
+# At the prompt, get the top N memory-intensive nodes.
+
+(pprof) top10
+
+# pprof displays the list:
+#   Showing nodes accounting for 142.46MB, 85.43% of 166.75MB total
+#   Dropped 895 nodes (cum <= 0.83MB)
+#   Showing top 10 nodes out of 143
+```
+
+### Profile mutual exclusions (mutexes)
+
+Profiles holders of contended mutual exclusions (mutexes).
+
+{{% api-endpoint method="GET" endpoint="http://localhost:8086/debug/pprof/mutex" %}}
+
+| Option  | Include by |
+|:--------|:-----------|
+| Seconds to sample | Pass an [unsigned integer](/influxdb/v2.1/reference/glossary/#unsigned-integer) with the `seconds` query parameter in your request URL |
+| Output plain text (mutually exclusive with `seconds`) | Pass `1` with the `debug` query parameter in your request URL |
+
+#### Example
+
+```sh
+# Analyze the profile in interactive mode.
+
+go tool pprof http://localhost:8086/debug/pprof/mutex
+
+# `pprof` returns the following prompt:
+#   Entering interactive mode (type "help" for commands, "o" for options)
+#   (pprof)
+
+#  At the prompt, get the top N entries.
+
+(pprof) top10
+```
+
+### Profile thread creation
+
+Profiles operations that led to the creation of OS threads.
+
+{{% api-endpoint method="GET" endpoint="http://localhost:8086/debug/pprof/threadcreate" %}}
+
+| Option  | Include by |
+|:--------|:-----------|
+| Seconds to sample | Pass an [unsigned integer](/influxdb/v2.1/reference/glossary/#unsigned-integer) with the `seconds` query parameter in your request URL |
+| Output plain text (mutually exclusive with `seconds`) | Pass `1` with the `debug` query parameter in your request URL |
+
+#### Example
+
+```sh
+# Analyze the profile in interactive mode.
+
+go tool pprof http://localhost:8086/debug/pprof/threadcreate
+
+# `pprof` returns the following prompt:
+#   Entering interactive mode (type "help" for commands, "o" for options)
+#   (pprof)
+
+#  At the prompt, get the top N entries.
+
+(pprof) top10
+```
+
+## Analyze the Go runtime trace
+
+To trace execution events for InfluxDB, use the `/debug/pprof/trace`
+endpoint with `go tool trace`.
+
+{{% api-endpoint method="GET" endpoint="http://localhost:8086/debug/pprof/trace" %}}
+
+#### Example
+
+```sh
+# Download the trace file.
+
+curl http://localhost:8086/debug/pprof/trace -o trace.out
+
+# Analyze the trace.
+
+go tool trace ./trace.out
+```
+
+#### Generate a pprof-like profile from trace
+
+You can use `go tool trace` to generate _pprof-like_ profiles from
+a trace file and then analyze them with `go tool pprof`.
+
+#### Example
+
+```sh
+# Generate a profile from the downloaded trace file.
+
+go tool trace -pprof=PROFILE_TYPE ./trace.out > PROFILE_TYPE.pprof
+```
+
+Replace *`PROFILE_TYPE`* with one of the following [Golang profile types](https://pkg.go.dev/cmd/trace):
+
+- `net`: network blocking profile
+- `sync`: synchronization blocking profile
+- `syscall`: syscall blocking profile
+- `sched`: scheduler latency profile
+
+## View the command line that invoked InfluxDB
+
+To view the command, arguments, and command-line variables that invoked InfluxDB, use the `/debug/pprof/cmdline` endpoint.
+
+{{% api-endpoint method="GET" endpoint="http://localhost:8086/debug/pprof/cmdline" %}}
+
+`/debug/pprof/cmdline` returns the command line invocation in plain text.
diff --git a/content/influxdb/v2.1/reference/internals/shards.md b/content/influxdb/v2.1/reference/internals/shards.md
index d0b38dee5..62812d7a0 100644
--- a/content/influxdb/v2.1/reference/internals/shards.md
+++ b/content/influxdb/v2.1/reference/internals/shards.md
@@ -8,7 +8,7 @@ menu:
   influxdb_2_1_ref:
     name: Shards & shard groups
     parent: InfluxDB internals
-weight: 102
+weight: 103
 influxdb/v2.1/tags: [storage, internals]
 related:
   - /influxdb/v2.1/reference/internals/storage-engine/
diff --git a/content/influxdb/v2.1/reference/internals/storage-engine.md b/content/influxdb/v2.1/reference/internals/storage-engine.md
index 69ac8cbb3..0fa480618 100644
--- a/content/influxdb/v2.1/reference/internals/storage-engine.md
+++ b/content/influxdb/v2.1/reference/internals/storage-engine.md
@@ -72,7 +72,10 @@ The cache:
 - Stores uncompressed data.
 - Gets updates from the WAL each time the storage engine restarts.
   The cache is queried at runtime and merged with the data stored in TSM files.
+- Uses a maximum `maxSize` bytes of memory.
 
+Cache snapshots are cache objects currently being written to TSM files.
+They're kept in memory while flushing so they can be queried along with the cache.
 Queries to the storage engine merge data from the cache with data from the TSM files.
 Queries execute on a copy of the data that is made from the cache at query processing time.
 This way writes that come in while a query is running do not affect the result.
diff --git a/content/influxdb/v2.1/reference/key-concepts/data-elements.md b/content/influxdb/v2.1/reference/key-concepts/data-elements.md
index dd75ef882..dbc8f66e2 100644
--- a/content/influxdb/v2.1/reference/key-concepts/data-elements.md
+++ b/content/influxdb/v2.1/reference/key-concepts/data-elements.md
@@ -8,7 +8,7 @@ menu:
     parent: Key concepts
     name: Data elements
 influxdb/v2.1/tags: [key concepts, schema]
-related: 
+related:
   - /resources/videos/data-model-building-blocks/
 ---
 
@@ -51,19 +51,19 @@ The  `_measurement` column shows the name of the measurement `census`. Measureme
 
 ## Fields
 
-A field includes a field key stored in the `_field` column and a field value stored in the `_value` column.
+A field includes a field key stored in the `_field` column and a field value stored in the `_value` column. A [measurement](#measurement) requires at least one field.
 
 ### Field key
 
-A field key is a string that represents the name of the field. In the sample data above, `bees` and `ants` are field keys.
+A field key is a string that represents the name of the field. In the [sample data](#sample-data) above, `bees` and `ants` are field keys.
 
 ### Field value
 
-A field value represents the value of an associated field. Field values can be strings, floats, integers, or booleans. The field values in the sample data show the number of `bees` at specified times: `23`, and `28` and the number of `ants` at a specified time: `30` and `32`.
+A field value represents the value of an associated field. Field values can be strings, floats, integers, or booleans. The field values in the [sample data](#sample-data) show the number of `bees` at specified times: `23`, and `28` and the number of `ants` at a specified time: `30` and `32`.
 
 ### Field set
 
-A field set is a collection of field key-value pairs associated with a timestamp. The sample data includes the following field sets:
+A field set is a collection of field key-value pairs associated with a timestamp. A [measurement](#measurement) requires at least one field. The [sample data](#sample-data) includes the following field sets:
 
 ```bash
 
@@ -75,17 +75,21 @@ census bees=28i,ants=32i 1566086760000000000
 ```
 
 {{% note %}}
-**Fields aren't indexed:** Fields are required in InfluxDB data and are not indexed. Queries that filter field values must scan all field values to match query conditions. As a result, queries on tags > are more performant than queries on fields. **Store commonly queried metadata in tags.**
+
+**Field values aren't indexed**. Store commonly queried metadata in tags.
+
+To learn how to use fields and tags to improve your queries, see [best practices for schema design](/influxdb/v2.1/write-data/best-practices/schema-design/).
+
 {{% /note %}}
 
 ## Tags
 
-The columns in the sample data, `location` and `scientist`, are tags.
-Tags include tag keys and tag values that are stored as strings and metadata.
+In the [sample data](#sample-data), the columns `location` and `scientist` are tags that provide metadata for the point.
+Tags include tag keys and tag values that are stored as strings.
 
 ### Tag key
 
-The tag keys in the sample data are `location` and `scientist`.
+The tag keys in the [sample data](#sample-data) are `location` and `scientist`.
 _For information about tag key requirements, see [Line protocol – Tag set](/influxdb/v2.1/reference/syntax/line-protocol/#tag-set)._
 
 ### Tag value
@@ -96,7 +100,7 @@ _For information about tag value requirements, see [Line protocol – Tag set](/
 
 ### Tag set
 
-The collection of tag key-value pairs make up a tag set. The sample data includes the following four tag sets:
+The collection of tag key-value pairs make up a tag set. The [sample data](#sample-data) includes the following four tag sets:
 
 ```bash
 location = klamath, scientist = anderson
@@ -106,12 +110,11 @@ location = portland, scientist = mullen
 ```
 
 {{% note %}}
-**Tags are indexed:** Tags are optional. You don't need tags in your data structure, but it's typically a good idea to include tags.
-Because tags are indexed, queries on tags are faster than queries on fields. This makes tags ideal for storing commonly-queried metadata.
-{{% /note %}}
 
-{{% note %}}
-Tags containing highly variable information like UUIDs, hashes, and random strings will lead to a large number of unique series in the database, known as **high series cardinality**. High series cardinality is a primary driver of high memory usage for many database workloads. See [series cardinality](/influxdb/v2.1/reference/glossary/#series-cardinality) for more information.   
+**Field values aren't indexed**. Store commonly queried metadata in tags.
+
+To learn how to use fields and tags to improve your queries, see [best practices for schema design](/influxdb/v2.1/write-data/best-practices/schema-design/).
+
 {{% /note %}}
 
 
@@ -121,11 +124,11 @@ If most of your queries focus on values in the fields, for example, a query to f
 
 ```js
 from(bucket: "bucket-name")
-  |> range(start: 2019-08-17T00:00:00Z, stop: 2019-08-19T00:00:00Z)
-  |> filter(fn: (r) => r._field == "bees" and r._value == 23)
+    |> range(start: 2019-08-17T00:00:00Z, stop: 2019-08-19T00:00:00Z)
+    |> filter(fn: (r) => r._field == "bees" and r._value == 23)
 ```
 
-InfluxDB scans every field value in the dataset for `bees` before the query returns a response. If our sample `census` data grew to millions of rows, to optimize your query, you could rearrange your [schema](/influxdb/v2.1/reference/glossary/#schema) so the fields (`bees` and `ants`) becomes tags and the tags (`location` and `scientist`) become fields:
+InfluxDB scans every field value in the dataset for `bees` before the query returns a response. If our `census` [sample data](#sample-data) grew to millions of rows, to optimize your query, you could rearrange your [schema](/influxdb/v2.1/reference/glossary/#schema) so the fields (`bees` and `ants`) becomes tags and the tags (`location` and `scientist`) become fields:
 
 | _time                | _measurement | {{< tooltip "Tag key" "bees" >}} | _field                                 | _value                                   |
 |:-------------------  |:------------ |:-------                          |:--                                     |:------                                   |
@@ -143,6 +146,12 @@ InfluxDB scans every field value in the dataset for `bees` before the query retu
 
 Now that `bees` and `ants` are tags, InfluxDB doesn't have to scan all `_field` and `_value` columns. This makes your queries faster.
 
+{{% note %}}
+
+For more information about designing measurements, tags, and fields for querying, see [best practices for schema design](/influxdb/v2.1/write-data/best-practices/schema-design/).
+
+{{% /note %}}
+
 ## Bucket schema
 
 In InfluxDB Cloud, a bucket with the `explicit` schema-type requires an explicit
@@ -204,4 +213,4 @@ If you're just starting out, we recommend taking a look at the following guides:
 
 For an overview of how these elements interconnect within InfluxDB's data model, watch the follwoing video:
 
-{{< youtube 3qTTqsL27lI >}}
\ No newline at end of file
+{{< youtube 3qTTqsL27lI >}}
diff --git a/content/influxdb/v2.1/reference/prometheus-metrics.md b/content/influxdb/v2.1/reference/prometheus-metrics.md
index 08cd92c8b..1a8e867b3 100644
--- a/content/influxdb/v2.1/reference/prometheus-metrics.md
+++ b/content/influxdb/v2.1/reference/prometheus-metrics.md
@@ -12,7 +12,7 @@ related:
   - https://prometheus.io/docs/concepts/data_model/, Prometheus data model
   - /influxdb/v2.1/write-data/developer-tools/scrape-prometheus-metrics/
   - /{{< latest "flux" >}}/prometheus/, Work with Prometheus in Flux
-  - /{{< latest "telegraf" >}}/plugins/#prometheus, Telegraf Prometheus input plugin
+  - /{{< latest "telegraf" >}}/plugins/#input-prometheus, Telegraf Prometheus input plugin
   - /influxdb/v2.1/write-data/no-code/scrape-data/
   - /{{< latest "flux" >}}/stdlib/experimental/prometheus/scrape/
 ---
@@ -28,7 +28,7 @@ are parsed and written to InfluxDB in one of two formats, depending on the scrap
 
 | Scraping tool                                                                              |                               InfluxDB Metric version |
 | :----------------------------------------------------------------------------------------- | ----------------------------------------------------: |
-| [Telegraf Prometheus plugin](/{{< latest "telegraf" >}}/plugins/#prometheus)               | _Determined by `metric_version` configuration option_ |
+| [Telegraf Prometheus plugin](/{{< latest "telegraf" >}}/plugins/#input-prometheus)               | _Determined by `metric_version` configuration option_ |
 | [InfluxDB scraper](/influxdb/v2.1/write-data/no-code/scrape-data/)                         |                                                     1 |
 | Flux [`prometheus.scrape()`]({{< latest "flux" >}}/stdlib/experimental/prometheus/scrape/) |                                                     2 |
 
@@ -37,7 +37,7 @@ are parsed and written to InfluxDB in one of two formats, depending on the scrap
 
 | Scraping tool                                                                              |                               InfluxDB Metric version |
 | :----------------------------------------------------------------------------------------- | ----------------------------------------------------: |
-| [Telegraf Prometheus plugin](/{{< latest "telegraf" >}}/plugins/#prometheus)               | _Determined by `metric_version` configuration option_ |
+| [Telegraf Prometheus plugin](/{{< latest "telegraf" >}}/plugins/#input-prometheus)               | _Determined by `metric_version` configuration option_ |
 | Flux [`prometheus.scrape()`]({{< latest "flux" >}}/stdlib/experimental/prometheus/scrape/) |                                                     2 |
 
 {{% /cloud-only %}}
diff --git a/content/influxdb/v2.1/reference/sample-data.md b/content/influxdb/v2.1/reference/sample-data.md
index 8ffc99d87..4fd80517f 100644
--- a/content/influxdb/v2.1/reference/sample-data.md
+++ b/content/influxdb/v2.1/reference/sample-data.md
@@ -133,7 +133,7 @@ we recommend that you [create a new bucket](/influxdb/v2.1/organizations/buckets
 import "experimental/csv"
 
 csv.from(url: "https://influx-testdata.s3.amazonaws.com/noaa.csv")
-  |> to(bucket: "noaa", org: "example-org")
+    |> to(bucket: "noaa", org: "example-org")
 ```
 {{% /note %}}
 
diff --git a/content/influxdb/v2.1/reference/syntax/delete-predicate.md b/content/influxdb/v2.1/reference/syntax/delete-predicate.md
index edf13c37d..cc5a02c49 100644
--- a/content/influxdb/v2.1/reference/syntax/delete-predicate.md
+++ b/content/influxdb/v2.1/reference/syntax/delete-predicate.md
@@ -31,9 +31,11 @@ Use [logical operators](#logical-operators) to combine two or more predicate exp
 ```sql
 key1="value1" AND key2="value"
 ```
-{{% note %}}
-Predicate expressions can use any column or tag except `_time` or `_value`.
-{{% /note %}}
+
+{{% warn %}}
+With **InfluxDB {{< current-version >}}**, delete predicates can use any column
+or tag **except** `_time`{{% oss-only %}}, `_field`, {{% /oss-only %}}or `_value`.
+{{% /warn %}}
 
 ## Logical operators
 Logical operators join two or more predicate expressions.
@@ -51,22 +53,29 @@ Comparison operators compare left and right operands and return `true` or `false
 
 ## Delete predicate examples
 
-### Delete points with a specific measurement
+- [Delete points by measurement](#delete-points-by-measurement)
+- {{% cloud-only %}}[Delete points by field](#delete-points-by-field){{% /cloud-only %}}
+- [Delete points by tag set](#delete-points-by-tag-set)
+
+### Delete points by measurement
 The following will delete points in the `sensorData` measurement:
 
 ```sql
 _measurement="sensorData"
 ```
 
-<!--
-### Delete points with a specific field
+{{% cloud-only %}}
+
+### Delete points by field
 The following will delete points with the `temperature` field:
 
 ```sql
 _field="temperature"
 ```
- -->
-### Delete points with a specific tag set
+
+{{% /cloud-only %}}
+
+### Delete points by tag set
 The following will delete points from the `prod-1.4` host in the `us-west` region:
 
 ```sql
@@ -79,4 +88,5 @@ The delete predicate syntax has the following limitations.
 - Delete predicates do not support regular expressions.
 - Delete predicates do not support the `OR` logical operator.
 - Delete predicates only support equality (`=`), not inequality (`!=`).
-- Delete predicates can use any column or tag except `_time` or `_value`.
+- Delete predicates can use any column or tag **except** `_time`
+  {{% oss-only %}}, `_field`, {{% /oss-only %}}or `_value`.
diff --git a/content/influxdb/v2.1/reference/syntax/flux/flux-vs-influxql.md b/content/influxdb/v2.1/reference/syntax/flux/flux-vs-influxql.md
index f8a4f4200..157743549 100644
--- a/content/influxdb/v2.1/reference/syntax/flux/flux-vs-influxql.md
+++ b/content/influxdb/v2.1/reference/syntax/flux/flux-vs-influxql.md
@@ -45,23 +45,14 @@ each data set includes the columns to join on.
 
 ```js
 dataStream1 = from(bucket: "example-bucket1")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "network" and
-    r._field == "bytes-transferred"
-  )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "network" and r._field == "bytes-transferred")
 
 dataStream2 = from(bucket: "example-bucket2")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "httpd" and
-    r._field == "requests-per-sec"
-    )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "httpd" and r._field == "requests-per-sec")
 
-join(
-    tables: {d1:dataStream1, d2:dataStream2},
-    on: ["_time", "_stop", "_start", "host"]
-  )
+join(tables: {d1: dataStream1, d2: dataStream2}, on: ["_time", "_stop", "_start", "host"])
 ```
 
 _For an in-depth walkthrough of using the `join()` function, see [how to join data with Flux](/influxdb/v2.1/query-data/flux/join/)._
@@ -75,31 +66,18 @@ joins them, and then calculates the average amount of memory used per running pr
 ```js
 // Memory used (in bytes)
 memUsed = from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "mem" and
-    r._field == "used"
-  )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used")
 
 // Total processes running
 procTotal = from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "processes" and
-    r._field == "total"
-    )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "processes" and r._field == "total")
 
 // Join memory used with total processes to calculate
 // the average memory (in MB) used for running processes.
-join(
-    tables: {mem:memUsed, proc:procTotal},
-    on: ["_time", "_stop", "_start", "host"]
-  )
-  |> map(fn: (r) => ({
-    _time: r._time,
-    _value: (r._value_mem / r._value_proc) / 1000000
-  })
-)
+join(tables: {mem: memUsed, proc: procTotal}, on: ["_time", "_stop", "_start", "host"])
+    |> map(fn: (r) => ({_time: r._time, _value: r._value_mem / r._value_proc / 1000000}))
 ```
 
 ### Sort by tags
@@ -110,13 +88,10 @@ sorts records based on a list of columns.
 Depending on the column type, Flux sorts records lexicographically, numerically, or chronologically.
 
 ```js
-from(bucket:"example-bucket")
-  |> range(start: -12h)
-  |> filter(fn: (r) =>
-    r._measurement == "system" and
-    r._field == "uptime"
-  )
-  |> sort(columns:["region", "host", "_value"])
+from(bucket: "example-bucket")
+    |> range(start: -12h)
+    |> filter(fn: (r) => r._measurement == "system" and r._field == "uptime")
+    |> sort(columns: ["region", "host", "_value"])
 ```
 
 ### Group by any column
@@ -127,9 +102,9 @@ to define which columns to group data by.
 
 ```js
 from(bucket:"example-bucket")
-  |> range(start: -12h)
-  |> filter(fn: (r) => r._measurement == "system" and r._field == "uptime" )
-  |> group(columns:["host", "_value"])
+    |> range(start: -12h)
+    |> filter(fn: (r) => r._measurement == "system" and r._field == "uptime" )
+    |> group(columns:["host", "_value"])
 ```
 
 ### Window by calendar months and years
@@ -139,9 +114,9 @@ window and aggregate data by calendar month and year.
 
 ```js
 from(bucket:"example-bucket")
-  |> range(start:-1y)
-  |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent" )
-  |> aggregateWindow(every: 1mo, fn: mean)
+    |> range(start:-1y)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent" )
+    |> aggregateWindow(every: 1mo, fn: mean)
 ```
 
 ### Work with multiple data sources
@@ -159,20 +134,22 @@ import "csv"
 import "sql"
 
 csvData = csv.from(csv: rawCSV)
+
 sqlData = sql.from(
-  driverName: "postgres",
-  dataSourceName: "postgresql://user:password@localhost",
-  query:"SELECT * FROM example_table"
+    driverName: "postgres",
+    dataSourceName: "postgresql://user:password@localhost",
+    query: "SELECT * FROM example_table",
 )
+
 data = from(bucket: "example-bucket")
-  |> range(start: -24h)
-  |> filter(fn: (r) => r._measurement == "sensor")
+    |> range(start: -24h)
+    |> filter(fn: (r) => r._measurement == "sensor")
 
 auxData = join(tables: {csv: csvData, sql: sqlData}, on: ["sensor_id"])
 enrichedData = join(tables: {data: data, aux: auxData}, on: ["sensor_id"])
 
 enrichedData
-  |> yield(name: "enriched_data")
+    |> yield(name: "enriched_data")
 ```
 
 _For an in-depth walkthrough of querying SQL data, see [Query SQL data sources](/influxdb/v2.1/query-data/flux/sql/)._
@@ -184,12 +161,9 @@ returns only data with time values in a specified hour range.
 
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "cpu" and
-    r.cpu == "cpu-total"
-  )
-  |> hourSelection(start: 9, stop: 17)
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "cpu" and r.cpu == "cpu-total")
+    |> hourSelection(start: 9, stop: 17)
 ```
 
 ### Pivot
@@ -199,16 +173,9 @@ to pivot data tables by `rowKey`, `columnKey`, and `valueColumn` parameters.
 
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "cpu" and
-    r.cpu == "cpu-total"
-  )
-  |> pivot(
-    rowKey:["_time"],
-    columnKey: ["_field"],
-    valueColumn: "_value"
-  )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "cpu" and r.cpu == "cpu-total")
+    |> pivot(rowKey: ["_time"], columnKey: ["_field"], valueColumn: "_value")
 ```
 
 ### Histograms
@@ -218,14 +185,9 @@ generate a cumulative histogram.
 
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "mem" and
-    r._field == "used_percent"
-  )
-  |> histogram(
-    buckets: [10, 20, 30, 40, 50, 60, 70, 80, 90, 100]
-  )
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+    |> histogram(buckets: [10, 20, 30, 40, 50, 60, 70, 80, 90, 100])
 ```
 
 _For more examples, see [how to create histograms with Flux](/influxdb/v2.1/query-data/flux/histograms/)._
@@ -239,23 +201,19 @@ to calculate the covariance between two data streams.
 ###### Covariance between two columns
 ```js
 from(bucket: "example-bucket")
-  |> range(start:-5m)
-  |> covariance(columns: ["x", "y"])
+    |> range(start:-5m)
+    |> covariance(columns: ["x", "y"])
 ```
 
 ###### Covariance between two streams of data
 ```js
 table1 = from(bucket: "example-bucket")
-  |> range(start: -15m)
-  |> filter(fn: (r) =>
-    r._measurement == "measurement_1"
-  )
+    |> range(start: -15m)
+    |> filter(fn: (r) => r._measurement == "measurement_1")
 
 table2 = from(bucket: "example-bucket")
-  |> range(start: -15m)
-  |> filter(fn: (r) =>
-    r._measurement == "measurement_2"
-  )
+    |> range(start: -15m)
+    |> filter(fn: (r) => r._measurement == "measurement_2")
 
 cov(x: table1, y: table2, on: ["_time", "_field"])
 ```
@@ -268,12 +226,9 @@ to perform many more type conversions, including casting boolean values to integ
 ##### Cast boolean field values to integers
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "m" and
-    r._field == "bool_field"
-  )
-  |> toInt()
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "m" and r._field == "bool_field")
+    |> toInt()
 ```
 
 ### String manipulation and data shaping
@@ -285,17 +240,16 @@ Combine functions in this package with the [`map()` function](/{{< latest "flux"
 import "strings"
 
 from(bucket: "example-bucket")
-  |> range(start: -1h)
-  |> filter(fn: (r) =>
-    r._measurement == "weather" and
-    r._field == "temp"
-  )
-  |> map(fn: (r) => ({
-    r with
-    location: strings.toTitle(v: r.location),
-    sensor: strings.replaceAll(v: r.sensor, t: " ", u: "-"),
-    status: strings.substring(v: r.status, start: 0, end: 8)
-  }))
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "weather" and r._field == "temp")
+    |> map(
+        fn: (r) => ({
+            r with
+            location: strings.toTitle(v: r.location),
+            sensor: strings.replaceAll(v: r.sensor, t: " ", u: "-"),
+            status: strings.substring(v: r.status, start: 0, end: 8),
+        })
+    )
 ```
 
 ### Work with geo-temporal data
@@ -307,14 +261,11 @@ let you shape, filter, and group geo-temporal data.
 import "experimental/geo"
 
 from(bucket: "geo/autogen")
-  |> range(start: -1w)
-  |> filter(fn: (r) => r._measurement == "taxi")
-  |> geo.shapeData(latField: "latitude", lonField: "longitude", level: 20)
-  |> geo.filterRows(
-    region: {lat: 40.69335938, lon: -73.30078125, radius: 20.0},
-    strict: true
-  )
-  |> geo.asTracks(groupBy: ["fare-id"])
+    |> range(start: -1w)
+    |> filter(fn: (r) => r._measurement == "taxi")
+    |> geo.shapeData(latField: "latitude", lonField: "longitude", level: 20)
+    |> geo.filterRows(region: {lat: 40.69335938, lon: -73.30078125, radius: 20.0}, strict: true)
+    |> geo.asTracks(groupBy: ["fare-id"])
 ```
 
 
diff --git a/content/influxdb/v2.1/reference/syntax/line-protocol.md b/content/influxdb/v2.1/reference/syntax/line-protocol.md
index 8e3c4b026..722acb008 100644
--- a/content/influxdb/v2.1/reference/syntax/line-protocol.md
+++ b/content/influxdb/v2.1/reference/syntax/line-protocol.md
@@ -14,6 +14,8 @@ aliases:
   - /influxdb/v2.1/write_protocols/line_protocol_reference/
 related:
   - /influxdb/v2.1/write-data/
+  - /influxdb/v2.1/reference/key-concepts/data-elements/
+  - /influxdb/v2.1/write-data/best-practices/schema-design/
 ---
 
 InfluxDB uses line protocol to write data points.
@@ -26,25 +28,38 @@ It is a text-based format that provides the measurement, tag set, field set, and
 - [Comments](#comments)
 - [Naming restrictions](#naming-restrictions)
 - [Duplicate points](#duplicate-points)
+- [Out of range values](#out-of-range-values)
+- [Parse errors](#parse-errors)
 
-```js
-// Syntax
+#### Syntax
+
+```py
+# Line protocol syntax
 <measurement>[,<tag_key>=<tag_value>[,<tag_key>=<tag_value>]] <field_key>=<field_value>[,<field_key>=<field_value>] [<timestamp>]
+```
+#### Example
 
-// Example
+```py
+# Line protocol example
 myMeasurement,tag1=value1,tag2=value2 fieldKey="fieldValue" 1556813561098000000
 ```
 
-Lines separated by the newline character `\n` represent a single point
-in InfluxDB. Line protocol is whitespace sensitive.
+## Lines
 
-{{% note %}}
-Line protocol does not support the newline character `\n` in tag or field values.
-{{% /note %}}
+Line protocol consists of zero or more entries, each terminated by the newline character (`\n`).
+A line contains one of the following:
+- [data point](#elements-of-line-protocol) that represents a [point](/influxdb/v2.1/reference/key-concepts/data-elements) in InfluxDB
+- blank line that consists entirely of [whitespace](#whitespace)
+- [comment](#comments) that starts with `#` optionally preceded by whitespace.
+
+Line protocol is [whitespace-sensitive](#whitespace).
+Line protocol string elements may support certain [special characters](#special-characters).
 
 ## Elements of line protocol
 
-```
+Lines that represent data points contain a [measurement name](#measurement), optional [tags](#tag-set), at least one [field](#field-set), and an optional [timestamp](#timestamp).
+
+```js
 measurementName,tagKey=tagValue fieldKey="fieldValue" 1465839830100400200
 --------------- --------------- --------------------- -------------------
        |               |                  |                    |
@@ -52,6 +67,7 @@ measurementName,tagKey=tagValue fieldKey="fieldValue" 1465839830100400200
 ```
 
 ### Measurement
+
 ({{< req >}})
 The measurement name.
 InfluxDB accepts one measurement per point.
@@ -59,11 +75,17 @@ _Measurement names are case-sensitive and subject to [naming restrictions](#nami
 
 _**Data type:** [String](#string)_
 
+{{% note %}}
+
+To learn more about designing efficient measurements for InfluxDB, see [best practices for schema design](/influxdb/v2.1/write-data/best-practices/schema-design/).
+
+{{% /note %}}
 
 ### Tag set
+
 _**Optional**_ –
-All tag key-value pairs for the point.
-Key-value relationships are denoted with the `=` operand.
+All [tag](/influxdb/v2.1/reference/key-concepts/data-elements/#tags) key-value pairs for the point.
+Key-value relationships are denoted by the `=` operand.
 Multiple tag key-value pairs are comma-delimited.
 _Tag keys and tag values are case-sensitive.
 Tag keys are subject to [naming restrictions](#naming-restrictions)._
@@ -71,9 +93,28 @@ Tag keys are subject to [naming restrictions](#naming-restrictions)._
 _**Key data type:** [String](#string)_  
 _**Value data type:** [String](#string)_
 
+#### Canonical form
+
+**Canonical form** describes a [tag set](/influxdb/v2.1/reference/key-concepts/data-elements/#tag-set) in which the tags' decoded values are in lexical order, lowest to highest.
+Line protocol consumers are often more efficient at decoding points with tags in canonical form.
+
+The data point in the following example has a tag set in canonical form:
+
+```py
+# The tag set below is in canonical form.
+foo,a\ b=x,aB=y value=99
+```
+
+{{% note %}}
+
+To learn more about designing efficient tags for InfluxDB, see [best practices for schema design](/influxdb/v2.1/write-data/best-practices/schema-design/).
+
+{{% /note %}}
+
 ### Field set
+
 ({{< req >}})
-All field key-value pairs for the point.
+All [field](/influxdb/v2.1/reference/key-concepts/data-elements/#fields) key-value pairs for the point.
 Points must have at least one field.
 _Field keys and string values are case-sensitive.
 Field keys are subject to [naming restrictions](#naming-restrictions)._
@@ -82,35 +123,51 @@ _**Key data type:** [String](#string)_
 _**Value data type:** [Float](#float) | [Integer](#integer) | [UInteger](#uinteger) | [String](#string) | [Boolean](#boolean)_
 
 {{% note %}}
-_Always double quote string field values. More on quotes [below](#quotes)._
 
-```sh
-measurementName fieldKey="field string value" 1556813561098000000
+Always double quote string field values. Learn more about using [quotes in line protocol](#quotes).
+
+```py
+measurementName fieldKey="string field value" 1556813561098000000
+measurementName fieldKey="\"quoted words\" in a string field value" 1556813561098000000
 ```
+
+{{% /note %}}
+
+{{% note %}}
+
+To learn more about designing efficient fields for InfluxDB, see [best practices for schema design](/influxdb/v2.1/write-data/best-practices/schema-design/).
+
 {{% /note %}}
 
 ### Timestamp
+
 _**Optional**_ –
-The [unix timestamp](/influxdb/v2.1/reference/glossary/#unix-timestamp) for the data point.
+Unix timestamp for the data point.
 InfluxDB accepts one timestamp per point.
-If no timestamp is provided, InfluxDB uses the system time (UTC) of its host machine.
+
+If no timestamp is provided, InfluxDB uses the system time (UTC) of its host machine. To ensure a data point includes the time a metric is observed (not received by InfluxDB), include the timestamp.
+
+Nanoseconds is the default precision for timestamps. If your timestamps are not in nanoseconds, specify the precision when [writing the data to InfluxDB](/influxdb/v2.1/write-data/#timestamp-precision).
 
 _**Data type:** [Unix timestamp](#unix-timestamp)_
 
-{{% note %}}
-#### Important notes about timestamps
-- To ensure a data point includes the time a metric is observed (not received by InfluxDB),
-  include the timestamp.
-- If your timestamps are not in nanoseconds, specify the precision of your timestamps
-  when [writing the data to InfluxDB](/influxdb/v2.1/write-data/#timestamp-precision).
-{{% /note %}}
+#### Example
+
+```py
+myMeasurementName fieldKey="fieldValue" 1556813561098000000
+                                        -------------------
+                                                  |
+                                              Timestamp
+```
 
 ### Whitespace
-Whitespace in line protocol determines how InfluxDB interprets the data point.
-The **first unescaped space** delimits the measurement and the tag set from the field set.
-The **second unescaped space** delimits the field set from the timestamp.
 
-```
+Whitespace in line protocol determines how InfluxDB interprets the data point.
+Allowed whitespace characters are regular spaces (` `) and carriage-returns (`\r`). Carriage-returns (`\r`) are only allowed as whitespace when they immediately precede a newline (`\n`).
+The **first unescaped space** after the start of the measurement delimits the [measurement](#measurement) and the [tag set](#tag-set) from the [field set](#field-set).
+The **second unescaped space** delimits the field set from the [timestamp](#timestamp).
+
+```js
 measurementName,tagKey=tagValue fieldKey="fieldValue" 1465839830100400200
                                |                     |
                            1st space             2nd space
@@ -118,19 +175,30 @@ measurementName,tagKey=tagValue fieldKey="fieldValue" 1465839830100400200
 
 ## Data types and format
 
-### Float
-IEEE-754 64-bit floating-point numbers.
-Default numerical type.
-_InfluxDB supports scientific notation in float field values._
+### Character set
 
-##### Float field value examples
-```js
+Line protocol is composed of Unicode characters encoded in UTF-8. Non-printable ASCII characters (0x00 - 0x1f and 0x7f) are not allowed.
+
+### Float
+
+64-bit floating-point numbers. Note that non-finite numbers (NaN and Inf) are not allowed.
+Default numerical type.
+
+#### Float field value examples
+
+```py
 myMeasurement fieldKey=1.0
 myMeasurement fieldKey=1
-myMeasurement fieldKey=-1.234456e+78
 ```
 
+InfluxDB supports scientific notation in float field values.
+
+```py
+myMeasurement fieldKey=-1.234456e+78
+
+```
 ### Integer
+
 Signed 64-bit integers.
 Trailing `i` on the number specifies an integer.
 
@@ -138,14 +206,16 @@ Trailing `i` on the number specifies an integer.
 | ---------------         | ---------------        |
 | `-9223372036854775808i` | `9223372036854775807i` |
 
-##### Integer field value examples
-```js
+#### Integer field value examples
+
+```py
 myMeasurement fieldKey=1i
 myMeasurement fieldKey=12485903i
 myMeasurement fieldKey=-12485903i
 ```
 
 ### UInteger
+
 Unsigned 64-bit integers.
 Trailing `u` on the number specifies an unsigned integer.
 
@@ -153,23 +223,27 @@ Trailing `u` on the number specifies an unsigned integer.
 | ---------------- | ----------------        |
 | `0u`             | `18446744073709551615u` |
 
-##### UInteger field value examples
-```js
+#### UInteger field value examples
+
+```py
 myMeasurement fieldKey=1u
 myMeasurement fieldKey=12485903u
 ```
 
 ### String
-Plain text string.
-Length limit 64KB.
 
-##### String example
-```sh
+Plain text string.
+Length limit is 1.8432MB. 64K is the recommended length limit.
+
+#### String example
+
+```py
 # String measurement name, field key, and field value
 myMeasurement fieldKey="this is a string"
 ```
 
 ### Boolean
+
 Stores `true` or `false` values.
 
 | Boolean value | Accepted syntax                     |
@@ -177,8 +251,9 @@ Stores `true` or `false` values.
 | True          | `t`, `T`, `true`, `True`, `TRUE`    |
 | False         | `f`, `F`, `false`, `False`, `FALSE` |
 
-##### Boolean field value examples
-```js
+#### Boolean field value examples
+
+```py
 myMeasurement fieldKey=true
 myMeasurement fieldKey=false
 myMeasurement fieldKey=t
@@ -188,55 +263,73 @@ myMeasurement fieldKey=FALSE
 ```
 
 {{% note %}}
+
 Do not quote boolean field values.
 Quoted field values are interpreted as strings.
+
 {{% /note %}}
 
 ### Unix timestamp
-Unix timestamp in a [specified precision](/influxdb/v2.1/reference/glossary/#unix-timestamp).
-Default precision is nanoseconds (`ns`).
+
+[Unix timestamp](/influxdb/v2.1/reference/glossary/#unix-timestamp) within the range `1677-09-21T00:12:43.145224194Z` to `2262-04-11T23:47:16.854775806Z` (i.e., almost the range of a 64-bit signed integer when expressed as nanoseconds from the epoch, but with a few nanoseconds removed at either end to allow for sentinel values).
 
 | Minimum timestamp      | Maximum timestamp     |
 | -----------------      | -----------------     |
 | `-9223372036854775806` | `9223372036854775806` |
 
-##### Unix timestamp example
-```js
-myMeasurementName fieldKey="fieldValue" 1556813561098000000
+## Special characters
+
+- Line protocol supports special characters in [string elements](#string).
+- Line protocol supports both literal backslashes and backslashes as an escape character.
+
+The following contexts require [escaping](#escaping-backslashes) certain characters with a backslash (`\`):
+
+### Escaping rules
+
+| Escape sequence | Supported in elements |
+|:----------------|:----------------------|
+| `\n` is replaced with `U+000A` (newline) | string field values |
+| `\r` is replaced with `U+000D` (carriage-return) | string field values |
+| `\t` is replaced with `U+0009` (tab) | string field values |
+| `\ ` is replaced with `U+0020` (space) | all except string field values |
+| `\,` is replaced with `,` | all except string field values |
+| `\=` is replaced with `=` | all except string field values and measurements |
+| `\”` is replaced with `”` | string field values |
+| `\\` is replaced with `\` | string field values |
+
+To unescape a character within a backslash escape sequence, InfluxDB removes _the last backslash_ and its following character and replaces them with the replacement character.
+If the backslash is followed by a character that the line protocol element doesn't support, InfluxDB leaves the backslash and the following character in place, unchanged.
+
+The [escaping rules](#escaping-rules) imply the following for [tag keys](/influxdb/v2.1/reference/glossary/#tag-key), [tag values](/influxdb/v2.1/reference/glossary/#tag-value), [field keys](/influxdb/v2.1/reference/glossary/#field-key), and [measurements](/influxdb/v2.1/reference/glossary/#measurement):
+- they cannot end with a backslash (`\`).
+- they accept double quote (`"`) and single quote (`'`) characters as part of the name, key, or value.
+
+In _string_ [field values](/influxdb/v2.1/reference/glossary/#field-value) with two contiguous backslashes, the first backslash is interpreted as an escape character.
+
+Given the following line protocol:
+
+```py
+# Escaped = in tag value.
+# Literal backslash at start of string field value.
+# Escaped backslash at end of string field value.
+airSensor,sensor_id=TLM\=0201 desc="\=My data==\\"
+
+# Measurement name with literal backslashes.
+# Escaped = in tag value.
+# Escaped \ and escaped " in string field value.
+air\\\\\Sensor,sensor_id=TLM\=0201 desc="\\\"==My data\==\\"
 ```
 
-## Quotes
-Line protocol supports single and double quotes as described in the following table:
+InfluxDB writes the following points:
 
-| Element     | Double quotes                           | Single quotes                           |
-| :------     | :------------:                          |:-------------:                          |
-| Measurement | _Limited_ <sup class="required">*</sup> | _Limited_ <sup class="required">*</sup> |
-| Tag key     | _Limited_ <sup class="required">*</sup> | _Limited_ <sup class="required">*</sup> |
-| Tag value   | _Limited_ <sup class="required">*</sup> | _Limited_ <sup class="required">*</sup> |
-| Field key   | _Limited_ <sup class="required">*</sup> | _Limited_ <sup class="required">*</sup> |
-| Field value | **Strings only**                        | Never                                   |
-| Timestamp   | Never                                   | Never                                   |
+| _measurement     | _sensor_id | _field     | _value |
+|:-----------------|------------|------------|--------|
+| `airSensor`      | `TLM=0201` | `desc`     | `\=My data==\`        |
+| `air\\\\\Sensor` | `TLM=0201` | `desc`     | `\"==My data\==\`     |
 
-<sup class="required">\*</sup> _Line protocol accepts double and single quotes in
-measurement names, tag keys, tag values, and field keys, but interprets them as
-part of the name, key, or value._
+#### Examples of special characters in line protocol
 
-## Special Characters
-Line protocol supports special characters in [string elements](#string).
-In the following contexts, it requires escaping certain characters with a backslash (`\`):
-
-| Element     | Escape characters         |
-|:-------     |:-----------------         |
-| Measurement | Comma, Space              |
-| Tag key     | Comma, Equals Sign, Space |
-| Tag value   | Comma, Equals Sign, Space |
-| Field key   | Comma, Equals Sign, Space |
-| Field value | Double quote, Backslash   |
-
-You do not need to escape other special characters.
-
-##### Examples of special characters in line protocol
-```sh
+```py
 # Measurement name with spaces
 my\ Measurement fieldKey="string value"
 
@@ -246,39 +339,53 @@ myMeasurement fieldKey="\"string\" within a string"
 # Tag keys and values with spaces
 myMeasurement,tag\ Key1=tag\ Value1,tag\ Key2=tag\ Value2 fieldKey=100
 
+# Measurement name and tag key with quotes
+joe'smeasurement,pat'sTag=tag1 fieldKey=100
+
 # Emojis
 myMeasurement,tagKey=🍭 fieldKey="Launch 🚀" 1556813561098000000
 ```
 
-### Escaping backslashes
-Line protocol supports both literal backslashes and backslashes as an escape character.
-With two contiguous backslashes, the first is interpreted as an escape character.
-For example:
-
-| Backslashes | Interpreted as |
-|:-----------:|:-------------:|
-| `\`         | `\`           |
-| `\\`        | `\`           |
-| `\\\`       | `\\`          |
-| `\\\\`      | `\\`          |
-| `\\\\\`     | `\\\`         |
-| `\\\\\\`    | `\\\`         |
-
 ## Comments
-Line protocol interprets `#` at the beginning of a line as a comment character
+
+If a line contains `#` as the first non-whitespace character, line protocol interprets it as a comment
 and ignores all subsequent characters until the next newline `\n`.
 
-```sh
+```py
 # This is a comment
 myMeasurement fieldKey="string value" 1556813561098000000
 ```
 
 ## Naming restrictions
-Measurement names, tag keys, and field keys cannot begin with an underscore `_`.
-The `_` namespace is reserved for InfluxDB system use.
+
+InfluxDB reserves the underscore (`_`) namespace and certain words for system use.
+- Measurement names, tag keys, and field keys cannot begin with an underscore (`_`).
+- Tag keys and tag values cannot end with a backslash (`\`).
+- Tag keys and field keys cannot be named `time`.
+- Tag keys cannot be named `field`.
+
+To make your schema easier to query, [avoid using Flux keywords and special characters](/influxdb/v2.1/write-data/best-practices/schema-design/#keep-keys-simple) in keys.
 
 ## Duplicate points
+
 A point is uniquely identified by the measurement name, tag set, and timestamp.
 If you submit line protocol with the same measurement, tag set, and timestamp,
 but with a different field set, the field set becomes the union of the old
 field set and the new field set, where any conflicts favor the new field set.
+
+See how InfluxDB [handles duplicate points](/influxdb/v2.1/write-data/best-practices/duplicate-points/).
+
+## Out of range values
+
+Fields can contain numeric values, which have the potential for falling outside supported ranges.
+Integer and float values should be considered **out of range** if they can't fit within a 64-bit value of the appropriate type. Out of range values may cause [parsing errors](#parsing-errors).
+
+For detail about supported ranges, see the minimum and maximum values for [data types](#data-types-and-format).
+
+## Parse errors
+
+When a line protocol decoder encounters an invalid line, tag, or field (e.g., with an [out-of-range value](#out-of-range-values)),
+the decoder may choose to recover from the error by ignoring the offending value or it may fail the decoding.
+One common approach to handling syntax errors is for the decoder to recover by discarding data until the next newline character and then resume parsing.
+
+See [how to troubleshoot issues writing data](/influxdb/v2.1/write-data/troubleshoot/) to InfluxDB.
diff --git a/content/influxdb/v2.1/security/secrets/use.md b/content/influxdb/v2.1/security/secrets/use.md
index 6dae06b7d..e7cf98c6b 100644
--- a/content/influxdb/v2.1/security/secrets/use.md
+++ b/content/influxdb/v2.1/security/secrets/use.md
@@ -22,8 +22,8 @@ username = secrets.get(key: "POSTGRES_USERNAME")
 password = secrets.get(key: "POSTGRES_PASSWORD")
 
 sql.from(
-  driverName: "postgres",
-  dataSourceName: "postgresql://${username}:${password}@localhost",
-  query:"SELECT * FROM example-table"
+    driverName: "postgres",
+    dataSourceName: "postgresql://${username}:${password}@localhost",
+    query:"SELECT * FROM example-table",
 )
 ```
diff --git a/content/influxdb/v2.1/security/tokens/create-token.md b/content/influxdb/v2.1/security/tokens/create-token.md
index d6b90c8d2..0aaf67db5 100644
--- a/content/influxdb/v2.1/security/tokens/create-token.md
+++ b/content/influxdb/v2.1/security/tokens/create-token.md
@@ -165,7 +165,7 @@ See the [`influx auth create` documentation](/{{< latest "influxdb" >}}/referenc
 
 Use the `/authorizations` endpoint of the InfluxDB API to create a token.
 
-[{{< api-endpoint method="POST" endpoint="http://localhost:8086/api/v2/authorizations" >}}]((/influxdb/v2.1/api/#operation/PostAuthorizations))
+[{{< api-endpoint method="POST" endpoint="http://localhost:8086/api/v2/authorizations" >}}](/influxdb/v2.1/api/#operation/PostAuthorizations)
 
 Include the following in your request:
 
diff --git a/content/influxdb/v2.1/security/tokens/use-tokens.md b/content/influxdb/v2.1/security/tokens/use-tokens.md
index 6b97a39fc..0d3f5bedf 100644
--- a/content/influxdb/v2.1/security/tokens/use-tokens.md
+++ b/content/influxdb/v2.1/security/tokens/use-tokens.md
@@ -17,11 +17,11 @@ Authenticate requests using the [`influx` CLI](/influxdb/v2.1/reference/cli/infl
 ### Add a token to a CLI request
 
 ```sh
-influx write -t <token> -b BUCKET -o org-name <LINE PROTOCOL>
+influx write -t <INFLUX_TOKEN> -b <BUCKET_NAME> -o org-name <LINE_PROTOCOL>
 ```
 
 ```
-export INFLUX_TOKEN=my-token
+export INFLUX_TOKEN=<INFLUX_TOKEN>
 influx write -t $INFLUX_TOKEN -b my-bucket -o my-org "measurement field=1"
 ```
 
diff --git a/content/influxdb/v2.1/tools/grafana.md b/content/influxdb/v2.1/tools/grafana.md
index 3dfae4005..8d135e262 100644
--- a/content/influxdb/v2.1/tools/grafana.md
+++ b/content/influxdb/v2.1/tools/grafana.md
@@ -59,10 +59,11 @@ configure your InfluxDB connection:
     - **Default Bucket**: The default [bucket](/influxdb/v2.1/organizations/buckets/) to use in Flux queries.
     - **Min time interval**: The [Grafana minimum time interval](https://grafana.com/docs/grafana/latest/features/datasources/influxdb/#min-time-interval).
 
-    {{< img-hd src="/img/influxdb/2-0-tools-grafana.png" />}}
-
 2. Click **Save & Test**. Grafana attempts to connect to the InfluxDB {{< current-version >}} datasource
    and returns the results of the test.
+
+{{< img-hd src="/img/influxdb/2-0-tools-grafana.png" />}}
+
 {{% /tab-content %}}
 <!----------------------------- END FLUX CONTENT ----------------------------->
 <!-------------------------- BEGIN INFLUXQL CONTENT -------------------------->
@@ -238,11 +239,11 @@ With **InfluxQL** selected as the query language in your InfluxDB data source se
         - **Password**: Enter the password associated with your [InfluxDB 1.x compatibility authorization](#view-and-create-influxdb-dbrp-mappings)
         - **HTTP Method**: Select **GET**
 
-        <!--  -->
-        {{< img-hd src="/img/influxdb/2-0-tools-grafana-influxql.png" />}}
-
 3. Click **Save & Test**. Grafana attempts to connect to the InfluxDB {{< current-version >}} data source
    and returns the results of the test.
+
+{{< img-hd src="/img/influxdb/2-0-tools-grafana-influxql.png" />}}
+
 {{% /tab-content %}}
 <!--------------------------- END INFLUXQL CONTENT --------------------------->
 {{< /tabs-wrapper >}}
diff --git a/content/influxdb/v2.1/tools/kapacitor.md b/content/influxdb/v2.1/tools/kapacitor.md
index 2f503cf23..807ef2e16 100644
--- a/content/influxdb/v2.1/tools/kapacitor.md
+++ b/content/influxdb/v2.1/tools/kapacitor.md
@@ -95,7 +95,7 @@ see [Write back to InfluxDB](#write-back-to-influxdb) below.
 InfluxDB Cloud and OSS {{< current-version >}} do not have subscription APIs and do not support Kapacitor stream tasks directly.
 To use Kapacitor stream tasks, write data directly to Kapacitor using the [Kapcitior `write` API](/{{< latest "kapacitor" >}}/working/api/#writing-data).
 
-We recommend using [Telegraf InfluxDB output plugin](/{{< latest "telegraf" >}}/plugins/#influxdb)
+We recommend using [Telegraf InfluxDB output plugin](/{{< latest "telegraf" >}}/plugins/#output-influxdb)
 to write data to both InfluxDB Cloud or OSS and Kapacitor.
 The following example Telegraf configuration writes data to both InfluxDB and Kapacitor:
 
diff --git a/content/influxdb/v2.1/tools/repl.md b/content/influxdb/v2.1/tools/repl.md
index 2af07f805..e3390805d 100644
--- a/content/influxdb/v2.1/tools/repl.md
+++ b/content/influxdb/v2.1/tools/repl.md
@@ -38,9 +38,10 @@ To query data from InfluxDB (local or remote), provide the host, organization, a
 to the [`from()` function](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/from/).
 
 ```js
-  host: "http://localhost:8086",
-  org: "example-org",
-  token: "My5uP3rS3cRetT0k3n"
+from(
+    host: "http://localhost:8086",
+    org: "example-org",
+    token: "My5uP3rS3cRetT0k3n",
 )
 ```
 
diff --git a/content/influxdb/v2.1/upgrade/v1-to-v2/automatic-upgrade.md b/content/influxdb/v2.1/upgrade/v1-to-v2/automatic-upgrade.md
index 804b4af58..9cb6ddac3 100644
--- a/content/influxdb/v2.1/upgrade/v1-to-v2/automatic-upgrade.md
+++ b/content/influxdb/v2.1/upgrade/v1-to-v2/automatic-upgrade.md
@@ -77,8 +77,8 @@ You can continue to use Kapacitor with InfluxDB OSS {{< current-version >}} unde
   Existing Kapacitor user credentials should continue to work using the [1.x compatibility API](/influxdb/v2.1/reference/api/influxdb-1x/).
 - InfluxDB {{< current-version >}} has no subscriptions API and does not support Kapacitor stream tasks.
   To continue using stream tasks, write data directly to both InfluxDB and Kapacitor.
-  Use **Telegraf** and its [InfluxDB output plugin](/{{< latest "telegraf" >}}/plugins/#influxdb)
-  to write to Kapacitor and the [InfluxDB v2 output plugin](/{{< latest "telegraf" >}}/plugins/#influxdb_v2) to write to InfluxDB v2.
+  Use **Telegraf** and its [InfluxDB output plugin](/{{< latest "telegraf" >}}/plugins/#output-influxdb)
+  to write to Kapacitor and the [InfluxDB v2 output plugin](/{{< latest "telegraf" >}}/plugins/#output-influxdb_v2) to write to InfluxDB v2.
 
 ##### Example Telegraf configuration
 ```toml
diff --git a/content/influxdb/v2.1/upgrade/v1-to-v2/migrate-cqs.md b/content/influxdb/v2.1/upgrade/v1-to-v2/migrate-cqs.md
index 06cd09a04..7a92ff52d 100644
--- a/content/influxdb/v2.1/upgrade/v1-to-v2/migrate-cqs.md
+++ b/content/influxdb/v2.1/upgrade/v1-to-v2/migrate-cqs.md
@@ -69,21 +69,15 @@ END
 
 ##### Equivalent Flux task
 ```js
-option task = {
-  name: "downsample-daily",
-  every: 1d
-}
+option task = {name: "downsample-daily", every: 1d}
 
 from(bucket: "my-db/")
-  |> range(start: -task.every)
-  |> filter(fn: (r) => r._measurement == "example-measurement")
-  |> filter(fn: (r) => r._field == "example-field")
-  |> aggregateWindow(every: 1h, fn: mean)
-  |> set(key: "_measurement", value: "average-example-measurement")
-  |> to(
-    org: "example-org",
-    bucket: "my-db/example-rp"
-  )
+    |> range(start: -task.every)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> filter(fn: (r) => r._field == "example-field")
+    |> aggregateWindow(every: 1h, fn: mean)
+    |> set(key: "_measurement", value: "average-example-measurement")
+    |> to(org: "example-org", bucket: "my-db/example-rp")
 ```
 
 ### Convert InfluxQL continuous queries to Flux
@@ -115,7 +109,7 @@ CREATE CONTINUOUS QUERY "downsample-daily" ON "my-db"
 ###### Flux
 ```js
 from(bucket: "my-db/")
-// ...
+    // ...
 ```
 
 #### SELECT statement
@@ -153,15 +147,15 @@ INTO "example-db"."example-rp"."example-measurement"
 {{% code-tab-content %}}
 ```js
 // ...
-  |> set(key: "_measurement", value: "example-measurement")
-  |> to(bucket: "example-db/example-rp")
+    |> set(key: "_measurement", value: "example-measurement")
+    |> to(bucket: "example-db/example-rp")
 ```
 {{% /code-tab-content %}}
 {{% code-tab-content %}}
 ```js
 // ...
-  |> map(fn: (r) => ({ r with _measurement: "example-measurement"}))
-  |> to(bucket: "example-db/example-rp")
+    |> map(fn: (r) => ({ r with _measurement: "example-measurement"}))
+    |> to(bucket: "example-db/example-rp")
 ```
 {{% /code-tab-content %}}
 {{< /code-tabs-wrapper >}}
@@ -192,12 +186,12 @@ END
 // ...
 
 from(bucket: "my-db/")
-  |> range(start: -task.every)
-  |> filter(fn: (r) => r._measurement == "example-measurement")
-  |> filter(fn: (r) => r._field == "example-field-1" or r._field == "example-field-2")
-  |> aggregateWindow(every: task.every, fn: mean)
-  |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
-  |> experimental.to(bucket: "example-db/example-rp")
+    |> range(start: -task.every)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> filter(fn: (r) => r._field == "example-field-1" or r._field == "example-field-2")
+    |> aggregateWindow(every: task.every, fn: mean)
+    |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
+    |> experimental.to(bucket: "example-db/example-rp")
 ```
 
 #### FROM clause
@@ -215,7 +209,7 @@ FROM "example-measurement"
 ###### Flux
 ```js
 // ...
-  |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> filter(fn: (r) => r._measurement == "example-measurement")
 ```
 
 #### AS clause
@@ -240,13 +234,13 @@ AS newfield
 {{% code-tab-content %}}
 ```js
 // ...
-  |> set(key: "_field", value: "newfield")
+    |> set(key: "_field", value: "newfield")
 ```
 {{% /code-tab-content %}}
 {{% code-tab-content %}}
 ```js
 // ...
-  |> map(fn: (r) => ({ r with _field: "newfield"}))
+    |> map(fn: (r) => ({ r with _field: "newfield"}))
 ```
 {{% /code-tab-content %}}
 {{< /code-tabs-wrapper >}}
@@ -267,8 +261,8 @@ WHERE "example-tag" = "foo" AND time > now() - 7d
 ###### Flux
 ```js
 // ...
-  |> range(start: -7d)
-  |> filter(fn: (r) => r["example-tag"] == "foo")
+    |> range(start: -7d)
+    |> filter(fn: (r) => r["example-tag"] == "foo")
 ```
 
 #### GROUP BY clause
@@ -287,7 +281,7 @@ GROUP BY "location"
 ###### Flux
 ```js
 // ...
-  |> group(columns: ["location"])
+    |> group(columns: ["location"])
 ```
 
 ##### Group by time
@@ -306,17 +300,11 @@ GROUP BY time(1h)
 
 ###### Flux
 ```js
-option task = {
-  name: "task-name",
-  every: 1h
-}
+option task = {name: "task-name", every: 1h}
 
 // ...
-  |> filter(fn: (r) =>
-    r._measurement == "example-measurement" and
-    r._field == "example-field"
-  )
-  |> aggregateWindow(every: task.every, fn: mean)
+    |> filter(fn: (r) => r._measurement == "example-measurement" and r._field == "example-field")
+    |> aggregateWindow(every: task.every, fn: mean)
 ```
 
 #### RESAMPLE clause
@@ -345,22 +333,15 @@ END
 
 ###### Flux
 ```js
-option task = {
-  name: "resample-example",
-  every: 1m
-}
+option task = {name: "resample-example", every: 1m}
 
 from(bucket: "my-db/")
-  |> range(start: -30m)
-  |> filter(fn: (r) =>
-    r._measurement == "example-measurement" and
-    r._field == "example-field" and
-    r.region == "example-region"
-  )
-  |> aggregateWindow(every: 1m, fn: mean)
-  |> exponentialMovingAverage(n: 30)
-  |> set(key: "_measurement", value: "resample-average-example-measurement")
-  |> to(bucket: "my-db/")
+    |> range(start: -30m)
+    |> filter(fn: (r) => r._measurement == "example-measurement" and r._field == "example-field" and r.region == "example-region")
+    |> aggregateWindow(every: 1m, fn: mean)
+    |> exponentialMovingAverage(n: 30)
+    |> set(key: "_measurement", value: "resample-average-example-measurement")
+    |> to(bucket: "my-db/")
 ```
 
 ## Create new InfluxDB tasks
diff --git a/content/influxdb/v2.1/visualize-data/variables/_index.md b/content/influxdb/v2.1/visualize-data/variables/_index.md
index 7733db8fc..a841737a5 100644
--- a/content/influxdb/v2.1/visualize-data/variables/_index.md
+++ b/content/influxdb/v2.1/visualize-data/variables/_index.md
@@ -23,9 +23,9 @@ Reference each variable using dot-notation (e.g. `v.variableName`).
 
 ```js
 from(bucket: v.bucket)
-  |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
-  |> filter(fn: (r) => r._measurement == v.measurement and r._field == v.field)
-  |> aggregateWindow(every: v.windowPeriod, fn: mean)
+    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
+    |> filter(fn: (r) => r._measurement == v.measurement and r._field == v.field)
+    |> aggregateWindow(every: v.windowPeriod, fn: mean)
 ```
 
 When building Flux queries for dashboard cells, view available dashboard variables
diff --git a/content/influxdb/v2.1/visualize-data/variables/common-variables.md b/content/influxdb/v2.1/visualize-data/variables/common-variables.md
index 34347f615..38e7a4297 100644
--- a/content/influxdb/v2.1/visualize-data/variables/common-variables.md
+++ b/content/influxdb/v2.1/visualize-data/variables/common-variables.md
@@ -19,8 +19,8 @@ _**Flux functions:**
 
 ```js
 buckets()
-  |> rename(columns: {"name": "_value"})
-  |> keep(columns: ["_value"])
+    |> rename(columns: {"name": "_value"})
+    |> keep(columns: ["_value"])
 ```
 
 ## List measurements
@@ -45,9 +45,9 @@ _**Flux package:** [InfluxDB schema](/{{< latest "flux" >}}/stdlib/influxdata/in
 import "influxdata/influxdb/schema"
 
 schema.measurementTagValues(
-  bucket: "bucket-name",
-  measurement: "measurement-name",
-  tag: "_field"
+    bucket: "bucket-name",
+    measurement: "measurement-name",
+    tag: "_field",
 )
 ```
 
@@ -67,7 +67,7 @@ schema.tagValues(bucket: "bucket-name", tag: "host")
 ## List Docker containers
 List all Docker containers when using the Docker Telegraf plugin.
 
-_**Telegraf plugin:** [Docker](/{{< latest "telegraf" >}}/plugins/#docker)_  
+_**Telegraf plugin:** [Docker](/{{< latest "telegraf" >}}/plugins/#input-docker)_  
 _**Flux package:** [InfluxDB schema](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/)_  
 _**Flux functions:** [schema.tagValues()](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/tagvalues/)_
 
@@ -80,7 +80,7 @@ schema.tagValues(bucket: "bucket-name", tag: "container_name")
 ## List Kubernetes pods
 List all Kubernetes pods when using the Kubernetes Telegraf plugin.
 
-_**Telegraf plugin:** [Kubernetes](/{{< latest "telegraf" >}}/plugins/#kubernetes)_  
+_**Telegraf plugin:** [Kubernetes](/{{< latest "telegraf" >}}/plugins/#input-kubernetes)_  
 _**Flux package:** [InfluxDB schema](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/)_  
 _**Flux functions:** [schema.measurementTagValues()](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/measurementtagvalues/)_
 
@@ -88,16 +88,16 @@ _**Flux functions:** [schema.measurementTagValues()](/{{< latest "flux" >}}/stdl
 import "influxdata/influxdb/schema"
 
 schema.measurementTagValues(
-  bucket: "bucket-name",
-  measurement: "kubernetes_pod_container",
-  tag: "pod_name"
+    bucket: "bucket-name",
+    measurement: "kubernetes_pod_container",
+    tag: "pod_name",
 )
 ```
 
 ## List Kubernetes nodes
 List all Kubernetes nodes when using the Kubernetes Telegraf plugin.
 
-_**Telegraf plugin:** [Kubernetes](/{{< latest "telegraf" >}}/plugins/#kubernetes)_  
+_**Telegraf plugin:** [Kubernetes](/{{< latest "telegraf" >}}/plugins/#input-kubernetes)_  
 _**Flux package:** [InfluxDB schema](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/)_  
 _**Flux functions:** [schema.measurementTagValues()](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/measurementtagvalues/)_
 
@@ -105,8 +105,8 @@ _**Flux functions:** [schema.measurementTagValues()](/{{< latest "flux" >}}/stdl
 import "influxdata/influxdb/schema"
 
 schema.measurementTagValues(
-  bucket: "bucket-name",
-  measurement: "kubernetes_node",
-  tag: "node_name"
+    bucket: "bucket-name",
+    measurement: "kubernetes_node",
+    tag: "node_name",
 )
 ```
diff --git a/content/influxdb/v2.1/visualize-data/variables/variable-types.md b/content/influxdb/v2.1/visualize-data/variables/variable-types.md
index 091594572..8c25a0d7e 100644
--- a/content/influxdb/v2.1/visualize-data/variables/variable-types.md
+++ b/content/influxdb/v2.1/visualize-data/variables/variable-types.md
@@ -39,8 +39,8 @@ Query variable values are populated using the `_value` column of a Flux query.
 ```js
 // List all buckets
 buckets()
-  |> rename(columns: {"name": "_value"})
-  |> keep(columns: ["_value"])
+    |> rename(columns: {"name": "_value"})
+    |> keep(columns: ["_value"])
 ```
 
 _For examples of dashboard variable queries, see [Common variable queries](/influxdb/v2.1/visualize-data/variables/common-variables)._
@@ -83,10 +83,10 @@ reference the variable with `v.exampleVar`:
 
 ```js
 from(bucket: "telegraf")
-  |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
-  |> filter(fn: (r) => r._measurement == "cpu" )
-  |> filter(fn: (r) => r._field == "usage_user" )
-  |> filter(fn: (r) => r.cpu == v.exampleVar)  
+    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
+    |> filter(fn: (r) => r._measurement == "cpu" )
+    |> filter(fn: (r) => r._field == "usage_user" )
+    |> filter(fn: (r) => r.cpu == v.exampleVar)  
 ```
 
 **To select variable values:**
diff --git a/content/influxdb/v2.1/visualize-data/visualization-types/band.md b/content/influxdb/v2.1/visualize-data/visualization-types/band.md
index 3a2f19d50..597a63ba5 100644
--- a/content/influxdb/v2.1/visualize-data/visualization-types/band.md
+++ b/content/influxdb/v2.1/visualize-data/visualization-types/band.md
@@ -49,34 +49,34 @@ To see bands (boundaries) in the **Band Plot** visualization, you must set up tw
 
 ```js
 from(bucket: "bucket_1")
-  |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
-  |> filter(fn: (r) => r["_measurement"] == "cpu")
-  |> filter(fn: (r) => r["_field"] == "usage_system")
-  |> filter(fn: (r) => r["cpu"] == "cpu0" or r["cpu"] == "cpu1")
-  |> aggregateWindow(every: 15s, fn: mean, createEmpty: false)
-  |> yield(name: "mean")
+    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
+    |> filter(fn: (r) => r["_measurement"] == "cpu")
+    |> filter(fn: (r) => r["_field"] == "usage_system")
+    |> filter(fn: (r) => r["cpu"] == "cpu0" or r["cpu"] == "cpu1")
+    |> aggregateWindow(every: 15s, fn: mean, createEmpty: false)
+    |> yield(name: "mean")
 
 from(bucket: "bucket_1")
-  |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
-  |> filter(fn: (r) => r["_measurement"] == "cpu")
-  |> filter(fn: (r) => r["_field"] == "usage_system")
-  |> filter(fn: (r) => r["cpu"] == "cpu0" or r["cpu"] == "cpu1")
-  |> aggregateWindow(every: 15s, fn: max, createEmpty: false)
-  |> yield(name: "max")
+    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
+    |> filter(fn: (r) => r["_measurement"] == "cpu")
+    |> filter(fn: (r) => r["_field"] == "usage_system")
+    |> filter(fn: (r) => r["cpu"] == "cpu0" or r["cpu"] == "cpu1")
+    |> aggregateWindow(every: 15s, fn: max, createEmpty: false)
+    |> yield(name: "max")
 
 from(bucket: "bucket_1")
-  |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
-  |> filter(fn: (r) => r["_measurement"] == "cpu")
-  |> filter(fn: (r) => r["_field"] == "usage_system")
-  |> filter(fn: (r) => r["cpu"] == "cpu0" or r["cpu"] == "cpu1")
-  |> aggregateWindow(every: 15s, fn: min, createEmpty: false)
-  |> yield(name: "min")
+    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
+    |> filter(fn: (r) => r["_measurement"] == "cpu")
+    |> filter(fn: (r) => r["_field"] == "usage_system")
+    |> filter(fn: (r) => r["cpu"] == "cpu0" or r["cpu"] == "cpu1")
+    |> aggregateWindow(every: 15s, fn: min, createEmpty: false)
+    |> yield(name: "min")
 ```
 
 5. (Optional) Customize the name of the yielded results for each function by editing the `name` parameter in the [`yield()`](/{{< latest "flux" >}}/stdlib/universe/yield/) function.
 For example, to change the name of the first function from  `mean` to `Average`, modify the last line to the following:
   ```js
-    |> yield(name: "Average")
+  |> yield(name: "Average")
   ```
 6. Click **Customize** in the upper left.
 7. Under **Aggregate Functions**, enter the functions you created to determine each boundary (column) for comparison. If you changed the `yield` name for any of the functions above, enter the modified name here instead of the function name:
diff --git a/content/influxdb/v2.1/visualize-data/visualization-types/gauge.md b/content/influxdb/v2.1/visualize-data/visualization-types/gauge.md
index 0cb3a6716..c96876d39 100644
--- a/content/influxdb/v2.1/visualize-data/visualization-types/gauge.md
+++ b/content/influxdb/v2.1/visualize-data/visualization-types/gauge.md
@@ -55,12 +55,8 @@ in a facility and displays it as a gauge.
 ###### Query pressure data from a specific sensor
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -1m)
-  |> filter(fn: (r) =>
-      r._measurement == "steam-sensors" and
-      r._field == "psi"
-      r.sensorID == "a211i"
-  )
+    |> range(start: -1m)
+    |> filter(fn: (r) => r._measurement == "steam-sensors" and r._field == "psi" and r.sensorID == "a211i")
 ```
 
 ###### Visualization options for pressure gauge
diff --git a/content/influxdb/v2.1/visualize-data/visualization-types/graph-single-stat.md b/content/influxdb/v2.1/visualize-data/visualization-types/graph-single-stat.md
index 2a69eaae9..323b3642c 100644
--- a/content/influxdb/v2.1/visualize-data/visualization-types/graph-single-stat.md
+++ b/content/influxdb/v2.1/visualize-data/visualization-types/graph-single-stat.md
@@ -130,11 +130,8 @@ The following example shows the current percentage of memory used as well as mem
 ###### Query memory usage percentage
 ```js
 from(bucket: "example-bucket")
-  |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
-  |> filter(fn: (r) =>
-      r._measurement == "mem" and
-      r._field == "used_percent"
-  )
+    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
 ```
 ###### Memory allocations percentage visualization with static legend
 {{< img-hd src="/img/influxdb/2-0-visualizations-graph-single-stat-mem-8.png" alt="Graph + Single Stat Memory Usage Example" />}}
diff --git a/content/influxdb/v2.1/visualize-data/visualization-types/heatmap.md b/content/influxdb/v2.1/visualize-data/visualization-types/heatmap.md
index 548807ec0..3e9eab3a8 100644
--- a/content/influxdb/v2.1/visualize-data/visualization-types/heatmap.md
+++ b/content/influxdb/v2.1/visualize-data/visualization-types/heatmap.md
@@ -92,19 +92,12 @@ Each row in the output table contains `_value_cpu` and `_value_mem` columns.
 
 ```js
 cpu = from(bucket: "example-bucket")
-  |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
-  |> filter(fn: (r) =>
-      r._measurement == "cpu" and
-      r._field == "usage_system" and
-      r.cpu == "cpu-total"
-  )
+    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_system" and r.cpu == "cpu-total")
 
 mem = from(bucket: "example-bucket")
-  |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
-  |> filter(fn: (r) =>
-      r._measurement == "mem" and
-      r._field == "used_percent"
-  )
+    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
 
 join(tables: {cpu: cpu, mem: mem}, on: ["_time"], method: "inner")
 ```
diff --git a/content/influxdb/v2.1/visualize-data/visualization-types/histogram.md b/content/influxdb/v2.1/visualize-data/visualization-types/histogram.md
index d93611207..cba27c3e9 100644
--- a/content/influxdb/v2.1/visualize-data/visualization-types/histogram.md
+++ b/content/influxdb/v2.1/visualize-data/visualization-types/histogram.md
@@ -73,11 +73,8 @@ _It utilizes data from the [Telegraf Syslog plugin](/{{< latest "telegraf" >}}/p
 ##### Query for errors by severity code
 ```js
 from(bucket: "example-bucket")
-  |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
-  |> filter(fn: (r) =>
-      r._measurement == "syslog" and
-      r._field == "severity_code"
-  )
+    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
+    |> filter(fn: (r) => r._measurement == "syslog" and r._field == "severity_code")
 ```
 
 ##### Histogram settings
diff --git a/content/influxdb/v2.1/visualize-data/visualization-types/mosaic.md b/content/influxdb/v2.1/visualize-data/visualization-types/mosaic.md
index 37295d177..21d6e8ce9 100644
--- a/content/influxdb/v2.1/visualize-data/visualization-types/mosaic.md
+++ b/content/influxdb/v2.1/visualize-data/visualization-types/mosaic.md
@@ -69,8 +69,8 @@ Use `level description` as the **Fill Column** in the [visualization controls](#
 
 ```js
 from(bucket: "noaa")
-  |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
-  |> filter(fn: (r) => r._measurement == "h2o_feet")
-  |> filter(fn: (r) => r._field == "level description")
-  |> aggregateWindow(every: v.windowPeriod, fn: last, createEmpty: false)
+    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
+    |> filter(fn: (r) => r._measurement == "h2o_feet")
+    |> filter(fn: (r) => r._field == "level description")
+    |> aggregateWindow(every: v.windowPeriod, fn: last, createEmpty: false)
 ```
diff --git a/content/influxdb/v2.1/visualize-data/visualization-types/scatter.md b/content/influxdb/v2.1/visualize-data/visualization-types/scatter.md
index 231b4ced2..5ceec8392 100644
--- a/content/influxdb/v2.1/visualize-data/visualization-types/scatter.md
+++ b/content/influxdb/v2.1/visualize-data/visualization-types/scatter.md
@@ -91,26 +91,14 @@ It scales the CPU usage metric to better align with baseline memory usage.
 
 ```js
 cpu = from(bucket: "example-bucket")
-  |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
-  |> filter(fn: (r) =>
-      r._measurement == "cpu" and
-      r._field == "usage_system" and
-      r.cpu == "cpu-total"
-  )
-  // Scale CPU usage
-  |> map(fn: (r) => ({
-      r with
-      _value: r._value + 60.0,
-      _time: r._time
-      })
-  )
+    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_system" and r.cpu == "cpu-total")
+    // Scale CPU usage
+    |> map(fn: (r) => ({r with _value: r._value + 60.0, _time: r._time}))
 
 mem = from(bucket: "example-bucket")
-  |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
-  |> filter(fn: (r) =>
-      r._measurement == "mem" and
-      r._field == "used_percent"
-  )
+    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
 
 union(tables: [cpu, mem])
 ```
diff --git a/content/influxdb/v2.1/visualize-data/visualization-types/single-stat.md b/content/influxdb/v2.1/visualize-data/visualization-types/single-stat.md
index 7f90578e3..e0eed5456 100644
--- a/content/influxdb/v2.1/visualize-data/visualization-types/single-stat.md
+++ b/content/influxdb/v2.1/visualize-data/visualization-types/single-stat.md
@@ -54,11 +54,8 @@ The following example shows the current memory usage displayed has a human-reada
 ###### Query memory usage percentage
 ```js
 from(bucket: "example-bucket")
-  |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
-  |> filter(fn: (r) =>
-      r._measurement == "mem" and
-      r._field == "used_percent"
-  )
+    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
 ```
 
 ###### Memory usage as a single stat
diff --git a/content/influxdb/v2.1/visualize-data/visualization-types/table.md b/content/influxdb/v2.1/visualize-data/visualization-types/table.md
index 0c18181d3..46c6d6585 100644
--- a/content/influxdb/v2.1/visualize-data/visualization-types/table.md
+++ b/content/influxdb/v2.1/visualize-data/visualization-types/table.md
@@ -63,15 +63,12 @@ The following example queries the latest reported memory usage from a cluster of
 ###### Query the latest memory usage from each host
 ```js
 from(bucket: "example-bucket")
-  |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
-  |> filter(fn: (r) =>
-      r._measurement == "mem" and
-      r._field == "used_percent"
-  )
-  |> group(columns: ["host"])
-  |> last()
-  |> group()
-  |> keep(columns: ["_value", "host"])
+    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+    |> group(columns: ["host"])
+    |> last()
+    |> group()
+    |> keep(columns: ["_value", "host"])
 ```
 
 ###### Cluster metrics in a table
diff --git a/content/influxdb/v2.1/write-data/_index.md b/content/influxdb/v2.1/write-data/_index.md
index 7a5f6be9f..4d80c817a 100644
--- a/content/influxdb/v2.1/write-data/_index.md
+++ b/content/influxdb/v2.1/write-data/_index.md
@@ -17,6 +17,7 @@ related:
   - /influxdb/v2.1/reference/syntax/line-protocol
   - /influxdb/v2.1/reference/syntax/annotated-csv
   - /influxdb/v2.1/reference/cli/influx/write
+  - /influxdb/v2.1/migrate-data/
   - /resources/videos/ingest-data/, How to Ingest Data in InfluxDB (Video)
 ---
 
@@ -28,6 +29,7 @@ related:
    - [Query and explore data](/influxdb/v2.1/query-data/)
    - [Process data](/influxdb/v2.1/process-data/)
    - [Visualize data](/influxdb/v2.1/visualize-data/)
+   - [Migrate data](/influxdb/v2.1/migrate-data/)
    - [Monitor and alert](/influxdb/v2.1/monitor-alert/)
 
 The following video discusses different ways to write data to InfluxDB:
diff --git a/content/influxdb/v2.1/write-data/best-practices/resolve-high-cardinality.md b/content/influxdb/v2.1/write-data/best-practices/resolve-high-cardinality.md
index 09030107f..c927c87fd 100644
--- a/content/influxdb/v2.1/write-data/best-practices/resolve-high-cardinality.md
+++ b/content/influxdb/v2.1/write-data/best-practices/resolve-high-cardinality.md
@@ -9,7 +9,8 @@ menu:
     parent: write-best-practices
 ---
 
-If reads and writes to InfluxDB have started to slow down, high [series cardinality](/influxdb/v2.1/reference/glossary/#series-cardinality) (too many series) may be causing memory issues.
+If reads and writes to InfluxDB have started to slow down, high [series cardinality](/influxdb/v2.1/reference/glossary/#series-cardinality) (too many series) may be causing memory issues. {{% cloud-only %}}Cardinality can also cause writes to fail if it exceeds your [plan’s adjustable service quota](/influxdb/cloud/account-management/limits/).{{% /cloud-only %}}
+
 Take steps to understand and resolve high series cardinality.
 
 1. [Learn the causes of high cardinality](#learn-the-causes-of-high-series-cardinality)
@@ -20,14 +21,14 @@ Take steps to understand and resolve high series cardinality.
 
 {{% oss-only %}}
 
-  IndexDB indexes the following data elements to speed up reads:
+  InfluxDB indexes the following data elements to speed up reads:
   - [measurement](/influxdb/v2.1/reference/glossary/#measurement)
   - [tags](/influxdb/v2.1/reference/glossary/#tag)
 
 {{% /oss-only %}}
 {{% cloud-only %}}
 
-  IndexDB indexes the following data elements to speed up reads:
+  InfluxDB indexes the following data elements to speed up reads:
   - [measurement](/influxdb/v2.1/reference/glossary/#measurement)
   - [tags](/influxdb/v2.1/reference/glossary/#tag)
   - [field keys](/influxdb/cloud/reference/glossary/#field-key)
@@ -76,17 +77,19 @@ The following example Flux query shows you which tags are contributing the most
 // Count unique values for each tag in a bucket
 import "influxdata/influxdb/schema"
 
-cardinalityByTag = (bucket) =>
-  schema.tagKeys(bucket: bucket)
-    |> map(fn: (r) => ({
-      tag: r._value,
-      _value:
-        if contains(set: ["_stop","_start"], value:r._value) then 0
-        else (schema.tagValues(bucket: bucket, tag: r._value)
-          |> count()
-          |> findRecord(fn: (key) => true, idx: 0))._value
-    }))
-    |> group(columns:["tag"])
+cardinalityByTag = (bucket) => schema.tagKeys(bucket: bucket)
+    |> map(
+        fn: (r) => ({
+            tag: r._value,
+            _value: if contains(set: ["_stop", "_start"], value: r._value) then
+                0
+            else
+                (schema.tagValues(bucket: bucket, tag: r._value)
+                    |> count()
+                    |> findRecord(fn: (key) => true, idx: 0))._value,
+        }),
+    )
+    |> group(columns: ["tag"])
     |> sum()
 
 cardinalityByTag(bucket: "example-bucket")
@@ -114,7 +117,7 @@ cardinalityByTag(bucket: "example-bucket")
     tag = "example-tag-key"
 
     schema.tagValues(bucket: "my-bucket", tag: tag)
-      |> count()
+        |> count()
     ```
 
 These queries should help identify the sources of high cardinality in each of your buckets. To determine which specific tags are growing, check the cardinality again after 24 hours to see if one or more tags have grown significantly.
diff --git a/content/influxdb/v2.1/write-data/best-practices/schema-design.md b/content/influxdb/v2.1/write-data/best-practices/schema-design.md
index 8ed79c535..c63e9ca65 100644
--- a/content/influxdb/v2.1/write-data/best-practices/schema-design.md
+++ b/content/influxdb/v2.1/write-data/best-practices/schema-design.md
@@ -109,9 +109,9 @@ The [Flux](/{{< latest "flux" >}}/) queries calculate the average `temp` for blu
 ```js
 // Query *Good Measurements*, data stored in separate tags (recommended)
 from(bucket:"example-bucket")
-  |> range(start:2016-08-30T00:00:00Z)
-  |> filter(fn: (r) =>  r._measurement == "weather_sensor" and r.region == "north" and r._field == "temp")
-  |> mean()
+    |> range(start:2016-08-30T00:00:00Z)
+    |> filter(fn: (r) =>  r._measurement == "weather_sensor" and r.region == "north" and r._field == "temp")
+    |> mean()
 ```
 
 **Difficult to query**: [_Bad Measurements_](#bad-measurements-schema) requires regular expressions to extract `plot` and `region` from the measurement, as in the following example.
@@ -119,9 +119,9 @@ from(bucket:"example-bucket")
 ```js
 // Query *Bad Measurements*, data encoded in the measurement (not recommended)
 from(bucket:"example-bucket")
-  |> range(start:2016-08-30T00:00:00Z)
-  |> filter(fn: (r) =>  r._measurement =~ /\.north$/ and r._field == "temp")
-  |> mean()
+    |> range(start:2016-08-30T00:00:00Z)
+    |> filter(fn: (r) =>  r._measurement =~ /\.north$/ and r._field == "temp")
+    |> mean()
 ```
 
 Complex measurements make some queries impossible. For example, calculating the average temperature of both plots is not possible with the [_Bad Measurements_](#bad-measurements-schema) schema.
@@ -134,10 +134,16 @@ In addition to keeping your keys free of data, follow these additional guideline
 
 ##### Avoid keywords and special characters in keys
 
-To simplify query writing, don't include reserved keywords or special characters in tag and field keys.
+To simplify query writing, don't include Flux keywords or special characters in tag and field keys.
 If you use [Flux keywords](/{{< latest "flux" >}}/spec/lexical-elements/#keywords) in keys,
 then you'll have to wrap the keys in double quotes.
-If you use non-alphanumeric characters in keys, then you'll have to use [bracket notation](/{{< latest "flux" >}}/data-types/composite/record/#bracket-notation) in [Flux]((/{{< latest "flux" >}}/).
+If you use non-alphanumeric characters in keys, then you'll have to use [bracket notation](/{{< latest "flux" >}}/data-types/composite/record/#bracket-notation) in [Flux](/{{< latest "flux" >}}/).
+
+{{% warn %}}
+
+InfluxDB doesn't allow writing points that use the following **reserved tag keys**: `time`, `field`, `_measurement`.
+
+{{% /warn %}}
 
 ##### Avoid duplicate names for tags and fields
 
@@ -158,6 +164,12 @@ Use [explicit bucket schemas]() to enforce unique tag and field keys within a sc
 This means that querying tags is more performant than querying fields.
 Your queries should guide what you store in tags and what you store in fields.
 
+{{% note %}}
+
+For more information about indexing and query performance, see how to [resolve high series cardinality](/influxdb/v2.1/write-data/best-practices/resolve-high-cardinality/).
+
+{{% /note %}}
+
 ### Use fields for unique and numeric data
 
 - Store unique or frequently changing values as field values.
@@ -174,8 +186,8 @@ For example, consider a bucket that stores data about thousands of users. With `
 
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -7d)
-  |> filter(fn: (r) => r._field == "userId" and r._value == "abcde")
+    |> range(start: -7d)
+    |> filter(fn: (r) => r._field == "userId" and r._value == "abcde")
 ```
 
 To retrieve data more quickly, filter on a tag to reduce the number of rows scanned.
@@ -184,9 +196,9 @@ The following query filters by the `company` tag to reduce the number of rows sc
 
 ```js
 from(bucket: "example-bucket")
-  |> range(start: -7d)
-  |> filter(fn: (r) => r.company == "Acme")
-  |> filter(fn: (r) => r._field == "userId" and r._value == "abcde")
+    |> range(start: -7d)
+    |> filter(fn: (r) => r.company == "Acme")
+    |> filter(fn: (r) => r._field == "userId" and r._value == "abcde")
 ```
 
 ### Keep tags simple
@@ -232,9 +244,9 @@ The [Flux](/{{< latest "flux" >}}/) queries calculate the average `temp` for blu
 ```js
 // Query *Good Tags* schema, data encoded in multiple tags
 from(bucket:"example-bucket")
-  |> range(start:2016-08-30T00:00:00Z)
-  |> filter(fn: (r) =>  r._measurement == "weather_sensor" and r.region == "north" and r._field == "temp")
-  |> mean()
+    |> range(start:2016-08-30T00:00:00Z)
+    |> filter(fn: (r) =>  r._measurement == "weather_sensor" and r.region == "north" and r._field == "temp")
+    |> mean()
 ```
 
 **Difficult to query**: [_Bad Tags_](#bad-tags-schema) requires regular expressions to parse the complex `location` values, as in the following example.
@@ -242,11 +254,11 @@ from(bucket:"example-bucket")
 ```js
 // Query *Bad Tags* schema, multiple data encoded in a single tag
 from(bucket:"example-bucket")
-  |> range(start:2016-08-30T00:00:00Z)
-  |> filter(fn: (r) =>  r._measurement == "weather_sensor" and r.location =~ /\.north$/ and r._field == "temp")
-  |> mean()
+    |> range(start:2016-08-30T00:00:00Z)
+    |> filter(fn: (r) =>  r._measurement == "weather_sensor" and r.location =~ /\.north$/ and r._field == "temp")
+    |> mean()
 ```
 
 For an overview of the InfluxDB data model, watch the following video:
 
-{{< youtube 3qTTqsL27lI >}}
\ No newline at end of file
+{{< youtube 3qTTqsL27lI >}}
diff --git a/content/influxdb/v2.1/write-data/delete-data.md b/content/influxdb/v2.1/write-data/delete-data.md
index 7fb7d9802..8f086a787 100644
--- a/content/influxdb/v2.1/write-data/delete-data.md
+++ b/content/influxdb/v2.1/write-data/delete-data.md
@@ -2,7 +2,8 @@
 title: Delete data
 list_title: Delete data
 description: >
-  Delete data in the InfluxDB CLI and API.
+  Use the `influx` CLI or the InfluxDB API `/api/v2/delete` endpoint to delete
+  data from an InfluxDB bucket.
 menu:
   influxdb_2_1:
     name: Delete data
@@ -14,47 +15,30 @@ related:
   - /influxdb/v2.1/reference/cli/influx/delete/
 ---
 
-<!--
-## Delete data in the InfluxDB UI
-
-Delete data from buckets you've created. You cannot delete data from system buckets.
-
-### Delete data from buckets
-
-1. Click **Load Data** in the navigation bar.
-
-    {{< nav-icon "load data" >}}
-
-2. Select **Buckets**.
-3. Next to the bucket with data you want to delete, click **Delete Data by Filter**.
-4. In the **Delete Data** window that appears:
-  - Select a **Target Bucket** to delete data from.
-  - Enter a **Time Range** to delete data from.
-  - Click **+ Add Filter** to filter by tag key and value pair.
-  - Select **I understand that this cannot be undone**.
-5. Click **Confirm Delete** to delete the selected data.
-
-### Delete data from the Data Explorer
-
-1. Click the **Data Explorer** icon in the sidebar.
-
-    {{< nav-icon "data-explorer" >}}
-
-2. Click **Delete Data** in the top navigation bar.
-3. In the **Delete Data** window that appears:
-  - Select a **Target Bucket** to delete data from.
-  - Enter a **Time Range** to delete data from.
-  - Click **+ Add Filter** to filter by tag key-value pairs.
-  - Select **I understand that this cannot be undone**.
-4. Click **Confirm Delete** to delete the selected data.
-!-->
-
 Use the [`influx` CLI](/influxdb/v2.1/reference/cli/influx/) or the InfluxDB API
-[`/api/v2/delete`](/influxdb/v2.1/api/#operation/PostDelete) endpoint to delete data.
+[`/api/v2/delete`](/influxdb/v2.1/api/#operation/PostDelete) endpoint to delete
+data from an InfluxDB bucket.
 
 - [Delete data using the influx CLI](#delete-data-using-the-influx-cli)
 - [Delete data using the API](#delete-data-using-the-api)
 
+InfluxDB {{< current-version >}} supports deleting data by the following:
+
+- time range
+- measurement (`_measurement`)
+- tag
+- {{% cloud-only %}}field (`_field`){{% /cloud-only %}}
+
+{{% oss-only %}}
+
+{{% warn %}}
+InfluxDB {{< current-version >}} does not support deleting data by field.
+{{% /warn %}}
+
+{{% /oss-only %}}
+
+Once a delete request completes successfully, the deleted data is no longer queryable,
+but will remain on disk until the compaction service runs.
 
 ## Delete data using the influx CLI
 
@@ -80,8 +64,8 @@ deletes all data in the specified bucket with timestamps between the specified `
 ##### Delete points in a specific measurement with a specific tag value
 ```sh
 influx delete --bucket example-bucket \
-  --start '1970-01-01T00:00:00Z' \
-  --stop $(date +"%Y-%m-%dT%H:%M:%SZ") \
+  --start '1970-01-01T00:00:00Z' \
+  --stop $(date +"%Y-%m-%dT%H:%M:%SZ") \
   --predicate '_measurement="example-measurement" AND exampleTag="exampleTagValue"'
 ```
 
@@ -95,6 +79,9 @@ influx delete --bucket example-bucket \
 ## Delete data using the API
 Use the InfluxDB API [`/api/v2/delete` endpoint](/influxdb/v2.1/api/#operation/PostDelete)
 to delete points from InfluxDB.
+
+{{< api-endpoint method="post" endpoint="http://localhost:8086/api/v2/delete" >}}
+
 Include the following:
 
 - **Request method:** `POST`
@@ -115,7 +102,7 @@ Deleting data without a [delete predicate](/influxdb/v2.1/reference/syntax/delet
 deletes all data in the specified bucket with timestamps between the specified `start` and `stop` times.
        {{% /warn %}}
 
-#### Examples
+### Examples
 
 ##### Delete points in a specific measurement with a specific tag value
 ```sh
diff --git a/content/influxdb/v2.1/write-data/developer-tools/api.md b/content/influxdb/v2.1/write-data/developer-tools/api.md
index 8fb5e2b66..aee349c25 100644
--- a/content/influxdb/v2.1/write-data/developer-tools/api.md
+++ b/content/influxdb/v2.1/write-data/developer-tools/api.md
@@ -36,7 +36,7 @@ The URL in the examples depends on the version and location of your InfluxDB {{<
 {{% /code-tab-content %}}
 {{% code-tab-content %}}
 ```js
-{{< get-shared-text "api/v2.0/write/write.sh" >}}
+{{< get-shared-text "api/v2.0/write/write.mjs" >}}
 ```
 {{% /code-tab-content %}}
 {{< /code-tabs-wrapper >}}
diff --git a/content/influxdb/v2.1/write-data/developer-tools/csv.md b/content/influxdb/v2.1/write-data/developer-tools/csv.md
index 8d091698b..eed6563f4 100644
--- a/content/influxdb/v2.1/write-data/developer-tools/csv.md
+++ b/content/influxdb/v2.1/write-data/developer-tools/csv.md
@@ -577,7 +577,7 @@ The example below writes [NOAA water sample data](/influxdb/v2.1/reference/sampl
 import "experimental/csv"
 
 csv.from(url: "https://influx-testdata.s3.amazonaws.com/noaa.csv")
-  |> to(bucket: "noaa", org: "example-org")
+    |> to(bucket: "noaa", org: "example-org")
 ```
 
 {{% note %}}
diff --git a/content/influxdb/v2.1/write-data/developer-tools/scrape-prometheus-metrics.md b/content/influxdb/v2.1/write-data/developer-tools/scrape-prometheus-metrics.md
index 4cfba667a..542020f35 100644
--- a/content/influxdb/v2.1/write-data/developer-tools/scrape-prometheus-metrics.md
+++ b/content/influxdb/v2.1/write-data/developer-tools/scrape-prometheus-metrics.md
@@ -11,7 +11,7 @@ menu:
     name: Scrape Prometheus metrics
     parent: Developer tools
 related:
-  - /{{< latest "telegraf" >}}/plugins/#prometheus, Telegraf Prometheus input plugin
+  - /{{< latest "telegraf" >}}/plugins/#input-prometheus, Telegraf Prometheus input plugin
   - /{{< latest "flux" >}}/prometheus/scrape-prometheus/, Scrape Prometheus metrics with Flux
   - /{{< latest "flux" >}}/stdlib/experimental/prometheus/scrape/
   - /{{< latest "flux" >}}/prometheus/metric-types/
@@ -42,15 +42,15 @@ to scrape Prometheus-formatted metrics from an HTTP-accessible endpoint and stor
 To use Telegraf to scrape Prometheus-formatted metrics from an HTTP-accessible
 endpoint and write them to InfluxDB{{% cloud-only %}} Cloud{{% /cloud-only %}}, follow these steps:
 
-1. Add the [Prometheus input plugin](/{{< latest "telegraf" >}}/plugins/#prometheus) to your Telegraf configuration file.
+1. Add the [Prometheus input plugin](/{{< latest "telegraf" >}}/plugins/#input-prometheus) to your Telegraf configuration file.
     1. Set the `urls` to scrape metrics from.
     2. Set the `metric_version` configuration option to specify which
       [metric parsing version](/influxdb/v2.1/reference/prometheus-metrics/) to use
       _(version `2` is recommended)_.
-2. Add the [InfluxDB v2 output plugin](/{{< latest "telegraf" >}}/plugins/#influxdb_v2)
+2. Add the [InfluxDB v2 output plugin](/{{< latest "telegraf" >}}/plugins/#output-influxdb_v2)
    to your Telegraf configuration file and configure it to to write to
    InfluxDB{{% cloud-only %}} Cloud{{% /cloud-only %}}.
-  
+
 ##### Example telegraf.conf
 ```toml
 # ...
@@ -73,9 +73,53 @@ endpoint and write them to InfluxDB{{% cloud-only %}} Cloud{{% /cloud-only %}},
 {{% oss-only %}}
 
 ## Use an InfluxDB scraper
-InfluxDB scrapers automatically scrape Prometheus-formatted metrics from an 
+InfluxDB scrapers automatically scrape Prometheus-formatted metrics from an
 HTTP-accessible endpoint at a regular interval.
-For information about setting up an InfluxDB scraper, see
+
+- [Create a scraper with the InfluxDB API](#create-a-scraper-with-the-influxdb-api)
+- [Create a scraper with the InfluxDB UI](#create-a-scraper-with-the-influxdb-ui)
+
+### Create a scraper with the InfluxDB API
+
+Use the InfluxDB API [`/api/v2/scrapers`](/influxdb/v2.1/api/#tag/Scraper-Targets) endpoint to manage scrapers and member privileges for scrapers.
+
+To create a scraper, send an HTTP `POST` request to the `/api/v2/scrapers` endpoint.
+
+{{< api-endpoint method="POST" endpoint="http://localhost:8086/api/v2/scrapers" >}}
+
+Include the following in your request:
+
+| Requirement          | Include by                                               |
+|:-----------          |:----------                                               |
+| API token with [`write: orgs/YOUR_ORG_ID/scrapers`](/influxdb/v2.1/api/#operation/PostAuthorizations) permission | Use the `Authorization` header and the `Bearer` or `Token` scheme. |
+| Organization         | Pass as `orgID` in the request body. |
+| Scraper name         | Pass as `name` in the request body. |
+| Format of scraped data | Pass as `type` in the request body. Prometheus data format (`prometheus`) is the only supported type. |
+| URL endpoint to scrape | Pass as `url` in the request body. |
+
+Optionally, to force the scraper to skip TLS verification and ignore self-signed certificates at the `url`, pass `"allowInsecure": true` in the request body.
+
+#### Example
+
+```sh
+curl -v --request POST http://localhost:8086/api/v2/scrapers \
+  --header "Authorization: Token ${INFLUX_TOKEN}" \
+  --header 'Content-type: application/json' \
+  --data-binary @- << JSON
+    {
+      "name": "Scraper name",
+      "type": "prometheus",
+      "url": "http://localhost:9090/metrics",
+      "orgID": "${INFLUX_ORG}",
+      "bucketID": "c55193a037c3b0ca",
+      "allowInsecure": true
+    }
+JSON
+```
+
+### Create a scraper with the InfluxDB UI
+
+To use the InfluxDB UI to manage scrapers, see
 [Scrape data using InfluxDB scrapers](/influxdb/v2.1/write-data/no-code/scrape-data/).
 
 {{% /oss-only %}}
@@ -95,7 +139,7 @@ them to InfluxDB{{% cloud-only %}} Cloud{{% /cloud-only %}}, do the following in
 import "experimental/prometheus"
 
 prometheus.scrape(url: "http://example.com/metrics")
-  |> to(bucket: "example-bucket")
+    |> to(bucket: "example-bucket")
 ```
 
 4. (Optional) To scrape Prometheus metrics at regular intervals using Flux, add your Flux
diff --git a/content/influxdb/v2.1/write-data/no-code/load-data.md b/content/influxdb/v2.1/write-data/no-code/load-data.md
index 5ccb87a6d..fdd7745bb 100644
--- a/content/influxdb/v2.1/write-data/no-code/load-data.md
+++ b/content/influxdb/v2.1/write-data/no-code/load-data.md
@@ -14,7 +14,6 @@ menu:
 Load data from the following sources in the InfluxDB user interface (UI):
 
 - [CSV or line protocol file](#load-csv-or-line-protocol-in-ui)
-- [Line protocol](#load-data-using-line-protocol)
 - [Client libraries](#load-data-from-a-client-library-in-the-ui)
 - [Telegraf plugins](#load-data-from-a-telegraf-plugin-in-the-ui)
 
@@ -22,17 +21,17 @@ Load data from the following sources in the InfluxDB user interface (UI):
 
 Load CSV or line protocol data by uploading a file or pasting the data manually into the UI.
 
-1. In the navigation menu on the left, click **Data (Load Data)** > **Sources**.
+1. In the navigation menu on the left, click **Load Data** > **Sources**.
     {{< nav-icon "data" >}}
 2. Under **File Upload**, select the type of data to upload:
     - **Annotated CSV**. Verify your CSV file follows the supported [annotated CSV](/influxdb/cloud/reference/syntax/annotated-csv/) syntax.
     - **Line Protocol**. Verify your line protocol file adheres to the following conventions:  
        - Each line represents a data point.
-        - Each data point requires a:  
-          - [*measurement*](/influxdb/cloud/reference/syntax/line-protocol/#measurement)
-          - [*field set*](/influxdb/cloud/reference/syntax/line-protocol/#field-set)
-          - (Optional) [*tag set*](/influxdb/cloud/reference/syntax/line-protocol/#tag-set)
-          - [*timestamp*](/influxdb/cloud/reference/syntax/line-protocol/#timestamp)
+         - Each data point requires a:  
+         - [*measurement*](/influxdb/cloud/reference/syntax/line-protocol/#measurement)
+         - [*field set*](/influxdb/cloud/reference/syntax/line-protocol/#field-set)
+         - (Optional) [*tag set*](/influxdb/cloud/reference/syntax/line-protocol/#tag-set)
+         - [*timestamp*](/influxdb/cloud/reference/syntax/line-protocol/#timestamp)
 
           For more information, see supported [line protocol](/influxdb/cloud/reference/syntax/line-protocol/) syntax.
 
@@ -44,7 +43,7 @@ Load CSV or line protocol data by uploading a file or pasting the data manually
 
 ### Load data from a client library in the UI
 
-1.  In the navigation menu on the left, click **Data (Load Data)** > **Sources**.
+1.  In the navigation menu on the left, click **Load Data** > **Sources**.
     {{< nav-icon "data" >}}
 2. Do one of the following:
    - Enter a specific client library to search for in the **Search data writing methods** field.
@@ -59,7 +58,7 @@ Load CSV or line protocol data by uploading a file or pasting the data manually
 
 ### Load data from a Telegraf plugin in the UI
 
-1. In the navigation menu on the left, click **Data (Load Data)** > **Sources**.
+1. In the navigation menu on the left, click **Load Data** > **Sources**.
     {{< nav-icon "data" >}}
 2. Do one of the following:
    - Enter a specific Telegraf plugin to search for in the **Search data writing methods** field.
diff --git a/content/influxdb/v2.1/write-data/no-code/scrape-data/manage-scrapers/create-a-scraper.md b/content/influxdb/v2.1/write-data/no-code/scrape-data/manage-scrapers/create-a-scraper.md
index aae83bbc4..bb251b548 100644
--- a/content/influxdb/v2.1/write-data/no-code/scrape-data/manage-scrapers/create-a-scraper.md
+++ b/content/influxdb/v2.1/write-data/no-code/scrape-data/manage-scrapers/create-a-scraper.md
@@ -10,9 +10,13 @@ menu:
     name: Create a scraper
     parent: Manage scrapers
 weight: 301
+related:
+  - /influxdb/v2.1/reference/prometheus-metrics/
+  - influxdb/v2.1/write-data/developer-tools/scrape-prometheus-metrics/
+influxdb/v2.1/tags: [prometheus, scraper]
 ---
 
-Create a new scraper in the InfluxDB user interface (UI).
+Create a scraper in the InfluxDB user interface (UI).
 
 ## Create a scraper in the InfluxDB UI
 1. In the navigation menu on the left, select **Data** (**Load Data**) > **Scrapers**.
diff --git a/content/influxdb/v2.2/_index.md b/content/influxdb/v2.2/_index.md
new file mode 100644
index 000000000..d60f043a0
--- /dev/null
+++ b/content/influxdb/v2.2/_index.md
@@ -0,0 +1,19 @@
+---
+title: InfluxDB OSS 2.2 documentation
+description: >
+  InfluxDB OSS 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: landing-influxdb
+menu:
+  influxdb_2_2:
+    name: InfluxDB OSS 2.2
+weight: 1
+---
+
+#### Welcome
+Welcome to the InfluxDB v2.2 documentation!
+InfluxDB is an open source time series database designed to handle high write and query workloads.
+
+This documentation is meant to help you learn how to use and leverage InfluxDB to meet your needs.
+Common use cases include infrastructure monitoring, IoT data collection, events handling, and more.
+If your use case involves time series data, InfluxDB is purpose-built to handle it.
diff --git a/content/influxdb/v2.2/api-guide/_index.md b/content/influxdb/v2.2/api-guide/_index.md
new file mode 100644
index 000000000..4aa736384
--- /dev/null
+++ b/content/influxdb/v2.2/api-guide/_index.md
@@ -0,0 +1,33 @@
+---
+title: Develop with the InfluxDB API
+seotitle: Use the InfluxDB API
+description: Interact with InfluxDB 2.2 using a rich API for writing and querying data and more.
+weight: 4
+menu:
+  influxdb_2_2:
+    name: Develop with the API
+influxdb/v2.2/tags: [api]
+---
+
+The InfluxDB v2 API provides a programmatic interface for interactions with InfluxDB.
+Access the InfluxDB API using the `/api/v2/` endpoint.
+
+## InfluxDB client libraries
+InfluxDB client libraries are language-specific packages that integrate with the InfluxDB v2 API.
+For information about supported client libraries, see [InfluxDB client libraries](/{{< latest "influxdb" >}}/api-guide/client-libraries/).
+
+## InfluxDB v2 API documentation
+<a class="btn" href="/influxdb/v2.2/api/">InfluxDB OSS {{< current-version >}} API documentation</a>
+
+#### View InfluxDB API documentation locally
+InfluxDB API documentation is built into the `influxd` service and represents
+the API specific to the current version of InfluxDB.
+To view the API documentation locally, [start InfluxDB](/influxdb/v2.2/get-started/#start-influxdb)
+and visit the `/docs` endpoint in a browser ([localhost:8086/docs](http://localhost:8086/docs)).
+
+## InfluxDB v1 compatibility API documentation
+The InfluxDB v2 API includes [InfluxDB 1.x compatibility endpoints](/influxdb/v2.2/reference/api/influxdb-1x/)
+that work with InfluxDB 1.x client libraries and third-party integrations like
+[Grafana](https://grafana.com) and others.
+
+<a class="btn" href="/influxdb/v2.2/api/v1-compatibility/">View full v1 compatibility API documentation</a>
diff --git a/content/influxdb/v2.2/api-guide/api_intro.md b/content/influxdb/v2.2/api-guide/api_intro.md
new file mode 100644
index 000000000..3d59e4382
--- /dev/null
+++ b/content/influxdb/v2.2/api-guide/api_intro.md
@@ -0,0 +1,75 @@
+---
+title: API Quick Start
+seotitle: Use the InfluxDB API
+description: Interact with InfluxDB 1 using a rich API for writing and querying data and more.
+weight: 3
+menu:
+  influxdb_2_2:
+    name: Quick Start
+    parent: Develop with the API
+aliases:
+  - /influxdb/v2.2/tools/api/
+influxdb/cloud/tags: [api]
+---
+
+InfluxDB offers a rich API and [client libraries](/influxdb/v2.2/api-guide/client-libraries) ready to integrate with your application. Use popular tools like Curl and [Postman](/influxdb/v2.2/api-guide/postman) for rapidly testing API requests.
+
+This section will guide you through the most commonly used API methods.
+
+For detailed documentation on the entire API, see [InfluxDBv2 API Reference](/influxdb/v2.2/reference/api/#influxdb-v2-api-documentation).
+
+{{% note %}}
+If you need to use InfluxDB {{< current-version >}} with **InfluxDB 1.x** API clients and integrations, see the [1.x compatibility API](/influxdb/v2.2/reference/api/influxdb-1x/).
+{{% /note %}}
+
+## Bootstrap your application
+
+With most API requests, you'll need to provide a minimum of your InfluxDB URL, Organization, and Authorization Token.
+
+[Install InfluxDB OSS v2.x](/influxdb/v2.2/install/) or upgrade to
+an [InfluxDB Cloud account](/influxdb/cloud/sign-up).
+
+### Authentication
+
+InfluxDB uses [API tokens](/influxdb/v2.2/security/tokens/) to authorize API requests.
+
+1. Before exploring the API, use the InfluxDB UI to
+[create an initial API token](/influxdb/v2.2/security/tokens/create-token/) for your application.
+
+2. Include your API token in an `Authentication: Token YOUR_API_TOKEN` HTTP header with each request.
+
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[curl](#curl)
+[Node.js](#nodejs)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```sh
+{{% get-shared-text "api/v2.0/auth/oss/token-auth.sh" %}}
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```js
+{{% get-shared-text "api/v2.0/auth/oss/token-auth.js" %}}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+Postman is another popular tool for exploring APIs. See how to [send authenticated requests with Postman](/{{< latest "influxdb" >}}/api-guide/postman/#send-authenticated-api-requests-with-postman).
+
+## Buckets API
+
+Before writing data you'll need to create a Bucket in InfluxDB.
+[Create a bucket](/influxdb/v2.2/organizations/buckets/create-bucket/#create-a-bucket-using-the-influxdb-api) using an HTTP request to the InfluxDB API `/buckets` endpoint.
+
+```sh
+{{% get-shared-text "api/v2.0/buckets/oss/create.sh" %}}
+```
+
+## Write API
+
+[Write data to InfluxDB](/influxdb/v2.2/write-data/developer-tools/api/) using an HTTP request to the InfluxDB API `/write` endpoint.
+
+## Query API
+
+[Query from InfluxDB](/influxdb/v2.2/query-data/execute-queries/influx-api/) using an HTTP request to the `/query` endpoint.
diff --git a/content/influxdb/v2.2/api-guide/client-libraries/_index.md b/content/influxdb/v2.2/api-guide/client-libraries/_index.md
new file mode 100644
index 000000000..60aa01488
--- /dev/null
+++ b/content/influxdb/v2.2/api-guide/client-libraries/_index.md
@@ -0,0 +1,26 @@
+---
+title: Use InfluxDB client libraries
+description: >
+  InfluxDB client libraries are language-specific tools that integrate with the InfluxDB v2 API.
+  View the list of available client libraries.
+weight: 101
+aliases:
+  - /influxdb/v2.2/reference/client-libraries/
+  - /influxdb/v2.2/reference/api/client-libraries/
+  - /influxdb/v2.2/tools/client-libraries/
+menu:
+  influxdb_2_2:
+    name: Client libraries
+    parent: Develop with the API
+influxdb/v2.2/tags: [client libraries]
+---
+
+InfluxDB client libraries are language-specific packages that integrate with the InfluxDB v2 API.
+The following **InfluxDB v2** client libraries are available:
+
+{{% note %}}
+These client libraries are in active development and may not be feature-complete.
+This list will continue to grow as more client libraries are released.
+{{% /note %}}
+
+{{< children type="list" >}}
diff --git a/content/influxdb/v2.2/api-guide/client-libraries/arduino.md b/content/influxdb/v2.2/api-guide/client-libraries/arduino.md
new file mode 100644
index 000000000..1d6be38f1
--- /dev/null
+++ b/content/influxdb/v2.2/api-guide/client-libraries/arduino.md
@@ -0,0 +1,15 @@
+---
+title: Arduino client library
+seotitle: Use the InfluxDB Arduino client library
+list_title: Arduino
+description: Use the InfluxDB Arduino client library to interact with InfluxDB.
+external_url: https://github.com/tobiasschuerg/InfluxDB-Client-for-Arduino
+list_note: _– contributed by [tobiasschuerg](https://github.com/tobiasschuerg)_
+menu:
+  influxdb_2_2:
+    name: Arduino
+    parent: Client libraries
+    params:
+      url: https://github.com/tobiasschuerg/InfluxDB-Client-for-Arduino
+weight: 201
+---
diff --git a/content/influxdb/v2.2/api-guide/client-libraries/browserjs.md b/content/influxdb/v2.2/api-guide/client-libraries/browserjs.md
new file mode 100644
index 000000000..470b66414
--- /dev/null
+++ b/content/influxdb/v2.2/api-guide/client-libraries/browserjs.md
@@ -0,0 +1,117 @@
+---
+title: JavaScript client library for web browsers
+seotitle: Use the InfluxDB JavaScript client library for web browsers
+list_title: JavaScript for browsers
+description: >
+  Use the InfluxDB JavaScript client library to interact with InfluxDB in web clients.
+menu:
+  influxdb_2_2:
+    name: JavaScript for browsers
+    identifier: client_js_browsers
+    parent: Client libraries
+influxdb/v2.2/tags: [client libraries, JavaScript]
+weight: 201
+aliases:
+  - /influxdb/v2.2/reference/api/client-libraries/browserjs/
+  - /influxdb/v2.2/api-guide/client-libraries/browserjs/write
+  - /influxdb/v2.2/api-guide/client-libraries/browserjs/query
+related:
+  - /influxdb/v2.2/api-guide/client-libraries/nodejs/write/
+  - /influxdb/v2.2/api-guide/client-libraries/nodejs/query/
+---
+
+Use the [InfluxDB JavaScript client library](https://github.com/influxdata/influxdb-client-js) to interact with the InfluxDB API in browsers and front-end clients. This library supports both front-end and server-side environments and provides the following distributions:
+* ECMAScript modules (ESM) and CommonJS modules (CJS)
+* Bundled ESM
+* Bundled UMD 
+
+This guide presumes some familiarity with JavaScript, browser environments, and InfluxDB.
+If you're just getting started with InfluxDB, see [Get started with InfluxDB](/{{% latest "influxdb" %}}/get-started/).
+
+{{% warn %}}
+### Tokens in production applications
+{{% api/browser-token-warning %}}
+{{% /warn %}}
+
+* [Before you begin](#before-you-begin)
+* [Use with module bundlers](#use-with-module-bundlers)
+* [Use bundled distributions with browsers and module loaders](#use-bundled-distributions-with-browsers-and-module-loaders)
+* [Get started with the example app](#get-started-with-the-example-app)
+
+## Before you begin
+
+1. Install [Node.js](https://nodejs.org/en/download/package-manager/) to serve your front-end app.
+
+2. Ensure that InfluxDB is running and you can connect to it.
+   For information about what URL to use to connect to InfluxDB OSS or InfluxDB Cloud, see [InfluxDB URLs](/{{% latest "influxdb" %}}/reference/urls/).
+
+## Use with module bundlers
+
+If you use a module bundler like Webpack or Parcel, install `@influxdata/influxdb-client-browser`.
+For more information and examples, see [Node.js](/{{% latest "influxdb" %}}/api-guide/client-libraries/nodejs/).  
+
+## Use bundled distributions with browsers and module loaders 
+
+1. Configure InfluxDB properties for your script.
+
+   ```html
+   <script>
+     window.INFLUX_ENV = {
+       url: 'http://localhost:8086',
+       token: 'YOUR_AUTH_TOKEN'
+     }
+   </script>
+   ```
+
+2. Import modules from the latest client library browser distribution.
+`@influxdata/influxdb-client-browser` exports bundled ESM and UMD syntaxes. 
+
+   {{< code-tabs-wrapper >}}
+   {{% code-tabs %}}
+   [ESM](#import-esm)
+   [UMD](#import-umd)
+   {{% /code-tabs %}}
+   {{% code-tab-content %}}
+   ```html
+   <script type="module">
+     import {InfluxDB, Point} from 'https://unpkg.com/@influxdata/influxdb-client-browser/dist/index.browser.mjs'
+
+     const influxDB = new InfluxDB({INFLUX_ENV.url, INFLUX_ENV.token})
+   </script>
+   ```
+   {{% /code-tab-content %}}
+   {{% code-tab-content %}}
+   ```html
+   <script src="https://unpkg.com/@influxdata/influxdb-client-browser"></script>
+   <script>
+     const Influx = window['@influxdata/influxdb-client']
+
+     const InfluxDB = Influx.InfluxDB
+     const influxDB = new InfluxDB({INFLUX_ENV.url, INFLUX_ENV.token})
+   </script>
+   ```
+   {{% /code-tab-content %}}
+   {{< /code-tabs-wrapper >}}
+
+After you've imported the client library, you're ready to [write data](/{{% latest "influxdb" %}}/api-guide/client-libraries/nodejs/write/?t=nodejs) to InfluxDB.
+
+## Get started with the example app
+
+This library includes an example browser app that queries from and writes to your InfluxDB instance.
+
+1. Clone the [influxdb-client-js](https://github.com/influxdata/influxdb-client-js) repo.
+
+2. Navigate to the `examples` directory:
+    ```js
+    cd examples
+    ```
+
+3. Update `./env_browser.js` with your InfluxDB [url](/{{% latest "influxdb" %}}/reference/urls/), [bucket](/{{% latest "influxdb" %}}/organizations/buckets/), [organization](/{{% latest "influxdb" %}}/organizations/), and [token](/{{% latest "influxdb" %}}/security/tokens/)
+
+4. Run the following command to start the application at [http://localhost:3001/examples/index.html]()
+
+    ```sh
+    npm run browser
+    ```
+
+    `index.html` loads the `env_browser.js` configuration, the client library ESM modules, and the application in your browser.
diff --git a/content/influxdb/v2.2/api-guide/client-libraries/csharp.md b/content/influxdb/v2.2/api-guide/client-libraries/csharp.md
new file mode 100644
index 000000000..6201d6e4d
--- /dev/null
+++ b/content/influxdb/v2.2/api-guide/client-libraries/csharp.md
@@ -0,0 +1,14 @@
+---
+title: C# client library
+list_title: C#
+seotitle: Use the InfluxDB C# client library
+description: Use the InfluxDB C# client library to interact with InfluxDB.
+external_url: https://github.com/influxdata/influxdb-client-csharp
+menu:
+  influxdb_2_2:
+    name: C#
+    parent: Client libraries
+    params:
+      url: https://github.com/influxdata/influxdb-client-csharp
+weight: 201
+---
diff --git a/content/influxdb/v2.2/api-guide/client-libraries/dart.md b/content/influxdb/v2.2/api-guide/client-libraries/dart.md
new file mode 100644
index 000000000..a1d57bc0d
--- /dev/null
+++ b/content/influxdb/v2.2/api-guide/client-libraries/dart.md
@@ -0,0 +1,14 @@
+---
+title: Dart client library
+list_title: Dart
+seotitle: Use the InfluxDB Dart client library
+description: Use the InfluxDB Dart client library to interact with InfluxDB.
+external_url: https://github.com/influxdata/influxdb-client-dart
+menu:
+  influxdb_2_2:
+    name: Dart
+    parent: Client libraries
+    params:
+      url: https://github.com/influxdata/influxdb-client-dart
+weight: 201
+---
diff --git a/content/influxdb/v2.2/api-guide/client-libraries/go.md b/content/influxdb/v2.2/api-guide/client-libraries/go.md
new file mode 100644
index 000000000..34bf777dd
--- /dev/null
+++ b/content/influxdb/v2.2/api-guide/client-libraries/go.md
@@ -0,0 +1,206 @@
+---
+title: Go client library
+seotitle: Use the InfluxDB Go client library
+list_title: Go
+description: >
+  Use the InfluxDB Go client library to interact with InfluxDB.
+menu:
+  influxdb_2_2:
+    name: Go
+    parent: Client libraries
+influxdb/v2.2/tags: [client libraries, Go]
+weight: 201
+aliases:
+  - /influxdb/v2.2/reference/api/client-libraries/go/
+  - /influxdb/v2.2/tools/client-libraries/go/
+---
+
+Use the [InfluxDB Go client library](https://github.com/influxdata/influxdb-client-go) to integrate InfluxDB into Go scripts and applications.
+
+This guide presumes some familiarity with Go and InfluxDB.
+If just getting started, see [Get started with InfluxDB](/influxdb/v2.2/get-started/).
+
+## Before you begin
+
+1. [Install Go 1.13 or later](https://golang.org/doc/install).
+2. Add the client package your to your project dependencies.
+
+    ```sh
+    # Add InfluxDB Go client package to your project go.mod
+    go get github.com/influxdata/influxdb-client-go/v2
+    ```
+3. Ensure that InfluxDB is running and you can connect to it.
+   For information about what URL to use to connect to InfluxDB OSS or InfluxDB Cloud, see [InfluxDB URLs](/influxdb/v2.2/reference/urls/).
+
+## Boilerplate for the InfluxDB Go Client Library  
+
+Use the Go library to write and query data from InfluxDB.
+
+1. In your Go program, import the necessary packages and specify the entry point of your executable program.
+
+   ```go
+   package main
+
+   import (
+       "context"
+       "fmt"
+       "time"
+
+       "github.com/influxdata/influxdb-client-go/v2"
+   )
+   ```
+
+2. Define variables for your InfluxDB [bucket](/influxdb/v2.2/organizations/buckets/), [organization](/influxdb/v2.2/organizations/), and [token](/influxdb/v2.2/security/tokens/).
+
+   ```go
+   bucket := "example-bucket"
+   org := "example-org"
+   token := "example-token"
+   // Store the URL of your InfluxDB instance
+   url := "http://localhost:8086"
+   ```
+
+3. Create the the InfluxDB Go client and pass in the `url` and `token` parameters.
+
+   ```go
+   client := influxdb2.NewClient(url, token)
+   ```
+
+4. Create a **write client** with the `WriteAPIBlocking` method and pass in the `org` and `bucket` parameters.
+
+   ```go
+   writeAPI := client.WriteAPIBlocking(org, bucket)
+   ```
+
+5. To query data, create an InfluxDB **query client** and pass in your InfluxDB `org`.
+
+   ```go
+   queryAPI := client.QueryAPI(org)
+   ```
+
+## Write data to InfluxDB with Go
+
+Use the Go library to write data to InfluxDB.
+
+1. Create a [point](/influxdb/v2.2/reference/glossary/#point) and write it to InfluxDB using the `WritePoint` method of the API writer struct.
+
+2. Close the client to flush all pending writes and finish.
+
+   ```go
+   p := influxdb2.NewPoint("stat",
+     map[string]string{"unit": "temperature"},
+     map[string]interface{}{"avg": 24.5, "max": 45},
+     time.Now())
+   writeAPI.WritePoint(context.Background(), p)
+   client.Close()
+   ```
+
+### Complete example write script
+
+```go
+func main() {
+    bucket := "example-bucket"
+    org := "example-org"
+    token := "example-token"
+    // Store the URL of your InfluxDB instance
+    url := "http://localhost:8086"
+    // Create new client with default option for server url authenticate by token
+    client := influxdb2.NewClient(url, token)
+    // User blocking write client for writes to desired bucket
+    writeAPI := client.WriteAPIBlocking(org, bucket)
+    // Create point using full params constructor
+    p := influxdb2.NewPoint("stat",
+        map[string]string{"unit": "temperature"},
+        map[string]interface{}{"avg": 24.5, "max": 45},
+        time.Now())
+    // Write point immediately
+    writeAPI.WritePoint(context.Background(), p)
+    // Ensures background processes finishes
+    client.Close()
+}
+```
+## Query data from InfluxDB with Go
+Use the Go library to query data to InfluxDB.
+
+1. Create a Flux query and supply your `bucket` parameter.
+
+    ```js
+    from(bucket:"<bucket>")
+        |> range(start: -1h)
+        |> filter(fn: (r) => r._measurement == "stat")
+    ```
+
+   The query client sends the Flux query to InfluxDB and returns the results as a FluxRecord object with a table structure.
+
+**The query client includes the following methods:**
+
+- `Query`: Sends the Flux query to InfluxDB.
+- `Next`: Iterates over the query response.
+- `TableChanged`: Identifies when the group key changes.
+- `Record`: Returns the last parsed FluxRecord and gives access to value and row properties.
+- `Value`: Returns the actual field value.
+
+```go
+result, err := queryAPI.Query(context.Background(), `from(bucket:"<bucket>")
+    |> range(start: -1h) 
+    |> filter(fn: (r) => r._measurement == "stat")`)
+if err == nil {
+    for result.Next() {
+        if result.TableChanged() {
+            fmt.Printf("table: %s\n", result.TableMetadata().String())
+        }
+        fmt.Printf("value: %v\n", result.Record().Value())
+    }
+    if result.Err() != nil {
+        fmt.Printf("query parsing error: %s\n", result.Err().Error())
+    }
+} else {
+    panic(err)
+}
+```
+
+**The FluxRecord object includes the following methods for accessing your data:**
+
+- `Table()`: Returns the index of the table the record belongs to.
+- `Start()`: Returns the inclusive lower time bound of all records in the current table.
+- `Stop()`: Returns the exclusive upper time bound of all records in the current table.
+- `Time()`: Returns the time of the record.
+- `Value() `: Returns the actual field value.
+- `Field()`: Returns the field name.
+- `Measurement()`: Returns the measurement name of the record.
+- `Values()`: Returns a map of column values.
+- `ValueByKey(<your_tags>)`: Returns a value from the record for given column key.
+
+### Complete example query script
+
+```go
+ func main() {
+    // Create client
+    client := influxdb2.NewClient(url, token)
+    // Get query client
+    queryAPI := client.QueryAPI(org)
+    // Get QueryTableResult
+    result, err := queryAPI.Query(context.Background(), `from(bucket:"my-bucket")|> range(start: -1h) |> filter(fn: (r) => r._measurement == "stat")`)
+    if err == nil {
+        // Iterate over query response
+        for result.Next() {
+            // Notice when group key has changed
+            if result.TableChanged() {
+                fmt.Printf("table: %s\n", result.TableMetadata().String())
+            }
+            // Access data
+            fmt.Printf("value: %v\n", result.Record().Value())
+        }
+        // Check for an error
+        if result.Err() != nil {
+            fmt.Printf("query parsing error: %s\n", result.Err().Error())
+        }
+    } else {
+        panic(err)
+    }
+    // Ensures background processes finishes
+    client.Close()
+}
+```
+
+For more information, see the [Go client README on GitHub](https://github.com/influxdata/influxdb-client-go).
diff --git a/content/influxdb/v2.2/api-guide/client-libraries/java.md b/content/influxdb/v2.2/api-guide/client-libraries/java.md
new file mode 100644
index 000000000..e819b0028
--- /dev/null
+++ b/content/influxdb/v2.2/api-guide/client-libraries/java.md
@@ -0,0 +1,14 @@
+---
+title: Java client library
+seotitle: Use the InfluxDB Java client library
+list_title: Java
+description: Use the Java client library to interact with InfluxDB.
+external_url: https://github.com/influxdata/influxdb-client-java
+menu:
+  influxdb_2_2:
+    name: Java
+    parent: Client libraries
+    params:
+      url: https://github.com/influxdata/influxdb-client-java
+weight: 201
+---
diff --git a/content/influxdb/v2.2/api-guide/client-libraries/kotlin.md b/content/influxdb/v2.2/api-guide/client-libraries/kotlin.md
new file mode 100644
index 000000000..3cbcaa859
--- /dev/null
+++ b/content/influxdb/v2.2/api-guide/client-libraries/kotlin.md
@@ -0,0 +1,14 @@
+---
+title: Kotlin client library
+seotitle: Use the Kotlin client library
+list_title: Kotlin
+description: Use the InfluxDB Kotlin client library to interact with InfluxDB.
+external_url: https://github.com/influxdata/influxdb-client-java/tree/master/client-kotlin
+menu:
+  influxdb_2_2:
+    name: Kotlin
+    parent: Client libraries
+    params:
+      url: https://github.com/influxdata/influxdb-client-java/tree/master/client-kotlin
+weight: 201
+---
diff --git a/content/influxdb/v2.2/api-guide/client-libraries/nodejs/_index.md b/content/influxdb/v2.2/api-guide/client-libraries/nodejs/_index.md
new file mode 100644
index 000000000..961b3fa95
--- /dev/null
+++ b/content/influxdb/v2.2/api-guide/client-libraries/nodejs/_index.md
@@ -0,0 +1,23 @@
+---
+title: Node.js JavaScript client library
+seotitle: Use the InfluxDB JavaScript client library
+list_title: Node.js
+description: >
+  Use the InfluxDB Node.js JavaScript client library to interact with InfluxDB.
+menu:
+  influxdb_2_2:
+    name: Node.js
+    parent: Client libraries
+influxdb/v2.2/tags: [client libraries, JavaScript]
+weight: 201
+aliases:
+  - /influxdb/v2.2/reference/api/client-libraries/nodejs/
+  - /influxdb/v2.2/reference/api/client-libraries/js/  
+---
+
+Use the [InfluxDB JavaScript client library](https://github.com/influxdata/influxdb-client-js) to integrate InfluxDB into your Node.js application.
+In this guide, you'll start a Node.js project from scratch and code some simple API operations.
+
+{{< children >}}
+
+{{% api/v2dot0/nodejs/learn-more %}}
diff --git a/content/influxdb/v2.2/api-guide/client-libraries/nodejs/install.md b/content/influxdb/v2.2/api-guide/client-libraries/nodejs/install.md
new file mode 100644
index 000000000..448a054af
--- /dev/null
+++ b/content/influxdb/v2.2/api-guide/client-libraries/nodejs/install.md
@@ -0,0 +1,97 @@
+---
+title: Install the InfluxDB JavaScript client library
+seotitle: Install the InfluxDB Node.js JavaScript client library
+description: >
+  Install the JavaScript client library to interact with the InfluxDB API in Node.js.
+menu:
+  influxdb_2_2:
+    name: Install
+    parent: Node.js
+influxdb/v2.2/tags: [client libraries, JavaScript]
+weight: 100
+aliases:
+  - /influxdb/v2.2/reference/api/client-libraries/nodejs/install
+---
+
+
+## Install Node.js
+
+1. Install [Node.js](https://nodejs.org/en/download/package-manager/).
+
+2. Ensure that InfluxDB is running and you can connect to it.
+   For information about what URL to use to connect to InfluxDB OSS or InfluxDB Cloud, see [InfluxDB URLs](/influxdb/v2.2/reference/urls/).
+
+3. Start a new Node.js project.
+  The `npm` package manager is included with Node.js.
+
+  ```sh
+  npm init -y influx-node-app
+  ```
+
+## Install TypeScript
+
+Many of the client library examples use [TypeScript](https://www.typescriptlang.org/). Follow these steps to initialize the TypeScript project.
+
+1. Install TypeScript and type definitions for Node.js.
+
+   ```sh
+   npm i -g typescript && npm i --save-dev @types/node
+   ```
+2. Create a TypeScript configuration with default values.
+
+   ```sh
+   tsc --init
+   ```
+3. Run the TypeScript compiler. To recompile your code automatically as you make changes, pass the `watch` flag to the compiler.
+
+   ```sh
+   tsc -w -p
+   ```
+
+## Install dependencies
+
+The JavaScript client library contains two packages: `@influxdata/influxdb-client` and `@influxdata/influxdb-client-apis`.
+Add both as dependencies of your project.
+
+1. Open a new terminal window and install  `@influxdata/influxdb-client` for querying and writing data:
+
+   ```sh
+   npm install --save @influxdata/influxdb-client
+   ```
+
+3. Install `@influxdata/influxdb-client-apis` for access to the InfluxDB management APIs:
+
+   ```sh
+   npm install --save @influxdata/influxdb-client-apis
+   ```
+
+## Next steps
+
+Once you've installed the Javascript client library, you're ready to [write data](/influxdb/v2.2/api-guide/client-libraries/nodejs/write/) to InfluxDB or [get started](#get-started-with-examples) with other examples from the client library.
+
+## Get started with examples
+
+{{% note %}}
+The client examples include an [`env`](https://github.com/influxdata/influxdb-client-js/blob/master/examples/env.js) module for accessing your InfluxDB properties from environment variables or from `env.js`.
+The examples use these properties to interact with the InfluxDB API.
+{{% /note %}}
+
+1. Set environment variables or update `env.js` with your InfluxDB [bucket](/influxdb/v2.2/organizations/buckets/), [organization](/influxdb/v2.2/organizations/), [token](/influxdb/v2.2/security/tokens/), and [url](/influxdb/v2.2/reference/urls/).
+
+   ```sh
+   export INFLUX_URL=http://localhost:8086
+   export INFLUX_TOKEN=YOUR_API_TOKEN
+   export INFLUX_ORG=YOUR_ORG
+   export INFLUX_BUCKET=YOUR_BUCKET
+   ```
+   Replace the following:
+   - *`YOUR_API_TOKEN`*: InfluxDB API token
+   - *`YOUR_ORG`*: InfluxDB organization ID
+   - *`YOUR_BUCKET`*: InfluxDB bucket name
+
+2. Run an example script.
+
+   ```sh
+   query.ts
+   ```
+{{% api/v2dot0/nodejs/learn-more %}}
diff --git a/content/influxdb/v2.2/api-guide/client-libraries/nodejs/query.md b/content/influxdb/v2.2/api-guide/client-libraries/nodejs/query.md
new file mode 100644
index 000000000..537d65c10
--- /dev/null
+++ b/content/influxdb/v2.2/api-guide/client-libraries/nodejs/query.md
@@ -0,0 +1,94 @@
+---
+title: Query data with the InfluxDB JavaScript client library
+description: >
+  Use the JavaScript client library to query data with the InfluxDB API in Node.js.
+menu:
+  influxdb_2_2:
+    name: Query
+    parent: Node.js
+influxdb/v2.2/tags: [client libraries, JavaScript]
+weight: 201
+aliases:
+  - /influxdb/v2.2/reference/api/client-libraries/nodejs/query
+---
+
+Use the [InfluxDB JavaScript client library](https://github.com/influxdata/influxdb-client-js) in a Node.js environment to query InfluxDB.  
+
+The following example sends a Flux query to an InfluxDB bucket and outputs rows from an observable table.
+
+## Before you begin
+
+- [Install the client library and other dependencies](/influxdb/v2.2/api-guide/client-libraries/nodejs/install/).
+
+## Query InfluxDB
+
+1. Change to your new project directory and create a file for your query module.
+
+   ```sh
+   cd influx-node-app && touch query.js
+   ```
+
+2. Instantiate an `InfluxDB` client. Provide your InfluxDB URL and API token.
+   Use the `getQueryApi()` method of the client.
+   Provide your InfluxDB organization ID to create a configured **query client**.
+
+   ```js
+   import { InfluxDB, Point } from '@influxdata/influxdb-client'
+
+   const queryApi = new InfluxDB({YOUR_URL, YOUR_API_TOKEN}).getQueryApi(YOUR_ORG)
+   ```
+
+   Replace the following:
+   - *`YOUR_URL`*: InfluxDB URL
+   - *`YOUR_API_TOKEN`*: InfluxDB API token
+   - *`YOUR_ORG`*: InfluxDB organization ID
+
+3. Create a Flux query for your InfluxDB bucket. Store the query as a string variable.
+   {{% warn %}}
+   To prevent SQL injection attacks, avoid concatenating unsafe user input with queries.
+   {{% /warn %}}
+
+    ```js
+    const fluxQuery =
+      'from(bucket: "YOUR_BUCKET")
+        |> range(start: 0)
+        |> filter(fn: (r) => r._measurement == "temperature")'
+    ```
+   Replace *`YOUR_BUCKET`* with the name of your InfluxDB bucket.
+
+4. Use the `queryRows()` method of the query client to query InfluxDB.
+   `queryRows()` takes a Flux query and an [RxJS **Observer**](http://reactivex.io/rxjs/manual/overview.html#observer) object.
+   The client returns [table](/{{% latest "influxdb" %}}/reference/syntax/annotated-csv/#tables) metadata and rows as an  [RxJS **Observable**](http://reactivex.io/rxjs/manual/overview.html#observable).
+   `queryRows()` subscribes your observer to the observable.
+   Finally, the observer logs the rows from the response to the terminal.
+
+   ```js
+   const observer = {
+     next(row, tableMeta) {
+       const o = tableMeta.toObject(row)
+       console.log(
+         `${o._time} ${o._measurement} in '${o.location}' (${o.sensor_id}): ${o._field}=${o._value}`
+       )
+     }
+   }
+
+   queryApi.queryRows(fluxQuery, observer)
+
+   ```
+
+### Complete example
+
+```js
+{{% get-shared-text "api/v2.0/query/query.mjs" %}}
+```
+
+To run the example from a file, set your InfluxDB environment variables and use `node` to execute the JavaScript file.
+
+```sh
+export INFLUX_URL=http://localhost:8086 && \
+export INFLUX_TOKEN=YOUR_API_TOKEN && \
+export INFLUX_ORG=YOUR_ORG && \
+node query.js
+```
+
+{{% api/v2dot0/nodejs/learn-more %}}
diff --git a/content/influxdb/v2.2/api-guide/client-libraries/nodejs/write.md b/content/influxdb/v2.2/api-guide/client-libraries/nodejs/write.md
new file mode 100644
index 000000000..c76d06f36
--- /dev/null
+++ b/content/influxdb/v2.2/api-guide/client-libraries/nodejs/write.md
@@ -0,0 +1,117 @@
+---
+title: Write data with the InfluxDB JavaScript client library
+description: >
+  Use the JavaScript client library to write data with the InfluxDB API in Node.js.
+menu:
+  influxdb_2_2:
+    name: Write
+    parent: Node.js
+influxdb/v2.2/tags: [client libraries, JavaScript]
+weight: 101
+aliases:
+  - /influxdb/v2.2/reference/api/client-libraries/nodejs/write
+related:
+  - /influxdb/v2.2/write-data/troubleshoot/
+---
+
+Use the [InfluxDB Javascript client library](https://github.com/influxdata/influxdb-client-js) to write data from a Node.js environment to InfluxDB.
+
+The Javascript client library includes the following convenient features for writing data to InfluxDB:
+- Apply default tags to data points.
+- Buffer points into batches to optimize data transfer.
+- Automatically retry requests on failure.
+- Set an optional HTTP proxy address for your network.
+
+### Before you begin
+
+- [Install the client library and other dependencies](/influxdb/v2.2/api-guide/client-libraries/nodejs/install/).
+### Write data with the client library
+
+1. Instantiate an `InfluxDB` client. Provide your InfluxDB URL and API token.
+
+   ```js
+   import {InfluxDB, Point} from '@influxdata/influxdb-client'
+
+   const influxDB = new InfluxDB({YOUR_URL, YOUR_API_TOKEN})
+   ```
+   Replace the following:
+   - *`YOUR_URL`*: InfluxDB URL
+   - *`YOUR_API_TOKEN`*: InfluxDB API token
+
+2. Use the `getWriteApi()` method of the client to create a **write client**.
+   Provide your InfluxDB organization ID and bucket name.
+
+   ```js
+   const writeApi = influxDB.getWriteApi(YOUR_ORG, YOUR_BUCKET)
+   ```
+   Replace the following:
+   - *`YOUR_ORG`*: InfluxDB organization ID
+   - *`YOUR_BUCKET`*: InfluxDB bucket name
+
+3. To apply one or more [tags](/influxdb/v2.2/reference/glossary/#tag) to all points, use the `useDefaultTags()` method.
+   Provide tags as an object of key/value pairs.
+
+    ```js
+    writeApi.useDefaultTags({region: 'west'})
+    ```
+
+4. Use the `Point()` constructor to create a [point](/influxdb/v2.2/reference/glossary/#point).
+   1. Call the constructor and provide a [measurement](/influxdb/v2.2/reference/glossary/#measurement).
+   2. To add one or more tags, chain the `tag()` method to the constructor.
+      Provide a `name` and `value`.
+   3. To add a field of type `float`, chain the `floatField()` method to the constructor.
+      Provide a `name` and `value`.
+
+    ```js
+    const point1 = new Point('temperature')
+      .tag('sensor_id', 'TLM010')
+      .floatField('value', 24)
+    ```
+
+5. Use the `writePoint()` method to write the point to your InfluxDB bucket.
+   Finally, use the `close()` method to flush all pending writes.
+   The example logs the new data point followed by "WRITE FINISHED" to stdout.
+
+    ```js
+    writeApi.writePoint(point1)
+
+    writeApi.close().then(() => {
+      console.log('WRITE FINISHED')
+    })
+    ```
+
+### Complete example
+
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[Curl](#curl)
+[Node.js](#nodejs)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+
+```sh
+{{< get-shared-text "api/v2.0/write/write.sh" >}}
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+
+```js
+{{< get-shared-text "api/v2.0/write/write.mjs" >}}
+```
+
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+To run the example from a file, set your InfluxDB environment variables and use `node` to execute the JavaScript file.
+
+```sh
+export INFLUX_URL=http://localhost:8086 && \
+export INFLUX_TOKEN=YOUR_API_TOKEN && \
+export INFLUX_ORG=YOUR_ORG && \
+export INFLUX_BUCKET=YOUR_BUCKET && \
+node write.js
+```
+
+### Response codes
+_For information about **InfluxDB API response codes**, see
+[InfluxDB API Write documentation](/influxdb/cloud/api/#operation/PostWrite)._
diff --git a/content/influxdb/v2.2/api-guide/client-libraries/php.md b/content/influxdb/v2.2/api-guide/client-libraries/php.md
new file mode 100644
index 000000000..58def40db
--- /dev/null
+++ b/content/influxdb/v2.2/api-guide/client-libraries/php.md
@@ -0,0 +1,14 @@
+---
+title: PHP client library
+seotitle: Use the InfluxDB PHP client library
+list_title: PHP
+description: Use the InfluxDB PHP client library to interact with InfluxDB.
+external_url: https://github.com/influxdata/influxdb-client-php
+menu:
+  influxdb_2_2:
+    name: PHP
+    parent: Client libraries
+    params:
+      url: https://github.com/influxdata/influxdb-client-php
+weight: 201
+---
diff --git a/content/influxdb/v2.2/api-guide/client-libraries/python.md b/content/influxdb/v2.2/api-guide/client-libraries/python.md
new file mode 100644
index 000000000..7925c501c
--- /dev/null
+++ b/content/influxdb/v2.2/api-guide/client-libraries/python.md
@@ -0,0 +1,176 @@
+---
+title: Python client library
+seotitle: Use the InfluxDB Python client library
+list_title: Python
+description: >
+  Use the InfluxDB Python client library to interact with InfluxDB.
+menu:
+  influxdb_2_2:
+    name: Python
+    parent: Client libraries
+influxdb/v2.2/tags: [client libraries, python]
+aliases:
+  - /influxdb/v2.2/reference/api/client-libraries/python/
+  - /influxdb/v2.2/reference/api/client-libraries/python-cl-guide/
+  - /influxdb/v2.2/tools/client-libraries/python/
+weight: 201
+---
+
+Use the [InfluxDB Python client library](https://github.com/influxdata/influxdb-client-python) to integrate InfluxDB into Python scripts and applications.
+
+This guide presumes some familiarity with Python and InfluxDB.
+If just getting started, see [Get started with InfluxDB](/influxdb/v2.2/get-started/).
+
+## Before you begin
+
+1. Install the InfluxDB Python library:
+
+    ```sh
+    pip install influxdb-client
+    ```
+
+2. Ensure that InfluxDB is running.
+   If running InfluxDB locally, visit http://localhost:8086.
+   (If using InfluxDB Cloud, visit the URL of your InfluxDB Cloud UI.
+   For example: https://us-west-2-1.aws.cloud2.influxdata.com.)
+
+## Write data to InfluxDB with Python
+
+We are going to write some data in [line protocol](/influxdb/v2.2/reference/syntax/line-protocol/) using the Python library.
+
+1. In your Python program, import the InfluxDB client library and use it to write data to InfluxDB.
+
+   ```python
+   import influxdb_client
+   from influxdb_client.client.write_api import SYNCHRONOUS
+   ```
+
+2. Define a few variables with the name of your [bucket](/influxdb/v2.2/organizations/buckets/), [organization](/influxdb/v2.2/organizations/), and [token](/influxdb/v2.2/security/tokens/).
+
+   ```python
+   bucket = "<my-bucket>"
+   org = "<my-org>"
+   token = "<my-token>"
+   # Store the URL of your InfluxDB instance
+   url="http://localhost:8086"
+   ```
+
+3. Instantiate the client. The `InfluxDBClient` object takes three named parameters: `url`, `org`, and `token`. Pass in the named parameters.
+
+   ```python
+   client = influxdb_client.InfluxDBClient(
+      url=url,
+      token=token,
+      org=org
+   )
+   ```
+    The `InfluxDBClient` object has a `write_api` method used for configuration.
+
+4. Instantiate a **write client** using the `client` object and the `write_api` method. Use the `write_api` method to configure the writer object.
+
+   ```python
+   write_api = client.write_api(write_options=SYNCHRONOUS)
+   ```
+
+5. Create a [point](/influxdb/v2.2/reference/glossary/#point) object and write it to InfluxDB using the `write` method of the API writer object. The write method requires three parameters: `bucket`, `org`, and `record`.
+
+   ```python
+   p = influxdb_client.Point("my_measurement").tag("location", "Prague").field("temperature", 25.3)
+   write_api.write(bucket=bucket, org=org, record=p)
+   ```
+
+### Complete example write script
+
+```python
+import influxdb_client
+from influxdb_client.client.write_api import SYNCHRONOUS
+
+bucket = "<my-bucket>"
+org = "<my-org>"
+token = "<my-token>"
+# Store the URL of your InfluxDB instance
+url="http://localhost:8086"
+
+client = influxdb_client.InfluxDBClient(
+    url=url,
+    token=token,
+    org=org
+)
+
+write_api = client.write_api(write_options=SYNCHRONOUS)
+
+p = influxdb_client.Point("my_measurement").tag("location", "Prague").field("temperature", 25.3)
+write_api.write(bucket=bucket, org=org, record=p)
+```
+## Query data from InfluxDB with Python
+
+1. Instantiate the **query client**.
+
+   ```python
+   query_api = client.query_api()
+   ```
+
+2. Create a Flux query, and then format it as a Python string.
+
+   ```python
+   query = ' from(bucket:"my-bucket")\
+   |> range(start: -10m)\
+   |> filter(fn:(r) => r._measurement == "my_measurement")\
+   |> filter(fn: (r) => r.location == "Prague")\
+   |> filter(fn:(r) => r._field == "temperature" ) '
+   ```
+
+    The query client sends the Flux query to InfluxDB and returns a Flux object with a table structure.
+
+3. Pass the `query()` method two named parameters:`org` and `query`.  
+
+   ```python
+   result = query_api.query(org=org, query=query)
+   ```
+
+4. Iterate through the tables and records in the Flux object.
+   - Use the `get_value()` method to return values.
+   - Use the `get_field()` method to return fields.
+
+   ```python
+   results = []
+   for table in result:
+     for record in table.records:
+       results.append((record.get_field(), record.get_value()))
+
+   print(results)
+   [(temperature, 25.3)]
+   ```
+
+**The Flux object provides the following methods for accessing your data:**
+
+- `get_measurement()`: Returns the measurement name of the record.
+- `get_field()`: Returns the field name.
+- `get_value()`: Returns the actual field value.
+- `values`: Returns a map of column values.
+- `values.get("<your tag>")`: Returns a value from the record for given column.
+- `get_time()`: Returns the time of the record.
+- `get_start()`: Returns the inclusive lower time bound of all records in the current table.
+- `get_stop()`: Returns the exclusive upper time bound of all records in the current table.
+
+
+### Complete example query script
+
+```python
+query_api = client.query_api()
+query = ‘ from(bucket:"my-bucket")\
+|> range(start: -10m)\
+|> filter(fn:(r) => r._measurement == "my_measurement")\
+|> filter(fn: (r) => r.location == "Prague")\
+|> filter(fn:(r) => r._field == "temperature" )‘
+result = query_api.query(org=org, query=query)
+results = []
+for table in result:
+    for record in table.records:
+        results.append((record.get_field(), record.get_value()))
+
+print(results)
+[(temperature, 25.3)]
+```
+
+For more information, see the [Python client README on GitHub](https://github.com/influxdata/influxdb-client-python).
diff --git a/content/influxdb/v2.2/api-guide/client-libraries/r.md b/content/influxdb/v2.2/api-guide/client-libraries/r.md
new file mode 100644
index 000000000..db7282c32
--- /dev/null
+++ b/content/influxdb/v2.2/api-guide/client-libraries/r.md
@@ -0,0 +1,14 @@
+---
+title: R package client library
+list_title: R
+seotitle: Use the InfluxDB client R package
+description: Use the InfluxDB client R package to interact with InfluxDB.
+external_url: https://github.com/influxdata/influxdb-client-r
+menu:
+  influxdb_2_2:
+    name: R
+    parent: Client libraries
+    params:
+      url: https://github.com/influxdata/influxdb-client-r
+weight: 201
+---
diff --git a/content/influxdb/v2.2/api-guide/client-libraries/ruby.md b/content/influxdb/v2.2/api-guide/client-libraries/ruby.md
new file mode 100644
index 000000000..148be7ddc
--- /dev/null
+++ b/content/influxdb/v2.2/api-guide/client-libraries/ruby.md
@@ -0,0 +1,14 @@
+---
+title: Ruby client library
+seotitle: Use the InfluxDB Ruby client library
+list_title: Ruby
+description: Use the InfluxDB Ruby client library to interact with InfluxDB.
+external_url: https://github.com/influxdata/influxdb-client-ruby
+menu:
+  influxdb_2_2:
+    name: Ruby
+    parent: Client libraries
+    params:
+      url: https://github.com/influxdata/influxdb-client-ruby
+weight: 201
+---
diff --git a/content/influxdb/v2.2/api-guide/client-libraries/scala.md b/content/influxdb/v2.2/api-guide/client-libraries/scala.md
new file mode 100644
index 000000000..84c57ac3e
--- /dev/null
+++ b/content/influxdb/v2.2/api-guide/client-libraries/scala.md
@@ -0,0 +1,14 @@
+---
+title: Scala client library
+seotitle: Use the InfluxDB Scala client library
+list_title: Scala
+description: Use the InfluxDB Scala client library to interact with InfluxDB.
+external_url: https://github.com/influxdata/influxdb-client-java/tree/master/client-scala
+menu:
+  influxdb_2_2:
+    name: Scala
+    parent: Client libraries
+    params:
+      url: https://github.com/influxdata/influxdb-client-java/tree/master/client-scala
+weight: 201
+---
diff --git a/content/influxdb/v2.2/api-guide/client-libraries/swift.md b/content/influxdb/v2.2/api-guide/client-libraries/swift.md
new file mode 100644
index 000000000..f0a49c56f
--- /dev/null
+++ b/content/influxdb/v2.2/api-guide/client-libraries/swift.md
@@ -0,0 +1,14 @@
+---
+title: Swift client library
+seotitle: Use the InfluxDB Swift client library
+list_title: Swift
+description: Use the InfluxDB Swift client library to interact with InfluxDB.
+external_url: https://github.com/influxdata/influxdb-client-swift
+menu:
+  influxdb_2_2:
+    name: Swift
+    parent: Client libraries
+    params:
+      url: https://github.com/influxdata/influxdb-client-swift
+weight: 201
+---
diff --git a/content/influxdb/v2.2/api-guide/postman.md b/content/influxdb/v2.2/api-guide/postman.md
new file mode 100644
index 000000000..ba27f5077
--- /dev/null
+++ b/content/influxdb/v2.2/api-guide/postman.md
@@ -0,0 +1,57 @@
+---
+title: Use Postman with the InfluxDB API
+description: >
+  Use [Postman](https://www.postman.com/), a popular tool for exploring APIs,
+  to interact with the [InfluxDB API](/influxdb/v2.2/api-guide/).
+menu:
+  influxdb_2_2:
+    parent: Tools & integrations
+    name: Use Postman
+weight: 105
+influxdb/v2.2/tags: [api, authentication]
+aliases:
+  - /influxdb/v2.2/reference/api/postman/
+---
+
+Use [Postman](https://www.postman.com/), a popular tool for exploring APIs,
+to interact with the [InfluxDB API](/influxdb/v2.2/api-guide/).
+
+## Install Postman
+
+Download Postman from the [official downloads page](https://www.postman.com/downloads/).
+
+Or to install with Homebrew on macOS, run the following command:
+
+```sh
+brew cask install postman
+```
+
+## Send authenticated API requests with Postman
+
+All requests to the [InfluxDB v2 API](/influxdb/v2.2/api-guide/) must include an [InfluxDB API token](/influxdb/v2.2/security/tokens/).
+
+{{% note %}}
+
+#### Authenticate with a username and password
+
+If you need to send a username and password (`Authorization: Basic`) to the [InfluxDB 1.x compatibility API](/influxdb/v2.2/reference/api/influxdb-1x/), see how to [authenticate with a username and password scheme](/influxdb/v2.2/reference/api/influxdb-1x/#authenticate-with-the-token-scheme).
+
+{{% /note %}}
+
+To configure Postman to send an [InfluxDB API token](/influxdb/v2.2/security/tokens/) with the `Authorization: Token` HTTP header, do the following:
+
+1. If you have not already, [create a token](/influxdb/v2.2/security/tokens/create-token/).
+2. In the Postman **Authorization** tab, select **API Key** in the **Type** dropdown.
+3. For **Key**, enter `Authorization`.
+4. For **Value**, enter `Token INFLUX_API_TOKEN`, replacing *`INFLUX_API_TOKEN`* with the token generated in step 1.
+5. Ensure that the **Add to** option is set to **Header**.
+
+#### Test authentication credentials
+
+To test the authentication, in Postman, enter your InfluxDB API `/api/v2/` root endpoint URL and click **Send**.
+
+###### InfluxDB v2 API root endpoint
+
+```sh
+http://localhost:8086/api/v2
+```
diff --git a/content/influxdb/v2.2/backup-restore/_index.md b/content/influxdb/v2.2/backup-restore/_index.md
new file mode 100644
index 000000000..b41fada69
--- /dev/null
+++ b/content/influxdb/v2.2/backup-restore/_index.md
@@ -0,0 +1,17 @@
+---
+title: Back up and restore data
+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.2/tags: [backup, restore]
+menu:
+  influxdb_2_2:
+    name: Back up & restore data
+weight: 9
+products: [oss]
+---
+
+InfluxDB provides tools to back up and restore data and metadata stored in InfluxDB.
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/backup-restore/backup.md b/content/influxdb/v2.2/backup-restore/backup.md
new file mode 100644
index 000000000..76697ae23
--- /dev/null
+++ b/content/influxdb/v2.2/backup-restore/backup.md
@@ -0,0 +1,49 @@
+---
+title: Back up data
+seotitle: Back up data in InfluxDB
+description: >
+  Use the `influx backup` command to back up data and metadata stored in InfluxDB.
+menu:
+  influxdb_2_2:
+    parent: Back up & restore data
+weight: 101
+related:
+  - /influxdb/v2.2/backup-restore/restore/
+  - /influxdb/v2.2/reference/cli/influx/backup/
+products: [oss]
+---
+
+Use the [`influx backup` command](/influxdb/v2.2/reference/cli/influx/backup/) to back up
+data and metadata stored in InfluxDB.
+InfluxDB copies all data and metadata to a set of files stored in a specified directory
+on your local filesystem.
+
+{{% note %}}
+#### InfluxDB 1.x/2.x compatibility
+The InfluxDB {{< current-version >}} `influx backup` command is not compatible with versions of InfluxDB prior to 2.0.0.
+**For information about migrating data between InfluxDB 1.x and {{< current-version >}}, see:**
+
+- [Automatically upgrade from InfluxDB 1.x to {{< current-version >}}](/influxdb/v2.2/upgrade/v1-to-v2/automatic-upgrade/)
+- [Manually upgrade from InfluxDB 1.x to {{< current-version >}}](/influxdb/v2.2/upgrade/v1-to-v2/manual-upgrade/)
+{{% /note %}}
+
+{{% cloud %}}
+The `influx backup` command **cannot** back up data stored in **{{< cloud-name "short" >}}**.
+{{% /cloud %}}
+
+The `influx backup` command requires:
+
+- The directory path for where to store the backup file set
+- The **root authorization token** (the token created for the first user in the
+  [InfluxDB setup process](/influxdb/v2.2/get-started/)).
+
+##### Back up data with the influx CLI
+```sh
+# Syntax
+influx backup <backup-path> -t <root-token>
+
+# Example
+influx backup \
+  path/to/backup_$(date '+%Y-%m-%d_%H-%M') \
+  -t xXXXX0xXX0xxX0xx_x0XxXxXXXxxXX0XXX0XXxXxX0XxxxXX0Xx0xx==
+```
diff --git a/content/influxdb/v2.2/backup-restore/restore.md b/content/influxdb/v2.2/backup-restore/restore.md
new file mode 100644
index 000000000..5a985ca39
--- /dev/null
+++ b/content/influxdb/v2.2/backup-restore/restore.md
@@ -0,0 +1,141 @@
+---
+title: Restore data
+seotitle: Restore data in InfluxDB
+description: >
+  Use the `influx restore` command to restore backup data and metadata from InfluxDB.
+menu:
+  influxdb_2_2:
+    parent: Back up & restore data
+weight: 101
+influxdb/v2.2/tags: [restore]
+related:
+  - /influxdb/v2.2/backup-restore/backup/
+  - /influxdb/v2.2/reference/cli/influxd/restore/
+products: [oss]
+---
+
+{{% cloud %}}
+Restores **not supported in {{< cloud-name "short" >}}**.
+{{% /cloud %}}
+
+Use the `influx restore` command to restore backup data and metadata from InfluxDB OSS.
+
+- [Restore data with the influx CLI](#restore-data-with-the-influx-cli)
+- [Recover from a failed restore](#recover-from-a-failed-restore)
+
+InfluxDB moves existing data and metadata to a temporary location.
+If the restore fails, InfluxDB preserves temporary data for recovery,
+otherwise this data is deleted.
+_See [Recover from a failed restore](#recover-from-a-failed-restore)._
+
+{{% note %}}
+#### Cannot restore to existing buckets
+The `influx restore` command cannot restore data to existing buckets.
+Use the `--new-bucket` flag to create a new bucket to restore data to.
+To restore data and retain bucket names, [delete existing buckets](/influxdb/v2.2/organizations/buckets/delete-bucket/)
+and then begin the restore process.
+{{% /note %}}
+
+## Restore data with the influx CLI
+Use the `influx restore` command and specify the path to the backup directory.
+
+_For more information about restore options and flags, see the
+[`influx restore` documentation](/influxdb/v2.2/reference/cli/influx/restore/)._
+
+- [Restore all time series data](#restore-all-time-series-data)
+- [Restore data from a specific bucket](#restore-data-from-a-specific-bucket)
+- [Restore and replace all InfluxDB data](#restore-and-replace-all-influxdb-data)
+
+### Restore all time series data
+To restore all time series data from a backup directory, provide the following:
+
+- backup directory path
+
+```sh
+influx restore /backups/2020-01-20_12-00/
+```
+
+### Restore data from a specific bucket
+To restore data from a specific backup bucket, provide the following:
+
+- backup directory path
+- bucket name or ID
+
+```sh
+influx restore \
+  /backups/2020-01-20_12-00/ \
+  --bucket example-bucket
+
+# OR
+
+influx restore \
+  /backups/2020-01-20_12-00/ \
+  --bucket-id 000000000000
+```
+
+If a bucket with the same name as the backed up bucket already exists in InfluxDB,
+use the `--new-bucket` flag to create a new bucket with a different name and
+restore data into it.
+
+```sh
+influx restore \
+  /backups/2020-01-20_12-00/ \
+  --bucket example-bucket \
+  --new-bucket new-example-bucket
+```
+
+### Restore and replace all InfluxDB data
+To restore and replace all time series data _and_ InfluxDB key-value data such as
+tokens, users, dashboards, etc., include the following:
+
+- `--full` flag
+- backup directory path
+
+```sh
+influx restore \
+  /backups/2020-01-20_12-00/ \
+  --full
+```
+
+{{% note %}}
+#### Restore to a new InfluxDB server
+If using a backup to populate a new InfluxDB server:
+
+1. Retrieve the [admin token](/influxdb/v2.2/security/tokens/#admin-token) from your source InfluxDB instance.
+2. Set up your new InfluxDB instance, but use the `-t`, `--token` flag to use the
+   **admin token** from your source instance as the admin token on your new instance.
+
+    ```sh
+    influx setup --token My5uP3rSecR37t0keN
+    ```
+3. Restore the backup to the new server.
+
+    ```sh
+    influx restore \
+      /backups/2020-01-20_12-00/ \
+      --full
+    ```
+
+If you do not provide the admin token from your source InfluxDB instance as the
+admin token in your new instance, the restore process and all subsequent attempts
+to authenticate with the new server will fail.
+
+1. The first restore API call uses the auto-generated token to authenticate with
+   the new server and overwrites the entire key-value store in the new server, including
+   the auto-generated token.
+2. The second restore API call attempts to upload time series data, but uses the
+   auto-generated token to authenticate with new server.
+   That token is overwritten in first restore API call and the process fails to authenticate.
+{{% /note %}}
+
+
+## Recover from a failed restore
+If the restoration process fails, InfluxDB preserves existing data in a `tmp`
+directory in the [target engine path](/influxdb/v2.2/reference/cli/influx/restore/#flags)
+(default is `~/.influxdbv2/engine`).
+
+To recover from a failed restore:
+
+1. Copy the temporary files back into the `engine` directory.
+2. Remove the `.tmp` extensions from each of the copied files.
+3. Restart the `influxd` server.
diff --git a/content/influxdb/v2.2/get-started.md b/content/influxdb/v2.2/get-started.md
new file mode 100644
index 000000000..5a96a089b
--- /dev/null
+++ b/content/influxdb/v2.2/get-started.md
@@ -0,0 +1,59 @@
+---
+title: Get started with InfluxDB
+description: >
+  Start collecting, processing, and visualizing data in InfluxDB OSS.
+menu:
+  influxdb_2_2:
+    name: Get started
+weight: 3
+influxdb/v2.2/tags: [get-started]
+aliases:
+  - /influxdb/v2.2/introduction/get-started/
+---
+
+After you've [installed InfluxDB OSS](/influxdb/v2.2/install/), you're ready to get started. Explore the following ways to work with your data:
+
+- [Collect and write data](#collect-and-write-data)
+- [Query data](#query-data)
+- [Process data](#process-data)
+- [Visualize data](#visualize-data)
+- [Monitor and alert](#monitor-and-alert)
+
+### Collect and write data
+
+Collect and write data to InfluxDB using the Telegraf plugins, the InfluxDB v2 API, the `influx` command line interface (CLI), the InfluxDB UI (the user interface for InfluxDB 2.2), or the InfluxDB v2 API client libraries.
+
+#### Use Telegraf
+
+Use Telegraf to quickly write data to {{< cloud-name >}}.
+Create new Telegraf configurations automatically in the InfluxDB UI, or manually update an existing Telegraf configuration to send data to your {{< cloud-name "short" >}} instance.
+
+For details, see [Automatically configure Telegraf](/influxdb/v2.2/write-data/no-code/use-telegraf/auto-config/)
+and [Manually update Telegraf configurations](/influxdb/v2.2/write-data/no-code/use-telegraf/manual-config/).
+
+#### Scrape data
+
+**InfluxDB OSS** lets you scrape Prometheus-formatted metrics from HTTP endpoints. For details, see [Scrape data](/influxdb/v2.2/write-data/no-code/scrape-data/).
+
+#### API, CLI, and client libraries
+
+For information about using the InfluxDB v2 API, `influx` CLI, and client libraries to write data, see [Write data to InfluxDB](/influxdb/v2.2/write-data/).
+
+### Query data
+
+Query data using Flux, the UI, and the `influx` command line interface.
+See [Query data](/influxdb/v2.2/query-data/).
+
+### Process data
+
+Use InfluxDB tasks to process and downsample data. See [Process data](/influxdb/v2.2/process-data/).
+
+### Visualize data
+
+Build custom dashboards to visualize your data.
+See [Visualize data](/influxdb/v2.2/visualize-data/).
+
+### Monitor and alert
+
+Monitor your data and sends alerts based on specified logic.
+See [Monitor and alert](/influxdb/v2.2/monitor-alert/).
diff --git a/content/influxdb/v2.2/influxdb-templates/_index.md b/content/influxdb/v2.2/influxdb-templates/_index.md
new file mode 100644
index 000000000..cf83154da
--- /dev/null
+++ b/content/influxdb/v2.2/influxdb-templates/_index.md
@@ -0,0 +1,98 @@
+---
+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_2
+weight: 10
+influxdb/v2.2/tags: [templates]
+---
+
+InfluxDB templates are prepackaged InfluxDB configurations that contain everything
+from dashboards and Telegraf configurations to notifications and alerts.
+Use templates to monitor your technology stack,
+set up a fresh instance of InfluxDB, back up your dashboard configuration, or
+[share your configuration](https://github.com/influxdata/community-templates/) with the InfluxData community.
+
+**InfluxDB templates do the following:**
+
+- Reduce setup time by giving you resources that are already configured for your use-case.
+- Facilitate secure, portable, and source-controlled InfluxDB resource states.
+- Simplify sharing and using pre-built InfluxDB solutions.
+
+{{< youtube 2JjW4Rym9XE >}}
+
+<a class="btn github" href="https://github.com/influxdata/community-templates/" target="_blank">View InfluxDB community templates</a>
+
+## Template manifests
+
+A template **manifest** is a file that defines
+InfluxDB [resources](#template-resources).
+Template manifests support the following formats:
+
+- [YAML](https://yaml.org/)
+- [JSON](https://www.json.org/)
+- [Jsonnet](https://jsonnet.org/)
+
+{{% note %}}
+Template manifests are compatible with
+[Kubernetes Custom Resource Definitions (CRD)](https://kubernetes.io/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions/).
+{{% /note %}}
+
+The `metadata.name` field in manifests uniquely identifies each resource in the template.
+`metadata.name` values must be [DNS-1123](https://tools.ietf.org/html/rfc1123) compliant.
+The `spec` object contains the resource configuration.
+
+#### Example
+
+```yaml
+# bucket-template.yml
+# Template manifest that defines two buckets.
+apiVersion: influxdata.com/v2alpha1
+kind: Bucket
+metadata:
+    name: thirsty-shaw-91b005
+spec:
+    description: My IoT Center Bucket
+    name: iot-center
+    retentionRules:
+      - everySeconds: 86400
+        type: expire
+---
+apiVersion: influxdata.com/v2alpha1
+kind: Bucket
+metadata:
+    name: upbeat-fermat-91b001
+spec:
+    name: air_sensor
+---
+```
+
+_See [Create an InfluxDB template](/influxdb/v2.2/influxdb-templates/create/) for information about
+generating template manifests._
+
+### Template resources
+
+Templates may contain the following InfluxDB resources:
+
+- [buckets](/influxdb/v2.2/organizations/buckets/create-bucket/)
+- [checks](/influxdb/v2.2/monitor-alert/checks/create/)
+- [dashboards](/influxdb/v2.2/visualize-data/dashboards/create-dashboard/)
+- [dashboard variables](/influxdb/v2.2/visualize-data/variables/create-variable/)
+- [labels](/influxdb/v2.2/visualize-data/labels/)
+- [notification endpoints](/influxdb/v2.2/monitor-alert/notification-endpoints/create/)
+- [notification rules](/influxdb/v2.2/monitor-alert/notification-rules/create/)
+- [tasks](/influxdb/v2.2/process-data/manage-tasks/create-task/)
+- [Telegraf configurations](/influxdb/v2.2/write-data/no-code/use-telegraf/)
+
+## Stacks
+
+Use **InfluxDB stacks** to manage InfluxDB templates.
+When you apply a template, InfluxDB associates resources in the template with a stack.
+Use stacks to add, update, or remove InfluxDB templates over time.
+
+For more information, see [InfluxDB stacks](#influxdb-stacks) below.
+
+---
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/influxdb-templates/create.md b/content/influxdb/v2.2/influxdb-templates/create.md
new file mode 100644
index 000000000..95de2cb32
--- /dev/null
+++ b/content/influxdb/v2.2/influxdb-templates/create.md
@@ -0,0 +1,291 @@
+---
+title: Create an InfluxDB template
+description: >
+  Use the InfluxDB UI and the `influx export` command to create InfluxDB templates.
+menu:
+  influxdb_2_2:
+    parent: InfluxDB templates
+    name: Create a template
+    identifier: Create an InfluxDB template
+weight: 103
+influxdb/v2.2/tags: [templates]
+related:
+  - /influxdb/v2.2/reference/cli/influx/export/
+  - /influxdb/v2.2/reference/cli/influx/export/all/
+---
+
+Use the InfluxDB user interface (UI) and the [`influx export` command](/influxdb/v2.2/reference/cli/influx/export/) to
+create InfluxDB templates from [resources](/influxdb/v2.2/influxdb-templates/#template-resources) in an organization.
+Add buckets, Telegraf configurations, tasks, and more in the InfluxDB
+UI and then export those resources as a template.
+
+{{< youtube 714uHkxKM6U >}}
+
+- [Create a template](#create-a-template)
+- [Export resources to a template](#export-resources-to-a-template)
+- [Include user-definable resource names](#include-user-definable-resource-names)
+- [Troubleshoot template results and permissions](#troubleshoot-template-results-and-permissions)
+- [Share your InfluxDB templates](#share-your-influxdb-templates)
+
+## Create a template
+
+Creating a new organization to contain only your template resources is an easy way
+to ensure you export the resources you want.
+Follow these steps to create a template from a new organization.
+
+1. [Start InfluxDB](/influxdb/v2.2/get-started/).
+2. [Create a new organization](/influxdb/v2.2/organizations/create-org/).
+3. In the InfluxDB UI, add one or more [resources](/influxdb/v2.2/influxdb-templates/#template-resources).
+4. [Create an **All-Access** API token](/influxdb/v2.2/security/tokens/create-token/) (or a token that has **read** access to the organization).
+5. Use the API token from **Step 4** with the [`influx export all` subcommand](/influxdb/v2.2/reference/cli/influx/export/all/) to [export all resources]() in the organization to a template file.
+
+   ```sh
+   influx export all \
+     -o YOUR_INFLUX_ORG \
+     -t YOUR_ALL_ACCESS_TOKEN \
+     -f ~/templates/template.yml
+   ```
+
+## Export resources to a template
+
+The [`influx export` command](/influxdb/v2.2/reference/cli/influx/export/) and subcommands let you
+export [resources](#template-resources) from an organization to a template manifest.
+Your [API token](/influxdb/v2.2/security/tokens/) must have **read** access to resources that you want to export.
+
+If you want to export resources that depend on other resources, be sure to export the dependencies.
+
+{{< cli/influx-creds-note >}}
+
+To create a template that **adds, modifies, and deletes resources** when applied to an organization, use [InfluxDB stacks](/influxdb/v2.2/influxdb-templates/stacks/).
+First, [initialize the stack](/influxdb/v2.2/influxdb-templates/stacks/init/)
+and then [export the stack](#export-a-stack).
+
+To create a template that only **adds resources** when applied to an organization (and doesn't modify existing resources there), choose one of the following:
+- [Export all resources](#export-all-resources) to export all resources or a filtered
+  subset of resources to a template.
+- [Export specific resources](#export-specific-resources) by name or ID to a template.
+
+### Export all resources
+
+To export all [resources](/influxdb/v2.2/influxdb-templates/#template-resources)
+within an organization to a template manifest file, use the
+[`influx export all` subcommand](/influxdb/v2.2/reference/cli/influx/export/all/)
+with the `--file` (`-f`) option.
+
+Provide the following:
+
+- **Destination path and filename** for the template manifest.
+  The filename extension determines the output format:
+  - `your-template.yml`: [YAML](https://yaml.org/) format
+  - `your-template.json`: [JSON](https://json.org/) format
+
+```sh
+# Syntax
+influx export all -f <FILE_PATH>
+```
+
+#### Export resources filtered by labelName or resourceKind
+
+The [`influx export all` subcommand](/influxdb/v2.2/reference/cli/influx/export/all/)
+accepts a `--filter` option that exports
+only resources that match specified label names or resource kinds.
+To filter on label name *and* resource kind, provide a `--filter` for each.
+
+#### Export only dashboards and buckets with specific labels
+
+The following example exports resources that match this predicate logic:
+
+```js
+(resourceKind == "Bucket" or resourceKind == "Dashboard")
+and
+(labelName == "Example1" or labelName == "Example2")
+```
+
+```sh
+influx export all \
+  -f ~/templates/template.yml \
+  --filter=resourceKind=Bucket \
+  --filter=resourceKind=Dashboard \
+  --filter=labelName=Example1 \
+  --filter=labelName=Example2
+```
+
+For more options and examples, see the
+[`influx export all` subcommand](/influxdb/v2.2/reference/cli/influx/export/all/).
+
+### Export specific resources
+
+To export specific [resources](/influxdb/v2.2/influxdb-templates/#template-resources) by name or ID, use the **[`influx export` command](/influxdb/v2.2/reference/cli/influx/export/)** with one or more lists of resources to include.
+
+Provide the following:
+
+- **Destination path and filename** for the template manifest.
+  The filename extension determines the output format:
+  - `your-template.yml`: [YAML](https://yaml.org/) format
+  - `your-template.json`: [JSON](https://json.org/) format
+- **Resource options** with corresponding lists of resource IDs or resource names to include in the template.
+  For information about what resource options are available, see the
+  [`influx export` command](/influxdb/v2.2/reference/cli/influx/export/).
+
+```sh
+# Syntax
+influx export -f <file-path> [resource-flags]
+```
+
+#### Export specific resources by ID
+```sh
+influx export \
+  --org-id ed32b47572a0137b \
+  -f ~/templates/template.yml \
+  -t $INFLUX_TOKEN \
+  --buckets=00x000ooo0xx0xx,o0xx0xx00x000oo \
+  --dashboards=00000xX0x0X00x000 \
+  --telegraf-configs=00000x0x000X0x0X0
+```
+
+#### Export specific resources by name
+```sh
+influx export \
+  --org-id ed32b47572a0137b \
+  -f ~/templates/template.yml \
+  --bucket-names=bucket1,bucket2 \
+  --dashboard-names=dashboard1,dashboard2 \
+  --telegraf-config-names=telegrafconfig1,telegrafconfig2
+```
+
+### Export a stack
+
+To export an InfluxDB [stack](/influxdb/v2.2/influxdb-templates/stacks/) and all its associated resources as a template, use the
+`influx export stack` command.
+Provide the following:
+
+- **Organization name** or **ID**
+- **API token** with read access to the organization
+- **Destination path and filename** for the template manifest.
+  The filename extension determines the output format:
+  - `your-template.yml`: [YAML](https://yaml.org/) format
+  - `your-template.json`: [JSON](https://json.org/) format
+- **Stack ID**
+
+#### Export a stack as a template
+
+```sh
+# Syntax
+influx export stack \
+  -o <INFLUX_ORG> \
+  -t <INFLUX_TOKEN> \
+  -f <FILE_PATH> \
+  <STACK_ID>
+
+# Example
+influx export stack \
+  -o my-org \
+  -t mYSuP3RS3CreTt0K3n
+  -f ~/templates/awesome-template.yml \
+  05dbb791a4324000
+```
+
+## Include user-definable resource names
+
+After exporting a template manifest, replace resource names with **environment references**
+to let users customize resource names when installing your template.
+
+1. [Export a template](#export-a-template).
+2. Select any of the following resource fields to update:
+
+    - `metadata.name`
+    - `associations[].name`
+    - `endpointName` _(unique to `NotificationRule` resources)_
+
+3. Replace the resource field value with an `envRef` object with a `key` property
+    that references the key of a key-value pair the user provides when installing the template.
+    During installation, the `envRef` object is replaced by the value of the
+    referenced key-value pair.
+    If the user does not provide the environment reference key-value pair, InfluxDB
+    uses the `key` string as the default value.
+
+    {{< code-tabs-wrapper >}}
+    {{% code-tabs %}}
+[YAML](#)
+[JSON](#)
+  {{% /code-tabs %}}
+  {{% code-tab-content %}}
+```yml
+apiVersion: influxdata.com/v2alpha1
+kind: Bucket
+metadata:
+  name:
+    envRef:
+      key: bucket-name-1
+```
+  {{% /code-tab-content %}}
+  {{% code-tab-content %}}
+```json
+{
+  "apiVersion": "influxdata.com/v2alpha1",
+  "kind": "Bucket",
+  "metadata": {
+    "name": {
+      "envRef": {
+        "key": "bucket-name-1"
+      }
+    }
+  }
+}
+```
+  {{% /code-tab-content %}}
+  {{< /code-tabs-wrapper >}}
+
+Using the example above, users are prompted to provide a value for `bucket-name-1`
+when [applying the template](/influxdb/v2.2/influxdb-templates/use/#apply-templates).
+Users can also include the `--env-ref` flag with the appropriate key-value pair
+when installing the template.
+
+```sh
+# Set bucket-name-1 to "myBucket"
+influx apply \
+  -f /path/to/template.yml \
+  --env-ref=bucket-name-1=myBucket
+```
+
+_If sharing your template, we recommend documenting what environment references
+exist in the template and what keys to use to replace them._
+
+{{% note %}}
+#### Resource fields that support environment references
+
+Only the following fields support environment references:
+
+- `metadata.name`
+- `spec.endpointName`
+- `spec.associations.name`
+{{% /note %}}
+
+## Troubleshoot template results and permissions
+
+If you get unexpected results, missing resources, or errors when exporting
+templates, check the following:
+- [Ensure `read` access](#ensure-read-access)
+- [Use Organization ID](#use-organization-id)
+- [Check for resource dependencies](#check-for-resource-dependencies)
+
+### Ensure read access
+
+The [API token](/influxdb/v2.2/security/tokens/) must have **read** access to resources that you want to export. The `influx export all` command only exports resources that the API token can read. For example, to export all resources in an organization that has ID `abc123`, the API token must have the `read:/orgs/abc123` permission.
+
+To learn more about permissions, see [how to view authorizations](/influxdb/v2.2/security/tokens/view-tokens/) and [how to create a token](/influxdb/v2.2/security/tokens/create-token/) with specific permissions.
+
+### Use Organization ID
+
+If your token doesn't have **read** access to the organization and you want to [export specific resources](#export-specific-resources), use the `--org-id <org-id>` flag (instead of `-o <org-name>` or `--org <org-name>`) to provide the organization.
+
+### Check for resource dependencies
+
+If you want to export resources that depend on other resources, be sure to export the dependencies as well. Otherwise, the resources may not be usable.
+
+## Share your InfluxDB templates
+
+Share your InfluxDB templates with the entire InfluxData community.
+Contribute your template to the [InfluxDB Community Templates](https://github.com/influxdata/community-templates/) repository on GitHub.
+
+<a class="btn" href="https://github.com/influxdata/community-templates/" target="\_blank">View InfluxDB Community Templates</a>
diff --git a/content/influxdb/v2.2/influxdb-templates/stacks/_index.md b/content/influxdb/v2.2/influxdb-templates/stacks/_index.md
new file mode 100644
index 000000000..47594f68b
--- /dev/null
+++ b/content/influxdb/v2.2/influxdb-templates/stacks/_index.md
@@ -0,0 +1,26 @@
+---
+title: InfluxDB stacks
+description: >
+  Use an InfluxDB stack to manage your InfluxDB templates—add, update, or remove templates over time.
+menu:
+  influxdb_2_2:
+    parent: InfluxDB templates
+weight: 105
+related:
+  - /influxdb/v2.2/reference/cli/influx/pkg/stack/
+---
+
+Use InfluxDB stacks to manage [InfluxDB templates](/influxdb/v2.2/influxdb-templates).
+When you apply a template, InfluxDB associates resources in the template with a stack. Use the stack to add, update, or remove InfluxDB templates over time.
+
+  {{< children type="anchored-list" >}}
+
+  {{< children readmore=true >}}
+
+{{% note %}}
+**Key differences between stacks and templates**:
+
+- A template defines a set of resources in a text file outside of InfluxDB. When you apply a template, a stack is automatically created to manage the applied template.
+- Stacks add, modify or delete resources in an instance.
+- Templates do not recognize resources in an instance. All resources in the template are added, creating duplicate resources if a resource already exists.
+  {{% /note %}}
diff --git a/content/influxdb/v2.2/influxdb-templates/stacks/init.md b/content/influxdb/v2.2/influxdb-templates/stacks/init.md
new file mode 100644
index 000000000..2b4de1944
--- /dev/null
+++ b/content/influxdb/v2.2/influxdb-templates/stacks/init.md
@@ -0,0 +1,73 @@
+---
+title: Initialize an InfluxDB stack
+list_title: Initialize a stack
+description: >
+  InfluxDB automatically creates a new stack each time you [apply an InfluxDB template](/influxdb/v2.2/influxdb-templates/use/)
+  **without providing a stack ID**.
+  To manually create or initialize a new stack, use the [`influx stacks init` command](/influxdb/v2.2/reference/cli/influx/stacks/init/).
+menu:
+  influxdb_2_2:
+    parent: InfluxDB stacks
+    name: Initialize a stack
+weight: 202
+related:
+  - /influxdb/v2.2/reference/cli/influx/stacks/init/
+list_code_example: |
+  ```sh
+  influx apply \
+    -o example-org \
+    -f path/to/template.yml
+  ```
+  ```sh
+  influx stacks init \
+    -o example-org \
+    -n "Example Stack" \
+    -d "InfluxDB stack for monitoring some awesome stuff" \
+    -u https://example.com/template-1.yml \
+    -u https://example.com/template-2.yml
+  ```
+---
+
+InfluxDB automatically creates a new stack each time you [apply an InfluxDB template](/influxdb/v2.2/influxdb-templates/use/)
+**without providing a stack ID**.
+To manually create or initialize a new stack, use the [`influx stacks init` command](/influxdb/v2.2/reference/cli/influx/stacks/init/).
+
+## Initialize a stack when applying a template
+To automatically create a new stack when [applying an InfluxDB template](/influxdb/v2.2/influxdb-templates/use/)
+**don't provide a stack ID**.
+InfluxDB applies the resources in the template to a new stack and provides the **stack ID** the output.
+
+```sh
+influx apply \
+  -o example-org \
+  -f path/to/template.yml
+```
+
+## Manually initialize a new stack
+Use the [`influx stacks init` command](/influxdb/v2.2/reference/cli/influx/stacks/init/)
+to create or initialize a new InfluxDB stack.
+
+**Provide the following:**
+
+- Organization name or ID
+- Stack name
+- Stack description
+- InfluxDB template URLs
+
+<!-- -->
+```sh
+# Syntax
+influx stacks init \
+  -o <org-name> \
+  -n <stack-name> \
+  -d <stack-description \
+  -u <package-url>
+
+# Example
+influx stacks init \
+  -o example-org \
+  -n "Example Stack" \
+  -d "InfluxDB stack for monitoring some awesome stuff" \
+  -u https://example.com/template-1.yml \
+  -u https://example.com/template-2.yml
+```
diff --git a/content/influxdb/v2.2/influxdb-templates/stacks/remove.md b/content/influxdb/v2.2/influxdb-templates/stacks/remove.md
new file mode 100644
index 000000000..3df204550
--- /dev/null
+++ b/content/influxdb/v2.2/influxdb-templates/stacks/remove.md
@@ -0,0 +1,39 @@
+---
+title: Remove an InfluxDB stack
+list_title: Remove a stack
+description: >
+  Use the [`influx stacks remove` command](/influxdb/v2.2/reference/cli/influx/stacks/remove/)
+  to remove an InfluxDB stack and all its associated resources.
+menu:
+  influxdb_2_2:
+    parent: InfluxDB stacks
+    name: Remove a stack
+weight: 205
+related:
+  - /influxdb/v2.2/reference/cli/influx/stacks/remove/
+list_code_example: |
+  ```sh
+  influx stacks remove \
+    -o example-org \
+    --stack-id=12ab34cd56ef
+  ```
+---
+
+Use the [`influx stacks remove` command](/influxdb/v2.2/reference/cli/influx/stacks/remove/)
+to remove an InfluxDB stack and all its associated resources.
+
+**Provide the following:**
+
+- Organization name or ID
+- Stack ID
+
+<!-- -->
+```sh
+# Syntax
+influx stacks remove -o <org-name> --stack-id=<stack-id>
+
+# Example
+influx stacks remove \
+  -o example-org \
+  --stack-id=12ab34cd56ef
+```
diff --git a/content/influxdb/v2.2/influxdb-templates/stacks/save-time.md b/content/influxdb/v2.2/influxdb-templates/stacks/save-time.md
new file mode 100644
index 000000000..cce0e1d19
--- /dev/null
+++ b/content/influxdb/v2.2/influxdb-templates/stacks/save-time.md
@@ -0,0 +1,165 @@
+---
+title: Save time with InfluxDB stacks
+list_title: Save time with stacks
+description: >
+  Discover how to use InfluxDB stacks to save time.
+menu:
+  influxdb_2_2:
+    parent: InfluxDB stacks
+    name: Save time with stacks
+weight: 201
+related:
+  - /influxdb/v2.2/reference/cli/influx/stacks/
+
+---
+
+Save time and money using InfluxDB stacks. Here's a few ideal use cases:
+
+- [Automate deployments with GitOps and stacks](#automate-deployments-with-gitops-and-stacks)
+- [Apply updates from source-controlled templates](#apply-updates-from-source-controlled-templates)
+- [Apply template updates across multiple InfluxDB instances](#apply-template-updates-across-multiple-influxdb-instances)
+- [Develop templates](#develop-templates)
+
+### Automate deployments with GitOps and stacks
+
+GitOps is popular way to configure and automate deployments. Use InfluxDB stacks in a GitOps workflow
+to automatically update distributed instances of InfluxDB OSS or InfluxDB Cloud.
+
+To automate an InfluxDB deployment with GitOps and stacks, complete the following steps:
+
+1. [Set up a GitHub repository](#set-up-a-github-repository)
+2. [Add existing resources to the GitHub repository](#add-existing-resources-to-the-github-repository)
+3. [Automate the creation of a stack for each folder](#automate-the-creation-of-a-stack-for-each-folder)
+4. [Set up Github Actions or CircleCI](#set-up-github-actions-or-circleci)
+
+#### Set up a GitHub repository
+
+Set up a GitHub repository to back your InfluxDB instance. Determine how you want to organize the resources in your stacks within your Github repository. For example, organize resources under folders for specific teams or functions.
+
+We recommend storing all resources for one stack in the same folder. For example, if you monitor Redis, create a `redis` stack and put your Redis monitoring resources (a Telegraf configuration, four dashboards, a label, and two alert checks) into one Redis folder, each resource in a separate file. Then, when you need to update a Redis resource, it's easy to find and make changes in one location.
+
+  {{% note %}}
+  Typically, we **do not recommend** using the same resource in multiple stacks. If your organization uses the same resource in multiple stacks, before you delete a stack, verify the stack does not include resources that another stack depends on. Stacks with buckets often contain data used by many different templates. Because of this, we recommend keeping buckets separate from the other stacks.
+  {{% /note %}}
+
+#### Add existing resources to the GitHub repository
+
+Skip this section if you are starting from scratch or don’t have existing resources you want to add to your stack. 
+
+Use the `influx export` command to quickly export resources. Keep all your resources in a single file or have files for each one. You can always split or combine them later.
+
+For example, if you export resources for three stacks: `buckets`, `redis`, and `mysql`, your folder structure might look something like this when you are done:
+
+  ```sh
+  influxdb-assets/
+  ├── buckets/
+  │   ├── telegraf_bucket.yml
+  ├── redis/
+  │   ├── redis_overview_dashboard.yml
+  │   ├── redis_label.yml
+  │   ├── redis_cpu_check.yml
+  │   └── redis_mem_check.yml
+  ├── mysql/
+  │   ├── mysql_assets.yml
+  └── README.md
+
+  ```
+  {{% note %}}
+  When you export a resource, InfluxDB creates a `meta.name` for that resource. These resource names should be unique inside your InfluxDB instance. Use a good naming convention to prevent duplicate `meta.names`. Changing the `meta.name` of the InfluxDB resource will cause the stack to orphan the resource with the previous name and create a new resource with the updated name.
+  {{% /note %}}
+
+Add the exported resources to your new GitHub repository.
+
+#### Automate the creation of a stack for each folder
+
+To automatically create a stack from each folder in your GitHub repository, create a shell script to check for an existing stack and if the stack isn't found, use the `influx stacks init` command to create a new stack. The following sample script creates a `redis` stack and automatically applies those changes to your instance:
+
+```sh
+echo "Checking for existing redis stack..."
+REDIS_STACK_ID=$(influx stacks --stack-name redis --json | jq -r '.[0].ID')
+if [ "$REDIS_STACK_ID" == "null" ]; then
+    echo "No stack found. Initializing our stack..."
+    REDIS_STACK_ID=$(influx stacks init -n redis --json | jq -r '.ID')
+fi
+
+# Setting the base path
+BASE_PATH="$(pwd)"
+
+echo "Applying our redis stack..."
+cat $BASE_PATH/redis/*.yml | \
+influx apply --force true --stack-id $REDIS_STACK_ID -q
+```
+
+  {{% note %}}
+  The `--json` flag in the InfluxDB CLI is very useful when scripting against the CLI. This flag lets you grab important information easily using [`jq`](https://stedolan.github.io/jq/manual/v1.6/).
+  {{% /note %}}
+
+Repeat this step for each of the stacks in your repository. When a resource in your stack changes, re-run this script to apply updated resources to your InfluxDB instance. Re-applying a stack with an updated resource won't add, delete, or duplicate resources.
+
+#### Set up Github Actions or CircleCI
+
+Once you have a script to apply changes being made to your local instance, automate the deployment to other environments as needed. Use the InfluxDB CLI to maintain multiple [configuration profiles]() to easily switch profile and issue commands against other InfluxDB instances. To apply the same script to a different InfluxDB instance, change your active configuration profile using the `influx config set` command. Or set the desired profile dynamically using the `-c, --active-config` flag.
+
+  {{% note %}}
+  Before you run automation scripts against shared environments, we recommend manually running the steps in your script.
+  {{% /note %}}
+
+Verify your deployment automation software lets you run a custom script, and then set up the custom script you've built locally another environment. For example, here's a custom Github Action that automates deployment:
+
+```yml
+name: deploy-influxdb-resources
+
+on:
+  push:
+    branches: [ master ]
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v2
+      with:
+        ref: ${{ github.ref }}
+    - name: Deploys repo to cloud
+      env:
+        # These secrets can be configured in the Github repo to connect to 
+        # your InfluxDB instance.
+        INFLUX_TOKEN: ${{ secrets.INFLUX_TOKEN }}
+        INFLUX_ORG: ${{ secrets.INFLUX_ORG }}
+        INFLUX_URL: ${{ secrets.INFLUX_URL }}
+        GITHUB_REPO: ${{ github.repository }}
+        GITHUB_BRANCH: ${{ github.ref }}  
+      run: |
+        cd /tmp
+        wget https://dl.influxdata.com/platform/nightlies/influx_nightly_linux_amd64.tar.gz
+        tar xvfz influx_nightly_linux_amd64.tar.gz
+        sudo cp influx_nightly_linux_amd64/influx /usr/local/bin/
+        cd $GITHUB_WORKSPACE
+        # This runs the script to set up your stacks
+        chmod +x ./setup.sh
+        ./setup.sh prod
+```
+
+For more information about using GitHub Actions in your project, check out the complete [Github Actions documentation](https://github.com/features/actions).
+
+### Apply updates from source-controlled templates
+
+You can use a variety of InfluxDB templates from many different sources including
+[Community Templates](https://github.com/influxdata/community-templates/) or
+self-built custom templates.
+As templates are updated over time, stacks let you gracefully
+apply updates without creating duplicate resources.
+
+### Apply template updates across multiple InfluxDB instances
+
+In many cases, you may have more than one instance of InfluxDB running and want to apply
+the same template to each separate instance.
+Using stacks, you can make changes to a stack on one instance,
+[export the stack as a template](/influxdb/v2.2/influxdb-templates/create/#export-a-stack)
+and then apply the changes to your other InfluxDB instances.
+
+### Develop templates
+
+InfluxDB stacks aid in developing and maintaining InfluxDB templates.
+Stacks let you modify and update template manifests and apply those changes in
+any stack that uses the template.
diff --git a/content/influxdb/v2.2/influxdb-templates/stacks/update.md b/content/influxdb/v2.2/influxdb-templates/stacks/update.md
new file mode 100644
index 000000000..7c861a339
--- /dev/null
+++ b/content/influxdb/v2.2/influxdb-templates/stacks/update.md
@@ -0,0 +1,56 @@
+---
+title: Update an InfluxDB stack
+list_title: Update a stack
+description: >
+  Use the [`influx apply` command](/influxdb/v2.2/reference/cli/influx/apply/)
+  to update a stack with a modified template.
+  When applying a template to an existing stack, InfluxDB checks to see if the
+  resources in the template match existing resources.
+  InfluxDB updates, adds, and removes resources to resolve differences between
+  the current state of the stack and the newly applied template.
+menu:
+  influxdb_2_2:
+    parent: InfluxDB stacks
+    name: Update a stack
+weight: 203
+related:
+  - /influxdb/v2.2/reference/cli/influx/apply
+  - /influxdb/v2.2/reference/cli/influx/stacks/update/
+list_code_example: |
+  ```sh
+  influx apply \
+    -o example-org \
+    -u http://example.com/template-1.yml \
+    -u http://example.com/template-2.yml \
+    --stack-id=12ab34cd56ef
+  ```
+---
+
+Use the [`influx apply` command](/influxdb/v2.2/reference/cli/influx/apply/)
+to update a stack with a modified template.
+When applying a template to an existing stack, InfluxDB checks to see if the
+resources in the template match existing resources.
+InfluxDB updates, adds, and removes resources to resolve differences between
+the current state of the stack and the newly applied template.
+
+Each stack is uniquely identified by a **stack ID**.
+For information about retrieving your stack ID, see [View stacks](/influxdb/v2.2/influxdb-templates/stacks/view/).
+
+**Provide the following:**
+
+- Organization name or ID
+- Stack ID
+- InfluxDB template URLs to apply
+
+<!-- -->
+```sh
+influx apply \
+  -o example-org \
+  -u http://example.com/template-1.yml \
+  -u http://example.com/template-2.yml \
+  --stack-id=12ab34cd56ef
+```
+
+Template resources are uniquely identified by their `metadata.name` field.
+If errors occur when applying changes to a stack, all applied changes are
+reversed and the stack is returned to its previous state.
diff --git a/content/influxdb/v2.2/influxdb-templates/stacks/view.md b/content/influxdb/v2.2/influxdb-templates/stacks/view.md
new file mode 100644
index 000000000..46537eed0
--- /dev/null
+++ b/content/influxdb/v2.2/influxdb-templates/stacks/view.md
@@ -0,0 +1,69 @@
+---
+title: View InfluxDB stacks
+list_title: View stacks
+description: >
+  Use the [`influx stacks` command](/influxdb/v2.2/reference/cli/influx/stacks/)
+  to view installed InfluxDB stacks and their associated resources.
+menu:
+  influxdb_2_2:
+    parent: InfluxDB stacks
+    name: View stacks
+weight: 204
+related:
+  - /influxdb/v2.2/reference/cli/influx/stacks/
+list_code_example: |
+  ```sh
+  influx stacks -o example-org
+  ```
+---
+
+Use the [`influx stacks` command](/influxdb/v2.2/reference/cli/influx/stacks/)
+to view installed InfluxDB stacks and their associated resources.
+
+**Provide the following:**
+
+- Organization name or ID
+
+<!-- -->
+```sh
+# Syntax
+influx stacks -o <org-name>
+
+# Example
+influx stacks -o example-org
+```
+
+### Filter stacks
+
+To output information about specific stacks, use the `--stack-name` or `--stack-id`
+flags to filter output by stack names or stack IDs.
+
+##### Filter by stack name
+
+```sh
+# Syntax
+influx stacks \
+  -o <org-name> \
+  --stack-name=<stack-name>
+
+# Example
+influx stacks \
+  -o example-org \
+  --stack-name=stack1 \
+  --stack-name=stack2
+```
+
+### Filter by stack ID
+
+```sh
+# Syntax
+influx stacks \
+  -o <org-name> \
+  --stack-id=<stack-id>
+
+# Example
+influx stacks \
+  -o example-org \
+  --stack-id=12ab34cd56ef \
+  --stack-id=78gh910i11jk
+```
diff --git a/content/influxdb/v2.2/influxdb-templates/use.md b/content/influxdb/v2.2/influxdb-templates/use.md
new file mode 100644
index 000000000..e52705449
--- /dev/null
+++ b/content/influxdb/v2.2/influxdb-templates/use.md
@@ -0,0 +1,241 @@
+---
+title: Use InfluxDB templates
+description: >
+  Use the `influx` command line interface (CLI) to summarize, validate, and apply
+  templates from your local filesystem and from URLs.
+menu:
+  influxdb_2_2:
+    parent: InfluxDB templates
+    name: Use templates
+weight: 102
+influxdb/v2.2/tags: [templates]
+related:
+  - /influxdb/v2.2/reference/cli/influx/apply/
+  - /influxdb/v2.2/reference/cli/influx/template/
+  - /influxdb/v2.2/reference/cli/influx/template/validate/
+---
+
+Use the `influx` command line interface (CLI) to summarize, validate, and apply
+templates from your local filesystem and from URLs.
+
+- [Use InfluxDB community templates](#use-influxdb-community-templates)
+- [View a template summary](#view-a-template-summary)
+- [Validate a template](#validate-a-template)
+- [Apply templates](#apply-templates)
+
+
+## Use InfluxDB community templates
+The [InfluxDB community templates repository](https://github.com/influxdata/community-templates/)
+is home to a growing number of InfluxDB templates developed and maintained by
+others in the InfluxData community.
+Apply community templates directly from GitHub using a template's download URL
+or download the template.
+
+{{< youtube 2JjW4Rym9XE >}}
+
+{{% note %}}
+When attempting to access the community templates via the URL, the templates use the following
+as the root of the URL:
+
+```sh
+https://raw.githubusercontent.com/influxdata/community-templates/master/
+```
+
+For example, the Docker community template can be accessed via:
+
+```sh
+https://raw.githubusercontent.com/influxdata/community-templates/master/docker/docker.yml
+```
+{{% /note %}}
+
+<a class="btn" href="https://github.com/influxdata/community-templates/" target="\_blank">View InfluxDB Community Templates</a>
+
+## View a template summary
+To view a summary of what's included in a template before applying the template,
+use the [`influx template` command](/influxdb/v2.2/reference/cli/influx/template/).
+View a summary of a template stored in your local filesystem or from a URL.
+
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[From a file](#)
+[From a URL](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```sh
+# Syntax
+influx template -f <FILE_PATH>
+
+# Example
+influx template -f /path/to/template.yml
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```sh
+# Syntax
+influx template -u <FILE_URL>
+
+# Example
+influx template -u https://raw.githubusercontent.com/influxdata/community-templates/master/linux_system/linux_system.yml
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+## Validate a template
+To validate a template before you install it or troubleshoot a template, use
+the [`influx template validate` command](/influxdb/v2.2/reference/cli/influx/template/validate/).
+Validate a template stored in your local filesystem or from a URL.
+
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[From a file](#)
+[From a URL](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```sh
+# Syntax
+influx template validate -f <FILE_PATH>
+
+# Example
+influx template validate -f /path/to/template.yml
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```sh
+# Syntax
+influx template validate -u <FILE_URL>
+
+# Example
+influx template validate -u https://raw.githubusercontent.com/influxdata/community-templates/master/linux_system/linux_system.yml
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+## Apply templates
+Use the [`influx apply` command](/influxdb/v2.2/reference/cli/influx/apply/) to install templates
+from your local filesystem or from URLs.
+
+- [Apply a template from a file](#apply-a-template-from-a-file)
+- [Apply all templates in a directory](#apply-all-templates-in-a-directory)
+- [Apply a template from a URL](#apply-a-template-from-a-url)
+- [Apply templates from both files and URLs](#apply-templates-from-both-files-and-urls)
+- [Define environment references](#define-environment-references)
+- [Include a secret when installing a template](#include-a-secret-when-installing-a-template)
+
+{{% note %}}
+#### Apply templates to an existing stack
+To apply a template to an existing stack, include the stack ID when applying the template.
+Any time you apply a template without a stack ID, InfluxDB initializes a new stack
+and all new resources.
+For more information, see [InfluxDB stacks](/influxdb/v2.2/influxdb-templates/stacks/).
+{{% /note %}}
+
+### Apply a template from a file
+To install templates stored on your local machine, use the `-f` or `--file` flag
+to provide the **file path** of the template manifest.
+
+```sh
+# Syntax
+influx apply -o <INFLUX_ORG> -f <FILE_PATH>
+
+# Examples
+# Apply a single template
+influx apply -o example-org -f /path/to/template.yml
+
+# Apply multiple templates
+influx apply -o example-org \
+  -f /path/to/this/template.yml \
+  -f /path/to/that/template.yml
+```
+
+### Apply all templates in a directory
+To apply all templates in a directory, use the `-f` or `--file` flag to provide
+the **directory path** of the directory where template manifests are stored.
+By default, this only applies templates stored in the specified directory.
+To apply all templates stored in the specified directory and its subdirectories,
+include the `-R`, `--recurse` flag.
+
+```sh
+# Syntax
+influx apply -o <INFLUX_ORG> -f <DIRECTORY_PATH>
+
+# Examples
+# Apply all templates in a directory
+influx apply -o example-org -f /path/to/template/dir/
+
+# Apply all templates in a directory and its subdirectories
+influx apply -o example-org -f /path/to/template/dir/ -R
+```
+
+### Apply a template from a URL
+To apply templates from a URL, use the `-u` or `--template-url` flag to provide the URL
+of the template manifest.
+
+```sh
+# Syntax
+influx apply -o <INFLUX_ORG> -u <FILE_URL>
+
+# Examples
+# Apply a single template from a URL
+influx apply -o example-org -u https://example.com/templates/template.yml
+
+# Apply multiple templates from URLs
+influx apply -o example-org \
+  -u https://example.com/templates/template1.yml \
+  -u https://example.com/templates/template2.yml
+```
+
+### Apply templates from both files and URLs
+To apply templates from both files and URLs in a single command, include multiple
+file or directory paths and URLs, each with the appropriate `-f` or `-u` flag.
+
+```sh
+# Syntax
+influx apply -o <INFLUX_ORG> -u <FILE_URL> -f <FILE_PATH>
+
+# Example
+influx apply -o example-org \
+  -u https://example.com/templates/template1.yml \
+  -u https://example.com/templates/template2.yml \
+  -f ~/templates/custom-template.yml \
+  -f ~/templates/iot/home/ \
+  --recurse
+```
+
+### Define environment references
+Some templates include [environment references](/influxdb/v2.2/influxdb-templates/create/#include-user-definable-resource-names) that let you provide custom resource names.
+The `influx apply` command prompts you to provide a value for each environment
+reference in the template.
+You can also provide values for environment references by including an `--env-ref`
+flag with a key-value pair comprised of the environment reference key and the
+value to replace it.
+
+```sh
+influx apply -o example-org -f /path/to/template.yml \
+  --env-ref=bucket-name-1=myBucket
+  --env-ref=label-name-1=Label1 \
+  --env-ref=label-name-2=Label2
+```
+
+### Include a secret when installing a template
+Some templates use [secrets](/influxdb/v2.2/security/secrets/) in queries.
+Secret values are not included in templates.
+To define secret values when installing a template, include the `--secret` flag
+with the secret key-value pair.
+
+```sh
+# Syntax
+influx apply -o <INFLUX_ORG> -f <FILE_PATH> \
+  --secret=<secret-key>=<secret-value>
+
+# Examples
+# Define a single secret when applying a template
+influx apply -o example-org -f /path/to/template.yml \
+  --secret=FOO=BAR
+
+# Define multiple secrets when applying a template
+influx apply -o example-org -f /path/to/template.yml \
+  --secret=FOO=bar \
+  --secret=BAZ=quz
+```
+
+_To add a secret after applying a template, see [Add secrets](/influxdb/v2.2/security/secrets/manage-secrets/add/)._
diff --git a/content/influxdb/v2.2/install.md b/content/influxdb/v2.2/install.md
new file mode 100644
index 000000000..32979c34a
--- /dev/null
+++ b/content/influxdb/v2.2/install.md
@@ -0,0 +1,757 @@
+---
+title: Install InfluxDB
+description: Download, install, and set up InfluxDB OSS.
+menu: influxdb_2_2
+weight: 2
+influxdb/v2.2/tags: [install]
+---
+
+The InfluxDB {{< current-version >}} time series platform is purpose-built to collect, store,
+process and visualize metrics and events.
+Download, install, and set up InfluxDB OSS.
+
+{{< tabs-wrapper >}}
+{{% tabs %}}
+[macOS](#)
+[Linux](#)
+[Windows](#)
+[Docker](#)
+[Kubernetes](#)
+[Raspberry Pi](#)
+{{% /tabs %}}
+
+<!-------------------------------- BEGIN macOS -------------------------------->
+{{% tab-content %}}
+## Install InfluxDB v{{< current-version >}}
+
+Do one of the following:
+
+- [Use Homebrew](#use-homebrew)
+- [Manually download and install](#manually-download-and-install)
+
+{{% note %}}
+#### InfluxDB and the influx CLI are separate packages
+The InfluxDB server ([`influxd`](/influxdb/v2.2/reference/cli/influxd/)) and the
+[`influx` CLI](/influxdb/v2.2/reference/cli/influx/) are packaged and
+versioned separately.
+For information about installing the `influx` CLI, see
+[Install and use the influx CLI](/influxdb/v2.2/tools/influx-cli/).
+{{% /note %}}
+
+### Use Homebrew
+
+We recommend using [Homebrew](https://brew.sh/) to install InfluxDB v{{< current-version >}} on macOS:
+
+```sh
+brew update
+brew install influxdb
+```
+
+{{% note %}}
+Homebrew also installs `influx-cli` as a dependency.
+For information about using the `influx` CLI, see the
+[`influx` CLI reference documentation](/influxdb/v2.2/reference/cli/influx/).
+{{% /note %}}
+
+### Manually download and install
+
+To download the InfluxDB v{{< current-version >}} binaries for macOS directly,
+do the following:
+
+1. **Download the InfluxDB package.**
+    
+    <a class="btn download" href="https://dl.influxdata.com/influxdb/releases/influxdb2-{{< latest-patch >}}-darwin-amd64.tar.gz" download>InfluxDB v{{< current-version >}} (macOS)</a>
+
+
+2. **Unpackage the InfluxDB binary.**
+
+    Do one of the following:
+
+    - Double-click the downloaded package file in **Finder**.
+    - Run the following command in a macOS command prompt application such
+      **Terminal** or **[iTerm2](https://www.iterm2.com/)**:
+
+    ```sh
+    # Unpackage contents to the current working directory
+    tar zxvf ~/Downloads/influxdb2-{{< latest-patch >}}-darwin-amd64.tar.gz
+    ```
+
+3. **(Optional) Place the binary in your `$PATH`**
+
+    ```sh
+    # (Optional) Copy the influxd binary to your $PATH
+    sudo cp influxdb2-{{< latest-patch >}}-darwin-amd64/influxd /usr/local/bin/
+    ```
+
+    If you do not move the `influxd` binary into your `$PATH`, prefix the executable
+    `./` to run it in place.
+
+{{< expand-wrapper >}}
+{{% expand "<span class='req'>Recommended</span> – Verify the authenticity of downloaded binary" %}}
+
+For added security, use `gpg` to verify the signature of your download.
+(Most operating systems include the `gpg` command by default.
+If `gpg` is not available, see the [GnuPG homepage](https://gnupg.org/download/) for installation instructions.)
+
+1. Download and import InfluxData's public key:
+
+    ```
+    curl -s https://repos.influxdata.com/influxdb2.key | gpg --import -
+    ```
+
+2. Download the signature file for the release by adding `.asc` to the download URL.
+For example:
+
+    ```
+    wget https://dl.influxdata.com/influxdb/releases/influxdb2-{{< latest-patch >}}-darwin-amd64.tar.gz.asc
+    ```
+
+3. Verify the signature with `gpg --verify`:
+
+    ```
+    gpg --verify influxdb2-{{< latest-patch >}}-darwin-amd64.tar.gz.asc influxdb2-{{< latest-patch >}}-darwin-amd64.tar.gz
+    ```
+
+    The output from this command should include the following:
+
+    ```
+    gpg: Good signature from "InfluxData <support@influxdata.com>" [unknown]
+    ```
+{{% /expand %}}
+{{< /expand-wrapper >}}
+
+{{% note %}}
+Both InfluxDB 1.x and 2.x have associated `influxd` and `influx` binaries.
+If InfluxDB 1.x binaries are already in your `$PATH`, run the {{< current-version >}} binaries in place
+or rename them before putting them in your `$PATH`.
+If you rename the binaries, all references to `influxd` and `influx` in this documentation refer to your renamed binaries.
+{{% /note %}}
+
+#### Networking ports
+
+By default, InfluxDB uses TCP port `8086` for client-server communication over
+the [InfluxDB HTTP API](/influxdb/v2.2/reference/api/).
+
+### Start InfluxDB
+
+Start InfluxDB by running the `influxd` daemon:
+
+```bash
+influxd
+```
+
+{{% note %}}
+#### Run InfluxDB on macOS Catalina
+
+macOS Catalina requires downloaded binaries to be signed by registered Apple developers.
+Currently, when you first attempt to run `influxd`, macOS will prevent it from running.
+To manually authorize the `influxd` binary:
+
+1. Attempt to run `influxd`.
+2. Open **System Preferences** and click **Security & Privacy**.
+3. Under the **General** tab, there is a message about `influxd` being blocked.
+   Click **Open Anyway**.
+
+We are in the process of updating our build process to ensure released binaries are signed by InfluxData.
+{{% /note %}}
+
+{{% warn %}}
+#### "too many open files" errors
+
+After running `influxd`, you might see an error in the log output like the
+following:
+
+```sh
+too many open files
+```
+
+To resolve this error, follow the
+[recommended steps](https://unix.stackexchange.com/a/221988/471569) to increase
+file and process limits for your operating system version then restart `influxd`.
+
+{{% /warn %}}
+
+_See the [`influxd` documentation](/influxdb/v2.2/reference/cli/influxd) for information about
+available flags and options._
+
+{{% note %}}
+#### InfluxDB "phone home"
+
+By default, InfluxDB sends telemetry data back to InfluxData.
+The [InfluxData telemetry](https://www.influxdata.com/telemetry) page provides
+information about what data is collected and how it is used.
+
+To opt-out of sending telemetry data back to InfluxData, include the
+`--reporting-disabled` flag when starting `influxd`.
+
+```bash
+influxd --reporting-disabled
+```
+{{% /note %}}
+
+{{% /tab-content %}}
+<!--------------------------------- END macOS --------------------------------->
+
+<!-------------------------------- BEGIN Linux -------------------------------->
+{{% tab-content %}}
+## Download and install InfluxDB v{{< current-version >}}
+
+Do one of the following:
+
+- [Install InfluxDB as a service with systemd](#install-influxdb-as-a-service-with-systemd)
+- [Manually download and install the influxd binary](#manually-download-and-install-the-influxd-binary)
+
+{{% note %}}
+#### InfluxDB and the influx CLI are separate packages
+The InfluxDB server ([`influxd`](/influxdb/v2.2/reference/cli/influxd/)) and the
+[`influx` CLI](/influxdb/v2.2/reference/cli/influx/) are packaged and
+versioned separately.
+For information about installing the `influx` CLI, see
+[Install and use the influx CLI](/influxdb/v2.2/tools/influx-cli/).
+{{% /note %}}
+
+### Install InfluxDB as a service with systemd
+
+1.  Download and install the appropriate `.deb` or `.rpm` file using a URL from the
+    [InfluxData downloads page](https://portal.influxdata.com/downloads/)
+    with the following commands:
+
+    ```sh
+    # Ubuntu/Debian
+    wget https://dl.influxdata.com/influxdb/releases/influxdb2-{{< latest-patch >}}-xxx.deb
+    sudo dpkg -i influxdb2-{{< latest-patch >}}-xxx.deb
+
+    # Red Hat/CentOS/Fedora
+    wget https://dl.influxdata.com/influxdb/releases/influxdb2-{{< latest-patch >}}-xxx.rpm
+    sudo yum localinstall influxdb2-{{< latest-patch >}}-xxx.rpm
+    ```
+    _Use the exact filename of the download of `.rpm` package (for example, `influxdb2-{{< latest-patch >}}-amd64.rpm`)._
+
+2.  Start the InfluxDB service:
+
+    ```sh
+    sudo service influxdb start
+    ```
+
+    Installing the InfluxDB package creates a service file at `/lib/systemd/services/influxdb.service`
+    to start InfluxDB as a background service on startup.
+
+3. Restart your system and verify that the service is running correctly:
+
+    ```
+    $  sudo service influxdb status
+    ● influxdb.service - InfluxDB is an open-source, distributed, time series database
+      Loaded: loaded (/lib/systemd/system/influxdb.service; enabled; vendor preset: enable>
+      Active: active (running)
+    ```
+
+For information about where InfluxDB stores data on disk when running as a service,
+see [File system layout](/influxdb/v2.2/reference/internals/file-system-layout/?t=Linux#installed-as-a-package).
+
+To customize your InfluxDB configuration, use either
+[command line flags (arguments)](#pass-arguments-to-systemd), environment variables, or an InfluxDB configuration file.
+See InfluxDB [configuration options](/influxdb/v2.2/reference/config-options/) for more information.
+
+#### Pass arguments to systemd
+
+1. Add one or more lines like the following containing arguments for `influxd` to `/etc/default/influxdb2`:
+
+   ```sh
+   ARG1="--http-bind-address :8087"
+   ARG2="<another argument here>"
+   ```
+
+2. Edit the `/lib/systemd/system/influxdb.service` file as follows:
+
+   ```sh
+   ExecStart=/usr/bin/influxd $ARG1 $ARG2
+   ```
+
+### Manually download and install the influxd binary
+
+1. **Download the InfluxDB binary.**
+
+    Download the InfluxDB binary [from your browser](#download-from-your-browser)
+    or [from the command line](#download-from-the-command-line).
+
+    #### Download from your browser
+
+    <a class="btn download" href="https://dl.influxdata.com/influxdb/releases/influxdb2-{{< latest-patch >}}-linux-amd64.tar.gz" download >InfluxDB v{{< current-version >}} (amd64)</a>
+    <a class="btn download" href="https://dl.influxdata.com/influxdb/releases/influxdb2-{{< latest-patch >}}-linux-arm64.tar.gz" download >InfluxDB v{{< current-version >}} (arm)</a>
+
+    #### Download from the command line
+
+    ```sh
+    # amd64
+    wget https://dl.influxdata.com/influxdb/releases/influxdb2-{{< latest-patch >}}-linux-amd64.tar.gz
+
+    # arm
+    wget https://dl.influxdata.com/influxdb/releases/influxdb2-{{< latest-patch >}}-linux-arm64.tar.gz
+    ```
+
+4. **Extract the downloaded binary.**
+
+    _**Note:** The following commands are examples. Adjust the filenames, paths, and utilities if necessary._
+
+    ```sh
+    # amd64
+    tar xvzf path/to/influxdb2-{{< latest-patch >}}-linux-amd64.tar.gz
+
+    # arm
+    tar xvzf path/to/influxdb2-{{< latest-patch >}}-linux-arm64.tar.gz
+    ```
+
+3. **(Optional) Place the extracted `influxd` executable binary in your system `$PATH`.**
+
+    ```sh
+    # amd64
+    sudo cp influxdb2-{{< latest-patch >}}-linux-amd64/influxd /usr/local/bin/
+
+    # arm
+    sudo cp influxdb2-{{< latest-patch >}}-linux-arm64/influxd /usr/local/bin/
+    ```
+
+    If you do not move the `influxd` binary into your `$PATH`, prefix the executable
+    `./` to run it in place.
+
+{{< expand-wrapper >}}
+{{% expand "<span class='req'>Recommended</span> – Verify the authenticity of downloaded binary" %}}
+
+For added security, use `gpg` to verify the signature of your download.
+(Most operating systems include the `gpg` command by default.
+If `gpg` is not available, see the [GnuPG homepage](https://gnupg.org/download/) for installation instructions.)
+
+1. Download and import InfluxData's public key:
+
+    ```
+    curl -s https://repos.influxdata.com/influxdb2.key | gpg --import -
+    ```
+
+2. Download the signature file for the release by adding `.asc` to the download URL.
+   For example:
+
+    ```
+    wget https://dl.influxdata.com/influxdb/releases/influxdb2-{{< latest-patch >}}-linux-amd64.tar.gz.asc
+    ```
+
+3. Verify the signature with `gpg --verify`:
+
+    ```
+    gpg --verify influxdb2-{{< latest-patch >}}-linux-amd64.tar.gz.asc influxdb2-{{< latest-patch >}}-linux-amd64.tar.gz
+    ```
+
+    The output from this command should include the following:
+
+    ```
+    gpg: Good signature from "InfluxData <support@influxdata.com>" [unknown]
+    ```
+{{% /expand %}}
+{{< /expand-wrapper >}}
+
+## Start InfluxDB
+
+If InfluxDB was installed as a systemd service, systemd manages the `influxd` daemon and no further action is required.
+If the binary was manually downloaded and added to the system `$PATH`, start the `influxd` daemon with the following command:
+
+```bash
+influxd
+```
+
+_See the [`influxd` documentation](/influxdb/v2.2/reference/cli/influxd) for information about
+available flags and options._
+
+### Networking ports
+
+By default, InfluxDB uses TCP port `8086` for client-server communication over
+the [InfluxDB HTTP API](/influxdb/v2.2/reference/api/).
+
+{{% note %}}
+#### InfluxDB "phone home"
+
+By default, InfluxDB sends telemetry data back to InfluxData.
+The [InfluxData telemetry](https://www.influxdata.com/telemetry) page provides
+information about what data is collected and how it is used.
+
+To opt-out of sending telemetry data back to InfluxData, include the
+`--reporting-disabled` flag when starting `influxd`.
+
+```bash
+influxd --reporting-disabled
+```
+{{% /note %}}
+
+{{% /tab-content %}}
+<!--------------------------------- END Linux --------------------------------->
+
+<!------------------------------- BEGIN Windows ------------------------------->
+{{% tab-content %}}
+{{% note %}}
+#### System requirements
+- Windows 10
+- 64-bit AMD architecture
+- [Powershell](https://docs.microsoft.com/powershell/) or
+  [Windows Subsystem for Linux (WSL)](https://docs.microsoft.com/en-us/windows/wsl/)
+
+#### Command line examples
+Use **Powershell** or **WSL** to execute `influx` and `influxd` commands.
+The command line examples in this documentation use `influx` and `influxd` as if
+installed on the system `PATH`.
+If these binaries are not installed on your `PATH`, replace `influx` and `influxd`
+in the provided examples with `./influx` and `./influxd` respectively.
+{{% /note %}}
+
+## Download and install InfluxDB v{{< current-version >}}
+
+{{% note %}}
+#### InfluxDB and the influx CLI are separate packages
+The InfluxDB server ([`influxd`](/influxdb/v2.2/reference/cli/influxd/)) and the
+[`influx` CLI](/influxdb/v2.2/reference/cli/influx/) are packaged and
+versioned separately.
+For information about installing the `influx` CLI, see
+[Install and use the influx CLI](/influxdb/v2.2/tools/influx-cli/).
+{{% /note %}}
+
+<a class="btn download" href="https://dl.influxdata.com/influxdb/releases/influxdb2-{{< latest-patch >}}-windows-amd64.zip" download >InfluxDB v{{< current-version >}} (Windows)</a>
+
+Expand the downloaded archive into `C:\Program Files\InfluxData\` and rename the files if desired.
+
+```powershell
+> Expand-Archive .\influxdb2-{{< latest-patch >}}-windows-amd64.zip -DestinationPath 'C:\Program Files\InfluxData\'
+> mv 'C:\Program Files\InfluxData\influxdb2-{{< latest-patch >}}-windows-amd64' 'C:\Program Files\InfluxData\influxdb'
+```
+
+## Networking ports
+By default, InfluxDB uses TCP port `8086` for client-server communication over
+the [InfluxDB HTTP API](/influxdb/v2.2/reference/api/).
+
+## Start InfluxDB
+In **Powershell**, navigate into `C:\Program Files\InfluxData\influxdb` and start
+InfluxDB by running the `influxd` daemon:
+
+```powershell
+> cd -Path 'C:\Program Files\InfluxData\influxdb'
+> ./influxd
+```
+
+_See the [`influxd` documentation](/influxdb/v2.2/reference/cli/influxd) for information about
+available flags and options._
+
+{{% note %}}
+#### Grant network access
+When starting InfluxDB for the first time, **Windows Defender** will appear with
+the following message:
+
+> Windows Defender Firewall has blocked some features of this app.
+
+1. Select **Private networks, such as my home or work network**.
+2. Click **Allow access**.
+{{% /note %}}
+
+{{% note %}}
+#### InfluxDB "phone home"
+
+By default, InfluxDB sends telemetry data back to InfluxData.
+The [InfluxData telemetry](https://www.influxdata.com/telemetry) page provides
+information about what data is collected and how it is used.
+
+To opt-out of sending telemetry data back to InfluxData, include the
+`--reporting-disabled` flag when starting `influxd`.
+
+```bash
+./influxd --reporting-disabled
+```
+{{% /note %}}
+
+{{% /tab-content %}}
+<!-------------------------------- END Windows -------------------------------->
+
+<!-------------------------------- BEGIN Docker ------------------------------->
+{{% tab-content %}}
+## Download and run InfluxDB v{{< current-version >}}
+
+Use `docker run` to download and run the InfluxDB v{{< current-version >}} Docker image.
+Expose port `8086`, which InfluxDB uses for client-server communication over
+the [InfluxDB HTTP API](/influxdb/v2.2/reference/api/).
+
+```sh
+docker run --name influxdb -p 8086:8086 influxdb:{{< latest-patch >}}
+```
+_To run InfluxDB in [detached mode](https://docs.docker.com/engine/reference/run/#detached-vs-foreground), include the `-d` flag in the `docker run` command._
+
+## Persist data outside the InfluxDB container
+
+1. Create a new directory to store your data in and navigate into the directory.
+
+   ```sh
+   mkdir path/to/influxdb-docker-data-volume && cd $_
+   ```
+2. From within your new directory, run the InfluxDB Docker container with the `--volume` flag to
+   persist data from `/var/lib/influxdb2` _inside_ the container to the current working directory in
+   the host file system.
+
+   ```sh
+   docker run \
+       --name influxdb \
+       -p 8086:8086 \
+       --volume $PWD:/var/lib/influxdb2 \
+       influxdb:{{< latest-patch >}}
+   ```
+
+## Configure InfluxDB with Docker
+
+To mount an InfluxDB configuration file and use it from within Docker:
+
+1. [Persist data outside the InfluxDB container](#persist-data-outside-the-influxdb-container).
+
+2. Use the command below to generate the default configuration file on the host file system:
+
+    ```sh
+    docker run \
+      --rm influxdb:{{< latest-patch >}} \
+      influxd print-config > config.yml
+    ```
+
+3. Modify the default configuration, which will now be available under `$PWD`.
+
+4. Start the InfluxDB container:
+
+    ```sh
+    docker run -p 8086:8086 \
+      -v $PWD/config.yml:/etc/influxdb2/config.yml \
+      influxdb:{{< latest-patch >}}
+    ```
+
+(Find more about configuring InfluxDB [here](https://docs.influxdata.com/influxdb/v2.2/reference/config-options/).)
+
+## Open a shell in the InfluxDB container
+
+To use the `influx` command line interface, open a shell in the `influxdb` Docker container:
+
+```sh
+docker exec -it influxdb /bin/bash
+```
+
+{{% note %}}
+#### InfluxDB "phone home"
+
+By default, InfluxDB sends telemetry data back to InfluxData.
+The [InfluxData telemetry](https://www.influxdata.com/telemetry) page provides
+information about what data is collected and how it is used.
+
+To opt-out of sending telemetry data back to InfluxData, include the
+`--reporting-disabled` flag when starting the InfluxDB container.
+
+```sh
+docker run -p 8086:8086 influxdb:{{< latest-patch >}} --reporting-disabled
+```
+{{% /note %}}
+
+{{% /tab-content %}}
+<!--------------------------------- END Docker -------------------------------->
+
+<!-------------------------------- BEGIN kubernetes---------------------------->
+{{% tab-content %}}
+
+## Install InfluxDB in a Kubernetes cluster
+
+The instructions below use **minikube** or **kind**, but the steps should be similar in any Kubernetes cluster.
+InfluxData also makes [Helm charts](https://github.com/influxdata/helm-charts) available.
+
+1. Install [minikube](https://kubernetes.io/docs/tasks/tools/install-minikube/) or
+   [kind](https://kind.sigs.k8s.io/docs/user/quick-start/#installation).
+
+2. Start a local cluster:
+
+    ```sh
+    # with minikube
+    minikube start
+
+    # with kind
+    kind create cluster
+    ```
+
+3. Apply the [sample InfluxDB configuration](https://github.com/influxdata/docs-v2/blob/master/static/downloads/influxdb-k8-minikube.yaml) by running:
+
+    ```sh
+    kubectl apply -f https://raw.githubusercontent.com/influxdata/docs-v2/master/static/downloads/influxdb-k8-minikube.yaml
+    ```
+
+    This creates an `influxdb` Namespace, Service, and StatefulSet.
+    A PersistentVolumeClaim is also created to store data written to InfluxDB.
+
+    **Important**: Always inspect YAML manifests before running `kubectl apply -f <url>`!
+
+4. Ensure the Pod is running:
+
+    ```sh
+    kubectl get pods -n influxdb
+    ```
+
+5. Ensure the Service is available:
+
+    ```sh
+    kubectl describe service -n influxdb influxdb
+    ```
+
+    You should see an IP address after `Endpoints` in the command's output.
+
+6. Forward port 8086 from inside the cluster to localhost:
+
+    ```sh
+    kubectl port-forward -n influxdb service/influxdb 8086:8086
+    ```
+
+{{% /tab-content %}}
+<!--------------------------------- END kubernetes ---------------------------->
+<!--------------------------------- BEGIN Rasberry Pi ------------------------->
+{{% tab-content %}}
+
+## Install InfluxDB v{{< current-version >}} on Raspberry Pi
+
+{{% note %}}
+#### Requirements
+
+To run InfluxDB on Raspberry Pi, you need:
+
+- a Raspberry Pi 4+ or 400
+- a 64-bit operating system.
+  We recommend installing a [64-bit version of Ubuntu](https://ubuntu.com/download/raspberry-pi)
+  of Ubuntu Desktop or Ubuntu Server compatible with 64-bit Raspberry Pi.
+{{% /note %}}
+
+### Install Linux binaries
+
+Follow the [Linux installation instructions](/influxdb/v2.2/install/?t=Linux)
+to install InfluxDB on a Raspberry Pi.
+
+### Monitor your Raspberry Pi
+Use the [InfluxDB Raspberry Pi template](/influxdb/cloud/monitor-alert/templates/infrastructure/raspberry-pi/)
+to easily configure collecting and visualizing system metrics for the Raspberry Pi.
+
+#### Monitor 32-bit Raspberry Pi systems
+If you have a 32-bit Raspberry Pi, [use Telegraf](/{{< latest "telegraf" >}}/)
+to collect and send data to:
+
+- [InfluxDB OSS](/influxdb/v2.2/), running on a 64-bit system
+- InfluxDB Cloud with a [**Free Tier**](/influxdb/cloud/account-management/pricing-plans/#free-plan) account
+- InfluxDB Cloud with a paid [**Usage-Based**](/influxdb/cloud/account-management/pricing-plans/#usage-based-plan) account with relaxed resource restrictions.
+
+{{% /tab-content %}}
+<!--------------------------------- END Rasberry Pi --------------------------->
+
+{{< /tabs-wrapper >}}
+
+## Download and install the influx CLI
+The [`influx` CLI](/influxdb/v2.2/reference/cli/influx/) lets you manage InfluxDB
+from your command line.
+
+<a class="btn" href="/influxdb/v2.2/tools/influx-cli/" target="_blank">Download and install the influx CLI</a>
+
+## Set up InfluxDB
+
+The initial setup process for InfluxDB walks through creating a default organization,
+user, bucket, and Operator API token.
+The setup process is available in both the InfluxDB user interface (UI) and in
+the `influx` command line interface (CLI).
+
+{{% note %}}
+#### Operator token permissions
+The **Operator token** created in the InfluxDB setup process has
+**full read and write access to all organizations** in the database.
+To prevent accidental interactions across organizations, we recommend
+[creating an All-Access token](/influxdb/v2.2/security/tokens/create-token/)
+for each organization and using those to manage InfluxDB.
+{{% /note %}}
+
+{{< tabs-wrapper >}}
+{{% tabs %}}
+[UI Setup](#)
+[CLI Setup](#)
+{{% /tabs %}}
+
+<!------------------------------- BEGIN UI Setup ------------------------------>
+{{% tab-content %}}
+### Set up InfluxDB through the UI
+
+1. With InfluxDB running, visit [localhost:8086](http://localhost:8086).
+2. Click **Get Started**
+
+#### Set up your initial user
+
+1. Enter a **Username** for your initial user.
+2. Enter a **Password** and **Confirm Password** for your user.
+3. Enter your initial **Organization Name**.
+4. Enter your initial **Bucket Name**.
+5. Click **Continue**.
+
+InfluxDB is now initialized with a primary user, organization, and bucket.
+You are ready to [write or collect data](/influxdb/v2.2/write-data).
+
+### (Optional) Set up and use the influx CLI
+
+To avoid having to pass your InfluxDB
+[API token](/influxdb/v2.2/security/tokens/) with each `influx` command, set up a configuration profile to store your credentials. To do this, complete the following steps:
+
+1. In a terminal, run the following command:
+
+    ```sh
+    # Set up a configuration profile
+    influx config create -n default \
+      -u http://localhost:8086 \
+      -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 the specified InfluxDB instance.
+    For more detail, see [`influx config`](/influxdb/v2.2/reference/cli/influx/config/).
+
+2. Learn `influx` CLI commands. To see all available `influx` commands, type
+   `influx -h` or check out [influx - InfluxDB command line interface](/influxdb/v2.2/reference/cli/influx/).
+
+{{% /tab-content %}}
+<!-------------------------------- END UI Setup ------------------------------->
+
+<!------------------------------ BEGIN CLI Setup ------------------------------>
+{{% tab-content %}}
+### Set up InfluxDB through the influx CLI
+
+Begin the InfluxDB setup process via the [`influx` CLI](/influxdb/v2.2/reference/cli/influx/) by running:
+
+```bash
+influx setup
+```
+
+1. Enter a **primary username**.
+2. Enter a **password** for your user.
+3. **Confirm your password** by entering it again.
+4. Enter a name for your **primary organization**.
+5. Enter a name for your **primary bucket**.
+6. Enter a **retention period** for your primary bucket—valid units are
+   nanoseconds (`ns`), microseconds (`us` or `µs`), milliseconds (`ms`),
+   seconds (`s`), minutes (`m`), hours (`h`), days (`d`), and weeks (`w`).
+   Enter nothing for an infinite retention period.
+7. Confirm the details for your primary user, organization, and bucket.
+
+InfluxDB is now initialized with a primary user, organization, bucket, and API token.
+InfluxDB also creates a configuration profile for you so that you don't have to
+add your InfluxDB host, organization, and token to every command.
+To view that config profile, use the [`influx config list`](/influxdb/v2.2/reference/cli/influx/config) command.
+
+To continue to use InfluxDB via the CLI, you need the API token created during setup.
+To view the token, log into the UI with the credentials created above.
+(For instructions, see [View tokens in the InfluxDB UI](/influxdb/v2.2/security/tokens/view-tokens/#view-tokens-in-the-influxdb-ui).)
+
+You are ready to [write or collect data](/influxdb/v2.2/write-data).
+
+{{% note %}}
+To automate the setup process, use [flags](/influxdb/v2.2/reference/cli/influx/setup/#flags)
+to provide the required information.
+{{% /note %}}
+
+{{% /tab-content %}}
+<!------------------------------- END UI Setup -------------------------------->
+{{< /tabs-wrapper >}}
+
+After you’ve installed InfluxDB, you’re ready to [get started working with your data in InfluxDB](/influxdb/v2.2/get-started/).
diff --git a/content/influxdb/v2.2/migrate-data/_index.md b/content/influxdb/v2.2/migrate-data/_index.md
new file mode 100644
index 000000000..601d644de
--- /dev/null
+++ b/content/influxdb/v2.2/migrate-data/_index.md
@@ -0,0 +1,15 @@
+---
+title: Migrate data to InfluxDB
+description: >
+  Migrate data to InfluxDB from other InfluxDB instances including by InfluxDB OSS
+  and InfluxDB Cloud.
+menu:
+  influxdb_2_2:
+    name: Migrate data
+weight: 9
+---
+
+Migrate data to InfluxDB from other InfluxDB instances including by InfluxDB OSS
+and InfluxDB Cloud.
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/migrate-data/migrate-cloud-to-oss.md b/content/influxdb/v2.2/migrate-data/migrate-cloud-to-oss.md
new file mode 100644
index 000000000..03513a156
--- /dev/null
+++ b/content/influxdb/v2.2/migrate-data/migrate-cloud-to-oss.md
@@ -0,0 +1,372 @@
+---
+title: Migrate data from InfluxDB Cloud to InfluxDB OSS
+description: >
+  To migrate data from InfluxDB Cloud to InfluxDB OSS, query the data from
+  InfluxDB Cloud in time-based batches and write the data to InfluxDB OSS.
+menu:
+  influxdb_2_2:
+    name: Migrate from Cloud to OSS
+    parent: Migrate data
+weight: 102
+---
+
+To migrate data from InfluxDB Cloud to InfluxDB OSS, query the data
+from InfluxDB Cloud and write the data to InfluxDB OSS.
+Because full data migrations will likely exceed your organization's limits and
+adjustable quotas, migrate your data in batches.
+
+The following guide provides instructions for setting up an InfluxDB OSS task
+that queries data from an InfluxDB Cloud bucket in time-based batches and writes
+each batch to an InfluxDB OSS bucket.
+
+{{% cloud %}}
+All queries against data in InfluxDB Cloud are subject to your organization's
+[rate limits and adjustable quotas](/influxdb/cloud/account-management/limits/).
+{{% /cloud %}}
+
+- [Set up the migration](#set-up-the-migration)
+- [Migration task](#migration-task)
+  - [Configure the migration](#configure-the-migration)
+  - [Migration Flux script](#migration-flux-script)
+  - [Configuration help](#configuration-help)
+- [Monitor the migration progress](#monitor-the-migration-progress)
+- [Troubleshoot migration task failures](#troubleshoot-migration-task-failures)
+
+## Set up the migration
+1.  [Install and set up InfluxDB OSS](/influxdb/{{< current-version-link >}}/install/).
+
+2.  **In InfluxDB Cloud**, [create an API token](/influxdb/cloud/security/tokens/create-token/)
+        with **read access** to the bucket you want to migrate.
+
+3.  **In InfluxDB OSS**:
+    1.  Add your **InfluxDB Cloud API token** as a secret using the key,
+        `INFLUXDB_CLOUD_TOKEN`.
+        _See [Add secrets](/influxdb/{{< current-version-link >}}/security/secrets/add/) for more information._
+    2.  [Create a bucket](/influxdb/{{< current-version-link >}}/organizations/buckets/create-bucket/)
+        **to migrate data to**.
+    3.  [Create a bucket](/influxdb/{{< current-version-link >}}/organizations/buckets/create-bucket/)
+        **to store temporary migration metadata**.
+    4.  [Create a new task](/influxdb/{{< current-version-link >}}/process-data/manage-tasks/create-task/)
+        using the provided [migration task](#migration-task).
+        Update the necessary [migration configuration options](#configure-the-migration).
+    5.  _(Optional)_ Set up [migration monitoring](#monitor-the-migration-progress).
+    6.  Save the task.
+
+        {{% note %}}
+Newly-created tasks are enabled by default, so the data migration begins when you save the task.
+        {{% /note %}}
+
+**After the migration is complete**, each subsequent migration task execution
+will fail with the following error:
+
+```
+error exhausting result iterator: error calling function "die" @41:9-41:86:
+Batch range is beyond the migration range. Migration is complete.
+```
+
+## Migration task
+
+### Configure the migration
+1.  Specify how often you want the task to run using the `task.every` option.
+    _See [Determine your task interval](#determine-your-task-interval)._
+
+2.  Define the following properties in the `migration`
+    [record](/{{< latest "flux" >}}/data-types/composite/record/):
+
+    ##### migration
+    - **start**: Earliest time to include in the migration.
+      _See [Determine your migration start time](#determine-your-migration-start-time)._
+    - **stop**: Latest time to include in the migration.
+    - **batchInterval**: Duration of each time-based batch.
+      _See [Determine your batch interval](#determine-your-batch-interval)._
+    - **batchBucket**: InfluxDB OSS bucket to store migration batch metadata in.
+    - **sourceHost**: [InfluxDB Cloud region URL](/influxdb/cloud/reference/regions)
+      to migrate data from.
+    - **sourceOrg**: InfluxDB Cloud organization to migrate data from.
+    - **sourceToken**: InfluxDB Cloud API token. To keep the API token secure, store
+      it as a secret in InfluxDB OSS.
+    - **sourceBucket**: InfluxDB Cloud bucket to migrate data from.
+    - **destinationBucket**: InfluxDB OSS bucket to migrate data to.
+
+### Migration Flux script
+
+```js
+import "array"
+import "experimental"
+import "influxdata/influxdb/secrets"
+
+// Configure the task
+option task = {every: 5m, name: "Migrate data from InfluxDB Cloud"}
+
+// Configure the migration
+migration = {
+    start: 2022-01-01T00:00:00Z,
+    stop: 2022-02-01T00:00:00Z,
+    batchInterval: 1h,
+    batchBucket: "migration",
+    sourceHost: "https://cloud2.influxdata.com",
+    sourceOrg: "example-cloud-org",
+    sourceToken: secrets.get(key: "INFLUXDB_CLOUD_TOKEN"),
+    sourceBucket: "example-cloud-bucket",
+    destinationBucket: "example-oss-bucket",
+}
+
+// batchRange dynamically returns a record with start and stop properties for
+// the current batch. It queries migration metadata stored in the
+// `migration.batchBucket` to determine the stop time of the previous batch.
+// It uses the previous stop time as the new start time for the current batch
+// and adds the `migration.batchInterval` to determine the current batch stop time.
+batchRange = () => {
+    _lastBatchStop =
+        (from(bucket: migration.batchBucket)
+            |> range(start: migration.start)
+            |> filter(fn: (r) => r._field == "batch_stop")
+            |> filter(fn: (r) => r.srcOrg == migration.sourceOrg)
+            |> filter(fn: (r) => r.srcBucket == migration.sourceBucket)
+            |> last()
+            |> findRecord(fn: (key) => true, idx: 0))._value
+    _batchStart =
+        if exists _lastBatchStop then
+            time(v: _lastBatchStop)
+        else
+            migration.start
+
+    return {start: _batchStart, stop: experimental.addDuration(d: migration.batchInterval, to: _batchStart)}
+}
+
+// Define a static record with batch start and stop time properties
+batch = {start: batchRange().start, stop: batchRange().stop}
+
+// Check to see if the current batch start time is beyond the migration.stop
+// time and exit with an error if it is.
+finished =
+    if batch.start >= migration.stop then
+        die(msg: "Batch range is beyond the migration range. Migration is complete.")
+    else
+        "Migration in progress"
+
+// Query all data from the specified source bucket within the batch-defined time
+// range. To limit migrated data by measurement, tag, or field, add a `filter()`
+// function after `range()` with the appropriate predicate fn.
+data = () =>
+    from(host: migration.sourceHost, org: migration.sourceOrg, token: migration.sourceToken, bucket: migration.sourceBucket)
+        |> range(start: batch.start, stop: batch.stop)
+
+// rowCount is a stream of tables that contains the number of rows returned in
+// the batch and is used to generate batch metadata.
+rowCount =
+    data()
+        |> group(columns: ["_start", "_stop"])
+        |> count()
+
+// emptyRange is a stream of tables that acts as filler data if the batch is
+// empty. This is used to generate batch metadata for empty batches and is
+// necessary to correctly increment the time range for the next batch.
+emptyRange = array.from(rows: [{_start: batch.start, _stop: batch.stop, _value: 0}])
+
+// metadata returns a stream of tables representing batch metadata.
+metadata = () => {
+    _input =
+        if exists (rowCount |> findRecord(fn: (key) => true, idx: 0))._value then
+            rowCount
+        else
+            emptyRange
+
+    return
+        _input
+            |> map(
+                fn: (r) =>
+                    ({
+                        _time: now(),
+                        _measurement: "batches",
+                        srcOrg: migration.sourceOrg,
+                        srcBucket: migration.sourceBucket,
+                        dstBucket: migration.destinationBucket,
+                        batch_start: string(v: batch.start),
+                        batch_stop: string(v: batch.stop),
+                        rows: r._value,
+                        percent_complete:
+                            float(v: int(v: r._stop) - int(v: migration.start)) / float(
+                                    v: int(v: migration.stop) - int(v: migration.start),
+                                ) * 100.0,
+                    }),
+            )
+            |> group(columns: ["_measurement", "srcOrg", "srcBucket", "dstBucket"])
+}
+
+// Write the queried data to the specified InfluxDB OSS bucket.
+data()
+    |> to(bucket: migration.destinationBucket)
+
+// Generate and store batch metadata in the migration.batchBucket.
+metadata()
+    |> experimental.to(bucket: migration.batchBucket)
+```
+
+### Configuration help
+
+{{< expand-wrapper >}}
+
+<!----------------------- BEGIN Determine task interval ----------------------->
+{{% expand "Determine your task interval" %}}
+
+The task interval determines how often the migration task runs and is defined by
+the [`task.every` option](/influxdb/v2.2/process-data/task-options/#every).
+InfluxDB Cloud rate limits and quotas reset every five minutes, so
+**we recommend a `5m` task interval**.
+
+You can do shorter task intervals and execute the migration task more often,
+but you need to balance the task interval with your [batch interval](#determine-your-batch-interval) 
+and the amount of data returned in each batch.
+If the total amount of data queried in each five-minute interval exceeds your
+InfluxDB Cloud organization's [rate limits and quotas](/influxdb/cloud/account-management/limits/),
+the batch will fail until rate limits and quotas reset.
+
+{{% /expand %}}
+<!------------------------ END Determine task interval ------------------------>
+
+<!---------------------- BEGIN Determine migration start ---------------------->
+{{% expand "Determine your migration start time" %}}
+
+The `migration.start` time should be at or near the same time as the earliest
+data point you want to migrate.
+All migration batches are determined using the `migration.start` time and
+`migration.batchInterval` settings.
+
+To find time of the earliest point in your bucket, run the following query:
+
+```js
+from(bucket: "example-cloud-bucket")
+    |> range(start: 0)
+    |> group()
+    |> first()
+    |> keep(columns: ["_time"])
+```
+
+{{% /expand %}}
+<!----------------------- END Determine migration start ----------------------->
+
+<!----------------------- BEGIN Determine batch interval ---------------------->
+{{% expand "Determine your batch interval" %}}
+
+The `migration.batchInterval` setting controls the time range queried by each batch.
+The "density" of the data in your InfluxDB Cloud bucket and your InfluxDB Cloud
+organization's [rate limits and quotas](/influxdb/cloud/account-management/limits/)
+determine what your batch interval should be.
+
+For example, if you're migrating data collected from hundreds of sensors with
+points recorded every second, your batch interval will need to be shorter.
+If you're migrating data collected from five sensors with points recorded every
+minute, your batch interval can be longer.
+It all depends on how much data gets returned in a single batch.
+
+If points occur at regular intervals, you can get a fairly accurate estimate of
+how much data will be returned in a given time range by using the `/api/v2/query`
+endpoint to execute a query for the time range duration and then measuring the
+size of the response body.
+
+The following `curl` command queries an InfluxDB Cloud bucket for the last day
+and returns the size of the response body in bytes.
+You can customize the range duration to match your specific use case and
+data density.
+
+```sh
+INFLUXDB_CLOUD_ORG=<your_influxdb_cloud_org>
+INFLUXDB_CLOUD_TOKEN=<your_influxdb_cloud_token>
+INFLUXDB_CLOUD_BUCKET=<your_influxdb_cloud_bucket>
+
+curl -so /dev/null --request POST \
+  https://cloud2.influxdata.com/api/v2/query?org=$INFLUXDB_CLOUD_ORG  \
+  --header "Authorization: Token $INFLUXDB_CLOUD_TOKEN" \
+  --header "Accept: application/csv" \
+  --header "Content-type: application/vnd.flux" \
+  --data "from(bucket:\"$INFLUXDB_CLOUD_BUCKET\") |> range(start: -1d, stop: now())" \
+  --write-out '%{size_download}'
+```
+
+{{% note %}}
+You can also use other HTTP API tools like [Postman](https://www.postman.com/)
+that provide the size of the response body.
+{{% /note %}}
+
+Divide the output of this command by 1000000 to convert it to megabytes (MB).
+
+```
+batchInterval = (read-rate-limit-mb / response-body-size-mb) * range-duration
+```
+
+For example, if the response body of your query that returns data from one day 
+is 8 MB and you're using the InfluxDB Cloud Free Plan with a read limit of
+300 MB per five minutes:
+
+```js
+batchInterval = (300 / 8) * 1d
+// batchInterval = 37d
+```
+
+You could query 37 days of data before hitting your read limit, but this is just an estimate.
+We recommend setting the `batchInterval` slightly lower than the calculated interval
+to allow for variation between batches.
+So in this example, **it would be best to set your `batchInterval` to `35d`**.
+
+##### Important things to note
+- This assumes no other queries are running in your InfluxDB Cloud organization.
+- You should also consider your network speeds and whether a batch can be fully
+  downloaded within the [task interval](#determine-your-task-interval).
+
+{{% /expand %}}
+<!------------------------ END Determine batch interval ----------------------->
+{{< /expand-wrapper >}}
+
+## Monitor the migration progress
+The [InfluxDB Cloud Migration Community template](https://github.com/influxdata/community-templates/tree/master/influxdb-cloud-oss-migration/)
+installs the migration task outlined in this guide as well as a dashboard
+for monitoring running data migrations.
+
+{{< img-hd src="/img/influxdb/2-1-migration-dashboard.png" alt="InfluxDB Cloud migration dashboard" />}}
+
+<a class="btn" href="https://github.com/influxdata/community-templates/tree/master/influxdb-cloud-oss-migration/#quick-install">Install the InfluxDB Cloud Migration template</a>
+
+## Troubleshoot migration task failures
+If the migration task fails, [view your task logs](/influxdb/v2.2/process-data/manage-tasks/task-run-history/)
+to identify the specific error. Below are common causes of migration task failures.
+
+- [Exceeded rate limits](#exceeded-rate-limits)
+- [Invalid API token](#invalid-api-token)
+- [Query timeout](#query-timeout)
+
+### Exceeded rate limits
+If your data migration causes you to exceed your InfluxDB Cloud organization's
+limits and quotas, the task will return an error similar to:
+
+```
+too many requests
+```
+
+**Possible solutions**:
+- Update the `migration.batchInterval` setting in your migration task to use
+  a smaller interval. Each batch will then query less data.
+
+### Invalid API token
+If the API token you add as the `INFLUXDB_CLOUD_SECRET` doesn't have read access to
+your InfluxDB Cloud bucket, the task will return an error similar to:
+
+```
+unauthorized access
+```
+
+**Possible solutions**:
+- Ensure the API token has read access to your InfluxDB Cloud bucket.
+- Generate a new InfluxDB Cloud API token with read access to the bucket you
+  want to migrate. Then, update the `INFLUXDB_CLOUD_TOKEN` secret in your
+  InfluxDB OSS instance with the new token.
+
+### Query timeout
+The InfluxDB Cloud query timeout is 90 seconds. If it takes longer than this to
+return the data from the batch interval, the query will time out and the
+task will fail.
+
+**Possible solutions**:
+- Update the `migration.batchInterval` setting in your migration task to use
+  a smaller interval. Each batch will then query less data and take less time
+  to return results.
diff --git a/content/influxdb/v2.2/migrate-data/migrate-oss.md b/content/influxdb/v2.2/migrate-data/migrate-oss.md
new file mode 100644
index 000000000..4b97db5fc
--- /dev/null
+++ b/content/influxdb/v2.2/migrate-data/migrate-oss.md
@@ -0,0 +1,64 @@
+---
+title: Migrate data from InfluxDB OSS to other InfluxDB instances
+description: >
+  To migrate data from an InfluxDB OSS bucket to another InfluxDB OSS or InfluxDB
+  Cloud bucket, export your data as line protocol and write it to your other
+  InfluxDB bucket.
+menu:
+  influxdb_2_2:
+    name: Migrate data from OSS
+    parent: Migrate data
+weight: 101
+---
+
+To migrate data from an InfluxDB OSS bucket to another InfluxDB OSS or InfluxDB
+Cloud bucket, export your data as line protocol and write it to your other
+InfluxDB bucket.
+
+{{% cloud %}}
+#### InfluxDB Cloud write limits
+If migrating data from InfluxDB OSS to InfluxDB Cloud, you are subject to your
+[InfluxDB Cloud organization's rate limits and adjustable quotas](/influxdb/cloud/account-management/limits/).
+Consider exporting your data in time-based batches to limit the file size
+of exported line protocol to match your InfluxDB Cloud organization's limits.
+{{% /cloud %}}
+
+1.  [Find the InfluxDB OSS bucket ID](/influxdb/{{< current-version-link >}}/organizations/buckets/view-buckets/)
+    that contains data you want to migrate.
+2.  Use the `influxd inspect export-lp` command to export data in your bucket as
+    [line protocol](/influxdb/v2.2/reference/syntax/line-protocol/).
+    Provide the following:
+
+    - **bucket ID**: ({{< req >}}) ID of the bucket to migrate.
+    - **engine path**: ({{< req >}}) Path to the TSM storage files on disk.
+      The default engine path [depends on your operating system](/influxdb/{{< current-version-link >}}/reference/internals/file-system-layout/#file-system-layout),
+      If using a [custom engine-path](/influxdb/{{< current-version-link >}}/reference/config-options/#engine-path)
+      provide your custom path.
+    - **output path**: ({{< req >}}) File path to output line protocol to.
+    - **start time**: Earliest time to export.
+    - **end time**: Latest time to export.
+    - **measurement**: Export a specific measurement. By default, the command
+      exports all measurements.
+    - **compression**: ({{< req text="Recommended" color="magenta" >}})
+      Use Gzip compression to compress the output line protocol file.
+
+    ```sh
+    influxd inspect export-lp \
+      --bucket-id 12ab34cd56ef \
+      --engine-path ~/.influxdbv2/engine \
+      --output-path path/to/export.lp
+      --start 2022-01-01T00:00:00Z \
+      --end 2022-01-31T23:59:59Z \
+      --compress
+    ```
+
+3.  Write the exported line protocol to your InfluxDB OSS or InfluxDB Cloud instance.
+    
+    Do any of the following:
+
+    - Write line protocol in the **InfluxDB UI**:
+        - [InfluxDB Cloud UI](/influxdb/cloud/write-data/no-code/load-data/#load-csv-or-line-protocol-in-ui)
+        - [InfluxDB OSS {{< current-version >}} UI](/influxdb/{{< current-version-link >}}/write-data/no-code/load-data/#load-csv-or-line-protocol-in-ui)
+    - [Write line protocol using the `influx write` command](/influxdb/{{< current-version-link >}}/reference/cli/influx/write/)
+    - [Write line protocol using the InfluxDB API](/influxdb/{{< current-version-link >}}/write-data/developer-tools/api/)
+    - [Bulk ingest data (InfluxDB Cloud)](/influxdb/cloud/write-data/bulk-ingest-cloud/)
diff --git a/content/influxdb/v2.2/monitor-alert/_index.md b/content/influxdb/v2.2/monitor-alert/_index.md
new file mode 100644
index 000000000..cf3af35e6
--- /dev/null
+++ b/content/influxdb/v2.2/monitor-alert/_index.md
@@ -0,0 +1,38 @@
+---
+title: Monitor data and send alerts
+seotitle: Monitor data and send alerts
+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_2:
+    name: Monitor & alert
+weight: 7
+influxdb/v2.2/tags: [monitor, alert, checks, notification, endpoints]
+---
+
+Monitor your time series data and send alerts by creating checks, notification
+rules, and notification endpoints. Or use [community templates to monitor](/influxdb/v2.2/monitor-alert/templates/) supported environments.
+
+## Overview
+
+1.  A [check](/influxdb/v2.2/reference/glossary/#check) in InfluxDB queries data and assigns a status with a `_level` based on specific conditions.
+2.  InfluxDB stores the output of a check in the `statuses` measurement in the `_monitoring` system bucket.
+3.  [Notification rules](/influxdb/v2.2/reference/glossary/#notification-rule) check data in the `statuses`
+    measurement and, based on conditions set in the notification rule, send a message
+    to a [notification endpoint](/influxdb/v2.2/reference/glossary/#notification-endpoint).
+4.  InfluxDB stores notifications in the `notifications` measurement in the `_monitoring` system bucket.
+
+## Create an alert
+
+To get started, do the following:
+
+1.  [Create checks](/influxdb/v2.2/monitor-alert/checks/create/) to monitor data and assign a status.
+2.  [Add notification endpoints](/influxdb/v2.2/monitor-alert/notification-endpoints/create/)
+    to send notifications to third parties.
+3.  [Create notification rules](/influxdb/v2.2/monitor-alert/notification-rules/create) to check
+    statuses and send notifications to your notifications endpoints.
+
+## Manage your monitoring and alerting pipeline
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/monitor-alert/checks/_index.md b/content/influxdb/v2.2/monitor-alert/checks/_index.md
new file mode 100644
index 000000000..c53fb3ed2
--- /dev/null
+++ b/content/influxdb/v2.2/monitor-alert/checks/_index.md
@@ -0,0 +1,19 @@
+---
+title: Manage checks
+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_2:
+    parent: Monitor & alert
+weight: 101
+influxdb/v2.2/tags: [monitor, checks, notifications, alert]
+related:
+  - /influxdb/v2.2/monitor-alert/notification-rules/
+  - /influxdb/v2.2/monitor-alert/notification-endpoints/
+---
+
+Checks in InfluxDB query data and apply a status or level to each data point based on specified conditions.
+Learn how to create and manage checks:
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/monitor-alert/checks/create.md b/content/influxdb/v2.2/monitor-alert/checks/create.md
new file mode 100644
index 000000000..93a84b2f1
--- /dev/null
+++ b/content/influxdb/v2.2/monitor-alert/checks/create.md
@@ -0,0 +1,150 @@
+---
+title: Create checks
+seotitle: Create monitoring checks in InfluxDB
+description: >
+  Create a check in the InfluxDB UI.
+menu:
+  influxdb_2_2:
+    parent: Manage checks
+weight: 201
+related:
+  - /influxdb/v2.2/monitor-alert/notification-rules/
+  - /influxdb/v2.2/monitor-alert/notification-endpoints/
+---
+
+Create a check in the InfluxDB user interface (UI).
+Checks query data and apply a status to each point based on specified conditions.
+
+## Parts of a check
+A check consists of two parts – a query and check configuration.
+
+#### Check query
+- Specifies the dataset to monitor.
+- May include tags to narrow results.
+
+#### Check configuration
+- Defines check properties, including the check interval and status message.
+- Evaluates specified conditions and applies a status (if applicable) to each data point:
+    - `crit`
+    - `warn`
+    - `info`
+    - `ok`
+- Stores status in the `_level` column.
+
+## Check types
+There are two types of checks:
+
+- [threshold](#threshold-check)
+- [deadman](#deadman-check)
+
+#### Threshold check
+A threshold check assigns a status based on a value being above, below,
+inside, or outside of defined thresholds.
+
+#### Deadman check
+A deadman check assigns a status to data when a series or group doesn't report
+in a specified amount of time.
+
+## Create a check
+1. In the navigation menu on the left, select **Alerts > Alerts**.
+
+    {{< nav-icon "alerts" >}}
+
+2.  Click **{{< caps >}}{{< icon "plus" >}} Create{{< /caps >}}** 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, and then do the following:
+    - [Configure the check query](#configure-the-check-query)
+    - [Configure the check](#configure-the-check)
+4. _(Optional)_ In the **Name this check** field at the top, enter a unique name for the check.
+
+#### Configure the check query
+1.  Select the **bucket**, **measurement**, **field** and **tag sets** to query.
+2.  If creating a threshold check, select an **aggregate function**.
+    Aggregate functions aggregate data between the specified check intervals and
+    return a single value for the check to process.
+
+    In the **Aggregate functions** column, select an interval from the interval drop-down list
+    (for example, "Every 5 minutes") and an aggregate function from the list of functions.
+3. Click **{{< caps >}}Submit{{< /caps >}}** to run the query and preview the results.
+   To see the raw query results, click the **View Raw Data {{< icon "toggle" >}}** toggle.
+
+#### Configure the check
+1.  Click **{{< caps >}}2. Configure Check{{< /caps >}}** near the top of the window.
+2.  In the **{{< caps >}}Properties{{< /caps >}}** column, configure the following:
+
+    ##### Schedule Every
+    Select the interval to run the check (for example, "Every 5 minutes").
+    This interval matches the aggregate function interval for the check query.
+    _Changing the interval here will update the aggregate function interval._
+
+    ##### Offset
+    Delay the execution of a task to account for any late data.
+    Offset queries do not change the queried time range.
+
+    {{% note %}}Your offset must be shorter than your [check interval](#schedule-every).
+    {{% /note %}}
+
+    ##### Tags
+    Add custom tags to the query output.
+    Each custom tag appends a new column to each row in the query output.
+    The column label is the tag key and the column value is the tag value.
+
+    Use custom tags to associate additional metadata with the check.
+    Common metadata tags across different checks lets you easily group and organize checks.
+    You can also use custom tags in [notification rules](/influxdb/v2.2/monitor-alert/notification-rules/create/).
+
+3.  In the **{{< caps >}}Status Message Template{{< /caps >}}** column, enter
+    the status message template for the check.
+    Use [Flux string interpolation](/{{< latest "flux" >}}/data-types/basic/string/#interpolate-strings)
+    to populate the message with data from the query.
+
+    Check data is represented as a record, `r`.
+    Access specific column values using dot notation: `r.columnName`.
+
+    Use data from the following columns:
+
+    - columns included in the query output
+    - [custom tags](#tags) added to the query output
+    - `_check_id`
+    - `_check_name`
+    - `_level`
+    - `_source_measurement`
+    - `_type`
+
+    ###### Example status message template
+    ```
+    From ${r._check_name}:
+    ${r._field} is ${r._level}.
+    Its value is ${string(v: r.field_name)}.
+    ```
+
+    When a check generates a status, it stores the message in the `_message` column.
+
+4.  Define check conditions that assign statuses to points.
+    Condition options depend on your check type.
+
+    ##### Configure a threshold check
+    1.  In the **{{< caps >}}Thresholds{{< /caps >}}** column, click the status name (CRIT, WARN, INFO, or OK)
+        to define conditions for that specific status.
+    2.  From the **When value** drop-down list, select a threshold: is above, is below,
+        is inside of, is outside of.
+    3.  Enter a value or values for the threshold.
+        You can also use the threshold sliders in the data visualization to define threshold values.
+
+    ##### Configure a deadman check
+    1.  In the **{{< caps >}}Deadman{{< /caps >}}** column, enter a duration for the deadman check in the **for** field.
+        For example, `90s`, `5m`, `2h30m`, etc.
+    2.  Use the **set status to** drop-down list to select a status to set on a dead series.
+    3.  In the **And stop checking after** field, enter the time to stop monitoring the series.
+        For example, `30m`, `2h`, `3h15m`, etc.
+
+5. Click the green **{{< icon "check" >}}** in the top right corner to save the check.
+
+## Clone a check
+Create a new check by cloning an existing check.
+
+1. Go to **Alerts > Alerts** in the navigation on the left.
+
+    {{< nav-icon "alerts" >}}
+
+2. Click the **{{< icon "gear" >}}** icon next to the check you want to clone
+    and then click **Clone**.
diff --git a/content/influxdb/v2.2/monitor-alert/checks/delete.md b/content/influxdb/v2.2/monitor-alert/checks/delete.md
new file mode 100644
index 000000000..5895838eb
--- /dev/null
+++ b/content/influxdb/v2.2/monitor-alert/checks/delete.md
@@ -0,0 +1,33 @@
+---
+title: Delete checks
+seotitle: Delete monitoring checks in InfluxDB
+description: >
+  Delete checks in the InfluxDB UI.
+menu:
+  influxdb_2_2:
+    parent: Manage checks
+weight: 204
+related:
+  - /influxdb/v2.2/monitor-alert/notification-rules/
+  - /influxdb/v2.2/monitor-alert/notification-endpoints/
+---
+
+If you no longer need a check, use the InfluxDB user interface (UI) to delete it.
+
+{{% warn %}}
+Deleting a check cannot be undone.
+{{% /warn %}}
+
+1.  In the navigation menu on the left, select **Alerts > Alerts**.
+
+    {{< nav-icon "alerts" >}}
+
+2.  Click the **{{< icon "delete" >}}** icon, and then click **{{< caps >}}Confirm{{< /caps >}}**.
+
+After a check is deleted, all statuses generated by the check remain in the `_monitoring`
+bucket until the retention period for the bucket expires.
+
+{{% note %}}
+You can also [disable a check](/influxdb/v2.2/monitor-alert/checks/update/#enable-or-disable-a-check)
+without having to delete it.
+{{% /note %}}
diff --git a/content/influxdb/v2.2/monitor-alert/checks/update.md b/content/influxdb/v2.2/monitor-alert/checks/update.md
new file mode 100644
index 000000000..349f20a43
--- /dev/null
+++ b/content/influxdb/v2.2/monitor-alert/checks/update.md
@@ -0,0 +1,60 @@
+---
+title: Update checks
+seotitle: Update monitoring checks in InfluxDB
+description: >
+  Update, rename, enable or disable checks in the InfluxDB UI.
+menu:
+  influxdb_2_2:
+    parent: Manage checks
+weight: 203
+related:
+  - /influxdb/v2.2/monitor-alert/notification-rules/
+  - /influxdb/v2.2/monitor-alert/notification-endpoints/
+---
+
+Update checks in the InfluxDB user interface (UI).
+Common updates include:
+
+- [Update check queries and logic](#update-check-queries-and-logic)
+- [Enable or disable a check](#enable-or-disable-a-check)
+- [Rename a check](#rename-a-check)
+- [Add or update a check description](#add-or-update-a-check-description)
+- [Add a label to a check](#add-a-label-to-a-check)
+
+To update checks, select **Alerts > Alerts** in the navigation menu on the left.
+
+{{< nav-icon "alerts" >}}
+
+
+## Update check queries and logic
+1. Click the name of the check you want to update. The check builder appears.
+2. To edit the check query, click **{{< caps >}}1. Define Query{{< /caps >}}** at the top of the check builder window.
+3. To edit the check logic, click **{{< caps >}}2. Configure Check{{< /caps >}}** at the top of the check builder window.
+
+_For details about using the check builder, see [Create checks](/influxdb/v2.2/monitor-alert/checks/create/)._
+
+## Enable or disable a check
+Click the {{< icon "toggle" >}} toggle next to a check to enable or disable it.
+
+## Rename a check
+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.  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)._
+
+## Add or update a check description
+1.  Hover over the check description you want to update.
+2.  Click the **{{< icon "edit" >}}** icon that appears next to the description.
+2.  Enter a new description and click out of the name field or press enter to save.
+
+## Add a label to a check
+1.  Click **{{< icon "add-label" >}} Add a label** next to the check you want to add a label to.
+    The **Add Labels** box appears.
+2.  To add an existing label, select the label from the list.
+3.  To create and add a new label:
+    - In the search field, enter the name of the new label. The **Create Label** box opens.
+    - In the **Description** field, enter an optional description for the label.
+    - Select a color for the label.
+    - Click **{{< caps >}}Create Label{{< /caps >}}**.
+4.  To remove a label, click **{{< icon "x" >}}** on the label.
diff --git a/content/influxdb/v2.2/monitor-alert/checks/view.md b/content/influxdb/v2.2/monitor-alert/checks/view.md
new file mode 100644
index 000000000..b77616ace
--- /dev/null
+++ b/content/influxdb/v2.2/monitor-alert/checks/view.md
@@ -0,0 +1,37 @@
+---
+title: View checks
+seotitle: View monitoring checks in InfluxDB
+description: >
+  View check details and statuses and notifications generated by checks in the InfluxDB UI.
+menu:
+  influxdb_2_2:
+    parent: Manage checks
+weight: 202
+related:
+  - /influxdb/v2.2/monitor-alert/notification-rules/
+  - /influxdb/v2.2/monitor-alert/notification-endpoints/
+---
+
+View check details and statuses and notifications generated by checks in the InfluxDB user interface (UI).
+
+- [View a list of all checks](#view-a-list-of-all-checks)
+- [View check details](#view-check-details)
+- [View statuses generated by a check](#view-statuses-generated-by-a-check)
+- [View notifications triggered by a check](#view-notifications-triggered-by-a-check)
+
+To view checks, click **Alerts > Alerts** in navigation menu on the left.
+
+{{< nav-icon "alerts" >}}
+
+## View a list of all checks
+The **{{< caps >}}Checks{{< /caps >}}** section of the Alerts landing page displays all existing checks.
+
+## View check details
+Click the name of the check you want to view.
+The check builder appears.
+Here you can view the check query and logic.
+
+## View statuses generated by a check
+1. Click the **{{< icon "view" >}}** icon on the check.
+2. Click **View History**.
+   The Statuses History page displays statuses generated by the selected check.
diff --git a/content/influxdb/v2.2/monitor-alert/custom-checks.md b/content/influxdb/v2.2/monitor-alert/custom-checks.md
new file mode 100644
index 000000000..648602878
--- /dev/null
+++ b/content/influxdb/v2.2/monitor-alert/custom-checks.md
@@ -0,0 +1,96 @@
+---
+title: Create custom checks
+seotitle: Custom checks
+description: >
+  Create custom checks with a Flux task.
+menu:
+  influxdb_2_2:
+    parent: Monitor & alert
+weight: 201
+influxdb/v2.2/tags: [alerts, checks, tasks, Flux]
+---
+
+In the UI, you can create two kinds of [checks](/influxdb/v2.2/reference/glossary/#check):
+[`threshold`](/influxdb/v2.2/monitor-alert/checks/create/#threshold-check) and
+[`deadman`](/influxdb/v2.2/monitor-alert/checks/create/#deadman-check).
+
+Using a Flux task, you can create a custom check that provides a couple advantages:
+
+- Customize and transform the data you would like to use for the check.
+- Set up custom criteria for your alert (other than `threshold` and `deadman`).
+
+## Create a task
+
+1. In the InfluxDB UI, select **Tasks** in the navigation menu on the left.
+
+    {{< nav-icon "tasks" >}}
+
+2. Click **{{< caps >}}{{< icon "plus" >}} Create Task{{< /caps >}}**.
+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`).
+   For more detail, such as using cron syntax or including an offset, see [Task configuration options](/influxdb/v2.2/process-data/task-options/).
+4. Enter the Flux script for your custom check, including the [`monitor.check`](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/monitor/check/) function.
+
+{{% note %}}
+Use the [`/api/v2/checks/{checkID}/query` API endpoint](/influxdb/v2.2/api/#operation/DeleteDashboardsIDOwnersID)
+to see the Flux code for a check built in the UI.
+This can be useful for constructing custom checks.
+{{% /note %}}
+
+### Example: Monitor failed tasks
+
+The script below is fairly complex, and can be used as a framework for similar tasks.
+It does the following:
+
+- Import the necessary `influxdata/influxdb/monitor` package, and other packages for data processing.
+- Query the `_tasks` bucket to retrieve all statuses generated by your check.
+- Set the `_level` to alert on, for example, `crit`, `warn`, `info`, or `ok`.
+- Create a `check` object that specifies an ID, name, and type for the check.
+- Define the `ok` and `crit` statuses.
+- Execute the `monitor` function on the `check` using the `task_data`.
+
+#### Example alert task script
+
+```js
+import "strings"
+import "regexp"
+import "influxdata/influxdb/monitor"
+import "influxdata/influxdb/schema"
+
+option task = {name: "Failed Tasks Check", every: 1h, offset: 4m}
+
+task_data = from(bucket: "_tasks")
+    |> range(start: -task.every)
+    |> filter(fn: (r) => r["_measurement"] == "runs")
+    |> filter(fn: (r) => r["_field"] == "logs")
+    |> map(fn: (r) => ({r with name: strings.split(v: regexp.findString(r: /option task = \{([^\}]+)/, v: r._value), t: "\\\\\\\"")[1]}))
+    |> drop(columns: ["_value", "_start", "_stop"])
+    |> group(columns: ["name", "taskID", "status", "_measurement"])
+    |> map(fn: (r) => ({r with _value: if r.status == "failed" then 1 else 0}))
+    |> last()
+
+check = {
+    // 16 characters, alphanumeric
+    _check_id: "0000000000000001",
+    // Name string
+    _check_name: "Failed Tasks Check",
+    // Check type (threshold, deadman, or custom)
+    _type: "custom",
+    tags: {},
+}
+ok = (r) => r["logs"] == 0
+crit = (r) => r["logs"] == 1
+messageFn = (r) => "The task: ${r.taskID} - ${r.name} has a status of ${r.status}"
+
+task_data
+    |> schema["fieldsAsCols"]()
+    |> monitor["check"](data: check, messageFn: messageFn, ok: ok, crit: crit)
+```
+
+{{% note %}}
+Creating a custom check does not send a notification email.
+For information on how to create notification emails, see
+[Create notification endpoints](/influxdb/v2.2/monitor-alert/notification-endpoints/create),
+[Create notification rules](/influxdb/v2.2/monitor-alert/notification-rules/create),
+and [Send alert email](/influxdb/v2.2/monitor-alert/send-email/)
+{{% /note %}}
diff --git a/content/influxdb/v2.2/monitor-alert/notification-endpoints/_index.md b/content/influxdb/v2.2/monitor-alert/notification-endpoints/_index.md
new file mode 100644
index 000000000..8b5e8a802
--- /dev/null
+++ b/content/influxdb/v2.2/monitor-alert/notification-endpoints/_index.md
@@ -0,0 +1,19 @@
+---
+title: Manage notification endpoints
+list_title: Manage notification endpoints
+description: >
+  Create, read, update, and delete endpoints in the InfluxDB UI.
+influxdb/v2.2/tags: [monitor, endpoints, notifications, alert]
+menu:
+  influxdb_2_2:
+    parent: Monitor & alert
+weight: 102
+related:
+  - /influxdb/v2.2/monitor-alert/checks/
+  - /influxdb/v2.2/monitor-alert/notification-rules/
+---
+
+Notification endpoints store information to connect to a third-party service.
+Create a connection to a HTTP, Slack, or PagerDuty endpoint.
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/monitor-alert/notification-endpoints/create.md b/content/influxdb/v2.2/monitor-alert/notification-endpoints/create.md
new file mode 100644
index 000000000..d155d2667
--- /dev/null
+++ b/content/influxdb/v2.2/monitor-alert/notification-endpoints/create.md
@@ -0,0 +1,67 @@
+---
+title: Create notification endpoints
+description: >
+   Create notification endpoints to send alerts on your time series data.
+menu:
+  influxdb_2_2:
+    name: Create endpoints
+    parent: Manage notification endpoints
+weight: 201
+related:
+  - /influxdb/v2.2/monitor-alert/checks/
+  - /influxdb/v2.2/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](/influxdb/v2.2/monitor-alert/notification-rules/create) to send alerts to third-party services on [check statuses](/influxdb/v2.2/monitor-alert/checks/create).
+
+{{% cloud-only %}}
+
+#### Endpoints available in InfluxDB Cloud
+The following endpoints are available for the InfluxDB Cloud Free Plan and Usage-based Plan:
+
+| Endpoint      | Free Plan                | Usage-based Plan             |
+|:--------      |:-------------------:     |:----------------------------:|
+| **Slack**     | **{{< icon "check" >}}** | **{{< icon "check" >}}**     |
+| **PagerDuty** |                          | **{{< icon "check" >}}**     |
+| **HTTP**      |                          | **{{< icon "check" >}}**     |
+
+{{% /cloud-only %}}
+
+## Create a notification endpoint
+
+1.  In the navigation menu on the left, select **Alerts > Alerts**.
+
+    {{< nav-icon "alerts" >}}
+
+2.  Select **{{< caps >}}Notification Endpoints{{< /caps >}}**.
+3.  Click **{{< caps >}}{{< icon "plus" >}} Create{{< /caps >}}**.
+4.  From the **Destination** drop-down list, select a destination endpoint to send notifications to.
+    {{% cloud-only %}}_See [available endpoints](#endpoints-available-in-influxdb-cloud)._{{% /cloud-only %}}
+5.  In the **Name** and **Description** fields, enter a name and description for the endpoint.
+6.  Enter information to connect to the endpoint:
+
+    - **For HTTP**, enter the **URL** to send the notification.
+      Select the **auth method** to use: **None** for no authentication.
+      To authenticate with a username and password, select **Basic** and then
+      enter credentials in the **Username** and **Password** fields.
+      To authenticate with an API token, select **Bearer**, and then enter the
+      API token in the **Token** field.
+
+    - **For Slack**, create an [Incoming WebHook](https://api.slack.com/incoming-webhooks#posting_with_webhooks)
+      in Slack, and then enter your webHook URL in the **Slack Incoming WebHook URL** field.
+
+    - **For PagerDuty**:
+      - [Create a new service](https://support.pagerduty.com/docs/services-and-integrations#section-create-a-new-service),
+        [add an integration for your service](https://support.pagerduty.com/docs/services-and-integrations#section-add-integrations-to-an-existing-service),
+        and then enter the PagerDuty integration key for your new service in the **Routing Key** field.
+      - The **Client URL** provides a useful link in your PagerDuty notification.
+        Enter any URL that you'd like to use to investigate issues.
+        This URL is sent as the `client_url` property in the PagerDuty trigger event.
+        By default, the **Client URL** is set to your Monitoring & Alerting History
+        page, and the following included in the PagerDuty trigger event:
+
+          ```json
+          "client_url": "http://localhost:8086/orgs/<your-org-ID>/alert-history"
+          ```
+
+6. Click **{{< caps >}}Create Notification Endpoint{{< /caps >}}**.
diff --git a/content/influxdb/v2.2/monitor-alert/notification-endpoints/delete.md b/content/influxdb/v2.2/monitor-alert/notification-endpoints/delete.md
new file mode 100644
index 000000000..4ffa3dbf3
--- /dev/null
+++ b/content/influxdb/v2.2/monitor-alert/notification-endpoints/delete.md
@@ -0,0 +1,28 @@
+---
+title: Delete notification endpoints
+description: >
+   Delete a notification endpoint in the InfluxDB UI.
+menu:
+  influxdb_2_2:
+    name: Delete endpoints
+    parent: Manage notification endpoints
+weight: 204
+related:
+  - /influxdb/v2.2/monitor-alert/checks/
+  - /influxdb/v2.2/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](/influxdb/v2.2/monitor-alert/notification-rules/update)
+with a new notification endpoint as needed.
+
+## Delete a notification endpoint
+
+1.  In the navigation menu on the left, select **Alerts > Alerts**.
+
+    {{< nav-icon "alerts" >}}
+
+2.  Select **{{< caps >}}Notification Endpoints{{< /caps >}}** and find the rule
+    you want to delete.
+3.  Click the **{{< icon "trash" >}}** icon on the notification you want to delete
+    and then click **{{< caps >}}Confirm{{< /caps >}}**.
diff --git a/content/influxdb/v2.2/monitor-alert/notification-endpoints/update.md b/content/influxdb/v2.2/monitor-alert/notification-endpoints/update.md
new file mode 100644
index 000000000..82f06e9dd
--- /dev/null
+++ b/content/influxdb/v2.2/monitor-alert/notification-endpoints/update.md
@@ -0,0 +1,55 @@
+---
+title: Update notification endpoints
+description: >
+  Update notification endpoints in the InfluxDB UI.
+menu:
+  influxdb_2_2:
+    name: Update endpoints
+    parent: Manage notification endpoints
+weight: 203
+related:
+  - /influxdb/v2.2/monitor-alert/checks/
+  - /influxdb/v2.2/monitor-alert/notification-rules/
+---
+
+Complete the following steps to update notification endpoint details.
+To update the notification endpoint selected for a notification rule, see [update notification rules](/influxdb/v2.2/monitor-alert/notification-rules/update/).
+
+**To update a notification endpoint**
+
+1. In the navigation menu on the left, select **Alerts > Alerts**.
+
+    {{< nav-icon "alerts" >}}
+
+2. Select **{{< caps >}}Notification Endpoints{{< /caps >}}** and then do the following as needed:
+
+    - [Update the name or description for notification endpoint](#update-the-name-or-description-for-notification-endpoint)
+    - [Change endpoint details](#change-endpoint-details)
+    - [Disable notification endpoint](#disable-notification-endpoint)
+    - [Add a label to notification endpoint](#add-a-label-to-notification-endpoint)
+
+## Update the name or description for notification endpoint
+1. Hover over the name or description of the endpoint and click the pencil icon
+   (**{{< icon "edit" >}}**) to edit the field.
+2. Click outside of the field to save your changes.
+
+## Change endpoint details
+1. Click the name of the endpoint to update.
+2. Update details as needed, and then click **Edit Notification Endpoint**.
+   For details about each field, see [Create notification endpoints](/influxdb/v2.2/monitor-alert/notification-endpoints/create/).
+
+## Disable notification endpoint
+Click the {{< icon "toggle" >}} toggle to disable the notification endpoint.
+
+## Add a label to notification endpoint
+1. Click **{{< icon "add-label" >}} Add a label** next to the endpoint you want to add a label to.
+   The **Add Labels** box opens.
+2. To add an existing label, select the label from the list.
+3. To create and add a new label:
+
+    - In the search field, enter the name of the new label. The **Create Label** box opens.
+    - In the **Description** field, enter an optional description for the label.
+    - Select a color for the label.
+    - Click **{{< caps >}}Create Label{{< /caps >}}**.
+
+4. To remove a label, click **{{< icon "x" >}}** on the label.
diff --git a/content/influxdb/v2.2/monitor-alert/notification-endpoints/view.md b/content/influxdb/v2.2/monitor-alert/notification-endpoints/view.md
new file mode 100644
index 000000000..052858d55
--- /dev/null
+++ b/content/influxdb/v2.2/monitor-alert/notification-endpoints/view.md
@@ -0,0 +1,40 @@
+---
+title: View notification endpoint history
+seotitle: View notification endpoint details and history
+description: >
+  View notification endpoint details and history in the InfluxDB UI.
+menu:
+  influxdb_2_2:
+    name: View endpoint history
+    parent: Manage notification endpoints
+weight: 202
+related:
+  - /influxdb/v2.2/monitor-alert/checks/
+  - /influxdb/v2.2/monitor-alert/notification-rules/
+---
+
+View notification endpoint details and history in the InfluxDB user interface (UI).
+
+
+1. In the navigation menu on the left, select **Alerts**.
+
+    {{< nav-icon "alerts" >}}
+
+2. Select **{{< caps >}}Notification Endpoints{{< /caps >}}**.
+
+    - [View notification endpoint details](#view-notification-endpoint-details)
+    - [View history notification endpoint history](#view-notification-endpoint-history), including statues and notifications sent to the endpoint
+
+## View notification endpoint details
+On the notification endpoints page:
+
+1. Click the name of the notification endpoint you want to view.
+2. View the notification endpoint destination, name, and information to connect to the endpoint.
+
+## View notification endpoint history
+On the notification endpoints page, click the **{{< icon "gear" >}}** icon,
+and then click **View History**.
+The Check Statuses History page displays:
+
+- Statuses generated for the selected notification endpoint
+- Notifications sent to the selected notification endpoint
diff --git a/content/influxdb/v2.2/monitor-alert/notification-rules/_index.md b/content/influxdb/v2.2/monitor-alert/notification-rules/_index.md
new file mode 100644
index 000000000..2ec9ae022
--- /dev/null
+++ b/content/influxdb/v2.2/monitor-alert/notification-rules/_index.md
@@ -0,0 +1,17 @@
+---
+title: Manage notification rules
+description: >
+  Manage notification rules in InfluxDB.
+weight: 103
+influxdb/v2.2/tags: [monitor, notifications, alert]
+menu:
+  influxdb_2_2:
+    parent: Monitor & alert
+related:
+  - /influxdb/v2.2/monitor-alert/checks/
+  - /influxdb/v2.2/monitor-alert/notification-endpoints/
+---
+
+The following articles provide information on managing your notification rules:
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/monitor-alert/notification-rules/create.md b/content/influxdb/v2.2/monitor-alert/notification-rules/create.md
new file mode 100644
index 000000000..a19c09f40
--- /dev/null
+++ b/content/influxdb/v2.2/monitor-alert/notification-rules/create.md
@@ -0,0 +1,44 @@
+---
+title: Create notification rules
+description: >
+  Create notification rules to send alerts on your time series data.
+weight: 201
+menu:
+  influxdb_2_2:
+    parent: Manage notification rules
+related:
+  - /influxdb/v2.2/monitor-alert/checks/
+  - /influxdb/v2.2/monitor-alert/notification-endpoints/
+---
+
+Once you've set up checks and notification endpoints, create notification rules to alert you.
+_For details, see [Manage checks](/influxdb/v2.2/monitor-alert/checks/) and
+[Manage notification endpoints](/influxdb/v2.2/monitor-alert/notification-endpoints/)._
+
+
+1. In the navigation menu on the left, select **Alerts > Alerts**.
+
+    {{< nav-icon "alerts" >}}
+
+2. Select **{{< caps >}}Notification Rules{{< /caps >}}** near to top of the page.
+
+    - [Create a new notification rule in the UI](#create-a-new-notification-rule-in-the-ui)
+    - [Clone an existing notification rule in the UI](#clone-an-existing-notification-rule-in-the-ui)
+
+## Create a new notification rule
+
+1. On the notification rules page, click **{{< caps >}}{{< icon "plus" >}} Create{{< /caps >}}**.
+2. Complete the **About** section:
+  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.
+  3. In the **Offset** field, enter an offset time. For example,if a task runs on the hour, a 10m offset delays the task to 10 minutes after the hour. Time ranges defined in the task are relative to the specified execution time.
+3. In the **Conditions** section, build a condition using a combination of status and tag keys.
+    - Next to **When status is equal to**, select a status from the drop-down field.
+    - Next to **AND When**, enter one or more tag key-value pairs to filter by.
+4. In the **Message** section, select an endpoint to notify.
+5. Click **{{< caps >}}Create Notification Rule{{< /caps >}}**.
+
+## Clone an existing notification rule
+
+On the notification rules page, click the **{{< icon "gear" >}}** icon and select **Clone**.
+The cloned rule appears.
diff --git a/content/influxdb/v2.2/monitor-alert/notification-rules/delete.md b/content/influxdb/v2.2/monitor-alert/notification-rules/delete.md
new file mode 100644
index 000000000..1d7360e6e
--- /dev/null
+++ b/content/influxdb/v2.2/monitor-alert/notification-rules/delete.md
@@ -0,0 +1,24 @@
+---
+title: Delete notification rules
+description: >
+  If you no longer need to receive an alert, delete the associated notification rule.
+weight: 204
+menu:
+  influxdb_2_2:
+    parent: Manage notification rules
+related:
+  - /influxdb/v2.2/monitor-alert/checks/
+  - /influxdb/v2.2/monitor-alert/notification-endpoints/
+---
+
+If you no longer need to receive an alert, delete the associated notification rule.
+
+## Delete a notification rule
+
+1. In the navigation menu on the left, select **Alerts > Alerts**.
+
+    {{< nav-icon "alerts" >}}
+
+2. Select **{{< caps >}}Notification Rules{{< /caps >}}** near to top of the page.
+3. Click the **{{< icon "trash" >}}** icon on the notification rule you want to delete.
+4. Click **{{< caps >}}Confirm{{< /caps >}}**.
diff --git a/content/influxdb/v2.2/monitor-alert/notification-rules/update.md b/content/influxdb/v2.2/monitor-alert/notification-rules/update.md
new file mode 100644
index 000000000..b09f1ea49
--- /dev/null
+++ b/content/influxdb/v2.2/monitor-alert/notification-rules/update.md
@@ -0,0 +1,50 @@
+---
+title: Update notification rules
+description: >
+  Update notification rules to update the notification message or change the schedule or conditions.
+weight: 203
+menu:
+  influxdb_2_2:
+    parent: Manage notification rules
+related:
+  - /influxdb/v2.2/monitor-alert/checks/
+  - /influxdb/v2.2/monitor-alert/notification-endpoints/
+---
+
+Update notification rules to update the notification message or change the schedule or conditions.
+
+
+1. In the navigation menu on the left, select **Alerts > Alerts**.
+
+    {{< nav-icon "alerts" >}}
+
+2. Select **{{< caps >}}Notification Rules{{< /caps >}}** near to top of the page.
+
+- [Update the name or description for notification rules](#update-the-name-or-description-for-notification-rules)
+- [Enable or disable notification rules](#enable-or-disable-notification-rules)
+- [Add a label to notification rules](#add-a-label-to-notification-rules)
+
+## Update the name or description for notification rules
+On the Notification Rules page:
+
+1. Hover over the name or description of a rule and click the pencil icon
+   (**{{< icon "edit" >}}**) to edit the field.
+2. Click outside of the field to save your changes.
+
+## Enable or disable notification rules
+On the notification rules page, click the {{< icon "toggle" >}} toggle to
+enable or disable the notification rule.
+
+## Add a label to notification rules
+On the notification rules page:
+
+1. Click **{{< icon "add-label" >}} Add a label**
+   next to the rule you want to add a label to.
+   The **Add Labels** box opens.
+2. To add an existing label, select the label from the list.
+3. To create and add a new label:
+  - In the search field, enter the name of the new label. The **Create Label** box opens.
+  - In the **Description** field, enter an optional description for the label.
+  - Select a color for the label.
+  - Click **{{< caps >}}Create Label{{< /caps >}}**.
+4. To remove a label, click **{{< icon "x" >}}** on the label.
diff --git a/content/influxdb/v2.2/monitor-alert/notification-rules/view.md b/content/influxdb/v2.2/monitor-alert/notification-rules/view.md
new file mode 100644
index 000000000..0dc67e38f
--- /dev/null
+++ b/content/influxdb/v2.2/monitor-alert/notification-rules/view.md
@@ -0,0 +1,44 @@
+---
+title: View notification rules
+description: >
+  Update notification rules to update the notification message or change the schedule or conditions.
+weight: 202
+menu:
+  influxdb_2_2:
+    parent: Manage notification rules
+related:
+  - /influxdb/v2.2/monitor-alert/checks/
+  - /influxdb/v2.2/monitor-alert/notification-endpoints/
+---
+
+View notification rule details and statuses and notifications generated by notification rules in the InfluxDB user interface (UI).
+
+- [View a list of all notification rules](#view-a-list-of-all-notification-rules)
+- [View notification rule details](#view-notification-rule-details)
+- [View statuses generated by a check](#view-statuses-generated-by-a-notification-rule)
+- [View notifications triggered by a notification rule](#view-notifications-triggered-by-a-notification-rule)
+
+**To view notification rules:**
+
+1. In the navigation menu on the left, select **Alerts**.
+
+    {{< nav-icon "alerts" >}}
+
+2. Select **{{< caps >}}Notification Rules{{< /caps >}}** near to top of the page.
+
+## View a list of all notification rules
+The **{{< caps >}}Notification Rules{{< /caps >}}** section of the Alerts landing page displays all existing checks.
+
+## View notification rule details
+Click the name of the check you want to view.
+The check builder appears.
+Here you can view the check query and logic.
+
+## View statuses generated by a notification rule
+Click the **{{< icon "gear" >}}** icon on the notification rule, and then **View History**.
+The Statuses History page displays statuses generated by the selected check.
+
+## View notifications triggered by a notification rule
+1. Click the **{{< icon "gear" >}}** icon on the notification rule, and then **View History**.
+2. In the top left corner, click **{{< caps >}}Notifications{{< /caps >}}**.
+   The Notifications History page displays notifications initiated by the selected notification rule.
diff --git a/content/influxdb/v2.2/monitor-alert/send-email.md b/content/influxdb/v2.2/monitor-alert/send-email.md
new file mode 100644
index 000000000..3172c67a6
--- /dev/null
+++ b/content/influxdb/v2.2/monitor-alert/send-email.md
@@ -0,0 +1,295 @@
+---
+title: Send alert email
+description: >
+  Send an alert email.
+menu:
+  influxdb_2_2:
+    parent: Monitor & alert
+weight: 104
+influxdb/v2.2/tags: [alert, email, notifications, check]
+related:
+  - /influxdb/v2.2/monitor-alert/checks/
+---
+
+Send an alert email using a third-party service, such as [SendGrid](https://sendgrid.com/), [Amazon Simple Email Service (SES)](https://aws.amazon.com/ses/), [Mailjet](https://www.mailjet.com/), or [Mailgun](https://www.mailgun.com/). To send an alert email, complete the following steps:
+
+1. [Create a check](/influxdb/v2.2/monitor-alert/checks/create/#create-a-check-in-the-influxdb-ui) to identify the data to monitor and the status to alert on.
+2. Set up your preferred email service (sign up, retrieve API credentials, and send test email):
+   - **SendGrid**: See [Getting Started With the SendGrid API](https://sendgrid.com/docs/API_Reference/api_getting_started.html)
+   - **AWS Simple Email Service (SES)**: See [Using the Amazon SES API](https://docs.aws.amazon.com/ses/latest/DeveloperGuide/send-email.html). Your AWS SES request, including the `url` (endpoint), authentication, and the structure of the request may vary. For more information, see [Amazon SES API requests](https://docs.aws.amazon.com/ses/latest/DeveloperGuide/using-ses-api-requests.html) and [Authenticating requests to the Amazon SES API](https://docs.aws.amazon.com/ses/latest/DeveloperGuide/using-ses-api-authentication.html).
+   - **Mailjet**: See [Getting Started with Mailjet](https://dev.mailjet.com/email/guides/getting-started/)
+   - **Mailgun**: See [Mailgun Signup](https://signup.mailgun.com/new/signup)
+3. [Create an alert email task](#create-an-alert-email-task) to call your email service and send an alert email.
+
+  {{% note %}}
+  In the procedure below, we use the **Task** page in the InfluxDB UI (user interface) to create a task. Explore other ways to [create a task](/influxdb/v2.2/process-data/manage-tasks/create-task/).
+  {{% /note %}}
+
+### Create an alert email task
+
+1.  In the InfluxDB UI, select **Tasks** in the navigation menu on the left.
+
+    {{< nav-icon "tasks" >}}
+
+2.  Click **{{< caps >}}{{< icon "plus" >}} Create Task{{< /caps >}}**.
+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.2/process-data/task-options/).
+
+4.  In the right panel, enter the following detail in your **task script** (see [examples below](#examples)):
+    - Import the [Flux HTTP package](/{{< latest "flux" >}}/stdlib/http/).
+    - (Optional) Store your API key as a secret for reuse.
+      First, [add your API key as a secret](/influxdb/v2.2/security/secrets/manage-secrets/add/),
+      and then import the [Flux InfluxDB Secrets package](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/secrets/).
+    - Query the `statuses` measurement in the `_monitoring` bucket to retrieve all statuses generated by your check.
+    - Set the time range to monitor; use the same interval that the task is scheduled to run. For example, `range (start: -task.every)`.
+    - Set the `_level` to alert on, for example, `crit`, `warn`, `info`, or `ok`.
+    - Use the `map()` function to evaluate the criteria to send an alert using `http.post()`.
+    - Specify your email service `url` (endpoint), include applicable request `headers`, and verify your request `data` format follows the format specified for your email service.
+
+#### Examples
+
+{{< tabs-wrapper >}}
+{{% tabs %}}
+[SendGrid](#)
+[AWS SES](#)
+[Mailjet](#)
+[Mailgun](#)
+{{% /tabs %}}
+
+<!-------------------------------- BEGIN SendGrid -------------------------------->
+{{% tab-content %}}
+
+The example below uses the SendGrid API to send an alert email when more than 3 critical statuses occur since the previous task run.
+
+```js
+import "http"
+import "json"
+// Import the Secrets package if you store your API key as a secret.
+// For detail on how to do this, see Step 4 above.
+import "influxdata/influxdb/secrets"
+
+// Retrieve the secret if applicable. Otherwise, skip this line
+// and add the API key as the Bearer token in the Authorization header.
+SENDGRID_APIKEY = secrets.get(key: "SENDGRID_APIKEY")
+
+numberOfCrits = from(bucket: "_monitoring")
+    |> range(start: -task.every)
+    |> filter(fn: (r) => r._measurement == "statuses" and r._level == "crit")
+    |> count()
+
+numberOfCrits
+    |> map(
+        fn: (r) => if r._value > 3 then
+            {r with _value: http.post(
+                url: "https://api.sendgrid.com/v3/mail/send",
+                headers: {"Content-Type": "application/json", "Authorization": "Bearer ${SENDGRID_APIKEY}"},
+                data: json.encode(
+                    v: {
+                        "personalizations": [
+                            {
+                                "to": [
+                                    {
+                                        "email": "jane.doe@example.com"
+                                    }
+                                ]
+                            }
+                        ],
+                        "from": {
+                            "email": "john.doe@example.com"
+                        },
+                        "subject": "InfluxDB critical alert",
+                        "content": [
+                            {
+                                "type": "text/plain",
+                                "value": "There have been ${r._value} critical statuses."
+                            }
+                        ]
+                    }
+                )
+            )}
+        else
+            {r with _value: 0},
+    )
+```
+
+{{% /tab-content %}}
+
+<!-------------------------------- BEGIN AWS SES -------------------------------->
+{{% tab-content %}}
+
+The example below uses the AWS SES API v2 to send an alert email when more than 3 critical statuses occur since the last task run.
+
+{{% note %}}
+Your AWS SES request, including the `url` (endpoint), authentication, and the structure of the request may vary. For more information, see [Amazon SES API requests](https://docs.aws.amazon.com/ses/latest/DeveloperGuide/using-ses-api-requests.html) and [Authenticating requests to the Amazon SES API](https://docs.aws.amazon.com/ses/latest/DeveloperGuide/using-ses-api-authentication.html). We recommend signing your AWS API requests using the [Signature Version 4 signing process](https://docs.aws.amazon.com/general/latest/gr/signing_aws_api_requests.html).
+{{% /note %}}
+
+```js
+import "http"
+import "json"
+// Import the Secrets package if you store your API credentials as secrets.
+// For detail on how to do this, see Step 4 above.
+import "influxdata/influxdb/secrets"
+
+// Retrieve the secrets if applicable. Otherwise, skip this line
+// and add the API key as the Bearer token in the Authorization header.
+AWS_AUTH_ALGORITHM = secrets.get(key: "AWS_AUTH_ALGORITHM")
+AWS_CREDENTIAL = secrets.get(key: "AWS_CREDENTIAL")
+AWS_SIGNED_HEADERS = secrets.get(key: "AWS_SIGNED_HEADERS")
+AWS_CALCULATED_SIGNATURE = secrets.get(key: "AWS_CALCULATED_SIGNATURE")
+
+numberOfCrits = from(bucket: "_monitoring")
+    |> range(start: -task.every)
+    |> filter(fn: (r) => r.measurement == "statuses" and r._level == "crit")
+    |> count()
+
+numberOfCrits
+    |> map(
+        fn: (r) => if r._value > 3 then
+            {r with _value: http.post(
+                url: "https://email.your-aws-region.amazonaws.com/sendemail/v2/email/outbound-emails",
+                headers: {
+                    "Content-Type": "application/json",
+                    "Authorization": "Bearer ${AWS_AUTH_ALGORITHM}${AWS_CREDENTIAL}${AWS_SIGNED_HEADERS}${AWS_CALCULATED_SIGNATURE}"},
+                data: json.encode(v: {
+                        "Content": {
+                            "Simple": {
+                                "Body": {
+                                    "Text": {
+                                        "Charset": "UTF-8",
+                                        "Data": "There have been ${r._value} critical statuses."
+                                    }
+                                },
+                                "Subject": {
+                                    "Charset": "UTF-8",
+                                    "Data": "InfluxDB critical alert"
+                                }
+                            }
+                        },
+                        "Destination": {
+                            "ToAddresses": [
+                                "john.doe@example.com"
+                            ]
+                        }
+                    }
+                )
+            )}
+        else
+            {r with _value: 0},
+    )
+```
+
+For details on the request syntax, see [SendEmail API v2 reference](https://docs.aws.amazon.com/ses/latest/APIReference-V2/API_SendEmail.html).
+
+{{% /tab-content %}}
+
+<!-------------------------------- BEGIN Mailjet ------------------------------->
+{{% tab-content %}}
+
+The example below uses the Mailjet Send API to send an alert email when more than 3 critical statuses occur since the last task run.
+
+{{% note %}}
+To view your Mailjet API credentials, sign in to Mailjet and open the [API Key Management page](https://app.mailjet.com/account/api_keys).
+{{% /note %}}
+
+```js
+import "http"
+import "json"
+// Import the Secrets package if you store your API keys as secrets.
+// For detail on how to do this, see Step 4 above.
+import "influxdata/influxdb/secrets"
+
+// Retrieve the secrets if applicable. Otherwise, skip this line
+// and add the API keys as Basic credentials in the Authorization header.
+MAILJET_APIKEY = secrets.get(key: "MAILJET_APIKEY")
+MAILJET_SECRET_APIKEY = secrets.get(key: "MAILJET_SECRET_APIKEY")
+
+numberOfCrits = from(bucket: "_monitoring")
+    |> range(start: -task.every)
+    |> filter(fn: (r) => r.measurement == "statuses" and "r.level" == "crit")
+    |> count()
+
+numberOfCrits
+    |> map(
+        fn: (r) => if r._value > 3 then
+            {r with
+                _value: http.post(
+                    url: "https://api.mailjet.com/v3.1/send",
+                    headers: {
+                        "Content-type": "application/json",
+                        "Authorization": "Basic ${MAILJET_APIKEY}:${MAILJET_SECRET_APIKEY}"
+                    },
+                    data: json.encode(
+                        v: {
+                            "Messages": [
+                                {
+                                    "From": {"Email": "jane.doe@example.com"},
+                                    "To": [{"Email": "john.doe@example.com"}],
+                                    "Subject": "InfluxDB critical alert",
+                                    "TextPart": "There have been ${r._value} critical statuses.",
+                                    "HTMLPart": "<h3>${r._value} critical statuses</h3><p>There have been ${r._value} critical statuses.",
+                                },
+                            ],
+                        },
+                    ),
+                ),
+            }
+        else
+            {r with _value: 0},
+    )
+```
+
+{{% /tab-content %}}
+
+<!-------------------------------- BEGIN Mailgun ---------------------------->
+
+{{% tab-content %}}
+
+The example below uses the Mailgun API to send an alert email when more than 3 critical statuses occur since the last task run.
+
+{{% note %}}
+To view your Mailgun API keys, sign in to Mailjet and open [Account Security - API security](https://app.mailgun.com/app/account/security/api_keys). Mailgun requires that a domain be specified via Mailgun. A domain is automatically created for you when you first set up your account. You must include this domain in your `url` endpoint (for example, `https://api.mailgun.net/v3/YOUR_DOMAIN` or `https://api.eu.mailgun.net/v3/YOUR_DOMAIN`. If you're using a free version of Mailgun, you can set up a maximum of five authorized recipients (to receive email alerts) for your domain. To view your Mailgun domains, sign in to Mailgun and view the [Domains page](https://app.mailgun.com/app/sending/domains).
+{{% /note %}}
+
+```js
+import "http"
+import "json"
+// Import the Secrets package if you store your API key as a secret.
+// For detail on how to do this, see Step 4 above.
+import "influxdata/influxdb/secrets"
+
+// Retrieve the secret if applicable. Otherwise, skip this line
+// and add the API key as the Bearer token in the Authorization header.
+MAILGUN_APIKEY = secrets.get(key: "MAILGUN_APIKEY")
+
+numberOfCrits = from(bucket: "_monitoring")
+    |> range(start: -task.every)
+    |> filter(fn: (r) => r["_measurement"] == "statuses")
+    |> filter(fn: (r) => r["_level"] == "crit")
+    |> count()
+
+numberOfCrits
+    |> map(
+        fn: (r) => if r._value > 1 then
+            {r with _value: http.post(
+                url: "https://api.mailgun.net/v3/YOUR_DOMAIN/messages",
+                headers: {
+                    "Content-type": "application/json",
+                    "Authorization": "Basic api:${MAILGUN_APIKEY}"
+                },
+                data: json.encode(v: {
+                        "from": "Username <mailgun@YOUR_DOMAIN_NAME>",
+                        "to": "email@example.com",
+                        "subject": "InfluxDB critical alert",
+                        "text": "There have been ${r._value} critical statuses."
+                    }                
+                )
+            )}
+        else
+            {r with _value: 0},
+    )
+```
+
+{{% /tab-content %}}
+
+{{< /tabs-wrapper >}}
diff --git a/content/influxdb/v2.2/monitor-alert/templates/_index.md b/content/influxdb/v2.2/monitor-alert/templates/_index.md
new file mode 100644
index 000000000..83f63058a
--- /dev/null
+++ b/content/influxdb/v2.2/monitor-alert/templates/_index.md
@@ -0,0 +1,14 @@
+---
+title: Monitor with templates
+description: >
+  Use community templates to monitor data in many supported environments. Monitor infrastructure, networking, IoT, software, security, TICK stack, and more.
+menu:
+  influxdb_2_2:
+    parent: Monitor & alert
+weight: 104
+influxdb/v2.2/tags: [monitor, templates]
+---
+
+Use one of our community templates to quickly set up InfluxDB (with a bucket and dashboard) to collect, analyze, and monitor data in supported environments.
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/monitor-alert/templates/infrastructure/_index.md b/content/influxdb/v2.2/monitor-alert/templates/infrastructure/_index.md
new file mode 100644
index 000000000..747724098
--- /dev/null
+++ b/content/influxdb/v2.2/monitor-alert/templates/infrastructure/_index.md
@@ -0,0 +1,14 @@
+---
+title: Monitor infrastructure
+description: >
+  Use one of our community templates to quickly set up InfluxDB (with a bucket and dashboard) to collect, analyze, and monitor your infrastructure.
+menu:
+  influxdb_2_2:
+    parent: Monitor with templates
+weight: 104
+influxdb/v2.2/tags: [monitor, templates, infrastructure]
+---
+
+Use one of our community templates to quickly set up InfluxDB (with a bucket and dashboard) to collect, analyze, and monitor your infrastructure.
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/monitor-alert/templates/infrastructure/aws.md b/content/influxdb/v2.2/monitor-alert/templates/infrastructure/aws.md
new file mode 100644
index 000000000..8b5250af8
--- /dev/null
+++ b/content/influxdb/v2.2/monitor-alert/templates/infrastructure/aws.md
@@ -0,0 +1,59 @@
+---
+title: Monitor Amazon Web Services (AWS)
+description: >
+  Use the AWS CloudWatch Monitoring template to monitor data from Amazon Web Services (AWS), Amazon Elastic Compute Cloud (EC2), and Amazon Elastic Load Balancing (ELB) with the AWS CloudWatch Service.
+menu:
+  influxdb_2_2:
+    parent: Monitor infrastructure
+    name: AWS CloudWatch
+weight: 201
+---
+
+Use the [AWS CloudWatch Monitoring template](https://github.com/influxdata/community-templates/tree/master/aws_cloudwatch) to monitor data from [Amazon Web Services (AWS)](https://aws.amazon.com/), [Amazon Elastic Compute Cloud (EC2)](https://aws.amazon.com/ec2/), and [Amazon Elastic Load Balancing (ELB)](https://aws.amazon.com/elasticloadbalancing/) with the [AWS CloudWatch Service](https://aws.amazon.com/cloudwatch/).
+
+The AWS CloudWatch Monitoring template includes the following:
+
+- two [dashboards](/influxdb/v2.2/reference/glossary/#dashboard):
+  - **AWS CloudWatch NLB (Network Load Balancers) Monitoring**: Displays data from the `cloudwatch_aws_network_elb measurement`
+  - **AWS CloudWatch Instance Monitoring**: Displays data from the `cloudwatch_aws_ec2` measurement
+- two [buckets](/influxdb/v2.2/reference/glossary/#bucket): `kubernetes` and `cloudwatch`
+- two labels: `inputs.cloudwatch`, `AWS`
+- one variable: `v.bucket`
+- one [Telegraf configuration](/influxdb/v2.2/telegraf-configs/): [AWS CloudWatch input plugin](/{{< latest "telegraf" >}}/plugins//#cloudwatch)
+
+## Apply the template
+
+1. Use the [`influx` CLI](/influxdb/v2.2/reference/cli/influx/) to run the following command:
+
+    ```sh
+    influx apply -f https://raw.githubusercontent.com/influxdata/community-templates/master/aws_cloudwatch/aws_cloudwatch.yml
+    ```
+    For more information, see [influx apply](/influxdb/v2.2/reference/cli/influx/apply/).
+2. [Install Telegraf](/{{< latest "telegraf" >}}/introduction/installation/) on a server with network access to both the CloudWatch API and [InfluxDB v2 API](/influxdb/v2.2/reference/api/).
+3. In your Telegraf configuration file (`telegraf.conf`), find the following example `influxdb_v2` output plugins, and then **replace** the `urls` to specify the servers to monitor:
+
+   ```sh
+    ## k8s
+    [[outputs.influxdb_v2]]
+     urls = ["http://influxdb.monitoring:8086"]
+     organization = "InfluxData"
+     bucket = "kubernetes"
+     token = "secret-token"
+ 
+    ## cloudv2 sample
+    [[outputs.influxdb_v2]]
+     urls = ["$INFLUX_HOST"]
+     token = "$INFLUX_TOKEN"
+     organization = "$INFLUX_ORG"
+     bucket = “cloudwatch"
+   ```
+4. [Start Telegraf](/influxdb/v2.2/write-data/no-code/use-telegraf/auto-config/#start-telegraf).
+
+## View the incoming data
+
+1. In the InfluxDB user interface (UI), select **Dashboards** in the left navigation.
+
+    {{< nav-icon "dashboards" >}}
+
+2. Open your AWS dashboards, and then set the `v.bucket` variable to specify the
+   bucket to query data from (`kubernetes` or `cloudwatch`).
diff --git a/content/influxdb/v2.2/monitor-alert/templates/infrastructure/docker.md b/content/influxdb/v2.2/monitor-alert/templates/infrastructure/docker.md
new file mode 100644
index 000000000..aebc4ce49
--- /dev/null
+++ b/content/influxdb/v2.2/monitor-alert/templates/infrastructure/docker.md
@@ -0,0 +1,57 @@
+---
+title: Monitor Docker
+description: >
+  Use the [Docker Monitoring template](https://github.com/influxdata/community-templates/tree/master/docker) to monitor your Docker containers.
+menu:
+  influxdb_2_2:
+    parent: Monitor infrastructure
+    name: Docker
+weight: 202
+---
+
+Use the [Docker Monitoring template](https://github.com/influxdata/community-templates/tree/master/docker) to monitor your Docker containers. First, [apply the template](#apply-the-template), and then [view incoming data](#view-incoming-data).
+This template uses the [Docker input plugin](/{{< latest "telegraf" >}}/plugins//#docker) to collect metrics stored in InfluxDB and display these metrics in a dashboard.
+
+The Docker Monitoring template includes the following:
+
+- one [dashboard](/influxdb/v2.2/reference/glossary/#dashboard): **Docker**
+- one [bucket](/influxdb/v2.2/reference/glossary/#bucket): `docker, 7d retention`
+- labels: Docker input plugin labels
+- one [Telegraf configuration](/influxdb/v2.2/telegraf-configs/): Docker input plugin
+- one variable: `bucket`
+- four [checks](/influxdb/v2.2/reference/glossary/#check): `Container cpu`, `mem`, `disk`, `non-zero exit`
+- one [notification endpoint](/influxdb/v2.2/reference/glossary/#notification-endpoint): `Http Post`
+- one [notification rule](/influxdb/v2.2/reference/glossary/#notification-rule): `Crit Alert`
+
+For more information about how checks, notification endpoints, and notifications rules work together, see [monitor data and send alerts](/influxdb/v2.2/monitor-alert/).
+
+## Apply the template
+
+1. Use the [`influx` CLI](/influxdb/v2.2/reference/cli/influx/) to run the following command:
+
+    ```sh
+    influx apply -f https://raw.githubusercontent.com/influxdata/community-templates/master/docker/docker.yml
+    ```
+    For more information, see [influx apply](/influxdb/v2.2/reference/cli/influx/apply/).
+
+    {{% note %}}
+Ensure your `influx` CLI is configured with your account credentials and that configuration is active. For more information, see [influx config](/influxdb/v2.2/reference/cli/influx/config/).
+    {{% /note %}}
+
+2. [Install Telegraf](/{{< latest "telegraf" >}}/introduction/installation/) on a server with network access to both the Docker containers and [InfluxDB v2 API](/influxdb/v2.2/reference/api/).
+3. In your [Telegraf configuration file (`telegraf.conf`)](/influxdb/v2.2/telegraf-configs/), do the following:
+    - Depending on how you run Docker, you may need to customize the [Docker input plugin](/{{< latest "telegraf" >}}/plugins//#docker) configuration, for example, you may need to specify the `endpoint` value.
+    - Set the following environment variables:
+      - INFLUX_TOKEN: Token must have permissions to read Telegraf configurations and write data to the `telegraf` bucket. See how to [view tokens](/influxdb/v2.2/security/tokens/view-tokens/).
+      - INFLUX_ORG: Name of your organization. See how to [view your organization](/influxdb/v2.2/organizations/view-orgs/).
+      - INFLUX_HOST: Your InfluxDB host URL, for example, localhost, a remote instance, or InfluxDB Cloud.
+
+4. [Start Telegraf](/influxdb/v2.2/write-data/no-code/use-telegraf/auto-config/#start-telegraf).
+
+## View incoming data
+
+1. In the InfluxDB user interface (UI), select **Dashboards** in the left navigation.
+
+    {{< nav-icon "dashboards" >}}
+
+2. Open the **Docker** dashboard to start monitoring.
diff --git a/content/influxdb/v2.2/monitor-alert/templates/infrastructure/raspberry-pi.md b/content/influxdb/v2.2/monitor-alert/templates/infrastructure/raspberry-pi.md
new file mode 100644
index 000000000..25f854adf
--- /dev/null
+++ b/content/influxdb/v2.2/monitor-alert/templates/infrastructure/raspberry-pi.md
@@ -0,0 +1,62 @@
+---
+title: Monitor Raspberry Pi
+description: >
+  Use the Raspberry Pi system template to monitor your Raspberry Pi 4 or 400 Linux system. 
+menu:
+  influxdb_2_2:
+    parent: Monitor infrastructure
+    name: Raspberry Pi
+weight: 201
+---
+
+Use the [Raspberry Pi Monitoring template](https://github.com/influxdata/community-templates/tree/master/raspberry-pi)
+to monitor your Raspberry Pi 4 or 400 Linux system.
+
+The Raspberry Pi template includes the following:
+
+- one [bucket](/influxdb/v2.2/reference/glossary/#bucket): `rasp-pi` (7d retention)
+- labels: `raspberry-pi` + Telegraf plugin labels
+  - [Diskio input plugin](/{{< latest "telegraf" >}}/plugins//#diskio) 
+  - [Mem input plugin](/{{< latest "telegraf" >}}/plugins//#mem) 
+  - [Net input plugin](/{{< latest "telegraf" >}}/plugins//#net) 
+  - [Processes input plugin](/{{< latest "telegraf" >}}/plugins//#processes) 
+  - [Swap input plugin](/{{< latest "telegraf" >}}/plugins//#swap) 
+  - [System input plugin](/{{< latest "telegraf" >}}/plugins//#system) 
+- one [Telegraf configuration](/influxdb/v2.2/telegraf-configs/)
+- one [dashboard](/influxdb/v2.2/reference/glossary/#dashboard): Raspberry Pi System
+- two variables: `bucket` and `linux_host`
+
+## Apply the template
+
+1. Use the [`influx` CLI](/influxdb/v2.2/reference/cli/influx/) to run the following command:
+
+    ```sh
+    influx apply -f https://raw.githubusercontent.com/influxdata/community-templates/master/raspberry-pi/raspberry-pi-system.yml
+    ```
+    For more information, see [influx apply](/influxdb/v2.2/reference/cli/influx/apply/).
+2.  [Install Telegraf](/{{< latest "telegraf" >}}/introduction/installation/) on
+    your Raspberry Pi and ensure your Raspberry Pi has network access to the
+    [InfluxDB {{% cloud-only %}}Cloud{{% /cloud-only %}} API](/influxdb/v2.2/reference/api/).
+3. Add the following environment variables to your Telegraf environment:
+
+    - `INFLUX_HOST`: {{% oss-only %}}Your [InfluxDB URL](/influxdb/v2.2/reference/urls/){{% /oss-only %}}
+      {{% cloud-only %}}Your [InfluxDB Cloud region URL](/influxdb/cloud/reference/regions/){{% /cloud-only %}}
+    - `INFLUX_TOKEN`: Your [InfluxDB {{% cloud-only %}}Cloud{{% /cloud-only %}} API token](/influxdb/v2.2/security/tokens/)
+    - `INFLUX_ORG`: Your InfluxDB {{% cloud-only %}}Cloud{{% /cloud-only %}} organization name.
+    
+    ```sh
+    export INFLUX_HOST=http://localhost:8086
+    export INFLUX_TOKEN=mY5uP3rS3cr3T70keN
+    export INFLUX_ORG=example-org
+    ```
+
+4. [Start Telegraf](/influxdb/v2.2/write-data/no-code/use-telegraf/auto-config/#start-telegraf).
+
+## View the incoming data
+
+1. In the InfluxDB user interface (UI), select **Boards** (**Dashboards**).
+
+    {{< nav-icon "dashboards" >}}
+
+2. Click the Raspberry Pi System link to open your dashboard, then select `rasp-pi`
+as your bucket and select your linux_host. 
diff --git a/content/influxdb/v2.2/monitor-alert/templates/infrastructure/vshpere.md b/content/influxdb/v2.2/monitor-alert/templates/infrastructure/vshpere.md
new file mode 100644
index 000000000..db85d7c60
--- /dev/null
+++ b/content/influxdb/v2.2/monitor-alert/templates/infrastructure/vshpere.md
@@ -0,0 +1,58 @@
+---
+title: Monitor vSphere
+description: >
+  Use the [vSphere Dashboard for InfluxDB v2 template](https://github.com/influxdata/community-templates/tree/master/vsphere) to monitor your vSphere host.
+menu:
+  influxdb_2_2:
+    parent: Monitor infrastructure
+    name: vSphere
+weight: 206
+---
+
+Use the [vSphere Dashboard for InfluxDB v2 template](https://github.com/influxdata/community-templates/tree/master/vsphere) to monitor your vSphere host. First, [apply the template](#apply-the-template), and then [view incoming data](#view-incoming-data).
+This template uses the [Docker input plugin](/{{< latest "telegraf" >}}/plugins//#docker) to collect metrics stored in InfluxDB and display these metrics in a dashboard.
+
+The Docker Monitoring template includes the following:
+
+- one [dashboard](/influxdb/v2.2/reference/glossary/#dashboard): **vsphere**
+- one [bucket](/influxdb/v2.2/reference/glossary/#bucket): `vsphere`
+- label: vsphere
+- one [Telegraf configuration](/influxdb/v2.2/telegraf-configs/): InfluxDB v2 output plugin, vSphere input plugin
+- one variable: `bucket`
+
+## Apply the template
+
+1. Use the [`influx` CLI](/influxdb/v2.2/reference/cli/influx/) to run the following command:
+
+    ```sh
+    influx apply -f https://raw.githubusercontent.com/influxdata/community-templates/master/vsphere/vsphere.yml
+    ```
+    For more information, see [influx apply](/influxdb/v2.2/reference/cli/influx/apply/).
+
+    {{% note %}}
+Ensure your `influx` CLI is configured with your account credentials and that configuration is active. For more information, see [influx config](/influxdb/v2.2/reference/cli/influx/config/).
+    {{% /note %}}
+
+2. [Install Telegraf](/{{< latest "telegraf" >}}/introduction/installation/) on a server with network access to both the vSphere host and [InfluxDB v2 API](/influxdb/v2.2/reference/api/).
+3. In your [Telegraf configuration file (`telegraf.conf`)](/influxdb/v2.2/telegraf-configs/), do the following:
+    - Set the following environment variables:
+      - INFLUX_TOKEN: Token must have permissions to read Telegraf configurations and write data to the `telegraf` bucket. See how to [view tokens](/influxdb/v2.2/security/tokens/view-tokens/).
+      - INFLUX_ORG: Name of your organization. See how to [view your organization](/influxdb/v2.2/organizations/view-orgs/).
+      - INFLUX_HOST: Your InfluxDB host URL, for example, localhost, a remote instance, or InfluxDB Cloud.
+      - INFLUX_BUCKET: Bucket to store data in. To use the bucket included, you must export the variable: `export INFLUX_BUCKET=vsphere`
+4.    - Set the host address to the vSphere and provide the `username` and `password` as variables:
+        ```sh
+        vcenters = [ "https://$VSPHERE_HOST/sdk" ]
+        username = "$vsphere-user"
+        password = "$vsphere-password"
+        ```
+
+4. [Start Telegraf](/influxdb/v2.2/write-data/no-code/use-telegraf/auto-config/#start-telegraf).
+
+## View incoming data
+
+1. In the InfluxDB user interface (UI), select **Dashboards** in the left navigation.
+
+    {{< nav-icon "dashboards" >}}
+
+2. Open the **vsphere** dashboard to start monitoring.
diff --git a/content/influxdb/v2.2/monitor-alert/templates/infrastructure/windows.md b/content/influxdb/v2.2/monitor-alert/templates/infrastructure/windows.md
new file mode 100644
index 000000000..b1677a889
--- /dev/null
+++ b/content/influxdb/v2.2/monitor-alert/templates/infrastructure/windows.md
@@ -0,0 +1,55 @@
+---
+title: Monitor Windows
+description: >
+  Use the [Windows System Monitoring template](https://github.com/influxdata/community-templates/tree/master/windows_system) to monitor your Windows system.
+menu:
+  influxdb_2_2:
+    parent: Monitor infrastructure
+    name: Windows
+weight: 207
+---
+
+Use the [Windows System Monitoring template](https://github.com/influxdata/community-templates/tree/master/windows_system) to monitor your Windows system. First, [apply the template](#apply-the-template), and then [view incoming data](#view-incoming-data).
+
+The Windows System Monitoring template includes the following:
+
+- one [dashboard](/influxdb/v2.2/reference/glossary/#dashboard): **Windows System**
+- one [bucket](/influxdb/v2.2/reference/glossary/#bucket): `telegraf`, 7d retention
+- label: `Windows System Template`, Telegraf plugin labels: `outputs.influxdb_v2`
+- one [Telegraf configuration](/influxdb/v2.2/telegraf-configs/): InfluxDB v2 output plugin, Windows Performance Counters input plugin
+- two variables: `bucket`, `windows_host`
+
+## Apply the template
+
+1. Use the [`influx` CLI](/influxdb/v2.2/reference/cli/influx/) to run the following command:
+
+    ```sh
+    influx apply -f https://raw.githubusercontent.com/influxdata/community-templates/master/windows_system/windows_system.yml
+    ```
+    For more information, see [influx apply](/influxdb/v2.2/reference/cli/influx/apply/).
+
+    {{% note %}}
+Ensure your `influx` CLI is configured with your account credentials and that configuration is active. For more information, see [influx config](/influxdb/v2.2/reference/cli/influx/config/).
+    {{% /note %}}
+
+2. [Install Telegraf](/{{< latest "telegraf" >}}/introduction/installation/) on a server with network access to both the Windows system and [InfluxDB v2 API](/influxdb/v2.2/reference/api/).
+3. In your [Telegraf configuration file (`telegraf.conf`)](/influxdb/v2.2/telegraf-configs/), do the following:
+    - Set the following environment variables:
+      - INFLUX_TOKEN: Token must have permissions to read Telegraf configurations and write data to the `telegraf` bucket. See how to [view tokens](/influxdb/v2.2/security/tokens/view-tokens/).
+      - INFLUX_ORG: Name of your organization. See how to [view your organization](/influxdb/v2.2/organizations/view-orgs/).
+      - INFLUX_URL: Your InfluxDB host URL, for example, localhost, a remote instance, or InfluxDB Cloud.
+
+4. [Start Telegraf](/influxdb/v2.2/write-data/no-code/use-telegraf/auto-config/#start-telegraf).
+5. To monitor multiple Windows systems, repeat steps 1-4 for each system.
+
+## View incoming data
+
+1. In the InfluxDB user interface (UI), select **Dashboards** in the left navigation.
+
+    {{< nav-icon "dashboards" >}}
+
+2. Open the **Windows System** dashboard to start monitoring.
+
+   {{% note %}}
+   If you're monitoring multiple Windows machines, switch between them using the `windows_host` filter at the top of the dashboard.
+   {{% /note %}}
diff --git a/content/influxdb/v2.2/monitor-alert/templates/monitor.md b/content/influxdb/v2.2/monitor-alert/templates/monitor.md
new file mode 100644
index 000000000..666290f8e
--- /dev/null
+++ b/content/influxdb/v2.2/monitor-alert/templates/monitor.md
@@ -0,0 +1,175 @@
+---
+title: Monitor InfluxDB OSS using a template
+description: >
+  Monitor your InfluxDB OSS instance using InfluxDB Cloud and
+  a pre-built InfluxDB template.
+menu:
+  influxdb_2_2:
+    parent: Monitor with templates
+    name: Monitor InfluxDB OSS
+weight: 102
+influxdb/v2.2/tags: [templates, monitor]
+aliases:
+  - /influxdb/v2.2/influxdb-templates/monitor/
+related:
+  - /influxdb/v2.2/reference/cli/influx/apply/
+  - /influxdb/v2.2/reference/cli/influx/template/
+---
+
+Use [InfluxDB Cloud](/influxdb/cloud/), the [InfluxDB Open Source (OSS) Metrics template](https://github.com/influxdata/community-templates/tree/master/influxdb2_oss_metrics),
+and [Telegraf](/{{< latest "telegraf" >}}/) to monitor one or more InfluxDB OSS instances.
+
+Do the following:
+
+1. [Review requirements](#review-requirements)
+2. [Install the InfluxDB OSS Monitoring template](#install-the-influxdb-oss-monitoring-template)
+3. [Set up InfluxDB OSS for monitoring](#set-up-influxdb-oss-for-monitoring)
+4. [Set up Telegraf](#set-up-telegraf)
+5. [View the Monitoring dashboard](#view-the-monitoring-dashboard)
+6. (Optional) [Alert when metrics stop reporting](#alert-when-metrics-stop-reporting)
+7. (Optional) [Create a notification endpoint and rule](#create-a-notification-endpoint-and-rule)
+
+## Review requirements
+
+Before you begin, make sure you have access to the following:
+
+- InfluxDB Cloud account ([sign up for free here](https://cloud2.influxdata.com/signup))
+- Command line access to a machine [running InfluxDB OSS 2.x](/influxdb/v2.2/install/) and permissions to install Telegraf on this machine
+- Internet connectivity from the machine running InfluxDB OSS 2.x and Telegraf to InfluxDB Cloud
+- Sufficient resource availability to install the template (InfluxDB Cloud Free
+  Plan accounts include [resource limits](/influxdb/cloud/account-management/pricing-plans/#resource-limits/influxdb/cloud/account-management/pricing-plans/#resource-limits))
+
+## Install the InfluxDB OSS Monitoring template
+
+The InfluxDB OSS Monitoring template includes a Telegraf configuration that sends
+InfluxDB OSS metrics to an InfluxDB endpoint and a dashboard that visualizes the metrics.
+
+1.  [Log into your InfluxDB Cloud account](https://cloud2.influxdata.com/).
+2.  Go to **Settings > Templates** in the navigation bar on the left
+
+    {{< nav-icon "Settings" >}}
+
+3.  Under **Paste the URL of the Template's resource manifest file**, enter the
+    following template URL:
+
+    ```
+    https://raw.githubusercontent.com/influxdata/community-templates/master/influxdb2_oss_metrics/influxdb2_oss_metrics.yml
+    ```
+
+4.  Click **{{< caps >}}Lookup Template{{< /caps >}}**, and then click **{{< caps >}}Install Template{{< /caps >}}**.
+    InfluxDB Cloud imports the template, which includes the following resources:
+
+    - Dashboard `InfluxDB OSS Metrics`
+    - Telegraf configuration `scrape-influxdb-oss-telegraf`
+    - Bucket `oss_metrics`
+    - Check `InfluxDB OSS Deadman`
+    - Labels `influxdb2` and `prometheus`
+
+## Set up InfluxDB OSS for monitoring
+
+By default, InfluxDB OSS 2.x has a `/metrics` endpoint available, which exports 
+internal InfluxDB metrics in [Prometheus format](https://prometheus.io/docs/concepts/data_model/).
+
+1. Ensure the `/metrics` endpoint is [enabled](/{{< latest "influxdb" >}}/reference/config-options/#metrics-disabled).
+   If you've changed the default settings to disable the `/metrics` endpoint,
+   [re-enable these settings](/{{< latest "influxdb" >}}/reference/config-options/#metrics-disabled).
+2. Navigate to the `/metrics` endpoint of your InfluxDB OSS instance to view the InfluxDB OSS system metrics in your browser: 
+
+## Set up Telegraf
+
+Set up Telegraf to scrape metrics from InfluxDB OSS to send to your InfluxDB Cloud account.
+
+On each InfluxDB OSS instance you want to monitor, do the following:
+
+1. [Install Telegraf](/{{< latest "telegraf" >}}/introduction/installation/).
+2. Set the following environment variables in your Telegraf environment:
+    
+    - `INFLUX_URL`: Your [InfluxDB Cloud region URL](/influxdb/cloud/reference/regions/)
+    - `INFLUX_ORG`: Your InfluxDB Cloud organization name
+
+1. [In the InfluxDB Cloud UI](https://cloud2.influxdata.com/), go to **Load Data > Telegraf** in the left navigation.
+
+    {{< nav-icon "load-data" >}}
+
+2. Click **Setup Instructions** under **Scrape InfluxDB OSS Metrics**. 
+3. Complete the Telegraf Setup instructions to start Telegraf using the Scrape InfluxDB OSS Metrics
+   Telegraf configuration stored in InfluxDB Cloud.
+
+      {{% note %}}
+For your API token, generate a new token or use an existing All Access token. If you run Telegraf as a service, edit your init script to set the environment variable and ensure its available to the service.
+      {{% /note %}}
+
+Telegraf runs quietly in the background (no immediate output appears), and begins
+pushing metrics to the `oss_metrics` bucket in your InfluxDB Cloud account.
+
+## View the Monitoring dashboard
+
+To see your data in real time, view the Monitoring dashboard.
+
+1. Select **Dashboards** in your **InfluxDB Cloud** account.
+
+    {{< nav-icon "dashboards" >}}
+
+2. Click **InfluxDB OSS Metrics**. Metrics appear in your dashboard.
+3. Customize your monitoring dashboard as needed. For example, send an alert in the following cases:
+   - Users create a new task or bucket
+   - You're testing machine limits
+   - [Metrics stop reporting](#alert-when-metrics-stop-reporting)
+
+## Alert when metrics stop reporting
+
+The Monitoring template includes a [deadman check](/influxdb/cloud/monitor-alert/checks/create/#deadman-check) to verify metrics are reported at regular intervals.
+
+To alert when data stops flowing from InfluxDB OSS instances to your InfluxDB Cloud account, do the following:
+
+1. [Customize the deadman check](#customize-the-deadman-check) to identify the fields you want to monitor.
+2. [Create a notification endpoint and rule](#create-a-notification-endpoint-and-rule) to receive notifications when your deadman check is triggered.
+
+### Customize the deadman check
+
+1.  To view the deadman check, click **Alerts** in the navigation bar of your **InfluxDB Cloud** account.
+
+    {{< nav-icon "alerts" >}}
+
+2. Choose a InfluxDB OSS field or create a new OSS field for your deadman alert:
+    1.  Click **{{< caps >}}{{< icon "plus" >}} Create{{< /caps >}}** and select **Deadman Check** in the dropdown menu.
+    2.  Define your query with at least one field.
+    3.  Click **{{< caps >}}Submit{{< /caps >}}** and **{{< caps >}}Configure Check{{< /caps >}}**.
+        When metrics stop reporting, you'll receive an alert.
+3. Start under **Schedule Every**, set the amount of time to check for data.
+4. Set the amount of time to wait before switching to a critical alert.
+5. Click **{{< icon "check" >}}** to save the check.
+
+## Create a notification endpoint and rule
+
+To receive a notification message when your deadman check is triggered, create a [notification endpoint](#create-a-notification-endpoint) and [rule](#create-a-notification-rule). 
+
+### Create a notification endpoint 
+
+InfluxData supports different endpoints: Slack, PagerDuty, and HTTP. Slack is free for all users, while PagerDuty and HTTP are exclusive to the Usage-Based Plan. 
+
+#### Send a notification to Slack
+
+1.  Create a [Slack Webhooks](https://api.slack.com/messaging/webhooks). 
+2.  Go to **Alerts > Alerts** in the left navigation menu and then click **{{< caps >}}Notification Endpoints{{< /caps >}}**.
+
+    {{< nav-icon "alerts" >}}
+
+4.  Click **{{< caps >}}{{< icon "plus" >}} Create{{< /caps >}}**, and enter a name and description for your Slack endpoint. 
+3.  Enter your Slack Webhook under **Incoming Webhook URL** and click **{{< caps >}}Create Notification Endpoint{{< /caps >}}**. 
+
+#### Send a notification to PagerDuty or HTTP 
+
+Send a notification to PagerDuty or HTTP endpoints (other webhooks) by [upgrading your InfluxDB Cloud account](/influxdb/cloud/account-management/billing/#upgrade-to-usage-based-plan).
+
+### Create a notification rule 
+
+[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 > Alerts** in the left navigation menu and then click **{{< caps >}}Notification Rules{{< /caps >}}**.
+
+    {{< nav-icon "alerts" >}}
+
+4.  Click **{{< caps >}}{{< icon "plus" >}} Create{{< /caps >}}**, and then provide
+    the required information. 
+3.  Click **{{< caps >}}Create Notification Rule{{< /caps >}}**. 
diff --git a/content/influxdb/v2.2/monitor-alert/templates/networks/_index.md b/content/influxdb/v2.2/monitor-alert/templates/networks/_index.md
new file mode 100644
index 000000000..9f0f23b04
--- /dev/null
+++ b/content/influxdb/v2.2/monitor-alert/templates/networks/_index.md
@@ -0,0 +1,14 @@
+---
+title: Monitor networks
+description: >
+  Use one of our community templates to quickly set up InfluxDB (with a bucket and dashboard) to collect, analyze, and monitor your networks.
+menu:
+  influxdb_2_2:
+    parent: Monitor with templates
+weight: 104
+influxdb/v2.2/tags: [monitor, templates, networks, networking]
+---
+
+Use one of our community templates to quickly set up InfluxDB (with a bucket and dashboard) to collect, analyze, and monitor your networks.
+
+{{< children >}}
\ No newline at end of file
diff --git a/content/influxdb/v2.2/monitor-alert/templates/networks/haproxy.md b/content/influxdb/v2.2/monitor-alert/templates/networks/haproxy.md
new file mode 100644
index 000000000..3b7d359ce
--- /dev/null
+++ b/content/influxdb/v2.2/monitor-alert/templates/networks/haproxy.md
@@ -0,0 +1,49 @@
+---
+title: Monitor HAProxy
+description: >
+  Use the [HAProxy for InfluxDB v2 template](https://github.com/influxdata/community-templates/tree/master/haproxy) to monitor your HAProxy instance.
+menu:
+  influxdb_2_2:
+    parent: Monitor networks
+    name: HAproxy
+weight: 201
+---
+
+Use the [HAProxy for InfluxDB v2 template](https://github.com/influxdata/community-templates/tree/master/haproxy) to monitor your HAProxy instances. First, [apply the template](#apply-the-template), and then [view incoming data](#view-incoming-data).
+This template uses the [HAProxy input plugin](/{{< latest "telegraf" >}}/plugins//#haproxy) to collect metrics stored in an HAProxy instance and display these metrics in a dashboard.
+
+The HAProxy for InfluxDB v2 template includes the following:
+
+- one [dashboard](/influxdb/v2.2/reference/glossary/#dashboard): **HAProxy**
+- one [bucket](/influxdb/v2.2/reference/glossary/#bucket): `haproxy`
+- label: `haproxy`
+- one [Telegraf configuration](/influxdb/v2.2/telegraf-configs/): HAProxy input plugin, InfluxDB v2 output plugin
+- one variable: `bucket`
+
+## Apply the template
+
+1. Use the [`influx` CLI](/influxdb/v2.2/reference/cli/influx/) to run the following command:
+
+    ```sh
+    influx apply -f https://raw.githubusercontent.com/influxdata/community-templates/master/haproxy/haproxy.yml
+    ```
+    For more information, see [influx apply](/influxdb/v2.2/reference/cli/influx/apply/).
+
+    > **Note:** Ensure your `influx` CLI is configured with your account credentials and that configuration is active. For more information, see [influx config](/influxdb/v2.2/reference/cli/influx/config/).
+
+2. [Install Telegraf](/{{< latest "telegraf" >}}/introduction/installation/) on a server with network access to both the HAProxy instances and [InfluxDB v2 API](/influxdb/v2.2/reference/api/).
+3. In your [Telegraf configuration file (`telegraf.conf`)](/influxdb/v2.2/telegraf-configs/), do the following:
+    - Set the following environment variables:
+      - INFLUX_TOKEN: Token must have permissions to read Telegraf configurations and write data to the `haproxy` bucket. See how to [view tokens](/influxdb/v2.2/security/tokens/view-tokens/).
+      - INFLUX_ORG: Name of your organization. See how to [view your organization](/influxdb/v2.2/organizations/view-orgs/).
+      - INFLUX_HOST: Your InfluxDB host URL, for example, localhost, a remote instance, or InfluxDB Cloud.
+
+4. [Start Telegraf](/influxdb/v2.2/write-data/no-code/use-telegraf/auto-config/#start-telegraf).
+
+## View incoming data
+
+1. In the InfluxDB user interface (UI), select **Dashboards** in the left navigation.
+
+    {{< nav-icon "dashboards" >}}
+    
+2. Open the **HAProxy** dashboard to start monitoring.
diff --git a/content/influxdb/v2.2/notebooks/_index.md b/content/influxdb/v2.2/notebooks/_index.md
new file mode 100644
index 000000000..ec9959719
--- /dev/null
+++ b/content/influxdb/v2.2/notebooks/_index.md
@@ -0,0 +1,17 @@
+---
+title: Notebooks
+seotitle: Build notebooks in InfluxDB Cloud
+description: >
+  Use notebooks to build and annotate processes and data flows for time series data.
+menu:
+  influxdb_2_2:
+    name: Notebooks
+weight: 6
+influxdb/v2.2/tags: [notebooks]
+---
+
+Notebooks are a way to build and annotate processes and data flows for time series data. Notebooks include cells and controls to transform the data in your bucket and other countless possibilities.
+
+To learn how to use notebooks, check out the following articles:
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/notebooks/clean-data.md b/content/influxdb/v2.2/notebooks/clean-data.md
new file mode 100644
index 000000000..9856f5f15
--- /dev/null
+++ b/content/influxdb/v2.2/notebooks/clean-data.md
@@ -0,0 +1,163 @@
+---
+title: Normalize data with notebooks
+description: >
+  Learn how to create a notebook that normalizes or cleans data to make it
+  easier to work with.
+weight: 105
+influxdb/v2.2/tags: [notebooks]
+menu:
+  influxdb_2_2:
+    name: Normalize data
+    parent: Notebooks
+---
+
+Learn how to create a notebook that normalizes data.
+Data normalization is the process of modifying or cleaning data to make it easier to
+work with. Examples include adjusting numeric values to a uniform scale and modifying strings.
+
+Walk through the following example to create a notebook that queries
+[NOAA NDBC sample data](/influxdb/v2.0/reference/sample-data/#noaa-ndbc-data),
+normalizes degree-based wind directions to cardinal directions, and then writes
+the normalized data to a bucket.
+
+{{< cloud-only >}}  
+{{% cloud %}}  
+**Note**: Using sample data counts towards your total InfluxDB Cloud usage.
+{{% /cloud %}}  
+{{< /cloud-only >}}
+
+1.  [Create a new notebook](/influxdb/v2.2/notebooks/create-notebook/).
+2.  In the **Build a Query** cell:
+
+    1.  In the **FROM** column under **{{% caps %}}Sample{{% /caps %}}**,
+        select **NOAA National Buoy Data**.
+    2.  In the next **FILTER** column, select **_measurement** from the drop-down list
+        and select the **ndbc** measurement in the list of measurements.
+    3.  In the next **FILTER** column, select **_field** from the drop-down list,
+        and select the **wind\_dir\_degt** field from the list of fields.
+
+3.  Click {{% icon "notebook-add-cell" %}} after your **Build a Query** cell to 
+    add a new cell and select **{{% caps %}}Flux Script{{% /caps %}}**.
+    
+4.  In the Flux script cell:
+    
+    1.  Define a custom function (`cardinalDir()`) that converts a numeric degree
+        value to a cardinal direction (N, NNE, NE, etc.).
+    2.  Use `__PREVIOUS_RESULT__` to load the output of the previous notebook
+        cell into the Flux script.
+    3.  Use [`map()`](/{{< latest "flux" >}}/stdlib/universe/map/) to iterate
+        over each input row, update the field key to `wind_dir_cardinal`, and
+        normalize the `_value` column to a cardinal direction using the custom
+        `cardinalDir()` function.
+    4.  {{% cloud-only %}}
+        
+        Use [`to()`](/{{< latest "flux">}}/stdlib/influxdata/influxdb/to/)
+        to write the normalized data back to InfluxDB.
+        Specify an existing bucket to write to or
+        [create a new bucket](/influxdb/v2.2/organizations/buckets/create-bucket/).
+
+        {{% /cloud-only %}}
+    
+    {{% oss-only %}}
+
+    ```js
+    import "array"
+
+    cardinalDir = (d) => {
+        _cardinal = if d >= 348.7 or d < 11.25 then "N"
+        else if d >= 11.25 and d < 33.75 then "NNE"
+        else if d >= 33.75 and d < 56.25 then "NE"
+        else if d >= 56.25 and d < 78.75 then "ENE"
+        else if d >= 78.75 and d < 101.25 then "E"
+        else if d >= 101.25 and d < 123.75 then "ESE"
+        else if d >= 123.75 and d < 146.25 then "SE"
+        else if d >= 146.25 and d < 168.75 then "SSE"
+        else if d >= 168.75 and d < 191.25 then "S"
+        else if d >= 191.25 and d < 213.75 then "SSW"
+        else if d >= 213.75 and d < 236.25 then "SW"
+        else if d >= 236.25 and d < 258.75 then "WSW"
+        else if d >= 258.75 and d < 281.25 then "W"
+        else if d >= 281.25 and d < 303.75 then "WNW"
+        else if d >= 303.75 and d < 326.25 then "NW"
+        else if d >= 326.25 and d < 348.75 then "NNW"
+        else ""
+
+        return _cardinal
+    }
+
+    __PREVIOUS_RESULT__
+        |> map(fn: (r) => ({r with
+            _field: "wind_dir_cardinal",
+            _value: cardinalDir(d: r._value),
+        }))
+    ```
+    {{% /oss-only %}}
+
+    {{% cloud-only %}}
+
+    ```js
+    import "array"
+
+    cardinalDir = (d) => {
+        _cardinal = if d >= 348.7 or d < 11.25 then "N"
+        else if d >= 11.25 and d < 33.75 then "NNE"
+        else if d >= 33.75 and d < 56.25 then "NE"
+        else if d >= 56.25 and d < 78.75 then "ENE"
+        else if d >= 78.75 and d < 101.25 then "E"
+        else if d >= 101.25 and d < 123.75 then "ESE"
+        else if d >= 123.75 and d < 146.25 then "SE"
+        else if d >= 146.25 and d < 168.75 then "SSE"
+        else if d >= 168.75 and d < 191.25 then "S"
+        else if d >= 191.25 and d < 213.75 then "SSW"
+        else if d >= 213.75 and d < 236.25 then "SW"
+        else if d >= 236.25 and d < 258.75 then "WSW"
+        else if d >= 258.75 and d < 281.25 then "W"
+        else if d >= 281.25 and d < 303.75 then "WNW"
+        else if d >= 303.75 and d < 326.25 then "NW"
+        else if d >= 326.25 and d < 348.75 then "NNW"
+        else ""
+
+        return _cardinal
+    }
+
+    __PREVIOUS_RESULT__
+        |> map(fn: (r) => ({r with
+            _field: "wind_dir_cardinal",
+            _value: cardinalDir(d: r._value),
+        }))
+        |> to(bucket: "example-bucket")
+    ```
+    {{% /cloud-only %}}
+
+4.  {{% oss-only %}}
+    
+    Click {{% icon "notebook-add-cell" %}} after your **Flux Script** cell to 
+    add a new cell and select **{{% caps %}}Output to Bucket{{% /caps %}}**.
+    Select a bucket from the **{{% icon "bucket" %}} Choose a bucket**
+    drop-down list. 
+
+    {{% /oss-only %}}
+    
+5.  _(Optional)_ Click {{% icon "notebook-add-cell" %}} and select **Note** to
+    add a cell containing notes about what this notebook does. For example, the
+    cell might say, "This notebook converts decimal degree wind direction values
+    to cardinal directions."
+6.  {{% oss-only %}}
+
+    Click **Preview** in the upper left to verify that your notebook runs and previews the output.
+    
+    {{% /oss-only %}}
+6.  Click **Run** to run the notebook and write the normalized data to your bucket.
+
+## Continuously run a notebook
+To continuously run your notebook, export the notebook as a task:
+
+1.  Click {{% icon "notebook-add-cell" %}} to add a new cell and then select
+    **{{% caps %}}Task{{% /caps %}}**.
+2.  Provide the following:
+
+    - **Every**: Interval that the task should run at.
+    - **Offset**: _(Optional)_ Time to wait after the defined interval to execute the task.
+      This allows the task to capture late-arriving data.
+
+3.  Click **{{% icon "export" %}} Export as Task**.
diff --git a/content/influxdb/v2.2/notebooks/create-notebook.md b/content/influxdb/v2.2/notebooks/create-notebook.md
new file mode 100644
index 000000000..868fdd797
--- /dev/null
+++ b/content/influxdb/v2.2/notebooks/create-notebook.md
@@ -0,0 +1,180 @@
+---
+title: Create a notebook
+description: >
+  Create a notebook to explore, visualize, and process your data.
+weight: 102
+influxdb/v2.2/tags: [notebooks]
+menu:
+  influxdb_2_2:
+    name: Create a notebook
+    parent: Notebooks
+---
+
+Create a notebook to explore, visualize, and process your data.
+Learn how to add and configure cells to customize your notebook.
+To learn the benefits and concepts of notebooks, see [Overview of Notebooks](/influxdb/v2.2/notebooks/overview/).
+
+- [Create a notebook from a preset](#create-a-notebook-from-a-preset)
+- [Use data source cells](#use-data-source-cells)
+- [Use visualization cells](#use-visualization-cells)
+- [Add a data source cell](#add-a-data-source-cell)
+- [Add a validation cell](#add-a-validation-cell)
+- [Add a visualization cell](#add-a-visualization-cell)
+
+## Create a notebook from a preset
+
+To create a new notebook, do the following:
+
+1. In the navigation menu on the left, click **Notebooks**.
+
+    {{< nav-icon "notebooks" >}}
+2. In the **Notebooks** page, select one of the following options under **Create a Notebook**:
+    - **New Notebook**: includes a [query builder cell](#add-a-data-source-cell), a [validation cell](#add-a-validation-cell), and a [visualization cell](#add-a-visualization-cell).
+    - **Set an Alert**: includes a [query builder cell](#add-a-data-source-cell), a [validation cell](#add-a-validation-cell), a [visualization cell](#add-a-visualization-cell), and an [alert builder cell](#add-an-action-cell).
+    - **Schedule a Task**: includes a [Flux Script editor cell](#add-a-data-source-cell), a [validation cell](#add-a-validation-cell), and a [task schedule cell](#add-an-action-cell).
+    - **Write a Flux Script**: includes a [Flux script editor cell](#add-a-data-source-cell), and a [validation cell](#add-a-validation-cell).
+
+3.  Enter a name for your notebook in the **Untitled Notebook** field.
+4. Do the following at the top of the page:
+   - Select your local time zone or UTC.
+   - Choose a time [range](/{{% latest "flux" %}}/stdlib/universe/range/) for your data.
+5. Your notebook should have a **Data Source** cell as the first cell. **Data Source** cells provide data to subsequent cells. The presets (listed in step 2) include either a **Query Builder** or a **Flux Script** as the first cell.
+6. To define your data source query, do one of the following:
+   - If your notebook uses a **Query Builder** cell, select your bucket and any additional filters for your query.
+   - If your notebook uses a **Flux Script** cell, enter or paste a [Flux script](/influxdb/v2.2/query-data/flux/).
+7. {{% oss-only %}}
+
+    Select and click **Preview** (or press **CTRL + Enter**) under the notebook title.
+    InfluxDB displays query results in **Validate the Data** and **Visualize the Result** *without writing data or
+    running actions*.
+
+    {{% /oss-only %}}
+8. (Optional) Change your visualization settings with the drop-down menu and the {{< icon "gear" >}} **Configure** button at the top of the **Visualize the Result** cell.
+9. (Optional) Toggle the **Presentation** switch to display visualization cells and hide all other cells.
+10. (Optional) Configure notebook actions {{% oss-only %}}(**Alert**, **Task**, or **Output to Bucket**){{% /oss-only %}}{{% cloud-only %}}(**Alert** or **Task**){{% /cloud-only %}}.
+11. (Optional) To run your notebook actions, select and click **Run** under the notebook title.
+12. (Optional) To add a new cell, follow the steps for one of the cell types:
+
+    - [Add a data source cell](#add-a-data-source-cell)
+    - [Add a validation cell](#add-a-validation-cell)
+    - [Add a visualization cell](#add-a-visualization-cell)
+    - [Add an action cell](#add-an-action-cell)
+13. (Optional) [Convert a query builder cell into raw Flux script](#convert-a-query-builder-to-flux) to view and edit the code.
+
+## Use Data Source cells
+
+### Convert a Query Builder to Flux
+To edit the raw Flux script of a **Query Builder** cell, convert the cell to Flux.
+
+{{% warn %}}
+You can't convert a **Flux Script** editor cell to a **Query Builder** cell.
+Once you convert a **Query Builder** cell to a **Flux Script** editor cell, you can't convert it back.
+{{% /warn %}}
+
+1. Click the {{% icon "more" %}} icon in the **Query Builder** cell you want to edit as Flux, and then select **Convert to |> Flux**.
+You won't be able to undo this step.
+
+   A **Flux Script** editor cell containing the raw Flux script replaces the **Query Builder** cell.
+
+2. View and edit the Flux script as needed.
+
+## Use visualization cells
+
+- To change your [visualization type](/influxdb/v2.2/visualize-data/visualization-types/), select a new type from the drop-down list at the top of the cell.
+- (For histogram only) To specify values, click **Select**.
+- To configure the visualization, click **Configure**.
+- To download results as an annotated CSV file, click the **CSV** button.
+- To export to the dashboard, click **Export to Dashboard**.
+
+## Add a data source cell
+
+Add a [data source cell](/influxdb/v2.2/notebooks/overview/#data-source) to pull information into your notebook.
+
+To add a data source cell, do the following:
+1. Click {{< icon "notebook-add-cell" >}}.
+2. Select **{{< caps >}}Flux Script{{< /caps >}}** or **{{< caps >}}Query Builder{{< /caps >}}** as your input, and then select or enter the bucket to pull data from.
+3. Select filters to narrow your data.
+4. Select {{% oss-only %}}**Preview** (**CTRL + Enter**) or {{% /oss-only %}}**Run** in the upper left drop-down list.
+
+## Add a validation cell
+
+A validation cell uses the **Table** [visualization type](/influxdb/v2.2/visualize-data/visualization-types/) to display query results from a data source cell.
+
+To add a **Table** visualization cell, do the following:
+
+1. Click {{< icon "notebook-add-cell" >}}.
+2. Under **Visualization**, click **{{< caps >}}Table{{< /caps >}}**.
+
+## Add a visualization cell
+
+Add a visualization cell to render query results as a [Visualization type](/influxdb/v2.2/visualize-data/visualization-types/).
+
+To add a Table visualization cell, do the following:
+
+1. Click {{< icon "notebook-add-cell" >}}.
+2. Under **Visualization**, select one of the following visualization cell-types:
+
+   - **{{< caps >}}Table{{< /caps >}}**: Display data in tabular format.
+   - **{{< caps >}}Graph{{< /caps >}}**: Visualize data using InfluxDB visualizations.
+   - **{{< caps >}}Note{{< /caps >}}**: Use Markdown to add notes or other information to your notebook.
+
+To modify a visualization cell, see [use visualization cells](#use-visualization-cells).
+For detail on available visualization types and how to use them, see [Visualization types](/influxdb/v2.2/visualize-data/visualization-types/).
+
+## Add an action cell
+
+Add an [action cell](/influxdb/v2.2/notebooks/overview/#action) to create an [alert](/influxdb/v2.2/monitor-alert/)
+{{% cloud-only %}}or{{% /cloud-only %}}{{% oss-only %}},{{% /oss-only %}} process data with a [task](/influxdb/v2.2/process-data/manage-tasks/)
+{{% oss-only %}}, or output data to a bucket{{% /oss-only %}}.
+
+{{% oss-only %}}
+
+{{% warn %}}
+If your cell contains a custom script that uses any output function to write data to InfluxDB (for example: the `to()` function) or sends data to a third-party service, clicking Preview will write data.
+{{% /warn %}}
+
+{{% /oss-only %}}
+
+- [Add an Alert cell](#add-an-alert-cell)
+- {{% oss-only %}}[Add an Output to Bucket cell](#add-an-output-to-bucket-cell){{% /oss-only %}}
+- [Add a Task cell](#add-a-task-cell)
+
+### Add an Alert cell
+
+To add an [alert](/influxdb/v2.2/monitor-alert/) to your notebook, do the following:
+
+1. Enter a time range to automatically check the data and enter your query offset.
+2. Customize the conditions to send an alert.
+3. Select an endpoint to receive an alert:
+   - Slack and a Slack Channel
+   - HTTP post
+   - PagerDuty
+4. (Optional) Personalize your message. By default, the message is:
+   ```
+   ${strings.title(v: r._type)} for ${r._source_measurement} triggered at ${time(v: r._source_timestamp)}!
+   ```
+5. Click **{{< caps >}}Test Alert{{< /caps >}}** to send a test message to your configured **Endpoint**. The test will not schedule the new alert.
+6. Click **{{< icon "export" >}} {{< caps >}}Export Alert Task{{< /caps >}}** to create your alert.
+
+{{% oss-only %}}
+
+### Add an Output to Bucket cell
+
+To write **Data Source** results to a bucket, do the following:
+
+1. Click {{% icon "notebook-add-cell" %}}.
+2. Click **{{< caps >}}Output to Bucket{{< /caps >}}**.
+3. In the **{{< icon "bucket" >}} Choose a bucket** drop-down list, select or create a bucket.
+4. Click **Preview** to view the query result in validation cells.
+5. Select and click **Run** in the upper left to write the query result to the bucket.
+
+{{% /oss-only %}}
+
+### Add a Task cell
+
+To add a [task](/influxdb/v2.2/process-data/manage-tasks/) to your notebook, do the following:
+
+1. Click {{% icon "notebook-add-cell" %}}.
+2. Click **{{< caps >}}Task{{< /caps >}}**.
+3. Enter a time and an offset to schedule the task.
+4. Click **{{< icon "task" >}} {{< caps >}}Export as Task{{< /caps >}}** to save.
diff --git a/content/influxdb/v2.2/notebooks/downsample.md b/content/influxdb/v2.2/notebooks/downsample.md
new file mode 100644
index 000000000..2eb24dbde
--- /dev/null
+++ b/content/influxdb/v2.2/notebooks/downsample.md
@@ -0,0 +1,111 @@
+---
+title: Downsample data with notebooks
+description: >
+  Create a notebook to downsample data. Downsampling aggregates or summarizes data
+  within specified time intervals, reducing the overall disk usage as data
+  collects over time.
+weight: 104
+influxdb/v2.2/tags: [notebooks]
+menu:
+  influxdb_2_2:
+    name: Downsample data
+    identifier: notebooks-downsample
+    parent: Notebooks
+---
+
+Create a notebook to downsample data. Downsampling aggregates or summarizes data
+within specified time intervals, reducing the overall disk usage as data
+collects over time.
+
+The following example creates a notebook that queries **Coinbase bitcoin price
+sample data** from the last hour, downsamples the data into ten minute summaries,
+and then writes the downsampled data to an InfluxDB bucket.
+
+1.  If you do not have an existing bucket to write the downsampled data to,
+    [create a new bucket](/influxdb/v2.2/organizations/buckets/create-bucket/).
+2.  [Create a new notebook](/influxdb/v2.2/notebooks/create-notebook/).
+3.  Select **Past 1h** from the time range drop-down list at the top of your notebook.
+4.  In the **Build a Query** cell:
+
+    1.  In the **FROM** column under **{{% caps %}}Sample{{% /caps %}}**,
+        select **Coinbase bitcoin price**.
+    2.  In the next **FILTER** column, select **_measurement** from the drop-down list
+        and select the **coindesk** measurement in the list of measurements.
+    3.  In the next **FILTER** column, select **_field** from the drop-down list,
+        and select the **price** field from the list of fields.
+    4.  In the next **FILTER** column, select **code** from the drop-down list,
+        and select a currency code.
+
+5.  Click {{% icon "notebook-add-cell" %}} after your **Build a Query** cell to 
+    add a new cell and select **{{% caps %}}Flux Script{{% /caps %}}**.
+
+6.  In the Flux script cell:
+    
+    1.  Use `__PREVIOUS_RESULT__` to load the output of the previous notebook
+        cell into the Flux script.
+    2.  Use [`aggregateWindow()`](/{{< latest "flux" >}}/stdlib/universe/aggregatewindow/)
+        to window data into ten minute intervals and return the average of each interval.
+        Specify the following parameters:
+
+        - **every**: Window interval _(should be less than or equal to the duration of the queried time range)_.
+          For this example, use `10m`.
+        - **fn**: [Aggregate](/{{< latest "flux" >}}/function-types/#aggregates)
+          or [selector](/{{< latest "flux" >}}/function-types/#selectors) function
+          to apply to each window.
+          For this example, use `mean`.
+
+    3.  {{% cloud-only %}}
+        
+        Use [`to()`](/{{< latest "flux">}}/stdlib/influxdata/influxdb/to/)
+        to write the downsampled data back to an InfluxDB bucket.
+
+        {{% /cloud-only %}}
+    
+    {{% oss-only %}}
+
+    ```js
+    __PREVIOUS_RESULT__
+        |> aggregateWindow(every: 10m, fn: mean)
+    ```
+    {{% /oss-only %}}
+
+    {{% cloud-only %}}
+
+    ```js
+    __PREVIOUS_RESULT__
+        |> aggregateWindow(every: 10m, fn: mean)
+        |> to(bucket: "example-bucket")
+    ```
+    {{% /cloud-only %}}
+
+7.  {{% oss-only %}}
+    
+    Click {{% icon "notebook-add-cell" %}} after your **Flux Script** cell to 
+    add a new cell and select **{{% caps %}}Output to Bucket{{% /caps %}}**.
+    Select a bucket from the **{{% icon "bucket" %}} Choose a bucket**
+    drop-down list. 
+
+    {{% /oss-only %}}
+    
+8.  _(Optional)_ Click {{% icon "notebook-add-cell" %}} and select **Note** to
+    add a note to describe your notebook, for example, 
+ "Downsample Coinbase bitcoin prices into hourly averages."
+9.  {{% oss-only %}}
+
+    Click **Preview** in the upper left to verify that your notebook runs and displays the output.
+    
+    {{% /oss-only %}}
+10. Click **Run** to run the notebook and write the downsampled data to your bucket.
+
+## Continuously run a notebook
+To continuously run your notebook, export the notebook as a task:
+
+1.  Click {{% icon "notebook-add-cell" %}} to add a new cell, and then select
+    **{{% caps %}}Task{{% /caps %}}**.
+2.  Provide the following:
+
+    - **Every**: Interval that the task should run at.
+    - **Offset**: _(Optional)_ Time to wait after the defined interval to execute the task.
+      This allows the task to capture late-arriving data.
+
+3.  Click **{{% icon "export" %}} Export as Task**.
diff --git a/content/influxdb/v2.2/notebooks/manage-notebooks.md b/content/influxdb/v2.2/notebooks/manage-notebooks.md
new file mode 100644
index 000000000..b440fe4c0
--- /dev/null
+++ b/content/influxdb/v2.2/notebooks/manage-notebooks.md
@@ -0,0 +1,56 @@
+---
+title: Manage notebooks
+description: View, update, and delete notebooks.
+weight: 103
+influxdb/v2.2/tags: [notebooks]
+menu:
+  influxdb_2_2:
+    name: Manage notebooks
+    parent: Notebooks
+---
+
+Manage your notebooks in the UI:
+
+- [View or update a notebook](#view-or-update-notebooks)
+- {{% cloud-only %}}[Share a notebook](#share-a-notebook){{% /cloud-only %}}
+- {{% cloud-only %}}[Unshare a notebook](#unshare-a-notebook){{% /cloud-only %}}
+- [Delete a notebook](#delete-a-notebook)
+
+## View or update notebooks
+
+1. In the navigation menu on the left, click **Notebooks**.
+
+    {{< nav-icon "notebooks" >}}
+
+    A list of notebooks appears.
+2. Click a notebook to open it.
+3. To update, edit the notebook's cells and content. Changes are saved automatically.
+
+{{% cloud-only %}}
+
+## Share a notebook
+
+1.  In the navigation menu on the left, click **Notebooks**.
+
+    {{< nav-icon "notebooks" >}}
+
+2.  Click the notebook to open it, and then click the **{{< icon "share" >}}** icon.
+3.  Select an API token with read-access to all resources in the notebook,
+    and then click the **{{< icon "check" >}}** icon.
+4.  Share the generated notebook URL as needed.
+
+## Unshare a notebook
+
+To stop sharing a notebook, select **{{< icon "trash" >}}** next to the shared notebook URL.
+
+{{% /cloud-only %}}
+
+## Delete a notebook
+
+1. In the navigation menu on the left, click **Notebooks**.
+
+    {{< nav-icon "notebooks" >}}
+
+2. Hover over a notebook in the list that appears.
+3. Click **Delete Notebook**.
+4. Click **Confirm**.
diff --git a/content/influxdb/v2.2/notebooks/overview.md b/content/influxdb/v2.2/notebooks/overview.md
new file mode 100644
index 000000000..506408ab7
--- /dev/null
+++ b/content/influxdb/v2.2/notebooks/overview.md
@@ -0,0 +1,97 @@
+---
+title: Overview of notebooks
+description: >
+  Learn about the building blocks of a notebook.
+weight: 101
+influxdb/v2.2/tags: [notebooks]
+menu:
+  influxdb_2_2:
+    name: Overview of notebooks
+    parent: Notebooks
+---
+
+Learn how notebooks can help to streamline and simplify your day-to-day business processes.
+
+See an overview of [notebook concepts](/influxdb/v2.2/notebooks/overview/#notebook-concepts), [notebook controls](/influxdb/v2.2/notebooks/overview/#notebook-controls), and [notebook cell types](/influxdb/v2.2/notebooks/overview/#notebook-cell-types) also know as the basic building blocks of a notebook.
+
+## Notebook concepts
+
+You can think of an InfluxDB notebook as a collection of sequential data processing steps. Each step is represented by a "cell" that performs an action such as querying, visualizing, processing, or writing data to your buckets. Notebooks help you do the following:
+
+- Create snippets of live code, equations, visualizations, and explanatory notes.
+- Create alerts or scheduled tasks.
+- Downsample and normalize data.
+- Build runbooks to share with your teams.
+- Output data to buckets.
+
+## Notebook controls
+
+The following options appear at the top of each notebook.
+
+{{% oss-only %}}
+
+### Preview/Run mode
+
+- Select **Preview** (or press **Control+Enter**) to display results of each cell without writing data. Helps to verify that cells return expected results before writing data.
+
+{{% /oss-only %}}
+
+{{% cloud-only %}}
+
+### Run
+
+Select {{< caps >}}Run{{< /caps >}} (or press **Control+Enter**) to display results of each cell and write data to the selected bucket.
+
+{{% /cloud-only %}}
+
+### Save Notebook (appears before first save)
+
+Select {{< caps >}}Save Notebook{{< /caps >}} to save all notebook cells. Once you've saved the notebook, this button disappears and the notebook automatically saves as subsequent changes are made.
+
+{{% note %}}
+Saving the notebook does not save cell results. When you open a saved notebook, click {{< caps >}}**Run**{{< /caps >}} to update cell results.
+{{% /note %}}
+
+### Local or UTC timezone
+
+Click the timezone drop-down list to select a timezone to use for the notebook. Select either the local time (default) or UTC.
+
+### Time range
+
+Select from the options in the dropdown list or select **Custom Time Range** to enter a custom time range with precision up to nanoseconds, and then click **{{< caps >}}Apply Time Range{{< /caps >}}**.
+
+{{% cloud-only %}}
+
+### Share notebook
+
+To generate a URL for the notebook, click the **{{< icon "share" >}}** icon.
+For more detail, see how to [share a notebook](/influxdb/cloud/notebooks/manage-notebooks/#share-a-notebook).
+
+{{% /cloud-only %}}
+
+## Notebook cell types
+
+The following cell types are available for your notebook:
+- [Data source](#data-source)
+- [Visualization](#visualization)
+- [Action](#action)
+
+### Data source
+
+At least one data source (input) cell is required in a notebook for other cells to run.
+
+- **{{< caps >}}Query Builder{{< /caps >}}**: Build a query with the Flux query builder.
+- **{{< caps >}}Flux Script{{< /caps >}}**: Enter a raw Flux script.
+
+  Data source cells work like the **Query Builder** or **Script Editor** in Data Explorer. For more information, see how to [query data with Flux and the Data Explorer](/influxdb/v2.2/query-data/execute-queries/data-explorer/#query-data-with-flux-and-the-data-explorer).
+
+### Visualization
+
+- **{{< caps >}}Table{{< /caps >}}**: View your data in a table.
+- **{{< caps >}}Graph{{< /caps >}}**: View your data in a graph.
+- **{{< caps >}}Note{{< /caps >}}**: Create explanatory notes or other information for yourself or your team members.
+
+### Action
+
+- **{{< caps >}}Alert{{< /caps >}}**: Set up alerts. See how to [monitor data and send alerts](/influxdb/v2.2/monitor-alert/).
+- **{{< caps >}}Tasks{{< /caps >}}**: Use the notebook to set up and export a task. See how to [manage tasks in InfluxDB](/influxdb/v2.2/process-data/manage-tasks/).
diff --git a/content/influxdb/v2.2/notebooks/troubleshoot-notebooks.md b/content/influxdb/v2.2/notebooks/troubleshoot-notebooks.md
new file mode 100644
index 000000000..112daca29
--- /dev/null
+++ b/content/influxdb/v2.2/notebooks/troubleshoot-notebooks.md
@@ -0,0 +1,14 @@
+---
+title: Troubleshoot notebooks
+description: Common issues with the notebooks feature.
+weight: 106
+influxdb/v2.2/tags: [notebooks]
+menu:
+  influxdb_2_2:
+    name: Troubleshoot notebooks
+    parent: Notebooks
+---
+
+### No measurements appear in my bucket even though there's data in it.
+
+Try changing the time range. You might have measurements prior to the time range you  selected. For example, if the selected time range is `Past 1h` and the last write happened 16 hours ago, you'd need to change the time range to `Past 24h` (or more) to see your data.
diff --git a/content/influxdb/v2.2/organizations/_index.md b/content/influxdb/v2.2/organizations/_index.md
new file mode 100644
index 000000000..d33017969
--- /dev/null
+++ b/content/influxdb/v2.2/organizations/_index.md
@@ -0,0 +1,17 @@
+---
+title: Manage organizations
+seotitle: Manage organizations in InfluxDB
+description: Manage organizations in InfluxDB using the InfluxDB UI or the influx CLI.
+menu:
+  influxdb_2_2:
+    name: Manage organizations
+weight: 10
+influxdb/v2.2/tags: [organizations]
+---
+
+An **organization** is a workspace for a group of users.
+All dashboards, tasks, buckets, members, etc., belong to an organization.
+
+The following articles provide information about managing organizations:
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/organizations/buckets/_index.md b/content/influxdb/v2.2/organizations/buckets/_index.md
new file mode 100644
index 000000000..cbcc82398
--- /dev/null
+++ b/content/influxdb/v2.2/organizations/buckets/_index.md
@@ -0,0 +1,20 @@
+---
+title: Manage buckets
+seotitle: Manage buckets in InfluxDB
+description: Manage buckets in InfluxDB using the InfluxDB UI or the influx CLI.
+menu:
+  influxdb_2_2:
+    name: Manage buckets
+    parent: Manage organizations
+weight: 105
+influxdb/v2.2/tags: [buckets]
+---
+
+A **bucket** is a named location where time series data is stored.
+All buckets have a **retention period**, a duration of time that each data point persists.
+InfluxDB drops all points with timestamps older than the bucket's retention period.
+A bucket belongs to an organization.
+
+The following articles provide information about managing buckets:
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/organizations/buckets/create-bucket.md b/content/influxdb/v2.2/organizations/buckets/create-bucket.md
new file mode 100644
index 000000000..01962ab36
--- /dev/null
+++ b/content/influxdb/v2.2/organizations/buckets/create-bucket.md
@@ -0,0 +1,112 @@
+---
+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_2:
+    name: Create a bucket
+    parent: Manage buckets
+weight: 201
+---
+
+Use the InfluxDB user interface (UI) or the `influx` command line interface (CLI)
+to create a bucket.
+
+{{% note %}}
+#### Bucket limits
+A single InfluxDB {{< current-version >}} OSS instance supports approximately 20 buckets actively being
+written to or queried across all organizations depending on the use case.
+Any more than that can adversely affect performance.
+{{% /note %}}
+
+## Create a bucket in the InfluxDB UI
+
+There are two places you can create a bucket in the UI.
+
+### Create a bucket from the Load Data menu
+
+1. In the navigation menu on the left, select **Data (Load Data)** > **Buckets**.
+
+    {{< nav-icon "data" >}}
+
+2. Click **{{< icon "plus" >}} Create Bucket** in the upper right.
+3. Enter a **Name** for the bucket.
+4. Select when to **Delete Data**:
+    - **Never** to retain data forever.  
+    - **Older than** to choose a specific retention period.
+5. Click **Create** to create the bucket.
+
+### Create a bucket in the Data Explorer
+
+1. In the navigation menu on the left, select **Explore* (**Data Explorer**).
+
+    {{< nav-icon "data-explorer" >}}
+
+2. In the **From** panel in the Flux Builder, select `+ Create Bucket`.
+3. Enter a **Name** for the bucket.
+4. Select when to **Delete Data**:
+    - **Never** to retain data forever.  
+    - **Older than** to choose a specific retention period.
+5. Click **Create** to create the bucket.
+
+## Create a bucket using the influx CLI
+
+Use the [`influx bucket create` command](/influxdb/v2.2/reference/cli/influx/bucket/create)
+to create a new bucket. A bucket requires the following:
+
+- bucket name
+- organization name or ID
+- retention period (duration to keep data) in one of the following units:
+  - nanoseconds (`ns`)
+  - microseconds (`us` or `µs`)
+  - milliseconds (`ms`)
+  - seconds (`s`)
+  - minutes (`m`)
+  - hours (`h`)
+  - days (`d`)
+  - weeks (`w`)
+
+  {{% note %}}
+  The minimum retention period is **one hour**.
+  {{% /note %}}
+
+```sh
+# Syntax
+influx bucket create -n <bucket-name> -o <org-name> -r <retention-period-duration>
+
+# Example
+influx bucket create -n my-bucket -o my-org -r 72h
+```
+
+## Create a bucket using the InfluxDB API
+
+Use the InfluxDB API to create a bucket.
+
+{{% note %}}
+#### Bucket limits
+A single InfluxDB {{< current-version >}} OSS instance supports approximately 20 buckets actively being
+written to or queried across all organizations depending on the use case.
+Any more than that can adversely affect performance.
+{{% /note %}}
+
+Create a bucket in InfluxDB using an HTTP request to the InfluxDB API `/buckets` endpoint.
+Use the `POST` request method and include the following in your request:
+
+| Requirement          | Include by                                               |
+|:-----------          |:----------                                               |
+| Organization         | Use `orgID` in the JSON payload.                |
+| Bucket               | Use `name` in the JSON payload.                 |
+| Retention Rules      | Use `retentionRules` in the JSON payload.    |
+| API token | Use the `Authorization: Token` header.                   |
+
+#### Example
+
+The URL depends on the version and location of your InfluxDB {{< current-version >}}
+instance _(see [InfluxDB URLs](/influxdb/v2.2/reference/urls/))_.
+
+```sh
+{{% get-shared-text "api/v2.0/buckets/oss/create.sh" %}}
+```
+
+_For information about **InfluxDB API options and response codes**, see
+[InfluxDB API Buckets documentation](/influxdb/v2.2/api/#operation/PostBuckets)._
diff --git a/content/influxdb/v2.2/organizations/buckets/delete-bucket.md b/content/influxdb/v2.2/organizations/buckets/delete-bucket.md
new file mode 100644
index 000000000..ec1fff825
--- /dev/null
+++ b/content/influxdb/v2.2/organizations/buckets/delete-bucket.md
@@ -0,0 +1,70 @@
+---
+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_2:
+    name: Delete a bucket
+    parent: Manage buckets
+weight: 203
+---
+
+Use the InfluxDB user interface (UI) or the `influx` command line interface (CLI)
+to delete a bucket.
+
+## Delete a bucket in the InfluxDB UI
+
+{{% oss-only %}}
+
+1. In the navigation menu on the left, select **Data (Load Data)** > **Buckets**.
+
+    {{< nav-icon "data" >}}
+2. Hover over the bucket you would like to delete.
+3. Click the **{{< icon "delete" >}}** icon located far right of the bucket name.
+4. Click **Delete** to delete the bucket.
+{{% /oss-only %}}
+
+{{% cloud-only %}}
+
+1. In the navigation menu on the left, select **Load Data** > **Buckets**.
+
+    {{< nav-icon "data" >}}
+
+2. Find the bucket that you would like to delete.
+3. Click the **{{< icon "delete" >}}** icon located far right of the bucket name.
+4. Click **{{< caps >}}Confirm{{< /caps >}}** to delete the bucket.
+{{% /cloud-only %}}
+
+## Delete a bucket using the influx CLI
+
+Use the [`influx bucket delete` command](/influxdb/v2.2/reference/cli/influx/bucket/delete)
+to delete a bucket a bucket by name or ID.
+
+### Delete a bucket by name
+**To delete a bucket by name, you need:**
+
+- Bucket name
+- Bucket's organization name or ID
+
+<!-- -->
+```sh
+# Syntax
+influx bucket delete -n <bucket-name> -o <org-name>
+
+# Example
+influx bucket delete -n my-bucket -o my-org
+```
+
+### Delete a bucket by ID
+**To delete a bucket by ID, you need:**
+
+- Bucket ID _(provided in the output of `influx bucket list`)_
+
+<!-- -->
+```sh
+# Syntax
+influx bucket delete -i <bucket-id>
+
+# Example
+influx bucket delete -i 034ad714fdd6f000
+```
diff --git a/content/influxdb/v2.2/organizations/buckets/update-bucket.md b/content/influxdb/v2.2/organizations/buckets/update-bucket.md
new file mode 100644
index 000000000..56c3e9a9e
--- /dev/null
+++ b/content/influxdb/v2.2/organizations/buckets/update-bucket.md
@@ -0,0 +1,88 @@
+---
+title: Update a bucket
+seotitle: Update a bucket in InfluxDB
+description: Update a bucket's name or retention period in InfluxDB using the InfluxDB UI or the influx CLI.
+menu:
+  influxdb_2_2:
+    name: Update a bucket
+    parent: Manage buckets
+weight: 202
+---
+
+Use the `influx` command line interface (CLI) or the InfluxDB user interface (UI) to update a bucket.
+
+Note that updating an bucket's name will affect any assets that reference the bucket by name, including the following:
+
+  - Queries
+  - Dashboards
+  - Tasks
+  - Telegraf configurations
+  - Templates
+
+If you change a bucket name, be sure to update the bucket in the above places as well.
+
+## Update a bucket's name in the InfluxDB UI
+
+1. In the navigation menu on the left, select **Data (Load Data)** > **Buckets**.
+
+    {{< nav-icon "data" >}}
+
+2. Click **Settings** under the bucket you want to rename.
+3. Click **Rename**.
+3. Review the information in the window that appears and click **I understand, let's rename my bucket**.
+4. Update the bucket's name and click **Change Bucket Name**.
+
+## Update a bucket's retention period in the InfluxDB UI
+
+1. In the navigation menu on the left, select **Data (Load Data)** > **Buckets**.
+
+    {{< nav-icon "data" >}}
+
+2. Click **Settings** next to the bucket you want to update.
+3. In the window that appears, edit the bucket's retention period.
+4. Click **Save Changes**.
+
+## Update a bucket using the influx CLI
+
+Use the [`influx bucket update` command](/influxdb/v2.2/reference/cli/influx/bucket/update)
+to update a bucket. Updating a bucket requires the following:
+
+- The bucket ID _(provided in the output of `influx bucket list`)_
+- The name or ID of the organization the bucket belongs to.
+
+{{< cli/influx-creds-note >}}
+
+##### Update the name of a bucket
+
+```sh
+# Syntax
+influx bucket update -i <bucket-id> -n <new-bucket-name>
+
+# Example
+influx bucket update -i 034ad714fdd6f000 -n my-new-bucket
+```
+
+##### Update a bucket's retention period
+
+Valid retention period duration units:
+
+- nanoseconds (`ns`)
+- microseconds (`us` or `µs`)
+- milliseconds (`ms`)
+- seconds (`s`)
+- minutes (`m`)
+- hours (`h`)
+- days (`d`)
+- weeks (`w`)
+
+{{% note %}}
+The minimum retention period is **one hour**.
+{{% /note %}}
+
+```sh
+# Syntax
+influx bucket update -i <bucket-id> -r <retention period with units>
+
+# Example
+influx bucket update -i 034ad714fdd6f000 -r 1209600000000000ns
+```
diff --git a/content/influxdb/v2.2/organizations/buckets/view-buckets.md b/content/influxdb/v2.2/organizations/buckets/view-buckets.md
new file mode 100644
index 000000000..f070d5415
--- /dev/null
+++ b/content/influxdb/v2.2/organizations/buckets/view-buckets.md
@@ -0,0 +1,34 @@
+---
+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_2:
+    name: View buckets
+    parent: Manage buckets
+weight: 202
+---
+
+## View buckets in the InfluxDB UI
+
+1. In the navigation menu on the left, select **Data (Load Data)** > **Buckets**.
+
+    {{< nav-icon "data" >}}
+
+    A list of buckets with their retention policies and IDs appears.
+
+2. Click a bucket to open it in the **Data Explorer**.
+3. Click the **bucket ID** to copy it to the clipboard.
+
+## View buckets using the influx CLI
+
+Use the [`influx bucket list` command](/influxdb/v2.2/reference/cli/influx/bucket/list)
+to view a buckets in an organization.
+
+```sh
+influx bucket list
+```
+
+Other filtering options such as filtering by organization, name, or ID are available.
+See the [`influx bucket list` documentation](/influxdb/v2.2/reference/cli/influx/bucket/list)
+for information about other available flags.
diff --git a/content/influxdb/v2.2/organizations/create-org.md b/content/influxdb/v2.2/organizations/create-org.md
new file mode 100644
index 000000000..54a32cd7a
--- /dev/null
+++ b/content/influxdb/v2.2/organizations/create-org.md
@@ -0,0 +1,47 @@
+---
+title: Create an organization
+seotitle: Create an organization in InfluxDB
+description: Create an organization in InfluxDB using the InfluxDB UI or the influx CLI.
+menu:
+  influxdb_2_2:
+    name: Create an organization
+    parent: Manage organizations
+weight: 101
+products: [oss]
+---
+
+Use the InfluxDB user interface (UI) or the `influx` command line interface (CLI)
+to create an organization.
+
+{{% note %}}
+#### Organization and bucket limits
+A single InfluxDB {{< current-version >}} OSS instance supports approximately 20 buckets actively being
+written to or queried across all organizations depending on the use case.
+Any more than that can adversely affect performance.
+Because each organization is created with a bucket, we do not recommend more than
+20 organizations in a single InfluxDB OSS instance.
+{{% /note %}}
+
+## Create an organization in the InfluxDB UI
+
+1. In the navigation menu on the left, click the **Account dropdown**.
+
+    {{< nav-icon "account" >}}
+
+2. Select **Create Organization**.
+3. In the window that appears, enter an **Organization Name** and **Bucket Name** and click **Create**.
+
+## Create an organization using the influx CLI
+
+Use the [`influx org create` command](/influxdb/v2.2/reference/cli/influx/org/create)
+to create a new organization. A new organization requires the following:
+
+- A name for the organization
+
+```sh
+# Syntax
+influx org create -n <org-name>
+
+# Example
+influx org create -n my-org
+```
diff --git a/content/influxdb/v2.2/organizations/delete-org.md b/content/influxdb/v2.2/organizations/delete-org.md
new file mode 100644
index 000000000..f54b29de3
--- /dev/null
+++ b/content/influxdb/v2.2/organizations/delete-org.md
@@ -0,0 +1,41 @@
+---
+title: Delete an organization
+seotitle: Delete an organization from InfluxDB
+description: Delete an existing organization from InfluxDB using the influx CLI.
+menu:
+  influxdb_2_2:
+    name: Delete an organization
+    parent: Manage organizations
+weight: 104
+products: [oss]
+---
+
+Use the `influx` command line interface (CLI)
+to delete an organization.
+
+<!--
+## Delete an organization in the InfluxDB UI
+
+1. In the navigation menu on the left, click the **Account dropdown**.
+
+    {{< nav-icon "account" >}}
+
+  The list of organizations appears.
+
+2. Hover over an organization's name, click **Delete**, and then **Confirm**.
+-->
+
+## Delete an organization using the influx CLI
+
+Use the [`influx org delete` command](/influxdb/v2.2/reference/cli/influx/org/delete)
+to delete an organization. Deleting an organization requires the following:
+
+- The organization ID _(provided in the output of `influx org list`)_
+
+```sh
+# Syntax
+influx org delete -i <org-id>
+
+# Example
+influx org delete -i 034ad714fdd6f000
+```
diff --git a/content/influxdb/v2.2/organizations/members/_index.md b/content/influxdb/v2.2/organizations/members/_index.md
new file mode 100644
index 000000000..338dc6ca2
--- /dev/null
+++ b/content/influxdb/v2.2/organizations/members/_index.md
@@ -0,0 +1,16 @@
+---
+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_2:
+    name: Manage members
+    parent: Manage organizations
+weight: 106
+influxdb/v2.2/tags: [members]
+---
+
+A **member** is a user that belongs to an organization.
+The following articles provide information about managing users:
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/organizations/members/add-member.md b/content/influxdb/v2.2/organizations/members/add-member.md
new file mode 100644
index 000000000..41fbc53c7
--- /dev/null
+++ b/content/influxdb/v2.2/organizations/members/add-member.md
@@ -0,0 +1,36 @@
+---
+title: Add a member
+seotitle: Add a member to an organization in InfluxDB
+description: Add a member to an organization.
+menu:
+  influxdb_2_2:
+    name: Add a member
+    parent: Manage members
+weight: 201
+---
+
+Use the `influx` command line interface (CLI) to add a member to an organization.
+
+<!-- ## Add a member to an organization in the InfluxDB UI
+
+1. In the navigation menu on the left, select **Org (Organization)** > **Members**.
+
+    {{< nav-icon "org" >}}
+
+_Complete content coming soon_ -->
+
+## Add a member to an organization using the influx CLI
+
+1. Get a list of users and their IDs by running the following:
+
+```sh
+influx user list
+```
+
+2. To add a user to an organization, run the following command:
+
+```sh
+influx org members add -n <org-name> -m <user-ID>
+```
+
+For more information, see the [`influx org members add` command](/influxdb/v2.2/reference/cli/influx/org/members/add).
diff --git a/content/influxdb/v2.2/organizations/members/remove-member.md b/content/influxdb/v2.2/organizations/members/remove-member.md
new file mode 100644
index 000000000..bf3134db5
--- /dev/null
+++ b/content/influxdb/v2.2/organizations/members/remove-member.md
@@ -0,0 +1,44 @@
+---
+title: Remove a member
+seotitle: Remove a member from an organization in InfluxDB
+description: Remove a member from an organization.
+menu:
+  influxdb_2_2:
+    name: Remove a member
+    parent: Manage members
+weight: 203
+---
+
+Use the InfluxDB user interface (UI) or the `influx` command line interface (CLI)
+to remove a member from an organization.
+
+{{% note %}}
+Removing a member from an organization removes all permissions associated with the organization,
+but it does not delete the user from the system entirely.
+For information about deleting a user from InfluxDB, see [Delete a user](/influxdb/v2.2/users/delete-user/).
+{{% /note %}}
+
+## Remove a member from an organization in the InfluxDB UI
+
+1. In the navigation menu on the left, select **Org (Organization)** > **Members**.
+
+    {{< nav-icon "org" >}}
+
+2. Hover over the member you would like to delete and click the **{{< icon "delete" >}}** icon.
+3. Click **Delete**.
+
+## Remove a member from an organization using the influx CLI
+
+Use the [`influx org members remove` command](/influxdb/v2.2/reference/cli/influx/org/members/remove)
+to remove a member from an organization. Removing a member requires the following:
+
+- The organization name or ID _(provided in the output of [`influx org list`](/influxdb/v2.2/reference/cli/influx/org/list/))_
+- The member ID _(provided in the output of [`influx org members list`](/influxdb/v2.2/reference/cli/influx/org/members/list/))_
+
+```sh
+# Syntax
+influx org members remove -o <member-id> -i <organization-id>
+
+# Example
+influx org members remove -o 00xXx0x00xXX0000 -i x0xXXXx00x0x000X
+```
diff --git a/content/influxdb/v2.2/organizations/members/view-members.md b/content/influxdb/v2.2/organizations/members/view-members.md
new file mode 100644
index 000000000..49afd4b73
--- /dev/null
+++ b/content/influxdb/v2.2/organizations/members/view-members.md
@@ -0,0 +1,35 @@
+---
+title: View members
+seotitle: View members of an organization in InfluxDB
+description: Review a list of members for an organization.
+menu:
+  influxdb_2_2:
+    name: View members
+    parent: Manage members
+weight: 202
+---
+
+Use the InfluxDB user interface (UI) or the `influx` command line interface (CLI)
+to view members of an organization.
+
+## View members of organization in the InfluxDB UI
+
+In the navigation menu on the left, select **Org (Organization)** > **Members**.
+
+{{< nav-icon "org" >}}
+
+
+## View members of organization using the influx CLI
+
+Use the [`influx org members list` command](/influxdb/v2.2/reference/cli/influx/org/members/list)
+to list members of an organization. Listing an organization's members requires the following:
+
+- The name or ID of the organization
+
+```sh
+# Syntax
+influx org members list -n <org-name>
+
+# Example
+influx org members list -n my-org
+```
diff --git a/content/influxdb/v2.2/organizations/switch-org.md b/content/influxdb/v2.2/organizations/switch-org.md
new file mode 100644
index 000000000..96e2368eb
--- /dev/null
+++ b/content/influxdb/v2.2/organizations/switch-org.md
@@ -0,0 +1,22 @@
+---
+title: Switch organizations
+seotitle: Switch organizations in InfluxDB
+description: Switch from one organization to another in the InfluxDB UI
+menu:
+  influxdb_2_2:
+    name: Switch organizations
+    parent: Manage organizations
+weight: 105
+products: [oss]
+---
+
+Use the InfluxDB user interface (UI) to switch from one organization to another. The organization you're currently viewing determines what dashboards, tasks, buckets, members, and other assets you can access.
+
+## Switch organizations in the InfluxDB UI
+
+1. In the navigation menu on the left, click the **Account dropdown**.
+
+    {{< nav-icon "account" >}}
+
+2. Select **Switch Organizations**.
+3. Click the organization you want to switch to.
diff --git a/content/influxdb/v2.2/organizations/update-org.md b/content/influxdb/v2.2/organizations/update-org.md
new file mode 100644
index 000000000..43a28ad60
--- /dev/null
+++ b/content/influxdb/v2.2/organizations/update-org.md
@@ -0,0 +1,49 @@
+---
+title: Update an organization
+seotitle: Update an organization in InfluxDB
+description: Update an organization's name and assets in InfluxDB using the InfluxDB UI or the influx CLI.
+menu:
+  influxdb_2_2:
+    name: Update an organization
+    parent: Manage organizations
+weight: 103
+---
+
+Use the `influx` command line interface (CLI) or the InfluxDB user interface (UI) to update an organization.
+
+Note that updating an organization's name will affect any assets that reference the organization by name, including the following:
+
+  - Queries
+  - Dashboards
+  - Tasks
+  - Telegraf configurations
+  - Templates
+
+If you change an organization name, be sure to update the organization in the above places as well.
+
+## Update an organization in the InfluxDB UI
+
+1. In the navigation menu on the left, click the user icon > **About**.
+
+    {{< img-hd src="/img/influxdb/user-icon.png" alt="User Icon" />}}
+
+2. Click **{{< icon "edit" >}} Rename**. A verification window appears.
+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**.
+
+## Update an organization using the influx CLI
+
+Use the [`influx org update` command](/influxdb/v2.2/reference/cli/influx/org/update)
+to update an organization. Updating an organization requires the following:
+
+- The org ID _(provided in the output of `influx org list`)_
+
+##### Update the name of a organization
+
+```sh
+# Syntax
+influx org update -i <org-id> -n <new-org-name>
+
+# Example
+influx org update -i 034ad714fdd6f000 -n my-new-org
+```
diff --git a/content/influxdb/v2.2/organizations/view-orgs.md b/content/influxdb/v2.2/organizations/view-orgs.md
new file mode 100644
index 000000000..060580044
--- /dev/null
+++ b/content/influxdb/v2.2/organizations/view-orgs.md
@@ -0,0 +1,58 @@
+---
+title: View organizations
+seotitle: View organizations in InfluxDB
+description: Review a list of organizations in InfluxDB using the InfluxDB UI or the influx CLI.
+menu:
+  influxdb_2_2:
+    name: View organizations
+    parent: Manage organizations
+weight: 102
+---
+
+Use the InfluxDB user interface (UI) or the `influx` command line interface (CLI)
+to view organizations.
+
+## View organizations in the InfluxDB UI
+
+1. In the navigation menu on the left, click the **Account dropdown**.
+
+    {{< nav-icon "account" >}}
+
+2. Select **Switch Organizations**. The list of organizations appears.
+
+## View organizations using the influx CLI
+
+Use the [`influx org list` command](/influxdb/v2.2/reference/cli/influx/org/list)
+to view organizations.
+
+```sh
+influx org list
+```
+
+Filtering options such as filtering by name or ID are available.
+See the [`influx org list` documentation](/influxdb/v2.2/reference/cli/influx/org/list)
+for information about other available flags.
+
+## View your organization ID
+
+Use the InfluxDB UI or `influx` CLI to view your organization ID.
+
+### Organization ID in the UI
+
+After logging in to the InfluxDB UI, your organization ID appears in the URL.
+
+<pre class="highlight">
+http://localhost:8086/orgs/<span class="bp" style="font-weight:bold;margin:0 .15rem">03a2bbf46249a000</span>/...
+</pre>
+
+### Organization ID in the CLI
+
+Use [`influx org list`](#view-organizations-using-the-influx-cli) to view your organization ID.
+
+```sh
+> influx org list
+
+ID                  Name
+03a2bbf46249a000    org-1
+03ace3a859669000    org-2
+```
diff --git a/content/influxdb/v2.2/process-data/_index.md b/content/influxdb/v2.2/process-data/_index.md
new file mode 100644
index 000000000..dc613415f
--- /dev/null
+++ b/content/influxdb/v2.2/process-data/_index.md
@@ -0,0 +1,28 @@
+---
+title: Process data with InfluxDB tasks
+seotitle: Process data with InfluxDB tasks
+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_2:
+    name: Process data
+weight: 6
+influxdb/v2.2/tags: [tasks]
+related:
+  - /resources/videos/influxdb-tasks/
+---
+
+Process and analyze your data with tasks in the InfluxDB **task engine**. Use tasks (scheduled Flux queries)
+to input a data stream and then analyze, modify, and act on the data accordingly.
+
+Discover how to create and manage tasks using the InfluxDB user interface (UI)
+and the `influx` command line interface (CLI).
+Find examples of data downsampling, anomaly detection _(Coming)_, alerting
+_(Coming)_, and other common tasks.
+
+{{% note %}}
+Tasks replace InfluxDB v1.x continuous queries.
+{{% /note %}}
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/process-data/common-tasks/_index.md b/content/influxdb/v2.2/process-data/common-tasks/_index.md
new file mode 100644
index 000000000..500ba2640
--- /dev/null
+++ b/content/influxdb/v2.2/process-data/common-tasks/_index.md
@@ -0,0 +1,17 @@
+---
+title: Common data processing tasks
+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.2/tags: [tasks]
+menu:
+  influxdb_2_2:
+    name: Common tasks
+    parent: Process data
+weight: 104
+---
+
+The following articles walk through common task use cases.
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/process-data/common-tasks/calculate_weekly_mean.md b/content/influxdb/v2.2/process-data/common-tasks/calculate_weekly_mean.md
new file mode 100644
index 000000000..9cdc3b4bf
--- /dev/null
+++ b/content/influxdb/v2.2/process-data/common-tasks/calculate_weekly_mean.md
@@ -0,0 +1,49 @@
+---
+title: Calculate a weekly mean
+description: >
+  Calculate a weekly mean and add it to a new bucket.
+menu:
+  influxdb_2_2:
+    name: Calculate a weekly mean
+    parent: Common tasks
+weight: 202
+influxdb/v2.2/tags: [tasks]
+---
+
+{{% note %}}
+This example uses [NOAA water sample data](/influxdb/v2.2/reference/sample-data/#noaa-water-sample-data).
+{{% /note %}}
+
+This example calculates a temperature weekly mean and stores it in a separate bucket.
+
+The following query:
+  -  Uses [`filter()`](/{{< latest "flux" >}}/stdlib/universe/filter/) to filter the `average_temperature` measurement.
+  - Uses [`range()`](/{{< latest "flux" >}}/stdlib/universe/range/) to define a time range.
+  - Uses [`aggregateWindow()`](/{{< latest "flux" >}}/stdlib/universe/aggregatewindow/) to group average temperature by week and compute the mean.
+  - Sends the weekly mean to a new bucket (`weekly_means`)
+
+```js
+option task = {
+  name: "weekly-means",
+  every: 1w,
+}
+
+from(bucket: "noaa")
+  |> filter(fn: (r) => r._measurement == "average_temperature")
+  |> range(start: 2019-09-01T11:24:00Z)
+  |> aggregateWindow(every:  1w, fn: mean)
+  |> to(bucket: "weekly_means")
+```
+### Example results
+
+| _start               | _stop                | _field  | _measurement        | location     | _value            | _time                |
+|:------               |:-----                |:------  |:------------        |:--------     | ------:           |:-----                |
+| 2019-09-01T11:24:00Z | 2020-10-19T20:39:49Z | degrees | average_temperature | coyote_creek | 80.31005917159763 | 2019-09-05T00:00:00Z |
+| 2019-09-01T11:24:00Z | 2020-10-19T20:39:49Z | degrees | average_temperature | coyote_creek | 79.8422619047619  | 2019-09-12T00:00:00Z |
+| 2019-09-01T11:24:00Z | 2020-10-19T20:39:49Z | degrees | average_temperature | coyote_creek | 79.82710622710623 | 2019-09-19T00:00:00Z |
+
+| _start               | _stop                | _field  | _measurement        | location     | _value            | _time                |
+|:------               |:-----                |:------  |:------------        |:--------     | ------:           |:-----                |
+| 2019-09-01T11:24:00Z | 2020-10-19T20:39:49Z | degrees | average_temperature | santa_monica | 80.19952494061758 | 2019-09-05T00:00:00Z |
+| 2019-09-01T11:24:00Z | 2020-10-19T20:39:49Z | degrees | average_temperature | santa_monica | 80.01964285714286 | 2019-09-12T00:00:00Z |
+| 2019-09-01T11:24:00Z | 2020-10-19T20:39:49Z | degrees | average_temperature | santa_monica | 80.20451
diff --git a/content/influxdb/v2.2/process-data/common-tasks/convert_results_to_json.md b/content/influxdb/v2.2/process-data/common-tasks/convert_results_to_json.md
new file mode 100644
index 000000000..0bbfa5b51
--- /dev/null
+++ b/content/influxdb/v2.2/process-data/common-tasks/convert_results_to_json.md
@@ -0,0 +1,45 @@
+---
+title: Convert results to JSON
+seotitle: Convert results to JSON and send them to a URL
+description: >
+  Use `json.encode()` to convert query results to JSON and `http.post()` to send them
+  to a URL endpoint.
+menu:
+  influxdb_2_2:
+    name: Convert results to JSON
+    parent: Common tasks
+weight: 203
+influxdb/v2.2/tags: [tasks]
+---
+{{% note %}}
+This example uses [NOAA water sample data](/influxdb/v2.2/reference/sample-data/#noaa-water-sample-data).
+{{% /note %}}
+
+Send each record to a URL endpoint using the HTTP POST method. This example uses [`json.encode()`](/{{< latest "flux" >}}/stdlib/json/encode/) to convert a value into JSON bytes, then uses [`http.post()`](/{{< latest "flux" >}}/stdlib/http/post/) to send them to a URL endpoint.
+
+The following query:
+  - Uses [`filter()`](/{{< latest "flux" >}}/stdlib/universe/filter/) to filter the `average_temperature` measurement.
+  - Uses [`mean()`](/{{< latest "flux" >}}/stdlib/universe/mean/) to calculate the average value from results.
+  - Uses [`map()`](/{{< latest "flux" >}}/stdlib/universe/map/) to create a new column, `jsonStr`, and build a JSON object using column values from the query. It then byte-encodes the JSON object and stores it as a string in the `jsonStr` column.
+  - Uses [`http.post()`](/{{< latest "flux" >}}/stdlib/http/post/) to send the `jsonStr` value from each record to an HTTP endpoint.
+
+
+```js
+import "http"
+import "json"
+
+from(bucket: "noaa")
+    |> filter(fn: (r) => r._measurement == "average_temperature")
+    |> mean()
+    |> map(fn: (r) => ({r with jsonStr: string(v: json.encode(v: {"location": r.location, "mean": r._value}))}))
+    |> map(
+        fn: (r) => ({
+            r with
+            status_code: http.post(
+                url: "http://somehost.com/",
+                headers: {x: "a", y: "b"},
+                data: bytes(v: r.jsonStr)
+            )
+        })
+    )
+```
diff --git a/content/influxdb/v2.2/process-data/common-tasks/downsample-data.md b/content/influxdb/v2.2/process-data/common-tasks/downsample-data.md
new file mode 100644
index 000000000..79b6f79e5
--- /dev/null
+++ b/content/influxdb/v2.2/process-data/common-tasks/downsample-data.md
@@ -0,0 +1,76 @@
+---
+title: Downsample data with InfluxDB
+seotitle: Downsample data in an InfluxDB task
+description: >
+  How to create a task that downsamples data much like continuous queries
+  in previous versions of InfluxDB.
+menu:
+  influxdb_2_2:
+    name: Downsample data
+    parent: Common tasks
+weight: 201
+influxdb/v2.2/tags: [tasks]
+---
+
+One of the most common use cases for InfluxDB tasks is downsampling data to reduce
+the overall disk usage as data collects over time.
+In previous versions of InfluxDB, continuous queries filled this role.
+
+This article walks through creating a continuous-query-like task that downsamples
+data by aggregating data within windows of time, then storing the aggregate value in a new bucket.
+
+### Requirements
+To perform a downsampling task, you need to the following:
+
+##### A "source" bucket
+The bucket from which data is queried.
+
+##### A "destination" bucket
+A separate bucket where aggregated, downsampled data is stored.
+
+##### Some type of aggregation
+To downsample data, it must be aggregated in some way.
+What specific method of aggregation you use depends on your specific use case,
+but examples include mean, median, top, bottom, etc.
+View [Flux's aggregate functions](/{{< latest "flux" >}}/function-types/#aggregates)
+for more information and ideas.
+
+## Example downsampling task script
+The example task script below is a very basic form of data downsampling that does the following:
+
+1. Defines a task named "cq-mem-data-1w" that runs once a week.
+2. Defines a `data` variable that represents all data from the last 2 weeks in the
+   `mem` measurement of the `system-data` bucket.
+3. Uses the [`aggregateWindow()` function](/{{< latest "flux" >}}/stdlib/universe/aggregatewindow/)
+   to window the data into 1 hour intervals and calculate the average of each interval.
+4. Stores the aggregated data in the `system-data-downsampled` bucket under the
+   `my-org` organization.
+
+```js
+// Task Options
+option task = {name: "cq-mem-data-1w", every: 1w}
+
+// Defines a data source
+data = from(bucket: "system-data")
+    |> range(start: -duration(v: int(v: task.every) * 2))
+    |> filter(fn: (r) => r._measurement == "mem")
+
+data
+    // Windows and aggregates the data in to 1h averages
+    |> aggregateWindow(fn: mean, every: 1h)
+    // Stores the aggregated data in a new bucket
+    |> to(bucket: "system-data-downsampled", org: "my-org")
+```
+
+Again, this is a very basic example, but it should provide you with a foundation
+to build more complex downsampling tasks.
+
+## Add your task
+Once your task is ready, see [Create a task](/influxdb/v2.2/process-data/manage-tasks/create-task) for information about adding it to InfluxDB.
+
+## Things to consider
+- If there is a chance that data may arrive late, specify an `offset` in your
+  task options long enough to account for late-data.
+- If running a task against a bucket with a finite retention period,
+  schedule tasks to run prior to the end of the retention period to let
+  downsampling tasks complete before data outside of the retention period is dropped.
diff --git a/content/influxdb/v2.2/process-data/get-started.md b/content/influxdb/v2.2/process-data/get-started.md
new file mode 100644
index 000000000..ce2324641
--- /dev/null
+++ b/content/influxdb/v2.2/process-data/get-started.md
@@ -0,0 +1,159 @@
+---
+title: Get started with InfluxDB tasks
+list_title: Get started with tasks
+description: >
+  Learn the basics of writing an InfluxDB task that processes data, and then performs an action,
+  such as storing the modified data in a new bucket or sending an alert.
+aliases:
+  - /influxdb/v2.2/process-data/write-a-task/
+influxdb/v2.2/tags: [tasks]
+menu:
+  influxdb_2_2:
+    name: Get started with tasks
+    parent: Process data
+weight: 101
+related:
+  - /influxdb/v2.2/process-data/manage-tasks/
+  - /influxdb/v2.2/process-data/manage-tasks/create-task/
+  - /resources/videos/influxdb-tasks/
+---
+
+An **InfluxDB task** is a scheduled Flux script that takes a stream of input data,
+modifies or analyzes it in some way, then writes the modified data back to InfluxDB
+or performs other actions.
+
+This article walks through writing a basic InfluxDB task that downsamples
+data and stores it in a new bucket.
+
+## Components of a task
+
+Every InfluxDB task needs the following components.
+Their form and order can vary, but they are all essential parts of a task.
+
+- [Task options](#define-task-options)
+- [A data source](#define-a-data-source)
+- [Data processing or transformation](#process-or-transform-your-data)
+- [A destination](#define-a-destination)
+
+_[Skip to the full example task script](#full-example-task-script)_
+
+## Define task options
+
+Task options define specific information about the task.
+The example below illustrates how task options are defined in your Flux script:
+
+```js
+option task = {name: "downsample_5m_precision", every: 1h, offset: 0m}
+```
+
+_See [Task configuration options](/influxdb/v2.2/process-data/task-options) for detailed information
+about each option._
+
+{{% note %}}
+The InfluxDB UI provides a form for defining task options.
+{{% /note %}}
+
+## Define a data source
+
+1.  Use [`from()`](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/from/)
+    to query data from InfluxDB {{% cloud-only %}}Cloud{{% /cloud-only %}}.
+    Use
+    other [Flux input functions](/{{< latest "flux" >}}/function-types/#inputs)
+    to retrieve data from other sources.
+2.  Use [`range()`](/{{< latest "flux" >}}/stdlib/universe/range/) to define the time
+    range to return data from.
+3.  Use [`filter()`](/{{< latest "flux" >}}/stdlib/universe/filter/) to filter
+    data based on column values.
+
+```js
+from(bucket: "example-bucket")
+    |> range(start: -task.every)
+    |> filter(fn: (r) => r._measurement == "mem" and r.host == "myHost")
+```
+
+{{% note %}}
+#### Use task options in your Flux script
+
+Task options are defined in a `task` option record and can be referenced in your Flux script.
+In the example above, the time range is defined as `-task.every`.
+
+`task.every` is dot notation that references the `every` property of the `task` option record.
+`every` is defined as `1h`, therefore `-task.every` equates to `-1h`.
+
+Using task options to define values in your Flux script can make reusing your task easier.
+{{% /note %}}
+
+## Process or transform your data
+
+Tasks automatically process or transform data in some way at regular intervals.
+Data processing can include operations such as downsampling data, detecting
+anomalies, sending notifications, and more.
+
+{{% note %}}
+#### Use offset to account for latent data
+
+Use the `offset` task option to account for potentially latent data (like data from edge devices).
+A task that runs at one hour intervals (`every: 1h`) with an offset of five minutes (`offset: 5m`)
+executes 5 minutes after the hour, but queries data from the original one hour interval.
+{{% /note %}}
+
+The task example below downsamples data by calculating the average of set intervals.
+It uses [`aggregateWindow()`](/{{< latest "flux" >}}/stdlib/universe/aggregatewindow/)
+to group points into 5 minute windows and calculate the average of each
+window with [`mean()`](/{{< latest "flux" >}}/stdlib/universe/mean/).
+
+```js
+option task = {name: "downsample_5m_precision", every: 1h, offset: 0m}
+
+from(bucket: "example-bucket")
+    |> range(start: -task.every)
+    |> filter(fn: (r) => r._measurement == "mem" and r.host == "myHost")
+    |> aggregateWindow(every: 5m, fn: mean)
+```
+
+_See [Common tasks](/influxdb/v2.2/process-data/common-tasks) for examples of tasks commonly used with InfluxDB._
+
+## Define a destination
+
+In most cases, you'll want to send and store data after the task has transformed it.
+The destination could be a separate InfluxDB measurement or bucket.
+
+The example below uses [`to()`](/{{< latest "flux" >}}/stdlib/universe/to)
+to write the transformed data back to another InfluxDB bucket:
+
+```js
+// ...
+    |> to(bucket: "example-downsampled", org: "my-org")
+```
+
+To write data into InfluxDB, `to()` requires the following columns:
+
+- `_time`
+- `_measurement`
+- `_field`
+- `_value`
+
+You can also write data to other destinations using
+[Flux output functions](/{{< latest "flux" >}}/function-types/#outputs).
+
+## Full example task script
+
+Below is a task script that combines all of the components described above:
+
+```js
+// Task options
+option task = {name: "downsample_5m_precision", every: 1h, offset: 0m}
+
+// Data source
+from(bucket: "example-bucket")
+    |> range(start: -task.every)
+    |> filter(fn: (r) => r._measurement == "mem" and r.host == "myHost")
+    // Data processing
+    |> aggregateWindow(every: 5m, fn: mean)
+    // Data destination
+    |> to(bucket: "example-downsampled")
+```
+
+To learn more about InfluxDB tasks and how they work, watch the following video:
+
+{{< youtube zgCmdtZaH9M >}}
diff --git a/content/influxdb/v2.2/process-data/manage-tasks/_index.md b/content/influxdb/v2.2/process-data/manage-tasks/_index.md
new file mode 100644
index 000000000..5e8af6ac7
--- /dev/null
+++ b/content/influxdb/v2.2/process-data/manage-tasks/_index.md
@@ -0,0 +1,20 @@
+---
+title: Manage tasks in InfluxDB
+seotitle: Manage data processing tasks in InfluxDB
+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.2/tags: [tasks]
+menu:
+  influxdb_2_2:
+    name: Manage tasks
+    parent: Process data
+weight: 102
+---
+
+InfluxDB provides two options for managing the creation, reading, updating, and deletion (CRUD) of tasks -
+through the InfluxDB user interface (UI) or using the `influx` command line interface (CLI).
+Both tools can perform all task CRUD operations.
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/process-data/manage-tasks/create-task.md b/content/influxdb/v2.2/process-data/manage-tasks/create-task.md
new file mode 100644
index 000000000..e3aa99f08
--- /dev/null
+++ b/content/influxdb/v2.2/process-data/manage-tasks/create-task.md
@@ -0,0 +1,147 @@
+---
+title: Create a task
+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_2:
+    name: Create a task
+    parent: Manage tasks
+weight: 201
+related:
+  - /influxdb/v2.2/reference/cli/influx/task/create
+---
+
+InfluxDB provides multiple ways to create tasks both in the InfluxDB user interface (UI)
+and the `influx` command line interface (CLI).
+
+_Before creating a task, review the [basics criteria for writing a task](/influxdb/v2.2/process-data/get-started)._
+
+- [InfluxDB UI](#create-a-task-in-the-influxdb-ui)
+- [`influx` CLI](#create-a-task-using-the-influx-cli)
+- [InfluxDB API](#create-a-task-using-the-influxdb-api)
+
+## Create a task in the InfluxDB UI
+The InfluxDB UI provides multiple ways to create a task:
+
+- [Create a task from the Data Explorer](#create-a-task-from-the-data-explorer)
+- [Create a task in the Task UI](#create-a-task-in-the-task-ui)
+- [Import a task](#import-a-task)
+- [Create a task from a template](#create-a-task-from-a-template)
+- [Clone a task](#clone-a-task)
+
+### Create a task from the Data Explorer
+1. In the navigation menu on the left, select **Data Explorer**.
+
+    {{< nav-icon "data-explorer" >}}
+
+2. Build a query and click **Save As** in the upper right.
+3. Select the **{{< caps >}}Task{{< /caps >}}** heading.
+4. Specify the task options. See [Task options](/influxdb/v2.2/process-data/task-options)
+   for detailed information about each option.
+5. Click **{{< caps >}}Save as Task{{< /caps >}}**.
+
+
+### Create a task in the Task UI
+1. In the navigation menu on the left, select **Tasks**.
+
+    {{< nav-icon "tasks" >}}
+
+2. Click **{{< caps >}}{{< icon "plus" >}} Create Task{{< /caps >}}** in the upper right.
+3. In the left panel, specify the task options.
+   See [Task options](/influxdb/v2.2/process-data/task-options) for detailed information about each option.
+4. In the right panel, enter your task script.
+
+    {{% note %}}
+##### Leave out the option tasks assignment
+When creating a _new_ task in the InfluxDB Task UI, leave the code editor empty.
+When you save the task, the Task UI uses the [task options](/influxdb/v2.2/process-data/task-options/) you specify in the **Task options** form to populate `option task = {task_options}` for you.
+
+When you edit the saved task, you'll see the injected `option task = {task_options}`.
+    {{% /note %}}
+
+7. Click **Save** in the upper right.
+
+### Import a task
+1. In the navigation menu on the left, select **Tasks**.
+
+    {{< nav-icon "tasks" >}}
+
+2. Click **{{< caps >}}{{< icon "plus" >}} Create Task{{< /caps >}}** in the upper right.
+3. In the left panel, specify the task options.
+   See [Task options](/influxdb/v2.2/process-data/task-options) for detailed information about each option.
+4. Paste a raw Flux task in the code editor to the right of the task options fields.
+5. Click **{{< caps >}}Save{{< /caps >}}** in the upper right.
+
+### Create a task from a template
+1. In the navigation menu on the left, select **Settings** > **Templates**.
+
+    {{< nav-icon "Settings" >}}
+
+2. Find the template you want to use and click its **Resources** list to expand the list of resources.
+3. In the **Resources** list, click the task you want to use.
+
+
+### Clone a task
+1. In the navigation menu on the left, select **Tasks**.
+
+    {{< nav-icon "tasks" >}}
+
+2. Find the task you would like to clone and click the **{{< icon "settings" >}}** icon located far right of the task name.
+4. Click **Clone**.
+
+## Create a task using the influx CLI
+Use the `influx task create` command to create a new task.
+It accepts either a file path or raw Flux.
+
+###### Create a task using a file
+```sh
+# Syntax
+influx task create --org <org-name>  -f </path/to/task-script>
+
+# Example
+influx task create --org my-org -f /tasks/cq-mean-1h.flux
+```
+
+###### Create a task using raw Flux
+```sh
+influx task create --org my-org - # <return> to open stdin pipe
+
+option task = {
+  name: "task-name",
+  every: 6h
+}
+
+# ... Task script ...
+
+# <ctrl-d> to close the pipe and submit the command
+```
+
+## Create a task using the InfluxDB API
+
+Send a request using the **POST** method to the `/api/v2/tasks` InfluxDB API endpoint.
+Provide the following in your API request:
+
+##### Request headers
+- **Content-Type**: application/json
+- **Authorization**: Token *`INFLUX_API_TOKEN`*
+
+##### Request body
+JSON object with the following fields:
+
+- **flux** : raw Flux task string
+- **orgID**: your [InfluxDB organization ID](/influxdb/v2.2/organizations/view-orgs/#view-your-organization-id)
+- **status**: task status ("active" or "inactive")
+- **description**: task description
+
+```sh
+curl --request POST 'https://us-west-2-1.aws.cloud2.influxdata.com/api/v2/tasks' \
+  --header 'Content-Type: application/json' \
+  --header 'Authorization: Token INFLUX_API_TOKEN' \
+  --data-raw '{
+    "flux": "option task = {name: \"CPU Total 1 Hour New\", every: 1h}\n\nfrom(bucket: \"telegraf\")\n\t|> range(start: -1h)\n\t|> filter(fn: (r) =>\n\t\t(r._measurement == \"cpu\"))\n\t|> filter(fn: (r) =>\n\t\t(r._field == \"usage_system\"))\n\t|> filter(fn: (r) =>\n\t\t(r.cpu == \"cpu-total\"))\n\t|> aggregateWindow(every: 1h, fn: max)\n\t|> to(bucket: \"cpu_usage_user_total_1h\", org: \"<MYORG>\")",
+    "orgID": "INFLUX_ORG_ID",
+    "status": "active",
+    "description": "This task downsamples CPU data every hour"
+}'
+```
diff --git a/content/influxdb/v2.2/process-data/manage-tasks/delete-task.md b/content/influxdb/v2.2/process-data/manage-tasks/delete-task.md
new file mode 100644
index 000000000..2cd75b87d
--- /dev/null
+++ b/content/influxdb/v2.2/process-data/manage-tasks/delete-task.md
@@ -0,0 +1,35 @@
+---
+title: Delete a task
+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_2:
+    name: Delete a task
+    parent: Manage tasks
+weight: 206
+related:
+  - /influxdb/v2.2/reference/cli/influx/task/delete
+---
+
+## Delete a task in the InfluxDB UI
+1. In the navigation menu on the left, select **Tasks**.
+
+    {{< nav-icon "tasks" >}}
+
+2. In the list of tasks, hover over the task you would like to delete.
+3. Click **Delete** on the far right.
+4. Click **Confirm**.
+
+## Delete a task with the influx CLI
+Use the `influx task delete` command to delete a task.
+
+_This command requires a task ID, which is available in the output of `influx task list`._
+
+```sh
+# Syntax
+influx task delete -i <task-id>
+
+# Example
+influx task delete -i 0343698431c35000
+```
diff --git a/content/influxdb/v2.2/process-data/manage-tasks/export-task.md b/content/influxdb/v2.2/process-data/manage-tasks/export-task.md
new file mode 100644
index 000000000..8a705c252
--- /dev/null
+++ b/content/influxdb/v2.2/process-data/manage-tasks/export-task.md
@@ -0,0 +1,26 @@
+---
+title: Export a task
+seotitle: Export an InfluxDB task
+description: Export a data processing task from InfluxDB using the InfluxDB UI.
+menu:
+  influxdb_2_2:
+    name: Export a task
+    parent: Manage tasks
+weight: 205
+---
+
+InfluxDB lets you export tasks from the InfluxDB user interface (UI).
+Tasks are exported as downloadable JSON files.
+
+## Export a task in the InfluxDB UI
+1. In the navigation menu on the left, select **Tasks**.
+
+    {{< nav-icon "tasks" >}}
+
+2. In the list of tasks, hover over the task you would like to export and click
+   the **{{< icon "gear" >}}** icon that appears.
+3. Select **Export**.
+4. Downloading or save the task export file using one of the following options:
+    - Click **Download JSON** to download the exported JSON file.
+    - Click **Save as template** to save the export file as a task template.
+    - Click **Copy to Clipboard** to copy the raw JSON content to your machine's clipboard.
diff --git a/content/influxdb/v2.2/process-data/manage-tasks/run-task.md b/content/influxdb/v2.2/process-data/manage-tasks/run-task.md
new file mode 100644
index 000000000..cb7cd6d69
--- /dev/null
+++ b/content/influxdb/v2.2/process-data/manage-tasks/run-task.md
@@ -0,0 +1,66 @@
+---
+title: Run a task
+seotitle: Run an InfluxDB task
+description: >
+  Run a data processing task using the InfluxDB UI or the `influx` CLI.
+menu:
+  influxdb_2_2:
+    name: Run a task
+    parent: Manage tasks
+weight: 203
+related:
+  - /influxdb/v2.2/reference/cli/influx/task/run
+  - /influxdb/v2.2/reference/cli/influx/task/run/retry
+  - /influxdb/v2.2/reference/cli/influx/task/retry-failed
+---
+
+InfluxDB data processing tasks generally run in defined intervals or at a specific time,
+however, you can manually run a task from the InfluxDB user interface (UI) or the
+`influx` command line interface (CLI).
+
+## Run a task from the InfluxDB UI
+1. In the navigation menu on the left, select **Tasks**.
+
+    {{< nav-icon "tasks" >}}
+
+2. Hover over the task you want to run and click the **{{< icon "gear" >}}** icon.
+3. Select **Run Task**.
+
+## Run a task with the influx CLI
+Use the `influx task run retry` command to run a task.
+
+{{% note %}}
+To run a task from the `influx` CLI, the task must have already run at least once.
+{{% /note %}}
+
+{{< cli/influx-creds-note >}}
+
+```sh
+# List all tasks to find the ID of the task to run
+influx task list
+
+# Use the task ID to list previous runs of the task
+influx task run list --task-id=0000000000000000
+
+# Use the task ID and run ID to retry a run
+influx task run retry --task-id=0000000000000000 --run-id=0000000000000000
+```
+
+### Retry failed task runs
+Use the [`influx task retry-failed` command](/influxdb/v2.2/reference/cli/influx/task/retry-failed/)
+to retry failed task runs.
+
+```sh
+# Retry failed tasks for a specific task
+influx task retry-failed \
+  --id 0000000000000000
+
+# Print information about runs that will be retried
+influx task retry-failed \
+  --dry-run
+
+# Retry failed task runs that occurred in a specific time range
+influx task retry-failed \
+  --after 2021-01-01T00:00:00Z \
+  --before 2021-01-01T23:59:59Z
+```
diff --git a/content/influxdb/v2.2/process-data/manage-tasks/task-run-history.md b/content/influxdb/v2.2/process-data/manage-tasks/task-run-history.md
new file mode 100644
index 000000000..a297ffb8e
--- /dev/null
+++ b/content/influxdb/v2.2/process-data/manage-tasks/task-run-history.md
@@ -0,0 +1,67 @@
+---
+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_2:
+    name: View run history
+    parent: Manage tasks
+weight: 203
+related:
+  - /influxdb/v2.2/reference/cli/influx/task/list
+  - /influxdb/v2.2/reference/cli/influx/task/run/list
+  - /influxdb/v2.2/reference/cli/influx/task/retry-failed
+---
+
+When an InfluxDB task runs, a "run" record is created in the task's history.
+Logs associated with each run provide relevant log messages, timestamps,
+and the exit status of the run attempt.
+
+Use the InfluxDB user interface (UI) or the `influx` command line interface (CLI)
+to view task run histories and associated logs.
+
+## View a task's run history in the InfluxDB UI
+
+1. In the navigation menu on the left, select **Tasks**.
+
+    {{< nav-icon "tasks" >}}
+
+2. Hover over the task you want to run and click the **{{< icon "gear" >}}** icon.
+3. Select **View Task Runs**.
+
+### View task run logs
+To view logs associated with a run, click **View Logs** next to the run in the task's run history.
+
+## View a task's run history with the influx CLI
+Use the `influx task run list` command to view a task's run history.
+
+```sh
+# List all tasks to find the ID of the task to run
+influx task list
+
+# Use the task ID to view the run history of a task
+influx task run list --task-id=0000000000000000
+```
+
+{{% note %}}
+Detailed run logs are not currently available in the `influx` CLI.
+{{% /note %}}
+
+## Retry failed task runs
+Use the [`influx task retry-failed` command](/influxdb/v2.2/reference/cli/influx/task/retry-failed/)
+to retry failed task runs.
+
+```sh
+# Retry failed tasks for a specific task
+influx task retry-failed \
+  --id 0000000000000000
+
+# Print information about runs that will be retried
+influx task retry-failed \
+  --dry-run
+
+# Retry failed task runs that occurred in a specific time range
+influx task retry-failed \
+  --after 2021-01-01T00:00:00Z \
+  --before 2021-01-01T23:59:59Z
+```
diff --git a/content/influxdb/v2.2/process-data/manage-tasks/update-task.md b/content/influxdb/v2.2/process-data/manage-tasks/update-task.md
new file mode 100644
index 000000000..8fc589710
--- /dev/null
+++ b/content/influxdb/v2.2/process-data/manage-tasks/update-task.md
@@ -0,0 +1,74 @@
+---
+title: Update a task
+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_2:
+    name: Update a task
+    parent: Manage tasks
+weight: 204
+related:
+  - /influxdb/v2.2/reference/cli/influx/task/update
+---
+
+## Update a task in the InfluxDB UI
+1. In the navigation menu on the left, select **Tasks**.
+
+    {{% nav-icon "tasks" %}}
+
+2. Find the task you would like to edit and click the **{{< icon "settings" >}}** icon located far right of the task name.
+3. Click **Edit**.
+4. Click **{{< caps >}}Save{{< /caps >}}** in the upper right.
+
+#### Update a task Flux script
+1. In the list of tasks, click the **Name** of the task you want to update.
+2. In the left panel, modify the task options.
+3. In the right panel, modify the task script.
+4. Click **{{< caps >}}Save{{< /caps >}}** in the upper right.
+
+#### Update the status of a task
+In the list of tasks, click the {{< icon "toggle" >}} toggle to the left of the
+task you want to activate or inactivate.
+
+#### Update a task description
+1. In the list of tasks, hover over the name of the task you want to update.
+2. Click the pencil icon {{< icon "pencil" >}}.
+3. Click outside of the field or press `RETURN` to update.
+
+## Update a task with the influx CLI
+Use the `influx task update` command to update or change the status of an existing task.
+
+_This command requires a task ID, which is available in the output of `influx task list`._
+
+#### Update a task Flux script
+Pass the file path of your updated Flux script to the `influx task update` command
+with the ID of the task you want to update.
+Modified [task options](/influxdb/v2.2/process-data/task-options) defined in the Flux
+script are also updated.
+
+```sh
+# Syntax
+influx task update -i <task-id> -f </path/to/updated-task-script>
+```
+
+```sh
+# Example
+influx task update -i 0343698431c35000 -f /tasks/cq-mean-1h.flux
+```
+
+#### Update the status of a task
+Pass the ID of the task you want to update to the `influx task update`
+command with the `--status` flag.
+
+_Possible arguments of the `--status` flag are `active` or `inactive`._
+
+```sh
+# Syntax
+influx task update -i <task-id> --status < active | inactive >
+```
+
+```sh
+# Example
+influx task update -i 0343698431c35000 --status inactive
+```
diff --git a/content/influxdb/v2.2/process-data/manage-tasks/view-tasks.md b/content/influxdb/v2.2/process-data/manage-tasks/view-tasks.md
new file mode 100644
index 000000000..7e9deed55
--- /dev/null
+++ b/content/influxdb/v2.2/process-data/manage-tasks/view-tasks.md
@@ -0,0 +1,38 @@
+---
+title: View tasks
+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_2:
+    name: View tasks
+    parent: Manage tasks
+weight: 202
+related:
+  - /influxdb/v2.2/reference/cli/influx/task/list
+---
+
+## View tasks in the InfluxDB UI
+Click the **Tasks** icon in the left navigation to view the lists of tasks.
+
+{{< nav-icon "tasks" >}}
+
+### Filter the list of tasks
+
+1. Click the **Show Inactive** {{< icon "toggle" >}} toggle to include or exclude
+   inactive tasks in the list.
+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.
+
+## View tasks with the influx CLI
+Use the `influx task list` command to return a list of created tasks.
+
+```sh
+influx task list
+```
+
+#### Filter tasks using the CLI
+Other filtering options such as filtering by organization or user,
+or limiting the number of tasks returned, are available.
+See the [`influx task list` documentation](/influxdb/v2.2/reference/cli/influx/task/list)
+for information about other available flags.
diff --git a/content/influxdb/v2.2/process-data/task-options.md b/content/influxdb/v2.2/process-data/task-options.md
new file mode 100644
index 000000000..d00143b7c
--- /dev/null
+++ b/content/influxdb/v2.2/process-data/task-options.md
@@ -0,0 +1,107 @@
+---
+title: Task configuration options
+seotitle: InfluxDB task configuration options
+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_2:
+    name: Task options
+    parent: Process data
+weight: 105
+influxdb/v2.2/tags: [tasks, flux]
+---
+
+Task options define specific information about a task.
+They are set in a Flux script or in the InfluxDB user interface (UI).
+The following task options are available:
+
+- [name](#name)
+- [every](#every)
+- [cron](#cron)
+- [offset](#offset)
+- [concurrency](#concurrency)
+
+{{% note %}}
+`every` and `cron` are mutually exclusive, but at least one is required.
+{{% /note %}}
+
+## name
+The name of the task. _**Required**_.
+
+_**Data type:** String_
+
+```js
+option task = {
+    name: "taskName",
+    // ...
+}
+```
+
+## every
+
+The interval at which the task runs. This option also determines when the task first starts to run, depending on the specified time (in [duration literal](/{{< latest "flux" >}}/spec/lexical-elements/#duration-literals)).
+
+_**Data type:** Duration_
+
+```js
+option task = {
+    // ...
+    every: 1h,
+}
+```
+
+For example, if you save or schedule a task at 2:30 and run the task every hour (`1h`):
+
+`option task = {name: "aggregation", every: 1h}`
+
+The task first executes at 3:00pm, and subsequently every hour after that.
+
+{{% note %}}
+In the InfluxDB UI, the **Interval** field sets this option.
+{{% /note %}}
+
+## cron
+The [cron expression](https://en.wikipedia.org/wiki/Cron#Overview) that
+defines the schedule on which the task runs.
+Cron scheduling is based on system time.
+
+_**Data type:** String_
+
+```js
+option task = {
+    // ...
+    cron: "0 * * * *",
+}
+```
+
+## offset
+
+Delays the execution of the task but preserves the original time range.
+For example, if a task is to run on the hour, a `10m` offset will delay it to 10
+minutes after the hour, but all time ranges defined in the task are relative to
+the specified execution time.
+A common use case is offsetting execution to account for data that may arrive late.
+
+_**Data type:** Duration_
+
+```js
+option task = {
+    // ...
+    offset: 10m,
+}
+```
+
+## concurrency
+The number task of executions that can run concurrently.
+If the concurrency limit is reached, all subsequent executions are queued until
+other running task executions complete.
+
+_**Data type:** Integer_
+
+```js
+option task = {
+    // ...
+    concurrency: 2,
+}
+```
diff --git a/content/influxdb/v2.2/query-data/_index.md b/content/influxdb/v2.2/query-data/_index.md
new file mode 100644
index 000000000..3c1ca1760
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/_index.md
@@ -0,0 +1,19 @@
+---
+title: Query data in InfluxDB
+seotitle: Query data stored in InfluxDB
+description: >
+  Learn to query data stored in InfluxDB using Flux and tools such as the InfluxDB
+  user interface and the 'influx' command line interface.
+aliases:
+  - /influxdb/v2.2/query_language/data_exploration/
+menu:
+  influxdb_2_2:
+    name: Query data
+weight: 5
+influxdb/v2.2/tags: [query, flux]
+---
+
+Learn to query data stored in InfluxDB using Flux and tools such as the InfluxDB
+user interface and the 'influx' command line interface.
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/query-data/common-queries/_index.md b/content/influxdb/v2.2/query-data/common-queries/_index.md
new file mode 100644
index 000000000..a8897c3c5
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/common-queries/_index.md
@@ -0,0 +1,22 @@
+---
+title: Common queries
+seotitle: Common queries with Flux
+description: >
+  This collection of articles walks through common use cases for Flux queries.
+influxdb/v2.2/tags: [queries]
+menu:
+  influxdb_2_2:
+    name: Common queries
+    parent: Query data
+weight: 104
+---
+
+The following articles walk through common queries using the
+[NOAA water database data](/influxdb/v2.2/reference/sample-data/#noaa-water-sample-data).
+
+{{< children >}}
+
+{{% note %}}
+This list will continue to grow.
+If you have suggestions, please [submit them to the InfluxData Community](https://community.influxdata.com/c/influxdb2).
+{{% /note %}}
diff --git a/content/influxdb/v2.2/query-data/common-queries/compare-values.md b/content/influxdb/v2.2/query-data/common-queries/compare-values.md
new file mode 100644
index 000000000..e74a00805
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/common-queries/compare-values.md
@@ -0,0 +1,48 @@
+---
+title: Comparing values from different buckets
+seotitle: Compare the last measurement to a mean stored in another bucket
+description: >
+  Compare the value from the latest point to an average value stored in another bucket. This is useful when using the average value to calculate a threshold check.
+influxdb/v2.2/tags: [queries]
+menu:
+  influxdb_2_2:
+    name: Compare values from different buckets
+    parent: Common queries
+weight: 104
+---
+
+{{% note %}}
+This example uses [NOAA water sample data](/influxdb/v2.2/reference/sample-data/#noaa-water-sample-data).
+{{% /note %}}
+
+This example compares the value from the latest point to an average value stored in another bucket. This is useful when using the average value to calculate a [threshold check](/influxdb/v2.2/monitor-alert/checks/create/#threshold-check).
+
+The following query:
+
+- Uses [`range()`](/{{< latest "flux" >}}/stdlib/universe/range/) to define a time range.
+- Gets the last value in the `means` bucket and compares it to the last value in the `noaa` bucket using [`last()`](/{{< latest "flux" >}}/stdlib/universe/last/).
+- Uses [`join()`](/{{< latest "flux" >}}/stdlib/universe/join/) to combine the results
+- Uses [`map()`](/{{< latest "flux" >}}/stdlib/universe/map/) to calculate the differences
+
+```js
+means = from(bucket: "weekly_means")
+    |> range(start: 2019-09-01T00:00:00Z)
+    |> last()
+    |> keep(columns: ["_value", "location"])
+
+latest = from(bucket: "noaa")
+    |> range(start: 2019-09-01T00:00:00Z)
+    |> filter(fn: (r) => r._measurement == "average_temperature")
+    |> last()
+    |> keep(columns: ["_value", "location"])
+
+join(tables: {mean: means, reading: latest}, on: ["location"])
+    |> map(fn: (r) => ({r with deviation: r._value_reading - r._value_mean}))
+```
+
+### Example results
+
+| location     | _value_mean       | _value_reading | deviation         |
+|:--------     | -----------:      | --------------:| ---------:        |
+| coyote_creek | 79.82710622710623 | 89             | 9.172893772893772 |
+| santa_monica | 80.20451339915374 | 85             | 4.79548660084626  |
diff --git a/content/influxdb/v2.2/query-data/common-queries/iot-common-queries.md b/content/influxdb/v2.2/query-data/common-queries/iot-common-queries.md
new file mode 100644
index 000000000..3080183b1
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/common-queries/iot-common-queries.md
@@ -0,0 +1,213 @@
+---
+title: IoT sensor common queries
+description: >
+  Use Flux to address common IoT use cases that query data collected from sensors.
+influxdb/v2.2/tags: [queries]
+menu:
+  influxdb_2_2:
+    name: IoT common queries
+    parent: Common queries
+weight: 205
+---
+
+The following scenarios illustrate common queries used to extract information from IoT sensor data:
+
+- [Calculate time in state](#calculate-time-in-state)
+- [Calculate time weighted average](#calculate-time-weighted-average)
+- [Calculate value between events](#calculate-value-between-events)
+- [Determine a state within existing values](#determine-a-state-within-existing-values)
+
+All scenarios below use the `machineProduction` sample dataset provided by the [InfluxDB `sample` package](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/sample/).
+For more information, see [Sample data](/influxdb/cloud/reference/sample-data/).
+
+## Calculate time in state
+
+In this scenario, we look at whether a production line is running smoothly (`state`=`OK`) and what percentage of time the production line is running smoothly or not (`state`=`NOK`). If no points are recorded during the interval (`state`=`NaN`), you may opt to retrieve the last state prior to the interval. 
+
+To visualize the time in state, see the [Mosaic visualization](#mosaic-visualization).
+
+**To calculate the percentage of time a machine spends in each state**
+
+1. Import the [`contrib/tomhollingworth/events` package](/{{< latest "flux" >}}/stdlib/contrib/tomhollingworth/events/).
+1. Query the `state` field.
+2. Use `events.duration()` to return the amount of time (in a specified unit) between each data point, and store the interval in the `duration` column.
+3. Group columns by the status value column (in this case `_value`), `_start`, `_stop`, and other relevant dimensions.
+4. Sum the `duration` column to calculate the total amount of time spent in each state.
+5. Pivot the summed durations into the `_value` column.
+6. Use `map()` to calculate the percentage of time spent in each state.
+
+```js
+import "contrib/tomhollingworth/events"
+
+from(bucket: "machine")
+    |> range(start: 2021-08-01T00:00:00Z, stop: 2021-08-02T00:30:00Z)
+    |> filter(fn: (r) => r["_measurement"] == "machinery")
+    |> filter(fn: (r) => r["_field"] == "state")
+    |> events.duration(unit: 1h, columnName: "duration")
+    |> group(columns: ["_value", "_start", "_stop", "station_id"])
+    |> sum(column: "duration")
+    |> pivot(rowKey: ["_stop"], columnKey: ["_value"], valueColumn: "duration")
+    |> map(
+        fn: (r) => {
+            totalTime = float(v: r.NOK + r.OK)
+    
+            return {r with NOK: float(v: r.NOK) / totalTime * 100.0, OK: float(v: r.OK) / totalTime * 100.0}
+        },
+    )
+```
+
+The query above focuses on a specific time range of state changes reported in the production line.
+
+- `range()` defines the time range to query.
+- `filter()` defines the field (`state`) and measurement (`machinery`) to filter by.
+- `events.duration()` calculates the time between points.
+- `group()` regroups the data by the field value, so points with `OK` and `NOK` field values are grouped into separate tables.
+- `sum()` returns the sum of durations spent in each state.
+
+The output of the query at this point is:
+
+| _value | duration | 
+| ------ | -------: | 
+| NOK    | 22       | 
+
+| _value | duration | 
+| ------ | -------: | 
+| OK     | 172      | 
+
+`pivot()` creates columns for each unique value in the `_value` column, and then assigns the associated duration as the column value.
+The output of the pivot operation is:
+
+| NOK | OK  |
+| :-- | :-- |
+| 22  | 172 |
+
+Given the output above, `map()` does the following:
+
+1. Adds the `NOK` and `OK` values to calculate `totalTime`. 
+2. Divides `NOK` by `totalTime`, and then multiplies the quotient by 100. 
+3. Divides `OK` by `totalTime`, and then multiplies the quotient by 100.
+
+This returns:
+
+| NOK               | OK                 | 
+| :---------------- | :----------------- | 
+| 11.34020618556701 | 88.65979381443299  | 
+
+The result shows that 88.66% of time production is in the `OK` state, and that 11.34% of time, production is in the `NOK` state.
+
+#### Mosaic visualization 
+
+The [mosaic visualization](/influxdb/v2.2/visualize-data/visualization-types/mosaic/) displays state changes over time. In this example, the mosaic visualization displays different colored tiles based on the `state` field. 
+
+```js
+from(bucket: "machine")
+    |> range(start: 2021-08-01T00:00:00Z, stop: 2021-08-02T00:30:00Z)
+    |> filter(fn: (r) => r._measurement == "machinery")
+    |> filter(fn: (r) => r._field == "state")
+    |> aggregateWindow(every: v.windowPeriod, fn: last, createEmpty: false)
+```
+
+When visualizing data, it is possible to have more data points than available pixels. To divide data into time windows that span a single pixel, use `aggregateWindow` with the `every` parameter set to `v.windowPeriod`.
+Use `last` as the aggregate `fn` to return the last value in each time window.
+Set `createEmpty` to `false` so results  won't include empty time windows. 
+
+
+## Calculate time weighted average
+
+To calculate the time-weighted average of data points, use the [`timeWeightedAvg()` function](/{{< latest "flux" >}}/stdlib/universe/timeweightedavg/).
+
+The example below queries the `oil_temp` field in the `machinery` measurement. The `timeWeightedAvg()` function returns the time-weighted average of oil temperatures based on 5 second intervals.
+
+```js
+from(bucket: "machine")
+    |> range(start: 2021-08-01T00:00:00Z, stop: 2021-08-01T00:00:30Z)
+    |> filter(fn: (r) => r._measurement == "machinery" and r._field == "oil_temp")
+    |> timeWeightedAvg(unit: 5s)
+```
+
+##### Output data
+
+| stationID | _start                   | _stop                    | _value             |
+|:-----     | -----                    | -----                    |             ------:|
+| g1        | 2021-08-01T01:00:00.000Z | 2021-08-01T00:00:30.000Z | 40.25396118491921  |
+| g2        | 2021-08-01T01:00:00.000Z | 2021-08-01T00:00:30.000Z | 40.6               |
+| g3        | 2021-08-01T01:00:00.000Z | 2021-08-01T00:00:30.000Z | 41.384505595567866 |
+| g4        | 2021-08-01T01:00:00.000Z | 2021-08-01T00:00:30.000Z | 41.26735518634935  |
+
+
+## Calculate value between events
+
+Calculate the value between events by getting the average value during a specific time range. 
+
+The following scenario queries data starting when four production lines start and end.
+The following query calculates the average oil temperature for each grinding station during that period.
+
+```js
+batchStart = 2021-08-01T00:00:00Z
+batchStop = 2021-08-01T00:00:20Z
+
+from(bucket: "machine")
+    |> range(start: batchStart, stop: batchStop)
+    |> filter(fn: (r) => r._measurement == "machinery" and r._field == "oil_temp")
+    |> mean()
+```
+
+##### Output
+
+| stationID | _start                   | _stop                    | _value             |
+|:-----     | -----                    | -----                    |             ------:|
+| g1        | 2021-08-01T01:00:00.000Z | 2021-08-02T00:00:00.000Z | 40                 |
+| g2        | 2021-08-01T01:00:00.000Z | 2021-08-02T00:00:00.000Z | 40.6               |
+| g3        | 2021-08-01T01:00:00.000Z | 2021-08-02T00:00:00.000Z | 41.379999999999995 |
+| g4        | 2021-08-01T01:00:00.000Z | 2021-08-02T00:00:00.000Z | 41.2               |
+
+
+## Determine a state with existing values
+
+Use multiple existing values to determine a state.
+The following example calculates a state based on the difference between the `pressure` and `pressure-target` fields in the machine-production sample data.
+To determine a state by comparing existing fields:
+
+1. Query the fields to compare (in this case, `pressure` and `pressure_target`).
+2. (Optional) Use `aggregateWindow()` to window data into time-based windows and
+    apply an aggregate function (like `mean()`) to return values that represent larger windows of time.
+3. Use `pivot()` to shift field values into columns.
+4. Use `map()` to compare or operate on the different field column values.
+5. Use `map()` to assign a status (in this case, `needsMaintenance` based on the relationship of the field column values.
+ 
+```js
+import "math"
+
+from(bucket: "machine")
+    |> range(start: 2021-08-01T00:00:00Z, stop: 2021-08-02T00:00:00Z)
+    |> filter(fn: (r) => r["_measurement"] == "machinery")
+    |> filter(fn: (r) => r["_field"] == "pressure" or r["_field"] == "pressure_target")
+    |> aggregateWindow(every: 12h, fn: mean)
+    |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
+    |> map(fn: (r) => ({ r with pressureDiff: r.pressure - r.pressure_target }))
+    |> map(fn: (r) => ({ r with needsMaintenance: if math.abs(x: r.pressureDiff) >= 15.0 then true else false }))
+```
+
+##### Output
+
+| _time                    | needsMaintenance |           pressure |    pressure_target |        pressureDiff | stationID |
+| :----------------------- | :--------------- | -----------------: | -----------------: | ------------------: | --------: |
+| 2021-08-01T12:00:00.000Z | false            | 101.83929080014092 | 104.37786394078252 | -2.5385731406416028 |        g1 |
+| 2021-08-02T00:00:00.000Z | false            |  96.04368008245874 | 102.27698650674662 |  -6.233306424287889 |        g1 |
+
+| _time                    | needsMaintenance |           pressure |    pressure_target |        pressureDiff | stationID |
+| :----------------------- | :--------------- | -----------------: | -----------------: | ------------------: | --------: |
+| 2021-08-01T12:00:00.000Z | false            | 101.62490431541765 | 104.83915260886623 |  -3.214248293448577 |        g2 |
+| 2021-08-02T00:00:00.000Z | false            |  94.52039415465273 | 105.90869375273046 | -11.388299598077722 |        g2 |
+
+| _time                    | needsMaintenance |           pressure |    pressure_target |        pressureDiff | stationID |
+| :----------------------- | :--------------- | -----------------: | -----------------: | ------------------: | --------: |
+| 2021-08-01T12:00:00.000Z | false            |  92.23774168403503 | 104.81867444768653 | -12.580932763651504 |        g3 |
+| 2021-08-02T00:00:00.000Z | true             |  89.20867846153847 |  108.2579185520362 | -19.049240090497733 |        g3 |
+
+| _time                    | needsMaintenance |           pressure |    pressure_target |        pressureDiff | stationID |
+| :----------------------- | :--------------- | -----------------: | -----------------: | ------------------: | --------: |
+| 2021-08-01T12:00:00.000Z | false            |  94.40834093349847 |  107.6827757125155 | -13.274434779017028 |        g4 |
+| 2021-08-02T00:00:00.000Z | true             |  88.61785638936534 | 108.25471698113208 | -19.636860591766734 |        g4 |
+
+The table reveals that the `pressureDiff` value `-19.636860591766734` from station g4 and `-19.049240090497733` from station g3 are higher than 15, therefore there is a change in state that marks the `needMaintenance` value as "true" and would require that station to need work to turn that value back to `false`. 
\ No newline at end of file
diff --git a/content/influxdb/v2.2/query-data/common-queries/multiple-fields-in-calculations.md b/content/influxdb/v2.2/query-data/common-queries/multiple-fields-in-calculations.md
new file mode 100644
index 000000000..d2d565ffc
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/common-queries/multiple-fields-in-calculations.md
@@ -0,0 +1,106 @@
+---
+title: Use multiple fields in a calculation
+description: >
+  Query multiple fields, pivot results, and use multiple field values to
+  calculate new values in query results.
+influxdb/v2.2/tags: [queries]
+menu:
+  influxdb_2_2:
+    parent: Common queries
+weight: 103
+---
+
+To use values from multiple fields in a mathematic calculation, complete the following steps:
+
+1. [Filter by fields required in your calculation](#filter-by-fields)
+2. [Pivot fields into columns](#pivot-fields-into-columns)
+3. [Perform the mathematic calculation](#perform-the-calculation)
+
+## Filter by fields
+Use [`filter()`](/{{< latest "flux" >}}/stdlib/universe/filter/)
+to return only the fields necessary for your calculation.
+Use the [`or` logical operator](/{{< latest "flux" >}}/spec/operators/#logical-operators)
+to filter by multiple fields.
+
+The following example queries two fields, `A` and `B`:
+
+```js
+from(bucket: "example-bucket")
+    |> range(start: -1m)
+    |> filter(fn: (r) => r._field == "A" or r._field == "B")
+```
+
+This query returns one or more tables for each field. For example:
+
+{{< flex >}}
+{{% flex-content %}}
+| _time                | _field | _value |
+|:-----                |:------:| ------:|
+| 2021-01-01T00:00:00Z | A      | 12.4   |
+| 2021-01-01T00:00:15Z | A      | 12.2   |
+| 2021-01-01T00:00:30Z | A      | 11.6   |
+| 2021-01-01T00:00:45Z | A      | 11.9   |
+{{% /flex-content %}}
+{{% flex-content %}}
+| _time                | _field | _value |
+|:-----                |:------:| ------:|
+| 2021-01-01T00:00:00Z | B      | 3.1    |
+| 2021-01-01T00:00:15Z | B      | 4.8    |
+| 2021-01-01T00:00:30Z | B      | 2.2    |
+| 2021-01-01T00:00:45Z | B      | 3.3    |
+{{% /flex-content %}}
+{{< /flex >}}
+
+## Pivot fields into columns
+Use [`pivot()`](/{{< latest "flux" >}}/stdlib/universe/pivot/)
+to align multiple fields by time.
+
+{{% note %}}
+To correctly pivot on `_time`, points for each field must have identical timestamps.
+If timestamps are irregular or do not align perfectly, see
+[Normalize irregular timestamps](/influxdb/v2.2/query-data/flux/manipulate-timestamps/#normalize-irregular-timestamps).
+{{% /note %}}
+
+```js
+// ...
+  |> pivot(rowKey: ["_time"], columnKey: ["_field"], valueColumn: "_value")
+```
+
+Using the queried data [above](#filter-by-fields), this `pivot()` function returns:
+
+| _time                | A      | B      |
+|:-----                | ------:| ------:|
+| 2021-01-01T00:00:00Z | 12.4   | 3.1    |
+| 2021-01-01T00:00:15Z | 12.2   | 4.8    |
+| 2021-01-01T00:00:30Z | 11.6   | 2.2    |
+| 2021-01-01T00:00:45Z | 11.9   | 3.3    |
+
+## Perform the calculation
+Use [`map()`](/{{< latest "flux" >}}/stdlib/universe/map/)
+to perform the mathematic operation using column values as operands.
+
+The following example uses values in the `A` and `B` columns to calculate a new `_value` column:
+
+```js
+// ...
+    |> map(fn: (r) => ({ r with _value: r.A * r.B }))
+```
+
+Using the pivoted data above, this `map()` function returns:
+
+| _time                | A      | B      | _value |
+|:-----                | ------:| ------:| ------:|
+| 2021-01-01T00:00:00Z | 12.4   | 3.1    | 38.44  |
+| 2021-01-01T00:00:15Z | 12.2   | 4.8    | 58.56  |
+| 2021-01-01T00:00:30Z | 11.6   | 2.2    | 25.52  |
+| 2021-01-01T00:00:45Z | 11.9   | 3.3    | 39.27  |
+
+## Full example query
+
+```js
+from(bucket: "example-bucket")
+    |> range(start: -1m)
+    |> filter(fn: (r) => r._field == "A" or r._field == "B")
+    |> pivot(rowKey: ["_time"], columnKey: ["_field"], valueColumn: "_value")
+    |> map(fn: (r) => ({r with _value: r.A * r.B}))
+```
diff --git a/content/influxdb/v2.2/query-data/common-queries/operate-on-columns.md b/content/influxdb/v2.2/query-data/common-queries/operate-on-columns.md
new file mode 100644
index 000000000..04366293f
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/common-queries/operate-on-columns.md
@@ -0,0 +1,137 @@
+---
+title: Operate on columns
+description: >
+  Find and count unique values, recalculate the `_value` column, and use values to calculate a new column.
+influxdb/v2.2/tags: [queries]
+aliases: 
+  - /influxdb/v2.2/query-data/common-queries/count_unique_values_for_column/
+  - /influxdb/v2.2/query-data/common-queries/recalculate_value_column/
+  - /influxdb/v2.2/query-data/common-queries/calculate_new_column/
+menu:
+  influxdb_2_2:
+    name: Operate on columns
+    parent: Common queries
+weight: 100  
+---
+
+Use the following common queries to operate on columns:
+
+- [Find and count unique values in a column](#find-and-count-unique-values-in-a-column)
+- [Recalculate the _values column](#recalculate-the-_values-column)
+- [Calculate a new column](#calculate-a-new-column)
+
+{{% note %}}
+These examples use [NOAA water sample data](/influxdb/v2.2/reference/sample-data/#noaa-water-sample-data).
+{{% /note %}}
+
+## Find and count unique values in a column
+
+Find and count the number of unique values in a specified column.
+The following examples find and count unique locations where data was collected.
+
+### Find unique values
+
+This query:
+
+  - Uses [`group()`](/{{< latest "flux" >}}/stdlib/universe/group/) to ungroup data and return results in a single table.
+  - Uses [`keep()`](/{{< latest "flux" >}}/stdlib/universe/keep/) and [`unique()`](/{{< latest "flux" >}}/stdlib/universe/selectors/unique/) to return unique values in the specified column.
+
+```js
+from(bucket: "noaa")
+    |> range(start: -30d)
+    |> group()
+    |> keep(columns: ["location"])
+    |> unique(column: "location")
+```
+
+#### Example results
+| location     |
+|:--------     |
+| coyote_creek |
+| santa_monica |
+
+### Count unique values
+
+This query:
+
+- Uses [`group()`](/{{< latest "flux" >}}/stdlib/universe/group/) to ungroup data and return results in a single table.
+- Uses [`keep()`](/{{< latest "flux" >}}/stdlib/universe/keep/), [`unique()`](/{{< latest "flux" >}}/stdlib/universe/unique/), and then [`count()`](/{{< latest "flux" >}}/stdlib/universe/count/) to count the number of unique values.
+
+```js
+from(bucket: "noaa")
+    |> group()
+    |> unique(column: "location")
+    |> count(column: "location")
+```
+
+#### Example results
+
+| location  |
+| ---------:|
+| 2         |
+
+
+## Recalculate the _values column
+
+To recalculate the `_value` column, use the `with` operator in [`map()`](/{{< latest "flux" >}}/stdlib/universe/map/) to overwrite the existing `_value` column.
+
+The following query:
+
+  - Uses [`filter()`](/{{< latest "flux" >}}/stdlib/universe/filter/) to filter the `average_temperature` measurement.
+  - Uses [`map()`](/{{< latest "flux" >}}/stdlib/universe/map/) to convert Fahrenheit temperature values into Celsius.
+
+```js
+
+from(bucket: "noaa")
+    |> filter(fn: (r) => r._measurement == "average_temperature")
+    |> range(start: -30d)
+    |> map(fn: (r) => ({r with _value: (float(v: r._value) - 32.0) * 5.0 / 9.0} ))
+```
+
+| _field  | _measurement        | _start               | _stop                | _time                | location     | _value             |
+|:------  |:------------        |:------               |:-----                |:-----                |:--------     | ------:            |
+| degrees | average_temperature | 1920-03-05T22:10:01Z | 2020-03-05T22:10:01Z | 2019-08-17T00:00:00Z | coyote_creek | 27.77777777777778  |
+| degrees | average_temperature | 1920-03-05T22:10:01Z | 2020-03-05T22:10:01Z | 2019-08-17T00:06:00Z | coyote_creek | 22.77777777777778  |
+| degrees | average_temperature | 1920-03-05T22:10:01Z | 2020-03-05T22:10:01Z | 2019-08-17T00:12:00Z | coyote_creek | 30                 |
+| degrees | average_temperature | 1920-03-05T22:10:01Z | 2020-03-05T22:10:01Z | 2019-08-17T00:18:00Z | coyote_creek | 31.666666666666668 |
+| degrees | average_temperature | 1920-03-05T22:10:01Z | 2020-03-05T22:10:01Z | 2019-08-17T00:24:00Z | coyote_creek | 25                 |
+| degrees | average_temperature | 1920-03-05T22:10:01Z | 2020-03-05T22:10:01Z | 2019-08-17T00:30:00Z | coyote_creek | 21.11111111111111  |
+| degrees | average_temperature | 1920-03-05T22:10:01Z | 2020-03-05T22:10:01Z | 2019-08-17T00:36:00Z | coyote_creek | 28.88888888888889  |
+| degrees | average_temperature | 1920-03-05T22:10:01Z | 2020-03-05T22:10:01Z | 2019-08-17T00:42:00Z | coyote_creek | 24.444444444444443 |
+| degrees | average_temperature | 1920-03-05T22:10:01Z | 2020-03-05T22:10:01Z | 2019-08-17T00:48:00Z | coyote_creek | 29.444444444444443 |
+| degrees | average_temperature | 1920-03-05T22:10:01Z | 2020-03-05T22:10:01Z | 2019-08-17T00:54:00Z | coyote_creek | 26.666666666666668 |
+| degrees | average_temperature | 1920-03-05T22:10:01Z | 2020-03-05T22:10:01Z | 2019-08-17T01:00:00Z | coyote_creek | 21.11111111111111  |
+| •••     | •••                 | •••                  | •••                  | •••                  | •••          | •••                |
+
+## Calculate a new column
+
+To use values in a row to calculate and add a new column, use `map()`.
+This example below converts temperature from Fahrenheit to Celsius and maps the Celsius value to a new `celsius` column.
+
+The following query:
+
+  - Uses [`filter()`](/{{< latest "flux" >}}/stdlib/universe/filter/) to filter the `average_temperature` measurement.
+  - Uses [`map()`](/{{< latest "flux" >}}/stdlib/universe/map/) to create a new column calculated from existing values in each row.
+
+```js
+from(bucket: "noaa")
+    |> filter(fn: (r) => r._measurement == "average_temperature")
+    |> range(start: -30d)
+    |> map(fn: (r) => ({r with celsius: (r._value - 32.0) * 5.0 / 9.0}))
+```
+
+#### Example results
+
+| _start               | _stop                | _field  | _measurement        | location     | _time                | _value | celsius |
+|:------               |:-----                |:------: |:------------:       |:--------:    |:-----                | ------:| -------:|
+| 1920-03-05T22:10:01Z | 2020-03-05T22:10:01Z | degrees | average_temperature | coyote_creek | 2019-08-17T00:00:00Z | 82     | 27.78   |
+| 1920-03-05T22:10:01Z | 2020-03-05T22:10:01Z | degrees | average_temperature | coyote_creek | 2019-08-17T00:06:00Z | 73     | 22.78   |
+| 1920-03-05T22:10:01Z | 2020-03-05T22:10:01Z | degrees | average_temperature | coyote_creek | 2019-08-17T00:12:00Z | 86     | 30.00   |
+| 1920-03-05T22:10:01Z | 2020-03-05T22:10:01Z | degrees | average_temperature | coyote_creek | 2019-08-17T00:18:00Z | 89     | 31.67   |
+| 1920-03-05T22:10:01Z | 2020-03-05T22:10:01Z | degrees | average_temperature | coyote_creek | 2019-08-17T00:24:00Z | 77     | 25.00   |
+| 1920-03-05T22:10:01Z | 2020-03-05T22:10:01Z | degrees | average_temperature | coyote_creek | 2019-08-17T00:30:00Z | 70     | 21.11   |
+| 1920-03-05T22:10:01Z | 2020-03-05T22:10:01Z | degrees | average_temperature | coyote_creek | 2019-08-17T00:36:00Z | 84     | 28.89   |
+| 1920-03-05T22:10:01Z | 2020-03-05T22:10:01Z | degrees | average_temperature | coyote_creek | 2019-08-17T00:42:00Z | 76     | 24.44   |
+| 1920-03-05T22:10:01Z | 2020-03-05T22:10:01Z | degrees | average_temperature | coyote_creek | 2019-08-17T00:48:00Z | 85     | 29.44   |
+| 1920-03-05T22:10:01Z | 2020-03-05T22:10:01Z | degrees | average_temperature | coyote_creek | 2019-08-17T00:54:00Z | 80     | 26.67   |
+| •••                  | •••                  | •••     | •••                 | •••          | •••                  | •••    | •••     |
diff --git a/content/influxdb/v2.2/query-data/execute-queries/_index.md b/content/influxdb/v2.2/query-data/execute-queries/_index.md
new file mode 100644
index 000000000..971e410cd
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/execute-queries/_index.md
@@ -0,0 +1,17 @@
+---
+title: Execute queries
+seotitle: Different ways to query InfluxDB
+description: There are multiple ways to query data from InfluxDB including the InfluxDB UI, CLI, and API.
+weight: 103
+menu:
+  influxdb_2_2:
+    name: Execute queries
+    parent: Query data
+influxdb/v2.2/tags: [query]
+---
+
+There are multiple ways to execute queries with InfluxDB. Choose from the following options:
+
+{{< children >}}
+
+
diff --git a/content/influxdb/v2.2/query-data/execute-queries/data-explorer.md b/content/influxdb/v2.2/query-data/execute-queries/data-explorer.md
new file mode 100644
index 000000000..07cb3b125
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/execute-queries/data-explorer.md
@@ -0,0 +1,101 @@
+---
+title: Query in Data Explorer
+description: >
+  Query InfluxDB using the InfluxDB user interface (UI) Data Explorer. Discover how to query data in InfluxDB 2.1 using the InfluxDB UI.
+aliases: 
+  - /influxdb/v2.2/visualize-data/explore-metrics/
+weight: 201
+menu:
+  influxdb_2_2:
+    name: Query with Data Explorer
+    parent: Execute queries
+influxdb/v2.2/tags: [query]
+---
+
+Build, execute, and visualize your queries in InfluxDB UI's **Data Explorer**.
+
+![Data Explorer with Flux](/img/influxdb/2-0-data-explorer.png)
+
+Move seamlessly between using the Flux builder or templates and manually editing the query.
+Choose between [visualization types](/influxdb/v2.2/visualize-data/visualization-types/) for your query.
+
+## Query data with Flux and the Data Explorer
+
+Flux is a functional data scripting language designed for querying,
+analyzing, and acting on time series data.
+See [Get started with Flux](/influxdb/v2.2/query-data/get-started) to learn more about Flux.
+
+1. In the navigation menu on the left, click **Data Explorer**.
+
+    {{< nav-icon "data-explorer" >}}
+
+2. Use the Flux builder in the bottom panel to create a Flux query:
+   - Select a bucket to define your data source or select `+ Create Bucket` to add a new bucket.
+   - Edit your time range with the [time range option](#select-time-range) in the dropdown menu.
+   - Add filters to narrow your data by selecting attributes or columns in the dropdown menu.
+   - Select **Group** from the **Filter** dropdown menu to group data into tables. For more about how grouping data in Flux works, see [Group data](/influxdb/v2.2/query-data/flux/group-data/).    
+3. Alternatively, click **Script Editor** to manually edit the query.
+   To switch back to the query builder, click **Query Builder**. Note that your updates from the Script Editor will not be saved.
+4. Use the **Functions** list to review the available Flux functions.
+   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.
+  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.
+   - 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.
+
+## Visualize your query
+
+- Select an available [visualization types](/influxdb/v2.2/visualize-data/visualization-types/) from the dropdown menu in the upper-left:
+
+    {{< img-hd src="/img/influxdb/2-0-visualizations-dropdown.png" title="Visualization dropdown" />}}
+
+## Control your dashboard cell
+
+To open the cell editor overlay, click the gear icon in the upper right of a cell and select **Configure**.
+ The cell editor overlay opens.
+
+### 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. 
+
+ {{< img-hd src="/img/influxdb/cloud-controls-view-raw-data.png" alt="View raw data" />}}
+
+### Save as CSV
+
+Click the CSV icon to save the cells contents as a CSV file.
+
+### Manually refresh dashboard
+
+Click the refresh button ({{< icon "refresh" >}}) to manually refresh the dashboard's data.
+
+### Select time range
+
+1. Select from the time range options in the dropdown menu.
+
+    {{< img-hd src="/img/influxdb/2-0-controls-time-range.png" alt="Select time range" />}}
+
+2. Select **Custom Time Range** to enter a custom time range with precision up to nanoseconds.
+The default time range is 5m.
+
+> The custom time range uses the selected timezone (local time or UTC).
+
+### Query Builder or Script Editor
+
+Click **Query Builder** to use the builder to create a Flux query. Click **Script Editor** to manually edit the query.
+
+#### Keyboard shortcuts
+
+In **Script Editor** mode, the following keyboard shortcuts are available:
+
+| Key                            | Description                                 |
+|--------------------------------|---------------------------------------------|
+| `Control + /` (`⌘ + /` on Mac) | Comment/uncomment current or selected lines |
+| `Control + Enter`              | Submit query                                |
+
+## Save your query as a dashboard cell or task
+
+- Click **Save as** in the upper right, and then:
+  - To add your query to a dashboard, click **Dashboard Cell**.
+  - To save your query as a task, click **Task**.
+  - To save your query as a variable, click **Variable**.
diff --git a/content/influxdb/v2.2/query-data/execute-queries/flux-repl.md b/content/influxdb/v2.2/query-data/execute-queries/flux-repl.md
new file mode 100644
index 000000000..4489c471d
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/execute-queries/flux-repl.md
@@ -0,0 +1,19 @@
+---
+title: Query in the Flux REPL
+description: Query InfluxDB using the Flux REPL. Discover how to query data in InfluxDB 2.2 using the Flux REPL.
+weight: 203
+menu:
+  influxdb_2_2:
+    name: Query in the Flux REPL
+    parent: Execute queries
+influxdb/v2.2/tags: [query]
+---
+
+The [Flux REPL](/influxdb/v2.2/tools/repl/) starts an interactive
+Read-Eval-Print Loop (REPL) where you can write and execute Flux queries.
+
+```sh
+./flux repl
+```
+
+For more information, see [Use the Flux REPL](/influxdb/v2.2/tools/repl/).
diff --git a/content/influxdb/v2.2/query-data/execute-queries/influx-api.md b/content/influxdb/v2.2/query-data/execute-queries/influx-api.md
new file mode 100644
index 000000000..dbeaa8d1a
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/execute-queries/influx-api.md
@@ -0,0 +1,111 @@
+---
+title: Query with the InfluxDB API
+description: Query InfluxDB with the InfluxDB API. Discover how to query data in InfluxDB 2.1 using the InfluxDB API.
+weight: 202
+menu:
+  influxdb_2_2:
+    name: Query with the InfluxDB API
+    parent: Execute queries
+influxdb/v2.2/tags: [query]
+---
+
+The [InfluxDB v2 API](/influxdb/v2.2/reference/api) provides a programmatic interface for all interactions with InfluxDB.
+To query InfluxDB {{< current-version >}}, do one of the following:
+
+- Send a Flux query request to the [`/api/v2/query`](/influxdb/v2.2/api/#operation/PostQueryAnalyze) endpoint.
+- Send an InfluxQL query request to the [/query 1.x compatibility API](/influxdb/v2.2/reference/api/influxdb-1x/query/).
+
+In your request, set the following:
+
+- Your organization via the `org` or `orgID` URL parameters.
+- `Authorization` header to `Token ` + your API token.
+- `Accept` header to `application/csv`.
+- `Content-type` header to `application/vnd.flux` (Flux only) or `application/json` (Flux or InfluxQL).
+- Query in Flux or InfluxQL with the request's raw data.
+
+{{% note %}}
+#### Use gzip to compress the query response
+
+To compress the query response, set the `Accept-Encoding` header to `gzip`.
+This saves network bandwidth, but increases server-side load.
+
+We recommend only using gzip compression on responses that are larger than 1.4 KB.
+If the response is smaller than 1.4 KB, gzip encoding will always return a 1.4 KB
+response, despite the uncompressed response size.
+1500 bytes (~1.4 KB) is the maximum transmission unit (MTU) size for the public
+network and is the largest packet size allowed at the network layer.
+{{% /note %}}
+
+#### Flux - Example query request
+
+Below is an example `curl` request that sends a Flux query to InfluxDB {{< current-version >}}:
+
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[Without compression](#)
+[With compression](#)
+{{% /code-tabs %}}
+
+{{% code-tab-content %}}
+```bash
+curl --request POST \
+  http://localhost:8086/api/v2/query?orgID=INFLUX_ORG_ID  \
+  --header 'Authorization: Token INFLUX_TOKEN' \
+  --header 'Accept: application/csv' \
+  --header 'Content-type: application/vnd.flux' \
+  --data 'from(bucket:"example-bucket")
+        |> range(start: -12h)
+        |> filter(fn: (r) => r._measurement == "example-measurement")
+        |> aggregateWindow(every: 1h, fn: mean)'
+```
+{{% /code-tab-content %}}
+
+{{% code-tab-content %}}
+```bash
+curl --request POST \
+  http://localhost:8086/api/v2/query?orgID=INFLUX_ORG_ID \
+  --header 'Authorization: Token INFLUX_TOKEN' \
+  --header 'Accept: application/csv' \
+  --header 'Content-type: application/vnd.flux' \
+  --header 'Accept-Encoding: gzip' \
+  --data 'from(bucket:"example-bucket")
+        |> range(start: -12h)
+        |> filter(fn: (r) => r._measurement == "example-measurement")
+        |> aggregateWindow(every: 1h, fn: mean)'
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+#### InfluxQL - Example query request
+
+Below is an example `curl` request that sends an InfluxQL query to InfluxDB {{< current-version >}}:
+
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[Without compression](#)
+[With compression](#)
+{{% /code-tabs %}}
+
+{{% code-tab-content %}}
+```bash
+curl --request -G http://localhost:8086/query?orgID=INFLUX_ORG_ID&database=MyDB&retention_policy=MyRP \
+  --header 'Authorization: Token INFLUX_TOKEN' \
+  --header 'Accept: application/csv' \
+  --header 'Content-type: application/json' \
+  --data-urlencode "q=SELECT used_percent FROM example-db.example-rp.example-measurement WHERE host=host1"
+```
+{{% /code-tab-content %}}
+
+{{% code-tab-content %}}
+```bash
+curl --request -G http://localhost:8086/query?orgID=INFLUX_ORG_ID&database=MyDB&retention_policy=MyRP \
+  --header 'Authorization: Token INFLUX_TOKEN' \
+  --header 'Accept: application/csv' \
+  --header 'Content-type: application/json' \
+  --header 'Accept-Encoding: gzip' \
+  --data-urlencode "q=SELECT used_percent FROM example-db.example-rp.example-measurement WHERE host=host1"
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+InfluxDB returns the query results in [annotated CSV](/influxdb/v2.2/reference/syntax/annotated-csv/).
diff --git a/content/influxdb/v2.2/query-data/execute-queries/influx-query.md b/content/influxdb/v2.2/query-data/execute-queries/influx-query.md
new file mode 100644
index 000000000..22b539dfd
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/execute-queries/influx-query.md
@@ -0,0 +1,41 @@
+---
+title: Use the influx query command
+description: Query InfluxDB using the influx CLI. Discover how to query data in InfluxDB 2.1 using `influx query`.
+weight: 204
+menu:
+  influxdb_2_2:
+    name: Use the influx CLI
+    parent: Execute queries
+influxdb/v2.2/tags: [query]
+related:
+  - /influxdb/v2.2/reference/cli/influx/query/
+---
+
+Use the [`influx query` command](/influxdb/v2.2/reference/cli/influx/query) to query data in InfluxDB using Flux.
+Pass Flux queries to the command as either a file or via stdin.
+
+###### Run a query from a file
+
+```bash
+influx query --file /path/to/query.flux
+```
+
+###### Pass raw Flux via stdin pipe
+
+```bash
+influx query - # Return to open the pipe
+
+data = from(bucket: "example-bucket") |> range(start: -10m) # ...
+# ctrl-d to close the pipe and submit the query
+```
+
+{{% note %}}
+#### Remove unnecessary columns in large datasets
+When using the `influx query` command to query and download large datasets,
+drop columns such as `_start` and `_stop` to optimize the download file size.
+
+```js
+// ...
+    |> drop(columns: ["_start", "_stop"])
+```
+{{% /note %}}
diff --git a/content/influxdb/v2.2/query-data/execute-queries/query-sample-data.md b/content/influxdb/v2.2/query-data/execute-queries/query-sample-data.md
new file mode 100644
index 000000000..8b1a8b347
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/execute-queries/query-sample-data.md
@@ -0,0 +1,88 @@
+---
+title: Query sample data 
+description: >
+  Explore InfluxDB OSS with our sample data buckets. 
+menu:
+  influxdb_2_2::
+    name: Query with sample data
+    parent: Execute queries
+weight: 10
+---
+
+Use **InfluxDB OSS** sample datasets to quickly access data that lets you explore and familiarize yourself with InfluxDB Cloud without requiring you to have or write your own data.
+
+- [Choose sample data](#choose-sample-data)
+- [Explore sample data](#explore-sample-data)
+- [Create sample data dashboards](#create-sample-data-dashboards)
+
+{{% note %}}
+#### Network bandwidth
+
+Each execution of `sample.data()` downloads the specified dataset from **Amazon S3**.
+If using [InfluxDB Cloud](/influxdb/cloud/) or a hosted InfluxDB OSS instance,
+you may see additional network bandwidth costs when using this function.
+Approximate sample dataset sizes are listed for each [sample dataset](/influxdb/v2.2/reference/sample-data/#sample-datasets) and in the output of [`sample.list()`](/influxdb/v2.2/reference/flux/stdlib/influxdb-sample/list/). 
+
+{{% /note %}}
+
+## Choose sample data
+
+1. Choose from the following sample datasets:
+   - **Air sensor sample data**: Explore, visualize, and monitor humidity, temperature, and carbon monoxide levels in the air.
+   - **Bird migration sample data**: Explore, visualize, and monitor the latitude and longitude of bird migration patterns.
+   - **NOAA NDBC sample data**: Explore, visualize, and monitor NDBC's observations from their buoys. This data observes air temperature, wind speed, and more from specific locations. 
+   - **NOAA water sample data**: Explore, visualize, and monitor temperature, water level, pH, and quality from specific locations.
+   - **USGS Earthquake data**: Explore, visualize, and monitor earthquake monitoring data. This data includes alerts, cdi, quarry blast, magnitide, and more.  
+2. Do one of the following to download sample data: 
+   - [Add sample data with community template](#add-sample-data-with-community-templates)
+   - [Add sample data using the InfluxDB UI](#add-sample-data)
+
+### Add sample data with community template
+
+1. Visit the **InfluxDB templates page** in the InfluxDB OSS UI. Click **Settings** > **Templates** in the navigation menu on the left.
+
+    {{< nav-icon "settings" >}}
+      
+2. Paste the Sample Data community temple URL in **resource manifest file** field:
+
+    ```
+    https://github.com/influxdata/community-templates/blob/master/sample-data/sample-data.yml
+    ```
+
+## Explore sample data
+Use the [Data Explorer](/influxdb/cloud/visualize-data/explore-metrics/)
+to query and visualize data in sample data buckets.
+
+In the navigation menu on the left, click **Data Explorer**.
+
+{{< nav-icon "explore" >}}
+
+### Add sample data
+
+1. In the navigation menu on the left, click **Data (Load Data)** > **Buckets**.
+
+    {{< nav-icon "data" >}}
+
+2. Click **{{< icon "plus" >}} 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.
+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**.
+6. Paste the `sample.data()` function.
+7. Click **Submit** to run the query.
+
+For more information about querying in the Script Editor, see how to [Query data with Flux and the Data Explorer](/influxdb/cloud/query-data/execute-queries/data-explorer/#query-data-with-flux-and-the-data-explorer).
+
+## Create sample data dashboards
+
+After adding a sample data bucket, create a dashboard specific to the sample dataset:
+
+1. Click **Boards (Dashboards)** in the navigation menu on the left.
+
+    {{< nav-icon "dashboards" >}}
+
+2. Click **Create Dashboard > New Dashboard**, and name the dashboard after your bucket. 
+3. Click **Add Cell**, and select your sample data bucket.
+4. Click **Script Editor**.
+5. Copy and paste the `sample.data()` function into the script editor.
+6. Click **Submit** to run the query.
+6. Define the variables of your sample data.
diff --git a/content/influxdb/v2.2/query-data/flux/_index.md b/content/influxdb/v2.2/query-data/flux/_index.md
new file mode 100644
index 000000000..168f9430d
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/flux/_index.md
@@ -0,0 +1,35 @@
+---
+title: Query data with Flux
+description: Guides that walk through both common and complex queries and use cases for Flux.
+weight: 102
+influxdb/v2.2/tags: [flux, query]
+menu:
+  influxdb_2_2:
+    name: Query with Flux
+    parent: Query data
+alias:
+  - /influxdb/v2.2/query-data/guides/
+---
+
+The following guides walk through both common and complex queries and use cases for Flux.
+
+{{% note %}}
+#### Example data variable
+Many of the examples provided in the following guides use a `data` variable,
+which represents a basic query that filters data by measurement and field.
+`data` is defined as:
+
+```js
+data = from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement" and r._field == "example-field")
+```
+{{% /note %}}
+
+## Flux query guides
+
+{{< children type="anchored-list" pages="all" >}}
+
+---
+
+{{< children pages="all" readmore=true hr=true >}}
diff --git a/content/influxdb/v2.2/query-data/flux/calculate-percentages.md b/content/influxdb/v2.2/query-data/flux/calculate-percentages.md
new file mode 100644
index 000000000..d80015c92
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/flux/calculate-percentages.md
@@ -0,0 +1,211 @@
+---
+title: Calculate percentages with Flux
+list_title: Calculate percentages
+description: >
+  Use [`pivot()` or `join()`](/influxdb/v2.2/query-data/flux/mathematic-operations/#pivot-vs-join)
+  and the `map()` function to align operand values into rows and calculate a percentage.
+menu:
+  influxdb_2_2:
+    name: Calculate percentages
+    parent: Query with Flux
+weight: 209
+aliases:
+ - /influxdb/v2.2/query-data/guides/calculate-percentages/
+related:
+  - /influxdb/v2.2/query-data/flux/mathematic-operations
+  - /{{< latest "flux" >}}/stdlib/universe/map
+  - /{{< latest "flux" >}}/stdlib/universe/pivot
+  - /{{< latest "flux" >}}/stdlib/universe/join
+list_query_example: percentages
+---
+
+Calculating percentages from queried data is a common use case for time series data.
+To calculate a percentage in Flux, operands must be in each row.
+Use `map()` to re-map values in the row and calculate a percentage.
+
+**To calculate percentages**
+
+1. Use [`from()`](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/from/),
+   [`range()`](/{{< latest "flux" >}}/stdlib/universe/range/) and
+   [`filter()`](/{{< latest "flux" >}}/stdlib/universe/filter/) to query operands.
+2. Use [`pivot()` or `join()`](/influxdb/v2.2/query-data/flux/mathematic-operations/#pivot-vs-join)
+   to align operand values into rows.
+3. Use [`map()`](/{{< latest "flux" >}}/stdlib/universe/map/)
+   to divide the numerator operand value by the denominator operand value and multiply by 100.
+
+{{% note %}}
+The following examples use `pivot()` to align operands into rows because
+`pivot()` works in most cases and is more performant than `join()`.
+_See [Pivot vs join](/influxdb/v2.2/query-data/flux/mathematic-operations/#pivot-vs-join)._
+{{% /note %}}
+
+```js
+from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "m1" and r._field =~ /field[1-2]/ )
+    |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
+    |> map(fn: (r) => ({ r with _value: r.field1 / r.field2 * 100.0 }))
+```
+
+## GPU monitoring example
+The following example queries data from the gpu-monitor bucket and calculates the
+percentage of GPU memory used over time.
+Data includes the following:
+
+- **`gpu` measurement**
+- **`mem_used` field**: used GPU memory in bytes
+- **`mem_total` field**: total GPU memory in bytes
+
+### Query mem_used and mem_total fields
+```js
+from(bucket: "gpu-monitor")
+    |> range(start: 2020-01-01T00:00:00Z)
+    |> filter(fn: (r) => r._measurement == "gpu" and r._field =~ /mem_/)
+```
+
+###### Returns the following stream of tables:
+
+| _time                | _measurement | _field   | _value     |
+|:-----                |:------------:|:------:  | ------:    |
+| 2020-01-01T00:00:00Z | gpu          | mem_used | 2517924577 |
+| 2020-01-01T00:00:10Z | gpu          | mem_used | 2695091978 |
+| 2020-01-01T00:00:20Z | gpu          | mem_used | 2576980377 |
+| 2020-01-01T00:00:30Z | gpu          | mem_used | 3006477107 |
+| 2020-01-01T00:00:40Z | gpu          | mem_used | 3543348019 |
+| 2020-01-01T00:00:50Z | gpu          | mem_used | 4402341478 |
+
+<p style="margin:-2.5rem 0;"></p>
+
+| _time                | _measurement | _field    | _value     |
+|:-----                |:------------:|:------:   | ------:    |
+| 2020-01-01T00:00:00Z | gpu          | mem_total | 8589934592 |
+| 2020-01-01T00:00:10Z | gpu          | mem_total | 8589934592 |
+| 2020-01-01T00:00:20Z | gpu          | mem_total | 8589934592 |
+| 2020-01-01T00:00:30Z | gpu          | mem_total | 8589934592 |
+| 2020-01-01T00:00:40Z | gpu          | mem_total | 8589934592 |
+| 2020-01-01T00:00:50Z | gpu          | mem_total | 8589934592 |
+
+### Pivot fields into columns
+Use `pivot()` to pivot the `mem_used` and `mem_total` fields into columns.
+Output includes `mem_used` and `mem_total` columns with values for each corresponding `_time`.
+
+```js
+// ...
+    |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
+```
+
+###### Returns the following:
+
+| _time                | _measurement | mem_used   | mem_total  |
+|:-----                |:------------:| --------:  | ---------: |
+| 2020-01-01T00:00:00Z | gpu          | 2517924577 | 8589934592 |
+| 2020-01-01T00:00:10Z | gpu          | 2695091978 | 8589934592 |
+| 2020-01-01T00:00:20Z | gpu          | 2576980377 | 8589934592 |
+| 2020-01-01T00:00:30Z | gpu          | 3006477107 | 8589934592 |
+| 2020-01-01T00:00:40Z | gpu          | 3543348019 | 8589934592 |
+| 2020-01-01T00:00:50Z | gpu          | 4402341478 | 8589934592 |
+
+### Map new values
+Each row now contains the values necessary to calculate a percentage.
+Use `map()` to re-map values in each row.
+Divide `mem_used` by `mem_total` and multiply by 100 to return the percentage.
+
+{{% note %}}
+To return a precise float percentage value that includes decimal points, the example
+below casts integer field values to floats and multiplies by a float value (`100.0`).
+{{% /note %}}
+
+```js
+// ...
+    |> map(
+        fn: (r) => ({
+            _time: r._time,
+            _measurement: r._measurement,
+            _field: "mem_used_percent",
+            _value: float(v: r.mem_used) / float(v: r.mem_total) * 100.0
+        }),
+    )
+```
+##### Query results:
+
+| _time                | _measurement | _field           | _value  |
+|:-----                |:------------:|:------:          | ------: |
+| 2020-01-01T00:00:00Z | gpu          | mem_used_percent | 29.31   |
+| 2020-01-01T00:00:10Z | gpu          | mem_used_percent | 31.37   |
+| 2020-01-01T00:00:20Z | gpu          | mem_used_percent | 30.00   |
+| 2020-01-01T00:00:30Z | gpu          | mem_used_percent | 35.00   |
+| 2020-01-01T00:00:40Z | gpu          | mem_used_percent | 41.25   |
+| 2020-01-01T00:00:50Z | gpu          | mem_used_percent | 51.25   |
+
+### Full query
+```js
+from(bucket: "gpu-monitor")
+    |> range(start: 2020-01-01T00:00:00Z)
+    |> filter(fn: (r) => r._measurement == "gpu" and r._field =~ /mem_/ )
+    |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
+    |> map(
+        fn: (r) => ({
+            _time: r._time,
+            _measurement: r._measurement,
+            _field: "mem_used_percent",
+            _value: float(v: r.mem_used) / float(v: r.mem_total) * 100.0
+        }),
+    )
+```
+
+## Examples
+
+#### Calculate percentages using multiple fields
+```js
+from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> filter(fn: (r) => r._field == "used_system" or r._field == "used_user" or r._field == "total")
+    |> pivot(rowKey: ["_time"], columnKey: ["_field"], valueColumn: "_value")
+    |> map(
+        fn: (r) => ({
+            r with _value: float(v: r.used_system + r.used_user) / float(v: r.total) * 100.0
+        }),
+    )
+```
+
+#### Calculate percentages using multiple measurements
+
+1. Ensure measurements are in the same [bucket](/influxdb/v2.2/reference/glossary/#bucket).
+2. Use `filter()` to include data from both measurements.
+3. Use `group()` to ungroup data and return a single table.
+4. Use `pivot()` to pivot fields into columns.
+5. Use `map()` to re-map rows and perform the percentage calculation.
+
+<!-- -->
+```js
+from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => (r._measurement == "m1" or r._measurement == "m2") and (r._field == "field1" or r._field == "field2"))
+    |> group()
+    |> pivot(rowKey: ["_time"], columnKey: ["_field"], valueColumn: "_value")
+    |> map(fn: (r) => ({r with _value: r.field1 / r.field2 * 100.0}))
+```
+
+#### Calculate percentages using multiple data sources
+```js
+import "sql"
+import "influxdata/influxdb/secrets"
+
+pgUser = secrets.get(key: "POSTGRES_USER")
+pgPass = secrets.get(key: "POSTGRES_PASSWORD")
+pgHost = secrets.get(key: "POSTGRES_HOST")
+
+t1 = sql.from(
+    driverName: "postgres",
+    dataSourceName: "postgresql://${pgUser}:${pgPass}@${pgHost}",
+    query: "SELECT id, name, available FROM example_table",
+)
+
+t2 = from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement" and r._field == "example-field")
+
+join(tables: {t1: t1, t2: t2}, on: ["id"])
+    |> map(fn: (r) => ({r with _value: r._value_t2 / r.available_t1 * 100.0}))
+```
diff --git a/content/influxdb/v2.2/query-data/flux/conditional-logic.md b/content/influxdb/v2.2/query-data/flux/conditional-logic.md
new file mode 100644
index 000000000..2630ad96d
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/flux/conditional-logic.md
@@ -0,0 +1,224 @@
+---
+title: Query using conditional logic
+seotitle: Query using conditional logic in Flux
+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.2/tags: [conditionals, flux]
+menu:
+  influxdb_2_2:
+    name: Conditional logic
+    parent: Query with Flux
+weight: 220
+aliases:
+  - /influxdb/v2.2/query-data/guides/conditional-logic/
+related:
+  - /influxdb/v2.2/query-data/flux/query-fields/
+  - /{{< latest "flux" >}}/stdlib/universe/filter/
+  - /{{< latest "flux" >}}/stdlib/universe/map/
+  - /{{< latest "flux" >}}/stdlib/universe/reduce/
+list_code_example: |
+  ```js
+  if color == "green" then "008000" else "ffffff"
+  ```
+---
+
+Flux provides `if`, `then`, and `else` conditional expressions that allow for powerful and flexible Flux queries.
+
+If you're just getting started with Flux queries, check out the following:
+
+- [Get started with Flux](/{{< latest "flux" >}}/get-started/) for a conceptual overview of Flux and parts of a Flux query.
+- [Execute queries](/influxdb/v2.2/query-data/execute-queries/) to discover a variety of ways to run your queries.
+
+##### Conditional expression syntax
+```js
+// Pattern
+if <condition> then <action> else <alternative-action>
+
+// Example
+if color == "green" then "008000" else "ffffff"
+```
+
+Conditional expressions are most useful in the following contexts:
+
+- When defining variables.
+- When using functions that operate on a single row at a time (
+  [`filter()`](/{{< latest "flux" >}}/stdlib/universe/filter/),
+  [`map()`](/{{< latest "flux" >}}/stdlib/universe/map/),
+  [`reduce()`](/{{< latest "flux" >}}/stdlib/universe/reduce) ).
+
+## Evaluating conditional expressions
+
+Flux evaluates statements in order and stops evaluating once a condition matches.
+
+For example, given the following statement:
+
+```js
+if r._value > 95.0000001 and r._value <= 100.0 then
+    "critical"
+else if r._value > 85.0000001 and r._value <= 95.0 then
+    "warning"
+else if r._value > 70.0000001 and r._value <= 85.0 then
+    "high"
+else
+    "normal"
+```
+
+When `r._value` is 96, the output is "critical" and the remaining conditions are not evaluated.
+
+## Examples
+
+- [Conditionally set the value of a variable](#conditionally-set-the-value-of-a-variable)
+- [Create conditional filters](#create-conditional-filters)
+- [Conditionally transform column values with map()](#conditionally-transform-column-values-with-map)
+- [Conditionally increment a count with reduce()](#conditionally-increment-a-count-with-reduce)
+
+### Conditionally set the value of a variable
+The following example sets the `overdue` variable based on the
+`dueDate` variable's relation to `now()`.
+
+```js
+dueDate = 2019-05-01
+overdue = if dueDate < now() then true else false
+```
+
+### Create conditional filters
+The following example uses an example `metric` [dashboard variable](/influxdb/v2.2/visualize-data/variables/)
+to change how the query filters data.
+`metric` has three possible values:
+
+- Memory
+- CPU
+- Disk
+
+```js
+from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(
+        fn: (r) => if v.metric == "Memory" then
+            r._measurement == "mem" and r._field == "used_percent"
+        else if v.metric == "CPU" then
+            r._measurement == "cpu" and r._field == "usage_user"
+        else if v.metric == "Disk" then
+            r._measurement == "disk" and r._field == "used_percent"
+        else
+            r._measurement != "",
+    )
+```
+
+
+### Conditionally transform column values with map()
+The following example uses the [`map()` function](/{{< latest "flux" >}}/stdlib/universe/map/)
+to conditionally transform column values.
+It sets the `level` column to a specific string based on `_value` column.
+
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[No Comments](#)
+[Comments](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```js
+from(bucket: "example-bucket")
+    |> range(start: -5m)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+    |> map(
+        fn: (r) => ({r with
+            level: if r._value >= 95.0000001 and r._value <= 100.0 then
+                "critical"
+            else if r._value >= 85.0000001 and r._value <= 95.0 then
+                "warning"
+            else if r._value >= 70.0000001 and r._value <= 85.0 then
+                "high"
+            else
+                "normal",
+        }),
+    )
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```js
+from(bucket: "example-bucket")
+    |> range(start: -5m)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+    |> map(
+        fn: (r) => ({
+            // Retain all existing columns in the mapped row
+            r with
+            // Set the level column value based on the _value column
+            level: if r._value >= 95.0000001 and r._value <= 100.0 then
+                "critical"
+            else if r._value >= 85.0000001 and r._value <= 95.0 then
+                "warning"
+            else if r._value >= 70.0000001 and r._value <= 85.0 then
+                "high"
+            else
+                "normal",
+        }),
+    )
+```
+
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+### Conditionally increment a count with reduce()
+The following example uses the [`aggregateWindow()`](/{{< latest "flux" >}}/stdlib/universe/aggregatewindow/)
+and [`reduce()`](/{{< latest "flux" >}}/stdlib/universe/reduce/)
+functions to count the number of records in every five minute window that exceed a defined threshold.
+
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[No Comments](#)
+[Comments](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```js
+threshold = 65.0
+
+data = from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+    |> aggregateWindow(
+        every: 5m,
+        fn: (column, tables=<-) => tables
+            |> reduce(
+                identity: {above_threshold_count: 0.0},
+                fn: (r, accumulator) => ({
+                    above_threshold_count: if r._value >= threshold then
+                        accumulator.above_threshold_count + 1.0
+                    else
+                        accumulator.above_threshold_count + 0.0,
+                }),
+            ),
+    )
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```js
+threshold = 65.0
+
+from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+    // Aggregate data into 5 minute windows using a custom reduce() function
+    |> aggregateWindow(
+        every: 5m,
+        // Use a custom function in the fn parameter.
+        // The aggregateWindow fn parameter requires 'column' and 'tables' parameters.
+        fn: (column, tables=<-) => tables
+            |> reduce(
+                identity: {above_threshold_count: 0.0},
+                fn: (r, accumulator) => ({
+                    // Conditionally increment above_threshold_count if
+                    // r.value exceeds the threshold
+                    above_threshold_count: if r._value >= threshold then
+                        accumulator.above_threshold_count + 1.0
+                    else
+                        accumulator.above_threshold_count + 0.0,
+                }),
+            ),
+    )
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
diff --git a/content/influxdb/v2.2/query-data/flux/cumulativesum.md b/content/influxdb/v2.2/query-data/flux/cumulativesum.md
new file mode 100644
index 000000000..134e94744
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/flux/cumulativesum.md
@@ -0,0 +1,70 @@
+---
+title: Query cumulative sum
+seotitle: Query cumulative sum in Flux
+list_title: Cumulative sum
+description: >
+  Use the `cumulativeSum()` function to calculate a running total of values.
+weight: 210
+menu:
+  influxdb_2_2:
+    parent: Query with Flux
+    name: Cumulative sum
+influxdb/v2.2/tags: [query, cumulative sum]
+related:
+  - /{{< latest "flux" >}}/stdlib/universe/cumulativesum/
+list_query_example: cumulative_sum
+---
+
+Use the [`cumulativeSum()` function](/{{< latest "flux" >}}/stdlib/universe/cumulativesum/)
+to calculate a running total of values.
+`cumulativeSum` sums the values of subsequent records and returns each row updated with the summed total.
+
+{{< flex >}}
+{{% flex-content "half" %}}
+**Given the following input table:**
+
+| _time | _value |
+| ----- |:------:|
+| 0001  | 1      |
+| 0002  | 2      |
+| 0003  | 1      |
+| 0004  | 3      |
+{{% /flex-content %}}
+{{% flex-content "half" %}}
+**`cumulativeSum()` returns:**
+
+| _time | _value |
+| ----- |:------:|
+| 0001  | 1      |
+| 0002  | 3      |
+| 0003  | 4      |
+| 0004  | 7      |
+{{% /flex-content %}}
+{{< /flex >}}
+
+{{% note %}}
+The examples below use the [example data variable](/influxdb/v2.2/query-data/flux/#example-data-variable).
+{{% /note %}}
+
+##### Calculate the running total of values
+```js
+data
+    |> cumulativeSum()
+```
+
+## Use cumulativeSum() with aggregateWindow()
+[`aggregateWindow()`](/{{< latest "flux" >}}/stdlib/universe/aggregatewindow/)
+segments data into windows of time, aggregates data in each window into a single
+point, then removes the time-based segmentation.
+It is primarily used to [downsample data](/influxdb/v2.2/process-data/common-tasks/downsample-data/).
+
+`aggregateWindow()` expects an aggregate function that returns a single row for each time window.
+To use `cumulativeSum()` with `aggregateWindow`, use `sum` in `aggregateWindow()`,
+then calculate the running total of the aggregate values with `cumulativeSum()`.
+
+<!-- -->
+```js
+data
+    |> aggregateWindow(every: 5m, fn: sum)
+    |> cumulativeSum()
+```
diff --git a/content/influxdb/v2.2/query-data/flux/custom-functions/_index.md b/content/influxdb/v2.2/query-data/flux/custom-functions/_index.md
new file mode 100644
index 000000000..5e33942d4
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/flux/custom-functions/_index.md
@@ -0,0 +1,223 @@
+---
+title: Create custom Flux functions
+description: Create your own custom Flux functions to transform and operate on data.
+list_title: Custom functions
+influxdb/v2.2/tags: [functions, custom, flux]
+menu:
+  influxdb_2_2:
+    name: Custom functions
+    parent: Query with Flux
+weight: 220
+aliases:
+  - /influxdb/v2.2/query-data/guides/custom-functions/
+list_code_example: |
+  ```js
+  multByX = (tables=<-, x) => tables
+      |> map(fn: (r) => ({r with _value: r._value * x}))
+
+  data
+      |> multByX(x: 2.0)
+  ```
+---
+
+Flux's functional syntax lets you create custom functions.
+This guide walks through the basics of creating your own function.
+
+- [Function definition syntax](#function-definition-syntax)
+- [Use piped-forward data in a custom function](#use-piped-forward-data-in-a-custom-function)
+- [Define parameter defaults](#define-parameter-defaults)
+- [Define functions with scoped variables](#define-functions-with-scoped-variables)
+
+## Function definition syntax
+The basic syntax for defining functions in Flux is as follows:
+
+```js
+// Basic function definition syntax
+functionName = (functionParameters) => functionOperations
+```
+
+##### functionName
+The name used to call the function in your Flux script.  
+
+##### functionParameters
+A comma-separated list of parameters passed into the function and used in its operations.
+[Parameter defaults](#define-parameter-defaults) can be defined for each.  
+
+##### functionOperations
+Operations and functions that manipulate the input into the desired output.
+
+#### Basic function examples
+
+###### Example square function
+```js
+// Function definition
+square = (n) => n * n
+
+// Function usage
+> square(n:3)
+9
+```
+
+###### Example multiply function
+```js
+// Function definition
+multiply = (x, y) => x * y
+
+// Function usage
+> multiply(x: 2, y: 15)
+30
+```
+
+## Use piped-forward data in a custom function
+Most Flux functions process piped-forward data.
+To process piped-forward data, one of the function
+parameters must capture the input tables using the `<-` pipe-receive expression.
+
+In the example below, the `tables` parameter is assigned to the `<-` expression,
+which represents all data piped-forward into the function.
+`tables` is then piped-forward into other operations in the function definition.
+
+```js
+functionName = (tables=<-) => tables |> functionOperations
+```
+
+#### Pipe-forwardable function example
+
+###### Multiply row values by x
+The example below defines a `multByX` function that multiplies the `_value` column
+of each row in the input table by the `x` parameter.
+It uses the [`map()` function](/{{< latest "flux" >}}/stdlib/universe/map)
+to modify each `_value`.
+
+```js
+// Function definition
+multByX = (tables=<-, x) => tables
+    |> map(fn: (r) => ({r with _value: r._value * x}))
+
+// Function usage
+from(bucket: "example-bucket")
+    |> range(start: -1m)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+    |> multByX(x: 2.0)
+```
+
+## Define parameter defaults
+Use the `=` assignment operator to assign a default value to function parameters
+in your function definition:
+
+```js
+functionName = (param1=defaultValue1, param2=defaultValue2) => functionOperation
+```
+
+Defaults are overridden by explicitly defining the parameter in the function call.
+
+### Example functions with defaults
+
+#### Get a list of leaders
+The example below defines a `leaderBoard` function that returns a limited number
+of records sorted by values in specified columns.
+It uses the [`sort()` function](/{{< latest "flux" >}}/stdlib/universe/sort)
+to sort records in either descending or ascending order.
+It then uses the [`limit()` function](/{{< latest "flux" >}}/stdlib/universe/limit)
+to return a specified number of records from the sorted table.
+
+```js
+// Function definition
+leaderBoard = (tables=<-, limit=4, columns=["_value"], desc=true) => tables
+    |> sort(columns: columns, desc: desc)
+    |> limit(n: limit)
+
+// Function usage
+// Get the 4 highest scoring players
+from(bucket: "example-bucket")
+    |> range(start: -1m)
+    |> filter(fn: (r) => r._measurement == "player-stats" and r._field == "total-points")
+    |> leaderBoard()
+
+// Get the 10 shortest race times
+from(bucket: "example-bucket")
+    |> range(start: -1m)
+    |> filter(fn: (r) => r._measurement == "race-times" and r._field == "elapsed-time")
+    |> leaderBoard(limit: 10, desc: false)
+```
+
+## Define functions with scoped variables
+To create custom functions with variables scoped to the function, place your
+function operations and variables inside of a [block (`{}`)](/influxdb/v2.2/reference/flux/language/blocks/)
+and use a `return` statement to return a specific variable.
+
+```js
+functionName = (functionParameters) => {
+    exampleVar = "foo"
+    
+    return exampleVar
+}
+```
+
+### Example functions with scoped variables
+
+- [Return an alert level based on a value](#return-an-alert-level-based-on-a-value)
+- [Convert a HEX color code to a name](#convert-a-hex-color-code-to-a-name)
+
+#### Return an alert level based on a value
+The following function uses conditional logic to return an alert level based on
+a numeric input value:
+
+```js
+alertLevel = (v) => {
+    level = if float(v: v) >= 90.0 then
+        "crit"
+    else if float(v: v) >= 80.0 then
+        "warn"
+    else if float(v: v) >= 65.0 then
+        "info"
+    else
+        "ok"
+
+    return level
+}
+
+alertLevel(v: 87.3)
+// Returns "warn"
+```
+
+#### Convert a HEX color code to a name
+The following function converts a hexadecimal (HEX) color code to the equivalent HTML color name.
+The functions uses the [Flux dictionary package](/{{< latest "flux" >}}/stdlib/dict/)
+to create a dictionary of HEX codes and their corresponding names.
+
+```js
+import "dict"
+
+hexName = (hex) => {
+    hexNames = dict.fromList(
+        pairs: [
+            {key: "#00ffff", value: "Aqua"},
+            {key: "#000000", value: "Black"},
+            {key: "#0000ff", value: "Blue"},
+            {key: "#ff00ff", value: "Fuchsia"},
+            {key: "#808080", value: "Gray"},
+            {key: "#008000", value: "Green"},
+            {key: "#00ff00", value: "Lime"},
+            {key: "#800000", value: "Maroon"},
+            {key: "#000080", value: "Navy"},
+            {key: "#808000", value: "Olive"},
+            {key: "#800080", value: "Purple"},
+            {key: "#ff0000", value: "Red"},
+            {key: "#c0c0c0", value: "Silver"},
+            {key: "#008080", value: "Teal"},
+            {key: "#ffffff", value: "White"},
+            {key: "#ffff00", value: "Yellow"},
+        ],
+    )
+    name = dict.get(dict: hexNames, key: hex, default: "No known name")
+
+    return name
+}
+
+hexName(hex: "#000000")
+// Returns "Black"
+
+hexName(hex: "#8b8b8b")
+// Returns "No known name"
+```
diff --git a/content/influxdb/v2.2/query-data/flux/custom-functions/custom-aggregate.md b/content/influxdb/v2.2/query-data/flux/custom-functions/custom-aggregate.md
new file mode 100644
index 000000000..d17f61920
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/flux/custom-functions/custom-aggregate.md
@@ -0,0 +1,245 @@
+---
+title: Create custom aggregate functions
+description: Create your own custom aggregate functions in Flux using the `reduce()` function.
+influxdb/v2.2/tags: [functions, custom, flux, aggregates]
+menu:
+  influxdb_2_2:
+    name: Custom aggregate functions
+    parent: Custom functions
+weight: 301
+aliases:
+  - /influxdb/v2.2/query-data/guides/custom-functions/custom-aggregate/
+related:
+  - /i{{< latest "flux" >}}/stdlib/universe/reduce/
+---
+
+To aggregate your data, use the Flux
+[aggregate functions](/{{< latest "flux" >}}/function-types#aggregates)
+or create custom aggregate functions using the
+[`reduce()`function](/{{< latest "flux" >}}/stdlib/universe/reduce/).
+
+## Aggregate function characteristics
+Aggregate functions all have the same basic characteristics:
+
+- They operate on individual input tables and transform all records into a single record.
+- The output table has the same [group key](/{{< latest "flux" >}}/get-started/data-model/#group-key) as the input table.
+
+## How reduce() works
+The `reduce()` function operates on one row at a time using the function defined in
+the [`fn` parameter](/{{< latest "flux" >}}/stdlib/universe/reduce/#fn).
+The `fn` function maps keys to specific values using two [records](/{{< latest "flux" >}}/data-types/composite/record/)
+specified by the following parameters:
+
+| Parameter     | Description                                                             |
+|:---------:    |:-----------                                                             |
+| `r`           | A record that represents the row or record.                             |
+| `accumulator` | A record that contains values used in each row's aggregate calculation. |
+
+{{% note %}}
+The `reduce()` function's [`identity` parameter](/{{< latest "flux" >}}/stdlib/universe/reduce/#identity)
+defines the initial `accumulator` record.
+{{% /note %}}
+
+### Example reduce() function
+The following example `reduce()` function produces a sum and product of all values
+in an input table.
+
+```js
+|> reduce(
+    fn: (r, accumulator) => ({
+        sum: r._value + accumulator.sum,
+        product: r._value * accumulator.product
+    }),
+    identity: {sum: 0.0, product: 1.0},
+)
+```
+
+To illustrate how this function works, take this simplified table for example:
+
+| _time                | _value |
+|:-----                | ------:|
+| 2019-04-23T16:10:49Z | 1.6    |
+| 2019-04-23T16:10:59Z | 2.3    |
+| 2019-04-23T16:11:09Z | 0.7    |
+| 2019-04-23T16:11:19Z | 1.2    |
+| 2019-04-23T16:11:29Z | 3.8    |
+
+###### Input records
+The `fn` function uses the data in the first row to define the `r` record.
+It defines the `accumulator` record using the `identity` parameter.
+
+```js
+r           = { _time: 2019-04-23T16:10:49.00Z, _value: 1.6 }
+accumulator = { sum  : 0.0, product : 1.0 }
+```
+
+###### Key mappings
+It then uses the `r` and `accumulator` records to populate values in the key mappings:
+```js
+// sum: r._value + accumulator.sum
+sum: 1.6 + 0.0
+
+// product: r._value * accumulator.product
+product: 1.6 * 1.0
+```
+
+###### Output record
+This produces an output record with the following key value pairs:
+
+```js
+{ sum: 1.6, product: 1.6 }
+```
+
+The function then processes the next row using this **output record** as the `accumulator`.
+
+{{% note %}}
+Because `reduce()` uses the output record as the `accumulator` when processing the next row,
+keys mapped in the `fn` function must match keys in the `identity` and `accumulator` records.
+{{% /note %}}
+
+###### Processing the next row
+```js
+// Input records for the second row
+r           = { _time: 2019-04-23T16:10:59.00Z, _value: 2.3 }
+accumulator = { sum  : 1.6, product : 1.6 }
+
+// Key mappings for the second row
+sum: 2.3 + 1.6
+product: 2.3 * 1.6
+
+// Output record of the second row
+{ sum: 3.9, product: 3.68 }
+```
+
+It then uses the new output record as the `accumulator` for the next row.
+This cycle continues until all rows in the table are processed.
+
+##### Final output record and table
+After all records in the table are processed, `reduce()` uses the final output record
+to create a transformed table with one row and columns for each mapped key.
+
+###### Final output record
+```js
+{ sum: 9.6, product: 11.74656 }
+```
+
+###### Output table
+| sum | product  |
+| --- | -------- |
+| 9.6 | 11.74656 |
+
+{{% note %}}
+#### What happened to the \_time column?
+The `reduce()` function only keeps columns that are:
+
+1. Are part of the input table's [group key](/{{< latest "flux" >}}/get-started/data-model/#group-key).
+2. Explicitly mapped in the `fn` function.
+
+It drops all other columns.
+Because `_time` is not part of the group key and is not mapped in the `fn` function,
+it isn't included in the output table.
+{{% /note %}}
+
+## Custom aggregate function examples
+To create custom aggregate functions, use principles outlined in
+[Creating custom functions](/influxdb/v2.2/query-data/flux/custom-functions)
+and the `reduce()` function to aggregate rows in each input table.
+
+### Create a custom average function
+This example illustrates how to create a function that averages values in a table.
+_This is meant for demonstration purposes only.
+The built-in [`mean()` function](/{{< latest "flux" >}}/stdlib/universe/mean/)
+does the same thing and is much more performant._
+
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[Comments](#)
+[No Comments](#)
+{{% /code-tabs %}}
+
+{{% code-tab-content %}}
+
+```js
+average = (tables=<-, outputField="average") => tables
+    |> reduce(
+        // Define the initial accumulator record
+        identity: {count: 0.0, sum: 0.0, avg: 0.0},
+        fn: (r, accumulator) => ({
+            // Increment the counter on each reduce loop
+            count: accumulator.count + 1.0,
+            // Add the _value to the existing sum
+            sum: accumulator.sum + r._value,
+            // Divide the existing sum by the existing count for a new average
+            avg: (accumulator.sum + r._value) / (accumulator.count + 1.0),
+        }),
+    )
+    // Drop the sum and the count columns since they are no longer needed
+    |> drop(columns: ["sum", "count"])
+    // Set the _field column of the output table to to the value
+    // provided in the outputField parameter
+    |> set(key: "_field", value: outputField)
+    // Rename avg column to _value
+    |> rename(columns: {avg: "_value"})
+```
+{{% /code-tab-content %}}
+
+{{% code-tab-content %}}
+```js
+average = (tables=<-, outputField="average") => tables
+    |> reduce(
+        identity: {count: 0.0, sum: 0.0, avg: 0.0},
+        fn: (r, accumulator) => ({
+            count: accumulator.count + 1.0,
+            sum: accumulator.sum + r._value,
+            avg: (accumulator.sum + r._value) / (accumulator.count + 1.0),
+        }),
+    )
+    |> drop(columns: ["sum", "count"])
+    |> set(key: "_field", value: outputField)
+    |> rename(columns: {avg: "_value"})
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+### Aggregate multiple columns
+Built-in aggregate functions only operate on one column.
+Use `reduce()` to create a custom aggregate function that aggregates multiple columns.
+
+The following function expects input tables to have `c1_value` and `c2_value`
+columns and generates an average for each.
+
+```js
+multiAvg = (tables=<-) => tables
+    |> reduce(
+        identity: {
+            count: 1.0,
+            c1_sum: 0.0,
+            c1_avg: 0.0,
+            c2_sum: 0.0,
+            c2_avg: 0.0,
+        },
+        fn: (r, accumulator) => ({
+            count: accumulator.count + 1.0,
+            c1_sum: accumulator.c1_sum + r.c1_value,
+            c1_avg: accumulator.c1_sum / accumulator.count,
+            c2_sum: accumulator.c2_sum + r.c2_value,
+            c2_avg: accumulator.c2_sum / accumulator.count,
+        }),
+    )
+```
+
+### Aggregate gross and net profit
+Use `reduce()` to create a function that aggregates gross and net profit.
+This example expects `profit` and `expenses` columns in the input tables.
+
+```js
+profitSummary = (tables=<-) => tables
+    |> reduce(
+        identity: {gross: 0.0, net: 0.0},
+        fn: (r, accumulator) => ({
+            gross: accumulator.gross + r.profit,
+            net: accumulator.net + r.profit - r.expenses
+            }
+        )
+    )
+```
diff --git a/content/influxdb/v2.2/query-data/flux/exists.md b/content/influxdb/v2.2/query-data/flux/exists.md
new file mode 100644
index 000000000..ec900c312
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/flux/exists.md
@@ -0,0 +1,88 @@
+---
+title: Check if a value exists
+seotitle: Use Flux to check if a value exists
+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.2/tags: [exists]
+menu:
+  influxdb_2_2:
+    name: Exists
+    parent: Query with Flux
+weight: 220
+aliases:
+  - /influxdb/v2.2/query-data/guides/exists/
+related:
+  - /influxdb/v2.2/query-data/flux/query-fields/
+  - /{{< latest "flux" >}}/stdlib/universe/filter/
+list_code_example: |
+  ##### Filter null values
+  ```js
+  data
+    |> filter(fn: (r) => exists r._value)
+  ```
+---
+
+Use the Flux `exists` operator to check if a record contains a key or if that
+key's value is `null`.
+
+```js
+p = {firstName: "John", lastName: "Doe", age: 42}
+
+exists p.firstName
+// Returns true
+
+exists p.height
+// Returns false
+```
+
+If you're just getting started with Flux queries, check out the following:
+
+- [Get started with Flux](/{{< latest "flux" >}}/get-started/) for a conceptual overview of Flux and parts of a Flux query.
+- [Execute queries](/influxdb/v2.2/query-data/execute-queries/) to discover a variety of ways to run your queries.
+
+Use `exists` with row functions (
+[`filter()`](/{{< latest "flux" >}}/stdlib/universe/filter/),
+[`map()`](/{{< latest "flux" >}}/stdlib/universe/map/),
+[`reduce()`](/{{< latest "flux" >}}/stdlib/universe/reduce/))
+to check if a row includes a column or if the value for that column is `null`.
+
+#### Filter null values
+```js
+from(bucket: "example-bucket")
+    |> range(start: -5m)
+    |> filter(fn: (r) => exists r._value)
+```
+
+#### Map values based on existence
+```js
+from(bucket: "default")
+    |> range(start: -30s)
+    |> map(
+        fn: (r) => ({r with
+            human_readable: if exists r._value then
+                "${r._field} is ${string(v: r._value)}."
+            else
+                "${r._field} has no value.",
+        }),
+    )
+```
+
+#### Ignore null values in a custom aggregate function
+```js
+customSumProduct = (tables=<-) => tables
+    |> reduce(
+        identity: {sum: 0.0, product: 1.0},
+        fn: (r, accumulator) => ({r with
+            sum: if exists r._value then
+                r._value + accumulator.sum
+            else
+                accumulator.sum,
+            product: if exists r._value then
+                r.value * accumulator.product
+            else
+                accumulator.product,
+        }),
+    )
+```
diff --git a/content/influxdb/v2.2/query-data/flux/explore-schema.md b/content/influxdb/v2.2/query-data/flux/explore-schema.md
new file mode 100644
index 000000000..19a528966
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/flux/explore-schema.md
@@ -0,0 +1,140 @@
+---
+title: Explore your data schema with Flux
+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.2/tags: [schema]
+menu:
+  influxdb_2_2:
+    name: Explore your schema
+    parent: Query with Flux
+weight: 206
+related:
+  - /{{< latest "flux" >}}/stdlib/universe/buckets/
+  - /{{< latest "flux" >}}/stdlib/schema/measurements
+  - /{{< latest "flux" >}}/stdlib/schema/fieldkeys
+  - /{{< latest "flux" >}}/stdlib/schema/measurementfieldkeys
+  - /{{< latest "flux" >}}/stdlib/schema/tagkeys
+  - /{{< latest "flux" >}}/stdlib/schema/measurementtagkeys
+  - /{{< latest "flux" >}}/stdlib/schema/tagvalues
+  - /{{< latest "flux" >}}/stdlib/schema/measurementtagvalues
+list_code_example: |
+  ```js
+  import "influxdata/influxdb/schema"
+
+  // List buckets
+  buckets()
+
+  // List measurements
+  schema.measurements(bucket: "example-bucket")
+
+  // List field keys
+  schema.fieldKeys(bucket: "example-bucket")
+
+  // List tag keys
+  schema.tagKeys(bucket: "example-bucket")
+
+  // List tag values
+  schema.tagValues(bucket: "example-bucket", tag: "example-tag")
+  ```
+---
+
+Flux provides functions that let you explore the structure and schema of your
+data stored in InfluxDB.
+
+- [List buckets](#list-buckets)
+- [List measurements](#list-measurements)
+- [List field keys](#list-field-keys)
+- [List tag keys](#list-tag-keys)
+- [List tag values](#list-tag-values)
+
+## List buckets
+Use the [`buckets()` function](/{{< latest "flux" >}}/stdlib/universe/buckets/)
+to list **buckets in your organization**.
+
+```js
+buckets()
+```
+
+## List measurements
+Use the [`schema.measurements()` function](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/measurements)
+to list **measurements in a bucket**.
+
+```js
+import "influxdata/influxdb/schema"
+
+schema.measurements(bucket: "example-bucket")
+```
+
+## List field keys
+Use the [`schema.fieldKeys` function](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/fieldkeys)
+to list **field keys in a bucket**.
+
+```js
+import "influxdata/influxdb/schema"
+
+schema.fieldKeys(bucket: "example-bucket")
+```
+
+### List fields in a measurement
+Use the [`schema.measurementFieldKeys` function](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/measurementfieldkeys)
+to list **field keys in a measurement**.
+
+```js
+import "influxdata/influxdb/schema"
+
+schema.measurementFieldKeys(
+    bucket: "example-bucket",
+    measurement: "example-measurement",
+)
+```
+
+## List tag keys
+Use the [`schema.tagKeys()` function](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/tagkeys)
+to list **tag keys in a bucket**.
+
+```js
+import "influxdata/influxdb/schema"
+
+schema.tagKeys(bucket: "example-bucket")
+```
+
+### List tag keys in a measurement
+Use the [`schema.measurementTagKeys` function](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/measurementtagkeys)
+to list **tag keys in a measurement**.
+_This function returns results from the last 30 days._
+
+```js
+import "influxdata/influxdb/schema"
+
+schema.measurementTagKeys(
+    bucket: "example-bucket",
+    measurement: "example-measurement",
+)
+```
+
+## List tag values
+Use the [`schema.tagValues()` function](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/tagvalues)
+to list **tag values for a given tag in a bucket**.
+
+```js
+import "influxdata/influxdb/schema"
+
+schema.tagValues(bucket: "example-bucket", tag: "example-tag")
+```
+
+### List tag values in a measurement
+Use the [`schema.measurementTagValues` function](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/measurementtagvalues)
+to list **tag values for a given tag in a measurement**.
+_This function returns results from the last 30 days._
+
+```js
+import "influxdata/influxdb/schema"
+
+schema.measurementTagValues(
+    bucket: "example-bucket",
+    tag: "example-tag",
+    measurement: "example-measurement",
+)
+```
diff --git a/content/influxdb/v2.2/query-data/flux/fill.md b/content/influxdb/v2.2/query-data/flux/fill.md
new file mode 100644
index 000000000..bdb819c4e
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/flux/fill.md
@@ -0,0 +1,113 @@
+---
+title: Fill null values in data
+seotitle: Fill null values in data
+list_title: Fill
+description: >
+  Use `fill()` function to replace _null_ values.
+weight: 210
+menu:
+  influxdb_2_2:
+    parent: Query with Flux
+    name: Fill
+influxdb/v2.2/tags: [query, fill]
+related:
+  - /{{< latest "flux" >}}/stdlib/universe/fill/
+list_query_example: fill_null
+---
+
+Use [`fill()`](/{{< latest "flux" >}}/stdlib/universe/fill/)
+to replace _null_ values with:
+
+- [the previous non-null value](#fill-with-the-previous-value)
+- [a specified value](#fill-with-a-specified-value)
+
+<!-- -->
+```js
+data
+    |> fill(usePrevious: true)
+
+// OR
+
+data
+    |> fill(value: 0.0)
+```
+
+{{% note %}}
+#### Fill empty windows of time
+The `fill()` function **does not** fill empty windows of time.
+It only replaces _null_ values in existing data.
+Filling empty windows of time requires time interpolation
+_(see [influxdata/flux#2428](https://github.com/influxdata/flux/issues/2428))_.
+{{% /note %}}
+
+## Fill with the previous value
+To fill _null_ values with the previous **non-null** value, set the `usePrevious` parameter to `true`.
+
+{{% note %}}
+Values remain _null_ if there is no previous non-null value in the table.
+{{% /note %}}
+
+```js
+data
+    |> fill(usePrevious: true)
+```
+
+{{< flex >}}
+{{% flex-content %}}
+**Given the following input:**
+
+| _time                | _value |
+|:-----                | ------:|
+| 2020-01-01T00:01:00Z | null   |
+| 2020-01-01T00:02:00Z | 0.8    |
+| 2020-01-01T00:03:00Z | null   |
+| 2020-01-01T00:04:00Z | null   |
+| 2020-01-01T00:05:00Z | 1.4    |
+{{% /flex-content %}}
+{{% flex-content %}}
+**`fill(usePrevious: true)` returns:**
+
+| _time                | _value |
+|:-----                | ------:|
+| 2020-01-01T00:01:00Z | null   |
+| 2020-01-01T00:02:00Z | 0.8    |
+| 2020-01-01T00:03:00Z | 0.8    |
+| 2020-01-01T00:04:00Z | 0.8    |
+| 2020-01-01T00:05:00Z | 1.4    |
+{{% /flex-content %}}
+{{< /flex >}}
+
+## Fill with a specified value
+To fill _null_ values with a specified value, use the `value` parameter to specify the fill value.
+_The fill value must match the [data type](/{{< latest "flux" >}}/spec/types/#basic-types)
+of the [column](/{{< latest "flux" >}}/stdlib/universe/fill/#column)._
+
+```js
+data
+    |> fill(value: 0.0)
+```
+
+{{< flex >}}
+{{% flex-content %}}
+**Given the following input:**
+
+| _time                | _value |
+|:-----                | ------:|
+| 2020-01-01T00:01:00Z | null   |
+| 2020-01-01T00:02:00Z | 0.8    |
+| 2020-01-01T00:03:00Z | null   |
+| 2020-01-01T00:04:00Z | null   |
+| 2020-01-01T00:05:00Z | 1.4    |
+{{% /flex-content %}}
+{{% flex-content %}}
+**`fill(value: 0.0)` returns:**
+
+| _time                | _value |
+|:-----                | ------:|
+| 2020-01-01T00:01:00Z | 0.0    |
+| 2020-01-01T00:02:00Z | 0.8    |
+| 2020-01-01T00:03:00Z | 0.0    |
+| 2020-01-01T00:04:00Z | 0.0    |
+| 2020-01-01T00:05:00Z | 1.4    |
+{{% /flex-content %}}
+{{< /flex >}}
diff --git a/content/influxdb/v2.2/query-data/flux/first-last.md b/content/influxdb/v2.2/query-data/flux/first-last.md
new file mode 100644
index 000000000..aea9685fc
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/flux/first-last.md
@@ -0,0 +1,145 @@
+---
+title: Query first and last values
+seotitle: Query first and last values in Flux
+list_title: First and last
+description: >
+  Use `first()` or `last()` to return the first or last point in an input table.
+weight: 210
+menu:
+  influxdb_2_2:
+    parent: Query with Flux
+    name: First & last
+influxdb/v2.2/tags: [query]
+related:
+  - /{{< latest "flux" >}}/stdlib/universe/first/
+  - /{{< latest "flux" >}}/stdlib/universe/last/
+list_query_example: first_last
+---
+
+Use [`first()`](/{{< latest "flux" >}}/stdlib/universe/first/) or
+[`last()`](/{{< latest "flux" >}}/stdlib/universe/last/) to return the first or
+last record in an input table.
+
+```js
+data
+    |> first()
+
+// OR
+
+data
+    |> last()
+```
+
+{{% note %}}
+By default, InfluxDB returns results sorted by time, however you can use the
+[`sort()` function](/{{< latest "flux" >}}/stdlib/universe/sort/)
+to change how results are sorted.
+`first()` and `last()` respect the sort order of input data and return records
+based on the order they are received in.
+{{% /note %}}
+
+### first
+`first()` returns the first non-null record in an input table.
+
+{{< flex >}}
+{{% flex-content %}}
+**Given the following input:**
+
+| _time                | _value |
+|:-----                | ------:|
+| 2020-01-01T00:01:00Z | 1.0    |
+| 2020-01-01T00:02:00Z | 1.0    |
+| 2020-01-01T00:03:00Z | 2.0    |
+| 2020-01-01T00:04:00Z | 3.0    |
+{{% /flex-content %}}
+{{% flex-content %}}
+**The following function returns:**
+```js
+|> first()
+```
+
+| _time                | _value |
+|:-----                | ------:|
+| 2020-01-01T00:01:00Z | 1.0    |
+{{% /flex-content %}}
+{{< /flex >}}
+
+### last
+`last()` returns the last non-null record in an input table.
+
+{{< flex >}}
+{{% flex-content %}}
+**Given the following input:**
+
+| _time | _value |
+|:-----                | ------:|
+| 2020-01-01T00:01:00Z | 1.0    |
+| 2020-01-01T00:02:00Z | 1.0    |
+| 2020-01-01T00:03:00Z | 2.0    |
+| 2020-01-01T00:04:00Z | 3.0    |
+{{% /flex-content %}}
+{{% flex-content %}}
+**The following function returns:**
+
+```js
+|> last()
+```
+
+| _time                | _value |
+|:-----                | ------:|
+| 2020-01-01T00:04:00Z | 3.0    |
+{{% /flex-content %}}
+{{< /flex >}}
+
+## Use first() or last() with aggregateWindow()
+Use `first()` and `last()` with [`aggregateWindow()`](/{{< latest "flux" >}}/stdlib/universe/aggregatewindow/)
+to select the first or last records in time-based groups.
+`aggregateWindow()` segments data into windows of time, aggregates data in each window into a single
+point using aggregate or selector functions, and then removes the time-based segmentation.
+
+
+{{< flex >}}
+{{% flex-content %}}
+**Given the following input:**
+
+| _time                | _value |
+|:-----                | ------:|
+| 2020-01-01T00:00:00Z | 10     |
+| 2020-01-01T00:00:15Z | 12     |
+| 2020-01-01T00:00:45Z | 9      |
+| 2020-01-01T00:01:05Z | 9      |
+| 2020-01-01T00:01:10Z | 15     |
+| 2020-01-01T00:02:30Z | 11     |
+{{% /flex-content %}}
+
+{{% flex-content %}}
+**The following function returns:**
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[first](#)
+[last](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```js
+|> aggregateWindow(every: 1h, fn: first)
+```
+| _time                | _value |
+|:-----                | ------:|
+| 2020-01-01T00:00:59Z | 10     |
+| 2020-01-01T00:01:59Z | 9      |
+| 2020-01-01T00:02:59Z | 11     |
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```js
+|> aggregateWindow(every: 1h, fn: last)
+```
+
+| _time                | _value |
+|:-----                | ------:|
+| 2020-01-01T00:00:59Z | 9      |
+| 2020-01-01T00:01:59Z | 15     |
+| 2020-01-01T00:02:59Z | 11     |
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+{{%/flex-content %}}
+{{< /flex >}}
diff --git a/content/influxdb/v2.2/query-data/flux/geo/_index.md b/content/influxdb/v2.2/query-data/flux/geo/_index.md
new file mode 100644
index 000000000..876d6d386
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/flux/geo/_index.md
@@ -0,0 +1,69 @@
+---
+title: Work with geo-temporal data
+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_2:
+    name: Geo-temporal data
+    parent: Query with Flux
+weight: 220
+list_code_example: |
+  ```js
+  import "experimental/geo"
+
+  sampleGeoData
+      |> geo.filterRows(region: {lat: 30.04, lon: 31.23, radius: 200.0})
+      |> geo.groupByArea(newColumn: "geoArea", level: 5)
+  ```
+---
+
+Use the [Flux Geo package](/{{< latest "flux" >}}/stdlib/experimental/geo) to
+filter geo-temporal data and group by geographic location or track.
+
+{{% warn %}}
+The Geo package is experimental and subject to change at any time.
+By using it, you agree to the [risks of experimental functions](/{{< latest "flux" >}}/stdlib/experimental/to/#experimental-functions-are-subject-to-change).
+{{% /warn %}}
+
+**To work with geo-temporal data:**
+
+1. Import the `experimental/geo` package.
+
+    ```js
+    import "experimental/geo"
+    ```
+
+2. Load geo-temporal data. _See below for [sample geo-temporal data](#sample-data)._
+3. Do one or more of the following:
+
+    - [Shape data to work with the Geo package](#shape-data-to-work-with-the-geo-package)
+    - [Filter data by region](#filter-geo-temporal-data-by-region) (using strict or non-strict filters)
+    - [Group data by area or by track](#group-geo-temporal-data)
+
+{{< children >}}
+
+---
+
+## Sample data
+Many of the examples in this section use a `sampleGeoData` variable that represents
+a sample set of geo-temporal data.
+The [Bird Migration Sample Data](/influxdb/v2.2/reference/sample-data/#bird-migration-sample-data)
+provides sample geo-temporal data that meets the
+[requirements of the Flux Geo package](/{{< latest "flux" >}}/stdlib/experimental/geo/#geo-schema-requirements).
+
+### Load bird migration sample data
+Use the [`sample.data()` function](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/sample/data/)
+to load the sample bird migration data:
+
+```js
+import "influxdata/influxdb/sample"
+
+sampleGeoData = sample.data(set: "birdMigration")
+```
+
+{{% note %}}
+`sample.data()` downloads sample data each time you execute the query **(~1.3 MB)**.
+If bandwidth is a concern, use the [`to()` function](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/to/)
+to write the data to a bucket, and then query the bucket with [`from()`](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/from/).
+{{% /note %}}
diff --git a/content/influxdb/v2.2/query-data/flux/geo/filter-by-region.md b/content/influxdb/v2.2/query-data/flux/geo/filter-by-region.md
new file mode 100644
index 000000000..7e2368773
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/flux/geo/filter-by-region.md
@@ -0,0 +1,124 @@
+---
+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_2:
+    name: Filter by region
+    parent: Geo-temporal data
+weight: 302
+related:
+  - /{{< latest "flux" >}}/stdlib/experimental/geo/
+  - /{{< latest "flux" >}}/stdlib/experimental/geo/filterrows/
+list_code_example: |
+  ```js
+  import "experimental/geo"
+
+  sampleGeoData
+      |> geo.filterRows(region: {lat: 30.04, lon: 31.23, radius: 200.0}, strict: true)
+  ```
+---
+
+Use the [`geo.filterRows` function](/{{< latest "flux" >}}/stdlib/experimental/geo/filterrows/)
+to filter geo-temporal data by geographic region:
+
+1. [Define a geographic region](#define-a-geographic-region)
+2. [Use strict or non-strict filtering](#strict-and-non-strict-filtering)
+
+The following example uses the [sample bird migration data](/influxdb/v2.2/query-data/flux/geo/#sample-data)
+and queries data points **within 200km of Cairo, Egypt**:
+
+```js
+import "experimental/geo"
+
+sampleGeoData
+    |> geo.filterRows(region: {lat: 30.04, lon: 31.23, radius: 200.0}, strict: true)
+```
+
+## Define a geographic region
+Many functions in the Geo package filter data based on geographic region.
+Define a geographic region using one of the the following shapes:
+
+- [box](#box)
+- [circle](#circle)
+- [polygon](#polygon)
+
+### box
+Define a box-shaped region by specifying a record containing the following properties:
+
+- **minLat:** minimum latitude in decimal degrees (WGS 84) _(Float)_
+- **maxLat:** maximum latitude in decimal degrees (WGS 84) _(Float)_
+- **minLon:** minimum longitude in decimal degrees (WGS 84) _(Float)_
+- **maxLon:** maximum longitude in decimal degrees (WGS 84) _(Float)_
+
+##### Example box-shaped region
+```js
+{
+    minLat: 40.51757813,
+    maxLat: 40.86914063,
+    minLon: -73.65234375,
+    maxLon: -72.94921875,
+}
+```
+
+### circle
+Define a circular region by specifying a record containing the following properties:
+
+- **lat**: latitude of the circle center in decimal degrees (WGS 84) _(Float)_
+- **lon**: longitude of the circle center in decimal degrees (WGS 84) _(Float)_
+- **radius**:  radius of the circle in kilometers (km) _(Float)_
+
+##### Example circular region
+```js
+{
+    lat: 40.69335938,
+    lon: -73.30078125,
+    radius: 20.0,
+}
+```
+
+### polygon
+Define a polygonal region with a record containing the latitude and longitude for
+each point in the polygon:
+
+- **points**: points that define the custom polygon _(Array of records)_
+
+    Define each point with a record containing the following properties:
+
+      - **lat**: latitude in decimal degrees (WGS 84) _(Float)_
+      - **lon**: longitude in decimal degrees (WGS 84) _(Float)_
+
+##### Example polygonal region
+```js
+{
+    points: [
+        {lat: 40.671659, lon: -73.936631},
+        {lat: 40.706543, lon: -73.749177},
+        {lat: 40.791333, lon: -73.880327},
+    ]
+}
+```
+
+## Strict and non-strict filtering
+In most cases, the specified geographic region does not perfectly align with S2 grid cells.
+
+- **Non-strict filtering** returns points that may be outside of the specified region but
+  inside S2 grid cells partially covered by the region.
+- **Strict filtering** returns only points inside the specified region.
+
+_Strict filtering is less performant, but more accurate than non-strict filtering._
+
+<span class="key-geo-cell"></span> S2 grid cell  
+<span class="key-geo-region"></span> Filter region  
+<span class="key-geo-point"></span> Returned point
+
+{{< flex >}}
+{{% flex-content %}}
+**Strict filtering**
+{{< svg "/static/svgs/geo-strict.svg" >}}
+{{% /flex-content %}}
+{{% flex-content %}}
+**Non-strict filtering**
+{{< svg "/static/svgs/geo-non-strict.svg" >}}
+{{% /flex-content %}}
+{{< /flex >}}
diff --git a/content/influxdb/v2.2/query-data/flux/geo/group-geo-data.md b/content/influxdb/v2.2/query-data/flux/geo/group-geo-data.md
new file mode 100644
index 000000000..ec1a9fa91
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/flux/geo/group-geo-data.md
@@ -0,0 +1,73 @@
+---
+title: Group geo-temporal data
+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_2:
+    parent: Geo-temporal data
+weight: 302
+related:
+  - /{{< latest "flux" >}}/stdlib/experimental/geo/
+  - /{{< latest "flux" >}}/stdlib/experimental/geo/groupbyarea/
+  - /{{< latest "flux" >}}/stdlib/experimental/geo/astracks/
+list_code_example: |
+  ```js
+  import "experimental/geo"
+
+  sampleGeoData
+      |> geo.groupByArea(newColumn: "geoArea", level: 5)
+      |> geo.asTracks(groupBy: ["id"],sortBy: ["_time"])
+  ```
+---
+
+Use the `geo.groupByArea()` to group geo-temporal data by area and `geo.asTracks()`
+to group data into tracks or routes.
+
+- [Group data by area](#group-data-by-area)
+- [Group data into tracks or routes](#group-data-by-track-or-route)
+
+{{% note %}}
+For example results, use the [bird migration sample data](/influxdb/v2.2/reference/sample-data/#bird-migration-sample-data)
+to populate the `sampleGeoData` variable in the queries below.
+{{% /note %}}
+
+### Group data by area
+Use the [`geo.groupByArea()` function](/{{< latest "flux" >}}/stdlib/experimental/geo/groupbyarea/)
+to group geo-temporal data points by geographic area.
+Areas are determined by [S2 grid cells](https://s2geometry.io/devguide/s2cell_hierarchy.html#s2cellid-numbering)
+
+- Specify a new column to store the unique area identifier for each point with the `newColumn` parameter.
+- Specify the [S2 cell level](https://s2geometry.io/resources/s2cell_statistics)
+  to use when calculating geographic areas with the `level` parameter.
+
+The following example uses the [sample bird migration data](/influxdb/v2.2/query-data/flux/geo/#sample-data)
+to query data points within 200km of Cairo, Egypt and group them by geographic area:
+
+```js
+import "experimental/geo"
+
+sampleGeoData
+    |> geo.filterRows(region: {lat: 30.04, lon: 31.23, radius: 200.0})
+    |> geo.groupByArea(newColumn: "geoArea", level: 5)
+```
+
+### Group data by track or route
+Use [`geo.asTracks()` function](/{{< latest "flux" >}}/stdlib/experimental/geo/astracks/)
+to group data points into tracks or routes and order them by time or other columns.
+Data must contain a unique identifier for each track. For example: `id` or `tid`.
+
+- Specify columns that uniquely identify each track or route with the `groupBy` parameter.
+- Specify which columns to sort by with the `sortBy` parameter. Default is `["_time"]`.
+
+The following example uses the [sample bird migration data](/influxdb/v2.2/query-data/flux/geo/#sample-data)
+to query data points within 200km of Cairo, Egypt and group them into routes unique
+to each bird:
+
+```js
+import "experimental/geo"
+
+sampleGeoData
+    |> geo.filterRows(region: {lat: 30.04, lon: 31.23, radius: 200.0})
+    |> geo.asTracks(groupBy: ["id"], orderBy: ["_time"])
+```
diff --git a/content/influxdb/v2.2/query-data/flux/geo/shape-geo-data.md b/content/influxdb/v2.2/query-data/flux/geo/shape-geo-data.md
new file mode 100644
index 000000000..2474bb9d2
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/flux/geo/shape-geo-data.md
@@ -0,0 +1,120 @@
+---
+title: Shape data to work with the Geo package
+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_2:
+    name: Shape geo-temporal data
+    parent: Geo-temporal data
+weight: 301
+related:
+  - /{{< latest "flux" >}}/stdlib/experimental/geo/
+  - /{{< latest "flux" >}}/stdlib/experimental/geo/shapedata/
+list_code_example: |
+  ```js
+  import "experimental/geo"
+
+  sampleGeoData
+      |> geo.shapeData(latField: "latitude", lonField: "longitude", level: 10)
+  ```
+---
+
+Functions in the Geo package require the following data schema:
+
+- an **s2_cell_id** tag containing the [S2 Cell ID](https://s2geometry.io/devguide/s2cell_hierarchy.html#s2cellid-numbering)
+  **as a token**
+- a **`lat` field** field containing the **latitude in decimal degrees** (WGS 84)
+- a **`lon` field** field containing the **longitude in decimal degrees** (WGS 84)
+
+## Shape geo-temporal data
+If your data already contains latitude and longitude fields, use the
+[`geo.shapeData()`function](/{{< latest "flux" >}}/stdlib/experimental/geo/shapedata/)
+to rename the fields to match the requirements of the Geo package, pivot the data
+into row-wise sets, and generate S2 cell ID tokens for each point.
+
+```js
+import "experimental/geo"
+
+from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> geo.shapeData(latField: "latitude", lonField: "longitude", level: 10)
+```
+
+## Generate S2 cell ID tokens
+The Geo package uses the [S2 Geometry Library](https://s2geometry.io/) to represent
+geographic coordinates on a three-dimensional sphere.
+The sphere is divided into [cells](https://s2geometry.io/devguide/s2cell_hierarchy),
+each with a unique 64-bit identifier (S2 cell ID).
+Grid and S2 cell ID accuracy are defined by a [level](https://s2geometry.io/resources/s2cell_statistics).
+
+{{% note %}}
+To filter more quickly, use higher S2 Cell ID levels,
+but know that that higher levels increase [series cardinality](/influxdb/v2.2/reference/glossary/#series-cardinality).
+{{% /note %}}
+
+The Geo package requires S2 cell IDs as tokens.
+To generate add S2 cell IDs tokens to your data, use one of the following options:
+
+- [Generate S2 cell ID tokens with Telegraf](#generate-s2-cell-id-tokens-with-telegraf)
+- [Generate S2 cell ID tokens language-specific libraries](#generate-s2-cell-id-tokens-language-specific-libraries)
+- [Generate S2 cell ID tokens with Flux](#generate-s2-cell-id-tokens-with-flux)
+
+### Generate S2 cell ID tokens with Telegraf
+Enable the [Telegraf S2 Geo (`s2geo`) processor](https://github.com/influxdata/telegraf/tree/master/plugins/processors/s2geo)
+to generate S2 cell ID tokens at a specified `cell_level` using `lat` and `lon` field values.
+
+Add the `processors.s2geo` configuration to your Telegraf configuration file (`telegraf.conf`):
+
+```toml
+[[processors.s2geo]]
+  ## The name of the lat and lon fields containing WGS-84 latitude and
+  ## longitude in decimal degrees.
+  lat_field = "lat"
+  lon_field = "lon"
+
+  ## New tag to create
+  tag_key = "s2_cell_id"
+
+  ## Cell level (see https://s2geometry.io/resources/s2cell_statistics.html)
+  cell_level = 9
+```
+
+Telegraf stores the S2 cell ID token in the `s2_cell_id` tag.
+
+### Generate S2 cell ID tokens language-specific libraries
+Many programming languages offer S2 Libraries with methods for generating S2 cell ID tokens.
+Use latitude and longitude with the `s2.CellID.ToToken` endpoint of the S2 Geometry
+Library to generate `s2_cell_id` tags. For example:
+
+- **Go:** [s2.CellID.ToToken()](https://godoc.org/github.com/golang/geo/s2#CellID.ToToken)
+- **Python:** [s2sphere.CellId.to_token()](https://s2sphere.readthedocs.io/en/latest/api.html#s2sphere.CellId)
+- **Crystal:** [cell.to_token(level)](https://github.com/spider-gazelle/s2_cells#usage)
+- **JavaScript:** [s2.cellid.toToken()](https://github.com/mapbox/node-s2/blob/master/API.md#cellidtotoken---string)
+
+### Generate S2 cell ID tokens with Flux
+Use the [`geo.s2CellIDToken()` function](/{{< latest "flux" >}}/stdlib/experimental/geo/s2cellidtoken/)
+with existing longitude (`lon`) and latitude (`lat`) field values to generate and add the S2 cell ID token.
+First, use the [`geo.toRows()` function](/{{< latest "flux" >}}/stdlib/experimental/geo/torows/)
+to pivot **lat** and **lon** fields into row-wise sets:
+
+```js
+import "experimental/geo"
+
+from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> geo.toRows()
+    |> map(
+        fn: (r) => ({
+            r with
+            s2_cell_id: geo.s2CellIDToken(point: {lon: r.lon, lat: r.lat}, level: 10)
+        })
+    )
+```
+
+{{% note %}}
+The [`geo.shapeData()`function](/{{< latest "flux" >}}/stdlib/experimental/geo/shapedata/)
+generates S2 cell ID tokens as well.
+{{% /note %}}
diff --git a/content/influxdb/v2.2/query-data/flux/group-data.md b/content/influxdb/v2.2/query-data/flux/group-data.md
new file mode 100644
index 000000000..a5697012b
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/flux/group-data.md
@@ -0,0 +1,676 @@
+---
+title: Group data in InfluxDB with Flux
+list_title: Group
+description: >
+  Use `group()` to group data with common values in specific columns.
+influxdb/v2.2/tags: [group]
+menu:
+  influxdb_2_2:
+    name: Group
+    parent: Query with Flux
+weight: 202
+aliases:
+  - /influxdb/v2.2/query-data/guides/group-data/
+  - /influxdb/v2.2/query-data/flux/grouping-data/
+related:
+  - /{{< latest "flux" >}}/stdlib/universe/group
+  - /{{< latest "flux" >}}/stdlib/experimental/group
+list_query_example: group
+---
+
+With Flux, you can group data by any column in your queried data set.
+"Grouping" partitions data into tables in which each row shares a common value for specified columns.
+This guide walks through grouping data in Flux and provides examples of how data is shaped in the process.
+
+If you're just getting started with Flux queries, check out the following:
+
+- [Get started with Flux](/{{< latest "flux" >}}/get-started/) for a conceptual overview of Flux and parts of a Flux query.
+- [Execute queries](/influxdb/v2.2/query-data/execute-queries/) to discover a variety of ways to run your queries.
+
+## Group keys
+Every table has a **group key** – a list of columns for which every row in the table has the same value.
+
+###### Example group key
+```js
+[_start, _stop, _field, _measurement, host]
+```
+
+Grouping data in Flux is essentially defining the group key of output tables.
+Understanding how modifying group keys shapes output data is key to successfully
+grouping and transforming data into your desired output.
+
+## group() Function
+Flux's [`group()` function](/{{< latest "flux" >}}/stdlib/universe/group) defines the
+group key for output tables, i.e. grouping records based on values for specific columns.
+
+###### group() example
+```js
+dataStream
+    |> group(columns: ["cpu", "host"])
+```
+
+###### Resulting group key
+```js
+[cpu, host]
+```
+
+The `group()` function has the following parameters:
+
+### columns
+The list of columns to include or exclude (depending on the [mode](#mode)) in the grouping operation.
+
+### mode
+The method used to define the group and resulting group key.
+Possible values include `by` and `except`.
+
+
+## Example grouping operations
+To illustrate how grouping works, define a `dataSet` variable that queries System
+CPU usage from the `example-bucket` bucket.
+Filter the `cpu` tag so it only returns results for each numbered CPU core.
+
+### Data set
+CPU used by system operations for all numbered CPU cores.
+It uses a regular expression to filter only numbered cores.
+
+```js
+dataSet = from(bucket: "example-bucket")
+    |> range(start: -2m)
+    |> filter(fn: (r) => r._field == "usage_system" and r.cpu =~ /cpu[0-9*]/)
+    |> drop(columns: ["host"])
+```
+
+{{% note %}}
+This example drops the `host` column from the returned data since the CPU data
+is only tracked for a single host and it simplifies the output tables.
+Don't drop the `host` column if monitoring multiple hosts.
+{{% /note %}}
+
+{{% truncate %}}
+```
+Table: keys: [_start, _stop, _field, _measurement, cpu]
+                   _start:time                      _stop:time           _field:string     _measurement:string              cpu:string                      _time:time                  _value:float
+------------------------------  ------------------------------  ----------------------  ----------------------  ----------------------  ------------------------------  ----------------------------
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu0  2018-11-05T21:34:00.000000000Z             7.892107892107892
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu0  2018-11-05T21:34:10.000000000Z                           7.2
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu0  2018-11-05T21:34:20.000000000Z                           7.4
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu0  2018-11-05T21:34:30.000000000Z                           5.5
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu0  2018-11-05T21:34:40.000000000Z                           7.4
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu0  2018-11-05T21:34:50.000000000Z                           7.5
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu0  2018-11-05T21:35:00.000000000Z                          10.3
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu0  2018-11-05T21:35:10.000000000Z                           9.2
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu0  2018-11-05T21:35:20.000000000Z                           8.4
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu0  2018-11-05T21:35:30.000000000Z                           8.5
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu0  2018-11-05T21:35:40.000000000Z                           8.6
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu0  2018-11-05T21:35:50.000000000Z                          10.2
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu0  2018-11-05T21:36:00.000000000Z                          10.6
+
+Table: keys: [_start, _stop, _field, _measurement, cpu]
+                   _start:time                      _stop:time           _field:string     _measurement:string              cpu:string                      _time:time                  _value:float
+------------------------------  ------------------------------  ----------------------  ----------------------  ----------------------  ------------------------------  ----------------------------
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu1  2018-11-05T21:34:00.000000000Z            0.7992007992007992
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu1  2018-11-05T21:34:10.000000000Z                           0.7
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu1  2018-11-05T21:34:20.000000000Z                           0.7
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu1  2018-11-05T21:34:30.000000000Z                           0.4
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu1  2018-11-05T21:34:40.000000000Z                           0.7
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu1  2018-11-05T21:34:50.000000000Z                           0.7
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu1  2018-11-05T21:35:00.000000000Z                           1.4
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu1  2018-11-05T21:35:10.000000000Z                           1.2
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu1  2018-11-05T21:35:20.000000000Z                           0.8
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu1  2018-11-05T21:35:30.000000000Z            0.8991008991008991
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu1  2018-11-05T21:35:40.000000000Z            0.8008008008008008
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu1  2018-11-05T21:35:50.000000000Z             0.999000999000999
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu1  2018-11-05T21:36:00.000000000Z            1.1022044088176353
+
+Table: keys: [_start, _stop, _field, _measurement, cpu]
+                   _start:time                      _stop:time           _field:string     _measurement:string              cpu:string                      _time:time                  _value:float
+------------------------------  ------------------------------  ----------------------  ----------------------  ----------------------  ------------------------------  ----------------------------
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu2  2018-11-05T21:34:00.000000000Z                           4.1
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu2  2018-11-05T21:34:10.000000000Z                           3.6
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu2  2018-11-05T21:34:20.000000000Z                           3.5
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu2  2018-11-05T21:34:30.000000000Z                           2.6
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu2  2018-11-05T21:34:40.000000000Z                           4.5
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu2  2018-11-05T21:34:50.000000000Z             4.895104895104895
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu2  2018-11-05T21:35:00.000000000Z             6.906906906906907
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu2  2018-11-05T21:35:10.000000000Z                           5.7
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu2  2018-11-05T21:35:20.000000000Z                           5.1
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu2  2018-11-05T21:35:30.000000000Z                           4.7
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu2  2018-11-05T21:35:40.000000000Z                           5.1
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu2  2018-11-05T21:35:50.000000000Z                           5.9
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu2  2018-11-05T21:36:00.000000000Z            6.4935064935064934
+
+Table: keys: [_start, _stop, _field, _measurement, cpu]
+                   _start:time                      _stop:time           _field:string     _measurement:string              cpu:string                      _time:time                  _value:float
+------------------------------  ------------------------------  ----------------------  ----------------------  ----------------------  ------------------------------  ----------------------------
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu3  2018-11-05T21:34:00.000000000Z            0.5005005005005005
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu3  2018-11-05T21:34:10.000000000Z                           0.5
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu3  2018-11-05T21:34:20.000000000Z                           0.5
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu3  2018-11-05T21:34:30.000000000Z                           0.3
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu3  2018-11-05T21:34:40.000000000Z                           0.6
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu3  2018-11-05T21:34:50.000000000Z                           0.6
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu3  2018-11-05T21:35:00.000000000Z            1.3986013986013985
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu3  2018-11-05T21:35:10.000000000Z                           0.9
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu3  2018-11-05T21:35:20.000000000Z            0.5005005005005005
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu3  2018-11-05T21:35:30.000000000Z                           0.7
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu3  2018-11-05T21:35:40.000000000Z                           0.6
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu3  2018-11-05T21:35:50.000000000Z                           0.8
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            usage_system                     cpu                    cpu3  2018-11-05T21:36:00.000000000Z                           0.9
+```
+{{% /truncate %}}
+
+**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 by CPU
+Group the `dataSet` stream by the `cpu` column.
+
+```js
+dataSet
+    |> group(columns: ["cpu"])
+```
+
+This won't actually change the structure of the data since it already has `cpu`
+in the group key and is therefore grouped by `cpu`.
+However, notice that it does change the group key:
+
+{{% truncate %}}
+###### Group by CPU output tables
+```
+Table: keys: [cpu]
+            cpu:string                      _stop:time                      _time:time                  _value:float           _field:string     _measurement:string                     _start:time
+----------------------  ------------------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+                  cpu0  2018-11-05T21:36:00.000000000Z  2018-11-05T21:34:00.000000000Z             7.892107892107892            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu0  2018-11-05T21:36:00.000000000Z  2018-11-05T21:34:10.000000000Z                           7.2            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu0  2018-11-05T21:36:00.000000000Z  2018-11-05T21:34:20.000000000Z                           7.4            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu0  2018-11-05T21:36:00.000000000Z  2018-11-05T21:34:30.000000000Z                           5.5            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu0  2018-11-05T21:36:00.000000000Z  2018-11-05T21:34:40.000000000Z                           7.4            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu0  2018-11-05T21:36:00.000000000Z  2018-11-05T21:34:50.000000000Z                           7.5            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu0  2018-11-05T21:36:00.000000000Z  2018-11-05T21:35:00.000000000Z                          10.3            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu0  2018-11-05T21:36:00.000000000Z  2018-11-05T21:35:10.000000000Z                           9.2            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu0  2018-11-05T21:36:00.000000000Z  2018-11-05T21:35:20.000000000Z                           8.4            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu0  2018-11-05T21:36:00.000000000Z  2018-11-05T21:35:30.000000000Z                           8.5            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu0  2018-11-05T21:36:00.000000000Z  2018-11-05T21:35:40.000000000Z                           8.6            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu0  2018-11-05T21:36:00.000000000Z  2018-11-05T21:35:50.000000000Z                          10.2            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu0  2018-11-05T21:36:00.000000000Z  2018-11-05T21:36:00.000000000Z                          10.6            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [cpu]
+            cpu:string                      _stop:time                      _time:time                  _value:float           _field:string     _measurement:string                     _start:time
+----------------------  ------------------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+                  cpu1  2018-11-05T21:36:00.000000000Z  2018-11-05T21:34:00.000000000Z            0.7992007992007992            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu1  2018-11-05T21:36:00.000000000Z  2018-11-05T21:34:10.000000000Z                           0.7            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu1  2018-11-05T21:36:00.000000000Z  2018-11-05T21:34:20.000000000Z                           0.7            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu1  2018-11-05T21:36:00.000000000Z  2018-11-05T21:34:30.000000000Z                           0.4            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu1  2018-11-05T21:36:00.000000000Z  2018-11-05T21:34:40.000000000Z                           0.7            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu1  2018-11-05T21:36:00.000000000Z  2018-11-05T21:34:50.000000000Z                           0.7            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu1  2018-11-05T21:36:00.000000000Z  2018-11-05T21:35:00.000000000Z                           1.4            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu1  2018-11-05T21:36:00.000000000Z  2018-11-05T21:35:10.000000000Z                           1.2            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu1  2018-11-05T21:36:00.000000000Z  2018-11-05T21:35:20.000000000Z                           0.8            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu1  2018-11-05T21:36:00.000000000Z  2018-11-05T21:35:30.000000000Z            0.8991008991008991            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu1  2018-11-05T21:36:00.000000000Z  2018-11-05T21:35:40.000000000Z            0.8008008008008008            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu1  2018-11-05T21:36:00.000000000Z  2018-11-05T21:35:50.000000000Z             0.999000999000999            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu1  2018-11-05T21:36:00.000000000Z  2018-11-05T21:36:00.000000000Z            1.1022044088176353            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [cpu]
+            cpu:string                      _stop:time                      _time:time                  _value:float           _field:string     _measurement:string                     _start:time
+----------------------  ------------------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+                  cpu2  2018-11-05T21:36:00.000000000Z  2018-11-05T21:34:00.000000000Z                           4.1            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu2  2018-11-05T21:36:00.000000000Z  2018-11-05T21:34:10.000000000Z                           3.6            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu2  2018-11-05T21:36:00.000000000Z  2018-11-05T21:34:20.000000000Z                           3.5            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu2  2018-11-05T21:36:00.000000000Z  2018-11-05T21:34:30.000000000Z                           2.6            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu2  2018-11-05T21:36:00.000000000Z  2018-11-05T21:34:40.000000000Z                           4.5            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu2  2018-11-05T21:36:00.000000000Z  2018-11-05T21:34:50.000000000Z             4.895104895104895            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu2  2018-11-05T21:36:00.000000000Z  2018-11-05T21:35:00.000000000Z             6.906906906906907            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu2  2018-11-05T21:36:00.000000000Z  2018-11-05T21:35:10.000000000Z                           5.7            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu2  2018-11-05T21:36:00.000000000Z  2018-11-05T21:35:20.000000000Z                           5.1            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu2  2018-11-05T21:36:00.000000000Z  2018-11-05T21:35:30.000000000Z                           4.7            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu2  2018-11-05T21:36:00.000000000Z  2018-11-05T21:35:40.000000000Z                           5.1            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu2  2018-11-05T21:36:00.000000000Z  2018-11-05T21:35:50.000000000Z                           5.9            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu2  2018-11-05T21:36:00.000000000Z  2018-11-05T21:36:00.000000000Z            6.4935064935064934            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [cpu]
+            cpu:string                      _stop:time                      _time:time                  _value:float           _field:string     _measurement:string                     _start:time
+----------------------  ------------------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+                  cpu3  2018-11-05T21:36:00.000000000Z  2018-11-05T21:34:00.000000000Z            0.5005005005005005            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu3  2018-11-05T21:36:00.000000000Z  2018-11-05T21:34:10.000000000Z                           0.5            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu3  2018-11-05T21:36:00.000000000Z  2018-11-05T21:34:20.000000000Z                           0.5            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu3  2018-11-05T21:36:00.000000000Z  2018-11-05T21:34:30.000000000Z                           0.3            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu3  2018-11-05T21:36:00.000000000Z  2018-11-05T21:34:40.000000000Z                           0.6            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu3  2018-11-05T21:36:00.000000000Z  2018-11-05T21:34:50.000000000Z                           0.6            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu3  2018-11-05T21:36:00.000000000Z  2018-11-05T21:35:00.000000000Z            1.3986013986013985            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu3  2018-11-05T21:36:00.000000000Z  2018-11-05T21:35:10.000000000Z                           0.9            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu3  2018-11-05T21:36:00.000000000Z  2018-11-05T21:35:20.000000000Z            0.5005005005005005            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu3  2018-11-05T21:36:00.000000000Z  2018-11-05T21:35:30.000000000Z                           0.7            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu3  2018-11-05T21:36:00.000000000Z  2018-11-05T21:35:40.000000000Z                           0.6            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu3  2018-11-05T21:36:00.000000000Z  2018-11-05T21:35:50.000000000Z                           0.8            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+                  cpu3  2018-11-05T21:36:00.000000000Z  2018-11-05T21:36:00.000000000Z                           0.9            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+```
+{{% /truncate %}}
+
+The visualization remains the same.
+
+![Group by CPU](/img/flux/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.
+
+```js
+dataSet
+    |> group(columns: ["_time"])
+```
+
+When grouping by `_time`, all records that share a common `_time` value are grouped into individual tables.
+So each output table represents a single point in time.
+
+{{% truncate %}}
+###### Group by time output tables
+```
+Table: keys: [_time]
+                    _time:time                     _start:time                      _stop:time                  _value:float           _field:string     _measurement:string              cpu:string
+------------------------------  ------------------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ----------------------
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z             7.892107892107892            usage_system                     cpu                    cpu0
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            0.7992007992007992            usage_system                     cpu                    cpu1
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           4.1            usage_system                     cpu                    cpu2
+2018-11-05T21:34:00.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            0.5005005005005005            usage_system                     cpu                    cpu3
+
+Table: keys: [_time]
+                    _time:time                     _start:time                      _stop:time                  _value:float           _field:string     _measurement:string              cpu:string
+------------------------------  ------------------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ----------------------
+2018-11-05T21:34:10.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           7.2            usage_system                     cpu                    cpu0
+2018-11-05T21:34:10.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           0.7            usage_system                     cpu                    cpu1
+2018-11-05T21:34:10.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           3.6            usage_system                     cpu                    cpu2
+2018-11-05T21:34:10.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           0.5            usage_system                     cpu                    cpu3
+
+Table: keys: [_time]
+                    _time:time                     _start:time                      _stop:time                  _value:float           _field:string     _measurement:string              cpu:string
+------------------------------  ------------------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ----------------------
+2018-11-05T21:34:20.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           7.4            usage_system                     cpu                    cpu0
+2018-11-05T21:34:20.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           0.7            usage_system                     cpu                    cpu1
+2018-11-05T21:34:20.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           3.5            usage_system                     cpu                    cpu2
+2018-11-05T21:34:20.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           0.5            usage_system                     cpu                    cpu3
+
+Table: keys: [_time]
+                    _time:time                     _start:time                      _stop:time                  _value:float           _field:string     _measurement:string              cpu:string
+------------------------------  ------------------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ----------------------
+2018-11-05T21:34:30.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           5.5            usage_system                     cpu                    cpu0
+2018-11-05T21:34:30.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           0.4            usage_system                     cpu                    cpu1
+2018-11-05T21:34:30.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           2.6            usage_system                     cpu                    cpu2
+2018-11-05T21:34:30.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           0.3            usage_system                     cpu                    cpu3
+
+Table: keys: [_time]
+                    _time:time                     _start:time                      _stop:time                  _value:float           _field:string     _measurement:string              cpu:string
+------------------------------  ------------------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ----------------------
+2018-11-05T21:34:40.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           7.4            usage_system                     cpu                    cpu0
+2018-11-05T21:34:40.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           0.7            usage_system                     cpu                    cpu1
+2018-11-05T21:34:40.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           4.5            usage_system                     cpu                    cpu2
+2018-11-05T21:34:40.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           0.6            usage_system                     cpu                    cpu3
+
+Table: keys: [_time]
+                    _time:time                     _start:time                      _stop:time                  _value:float           _field:string     _measurement:string              cpu:string
+------------------------------  ------------------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ----------------------
+2018-11-05T21:34:50.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           7.5            usage_system                     cpu                    cpu0
+2018-11-05T21:34:50.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           0.7            usage_system                     cpu                    cpu1
+2018-11-05T21:34:50.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z             4.895104895104895            usage_system                     cpu                    cpu2
+2018-11-05T21:34:50.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           0.6            usage_system                     cpu                    cpu3
+
+Table: keys: [_time]
+                    _time:time                     _start:time                      _stop:time                  _value:float           _field:string     _measurement:string              cpu:string
+------------------------------  ------------------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ----------------------
+2018-11-05T21:35:00.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                          10.3            usage_system                     cpu                    cpu0
+2018-11-05T21:35:00.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           1.4            usage_system                     cpu                    cpu1
+2018-11-05T21:35:00.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z             6.906906906906907            usage_system                     cpu                    cpu2
+2018-11-05T21:35:00.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            1.3986013986013985            usage_system                     cpu                    cpu3
+
+Table: keys: [_time]
+                    _time:time                     _start:time                      _stop:time                  _value:float           _field:string     _measurement:string              cpu:string
+------------------------------  ------------------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ----------------------
+2018-11-05T21:35:10.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           9.2            usage_system                     cpu                    cpu0
+2018-11-05T21:35:10.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           1.2            usage_system                     cpu                    cpu1
+2018-11-05T21:35:10.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           5.7            usage_system                     cpu                    cpu2
+2018-11-05T21:35:10.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           0.9            usage_system                     cpu                    cpu3
+
+Table: keys: [_time]
+                    _time:time                     _start:time                      _stop:time                  _value:float           _field:string     _measurement:string              cpu:string
+------------------------------  ------------------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ----------------------
+2018-11-05T21:35:20.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           8.4            usage_system                     cpu                    cpu0
+2018-11-05T21:35:20.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           0.8            usage_system                     cpu                    cpu1
+2018-11-05T21:35:20.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           5.1            usage_system                     cpu                    cpu2
+2018-11-05T21:35:20.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            0.5005005005005005            usage_system                     cpu                    cpu3
+
+Table: keys: [_time]
+                    _time:time                     _start:time                      _stop:time                  _value:float           _field:string     _measurement:string              cpu:string
+------------------------------  ------------------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ----------------------
+2018-11-05T21:35:30.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           8.5            usage_system                     cpu                    cpu0
+2018-11-05T21:35:30.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            0.8991008991008991            usage_system                     cpu                    cpu1
+2018-11-05T21:35:30.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           4.7            usage_system                     cpu                    cpu2
+2018-11-05T21:35:30.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           0.7            usage_system                     cpu                    cpu3
+
+Table: keys: [_time]
+                    _time:time                     _start:time                      _stop:time                  _value:float           _field:string     _measurement:string              cpu:string
+------------------------------  ------------------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ----------------------
+2018-11-05T21:35:40.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           8.6            usage_system                     cpu                    cpu0
+2018-11-05T21:35:40.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            0.8008008008008008            usage_system                     cpu                    cpu1
+2018-11-05T21:35:40.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           5.1            usage_system                     cpu                    cpu2
+2018-11-05T21:35:40.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           0.6            usage_system                     cpu                    cpu3
+
+Table: keys: [_time]
+                    _time:time                     _start:time                      _stop:time                  _value:float           _field:string     _measurement:string              cpu:string
+------------------------------  ------------------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ----------------------
+2018-11-05T21:35:50.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                          10.2            usage_system                     cpu                    cpu0
+2018-11-05T21:35:50.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z             0.999000999000999            usage_system                     cpu                    cpu1
+2018-11-05T21:35:50.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           5.9            usage_system                     cpu                    cpu2
+2018-11-05T21:35:50.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           0.8            usage_system                     cpu                    cpu3
+
+Table: keys: [_time]
+                    _time:time                     _start:time                      _stop:time                  _value:float           _field:string     _measurement:string              cpu:string
+------------------------------  ------------------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ----------------------
+2018-11-05T21:36:00.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                          10.6            usage_system                     cpu                    cpu0
+2018-11-05T21:36:00.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            1.1022044088176353            usage_system                     cpu                    cpu1
+2018-11-05T21:36:00.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z            6.4935064935064934            usage_system                     cpu                    cpu2
+2018-11-05T21:36:00.000000000Z  2018-11-05T21:34:00.000000000Z  2018-11-05T21:36:00.000000000Z                           0.9            usage_system                     cpu                    cpu3
+```
+{{% /truncate %}}
+
+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)
+
+{{% note %}}
+With some further processing, you could calculate the average CPU usage across all CPUs per point
+of time and group them into a single table, but we won't cover that in this example.
+If you're interested in running and visualizing this yourself, here's what the query would look like:
+
+```js
+dataSet
+    |> group(columns: ["_time"])
+    |> mean()
+    |> group(columns: ["_value", "_time"], mode: "except")
+```
+{{% /note %}}
+
+## Group by CPU and time
+Group by the `cpu` and `_time` columns.
+
+```js
+dataSet
+    |> group(columns: ["cpu", "_time"])
+```
+
+This outputs a table for every unique `cpu` and `_time` combination:
+
+{{% truncate %}}
+###### Group by CPU and time output tables
+```
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:34:00.000000000Z                    cpu0  2018-11-05T21:36:00.000000000Z             7.892107892107892            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:34:00.000000000Z                    cpu1  2018-11-05T21:36:00.000000000Z            0.7992007992007992            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:34:00.000000000Z                    cpu2  2018-11-05T21:36:00.000000000Z                           4.1            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:34:00.000000000Z                    cpu3  2018-11-05T21:36:00.000000000Z            0.5005005005005005            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:34:10.000000000Z                    cpu0  2018-11-05T21:36:00.000000000Z                           7.2            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:34:10.000000000Z                    cpu1  2018-11-05T21:36:00.000000000Z                           0.7            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:34:10.000000000Z                    cpu2  2018-11-05T21:36:00.000000000Z                           3.6            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:34:10.000000000Z                    cpu3  2018-11-05T21:36:00.000000000Z                           0.5            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:34:20.000000000Z                    cpu0  2018-11-05T21:36:00.000000000Z                           7.4            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:34:20.000000000Z                    cpu1  2018-11-05T21:36:00.000000000Z                           0.7            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:34:20.000000000Z                    cpu2  2018-11-05T21:36:00.000000000Z                           3.5            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:34:20.000000000Z                    cpu3  2018-11-05T21:36:00.000000000Z                           0.5            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:34:30.000000000Z                    cpu0  2018-11-05T21:36:00.000000000Z                           5.5            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:34:30.000000000Z                    cpu1  2018-11-05T21:36:00.000000000Z                           0.4            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:34:30.000000000Z                    cpu2  2018-11-05T21:36:00.000000000Z                           2.6            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:34:30.000000000Z                    cpu3  2018-11-05T21:36:00.000000000Z                           0.3            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:34:40.000000000Z                    cpu0  2018-11-05T21:36:00.000000000Z                           7.4            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:34:40.000000000Z                    cpu1  2018-11-05T21:36:00.000000000Z                           0.7            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:34:40.000000000Z                    cpu2  2018-11-05T21:36:00.000000000Z                           4.5            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:34:40.000000000Z                    cpu3  2018-11-05T21:36:00.000000000Z                           0.6            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:34:50.000000000Z                    cpu0  2018-11-05T21:36:00.000000000Z                           7.5            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:34:50.000000000Z                    cpu1  2018-11-05T21:36:00.000000000Z                           0.7            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:34:50.000000000Z                    cpu2  2018-11-05T21:36:00.000000000Z             4.895104895104895            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:34:50.000000000Z                    cpu3  2018-11-05T21:36:00.000000000Z                           0.6            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:35:00.000000000Z                    cpu0  2018-11-05T21:36:00.000000000Z                          10.3            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:35:00.000000000Z                    cpu1  2018-11-05T21:36:00.000000000Z                           1.4            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:35:00.000000000Z                    cpu2  2018-11-05T21:36:00.000000000Z             6.906906906906907            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:35:00.000000000Z                    cpu3  2018-11-05T21:36:00.000000000Z            1.3986013986013985            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:35:10.000000000Z                    cpu0  2018-11-05T21:36:00.000000000Z                           9.2            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:35:10.000000000Z                    cpu1  2018-11-05T21:36:00.000000000Z                           1.2            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:35:10.000000000Z                    cpu2  2018-11-05T21:36:00.000000000Z                           5.7            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:35:10.000000000Z                    cpu3  2018-11-05T21:36:00.000000000Z                           0.9            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:35:20.000000000Z                    cpu0  2018-11-05T21:36:00.000000000Z                           8.4            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:35:20.000000000Z                    cpu1  2018-11-05T21:36:00.000000000Z                           0.8            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:35:20.000000000Z                    cpu2  2018-11-05T21:36:00.000000000Z                           5.1            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:35:20.000000000Z                    cpu3  2018-11-05T21:36:00.000000000Z            0.5005005005005005            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:35:30.000000000Z                    cpu0  2018-11-05T21:36:00.000000000Z                           8.5            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:35:30.000000000Z                    cpu1  2018-11-05T21:36:00.000000000Z            0.8991008991008991            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:35:30.000000000Z                    cpu2  2018-11-05T21:36:00.000000000Z                           4.7            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:35:30.000000000Z                    cpu3  2018-11-05T21:36:00.000000000Z                           0.7            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:35:40.000000000Z                    cpu0  2018-11-05T21:36:00.000000000Z                           8.6            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:35:40.000000000Z                    cpu1  2018-11-05T21:36:00.000000000Z            0.8008008008008008            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:35:40.000000000Z                    cpu2  2018-11-05T21:36:00.000000000Z                           5.1            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:35:40.000000000Z                    cpu3  2018-11-05T21:36:00.000000000Z                           0.6            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:35:50.000000000Z                    cpu0  2018-11-05T21:36:00.000000000Z                          10.2            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:35:50.000000000Z                    cpu1  2018-11-05T21:36:00.000000000Z             0.999000999000999            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:35:50.000000000Z                    cpu2  2018-11-05T21:36:00.000000000Z                           5.9            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:35:50.000000000Z                    cpu3  2018-11-05T21:36:00.000000000Z                           0.8            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:36:00.000000000Z                    cpu0  2018-11-05T21:36:00.000000000Z                          10.6            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:36:00.000000000Z                    cpu1  2018-11-05T21:36:00.000000000Z            1.1022044088176353            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:36:00.000000000Z                    cpu2  2018-11-05T21:36:00.000000000Z            6.4935064935064934            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+
+Table: keys: [_time, cpu]
+                    _time:time              cpu:string                      _stop:time                  _value:float           _field:string     _measurement:string                     _start:time
+------------------------------  ----------------------  ------------------------------  ----------------------------  ----------------------  ----------------------  ------------------------------
+2018-11-05T21:36:00.000000000Z                    cpu3  2018-11-05T21:36:00.000000000Z                           0.9            usage_system                     cpu  2018-11-05T21:34:00.000000000Z
+```
+{{% /truncate %}}
+
+When visualized, tables appear as individual, unconnected points.
+
+![Group by CPU and time](/img/flux/grouping-by-cpu-time.png)
+
+Grouping by `cpu` and `_time` is a good illustration of how grouping works.
+
+## In conclusion
+Grouping is a powerful way to shape your data into your desired output format.
+It modifies the group keys of output tables, grouping records into tables that
+all share common values within specified columns.
diff --git a/content/influxdb/v2.2/query-data/flux/histograms.md b/content/influxdb/v2.2/query-data/flux/histograms.md
new file mode 100644
index 000000000..414ea97c1
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/flux/histograms.md
@@ -0,0 +1,171 @@
+---
+title: Create histograms with Flux
+list_title: Histograms
+description: >
+  Use `histogram()` to create cumulative histograms with Flux.
+influxdb/v2.2/tags: [histogram]
+menu:
+  influxdb_2_2:
+    name: Histograms
+    parent: Query with Flux
+weight: 210
+aliases:
+  - /influxdb/v2.2/query-data/guides/histograms/
+related:
+  - /{{< latest "flux" >}}/stdlib/universe/histogram
+  - /{{< latest "flux" >}}/prometheus/metric-types/histogram/, Work with Prometheus histograms in Flux
+list_query_example: histogram
+---
+
+Histograms provide valuable insight into the distribution of your data.
+This guide walks through using Flux's `histogram()` function to transform your data into a **cumulative histogram**.
+
+If you're just getting started with Flux queries, check out the following:
+
+- [Get started with Flux](/{{< latest "flux" >}}/get-started/) for a conceptual overview of Flux and parts of a Flux query.
+- [Execute queries](/influxdb/v2.2/query-data/execute-queries/) to discover a variety of ways to run your queries.
+
+## histogram() function
+
+The [`histogram()` function](/{{< latest "flux" >}}/stdlib/universe/histogram) approximates the
+cumulative distribution of a dataset by counting data frequencies for a list of "bins."
+A **bin** is simply a range in which a data point falls.
+All data points that are less than or equal to the bound are counted in the bin.
+In the histogram output, a column is added (`le`) that represents the upper bounds of of each bin.
+Bin counts are cumulative.
+
+```js
+from(bucket: "example-bucket")
+    |> range(start: -5m)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+    |> histogram(bins: [0.0, 10.0, 20.0, 30.0])
+```
+
+{{% note %}}
+Values output by the `histogram` function represent points of data aggregated over time.
+Since values do not represent single points in time, there is no `_time` column in the output table.
+{{% /note %}}
+
+## Bin helper functions
+Flux provides two helper functions for generating histogram bins.
+Each generates an array of floats designed to be used in the `histogram()` function's `bins` parameter.
+
+### linearBins()
+The [`linearBins()` function](/{{< latest "flux" >}}/stdlib/universe/linearbins) generates a list of linearly separated floats.
+
+```js
+linearBins(start: 0.0, width: 10.0, count: 10)
+
+// Generated list: [0, 10, 20, 30, 40, 50, 60, 70, 80, 90, +Inf]
+```
+
+### logarithmicBins()
+The [`logarithmicBins()` function](/{{< latest "flux" >}}/stdlib/universe/logarithmicbins) generates a list of exponentially separated floats.
+
+```js
+logarithmicBins(start: 1.0, factor: 2.0, count: 10, infinity: true)
+
+// Generated list: [1, 2, 4, 8, 16, 32, 64, 128, 256, 512, +Inf]
+```
+
+## Histogram visualization
+The [Histogram visualization type](/influxdb/v2.2/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" />}}
+
+Use the [Histogram visualization controls](/influxdb/v2.2/visualize-data/visualization-types/histogram/#histogram-controls)
+to specify the number of bins and define groups in bins.
+
+### Histogram visualization data structure
+Because the Histogram visualization uses visualization controls to creates bins and groups,
+**do not** structure query results as histogram data.
+
+{{% note %}}
+Output of the [`histogram()` function](#histogram-function) is **not** compatible
+with the Histogram visualization type.
+View the example [below](#visualize-errors-by-severity).
+{{% /note %}}
+
+## Examples
+
+### Generate a histogram with linear bins
+```js
+from(bucket: "example-bucket")
+    |> range(start: -5m)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+    |> histogram(bins: linearBins(start: 65.5, width: 0.5, count: 20, infinity: false))
+```
+
+###### Output table
+```
+Table: keys: [_start, _stop, _field, _measurement, host]
+                   _start:time                      _stop:time           _field:string     _measurement:string               host:string                      le:float                  _value:float
+------------------------------  ------------------------------  ----------------------  ----------------------  ------------------------  ----------------------------  ----------------------------
+2018-11-07T22:19:58.423358000Z  2018-11-07T22:24:58.423358000Z            used_percent                     mem  Scotts-MacBook-Pro.local                          65.5                             5
+2018-11-07T22:19:58.423358000Z  2018-11-07T22:24:58.423358000Z            used_percent                     mem  Scotts-MacBook-Pro.local                            66                             6
+2018-11-07T22:19:58.423358000Z  2018-11-07T22:24:58.423358000Z            used_percent                     mem  Scotts-MacBook-Pro.local                          66.5                             8
+2018-11-07T22:19:58.423358000Z  2018-11-07T22:24:58.423358000Z            used_percent                     mem  Scotts-MacBook-Pro.local                            67                             9
+2018-11-07T22:19:58.423358000Z  2018-11-07T22:24:58.423358000Z            used_percent                     mem  Scotts-MacBook-Pro.local                          67.5                             9
+2018-11-07T22:19:58.423358000Z  2018-11-07T22:24:58.423358000Z            used_percent                     mem  Scotts-MacBook-Pro.local                            68                            10
+2018-11-07T22:19:58.423358000Z  2018-11-07T22:24:58.423358000Z            used_percent                     mem  Scotts-MacBook-Pro.local                          68.5                            12
+2018-11-07T22:19:58.423358000Z  2018-11-07T22:24:58.423358000Z            used_percent                     mem  Scotts-MacBook-Pro.local                            69                            12
+2018-11-07T22:19:58.423358000Z  2018-11-07T22:24:58.423358000Z            used_percent                     mem  Scotts-MacBook-Pro.local                          69.5                            15
+2018-11-07T22:19:58.423358000Z  2018-11-07T22:24:58.423358000Z            used_percent                     mem  Scotts-MacBook-Pro.local                            70                            23
+2018-11-07T22:19:58.423358000Z  2018-11-07T22:24:58.423358000Z            used_percent                     mem  Scotts-MacBook-Pro.local                          70.5                            30
+2018-11-07T22:19:58.423358000Z  2018-11-07T22:24:58.423358000Z            used_percent                     mem  Scotts-MacBook-Pro.local                            71                            30
+2018-11-07T22:19:58.423358000Z  2018-11-07T22:24:58.423358000Z            used_percent                     mem  Scotts-MacBook-Pro.local                          71.5                            30
+2018-11-07T22:19:58.423358000Z  2018-11-07T22:24:58.423358000Z            used_percent                     mem  Scotts-MacBook-Pro.local                            72                            30
+2018-11-07T22:19:58.423358000Z  2018-11-07T22:24:58.423358000Z            used_percent                     mem  Scotts-MacBook-Pro.local                          72.5                            30
+2018-11-07T22:19:58.423358000Z  2018-11-07T22:24:58.423358000Z            used_percent                     mem  Scotts-MacBook-Pro.local                            73                            30
+2018-11-07T22:19:58.423358000Z  2018-11-07T22:24:58.423358000Z            used_percent                     mem  Scotts-MacBook-Pro.local                          73.5                            30
+2018-11-07T22:19:58.423358000Z  2018-11-07T22:24:58.423358000Z            used_percent                     mem  Scotts-MacBook-Pro.local                            74                            30
+2018-11-07T22:19:58.423358000Z  2018-11-07T22:24:58.423358000Z            used_percent                     mem  Scotts-MacBook-Pro.local                          74.5                            30
+2018-11-07T22:19:58.423358000Z  2018-11-07T22:24:58.423358000Z            used_percent                     mem  Scotts-MacBook-Pro.local                            75                            30
+```
+
+### Generate a histogram with logarithmic bins
+```js
+from(bucket: "example-bucket")
+    |> range(start: -5m)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+    |> histogram(bins: logarithmicBins(start: 0.5, factor: 2.0, count: 10, infinity: false))
+```
+
+###### Output table
+```
+Table: keys: [_start, _stop, _field, _measurement, host]
+                   _start:time                      _stop:time           _field:string     _measurement:string               host:string                      le:float                  _value:float
+------------------------------  ------------------------------  ----------------------  ----------------------  ------------------------  ----------------------------  ----------------------------
+2018-11-07T22:23:36.860664000Z  2018-11-07T22:28:36.860664000Z            used_percent                     mem  Scotts-MacBook-Pro.local                           0.5                             0
+2018-11-07T22:23:36.860664000Z  2018-11-07T22:28:36.860664000Z            used_percent                     mem  Scotts-MacBook-Pro.local                             1                             0
+2018-11-07T22:23:36.860664000Z  2018-11-07T22:28:36.860664000Z            used_percent                     mem  Scotts-MacBook-Pro.local                             2                             0
+2018-11-07T22:23:36.860664000Z  2018-11-07T22:28:36.860664000Z            used_percent                     mem  Scotts-MacBook-Pro.local                             4                             0
+2018-11-07T22:23:36.860664000Z  2018-11-07T22:28:36.860664000Z            used_percent                     mem  Scotts-MacBook-Pro.local                             8                             0
+2018-11-07T22:23:36.860664000Z  2018-11-07T22:28:36.860664000Z            used_percent                     mem  Scotts-MacBook-Pro.local                            16                             0
+2018-11-07T22:23:36.860664000Z  2018-11-07T22:28:36.860664000Z            used_percent                     mem  Scotts-MacBook-Pro.local                            32                             0
+2018-11-07T22:23:36.860664000Z  2018-11-07T22:28:36.860664000Z            used_percent                     mem  Scotts-MacBook-Pro.local                            64                             2
+2018-11-07T22:23:36.860664000Z  2018-11-07T22:28:36.860664000Z            used_percent                     mem  Scotts-MacBook-Pro.local                           128                            30
+2018-11-07T22:23:36.860664000Z  2018-11-07T22:28:36.860664000Z            used_percent                     mem  Scotts-MacBook-Pro.local                           256                            30
+```
+
+### Visualize errors by severity
+Use the [Telegraf Syslog plugin](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/syslog)
+to collect error information from your system.
+Query the `severity_code` field in the `syslog` measurement:
+
+```js
+from(bucket: "example-bucket")
+    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
+    |> filter(fn: (r) => r._measurement == "syslog" and r._field == "severity_code")
+```
+
+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" />}}
+
+### Use Prometheus histograms in Flux
+
+_For information about working with Prometheus histograms in Flux, see
+[Work with Prometheus histograms](/{{< latest "flux" >}}/prometheus/metric-types/histogram/)._
\ No newline at end of file
diff --git a/content/influxdb/v2.2/query-data/flux/increase.md b/content/influxdb/v2.2/query-data/flux/increase.md
new file mode 100644
index 000000000..713eba81d
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/flux/increase.md
@@ -0,0 +1,57 @@
+---
+title: Calculate the increase
+seotitle: Calculate the increase in Flux
+list_title: Increase
+description: >
+  Use `increase()` to track increases across multiple columns in a table.
+  This function is especially useful when tracking changes in counter values that
+  wrap over time or periodically reset.
+weight: 210
+menu:
+  influxdb_2_2:
+    parent: Query with Flux
+    name: Increase
+influxdb/v2.2/tags: [query, increase, counters]
+related:
+  - /{{< latest "flux" >}}/stdlib/universe/increase/
+list_query_example: increase
+---
+
+Use [`increase()`](/{{< latest "flux" >}}/stdlib/universe/increase/)
+to track increases across multiple columns in a table.
+This function is especially useful when tracking changes in counter values that
+wrap over time or periodically reset.
+
+```js
+data
+    |> increase()
+```
+
+`increase()` returns a cumulative sum of **non-negative** differences between rows in a table.
+For example:
+
+{{< flex >}}
+{{% flex-content %}}
+**Given the following input:**
+
+| _time                | _value |
+|:-----                | ------:|
+| 2020-01-01T00:01:00Z | 1      |
+| 2020-01-01T00:02:00Z | 2      |
+| 2020-01-01T00:03:00Z | 8      |
+| 2020-01-01T00:04:00Z | 10     |
+| 2020-01-01T00:05:00Z | 0      |
+| 2020-01-01T00:06:00Z | 4      |
+{{% /flex-content %}}
+{{% flex-content %}}
+**`increase()` returns:**
+
+| _time                | _value |
+|:-----                | ------:|
+| 2020-01-01T00:02:00Z | 1      |
+| 2020-01-01T00:03:00Z | 7      |
+| 2020-01-01T00:04:00Z | 9      |
+| 2020-01-01T00:05:00Z | 9      |
+| 2020-01-01T00:06:00Z | 13     |
+{{% /flex-content %}}
+{{< /flex >}}
diff --git a/content/influxdb/v2.2/query-data/flux/join.md b/content/influxdb/v2.2/query-data/flux/join.md
new file mode 100644
index 000000000..a7cde1b59
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/flux/join.md
@@ -0,0 +1,291 @@
+---
+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.2/tags: [join, flux]
+menu:
+  influxdb_2_2:
+    name: Join
+    parent: Query with Flux
+weight: 210
+aliases:
+  - /influxdb/v2.2/query-data/guides/join/
+related:
+  - /{{< latest "flux" >}}/stdlib/universe/join
+list_query_example: join
+---
+
+The [`join()` function](/{{< latest "flux" >}}/stdlib/universe/join) merges two or more
+input streams, whose values are equal on a set of common columns, into a single output stream.
+Flux allows you to join on any columns common between two data streams and opens the door
+for operations such as cross-measurement joins and math across measurements.
+
+To illustrate a join operation, use data captured by Telegraf and stored in
+InfluxDB - memory usage and processes.
+
+In this guide, we'll join two data streams, one representing memory usage and the other representing the
+total number of running processes, then calculate the average memory usage per running process.
+
+If you're just getting started with Flux queries, check out the following:
+
+- [Get started with Flux](/{{< latest "flux" >}}/get-started/) for a conceptual overview of Flux and parts of a Flux query.
+- [Execute queries](/influxdb/v2.2/query-data/execute-queries/) to discover a variety of ways to run your queries.
+
+## Define stream variables
+In order to perform a join, you must have two streams of data.
+Assign a variable to each data stream.
+
+### Memory used variable
+Define a `memUsed` variable that filters on the `mem` measurement and the `used` field.
+This returns the amount of memory (in bytes) used.
+
+###### memUsed stream definition
+```js
+memUsed = from(bucket: "example-bucket")
+    |> range(start: -5m)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used")
+```
+
+{{% truncate %}}
+###### memUsed data output
+```
+Table: keys: [_start, _stop, _field, _measurement, host]
+                   _start:time                      _stop:time           _field:string     _measurement:string               host:string                      _time:time                  _value:int
+------------------------------  ------------------------------  ----------------------  ----------------------  ------------------------  ------------------------------  --------------------------
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                    used                     mem               host1.local  2018-11-06T05:50:00.000000000Z                 10956333056
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                    used                     mem               host1.local  2018-11-06T05:50:10.000000000Z                 11014008832
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                    used                     mem               host1.local  2018-11-06T05:50:20.000000000Z                 11373428736
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                    used                     mem               host1.local  2018-11-06T05:50:30.000000000Z                 11001421824
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                    used                     mem               host1.local  2018-11-06T05:50:40.000000000Z                 10985852928
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                    used                     mem               host1.local  2018-11-06T05:50:50.000000000Z                 10992279552
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                    used                     mem               host1.local  2018-11-06T05:51:00.000000000Z                 11053568000
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                    used                     mem               host1.local  2018-11-06T05:51:10.000000000Z                 11092242432
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                    used                     mem               host1.local  2018-11-06T05:51:20.000000000Z                 11612774400
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                    used                     mem               host1.local  2018-11-06T05:51:30.000000000Z                 11131961344
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                    used                     mem               host1.local  2018-11-06T05:51:40.000000000Z                 11124805632
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                    used                     mem               host1.local  2018-11-06T05:51:50.000000000Z                 11332464640
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                    used                     mem               host1.local  2018-11-06T05:52:00.000000000Z                 11176923136
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                    used                     mem               host1.local  2018-11-06T05:52:10.000000000Z                 11181068288
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                    used                     mem               host1.local  2018-11-06T05:52:20.000000000Z                 11182579712
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                    used                     mem               host1.local  2018-11-06T05:52:30.000000000Z                 11238862848
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                    used                     mem               host1.local  2018-11-06T05:52:40.000000000Z                 11275296768
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                    used                     mem               host1.local  2018-11-06T05:52:50.000000000Z                 11225411584
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                    used                     mem               host1.local  2018-11-06T05:53:00.000000000Z                 11252690944
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                    used                     mem               host1.local  2018-11-06T05:53:10.000000000Z                 11227029504
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                    used                     mem               host1.local  2018-11-06T05:53:20.000000000Z                 11201646592
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                    used                     mem               host1.local  2018-11-06T05:53:30.000000000Z                 11227897856
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                    used                     mem               host1.local  2018-11-06T05:53:40.000000000Z                 11330428928
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                    used                     mem               host1.local  2018-11-06T05:53:50.000000000Z                 11347976192
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                    used                     mem               host1.local  2018-11-06T05:54:00.000000000Z                 11368271872
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                    used                     mem               host1.local  2018-11-06T05:54:10.000000000Z                 11269623808
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                    used                     mem               host1.local  2018-11-06T05:54:20.000000000Z                 11295637504
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                    used                     mem               host1.local  2018-11-06T05:54:30.000000000Z                 11354423296
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                    used                     mem               host1.local  2018-11-06T05:54:40.000000000Z                 11379687424
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                    used                     mem               host1.local  2018-11-06T05:54:50.000000000Z                 11248926720
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                    used                     mem               host1.local  2018-11-06T05:55:00.000000000Z                 11292524544
+```
+{{% /truncate %}}
+
+### Total processes variable
+Define a `procTotal` variable that filters on the `processes` measurement and the `total` field.
+This returns the number of running processes.
+
+###### procTotal stream definition
+```js
+procTotal = from(bucket: "example-bucket")
+    |> range(start: -5m)
+    |> filter(fn: (r) => r._measurement == "processes" and r._field == "total")
+```
+
+{{% truncate %}}
+###### procTotal data output
+```
+Table: keys: [_start, _stop, _field, _measurement, host]
+                   _start:time                      _stop:time           _field:string     _measurement:string               host:string                      _time:time                  _value:int
+------------------------------  ------------------------------  ----------------------  ----------------------  ------------------------  ------------------------------  --------------------------
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                   total               processes               host1.local  2018-11-06T05:50:00.000000000Z                         470
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                   total               processes               host1.local  2018-11-06T05:50:10.000000000Z                         470
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                   total               processes               host1.local  2018-11-06T05:50:20.000000000Z                         471
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                   total               processes               host1.local  2018-11-06T05:50:30.000000000Z                         470
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                   total               processes               host1.local  2018-11-06T05:50:40.000000000Z                         469
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                   total               processes               host1.local  2018-11-06T05:50:50.000000000Z                         471
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                   total               processes               host1.local  2018-11-06T05:51:00.000000000Z                         470
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                   total               processes               host1.local  2018-11-06T05:51:10.000000000Z                         470
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                   total               processes               host1.local  2018-11-06T05:51:20.000000000Z                         470
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                   total               processes               host1.local  2018-11-06T05:51:30.000000000Z                         470
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                   total               processes               host1.local  2018-11-06T05:51:40.000000000Z                         469
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                   total               processes               host1.local  2018-11-06T05:51:50.000000000Z                         471
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                   total               processes               host1.local  2018-11-06T05:52:00.000000000Z                         471
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                   total               processes               host1.local  2018-11-06T05:52:10.000000000Z                         470
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                   total               processes               host1.local  2018-11-06T05:52:20.000000000Z                         470
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                   total               processes               host1.local  2018-11-06T05:52:30.000000000Z                         471
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                   total               processes               host1.local  2018-11-06T05:52:40.000000000Z                         472
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                   total               processes               host1.local  2018-11-06T05:52:50.000000000Z                         471
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                   total               processes               host1.local  2018-11-06T05:53:00.000000000Z                         470
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                   total               processes               host1.local  2018-11-06T05:53:10.000000000Z                         470
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                   total               processes               host1.local  2018-11-06T05:53:20.000000000Z                         470
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                   total               processes               host1.local  2018-11-06T05:53:30.000000000Z                         471
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                   total               processes               host1.local  2018-11-06T05:53:40.000000000Z                         471
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                   total               processes               host1.local  2018-11-06T05:53:50.000000000Z                         471
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                   total               processes               host1.local  2018-11-06T05:54:00.000000000Z                         471
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                   total               processes               host1.local  2018-11-06T05:54:10.000000000Z                         470
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                   total               processes               host1.local  2018-11-06T05:54:20.000000000Z                         471
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                   total               processes               host1.local  2018-11-06T05:54:30.000000000Z                         473
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                   total               processes               host1.local  2018-11-06T05:54:40.000000000Z                         471
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                   total               processes               host1.local  2018-11-06T05:54:50.000000000Z                         471
+2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z                   total               processes               host1.local  2018-11-06T05:55:00.000000000Z                         471
+```
+{{% /truncate %}}
+
+## Join the two data streams
+With the two data streams defined, use the `join()` function to join them together.
+`join()` requires two parameters:
+
+##### `tables`
+A map of tables to join with keys by which they will be aliased.
+In the example below, `mem` is the alias for `memUsed` and `proc` is the alias for `procTotal`.
+
+##### `on`
+An array of strings defining the columns on which the tables will be joined.
+_**Both tables must have all columns specified in this list.**_
+
+```js
+join(
+    tables: {mem:memUsed, proc:procTotal},
+    on: ["_time", "_stop", "_start", "host"],
+)
+```
+
+{{% truncate %}}
+###### Joined output table
+```
+Table: keys: [_field_mem, _field_proc, _measurement_mem, _measurement_proc, _start, _stop, host]
+     _field_mem:string      _field_proc:string  _measurement_mem:string  _measurement_proc:string                     _start:time                      _stop:time               host:string                      _time:time              _value_mem:int             _value_proc:int
+----------------------  ----------------------  -----------------------  ------------------------  ------------------------------  ------------------------------  ------------------------  ------------------------------  --------------------------  --------------------------
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:50:00.000000000Z                 10956333056                         470
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:50:10.000000000Z                 11014008832                         470
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:50:20.000000000Z                 11373428736                         471
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:50:30.000000000Z                 11001421824                         470
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:50:40.000000000Z                 10985852928                         469
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:50:50.000000000Z                 10992279552                         471
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:51:00.000000000Z                 11053568000                         470
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:51:10.000000000Z                 11092242432                         470
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:51:20.000000000Z                 11612774400                         470
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:51:30.000000000Z                 11131961344                         470
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:51:40.000000000Z                 11124805632                         469
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:51:50.000000000Z                 11332464640                         471
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:52:00.000000000Z                 11176923136                         471
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:52:10.000000000Z                 11181068288                         470
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:52:20.000000000Z                 11182579712                         470
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:52:30.000000000Z                 11238862848                         471
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:52:40.000000000Z                 11275296768                         472
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:52:50.000000000Z                 11225411584                         471
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:53:00.000000000Z                 11252690944                         470
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:53:10.000000000Z                 11227029504                         470
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:53:20.000000000Z                 11201646592                         470
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:53:30.000000000Z                 11227897856                         471
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:53:40.000000000Z                 11330428928                         471
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:53:50.000000000Z                 11347976192                         471
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:54:00.000000000Z                 11368271872                         471
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:54:10.000000000Z                 11269623808                         470
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:54:20.000000000Z                 11295637504                         471
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:54:30.000000000Z                 11354423296                         473
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:54:40.000000000Z                 11379687424                         471
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:54:50.000000000Z                 11248926720                         471
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:55:00.000000000Z                 11292524544                         471
+```
+{{% /truncate %}}
+
+Notice the output table includes the following columns:
+
+- `_field_mem`
+- `_field_proc`
+- `_measurement_mem`
+- `_measurement_proc`
+- `_value_mem`
+- `_value_proc`
+
+These represent the columns with values unique to the two input tables.
+
+## Calculate and create a new table
+With the two streams of data joined into a single table, use the
+[`map()` function](/{{< latest "flux" >}}/stdlib/universe/map)
+to build a new table by mapping the existing `_time` column to a new `_time`
+column and dividing `_value_mem` by `_value_proc` and mapping it to a
+new `_value` column.
+
+```js
+join(tables: {mem: memUsed, proc: procTotal}, on: ["_time", "_stop", "_start", "host"])
+    |> map(fn: (r) => ({_time: r._time, _value: r._value_mem / r._value_proc}))
+```
+
+{{% truncate %}}
+###### Mapped table
+```
+Table: keys: [_field_mem, _field_proc, _measurement_mem, _measurement_proc, _start, _stop, host]
+     _field_mem:string      _field_proc:string  _measurement_mem:string  _measurement_proc:string                     _start:time                      _stop:time               host:string                      _time:time                  _value:int
+----------------------  ----------------------  -----------------------  ------------------------  ------------------------------  ------------------------------  ------------------------  ------------------------------  --------------------------
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:50:00.000000000Z                    23311346
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:50:10.000000000Z                    23434061
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:50:20.000000000Z                    24147407
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:50:30.000000000Z                    23407280
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:50:40.000000000Z                    23423993
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:50:50.000000000Z                    23338173
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:51:00.000000000Z                    23518229
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:51:10.000000000Z                    23600515
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:51:20.000000000Z                    24708030
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:51:30.000000000Z                    23685024
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:51:40.000000000Z                    23720267
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:51:50.000000000Z                    24060434
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:52:00.000000000Z                    23730197
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:52:10.000000000Z                    23789506
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:52:20.000000000Z                    23792722
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:52:30.000000000Z                    23861704
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:52:40.000000000Z                    23888340
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:52:50.000000000Z                    23833145
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:53:00.000000000Z                    23941895
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:53:10.000000000Z                    23887296
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:53:20.000000000Z                    23833290
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:53:30.000000000Z                    23838424
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:53:40.000000000Z                    24056112
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:53:50.000000000Z                    24093367
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:54:00.000000000Z                    24136458
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:54:10.000000000Z                    23977922
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:54:20.000000000Z                    23982245
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:54:30.000000000Z                    24005123
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:54:40.000000000Z                    24160695
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:54:50.000000000Z                    23883071
+                  used                   total                      mem                 processes  2018-11-06T05:50:00.000000000Z  2018-11-06T05:55:00.000000000Z  Scotts-MacBook-Pro.local  2018-11-06T05:55:00.000000000Z                    23975635
+```
+{{% /truncate %}}
+
+This table represents the average amount of memory in bytes per running process.
+
+
+## Real world example
+The following function calculates the batch sizes written to an InfluxDB cluster by joining
+fields from `httpd` and `write` measurements in order to compare `pointReq` and `writeReq`.
+The results are grouped by cluster ID so you can make comparisons across clusters.
+
+```js
+batchSize = (cluster_id, start=-1m, interval=10s) => {
+    httpd = from(bucket: "telegraf")
+        |> range(start: start)
+        |> filter(fn: (r) => r._measurement == "influxdb_httpd" and r._field == "writeReq" and r.cluster_id == cluster_id)
+        |> aggregateWindow(every: interval, fn: mean)
+        |> derivative(nonNegative: true, unit: 60s)
+
+    write = from(bucket: "telegraf")
+        |> range(start: start)
+        |> filter(fn: (r) => r._measurement == "influxdb_write" and r._field == "pointReq" and r.cluster_id == cluster_id)
+        |> aggregateWindow(every: interval, fn: max)
+        |> derivative(nonNegative: true, unit: 60s)
+
+    return join(tables: {httpd: httpd, write: write}, on: ["_time", "_stop", "_start", "host"])
+        |> map(fn: (r) => ({_time: r._time, _value: r._value_httpd / r._value_write}))
+        |> group(columns: cluster_id)
+}
+
+batchSize(cluster_id: "enter cluster id here")
+```
diff --git a/content/influxdb/v2.2/query-data/flux/manipulate-timestamps.md b/content/influxdb/v2.2/query-data/flux/manipulate-timestamps.md
new file mode 100644
index 000000000..08a233658
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/flux/manipulate-timestamps.md
@@ -0,0 +1,212 @@
+---
+title: Manipulate timestamps with Flux
+list_title: Manipulate timestamps
+description: >
+  Use Flux to process and manipulate timestamps.
+menu:
+  influxdb_2_2:
+    name: Manipulate timestamps
+    parent: Query with Flux
+weight: 220
+aliases:
+  - /influxdb/v2.2/query-data/guides/manipulate-timestamps/
+related:
+  - /{{< latest "flux" >}}/stdlib/universe/now/
+  - /{{< latest "flux" >}}/stdlib/system/time/
+  - /{{< latest "flux" >}}/stdlib/universe/time/
+  - /{{< latest "flux" >}}/stdlib/universe/uint/
+  - /{{< latest "flux" >}}/stdlib/universe/int/
+  - /{{< latest "flux" >}}/stdlib/universe/truncatetimecolumn/
+  - /{{< latest "flux" >}}/stdlib/date/truncate/
+  - /{{< latest "flux" >}}/stdlib/experimental/addduration/
+  - /{{< latest "flux" >}}/stdlib/experimental/subduration/
+---
+
+Every point stored in InfluxDB has an associated timestamp.
+Use Flux to process and manipulate timestamps to suit your needs.
+
+- [Convert timestamp format](#convert-timestamp-format)
+- [Calculate the duration between two timestamps](#calculate-the-duration-between-two-timestamps)
+- [Retrieve the current time](#retrieve-the-current-time)
+- [Normalize irregular timestamps](#normalize-irregular-timestamps)
+- [Use timestamps and durations together](#use-timestamps-and-durations-together)
+
+{{% note %}}
+If you're just getting started with Flux queries, check out the following:
+
+- [Get started with Flux](/{{< latest "flux" >}}/get-started/) for a conceptual overview of Flux and parts of a Flux query.
+- [Execute queries](/influxdb/v2.2/query-data/execute-queries/) to discover a variety of ways to run your queries.
+{{% /note %}}
+
+
+## Convert timestamp format
+
+- [Unix nanosecond to RFC3339](#unix-nanosecond-to-rfc3339)
+- [RFC3339 to Unix nanosecond](#rfc3339-to-unix-nanosecond)
+
+### Unix nanosecond to RFC3339
+Use the [`time()` function](/{{< latest "flux" >}}/stdlib/universe/time/)
+to convert a [Unix **nanosecond** timestamp](/influxdb/v2.2/reference/glossary/#unix-timestamp)
+to an [RFC3339 timestamp](/influxdb/v2.2/reference/glossary/#rfc3339-timestamp).
+
+```js
+time(v: 1568808000000000000)
+// Returns 2019-09-18T12:00:00.000000000Z
+```
+
+### RFC3339 to Unix nanosecond
+Use the [`uint()` function](/{{< latest "flux" >}}/stdlib/universe/uint/)
+to convert an RFC3339 timestamp to a Unix nanosecond timestamp.
+
+```js
+uint(v: 2019-09-18T12:00:00.000000000Z)
+// Returns 1568808000000000000
+```
+
+## Calculate the duration between two timestamps
+Flux doesn't support mathematical operations using [time type](/{{< latest "flux" >}}/spec/types/#time-types) values.
+To calculate the duration between two timestamps:
+
+1. Use the `uint()` function to convert each timestamp to a Unix nanosecond timestamp.
+2. Subtract one Unix nanosecond timestamp from the other.
+3. Use the `duration()` function to convert the result into a duration.
+
+```js
+time1 = uint(v: 2019-09-17T21:12:05Z)
+time2 = uint(v: 2019-09-18T22:16:35Z)
+
+duration(v: time2 - time1)
+// Returns 25h4m30s
+```
+
+{{% note %}}
+Flux doesn't support duration column types.
+To store a duration in a column, use the [`string()` function](/{{< latest "flux" >}}/stdlib/universe/string/)
+to convert the duration to a string.
+{{% /note %}}
+
+## Retrieve the current time
+- [Current UTC time](#current-utc-time)
+- [Current system time](#current-system-time)
+
+### Current UTC time
+Use the [`now()` function](/{{< latest "flux" >}}/stdlib/universe/now/) to
+return the current UTC time in RFC3339 format.
+
+```js
+now()
+```
+
+{{% note %}}
+`now()`  is cached at runtime, so all instances of `now()` in a Flux script
+return the same value.
+{{% /note %}}
+
+### Current system time
+Import the `system` package and use the [`system.time()` function](/{{< latest "flux" >}}/stdlib/system/time/)
+to return the current system time of the host machine in RFC3339 format.
+
+```js
+import "system"
+
+system.time()
+```
+
+{{% note %}}
+`system.time()` returns the time it is executed, so each instance of `system.time()`
+in a Flux script returns a unique value.
+{{% /note %}}
+
+## Normalize irregular timestamps
+To normalize irregular timestamps, truncate all `_time` values to a specified unit
+with the [`truncateTimeColumn()` function](/{{< latest "flux" >}}/stdlib/universe/truncatetimecolumn/).
+This is useful in [`join()`](/{{< latest "flux" >}}/stdlib/universe/join/)
+and [`pivot()`](/{{< latest "flux" >}}/stdlib/universe/pivot/)
+operations where points should align by time, but timestamps vary slightly.
+
+```js
+data
+    |> truncateTimeColumn(unit: 1m)
+```
+
+{{< flex >}}
+{{% flex-content %}}
+**Input:**
+
+| _time                | _value |
+|:-----                | ------:|
+| 2020-01-01T00:00:49Z | 2.0    |
+| 2020-01-01T00:01:01Z | 1.9    |
+| 2020-01-01T00:03:22Z | 1.8    |
+| 2020-01-01T00:04:04Z | 1.9    |
+| 2020-01-01T00:05:38Z | 2.1    |
+{{% /flex-content %}}
+{{% flex-content %}}
+**Output:**
+
+| _time                | _value |
+|:-----                | ------:|
+| 2020-01-01T00:00:00Z | 2.0    |
+| 2020-01-01T00:01:00Z | 1.9    |
+| 2020-01-01T00:03:00Z | 1.8    |
+| 2020-01-01T00:04:00Z | 1.9    |
+| 2020-01-01T00:05:00Z | 2.1    |
+{{% /flex-content %}}
+{{< /flex >}}
+
+## Use timestamps and durations together
+- [Add a duration to a timestamp](#add-a-duration-to-a-timestamp)
+- [Subtract a duration from a timestamp](#subtract-a-duration-from-a-timestamp)
+
+### Add a duration to a timestamp
+The [`experimental.addDuration()` function](/{{< latest "flux" >}}/stdlib/experimental/to/addduration/)
+adds a duration to a specified time and returns the resulting time.
+
+{{% warn %}}
+By using `experimental.addDuration()`, you accept the
+[risks of experimental functions](/{{< latest "flux" >}}/stdlib/experimental/to/#experimental-functions-are-subject-to-change).
+{{% /warn %}}
+
+```js
+import "experimental"
+
+experimental.addDuration(d: 6h, to: 2019-09-16T12:00:00Z)
+
+// Returns 2019-09-16T18:00:00.000000000Z
+```
+
+### Subtract a duration from a timestamp
+The [`experimental.subDuration()` function](/{{< latest "flux" >}}/stdlib/experimental/to/subduration/)
+subtracts a duration from a specified time and returns the resulting time.
+
+{{% warn %}}
+By using `experimental.subDuration()`, you accept the
+[risks of experimental functions](/{{< latest "flux" >}}/stdlib/experimental/to/#experimental-functions-are-subject-to-change).
+{{% /warn %}}
+
+```js
+import "experimental"
+
+experimental.subDuration(d: 6h, from: 2019-09-16T12:00:00Z)
+
+// Returns 2019-09-16T06:00:00.000000000Z
+```
+
+### Shift a timestamp forward or backward
+
+The [timeShift()](/{{< latest "flux" >}}/stdlib/universe/timeshift/) function adds the specified duration of time to each value in time columns (`_start`, `_stop`, `_time`).
+
+Shift forward in time:
+
+```js
+from(bucket: "example-bucket")
+    |> range(start: -5m)
+    |> timeShift(duration: 12h)
+```
+Shift backward in time:
+
+```js
+from(bucket: "example-bucket")
+    |> range(start: -5m)
+    |> timeShift(duration: -12h)
+```
diff --git a/content/influxdb/v2.2/query-data/flux/mathematic-operations.md b/content/influxdb/v2.2/query-data/flux/mathematic-operations.md
new file mode 100644
index 000000000..e5702d322
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/flux/mathematic-operations.md
@@ -0,0 +1,208 @@
+---
+title: Transform data with mathematic operations
+seotitle: Transform data with mathematic operations in Flux
+list_title: Transform data with math
+description: >
+  Use `map()` to remap column values and apply mathematic operations.
+influxdb/v2.2/tags: [math, flux]
+menu:
+  influxdb_2_2:
+    name: Transform data with math
+    parent: Query with Flux
+weight: 208
+aliases:
+  - /influxdb/v2.2/query-data/guides/mathematic-operations/
+related:
+  - /{{< latest "flux" >}}/stdlib/universe/map
+  - /{{< latest "flux" >}}/stdlib/universe/aggregates/reduce/
+  - /{{< latest "flux" >}}/language/operators/
+  - /{{< latest "flux" >}}/function-types/#type-conversions, Flux type-conversion functions
+  - /influxdb/v2.2/query-data/flux/calculate-percentages/
+list_query_example: map_math
+---
+
+[Flux](/{{< latest "flux" >}}/), InfluxData's data scripting and query language,
+supports mathematic expressions in data transformations.
+This article describes how to use [Flux arithmetic operators](/{{< latest "flux" >}}/spec/operators/#arithmetic-operators)
+to "map" over data and transform values using mathematic operations.
+
+If you're just getting started with Flux queries, check out the following:
+
+- [Get started with Flux](/{{< latest "flux" >}}/get-started/) for a conceptual overview of Flux and parts of a Flux query.
+- [Execute queries](/influxdb/v2.2/query-data/execute-queries/) to discover a variety of ways to run your queries.
+
+##### Basic mathematic operations
+```js
+// Examples executed using the Flux REPL
+> 9 + 9
+18
+> 22 - 14
+8
+> 6 * 5
+30
+> 21 / 7
+3
+```
+
+<p style="font-size:.85rem;font-style:italic;margin-top:-2rem;">See <a href="/influxdb/v2.2/tools/repl/">Flux Read-Eval-Print Loop (REPL)</a>.</p>
+
+{{% note %}}
+#### Operands must be the same type
+Operands in Flux mathematic operations must be the same data type.
+For example, integers cannot be used in operations with floats.
+Otherwise, you will get an error similar to:
+
+```
+Error: type error: float != int
+```
+
+To convert operands to the same type, use [type-conversion functions](/{{< latest "flux" >}}/stdlib/universe/)
+or manually format operands.
+The operand data type determines the output data type.
+For example:
+
+```js
+100 // Parsed as an integer
+100.0 // Parsed as a float
+
+// Example evaluations
+> 20 / 8
+2
+
+> 20.0 / 8.0
+2.5
+```
+{{% /note %}}
+
+## Custom mathematic functions
+Flux lets you [create custom functions](/influxdb/v2.2/query-data/flux/custom-functions) that use mathematic operations.
+View the examples below.
+
+###### Custom multiplication function
+```js
+multiply = (x, y) => x * y
+
+multiply(x: 10, y: 12)
+// Returns 120
+```
+
+###### Custom percentage function
+```js
+percent = (sample, total) => (sample / total) * 100.0
+
+percent(sample: 20.0, total: 80.0)
+// Returns 25.0
+```
+
+### Transform values in a data stream
+To transform multiple values in an input stream, your function needs to:
+
+- [Handle piped-forward data](/influxdb/v2.2/query-data/flux/custom-functions/#use-piped-forward-data-in-a-custom-function).
+- Each operand necessary for the calculation exists in each row _(see [Pivot vs join](#pivot-vs-join) below)_.
+- Use the [`map()` function](/{{< latest "flux" >}}/stdlib/universe/map) to iterate over each row.
+
+The example `multiplyByX()` function below includes:
+
+- A `tables` parameter that represents the input data stream (`<-`).
+- An `x` parameter which is the number by which values in the `_value` column are multiplied.
+- A `map()` function that iterates over each row in the input stream.
+  It uses the `with` operator to preserve existing columns in each row.
+  It also multiples the `_value` column by `x`.
+
+```js
+multiplyByX = (x, tables=<-) => tables
+    |> map(fn: (r) => ({r with _value: r._value * x}))
+
+data
+    |> multiplyByX(x: 10)
+```
+
+## Examples
+
+### Convert bytes to gigabytes
+To convert active memory from bytes to gigabytes (GB), divide the `active` field
+in the `mem` measurement by 1,073,741,824.
+
+The `map()` function iterates over each row in the piped-forward data and defines
+a new `_value` by dividing the original `_value` by 1073741824.
+
+```js
+from(bucket: "example-bucket")
+    |> range(start: -10m)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "active")
+    |> map(fn: (r) => ({r with _value: r._value / 1073741824}))
+```
+
+You could turn that same calculation into a function:
+
+```js
+bytesToGB = (tables=<-) => tables
+    |> map(fn: (r) => ({r with _value: r._value / 1073741824}))
+
+data
+    |> bytesToGB()
+```
+
+#### Include partial gigabytes
+Because the original metric (bytes) is an integer, the output of the operation is an integer and does not include partial GBs.
+To calculate partial GBs, convert the `_value` column and its values to floats using the
+[`float()` function](/{{< latest "flux" >}}/stdlib/universe/float)
+and format the denominator in the division operation as a float.
+
+```js
+bytesToGB = (tables=<-) => tables
+    |> map(fn: (r) => ({r with _value: float(v: r._value) / 1073741824.0}))
+```
+
+### Calculate a percentage
+To calculate a percentage, use simple division, then multiply the result by 100.
+
+```js
+> 1.0 / 4.0 * 100.0
+25.0
+```
+
+_For an in-depth look at calculating percentages, see [Calculate percentages](/influxdb/v2.2/query-data/flux/calculate-percentages)._
+
+## Pivot vs join
+To query and use values in mathematical operations in Flux, operand values must
+exists in a single row.
+Both `pivot()` and `join()` will do this, but there are important differences between the two:
+
+#### Pivot is more performant
+`pivot()` reads and operates on a single stream of data.
+`join()` requires two streams of data and the overhead of reading and combining
+both streams can be significant, especially for larger data sets.
+
+#### Use join for multiple data sources
+Use `join()` when querying data from different buckets or data sources.
+
+##### Pivot fields into columns for mathematic calculations
+```js
+data
+    |> pivot(rowKey: ["_time"], columnKey: ["_field"], valueColumn: "_value")
+    |> map(fn: (r) => ({r with _value: (r.field1 + r.field2) / r.field3 * 100.0}))
+```
+
+##### Join multiple data sources for mathematic calculations
+```js
+import "sql"
+import "influxdata/influxdb/secrets"
+
+pgUser = secrets.get(key: "POSTGRES_USER")
+pgPass = secrets.get(key: "POSTGRES_PASSWORD")
+pgHost = secrets.get(key: "POSTGRES_HOST")
+
+t1 = sql.from(
+    driverName: "postgres",
+    dataSourceName: "postgresql://${pgUser}:${pgPass}@${pgHost}",
+    query: "SELECT id, name, available FROM example_table",
+)
+
+t2 = from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement" and r._field == "example-field")
+
+join(tables: {t1: t1, t2: t2}, on: ["id"])
+    |> map(fn: (r) => ({r with _value: r._value_t2 / r.available_t1 * 100.0}))
+```
diff --git a/content/influxdb/v2.2/query-data/flux/median.md b/content/influxdb/v2.2/query-data/flux/median.md
new file mode 100644
index 000000000..3bb0d615f
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/flux/median.md
@@ -0,0 +1,149 @@
+---
+title: Find median values
+seotitle: Find median values in Flux
+list_title: Median
+description: >
+  Use `median()` to return a value representing the `0.5` quantile (50th percentile) or median of input data.
+weight: 210
+menu:
+  influxdb_2_2:
+    parent: Query with Flux
+    name: Median
+influxdb/v2.2/tags: [query, median]
+related:
+  - /influxdb/v2.2/query-data/flux/percentile-quantile/
+  - /{{< latest "flux" >}}/stdlib/universe/median/
+  - /{{< latest "flux" >}}/stdlib/universe/quantile/
+list_query_example: median
+---
+
+Use the [`median()` function](/{{< latest "flux" >}}/stdlib/universe/median/)
+to return a value representing the `0.5` quantile (50th percentile) or median of input data.
+
+## Select a method for calculating the median
+Select one of the following methods to calculate the median:
+
+- [estimate_tdigest](#estimate_tdigest)
+- [exact_mean](#exact_mean)
+- [exact_selector](#exact_selector)
+
+### estimate_tdigest
+**(Default)** An aggregate method that uses a [t-digest data structure](https://github.com/tdunning/t-digest)
+to compute an accurate `0.5` quantile estimate on large data sources.
+Output tables consist of a single row containing the calculated median.
+
+{{< flex >}}
+{{% flex-content %}}
+**Given the following input table:**
+
+| _time                | _value |
+|:-----                | ------:|
+| 2020-01-01T00:01:00Z | 1.0    |
+| 2020-01-01T00:02:00Z | 1.0    |
+| 2020-01-01T00:03:00Z | 2.0    |
+| 2020-01-01T00:04:00Z | 3.0    |
+{{% /flex-content %}}
+{{% flex-content %}}
+**`estimate_tdigest` returns:**
+
+| _value |
+|:------:|
+| 1.5    |
+{{% /flex-content %}}
+{{< /flex >}}
+
+### exact_mean
+An aggregate method that takes the average of the two points closest to the `0.5` quantile value.
+Output tables consist of a single row containing the calculated median.
+
+{{< flex >}}
+{{% flex-content %}}
+**Given the following input table:**
+
+| _time                | _value |
+|:-----                | ------:|
+| 2020-01-01T00:01:00Z | 1.0    |
+| 2020-01-01T00:02:00Z | 1.0    |
+| 2020-01-01T00:03:00Z | 2.0    |
+| 2020-01-01T00:04:00Z | 3.0    |
+{{% /flex-content %}}
+{{% flex-content %}}
+**`exact_mean` returns:**
+
+| _value |
+|:------:|
+| 1.5    |
+{{% /flex-content %}}
+{{< /flex >}}
+
+### exact_selector
+A selector method that returns the data point for which at least 50% of points are less than.
+Output tables consist of a single row containing the calculated median.
+
+{{< flex >}}
+{{% flex-content %}}
+**Given the following input table:**
+
+| _time                | _value |
+|:-----                | ------:|
+| 2020-01-01T00:01:00Z | 1.0    |
+| 2020-01-01T00:02:00Z | 1.0    |
+| 2020-01-01T00:03:00Z | 2.0    |
+| 2020-01-01T00:04:00Z | 3.0    |
+{{% /flex-content %}}
+{{% flex-content %}}
+**`exact_selector` returns:**
+
+| _time                | _value |
+|:-----                | ------:|
+| 2020-01-01T00:02:00Z | 1.0    |
+{{% /flex-content %}}
+{{< /flex >}}
+
+{{% note %}}
+The examples below use the [example data variable](/influxdb/v2.2/query-data/flux/#example-data-variable).
+{{% /note %}}
+
+## Find the value that represents the median
+Use the default method, `"estimate_tdigest"`, to return all rows in a table that
+contain values in the 50th percentile of data in the table.
+
+```js
+data
+    |> median()
+```
+
+## Find the average of values closest to the median
+Use the `exact_mean` method to return a single row per input table containing the
+average of the two values closest to the mathematical median of data in the table.
+
+```js
+data
+    |> median(method: "exact_mean")
+```
+
+## Find the point with the median value
+Use the `exact_selector` method to return a single row per input table containing the
+value that 50% of values in the table are less than.
+
+```js
+data
+    |> median(method: "exact_selector")
+```
+
+## Use median() with aggregateWindow()
+[`aggregateWindow()`](/{{< latest "flux" >}}/stdlib/universe/aggregatewindow/)
+segments data into windows of time, aggregates data in each window into a single
+point, and then removes the time-based segmentation.
+It is primarily used to [downsample data](/influxdb/v2.2/process-data/common-tasks/downsample-data/).
+
+To specify the [median calculation method](#select-a-method-for-calculating-the-median) in `aggregateWindow()`, use the
+[full function syntax](/{{< latest "flux" >}}/stdlib/universe/aggregatewindow/#specify-parameters-of-the-aggregate-function):
+
+```js
+data
+  |> aggregateWindow(
+    every: 5m,
+    fn: (tables=<-, column) => tables |> median(method: "exact_selector"),
+  )
+```
diff --git a/content/influxdb/v2.2/query-data/flux/monitor-states.md b/content/influxdb/v2.2/query-data/flux/monitor-states.md
new file mode 100644
index 000000000..8b330621d
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/flux/monitor-states.md
@@ -0,0 +1,189 @@
+---
+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.2/tags: [states, monitor, flux]
+menu:
+  influxdb_2_2:
+    name: Monitor states
+    parent: Query with Flux
+weight: 220
+aliases:
+  - /influxdb/v2.2/query-data/guides/monitor-states/
+related:
+  - /{{< latest "flux" >}}/stdlib/universe/stateduration/
+  - /{{< latest "flux" >}}/stdlib/universe/statecount/
+---
+
+Flux helps you monitor states in your metrics and events:
+
+- [Find how long a state persists](#find-how-long-a-state-persists)
+- [Count the number of consecutive states](#count-the-number-of-consecutive-states)
+<!-- - [Detect state changes](#detect-state-changes) -->
+
+If you're just getting started with Flux queries, check out the following:
+
+- [Get started with Flux](/{{< latest "flux" >}}/get-started/) for a conceptual overview of Flux.
+- [Execute queries](/influxdb/v2.2/query-data/execute-queries/) to discover a variety of ways to run your queries.
+
+## Find how long a state persists
+
+Use [`stateDuration()`](/{{< latest "flux" >}}/stdlib/universe/stateduration/)
+to calculate the duration of consecutive rows with a specified state.
+For each consecutive point that matches the specified state, `stateDuration()`
+increments and stores the duration (in the specified unit) in a user-defined column.
+
+Include the following information:
+
+- **Column to search:** any tag key, tag value, field key, field value, or measurement.
+- **Value:** the value (or state) to search for in the specified column.
+- **State duration column:** a new column to store the state duration─the length of time that the specified value persists.
+- **Unit:** the unit of time (`1s` (by default), `1m`, `1h`) used to increment the state duration.
+
+```js
+data
+    |> stateDuration(fn: (r) => r.column_to_search == "value_to_search_for", column: "state_duration", unit: 1s)
+```
+
+- For the first point that evaluates `true`, the state duration is set to `0`.
+  For each consecutive point that evaluates `true`, the state duration
+  increases by the time interval between each consecutive point (in specified units).
+- If the state is `false`, the state duration is reset to `-1`.
+
+### Example query with stateDuration()
+
+The following query searches the `doors` bucket over the past 5 minutes to find how many seconds a door has been `closed`.
+
+```js
+from(bucket: "doors")
+    |> range(start: -5m)
+    |> stateDuration(fn: (r) => r._value == "closed", column: "door_closed", unit: 1s)
+```
+
+In this example, `door_closed` is the **State duration** column.
+If you write data to the `doors` bucket every minute, the state duration
+increases by `60s` for each consecutive point where `_value` is `closed`.
+If `_value` is not `closed`, the state duration is reset to `0`.
+
+#### Query results
+
+Results for the example query above may look like this (for simplicity, we've omitted the measurement, tag, and field columns):
+
+| _time                | _value | door_closed |
+| :------------------- | :----: | ----------: |
+| 2019-10-26T17:39:16Z | closed |           0 |
+| 2019-10-26T17:40:16Z | closed |          60 |
+| 2019-10-26T17:41:16Z | closed |         120 |
+| 2019-10-26T17:42:16Z |  open  |          -1 |
+| 2019-10-26T17:43:16Z | closed |           0 |
+| 2019-10-26T17:44:27Z | closed |          60 |
+
+## Count the number of consecutive states
+
+Use the [`stateCount()` function](/{{< latest "flux" >}}/stdlib/universe/statecount/)
+and include the following information:
+
+- **Column to search:** any tag key, tag value, field key, field value, or measurement.
+- **Value:** to search for in the specified column.
+- **State count column:** a new column to store the state count─the number of
+  consecutive records in which the specified value exists.
+
+```js
+|> stateCount(
+    fn: (r) => r.column_to_search == "value_to_search_for",
+    column: "state_count",
+)
+```
+
+- For the first point that evaluates `true`, the state count is set to `1`. For each consecutive point that evaluates `true`, the state count increases by 1.
+- If the state is `false`, the state count is reset to `-1`.
+
+### Example query with stateCount()
+
+The following query searches the `doors` bucket over the past 5 minutes and calculates how many points have `closed` as their `_value`.
+
+```js
+from(bucket: "doors")
+    |> range(start: -5m)
+    |> stateDuration(fn: (r) => r._value == "closed", column: "door_closed")
+```
+
+This example stores the **state count** in the `door_closed` column. If you write data to the `doors` bucket every minute, the state count increases by `1` for each consecutive point where `_value` is `closed`. If `_value` is not `closed`, the state count is reset to `-1`.
+
+#### Query results
+
+Results for the example query above may look like this (for simplicity, we've omitted the measurement, tag, and field columns):
+
+| _time                | _value | door_closed |
+| :------------------- | :----: | ----------: |
+| 2019-10-26T17:39:16Z | closed |           1 |
+| 2019-10-26T17:40:16Z | closed |           2 |
+| 2019-10-26T17:41:16Z | closed |           3 |
+| 2019-10-26T17:42:16Z |  open  |          -1 |
+| 2019-10-26T17:43:16Z | closed |           1 |
+| 2019-10-26T17:44:27Z | closed |           2 |
+
+#### Example query to count machine state
+
+The following query checks the machine state every minute (idle, assigned, or busy). InfluxDB searches the `servers` bucket over the past hour and counts records with a machine state of `idle`, `assigned` or `busy`.
+
+```js
+from(bucket: "servers")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r.machine_state == "idle" or r.machine_state == "assigned" or r.machine_state == "busy")
+    |> stateCount(fn: (r) => r.machine_state == "busy", column: "_count")
+    |> stateCount(fn: (r) => r.machine_state == "assigned", column: "_count")
+    |> stateCount(fn: (r) => r.machine_state == "idle", column: "_count")
+```
+
+<!--## Detect state changes
+
+Detect state changes with the `monitor.stateChanges()` function. To use the `monitor.stateChanges()` function, set up a **check** to query data (stored in the `_monitoring` bucket > `statuses` measurement > `_level` column; see [Monitor data and send alerts](/influxdb/v2.2/monitor-alert/) for more detail.
+
+1. In the InfluxDB user interface, click the **Monitoring and Alerting** icon from the sidebar.
+
+    {{< nav-icon "alerts" >}}
+
+2. If you haven't already, [create a check](/influxdb/v2.2/monitor-alert/checks/create/) that stores statuses (`CRIT`, `WARN`, `INFO`, `OK` or `ANY`) in the `_level` column. <!-- specify how to do this with monitor.check() function or in UI, with check threshold or deadman?
+3. Import the InfluxDB `monitor` package.
+4. In your query, the specify the check. <!--can users specify a Flux query with the `monitoring` bucket and _level field without specifying the check? does importing the monitor package create the `monitoring` bucket?
+5. Use the `monitor.stateChanges()` function and include the following information:
+
+  - `fromLevel` (optional; by default, this is set to `any`)
+  - `toLevel`
+
+### Example query with monitor.stateChanges()
+
+```js
+  import "influxdata/influxdb/monitor"
+
+  `from ${ r._check_name}`
+    monitor.stateChanges(
+    fromLevel: "warn",
+    toLevel: "crit")
+```
+
+<!-- ### Example query results
+
+TBD what query results look like -->
+
+<!--traffic lights
+
+```from(bucket: "doors")
+
+  |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
+  |> filter(fn: (r) => r._measurement == "doors")
+  |> stateCount(fn: (r) => r._field == "door1", column: "_value")
+```
+
+
+   |> stateDuration(fn: (r) => r._cpu == "usage_idle <= 10s", column "stateDuration", unit: 1s)
+  ]]
+  |alert()
+    // Warn after 1 minute
+    .warn(lambda: "state_duration" >= 1)
+    // Critical after 5 minutes
+    .crit(lambda: "state_duration" >= 5)
+```
+
+-->
diff --git a/content/influxdb/v2.2/query-data/flux/moving-average.md b/content/influxdb/v2.2/query-data/flux/moving-average.md
new file mode 100644
index 000000000..6cc6e6de1
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/flux/moving-average.md
@@ -0,0 +1,118 @@
+---
+title: Calculate the moving average
+seotitle: Calculate the moving average in Flux
+list_title: Moving Average
+description: >
+  Use `movingAverage()` or `timedMovingAverage()` to return the moving average of data.
+weight: 210
+menu:
+  influxdb_2_2:
+    parent: Query with Flux
+    name: Moving Average
+influxdb/v2.2/tags: [query, moving average]
+related:
+  - /{{< latest "flux" >}}/stdlib/universe/movingaverage/
+  - /{{< latest "flux" >}}/stdlib/universe/timedmovingaverage/
+list_query_example: moving_average
+---
+
+Use [`movingAverage()`](/{{< latest "flux" >}}/stdlib/universe/movingaverage/)
+or [`timedMovingAverage()`](/{{< latest "flux" >}}/stdlib/universe/timedmovingaverage/)
+to return the moving average of data.
+
+```js
+data
+    |> movingAverage(n: 5)
+
+// OR
+
+data
+    |> timedMovingAverage(every: 5m, period: 10m)
+```
+
+### movingAverage()
+For each row in a table, `movingAverage()` returns the average of the current value and
+**previous** values where `n` is the total number of values used to calculate the average.
+
+If `n = 3`:
+
+| Row # | Calculation                   |
+|:-----:|:-----------                   |
+| 1     | _Insufficient number of rows_ |
+| 2     | _Insufficient number of rows_ |
+| 3     | (Row1 + Row2 + Row3) / 3      |
+| 4     | (Row2 + Row3 + Row4) / 3      |
+| 5     | (Row3 + Row4 + Row5) / 3      |
+
+{{< flex >}}
+{{% flex-content %}}
+**Given the following input:**
+
+| _time                | _value |
+|:-----                | ------:|
+| 2020-01-01T00:01:00Z | 1.0    |
+| 2020-01-01T00:02:00Z | 1.2    |
+| 2020-01-01T00:03:00Z | 1.8    |
+| 2020-01-01T00:04:00Z | 0.9    |
+| 2020-01-01T00:05:00Z | 1.4    |
+| 2020-01-01T00:06:00Z | 2.0    |
+{{% /flex-content %}}
+{{% flex-content %}}
+**The following would return:**
+
+```js
+|> movingAverage(n: 3)
+```  
+
+| _time                | _value |
+|:-----                | ------:|
+| 2020-01-01T00:03:00Z | 1.33   |
+| 2020-01-01T00:04:00Z | 1.30   |
+| 2020-01-01T00:05:00Z | 1.36   |
+| 2020-01-01T00:06:00Z | 1.43   |
+{{% /flex-content %}}
+{{< /flex >}}
+
+### timedMovingAverage()
+For each row in a table, `timedMovingAverage()` returns the average of the
+current value and all row values in the **previous** `period` (duration).
+It returns moving averages at a frequency defined by the `every` parameter.
+
+Each color in the diagram below represents a period of time used to calculate an
+average and the time a point representing the average is returned.
+If `every = 30m` and `period = 1h`:
+
+{{< svg "/static/svgs/timed-moving-avg.svg" >}}
+
+{{< flex >}}
+{{% flex-content %}}
+**Given the following input:**
+
+| _time                | _value |
+|:-----                | ------:|
+| 2020-01-01T00:00:00Z | 1.0    |
+| 2020-01-01T00:30:00Z | 1.2    |
+| 2020-01-01T01:00:00Z | 1.8    |
+| 2020-01-01T01:30:00Z | 0.9    |
+| 2020-01-01T02:00:00Z | 1.4    |
+| 2020-01-01T02:30:00Z | 2.0    |  
+| 2020-01-01T03:00:00Z | 1.9    |  
+{{% /flex-content %}}
+{{% flex-content %}}
+**The following would return:**
+
+```js
+|> timedMovingAverage(every: 30m, period: 1h)
+```  
+
+| _time                | _value |
+| :------------------- | -----: |
+| 2020-01-01T00:30:00Z |    1.0 |
+| 2020-01-01T01:00:00Z |    1.1 |
+| 2020-01-01T01:30:00Z |    1.5 |
+| 2020-01-01T02:00:00Z |   1.35 |
+| 2020-01-01T02:30:00Z |   1.15 |
+| 2020-01-01T03:00:00Z |    1.7 |
+| 2020-01-01T03:00:00Z |      2 |
+{{% /flex-content %}}
+{{< /flex >}}
diff --git a/content/influxdb/v2.2/query-data/flux/percentile-quantile.md b/content/influxdb/v2.2/query-data/flux/percentile-quantile.md
new file mode 100644
index 000000000..d4fb6053e
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/flux/percentile-quantile.md
@@ -0,0 +1,164 @@
+---
+title: Find percentile and quantile values
+seotitle: Query percentile and quantile values in Flux
+list_title: Percentile & quantile
+description: >
+  Use the `quantile()` function to return all values within the `q` quantile or
+  percentile of input data.
+weight: 210
+menu:
+  influxdb_2_2:
+    parent: Query with Flux
+    name: Percentile & quantile
+influxdb/v2.2/tags: [query, percentile, quantile]
+related:
+  - /influxdb/v2.2/query-data/flux/query-median/
+  - /{{< latest "flux" >}}/stdlib/universe/quantile/
+list_query_example: quantile
+---
+
+Use the [`quantile()` function](/{{< latest "flux" >}}/stdlib/universe/quantile/)
+to return a value representing the `q` quantile or percentile of input data.
+
+## Percentile versus quantile
+Percentiles and quantiles are very similar, differing only in the number used to calculate return values.
+A percentile is calculated using numbers between `0` and `100`.
+A quantile is calculated using numbers between `0.0` and `1.0`.
+For example, the **`0.5` quantile** is the same as the **50th percentile**.
+
+## Select a method for calculating the quantile
+Select one of the following methods to calculate the quantile:
+
+- [estimate_tdigest](#estimate_tdigest)
+- [exact_mean](#exact_mean)
+- [exact_selector](#exact_selector)
+
+### estimate_tdigest
+**(Default)** An aggregate method that uses a [t-digest data structure](https://github.com/tdunning/t-digest)
+to compute a quantile estimate on large data sources.
+Output tables consist of a single row containing the calculated quantile.
+
+If calculating the `0.5` quantile or 50th percentile:
+
+{{< flex >}}
+{{% flex-content %}}
+**Given the following input table:**
+
+| _time                | _value |
+|:-----                | ------:|
+| 2020-01-01T00:01:00Z | 1.0    |
+| 2020-01-01T00:02:00Z | 1.0    |
+| 2020-01-01T00:03:00Z | 2.0    |
+| 2020-01-01T00:04:00Z | 3.0    |
+{{% /flex-content %}}
+{{% flex-content %}}
+**`estimate_tdigest` returns:**
+
+| _value |
+|:------:|
+| 1.5    |
+{{% /flex-content %}}
+{{< /flex >}}
+
+### exact_mean
+An aggregate method that takes the average of the two points closest to the quantile value.
+Output tables consist of a single row containing the calculated quantile.
+
+If calculating the `0.5` quantile or 50th percentile:
+
+{{< flex >}}
+{{% flex-content %}}
+**Given the following input table:**
+
+| _time                | _value |
+|:-----                | ------:|
+| 2020-01-01T00:01:00Z | 1.0    |
+| 2020-01-01T00:02:00Z | 1.0    |
+| 2020-01-01T00:03:00Z | 2.0    |
+| 2020-01-01T00:04:00Z | 3.0    |
+{{% /flex-content %}}
+{{% flex-content %}}
+**`exact_mean` returns:**
+
+| _value |
+|:------:|
+| 1.5    |
+{{% /flex-content %}}
+{{< /flex >}}
+
+### exact_selector
+A selector method that returns the data point for which at least `q` points are less than.
+Output tables consist of a single row containing the calculated quantile.
+
+If calculating the `0.5` quantile or 50th percentile:
+
+{{< flex >}}
+{{% flex-content %}}
+**Given the following input table:**
+
+| _time                | _value |
+|:-----                | ------:|
+| 2020-01-01T00:01:00Z | 1.0    |
+| 2020-01-01T00:02:00Z | 1.0    |
+| 2020-01-01T00:03:00Z | 2.0    |
+| 2020-01-01T00:04:00Z | 3.0    |
+{{% /flex-content %}}
+{{% flex-content %}}
+**`exact_selector` returns:**
+
+| _time                | _value |
+|:-----                | ------:|
+| 2020-01-01T00:02:00Z | 1.0    |
+{{% /flex-content %}}
+{{< /flex >}}
+
+{{% note %}}
+The examples below use the [example data variable](/influxdb/v2.2/query-data/flux/#example-data-variable).
+{{% /note %}}
+
+## Find the value representing the 99th percentile
+Use the default method, `"estimate_tdigest"`, to return all rows in a table that
+contain values in the 99th percentile of data in the table.
+
+```js
+data
+    |> quantile(q: 0.99)
+```
+
+## Find the average of values closest to the quantile
+Use the `exact_mean` method to return a single row per input table containing the
+average of the two values closest to the mathematical quantile of data in the table.
+For example, to calculate the `0.99` quantile:
+
+```js
+data
+    |> quantile(q: 0.99, method: "exact_mean")
+```
+
+## Find the point with the quantile value
+Use the `exact_selector` method to return a single row per input table containing the
+value that `q * 100`% of values in the table are less than.
+For example, to calculate the `0.99` quantile:
+
+```js
+data
+    |> quantile(q: 0.99, method: "exact_selector")
+```
+
+## Use quantile() with aggregateWindow()
+[`aggregateWindow()`](/{{< latest "flux" >}}/stdlib/universe/aggregatewindow/)
+segments data into windows of time, aggregates data in each window into a single
+point, and then removes the time-based segmentation.
+It is primarily used to [downsample data](/influxdb/v2.2/process-data/common-tasks/downsample-data/).
+
+To specify the [quantile calculation method](#select-a-method-for-calculating-the-quantile) in
+`aggregateWindow()`, use the [full function syntax](/{{< latest "flux" >}}/stdlib/universe/aggregatewindow/#specify-parameters-of-the-aggregate-function):
+
+```js
+data
+    |> aggregateWindow(
+        every: 5m,
+        fn: (tables=<-, column) => tables
+            |> quantile(q: 0.99, method: "exact_selector"),
+    )
+```
diff --git a/content/influxdb/v2.2/query-data/flux/query-fields.md b/content/influxdb/v2.2/query-data/flux/query-fields.md
new file mode 100644
index 000000000..90b7d6f91
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/flux/query-fields.md
@@ -0,0 +1,76 @@
+---
+title: Query fields and tags
+seotitle: Query fields and tags in InfluxDB using Flux
+description: >
+    Use `filter()` to query data based on fields, tags, or any other column value.
+    `filter()` performs operations similar to the `SELECT` statement and the `WHERE`
+    clause in InfluxQL and other SQL-like query languages.
+weight: 201
+menu:
+  influxdb_2_2:
+    parent: Query with Flux
+influxdb/v2.2/tags: [query, select, where]
+related:
+  - /{{< latest "flux" >}}/stdlib/universe/filter/
+  - /influxdb/v2.2/query-data/flux/conditional-logic/
+  - /influxdb/v2.2/query-data/flux/regular-expressions/
+list_code_example: |
+  ```js
+  from(bucket: "example-bucket")
+      |> range(start: -1h)
+      |> filter(fn: (r) => r._measurement == "example-measurement" and r.tag == "example-tag")
+      |> filter(fn: (r) => r._field == "example-field")
+  ```
+---
+
+Use [`filter()`](/{{< latest "flux" >}}/stdlib/universe/filter/)
+to query data based on fields, tags, or any other column value.
+`filter()` performs operations similar to the `SELECT` statement and the `WHERE`
+clause in InfluxQL and other SQL-like query languages.
+
+## The filter() function
+`filter()` has an `fn` parameter that expects a [predicate function](/influxdb/v2.2/reference/glossary/#predicate-function),
+an anonymous function comprised of one or more [predicate expressions](/influxdb/v2.2/reference/glossary/#predicate-expression).
+The predicate function evaluates each input row.
+Rows that evaluate to `true` are **included** in the output data.
+Rows that evaluate to `false` are **excluded** from the output data.
+
+```js
+// ...
+    |> filter(fn: (r) => r._measurement == "example-measurement" )
+```
+
+The `fn` predicate function requires an `r` argument, which represents each row
+as `filter()` iterates over input data.
+Key-value pairs in the row record represent columns and their values.
+Use [dot notation or bracket notation](/{{< latest "flux" >}}/data-types/composite/record/#reference-values-in-a-record) 
+to reference specific column values in the predicate function.
+Use [logical operators](/{{< latest "flux" >}}/spec/operators/#logical-operators)
+to chain multiple predicate expressions together.
+
+```js
+// Row record
+r = {foo: "bar", baz: "quz"}
+
+// Example predicate function
+(r) => r.foo == "bar" and r["baz"] == "quz"
+
+// Evaluation results
+(r) => true and true
+```
+
+## Filter by fields and tags
+The combination of [`from()`](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/from),
+[`range()`](/{{< latest "flux" >}}/stdlib/universe/range),
+and `filter()` represent the most basic Flux query:
+
+1. Use `from()` to define your [bucket](/influxdb/v2.2/reference/glossary/#bucket).
+2. Use `range()` to limit query results by time.
+3. Use `filter()` to identify what rows of data to output.
+
+```js
+from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "example-measurement" and r.tag == "example-tag")
+    |> filter(fn: (r) => r._field == "example-field")
+```
diff --git a/content/influxdb/v2.2/query-data/flux/rate.md b/content/influxdb/v2.2/query-data/flux/rate.md
new file mode 100644
index 000000000..040f04b79
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/flux/rate.md
@@ -0,0 +1,173 @@
+---
+title: Calculate the rate of change
+seotitle: Calculate the rate of change in Flux
+list_title: Rate
+description: >
+  Use `derivative()` to calculate the rate of change between subsequent values or
+  `aggregate.rate()` to calculate the average rate of change per window of time.
+  If time between points varies, these functions normalize points to a common time interval
+  making values easily comparable.
+weight: 210
+menu:
+  influxdb_2_2:
+    parent: Query with Flux
+    name: Rate
+influxdb/v2.2/tags: [query, rate]
+related:
+  - /{{< latest "flux" >}}/stdlib/universe/derivative/
+  - /{{< latest "flux" >}}/stdlib/experimental/aggregate/rate/
+list_query_example: rate_of_change
+---
+
+
+Use [`derivative()`](/{{< latest "flux" >}}/stdlib/universe/derivative/)
+to calculate the rate of change between subsequent values or
+[`aggregate.rate()`](/{{< latest "flux" >}}/stdlib/experimental/to/aggregate/rate/)
+to calculate the average rate of change per window of time.
+If time between points varies, these functions normalize points to a common time interval
+making values easily comparable.
+
+- [Rate of change between subsequent values](#rate-of-change-between-subsequent-values)
+- [Average rate of change per window of time](#average-rate-of-change-per-window-of-time)
+
+## Rate of change between subsequent values
+Use the [`derivative()` function](/{{< latest "flux" >}}/stdlib/universe/derivative/)
+to calculate the rate of change per unit of time between subsequent _non-null_ values.
+
+```js
+data
+    |> derivative(unit: 1s)
+```
+
+By default, `derivative()` returns only positive derivative values and replaces negative values with _null_.
+Calculated values are returned as [floats](/{{< latest "flux" >}}/spec/types/#numeric-types).
+
+{{< flex >}}
+{{% flex-content %}}
+**Given the following input:**
+
+| _time                | _value |
+|:-----                | ------:|
+| 2020-01-01T00:00:00Z | 250    |
+| 2020-01-01T00:04:00Z | 160    |
+| 2020-01-01T00:12:00Z | 150    |
+| 2020-01-01T00:19:00Z | 220    |
+| 2020-01-01T00:32:00Z | 200    |
+| 2020-01-01T00:51:00Z | 290    |
+| 2020-01-01T01:00:00Z | 340    |
+{{% /flex-content %}}
+{{% flex-content %}}
+**`derivative(unit: 1m)` returns:**
+
+| _time                | _value |
+|:-----                | ------:|
+| 2020-01-01T00:04:00Z |        |
+| 2020-01-01T00:12:00Z |        |
+| 2020-01-01T00:19:00Z | 10.0   |
+| 2020-01-01T00:32:00Z |        |
+| 2020-01-01T00:51:00Z | 4.74   |
+| 2020-01-01T01:00:00Z | 5.56   |
+{{% /flex-content %}}
+{{< /flex >}}
+
+Results represent the rate of change **per minute** between subsequent values with
+negative values set to _null_.
+
+### Return negative derivative values
+To return negative derivative values, set the `nonNegative` parameter to `false`,
+
+{{< flex >}}
+{{% flex-content %}}
+**Given the following input:**
+
+| _time                | _value |
+|:-----                | ------:|
+| 2020-01-01T00:00:00Z | 250    |
+| 2020-01-01T00:04:00Z | 160    |
+| 2020-01-01T00:12:00Z | 150    |
+| 2020-01-01T00:19:00Z | 220    |
+| 2020-01-01T00:32:00Z | 200    |
+| 2020-01-01T00:51:00Z | 290    |
+| 2020-01-01T01:00:00Z | 340    |
+{{% /flex-content %}}
+{{% flex-content %}}
+**The following returns:**
+
+```js
+|> derivative(unit: 1m, nonNegative: false)
+```
+
+| _time                | _value |
+|:-----                | ------:|
+| 2020-01-01T00:04:00Z | -22.5  |
+| 2020-01-01T00:12:00Z | -1.25  |
+| 2020-01-01T00:19:00Z | 10.0   |
+| 2020-01-01T00:32:00Z | -1.54  |
+| 2020-01-01T00:51:00Z | 4.74   |
+| 2020-01-01T01:00:00Z | 5.56   |
+{{% /flex-content %}}
+{{< /flex >}}
+
+Results represent the rate of change **per minute** between subsequent values and
+include negative values.
+
+## Average rate of change per window of time
+
+Use the [`aggregate.rate()` function](/{{< latest "flux" >}}/stdlib/experimental/to/aggregate/rate/)
+to calculate the average rate of change per window of time.
+
+```js
+import "experimental/aggregate"
+
+data
+    |> aggregate.rate(
+        every: 1m,
+        unit: 1s,
+        groupColumns: ["tag1", "tag2"],
+    )
+```
+
+`aggregate.rate()` returns the average rate of change (as a [float](/{{< latest "flux" >}}/spec/types/#numeric-types))
+per `unit` for time intervals defined by `every`.
+Negative values are replaced with _null_.
+
+{{% note %}}
+`aggregate.rate()` does not support `nonNegative: false`.
+{{% /note %}}
+
+{{< flex >}}
+{{% flex-content %}}
+**Given the following input:**
+
+| _time                | _value |
+|:-----                | ------:|
+| 2020-01-01T00:00:00Z | 250    |
+| 2020-01-01T00:04:00Z | 160    |
+| 2020-01-01T00:12:00Z | 150    |
+| 2020-01-01T00:19:00Z | 220    |
+| 2020-01-01T00:32:00Z | 200    |
+| 2020-01-01T00:51:00Z | 290    |
+| 2020-01-01T01:00:00Z | 340    |
+{{% /flex-content %}}
+{{% flex-content %}}
+**The following returns:**
+
+```js
+|> aggregate.rate(
+    every: 20m,
+    unit: 1m,
+)
+```
+
+| _time                | _value |
+|:-----                | ------:|
+| 2020-01-01T00:20:00Z | 10.00  |
+| 2020-01-01T00:40:00Z |        |
+| 2020-01-01T01:00:00Z | 4.74   |
+| 2020-01-01T01:20:00Z | 5.56   |
+{{% /flex-content %}}
+{{< /flex >}}
+
+Results represent the **average change rate per minute** of every **20 minute interval**
+with negative values set to _null_.
+Timestamps represent the right bound of the time window used to average values.
diff --git a/content/influxdb/v2.2/query-data/flux/regular-expressions.md b/content/influxdb/v2.2/query-data/flux/regular-expressions.md
new file mode 100644
index 000000000..b14097bf4
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/flux/regular-expressions.md
@@ -0,0 +1,90 @@
+---
+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.2/tags: [regex]
+menu:
+  influxdb_2_2:
+    name: Regular expressions
+    parent: Query with Flux
+weight: 220
+aliases:
+  - /influxdb/v2.2/query-data/guides/regular-expressions/
+related:
+  - /influxdb/v2.2/query-data/flux/query-fields/
+  - /{{< latest "flux" >}}/stdlib/regexp/
+list_query_example: regular_expressions
+---
+
+Regular expressions (regexes) are incredibly powerful when matching patterns in large collections of data.
+With Flux, regular expressions are primarily used for evaluation logic in predicate functions for things
+such as filtering rows, dropping and keeping columns, state detection, etc.
+This guide shows how to use regular expressions in your Flux scripts.
+
+If you're just getting started with Flux queries, check out the following:
+
+- [Get started with Flux](/{{< latest "flux" >}}/get-started/) for a conceptual overview of Flux and parts of a Flux query.
+- [Execute queries](/influxdb/v2.2/query-data/execute-queries/) to discover a variety of ways to run your queries.
+
+## Go regular expression syntax
+Flux uses Go's [regexp package](https://golang.org/pkg/regexp/) for regular expression search.
+The links [below](#helpful-links) provide information about Go's regular expression syntax.
+
+## Regular expression operators
+Flux provides two comparison operators for use with regular expressions.
+
+#### `=~`
+When the expression on the left **MATCHES** the regular expression on the right, this evaluates to `true`.
+
+#### `!~`
+When the expression on the left **DOES NOT MATCH** the regular expression on the right, this evaluates to `true`.
+
+## Regular expressions in Flux
+When using regex matching in your Flux scripts, enclose your regular expressions with `/`.
+The following is the basic regex comparison syntax:
+
+###### Basic regex comparison syntax
+```js
+expression =~ /regex/
+expression !~ /regex/
+```
+## Examples
+
+### Use a regex to filter by tag value
+The following example filters records by the `cpu` tag.
+It only keeps records for which the `cpu` is either `cpu0`, `cpu1`, or `cpu2`.
+
+```js
+from(bucket: "example-bucket")
+    |> range(start: -15m)
+    |> filter(fn: (r) => r._measurement == "cpu" and r.cpu =~ /cpu[0-2]$/)
+```
+
+### Use a regex to filter by field key
+The following example excludes records that do not have `_percent` in a field key.
+
+```js
+from(bucket: "example-bucket")
+    |> range(start: -15m)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field =~ /_percent/)
+```
+
+### Drop columns matching a regex
+The following example drops columns whose names do not being with `_`.
+
+```js
+from(bucket: "example-bucket")
+    |> range(start: -15m)
+    |> filter(fn: (r) => r._measurement == "mem")
+    |> drop(fn: (column) => column !~ /_.*/)
+```
+
+## Helpful links
+
+##### Syntax documentation
+[regexp Syntax GoDoc](https://godoc.org/regexp/syntax)  
+[RE2 Syntax Overview](https://github.com/google/re2/wiki/Syntax)
+
+##### Go regex testers
+[Regex Tester - Golang](https://regex-golang.appspot.com/assets/html/index.html)  
+[Regex101](https://regex101.com/)
diff --git a/content/influxdb/v2.2/query-data/flux/scalar-values.md b/content/influxdb/v2.2/query-data/flux/scalar-values.md
new file mode 100644
index 000000000..0dc5b2600
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/flux/scalar-values.md
@@ -0,0 +1,232 @@
+---
+title: Extract scalar values in Flux
+list_title: Extract scalar values
+description: >
+  Use Flux dynamic query functions to extract scalar values from Flux query output.
+  This lets you, for example, dynamically set variables using query results.
+menu:
+  influxdb_2_2:
+    name: Extract scalar values
+    parent:  Query with Flux
+weight: 220
+influxdb/v2.2/tags: [scalar]
+related:
+  - /{{< latest "flux" >}}/function-types/#dynamic-queries, Flux dynamic query functions
+aliases:
+  - /influxdb/v2.2/query-data/guides/scalar-values/
+list_code_example: |
+  ```js
+  scalarValue = (tables=<-) => {
+      _record = tables
+          |> findRecord(fn: (key) => true, idx: 0)
+
+      return _record._value
+  }
+  ```
+---
+
+Use Flux [dynamic query functions](/{{< latest "flux" >}}/function-types/#dynamic-queries)
+to extract scalar values from Flux query output.
+This lets you, for example, dynamically set variables using query results.
+
+**To extract scalar values from output:**
+
+1. [Extract a column from the input stream](#extract-a-column)
+   _**or**_ [extract a row from the input stream](#extract-a-row).
+2. Use the returned array or record to reference scalar values.
+
+_The samples on this page use the [sample data provided below](#sample-data)._
+
+{{% warn %}}
+#### Current limitations
+- The InfluxDB user interface (UI) does not currently support raw scalar output.
+  Use [`map()`](/{{< latest "flux" >}}/stdlib/universe/map/) to add
+  scalar values to output data.
+{{% /warn %}}
+
+## Table extraction
+Flux formats query results as a stream of tables.
+Both [`findColumn()`](/{{< latest "flux" >}}/stdlib/universe/findcolumn/)
+and [`findRecord()`](/{{< latest "flux" >}}/stdlib/universe/findrecord/)
+extract the first table in a stream of tables whose [group key](/{{< latest "flux" >}}/get-started/data-model/#group-key)
+values match the `fn` [predicate function](/{{< latest "flux" >}}/get-started/syntax-basics/#predicate-functions).
+
+{{% note %}}
+#### Extract the correct table
+Flux functions do not guarantee table order.
+`findColumn()` and `findRecord` extract only the **first** table that matches the `fn` predicate.
+To extract the correct table, be very specific in your predicate function or
+filter and transform your data to minimize the number of tables piped-forward into the functions.
+{{% /note %}}
+
+## Extract a column
+Use the [`findColumn()` function](/{{< latest "flux" >}}/stdlib/universe/findcolumn/)
+to output an array of values from a specific column in the extracted table.
+
+_See [Sample data](#sample-data) below._
+
+```js
+sampleData
+    |> findColumn(
+        fn: (key) => key._field == "temp" and key.location == "sfo",
+        column: "_value",
+    )
+
+// Returns [65.1, 66.2, 66.3, 66.8]
+```
+
+### Use extracted column values
+Use a variable to store the array of values.
+In the example below, `SFOTemps` represents the array of values.
+Reference a specific index (integer starting from `0`) in the array to return the
+value at that index.
+
+_See [Sample data](#sample-data) below._
+
+```js
+SFOTemps = sampleData
+    |> findColumn(
+        fn: (key) => key._field == "temp" and key.location == "sfo",
+        column: "_value",
+    )
+
+SFOTemps
+// Returns [65.1, 66.2, 66.3, 66.8]
+
+SFOTemps[0]
+// Returns 65.1
+
+SFOTemps[2]
+// Returns 66.3
+```
+
+## Extract a row
+Use the [`findRecord()` function](/{{< latest "flux" >}}/stdlib/universe/findrecord/)
+to output data from a single row in the extracted table.
+Specify the index of the row to output using the `idx` parameter.
+The function outputs a record with key-value pairs for each column.
+
+```js
+sampleData
+    |> findRecord(
+        fn: (key) => key._field == "temp" and key.location == "sfo",
+        idx: 0,
+    )
+
+// Returns {
+//   _time:2019-11-11T12:00:00Z,
+//   _field:"temp",
+//   location:"sfo",
+//   _value: 65.1
+// }
+```
+
+### Use an extracted row record
+Use a variable to store the extracted row record.
+In the example below, `tempInfo` represents the extracted row.
+Use [dot or bracket notation](/{{< latest "flux" >}}/data-types/composite/record/#dot-notation)
+to reference keys in the record.
+
+```js
+tempInfo = sampleData
+    |> findRecord(
+        fn: (key) => key._field == "temp" and key.location == "sfo",
+        idx: 0,
+    )
+
+tempInfo
+// Returns {
+//   _time:2019-11-11T12:00:00Z,
+//   _field:"temp",
+//   location:"sfo",
+//   _value: 65.1
+// }
+
+tempInfo._time
+// Returns 2019-11-11T12:00:00Z
+
+tempInfo.location
+// Returns sfo
+```
+
+## Example helper functions
+Create custom helper functions to extract scalar values from query output.
+
+##### Extract a scalar field value
+```js
+// Define a helper function to extract field values
+getFieldValue = (tables=<-, field) => {
+    extract = tables
+        |> findColumn(fn: (key) => key._field == field, column: "_value")
+
+    return extract[0]
+}
+
+// Use the helper function to define a variable
+lastJFKTemp = sampleData
+    |> filter(fn: (r) => r.location == "kjfk")
+    |> last()
+    |> getFieldValue(field: "temp")
+
+lastJFKTemp
+// Returns 71.2
+```
+
+##### Extract scalar row data
+```js
+// Define a helper function to extract a row as a record
+getRow = (tables=<-, field, idx=0) => {
+    extract = tables
+        |> findRecord(fn: (key) => true, idx: idx)
+
+    return extract
+}
+
+// Use the helper function to define a variable
+lastReported = sampleData
+    |> last()
+    |> getRow(field: "temp")
+
+"The last location to report was ${lastReported.location}.
+The temperature was ${string(v: lastReported._value)}°F."
+
+// Returns:
+// The last location to report was kord.
+// The temperature was 38.9°F.
+```
+
+---
+
+## Sample data
+
+The following sample data set represents fictional temperature metrics collected
+from three locations.
+It's formatted in [annotated CSV](/influxdb/v2.2/reference/syntax/annotated-csv/) and imported
+into the Flux query using the [`csv.from()` function](/{{< latest "flux" >}}/stdlib/csv/from/).
+
+Place the following at the beginning of your query to use the sample data:
+
+{{% truncate %}}
+```js
+import "csv"
+
+sampleData = csv.from(csv: "
+#datatype,string,long,dateTime:RFC3339,string,string,double
+#group,false,true,false,true,true,false
+#default,,,,,,
+,result,table,_time,location,_field,_value
+,,0,2019-11-01T12:00:00Z,sfo,temp,65.1
+,,0,2019-11-01T13:00:00Z,sfo,temp,66.2
+,,0,2019-11-01T14:00:00Z,sfo,temp,66.3
+,,0,2019-11-01T15:00:00Z,sfo,temp,66.8
+,,1,2019-11-01T12:00:00Z,kjfk,temp,69.4
+,,1,2019-11-01T13:00:00Z,kjfk,temp,69.9
+,,1,2019-11-01T14:00:00Z,kjfk,temp,71.0
+,,1,2019-11-01T15:00:00Z,kjfk,temp,71.2
+,,2,2019-11-01T12:00:00Z,kord,temp,46.4
+,,2,2019-11-01T13:00:00Z,kord,temp,46.3
+,,2,2019-11-01T14:00:00Z,kord,temp,42.7
+,,2,2019-11-01T15:00:00Z,kord,temp,38.9
+")
+```
+{{% /truncate %}}
diff --git a/content/influxdb/v2.2/query-data/flux/sort-limit.md b/content/influxdb/v2.2/query-data/flux/sort-limit.md
new file mode 100644
index 000000000..a536ef6f8
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/flux/sort-limit.md
@@ -0,0 +1,68 @@
+---
+title: Sort and limit data with Flux
+seotitle: Sort and limit data in InfluxDB with Flux
+list_title: Sort and limit
+description: >
+  Use `sort()` to order records within each table by specific columns and
+  `limit()` to limit the number of records in output tables to a fixed number, `n`.
+influxdb/v2.2/tags: [sort, limit]
+menu:
+  influxdb_2_2:
+    name: Sort and limit
+    parent: Query with Flux
+weight: 203
+aliases:
+  - /influxdb/v2.2/query-data/guides/sort-limit/
+related:
+  - /{{< latest "flux" >}}/stdlib/universe/sort
+  - /{{< latest "flux" >}}/stdlib/universe/limit
+list_query_example: sort_limit
+---
+
+Use [`sort()`](/{{< latest "flux" >}}/stdlib/universe/sort)
+to order records within each table by specific columns and
+[`limit()`](/{{< latest "flux" >}}/stdlib/universe/limit)
+to limit the number of records in output tables to a fixed number, `n`.
+
+If you're just getting started with Flux queries, check out the following:
+
+- [Get started with Flux](/{{< latest "flux" >}}/get-started/) for a conceptual overview of Flux and parts of a Flux query.
+- [Execute queries](/influxdb/v2.2/query-data/execute-queries/) to discover a variety of ways to run your queries.
+
+##### Example sorting system uptime
+
+The following example orders system uptime first by region, then host, then value.
+
+```js
+from(bucket: "example-bucket")
+    |> range(start: -12h)
+    |> filter(fn: (r) => r._measurement == "system" and r._field == "uptime")
+    |> sort(columns: ["region", "host", "_value"])
+```
+
+The [`limit()` function](/{{< latest "flux" >}}/stdlib/universe/limit)
+limits the number of records in output tables to a fixed number, `n`.
+The following example shows up to 10 records from the past hour.
+
+```js
+from(bucket:"example-bucket")
+    |> range(start:-1h)
+    |> limit(n:10)
+```
+
+You can use `sort()` and `limit()` together to show the top N records.
+The example below returns the 10 top system uptime values sorted first by
+region, then host, then value.
+
+```js
+from(bucket: "example-bucket")
+    |> range(start: -12h)
+    |> filter(fn: (r) => r._measurement == "system" and r._field == "uptime")
+    |> sort(columns: ["region", "host", "_value"])
+    |> limit(n: 10)
+```
+
+You now have created a Flux query that sorts and limits data.
+Flux also provides the [`top()`](/{{< latest "flux" >}}/stdlib/universe/top)
+and [`bottom()`](/{{< latest "flux" >}}/stdlib/universe/bottom)
+functions to perform both of these functions at the same time.
diff --git a/content/influxdb/v2.2/query-data/flux/sql.md b/content/influxdb/v2.2/query-data/flux/sql.md
new file mode 100644
index 000000000..f5b03d82b
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/flux/sql.md
@@ -0,0 +1,378 @@
+---
+title: Query SQL data sources
+seotitle: Query SQL data sources with InfluxDB
+list_title: Query SQL data
+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, Amazon Athena, and Google BigQuery.
+influxdb/v2.2/tags: [query, flux, sql]
+menu:
+  influxdb_2_2:
+    parent: Query with Flux
+    list_title: SQL data
+weight: 220
+aliases:
+  - /influxdb/v2.2/query-data/guides/sql/
+related:
+  - /{{< latest "flux" >}}/stdlib/sql/
+list_code_example: |
+  ```js
+  import "sql"
+
+  sql.from(
+      driverName: "postgres",
+      dataSourceName: "postgresql://user:password@localhost",
+      query: "SELECT * FROM example_table",
+  )
+  ```
+---
+
+The [Flux](/influxdb/v2.2/reference/flux) `sql` package provides functions for working with SQL data sources.
+[`sql.from()`](/{{< latest "flux" >}}/stdlib/sql/from/) lets you query SQL data sources
+like [PostgreSQL](https://www.postgresql.org/), [MySQL](https://www.mysql.com/),
+[Snowflake](https://www.snowflake.com/), [SQLite](https://www.sqlite.org/index.html),
+[Microsoft SQL Server](https://www.microsoft.com/en-us/sql-server/default.aspx),
+[Amazon Athena](https://aws.amazon.com/athena/) and [Google BigQuery](https://cloud.google.com/bigquery)
+and use the results with InfluxDB dashboards, tasks, and other operations.
+
+- [Query a SQL data source](#query-a-sql-data-source)
+- [Join SQL data with data in InfluxDB](#join-sql-data-with-data-in-influxdb)
+- [Use SQL results to populate dashboard variables](#use-sql-results-to-populate-dashboard-variables)
+- [Use secrets to store SQL database credentials](#use-secrets-to-store-sql-database-credentials)
+- [Sample sensor data](#sample-sensor-data)
+
+If you're just getting started with Flux queries, check out the following:
+
+- [Get started with Flux](/{{< latest "flux" >}}/get-started/) for a conceptual overview of Flux and parts of a Flux query.
+- [Execute queries](/influxdb/v2.2/query-data/execute-queries/) to discover a variety of ways to run your queries.
+
+## Query a SQL data source
+To query a SQL data source:
+
+1. Import the `sql` package in your Flux query
+2. Use the `sql.from()` function to specify the driver, data source name (DSN),
+   and query used to query data from your SQL data source:
+
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[PostgreSQL](#)
+[MySQL](#)
+[Snowflake](#)
+[SQLite](#)
+[SQL Server](#)
+[Athena](#)
+[BigQuery](#)
+{{% /code-tabs %}}
+
+{{% code-tab-content %}}
+```js
+import "sql"
+
+sql.from(
+    driverName: "postgres",
+    dataSourceName: "postgresql://user:password@localhost",
+    query: "SELECT * FROM example_table",
+)
+```
+{{% /code-tab-content %}}
+
+{{% code-tab-content %}}
+```js
+import "sql"
+
+sql.from(
+    driverName: "mysql",
+    dataSourceName: "user:password@tcp(localhost:3306)/db",
+    query: "SELECT * FROM example_table",
+)
+```
+{{% /code-tab-content %}}
+
+{{% code-tab-content %}}
+```js
+import "sql"
+
+sql.from(
+    driverName: "snowflake",
+    dataSourceName: "user:password@account/db/exampleschema?warehouse=wh",
+    query: "SELECT * FROM example_table",
+)
+```
+{{% /code-tab-content %}}
+
+{{% code-tab-content %}}
+```js
+// NOTE: InfluxDB OSS and InfluxDB Cloud do not have access to
+// the local filesystem and cannot query SQLite data sources.
+// Use the Flux REPL to query an SQLite data source.
+
+import "sql"
+
+sql.from(
+    driverName: "sqlite3",
+    dataSourceName: "file:/path/to/test.db?cache=shared&mode=ro",
+    query: "SELECT * FROM example_table",
+)
+```
+{{% /code-tab-content %}}
+
+{{% code-tab-content %}}
+```js
+import "sql"
+
+sql.from(
+    driverName: "sqlserver",
+    dataSourceName: "sqlserver://user:password@localhost:1234?database=examplebdb",
+    query: "GO SELECT * FROM Example.Table",
+)
+```
+
+_For information about authenticating with SQL Server using ADO-style parameters,
+see [SQL Server ADO authentication](/{{< latest "flux" >}}/stdlib/sql/from/#sql-server-ado-authentication)._
+{{% /code-tab-content %}}
+
+{{% code-tab-content %}}
+```js
+import "sql"
+sql.from(
+    driverName: "awsathena",
+    dataSourceName: "s3://myorgqueryresults/?accessID=12ab34cd56ef&region=region-name&secretAccessKey=y0urSup3rs3crEtT0k3n",
+    query: "GO SELECT * FROM Example.Table",
+)
+```
+
+_For information about parameters to include in the Athena DSN,
+see [Athena connection string](/{{< latest "flux" >}}/stdlib/sql/from/#athena-connection-string)._
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```js
+import "sql"
+sql.from(
+    driverName: "bigquery",
+    dataSourceName: "bigquery://projectid/?apiKey=mySuP3r5ecR3tAP1K3y",
+    query: "SELECT * FROM exampleTable",
+)
+```
+
+_For information about authenticating with BigQuery, see
+[BigQuery authentication parameters](/{{< latest "flux" >}}/stdlib/sql/from/#bigquery-authentication-parameters)._
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+_See the [`sql.from()` documentation](/{{< latest "flux" >}}/stdlib/sql/from/) for
+information about required function parameters._
+
+## Join SQL data with data in InfluxDB
+One of the primary benefits of querying SQL data sources from InfluxDB
+is the ability to enrich query results with data stored outside of InfluxDB.
+
+Using the [air sensor sample data](#sample-sensor-data) below, the following query
+joins air sensor metrics stored in InfluxDB with sensor information stored in PostgreSQL.
+The joined data lets you query and filter results based on sensor information
+that isn't stored in InfluxDB.
+
+```js
+// Import the "sql" package
+import "sql"
+
+// Query data from PostgreSQL
+sensorInfo = sql.from(
+    driverName: "postgres",
+    dataSourceName: "postgresql://localhost?sslmode=disable",
+    query: "SELECT * FROM sensors",
+)
+
+// Query data from InfluxDB
+sensorMetrics = from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "airSensors")
+
+// Join InfluxDB query results with PostgreSQL query results
+join(tables: {metric: sensorMetrics, info: sensorInfo}, on: ["sensor_id"])
+```
+
+## Use SQL results to populate dashboard variables
+Use `sql.from()` to [create dashboard variables](/influxdb/v2.2/visualize-data/variables/create-variable/)
+from SQL query results.
+The following example uses the [air sensor sample data](#sample-sensor-data) below to
+create a variable that lets you select the location of a sensor.
+
+```js
+import "sql"
+
+sql.from(
+    driverName: "postgres",
+    dataSourceName: "postgresql://localhost?sslmode=disable",
+    query: "SELECT * FROM sensors",
+)
+    |> rename(columns: {location: "_value"})
+    |> keep(columns: ["_value"])
+```
+
+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" />}}
+
+---
+
+## Use secrets to store SQL database credentials
+If your SQL database requires authentication, use [InfluxDB secrets](/influxdb/v2.2/security/secrets/)
+to store and populate connection credentials.
+By default, InfluxDB base64-encodes and stores secrets in its internal key-value store, BoltDB.
+For added security, [store secrets in Vault](/influxdb/v2.2/security/secrets/use-vault/).
+
+### Store your database credentials as secrets
+Use the [InfluxDB API](/influxdb/v2.2/reference/api/) or the [`influx` CLI](/influxdb/v2.2/reference/cli/influx/secret/)
+to store your database credentials as secrets.
+
+{{< tabs-wrapper >}}
+{{% tabs %}}
+[InfluxDB API](#)
+[influx CLI](#)
+{{% /tabs %}}
+{{% tab-content %}}
+```sh
+curl --request PATCH http://localhost:8086/api/v2/orgs/<org-id>/secrets \
+  --header 'Authorization: Token YOURAUTHTOKEN' \
+  --header 'Content-type: application/json' \
+  --data '{
+  "POSTGRES_HOST": "http://example.com",
+  "POSTGRES_USER": "example-username",
+  "POSTGRES_PASS": "example-password"
+}'
+```
+
+**To store secrets, you need:**
+
+- [your organization ID](/influxdb/v2.2/organizations/view-orgs/#view-your-organization-id)  
+- [your API token](/influxdb/v2.2/security/tokens/view-tokens/)
+{{% /tab-content %}}
+{{% tab-content %}}
+```sh
+# Syntax
+influx secret update -k <secret-key>
+
+# Example
+influx secret update -k POSTGRES_PASS
+```
+
+**When prompted, enter your secret value.**
+
+{{% warn %}}
+You can provide the secret value with the `-v`, `--value` flag, but the **plain text
+secret may appear in your shell history**.
+
+```sh
+influx secret update -k <secret-key> -v <secret-value>
+```
+{{% /warn %}}
+{{% /tab-content %}}
+{{< /tabs-wrapper >}}
+
+### Use secrets in your query
+Import the `influxdata/influxdb/secrets` package and use [string interpolation](/{{< latest "flux" >}}/spec/string-interpolation/)
+to populate connection credentials with stored secrets in your Flux query.
+
+```js
+import "sql"
+import "influxdata/influxdb/secrets"
+
+POSTGRES_HOST = secrets.get(key: "POSTGRES_HOST")
+POSTGRES_USER = secrets.get(key: "POSTGRES_USER")
+POSTGRES_PASS = secrets.get(key: "POSTGRES_PASS")
+
+sql.from(
+    driverName: "postgres",
+    dataSourceName: "postgresql://${POSTGRES_USER}:${POSTGRES_PASS}@${POSTGRES_HOST}",
+    query: "SELECT * FROM sensors",
+)
+```
+
+---
+
+## Sample sensor data
+The [air sensor sample data](#download-sample-air-sensor-data) and
+[sample sensor information](#import-the-sample-sensor-information) simulate a
+group of sensors that measure temperature, humidity, and carbon monoxide
+in rooms throughout a building.
+Each collected data point is stored in InfluxDB with a `sensor_id` tag that identifies
+the specific sensor it came from.
+Sample sensor information is stored in PostgreSQL.
+
+**Sample data includes:**
+
+- Simulated data collected from each sensor and stored in the `airSensors` measurement in **InfluxDB**:
+  - temperature
+  - humidity
+  - co
+
+- Information about each sensor stored in the `sensors` table in **PostgreSQL**:
+  - sensor_id
+  - location
+  - model_number
+  - last_inspected
+
+#### Download sample air sensor data
+
+1.  [Create a bucket](/influxdb/v2.2/organizations/buckets/create-bucket/) to store the data.
+2.  [Create an InfluxDB task](/influxdb/v2.2/process-data/manage-tasks/create-task/)
+    and use the [`sample.data()` function](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/sample/data/)
+    to download sample air sensor data every 15 minutes.
+    Write the downloaded sample data to your new bucket:
+
+    ```js
+    import "influxdata/influxdb/sample"
+
+    option task = {name: "Collect sample air sensor data", every: 15m}
+
+    sample.data(set: "airSensor")
+        |> to(org: "example-org", bucket: "example-bucket")
+    ```
+
+3.  [Query your target bucket](/influxdb/v2.2/query-data/execute-queries/) after
+    the first task run to ensure the sample data is writing successfully.
+
+    ```js
+    from(bucket: "example-bucket")
+        |> range(start: -1m)
+        |> filter(fn: (r) => r._measurement == "airSensors")
+    ```
+
+#### Import the sample sensor information
+1. [Download and install PostgreSQL](https://www.postgresql.org/download/).
+2. Download the sample sensor information CSV.
+
+    <a class="btn download" href="https://influx-testdata.s3.amazonaws.com/sample-sensor-info.csv" download>Download sample sensor information</a>
+
+3. Use a PostgreSQL client (`psql` or a GUI) to create the `sensors` table:
+
+    ```
+    CREATE TABLE sensors (
+      sensor_id character varying(50),
+      location character varying(50),
+      model_number character varying(50),
+      last_inspected date
+    );
+    ```
+
+4. Import the downloaded CSV sample data.
+   _Update the `FROM` file path to the path of the downloaded CSV sample data._
+
+    ```
+    COPY sensors(sensor_id,location,model_number,last_inspected)
+    FROM '/path/to/sample-sensor-info.csv' DELIMITER ',' CSV HEADER;
+    ```
+
+5. Query the table to ensure the data was imported correctly:
+
+    ```
+    SELECT * FROM sensors;
+    ```
+
+#### Import the sample data dashboard
+Download and import the Air Sensors dashboard to visualize the generated data:
+
+<a class="btn github" href="https://raw.githubusercontent.com/influxdata/influxdb2-sample-data/master/air-sensor-data/air-sensors-dashboard.json" target="_blank">View Air Sensors dashboard JSON</a>
+
+_For information about importing a dashboard, see [Create a dashboard](/influxdb/v2.2/visualize-data/dashboards/create-dashboard)._
diff --git a/content/influxdb/v2.2/query-data/flux/window-aggregate.md b/content/influxdb/v2.2/query-data/flux/window-aggregate.md
new file mode 100644
index 000000000..590c7d77a
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/flux/window-aggregate.md
@@ -0,0 +1,358 @@
+---
+title: Window and aggregate data with Flux
+seotitle: Window and aggregate data in InfluxDB with Flux
+list_title: Window & aggregate
+description: >
+  This guide walks through windowing and aggregating data with Flux and outlines
+  how it shapes your data in the process.
+menu:
+  influxdb_2_2:
+    name: Window & aggregate
+    parent: Query with Flux
+weight: 204
+influxdb/v2.2/tags: [flux, aggregates]
+aliases:
+  - /influxdb/v2.2/query-data/guides/window-aggregate/
+  - /influxdb/v2.2/query-data/flux/windowing-aggregating/
+related:
+  - /{{< latest "flux" >}}/stdlib/universe/aggregatewindow
+  - /{{< latest "flux" >}}/stdlib/universe/window
+  - /{{< latest "flux" >}}/function-types/#aggregates, Flux aggregate functions
+  - /{{< latest "flux" >}}/function-types/#selectors, Flux selector functions
+list_query_example: aggregate_window
+---
+
+A common operation performed with time series data is grouping data into windows of time,
+or "windowing" data, then aggregating windowed values into a new value.
+This guide walks through windowing and aggregating data with Flux and demonstrates
+how data is shaped in the process.
+
+If you're just getting started with Flux queries, check out the following:
+
+- [Get started with Flux](/{{< latest "flux" >}}/get-started/) for a conceptual overview of Flux and parts of a Flux query.
+- [Execute queries](/influxdb/v2.2/query-data/execute-queries/) to discover a variety of ways to run your queries.
+
+{{% note %}}
+The following example is an in-depth walk-through of the steps required to window and aggregate data.
+The [`aggregateWindow()` function](#summing-up) performs these operations for you, but understanding
+how data is shaped in the process helps to successfully create your desired output.
+{{% /note %}}
+
+## Data set
+For the purposes of this guide, define a variable that represents your base data set.
+The following example queries the memory usage of the host machine.
+
+```js
+dataSet = from(bucket: "example-bucket")
+    |> range(start: -5m)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+    |> drop(columns: ["host"])
+```
+
+{{% note %}}
+This example drops the `host` column from the returned data since the memory data
+is only tracked for a single host and it simplifies the output tables.
+Dropping the `host` column is optional and not recommended if monitoring memory
+on multiple hosts.
+{{% /note %}}
+
+`dataSet` can now be used to represent your base data, which will look similar to the following:
+
+{{% truncate %}}
+```
+Table: keys: [_start, _stop, _field, _measurement]
+                   _start:time                      _stop:time           _field:string     _measurement:string                      _time:time                  _value:float
+------------------------------  ------------------------------  ----------------------  ----------------------  ------------------------------  ----------------------------
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:50:00.000000000Z             71.11611366271973
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:50:10.000000000Z             67.39630699157715
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:50:20.000000000Z             64.16666507720947
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:50:30.000000000Z             64.19951915740967
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:50:40.000000000Z              64.2122745513916
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:50:50.000000000Z             64.22209739685059
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:51:00.000000000Z              64.6336555480957
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:51:10.000000000Z             64.16516304016113
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:51:20.000000000Z             64.18349742889404
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:51:30.000000000Z             64.20474052429199
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:51:40.000000000Z             68.65062713623047
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:51:50.000000000Z             67.20139980316162
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:52:00.000000000Z              70.9143877029419
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:52:10.000000000Z             64.14549350738525
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:52:20.000000000Z             64.15379047393799
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:52:30.000000000Z              64.1592264175415
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:52:40.000000000Z             64.18190002441406
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:52:50.000000000Z             64.28837776184082
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:53:00.000000000Z             64.29731845855713
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:53:10.000000000Z             64.36963081359863
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:53:20.000000000Z             64.37397003173828
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:53:30.000000000Z             64.44413661956787
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:53:40.000000000Z             64.42906856536865
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:53:50.000000000Z             64.44573402404785
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:54:00.000000000Z             64.48912620544434
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:54:10.000000000Z             64.49522972106934
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:54:20.000000000Z             64.48652744293213
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:54:30.000000000Z             64.49949741363525
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:54:40.000000000Z              64.4949197769165
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:54:50.000000000Z             64.49787616729736
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:55:00.000000000Z             64.49816226959229
+```
+{{% /truncate %}}
+
+## Windowing data
+Use the [`window()` function](/{{< latest "flux" >}}/stdlib/universe/window)
+to group your data based on time bounds.
+The most common parameter passed with the `window()` is `every` which
+defines the duration of time between windows.
+Other parameters are available, but for this example, window the base data
+set into one minute windows.
+
+```js
+dataSet
+    |> window(every: 1m)
+```
+
+{{% note %}}
+The `every` parameter supports all [valid duration units](/{{< latest "flux" >}}/spec/types/#duration-types),
+including **calendar months (`1mo`)** and **years (`1y`)**.
+{{% /note %}}
+
+Each window of time is output in its own table containing all records that fall within the window.
+
+{{% truncate %}}
+###### window() output tables
+```
+Table: keys: [_start, _stop, _field, _measurement]
+                   _start:time                      _stop:time           _field:string     _measurement:string                      _time:time                  _value:float
+------------------------------  ------------------------------  ----------------------  ----------------------  ------------------------------  ----------------------------
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:51:00.000000000Z            used_percent                     mem  2018-11-03T17:50:00.000000000Z             71.11611366271973
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:51:00.000000000Z            used_percent                     mem  2018-11-03T17:50:10.000000000Z             67.39630699157715
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:51:00.000000000Z            used_percent                     mem  2018-11-03T17:50:20.000000000Z             64.16666507720947
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:51:00.000000000Z            used_percent                     mem  2018-11-03T17:50:30.000000000Z             64.19951915740967
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:51:00.000000000Z            used_percent                     mem  2018-11-03T17:50:40.000000000Z              64.2122745513916
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:51:00.000000000Z            used_percent                     mem  2018-11-03T17:50:50.000000000Z             64.22209739685059
+
+
+Table: keys: [_start, _stop, _field, _measurement]
+                   _start:time                      _stop:time           _field:string     _measurement:string                      _time:time                  _value:float
+------------------------------  ------------------------------  ----------------------  ----------------------  ------------------------------  ----------------------------
+2018-11-03T17:51:00.000000000Z  2018-11-03T17:52:00.000000000Z            used_percent                     mem  2018-11-03T17:51:00.000000000Z              64.6336555480957
+2018-11-03T17:51:00.000000000Z  2018-11-03T17:52:00.000000000Z            used_percent                     mem  2018-11-03T17:51:10.000000000Z             64.16516304016113
+2018-11-03T17:51:00.000000000Z  2018-11-03T17:52:00.000000000Z            used_percent                     mem  2018-11-03T17:51:20.000000000Z             64.18349742889404
+2018-11-03T17:51:00.000000000Z  2018-11-03T17:52:00.000000000Z            used_percent                     mem  2018-11-03T17:51:30.000000000Z             64.20474052429199
+2018-11-03T17:51:00.000000000Z  2018-11-03T17:52:00.000000000Z            used_percent                     mem  2018-11-03T17:51:40.000000000Z             68.65062713623047
+2018-11-03T17:51:00.000000000Z  2018-11-03T17:52:00.000000000Z            used_percent                     mem  2018-11-03T17:51:50.000000000Z             67.20139980316162
+
+
+Table: keys: [_start, _stop, _field, _measurement]
+                   _start:time                      _stop:time           _field:string     _measurement:string                      _time:time                  _value:float
+------------------------------  ------------------------------  ----------------------  ----------------------  ------------------------------  ----------------------------
+2018-11-03T17:52:00.000000000Z  2018-11-03T17:53:00.000000000Z            used_percent                     mem  2018-11-03T17:52:00.000000000Z              70.9143877029419
+2018-11-03T17:52:00.000000000Z  2018-11-03T17:53:00.000000000Z            used_percent                     mem  2018-11-03T17:52:10.000000000Z             64.14549350738525
+2018-11-03T17:52:00.000000000Z  2018-11-03T17:53:00.000000000Z            used_percent                     mem  2018-11-03T17:52:20.000000000Z             64.15379047393799
+2018-11-03T17:52:00.000000000Z  2018-11-03T17:53:00.000000000Z            used_percent                     mem  2018-11-03T17:52:30.000000000Z              64.1592264175415
+2018-11-03T17:52:00.000000000Z  2018-11-03T17:53:00.000000000Z            used_percent                     mem  2018-11-03T17:52:40.000000000Z             64.18190002441406
+2018-11-03T17:52:00.000000000Z  2018-11-03T17:53:00.000000000Z            used_percent                     mem  2018-11-03T17:52:50.000000000Z             64.28837776184082
+
+
+Table: keys: [_start, _stop, _field, _measurement]
+                   _start:time                      _stop:time           _field:string     _measurement:string                      _time:time                  _value:float
+------------------------------  ------------------------------  ----------------------  ----------------------  ------------------------------  ----------------------------
+2018-11-03T17:53:00.000000000Z  2018-11-03T17:54:00.000000000Z            used_percent                     mem  2018-11-03T17:53:00.000000000Z             64.29731845855713
+2018-11-03T17:53:00.000000000Z  2018-11-03T17:54:00.000000000Z            used_percent                     mem  2018-11-03T17:53:10.000000000Z             64.36963081359863
+2018-11-03T17:53:00.000000000Z  2018-11-03T17:54:00.000000000Z            used_percent                     mem  2018-11-03T17:53:20.000000000Z             64.37397003173828
+2018-11-03T17:53:00.000000000Z  2018-11-03T17:54:00.000000000Z            used_percent                     mem  2018-11-03T17:53:30.000000000Z             64.44413661956787
+2018-11-03T17:53:00.000000000Z  2018-11-03T17:54:00.000000000Z            used_percent                     mem  2018-11-03T17:53:40.000000000Z             64.42906856536865
+2018-11-03T17:53:00.000000000Z  2018-11-03T17:54:00.000000000Z            used_percent                     mem  2018-11-03T17:53:50.000000000Z             64.44573402404785
+
+
+Table: keys: [_start, _stop, _field, _measurement]
+                   _start:time                      _stop:time           _field:string     _measurement:string                      _time:time                  _value:float
+------------------------------  ------------------------------  ----------------------  ----------------------  ------------------------------  ----------------------------
+2018-11-03T17:54:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:54:00.000000000Z             64.48912620544434
+2018-11-03T17:54:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:54:10.000000000Z             64.49522972106934
+2018-11-03T17:54:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:54:20.000000000Z             64.48652744293213
+2018-11-03T17:54:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:54:30.000000000Z             64.49949741363525
+2018-11-03T17:54:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:54:40.000000000Z              64.4949197769165
+2018-11-03T17:54:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:54:50.000000000Z             64.49787616729736
+
+
+Table: keys: [_start, _stop, _field, _measurement]
+                   _start:time                      _stop:time           _field:string     _measurement:string                      _time:time                  _value:float
+------------------------------  ------------------------------  ----------------------  ----------------------  ------------------------------  ----------------------------
+2018-11-03T17:55:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:55:00.000000000Z             64.49816226959229
+```
+{{% /truncate %}}
+
+When visualized in the InfluxDB UI, each window table is displayed in a different color.
+
+![Windowed data](/img/flux/simple-windowed-data.png)
+
+## Aggregate data
+[Aggregate functions](/{{< latest "flux" >}}/function-types#aggregates) take the values
+of all rows in a table and use them to perform an aggregate operation.
+The result is output as a new value in a single-row table.
+
+Since windowed data is split into separate tables, aggregate operations run against
+each table separately and output new tables containing only the aggregated value.
+
+For this example, use the [`mean()` function](/{{< latest "flux" >}}/stdlib/universe/mean)
+to output the average of each window:
+
+```js
+dataSet
+    |> window(every: 1m)
+    |> mean()
+```
+
+{{% truncate %}}
+###### mean() output tables
+```
+Table: keys: [_start, _stop, _field, _measurement]
+                   _start:time                      _stop:time           _field:string     _measurement:string                  _value:float
+------------------------------  ------------------------------  ----------------------  ----------------------  ----------------------------
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:51:00.000000000Z            used_percent                     mem             65.88549613952637
+
+
+Table: keys: [_start, _stop, _field, _measurement]
+                   _start:time                      _stop:time           _field:string     _measurement:string                  _value:float
+------------------------------  ------------------------------  ----------------------  ----------------------  ----------------------------
+2018-11-03T17:51:00.000000000Z  2018-11-03T17:52:00.000000000Z            used_percent                     mem             65.50651391347249
+
+
+Table: keys: [_start, _stop, _field, _measurement]
+                   _start:time                      _stop:time           _field:string     _measurement:string                  _value:float
+------------------------------  ------------------------------  ----------------------  ----------------------  ----------------------------
+2018-11-03T17:52:00.000000000Z  2018-11-03T17:53:00.000000000Z            used_percent                     mem             65.30719598134358
+
+
+Table: keys: [_start, _stop, _field, _measurement]
+                   _start:time                      _stop:time           _field:string     _measurement:string                  _value:float
+------------------------------  ------------------------------  ----------------------  ----------------------  ----------------------------
+2018-11-03T17:53:00.000000000Z  2018-11-03T17:54:00.000000000Z            used_percent                     mem             64.39330975214641
+
+
+Table: keys: [_start, _stop, _field, _measurement]
+                   _start:time                      _stop:time           _field:string     _measurement:string                  _value:float
+------------------------------  ------------------------------  ----------------------  ----------------------  ----------------------------
+2018-11-03T17:54:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem             64.49386278788249
+
+
+Table: keys: [_start, _stop, _field, _measurement]
+                   _start:time                      _stop:time           _field:string     _measurement:string                  _value:float
+------------------------------  ------------------------------  ----------------------  ----------------------  ----------------------------
+2018-11-03T17:55:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem             64.49816226959229
+```
+{{% /truncate %}}
+
+Because each data point is contained in its own table, when visualized,
+they appear as single, unconnected points.
+
+![Aggregated windowed data](/img/flux/simple-windowed-aggregate-data.png)
+
+### Recreate the time column
+**Notice the `_time` column is not in the [aggregated output tables](#mean-output-tables).**
+Because records in each table are aggregated together, their timestamps no longer
+apply and the column is removed from the group key and table.
+
+Also notice the `_start` and `_stop` columns still exist.
+These represent the lower and upper bounds of the time window.
+
+Many Flux functions rely on the `_time` column.
+To further process your data after an aggregate function, you need to re-add `_time`.
+Use the [`duplicate()` function](/{{< latest "flux" >}}/stdlib/universe/duplicate) to
+duplicate either the `_start` or `_stop` column as a new `_time` column.
+
+```js
+dataSet
+    |> window(every: 1m)
+    |> mean()
+    |> duplicate(column: "_stop", as: "_time")
+```
+
+{{% truncate %}}
+###### duplicate() output tables
+```
+Table: keys: [_start, _stop, _field, _measurement]
+                   _start:time                      _stop:time           _field:string     _measurement:string                      _time:time                  _value:float
+------------------------------  ------------------------------  ----------------------  ----------------------  ------------------------------  ----------------------------
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:51:00.000000000Z            used_percent                     mem  2018-11-03T17:51:00.000000000Z             65.88549613952637
+
+
+Table: keys: [_start, _stop, _field, _measurement]
+                   _start:time                      _stop:time           _field:string     _measurement:string                      _time:time                  _value:float
+------------------------------  ------------------------------  ----------------------  ----------------------  ------------------------------  ----------------------------
+2018-11-03T17:51:00.000000000Z  2018-11-03T17:52:00.000000000Z            used_percent                     mem  2018-11-03T17:52:00.000000000Z             65.50651391347249
+
+
+Table: keys: [_start, _stop, _field, _measurement]
+                   _start:time                      _stop:time           _field:string     _measurement:string                      _time:time                  _value:float
+------------------------------  ------------------------------  ----------------------  ----------------------  ------------------------------  ----------------------------
+2018-11-03T17:52:00.000000000Z  2018-11-03T17:53:00.000000000Z            used_percent                     mem  2018-11-03T17:53:00.000000000Z             65.30719598134358
+
+
+Table: keys: [_start, _stop, _field, _measurement]
+                   _start:time                      _stop:time           _field:string     _measurement:string                      _time:time                  _value:float
+------------------------------  ------------------------------  ----------------------  ----------------------  ------------------------------  ----------------------------
+2018-11-03T17:53:00.000000000Z  2018-11-03T17:54:00.000000000Z            used_percent                     mem  2018-11-03T17:54:00.000000000Z             64.39330975214641
+
+
+Table: keys: [_start, _stop, _field, _measurement]
+                   _start:time                      _stop:time           _field:string     _measurement:string                      _time:time                  _value:float
+------------------------------  ------------------------------  ----------------------  ----------------------  ------------------------------  ----------------------------
+2018-11-03T17:54:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:55:00.000000000Z             64.49386278788249
+
+
+Table: keys: [_start, _stop, _field, _measurement]
+                   _start:time                      _stop:time           _field:string     _measurement:string                      _time:time                  _value:float
+------------------------------  ------------------------------  ----------------------  ----------------------  ------------------------------  ----------------------------
+2018-11-03T17:55:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:55:00.000000000Z             64.49816226959229
+```
+{{% /truncate %}}
+
+## "Unwindow" aggregate tables
+Keeping aggregate values in separate tables generally isn't the format in which you want your data.
+Use the `window()` function to "unwindow" your data into a single infinite (`inf`) window.
+
+```js
+dataSet
+    |> window(every: 1m)
+    |> mean()
+    |> duplicate(column: "_stop", as: "_time")
+    |> window(every: inf)
+```
+
+{{% note %}}
+Windowing requires a `_time` column which is why it's necessary to
+[recreate the `_time` column](#recreate-the-time-column) after an aggregation.
+{{% /note %}}
+
+###### Unwindowed output table
+```
+Table: keys: [_start, _stop, _field, _measurement]
+                   _start:time                      _stop:time           _field:string     _measurement:string                      _time:time                  _value:float
+------------------------------  ------------------------------  ----------------------  ----------------------  ------------------------------  ----------------------------
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:51:00.000000000Z             65.88549613952637
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:52:00.000000000Z             65.50651391347249
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:53:00.000000000Z             65.30719598134358
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:54:00.000000000Z             64.39330975214641
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:55:00.000000000Z             64.49386278788249
+2018-11-03T17:50:00.000000000Z  2018-11-03T17:55:00.000000000Z            used_percent                     mem  2018-11-03T17:55:00.000000000Z             64.49816226959229
+```
+
+With the aggregate values in a single table, data points in the visualization are connected.
+
+![Unwindowed aggregate data](/img/flux/simple-unwindowed-data.png)
+
+## Summing up
+You have now created a Flux query that windows and aggregates data.
+The data transformation process outlined in this guide should be used for all aggregation operations.
+
+Flux also provides the [`aggregateWindow()` function](/{{< latest "flux" >}}/stdlib/universe/aggregatewindow)
+which performs all these separate functions for you.
+
+The following Flux query will return the same results:
+
+###### aggregateWindow function
+```js
+dataSet
+    |> aggregateWindow(every: 1m, fn: mean)
+```
diff --git a/content/influxdb/v2.2/query-data/get-started/_index.md b/content/influxdb/v2.2/query-data/get-started/_index.md
new file mode 100644
index 000000000..6427a8e48
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/get-started/_index.md
@@ -0,0 +1,35 @@
+---
+title: Get started with Flux and InfluxDB
+description: >
+  Get started with Flux, the functional data scripting language, and learn the 
+  basics of writing a Flux query that queries InfluxDB.
+aliases:
+  - /influxdb/v2.2/query-data/get-started/getting-started
+weight: 101
+influxdb/v2.2/tags: [query, flux, get-started]
+menu:
+  influxdb_2_2:
+    name: Get started with Flux
+    parent: Query data
+related:
+  - /{{< latest "flux" >}}/get-started/
+  - /{{< latest "flux" >}}/
+  - /{{< latest "flux" >}}/stdlib/
+---
+
+Flux is InfluxData's functional data scripting language designed for querying,
+analyzing, and acting on data.
+
+These guides walks through important concepts related to Flux and querying time
+series data from InfluxDB using Flux.
+
+## Tools for working with Flux
+The [Execute queries](/influxdb/v2.2/query-data/execute-queries) guide walks through
+the different tools available for querying InfluxDB with Flux.
+
+## Before you start
+To get a basic understanding of the Flux data model and syntax, see
+[Get started with Flux](/{{< latest "flux" >}}/get-started/) in the
+[Flux documentation](/{{< latest "flux" >}}/).
+
+{{< page-nav next="/influxdb/v2.2/query-data/get-started/query-influxdb/" >}}
diff --git a/content/influxdb/v2.2/query-data/get-started/query-influxdb.md b/content/influxdb/v2.2/query-data/get-started/query-influxdb.md
new file mode 100644
index 000000000..524265391
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/get-started/query-influxdb.md
@@ -0,0 +1,133 @@
+---
+title: Query InfluxDB with Flux
+description: Learn the basics of using Flux to query data from InfluxDB.
+influxdb/v2.2/tags: [query, flux]
+menu:
+  influxdb_2_2:
+    name: Query InfluxDB
+    parent: Get started with Flux
+weight: 201
+related:
+  - /{{< latest "flux" >}}/get-started/query-basics/
+  - /influxdb/v2.2/query-data/flux/
+  - /{{< latest "flux" >}}/stdlib/influxdata/influxdb/from
+  - /{{< latest "flux" >}}/stdlib/universe/range
+  - /{{< latest "flux" >}}/stdlib/universe/filter
+---
+
+This guide walks through the basics of using Flux to query data from InfluxDB.
+Every Flux query needs the following:
+
+1. [A data source](#1-define-your-data-source)
+2. [A time range](#2-specify-a-time-range)
+3. [Data filters](#3-filter-your-data)
+
+
+## 1. Define your data source
+Flux's [`from()`](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/from/) function defines an InfluxDB data source.
+It requires a [`bucket`](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/from/#bucket) parameter.
+The following examples use `example-bucket` as the bucket name.
+
+```js
+from(bucket:"example-bucket")
+```
+
+## 2. Specify a time range
+Flux requires a time range when querying time series data.
+"Unbounded" queries are very resource-intensive and as a protective measure,
+Flux will not query the database without a specified range.
+
+Use the [pipe-forward operator](/{{< latest "flux" >}}/get-started/syntax-basics/#pipe-forward-operator)
+(`|>`) to pipe data from your data source into
+[`range()`](/{{< latest "flux" >}}/stdlib/universe/range), which specifies a time range for your query.
+It accepts two parameters: `start` and `stop`.
+Start and stop values can be **relative** using negative [durations](/{{< latest "flux" >}}/data-types/basic/duration/)
+or **absolute** using [timestamps](/{{< latest "flux" >}}/data-types/basic/time/).
+
+###### Example relative time ranges
+```js
+// Relative time range with start only. Stop defaults to now.
+from(bucket:"example-bucket")
+    |> range(start: -1h)
+
+// Relative time range with start and stop
+from(bucket:"example-bucket")
+    |> range(start: -1h, stop: -10m)
+```
+
+{{% note %}}
+Relative ranges are relative to "now."
+{{% /note %}}
+
+###### Example absolute time range
+```js
+from(bucket:"example-bucket")
+    |> range(start: 2021-01-01T00:00:00Z, stop: 2021-01-01T12:00:00Z)
+```
+
+#### Use the following:
+For this guide, use the relative time range, `-15m`, to limit query results to data from the last 15 minutes:
+
+```js
+from(bucket:"example-bucket")
+    |> range(start: -15m)
+```
+
+## 3. Filter your data
+Pass your ranged data into `filter()` to narrow results based on data attributes or columns.
+`filter()` has one parameter, `fn`, which expects a
+[predicate function](/{{< latest "flux" >}}/get-started/syntax-basics/#predicate-functions)
+evaluates rows by column values.
+
+`filter()` iterates over every input row and structures row data as a Flux
+[record](/{{< latest "flux" >}}/data-types/composite/record/). 
+The record is passed into the predicate function as `r` where it is evaluated using
+[predicate expressions](/{{< latest "flux" >}}/get-started/syntax-basics/#predicate-expressions).
+
+Rows that evaluate to `false` are dropped from the output data.
+Rows that evaluate to `true` persist in the output data.
+
+```js
+// Pattern
+(r) => (r.recordProperty comparisonOperator comparisonExpression)
+
+// Example with single filter
+(r) => (r._measurement == "cpu")
+
+// Example with multiple filters
+(r) => r._measurement == "cpu" and r._field != "usage_system")
+```
+
+#### Use the following:
+For this example, filter by the `cpu` measurement, `usage_system` field, and
+`cpu-total` tag value:
+
+```js
+from(bucket: "example-bucket")
+    |> range(start: -15m)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_system" and r.cpu == "cpu-total")
+```
+
+## 4. Yield your queried data
+[`yield()`](/{{< latest "flux" >}}/stdlib/universe/yield/) outputs the result of the query.
+
+```js
+from(bucket: "example-bucket")
+    |> range(start: -15m)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_system" and r.cpu == "cpu-total")
+    |> yield()
+```
+
+Flux automatically assumes a `yield()` function at
+the end of each script to output and visualize the data.
+Explicitly calling `yield()` is only necessary when including multiple queries
+in the same Flux query.
+Each set of returned data needs to be named using the `yield()` function.
+
+## Congratulations!
+You have now queried data from InfluxDB using Flux.
+
+The query shown here is a basic example.
+Flux queries can be extended in many ways to form powerful scripts.
+
+{{< page-nav prev="/influxdb/v2.2/query-data/get-started/" next="/influxdb/v2.2/query-data/get-started/transform-data/" >}}
diff --git a/content/influxdb/v2.2/query-data/get-started/transform-data.md b/content/influxdb/v2.2/query-data/get-started/transform-data.md
new file mode 100644
index 000000000..e4cc678ac
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/get-started/transform-data.md
@@ -0,0 +1,162 @@
+---
+title: Transform data with Flux
+description: Learn the basics of using Flux to transform data queried from InfluxDB.
+influxdb/v2.2/tags: [flux, transform, query]
+menu:
+  influxdb_2_2:
+    name: Transform data
+    parent: Get started with Flux
+weight: 202
+related:
+  - /{{< latest "flux" >}}/stdlib/universe/aggregatewindow
+  - /{{< latest "flux" >}}/stdlib/universe/window
+---
+
+When [querying data from InfluxDB](/influxdb/v2.2/query-data/get-started/query-influxdb),
+you often need to transform that data in some way.
+Common examples are aggregating data, downsampling data, etc.
+
+This guide demonstrates using [Flux functions](/{{< latest "flux" >}}/stdlib/) to transform your data.
+It walks through creating a Flux script that partitions data into windows of time,
+averages the `_value`s in each window, and outputs the averages as a new table.
+
+{{% note %}}
+If you're not familiar with how Flux structures and operates on data, see
+[Flux data model](/{{< latest "flux" >}}/get-started/data-model/).
+{{% /note %}}
+
+## Query data
+Use the query built in the previous [Query data from InfluxDB](/influxdb/v2.2/query-data/get-started/query-influxdb)
+guide, but update the range to pull data from the last hour:
+
+```js
+from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_system" and r.cpu == "cpu-total")
+```
+
+## Flux functions
+Flux provides a number of functions that perform specific operations, transformations, and tasks.
+You can also [create custom functions](/influxdb/v2.2/query-data/flux/custom-functions) in your Flux queries.
+_Functions are covered in detail in the [Flux standard library](/{{< latest "flux" >}}/stdlib/) documentation._
+
+A common type of function used when transforming data queried from InfluxDB is an aggregate function.
+Aggregate functions take a set of `_value`s in a table, aggregate them, and transform
+them into a new value.
+
+This example uses the [`mean()` function](/{{< latest "flux" >}}/stdlib/universe/mean)
+to average values within each time window.
+
+{{% note %}}
+The following example walks through the steps required to window and aggregate data,
+but there is a [`aggregateWindow()` helper function](#helper-functions) that does it for you.
+It's just good to understand the steps in the process.
+{{% /note %}}
+
+## Window your data
+Flux's [`window()` function](/{{< latest "flux" >}}/stdlib/universe/window) partitions records based on a time value.
+Use the `every` parameter to define a duration of each window.
+
+{{% note %}}
+#### Calendar months and years
+`every` supports all [valid duration units](/{{< latest "flux" >}}/spec/types/#duration-types),
+including **calendar months (`1mo`)** and **years (`1y`)**.
+{{% /note %}}
+
+For this example, window data in five minute intervals (`5m`).
+
+```js
+from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_system" and r.cpu == "cpu-total")
+    |> window(every: 5m)
+```
+
+As data is gathered into windows of time, each window is output as its own table.
+When visualized, each table is assigned a unique color.
+
+![Windowed data tables](/img/flux/windowed-data.png)
+
+## Aggregate windowed data
+Flux aggregate functions take the `_value`s in each table and aggregate them in some way.
+Use the [`mean()` function](/{{< latest "flux" >}}/stdlib/universe/mean) to average the `_value`s of each table.
+
+```js
+from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_system" and r.cpu == "cpu-total")
+    |> window(every: 5m)
+    |> mean()
+```
+
+As rows in each window are aggregated, their output table contains only a single row with the aggregate value.
+Windowed tables are all still separate and, when visualized, will appear as single, unconnected points.
+
+![Windowed aggregate data](/img/flux/windowed-aggregates.png)
+
+## Add times to your aggregates
+As values are aggregated, the resulting tables do not have a `_time` column because
+the records used for the aggregation all have different timestamps.
+Aggregate functions don't infer what time should be used for the aggregate value.
+Therefore the `_time` column is dropped.
+
+A `_time` column is required in the [next operation](#unwindow-aggregate-tables).
+To add one, use the [`duplicate()` function](/{{< latest "flux" >}}/stdlib/universe/duplicate)
+to duplicate the `_stop` column as the `_time` column for each windowed table.
+
+```js
+from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_system" and r.cpu == "cpu-total")
+    |> window(every: 5m)
+    |> mean()
+    |> duplicate(column: "_stop", as: "_time")
+```
+
+## Unwindow aggregate tables
+
+Use the `window()` function with the `every: inf` parameter to gather all points
+into a single, infinite window.
+
+```js
+from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_system" and r.cpu == "cpu-total")
+    |> window(every: 5m)
+    |> mean()
+    |> duplicate(column: "_stop", as: "_time")
+    |> window(every: inf)
+```
+
+Once ungrouped and combined into a single table, the aggregate data points will appear connected in your visualization.
+
+![Unwindowed aggregate data](/img/flux/windowed-aggregates-ungrouped.png)
+
+## Helper functions
+This may seem like a lot of coding just to build a query that aggregates data, however going through the
+process helps to understand how data changes "shape" as it is passed through each function.
+
+Flux provides (and allows you to create) "helper" functions that abstract many of these steps.
+The same operation performed in this guide can be accomplished using
+[`aggregateWindow()`](/{{< latest "flux" >}}/stdlib/universe/aggregatewindow).
+
+```js
+from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_system" and r.cpu == "cpu-total")
+    |> aggregateWindow(every: 5m, fn: mean)
+```
+
+## Congratulations!
+You have now constructed a Flux query that uses Flux functions to transform your data.
+There are many more ways to manipulate your data using both Flux's primitive functions
+and your own custom functions, but this is a good introduction into the basic syntax and query structure.
+
+---
+
+_For a deeper dive into windowing and aggregating data with example data output for each transformation,
+view the [Window and aggregate data](/influxdb/v2.2/query-data/flux/window-aggregate) guide._
+
+---
+
+{{< page-nav prev="/influxdb/v2.2/query-data/get-started/query-influxdb/" >}}
diff --git a/content/influxdb/v2.2/query-data/influxql.md b/content/influxdb/v2.2/query-data/influxql.md
new file mode 100644
index 000000000..2210f3cc5
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/influxql.md
@@ -0,0 +1,250 @@
+---
+title: Query data with InfluxQL
+description: >
+  Use the [InfluxDB 1.x `/query` compatibility endpoint](/influxdb/v2.2/reference/api/influxdb-1x/query)
+  to query data in InfluxDB Cloud and InfluxDB OSS 2.2 with **InfluxQL**.
+weight: 102
+influxdb/v2.2/tags: [influxql, query]
+menu:
+  influxdb_2_2:
+    name: Query with InfluxQL
+    parent: Query data
+related:
+  - /influxdb/v2.2/reference/api/influxdb-1x/
+  - /influxdb/v2.2/reference/api/influxdb-1x/query
+  - /influxdb/v2.2/reference/api/influxdb-1x/dbrp
+---
+
+In InfluxDB 1.x, data is stored in [databases](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#database)
+and [retention policies](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#retention-policy-rp).
+In InfluxDB OSS {{< current-version >}}, data is stored in [buckets](/influxdb/v2.2/reference/glossary/#bucket).
+Because InfluxQL uses the 1.x data model, a bucket must be mapped to a database and retention policy (DBRP) before it can be queried using InfluxQL.
+
+{{% note %}}
+#### InfluxQL reference documentation
+For complete InfluxQL reference documentation, see
+[Influx Query Language in the latest InfluxDB 1.x documentation](/{{< latest "influxdb" "v1" >}}/query_language/).
+{{% /note %}}
+
+**To use InfluxQL to query bucket data, complete the following steps:**
+
+1. [Verify buckets have a mapping](#verify-buckets-have-a-mapping).
+2. [Map unmapped buckets](#map-unmapped-buckets).
+3. [Query a mapped bucket with InfluxQL](#query-a-mapped-bucket-with-influxql).
+
+## Verify buckets have a mapping
+
+{{% note %}}
+When [upgrading from InfluxDB 1.x to {{< current-version >}}](/influxdb/v2.2/upgrade/v1-to-v2/),
+database and retention policy combinations are mapped to InfluxDB {{< current-version >}} buckets.
+For more information, see [Database and retention policy mapping](/influxdb/v2.2/reference/api/influxdb-1x/dbrp/).
+If you're not sure how data was written into a bucket, verify the bucket has a mapping.
+{{% /note %}}
+
+Use the [`influx` CLI](/influxdb/v2.2/reference/cli/influx/) or the [InfluxDB API](/influxdb/v2.2/reference/api/)
+to verify the buckets you want to query are mapped to a database and retention policy.
+
+{{< tabs-wrapper >}}
+{{% tabs %}}
+[influx CLI](#)
+[InfluxDB API](#)
+{{% /tabs %}}
+{{% tab-content %}}
+
+Use the [`influx v1 dbrp list` command](/influxdb/v2.2/reference/cli/influx/v1/dbrp/list/) to list DBRP mappings.
+
+{{% note %}}
+The examples below assume that your organization and API token are
+provided by the active [InfluxDB connection configuration](/influxdb/v2.2/reference/cli/influx/config/) in the `influx` CLI.
+If not, include your organization (`--org`) and API token (`--token`) with each command.
+{{% /note %}}
+
+##### View all DBRP mappings
+```sh
+influx v1 dbrp list
+```
+
+##### Filter DBRP mappings by database
+```sh
+influx v1 dbrp list --db example-db
+```
+
+##### Filter DBRP mappings by bucket ID
+```sh
+influx v1 dbrp list --bucket-id 00oxo0oXx000x0Xo
+```
+{{% /tab-content %}}
+{{% tab-content %}}
+Use the [`/api/v2/dbrps` API endpoint](/influxdb/v2.2/api/#operation/GetDBRPs) to list DBRP mappings.
+Include the following:
+
+- **Request method:** `GET`
+- **Headers:**
+  - **Authorization:** `Token` schema with your InfluxDB [API token](/influxdb/v2.2/security/tokens/)
+- **Query parameters:**  
+  {{< req type="key" >}}
+  - {{< req "\*" >}} **orgID:** [organization ID](/influxdb/v2.2/organizations/view-orgs/#view-your-organization-id)
+  - **bucketID:** [bucket ID](/influxdb/v2.2/organizations/buckets/view-buckets/) _(to list DBRP mappings for a specific bucket)_
+  - **database:** database name _(to list DBRP mappings with a specific database name)_
+  - **rp:** retention policy name _(to list DBRP mappings with a specific retention policy name)_
+  - **id:** DBRP mapping ID _(to list a specific DBRP mapping)_
+
+##### View all DBRP mappings
+```sh
+curl --request GET \
+  http://localhost:8086/api/v2/dbrps?orgID=00oxo0oXx000x0Xo \
+  --header "Authorization: Token YourAuthToken"
+```
+
+##### Filter DBRP mappings by database
+```sh
+curl --request GET \
+  http://localhost:8086/api/v2/dbrps?orgID=00oxo0oXx000x0Xo&db=example-db \
+  --header "Authorization: Token YourAuthToken"
+```
+
+##### Filter DBRP mappings by bucket ID
+```sh
+curl --request GET \
+  https://cloud2.influxdata.com/api/v2/dbrps?organization_id=00oxo0oXx000x0Xo&bucketID=00oxo0oXx000x0Xo \
+  --header "Authorization: Token YourAuthToken"
+```
+{{% /tab-content %}}
+{{% /tabs-wrapper %}}
+
+If you **do not find a DBRP mapping for a bucket**, complete the next procedure to map the unmapped bucket.
+_For more information on the DBRP mapping API, see the [`/api/v2/dbrps` endpoint documentation](/influxdb/v2.2/api/#tag/DBRPs)._
+
+## Map unmapped buckets
+Use the [`influx` CLI](/influxdb/v2.2/reference/cli/influx/) or the [InfluxDB API](/influxdb/v2.2/reference/api/)
+to manually create DBRP mappings for unmapped buckets.
+
+{{< tabs-wrapper >}}
+{{% tabs %}}
+[influx CLI](#)
+[InfluxDB API](#)
+{{% /tabs %}}
+{{% tab-content %}}
+
+Use the [`influx v1 dbrp create` command](/influxdb/v2.2/reference/cli/influx/v1/dbrp/create/)
+to map an unmapped bucket to a database and retention policy.
+Include the following:
+
+{{< req type="key" >}}
+
+- {{< req "\*" >}} **org** and **token** to authenticate. We recommend setting your organization and token to your active InfluxDB connection configuration in the influx CLI, so you don't have to add these parameters to each command. To set up your active InfluxDB configuration, see [`influx config set`](/influxdb/v2.2/reference/cli/influx/config/set/).
+- {{< req "\*" >}} **database name** to map
+- {{< req "\*" >}} **retention policy** name to map
+- {{< req "\*" >}} [Bucket ID](/influxdb/v2.2/organizations/buckets/view-buckets/#view-buckets-in-the-influxdb-ui) to map to
+- **Default flag** to set the provided retention policy as the default retention policy for the database
+
+```sh
+influx v1 dbrp create \
+  --db example-db \
+  --rp example-rp \
+  --bucket-id 00oxo0oXx000x0Xo \
+  --default
+```
+
+{{% /tab-content %}}
+{{% tab-content %}}
+
+Use the [`/api/v2/dbrps` API endpoint](/influxdb/v2.2/api/#operation/PostDBRP) to create a new DBRP mapping.
+Include the following:
+
+- **Request method:** `POST`
+- **Headers:**
+  - **Authorization:** `Token` schema with your InfluxDB [API token](/influxdb/v2.2/security/tokens/)
+  - **Content-type:** `application/json`
+- **Request body:** JSON object with the following fields:  
+  {{< req type="key" >}}
+  - {{< req "\*" >}} **bucketID:** [bucket ID](/influxdb/v2.2/organizations/buckets/view-buckets/)
+  - {{< req "\*" >}} **database:** database name
+  - **default:** set the provided retention policy as the default retention policy for the database
+  - {{< req "\*" >}} **org** or **orgID:** organization name or [organization ID](/influxdb/v2.2/organizations/view-orgs/#view-your-organization-id)
+  - {{< req "\*" >}} **retention_policy:** retention policy name
+
+<!--  -->
+```sh
+curl --request POST http://localhost:8086/api/v2/dbrps \
+  --header "Authorization: Token YourAuthToken" \
+  --header 'Content-type: application/json' \
+  --data '{
+        "bucketID": "00oxo0oXx000x0Xo",
+        "database": "example-db",
+        "default": true,
+        "orgID": "00oxo0oXx000x0Xo",
+        "retention_policy": "example-rp"
+      }'
+```
+
+{{% /tab-content %}}
+{{< /tabs-wrapper >}}
+
+After you've verified the bucket is mapped, query the bucket using the `query` 1.x compatibility endpoint.
+
+## Query a mapped bucket with InfluxQL
+
+The [InfluxDB 1.x compatibility API](/influxdb/v2.2/reference/api/influxdb-1x/) supports
+all InfluxDB 1.x client libraries and integrations in InfluxDB OSS {{< current-version >}}.
+
+To query a mapped bucket with InfluxQL, use the [`/query` 1.x compatibility endpoint](/influxdb/v2.2/reference/api/influxdb-1x/query/).
+Include the following in your request:
+
+- **Request method:** `GET`
+- **Headers:**
+  - **Authorization:** _See [compatibility API authentication](/influxdb/v2.2/reference/api/influxdb-1x/#authentication)_
+- **Query parameters:**
+  - **db**: 1.x database to query
+  - **rp**: 1.x retention policy to query _(if no retention policy is specified, InfluxDB uses the default retention policy for the specified database)_
+  - **q**: URL-encoded InfluxQL query
+
+{{% api/url-encode-note %}}
+
+```sh
+curl --get http://localhost:8086/query?db=example-db \
+  --header "Authorization: Token YourAuthToken" \
+  --data-urlencode "q=SELECT used_percent FROM example-db.example-rp.example-measurement WHERE host=host1"
+```
+
+By default, the `/query` compatibility endpoint returns results in **JSON**.
+To return results as **CSV**, include the `Accept: application/csv` header.
+
+## InfluxQL support
+
+InfluxDB OSS {{< current-version >}} supports InfluxQL **read-only** queries. See supported and unsupported queries below.
+To learn more about InfluxQL, see [Influx Query Language (InfluxQL)](/{{< latest "influxdb" "v1" >}}/query_language/).
+
+{{< flex >}}
+{{< flex-content >}}
+{{% note %}}
+##### Supported InfluxQL queries
+
+- `DELETE`*
+- `DROP MEASUREMENT`*
+- `EXPLAIN ANALYZE`
+- `SELECT` _(read-only)_
+- `SHOW DATABASES`
+- `SHOW MEASUREMENTS`
+- `SHOW TAG KEYS`
+- `SHOW TAG VALUES`
+- `SHOW FIELD KEYS`
+
+\* These commands delete data.
+{{% /note %}}
+{{< /flex-content >}}
+{{< flex-content >}}
+{{% warn %}}
+
+##### Unsupported InfluxQL queries
+
+- `SELECT INTO`
+- `ALTER`
+- `CREATE`
+- `DROP` _(limited support)_
+- `GRANT`
+- `KILL`
+- `REVOKE`
+{{% /warn %}}
+{{< /flex-content >}}
+{{< /flex >}}
diff --git a/content/influxdb/v2.2/query-data/optimize-queries.md b/content/influxdb/v2.2/query-data/optimize-queries.md
new file mode 100644
index 000000000..3141a9b54
--- /dev/null
+++ b/content/influxdb/v2.2/query-data/optimize-queries.md
@@ -0,0 +1,190 @@
+---
+title: Optimize Flux queries
+description: >
+  Optimize your Flux queries to reduce their memory and compute (CPU) requirements.
+weight: 104
+menu:
+  influxdb_2_2:
+    name: Optimize queries
+    parent: Query data
+influxdb/v2.2/tags: [query]
+---
+
+Optimize your Flux queries to reduce their memory and compute (CPU) requirements.
+
+- [Start queries with pushdowns](#start-queries-with-pushdowns)
+  - [Avoid processing filters inline](#avoid-processing-filters-inline)
+- [Avoid short window durations](#avoid-short-window-durations)
+- [Use "heavy" functions sparingly](#use-heavy-functions-sparingly)
+- [Use set() instead of map() when possible](#use-set-instead-of-map-when-possible)
+- [Balance time range and data precision](#balance-time-range-and-data-precision)
+- [Measure query performance with Flux profilers](#measure-query-performance-with-flux-profilers)
+
+## Start queries with pushdowns
+**Pushdowns** are functions or function combinations that push data operations
+to the underlying data source rather than operating on data in memory.
+Start queries with pushdowns to improve query performance.
+Once a non-pushdown function runs, Flux pulls data into memory and runs all
+subsequent operations there.
+
+#### Pushdown functions and function combinations
+Most pushdowns are supported when querying an InfluxDB {{< current-version >}} or InfluxDB Cloud data source.
+As shown in the following table, a handful of pushdowns are not supported in InfluxDB {{< current-version >}}.
+
+| Functions                      | InfluxDB {{< current-version keep=true >}} |    InfluxDB Cloud    |
+| :----------------------------- | :----------------------------------------: | :------------------: |
+| **count()**                    |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| **duplicate()**                |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| **filter()** {{% req " \*" %}} |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| **fill()**                     |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| **first()**                    |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| **last()**                     |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| **max()**                      |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| **mean()**                     |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| **min()**                      |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| **range()**                    |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| **rename()**                   |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| **sum()**                      |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| **window()**                   |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| _Function combinations_        |                                            |                      |
+| **group()** \|> **count()**    |                                            | {{< icon "check" >}} |
+| **group()** \|> **first()**    |                                            | {{< icon "check" >}} |
+| **group()** \|> **last()**     |                                            | {{< icon "check" >}} |
+| **group()** \|> **max()**      |                                            | {{< icon "check" >}} |
+| **group()** \|> **min()**      |                                            | {{< icon "check" >}} |
+| **group()** \|> **sum()**      |                                            | {{< icon "check" >}} |
+| **sort()** \|> **limit()**     |                                            | {{< icon "check" >}} |
+| **window()** \|> **count()**   |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| **window()** \|> **first()**   |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| **window()** \|> **last()**    |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| **window()** \|> **max()**     |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| **window()** \|> **min()**     |            {{< icon "check" >}}            | {{< icon "check" >}} |
+| **window()** \|> **sum()**     |            {{< icon "check" >}}            | {{< icon "check" >}} |
+
+{{% caption %}}
+{{< req "\*" >}} **filter()** only pushes down when all parameter values are static.
+See [Avoid processing filters inline](#avoid-processing-filters-inline).
+{{% /caption %}}
+
+Use pushdown functions and function combinations at the beginning of your query.
+Once a non-pushdown function runs, Flux pulls data into memory and runs all
+subsequent operations there.
+
+##### Pushdown functions in use
+```js
+from(bucket: "example-bucket")
+    |> range(start: -1h)                       //
+    |> filter(fn: (r) => r.sensor == "abc123") //
+    |> group(columns: ["_field", "host"])      // Pushed to the data source
+    |> aggregateWindow(every: 5m, fn: max)     //
+    |> filter(fn: (r) => r._value >= 90.0)     //
+
+    |> top(n: 10)                              // Run in memory
+```
+
+### Avoid processing filters inline
+Avoid using mathematic operations or string manipulation inline to define data filters.
+Processing filter values inline prevents `filter()` from pushing its operation down
+to the underlying data source, so data returned by the
+previous function loads into memory.
+This often results in a significant performance hit.
+
+For example, the following query uses [dashboard variables](/influxdb/v2.2/visualize-data/variables/)
+and string concatenation to define a region to filter by.
+Because `filter()` uses string concatenation inline, it can't push its operation
+to the underlying data source and loads all data returned from `range()` into memory.
+
+```js
+from(bucket: "example-bucket")
+    |> range(start: -1h)                      
+    |> filter(fn: (r) => r.region == v.provider + v.region)
+```
+
+To dynamically set filters and maintain the pushdown ability of the `filter()` function,
+use variables to define filter values outside of `filter()`:
+
+```js
+region = v.provider + v.region
+
+from(bucket: "example-bucket")
+    |> range(start: -1h)                      
+    |> filter(fn: (r) => r.region == region)
+```
+
+## Avoid short window durations
+Windowing (grouping data based on time intervals) is commonly used to aggregate and downsample data.
+Increase performance by avoiding short window durations.
+More windows require more compute power to evaluate which window each row should be assigned to.
+Reasonable window durations depend on the total time range queried.
+
+## Use "heavy" functions sparingly
+The following functions use more memory or CPU than others.
+Consider their necessity in your data processing before using them:
+
+- [map()](/{{< latest "flux" >}}/stdlib/universe/map/)
+- [reduce()](/{{< latest "flux" >}}/stdlib/universe/reduce/)
+- [join()](/{{< latest "flux" >}}/stdlib/universe/join/)
+- [union()](/{{< latest "flux" >}}/stdlib/universe/union/)
+- [pivot()](/{{< latest "flux" >}}/stdlib/universe/pivot/)
+
+{{% note %}}
+We're continually optimizing Flux and this list may not represent its current state.
+{{% /note %}}
+
+## Use set() instead of map() when possible
+[`set()`](/{{< latest "flux" >}}/stdlib/universe/set/),
+[`experimental.set()`](/{{< latest "flux" >}}/stdlib/experimental/set/),
+and [`map`](/{{< latest "flux" >}}/stdlib/universe/map/)
+can each set columns value in data, however **set** functions have performance
+advantages over `map()`.
+
+Use the following guidelines to determine which to use:
+
+- If setting a column value to a predefined, static value, use `set()` or `experimental.set()`.
+- If dynamically setting a column value using **existing row data**, use `map()`.
+
+#### Set a column value to a static value
+The following queries are functionally the same, but using `set()` is more performant than using `map()`.
+
+```js
+data
+    |> map(fn: (r) => ({ r with foo: "bar" }))
+
+// Recommended
+data
+    |> set(key: "foo", value: "bar")
+```
+
+#### Dynamically set a column value using existing row data
+```js
+data
+    |> map(fn: (r) => ({ r with foo: r.bar }))
+```
+
+## Balance time range and data precision
+To ensure queries are performant, balance the time range and the precision of your data.
+For example, if you query data stored every second and request six months worth of data,
+results would include ≈15.5 million points per series.  Depending on the number of series returned after `filter()`([cardinality](/influxdb/v2.2/reference/glossary/#series-cardinality)), this can quickly become many billions of points.
+Flux must store these points in memory to generate a response. Use [pushdowns](#pushdown-functions-and-function-combinations) to optimize how many points are stored in memory.
+
+To query data over large periods of time, create a task to [downsample data](/influxdb/v2.2/process-data/common-tasks/downsample-data/), and then query the downsampled data instead.
+
+## Measure query performance with Flux profilers
+Use the [Flux Profiler package](/{{< latest "flux" >}}/stdlib/profiler/)
+to measure query performance and append performance metrics to your query output.
+The following Flux profilers are available:
+
+- **query**: provides statistics about the execution of an entire Flux script.
+- **operator**: provides statistics about each operation in a query.
+
+Import the `profiler` package and enable profilers with the `profile.enabledProfilers` option.
+
+```js
+import "profiler"
+
+option profiler.enabledProfilers = ["query", "operator"]
+
+// Query to profile
+```
+
+For more information about Flux profilers, see the [Flux Profiler package](/{{< latest "flux" >}}/stdlib/profiler/).
diff --git a/content/influxdb/v2.2/reference/_index.md b/content/influxdb/v2.2/reference/_index.md
new file mode 100644
index 000000000..85629285e
--- /dev/null
+++ b/content/influxdb/v2.2/reference/_index.md
@@ -0,0 +1,8 @@
+---
+title: InfluxDB reference
+description: >
+  Reference documentation for InfluxDB including release notes, API documentation,
+  tools, syntaxes, database internals, and more.
+---
+
+{{< children >}}
\ No newline at end of file
diff --git a/content/influxdb/v2.2/reference/api/_index.md b/content/influxdb/v2.2/reference/api/_index.md
new file mode 100644
index 000000000..c343efb50
--- /dev/null
+++ b/content/influxdb/v2.2/reference/api/_index.md
@@ -0,0 +1,30 @@
+---
+title: InfluxDB v2 API
+description: >
+  The InfluxDB v2 API provides a programmatic interface for interactions with InfluxDB.
+  Access the InfluxDB API using the `/api/v2/` endpoint.
+menu: influxdb_2_2_ref
+weight: 3
+influxdb/v2.2/tags: [api]
+aliases:
+  - /influxdb/v2.2/concepts/api/
+---
+
+The InfluxDB v2 API provides a programmatic interface for interactions with InfluxDB.
+Access the InfluxDB API using the `/api/v2/` endpoint.
+
+## InfluxDB v2 API documentation
+<a class="btn" href="/influxdb/v2.2/api/">InfluxDB OSS {{< current-version >}} API documentation</a>
+
+#### View InfluxDB API documentation locally
+InfluxDB API documentation is built into the `influxd` service and represents
+the API specific to the current version of InfluxDB.
+To view the API documentation locally, [start InfluxDB](/influxdb/v2.2/get-started/#start-influxdb)
+and visit the `/docs` endpoint in a browser ([localhost:8086/docs](http://localhost:8086/docs)).
+
+## InfluxDB v1 compatibility API documentation
+The InfluxDB v2 API includes [InfluxDB 1.x compatibility endpoints](/influxdb/v2.2/reference/api/influxdb-1x/)
+that work with InfluxDB 1.x client libraries and third-party integrations like
+[Grafana](https://grafana.com) and others.
+
+<a class="btn" href="/influxdb/v2.2/api/v1-compatibility/">View full v1 compatibility API documentation</a>
diff --git a/content/influxdb/v2.2/reference/api/influxdb-1x/_index.md b/content/influxdb/v2.2/reference/api/influxdb-1x/_index.md
new file mode 100644
index 000000000..88fe728f9
--- /dev/null
+++ b/content/influxdb/v2.2/reference/api/influxdb-1x/_index.md
@@ -0,0 +1,268 @@
+---
+title: InfluxDB 1.x compatibility API
+description: >
+  The InfluxDB v2 API includes InfluxDB 1.x compatibility endpoints that work with
+  InfluxDB 1.x client libraries and third-party integrations like [Grafana](https://grafana.com) and others.
+menu:
+  influxdb_2_2_ref:
+    name: 1.x compatibility
+    parent: InfluxDB v2 API
+weight: 104
+influxdb/v2.2/tags: [influxql, query, write]
+related:
+  - /influxdb/v2.2/query-data/influxql
+  - /influxdb/v2.2/upgrade/v1-to-v2/
+---
+
+The InfluxDB v2 API includes InfluxDB 1.x compatibility endpoints that work with
+InfluxDB 1.x client libraries and third-party integrations like [Grafana](https://grafana.com) and others.
+
+<a class="btn" href="/influxdb/v2.2/api/v1-compatibility/">View full v1 compatibility API documentation</a>
+
+## Authentication
+
+InfluxDB 1.x compatibility endpoints require all query and write requests to be authenticated with an
+[API token](/influxdb/v2.2/security/tokens/) or 1.x-compatible
+credentials.
+
+* [Authenticate with the Token scheme](#authenticate-with-the-token-scheme)
+* [Authenticate with a 1.x username and password scheme](#authenticate-with-a-username-and-password-scheme)
+
+### Authenticate with the Token scheme
+Token authentication requires the following credential:
+
+- **token**: InfluxDB [API token](/influxdb/v2.2/security/tokens/)
+
+Use the `Authorization` header with the `Token` scheme to provide your token to InfluxDB.
+
+#### Syntax
+
+```sh
+Authorization: Token INFLUX_API_TOKEN
+```
+
+#### Example
+
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[curl](#curl)
+[Node.js](#nodejs)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```sh
+{{% get-shared-text "api/v1-compat/auth/oss/token-auth.sh" %}}
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```js
+{{% get-shared-text "api/v1-compat/auth/oss/token-auth.js" %}}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+### Authenticate with a username and password scheme
+
+Use the following authentication schemes with clients that support the InfluxDB 1.x convention of `username` and `password` (that don't support the `Authorization: Token` scheme):
+
+- [Basic authentication](#basic-authentication)
+- [Query string authentication](#query-string-authentication)
+
+#### Manage credentials
+
+{{% oss-only %}}
+
+Username and password schemes require the following credentials:
+- **username**: 1.x username (this is separate from the UI login username)
+- **password**: 1.x password or InfluxDB API token.
+
+{{% note %}}
+#### Password or Token
+If you have [set a password](/influxdb/v2.2/upgrade/v1-to-v2/manual-upgrade/#1x-compatible-authorizations) for the 1.x-compatible username, provide the 1.x-compatible password.
+If you haven't set a password for the 1.x-compatible username, provide the InfluxDB [authentication token](/influxdb/v2.2/security/tokens/) as the password.
+{{% /note %}}
+
+For information about creating and managing 1.x-compatible authorizations, see:
+
+- [`influx v1 auth` command](/influxdb/v2.2/reference/cli/influx/v1/auth/)
+- [Manually upgrade – 1.x-compatible authorizations](/influxdb/v2.2/upgrade/v1-to-v2/manual-upgrade/#1x-compatible-authorizations)
+
+{{% /oss-only %}}
+
+{{% cloud-only %}}
+
+- **username**: InfluxDB Cloud username
+  (Use the email address you signed up with as your username, _e.g._ `exampleuser@influxdata.com`.)
+- **password**: InfluxDB Cloud [API token](/influxdb/cloud/security/tokens/)
+
+{{% /cloud-only %}}
+
+#### Basic authentication
+
+Use the `Authorization` header with the `Basic` scheme to provide username and
+password credentials to InfluxDB.
+
+{{% api/v1-compat/basic-auth-syntax %}}
+
+##### Syntax
+
+{{% oss-only %}}
+
+```sh
+Authorization: Basic INFLUX_USERNAME:INFLUX_PASSWORD_OR_TOKEN
+```
+
+{{% /oss-only %}}
+
+
+{{% cloud-only %}}
+
+```sh
+Authorization: Basic exampleuser@influxdata.com:INFLUX_API_TOKEN
+```
+
+{{% /cloud-only %}}
+
+##### Example
+
+{{% oss-only %}}
+
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[curl](#curl)
+[Node.js](#nodejs)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```sh
+{{% get-shared-text "api/v1-compat/auth/oss/basic-auth.sh" %}}
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```js
+{{% get-shared-text "api/v1-compat/auth/oss/basic-auth.js" %}}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+{{% /oss-only %}}
+
+
+{{% cloud-only %}}
+
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[curl](#curl)
+[Node.js](#nodejs)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```sh
+{{% get-shared-text "api/v1-compat/auth/cloud/basic-auth.sh" %}}
+```
+{{% /code-tab-content %}}
+
+{{% code-tab-content %}}
+```js
+{{% get-shared-text "api/v1-compat/auth/cloud/basic-auth.js" %}}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+Replace the following:
+- *`exampleuser@influxdata.com`*: the email address that you signed up with
+- *`INFLUX_API_TOKEN`*: your [InfluxDB API token](/influxdb/cloud/reference/glossary/#token)
+
+{{% /cloud-only %}}
+
+#### Query string authentication
+Use InfluxDB 1.x API parameters to provide credentials through the query string.
+
+{{% note %}}
+##### Consider when using query string parameters
+
+- URL-encode query parameters that may contain whitespace or other special characters.
+- Be aware of the [risks](https://owasp.org/www-community/vulnerabilities/Information_exposure_through_query_strings_in_url) when exposing sensitive data through URLs.
+{{% /note %}}
+
+##### Syntax
+
+{{% oss-only %}}
+
+```sh
+ /query/?u=INFLUX_USERNAME&p=INFLUX_PASSWORD_OR_TOKEN
+ /write/?u=INFLUX_USERNAME&p=INFLUX_PASSWORD_OR_TOKEN
+ ```
+
+{{% /oss-only %}}
+
+{{% cloud-only %}}
+
+```sh
+/query/?u=INFLUX_USERNAME&p=INFLUX_API_TOKEN
+/write/?u=INFLUX_USERNAME&p=INFLUX_API_TOKEN
+```
+
+{{% /cloud-only %}}
+
+##### Example
+
+{{% oss-only %}}
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[curl](#curl)
+[Node.js](#nodejs)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```sh
+{{< get-shared-text "api/v1-compat/auth/oss/querystring-auth.sh" >}}
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```js
+{{< get-shared-text "api/v1-compat/auth/oss/querystring-auth.js" >}}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+Replace the following:
+- *`INFLUX_USERNAME`*: [InfluxDB 1.x username](#manage-credentials)
+- *`INFLUX_PASSWORD_OR_TOKEN`*: [InfluxDB 1.x password or InfluxDB API token](#manage-credentials)
+
+{{% /oss-only %}}
+
+{{% cloud-only %}}
+
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[curl](#curl)
+[Node.js](#nodejs)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```sh
+{{% get-shared-text "api/v1-compat/auth/cloud/basic-auth.sh" %}}
+```
+{{% /code-tab-content %}}
+
+{{% code-tab-content %}}
+```js
+{{% get-shared-text "api/v1-compat/auth/cloud/basic-auth.js" %}}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+Replace the following:
+- *`exampleuser@influxdata.com`*: the email address that you signed up with
+- *`INFLUX_API_TOKEN`*: your [InfluxDB API token](/influxdb/cloud/reference/glossary/#token)
+
+{{% /cloud-only %}}
+
+##### InfluxQL support
+
+The compatibility API supports InfluxQL, with the following caveats:
+
+- The `INTO` clause (e.g. `SELECT ... INTO ...`) is not supported.
+- With the exception of [`DELETE`](/{{< latest "influxdb" "v1" >}}/query_language/manage-database/#delete-series-with-delete) and
+  [`DROP MEASUREMENT`](/{{< latest "influxdb" "v1" >}}/query_language/manage-database/#delete-measurements-with-drop-measurement) queries, which are still allowed,
+  InfluxQL database management commands are not supported.
+
+## Compatibility endpoints
+
+{{< children readmore=true >}}
diff --git a/content/influxdb/v2.2/reference/api/influxdb-1x/dbrp.md b/content/influxdb/v2.2/reference/api/influxdb-1x/dbrp.md
new file mode 100644
index 000000000..e4f21adad
--- /dev/null
+++ b/content/influxdb/v2.2/reference/api/influxdb-1x/dbrp.md
@@ -0,0 +1,74 @@
+---
+title: Database and retention policy mapping
+description: >
+  The database and retention policy (DBRP) mapping service maps InfluxDB 1.x
+  database and retention policy combinations to InfluxDB Cloud and InfluxDB OSS 2.x buckets.
+menu:
+  influxdb_2_2_ref:
+    name: DBRP mapping
+    parent: 1.x compatibility
+weight: 302
+related:
+  - /influxdb/v2.2/reference/api/influxdb-1x/query
+  - /influxdb/v2.2/reference/api/influxdb-1x/write
+  - /influxdb/v2.2/api/#tag/DBRPs, InfluxDB v2 API /dbrps endpoint
+---
+
+The InfluxDB 1.x data model includes [databases](/influxdb/v1.8/concepts/glossary/#database)
+and [retention policies](/influxdb/v1.8/concepts/glossary/#retention-policy-rp).
+InfluxDB Cloud and InfluxDB OSS {{< current-version >}} replace databases and retention policies with [buckets](/influxdb/v2.2/reference/glossary/#bucket).
+To support InfluxDB 1.x query and write patterns in InfluxDB OSS {{< current-version >}} and Cloud, databases and retention
+policies are mapped to buckets using the **database and retention policy (DBRP) mapping service**.
+
+The DBRP mapping service uses the **database** and **retention policy** specified in
+[1.x compatibility API](/influxdb/v2.2/reference/api/influxdb-1x/) requests to route operations to a bucket.
+
+{{% note %}}
+To query data in InfluxQL that was written using the 2.x `/write` API,
+you must **manually create a DBRP mapping** to map a bucket to a database and retention policy.
+For more information, see [Map unmapped buckets](/influxdb/v2.2/query-data/influxql/#map-unmapped-buckets).
+{{% /note %}}
+
+### Default retention policies
+
+A database can have multiple retention policies with one set as default.
+If no retention policy is specified in a query or write request, InfluxDB uses
+the default retention policy for the specified database.
+
+### When writing data
+
+When writing data using the
+[`/write` compatibility endpoint](/influxdb/v2.2/reference/api/influxdb-1x/write/),
+the DBRP mapping service checks for a bucket mapped to the database and retention policy:
+
+{{% oss-only %}}
+
+- If a mapped bucket is found, data is written to the bucket.
+- If the bucket is unmapped, InfluxDB returns an error.
+  See how to [Map unmapped buckets](/influxdb/v2.2/query-data/influxql/#map-unmapped-buckets).
+
+{{% /oss-only %}}
+
+{{% cloud-only %}}
+
+- If a mapped bucket is found, data is written to the bucket.
+- If an unmapped bucket with a name matching:
+    - **database/retention policy** exists, a DBRP mapping is added to the bucket,
+      and data is written to the bucket.
+    - **database** exists (without a specified retention policy), the default
+      database retention policy is used, a DBRP mapping is added to the bucket,
+      and data is written to the bucket.
+
+{{% /cloud-only %}}
+
+### When querying data
+
+When querying data from InfluxDB Cloud and InfluxDB OSS {{< current-version >}} using the
+[`/query` compatibility endpoint](/influxdb/v2.2/reference/api/influxdb-1x/query/),
+the DBRP mapping service checks for the specified database and retention policy
+(if no retention policy is specified, the database's default retention policy is used):
+
+- If a mapped bucket exists, data is queried from the mapped bucket.
+- If no mapped bucket exists, InfluxDB returns an error. See how to [Map unmapped buckets](/influxdb/v2.2/query-data/influxql/#map-unmapped-buckets).
+
+_For more information on the DBRP mapping API, see the [`/api/v2/dbrps` endpoint documentation](/influxdb/v2.2/api/#tag/DBRPs)._
diff --git a/content/influxdb/v2.2/reference/api/influxdb-1x/query.md b/content/influxdb/v2.2/reference/api/influxdb-1x/query.md
new file mode 100644
index 000000000..a3b294be0
--- /dev/null
+++ b/content/influxdb/v2.2/reference/api/influxdb-1x/query.md
@@ -0,0 +1,173 @@
+---
+title: /query 1.x compatibility API
+list_title: /query
+description: >
+  The `/query` 1.x compatibility endpoint queries InfluxDB Cloud and InfluxDB OSS 2.x using **InfluxQL**.
+menu:
+  influxdb_2_2_ref:
+    name: /query
+    parent: 1.x compatibility
+weight: 301
+influxdb/v2.2/tags: [influxql, query]
+list_code_example: |
+  <pre>
+  <span class="api get">GET</span> http://localhost:8086/query
+  </pre>
+related:
+  - /influxdb/v2.2/query-data/influxql
+---
+
+The `/query` 1.x compatibility endpoint queries InfluxDB Cloud and InfluxDB OSS {{< current-version >}} using **InfluxQL**.
+Use the `GET` request method to query data from the `/query` endpoint.
+
+<pre>
+<span class="api get">GET</span> http://localhost:8086/query
+</pre>
+
+The `/query` compatibility endpoint uses the **database** and **retention policy**
+specified in the query request to map the request to an InfluxDB bucket.
+For more information, see [Database and retention policy mapping](/influxdb/v2.2/reference/api/influxdb-1x/dbrp).
+
+{{% note %}}
+If you have an existing bucket that doesn't follow the **database/retention-policy** naming convention,
+you **must** [manually create a database and retention policy mapping](/influxdb/v2.2/query-data/influxql/#map-unmapped-buckets)
+to query that bucket with the `/query` compatibility API.
+{{% /note %}}
+
+## Authentication
+
+Use one of the following authentication methods:
+* **token authentication**
+* **basic authentication with username and password**
+* **query string authentication with username and password**
+
+_For more information, see [Authentication](/influxdb/v2.2/reference/api/influxdb-1x/#authentication)._
+
+## Query string parameters
+
+### u
+(Optional) The 1.x **username** to authenticate the request.
+_See [query string authentication](/influxdb/v2.2/reference/api/influxdb-1x/#query-string-authentication)._
+
+### p
+(Optional) The 1.x **password** to authenticate the request.
+_See [query string authentication](/influxdb/v2.2/reference/api/influxdb-1x/#query-string-authentication)._
+
+### db
+({{< req >}}) The **database** to query data from.
+This is mapped to an InfluxDB [bucket](/influxdb/v2.2/reference/glossary/#bucket).
+_See [Database and retention policy mapping](/influxdb/v2.2/reference/api/influxdb-1x/dbrp/)._
+
+### rp
+The **retention policy** to query data from.
+This is mapped to an InfluxDB [bucket](/influxdb/v2.2/reference/glossary/#bucket).
+_See [Database and retention policy mapping](/influxdb/v2.2/reference/api/influxdb-1x/dbrp/)._
+
+### q
+({{< req >}}) The **InfluxQL** query to execute.
+To execute multiple queries, delimit queries with a semicolon (`;`).
+
+### epoch
+Return results with [Unix timestamps](/influxdb/v2.2/reference/glossary/#unix-timestamp)
+(also known as epoch timestamps) in the specified precision instead of
+[RFC3339 timestamps](/influxdb/v2.2/reference/glossary/#rfc3339-timestamp) with nanosecond precision.
+The following precisions are available:
+
+- `ns` - nanoseconds
+- `u` or `µ` - microseconds
+- `ms` - milliseconds
+- `s` - seconds
+- `m` - minutes
+- `h` - hours
+
+## Query examples
+
+- [Query using basic authentication](#query-using-basic-authentication)
+- [Query a non-default retention policy](#query-a-non-default-retention-policy)
+- [Execute multiple queries](#execute-multiple-queries)
+- [Return query results with millisecond Unix timestamps](#return-query-results-with-millisecond-unix-timestamps)
+- [Execute InfluxQL queries from a file](#execute-influxql-queries-from-a-file)
+
+##### Query using basic authentication
+
+{{% oss-only %}}
+
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[curl](#curl)
+[Node.js](#nodejs)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```sh
+{{% get-shared-text "api/v1-compat/auth/oss/basic-auth.sh" %}}
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```js
+{{% get-shared-text "api/v1-compat/auth/oss/basic-auth.js" %}}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+{{% /oss-only %}}
+
+{{% cloud-only %}}
+
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[curl](#curl)
+[Node.js](#nodejs)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```sh
+{{% get-shared-text "api/v1-compat/auth/cloud/basic-auth.sh" %}}
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```js
+{{% get-shared-text "api/v1-compat/auth/cloud/basic-auth.js" %}}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+
+{{% /cloud-only %}}
+
+##### Query a non-default retention policy
+```sh
+curl --get http://localhost:8086/query \
+  --header "Authorization: Token INFLUX_API_TOKEN" \
+  --data-urlencode "db=mydb" \
+  --data-urlencode "rp=customrp" \
+  --data-urlencode "q=SELECT used_percent FROM mem WHERE host=host1"
+```
+
+##### Execute multiple queries
+```sh
+curl --get http://localhost:8086/query \
+  --header "Authorization: Token INFLUX_API_TOKEN" \
+  --data-urlencode "db=mydb" \
+  --data-urlencode "q=SELECT * FROM mem WHERE host=host1;SELECT mean(used_percent) FROM mem WHERE host=host1 GROUP BY time(10m)"
+```
+
+##### Return query results with millisecond Unix timestamps
+```sh
+curl --get http://localhost:8086/query \
+  --header "Authorization: Token INFLUX_API_TOKEN" \
+  --data-urlencode "db=mydb" \
+  --data-urlencode "rp=myrp" \
+  --data-urlencode "q=SELECT used_percent FROM mem WHERE host=host1" \
+  --data-urlencode "epoch=ms"
+```
+
+##### Execute InfluxQL queries from a file
+```sh
+curl --get http://localhost:8086/query \
+  --header "Authorization: Token INFLUX_API_TOKEN" \
+  --data-urlencode "db=mydb" \
+  --form "q=@path/to/influxql.txt" \
+  --form "async=true"
+```
+
+Replace the following:
+- *`INFLUX_API_TOKEN`*: InfluxDB API token
diff --git a/content/influxdb/v2.2/reference/api/influxdb-1x/write.md b/content/influxdb/v2.2/reference/api/influxdb-1x/write.md
new file mode 100644
index 000000000..cf935593a
--- /dev/null
+++ b/content/influxdb/v2.2/reference/api/influxdb-1x/write.md
@@ -0,0 +1,194 @@
+---
+title: /write 1.x compatibility API
+list_title: /write
+description: >
+  The `/write` 1.x compatibility endpoint writes data to InfluxDB Cloud and
+  InfluxDB OSS 2.x using patterns from the InfluxDB 1.x `/write` API endpoint.
+menu:
+  influxdb_2_2_ref:
+    name: /write
+    parent: 1.x compatibility
+weight: 301
+influxdb/v2.2/tags: [write]
+list_code_example: |
+  <pre>
+  <span class="api post">POST</span> http://localhost:8086/write
+  </pre>
+related:
+  - /influxdb/v2.2/reference/syntax/line-protocol
+---
+
+The `/write` 1.x compatibility endpoint writes data to InfluxDB Cloud and InfluxDB OSS {{< current-version >}}
+using patterns from the InfluxDB 1.x `/write` API endpoint.
+Use the `POST` request method to write [line protocol](/influxdb/v2.2/reference/syntax/line-protocol/)
+to the `/write` endpoint.
+
+<pre>
+<span class="api post">POST</span> http://localhost:8086/write
+</pre>
+
+{{% note %}}
+If you have an existing bucket that doesn't follow the **database/retention-policy** naming convention,
+you **must** [manually create a database and retention policy mapping](/influxdb/v2.2/query-data/influxql/#map-unmapped-buckets)
+to write data to that bucket with the `/write` compatibility API.
+{{% /note %}}
+
+## Authentication
+
+{{% oss-only %}}
+
+Use one of the following authentication methods:
+* **token authentication**
+* **basic authentication with username and password**
+* **query string authentication with username and password**
+
+_For more information, see [Authentication](/influxdb/v2.2/reference/api/influxdb-1x/#authentication)._
+
+{{% /oss-only %}}
+
+{{% cloud-only %}}
+
+{{% api/v1-compat/cloud/authentication %}}
+
+{{% /cloud-only %}}
+
+## Request body
+Include your line protocol in the request body.
+**Binary encode** the line protocol to prevent unintended formatting.
+The examples [below](#write-examples) use the curl `--data-binary` flag to binary
+encode the line protocol.
+
+## Query string parameters
+
+{{% oss-only %}}
+
+### u
+(Optional) The 1.x **username** to authenticate the request.
+_See [query string authentication](/influxdb/v2.2/reference/api/influxdb-1x/#query-string-authentication)._
+
+### p
+(Optional) The 1.x **password** to authenticate the request.
+_See [query string authentication](/influxdb/v2.2/reference/api/influxdb-1x/#query-string-authentication)._
+
+{{% /oss-only %}}
+
+{{% cloud-only %}}
+
+### u
+(Optional) The InfluxDB Cloud **username** to authenticate the request.
+_See [query string authentication](/influxdb/cloud/reference/api/influxdb-1x/#query-string-authentication)._
+
+### p
+(Optional) The InfluxDB Cloud **API token** to authenticate the request.
+_See [query string authentication](/influxdb/cloud/reference/api/influxdb-1x/#query-string-authentication)._
+
+{{% /cloud-only %}}
+
+### db
+({{< req >}}) The **database** to write data to.
+This is mapped to an InfluxDB [bucket](/influxdb/v2.2/reference/glossary/#bucket).
+_See [Database and retention policy mapping](/influxdb/v2.2/reference/api/influxdb-1x/dbrp/)._
+
+### rp
+The **retention policy** to write data to.
+This is mapped to an InfluxDB [bucket](/influxdb/v2.2/reference/glossary/#bucket).
+_See [Database and retention policy mapping](/influxdb/v2.2/reference/api/influxdb-1x/dbrp/)._
+
+### precision
+The precision of [Unix timestamps](/influxdb/v2.2/reference/glossary/#unix-timestamp) in the line protocol.
+Default is nanosconds (`ns`).
+The following precisions are available:
+
+- `ns` - nanoseconds
+- `u` or `µ` - microseconds
+- `ms` - milliseconds
+- `s` - seconds
+- `m` - minutes
+- `h` - hours
+
+## Write examples
+
+- [Write data using basic authentication](#write-data-using-basic-authentication)
+- [Write data to a non-default retention policy](#write-data-to-a-non-default-retention-policy)
+- [Write multiple lines of line protocol](#write-multiple-lines-of-line-protocol)
+- [Write data with millisecond Unix timestamps](#write-data-with-millisecond-unix-timestamps)
+- [Use curl to write data from a file](#use-curl-to-write-data-from-a-file)
+
+##### Write data using basic authentication
+
+{{% oss-only %}}
+
+```sh
+curl --request POST http://localhost:8086/write?db=mydb \
+  --user "INFLUX_USERNAME:INFLUX_PASSWORD_OR_TOKEN" \
+  --data-binary "measurement,host=host1 field1=2i,field2=2.0 1577836800000000000"
+```
+
+{{% /oss-only %}}
+
+{{% cloud-only %}}
+
+```sh
+curl --request POST https://cloud2.influxdata.com/write?db=mydb \
+  --user "exampleuser@influxdata.com:INFLUX_API_TOKEN" \
+  --data-binary "measurement,host=host1 field1=2i,field2=2.0 1577836800000000000"
+```
+
+{{% /cloud-only %}}
+
+##### Write data using token authentication
+```sh
+curl --request POST http://localhost:8086/write?db=mydb \
+  --header "Authorization: Token INFLUX_API_TOKEN" \
+  --data-binary "measurement,host=host1 field1=2i,field2=2.0 1577836800000000000"
+```
+
+##### Write data to a non-default retention policy
+
+```sh
+curl --request POST http://localhost:8086/write?db=mydb&rp=customrp \
+  --header "Authorization: Token INFLUX_API_TOKEN" \
+  --data-binary "measurement,host=host1 field1=2i,field2=2.0 1577836800000000000"
+```
+
+
+
+##### Write multiple lines of line protocol
+```sh
+curl --request POST http://localhost:8086/write?db=mydb \
+  --header "Authorization: Token INFLUX_API_TOKEN" \
+  --data-binary "measurement,host=host1 field1=2i,field2=2.0 1577836800000000000
+measurement,host=host2 field1=14i,field2=12.7 1577836800000000000
+measurement,host=host3 field1=5i,field2=6.8 1577836800000000000"
+```
+
+##### Write data with millisecond Unix timestamps
+```sh
+curl --request POST http://localhost:8086/write?db=mydb&precision=ms \
+  --header "Authorization: Token INFLUX_API_TOKEN" \
+  --data-binary "measurement,host=host1 field1=2i,field2=2.0 1577836800000"
+```
+
+##### Use curl to write data from a file
+```sh
+curl --request POST http://localhost:8086/write?db=mydb \
+  --header "Authorization: Token INFLUX_API_TOKEN" \
+  --data-binary @path/to/line-protocol.txt
+```
+
+{{% oss-only %}}
+
+Replace the following:
+- *`INFLUX_USERNAME`*: [InfluxDB 1.x username](/influxdb/v2.2/reference/api/influxdb-1x/#manage-credentials)
+- *`INFLUX_PASSWORD_OR_TOKEN`*: [InfluxDB 1.x password or InfluxDB API token](/influxdb/v2.2/reference/api/influxdb-1x/#manage-credentials)
+- *`INFLUX_API_TOKEN`*: your [InfluxDB API token](/influxdb/v2.2/reference/glossary/#token)
+
+{{% /oss-only %}}
+
+{{% cloud-only %}}
+
+Replace the following:
+- *`exampleuser@influxdata.com`*: the email address that you signed up with
+- *`INFLUX_API_TOKEN`*: your [InfluxDB API token](/influxdb/cloud/reference/glossary/#token)
+
+{{% /cloud-only %}}
diff --git a/content/influxdb/v2.2/reference/cli/_index.md b/content/influxdb/v2.2/reference/cli/_index.md
new file mode 100644
index 000000000..3e64c4e92
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/_index.md
@@ -0,0 +1,18 @@
+---
+title: Command line tools
+seotitle: Command line tools for managing InfluxDB
+description: >
+  InfluxDB provides command line tools designed to aid in managing and working
+  with InfluxDB from the command line.
+influxdb/v2.2/tags: [cli]
+menu:
+  influxdb_2_2_ref:
+    name: Command line tools
+weight: 4
+---
+
+InfluxDB provides command line tools designed to aid in managing and working
+with InfluxDB from the command line.
+The following command line interfaces (CLIs) are available:
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/reference/cli/influx/_index.md b/content/influxdb/v2.2/reference/cli/influx/_index.md
new file mode 100644
index 000000000..51d7cd18f
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/_index.md
@@ -0,0 +1,133 @@
+---
+title: influx - InfluxDB command line interface
+seotitle: influx - InfluxDB command line interface
+description: >
+  The `influx` CLI includes commands to manage many aspects of InfluxDB,
+  including buckets, organizations, users, tasks, etc.
+menu:
+  influxdb_2_2_ref:
+    name: influx
+    parent: Command line tools
+weight: 101
+influxdb/v2.2/tags: [cli]
+related:
+  - /influxdb/v2.2/tools/influx-cli/
+---
+
+The `influx` command line interface (CLI) includes commands to manage many aspects of InfluxDB,
+including buckets, organizations, users, tasks, etc.
+
+{{% oss-only %}}
+
+{{% note %}}
+#### InfluxDB OSS and influx CLI versions
+Beginning with **InfluxDB 2.1**, the `influx` CLI is packaged and versioned separately
+from InfluxDB.
+InfluxDB and `influx` CLI versions may differ, but compatibility is noted for each command.
+{{% /note %}}
+
+{{% /oss-only %}}
+
+## Download and install the influx CLI
+<a class="btn" href="/influxdb/v2.2/tools/influx-cli/">Download and install the influx CLI</a>
+
+### Provide required authentication credentials
+To avoid having to pass your InfluxDB **host**, **API token**, and **organization**
+with each command, store them in an `influx` CLI configuration (config).
+`influx` commands that require these credentials automatically retrieve these
+credentials from the active config.
+
+Use the [`influx config create` command](/influxdb/v2.2/reference/cli/influx/config/create/)
+to create an `influx` CLI config and set it as active:
+
+```sh
+influx config create --config-name <config-name> \
+  --host-url http://localhost:8086 \
+  --org <your-org> \
+  --token <your-auth-token> \
+  --active
+```
+
+For more information about managing CLI configurations, see the
+[`influx config` documentation](/influxdb/v2.2/reference/cli/influx/config/).
+
+## Usage
+
+```
+influx [flags]
+influx [command]
+```
+
+## Commands
+
+| Command                                                             | Description                                                                |
+| :------------------------------------------------------------------ | :------------------------------------------------------------------------- |
+| [apply](/influxdb/v2.2/reference/cli/influx/apply/)                 | Apply an InfluxDB template                                                 |
+| [auth](/influxdb/v2.2/reference/cli/influx/auth/)                   | API token management commands                                              |
+| [backup](/influxdb/v2.2/reference/cli/influx/backup/)               | Back up data _(InfluxDB OSS only)_                                         |
+| [bucket](/influxdb/v2.2/reference/cli/influx/bucket/)               | Bucket management commands                                                 |
+| [bucket-schema](/influxdb/v2.2/reference/cli/influx/bucket-schema/) | Manage InfluxDB bucket schemas _(InfluxDB Cloud only)_                     |
+| [completion](/influxdb/v2.2/reference/cli/influx/completion/)       | Generate completion scripts                                                |
+| [config](/influxdb/v2.2/reference/cli/influx/config/)               | Configuration management commands                                          |
+| [dashboards](/influxdb/v2.2/reference/cli/influx/dashboards/)       | List dashboards                                                            |
+| [delete](/influxdb/v2.2/reference/cli/influx/delete/)               | Delete points from InfluxDB                                                |
+| [export](/influxdb/v2.2/reference/cli/influx/export/)               | Export resources as a template                                             |
+| [help](/influxdb/v2.2/reference/cli/influx/help/)                   | Help about any command                                                     |
+| [org](/influxdb/v2.2/reference/cli/influx/org/)                     | Organization management commands                                           |
+| [ping](/influxdb/v2.2/reference/cli/influx/ping/)                   | Check the InfluxDB `/health` endpoint                                      |
+| [query](/influxdb/v2.2/reference/cli/influx/query/)                 | Execute a Flux query                                                       |
+| [restore](/influxdb/v2.2/reference/cli/influx/restore/)             | Restore backup data _(InfluxDB OSS only)_                                  |
+| [secret](/influxdb/v2.2/reference/cli/influx/secret/)               | Manage secrets                                                             |
+| [setup](/influxdb/v2.2/reference/cli/influx/setup/)                 | Create default username, password, org, bucket, etc. _(InfluxDB OSS only)_ |
+| [stacks](/influxdb/v2.2/reference/cli/influx/stacks/)               | Manage InfluxDB stacks                                                     |
+| [task](/influxdb/v2.2/reference/cli/influx/task/)                   | Task management commands                                                   |
+| [telegrafs](/influxdb/v2.2/reference/cli/influx/telegrafs/)         | Telegraf configuration management commands                                 |
+| [template](/influxdb/v2.2/reference/cli/influx/template/)           | Summarize and validate an InfluxDB template                                |
+| [user](/influxdb/v2.2/reference/cli/influx/user/)                   | User management commands                                                   |
+| [v1](/influxdb/v2.2/reference/cli/influx/v1/)                       | Work with the v1 compatibility API                                         |
+| [version](/influxdb/v2.2/reference/cli/influx/version/)             | Print the influx CLI version                                               |
+| [write](/influxdb/v2.2/reference/cli/influx/write/)                 | Write points to InfluxDB                                                   |
+
+## Flags
+
+| Flag |          | Description                   |
+|:---- |:---      |:-----------                   |
+| `-h` | `--help` | Help for the `influx` command |
+
+### Flag patterns and conventions
+The `influx` CLI uses the following patterns and conventions:
+
+- [Mapped environment variables](#mapped-environment-variables)
+- [Shorthand and longhand flags](#shorthand-and-longhand-flags)
+- [Flag input types](#flag-input-types)
+
+#### Mapped environment variables
+`influx` CLI flags mapped to environment variables are listed in the **Mapped to** column.
+Mapped flags inherit the value of the environment variable.
+To override environment variables, set the flag explicitly in your command.
+
+#### Shorthand and longhand flags
+Many `influx` CLI flags support both shorthand and longhand forms.
+
+- **shorthand:** a shorthand flag begins with a single hyphen followed by a single letter (for example: `-c`).
+- **longhand:** a longhand flag starts with two hyphens followed by a multi-letter,
+  hyphen-spaced flag name (for example: `--active-config`).
+
+Commands can use both shorthand and longhand flags in a single execution.
+
+#### Flag input types
+`influx` CLI flag input types are listed in each the table of flags for each command.
+Flags support the following input types:
+
+##### string
+Text string, but the flag can be used **only once** per command execution.
+
+##### stringArray
+Single text string, but the flag can be used **multiple times** per command execution.
+
+##### integer
+Sequence of digits representing an integer value.
+
+##### duration
+Length of time represented by an integer and a duration unit
+(`1ns`, `1us`, `1µs`, `1ms`, `1s`, `1m`, `1h`, `1d`, `1w`).
diff --git a/content/influxdb/v2.2/reference/cli/influx/apply/_index.md b/content/influxdb/v2.2/reference/cli/influx/apply/_index.md
new file mode 100644
index 000000000..19d457fea
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/apply/_index.md
@@ -0,0 +1,132 @@
+---
+title: influx apply
+description: The `influx apply` command applies InfluxDB templates.
+menu:
+  influxdb_2_2_ref:
+    name: influx apply
+    parent: influx
+weight: 101
+aliases:
+  - /influxdb/v2.2/reference/cli/influx/pkg/
+influxdb/v2.2/tags: [templates]
+related:
+  - /influxdb/v2.2/reference/cli/influx/#provide-required-authentication-credentials, influx CLI—Provide required authentication credentials
+  - /influxdb/v2.2/reference/cli/influx/#flag-patterns-and-conventions, influx CLI—Flag patterns and conventions
+metadata: [influx CLI 2.0.0+, InfluxDB 2.0.0+]
+---
+
+The `influx apply` command applies InfluxDB templates.
+_For information about finding and using InfluxDB templates, see
+[Use InfluxDB templates](/influxdb/v2.2/influxdb-templates/use/)._
+
+## Usage
+```
+influx apply [flags]
+```
+
+## Flags
+| Flag |                           | Description                                                                                 | Input Type | {{< cli/mapped >}}    |
+|:-----|:--------------------------|:--------------------------------------------------------------------------------------------|:-----------|:----------------------|
+| `-c` | `--active-config`         | CLI configuration to use for command                                                        | string     |                       |
+|      | `--configs-path`          | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`)                       | string     | `INFLUX_CONFIGS_PATH` |
+|      | `--disable-color`         | Disable color in output                                                                     |            |                       |
+|      | `--disable-table-borders` | Disable table borders                                                                       |            |                       |
+| `-e` | `--encoding`              | Encoding of the input stream                                                                | string     |                       |
+|      | `--env-ref`               | Environment references to provide with the template (format: `--env-ref=REF_KEY=REF_VALUE`) | string     |                       |
+| `-f` | `--file`                  | Path to template file (supports HTTP(S) URLs or file paths)                                 | string     |                       |
+|      | `--filter`                | Resources to skip when applying the template (filter by `kind` or `resource`)               | string     |                       |
+|      | `--force`                 | Ignore warnings about destructive changes                                                   |            |                       |
+| `-h` | `--help`                  | Help for the `apply` command                                                                |            |                       |
+|      | `--host`                  | HTTP address of InfluxDB (default `http://localhost:8086`)                                  | string     | `INFLUX_HOST`         |
+|      | `--http-debug`            | Inspect communication with InfluxDB servers.                                                | string     |                       |
+|      | `--json`                  | Output data as JSON                                                                         |            | `INFLUX_OUTPUT_JSON`  |
+| `-o` | `--org`                   | Organization name that owns the bucket (mutually exclusive with `--org-id`)                 | string     | `INFLUX_ORG`          |
+|      | `--org-id`                | Organization ID that owns the bucket (mutually exclusive with `--org`)                      | string     | `INFLUX_ORG_ID`       |
+| `-q` | `--quiet`                 | Disable output printing                                                                     |            |                       |
+| `-R` | `--recurse`               | Recurse through files in the directory specified in `-f`, `--file`                          |            |                       |
+|      | `--secret`                | Secrets to provide with the template (format: `--secret=SECRET_KEY=SECRET_VALUE`)           | string     |                       |
+|      | `--skip-verify`           | Skip TLS certificate verification                                                           |            | `INFLUX_SKIP_VERIFY`  |
+|      | `--stack-id`              | Stack ID to associate when applying the template                                            | string     |                       |
+| `-t` | `--token`                 | API token                                                                                   | string     | `INFLUX_TOKEN`        |
+
+## Examples: how to apply a template or stack
+
+{{< cli/influx-creds-note >}}
+
+- [from a file](#apply-a-template-from-a-file)
+- [from a URL](#apply-a-template-from-a-url)
+- [from a stack that has associated templates](#apply-a-stack-that-has-associated-templates)
+- [a template to a stack](#apply-a-template-to-a-stack)
+- [multiple template files together](#apply-multiple-template-files-together)
+- [a template from stdin](#apply-a-template-from-stdin)
+- [all templates in a directory](#apply-all-templates-in-a-directory)
+- [recursively from a directory](#recursively-apply-templates-from-a-directory)
+- [from multiple sources](#apply-templates-from-multiple-sources)
+- [skip resources](#apply-a-template-but-skip-resources)
+
+##### Apply a template from a file
+```sh
+influx apply --file path/to/template.json
+```
+
+##### Apply a template from a URL
+```sh
+influx apply --file https://raw.githubusercontent.com/influxdata/community-templates/master/docker/docker.yml
+```
+
+##### Apply a stack that has associated templates
+To apply all templates associated with a stack ID to a new stack:
+
+```sh
+influx apply --stack-id $STACK_ID
+```
+
+##### Apply a template to a stack
+```sh
+influx apply --file path/to/template.json --stack-id $STACK_ID
+```
+
+##### Apply multiple template files together
+```sh
+influx apply \
+  --file path/to/template_1.json \
+  --file path/to/template_2.yml
+```
+
+##### Apply a template from stdin
+```sh
+cat template.json | influx apply --encoding json
+```
+
+##### Apply all templates in a directory
+```sh
+influx apply --file path/to/template_directory
+```
+
+##### Recursively apply templates from a directory
+```sh
+influx apply --recurse --file path/to/template_directory
+```
+
+##### Apply templates from multiple sources
+```sh
+influx apply \
+  --file path/to/template.yml
+  --file path/to/templates_directory
+  --file https://example.com/template.json
+```
+
+##### Apply a template, but skip resources
+```sh
+# The following example skips all buckets and the dashboard
+# whose metadata.name field matches "example-dashboard".
+
+# Filter format:
+#	--filter=kind=Bucket
+#	--filter=resource=Label:$Label_TMPL_NAME
+
+influx apply \
+	--file path/to/template.yml \
+	--filter kind=Bucket \
+	--filter resource=Dashboard:example-dashboard
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/auth/_index.md b/content/influxdb/v2.2/reference/cli/influx/auth/_index.md
new file mode 100644
index 000000000..8767d5655
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/auth/_index.md
@@ -0,0 +1,41 @@
+---
+title: influx auth
+description: The `influx auth` command and its subcommands manage API tokens in InfluxDB.
+menu:
+  influxdb_2_2_ref:
+    name: influx auth
+    parent: influx
+weight: 101
+influxdb/v2.2/tags: [authentication]
+cascade:
+  related:
+    - /influxdb/v2.2/reference/cli/influx/#provide-required-authentication-credentials, influx CLI—Provide required authentication credentials
+    - /influxdb/v2.2/reference/cli/influx/#flag-patterns-and-conventions, influx CLI—Flag patterns and conventions
+cascade:
+  metadata: [influx CLI 2.0.0+, InfluxDB 2.0.0+]
+---
+
+The `influx auth` command and its subcommands manage API tokens in InfluxDB.
+
+## Usage
+```
+influx auth [flags]
+influx auth [command]
+```
+
+#### Command aliases
+`auth`, `authorization`
+
+## Subcommands
+| Subcommand                                                    | Description                     |
+|:----------                                                    |:-----------                     |
+| [active](/influxdb/v2.2/reference/cli/influx/auth/active)     | Activate API token   |
+| [create](/influxdb/v2.2/reference/cli/influx/auth/create)     | Create API token     |
+| [delete](/influxdb/v2.2/reference/cli/influx/auth/delete)     | Delete API token     |
+| [list](/influxdb/v2.2/reference/cli/influx/auth/list)         | List API tokens      |
+| [inactive](/influxdb/v2.2/reference/cli/influx/auth/inactive) | Inactivate API token |
+
+## Flags
+| Flag |          | Description                 |
+|:---- |:---      |:-----------                 |
+| `-h` | `--help` | Help for the `auth` command |
diff --git a/content/influxdb/v2.2/reference/cli/influx/auth/active.md b/content/influxdb/v2.2/reference/cli/influx/auth/active.md
new file mode 100644
index 000000000..582fb35fc
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/auth/active.md
@@ -0,0 +1,40 @@
+---
+title: influx auth active
+description: The `influx auth active` command sets an API token to active in InfluxDB.
+menu:
+  influxdb_2_2_ref:
+    name: influx auth active
+    parent: influx auth
+weight: 201
+---
+
+The `influx auth active` command activates an API token.
+Only active tokens authorize access to InfluxDB.
+
+## Usage
+```
+influx auth active [flags]
+```
+
+## Flags
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:----------:|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+| `-h` | `--help`          | Help for the `active` command                                         |            |                       |
+|      | `--hide-headers`  | Hide table headers (default `false`)                                  |            | `INFLUX_HIDE_HEADERS` |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers.                          | string     |                       |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)            | string     | `INFLUX_HOST`         |
+| `-i` | `--id`            | ({{< req >}}) API token ID                                            | string     |                       |
+|      | `--json`          | Output data as JSON (default `false`)                                 |            | `INFLUX_OUTPUT_JSON`  |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`         | API token                                                             | string     | `INFLUX_TOKEN`        |
+
+## Example
+
+{{< cli/influx-creds-note >}}
+
+##### Activate an API token
+```sh
+influx auth active --id 06c86c40a9f36000
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/auth/create.md b/content/influxdb/v2.2/reference/cli/influx/auth/create.md
new file mode 100644
index 000000000..4e08a6b42
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/auth/create.md
@@ -0,0 +1,154 @@
+---
+title: influx auth create
+description: The `influx auth create` command creates an API token in InfluxDB.
+menu:
+  influxdb_2_2_ref:
+    name: influx auth create
+    parent: influx auth
+weight: 201
+updated_in: CLI v2.2.0
+---
+
+The `influx auth create` command creates an API token in InfluxDB.
+
+## Usage
+```
+influx auth create [flags]
+```
+
+## Flags
+| Flag |                                 | Description                                                           | Input type  | {{< cli/mapped >}}    |
+|:-----|:--------------------------------|:----------------------------------------------------------------------|:-----------:|:----------------------|
+| `-c` | `--active-config`               | CLI configuration to use for command                                  | string      |                       |
+|      | `--all-access`                  | Grants all permissions in a single organization                       |             |                       |
+|      | `--configs-path`                | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string      | `INFLUX_CONFIGS_PATH` |
+| `-d` | `--description`                 | API token description                                                 | string      |                       |
+| `-h` | `--help`                        | Help for the `create` command                                         |             |                       |
+|      | `--hide-headers`                | Hide table headers (default `false`)                                  |             | `INFLUX_HIDE_HEADERS` |
+|      | `--host`                        | HTTP address of InfluxDB (default `http://localhost:8086`)            | string      | `INFLUX_HOST`         |
+|      | `--http-debug`                  | Inspect communication with InfluxDB servers                           | string      |                       |
+|      | `--json`                        | Output data as JSON (default `false`)                                 |             | `INFLUX_OUTPUT_JSON`  |
+|      | `--operator`                    | _(InfluxDB OSS only)_ Grants all permissions in all organizations     | string      |                       |
+| `-o` | `--org`                         | Organization name (mutually exclusive with `--org-id`)                | string      | `INFLUX_ORG`          |
+|      | `--org-id`                      | Organization ID (mutually exclusive with `--org`)                     | string      | `INFLUX_ORG_ID`       |
+|      | `--read-bucket`                 | Grant permission to read a specified bucket ID                        | stringArray |                       |
+|      | `--read-buckets`                | Grant permission to read **all** organization buckets                 |             |                       |
+|      | `--read-checks`                 | Grant permission to read checks                                       |             |                       |
+|      | `--read-dashboards`             | Grant permission to read dashboards                                   |             |                       |
+|      | `--read-dbrps`                  | Grant permission to read database retention policy mappings           |             |                       |
+|      | `--read-notificationEndpoints`  | Grant permission to read notificationEndpoints                        |             |                       |
+|      | `--read-notificationRules`      | Grant permission to read notificationRules                            |             |                       |
+|      | `--read-orgs`                   | Grant permission to read organizations                                |             |                       |
+|      | `--read-remotes`                | Grant permission to read remote configurations                        |             |                       |
+|      | `--read-replications`           | Grant permission to read replication configurations                   |             |                       |
+|      | `--read-tasks`                  | Grant permission to read tasks                                        |             |                       |
+|      | `--read-telegrafs`              | Grant permission to read Telegraf configurations                      |             |                       |
+|      | `--read-users`                  | Grant permission to read organization users                           |             |                       |
+|      | `--skip-verify`                 | Skip TLS certificate verification                                     |             | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`                       | API token                                                             | string      | `INFLUX_TOKEN`        |
+| `-u` | `--user`                        | Username                                                              | string      |                       |
+|      | `--write-annotations`           | Grant permission to create annotations                                |             |                       |
+|      | `--write-bucket`                | Grant permission to write to specified a bucket ID                    | stringArray |                       |
+|      | `--write-buckets`               | Grant permission to create and update **all** organization buckets    |             |                       |
+|      | `--write-checks`                | Grant permission to create checks                                     |             |                       |
+|      | `--write-dashboards`            | Grant permission to create and update dashboards                      |             |                       |
+|      | `--write-dbrps`                 | Grant permission to create database retention policy mappings         |             |                       |
+|      | `--write-notificationEndpoints` | Grant permission to create notificationEndpoints                      |             |                       |
+|      | `--write-notificationRules`     | Grant permission to create notificationRules                          |             |                       |
+|      | `--write-orgs`                  | Grant permission to create and update organizations                   |             |                       |
+|      | `--write-remotes`               | Grant permission to create and update remote configurations           |             |                       |
+|      | `--write-replications`          | Grant permission to create and update replication configurations      |             |                       |
+|      | `--write-tasks`                 | Grant permission to create and update tasks                           |             |                       |
+|      | `--write-telegrafs`             | Grant permission to create and update Telegraf configurations         |             |                       |
+|      | `--write-users`                 | Grant permission to create and update organization users              |             |                       |
+|      | `--write-variables`             | Grant permission to create and update variables                       |             |                       |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+- [Create an All-Access API token](#create-an-all-access-api-token) {{% oss-only %}} or [Create an Operator API token](#create-an-operator-api-token){{% /oss-only %}}
+- [Create an API token with specified read and write permissions](#create-an-api-token-with-specified-read-and-write-permissions)
+- [Create a token with read and write access to specific buckets](#create-an-api-token-with-read-and-write-access-to-specific-buckets)
+- [Create a read-only API token](#create-a-read-only-api-token)
+
+### Create an All-Access API token
+
+Create an [All-Access token](/influxdb/cloud/security/tokens/#all-access-token) to grant permissions to all resources in an organization.
+
+```sh
+influx auth create \
+  --all-access 
+```
+
+{{% oss-only %}}
+
+### Create an Operator API token
+
+Create an [Operator token](/influxdb/v2.0/security/tokens/#operator-token) to grant permissions to all resources in all organizations.
+
+```sh
+influx auth create \
+  --operator
+```
+{{% /oss-only %}}
+
+### Create an API token with specified read and write permissions
+
+```sh
+influx auth create \
+  --read-buckets \
+  --read-checks \
+  --read-dashboards \
+  --read-dbrps \
+  --read-notificationEndpoints \
+  --read-notificationRules \
+  --read-orgs \
+  --read-remotes \
+  --read-replications \
+  --read-tasks \
+  --read-telegrafs \
+  --read-users \
+  --write-annotations \
+  --write-buckets \
+  --write-checks \
+  --write-dashboards \
+  --write-dbrps \
+  --write-notificationEndpoints \
+  --write-notificationRules \
+  --write-orgs \
+  --write-remotes \
+  --write-replications \
+  --write-tasks \
+  --write-telegrafs \
+  --write-users \
+  --write-variables
+```
+
+### Create an API token with read and write access to specific buckets
+
+```sh
+influx auth create \
+  --read-bucket 0000000000000001 \
+  --read-bucket 0000000000000002 \
+  --write-bucket 0000000000000001 \
+  --write-bucket 0000000000000002
+```
+
+### Create a read-only API token
+
+```sh
+influx auth create \
+  --read-buckets \
+  --read-checks \
+  --read-dashboards \
+  --read-dbrps \
+  --read-notificationEndpoints \
+  --read-notificationRules \
+  --read-orgs \
+  --read-remotes \
+  --read-replications \
+  --read-tasks \
+  --read-telegrafs \
+  --read-users
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/auth/delete.md b/content/influxdb/v2.2/reference/cli/influx/auth/delete.md
new file mode 100644
index 000000000..79f60f5aa
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/auth/delete.md
@@ -0,0 +1,39 @@
+---
+title: influx auth delete
+description: The `influx auth delete` command deletes an API token from InfluxDB.
+menu:
+  influxdb_2_2_ref:
+    name: influx auth delete
+    parent: influx auth
+weight: 201
+---
+
+The `influx auth delete` command deletes an API token from InfluxDB.
+
+## Usage
+```
+influx auth delete [flags]
+```
+
+## Flags
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:----------:|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+| `-h` | `--help`          | Help for the `delete` command                                         |            |                       |
+|      | `--hide-headers`  | Hide table headers (default `false`)                                  |            | `INFLUX_HIDE_HEADERS` |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)            | string     | `INFLUX_HOST`         |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers.                          | string     |                       |
+| `-i` | `--id`            | ({{< req >}}) API token ID                                            | string     |                       |
+|      | `--json`          | Output data as JSON (default `false`)                                 |            | `INFLUX_OUTPUT_JSON`  |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`         | API token                                                             | string     | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### Delete an API token
+```sh
+influx auth delete --id 06c86c40a9f36000
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/auth/inactive.md b/content/influxdb/v2.2/reference/cli/influx/auth/inactive.md
new file mode 100644
index 000000000..79829ecbf
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/auth/inactive.md
@@ -0,0 +1,47 @@
+---
+title: influx auth inactive
+description: The `influx auth inactive` command inactivates an API token in InfluxDB.
+menu:
+  influxdb_2_2_ref:
+    name: influx auth inactive
+    parent: influx auth
+weight: 201
+---
+
+The `influx auth inactive` command inactivates an API token in InfluxDB.
+Inactive tokens **do not** authorize access to InfluxDB.
+
+To temporarily disable client access to InfluxDB, inactivate the authentication
+token the client is using rather than delete the token.
+If you delete the token, you have to generate a new token and update the client
+with the new token.
+By setting a token to inactive, you can [activate the token](/influxdb/v2.2/reference/cli/influx/auth/active/)
+to grant the client access without having to modify the client.
+
+## Usage
+```
+influx auth inactive [flags]
+```
+
+## Flags
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:----------:|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+| `-h` | `--help`          | Help for the `inactive` command                                       |            |                       |
+|      | `--hide-headers`  | Hide table headers (default `false`)                                  |            | `INFLUX_HIDE_HEADERS` |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)            | string     | `INFLUX_HOST`         |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers.                          | string     |                       |
+| `-i` | `--id`            | ({{< req >}}) API token ID                                            | string     |                       |
+|      | `--json`          | Output data as JSON (default `false`)                                 |            | `INFLUX_OUTPUT_JSON`  |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`         | API token                                                             | string     | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### Inactivate an API token
+```sh
+influx auth inactive --id 06c86c40a9f36000
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/auth/list.md b/content/influxdb/v2.2/reference/cli/influx/auth/list.md
new file mode 100644
index 000000000..7a118b8c3
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/auth/list.md
@@ -0,0 +1,53 @@
+---
+title: influx auth list
+description: The `influx auth list` command lists API tokens in InfluxDB.
+menu:
+  influxdb_2_2_ref:
+    name: influx auth list
+    parent: influx auth
+weight: 201
+aliases:
+  - /influxdb/v2.2/reference/cli/influx/auth/find
+---
+
+The `influx auth list` command lists and searches API tokens in InfluxDB.
+
+## Usage
+```
+influx auth list [flags]
+```
+
+#### Command aliases
+`list`, `ls`, `find`
+
+## Flags
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:----------:|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+| `-h` | `--help`          | Help for the `list` command                                           |            |                       |
+|      | `--hide-headers`  | Hide table headers (default `false`)                                  |            | `INFLUX_HIDE_HEADERS` |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)            | string     | `INFLUX_HOST`         |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers.                          | string     |                       |
+| `-i` | `--id`            | API token ID                                                          | string     |                       |
+|      | `--json`          | Output data as JSON (default `false`)                                 |            | `INFLUX_OUTPUT_JSON`  |
+| `-o` | `--org`           | Organization name (mutually exclusive with `--org-id`)                | string     |                       |
+|      | `--org-id`        | Organization ID (mutually exclusive with `--org`)                     | string     |                       |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`         | API token                                                             | string     | `INFLUX_TOKEN`        |
+| `-u` | `--user`          | Username                                                              | string     |                       |
+|      | `--user-id`       | User ID                                                               | string     |                       |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### List all API tokens
+```sh
+influx auth list
+```
+
+##### List API tokens associated with a user
+```sh
+influx auth list --user username
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/backup/_index.md b/content/influxdb/v2.2/reference/cli/influx/backup/_index.md
new file mode 100644
index 000000000..9d625f02e
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/backup/_index.md
@@ -0,0 +1,66 @@
+---
+title: influx backup
+description: The `influx backup` command backs up data stored in InfluxDB to a specified directory.
+menu:
+  influxdb_2_2_ref:
+    name: influx backup
+    parent: influx
+weight: 101
+influxdb/v2.2/tags: [backup]
+related:
+  - /influxdb/v2.2/backup-restore/backup/
+  - /influxdb/v2.2/reference/cli/influx/restore/
+  - /influxdb/v2.2/reference/cli/influx/#provide-required-authentication-credentials, influx CLI—Provide required authentication credentials
+  - /influxdb/v2.2/reference/cli/influx/#flag-patterns-and-conventions, influx CLI—Flag patterns and conventions
+metadata: [influx CLI 2.0.0+, InfluxDB 2.0.0+]
+updated_in: CLI v2.0.2
+---
+
+The `influx backup` command backs up data stored in InfluxDB to a specified directory.
+
+## Usage
+```
+influx backup [flags] path
+```
+
+## Flags
+
+| Flag |                   | Description                                                                                                | Input type | {{< cli/mapped >}}    |
+|------|-------------------|------------------------------------------------------------------------------------------------------------|------------|-----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                                                       | string     |                       |
+|      | `--bucket-id`     | ID of the bucket to back up from (mutually exclusive with `--bucket`)                                      | string     |                       |
+| `-b` | `--bucket`        | Name of the bucket to back up from (mutually exclusive with `--bucket-id`)                                 | string     |                       |
+|      | `--compression`   | By default, `gzip` argument enables compression on downloaded files. Set to `none` to disable compression. | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`)                                      | string     | `INFLUX_CONFIGS_PATH` |
+| `-h` | `--help`          | Help for the `backup` command                                                                              |            |                       |
+|      | `--hide-headers`  | Hide table headers (default `false`)                                                                       |            | `INFLUX_HIDE_HEADERS` |
+|      | `--host`          | HTTP address of InfluxDB (default: `http://localhost:8086`)                                                | string     | `INFLUX_HOST`         |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers.                                                               | string     |                       |
+|      | `--json`          | Output data as JSON (default `false`)                                                                      |            | `INFLUX_OUTPUT_JSON`  |
+| `-o` | `--org`           | Organization name (mutually exclusive with `--org-id`)                                                     | string     | `INFLUX_ORG`          |
+|      | `--org-id`        | Organization ID (mutually exclusive with `--org`)                                                          | string     | `INFLUX_ORG_ID`       |
+|      | `--skip-verify`   | Skip TLS certificate verification                                                                          | string     | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`         | API token                                                                                                  | string     | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+- [Back up all data to a directory](#back-up-all-data-to-a-directory)
+- [Back up all data to the current working directory](#back-up-all-data-to-the-current-working-directory)
+- [Back up a specific bucket to a directory](#back-up-a-specific-bucket-to-a-directory)
+
+##### Back up all data to a directory
+```sh
+influx backup /path/to/backup/dir/
+```
+
+##### Back up all data to the current working directory
+```sh
+influx backup ./
+```
+
+##### Back up a specific bucket to a directory
+```sh
+influx backup --bucket example-bucket /path/to/backup/dir/
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/bucket-schema/_index.md b/content/influxdb/v2.2/reference/cli/influx/bucket-schema/_index.md
new file mode 100644
index 000000000..6e485afd6
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/bucket-schema/_index.md
@@ -0,0 +1,47 @@
+---
+title: influx bucket-schema
+description: The `influx bucket-schema` command and its subcommands manage schemas of buckets in InfluxDB.
+menu:
+  influxdb_2_2_ref:
+    name: influx bucket-schema
+    parent: influx
+weight: 101
+influxdb/v2.2/tags: [buckets, bucket-schema]
+cascade:
+  related:
+    - /influxdb/cloud/organizations/buckets/bucket-schema
+    - /influxdb/cloud/organizations/buckets/
+    - /influxdb/v2.2/reference/cli/influx/#provide-required-authentication-credentials, influx CLI—Provide required authentication credentials
+    - /influxdb/v2.2/reference/cli/influx/#flag-patterns-and-conventions, influx CLI—Flag patterns and conventions
+  metadata: [influx CLI 2.1.0+, InfluxDB Cloud only]
+  prepend:
+    block: cloud
+    content: |
+      #### Works with InfluxDB Cloud bucket schemas
+      `influx bucket-schema` and its subcommands work with [InfluxDB Cloud bucket schemas](/influxdb/cloud/organizations/buckets/bucket-schema).
+      This feature is not available in InfluxDB OSS v2.2.
+---
+
+The `influx bucket-schema` command and its subcommands manage
+schemas for InfluxDB buckets.
+
+## Usage
+
+```
+influx bucket-schema [flags]
+influx bucket-schema [command]
+```
+
+## Subcommands
+
+| Subcommand                                                         | Description            |
+| :----------------------------------------------------------------- | :--------------------- |
+| [create](/influxdb/v2.2/reference/cli/influx/bucket-schema/create) | Create a bucket schema |
+| [list](/influxdb/v2.2/reference/cli/influx/bucket-schema/list)     | List bucket schemas    |
+| [update](/influxdb/v2.2/reference/cli/influx/bucket-schema/update) | Update a bucket schema |
+
+## Flags
+
+| Flag |          | Description                          |
+| :--- | :------- | :----------------------------------- |
+| `-h` | `--help` | Help for the `bucket-schema` command |
diff --git a/content/influxdb/v2.2/reference/cli/influx/bucket-schema/create.md b/content/influxdb/v2.2/reference/cli/influx/bucket-schema/create.md
new file mode 100644
index 000000000..4729bab14
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/bucket-schema/create.md
@@ -0,0 +1,90 @@
+---
+title: influx bucket-schema create
+description: The `influx bucket-schema create` command sets the schema for a measurement in an InfluxDB bucket that has the `explicit` schema-type.
+menu:
+  influxdb_2_2_ref:
+    name: influx bucket-schema create
+    parent: influx bucket-schema
+weight: 201
+related:
+  - /influxdb/cloud/organizations/buckets/bucket-schema
+---
+
+The `influx bucket-schema create` command sets the schema for a measurement in
+an InfluxDB bucket that has the [`explicit` schema-type](/influxdb/cloud/reference/cli/influx/bucket/create/#create-a-bucket-with-an-explicit-schema).
+
+## Usage
+
+```sh
+influx bucket-schema create [flags]
+```
+
+## Flags
+
+| Flag |                     | Description                                                                                                                                                                         | Input type | {{< cli/mapped >}}    |
+|:-----|:--------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------:|:----------------------|
+| `-c` | `--active-config`   | CLI configuration to use for command                                                                                                                                                | string     |                       |
+| `-n` | `--bucket`          | ({{< req >}}) Bucket name (mutually exclusive with `--bucket-id`)                                                                                                                   | string     |                       |
+| `-i` | `--bucket-id`       | ({{< req >}}) Bucket ID (mutually exclusive with `--bucket`)                                                                                                                        | string     |                       |
+|      | `--columns-file`    | ({{< req >}}) Path to column definitions file. For more information, see [Create a columns file](/influxdb/cloud/reference/cli/influx/bucket-schema/create/#create-a-columns-file). | string     |                       |
+|      | `--columns-format`  | Columns file format (`csv`, `ndjson`, `json`, default: `auto`). For more information, see [Create a schema with columns format](#create-a-schema-with-columns-format)               | string     |                       |
+|      | `--configs-path`    | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`)                                                                                                               | string     | `INFLUX_CONFIGS_PATH` |
+| `-x` | `--extended-output` | Print column information for each measurement schema (default: false)                                                                                                               |            |                       |
+| `-h` | `--help`            | Help for the `create` command                                                                                                                                                       |            |                       |
+|      | `--hide-headers`    | Hide table headers (default `false`)                                                                                                                                                |            | `INFLUX_HIDE_HEADERS` |
+|      | `--host`            | HTTP address of InfluxDB (default `http://localhost:8086`)                                                                                                                          | string     | `INFLUX_HOST`         |
+|      | `--json`            | Output data as JSON (default `false`)                                                                                                                                               |            | `INFLUX_OUTPUT_JSON`  |
+| `-n` | `--name`            | ({{< req >}}) Measurement name                                                                                                                                                      | string     |                       |
+| `-o` | `--org`             | Organization name (mutually exclusive with `--org-id`)                                                                                                                              | string     | `INFLUX_ORG`          |
+|      | `--org-id`          | Organization ID (mutually exclusive with `--org`)                                                                                                                                   | string     | `INFLUX_ORG_ID`       |
+|      | `--skip-verify`     | Skip TLS certificate verification                                                                                                                                                   |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`           | API token                                                                                                                                                                           | string     | `INFLUX_TOKEN`        |
+
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+- [Create a schema using the influx CLI](#create-a-schema-using-the-influx-cli)
+- [Create a schema and print column information](#create-a-schema-and-print-column-information)
+- [Create a schema with columns format](#create-a-schema-with-columns-format)
+
+### Create a schema using the influx CLI
+
+```sh
+influx bucket-schema create \
+  --bucket example-bucket \
+  --name temperature \
+  --columns-file columns.csv
+```
+
+### Create a schema and print column information
+
+```sh
+influx bucket-schema create \
+  --bucket example-bucket \
+  --name cpu \
+  --columns-file columns.csv \
+  --extended-output
+```
+
+### Create a schema with columns format
+
+By default, InfluxDB attempts to detect the **columns file** format.
+If your file's extension doesn't match the format, set the format with the [`columns-format` flag](/influxdb/cloud/reference/cli/influx/bucket-schema/create).
+
+```sh
+influx bucket-schema create \
+  --bucket example-bucket \
+  --name cpu \
+  --columns-file columns.json \
+  --columns-format ndjson
+```
+
+```sh
+influx bucket-schema create \
+  --bucket example-bucket \
+  --name cpu \
+  --columns-file columns.txt \
+  --columns-format csv
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/bucket-schema/list.md b/content/influxdb/v2.2/reference/cli/influx/bucket-schema/list.md
new file mode 100644
index 000000000..3890786ae
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/bucket-schema/list.md
@@ -0,0 +1,59 @@
+---
+title: influx bucket-schema list
+description: The `influx bucket-schema list` command lists the schemas of an InfluxDB bucket that has the `explicit` schema-type.
+menu:
+  influxdb_2_2_ref:
+    name: influx bucket-schema list
+    parent: influx bucket-schema
+weight: 201
+related:
+  - /influxdb/cloud/organizations/buckets/bucket-schema
+---
+
+The `influx bucket-schema list` command lists the schemas of an
+InfluxDB bucket that has the [`explicit` schema-type](/influxdb/cloud/reference/cli/influx/bucket/create/#create-a-bucket-with-an-explicit-schema).
+
+## Usage
+
+```sh
+influx bucket-schema list [flags]
+```
+
+## Flags
+
+| Flag |                     | Description                                                           | Input type | {{< cli/mapped >}}    |
+|:-----|:--------------------|:----------------------------------------------------------------------|:----------:|:----------------------|
+| `-c` | `--active-config`   | CLI configuration to use for command                                  | string     |                       |
+| `-n` | `--bucket`          | Bucket name (mutually exclusive with `--bucket-id`)                   | string     |                       |
+| `-i` | `--bucket-id`       | Bucket ID (mutually exclusive with `--bucket`)                        | string     |                       |
+|      | `--configs-path`    | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+| `-x` | `--extended-output` | Print column information for each measurement schema (default: false) |            |                       |
+| `-h` | `--help`            | Help for the `create` command                                         |            |                       |
+|      | `--hide-headers`    | Hide table headers (default `false`)                                  |            | `INFLUX_HIDE_HEADERS` |
+|      | `--host`            | HTTP address of InfluxDB (default `http://localhost:8086`)            | string     | `INFLUX_HOST`         |
+|      | `--json`            | Output data as JSON (default `false`)                                 |            | `INFLUX_OUTPUT_JSON`  |
+| `-n` | `--name`            | Measurement name                                                      | string     |                       |
+| `-o` | `--org`             | Organization name (mutually exclusive with `--org-id`)                | string     | `INFLUX_ORG`          |
+|      | `--org-id`          | Organization ID (mutually exclusive with `--org`)                     | string     | `INFLUX_ORG_ID`       |
+|      | `--skip-verify`     | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`           | API token                                                             | string     | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+### List all schemas of a bucket and print column information
+
+```sh
+influx bucket-schema list \
+  --bucket example-bucket
+  --extended-output
+```
+
+### Print column details for a single measurement
+```sh
+influx bucket-schema list \
+  --bucket example-bucket \
+  --name cpu \
+  --extended-output
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/bucket-schema/update.md b/content/influxdb/v2.2/reference/cli/influx/bucket-schema/update.md
new file mode 100644
index 000000000..c8566039b
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/bucket-schema/update.md
@@ -0,0 +1,96 @@
+---
+title: influx bucket-schema update
+description: The `influx bucket-schema update` command updates the schema of an InfluxDB bucket that has the `explicit` schema-type.
+menu:
+  influxdb_2_2_ref:
+    name: influx bucket-schema update
+    parent: influx bucket-schema
+weight: 201
+related:
+  - /influxdb/cloud/organizations/buckets/bucket-schema
+---
+
+The `influx bucket-schema update` command updates the schema of an InfluxDB bucket that has the [`explicit` schema-type](/influxdb/cloud/reference/cli/influx/bucket/create/#create-a-bucket-with-an-explicit-schema).
+
+`bucket-schema update` requires a bucket with at least one defined schema.
+
+## Usage
+
+```sh
+influx bucket-schema update [flags]
+```
+
+##### Supported operations
+- Adding new columns to a schema
+
+##### Unsupported operations
+- Modify existing columns in a schema
+- Delete columns from a schema
+
+## Flags
+
+| Flag |                     | Description                                                                                                                                                                         | Input type | {{< cli/mapped >}}    |
+|:-----|:--------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:----------:|:----------------------|
+| `-c` | `--active-config`   | CLI configuration to use for command                                                                                                                                                | string     |                       |
+| `-n` | `--bucket`          | ({{< req >}}) Bucket name (mutually exclusive with `--bucket-id`)                                                                                                                   | string     |                       |
+| `-i` | `--bucket-id`       | ({{< req >}}) Bucket ID (mutually exclusive with `--bucket`)                                                                                                                        | string     |                       |
+|      | `--columns-file`    | ({{< req >}}) Path to column definitions file. For more information, see [Create a columns file](/influxdb/cloud/reference/cli/influx/bucket-schema/create/#create-a-columns-file). | string     |                       |
+|      | `--columns-format`  | Columns file format (`csv`, `ndjson`, `json`, default: `auto`). For more information, see [Update a schema with columns format](#update-a-schema-with-columns-format)               | string     |                       |
+|      | `--configs-path`    | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`)                                                                                                               | string     | `INFLUX_CONFIGS_PATH` |
+| `-x` | `--extended-output` | Print column information for each measurement schema (default: false)                                                                                                               |            |                       |
+| `-h` | `--help`            | Help for the `create` command                                                                                                                                                       |            |                       |
+|      | `--hide-headers`    | Hide table headers (default `false`)                                                                                                                                                |            | `INFLUX_HIDE_HEADERS` |
+|      | `--host`            | HTTP address of InfluxDB (default `http://localhost:8086`)                                                                                                                          | string     | `INFLUX_HOST`         |
+|      | `--json`            | Output data as JSON (default `false`)                                                                                                                                               |            | `INFLUX_OUTPUT_JSON`  |
+| `-n` | `--name`            | ({{< req >}}) Measurement name                                                                                                                                                      | string     |                       |
+| `-o` | `--org`             | Organization name (mutually exclusive with `--org-id`)                                                                                                                              | string     | `INFLUX_ORG`          |
+|      | `--org-id`          | Organization ID (mutually exclusive with `--org`)                                                                                                                                   | string     | `INFLUX_ORG_ID`       |
+|      | `--skip-verify`     | Skip TLS certificate verification                                                                                                                                                   |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`           | API token                                                                                                                                                                           | string     | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+- [Update a schema using the influx CLI](#update-a-schema-using-the-influx-cli)
+- [Update a schema and print column information](#update-a-schema-and-print-column-information)
+- [Update a schema with columns format](#update-a-schema-specifying-the-columns-format)
+
+### Update a schema using the influx CLI
+
+```sh
+influx bucket-schema update \
+  --bucket example-bucket \
+  --name temperature \
+  --columns-file columns.csv
+```
+
+### Update a schema and print column information
+```sh
+influx bucket-schema update \
+  --bucket example-bucket \
+  --name cpu \
+  --columns-file columns.csv \
+  -extended-output
+```
+
+### Update a schema with columns format
+
+By default, InfluxDB attempts to detect the **columns file** format.
+If your file's extension doesn't match the format, set the format with the `columns-format` flag.
+
+```sh
+influx bucket-schema update \
+  --bucket example-bucket \
+  --name cpu \
+  --columns-file columns.json \
+  --columns-format ndjson
+```
+
+```sh
+influx bucket-schema update \
+  --bucket example-bucket \
+  --name cpu \
+  --columns-file columns.txt \
+  --columns-format csv
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/bucket/_index.md b/content/influxdb/v2.2/reference/cli/influx/bucket/_index.md
new file mode 100644
index 000000000..3a2f027d7
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/bucket/_index.md
@@ -0,0 +1,43 @@
+---
+title: influx bucket
+description: The `influx bucket` command and its subcommands manage buckets in InfluxDB.
+menu:
+  influxdb_2_2_ref:
+    name: influx bucket
+    parent: influx
+weight: 101
+influxdb/v2.2/tags: [buckets]
+cascade:
+  related:
+    - /influxdb/v2.2/reference/cli/influx/#provide-required-authentication-credentials, influx CLI—Provide required authentication credentials
+    - /influxdb/v2.2/reference/cli/influx/#flag-patterns-and-conventions, influx CLI—Flag patterns and conventions
+cascade:
+  metadata: [influx CLI 2.0.0+, InfluxDB 2.0.0+]
+---
+
+The `influx bucket` command and its subcommands manage buckets in InfluxDB.
+
+## Usage
+```
+influx bucket [flags]
+influx bucket [command]
+```
+
+## Subcommands
+| Subcommand                                                  | Description   |
+|:----------                                                  |:-----------   |
+| [create](/influxdb/v2.2/reference/cli/influx/bucket/create) | Create bucket |
+| [delete](/influxdb/v2.2/reference/cli/influx/bucket/delete) | Delete bucket |
+| [list](/influxdb/v2.2/reference/cli/influx/bucket/list)     | List buckets  |
+| [update](/influxdb/v2.2/reference/cli/influx/bucket/update) | Update bucket |
+
+## Flags
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:-----------|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+| `-h` | `--help`          | Help for the `bucket` command                                         |            |                       |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)            | string     | `INFLUX_HOST`         |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers.                          | string     |                       |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`         | API token                                                             | string     | `INFLUX_TOKEN`        |
diff --git a/content/influxdb/v2.2/reference/cli/influx/bucket/create.md b/content/influxdb/v2.2/reference/cli/influx/bucket/create.md
new file mode 100644
index 000000000..b7634c148
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/bucket/create.md
@@ -0,0 +1,116 @@
+---
+title: influx bucket create
+description: The `influx bucket create` command creates a bucket in InfluxDB.
+menu:
+  influxdb_2_2_ref:
+    name: influx bucket create
+    parent: influx bucket
+weight: 201
+aliases:
+  - /influxdb/v2.2/reference/cli/influx/bucket/create/
+related:
+  - /influxdb/v2.2/organizations/buckets/create-bucket/
+  - /influxdb/v2.2/reference/internals/shards/
+  - /influxdb/v2.2/reference/cli/influx/#provide-required-authentication-credentials, influx CLI—Provide required authentication credentials
+  - /influxdb/v2.2/reference/cli/influx/#flag-patterns-and-conventions, influx CLI—Flag patterns and conventions
+updated_in: CLI v2.2.0
+---
+
+The `influx bucket create` command creates a bucket in InfluxDB.
+
+## Usage
+
+```sh
+influx bucket create [flags]
+```
+
+## Flags
+
+| Flag |                          | Description                                                                                                                                                                 | Input type | {{< cli/mapped >}}    |
+| :--- | :----------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :--------: | :-------------------- |
+| `-c` | `--active-config`        | CLI configuration to use for command                                                                                                                                        |   string   |                       |
+|      | `--configs-path`         | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`)                                                                                                       |   string   | `INFLUX_CONFIGS_PATH` |
+| `-d` | `--description`          | Bucket description                                                                                                                                                          |   string   |                       |
+| `-h` | `--help`                 | Help for the `create` command                                                                                                                                               |            |                       |
+|      | `--hide-headers`         | Hide table headers (default `false`)                                                                                                                                        |            | `INFLUX_HIDE_HEADERS` |
+|      | `--host`                 | HTTP address of InfluxDB (default `http://localhost:8086`)                                                                                                                  |   string   | `INFLUX_HOST`         |
+|      | `--http-debug`           | Inspect communication with InfluxDB servers.                                                                                                                                |   string   |                       |
+|      | `--json`                 | Output data as JSON (default `false`)                                                                                                                                       |            | `INFLUX_OUTPUT_JSON`  |
+| `-n` | `--name`                 | Bucket name                                                                                                                                                                 |   string   | `INFLUX_BUCKET_NAME`  |
+| `-o` | `--org`                  | Organization name (mutually exclusive with `--org-id`)                                                                                                                      |   string   | `INFLUX_ORG`          |
+|      | `--org-id`               | Organization ID (mutually exclusive with `--org`)                                                                                                                           |   string   | `INFLUX_ORG_ID`       |
+| `-r` | `--retention`            | Duration bucket retains data (0 is infinite, default is 0)                                                                                                                  |  duration  |                       |
+|      | `--schema-type`          | Bucket schema type (`explicit`, default `implicit`) _(Cloud only)_. For more information, see [Manage bucket schema](/influxdb/cloud/organizations/buckets/bucket-schema/). |   string   |                       |
+|      | `--shard-group-duration` | Bucket shard group duration (OSS only)                                                                                                                                      |   string   |                       |
+|      | `--skip-verify`          | Skip TLS certificate verification                                                                                                                                           |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`                | API token                                                                                                                                                                   |   string   | `INFLUX_TOKEN`        |
+
+{{% note %}}
+#### Retention periods
+The minimum retention period is **one hour**. Valid `--retention` units:
+
+- nanoseconds (`ns`)
+- microseconds (`us` or `µs`)
+- milliseconds (`ms`)
+- seconds (`s`)
+- minutes (`m`)
+- hours (`h`)
+- days (`d`)
+- weeks (`w`)
+{{% /note %}}
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+- [Create a bucket with infinite data retention](#create-a-bucket-with-infinite-data-retention)
+- [Create a bucket that retains data for 30 days](#create-a-bucket-that-retains-data-for-30-days)
+- [Create a bucket with a description](#create-a-bucket-with-a-description)
+- [Create a bucket with a custom shard group duration](#create-a-bucket-with-a-custom-shard-group-duration)
+- [Create a bucket with an explicit schema](#create-a-bucket-with-an-explicit-schema)
+
+##### Create a bucket with infinite data retention
+
+```sh
+influx bucket create --name example-bucket
+```
+
+##### Create a bucket that retains data for 30 days
+
+```sh
+influx bucket create \
+  --name example-bucket \
+  --retention 30d
+```
+
+##### Create a bucket with a description
+
+```sh
+influx bucket create \
+  --name example-bucket \
+  --description "Example bucket description"
+```
+
+##### Create a bucket with a custom shard group duration
+
+Custom shard group durations are only supported in **InfluxDB OSS**.
+The shard group duration must be shorter than the bucket's retention period. For more information, see [InfluxDB shards and shard groups](/influxdb/v2.2/reference/internals/shards/).
+
+```sh
+influx bucket create \
+  --name example-bucket \
+  --retention 30d \
+  --shard-group-duration 2d
+```
+
+##### Create a bucket with an explicit schema
+
+{{% cloud %}}
+[Explicit bucket schemas](/influxdb/cloud/reference/cli/influx/bucket-schema) are only
+supported in **InfluxDB Cloud**.
+For more information, see [Manage bucket schema](/influxdb/cloud/organizations/buckets/bucket-schema/).
+{{% /cloud %}}
+
+```sh
+{{< get-shared-text "bucket-schema/bucket-schema-type.sh" >}}
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/bucket/delete.md b/content/influxdb/v2.2/reference/cli/influx/bucket/delete.md
new file mode 100644
index 000000000..4080fb7ac
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/bucket/delete.md
@@ -0,0 +1,53 @@
+---
+title: influx bucket delete
+description: The `influx bucket delete` command deletes a bucket from InfluxDB and all the data it contains.
+menu:
+  influxdb_2_2_ref:
+    name: influx bucket delete
+    parent: influx bucket
+weight: 201
+aliases:
+  - /influxdb/v2.2/reference/cli/influx/bucket/delete/
+related:
+  - /influxdb/v2.2/organizations/buckets/delete-bucket/
+  - /influxdb/v2.2/reference/cli/influx/#provide-required-authentication-credentials, influx CLI—Provide required authentication credentials
+  - /influxdb/v2.2/reference/cli/influx/#flag-patterns-and-conventions, influx CLI—Flag patterns and conventions
+---
+
+The `influx bucket delete` command deletes a bucket from InfluxDB and all the data it contains.
+
+## Usage
+```sh
+influx bucket delete [flags]
+```
+
+## Flags
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:----------:|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+| `-h` | `--help`          | Help for the `delete` command                                         |            |                       |
+|      | `--hide-headers`  | Hide table headers (default `false`)                                  |            | `INFLUX_HIDE_HEADERS` |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)            | string     | `INFLUX_HOST`         |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers.                          | string     |                       |
+| `-i` | `--id`            | Bucket ID _(required if no `--name`)_                                 | string     |                       |
+|      | `--json`          | Output data as JSON (default `false`)                                 |            | `INFLUX_OUTPUT_JSON`  |
+| `-n` | `--name`          | Bucket name _(requires `--org` or `org-id`)_                          | string     |                       |
+| `-o` | `--org`           | Organization name (mutually exclusive with `--org-id`)                | string     | `INFLUX_ORG`          |
+|      | `--org-id`        | Organization ID (mutually exclusive with `--org`)                     | string     | `INFLUX_ORG_ID`       |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`         | API token                                                             | string     | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### Delete a bucket by name
+```sh
+influx bucket delete --name example-bucket
+```
+
+##### Delete a bucket by ID
+```sh
+influx bucket delete --id 06c86c40a9f36000
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/bucket/list.md b/content/influxdb/v2.2/reference/cli/influx/bucket/list.md
new file mode 100644
index 000000000..b0e47cc28
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/bucket/list.md
@@ -0,0 +1,66 @@
+---
+title: influx bucket list
+description: The `influx bucket list` command lists and searches for buckets in InfluxDB.
+menu:
+  influxdb_2_2_ref:
+    name: influx bucket list
+    parent: influx bucket
+weight: 201
+aliases:
+  - /influxdb/v2.2/reference/cli/influx/bucket/find
+  - /influxdb/v2.2/reference/cli/influx/bucket/list/
+updated_in: CLI v2.2.0
+---
+
+The `influx bucket list` command lists and searches for buckets in InfluxDB.
+
+## Usage
+```
+influx bucket list [flags]
+```
+
+#### Command aliases
+`list`, `ls`, `find`
+
+## Flags
+| Flag |                   | Description                                                                  | Input type | {{< cli/mapped >}}    |
+| :--- | :---------------- | :--------------------------------------------------------------------------- | :--------: | :-------------------- |
+| `-c` | `--active-config` | CLI configuration to use for command                                         |   string   |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`)        |   string   | `INFLUX_CONFIGS_PATH` |
+| `-h` | `--help`          | Help for the `list` command                                                  |            |                       |
+|      | `--hide-headers`  | Hide table headers (default `false`)                                         |            | `INFLUX_HIDE_HEADERS` |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)                   |   string   | `INFLUX_HOST`         |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers.                                 |   string   |                       |
+| `-i` | `--id`            | Bucket ID                                                                    |   string   |                       |
+|      | `--json`          | Output data as JSON (default `false`)                                        |            | `INFLUX_OUTPUT_JSON`  |
+|      | `--limit`         | Total number of buckets to fetch from the server, or 0 to return all buckets |   string   |                       |
+| `-n` | `--name`          | Bucket name                                                                  |   string   | `INFLUX_BUCKET_NAME`  |
+|      | `--offset`        | Number of buckets to skip over in the list                                   |            | `INFLUX_ORG`          |
+| `-o` | `--org`           | Organization name (mutually exclusive with `--org-id`)                       |   string   | `INFLUX_ORG`          |
+|      | `--org-id`        | Organization ID (mutually exclusive with `--org`)                            |   string   | `INFLUX_ORG_ID`       |
+|      | `--page-size`     | Number of buckets to fetch per request to the server (default 20)            |            |                       |
+|      | `--skip-verify`   | Skip TLS certificate verification                                            |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`         | API token                                                                    |   string   | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+- [List all buckets](#list-all-buckets)
+- [List a bucket by name](#list-a-bucket-by-name)
+- [List a bucket by ID](#list-a-bucket-by-id)
+
+##### List all buckets
+```sh
+influx bucket list
+```
+
+##### List a bucket by name
+```sh
+influx bucket list --name example-bucket
+```
+
+##### List a bucket by ID
+```sh
+influx bucket list --id 06c86c40a9f36000
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/bucket/update.md b/content/influxdb/v2.2/reference/cli/influx/bucket/update.md
new file mode 100644
index 000000000..50d3fae26
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/bucket/update.md
@@ -0,0 +1,83 @@
+---
+title: influx bucket update
+description: The `influx bucket update` command updates information associated with buckets in InfluxDB.
+menu:
+  influxdb_2_2_ref:
+    name: influx bucket update
+    parent: influx bucket
+weight: 201
+aliases:
+  - /influxdb/v2.2/reference/cli/influx/bucket/update/
+related:
+  - /influxdb/v2.2/organizations/buckets/update-bucket/
+  - /influxdb/v2.2/reference/internals/shards/  
+  - /influxdb/v2.2/reference/cli/influx/#provide-required-authentication-credentials, influx CLI—Provide required authentication credentials
+  - /influxdb/v2.2/reference/cli/influx/#flag-patterns-and-conventions, influx CLI—Flag patterns and conventions
+---
+
+The `influx bucket update` command updates information associated with buckets in InfluxDB.
+
+## Usage
+```
+influx bucket update [flags]
+```
+
+## Flags
+| Flag |                          | Description                                                           | Input type | {{< cli/mapped >}}    |
+|:-----|:-------------------------|:----------------------------------------------------------------------|:----------:|:----------------------|
+| `-c` | `--active-config`        | CLI configuration to use for command                                  | string     |                       |
+|      | `--configs-path`         | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+| `-d` | `--description`          | Bucket description                                                    | string     |                       |
+| `-h` | `--help`                 | Help for the `update` command                                         |            |                       |
+|      | `--hide-headers`         | Hide table headers (default `false`)                                  |            | `INFLUX_HIDE_HEADERS` |
+|      | `--host`                 | HTTP address of InfluxDB (default `http://localhost:8086`)            | string     | `INFLUX_HOST`         |
+|      | `--http-debug`           | Inspect communication with InfluxDB servers.                          | string     |                       |
+| `-i` | `--id`                   | ({{< req >}}) Bucket ID                                               | string     |                       |
+|      | `--json`                 | Output data as JSON (default `false`)                                 |            | `INFLUX_OUTPUT_JSON`  |
+| `-n` | `--name`                 | New bucket name                                                       | string     | `INFLUX_BUCKET_NAME`  |
+| `-r` | `--retention`            | New duration bucket will retain data                                  | duration   |                       |
+|      | `--shard-group-duration` | Custom shard group duration for the bucket (OSS only)                 | string     |                       |
+|      | `--skip-verify`          | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`                | API token                                                             | string     | `INFLUX_TOKEN`        |
+
+{{% note %}}
+#### Retention periods
+The minimum retention period is **one hour**. Valid `--retention` units:
+
+- nanoseconds (`ns`)
+- microseconds (`us` or `µs`)
+- milliseconds (`ms`)
+- seconds (`s`)
+- minutes (`m`)
+- hours (`h`)
+- days (`d`)
+- weeks (`w`)
+{{% /note %}}
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### Update the name of a bucket
+```sh
+influx bucket update \
+  --id 06c86c40a9f36000 \
+  --name new-bucket-name
+```
+
+##### Update the retention period of a bucket
+```sh
+influx bucket update \
+  --id 06c86c40a9f36000 \
+  --retention 90d
+```
+
+##### Update the shard group duration of a bucket
+Custom shard group durations are only supported in **InfluxDB OSS**.
+The shard group duration must be shorter than the buckets retention period.
+
+```sh
+influx bucket update \
+  --id 06c86c40a9f36000 \
+  --shard-group-duration 2d
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/completion/_index.md b/content/influxdb/v2.2/reference/cli/influx/completion/_index.md
new file mode 100644
index 000000000..13b3bfe28
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/completion/_index.md
@@ -0,0 +1,61 @@
+---
+title: influx completion
+description: >
+  The `influx completion` command outputs `influx` shell completion scripts for a
+  specified shell (`bash` or `zsh`).
+menu:
+  influxdb_2_2_ref:
+    name: influx completion
+    parent: influx
+weight: 101
+influxdb/v2.2/tags: [cli, tools]
+related:
+  - /influxdb/v2.2/reference/cli/influx/#provide-required-authentication-credentials, influx CLI—Provide required authentication credentials
+  - /influxdb/v2.2/reference/cli/influx/#flag-patterns-and-conventions, influx CLI—Flag patterns and conventions
+metadata: [influx CLI 2.0.0+, InfluxDB 2.0.0+]
+---
+
+The `influx completion` command outputs `influx` shell completion scripts for a
+specified shell (`bash` or `zsh`).
+
+## Usage
+```
+influx completion [bash|zsh] [flags]
+```
+
+## Flags
+| Flag |          | Description                       |
+|:---- |:---      |:-----------                       |
+| `-h` | `--help` | Help for the `completion` command |
+
+## Install completion scripts
+
+Add the appropriate installation command below to your `.bashrc` or `.zshrc`.
+
+#### Completion snippets in .bashrc or .zshrc
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[bash](#)
+[zsh](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```sh
+# macOS
+$ source $(brew --prefix)/etc/bash_completion.d
+$ source <(influx completion bash)
+
+# Ubuntu
+$ source /etc/bash_completion.d
+$ source <(influx completion bash)
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```sh
+# macOS
+$ source <(influx completion zsh)
+
+# Ubuntu
+$ source <(influx completion zsh)
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
diff --git a/content/influxdb/v2.2/reference/cli/influx/config/_index.md b/content/influxdb/v2.2/reference/cli/influx/config/_index.md
new file mode 100644
index 000000000..8c0a74bbe
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/config/_index.md
@@ -0,0 +1,65 @@
+---
+title: influx config
+description: The `influx config` command and subcommands manage multiple InfluxDB connection configurations.
+menu:
+  influxdb_2_2_ref:
+    name: influx config
+    parent: influx
+weight: 101
+influxdb/v2.2/tags: [config]
+cascade:
+  related:
+    - /influxdb/v2.2/reference/cli/influx/#provide-required-authentication-credentials, influx CLI—Provide required authentication credentials
+    - /influxdb/v2.2/reference/cli/influx/#flag-patterns-and-conventions, influx CLI—Flag patterns and conventions
+  metadata: [influx CLI 2.0.0+, InfluxDB 2.0.0+]
+---
+
+The `influx config` command displays the active InfluxDB connection configuration
+and manages multiple connection configurations stored, by default, in `~/.influxdbv2/configs`.
+Each connection includes a URL, token, associated organization, and active setting.
+InfluxDB reads the token from the active connection configuration, so you don't
+have to manually enter a token to log into InfluxDB.
+
+## Usage
+```
+influx config [flags]
+influx config [command]
+influx config <config-name>
+```
+
+##### Quickly switch between configurations
+```sh
+# Syntax
+influx config <config-name>
+
+# Example
+influx config local-config
+```
+
+To quickly switch back to the previous configuration, use the following command:
+
+```sh
+influx config -
+```
+
+## Examples
+```sh
+# Show the active connection configuration
+influx config
+
+# Set a connection configuration as active
+influx config local-config
+```
+
+## Subcommands
+| Subcommand                                                  | Description                              |
+|:----                                                        |:-----------                              |
+| [create](/influxdb/v2.2/reference/cli/influx/config/create) | Create a connection configuration        |
+| [list](/influxdb/v2.2/reference/cli/influx/config/create)   | List connection configurations           |
+| [delete](/influxdb/v2.2/reference/cli/influx/config/rm)     | Delete a connection configuration        |
+| [set](/influxdb/v2.2/reference/cli/influx/config/set)       | Set or update a connection configuration |
+
+## Flags
+| Flag |          | Description                   |
+|:---- |:---      |:-----------                   |
+| `-h` | `--help` | Help for the `config` command |
diff --git a/content/influxdb/v2.2/reference/cli/influx/config/create.md b/content/influxdb/v2.2/reference/cli/influx/config/create.md
new file mode 100644
index 000000000..8fe2f91b7
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/config/create.md
@@ -0,0 +1,49 @@
+---
+title: influx config create
+description: The `influx config create` command creates a InfluxDB connection configuration.
+menu:
+  influxdb_2_2_ref:
+    name: influx config create
+    parent: influx config
+weight: 201
+---
+
+The `influx config create` command creates a InfluxDB connection configuration
+and stores it in the `configs` file (by default, stored at `~/.influxdbv2/configs`).
+
+## Usage
+```
+influx config create [flags]
+```
+
+## Flags
+| Flag |                  | Description                                                  | Input type | {{< cli/mapped >}}    |
+|:-----|:-----------------|:-------------------------------------------------------------|:----------:|:----------------------|
+| `-a` | `--active`       | Set the specified connection to be the active configuration. |            |                       |
+| `-n` | `--config-name`  | ({{< req >}}) Name of the new configuration.                 | string     |                       |
+| `-h` | `--help`         | Help for the `create` command                                |            |                       |
+|      | `--hide-headers` | Hide table headers (default `false`)                         |            | `INFLUX_HIDE_HEADERS` |
+| `-u` | `--host-url`     | ({{< req >}}) Connection URL for the new configuration.      | string     |                       |
+|      | `--json`         | Output data as JSON (default `false`)                        |            | `INFLUX_OUTPUT_JSON`  |
+| `-o` | `--org`          | Organization name                                            | string     |                       |
+| `-t` | `--token`        | API token                                                    | string     | `INFLUX_TOKEN`        |
+
+## Examples
+
+##### Create a connection configuration and set it active
+```sh
+influx config create --active \
+  -n config-name \
+  -u http://localhost:8086 \
+  -t mySuP3rS3cr3tT0keN \
+  -o example-org
+```
+
+##### Create a connection configuration without setting it active
+```sh
+influx config create \
+  -n config-name \
+  -u http://localhost:8086 \
+  -t mySuP3rS3cr3tT0keN \
+  -o example-org
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/config/list.md b/content/influxdb/v2.2/reference/cli/influx/config/list.md
new file mode 100644
index 000000000..7585c5b70
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/config/list.md
@@ -0,0 +1,29 @@
+---
+title: influx config list
+description: The `influx config list` command lists all InfluxDB connection configurations.
+menu:
+  influxdb_2_2_ref:
+    name: influx config list
+    parent: influx config
+weight: 201
+---
+
+The `influx config list` command lists all InfluxDB connection configurations in
+the `configs` file (by default, stored at `~/.influxdbv2/configs`).
+Each connection configuration includes a URL, API token, and active setting.
+An asterisk (`*`) indicates the active configuration.
+
+## Usage
+```
+influx config list [flags]
+```
+
+#### Command aliases
+`list`, `ls`
+
+## Flags
+| Flag |                  | Description                                  | {{< cli/mapped >}}    |
+| :--- | :--------------- | :------------------------------------------- | :-------------------- |
+| `-h` | `--help`         | Help for the `list` command                  |                       |
+|      | `--hide-headers` | Hide table headers (default `false`)         | `INFLUX_HIDE_HEADERS` |
+|      | `--json`         | Output data as JSON (default `false`)        | `INFLUX_OUTPUT_JSON`  |
diff --git a/content/influxdb/v2.2/reference/cli/influx/config/rm.md b/content/influxdb/v2.2/reference/cli/influx/config/rm.md
new file mode 100644
index 000000000..c3606d551
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/config/rm.md
@@ -0,0 +1,42 @@
+---
+title: influx config rm
+description: The `influx config rm` command removes an InfluxDB connection configuration.
+menu:
+  influxdb_2_2_ref:
+    name: influx config rm
+    parent: influx config
+weight: 201
+aliases:
+  - /influxdb/v2.2/reference/cli/influx/config/delete/
+---
+
+The `influx config rm` command removes an InfluxDB connection configuration
+from the `configs` file (by default, stored at `~/.influxdbv2/configs`).
+
+## Usage
+```
+influx config rm <config-name> [flags]
+```
+
+#### Command aliases
+`rm`, `remove`, `delete`
+
+
+## Flags
+| Flag |                  | Description                                  | Input type | {{< cli/mapped >}}    |
+| :--- | :--------------- | :------------------------------------------- | :--------: | :-------------------- |
+| `-h` | `--help`         | Help for the `delete` command                |            |                       |
+|      | `--hide-headers` | Hide table headers (default `false`)         |            | `INFLUX_HIDE_HEADERS` |
+|      | `--json`         | Output data as JSON (default `false`)        |            | `INFLUX_OUTPUT_JSON`  |
+
+## Examples
+
+##### Delete a connection configuration
+```sh
+influx config rm local-config
+```
+
+##### Delete multiple connection configurations
+```sh
+influx config rm config-1 config-2
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/config/set.md b/content/influxdb/v2.2/reference/cli/influx/config/set.md
new file mode 100644
index 000000000..92cdd8e7f
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/config/set.md
@@ -0,0 +1,49 @@
+---
+title: influx config set
+description: The `influx config set` command updates an InfluxDB connection configuration.
+menu:
+  influxdb_2_2_ref:
+    name: influx config set
+    parent: influx config
+weight: 201
+---
+
+The `influx config set` command updates information in an InfluxDB connection
+configuration in the `configs` file (by default, stored at `~/.influxdbv2/configs`).
+
+## Usage
+```
+influx config set [flags]
+```
+
+#### Command aliases
+`set` , `update`
+
+## Flags
+| Flag |                  | Description                                                     | Input type | {{< cli/mapped >}}    |
+| :--- | :--------------- | :-------------------------------------------------------------- | :--------: | :-------------------- |
+| `-a` | `--active`       | Set the specified connection to active                          |            |                       |
+| `-n` | `--config-name`  | Name for the InfluxDB connection configuration to set or update |   string   |                       |
+| `-h` | `--help`         | Help for the `set` command                                      |            |                       |
+|      | `--hide-headers` | Hide table headers (default `false`)                            |            | `INFLUX_HIDE_HEADERS` |
+| `-u` | `--host-url`     | URL for InfluxDB connection configuration to set or update      |   string   |                       |
+|      | `--json`         | Output data as JSON (default `false`)                           |            | `INFLUX_OUTPUT_JSON`  |
+| `-o` | `--org`          | Organization name for the connection configuration              |   string   |                       |
+
+## Examples
+
+##### Update a connection configuration and set it to active
+```sh
+influx config set --active \
+  -n config-name \
+  -t mySuP3rS3cr3tT0keN \
+  -o example-org
+```
+
+##### Update a connection configuration and do not set it to active
+```sh
+influx config set \
+  -n config-name \
+  -t mySuP3rS3cr3tT0keN \
+  -o example-org
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/dashboards/_index.md b/content/influxdb/v2.2/reference/cli/influx/dashboards/_index.md
new file mode 100644
index 000000000..4e7ad1a40
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/dashboards/_index.md
@@ -0,0 +1,54 @@
+---
+title: influx dashboards
+description: >
+  The `influx dashboards` command lists existing InfluxDB dashboards.
+menu:
+  influxdb_2_2_ref:
+    name: influx dashboards
+    parent: influx
+weight: 101
+influxdb/v2.2/tags: [telegraf]
+related:
+  - /influxdb/v2.2/reference/cli/influx/#provide-required-authentication-credentials, influx CLI—Provide required authentication credentials
+  - /influxdb/v2.2/reference/cli/influx/#flag-patterns-and-conventions, influx CLI—Flag patterns and conventions
+metadata: [influx CLI 2.0.0+, InfluxDB 2.0.0+]
+---
+
+The `influx dashboards` command lists existing InfluxDB dashboards.
+
+## Usage
+```sh
+influx dashboards [flags]
+```
+
+## Flags
+| Flag |                   | Description                                                           | Input type  | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:-----------:|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string      |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string      | `INFLUX_CONFIGS_PATH` |
+| `-h` | `--help`          | Help for the `dashboards` command                                     |             |                       |
+|      | `--hide-headers`  | Hide table headers                                                    |             | `INFLUX_HIDE_HEADERS` |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)            | string      | `$INFLUX_HOST`        |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers.                          | string      |                       |
+| `-i` | `--id`            | Dashboard ID to retrieve                                              | stringArray |                       |
+|      | `--json`          | Output data as JSON                                                   |             | `INFLUX_OUTPUT_JSON`  |
+| `-o` | `--org`           | Organization name (mutually exclusive with `--org-id`)                | string      | `INFLUX_ORG`          |
+|      | `--org-id`        | Organization ID (mutually exclusive with `--org`)                     | string      | `INFLUX_ORG_ID`       |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |             | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`         | API token                                                             | string      | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### List all dashboards
+```sh
+influx dashboards
+```
+
+##### List only specific dashboards
+```sh
+influx dashboards \
+  --id 068ad4a493f2d000 \
+  --id 0623f2dabc000121
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/delete/_index.md b/content/influxdb/v2.2/reference/cli/influx/delete/_index.md
new file mode 100644
index 000000000..754a1e1a6
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/delete/_index.md
@@ -0,0 +1,78 @@
+---
+title: influx delete
+description: The `influx delete` command deletes points from an InfluxDB bucket.
+menu:
+  influxdb_2_2_ref:
+    name: influx delete
+    parent: influx
+weight: 101
+influxdb/v2.2/tags: [delete]
+related:
+  - /influxdb/v2.2/write-data/delete-data
+  - /influxdb/v2.2/reference/syntax/delete-predicate
+  - /influxdb/v2.2/reference/cli/influx/#provide-required-authentication-credentials, influx CLI—Provide required authentication credentials
+  - /influxdb/v2.2/reference/cli/influx/#flag-patterns-and-conventions, influx CLI—Flag patterns and conventions
+metadata: [influx CLI 2.0.3+, InfluxDB 2.0.3+]
+updated_in: CLI v2.2.0
+---
+
+The `influx delete` command deletes [points](/influxdb/v2.2/reference/glossary/#point)
+from an InfluxDB bucket in a specified time range.
+Select points to delete within the specified time range using [delete predicate syntax](/influxdb/v2.2/reference/syntax/delete-predicate).
+
+{{% warn %}}
+Running `influx delete` without the `-p` or `--predicate` flag deletes all data with timestamps between the specified
+`--start` and `--stop` times in the specified bucket.
+{{% /warn %}}
+
+## Flags
+| Flag |                   | Description                                                                                               | Input type | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------------------------------------------|:----------:|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                                                      | string     |                       |
+| `-b` | `--bucket`        | Name of bucket to remove data from (mutually exclusive with `--bucket-id`)                                | string     | `INFLUX_BUCKET_NAME`  |
+|      | `--bucket-id`     | Bucket ID (mutually exclusive with `--bucket`)                                                            | string     | `INFLUX_BUCKET_ID`    |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`)                                     | string     | `INFLUX_CONFIGS_PATH` |
+| `-h` | `--help`          | Help for the `delete` command                                                                             |            |                       |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)                                                | string     | `INFLUX_HOST`         |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers.                                                              | string     |                       |
+| `-o` | `--org`           | Organization name (mutually exclusive with `--org-id`)                                                    | string     | `INFLUX_ORG`          |
+|      | `--org-id`        | Organization ID (mutually exclusive with `--org`)                                                         | string     | `INFLUX_ORG_ID`       |
+| `-p` | `--predicate`     | InfluxQL-like predicate string (see [Delete predicate](/influxdb/v2.2/reference/syntax/delete-predicate)) | string     |                       |
+|      | `--skip-verify`   | Skip TLS certificate verification                                                                         |            | `INFLUX_SKIP_VERIFY`  |
+|      | `--start`         | ({{< req >}}) Start time in RFC3339 format (i.e. `2009-01-02T23:00:00Z`)                                  | string     |                       |
+|      | `--stop`          | ({{< req >}}) Stop time in RFC3339 format (i.e. `2009-01-02T23:00:00Z`)                                   | string     |                       |
+| `-t` | `--token`         | API token                                                                                                 | string     | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+- [Delete all points in a measurement](#delete-all-points-in-a-measurement)
+- [Delete points in a measurement with a specific tag value](#delete-points-in-a-measurement-with-a-specific-tag-value)
+- [Delete all points within a specified time frame](#delete-all-points-within-a-specified-time-frame)
+
+##### Delete all points in a measurement
+```sh
+influx delete \
+  --bucket example-bucket \
+  --start 1970-01-01T00:00:00Z \
+  --stop $(date +"%Y-%m-%dT%H:%M:%SZ") \
+  --predicate '_measurement="example-measurement"'
+```
+
+##### Delete points in a measurement with a specific tag value
+```sh
+influx delete \
+  --bucket example-bucket \
+  --start 1970-01-01T00:00:00Z \
+  --stop $(date +"%Y-%m-%dT%H:%M:%SZ") \
+  --predicate '_measurement="example-measurement" AND host="old-host"'
+```
+
+##### Delete all points within a specified time frame
+```sh
+influx delete \
+  --bucket example-bucket \
+  --start 2020-03-01T00:00:00Z \
+  --stop 2020-11-14T00:00:00Z
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/export/_index.md b/content/influxdb/v2.2/reference/cli/influx/export/_index.md
new file mode 100644
index 000000000..acd871326
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/export/_index.md
@@ -0,0 +1,111 @@
+---
+title: influx export
+description: The `influx export` command exports existing resources as an InfluxDB template.
+menu:
+  influxdb_2_2_ref:
+    parent: influx
+weight: 101
+aliases:
+  - /influxdb/v2.2/reference/cli/influx/pkg/export/
+related:
+  - /influxdb/v2.2/influxdb-templates/create/
+  - /influxdb/v2.2/reference/cli/influx/#provide-required-authentication-credentials, influx CLI—Provide required authentication credentials
+  - /influxdb/v2.2/reference/cli/influx/#flag-patterns-and-conventions, influx CLI—Flag patterns and conventions
+cascade:
+  metadata: [influx CLI 2.0.0+, InfluxDB 2.0.0+]
+---
+
+The `influx export` command exports existing resources as an InfluxDB template.
+_For detailed examples of exporting InfluxDB templates, see
+[Create an InfluxDB template](/influxdb/v2.2/influxdb-templates/create/)._
+
+## Usage
+
+```
+influx export [flags]
+influx export [command]
+```
+
+## Available subcommands
+
+| Subcommand                                                 | Description                                                |
+|:----------                                                 |:-----------                                                |
+| [all](/influxdb/v2.2/reference/cli/influx/export/all/)     | Export all resources in an organization as a template      |
+| [stack](/influxdb/v2.2/reference/cli/influx/export/stack/) | Export all resources associated with a stack as a template |
+
+## Flags
+
+| Flag |                           | Description                                                                      | Input Type | {{< cli/mapped >}}    |
+|:-----|:--------------------------|:---------------------------------------------------------------------------------|:-----------|:----------------------|
+| `-c` | `--active-config`         | CLI configuration to use for command                                             | string     |                       |
+|      | `--bucket-names`          | Comma-separated list of bucket names                                             | string     |                       |
+|      | `--buckets`               | Comma-separated list of bucket IDs                                               | string     |                       |
+|      | `--check-names`           | Comma-separated list of check names                                              | string     |                       |
+|      | `--checks`                | Comma-separated list of check IDs                                                | string     |                       |
+|      | `--configs-path`          | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`)            | string     | `INFLUX_CONFIGS_PATH` |
+|      | `--dashboard-names`       | Comma-separated list of dashboard names                                          | string     |                       |
+|      | `--dashboards`            | Comma-separated list of dashboard IDs                                            | string     |                       |
+|      | `--endpoint-names`        | Comma-separated list of notification endpoint names                              | string     |                       |
+|      | `--endpoints`             | Comma-separated list of notification endpoint IDs                                | string     |                       |
+| `-f` | `--file`                  | Template output file. Defaults to stdout. Use `.yml` or `.json` file extensions. | string     |                       |
+| `-h` | `--help`                  | Help for the `export` command                                                    |            |                       |
+|      | `--host`                  | HTTP address of InfluxDB (default `http://localhost:9999`)                       | string     | `INFLUX_HOST`         |
+|      | `--http-debug`            | Inspect communication with InfluxDB servers.                                     | string     |                       |
+|      | `--label-names`           | Comma-separated list of label names                                              | string     |                       |
+|      | `--labels`                | Comma-separated list of label IDs                                                | string     |                       |
+|      | `--resource-type`         | Resource type associated with all IDs via stdin                                  | string     |                       |
+|      | `--rule-names`            | Comma-separated list of notification rule names                                  | string     |                       |
+|      | `--rules`                 | Comma-separated list of notification rule IDs                                    | string     |                       |
+|      | `--skip-verify`           | Skip TLS certificate verification                                                |            | `INFLUX_SKIP_VERIFY`  |
+|      | `--stack-id`              | Stack ID to include resources from in export                                     | string     |                       |
+|      | `--task-names`            | Comma-separated list of task names                                               | string     |                       |
+|      | `--tasks`                 | Comma-separated list of task IDs                                                 | string     |                       |
+|      | `--telegraf-config-names` | Comma-separated list of Telegraf configuration names                             | string     |                       |
+|      | `--telegraf-configs`      | Comma-separated list of Telegraf configuration IDs                               | string     |                       |
+| `-t` | `--token`                 | API token                                                                        | string     | `INFLUX_TOKEN`        |
+|      | `--variable-names`        | Comma-separated list of variable names                                           | string     |                       |
+|      | `--variables`             | Comma-separated list of variable IDs                                             | string     |                       |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+- [Export buckets by ID](#export-buckets-by-id)
+- [Export buckets, labels, and dashboards by ID](#export-buckets-labels-and-dashboards-by-id)
+- [Export buckets, labels, and dashboards by name](#export-buckets-labels-and-dashboards-by-name)
+- [Export all resources associated with a stack](#export-all-resources-associated-with-a-stack)
+- [Export resources both associated and not associated with a stack](#export-resources-both-associated-and-not-associated-with-a-stack)
+
+##### Export buckets by ID
+```sh
+influx export --buckets 0Xx0oox00XXoxxoo1,0Xx0oox00XXoxxoo2
+```
+
+##### Export buckets, labels, and dashboards by ID
+```sh
+influx export \
+  --buckets 0Xx0oox00XXoxxoo1,0Xx0oox00XXoxxoo2 \
+  --labels o0x0oox0Xxoxx001,o0x0oox0Xxoxx002 \
+  --dashboards 0XxXooXoo0xooXo0X1,0XxXooXoo0xooXo0X2
+```
+
+##### Export buckets, labels, and dashboards by name
+```sh
+influx export \
+  --bucket-names bucket1,bucket2,bucket3 \
+  --label-names label1,label2,label3 \
+  --dashboard-names dashboard1,dashboard2,dashboard3
+```
+
+##### Export all resources associated with a stack
+```sh
+influx export --stack-id 0Xx0oox00XXoxxoo1
+```
+
+##### Export resources both associated and not associated with a stack
+```sh
+influx export \
+  --stack-id 0Xx0oox00XXoxxoo1 \
+  --buckets o0x0oox0Xxoxx001,0XxXooXoo0xooXo0X2 \
+  --dashboard-names bucket1
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/export/all.md b/content/influxdb/v2.2/reference/cli/influx/export/all.md
new file mode 100644
index 000000000..c0b5b7704
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/export/all.md
@@ -0,0 +1,87 @@
+---
+title: influx export all
+description: >
+  The `influx export all` command exports all resources in an organization as an InfluxDB template.
+menu:
+  influxdb_2_2_ref:
+    parent: influx export
+weight: 201
+aliases:
+  - /influxdb/v2.2/reference/cli/influx/pkg/export/all/
+related:
+  - /influxdb/v2.2/influxdb-templates/create/
+  - /influxdb/v2.2/reference/cli/influx/#provide-required-authentication-credentials, influx CLI—Provide required authentication credentials
+  - /influxdb/v2.2/reference/cli/influx/#flag-patterns-and-conventions, influx CLI—Flag patterns and conventions
+---
+
+The `influx export all` command exports all resources in an
+organization as an InfluxDB template.
+_For detailed examples of exporting InfluxDB templates, see
+[Create an InfluxDB template](/influxdb/v2.2/influxdb-templates/create/)._
+
+{{% note %}}
+To export resources as a template, you must use the **Operator token** created for
+the initial InfluxDB user or an **All-Access token**.
+For information about creating an All-Access API token, see [Create an API token](/influxdb/v2.2/security/tokens/create-token/).
+{{% /note %}}
+
+## Usage
+```
+influx export all [flags]
+```
+
+## Flags
+| Flag |                   | Description                                                                                     | Input Type  | {{< cli/mapped >}}    |
+|:-----|:------------------|:------------------------------------------------------------------------------------------------|:------------|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                                            | string      |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`)                           | string      | `INFLUX_CONFIGS_PATH` |
+| `-f` | `--file`          | Template output file. Defaults to stdout. Use `.yml` or `.json` file extensions.                | string      |                       |
+|      | `--filter`        | Specify resources to export by labelName or resourceKind (format: `--filter=labelName=example`) | stringArray |                       |
+| `-h` | `--help`          | Help for the `export all` command                                                               |             |                       |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)                                      | string      | `INFLUX_HOST`         |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers.                                                    | string      |                       |
+| `-o` | `--org`           | Organization name that owns the resources (mutually exclusive with `--org-id`)                  | string      | `INFLUX_ORG`          |
+|      | `--org-id`        | Organization ID that owns the resources (mutually exclusive with `--org`)                       | string      | `INFLUX_ORG_ID`       |
+|      | `--skip-verify`   | Skip TLS certificate verification                                                               |             | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`         | API token                                                                                       | string      | `INFLUX_TOKEN`        |
+
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+- [Export all resources in an organization as a template](#export-all-resources-in-an-organization-as-a-template)
+- [Export all bucket resources as a template](#export-all-bucket-resources-as-a-template)
+- [Export all resources associated with label Foo](#export-all-resources-associated-with-label-foo)
+- [Export all bucket resources and with label Foo](#export-all-bucket-resources-with-label-foo)
+- [Export all bucket or dashboard resources with label Foo](#export-all-bucket-or-dashboard-resources-with-label-foo)
+
+##### Export all resources in an organization as a template
+```sh
+influx export all
+```
+
+##### Export all bucket resources as a template
+```sh
+influx export all --filter=resourceKind=Bucket
+```
+
+##### Export all resources associated with label Foo
+```sh
+influx export all --filter=labelName=Foo
+```
+
+##### Export all bucket resources and with label Foo
+```sh
+influx export all \
+	--filter=resourceKind=Bucket \
+	--filter=labelName=Foo
+```
+
+##### Export all bucket or dashboard resources with label Foo
+```sh
+influx export all \
+	--filter=resourceKind=Bucket \
+	--filter=resourceKind=Dashboard \
+	--filter=labelName=Foo
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/export/stack.md b/content/influxdb/v2.2/reference/cli/influx/export/stack.md
new file mode 100644
index 000000000..c2e2c804f
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/export/stack.md
@@ -0,0 +1,51 @@
+---
+title: influx export stack
+description: >
+  The `influx export stack` command exports all resources associated with a stack as an InfluxDB template.
+menu:
+  influxdb_2_2_ref:
+    parent: influx export
+weight: 201
+aliases:
+  - /influxdb/v2.2/reference/cli/influx/pkg/export/stack
+related:
+  - /influxdb/v2.2/reference/cli/influx/#provide-required-authentication-credentials, influx CLI—Provide required authentication credentials
+  - /influxdb/v2.2/reference/cli/influx/#flag-patterns-and-conventions, influx CLI—Flag patterns and conventions
+---
+
+The `influx export stack` command exports all resources associated with a stack as a template.
+All `metadata.name` fields remain the same.
+
+{{% note %}}
+To export resources as a template, you must use the **Operator token** created for
+the initial InfluxDB user or an **All-Access token**.
+For information about creating an All-Access API token, see [Create an API token](/influxdb/v2.2/security/tokens/create-token/).
+{{% /note %}}
+
+## Usage
+```
+influx export stack <stack_id> [flags]
+```
+
+## Flags
+| Flag |                   | Description                                                                      | Input Type | {{< cli/mapped >}}    |
+|:-----|:------------------|:---------------------------------------------------------------------------------|:-----------|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                             | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`)            | string     | `INFLUX_CONFIGS_PATH` |
+| `-f` | `--file`          | Template output file. Defaults to stdout. Use `.yml` or `.json` file extensions. | string     |                       |
+| `-h` | `--help`          | Help for the `export stack` command                                              |            |                       |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)                       | string     | `INFLUX_HOST`         |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers.                                     | string     |                       |
+| `-o` | `--org`           | Organization name that owns the resources (mutually exclusive with `--org-id`)   | string     | `INFLUX_ORG`          |
+|      | `--org-id`        | Organization ID that owns the resources (mutually exclusive with `--org`)        | string     | `INFLUX_ORG_ID`       |
+|      | `--skip-verify`   | Skip TLS certificate verification                                                |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`         | API token                                                                        | string     | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### Export a stack as a template
+```sh
+influx export stack $STACK_ID
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/help/_index.md b/content/influxdb/v2.2/reference/cli/influx/help/_index.md
new file mode 100644
index 000000000..1eb3495dc
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/help/_index.md
@@ -0,0 +1,25 @@
+---
+title: influx help
+description: The `influx help` command provides help for any command in the `influx` command line interface.
+menu:
+  influxdb_2_2_ref:
+    name: influx help
+    parent: influx
+weight: 101
+related:
+  - /influxdb/v2.2/reference/cli/influx/#provide-required-authentication-credentials, influx CLI—Provide required authentication credentials
+  - /influxdb/v2.2/reference/cli/influx/#flag-patterns-and-conventions, influx CLI—Flag patterns and conventions
+metadata: [influx CLI 2.0.0+, InfluxDB 2.0.0+]
+---
+
+The `influx help` command provides help for any command in the `influx` command line interface.
+
+## Usage
+```
+influx help [command] [flags]
+```
+
+## Flags
+| Flag |          | Description                 |
+|:---- |:---      |:-----------                 |
+| `-h` | `--help` | Help for the `help` command |
diff --git a/content/influxdb/v2.2/reference/cli/influx/org/_index.md b/content/influxdb/v2.2/reference/cli/influx/org/_index.md
new file mode 100644
index 000000000..c40a8d2ff
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/org/_index.md
@@ -0,0 +1,40 @@
+---
+title: influx org
+description: The `influx org` command and its subcommands manage organization information in InfluxDB.
+menu:
+  influxdb_2_2_ref:
+    name: influx org
+    parent: influx
+weight: 101
+influxdb/v2.2/tags: [organizations]
+cascade:
+  related:
+    - /influxdb/v2.2/reference/cli/influx/#provide-required-authentication-credentials, influx CLI—Provide required authentication credentials
+    - /influxdb/v2.2/reference/cli/influx/#flag-patterns-and-conventions, influx CLI—Flag patterns and conventions
+  metadata: [influx CLI 2.0.0+, InfluxDB 2.0.0+]
+---
+
+The `influx org` command and its subcommands manage organization information in InfluxDB.
+
+## Usage
+```
+influx org [flags]
+influx org [command]
+```
+
+#### Command aliases
+`org`, `organization`
+
+## Subcommands
+| Subcommand                                                 | Description                      |
+|:----------                                                 |:-----------                      |
+| [create](/influxdb/v2.2/reference/cli/influx/org/create)   | Create an organization           |
+| [delete](/influxdb/v2.2/reference/cli/influx/org/delete)   | Delete an organization           |
+| [list](/influxdb/v2.2/reference/cli/influx/org/list)       | List organizations               |
+| [members](/influxdb/v2.2/reference/cli/influx/org/members) | Organization membership commands |
+| [update](/influxdb/v2.2/reference/cli/influx/org/update)   | Update an organization           |
+
+## Flags
+| Flag |          | Description                |
+|:---- |:---      |:-----------                |
+| `-h` | `--help` | Help for the `org` command |
diff --git a/content/influxdb/v2.2/reference/cli/influx/org/create.md b/content/influxdb/v2.2/reference/cli/influx/org/create.md
new file mode 100644
index 000000000..a07083f73
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/org/create.md
@@ -0,0 +1,47 @@
+---
+title: influx org create
+description: The `influx org create` creates an organization in InfluxDB.
+menu:
+  influxdb_2_2_ref:
+    name: influx org create
+    parent: influx org
+weight: 201
+---
+
+The `influx org create` creates an organization in InfluxDB.
+
+## Usage
+```
+influx org create [flags]
+```
+
+## Flags
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:----------:|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+| `-d` | `--description`   | Description of the organization                                       |            |                       |
+| `-h` | `--help`          | Help for the `create` command                                         |            |                       |
+|      | `--hide-headers`  | Hide table headers (default `false`)                                  |            | `INFLUX_HIDE_HEADERS` |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)            | string     | `INFLUX_HOST`         |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers.                          | string     |                       |
+|      | `--json`          | Output data as JSON (default `false`)                                 |            | `INFLUX_OUTPUT_JSON`  |
+| `-n` | `--name`          | ({{< req >}}) Organization name                                       | string     |                       |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`         | API token                                                             | string     | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### Create an organization
+```sh
+influx org create --name example-org
+```
+
+##### Create an organization with a description
+```sh
+influx org create \
+  --name example-org \
+  --description "Example organization description"
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/org/delete.md b/content/influxdb/v2.2/reference/cli/influx/org/delete.md
new file mode 100644
index 000000000..2b3734102
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/org/delete.md
@@ -0,0 +1,39 @@
+---
+title: influx org delete
+description: The `influx org delete` command deletes an organization in InfluxDB.
+menu:
+  influxdb_2_2_ref:
+    name: influx org delete
+    parent: influx org
+weight: 201
+---
+
+The `influx org delete` command deletes an organization in InfluxDB.
+
+## Usage
+```
+influx org delete [flags]
+```
+
+## Flags
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:----------:|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+| `-h` | `--help`          | Help for the `delete` command                                         |            |                       |
+|      | `--hide-headers`  | Hide table headers (default `false`)                                  |            | `INFLUX_HIDE_HEADERS` |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)            | string     | `INFLUX_HOST`         |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers.                          | string     |                       |
+| `-i` | `--id`            | ({{< req >}}) Organization ID                                         | string     | `INFLUX_ORG_ID`       |
+|      | `--json`          | Output data as JSON (default `false`)                                 |            | `INFLUX_OUTPUT_JSON`  |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`         | API token                                                             | string     | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### Delete an organization
+```sh
+influx org delete --id 0Xx0oox00XXoxxoo1
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/org/list.md b/content/influxdb/v2.2/reference/cli/influx/org/list.md
new file mode 100644
index 000000000..97f48de07
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/org/list.md
@@ -0,0 +1,59 @@
+---
+title: influx org list
+description: The `influx org list` lists and searches for organizations in InfluxDB.
+menu:
+  influxdb_2_2_ref:
+    name: influx org list
+    parent: influx org
+weight: 201
+aliases:
+  - /influxdb/v2.2/reference/influx/org/find
+---
+
+The `influx org list` lists and searches for organizations in InfluxDB.
+
+## Usage
+```
+influx org list [flags]
+```
+
+#### Command aliases
+`list`, `ls`, `find`
+
+## Flags
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:----------:|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+| `-h` | `--help`          | Help for the `list` command                                           |            |                       |
+|      | `--hide-headers`  | Hide table headers (default `false`)                                  |            | `INFLUX_HIDE_HEADERS` |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)            | string     | `INFLUX_HOST`         |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers.                          | string     |                       |
+| `-i` | `--id`            | Organization ID                                                       | string     | `INFLUX_ORG`          |
+|      | `--json`          | Output data as JSON (default `false`)                                 |            | `INFLUX_OUTPUT_JSON`  |
+| `-n` | `--name`          | Organization name                                                     | string     | `INFLUX_ORG_ID`       |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`         | API token                                                             | string     | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+- [List all organizations](#list-all-organizations)
+- [List a specific organization by name](#list-a-specific-organization-by-name)
+- [List a specific organization by ID](#list-a-specific-organization-by-id)
+
+##### List all organizations
+```sh
+influx org list
+```
+
+##### List a specific organization by name
+```sh
+influx org list --name example-org
+```
+
+##### List a specific organization by ID
+```sh
+influx org list --id 0Xx0oox00XXoxxoo1
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/org/members/_index.md b/content/influxdb/v2.2/reference/cli/influx/org/members/_index.md
new file mode 100644
index 000000000..fe6c0d017
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/org/members/_index.md
@@ -0,0 +1,30 @@
+---
+title: influx org members
+description: The `influx org members` command and its subcommands manage organization members in InfluxDB.
+menu:
+  influxdb_2_2_ref:
+    name: influx org members
+    parent: influx org
+weight: 201
+influxdb/v2.2/tags: [members, organizations]
+---
+
+The `influx org members` command and its subcommands manage organization members in InfluxDB.
+
+## Usage
+```
+influx org members [flags]
+influx org members [command]
+```
+
+## Subcommands
+| Subcommand                                                       | Description                |
+|:----------                                                       |:-----------                |
+| [add](/influxdb/v2.2/reference/cli/influx/org/members/add)       | Add organization member    |
+| [list](/influxdb/v2.2/reference/cli/influx/org/members/list)     | List organization members  |
+| [remove](/influxdb/v2.2/reference/cli/influx/org/members/remove) | Remove organization member |
+
+## Flags
+| Flag |          | Description                    |
+|:---- |:---      |:-----------                    |
+| `-h` | `--help` | Help for the `members` command |
diff --git a/content/influxdb/v2.2/reference/cli/influx/org/members/add.md b/content/influxdb/v2.2/reference/cli/influx/org/members/add.md
new file mode 100644
index 000000000..a29c37193
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/org/members/add.md
@@ -0,0 +1,38 @@
+---
+title: influx org members add
+description: The `influx org members add` command adds a member to an organization in InfluxDB.
+menu:
+  influxdb_2_2_ref:
+    name: influx org members add
+    parent: influx org members
+weight: 301
+---
+
+The `influx org members add` command adds a member to an organization in InfluxDB.
+
+## Usage
+```
+influx org members add [flags]
+```
+
+## Flags
+| Flag |                 | Description                                                | Input type | {{< cli/mapped >}}   |
+|:-----|:----------------|:-----------------------------------------------------------|:----------:|:---------------------|
+| `-h` | `--help`        | Help for the `add` command                                 |            |                      |
+|      | `--host`        | HTTP address of InfluxDB (default `http://localhost:8086`) | string     | `INFLUX_HOST`        |
+| `-i` | `--id`          | Organization ID                                            | string     | `INFLUX_ORG_ID`      |
+| `-m` | `--member`      | User ID                                                    | string     |                      |
+| `-n` | `--name`        | Organization name                                          | string     | `INFLUX_ORG`         |
+|      | `--skip-verify` | Skip TLS certificate verification                          |            | `INFLUX_SKIP_VERIFY` |
+| `-t` | `--token`       | API token                                                  | string     | `INFLUX_TOKEN`       |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### Add a member to an organization
+```sh
+influx org members add \
+  --member 00x0oo0X0xxxo000 \
+  --name example-org
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/org/members/list.md b/content/influxdb/v2.2/reference/cli/influx/org/members/list.md
new file mode 100644
index 000000000..c970b687e
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/org/members/list.md
@@ -0,0 +1,39 @@
+---
+title: influx org members list
+description: The `influx org members list` command lists members within an organization in InfluxDB.
+menu:
+  influxdb_2_2_ref:
+    name: influx org members list
+    parent: influx org members
+weight: 301
+---
+
+The `influx org members list` command lists members within an organization in InfluxDB.
+
+## Usage
+```
+influx org members list [flags]
+```
+
+## Flags
+| Flag |                  | Description                                                | Input type | {{< cli/mapped >}}    |
+|:-----|:-----------------|:-----------------------------------------------------------|:----------:|:----------------------|
+| `-h` | `--help`         | Help for the `list` command                                |            |                       |
+|      | `--hide-headers` | Hide table headers (default `false`)                       |            | `INFLUX_HIDE_HEADERS` |
+|      | `--host`         | HTTP address of InfluxDB (default `http://localhost:8086`) | string     | `INFLUX_HOST`         |
+|      | `--http-debug`   | Inspect communication with InfluxDB servers.               | string     |                       |
+| `-i` | `--id`           | Organization ID                                            | string     | `INFLUX_ORG_ID`       |
+|      | `--json`         | Output data as JSON (default `false`)                      |            | `INFLUX_OUTPUT_JSON`  |
+| `-n` | `--name`         | Organization name                                          | string     | `INFLUX_ORG`          |
+|      | `--skip-verify`  | Skip TLS certificate verification                          |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`        | API token                                                  | string     | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### List members of an organization
+```sh
+influx org members list \
+  --name example-org
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/org/members/remove.md b/content/influxdb/v2.2/reference/cli/influx/org/members/remove.md
new file mode 100644
index 000000000..48534d9fc
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/org/members/remove.md
@@ -0,0 +1,39 @@
+---
+title: influx org members remove
+description: The `influx org members remove` command removes a member from an organization in InfluxDB.
+menu:
+  influxdb_2_2_ref:
+    name: influx org members remove
+    parent: influx org members
+weight: 301
+---
+
+The `influx org members remove` command removes a member from an organization in InfluxDB.
+
+## Usage
+```
+influx org members remove [flags]
+```
+
+## Flags
+| Flag |                 | Description                                                | Input type | {{< cli/mapped >}}   |
+|:-----|:----------------|:-----------------------------------------------------------|:----------:|:---------------------|
+| `-h` | `--help`        | Help for the `remove` command                              |            |                      |
+|      | `--host`        | HTTP address of InfluxDB (default `http://localhost:8086`) | string     | `INFLUX_HOST`        |
+|      | `--http-debug`  | Inspect communication with InfluxDB servers.               | string     |                      |
+| `-i` | `--id`          | Organization ID                                            | string     | `INFLUX_ORG_ID`      |
+| `-m` | `--member`      | Member ID                                                  | string     |                      |
+| `-n` | `--name`        | Organization name                                          | string     | `INFLUX_ORG`         |
+|      | `--skip-verify` | Skip TLS certificate verification                          |            | `INFLUX_SKIP_VERIFY` |
+| `-t` | `--token`       | API token                                                  | string     | `INFLUX_TOKEN`       |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### Remove a member from an organization
+```sh
+influx org members remove \
+  --member 00x0oo0X0xxxo000 \
+  --name example-org
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/org/update.md b/content/influxdb/v2.2/reference/cli/influx/org/update.md
new file mode 100644
index 000000000..d8f4ee44f
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/org/update.md
@@ -0,0 +1,50 @@
+---
+title: influx org update
+description: The `influx org update` command updates information related to organizations in InfluxDB.
+menu:
+  influxdb_2_2_ref:
+    name: influx org update
+    parent: influx org
+weight: 201
+---
+
+The `influx org update` command updates information related to organizations in InfluxDB.
+
+## Usage
+```
+influx org update [flags]
+```
+
+## Flags
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}       |
+|:-----|:------------------|:----------------------------------------------------------------------|:----------:|:-------------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string     |                          |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH`    |
+| `-d` | `--description`   | New description for the organization                                  | string     | `INFLUX_ORG_DESCRIPTION` |
+| `-h` | `--help`          | Help for the `update` command                                         |            |                          |
+|      | `--hide-headers`  | Hide table headers (default `false`)                                  |            | `INFLUX_HIDE_HEADERS`    |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)            | string     | `INFLUX_HOST`            |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers.                          | string     |                          |
+| `-i` | `--id`            | ({{< req >}}) Organization ID                                         | string     | `INFLUX_ORG_ID`          |
+|      | `--json`          | Output data as JSON (default `false`)                                 |            | `INFLUX_OUTPUT_JSON`     |
+| `-n` | `--name`          | New organization name                                                 | string     | `INFLUX_ORG`             |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`     |
+| `-t` | `--token`         | API token                                                             | string     | `INFLUX_TOKEN`           |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### Update the name of an organization
+```sh
+influx org update \
+  --id 0Xx0oox00XXoxxoo1
+  --name new-org-name
+```
+
+##### Update the description of an organization
+```sh
+influx org update \
+  --id 0Xx0oox00XXoxxoo1
+  --description "New example organization description"
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/ping/_index.md b/content/influxdb/v2.2/reference/cli/influx/ping/_index.md
new file mode 100644
index 000000000..fa57003d4
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/ping/_index.md
@@ -0,0 +1,35 @@
+---
+title: influx ping
+description: >
+  The `influx ping` command checks the health of a running InfluxDB instance by
+  querying the `/health` endpoint.
+menu:
+  influxdb_2_2_ref:
+    name: influx ping
+    parent: influx
+weight: 101
+influxdb/v2.2/tags: [ping, health]
+related:
+  - /influxdb/v2.2/reference/cli/influx/#provide-required-authentication-credentials, influx CLI—Provide required authentication credentials
+  - /influxdb/v2.2/reference/cli/influx/#flag-patterns-and-conventions, influx CLI—Flag patterns and conventions
+metadata: [influx CLI 2.0.0+, InfluxDB 2.0.0+]
+---
+
+The `influx ping` command checks the health of a running InfluxDB instance by
+querying the `/health` endpoint.
+It does not require an API token.
+
+## Usage
+```
+influx ping [flags]
+```
+
+## Flags
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:-----------|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+| `-h` | `--help`          | Help for the `ping` command                                           |            |                       |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)            | string     | `INFLUX_HOST`         |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers.                          | string     |                       |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
diff --git a/content/influxdb/v2.2/reference/cli/influx/query/_index.md b/content/influxdb/v2.2/reference/cli/influx/query/_index.md
new file mode 100644
index 000000000..a63b18b4c
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/query/_index.md
@@ -0,0 +1,87 @@
+---
+title: influx query
+description: >
+  The `influx query` command executes a literal Flux query provided as a string
+  or a literal Flux query contained in a file.
+menu:
+  influxdb_2_2_ref:
+    name: influx query
+    parent: influx
+weight: 101
+influxdb/v2.2/tags: [query]
+related:
+  - /influxdb/v2.2/query-data/
+  - /influxdb/v2.2/query-data/execute-queries/influx-query/
+  - /influxdb/v2.2/reference/cli/influx/#provide-required-authentication-credentials, influx CLI—Provide required authentication credentials
+  - /influxdb/v2.2/reference/cli/influx/#flag-patterns-and-conventions, influx CLI—Flag patterns and conventions
+metadata: [influx CLI 2.0.0+, InfluxDB 2.0.0+]
+updated_in: CLI v2.0.5
+---
+
+The `influx query` command executes a literal Flux query provided as a string
+or a literal Flux query contained in a file.
+
+## Usage
+```
+influx query [query literal] [flags]
+```
+
+{{% note %}}
+#### Remove unnecessary columns in large datasets
+When using the `influx query` command to query and download large datasets,
+drop columns such as `_start` and `_stop` to optimize the download file size.
+
+```js
+// ...
+    |> drop(columns: ["_start", "_stop"])
+```
+{{% /note %}}
+
+## Flags
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:----------:|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+| `-f` | `--file`          | Path to Flux script file                                              | string     |                       |
+| `-h` | `--help`          | Help for the `query` command                                          |            |                       |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)            | string     | `INFLUX_HOST`         |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers.                          | string     |                       |
+| `-o` | `--org`           | Organization name (mutually exclusive with `--org-id`)                | string     | `INFLUX_ORG`          |
+|      | `--org-id`        | Organization ID (mutually exclusive with `--org`)                     | string     | `INFLUX_ORG_ID`       |
+| `-p` | `--profilers`     | Flux query profilers to enable (comma-separated)                      | string     |                       |
+| `-r` | `--raw`           | Output raw query results (annotated CSV)                              |            |                       |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`         | API token                                                             | string     | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+- [Query InfluxDB with a Flux string](#query-influxdb-with-a-flux-string)
+- [Query InfluxDB using a Flux file](#query-influxdb-with-a-flux-file)
+- [Query InfluxDB and return annotated CSV](#query-influxdb-and-return-annotated-csv)
+- [Query InfluxDB and append query profile data to results](#query-influxdb-and-append-query-profile-data-to-results)
+
+##### Query InfluxDB with a Flux string
+```sh
+influx query 'from(bucket:"example-bucket") |> range(start:-1m)'
+```
+
+##### Query InfluxDB with a Flux file
+```sh
+influx query --file /path/to/example-query.flux
+```
+
+##### Query InfluxDB and return annotated CSV
+```sh
+influx query 'from(bucket:"example-bucket") |> range(start:-1m)' --raw
+```
+
+##### Query InfluxDB and append query profile data to results
+_For more information about profilers, see [Flux profilers](/{{< latest "flux" >}}/stdlib/profiler/#available-profilers)._
+
+```sh
+influx query \
+  --profilers operator,query \
+  'from(bucket:"example-bucket") |> range(start:-1m)'
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/remote/_index.md b/content/influxdb/v2.2/reference/cli/influx/remote/_index.md
new file mode 100644
index 000000000..95561c6c4
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/remote/_index.md
@@ -0,0 +1,39 @@
+---
+title: influx remote
+description: Manage remote InfluxDB connections for replicating data.
+menu:
+  influxdb_2_2_ref:
+    name: influx remote
+    parent: influx
+weight: 101
+influxdb/v2.2/tags: [write, replication]
+related:
+  - /influxdb/v2.2/reference/cli/influx/replication
+  - /influxdb/v2.2/write-data/replication
+---
+
+{{% cloud %}}
+Replication remotes and replication streams can only be configured for InfluxDB OSS.
+{{% /cloud %}}
+
+Use the `influx remote` command to manage connections to remote instances of InfluxDB.
+Remote connections are used to replicate data on write at the bucket level.
+
+## Usage
+```
+influx remote [commond options] [arguments...]
+```
+
+## Subcommands
+
+|  Subcommand                                                 |  Description                           |
+|:--------------------------------------------------------------|--------------------------------------|
+| [`create`](/influxdb/v2.2/reference/cli/influx/remote/create) | Create a new remote connection       |
+| [`delete`](/influxdb/v2.2/reference/cli/influx/remote/delete) | Delete a remote connection |
+| [`list`](/influxdb/v2.2/reference/cli/influx/remote/list)     | List remote connections          |
+| [`update`](/influxdb/v2.2/reference/cli/influx/remote/update) | Update a remote connection |
+
+## Flags
+| Flag |          | Description                   |
+|:-----|:---------|:------------------------------|
+| `-h` | `--help` | Help for the `remote` command |
diff --git a/content/influxdb/v2.2/reference/cli/influx/remote/create.md b/content/influxdb/v2.2/reference/cli/influx/remote/create.md
new file mode 100644
index 000000000..42cf1295b
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/remote/create.md
@@ -0,0 +1,60 @@
+---
+title: influx remote create
+description: Create a new remote InfluxDB connection for replicating data.
+menu:
+  influxdb_2_2_ref:
+    name: influx remote create
+    parent: influx remote
+weight: 101
+influxdb/v2.2/tags: [write, replication]
+related:
+  - /influxdb/v2.2/reference/cli/influx/replication
+---
+
+{{% cloud %}}
+Replication remotes and replication streams can only be configured for InfluxDB OSS.
+{{% /cloud %}}
+
+The `influx remote create` command creates a new remote InfluxDB connection for replicating data.
+
+## Usage
+```
+influx remote create [commond options] [arguments...]
+```
+
+## Flags
+
+| Flag |                        | Description                                                           | Input type | {{< cli/mapped >}}    |
+| :--- | :--------------------- | :-------------------------------------------------------------------- | :--------: | :-------------------- |
+|      | `--org-id`             | Organization ID                                                       |   string   | `INFLUX_ORG_ID`       |
+| `-o` | `--org`                | Organization name                                                     |   string   | `INFLUX_ORG`          |
+| `-n` | `--name`               | Remote connection name                                                |   string   |                       |
+| `-d` | `--description`        | Remote connection description                                         |   string   |                       |
+|      | `--remote-url`         | Remote InfluxDB instance URL                                          |   string   |                       |
+|      | `--remote-api-token`   | Remote InfluxDB API token                                             |   string   |                       |
+|      | `--remote-org-id`      | Remote InfluxDB organization ID                                       |   string   |                       |
+|      | `--allow-insecure-tls` | Allows insecure TLS (self-signed certificates)                        |            |                       |
+|      | `--host`               | InfluxDB HTTP address (default `http://localhost:8086`)               |   string   | `INFLUX_HOST`         |
+|      | `--skip-verify`        | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+|      | `--configs-path`       | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) |   string   | `INFLUX_CONFIGS_PATH` |
+| `-c` | `--active-config`      | CLI configuration to use for command                                  |   string   |                       |
+|      | `--http-debug`         | Inspect communication with InfluxDB servers                           |   string   |                       |
+|      | `--json`               | Output data as JSON (default `false`)                                 |            | `INFLUX_OUTPUT_JSON`  |
+|      | `--hide-headers`       | Hide table headers (default `false`)                                  |            | `INFLUX_HIDE_HEADERS` |
+| `-t` | `--token`              | InfluxDB API token                                                    |   string   | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+### Create a new remote with InfluxDB Cloud
+
+```sh
+influx remote create \
+  --name myremote \
+  --org-id <OSS org ID> \
+  --token <OSS token> \
+  --remote-url <remote URL> \
+  --remote-api-token <remote token> \
+  --remote-org-id <remote ord ID>
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/remote/delete.md b/content/influxdb/v2.2/reference/cli/influx/remote/delete.md
new file mode 100644
index 000000000..846716ed6
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/remote/delete.md
@@ -0,0 +1,55 @@
+---
+title: influx remote delete
+description: Delete remote InfluxDB connections used for replicating data.
+menu:
+  influxdb_2_2_ref:
+    name: influx remote delete
+    parent: influx remote
+weight: 102
+influxdb/v2.2/tags: [write, replication]
+related:
+  - /influxdb/v2.2/reference/cli/influx/replication
+---
+
+{{% cloud %}}
+Replication remotes and replication streams can only be configured for InfluxDB OSS.
+{{% /cloud %}}
+
+The `influx remote delete` command delete an existing remote InfluxDB connection used for replication.
+
+## Usage
+```
+influx remote delete [command options] [arguments...]
+```
+
+## Flags
+
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+| :--- | :---------------- | :-------------------------------------------------------------------- | :--------: | :-------------------- |
+| `-i` | `--id`            | Remote connection ID to delete                                        |            |                       |
+|      | `--host`          | InfluxDB HTTP address (default `http://localhost:8086`)               |   string   | `INFLUX_HOST`         |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) |   string   | `INFLUX_CONFIGS_PATH` |
+| `-c` | `--active-config` | CLI configuration to use for command                                  |   string   |                       |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers                           |   string   |                       |
+|      | `--json`          | Output data as JSON (default `false`)                                 |            | `INFLUX_OUTPUT_JSON`  |
+|      | `--hide-headers`  | Hide table headers (default `false`)                                  |            | `INFLUX_HIDE_HEADERS` |
+| `-t` | `--token`         | InfluxDB API token                                                    |   string   | `INFLUX_TOKEN`        |
+
+## Examples
+{{< cli/influx-creds-note >}}
+
+### Delete a remote
+1. Use `influx remote list` to get the ID for the remote you want to delete.
+   ```sh
+   $ influx remote list --org-id <OSS org ID> --token <OSS token>
+   ID			        Name		Org ID
+   0ooxX0xxXo0x 	    myremote    [...]
+   ```
+2. Use the following command to delete the remote:
+    ```sh
+    influx remote delete \
+      --org-id <OSS org ID> \
+      --token <OSS token> \
+      --id 0ooxX0xxXo0x
+    ```
diff --git a/content/influxdb/v2.2/reference/cli/influx/remote/list.md b/content/influxdb/v2.2/reference/cli/influx/remote/list.md
new file mode 100644
index 000000000..ba158508f
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/remote/list.md
@@ -0,0 +1,57 @@
+---
+title: influx remote list
+description: List remote InfluxDB connections sued for replicating data.
+menu:
+  influxdb_2_2_ref:
+    name: influx remote list
+    parent: influx remote
+weight: 102
+influxdb/v2.2/tags: [write, replication]
+related:
+  - /influxdb/v2.2/reference/cli/influx/replication
+---
+
+{{% cloud %}}
+Replication remotes and replication streams can only be configured for InfluxDB OSS.
+{{% /cloud %}}
+
+The `influx remote list` command lists all remote InfluxDB connections used for replication.
+
+## Usage
+
+```
+influx remote list [command options] [arguments...]
+```
+
+## Flags
+
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+| :--- | :---------------- | :-------------------------------------------------------------------- | :--------: | :-------------------- |
+| `-n` | `--name`          | Filter remote connections by name                                     |            |                       |
+|      | `--org-id`        | Organization ID                                                       |   string   | `INFLUX_ORG_ID`       |
+| `-o` | `--org`           | Organization name                                                     |   string   | `INFLUX_ORG`          |
+|      | `--remote-url`    | Filter remote connections by remote URL                               |   string   |                       |
+|      | `--host`          | InfluxDB HTTP address (default `http://localhost:8086`)               |   string   | `INFLUX_HOST`         |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) |   string   | `INFLUX_CONFIGS_PATH` |
+| `-c` | `--active-config` | CLI configuration to use for command                                  |   string   |                       |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers                           |   string   |                       |
+|      | `--json`          | Output data as JSON (default `false`)                                 |            | `INFLUX_OUTPUT_JSON`  |
+|      | `--hide-headers`  | Hide table headers (default `false`)                                  |            | `INFLUX_HIDE_HEADERS` |
+| `-t` | `--token`         | InfluxDB API token                                                    |   string   | `INFLUX_TOKEN`        |
+
+
+## Examples
+{{< cli/influx-creds-note >}}
+
+### List all remotes
+
+```sh
+influx remote list
+```
+
+### List a specific remote by name
+
+```sh
+influx remote list --name example-name
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/remote/update.md b/content/influxdb/v2.2/reference/cli/influx/remote/update.md
new file mode 100644
index 000000000..43653519e
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/remote/update.md
@@ -0,0 +1,66 @@
+---
+title: influx remote update
+description: Update remote InfluxDB connections used for for replicating data.
+menu:
+  influxdb_2_2_ref:
+    name: influx remote update
+    parent: influx remote
+weight: 102
+influxdb/v2.2/tags: [write, replication]
+related:
+  - /influxdb/v2.2/reference/cli/influx/replication
+---
+
+
+{{% cloud %}}
+Replication remotes and replication streams can only be configured for InfluxDB OSS.
+{{% /cloud %}}
+
+The `influx remote update` command updates an existing InfluxDB remote connection used for replicating data.
+
+## Usage
+```
+influx remote update [command options] [arguments...]
+```
+
+## Flags
+
+| Flag |                        | Description                                                           | Input type | {{< cli/mapped >}}    |
+| :--- | ---------------------- | --------------------------------------------------------------------- | ---------- | --------------------- |
+| `-i` | `--id`                 | Remote connection ID to update                                        | string     |                       |
+| `-n` | `--name`               | New name for the remote connection                                    | string     |                       |
+| `-d` | `--description`        | New remote connection description                                     | string     |                       |
+|      | `--remote-url`         | New remote InfluxDB URL                                               | string     |                       |
+|      | `--remote-api-token`   | New remote InfluxDB API token                                         | string     |                       |
+|      | `--remote-org-id`      | New remote organization ID                                            | string     |                       |
+|      | `--allow-insecure-tls` | Allows insecure TLS connections                                       |            |                       |
+|      | `--host`               | InfluxDB HTTP address (default `http://localhost:8086`)               | string     | `INFLUX_HOST`         |
+|      | `--skip-verify`        | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+|      | `--configs-path`       | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+| `-c` | `--active-config`      | CLI configuration to use for command                                  | string     |                       |
+|      | `--http-debug`         | Inspect communication with InfluxDB servers                           | string     |                       |
+|      | `--json`               | Output data as JSON (default `false`)                                 |            | `INFLUX_OUTPUT_JSON`  |
+|      | `--hide-headers`       | Hide table headers (default `false`)                                  |            | `INFLUX_HIDE_HEADERS` |
+| `-t` | `--token`              | InfluxDB API token                                                    | string     | `INFLUX_TOKEN`        |
+
+## Example
+{{< cli/influx-creds-note >}}
+
+### Update a remote
+1. Use `influx remote list` to get the ID for the remote you want to update.
+   ```sh
+   $ influx remote list
+   ID			        Name		Org ID
+   0ooxX0xxXo0x 	    myremote    [...]
+   ```
+2. Use the following command to update the remote:
+    ```sh
+    influx remote remote \
+      --id 0ooxX0xxXo0x
+      --name new-example-name
+      --description new-examle-description
+      --remote-url http://new-example-url.com
+      --remote-api-token myN3wS3crE7t0k3n==
+      --remote-org-id new-example-org-id
+    ```
+
diff --git a/content/influxdb/v2.2/reference/cli/influx/repl/_index.md b/content/influxdb/v2.2/reference/cli/influx/repl/_index.md
new file mode 100644
index 000000000..c6dbd5d31
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/repl/_index.md
@@ -0,0 +1,44 @@
+---
+title: influx repl
+description: >
+  The `influx repl` command opens an interactive Read-Eval-Print Loop (REPL)
+  from which you can run Flux commands.
+influxdb/v2.2/tags: [query]
+related:
+  - /influxdb/v2.2/reference/cli/influx/#provide-required-authentication-credentials, influx CLI—Provide required authentication credentials
+  - /influxdb/v2.2/reference/cli/influx/#flag-patterns-and-conventions, influx CLI—Flag patterns and conventions
+---
+
+{{% warn %}}
+#### Removed in InfluxDB 2.0 beta-16
+The `influx repl` command was removed in **InfluxDB 2.0 beta-16**.
+To use the Flux REPL, build the REPL from source.
+For more information, see the [Flux GitHub repository](https://github.com/influxdata/flux/#readme).
+{{% /warn %}}
+
+The `influx repl` command opens an interactive Read-Eval-Print Loop (REPL)
+from which you can run Flux commands.
+
+## Usage
+```
+influx repl [flags]
+```
+
+{{% note %}}
+Use **ctrl + d** to exit the REPL.
+{{% /note %}}
+
+To use the Flux REPL, you must first authenticate with a [token](/influxdb/v2.2/security/tokens/view-tokens/).
+
+## Flags
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:----------:|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+| `-h` | `--help`          | Help for the `repl` command                                           |            |                       |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)            | string     | `INFLUX_HOST`         |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers.                          | string     |                       |
+| `-o` | `--org`           | Organization name (mutually exclusive with `--org-id`)                | string     | `INFLUX_ORG`          |
+|      | `--org-id`        | Organization ID (mutually exclusive with `--org`)                     | string     | `INFLUX_ORG_ID`       |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`         | API token                                                             | string     | `INFLUX_TOKEN`        |
diff --git a/content/influxdb/v2.2/reference/cli/influx/replication/_index.md b/content/influxdb/v2.2/reference/cli/influx/replication/_index.md
new file mode 100644
index 000000000..9190db61c
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/replication/_index.md
@@ -0,0 +1,33 @@
+---
+title: influx replication
+description: Use the `influx` CLI to manage InfluxDB replication streams.
+menu:
+  influxdb_2_2_ref:
+    name: influx replication
+    parent: influx
+weight: 101
+influxdb/v2.2/tags: [write, replication]
+related:
+  - /influxdb/v2.2/reference/cli/influx/remote
+---
+
+The `influx replication` command and its subcommands manage InfluxDB replication streams.
+
+## Usage
+```
+influx replication [commond options] [arguments...]
+```
+
+## Subcommands
+| Subcommand                                                       | Description                              |
+| :--------------------------------------------------------------- | :--------------------------------------- |
+| [create](/influxdb/v2.2/reference/cli/influx/replication/create) | Create a new replication stream          |
+| [delete](/influxdb/v2.2/reference/cli/influx/replication/delete) | Delete a replication stream              |
+| [list](/influxdb/v2.2/reference/cli/influx/replication/list)     | List all replication streams and metrics |
+| [update](/influxdb/v2.2/reference/cli/influx/replication/update) | Update a replication stream              |
+
+## Flags
+| Flag |          | Description                        |
+| :--- | :------- | :--------------------------------- |
+| `-h` | `--help` | Help for the `replication` command |
+
diff --git a/content/influxdb/v2.2/reference/cli/influx/replication/create.md b/content/influxdb/v2.2/reference/cli/influx/replication/create.md
new file mode 100644
index 000000000..9d5f941d8
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/replication/create.md
@@ -0,0 +1,70 @@
+---
+title: influx replication create
+description: Create a new InfluxDB replication stream.
+menu:
+  influxdb_2_2_ref:
+    name: influx replication create
+    parent: influx replication
+weight: 101
+influxdb/v2.2/tags: [write]
+related:
+  - /influxdb/v2.2/reference/cli/influx/replication
+---
+
+{{% cloud %}}
+Replication remotes and replication streams can only be configured for InfluxDB OSS.
+{{% /cloud %}}
+
+
+The `influx replication create` command creates a new InfluxDB replication stream.
+
+## Usage
+```   
+influx replication create [command options] [arguments...]
+```
+
+## Flags
+
+| Flag |                                | Description                                                           | Input type | {{< cli/mapped >}}    |
+| :--- | :----------------------------- | :-------------------------------------------------------------------- | :--------: | :-------------------- |
+| `-n` | `--name`                       | Replication stream name                                               |   string   |                       |
+| `-d` | `--description`                | Replication stream description                                        |   string   |                       |
+|      | `--org-id`                     | Local organization ID                                                 |   string   | `INFLUX_ORG_ID`       |
+| `-o` | `--org`                        | Local organization name                                               |   string   | `INFLUX_ORG`          |
+|      | `--remote-id`                  | Remote connection ID to replicate data to                             |   string   |                       |
+|      | `--local-bucket-id`               | Local bucket ID to replicate data from                                |   string   |                       |
+|      | `--remote-bucket-id`              | Remote bucket ID to replicate data to                                 |   string   |                       |
+|      | `--max-queue-bytes`            | Max queue size in bytes (default: `67108860`)                         |  integer   |                       |
+|      | `--drop-non-retryable-data`    | Drop data when a non-retryable error is encountered                   |            |                       |
+|      | `--no-drop-non-retryable-data` | Do not drop data when a non-retryable error is encountered            |            |                       |
+|      | `--max-age`                    | Specify a maximum age (in seconds) for data before it is dropped      |  integer   |                       |
+|      | `--host`                       | InfluxDB HTTP address (default `http://localhost:8086`)               |   string   | `INFLUX_HOST`         |
+|      | `--skip-verify`                | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+|      | `--configs-path`               | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) |   string   | `INFLUX_CONFIGS_PATH` |
+| `-c` | `--active-config`              | CLI configuration to use for command                                  |   string   |                       |
+|      | `--http-debug`                 | Inspect communication with InfluxDB servers                           |   string   |                       |
+|      | `--json`                       | Output data as JSON (default `false`)                                 |            | `INFLUX_OUTPUT_JSON`  |
+|      | `--hide-headers`               | Hide table headers (default `false`)                                  |            | `INFLUX_HIDE_HEADERS` |
+| `-t` | `--token`                      | InfluxDB API token                                                    |   string   | `INFLUX_TOKEN`        |
+
+
+## Examples
+{{< cli/influx-creds-note >}}
+
+### Create a replication stream
+
+1. [Create a remote connection](/influxdb/v2.2/reference/cli/influx/remote/create/), if you haven't already.
+2. Use `influx remote list` to get the ID for the remote you want to replicate data to.
+   ```sh
+   $ influx remote list
+   ID			        Name		Org ID
+   0ooxX0xxXo0x 	    myremote    [...]
+   ```
+3. Create the replication:
+   ```sh
+   influx replication create \
+     --name myreplication
+     --local-bucket example-local-bucket
+     --remote-bucket example-remote-bucket
+     --remote-id 0ooxX0xxXo0x
+   ```
diff --git a/content/influxdb/v2.2/reference/cli/influx/replication/delete.md b/content/influxdb/v2.2/reference/cli/influx/replication/delete.md
new file mode 100644
index 000000000..6b04d0f29
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/replication/delete.md
@@ -0,0 +1,52 @@
+---
+title: influx replication delete
+description: Delete an InfluxDB replication stream.
+menu:
+  influxdb_2_2_ref:
+    name: influx replication delete
+    parent: influx replication
+weight: 102
+influxdb/v2.2/tags: [write, replication]
+related:
+  - /influxdb/v2.2/reference/cli/influx/replication
+---
+
+{{% cloud %}}
+Replication remotes and replication streams can only be configured for InfluxDB OSS.
+{{% /cloud %}}
+
+The `influx replication delete` command deletes an InfluxDB replication stream.
+
+## Usage
+   
+```
+influx replication delete [command options] [arguments...]
+```
+
+## Flags
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+| :--- | :---------------- | :-------------------------------------------------------------------- | :--------: | :-------------------- |
+| `-i` | `--id`            | Replication stream ID to delete                                       |   string   |                       |
+|      | `--host`          | InfluxDB HTTP address (default `http://localhost:8086`)               |   string   | `INFLUX_HOST`         |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) |   string   | `INFLUX_CONFIGS_PATH` |
+| `-c` | `--active-config` | CLI configuration to use for command                                  |   string   |                       |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers                           |   string   |                       |
+|      | `--json`          | Output data as JSON (default `false`)                                 |            | `INFLUX_OUTPUT_JSON`  |
+|      | `--hide-headers`  | Hide table headers (default `false`)                                  |            | `INFLUX_HIDE_HEADERS` |
+| `-t` | `--token`         | InfluxDB API token                                                    |   string   | `INFLUX_TOKEN`        |
+
+## Examples
+{{< cli/influx-creds-note >}}
+
+### Delete a replication
+1. Use `influx replication list` to get the ID for the replication you want to delete.
+   ```sh
+   $ influx replication list
+   ID			        Name		Org ID
+   0ooxX0xxXo0x      	    myreplication    [...]
+   ```
+2. Use the following command to delete the replication:
+    ```sh
+    influx replication delete --id 0ooxX0xxXo0x
+    ```
diff --git a/content/influxdb/v2.2/reference/cli/influx/replication/list.md b/content/influxdb/v2.2/reference/cli/influx/replication/list.md
new file mode 100644
index 000000000..c0a4eea4e
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/replication/list.md
@@ -0,0 +1,56 @@
+---
+title: influx replication list
+description: List InfluxDB replication streams and corresponding metrics.
+menu:
+  influxdb_2_2_ref:
+    name: influx replication list
+    parent: influx replication
+weight: 102
+influxdb/v2.2/tags: [write, replication]
+related:
+  - /influxdb/v2.2/reference/cli/influx/replication
+---
+
+{{% cloud %}}
+Replication remotes and replication streams can only be configured for InfluxDB OSS.
+{{% /cloud %}}
+
+
+The `influx replication list` command lists all InfluxDB replication streams and their corresponding metrics.
+
+## Usage
+```
+influx replication list [command options] [arguments...]
+```
+
+## Flags
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+| :--- | :---------------- | :-------------------------------------------------------------------- | :--------: | :-------------------- |
+| `-n` | `--name`          | Filter replication streams by name                                    |   string   |                       |
+|      | `--org-id`        | Local organization ID                                                 |   string   | `INFLUX_ORG_ID`       |
+| `-o` | `--org`           | Local organization name                                               |   string   | `INFLUX_ORG`          |
+|      | `--remote-id`     | Filter replication streams by remote connection ID                    |   string   |                       |
+|      | `--local-bucket-id`  | Filter replication streams by local bucket                            |   string   |                       |
+|      | `--host`          | InfluxDB HTTP address (default `http://localhost:8086`)               |   string   | `INFLUX_HOST`         |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) |   string   | `INFLUX_CONFIGS_PATH` |
+| `-c` | `--active-config` | CLI configuration to use for command                                  |   string   |                       |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers                           |   string   |                       |
+|      | `--json`          | Output data as JSON (default `false`)                                 |            | `INFLUX_OUTPUT_JSON`  |
+|      | `--hide-headers`  | Hide table headers (default `false`)                                  |            | `INFLUX_HIDE_HEADERS` |
+| `-t` | `--token`         | InfluxDB API token                                                    |   string   | `INFLUX_TOKEN`        |
+
+## Examples
+{{< cli/influx-creds-note >}}
+
+### List all replication streams
+
+```sh
+influx replication list --org-id <OSS org ID> --token <OSS token>
+```
+
+### List a replication stream by name
+
+```sh
+influx replication list --name example-replication-name
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/replication/update.md b/content/influxdb/v2.2/reference/cli/influx/replication/update.md
new file mode 100644
index 000000000..2ba1c796b
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/replication/update.md
@@ -0,0 +1,66 @@
+---
+title: influx replication update
+description: Update InfluxDB replication streams.
+menu:
+  influxdb_2_2_ref:
+    name: influx replication update
+    parent: influx replication
+weight: 102
+influxdb/v2.2/tags: [write, replication]
+related:
+  - /influxdb/v2.2/reference/cli/influx/replication
+---
+
+{{% cloud %}}
+Replication remotes and replication streams can only be configured for InfluxDB OSS.
+{{% /cloud %}}
+
+The `influx replication update` command updates an InfluxDB replication stream.
+
+## Usage
+```
+influx replication update [command options] [arguments...]
+```
+
+## Flag 
+  
+| Flag |                                | Description                                                           | Input type | {{< cli/mapped >}}    |
+| :--- | :----------------------------- | :-------------------------------------------------------------------- | :--------: | :-------------------- |
+| `-i` | `--id`                         | Replication stream ID to update                                       |   string   |                       |
+| `-n` | `--name`                       | New replication stream name                                           |   string   |                       |
+| `-d` | `--description`                | New replication stream description                                    |   string   |                       |
+|      | `--remote-id`                  | New remote connection ID to send data to                              |   string   |                       |
+|      | `--remote-bucket-id`              | New remote bucket ID to replicate data to                             |   string   |                       |
+|      | `--max-queue-bytes`            | New max queue size in bytes (default: `0`)                            |  integer   |                       |
+|      | `--drop-non-retryable-data`    | Drop data when a non-retryable error is encountered                   |            |                       |
+|      | `--no-drop-non-retryable-data` | Do not drop data when a non-retryable error is encountered            |            |                       |
+|      | `--max-age`                    | Specify a maximum age (in seconds) for data before it is dropped      |  integer   |                       |
+|      | `--host`                       | InfluxDB HTTP address (default `http://localhost:8086`)               |   string   | `INFLUX_HOST`         |
+|      | `--skip-verify`                | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+|      | `--configs-path`               | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) |   string   | `INFLUX_CONFIGS_PATH` |
+| `-c` | `--active-config`              | CLI configuration to use for command                                  |   string   |                       |
+|      | `--http-debug`                 | Inspect communication with InfluxDB servers                           |   string   |                       |
+|      | `--json`                       | Output data as JSON (default `false`)                                 |            | `INFLUX_OUTPUT_JSON`  |
+|      | `--hide-headers`               | Hide table headers (default `false`)                                  |            | `INFLUX_HIDE_HEADERS` |
+| `-t` | `--token`                      | InfluxDB API token                                                    |   string   | `INFLUX_TOKEN`        |
+
+## Example
+{{< cli/influx-creds-note >}}
+
+### Update a replication
+1. Use `influx replication list` to get the ID for the replication you want to update.
+   ```sh
+   $ influx replication list
+   ID			        Name		Org ID
+   0ooxX0xxXo0x      	    myreplication    [...]
+   ```
+2. Use the following command to update the replication:
+    ```sh
+    influx replication update \
+      --id 0ooxX0xxXo0x
+      --name new-replication-name
+      --description new-replication-description
+      --replication-url http://new-replication-url.com
+      --replication-api-token new-replication-api-token
+      --replication-org-id new-replication-org-id
+    ```
diff --git a/content/influxdb/v2.2/reference/cli/influx/restore/index.md b/content/influxdb/v2.2/reference/cli/influx/restore/index.md
new file mode 100644
index 000000000..92bef17c3
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/restore/index.md
@@ -0,0 +1,96 @@
+---
+title: influx restore
+description: The `influx restore` command restores backup data and metadata from an InfluxDB backup directory.
+influxdb/v2.2/tags: [restore]
+menu:
+  influxdb_2_2_ref:
+    parent: influx
+weight: 101
+aliases:
+  - /influxdb/v2.2/reference/cli/influxd/restore/
+  - /influxdb/v2.2/administration/backup_and_restore/
+related:
+  - /influxdb/v2.2/backup-restore/restore/
+  - /influxdb/v2.2/reference/cli/influx/backup/
+  - /influxdb/v2.2/reference/cli/influx/#provide-required-authentication-credentials, influx CLI—Provide required authentication credentials
+  - /influxdb/v2.2/reference/cli/influx/#flag-patterns-and-conventions, influx CLI—Flag patterns and conventions
+metadata: [influx CLI 2.0.0+, InfluxDB 2.0.0+]
+updated_in: CLI v2.0.7
+---
+
+The `influx restore` command restores backup data and metadata from an InfluxDB OSS backup directory.
+
+### The restore process
+When restoring data from a backup file set, InfluxDB temporarily moves existing
+data and metadata while `restore` runs.
+After `restore` completes, the temporary data is deleted.
+If the restore process fails, InfluxDB preserves the data in the temporary location.
+
+_For information about recovering from a failed restore process, see
+[Restore data](/influxdb/v2.2/backup-restore/restore/#recover-from-a-failed-restore)._
+
+{{% note %}}
+#### Cannot restore to existing buckets
+The `influx restore` command cannot restore data to existing buckets.
+Use the `--new-bucket` flag to create a bucket with a new name and restore data into it.
+To restore data and retain bucket names, [delete existing buckets](/influxdb/v2.2/organizations/buckets/delete-bucket/)
+and then begin the restore process.
+{{% /note %}}
+
+## Usage
+
+```
+influx restore [flags]
+```
+
+## Flags
+
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:----------:|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string     |                       |
+| `-b` | `--bucket`        | Name of the bucket to restore (mutually exclusive with `--bucket-id`) | string     |                       |
+|      | `--bucket-id`     | ID of the bucket to restore (mutually exclusive with `--bucket`)      | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+|      | `--full`          | Fully restore and replace all data on server                          |            |                       |
+| `-h` | `--help`          | Help for the `restore` command                                        |            |                       |
+|      | `--hide-headers`  | Hide table headers (default `false`)                                  |            | `INFLUX_HIDE_HEADERS` |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)            | string     | `INFLUX_HOST`         |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers.                          | string     |                       |
+|      | `--json`          | Output data as JSON (default `false`)                                 |            | `INFLUX_OUTPUT_JSON`  |
+|      | `--new-bucket`    | Name of the bucket to restore to                                      | string     |                       |
+|      | `--new-org`       | Name of the organization to restore to                                | string     |                       |
+| `-o` | `--org`           | Organization name (mutually exclusive with `--org-id`)                | string     |                       |
+|      | `--org-id`        | Organization ID (mutually exclusive with `--org`)                     | string     |                       |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`         | API token                                                             | string     | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+- [Restore backup data](#restore-backup-data)
+- [Restore backup data for a specific bucket into a new bucket](#restore-backup-data-for-a-specific-bucket-into-a-new-bucket)
+- [Restore and replace all data](#restore-and-replace-all-data)
+
+##### Restore backup data
+```sh
+influx restore /path/to/backup/dir/
+```
+
+##### Restore backup data for a specific bucket into a new bucket
+```sh
+influx restore \
+  --bucket example-bucket \
+  --new-bucket new-example-bucket \
+  /path/to/backup/dir/
+```
+
+##### Restore and replace all data
+{{% note %}}
+`influx restore --full` restores all time series data _and_ InfluxDB key-value
+data such as tokens, dashboards, users, etc.
+{{% /note %}}
+
+```sh
+influx restore --full /path/to/backup/dir/
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/secret/_index.md b/content/influxdb/v2.2/reference/cli/influx/secret/_index.md
new file mode 100644
index 000000000..6620dbcf8
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/secret/_index.md
@@ -0,0 +1,36 @@
+---
+title: influx secret
+description: The `influx secret` command manages secrets.
+menu:
+  influxdb_2_2_ref:
+    name: influx secret
+    parent: influx
+weight: 101
+influxdb/v2.2/tags: [secrets]
+cascade:
+  related:
+    - /influxdb/v2.2/security/secrets/
+    - /influxdb/v2.2/reference/cli/influx/#provide-required-authentication-credentials, influx CLI—Provide required authentication credentials
+    - /influxdb/v2.2/reference/cli/influx/#flag-patterns-and-conventions, influx CLI—Flag patterns and conventions
+  metadata: [influx CLI 2.0.0+, InfluxDB 2.0.0+]
+---
+
+The `influx secret` command manages [secrets](/influxdb/v2.2/reference/glossary/#secret).
+
+## Usage
+```
+influx secret [flags]
+influx secret [subcommand]
+```
+
+## Subcommands
+| Subcommand                                                   | Description            |
+|:----------                                                   |:-----------            |
+| [delete](/influxdb/v2.2/reference/cli/influx/secret/delete/) | Delete a secret        |
+| [list](/influxdb/v2.2/reference/cli/influx/secret/list/)     | List secrets           |
+| [update](/influxdb/v2.2/reference/cli/influx/secret/update/) | Add or update a secret |
+
+## Flags
+| Flag |          | Description                   |
+|:---- |:---      |:-----------                   |
+| `-h` | `--help` | Help for the `secret` command |
diff --git a/content/influxdb/v2.2/reference/cli/influx/secret/delete.md b/content/influxdb/v2.2/reference/cli/influx/secret/delete.md
new file mode 100644
index 000000000..880ab0767
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/secret/delete.md
@@ -0,0 +1,42 @@
+---
+title: influx secret delete
+description: The `influx secret delete` command deletes secrets.
+menu:
+  influxdb_2_2_ref:
+    name: influx secret delete
+    parent: influx secret
+weight: 101
+influxdb/v2.2/tags: [secrets]
+---
+
+The `influx secret delete` command deletes secrets.
+
+## Usage
+```
+influx secret delete [flags]
+```
+
+## Flags
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:----------:|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+| `-h` | `--help`          | Help for the `delete` command                                         |            |                       |
+|      | `--hide-headers`  | Hide table headers (default `false`)                                  |            | `INFLUX_HIDE_HEADERS` |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)            | string     | `INFLUX_HOST`         |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers.                          | string     |                       |
+|      | `--json`          | Output data as JSON (default `false`)                                 |            | `INFLUX_OUTPUT_JSON`  |
+| `-k` | `--key`           | ({{< req >}}) Secret key                                              | string     |                       |
+| `-o` | `--org`           | Organization name (mutually exclusive with `--org-id`)                | string     | `INFLUX_ORG`          |
+|      | `--org-id`        | Organization ID (mutually exclusive with `--org`)                     | string     | `INFLUX_ORG_ID`       |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`         | API token                                                             | string     | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### Delete a secret
+```sh
+influx secret delete --key EXAMPLE_SECRET_KEY
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/secret/list.md b/content/influxdb/v2.2/reference/cli/influx/secret/list.md
new file mode 100644
index 000000000..ea6f2308a
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/secret/list.md
@@ -0,0 +1,44 @@
+---
+title: influx secret list
+description: The `influx secret list` command lists secret keys.
+menu:
+  influxdb_2_2_ref:
+    name: influx secret list
+    parent: influx secret
+weight: 101
+influxdb/v2.2/tags: [secrets]
+---
+
+The `influx secret list` command lists secret keys.
+
+## Usage
+```
+influx secret list [flags]
+```
+
+#### Command aliases
+`list`, `ls`, `find`
+
+## Flags
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:----------:|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+| `-h` | `--help`          | Help for the `list` command                                           |            |                       |
+|      | `--hide-headers`  | Hide table headers (default `false`)                                  |            | `INFLUX_HIDE_HEADERS` |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)            | string     | `INFLUX_HOST`         |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers.                          | string     |                       |
+|      | `--json`          | Output data as JSON (default `false`)                                 |            | `INFLUX_OUTPUT_JSON`  |
+| `-o` | `--org`           | Organization name (mutually exclusive with `--org-id`)                | string     | `INFLUX_ORG`          |
+|      | `--org-id`        | Organization ID (mutually exclusive with `--org`)                     | string     | `INFLUX_ORG_ID`       |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`         | API token                                                             | string     | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### List all secret keys
+```sh
+influx secret list
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/secret/update.md b/content/influxdb/v2.2/reference/cli/influx/secret/update.md
new file mode 100644
index 000000000..d0fcd4f06
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/secret/update.md
@@ -0,0 +1,61 @@
+---
+title: influx secret update
+description: The `influx secret update` command adds and updates secrets.
+menu:
+  influxdb_2_2_ref:
+    name: influx secret update
+    parent: influx secret
+weight: 101
+influxdb/v2.2/tags: [secrets]
+---
+
+The `influx secret update` command adds and updates secrets.
+Provide the secret key with the `-k` or `--key` flag.
+You may also provide the secret value with the `-v` or `--value` flag.
+If you do not provide the secret value with the `-v` or `--value` flag,
+enter the value when prompted.
+
+{{% warn %}}
+Providing a secret value with the `-v` or `--value` flag may expose the secret
+in your command history.
+{{% /warn %}}
+
+## Usage
+```
+influx secret update [flags]
+```
+
+## Flags
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:----------:|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+| `-h` | `--help`          | Help for the `update` command                                         |            |                       |
+|      | `--hide-headers`  | Hide table headers (default `false`)                                  |            | `INFLUX_HIDE_HEADERS` |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)            | string     | `INFLUX_HOST`         |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers.                          | string     |                       |
+|      | `--json`          | Output data as JSON (default `false`)                                 |            | `INFLUX_OUTPUT_JSON`  |
+| `-k` | `--key`           | ({{< req >}}) Secret key                                              | string     |                       |
+| `-o` | `--org`           | Organization name (mutually exclusive with `--org-id`)                | string     | `INFLUX_ORG`          |
+|      | `--org-id`        | Organization ID (mutually exclusive with `--org`)                     | string     | `INFLUX_ORG_ID`       |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`         | API token                                                             | string     | `INFLUX_TOKEN`        |
+| `-v` | `--value`         | ({{< req >}}) Secret value                                            | string     |                       |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### Add a secret
+```sh
+influx secret update \
+  --key EXAMPLE_KEY \
+  --value EXAMPLE_VALUE
+```
+
+##### Update an existing secret
+```sh
+influx secret update \
+  --key EXAMPLE_KEY \
+  --value NEW_EXAMPLE_VALUE
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/server-config/_index.md b/content/influxdb/v2.2/reference/cli/influx/server-config/_index.md
new file mode 100644
index 000000000..01a3c77f7
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/server-config/_index.md
@@ -0,0 +1,53 @@
+---
+title: influx server-config
+description: The `influx server-config` command displays the runtime server configuration.
+menu:
+  influxdb_2_2_ref:
+    name: influx server-config
+    parent: influx
+weight: 101
+influxdb/v2.2/tags: [config]
+cascade:
+  related:
+    - /influxdb/v2.2/reference/cli/influx/#provide-required-authentication-credentials, influx CLI—Provide required authentication credentials
+    - /influxdb/v2.2/reference/cli/influx/#flag-patterns-and-conventions, influx CLI—Flag patterns and conventions
+  metadata: [influx CLI 2.0.0+, InfluxDB 2.0.0+]
+---
+
+The `influx server-config` command displays the InfluxDB runtime [server configuration](/influxdb/v2.2/reference/config-options/).
+
+{{% note %}}
+To display the server configuration, you must use an [operator token](/influxdb/v2.2/security/tokens/#operator-token).
+{{% /note %}}
+
+## Usage
+```
+influx server-config [flags]
+influx server-config [command]
+```
+
+## Examples
+```sh
+# Show the server configuration.
+influx server-config
+
+# Show the server configuration as YAML.
+influx server-config --yaml
+```
+
+## Flags
+| Flag |          | Description                   |
+|:---- |:---      |:-----------                   |
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+| `-h` | `--help`          | Help for the `list` command                                           |            |                       |
+|      | `--hide-headers`  | Hide table headers (default `false`)                                  |            | `INFLUX_HIDE_HEADERS` |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)            | string     | `INFLUX_HOST`         |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers                          | string     |                       |
+| `-i` | `--id`            | Organization ID                                                       | string     | `INFLUX_ORG`          |
+|      | `--json`          | Output data as JSON (default `false`)                                 |            | `INFLUX_OUTPUT_JSON`  |
+| `-n` | `--name`          | Organization name                                                     | string     | `INFLUX_ORG_ID`       |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`         | API token                                                             | string     | `INFLUX_TOKEN`        |
+|      | `--toml` | Output configuration as TOML instead of JSON |
+|      | `--yaml` | Output configuration as YAML instead of JSON |
diff --git a/content/influxdb/v2.2/reference/cli/influx/setup/_index.md b/content/influxdb/v2.2/reference/cli/influx/setup/_index.md
new file mode 100644
index 000000000..3cbe911f1
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/setup/_index.md
@@ -0,0 +1,70 @@
+---
+title: influx setup
+description: >
+  The `influx setup` command walks through the initial InfluxDB OSS setup process,
+  creating a default user, organization, and bucket.
+menu:
+  influxdb_2_2_ref:
+    name: influx setup
+    parent: influx
+weight: 101
+influxdb/v2.2/tags: [get-started]
+related:
+  - /influxdb/v2.2/reference/cli/influx/#provide-required-authentication-credentials, influx CLI—Provide required authentication credentials
+  - /influxdb/v2.2/reference/cli/influx/#flag-patterns-and-conventions, influx CLI—Flag patterns and conventions
+metadata: [influx CLI 2.0.0+, InfluxDB 2.0.0+]
+updated_in: CLI v2.0.3
+canonical: /{{< latest "influxdb" "v2" >}}/reference/cli/influx/setup/
+---
+
+The `influx setup` command walks through the initial InfluxDB OSS setup process,
+creating a default user, organization, and bucket.
+
+{{% note %}}
+The **Operator token** created in the InfluxDB setup process has full read and write
+access to all organizations in the database.
+{{% /note %}}
+
+## Usage
+```
+influx setup [flags]
+```
+
+## Flags
+| Flag |                   | Description                                                           | Data type | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:---------:|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string    |                       |
+| `-b` | `--bucket`        | Primary bucket name                                                   | string    |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string    | `INFLUX_CONFIGS_PATH` |
+| `-f` | `--force`         | Skip confirmation prompt                                              |           |                       |
+| `-h` | `--help`          | Help for the `setup` command                                          |           |                       |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)            | string    | `INFLUX_HOST`         |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers.                          | string    |                       |
+| `-o` | `--org`           | Primary organization name                                             | string    |                       |
+| `-p` | `--password`      | Password for primary user                                             | string    |                       |
+| `-r` | `--retention`     | Duration bucket will retain data (0 is infinite, default is 0)        | duration  |                       |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |           | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`         | Token for admin user (auto-generated by default)                      | string    | `INFLUX_TOKEN`        |
+| `-u` | `--username`      | Primary username                                                      | string    |                       |
+
+{{% note %}}
+Valid `--retention` units are nanoseconds (`ns`), microseconds (`us` or `µs`),
+milliseconds (`ms`), seconds (`s`), minutes (`m`), hours (`h`), days (`d`), and weeks (`w`).
+{{% /note %}}
+
+## Examples
+
+##### Start interactive InfluxDB setup
+```sh
+influx setup
+```
+
+##### Set up InfluxDB with all required information and skip confirmation
+```sh
+influx setup \
+  --org example-org \
+  --bucket example-bucket \
+  --username example-user \
+  --password ExAmPl3PA55W0rD \
+  --force  
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/stacks/_index.md b/content/influxdb/v2.2/reference/cli/influx/stacks/_index.md
new file mode 100644
index 000000000..296382d87
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/stacks/_index.md
@@ -0,0 +1,79 @@
+---
+title: influx stacks
+description: >
+  The `influx stacks` command and its subcommands list and manage InfluxDB stacks
+  and associated resources.
+menu:
+  influxdb_2_2_ref:
+    name: influx stacks
+    parent: influx
+weight: 101
+aliases:
+  - /influxdb/v2.2/reference/cli/influx/pkg/stack/list/
+influxdb/v2.2/tags: [templates]
+cascade:
+  related:
+    - /influxdb/v2.2/influxdb-templates/stacks/
+    - /influxdb/v2.2/reference/cli/influx/#provide-required-authentication-credentials, influx CLI—Provide required authentication credentials
+    - /influxdb/v2.2/reference/cli/influx/#flag-patterns-and-conventions, influx CLI—Flag patterns and conventions
+  metadata: [influx CLI 2.0.1+, InfluxDB 2.0.1+]
+---
+
+The `influx stacks` command and its subcommands list and manage InfluxDB stacks
+and associated resources.
+
+## Usage
+```
+influx stacks [flags]
+influx stacks [command]
+```
+
+## Subcommands
+| Subcommand                                                   | Description        |
+|:-------                                                      |:-----------        |
+| [init](/influxdb/v2.2/reference/cli/influx/stacks/init/)     | Initialize a stack |
+| [remove](/influxdb/v2.2/reference/cli/influx/stacks/remove/) | Remove a stack     |
+
+## Flags
+| Flag |                   | Description                                                           | Input type  | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:-----------:|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string      |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string      | `INFLUX_CONFIGS_PATH` |
+| `-h` | `--help`          | Help for the `stacks` command                                         |             |                       |
+|      | `--hide-headers`  | Hide table headers (default `false`)                                  |             | `INFLUX_HIDE_HEADERS` |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)            | string      | `INFLUX_HOST`         |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers.                          | string      |                       |
+|      | `--json`          | Output data as JSON (default `false`)                                 |             | `INFLUX_OUTPUT_JSON`  |
+| `-o` | `--org`           | Organization name (mutually exclusive with `--org-id`)                | string      | `INFLUX_ORG`          |
+|      | `--org-id`        | Organization ID (mutually exclusive with `--org`)                     | string      | `INFLUX_ORG_ID`       |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |             | `INFLUX_SKIP_VERIFY`  |
+|      | `--stack-id`      | Stack IDs to filter by                                                | stringArray |                       |
+|      | `--stack-name`    | Stack names to filter by                                              | stringArray |                       |
+| `-t` | `--token`         | API token                                                             | string      | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+- [List all stacks](#list-all-stacks)
+- [Filter stacks by name](#filter-stacks-by-name)
+- [Filter stacks by ID](#filter-stacks-by-id)
+
+##### List all stacks
+```sh
+influx stacks
+```
+
+##### Filter stacks by name
+```sh
+influx stacks \
+  --stack-name stack1 \
+  --stack-name stack2
+```
+
+##### Filter stacks by ID
+```sh
+influx stacks \
+  --stack-id 0Xx0oox00XXoxxoo1 \
+  --stack-id 0Xx0oox00XXoxxoo2
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/stacks/init.md b/content/influxdb/v2.2/reference/cli/influx/stacks/init.md
new file mode 100644
index 000000000..a69da4b42
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/stacks/init.md
@@ -0,0 +1,53 @@
+---
+title: influx stacks init
+description: The `influx stacks init` command initializes an InfluxDB stack.
+menu:
+  influxdb_2_2_ref:
+    name: influx stacks init
+    parent: influx stacks
+weight: 201
+aliases:
+  - /influxdb/v2.2/reference/cli/influx/pkg/stack/init/
+influxdb/v2.2/tags: [templates]
+---
+
+The `influx stacks init` command initializes an InfluxDB stack.
+
+## Usage
+```
+influx stacks init [flags]
+```
+
+## Flags
+| Flag |                       | Description                                                           | Input type      | {{< cli/mapped >}}    |
+|:-----|:----------------------|:----------------------------------------------------------------------|:---------------:|:----------------------|
+| `-c` | `--active-config`     | CLI configuration to use for command                                  | string          |                       |
+|      | `--configs-path`      | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string          | `INFLUX_CONFIGS_PATH` |
+| `-h` | `--help`              | Help for the `init` command                                           |                 |                       |
+|      | `--hide-headers`      | Hide table headers (default `false`)                                  |                 | `INFLUX_HIDE_HEADERS` |
+|      | `--host`              | HTTP address of InfluxDB (default `http://localhost:8086`)            | string          | `INFLUX_HOST`         |
+|      | `--http-debug`        | Inspect communication with InfluxDB servers.                          | string          |                       |
+|      | `--json`              | Output data as JSON (default `false`)                                 |                 | `INFLUX_OUTPUT_JSON`  |
+| `-o` | `--org`               | Organization name (mutually exclusive with `--org-id`)                | string          | `INFLUX_ORG`          |
+|      | `--org-id`            | Organization ID (mutually exclusive with `--org`)                     | string          | `INFLUX_ORG_ID`       |
+|      | `--skip-verify`       | Skip TLS certificate verification                                     |                 | `INFLUX_SKIP_VERIFY`  |
+| `-d` | `--stack-description` | Stack description                                                     | string          |                       |
+| `-n` | `--stack-name`        | Stack name                                                            | string          |                       |
+| `-u` | `--template-url`      | Template URLs to associate with a stack                               | list of strings |                       |
+| `-t` | `--token`             | API token                                                             | string          | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### Initialize a stack with a name and description
+
+```sh
+influx stack init -n "Example Stack" -d "InfluxDB stack for monitoring some awesome stuff"
+```
+
+##### Initialize a stack with a name and URLs to associate with the stack
+
+```sh
+influx stack init -n "Example Stack" -u https://example.com/template-1.yml
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/stacks/remove.md b/content/influxdb/v2.2/reference/cli/influx/stacks/remove.md
new file mode 100644
index 000000000..42fc7d869
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/stacks/remove.md
@@ -0,0 +1,48 @@
+---
+title: influx stacks remove
+description: The `influx stacks remove` command removes an InfluxDB stack and all associated resources.
+menu:
+  influxdb_2_2_ref:
+    name: influx stacks remove
+    parent: influx stacks
+weight: 201
+aliases:
+  - /influxdb/v2.2/reference/cli/influx/pkg/stack/remove/
+influxdb/v2.2/tags: [templates]
+---
+
+The `influx stacks remove` command removes an InfluxDB stack and all associated resources.
+
+## Usage
+```
+influx stacks remove [flags]
+```
+
+#### Command aliases
+`remove`, `rm`, `uninstall`
+
+## Flags
+| Flag |                   | Description                                                           | Input type      | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:---------------:|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string          |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string          | `INFLUX_CONFIGS_PATH` |
+|      | `--force`         | Skip confirmation prompt.                                             |                 |                       |
+| `-h` | `--help`          | Help for the `remove` command                                         |                 |                       |
+|      | `--hide-headers`  | Hide table headers (default `false`)                                  |                 | `INFLUX_HIDE_HEADERS` |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)            | string          | `INFLUX_HOST`         |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers.                          | string          |                       |
+|      | `--json`          | Output data as JSON (default `false`)                                 |                 | `INFLUX_OUTPUT_JSON`  |
+| `-o` | `--org`           | Organization name (mutually exclusive with `--org-id`)                | string          | `INFLUX_ORG`          |
+|      | `--org-id`        | Organization ID (mutually exclusive with `--org`)                     | string          | `INFLUX_ORG_ID`       |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |                 | `INFLUX_SKIP_VERIFY`  |
+|      | `--stack-id`      | Stack IDs to remove                                                   | list of strings |                       |
+| `-t` | `--token`         | API token                                                             | string          | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### Remove a stack and all of its associated resources
+```sh
+influx stacks remove --stack-id 0Xx0oox00XXoxxoo1
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/stacks/update.md b/content/influxdb/v2.2/reference/cli/influx/stacks/update.md
new file mode 100644
index 000000000..544bf2cd9
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/stacks/update.md
@@ -0,0 +1,89 @@
+---
+title: influx stacks update
+description: The 'influx stacks update' command updates an InfluxDB stack.
+menu:
+  influxdb_2_2_ref:
+    name: influx stacks update
+    parent: influx stacks
+weight: 201
+influxdb/v2.2/tags: [templates]
+updated_in: CLI v2.0.4
+---
+
+The `influx stacks update` command updates an InfluxDB stack.
+
+## Usage
+```
+influx stacks update [flags]
+```
+
+## Flags
+| Flag |                       | Description                                                           | Input type      | {{< cli/mapped >}}    |
+|:-----|:----------------------|:----------------------------------------------------------------------|:---------------:|:----------------------|
+|      | `--addResource`       | Associate an existing resource with a stack                           | string          |                       |
+| `-c` | `--active-config`     | CLI configuration to use for command                                  | string          |                       |
+|      | `--configs-path`      | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string          | `INFLUX_CONFIGS_PATH` |
+| `-f` | `--export-file`       | Destination for exported template                                     | string          |                       |
+| `-h` | `--help`              | Help for the `update` command                                         |                 |                       |
+|      | `--hide-headers`      | Hide table headers (default `false`)                                  |                 | `INFLUX_HIDE_HEADERS` |
+|      | `--host`              | HTTP address of InfluxDB (default `http://localhost:8086`)            | string          | `INFLUX_HOST`         |
+|      | `--http-debug`        | Inspect communication with InfluxDB servers.                          | string          |                       |
+| `-i` | `--stack-id`          | The stack ID to update                                                | string          |                       |
+|      | `--json`              | Output data as JSON (default `false`)                                 |                 | `INFLUX_OUTPUT_JSON`  |
+|      | `--skip-verify`       | Skip TLS certificate verification                                     |                 | `INFLUX_SKIP_VERIFY`  |
+| `-d` | `--stack-description` | Stack description                                                     | string          |                       |
+| `-n` | `--stack-name`        | Stack name                                                            | string          |                       |
+| `-u` | `--template-url`      | Template URLs to associate with a stack                               | list of strings |                       |
+| `-t` | `--token`             | API token                                                             | string          | `INFLUX_TOKEN`        |
+
+{{% warn %}}
+#### Export an updated template
+To prevent accidental changes, we **strongly recommend** exporting a new template
+any time you add additional resources to a stack using the `--addResource` flag
+with the `influx stack update` command.
+The updated stack will differ from the previous template.
+If you apply the outdated template, InfluxDB will revert the updates and remove
+the added resources.
+{{% /warn %}}
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+- [Update a stack with a name and description](#update-a-stack-with-a-name-and-description)
+- [Update a stack with a name and urls to associate with stack](#update-a-stack-with-a-name-and-urls-to-associate-with-stack)
+- [Update a stack with new resources to manage](#update-a-stack-with-new-resources-to-manage)
+- [Update a stack with new resources and export the stack as a template](#update-a-stack-with-new-resources-and-export-the-stack-as-a-template)
+
+##### Update a stack with a name and description
+```sh
+influx stack update \
+  -i ab12cd34ef56 \
+  -n "New stack name" \
+  -d "New stack description"
+```
+
+##### Update a stack with a name and URLs to associate with stack
+```sh
+influx stack update \
+  -i ab12cd34ef56 \
+  -n "New stack name" \
+  --template-url https://example.com/template-1.yml \
+  --template-url https://example.com/template-2.yml
+```
+
+##### Update a stack with new resources to manage
+```sh
+influx stacks update \
+	--stack-id ab12cd34ef56 \
+	--addResource=Bucket=12ab34cd56ef \
+	--addResource=Dashboard=98zy76xw54vu
+```
+
+##### Update a stack with new resources and export the stack as a template
+```sh
+influx stacks update \
+	--stack-id ab12cd34ef56 \
+	--addResource=Bucket=12ab34cd56ef \
+	--export-file /path/to/template-file.yml
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/task/_index.md b/content/influxdb/v2.2/reference/cli/influx/task/_index.md
new file mode 100644
index 000000000..39f9375e0
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/task/_index.md
@@ -0,0 +1,40 @@
+---
+title: influx task
+description: The `influx task` command and its subcommands manage tasks in InfluxDB.
+menu:
+  influxdb_2_2_ref:
+    name: influx task
+    parent: influx
+weight: 101
+influxdb/v2.2/tags: [tasks]
+cascade:
+  related:
+    - /influxdb/v2.2/process-data/
+    - /influxdb/v2.2/reference/cli/influx/#provide-required-authentication-credentials, influx CLI—Provide required authentication credentials
+    - /influxdb/v2.2/reference/cli/influx/#flag-patterns-and-conventions, influx CLI—Flag patterns and conventions
+  metadata: [influx CLI 2.0.0+, InfluxDB 2.0.0+]
+---
+
+The `influx task` command and its subcommands manage tasks in InfluxDB.
+
+### Usage
+```
+influx task [flags]
+influx task [command]
+```
+
+### Subcommands
+| Subcommand                                                            | Description            |
+|:----------                                                            |:-----------            |
+| [create](/influxdb/v2.2/reference/cli/influx/task/create)             | Create task            |
+| [delete](/influxdb/v2.2/reference/cli/influx/task/delete)             | Delete task            |
+| [list](/influxdb/v2.2/reference/cli/influx/task/list)                 | List tasks             |
+| [log](/influxdb/v2.2/reference/cli/influx/task/log)                   | Log related commands   |
+| [retry-failed](/influxdb/v2.2/reference/cli/influx/task/retry-failed) | Retry failed task runs |
+| [run](/influxdb/v2.2/reference/cli/influx/task/run)                   | Run related commands   |
+| [update](/influxdb/v2.2/reference/cli/influx/task/update)             | Update task            |
+
+### Flags
+| Flag |          | Description                 |
+|:---- |:---      |:-----------                 |
+| `-h` | `--help` | Help for the `task` command |
diff --git a/content/influxdb/v2.2/reference/cli/influx/task/create.md b/content/influxdb/v2.2/reference/cli/influx/task/create.md
new file mode 100644
index 000000000..e1822fa84
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/task/create.md
@@ -0,0 +1,59 @@
+---
+title: influx task create
+description: The `influx task create` command creates a task in InfluxDB.
+menu:
+  influxdb_2_2_ref:
+    name: influx task create
+    parent: influx task
+weight: 201
+---
+
+The `influx task create` command creates a task in InfluxDB.
+
+## Usage
+```
+influx task create [task literal] [flags]
+```
+
+## Flags
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:----------:|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+| `-f` | `--file`          | Path to Flux script file                                              | string     |                       |
+| `-h` | `--help`          | Help for the `create` command                                         |            |                       |
+|      | `--hide-headers`  | Hide table headers (default `false`)                                  |            | `INFLUX_HIDE_HEADERS` |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)            | string     | `INFLUX_HOST`         |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers.                          | string     |                       |
+|      | `--json`          | Output data as JSON (default `false`)                                 |            | `INFLUX_OUTPUT_JSON`  |
+| `-o` | `--org`           | Organization name (mutually exclusive with `--org-id`)                | string     | `INFLUX_ORG`          |
+|      | `--org-id`        | Organization ID (mutually exclusive with `--org`)                     | string     | `INFLUX_ORG_ID`       |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`         | API token                                                             | string     | `INFLUX_TOKEN`        |
+
+## Example
+
+{{< cli/influx-creds-note >}}
+
+##### Create a task using raw Flux
+```sh
+export FLUX_TASK='
+  option task = {
+    name: "Example Task",
+    every: 1d
+  }
+
+  from(bucket: "example-bucket")
+    |> range(start: -task.every)
+    |> filter(fn: (r) => (r._measurement == "m")
+    |> aggregateWindow(every: 1h, fn: mean)
+    |> to(bucket: "default-ds-1d", org: "my-org")
+'
+
+influx task create $FLUX_TASK
+```
+
+##### Create a task from a file
+```sh
+influx task create --file /path/to/example-task.flux
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/task/delete.md b/content/influxdb/v2.2/reference/cli/influx/task/delete.md
new file mode 100644
index 000000000..45c76fb9e
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/task/delete.md
@@ -0,0 +1,41 @@
+---
+title: influx task delete
+description: The `influx task delete` command deletes a task in InfluxDB.
+menu:
+  influxdb_2_2_ref:
+    name: influx task delete
+    parent: influx task
+weight: 201
+---
+
+The `influx task delete` command deletes a task in InfluxDB.
+
+## Usage
+```
+influx task delete [flags]
+```
+
+## Flags
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:----------:|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+| `-h` | `--help`          | Help for the `delete` command                                         |            |                       |
+|      | `--hide-headers`  | Hide table headers (default `false`)                                  |            | `INFLUX_HIDE_HEADERS` |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)            | string     | `INFLUX_HOST`         |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers.                          | string     |                       |
+| `-i` | `--id`            | ({{< req >}}) Task ID                                                 | string     |                       |
+|      | `--json`          | Output data as JSON (default `false`)                                 |            | `INFLUX_OUTPUT_JSON`  |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`         | API token                                                             | string     | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### Delete a task
+```sh
+influx task delete --id 0Xx0oox00XXoxxoo1
+```
+
+
diff --git a/content/influxdb/v2.2/reference/cli/influx/task/list.md b/content/influxdb/v2.2/reference/cli/influx/task/list.md
new file mode 100644
index 000000000..894bbb102
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/task/list.md
@@ -0,0 +1,68 @@
+---
+title: influx task list
+description: The `influx task list` command lists and searches for tasks in InfluxDB.
+menu:
+  influxdb_2_2_ref:
+    name: influx task list
+    parent: influx task
+weight: 201
+aliases:
+  - /influxdb/v2.2/reference/cli/influx/task/find
+---
+
+The `influx task list` command lists and searches for tasks in InfluxDB.
+
+## Usage
+```
+influx task list [flags]
+```
+
+#### Command aliases
+`list`, `ls`, `find`
+
+## Flags
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:----------:|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+| `-h` | `--help`          | Help for the `list` command                                           |            |                       |
+|      | `--hide-headers`  | Hide table headers (default `false`)                                  |            | `INFLUX_HIDE_HEADERS` |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)            | string     | `INFLUX_HOST`         |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers.                          | string     |                       |
+| `-i` | `--id`            | Task ID                                                               | string     |                       |
+|      | `--json`          | Output data as JSON (default `false`)                                 |            | `INFLUX_OUTPUT_JSON`  |
+|      | `--limit`         | Number of tasks to find (default `100`)                               | integer    |                       |
+| `-o` | `--org`           | Task organization name                                                | string     | `INFLUX_ORG`          |
+|      | `--org-id`        | Task organization ID                                                  | string     | `INFLUX_ORG_ID`       |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`         | API token                                                             | string     | `INFLUX_TOKEN`        |
+| `-n` | `--user-id`       | Task owner ID                                                         | string     |                       |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+- [List all tasks](#list-all-tasks)
+- [List a specific task](#list-a-specific-task)
+- [Limit the number of tasks returned to 20](#limit-the-number-of-tasks-returned-to-20)
+- [List all tasks created by a specific user](#list-all-tasks-created-by-a-specific-user)
+
+##### List all tasks
+```sh
+influx task list
+```
+
+##### List a specific task
+```sh
+influx task list --id 0Xx0oox00XXoxxoo1
+```
+
+##### Limit the number of tasks returned to 20
+```sh
+influx task list --limit 20
+```
+
+##### List all tasks created by a specific user
+```sh
+influx task list --user-id 0Xx0oox00XXoxxoo1
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/task/log/_index.md b/content/influxdb/v2.2/reference/cli/influx/task/log/_index.md
new file mode 100644
index 000000000..8ed4c6bb3
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/task/log/_index.md
@@ -0,0 +1,30 @@
+---
+title: influx task log
+description: >
+  The `influx task log` and its subcommand, `list`, output log information
+  related to a task.
+menu:
+  influxdb_2_2_ref:
+    name: influx task log
+    parent: influx task
+weight: 201
+influxdb/v2.2/tags: [logs]
+---
+
+The `influx task log` command and its subcommand `list` output log information related to a task.
+
+## Usage
+```
+influx task log [flags]
+influx task log [command]
+```
+
+## Subcommands
+| Subcommand                                                | Description        |
+|:----------                                                |:-----------        |
+| [list](/influxdb/v2.2/reference/cli/influx/task/log/list) | List logs for task |
+
+## Flags
+| Flag |          | Description                |
+|:---- |:---      |:-----------                |
+| `-h` | `--help` | Help for the `log` command |
diff --git a/content/influxdb/v2.2/reference/cli/influx/task/log/list.md b/content/influxdb/v2.2/reference/cli/influx/task/log/list.md
new file mode 100644
index 000000000..c193ff0fc
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/task/log/list.md
@@ -0,0 +1,52 @@
+---
+title: influx task log list
+description: The `influx task log list` command outputs log information related to a task.
+menu:
+  influxdb_2_2_ref:
+    name: influx task log list
+    parent: influx task log
+weight: 301
+aliases:
+  - /influxdb/v2.2/reference/cli/influx/task/log/list
+---
+
+The `influx task log list` command outputs log information related to a task.
+
+## Usage
+```
+influx task log list [flags]
+```
+
+#### Command aliases
+`list`, `ls`, `find`
+
+## Flags
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:----------:|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+| `-h` | `--help`          | Help for the `list` command                                           |            |                       |
+|      | `--hide-headers`  | Hide table headers (default `false`)                                  |            | `INFLUX_HIDE_HEADERS` |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)            | string     | `INFLUX_HOST`         |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers.                          | string     |                       |
+|      | `--run-id`        | Run ID                                                                | string     |                       |
+|      | `--json`          | Output data as JSON (default `false`)                                 |            | `INFLUX_OUTPUT_JSON`  |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+|      | `--task-id`       | ({{< req >}}) Task ID                                                 | string     |                       |
+| `-t` | `--token`         | API token                                                             | string     | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### List logs from all task executions
+```sh
+influx task log list --task-id 0Xx0oox00XXoxxoo1
+```
+
+##### List logs from a specific task execution
+```sh
+influx task log list \
+  --task-id 0Xx0oox00XXoxxoo1 \
+  --run-id ox0Xx0ooxx00XXoo2
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/task/retry-failed.md b/content/influxdb/v2.2/reference/cli/influx/task/retry-failed.md
new file mode 100644
index 000000000..e2da31b45
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/task/retry-failed.md
@@ -0,0 +1,98 @@
+---
+title: influx task retry-failed
+description: The `influx task retry-failed` command retries failed InfluxDB task runs.
+menu:
+  influxdb_2_2_ref:
+    name: influx task retry-failed
+    parent: influx task
+weight: 201
+metadata: [influx CLI 2.0.5+, InfluxDB 2.0.5+]
+---
+
+The `influx task retry-failed` command retries failed InfluxDB task runs.
+## Usage
+```
+influx task retry-failed [flags]
+```
+
+## Flags
+| Flag |                   | Description                                                               | Input type | {{< cli/mapped >}}    |
+|:-----|:------------------|:--------------------------------------------------------------------------|:----------:|:----------------------|
+|      | `--after`         | Retry task runs that occurred after this time (RFC3339 timestamp)         | string     |                       |
+| `-c` | `--active-config` | CLI configuration to use for command                                      | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`)     | string     | `INFLUX_CONFIGS_PATH` |
+|      | `--before`        | Retry task runs that occurred before this time (RFC3339 timestamp)        | string     |                       |
+|      | `--dry-run`       | Print information about task runs that would be retried                   |            |                       |
+| `-h` | `--help`          | Help for the `list` command                                               |            |                       |
+|      | `--hide-headers`  | Hide table headers (default `false`)                                      |            | `INFLUX_HIDE_HEADERS` |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)                | string     | `INFLUX_HOST`         |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers.                              | string     |                       |
+| `-i` | `--id`            | Task ID                                                                   | string     |                       |
+|      | `--json`          | Output data as JSON (default `false`)                                     |            | `INFLUX_OUTPUT_JSON`  |
+| `-o` | `--org`           | Task organization name                                                    | string     | `INFLUX_ORG`          |
+|      | `--org-id`        | Task organization ID                                                      | string     | `INFLUX_ORG_ID`       |
+|      | `--run-limit`     | Maximum number of failed runs to retry per task (`1-500`, default `100`)  | integer    |                       |
+|      | `--skip-verify`   | Skip TLS certificate verification                                         |            | `INFLUX_SKIP_VERIFY`  |
+|      | `--task-limit`    | Maximum number of tasks to retry failed runs for (`1-500`, default `100`) | integer    |                       |
+| `-t` | `--token`         | API token                                                                 | string     | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+{{% note %}}
+#### Required permissions
+Use an [{{% oss-only %}}**Operator** or{{% /oss-only %}} **All-Access** token](/influxdb/v2.2/security/tokens/) to retry failed tasks.
+{{% /note %}}
+
+- [Retry failed task runs for a specific task ID](#retry-failed-task-runs-for-a-specific-task-id)
+- [Retry failed task runs that occurred before a specific time](#retry-failed-task-runs-that-occurred-before-a-specific-time)
+- [Retry failed task runs that occurred after a specific time](#retry-failed-task-runs-that-occurred-after-a-specific-time)
+- [Retry failed task runs that occurred in a specific time range](#retry-failed-task-runs-that-occurred-in-a-specific-time-range)
+- [Retry failed runs for a limited number of tasks](#retry-failed-runs-for-a-limited-number-of-tasks)
+- [Retry a limited number of failed runs for a task](#retry-a-limited-number-of-failed-runs-for-a-task)
+- [Print information about runs that will be retried](#print-information-about-runs-that-will-be-retried)
+
+##### Retry failed task runs for a specific task ID
+```sh
+influx task retry-failed \
+  --id 0Xx0oox00XXoxxoo1
+```
+
+##### Retry failed task runs that occurred before a specific time
+```sh
+influx task retry-failed \
+  --before 2021-01-01T00:00:00Z
+```
+
+##### Retry failed task runs that occurred after a specific time
+```sh
+influx task retry-failed \
+  --after 2021-01-01T00:00:00Z
+```
+
+##### Retry failed task runs that occurred in a specific time range
+```sh
+influx task retry-failed \
+  --after 2021-01-01T00:00:00Z \
+  --before 2021-01-01T23:59:59Z
+```
+
+##### Retry failed runs for a limited number of tasks
+```sh
+influx task retry-failed \
+  --task-limit 5
+```
+
+##### Retry a limited number of failed runs for a task
+```sh
+influx task retry-failed \
+  --id 0Xx0oox00XXoxxoo1 \
+  --run-limit 5
+```
+
+##### Print information about runs that will be retried
+```sh
+influx task retry-failed \
+  --dry-run
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/task/run/_index.md b/content/influxdb/v2.2/reference/cli/influx/task/run/_index.md
new file mode 100644
index 000000000..c42f4cb46
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/task/run/_index.md
@@ -0,0 +1,30 @@
+---
+title: influx task run
+description: >
+  The `influx task run` command and its subcommand, `list` output information
+  related to runs of a task.
+menu:
+  influxdb_2_2_ref:
+    name: influx task run
+    parent: influx task
+weight: 201
+---
+
+The `influx task run` command and its subcommand `list` output information related to runs of a task.
+
+## Usage
+```
+influx task run [flags]
+influx task run [command]
+```
+
+## Subcommands
+| Subcommand                                         | Description          |
+|:----------                                         |:-----------          |
+| [list](/influxdb/v2.2/reference/cli/influx/task/run/list)   | List runs for a task |
+| [retry](/influxdb/v2.2/reference/cli/influx/task/run/retry) | Retry a task         |
+
+## Flags
+| Flag |          | Description                |
+|:---- |:---      |:-----------                |
+| `-h` | `--help` | Help for the `run` command |
diff --git a/content/influxdb/v2.2/reference/cli/influx/task/run/list.md b/content/influxdb/v2.2/reference/cli/influx/task/run/list.md
new file mode 100644
index 000000000..230a0dd45
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/task/run/list.md
@@ -0,0 +1,66 @@
+---
+title: influx task run list
+description: The `influx task run list` command outputs information related to runs of a task.
+menu:
+  influxdb_2_2_ref:
+    name: influx task run list
+    parent: influx task run
+weight: 301
+aliases:
+  - /influxdb/v2.2/reference/cli/influx/task/run/find
+---
+
+The `influx task run list` command outputs information related to runs of a task.
+
+## Usage
+```
+influx task run list [flags]
+```
+
+#### Command aliases
+`list`, `ls`, `find`
+
+## Flags
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:----------:|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string     |                       |
+|      | `--after`         | After-time for filtering                                              | string     |                       |
+|      | `--before`        | Before-time for filtering                                             | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+| `-h` | `--help`          | Help for the `list` command                                           |            |                       |
+|      | `--hide-headers`  | Hide table headers (default `false`)                                  |            | `INFLUX_HIDE_HEADERS` |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)            | string     | `INFLUX_HOST`         |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers.                          | string     |                       |
+|      | `--json`          | Output data as JSON (default `false`)                                 |            | `INFLUX_OUTPUT_JSON`  |
+|      | `--limit`         | Limit the number of results                                           | integer    |                       |
+|      | `--run-id`        | Run ID                                                                | string     |                       |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+|      | `--task-id`       | ({{< req >}}) Task ID                                                 | string     |                       |
+| `-t` | `--token`         | API token                                                             | string     | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+- [List all runs of a task](#list-all-runs-of-a-task)
+- [List a specific run of a task](#list-a-specific-run-of-a-task)
+- [Limit the number of returned task runs to 20](#limit-the-number-of-returned-task-runs-to-20)
+
+##### List all runs of a task
+```sh
+influx task run list --task-id 0Xx0oox00XXoxxoo1
+```
+
+##### List a specific run of a task
+```sh
+influx task run list \
+  --task-id 0Xx0oox00XXoxxoo1 \
+  --run-id ox0Xx0ooxx00XXoo2
+```
+
+##### Limit the number of returned task runs to 20
+```sh
+influx task run list \
+  --task-id 0Xx0oox00XXoxxoo1 \
+  --limit 20
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/task/run/retry.md b/content/influxdb/v2.2/reference/cli/influx/task/run/retry.md
new file mode 100644
index 000000000..6cbaee7ab
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/task/run/retry.md
@@ -0,0 +1,45 @@
+---
+title: influx task run retry
+description: The `influx task run retry` command retries to run a task in InfluxDB.
+menu:
+  influxdb_2_2_ref:
+    name: influx task run retry
+    parent: influx task run
+weight: 301
+---
+
+The `influx task run retry` command retries to run a task in InfluxDB.
+
+## Usage
+```
+influx task run retry [flags]
+```
+
+## Flags
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:----------:|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+| `-h` | `--help`          | Help for the `retry` command                                          |            |                       |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)            | string     | `INFLUX_HOST`         |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers.                          | string     |                       |
+| `-r` | `--run-id`        | ({{< req >}}) Run ID                                                  | string     |                       |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+| `-i` | `--task-id`       | ({{< req >}}) Task ID                                                 | string     |                       |
+| `-t` | `--token`         | API token                                                             | string     | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+{{% note %}}
+#### Required permissions
+Use an [{{% oss-only %}}**Operator** or{{% /oss-only %}} <span>**All-Access**</span> token](/influxdb/v2.2/security/tokens/) to retry tasks.
+{{% /note %}}
+
+##### Retry a task run
+```sh
+influx task run retry \
+  --task-id 0Xx0oox00XXoxxoo1 \
+  --run-id ox0Xx0ooxx00XXoo2
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/task/update.md b/content/influxdb/v2.2/reference/cli/influx/task/update.md
new file mode 100644
index 000000000..682b9dcdb
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/task/update.md
@@ -0,0 +1,74 @@
+---
+title: influx task update
+description: The `influx task update` command updates information related to tasks in InfluxDB.
+menu:
+  influxdb_2_2_ref:
+    name: influx task update
+    parent: influx task
+weight: 201
+---
+
+The `influx task update` command updates information related to tasks in InfluxDB.
+
+## Usage
+```
+influx task update [task literal] [flags]
+```
+
+## Flags
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:----------:|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+| `-f` | `--file`          | Path to Flux script file                                              | string     |                       |
+| `-h` | `--help`          | Help for the `update` command                                         |            |                       |
+|      | `--hide-headers`  | Hide table headers (default `false`)                                  |            | `INFLUX_HIDE_HEADERS` |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)            | string     | `INFLUX_HOST`         |
+|      | `--http-debug`    | Inspect communication with InfluxDB servers.                          | string     |                       |
+| `-i` | `--id`            | ({{< req >}}) Task ID                                                 | string     |                       |
+|      | `--json`          | Output data as JSON (default `false`)                                 |            | `INFLUX_OUTPUT_JSON`  |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+|      | `--status`        | Update task status (`active` or `inactive`)                           | string     |                       |
+| `-t` | `--token`         | API token                                                             | string     | `INFLUX_TOKEN`        |
+
+## Example
+
+{{< cli/influx-creds-note >}}
+
+- [Update a task from a Flux string](#update-a-task-from-a-flux-string)
+- [Update a task from a Flux file](#update-a-task-from-a-flux-file)
+- [Enable a task](#enable-a-task)
+- [Disable a task](#disable-a-task)
+
+##### Update a task from a Flux string
+```sh
+export UPDATED_FLUX_TASK='
+  option task = {
+    name: "Example Task",
+    every: 1d
+  }
+
+  from(bucket: "example-bucket")
+    |> range(start: -task.every)
+    |> filter(fn: (r) => (r._measurement == "m")
+    |> aggregateWindow(every: 1h, fn: mean)
+    |> to(bucket: "default-ds-1d", org: "my-org")
+'
+
+influx task update $UPDATED_FLUX_TASK
+```
+
+##### Update a task from a Flux file
+```sh
+influx task update --file /path/to/example-task.flux
+```
+
+##### Enable a task
+```sh
+influx task update --status active
+```
+
+##### Disable a task
+```sh
+influx task update --status inactive
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/telegrafs/_index.md b/content/influxdb/v2.2/reference/cli/influx/telegrafs/_index.md
new file mode 100644
index 000000000..c1546cda3
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/telegrafs/_index.md
@@ -0,0 +1,62 @@
+---
+title: influx telegrafs
+description: >
+  The `influx telegrafs` command lists Telegraf configurations.
+  Subcommands manage Telegraf configurations.
+menu:
+  influxdb_2_2_ref:
+    name: influx telegrafs
+    parent: influx
+weight: 101
+influxdb/v2.2/tags: [telegraf]
+cascade:
+  related:
+    - /influxdb/v2.2/telegraf-configs/
+    - /influxdb/v2.2/reference/cli/influx/#provide-required-authentication-credentials, influx CLI—Provide required authentication credentials
+    - /influxdb/v2.2/reference/cli/influx/#flag-patterns-and-conventions, influx CLI—Flag patterns and conventions
+  metadata: [influx CLI 2.0.0+, InfluxDB 2.0.0+]
+---
+
+The `influx telegrafs` command lists Telegraf configurations.
+Subcommands manage Telegraf configurations.
+
+## Usage
+```sh
+influx telegrafs [flags]
+influx telegrafs [command]
+```
+
+## Subcommands
+| Subcommand                                                     | Description                     |
+|:----------                                                     |:-----------                     |
+| [create](/influxdb/v2.2/reference/cli/influx/telegrafs/create) | Create a Telegraf configuration |
+| [rm](/influxdb/v2.2/reference/cli/influx/telegrafs/rm)         | Remove a Telegraf configuration |
+| [update](/influxdb/v2.2/reference/cli/influx/telegrafs/update) | Update a Telegraf configuration |
+
+## Flags
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:----------:|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+| `-h` | `--help`          | Help for the `telegrafs` command                                      |            |                       |
+|      | `--hide-headers`  | Hide table headers                                                    |            | `INFLUX_HIDE_HEADERS` |
+| `-i` | `--id`            | Telegraf configuration ID to retrieve                                 | string     |                       |
+|      | `--json`          | Output data as JSON                                                   |            | `INFLUX_OUTPUT_JSON`  |
+| `-o` | `--org`           | Organization name (mutually exclusive with `--org-id`)                | string     | `INFLUX_ORG`          |
+|      | `--org-id`        | Organization ID (mutually exclusive with `--org`)                     | string     | `INFLUX_ORG_ID`       |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`         | API token                                                             | string     | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### List all Telegraf configurations
+```sh
+influx telegrafs
+```
+
+##### List a Telegraf configuration with the specified ID
+```sh
+influx telegrafs --id 0Xx0oox00XXoxxoo1
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/telegrafs/create.md b/content/influxdb/v2.2/reference/cli/influx/telegrafs/create.md
new file mode 100644
index 000000000..586b665ac
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/telegrafs/create.md
@@ -0,0 +1,54 @@
+---
+    title: influx telegrafs create
+description: >
+  The `influx telegrafs create` command creates a Telegraf configuration in InfluxDB
+  using a provided Telegraf configuration file.
+menu:
+  influxdb_2_2_ref:
+    name: influx telegrafs create
+    parent: influx telegrafs
+weight: 201
+---
+
+The `influx telegrafs create` command creates a Telegraf configuration in InfluxDB
+using a provided Telegraf configuration file.
+
+## Usage
+```sh
+influx telegrafs create [flags]
+```
+
+## Flags
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:----------:|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+| `-d` | `--description`   | Telegraf configuration description                                    | string     |                       |
+| `-f` | `--file`          | Path to Telegraf configuration                                        | string     |                       |
+| `-h` | `--help`          | Help for the `create` command                                         |            |                       |
+|      | `--hide-headers`  | Hide table headers                                                    |            | `INFLUX_HIDE_HEADERS` |
+|      | `--json`          | Output data as JSON                                                   |            | `INFLUX_OUTPUT_JSON`  |
+| `-n` | `--name`          | Telegraf configuration name                                           | string     |                       |
+| `-o` | `--org`           | Organization name (mutually exclusive with `--org-id`)                | string     | `INFLUX_ORG`          |
+|      | `--org-id`        | Organization ID (mutually exclusive with `--org`)                     | string     | `INFLUX_ORG_ID`       |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`         | API token                                                             | string     | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### Create a Telegraf configuration
+```sh
+influx telegrafs create \
+  --name "Example configuration name" \
+  --description "Example Telegraf configuration description" \
+  --file /path/to/telegraf.conf
+```
+
+##### Create a Telegraf configuration via stdin
+```sh
+cat /path/to/telegraf.conf | influx telegrafs create \
+  --name "Example configuration name" \
+  --description "Example Telegraf configuration description" \
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/telegrafs/rm.md b/content/influxdb/v2.2/reference/cli/influx/telegrafs/rm.md
new file mode 100644
index 000000000..b20919d0a
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/telegrafs/rm.md
@@ -0,0 +1,48 @@
+---
+title: influx telegrafs rm
+description: >
+  The `influx telegrafs rm` command removes Telegraf configurations from InfluxDB.
+menu:
+  influxdb_2_2_ref:
+    name: influx telegrafs rm
+    parent: influx telegrafs
+weight: 201
+---
+
+The `influx telegrafs rm` command removes Telegraf configurations from InfluxDB.
+
+## Usage
+```sh
+influx telegrafs rm [flags]
+```
+
+#### Command aliases
+`rm`, `remove`
+
+## Flags
+| Flag |                   | Description                                                           | Input type  | {{< cli/mapped >}}     |
+|:-----|:------------------|:----------------------------------------------------------------------|:-----------:|:-----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string      |                        |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string      | `INFLUX_CONFIGS_PATH`  |
+| `-h` | `--help`          | Help for the `rm` command                                             |             |                        |
+|      | `--hide-headers`  | Hide the table headers                                                |             | `$INFLUX_HIDE_HEADERS` |
+| `-i` | `--id`            | Telegraf configuration ID to remove                                   | stringArray |                        |
+|      | `--json`          | Output data as json                                                   |             | `$INFLUX_OUTPUT_JSON`  |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |             | `INFLUX_SKIP_VERIFY`   |
+| `-t` | `--token`         | API token                                                             | string      | `INFLUX_TOKEN`         |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### Remove a Telegraf configuration
+```sh
+influx telegrafs rm --id ab12cd34ef56
+```
+
+##### Remove multiple Telegraf configurations
+```sh
+influx telegrafs rm \
+  --i 0Xx0oox00XXoxxoo1 \
+  --i oox0Xx0ox00XXxoo2
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/telegrafs/update.md b/content/influxdb/v2.2/reference/cli/influx/telegrafs/update.md
new file mode 100644
index 000000000..f5ba56791
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/telegrafs/update.md
@@ -0,0 +1,56 @@
+---
+title: influx telegrafs update
+description: >
+  The `influx telegrafs update` command updates a Telegraf configuration to match the specified parameters.
+  If a name or description are not provided, they are set to an empty string.
+menu:
+  influxdb_2_2_ref:
+    name: influx telegrafs update
+    parent: influx telegrafs
+weight: 201
+---
+
+The `influx telegrafs update` command updates a Telegraf configuration to match the specified parameters.
+If a name or description are not provided, they are set to an empty string.
+
+## Usage
+```sh
+influx telegrafs update [flags]
+```
+
+## Flags
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:----------:|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+| `-d` | `--description`   | Telegraf configuration description                                    | string     |                       |
+| `-f` | `--file`          | Path to Telegraf configuration                                        | string     |                       |
+| `-h` | `--help`          | Help for the `update` command                                         |            |                       |
+|      | `--hide-headers`  | Hide table headers                                                    |            | `INFLUX_HIDE_HEADERS` |
+|      | `--json`          | Output data as JSON                                                   |            | `INFLUX_OUTPUT_JSON`  |
+| `-n` | `--name`          | Telegraf configuration name                                           | string     |                       |
+| `-o` | `--org`           | Organization name (mutually exclusive with `--org-id`)                | string     | `INFLUX_ORG`          |
+|      | `--org-id`        | Organization ID (mutually exclusive with `--org`)                     | string     | `INFLUX_ORG_ID`       |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`         | API token                                                             | string     | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### Update a Telegraf configuration
+```sh
+influx telegrafs update \
+  --id 0Xx0oox00XXoxxoo1 \
+  --name "Example configuration name" \
+  --description "Example Telegraf configuration description" \
+  --file /path/to/telegraf.conf
+```
+
+##### Update a Telegraf configuration via stdin
+```sh
+cat /path/to/telegraf.conf | influx telegrafs update \
+  --id 0Xx0oox00XXoxxoo1 \
+  --name "Example configuration name" \
+  --description "Example Telegraf configuration description" \
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/template/_index.md b/content/influxdb/v2.2/reference/cli/influx/template/_index.md
new file mode 100644
index 000000000..d52ecadd1
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/template/_index.md
@@ -0,0 +1,86 @@
+---
+title: influx template
+description: The `influx template` command summarizes the specified InfluxDB template.
+menu:
+  influxdb_2_2_ref:
+    name: influx template
+    parent: influx
+weight: 101
+influxdb/v2.2/tags: [templates]
+aliases:
+  - /influxdb/v2.2/reference/cli/influx/pkg/summary/
+cascade:
+  related:
+    - /influxdb/v2.2/influxdb-templates/
+    - /influxdb/v2.2/reference/cli/influx/#provide-required-authentication-credentials, influx CLI—Provide required authentication credentials
+    - /influxdb/v2.2/reference/cli/influx/#flag-patterns-and-conventions, influx CLI—Flag patterns and conventions
+  metadata: [influx CLI 2.0.1+, InfluxDB 2.0.1+]
+---
+
+The `influx template` command summarizes the specified InfluxDB template.
+The command returns information about all resources included in the template.
+
+## Usage
+```
+influx template [flags]
+influx template [command]
+```
+
+## Subcommands
+| Subcommand                                                        | Description         |
+|:----------                                                        |:-----------         |
+| [validate](/influxdb/v2.2/reference/cli/influx/template/validate) | Validate a template |
+
+## Flags
+| Flag |                           | Description                                                        | Input Type  | {{< cli/mapped >}}   |
+|:---- |:---                       |:-----------                                                        |:----------  |:------------------   |
+|      | `--disable-color`         | Disable color in output                                            |             |                      |
+|      | `--disable-table-borders` | Disable table borders                                              |             |                      |
+| `-e` | `--encoding`              | Template encoding (`yaml`,`yml`,`json`, or `jsonnet`)              | string      |                      |
+| `-f` | `--file`                  | Path to template file (supports HTTP(S) URLs or file paths)        | stringArray |                      |
+| `-h` | `--help`                  | Help for the `template` command                                    |             |                      |
+|      | `--json`                  | Output data as JSON (default `false`)                              |             | `INFLUX_OUTPUT_JSON` |
+| `-R` | `--recurse`               | Recurse through files in the directory specified in `-f`, `--file` |             |                      |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+**Summarize InfluxDB Templates:**
+
+- [from a local file](#summarize-an-influxdb-template-from-a-local-file)
+- [from multiple files](#summarize-influxdb-templates-from-multiple-files)
+- [from a URL](#summarize-an-influxdb-template-from-a-url)
+- [from a directory](#summarize-all-influxdb-templates-in-a-directory)
+- [using a specific encoding](#specify-the-encoding-of-the-influxdb-template-to-summarize)
+
+##### Summarize an InfluxDB template from a local file
+```sh
+influx template --file /path/to/template.yml
+```
+
+##### Summarize InfluxDB templates from multiple files
+```sh
+influx template \
+  --file /path/to/template1.yml \
+  --file /path/to/template2.yml
+```
+
+##### Summarize an InfluxDB template from a URL
+```sh
+influx template --file https://example.com/path/to/template.yml
+```
+
+##### Summarize all InfluxDB templates in a directory
+```sh
+influx template \
+  --file /path/to/template/dir/ \
+  --recurse
+```
+
+##### Specify the encoding of the InfluxDB template to summarize
+```sh
+influx template \
+  --file /path/to/template \
+  --encoding json
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/template/validate.md b/content/influxdb/v2.2/reference/cli/influx/template/validate.md
new file mode 100644
index 000000000..7994df0d7
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/template/validate.md
@@ -0,0 +1,70 @@
+---
+title: influx template validate
+description: >
+  The `influx template validate` command validates the provided InfluxDB template.
+menu:
+  influxdb_2_2_ref:
+    parent: influx template
+weight: 201
+aliases:
+  - /influxdb/v2.2/reference/cli/influx/pkg/validate/
+---
+
+The `influx template validate` command validates the provided InfluxDB template.
+
+## Usage
+```
+influx template validate [flags]
+```
+
+## Flags
+
+| Flag |              | Description                                                        | Input Type  |
+|:---- |:---          |:-----------                                                        |:----------  |
+| `-e` | `--encoding` | Template encoding                                                  | string      |
+| `-f` | `--file`     | Path to template file (supports HTTP(S) URLs or file paths)        | stringArray |
+| `-h` | `--help`     | Help for the `validate` command                                    |             |
+| `-R` | `--recurse`  | Recurse through files in the directory specified in `-f`, `--file` |             |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+**Validate InfluxDB Templates:**
+
+- [from a local file](#validate-an-influxdb-template-from-a-local-file)
+- [from multiple files](#validate-influxdb-templates-from-multiple-files)
+- [from a URL](#validate-an-influxdb-template-from-a-url)
+- [from a directory](#validate-all-influxdb-templates-in-a-directory)
+- [using a specific encoding](#specify-the-encoding-of-the-influxdb-template-to-validate)
+
+##### Validate an InfluxDB template from a local file
+```sh
+influx template validate --file /path/to/template.yml
+```
+
+##### Validate InfluxDB templates from multiple files
+```sh
+influx template validate \
+  --file /path/to/template1.yml \
+  --file /path/to/template2.yml
+```
+
+##### Validate an InfluxDB template from a URL
+```sh
+influx template validate --file https://example.com/path/to/template.yml
+```
+
+##### Validate all InfluxDB templates in a directory
+```sh
+influx template validate \
+  --file /path/to/template/dir/ \
+  --recurse
+```
+
+##### Specify the encoding of the InfluxDB template to validate
+```sh
+influx template validate \
+  --file /path/to/template \
+  --encoding json
+```
\ No newline at end of file
diff --git a/content/influxdb/v2.2/reference/cli/influx/transpile/_index.md b/content/influxdb/v2.2/reference/cli/influx/transpile/_index.md
new file mode 100644
index 000000000..147aefb79
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/transpile/_index.md
@@ -0,0 +1,55 @@
+---
+title: influx transpile
+description: >
+  The `influx transpile` command transpiles an InfluxQL query to Flux source code.
+weight: 101
+related:
+  - /influxdb/v2.2/reference/cli/influx/#provide-required-authentication-credentials, influx CLI—Provide required authentication credentials
+  - /influxdb/v2.2/reference/cli/influx/#flag-patterns-and-conventions, influx CLI—Flag patterns and conventions
+metadata: [influx CLI 2.0.0 – 2.0.5]
+prepend:
+  block: warn
+  content: |
+    ### Removed in InfluxDB OSS 2.0.5
+    The `influx transpile` command was removed in **InfluxDB 2.0.5**.
+    [Use InfluxQL to query InfluxDB](/influxdb/v2.2/query-data/influxql/).
+    For information about manually converting InfluxQL queries to Flux, see:
+
+    - [Get started with Flux](/flux/v0.x/get-started/)
+    - [Query data with Flux](/influxdb/v2.2/query-data/flux/)
+    - [Migrate continuous queries to Flux tasks](/influxdb/v2.2/upgrade/v1-to-v2/migrate-cqs/)
+---
+
+The `influx transpile` command transpiles an InfluxQL query to Flux source code.
+The transpiled query assumes the bucket name is `<database>/<retention policy>`
+and includes absolute time ranges using the provided `--now` time.
+
+## Usage
+```
+influx transpile [InfluxQL query] [flags]
+```
+
+{{% note %}}
+The InfluxQL query must be valid and contain both a database and measurement.
+See the [InfluxQL documentation](/{{< latest "influxdb" "v1" >}}/query_language/) for more information.
+{{% /note %}}
+
+## Flags
+| Flag |          | Description                                                                |
+|:---- |:---      |:-----------                                                                |
+| `-h` | `--help` | Help for the `transpile` command                                           |
+|      | `--now`  | RFC3339Nano timestamp to use as `now()` time (default is current UTC time) |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### Transpile InfluxQL queries to Flux
+```sh
+## Transpile an InfluxQL query that specifies the database,
+## retention policy, and measurement.
+influx transpile 'SELECT example-field FROM db.rp.measurement'
+
+## Transpile InfluxQL query using default retention policy
+influx transpile 'SELECT example-field FROM db..measurement'
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/user/_index.md b/content/influxdb/v2.2/reference/cli/influx/user/_index.md
new file mode 100644
index 000000000..2052694df
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/user/_index.md
@@ -0,0 +1,39 @@
+---
+title: influx user
+description: The `influx user` command and its subcommands manage user information in InfluxDB.
+menu:
+  influxdb_2_2_ref:
+    name: influx user
+    parent: influx
+weight: 101
+influxdb/v2.2/tags: [users]
+cascade:
+  related:
+    - /influxdb/v2.2/users/
+    - /influxdb/v2.2/reference/cli/influx/#provide-required-authentication-credentials, influx CLI—Provide required authentication credentials
+    - /influxdb/v2.2/reference/cli/influx/#flag-patterns-and-conventions, influx CLI—Flag patterns and conventions
+  metadata: [influx CLI 2.0.0+, InfluxDB 2.0.0+]
+canonical: /{{< latest "influxdb" "v2" >}}/reference/cli/influx/user/
+---
+
+The `influx user` command and its subcommands manage user information in InfluxDB.
+
+## Usage
+```
+influx user [flags]
+influx user [command]
+```
+
+## Subcommands
+| Subcommand                                                    | Description              |
+|:----------                                                    |:-----------              |
+| [create](/influxdb/v2.2/reference/cli/influx/user/create)     | Create a user            |
+| [delete](/influxdb/v2.2/reference/cli/influx/user/delete)     | Delete a user            |
+| [list](/influxdb/v2.2/reference/cli/influx/user/list)         | List users               |
+| [password](/influxdb/v2.2/reference/cli/influx/user/password) | Update a user's password |
+| [update](/influxdb/v2.2/reference/cli/influx/user/update)     | Update a user            |
+
+## Flags
+| Flag |          | Description                 |
+|:---- |:---      |:-----------                 |
+| `-h` | `--help` | Help for the `user` command |
diff --git a/content/influxdb/v2.2/reference/cli/influx/user/create.md b/content/influxdb/v2.2/reference/cli/influx/user/create.md
new file mode 100644
index 000000000..d8aa7a0d6
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/user/create.md
@@ -0,0 +1,44 @@
+---
+title: influx user create
+description: The `influx user create` command creates a user in InfluxDB.
+menu:
+  influxdb_2_2_ref:
+    name: influx user create
+    parent: influx user
+weight: 201
+canonical: /{{< latest "influxdb" "v2" >}}/reference/cli/influx/user/create/
+---
+
+The `influx user create` command creates a user in InfluxDB.
+
+## Usage
+```
+influx user create [flags]
+```
+
+## Flags
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:----------:|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+| `-h` | `--help`          | Help for the `create` command                                         |            |                       |
+|      | `--hide-headers`  | Hide table headers (default `false`)                                  |            | `INFLUX_HIDE_HEADERS` |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)            | string     | `INFLUX_HOST`         |
+|      | `--json`          | Output data as JSON (default `false`)                                 |            | `INFLUX_OUTPUT_JSON`  |
+| `-n` | `--name`          | ({{< req >}}) Username                                                | string     | `INFLUX_NAME`         |
+| `-o` | `--org`           | Organization name (mutually exclusive with `--org-id`)                | string     | `INFLUX_ORG`          |
+|      | `--org-id`        | Organization ID (mutually exclusive with `--org`)                     | string     | `INFLUX_ORG_ID`       |
+| `-p` | `--password`      | User password                                                         | string     |                       |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`         | API token                                                             | string     | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### Create a user
+```sh
+influx user create \
+  --name example-username \
+  --password ExAmPl3PA55W0rD
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/user/delete.md b/content/influxdb/v2.2/reference/cli/influx/user/delete.md
new file mode 100644
index 000000000..d35b0c79e
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/user/delete.md
@@ -0,0 +1,39 @@
+---
+title: influx user delete
+description: The `influx user delete` command deletes a specified user.
+menu:
+  influxdb_2_2_ref:
+    name: influx user delete
+    parent: influx user
+weight: 201
+canonical: /{{< latest "influxdb" "v2" >}}/reference/cli/influx/user/delete/
+---
+
+The `influx user delete` command deletes a specified user in InfluxDB.
+
+## Usage
+```
+influx user delete [flags]
+```
+
+## Flags
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:----------:|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+| `-h` | `--help`          | Help for the `delete` command                                         |            |                       |
+|      | `--hide-headers`  | Hide table headers (default `false`)                                  |            | `INFLUX_HIDE_HEADERS` |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)            | string     | `INFLUX_HOST`         |
+| `-i` | `--id`            | ({{< req >}}) User ID                                                 | string     |                       |
+|      | `--json`          | Output data as JSON (default `false`)                                 |            | `INFLUX_OUTPUT_JSON`  |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`         | API token                                                             | string     | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### Delete a user
+```sh
+influx user delete --id 0Xx0oox00XXoxxoo1
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/user/list.md b/content/influxdb/v2.2/reference/cli/influx/user/list.md
new file mode 100644
index 000000000..4959446ec
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/user/list.md
@@ -0,0 +1,59 @@
+---
+title: influx user list
+description: The `influx user list` lists users in InfluxDB.
+menu:
+  influxdb_2_2_ref:
+    name: influx user list
+    parent: influx user
+weight: 201
+aliases:
+  - /influxdb/v2.2/reference/cli/influx/user/find
+canonical: /{{< latest "influxdb" "v2" >}}/reference/cli/influx/user/list/
+---
+
+The `influx user list` command lists users in InfluxDB.
+
+## Usage
+```
+influx user list [flags]
+```
+
+#### Command aliases
+`list`, `ls`, `find`
+
+## Flags
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:----------:|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+| `-h` | `--help`          | Help for the `list` command                                           |            |                       |
+|      | `--hide-headers`  | Hide table headers (default `false`)                                  |            | `INFLUX_HIDE_HEADERS` |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)            | string     | `INFLUX_HOST`         |
+| `-i` | `--id`            | User ID                                                               | string     |                       |
+|      | `--json`          | Output data as JSON (default `false`)                                 |            | `INFLUX_OUTPUT_JSON`  |
+| `-n` | `--name`          | Username                                                              | string     |                       |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`         | API token                                                             | string     | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+- [List all users](#list-all-users)
+- [List a specific user by username](#list-a-specific-user-by-username)
+- [List a specific user by ID](#list-a-specific-user-by-id)
+
+##### List all users
+```sh
+influx user list
+```
+
+##### List a specific user by username
+```sh
+influx user list --name example-username
+```
+
+##### List a specific user by ID
+```sh
+influx user list --id 0Xx0oox00XXoxxoo1
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/user/password.md b/content/influxdb/v2.2/reference/cli/influx/user/password.md
new file mode 100644
index 000000000..4b02ce88c
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/user/password.md
@@ -0,0 +1,48 @@
+---
+title: influx user password
+description: The `influx user password` command updates the password for a user in InfluxDB.
+menu:
+  influxdb_2_2_ref:
+    name: influx user password
+    parent: influx user
+weight: 201
+related:
+  - /influxdb/v2.2/users/change-password/
+canonical: /{{< latest "influxdb" "v2" >}}/reference/cli/influx/user/password/
+---
+
+The `influx user password` command updates the password for a user in InfluxDB.
+
+## Usage
+```
+influx user password [flags]
+```
+
+## Flags
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:----------:|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+| `-h` | `--help`          | Help for the `password` command                                       |            |                       |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)            | string     | `INFLUX_HOST`         |
+| `-i` | `--id`            | User ID                                                               | string     |                       |
+| `-n` | `--name`          | Username                                                              | string     |                       |
+|      | `--password`      | Use `password` flag to send your password instead of typing it in     | string     |                       |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`         | API token                                                             | string     | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### Update a user password using a username
+```sh
+influx user password --name example-username
+# Prompts for password
+```
+
+##### Update a user password using a user ID
+```sh
+influx user password --id 0Xx0oox00XXoxxoo1
+# Prompts for password
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/user/update.md b/content/influxdb/v2.2/reference/cli/influx/user/update.md
new file mode 100644
index 000000000..e0b5dec3e
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/user/update.md
@@ -0,0 +1,43 @@
+---
+title: influx user update
+description: >
+  The `influx user update` command updates information related to a user such as their user name.
+menu:
+  influxdb_2_2_ref:
+    name: influx user update
+    parent: influx user
+weight: 201
+canonical: /{{< latest "influxdb" "v2" >}}/reference/cli/influx/user/update/
+---
+
+The `influx user update` command updates information related to a user in InfluxDB.
+
+## Usage
+```
+influx user update [flags]
+```
+
+## Flags
+| Flag |                   | Description                                                           | Input type | {{< cli/mapped >}}    |
+|:-----|:------------------|:----------------------------------------------------------------------|:----------:|:----------------------|
+| `-c` | `--active-config` | CLI configuration to use for command                                  | string     |                       |
+|      | `--configs-path`  | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`) | string     | `INFLUX_CONFIGS_PATH` |
+| `-h` | `--help`          | Help for the `update` command                                         |            |                       |
+|      | `--hide-headers`  | Hide table headers (default `false`)                                  |            | `INFLUX_HIDE_HEADERS` |
+|      | `--host`          | HTTP address of InfluxDB (default `http://localhost:8086`)            | string     | `INFLUX_HOST`         |
+| `-i` | `--id`            | ({{< req >}}) User ID                                                 | string     |                       |
+|      | `--json`          | Output data as JSON (default `false`)                                 |            | `INFLUX_OUTPUT_JSON`  |
+| `-n` | `--name`          | Username                                                              | string     |                       |
+|      | `--skip-verify`   | Skip TLS certificate verification                                     |            | `INFLUX_SKIP_VERIFY`  |
+| `-t` | `--token`         | API token                                                             | string     | `INFLUX_TOKEN`        |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### Update a username
+```sh
+influx user update \
+  --id 0Xx0oox00XXoxxoo1 \
+  --name new-username
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/v1/_index.md b/content/influxdb/v2.2/reference/cli/influx/v1/_index.md
new file mode 100644
index 000000000..d73ebc98b
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/v1/_index.md
@@ -0,0 +1,36 @@
+---
+title: influx v1
+description: >
+  The `influx v1` command provides commands for working with the InfluxDB 1.x API in InfluxDB 2.x.
+menu:
+  influxdb_2_2_ref:
+    name: influx v1
+    parent: influx
+weight: 101
+cascade:
+  related:
+    - /influxdb/v2.2/upgrade/v1-to-v2/
+    - /influxdb/v2.2/reference/api/influxdb-1x/
+    - /influxdb/v2.2/reference/cli/influx/#provide-required-authentication-credentials, influx CLI—Provide required authentication credentials
+    - /influxdb/v2.2/reference/cli/influx/#flag-patterns-and-conventions, influx CLI—Flag patterns and conventions
+  metadata: [influx CLI 2.0.0+, InfluxDB 2.0.0+]
+---
+
+The `influx v1` command provides commands for working with the [InfluxDB 1.x compatibility API](/influxdb/v2.2/reference/api/influxdb-1x/) in InfluxDB {{< current-version >}}.
+
+## Usage
+```
+influx v1 [flags]
+influx v1 [command]
+```
+
+## Subcommands
+| Subcommand                                           | Description                                                       |
+|:-----------------------------------------------------|:----------------------------------------------                    |
+| [auth](/influxdb/v2.2/reference/cli/influx/v1/auth/) | Authorization management commands for v1 APIs                     |
+| [dbrp](/influxdb/v2.2/reference/cli/influx/v1/dbrp/) | Database retention policy mapping management commands for v1 APIs |
+
+## Flags
+| Flag |          | Description               |
+|:-----|:---------|:--------------------------|
+| `-h` | `--help` | Help for the `v1` command |
diff --git a/content/influxdb/v2.2/reference/cli/influx/v1/auth/_index.md b/content/influxdb/v2.2/reference/cli/influx/v1/auth/_index.md
new file mode 100644
index 000000000..fc17e9c65
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/v1/auth/_index.md
@@ -0,0 +1,47 @@
+---
+title: influx v1 auth
+description: >
+  The `influx v1 auth` subcommands provide authorization management for the InfluxDB 1.x compatibility API.
+menu:
+  influxdb_2_2_ref:
+    name: influx v1 auth
+    parent: influx v1
+weight: 101
+influxdb/v2.2/tags: [authorization]
+---
+
+The `influx v1 auth` subcommands provide authorization management for the
+[InfluxDB 1.x compatibility API](/influxdb/v2.2/reference/api/influxdb-1x/).
+
+InfluxDB {{< current-version >}} uses [API tokens](/influxdb/v2.2/security/tokens/) to authorize API requests.
+The [1.x compatibility API](/influxdb/v2.2/reference/api/influxdb-1x/) lets clients authenticate with InfluxDB {{< current-version >}} using the InfluxDB 1.x convention of username and password.
+
+{{% note %}}
+1.x-compatible authorizations are separate from the credentials used to log
+into the InfluxDB user interface.
+{{% /note %}}
+
+## Usage
+```
+influx v1 auth [flags]
+influx v1 auth [command]
+```
+
+#### Command aliases
+`auth`, `authorization`
+
+## Commands
+
+| Command                                                                     | Description                                  |
+|:----------------------------------------------------------------------------|:---------------------------------------------|
+| [create](/influxdb/v2.2/reference/cli/influx/v1/auth/create/)             | Create authorization                         |
+| [delete](/influxdb/v2.2/reference/cli/influx/v1/auth/delete/)             | Delete authorization                         |
+| [list](/influxdb/v2.2/reference/cli/influx/v1/auth/list/)                 | List authorizations                          |
+| [set-active](/influxdb/v2.2/reference/cli/influx/v1/auth/set-active/)     | Activate an authorization                    |
+| [set-inactive](/influxdb/v2.2/reference/cli/influx/v1/auth/set-inactive/) | Deactivate an authorization                  |
+| [set-password](/influxdb/v2.2/reference/cli/influx/v1/auth/set-password/) | Set a password for an existing authorization |
+
+## Flags
+| Flag |          | Description                     |
+|:-----|:---------|:--------------------------------|
+| `-h` | `--help` | Help for the `v1 auth ` command |
diff --git a/content/influxdb/v2.2/reference/cli/influx/v1/auth/create.md b/content/influxdb/v2.2/reference/cli/influx/v1/auth/create.md
new file mode 100644
index 000000000..2f3828e4c
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/v1/auth/create.md
@@ -0,0 +1,54 @@
+---
+title: influx v1 auth create
+description: >
+  The `influx v1 auth create` command creates an authorization in the InfluxDB 1.x compatibility API.
+menu:
+  influxdb_2_2_ref:
+    name: influx v1 auth create
+    parent: influx v1 auth
+weight: 101
+influxdb/v2.2/tags: [authorization]
+updated_in: CLI v2.0.3
+---
+
+The `influx v1 auth create` command creates a legacy authorization with the [InfluxDB 1.x compatibility API](/influxdb/v2.2/reference/api/influxdb-1x/).
+
+## Usage
+```
+influx v1 auth create [flags]
+```
+
+## Flags
+| Flag |                   | Description                                                                                                | Input type  | {{< cli/mapped >}}      |
+|:-----|:------------------|:-----------------------------------------------------------------------------------------------------------|:-----------:|:------------------------|
+| `-c` | `--active-config` | Config name to use for command                                                                             | string      | `$INFLUX_ACTIVE_CONFIG` |
+|      | `--configs-path`  | Path to the influx CLI configurations (default: `~/.influxdbv2/configs`)                                   | string      | `$INFLUX_CONFIGS_PATH`  |
+| `-d` | `--description`   | Token description                                                                                          | string      |                         |
+| `-h` | `--help`          | Help for the `create` command                                                                              |             |                         |
+|      | `--hide-headers`  | Hide the table headers (default: `false`)                                                                  |             | `$INFLUX_HIDE_HEADERS`  |
+|      | `--host`          | HTTP address of InfluxDB                                                                                   | string      | `$INFLUX_HOST`          |
+|      | `--json`          | Output data as JSON (default: `false`)                                                                     |             | `$INFLUX_OUTPUT_JSON`   |
+|      | `--no-password`   | Don't prompt for a password (to use the token, you must set a password with `influx v1 auth set-password`) |             |                         |
+| `-o` | `--org`           | Organization name (mutually exclusive with `--org-id`)                                                     | string      | `$INFLUX_ORG`           |
+|      | `--org-id`        | Organization ID (mutually exclusive with `--org`)                                                          | string      | `$INFLUX_ORG_ID`        |
+|      | `--password`      | Password to set on the authorization                                                                       |             |                         |
+|      | `--read-bucket`   | Bucket ID to assign read permissions to                                                                    | stringArray |                         |
+|      | `--skip-verify`   | Skip TLS certificate verification                                                                          |             | `INFLUX_SKIP_VERIFY`    |
+| `-t` | `--token`         | API token                                                                                                  | string      | `$INFLUX_TOKEN`         |
+|      | `--username`      | ({{< req >}}) Token username                                                                               | string      |                         |
+|      | `--write-bucket`  | Bucket ID to assign write permissions to                                                                   | stringArray |                         |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### Create a v1 authorization with read and write permissions
+```sh
+# Create an authorization with read and write access to bucket 00xX00o0X001
+# but only read access to bucket 00xX00o0X002
+influx v1 auth create \
+  --read-bucket 00xX00o0X001 \
+  --read-bucket 00xX00o0X002 \
+  --write-bucket 00xX00o0X001 \
+  --username example-user
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/v1/auth/delete.md b/content/influxdb/v2.2/reference/cli/influx/v1/auth/delete.md
new file mode 100644
index 000000000..8033b6072
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/v1/auth/delete.md
@@ -0,0 +1,41 @@
+---
+title: influx v1 auth delete
+description: >
+  The `influx v1 auth delete` command deletes an authorization in the InfluxDB 1.x compatibility API.
+menu:
+  influxdb_2_2_ref:
+    name: influx v1 auth delete
+    parent: influx v1 auth
+weight: 101
+influxdb/v2.2/tags: [authorization]
+---
+
+The `influx v1 auth delete` command deletes an authorization in the [InfluxDB 1.x compatibility API](/influxdb/v2.2/reference/api/influxdb-1x/).
+
+## Usage
+```
+influx v1 auth delete [flags]
+```
+
+## Flags
+| Flag |                   | Description                                                              | Input type | {{< cli/mapped >}}      |
+|:-----|:------------------|:-------------------------------------------------------------------------|:----------:|:------------------------|
+| `-c` | `--active-config` | Config name to use for command                                           | string     | `$INFLUX_ACTIVE_CONFIG` |
+|      | `--configs-path`  | Path to the influx CLI configurations (default: `~/.influxdbv2/configs`) | string     | `$INFLUX_CONFIGS_PATH`  |
+| `-h` | `--help`          | Help for the `delete` command                                            |            |                         |
+|      | `--hide-headers`  | Hide the table headers (default: `false`)                                |            | `$INFLUX_HIDE_HEADERS`  |
+|      | `--host`          | HTTP address of InfluxDB                                                 | string     | `$INFLUX_HOST`          |
+| `-i` | `--id`            | ({{< req >}}) Authorization ID                                           | string     |                         |
+|      | `--json`          | Output data as JSON (default: `false`)                                   |            | `$INFLUX_OUTPUT_JSON`   |
+|      | `--skip-verify`   | Skip TLS certificate verification                                        |            | `INFLUX_SKIP_VERIFY`    |
+| `-t` | `--token`         | API token                                                                | string     | `$INFLUX_TOKEN`         |
+|      | `--username`      | Authorization username                                                   | string     | `$INFLUX_USERNAME`      |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### Delete a v1 authorization
+```sh
+influx v1 auth delete --id 00xX00o0X001
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/v1/auth/list.md b/content/influxdb/v2.2/reference/cli/influx/v1/auth/list.md
new file mode 100644
index 000000000..2066efb5b
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/v1/auth/list.md
@@ -0,0 +1,68 @@
+---
+title: influx v1 auth list
+description: >
+  The `influx v1 auth list` command lists and searches authorizations in the InfluxDB 1.x compatibility API.
+menu:
+  influxdb_2_2_ref:
+    name: influx v1 auth list
+    parent: influx v1 auth
+weight: 101
+influxdb/v2.2/tags: [authorization]
+---
+
+The `influx v1 auth list` command lists and searches authorizations in the [InfluxDB 1.x compatibility API](/influxdb/v2.2/reference/api/influxdb-1x/).
+
+## Usage
+```
+influx v1 auth list [flags]
+```
+
+#### Command aliases
+`list`, `ls`, `find`
+
+## Flags
+| Flag |                   | Description                                                              | Input type | {{< cli/mapped >}}      |
+|:-----|:------------------|:-------------------------------------------------------------------------|:----------:|:------------------------|
+| `-c` | `--active-config` | Config name to use for command                                           | string     | `$INFLUX_ACTIVE_CONFIG` |
+|      | `--configs-path`  | Path to the influx CLI configurations (default: `~/.influxdbv2/configs`) | string     | `$INFLUX_CONFIGS_PATH`  |
+| `-h` | `--help`          | Help for the `list` command                                              |            |                         |
+|      | `--hide-headers`  | Hide the table headers (default: `false`)                                |            | `$INFLUX_HIDE_HEADERS`  |
+|      | `--host`          | HTTP address of InfluxDB                                                 | string     | `$INFLUX_HOST`          |
+| `-i` | `--id`            | Authorization ID                                                         | string     |                         |
+|      | `--json`          | Output data as JSON (default: `false`)                                   |            | `$INFLUX_OUTPUT_JSON`   |
+| `-o` | `--org`           | Organization name (mutually exclusive with `--org-id`)                   | string     | `$INFLUX_ORG`           |
+|      | `--org-id`        | Organization ID (mutually exclusive with `--org`)                        | string     | `$INFLUX_ORG_ID`        |
+|      | `--skip-verify`   | Skip TLS certificate verification                                        |            | `INFLUX_SKIP_VERIFY`    |
+| `-t` | `--token`         | API token                                                                | string     | `$INFLUX_TOKEN`         |
+| `-u` | `--user`          | InfluxDB user                                                            | string     |                         |
+|      | `--user-id`       | InfluxDB user ID                                                         | string     |                         |
+|      | `--username`      | Authorization username                                                   | string     | `$INFLUX_USERNAME`      |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+- [List all v1 authorizations](#list-all-v1-authorizations)
+- [List v1 authorizations associated with a username](#list-v1-authorizations-associated-with-a-username)
+- [List v1 authorizations associated with a user ID](#list-v1-authorizations-associated-with-a-user-id)
+- [List a specific v1 authorization by ID](#list-a-specific-v1-authorization-by-id)
+
+##### List all v1 authorizations
+```sh
+influx v1 auth list
+```
+
+##### List v1 authorizations associated with a username
+```sh
+influx v1 auth list --user example-username
+```
+
+##### List v1 authorizations associated with a user ID
+```sh
+influx v1 auth list --user-id 00xX00o0X001
+```
+
+##### List a specific v1 authorization by ID
+```sh
+influx v1 auth list --id 00xX00o0X001
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/v1/auth/set-active.md b/content/influxdb/v2.2/reference/cli/influx/v1/auth/set-active.md
new file mode 100644
index 000000000..0660ee086
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/v1/auth/set-active.md
@@ -0,0 +1,42 @@
+---
+title: influx v1 auth set-active
+description: >
+  The `influx v1 auth set-active` command activates an authorization in the InfluxDB 1.x compatibility API.
+menu:
+  influxdb_2_2_ref:
+    name: influx v1 auth set-active
+    parent: influx v1 auth
+weight: 101
+influxdb/v2.2/tags: [authorization]
+---
+
+The `influx v1 auth set-active` command activates an authorization in the [InfluxDB 1.x compatibility API](/influxdb/v2.2/reference/api/influxdb-1x/).
+Only active authorizations grant access to InfluxDB.
+
+## Usage
+```
+influx v1 auth set-active [flags]
+```
+
+## Flags
+| Flag |                   | Description                                                              | Input type | {{< cli/mapped >}}      |
+|:-----|:------------------|:-------------------------------------------------------------------------|:----------:|:------------------------|
+| `-c` | `--active-config` | Config name to use for command                                           | string     | `$INFLUX_ACTIVE_CONFIG` |
+|      | `--configs-path`  | Path to the influx CLI configurations (default: `~/.influxdbv2/configs`) | string     | `$INFLUX_CONFIGS_PATH`  |
+| `-h` | `--help`          | Help for the `set-active` command                                        |            |                         |
+|      | `--hide-headers`  | Hide the table headers (default: `false`)                                |            | `$INFLUX_HIDE_HEADERS`  |
+|      | `--host`          | ({{< req >}}) HTTP address of InfluxDB                                   | string     | `$INFLUX_HOST`          |
+| `-i` | `--id`            | Authorization ID                                                         | string     |                         |
+|      | `--json`          | Output data as JSON (default: `false`)                                   |            | `$INFLUX_OUTPUT_JSON`   |
+|      | `--skip-verify`   | Skip TLS certificate verification                                        |            | `INFLUX_SKIP_VERIFY`    |
+| `-t` | `--token`         | API token                                                                | string     | `$INFLUX_TOKEN`         |
+|      | `--username`      | Authorization username                                                   | string     | `$INFLUX_USERNAME`      |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### Activate a v1 authorization
+```sh
+influx v1 auth set-active --id 00xX00o0X001
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/v1/auth/set-inactive.md b/content/influxdb/v2.2/reference/cli/influx/v1/auth/set-inactive.md
new file mode 100644
index 000000000..018e4de52
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/v1/auth/set-inactive.md
@@ -0,0 +1,42 @@
+---
+title: influx v1 auth set-inactive
+description: >
+  The `influx v1 auth set-inactive` command deactivates an authorization in the InfluxDB 1.x compatibility API.
+menu:
+  influxdb_2_2_ref:
+    name: influx v1 auth set-inactive
+    parent: influx v1 auth
+weight: 101
+influxdb/v2.2/tags: [authorization]
+---
+
+The `influx v1 auth set-inactive` command deactivates an authorization in the [InfluxDB 1.x compatibility API](/influxdb/v2.2/reference/api/influxdb-1x/).
+Inactive authorizations **do not** grant access to InfluxDB.
+
+## Usage
+```
+influx v1 auth set-inactive [flags]
+```
+
+## Flags
+| Flag |                   | Description                                                              | Input type | {{< cli/mapped >}}      |
+|:-----|:------------------|:-------------------------------------------------------------------------|:----------:|:------------------------|
+| `-c` | `--active-config` | Config name to use for command                                           | string     | `$INFLUX_ACTIVE_CONFIG` |
+|      | `--configs-path`  | Path to the influx CLI configurations (default: `~/.influxdbv2/configs`) | string     | `$INFLUX_CONFIGS_PATH`  |
+| `-h` | `--help`          | Help for the `set-inactive` command                                      |            |                         |
+|      | `--hide-headers`  | Hide the table headers (default: `false`)                                |            | `$INFLUX_HIDE_HEADERS`  |
+|      | `--host`          | HTTP address of InfluxDB                                                 | string     | `$INFLUX_HOST`          |
+| `-i` | `--id`            | ({{< req >}}) Authorization ID                                           | string     |                         |
+|      | `--json`          | Output data as JSON (default: `false`)                                   |            | `$INFLUX_OUTPUT_JSON`   |
+|      | `--skip-verify`   | Skip TLS certificate verification                                        |            | `INFLUX_SKIP_VERIFY`    |
+| `-t` | `--token`         | API token                                                                | string     | `$INFLUX_TOKEN`         |
+|      | `--username`      | Authorization username                                                   | string     | `$INFLUX_USERNAME`      |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### Deactivate a v1 authorization
+```sh
+influx v1 auth set-inactive --id 00xX00o0X001
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/v1/auth/set-password.md b/content/influxdb/v2.2/reference/cli/influx/v1/auth/set-password.md
new file mode 100644
index 000000000..a4831e6cf
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/v1/auth/set-password.md
@@ -0,0 +1,43 @@
+---
+title: influx v1 auth set-password
+description: >
+  The `influx v1 auth set-password` command sets a password for an existing authorization in the InfluxDB 1.x compatibility API.
+menu:
+  influxdb_2_2_ref:
+    name: influx v1 auth set-password
+    parent: influx v1 auth
+weight: 101
+influxdb/v2.2/tags: [authorization]
+updated_in: CLI v2.0.3
+---
+
+The `influx v1 auth set-password` command sets a password for an existing authorization in the [InfluxDB 1.x compatibility API](/influxdb/v2.2/reference/api/influxdb-1x/).
+
+## Usage
+```
+influx v1 auth set-password [flags]
+```
+
+## Flags
+| Flag |                   | Description                                                              | Input type | {{< cli/mapped >}}      |
+|:-----|:------------------|:-------------------------------------------------------------------------|:----------:|:------------------------|
+| `-c` | `--active-config` | Config name to use for command                                           | string     | `$INFLUX_ACTIVE_CONFIG` |
+|      | `--configs-path`  | Path to the influx CLI configurations (default: `~/.influxdbv2/configs`) | string     | `$INFLUX_CONFIGS_PATH`  |
+| `-h` | `--help`          | Help for the `set-password` command                                      |            |                         |
+|      | `--host`          | HTTP address of InfluxDB                                                 | string     | `$INFLUX_HOST`          |
+| `-i` | `--id`            | Authorization ID                                                         | string     |                         |
+|      | `--password`      | Password to set on the authorization                                     | string     |                         |
+|      | `--skip-verify`   | Skip TLS certificate verification                                        |            | `INFLUX_SKIP_VERIFY`    |
+| `-t` | `--token`         | API token                                                                | string     | `$INFLUX_TOKEN`         |
+|      | `--username`      | Authorization username                                                   | string     | `$INFLUX_USERNAME`      |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### Set a password for a v1 authorization
+```sh
+influx v1 auth set-password \
+  --id 00xX00o0X001 \
+  --password ExAmPl3PA55W0rD
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/v1/dbrp/_index.md b/content/influxdb/v2.2/reference/cli/influx/v1/dbrp/_index.md
new file mode 100644
index 000000000..42aa81174
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/v1/dbrp/_index.md
@@ -0,0 +1,37 @@
+---
+title: influx v1 dbrp
+description: >
+  The `influx v1 dbrp` subcommands manage database and retention policy mappings (DBRP)
+  for the [InfluxDB 1.x compatibility API](/influxdb/v2.2/reference/api/influxdb-1x/).
+menu:
+  influxdb_2_2_ref:
+    name: influx v1 dbrp
+    parent: influx v1
+weight: 101
+influxdb/v2.2/tags: [DBRP]
+cascade:
+  metadata: [influx CLI 2.0.2+, InfluxDB 2.0.1+]
+---
+
+The `influx v1 dbrp` subcommands manage database and retention policy mappings (DBRP)
+for the [InfluxDB 1.x compatibility API](/influxdb/v2.2/reference/api/influxdb-1x/).
+
+## Usage
+```
+influx v1 dbrp [flags]
+influx v1 dbrp [command]
+```
+
+## Commands
+
+| Command                                                       | Description           |
+|:------------------------------------------------------------- |:--------------------- |
+| [create](/influxdb/v2.2/reference/cli/influx/v1/dbrp/create/) | Create a DBRP mapping |
+| [delete](/influxdb/v2.2/reference/cli/influx/v1/dbrp/delete/) | Delete a DBRP mapping |
+| [list](/influxdb/v2.2/reference/cli/influx/v1/dbrp/list/)     | List DBRP mappings    |
+| [update](/influxdb/v2.2/reference/cli/influx/v1/dbrp/update/) | Update a DBRP mapping |
+
+## Flags
+| Flag |          | Description                     |
+|:-----|:---------|:--------------------------------|
+| `-h` | `--help` | Help for the `v1 dbrp ` command |
diff --git a/content/influxdb/v2.2/reference/cli/influx/v1/dbrp/create.md b/content/influxdb/v2.2/reference/cli/influx/v1/dbrp/create.md
new file mode 100644
index 000000000..5fa39caeb
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/v1/dbrp/create.md
@@ -0,0 +1,50 @@
+---
+title: influx v1 dbrp create
+description: >
+  The `influx v1 dbrp create` command creates a DBRP mapping in the InfluxDB 1.x compatibility API.
+menu:
+  influxdb_2_2_ref:
+    name: influx v1 dbrp create
+    parent: influx v1 dbrp
+weight: 101
+influxdb/v2.2/tags: [DBRP]
+---
+
+The `influx v1 dbrp create` command creates a DBRP mapping with the [InfluxDB 1.x compatibility API](/influxdb/v2.2/reference/api/influxdb-1x/).
+
+## Usage
+```
+influx v1 dbrp create [flags]
+```
+
+## Flags
+| Flag |                   | Description                                                              | Input type | {{< cli/mapped >}}      |
+|:-----|:------------------|:-------------------------------------------------------------------------|:----------:|:------------------------|
+| `-c` | `--active-config` | Config name to use for command                                           | string     | `$INFLUX_ACTIVE_CONFIG` |
+|      | `--bucket-id`     | Bucket ID to map to                                                      |            |                         |
+|      | `--configs-path`  | Path to the influx CLI configurations (default: `~/.influxdbv2/configs`) | string     | `$INFLUX_CONFIGS_PATH`  |
+|      | `--db`            | InfluxDB v1 database to map from                                         |            |                         |
+|      | `--default`       | Set DBRP mapping's retention policy as default                           |            |                         |
+| `-h` | `--help`          | Help for the `create` command                                            |            |                         |
+|      | `--hide-headers`  | Hide table headers (default: `false`)                                    |            | `$INFLUX_HIDE_HEADERS`  |
+|      | `--host`          | HTTP address of InfluxDB                                                 | string     | `$INFLUX_HOST`          |
+|      | `--json`          | Output data as JSON (default: `false`)                                   |            | `$INFLUX_OUTPUT_JSON`   |
+| `-o` | `--org`           | Organization name (mutually exclusive with `--org-id`)                   | string     | `$INFLUX_ORG`           |
+|      | `--org-id`        | Organization ID (mutually exclusive with `--org`)                        | string     | `$INFLUX_ORG_ID`        |
+|      | `--rp`            | InfluxDB v1 retention policy to map from                                 |            |                         |
+|      | `--skip-verify`   | Skip TLS certificate verification                                        |            | `INFLUX_SKIP_VERIFY`    |
+| `-t` | `--token`         | API token                                                                | string     | `$INFLUX_TOKEN`         |
+
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### Create a DBRP mapping
+```sh
+influx v1 dbrp create \
+  --bucket-id 12ab34cd56ef \
+  --db example-db \
+  --rp example-rp \
+  --default
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/v1/dbrp/delete.md b/content/influxdb/v2.2/reference/cli/influx/v1/dbrp/delete.md
new file mode 100644
index 000000000..3af9ab96e
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/v1/dbrp/delete.md
@@ -0,0 +1,42 @@
+---
+title: influx v1 dbrp delete
+description: >
+  The `influx v1 dbrp delete` command deletes a DBRP mapping in the InfluxDB 1.x compatibility API.
+menu:
+  influxdb_2_2_ref:
+    name: influx v1 dbrp delete
+    parent: influx v1 dbrp
+weight: 101
+influxdb/v2.2/tags: [DBRP]
+---
+
+The `influx v1 dbrp delete` command deletes a DBRP mapping in the [InfluxDB 1.x compatibility API](/influxdb/v2.2/reference/api/influxdb-1x/).
+
+## Usage
+```
+influx v1 dbrp delete [flags]
+```
+
+## Flags
+| Flag |                   | Description                                                              | Input type | {{< cli/mapped >}}      |
+|------|-------------------|--------------------------------------------------------------------------|------------|-------------------------|
+| `-c` | `--active-config` | Config name to use for command                                           | string     | `$INFLUX_ACTIVE_CONFIG` |
+|      | `--configs-path`  | Path to the influx CLI configurations (default: `~/.influxdbv2/configs`) | string     | `$INFLUX_CONFIGS_PATH`  |
+| `-h` | `--help`          | Help for the `delete` command                                            |            |                         |
+|      | `--hide-headers`  | Hide the table headers (default: `false`)                                |            | `$INFLUX_HIDE_HEADERS`  |
+|      | `--host`          | HTTP address of InfluxDB                                                 | string     | `$INFLUX_HOST`          |
+|      | `--id`            | ({{< req >}}) DBRP ID                                                    | string     |                         |
+|      | `--json`          | Output data as JSON (default: `false`)                                   |            | `$INFLUX_OUTPUT_JSON`   |
+| `-o` | `--org`           | Organization name (mutually exclusive with `--org-id`)                   | string     | `$INFLUX_ORG`           |
+|      | `--org-id`        | Organization ID (mutually exclusive with `--org`)                        | string     | `$INFLUX_ORG_ID`        |
+|      | `--skip-verify`   | Skip TLS certificate verification                                        |            | `INFLUX_SKIP_VERIFY`    |
+| `-t` | `--token`         | API token                                                                | string     | `$INFLUX_TOKEN`         |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### Delete a DBRP mapping
+```sh
+influx v1 dbrp delete --id 12ab34cd56ef
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/v1/dbrp/list.md b/content/influxdb/v2.2/reference/cli/influx/v1/dbrp/list.md
new file mode 100644
index 000000000..829f2db05
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/v1/dbrp/list.md
@@ -0,0 +1,64 @@
+---
+title: influx v1 dbrp list
+description: >
+  The `influx v1 dbrp list` command lists and searches DBRP mappings in the InfluxDB 1.x compatibility API.
+menu:
+  influxdb_2_2_ref:
+    name: influx v1 dbrp list
+    parent: influx v1 dbrp
+weight: 101
+influxdb/v2.2/tags: [dbrp]
+---
+
+The `influx v1 dbrp list` command lists and searches DBRP mappings in the [InfluxDB 1.x compatibility API](/influxdb/v2.2/reference/api/influxdb-1x/).
+
+## Usage
+```
+influx v1 dbrp list [flags]
+```
+
+## Flags
+
+| Flag |                   | Description                                                              | Input type | {{< cli/mapped >}}      |
+|------|-------------------|--------------------------------------------------------------------------|------------|-------------------------|
+| `-c` | `--active-config` | Config name to use for command                                           | string     | `$INFLUX_ACTIVE_CONFIG` |
+|      | `--bucket-id`     | Bucket ID                                                                |            |                         |
+|      | `--configs-path`  | Path to the influx CLI configurations (default: `~/.influxdbv2/configs`) | string     | `$INFLUX_CONFIGS_PATH`  |
+|      | `--db`            | Filter DBRP mappings by database                                         |            |                         |
+|      | `--default`       | Limit results to default mapping                                         |            |                         |
+| `-h` | `--help`          | Help for the `list` command                                              |            |                         |
+|      | `--hide-headers`  | Hide the table headers (default: `false`)                                |            | `$INFLUX_HIDE_HEADERS`  |
+|      | `--host`          | HTTP address of InfluxDB                                                 | string     | `$INFLUX_HOST`          |
+|      | `--id`            | Limit results to a specified mapping                                     | string     |                         |
+|      | `--json`          | Output data as JSON (default: `false`)                                   |            | `$INFLUX_OUTPUT_JSON`   |
+| `-o` | `--org`           | Organization name (mutually exclusive with `--org-id`)                   | string     | `$INFLUX_ORG`           |
+|      | `--org-id`        | Organization ID (mutually exclusive with `--org`)                        | string     | `$INFLUX_ORG_ID`        |
+|      | `--rp`            | Filter DBRP mappings by InfluxDB v1 retention policy                     | string     | `$INFLUX_ORG`           |
+|      | `--skip-verify`   | Skip TLS certificate verification                                        |            | `INFLUX_SKIP_VERIFY`    |
+| `-t` | `--token`         | API token                                                                | string     | `$INFLUX_TOKEN`         |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### List all DBRP mappings in your organization
+```sh
+influx v1 dbrp list
+```
+
+##### List DBRP mappings for specific buckets
+```sh
+influx v1 dbrp list \
+  --bucket-id 12ab34cd56ef78 \
+  --bucket-id 09zy87xw65vu43
+```
+
+##### List DBRP mappings with a specific database
+```sh
+influx v1 dbrp list --db example-db
+```
+
+##### List DBRP mappings with a specific retention policy
+```sh
+influx v1 dbrp list --rp example-rp
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/v1/dbrp/update.md b/content/influxdb/v2.2/reference/cli/influx/v1/dbrp/update.md
new file mode 100644
index 000000000..908492161
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/v1/dbrp/update.md
@@ -0,0 +1,53 @@
+---
+title: influx v1 dbrp update
+description: >
+  The `influx v1 dbrp update` command updates a DBRP mapping in the InfluxDB 1.x compatibility API.
+menu:
+  influxdb_2_2_ref:
+    name: influx v1 dbrp update
+    parent: influx v1 dbrp
+weight: 101
+influxdb/v2.2/tags: [DBRP]
+---
+
+The `influx v1 dbrp update` command updates a DBRP mapping in the [InfluxDB 1.x compatibility API](/influxdb/v2.2/reference/api/influxdb-1x/).
+
+## Usage
+```
+influx v1 dbrp update [flags]
+```
+
+## Flags
+| Flag |                   | Description                                                              | Input type | {{< cli/mapped >}}      |
+|:-----|:------------------|:-------------------------------------------------------------------------|:----------:|:------------------------|
+| `-c` | `--active-config` | Config name to use for command                                           | string     | `$INFLUX_ACTIVE_CONFIG` |
+|      | `--configs-path`  | Path to the influx CLI configurations (default: `~/.influxdbv2/configs`) | string     | `$INFLUX_CONFIGS_PATH`  |
+|      | `--default`       | Set DBRP mapping's retention policy as default                           |            |                         |
+| `-h` | `--help`          | Help for the `update` command                                            |            |                         |
+|      | `--hide-headers`  | Hide the table headers (default: `false`)                                |            | `$INFLUX_HIDE_HEADERS`  |
+|      | `--host`          | HTTP address of InfluxDB                                                 | string     | `$INFLUX_HOST`          |
+|      | `--id`            | ({{< req >}}) DBRP ID                                                    | string     |                         |
+|      | `--json`          | Output data as JSON (default: `false`)                                   |            | `$INFLUX_OUTPUT_JSON`   |
+| `-o` | `--org`           | Organization name (mutually exclusive with `--org-id`)                   | string     | `$INFLUX_ORG`           |
+|      | `--org-id`        | Organization ID (mutually exclusive with `--org`)                        | string     | `$INFLUX_ORG_ID`        |
+| `-r` | `--rp`            | InfluxDB v1 retention policy to map from                                 |            |                         |
+|      | `--skip-verify`   | Skip TLS certificate verification                                        |            | `INFLUX_SKIP_VERIFY`    |
+| `-t` | `--token`         | API token                                                                | string     | `$INFLUX_TOKEN`         |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+##### Set a DBRP mapping as default
+```sh
+influx v1 dbrp update \
+  --id 12ab34cd56ef78 \
+  --default
+```
+
+##### Update the retention policy of a DBRP mapping
+```sh
+influx v1 dbrp update \
+  --id 12ab34cd56ef78 \
+  --rp new-rp-name
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/version/_index.md b/content/influxdb/v2.2/reference/cli/influx/version/_index.md
new file mode 100644
index 000000000..879f56096
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/version/_index.md
@@ -0,0 +1,25 @@
+---
+title: influx version
+description: The `influx version` command outputs the current version of the influx command line interface (CLI).
+influxdb/v2.2/tags: [influx, cli]
+menu:
+  influxdb_2_2_ref:
+    parent: influx
+weight: 202
+metadata: [influx CLI 2.0.0+]
+---
+
+The `influx version` command outputs the current version of the `influx`
+command line interface (CLI).
+
+## Usage
+
+```
+influx version [flags]
+```
+
+## Flags
+
+| Flag |          | Description                    |
+| :--- | :------- | :----------------------------- |
+| `-h` | `--help` | Help for the `version` command |
diff --git a/content/influxdb/v2.2/reference/cli/influx/write/_index.md b/content/influxdb/v2.2/reference/cli/influx/write/_index.md
new file mode 100644
index 000000000..976f313c0
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/write/_index.md
@@ -0,0 +1,289 @@
+---
+title: influx write
+description: >
+  The `influx write` command writes data to InfluxDB via stdin or from a specified file.
+  Write data using line protocol, annotated CSV, or extended annotated CSV.
+menu:
+  influxdb_2_2_ref:
+    name: influx write
+    parent: influx
+weight: 101
+influxdb/v2.2/tags: [write]
+cascade:
+  related:
+    - /influxdb/v2.2/write-data/
+    - /influxdb/v2.2/write-data/developer-tools/csv/
+    - /influxdb/v2.2/reference/syntax/line-protocol/
+    - /influxdb/v2.2/reference/syntax/annotated-csv/
+    - /influxdb/v2.2/reference/syntax/annotated-csv/extended/
+    - /influxdb/v2.2/reference/cli/influx/#provide-required-authentication-credentials, influx CLI—Provide required authentication credentials
+    - /influxdb/v2.2/reference/cli/influx/#flag-patterns-and-conventions, influx CLI—Flag patterns and conventions
+  metadata: [influx CLI 2.0.0+, InfluxDB 2.0.0+]
+updated_in: CLI v2.0.5
+---
+
+The `influx write` command writes data to InfluxDB via stdin or from a specified file.
+Write data using [line protocol](/influxdb/v2.2/reference/syntax/line-protocol),
+[annotated CSV](/influxdb/v2.2/reference/syntax/annotated-csv), or
+[extended annotated CSV](/influxdb/v2.2/reference/syntax/annotated-csv/extended/).
+If you write CSV data, CSV annotations determine how the data translates into line protocol.
+
+
+## Usage
+```
+influx write [flags]
+influx write [command]
+```
+
+{{% note %}}
+### Required data
+To write data to InfluxDB, you must provide the following for each row:
+
+- **measurement**
+- **field**
+- **value**
+
+#### Line protocol
+In **line protocol**, the [structure of the line data](/influxdb/v2.2/reference/syntax/line-protocol/#elements-of-line-protocol)
+determines the measurement, field, and value.
+
+#### Annotated CSV
+In **annotated CSV**, measurements, fields, and values are represented by the
+`_measurement`, `_field`, and `_value` columns.
+Their types are determined by CSV annotations.
+To successfully write annotated CSV to InfluxDB, include all
+[annotation rows](/influxdb/v2.2/reference/syntax/annotated-csv/#annotations).
+
+#### Extended annotated CSV
+In **extended annotated CSV**, measurements, fields, and values and their types are determined by
+[CSV annotations](/influxdb/v2.2/reference/syntax/annotated-csv/extended/#csv-annotations).
+{{% /note %}}
+
+## Subcommands
+| Subcommand                                                 | Description                         |
+|:----------                                                 |:-----------                         |
+| [dryrun](/influxdb/v2.2/reference/cli/influx/write/dryrun) | Write to stdout instead of InfluxDB |
+
+## Flags
+| Flag |                     | Description                                                                                | Input type  | {{< cli/mapped >}}    |
+|:-----|:--------------------|:-------------------------------------------------------------------------------------------|:-----------:|:----------------------|
+| `-c` | `--active-config`   | CLI configuration to use for command                                                       | string      |                       |
+| `-b` | `--bucket`          | Bucket name (mutually exclusive with `--bucket-id`)                                        | string      | `INFLUX_BUCKET_NAME`  |
+|      | `--bucket-id`       | Bucket ID (mutually exclusive with `--bucket`)                                             | string      | `INFLUX_BUCKET_ID`    |
+|      | `--configs-path`    | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`)                      | string      | `INFLUX_CONFIGS_PATH` |
+|      | `--compression`     | Input compression (`none` or `gzip`, default is `none` unless input file ends with `.gz`.) | string      |                       |
+|      | `--debug`           | Output errors to stderr                                                                    |             |                       |
+|      | `--encoding`        | Character encoding of input (default `UTF-8`)                                              | string      |                       |
+|      | `--error-file`      | Path to a file used for recording rejected row errors                                      | string      |                       |
+| `-f` | `--file`            | File to import                                                                             | stringArray |                       |
+|      | `--format`          | Input format (`lp` or `csv`, default `lp`)                                                 | string      |                       |
+|      | `--header`          | Prepend header line to CSV input data                                                      | string      |                       |
+| `-h` | `--help`            | Help for the `write` command                                                               |             |                       |
+|      | `--host`            | HTTP address of InfluxDB (default `http://localhost:8086`)                                 | string      | `INFLUX_HOST`         |
+|      | `--max-line-length` | Maximum number of bytes that can be read for a single line (default `16000000`)            | integer     |                       |
+| `-o` | `--org`             | Organization name (mutually exclusive with `--org-id`)                                     | string      | `INFLUX_ORG`          |
+|      | `--org-id`          | Organization ID (mutually exclusive with `--org`)                                          | string      | `INFLUX_ORG_ID`       |
+| `-p` | `--precision`       | [Precision](/influxdb/v2.2/write-data/#timestamp-precision) of the timestamps (default `ns`)                                                 | string      | `INFLUX_PRECISION`    |
+|      | `--rate-limit`      | Throttle write rate (examples: `5 MB / 5 min` or `1MB/s`).                                 | string      |                       |
+|      | `--skip-verify`     | Skip TLS certificate verification                                                          |             | `INFLUX_SKIP_VERIFY`  |
+|      | `--skipHeader`      | Skip first *n* rows of input data                                                          | integer     |                       |
+|      | `--skipRowOnError`  | Output CSV errors to stderr, but continue processing                                       |             |                       |
+| `-t` | `--token`           | API token                                                                                  | string      | `INFLUX_TOKEN`        |
+| `-u` | `--url`             | URL to import data from                                                                    | stringArray |                       |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+###### Write line protocol
+
+- [via stdin](#write-line-protocol-via-stdin)
+- [from a file](#write-line-protocol-from-a-file)
+- [from multiple files](#write-line-protocol-from-multiple-files)
+- [from a URL](#write-line-protocol-from-a-url)
+- [from multiple URLs](#write-line-protocol-from-multiple-urls)
+- [from multiple sources](#write-line-protocol-from-multiple-sources)
+- [from a compressed file](#write-line-protocol-from-a-compressed-file)
+
+###### Write CSV data
+
+- [annotated CSV via stdin](#write-annotated-csv-data-via-stdin)
+- [extended annotated CSV via stdin](#write-extended-annotated-csv-data-via-stdin)
+- [from a file](#write-annotated-csv-data-from-a-file)
+- [from multiple files](#write-annotated-csv-data-from-multiple-files)
+- [from a URL](#write-annotated-csv-data-from-a-url)
+- [from multiple URLs](#write-annotated-csv-data-from-multiple-urls)
+- [from multiple sources](#write-annotated-csv-data-from-multiple-sources)
+- [and prepend annotation headers](#prepend-csv-data-with-annotation-headers)
+- [from a compressed file](#write-annotated-csv-data-from-a-compressed-file)
+- [using rate limiting](#write-annotated-csv-data-using-rate-limiting)
+
+### Line protocol
+
+##### Write line protocol via stdin
+```sh
+influx write --bucket example-bucket "
+m,host=host1 field1=1.2
+m,host=host2 field1=2.4
+m,host=host1 field2=5i
+m,host=host2 field2=3i
+"
+```
+
+##### Write line protocol from a file
+```sh
+influx write \
+  --bucket example-bucket \
+  --file path/to/line-protocol.txt
+```
+
+##### Write line protocol from multiple files
+```sh
+influx write \
+  --bucket example-bucket \
+  --file path/to/line-protocol-1.txt \
+  --file path/to/line-protocol-2.txt
+```
+
+##### Write line protocol from a URL
+```sh
+influx write \
+  --bucket example-bucket \
+  --url https://example.com/line-protocol.txt
+```
+
+##### Write line protocol from multiple URLs
+```sh
+influx write \
+  --bucket example-bucket \
+  --url https://example.com/line-protocol-1.txt \
+  --url https://example.com/line-protocol-2.txt
+```
+
+##### Write line protocol from multiple sources
+```sh
+influx write \
+  --bucket example-bucket \
+  --file path/to/line-protocol-1.txt \
+  --url https://example.com/line-protocol-2.txt
+```
+
+##### Write line protocol from a compressed file
+```sh
+# The influx CLI assumes files with the .gz extension use gzip compression 
+influx write \
+  --bucket example-bucket \
+  --file path/to/line-protocol.txt.gz
+
+# Specify gzip compression for gzipped files without the .gz extension
+influx write \
+  --bucket example-bucket \
+  --file path/to/line-protocol.txt.comp \
+  --compression gzip
+```
+
+---
+
+### CSV
+
+##### Write annotated CSV data via stdin
+```sh
+influx write \
+  --bucket example-bucket \
+  --format csv \
+  "#group,false,false,false,false,true,true
+#datatype,string,long,dateTime:RFC3339,double,string,string
+#default,_result,,,,,
+,result,table,_time,_value,_field,_measurement
+,,0,2020-12-18T18:16:11Z,72.7,temp,sensorData
+,,0,2020-12-18T18:16:21Z,73.8,temp,sensorData
+,,0,2020-12-18T18:16:31Z,72.7,temp,sensorData
+,,0,2020-12-18T18:16:41Z,72.8,temp,sensorData
+,,0,2020-12-18T18:16:51Z,73.1,temp,sensorData
+"
+```
+
+##### Write extended annotated CSV data via stdin
+```sh
+influx write \
+  --bucket example-bucket \
+  --format csv \
+  "#constant measurement,sensorData
+#datatype,datetime:RFC3339,double
+time,temperature
+2020-12-18T18:16:11Z,72.7
+2020-12-18T18:16:21Z,73.8
+2020-12-18T18:16:31Z,72.7
+2020-12-18T18:16:41Z,72.8
+2020-12-18T18:16:51Z,73.1
+"
+```
+
+##### Write annotated CSV data from a file
+```sh
+influx write \
+  --bucket example-bucket \
+  --file path/to/data.csv
+```
+
+##### Write annotated CSV data from multiple files
+```sh
+influx write \
+  --bucket example-bucket \
+  --file path/to/data-1.csv \
+  --file path/to/data-2.csv
+```
+
+##### Write annotated CSV data from a URL
+```sh
+influx write \
+  --bucket example-bucket \
+  --url https://example.com/data.csv
+```
+
+##### Write annotated CSV data from multiple URLs
+```sh
+influx write \
+  --bucket example-bucket \
+  --url https://example.com/data-1.csv \
+  --url https://example.com/data-2.csv
+```
+
+##### Write annotated CSV data from multiple sources
+```sh
+influx write \
+  --bucket example-bucket \
+  --file path/to/data-1.csv \
+  --url https://example.com/data-2.csv
+```
+
+##### Prepend CSV data with annotation headers
+```sh
+influx write \
+  --bucket example-bucket \
+  --header "#constant measurement,birds" \
+  --header "#datatype dateTime:2006-01-02,long,tag" \
+  --file path/to/data.csv
+```
+
+##### Write annotated CSV data from a compressed file
+```sh
+# The influx CLI assumes files with the .gz extension use gzip compression 
+influx write \
+  --bucket example-bucket \
+  --file path/to/data.csv.gz
+
+# Specify gzip compression for gzipped files without the .gz extension
+influx write \
+  --bucket example-bucket \
+  --file path/to/data.csv.comp \
+  --compression gzip
+```
+
+##### Write annotated CSV data using rate limiting
+```sh
+influx write \
+  --bucket example-bucket \
+  --file path/to/data.csv \
+  --rate-limit 5 MB / 5 min
+```
diff --git a/content/influxdb/v2.2/reference/cli/influx/write/dryrun.md b/content/influxdb/v2.2/reference/cli/influx/write/dryrun.md
new file mode 100644
index 000000000..e93ef17a4
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influx/write/dryrun.md
@@ -0,0 +1,192 @@
+---
+title: influx write dryrun
+description: >
+  The `influx write dryrun` command prints write output to stdout instead of writing
+  to InfluxDB. Use this command to test writing data.
+menu:
+  influxdb_2_2_ref:
+    name: influx write dryrun
+    parent: influx write
+weight: 101
+influxdb/v2.2/tags: [write]
+related:
+  - /influxdb/v2.2/write-data/
+  - /influxdb/v2.2/write-data/developer-tools/csv/
+  - /influxdb/v2.2/reference/syntax/line-protocol/
+  - /influxdb/v2.2/reference/syntax/annotated-csv/
+  - /influxdb/v2.2/reference/syntax/annotated-csv/extended/
+---
+
+The `influx write dryrun` command prints write output to stdout instead of writing
+to InfluxDB. Use this command to test writing data.
+
+Supports [line protocol](/influxdb/v2.2/reference/syntax/line-protocol),
+[annotated CSV](/influxdb/v2.2/reference/syntax/annotated-csv), and
+[extended annotated CSV](/influxdb/v2.2/reference/syntax/annotated-csv/extended).
+Output is always **line protocol**.
+
+## Usage
+```
+influx write dryrun [flags]
+```
+
+## Flags
+| Flag |                     | Description                                                                     | Input type  | {{< cli/mapped >}}    |
+|:-----|:--------------------|:--------------------------------------------------------------------------------|:-----------:|:----------------------|
+| `-c` | `--active-config`   | CLI configuration to use for command                                            | string      |                       |
+| `-b` | `--bucket`          | Bucket name (mutually exclusive with `--bucket-id`)                             | string      | `INFLUX_BUCKET_NAME`  |
+|      | `--bucket-id`       | Bucket ID (mutually exclusive with `--bucket`)                                  | string      | `INFLUX_BUCKET_ID`    |
+|      | `--configs-path`    | Path to `influx` CLI configurations (default `~/.influxdbv2/configs`)           | string      | `INFLUX_CONFIGS_PATH` |
+|      | `--debug`           | Output errors to stderr                                                         |             |                       |
+|      | `--encoding`        | Character encoding of input (default `UTF-8`)                                   | string      |                       |
+|      | `--error-file`      | Path to a file used for recording rejected row errors                           | string      |                       |
+| `-f` | `--file`            | File to import                                                                  | stringArray |                       |
+|      | `--format`          | Input format (`lp` or `csv`, default `lp`)                                      | string      |                       |
+|      | `--header`          | Prepend header line to CSV input data                                           | string      |                       |
+| `-h` | `--help`            | Help for the `dryrun` command                                                   |             |                       |
+|      | `--host`            | HTTP address of InfluxDB (default `http://localhost:9999`)                      | string      | `INFLUX_HOST`         |
+|      | `--max-line-length` | Maximum number of bytes that can be read for a single line (default `16000000`) | integer     |                       |
+| `-o` | `--org`             | Organization name (mutually exclusive with `--org-id`)                          | string      | `INFLUX_ORG`          |
+|      | `--org-id`          | Organization ID (mutually exclusive with `--org`)                               | string      | `INFLUX_ORG_ID`       |
+| `-p` | `--precision`       | Precision of the timestamps (default `ns`)                                      | string      | `INFLUX_PRECISION`    |
+|      | `--rate-limit`      | Throttle write rate (examples: `5 MB / 5 min` or `1MB/s`).                      | string      |                       |
+|      | `--skip-verify`     | Skip TLS certificate verification                                               |             | `INFLUX_SKIP_VERIFY`                      |
+|      | `--skipHeader`      | Skip first *n* rows of input data                                               | integer     |                       |
+|      | `--skipRowOnError`  | Output CSV errors to stderr, but continue processing                            |             |                       |
+| `-t` | `--token`           | API token                                                                       | string      | `INFLUX_TOKEN`        |
+| `-u` | `--url`             | URL to import data from                                                         | stringArray |                       |
+
+## Examples
+
+{{< cli/influx-creds-note >}}
+
+- [Dry run writing line protocol](#line-protocol)
+  - [via stdin](#dry-run-writing-line-protocol-via-stdin)
+  - [from a file](#dry-run-writing-line-protocol-from-a-file)
+  - [from multiple files](#dry-run-writing-line-protocol-from-multiple-files)
+  - [from a URL](#dry-run-writing-line-protocol-from-a-url)
+  - [from multiple URLs](#dry-run-writing-line-protocol-from-multiple-urls)
+  - [from multiple sources](#dry-run-writing-line-protocol-from-multiple-sources)
+
+- [Dry run writing CSV data](#csv)
+  - [via stdin](#dry-run-writing-annotated-csv-data-via-stdin)
+  - [from a file](#dry-run-writing-annotated-csv-data-from-a-file)
+  - [from multiple files](#dry-run-writing-annotated-csv-data-from-multiple-files)
+  - [from a URL](#dry-run-writing-annotated-csv-data-from-a-url)
+  - [from multiple URLs](#dry-run-writing-annotated-csv-data-from-multiple-urls)
+  - [from multiple sources](#dry-run-writing-annotated-csv-data-from-multiple-sources)
+  - [and prepending annotation headers](#dry-run-prepending-csv-data-with-annotation-headers)
+
+
+### Line protocol
+
+##### Dry run writing line protocol via stdin
+```sh
+influx write --bucket example-bucket "
+m,host=host1 field1=1.2
+m,host=host2 field1=2.4
+m,host=host1 field2=5i
+m,host=host2 field2=3i
+"
+```
+
+##### Dry run writing line protocol from a file
+```sh
+influx write dryrun \
+  --bucket example-bucket \
+  --file path/to/line-protocol.txt
+```
+
+##### Dry run writing line protocol from multiple files
+```sh
+influx write dryrun \
+  --bucket example-bucket \
+  --file path/to/line-protocol-1.txt \
+  --file path/to/line-protocol-2.txt
+```
+
+##### Dry run writing line protocol from a URL
+```sh
+influx write dryrun \
+  --bucket example-bucket \
+  --url https://example.com/line-protocol.txt
+```
+
+##### Dry run writing line protocol from multiple URLs
+```sh
+influx write dryrun \
+  --bucket example-bucket \
+  --url https://example.com/line-protocol-1.txt \
+  --url https://example.com/line-protocol-2.txt
+```
+
+##### Dry run writing line protocol from multiple sources
+```sh
+influx write dryrun \
+  --bucket example-bucket \
+  --file path/to/line-protocol-1.txt \
+  --url https://example.com/line-protocol-2.txt
+```
+
+---
+
+### CSV
+
+##### Dry run writing annotated CSV data via stdin
+```sh
+influx write dryrun \
+  --bucket example-bucket \
+  --format csv \
+  "#datatype measurement,tag,tag,field,field,ignored,time
+m,cpu,host,time_steal,usage_user,nothing,time
+cpu,cpu1,host1,0,2.7,a,1482669077000000000
+cpu,cpu1,host2,0,2.2,b,1482669087000000000
+"
+```
+
+##### Dry run writing annotated CSV data from a file
+```sh
+influx write dryrun \
+  --bucket example-bucket \
+  --file path/to/data.csv
+```
+
+##### Dry run writing annotated CSV data from multiple files
+```sh
+influx write dryrun \
+  --bucket example-bucket \
+  --file path/to/data-1.csv \
+  --file path/to/data-2.csv
+```
+
+##### Dry run writing annotated CSV data from a URL
+```sh
+influx write dryrun \
+  --bucket example-bucket \
+  --url https://example.com/data.csv
+```
+
+##### Dry run writing annotated CSV data from multiple URLs
+```sh
+influx write dryrun \
+  --bucket example-bucket \
+  --url https://example.com/data-1.csv \
+  --url https://example.com/data-2.csv
+```
+
+##### Dry run writing annotated CSV data from multiple sources
+```sh
+influx write dryrun \
+  --bucket example-bucket \
+  --file path/to/data-1.csv \
+  --url https://example.com/data-2.csv
+```
+
+##### Dry run prepending CSV data with annotation headers
+```sh
+influx write dryrun \
+  --bucket example-bucket \
+  --header "#constant measurement,birds" \
+  --header "#datatype dataTime:2006-01-02,long,tag" \
+  --file path/to/data.csv
+```
diff --git a/content/influxdb/v2.2/reference/cli/influxd/_index.md b/content/influxdb/v2.2/reference/cli/influxd/_index.md
new file mode 100644
index 000000000..c147350b6
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influxd/_index.md
@@ -0,0 +1,45 @@
+---
+title: influxd - InfluxDB service
+description: The `influxd` service starts and runs all the processes necessary for InfluxDB to function.
+influxdb/v2.2/tags: [influxd, cli]
+menu:
+  influxdb_2_2_ref:
+    name: influxd
+    parent: Command line tools
+weight: 102
+related:
+  - /influxdb/v2.2/reference/config-options/
+products: [oss]
+---
+
+The `influxd` daemon starts and runs all the processes necessary for InfluxDB to function.
+
+## Usage
+
+```
+influxd [flags]
+influxd [command]
+```
+
+{{% note %}}
+For information about other available InfluxDB configuration methods, see
+[InfluxDB configuration options](/influxdb/v2.2/reference/config-options/).
+{{% /note %}}
+
+## Commands
+
+| Command                                                            | Description                                                  |
+| :----------------------------------------------------------------- | :----------------------------------------------------------- |
+| [downgrade](/influxdb/v2.2/reference/cli/influxd/downgrade/)       | Downgrade metadata schema to match an older release          |
+| help                                                               | Output help information for `influxd`                        |
+| [inspect](/influxdb/v2.2/reference/cli/influxd/inspect/)           | Inspect on-disk database data                                |
+| [print-config](/influxdb/v2.2/reference/cli/influxd/print-config/) | (**Deprecated**) Print full influxd configuration for the current environment |
+| [recovery](/influxdb/v2.2/reference/cli/influxd/recovery/)         | Recover operator access to InfluxDB                          |
+| [run](/influxdb/v2.2/reference/cli/influxd/run/)                   | Start the influxd server _**(default)**_                     |
+| [upgrade](/influxdb/v2.2/reference/cli/influxd/upgrade/)           | Upgrade a 1.x version of InfluxDB to {{< current-version >}} |
+| [version](/influxdb/v2.2/reference/cli/influxd/version/)           | Output the current version of InfluxDB                       |
+
+## Flags
+
+<!-- Influxd flags are maintained in data/influxd_flags.yml -->
+{{< cli/influxd-flags >}}
diff --git a/content/influxdb/v2.2/reference/cli/influxd/downgrade.md b/content/influxdb/v2.2/reference/cli/influxd/downgrade.md
new file mode 100644
index 000000000..a0cc28b42
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influxd/downgrade.md
@@ -0,0 +1,48 @@
+---
+title: influxd downgrade
+description: >
+  The `influxd downgrade` command downgrades the metadata schema used by
+  `influxd` to match the schema of an older release.
+menu:
+  influxdb_2_2_ref:
+    parent: influxd
+weight: 201
+related:
+  - /influxdb/v2.2/upgrade/downgrade/
+---
+
+Use the `influxd downgrade` command to downgrade the metadata schema used by
+`influxd` to match the metadata schema of a older release.
+
+InfluxDB does not guarantee backwards-compatibility with earlier releases.
+Attempting to start an older `influxd` binary with a BoltDB or SQLite file that
+has been migrated to a newer schema will result in a startup error.
+This command downgrades metadata schemas to match the schemas of an older release
+and allows the older `influxd` binary to boot successfully.
+
+{{% note %}}
+Run this command **prior** to downgrading the `influxd` binary.
+{{% /note %}}
+
+## Usage
+
+```sh
+influxd downgrade [flags] <target-version>
+```
+
+## Flags
+
+| Flag |                 | Description                                                                      | Input type |
+| :--- | :-------------- | :------------------------------------------------------------------------------- | :--------: |
+|      | `--bolt-path`   | Path to BoltDB database (default is `~/.influxdbv2/influxd.bolt`)                |   string   |
+| `-h` | `--help`        | Help for `downgrade`                                                             |            |
+|      | `--log-level`   | Log level (`debug`, `info` _(default_), `warn` or  `error`)                      |   string   |
+|      | `--sqlite-path` | Path to SQLite database (default is `influxd.sqlite` in the bolt path directory) |   string   |
+
+
+## Examples
+
+##### Downgrade to InfluxDB 2.0
+```sh
+influxd downgrade 2.0
+```
\ No newline at end of file
diff --git a/content/influxdb/v2.2/reference/cli/influxd/inspect/_index.md b/content/influxdb/v2.2/reference/cli/influxd/inspect/_index.md
new file mode 100644
index 000000000..d244d0fbf
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influxd/inspect/_index.md
@@ -0,0 +1,38 @@
+---
+title: influxd inspect
+description: The `influxd inspect` commands and subcommands inspecting on-disk InfluxDB time series data.
+influxdb/v2.2/tags: [inspect]
+menu:
+  influxdb_2_2_ref:
+    parent: influxd
+weight: 201
+---
+
+The `influxd inspect` commands and subcommands inspecting on-disk InfluxDB time series data.
+
+## Usage
+```sh
+influxd inspect [subcommand]
+```
+
+## Subcommands
+| Subcommand                                                                           | Description                             |
+| :----------------------------------------------------------------------------------- | :-------------------------------------- |
+| [build-tsi](/influxdb/v2.2/reference/cli/influxd/inspect/build-tsi/)                 | Rebuild the TSI index and series file   |
+| [delete-tsm](/influxdb/v2.2/reference/cli/influxd/inspect/delete-tsm/)               | Delete a measurement from a TSM file   |
+| [dump-tsi](/influxdb/v2.2/reference/cli/influxd/inspect/dump-tsi/)                   | Output low level TSI information        |
+| [dump-tsm](/influxdb/v2.2/reference/cli/influxd/inspect/dump-tsm/)                   | Output low level TSM information        |
+| [dump-wal](/influxdb/v2.2/reference/cli/influxd/inspect/dump-wal/)                   | Output TSM data from WAL files          |
+| [export-index](/influxdb/v2.2/reference/cli/influxd/inspect/export-index/)           | Export TSI index data                   |
+| [export-lp](/influxdb/v2.2/reference/cli/influxd/inspect/export-lp/)                 | Export TSM data to line protocol        |
+| [report-tsi](/influxdb/v2.2/reference/cli/influxd/inspect/report-tsi/)               | Report the cardinality of TSI files     |
+| [report-tsm](/influxdb/v2.2/reference/cli/influxd/inspect/report-tsm/)               | Report information about TSM files      |
+| [verify-seriesfile](/influxdb/v2.2/reference/cli/influxd/inspect/verify-seriesfile/) | Verify the integrity of series files    |
+| [verify-tombstone](/influxdb/v2.2/reference/cli/influxd/inspect/verify-tombstone/)   | Verify the integrity of tombstone files |
+| [verify-tsm](/influxdb/v2.2/reference/cli/influxd/inspect/verify-tsm/)               | Verify the integrity of TSM files       |
+| [verify-wal](/influxdb/v2.2/reference/cli/influxd/inspect/verify-wal/)               | Verify the integrity of WAL files       |
+
+## Flags
+| Flag |          | Description                    |
+|:---- |:---      |:-----------                    |
+| `-h` | `--help` | Help for the `inspect` command |
diff --git a/content/influxdb/v2.2/reference/cli/influxd/inspect/build-tsi.md b/content/influxdb/v2.2/reference/cli/influxd/inspect/build-tsi.md
new file mode 100644
index 000000000..ecac87e3c
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influxd/inspect/build-tsi.md
@@ -0,0 +1,59 @@
+---
+title: influxd inspect build-tsi
+description: >
+  The `influxd inspect build-tsi` command rebuilds the TSI index and, if necessary,
+  the series file.
+influxdb/v2.2/tags: [tsi]
+menu:
+  influxdb_2_2_ref:
+    parent: influxd inspect
+weight: 301
+---
+
+The `influxd inspect build-tsi` command rebuilds the TSI index and, if necessary,
+the series file.
+
+## Usage
+```sh
+influxd inspect build-tsi [flags]
+```
+
+InfluxDB builds the index by reading all Time-Structured Merge tree (TSM) indexes
+and Write Ahead Log (WAL) entries in the TSM and WAL data directories.
+If the series file directory is missing, it rebuilds the series file.
+If the TSI index directory already exists, the command will fail.
+
+### Adjust performance
+Use the following options to adjust the performance of the indexing process:
+
+##### --max-log-file-size
+`--max-log-file-size` determines how much of an index to store in memory before
+compacting it into memory-mappable index files.
+If you find the memory requirements of your TSI index are too high, consider
+decreasing this setting.
+
+##### --max-cache-size
+`--max-cache-size` defines the maximum cache size.
+The indexing process replays WAL files into a `tsm1.Cache`.
+If the maximum cache size is too low, the indexing process will fail.
+Increase `--max-cache-size` to account for the size of your WAL files.
+
+##### --batch-size
+`--batch-size` defines the size of the batches written into the index.
+Altering the batch size can improve performance but may result in significantly
+higher memory usage.
+
+## Flags
+| Flag |                         | Description                                                                                     | Input Type |
+| :--- | :---------------------- | :---------------------------------------------------------------------------------------------- | :--------: |
+|      | `--batch-size`          | Size of the batches to write to the index. Defaults to `10000`. [See above](#--batch-size).     |  integer   |
+|      | `--bucket-id`           | Bucket ID (required if `--shard-id` is present).                                                |   string   |
+|      | `--compact-series-file` | Compact existing series file. Does not rebuilt index.                                           |            |
+|      | `--concurrency`         | Number of workers to dedicate to shard index building. Defaults to `GOMAXPROCS` (8 by default). |  integer   |
+|      | `--data-path`           | Path to the TSM data directory. Default is `~/.influxdbv2/engine/data`.                         |   string   |
+| `-h` | `--help`                | Help for the `build-tsi` command.                                                               |            |
+|      | `--max-cache-size`      | Maximum cache size. Defaults to `1073741824`. [See above](#--max-cache-size).                   |  uinteger  |
+|      | `--max-log-file-size`   | Maximum log file size. Defaults to `1048576`. [See above](#--max-log-file-size) .               |  integer   |
+|      | `--shard-id`            | Shard ID (requires a `--bucket-id`).                                                            |   string   |
+| `-v` | `--verbose`             | Enable verbose output.                                                                          |            |
+|      | `--wal-path`            | Path to the WAL data directory. Defaults to `~/.influxdbv2/engine/wal`.                         |   string   |
diff --git a/content/influxdb/v2.2/reference/cli/influxd/inspect/delete-tsm.md b/content/influxdb/v2.2/reference/cli/influxd/inspect/delete-tsm.md
new file mode 100644
index 000000000..caac80d69
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influxd/inspect/delete-tsm.md
@@ -0,0 +1,38 @@
+---
+title: influxd inspect delete-tsm
+description: >
+  The `influxd inspect delete-tsm` command deletes a measurement from a raw TSM file.
+influxdb/v2.2/tags: [tsm]
+menu:
+  influxdb_2_2_ref:
+    parent: influxd inspect
+weight: 301
+---
+
+The `influxd inspect delete-tsm` command deletes a measurement from a raw TSM file.
+
+## Usage
+```sh
+influxd inspect delete-tsm [flags]
+```
+
+## Flags
+| Flag |                 | Description                                           | Input Type |
+| :--- | :-------------- | :---------------------------------------------------- | :--------: |
+| `-h` | `--help`        | Help for `delete-tsm`                                 |            |
+|      | `--measurement` | Name of the measurement to delete                     |   string   |
+|      | `--sanitize`    | Remove all keys with non-printable unicode characters |            |
+| `-v` | `--verbose`     | Enable verbose logging                                |            |
+
+## Examples
+
+##### Delete a measurement from a TSM file
+```sh
+influxd inspect delete-tsm \
+  --measurement example-measurement
+```
+
+##### Remove non-printable unicode characters from all TSM files
+```sh
+influxd inspect delete-tsm --sanitize
+```
diff --git a/content/influxdb/v2.2/reference/cli/influxd/inspect/dump-tsi.md b/content/influxdb/v2.2/reference/cli/influxd/inspect/dump-tsi.md
new file mode 100644
index 000000000..735753626
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influxd/inspect/dump-tsi.md
@@ -0,0 +1,32 @@
+---
+title: influxd inspect dump-tsi
+description: >
+  The `influxd inspect dump-tsi` command outputs low-level information about `tsi1` files.
+influxdb/v2.2/tags: [tsi, inspect]
+menu:
+  influxdb_2_2_ref:
+    parent: influxd inspect
+weight: 301
+---
+
+The `influxd inspect dump-tsi` command outputs low-level information about
+Time Series Index (`tsi1`) files.
+
+## Usage
+```sh
+influxd inspect dump-tsi [flags]
+```
+
+## Flags
+| Flag |                        | Description                            | Input Type |
+| :--- | :--------------------- | :------------------------------------- | :--------: |
+| `-h` | `--help`               | Help for the `dump-tsi` command.       |            |
+|      | `--measurement-filter` | Regular expression measurement filter. |   string   |
+|      | `--measurements`       | Show raw measurement data.             |            |
+|      | `--series`             | Show raw series data.                  |            |
+|      | `--series-file`        | Path to series file.                   |   string   |
+|      | `--tag-key-filter`     | Regular expression tag key filter.     |   string   |
+|      | `--tag-keys`           | Show raw tag key data.                 |            |
+|      | `--tag-value-filter`   | Regular expression tag value filter.   |   string   |
+|      | `--tag-value-series`   | Show raw series data for each value.   |            |
+|      | `--tag-values`         | Show raw tag value data.               |            |
diff --git a/content/influxdb/v2.2/reference/cli/influxd/inspect/dump-tsm.md b/content/influxdb/v2.2/reference/cli/influxd/inspect/dump-tsm.md
new file mode 100644
index 000000000..975853600
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influxd/inspect/dump-tsm.md
@@ -0,0 +1,30 @@
+---
+title: influxd inspect dump-tsm
+description: >
+  The `influxd inspect dump-tsm` command outputs low-level information about `tsi1` files.
+influxdb/v2.2/tags: [tsm, inspect]
+menu:
+  influxdb_2_2_ref:
+    parent: influxd inspect
+weight: 301
+---
+
+The `influxd inspect dump-tsm` command outputs low-level information about
+Time Series Merge Tree (`tsm1`) files.
+
+## Usage
+```sh
+influxd inspect dump-tsm [flags]
+```
+
+## Flags
+| Flag |                | Description                                    | Input Type |
+| :--- | :------------- | :--------------------------------------------- | :--------: |
+|      | `--all`        | Output all TSM data {{< req " \*" >}}          |            |
+|      | `--blocks`     | Output raw block data.                         |            |
+|      | `--file-path`  | Path to TSM file.                              |   string   |
+|      | `--filter-key` | Only display data matching this key substring. |   string   |
+| `-h` | `--help`       | Help for `dump-tsm`.                           |            |
+|      | `--index`      | Dump raw index data.                           |            |
+
+_{{< req "\*" >}} Using the `--all` flag may print a significant amount of information._
diff --git a/content/influxdb/v2.2/reference/cli/influxd/inspect/dump-wal.md b/content/influxdb/v2.2/reference/cli/influxd/inspect/dump-wal.md
new file mode 100644
index 000000000..11c1ee7f7
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influxd/inspect/dump-wal.md
@@ -0,0 +1,43 @@
+---
+title: influxd inspect dump-wal
+description: >
+  The `influxd inspect dump-wal` command outputs data from WAL files for debugging purposes.
+influxdb/v2.2/tags: [wal, inspect]
+menu:
+  influxdb_2_2_ref:
+    parent: influxd inspect
+weight: 301
+---
+
+The `influxd inspect dump-wal` command outputs data from Write Ahead Log (WAL)
+files for debugging purposes.
+Given at least one WAL file path as an argument, the tool parses and prints
+out the entries in each file.
+
+## Usage
+```sh
+influxd inspect dump-wal [flags]
+```
+
+## Output details
+The `--find-duplicates` flag determines the `influxd inspect dump-wal` output.
+
+**Without `--find-duplicates`**, the command outputs the following for each file:
+
+- The file name
+- For each entry in a file:
+	  - The type of the entry (`[write]` or `[delete-bucket-range]`)
+	  - The formatted entry contents
+
+**With `--find-duplicates`**, the command outputs the following for each file):
+
+- The file name
+- A list of keys with timestamps in the wrong order
+
+
+
+## Flags
+| Flag |                     | Description                                                                |
+|:---- |:---                 |:-----------                                                                |
+|      | `--find-duplicates` | Ignore dumping entries; only report keys in the WAL that are out of order. |
+| `-h` | `--help`            | Help for the `dump-wal` command.                                            |
diff --git a/content/influxdb/v2.2/reference/cli/influxd/inspect/export-index.md b/content/influxdb/v2.2/reference/cli/influxd/inspect/export-index.md
new file mode 100644
index 000000000..fd8624c2f
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influxd/inspect/export-index.md
@@ -0,0 +1,26 @@
+---
+title: influxd inspect export-index
+description: >
+  The `influxd inspect export-index` command exports all series in a TSI index to
+  SQL format for inspection and debugging.
+influxdb/v2.2/tags: [inspect]
+menu:
+  influxdb_2_2_ref:
+    parent: influxd inspect
+weight: 301
+---
+
+The `influxd inspect export-index` command exports all series in a TSI index to
+SQL format for inspection and debugging.
+
+## Usage
+```sh
+influxd inspect export-index [flags]
+```
+
+## Flags
+| Flag |                | Description                                                             | Input type |
+|:---- |:---            |:-----------                                                             |:----------:|
+| `-h` | `--help`       | Help for the `export-index` command.                                    |            |
+|      |`--index-path`  | Path to the index directory. Defaults to `~/.influxdbv2/engine/index`). | string     |
+|      |`--series-path` | Path to series file. Defaults to `~/.influxdbv2/engine/_series`).       | string     |
diff --git a/content/influxdb/v2.2/reference/cli/influxd/inspect/export-lp.md b/content/influxdb/v2.2/reference/cli/influxd/inspect/export-lp.md
new file mode 100644
index 000000000..25bc535d6
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influxd/inspect/export-lp.md
@@ -0,0 +1,133 @@
+---
+title: influxd inspect export-lp
+description: >
+  The `influxd inspect export-lp` command exports all time series data in a bucket
+  as line protocol.
+influxdb/v2.2/tags: [inspect, export]
+menu:
+  influxdb_2_2_ref:
+    parent: influxd inspect
+weight: 301
+---
+
+The `influxd inspect export-lp` command exports all time-structured merge tree (TSM)
+data in a bucket to [line protocol](/influxdb/v2.2/reference/syntax/line-protocol/).
+
+## Usage
+```sh
+influxd inspect export-lp [flags]
+```
+
+## Flags
+| Flag |                 | Description                                             | Input type |
+|:---- |:---             |:-----------                                             |:----------:|
+|      | `--bucket-id`   | ({{< req >}}) Bucket ID                                 | string     |
+|      | `--compress`    | Compress output with GZIP                               |            |
+|      | `--end`         | End time to export (RFC3339 format)                     | string     |
+|      | `--engine-path` | ({{< req >}}) Path to persistent InfluxDB engine files  | string     |
+| `-h` | `--help`        | Help for the `export-lp` command.                       |            |
+|      | `--log-level`   | Log-level (`debug`, `info` _(default)_, or `error`)     | string     |
+|      | `--measurement` | Measurement name(s) to export                           | strings    |
+|      | `--output-path` | ({{< req >}}) Output path (file path or stdout _(`-`)_) | string     |
+|      | `--start`       | Start time to export (RFC3339 format)                   | string     |
+
+## Examples
+
+- [Export all data in a bucket as line protocol](#export-all-data-in-a-bucket-as-line-protocol)
+- [Export data in measurements as line protocol](#export-data-in-measurements-as-line-protocol)
+- [Export data in specified time range as line protocol](#export-data-in-specified-time-range-as-line-protocol)
+
+##### Export all data in a bucket as line protocol
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[To a file](#)
+[To stdout](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```sh
+influxd inspect export-lp \
+  --bucket-id 12ab34cd56ef \
+  --engine-path ~/.influxdbv2/engine \
+  --output-path path/to/export.lp
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```sh
+influxd inspect export-lp \
+  --bucket-id 12ab34cd56ef \
+  --engine-path ~/.influxdbv2/engine \
+  --output-path -
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+##### Export data in measurements as line protocol
+
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[To a file](#)
+[To stdout](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```sh
+# Export a single measurement
+influxd inspect export-lp \
+  --bucket-id 12ab34cd56ef \
+  --engine-path ~/.influxdbv2/engine \
+  --measurement example-measurement \
+  --output-path path/to/export.lp
+
+# Export multiple measurements
+influxd inspect export-lp \
+  --bucket-id 12ab34cd56ef \
+  --engine-path ~/.influxdbv2/engine \
+  --measurement example-measurement-1 example-measurement-2 \
+  --output-path path/to/export.lp
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```sh
+# Export a single measurement
+influxd inspect export-lp \
+  --bucket-id 12ab34cd56ef \
+  --engine-path ~/.influxdbv2/engine \
+  --measurement example-measurement \
+  --output-path -
+
+# Export multiple measurements
+influxd inspect export-lp \
+  --bucket-id 12ab34cd56ef \
+  --engine-path ~/.influxdbv2/engine \
+  --measurement example-measurement-1 example-measurement-2 \
+  --output-path -
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+##### Export data in specified time range as line protocol
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[To a file](#)
+[To stdout](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```sh
+influxd inspect export-lp \
+  --bucket-id 12ab34cd56ef \
+  --engine-path ~/.influxdbv2/engine \
+  --start 2021-01-01T00:00:00Z \
+  --end 2021-01-31T23:59:59Z \
+  --output-path path/to/export.lp
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```sh
+influxd inspect export-lp \
+  --bucket-id 12ab34cd56ef \
+  --engine-path ~/.influxdbv2/engine \
+  --start 2021-01-01T00:00:00Z \
+  --end 2021-01-31T23:59:59Z \
+  --output-path -
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
diff --git a/content/influxdb/v2.2/reference/cli/influxd/inspect/report-tsi.md b/content/influxdb/v2.2/reference/cli/influxd/inspect/report-tsi.md
new file mode 100644
index 000000000..05283b867
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influxd/inspect/report-tsi.md
@@ -0,0 +1,29 @@
+---
+title: influxd inspect report-tsi
+description: >
+  The `influxd inspect report-tsi` command analyzes Time Series Index (TSI) files
+  in a storage directory and reports the cardinality of data stored in the files.
+influxdb/v2.2/tags: [tsi, cardinality, inspect]
+menu:
+  influxdb_2_2_ref:
+    parent: influxd inspect
+weight: 301
+---
+
+The `influxd inspect report-tsi` command analyzes Time Series Index (TSI) within
+a specified bucket and reports the cardinality of data stored in the bucket
+segmented by shard and measurement.
+
+## Usage
+```sh
+influxd inspect report-tsi [flags]
+```
+
+## Flags
+| Flag  |                  | Description                                                                                  | Input Type |
+| :---- | :--------------- | :------------------------------------------------------------------------------------------- | :--------: |
+| `-b`  | `--bucket-id`    | ({{< req >}}) Process data for specified bucket ID.                                          |   string   |
+| `-c ` | `--concurrency`  | Number of workers to run concurrently (default is the number of available processing units). |  integer   |
+|       | `--data-path`    | Path to data directory (default `~/.influxdbv2/engine/data`).                                |   string   |
+| `-h`  | `--help`         | View Help for the `report-tsi` command.                                                      |            |
+| `-t`  | `-top`           | Limit results to the top n.                                                                  |  integer   |
diff --git a/content/influxdb/v2.2/reference/cli/influxd/inspect/report-tsm.md b/content/influxdb/v2.2/reference/cli/influxd/inspect/report-tsm.md
new file mode 100644
index 000000000..98ba76de0
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influxd/inspect/report-tsm.md
@@ -0,0 +1,55 @@
+---
+title: influxd inspect report-tsm
+description: >
+  The `influxd inspect report-tsm` command analyzes Time-Structured Merge Tree (TSM)
+  files within a storage engine directory and reports the cardinality within the files
+  and the time range the data covers.
+influxdb/v2.2/tags: [tsm, cardinality, inspect]
+menu:
+  influxdb_2_2_ref:
+    parent: influxd inspect
+weight: 301
+---
+
+The `influxd inspect report-tsm` command analyzes Time-Structured Merge Tree (TSM)
+files within a storage engine directory and reports the cardinality within the files
+and the time range the data covers.
+
+This command only reports on the index within each TSM file.
+It does not read any block data.
+To reduce heap requirements, by default `report-tsm` estimates the overall
+cardinality in the file set by using the HLL++ algorithm.
+Determine exact cardinalities by using the `--exact` flag.
+
+## Usage
+```sh
+influxd inspect report-tsm [flags]
+```
+
+## Output details
+`influxd inspect report-tsm` outputs the following for each TSM file:
+
+- The full file name.
+- The series cardinality within the file.
+- The number of series first encountered within the file.
+- The minimum and maximum timestamp associated with TSM data in the file.
+- The time to load the TSM index and apply any tombstones.
+
+The summary section then outputs the total time range and series cardinality for
+the file set. Depending on the `--detailed` flag, series cardinality is segmented
+in the following ways:
+
+- Series cardinality for each organization.
+- Series cardinality for each bucket.
+- Series cardinality for each measurement.
+- Number of field keys for each measurement.
+- Number of tag values for each tag key.
+
+## Flags
+| Flag |               | Description                                                                                      | Input Type |
+| :--- | :------------ | :----------------------------------------------------------------------------------------------- | :--------: |
+|      | `--data-path` | Path to data directory (defaults to `~/.influxdbv2/engine/data`).                                |   string   |
+|      | `--detailed`  | Emit series cardinality segmented by measurements, tag keys, and fields. _**May take a while**_. |            |
+|      | `--exact`     | Calculate an exact cardinality count. _**May use significant memory**_.                          |            |
+| `-h` | `--help`      | Help for the `report-tsm` command.                                                               |            |
+|      | `--pattern`   | Only process TSM files containing pattern.                                                       |   string   |
diff --git a/content/influxdb/v2.2/reference/cli/influxd/inspect/verify-seriesfile.md b/content/influxdb/v2.2/reference/cli/influxd/inspect/verify-seriesfile.md
new file mode 100644
index 000000000..d12cbe58c
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influxd/inspect/verify-seriesfile.md
@@ -0,0 +1,27 @@
+---
+title: influxd inspect verify-seriesfile
+description: >
+  The `influxd inspect verify-seriesfile` command verifies the integrity of series files.
+influxdb/v2.2/tags: [inspect]
+menu:
+  influxdb_2_2_ref:
+    parent: influxd inspect
+weight: 301
+---
+
+The `influxd inspect verify-seriesfile` command verifies the integrity of series files.
+
+## Usage
+```sh
+influxd inspect verify-seriesfile [flags]
+```
+
+## Flags
+| Flag |                 | Description                                                                                   | Input Type |
+| :--- | :-------------- | :-------------------------------------------------------------------------------------------- | :--------: |
+|      | `--bucket-id`   | Verify series files from a specific bucket.                                              |   string   |
+| `-c` | `--concurrency` | Number of workers to run concurrently (defaults to the number of available processing units). |  integer   |
+|      | `--data-path`   | Path to data directory (defaults to `~/.influxdbv2/engine/data`).                             |   string   |
+| `-h` | `--help`        | Help for the `verify-seriesfile` command.                                                     |            |
+|      | `--series-path` | Path to series file (overrides `--data-path` and `--bucket-id`).                              |   string   |
+| `-v` | `--verbose`     | Enable verbose output.                                                                        |            |
diff --git a/content/influxdb/v2.2/reference/cli/influxd/inspect/verify-tombstone.md b/content/influxdb/v2.2/reference/cli/influxd/inspect/verify-tombstone.md
new file mode 100644
index 000000000..59d709d84
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influxd/inspect/verify-tombstone.md
@@ -0,0 +1,25 @@
+---
+title: influxd inspect verify-tombstone
+description: >
+  The `influxd inspect verify-tombstone` command verifies the integrity of tombstone files.
+influxdb/v2.2/tags: [inspect]
+menu:
+  influxdb_2_2_ref:
+    parent: influxd inspect
+weight: 301
+---
+
+The `influxd inspect verify-tombstone` command verifies the integrity of tombstone files.
+
+## Usage
+```sh
+influxd inspect verify-tombstone [flags]
+```
+
+## Flags
+| Flag |                 | Description                                                          | Input Type |
+| :--- | :-------------- | :------------------------------------------------------------------- | :--------: |
+|      | `--engine-path` | Path to find tombstone files (defaults to `~/.influxdbv2/engine`).   |   string   |
+| `-h` | `--help`        | Help for `verify-tombstone`.                                         |            |
+| `-v` | `--verbose`     | Verbose output (emit periodic progress).                             |            |
+|      | `--vv`          | Very verbose output (emit every tombstone entry key and time range). |            |
diff --git a/content/influxdb/v2.2/reference/cli/influxd/inspect/verify-tsm.md b/content/influxdb/v2.2/reference/cli/influxd/inspect/verify-tsm.md
new file mode 100644
index 000000000..73dabedee
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influxd/inspect/verify-tsm.md
@@ -0,0 +1,26 @@
+---
+title: influxd inspect verify-tsm
+description: >
+  The `influxd inspect verify-tsm` command analyzes a set of TSM files for inconsistencies
+  between the TSM index and the blocks.
+influxdb/v2.2/tags: [tsm, inspect]
+menu:
+  influxdb_2_2_ref:
+    parent: influxd inspect
+weight: 301
+---
+
+The `influxd inspect verify-tsm` command verifies the integrity of TSM files.
+
+## Usage
+```sh
+influxd inspect verify-tsm [flags]
+```
+
+## Flags
+| Flag |                 | Description                                                             | Input Type |
+| :--- | :-------------- | :---------------------------------------------------------------------- | :--------: |
+|      | `--check-utf8`  | Verify series keys are valid UTF-8 (skips block checksum verification). |            |
+|      | `--engine-path` | Storage engine directory path (default is `~/.influxdbv2/engine`).      |   string   |
+| `-h` | `--help`        | Help for `verify-tsm`.                                                  |            |
+| `-v` | `--verbose`     | Enable verbose logging.                                                 |            |
diff --git a/content/influxdb/v2.2/reference/cli/influxd/inspect/verify-wal.md b/content/influxdb/v2.2/reference/cli/influxd/inspect/verify-wal.md
new file mode 100644
index 000000000..2d32ad384
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influxd/inspect/verify-wal.md
@@ -0,0 +1,40 @@
+---
+title: influxd inspect verify-wal
+description: >
+  The `influxd inspect verify-wal` command analyzes the Write-Ahead Log (WAL)
+  to check if there are any corrupt files.
+influxdb/v2.2/tags: [wal, inspect]
+menu:
+  influxdb_2_2_ref:
+    parent: influxd inspect
+weight: 301
+---
+
+The `influxd inspect verify-wal` command analyzes the Write-Ahead Log (WAL)
+to check if there are any corrupt files.
+If it finds corrupt files, the command returns the names of those files.
+It also returns the total number of entries in each scanned WAL file.
+
+## Usage
+```sh
+influxd inspect verify-wal [flags]
+```
+
+## Output details
+`influxd inspect verify-wal` outputs the following for each file:
+
+- The file name.
+- The first position of any identified corruption or "clean" if no corruption is found.
+
+After the verification is complete, it returns a summary with:
+
+- The number of WAL files scanned.
+- The number of WAL entries scanned.
+- A list of files found to be corrupt.
+
+## Flags
+| Flag |              | Description                                                   | Input Type |
+| :--- | :----------- | :------------------------------------------------------------ | :--------: |
+| `-h` | `--help`     | Help for the `verify-wal` command.                            |            |
+| `-v` | `--verbose`  | Enable verbose logging.                                       |            |
+|      | `--wal-path` | Path to WAL directory (default is `~/.influxdbv2/engine/wal`) |   string   |
diff --git a/content/influxdb/v2.2/reference/cli/influxd/print-config.md b/content/influxdb/v2.2/reference/cli/influxd/print-config.md
new file mode 100644
index 000000000..e1e61bd4d
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influxd/print-config.md
@@ -0,0 +1,93 @@
+---
+title: influxd print-config
+description: >
+  The `influxd print-config` command prints a full InfluxDB configuration resolved
+  from the current `influxd` environment.
+influxdb/v2.2/tags: [influxd, cli]
+menu:
+  influxdb_2_2_ref:
+    parent: influxd
+weight: 201
+related:
+  - /influxdb/v2.2/reference/config-options/
+  - /influxdb/v2.2/reference/cli/influx/server-config/
+---
+
+The `influxd print-config` command prints a full InfluxDB configuration resolved
+from the current `influxd` environment.
+The command formats output as YAML.
+
+{{% warn %}}
+
+#### Use influx CLI server-config
+
+`influxd print-config` is deprecated in InfluxDB v2.2.
+
+To display the runtime server configuration, use the [`influx server-config` command](/influxdb/v2.2/reference/cli/influx/server-config/)
+or the [`/api/v2/config`](/influxdb/v2.2/api/#operation/GetConfig) InfluxDB API endpoint.
+For more information, see [how to view your server configuration](/influxdb/v2.2/reference/config-options/#view-your-runtime-server-configuration).
+{{% /warn %}}
+
+`influxd print-config` does not output the configuration of the running server. Rather, it evaluates the current environment, config file, and _flags passed to the `influxd print-config` command_. It is unaware of configuration options passed to the `influxd` command at runtime.
+
+For example, with the following configuration value:
+```sh
+# Configuration file
+...
+log-level: info
+...
+```
+
+and `--log-level` provided at startup:
+
+```
+influxd --log-level warn
+```
+
+`influxd print-config` displays
+
+```sh
+...
+log-level: info
+...
+```
+
+`influxd print-config log-level warn` displays
+
+```sh
+...
+log-level: warn
+...
+```
+
+## Usage
+
+```
+influxd print-config [flags]
+```
+
+
+{{% note %}}
+For information about available InfluxDB configuration methods, see
+[InfluxDB configuration options](/influxdb/v2.2/reference/config-options/).
+{{% /note %}}
+
+## Flags
+
+| Flag |              | Description                                     | Input type |
+|:---- | ---          |:-----------                                     |:----------:|
+| `-h` | `--help`     | Help for `print-config`                         |            |
+|      | `--key-name` | Print the value of a specific configuration key | string     |
+
+
+## Examples
+
+##### Print full influxd configuration
+```sh
+influxd print-config
+```
+
+##### Print the value of a specific influxd configuration setting
+```sh
+influxd print-config --key-name=http-bind-address
+```
diff --git a/content/influxdb/v2.2/reference/cli/influxd/recovery/_index.md b/content/influxdb/v2.2/reference/cli/influxd/recovery/_index.md
new file mode 100644
index 000000000..60203f1cd
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influxd/recovery/_index.md
@@ -0,0 +1,33 @@
+---
+title: influxd recovery
+description: >
+  The `influxd recovery` command and subcommands provide tools for recovering
+  operator access to InfluxDB by directly modifying authorization, organization,
+  and user data stored on disk.
+menu:
+  influxdb_2_2_ref:
+    parent: influxd
+weight: 201
+---
+
+The `influxd recovery` command and subcommands provide tools for recovering
+operator access to InfluxDB by directly modifying authorization, organization,
+and user data stored on disk.
+
+## Usage
+```sh
+influxd recovery [flags]
+influxd recovery [command]
+```
+
+## Subcommands
+| Subcommand                                                  | Description                                    |
+| :---------------------------------------------------------- | :--------------------------------------------- |
+| [auth](/influxdb/v2.2/reference/cli/influxd/recovery/auth/) | Manage on-disk authorization data for recovery |
+| [org](/influxdb/v2.2/reference/cli/influxd/recovery/org/)   | Manage on-disk organization data for recovery  |
+| [user](/influxdb/v2.2/reference/cli/influxd/recovery/user/) | Manage on-disk user data for recovery          |
+
+## Flags
+| Flag |          | Description         |
+| :--- | :------- | :------------------ |
+| `-h` | `--help` | Help for `recovery` |
\ No newline at end of file
diff --git a/content/influxdb/v2.2/reference/cli/influxd/recovery/auth/_index.md b/content/influxdb/v2.2/reference/cli/influxd/recovery/auth/_index.md
new file mode 100644
index 000000000..22c44d9d9
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influxd/recovery/auth/_index.md
@@ -0,0 +1,30 @@
+---
+title: influxd recovery auth
+description: >
+  The `influxd recovery auth` command and subcommands manage on-disk authorization 
+  data for recovery purposes.
+menu:
+  influxdb_2_2_ref:
+    parent: influxd recovery
+weight: 301
+---
+
+The `influxd recovery auth` command and subcommands manage on-disk authorization 
+data for recovery purposes.
+
+## Usage
+```sh
+influxd recovery auth [flags]
+influxd recovery auth [command]
+```
+
+## Subcommands
+| Subcommand                                                                             | Description                          |
+| :------------------------------------------------------------------------------------- | :----------------------------------- |
+| [create-operator](/influxdb/v2.2/reference/cli/influxd/recovery/auth/create-operator/) | Create new operator token for a user |
+| [list](/influxdb/v2.2/reference/cli/influxd/recovery/auth/list/)                       | List authorizations                  |
+
+## Flags
+| Flag  |          | Description     |
+| :---- | :------- | :-------------- |
+| `-h ` | `--help` | Help for `auth` |
\ No newline at end of file
diff --git a/content/influxdb/v2.2/reference/cli/influxd/recovery/auth/create-operator.md b/content/influxdb/v2.2/reference/cli/influxd/recovery/auth/create-operator.md
new file mode 100644
index 000000000..510b6fff9
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influxd/recovery/auth/create-operator.md
@@ -0,0 +1,41 @@
+---
+title: influxd recovery auth create-operator
+description: >
+  The `influxd recovery auth create-operator` command creates new
+  [Operator token](/influxdb/v2.2/security/tokens/#operator-token) directly on disk
+  for a specified user.
+menu:
+  influxdb_2_2_ref:
+    parent: influxd recovery auth
+weight: 401
+---
+
+The `influxd recovery auth create-operator` command creates a new
+[Operator token](/influxdb/v2.2/security/tokens/#operator-token) directly on disk
+for a specified user.
+
+{{% note %}}
+This command can only be executed when the InfluxDB server (`influxd`) is not running.
+{{% /note %}}
+
+## Usage
+```sh
+influxd recovery auth create-operator [flags]
+```
+
+## Flags
+| Flag |               | Description                                                    | Input Type |
+| :--- | :------------ | :------------------------------------------------------------- | :--------: |
+|      | `--bolt-path` | Path to the BoltDB file (default `~/.influxdbv2/influxd.bolt`) |   string   |
+| `-h` | `--help`      | Help for `create-operator`                                     |            |
+|      | `--org`       | ({{< req >}}) Organization name                                |   string   |
+|      | `--username`  | ({{< req >}}) Username to assign the operator token to         |   string   |
+
+## Examples
+
+##### Generate a new operator token
+```sh
+influxd \
+  --org example-org \
+  --username example-user
+```
\ No newline at end of file
diff --git a/content/influxdb/v2.2/reference/cli/influxd/recovery/auth/list.md b/content/influxdb/v2.2/reference/cli/influxd/recovery/auth/list.md
new file mode 100644
index 000000000..9c5d64b1c
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influxd/recovery/auth/list.md
@@ -0,0 +1,28 @@
+---
+title: influxd recovery auth list
+description: >
+  The `influxd recovery auth list` command lists authorizations and data 
+  associated with each authorization stored on disk.
+menu:
+  influxdb_2_2_ref:
+    parent: influxd recovery auth
+weight: 401
+---
+
+The `influxd recovery org list` command lists authorizations stored on disk and 
+outputs data associated with each authorization.
+
+{{% note %}}
+This command can only be executed when the InfluxDB server (`influxd`) is not running.
+{{% /note %}}
+
+## Usage
+```sh
+influxd recovery auth list [flags]
+```
+
+## Flags
+| Flag |               | Description                                                    | Input Type |
+| :--- | :------------ | :------------------------------------------------------------- | :--------: |
+|      | `--bolt-path` | Path to the BoltDB file (default `~/.influxdbv2/influxd.bolt`) |   string   |
+| `-h` | `--help`      | Help for `list`                                                |            |
\ No newline at end of file
diff --git a/content/influxdb/v2.2/reference/cli/influxd/recovery/org/_index.md b/content/influxdb/v2.2/reference/cli/influxd/recovery/org/_index.md
new file mode 100644
index 000000000..002f8be7e
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influxd/recovery/org/_index.md
@@ -0,0 +1,30 @@
+---
+title: influxd recovery org
+description: >
+  The `influxd recovery org` command and subcommands manage on-disk organization 
+  data for recovery purposes.
+menu:
+  influxdb_2_2_ref:
+    parent: influxd recovery
+weight: 301
+---
+
+The `influxd recovery org` command and subcommands manage on-disk organization 
+data for recovery purposes.
+
+## Usage
+```sh
+influxd recovery org [flags]
+influxd recovery org [command]
+```
+
+## Subcommands
+| Subcommand                                                          | Description        |
+| :------------------------------------------------------------------ | :----------------- |
+| [create](/influxdb/v2.2/reference/cli/influxd/recovery/org/create/) | Create new org     |
+| [list](/influxdb/v2.2/reference/cli/influxd/recovery/org/list/)     | List organizations |
+
+## Flags
+| Flag |          | Description    |
+| :--- | :------- | :------------- |
+| `-h` | `--help` | Help for `org` |
\ No newline at end of file
diff --git a/content/influxdb/v2.2/reference/cli/influxd/recovery/org/create.md b/content/influxdb/v2.2/reference/cli/influxd/recovery/org/create.md
new file mode 100644
index 000000000..4ac32e2d5
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influxd/recovery/org/create.md
@@ -0,0 +1,36 @@
+---
+title: influxd recovery org create
+description: >
+  The `influxd recovery org create` command creates a new organization directly
+  on disk for recovery purposes.
+menu:
+  influxdb_2_2_ref:
+    parent: influxd recovery org
+weight: 401
+---
+
+The `influxd recovery org create` command creates a new organization directly
+on disk for recovery purposes.
+
+{{% note %}}
+This command can only be executed when the InfluxDB server (`influxd`) is not running.
+{{% /note %}}
+
+## Usage
+```sh
+influxd recovery org create [flags]
+```
+
+## Flags
+| Flag |               | Description                                                    | Input Type |
+| :--- | :------------ | :------------------------------------------------------------- | :--------: |
+|      | `--bolt-path` | Path to the BoltDB file (default `~/.influxdbv2/influxd.bolt`) |   string   |
+| `-h` | `--help`      | Help for `create`                                              |            |
+|      | `--org`       | Organization name                                              |   string   |
+
+## Examples
+
+##### Create a new organization directly on disk
+```sh
+influxd recovery org create --org example-org
+```
\ No newline at end of file
diff --git a/content/influxdb/v2.2/reference/cli/influxd/recovery/org/list.md b/content/influxdb/v2.2/reference/cli/influxd/recovery/org/list.md
new file mode 100644
index 000000000..ad752f0ca
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influxd/recovery/org/list.md
@@ -0,0 +1,28 @@
+---
+title: influxd recovery org list
+description: >
+  The `influxd recovery org list` command lists organizations stored on disk and 
+  outputs data associated with each organization.
+menu:
+  influxdb_2_2_ref:
+    parent: influxd recovery org
+weight: 401
+---
+
+The `influxd recovery org list` command lists organizations stored on disk and 
+outputs data associated with each organization.
+
+{{% note %}}
+This command can only be executed when the InfluxDB server (`influxd`) is not running.
+{{% /note %}}
+
+## Usage
+```sh
+influxd recovery org list [flags]
+```
+
+## Flags
+| Flag |               | Description                                                    | Input Type |
+| :--- | :------------ | :------------------------------------------------------------- | :--------: |
+|      | `--bolt-path` | Path to the BoltDB file (default `~/.influxdbv2/influxd.bolt`) |   string   |
+| `-h` | `--help`      | Help for `list`                                                |            |
\ No newline at end of file
diff --git a/content/influxdb/v2.2/reference/cli/influxd/recovery/user/_index.md b/content/influxdb/v2.2/reference/cli/influxd/recovery/user/_index.md
new file mode 100644
index 000000000..6fde51eed
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influxd/recovery/user/_index.md
@@ -0,0 +1,32 @@
+---
+title: influxd recovery user
+description: >
+  The `influxd recovery user` command and subcommands manage on-disk user 
+  data for recovery purposes.
+menu:
+menu:
+  influxdb_2_2_ref:
+    parent: influxd recovery
+weight: 301
+---
+
+The `influxd recovery user` command and subcommands manage on-disk user 
+data for recovery purposes.
+
+## Usage
+```sh
+influxd recovery user [flags]
+influxd recovery user [command]
+```
+
+## Subcommands
+| Subcommand                                                           | Description       |
+| :------------------------------------------------------------------- | :---------------- |
+| [create](/influxdb/v2.2/reference/cli/influxd/recovery/user/create/) | Create new user   |
+| [list](/influxdb/v2.2/reference/cli/influxd/recovery/user/list/)     | List users        |
+| [update](/influxdb/v2.2/reference/cli/influxd/recovery/user/list/)   | Update a password |
+
+## Flags
+| Flag |          | Description     |
+| :--- | :------- | :-------------- |
+| `-h` | `--help` | Help for `user` |
\ No newline at end of file
diff --git a/content/influxdb/v2.2/reference/cli/influxd/recovery/user/create.md b/content/influxdb/v2.2/reference/cli/influxd/recovery/user/create.md
new file mode 100644
index 000000000..69c1b265e
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influxd/recovery/user/create.md
@@ -0,0 +1,39 @@
+---
+title: influxd recovery user create
+description: >
+  The `influxd recovery user create` command creates a new user directly
+  on disk for recovery purposes.
+menu:
+  influxdb_2_2_ref:
+    parent: influxd recovery user
+weight: 401
+---
+
+The `influxd recovery user create` command creates a new user directly
+on disk for recovery purposes.
+
+{{% note %}}
+This command can only be executed when the InfluxDB server (`influxd`) is not running.
+{{% /note %}}
+
+## Usage
+```sh
+influxd recovery user create [flags]
+```
+
+## Flags
+| Flag |               | Description                                                   | Input Type |
+| :--- | :------------ | :------------------------------------------------------------ | :--------: |
+|      | `--bolt-path` | Path to the BoltDB file (default `~.influxdbv2/influxd.bolt`) |   string   |
+| `-h` | `--help`      | Help for `create`                                             |            |
+|      | `--password`  | Password for the new user                                     |   string   |
+|      | `--username`  | Username of the new user                                      |   string   |
+
+## Examples
+
+##### Create a new user directly on disk
+```sh
+influxd recovery user create \
+  --username example-username \
+  --password ExAmPL3-paS5W0rD
+```
\ No newline at end of file
diff --git a/content/influxdb/v2.2/reference/cli/influxd/recovery/user/list.md b/content/influxdb/v2.2/reference/cli/influxd/recovery/user/list.md
new file mode 100644
index 000000000..1333d856c
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influxd/recovery/user/list.md
@@ -0,0 +1,28 @@
+---
+title: influxd recovery user list
+description: >
+  The `influxd recovery user list` command lists users stored on disk and 
+  outputs data associated with each user.
+menu:
+  influxdb_2_2_ref:
+    parent: influxd recovery user
+weight: 401
+---
+
+The `influxd recovery user list` command lists users stored on disk and 
+outputs data associated with each user.
+
+{{% note %}}
+This command can only be executed when the InfluxDB server (`influxd`) is not running.
+{{% /note %}}
+
+## Usage
+```sh
+influxd recovery user list [flags]
+```
+
+## Flags
+| Flag |               | Description                                                   | Input Type |
+| :--- | :------------ | :------------------------------------------------------------ | :--------: |
+|      | `--bolt-path` | Path to the BoltDB file (default `~.influxdbv2/influxd.bolt`) |   string   |
+| `-h` | `--help`      | Help for `list`                                               |            |
\ No newline at end of file
diff --git a/content/influxdb/v2.2/reference/cli/influxd/recovery/user/update.md b/content/influxdb/v2.2/reference/cli/influxd/recovery/user/update.md
new file mode 100644
index 000000000..d38af9b21
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influxd/recovery/user/update.md
@@ -0,0 +1,38 @@
+---
+title: influxd recovery user update
+description: >
+  The `influxd recovery user update` command lets you change your password if you forget your credentials.
+menu:
+  influxdb_2_2_ref:
+    parent: influxd recovery user
+weight: 401
+---
+
+Use `influxd recovery user update` to update a password. Useful when you forget your username and need to update your credentials. To retrieve all usernames in the system, use [`influxd recovery user list`](/influxdb/v2.2/reference/cli/influxd/recovery/user/list/) or use [`influxd recovery user create`](/influxdb/v2.2/reference/cli/influxd/recovery/user/create/) to create new user for recovery purposes.
+
+{{% note %}}
+This command can only be executed when the InfluxDB server (`influxd`) is not running.
+{{% /note %}}
+
+## Usage
+```sh
+influxd recovery user update [flags]
+```
+
+## Flags
+| Flag |                      | Description                                                   | Input Type |
+| :--- | :------------------- | :------------------------------------------------------------ | :--------: |
+|      | `--bolt-path`        | Path to the BoltDB file (default `~.influxdbv2/influxd.bolt`) |   string   |
+| `-h` | `--help`             | Help for `update`                                             |            |
+|      | `--id` or `username` | Enter the ID or name for an existing user                     |   string   |
+|      | `--password`         | New password for the specified user                           |   string   |
+
+## Examples
+
+##### Update a user password
+
+```sh
+influxd recovery user update \
+  --username example-username \
+  --password ExAmPL3-paS5W0rD
+```
\ No newline at end of file
diff --git a/content/influxdb/v2.2/reference/cli/influxd/run.md b/content/influxdb/v2.2/reference/cli/influxd/run.md
new file mode 100644
index 000000000..d33ee062c
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influxd/run.md
@@ -0,0 +1,40 @@
+---
+title: influxd run
+description: The `influxd run` command is the default `influxd` command and starts the influxd server.
+influxdb/v2.2/tags: [influxd, cli]
+menu:
+  influxdb_2_2_ref:
+    parent: influxd
+weight: 201
+related:
+  - /influxdb/v2.2/reference/config-options/
+products: [oss]
+---
+
+The `influxd run` command is the default command for `influxd`.
+It starts and runs all the processes necessary for InfluxDB to function.
+
+## Usage
+
+```
+influxd run [flags]
+```
+
+
+{{% note %}}
+Because `run` is the default command for `influxd`, the following commands are the same:
+
+```bash
+influxd
+influxd run
+```
+{{% /note %}}
+
+{{% note %}}
+For information about other available InfluxDB configuration methods, see
+[InfluxDB configuration options](/influxdb/v2.2/reference/config-options/).
+{{% /note %}}
+
+## Flags
+
+{{% cli/influxd-flags %}}
diff --git a/content/influxdb/v2.2/reference/cli/influxd/upgrade.md b/content/influxdb/v2.2/reference/cli/influxd/upgrade.md
new file mode 100644
index 000000000..52420f9e3
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influxd/upgrade.md
@@ -0,0 +1,59 @@
+---
+title: influxd upgrade
+description: The `influxd upgrade` command upgrades a InfluxdDB 1.x instance to 2.x.
+menu:
+  influxdb_2_2_ref:
+    parent: influxd
+weight: 201
+products: [oss]
+---
+
+Use the `influxd upgrade` command to upgrade an instance of InfluxDB 1.x to InfluxDB {{< current-version >}}.
+This command copies all data in [databases](/influxdb/v1.8/concepts/glossary/#database) and
+[retention policies](/influxdb/v1.8/concepts/glossary/#retention-policy-rp) (used in 1.x)
+over to [buckets](/influxdb/v2.2/reference/glossary/#bucket) (used in {{< current-version >}}).
+
+{{% warn %}}
+Be sure to back up all data before upgrading with `influx upgrade`.
+{{% /warn %}}
+
+This command performs the following actions:
+
+1. Creates the InfluxDB 2.x configuration file using 1.x configuration file options.
+   Unsupported 1.x options are reported to standard output.
+   If the configuration file is not available, the 1.x database folder can be passed via th `--v1-dir` flag.
+2. Copies and upgrades 1.x database files.
+
+The target 2.x database directory is specified by the `--engine-path` option.
+If changed, the bolt path can be specified by the `--bolt-path` option.
+
+## Usage
+
+```
+influxd upgrade [flags]
+influxd upgrade [command]
+```
+
+## Flags
+
+| Flag |                                  | Description                                                                                                | Input type |
+|:-----|:------------------------         |:-----------------------------------------------------------------------------------------------------------|:----------:|
+| `-m` | `--bolt-path`                    | Path for boltdb database (default `~/.influxdbv2/influxd.bolt`)                                            | string     |
+| `-b` | `--bucket`                       | Primary bucket name                                                                                        | string     |
+|      | `--config-file`                  | Custom InfluxDB 1.x config file path (default `~/.influxdb/influxdb.conf`)                                 | string     |
+|      | `--continuous-query-export-path` | Path for exported 1.x continuous queries (default `~/continuous_queries.txt`)                              | string     |
+| `-e` | `--engine-path`                  | Path for persistent engine files (default `~/.influxdbv2/engine`)                                          | string     |
+| `-f` | `--force`                        | Skip the confirmation prompt                                                                               |            |
+| `-h` | `--help`                         | Help for `influxd upgrade`                                                                                 |            |
+| `-c` | `--influx-configs-path`          | Path for 2.x `influx` CLI configurations file (default `~/.influxdbv2/configs`)                            |            |
+|      | `--log-level`                    | Supported log levels are `debug`, `info`, `warn`, and `error` (default `info`)                             | string     |
+|      | `--log-path`                     | Custom log file path (default `~/upgrade.log`)                                                             | string     |
+| `-o` | `--org`                          | Primary organization name                                                                                  | string     |
+|      | `--overwrite-existing-v2`        | Overwrite existing files at the output paths instead of aborting the upgrade process                        |            |
+| `-p` | `--password`                     | Password for username                                                                                      | string     |
+| `-r` | `--retention`                    | Duration bucket will retain data (default `0`; retains data infinitely)                                    | string     |
+| `-t` | `--token`                        | Token for username. If not specified, a token is auto-generated.                                           | string     |
+| `-u` | `--username`                     | Primary username                                                                                           | string     |
+|      | `--v1-dir`                       | Path to source 1.x `db` directory containing `meta`, `data`, and `wal` sub-folders (default `~/.influxdb`) | string     |
+|      | `--v2-config-path`               | Destination path for upgraded 2.x configuration file (default `~/.influxdbv2/config.toml`)                 | string     |
+| `-v` | `--verbose`                      | Verbose output                                                                                             |            |
diff --git a/content/influxdb/v2.2/reference/cli/influxd/version.md b/content/influxdb/v2.2/reference/cli/influxd/version.md
new file mode 100644
index 000000000..d1fa617f6
--- /dev/null
+++ b/content/influxdb/v2.2/reference/cli/influxd/version.md
@@ -0,0 +1,24 @@
+---
+title: influxd version
+description: The `influxd version` command outputs the current version of InfluxDB.
+influxdb/v2.2/tags: [influxd, cli]
+menu:
+  influxdb_2_2_ref:
+    parent: influxd
+weight: 202
+products: [oss]
+---
+
+The `influxd version` command outputs the current version of InfluxDB.
+
+## Usage
+
+```
+influxd version [flags]
+```
+
+## Flags
+
+| Flag |          | Description                    |
+|:---- |:---      |:-----------                    |
+| `-h` | `--help` | Help for the `version` command |
diff --git a/content/influxdb/v2.2/reference/config-options.md b/content/influxdb/v2.2/reference/config-options.md
new file mode 100644
index 000000000..7ecb29083
--- /dev/null
+++ b/content/influxdb/v2.2/reference/config-options.md
@@ -0,0 +1,3503 @@
+---
+title: InfluxDB configuration options
+description: >
+  Customize your InfluxDB configuration by using [`influxd`](/influxdb/v2.2/reference/cli/influxd/)
+  configuration flags, setting environment variables, or defining configuration
+  options in a configuration file.
+menu:
+  influxdb_2_2_ref:
+    name: Configuration options
+weight: 3
+products: [oss]
+related:
+  - /influxdb/v2.2/reference/cli/influxd
+---
+
+Customize your InfluxDB configuration by using [`influxd`](/influxdb/v2.2/reference/cli/influxd/)
+configuration flags, setting environment variables, or defining configuration
+options in a configuration file.
+
+- [View your runtime server configuration](#view-your-runtime-server-configuration)
+- [Configuration precedence](#configuration-precedence)
+- [InfluxDB configuration file](#influxdb-configuration-file)
+- [Configuration options](#configuration-options)
+
+### View your runtime server configuration
+
+Use the `influx` CLI or the InfluxDB API to get the runtime server configuration of your InfluxDB instance.
+
+Server configuration commands require an [Operator token](/influxdb/v2.2/security/tokens/#operator-token).
+
+#### View your server configuration with the CLI
+
+Use the [`influx server-config` command](/influxdb/v2.2/reference/cli/influx/server-config/)
+to retrieve your runtime server configuration.
+
+```sh
+influx server-config
+```
+
+### View your server configuration with the API
+
+Use the `/api/v2/config` InfluxDB API endpoint to retrieve your runtime server configuration.
+
+[{{< api-endpoint method="GET" endpoint="http://localhost:8086/api/v2/config" >}}]((/influxdb/v2.2/api/#operation/GetConfig))
+
+### Configuration precedence
+InfluxDB honors configuration settings using the following precedence:
+
+1. `influxd` flags
+2. Environment variables
+3. Configuration file settings
+
+### InfluxDB configuration file
+
+When `influxd` starts, it checks for a file named `config.*` **in the current working directory**.
+The file extension depends on the syntax of the configuration file.
+InfluxDB configuration files support the following syntaxes:
+
+- **YAML** (`.yaml`, `.yml`)
+- **TOML** (`.toml`)
+- **JSON** (`.json`)
+
+To customize the directory path of the configuration file, set the `INFLUXD_CONFIG_PATH`
+environment variable to your custom path.
+
+```sh
+export INFLUXD_CONFIG_PATH=/path/to/custom/config/directory
+```
+
+On startup, `influxd` will check for a `config.*` in the `INFLUXD_CONFIG_PATH` directory.
+
+##### Example configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yaml
+query-concurrency: 20
+query-queue-size: 15
+secret-store: vault
+session-length: 120
+tls-cert: /path/to/influxdb.crt
+tls-key: /path/to/influxdb.key
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+query-concurrency = 20
+query-queue-size = 15
+secret-store = "vault"
+session-length = 120
+tls-cert = "/path/to/influxdb.crt"
+tls-key = "/path/to/influxdb.key"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "query-concurrency": 20,
+  "query-queue-size": 15,
+  "secret-store": "vault",
+  "session-length": 120,
+  "tls-cert": "/path/to/influxdb.crt",
+  "tls-key": "/path/to/influxdb.key"
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+{{% note %}}
+Only non-default settings need to be defined in the configuration file.
+{{% /note %}}
+
+## Configuration options
+
+To configure InfluxDB, use the following configuration options when starting the
+[`influxd` service](/influxdb/v2.2/reference/cli/influxd):
+
+- [assets-path](#assets-path)
+- [bolt-path](#bolt-path)
+- [e2e-testing](#e2e-testing)
+- [engine-path](#engine-path)
+- [feature-flags](#feature-flags)
+- [flux-log-enabled](#flux-log-enabled)
+- [hardening-enabled](#hardening-enabled)
+- [http-bind-address](#http-bind-address)
+- [http-idle-timeout](#http-idle-timeout)
+- [http-read-header-timeout](#http-read-header-timeout)
+- [http-read-timeout](#http-read-timeout)
+- [http-write-timeout](#http-write-timeout)
+- [influxql-max-select-buckets](#influxql-max-select-buckets)
+- [influxql-max-select-point](#influxql-max-select-point)
+- [influxql-max-select-series](#influxql-max-select-series)
+- [log-level](#log-level)
+- [metrics-disabled](#metrics-disabled)
+- [nats-max-payload-bytes](#nats-max-payload-bytes) <em style="opacity:.65">- (deprecated)</em>
+- [nats-port](#nats-port) <em style="opacity:.65">- (deprecated)</em>
+- [no-tasks](#no-tasks)
+- [pprof-disabled](#pprof-disabled)
+- [query-concurrency](#query-concurrency)
+- [query-initial-memory-bytes](#query-initial-memory-bytes)
+- [query-max-memory-bytes](#query-max-memory-bytes)
+- [query-memory-bytes](#query-memory-bytes)
+- [query-queue-size](#query-queue-size)
+- [reporting-disabled](#reporting-disabled)
+- [secret-store](#secret-store)
+- [session-length](#session-length)
+- [session-renew-disabled](#session-renew-disabled)
+- [sqlite-path](#sqlite-path)
+- [storage-cache-max-memory-size](#storage-cache-max-memory-size)
+- [storage-cache-snapshot-memory-size](#storage-cache-snapshot-memory-size)
+- [storage-cache-snapshot-write-cold-duration](#storage-cache-snapshot-write-cold-duration)
+- [storage-compact-full-write-cold-duration](#storage-compact-full-write-cold-duration)
+- [storage-compact-throughput-burst](#storage-compact-throughput-burst)
+- [storage-max-concurrent-compactions](#storage-max-concurrent-compactions)
+- [storage-max-index-log-file-size](#storage-max-index-log-file-size)
+- [storage-no-validate-field-size](#storage-no-validate-field-size)
+- [storage-retention-check-interval](#storage-retention-check-interval)
+- [storage-series-file-max-concurrent-snapshot-compactions](#storage-series-file-max-concurrent-snapshot-compactions)
+- [storage-series-id-set-cache-size](#storage-series-id-set-cache-size)
+- [storage-shard-precreator-advance-period](#storage-shard-precreator-advance-period)
+- [storage-shard-precreator-check-interval](#storage-shard-precreator-check-interval)
+- [storage-tsm-use-madv-willneed](#storage-tsm-use-madv-willneed)
+- [storage-validate-keys](#storage-validate-keys)
+- [storage-wal-fsync-delay](#storage-wal-fsync-delay)
+- [storage-wal-max-concurrent-writes](#storage-wal-max-concurrent-writes)
+- [storage-wal-max-write-delay](#storage-wal-max-write-delay)
+- [storage-write-timeout](#storage-write-timeout)
+- [store](#store)
+- [testing-always-allow-setup](#testing-always-allow-setup)
+- [tls-cert](#tls-cert)
+- [tls-key](#tls-key)
+- [tls-min-version](#tls-min-version)
+- [tls-strict-ciphers](#tls-strict-ciphers)
+- [tracing-type](#tracing-type)
+- [ui-disabled](#ui-disabled)
+- [vault-addr](#vault-addr)
+- [vault-cacert](#vault-cacert)
+- [vault-capath](#vault-capath)
+- [vault-client-cert](#vault-client-cert)
+- [vault-client-key](#vault-client-key)
+- [vault-client-timeout](#vault-client-timeout)
+- [vault-max-retries](#vault-max-retries)
+- [vault-skip-verify](#vault-skip-verify)
+- [vault-tls-server-name](#vault-tls-server-name)
+- [vault-token](#vault-token)
+
+---
+
+### assets-path
+Override the default InfluxDB user interface (UI) assets by serving assets from the specified directory.
+_Typically, InfluxData internal use only._
+
+| influxd flag    | Environment variable  | Configuration key |
+|:------------    |:--------------------  |:----------------- |
+| `--assets-path` | `INFLUXD_ASSETS_PATH` | `assets-path`     |
+
+###### influxd flag
+```sh
+influxd --assets-path=/path/to/custom/assets-dir
+```
+
+###### Environment variable
+```sh
+export INFLUXD_ASSETS_PATH=/path/to/custom/assets-dir
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+assets-path: /path/to/custom/assets-dir
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+assets-path = "/path/to/custom/assets-dir"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "assets-path": "/path/to/custom/assets-dir"
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### bolt-path
+Path to the [BoltDB](https://github.com/boltdb/bolt) database.
+BoltDB is a key value store written in Go.
+InfluxDB uses BoltDB to store data including organization and
+user information, UI data, REST resources, and other key value data.
+
+**Default:** `~/.influxdbv2/influxd.bolt`  
+
+| influxd flag  | Environment variable | Configuration key |
+|:------------  |:-------------------- |:----------------- |
+| `--bolt-path` | `INFLUXD_BOLT_PATH`  | `bolt-path`       |
+
+###### influxd flag
+```sh
+influxd --bolt-path=~/.influxdbv2/influxd.bolt
+```
+
+###### Environment variable
+```sh
+export INFLUXD_BOLT_PATH=~/.influxdbv2/influxd.bolt
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+bolt-path: ~/.influxdbv2/influxd.bolt
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+bolt-path = "~/.influxdbv2/influxd.bolt"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "bolt-path": "~/.influxdbv2/influxd.bolt"
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### e2e-testing
+Add a `/debug/flush` endpoint to the InfluxDB HTTP API to clear stores.
+InfluxData uses this endpoint in end-to-end testing.
+
+| influxd flag    | Environment variable  | Configuration key |
+|:------------    |:--------------------  |:----------------- |
+| `--e2e-testing` | `INFLUXD_E2E_TESTING` | `e2e-testing`     |
+
+###### influxd flag
+```sh
+influxd --e2e-testing
+```
+
+###### Environment variable
+```sh
+export INFLUXD_E2E_TESTING=true
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+e2e-testing: true
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+e2e-testing = true
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "e2e-testing": true
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### engine-path
+Path to persistent storage engine files where InfluxDB stores all
+Time-Structure Merge Tree (TSM) data on disk.
+
+**Default:** `~/.influxdbv2/engine`  
+
+| influxd flag    | Environment variable  | Configuration key |
+|:------------    |:--------------------  |:----------------- |
+| `--engine-path` | `INFLUXD_ENGINE_PATH` | `engine-path`     |
+
+###### influxd flag
+```sh
+influxd --engine-path=~/.influxdbv2/engine
+```
+
+###### Environment variable
+```sh
+export INFLUXD_ENGINE_PATH=~/.influxdbv2/engine
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+engine-path: ~/.influxdbv2/engine
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+engine-path = "~/.influxdbv2/engine"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "engine-path": "~/.influxdbv2/engine"
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### feature-flags
+Enable, disable, or override default values for feature flags.
+
+{{% note %}}
+Feature flags are used to develop and test experimental features and are
+intended for internal use only.
+{{% /note %}}
+
+| influxd flag      | Environment variable    | Configuration key |
+| :---------------- | :---------------------- | :---------------- |
+| `--feature-flags` | `INFLUXD_FEATURE_FLAGS` | `feature-flags`   |
+
+###### influxd flag
+```sh
+influxd --feature-flags flag1=value2,flag2=value2
+```
+
+###### Environment variable
+```sh
+export INFLUXD_FEATURE_FLAGS="{\"flag1\":\value1\",\"flag2\":\"value2\"}"
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+feature-flags:
+  flag1: "value1"
+  flag2: "value2"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+[feature-flags]
+  flag1 = "value1"
+  glag2 = "value2"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "feature-flags": {
+    "flag1": "value1",
+    "flag2": "value2"
+  }
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### flux-log-enabled
+
+Include option to show detailed logs for Flux queries, including the following log fields:
+
+- `compiler_type`: Compiler used for processing the query (will always be Flux).
+- `response_size`: Size of the response, in bytes.
+- `query`: The textual representation of the query.
+- `err`: Errors encountered while processing the query.
+- `stat_total_duration`: Total duration to process the query.
+- `stat_compile_duration`: Duration to compile the query.
+- `stat_execute_duration`: Duration to execute the query.
+- `stat_max_allocated`: Maximum amount of memory allocated while processing the query, in - bytes.
+- `stat_total_allocated`: Total amount of memory allocated while processing the query, in bytes. This includes memory that was freed and then used again.
+
+**Default:** `false`  
+
+| influxd flag         | Environment variable       | Configuration key |
+|:------------         |:--------------------       |:----------------- |
+| `--flux-log-enabled` | `INFLUXD_FLUX_LOG_ENABLED` | `flux-log-enabled`|
+
+###### influxd flag
+```sh
+influxd --flux-log-enabled=true
+```
+
+###### Environment variable
+```sh
+export INFLUXD_FLUX_LOG_ENABLED=true
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+flux-log-enabled: true
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+flux-log-enabled = "true"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "flux-log-enabled": "true"
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### hardening-enabled
+
+Enable [additional security features](/influxdb/v2.2/security/enable-hardening/)
+in InfluxDB.
+**Default:** `false`
+| influxd flag          | Environment variable        | Configuration key   |
+| :-------------------- | :-------------------------- | :------------------ |
+| `--hardening-enabled` | `INFLUXD_HARDENING_ENABLED` | `hardening-enabled` |
+
+###### influxd flag
+```sh
+influxd --hardening-enabled
+```
+
+###### Environment variable
+```sh
+export INFLUXD_HARDENING_ENABLED=true
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+hardening-enabled: true
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+hardening-enabled = true
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "hardening-enabled": true
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### http-bind-address
+Bind address for the InfluxDB HTTP API.
+Customize the URL and port for the InfluxDB API and UI.
+
+**Default:** `:8086`  
+
+| influxd flag          | Environment variable        | Configuration key   |
+|:------------          |:--------------------        |:-----------------   |
+| `--http-bind-address` | `INFLUXD_HTTP_BIND_ADDRESS` | `http-bind-address` |
+
+###### influxd flag
+```sh
+influxd --http-bind-address=:8086
+```
+
+###### Environment variable
+```sh
+export INFLUXD_HTTP_BIND_ADDRESS=:8086
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+http-bind-address: ":8086"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+http-bind-address = ":8086"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "http-bind-address": ":8086"
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### http-idle-timeout
+Maximum duration the server should keep established connections alive while waiting for new requests.
+Set to `0` for no timeout.
+
+**Default:** `3m0s`
+
+| influxd flag          | Environment variable        | Configuration key   |
+|:------------          |:--------------------        |:-----------------   |
+| `--http-idle-timeout` | `INFLUXD_HTTP_IDLE_TIMEOUT` | `http-idle-timeout` |
+
+###### influxd flag
+```sh
+influxd --http-idle-timeout=3m0s
+```
+
+###### Environment variable
+```sh
+export INFLUXD_HTTP_IDLE_TIMEOUT=3m0s
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+http-idle-timeout: 3m0s
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+http-idle-timeout = "3m0s"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "http-idle-timeout": "3m0s"
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### http-read-header-timeout
+Maximum duration the server should try to read HTTP headers for new requests.
+Set to `0` for no timeout.
+
+**Default:** `10s`
+
+| influxd flag                 | Environment variable               | Configuration key          |
+|:------------                 |:--------------------               |:-----------------          |
+| `--http-read-header-timeout` | `INFLUXD_HTTP_READ_HEADER_TIMEOUT` | `http-read-header-timeout` |
+
+###### influxd flag
+```sh
+influxd --http-read-header-timeout=10s
+```
+
+###### Environment variable
+```sh
+export INFLUXD_HTTP_READ_HEADER_TIMEOUT=10s
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+http-read-header-timeout: 10s
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+http-read-header-timeout = "10s"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "http-read-header-timeout": "10s"
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### http-read-timeout
+Maximum duration the server should try to read the entirety of new requests.
+Set to `0` for no timeout.
+
+**Default:** `0`
+
+{{% note %}}
+#### Set timeouts specific to your workload
+Although no `http-read-timeout` is set by default, we **strongly recommend**
+setting a timeout specific to your workload.
+HTTP timeouts protect against large amounts of open connections that could
+potentially hurt performance.
+{{% /note %}}
+
+| influxd flag          | Environment variable        | Configuration key   |
+|:------------          |:--------------------        |:-----------------   |
+| `--http-read-timeout` | `INFLUXD_HTTP_READ_TIMEOUT` | `http-read-timeout` |
+
+###### influxd flag
+```sh
+influxd --http-read-timeout=10s
+```
+
+###### Environment variable
+```sh
+export INFLUXD_HTTP_READ_TIMEOUT=10s
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+http-read-timeout: 10s
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+http-read-timeout = "10s"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "http-read-timeout": "10s"
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### http-write-timeout
+Maximum duration the server should spend processing and responding to write requests.
+Set to `0` for no timeout.
+
+**Default:** `0`
+
+{{% note %}}
+#### Set timeouts specific to your workload
+Although no `http-write-timeout` is set by default, we **strongly recommend**
+setting a timeout specific to your workload.
+HTTP timeouts protect against large amounts of open connections that could
+potentially hurt performance.
+{{% /note %}}
+
+| influxd flag           | Environment variable         | Configuration key    |
+|:------------           |:--------------------         |:-----------------    |
+| `--http-write-timeout` | `INFLUXD_HTTP_WRITE_TIMEOUT` | `http-write-timeout` |
+
+###### influxd flag
+```sh
+influxd --http-write-timeout=10s
+```
+
+###### Environment variable
+```sh
+export INFLUXD_HTTP_WRITE_TIMEOUT=10s
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+http-write-timeout: 10s
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+http-write-timeout = "10s"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "http-write-timeout": "10s"
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### influxql-max-select-buckets
+Maximum number of group by time buckets a `SELECT` statement can create.
+`0` allows an unlimited number of buckets.
+
+**Default:** `0`
+
+| influxd flag                    | Environment variable                  | Configuration key             |
+|:------------                    |:--------------------                  |:-----------------             |
+| `--influxql-max-select-buckets` | `INFLUXD_INFLUXQL_MAX_SELECT_BUCKETS` | `influxql-max-select-buckets` |
+
+###### influxd flag
+```sh
+influxd --influxql-max-select-buckets=0
+```
+
+###### Environment variable
+```sh
+export INFLUXD_INFLUXQL_MAX_SELECT_BUCKETS=0
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+influxql-max-select-buckets: 0
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+influxql-max-select-buckets = 0
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "influxql-max-select-buckets": 0
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### influxql-max-select-point
+Maximum number of points a `SELECT` statement can process.
+`0` allows an unlimited number of points.
+InfluxDB checks the point count every second (so queries exceeding the maximum aren’t immediately aborted).
+
+**Default:** `0`
+
+| influxd flag                  | Environment variable                | Configuration key           |
+|:------------                  |:--------------------                |:-----------------           |
+| `--influxql-max-select-point` | `INFLUXD_INFLUXQL_MAX_SELECT_POINT` | `influxql-max-select-point` |
+
+###### influxd flag
+```sh
+influxd --influxql-max-select-point=0
+```
+
+###### Environment variable
+```sh
+export INFLUXD_INFLUXQL_MAX_SELECT_POINT=0
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+influxql-max-select-point: 0
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+influxql-max-select-point = 0
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "influxql-max-select-point": 0
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### influxql-max-select-series
+Maximum number of series a `SELECT` statement can return.
+`0` allows an unlimited number of series.
+
+**Default:** `0`
+
+| influxd flag                   | Environment variable                 | Configuration key            |
+|:------------                   |:--------------------                 |:-----------------            |
+| `--influxql-max-select-series` | `INFLUXD_INFLUXQL_MAX_SELECT_SERIES` | `influxql-max-select-series` |
+
+###### influxd flag
+```sh
+influxd --influxql-max-select-series=0
+```
+
+###### Environment variable
+```sh
+export INFLUXD_INFLUXQL_MAX_SELECT_SERIES=0
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+influxql-max-select-series: 0
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+influxql-max-select-series = 0
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "influxql-max-select-series": 0
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### log-level
+Log output level.
+InfluxDB outputs log entries with severity levels greater than or equal to the level specified.
+
+**Options:** `debug`, `info`, `error`  
+**Default:** `info`  
+
+| influxd flag  | Environment variable | Configuration key |
+|:------------  |:-------------------- |:----------------- |
+| `--log-level` | `INFLUXD_LOG_LEVEL`  | `log-level`       |
+
+###### influxd flag
+```sh
+influxd --log-level=info
+```
+
+###### Environment variable
+```sh
+export INFLUXD_LOG_LEVEL=info
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+log-level: info
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+log-level = "info"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "log-level": "info"
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### metrics-disabled
+Disable the HTTP `/metrics` endpoint which exposes [internal InfluxDB metrics](/influxdb/v2.2/reference/internals/metrics/).
+
+**Default:** `false`  
+
+| influxd flag         | Environment variable       | Configuration key  |
+|:------------         |:--------------------       |:-----------------  |
+| `--metrics-disabled` | `INFLUXD_METRICS_DISABLED` | `metrics-disabled` |
+
+###### influxd flag
+```sh
+influxd --metrics-disabled
+```
+
+###### Environment variable
+```sh
+export INFLUXD_METRICS_DISABLED=true
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+metrics-disabled: true
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+metrics-disabled = true
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "metrics-disabled": true
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### nats-max-payload-bytes
+
+{{% warn %}}
+`nats-max-payload-bytes` was **deprecated in InfluxDB 2.2** and no longer has any effect.
+{{% /warn %}}
+
+Maximum number of bytes allowed in a NATS message payload.
+
+**Default:** `1048576`
+
+| influxd flag               | Environment variable             | Configuration key        |
+|:------------               |:--------------------             |:-----------------        |
+| `--nats-max-payload-bytes` | `INFLUXD_NATS_MAX_PAYLOAD_BYTES` | `nats-max-payload-bytes` |
+
+###### influxd flag
+```sh
+influxd --nats-max-payload-bytes=1048576
+```
+
+###### Environment variable
+```sh
+export INFLUXD_NATS_MAX_PAYLOAD_BYTES=1048576
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+nats-max-payload-bytes: 1048576
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+nats-max-payload-bytes = 1048576
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "nats-max-payload-bytes": 1048576
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### nats-port
+
+{{% warn %}}
+`nats-port` was **deprecated in InfluxDB 2.2** and no longer has any effect.
+{{% /warn %}}
+
+Port for the NATS streaming server. `-1` selects a random port.
+
+**Default:** `-1`
+
+| influxd flag  | Environment variable | Configuration key |
+|:------------  |:-------------------- |:----------------- |
+| `--nats-port` | `INFLUXD_NATS_PORT`  | `nats-port`       |
+
+###### influxd flag
+```sh
+influxd --nats-port=-1
+```
+
+###### Environment variable
+```sh
+export INFLUXD_NATS_PORT=-1
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+nats-port: -1
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+nats-port = -1
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "nats-port": -1
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### no-tasks
+Disable the task scheduler.
+If problematic tasks prevent InfluxDB from starting, use this option to start
+InfluxDB without scheduling or executing tasks.
+
+**Default:** `false`
+
+| influxd flag | Environment variable | Configuration key |
+|:------------ |:-------------------- |:----------------- |
+| `--no-tasks` | `INFLUXD_NO_TASKS`   | `no-tasks`        |
+
+###### influxd flag
+```sh
+influxd --no-tasks
+```
+
+###### Environment variable
+```sh
+export INFLUXD_NO_TASKS=true
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+no-tasks: true
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+no-tasks = true
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "no-tasks": true
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### pprof-disabled
+Disable the `/debug/pprof` HTTP endpoint.
+This endpoint provides runtime profiling data and can be helpful when debugging.
+
+**Default:** `false`
+
+| influxd flag       | Environment variable     | Configuration key |
+|:-------------------|:-------------------------|:------------------|
+| `--pprof-disabled` | `INFLUXD_PPROF_DISABLED` | `pprof-disabled`  |
+
+###### influxd flag
+```sh
+influxd --pprof-disabled
+```
+
+###### Environment variable
+```sh
+export INFLUXD_PPROF_DISABLED=true
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+pprof-disabled: true
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+pprof-disabled = true
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "pprof-disabled": true
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### query-concurrency
+Number of queries allowed to execute concurrently.
+
+**Default:** `10`
+
+| influxd flag          | Environment variable        | Configuration key   |
+|:------------          |:--------------------        |:-----------------   |
+| `--query-concurrency` | `INFLUXD_QUERY_CONCURRENCY` | `query-concurrency` |
+
+###### influxd flag
+```sh
+influxd --query-concurrency=10
+```
+
+###### Environment variable
+```sh
+export INFLUXD_QUERY_CONCURRENCY=10
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+query-concurrency: 10
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+query-concurrency = 10
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "query-concurrency": 10
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### query-initial-memory-bytes
+Initial bytes of memory allocated for a query.
+
+**Default:** _equal to_ [query-memory-bytes](#query-memory-bytes)
+
+| influxd flag                   | Environment variable                 | Configuration key            |
+|:------------                   |:--------------------                 |:-----------------            |
+| `--query-initial-memory-bytes` | `INFLUXD_QUERY_INITIAL_MEMORY_BYTES` | `query-initial-memory-bytes` |
+
+###### influxd flag
+```sh
+influxd --query-initial-memory-bytes=10485760
+```
+
+###### Environment variable
+```sh
+export INFLUXD_QUERY_INITIAL_MEMORY_BYTES=10485760
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+query-initial-memory-bytes: 10485760
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+query-initial-memory-bytes = 10485760
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "query-initial-memory-bytes": 10485760
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### query-max-memory-bytes
+Maximum total bytes of memory allowed for queries.
+
+**Default:** _equal to_ [query-concurrency](#query-concurrency) × [query-memory-bytes](#query-memory-bytes)
+
+| influxd flag               | Environment variable             | Configuration key        |
+|:------------               |:--------------------             |:-----------------        |
+| `--query-max-memory-bytes` | `INFLUXD_QUERY_MAX_MEMORY_BYTES` | `query-max-memory-bytes` |
+
+###### influxd flag
+```sh
+influxd --query-max-memory-bytes=104857600
+```
+
+###### Environment variable
+```sh
+export INFLUXD_QUERY_MAX_MEMORY_BYTES=104857600
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+query-max-memory-bytes: 104857600
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+query-max-memory-bytes = 104857600
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "query-max-memory-bytes": 104857600
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### query-memory-bytes
+Maximum bytes of memory allowed for a single query.
+
+**Default:** _unlimited_
+
+{{% note %}}
+Must be greater than or equal to [query-initial-memory-bytes](#query-initial-memory-bytes).
+{{% /note %}}
+
+| influxd flag           | Environment variable         | Configuration key    |
+|:------------           |:--------------------         |:-----------------    |
+| `--query-memory-bytes` | `INFLUXD_QUERY_MEMORY_BYTES` | `query-memory-bytes` |
+
+###### influxd flag
+```sh
+influxd --query-memory-bytes=10485760
+```
+
+###### Environment variable
+```sh
+export INFLUXD_QUERY_MEMORY_BYTES=10485760
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+query-memory-bytes: 10485760
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+query-memory-bytes = 10485760
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "query-memory-bytes": 10485760
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### query-queue-size
+Maximum number of queries allowed in execution queue.
+When queue limit is reached, new queries are rejected.
+
+**Default:** `10`
+
+| influxd flag         | Environment variable       | Configuration key  |
+|:------------         |:--------------------       |:-----------------  |
+| `--query-queue-size` | `INFLUXD_QUERY_QUEUE_SIZE` | `query-queue-size` |
+
+###### influxd flag
+```sh
+influxd --query-queue-size=10
+```
+
+###### Environment variable
+```sh
+export INFLUXD_QUERY_QUEUE_SIZE=10
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+query-queue-size: 10
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+query-queue-size = 10
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "query-queue-size": 10
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### reporting-disabled
+Disables sending telemetry data to InfluxData.
+The [InfluxData telemetry](https://www.influxdata.com/telemetry) page provides
+information about what data is collected and how InfluxData uses it.
+
+**Default:** `false`
+
+| influxd flag           | Environment variable         | Configuration key    |
+|:------------           |:--------------------         |:-----------------    |
+| `--reporting-disabled` | `INFLUXD_REPORTING_DISABLED` | `reporting-disabled` |
+
+###### influxd flag
+```sh
+influxd --reporting-disabled
+```
+
+###### Environment variable
+```sh
+export INFLUXD_REPORTING_DISABLED=true
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+reporting-disabled: true
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+reporting-disabled = true
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "reporting-disabled": true
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### secret-store
+Specifies the data store for secrets such as passwords and tokens.
+Store secrets in either the InfluxDB [internal BoltDB](#bolt-path)
+or in [Vault](https://www.vaultproject.io/).
+
+**Options:** `bolt`, `vault`  
+**Default:** `bolt`  
+
+| influxd flag     | Environment variable   | Configuration key |
+|:------------     |:--------------------   |:----------------- |
+| `--secret-store` | `INFLUXD_SECRET_STORE` | `secret-store`    |
+
+###### influxd flag
+```sh
+influxd --secret-store=bolt
+```
+
+###### Environment variable
+```sh
+export INFLUXD_SECRET_STORE=bolt
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+secret-store: bolt
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+secret-store = "bolt"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "secret-store": "bolt"
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### session-length
+Specifies the Time to Live (TTL) **in minutes** for newly created user sessions.
+
+**Default:** `60`
+
+| influxd flag       | Environment variable     | Configuration key |
+|:------------       |:--------------------     |:----------------- |
+| `--session-length` | `INFLUXD_SESSION_LENGTH` | `session-length`  |
+
+###### influxd flag
+```sh
+influxd --session-length=60
+```
+
+###### Environment variable
+```sh
+export INFLUXD_SESSION_LENGTH=60
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+session-length: 60
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+session-length = 60
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "session-length": 60
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### session-renew-disabled
+Disables automatically extending a user's session TTL on each request.
+By default, every request sets the session's expiration time to five minutes from now.
+When disabled, sessions expire after the specified [session length](#session-length)
+and the user is redirected to the login page, even if recently active.
+
+**Default:** `false`
+
+| influxd flag               | Environment variable             | Configuration key        |
+|:------------               |:--------------------             |:-----------------        |
+| `--session-renew-disabled` | `INFLUXD_SESSION_RENEW_DISABLED` | `session-renew-disabled` |
+
+###### influxd flag
+```sh
+influxd --session-renew-disabled
+```
+
+###### Environment variable
+```sh
+export INFLUXD_SESSION_RENEW_DISABLED=true
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+session-renew-disabled: true
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+session-renew-disabled = true
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "session-renew-disabled": true
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### sqlite-path
+
+Path to the SQLite database file.
+The SQLite database is used to store metadata for notebooks and annotations.
+
+**Default:** _`influxd.sqlite` in the same directory as the [bolt-path](#bolt-path)._
+
+| influxd flag    | Environment variable  | Configuration key |
+|:----------------|:----------------------|:------------------|
+| `--sqlite-path` | `INFLUXD_SQLITE_PATH` | `sqlite-path`     |
+
+###### influxd flag
+```sh
+influxd --sqlite-path ~/.influxdbv2/influxd.sqlite
+```
+
+###### Environment variable
+```sh
+export INFLUXD_SQLITE_PATH=~/.influxdbv2/influxd.sqlite
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+sqlite-path: ~/.influxdbv2/influxd.sqlite
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+sqlite-path = "~/.influxdbv2/influxd.sqlite"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "sqlite-path": "~/.influxdbv2/influxd.sqlite"
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### storage-cache-max-memory-size
+Maximum size (in bytes) a shard's cache can reach before it starts rejecting writes.
+
+**Default:** `1073741824`
+
+| influxd flag                      | Environment variable                    | Configuration key               |
+|:----------------------------------|:----------------------------------------|:--------------------------------|
+| `--storage-cache-max-memory-size` | `INFLUXD_STORAGE_CACHE_MAX_MEMORY_SIZE` | `storage-cache-max-memory-size` |
+
+###### influxd flag
+```sh
+influxd --storage-cache-max-memory-size=1073741824
+```
+
+###### Environment variable
+```sh
+export INFLUXD_STORAGE_CACHE_MAX_MEMORY_SIZE=1073741824
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+storage-cache-max-memory-size: 1073741824
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+storage-cache-max-memory-size = 1073741824
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "storage-cache-max-memory-size": 1073741824
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### storage-cache-snapshot-memory-size
+Size (in bytes) at which the storage engine will snapshot the cache
+and write it to a TSM file to make more memory available.
+
+**Default:** `26214400`)
+
+| influxd flag                           | Environment variable                         | Configuration key                    |
+|:------------                           |:--------------------                         |:-----------------                    |
+| `--storage-cache-snapshot-memory-size` | `INFLUXD_STORAGE_CACHE_SNAPSHOT_MEMORY_SIZE` | `storage-cache-snapshot-memory-size` |
+
+###### influxd flag
+```sh
+influxd --storage-cache-snapshot-memory-size=26214400
+```
+
+###### Environment variable
+```sh
+export INFLUXD_STORAGE_CACHE_SNAPSHOT_MEMORY_SIZE=26214400
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+storage-cache-snapshot-memory-size: 26214400
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+storage-cache-snapshot-memory-size = 26214400
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "storage-cache-snapshot-memory-size": 26214400
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### storage-cache-snapshot-write-cold-duration
+Duration at which the storage engine will snapshot the cache and
+write it to a new TSM file if the shard hasn't received writes or deletes.
+
+**Default:** `10m0s`
+
+| influxd flag                                   | Environment variable                                 | Configuration key                            |
+|:------------                                   |:--------------------                                 |:-----------------                            |
+| `--storage-cache-snapshot-write-cold-duration` | `INFLUXD_STORAGE_CACHE_SNAPSHOT_WRITE_COLD_DURATION` | `storage-cache-snapshot-write-cold-duration` |
+
+###### influxd flag
+```sh
+influxd --storage-cache-snapshot-write-cold-duration=10m0s
+```
+
+###### Environment variable
+```sh
+export INFLUXD_STORAGE_CACHE_SNAPSHOT_WRITE_COLD_DURATION=10m0s
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+storage-cache-snapshot-write-cold-duration: 10m0s
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+storage-cache-snapshot-write-cold-duration = "10m0s"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "storage-cache-snapshot-write-cold-duration": "10m0s"
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### storage-compact-full-write-cold-duration
+Duration at which the storage engine will compact all TSM files in a
+shard if it hasn't received writes or deletes.
+
+**Default:** `4h0m0s`
+
+| influxd flag                                 | Environment variable                               | Configuration key                          |
+|:------------                                 |:--------------------                               |:-----------------                          |
+| `--storage-compact-full-write-cold-duration` | `INFLUXD_STORAGE_COMPACT_FULL_WRITE_COLD_DURATION` | `storage-compact-full-write-cold-duration` |
+
+###### influxd flag
+```sh
+influxd --storage-compact-full-write-cold-duration=4h0m0s
+```
+
+###### Environment variable
+```sh
+export INFLUXD_STORAGE_COMPACT_FULL_WRITE_COLD_DURATION=4h0m0s
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+storage-compact-full-write-cold-duration: 4h0m0s
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+storage-compact-full-write-cold-duration = "4h0m0s"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "storage-compact-full-write-cold-duration": "4h0m0s"
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### storage-compact-throughput-burst
+Rate limit (in bytes per second) that TSM compactions can write to disk.
+
+**Default:** `50331648`
+
+| influxd flag                         | Environment variable                       | Configuration key                  |
+|:------------                         |:--------------------                       |:-----------------                  |
+| `--storage-compact-throughput-burst` | `INFLUXD_STORAGE_COMPACT_THROUGHPUT_BURST` | `storage-compact-throughput-burst` |
+
+###### influxd flag
+```sh
+influxd --storage-compact-throughput-burst=50331648
+```
+
+###### Environment variable
+```sh
+export INFLUXD_STORAGE_COMPACT_THROUGHPUT_BURST=50331648
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+storage-compact-throughput-burst: 50331648
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+storage-compact-throughput-burst = 50331648
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "storage-compact-throughput-burst": 50331648
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### storage-max-concurrent-compactions
+Maximum number of full and level compactions that can run concurrently.
+A value of `0` results in 50% of `runtime.GOMAXPROCS(0)` used at runtime.
+Any number greater than zero limits compactions to that value.
+_This setting does not apply to cache snapshotting._
+
+**Default:** `0`
+
+| influxd flag                           | Environment variable                         | Configuration key                    |
+|:------------                           |:--------------------                         |:-----------------                    |
+| `--storage-max-concurrent-compactions` | `INFLUXD_STORAGE_MAX_CONCURRENT_COMPACTIONS` | `storage-max-concurrent-compactions` |
+
+###### influxd flag
+```sh
+influxd --storage-max-concurrent-compactions=0
+```
+
+###### Environment variable
+```sh
+export INFLUXD_STORAGE_MAX_CONCURRENT_COMPACTIONS=0
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+storage-max-concurrent-compactions: 0
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+storage-max-concurrent-compactions = 0
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "storage-max-concurrent-compactions": 0
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### storage-max-index-log-file-size
+Size (in bytes) at which an index write-ahead log (WAL) file will compact into an index file.
+Lower sizes will cause log files to be compacted more quickly and result in lower
+heap usage at the expense of write throughput.
+
+**Default:** `1048576`
+
+| influxd flag                        | Environment variable                      | Configuration key                 |
+|:------------                        |:--------------------                      |:-----------------                 |
+| `--storage-max-index-log-file-size` | `INFLUXD_STORAGE_MAX_INDEX_LOG_FILE_SIZE` | `storage-max-index-log-file-size` |
+
+###### influxd flag
+```sh
+influxd --storage-max-index-log-file-size=1048576
+```
+
+###### Environment variable
+```sh
+export INFLUXD_STORAGE_MAX_INDEX_LOG_FILE_SIZE=1048576
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+storage-max-index-log-file-size: 1048576
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+storage-max-index-log-file-size = 1048576
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "storage-max-index-log-file-size": 1048576
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### storage-no-validate-field-size
+Skip field size validation on incoming write requests.
+
+**Default:** `false`
+
+| influxd flag                       | Environment variable                     | Configuration key                |
+| :--------------------------------- | :--------------------------------------- | :------------------------------- |
+| `--storage-no-validate-field-size` | `INFLUXD_STORAGE_NO_VALIDATE_FIELD_SIZE` | `storage-no-validate-field-size` |
+
+###### influxd flag
+```sh
+influxd --storage-no-validate-field-size
+```
+
+###### Environment variable
+```sh
+export INFLUXD_STORAGE_NO_VALIDATE_FIELD_SIZE=true
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+storage-no-validate-field-size: true
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+storage-no-validate-field-size = true
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "storage-no-validate-field-size": true
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### storage-retention-check-interval
+Interval of retention policy enforcement checks.
+
+**Default:** `30m0s`
+
+| influxd flag                         | Environment variable                       | Configuration key                  |
+|:------------                         |:--------------------                       |:-----------------                  |
+| `--storage-retention-check-interval` | `INFLUXD_STORAGE_RETENTION_CHECK_INTERVAL` | `storage-retention-check-interval` |
+
+###### influxd flag
+```sh
+influxd --storage-retention-check-interval=30m0s
+```
+
+###### Environment variable
+```sh
+export INFLUXD_STORAGE_RETENTION_CHECK_INTERVAL=30m0s
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+storage-retention-check-interval: 30m0s
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+storage-retention-check-interval = "30m0s"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "storage-retention-check-interval": "30m0s"
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### storage-series-file-max-concurrent-snapshot-compactions
+Maximum number of snapshot compactions that can run concurrently across
+all series partitions in a database.
+
+**Default:** `0`
+
+| influxd flag                                                | Environment variable                                              | Configuration key                                         |
+|:------------                                                |:--------------------                                              |:-----------------                                         |
+| `--storage-series-file-max-concurrent-snapshot-compactions` | `INFLUXD_STORAGE_SERIES_FILE_MAX_CONCURRENT_SNAPSHOT_COMPACTIONS` | `storage-series-file-max-concurrent-snapshot-compactions` |
+
+###### influxd flag
+```sh
+influxd --storage-series-file-max-concurrent-snapshot-compactions=0
+```
+
+###### Environment variable
+```sh
+export INFLUXD_STORAGE_SERIES_FILE_MAX_CONCURRENT_SNAPSHOT_COMPACTIONS=0
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+storage-series-file-max-concurrent-snapshot-compactions: 0
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+storage-series-file-max-concurrent-snapshot-compactions = 0
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "storage-series-file-max-concurrent-snapshot-compactions": 0
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### storage-series-id-set-cache-size
+Size of the internal cache used in the TSI index to store
+previously calculated series results.
+Cached results are returned quickly rather than needing to be recalculated when
+a subsequent query with the same tag key/value predicate is executed.
+Setting this value to `0` will disable the cache and may decrease query performance.
+
+**Default:** `100`
+
+{{% note %}}
+This value should only be increased if the set of regularly used tag key/value
+predicates across all measurements for a database is larger than 100.
+An increase in cache size may lead to an increase in heap usage.
+{{% /note %}}
+
+| influxd flag                                                | Environment variable                                              | Configuration key                                         |
+|:------------                                                |:--------------------                                              |:-----------------                                         |
+| `--storage-series-id-set-cache-size` | `INFLUXD_STORAGE_SERIES_ID_SET_CACHE_SIZE` | `storage-series-id-set-cache-size` |
+
+###### influxd flag
+```sh
+influxd --storage-series-id-set-cache-size=100
+```
+
+###### Environment variable
+```sh
+export INFLUXD_STORAGE_SERIES_ID_SET_CACHE_SIZE=100
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+storage-series-id-set-cache-size: 100
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+storage-series-id-set-cache-size = 100
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "storage-series-id-set-cache-size": 100
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### storage-shard-precreator-advance-period
+The time before a shard group's end-time that the successor shard group is created.
+
+**Default:** `30m0s`
+
+| influxd flag                                | Environment variable                              | Configuration key                         |
+|:------------                                |:--------------------                              |:-----------------                         |
+| `--storage-shard-precreator-advance-period` | `INFLUXD_STORAGE_SHARD_PRECREATOR_ADVANCE_PERIOD` | `storage-shard-precreator-advance-period` |
+
+###### influxd flag
+```sh
+influxd --storage-shard-precreator-advance-period=30m0s
+```
+
+###### Environment variable
+```sh
+export INFLUXD_STORAGE_SHARD_PRECREATOR_ADVANCE_PERIOD=30m0s
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+storage-shard-precreator-advance-period: 30m0s
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+storage-shard-precreator-advance-period = "30m0s"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "storage-shard-precreator-advance-period": "30m0s"
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### storage-shard-precreator-check-interval
+Interval of pre-create new shards check.
+
+**Default:** `10m0s`
+
+| influxd flag                                | Environment variable                              | Configuration key                         |
+|:------------                                |:--------------------                              |:-----------------                         |
+| `--storage-shard-precreator-check-interval` | `INFLUXD_STORAGE_SHARD_PRECREATOR_CHECK_INTERVAL` | `storage-shard-precreator-check-interval` |
+
+###### influxd flag
+```sh
+influxd --storage-shard-precreator-check-interval=10m0s
+```
+
+###### Environment variable
+```sh
+export INFLUXD_STORAGE_SHARD_PRECREATOR_CHECK_INTERVAL=10m0s
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+storage-shard-precreator-check-interval: 10m0s
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+storage-shard-precreator-check-interval = "10m0s"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "storage-shard-precreator-check-interval": "10m0s"
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### storage-tsm-use-madv-willneed
+Inform the kernel that InfluxDB intends to page in mmap'd sections of TSM files.
+
+**Default:** `false`
+
+| influxd flag                      | Environment variable                    | Configuration key               |
+|:------------                      |:--------------------                    |:-----------------               |
+| `--storage-tsm-use-madv-willneed` | `INFLUXD_STORAGE_TSM_USE_MADV_WILLNEED` | `storage-tsm-use-madv-willneed` |
+
+###### influxd flag
+```sh
+influxd --storage-tsm-use-madv-willneed
+```
+
+###### Environment variable
+```sh
+export INFLUXD_STORAGE_TSM_USE_MADV_WILLNEED=true
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+storage-tsm-use-madv-willneed: true
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+storage-tsm-use-madv-willneed = true
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "storage-tsm-use-madv-willneed": true
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### storage-validate-keys
+Validate incoming writes to ensure keys have only valid unicode characters.
+
+**Default:** `false`
+
+| influxd flag              | Environment variable            | Configuration key       |
+|:------------              |:--------------------            |:-----------------       |
+| `--storage-validate-keys` | `INFLUXD_STORAGE_VALIDATE_KEYS` | `storage-validate-keys` |
+
+###### influxd flag
+```sh
+influxd --storage-validate-keys
+```
+
+###### Environment variable
+```sh
+export INFLUXD_STORAGE_VALIDATE_KEYS=true
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+storage-validate-keys: true
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+storage-validate-keys = true
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "storage-validate-keys": true
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### storage-wal-fsync-delay
+Duration a write will wait before fsyncing.
+A duration greater than `0` batches multiple fsync calls.
+This is useful for slower disks or when WAL write contention is present.
+
+**Default:** `0s`
+
+| influxd flag                | Environment variable              | Configuration key         |
+|:------------                |:--------------------              |:-----------------         |
+| `--storage-wal-fsync-delay` | `INFLUXD_STORAGE_WAL_FSYNC_DELAY` | `storage-wal-fsync-delay` |
+
+###### influxd flag
+```sh
+influxd --storage-wal-fsync-delay=0s
+```
+
+###### Environment variable
+```sh
+export INFLUXD_STORAGE_WAL_FSYNC_DELAY=0s
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+storage-wal-fsync-delay: 0s
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+storage-wal-fsync-delay = "0s"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "storage-wal-fsync-delay": "0s"
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### storage-wal-max-concurrent-writes
+Maximum number writes to the WAL directory to attempt at the same time.
+
+**Default:** `0` _(number of processing units available × 2)_
+
+| influxd flag                          | Environment variable                        | Configuration key                   |
+| :------------------------------------ | :------------------------------------------ | :---------------------------------- |
+| `--storage-wal-max-concurrent-writes` | `INFLUXD_STORAGE_WAL_MAX_CONCURRENT_WRITES` | `storage-wal-max-concurrent-writes` |
+
+###### influxd flag
+```sh
+influxd --storage-wal-max-concurrent-writes=0
+```
+
+###### Environment variable
+```sh
+export INFLUXD_STORAGE_WAL_MAX_CONCURRENT_WRITES=0
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+storage-wal-max-concurrent-writes: 0
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+storage-wal-max-concurrent-writes = 0
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "storage-wal-max-concurrent-writes": 0
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### storage-wal-max-write-delay
+Maximum amount of time a write request to the WAL directory will wait when the
+the [maximum number of concurrent active writes to the WAL directory](#storage-wal-max-concurrent-writes)
+has been met. Set to `0` to disable the timeout.
+
+**Default:** `10m`
+
+| influxd flag                    | Environment variable                  | Configuration key             |
+| :------------------------------ | :------------------------------------ | :---------------------------- |
+| `--storage-wal-max-write-delay` | `INFLUXD_STORAGE_WAL_MAX_WRITE_DELAY` | `storage-wal-max-write-delay` |
+
+###### influxd flag
+```sh
+influxd --storage-wal-max-write-delay=10m
+```
+
+###### Environment variable
+```sh
+export INFLUXD_STORAGE_WAL_MAX_WRITE_DELAY=10m
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+storage-wal-max-write-delay: 10m
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+storage-wal-max-write-delay = "10m"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "storage-wal-max-write-delay": "10m"
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### storage-write-timeout
+Maximum amount of time the storage engine will process a write request before timing out.
+
+**Default:** `10s`
+
+| influxd flag              | Environment variable            | Configuration key       |
+| :------------------------ | :------------------------------ | :---------------------- |
+| `--storage-write-timeout` | `INFLUXD_STORAGE_WRITE_TIMEOUT` | `storage-write-timeout` |
+
+###### influxd flag
+```sh
+influxd --storage-write-timeout=10s
+```
+
+###### Environment variable
+```sh
+export INFLUXD_STORAGE_WRITE_TIMEOUT=10s
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+storage-write-timeout: 10s
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+storage-write-timeout = "10s"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "storage-write-timeout": "10s"
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### store
+Specifies the data store for REST resources.
+
+**Options:** `disk`, `memory`  
+**Default:** `disk`  
+
+{{% note %}}
+For backwards compatibility, this flag also acceptss `bolt` as a value.
+When using `disk`, REST resources are stored on disk using the [bolt-path](#bolt-path) and [sqlite-path](#sqlite-path).
+{{% /note %}}
+
+{{% note %}}
+`memory` is meant for transient environments, such as testing environments, where
+data persistence does not matter.
+InfluxData does not recommend using `memory` in production.
+{{% /note %}}
+
+| influxd flag | Environment variable | Configuration key |
+|:------------ |:-------------------- |:----------------- |
+| `--store`    | `INFLUXD_STORE`      | `store`           |
+
+###### influxd flag
+```sh
+influxd --store=bolt
+```
+
+###### Environment variable
+```sh
+export INFLUXD_STORE=bolt
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+store: bolt
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+store = "bolt"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "store": "bolt"
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### testing-always-allow-setup
+Ensures the `/api/v2/setup` endpoint always returns `true` to allow onboarding.
+This configuration option is primary used in continuous integration tests.
+
+**Default:** `false`
+
+| influxd flag                   | Environment variable                 | Configuration key            |
+|:------------                   |:--------------------                 |:-----------------            |
+| `--testing-always-allow-setup` | `INFLUXD_TESTING_ALWAYS_ALLOW_SETUP` | `testing-always-allow-setup` |
+
+###### influxd flag
+```sh
+influxd --testing-always-allow-setup
+```
+
+###### Environment variable
+```sh
+export INFLUXD_TESTING_ALWAYS_ALLOW_SETUP=true
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+testing-always-allow-setup: true
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+testing-always-allow-setup = true
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "testing-always-allow-setup": true
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### tls-cert
+Path to TLS certificate file.
+Requires the [`tls-key`](#tls-key) to be set.
+
+_For more information, see [Enable TLS encryption](/influxdb/v2.2/security/enable-tls/)._
+
+| influxd flag | Environment variable | Configuration key |
+|:------------ |:-------------------- |:----------------- |
+| `--tls-cert` | `INFLUXD_TLS_CERT`   | `tls-cert`        |
+
+###### influxd flag
+```sh
+influxd --tls-cert=/path/to/influxdb.crt
+```
+
+###### Environment variable
+```sh
+export INFLUXD_TLS_CERT=/path/to/influxdb.crt
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+tls-cert: /path/to/influxdb.crt
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+tls-cert = "/path/to/influxdb.crt"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "tls-cert": "/path/to/influxdb.crt"
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### tls-key
+Path to TLS key file.
+Requires the [`tls-cert`](#tls-cert) to be set.
+
+_For more information, see [Enable TLS encryption](/influxdb/v2.2/security/enable-tls/)._
+
+| influxd flag | Environment variable | Configuration key |
+|:------------ |:-------------------- |:----------------- |
+| `--tls-key` | `INFLUXD_TLS_KEY`   | `tls-key`        |
+
+###### influxd flag
+```sh
+influxd --tls-key=/path/to/influxdb.key
+```
+
+###### Environment variable
+```sh
+export INFLUXD_TLS_KEY=/path/to/influxdb.key
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+tls-key: /path/to/influxdb.key
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+tls-key = "/path/to/influxdb.key"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "tls-key": "/path/to/influxdb.key"
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### tls-min-version
+Minimum accepted TLS version.
+
+**Default:** `1.2`
+
+| influxd flag        | Environment variable      | Configuration key |
+|:------------        |:--------------------      |:----------------- |
+| `--tls-min-version` | `INFLUXD_TLS_MIN_VERSION` | `tls-min-version` |
+
+###### influxd flag
+```sh
+influxd --tls-min-version=1.2
+```
+
+###### Environment variable
+```sh
+export INFLUXD_TLS_MIN_VERSION=1.2
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+tls-min-version: "1.2"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+tls-min-version = "1.2"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "tls-min-version": "1.2"
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### tls-strict-ciphers
+Restrict accepted TLS ciphers to:
+
+- ECDHE_RSA_WITH_AES_256_GCM_SHA384
+- ECDHE_RSA_WITH_AES_256_CBC_SHA
+- RSA_WITH_AES_256_GCM_SHA384
+- RSA_WITH_AES_256_CBC_SHA
+
+**Default:** `false`
+
+| influxd flag           | Environment variable         | Configuration key    |
+|:------------           |:--------------------         |:-----------------    |
+| `--tls-strict-ciphers` | `INFLUXD_TLS_STRICT_CIPHERS` | `tls-strict-ciphers` |
+
+###### influxd flag
+```sh
+influxd --tls-strict-ciphers
+```
+
+###### Environment variable
+```sh
+export INFLUXD_TLS_STRICT_CIPHERS=true
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+tls-strict-ciphers: true
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+tls-strict-ciphers = true
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "tls-strict-ciphers": true
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### tracing-type
+Enable tracing in InfluxDB and specifies the tracing type.
+Tracing is disabled by default.
+
+**Options:** `log`, `jaeger`
+
+| influxd flag     | Environment variable   | Configuration key |
+|:------------     |:--------------------   |:----------------- |
+| `--tracing-type` | `INFLUXD_TRACING_TYPE` | `tracing-type`    |
+
+###### influxd flag
+```sh
+influxd --tracing-type=log
+```
+
+###### Environment variable
+```sh
+export INFLUXD_TRACING_TYPE=log
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+tracing-type: log
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+tracing-type = "log"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "tracing-type": "log"
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### ui-disabled
+Disable the InfluxDB user interface (UI).
+The UI is enabled by default.
+
+**Default:** `false`
+
+| influxd flag    | Environment variable  | Configuration key |
+| :-------------- | :-------------------- | :---------------- |
+| `--ui-disabled` | `INFLUXD_UI_DISABLED` | `ui-disabled`     |
+
+###### influxd flag
+```sh
+influxd --ui-disabled
+```
+
+###### Environment variable
+```sh
+export INFLUXD_UI_DISABLED=true
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+ui-disabled: true
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+ui-disabled = true
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "ui-disabled": true
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### vault-addr
+Specifies the address of the Vault server expressed as a URL and port.
+For example: `https://127.0.0.1:8200/`.
+
+| influxd flag   | Environment variable | Configuration key |
+|:------------   |:-------------------- |:----------------- |
+| `--vault-addr` | `VAULT_ADDR`         | `vault-addr`      |
+
+###### influxd flag
+```sh
+influxd --vault-addr=https://127.0.0.1:8200/
+```
+
+###### Environment variable
+```sh
+export VAULT_ADDR=https://127.0.0.1:8200/
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+vault-addr: https://127.0.0.1:8200/
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+vault-addr = "https://127.0.0.1:8200/"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "vault-addr": "https://127.0.0.1:8200/"
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### vault-cacert
+Specifies the path to a PEM-encoded CA certificate file on the local disk.
+This file is used to verify the Vault server's SSL certificate.
+**This setting takes precedence over the [`--vault-capath`](#vault-capath) setting.**
+
+| influxd flag     | Environment variable | Configuration key |
+|:------------     |:-------------------- |:----------------- |
+| `--vault-cacert` | `VAULT_CACERT`       | `vault-cacert`    |
+
+###### influxd flag
+```sh
+influxd  --vault-cacert=/path/to/ca.pem
+```
+
+###### Environment variable
+```sh
+export VAULT_CACERT=/path/to/ca.pem
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+vault-cacert: /path/to/ca.pem
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+vault-cacert = "/path/to/ca.pem"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "vault-cacert": "/path/to/ca.pem"
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### vault-capath
+Specifies the path to a directory of PEM-encoded CA certificate files on the local disk.
+These certificates are used to verify the Vault server's SSL certificate.
+
+| influxd flag     | Environment variable | Configuration key |
+|:------------     |:-------------------- |:----------------- |
+| `--vault-capath` | `VAULT_CAPATH`       | `vault-capath`    |
+
+###### influxd flag
+```sh
+influxd --vault-capath=/path/to/certs/
+```
+
+###### Environment variable
+```sh
+export VAULT_CAPATH=/path/to/certs/
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+vault-capath: /path/to/certs/
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+vault-capath = "/path/to/certs/"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "vault-capath": "/path/to/certs/"
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### vault-client-cert
+Specifies the path to a PEM-encoded client certificate on the local disk.
+This file is used for TLS communication with the Vault server.
+
+| influxd flag          | Environment variable | Configuration key   |
+|:------------          |:-------------------- |:-----------------   |
+| `--vault-client-cert` | `VAULT_CLIENT_CERT`  | `vault-client-cert` |
+
+###### influxd flag
+```sh
+influxd --vault-client-cert=/path/to/client_cert.pem
+```
+
+###### Environment variable
+```sh
+export VAULT_CLIENT_CERT=/path/to/client_cert.pem
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+vault-client-cert: /path/to/client_cert.pem
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+vault-client-cert = "/path/to/client_cert.pem"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "vault-client-cert": "/path/to/client_cert.pem"
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### vault-client-key
+Specifies the path to an unencrypted, PEM-encoded private key on disk which
+corresponds to the matching client certificate.
+
+| influxd flag          | Environment variable | Configuration key   |
+|:------------          |:-------------------- |:-----------------   |
+| `--vault-client-key` | `VAULT_CLIENT_KEY`  | `vault-client-key` |
+
+###### influxd flag
+```sh
+influxd --vault-client-key=/path/to/private_key.pem
+```
+
+###### Environment variable
+```sh
+export VAULT_CLIENT_KEY=/path/to/private_key.pem
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+vault-client-key: /path/to/private_key.pem
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+vault-client-key = "/path/to/private_key.pem"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "vault-client-key": "/path/to/private_key.pem"
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### vault-max-retries
+Specifies the maximum number of retries when encountering a 5xx error code.
+The default is 2 (for three attempts in total). Set this to 0 or less to disable retrying.
+
+**Default:** `2`  
+
+| influxd flag          | Environment variable | Configuration key   |
+|:------------          |:-------------------- |:-----------------   |
+| `--vault-max-retries` | `VAULT_MAX_RETRIES`  | `vault-max-retries` |
+
+###### influxd flag
+```sh
+influxd --vault-max-retries=2
+```
+
+###### Environment variable
+```sh
+export VAULT_MAX_RETRIES=2
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+vault-max-retries: 2
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+vault-max-retries = 2
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "vault-max-retries": 2
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### vault-client-timeout
+Specifies the Vault client timeout.
+
+**Default:** `60s`  
+
+| influxd flag             | Environment variable   | Configuration key      |
+|:------------             |:--------------------   |:-----------------      |
+| `--vault-client-timeout` | `VAULT_CLIENT_TIMEOUT` | `vault-client-timeout` |
+
+###### influxd flag
+```sh
+influxd --vault-client-timeout=60s
+```
+
+###### Environment variable
+```sh
+export VAULT_CLIENT_TIMEOUT=60s
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+vault-client-timeout: 60s
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+vault-client-timeout = "60s"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "vault-client-timeout": "60s"
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### vault-skip-verify
+Skip certificate verification when communicating with Vault.
+_Setting this variable voids [Vault's security model](https://www.vaultproject.io/docs/internals/security.html)
+and is **not recommended**._
+
+**Default:** `false`
+
+| influxd flag          | Environment variable | Configuration key   |
+|:------------          |:-------------------- |:-----------------   |
+| `--vault-skip-verify` | `VAULT_SKIP_VERIFY`  | `vault-skip-verify` |
+
+###### influxd flag
+```sh
+influxd --vault-skip-verify
+```
+
+###### Environment variable
+```sh
+export VAULT_SKIP_VERIFY=true
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+vault-skip-verify: true
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+vault-skip-verify = true
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "vault-skip-verify": true
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### vault-tls-server-name
+Specifies the name to use as the Server Name Indication (SNI) host when connecting via TLS.
+
+| influxd flag              | Environment variable    | Configuration key       |
+|:------------              |:--------------------    |:-----------------       |
+| `--vault-tls-server-name` | `VAULT_TLS_SERVER_NAME` | `vault-tls-server-name` |
+
+###### influxd flag
+```sh
+influxd --vault-tls-server-name=secure.example.com
+```
+
+###### Environment variable
+```sh
+export VAULT_TLS_SERVER_NAME=secure.example.com
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+vault-tls-server-name: secure.example.com
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+vault-tls-server-name = "secure.example.com"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "vault-tls-server-name": "secure.example.com"
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+---
+
+### vault-token
+Specifies the Vault token use when authenticating with Vault.
+
+| influxd flag    | Environment variable | Configuration key |
+|:------------    |:-------------------- |:----------------- |
+| `--vault-token` | `VAULT_TOKEN`        | `vault-token`     |
+
+###### influxd flag
+```sh
+influxd --vault-token=exAmple-t0ken-958a-f490-c7fd0eda5e9e
+```
+
+###### Environment variable
+```sh
+export VAULT_TOKEN=exAmple-t0ken-958a-f490-c7fd0eda5e9e
+```
+
+###### Configuration file
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[YAML](#)
+[TOML](#)
+[JSON](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```yml
+vault-token: exAmple-t0ken-958a-f490-c7fd0eda5e9e
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```toml
+vault-token = "exAmple-t0ken-958a-f490-c7fd0eda5e9e"
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```json
+{
+  "vault-token": "exAmple-t0ken-958a-f490-c7fd0eda5e9e"
+}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
diff --git a/content/influxdb/v2.2/reference/contributing/_index.md b/content/influxdb/v2.2/reference/contributing/_index.md
new file mode 100644
index 000000000..8c75f8e13
--- /dev/null
+++ b/content/influxdb/v2.2/reference/contributing/_index.md
@@ -0,0 +1,26 @@
+---
+title: Contribute to InfluxDB OSS
+description: Find important information about what's included in new versions of InfluxData products.
+menu:
+  influxdb_2_2_ref:
+    name: Contribute to InfluxDB
+    weight: 10
+---
+
+To contribute to the InfluxDB OSS project, complete the following steps:
+
+1. [Sign the InfluxData Contributor License Agreement (CLA)](#sign-influxdata-contributor-license-agreement-cla).
+2. [Review contribution guidelines](#review-contribution-guidelines).
+3. [Review the InfluxDB open source license](#review-open-source-license).
+
+## Sign InfluxData Contributor License Agreement (CLA)
+
+Before contributing to the InfluxDB OSS project, you must complete and sign the [InfluxData Contributor License Agreement (CLA)](https://www.influxdata.com/legal/cla/), available on the InfluxData website.
+
+## Review contribution guidelines
+
+To learn how you can contribute to the InfluxDB OSS project, see our [Contributing guidelines](https://github.com/influxdata/influxdb/blob/master/CONTRIBUTING.md) in the GitHub repository.
+
+## Review open source license
+
+See information about our [open source MIT license for InfluxDB](https://github.com/influxdata/influxdb/blob/master/LICENSE) in GitHub.
diff --git a/content/influxdb/v2.2/reference/glossary.md b/content/influxdb/v2.2/reference/glossary.md
new file mode 100644
index 000000000..02b7b375c
--- /dev/null
+++ b/content/influxdb/v2.2/reference/glossary.md
@@ -0,0 +1,1241 @@
+---
+title: Glossary
+description: >
+  Terms related to InfluxData products and platforms.
+weight: 9
+menu:
+  influxdb_2_2_ref:
+    name: Glossary
+influxdb/v2.2/tags: [glossary]
+---
+
+[A](#a) | [B](#b) | [C](#c) | [D](#d) | [E](#e) | [F](#f) | [G](#g) | [H](#h) | [I](#i) | [J](#j) | [K](#k) | [L](#l) | [M](#m) | [N](#n) | [O](#o) | [P](#p) | [Q](#q) | [R](#r) | [S](#s) | [T](#t) | [U](#u) | [V](#v) | [W](#w) | <span style="opacity:.35;font-weight:500">X</span> | <span style="opacity:.35;font-weight:500">Y</span> | <span style="opacity:.35;font-weight:500">Z</span>
+
+## A
+
+### agent
+
+A background process started by (or on behalf of) a user and typically requires user input.
+
+Telegraf is an agent that requires user input (a configuration file) to gather metrics from declared input plugins and sends metrics to declared output plugins, based on the plugins enabled for a configuration.
+
+Related entries: [input plugin](#input-plugin), [output plugin](#output-plugin), [daemon](#daemon)
+
+### aggregator plugin
+
+Receives metrics from input plugins, creates aggregate metrics, and then passes aggregate metrics to configured output plugins.
+
+Related entries: [input plugin](#input-plugin), [output plugin](#output-plugin), [processor plugin](#processor-plugin)
+
+### aggregate
+
+A function that returns an aggregated value across a set of points.
+For a list of available aggregation functions, see [Flux aggregate functions](/{{< latest "flux" >}}/function-types#aggregates).
+
+Related entries: [function](#function), [selector](#selector), [transformation](#transformation)
+
+## B
+
+### bar graph
+
+A visual representation in the InfluxDB user interface used to compare variables (bars) and plot categorical data.
+A bar graph has spaces between bars, can be sorted in any order, and bars in the graph typically have the same width.
+
+Related entries: [histogram](#histogram)
+
+### batch
+
+A collection of points in line protocol format, separated by newlines (`0x0A`).
+Submitting a batch of points using a single HTTP request to the write endpoints drastically increases performance by reducing the HTTP overhead.
+InfluxData typically recommends batch sizes of 5,000-10,000 points.
+In some use cases, performance may improve with significantly smaller or larger batches.
+
+Related entries: [line protocol](/influxdb/v2.2/reference/syntax/line-protocol/), [point](#point)
+
+### batch size
+
+The number of lines or individual data points in a line protocol batch.
+The Telegraf agent sends metrics to output plugins in batches rather than individually.
+Batch size controls the size of each write batch that Telegraf sends to the output plugins.
+
+Related entries: [output plugin](#output-plugin)
+
+### bin
+
+In a cumulative histogram, a bin includes all data points less than or equal to a specified upper bound.
+In a normal histogram, a bin includes all data points between the upper and lower bounds.
+
+### block
+
+In Flux, a block is a possibly empty sequence of statements within matching braces (`{ }`).
+Two types of blocks exist in Flux:
+
+- Explicit blocks in the source code, for example:
+
+  ```
+  Block         = "{" StatementList "}
+  StatementList = { Statement }
+  ```
+
+- Implicit blocks, including:
+
+  - Universe: Encompasses all Flux source text.
+  - Package: Each package includes a package block that contains Flux source text for the package.
+  - File: Each file has a file block containing Flux source text in the file.
+  - Function: Each function literal has a function block with Flux source text (even if not explicitly declared).
+
+Related entries: [implicit block](#implicit-block), [explicit block](#explicit-block)
+
+### boolean
+
+A data type with two possible values: true or false.
+By convention, you can express `true` as the integer `1` and false as the integer `0` (zero).
+In [annotated CSV](/influxdb/v2.2/reference/syntax/annotated-csv/), columns that contain
+boolean values are annotated with the `boolean` datatype.
+
+### bucket
+
+A bucket is a named location where time series data is stored.
+All buckets have a [retention period](#retention-period).
+A bucket belongs to an organization.
+
+
+### bucket schema
+
+In InfluxDB Cloud, an explicit bucket schema lets you strictly enforce the data that can be written into one or more measurements in a bucket by defining the column names, tags, fields, and data types allowed for each measurement. By default, buckets in InfluxDB {{< current-version >}} have an `implicit` schema that lets you write data without restrictions on columns, fields, or data types.
+
+Learn how to [manage bucket schemas](/influxdb/cloud/organizations/buckets/bucket-schema/) in InfluxDB Cloud.
+
+Related entries: [data type](#data-type), [field](#field), [measurement](#measurement)
+
+## C
+
+### check
+
+Checks are part of queries used in monitoring to read input data and assign a [status](#check-status) (`_level`) based on specified conditions.
+For example:
+
+```
+monitor.check(
+  crit: (r) => r._value > 90.0,
+  warn: (r) => r._value > 80.0,
+  info: (r) => r._value > 60.0,
+  ok:   (r) => r._value <= 20.0,
+  messageFn: (r) => "The current level is ${r._level}",
+)
+```
+
+This check gives rows with a `_value` greater than 90.0 a crit `_level`; rows greater than 80.0 get a warn `_level`, and so on.
+
+Learn how to [create a check](/influxdb/v2.2/monitor-alert/checks/create/).
+
+Related entries: [check status](#check-status), [notification rule](#notification-rule), [notification endpoint](#notification-endpoint)
+
+### check status
+
+A [check](#check) gets one of the following statuses (`_level`): `crit`, `info`, `warn`, or `ok`.
+Check statuses are written to a status measurement in the `_monitoring` bucket.
+
+Related entries: [check](#check), [notification rule](#notification-rule), [notification endpoint](#notification-endpoint)
+
+### CSV
+
+Comma-separated values (CSV) delimits text between commas to separate values.
+A CSV file stores tabular data (numbers and text) in plain text.
+Each line of the file is a data record.
+Each record consists of one or more fields, separated by commas.
+CSV file format is not fully standardized.
+
+InfluxData uses annotated CSV (comma-separated values) format to encode HTTP responses and results returned to the Flux csv.from() function.
+For more detail, see [Annotated CSV](/influxdb/v2.2/reference/syntax/annotated-csv/).
+
+<!-- enterprise
+### cardinality
+
+Cardinality is the number of unique series in a bucket or database as a whole.
+
+### cluster
+
+An InfluxDB cluster includes meta nodes, data nodes, and the InfluxDB Enterprise web server. In a cluster, meta nodes must communicate with each other and data nodes must communicate with each other and with meta nodes.
+-->
+
+### co-monitoring dashboard
+
+The prebuilt co-monitoring dashboard displays details of your instance based on metrics from Telegraf, allowing you to monitor overall performance.
+
+### collect
+
+Collect and write time series data to InfluxDB using line protocol, Telegraf or InfluxDB scrapers, the InfluxDB v2 API, influx command line interface (CLI),the InfluxDB user interface (UI), and client libraries.
+
+### collection interval
+
+The default global interval for collecting data from each Telegraf input plugin.
+The collection interval can be overridden by each individual input plugin's configuration.
+
+Related entries: [input plugin](#input-plugin)
+
+<!--Likely configurable for scrapers in the future.-->
+
+### collection jitter
+
+Collection jitter prevents every input plugin from collecting metrics simultaneously, which can have a measurable effect on the system.
+For each collection interval, every Telegraf input plugin will sleep for a random time between zero and the collection jitter before collecting the metrics.
+
+Related entries: [collection interval](#collection-interval), [input plugin](#input-plugin)
+
+### column
+
+InfluxDB data is stored in tables within rows and columns.
+Columns store tag sets (indexed) and fields sets.
+The only required column is _time_, which stores timestamps and is included in all InfluxDB tables.
+
+### comment
+
+Use comments with Flux statements to describe your functions.
+
+### common log format (CLF)
+
+A standardized text file format used by the InfluxDB web server to create log entries when generating server log files.
+
+### compaction
+
+Compressing time series data to optimize disk usage.
+
+### continuous query (CQ)
+
+Continuous queries are the predecessor to tasks in InfluxDB {{< current-version >}}.
+Continuous queries run automatically and periodically on a database.
+
+Related entries: [function](#function)
+
+## D
+
+### daemon
+
+A background process that runs without user input.
+
+### dashboard
+
+InfluxDB dashboards visualize time series data.
+Use dashboards to query and graph data.
+
+### dashboard variable
+
+Dashboard template variables define components of a cell query.
+Dashboard variables make is easier to interact with and explore your databoard data.
+Use the InfluxDB user interface (UI) to add predefined template variables or customize your own template variables.
+
+### Data Explorer
+
+Use the Data Explorer in the InfluxDB user interface (UI) to view, add, or delete variables and functions manually or using the Script Editor.
+
+### data model
+
+A data model organizes elements of data and standardizes how they relate to one another and to properties of the real world entities.
+
+Flux uses a data model built from basic data types: tables, records, columns and streams.
+
+<!-- enterprise ### data node
+
+Data nodes allow a system to replicate data across multiple nodes.
+
+For high availability in InfluxDB, a cluster must have at least two data nodes. The number of data nodes in a cluster must be the same as the highest replication factor. A replication factor greater than two adds fault tolerance and query capacity in a cluster.
+
+Data node sizes will depend on your needs. The Amazon EC2 m4.large or m4.xlarge are good starting points.
+
+Related entries: [data service](#data-service), [replication factor](#replication-factor)
+-->
+
+### data service
+
+Stores time series data and handles writes and queries.
+
+### data source
+
+A source of data that InfluxDB collects or queries data from.
+Examples include InfluxDB buckets, Prometheus, Postgres, MySQL, and InfluxDB clients.
+
+Related entries: [bucket](#bucket)
+
+### data type
+
+A data type is defined by the values it can take, the programming language used, or the operations that can be performed on it.
+
+InfluxDB supports the following data types:
+| Data type        | Alias/annotation   |
+| :--------------- | :----------------- |
+| string           |                    |
+| boolean          |                    |
+| float            | double             |
+| integer          | int, long          |
+| unsigned integer | uint, unsignedLong |
+| time             | dateTime           |
+
+For more information about different data types, see:
+- [annotated CSV](/influxdb/v2.2/reference/syntax/annotated-csv/)
+- [extended annotated CSV](/influxdb/cloud/reference/syntax/annotated-csv/extended/#datatype)
+- [line protocol](/influxdb/v2.2/reference/syntax/line-protocol/#data-types-and-format)
+- [InfluxQL](/influxdb/v1.8/query_language/spec/#literals)
+- [Flux](/influxdb/v2.2/reference/flux/language/types/)
+- [InfluxDB](/influxdb/v2.2/reference/syntax/line-protocol/#data-types-and-format)
+
+### database
+
+In InfluxDB {{< current-version >}}, a database represents the InfluxDB instance as a whole.
+
+Related entries: [continuous query](#continuous-query-cq), <!-- [retention policy](#retention-policy-rp),--> [user](#user)
+
+### date-time
+
+InfluxDB stores the date-time format for each data point in a timestamp with nanosecond-precision Unix time.
+Specifying a timestamp is options.
+If a timestamp isn't specified for a data point, InfluxDB uses the server’s local nanosecond timestamp in UTC.
+
+### downsample
+
+Aggregating high resolution data into lower resolution data to preserve disk space.
+
+### duration
+
+A data type that represents a duration of time (1s, 1m, 1h, 1d).
+Retention policies are set using durations.
+Data older than the duration is automatically dropped from the database.
+
+<!-- Related entries: [retention policy](#retention-policy-rp) -->
+
+## E
+
+### event
+
+Metrics gathered at irregular time intervals.
+
+### explicit block
+
+In Flux, a an explicit block is a possibly empty sequence of statements within matching braces (`{ }`) that is defined in the source code, for example:
+
+```
+Block         = "{" StatementList "}
+StatementList = { Statement }
+```
+
+Related entries: [implicit block](#implicit-block), [block](#block)
+
+### expression
+
+A combination of one or more constants, variables, operators, and functions.
+
+## F
+
+### field
+
+The key-value pair in InfluxDB's data structure that records metadata and the actual data value.
+Fields are required in InfluxDB's data structure and they are not indexed - queries on field values scan all points that match the specified time range and, as a result, are not performant relative to tags.
+
+*Query tip:* Compare fields to tags; tags are indexed.
+
+Related entries: [field key](#field-key), [field set](#field-set), [field value](#field-value), [tag](#tag)
+
+### field key
+
+The key of the key-value pair.
+Field keys are strings and they store metadata.
+
+Related entries: [field](#field), [field set](#field-set), [field value](#field-value), [tag key](#tag-key)
+
+### field set
+
+The collection of field keys and field values on a point.
+
+Related entries: [field](#field), [field key](#field-key), [field value](#field-value), [point](#point)
+
+### field value
+
+The value of a key-value pair.
+Field values are the actual data; they can be strings, floats, integers, or booleans.
+A field value is always associated with a timestamp.
+
+Field values are not indexed - queries on field values scan all points that match the specified time range and, as a result, are not performant.
+
+*Query tip:* Compare field values to tag values; tag values are indexed.
+
+Related entries: [field](#field), [field key](#field-key), [field set](#field-set), [tag value](#tag-value), [timestamp](#timestamp)
+
+### file block
+
+A file block is a fixed-length chunk of data read into memory when requested by an application.
+
+Related entries: [block](#block)
+
+### float
+
+A real number written with a decimal point dividing the integer and fractional parts (`1.0`, `3.14`, `-20.1`).
+InfluxDB supports 64-bit float values.
+In [annotated CSV](/influxdb/v2.2/reference/syntax/annotated-csv/), columns that contain
+float values are annotated with the `double` datatype.
+
+### flush interval
+
+The global interval for flushing data from each Telegraf output plugin to its destination.
+This value should not be set lower than the collection interval.
+
+Related entries: [collection interval](#collection-interval), [flush jitter](#flush-jitter), [output plugin](#output-plugin)
+
+### flush jitter
+
+Flush jitter prevents every Telegraf output plugin from sending writes simultaneously, which can overwhelm some data sinks.
+Each flush interval, every Telegraf output plugin will sleep for a random time between zero and the flush jitter before emitting metrics.
+Flush jitter smooths out write spikes when running a large number of Telegraf instances.
+
+Related entries: [flush interval](#flush-interval), [output plugin](#output-plugin)
+
+### Flux
+
+A lightweight scripting language for querying databases (like InfluxDB) and working with data.
+
+### function
+
+Flux functions aggregate, select, and transform time series data.
+For a complete list of Flux functions, see [Flux functions](/{{< latest "flux" >}}/stdlib/all-functions/).
+
+Related entries: [aggregate](#aggregate), [selector](#selector), [transformation](#transformation)
+
+### function block
+
+In Flux, each file has a file block containing all Flux source text in that file.
+Each function literal has its own function block even if not explicitly declared.
+
+## G
+
+### gauge
+
+ A type of visualization that displays the single most recent value for a time series.
+A gauge typically displays one or more measures from a single row, and is not designed to display multiple rows of data.
+Elements include a range, major and minor tick marks (within the range), and a pointer (needle) indicating the single most recent value.
+
+### graph
+
+A diagram that visually depicts the relation between variable quantities measured along specified axes.
+
+### group key
+Group keys determine the schema and contents of tables in Flux output.
+A group key is a list of columns for which every row in the table has the same value.
+Columns with unique values in each row are not part of the group key.
+
+### gzip
+
+gzip is a type of data compression that compress chunks of data, which is restored by unzipping compressed gzip files.
+The gzip file extension is `.gz`.
+
+## H
+
+<!--enterprise
+### Hinted Handoff (HH)
+
+Offers full write availability on an InfluxDB cluster. Hinted handoff improves response consistency after temporary outages such as network failures.
+
+-->
+
+### histogram
+
+A visual representation of statistical information that uses rectangles to show the frequency of data items in successive, equal intervals or bins.
+
+## I
+
+### identifier
+
+Identifiers are tokens that refer to task names, bucket names, field keys,
+measurement names, tag keys, and user names.
+For examples and rules, see [Flux language lexical elements](/{{< latest "flux" >}}/spec/lexical-elements/#identifiers).
+
+Related entries:
+[bucket](#bucket)
+[field key](#field-key),
+[measurement](#measurement),
+<!-- [retention policy](#retention-policy-rp), -->
+[tag key](#tag-key),
+[user](#user)
+
+### implicit block
+
+In Flux, an implicit block is a possibly empty sequence of statements within matching braces ({ }) that includes the following types:
+
+  - Universe: Encompasses all Flux source text.
+  - Package: Each package includes a package block that contains Flux source text for the package.
+  - File: Each file has a file block containing Flux source text in the file.
+  - Function: Each function literal has a function block with Flux source text (even if not explicitly declared).
+
+Related entries: [explict block](#explicit-block), [block](#block)
+
+### influx
+
+`influx` is a command line interface (CLI) that interacts with the InfluxDB daemon (influxd).
+
+### influxd
+
+`influxd` is the InfluxDB daemon that runs the InfluxDB server and other required processes.
+
+### InfluxDB
+
+An open-source time series database (TSDB) developed by InfluxData.
+Written in Go and optimized for fast, high-availability storage and retrieval of time series data in fields such as operations monitoring, application metrics, Internet of Things sensor data, and real-time analytics.
+
+### InfluxDB UI
+
+The graphical web interface provided by InfluxDB for visualizing data and managing InfluxDB functionality.
+
+### InfluxQL
+
+The SQL-like query language used to query data in InfluxDB 1.x.
+The prefered method for querying data in InfluxDB {{< current-version >}} is the [Flux](#flux) language.
+
+### input plugin
+
+Telegraf input plugins actively gather metrics and deliver them to the core agent, where aggregator, processor, and output plugins can operate on the metrics.
+In order to activate an input plugin, it needs to be enabled and configured in Telegraf's configuration file.
+
+Related entries: [aggregator plugin](#aggregator-plugin), [collection interval](#collection-interval), [output plugin](#output-plugin), [processor plugin](#processor-plugin)
+
+### instance
+
+An entity comprising data on a server (or virtual server in cloud computing).
+<!-- An instance in an InfluxDB Enterprise cluster may scale across multiple servers or nodes in a network. -->
+
+### integer
+
+A whole number that is positive, negative, or zero (`0`, `-5`, `143`).
+InfluxDB supports 64-bit integers (minimum: `-9223372036854775808`, maximum: `9223372036854775807`).
+In [annotated CSV](/influxdb/v2.2/reference/syntax/annotated-csv/), columns that contain
+integers are annotated with the `long` datatype.
+
+Related entries: [unsigned integer](#unsigned-integer)
+
+## J
+
+### JWT
+
+Typically, JSON web tokens (JWT) are used to authenticate users between an identity provider and a service provider.
+A server can generate a JWT to assert any business processes.
+For example, an "admin" token sent to a client can prove the client is logged in as admin.
+Tokens are signed by one party's private key (typically, the server).
+Private keys are used by both parties to verify that a token is legitimate.
+
+JWT uses an open standard specified in [RFC 7519](https://tools.ietf.org/html/rfc7519).
+
+### Jaeger
+
+Open source tracing used in distributed systems to monitor and troubleshoot transactions.
+
+### JSON
+
+JavaScript Object Notation (JSON) is an open-standard file format that uses human-readable text to transmit data objects consisting of attribute–value pairs and array data types.
+
+## K
+
+### keyword
+
+A keyword is reserved by a program because it has special meaning.
+Every programming language has a set of keywords (reserved names) that cannot be used as an identifier.
+
+See a list of [Flux keywords](/{{< latest "flux" >}}/spec/lexical-elements/#keywords).
+
+## L
+
+### literal
+
+A literal is value in an expression, a number, character, string, function, record, or array.
+Literal values are interpreted as defined.
+
+See examples of [Flux literals](/{{< latest "flux" >}}/spec/expressions/#examples-of-function-literals).
+
+<!-- enterprise
+### load balancing
+
+Improves workload distribution across multiple computing resources in a network. Load balancing optimizes resource use, maximizes throughput, minimizes response time, and avoids overloading a single resource. Using multiple components with load balancing instead of a single component may increase reliability and availability. If requests to any server in a network increase, requests are forwarded to another server with more capacity. Load balancing can also refer to the communications channels themselves.
+
+-->
+
+### logs
+
+Logs record information.
+Event logs describe system events and activity that help to describe and diagnose problems.
+Transaction logs describe changes to stored data that help recover data if a database crashes or other errors occur.
+
+The InfluxDB {{< current-version >}} user interface (UI) can be used to view log history and data.
+
+### Line protocol (LP)
+
+The text based format for writing points to InfluxDB.
+See [line protocol](/influxdb/v2.2/reference/syntax/line-protocol/).
+
+## M
+
+### measurement
+
+The part of InfluxDB's structure that describes the data stored in the associated fields.
+Measurements are strings.
+
+Related entries: [field](#field), [series](#series)
+
+### member
+
+A user in an organization.
+<!--or a node in a cluster. -->
+
+<!--### meta node - in development
+
+A node that runs the meta service.
+
+For high availability, installations must have three meta nodes.
+Meta nodes can be very modestly sized instances like an EC2 t2.micro or even a
+nano.
+For additional fault tolerance, installations may use five meta nodes. The
+number of meta nodes must be an odd number.
+
+Related entries: [meta service](#meta-service)
+
+### meta service
+
+The consistent data store that keeps state about the cluster, including which
+servers, buckets, users, tasks, subscriptions, and blocks of time exist.
+
+Related entries: [meta node](#meta-node)
+
+### metastore
+
+Contains internal information about the status of the system.
+The metastore contains the user information, buckets, shard metadata, tasks, and subscriptions.
+
+Related entries: [bucket](#bucket), [retention policy](#retention-policy-rp), [user](#user)
+-->
+
+### metric
+
+Data tracked over time.
+
+### metric buffer
+
+The metric buffer caches individual metrics when writes are failing for an Telegraf output plugin.
+Telegraf will attempt to flush the buffer upon a successful write to the output.
+The oldest metrics are dropped first when this buffer fills.
+
+Related entries: [output plugin](#output-plugin)
+
+### missing values
+
+Denoted by a null value.
+Identifies missing information, which may be useful to include in an error message.
+
+The Flux data model includes [Missing values (null)](/{{< latest "flux" >}}/spec/data-model/#missing-values-null).
+
+## N
+
+### node
+
+An independent `influxd` process.
+
+Related entries: [server](#server)
+
+### notification endpoint
+
+ The notification endpoint specifies the Slack or PagerDuty endpoint to send a notification and contains configuration details for connecting to the endpoint.
+Learn how to [create a notification endpoint](/influxdb/v2.2/monitor-alert/notification-endpoints/create).
+
+Related entries: [check](#check), [notification rule](#notification-rule)
+
+### notification rule
+
+A notification rule specifies a status level (and tags) to alert on, the notification message to send for the specified status level (or change in status level), and the interval or schedule you want to check the status level (and tags).
+If conditions are met, the notification rule sends a message to the [notification endpoint](#notification-endpoint) and stores a receipt in a notification measurement in the `_monitoring` bucket.
+For example, a notification rule may specify a message to send to a Slack endpoint when a status level is critical (`crit`).
+
+Learn how to [create a notification rule](/influxdb/v2.2/monitor-alert/notification-rules/create).
+
+Related entries: [check](#check), [notification endpoint](#notification-endpoint)
+
+### now()
+
+The local server's nanosecond timestamp.
+
+### null
+
+A data type that represents a missing or unknown value.
+Denoted by the null value.
+
+## O
+
+### operator
+
+A symbol that usually represents an action or process.
+For example: `+`, `-`, `>`.
+
+### operand
+
+The object or value on either side of an operator.
+
+### option
+
+Represents a storage location for any value of a specified type.
+Mutable, can hold different values during its lifetime.
+
+See built-in Flux [options](/{{< latest "flux" >}}/spec/options/).
+
+### option assignment
+
+An option assignment binds an identifier to an option.
+
+Learn about the [option assignment](/{{< latest "flux" >}}/spec/assignment-scope/#option-assignment) in Flux.
+
+### organization
+
+A workspace for a group of users.
+All dashboards, tasks, buckets, members, and so on, belong to an organization.
+
+### output plugin
+
+Telegraf output plugins deliver metrics to their configured destination.
+To activate an output plugin, enable and configure the plugin in Telegraf's configuration file.
+
+Related entries: [aggregator plugin](#aggregator-plugin), [flush interval](#flush-interval), [input plugin](#input-plugin), [processor plugin](#processor-plugin)
+
+## P
+
+### parameter
+
+A key-value pair used to pass information to functions.
+
+### pipe
+
+Method for passing information from one process to another.
+For example, an output parameter from one process is input to another process.
+Information passed through a pipe is retained until the receiving process reads the information.
+
+### pipe-forward operator
+
+An operator (`|>`) used in Flux to chain operations together.
+Specifies the output from a function is input to next function.
+
+### point
+
+In InfluxDB, a point represents a single data record, similar to a row in a SQL database table.
+Each point:
+
+- has a measurement, a tag set, a field key, a field value, and a timestamp;
+- is uniquely identified by its series and timestamp.
+
+In a series, each point has a unique timestamp.
+If you write a point to a series with a timestamp that matches an existing point, the field set becomes a union of the old and new field set, where any ties go to the new field set.
+
+Related entries: [measurement](#measurement), [tag set](#tag-set), [field set](#field-set), [timestamp](#timestamp)
+
+### precision
+
+The precision configuration setting determines the timestamp precision retained for input data points.
+All incoming timestamps are truncated to the specified precision.
+Valid precisions are `ns`, `us` or `µs`, `ms`, and `s`.
+
+In Telegraf, truncated timestamps are padded with zeros to create a nanosecond timestamp.
+Telegraf output plugins emit timestamps in nanoseconds.
+For example, if the precision is set to `ms`, the nanosecond epoch timestamp `1480000000123456789` is truncated to `1480000000123` in millisecond precision and padded with zeroes to make a new, less precise nanosecond timestamp of `1480000000123000000`.
+Telegraf output plugins do not alter the timestamp further.
+The precision setting is ignored for service input plugins.
+
+Related entries:  [aggregator plugin](#aggregator-plugin), [input plugin](#input-plugin), [output plugin](#output-plugin), [processor plugin](#processor-plugin), [service input plugin](#service-input-plugin)
+
+### predicate expression
+
+A predicate expression compares two values and returns `true` or `false` based on
+the relationship between the two values.
+A predicate expression is comprised of a left operand, a comparison operator, and a right operand.
+
+### predicate function
+A Flux predicate function is an anonymous function that returns `true` or `false`
+based on one or more [predicate expressions](#predicate-expression).
+
+###### Example predicate function
+```js
+(r) => r.foo == "bar" and r.baz != "quz"
+```
+
+### process
+
+A set of predetermined rules.
+A process can refer to instructions being executed by the computer processor or refer to the act of manipulating data.
+
+In Flux, you can process data with [InfluxDB tasks](/influxdb/v2.2/process-data/get-started/).
+
+### processor plugin
+
+Telegraf processor plugins transform, decorate, and filter metrics collected by input plugins, passing the transformed metrics to the output plugins.
+
+Related entries: [aggregator plugin](#aggregator-plugin), [input plugin](#input-plugin), [output plugin](#output-plugin)
+
+### Prometheus format
+
+A simple text-based format for exposing metrics and ingesting them into Prometheus or InfluxDB using InfluxDB scrapers.
+
+Collect data from any accessible endpoint that provides data in the [Prometheus exposition format](https://prometheus.io/docs/instrumenting/exposition_formats/).
+
+## Q
+
+### query
+
+A Flux script that returns time series data, including [tags](#tag) and [timestamps](#timestamp).
+
+See [Query data in InfluxDB](/influxdb/v2.2/query-data/).
+
+## R
+
+### REPL
+
+A Read-Eval-Print Loop (REPL) is an interactive programming environment where you type a command and immediately see the result.
+See [Flux REPL](/influxdb/v2.2/tools/repl/) for information on building and using the REPL.
+
+### record
+
+A tuple of named values represented using a record type.
+
+### regular expressions
+
+Regular expressions (regex or regexp) are patterns used to match character combinations in strings.
+
+### rejected points
+
+In a batch of data, points that InfluxDB couldn't write to a bucket.
+Field type conflicts are a common cause of rejected points.
+
+### retention period
+The [duration](#duration) of time that a bucket retains data.
+InfluxDB drops points with timestamps older than their bucket's retention period.
+The minimum retention period is **one hour**.
+
+Related entries: [bucket](#bucket), [shard group duration](#shard-group-duration)
+
+<!--### replication factor
+
+The attribute of the retention policy that determines how many copies of the data are stored in the cluster. InfluxDB replicates data across N data nodes, where N is the replication factor.
+
+To maintain data availability for queries, the replication factor should be less than or equal to the number of data nodes in the cluster:
+
+Data is fully available when the replication factor is greater than the number of unavailable data nodes.
+Data may be unavailable when the replication factor is less than the number of unavailable data nodes.
+Any replication factor greater than two gives you additional fault tolerance and query capacity within the cluster.
+-->
+
+### retention policy (RP)
+Retention policy is an InfluxDB 1.x concept that represents the duration of time
+that each data point in the retention policy persists.
+The InfluxDB 2.x equivalent is [retention period](#retention-period).
+For more information about retention policies, see the
+[latest 1.x documentation](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#retention-policy-rp).
+
+Related entries:  [retention period](#retention-period),
+
+### RFC3339 timestamp
+A timestamp that uses the human readable DateTime format proposed in
+[RFC 3339](https://tools.ietf.org/html/rfc3339) (for example: `2020-01-01T00:00:00.00Z`).
+Flux and InfluxDB clients return query results with RFC3339 timestamps.
+
+Related entries: [timestamp](#timestamp), [unix timestamp](#unix-timestamp)
+
+## S
+
+### schema
+
+How data is organized in InfluxDB.
+The fundamentals of the InfluxDB schema are buckets (which include retention policies), series, measurements, tag keys, tag values, and field keys.
+
+Related entries: [bucket](#bucket), [field key](#field-key), [measurement](#measurement), <!--[retention policy](#retention-policy-rp),--> [series](#series), [tag key](#tag-key), [tag value](#tag-value)
+
+### scrape
+
+InfluxDB scrapes data from specified targets at regular intervals and writes the data to an InfluxDB bucket.
+Data can be scraped from any accessible endpoint that provides data in the [Prometheus exposition format](https://prometheus.io/docs/instrumenting/exposition_formats/).
+
+### secret
+Secrets are key-value pairs that contain information you want to control access to, such as API keys, passwords, or certificates.
+
+### selector
+
+A Flux function that returns a single point from the range of specified points.
+See [Flux selector functions](/{{< latest "flux" >}}/stdlib/universe/) for a complete list of available selector functions.
+
+Related entries: [aggregate](#aggregate), [function](#function), [transformation](#transformation)
+
+### series
+
+A collection of data in the InfluxDB data structure that shares a measurement, tag set, and bucket.
+
+Related entries: [field set](#field-set), [measurement](#measurement),<!-- [retention policy](/#retention-policy-rp), --> [tag set](#tag-set)
+
+### series cardinality
+
+The number of unique measurement, tag set, and field key combinations in an InfluxDB bucket.
+
+For example, assume that an InfluxDB bucket has one measurement.
+The single measurement has two tag keys: `email` and `status`.
+If there are three different `email`s, and each email address is associated with two
+different `status`es, the series cardinality for the measurement is 6
+(3 × 2 = 6):
+
+| email                 | status |
+| :-------------------- | :----- |
+| lorr@influxdata.com   | start  |
+| lorr@influxdata.com   | finish |
+| marv@influxdata.com   | start  |
+| marv@influxdata.com   | finish |
+| cliff@influxdata.com  | start  |
+| cliff@influxdata.com  | finish |
+
+In some cases, performing this multiplication may overestimate series cardinality
+because of the presence of dependent tags.
+Dependent tags are scoped by another tag and do not increase series cardinality.
+If we add the tag `firstname` to the example above, the series cardinality
+would not be 18 (3 × 2 × 3 = 18).
+The series cardinality would remain unchanged at 6, as `firstname` is already scoped by the `email` tag:
+
+| email                | status | firstname |
+| :------------------- | :----- | :-------- |
+| lorr@influxdata.com  | start  | lorraine  |
+| lorr@influxdata.com  | finish | lorraine  |
+| marv@influxdata.com  | start  | marvin    |
+| marv@influxdata.com  | finish | marvin    |
+| cliff@influxdata.com | start  | clifford  |
+| cliff@influxdata.com | finish | clifford  |
+
+##### Query for cardinality:
+- **Flux:** [influxdb.cardinality()](/{{< latest "flux" >}}/stdlib/influxdb/cardinality/)
+- **InfluxQL:** [SHOW CARDINALITY](/{{< latest "influxdb" "v1" >}}/query_language/spec/#show-cardinality)
+
+Related entries: [field key](#field-key),[measurement](#measurement), [tag key](#tag-key), [tag set](#tag-set)
+
+### series file
+
+A file created and used by the **InfluxDB OSS storage engine**
+that contains a set of all series keys across the entire database.
+
+### series key
+
+A series key identifies a particular series by measurement, tag set, and field key.
+
+For example:
+
+```
+# measurement, tag set, field key
+h2o_level, location=santa_monica, h2o_feet
+```
+
+Related entries: [series](#series)
+
+### server
+
+A computer, virtual or physical, running InfluxDB.
+<!--is this still valid for {{< current-version >}}: There should only be one InfluxDB process per server. -->
+
+Related entries: [node](#node)
+
+### service input plugin
+
+Telegraf input plugins that run in a passive collection mode while the Telegraf agent is running.
+Service input plugins listen on a socket for known protocol inputs, or apply their own logic to ingested metrics before delivering metrics to the Telegraf agent.
+
+Related entries: [aggregator plugin](#aggregator-plugin), [input plugin](#input-plugin), [output plugin](#output-plugin), [processor plugin](#processor-plugin)
+
+### shard
+
+A shard contains encoded and compressed data for a specific set of [series](#series).
+A shard consists of one or more [TSM files](#tsm-time-structured-merge-tree) on disk.
+All points in a series in a given shard group are stored in the same shard (TSM file) on disk.
+A shard belongs to a single [shard group](#shard-group).
+
+For more information, see [Shards and shard groups (OSS)](/influxdb/%762.1/reference/internals/shards/).
+
+Related entries: [series](#series), [shard duration](#shard-duration),
+[shard group](#shard-group), [tsm](#tsm-time-structured-merge-tree)
+
+### shard group
+
+Shard groups are logical containers for shards organized by [bucket](#bucket).
+Every bucket with data has at least one shard group.
+A shard group contains all shards with data for the time interval covered by the shard group.
+The interval spanned by each shard group is the [shard group duration](#shard-group-duration).
+
+For more information, see [Shards and shard groups (OSS)](/influxdb/%762.1/reference/internals/shards/).
+
+Related entries: [bucket](#bucket), [retention period](#retention-period),
+[series](#series), [shard](#shard), [shard duration](#shard-duration)
+
+### shard group duration
+
+The duration of time or interval that each [shard group](#shard-group) covers. Set the `shard-group-duration` for each [bucket](#bucket).
+
+For more information, see:
+
+- [Shards and shard groups (OSS)](/influxdb/%762.1/reference/internals/shards/)
+- [Manage buckets](/influxdb/v2.2/organizations/buckets/)
+
+<!-- See [Retention Policy management](/{{< latest "influxdb" "v1" >}}/query_language/manage-database/#retention-policy-management) for more information.
+
+For example, given a retention policy with `SHARD DURATION` set to `1w`, each shard group will span a single week and contain all points with timestamps in that week.
+
+Related entries: [database](#database), [retention policy](#retention-policy-rp), [series](/#series), [shard](#shard), [shard group](#shard-group)
+-->
+
+### Single Stat
+
+A visualization that displays the numeric value of the most recent point in a table (or series) returned by a query.
+
+### Snappy compression
+
+InfluxDB uses snappy compression to compress batches of points.
+To improve space and disk IO efficiency, each batch is compressed before being written to disk.
+
+<!-- in development ### stacked graph
+
+A visualization that displays points sharing a common X value as stacked rather than overlaid. Hence, the Y value is equal to the sum of Y values.
+
+Related entries: [bin](#bin)
+-->
+
+### step-plot
+
+A data visualization that displays time series data in a staircase graph.
+Generate a step-plot using the step [interpolation option for line graphs](/influxdb/v2.2/visualize-data/visualization-types/graph/#options).
+
+### stream
+
+Flux processes streams of data.
+A stream includes a series of tables over a sequence of time intervals.
+
+### string
+
+A data type used to represent text.
+In [annotated CSV](/influxdb/v2.2/reference/syntax/annotated-csv/), columns that contain
+string values are annotated with the `string` datatype.
+
+## T
+
+### TCP
+
+InfluxDB uses Transmission Control Protocol (TCP) port 8086 for client-server communication over the InfluxDB HTTP API.
+
+<!--ports for InfluxDB Enterprise -->
+
+### table
+
+Flux processes a series of tables for a specified time series.
+These tables in sequence result in a stream of data.
+
+### tag
+
+The key-value pair in InfluxDB's data structure that records metadata.
+Tags are an optional part of InfluxDB's data structure but they are useful for storing commonly-queried metadata; tags are indexed so queries on tags are performant.
+*Query tip:* Compare tags to fields; fields are not indexed.
+
+Related entries: [field](#field), [tag key](#tag-key), [tag set](#tag-set), [tag value](#tag-value)
+
+### tag key
+
+The key of a tag key-value pair.
+Tag keys are strings and store metadata.
+Tag keys are indexed so queries on tag keys are processed quickly.
+
+*Query tip:* Compare tag keys to field keys.
+Field keys are not indexed.
+
+Related entries: [field key](#field-key), [tag](#tag), [tag set](#tag-set), [tag value](#tag-value)
+
+### tag set
+
+The collection of tag keys and tag values on a point.
+
+Related entries: [point](#point), [series](#series), [tag](#tag), [tag key](#tag-key), [tag value](#tag-value)
+
+### tag value
+
+The value of a tag key-value pair.
+Tag values are strings and they store metadata.
+Tag values are indexed so queries on tag values are processed quickly.
+
+Related entries: [tag](#tag), [tag key](#tag-key), [tag set](#tag-set)
+
+### task
+
+A scheduled Flux query that runs periodically and may store results in a specified measurement.
+Examples include downsampling and batch jobs.
+For more information, see [Process Data with InfluxDB tasks](/influxdb/v2.2/process-data/).
+
+Related entries: [function](#function)
+
+### technical preview
+
+A new feature released to gather feedback from customers and the InfluxDB community. Send feedback to InfluxData via [Community Slack](https://app.slack.com/client/TH8RGQX5Z) or our [Community Site](https://community.influxdata.com/).
+
+### Telegraf
+
+A plugin-driven agent that collects, processes, aggregates, and writes metrics.
+
+Related entries: [Automatically configure Telegraf](/influxdb/v2.2/write-data/no-code/use-telegraf/auto-config/), [Manually configure Telegraf](/influxdb/v2.2/write-data/no-code/use-telegraf/manual-config/), [Telegraf plugins](/{{< latest "telegraf" >}}/plugins//), [Use Telegraf to collect data](/influxdb/v2.2/write-data/no-code/use-telegraf/), [View a Telegraf configuration](/influxdb/v2.2/telegraf-configs/view/)
+
+### time (data type)
+
+A data type that represents a single point in time with nanosecond precision.
+
+### time series data
+
+Sequence of data points typically consisting of successive measurements made from the same source over a time interval.
+Time series data shows how data evolves over time.
+On a time series data graph, one of the axes is always time.
+Time series data may be regular or irregular.
+Regular time series data changes in constant intervals.
+Irregular time series data changes at non-constant intervals.
+
+### timestamp
+
+The date and time associated with a point.
+Time in InfluxDB is in UTC.
+
+To specify time when writing data, see [Elements of line protocol](/influxdb/v2.2/reference/syntax/line-protocol/#elements-of-line-protocol).
+To specify time when querying data, see [Query InfluxDB with Flux](/influxdb/v2.2/query-data/get-started/query-influxdb/#2-specify-a-time-range).
+
+Related entries: [point](#point), [unix timestamp](#unix-timestamp), [RFC3339 timestamp](#rfc3339-timestamp)
+
+### token
+
+Tokens (or API tokens) verify user and organization permissions in InfluxDB.
+There are different types of API tokens:
+
+{{% oss-only %}}
+
+- **Operator token:** grants full read and write access to all resources in **all organizations in InfluxDB OSS 2.x**. _InfluxDB Cloud does not support Operator tokens._
+- **All-Access token:** grants full read and write access to all resources in an organization.
+- **Read/Write token:** grants read or write access to specific resources in an organization.
+
+{{% /oss-only %}}
+{{% cloud-only %}}
+
+- **All-Access token:** grants full read and write access to all resources in an organization.
+- **Read/Write token:** grants read or write access to specific resources in an organization.
+
+{{% /cloud-only %}}
+
+Related entries: [Create a token](/influxdb/v2.2/security/tokens/create-token/).
+
+### tracing
+
+By default, tracing is disabled in InfluxDB OSS.
+To enable tracing or set other InfluxDB OSS configuration options,
+see [InfluxDB OSS configuration options](/influxdb/v2%2E0/reference/config-options/).
+
+### transformation
+
+An InfluxQL function that returns a value or a set of values calculated from specified points, but does not return an aggregated value across those points.
+See [InfluxQL functions](/{{< latest "influxdb" "v1" >}}/query_language/functions/#transformations) for a complete list of the available and upcoming aggregations.
+
+Related entries: [aggregate](#aggregate), [function](#function), [selector](#selector)
+
+### TSI (Time Series Index)
+
+TSI uses the operating system's page cache to pull frequently accessed data into memory and keep infrequently accessed data on disk.
+
+### TSL
+
+The Time Series Logs (TSL) extension (`.tsl`) identifies Time Series Index (TSI) log files, generated by the tsi1 engine.
+
+### TSM (Time Structured Merge tree)
+
+A data storage format that allows greater compaction and higher write and read throughput than B+ or LSM tree implementations.
+For more information, see [Storage engine](/{{< latest "influxdb" "v1" >}}/concepts/storage_engine/).
+
+Related entries: [TSI](#tsi-time-series-index)
+
+## U
+
+### UDP
+
+User Datagram Protocol is a packet of information.
+When a request is made, a UDP packet is sent to the recipient.
+The sender doesn't verify the packet is received.
+The sender continues to send the next packets.
+This means computers can communicate more quickly.
+This protocol is used when speed is desirable and error correction is not necessary.
+
+### universe block
+
+An implicit block that encompasses all Flux source text in a universe block.
+
+### unix timestamp
+
+Counts time since **Unix Epoch (1970-01-01T00:00:00Z UTC)** in specified units ([precision](#precision)).
+Specify timestamp precision when [writing data to InfluxDB](/influxdb/v2.2/write-data/).
+InfluxDB supports the following unix timestamp precisions:
+
+| Precision | Description  | Example               |
+|:--------- |:-----------  |:-------               |
+| `ns`      | Nanoseconds  | `1577836800000000000` |
+| `us`      | Microseconds | `1577836800000000`    |
+| `ms`      | Milliseconds | `1577836800000`       |
+| `s`       | Seconds      | `1577836800`          |
+
+<p style="font-size:.9rem;margin-top:-2rem"><em>The examples above represent <strong>2020-01-01T00:00:00Z UTC</strong>.</em></p>
+
+Related entries: [timestamp](#timestamp), [RFC3339 timestamp](#rfc3339-timestamp)
+
+### unsigned integer
+A whole number that is positive or zero (`0`, `143`). Also known as a "uinteger."
+InfluxDB supports 64-bit unsigned integers (minimum: `0`, maximum: `18446744073709551615`).
+In [annotated CSV](/influxdb/v2.2/reference/syntax/annotated-csv/), columns that contain
+integers are annotated with the `unisgnedLong` datatype.
+
+Related entries: [integer](#integer)
+
+### user
+
+InfluxDB users are granted permission to access to InfluxDB.
+Users are added as a member of an organization and are given a unique API token.
+
+## V
+
+### values per second
+
+The preferred measurement of the rate at which data are persisted to InfluxDB.
+Write speeds are generally quoted in values per second.
+
+To calculate the values per second rate, multiply the number of points written
+per second by the number of values stored per point.
+For example, if the points have four fields each, and a batch of 5000 points is
+written 10 times per second, the values per second rate is:
+
+**4 field values per point** × **5000 points per batch** × **10 batches per second** = **200,000 values per second**  
+
+
+Related entries: [batch](#batch), [field](#field), [point](#point)
+
+### variable
+
+A storage location (identified by a memory address) paired with an associated symbolic name (an identifier).
+A variable contains some known or unknown quantity of information referred to as a value.
+
+### variable assignment
+
+A statement that sets or updates the value stored in a variable.
+
+In Flux, the variable assignment creates a variable bound to an identifier and gives it a type and value.
+A variable keeps the same type and value for the remainder of its lifetime.
+An identifier assigned to a variable in a block cannot be reassigned in the same block.
+
+## W
+
+<!--
+### WAL (Write Ahead Log) - enterprise
+
+The temporary cache for recently written points. To reduce the frequency that permanent storage files are accessed, InfluxDB caches new points in the WAL until their total size or age triggers a flush to more permanent storage. This allows for efficient batching of the writes into the TSM.
+
+Points in the WAL can be queried and persist through a system reboot. On process start, all points in the WAL must be flushed before the system accepts new writes.
+
+Related entries: [tsm](#tsm-time-structured-merge-tree)
+-->
+
+### windowing
+
+Grouping data based on specified time intervals.
+For information about how to window in Flux, see [Window and aggregate data with Flux](/influxdb/v2.2/query-data/flux/window-aggregate/).
diff --git a/content/influxdb/v2.2/reference/internals/_index.md b/content/influxdb/v2.2/reference/internals/_index.md
new file mode 100644
index 000000000..97af12692
--- /dev/null
+++ b/content/influxdb/v2.2/reference/internals/_index.md
@@ -0,0 +1,9 @@
+---
+title: InfluxDB internals
+menu:
+  influxdb_2_2_ref:
+    name: InfluxDB internals
+weight: 7
+---
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/reference/internals/data-retention.md b/content/influxdb/v2.2/reference/internals/data-retention.md
new file mode 100644
index 000000000..d4ae6786d
--- /dev/null
+++ b/content/influxdb/v2.2/reference/internals/data-retention.md
@@ -0,0 +1,80 @@
+---
+title: Data retention in InfluxDB
+description: >
+  The InfluxDB retention service checks for and removes data with timestamps beyond
+  the defined retention period of the bucket the data is stored in.
+weight: 103
+menu:
+  influxdb_2_2_ref:
+    name: Data retention
+    parent: InfluxDB internals
+influxdb/v2.2/tags: [storage, internals]
+related: 
+  - /influxdb/v2.2/reference/internals/shards/
+  - /influxdb/v2.2/reference/internals/storage-engine/
+---
+
+The **InfluxDB retention enforcement service** checks for and removes data with
+timestamps beyond the defined retention period of the
+[bucket](/influxdb/v2.2/reference/glossary/#bucket) the data is stored in.
+This service is designed to automatically delete "expired" data and optimize disk
+usage without any user intervention.
+
+By default, the retention enforcement service runs every 30 minutes.
+You can
+configure this interval with the
+[`storage-retention-check-interval`](/influxdb/v2.2/reference/config-options/#storage-retention-check-interval)
+configuration option.
+
+- [Bucket retention period](#bucket-retention-period)
+- [Shard group duration](#shard-group-duration)
+- [When does data actually get deleted?](#when-does-data-actually-get-deleted)
+
+## Bucket retention period
+A **bucket retention period** is the duration of time that a bucket retains data.
+Retention periods can be as short as an hour or infinite.
+[Points](/influxdb/v2.2/reference/glossary/#point) in a bucket with timestamps
+beyond the defined retention period (relative to now) are _eligible_ for deletion.
+
+## Shard group duration
+InfluxDB stores data on disk in [shards](/influxdb/v2.2/reference/glossary/#shard).
+Each shard belongs to a shard group and each shard group has a shard group duration.
+The **shard group duration** defines the duration of time that each
+shard in the shard group covers.
+Each shard contains only points with timestamps in a specific time range defined
+by the shard group duration.
+
+By default, shard group durations are set automatically based on the bucket retention
+period, but can also be explicitly defined when creating or updating a bucket.
+
+_For more information, see [InfluxDB shard group duration](/influxdb/v2.2/reference/internals/shards/#shard-group-duration)._
+
+{{% note %}}
+#### View bucket retention periods and shard group durations
+Use the [`influx bucket list` command](/influxdb/v2.2/reference/cli/influx/bucket/list/)
+to view the retention period and shard group duration of buckets in your organization.
+{{% /note %}}
+
+## When does data actually get deleted?
+The InfluxDB retention enforcement service runs at regular intervals and deletes
+[shard groups](/influxdb/v2.2/reference/internals/shards/#shard-groups), not individual points.
+The service will only delete a shard group when the entire time range covered by
+the shard group is beyond the bucket retention period.
+
+{{% note %}}
+#### Data is queryable until deleted
+Even though data may be older than the specified bucket retention period,
+it is queryable until removed by the retention enforcement service.
+{{% /note %}}
+
+To calculate the possible time data will persist before being deleted:
+
+- **minimum**: `bucket-retention-period`
+- **maximum** `bucket-retention-period + shard-group-duration`
+
+For example, if your bucket retention period is three days (`3d`) and your 
+shard group duration is one day (`1d`), the retention enforcement service
+deletes all shard groups with data that is **three to four days old** the next
+time the service runs.
+
+{{< html-diagram/data-retention >}}
diff --git a/content/influxdb/v2.2/reference/internals/file-system-layout.md b/content/influxdb/v2.2/reference/internals/file-system-layout.md
new file mode 100644
index 000000000..9454521a9
--- /dev/null
+++ b/content/influxdb/v2.2/reference/internals/file-system-layout.md
@@ -0,0 +1,260 @@
+---
+title: InfluxDB file system layout
+description: >
+  The InfluxDB file system layout depends on the operating system, package manager,
+  or containerization platform used to install InfluxDB.
+weight: 102
+menu:
+  influxdb_2_2_ref:
+    name: File system layout
+    parent: InfluxDB internals
+influxdb/v2.2/tags: [storage, internals]
+---
+
+The InfluxDB file system layout depends on the operating system, installation method,
+or containerization platform used to install InfluxDB.
+
+- [InfluxDB file structure](#influxdb-file-structure)
+- [File system layout](#file-system-layout)
+
+## InfluxDB file structure
+The InfluxDB file structure includes of the following:
+
+#### Engine path
+Directory path to the [storage engine](/{{< latest "influxdb" >}}/reference/internals/storage-engine/),
+where InfluxDB stores time series data, includes the following directories:
+
+- **data**: stores Time-Structured Merge Tree (TSM) files
+- **wal**: stores Write Ahead Log (WAL) files.
+
+To customize this path, use the [engine-path](/influxdb/v2.2/reference/config-options/#engine-path)
+configuration option.
+
+#### Bolt path
+File path to the [Boltdb](https://github.com/boltdb/bolt) database, a file-based
+key-value store for non-time series data, such as InfluxDB users, dashboards, tasks, etc.
+To customize this path, use the [bolt-path](/influxdb/v2.2/reference/config-options/#bolt-path)
+configuration option.
+
+#### Configs path
+File path to [`influx` CLI connection configurations](/influxdb/v2.2/reference/cli/influx/config/) (configs).
+To customize this path, use the `--configs-path` flag with `influx` CLI commands.
+
+#### InfluxDB configuration files
+Some operating systems and package managers store a default InfluxDB (`influxd`) configuration file on disk.
+For more information about using InfluxDB configuration files, see
+[Configuration options](/influxdb/v2.2/reference/config-options/).
+
+## File system layout
+{{< tabs-wrapper >}}
+{{% tabs %}}
+[macOS](#)
+[Linux](#)
+[Windows](#)
+[Docker](#)
+[Kubernetes](#)
+{{% /tabs %}}
+<!---------------------------- BEGIN MACOS CONTENT ---------------------------->
+{{% tab-content %}}
+
+#### macOS default paths
+| Path                          | Default                        |
+|:------------------------------|:-------------------------------|
+| [Engine path](#engine-path)   | `~/.influxdbv2/engine/`        |
+| [Bolt path](#bolt-path)       | `~/.influxdbv2/influxd.bolt`   |
+| [SQLite path](#sqlite-path)   | `~/.influxdbv2/influxd.sqlite` |
+| [Configs path](#configs-path) | `~/.influxdbv2/configs`        |
+
+#### macOS file system overview
+{{% filesystem-diagram %}}
+- ~/.influxdbv2/
+  - engine/
+    - data/
+      - _<span style="opacity:.4">TSM directories and files</span>_
+    - wal/
+      - _<span style="opacity:.4">WAL directories and files</span>_
+  - configs
+  - influxd.bolt
+  - influxd.sqlite
+{{% /filesystem-diagram %}}
+{{% /tab-content %}}
+<!----------------------------- END MACOS CONTENT ----------------------------->
+
+<!---------------------------- BEGIN LINUX CONTENT ---------------------------->
+{{% tab-content %}}
+When installing InfluxDB on Linux, you can download and install the `influxd` binary,
+or you can use a package manager.
+Which installation method you use determines the file system layout.
+
+- [Installed as a standalone binary](#installed-as-a-standalone-binary)
+- [Installed as a package](#installed-as-a-package)
+
+### Installed as a standalone binary
+
+#### Linux default paths (standalone binary)
+| Path                          | Default                      |
+|:----                          |:-------                      |
+| [Engine path](#engine-path)   | `~/.influxdbv2/engine/`      |
+| [Bolt path](#bolt-path)       | `~/.influxdbv2/influxd.bolt` |
+| [SQLite path](#sqlite-path)   | `~/.influxdbv2/influxd.sqlite` |
+| [Configs path](#configs-path) | `~/.influxdbv2/configs`      |
+
+#### Linux file system overview (standalone binary)
+{{% filesystem-diagram %}}
+- ~/.influxdbv2/
+  - engine/
+    - data/
+      - _<span style="opacity:.4">TSM directories and files</span>_
+    - wal/
+      - _<span style="opacity:.4">WAL directories and files</span>_
+  - configs
+  - influxd.bolt
+  - influxd.sqlite
+{{% /filesystem-diagram %}}
+
+### Installed as a package
+InfluxDB {{< current-version >}} supports **.deb-** and **.rpm-based** Linux package managers.
+The file system layout is the same with each.
+
+#### Linux default paths (package)
+| Path                                                      | Default                            |
+|:----------------------------------------------------------|:-----------------------------------|
+| [Engine path](#engine-path)                               | `/var/lib/influxdb/engine/`        |
+| [Bolt path](#bolt-path)                                   | `/var/lib/influxdb/influxd.bolt`   |
+| [SQLite path](#sqlite-path)                               | `/var/lib/influxdb/influxd.sqlite` |
+| [Configs path](#configs-path)                             | `/var/lib/influxdb/configs`        |
+| [Default config file path](#influxdb-configuration-files) | `/etc/influxdb/config.toml`        |
+
+#### Linux file system overview (package)
+{{% filesystem-diagram %}}
+- /var/lib/influxdb/
+  - engine/
+    - data/
+      - _<span style="opacity:.4">TSM directories and files</span>_
+    - wal/
+      - _<span style="opacity:.4">WAL directories and files</span>_
+  - configs
+  - influxd.bolt
+  - influxd.sqlite
+- /etc/influxdb/
+  - config.toml _<span style="opacity:.4">(influxd configuration file)</span>_
+{{% /filesystem-diagram %}}
+{{% /tab-content %}}
+<!----------------------------- END LINUX CONTENT ----------------------------->
+
+<!--------------------------- BEGIN WINDOWS CONTENT --------------------------->
+{{% tab-content %}}
+
+#### Windows default paths
+| Path                          | Default                                  |
+|:----                          |:-------                                  |
+| [Engine path](#engine-path)   | `%USERPROFILE%\.influxdbv2\engine\`      |
+| [Bolt path](#bolt-path)       | `%USERPROFILE%\.influxdbv2\influxd.bolt` |
+| [SQLite path](#sqlite-path)   | `%USERPROFILE%\.influxdbv2\influxd.sqlite` |
+| [Configs path](#configs-path) | `%USERPROFILE%\.influxdbv2\configs`      |
+
+#### Windows file system overview
+{{% filesystem-diagram %}}
+- %USERPROFILE%\\.influxdbv2\
+  - engine\
+    - data\
+      - _<span style="opacity:.4">TSM directories and files</span>_
+    - wal\
+      - _<span style="opacity:.4">WAL directories and files</span>_
+  - configs
+  - influxd.bolt
+  - influxd.sqlite
+{{% /filesystem-diagram %}}
+{{% /tab-content %}}
+<!---------------------------- END WINDOWS CONTENT ---------------------------->
+
+<!---------------------------- BEGIN DOCKER CONTENT --------------------------->
+{{% tab-content %}}
+InfluxDB Docker images are available from both [Dockerhub](https://hub.docker.com/_/influxdb)
+and [Quay.io](https://quay.io/repository/influxdb/influxdb?tab=tags).
+Each have a unique InfluxDB file system layout.
+
+- [Dockerhub](#dockerhub)
+- [Quay.io](#quayio)
+
+### Dockerhub
+
+{{% note %}}
+The InfluxDB Dockerhub image uses `/var/lib/influxdb2` instead of `/var/lib/influxdb`
+so you can easily mount separate volumes for InfluxDB 1.x and 2.x data during the
+[upgrade process](/influxdb/v2.2/upgrade/v1-to-v2/docker/).
+{{% /note %}}
+
+#### Dockerhub default paths
+| Path                          | Default                           |
+|:----                          |:-------                           |
+| [Engine path](#engine-path)   | `/var/lib/influxdb2/engine/`      |
+| [Bolt path](#bolt-path)       | `/var/lib/influxdb2/influxd.bolt` |
+| [SQLite path](#sqlite-path)   | `/var/lib/influxdb2/influxd.sqlite` |
+| [Configs path](#configs-path) | `/etc/influxdb2/configs`          |
+
+#### Dockerhub file system overview
+{{% filesystem-diagram %}}
+- /var/lib/influxdb2/
+  - engine/
+    - data/
+      - _<span style="opacity:.4">TSM directories and files</span>_
+    - wal/
+      - _<span style="opacity:.4">WAL directories and files</span>_
+  - influxd.bolt
+  - influxd.sqlite
+- /etc/influxdb2/
+  - configs
+{{% /filesystem-diagram %}}
+
+### Quay.io
+
+#### Quay default paths
+| Path                          | Default                          |
+|:----                          |:-------                          |
+| [Engine path](#engine-path)   | `/root/.influxdbv2/engine/`      |
+| [Bolt path](#bolt-path)       | `/root/.influxdbv2/influxd.bolt` |
+| [SQLite path](#sqlite-path)   | `/root/.influxdbv2/influxd.sqlite` |
+| [Configs path](#configs-path) | `/root/.influxdbv2/configs`      |
+
+#### Quay file system overview
+{{% filesystem-diagram %}}
+- /root/.influxdbv2/
+  - engine/
+    - data/
+      - _<span style="opacity:.4">TSM directories and files</span>_
+    - wal/
+      - _<span style="opacity:.4">WAL directories and files</span>_
+  - configs
+  - influxd.bolt
+  - influxd.sqlite
+{{% /filesystem-diagram %}}
+{{% /tab-content %}}
+<!----------------------------- END DOCKER CONTENT ---------------------------->
+
+<!-------------------------- BEGIN KUBERNETES CONTENT ------------------------->
+{{% tab-content %}}
+#### Kubernetes default paths
+| Path                          | Default                             |
+|:------------------------------|:------------------------------------|
+| [Engine path](#engine-path)   | `/var/lib/influxdb2/engine/`        |
+| [Bolt path](#bolt-path)       | `/var/lib/influxdb2/influxd.bolt`   |
+| [SQLite path](#sqlite-path)   | `/var/lib/influxdb2/influxd.sqlite` |
+| [Configs path](#configs-path) | `/etc/influxdb2/configs`            |
+
+#### Kubernetes file system overview
+{{% filesystem-diagram %}}
+- /var/lib/influxdb2/
+  - engine/
+    - data/
+      - _<span style="opacity:.4">TSM directories and files</span>_
+    - wal/
+      - _<span style="opacity:.4">WAL directories and files</span>_
+  - influxd.bolt
+  - influxd.sqlite
+- /etc/influxdb2/
+  - configs
+{{% /filesystem-diagram %}}
+{{% /tab-content %}}
+<!--------------------------- END KUBERNETES CONTENT -------------------------->
+{{< /tabs-wrapper >}}
diff --git a/content/influxdb/v2.2/reference/internals/metrics.md b/content/influxdb/v2.2/reference/internals/metrics.md
new file mode 100644
index 000000000..82c0dbdf1
--- /dev/null
+++ b/content/influxdb/v2.2/reference/internals/metrics.md
@@ -0,0 +1,1743 @@
+---
+title: InfluxDB OSS metrics
+description: >
+ Get metrics about the workload performance of an InfluxDB OSS instance.
+menu:
+ influxdb_2_2_ref:
+   parent: InfluxDB internals
+   name: Metrics
+influxdb/v2.2/tags: [cpu, memory, metrics, performance, Prometheus, storage, usage]
+---
+Get metrics about the workload performance of an InfluxDB OSS instance.
+
+InfluxDB OSS exposes a `/metrics` endpoint that returns
+performance, resource, and usage metrics formatted in the [Prometheus plain-text exposition format](https://prometheus.io/docs/instrumenting/exposition_formats).
+
+[{{< api-endpoint method="GET" endpoint="http://localhost:8086/metrics" >}}](/influxdb/v2.1/api/#operation/GetMetrics)
+
+Metrics contain a name, an optional set of key-value pairs, and a value.
+
+The following descriptors precede each metric:
+
+- `HELP`: description of the metric
+- `TYPE`: [Prometheus metric type](https://prometheus.io/docs/concepts/metric_types/) (`counter`, `gauge`, `histogram`, or `summary`)
+
+#### Example
+
+```sh
+# HELP go_info Information about the Go environment.
+# TYPE go_info gauge
+go_info{version="go1.17"} 1
+# HELP go_memstats_alloc_bytes Number of bytes allocated and still in use.
+# TYPE go_memstats_alloc_bytes gauge
+go_memstats_alloc_bytes 2.27988488e+08
+# HELP go_memstats_alloc_bytes_total Total number of bytes allocated, even if freed.
+# TYPE go_memstats_alloc_bytes_total counter
+go_memstats_alloc_bytes_total 9.68016566648e+11
+```
+
+The InfluxDB `/metrics` endpoint returns metrics associated with the following categories:
+
+- [Boltdb](#boltdb-statistics)
+- [Go runtime](#go-runtime-statistics)
+- [HTTP API](#http-api-statistics)
+- [InfluxDB objects and queries](#influxdb-object-and-query-statistics)
+  - [QC (query controller)](#qc-query-controller-statistics)
+- [InfluxDB services](#influxdb-service-statistics)
+- [InfluxDB storage](#influxdb-storage-statistics)
+- [InfluxDB tasks](#influxdb-task-statistics)
+
+## Boltdb statistics
+
+### Reads total
+
+Total number of boltdb reads.
+
+#### Example
+
+```sh
+# HELP boltdb_reads_total Total number of boltdb reads
+# TYPE boltdb_reads_total counter
+boltdb_reads_total 75129
+```
+### Writes total
+
+Total number of boltdb writes.
+
+#### Example
+
+```sh
+# HELP boltdb_writes_total Total number of boltdb writes
+# TYPE boltdb_writes_total counter
+boltdb_writes_total 201591
+```
+
+## Go runtime statistics
+
+For more detail about Go runtime statistics, see the following:
+- [Go diagostics documentation](https://go.dev/doc/diagnostics)
+- [Go mstats](https://github.com/golang/go/blob/master/src/runtime/mstats.go)
+
+### GC (garbage collection) duration seconds
+
+Summary of the pause duration of garbage collection cycles.
+
+#### Example
+
+```sh
+# HELP go_gc_duration_seconds A summary of the pause duration of garbage collection cycles.
+# TYPE go_gc_duration_seconds summary
+go_gc_duration_seconds{quantile="0"} 5.1467e-05
+--
+```
+
+### Goroutines
+
+Number of goroutines that currently exist.
+
+#### Example
+
+```sh
+# HELP go_goroutines Number of goroutines that currently exist.
+# TYPE go_goroutines gauge
+go_goroutines 1566
+```
+
+### Info
+
+Information about the Go environment.
+
+#### Example
+
+```sh
+# HELP go_info Information about the Go environment.
+# TYPE go_info gauge
+go_info{version="go1.17"} 1
+```
+
+### Memory allocated bytes
+
+Number of bytes allocated and still in use.
+
+#### Example
+
+```sh
+# HELP go_memstats_alloc_bytes Number of bytes allocated and still in use.
+# TYPE go_memstats_alloc_bytes gauge
+go_memstats_alloc_bytes 2.27988488e+08
+```
+
+### Memory allocated bytes total
+
+Total number of bytes allocated, even if freed.
+
+#### Example
+
+```sh
+# HELP go_memstats_alloc_bytes_total Total number of bytes allocated, even if freed.
+# TYPE go_memstats_alloc_bytes_total counter
+go_memstats_alloc_bytes_total 9.68016566648e+11
+```
+
+### Memory bucket hash system bytes
+
+Number of bytes used by the profiling bucket hash table.
+
+#### Example
+
+```sh
+# HELP go_memstats_buck_hash_sys_bytes Number of bytes used by the profiling bucket hash table.
+# TYPE go_memstats_buck_hash_sys_bytes gauge
+go_memstats_buck_hash_sys_bytes 1.0067613e+07
+```
+
+### Memory frees total
+
+Total number of frees.
+
+#### Example
+
+```sh
+# HELP go_memstats_frees_total Total number of frees.
+# TYPE go_memstats_frees_total counter
+go_memstats_frees_total 1.3774541795e+10
+```
+
+### Memory GC (garbage collection) CPU fraction
+
+Fraction of this program's available CPU time used by the GC since the program started.
+
+#### Example
+
+```sh
+# HELP go_memstats_gc_cpu_fraction The fraction of this program's available CPU time used by the GC since the program started.
+# TYPE go_memstats_gc_cpu_fraction gauge
+go_memstats_gc_cpu_fraction 0.011634918451016558
+```
+
+### Memory GC (garbage collection) system bytes
+
+Number of bytes used for garbage collection system metadata.
+
+#### Example
+
+```sh
+# HELP go_memstats_gc_sys_bytes Number of bytes used for garbage collection system metadata.
+# TYPE go_memstats_gc_sys_bytes gauge
+go_memstats_gc_sys_bytes 4.63048016e+08
+```
+
+### Memory heap allocated bytes
+
+Number of heap bytes allocated and still in use.
+
+#### Example
+
+```sh
+# HELP go_memstats_heap_alloc_bytes Number of heap bytes allocated and still in use.
+# TYPE go_memstats_heap_alloc_bytes gauge
+go_memstats_heap_alloc_bytes 2.27988488e+08
+```
+
+### Memory heap idle bytes
+
+Number of heap bytes waiting to be used.
+
+#### Example
+
+```sh
+# HELP go_memstats_heap_idle_bytes Number of heap bytes waiting to be used.
+# TYPE go_memstats_heap_idle_bytes gauge
+go_memstats_heap_idle_bytes 1.0918273024e+10
+```
+
+### Memory heap in use bytes
+
+Number of heap bytes that are in use.
+
+#### Example
+
+```sh
+# HELP go_memstats_heap_inuse_bytes Number of heap bytes that are in use.
+# TYPE go_memstats_heap_inuse_bytes gauge
+go_memstats_heap_inuse_bytes 3.5975168e+08
+```
+
+### Memory heap objects
+
+Number of allocated objects.
+_Allocated_ heap objects include all reachable objects, as
+well as unreachable objects that the garbage collector has not yet freed.
+
+#### Example
+
+```sh
+# HELP go_memstats_heap_objects Number of allocated objects.
+# TYPE go_memstats_heap_objects gauge
+go_memstats_heap_objects 2.404017e+06
+```
+
+### Memory heap released bytes
+
+Number of heap bytes released to the OS.
+
+#### Example
+
+```sh
+# HELP go_memstats_heap_released_bytes Number of heap bytes released to OS.
+# TYPE go_memstats_heap_released_bytes gauge
+go_memstats_heap_released_bytes 2.095038464e+09
+```
+
+### Memory heap system bytes
+
+Number of heap bytes obtained from the system.
+
+#### Example
+
+```sh
+# HELP go_memstats_heap_sys_bytes Number of heap bytes obtained from system.
+# TYPE go_memstats_heap_sys_bytes gauge
+go_memstats_heap_sys_bytes 1.1278024704e+10
+```
+
+### Memory last GC (garbage collection) time seconds
+
+Number of seconds since 1970 of the last garbage collection.
+
+#### Example
+
+```sh
+# HELP go_memstats_last_gc_time_seconds Number of seconds since 1970 of last garbage collection.
+# TYPE go_memstats_last_gc_time_seconds gauge
+go_memstats_last_gc_time_seconds 1.64217120199452e+09
+```
+
+### Memory lookups total
+
+Total number of pointer lookups.
+
+#### Example
+
+```sh
+# HELP go_memstats_lookups_total Total number of pointer lookups.
+# TYPE go_memstats_lookups_total counter
+go_memstats_lookups_total 0
+```
+
+### Memory allocations total
+
+Cumulative count of heap objects allocated.
+
+#### Example
+
+```sh
+# HELP go_memstats_mallocs_total Total number of mallocs.
+# TYPE go_memstats_mallocs_total counter
+go_memstats_mallocs_total 1.3776945812e+10
+```
+
+### Memory mcache in use bytes
+
+Number of bytes in use by mcache structures.
+
+#### Example
+
+```sh
+# HELP go_memstats_mcache_inuse_bytes Number of bytes in use by mcache structures.
+# TYPE go_memstats_mcache_inuse_bytes gauge
+go_memstats_mcache_inuse_bytes 9600
+```
+
+### Memory mcache system bytes
+
+Number of bytes used for mcache structures obtained from system.
+
+#### Example
+
+```sh
+# HELP go_memstats_mcache_sys_bytes Number of bytes used for mcache structures obtained from system.
+# TYPE go_memstats_mcache_sys_bytes gauge
+go_memstats_mcache_sys_bytes 16384
+```
+
+### Memory mspan in use bytes
+
+Number of bytes of allocated mspan structures.
+
+#### Example
+
+```sh
+# HELP go_memstats_mspan_inuse_bytes Number of bytes in use by mspan structures.
+# TYPE go_memstats_mspan_inuse_bytes gauge
+go_memstats_mspan_inuse_bytes 4.199e+06
+```
+
+### Memory mspan system bytes
+
+Bytes of memory obtained from the OS for mspan structures.
+
+#### Example
+
+```sh
+# HELP go_memstats_mspan_sys_bytes Number of bytes used for mspan structures obtained from system.
+# TYPE go_memstats_mspan_sys_bytes gauge
+go_memstats_mspan_sys_bytes 1.65609472e+08
+```
+
+### Memory next GC (garbage collection) bytes
+
+Number of heap bytes when next garbage collection will take place.
+
+#### Example
+
+```sh
+# HELP go_memstats_next_gc_bytes Number of heap bytes when next garbage collection will take place.
+# TYPE go_memstats_next_gc_bytes gauge
+go_memstats_next_gc_bytes 4.45628016e+08
+```
+
+### Memory other system bytes
+
+Number of bytes used for other system allocations.
+
+#### Example
+
+```sh
+# HELP go_memstats_other_sys_bytes Number of bytes used for other system allocations.
+# TYPE go_memstats_other_sys_bytes gauge
+go_memstats_other_sys_bytes 8.1917722e+07
+```
+
+### Memory stack in use bytes
+
+Number of bytes in use by the stack allocator.
+
+#### Example
+
+```sh
+# HELP go_memstats_stack_inuse_bytes Number of bytes in use by the stack allocator.
+# TYPE go_memstats_stack_inuse_bytes gauge
+go_memstats_stack_inuse_bytes 8.84736e+06
+```
+
+### Memory stack system bytes
+
+Number of bytes obtained from system for stack allocator.
+
+#### Example
+
+```sh
+# HELP go_memstats_stack_sys_bytes Number of bytes obtained from system for stack allocator.
+# TYPE go_memstats_stack_sys_bytes gauge
+go_memstats_stack_sys_bytes 8.84736e+06
+```
+
+### Memory system bytes
+
+Number of bytes obtained from system.
+
+#### Example
+
+```sh
+# HELP go_memstats_sys_bytes Number of bytes obtained from system.
+# TYPE go_memstats_sys_bytes gauge
+go_memstats_sys_bytes 1.2007531271e+10
+```
+
+### Threads
+
+Number of OS threads created.
+
+#### Example
+
+```sh
+# HELP go_threads Number of OS threads created.
+# TYPE go_threads gauge
+go_threads 27
+```
+
+## HTTP API statistics
+
+### API request duration seconds
+
+How long InfluxDB took to respond to the HTTP request.
+
+#### Example
+
+```sh
+# HELP http_api_request_duration_seconds Time taken to respond to HTTP request
+# TYPE http_api_request_duration_seconds histogram
+http_api_request_duration_seconds_bucket{handler="platform",method="DELETE",path="/api/v2/authorizations/:id",response_code="204",status="2XX",user_agent="Chrome",le="0.005"} 0
+--
+```
+
+### API requests total
+
+Number of HTTP requests received.
+
+#### Example
+
+```sh
+# HELP http_api_requests_total Number of http requests received
+# TYPE http_api_requests_total counter
+http_api_requests_total{handler="platform",method="DELETE",path="/api/v2/authorizations/:id",response_code="204",status="2XX",user_agent="Chrome"} 1
+--
+```
+
+### Query request bytes
+
+Count of bytes received.
+
+#### Example
+
+```sh
+# HELP http_query_request_bytes Count of bytes received
+# TYPE http_query_request_bytes counter
+http_query_request_bytes{endpoint="/api/v2/query",org_id="48c88459ee424a04",status="200"} 727
+```
+
+### Query request count
+
+Total number of query requests.
+
+#### Example
+
+```sh
+# HELP http_query_request_count Total number of query requests
+# TYPE http_query_request_count counter
+http_query_request_count{endpoint="/api/v2/query",org_id="48c88459ee424a04",status="200"} 2
+```
+
+### Query response bytes
+
+Count of bytes returned by the query endpoint.
+
+#### Example
+
+```sh
+# HELP http_query_response_bytes Count of bytes returned
+# TYPE http_query_response_bytes counter
+http_query_response_bytes{endpoint="/api/v2/query",org_id="48c88459ee424a04",status="200"} 103
+```
+
+## InfluxDB object and query statistics
+
+### Buckets total
+
+Total number of buckets on the server.
+
+#### Example
+
+```sh
+# HELP influxdb_buckets_total Number of total buckets on the server
+# TYPE influxdb_buckets_total counter
+influxdb_buckets_total 9
+```
+
+### Dashboards total
+
+Total number of dashboards on the server.
+
+#### Example
+
+```sh
+# HELP influxdb_dashboards_total Number of total dashboards on the server
+# TYPE influxdb_dashboards_total counter
+influxdb_dashboards_total 2
+```
+
+### Info
+
+Information about the InfluxDB environment.
+
+#### Example
+
+```sh
+# HELP influxdb_info Information about the influxdb environment.
+# TYPE influxdb_info gauge
+influxdb_info{arch="amd64",build_date="2021-12-28T22:12:40Z",commit="657e1839de",cpus="8",os="darwin",version="v2.1.1"} 1
+```
+
+### Organizations total
+
+Total number of organizations on the server.
+
+#### Example
+
+```sh
+# HELP influxdb_organizations_total Number of total organizations on the server
+# TYPE influxdb_organizations_total counter
+influxdb_organizations_total 2
+```
+
+### Scrapers total
+
+Total number of scrapers on the server.
+
+#### Example
+
+```sh
+# HELP influxdb_scrapers_total Number of total scrapers on the server
+# TYPE influxdb_scrapers_total counter
+influxdb_scrapers_total 0
+```
+
+### Telegrafs total
+
+Total number of Telegraf configurations on the server.
+
+#### Example
+
+```sh
+# HELP influxdb_telegrafs_total Number of total telegraf configurations on the server
+# TYPE influxdb_telegrafs_total counter
+influxdb_telegrafs_total 0
+```
+
+### Token services total
+
+Total number of API tokens on the server.
+
+#### Example
+
+```sh
+# HELP influxdb_tokens_total Number of total tokens on the server
+# TYPE influxdb_tokens_total counter
+influxdb_tokens_total 23
+```
+
+### Uptime seconds
+
+InfluxDB process uptime in seconds.
+
+#### Example
+
+```sh
+# HELP influxdb_uptime_seconds influxdb process uptime in seconds
+# TYPE influxdb_uptime_seconds gauge
+influxdb_uptime_seconds{id="077238f9ca108000"} 343354.914499305
+```
+
+### Users total
+
+Total number of users on the server.
+
+#### Example
+
+```sh
+# HELP influxdb_users_total Number of total users on the server
+# TYPE influxdb_users_total counter
+influxdb_users_total 84
+```
+
+## QC (query controller) statistics
+
+### All active
+
+Number of queries in all states.
+
+#### Example
+
+```sh
+# HELP qc_all_active Number of queries in all states
+# TYPE qc_all_active gauge
+qc_all_active{org="48c88459ee424a04"} 0
+--
+```
+
+### All duration seconds
+
+Total time spent in all query states.
+
+#### Example
+
+```sh
+# HELP qc_all_duration_seconds Histogram of total times spent in all query states
+# TYPE qc_all_duration_seconds histogram
+qc_all_duration_seconds_bucket{org="48c88459ee424a04",le="0.001"} 0
+--
+```
+
+### Compiling active
+
+Number of queries actively compiling.
+
+#### Example
+
+```sh
+# HELP qc_compiling_active Number of queries actively compiling
+# TYPE qc_compiling_active gauge
+qc_compiling_active{compiler_type="ast",org="ed32b47572a0137b"} 0
+--
+```
+
+### Compiling duration seconds
+
+Histogram of times spent compiling queries.
+
+#### Example
+
+```sh
+# HELP qc_compiling_duration_seconds Histogram of times spent compiling queries
+# TYPE qc_compiling_duration_seconds histogram
+qc_compiling_duration_seconds_bucket{compiler_type="ast",org="ed32b47572a0137b",le="0.001"} 999
+--
+```
+
+### Executing active
+
+Number of queries actively executing.
+
+#### Example
+
+```sh
+# HELP qc_executing_active Number of queries actively executing
+# TYPE qc_executing_active gauge
+qc_executing_active{org="48c88459ee424a04"} 0
+--
+```
+
+### Executing duration seconds
+
+Histogram of times spent executing queries.
+
+#### Example
+
+```sh
+# HELP qc_executing_duration_seconds Histogram of times spent executing queries
+# TYPE qc_executing_duration_seconds histogram
+qc_executing_duration_seconds_bucket{org="48c88459ee424a04",le="0.001"} 0
+--
+```
+
+### Memory unused bytes
+
+Free memory as seen by the internal memory manager.
+
+#### Example
+
+```sh
+# HELP qc_memory_unused_bytes The free memory as seen by the internal memory manager
+# TYPE qc_memory_unused_bytes gauge
+qc_memory_unused_bytes{org="48c88459ee424a04"} 0
+--
+```
+
+### Queueing active
+
+Number of queries actively queueing.
+
+#### Example
+
+```sh
+# HELP qc_queueing_active Number of queries actively queueing
+# TYPE qc_queueing_active gauge
+qc_queueing_active{org="48c88459ee424a04"} 0
+--
+```
+
+### Queueing duration seconds
+
+Histogram of times spent queueing queries.
+
+#### Example
+
+```sh
+# HELP qc_queueing_duration_seconds Histogram of times spent queueing queries
+# TYPE qc_queueing_duration_seconds histogram
+qc_queueing_duration_seconds_bucket{org="48c88459ee424a04",le="0.001"} 2
+--
+```
+
+### Requests total
+
+Count of the query requests.
+
+#### Example
+
+```sh
+# HELP qc_requests_total Count of the query requests
+# TYPE qc_requests_total counter
+qc_requests_total{org="48c88459ee424a04",result="success"} 2
+--
+```
+
+### Read request duration
+
+Histogram of times spent in read requests.
+
+#### Example
+
+```sh
+# HELP query_influxdb_source_read_request_duration_seconds Histogram of times spent in read requests
+# TYPE query_influxdb_source_read_request_duration_seconds histogram
+query_influxdb_source_read_request_duration_seconds_bucket{op="readTagKeys",org="48c88459ee424a04",le="0.001"} 0
+--
+```
+
+## InfluxDB service statistics
+
+### Bucket service new call total
+
+Number of calls to the bucket creation service.
+
+#### Example
+
+```sh
+# HELP service_bucket_new_call_total Number of calls
+# TYPE service_bucket_new_call_total counter
+service_bucket_new_call_total{method="find_bucket"} 6177
+--
+```
+
+### Bucket service new duration
+
+Duration of calls to the bucket creation service.
+
+#### Example
+
+```sh
+# HELP service_bucket_new_duration Duration of calls
+# TYPE service_bucket_new_duration histogram
+service_bucket_new_duration_bucket{method="find_bucket",le="0.005"} 5876
+--
+```
+
+### Bucket service new error total
+
+Number of errors encountered by the bucket creation service.
+
+#### Example
+
+```sh
+# HELP service_bucket_new_error_total Number of errors encountered
+# TYPE service_bucket_new_error_total counter
+service_bucket_new_error_total{code="not found",method="find_bucket_by_id"} 76
+```
+
+### Onboard service new call total
+
+Number of calls to the onboarding service.
+
+#### Example
+
+```sh
+# HELP service_onboard_new_call_total Number of calls
+# TYPE service_onboard_new_call_total counter
+service_onboard_new_call_total{method="is_onboarding"} 11
+```
+
+### Onboard service new duration
+
+Duration of calls to the onboarding service.
+
+#### Example
+
+```sh
+# HELP service_onboard_new_duration Duration of calls
+# TYPE service_onboard_new_duration histogram
+service_onboard_new_duration_bucket{method="is_onboarding",le="0.005"} 11
+--
+```
+
+### Organization service call total
+
+Number of calls to the organization service.
+
+#### Example
+
+```sh
+# HELP service_org_call_total Number of calls
+# TYPE service_org_call_total counter
+service_org_call_total{method="find_labels_for_resource"} 10
+```
+
+### Organization service duration
+
+Duration of calls to the organization service.
+
+#### Example
+
+```sh
+# HELP service_org_duration Duration of calls
+# TYPE service_org_duration histogram
+service_org_duration_bucket{method="find_labels_for_resource",le="0.005"} 10
+--
+```
+
+### Organization service new call total
+
+Number of calls to the organization creation service.
+
+#### Example
+
+```sh
+# HELP service_org_new_call_total Number of calls
+# TYPE service_org_new_call_total counter
+service_org_new_call_total{method="find_org"} 1572
+--
+```
+
+### Organization service new duration
+
+Duration of calls to the organization creation service.
+
+#### Example
+
+```sh
+# HELP service_org_new_duration Duration of calls
+# TYPE service_org_new_duration histogram
+service_org_new_duration_bucket{method="find_org",le="0.005"} 1475
+--
+```
+
+### Organization service new error total
+
+Number of errors encountered by the organization creation service.
+
+#### Example
+
+```sh
+# HELP service_org_new_error_total Number of errors encountered
+# TYPE service_org_new_error_total counter
+service_org_new_error_total{code="not found",method="find_orgs"} 1
+```
+
+### Password service new call total
+
+Number of calls to the password creation service.
+
+#### Example
+
+```sh
+# HELP service_password_new_call_total Number of calls
+# TYPE service_password_new_call_total counter
+service_password_new_call_total{method="compare_password"} 4
+```
+
+### Password service new duration
+
+Duration of calls to the password creation service.
+
+#### Example
+
+```sh
+# HELP service_password_new_duration Duration of calls
+# TYPE service_password_new_duration histogram
+service_password_new_duration_bucket{method="compare_password",le="0.005"} 0
+--
+```
+
+### Password service new error total
+
+Number of errors encountered by the password creation service.
+
+#### Example
+
+```sh
+# HELP service_password_new_error_total Number of errors encountered
+# TYPE service_password_new_error_total counter
+service_password_new_error_total{code="forbidden",method="compare_password"} 1
+```
+
+### Pkger service call total
+
+Number of calls to the `pkger` service.
+
+#### Example
+
+```sh
+# HELP service_pkger_call_total Number of calls
+# TYPE service_pkger_call_total counter
+service_pkger_call_total{method="export"} 3
+```
+
+### Pkger service duration
+
+Duration of calls to the `pkger` service.
+
+#### Example
+
+```sh
+# HELP service_pkger_duration Duration of calls
+# TYPE service_pkger_duration histogram
+service_pkger_duration_bucket{method="export",le="0.005"} 0
+--
+```
+
+### Pkger service template export
+
+Metrics for exported resources.
+
+#### Example
+
+```sh
+# HELP service_pkger_template_export Metrics for resources being exported
+# TYPE service_pkger_template_export counter
+service_pkger_template_export{buckets="0",by_stack="false",checks="0",dashboards="0",endpoints="0",label_mappings="0",labels="0",method="export",num_org_ids="1",rules="0",tasks="0",telegraf_configs="0",variables="0"} 3
+```
+
+### Session service call total
+
+Number of calls to the session service.
+
+#### Example
+
+```sh
+# HELP service_session_call_total Number of calls
+# TYPE service_session_call_total counter
+service_session_call_total{method="create_session"} 3
+--
+```
+
+### Session service duration
+
+Duration of calls to the session service.
+
+#### Example
+
+```sh
+# HELP service_session_duration Duration of calls
+# TYPE service_session_duration histogram
+service_session_duration_bucket{method="create_session",le="0.005"} 3
+--
+```
+
+### Session service error total
+
+Number of errors encountered by the session service.
+
+#### Example
+
+```sh
+# HELP service_session_error_total Number of errors encountered
+# TYPE service_session_error_total counter
+service_session_error_total{code="not found",method="find_session"} 4
+```
+
+### Token service call total
+
+Number of calls to the token service.
+
+#### Example
+
+```sh
+# HELP service_token_call_total Number of calls
+# TYPE service_token_call_total counter
+service_token_call_total{method="delete_authorization"} 3
+--
+```
+
+### Token service duration
+
+Duration of calls to the token service.
+
+#### Example
+
+```sh
+# HELP service_token_duration Duration of calls
+# TYPE service_token_duration histogram
+service_token_duration_bucket{method="delete_authorization",le="0.005"} 1
+--
+```
+
+### Token service error total
+
+Number of errors encountered by the token service.
+
+#### Example
+
+```sh
+# HELP service_token_error_total Number of errors encountered
+# TYPE service_token_error_total counter
+service_token_error_total{code="not found",method="delete_authorization"} 1
+```
+
+### URM new call total
+Number of calls to the URM (unified resource management) creation service.
+
+#### Example
+
+```sh
+# HELP service_urm_new_call_total Number of calls
+# TYPE service_urm_new_call_total counter
+service_urm_new_call_total{method="find_urms"} 6451
+```
+
+### urm new duration
+Duration of calls to the URM creation service.
+
+#### Example
+
+```sh
+# HELP service_urm_new_duration Duration of calls
+# TYPE service_urm_new_duration histogram
+service_urm_new_duration_bucket{method="find_urms",le="0.005"} 6198
+--
+```
+
+### User new call total
+Number of calls to the user creation service.
+
+#### Example
+
+```sh
+# HELP service_user_new_call_total Number of calls
+# TYPE service_user_new_call_total counter
+service_user_new_call_total{method="find_permission_for_user"} 4806
+--
+```
+
+### User new duration
+Duration of calls to the user creation service.
+
+#### Example
+
+```sh
+# HELP service_user_new_duration Duration of calls
+# TYPE service_user_new_duration histogram
+service_user_new_duration_bucket{method="find_permission_for_user",le="0.005"} 4039
+--
+```
+
+## InfluxDB storage statistics
+
+To learn how InfluxDB writes, stores, and caches data, see [InfluxDB storage engine](/influxdb/v2.2/reference/internals/storage-engine/).
+
+### Bucket measurement number
+
+Number of measurements in a bucket.
+
+#### Example
+
+```sh
+# HELP storage_bucket_measurement_num Gauge of measurement cardinality per bucket
+# TYPE storage_bucket_measurement_num gauge
+storage_bucket_measurement_num{bucket="0c3dd7d2d97f4b23"} 4
+--
+```
+
+### Bucket series number
+
+Number of series in a bucket.
+
+#### Example
+
+```sh
+# HELP storage_bucket_series_num Gauge of series cardinality per bucket
+# TYPE storage_bucket_series_num gauge
+storage_bucket_series_num{bucket="0c3dd7d2d97f4b23"} 38
+--
+```
+
+### Cache disk bytes
+
+Size (in bytes) of the most recent [snapshot](/influxdb/v2.2/reference/internals/storage-engine/#cache).
+
+#### Example
+
+```sh
+# HELP storage_cache_disk_bytes Gauge of size of most recent snapshot
+# TYPE storage_cache_disk_bytes gauge
+storage_cache_disk_bytes{bucket="0c3dd7d2d97f4b23",engine="tsm1",id="561",path="/Users/me/.influxdbv2/engine/data/0c3dd7d2d97f4b23/autogen/561",walPath="/Users/me/.influxdbv2/engine/wal/0c3dd7d2d97f4b23/autogen/561"} 0
+--
+```
+
+### Cache in use bytes
+
+Current memory consumption (in bytes) of the [cache](/influxdb/v2.2/reference/internals/storage-engine/#cache).
+
+#### Example
+
+```sh
+# HELP storage_cache_inuse_bytes Gauge of current memory consumption of cache
+# TYPE storage_cache_inuse_bytes gauge
+storage_cache_inuse_bytes{bucket="0c3dd7d2d97f4b23",engine="tsm1",id="561",path="/Users/me/.influxdbv2/engine/data/0c3dd7d2d97f4b23/autogen/561",walPath="/Users/me/.influxdbv2/engine/wal/0c3dd7d2d97f4b23/autogen/561"} 0
+--
+```
+
+### Cache latest snapshot
+
+[Unix time](/influxdb/v2.2/reference/glossary/#unix-timestamp) of the most recent [snapshot](/influxdb/v2.2/reference/internals/storage-engine/#cache).
+
+#### Example
+
+```sh
+# HELP storage_cache_latest_snapshot Unix time of most recent snapshot
+# TYPE storage_cache_latest_snapshot gauge
+storage_cache_latest_snapshot{bucket="0c3dd7d2d97f4b23",engine="tsm1",id="561",path="/Users/me/.influxdbv2/engine/data/0c3dd7d2d97f4b23/autogen/561",walPath="/Users/me/.influxdbv2/engine/wal/0c3dd7d2d97f4b23/autogen/561"} 1.644269658196893e+09
+--
+```
+
+### Cache writes with dropped points
+
+Cumulative number of [cached](/influxdb/v2.2/reference/internals/storage-engine/#cache) writes that had [rejected points](/influxdb/v2.2/reference/glossary/#rejected-point). Writes with rejected points also increment the [write errors counter (`storage_cache_writes_err`)](#cache-writes-failed).
+
+#### Example
+
+```sh
+# HELP storage_cache_writes_dropped Counter of writes to cache with some dropped points
+# TYPE storage_cache_writes_dropped counter
+storage_cache_writes_dropped{bucket="0c3dd7d2d97f4b23",engine="tsm1",id="561",path="/Users/me/.influxdbv2/engine/data/0c3dd7d2d97f4b23/autogen/561",walPath="/Users/me/.influxdbv2/engine/wal/0c3dd7d2d97f4b23/autogen/561"} 0
+--
+```
+
+### Cache writes failed
+
+Cumulative number of  [cached](/influxdb/v2.2/reference/internals/storage-engine/#cache) writes that [failed](/influxdb/v2.2/write-data/troubleshoot/#troubleshoot-failures), inclusive of [cache writes with dropped points (`storage_cache_writes_dropped`)](#cache-writes-with-dropped-points).
+
+#### Example
+
+```sh
+# HELP storage_cache_writes_err Counter of failed writes to cache
+# TYPE storage_cache_writes_err counter
+storage_cache_writes_err{bucket="0c3dd7d2d97f4b23",engine="tsm1",id="561",path="/Users/me/.influxdbv2/engine/data/0c3dd7d2d97f4b23/autogen/561",walPath="/Users/me/.influxdbv2/engine/wal/0c3dd7d2d97f4b23/autogen/561"} 0
+--
+```
+
+### Cache writes total
+
+Cumulative number of  writes to [cache](/influxdb/v2.2/reference/internals/storage-engine/#cache).
+
+#### Example
+
+```sh
+# HELP storage_cache_writes_total Counter of all writes to cache
+# TYPE storage_cache_writes_total counter
+storage_cache_writes_total{bucket="0c3dd7d2d97f4b23",engine="tsm1",id="561",path="/Users/me/.influxdbv2/engine/data/0c3dd7d2d97f4b23/autogen/561",walPath="/Users/me/.influxdbv2/engine/wal/0c3dd7d2d97f4b23/autogen/561"} 0
+--
+```
+
+### Compactions active
+
+Currently running [TSM](/influxdb/v2.2/reference/internals/storage-engine/#time-structured-merge-tree-tsm) compactions (by level).
+
+#### Example
+
+```sh
+# HELP storage_compactions_active Gauge of compactions (by level) currently running
+# TYPE storage_compactions_active gauge
+storage_compactions_active{bucket="ec3f82d1de90eddf",engine="tsm1",id="565",level="1",path="/Users/me/.influxdbv2/engine/data/ec3f82d1de90eddf/autogen/565",walPath="/Users/me/.influxdbv2/engine/wal/ec3f82d1de90eddf/autogen/565"} 0
+--
+```
+
+### Compactions since startup
+
+[TSM](/influxdb/v2.2/reference/internals/storage-engine/#time-structured-merge-tree-tsm) compactions (by level) since startup.
+
+#### Example
+
+```sh
+# HELP storage_compactions_duration_seconds Histogram of compactions by level since startup
+# TYPE storage_compactions_duration_seconds histogram
+storage_compactions_duration_seconds_bucket{bucket="0c3dd7d2d97f4b23",engine="tsm1",id="567",level="cache",path="/Users/me/.influxdbv2/engine/data/0c3dd7d2d97f4b23/autogen/567",walPath="/Users/me/.influxdbv2/engine/wal/0c3dd7d2d97f4b23/autogen/567",le="60"} 1
+storage_compactions_duration_seconds_bucket{bucket="0c3dd7d2d97f4b23",engine="tsm1",id="567",level="cache",path="/Users/me/.influxdbv2/engine/data/0c3dd7d2d97f4b23/autogen/567",walPath="/Users/me/.influxdbv2/engine/wal/0c3dd7d2d97f4b23/autogen/567",le="600"} 1
+storage_compactions_duration_seconds_bucket{bucket="0c3dd7d2d97f4b23",engine="tsm1",id="567",level="cache",path="/Users/me/.influxdbv2/engine/data/0c3dd7d2d97f4b23/autogen/567",walPath="/Users/me/.influxdbv2/engine/wal/0c3dd7d2d97f4b23/autogen/567",le="6000"} 1
+storage_compactions_duration_seconds_bucket{bucket="0c3dd7d2d97f4b23",engine="tsm1",id="567",level="cache",path="/Users/me/.influxdbv2/engine/data/0c3dd7d2d97f4b23/autogen/567",walPath="/Users/me/.influxdbv2/engine/wal/0c3dd7d2d97f4b23/autogen/567",le="+Inf"} 1
+storage_compactions_duration_seconds_sum{bucket="0c3dd7d2d97f4b23",engine="tsm1",id="567",level="cache",path="/Users/me/.influxdbv2/engine/data/0c3dd7d2d97f4b23/autogen/567",walPath="/Users/me/.influxdbv2/engine/wal/0c3dd7d2d97f4b23/autogen/567"} 0.167250668
+storage_compactions_duration_seconds_count{bucket="0c3dd7d2d97f4b23",engine="tsm1",id="567",level="cache",path="/Users/me/.influxdbv2/engine/data/0c3dd7d2d97f4b23/autogen/567",walPath="/Users/me/.influxdbv2/engine/wal/0c3dd7d2d97f4b23/autogen/567"} 1
+--
+```
+
+### Compactions failed
+
+Failed [TSM](/influxdb/v2.2/reference/internals/storage-engine/#time-structured-merge-tree-tsm) compactions (by level).
+
+#### Example
+
+```sh
+# HELP storage_compactions_failed Counter of TSM compactions (by level) that have failed due to error
+# TYPE storage_compactions_failed counter
+storage_compactions_failed{bucket="ec3f82d1de90eddf",engine="tsm1",id="565",level="1",path="/Users/me/.influxdbv2/engine/data/ec3f82d1de90eddf/autogen/565",walPath="/Users/me/.influxdbv2/engine/wal/ec3f82d1de90eddf/autogen/565"} 0
+--
+```
+
+### Compactions queued
+
+Queued [TSM](/influxdb/v2.2/reference/internals/storage-engine/#time-structured-merge-tree-tsm) compactions (by level).
+
+#### Example
+
+```sh
+# HELP storage_compactions_queued Counter of TSM compactions (by level) that are currently queued
+# TYPE storage_compactions_queued gauge
+storage_compactions_queued{bucket="0c3dd7d2d97f4b23",engine="tsm1",id="567",level="1",path="/Users/me/.influxdbv2/engine/data/0c3dd7d2d97f4b23/autogen/567",walPath="/Users/me/.influxdbv2/engine/wal/0c3dd7d2d97f4b23/autogen/567"} 0
+--
+```
+
+### Retention check duration
+
+Retention policy check duration (in seconds).
+
+#### Example
+
+```sh
+# HELP storage_retention_check_duration Histogram of duration of retention check (in seconds)
+# TYPE storage_retention_check_duration histogram
+storage_retention_check_duration_bucket{le="0.005"} 1
+storage_retention_check_duration_bucket{le="0.01"} 1
+storage_retention_check_duration_bucket{le="0.025"} 1
+storage_retention_check_duration_bucket{le="0.05"} 1
+storage_retention_check_duration_bucket{le="0.1"} 1
+storage_retention_check_duration_bucket{le="0.25"} 1
+storage_retention_check_duration_bucket{le="0.5"} 1
+storage_retention_check_duration_bucket{le="1"} 1
+storage_retention_check_duration_bucket{le="2.5"} 1
+storage_retention_check_duration_bucket{le="5"} 1
+storage_retention_check_duration_bucket{le="10"} 1
+storage_retention_check_duration_bucket{le="+Inf"} 1
+storage_retention_check_duration_sum 0.000351857
+storage_retention_check_duration_count 1
+--
+```
+
+### Shard disk size
+
+Disk size (in bytes) of the [shard](/influxdb/v2.2/reference/internals/shards/).
+
+#### Example
+
+```sh
+# HELP storage_shard_disk_size Gauge of the disk size for the shard
+# TYPE storage_shard_disk_size gauge
+storage_shard_disk_size{bucket="0c3dd7d2d97f4b23",engine="tsm1",id="561",path="/Users/me/.influxdbv2/engine/data/0c3dd7d2d97f4b23/autogen/561",walPath="/Users/me/.influxdbv2/engine/wal/0c3dd7d2d97f4b23/autogen/561"} 4.188743e+06
+--
+```
+
+### Shard fields created
+
+Number of [shard](/influxdb/v2.2/reference/internals/shards/) fields created.
+
+#### Example
+
+```sh
+# HELP storage_shard_fields_created Counter of the number of fields created
+# TYPE storage_shard_fields_created counter
+storage_shard_fields_created{bucket="0c3dd7d2d97f4b23",engine="tsm1",id="561",path="/Users/me/.influxdbv2/engine/data/0c3dd7d2d97f4b23/autogen/561",walPath="/Users/me/.influxdbv2/engine/wal/0c3dd7d2d97f4b23/autogen/561"} 0
+--
+```
+
+### Shard series
+
+Number of series in the [shard](/influxdb/v2.2/reference/internals/shards/) index.
+
+#### Example
+
+```sh
+# HELP storage_shard_series Gauge of the number of series in the shard index
+# TYPE storage_shard_series gauge
+storage_shard_series{bucket="0c3dd7d2d97f4b23",engine="tsm1",id="561",path="/Users/me/.influxdbv2/engine/data/0c3dd7d2d97f4b23/autogen/561",walPath="/Users/me/.influxdbv2/engine/wal/0c3dd7d2d97f4b23/autogen/561"} 38
+--
+```
+
+### Shard writes
+
+Number of [shard write](/influxdb/v2.2/reference/internals/shards/#shard-writes) requests.
+
+#### Example
+
+```sh
+# HELP storage_shard_write_count Count of the number of write requests
+# TYPE storage_shard_write_count counter
+storage_shard_write_count{bucket="0c3dd7d2d97f4b23",engine="tsm1",id="561",path="/Users/me/.influxdbv2/engine/data/0c3dd7d2d97f4b23/autogen/561",walPath="/Users/me/.influxdbv2/engine/wal/0c3dd7d2d97f4b23/autogen/561"} 0
+--
+```
+
+### Shard dropped points
+
+Number of [rejected points](/influxdb/v2.2/reference/glossary/#rejected-point) in [shard writes](/influxdb/v2.2/reference/internals/shards/#shard-writes).
+
+#### Example
+
+```sh
+# HELP storage_shard_write_dropped_sum Counter of the number of points dropped
+# TYPE storage_shard_write_dropped_sum counter
+storage_shard_write_dropped_sum{bucket="0c3dd7d2d97f4b23",engine="tsm1",id="561",path="/Users/me/.influxdbv2/engine/data/0c3dd7d2d97f4b23/autogen/561",walPath="/Users/me/.influxdbv2/engine/wal/0c3dd7d2d97f4b23/autogen/561"} 0
+--
+```
+
+### Shard writes with errors
+
+Number of [shard write](/influxdb/v2.2/reference/internals/shards/#shard-writes) requests with errors.
+
+#### Example
+
+```sh
+# HELP storage_shard_write_err_count Count of the number of write requests with errors
+# TYPE storage_shard_write_err_count counter
+storage_shard_write_err_count{bucket="0c3dd7d2d97f4b23",engine="tsm1",id="561",path="/Users/me/.influxdbv2/engine/data/0c3dd7d2d97f4b23/autogen/561",walPath="/Users/me/.influxdbv2/engine/wal/0c3dd7d2d97f4b23/autogen/561"} 0
+--
+```
+
+### Points in shard writes with errors
+
+Number of points in [shard write](/influxdb/v2.2/reference/internals/shards/#shard-writes) requests with errors.
+
+#### Example
+
+```sh
+# HELP storage_shard_write_err_sum Counter of the number of points for write requests with errors
+# TYPE storage_shard_write_err_sum counter
+storage_shard_write_err_sum{bucket="0c3dd7d2d97f4b23",engine="tsm1",id="561",path="/Users/me/.influxdbv2/engine/data/0c3dd7d2d97f4b23/autogen/561",walPath="/Users/me/.influxdbv2/engine/wal/0c3dd7d2d97f4b23/autogen/561"} 0
+--
+```
+
+### Points in shard writes
+
+Number of points in [shard write](/influxdb/v2.2/reference/internals/shards/#shard-writes) requests.
+
+#### Example
+
+```sh
+# HELP storage_shard_write_sum Counter of the number of points for write requests
+# TYPE storage_shard_write_sum counter
+storage_shard_write_sum{bucket="0c3dd7d2d97f4b23",engine="tsm1",id="561",path="/Users/me/.influxdbv2/engine/data/0c3dd7d2d97f4b23/autogen/561",walPath="/Users/me/.influxdbv2/engine/wal/0c3dd7d2d97f4b23/autogen/561"} 0
+--
+```
+
+### Shard data size
+
+Gauge of the data size (in bytes) for each [shard](/influxdb/v2.2/reference/internals/shards/).
+
+#### Example
+
+```sh
+# HELP storage_tsm_files_disk_bytes Gauge of data size in bytes for each shard
+# TYPE storage_tsm_files_disk_bytes gauge
+storage_tsm_files_disk_bytes{bucket="0c3dd7d2d97f4b23",engine="tsm1",id="561",path="/Users/me/.influxdbv2/engine/data/0c3dd7d2d97f4b23/autogen/561",walPath="/Users/me/.influxdbv2/engine/wal/0c3dd7d2d97f4b23/autogen/561"} 4.188743e+06
+--
+```
+
+### Shard files
+
+Number of files per [shard](/influxdb/v2.2/reference/internals/shards/).
+
+#### Example
+
+```sh
+# HELP storage_tsm_files_total Gauge of number of files per shard
+# TYPE storage_tsm_files_total gauge
+storage_tsm_files_total{bucket="0c3dd7d2d97f4b23",engine="tsm1",id="561",path="/Users/me/.influxdbv2/engine/data/0c3dd7d2d97f4b23/autogen/561",walPath="/Users/me/.influxdbv2/engine/wal/0c3dd7d2d97f4b23/autogen/561"} 1
+--
+```
+
+### WAL size
+
+[WAL](/influxdb/v2.2/reference/internals/storage-engine/#write-ahead-log-wal) size (in bytes).
+
+#### Example
+
+```sh
+# HELP storage_wal_size Gauge of size of WAL in bytes
+# TYPE storage_wal_size gauge
+storage_wal_size{bucket="0c3dd7d2d97f4b23",engine="tsm1",id="561",path="/Users/me/.influxdbv2/engine/data/0c3dd7d2d97f4b23/autogen/561",walPath="/Users/me/.influxdbv2/engine/wal/0c3dd7d2d97f4b23/autogen/561"} 0
+--
+```
+
+## WAL write attempts
+
+Cumulative number of write attempts to the [WAL](/influxdb/v2.2/reference/internals/storage-engine/#write-ahead-log-wal).
+
+#### Example
+
+```sh
+# HELP storage_wal_writes Number of write attempts to the WAL
+# TYPE storage_wal_writes counter
+storage_wal_writes{bucket="0c3dd7d2d97f4b23",engine="tsm1",id="561",path="/Users/me/.influxdbv2/engine/data/0c3dd7d2d97f4b23/autogen/561",walPath="/Users/me/.influxdbv2/engine/wal/0c3dd7d2d97f4b23/autogen/561"} 0
+--
+```
+
+## WAL failed write attempts
+
+Cumulative number of failed write attempts to the [WAL](/influxdb/v2.2/reference/internals/storage-engine/#write-ahead-log-wal).
+
+#### Example
+
+```sh
+# HELP storage_wal_writes_err Number of failed write attempts to the WAL
+# TYPE storage_wal_writes_err counter
+storage_wal_writes_err{bucket="0c3dd7d2d97f4b23",engine="tsm1",id="561",path="/Users/me/.influxdbv2/engine/data/0c3dd7d2d97f4b23/autogen/561",walPath="/Users/me/.influxdbv2/engine/wal/0c3dd7d2d97f4b23/autogen/561"} 0
+--
+```
+
+## Points dropped due to partial writes
+
+Number of points dropped due to partial writes.
+
+#### Example
+
+```sh
+# HELP storage_writer_dropped_points Histogram of number of points dropped due to partial writes
+# TYPE storage_writer_dropped_points histogram
+storage_writer_dropped_points_bucket{path="/Users/me/.influxdbv2/engine",le="10"} 0
+storage_writer_dropped_points_bucket{path="/Users/me/.influxdbv2/engine",le="100"} 0
+storage_writer_dropped_points_bucket{path="/Users/me/.influxdbv2/engine",le="1000"} 0
+storage_writer_dropped_points_bucket{path="/Users/me/.influxdbv2/engine",le="10000"} 0
+storage_writer_dropped_points_bucket{path="/Users/me/.influxdbv2/engine",le="100000"} 0
+storage_writer_dropped_points_bucket{path="/Users/me/.influxdbv2/engine",le="+Inf"} 0
+storage_writer_dropped_points_sum{path="/Users/me/.influxdbv2/engine"} 0
+storage_writer_dropped_points_count{path="/Users/me/.influxdbv2/engine"} 0
+--
+```
+
+## Points in shard write requests with errors
+
+Number of points in [shard write](/influxdb/v2.2/reference/internals/shards/#shard-writes) requests with errors.
+
+#### Example
+
+```sh
+# HELP storage_writer_err_points Histogram of number of points in errored shard write requests
+# TYPE storage_writer_err_points histogram
+storage_writer_err_points_bucket{path="/Users/me/.influxdbv2/engine",le="10"} 0
+storage_writer_err_points_bucket{path="/Users/me/.influxdbv2/engine",le="100"} 0
+storage_writer_err_points_bucket{path="/Users/me/.influxdbv2/engine",le="1000"} 0
+storage_writer_err_points_bucket{path="/Users/me/.influxdbv2/engine",le="10000"} 0
+storage_writer_err_points_bucket{path="/Users/me/.influxdbv2/engine",le="100000"} 0
+storage_writer_err_points_bucket{path="/Users/me/.influxdbv2/engine",le="+Inf"} 0
+storage_writer_err_points_sum{path="/Users/me/.influxdbv2/engine"} 0
+storage_writer_err_points_count{path="/Users/me/.influxdbv2/engine"} 0
+--
+```
+
+## Points in successful shard write requests
+
+Number of points in successful [shard write](/influxdb/v2.2/reference/internals/shards/#shard-writes) requests.
+
+#### Example
+
+```sh
+# HELP storage_writer_ok_points Histogram of number of points in successful shard write requests
+# TYPE storage_writer_ok_points histogram
+storage_writer_ok_points_bucket{path="/Users/me/.influxdbv2/engine",le="10"} 6
+storage_writer_ok_points_bucket{path="/Users/me/.influxdbv2/engine",le="100"} 6
+storage_writer_ok_points_bucket{path="/Users/me/.influxdbv2/engine",le="1000"} 8
+storage_writer_ok_points_bucket{path="/Users/me/.influxdbv2/engine",le="10000"} 20
+storage_writer_ok_points_bucket{path="/Users/me/.influxdbv2/engine",le="100000"} 24
+storage_writer_ok_points_bucket{path="/Users/me/.influxdbv2/engine",le="+Inf"} 24
+storage_writer_ok_points_sum{path="/Users/me/.influxdbv2/engine"} 125787
+storage_writer_ok_points_count{path="/Users/me/.influxdbv2/engine"} 24
+--
+```
+
+## Points in write requests
+
+Number of points in write requests.
+
+#### Example
+
+```sh
+# HELP storage_writer_req_points Histogram of number of points requested to be written
+# TYPE storage_writer_req_points histogram
+storage_writer_req_points_bucket{path="/Users/me/.influxdbv2/engine",le="10"} 6
+storage_writer_req_points_bucket{path="/Users/me/.influxdbv2/engine",le="100"} 6
+storage_writer_req_points_bucket{path="/Users/me/.influxdbv2/engine",le="1000"} 6
+storage_writer_req_points_bucket{path="/Users/me/.influxdbv2/engine",le="10000"} 14
+storage_writer_req_points_bucket{path="/Users/me/.influxdbv2/engine",le="100000"} 18
+storage_writer_req_points_bucket{path="/Users/me/.influxdbv2/engine",le="+Inf"} 18
+storage_writer_req_points_sum{path="/Users/me/.influxdbv2/engine"} 125787
+storage_writer_req_points_count{path="/Users/me/.influxdbv2/engine"} 18
+--
+```
+
+## Shard write request timeouts
+
+Cumulative number of [shard write](/influxdb/v2.2/reference/internals/shards/#shard-writes) request timeouts.
+
+#### Example
+
+```sh
+# HELP storage_writer_timeouts Number of shard write request timeouts
+# TYPE storage_writer_timeouts counter
+storage_writer_timeouts{path="/Users/me/.influxdbv2/engine"} 0
+--
+```
+
+## InfluxDB task statistics
+
+### Task executor errors
+
+Number of errors thrown by the executor with the type of error (ex. Invalid, Internal, etc.)
+
+#### Example
+
+```sh
+# HELP task_executor_errors_counter The number of errors thrown by the executor with the type of error (ex. Invalid, Internal, etc.)
+# TYPE task_executor_errors_counter counter
+task_executor_errors_counter{errorType="internal error",task_type="system"} 1183
+--
+```
+
+### Task executor promise queue usage
+
+Percent of the promise queue that is currently full.
+
+#### Example
+
+```sh
+# HELP task_executor_promise_queue_usage Percent of the promise queue that is currently full
+# TYPE task_executor_promise_queue_usage gauge
+task_executor_promise_queue_usage 0
+```
+
+### Task executor run duration
+
+Duration (in seconds) between a task run starting and finishing.
+
+#### Example
+
+```sh
+# HELP task_executor_run_duration The duration in seconds between a run starting and finishing.
+# TYPE task_executor_run_duration summary
+
+task_executor_run_duration{taskID="08017725990f6000",task_type="",quantile="0.5"} 0.865043855
+task_executor_run_duration{taskID="08017725990f6000",task_type="",quantile="0.9"} 0.865043855
+task_executor_run_duration{taskID="08017725990f6000",task_type="",quantile="0.99"} 0.865043855
+task_executor_run_duration_sum{taskID="08017725990f6000",task_type=""} 1.524920552
+task_executor_run_duration_count{taskID="08017725990f6000",task_type=""} 2
+--
+```
+
+### Task executor run latency seconds
+
+Latency between the task run's scheduled start time and the execution time, by task type.
+
+#### Example
+
+```sh
+# HELP task_executor_run_latency_seconds Records the latency between the time the run was due to run and the time the task started execution, by task type
+# TYPE task_executor_run_latency_seconds histogram
+task_executor_run_latency_seconds_bucket{task_type="system",le="0.005"} 0
+task_executor_run_latency_seconds_bucket{task_type="system",le="0.01"} 0
+task_executor_run_latency_seconds_bucket{task_type="system",le="0.025"} 0
+task_executor_run_latency_seconds_bucket{task_type="system",le="0.05"} 0
+task_executor_run_latency_seconds_bucket{task_type="system",le="0.1"} 0
+task_executor_run_latency_seconds_bucket{task_type="system",le="0.25"} 2
+task_executor_run_latency_seconds_bucket{task_type="system",le="0.5"} 6
+task_executor_run_latency_seconds_bucket{task_type="system",le="1"} 6
+task_executor_run_latency_seconds_bucket{task_type="system",le="2.5"} 6
+task_executor_run_latency_seconds_bucket{task_type="system",le="5"} 6
+task_executor_run_latency_seconds_bucket{task_type="system",le="10"} 6
+task_executor_run_latency_seconds_bucket{task_type="system",le="+Inf"} 6
+task_executor_run_latency_seconds_sum{task_type="system"} 2.237636
+task_executor_run_latency_seconds_count{task_type="system"} 6
+--
+```
+
+### Task executor run queue delta
+
+Duration (in seconds) between the task run's scheduled start time and the execution time.
+
+#### Example
+
+```sh
+# HELP task_executor_run_queue_delta The duration in seconds between a run being due to start and actually starting.
+# TYPE task_executor_run_queue_delta summary
+task_executor_run_queue_delta{taskID="08017725990f6000",task_type="",quantile="0.5"} 0.324742
+task_executor_run_queue_delta{taskID="08017725990f6000",task_type="",quantile="0.9"} 0.324742
+task_executor_run_queue_delta{taskID="08017725990f6000",task_type="",quantile="0.99"} 0.324742
+task_executor_run_queue_delta_sum{taskID="08017725990f6000",task_type=""} 0.674875
+task_executor_run_queue_delta_count{taskID="08017725990f6000",task_type=""} 2
+--
+```
+
+### Task executor total runs active
+
+Number of workers currently running tasks.
+
+#### Example
+
+```sh
+# HELP task_executor_total_runs_active Total number of workers currently running tasks
+# TYPE task_executor_total_runs_active gauge
+task_executor_total_runs_active 0
+```
+
+### Task executor total runs complete
+
+Number of task runs completed across all tasks, split out by success or failure.
+
+#### Example
+
+```sh
+# HELP task_executor_total_runs_complete Total number of runs completed across all tasks, split out by success or failure.
+# TYPE task_executor_total_runs_complete counter
+task_executor_total_runs_complete{status="failed",task_type="system"} 1384
+task_executor_total_runs_complete{status="success",task_type="system"} 6
+--
+```
+
+### Task executor workers busy
+
+Percent of total available workers that are currently busy.
+
+#### Example
+
+```sh
+# HELP task_executor_workers_busy Percent of total available workers that are currently busy
+# TYPE task_executor_workers_busy gauge
+task_executor_workers_busy 0
+```
+
+### Task scheduler current execution
+
+Number of tasks currently being executed.
+
+#### Example
+
+```sh
+# HELP task_scheduler_current_execution Number of tasks currently being executed
+# TYPE task_scheduler_current_execution gauge
+task_scheduler_current_execution 128
+```
+
+### Task scheduler execute delta
+
+Duration (in seconds) between a task run starting and finishing.
+
+#### Example
+
+```sh
+# HELP task_scheduler_execute_delta The duration in seconds between a run starting and finishing.
+# TYPE task_scheduler_execute_delta summary
+task_scheduler_execute_delta{quantile="0.5"} NaN
+--
+```
+
+### Task scheduler schedule delay
+
+Summary of the delay between when a task is scheduled to run and when it is told to execute.
+
+#### Example
+
+```sh
+# HELP task_scheduler_schedule_delay The duration between when a Item should be scheduled and when it is told to execute.
+# TYPE task_scheduler_schedule_delay summary
+task_scheduler_schedule_delay{quantile="0.5"} 120.001036
+task_scheduler_schedule_delay{quantile="0.9"} 120.001074
+task_scheduler_schedule_delay{quantile="0.99"} 120.001074
+task_scheduler_schedule_delay_sum 720.0033010000001
+task_scheduler_schedule_delay_count 6
+--
+```
+
+### Task scheduler total execute failure
+
+Number of times a scheduled task execution has failed.
+
+#### Example
+
+```sh
+# HELP task_scheduler_total_execute_failure Total number of times an execution has failed.
+# TYPE task_scheduler_total_execute_failure counter
+task_scheduler_total_execute_failure 0
+```
+
+### Task scheduler total execution calls
+
+Number of scheduled executions across all tasks.
+
+#### Example
+
+```sh
+# HELP task_scheduler_total_execution_calls Total number of executions across all tasks.
+# TYPE task_scheduler_total_execution_calls counter
+task_scheduler_total_execution_calls 4806
+```
+
+### Task scheduler total release calls
+
+Number of release requests.
+
+#### Example
+
+```sh
+# HELP task_scheduler_total_release_calls Total number of release requests.
+# TYPE task_scheduler_total_release_calls counter
+task_scheduler_total_release_calls 0
+```
+
+### Task scheduler total schedule calls
+
+Number of schedule requests.
+
+#### Example
+
+```sh
+# HELP task_scheduler_total_schedule_calls Total number of schedule requests.
+# TYPE task_scheduler_total_schedule_calls counter
+task_scheduler_total_schedule_calls 6
+```
+
+### Task scheduler total schedule fails
+
+Number of schedule requests that fail to schedule.
+
+#### Example
+
+```sh
+# HELP task_scheduler_total_schedule_fails Total number of schedule requests that fail to schedule.
+# TYPE task_scheduler_total_schedule_fails counter
+task_scheduler_total_schedule_fails 0
+```
diff --git a/content/influxdb/v2.2/reference/internals/runtime.md b/content/influxdb/v2.2/reference/internals/runtime.md
new file mode 100644
index 000000000..829ad7af9
--- /dev/null
+++ b/content/influxdb/v2.2/reference/internals/runtime.md
@@ -0,0 +1,353 @@
+---
+title: InfluxDB runtime
+description: >
+  Learn how to collect Go runtime profiling and tracing information to help with InfluxDB performance analysis and debugging.
+menu:
+  influxdb_2_2_ref:
+    name: Runtime
+    parent: InfluxDB internals
+weight: 103
+influxdb/2.2/tags: [go, internals, performance]
+---
+
+InfluxDB provides Go runtime profiles, trace, and other information
+useful for analyzing and debugging the server runtime execution.
+
+- [Overview of Go runtime profiles](#overview-of-go-runtime-profiles)
+- [Analyze Go runtime profiles](#analyze-go-runtime-profiles)
+- [Analyze the Go runtime trace](#analyze-the-go-runtime-trace)
+- [View the command line that invoked InfluxDB](#view-the-command-line-that-invoked-influxdb)
+- [View runtime configuration](#view-runtime-configuration)
+
+## Overview of Go runtime profiles
+
+A **Go runtime profile** is a collection of stack traces showing call sequences that led to instances of a particular event. InfluxDB provides profile data for the following events:
+
+- blocks
+- CPU usage
+- memory allocation
+- mutual exclusion (mutex)
+- OS thread creation
+
+When you send a profile request to InfluxDB, the [Golang runtime pprof package](https://pkg.go.dev/runtime/pprof) samples the events on the runtime to collect stack traces and statistics (e.g., number of bytes of memory for heap allocation events). For some profiles, you can set the number of seconds that InfluxDB will collect profile data.
+
+Once data collection is complete, InfluxDB returns the profile data. The default response format is a compressed protocol buffer in
+[profile.proto](https://github.com/google/pprof/blob/master/proto/profile.proto) format. **profile.proto** files are compatible with the [pprof](https://github.com/google/pprof) and [`go tool pprof`](https://go.dev/blog/pprof) analysis tools. For some profiles, InfluxDB provides an alternative human-readable plain text format with comments that translate to function calls and line numbers, but the `pprof` tools and **profile.proto** format offer the following advantages:
+
+- Read profiles from disk or HTTP.
+- Aggregate and compare multiple profiles of the same type.
+- Analyze and filter profile data.
+- Generate visualizations and reports.
+
+## Analyze Go runtime profiles
+
+Use the `/debug/pprof` InfluxDB endpoints to download all the profiles at once or request them individually.
+
+- [Get all runtime profiles](#get-all-runtime-profiles)
+- [Profile all memory allocations](#profile-all-memory-allocations)
+- [Profile blocking operations](#profile-blocking-operations)
+- [Profile CPU](#profile-cpu)
+- [Profile goroutines](#profile-goroutines)
+- [Profile heap memory allocations](#profile-heap-memory-allocations)
+- [Profile mutual exclusions](#profile-mutual-exclusions-mutexes)
+- [Profile thread creation](#profile-thread-creation)
+
+### Get all runtime profiles
+
+To download all runtime profiles at once, use an HTTP client to send a `GET` request to the `/debug/pprof/all` endpoint. `go tool pprof` can't fetch profiles directly from `/debug/pprof/all`.
+
+{{% api-endpoint method="GET" endpoint="http://localhost:8086/debug/pprof/all" %}}
+
+InfluxDB returns a gzipped tar file that contains the following profiles in the **profile.proto** format:
+
+- `profiles/allocs.pb.gz`: [profile all memory allocations](#profile-all-memory-allocations)
+- `profiles/block.pb.gz`: [profile blocking operations](#profile-blocking-operations)
+- `profiles/cpu.pb.gz`: _(Optional)_ [profile CPU](#profile-cpu).
+- `profiles/goroutine.pb.gz`: [profile goroutines](#profile-goroutines)
+- `profiles/heap.pb.gz`: [profile heap memory allocations](#profile-heap-memory-allocations)
+- `profiles/mutex.pb.gz`: [profile mutual exclusions](#profile-mutual-exclusions-mutexes)
+- `profiles/threadcreate.pb.gz`: [profile thread creation](#profile-thread-creation)
+
+| Option  | Include by |
+|:--------|:-----------|
+| Profile CPU | Pass a [duration of seconds](/influxdb/v2.2/reference/glossary/#duration) with the `cpu` query parameter in your request URL |
+
+Use an HTTP client like `curl` or `wget` to download profiles from `/debug/pprof/all`.
+
+#### Example
+
+```sh
+# Use `curl` to download a `.tar.gz` of all profiles after 10 seconds of CPU sampling.
+# Use `tar` to extract the profiles folder.
+
+curl "http://localhost:8086/debug/pprof/all?cpu=10s" | tar -xz
+
+# Analyze an extracted profile.
+
+go tool pprof profiles/heap.pb.gz
+```
+
+### Profile all memory allocations
+
+Profiles memory allocations and sets the default profile display to __alloc_space__,
+the total number of bytes allocated since the program began (including garbage-collected bytes).
+
+{{% api-endpoint method="GET" endpoint="http://localhost:8086/debug/pprof/allocs" %}}
+
+| Option  | Include by |
+|:--------|:-----------|
+| Seconds to sample | Pass an [unsigned integer](/influxdb/v2.2/reference/glossary/#unsigned-integer) with the `seconds` query parameter in your request URL |
+| Output plain text (mutually exclusive with `seconds`) | Pass `1` with the `debug` query parameter in your request URL |
+
+```sh
+# Analyze the profile in interactive mode.
+
+go tool pprof http://localhost:8086/debug/pprof/allocs
+
+# `pprof` returns the following prompt:
+#   Entering interactive mode (type "help" for commands, "o" for options)
+#   (pprof)
+
+# At the prompt, get the top N memory allocations.
+
+(pprof) top10
+```
+
+### Profile blocking operations
+
+Profiles operations that led to blocking on synchronization primitives and caused Go to suspend goroutine's execution.
+
+{{% api-endpoint method="GET" endpoint="http://localhost:8086/debug/pprof/block" %}}
+
+| Option  | Include by |
+|:--------|:-----------|
+| Output plain text | Pass `1` with the `debug` query parameter in your request URL |
+
+```sh
+# Analyze the profile in interactive mode.
+
+go tool pprof http://localhost:8086/debug/pprof/block
+
+# `pprof` returns the following prompt:
+#   Entering interactive mode (type "help" for commands, "o" for options)
+#   (pprof)
+
+#  At the prompt, get the top N entries.
+
+(pprof) top10
+```
+
+### Profile CPU
+
+Profiles program counters sampled from the execution stack. To download the profile, use an HTTP client to send a `GET` request to the `/debug/pprof/profile` endpoint. `go tool pprof` can't fetch the CPU profile directly.
+
+{{% api-endpoint method="GET" endpoint="http://localhost:8086/debug/pprof/profile" %}}
+
+| Option  | Include by |
+|:--------|:-----------|
+| Seconds to sample (default `30`) | Pass an [unsigned integer](/influxdb/v2.2/reference/glossary/#unsigned-integer) with the `seconds` query parameter in your request URL |
+
+Use an HTTP client like `curl` or `wget` to download the profile.
+
+#### Example
+
+```sh
+# Get the profile.
+
+curl http://localhost:8086/debug/pprof/profile -o cpu
+
+# Analyze the profile in interactive mode.
+
+go tool pprof ./cpu
+
+# At the prompt, get the top N functions most often running
+# or waiting during the sample period.
+
+(pprof) top10
+```
+
+Use the `seconds` query parameter to control the sampling duration.
+
+{{% note %}}
+
+`/debug/pprof/profile?seconds=SECONDS` returns the same CPU profile as `/debug/pprof/all?cpu=DURATION`.
+
+{{% /note %}}
+
+#### Example
+
+```sh
+# Get the CPU profile after 10 seconds of sampling.
+
+curl "http://localhost:8086/debug/pprof/profile?seconds=10" -o cpu
+
+# Get all profiles after 10 seconds of CPU sampling.
+
+curl "http://localhost:8086/debug/pprof/all?cpu=10s" -o all.tar.gz
+```
+
+### Profile goroutines
+
+Profiles all current goroutines.
+
+{{% api-endpoint method="GET" endpoint="http://localhost:8086/debug/pprof/goroutine" %}}
+
+| Option  | Include by |
+|:--------|:-----------|
+| Seconds to sample | Pass an [unsigned integer](/influxdb/v2.2/reference/glossary/#unsigned-integer) with the `seconds` query parameter in your request URL |
+| Output plain text (mutually exclusive with `seconds`) | Pass `1` with the `debug` query parameter in your request URL |
+
+#### Example
+
+```sh
+# Analyze the profile in interactive mode.
+
+go tool pprof http://localhost:8086/debug/pprof/goroutine
+
+# `pprof` returns the following prompt:
+#   Entering interactive mode (type "help" for commands, "o" for options)
+#   (pprof)
+
+#  At the prompt, get the top N entries.
+
+(pprof) top10
+```
+
+### Profile heap memory allocations
+
+Profiles heap, or memory allocations for live objects.
+
+{{% api-endpoint method="GET" endpoint="http://localhost:8086/debug/pprof/heap" %}}
+
+| Option  | Include by |
+|:--------|:-----------|
+| Run garbage control before sampling | Pass `1` with the `gc` query parameter in your request URL |
+| Seconds to sample | Pass an [unsigned integer](/influxdb/v2.2/reference/glossary/#unsigned-integer) with the `seconds` query parameter in your request URL |
+| Output plain text (mutually exclusive with `seconds`) | Pass `1` with the `debug` query parameter in your request URL |
+
+#### Example
+
+```sh
+# Analyze the profile in interactive mode.
+
+go tool pprof http://localhost:8086/debug/pprof/heap
+
+# `pprof` returns the following prompt:
+#   Entering interactive mode (type "help" for commands, "o" for options)
+#   (pprof)
+
+# At the prompt, get the top N memory-intensive nodes.
+
+(pprof) top10
+
+# pprof displays the list:
+#   Showing nodes accounting for 142.46MB, 85.43% of 166.75MB total
+#   Dropped 895 nodes (cum <= 0.83MB)
+#   Showing top 10 nodes out of 143
+```
+
+### Profile mutual exclusions (mutexes)
+
+Profiles holders of contended mutual exclusions (mutexes).
+
+{{% api-endpoint method="GET" endpoint="http://localhost:8086/debug/pprof/mutex" %}}
+
+| Option  | Include by |
+|:--------|:-----------|
+| Seconds to sample | Pass an [unsigned integer](/influxdb/v2.2/reference/glossary/#unsigned-integer) with the `seconds` query parameter in your request URL |
+| Output plain text (mutually exclusive with `seconds`) | Pass `1` with the `debug` query parameter in your request URL |
+
+#### Example
+
+```sh
+# Analyze the profile in interactive mode.
+
+go tool pprof http://localhost:8086/debug/pprof/mutex
+
+# `pprof` returns the following prompt:
+#   Entering interactive mode (type "help" for commands, "o" for options)
+#   (pprof)
+
+#  At the prompt, get the top N entries.
+
+(pprof) top10
+```
+
+### Profile thread creation
+
+Profiles operations that led to the creation of OS threads.
+
+{{% api-endpoint method="GET" endpoint="http://localhost:8086/debug/pprof/threadcreate" %}}
+
+| Option  | Include by |
+|:--------|:-----------|
+| Seconds to sample | Pass an [unsigned integer](/influxdb/v2.2/reference/glossary/#unsigned-integer) with the `seconds` query parameter in your request URL |
+| Output plain text (mutually exclusive with `seconds`) | Pass `1` with the `debug` query parameter in your request URL |
+
+#### Example
+
+```sh
+# Analyze the profile in interactive mode.
+
+go tool pprof http://localhost:8086/debug/pprof/threadcreate
+
+# `pprof` returns the following prompt:
+#   Entering interactive mode (type "help" for commands, "o" for options)
+#   (pprof)
+
+#  At the prompt, get the top N entries.
+
+(pprof) top10
+```
+
+## Analyze the Go runtime trace
+
+To trace execution events for InfluxDB, use the `/debug/pprof/trace`
+endpoint with `go tool trace`.
+
+{{% api-endpoint method="GET" endpoint="http://localhost:8086/debug/pprof/trace" %}}
+
+#### Example
+
+```sh
+# Download the trace file.
+
+curl http://localhost:8086/debug/pprof/trace -o trace.out
+
+# Analyze the trace.
+
+go tool trace ./trace.out
+```
+
+#### Generate a pprof-like profile from trace
+
+You can use `go tool trace` to generate _pprof-like_ profiles from
+a trace file and then analyze them with `go tool pprof`.
+
+#### Example
+
+```sh
+# Generate a profile from the downloaded trace file.
+
+go tool trace -pprof=PROFILE_TYPE ./trace.out > PROFILE_TYPE.pprof
+```
+
+Replace *`PROFILE_TYPE`* with one of the following [Golang profile types](https://pkg.go.dev/cmd/trace):
+
+- `net`: network blocking profile
+- `sync`: synchronization blocking profile
+- `syscall`: syscall blocking profile
+- `sched`: scheduler latency profile
+
+## View the command line that invoked InfluxDB
+
+To view the command, arguments, and command-line variables that invoked InfluxDB, use the `/debug/pprof/cmdline` endpoint.
+
+{{% api-endpoint method="GET" endpoint="http://localhost:8086/debug/pprof/cmdline" %}}
+
+`/debug/pprof/cmdline` returns the command line invocation in plain text.
+
+## View runtime configuration
+
+In InfluxDB v2.2+, you can view your active runtime configuration, including flags and environment variables.
+See how to [view your runtime server configuration](/influxdb/v2.2/reference/config-options/#view-your-runtime-server-configuration).
diff --git a/content/influxdb/v2.2/reference/internals/shards.md b/content/influxdb/v2.2/reference/internals/shards.md
new file mode 100644
index 000000000..7426750a0
--- /dev/null
+++ b/content/influxdb/v2.2/reference/internals/shards.md
@@ -0,0 +1,145 @@
+---
+title: InfluxDB shards and shard groups
+description: >
+  Learn the relationships between buckets, shards, and shard groups.
+  InfluxDB organizes time series data into **shards** when storing data to disk.
+  Shards are grouped into **shard groups**.
+menu:
+  influxdb_2_2_ref:
+    name: Shards & shard groups
+    parent: InfluxDB internals
+weight: 103
+influxdb/v2.2/tags: [storage, internals]
+related:
+  - /influxdb/v2.2/reference/internals/storage-engine/
+  - /influxdb/v2.2/organizations/buckets/
+  - /influxdb/v2.2/reference/cli/influx/bucket/
+---
+
+InfluxDB organizes time series data into **shards** when storing data to disk.
+Shards are grouped into **shard groups**.
+Learn the relationships between buckets, shards, and shard groups.
+
+- [Shards](#shards)
+- [Shard groups](#shard-groups)
+  - [Shard group duration](#shard-group-duration)
+  - [Shard group diagram](#shard-group-diagram)
+- [Shard life-cycle](#shard-life-cycle)
+  - [Shard precreation](#shard-precreation)
+  - [Shard writes](#shard-writes)
+  - [Shard compaction](#shard-compaction)
+- [Shard deletion](#shard-deletion)
+
+## Shards
+A shard contains encoded and compressed time series data for a given time range
+defined by the [shard group duration](#shard-group-duration).
+All points in a [series](#series) within the specified shard group duration are stored in the same shard.
+A single shard contains multiple series, one or more [TSM files](#tsm-time-structured-merge-tree) on disk,
+and belongs to a [shard group](#shard-groups).
+
+## Shard groups
+A shard group belongs to an InfluxDB [bucket](/influxdb/v2.2/reference/glossary/#bucket) and contains time series data for a specific time range defined by
+the [shard group duration](#shard-group-duration).
+
+{{% note %}}
+In **InfluxDB OSS**, a shard group typically contains only a single shard.
+In an **InfluxDB Enterprise 1.x cluster**, shard groups contain multiple shards
+distributed across multiple data nodes.
+{{% /note %}}
+
+### Shard group duration
+The **shard group duration** specifies the time range for each shard group and determines how often to create a new shard group.
+By default, InfluxDB sets the shard group duration according to
+the [retention period](/influxdb/v2.2/reference/glossary/#retention-period)
+of the bucket:
+
+| Bucket retention period     | Default shard group duration |
+|:-----------------------     | ----------------------------:|
+| less than 2 days            | 1h                           |
+| between 2 days and 6 months | 1d                           |
+| greater than 6 months       | 7d                           |
+
+##### Shard group duration configuration options
+To configure a custom bucket shard group duration, use the `--shard-group-duration`
+flag with the [`influx bucket create`](/influxdb/v2.2/reference/cli/influx/bucket/create/#create-a-custom-shard-group-duration)
+and [`influx bucket update`](/influxdb/v2.2/reference/cli/influx/bucket/update//#update-the-shard-group-duration-of-a-bucket) commands.
+
+{{% note %}}
+Shard group durations must be shorter than the bucket's retention period.
+{{% /note %}}
+
+To view your bucket's shard group duration, use the
+[`influx bucket list` command](/influxdb/v2.2/reference/cli/influx/bucket/list/).
+
+### Shard group diagram
+The following diagram represents a **bucket** with a **4d retention period**
+and a **1d shard group duration**:
+
+---
+
+{{< html-diagram/shards >}}
+
+---
+
+## Shard life-cycle
+
+### Shard precreation
+The InfluxDB **shard precreation service** pre-creates shards with future start
+and end times for each shard group based on the shard group duration.
+
+The precreator service does not pre-create shards for past time ranges.
+When backfilling historical data, InfluxDB creates shards for past time ranges as needed,
+resulting in temporarily lower write throughput.
+
+##### Shard precreation-related configuration settings
+- [`storage-shard-precreator-advance-period`](/influxdb/v2.2/reference/config-options/#storage-shard-precreator-advance-period)
+- [`storage-shard-precreator-check-interval`](/influxdb/v2.2/reference/config-options/#storage-shard-precreator-check-interval)
+
+### Shard writes
+InfluxDB writes time series data to un-compacted or "hot" shards.
+When a shard is no longer actively written to, InfluxDB [compacts](#shard-compaction) shard data, resulting in a "cold" shard.
+
+Typically, InfluxDB writes data to the most recent shard group, but when backfilling
+historical data, InfluxDB writes to older shards that must first be un-compacted.
+When the backfill is complete, InfluxDB re-compacts the older shards.
+
+### Shard compaction
+InfluxDB compacts shards at regular intervals to compress time series data and optimize disk usage.
+InfluxDB uses the following four compaction levels:
+
+- **Level 1 (L1):** InfluxDB flushes all newly written data held in an in-memory cache to disk.
+- **Level 2 (L2):** InfluxDB compacts up to eight L1-compacted files into one or more L2 files by
+     combining multiple blocks containing the same series into fewer blocks in one or more new files.
+- **Level 3 (L3):** InfluxDB iterates over L2-compacted file blocks (over a certain size)
+  and combines multiple blocks containing the same series into one block in a new file.
+- **Level 4 (L4):** **Full compaction**—InfluxDB iterates over L3-compacted file blocks
+  and combines multiple blocks containing the same series into one block in a new file.
+
+##### Shard compaction-related configuration settings
+- [`storage-compact-full-write-cold-duration`](/influxdb/v2.2/reference/config-options/#storage-compact-full-write-cold-duration)
+- [`storage-compact-throughput-burst`](/influxdb/v2.2/reference/config-options/#storage-compact-throughput-burst)
+- [`storage-max-concurrent-compactions`](/influxdb/v2.2/reference/config-options/#storage-max-concurrent-compactions)
+- [`storage-max-index-log-file-size`](/influxdb/v2.2/reference/config-options/#storage-max-index-log-file-size)
+- [`storage-series-file-max-concurrent-snapshot-compactions`](/influxdb/v2.2/reference/config-options/#storage-series-file-max-concurrent-snapshot-compactions)
+- [`storage-series-file-max-concurrent-snapshot-compactions`](/influxdb/v2.2/reference/config-options/#storage-series-file-max-concurrent-snapshot-compactions)
+
+## Shard deletion
+The InfluxDB **retention enforcement service** routinely checks for shard groups
+older than their bucket's retention period.
+Once the start time of a shard group is beyond the bucket's retention period,
+InfluxDB deletes the shard group and associated shards and TSM files.
+
+In buckets with an infinite retention period, shards remain on disk indefinitely.
+
+{{% note %}}
+#### InfluxDB only deletes cold shards
+InfluxDB only deletes **cold** shards.
+If backfilling data beyond a bucket's retention period, the backfilled data will
+remain on disk until the following occurs:
+
+1. The shard returns to a cold state.
+2. The retention enforcement service deletes the shard group.
+{{% /note %}}
+
+##### Retention enforcement-related configuration settings
+- [`storage-retention-check-interval`](/influxdb/v2.2/reference/config-options/#storage-retention-check-interval)
diff --git a/content/influxdb/v2.2/reference/internals/storage-engine.md b/content/influxdb/v2.2/reference/internals/storage-engine.md
new file mode 100644
index 000000000..47acfced2
--- /dev/null
+++ b/content/influxdb/v2.2/reference/internals/storage-engine.md
@@ -0,0 +1,115 @@
+---
+title: InfluxDB storage engine
+description: >
+  An overview of the InfluxDB storage engine architecture.
+weight: 101
+menu:
+  influxdb_2_2_ref:
+    name: Storage engine
+    parent: InfluxDB internals
+influxdb/v2.2/tags: [storage, internals]
+products: [oss]
+related:
+  - /resources/videos/tsm-engine/
+---
+
+The InfluxDB storage engine ensures that:
+
+- Data is safely written to disk
+- Queried data is returned complete and correct
+- Data is accurate (first) and performant (second)
+
+This document outlines the internal workings of the storage engine.
+This information is presented both as a reference and to aid those looking to maximize performance.
+
+The storage engine includes the following components:
+
+* [Write Ahead Log (WAL)](#write-ahead-log-wal)
+* [Cache](#cache)
+* [Time-Structed Merge Tree (TSM)](#time-structured-merge-tree-tsm)
+* [Time Series Index (TSI)](#time-series-index-tsi)
+
+## Writing data from API to disk
+
+The storage engine handles data from the point an API write request is received through writing data to the physical disk.
+Data is written to InfluxDB using [line protocol](/influxdb/v2.2/reference/syntax/line-protocol/) sent via HTTP POST request to the `/write` endpoint.
+Batches of [points](/influxdb/v2.2/reference/glossary/#point) are sent to InfluxDB, compressed, and written to a WAL for immediate durability.
+Points are also written to an in-memory cache and become immediately queryable.
+The in-memory cache is periodically written to disk in the form of [TSM](#time-structured-merge-tree-tsm) files.
+As TSM files accumulate, the storage engine combines and compacts accumulated them into higher level TSM files.
+
+{{% note %}}
+While points can be sent individually, for efficiency, most applications send points in batches.
+Points in a POST body can be from an arbitrary number of series, measurements, and tag sets.
+Points in a batch do not have to be from the same measurement or tagset.
+{{% /note %}}
+
+## Write Ahead Log (WAL)
+
+The **Write Ahead Log** (WAL) retains InfluxDB data when the storage engine restarts.
+The WAL ensures data is durable in case of an unexpected failure.
+
+When the storage engine receives a write request, the following steps occur:
+
+1. The write request is appended to the end of the WAL file.
+2. Data is written to disk using `fsync()`.
+3. The in-memory cache is updated.
+4. When data is successfully written to disk, a response confirms the write request was successful.
+
+`fsync()` takes the file and pushes pending writes all the way to the disk.
+As a system call, `fsync()` has a kernel context switch that's computationally expensive, but guarantees that data is safe on disk.
+
+When the storage engine restarts, the WAL file is read back into the in-memory database.
+InfluxDB then answers requests to the `/read` endpoint.
+
+## Cache
+
+The **cache** is an in-memory copy of data points currently stored in the WAL.
+The [WAL](#write-ahead-log-wal) and cache are separate entities and do not interact with each other.  The storage engine coordinates writes to both.
+
+The cache:
+
+- Organizes points by key (measurement, tag set, and unique field)
+  Each field is stored in its own time-ordered range.
+- Stores uncompressed data.
+- Gets updates from the WAL each time the storage engine restarts.
+  The cache is queried at runtime and merged with the data stored in TSM files.
+- Uses a maximum `maxSize` bytes of memory.
+
+Cache snapshots are cache objects currently being written to TSM files.
+They're kept in memory while flushing so they can be queried along with the cache.
+Queries to the storage engine merge data from the cache with data from the TSM files.
+Queries execute on a copy of the data that is made from the cache at query processing time.
+This way writes that come in while a query is running do not affect the result.
+Deletes sent to the cache clear the specified key or time range for a specified key.
+
+## Time-Structured Merge Tree (TSM)
+
+To efficiently compact and store data,
+the storage engine groups field values by series key, and then orders those field values by time.
+(A [series key](/influxdb/v2.2/reference/glossary/#series-key) is defined by measurement, tag key and value, and field key.)
+
+The storage engine uses a **Time-Structured Merge Tree** (TSM) data format.
+TSM files store compressed series data in a columnar format.
+To improve efficiency, the storage engine only stores differences (or *deltas*) between values in a series.
+Column-oriented storage lets the engine read by series key and omit extraneous data.
+
+After fields are stored safely in TSM files, the WAL is truncated and the cache is cleared.
+The **compaction** process creates read-optimized TSM files. The TSM compaction code is quite complex.
+However, the high-level goal is quite simple:
+organize values for a series together into long runs to best optimize compression and scanning queries.
+
+For more information on the TSM engine, watch the video below:
+
+{{< youtube C5sv0CtuMCw >}}
+
+## Time Series Index (TSI)
+
+As data cardinality (the number of series) grows, queries read more series keys and become slower.
+The **Time Series Index** ensures queries remain fast as data cardinality grows.
+The TSI stores series keys grouped by measurement, tag, and field.
+This allows the database to answer two questions well:
+
+- What measurements, tags, fields exist?
+  (This happens in meta queries.)
+- Given a measurement, tags, and fields, what series keys exist?
diff --git a/content/influxdb/v2.2/reference/internals/system-buckets.md b/content/influxdb/v2.2/reference/internals/system-buckets.md
new file mode 100644
index 000000000..690dd3b13
--- /dev/null
+++ b/content/influxdb/v2.2/reference/internals/system-buckets.md
@@ -0,0 +1,110 @@
+---
+title: InfluxDB system buckets
+description: >
+  InfluxDB system buckets contain time series data used by and generated from the
+  InfluxDB monitoring and alerting system and the task engine.
+menu:
+  influxdb_2_2_ref:
+    name: System buckets
+    parent: InfluxDB internals
+weight: 103
+influxdb/v2.2/tags: [buckets]
+related:
+  - /influxdb/v2.2/monitor-alert/
+  - /influxdb/v2.2/process-data/
+  - /{{< latest "flux" >}}/stdlib/influxdata/influxdb/monitor/check/
+  - /{{< latest "flux" >}}/stdlib/influxdata/influxdb/monitor/deadman/
+  - /{{< latest "flux" >}}/stdlib/influxdata/influxdb/monitor/from/
+  - /{{< latest "flux" >}}/stdlib/influxdata/influxdb/monitor/logs/
+  - /{{< latest "flux" >}}/stdlib/influxdata/influxdb/monitor/notify/
+---
+
+InfluxDB system buckets contain time series data used by and generated from the
+InfluxDB monitoring and alerting system and the task engine.
+
+Each InfluxDB organization includes the following system buckets:
+
+- [\_monitoring](#_monitoring-system-bucket)
+- [\_tasks](#_tasks-system-bucket)
+
+{{% note %}}
+The system bucket schemas below reference **InfluxDB data elements**.
+For more information, see [InfluxDB key concepts](/influxdb/v2.2/reference/key-concepts/data-elements/).
+{{% /note %}}
+
+## \_monitoring system bucket
+The `_monitoring` system bucket stores InfluxDB data used to
+[monitor data and send alerts](/influxdb/v2.2/monitor-alert/).
+
+**Data retention:** 7 days
+
+### \_monitoring bucket schema
+
+- **statuses** _(measurement)_
+    - **tags:**
+        - **\_check\_id:** check ID
+        - **\_check\_name:** check name
+        - **\_level:** level evaluated by the check (ok, info, warn, or crit)
+        - **\_source\_measurement:** original measurement queried by the check
+        - **\_type:** check type (threshold or deadman)
+        - _other tags inherited from queried data or added in the check configuration_
+    - **fields:**
+        - **\_message:** message generated by the check
+        - **\_source_timestamp:** original timestamp of the queried data
+        - _other fields inherited from queried data_
+- **notifications** _(measurement)_
+    - **tags:**
+        - **\_check\_id:** check ID that triggered the notification
+        - **\_check\_name:** check name that triggered the notification
+        - **\_level:** check-evaluated level that triggered the notification (ok, info, warn, or crit)
+        - **\_notification_endpoint_id:** notification endpoint ID
+        - **\_notification_endpoint_name:** notification endpoint name
+        - **\_notification_rule_id:** notification rule ID
+        - **\_notification_rule_name:** notification rule name
+        - **\_sent:** sent status (true or false)
+        - **\_source\_measurement:** original measurement queried by the check
+        - **\_type:** check type (threshold or deadman)
+        - _other tags inherited from queried data or added in the check configuration_
+    - **fields:**
+        - **\_message:** message generated by the check
+        - **\_source_timestamp:** original timestamp of the queried data
+        - **\_status_timestamp:** timestamp when the status (`_level`) was evaluated
+        - _other fields inherited from queried data_
+- {{% cloud-only %}}
+
+  **rejected_points** _(measurement)_
+  
+  - **tags:**
+    - **bucket:** ID of the bucket targeted in the write request
+    - **reason:** brief description of why InfluxDB rejected the point
+    - **field:** field name of the point (present if the point contained a field)
+    - **measurement:** measurement of the point (present if the point contained a measurement)
+    - **gotType:** InfluxDB field type in the point (present if type mismatch)
+    - **wantType:** InfluxDB field type in the bucket schema (present if type mismatch)
+  - **fields:**
+    - **_field:** `count` (for data type and schema conflicts) or `error` (for parsing errors)
+    - **_value:** `1` if `_field: "count"` or error details if `_field: "error"`
+    - **timestamp:** time the rejected point was logged
+  {{% /cloud-only %}}
+
+
+## \_tasks system bucket
+The `_tasks` system bucket stores data related to [InfluxDB task](/influxdb/v2.2/process-data/) executions.
+
+**Data retention:** 3 days
+
+### \_tasks bucket schema
+
+_A **task run** refers to a single task execution._
+
+- **runs** _(measurement)_
+    - **tags:**
+        - **status:** task run status (success or failed)
+        - **taskID:** task ID
+    - **fields:**
+        - **finishedAt:** timestamp when the task run finished
+        - **logs:** log output from the task run
+        - **requestedAt:** timestamp when the task run was requested
+        - **runID** task run ID
+        - **scheduledFor:** timestamp the task run was scheduled for
+        - **startedAt:** timestamp when the task run started
diff --git a/content/influxdb/v2.2/reference/key-concepts/_index.md b/content/influxdb/v2.2/reference/key-concepts/_index.md
new file mode 100644
index 000000000..2bc387b14
--- /dev/null
+++ b/content/influxdb/v2.2/reference/key-concepts/_index.md
@@ -0,0 +1,14 @@
+---
+title: InfluxDB key concepts
+description: >
+  Concepts related to InfluxDB.
+weight: 2
+menu:
+  influxdb_2_2_ref:
+    name: Key concepts
+influxdb/v2.2/tags: [key concepts]
+---
+
+Before working with InfluxDB {{< current-version >}}, it's helpful to learn a few key concepts. Browse the topics below to learn more.
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/reference/key-concepts/data-elements.md b/content/influxdb/v2.2/reference/key-concepts/data-elements.md
new file mode 100644
index 000000000..94bda54cd
--- /dev/null
+++ b/content/influxdb/v2.2/reference/key-concepts/data-elements.md
@@ -0,0 +1,207 @@
+---
+title: InfluxDB data elements
+description: >
+  InfluxDB structures data using elements such as timestamps, field keys, field values, tags, etc.
+weight: 102
+menu:
+  influxdb_2_2_ref:
+    parent: Key concepts
+    name: Data elements
+influxdb/v2.2/tags: [key concepts, schema]
+related: 
+  - /resources/videos/data-model-building-blocks/
+---
+
+InfluxDB {{< current-version >}} includes the following data elements:
+
+- [timestamp](#timestamp)
+- [field key](#field-key)
+- [field value](#field-value)
+- [field set](#field-set)
+- [tag key](#tag-key)
+- [tag value](#tag-value)
+- [tag set](#tag-set)
+- [measurement](#measurement)
+- [series](#series)
+- [point](#point)
+- [bucket](#bucket)
+- [bucket schema](#bucket-schema)
+- [organization](#organization)
+
+The sample data below is used to illustrate data elements concepts.
+_Hover over highlighted terms to get acquainted with InfluxDB terminology and layout._
+<a id="sample-data"></a>
+
+**bucket:**  `my_bucket`
+
+| _time                                              | _measurement                           | {{< tooltip "Tag key" "location" >}}    | {{< tooltip "Tag key" "scientist" >}} | _field                              | _value                             |
+|:-------------------                                |:------------                           |:-------                                |:------                                |:--                                  |:------                             |
+| 2019-08-18T00:00:00Z                               | census                                 | klamath                                | anderson                              | bees                                | 23                                 |
+| 2019-08-18T00:00:00Z                               | census                                 | portland                               | mullen                                | ants                                | 30                                 |
+| 2019-08-18T00:06:00Z                               | census                                 | klamath                                | anderson                              | bees                                | 28                                 |
+| {{< tooltip "Timestamp" "2019-08-18T00:06:00Z" >}} | {{< tooltip "measurement" "census" >}} | {{< tooltip "Tag value" "portland" >}} | {{< tooltip "Tag value" "mullen">}}   | {{< tooltip "Field key" "ants" >}} | {{< tooltip "Field value" "32" >}} |
+
+## Timestamp
+
+All data stored in InfluxDB has a `_time` column that stores timestamps. On disk, timestamps are stored in epoch nanosecond format. InfluxDB formats timestamps show the date and time in [RFC3339](/influxdb/v2.2/reference/glossary/#rfc3339-timestamp) UTC associated with data. Timestamp precision is important when you write data.
+
+## Measurement
+
+The  `_measurement` column shows the name of the measurement `census`. Measurement names are strings. A measurement acts as a container for tags, fields, and timestamps. Use a measurement name that describes your data. The name `census` tells us that the field values record the number of `bees` and `ants`.
+
+## Fields
+
+A field includes a field key stored in the `_field` column and a field value stored in the `_value` column.
+
+### Field key
+
+A field key is a string that represents the name of the field. In the sample data above, `bees` and `ants` are field keys.
+
+### Field value
+
+A field value represents the value of an associated field. Field values can be strings, floats, integers, or booleans. The field values in the sample data show the number of `bees` at specified times: `23`, and `28` and the number of `ants` at a specified time: `30` and `32`.
+
+### Field set
+
+A field set is a collection of field key-value pairs associated with a timestamp. The sample data includes the following field sets:
+
+```bash
+
+census bees=23i,ants=30i 1566086400000000000
+census bees=28i,ants=32i 1566086760000000000
+       -----------------
+           Field set
+
+```
+
+{{% note %}}
+**Fields aren't indexed:** Fields are required in InfluxDB data and are not indexed. Queries that filter field values must scan all field values to match query conditions. As a result, queries on tags > are more performant than queries on fields. **Store commonly queried metadata in tags.**
+{{% /note %}}
+
+## Tags
+
+The columns in the sample data, `location` and `scientist`, are tags.
+Tags include tag keys and tag values that are stored as strings and metadata.
+
+### Tag key
+
+The tag keys in the sample data are `location` and `scientist`.
+_For information about tag key requirements, see [Line protocol – Tag set](/influxdb/v2.2/reference/syntax/line-protocol/#tag-set)._
+
+### Tag value
+
+The tag key `location` has two tag values: `klamath` and `portland`.
+The tag key `scientist` also has two tag values: `anderson` and `mullen`.
+_For information about tag value requirements, see [Line protocol – Tag set](/influxdb/v2.2/reference/syntax/line-protocol/#tag-set)._
+
+### Tag set
+
+The collection of tag key-value pairs make up a tag set. The sample data includes the following four tag sets:
+
+```bash
+location = klamath, scientist = anderson
+location = portland, scientist = anderson
+location = klamath, scientist = mullen
+location = portland, scientist = mullen
+```
+
+{{% note %}}
+**Tags are indexed:** Tags are optional. You don't need tags in your data structure, but it's typically a good idea to include tags.
+Because tags are indexed, queries on tags are faster than queries on fields. This makes tags ideal for storing commonly-queried metadata.
+{{% /note %}}
+
+{{% note %}}
+Tags containing highly variable information like UUIDs, hashes, and random strings will lead to a large number of unique series in the database, known as **high series cardinality**. High series cardinality is a primary driver of high memory usage for many database workloads. See [series cardinality](/influxdb/v2.2/reference/glossary/#series-cardinality) for more information.   
+{{% /note %}}
+
+
+#### Why your schema matters
+
+If most of your queries focus on values in the fields, for example, a query to find when 23 bees were counted:
+
+```js
+from(bucket: "bucket-name")
+    |> range(start: 2019-08-17T00:00:00Z, stop: 2019-08-19T00:00:00Z)
+    |> filter(fn: (r) => r._field == "bees" and r._value == 23)
+```
+
+InfluxDB scans every field value in the dataset for `bees` before the query returns a response. If our sample `census` data grew to millions of rows, to optimize your query, you could rearrange your [schema](/influxdb/v2.2/reference/glossary/#schema) so the fields (`bees` and `ants`) becomes tags and the tags (`location` and `scientist`) become fields:
+
+| _time                | _measurement | {{< tooltip "Tag key" "bees" >}} | _field                                 | _value                                   |
+|:-------------------  |:------------ |:-------                          |:--                                     |:------                                   |
+| 2019-08-18T00:00:00Z | census       | 23                               | location                               | klamath                                  |
+| 2019-08-18T00:00:00Z | census       | 23                               | scientist                              | anderson                                 |
+| 2019-08-18T00:06:00Z | census       | {{< tooltip "Tag value" "28" >}} | {{< tooltip "Field key" "location" >}} | {{< tooltip "Field value" "klamath" >}}  |
+| 2019-08-18T00:06:00Z | census       | 28                               | scientist                              | anderson                                 |
+
+| _time                | _measurement | {{< tooltip "Tag key" "ants" >}} | _field                                 | _value                                   |
+|:-------------------  |:------------ |:-------                          |:--                                     |:------                                   |
+| 2019-08-18T00:00:00Z | census       | 30                               | location                               | portland                                 |
+| 2019-08-18T00:00:00Z | census       | 30                               | scientist                              | mullen                                   |
+| 2019-08-18T00:06:00Z | census       | {{< tooltip "Tag value" "32" >}} | {{< tooltip "Field key" "location" >}} | {{< tooltip "Field value" "portland" >}} |
+| 2019-08-18T00:06:00Z | census       | 32                               | scientist                              | mullen                                   |
+
+Now that `bees` and `ants` are tags, InfluxDB doesn't have to scan all `_field` and `_value` columns. This makes your queries faster.
+
+## Bucket schema
+
+In InfluxDB Cloud, a bucket with the `explicit` schema-type requires an explicit
+schema for each measurement.
+Measurements contain tags, fields, and timestamps.
+An explicit schema constrains the shape of data that can be written to that measurement.
+
+The following schema constrains `census` data:
+
+name      | type           | data_type
+|:------- |:---------------|:--------------------
+time      | timestamp      |
+location  | tag            | string
+scientist | tag            | string
+ants      | field          | integer
+bees      | field          | integer
+
+## Series
+
+Now that you're familiar with measurements, field sets, and tag sets, it's time to discuss series keys and series. A **series key** is a collection of points that share a measurement, tag set, and field key. For example, the [sample data](#sample-data) includes two unique series keys:
+
+| _measurement  | tag set                                                         | _field                             |
+|:------------- |:-------------------------------                                 |:------                             |
+| census        | {{< tooltip "Tag set" "location=klamath,scientist=anderson" >}} | {{< tooltip "Field key" "bees" >}} |
+| census        | location=portland,scientist=mullen                              | ants                               |
+
+A **series** includes timestamps and field values for a given series key. From the sample data, here's a **series key** and the corresponding **series**:
+
+```bash
+# series key
+census,location=klamath,scientist=anderson bees
+
+# series
+2019-08-18T00:00:00Z 23
+2019-08-18T00:06:00Z 28        
+```
+
+Understanding the concept of a series is essential when designing your [schema](/influxdb/v2.2/reference/glossary/#schema) and working with your data in InfluxDB.
+
+## Point
+
+A **point** includes the series key, a field value, and a timestamp. For example, a single point from the [sample data](#sample-data) looks like this:
+
+`2019-08-18T00:00:00Z census ants 30 portland mullen`
+
+## Bucket
+
+All InfluxDB data is stored in a bucket. A **bucket** combines the concept of a database and a retention period (the duration of time that each data point persists). A bucket belongs to an organization. For more information about buckets, see [Manage buckets](/influxdb/v2.2/organizations/buckets/).
+
+## Organization
+
+An InfluxDB **organization** is a workspace for a group of [users](/influxdb/v2.2/users/). All [dashboards](/influxdb/v2.2/visualize-data/dashboards/), [tasks](/influxdb/v2.2/process-data/), buckets, and users belong to an organization. For more information about organizations, see [Manage organizations](/influxdb/v2.2/organizations/).
+
+If you're just starting out, we recommend taking a look at the following guides:
+
+- [Get started](/influxdb/v2.2/get-started)
+- [Write data](/influxdb/v2.2/write-data)
+- [Query data](/influxdb/v2.2/query-data)
+
+For an overview of how these elements interconnect within InfluxDB's data model, watch the follwoing video:
+
+{{< youtube 3qTTqsL27lI >}}
\ No newline at end of file
diff --git a/content/influxdb/v2.2/reference/key-concepts/data-schema.md b/content/influxdb/v2.2/reference/key-concepts/data-schema.md
new file mode 100644
index 000000000..5a84819bd
--- /dev/null
+++ b/content/influxdb/v2.2/reference/key-concepts/data-schema.md
@@ -0,0 +1,63 @@
+---
+title: InfluxDB data schema
+description: >
+  InfluxDB uses a tabular data schema for displaying raw data in Data Explorer and for returning query results in annotated CSV syntax.
+aliases:
+  - /influxdb/v2.2/reference/key-concepts/table-structure
+weight: 103
+menu:
+  influxdb_2_2_ref:
+    parent: Key concepts
+    name: Data schema
+influxdb/v2.2/tags: [key concepts]
+---
+
+InfluxDB [data elements](/influxdb/v2.2/reference/key-concepts/data-elements/) are stored in **time-structured merge tree (TSM)** and **time series index (TSI)** files to efficiently compact stored data.
+
+InfluxDB also provides a **tabular data schema** that includes the following:
+
+- [Annotation rows](#annotation-rows)
+- [Header row](#header-row)
+- [Data rows](#data-rows)
+- [Other columns](#other-columns)
+- [Group keys](#group-keys)
+
+The **tabular data schema is used for the following**:
+
+- To [view raw data](/influxdb/v2.2/query-data/execute-queries/data-explorer/#view-raw-data) when [exploring metrics with InfluxDB](/influxdb/v2.2/visualize-data/explore-metrics)
+- To return query results in [annotated CSV syntax](/influxdb/v2.2/reference/syntax/annotated-csv/)
+
+## Annotation rows
+
+Annotation rows describe column properties, for example:
+
+- `#group`
+- `#datatype`
+- `#default`
+
+## Header row
+
+The header row defines column labels that describe data in each column, for example:
+
+- `table`
+- `_time`
+- `_value`
+- `_field`
+- `_measurement`
+-  tag key names (without underscore prefix): `tag-1`, `tag-2`
+
+## Data rows
+
+Each data row contains the data specified in the header row for one [point](/influxdb/v2.2/reference/glossary/#point).
+
+## Other columns
+
+In addition to the columns in each data row (specified in the header row), the following columns are optional:
+
+- `annotation`
+- `result`
+- `table`
+
+## Group keys
+
+Determine the contents of output tables in Flux by grouping records that share common values in specified columns. Learn more about [grouping your data with Flux](/influxdb/v2.2/query-data/flux/group-data/).
diff --git a/content/influxdb/v2.2/reference/key-concepts/design-principles.md b/content/influxdb/v2.2/reference/key-concepts/design-principles.md
new file mode 100644
index 000000000..513fbcadb
--- /dev/null
+++ b/content/influxdb/v2.2/reference/key-concepts/design-principles.md
@@ -0,0 +1,44 @@
+---
+title: InfluxDB design principles
+description: >
+  Principles and tradeoffs related to InfluxDB design.
+weight: 104
+menu:
+  influxdb_2_2_ref:
+    parent: Key concepts
+    name: Design principles
+influxdb/v2.2/tags: [key concepts, design principles]
+---
+
+InfluxDB implements optimal design principles for time series data. Some of these design principles may have associated tradeoffs in performance.
+
+- [Time-ordered data](#time-ordered-data)
+- [Strict update and delete permissions](#strict-update-and-delete-permissions)
+- [Handle read and write queries first](#handle-read-and-write-queries-first)
+- [Schemaless design](#schemaless-design)
+- [Datasets over individual points](#datasets-over-individual-points)
+- [Duplicate data](#duplicate-data)
+
+## Time-ordered data
+
+To improve performance, data is written in time-ascending order.
+
+## Strict update and delete permissions
+
+To increase query and write performance, InfluxDB tightly restricts **update** and **delete** permissions. Time series data is predominantly new data that is never updated. Deletes generally only affect data that isn't being written to, and contentious updates never occur.
+
+## Handle read and write queries first
+
+InfluxDB prioritizes read and write requests over strong consistency. InfluxDB returns results when a query is executed. Any transactions that affect the queried data are processed subsequently to ensure that data is eventually consistent. Therefore, if the ingest rate is high (multiple writes per ms), query results may not include the most recent data.
+
+## Schemaless design
+
+InfluxDB uses a schemaless design to better manage discontinuous data. Time series data are often ephemeral, meaning the data appears for a few hours and then goes away. For example, a new host that gets started and reports for a while and then gets shut down.
+
+## Datasets over individual points
+
+Because the data set is more important than an individual point, InfluxDB implements powerful tools to aggregate data and handle large data sets. Points are differentiated by timestamp and series, so don’t have IDs in the traditional sense.
+
+## Duplicate data
+
+To simplify conflict resolution and increase write performance, InfluxDB assumes data sent multiple times is duplicate data. Identical points aren't stored twice. If a new field value is submitted for a point, InfluxDB updates the point with the most recent field value. In rare circumstances, data may be overwritten. Learn more about [duplicate points](/influxdb/v2.2/write-data/best-practices/duplicate-points/).
diff --git a/content/influxdb/v2.2/reference/prometheus-metrics.md b/content/influxdb/v2.2/reference/prometheus-metrics.md
new file mode 100644
index 000000000..6dec81bf2
--- /dev/null
+++ b/content/influxdb/v2.2/reference/prometheus-metrics.md
@@ -0,0 +1,286 @@
+---
+title: Prometheus metric parsing formats
+description: >
+  When scraping [Prometheus-formatted metrics](https://prometheus.io/docs/concepts/data_model/)
+  and writing them to InfluxDB, metrics are parsed and stored in InfluxDB in different formats.
+menu:
+  influxdb_2_2_ref:
+    name: Prometheus metrics
+weight: 8
+influxdb/v2.2/tags: [prometheus]
+related:
+  - https://prometheus.io/docs/concepts/data_model/, Prometheus data model
+  - /influxdb/v2.2/write-data/developer-tools/scrape-prometheus-metrics/
+  - /{{< latest "flux" >}}/prometheus/, Work with Prometheus in Flux
+  - /{{< latest "telegraf" >}}/plugins/#input-prometheus, Telegraf Prometheus input plugin
+  - /influxdb/v2.2/write-data/no-code/scrape-data/
+  - /{{< latest "flux" >}}/stdlib/experimental/prometheus/scrape/
+---
+
+[Prometheus-formatted metrics](https://prometheus.io/docs/concepts/data_model/)
+are parsed and written to InfluxDB in one of two formats, depending on the scraping tool used:
+
+- [Metric version 1](#metric-version-1)
+- [Metric version 2](#metric-version-2)
+
+#### Scraping tools and parsing format
+{{% oss-only %}}
+
+| Scraping tool                                                                              |                               InfluxDB Metric version |
+| :----------------------------------------------------------------------------------------- | ----------------------------------------------------: |
+| [Telegraf Prometheus plugin](/{{< latest "telegraf" >}}/plugins/#input-prometheus)         | _Determined by `metric_version` configuration option_ |
+| [InfluxDB scraper](/influxdb/v2.2/write-data/no-code/scrape-data/)                         |                                                     1 |
+| Flux [`prometheus.scrape()`]({{< latest "flux" >}}/stdlib/experimental/prometheus/scrape/) |                                                     2 |
+
+{{% /oss-only %}}
+{{% cloud-only %}}
+
+| Scraping tool                                                                              |                               InfluxDB Metric version |
+| :----------------------------------------------------------------------------------------- | ----------------------------------------------------: |
+| [Telegraf Prometheus plugin](/{{< latest "telegraf" >}}/plugins/#input-prometheus)         | _Determined by `metric_version` configuration option_ |
+| Flux [`prometheus.scrape()`]({{< latest "flux" >}}/stdlib/experimental/prometheus/scrape/) |                                                     2 |
+
+{{% /cloud-only %}}
+
+## Metric version 1
+
+- **_time**: timestamp
+- **_measurement**: [Prometheus metric name](https://prometheus.io/docs/concepts/data_model/#metric-names-and-labels)
+  _(`_bucket`, `_sum`, and `_count` are trimmed from histogram and summary metric names)_
+- **\_field**: _depends on the [Prometheus metric type](https://prometheus.io/docs/concepts/metric_types/)_
+  - Counter: `counter`
+  - Gauge: `gauge`
+  - Histogram: _histogram bucket upper limits_, `count`, `sum`
+  - Summary: _summary quantiles_, `count`, `sum`
+- **_value**: [Prometheus metric value](https://prometheus.io/docs/concepts/data_model/#metric-names-and-labels)
+- **tags**: A tag for each [Prometheus label](https://prometheus.io/docs/concepts/data_model/#metric-names-and-labels)
+  _(except for histogram bucket upper limits (`le`) or summary quantiles (`quantile`))_.
+  The label name is the tag key and the label value is the tag value.
+
+### Example Prometheus query results
+The following are example Prometheus metrics scraped from the **InfluxDB OSS 2.x `/metrics`** endpoint:
+
+```sh
+# HELP go_memstats_alloc_bytes_total Total number of bytes allocated, even if freed.
+# TYPE go_memstats_alloc_bytes_total counter
+go_memstats_alloc_bytes_total 1.42276424e+09
+# HELP go_memstats_buck_hash_sys_bytes Number of bytes used by the profiling bucket hash table.
+# TYPE go_memstats_buck_hash_sys_bytes gauge
+go_memstats_buck_hash_sys_bytes 5.259247e+06
+# HELP task_executor_run_latency_seconds Records the latency between the time the run was due to run and the time the task started execution, by task type
+# TYPE task_executor_run_latency_seconds histogram
+task_executor_run_latency_seconds_bucket{task_type="system",le="0.25"} 4413
+task_executor_run_latency_seconds_bucket{task_type="system",le="0.5"} 11901
+task_executor_run_latency_seconds_bucket{task_type="system",le="1"} 12565
+task_executor_run_latency_seconds_bucket{task_type="system",le="2.5"} 12823
+task_executor_run_latency_seconds_bucket{task_type="system",le="5"} 12844
+task_executor_run_latency_seconds_bucket{task_type="system",le="10"} 12864
+task_executor_run_latency_seconds_bucket{task_type="system",le="+Inf"} 74429
+task_executor_run_latency_seconds_sum{task_type="system"} 4.256783538679698e+11
+task_executor_run_latency_seconds_count{task_type="system"} 74429
+# HELP task_executor_run_duration The duration in seconds between a run starting and finishing.
+# TYPE task_executor_run_duration summary
+task_executor_run_duration{taskID="00xx0Xx0xx00XX0x0",task_type="threshold",quantile="0.5"} 5.178160855
+task_executor_run_duration{taskID="00xx0Xx0xx00XX0x0",task_type="threshold",quantile="0.9"} 5.178160855
+task_executor_run_duration{taskID="00xx0Xx0xx00XX0x0",task_type="threshold",quantile="0.99"} 5.178160855
+task_executor_run_duration_sum{taskID="00xx0Xx0xx00XX0x0",task_type="threshold"} 2121.9758301650004
+task_executor_run_duration_count{taskID="00xx0Xx0xx00XX0x0",task_type="threshold"} 570
+```
+
+#### Resulting line protocol
+```
+go_memstats_alloc_bytes_total counter=1.42276424e+09
+go_memstats_buck_hash_sys_bytes gauge=5.259247e+06
+task_executor_run_latency_seconds,task_type=system 0.25=4413,0.5=11901,1=12565,2.5=12823,5=12844,10=12864,+Inf=74429,sum=4.256783538679698e+11,count=74429
+task_executor_run_duration,taskID=00xx0Xx0xx00XX0x0,task_type=threshold 0.5=5.178160855,0.9=5.178160855,0.99=5.178160855,sum=2121.9758301650004,count=570
+```
+
+{{< expand-wrapper >}}
+{{% expand "View version 1 tables when queried from InfluxDB" %}}
+| _time                     | _measurement                  | _field  |       _value |
+| :------------------------ | :---------------------------- | :------ | -----------: |
+| {{< flux/current-time >}} | go_memstats_alloc_bytes_total | counter | 1422764240.0 |
+
+| _time                     | _measurement                    | _field |    _value |
+| :------------------------ | :------------------------------ | :----- | --------: |
+| {{< flux/current-time >}} | go_memstats_buck_hash_sys_bytes | gauge  | 5259247.0 |
+
+| _time                     | _measurement                      | task_type | _field | _value |
+| :------------------------ | :-------------------------------- | :-------- | :----- | -----: |
+| {{< flux/current-time >}} | task_executor_run_latency_seconds | system    | 0.25   | 4413.0 |
+
+| _time                     | _measurement                      | task_type | _field |  _value |
+| :------------------------ | :-------------------------------- | :-------- | :----- | ------: |
+| {{< flux/current-time >}} | task_executor_run_latency_seconds | system    | 0.5    | 11901.0 |
+
+| _time                     | _measurement                      | task_type | _field |  _value |
+| :------------------------ | :-------------------------------- | :-------- | :----- | ------: |
+| {{< flux/current-time >}} | task_executor_run_latency_seconds | system    | 1      | 12565.0 |
+
+| _time                     | _measurement                      | task_type | _field |  _value |
+| :------------------------ | :-------------------------------- | :-------- | :----- | ------: |
+| {{< flux/current-time >}} | task_executor_run_latency_seconds | system    | 2.5    | 12823.0 |
+
+| _time                     | _measurement                      | task_type | _field |  _value |
+| :------------------------ | :-------------------------------- | :-------- | :----- | ------: |
+| {{< flux/current-time >}} | task_executor_run_latency_seconds | system    | 5      | 12844.0 |
+
+| _time                     | _measurement                      | task_type | _field |  _value |
+| :------------------------ | :-------------------------------- | :-------- | :----- | ------: |
+| {{< flux/current-time >}} | task_executor_run_latency_seconds | system    | +Inf   | 74429.0 |
+
+| _time                     | _measurement                      | task_type | _field |            _value |
+| :------------------------ | :-------------------------------- | :-------- | :----- | ----------------: |
+| {{< flux/current-time >}} | task_executor_run_latency_seconds | system    | sum    | 425678353867.9698 |
+
+| _time                     | _measurement                      | task_type | _field | _value |
+| :------------------------ | :-------------------------------- | :-------- | :----- | -----: |
+| {{< flux/current-time >}} | task_executor_run_latency_seconds | system    | count  |  74429.0 |
+
+| _time                     | _measurement               | task_type | _field |      _value |
+| :------------------------ | :------------------------- | :-------- | :----- | ----------: |
+| {{< flux/current-time >}} | task_executor_run_duration | threshold | 0.5    | 5.178160855 |
+
+| _time                     | _measurement               | task_type | _field |      _value |
+| :------------------------ | :------------------------- | :-------- | :----- | ----------: |
+| {{< flux/current-time >}} | task_executor_run_duration | threshold | 0.9    | 5.178160855 |
+
+| _time                     | _measurement               | task_type | _field |      _value |
+| :------------------------ | :------------------------- | :-------- | :----- | ----------: |
+| {{< flux/current-time >}} | task_executor_run_duration | threshold | 0.99   | 5.178160855 |
+
+| _time                     | _measurement               | task_type | _field |             _value |
+| :------------------------ | :------------------------- | :-------- | :----- | -----------------: |
+| {{< flux/current-time >}} | task_executor_run_duration | threshold | sum    | 2121.9758301650004 |
+
+| _time                     | _measurement               | task_type | _field | _value |
+| :------------------------ | :------------------------- | :-------- | :----- | -----: |
+| {{< flux/current-time >}} | task_executor_run_duration | threshold | count  |  570.0 |
+{{% /expand %}}
+{{< /expand-wrapper >}}
+
+## Metrics version 2
+
+- **_time**: timestamp
+- **_measurement**: `prometheus`
+- **_field**: [Prometheus metric name](https://prometheus.io/docs/concepts/data_model/#metric-names-and-labels)
+  _(`_bucket` is trimmed from histogram metric names)_
+- **_value**: [Prometheus metric value](https://prometheus.io/docs/concepts/data_model/#metric-names-and-labels)
+- **url**: URL metrics were scraped from
+- **tags**: A tag for each [Prometheus label](https://prometheus.io/docs/concepts/data_model/#metric-names-and-labels).
+  The label name is the tag key and the label value is the tag value.
+
+### Example Prometheus query results
+The following are example Prometheus metrics scraped from the **InfluxDB OSS 2.x `/metrics`** endpoint:
+
+```sh
+# HELP go_memstats_alloc_bytes_total Total number of bytes allocated, even if freed.
+# TYPE go_memstats_alloc_bytes_total counter
+go_memstats_alloc_bytes_total 1.42276424e+09
+# HELP go_memstats_buck_hash_sys_bytes Number of bytes used by the profiling bucket hash table.
+# TYPE go_memstats_buck_hash_sys_bytes gauge
+go_memstats_buck_hash_sys_bytes 5.259247e+06
+# HELP task_executor_run_latency_seconds Records the latency between the time the run was due to run and the time the task started execution, by task type
+# TYPE task_executor_run_latency_seconds histogram
+task_executor_run_latency_seconds_bucket{task_type="system",le="0.25"} 4413
+task_executor_run_latency_seconds_bucket{task_type="system",le="0.5"} 11901
+task_executor_run_latency_seconds_bucket{task_type="system",le="1"} 12565
+task_executor_run_latency_seconds_bucket{task_type="system",le="2.5"} 12823
+task_executor_run_latency_seconds_bucket{task_type="system",le="5"} 12844
+task_executor_run_latency_seconds_bucket{task_type="system",le="10"} 12864
+task_executor_run_latency_seconds_bucket{task_type="system",le="+Inf"} 74429
+task_executor_run_latency_seconds_sum{task_type="system"} 4.256783538679698e+11
+task_executor_run_latency_seconds_count{task_type="system"} 74429
+# HELP task_executor_run_duration The duration in seconds between a run starting and finishing.
+# TYPE task_executor_run_duration summary
+task_executor_run_duration{taskID="00xx0Xx0xx00XX0x0",task_type="threshold",quantile="0.5"} 5.178160855
+task_executor_run_duration{taskID="00xx0Xx0xx00XX0x0",task_type="threshold",quantile="0.9"} 5.178160855
+task_executor_run_duration{taskID="00xx0Xx0xx00XX0x0",task_type="threshold",quantile="0.99"} 5.178160855
+task_executor_run_duration_sum{taskID="00xx0Xx0xx00XX0x0",task_type="threshold"} 2121.9758301650004
+task_executor_run_duration_count{taskID="00xx0Xx0xx00XX0x0",task_type="threshold"} 570
+```
+
+#### Resulting line protocol
+{{< keep-url >}}
+```
+prometheus,url=http://localhost:8086/metrics go_memstats_alloc_bytes_total=1.42276424e+09
+prometheus,url=http://localhost:8086/metrics go_memstats_buck_hash_sys_bytes=5.259247e+06
+prometheus,url=http://localhost:8086/metrics,task_type=system,le=0.25 task_executor_run_latency_seconds=4413
+prometheus,url=http://localhost:8086/metrics,task_type=system,le=0.5 task_executor_run_latency_seconds=11901
+prometheus,url=http://localhost:8086/metrics,task_type=system,le=1 task_executor_run_latency_seconds=12565
+prometheus,url=http://localhost:8086/metrics,task_type=system,le=2.5 task_executor_run_latency_seconds=12823
+prometheus,url=http://localhost:8086/metrics,task_type=system,le=5 task_executor_run_latency_seconds=12844
+prometheus,url=http://localhost:8086/metrics,task_type=system,le=10 task_executor_run_latency_seconds=12864
+prometheus,url=http://localhost:8086/metrics,task_type=system,le=+Inf task_executor_run_latency_seconds=74429
+prometheus,url=http://localhost:8086/metrics,task_type=system task_executor_run_latency_seconds_sum=4.256783538679698e+11
+prometheus,url=http://localhost:8086/metrics,task_type=system task_executor_run_latency_seconds_count=74429
+prometheus,url=http://localhost:8086/metrics,taskID=00xx0Xx0xx00XX0x0,task_type=threshold quantile=0.5 task_executor_run_duration=5.178160855
+prometheus,url=http://localhost:8086/metrics,taskID=00xx0Xx0xx00XX0x0,task_type=threshold quantile=0.9 task_executor_run_duration=5.178160855
+prometheus,url=http://localhost:8086/metrics,taskID=00xx0Xx0xx00XX0x0,task_type=threshold quantile=0.99 task_executor_run_duration=5.178160855
+prometheus,url=http://localhost:8086/metrics,taskID=00xx0Xx0xx00XX0x0,task_type=threshold task_executor_run_duration_sum=2121.9758301650004
+prometheus,url=http://localhost:8086/metrics,taskID=00xx0Xx0xx00XX0x0,task_type=threshold task_executor_run_duration_count=570
+```
+
+{{< expand-wrapper >}}
+{{% expand "View version 2 tables when queried from InfluxDB" %}}
+| _time                     | _measurement | url                           | _field                        |       _value |
+| :------------------------ | :----------- | :---------------------------- | :---------------------------- | -----------: |
+| {{< flux/current-time >}} | prometheus   | http://localhost:8086/metrics | go_memstats_alloc_bytes_total | 1422764240.0 |
+
+| _time                     | _measurement | url                           | _field                          |    _value |
+| :------------------------ | :----------- | :---------------------------- | :------------------------------ | --------: |
+| {{< flux/current-time >}} | prometheus   | http://localhost:8086/metrics | go_memstats_buck_hash_sys_bytes | 5259247.0 |
+
+| _time                     | _measurement | task_type | url                           | le   | _field                            | _value |
+| :------------------------ | :----------- | :-------- | :---------------------------- | :--- | :-------------------------------- | -----: |
+| {{< flux/current-time >}} | prometheus   | system    | http://localhost:8086/metrics | 0.25 | task_executor_run_latency_seconds |   4413 |
+
+| _time                     | _measurement | task_type | url                           | le  | _field                            | _value |
+| :------------------------ | :----------- | :-------- | :---------------------------- | :-- | :-------------------------------- | -----: |
+| {{< flux/current-time >}} | prometheus   | system    | http://localhost:8086/metrics | 0.5 | task_executor_run_latency_seconds |  11901 |
+
+| _time                     | _measurement | task_type | url                           | le  | _field                            | _value |
+| :------------------------ | :----------- | :-------- | :---------------------------- | :-- | :-------------------------------- | -----: |
+| {{< flux/current-time >}} | prometheus   | system    | http://localhost:8086/metrics | 1   | task_executor_run_latency_seconds |  12565 |
+
+| _time                     | _measurement | task_type | url                           | le  | _field                            | _value |
+| :------------------------ | :----------- | :-------- | :---------------------------- | :-- | :-------------------------------- | -----: |
+| {{< flux/current-time >}} | prometheus   | system    | http://localhost:8086/metrics | 2.5 | task_executor_run_latency_seconds |  12823 |
+
+| _time                     | _measurement | task_type | url                           | le  | _field                            | _value |
+| :------------------------ | :----------- | :-------- | :---------------------------- | :-- | :-------------------------------- | -----: |
+| {{< flux/current-time >}} | prometheus   | system    | http://localhost:8086/metrics | 5   | task_executor_run_latency_seconds |  12844 |
+
+| _time                     | _measurement | task_type | url                           | le   | _field                            | _value |
+| :------------------------ | :----------- | :-------- | :---------------------------- | :--- | :-------------------------------- | -----: |
+| {{< flux/current-time >}} | prometheus   | system    | http://localhost:8086/metrics | +Inf | task_executor_run_latency_seconds |  74429 |
+
+| _time                     | _measurement | task_type | url                           | _field                                |            _value |
+| :------------------------ | :----------- | :-------- | :---------------------------- | :------------------------------------ | ----------------: |
+| {{< flux/current-time >}} | prometheus   | system    | http://localhost:8086/metrics | task_executor_run_latency_seconds_sum | 425678353867.9698 |
+
+| _time                     | _measurement | task_type | url                           | _field                                  | _value |
+| :------------------------ | :----------- | :-------- | :---------------------------- | :-------------------------------------- | -----: |
+| {{< flux/current-time >}} | prometheus   | system    | http://localhost:8086/metrics | task_executor_run_latency_seconds_count |  74429 |
+
+| _time                     | _measurement | task_type | taskID            | url                           | quantile | _field                     |      _value |
+| :------------------------ | :----------- | :-------- | :---------------- | :---------------------------- | :------- | :------------------------- | ----------: |
+| {{< flux/current-time >}} | prometheus   | threshold | 00xx0Xx0xx00XX0x0 | http://localhost:8086/metrics | 0.5      | task_executor_run_duration | 5.178160855 |
+
+| _time                     | _measurement | task_type | taskID            | url                           | quantile | _field                     |      _value |
+| :------------------------ | :----------- | :-------- | :---------------- | :---------------------------- | :------- | :------------------------- | ----------: |
+| {{< flux/current-time >}} | prometheus   | threshold | 00xx0Xx0xx00XX0x0 | http://localhost:8086/metrics | 0.9      | task_executor_run_duration | 5.178160855 |
+
+| _time                     | _measurement | task_type | taskID            | url                           | quantile | _field                     |      _value |
+| :------------------------ | :----------- | :-------- | :---------------- | :---------------------------- | :------- | :------------------------- | ----------: |
+| {{< flux/current-time >}} | prometheus   | threshold | 00xx0Xx0xx00XX0x0 | http://localhost:8086/metrics | 0.99     | task_executor_run_duration | 5.178160855 |
+
+| _time                     | _measurement | task_type | taskID            | url                           | _field                         |             _value |
+| :------------------------ | :----------- | :-------- | :---------------- | :---------------------------- | :----------------------------- | -----------------: |
+| {{< flux/current-time >}} | prometheus   | threshold | 00xx0Xx0xx00XX0x0 | http://localhost:8086/metrics | task_executor_run_duration_sum | 2121.9758301650004 |
+
+| _time                     | _measurement | task_type | taskID            | url                           | _field                           | _value |
+| :------------------------ | :----------- | :-------- | :---------------- | :---------------------------- | :------------------------------- | -----: |
+| {{< flux/current-time >}} | prometheus   | threshold | 00xx0Xx0xx00XX0x0 | http://localhost:8086/metrics | task_executor_run_duration_count |    570 |
+{{% /expand %}}
+{{< /expand-wrapper >}}
diff --git a/content/influxdb/v2.2/reference/release-notes/_index.md b/content/influxdb/v2.2/reference/release-notes/_index.md
new file mode 100644
index 000000000..28bcdb0aa
--- /dev/null
+++ b/content/influxdb/v2.2/reference/release-notes/_index.md
@@ -0,0 +1,12 @@
+---
+title: Release notes
+description: Find important information about what's included in new versions of InfluxData products.
+menu:
+  influxdb_2_2_ref:
+    name: Release notes
+weight: 1
+---
+
+Find important information about what's included in new versions of our products:
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/reference/release-notes/influx-cli.md b/content/influxdb/v2.2/reference/release-notes/influx-cli.md
new file mode 100644
index 000000000..2173d7e23
--- /dev/null
+++ b/content/influxdb/v2.2/reference/release-notes/influx-cli.md
@@ -0,0 +1,135 @@
+---
+title: influx CLI release notes
+description: Important changes and and what's new in each version of the influx command line interface (CLI).
+weight: 103
+menu:
+  influxdb_2_2_ref:
+    parent: Release notes
+    name: influx CLI 
+---
+
+## v2.3 [2022-04-08]
+
+## Features
+
+- Add [`influx remote`](/{{< latest "influxdb" >}}/reference/cli/influx/remote/) command.
+- Add [`influx replication`](/{{< latest "influxdb" >}}/reference/cli/influx/replication/) command.
+- Enhanced error messaging for InfluxDB and OSS specific commands.
+- Add `api/v2/config` endpoint to display the runtime configuration (for example, when you run `influxd print-config`). This endpoint lets you review runtime configuration while the instance is live.
+
+## Bug fixes
+
+- `Auth create` command supports multiple buckets.
+- Use `influx-debug-id` header for tracing.
+- Duration parser shows duration missing units on error.
+- Template apply uses improved diff checking.
+- Fix error applying `-e jsonnet` template.
+
+## v2.2.1 [2021-11-09]
+
+This release includes two new bug fixes.
+
+## Bug fixes
+
+- Improve error messages for unknown subcommands (`Error: command “…” not recognized.`) by describing how to 
+run `./influx --help` to see a list of valid commands. Thanks @slai!
+
+- Ensure `org members remove` API calls successfully remove a member from an organization by fixing accidental swap of `orgID` and `userID`. Thanks @geek981108!
+
+## v2.2.0 [2021-10-21]
+
+This release includes three new features and bug fixes.
+
+## Features
+
+This release makes it easier to create API tokens with the `influx` CLI, adds support for viewing more than 20 buckets using `influx bucket list`, and adds a shorthand flag for bucket (`-b`) to `influx delete`.
+
+{{% oss-only %}}
+
+### Create an Operator token in the influx CLI
+
+Add the ability to use the `influx` CLI to [create an Operator token](/influxdb/v2.0/security/tokens/#operator-token) with read and write permissions to all resources in all organizations available in InfluxDB. (Note, this is the same permissions generated for the initial token created by `influx setup` or `influxd upgrade`.)
+
+{{% /oss-only %}}
+
+### Create an All-Access token in the influx CLI
+
+Add the ability to use the `influx` CLI to [create an All-Access API token](/influxdb/cloud/security/tokens/create-token/#create-a-token-using-the-influx-cli) with read and write permissions to all resources in an organization.
+
+### View more buckets in the influx CLI
+
+Update [`influx bucket list`](/influxdb/cloud/reference/cli/influx/bucket/list/) with pagination to support displaying more than 20 buckets. By default, buckets are fetched in batches of 20; set `--page-size` to override this default value. You may also limit the total number of buckets to display with `--limit` (by default, there's no limit).
+
+### New bucket shorthand for influx delete
+
+Add the shorthand flag `-b` for `--bucket` to [`influx delete`](/influxdb/cloud/reference/cli/influx/delete/).
+
+## Bug fixes
+
+- Detect and warn when the Operator token is changed using `influx restore` (either setting a new `--active` config or updating the `INFLUX_TOKEN` variable).
+- Set newly-created connection configuration as active in `influx setup`.
+- Embed timezone data into Windows builds to avoid errors.
+
+## v2.1.1 [2021-09-24]
+
+## Go version 
+
+Upgrade to Go 1.17.
+
+## Bug fixes 
+
+- Fix shell completion for top-level `influx` commands.
+- Make global `--http-debug` flag visible in help text.
+- Don't set empty strings for IDs in permission resources.
+- Detect and error out on incorrect positional arguments.
+- Respect value of `--host` flag when writing CLI configs in `setup`.
+
+## v2.1.0 [2021-07-29]
+
+## New repository
+
+This is the initial release of the `influx` CLI from the `influxdata/influx-cli` GitHub repository.
+
+## Breaking changes
+
+### `influx write` skip-header parsing
+
+To simplify the CLI parser, the `write` command no longer supports `--skipHeader`
+as short-hand for `--skipHeader 1`.
+
+### Stricter input validation for `influx template` commands
+
+The `apply`, `export`, and `stacks` commands now raise errors when CLI options fail to parse instead of silently discarding bad inputs.
+This change was made to help users debug when their commands fail to execute as expected.
+
+### Server-side template summarization and validation
+
+The `template` and `template validate` commands now use an API request to the server to perform their logic, instead of performing the work on the client-side.
+Offline summarization and validation is no longer supported.
+This change was made to avoid significant code duplication between `influxdb` and `influx CLI`, and to allow server-side template logic to evolve without requiring coordinated CLI changes.
+
+### `influx stacks --json` output conventions
+
+The output of `influx stacks --json` previously used an UpperCamelCase naming convention for most keys.
+The command now uses lowerCamelCase consistently for all objects keys, matching the schema returned by the API.
+
+## Features
+
+- Add global `--http-debug` flag to all `influx` commands to help inspect communication with InfluxDB servers.
+- Update [`bucket create`](/influxdb/cloud/reference/cli/influx/bucket/create/) to allow setting a schema type.
+- Update [`bucket list`](/influxdb/cloud/reference/cli/influx/bucket/list/) to display schema types.
+- Bind [`--skip-verify`](/influxdb/cloud/reference/cli/influx/org/members/add/#flags) flag to the `INFLUX_SKIP_VERIFY` environment variable.
+- (InfluxDB Cloud only) Add [`buck
+- (InfluxDB OSS only) Updates to `backup` and `restore`:
+  - Reimplement [`backup`](/influxdb/cloud/reference/cli/influx/backup/) to support downloading embedded SQL store from InfluxDB 2.0 or later.
+  - Add [`--compression`](/influxdb/v2.0/reference/cli/influx/backup/_index.md) flag to support GZIP compression of downloaded files.
+  - Reimplement `restore` to support uploading embedded SQL store from InfluxDB v2.1.x.
+- (InfluxDB OSS only) Add [`--password`](/influxdb/cloud/reference/cli/influx/user/password/) flag to `user password` command to allow bypassing interactive prompt.
+
+## Bug fixes
+
+- Fix interactive password collection and color rendering in PowerShell.
+- `org members list` no longer hangs on organizations with more than 10 members.
+- Detect and warn when inputs to `write` contain standalone CR characters.
+- `dashboards` command now accepts `--org` flag, or falls back to default org in config.
+- Return a consistent error when responses fail to decode, including hints for OSS-only and Cloud-only commands.
diff --git a/content/influxdb/v2.2/reference/release-notes/influxdb.md b/content/influxdb/v2.2/reference/release-notes/influxdb.md
new file mode 100644
index 000000000..5f9d5f33e
--- /dev/null
+++ b/content/influxdb/v2.2/reference/release-notes/influxdb.md
@@ -0,0 +1,1767 @@
+---
+title: InfluxDB v2.2 release notes
+description: Important changes and what's new in each version of InfluxDB.
+menu:
+  influxdb_2_2_ref:
+    name: InfluxDB
+    parent: Release notes
+weight: 101
+---
+
+## v2.2 [2022-04-06]
+
+This release includes the following new [features](#features) and several [bug fixes](#bug-fixes).
+
+### Features
+
+- [Technical preview: replicate data remotely](#technical-preview-replicate-data-remotely)
+- [Flux updates](#flux-updates)
+- [Build maintenance](#build-maintenance)
+- [Task metadata](#task-metadata)
+- [Troubleshoot with new metrics](#troubleshoot-with-new-metrics)
+- [Display runtime configuration in use by `influxd`](#display-runtime-configuration-in-use-by-influxd)
+- [Recover user credentials](#recover-user-credentials)
+- [Security updates](#security-updates), including a new `hardening-enabled` option to enable additional security.
+
+#### Technical preview: replicate data remotely
+
+- Add the option to [Replicate data from InfluxDB OSS to InfluxDB Cloud](/influxdb/v2.2/write-data/replication).
+
+  This [**technical preview**](/influxdb/v2.2/reference/glossary/#technical-preview) feature lets you create a durable subscription on a per bucket basis for the purposes of replicating data on-write from an InfluxDB OSS instance to InfluxDB Cloud.
+  - Lets you store, analyze, and aggregate data locally while also forwarding newly arriving data to a centralized InfluxDB Cloud account.
+  - If InfluxDB OSS loses connectivity to InfluxDB Cloud, the data gets sent when network connectivity is reestablished.
+  - Configuration options include a maximum buffer size and data age restrictions to restrict the amount of data stored on disk.
+
+#### Flux updates
+
+- Update to [Flux v0.150.0](/flux/v0.x/release-notes/#v01500-2022-01-19).
+- Add option to log Flux queries that are cancelled because of server shutdown.
+
+#### Build maintenance
+
+- Upgrade `protobuf` library.
+
+#### Task metadata
+
+- Add option to pass `type=basic` to [`/api/v2/tasks`](/influxdb/v2.2/api/#tag/Tasks) to return task metadata without the query text.
+
+#### Troubleshoot with new metrics
+
+To assist with troubleshooting and operational management, expose the following metrics in Prometheus Exposition Format.
+
+##### TSM compaction metrics
+
+- `storage_compaction`
+- `storage_compactions_active`
+- `storage_compactions_duration_seconds_bucket`
+- `storage_compactions_duration_seconds_count`
+- `storage_compactions_duration_seconds_sum`
+- `storage_compactions_queued`
+- `storage_compactions_total`
+
+##### Failed to add to replication queue metrics
+
+- `PointsFailedToQueue`
+- `BytesFailedToQueue`
+
+##### Write status metrics
+
+- `pointsWriteRequested`
+- `pointsWriteOk`
+- `pointsWriteDropped`
+- `pointsWriteErr`
+- `timeout`
+
+##### Disk size metrics per shard
+
+- `total`: number of files per shard
+- `disk_bytes`: data size in bytes for each shard
+
+##### Cache subsystem metrics
+
+- `inuse_bytes`: Current memory consumption of cache
+- `diskBytes`: Size of most recent snapshot"
+- `latest_snapshot`: Unix time of most recent snapshot
+- `writes_total`: Counter of all writes to cache
+- `writes_err`: Counter of failed writes to cache
+- `writes_dropped`: Counter of writes (with any dropped points) to cache
+
+##### WAL subsystem metrics
+
+- `size`: Size of WAL in bytes
+- `writes`: Number of write attempts to the WAL
+- `writes_err`: Number of failed write attempts to the WAL
+
+See [InfluxDB OSS metrics](/influxdb/v2.2/reference/internals/metrics/) for additional detail.
+
+#### Display runtime configuration in use by `influxd`
+
+- Add `api/v2/config` endpoint to display the runtime configuration (for example, when you run `influxd print-config`). This endpoint lets you review runtime configuration while the instance is live.
+
+#### Recover user credentials
+
+To recover user credentials, use [`influx recovery user list`](/influxdb/v2.2/reference/cli/influxd/recovery/user/list/) to retrieve a list of users, and then use [`influx recovery user update`](/influxdb/v2.2/reference/cli/influxd/recovery/user/update/) to update the password for a specified user.
+
+### Security updates
+
+- Add the [`hardening-enabled`](/influxdb/v2.2/security/enable-hardening) option to limit flux/pkger HTTP requests. The new `hardening-enabled` option ensures that InfluxDB first verifies the IP address of the URL is not private.
+  By default, Flux HTTP and template fetching requests are allowed to access localhost and private IP addresses.
+  - Disable use of jsonnet with `/api/v2/templates/apply`.
+This prevents crafted authenticated requests from exfiltrating files accessible to the user InfluxDB runs as.
+- Add read permissions check for querying data.
+  This prevents authenticated requests using a write-only token from reading data
+  via the InfluxQL `/query` compatibility API.
+- Add write permissions check for `DELETE` and `DROP MEASUREMENT`.
+  This prevents authenticated requests using a read-only token from deleting data
+  via the InfluxQL `/query` compatibility API.
+Additionally, several security issues were fixed in dependencies and
+the toolchain used to build InfluxDB, including:
+- The following cumulative security fixes for [Flux v0.161.0](/flux/v0.x/release-notes/) since 0.139.0 are included in this release:
+  - Quote db identifiers.
+    This addresses injection vulnerabilities in database connections using `to()`.
+  - Make substring check bounds correctly.
+    This prevents authenticated queries from crashing the Flux engine.
+- The cumulative security fixes for [Go 1.17.8](https://go.dev/doc/devel/release#go1.17.minor) since Go 1.17.2 are included in this release.
+  This addresses an issue in the InfluxDB test suite.
+
+### Bug fixes
+
+- Ensure manual task runs can happen concurrently.
+- Extend snapshot copy of backup to filesystems that do not support hard links.
+- Detect misquoted tag values and return an error.
+- Fix potential deadlock in `influxd inspect dump-tsi`.
+- Successfully handle errors returned by `Sketch.Merge`.
+- Return `X-version` and `X-Build` headers for all requests to `/ping` endpoint.
+- Add error when `meta.db` is missing.
+- Sync TSI index file before closing.
+- Fix race condition that could cause `restore` command to fail.
+- To successfully restore a backup, use copy when a rename spans volumes.
+- Disable use of jsonnet with `/api/v2/templates/apply`.
+- Ensure that updating a check (`/checks/{checkID}`) does not require an owner ID.
+- Remove NATS for scraper processing. Note, this fix does not alter scraper functionality--scrapers still work as they did before.
+  - `nats-port` and `nats-max-payload-bytes` flags have been deprecated.
+  -  NATS is no longer embedded in InfluxDB. Because InfluxDB no longer requires a port for NATS, port conflict issues are reduced.
+- Resolve the issue that prevented the browser from tracking the cookie `expiry` correctly, causing the cookie to expire automatically when restarting the browser or changing tabs. Now, the cookie is correctly preserved.
+- Allow unlimited Flux HTTP calls. Previously, HTTP requests failed silently after 100MB of data transfer.
+- Remove pagination limits on the `/telegrafs` API. Previously, pagination wasn't exposed to the API, so API requests were limited to the default 20 pages.
+
+## v2.1.1 [2021-11-08]
+
+{{% note %}}
+To address underlying installation package issues, we bumped the 2.1 release version to 2.1.1.
+{{% /note %}}
+
+This release includes several new [features](#features) and [bug fixes](#bug-fixes).
+
+### `influx` CLI moved to separate repository
+
+The `influx` CLI has been moved to its own GitHub [repository](https://github.com/influxdata/influx-cli/).
+
+{{% warn %}}
+#### `influxdb` release artifacts affected
+Release artifacts produced by `influxdb` are impacted as follows:
+
+- Release archives (`.tar.gz` and `.zip`) **no longer contain** the `influx` binary.
+- The `influxdb2` package (`.deb` and `.rpm`) **no longer contains** the `influx` binary. Instead, the package declares a recommended dependency on the new `influxdb2-cli` package.
+- The `quay.io/influxdb/influxdb` image **no longer contains** the `influx` binary. We recommend migrating to the `influxdb` image hosted on [DockerHub](https://hub.docker.com/_/influxdb).
+{{% /warn %}}
+
+#### Find supported `influx` CLI commands
+
+With this change, versions of the `influx` CLI and InfluxDB server (`influxd`) are not guaranteed to exactly match. To check the version of the `influxd` server, see `influxd version` in `influx` CLI or use the `/health` endpoint of your InfluxDB server.
+
+{{% note %}}
+The [`influx` CLI documentation](/influxdb/v2.2/reference/cli/influx/) has been updated to reflect which `influx` CLI commands work with which versions of InfluxDB.
+{{% /note %}}
+
+### Features
+
+This release includes the following new features:
+
+- [Notebooks, annotations, and visualization updates](#notebooks-annotations-and-visualization-updates)
+- [API](#api) and [CLI](#cli) updates
+- Support for latest [Flux](#flux) and [Telegraf](#telegraf) releases
+- Updates to the [InfluxQL](#influxql)
+- [Token](#tokens) updates
+- [Flux location support](#flux-location-support)
+
+#### Notebooks, annotations, and visualization updates
+
+- Add support for [notebooks](/influxdb/v2.2/notebooks/) and [annotations](/influxdb/v2.2/visualize-data/annotations/).
+- Add support for static legends to line graphs and band plots.
+- Enable new dashboard auto-refresh.
+- Simplify display of data for table visualizations.
+
+#### API
+
+- Add new parameters to GET [`/users`](/influxdb/v2.2/api/#operation/GetUsers) API, including: `offset`, `limit`, and `after`.
+- Add the [`api/v2/backup/metadata`](/influxdb/v2.2/api/#operation/GetBackupMetadata) endpoint for backing up both key-value and SQL metadata, and the [`api/v2/restore/sql`](/influxdb/v2.2/api/#operation/GetRoutes) for restoring SQL metadata.
+- Deprecated [`POST .../secrets/delete`](/influxdb/v2.2/api/#operation/PostOrgsIDSecrets). To delete a secret, use [`DELETE .../secrets/{secretID}`](/influxdb/v2.2/api/#operation/DeleteOrgsIDSecretsID).
+
+#### CLI
+
+##### influxd configuration
+
+Added several new configuration options to [`influxd`](/influxdb/v2.2/reference/cli/influxd/):
+
+- Add `influxd recovery` command to let you create a recovery [Operator token](/influxdb/v2.2/security/tokens/#operator-token).
+- Add `--sqlite-path` flag for specifying a user-defined path to the SQLite database file.
+- Add `--storage-wal-max-concurrent-writes` flag to enable tuning memory pressure under heavy write load.
+- Add `--storage-wal-max-write-delay` flag to prevent deadlocks when the WAL is overloaded with concurrent writes.
+- Add `--storage-write-timeout` flag to set write request timeouts.
+- Add `--storage-no-validate-field-size` flag to disable enforcement of max field size.
+- Update `--store` flag to work with string values disk or memory. Memory continues to store metadata in-memory for testing; disk persists metadata to disk via bolt and SQLite.
+
+For more information, see [InfluxDB configuration options](/influxdb/v2.2/reference/config-options/).
+
+##### influxd inspect
+
+Ported the following [`influxd inspect`](/influxdb/v2.2/reference/cli/influxd/inspect/) commands from InfluxDB 1.x:
+
+- [influxd inspect build-tsi](/influxdb/v2.2/reference/cli/influxd/inspect/build-tsi/)
+- [influxd inspect delete-tsm](/influxdb/v2.2/reference/cli/influxd/inspect/delete-tsm/)
+- [influxd inspect dump-tsi](/influxdb/v2.2/reference/cli/influxd/inspect/dump-tsi/)
+- [influxd inspect dump-tsm](/influxdb/v2.2/reference/cli/influxd/inspect/dump-tsm/)
+- [influxd inspect dump-wal](/influxdb/v2.2/reference/cli/influxd/inspect/dump-wal/)
+- [influxd inspect report-tsi](/influxdb/v2.2/reference/cli/influxd/inspect/report-tsi/)
+- [influxd inspect report-tsm](/influxdb/v2.2/reference/cli/influxd/inspect/report-tsm/)
+- [influxd inspect verify-seriesfile](/influxdb/v2.2/reference/cli/influxd/inspect/verify-seriesfile/) 
+- [influxd inspect verify-tombstone](/influxdb/v2.2/reference/cli/influxd/inspect/verify-tombstone/)
+- [influxd inspect verify-tsm](/influxdb/v2.2/reference/cli/influxd/inspect/verify-tsm/)
+- [influxd inspect verify-wal](/influxdb/v2.2/reference/cli/influxd/inspect/verify-wal/)
+
+##### influxd downgrade
+
+Added the [influxd downgrade command](/influxdb/v2.2/reference/cli/influxd/downgrade/)
+to migrate InfluxDB key-value metadata schemas to earlier 2.x versions when necessary.
+
+#### Flux
+
+- Update to [Flux v0.139.0](/flux/v0.x/release-notes/#v01390-2021-11-01).
+- Enable writing to remote hosts using the Flux [`to()`](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/to/) and [`experimental.to()`](/{{< latest "flux" >}}/v0.x/stdlib/experimental/to/) functions.
+- Flux now supports locations that dynamically modify time offsets based on your specified timezone. You can also specify fixed time offsets relative to UTC.
+- Perform [bitwise operations](/{{< latest "flux" >}}/stdlib/experimental/bitwise/)
+  on integers and unsigned integers.
+- [Query](/{{< latest "flux" >}}/query-data/sql/vertica/) and
+  [write to Vertica](/{{< latest "flux" >}}/query-data/sql/vertica/) SQL databases.
+- Add the [`hex` package](/{{< latest "flux" >}}/stdlib/contrib/bonitoo-io/hex/)
+  for working with hexadecimal string values.
+
+#### InfluxQL
+
+- `SHOW MEASUREMENTS ON` now supports database and retention policy wildcards. For example, `SHOW MEASUREMENTS ON *.*` to show all databases and `SHOW MEASUREMENTS ON <db>.*` to show all retention policies.
+-  Add hyper log operators `merge_hll`, `sum_hll`, and `count_hll` in InfluxQL to optimize series iteration. (`count_hll` optimizes queries that can be answered without inspecting TSM data.)
+
+#### Telegraf
+
+- Add the following new [Telegraf plugins](https://docs.influxdata.com/telegraf/v1.20/plugins/) to the Load Data page:
+  - Alibaba (Aliyun) CloudMonitor Service Statistics (`aliyuncms`)
+  - AMD ROCm System Management Interface (SMI) (`amd_rocm_smi`)
+  - Counter-Strike: Global Offensive (CS:GO) (`csgo`)
+  - Directory Monitoring (`directory_monitor`)
+  - Intel Data Plane Development Kit (DPDK) (`dpdk`)
+  - Elasticsearch Query (`elasticsearch_query`)
+  - Internet Speed Monitor (`internet_speed`)
+  - KNX (`knx_listener`)
+  - Mdstat (`mdstat`)
+  - Netstat (`netstat`)
+  - NFS Client (`nfsclient`)
+  - OpenTelemetry (`opentelemetry`)
+  - RavenDB (`ravendb`)
+  - SQL (`sql`)
+  - Trig (`trig`)
+  - Twemproxy (`twemproxy`)
+
+For more information about each plugin, see [Telegraf plugins](/telegraf/v1.20/plugins/), and search for the plugin name.
+
+#### Tokens
+
+- Add support for standard Bearer token syntax. Now you can specify token credentials as: `Authorization: Bearer xxxxxxxx`.
+- If restoring a backup overwrites the Operator token, the new token value is returned.
+
+### Bug fixes
+
+- Log API errors to server logs and tell clients to check the server logs for the error message.
+- Fix pagination for GET [`/buckets`](/influxdb/v2.2/api/#operation/GetBuckets) API when displaying results. Previously, pagination was broken if a request included both an `org` filter AND the `after` request parameter. Also corrects `descending` parameter to sort when an `org` filter is used and saved.
+- Sync series segment to disk after writing.
+- Do not allow shard creation to create overlapping shards.
+- Don't drop shard group durations when upgrading InfluxDB.
+
+## v2.0.9 [2021-09-27]
+
+This release includes several new [features](#features) and [bug fixes](#bug-fixes).
+
+### Features
+
+New features include:
+
+- [API updates](#api-updates)
+- [Flux updates](#flux-updates)
+- [Performance enhancements](#performance-enhancements)
+
+#### API updates
+
+- Add a new route `/api/v2/resources` that returns a list of known resources to the platform, including the following resource types. Makes it easier to update all-access tokens with current resources:
+
+   - `AuthorizationsResourceType`
+   - `BucketsResourceType`
+   - `ChecksResourceType`
+   - `DashboardsResourceType`
+   - `DBRPResourceType`
+   - `DocumentsResourceType`
+   - `LabelsResourceType`
+   - `NotificationEndpointResourceType`
+   - `NotificationRuleResourceType`
+   - `OrgsResourceType`
+   - `ScraperResourceType`
+   - `SecretsResourceType`
+   - `SourcesResourceType`
+   - `TasksResourceType`
+   - `TelegrafsResourceType`
+   - `UsersResourceType`
+   - `VariablesResourceType`
+   - `ViewsResourceType`
+
+#### Flux updates
+
+- Update to [Flux v0.130.0](/flux/v0.x/release-notes/#v01300-2021-09-15).
+- Add support for [`influxdb.cardinality()`](/flux/v0.x/stdlib/influxdata/influxdb/cardinality/) function.
+- Operational improvements:
+  - Add logging to Flux end-to-end tests (`TestFluxEndToEnd`) to help diagnose test failures.
+  - Add `--flux-log-enabled` option to [`influxd`](/influxdb/v2.2/reference/config-options/) to show detailed logs for Flux queries.
+
+#### Performance enhancements
+
+- Optimize series iteration for queries that can be answered without inspecting TSM data.
+- Optimize queries with predicates that contain multiple measurements.
+
+### Bug fixes
+
+This release includes the following bug fixes and updates:
+
+- [API fix](#api-fix)
+- [Dependency update](#dependency-update)
+- [Error updates](#error-updates)
+- [Limit update](#limit-update)
+- [Miscellaneous operational fixes](#miscellaneous-operational-fixes)
+- [Task updates](#task-updates)
+- [Version maintenance](#version-maintenance)
+
+#### API fix
+
+- Correctly filter requests to `/api/v2/authorizations` by `org` and `user` parameters.
+
+#### Dependency update
+
+- Include `curl` as a dependency in `influxdb2` packages.
+
+#### Errors updates
+
+- Add message to set the Flux `content-type` when a query fails to parse as JSON.
+- Discard excessive errors over `DefaultMaxSavedErrors (100)` to prevent out-of-memory crashes.
+- Upgrade `golang.org/x/sys` to avoid panics on macs.
+
+#### Limit update
+
+- Implement hard limit on field size (`MaxFieldValueLength = 1048576`) while parsing line protocol.
+
+#### Miscellaneous operational fixes
+
+- Resolve the compaction queue stats flutter.
+- Ensure the TSI index compacts log files that meet one of the following criteria:
+  - Log file hasn't been updated (no new series have been added to the shard) for 4 (or more) hours (to change this duration, specify a new [`storage-compact-full-write-cold-duration`](/influxdb/v2.2/reference/config-options/#storage-compact-full-write-cold-duration))
+  - Log file is one (or more) megabytes (to update this size, specify a new [`storage-max-index-log-file-size`](/influxdb/v2.2/reference/config-options/#storage-max-index-log-file-size))
+- Repair bad port dropping return value names.
+- Use consistent path separator in permission string representation.
+- (Windows only) Copy snapshot files being backed up.
+
+#### Task updates
+
+- Updating an inactive task no longer schedules it. Thanks @raffs!
+- Preserve comments in Flux queries when saving task definitions.
+
+#### Version maintenance
+
+- Fix `X-Influxdb-Build` and `X-Influxdb-Version` response header at `/ping`.
+- Upgrade `influxql` to latest version and fix predicate handling for `SHOW TAG VALUES` meta queries.
+
+## v2.0.8 [2021-08-13]
+
+{{% warn %}} #### Upcoming changes to influx CLI packaging
+
+Beginning in InfluxDB 2.1, the `influx` CLI will no longer be packaged with the release. Future versions of `influx` CLI will be released from the [influx-cli](https://github.com/influxdata/influx-cli) repository.
+
+To adopt the new, separate `influx` CLI early, download the latest release from [GitHub](https://github.com/influxdata/influx-cli/releases/tag/v2.2.0) or from the [InfluxData Downloads portal](https://portal.influxdata.com/downloads/).
+{{% /warn %}}
+
+### Go version
+
+- Upgrade to Go 1.16. **Requires macOS Sierra 10.12 or later to run.**
+
+### Features
+
+- Add `--ui-disabled` option to `influxd` to support running with the UI disabled.
+- Telemetry improvements: Do not record telemetry data for non-existent paths; replace invalid static asset paths with a slug.
+- Upgrade to Flux v0.124.0.
+- Upgrade to UI v2.0.8.
+- Upgrade `flux-lsp-browser` to v0.5.53.
+
+### Bug fixes
+
+- Rename ARM RPM packages with yum-compatible names.
+- Upgrade to latest version of `influxdata/cron` so that tasks can be created with interval of `every: 1w`.
+- Avoid rewriting `fields.idx` unnecessarily.
+- Do not close connection twice in DigestWithOptions.
+- Remove incorrect optimization for group-by.
+- Return an error instead of panicking when InfluxQL statement rewrites fail.
+- Migrate restored KV snapshots to latest schema before using them.
+- Specify which fields are missing when rejecting an incomplete onboarding request.
+- Ensure `systemd` unit blocks on startup until HTTP endpoint is ready.
+- Fix display and parsing of `influxd upgrade` CLI prompts in PowerShell.
+- Removed unused `chronograf-migator` package and chronograf API service, and updated various "chronograf" references.
+- Fix display and parsing of interactive `influx` CLI prompts in PowerShell.
+- Upgrade to `golang-jwt` 3.2.1.
+- Prevent silently dropped writes when there are overlapping shards.
+- Invalid requests to `/api/v2` subroutes now return 404 instead of a list of links.
+- Flux meta queries for `_field` take fast path if `_measurement` is the only predicate.
+- Copy names from mmapped memory before closing iterator.
+
+## v2.0.7 [2021-06-04]
+
+### Features
+
+- Optimize [`table.fill()`](/{{< latest "flux" >}}/stdlib/experimental/table/fill/)
+  execution within Flux aggregate windows.
+- Upgrade Flux to [v0.117.0](/{{< latest "flux" >}}/release-notes/#v01171-2021-06-01).
+- Upgrade UI to v2.0.7.
+- Upgrade `flux-lsp-browser` to v0.5.47.
+
+### Bug Fixes
+
+- Fix query range calculation (off by one) over partially compacted data.
+- Deprecate the unsupported `PostSetupUser` API.
+- Add limits to the `/api/v2/delete` endpoint for start and stop times with error messages.
+- Add logging to NATS streaming server to help debug startup failures.
+- Accept `--input` instead of a positional argument in `influx restore`.
+- Print error instead of panicking when `influx restore` fails to find backup manifests.
+- Set last-modified time of empty shard directory to the directory's last-modified time, instead of the Unix epoch.
+- Remove deadlock in `influx org members list` when an organization has greater than 10 members.
+- Replace telemetry file name with slug for `ttf`, `woff`, and `eot` files.
+- Enable use of absolute path for `--upgrade-log` when running `influxd upgrade` on Windows.
+- Make InfluxQL meta queries respect query timeouts.
+
+---
+
+## v2.0.6 General Availability [2021-04-29]
+
+### Bug Fixes
+- Ensure query configuration written by `influxd upgrade` is valid.
+- Set `query-concurrency` and `query-queue-size` configuration option defaults
+  to `0` to avoid validation failures when upgrading users.
+- Correctly validate when `query-concurrency` is `0` and `query-queue-size` is
+  greater than `0`.
+
+## v2.0.5 General Availability [2021-04-27]
+
+{{% warn %}}
+InfluxDB v2.0.5 introduced a defect that prevents users from successfully upgrading
+from InfluxDB 1.x to 2.0 using the `influxd upgrade` command or Docker.
+To [automatically upgrade from 1.x to 2.0](/influxdb/v2.2/upgrade/v1-to-v2/automatic-upgrade/)
+with the `influxd upgrade` command or [with Docker](/influxdb/v2.2/upgrade/v1-to-v2/docker/),
+use [InfluxDB v2.0.6](#v206-general-availability-2021-04-29).
+{{% /warn %}}
+
+### Windows Support
+This release includes our initial Windows preview build.
+
+### Breaking Changes
+
+#### /debug/vars removed
+Prior to this release, the `influxd` server would expose profiling information over the `/debug/vars` endpoint.
+This endpoint was unauthenticated and not used by InfluxDB systems to report diagnostics.
+For security and clarity, the endpoint has been removed.
+Use the `/metrics` endpoint to collect system statistics.
+
+#### `influx transpile` removed
+The `transpile` command has been removed. Send InfluxQL requests directly to the server via the `/api/v2/query`
+or `/query` HTTP endpoints.
+
+#### Default query concurrency changed
+The default setting for the max number of concurrent Flux queries has been changed from 10 to unlimited (`0`).
+To limit query concurrency and queue size:
+
+1. Set the `query-concurrency` config parameter to > 0 when running `influxd` to re-limit the maximum running query count,
+2. Set the `query-queue-size` config parameter to > 0 to set the max number of queries that can be queued before the
+   server starts rejecting requests.
+
+#### Prefix for query-controller metrics changed
+The prefix used for Prometheus metrics from the query controller has changed from `query_control_` to `qc_`.
+
+### Features
+- Add [Swift client library](https://github.com/influxdata/influxdb-client-swift)
+  to the **Load Data** section of the InfluxDB UI.
+- Add [`influx task retry-failed` command](/influxdb/v2.2/reference/cli/influx/task/retry-failed/) to rerun failed runs.
+- Add [`--compression` option](/influxdb/v2.2/reference/cli/influx/write/#flags)
+  to the `influx write` command to support Gzip inputs.
+- Add new `influxd` configuration options:
+  - [pprof-disabled](/influxdb/v2.2/reference/config-options/#pprof-disabled)
+  - [metrics-disabled](/influxdb/v2.2/reference/config-options/#metrics-disabled)
+  - [http-read-header-timeout](/influxdb/v2.2/reference/config-options/#http-read-header-timeout)
+  - [http-read-timeout](/influxdb/v2.2/reference/config-options/#http-read-timeout)
+  - [http-write-timeout](/influxdb/v2.2/reference/config-options/#http-write-timeout)
+  - [http-idle-timeout](/influxdb/v2.2/reference/config-options/#http-idle-timeout)
+- Add `/debug/pprof/all` HTTP endpoint to gather all profiles at once.
+- Include the InfluxDB 1.x `http.pprof-enabled` configuration option in the 2.0 configuration file generated by the [InfluxDB upgrade process](/influxdb/v2.2/upgrade/v1-to-v2/automatic-upgrade/).
+- Add support for [custom shard group durations](/influxdb/v2.2/reference/cli/influx/bucket/create#create-a-bucket-with-a-custom-shard-group-duration) on buckets.
+- Optimize regular expression conditions in InfluxQL subqueries.
+- Update Telegraf plugins in the InfluxDB UI to include additions and changes from
+  [Telegraf 1.18](/telegraf/v1.18/about_the_project/release-notes-changelog/#v118-2021-3-17).
+- Display task IDs in the tasks list in the InfluxDB UI.
+- Write to standard output (`stdout`) when `--output-path -` is passed to [`influxd inspect export-lp`](/influxdb/v2.2/reference/cli/influxd/inspect/export-lp/).
+- Add `-p, --profilers` flag to [`influx query` command](/influxdb/v2.2/reference/cli/influx/query/)
+  to enable [Flux profilers](/{{< latest "flux" >}}/stdlib/profiler/) on
+  a query executed from the `influx` CLI.
+- Update InfluxDB OSS UI to match InfluxDB Cloud.
+- Support disabling concurrency limits in the Flux controller.
+- Replace unique resource IDs (UI assets, backup shards) with slugs to reduce
+  cardinality of telemetry data.
+- Standardize HTTP server error log output.
+- Enable InfluxDB user interface features:
+  - [Band visualization type](/influxdb/v2.2/visualize-data/visualization-types/band/)
+  - [Mosiac visualization type](/influxdb/v2.2/visualize-data/visualization-types/mosaic/)
+  - [Configure axis tick marks](/influxdb/v2.2/visualize-data/visualization-types/graph/#x-axis)
+  - Upload CSV files through the InfluxDB UI
+  - [Edit Telegraf configurations](/influxdb/v2.2/telegraf-configs/update/#edit-the-configuration-file-directly-in-the-ui) in the InfluxDB UI
+  - [Legend orientation options](/influxdb/v2.2/visualize-data/visualization-types/graph/#legend)
+  - [Refresh a single dashboard cell](/influxdb/v2.2/visualize-data/dashboards/control-dashboard/#refresh-a-single-dashboard-cell)
+- Upgrade to **Flux v0.113.0**.
+
+### Bug Fixes
+- Prevent "do not have an execution context" error when parsing Flux options in tasks.
+- Fix swagger to match implementation of DBRPs type.
+- Fix use-after-free bug in series ID iterator.
+- Fix TSM and WAL segment size check to check against the local `SegmentSize`.
+- Fix TSM and WAL segment size computing to correctly calculate `totalOldDiskSize`.
+- Update references to the documentation site site to use current URLs.
+- Fix data race in then TSM engine when inspecting tombstone statistics.
+- Fix data race in then TSM cache.
+- Deprecate misleading `retentionPeriodHrs` key in the onboarding API.
+- Fix Single Stat graphs with thresholds crashing on negative values.
+- Fix InfluxDB port in Flux function UI examples.
+- Remove unauthenticated, unsupported `/debug/vars` HTTP endpoint.
+- Respect 24 hour clock formats in the InfluxDB UI and add more format choices.
+- Prevent "do not have an execution context" error when parsing Flux options in tasks.
+- Prevent time field names from being formatted in the Table visualization.
+- Log error details when `influxd upgrade` fails to migrate databases.
+- Fix the cipher suite used when TLS strict ciphers are enabled in `influxd`.
+- Fix parse error in UI for tag filters containing regular expression meta characters.
+- Prevent concurrent access panic when gathering bolt metrics.
+- Fix race condition in Flux controller shutdown.
+- Reduce lock contention when adding new fields and measurements.
+- Escape dots in community templates hostname regular expression.
+
+## v2.0.4 General Availability [2021-02-04]
+
+### Docker
+
+#### ARM64
+This release extends the Docker builds hosted in `quay.io` to support the Linux/ARM64 platform.
+
+#### 2.x nightly images
+Prior to this release, competing nightly builds caused the nightly Docker tag to contain outdated binaries. This conflict is fixed, and the image tagged with nightly now contains 2.x binaries built from the `HEAD` of the `master` branch.
+
+### Breaking Changes
+
+#### `inmem` index option removed
+
+This release fully removes the `inmem` indexing option, along with the associated config options:
+- `max-series-per-database`
+- `max-values-per-tag`
+
+The startup process automatically generates replacement `tsi1` indexes for shards that need it.
+
+### Features
+
+#### `influxd` updates
+- Add new [`influxd upgrade`](/influxdb/v2.2/reference/cli/influxd/upgrade/) flag `—overwrite-existing-v2` to overwrite existing files at output paths (instead of aborting).
+- Add new configuration options:
+       - [`nats-port`](/influxdb/v2.2/reference/config-options/#nats-port)
+       - [`nats-max-payload-bytes`](/influxdb/v2.2/reference/config-options/#nats-max-payload-bytes)
+- Add new commands:
+       - Add [`influxd print-config`](/influxdb/v2.2/reference/cli/influxd/print-config/) to support automated configuration inspection.
+       - Add [`influxd inspect export-lp`](/influxdb/v2.2/reference/cli/influxd/inspect/export-lp/) to extract data in line-protocol format.  
+
+#### New Telegraf plugins in UI
+- Update Telegraf plugins list in UI to include Beat, Intel PowerStats, and Rienmann.
+
+#### Performance improvements
+- Promote schema and fill query optimizations to default behavior.
+
+#### Flux updates
+- Upgrade to [Flux v0.104.0](/{{< latest "flux" >}}/release-notes/#v0-104-0-2021-02-02).
+- Upgrade to `flux-lsp-browser` v0.5.31.
+
+### Bug Fixes
+
+- Standardize binary naming conventions.
+- Fix configuration loading issue.
+- Add Flux dictionary expressions to Swagger documetnation.
+- Ensure `influxdb` service sees default environment variables when running under `init.d`.
+- Remove upgrade notice from new installs.
+- Ensure `config.toml` is initialized on new installs.
+- Include upgrade helper script (`influxdb2-upgrade.sh`) in GoReleaser manifest.
+- Prevent `influx stack update` from overwriting stack name and description.
+- Fix timeout setup for `influxd` graceful shutdown.
+- Require user to set password during initial user onboarding.
+- Error message improvements:
+    - Remove duplication from task error messages.
+    - Improve error message shown when influx CLI can't find an `org` by name.
+    - Improve error message when opening BoltDB with unsupported file system options.
+    - Improve messages in DBRP API validation errors.
+- `influxd upgrade` improvements:
+  - Add confirmation step with file sizes before copying data files.
+  - Prevent panic in `influxd upgrade` when v1 users exist but v1 config is missing.
+- Fix logging initialization for storage engine.
+- Don't return 500 codes for partial write failures.
+- Don't leak `.tmp` files while backing up shards.
+- Allow backups to complete while a snapshot is in progress.
+- Fix silent failure to register CLI arguments as required.
+- Fix loading when `INFLUXD_CONFIG_PATH` points to a .yml file.
+- Prevent extra output row from GROUP BY crossing DST boundary.
+- Update Flux functions list in UI to reflect that `v1` package was renamed to `schema`.
+- Set correct `Content-Type` on v1 query responses.
+- Respect the `--skip-verify` flag when running `influx query`.
+- Remove blank lines from payloads sent by `influx write`.
+- Fix infinite loop in Flux parser caused by invalid array expressions.
+- Support creating users without initial passwords in `influx user create`.
+- Fix incorrect errors when passing `--bucket-id` to `influx write`.
+
+## v2.0.3 General Availability [2020-12-14]
+
+### Breaking Changes
+
+#### `influxd upgrade`
+
+Previously, `influxd upgrade` would attempt to write upgraded `config.toml` files into the same directory as the source
+`influxdb.conf` file. If this failed, a warning would be logged and `config.toml` would write into the `home` directory of the user who launched the upgrade.
+
+This release breaks this behavior in two ways:
+
+- By default, `config.toml` writes into the same directory as the Bolt DB and engine files (`~/.influxdbv2/`)
+- If writing upgraded config fails, the `upgrade` process exits with an error instead of falling back to the `HOME` directory
+
+To override the default configuration path (`~/.influxdbv2/`), use the new `--v2-config-path` option to specify the output path to the v2 configuration file (`config.toml`). For details, see [Upgrade from InfluxDB 1.x to InfluxDB 2.0](/influxdb/v2.2/upgrade/v1-to-v2/).
+
+#### InfluxDB v2 packaging
+
+We've renamed the InfluxDB v2 DEB and RPM packages to clarify versions. The package name is now `influxdb2` and conflicts with any previous `influxdb` package (including initial 2.0.0, 2.0.1, and 2.0.2 packages).
+
+This release also defines v2-specific path defaults and provides [helper scripts](https://github.com/influxdata/influxdb/blob/master/scripts/influxdb2-upgrade.sh) for `influxd upgrade` and cleanup cases.
+
+### Features
+
+- Allow password to be specified as a CLI option in [`influx v1 auth create`](/influxdb/cloud/reference/cli/influx/auth/create/).
+- Allow password to be specified as a CLI option in [`influx v1 auth set-password`](/influxdb/cloud/reference/cli/influx/auth/).
+- Implement [delete with predicate](/influxdb/v2.2/write-data/delete-data/).
+- Improve ID-related error messages for `influx v1 dbrp` commands.
+- Update Flux to [v0.99.0](/{{< latest "flux" >}}/release-notes/#v0-99-0-2020-12-15).
+- Update `flux-lsp-browser` to v0.5.25.
+- Support for ARM64 preview build.
+
+### Bug Fixes
+
+- Don't log bodies of v1 write request bodies.
+- Fix panic when writing a point with 100 or more tags.
+- Fix validation of existing DB names when creating DBRP mappings.
+- Enforce max value of 2147483647 on query concurrency to avoid startup panic.
+- Automatically migrate existing DBRP mappings from old schema to avoid panic.
+- Optimize shard lookup in groups containing only one shard.
+- Always respect the `--name` option in `influx setup`.
+- Allow for 0 (infinite) values for `--retention` in `influx setup`.
+- Fix panic when using a `null` value as a record or array in a Flux query.
+
+## v2.0.2 General Availability [2020-11-19]
+
+### Breaking changes
+
+#### DBRP HTTP API now matches Swagger documentation
+
+Previously, the database retention policy (DBRP) mapping API did not match the swagger spec. If you're using scripts based on the previous implementation instead of the swagger spec, you'll need to either update them or use the new [DBRP CLI commands](/influxdb/v2.2/reference/cli/influx/v1/dbrp/) instead.
+
+### Features
+- Improvements to upgrade from 1.x to 2.x:
+    - Warning appears if auth is not enabled in 1.x (`auth-enabled = false`), which is not an option in 2.x. For details, see [Upgrade from InfluxDB 1.x to InfluxDB 2.0](/influxdb/v2.2/upgrade/v1-to-v2/).
+    - `upgrade` command now checks to see if continuous queries are running and automatically exports them to a local file.
+- Upgrade to [Flux v0.95.0](/{{< latest "flux" >}}/release-notes/#v0-95-0-2020-11-17).
+- Upgrade `flux-lsp-browser` to v.0.5.23.
+- Manage database retention policy (DBRP) mappings via CLI. See [`influx v1 dbrp`](/influxdb/v2.2/reference/cli/influx/v1/dbrp/).
+- Filter task runs by time.
+
+### Bug Fixes
+- Fixes to `influx upgrade` command:
+  - Remove internal subcommands from help text.
+  - Validate used input paths upfront.
+- Add locking during TSI iteration creation.
+- Fix various typos.
+- Use `--skip-verify` flag for backup/restore CLI command. This is passed to the underlying HTTP client for the `BackupService` and `RestoreService` to support backup and restore on servers with self-signed certificates.
+- Don't automatically print help on `influxd` errors.
+- Add `SameSite=Strict` flag to session cookie.
+- Ensure `SHOW DATABASES` returns a list of the unique databases only.
+- Allow scraper to ignore insecure certificates on an endpoint.
+- Ensure Flux reads across all shards.
+- Use the associated default retention policies defined within the DBRP mapping if no retention policy is specified as part of a v1 write API call.
+- Add locking during TSI iterator creation.
+- Allow self-signed certificates for scraper targets.
+- Bump version in `package.json` so it appears correctly.
+
+## v2.0.1 General Availability [2020-11-10]
+
+InfluxDB 2.0 general availability (GA) introduces the first **production-ready** open source version of InfluxDB 2.0. This release comprises all features and bug fixes included in prior alpha, beta, and release candidate versions.
+
+{{% note %}}
+#### Known issues
+
+##### Delete with predicate API not implemented
+
+The delete with predicate API (`/api/v2/delete`) has not been implemented and currently returns a `501 Not implemented` message. This API will be implemented post GA.
+
+##### Duplicate DBRP mappings per database
+
+When there are multiple [DBRP mappings](/influxdb/v2.2/reference/api/influxdb-1x/dbrp/) with the same database name in InfluxDB 1.x, SHOW DATABASES incorrectly returns duplicates.
+{{% /note %}}
+
+Highlights include:
+
+- Support for **upgrading to InfluxDB 2.0**:
+   - To upgrade **from InfluxDB 1.x**, see [Upgrade from InfluxDB 1.x to InfluxDB 2.0](/influxdb/v2.2/upgrade/v1-to-v2).
+   - To upgrade **from InfluxDB 2.0 beta 16 or earlier**, see [Upgrade from InfluxDB 2.0 beta to InfluxDB 2.0](/influxdb/v2.2/upgrade/v2-beta-to-v2).
+- **Flux**, our powerful new functional data scripting language designed for querying, analyzing, and acting on data. This release includes [Flux v0.94.0](/{{< latest "flux" >}}/release-notes/#v0-94-0-2020-11-09). If you're new to Flux, [check out how to get started with Flux](/influxdb/v2.2/query-data/get-started/). Next, delve deeper into the [Flux standard library](/{{< latest "flux" >}}/stdlib//) reference docs and see how to [query with Flux](/influxdb/v2.2/query-data/flux/).
+- Support for [InfluxDB 1.x API compatibility](/influxdb/v2.2/reference/api/influxdb-1x/).
+- **Templates** and **stacks**. Discover how to [use community templates](/influxdb/v2.2/influxdb-templates/use/) and how to [manage templates with stacks](/influxdb/v2.2/influxdb-templates/stacks/).
+
+If you're new to InfluxDB 2.0, we recommend checking out [how to get started](/influxdb/v2.2/get-started/) and [InfluxDB key concepts](/influxdb/v2.2/reference/key-concepts/).
+
+## v2.0.0 [2020-11-09]
+
+### Features
+- Improve  UI for v1 `influx auth` commands.
+- Upgrade to [Flux v0.94.0](/{{< latest "flux" >}}/release-notes/#v0-94-0-2020-11-10)
+- Upgrade `flux-lsp-browser` to v0.5.22.
+- Add [RAS Telegraf input plugin](/telegraf/v1.16/plugins//#ras).
+
+### Bug Fixes
+
+- Remove unused `security-script` option from `influx upgrade` command.
+- Fix parsing of retention policy CLI arguments in `influx setup` and `influxd upgrade`.
+- Create CLI configs during upgrade to v2.
+- Allow write-only v1 tokens to find database retention policies (DBRPs).
+- Update `v1 auth` description.
+- Use `db`/`rp` naming convention when migrating databases to buckets.
+- Improve help text for `influxd` and `--no-password` switch.
+- Use `10` instead of `MaxInt` when rewriting query-concurrency.
+- Remove bucket and mapping auto-creation from `/write` 1.x compatibility API.
+- Fix misuse of `reflect.SliceHeader`.
+
+## v2.0.0-rc.4 [2020-11-05]
+
+### Features
+
+- Upgrade to [Flux v0.93.0](/{{< latest "flux" >}}/release-notes/#v0-93-0-2020-11-02).
+- Add `influx backup` and `influx restore` CLI commands to support backing up and restoring data in InfluxDB 2.0.
+- Add the `v1/authorization` package to support authorizing requests to the InfluxDB 1.x API.
+
+### Bug Fixes
+
+- Add a new `CreateUniquePhysicalNode` method, which reads and applies the plan node ID in context. Each physical node has a unique ID to support planner rules applied more than once in a query. Previously, the same node ID (hence the same dataset ID) caused the execution engine to generate undefined results.
+- A cloned task is now only activated when you select **Active**. Previously, a cloned task was activated if the original task was activated.
+- Reduce the `influx` binary file size.
+- Isolate the `TelegrafConfigService` and remove URM interactions.
+- Use the updated HTTP client for the authorization service.
+- Make `tagKeys` and `tagValues` work for edge cases involving fields.
+- Correctly parse float as 64-bits.
+- Add simple metrics related to installed templates.
+- Remove extra multiplication of retention policies in onboarding.
+- Use the `fluxinit` package to initialize the Flux library instead of builtin.
+- Add Logger to the constructor function to ensure the log field is initialized.
+- Return an empty iterator instead of null in `tagValues`.
+- Fix the `/ready` response content type to return `application/json`.
+
+## v2.0.0-rc.3 [2020-10-29]
+
+### Features
+
+- Upgrade to [Flux v0.91.0](/{{< latest "flux" >}}/release-notes/#v0910-2020-10-26).
+- Enable window aggregate mean pushdown.
+- Add `newMultiShardArrayCursors` to aggregate array cursors.
+- UI updates:
+  - Upgrade `papaparse` to 5.2.0.
+  - Upgrade `flux-lsp-browser` to v0.5.21.
+  - Add properties for storing your tick generation selections, including a `generateAxisTicks` property to turn this feature on and off.
+  - Update generate ticks into an array of properties for each axis.
+  - Add the `legendColorizeRows` property to toggle the color on and off in the legend.
+
+### Bug Fixes
+
+- Resolve `invalid operation: fs.Bavail` error that occurred in some cases using when `DiskUsage()`. Now, `fs.Bavail` is always converted to `unit64` to ensure the types in an expression align.
+- Refactor notifications to isolate the `notification/endpoint/service` package and move the rule service into its own package.
+- Update to clear log out.
+- Refactor to allow `newIndexSeriesCursor()` to accept an `influxql.Expr`.
+- Remove unreferenced packages.
+
+## v2.0.0-rc.2 [2020-10-22]
+
+### Features
+
+- Upgrade to [Flux v0.90.0](/{{< latest "flux" >}}/release-notes/#v0900-2020-10-19).
+- Add `--force` option to the `influx stacks rm` command, which lets you remove a stack without the confirmation prompt.
+- Add `aggregate_resultset` for mean aggregate pushdown to optimize windowed results.
+- Return an error if adding a resource to a stack (`influx stacks update --addResource`) fails due to an invalid resource type or resource ID.
+
+### Bug Fixes
+
+- Update `pkger` test templates to use valid Flux to avoid `found unexpected argument end` error. Previously, any template with a `v.dashboardVariable` returned an `undefined identifier v` error.
+- Update the InfluxDB configuration file `/etc/influxdb/influxdb.conf` to recognize the user's home directory. Previously, if a user (other than root user) ran the `upgrade` command, a permissions error occurred.
+- Remove the Telegraf RAS Daemon plugin and other miscellaneous Telegraf plugin updates.
+- Update the `derivative` in the InfluxDB UI (`ui/src/timeMachiner`) to specify the `unit` is one second (`1s`).
+- Enable the new `AuthorizationService` from authorization package in the `launcher` package (`cmd\influxd\launcher`).
+- Update `config upgrade` to save the correct InfluxDB configuration filename.
+
+## v2.0.0-rc.1 [2020-10-14]
+
+### Features
+- Add [`influx upgrade`](/influxdb/v2.2/reference/cli/influxd/upgrade/) command for upgrading from 1.x to 2.0.
+- Upgrade to Flux v0.89.0.
+
+### Bug Fixes
+- Enable scrapers. (Scrapers did not work in rc0.)
+- Update default number of tasks listed with `influx task list` to 100.
+- Add support for [duration unit identifiers](/{{< latest "flux" >}}/spec/lexical-elements/#duration-literals) to templates.
+- Preserve cell colors in imported and exported templates.
+- Resolve issue to ensure the `influx` CLI successfully returns a single Telegraf configuration.
+- Ensure passwords are at least 8 characters in `influx setup`.
+
+## v2.0.0-rc.0 [2020-09-29]
+
+{{% warn %}}
+#### Manual upgrade required
+
+To simplify the migration for existing users of InfluxDB 1.x, this release includes significant breaking changes that require a manual upgrade from all alpha and beta versions. For more information, see [Upgrade to InfluxDB OSS 2.0rc](/influxdb/v2.2/reference/upgrading/rc-upgrade-guide/),
+{{% /warn %}}
+
+### Breaking changes
+
+#### Manual upgrade
+
+- To continue using data from InfluxDB 2.0 beta 16 or earlier, you must move all existing data out of the `~/.influxdbv2` (or equivalent) path, including `influxd.bolt`. All existing dashboards, tasks, integrations, alerts, users, and tokens must be recreated. For information on how to migrate your data, see [Upgrade to InfluxDB OSS 2.0rc](/influxdb/v2.2/reference/upgrading/rc-upgrade-guide/).
+
+#### Port update to 8086
+
+- Change the default port of InfluxDB from 9999 back to 8086. If you would still like to run on port 9999, you can start `influxd` with the `--http-bind-address` option. You must also [update any InfluxDB CLI configuration profiles](/influxdb/v2.2/reference/cli/influx/config/set/) with the new port number.
+
+#### Support for 1.x storage engine and InfluxDB 1.x compatibility API
+
+- Port the TSM1 storage engine. This change supports a multi-shared storage engine and InfluxQL writes and queries using the InfluxDB 1.x API compatibility [`/write`](/influxdb/v2.2/reference/api/influxdb-1x/write/) and [`/query`](/influxdb/v2.2/reference/api/influxdb-1x/query/) endpoints.
+
+#### Disable delete with predicate API
+
+- Disable the delete with predicate API (`/api/v2/delete`). This API now returns a `501 Not implemented` message.
+
+### Features
+
+#### Load Data redesign
+
+- Update the Load Data page to increase discovery and ease of use. Now, you can [load data from sources in the InfluxDB user interface](/influxdb/v2.2/write-data/no-code/load-data/).
+
+#### Community templates added to InfluxDB UI
+
+- Add [InfluxDB community templates](/influxdb/v2.2/influxdb-templates/) directly in the InfluxDB user interface (UI).
+
+#### New data sources
+
+- Add InfluxDB v2 Listener, NSD, OPC-UA, and Windows Event Log to the Sources page.
+
+#### CLI updates
+
+- Add option to print raw query results in [`influx query`](/influxdb/v2.2/reference/cli/influx/query/).
+- Add ability to export resources by name using [`influx export`](/influxdb/v2.2/reference/cli/influx/export/).
+- Add new processing options and enhancements to [`influx write`](/influxdb/v2.2/reference/cli/influx/write/).
+- Add `--active-config` flag to [`influx` commands](/influxdb/v2.2/reference/cli/influx/#commands) to set the configuration for a single command.
+- Add `influxd`[configuration options](/influxdb/v2.2/reference/config-options/#configuration-options) for storage options and InfluxQL coordinator tuning.
+- Add `max-line-length` switch to the [`influx write`](/influxdb/v2.2/reference/cli/influx/write/) command to address `token too long errors` for large inputs.
+
+#### API updates
+
+- List buckets in the API now supports the `after` (ID) parameter as an alternative to `offset`.
+
+#### Task updates
+
+- Record last success and failure run times in the task.
+- Inject the task option `latestSuccessTime` in Flux `Extern`.
+
+### Bug Fixes
+
+- Add description to [`influx auth`](/influxdb/v2.2/reference/cli/influx/auth/) command outputs.
+- Resolve issues with check triggers in notification tasks by including the edge of the observed boundary.
+- Detect and provide warning about duplicate tag names when writing CSV data using `influx write`.
+- Ensure the group annotation does not override the existing line part (measurement, field, tag, time) in a CSV group annotation.
+- Added `PATCH` to the list of allowed methods.
+
+## v2.0.0-beta.16 [2020-08-06]
+
+{{% warn %}}
+This release includes breaking changes:
+- Remove `influx repl` command. To use the Flux REPL, build the REPL from source.
+- Drop deprecated `/packages` route tree.
+- Support more types for template `envRef` default value and require explicit default values.
+- Remove orgs/labels nested routes from the API.
+{{% /warn %}}
+
+### Features
+
+- Add resource links to a stack's resources from public HTTP API list/read calls.
+- Enhance resource creation experience when limits are reached.
+- Add `dashboards` command to `influx` CLI.
+- Allow user onboarding to optionally set passwords.
+- Limit query response sizes for queries built in QueryBuilder by requiring an aggregate window.
+
+### Bug Fixes
+
+- Require all `influx` CLI flag arguments to be valid.
+- Dashboard cells correctly map results when multiple queries exist.
+- Dashboard cells and overlay use UTC as query time when toggling to UTC timezone.
+- Bucket names may not include quotation marks.
+
+### UI Improvements
+
+- Alerts page filter inputs now have tab indices for keyboard navigation.
+
+## v2.0.0-beta.15 [2020-07-23]
+
+### Features
+
+- Add event source to stacks.
+- Add ability to uninstall stacks.
+- Drop deprecated `influx pkg` commands.
+- Add Telegraf management commands to `influx` CLI.
+- Enable dynamic destination for the `influx` CLI configuration file.
+
+### Bug Fixes
+
+- Allow 0 to be the custom set minimum value for y domain.
+- Single Stat cells render properly in Safari.
+- Limit variable querying when submitting queries to used variables.
+
+## v2.0.0-beta.14 [2020-07-08]
+
+### Features
+
+- Extend `influx stacks update` command with ability to add resources without apply template.
+- Consolidate all InfluxDB template and stack functionality into two new public APIs: `/api/v2/templates` and `/api/v2/stacks`.
+- Extend template `Summary` and `Diff` nested types with `kind` identifiers.
+- Add static builds for Linux.
+- Update Flux to v.0.71.1.
+
+### Bug Fixes
+
+- Don't overwrite build date set via `ldflags`.
+- Fix issue where define query was unusable after importing a Check.
+- Update documentation links
+
+## v2.0.0-beta.13 [2020-06-25]
+
+### Features
+
+- Cancel submitted queries in the Data Explorer.
+- Extend templates with the source `file|url|reader`.
+- Collect stats on installed InfluxData community template usage.
+- Allow raw `github.com` host URLs for `yaml|json|jsonnet` URLs in InfluxDB templates.
+- Allow for remote files for all `influx template` commands.
+- Extend stacks API with update capability.
+- Add support for config files to `influxd` and any `cli.NewCommand` use case.
+- Extend `influx stacks` command with new `influx stacks update` command.
+- Skip resources in a template by kind or by `metadata.name`.
+- Extend `influx apply` with resource filter capabilities.
+- Provide active configuration when running `influx config` without arguments.
+- Enable `influxd` binary to look for a configuration file on startup.
+- Add environmental default values to the template parser.
+- Templates will store which dashboard variable should be selected by default.
+
+### Bug Fixes
+
+- Fix `uint` overflow during setup on 32bit systems.
+- Drop support for `--local` flag within `influx` CLI.
+- Fix issue where undefined queries in cells result in error in dashboard.
+- Add support for day and week time identifiers in the CLI for bucket and setup commands.
+- Cache dashboard cell query results to use as a reference for cell configurations.
+- Validate `host-url` for `influx config create` and `influx config set` commands.
+- Fix `influx` CLI flags to accurately depict flags for all commands.
+
+## v2.0.0-beta.12 [2020-06-12]
+
+### Features
+
+- Add option for Cloud users to use the `influx` CLI to interact with a Cloud instance. For more information, see how to [download and install the influx CLI](/influxdb/v2.2/get-started/) and then learn more about how the [influx - InfluxDB command line interface](/influxdb/v2.2/reference/cli/influx/) works.
+- Consolidate `influx apply` commands under templates. Remove some nesting of the `influx` CLI commands.
+- Make all `influx apply` applications stateful through stacks.
+- Add ability to export a stack's existing resource state using `influx export`.
+- Update `influx apply` commands with improved usage and examples in long form.
+- Update `influx` CLI to include the `-version` command and return the User-Agent header.
+- Add `RedirectTo` functionality to ensure Cloud users are redirected to the page that they were trying access after logging into Cloud.
+- Maintain sort order on a dashboard after navigating away.
+- Allow tasks to open in new tabs.
+
+### Bug Fixes
+
+- Support organization name and ID in DBRP operations.
+- Prevent the CLI from failing when an unexpected flag is entered in the CLI.
+- `influx delete` now respects the configuration settings.
+- Store initialization for `pkger` enforced on reads.
+- Backfill missing `fillColumns` field for histograms in `pkger`.
+- Notify the user how to escape presentation mode when the feature is toggled.
+
+### UI Improvements
+
+- Display bucket ID in bucket list and enable 1-click copying.
+- Update Tokens list to be consistent with other resource lists.
+- Reduce the number of variables being hydrated when toggling variables.
+- Redesign dashboard cell loading indicator to be more obvious.
+
+## v2.0.0-beta.11 [2020-05-27]
+
+{{% warn %}}
+The beta 11 version was **not released**. Changes below are included in the beta 12 release.
+{{% /warn %}}
+
+### Features
+
+- Ability to set UTC time for a custom time range query.
+- Ability to set a minimum or maximum value for the y-axis visualization setting (rather than requiring both).
+- New `csv2lp` library for converting CSV (comma separated values) to InfluxDB line protocol.
+- Add influxdb version to the InfluxDB v2 API `/health` endpoint.
+
+### Bug Fixes
+
+- Automatically adjust the drop-down list width to ensure the longest item in a list is visible.
+- Fix bug in Graph + Single Stat visualizations to ensure `timeFormat` persists.
+- Authorizer now exposes the full permission set. This adds the ability to derive which organizations the Authorizer has access to read or write to without using a User Request Management (URM) service.
+- Fix issue causing variable selections to hydrate all variable values, decreasing the impact on network requests.
+- Resolve scrollbar issues to ensure datasets are visible and scrollable.
+- Check status now displays a warning if loading a large amount.
+
+## v2.0.0-beta.10 [2020-05-07]
+
+### Features
+
+- Add ability to delete a stack and all associated resources.
+- Enforce DNS name compliance on the `metadata.name` field in all `pkger` resources.
+- Add stateful `pkg` management with stacks.
+
+### Bug Fixes
+
+- Ensure `UpdateUser` cleans up the index when updating names.
+- Ensure Checks can be set for zero values.
+
+### UI Improvements
+
+- Create buckets in the Data Explorer and Cell Editor.
+
+---
+
+## v2.0.0-beta.9 [2020-04-23]
+
+### Bug Fixes
+- Add index for URM by user ID to improve lookup performance.
+- Existing session expiration time is respected on session renewal.
+- Make CLI respect environment variables and flags and extend support for config orgs to all commands.
+
+### UI Improvements
+- Update layout of alerts page to work on all screen sizes.
+- Sort dashboards on Getting Started page by recently modified.
+- Add single-color schemes for visualizations: Solid Red, Solid Blue, Solid Yellow, Solid Green, and Solid Purple.
+
+---
+
+## v2.0.0-beta.8 [2020-04-10]
+
+### Features
+- Add `influx config` CLI command to switch back to previous activated configuration.
+- Introduce new navigation menu.
+- Add `-file` option to `influx query` and `influx task` CLI commands.
+- Add support for command line options to limit memory for queries.
+
+### Bug Fixes
+- Fix card size and layout issues in dashboards index view.
+- Fix check graph font and lines defaulting to black causing graph to be unreadable
+- Fix text-wrapping display issue and popover sizing bug when adding labels to a resource.
+- Respect the now-time of the compiled query if provided.
+- Fix spacing between ticks.
+- Fix typos in Flux functions list.
+
+### UI Improvements
+- Update layout of Alerts page to work on all screen sizes.
+- Sort dashboards on Getting Started page by recently modified.
+
+---
+
+## v2.0.0-beta.7 [2020-03-27]
+
+### Features
+
+- Add option to display dashboards in [light mode](/influxdb/v2.2/visualize-data/dashboards/control-dashboard/#toggle-dark-mode-and-light-mode).
+- Add [shell `completion` commands](/influxdb/v2.2/reference/cli/influx/completion/) to the `influx` CLI.
+  specified shell (`bash` or `zsh`).
+- Make all `pkg` resources unique by `metadata.name` field.
+- Ensure Telegraf configuration tokens aren't retrievable after creation. New tokens can be created after Telegraf has been setup.
+- [Delete bucket by name](/influxdb/v2.2/organizations/buckets/delete-bucket/#delete-a-bucket-by-name) using the `influx` CLI.
+- Add helper module to write line protocol to specified url, org, and bucket.
+- Add [`pkg stack`](/influxdb/v2.2/reference/cli/influx/stacks) for stateful package management.
+- Add `--no-tasks` flag to `influxd` to disable scheduling of tasks.
+- Add ability to output CLI output as JSON and hide table headers.
+- Add an [easy way to switch configurations](/influxdb/v2.2/reference/cli/influx/config/#quickly-switch-between-configurations) using the `influx` CLI.
+
+### Bug fixes
+
+- Fix NodeJS logo display in Firefox.
+- Fix Telegraf configuration bugs where system buckets were appearing in the Buckets list.
+- Fix threshold check bug where checks could not be created when a field had a space in the name.
+- Reuse slices built by iterator to reduce allocations.
+- Updated duplicate check error message to be more explicit and actionable.
+
+### UI improvements
+
+- Redesign OSS Login page.
+- Display graphic when a dashboard has no cells.
+
+---
+
+## v2.0.0-beta.6 [2020-03-12]
+
+### Features
+- Clicking on bucket name takes user to Data Explorer with bucket selected.
+- Extend pkger (InfluxDB Templates) dashboards with table view support.
+- Allow for retention to be provided to `influx setup` command as a duration.
+- Extend `influx pkg export all` capabilities to support filtering by lable name and resource type.
+- Added new login and sign-up screen for InfluxDB Cloud users that allows direct login from their region.
+- Added new `influx config` CLI for managing multiple configurations.
+
+### Bug Fixes
+- Fixed issue where tasks were exported for notification rules.
+- Fixed issue where tasks were not exported when exporting by organization ID.
+- Fixed issue where tasks with imports in the query would break in pkger.
+- Fixed issue where selecting an aggregate function in the script editor did not
+  add the function to a new line.
+- Fixed issue where creating a dashboard variable of type "map" piped the incorrect
+  value when map variables were used in queries.
+- Added missing usernames to `influx auth` CLI commands.
+- Disabled group functionality for check query builder.
+- Fixed cell configuration error that popped up when users created a dashboard
+  and accessed the "Disk Usage" cell for the first time.
+- Listing all the default variables in the Variable tab of the script editor.
+- Fixed bug that prevented the interval status on the dashboard header from
+  refreshing on selections.
+- Updated table custom decimal feature for tables to update on focus.
+- Fixed UI bug that set Telegraf config buttons off-center and resized config
+  selections when filtering through the data.
+- Fixed UI bug that caused dashboard cells to error when using `v.bucket` for the first time.
+- Fixed appearance of client library logos in Safari.
+- Fixed UI bug that prevented checks created with the query builder from updating.
+- Fixed a bug that prevented dashboard cell queries from working properly when
+  creating group queries using the query builder.
+
+### UI Improvements
+- Swap `billingURL` with `checkoutURL`.
+- Move Cloud navigation to top of page instead of within left side navigation.
+- Adjust aggregate window periods to use duration input with validation.
+
+---
+
+## v2.0.0-beta.5 [2020-02-27]
+
+### Features
+- Update Flux to v0.61.0.
+- Add secure flag to session cookie.
+- Add optional secret value flag to `influx secret` command.
+
+### Bug Fixes
+- Sort dashboards on homepage alphabetically.
+- Tokens page now sorts by status.
+- Set the default value of tags in a check.
+- Fix sort by variable type.
+- Calculate correct stacked line cumulative when lines are different lengths.
+- Resource cards are scrollable.
+- Query Builder groups on column values, not tag values.
+- Scatterplots render tooltips correctly.
+- Remove pkger gauge chart requirement for color threshold type.
+- Remove secret confirmation from `influx secret update`.
+
+---
+
+## v2.0.0-beta.4 [2020-02-14]
+
+### Features
+- Added labels to buckets.
+- Connect Monaco Editor to Flux LSP server.
+- Update Flux to v0.59.6.
+
+### Bug Fixes
+- Revert bad indexing of `UserResourceMappings` and `Authorizations`.
+- Prevent gauge visualization from becoming too small.
+
+---
+
+## v2.0.0-beta.3 [2020-02-11]
+
+### Features
+- Extend `influx cli pkg command` with ability to take multiple files and directories.
+- Extend `influx cli pkg command` with ability to take multiple URLs, files,
+  directories, and stdin at the same time.
+- `influx` CLI can manage secrets.
+
+### Bug Fixes
+- Fix notification rule renaming panics in UI.
+- Fix the tooltip for stacked line graphs.
+- Fixed false success notification for read-only users creating dashboards.
+- Fix issue with pkger/http stack crashing on duplicate content type.
+
+---
+
+## v2.0.0-beta.2 [2020-01-24]
+
+### Features
+- Change Influx packages to be CRD compliant.
+- Allow trailing newline in credentials file and CLI integration.
+- Add support for prefixed cursor search to ForwardCursor types.
+- Add backup and restore.
+- Introduce resource logger to tasks, buckets and organizations.
+
+### Bug Fixes
+- Check engine closed before collecting index metrics.
+- Reject writes which use any of the reserved tag keys.
+
+### UI Improvements
+- Swap `billingURL` with `checkoutURL`.
+- Move Cloud navigation to top of page instead of within left side navigation.
+- Adjust aggregate window periods to use duration input with validation.
+
+---
+
+## v2.0.0-beta.1 [2020-01-08]
+
+### Features
+- Add support for notification endpoints to `influx` templates and packages.
+- Drop `id` prefix for secret key requirement for notification endpoints.
+- Add support for check resource to `pkger` parser.
+- Add support for check resource `pkger` dry run functionality
+- Add support for check resource `pkger` apply functionality
+- Add support for check resource `pkger` export functionality
+- Add new `kv.ForwardCursor` interface.
+- Add support for notification rule to `pkger` parser.
+- Add support for notification rule `pkger` dry run functionality
+- Add support for notification rule `pkger` apply functionality.
+- Add support for notification rule `pkger` export functionality.
+- Add support for tasks to `pkger` parser.
+- Add support for tasks to `pkger` dry run functionality
+- Add support for tasks to `pkger` apply functionality.
+- Add support for tasks to `pkger` export functionality.
+- Add `group()` to Query Builder.
+- Add last run status to check and notification rules.
+- Add last run status to tasks.
+- Extend `pkger` apply functionality with ability to provide secrets outside of package.
+- Add hide headers flag to `influx` CLI task find command.
+- Manual overrides for readiness endpoint.
+- Drop legacy inmem service implementation in favor of KV service with inmem dependency.
+- Drop legacy bolt service implementation in favor of KV service with bolt dependency.
+- While creating check, also display notification rules that would match check based on tag rules.
+- Increase default bucket retention period to 30 days.
+- Add toggle to table thresholds to allow users to choose between setting threshold colors to text or background.
+- Add developer documentation.
+- Capture User-Agent header as query source for logging purposes.
+
+### Bug Fixes
+- Ensure environment variables are applied consistently across command and fixes issue where `INFLUX_` environment variable prefix was not set globally.
+- Remove default frontend sorting when flux queries specify sorting.
+- Store canceled task runs in the correct bucket.
+- Update `sortby` functionality for table frontend sorts to sort numbers correctly.
+- Prevent potential infinite loop when finding tasks by organization.
+- Retain user input when parsing invalid JSON during import.
+- Fix test issues due to multiple flush/sign-ins being called in the same test suite.
+- Update `influx` CLI to show only "see help" message, instead of the whole usage.
+- Fix notification tag-matching rules and enable tests to verify.
+- Extend y-axis when stacked graph is selected.
+- Fix query reset bug that was resetting query in script editor whenever dates were changed.
+- Fix table threshold bug defaulting set colors to the background.
+- Time labels no longer squished to the left.
+- Fix underlying issue with disappearing queries made in Advanced Mode.
+- Prevent negative zero and allow zero to have decimal places.
+- Limit data loader bucket selection to non system buckets.
+
+### UI Improvements
+- Add honeybadger reporting to create checks.
+
+---
+
+## v2.0.0-alpha.21 [2019-12-13]
+
+### Features
+- Add stacked line layer option to graphs.
+- Annotate log messages with trace ID, if available.
+- Bucket create to accept an organization name flag.
+- Add trace ID response header to query endpoint.
+
+### Bug Fixes
+- Allow table columns to be draggable in table settings.
+- Light up the home page icon when active.
+- Make numeric inputs first class citizens.
+- Prompt users to make a dashboard when dashboards are empty.
+- Remove name editing from query definition during threshold check creation.
+- Wait until user stops dragging and releases marker before zooming in after threshold changes.
+- Adds properties to each cell on `GET /dashboards/{dashboardID}`.
+- Gracefully handle invalid user-supplied JSON.
+- Fix crash when loading queries built using the query builder.
+- Create cell view properties on dashboard creation.
+- Update scrollbar style.
+- Fixed table UI threshold colorization issue.
+- Fixed windowPeriod issue that stemmed from Webpack rules.
+- Added delete functionality to note cells so that they can be deleted
+- Fix failure to create labels when creating Telegraf configs
+- Fix crash when editing a Telegraf config.
+- Updated start/end time functionality so that custom script time ranges overwrite dropdown selections.
+
+---
+
+## v2.0.0-alpha.20 [2019-11-20]
+
+### Features
+- Add TLS insecure skip verify to influx CLI.
+- Extend influx cli user create to allow for organization ID and user passwords to be set on user.
+- Auto-populate organization IDs in the code samples.
+- Expose bundle analysis tools for front end resources.
+- Allow users to view just the output section of a Telegraf config.
+- Allow users to see string data in single stat graph type.
+
+### Bug Fixes
+- Fix long startup when running `influx help`.
+- Mock missing Flux dependencies when creating tasks.
+- Ensure array cursor iterator stats accumulate all cursor stats.
+- Hide Members section in Cloud environments.
+- Change how cloud mode is enabled.
+- Merge front end development environments.
+- Refactor table state logic on the front end.
+- Arrows in tables show data in ascending and descending order.
+- Sort by retention rules now sorts by second.
+- Horizontal scrollbar no longer covering data;
+- Allow table columns to be draggable in table settings.
+- Light up the home page icon when active.
+- Make numeric inputs first-class citizens.
+- Prompt users to make a dashboard when dashboards are empty.
+- Remove name editing from query definition during threshold check creation.
+- Wait until user stops dragging and releases marker before zooming in after threshold changes.
+
+### UI Improvements
+- Redesign cards and animations on Getting Started page.
+- Allow users to filter with labels in Telegraf input search.
+
+---
+
+## v2.0.0-alpha.19 [2019-10-30]
+
+### Features
+- Add shortcut for toggling comments and submitting in Script Editor.
+
+### UI Improvements
+- Redesign page headers to be more space-efficient.
+- Add 403 handler that redirects back to the sign-in page on oats-generated routes.
+
+### Bug Fixes
+- Ensure users are created with an active status.
+- Added missing string values for `CacheStatus` type.
+- Disable saving for threshold check if no threshold selected.
+- Query variable selector shows variable keys, not values.
+- Create Label overlay disables the submit button and returns a UI error if name field is empty.
+- Log error as info message on unauthorized API call attempts.
+- Ensure `members` and `owners` endpoints lead to 404 when organization resource does not exist.
+- Telegraf UI filter functionality shows results based on input name.
+- Fix Telegraf UI sort functionality.
+- Fix task UI sort functionality.
+- Exiting a configuration of a dashboard cell properly renders the cell content.
+- Newly created checks appear on the checklist.
+- Changed task runs success status code from 200 to 201 to match Swagger documentation.
+- Text areas have the correct height.
+
+---
+
+## v2.0.0-alpha.18 [2019-09-26]
+
+### Features
+- Add jsonweb package for future JWT support.
+- Added the JMeter Template dashboard.
+
+### UI Improvements
+- Display dashboards index as a grid.
+- Add viewport scaling to html meta for responsive mobile scaling.
+- Remove rename and delete functionality from system buckets.
+-  Prevent new buckets from being named with the reserved `_` prefix.
+- Prevent user from selecting system buckets when creating Scrapers, Telegraf configurations, read/write tokens, and when saving as a task.
+- Limit values from draggable threshold handles to 2 decimal places.
+- Redesign check builder UI to fill the screen and make more room for composing message templates.
+- Move Tokens tab from Settings to Load Data page.
+- Expose all Settings tabs in navigation menu.
+- Added Stream and table functions to query builder.
+
+### Bug Fixes
+- Remove scrollbars blocking onboarding UI step.
+
+---
+
+## v2.0.0-alpha.17 [2019-08-14]
+
+### Features
+- Optional gzip compression of the query CSV response.
+- Add task types.
+- When getting task runs from the API, runs will be returned in order of most recently scheduled first.
+
+### Bug Fixes
+- Fix authentication when updating a task with invalid org or bucket.
+- Update the documentation link for Telegraf.
+- Fix to surface errors properly as task notifications on create.
+- Fix limiting of get runs for task.
+
+---
+
+## v2.0.0-alpha.16 [2019-07-25]
+
+### Bug Fixes
+- Add link to documentation text in line protocol upload overlay.
+- Fix issue in Authorization API, can't create auth for another user.
+- Fix Influx CLI ignored user flag for auth creation.
+- Fix the map example in the documentation.
+- Ignore null/empty Flux rows which prevents a single stat/gauge crash.
+- Fixes an issue where clicking on a dashboard name caused an incorrect redirect.
+- Upgrade templates lib to 0.5.0.
+- Upgrade giraffe lib to 0.16.1.
+- Fix incorrect notification type for manually running a task.
+- Fix an issue where canceled tasks did not resume.
+
+---
+
+## v2.0.0-alpha.15 [2019-07-11]
+
+### Features
+- Add time zone support to UI.
+- Added new storage inspection tool to verify TSM files.
+
+### Bug Fixes
+- Fix incorrect reporting of tasks as successful when errors occur during result iteration.
+
+#### Known Issues
+The version of Flux included in Alpha 14 introduced `null` support.
+Most issues related to the `null` implementation have been fixed, but one known issue remains –
+The `map()` function panics if the first record processed has a `null` value.
+
+---
+
+## v2.0.0-alpha.14 [2019-06-28]
+
+### Features
+- Add `influxd inspect verify-wal` tool.
+- Move to [Flux 0.34.2](/{{< latest "flux" >}}/release-notes/#v0342-2019-06-27) -
+  includes new string functions and initial multi-datasource support with `sql.from()`.
+- Only click save once to save cell.
+- Enable selecting more columns for line visualizations.
+
+### UI Improvements
+- Draw gauges correctly on HiDPI displays.
+- Clamp gauge position to gauge domain.
+- Improve display of error messages.
+- Remove rendering bottleneck when streaming Flux responses.
+- Prevent variable dropdown from clipping.
+
+---
+
+## v2.0.0-alpha.13 [2019-06-13]
+
+### Features
+- Add static templates for system, Docker, Redis, Kubernetes.
+
+---
+
+## v2.0.0-alpha.12 [2019-06-13]
+
+### Features
+- Enable formatting line graph y ticks with binary prefix.
+- Add x and y column pickers to graph types.
+- Add option to shade area below line graphs.
+
+### Bug Fixes
+- Fix performance regression in graph tooltips.
+
+---
+
+## v2.0.0-alpha.11 [2019-05-31]
+
+### Bug Fixes
+- Correctly check if columnKeys include xColumn in heatmap.
+
+---
+
+## v2.0.0-alpha.10 [2019-05-30]
+
+### Features
+- Add heatmap visualization type.
+- Add scatterplot graph visualization type.
+- Add description field to tasks.
+- Add CLI arguments for configuring session length and renewal.
+- Add smooth interpolation option to line graphs.
+
+### Bug Fixes
+- Removed hardcoded bucket for Getting Started with Flux dashboard.
+- Ensure map type variables allow for selecting values.
+- Generate more idiomatic Flux in query builder.
+- Expand tab key presses to two spaces in the Flux editor.
+- Prevent dragging of variable dropdowns when dragging a scrollbar inside the dropdown.
+- Improve single stat computation.
+- Fix crash when opening histogram settings with no data.
+
+### UI Improvements
+- Render checkboxes in query builder tag selection lists.
+- Fix jumbled card text in Telegraf configuration wizard.
+- Change scrapers in scrapers list to be resource cards.
+- Export and download resource with formatted resource name with no spaces.
+
+---
+
+## v2.0.0-alpha.9 [2019-05-01]
+
+{{% warn %}}
+**This will remove all tasks from your InfluxDB v2.0 instance.**
+
+Before upgrading, [export all existing tasks](/influxdb/v2.2/process-data/manage-tasks/export-task/). After upgrading, [reimport your exported tasks](/influxdb/v2.2/process-data/manage-tasks/create-task/#import-a-task).
+{{% /warn %}}
+
+### Features
+- Set autorefresh of dashboard to pause if absolute time range is selected.
+- Switch task back end to a more modular and flexible system.
+- Add org profile tab with ability to edit organization name.
+- Add org name to dashboard page title.
+- Add cautioning to bucket renaming.
+- Add option to generate all access token in tokens tab.
+- Add option to generate read/write token in tokens tab.
+- Add new Local Metrics Dashboard template that is created during Quick Start.
+
+### Bug Fixes
+- Fixed scroll clipping found in label editing flow.
+- Prevent overlapping text and dot in time range dropdown.
+- Updated link in notes cell to a more useful site.
+- Show error message when adding line protocol.
+- Update UI Flux function documentation.
+- Update System template to support math with floats.
+- Fix the `window` function documentation.
+- Fix typo in the `range` Flux function example.
+- Update the `systemTime` function to use `system.time`.
+
+### UI Improvements
+- Add general polish and empty states to Create Dashboard from Template overlay.
+
+---
+
+## v2.0.0-alpha.8 [2019-04-12]
+
+### Features
+- Add the ability to edit token's description.
+- Add the option to create a dashboard from a template.
+- Add the ability to add labels on variables.
+- Add switch organizations dropdown to home navigation menu item.
+- Add create org to side nav.
+- Add "Getting Started with Flux" template.
+- Update to Flux v0.25.0.
+
+### Bug Fixes
+- Update shift to timeShift in Flux functions sidebar.
+
+### UI Improvements
+- Update cursor to grab when hovering draggable areas.
+- Sync note editor text and preview scrolling.
+- Add the ability to create a bucket when creating an organization.
+
+---
+
+## v2.0.0-alpha.7 [2019-03-28]
+
+### Features
+- Insert Flux function near cursor in Flux Editor.
+- Enable the use of variables in the Data Explorer and Cell Editor Overlay.
+- Add a variable control bar to dashboards to select values for variables.
+- Add ability to add variable to script from the side menu.
+- Use time range for meta queries in Data Explorer and Cell Editor Overlay.
+- Fix screen tearing bug in raw data view.
+- Add copy to clipboard button to export overlays.
+- Enable copying error messages to the clipboard from dashboard cells.
+- Add the ability to update token's status in token list.
+- Allow variables to be re-ordered within control bar on a dashboard.
+- Add the ability to delete a template.
+- Save user preference for variable control bar visibility and default to visible.
+- Add the ability to clone a template.
+- Add the ability to import a variable.
+
+### Bug Fixes
+- Fix mismatch in bucket row and header.
+- Allows user to edit note on cell.
+- Fix empty state styles in scrapers in org view.
+- Fix bucket creation error when changing retention rules types.
+- Fix task creation error when switching schedule types.
+- Fix hidden horizontal scrollbars in flux raw data view.
+- Fix screen tearing bug in raw data View.
+- Fix routing loop.
+
+### UI Improvements
+- Move bucket selection in the query builder to the first card in the list.
+- Ensure editor is automatically focused in Note Editor.
+- Add ability to edit a template's name.
+
+---
+
+## v2.0.0-alpha.6 [2019-03-15]
+
+### Release Notes
+
+{{% warn %}}
+We have updated the way we do predefined dashboards to [include Templates](https://github.com/influxdata/influxdb/pull/12532)
+in this release which will cause existing Organizations to not have a System
+dashboard created when they build a new Telegraf configuration.
+In order to get this functionality, remove your existing data and start from scratch.
+
+_**This will remove all data from your InfluxDB v2.0 instance including time series data.**_
+
+###### Linux and macOS
+```sh
+rm ~/.influxdbv2/influxd.bolt
+```
+
+Once completed, `v2.0.0-alpha.6` can be started.
+{{% /warn %}}
+
+### Features
+- Add ability to import a dashboard.
+- Add ability to import a dashboard from organization view.
+- Add ability to export a dashboard and a task.
+- Add `run` subcommand to `influxd` binary. This is also the default when no subcommand is specified.
+- Add ability to save a query as a variable from the Data Explorer.
+- Add System template on onboarding.
+
+### Bug Fixes
+- Stop scrollbars from covering text in Flux editor.
+
+### UI Improvements
+- Fine tune keyboard interactions for managing labels from a resource card.
+
+---
+
+## v2.0.0-alpha.5 [2019-03-08]
+
+{{% warn %}}
+This release includes a breaking change to the format in which Time-Structured Merge Tree (TSM) and index data are stored on disk.
+_**Existing local data will not be queryable after upgrading to this release.**_
+
+Prior to installing this release, remove all storage-engine data from your local InfluxDB 2.x installation.
+To remove only TSM and index data and preserve all other other InfluxDB 2.x data (organizations, buckets, settings, etc),
+run the following command.
+
+###### Linux and macOS
+```sh
+rm -r ~/.influxdbv2/engine
+```
+
+Once completed, InfluxDB v2.0.0-alpha.5 can be started.
+{{% /warn %}}
+
+### Features
+- Add labels to cloned tasks.
+- Add ability to filter resources by clicking a label.
+- Add ability to add a member to org.
+- Improve representation of TSM tagsets on disk.
+- Add ability to remove a member from org.
+- Update to Flux v0.21.4.
+
+### Bug Fixes
+- Prevent clipping of code snippets in Firefox.
+- Prevent clipping of cell edit menus in dashboards.
+
+### UI Improvements
+- Make code snippet copy functionality easier to use.
+- Always show live preview in note cell editor.
+- Redesign scraper creation workflow.
+- Show warning in Telegraf and scraper lists when user has no buckets.
+- Streamline label addition, removal, and creation from the dashboards list.
+
+---
+
+## v2.0.0-alpha.4 [2019-02-21]
+
+### Features
+- Add the ability to run a task manually from tasks page.
+- Add the ability to select a custom time range in explorer and dashboard.
+- Display the version information on the login page.
+- Add the ability to update a variable's name and query.
+- Add labels to cloned dashboard.
+- Add ability filter resources by label name.
+- Add ability to create or add labels to a resource from labels editor.
+- Update to Flux v0.20.
+
+### Bug Fixes
+- Update the bucket retention policy to update the time in seconds.
+
+### UI Improvements
+- Update the preview in the label overlays to be shorter.
+- Add notifications to scrapers page for created/deleted/updated scrapers.
+- Add notifications to buckets page for created/deleted/updated buckets.
+- Update the admin page to display error for password length.
+
+---
+
+## v2.0.0-alpha.3 [2019-02-15]
+
+### Features
+- Add the ability to name a scraper target.
+- Display scraper name as the first and only updatable column in scrapers list.
+- Add the ability to view runs for a task.
+- Display last completed run for tasks list.
+- Add the ability to view the logs for a specific task run.
+
+### Bug Fixes
+- Update the inline edit for resource names to guard for empty strings.
+- Prevent a new template dashboard from being created on every Telegraf config update.
+- Fix overlapping buttons in Telegraf verify data step.
+
+### UI Improvements
+- Move the download Telegraf config button to view config overlay.
+- Combine permissions for user by type.
+
+---
+
+## v2.0.0-alpha.2 [2019-02-07]
+
+### Features
+- Add instructions button to view `$INFLUX_TOKEN` setup for Telegraf configs.
+- Save the `$INFLUX_TOKEN` environmental variable in Telegraf configs.
+- Update Tasks tab on Organizations page to look like Tasks Page.
+- Add view button to view the Telegraf config toml.
+- Add plugin information step to allow for config naming and configure one plugin at a time.
+- Update Dashboards tab on Organizations page to look like Dashboards Page.
+
+### Bug Fixes
+- Update the System Telegraf Plugin bundle to include the Swap plugin.
+- Revert behavior allowing users to create authorizations on behalf of another user.
+
+### UI Improvements
+- Change the wording for the plugin config form button to "Done."
+- Change the wording for the Collectors configure step button to "Create and Verify."
+- Standardize page loading spinner styles.
+- Show checkbox on "Save As" button in data explorer.
+- Make collectors plugins side bar visible in only the configure step.
+- Swap retention policies on Create bucket page.
+
+---
+
+## v2.0.0-alpha.1 [2019-01-23]
+
+This is the initial alpha release of InfluxDB 2.0.
diff --git a/content/influxdb/v2.2/reference/release-notes/supported-release.md b/content/influxdb/v2.2/reference/release-notes/supported-release.md
new file mode 100644
index 000000000..47d7d8f71
--- /dev/null
+++ b/content/influxdb/v2.2/reference/release-notes/supported-release.md
@@ -0,0 +1,36 @@
+---
+title: Supported releases 
+description: >
+  Supported releases made to InfluxData. 
+menu:
+  influxdb_2_2_ref:
+    name: Supported releases 
+    parent: Release notes
+weight: 204
+related:
+  - /influxdb/v2.2/reference/release-notes
+---
+
+InfluxData provides support for the following minor, major, and maintenance releases: 
+
+##### Major
+
+- Includes new features, enhancements to existing features, and applicable error corrections from all prior releases.
+- InfluxDB supports backward compatibility within a major release.
+
+##### Minor (x.Y.z) 
+
+- Includes new minor features, enhancements to existing features, and includes applicable error corrections from prior minor and maintenance releases. 
+
+##### Maintenance (x.y.Z) 
+
+- Includes error corrections severely affecting a number of customers that cannot wait for the next major or minor release. Include applicable error corrections made in prior maintenance releases. Released as as needed based on customer feedback and outstanding errors (no predefined schedule).
+- Interim (x.y.z.A) Fourth digit (or beyond) are an exception, and only delivered to address specific customer issues. These releases are retired in a timely manner by the customer once the issue has been addressed in a standard release.
+- InfluxData provides Support Services for the current and previous Minor Release (x.Y) including Maintenance Releases (x.y.Z) included in the respective Minor Release. 
+- When InfluxData releases a Major Release (X.y), InfluxData will provide Support Services for the current and preceding Major Release (X.y), including all Maintenance Releases (x.y.Z) included in the respective Minor Release that is available at least 12 months from the Major Release. 
+
+For more information about supported 2.x releases, click [here](https://www.influxdata.com/legal/support-policy/).
+
+{{% note %}}
+The link above contains the full legal description of the supported releases. 
+{{% /note %}}
\ No newline at end of file
diff --git a/content/influxdb/v2.2/reference/sample-data.md b/content/influxdb/v2.2/reference/sample-data.md
new file mode 100644
index 000000000..bfb3d5916
--- /dev/null
+++ b/content/influxdb/v2.2/reference/sample-data.md
@@ -0,0 +1,161 @@
+---
+title: Sample data
+description: >
+  Use sample data to familiarize yourself with time series data and InfluxDB.
+  InfluxData provides many sample time series datasets to use with InfluxDB
+  and InfluxDB Cloud.
+aliases:
+  - /influxdb/v2.2/write-data/sample-data/
+menu: influxdb_2_2_ref
+weight: 7
+---
+
+Use sample data to familiarize yourself with time series data and InfluxDB.
+InfluxData provides many sample time series datasets to use with InfluxDB.
+You can also use the [Flux InfluxDB sample package](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/sample/)
+to view, download, and output sample datasets.
+
+- [Air sensor sample data](#air-sensor-sample-data)
+- [Bird migration sample data](#bird-migration-sample-data)
+- [NOAA sample data](#noaa-sample-data)
+  - [NOAA NDBC data](#noaa-ndbc-data)
+  - [NOAA water sample data](#noaa-water-sample-data)
+- [USGS Earthquake data](#usgs-earthquake-data)
+
+## Air sensor sample data
+
+{{% caption %}}
+**Size**: ~600 KB • **Updated**: every 15m
+{{% /caption %}}
+
+Air sensor sample data represents an "Internet of Things" (IoT) use case by simulating
+temperature, humidity, and carbon monoxide levels for multiple rooms in a building.
+
+To download and output the air sensor sample dataset, use the
+[`sample.data()` function](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/sample/data/).
+
+```js
+import "influxdata/influxdb/sample"
+
+sample.data(set: "airSensor")
+```
+
+#### Companion SQL sensor data
+The air sensor sample dataset is paired with a relational SQL dataset with meta
+information about sensors in each room.
+These two sample datasets are used to demonstrate
+[how to join time series data and relational data with Flux](/influxdb/v2.2/query-data/flux/sql/#join-sql-data-with-data-in-influxdb)
+in the [Query SQL data sources](/influxdb/v2.2/query-data/flux/sql/) guide.
+
+<a class="btn download" href="https://influx-testdata.s3.amazonaws.com/sample-sensor-info.csv" download>Download SQL air sensor data</a>
+
+## Bird migration sample data
+
+{{% caption %}}
+**Size**: ~1.2 MB • **Updated**: N/A
+{{% /caption %}}
+
+Bird migration sample data is adapted from the
+[Movebank: Animal Tracking data set](https://www.kaggle.com/pulkit8595/movebank-animal-tracking)
+and represents animal migratory movements throughout 2019.
+
+To download and output the bird migration sample dataset, use the
+[`sample.data()` function](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/sample/data/).
+
+```js
+import "influxdata/influxdb/sample"
+
+sample.data(set: "birdMigration")
+```
+
+The bird migration sample dataset is used in the [Work with geo-temporal data](/influxdb/v2.2/query-data/flux/geo/)
+guide to demonstrate how to query and analyze geo-temporal data.
+
+## NOAA sample data
+
+There are two National Oceanic and Atmospheric Administration (NOAA) datasets 
+available to use with InfluxDB.
+
+- [NOAA NDBC data](#noaa-ndbc-data)
+- [NOAA water sample data](#noaa-water-sample-data)
+
+### NOAA NDBC data
+
+{{% caption %}}
+**Size**: ~1.3 MB • **Updated**: every 15m
+{{% /caption %}}
+
+The **NOAA National Data Buoy Center (NDBC)** dataset provides the latest
+observations from the NOAA NDBC network of buoys throughout the world.
+Observations are updated approximately every 15 minutes.
+
+To download and output the most recent NOAA NDBC observations, use the
+[`sample.data()` function](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/sample/data/).
+
+```js
+import "influxdata/influxdb/sample"
+
+sample.data(set: "noaa")
+```
+
+{{% note %}}
+#### Store historical NOAA NDBC data
+
+The **NOAA NDBC sample dataset** only returns the most recent observations;
+not historical observations.
+To regularly query and store NOAA NDBC observations, add the following as an
+[InfluxDB task](/influxdb/v2.2/process-data/manage-tasks/).
+Replace `example-org` and `example-bucket` with your organization name and the
+name of the bucket to store data in.
+
+{{% get-shared-text "flux/noaa-ndbc-sample-task.md" %}}
+{{% /note %}}
+
+### NOAA water sample data
+
+{{% caption %}}
+**Size**: ~10 MB • **Updated**: N/A
+{{% /caption %}}
+
+The **NOAA water sample dataset** is static dataset extracted from
+[NOAA Center for Operational Oceanographic Products and Services](http://tidesandcurrents.noaa.gov/stations.html) data.
+The sample dataset includes 15,258 observations of water levels (ft) collected every six minutes at two stations
+(Santa Monica, CA (ID 9410840) and Coyote Creek, CA (ID 9414575)) over the period
+from **August 18, 2015** through **September 18, 2015**.
+
+{{% note %}}
+#### Store NOAA water sample data to avoid bandwidth usage
+To avoid having to re-download this 10MB dataset every time you run a query,
+we recommend that you [create a new bucket](/influxdb/v2.2/organizations/buckets/create-bucket/)
+(`noaa`) and write the NOAA sample water data to it.
+
+```js
+import "experimental/csv"
+
+csv.from(url: "https://influx-testdata.s3.amazonaws.com/noaa.csv")
+    |> to(bucket: "noaa", org: "example-org")
+```
+{{% /note %}}
+
+The NOAA water sample dataset is used to demonstrate Flux queries in the
+[Common queries](/influxdb/v2.2/query-data/common-queries/) and
+[Common tasks](/influxdb/v2.2/process-data/common-tasks/) guides.
+
+## USGS Earthquake data
+
+{{% caption %}}
+**Size**: ~6 MB • **Updated**: every 15m
+{{% /caption %}}
+
+The United States Geological Survey (USGS) earthquake dataset contains observations
+collected from USGS seismic sensors around the world over the last week.
+Data is updated approximately every 15m.
+
+To download and output the last week of USGS seismic data, use the
+[`sample.data()` function](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/sample/data/).
+
+```js
+import "influxdata/influxdb/sample"
+
+sample.data(set: "usgs")
+```
diff --git a/content/influxdb/v2.2/reference/syntax/_index.md b/content/influxdb/v2.2/reference/syntax/_index.md
new file mode 100644
index 000000000..d4edcf555
--- /dev/null
+++ b/content/influxdb/v2.2/reference/syntax/_index.md
@@ -0,0 +1,18 @@
+---
+title: InfluxDB syntaxes
+description: >
+  InfluxDB uses a handful of languages and syntaxes to perform tasks such as
+  writing, querying, processing, and deleting data.
+weight: 5
+menu:
+  influxdb_2_2_ref:
+    name: Syntax
+influxdb/v2.2/tags: [syntax]
+---
+
+InfluxDB uses a handful of languages and syntaxes to perform tasks such as
+writing, querying, processing, and deleting data.
+The following articles provide information about the different syntaxes used with
+InfluxDB and the contexts in which they're used:
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/reference/syntax/annotated-csv/_index.md b/content/influxdb/v2.2/reference/syntax/annotated-csv/_index.md
new file mode 100644
index 000000000..b8ed46ba5
--- /dev/null
+++ b/content/influxdb/v2.2/reference/syntax/annotated-csv/_index.md
@@ -0,0 +1,311 @@
+---
+title: Annotated CSV
+description: >
+  InfluxDB and Flux return query results in annotated CSV format.
+  You can also read annotated CSV directly from Flux with the `csv.from()` function,
+  write data to InfluxDB using annotated CSV and the `influx write` command, or upload a CSV file in the UI.
+weight: 103
+menu:
+  influxdb_2_2_ref:
+    parent: Syntax
+influxdb/v2.2/tags: [csv, syntax]
+related:
+  - /{{< latest "flux" >}}/stdlib/csv/from/
+  - /influxdb/v2.2/reference/syntax/annotated-csv/extended/
+---
+
+InfluxDB and Flux return query results in annotated CSV format.
+You can also read annotated CSV directly from Flux with the [`csv.from()` function](/{{< latest "flux" >}}/stdlib/csv/from/), write data to InfluxDB using annotated CSV and the `influx write` command, or [upload a CSV file](/influxdb/cloud/write-data/no-code/load-data/#load-data-by-uploading-a-csv-or-line-protocol-file) in the UI.
+
+CSV tables must be encoded in UTF-8 and Unicode Normal Form C as defined in [UAX15](http://www.unicode.org/reports/tr15/).
+InfluxDB removes carriage returns before newline characters.
+
+## Examples
+
+In this topic, you'll find examples of valid CSV syntax for responses to the following query:
+
+```js
+from(bucket:"mydb/autogen")
+    |> range(start:2018-05-08T20:50:00Z, stop:2018-05-08T20:51:00Z)
+    |> group(columns:["_start","_stop", "region", "host"])
+    |> yield(name:"my-result")
+```
+
+## CSV response format
+
+Flux supports encodings listed below.
+
+### Tables
+
+A table may have the following rows and columns.
+
+#### Rows
+
+- **Annotation rows**: describe column properties.
+
+- **Header row**: defines column labels (one header row per table).
+
+- **Record row**: describes data in the table (one record per row).
+
+##### Example
+
+Encoding of a table with and without a header row.
+
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[Header row](#)
+[Without header row](#)
+{{% /code-tabs %}}
+
+{{% code-tab-content %}}
+```sh
+result,table,_start,_stop,_time,region,host,_value
+my-result,0,2018-05-08T20:50:00Z,2018-05-08T20:51:00Z,2018-05-08T20:50:00Z,east,A,15.43
+my-result,0,2018-05-08T20:50:00Z,2018-05-08T20:51:00Z,2018-05-08T20:50:20Z,east,B,59.25
+my-result,0,2018-05-08T20:50:00Z,2018-05-08T20:51:00Z,2018-05-08T20:50:40Z,east,C,52.62
+```
+{{% /code-tab-content %}}
+
+{{% code-tab-content %}}
+```sh
+my-result,0,2018-05-08T20:50:00Z,2018-05-08T20:51:00Z,2018-05-08T20:50:00Z,east,A,15.43
+my-result,0,2018-05-08T20:50:00Z,2018-05-08T20:51:00Z,2018-05-08T20:50:20Z,east,B,59.25
+my-result,0,2018-05-08T20:50:00Z,2018-05-08T20:51:00Z,2018-05-08T20:50:40Z,east,C,52.62
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+#### Columns
+
+In addition to the data columns, a table may include the following columns:
+
+- **Annotation column**: Only used in annotation rows. Always the first column.
+  Displays the name of an annotation. Value can be empty or a supported [annotation](#annotations).
+  You'll notice a space for this column for the entire length of the table,
+  so rows appear to start with `,`.
+
+- **Result column**: Contains the name of the result specified by the query.
+
+- **Table column**: Contains a unique ID for each table in a result.
+
+### Multiple tables and results
+
+If a file or data stream contains multiple tables or results, the following requirements must be met:
+
+- A table column indicates which table a row belongs to.
+- All rows in a table are contiguous.
+- An empty row delimits a new table boundary in the following cases:
+    - Between tables in the same result that do not share a common table schema.
+    - Between concatenated CSV files.
+- Each new table boundary starts with new annotation and header rows.
+
+##### Example
+
+Encoding of two tables in the same result with the same schema (header row) and different schema.
+
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[Same schema](#)
+[Different schema](#)
+{{% /code-tabs %}}
+
+{{% code-tab-content %}}
+```sh
+result,table,_start,_stop,_time,region,host,_value
+my-result,0,2018-05-08T20:50:00Z,2018-05-08T20:51:00Z,2018-05-08T20:50:00Z,east,A,15.43
+my-result,0,2018-05-08T20:50:00Z,2018-05-08T20:51:00Z,2018-05-08T20:50:20Z,east,B,59.25
+my-result,0,2018-05-08T20:50:00Z,2018-05-08T20:51:00Z,2018-05-08T20:50:40Z,east,C,52.62
+my-result,1,2018-05-08T20:50:00Z,2018-05-08T20:51:00Z,2018-05-08T20:50:00Z,west,A,62.73
+my-result,1,2018-05-08T20:50:00Z,2018-05-08T20:51:00Z,2018-05-08T20:50:20Z,west,B,12.83
+my-result,1,2018-05-08T20:50:00Z,2018-05-08T20:51:00Z,2018-05-08T20:50:40Z,west,C,51.62
+
+```
+{{% /code-tab-content %}}
+
+{{% code-tab-content %}}
+```sh
+,result,table,_start,_stop,_time,region,host,_value
+,my-result,0,2018-05-08T20:50:00Z,2018-05-08T20:51:00Z,2018-05-08T20:50:00Z,east,A,15.43
+,my-result,0,2018-05-08T20:50:00Z,2018-05-08T20:51:00Z,2018-05-08T20:50:20Z,east,B,59.25
+,my-result,0,2018-05-08T20:50:00Z,2018-05-08T20:51:00Z,2018-05-08T20:50:40Z,east,C,52.62
+
+,result,table,_start,_stop,_time,location,device,min,max
+,my-result,1,2018-05-08T20:50:00Z,2018-05-08T20:51:00Z,2018-05-08T20:50:00Z,USA,5825,62.73,68.42
+,my-result,1,2018-05-08T20:50:00Z,2018-05-08T20:51:00Z,2018-05-08T20:50:20Z,USA,2175,12.83,56.12
+,my-result,1,2018-05-08T20:50:00Z,2018-05-08T20:51:00Z,2018-05-08T20:50:40Z,USA,6913,51.62,54.25
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+## Dialect options
+
+Flux supports the following dialect options for `text/csv` format.
+
+| Option            | Description                                                       | Default |
+| :--------         | :---------                                                        |:-------:|
+| **header**        | If true, the header row is included.                              | `true`  |
+| **delimiter**     | Character used to delimit columns.                                | `,`     |
+| **quoteChar**     | Character used to quote values containing the delimiter.          | `"`     |
+| **annotations**   | List of annotations to encode (datatype, group, or default).      | `empty` |
+| **commentPrefix** | String prefix to identify a comment. Always added to annotations. | `#`     |
+
+## Annotations
+
+Annotation rows describe column properties, and start with `#` (or commentPrefix value).
+The first column in an annotation row always contains the annotation name.
+Subsequent columns contain annotation values as shown in the table below.
+
+| Annotation name | Values                                                                         | Description                                                                      |
+|:--------        |:---------                                                                      | :-------                                                                         |
+| **datatype**    | a [data type](#data-types) or [line protocol element](#line-protocol-elements) | Describes the type of data or which line protocol element the column represents. |
+| **group**       | boolean flag `true` or `false`                                                 | Indicates the column is part of the group key.                                   |
+| **default**     | a value of the column's data type                                              | Value to use for rows with an empty value.                                       |
+
+
+{{% note %}}
+To encode a table with its [group key](/influxdb/v2.2/reference/glossary/#group-key),
+the `datatype`, `group`, and `default` annotations must be included.
+If a table has no rows, the `default` annotation provides the group key values.
+{{% /note %}}
+
+## Data types
+
+| Datatype     | Flux type  | Description                                                                                                    |
+| :--------    | :--------- | :----------                                                                                                    |
+| boolean      | bool       | "true" or "false"                                                                                              |
+| unsignedLong | uint       | unsigned 64-bit integer                                                                                        |
+| long         | int        | signed 64-bit integer                                                                                          |
+| double       | float      | IEEE-754 64-bit floating-point number                                                                          |
+| string       | string     | UTF-8 encoded string                                                                                           |
+| base64Binary | bytes      | base64 encoded sequence of bytes as defined in RFC 4648                                                        |
+| dateTime     | time       | instant in time, may be followed with a colon : and a description of the format (number, RFC3339, RFC3339Nano) |
+| duration     | duration   | length of time represented as an unsigned 64-bit integer number of nanoseconds                                 |
+
+
+## Line protocol elements
+The `datatype` annotation accepts [data types](#data-types) and **line protocol elements**.
+Line protocol elements identify how columns are converted into line protocol when using the
+[`influx write` command](/influxdb/v2.2/reference/cli/influx/write/) to write annotated CSV to InfluxDB.
+
+| Line protocol element | Description                                                     |
+|:--------------------- |:-----------                                                     |
+| `measurement`         | column value is the measurement                                 |
+| `field` _(default)_   | column header is the field key, column value is the field value |
+| `tag`                 | column header is the tag key, column value is the tag value     |
+| `time`                | column value is the timestamp _(alias for `dateTime`)_          |
+| `ignore` or`ignored`  | column is ignored and not included in line protocol             |
+
+### Mixing data types and line protocol elements
+Columns with [data types](#data-types) (other than `dateTime`) in the
+`#datatype` annotation are treated as **fields** when converted to line protocol.
+Columns without a specified data type default to `field` when converted to line protocol
+and **column values are left unmodified** in line protocol.
+_See an example [below](#example-of-mixing-data-types-line-protocol-elements) and
+[line protocol data types and format](/influxdb/v2.2/reference/syntax/line-protocol/#data-types-and-format)._
+
+### Time columns
+A column with `time` or `dateTime` `#datatype` annotations are used as the timestamp
+when converted to line protocol.
+If there are multiple `time` or `dateTime` columns, the last column (on the right)
+is used as the timestamp in line protocol.
+Other time columns are ignored and the `influx write` command outputs a warning.
+
+Time column values should be **Unix timestamps** (in an [accepted timestamp precision](/influxdb/v2.2/write-data/#timestamp-precision)),
+**RFC3339**, or **RFC3339Nano**.
+
+##### Example line protocol elements in datatype annotation
+```
+#datatype measurement,tag,tag,field,field,ignored,time
+m,cpu,host,time_steal,usage_user,nothing,time
+cpu,cpu1,host1,0,2.7,a,1482669077000000000
+cpu,cpu1,host2,0,2.2,b,1482669087000000000
+```
+
+Resulting line protocol:
+
+```
+cpu,cpu=cpu1,host=host1 time_steal=0,usage_user=2.7 1482669077000000000
+cpu,cpu=cpu1,host=host2 time_steal=0,usage_user=2.2 1482669087000000000
+```
+
+##### Example of mixing data types line protocol elements
+```
+#datatype measurement,tag,string,double,boolean,long,unsignedLong,duration,dateTime
+#default test,annotatedDatatypes,,,,,,
+m,name,s,d,b,l,ul,dur,time
+,,str1,1.0,true,1,1,1ms,1
+,,str2,2.0,false,2,2,2us,2020-01-11T10:10:10Z
+```
+
+Resulting line protocol:
+
+```
+test,name=annotatedDatatypes s="str1",d=1,b=true,l=1i,ul=1u,dur=1000000i 1
+test,name=annotatedDatatypes s="str2",d=2,b=false,l=2i,ul=2u,dur=2000i 1578737410000000000
+```
+
+## Annotated CSV in Flux
+Flux requires all annotation and header rows in annotated CSV.
+The example below illustrates how to use the [`csv.from()` function](/{{< latest "flux" >}}/stdlib/csv/from/)
+to read annotated CSV in Flux:
+
+```js
+import "csv"
+
+csvData = "#datatype,string,long,dateTime:RFC3339,dateTime:RFC3339,dateTime:RFC3339,string,string,double,string
+#group,false,false,true,true,false,true,false,false,true
+#default,,,,,,,,,
+,result,table,_start,_stop,_time,region,host,_value,_measurement
+,,0,2018-05-08T20:50:00Z,2018-05-08T20:51:00Z,2018-05-08T20:50:00Z,east,A,15.43,cpu
+,,0,2018-05-08T20:50:00Z,2018-05-08T20:51:00Z,2018-05-08T20:50:20Z,east,B,59.25,cpu
+,,0,2018-05-08T20:50:00Z,2018-05-08T20:51:00Z,2018-05-08T20:50:40Z,east,C,52.62,cpu
+,,1,2018-05-08T20:50:00Z,2018-05-08T20:51:00Z,2018-05-08T20:50:00Z,west,A,62.73,cpu
+,,1,2018-05-08T20:50:00Z,2018-05-08T20:51:00Z,2018-05-08T20:50:20Z,west,B,12.83,cpu
+,,1,2018-05-08T20:50:00Z,2018-05-08T20:51:00Z,2018-05-08T20:50:40Z,west,C,51.62,cpu
+"
+
+csv.from(csv: csvData)
+```
+
+{{% warn %}}
+Flux only supports [data types](#data-types) in the `#datatype` annotation.
+It does **does not** support [line protocol elements](#line-protocol-elements).
+{{% /warn %}}
+
+## Errors
+
+If an error occurs during execution, a table returns with:
+
+- An error column that contains an error message.
+- A reference column with a unique reference code to identify more information about the error.
+- A second row with error properties.
+
+If an error occurs:
+
+- Before results materialize, the HTTP status code indicates an error. Error details are encoded in the csv table.
+- After partial results are sent to the client, the error is encoded as the next table and remaining results are discarded. In this case, the HTTP status code remains 200 OK.
+
+##### Example
+
+Encoding for an error with the datatype annotation:
+
+```
+#datatype,string,long
+,error,reference
+,Failed to parse query,897
+```
+
+Encoding for an error that occurs after a valid table has been encoded:
+
+```
+#datatype,string,long,dateTime:RFC3339,dateTime:RFC3339,dateTime:RFC3339,string,string,double
+,result,table,_start,_stop,_time,region,host,_value
+,my-result,1,2018-05-08T20:50:00Z,2018-05-08T20:51:00Z,2018-05-08T20:50:00Z,west,A,62.73
+,my-result,1,2018-05-08T20:50:00Z,2018-05-08T20:51:00Z,2018-05-08T20:50:20Z,west,B,12.83
+,my-result,1,2018-05-08T20:50:00Z,2018-05-08T20:51:00Z,2018-05-08T20:50:40Z,west,C,51.62
+```
+
+```
+#datatype,string,long
+,error,reference,query terminated: reached maximum allowed memory limits,576
+```
diff --git a/content/influxdb/v2.2/reference/syntax/annotated-csv/extended.md b/content/influxdb/v2.2/reference/syntax/annotated-csv/extended.md
new file mode 100644
index 000000000..8ed775e94
--- /dev/null
+++ b/content/influxdb/v2.2/reference/syntax/annotated-csv/extended.md
@@ -0,0 +1,396 @@
+---
+title: Extended annotated CSV
+description: >
+  Extended annotated CSV provides additional annotations and options that specify
+  how CSV data should be converted to [line protocol](/influxdb/v2.2/reference/syntax/line-protocol/)
+  and written to InfluxDB.
+menu:
+  influxdb_2_2_ref:
+    name: Extended annotated CSV
+    parent: Annotated CSV
+weight: 201
+influxdb/v2.2/tags: [csv, syntax, write]
+related:
+  - /influxdb/v2.2/write-data/developer-tools/csv/
+  - /influxdb/v2.2/reference/cli/influx/write/
+  - /influxdb/v2.2/reference/syntax/line-protocol/
+  - /influxdb/v2.2/reference/syntax/annotated-csv/
+---
+
+**Extended annotated CSV** provides additional annotations and options that specify
+how CSV data should be converted to [line protocol](/influxdb/v2.2/reference/syntax/line-protocol/)
+and written to InfluxDB.
+InfluxDB uses the [`csv2lp` library](https://github.com/influxdata/influxdb/tree/master/pkg/csv2lp)
+to convert CSV into line protocol.
+Extended annotated CSV supports all [Annotated CSV](/influxdb/v2.2/reference/syntax/annotated-csv/)
+annotations.
+
+{{% warn %}}
+The Flux [`csv.from` function](/{{< latest "flux" >}}/stdlib/csv/from/) only supports
+[annotated CSV](/influxdb/v2.2/reference/syntax/annotated-csv/), not extended annotated CSV.
+{{% /warn %}}
+
+To write data to InfluxDB, line protocol must include the following:
+
+- [measurement](/influxdb/v2.2/reference/syntax/line-protocol/#measurement)
+- [field set](/influxdb/v2.2/reference/syntax/line-protocol/#field-set)
+- [timestamp](/influxdb/v2.2/reference/syntax/line-protocol/#timestamp) _(Optional but recommended)_
+- [tag set](/influxdb/v2.2/reference/syntax/line-protocol/#tag-set) _(Optional)_
+
+Extended CSV annotations identify the element of line protocol a column represents.
+
+## CSV Annotations
+Extended annotated CSV extends and adds the following annotations:
+
+- [datatype](#datatype)
+- [constant](#constant)
+- [timezone](#timezone)
+- [concat](#concat)
+
+### datatype
+Use the `#datatype` annotation to specify the [line protocol element](/influxdb/v2.2/reference/syntax/line-protocol/#elements-of-line-protocol)
+a column represents.
+To explicitly define a column as a **field** of a specific data type, use the field
+type in the annotation (for example: `string`, `double`, `long`, etc.).
+
+| Data type                     | Resulting line protocol                 |
+|:----------                    |:-----------------------                 |
+| [measurement](#measurement)   | Column is the **measurement**           |
+| [tag](#tag)                   | Column is a **tag**                     |
+| [dateTime](#datetime)         | Column is the **timestamp**             |
+| [field](#field)               | Column is a **field**                   |
+| [ignored](#ignored)           | Column is ignored                       |
+| [string](#string)             | Column is a **string field**            |
+| [double](#double)             | Column is a **float field**             |
+| [long](#long)                 | Column is an **integer field**          |
+| [unsignedLong](#unsignedlong) | Column is an **unsigned integer field** |
+| [boolean](#boolean)           | Column is a **boolean field**           |
+
+#### measurement
+Indicates the column is the **measurement**.
+
+#### tag
+Indicates the column is a **tag**.
+The **column label** is the **tag key**.
+The **column value** is the **tag value**.
+
+#### dateTime
+Indicates the column is the **timestamp**.
+`time` is an alias for `dateTime`.
+If the [timestamp format](#supported-timestamp-formats) includes a time zone,
+the parsed timestamp includes the time zone offset.
+By default, all timestamps are UTC.
+You can also use the [`#timezone` annotation](#timezone) to adjust timestamps to
+a specific time zone.
+
+{{% note %}}
+There can only be **one** `dateTime` column.
+{{% /note %}}
+
+The `influx write` command converts timestamps to [Unix timestamps](/influxdb/v2.2/reference/glossary/#unix-timestamp).
+Append the timestamp format to the `dateTime` datatype with (`:`).
+
+```csv
+#datatype dateTime:RFC3339
+#datatype dateTime:RFC3339Nano
+#datatype dateTime:number
+#datatype dateTime:2006-01-02
+```
+
+##### Supported timestamp formats
+
+| Timestamp format | Description       | Example                          |
+|:---------------- |:-----------       |:-------                          |
+| **RFC3339**      | RFC3339 timestamp | `2020-01-01T00:00:00Z`           |
+| **RFC3339Nano**  | RFC3339 timestamp | `2020-01-01T00:00:00.000000000Z` |
+| **number**       | Unix timestamp    | `1577836800000000000`            |
+
+{{% note %}}
+If using the `number` timestamp format and timestamps are **not in nanoseconds**,
+use the [`influx write --precision` flag](/influxdb/v2.2/reference/cli/influx/write/#flags)
+to specify the [timestamp precision](/influxdb/v2.2/reference/glossary/#precision).
+{{% /note %}}
+
+##### Custom timestamp formats
+To specify a custom timestamp format, use timestamp formats as described in the
+[Go time package](https://golang.org/pkg/time).
+For example: `2020-01-02`.
+
+#### field
+Indicates the column is a **field**.
+The **column label** is the **field key**.
+The **column value** is the **field value**.
+
+{{% note %}}
+With the `field` datatype, field values are copies **as-is** to line protocol.
+For information about line protocol values and how they are written to InfluxDB,
+see [Line protocol data types and formats](/influxdb/v2.2/reference/syntax/line-protocol/#data-types-and-format).
+We generally recommend specifying the [field type](#field-types) in annotations.
+{{% /note %}}
+
+#### ignored
+The column is ignored and not written to InfluxDB.
+
+#### Field types
+The column is a **field** of a specified type.
+The **column label** is the **field key**.
+The **column value** is the **field value**.
+
+- [string](#string)
+- [double](#double)
+- [long](#long)
+- [unsignedLong](#unsignedlong)
+- [boolean](#boolean)
+
+##### string
+Column is a **[string](/influxdb/v2.2/reference/glossary/#string) field**.
+
+##### double
+Column is a **[float](/influxdb/v2.2/reference/glossary/#float) field**.
+By default, InfluxDB expects float values that use a period (`.`) to separate the
+fraction from the whole number.
+If column values include or use other separators, such as commas (`,`) to visually
+separate large numbers into groups, specify the following  **float separators**:
+
+- **fraction separator**: Separates the fraction from the whole number.
+- **ignored separator**: Visually separates the whole number into groups but ignores
+  the separator when parsing the float value.
+
+Use the following syntax to specify **float separators**:
+
+```sh
+# Syntax
+<fraction-separator><ignored-separator>
+
+# Example
+.,
+
+# With the float separators above
+# 1,200,000.15 => 1200000.15
+```
+
+Append **float separators** to the `double` datatype annotation with a colon (`:`).
+For example:
+
+```
+#datatype "double:.,"
+```
+
+{{% note %}}
+If your **float separators** include a comma (`,`), wrap the column annotation in double
+quotes (`""`) to prevent the comma from being parsed as a column separator or delimiter.
+You can also [define a custom column separator](#define-custom-column-separator).
+{{% /note %}}
+
+##### long
+Column is an **[integer](/influxdb/v2.2/reference/glossary/#integer) field**.
+If column values contain separators such as periods (`.`) or commas (`,`), specify
+the following **integer separators**:
+
+- **fraction separator**: Separates the fraction from the whole number.
+  _**Integer values are truncated at the fraction separator when converted to line protocol.**_
+- **ignored separator**: Visually separates the whole number into groups but ignores
+  the separator when parsing the integer value.
+
+Use the following syntax to specify **integer separators**:
+
+```sh
+# Syntax
+<fraction-separator><ignored-separator>
+
+# Example
+.,
+
+# With the integer separators above
+# 1,200,000.00 => 1200000i
+```
+
+Append **integer separators** to the `long` datatype annotation with a colon (`:`).
+For example:
+
+```
+#datatype "long:.,"
+```
+
+{{% note %}}
+If your **integer separators** include a comma (`,`), wrap the column annotation in double
+quotes (`""`) to prevent the comma from being parsed as a column separator or delimiter.
+You can also [define a custom column separator](#define-custom-column-separator).
+{{% /note %}}
+
+##### unsignedLong
+Column is an **[unsigned integer (uinteger)](/influxdb/v2.2/reference/glossary/#unsigned-integer) field**.
+If column values contain separators such as periods (`.`) or commas (`,`), specify
+the following **uinteger separators**:
+
+- **fraction separator**: Separates the fraction from the whole number.
+  _**Uinteger values are truncated at the fraction separator when converted to line protocol.**_
+- **ignored separator**: Visually separates the whole number into groups but ignores
+  the separator when parsing the uinteger value.
+
+Use the following syntax to specify **uinteger separators**:
+
+```sh
+# Syntax
+<fraction-separator><ignored-separator>
+
+# Example
+.,
+
+# With the uinteger separators above
+# 1,200,000.00 => 1200000u
+```
+
+Append **uinteger separators** to the `long` datatype annotation with a colon (`:`).
+For example:
+
+```
+#datatype "usignedLong:.,"
+```
+
+{{% note %}}
+If your **uinteger separators** include a comma (`,`), wrap the column annotation in double
+quotes (`""`) to prevent the comma from being parsed as a column separator or delimiter.
+You can also [define a custom column separator](#define-custom-column-separator).
+{{% /note %}}
+
+##### boolean
+Column is a **[boolean](/influxdb/v2.2/reference/glossary/#boolean) field**.
+If column values are not [supported boolean values](/influxdb/v2.2/reference/syntax/line-protocol/#boolean),
+specify the **boolean format** with the following syntax:
+
+```sh
+# Syntax
+<true-values>:<false-values>
+
+# Example
+y,Y,1:n,N,0
+
+# With the boolean format above
+# y => true, Y => true, 1 => true
+# n => false, N => false, 0 => false
+```
+
+Append the **boolean format** to the `boolean` datatype annotation with a colon (`:`).
+For example:
+
+```
+#datatype "boolean:y,Y:n,N"
+```
+
+{{% note %}}
+If your **boolean format** contains commas (`,`), wrap the column annotation in double
+quotes (`""`) to prevent the comma from being parsed as a column separator or delimiter.
+You can also [define a custom column separator](#define-custom-column-separator).
+{{% /note %}}
+
+### constant
+Use the `#constant` annotation to define a constant column label and value for each row.
+The `#constant` annotation provides a way to supply
+[line protocol elements](/influxdb/v2.2/reference/syntax/line-protocol/#elements-of-line-protocol)
+that don't exist in the CSV data.
+
+Use the following syntax to define constants:
+
+```
+#constant <datatype>,<column-label>,<column-value>
+```
+
+To provide multiple constants, include each `#constant` annotations on a separate line.
+
+```
+#constant measurement,m
+#constant tag,dataSource,csv
+```
+
+{{% note %}}
+For constants with `measurement` and `dateTime` datatypes, the second value in
+the constant definition is the **column-value**.
+{{% /note %}}
+
+### timezone
+Use the `#timezone` annotation to update timestamps to a specific timezone.
+By default, timestamps are parsed as UTC.
+Use the `±HHmm` format to specify the timezone offset relative to UTC.
+
+### strict mode
+Use the `:strict` keyword to indicate a loss of precision when parsing `long` or `unsignedLong` data types.
+Turn on strict mode by using a column data type that ends with `strict`, such as `long:strict`.
+When parsing `long` or `unsignedLong` value from a string value with fraction digits, the whole CSV row fails when in a strict mode.
+A warning is printed when not in a strict mode, saying `line x: column y: '1.2' truncated to '1' to fit into long data type`.
+For more information on strict parsing, see the [package documentation](https://github.com/influxdata/influxdb/tree/master/pkg/csv2lp).
+
+##### Timezone examples
+| Timezone                        | Offset  |
+|:--------                        | ------: |
+| US Mountain Daylight Time       | `-0600` |
+| Central European Summer Time    | `+0200` |
+| Australia Eastern Standard Time | `+1000` |
+| Apia Daylight Time              | `+1400` |
+
+##### Timezone annotation example
+```
+#timezone -0600
+```
+
+### concat
+
+The `#concat` annotation adds a new column that is concatenated from existing columns according to bash-like string interpolation literal with variables referencing existing column labels.
+
+For example:
+
+```
+#concat,string,fullName,${firstName} ${lastName}
+```
+
+This is especially useful when constructing a timestamp from multiple columns.
+For example, the following annotation will combine the given CSV columns into a timestamp:
+
+```
+#concat,dateTime:2006-01-02,${Year}-${Month}-${Day}
+
+Year,Month,Day,Hour,Minute,Second,Tag,Value
+2020,05,22,00,00,00,test,0
+2020,05,22,00,05,00,test,1
+2020,05,22,00,10,00,test,2
+```
+
+## Define custom column separator
+If columns are delimited using a character other than a comma, use the `sep`
+keyword to define a custom separator **in the first line of your CSV file**.
+
+```
+sep=;
+```
+
+## Annotation shorthand
+Extended annotated CSV supports **annotation shorthand**.
+Include the column label, datatype, and _(optional)_ default value in each column
+header row using the following syntax:
+
+```
+<column-label>|<column-datatype>|<column-default-value>
+```
+
+##### Example annotation shorthand
+```
+m|measurement,location|tag|Hong Kong,temp|double,pm|long|0,time|dateTime:RFC3339
+weather,San Francisco,51.9,38,2020-01-01T00:00:00Z
+weather,New York,18.2,,2020-01-01T00:00:00Z
+weather,,53.6,171,2020-01-01T00:00:00Z
+```
+
+##### The shorthand explained
+- The `m` column represents the **measurement** and has no default value.
+- The `location` column is a **tag** with the default value, `Hong Kong`.
+- The `temp` column is a **field** with **float** (`double`) values and no default value.
+- The `pm` column is a **field** with **integer** (`long`) values and a default of `0`.
+- The `time` column represents the **timestamp**, uses the **RFC3339** timestamp format,
+  and has no default value.
+
+##### Resulting line protocol
+```
+weather,location=San\ Francisco temp=51.9,pm=38i 1577836800000000000
+weather,location=New\ York temp=18.2,pm=0i 1577836800000000000
+weather,location=Hong\ Kong temp=53.6,pm=171i 1577836800000000000
+```
diff --git a/content/influxdb/v2.2/reference/syntax/delete-predicate.md b/content/influxdb/v2.2/reference/syntax/delete-predicate.md
new file mode 100644
index 000000000..275c61acd
--- /dev/null
+++ b/content/influxdb/v2.2/reference/syntax/delete-predicate.md
@@ -0,0 +1,92 @@
+---
+title: Delete predicate syntax
+list_title: Delete predicate
+description: >
+  InfluxDB uses an InfluxQL-like predicate syntax to determine what data points to delete.
+menu:
+  influxdb_2_2_ref:
+    parent: Syntax
+    name: Delete predicate
+weight: 104
+influxdb/v2.2/tags: [syntax, delete]
+related:
+  - /influxdb/v2.2/write-data/delete-data/
+  - /influxdb/v2.2/reference/cli/influx/delete/
+---
+
+InfluxDB uses an InfluxQL-like predicate syntax to determine what data
+[points](/influxdb/v2.2/reference/glossary/#point) to delete.
+InfluxDB uses the delete predicate to evaluate the [series keys](/influxdb/v2.2/reference/glossary/#series-key)
+of points in the time range specified in the delete request.
+Points with series keys that evaluate to `true` for the given predicate are deleted.
+Points with series keys that evaluate to `false` are preserved.
+
+A delete predicate is comprised of one or more [predicate expressions](/influxdb/v2.2/reference/glossary/#predicate-expression).
+The left operand of the predicate expression is the column name.
+The right operand is the column value.
+Operands are compared using [comparison operators](#comparison-operators).
+Use [logical operators](#logical-operators) to combine two or more predicate expressions.
+
+##### Example delete predicate
+```sql
+key1="value1" AND key2="value"
+```
+{{% warn %}}
+With **InfluxDB {{< current-version >}}**, delete predicates can use any column
+or tag **except** `_time`{{% oss-only %}}, `_field`, {{% /oss-only %}}or `_value`.
+{{% /warn %}}
+
+## Logical operators
+Logical operators join two or more predicate expressions.
+
+| Operator | Description                                                                  |
+|:-------- |:-----------                                                                  |
+| `AND`    | Both left and right operands must be `true` for the expression to be `true`. |
+
+## Comparison operators
+Comparison operators compare left and right operands and return `true` or `false`.
+
+| Operator | Description  | Example        | Result |
+|:-------- |:-----------  |:-------:       |:------:|
+| `=`      | Equal to     | `"abc"="abc"`  | `true` |
+
+## Delete predicate examples
+
+- [Delete points by measurement](#delete-points-by-measurement)
+- {{% cloud-only %}}[Delete points by field](#delete-points-by-field){{% /cloud-only %}}
+- [Delete points by tag set](#delete-points-by-tag-set)
+
+### Delete points by measurement
+The following will delete points in the `sensorData` measurement:
+
+```sql
+_measurement="sensorData"
+```
+
+{{% cloud-only %}}
+
+### Delete points by field
+The following will delete points with the `temperature` field:
+
+```sql
+_field="temperature"
+```
+
+{{% /cloud-only %}}
+
+### Delete points by tag set
+The following will delete points from the `prod-1.4` host in the `us-west` region:
+
+```sql
+host="prod-1.4" AND region="us-west"
+```
+
+## Limitations
+The delete predicate syntax has the following limitations.
+
+- Delete predicates do not support regular expressions.
+- Delete predicates do not support the `OR` logical operator.
+- Delete predicates only support equality (`=`), not inequality (`!=`).
+- Delete predicates can use any column or tag **except** `_time`
+  {{% oss-only %}}, `_field`, {{% /oss-only %}}or `_value`.
+  
\ No newline at end of file
diff --git a/content/influxdb/v2.2/reference/syntax/flux/_index.md b/content/influxdb/v2.2/reference/syntax/flux/_index.md
new file mode 100644
index 000000000..b0b6c0695
--- /dev/null
+++ b/content/influxdb/v2.2/reference/syntax/flux/_index.md
@@ -0,0 +1,29 @@
+---
+title: Flux syntax
+list_title: Flux
+description: >
+  Flux is a functional data scripting language designed for querying, analyzing, and acting on data.
+menu:
+  influxdb_2_2_ref:
+    parent: Syntax
+    name: Flux
+    identifier: flux-syntax
+weight: 101
+influxdb/v2.2/tags: [syntax, flux]
+---
+
+Flux is a functional data scripting language designed for querying, analyzing, and acting on data.
+
+## Flux documentation
+View the [Flux documentation](/{{< latest "flux" >}}/) for more information about
+the Flux syntax.
+
+- [Get started with Flux](/{{< latest "flux" >}}/get-started/)
+- [Flux standard library](/{{< latest "flux" >}}/stdlib/)
+- [Flux language specification](/{{< latest "flux" >}}/spec/)
+
+---
+
+**The following provide information about Flux and InfluxDB:**
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/reference/syntax/flux/flux-vs-influxql.md b/content/influxdb/v2.2/reference/syntax/flux/flux-vs-influxql.md
new file mode 100644
index 000000000..6c930d0bf
--- /dev/null
+++ b/content/influxdb/v2.2/reference/syntax/flux/flux-vs-influxql.md
@@ -0,0 +1,356 @@
+---
+title: Flux vs InfluxQL
+description: >
+  Flux is an alternative to InfluxQL and other SQL-like query languages for querying and analyzing data.
+  Learn about what's possible with Flux and how Flux compares to InfluxQL.
+aliases:
+  - /influxdb/v2.2/reference/flux/flux-vs-influxql/
+menu:
+  influxdb_2_2_ref:
+    name: Flux vs InfluxQL
+    parent: flux-syntax
+    weight: 105
+---
+
+Flux is an alternative to [InfluxQL](/influxdb/v2.2/query-data/influxql/)
+and other SQL-like query languages for querying and analyzing data.
+Flux uses functional language patterns that overcome many InfluxQL limitations.
+Check out the following distinctions between Flux and InfluxQL:
+
+- [Tasks possible with Flux](#tasks-possible-with-flux)
+- [InfluxQL and Flux parity](#influxql-and-flux-parity)
+
+## Tasks possible with Flux
+
+- [Joins](#joins)
+- [Math across measurements](#math-across-measurements)
+- [Sort by tags](#sort-by-tags)
+- [Group by any column](#group-by-any-column)
+- [Window by calendar months and years](#window-by-calendar-months-and-years)
+- [Work with multiple data sources](#work-with-multiple-data-sources)
+- [DatePart-like queries](#datepart-like-queries)
+- [Pivot](#pivot)
+- [Histograms](#histograms)
+- [Covariance](#covariance)
+- [Cast booleans to integers](#cast-booleans-to-integers)
+- [String manipulation and data shaping](#string-manipulation-and-data-shaping)
+- [Work with geo-temporal data](#work-with-geo-temporal-data)
+
+### Joins
+InfluxQL has never supported joins. Although you can use a join in a [TICKscript](/{{< latest "kapacitor" >}}/tick/introduction/),
+TICKscript's join capabilities are limited.
+Flux's [`join()` function](/{{< latest "flux" >}}/stdlib/universe/join/) lets you
+join data **from any bucket, any measurement, and on any columns** as long as
+each data set includes the columns to join on.
+
+```js
+dataStream1 = from(bucket: "example-bucket1")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "network" and r._field == "bytes-transferred")
+
+dataStream2 = from(bucket: "example-bucket2")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "httpd" and r._field == "requests-per-sec")
+
+join(tables: {d1: dataStream1, d2: dataStream2}, on: ["_time", "_stop", "_start", "host"])
+```
+
+_For an in-depth walkthrough of using the `join()` function, see [how to join data with Flux](/influxdb/v2.2/query-data/flux/join/)._
+
+### Math across measurements
+Being able to perform joins across measurements lets you calculate
+data from separate measurements.
+The example below takes data from two measurements, `mem` and `processes`,
+joins them, and then calculates the average amount of memory used per running process:
+
+```js
+// Memory used (in bytes)
+memUsed = from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used")
+
+// Total processes running
+procTotal = from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "processes" and r._field == "total")
+
+// Join memory used with total processes to calculate
+// the average memory (in MB) used for running processes.
+join(tables: {mem: memUsed, proc: procTotal}, on: ["_time", "_stop", "_start", "host"])
+    |> map(fn: (r) => ({_time: r._time, _value: r._value_mem / r._value_proc / 1000000}))
+```
+
+### Sort by tags
+InfluxQL's sorting capabilities only let you control the
+sort order of `time` using the `ORDER BY time` clause.
+The Flux [`sort()` function](/{{< latest "flux" >}}/stdlib/universe/sort)
+sorts records based on a list of columns.
+Depending on the column type, Flux sorts records lexicographically, numerically, or chronologically.
+
+```js
+from(bucket: "example-bucket")
+    |> range(start: -12h)
+    |> filter(fn: (r) => r._measurement == "system" and r._field == "uptime")
+    |> sort(columns: ["region", "host", "_value"])
+```
+
+### Group by any column
+InfluxQL lets you group by tags or time intervals only.
+Flux lets you group data by any column, including `_value`.
+Use the Flux [`group()` function](/{{< latest "flux" >}}/stdlib/universe/group/)
+to define which columns to group data by.
+
+```js
+from(bucket:"example-bucket")
+    |> range(start: -12h)
+    |> filter(fn: (r) => r._measurement == "system" and r._field == "uptime" )
+    |> group(columns:["host", "_value"])
+```
+
+### Window by calendar months and years
+InfluxQL does not support windowing data by calendar months and years due to their varied lengths.
+Flux supports calendar month and year duration units (`1mo`, `1y`) and lets you
+window and aggregate data by calendar month and year.
+
+```js
+from(bucket:"example-bucket")
+    |> range(start:-1y)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent" )
+    |> aggregateWindow(every: 1mo, fn: mean)
+```
+
+### Work with multiple data sources
+InfluxQL can only query data stored in InfluxDB.
+Flux can query data from other data sources such as CSV, PostgreSQL, MySQL, Google BigTable, and more.
+Join that data with data in InfluxDB to enrich query results.
+
+- [Flux CSV package](/{{< latest "flux" >}}/stdlib/csv/)
+- [Flux SQL package](/{{< latest "flux" >}}/stdlib/sql/)
+- [Flux BigTable package](/{{< latest "flux" >}}/stdlib/experimental/bigtable/)
+
+<!-- -->
+```js
+import "csv"
+import "sql"
+
+csvData = csv.from(csv: rawCSV)
+
+sqlData = sql.from(
+    driverName: "postgres",
+    dataSourceName: "postgresql://user:password@localhost",
+    query: "SELECT * FROM example_table",
+)
+
+data = from(bucket: "example-bucket")
+    |> range(start: -24h)
+    |> filter(fn: (r) => r._measurement == "sensor")
+
+auxData = join(tables: {csv: csvData, sql: sqlData}, on: ["sensor_id"])
+enrichedData = join(tables: {data: data, aux: auxData}, on: ["sensor_id"])
+
+enrichedData
+    |> yield(name: "enriched_data")
+```
+
+_For an in-depth walkthrough of querying SQL data, see [Query SQL data sources](/influxdb/v2.2/query-data/flux/sql/)._
+
+### DatePart-like queries
+InfluxQL doesn't support DatePart-like queries that only return results during specified hours of the day.
+The Flux [`hourSelection` function](/{{< latest "flux" >}}/stdlib/universe/hourselection/)
+returns only data with time values in a specified hour range.
+
+```js
+from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "cpu" and r.cpu == "cpu-total")
+    |> hourSelection(start: 9, stop: 17)
+```
+
+### Pivot
+Pivoting data tables isn't supported in InfluxQL.
+Use the Flux [`pivot()` function](/{{< latest "flux" >}}/stdlib/universe/pivot)
+to pivot data tables by `rowKey`, `columnKey`, and `valueColumn` parameters.
+
+```js
+from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "cpu" and r.cpu == "cpu-total")
+    |> pivot(rowKey: ["_time"], columnKey: ["_field"], valueColumn: "_value")
+```
+
+### Histograms
+Generating histograms isn't supported in InfluxQL.
+Use the Flux [`histogram()` function](/{{< latest "flux" >}}/stdlib/universe/histogram) to
+generate a cumulative histogram.
+
+```js
+from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+    |> histogram(buckets: [10, 20, 30, 40, 50, 60, 70, 80, 90, 100])
+```
+
+_For more examples, see [how to create histograms with Flux](/influxdb/v2.2/query-data/flux/histograms/)._
+
+### Covariance
+Flux provides functions for simple covariance calculations.
+Use the [`covariance()` function](/{{< latest "flux" >}}/stdlib/universe/covariance)
+to calculate the covariance between two columns and the [`cov()` function](/{{< latest "flux" >}}/stdlib/universe/cov)
+to calculate the covariance between two data streams.
+
+###### Covariance between two columns
+```js
+from(bucket: "example-bucket")
+    |> range(start:-5m)
+    |> covariance(columns: ["x", "y"])
+```
+
+###### Covariance between two streams of data
+```js
+table1 = from(bucket: "example-bucket")
+    |> range(start: -15m)
+    |> filter(fn: (r) => r._measurement == "measurement_1")
+
+table2 = from(bucket: "example-bucket")
+    |> range(start: -15m)
+    |> filter(fn: (r) => r._measurement == "measurement_2")
+
+cov(x: table1, y: table2, on: ["_time", "_field"])
+```
+
+### Cast booleans to integers
+InfluxQL supports type casting for numeric data types (floats to integers and vice versa) only.
+Use [Flux type conversion functions](/{{< latest "flux" >}}/function-types/#type-conversions)
+to perform many more type conversions, including casting boolean values to integers.
+
+##### Cast boolean field values to integers
+```js
+from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "m" and r._field == "bool_field")
+    |> toInt()
+```
+
+### String manipulation and data shaping
+InfluxQL doesn't support string manipulation when querying data.
+Use [Flux Strings package](/{{< latest "flux" >}}/stdlib/strings/) functions to operate on string data.
+Combine functions in this package with the [`map()` function](/{{< latest "flux" >}}/stdlib/universe/map/) to perform operations like sanitizing and normalizing strings.
+
+```js
+import "strings"
+
+from(bucket: "example-bucket")
+    |> range(start: -1h)
+    |> filter(fn: (r) => r._measurement == "weather" and r._field == "temp")
+    |> map(
+        fn: (r) => ({
+            r with
+            location: strings.toTitle(v: r.location),
+            sensor: strings.replaceAll(v: r.sensor, t: " ", u: "-"),
+            status: strings.substring(v: r.status, start: 0, end: 8)
+        })
+    )
+```
+
+### Work with geo-temporal data
+InfluxQL doesn't support working with geo-temporal data.
+The [Flux Geo package](/{{< latest "flux" >}}/stdlib/experimental/geo/) is a collection of functions that
+let you shape, filter, and group geo-temporal data.
+
+```js
+import "experimental/geo"
+
+from(bucket: "geo/autogen")
+    |> range(start: -1w)
+    |> filter(fn: (r) => r._measurement == "taxi")
+    |> geo.shapeData(latField: "latitude", lonField: "longitude", level: 20)
+    |> geo.filterRows(region: {lat: 40.69335938, lon: -73.30078125, radius: 20.0}, strict: true)
+    |> geo.asTracks(groupBy: ["fare-id"])
+```
+
+
+## InfluxQL and Flux parity
+We're continuing to add functions to complete parity between Flux and InfluxQL.
+The table below shows InfluxQL statements, clauses, and functions along with their equivalent Flux functions.
+
+_For a complete list of Flux functions, [view all Flux functions](/{{< latest "flux" >}}/stdlib/all-functions/)._
+
+| InfluxQL                                                                                                                                          | Flux Functions                                                                                                                                                                                           |
+| :------------------------------------------------------------------------------------------------------------------------------------------------ | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [SELECT](/{{< latest "influxdb" "v1" >}}/query_language/explore-data/#the-basic-select-statement)                                                 | [filter()](/{{< latest "flux" >}}/stdlib/universe/filter/)                                                                                                                                               |
+| [WHERE](/{{< latest "influxdb" "v1" >}}/query_language/explore-data/#the-where-clause)                                                            | [filter()](/{{< latest "flux" >}}/stdlib/universe/filter/), [range()](/{{< latest "flux" >}}/stdlib/universe/range/)                                                                                     |
+| [GROUP BY](/{{< latest "influxdb" "v1" >}}/query_language/explore-data/#the-group-by-clause)                                                      | [group()](/{{< latest "flux" >}}/stdlib/universe/group/)                                                                                                                                                 |
+| [INTO](/{{< latest "influxdb" "v1" >}}/query_language/explore-data/#the-into-clause)                                                              | [to()](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/to/)                                                                                                                                            |
+| [ORDER BY](/{{< latest "influxdb" "v1" >}}/query_language/explore-data/#order-by-time-desc)                                                       | [sort()](/{{< latest "flux" >}}/stdlib/universe/sort/)                                                                                                                                                   |
+| [LIMIT](/{{< latest "influxdb" "v1" >}}/query_language/explore-data/#the-limit-clause)                                                            | [limit()](/{{< latest "flux" >}}/stdlib/universe/limit/)                                                                                                                                                 |
+| [SLIMIT](/{{< latest "influxdb" "v1" >}}/query_language/explore-data/#the-slimit-clause)                                                          | --                                                                                                                                                                                                       |
+| [OFFSET](/{{< latest "influxdb" "v1" >}}/query_language/explore-data/#the-offset-clause)                                                          | --                                                                                                                                                                                                       |
+| [SOFFSET](/{{< latest "influxdb" "v1" >}}/query_language/explore-data/#the-soffset-clause)                                                        | --                                                                                                                                                                                                       |
+| [SHOW DATABASES](/{{< latest "influxdb" "v1" >}}/query_language/explore-schema/#show-databases)                                                   | [buckets()](/{{< latest "flux" >}}/stdlib/universe/buckets/)                                                                                                                                             |
+| [SHOW MEASUREMENTS](/{{< latest "influxdb" "v1" >}}/query_language/explore-schema/#show-measurements)                                             | [schema.measurements](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/measurements)                                                                                                             |
+| [SHOW FIELD KEYS](/{{< latest "influxdb" "v1" >}}/query_language/explore-schema/#show-field-keys)                                                 | [keys()](/{{< latest "flux" >}}/stdlib/universe/keys/)                                                                                                                                                   |
+| [SHOW RETENTION POLICIES](/{{< latest "influxdb" "v1" >}}/query_language/explore-schema/#show-retention-policies)                                 | [buckets()](/{{< latest "flux" >}}/stdlib/universe/buckets/)                                                                                                                                             |
+| [SHOW TAG KEYS](/{{< latest "influxdb" "v1" >}}/query_language/explore-schema/#show-tag-keys)                                                     | [schema.tagKeys()](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/tagkeys), [schema.measurementTagKeys()](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/measurementtagkeys)         |
+| [SHOW TAG VALUES](/{{< latest "influxdb" "v1" >}}/query_language/explore-schema/#show-tag-values)                                                 | [schema.tagValues()](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/tagvalues), [schema.measurementTagValues()](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/measurementtagvalues) |
+| [SHOW SERIES](/{{< latest "influxdb" "v1" >}}/query_language/explore-schema/#show-series)                                                         | --                                                                                                                                                                                                       |
+| [CREATE DATABASE](/{{< latest "influxdb" "v1" >}}/query_language/manage-database/#create-database)                                                | <span style="opacity:.25;font-weight:500;">N/A</span>                                                                                                                                                    |
+| [DROP DATABASE](/{{< latest "influxdb" "v1" >}}/query_language/manage-database/#delete-a-database-with-drop-database)                             | <span style="opacity:.25;font-weight:500;">N/A</span>                                                                                                                                                    |
+| [DROP SERIES](/{{< latest "influxdb" "v1" >}}/query_language/manage-database/#drop-series-from-the-index-with-drop-serie)                         | <span style="opacity:.25;font-weight:500;">N/A</span>                                                                                                                                                    |
+| [DELETE](/{{< latest "influxdb" "v1" >}}/query_language/manage-database/#delete-series-with-delete)                                               | <span style="opacity:.25;font-weight:500;">N/A</span>                                                                                                                                                    |
+| [DROP MEASUREMENT](/{{< latest "influxdb" "v1" >}}/query_language/manage-database/#delete-measurements-with-drop-measurement)                     | <span style="opacity:.25;font-weight:500;">N/A</span>                                                                                                                                                    |
+| [DROP SHARD](/{{< latest "influxdb" "v1" >}}/query_language/manage-database/#delete-a-shard-with-drop-shard)                                      | <span style="opacity:.25;font-weight:500;">N/A</span>                                                                                                                                                    |
+| [CREATE RETENTION POLICY](/{{< latest "influxdb" "v1" >}}/query_language/manage-database/#create-retention-policies-with-create-retention-policy) | <span style="opacity:.25;font-weight:500;">N/A</span>                                                                                                                                                    |
+| [ALTER RETENTION POLICY](/{{< latest "influxdb" "v1" >}}/query_language/manage-database/#modify-retention-policies-with-alter-retention-policy)   | <span style="opacity:.25;font-weight:500;">N/A</span>                                                                                                                                                    |
+| [DROP RETENTION POLICY](/{{< latest "influxdb" "v1" >}}/query_language/manage-database/#delete-retention-policies-with-drop-retention-policy)     | <span style="opacity:.25;font-weight:500;">N/A</span>                                                                                                                                                    |
+| [COUNT](/{{< latest "influxdb" "v1" >}}/query_language/functions#count)                                                                           | [count()](/{{< latest "flux" >}}/stdlib/universe/count/)                                                                                                                                                 |
+| [DISTINCT](/{{< latest "influxdb" "v1" >}}/query_language/functions#distinct)                                                                     | [distinct()](/{{< latest "flux" >}}/stdlib/universe/distinct/)                                                                                                                                           |
+| [INTEGRAL](/{{< latest "influxdb" "v1" >}}/query_language/functions#integral)                                                                     | [integral()](/{{< latest "flux" >}}/stdlib/universe/integral/)                                                                                                                                           |
+| [MEAN](/{{< latest "influxdb" "v1" >}}/query_language/functions#mean)                                                                             | [mean()](/{{< latest "flux" >}}/stdlib/universe/mean/)                                                                                                                                                   |
+| [MEDIAN](/{{< latest "influxdb" "v1" >}}/query_language/functions#median)                                                                         | [median()](/{{< latest "flux" >}}/stdlib/universe/median/)                                                                                                                                               |
+| [MODE](/{{< latest "influxdb" "v1" >}}/query_language/functions#mode)                                                                             | [mode()](/{{< latest "flux" >}}/stdlib/universe/mode/)                                                                                                                                                   |
+| [SPREAD](/{{< latest "influxdb" "v1" >}}/query_language/functions#spread)                                                                         | [spread()](/{{< latest "flux" >}}/stdlib/universe/spread/)                                                                                                                                               |
+| [STDDEV](/{{< latest "influxdb" "v1" >}}/query_language/functions#stddev)                                                                         | [stddev()](/{{< latest "flux" >}}/stdlib/universe/stddev/)                                                                                                                                               |
+| [SUM](/{{< latest "influxdb" "v1" >}}/query_language/functions#sum)                                                                               | [sum()](/{{< latest "flux" >}}/stdlib/universe/sum/)                                                                                                                                                     |
+| [BOTTOM](/{{< latest "influxdb" "v1" >}}/query_language/functions#bottom)                                                                         | [bottom()](/{{< latest "flux" >}}/stdlib/universe/bottom/)                                                                                                                                               |
+| [FIRST](/{{< latest "influxdb" "v1" >}}/query_language/functions#first)                                                                           | [first()](/{{< latest "flux" >}}/stdlib/universe/first/)                                                                                                                                                 |
+| [LAST](/{{< latest "influxdb" "v1" >}}/query_language/functions#last)                                                                             | [last()](/{{< latest "flux" >}}/stdlib/universe/last/)                                                                                                                                                   |
+| [MAX](/{{< latest "influxdb" "v1" >}}/query_language/functions#max)                                                                               | [max()](/{{< latest "flux" >}}/stdlib/universe/max/)                                                                                                                                                     |
+| [MIN](/{{< latest "influxdb" "v1" >}}/query_language/functions#min)                                                                               | [min()](/{{< latest "flux" >}}/stdlib/universe/min/)                                                                                                                                                     |
+| [PERCENTILE](/{{< latest "influxdb" "v1" >}}/query_language/functions#percentile)                                                                 | [quantile()](/{{< latest "flux" >}}/stdlib/universe/quantile/)                                                                                                                                           |
+| [SAMPLE](/{{< latest "influxdb" "v1" >}}/query_language/functions#sample)                                                                         | [sample()](/{{< latest "flux" >}}/stdlib/universe/sample/)                                                                                                                                               |
+| [TOP](/{{< latest "influxdb" "v1" >}}/query_language/functions#top)                                                                               | [top()](/{{< latest "flux" >}}/stdlib/universe/top/)                                                                                                                                                     |
+| [ABS](/{{< latest "influxdb" "v1" >}}/query_language/functions#abs)                                                                               | [math.abs()](/{{< latest "flux" >}}/stdlib/math/abs/)                                                                                                                                                    |
+| [ACOS](/{{< latest "influxdb" "v1" >}}/query_language/functions#acos)                                                                             | [math.acos()](/{{< latest "flux" >}}/stdlib/math/acos/)                                                                                                                                                  |
+| [ASIN](/{{< latest "influxdb" "v1" >}}/query_language/functions#asin)                                                                             | [math.asin()](/{{< latest "flux" >}}/stdlib/math/asin/)                                                                                                                                                  |
+| [ATAN](/{{< latest "influxdb" "v1" >}}/query_language/functions#atan)                                                                             | [math.atan()](/{{< latest "flux" >}}/stdlib/math/atan/)                                                                                                                                                  |
+| [ATAN2](/{{< latest "influxdb" "v1" >}}/query_language/functions#atan2)                                                                           | [math.atan2()](/{{< latest "flux" >}}/stdlib/math/atan2/)                                                                                                                                                |
+| [CEIL](/{{< latest "influxdb" "v1" >}}/query_language/functions#ceil)                                                                             | [math.ceil()](/{{< latest "flux" >}}/stdlib/math/ceil/)                                                                                                                                                  |
+| [COS](/{{< latest "influxdb" "v1" >}}/query_language/functions#cos)                                                                               | [math.cos()](/{{< latest "flux" >}}/stdlib/math/cos/)                                                                                                                                                    |
+| [CUMULATIVE_SUM](/{{< latest "influxdb" "v1" >}}/query_language/functions#cumulative-sum)                                                         | [cumulativeSum()](/{{< latest "flux" >}}/stdlib/universe/cumulativesum/)                                                                                                                                 |
+| [DERIVATIVE](/{{< latest "influxdb" "v1" >}}/query_language/functions#derivative)                                                                 | [derivative()](/{{< latest "flux" >}}/stdlib/universe/derivative/)                                                                                                                                       |
+| [DIFFERENCE](/{{< latest "influxdb" "v1" >}}/query_language/functions#difference)                                                                 | [difference()](/{{< latest "flux" >}}/stdlib/universe/difference/)                                                                                                                                       |
+| [ELAPSED](/{{< latest "influxdb" "v1" >}}/query_language/functions#elapsed)                                                                       | [elapsed()](/{{< latest "flux" >}}/stdlib/universe/elapsed/)                                                                                                                                             |
+| [EXP](/{{< latest "influxdb" "v1" >}}/query_language/functions#exp)                                                                               | [math.exp()](/{{< latest "flux" >}}/stdlib/math/exp/)                                                                                                                                                    |
+| [FLOOR](/{{< latest "influxdb" "v1" >}}/query_language/functions#floor)                                                                           | [math.floor()](/{{< latest "flux" >}}/stdlib/math/floor/)                                                                                                                                                |
+| [HISTOGRAM](/{{< latest "influxdb" "v1" >}}/query_language/functions#histogram)                                                                   | [histogram()](/{{< latest "flux" >}}/stdlib/universe/histogram/)                                                                                                                                         |
+| [LN](/{{< latest "influxdb" "v1" >}}/query_language/functions#ln)                                                                                 | [math.log()](/{{< latest "flux" >}}/stdlib/math/log/)                                                                                                                                                    |
+| [LOG](/{{< latest "influxdb" "v1" >}}/query_language/functions#log)                                                                               | [math.logb()](/{{< latest "flux" >}}/stdlib/math/logb/)                                                                                                                                                  |
+| [LOG2](/{{< latest "influxdb" "v1" >}}/query_language/functions#log2)                                                                             | [math.log2()](/{{< latest "flux" >}}/stdlib/math/log2/)                                                                                                                                                  |
+| [LOG10](/{{< latest "influxdb" "v1" >}}/query_language/functions#logt10)                                                                          | [math.log10()](/{{< latest "flux" >}}/stdlib/math/log10/)                                                                                                                                                |
+| [MOVING_AVERAGE](/{{< latest "influxdb" "v1" >}}/query_language/functions#moving-average)                                                         | [movingAverage()](/{{< latest "flux" >}}/stdlib/universe/movingaverage/)                                                                                                                                 |
+| [NON_NEGATIVE_DERIVATIVE](/{{< latest "influxdb" "v1" >}}/query_language/functions#non-negative-derivative)                                       | [derivative(nonNegative:true)](/{{< latest "flux" >}}/stdlib/universe/derivative/)                                                                                                                       |
+| [NON_NEGATIVE_DIFFERENCE](/{{< latest "influxdb" "v1" >}}/query_language/functions#non-negative-difference)                                       | [difference(nonNegative:true)](/{{< latest "flux" >}}/stdlib/universe/derivative/)                                                                                                                       |
+| [POW](/{{< latest "influxdb" "v1" >}}/query_language/functions#pow)                                                                               | [math.pow()](/{{< latest "flux" >}}/stdlib/math/pow/)                                                                                                                                                    |
+| [ROUND](/{{< latest "influxdb" "v1" >}}/query_language/functions#round)                                                                           | [math.round()](/{{< latest "flux" >}}/stdlib/math/round/)                                                                                                                                                |
+| [SIN](/{{< latest "influxdb" "v1" >}}/query_language/functions#sin)                                                                               | [math.sin()](/{{< latest "flux" >}}/stdlib/math/sin/)                                                                                                                                                    |
+| [SQRT](/{{< latest "influxdb" "v1" >}}/query_language/functions#sqrt)                                                                             | [math.sqrt()](/{{< latest "flux" >}}/stdlib/math/sqrt/)                                                                                                                                                  |
+| [TAN](/{{< latest "influxdb" "v1" >}}/query_language/functions#tan)                                                                               | [math.tan()](/{{< latest "flux" >}}/stdlib/math/tan/)                                                                                                                                                    |
+| [HOLT_WINTERS](/{{< latest "influxdb" "v1" >}}/query_language/functions#holt-winters)                                                             | [holtWinters()](/{{< latest "flux" >}}/stdlib/universe/holtwinters/)                                                                                                                                     |
+| [CHANDE_MOMENTUM_OSCILLATOR](/{{< latest "influxdb" "v1" >}}/query_language/functions#chande-momentum-oscillator)                                 | [chandeMomentumOscillator()](/{{< latest "flux" >}}/stdlib/universe/chandemomentumoscillator/)                                                                                                           |
+| [EXPONENTIAL_MOVING_AVERAGE](/{{< latest "influxdb" "v1" >}}/query_language/functions#exponential-moving-average)                                 | [exponentialMovingAverage()](/{{< latest "flux" >}}/stdlib/universe/exponentialmovingaverage/)                                                                                                           |
+| [DOUBLE_EXPONENTIAL_MOVING_AVERAGE](/{{< latest "influxdb" "v1" >}}/query_language/functions#double-exponential-moving-average)                   | [doubleEMA()](/{{< latest "flux" >}}/stdlib/universe/doubleema/)                                                                                                                                         |
+| [KAUFMANS_EFFICIENCY_RATIO](/{{< latest "influxdb" "v1" >}}/query_language/functions#kaufmans-efficiency-ratio)                                   | [kaufmansER()](/{{< latest "flux" >}}/stdlib/universe/kaufmanser/)                                                                                                                                       |
+| [KAUFMANS_ADAPTIVE_MOVING_AVERAGE](/{{< latest "influxdb" "v1" >}}/query_language/functions#kaufmans-adaptive-moving-average)                     | [kaufmansAMA()](/{{< latest "flux" >}}/stdlib/universe/kaufmansama/)                                                                                                                                     |
+| [TRIPLE_EXPONENTIAL_MOVING_AVERAGE](/{{< latest "influxdb" "v1" >}}/query_language/functions#triple-exponential-moving-average)                   | [tripleEMA()](/{{< latest "flux" >}}/stdlib/universe/tripleema/)                                                                                                                                         |
+| [TRIPLE_EXPONENTIAL_DERIVATIVE](/{{< latest "influxdb" "v1" >}}/query_language/functions#triple-exponential-derivative)                           | [tripleExponentialDerivative()](/{{< latest "flux" >}}/stdlib/universe/tripleexponentialderivative/)                                                                                                     |
+| [RELATIVE_STRENGTH_INDEX](/{{< latest "influxdb" "v1" >}}/query_language/functions#relative-strength-index)                                       | [relativeStrengthIndex()](/{{< latest "flux" >}}/stdlib/universe/relativestrengthindex/)                                                                                                                 |
diff --git a/content/influxdb/v2.2/reference/syntax/line-protocol.md b/content/influxdb/v2.2/reference/syntax/line-protocol.md
new file mode 100644
index 000000000..5b65cde2f
--- /dev/null
+++ b/content/influxdb/v2.2/reference/syntax/line-protocol.md
@@ -0,0 +1,284 @@
+---
+title: Line protocol
+description: >
+  InfluxDB uses line protocol to write data points.
+  It is a text-based format that provides the measurement, tag set, field set, and timestamp of a data point.
+menu:
+  influxdb_2_2_ref:
+    parent: Syntax
+weight: 102
+influxdb/v2.2/tags: [write, line protocol, syntax]
+aliases:
+  - /influxdb/v2.2/reference/line-protocol
+  - /influxdb/v2.2/write_protocols/line_protocol_tutorial/
+  - /influxdb/v2.2/write_protocols/line_protocol_reference/
+related:
+  - /influxdb/v2.2/write-data/
+---
+
+InfluxDB uses line protocol to write data points.
+It is a text-based format that provides the measurement, tag set, field set, and timestamp of a data point.
+
+- [Elements of line protocol](#elements-of-line-protocol)
+- [Data types and format](#data-types-and-format)
+- [Quotes](#quotes)
+- [Special characters](#special-characters)
+- [Comments](#comments)
+- [Naming restrictions](#naming-restrictions)
+- [Duplicate points](#duplicate-points)
+
+```js
+// Syntax
+<measurement>[,<tag_key>=<tag_value>[,<tag_key>=<tag_value>]] <field_key>=<field_value>[,<field_key>=<field_value>] [<timestamp>]
+
+// Example
+myMeasurement,tag1=value1,tag2=value2 fieldKey="fieldValue" 1556813561098000000
+```
+
+Lines separated by the newline character `\n` represent a single point
+in InfluxDB. Line protocol is whitespace sensitive.
+
+{{% note %}}
+Line protocol does not support the newline character `\n` in tag or field values.
+{{% /note %}}
+
+## Elements of line protocol
+
+```
+measurementName,tagKey=tagValue fieldKey="fieldValue" 1465839830100400200
+--------------- --------------- --------------------- -------------------
+       |               |                  |                    |
+  Measurement       Tag set           Field set            Timestamp
+```
+
+### Measurement
+({{< req >}})
+The measurement name.
+InfluxDB accepts one measurement per point.
+_Measurement names are case-sensitive and subject to [naming restrictions](#naming-restrictions)._
+
+_**Data type:** [String](#string)_
+
+
+### Tag set
+_**Optional**_ –
+All tag key-value pairs for the point.
+Key-value relationships are denoted with the `=` operand.
+Multiple tag key-value pairs are comma-delimited.
+_Tag keys and tag values are case-sensitive.
+Tag keys are subject to [naming restrictions](#naming-restrictions)._
+
+_**Key data type:** [String](#string)_  
+_**Value data type:** [String](#string)_
+
+### Field set
+({{< req >}})
+All field key-value pairs for the point.
+Points must have at least one field.
+_Field keys and string values are case-sensitive.
+Field keys are subject to [naming restrictions](#naming-restrictions)._
+
+_**Key data type:** [String](#string)_  
+_**Value data type:** [Float](#float) | [Integer](#integer) | [UInteger](#uinteger) | [String](#string) | [Boolean](#boolean)_
+
+{{% note %}}
+_Always double quote string field values. More on quotes [below](#quotes)._
+
+```sh
+measurementName fieldKey="field string value" 1556813561098000000
+```
+{{% /note %}}
+
+### Timestamp
+_**Optional**_ –
+The [unix timestamp](/influxdb/v2.2/reference/glossary/#unix-timestamp) for the data point.
+InfluxDB accepts one timestamp per point.
+If no timestamp is provided, InfluxDB uses the system time (UTC) of its host machine.
+
+_**Data type:** [Unix timestamp](#unix-timestamp)_
+
+{{% note %}}
+#### Important notes about timestamps
+- To ensure a data point includes the time a metric is observed (not received by InfluxDB),
+  include the timestamp.
+- If your timestamps are not in nanoseconds, specify the precision of your timestamps
+  when [writing the data to InfluxDB](/influxdb/v2.2/write-data/#timestamp-precision).
+{{% /note %}}
+
+### Whitespace
+Whitespace in line protocol determines how InfluxDB interprets the data point.
+The **first unescaped space** delimits the measurement and the tag set from the field set.
+The **second unescaped space** delimits the field set from the timestamp.
+
+```
+measurementName,tagKey=tagValue fieldKey="fieldValue" 1465839830100400200
+                               |                     |
+                           1st space             2nd space
+```
+
+## Data types and format
+
+### Float
+IEEE-754 64-bit floating-point numbers.
+Default numerical type.
+_InfluxDB supports scientific notation in float field values._
+
+##### Float field value examples
+```js
+myMeasurement fieldKey=1.0
+myMeasurement fieldKey=1
+myMeasurement fieldKey=-1.234456e+78
+```
+
+### Integer
+Signed 64-bit integers.
+Trailing `i` on the number specifies an integer.
+
+| Minimum integer         | Maximum integer        |
+| ---------------         | ---------------        |
+| `-9223372036854775808i` | `9223372036854775807i` |
+
+##### Integer field value examples
+```js
+myMeasurement fieldKey=1i
+myMeasurement fieldKey=12485903i
+myMeasurement fieldKey=-12485903i
+```
+
+### UInteger
+Unsigned 64-bit integers.
+Trailing `u` on the number specifies an unsigned integer.
+
+| Minimum uinteger | Maximum uinteger        |
+| ---------------- | ----------------        |
+| `0u`             | `18446744073709551615u` |
+
+##### UInteger field value examples
+```js
+myMeasurement fieldKey=1u
+myMeasurement fieldKey=12485903u
+```
+
+### String
+Plain text string.
+Length limit 64KB.
+
+##### String example
+```sh
+# String measurement name, field key, and field value
+myMeasurement fieldKey="this is a string"
+```
+
+### Boolean
+Stores `true` or `false` values.
+
+| Boolean value | Accepted syntax                     |
+|:-------------:|:---------------                     |
+| True          | `t`, `T`, `true`, `True`, `TRUE`    |
+| False         | `f`, `F`, `false`, `False`, `FALSE` |
+
+##### Boolean field value examples
+```js
+myMeasurement fieldKey=true
+myMeasurement fieldKey=false
+myMeasurement fieldKey=t
+myMeasurement fieldKey=f
+myMeasurement fieldKey=TRUE
+myMeasurement fieldKey=FALSE
+```
+
+{{% note %}}
+Do not quote boolean field values.
+Quoted field values are interpreted as strings.
+{{% /note %}}
+
+### Unix timestamp
+Unix timestamp in a [specified precision](/influxdb/v2.2/reference/glossary/#unix-timestamp).
+Default precision is nanoseconds (`ns`).
+
+| Minimum timestamp      | Maximum timestamp     |
+| -----------------      | -----------------     |
+| `-9223372036854775806` | `9223372036854775806` |
+
+##### Unix timestamp example
+```js
+myMeasurementName fieldKey="fieldValue" 1556813561098000000
+```
+
+## Quotes
+Line protocol supports single and double quotes as described in the following table:
+
+| Element     | Double quotes                           | Single quotes                           |
+| :------     | :------------:                          |:-------------:                          |
+| Measurement | _Limited_ <sup class="required">*</sup> | _Limited_ <sup class="required">*</sup> |
+| Tag key     | _Limited_ <sup class="required">*</sup> | _Limited_ <sup class="required">*</sup> |
+| Tag value   | _Limited_ <sup class="required">*</sup> | _Limited_ <sup class="required">*</sup> |
+| Field key   | _Limited_ <sup class="required">*</sup> | _Limited_ <sup class="required">*</sup> |
+| Field value | **Strings only**                        | Never                                   |
+| Timestamp   | Never                                   | Never                                   |
+
+<sup class="required">\*</sup> _Line protocol accepts double and single quotes in
+measurement names, tag keys, tag values, and field keys, but interprets them as
+part of the name, key, or value._
+
+## Special Characters
+Line protocol supports special characters in [string elements](#string).
+In the following contexts, it requires escaping certain characters with a backslash (`\`):
+
+| Element     | Escape characters         |
+|:-------     |:-----------------         |
+| Measurement | Comma, Space              |
+| Tag key     | Comma, Equals Sign, Space |
+| Tag value   | Comma, Equals Sign, Space |
+| Field key   | Comma, Equals Sign, Space |
+| Field value | Double quote, Backslash   |
+
+You do not need to escape other special characters.
+
+##### Examples of special characters in line protocol
+```sh
+# Measurement name with spaces
+my\ Measurement fieldKey="string value"
+
+# Double quotes in a string field value
+myMeasurement fieldKey="\"string\" within a string"
+
+# Tag keys and values with spaces
+myMeasurement,tag\ Key1=tag\ Value1,tag\ Key2=tag\ Value2 fieldKey=100
+
+# Emojis
+myMeasurement,tagKey=🍭 fieldKey="Launch 🚀" 1556813561098000000
+```
+
+### Escaping backslashes
+Line protocol supports both literal backslashes and backslashes as an escape character.
+With two contiguous backslashes, the first is interpreted as an escape character.
+For example:
+
+| Backslashes | Interpreted as |
+|:-----------:|:-------------:|
+| `\`         | `\`           |
+| `\\`        | `\`           |
+| `\\\`       | `\\`          |
+| `\\\\`      | `\\`          |
+| `\\\\\`     | `\\\`         |
+| `\\\\\\`    | `\\\`         |
+
+## Comments
+Line protocol interprets `#` at the beginning of a line as a comment character
+and ignores all subsequent characters until the next newline `\n`.
+
+```sh
+# This is a comment
+myMeasurement fieldKey="string value" 1556813561098000000
+```
+
+## Naming restrictions
+Measurement names, tag keys, and field keys cannot begin with an underscore `_`.
+The `_` namespace is reserved for InfluxDB system use.
+
+## Duplicate points
+A point is uniquely identified by the measurement name, tag set, and timestamp.
+If you submit line protocol with the same measurement, tag set, and timestamp,
+but with a different field set, the field set becomes the union of the old
+field set and the new field set, where any conflicts favor the new field set.
diff --git a/content/influxdb/v2.2/reference/telegraf-plugins.md b/content/influxdb/v2.2/reference/telegraf-plugins.md
new file mode 100644
index 000000000..f66a9b9c5
--- /dev/null
+++ b/content/influxdb/v2.2/reference/telegraf-plugins.md
@@ -0,0 +1,12 @@
+---
+title: Telegraf plugins
+description: >
+  Telegraf is a plugin-driven agent that collects, processes, aggregates, and writes metrics.
+  It supports four categories of plugins including input, output, aggregator, and processor.
+  View and search all available Telegraf plugins.
+---
+
+Telegraf is a plugin-driven agent that collects, processes, aggregates, and writes metrics.
+It supports four categories of plugins including input, output, aggregator, and processor.
+
+<a class="btn" href="/{{< latest "telegraf" >}}/plugins//">View Telegraf plugins</a>
diff --git a/content/influxdb/v2.2/reference/urls.md b/content/influxdb/v2.2/reference/urls.md
new file mode 100644
index 000000000..329cdcbbf
--- /dev/null
+++ b/content/influxdb/v2.2/reference/urls.md
@@ -0,0 +1,45 @@
+---
+title: InfluxDB OSS URLs
+description: >
+  InfluxDB OSS is accessed at `localhost:8086` by default, but you can also
+  customize your InfluxDB host and port.
+weight: 6
+menu:
+  influxdb_2_2_ref:
+    name: InfluxDB URLs
+---
+
+InfluxDB OSS is accessed at `localhost:8086` by default, but you can also
+customize your InfluxDB host and port.
+
+**Default host:** `localhost`  
+**Default port:** `8086`
+
+{{< keep-url >}}
+```
+http://localhost:8086/
+```
+
+## Customize your InfluxDB OSS URL
+To customize your InfluxDB host and port, use the
+[`http-bind-address` configuration option](/influxdb/v2.2/reference/config-options/#http-bind-address)
+when starting `influxd`.
+
+{{< keep-url >}}
+```sh
+# Syntax
+influxd --http-bind-address <custom-domain>:<custom-port>
+
+# Example - Run InfluxDB at http://example.com:8080
+influxd --http-bind-address example.com:8080
+
+# Example - Run InfluxDB at http://localhost:8080
+influxd --http-bind-address :8080
+```
+
+{{% note %}}
+#### Configure DNS routing
+You must configure DNS routing to successfully route requests to your custom hostname.
+Methods for configuring DNS routing vary depending on your operating system and
+network architecture and are not covered in this documentation.
+{{% /note %}}
diff --git a/content/influxdb/v2.2/security/_index.md b/content/influxdb/v2.2/security/_index.md
new file mode 100644
index 000000000..29502b09e
--- /dev/null
+++ b/content/influxdb/v2.2/security/_index.md
@@ -0,0 +1,25 @@
+---
+title: Manage security and authorization
+description: >
+  Security, access control, and sensitive secret handling are incredibly important
+  when handling any sort of sensitive data.
+  This section provides information about managing the security of your InfluxDB instance.
+weight: 12
+menu:
+  influxdb_2_2:
+    name: Security & authorization
+influxdb/v2.2/tags: [security, authentication]
+---
+
+Security, access control, and sensitive secret handling are incredibly important
+when handling any sort of sensitive data.
+This section provides information about managing the security of your InfluxDB instance.
+
+{{% note %}}
+#### InfluxDB 2.x/1.x compatibility
+If you [upgraded from 1.x to {{< current-version >}}](/influxdb/v2.2/upgrade/v1-to-v2/),
+use the [`influx v1 auth`](/influxdb/v2.2/reference/cli/influx/v1/auth/) commands
+to manage authorizations for the [1.x compatibility API](/influxdb/v2.2/reference/api/influxdb-1x/).
+{{% /note %}}
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/security/enable-hardening.md b/content/influxdb/v2.2/security/enable-hardening.md
new file mode 100644
index 000000000..84c974ec5
--- /dev/null
+++ b/content/influxdb/v2.2/security/enable-hardening.md
@@ -0,0 +1,47 @@
+---
+title: Enable security features
+seotitle: Enable security and hardening features in InfluxDB
+description: >
+  Enable a collection of additional security and hardening features in InfluxDB OSS to better
+  secure your InfluxDB instance.
+weight: 102
+menu:
+  influxdb_2_2:
+    parent: Security & authorization
+influxdb/v2.2/tags: [security, hardening]
+---
+
+InfluxDB {{< current-version >}} provides optional security features that ensure your
+InfluxDB instance is secure in whatever environment it's used in.
+
+To enable all [additional security features](#security-features), use the
+[`hardening-enabled` configuration option](/influxdb/v2.2/reference/config-options/#hardening-enabled)
+when starting InfluxDB.
+
+## Security features
+
+- [Private IP Validation](#private-ip-validation)
+
+### Private IP Validation
+
+Some Flux functions ([`to()`](/flux/v0.x/stdlib/influxdata/influxdb/to/),
+[`from()`](/flux/v0.x/stdlib/influxdata/influxdb/from/), [`http.post()`](/flux/v0.x/stdlib/http/post/), etc.)
+and [template fetching](/influxdb/v2.2/influxdb-templates/) can require InfluxDB to make
+HTTP requests over the network.
+With private IP validation enabled, InfluxDB first verifies that the IP address of the URL is not a private IP address.
+
+IP addresses are considered private if they fall into one of the following categories:
+
+- IPv4 loopback (`127.0.0.0/8`)
+- RFC1918 (`10.0.0.0/8`, `172.26.0.0/12`, `192.268.0.0/16`)
+- RFC3927 (`169.254.0.0/16`)
+- IPv6 loopback (`::1/128`)
+- IPv6 link-local (`fe80::/10`)
+- IPv6 unique local (`fc00::/7`)
+
+{{% note %}}
+#### Private IP considerations
+If your environment requires that these authenticated HTTP requests be made to private IP addresses,
+omit the use of `--hardening-enabled` and
+consider instead setting up egress firewalling to limit which hosts InfluxDB is allowed to connect.
+{{% /note %}}
diff --git a/content/influxdb/v2.2/security/enable-tls.md b/content/influxdb/v2.2/security/enable-tls.md
new file mode 100644
index 000000000..7201e34f0
--- /dev/null
+++ b/content/influxdb/v2.2/security/enable-tls.md
@@ -0,0 +1,154 @@
+---
+title: Enable TLS encryption
+seotitle: Enable TLS/SSL encryption
+description: >
+  Enable Transport Layer Security (TLS) and use the HTTPS protocol to secure communication between clients and InfluxDB.
+weight: 101
+menu:
+  influxdb_2_2:
+    parent: Security & authorization
+influxdb/v2.2/tags: [security, authentication, tls, https, ssl]
+products: [oss]
+---
+
+Enabling TLS encrypts the communication between clients and the InfluxDB server.
+When configured with a signed certificate, TLS also allows clients to verify the authenticity of the InfluxDB server.
+
+To set up TLS over HTTPS, do the following:
+
+- [Obtain requirements](#obtain-requirements)
+- [Configure InfluxDB to use TLS](#configure-influxdb-to-use-tls)
+
+{{% warn %}}
+InfluxData **strongly recommends** enabling HTTPS, especially if you plan on sending requests to InfluxDB over a network.
+{{% /warn %}}
+
+## Obtain requirements
+
+To enable HTTPS with InfluxDB, you need a Transport Layer Security (TLS) certificate, also known as a Secured Sockets Layer (SSL) certificate.
+InfluxDB supports three types of TLS certificates:
+
+* **Single domain certificates signed by a [Certificate Authority](https://en.wikipedia.org/wiki/Certificate_authority)**
+
+    Single domain certificates provide cryptographic security to HTTPS requests and allow clients to verify the identity of the InfluxDB server.
+    These certificates are signed and issued by a trusted, third-party Certificate Authority (CA).
+    With this certificate option, every InfluxDB instance requires a unique single domain certificate.
+
+* **Wildcard certificates signed by a Certificate Authority**
+
+    Wildcard certificates provide cryptographic security to HTTPS requests and allow clients to verify the identity of the InfluxDB server.
+    Wildcard certificates can be used across multiple InfluxDB instances on different servers.
+
+* **Self-signed certificates**
+
+    Self-signed certificates are _not_ signed by a trusted, third-party CA.
+    Unlike CA-signed certificates, self-signed certificates only provide cryptographic security to HTTPS requests.
+    They do not allow clients to verify the identity of the InfluxDB server.
+    With this certificate option, every InfluxDB instance requires a unique self-signed certificate.
+    You can generate a self-signed certificate on your own machine.
+
+<!-- InfluxDB supports certificates composed of a private key file (`.key`) and a signed certificate file (`.crt`) file pair, -->
+<!-- as well as certificates that combine the private key file and the signed certificate file into a single bundled file (`.pem`). -->
+
+## Configure InfluxDB to use TLS
+
+1. **Download or generate certificate files**
+
+    If using a certificate provided by a CA, follow their instructions to download the certificate files.
+
+    If using a self-signed certificate, use the `openssl` utility to create a certificate.
+
+    The following command generates a private key file (.key) and a self-signed certificate file (.crt) with required permissions
+    and saves them to `/etc/ssl/`.
+    (Other paths will also work.)
+    Files remain valid for the specified `NUMBER_OF_DAYS`.
+
+    ```sh
+    sudo openssl req -x509 -nodes -newkey rsa:2048 \
+      -keyout /etc/ssl/influxdb-selfsigned.key \
+      -out /etc/ssl/influxdb-selfsigned.crt \
+      -days <NUMBER_OF_DAYS>
+    ```
+
+    The command will prompt you for more information.
+    You can choose to fill out these fields or leave them blank; both actions generate valid certificate files.
+
+2. **Set certificate file permissions**
+
+    The user running InfluxDB must have read permissions on the TLS certificate.
+
+    {{% note %}}You may opt to set up multiple users, groups, and permissions.
+    Ultimately, make sure all users running InfluxDB have read permissions for the TLS certificate.
+    {{% /note %}}
+
+    Run the following command to give InfluxDB read and write permissions on the certificate files.
+
+    ```bash
+    sudo chmod 644 /etc/ssl/<CA-certificate-file>
+    sudo chmod 600 /etc/ssl/<private-key-file>
+    ```
+
+3. **Run `influxd` with TLS flags**
+
+    Start InfluxDB with TLS command line flags:
+
+    ```bash
+    influxd \
+    --tls-cert="<path-to-crt>" \
+    --tls-key="<path-to-key>"
+    ```
+
+4. **Verify TLS connection**
+
+
+    Ensure you can connect over HTTPS by running
+
+    ```
+    curl -v https://localhost:8086/api/v2/ping
+    ```
+
+    If using a self-signed certificate, use the `-k` flag to skip certificate verification:
+
+    ```
+    curl -vk https://localhost:8086/api/v2/ping
+    ```
+
+    With this command, you should see output confirming a succussful TLS handshake.
+
+You can further configure TLS settings using 
+[`tls-min-version`](/influxdb/v2.2/reference/config-options/#tls-min-version)
+and
+[`tls-strict-ciphers`](/influxdb/v2.2/reference/config-options/#tls-strict-ciphers).
+
+## Connect Telegraf to a secured InfluxDB instance
+
+To connect [Telegraf](/{{< latest "telegraf" >}}/) to an InfluxDB {{< current-version >}} instance with TLS enabled,
+update the following `influxdb_v2` output settings in your Telegraf configuration file:
+
+- Update URLs to use HTTPS instead of HTTP.
+- If using a self-signed certificate, uncomment and set `insecure_skip_verify` to `true`.
+
+### Example configuration
+
+```toml
+###############################################################################
+#                            OUTPUT PLUGINS                                   #
+###############################################################################
+
+# Configuration for sending metrics to InfluxDB
+[[outputs.influxdb_v2]]
+  ## The URLs of the InfluxDB cluster nodes.
+  ##
+  ## Multiple URLs can be specified for a single cluster, only ONE of the
+  ## urls will be written to each interval.
+  urls = ["https://127.0.0.1:8086"]
+
+  [...]
+
+  ## Optional TLS Config for use on HTTP connections.
+  [...]
+  ## Use TLS but skip chain & host verification
+  insecure_skip_verify = true
+```
+
+Restart Telegraf using the updated configuration file.
diff --git a/content/influxdb/v2.2/security/secrets/_index.md b/content/influxdb/v2.2/security/secrets/_index.md
new file mode 100644
index 000000000..477249f78
--- /dev/null
+++ b/content/influxdb/v2.2/security/secrets/_index.md
@@ -0,0 +1,24 @@
+---
+title: Manage secrets
+description: Manage, use, and store secrets in InfluxDB.
+influxdb/v2.2/tags: [secrets, security]
+menu:
+  influxdb_2_2:
+    parent: Security & authorization
+weight: 103
+aliases:
+  - /influxdb/v2.2/security/secrets/manage-secrets/
+---
+
+Secrets are key-value pairs that contain sensitive information you want to control
+access to, such as API keys, passwords, or certificates.
+There are two options for storing secrets with InfluxDB:
+
+- By default, secrets are Base64-encoded and stored in the InfluxDB embedded key value store,
+  [BoltDB](https://github.com/boltdb/bolt).
+- You can also set up a Vault server to store secrets.
+  For details, see [Store secrets in Vault](/influxdb/v2.2/security/secrets/use-vault).
+
+---
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/security/secrets/add.md b/content/influxdb/v2.2/security/secrets/add.md
new file mode 100644
index 000000000..df71508f5
--- /dev/null
+++ b/content/influxdb/v2.2/security/secrets/add.md
@@ -0,0 +1,58 @@
+---
+title: Add secrets
+description: Add secrets using the `influx` CLI or the InfluxDB API.
+influxdb/v2.2/tags: [secrets, security]
+menu:
+  influxdb_2_2:
+    parent: Manage secrets
+weight: 301
+aliases:
+  - /influxdb/v2.2/security/secrets/manage-secrets/add/
+---
+
+Add secrets using the `influx` command line interface (CLI) or the InfluxDB API.
+
+
+- [Add a secret using the influx CLI](#add-a-secret-using-the-influx-cli)
+- [Add a secret using the InfluxDB API](#add-a-secret-using-the-influxdb-api)
+
+## Add a secret using the influx CLI
+Use the [`influx secret update` command](/influxdb/v2.2/reference/cli/influx/secret/update/)
+to add a new secret to your organization.
+Provide the secret key with the `-k` or `--key` flag.
+You may also provide the secret value with the `-v` or `--value` flag.
+If you do not provide the secret value with the `-v` or `--value` flag,
+enter the value when prompted.
+
+{{% warn %}}
+Providing a secret value with the `-v` or `--value` flag may expose the secret
+in your command history.
+{{% /warn %}}
+
+```sh
+# Syntax
+influx secret update -k <secret-key>
+
+# Example
+influx secret update -k foo
+```
+
+## Add a secret using the InfluxDB API
+Use the `PATCH` request method and the `/orgs/{orgID}/secrets` API endpoint to
+add a new secret to your organization.
+
+**Include the following:**
+
+- Your [organization ID](/influxdb/v2.2/organizations/view-orgs/#view-your-organization-id) in the request URL
+- Your [API token](/influxdb/v2.2/security/tokens/view-tokens/) in the `Authorization` header
+- The secret key-value pair in the request body
+
+<!-- -->
+```sh
+curl --request PATCH http://localhost:8086/api/v2/orgs/<org-id>/secrets \
+  --header 'Authorization: Token YOURAUTHTOKEN' \
+  --header 'Content-type: application/json' \
+  --data '{
+	"<secret-key>": "<secret-value>"
+}'
+```
diff --git a/content/influxdb/v2.2/security/secrets/delete.md b/content/influxdb/v2.2/security/secrets/delete.md
new file mode 100644
index 000000000..9aace8e53
--- /dev/null
+++ b/content/influxdb/v2.2/security/secrets/delete.md
@@ -0,0 +1,50 @@
+---
+title: Delete secrets
+description: Delete secrets using the `influx` CLI or the InfluxDB API.
+influxdb/v2.2/tags: [secrets, security]
+menu:
+  influxdb_2_2:
+    parent: Manage secrets
+weight: 304
+aliases:
+  - /influxdb/v2.2/security/secrets/manage-secrets/delete/
+---
+
+Delete secrets using the `influx` command line interface (CLI) or the InfluxDB API.
+
+- [Delete a secret using the influx CLI](#delete-a-secret-using-the-influx-cli)
+- [Delete secrets using the InfluxDB API](#delete-secrets-using-the-influxdb-api)
+
+## Delete a secret using the influx CLI
+Use the [`influx secret delete` command](/influxdb/v2.2/reference/cli/influx/secret/delete/)
+to delete a secret key-value pair from your organization.
+Provide the secret key to delete with the `-k` or `--key` flag.
+
+```sh
+# Syntax
+influx secret delete -k <secret-key>
+
+# Example
+influx secret delete -k foo
+```
+
+## Delete secrets using the InfluxDB API
+Use the `POST` request method and the `orgs/{orgID}/secrets/delete` API endpoint
+to delete one or more secrets.
+
+**Include the following:**
+
+- Your [organization ID](/influxdb/v2.2/organizations/view-orgs/#view-your-organization-id) in the request URL
+- Your [API token](/influxdb/v2.2/security/tokens/view-tokens/) in the `Authorization` header
+- An array of secret keys to delete in the request body
+
+<!-- -->
+```bash
+curl --request GET http://localhost:8086/api/v2/orgs/<org-id>/secrets/delete \
+  --header 'Authorization: Token YOURAUTHTOKEN' \
+  --data '{
+  "secrets": [
+    "<secret-key>"
+  ]
+}'
+```
diff --git a/content/influxdb/v2.2/security/secrets/update.md b/content/influxdb/v2.2/security/secrets/update.md
new file mode 100644
index 000000000..b565e7949
--- /dev/null
+++ b/content/influxdb/v2.2/security/secrets/update.md
@@ -0,0 +1,57 @@
+---
+title: Update secrets
+description: Update secrets using the `influx` CLI or the InfluxDB API.
+influxdb/v2.2/tags: [secrets, security]
+menu:
+  influxdb_2_2:
+    parent: Manage secrets
+weight: 303
+aliases:
+  - /influxdb/v2.2/security/secrets/manage-secrets/update/
+---
+
+Update secrets using the `influx` command line interface (CLI) or the InfluxDB API.
+
+- [Update a secret using the influx CLI](#update-a-secret-using-the-influx-cli)
+- [Update a secret using the InfluxDB API](#update-a-secret-using-the-influxdb-api)
+
+## Update a secret using the influx CLI
+Use the [`influx secret update` command](/influxdb/v2.2/reference/cli/influx/secret/update/)
+to update a secret in your organization.
+Provide the secret key to update with the `-k` or `--key` flag.
+You may also provide the secret value with the `-v` or `--value` flag.
+If you do not provide the secret value with the `-v` or `--value` flag,
+enter the value when prompted.
+
+{{% warn %}}
+Providing a secret value with the `-v` or `--value` flag may expose the secret
+in your command history.
+{{% /warn %}}
+
+```sh
+# Syntax
+influx secret update -k <secret-key>
+
+# Example
+influx secret update -k foo
+```
+
+## Update a secret using the InfluxDB API
+Use the `PATCH` request method and the InfluxDB `/orgs/{orgID}/secrets` API endpoint
+to update a secret in your organization.
+
+**Include the following:**
+
+- Your [organization ID](/influxdb/v2.2/organizations/view-orgs/#view-your-organization-id) in the request URL
+- Your [API token](/influxdb/v2.2/security/tokens/view-tokens/) in the `Authorization` header
+- The updated secret key-value pair in the request body
+
+<!-- -->
+```sh
+curl --request PATCH http://localhost:8086/api/v2/orgs/<org-id>/secrets \
+  --header 'Authorization: Token YOURAUTHTOKEN' \
+  --header 'Content-type: application/json' \
+  --data '{
+	"<secret-key>": "<secret-value>"
+}'
+```
diff --git a/content/influxdb/v2.2/security/secrets/use-vault.md b/content/influxdb/v2.2/security/secrets/use-vault.md
new file mode 100644
index 000000000..8e8598d53
--- /dev/null
+++ b/content/influxdb/v2.2/security/secrets/use-vault.md
@@ -0,0 +1,98 @@
+---
+title: Store secrets in Vault
+description: Use Vault as an InfluxDB secret store and manage secrets through the in InfluxDB API.
+influxdb/v2.2/tags: [secrets, security]
+menu:
+  influxdb_2_2:
+    parent: Manage secrets
+weight: 306
+---
+
+[Vault](https://www.vaultproject.io/) secures, stores, and controls access
+to tokens, passwords, certificates, and other sensitive secrets.
+Store sensitive secrets in Vault using InfluxDB's built-in Vault integration.
+
+To store secrets in Vault, complete the following steps:
+ 
+1. [Start a Vault server](#start-a-vault-server).
+2. [Provide Vault server address and token](#provide-vault-server-address-and-token).
+3. [Start InfluxDB](#start-influxdb).
+4. [Manage secrets through the InfluxDB API](#manage-secrets-through-the-influxdb-api).
+
+## Start a Vault server
+
+Start a Vault server and ensure InfluxDB has network access to the server.
+
+The following links provide information about running Vault in both development and production:
+
+- [Install Vault](https://learn.hashicorp.com/vault/getting-started/install)
+- [Start a Vault dev server](https://learn.hashicorp.com/vault/getting-started/dev-server)
+- [Deploy Vault](https://learn.hashicorp.com/vault/getting-started/deploy)
+
+{{% note %}}
+InfluxDB supports the [Vault KV Secrets Engine Version 2 API](https://www.vaultproject.io/api/secret/kv/kv-v2.html) only.
+When you create a secrets engine, enable the `kv-v2` version by running:
+
+```js
+vault secrets enable kv-v2
+```
+{{% /note %}}
+
+For this example, install Vault on your local machine and start a Vault dev server.
+
+```sh
+vault server -dev
+```
+
+## Provide Vault server address and token
+
+Use `influxd` Vault-related tags or [Vault environment variables](https://www.vaultproject.io/docs/commands/index.html#environment-variables)
+to provide connection credentials and other important Vault-related information to InfluxDB.
+
+### Required credentials
+
+#### Vault address
+
+Provide the API address of your Vault server _(available in the Vault server output)_
+using the [`--vault-addr` flag](/influxdb/v2.2/reference/config-options/#vault-addr) when
+starting `influxd` or with the `VAULT_ADDR` environment variable.
+
+#### Vault token
+
+Provide your [Vault token](https://learn.hashicorp.com/vault/getting-started/authentication)
+(required to access your Vault server) using the [`--vault-token` flag](/influxdb/v2.2/reference/config-options/#vault-token)
+when starting `influxd` or with the `VAULT_TOKEN` environment variable.
+
+_Your Vault server configuration may require other Vault settings._
+
+## Start InfluxDB
+
+Start the [`influxd` service](/influxdb/v2.2/reference/cli/influxd/) with the `--secret-store`
+option set to `vault` any other necessary flags.
+
+```bash
+influxd --secret-store vault \
+  --vault-addr=http://127.0.0.1:8200 \
+  --vault-token=s.0X0XxXXx0xXxXXxxxXxXxX0x
+```
+
+`influxd` includes the following Vault configuration options.
+If set, these flags override any [Vault environment variables](https://www.vaultproject.io/docs/commands/index.html#environment-variables):
+
+- `--vault-addr`
+- `--vault-cacert`
+- `--vault-capath`
+- `--vault-client-cert`
+- `--vault-client-key`
+- `--vault-max-retries`
+- `--vault-client-timeout`
+- `--vault-skip-verify`
+- `--vault-tls-server-name`
+- `--vault-token`
+
+For more information, see [InfluxDB configuration options](/influxdb/v2.2/reference/config-options/).
+
+## Manage secrets through the InfluxDB API
+
+Use the InfluxDB `/org/{orgID}/secrets` API endpoint to add tokens to Vault.
+For details, see [Manage secrets](/influxdb/v2.2/security/secrets/manage-secrets/).
diff --git a/content/influxdb/v2.2/security/secrets/use.md b/content/influxdb/v2.2/security/secrets/use.md
new file mode 100644
index 000000000..f10f92dbd
--- /dev/null
+++ b/content/influxdb/v2.2/security/secrets/use.md
@@ -0,0 +1,29 @@
+---
+title: Use secrets
+description: Use secrets in a query with Flux.
+influxdb/v2.2/tags: [secrets, security]
+menu:
+  influxdb_2_2:
+    parent: Manage secrets
+weight: 305
+aliases:
+  - /influxdb/v2.2/security/secrets/manage-secrets/use/
+---
+
+## Use secrets in a query
+Import the `influxdata/influxd/secrets` package and use the `secrets.get()` function
+to populate sensitive data in queries with secrets from your secret store.
+
+```js
+import "influxdata/influxdb/secrets"
+import "sql"
+
+username = secrets.get(key: "POSTGRES_USERNAME")
+password = secrets.get(key: "POSTGRES_PASSWORD")
+
+sql.from(
+    driverName: "postgres",
+    dataSourceName: "postgresql://${username}:${password}@localhost",
+    query:"SELECT * FROM example-table",
+)
+```
diff --git a/content/influxdb/v2.2/security/secrets/view.md b/content/influxdb/v2.2/security/secrets/view.md
new file mode 100644
index 000000000..e6084aa73
--- /dev/null
+++ b/content/influxdb/v2.2/security/secrets/view.md
@@ -0,0 +1,39 @@
+---
+title: View secret keys
+description: View secret keys using the `influx` CLI or the InfluxDB API.
+influxdb/v2.2/tags: [secrets, security]
+menu:
+  influxdb_2_2:
+    parent: Manage secrets
+weight: 302
+aliases:
+  - /influxdb/v2.2/security/secrets/manage-secrets/view/
+---
+
+View secret keys using the `influx` command line interface (CLI) or the InfluxDB API.
+
+- [View secret keys using the influx CLI](#view-secret-keys-using-the-influx-cli)
+- [View secret keys using the InfluxDB API](#view-secret-keys-using-the-influxdb-api)
+
+## View secret keys using the influx CLI
+Use the [`influx secret list` command](/influxdb/v2.2/reference/cli/influx/secret/list/)
+to list your organization's secret keys.
+
+```sh
+influx secret list
+```
+
+## View secret keys using the InfluxDB API
+Use the `GET` request method and the InfluxDB `/orgs/{orgID}/secrets` API endpoint
+to view your organization's secrets keys.
+
+**Include the following:**
+
+- Your [organization ID](/influxdb/v2.2/organizations/view-orgs/#view-your-organization-id) in the request URL
+- Your [API token](/influxdb/v2.2/security/tokens/view-tokens/) in the `Authorization` header
+
+<!-- -->
+```sh
+curl --request GET http://localhost:8086/api/v2/orgs/<org-id>/secrets \
+  --header 'Authorization: Token YOURAUTHTOKEN'
+```
diff --git a/content/influxdb/v2.2/security/tokens/_index.md b/content/influxdb/v2.2/security/tokens/_index.md
new file mode 100644
index 000000000..d464ca421
--- /dev/null
+++ b/content/influxdb/v2.2/security/tokens/_index.md
@@ -0,0 +1,45 @@
+---
+title: Manage API tokens
+seotitle: Manage API tokens in InfluxDB
+description: Manage API tokens in InfluxDB using the InfluxDB UI or the influx CLI.
+aliases:
+  - /influxdb/v2.2/users/tokens
+influxdb/v2.2/tags: [tokens, authentication, security]
+menu:
+  influxdb_2_2:
+    name: Manage tokens
+    parent: Security & authorization
+weight: 104
+---
+
+InfluxDB **API tokens** ensure secure interaction between InfluxDB and external tools such as clients or applications.
+An API token belongs to a specific user and identifies InfluxDB permissions within the user's organization.
+
+Learn how to create, view, update, or delete an API token.
+
+## API token types
+
+- [Operator API token](#operator-token)
+- [All-Access API token](#all-access-token)
+- [Read/Write token](#readwrite-token)
+
+#### Operator token
+Grants full read and write access to **all organizations and all organization resources in InfluxDB OSS 2.x**.
+Some operations, e.g. [retrieving the server configuration](/influxdb/v2.2/reference/config-options/), require operator permissions.
+Operator tokens are created in the InfluxDB setup process.
+To [create an operator token manually](/influxdb/v2.2/security/tokens/create-token/), you must use an existing operator token.
+
+{{% note %}}
+Because Operator tokens have full read and write access to all organizations in the database,
+we recommend [creating an All-Access token](/influxdb/v2.2/security/tokens/create-token/)
+for each organization and using those to manage InfluxDB.
+This helps to prevent accidental interactions across organizations.
+{{% /note %}}
+
+#### All-Access token
+Grants full read and write access to all resources in an organization.
+
+#### Read/Write token
+Grants read access, write access, or both to specific buckets in an organization.
+
+{{< children hlevel="h2" >}}
diff --git a/content/influxdb/v2.2/security/tokens/create-token.md b/content/influxdb/v2.2/security/tokens/create-token.md
new file mode 100644
index 000000000..f6c85e7ef
--- /dev/null
+++ b/content/influxdb/v2.2/security/tokens/create-token.md
@@ -0,0 +1,193 @@
+---
+title: Create a token
+seotitle: Create an API token in InfluxDB
+description: Create an API token in InfluxDB using the InfluxDB UI, the `influx` CLI, or the InfluxDB API.
+aliases:
+  - /influxdb/v2.2/users/tokens/create-token/
+menu:
+  influxdb_2_2:
+    name: Create a token
+    parent: Manage tokens
+weight: 201
+---
+
+Create API tokens using the InfluxDB user interface (UI), the `influx`
+command line interface (CLI), or the InfluxDB API.
+
+{{% note %}}
+
+{{% oss-only %}}Tokens are visible to the user who created the token. Users who own a token with Operator permissions also have access to all tokens.
+Tokens stop working when the user who created the token is deleted.
+
+**We recommend creating a generic user to create and manage tokens for writing data.**
+{{% /oss-only %}}
+
+{{% cloud-only %}}
+
+To follow best practices for secure API token generation and retrieval, InfluxDB Cloud enforces access restrictions on API tokens.
+
+- Tokens are visible to the user who created the token.
+- InfluxDB Cloud UI only allows access to the API token value immediately after the token is created.
+- You can't change access (**read/write**) permissions for an API token after it's created.
+- Tokens stop working when the user who created the token is deleted.
+
+**We recommend the following for managing your tokens:**
+- Create a generic user to create and manage tokens for writing data.
+- Store your tokens in a secure password vault for future access.
+
+{{% /cloud-only %}}
+{{% /note %}}
+
+- [Manage tokens in the InfluxDB UI](#manage-tokens-in-the-influxdb-ui)
+- [Create a token in the InfluxDB UI](#create-a-token-in-the-influxdb-ui)
+- [Create a token using the influx CLI](#create-a-token-using-the-influx-cli)
+- [Create a token using the InfluxDB API](#create-a-token-using-the-influxdb-api)
+
+## Manage tokens in the InfluxDB UI
+
+To manage InfluxDB API Tokens in the InfluxDB UI, navigate to the **API Tokens** management page.
+
+{{% oss-only %}}
+
+In the navigation menu on the left, select **Data (Load Data)** > **Tokens**.
+
+{{% /oss-only %}}
+
+{{% cloud-only %}}
+
+In the navigation menu on the left, select **Load Data** > **API Tokens**.
+
+{{% /cloud-only %}}
+
+{{< nav-icon "load-data" >}}
+
+## Create a token in the InfluxDB UI
+
+{{% oss-only %}}
+
+1. From the [API Tokens management page](#manage-tokens-in-the-influxdb-ui),
+click **{{< icon "plus" >}} Generate** and select a token type
+   (**Read/Write Token** or **All Access API Token**).
+2. In the window that appears, enter a description for your token in the **Description** field.
+3. If generating a **read/write token**:
+    - Search for and select buckets to read from in the **Read** pane.
+    - Search for and select buckets to write to in the **Write** pane.
+4. Click **Save**.
+
+{{% /oss-only %}}
+
+
+{{% cloud-only %}}
+
+### Create an All-Access token
+
+1. From the [API Tokens management page](#manage-tokens-in-the-influxdb-ui),
+click the **{{< icon "plus" >}} {{< caps >}}Generate API Token{{< /caps >}}** button.
+2. Select **All Access API Token**.
+
+### Create a Custom token
+
+1. From the [API Tokens management page](#manage-tokens-in-the-influxdb-ui),
+click the **{{< icon "plus" >}} {{< caps >}}Generate API Token{{< /caps >}}** button.
+2. Select **Custom API Token**.
+3. When the **Generate a Personal API Token** window appears, enter a description. If you don't provide a description for the token, InfluxDB will generate a description from the permissions you assign.
+   For example, if you select **Read** for a bucket named "\_monitoring" and **Write** for a bucket named "\_tasks", InfluxDB will generate the description "Read buckets \_monitoring Write buckets \_tasks".
+4. Select checkboxes in the **Read** and **Write** columns to assign access permissions for the token. You can enable access to all buckets, individual buckets, Telegraf configurations, and other InfluxDB resources. By default, the new token has no access permissions.
+5. When you're finished, click **{{< caps >}}Generate{{< /caps >}}**.
+6. When InfluxDB displays the token value, click **{{< caps >}}Copy to Clipboard{{< /caps >}}**. This is your only chance to access and copy the token value from InfluxDB.
+7. (Optional) Store the API token value in a secure password vault.
+
+### Clone a token
+
+To create a token with the same authorizations as an existing token, clone the existing token.
+
+1. From the [API Tokens management page](#manage-tokens-in-the-influxdb-ui),
+find the token you want to clone and click the **{{< icon "settings" >}}** icon located far right of the token description.
+3. Select **Clone**.
+3. When InfluxDB UI displays the created token, click **{{< caps >}}Copy to Clipboard{{< /caps >}}**. This is your only chance to access and copy the token value from InfluxDB.
+4. (Optional) Store the API token value in a secure password vault.
+
+{{% /cloud-only %}}
+
+## Create a token using the influx CLI
+
+Use the [`influx auth create` command](/influxdb/v2.2/reference/cli/influx/auth/create) to create a token.
+Include flags with the command to grant specific permissions to the token.
+See the [available flags](/influxdb/v2.2/reference/cli/influx/auth/create#flags).
+Only tokens with the `write: authorizations` permission can create tokens.
+
+```sh
+# Syntax
+influx auth create -o <org-name> [permission-flags]
+```
+
+### Examples
+#### Create an All-Access token
+
+Create an All-Access token to grant permissions to all resources in an organization.
+
+```sh
+influx auth create \
+  --org my-org \
+  --all-access
+```
+
+{{% oss-only %}}
+
+#### Create an Operator token
+
+Create an Operator token to grant permissions to all resources in all organizations.
+
+```sh
+influx auth create \
+  --org my-org \
+  --operator
+```
+
+{{% /oss-only %}}
+
+#### Create a token with specified read permissions
+
+```sh
+influx auth create \
+  --org my-org \
+  --read-bucket 03a2bbf46309a000 \
+  --read-bucket 3a87c03ace269000 \
+  --read-dashboards \
+  --read-tasks \
+  --read-telegrafs \
+  --read-user
+```
+
+See the [`influx auth create` documentation](/{{< latest "influxdb" >}}/reference/cli/influx/auth/create) for information about other available flags.
+
+## Create a token using the InfluxDB API
+
+Use the `/api/v2/authorizations` InfluxDB API endpoint to create a token.
+
+[{{< api-endpoint method="POST" endpoint="http://localhost:8086/api/v2/authorizations" >}}]((/influxdb/v2.2/api/#operation/PostAuthorizations))
+
+Include the following in your request:
+
+| Requirement          | Include by                                               |
+|:-----------          |:----------                                               |
+| API token with the [`write: authorizations`](/influxdb/v2.2/api/#operation/PostAuthorizations) permission  | Use the `Authorization` header and the {{% oss-only %}}`Bearer` or {{% /oss-only %}}`Token` scheme. |
+| Organization         | Pass as `orgID` in the request body.
+| Permissions list     | Pass as a `permissions` array in the request body.
+
+```sh
+{{% get-shared-text "api/v2.0/auth/oss/token-create.sh" %}}
+```
+
+### Create a token scoped to a user
+
+To scope a token to a user other than the token creator, pass `userID` in the request
+body.
+
+```sh
+{{% get-shared-text "api/v2.0/auth/oss/tokens-create-with-user.sh" %}}
+```
+
+See the
+[`POST /api/v2/authorizations` documentation](/influxdb/v2.2/api/#operation/PostAuthorizations)
+for more information about options.
diff --git a/content/influxdb/v2.2/security/tokens/delete-token.md b/content/influxdb/v2.2/security/tokens/delete-token.md
new file mode 100644
index 000000000..836779027
--- /dev/null
+++ b/content/influxdb/v2.2/security/tokens/delete-token.md
@@ -0,0 +1,87 @@
+---
+title: Delete a token
+seotitle: Delete an API token from InfluxDB
+description: Delete an API token from InfluxDB using the InfluxDB UI or the `influx` CLI.
+aliases:
+  - /influxdb/v2.2/users/tokens/delete-token
+menu:
+  influxdb_2_2:
+    name: Delete a token
+    parent: Manage tokens
+weight: 204
+---
+
+Delete API tokens from the InfluxDB user interface (UI) or the `influx` command line interface (CLI).
+Once deleted, all users and external integrations using the API token will no longer
+have access to your InfluxDB instance.
+
+- [Delete tokens in the InfluxDB UI](#delete-tokens-in-the-influxdb-ui)
+- [Delete a token using the influx CLI](#delete-a-token-using-the-influx-cli)
+- [Delete a token using the InfluxDB API](#delete-a-token-using-the-influxdb-api)
+
+## Delete tokens in the InfluxDB UI
+
+{{% oss-only %}}
+
+1. In the navigation menu on the left, select **Data (Load Data)** > **Tokens**.
+
+    {{< nav-icon "load-data" >}}
+
+2. Hover over the token you want to delete.
+3. Click the **{{< icon "delete" >}}** icon located far right of the token description.
+3. Click **Delete** to delete the token.
+
+{{% /oss-only %}}
+
+{{% cloud-only %}}
+
+1. In the navigation menu on the left, select **Load Data** > **API Tokens**.
+
+    {{< nav-icon "data" >}}
+
+2. Find the token that you would like to delete.
+3. Click the **{{< icon "delete" >}}** icon located far right of the token description.
+4. Click **{{< caps >}}Confirm{{< /caps >}}** to delete the token.
+
+{{% /cloud-only %}}
+
+## Delete a token using the influx CLI
+
+Use the [`influx auth delete` command](/influxdb/v2.2/reference/cli/influx/auth/delete)
+to delete a token.
+
+_This command requires an auth ID, which is available in the output of `influx auth find`._
+
+```sh
+# Syntax
+influx auth delete -i <auth-id>
+
+# Example
+influx auth delete -i 03a2bee5a9c9a000
+```
+
+## Delete a token using the InfluxDB API
+
+Use the `/api/v2/authorizations` InfluxDB API endpoint to delete a token.
+
+[{{< api-endpoint method="DELETE" endpoint="http://localhost:8086/api/v2/authorizations/AUTH_ID" >}}](/influxdb/v2.2/api/#operation/DeleteAuthorizationsID)
+
+Include the following in your request:
+
+| Requirement          | Include by                                               |
+|:-----------          |:----------                                               |
+| API token with the [`write: authorizations`](/influxdb/v2.2/api/#operation/PostAuthorizations) permission  | Use the `Authorization: Token YOUR_API_TOKEN` header. |
+| Authorization ID     | URL path parameter. |
+
+```sh
+# Delete the first authorization listed for the user.
+curl --request GET \
+  "http://localhost:8086/api/v2/authorizations?user=user2" \
+  --header "Authorization: Token ${INFLUX_OP_TOKEN}" \
+  --header 'Content-type: application/json' \
+| jq .authorizations[0].id \
+| xargs -I authid curl --request DELETE \
+  http://localhost:8086/api/v2/authorizations/authid \
+  --header "Authorization: Token ${INFLUX_OP_TOKEN}" \
+  --header 'Content-type: application/json'
+```
diff --git a/content/influxdb/v2.2/security/tokens/update-tokens.md b/content/influxdb/v2.2/security/tokens/update-tokens.md
new file mode 100644
index 000000000..ca66c3399
--- /dev/null
+++ b/content/influxdb/v2.2/security/tokens/update-tokens.md
@@ -0,0 +1,129 @@
+---
+title: Update a token
+seotitle: Update API tokens in InfluxDB
+description: Update API tokens' descriptions in InfluxDB using the InfluxDB UI.
+aliases:
+  - /influxdb/v2.2/users/tokens/update-tokens
+menu:
+  influxdb_2_2:
+    name: Update a token
+    parent: Manage tokens
+weight: 203
+---
+
+Update an API token's description and status.
+using the InfluxDB user interface (UI).
+
+- [Update a token in the InfluxDB UI](#update-a-token-in-the-influxdb-ui)
+- [Enable or disable a token in the InfluxDB UI](#enable-or-disable-a-token-in-the-influxdb-ui)
+- [Enable a token using the influx CLI](#enable-a-token-using-the-influx-cli)
+- [Disable a token using the influx CLI](#disable-a-token-using-the-influx-cli)
+- [Update a token using the InfluxDB API](#update-a-token-using-the-influxdb-api)
+
+## Update a token in the InfluxDB UI
+
+1. In the navigation menu on the left, select **Data (Load Data)** > **Tokens**.
+
+    {{< nav-icon "load-data" >}}
+
+2. Click the pencil icon {{< icon "pencil" >}} next to the token's name in the **Description** column.
+3. Update the token description, then click anywhere else to save.
+
+## Enable or disable a token in the InfluxDB UI
+
+{{% oss-only %}}
+
+1. In the navigation menu on the left, select **Data (Load Data)** > **Tokens**.
+
+    {{< nav-icon "load-data" >}}
+
+2. Click the **{{< icon "toggle-green" >}} Status** toggle.
+
+{{% /oss-only %}}
+
+{{% cloud-only %}}
+
+1. In the navigation menu on the left, select **Load Data** > **API Tokens**.
+
+    {{< nav-icon "data" >}}
+
+2. Find the token that you would like to enable or disable.
+3. Click the token description.
+4. Click the **{{< icon "toggle-blue" >}} Status** toggle.
+
+{{% /cloud-only %}}
+
+## Enable a token using the influx CLI
+
+Use the [`influx auth active` command](/influxdb/v2.2/reference/cli/influx/auth/active)
+to activate a token.
+
+_This command requires an authorization ID, which is available in the output of `influx auth find`._
+
+```sh
+# Syntax
+influx auth active -i <auth-id>
+
+# Example
+influx auth active -i 0804f74142bbf000
+```
+To get the current status of a token, use the JSON output of the [`influx auth list` command](/influxdb/v2.2/reference/cli/influx/auth/list).
+
+```sh
+influx auth find --json
+```
+
+### Disable a token using the influx CLI
+
+Use the [`influx auth inactive` command](/influxdb/v2.2/reference/cli/influx/auth/active)
+to deactivate a token.
+
+_This command requires an authorization ID, which is available in the output of `influx auth find`._
+
+```sh
+# Syntax
+influx auth inactive -i <auth-id>
+
+# Example
+influx auth inactive -i 0804f74142bbf000
+```
+
+To get the current status of a token, use the JSON output of the [`influx auth list` command](/influxdb/v2.2/reference/cli/influx/auth/list).
+
+```sh
+influx auth find --json
+```
+
+## Update a token using the InfluxDB API
+
+Use the `/api/v2/authorizations` InfluxDB API endpoint to update the description and status of a token.
+
+[{{< api-endpoint method="PATCH" endpoint="http://localhost:8086/api/v2/authorizations/AUTH_ID" >}}](/influxdb/v2.2/api/#operation/PatchAuthorizationsID)
+
+Include the following in your request:
+
+| Requirement          | Include by                                               |
+|:-----------          |:----------                                               |
+| API token with the [`write: authorizations`](/influxdb/v2.2/api/#operation/PostAuthorizations) permission  | Use the `Authorization: Token YOUR_API_TOKEN` header. |
+| Authorization ID     | URL path parameter.                                      |
+| Description and/or Status | Pass as `description`, `status` in the request body.    |
+
+### Disable a token
+
+```sh
+# Update the description and status of the first authorization listed for the user.
+
+curl --request GET \
+  "http://localhost:8086/api/v2/authorizations?user=user2" \
+  --header "Authorization: Token ${INFLUX_TOKEN}" \
+  --header 'Content-type: application/json' \
+| jq .authorizations[0].id \
+| xargs -I authid curl --request PATCH \
+  http://localhost:8086/api/v2/authorizations/authid \
+  --header "Authorization: Token ${INFLUX_TOKEN}" \
+  --header 'Content-type: application/json' \
+  --data '{
+            "description": "deactivated_auth",
+            "status": "inactive"
+          }' | jq .
+```
diff --git a/content/influxdb/v2.2/security/tokens/use-tokens.md b/content/influxdb/v2.2/security/tokens/use-tokens.md
new file mode 100644
index 000000000..3c96f0e5e
--- /dev/null
+++ b/content/influxdb/v2.2/security/tokens/use-tokens.md
@@ -0,0 +1,44 @@
+---
+title: Use tokens
+seotitle: Use an API token in InfluxDB
+description: Use an API token in the InfluxDB UI, the `influx` CLI, or the InfluxDB API.
+aliases:
+  - /influxdb/v2.2/users/tokens/use-tokens
+menu:
+  influxdb_2_2:
+    name: Use tokens
+    parent: Manage tokens
+weight: 204
+---
+
+Use tokens to authenticate requests to InfluxDB, including requests to write, query, and manage data and resources.
+Authenticate requests using the [`influx` CLI](/influxdb/v2.2/reference/cli/influx/), API requests made with client libraries, and tools like `curl`.
+
+### Add a token to a CLI request
+
+```sh
+influx write -t <token> -b BUCKET -o org-name <LINE PROTOCOL>
+```
+
+```
+export INFLUX_TOKEN=my-token
+influx write -t $INFLUX_TOKEN -b my-bucket -o my-org "measurement field=1"
+```
+
+{{% note %}}
+See [here](/influxdb/v2.2/write-data/no-code/use-telegraf/auto-config/#configure-your-token-as-an-environment-variable)
+to configure environment variables on Windows.
+(Click on the **Windows** tab.)
+{{% /note %}}
+
+### Use CLI configurations
+
+Automatically manage and use tokens from the CLI using [`influx config`](/influxdb/v2.2/reference/cli/influx/config/).
+
+### Use a token in an API request
+
+Use tokens in [API requests](/influxdb/v2.2/api-guide/api_intro/#authentication).
+
+### Use a token in Postman
+
+Make authenticated requests with tokens [using Postman](/influxdb/v2.2/api-guide/postman/).
diff --git a/content/influxdb/v2.2/security/tokens/view-tokens.md b/content/influxdb/v2.2/security/tokens/view-tokens.md
new file mode 100644
index 000000000..3f574ce7a
--- /dev/null
+++ b/content/influxdb/v2.2/security/tokens/view-tokens.md
@@ -0,0 +1,110 @@
+---
+title: View tokens
+seotitle: View API tokens in InfluxDB
+description: View API tokens in InfluxDB using the InfluxDB UI, the `influx` CLI, or the InfluxDB API.
+aliases:
+  - /influxdb/v2.2/users/tokens/view-tokens
+menu:
+  influxdb_2_2:
+    name: View tokens
+    parent: Manage tokens
+weight: 202
+---
+
+View API tokens and permissions using the InfluxDB user interface (UI),
+the `influx` command line interface (CLI), or the InfluxDB API.
+
+{{% note %}}
+
+{{% oss-only %}}Tokens are visible to the user who created the token. Users who own a token with Operator permissions also have access to all tokens.
+Tokens stop working when the user who created the token is deleted.
+
+**We recommend creating a generic user to create and manage tokens for writing data.**
+{{% /oss-only %}}
+
+{{% cloud-only %}}
+To follow best practices for secure API token generation and retrieval, InfluxDB Cloud enforces access restrictions on API tokens.
+  - InfluxDB Cloud UI only allows access to the API token value immediately after the token is created.
+  - You can't change access (**read/write**) permissions for an API token after it's created.
+  - Tokens stop working when the user who created the token is deleted.
+
+We recommend the following for managing your tokens:
+- Create a generic user to create and manage tokens for writing data.
+- Store your tokens in a secure password vault for future access.
+{{% /cloud-only %}}
+{{% /note %}}
+
+## View tokens in the InfluxDB UI
+
+{{% oss-only %}}
+
+1. In the navigation menu on the left, select **Data (Load Data)** > **API Tokens**.
+
+    {{< nav-icon "load-data" >}}
+
+2. Click a token name in the list to view the token and a summary of access permissions.
+
+{{% /oss-only %}}
+
+{{% cloud-only %}}
+
+1. In the navigation menu on the left, select **Load Data** > **API Tokens**.
+
+    {{< nav-icon "load-data" >}}
+
+2. Click a token description in the list to view the token status and a list of access permissions.
+
+{{% /cloud-only %}}
+
+## View tokens using the influx CLI
+
+Use the [`influx auth list` command](/influxdb/v2.2/reference/cli/influx/auth/list)
+to view tokens.
+
+```sh
+influx auth list
+```
+
+Filtering options such as filtering by authorization ID, username, or user ID are available.
+See the [`influx auth list` documentation](/influxdb/v2.2/reference/cli/influx/auth/list)
+for information about other available flags.
+
+## View tokens using the InfluxDB API
+
+Use the `/api/v2/authorizations` InfluxDB API endpoint to view tokens and permissions.
+
+[{{< api-endpoint method="GET" endpoint="/api/v2/authorizations" >}}](/influxdb/cloud/api/#operation/GetAuthorizations)
+
+Include the following in your request:
+
+| Requirement          | Include by                                               |
+|:-----------          |:----------                                               |
+| API token with the [`read: authorizations`](/influxdb/v2.2/api/#operation/PostAuthorizations) permission  | Use the `Authorization: Token YOUR_API_TOKEN` header.                   |
+
+```sh
+{{% get-shared-text "api/v2.0/auth/oss/tokens-view.sh" %}}
+```
+
+### View a single token
+
+To view a specific authorization and token, include the authorization ID in the URL path.
+
+{{% api-endpoint method="GET" endpoint="/api/v2/authorizations/{authID}" %}}
+
+### Filter the token list
+
+InfluxDB returns authorizations from the same organization as the token used in the request.
+To filter tokens by user, include `userID` as a query parameter in your request.
+
+```sh
+{{% get-shared-text "api/v2.0/auth/oss/tokens-view-filter.sh" %}}
+```
+
+{{% oss-only %}}
+
+[***Operator tokens***](/{{% latest "influxdb" %}}/security/tokens/#operator-token) have access to all organizations' authorizations.
+To filter authorizations by organization when using an operator token, include an `org` or `orgID` query parameter in your request.
+
+{{% oss-only %}}
+
+See the [`/authorizations` endpoint documentation](/influxdb/v2.2/api/#tag/Authorizations) for more information about available parameters.
diff --git a/content/influxdb/v2.2/tags/_index.md b/content/influxdb/v2.2/tags/_index.md
new file mode 100644
index 000000000..3a3d5c828
--- /dev/null
+++ b/content/influxdb/v2.2/tags/_index.md
@@ -0,0 +1,4 @@
+---
+title: Tags and related content
+layout: tags-landing
+---
diff --git a/content/influxdb/v2.2/telegraf-configs/_index.md b/content/influxdb/v2.2/telegraf-configs/_index.md
new file mode 100644
index 000000000..bf700b10e
--- /dev/null
+++ b/content/influxdb/v2.2/telegraf-configs/_index.md
@@ -0,0 +1,37 @@
+---
+title: Telegraf configurations
+description: >
+  InfluxDB OSS lets you automatically generate Telegraf configurations or upload custom
+  Telegraf configurations that collect metrics and write them to InfluxDB OSS.
+weight: 12
+menu: influxdb_2_2
+influxdb/v2.2/tags: [telegraf]
+related:
+  - /influxdb/v2.2/write-data/no-code/use-telegraf/manual-config/
+  - /influxdb/v2.2/write-data/no-code/use-telegraf/auto-config/
+---
+
+InfluxDB lets you automatically generate Telegraf configurations or upload custom
+Telegraf configurations that collect metrics and write them to InfluxDB.
+Telegraf retrieves configurations from InfluxDB on startup.
+
+## Use InfluxDB Telegraf configurations
+With a Telegraf configuration stored in InfluxDB, the `telegraf` agent can retrieve
+the configuration from an InfluxDB HTTP(S) endpoint.
+
+- Ensure Telegraf has network access to InfluxDB (OSS or Cloud).
+- Start the `telegraf` agent using the `--config` flag to provide the URL of the
+  InfluxDB Telegraf configuration. For example:
+
+    ```sh
+    telegraf --config http://localhost:8086/api/v2/telegrafs/<telegraf-config-id>
+    ```
+
+{{% note %}}
+_[Setup instructions](/influxdb/v2.2/telegraf-configs/view/#view-setup-instructions) for
+each Telegraf configuration are provided in the InfluxDB UI._
+{{% /note %}}
+
+## Manage Telegraf configurations
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/telegraf-configs/clone.md b/content/influxdb/v2.2/telegraf-configs/clone.md
new file mode 100644
index 000000000..718c08349
--- /dev/null
+++ b/content/influxdb/v2.2/telegraf-configs/clone.md
@@ -0,0 +1,21 @@
+---
+title: Clone a Telegraf configuration
+description: >
+  Use the InfluxDB UI to clone an Telegraf configuration.
+weight: 101
+menu:
+  influxdb_2_2:
+    name: Clone a config
+    parent: Telegraf configurations
+---
+
+Use the InfluxDB user interface (UI) to clone a Telegraf configuration.
+
+
+1. In the navigation menu on the left, select **Data** (**Load Data**) > **Telegraf**.
+
+    {{< nav-icon "load data" >}}
+
+2. Hover over the configuration you want to clone, click the **{{< icon "clone" >}}**
+   icon, and then click **Clone**.
+   The clone appears in your list of Telegraf configurations.
diff --git a/content/influxdb/v2.2/telegraf-configs/create.md b/content/influxdb/v2.2/telegraf-configs/create.md
new file mode 100644
index 000000000..a2ee596cf
--- /dev/null
+++ b/content/influxdb/v2.2/telegraf-configs/create.md
@@ -0,0 +1,72 @@
+---
+title: Create a Telegraf configuration
+description: >
+  Use the InfluxDB UI or the [`influx` CLI](/influxdb/v2.2/reference/cli/influx/)
+  to create an Telegraf configuration.
+weight: 101
+menu:
+  influxdb_2_2:
+    name: Create a config
+    parent: Telegraf configurations
+related:
+  - /influxdb/v2.2/write-data/no-code/use-telegraf/manual-config/
+  - /influxdb/v2.2/write-data/no-code/use-telegraf/auto-config/
+  - /influxdb/v2.2/telegraf-configs/update/
+---
+Telegraf has an extensive list of plugins for many different technologies and use cases.
+Not all plugins are available through the InfluxDB UI, but you can
+[create and upload custom Telegraf configurations](#create-a-custom-telegraf-configuration)
+to include any of the available [Telegraf plugins](/{{< latest "telegraf" >}}/plugins/).
+
+Use the InfluxDB user interface (UI) or the [`influx` CLI](/influxdb/v2.2/reference/cli/influx/)
+to create a Telegraf configuration.
+
+To create a Telegraf configuration, do one of the following:
+
+- [Use the InfluxDB UI](#use-the-influxdb-ui)
+- [Use the `influx` CLI](#use-the-influx-cli)
+- [Create a custom Telegraf configuration](#create-a-custom-telegraf-configuration)
+
+## Use the InfluxDB UI
+Use the InfluxDB UI to automatically generate and store new Telegraf configurations in InfluxDB.
+Creating the configuration in the UI lets you select from a list of available technologies and generates a Telegraf configuration to collect metrics from those technologies.
+For more information, see [Automatically configure Telegraf](/influxdb/v2.2/write-data/no-code/use-telegraf/auto-config/).
+
+## Use the influx CLI
+Use the [`influx telegrafs create` command](/influxdb/v2.2/reference/cli/influx/telegrafs/create/)
+to upload a Telegraf configuration file from your local machine and create a new Telegraf
+configuration in InfluxDB.
+
+Provide the following:
+
+- **Telegraf configuration name**
+- **Telegraf configuration description**
+- **Telegraf configuration file**
+
+{{% note %}}
+If a **name** and **description** are not provided, they are set to empty strings.
+{{% /note %}}
+
+<!--  -->
+```sh
+# Syntax
+influx telegrafs create \
+  -n <telegraf-config-name> \
+  -d <telegraf-config-description> \
+  -f /path/to/telegraf.conf
+
+# Example
+influx telegrafs create \
+  -n "Example Telegraf config"
+  -d "This is a description for an example Telegraf configuration."
+  -f /path/to/telegraf.conf
+```
+
+## Create a custom Telegraf configuration
+
+1. Create a custom Telegraf configuration file that includes the `outputs.influxdb_v2`
+   output plugin. _See [Manually configure Telegraf](/influxdb/v2.2/write-data/no-code/use-telegraf/manual-config/)_
+   for more information.
+2. Add and customize [Telegraf plugins](/{{< latest "telegraf" >}}/plugins/) and save your changes.
+3. [Use the `influx telegrafs create` command](#use-the-influx-cli) to upload your
+   custom Telegraf configuration to InfluxDB.
diff --git a/content/influxdb/v2.2/telegraf-configs/remove.md b/content/influxdb/v2.2/telegraf-configs/remove.md
new file mode 100644
index 000000000..377f35ec4
--- /dev/null
+++ b/content/influxdb/v2.2/telegraf-configs/remove.md
@@ -0,0 +1,53 @@
+---
+title: Remove a Telegraf configuration
+description: >
+  Use the InfluxDB UI or the [`influx` CLI](/influxdb/v2.2/reference/cli/influx/)
+  to remove Telegraf configurations from InfluxDB.
+weight: 104
+menu:
+  influxdb_2_2:
+    name: Remove a config
+    parent: Telegraf configurations
+aliases:
+  - /influxdb/v2.2/write-data/no-code/use-telegraf/auto-config/delete-telegraf-config/
+  - /influxdb/v2.2/collect-data/use-telegraf/auto-config/delete-telegraf-config
+---
+
+Use the InfluxDB user interface (UI) or the [`influx` CLI](/influxdb/v2.2/reference/cli/influx/)
+to remove Telegraf configurations from InfluxDB.
+
+{{% note %}}
+Deleting a Telegraf configuration does not affect _**running**_ Telegraf agents.
+However, if an agents stops, it needs a new configuration to start.
+{{% /note %}}
+
+To remove a Telegraf configuration, do one of the following:
+
+- [Use the InfluxDB UI](#use-the-influxdb-ui)
+- [Use the `influx` CLI](#use-the-influx-cli)
+
+## Use the InfluxDB UI
+
+1. In the navigation menu on the left, select **Data** (**Load Data**) > **Telegraf**.
+
+    {{< nav-icon "load data" >}}
+
+2. Hover over the configuration you want to delete, click the **{{< icon "trash" >}}**
+   icon, and then click **Delete**.
+
+
+## Use the influx CLI
+Use the [`influx telegrafs rm` command](/influxdb/v2.2/reference/cli/influx/telegrafs/rm/)
+to remove a Telegraf configuration from InfluxDB.
+
+Provide the following:
+
+- **Telegraf configuration ID** (shown in the output of `influx telegrafs`)
+
+```sh
+# Syntax
+influx telegrafs rm -i <telegraf-config-id>
+
+# Example
+influx telegrafs rm -i 12ab34de56fg78hi
+```
diff --git a/content/influxdb/v2.2/telegraf-configs/update.md b/content/influxdb/v2.2/telegraf-configs/update.md
new file mode 100644
index 000000000..36175b504
--- /dev/null
+++ b/content/influxdb/v2.2/telegraf-configs/update.md
@@ -0,0 +1,102 @@
+---
+title: Update a Telegraf configuration
+description: >
+  Use the InfluxDB user interface (UI) or the [`influx` CLI](/influxdb/v2.2/reference/cli/influx/)
+  to update InfluxDB Telegraf configurations.
+weight: 103
+menu:
+  influxdb_2_2:
+    name: Update a config
+    parent: Telegraf configurations
+aliases:
+  - /influxdb/v2.2/write-data/no-code/use-telegraf/auto-config/update-telegraf-config/
+  - /influxdb/v2.2/collect-data/use-telegraf/auto-config/update-telegraf-config
+---
+
+Use the InfluxDB user interface (UI) or the [`influx` CLI](/influxdb/v2.2/reference/cli/influx/)
+to update InfluxDB Telegraf configurations.
+
+To update a Telegraf configuration, do one of the following:
+
+- [Use the InfluxDB UI](#use-the-influxdb-ui)
+- [Use the `influx` CLI](#use-the-influx-cli)
+
+{{% note %}}
+Telegraf doesn't detect changes to remote configurations. If you edit a remote configuration, you must restart Telegraf or send it a SIGHUP command for your changes to take effect.
+{{% /note %}}
+
+## Use the InfluxDB UI
+
+### Update the name or description  of a configuration
+
+1. In the navigation menu on the left, select **Data** (**Load Data**) > **Telegraf**.
+
+    {{< nav-icon "load data" >}}
+
+2. Hover over the configuration you want to edit and click **{{< icon "pencil" >}}**
+   to update the name or description.
+3. Press **Return** or click out of the editable field to save your changes.
+
+### Edit the configuration file directly in the UI
+
+1. In the navigation menu on the left, select **Data** (**Load Data**) > **Telegraf**.
+
+    {{< nav-icon "load data" >}}
+
+2. To edit the configuration file:
+  a. Click the name of the configuration.
+  b. Add or update [Telegraf plugin settings](/{{< latest "telegraf" >}}/plugins/) in the window that appears.
+  {{% note %}}
+  The text editor window doesn't detect if any plugins or settings are misconfigured. Any errors in your configuration that may cause Telegraf to fail when you restart it.
+  {{% /note %}}
+  c. Click **Save Changes** and then **Save** again to confirm.
+3. To apply the updated configuration, restart Telegraf. To find the exact command to start Telegraf, click **Setup Instructions** on the **Telegraf** page.
+
+### Download and verify the configuration file
+
+1. In the navigation menu on the left, select **Data** (**Load Data**) > **Telegraf**.
+
+    {{< nav-icon "load data" >}}
+
+2. Click the **name** of the Telegraf configuration to customize.
+3. Click **Download Config** to download the Telegraf configuration file to your
+   local machine.
+4. Review the configuration file. Add or update [Telegraf plugin](/{{< latest "telegraf" >}}/plugins/) settings and
+   save your changes.
+5. [Use the `influx telegrafs update` command](#use-the-influx-cli) to upload your
+   modified Telegraf configuration to InfluxDB and replace the existing configuration.
+6. To apply the updated configuration, restart Telegraf. To find the exact command to start Telegraf, click **Setup Instructions** on the **Telegraf** page.
+
+## Use the influx CLI
+
+Use the [`influx telegrafs update` command](/influxdb/v2.2/reference/cli/influx/telegrafs/update/)
+to update an existing InfluxDB Telegraf configuration name, description, or settings
+from a Telegraf configuration file on your local machine.
+
+Provide the following:
+
+- **Telegraf configuration ID** (shown in the output of `influx telegrafs`)
+- **Telegraf configuration name**
+- **Telegraf configuration description**
+- **Telegraf configuration file**
+
+{{% warn %}}
+If a **name** and **description** are not provided, they are replaced with empty strings.
+{{% /warn %}}
+
+<!--  -->
+```sh
+# Syntax
+influx telegrafs update \
+  -i <telegraf-config-id> \
+  -n <telegraf-config-name> \
+  -d <telegraf-config-description> \
+  -f /path/to/telegraf.conf
+
+# Example
+influx telegrafs update \
+  -i 12ab34de56fg78hi
+  -n "Example Telegraf config"
+  -d "This is a description for an example Telegraf configuration."
+  -f /path/to/telegraf.conf
+```
diff --git a/content/influxdb/v2.2/telegraf-configs/view.md b/content/influxdb/v2.2/telegraf-configs/view.md
new file mode 100644
index 000000000..50b331794
--- /dev/null
+++ b/content/influxdb/v2.2/telegraf-configs/view.md
@@ -0,0 +1,45 @@
+---
+title: View Telegraf configurations
+description: >
+  Use the InfluxDB user interface (UI) or the [`influx` CLI](/influxdb/v2.2/reference/cli/influx/)
+  to view and download InfluxDB Telegraf configurations.
+weight: 102
+menu:
+  influxdb_2_2:
+    name: View configs
+    parent: Telegraf configurations
+aliases:
+  - /influxdb/v2.2/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/
+  - /influxdb/v2.2/collect-data/use-telegraf/auto-config/view-telegraf-config
+---
+
+Use the InfluxDB user interface (UI) or the [`influx` CLI](/influxdb/v2.2/reference/cli/influx/)
+to view and download InfluxDB Telegraf configurations.
+
+To view Telegraf configurations, do one of the following:
+
+- [Use the InfluxDB UI](#use-the-influxdb-ui)
+- [Use the `influx` CLI](#use-the-influx-cli)
+
+## Use the InfluxDB UI
+In the navigation menu on the left, select **Data** (**Load Data**) > **Telegraf**.
+
+{{< nav-icon "load data" >}}
+
+### View and download the telegraf.conf
+To view the `telegraf.conf` associated with the configuration,
+click the **Name** of the configuration.
+Then click **Download Config** to download the file.
+
+### View setup instructions
+To view the setup instructions for a Telegraf configuration, click **Setup Instructions**.
+Setup instructions include commands for adding your InfluxDB API token
+as an environment variable and starting Telegraf with the specific configuration.
+
+## Use the influx CLI
+Use the [`influx telegrafs` command](/influxdb/v2.2/reference/cli/influx/telegrafs/) to
+list Telegraf configurations stored in InfluxDB.
+
+```sh
+influx telegrafs
+```
diff --git a/content/influxdb/v2.2/tools/_index.md b/content/influxdb/v2.2/tools/_index.md
new file mode 100644
index 000000000..95baaa960
--- /dev/null
+++ b/content/influxdb/v2.2/tools/_index.md
@@ -0,0 +1,11 @@
+---
+title: InfluxDB tools and integrations
+description: >
+  Use InfluxDB tools and other third-party integrations to interact with, manage, and visualize data in InfluxDB.
+weight: 13
+menu:
+  influxdb_2_2:
+    name: Tools & integrations
+---
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/tools/chronograf.md b/content/influxdb/v2.2/tools/chronograf.md
new file mode 100644
index 000000000..2ece60569
--- /dev/null
+++ b/content/influxdb/v2.2/tools/chronograf.md
@@ -0,0 +1,95 @@
+---
+title: Use Chronograf with InfluxDB OSS
+description: >
+  Chronograf is a data visualization and dashboarding tool designed to visualize data in InfluxDB 1.x.
+  It is part of the [TICKstack](/platform/) that provides an InfluxQL data explorer, Kapacitor integrations, and more.
+  Continue to use Chronograf with **InfluxDB Cloud** and **InfluxDB OSS 2.x** and the
+  [1.x compatibility API](/influxdb/v2.2/reference/api/influxdb-1x/).
+menu:
+  influxdb_2_2:
+    name: Use Chronograf
+    parent: Tools & integrations
+weight: 103
+related:
+  - /{{< latest "chronograf" >}}/
+---
+
+[Chronograf](/{{< latest "chronograf" >}}/) is a data visualization and dashboarding
+tool designed to visualize data in InfluxDB 1.x. It is part of the [TICKstack](/platform/)
+that provides an InfluxQL data explorer, Kapacitor integrations, and more.
+Continue to use Chronograf with **InfluxDB Cloud** and **InfluxDB OSS {{< current-version >}}** and the
+[1.x compatibility API](/influxdb/v2.2/reference/api/influxdb-1x/).
+
+
+## Create an InfluxDB connection
+1. In Chronograf, click **Configuration** in the left navigation bar,
+   and then click **{{< icon "plus" >}} Add Connection**.
+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" />}}
+3. Enter your InfluxDB connection credentials:
+    - **Connection URL:** InfluxDB URL _(see [InfluxDB Cloud regions](/influxdb/cloud/reference/regions/)
+      or [InfluxDB OSS URLs](/influxdb/%762.1/reference/urls/))_
+
+      ```
+      http://localhost:8086
+      ```
+
+    - **Connection Name:** Name to uniquely identify this connection configuration
+    - **Organization:** InfluxDB [organization](/influxdb/v2.2/organizations/)
+    - **Token:** InfluxDB [API token](/influxdb/v2.2/security/tokens/)
+    - **Telegraf Database Name:** InfluxDB [bucket](/influxdb/v2.2/organizations/buckets/)
+      Chronograf uses to populate parts of the application, including the Host List page (default is `telegraf`)
+    - **Default Retention Policy:** default [retention policy](/{{< latest "influxdb" "v1" >}}/concepts/glossary/#retention-policy-rp)
+      _**(leave blank)**_
+
+        {{% note %}}
+#### DBRPs map to InfluxDB buckets
+In InfluxDB Cloud and InfluxDB OSS {{< current-version >}}, database/retention-policy (DBRP) combinations
+are mapped to buckets using the `database-name/retention-policy` naming convention.
+**DBRP mappings are required to query InfluxDB OSS 2.x or InfluxDB Cloud using InfluxQL.**
+
+For information, see [DBRP mapping](/influxdb/v2.2/reference/api/influxdb-1x/dbrp/)
+and [Map unmapped buckets](/influxdb/v2.2/query-data/influxql/#map-unmapped-buckets).
+      {{% /note %}}
+
+3. Click **Add Connection**.
+4. Select the dashboards you would like to create, and then click **Next**.
+5. To configure a Kapacitor connection, provide the necessary credentials,
+   and then click **Continue**. Otherwise, click **Skip**.
+   _For information about using Kapacitor with InfluxDB Cloud or InfluxDB OSS {{< current-version >}},
+   see [Use Kapacitor with InfluxDB](/influxdb/v2.2/tools/kapacitor/)._
+6. Click **Finish**.
+
+## Important notes
+
+- [Update upgraded InfluxDB connections](#Update-upgraded-InfluxDB-connections)
+- [No administrative functionality](#No-administrative-functionality)
+- [Limited InfluxQL support](#Limited-InfluxQL-support)
+
+### Update upgraded InfluxDB connections
+If using Chronograf with an InfluxDB instance that was upgraded from 1.x
+to 2.x, update your InfluxDB connection configuration in Chronograf to use the
+**InfluxDB v2 Auth** option and provide an organization and a token.
+**Without an organization, Chronograf cannot use Flux to query InfluxDB.**
+
+### No administrative functionality
+Chronograf cannot be used for administrative tasks in InfluxDB Cloud and InfluxDB OSS {{< current-version >}}.
+For example, you **cannot** do the following:
+
+- Define databases
+- Modify retention policies
+- Add users
+- Kill queries
+
+When connected to an InfluxDB Cloud or InfluxDB {{< current-version >}} database, functionality in the
+**{{< icon "crown" >}} InfluxDB Admin** section of Chronograf is disabled.
+
+To complete administrative tasks, use the following:
+
+- **InfluxDB user interface (UI)**
+- [InfluxDB CLI](/influxdb/v2.2/reference/cli/influx/)
+- [InfluxDB v2 API](/influxdb/v2.2/reference/api/)
+
+### Limited InfluxQL support
+InfluxDB Cloud and InfluxDB OSS {{< current-version >}} support InfluxQL **read-only** queries.
+For more information, see [InfluxQL support](/influxdb/v2.2/query-data/influxql/#influxql-support).
diff --git a/content/influxdb/v2.2/tools/flux-vim-lsp.md b/content/influxdb/v2.2/tools/flux-vim-lsp.md
new file mode 100644
index 000000000..1feeb6630
--- /dev/null
+++ b/content/influxdb/v2.2/tools/flux-vim-lsp.md
@@ -0,0 +1,111 @@
+---
+title: Use the Flux LSP with Vim
+description: >
+  Use the Flux LSP with Vim to add auto-completion, syntax checking, and other language-specific features to your editor.
+menu:
+  influxdb_2_2:
+    parent: Tools & integrations
+weight: 102
+---
+
+## Requirements
+
+- Vim 8+
+- [npm](https://www.npmjs.com/get-npm)
+
+## Install the Flux plugin
+
+There are many ways to install and manage Vim plugins.
+We recommend either of the following two methods:
+
+- [Install with vim-lsp](#install-with-vim-lsp)
+- [Install with vim-coc](#install-with-vim-coc)
+
+Both methods require you to add the following to your `.vimrc` so that Vim can recognize the `.flux` file type:
+
+```
+" Flux file type
+au BufRead,BufNewFile *.flux		set filetype=flux
+```
+
+### Install with vim-lsp
+
+1. **Install `flux-lsp-cli` with npm**
+
+    ```sh
+    npm i -g @influxdata/flux-lsp-cli
+    ```
+
+2. **Install [vim-lsp](https://github.com/prabirshrestha/vim-lsp)**
+
+    If it doesn't exist yet, create a directory called `pack/$USER/start/` in your `~/.vim/` and clone `vim-lsp` into it:
+
+    ```sh
+    cd ~
+    mkdir -p .vim/pack/$USER/start/
+    cd .vim/pack/$USER/start/
+    git clone https://github.com/prabirshrestha/vim-lsp
+    ```
+
+3. **Edit your `.vimrc`**
+
+    Next, edit your `.vimrc` configuration file to include the following:
+
+    ```
+    let g:lsp_diagnostics_enabled = 1
+
+    if executable('flux-lsp')
+        au User lsp_setup call lsp#register_server({
+            \ 'name': 'flux lsp',
+            \ 'cmd': {server_info->[&shell, &shellcmdflag, 'flux-lsp']},
+            \ 'whitelist': ['flux'],
+            \ })
+    endif
+
+    autocmd FileType flux nmap gd <plug>(lsp-definition)
+    ```
+
+### Install with vim-coc
+
+1. **Install `flux-lsp-cli` from npm**
+
+    ```sh
+    npm i -g @influxdata/flux-lsp-cli
+    ```
+2. **Install plug-vim**
+
+    [Install plug-vim](https://github.com/junegunn/vim-plug#installation), a plugin manager for Vim.
+
+3. **Install vim-coc**
+
+    [Install vim-coc](https://github.com/neoclide/coc.nvim#quick-start), a code-completion plugin for Vim.
+
+4. **Configure vim-coc**
+
+    vim-coc uses a `coc-settings.json` located in your `~/.vim/` directory.
+    To run the Flux LSP, add the Flux section under `languageserver`:
+
+    ```json
+    {
+      "languageserver": {
+          "flux": {
+            "command": "flux-lsp",
+            "filetypes": ["flux"]
+          }
+      }
+    }
+    ```
+
+    To debug flux-lsp, configure it to log to `/tmp/fluxlsp`:
+
+    ```json
+    {
+      "languageserver": {
+          "flux": {
+            "command": "flux-lsp",
+            "args": ["-l", "/tmp/fluxlsp"],
+            "filetypes": ["flux"]
+          }
+      }
+    }
+    ```
diff --git a/content/influxdb/v2.2/tools/flux-vscode.md b/content/influxdb/v2.2/tools/flux-vscode.md
new file mode 100644
index 000000000..1be52cd24
--- /dev/null
+++ b/content/influxdb/v2.2/tools/flux-vscode.md
@@ -0,0 +1,94 @@
+---
+title: Use the Flux VS Code extension
+seotitle: Use the Flux Visual Studio Code extension
+description: >
+  The [Flux Visual Studio Code (VS Code) extension](https://marketplace.visualstudio.com/items?itemName=influxdata.flux)
+  provides Flux syntax highlighting, autocompletion, and a direct InfluxDB OSS server
+  integration that lets you run Flux scripts natively and show results in VS Code.
+weight: 103
+menu:
+  influxdb_2_2:
+    name: Use the Flux VS Code extension
+    parent: Tools & integrations
+---
+
+The [Flux Visual Studio Code (VS Code) extension](https://marketplace.visualstudio.com/items?itemName=influxdata.flux)
+provides Flux syntax highlighting, autocompletion, and a direct InfluxDB server
+integration that lets you run Flux scripts natively and show results in VS Code.
+
+##### On this page
+- [Install the Flux VS Code extension](#install-the-flux-vs-code-extension)
+- [Connect to InfluxDB](#connect-to-influxdb)
+  - [Manage InfluxDB connections](#manage-influxdb-connections)
+- [Query InfluxDB from VS Code](#query-influxdb-from-vs-code)
+- [Explore your schema](#explore-your-schema)
+- [Debug Flux queries](#debug-flux-queries)
+- [Upgrade the Flux extension](#upgrade-the-flux-extension)
+- [Flux extension commands](#flux-extension-commands)
+
+## Install the Flux VS Code extension
+The Flux VS Code extension is available in the **Visual Studio Marketplace**.
+For information about installing extensions from the Visual Studio marketplace,
+see the [Extension Marketplace documentation](https://code.visualstudio.com/docs/editor/extension-gallery).
+
+Once installed, open the **Explorer** area of your VS Code user interface.
+A new **InfluxDB** pane is available below your file explorer.
+
+{{< img-hd src="/img/influxdb/2-1-tools-vsflux-influxdb-pane.png" alt="InfluxDB pane in VS Code" />}}
+
+## Connect to InfluxDB
+To create an InfluxDB connection in VS Code:
+
+1. Hover over the **InfluxDB** pane and then click the **{{< icon "plus" >}}** icon that appears.
+
+    {{< img-hd src="/img/influxdb/2-1-tools-vsflux-add-connection.png" alt="Add an InfluxDB connection in VS Code" />}}
+
+2. Provide the required connection credentials:
+    - **Type:** type of InfluxDB data source. Select **InfluxDB v2**.
+    - **Name:** unique identifier for your InfluxDB connection.
+    - **Hostname and Port:** InfluxDB host and port
+      (see [InfluxDB OSS URLs](/influxdb/v2.2/reference/urls/) or [InfluxDB Cloud regions](/influxdb/cloud/reference/regions/)).
+    - **Token:** InfluxDB [API token](/influxdb/v2.2/security/tokens/).
+    - **Organization:** InfluxDB organization name.
+3. Click **Test** to test the connection.
+4. Once tested successfully, click **Save**.
+
+### Manage InfluxDB connections
+In the **InfluxDB** pane:
+
+- **To edit a connection**, right click on the connection to edit and select **Edit Connection**.
+- **To remove a connection**, right click on the connection to remove and select **Remove Connection**.
+- **To switch to a connection**, right click on the connection to switch to and select **Switch To This Connection**.
+
+## Query InfluxDB from VS Code
+1. Write your Flux query in a new VS Code file.
+2. Save your Flux script with the `.flux` extension or set the
+   [VS Code Language Mode](https://code.visualstudio.com/docs/languages/overview#_changing-the-language-for-the-selected-file) to **Flux**.
+3. Execute the query with the `influxdb.runQuery` command or {{< keybind mac="F5" other="F5" >}}.
+4. Query results appear in a new tab. If query results do not appear, see [Debug Flux queries](#debug-flux-queries).
+
+## Explore your schema
+After you've configured an InfluxDB connection, VS Code provides an overview of buckets,
+measurements, and tags in your InfluxDB organization.
+Use the **InfluxDB** pane in VS code to explore your schema.
+
+{{< img-hd src="/img/influxdb/2-0-tools-vsflux-explore-schema.png" alt="Explore your InfluxDB schema in VS Code" />}}
+
+## Debug Flux queries
+To view errors returned from Flux script executions, click the **Errors and Warnings**
+icons in the bottom left of your VS Code window, and then select the **Output** tab in the debugging pane.
+
+{{< img-hd src="/img/influxdb/2-0-tools-vsflux-errors-warnings.png" alt="VS Code errors and warnings"/>}}
+
+## Upgrade the Flux extension
+VS Code auto-updates extensions by default, but you are able to disable auto-update.
+If you disable auto-update, [manually update your VS Code Flux extension](https://code.visualstudio.com/docs/editor/extension-gallery#_update-an-extension-manually).
+After updating the extension, reload your VS Code window ({{< keybind mac="⇧⌘P" other="Ctrl+Shift+P" >}},
+and then `Reload Window`) to initialize the updated extensions.
+
+## Flux extension commands
+
+| Command                     | Description       | Keyboard shortcut                            | Menu context      |
+|:-------                     |:-----------       |:-----------------:                           | ------------:     |
+| `influxdb.refresh`          | Refresh           |                                              |                   |
+| `influxdb.runQuery`         | Run Query         | {{< keybind mac="F5" other="F5" >}} | editor/context    |
diff --git a/content/influxdb/v2.2/tools/google-data-studio.md b/content/influxdb/v2.2/tools/google-data-studio.md
new file mode 100644
index 000000000..9be4145a5
--- /dev/null
+++ b/content/influxdb/v2.2/tools/google-data-studio.md
@@ -0,0 +1,35 @@
+---
+title: Use the Google Data Studio connector
+description: >
+  The [InfluxDB Google Data Studio connector](https://datastudio.google.com/u/0/datasources/create?connectorId=AKfycbwhJChhmMypQvNlihgRJMAhCb8gaM3ii9oUNWlW_Cp2PbJSfqeHfPyjNVp15iy9ltCs)
+  lets you create reports and dashboards in Google Data Studio with data from
+  InfluxDB Cloud or InfluxDB OSS 2.x.
+menu:
+  influxdb_2_2:
+    parent: Tools & integrations
+weight: 104
+influxdb/v2.2/tags: [google]
+---
+
+The [InfluxDB Google Data Studio connector](https://datastudio.google.com/u/0/datasources/create?connectorId=AKfycbwhJChhmMypQvNlihgRJMAhCb8gaM3ii9oUNWlW_Cp2PbJSfqeHfPyjNVp15iy9ltCs) lets you create reports and dashboards in Google Data Studio with data from **InfluxDB Cloud** or **InfluxDB OSS {{< current-version >}}**. The connector supports one measurement per organization.
+
+### Add the InfluxDB Connector to Data Studio
+
+1. Add the [InfluxDB Connector data source](https://datastudio.google.com/u/0/datasources/create?connectorId=AKfycbwhJChhmMypQvNlihgRJMAhCb8gaM3ii9oUNWlW_Cp2PbJSfqeHfPyjNVp15iy9ltCs).
+2. Enter the following connection details:
+  - `InfluxDB URL`: Your [InfluxDB URL](/influxdb/v2.2/reference/urls/).
+  - `Token`: Your [API token](/influxdb/v2.2/security/tokens/create-token/) with permission to read from the bucket you're using.
+  - `Organization`: Your [organization name](/influxdb/v2.2/organizations/view-orgs).
+  - `Bucket`: Your [bucket name](/influxdb/v2.2/organizations/buckets/view-buckets/). This is auto-populated when you enter the fields above.
+  - `Measurement`: The [measurement](/influxdb/v2.2/reference/glossary/#measurement) to connect to.
+3. Click **Connect**.
+
+### Create a report of InfluxDB data in Data Studio
+
+1. Once you're connected, a list of fields available from your measurement, including the [tag set](/influxdb/v2.2/reference/glossary/#tag-set), [field set](/influxdb/v2.2/reference/glossary/#field-set), and [timestamp](/influxdb/v2.2/reference/glossary/#timestamp) appear. Review the list of fields and [edit as needed](https://support.google.com/datastudio/answer/7000529?hl=en&ref_topic=6370331).
+2. Click **CREATE REPORT** to [create the report](https://support.google.com/datastudio/topic/6369007?hl=en&ref_topic=6291037).
+3. Customize the [visualization in your report](https://support.google.com/datastudio/?hl=en#topic=6291037).
+
+### Example use case with COVID-19 data
+
+For an example of how to use this connector, see a [COVID-19 report powered by InfluxDB](https://github.com/influxdata/influxdb-gds-connector/tree/master/examples).
diff --git a/content/influxdb/v2.2/tools/grafana.md b/content/influxdb/v2.2/tools/grafana.md
new file mode 100644
index 000000000..04cf6cd78
--- /dev/null
+++ b/content/influxdb/v2.2/tools/grafana.md
@@ -0,0 +1,256 @@
+---
+title: Use Grafana with InfluxDB OSS
+description: >
+  Use [Grafana](https://grafana.com/) to visualize data from your **InfluxDB** instance.
+menu:
+  influxdb_2_2:
+    name: Use Grafana
+    parent: Tools & integrations
+weight: 104
+influxdb/v2.2/tags: [grafana]
+aliases:
+  - /influxdb/v2.2/visualize-data/other-tools/grafana/
+related:
+  - https://grafana.com/docs/, Grafana documentation
+  - /influxdb/v2.2/query-data/get-started/
+---
+
+Use [Grafana](https://grafana.com/) or [Grafana Cloud](https://grafana.com/products/cloud/)
+to visualize data from your **InfluxDB** instance.
+
+{{% note %}}
+The instructions in this guide require **Grafana Cloud** or **Grafana v7.1+**.
+{{% /note %}}
+
+1. [Start InfluxDB OSS {{< current-version >}}](/influxdb/v2.2/install/#start-influxdb).
+2. [Sign up for Grafana Cloud](https://grafana.com/products/cloud/) or
+   [download and install Grafana](https://grafana.com/grafana/download).
+3. Visit your **Grafana Cloud user interface** (UI) or, if running Grafana locally,
+   [start Grafana](https://grafana.com/docs/grafana/latest/installation/) and visit
+   `http://localhost:3000` in your browser.
+4. In the left navigation of the Grafana UI, hover over the gear
+   icon to expand the **Configuration** section. Click **Data Sources**.
+5. Click **Add data source**.
+6. Select **InfluxDB** from the list of available data sources.
+7. On the **Data Source configuration page**, enter a **name** for your InfluxDB data source.
+8. Under **Query Language**, select one of the following:
+
+{{< tabs-wrapper >}}
+{{% tabs %}}
+[Flux](#)                 
+[InfluxQL](#)
+{{% /tabs %}}
+{{% tab-content %}}
+## Configure Grafana to use Flux
+
+With **Flux** selected as the query language in your InfluxDB data source,
+configure your InfluxDB connection:
+
+1. Under **Connection**, enter the following:
+
+    - **URL**: Your [InfluxDB URL](/influxdb/v2.2/reference/urls/).
+
+        ```sh
+        http://localhost:8086/
+        ```
+
+    - **Organization**: Your InfluxDB [organization name **or** ID](/influxdb/v2.2/organizations/view-orgs/).
+    - **Token**: Your InfluxDB [API token](/influxdb/v2.2/security/tokens/).
+    - **Default Bucket**: The default [bucket](/influxdb/v2.2/organizations/buckets/) to use in Flux queries.
+    - **Min time interval**: The [Grafana minimum time interval](https://grafana.com/docs/grafana/latest/features/datasources/influxdb/#min-time-interval).
+
+    {{< img-hd src="/img/influxdb/2-0-tools-grafana.png" />}}
+
+2. Click **Save & Test**. Grafana attempts to connect to the InfluxDB {{< current-version >}} datasource
+   and returns the results of the test.
+{{% /tab-content %}}
+<!----------------------------- END FLUX CONTENT ----------------------------->
+<!-------------------------- BEGIN INFLUXQL CONTENT -------------------------->
+{{% tab-content %}}
+
+## Configure Grafana to use InfluxQL
+
+To query InfluxDB OSS {{< current-version >}} with InfluxQL, find your use case below, and then complete the instructions to configure Grafana:
+
+- [Installed a new InfluxDB {{< current-version >}} instance](#installed-a-new-influxdb-instance)
+- [Upgraded from InfluxDB 1.x to {{< current-version >}} (following the official upgrade)](#upgraded-from-influxdb-1x-to-2x)
+- [Manually migrated from InfluxDB 1.x to {{< current-version >}}](#manually-migrated-from-influxdb-1x-to-2x)
+
+### Installed a new InfluxDB instance
+To configure Grafana to use InfluxQL with a new install of InfluxDB {{< current-version >}}, do the following:
+
+1. [Authenticate with InfluxDB {{< current-version >}} tokens](/influxdb/v2.2/security/tokens/).
+2. [Manually create DBRP mappings](#view-and-create-influxdb-dbrp-mappings).
+
+### Upgraded from InfluxDB 1.x to 2.x
+To configure Grafana to use InfluxQL when you've upgraded from InfluxDB 1.x to
+InfluxDB {{< current-version >}} (following an [official upgrade guide](/influxdb/v2.2/upgrade/v1-to-v2/)):
+
+1. Authenticate using the _non-admin_ [v1 compatible authentication credentials](#view-and-create-influxdb-v1-authorizations)
+   created during the upgrade process.
+2. Use the DBRP mappings InfluxDB automatically created in the upgrade process (no action necessary).
+
+### Manually migrated from InfluxDB 1.x to 2.x
+To configure Grafana to use InfluxQL when you've manually migrated from InfluxDB
+1.x to InfluxDB {{< current-version >}}, do the following:
+
+1. If your InfluxDB 1.x instance required authentication,
+   [create v1 compatible authentication credentials](#view-and-create-influxdb-v1-authorizations)
+   to match your previous 1.x username and password.
+   Otherwise, use [InfluxDB v2 token authentication](/influxdb/v2.2/security/tokens/).
+2. [Manually create DBRP mappings](#view-and-create-influxdb-dbrp-mappings).
+
+{{< expand-wrapper >}}
+{{% expand "View and create InfluxDB v1 authorizations" %}}
+
+InfluxDB OSS {{< current-version >}} provides a 1.x compatible authentication API that lets you
+authenticate with a username and password like InfluxDB 1.x
+_(separate from the credentials used to log into the InfluxDB user interface)_.
+
+#### View existing v1 authorizations
+Use the [`influx v1 auth list`](/influxdb/v2.2/reference/cli/influx/v1/auth/list/)
+to list existing InfluxDB v1 compatible authorizations.
+
+```sh
+influx v1 auth list
+```
+
+#### Create a v1 authorization
+Use the [`influx v1 auth create` command](/influxdb/v2.2/reference/cli/influx/v1/auth/create/)
+to grant read/write permissions to specific buckets. Provide the following:
+
+- [bucket IDs](/influxdb/v2.2/organizations/buckets/view-buckets/) to grant read
+  or write permissions to
+- new username
+- new password _(when prompted)_
+
+<!--  -->
+```sh
+influx v1 auth create \
+  --read-bucket 00xX00o0X001 \
+  --write-bucket 00xX00o0X001 \
+  --username example-user
+```
+{{% /expand %}}
+{{< expand "View and create InfluxDB DBRP mappings" >}}
+
+When using InfluxQL to query InfluxDB, the query must specify a database and a retention policy.
+InfluxDB DBRP mappings associate database and retention policy combinations with
+InfluxDB {{< current-version >}} [buckets](/influxdb/v2.2/reference/glossary/#bucket).
+
+DBRP mappings do not affect the retention period of the target bucket.
+These mappings allow queries following InfluxDB 1.x conventions to successfully
+query InfluxDB {{< current-version >}} buckets.
+
+#### View existing DBRP mappings
+Use the [`influx v1 dbrp list`](/influxdb/v2.2/reference/cli/influx/v1/dbrp/list/)
+to list existing DBRP mappings.
+
+```sh
+influx v1 dbrp list
+```
+
+#### Create a DBRP mapping
+Use the [`influx v1 dbrp create` command](/influxdb/v2.2/reference/cli/influx/v1/dbrp/create/)
+command to create a DBRP mapping.
+Provide the following:
+
+- database name
+- retention policy name _(not retention period)_
+- [bucket ID](/influxdb/v2.2/organizations/buckets/view-buckets/)
+- _(optional)_ `--default` flag if you want the retention policy to be the default retention
+  policy for the specified database
+
+#### Examples
+
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[DB with one RP](#)
+[DB with multiple RPs](#)
+{{% /code-tabs %}}
+{{< code-tab-content >}}
+```sh
+influx v1 dbrp create \
+  --db example-db \
+  --rp example-rp \
+  --bucket-id 00xX00o0X001 \
+  --default
+```
+{{< /code-tab-content >}}
+{{< code-tab-content >}}
+```sh
+# Create telegraf/autogen DBRP mapping with autogen
+# as the default RP for the telegraf DB
+
+influx v1 dbrp create \
+  --db telegraf \
+  --rp autogen \
+  --bucket-id 00xX00o0X001 \
+  --default
+
+# Create telegraf/downsampled-daily DBRP mapping that
+# writes to a different bucket
+
+influx v1 dbrp create \
+  --db telegraf \
+  --rp downsampled-daily \
+  --bucket-id 00xX00o0X002
+```
+{{< /code-tab-content >}}
+{{< /code-tabs-wrapper >}}
+
+_For more information about DBRP mapping, see [Database and retention policy mapping](/influxdb/v2.2/reference/api/influxdb-1x/dbrp/)._
+{{< /expand >}}
+{{< /expand-wrapper >}}
+
+### Configure your InfluxDB connection
+With **InfluxQL** selected as the query language in your InfluxDB data source settings:
+
+1. Under **HTTP**, enter the following:
+
+    - **URL**: Your [InfluxDB URL](/influxdb/v2.2/reference/urls/).
+
+        ```sh
+        http://localhost:8086/
+        ```
+    - **Access**: Server (default)
+
+2. Configure InfluxDB authentication:
+
+    - ##### Token authentication
+
+        Under **Custom HTTP Headers**, select **Add Header**. Provide your InfluxDB API token:
+
+        - **Header**: Enter `Authorization`
+        - **Value**: Use the `Token` schema and provide your [InfluxDB API token](/influxdb/v2.2/security/tokens/).
+          For example:
+
+          ```
+          Token y0uR5uP3rSecr3tT0k3n
+          ```
+
+    - ##### Authenticate with username and password
+
+        Under **InfluxDB Details**, do the following:
+
+        - **Database**: Enter the database name [mapped to your InfluxDB {{< current-version >}} bucket](#view-and-create-influxdb-dbrp-mappings)
+        - **User**: Enter the username associated with your [InfluxDB 1.x compatibility authorization](#view-and-create-influxdb-v1-authorizations)
+        - **Password**: Enter the password associated with your [InfluxDB 1.x compatibility authorization](#view-and-create-influxdb-dbrp-mappings)
+        - **HTTP Method**: Select **GET**
+
+        <!--  -->
+        {{< img-hd src="/img/influxdb/2-0-tools-grafana-influxql.png" />}}
+
+3. Click **Save & Test**. Grafana attempts to connect to the InfluxDB {{< current-version >}} data source
+   and returns the results of the test.
+{{% /tab-content %}}
+<!--------------------------- END INFLUXQL CONTENT --------------------------->
+{{< /tabs-wrapper >}}
+
+## Query and visualize data
+
+With your InfluxDB connection configured, use Grafana and Flux to query and
+visualize time series data stored in your **InfluxDB** instance.
+
+For more information about using Grafana, see the [Grafana documentation](https://grafana.com/docs/).
+If you're just learning Flux, see [Get started with Flux](/{{< latest "flux" >}}/get-started/).
diff --git a/content/influxdb/v2.2/tools/influx-cli.md b/content/influxdb/v2.2/tools/influx-cli.md
new file mode 100644
index 000000000..555b60284
--- /dev/null
+++ b/content/influxdb/v2.2/tools/influx-cli.md
@@ -0,0 +1,232 @@
+---
+title: Install and use the influx CLI
+description:
+  Use the `influx` and `influxd` command line interfaces to interact with and
+  manage InfluxDB.
+menu:
+  influxdb_2_2:
+    name: Use the influx CLI
+    parent: Tools & integrations
+    identifier: influx-cli-task-based
+weight: 101
+influxdb/v2.2/tags: [cli]
+aliases:
+  - /influxdb/v2.2/tools/clis/
+related:
+  - /influxdb/v2.2/reference/cli/influx/
+---
+
+Use the `influx` CLI to interact with and manage your
+InfluxDB {{% cloud-only %}}Cloud{{% /cloud-only %}} instance.
+Write and query data, generate InfluxDB templates, export data, and more.
+
+{{% oss-only %}}
+
+{{% note %}}
+The [`influx` CLI](/influxdb/v2.2/reference/cli/influx) is packaged and versioned
+separately from the InfluxDB server (`influxd`).
+{{% /note %}}
+
+{{% /oss-only %}}
+
+- [Install the influx CLI](#install-the-influx-cli)
+- [Set up the influx CLI](#set-up-the-influx-cli)
+- [Use influx CLI commands](#use-influx-cli-commands)
+
+## Install the influx CLI
+
+{{< tabs-wrapper >}}
+{{% tabs %}}
+[macOS](#)
+[Linux](#)
+[Windows](#)
+{{% /tabs %}}
+
+<!-------------------------------- BEGIN macOS -------------------------------->
+{{% tab-content %}}
+
+Do one of the following:
+
+- [Use Homebrew](#use-homebrew)
+- [Manually download and install](#manually-download-and-install)
+
+### Use Homebrew
+```sh
+brew install influxdb-cli
+```
+
+{{% oss-only %}}
+
+{{% note %}}
+If you used Homebrew to install **InfluxDB v{{< current-version >}}**, the `influxdb-cli`
+formula was downloaded as a dependency and should already be installed.
+If installed, `influxdb-cli` will appear in the output of the following command:
+
+```sh
+brew list | grep influxdb-cli
+```
+{{% /note %}}
+
+{{% /oss-only %}}
+
+### Manually download and install
+
+1. **Download the `influx` CLI package.**
+
+    <a class="btn download" href="https://dl.influxdata.com/influxdb/releases/influxdb2-client-{{< latest-patch cli=true >}}-darwin-amd64.tar.gz" download>influx CLI v{{< latest-patch cli=true >}} (macOS)</a>
+
+2. **Unpackage the downloaded package.**
+
+    Do one of the following:
+    
+    - Double-click the downloaded package file in **Finder**.
+    - Run the following command in a macOS command prompt application such
+    **Terminal** or **[iTerm2](https://www.iterm2.com/)**:
+
+        ```sh
+        # Unpackage contents to the current working directory
+        tar zxvf ~/Downloads/influxdb2-client-{{< latest-patch cli=true >}}-darwin-amd64.tar.gz
+        ```
+
+3. **(Optional) Place the binary in your `$PATH`.**
+
+    ```sh
+    # (Optional) Copy the influx binary to your $PATH
+    sudo cp ~/Downloads/influxdb2-client-{{< latest-patch cli=true >}}-darwin-amd64/influx /usr/local/bin/
+    ```
+
+    If you do not move the `influx` binary into your `$PATH`, prefix the executable
+    `./` to run it in place.
+
+4. **(macOS Catalina and newer) Authorize the `influx` binary.**
+
+    macOS requires downloaded binaries to be signed by registered Apple developers.
+    When you first attempt to run `influx`, macOS will prevent it from running.
+    To authorize the `influx` binary:
+
+    1. Attempt to run an `influx` command.
+    2. Open **System Preferences** and click **Security & Privacy**.
+    3. Under the **General** tab, there is a message about `influx` being blocked.
+      Click **Open Anyway**.
+
+{{% /tab-content %}}
+<!--------------------------------- END macOS --------------------------------->
+
+<!-------------------------------- BEGIN Linux -------------------------------->
+{{% tab-content %}}
+
+1. **Download the influx CLI package.**
+
+    Download the `influx` CLI package [from your browser](#download-from-your-browser)
+    or [from the command line](#download-from-the-command-line).
+
+    #### Download from your browser
+
+    <a class="btn download" href="https://dl.influxdata.com/influxdb/releases/influxdb2-client-{{< latest-patch cli=true >}}-linux-amd64.tar.gz" download >influx CLI v{{< latest-patch cli=true >}} (amd64)</a>
+    <a class="btn download" href="https://dl.influxdata.com/influxdb/releases/influxdb2-client-{{< latest-patch cli=true >}}-linux-arm64.tar.gz" download >influx CLI v{{< latest-patch cli=true >}} (arm)</a>
+
+    #### Download from the command line
+
+    ```sh
+    # amd64
+    wget https://dl.influxdata.com/influxdb/releases/influxdb2-client-{{< latest-patch cli=true >}}-linux-amd64.tar.gz
+
+    # arm
+    wget https://dl.influxdata.com/influxdb/releases/influxdb2-client-{{< latest-patch cli=true >}}-linux-arm64.tar.gz
+    ```
+
+4. **Unpackage the downloaded package.**
+
+    _**Note:** The following commands are examples. Adjust the filenames, paths, and utilities if necessary._
+
+    ```sh
+    # amd64
+    tar xvzf path/to/influxdb2-client-{{< latest-patch cli=true >}}-linux-amd64.tar.gz
+
+    # arm
+    tar xvzf path/to/influxdb2-client-{{< latest-patch cli=true >}}-linux-arm64.tar.gz
+    ```
+
+3. **(Optional) Place the unpackaged `influx` executable in your system `$PATH`.**
+
+    ```sh
+    # amd64
+    sudo cp influxdb2-client-{{< latest-patch cli=true >}}-linux-amd64/influx /usr/local/bin/
+
+    # arm
+    sudo cp influxdb2-client-{{< latest-patch cli=true >}}-linux-arm64/influx /usr/local/bin/
+    ```
+
+    If you do not move the `influx` binary into your `$PATH`, prefix the executable
+    `./` to run it in place.
+
+{{% /tab-content %}}
+<!--------------------------------- END Linux --------------------------------->
+
+<!-------------------------------- BEGIN Windows -------------------------------->
+{{% tab-content %}}
+
+1. **Download the `influx` CLI package.**
+
+    <a class="btn download" href="https://dl.influxdata.com/influxdb/releases/influxdb2-client-{{< latest-patch cli=true >}}-windows-amd64.zip" download>influx CLI v{{< latest-patch cli=true >}} (Windows)</a>
+
+2. **Expand the downloaded archive.**
+  
+    Expand the downloaded archive into `C:\Program Files\InfluxData\` and rename it if desired.
+
+    ```powershell
+    > Expand-Archive .\influxdb2-client-{{< latest-patch cli=true >}}-windows-amd64.zip -DestinationPath 'C:\Program Files\InfluxData\'
+    > mv 'C:\Program Files\InfluxData\influxdb2-client-{{< latest-patch cli=true >}}-windows-amd64' 'C:\Program Files\InfluxData\influx'
+    ```
+
+3. **Grant network access to the `influx` CLI.**
+
+    When using the `influx` CLI for the first time, **Windows Defender** displays
+    the following message:
+
+    > Windows Defender Firewall has blocked some features of this app.
+
+    To grant the `influx` CLI the required access, do the following:
+
+    1. Select **Private networks, such as my home or work network**.
+    2. Click **Allow access**.
+
+{{% /tab-content %}}
+<!--------------------------------- END Windows --------------------------------->
+{{< /tabs-wrapper >}}
+
+## Set up the influx CLI
+
+- [Provide required authentication credentials](#provide-required-authentication-credentials)
+- [Enable shell completion (Optional)](#enable-shell-completion-optional)
+
+### Provide required authentication credentials
+To avoid having to pass your InfluxDB **host**, **API token**, and **organization**
+with each command, store them in an `influx` CLI configuration (config).
+`influx` commands that require these credentials automatically retrieve these
+credentials from the active config.
+
+Use the [`influx config create` command](/influxdb/v2.2/reference/cli/influx/config/create/)
+to create an `influx` CLI config and set it as active:
+
+```sh
+influx config create --config-name <config-name> \
+  --host-url http://localhost:8086 \
+  --org <your-org> \
+  --token <your-auth-token> \
+  --active
+```
+
+For more information about managing CLI configurations, see the
+[`influx config` documentation](/influxdb/v2.2/reference/cli/influx/config/).
+
+For instructions on how to create API tokens, see [Create a token](/influxdb/v2.2/security/tokens/create-token/).
+
+### Enable shell completion (Optional)
+
+To install `influx` shell completion scripts, see
+[`influx completion`](/influxdb/v2.2/reference/cli/influx/completion/#install-completion-scripts).
+
+## Use influx CLI commands
+_For information about `influx` CLI commands, see the
+[`influx` CLI reference documentation](/influxdb/v2.2/reference/cli/influx/)._
diff --git a/content/influxdb/v2.2/tools/kapacitor.md b/content/influxdb/v2.2/tools/kapacitor.md
new file mode 100644
index 000000000..5d4adbade
--- /dev/null
+++ b/content/influxdb/v2.2/tools/kapacitor.md
@@ -0,0 +1,139 @@
+---
+title: Use Kapacitor with InfluxDB OSS
+description: >
+  [Kapacitor](/kapacitor/) is a data processing framework that makes it easy to
+  create alerts, run ETL (Extract, Transform and Load) jobs and detect anomalies.
+  Use Kapacitor with **InfluxDB OSS 2.x**.
+menu:
+  influxdb_2_2:
+    name: Use Kapacitor
+    parent: Tools & integrations
+weight: 102
+related:
+  - /{{< latest "kapacitor" >}}/
+---
+
+[Kapacitor](/{{< latest "kapacitor" >}}/) is a data processing framework that makes
+it easy to create alerts, run ETL jobs and detect anomalies.
+Kapacitor interacts with **InfluxDB Cloud** and **InfluxDB OSS {{< current-version >}}** using the
+[InfluxDB 1.x compatibility API](/influxdb/v2.2/reference/api/influxdb-1x/), so
+you can continue using Kapacitor without having to migrate libraries of TICKscripts
+to InfluxDB tasks.
+
+{{% note %}}
+#### Support for stream tasks
+InfluxDB Cloud and InfluxDB OSS {{< current-version >}} do not have subscription APIs and
+**do not support Kapacitor stream tasks**, but you can continue to use stream
+tasks by writing data directly to Kapacitor.
+For more information, see [below](#use-kapacitor-stream-tasks).
+{{% /note %}}
+
+#### On this page
+- [Configure Kapacitor to connect to InfluxDB](#configure-kapacitor-to-connect-to-influxdb)
+- [Use Kapacitor batch tasks](#use-kapacitor-batch-tasks)
+- [Use Kapacitor stream tasks](#use-kapacitor-stream-tasks)
+- [Write back to InfluxDB](#write-back-to-influxdb)
+
+## Configure Kapacitor to connect to InfluxDB
+To connect Kapacitor to InfluxDB Cloud or InfluxDB OSS {{< current-version >}}, update the `[[influxdb]]`
+section(s) of your [Kapacitor configuration file](/{{< latest "kapacitor" >}}/administration/configuration/#kapacitor-configuration-file):
+
+- [Specify your InfluxDB URL](#specify-your-influxdb-url)
+- [Provide InfluxDB authentication credentials](#provide-influxdb-authentication-credentials)
+- [Disable InfluxDB subcriptions](#disable-influxdb-subscriptions)
+
+### Specify your InfluxDB URL
+Provide your InfluxDB URL in the `[[influxdb]].urls` configuration option.
+For more information, see [InfluxDB Cloud regions](/influxdb/cloud/reference/regions/)
+or [InfluxDB OSS URLs](/influxdb/v2.2/reference/urls/).
+
+```toml
+[[influxdb]]
+  # ...
+  urls = ["http://localhost:8086"]
+```
+
+### Provide InfluxDB authentication credentials
+InfluxDB Cloud and InfluxDB OSS {{< current-version >}} require authentication.
+Provide the following credentials in your `[[influxdb]].username` and `[[influxdb]].password`
+configuration options:
+
+- **username:** InfluxDB username
+- **password:** InfluxDB [API token](/influxdb/v2.2/security/tokens/)
+
+```toml
+[[influxdb]]
+  # ...
+  username = "influxdb-username"
+  password = "influxdb-token"
+```
+
+{{% warn %}}
+Kapacitor is subject to InfluxDB token permission restrictions.
+To query or write to an InfluxDB bucket, the InfluxDB token must have read and/or
+write permissions for the target bucket.
+For information about token permissions, see [Create a token](/influxdb/v2.2/security/tokens/create-token/).
+{{% /warn %}}
+
+### Disable InfluxDB subscriptions
+InfluxDB Cloud and InfluxDB OSS {{< current-version >}} do not have subscriptions APIs.
+Set the `[[influxdb]].disable-subscriptions`to `true` to disable InfluxDB subscriptions.
+
+```toml
+[[influxdb]]
+  # ...
+  disable-subscriptions = true
+```
+
+## Use Kapacitor batch tasks
+Kapacitor batch tasks use the `query` endpoint of the 1.x compatibility API
+and require no change to use with InfluxDB Cloud and InfluxDB OSS.
+For information about writing back to InfluxDB in Kapacitor tasks,
+see [Write back to InfluxDB](#write-back-to-influxdb) below.
+
+## Use Kapacitor stream tasks
+InfluxDB Cloud and OSS {{< current-version >}} do not have subscription APIs and do not support Kapacitor stream tasks directly.
+To use Kapacitor stream tasks, write data directly to Kapacitor using the [Kapcitior `write` API](/{{< latest "kapacitor" >}}/working/api/#writing-data).
+
+We recommend using [Telegraf InfluxDB output plugin](/{{< latest "telegraf" >}}/plugins/#output-influxdb)
+to write data to both InfluxDB Cloud or OSS and Kapacitor.
+The following example Telegraf configuration writes data to both InfluxDB and Kapacitor:
+
+##### Example Telegraf configuration
+```toml
+# Write to Kapacitor
+[[outputs.influxdb]]
+  urls = ["http://localhost:9092"]
+  database = "example-db"
+  retention_policy = "example-rp"
+
+# Write to InfluxDB Cloud or OSS
+[[outputs.influxdb]]
+  urls = ["http://localhost:8086"]
+  database = "example-db"
+  retention_policy = "example-rp"
+  username = "influxdb-username"
+  password = "influxdb-token"
+```
+
+## Write back to InfluxDB
+If using the Kapacitor `InfluxDBOut` node to write data to InfluxDB Cloud or OSS {{< current-version >}},
+InfluxDB maps the specified database and retention policy to a corresponding bucket.
+You can also manually map database/retention policy combinations (DBRPs) to buckets.
+For more information, see [DBRP mapping](/influxdb/v2.2/reference/api/influxdb-1x/dbrp/)
+and [Map unmapped buckets](/influxdb/v2.2/query-data/influxql/#map-unmapped-buckets).
+
+The following example TICKscript writes to the `my-db/my-rp` bucket in
+InfluxDB Cloud or InfluxDB OSS {{< current-version >}}.
+
+```js
+batch
+  |query('SELECT errors / total AS error_percent from requests')
+  // Write the transformed data to InfluxDB
+  |influxDBOut()
+    .database('my-db')
+    .retentionPolicy('my-rp')
+    .measurement('errors')
+    .tag('kapacitor', 'true')
+    .tag('version', '0.2')
+```
diff --git a/content/influxdb/v2.2/tools/repl.md b/content/influxdb/v2.2/tools/repl.md
new file mode 100644
index 000000000..2ce7955ea
--- /dev/null
+++ b/content/influxdb/v2.2/tools/repl.md
@@ -0,0 +1,55 @@
+---
+title: Use the Interactive Flux REPL
+description: >
+  Use the Flux REPL (Read–Eval–Print Loop) to execute Flux scripts and interact
+  with InfluxDB and other data sources.
+influxdb/v2.2/tags: [flux]
+menu:
+  influxdb_2_2:
+    name: Use the Flux REPL
+    parent: Tools & integrations
+weight: 103
+---
+
+Use the Flux REPL (Read–Eval–Print Loop) to execute Flux scripts and interact with InfluxDB and other data sources.
+[Build the REPL](#build-the-repl) from the Flux source code.
+
+## Build the REPL
+
+To use the Flux REPL, build it from source using the [Flux repository](https://github.com/influxdata/flux/).
+For instructions, see the [Flux repository README](https://github.com/influxdata/flux/#requirements).
+
+## Use the REPL
+
+- [Open a REPL session](#open-a-repl-session)
+- [Query data from InfluxDB](#query-data-from-influxdb)
+- [Multi-line entries](#multi-line-entries)
+- [Exit the REPL](#exit-the-repl)
+
+### Open a REPL session
+To open a new REPL session, run:
+
+```sh
+./flux repl
+```
+
+### Query data from InfluxDB
+To query data from InfluxDB (local or remote), provide the host, organization, and token parameters
+to the [`from()` function](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/from/).
+
+```js
+from(
+    bucket: "example-bucket",
+    host: "http://localhost:8086",
+    org: "example-org",
+    token: "My5uP3rS3cRetT0k3n",
+)
+```
+
+### Multi-line entries
+Multi-line scripts like the example above work when pasted into the REPL.
+Pasting newlines from the clipboard is allowed.
+However, you cannot enter newline characters directly from the keyboard.
+
+### Exit the REPL
+Exit the REPL by pressing **Control + D**.
diff --git a/content/influxdb/v2.2/upgrade/_index.md b/content/influxdb/v2.2/upgrade/_index.md
new file mode 100644
index 000000000..c6e407dbe
--- /dev/null
+++ b/content/influxdb/v2.2/upgrade/_index.md
@@ -0,0 +1,12 @@
+---
+title: Upgrade InfluxDB
+description: >
+  Upgrade your version of InfluxDB
+menu: influxdb_2_2
+weight: 3
+aliases:
+  - /influxdb/v2.2/reference/upgrading/
+influxdb/v2.2/tags: [upgrade]
+---
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/upgrade/downgrade.md b/content/influxdb/v2.2/upgrade/downgrade.md
new file mode 100644
index 000000000..930d933aa
--- /dev/null
+++ b/content/influxdb/v2.2/upgrade/downgrade.md
@@ -0,0 +1,42 @@
+---
+title: Downgrade InfluxDB
+description: >
+  To downgrade from InfluxDB {{< current-version >}} to a previous 2.x version,
+  use the `influxd downgrade` command to downgrade the metadata schema used by
+  `influxd` to match the metadata schema of a older release.
+menu:
+  influxdb_2_2:
+    parent: Upgrade InfluxDB
+    name: Downgrade InfluxDB
+weight: 12
+related:
+  - /influxdb/v2.2/reference/cli/influxd/downgrade/
+---
+
+To downgrade from InfluxDB {{< current-version >}} to a previous 2.x version,
+use the `influxd downgrade` command to downgrade the metadata schema used by
+`influxd` to match the metadata schema of a older release.
+
+InfluxDB does not guarantee backwards-compatibility with older releases in its embedded metadata stores.
+Attempting to start an older `influxd` binary with a BoltDB or SQLite file that has
+been migrated to a newer schema will result in a startup error similar to:
+
+```
+Error: up: reading migrations: migration "...": migration specification not found
+```
+
+**To downgrade from InfluxDB {{< current-version >}} to a previous 2.x version**:
+
+1.  Run `influxd downgrade` using the **{{< current-version >}} `influxd` binary**.
+    Specify the previous InfluxDB version to downgrade to.
+    For example, to downgrade to InfluxDB 2.0: 
+
+    ```sh
+    influxd downgrade 2.0
+    ```
+
+2. Install the **earlier version** of InfluxDB:
+
+    {{< influxdb/install-old-versions >}}
+
+3. Start InfluxDB with the **earlier versioned `influxd` binary**.
diff --git a/content/influxdb/v2.2/upgrade/v1-to-v2/_index.md b/content/influxdb/v2.2/upgrade/v1-to-v2/_index.md
new file mode 100644
index 000000000..bdccf1f5c
--- /dev/null
+++ b/content/influxdb/v2.2/upgrade/v1-to-v2/_index.md
@@ -0,0 +1,28 @@
+---
+title: Upgrade from InfluxDB 1.x to 2.2
+description: >
+  Explore different methods for upgrading from InfluxDB 1.x to InfluxDB 2.2 and
+  choose the best one for your use case.
+menu:
+  influxdb_2_2:
+    parent: Upgrade InfluxDB
+    name: InfluxDB 1.x to 2.2
+weight: 11
+---
+
+Explore different methods for upgrading from InfluxDB 1.x to InfluxDB {{< current-version >}} and
+determine which best suits your use case.
+Consider the following:
+
+#### Do you want to migrate all your time series data?
+[Automatically upgrade to InfluxDB {{< current-version >}}](/influxdb/v2.2/upgrade/v1-to-v2/automatic-upgrade/).
+
+#### Do you want to selectively migrate your time series data?
+[Manually upgrade to InfluxDB {{< current-version >}}](/influxdb/v2.2/upgrade/v1-to-v2/manual-upgrade/).
+
+#### Are you using Docker?
+[Upgrade to the 2.x Docker image](/influxdb/v2.2/upgrade/v1-to-v2/docker/).
+
+#### Are you using continuous queries (CQs)?
+After you upgrade (automatically, manually, or using Docker),
+[migrate your 1.x CQs to InfluxDB {{< current-version >}} tasks](/influxdb/v2.2/upgrade/v1-to-v2/migrate-cqs/).
diff --git a/content/influxdb/v2.2/upgrade/v1-to-v2/automatic-upgrade.md b/content/influxdb/v2.2/upgrade/v1-to-v2/automatic-upgrade.md
new file mode 100644
index 000000000..4f91345fe
--- /dev/null
+++ b/content/influxdb/v2.2/upgrade/v1-to-v2/automatic-upgrade.md
@@ -0,0 +1,266 @@
+---
+title: Automatically upgrade from InfluxDB 1.x to 2.1
+list_title: Automatically upgrade from 1.x to 2.1
+description: >
+  Use the `influx upgrade` tool to automatically upgrade from InfluxDB 1.x to InfluxDB 2.1.
+menu:
+  influxdb_2_2:
+    parent: InfluxDB 1.x to 2.2
+    name: Automatically upgrade
+weight: 10
+aliases:
+  - /influxdb/v2.2/reference/upgrading/influxd-upgrade-guide/
+related:
+  - /influxdb/v2.2/reference/cli/influxd/upgrade/
+  - /influxdb/v2.2/upgrade/v1-to-v2/manual-upgrade/
+  - /influxdb/v2.2/upgrade/v1-to-v2/docker/
+---
+
+Use the `influxd upgrade` command to upgrade InfluxDB 1.x to InfluxDB {{< current-version >}}.
+The `upgrade` command provides an in-place upgrade from InfluxDB 1.x to InfluxDB {{< current-version >}}.
+
+Specifically, the upgrade process does the following:
+
+1. Reads the existing InfluxDB 1.x configuration file and generates an equivalent InfluxDB {{< current-version >}} configuration file at `~/.influxdbv2/config.toml` or at a custom path specified with the `--v2-config-path` flag.
+2. Upgrades metadata and storage engine paths to `~/.influxdbv2/meta` and `~/.influxdbv2/engine`, respectively (unless otherwise specified).
+3. Writes existing data and write ahead log (WAL) files into InfluxDB {{< current-version >}} [buckets](/influxdb/v2.2/reference/glossary/#bucket).
+4. Creates [database and retention policy (DBRP) mappings](/influxdb/v2.2/reference/api/influxdb-1x/dbrp/) required to query data with InfluxQL.
+5. Reads existing metadata and migrates non-admin users, passwords, and permissions into a 1.x authorization–compatible store within `~/influxdbv2/influxdb.bolt`.
+
+When starting InfluxDB {{< current-version >}} after running `influxdb upgrade`, InfluxDB must build a new time series index (TSI).
+Depending on the volume of data present, this may take some time.
+
+## Important considerations before you begin
+
+Before upgrading to InfluxDB {{< current-version >}}, consider the following guidelines.
+Some or all might apply to your specific installation and use case.
+The sections below contain our recommendations for addressing possible gaps in the upgrade process.
+Consider whether you need to address any of the following before upgrading.
+
+- [Available operating system, container, and platform support](#available-operating-system-container-and-platform-support)
+- [Continuous queries](#continuous-queries)
+- [Supported protocols](#supported-protocols)
+- [Kapacitor](#kapacitor)
+- [User migration](#user-migration)
+- [Dashboards](#dashboards)
+- [Other data](#other-data)
+- [Secure by default](#secure-by-default)
+- [`inmem` indexing option](#in-memory-indexing-option)
+
+### Available operating system, container, and platform support
+
+InfluxDB {{< current-version >}} is currently available for macOS, Linux, and Windows.
+
+{{% note %}}
+InfluxDB {{< current-version >}} requires 64-bit operating systems.
+{{% /note %}}
+
+### Continuous queries
+
+Continuous queries are replaced by **tasks** in InfluxDB {{< current-version >}}.
+By default, `influxd upgrade` writes all continuous queries to `~/continuous_queries.txt`.
+To convert continuous queries to InfluxDB tasks, see
+[Migrate continuous queries to tasks](/influxdb/v2.2/upgrade/v1-to-v2/migrate-cqs/).
+
+### Supported protocols
+
+InfluxDB {{< current-version >}} doesn't directly support the alternate write protocols
+[supported in InfluxDB 1.x](/influxdb/v1.8/supported_protocols/)
+(CollectD, Graphite, OpenTSDB, Prometheus, UDP).
+Use [Telegraf](/{{< latest "telegraf" >}}/) to translate these protocols to line protocol.
+
+### Kapacitor
+
+You can continue to use Kapacitor with InfluxDB OSS {{< current-version >}} under the following scenarios:
+
+- Kapacitor Batch-style TICKscripts work with the 1.x read compatible API.
+  Existing Kapacitor user credentials should continue to work using the [1.x compatibility API](/influxdb/v2.2/reference/api/influxdb-1x/).
+- InfluxDB {{< current-version >}} has no subscriptions API and does not support Kapacitor stream tasks.
+  To continue using stream tasks, write data directly to both InfluxDB and Kapacitor.
+  Use **Telegraf** and its [InfluxDB output plugin](/{{< latest "telegraf" >}}/plugins/#output-influxdb)
+  to write to Kapacitor and the [InfluxDB v2 output plugin](/{{< latest "telegraf" >}}/plugins/#output-influxdb_v2) to write to InfluxDB v2.
+
+##### Example Telegraf configuration
+```toml
+# Write to Kapacitor
+[[outputs.influxdb]]
+  urls = ["http://localhost:9092"]
+  database = "example-db"
+  retention_policy = "example-rp"
+
+# Write to InfluxDB {{< current-version >}}
+[[outputs.influxdb]]
+  urls = ["http://localhost:8086"]
+  database = "example-db"
+  retention_policy = "example-rp"
+  username = "v1-auth-username"
+  password = "v1-auth-password"
+```
+
+### User migration
+
+`influxd upgrade` migrates existing 1.x users and their permissions **except** the following users:
+
+- [1.x admin users](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#admin-users)
+- [1.x non-admin users](/{{< latest "influxdb" "v1" >}}/administration/authentication_and_authorization/#non-admin-users)
+  that have not been granted any privileges
+
+{{< expand-wrapper >}}
+{{% expand "Review 1.x user privileges" %}}
+**To review 1.x users with admin privileges**, run the following against your InfluxDB 1.x instance:
+
+```sql
+SHOW USERS
+```
+
+Users with `admin` set to `true` will **not** be migrated.
+
+**To review the specific privileges granted to each 1.x user**, run the following for each user in your InfluxDB 1.x instance:
+
+```sql
+SHOW GRANTS FOR "<username>"
+```
+
+If no grants appear, the user will **not** be migrated.
+{{% /expand %}}
+{{< /expand-wrapper >}}
+
+If using an admin user for visualization or Chronograf administrative functions,
+**create a new read-only user before upgrading**:
+
+##### Create a read-only 1.x user
+```sh
+> CREATE USER <username> WITH PASSWORD '<password>'
+> GRANT READ ON <database> TO "<username>"
+```
+
+InfluxDB {{< current-version >}} only grants admin privileges to the primary user set up during the InfluxDB {{< current-version >}} upgrade.
+This provides you with the opportunity to reassess who to grant admin permissions when setting up InfluxDB {{< current-version >}}.
+
+### Dashboards
+
+You can continue to use your existing dashboards and visualization tools with InfluxDB {{< current-version >}} via the [1.x read compatibility API](/influxdb/v2.2/reference/api/influxdb-1x/).
+The upgrade process creates [DBRP mappings](/influxdb/v2.2/reference/api/influxdb-1x/dbrp/) to ensure existing users can execute InfluxQL queries with the appropriate permissions.
+
+However, if your dashboard tool is configured using a user with admin permissions,
+you will need to create a new read-only user with the appropriate database permissions *before* upgrading.
+This new username and password combination should be used within the data source configurations to continue to provide read-only access to the underlying data.
+
+Ensure your dashboards are all functioning before upgrading.
+
+### Other data
+
+The 1.x `_internal` database is not migrated with the `influxd upgrade` command.
+To collect, store, and monitor similar internal InfluxDB metrics,
+[create an InfluxDB {{< current-version >}} scraper](/influxdb/v2.2/write-data/no-code/scrape-data/manage-scrapers/create-a-scraper/)
+to scrape data from the `/metrics` endpoint and store them in a bucket.
+
+### Secure by default
+
+InfluxDB {{< current-version >}} requires authentication and does not support the InfluxDB 1.x `auth-enabled = false` configuration option.
+
+Before upgrading to {{< current-version >}}, [enable authentication in your InfluxDB 1.x instance](/influxdb/v1.8/administration/authentication_and_authorization/#set-up-authentication)
+and test your credentials to ensure your applications, agents, and visualization tools can connect to InfluxDB.
+
+If you upgrade with `auth-enabled = false`, the upgrade may appear complete,
+but client requests to InfluxDB {{< current-version >}} may be silently ignored (you won't see a notification the request was denied).
+
+### In-memory indexing option
+
+InfluxDB {{< current-version >}} doesn't support [in-memory (`inmem`) indexing](/influxdb/v1.8/administration/config/#in-memory-inmem-index-settings). The following InfluxDB 1.x configuration options associated with `inmem` indexing are ignored in the upgrade process:
+
+- `max-series-per-database`
+- `max-values-per-tag`
+
+### Interactive shell
+
+The InfluxDB 2.x `influx` CLI does not include an interactive shell for executing InfluxQL queries or Flux queries. For information about executing InfluxQL queries, see [Query data with InfluxQL](/influxdb/v2.2/query-data/influxql/). To build an interactive shell to execute Flux queries, [compile and build a command line Flux REPL from source](https://github.com/influxdata/flux/blob/master/README.md#getting-started). 
+
+## Perform the upgrade
+
+If you've considered the [guidance above](#before-you-begin-important-considerations)
+and are ready to proceed, follow these steps to upgrade your InfluxDB 1.x to InfluxDB {{< current-version >}}.
+
+1. [Download InfluxDB OSS {{< current-version >}}](https://portal.influxdata.com/downloads/).
+   Unpackage the InfluxDB binaries and place them in your `$PATH`.
+2. Stop your running InfluxDB 1.x instance.
+   Make a backup copy of all 1.x data before upgrading:
+
+   ```sh
+   cp -R .influxdb/ .influxdb_bak/
+   ```
+3. Use `influxd version` to ensure you are running InfluxDB {{< current-version >}} from the command line.
+   The `influxd upgrade` command is only available in InfluxDB {{< current-version >}}.
+4. If your 1.x configuration file is at the [default location](/influxdb/v1.8/administration/config/#using-the-configuration-file), run:
+    ```sh
+    influxd upgrade
+    ```
+    {{% note %}}
+#### Upgrade `.deb` packages
+When installed from a `.deb` package, InfluxDB 1.x and 2.x run under the `influxdb` user.
+If you've installed both versions from `.deb` packages, run the upgrade command
+as the `influxdb` user:
+
+```sh
+sudo -u influxdb influxd upgrade
+```
+    {{% /note %}}
+    If your 1.x configuration file is not at the default location, run:
+
+    ```sh
+    influxd upgrade --config-file <path to v1 config file>
+    ```
+
+    To store the upgraded {{< current-version >}} configuration file in a custom location, include the `--v2-config-path` flag:
+
+    ```sh
+    influxd upgrade --v2-config-path <destination path for v2 config file>
+    ```
+    
+    
+5. Follow the prompts to set up a new InfluxDB {{< current-version >}} instance.
+
+   ```
+   Welcome to InfluxDB {{< current-version >}} upgrade!
+   Please type your primary username: <your-username>
+
+   Please type your password:
+
+   Please type your password again:
+
+   Please type your primary organization name: <your-org>
+
+   Please type your primary bucket name: <your-bucket>
+
+   Please type your retention period in hours.
+   Or press ENTER for infinite:
+
+   You have entered:
+     Username:          <your-username>
+     Organization:      <your-org>
+     Bucket:            <your-bucket>
+     Retention Period:  infinite
+   Confirm? (y/n): y
+   ```
+
+The output of the upgrade prints to standard output.
+It is also saved (for troubleshooting and debugging) in the current directory to a file called `upgrade.log` located in the home directory of the user running `influxdb upgrade`.
+
+## Post-upgrade
+
+### Verify 1.x users were migrated to {{< current-version >}}
+
+To verify 1.x users were successfully migrated to {{< current-version >}}, run
+[`influx v1 auth list`](/influxdb/v2.2/reference/cli/influx/v1/auth/list/).
+
+#### Add authorizations for external clients
+
+If your InfluxDB 1.x instance **did not have authentication enabled** and the
+`influx v1 auth list` doesn't return any users, external clients connected to
+your 1.x instance will not be able to access InfluxDB {{< current-version >}}, which requires authentication.
+
+**For these external clients to work with InfluxDB {{< current-version >}}:**
+
+1. [Manually create a 1.x-compatible authorization](/influxdb/v2.2/upgrade/v1-to-v2/manual-upgrade/#create-a-1x-compatible-authorization).
+2. Update the client configuration to use the username and password associated
+   with your 1.x-compatible authorization.
diff --git a/content/influxdb/v2.2/upgrade/v1-to-v2/docker.md b/content/influxdb/v2.2/upgrade/v1-to-v2/docker.md
new file mode 100644
index 000000000..e54fa645d
--- /dev/null
+++ b/content/influxdb/v2.2/upgrade/v1-to-v2/docker.md
@@ -0,0 +1,251 @@
+---
+title: Upgrade from InfluxDB 1.x to 2.2 with Docker
+list_title: Upgrade from 1.x to 2.2 with Docker
+description: >
+  Use the automated upgrade process built into the InfluxDB 2.x Docker image to
+  update InfluxDB 1.x Docker deployments to InfluxDB 2.x.
+menu:
+  influxdb_2_2:
+    parent: InfluxDB 1.x to 2.2
+    name: Upgrade with Docker
+weight: 101
+---
+
+Use the automated upgrade process built into the [InfluxDB 2.x Docker image](https://hub.docker.com/_/influxdb)
+to update InfluxDB 1.x Docker deployments to InfluxDB 2.x.
+
+- [Upgrade requirements](#upgrade-requirements)
+- [Minimal upgrade](#minimal-upgrade)
+- [Upgrade with a custom InfluxDB 1.x configuration file](#upgrade-with-a-custom-influxdb-1-x-configuration-file)
+- [Upgrade with custom paths](#upgrade-with-custom-paths)
+
+{{% note %}}
+#### Export continuous queries before upgrading
+The automated upgrade process **does not** migrate InfluxDB 1.x continuous queries (CQs)
+to InfluxDB 2.x tasks (the 2.x equivalent). Export all of your CQs before upgrading to InfluxDB 2.x.
+For information about exporting and migrating CQs to tasks, see
+[Migrate continuous queries to tasks](/influxdb/v2.2/upgrade/v1-to-v2/migrate-cqs/).
+{{% /note %}}
+
+## Upgrade requirements
+InfluxDB 2.x provides a 1.x compatibility API, but expects a different storage layout on disk.
+To account for theses differences, the InfluxDB Docker image migrates
+1.x data and into 2.x-compatible data automatically before booting the `influxd` server.
+
+- [InfluxDB 2.x initialization credentials](#influxdb-2x-initialization-credentials)
+- [File system mounts](#file-system-mounts)
+- [Upgrade initialization mode](#upgrade-initialization-mode)
+
+{{% note %}}
+To ensure InfluxDB reboots post-upgrade without overwriting migrated data,
+the upgrade won't run if an existing boltdb file is found at the
+[configured 2.x configuration path](#file-system-mounts).
+{{% /note %}}
+
+Find more information about the automated InfluxDB upgrade process,
+see [Automatically upgrade from InfluxDB 1.x to {{< current-version >}}](/influxdb/v2.2/upgrade/v1-to-v2/automatic-upgrade/).
+
+### InfluxDB 2.x initialization credentials
+The automated InfluxDB upgrade process bootstraps an initial admin user,
+[organization](/influxdb/v2.2/reference/glossary/#organization), and
+[bucket](/influxdb/v2.2/reference/glossary/#bucket) required by InfluxDB 2.x.
+Set the following [environment variables in your Docker container](https://docs.docker.com/search/?q=environment%20variables)
+to provide setup credentials:
+
+- `DOCKER_INFLUXDB_INIT_USERNAME`: Username to set for the admin user ({{< req >}}).
+- `DOCKER_INFLUXDB_INIT_PASSWORD`: Password to set for the admin user ({{< req >}}).
+- `DOCKER_INFLUXDB_INIT_ORG`: Name to set for the initial organization ({{< req >}}).
+- `DOCKER_INFLUXDB_INIT_BUCKET`: Name to set for the initial bucket ({{< req >}}).
+- `DOCKER_INFLUXDB_INIT_RETENTION`: Duration for the initial bucket's retention period.
+  If not set, the initial bucket will retain data forever.
+- `DOCKER_INFLUXDB_INIT_ADMIN_TOKEN`: API token to associate with the admin user.
+  If not set, InfluxDB automatically generates a token.
+
+### File system mounts
+The InfluxDB upgrade process requires extra volumes to be mounted into the 2.x container.
+Use **environment variables** and **Docker mounts** to specify and configure the
+appropriate mount paths for the following:
+
+- 1.x data on disk
+- Custom 1.x configuration file (if any)
+- 2.x data on disk (`/var/lib/influxdb2`)
+- 2.x configuration directory (`/etc/influxdb2`)
+
+The InfluxDB upgrade process searches for mounted 1.x data and configuration files
+in the following priority order:
+
+1. 1.x configuration file specified by the `DOCKER_INFLUXDB_INIT_UPGRADE_V1_CONFIG` environment variable
+2. 1.x data directory specified by the `DOCKER_INFLUXDB_INIT_UPGRADE_V1_DIR` environment variable
+3. 1.x configuration file mounted at `/etc/influxdb/influxdb.conf`
+4. 1.x data directory mounted at `/var/lib/influxdb`
+
+{{% note %}}
+#### Avoid data loss
+By default, the automated upgrade process generates both data and configuration files
+under `/var/lib/influxdb2` and `/etc/influxdb2`.
+We recommend mounting volumes at both paths to avoid losing data.
+{{% /note %}}
+
+### Upgrade initialization mode
+Set the `DOCKER_INFLUXDB_INIT_MODE` environment variable to `upgrade`.
+
+## Minimal upgrade
+If you're currently running a minimal InfluxDB 1.x deployment similar to:
+
+```sh
+docker run -p 8086:8086 \
+  -v influxdb:/var/lib/influxdb \
+  influxdb:1.8
+```
+
+**To upgrade this minimal deployment to InfluxDB 2.x:**
+
+1.  Stop the running InfluxDB 1.x container.
+2.  Start the InfluxDB container with the following:
+
+    - Volume mount for the InfluxDB 1.x data directory
+    - Volume mount for the InfluxDB 2.x data directory
+    - InfluxDB [initialization mode](#upgrade-initialization-mode) environment variable
+    - InfluxDB [initialization credential](#influxdb-2x-initialization-credentials) environment variables
+    - `influxdb:{{< current-version >}}` Docker image
+
+    ```sh
+    docker run -p 8086:8086 \
+      -v influxdb:/var/lib/influxdb \
+      -v influxdb2:/var/lib/influxdb2 \
+      -e DOCKER_INFLUXDB_INIT_MODE=upgrade \
+      -e DOCKER_INFLUXDB_INIT_USERNAME=my-user \
+      -e DOCKER_INFLUXDB_INIT_PASSWORD=my-password \
+      -e DOCKER_INFLUXDB_INIT_ORG=my-org \
+      -e DOCKER_INFLUXDB_INIT_BUCKET=my-bucket \
+      influxdb:{{< current-version >}}
+    ```
+
+## Upgrade with a custom InfluxDB 1.x configuration file
+If you're currently running an InfluxDB 1.x deployment with a custom configuration
+file similar to:
+
+```sh
+docker run -p 8086:8086 \
+  -v influxdb:/var/lib/influxdb \
+  -v $PWD/influxdb.conf:/etc/influxdb/influxdb.conf:ro \
+  influxdb:1.8
+```
+
+**To upgrade an InfluxDB 1.x deployment with a custom configuration file to InfluxDB 2.x:**
+
+1.  Stop the running InfluxDB 1.x container.
+2.  Start the InfluxDB container with the following:
+
+    - Volume mount for the InfluxDB 1.x data directory
+    - Volume mount for the InfluxDB 1.x configuration file
+    - Volume mount for the InfluxDB 2.x data directory (`/var/lib/influxdb2`)
+    - Volume mount for the InfluxDB 2.x configuration directory (`/etc/influxdb2`)
+    - InfluxDB [initialization mode](#upgrade-initialization-mode) environment variable
+    - InfluxDB [initialization credential](#influxdb-2x-initialization-credentials) environment variables
+    - `influxdb:{{< current-version >}}` Docker image
+
+```sh
+docker run -p 8086:8086 \
+  -v influxdb:/var/lib/influxdb \
+  -v $PWD/influxdb.conf:/etc/influxdb/influxdb.conf:ro \
+  -v influxdb2:/var/lib/influxdb2 \
+  -v influxdb2:/etc/influxdb2 \
+  -e DOCKER_INFLUXDB_INIT_MODE=upgrade \
+  -e DOCKER_INFLUXDB_INIT_USERNAME=my-user \
+  -e DOCKER_INFLUXDB_INIT_PASSWORD=my-password \
+  -e DOCKER_INFLUXDB_INIT_ORG=my-org \
+  -e DOCKER_INFLUXDB_INIT_BUCKET=my-bucket \
+  influxdb:{{< current-version >}}
+```
+
+## Upgrade with custom paths
+If you're currently running an InfluxDB 1.x deployment with the data directory and
+configuration file mounted at custom paths similar to:
+
+```sh
+docker run -p 8086:8086 \
+  -v influxdb:/root/influxdb/data \
+  -v $PWD/influxdb.conf:/root/influxdb/influxdb.conf:ro \
+  influxdb:1.8 -config /root/influxdb/influxdb.conf
+```
+
+**To upgrade an InfluxDB 1.x deployment with custom paths to InfluxDB 2.x:**
+
+1. Stop the running InfluxDB 1.x container.
+2. Decide to either **keep using custom paths** or **use InfluxDB 2.x default paths**.
+
+{{< tabs-wrapper >}}
+{{% tabs %}}
+[Keep using custom paths](#)
+[Use InfluxDB 2.x defaults](#)
+{{% /tabs %}}
+<!-------------------------- BEGIN KEEP CUSTOM PATHS -------------------------->
+{{% tab-content %}}
+
+To retain your custom InfluxDB 1.x paths, start the InfluxDB container with the following:
+
+- Volume mount for the InfluxDB 1.x data directory
+- Volume mount for the InfluxDB 1.x configuration file
+- Volume mount for the InfluxDB 2.x data directory
+- Volume mount for the InfluxDB 2.x configuration directory
+- InfluxDB [initialization mode](#upgrade-initialization-mode) environment variable
+- InfluxDB [initialization credential](#influxdb-2x-initialization-credentials) environment variables
+- InfluxDB 2.x [v1 configuration file path](#file-system-mounts) environment variable:
+    - `DOCKER_INFLUXDB_INIT_UPGRADE_V1_CONFIG`
+- InfluxDB 1.x custom path environment variables:
+    - `INFLUXD_CONFIG_PATH`
+    - `INFLUXD_BOLT_PATH`
+    - `INFLUXD_ENGINE_PATH`
+- `influxdb:{{< current-version >}}` Docker image
+
+```sh
+docker run -p 8086:8086 \
+  -v influxdb:/root/influxdb/data \
+  -v $PWD/influxdb.conf:/root/influxdb/influxdb.conf:ro \
+  -v influxdb2:/root/influxdb2/data \
+  -v influxdb2:/root/influxdb2 \
+  -e DOCKER_INFLUXDB_INIT_MODE=upgrade \
+  -e DOCKER_INFLUXDB_INIT_USERNAME=my-user \
+  -e DOCKER_INFLUXDB_INIT_PASSWORD=my-password \
+  -e DOCKER_INFLUXDB_INIT_ORG=my-org \
+  -e DOCKER_INFLUXDB_INIT_BUCKET=my-bucket \
+  -e DOCKER_INFLUXDB_INIT_UPGRADE_V1_CONFIG=/root/influxdb/influxdb.conf \
+  -e INFLUXD_CONFIG_PATH=/root/influxdb2/config.toml \
+  -e INFLUXD_BOLT_PATH=/root/influxdb2/influxdb.bolt \
+  -e INFLUXD_ENGINE_PATH=/root/influxdb2/engine \
+  influxdb:{{< current-version >}}
+```
+{{% /tab-content %}}
+<!--------------------------- END KEEP CUSTOM PATHS --------------------------->
+<!-------------------------- BEGIN USE 2.x DEFAULTS --------------------------->
+{{% tab-content %}}
+To use default InfluxDB 2.x paths, start the InfluxDB container with the following:
+
+- Volume mount for the InfluxDB 1.x data directory
+- Volume mount for the InfluxDB 1.x configuration file
+- Volume mount for the InfluxDB 2.x data directory (`/var/lib/influxdb2`)
+- Volume mount for the InfluxDB 2.x configuration directory (`/etc/influxdb2`)
+- InfluxDB [initialization mode](#upgrade-initialization-mode) environment variable
+- InfluxDB [initialization credential](#influxdb-2x-initialization-credentials) environment variables
+- InfluxDB 2.x [v1 configuration file path](#file-system-mounts) environment variable:
+    - `DOCKER_INFLUXDB_INIT_UPGRADE_V1_CONFIG`
+- `influxdb:{{< current-version >}}` Docker image
+
+```sh
+docker run -p 8086:8086 \
+  -v influxdb:/root/influxdb/data \
+  -v $PWD/influxdb.conf:/root/influxdb/influxdb.conf:ro \
+  -v influxdb2:/var/lib/influxdb2 \
+  -v influxdb2:/etc/influxdb2 \
+  -e DOCKER_INFLUXDB_INIT_MODE=upgrade \
+  -e DOCKER_INFLUXDB_INIT_USERNAME=my-user \
+  -e DOCKER_INFLUXDB_INIT_PASSWORD=my-password \
+  -e DOCKER_INFLUXDB_INIT_ORG=my-org \
+  -e DOCKER_INFLUXDB_INIT_BUCKET=my-bucket \
+  -e DOCKER_INFLUXDB_INIT_UPGRADE_V1_CONFIG=/root/influxdb/influxdb.conf \
+  influxdb:{{< current-version >}}
+```
+{{% /tab-content %}}
+<!--------------------------- END USE 2.x DEFAULTS ---------------------------->
+{{< /tabs-wrapper >}}
diff --git a/content/influxdb/v2.2/upgrade/v1-to-v2/manual-upgrade.md b/content/influxdb/v2.2/upgrade/v1-to-v2/manual-upgrade.md
new file mode 100644
index 000000000..2c640f4c4
--- /dev/null
+++ b/content/influxdb/v2.2/upgrade/v1-to-v2/manual-upgrade.md
@@ -0,0 +1,339 @@
+---
+title: Manually upgrade from InfluxDB 1.x to 2.2
+list_title: Manually upgrade from 1.x to 2.2
+description: >
+  To manually upgrade from InfluxDB 1.x to InfluxDB 2.2, migrate data, create
+  1.x-compatible authorizations, and create database and retention policy
+  (DBRP) mappings.
+menu:
+  influxdb_2_2:
+    parent: InfluxDB 1.x to 2.2
+    name: Manually upgrade
+weight: 11
+related:
+  - /influxdb/v2.2/upgrade/v1-to-v2/
+  - /influxdb/v2.2/upgrade/v1-to-v2/migrate-cqs/
+---
+
+To manually upgrade from InfluxDB 1.x to InfluxDB {{< current-version >}}:
+
+1. [Install InfluxDB {{< current-version >}}](#install-influxdb-21)
+2. [Migrate custom configuration settings](#migrate-custom-configuration-settings)
+3. [Create DBRP mappings](#create-dbrp-mappings)
+4. [Create authorizations](#create-authorizations)
+5. [Migrate time series data](#migrate-time-series-data)
+6. [Migrate continuous queries](#migrate-continuous-queries)
+
+## Install InfluxDB {{< current-version >}}
+[Download, install, and set up InfluxDB {{< current-version >}}](/influxdb/v2.2/get-started/).
+
+{{% note %}}
+#### Required 2.x credentials
+All InfluxDB {{< current-version >}} `influx` CLI examples below assume the required **host**,
+**organization**, and **API token** credentials are provided by your
+[`influx` CLI configuration](/influxdb/v2.2/reference/cli/influx/#provide-required-authentication-credentials).
+{{% /note %}}
+
+## Migrate custom configuration settings
+If you're using custom configuration settings in your InfluxDB 1.x instance, do the following:
+
+1.  Compare 1.x and {{< current-version >}} configuration settings:
+
+    {{< expand-wrapper >}}
+    {{% expand "View configuration option parity" %}}
+
+| 1.x configuration option           | {{< current-version >}} configuration option                                                                                      |
+| :--------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------- |
+| **[data]**                         |                                                                                                                                   |
+| dir                                | [engine-path](/influxdb/v2.2/reference/config-options/#engine-path)                                                               |
+| wal-dir                            | [engine-path](/influxdb/v2.2/reference/config-options/#engine-path)                                                               |
+| wal-fsync-delay                    | [storage-wal-fsync-delay](/influxdb/v2.2/reference/config-options/#storage-wal-fsync-delay)                                       |
+| index-version                      |                                                                                                                                   |
+| trace-logging-enabled              |                                                                                                                                   |
+| query-log-enabled                  |                                                                                                                                   |
+| strict-error-handling              |                                                                                                                                   |
+| validate-keys                      | [storage-validate-keys](/influxdb/v2.2/reference/config-options/#storage-validate-keys)                                           |
+| cache-max-memory-size              | [storage-cache-max-memory-size](/influxdb/v2.2/reference/config-options/#storage-cache-max-memory-size)                           |
+| cache-snapshot-memory-size         | [storage-cache-snapshot-memory-size](/influxdb/v2.2/reference/config-options/#storage-cache-snapshot-memory-size)                 |
+| cache-snapshot-write-cold-duration | [storage-cache-snapshot-write-cold-duration](/influxdb/v2.2/reference/config-options/#storage-cache-snapshot-write-cold-duration) |
+| compact-full-write-cold-duration   | [storage-compact-full-write-cold-duration](/influxdb/v2.2/reference/config-options/#storage-compact-full-write-cold-duration)     |
+| max-concurrent-compactions         | [storage-max-concurrent-compactions](/influxdb/v2.2/reference/config-options/#storage-max-concurrent-compactions)                 |
+| compact-throughput                 |                                                                                                                                   |
+| compact-throughput-burst           | [storage-compact-throughput-burst](/influxdb/v2.2/reference/config-options/#storage-compact-throughput-burst)                     |
+| tsm-use-madv-willneed              | [storage-tsm-use-madv-willneed](/influxdb/v2.2/reference/config-options/#storage-tsm-use-madv-willneed)                           |
+| max-series-per-database            |                                                                                                                                   |
+| max-values-per-tag                 |                                                                                                                                   |
+| max-index-log-file-size            | [storage-max-index-log-file-size](/influxdb/v2.2/reference/config-options/#storage-max-index-log-file-size)                       |
+| series-id-set-cache-size           | [storage-series-id-set-cache-size](/influxdb/v2.2/reference/config-options/#storage-series-id-set-cache-size)                     |
+|                                    |                                                                                                                                   |
+| **[retention]**                    |                                                                                                                                   |
+| check-interval                     | [storage-retention-check-interval](/influxdb/v2.2/reference/config-options/#storage-retention-check-interval)                     |
+|                                    |                                                                                                                                   |
+| **[shard-precreation]**            |                                                                                                                                   |
+| check-interval                     | [storage-shard-precreator-check-interval](/influxdb/v2.2/reference/config-options/#storage-shard-precreator-check-interval)       |
+| advance-period                     | [storage-shard-precreator-advance-period](/influxdb/v2.2/reference/config-options/#storage-shard-precreator-advance-period)       |
+|                                    |                                                                                                                                   |
+| **[http]**                         |                                                                                                                                   |
+| flux-enabled                       |                                                                                                                                   |
+| flux-log-enabled                   |                                                                                                                                   |
+| bind-address                       | [http-bind-address](/influxdb/v2.2/reference/config-options/#http-bind-address)                                                   |
+| auth-enabled                       |                                                                                                                                   |
+| realm                              |                                                                                                                                   |
+| log-enabled                        |                                                                                                                                   |
+| suppress-write-log                 |                                                                                                                                   |
+| access-log-path                    |                                                                                                                                   |
+| access-log-status-filters          |                                                                                                                                   |
+| write-tracing                      |                                                                                                                                   |
+| pprof-enabled                      | [pprof-disabled](/influxdb/v2.2/reference/config-options/#pprof-disabled)                                                         |
+| pprof-auth-enabled                 |                                                                                                                                   |
+| debug-pprof-enabled                |                                                                                                                                   |
+| ping-auth-enabled                  |                                                                                                                                   |
+| https-enabled                      |                                                                                                                                   |
+| https-certificate                  | [tls-cert](/influxdb/v2.2/reference/config-options/#tls-cert)                                                                     |
+| https-private-key                  | [tls-key](/influxdb/v2.2/reference/config-options/#tls-key)                                                                       |
+| shared-secret                      |                                                                                                                                   |
+| max-row-limit                      |                                                                                                                                   |
+| max-connection-limit               |                                                                                                                                   |
+| unix-socket-enabled                |                                                                                                                                   |
+| bind-socket                        |                                                                                                                                   |
+| max-body-size                      |                                                                                                                                   |
+| max-concurrent-write-limit         |                                                                                                                                   |
+| max-enqueued-write-limit           |                                                                                                                                   |
+| enqueued-write-timeout             | [http-write-timeout](/influxdb/v2.2/reference/config-options/#http-write-timeout)                                                 |
+|                                    |                                                                                                                                   |
+| **[logging]**                      |                                                                                                                                   |
+| format                             |                                                                                                                                   |
+| level                              | [log-level](/influxdb/v2.2/reference/config-options/#log-level)                                                                   |
+| suppress-logo                      |                                                                                                                                   |
+|                                    |                                                                                                                                   |
+| **[tls]**                          |                                                                                                                                   |
+| ciphers                            | [tls-strict-ciphers](/influxdb/v2.2/reference/config-options/#tls-strict-ciphers)                                                 |
+| min-version                        | [tls-min-version](/influxdb/v2.2/reference/config-options/#tls-min-version)                                                       |
+| max-version                        |                                                                                                                                   |
+
+{{% note %}}
+#### 1.x configuration groups not in {{< current-version >}}
+The following 1.x configuration groups **do not** apply to InfluxDB {{< current-version >}}:
+
+- meta
+- coordinator
+- monitor
+- subscriber
+- graphite
+- collectd
+- opentsdb
+- udp
+- continuous_queries
+{{% /note %}}
+    {{% /expand %}}
+    {{< /expand-wrapper >}}
+
+2.  Apply your 1.x custom settings to the comparable InfluxDB {{< current-version >}} settings using
+   `influxd` flags, environment variables, or a {{< current-version >}} configuration file.
+    For more information about configuring InfluxDB {{< current-version >}}, see
+    [Configuration options](/influxdb/v2.2/reference/config-options/).
+3.  **Restart `influxd`**.
+
+## Create DBRP mappings
+InfluxDB database and retention policy (DBRP) mappings associate database and
+retention policy combinations with InfluxDB {{< current-version >}} [buckets](/influxdb/v2.2/reference/glossary/#bucket).
+These mappings allow InfluxDB 1.x clients to successfully query and write to
+InfluxDB {{< current-version >}} buckets while using the 1.x DBRP convention.
+
+_For more information about DBRP mapping, see
+[Database and retention policy mapping](/influxdb/v2.2/reference/api/influxdb-1x/dbrp/)._
+
+**To map a DBRP combination to an InfluxDB {{< current-version >}} bucket:**
+
+1.  **Create a bucket**  
+    [Create an InfluxDB {{< current-version >}} bucket](/influxdb/v2.2/organizations/buckets/create-bucket/).
+    We recommend creating a bucket for each unique 1.x database and retention
+    policy combination using the following naming convention:
+
+    ```sh
+    # Naming convention
+    db-name/rp-name
+
+    # Example
+    telegraf/autogen
+    ```
+
+2.  **Create a DBRP mapping**  
+    Use the [`influx v1 dbrp create` command](/influxdb/v2.2/reference/cli/influx/v1/dbrp/create/)
+    to create a DBRP mapping.
+    Provide the following:
+
+    - database name
+    - retention policy name _(not retention period)_
+    - [bucket ID](/influxdb/v2.2/organizations/buckets/view-buckets/)
+    - _(optional)_ `--default` flag if you want the retention policy to be the default retention
+      policy for the specified database
+
+    {{< code-tabs-wrapper >}}
+    {{% code-tabs %}}
+[DB with one RP](#)
+[DB with multiple RPs](#)
+    {{% /code-tabs %}}
+    {{% code-tab-content %}}
+```sh
+influx v1 dbrp create \
+  --db example-db \
+  --rp example-rp \
+  --bucket-id 00xX00o0X001 \
+  --default
+```
+    {{% /code-tab-content %}}
+    {{% code-tab-content %}}
+```sh
+# Create telegraf/autogen DBRP mapping with autogen
+# as the default RP for the telegraf DB
+
+influx v1 dbrp create \
+  --db telegraf \
+  --rp autogen \
+  --bucket-id 00xX00o0X001 \
+  --default
+
+# Create telegraf/downsampled-daily DBRP mapping that
+# writes to a different bucket
+
+influx v1 dbrp create \
+  --db telegraf \
+  --rp downsampled-daily \
+  --bucket-id 00xX00o0X002
+```
+    {{% /code-tab-content %}}
+    {{< /code-tabs-wrapper >}}
+
+3.  **Confirm the DBRP mapping was created**  
+    Use the [`influx v1 dbrp list`](/influxdb/v2.2/reference/cli/influx/v1/dbrp/list/) to list existing DBRP mappings.
+
+    ```sh
+    influx v1 dbrp list
+    ```
+
+For information about managing DBRP mappings, see the
+[`influx v1 dbrp` command documentation](/influxdb/v2.2/reference/cli/influx/v1/dbrp/).
+
+## Create authorizations
+InfluxDB {{< current-version >}} requires authentication and provides two authentication methods:
+
+- [Token authentication](#token-authentication)
+- [1.x compatible authorizations](#1x-compatible-authorizations)
+
+### Token authentication
+Use [InfluxDB {{< current-version >}} token authentication](/influxdb/v2.2/security/tokens/) to
+authenticate requests to InfluxDB {{< current-version >}}.
+
+##### Recommended if:
+- Your 1.x instance **does not have authentication enabled**.
+
+{{% note %}}
+#### Use tokens with basic authentication
+To use tokens with InfluxDB clients that require an InfluxDB username and password,
+provide an arbitrary user name and pass the token as the password.
+{{% /note %}}
+
+### 1.x-compatible authorizations
+InfluxDB {{< current-version >}} provides a [1.x compatibility API](/influxdb/v2.2/reference/api/influxdb-1x/)
+that lets you authenticate using a username and password as in InfluxDB 1.x.
+If authentication is enabled in your InfluxDB 1.x instance,
+[create a 1.x-compatible authorization](#create-a-1x-compatible-authorization)
+with the same username and password as your InfluxDB 1.x instance to allow
+external clients to connect to your InfluxDB {{< current-version >}} instance without any change.
+
+##### Recommended if:
+- Your 1.x instance **has authentication enabled**.
+- You're using **InfluxDB 1.x clients or client libraries** configured with
+  InfluxDB usernames and passwords.
+
+{{% note %}}
+1.x compatibility authorizations are separate from credentials used to log
+into the InfluxDB {{< current-version >}} user interface (UI).
+{{% /note %}}
+
+#### Create a 1.x-compatible authorization
+Use the InfluxDB {{< current-version >}} [`influx v1 auth create` command](/influxdb/v2.2/reference/cli/influx/v1/auth/create/)
+to create a 1.x-compatible authorization that grants read/write permissions to specific {{< current-version >}} buckets.
+Provide the following:
+
+- list of [bucket IDs](/influxdb/v2.2/organizations/buckets/view-buckets/) to
+  grant read or write permissions to
+- new v1 auth username
+- new v1 auth password _(when prompted)_
+
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[Single bucket](#)
+[Mutiple buckets](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```sh
+influx v1 auth create \
+  --read-bucket 00xX00o0X001 \
+  --write-bucket 00xX00o0X001 \
+  --username example-user
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```sh
+influx v1 auth create \
+  --read-bucket 00xX00o0X001 \
+  --read-bucket 00xX00o0X002 \
+  --write-bucket 00xX00o0X001 \
+  --write-bucket 00xX00o0X002 \
+  --username example-user
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+For information about managing 1.x compatible authorizations, see the
+[`influx v1 auth` command documentation](/influxdb/v2.2/reference/cli/influx/v1/auth/).
+
+## Migrate time series data
+To migrate time series data from your InfluxDB 1.x instance to InfluxDB {{< current-version >}}:
+
+1. Use the **InfluxDB 1.x** [`influx_inspect export` command](/{{< latest "influxdb" "v1" >}}/tools/influx_inspect/#export)
+   to export time series data as line protocol.
+   Include the `-lponly` flag to exclude comments and the data definition
+   language (DDL) from the output file.
+
+   _We recommend exporting each DBRP combination separately to easily write data
+   to a corresponding InfluxDB {{< current-version >}} bucket._
+
+    ```sh
+    # Syntax
+    influx_inspect export \
+      -database <database-name> \
+      -retention <retention-policy-name> \
+      -out <output-file-path> \
+      -lponly
+
+    # Example
+    influx_inspect export \
+      -database example-db \
+      -retention example-rp \
+      -out /path/to/example-db_example-rp.lp \
+      -lponly
+    ```
+
+2. Use the **InfluxDB {{< current-version >}}** [`influx write` command](/influxdb/v2.2/reference/cli/influx/write/)
+   to write the exported line protocol to InfluxDB {{< current-version >}}.
+
+    ```sh
+    # Syntax
+    influx write \
+      --bucket <bucket-name> \
+      --file <path-to-line-protocol-file>
+
+    # Example
+    influx write \
+      --bucket example-db/example-rp \
+      --file /path/to/example-db_example-rp.lp
+    ```
+
+3. Repeat steps 1-2 for each bucket.
+
+## Migrate continuous queries
+For information about migrating InfluxDB 1.x continuous queries to InfluxDB {{< current-version >}} tasks,
+see [Migrate continuous queries to tasks](/influxdb/v2.2/upgrade/v1-to-v2/migrate-cqs/).
diff --git a/content/influxdb/v2.2/upgrade/v1-to-v2/migrate-cqs.md b/content/influxdb/v2.2/upgrade/v1-to-v2/migrate-cqs.md
new file mode 100644
index 000000000..8b4e17187
--- /dev/null
+++ b/content/influxdb/v2.2/upgrade/v1-to-v2/migrate-cqs.md
@@ -0,0 +1,362 @@
+---
+title: Migrate continuous queries to tasks
+description: >
+  InfluxDB OSS 2.x replaces 1.x continuous queries (CQs) with **InfluxDB tasks**.
+  To migrate continuous queries to InfluxDB 2.x, convert InfluxDB 1.x CQs into Flux and create new
+  InfluxDB 2.x tasks.
+menu:
+  influxdb_2_2:
+    parent: InfluxDB 1.x to 2.2
+    name: Migrate CQs
+weight: 102
+related:
+  - /influxdb/v2.2/query-data/get-started/
+  - /influxdb/v2.2/query-data/flux/
+  - /influxdb/v2.2/process-data/
+  - /influxdb/v2.2/process-data/common-tasks/
+  - /influxdb/v2.2/reference/flux/flux-vs-influxql/
+---
+
+InfluxDB OSS {{< current-version >}} replaces 1.x continuous queries (CQs) with **InfluxDB tasks**.
+To migrate continuous queries to InfluxDB {{< current-version >}} tasks, do the following:
+
+1. [Output all InfluxDB 1.x continuous queries](#output-all-influxdb-1x-continuous-queries)
+2. [Convert continuous queries to Flux queries](#convert-continuous-queries-to-flux-queries)
+3. [Create new InfluxDB tasks](#create-new-influxdb-tasks)
+
+## Output all InfluxDB 1.x continuous queries
+
+If using the `influxd upgrade` command, by default, all continuous queries are
+output to `~/continuous_queries.txt` during the upgrade process.
+To customize the destination path of the continuous queries file,
+use the `--continuous-query-export-path` flag with the `influxd upgrade` command.
+
+```sh
+influxd upgrade --continuous-query-export-path /path/to/continuous_queries.txt
+```
+
+**To manually output continuous queries:**
+
+1. Use the **InfluxDB 1.x `influx` interactive shell** to run `SHOW CONTINUOUS QUERIES`:
+
+    {{< keep-url >}}
+    ```sh
+    $ influx
+    Connected to http://localhost:8086 version {{< latest-patch version="1.8" >}}
+    InfluxDB shell version: {{< latest-patch version="1.8" >}}
+    > SHOW CONTINUOUS QUERIES
+    ```
+
+2. Copy and save the displayed continuous queries.
+
+## Convert continuous queries to Flux queries
+
+To migrate InfluxDB 1.x continuous queries to InfluxDB {{< current-version >}} tasks, convert the InfluxQL query syntax to Flux.
+The majority of continuous queries are simple downsampling queries and can be converted quickly
+using the [`aggregateWindow()` function](/{{< latest "flux" >}}/stdlib/universe/aggregatewindow/).
+For example:
+
+##### Example continuous query
+```sql
+CREATE CONTINUOUS QUERY "downsample-daily" ON "my-db"
+BEGIN
+  SELECT mean("example-field")
+  INTO "my-db"."example-rp"."average-example-measurement"
+  FROM "example-measurement"
+  GROUP BY time(1h)
+END
+```
+
+##### Equivalent Flux task
+```js
+option task = {name: "downsample-daily", every: 1d}
+
+from(bucket: "my-db/")
+    |> range(start: -task.every)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> filter(fn: (r) => r._field == "example-field")
+    |> aggregateWindow(every: 1h, fn: mean)
+    |> set(key: "_measurement", value: "average-example-measurement")
+    |> to(org: "example-org", bucket: "my-db/example-rp")
+```
+
+### Convert InfluxQL continuous queries to Flux
+Review the following statements and clauses to see how to convert your CQs to Flux:
+
+- [ON clause](#on-clause)
+- [SELECT statement](#select-statement)
+- [INTO clause](#into-clause)
+- [FROM clause](#from-clause)
+- [AS clause](#as-clause)
+- [WHERE clause](#where-clause)
+- [GROUP BY clause](#group-by-clause)
+- [RESAMPLE clause](#resample-clause)
+
+#### ON clause
+The `ON` clause defines the database to query.
+In InfluxDB OSS {{< current-version >}}, database and retention policy combinations are mapped to specific buckets
+(for more information, see [Database and retention policy mapping](/influxdb/v2.2/reference/api/influxdb-1x/dbrp/)).
+
+Use the [`from()` function](/{{< latest "flux" >}}/stdlib/universe/from)
+to specify the bucket to query:
+
+###### InfluxQL
+```sql
+CREATE CONTINUOUS QUERY "downsample-daily" ON "my-db"
+-- ...
+```
+
+###### Flux
+```js
+from(bucket: "my-db/")
+// ...
+```
+
+#### SELECT statement
+The `SELECT` statement queries data by field, tag, and time from a specific measurement.
+`SELECT` statements can take many different forms and converting them to Flux depends
+on your use case. For information about Flux and InfluxQL function parity, see
+[Flux vs InfluxQL](/influxdb/v2.2/reference/syntax/flux/flux-vs-influxql/#influxql-and-flux-parity).
+See [other resources available to help](#other-helpful-resources).
+
+#### INTO clause
+The `INTO` clause defines the measurement to write results to.
+`INTO` also supports fully-qualified measurements that include the database and retention policy.
+In InfluxDB OSS {{< current-version >}}, database and retention policy combinations are mapped to specific buckets
+(for more information, see [Database and retention policy mapping](/influxdb/v2.2/reference/api/influxdb-1x/dbrp/)).
+
+To write to a measurement different than the measurement queried, use
+[`set()`](/{{< latest "flux" >}}/stdlib/universe/set/) or
+[`map()`](/{{< latest "flux" >}}/stdlib/universe/map/)
+to change the measurement name.
+Use the `to()` function to specify the bucket to write results to.
+
+###### InfluxQL
+```sql
+-- ...
+INTO "example-db"."example-rp"."example-measurement"
+-- ...
+```
+
+###### Flux
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[set()](#)
+[map()](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```js
+// ...
+    |> set(key: "_measurement", value: "example-measurement")
+    |> to(bucket: "example-db/example-rp")
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```js
+// ...
+    |> map(fn: (r) => ({ r with _measurement: "example-measurement"}))
+    |> to(bucket: "example-db/example-rp")
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+##### Write pivoted data to InfluxDB
+InfluxDB 1.x query results include a column for each field.
+InfluxDB {{< current-version >}} does not do this by default, but it is possible with
+[`pivot()`](/{{< latest "flux" >}}/stdlib/universe/pivot)
+or [`schema.fieldsAsCols()`](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/fieldsascols/).
+
+If you use `to()` to write _pivoted data_ back to InfluxDB {{< current-version >}}, each field column is stored as a tag.
+To write pivoted fields back to InfluxDB as fields, import the `experimental` package
+and use the [`experimental.to()` function](/{{< latest "flux" >}}/stdlib/experimental/to/).
+
+###### InfluxQL
+```sql
+CREATE CONTINUOUS QUERY "downsample-daily" ON "my-db"
+BEGIN
+  SELECT mean("example-field-1"), mean("example-field-2")
+  INTO "example-db"."example-rp"."example-measurement"
+  FROM "example-measurement"
+  GROUP BY time(1h)
+END
+```
+
+###### Flux
+```js
+// ...
+
+from(bucket: "my-db/")
+    |> range(start: -task.every)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> filter(fn: (r) => r._field == "example-field-1" or r._field == "example-field-2")
+    |> aggregateWindow(every: task.every, fn: mean)
+    |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
+    |> experimental.to(bucket: "example-db/example-rp")
+```
+
+#### FROM clause
+The from clause defines the measurement to query.
+Use the [`filter()` function](/{{< latest "flux" >}}/stdlib/universe/filter/)
+to specify the measurement to query.
+
+###### InfluxQL
+```sql
+-- ...
+FROM "example-measurement"
+-- ...
+```
+
+###### Flux
+```js
+// ...
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+```
+
+#### AS clause
+The `AS` clause changes the name of the field when writing data back to InfluxDB.
+Use [`set()`](/{{< latest "flux" >}}/stdlib/universe/set/)
+or [`map()`](/{{< latest "flux" >}}/stdlib/universe/map/)
+to change the field name.
+
+###### InfluxQL
+```sql
+-- ...
+AS newfield
+-- ...
+```
+
+###### Flux
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[set()](#)
+[map()](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```js
+// ...
+    |> set(key: "_field", value: "newfield")
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```js
+// ...
+    |> map(fn: (r) => ({ r with _field: "newfield"}))
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+#### WHERE clause
+The `WHERE` clause uses predicate logic to filter results based on fields, tags, or timestamps.
+Use the [`filter()` function](/{{< latest "flux" >}}/stdlib/universe/filter/)
+and Flux [comparison operators](/{{< latest "flux" >}}/spec/operators/#comparison-operators)
+to filter results based on fields and tags.
+Use the [`range()` function](/{{< latest "flux" >}}/stdlib/universe/range/) to filter results based on timestamps.
+
+###### InfluxQL
+```sql
+-- ...
+WHERE "example-tag" = "foo" AND time > now() - 7d
+```
+
+###### Flux
+```js
+// ...
+    |> range(start: -7d)
+    |> filter(fn: (r) => r["example-tag"] == "foo")
+```
+
+#### GROUP BY clause
+The InfluxQL `GROUP BY` clause groups data by specific tags or by time (typically to calculate an aggregate value for windows of time).
+
+##### Group by tags
+Use the [`group()` function](/{{< latest "flux" >}}/stdlib/universe/group/)
+to modify the [group key](/{{< latest "flux" >}}/get-started/data-model/#group-key) and change how data is grouped.
+
+###### InfluxQL
+```sql
+-- ...
+GROUP BY "location"
+```
+
+###### Flux
+```js
+// ...
+    |> group(columns: ["location"])
+```
+
+##### Group by time
+Use the [`aggregateWindow()` function](//{{< latest "flux" >}}/stdlib/universe/aggregatewindow/)
+to group data into time windows and perform an aggregation on each window.
+In CQs, the interval specified in the `GROUP BY time()` clause determines the CQ execution interval.
+Use the `GROUP BY time()` interval to set the `every` task option.
+
+###### InfluxQL
+```sql
+-- ...
+SELECT MEAN("example-field")
+FROM "example-measurement"
+GROUP BY time(1h)
+```
+
+###### Flux
+```js
+option task = {name: "task-name", every: 1h}
+
+// ...
+    |> filter(fn: (r) => r._measurement == "example-measurement" and r._field == "example-field")
+    |> aggregateWindow(every: task.every, fn: mean)
+```
+
+#### RESAMPLE clause
+
+The CQ `RESAMPLE` clause uses data from the last specified duration to calculate a new aggregate point.
+The `EVERY` interval in `RESAMPLE` defines how often the CQ runs.
+The `FOR` interval defines the total time range queried by the CQ.
+
+To accomplish this same functionality in a Flux task, set the `start` parameter
+in the `range()` function to the negative `FOR` duration.
+Define the task execution interval in the `task` options.
+For example:
+
+###### InfluxQL
+```sql
+CREATE CONTINUOUS QUERY "resample-example" ON "my-db"
+RESAMPLE EVERY 1m FOR 30m
+BEGIN
+  SELECT exponential_moving_average(mean("example-field"), 30)
+  INTO "resample-average-example-measurement"
+  FROM "example-measurement"
+  WHERE region = 'example-region'
+  GROUP BY time(1m)
+END
+```
+
+###### Flux
+```js
+option task = {name: "resample-example", every: 1m}
+
+from(bucket: "my-db/")
+    |> range(start: -30m)
+    |> filter(fn: (r) => r._measurement == "example-measurement" and r._field == "example-field" and r.region == "example-region")
+    |> aggregateWindow(every: 1m, fn: mean)
+    |> exponentialMovingAverage(n: 30)
+    |> set(key: "_measurement", value: "resample-average-example-measurement")
+    |> to(bucket: "my-db/")
+```
+
+## Create new InfluxDB tasks
+After converting your continuous query to Flux, use the Flux query to
+[create a new task](/influxdb/v2.2/process-data/manage-tasks/create-task/).
+
+## Other helpful resources
+The following resources are available and may be helpful when converting
+continuous queries to Flux tasks.
+
+##### Documentation
+- [Get started with Flux](/{{< latest "flux" >}}/get-started/)
+- [Query data with Flux](/influxdb/v2.2/query-data/flux/)
+- [Common tasks](/influxdb/v2.2/process-data/common-tasks/#downsample-data-with-influxdb)
+
+##### Community
+- Post in the [InfluxData Community](https://community.influxdata.com/)
+- Ask in the [InfluxDB Community Slack](https://influxdata.com/slack)
diff --git a/content/influxdb/v2.2/upgrade/v2-to-v2.md b/content/influxdb/v2.2/upgrade/v2-to-v2.md
new file mode 100644
index 000000000..be00afa74
--- /dev/null
+++ b/content/influxdb/v2.2/upgrade/v2-to-v2.md
@@ -0,0 +1,81 @@
+---
+title: Upgrade from InfluxDB 2.x to InfluxDB 2.2
+description: >
+  To upgrade from InfluxDB 2.0 beta 16 or earlier to InfluxDB 2.2 (stable),
+  manually upgrade all resources and data to the latest version by completing these steps.
+menu:
+  influxdb_2_2:
+    parent: Upgrade InfluxDB
+    name: InfluxDB 2.x to 2.2
+weight: 10
+related:
+  - /influxdb/v2.2/reference/cli/influxd/downgrade/
+  - /influxdb/v2.2/install/
+---
+
+Upgrade to InfluxDB {{< current-version >}} from an earlier version of InfluxDB 2.x.
+
+{{% note %}}
+#### InfluxDB 2.0 beta-16 or earlier
+If you're upgrading from InfluxDB 2.0 beta-16 or earlier, you must first
+[upgrade to InfluxDB 2.0](/influxdb/v2.0/upgrade/v2-beta-to-v2/), 
+and then complete the steps below.
+{{% /note %}}
+
+{{< tabs-wrapper >}}
+{{% tabs %}}
+[macOS](#)
+[Linux](#)
+[Windows](#)
+[Docker](#)
+{{% /tabs %}}
+
+<!---------------------------- BEGIN MACOS CONTENT ---------------------------->
+{{% tab-content %}}
+Do one of the following:
+
+- [Use homebrew to upgrade](#use-homebrew-to-upgrade)
+- [Manually upgrade](#manually-upgrade)
+
+### Use homebrew to upgrade
+```
+brew upgrade influxdb
+```
+
+### Manually upgrade
+To manually upgrade, [download and install the latest version of InfluxDB {{< current-version >}} for macOS](/influxdb/v2.2/install/#manually-download-and-install)
+in place of your current 2.x version.
+{{% /tab-content %}}
+<!----------------------------- END MACOS CONTENT ----------------------------->
+
+<!---------------------------- BEGIN LINUX CONTENT ---------------------------->
+{{% tab-content %}}
+
+[Download and install the latest version of InfluxDB {{< current-version >}} for Linux](/influxdb/v2.2/install/?t=Linux#download-and-install-influxdb-v21)
+in place of current 2.x version.
+
+{{% /tab-content %}}
+<!----------------------------- END LINUX CONTENT ----------------------------->
+
+<!--------------------------- BEGIN WINDOWS CONTENT --------------------------->
+{{% tab-content %}}
+
+[Download and install the latest version of InfluxDB {{< current-version >}} for Windows](/influxdb/v2.2/install/?t=Windows)
+in place of current 2.x version.
+
+{{% /tab-content %}}
+<!---------------------------- END WINDOWS CONTENT ---------------------------->
+
+<!--------------------------- BEGIN DOCKER CONTENT ---------------------------->
+{{% tab-content %}}
+
+To upgrade to InfluxDB {{< current-version >}} with Docker, update your Docker
+image to use the latest InfluxDB image.
+
+```sh
+influxdb:{{< latest-patch >}}
+```
+{{% /tab-content %}}
+<!---------------------------- END DOCKER CONTENT ----------------------------->
+
+{{< /tabs-wrapper >}}
diff --git a/content/influxdb/v2.2/users/_index.md b/content/influxdb/v2.2/users/_index.md
new file mode 100644
index 000000000..d319688ce
--- /dev/null
+++ b/content/influxdb/v2.2/users/_index.md
@@ -0,0 +1,26 @@
+---
+title: Manage users
+seotitle: Manage users in InfluxDB
+description: Manage users in InfluxDB using the InfluxDB UI or the influx CLI.
+influxdb/v2.2/tags: [users, authentication]
+menu:
+  influxdb_2_2:
+    name: Manage users
+weight: 11
+products: [oss]
+---
+
+Users are those with access to InfluxDB.
+To grant a user permission to access data, add them as a [member of an organization](/influxdb/v2.2/organizations/members/)
+and provide them with an [API token](/influxdb/v2.2/security/tokens/).
+
+The following articles walk through managing users.
+
+{{% note %}}
+#### InfluxDB 2.x/1.x compatibility
+If you [upgraded from 1.x to {{< current-version >}}](/influxdb/v2.2/upgrade/v1-to-v2/),
+use the [`influx v1 auth`](/influxdb/v2.2/reference/cli/influx/v1/auth/) commands
+to manage authorizations for the InfluxDB [1.x compatibility API](/influxdb/v2.2/reference/api/influxdb-1x/).
+{{% /note %}}
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/users/change-password.md b/content/influxdb/v2.2/users/change-password.md
new file mode 100644
index 000000000..e12cb1872
--- /dev/null
+++ b/content/influxdb/v2.2/users/change-password.md
@@ -0,0 +1,35 @@
+---
+title: Change your password
+seotitle: Change your password in InfluxDB
+description: Change your password in InfluxDB using the influx CLI.
+menu:
+  influxdb_2_2:
+    name: Change your password
+    parent: Manage users
+weight: 105
+---
+
+Use `influx` command line interface (CLI) to update your password.
+
+{{% note %}}
+User passwords cannot be updated in the InfluxDB UI.
+{{% /note %}}
+
+## Change your password using the influx CLI
+
+Use the [`influx user password` command](/influxdb/v2.2/reference/cli/influx/user/password)
+to update a password for a user. To update a password, you need the following:
+
+- Username or user ID _(provided in the output of `influx user list`)_
+- New password
+
+##### Update a password
+```sh
+# Syntax
+influx user password -n <username>
+
+# Example
+influx user password -n johndoe
+```
+
+When prompted, enter and confirm the new password.
diff --git a/content/influxdb/v2.2/users/create-user.md b/content/influxdb/v2.2/users/create-user.md
new file mode 100644
index 000000000..9d31b8a11
--- /dev/null
+++ b/content/influxdb/v2.2/users/create-user.md
@@ -0,0 +1,51 @@
+---
+title: Create a user
+seotitle: Create a user in InfluxDB
+description: Create a user in InfluxDB using the InfluxDB UI or the influx CLI.
+menu:
+  influxdb_2_2:
+    name: Create a user
+    parent: Manage users
+weight: 101
+products: [oss]
+---
+
+Use the `influx` command line interface (CLI) to create a user.
+
+{{% note %}}
+Additional users cannot be created in the InfluxDB UI.
+{{% /note %}}
+
+## Create a user using the influx CLI
+
+To create a new user, use the [`influx user create` command](/influxdb/v2.2/reference/cli/influx/user/create)
+and include the following:
+
+- Username
+- Organization name or organization ID to add the user to _(provided in the output of
+  [`influx org list`](/influxdb/v2.2/reference/cli/influx/org/list/))_
+
+```sh
+# Syntax
+influx user create -n <username> -o <org-name>
+
+# Example
+influx user create -n johndoe -o example-org
+```
+
+### Create a user with a password and organization
+To create a new user with a password and add the user as a member of an organization,
+include a password and organization ID with the `influx user create` command.
+
+- Username
+- Organization name or organization ID to add the user to _(provided in the output of
+  [`influx org list`](/influxdb/v2.2/reference/cli/influx/org/list/))_
+- Password
+
+```sh
+# Syntax
+influx user create -n <username> -p <password> -o <org-name>
+
+# Example
+influx user create -n johndoe -p PaSsWoRd -o example-org
+```
diff --git a/content/influxdb/v2.2/users/delete-user.md b/content/influxdb/v2.2/users/delete-user.md
new file mode 100644
index 000000000..87ed9ef0a
--- /dev/null
+++ b/content/influxdb/v2.2/users/delete-user.md
@@ -0,0 +1,41 @@
+---
+title: Delete a user
+seotitle: Delete a user from InfluxDB
+description: Delete a user from InfluxDB using the InfluxDB UI or the influx CLI.
+menu:
+  influxdb_2_2:
+    name: Delete a user
+    parent: Manage users
+weight: 103
+products: [oss]
+---
+
+Use the InfluxDB user interface (UI) or the `influx` command line interface (CLI)
+to delete a user.
+
+{{% warn %}}
+Deleting a user removes them completely from InfluxDB.
+To remove a user from an organization without deleting the user entirely, see
+[Remove a member from an organization](/influxdb/v2.2/organizations/members/remove-member/).
+{{% /warn %}}
+
+## Delete a user from the InfluxDB UI
+
+{{% note %}}
+Users cannot be deleted from the InfluxDB UI.
+{{% /note %}}
+
+## Delete a user using the influx CLI
+
+Use the [`influx user delete` command](/influxdb/v2.2/reference/cli/influx/user/delete)
+to delete a user. Deleting a user requires the following:
+
+- The user ID _(provided in the output of `influx user list`)_
+
+```sh
+# Syntax
+influx user delete -i <user-id>
+
+# Example
+influx user delete -i 034ad714fdd6f000
+```
diff --git a/content/influxdb/v2.2/users/recover-credentials.md b/content/influxdb/v2.2/users/recover-credentials.md
new file mode 100644
index 000000000..4fad209a7
--- /dev/null
+++ b/content/influxdb/v2.2/users/recover-credentials.md
@@ -0,0 +1,54 @@
+---
+title: Recover user credentials
+seotitle: Recover InfluxDB user credentials
+description: Recover InfluxDB user credentials using the influx CLI.
+menu:
+  influxdb_2_2:
+    name: Recover credentials
+    parent: Manage users
+weight: 106
+products: [oss]
+related:
+  - /influxdb/v2.2/reference/cli/influxd/recovery/
+---
+
+Use the `influxd` command line interface (CLI) to recover user credentials and regain access to your InfluxDB instance:
+- [Update a password](#update-a-password)
+- [List existing users in the InfluxDB instance](#list-existing-users-in-the-influxdb-instance)
+- [Create a user for recovery purposes](#create-a-user-for-recovery-purposes)
+
+## Update a password
+
+To update a password, run the following:
+
+```sh
+influxd recovery user update \
+  --username example-username \
+  --password ExAmPL3-paS5W0rD
+```
+
+{{% note %}}
+**Note:** If you're not sure of the username, [list existing users in the InfluxDB instance](#list-existing-users-in-the-influxdb-instance) or [create a user for recovery purposes](#create-a-user-for-recovery-purposes).
+{{% /note %}}
+
+## List existing users in the InfluxDB instance
+
+To list existing users in the system, run the following:
+
+```sh
+influxd recovery user list
+```
+
+{{% note %}}
+If you used a [custom `bolt-path`](/influxdb/v2.2/reference/config-options/#bolt-path) when starting InfluxDB, provide your custom bolt path to the `influx recovery user list` command with the `--bolt-path` flag.
+{{% /note %}}
+
+## Create a user for recovery purposes
+
+To create a new user for recovery purposes, run the following:
+
+```sh
+influxd recovery user create \
+  --username example-username \
+  --password ExAmPL3-paS5W0rD
+```
diff --git a/content/influxdb/v2.2/users/update-user.md b/content/influxdb/v2.2/users/update-user.md
new file mode 100644
index 000000000..8029a01c0
--- /dev/null
+++ b/content/influxdb/v2.2/users/update-user.md
@@ -0,0 +1,36 @@
+---
+title: Update a user
+seotitle: Update a user in InfluxDB
+description: Update a user in InfluxDB using the InfluxDB UI or the influx CLI.
+menu:
+  influxdb_2_2:
+    name: Update a user
+    parent: Manage users
+weight: 103
+products: [oss]
+---
+
+Use the InfluxDB user interface (UI) or the `influx` command line interface (CLI)
+to update a user.
+
+## Update a user in the InfluxDB UI
+
+{{% note %}}
+User information cannot be updated in the InfluxDB UI.
+{{% /note %}}
+
+## Update a user using the influx CLI
+
+Use the [`influx user update` command](/influxdb/v2.2/reference/cli/influx/user/update)
+to update a user. Updating a user requires the following:
+
+- The user ID _(provided in the output of `influx user list`)_
+
+##### Update the name of a user
+```sh
+# Syntax
+influx user update -i <user-id> -n <new-username>
+
+# Example
+influx user update -i 034ad714fdd6f000 -n janedoe
+```
diff --git a/content/influxdb/v2.2/users/view-users.md b/content/influxdb/v2.2/users/view-users.md
new file mode 100644
index 000000000..dd9394358
--- /dev/null
+++ b/content/influxdb/v2.2/users/view-users.md
@@ -0,0 +1,33 @@
+---
+title: View users
+seotitle: View users in InfluxDB
+description: Review a list of users in InfluxDB using the InfluxDB UI or the influx CLI.
+menu:
+  influxdb_2_2:
+    name: View users
+    parent: Manage users
+weight: 102
+products: [oss]
+---
+
+Use the InfluxDB user interface (UI) or the `influx` command line interface (CLI)
+to view users.
+
+## View users in the InfluxDB UI
+
+{{% note %}}
+There is no list of users in the InfluxDB UI.
+{{% /note %}}
+
+## View users using the influx CLI
+
+Use the [`influx user list` command](/influxdb/v2.2/reference/cli/influx/user/list)
+to view users.
+
+```sh
+influx user list
+```
+
+Filtering options such as filtering by username or ID are available.
+See the [`influx user list` documentation](/influxdb/v2.2/reference/cli/influx/user/list)
+for information about other available flags.
diff --git a/content/influxdb/v2.2/visualize-data/_index.md b/content/influxdb/v2.2/visualize-data/_index.md
new file mode 100644
index 000000000..ec5566206
--- /dev/null
+++ b/content/influxdb/v2.2/visualize-data/_index.md
@@ -0,0 +1,16 @@
+---
+title: Visualize data with the InfluxDB UI
+description: >
+  InfluxDB offers a complete dashboard solution for visualizing your time series data.
+  Create custom dashboards with flexible queries and visualization types.
+influxdb/v2.2/tags: [visualize]
+menu:
+  influxdb_2_2:
+    name: Visualize data
+weight: 5
+---
+
+The InfluxDB user interface (UI) provides tools for building custom dashboards to visualize your data.
+The following articles outline ways to customize and manage dashboards.
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/visualize-data/annotations.md b/content/influxdb/v2.2/visualize-data/annotations.md
new file mode 100644
index 000000000..af3a5942d
--- /dev/null
+++ b/content/influxdb/v2.2/visualize-data/annotations.md
@@ -0,0 +1,68 @@
+---
+title: Use annotations in dashboards
+description: >
+  Add annotations to your InfluxDB dashboards to provide useful, contextual information about single points in time.
+influxdb/v2.2/tags: [labels, annotations]
+menu:
+  influxdb_2_2:
+    name: Use annotations
+    parent: Visualize data
+weight: 105
+---
+
+Add annotations to your dashboards to provide useful, contextual information about single points in time. After an annotation is created, edit the annotation by updating the text or timestamp, or delete the annotation.
+
+- [Create an annotation](#create-an-annotation)
+- [Edit an annotation](#edit-an-annotation)
+- [View or hide annotations](#view-or-hide-annotations)
+- [Delete an annotation](#delete-an-annotation)
+
+{{% note %}}
+Annotations may be useful to highlight operations or anomalies for your team to reference.
+{{% /note %}}
+
+<!-- {{< youtube 5NEplCesNAc >}} --->
+
+## Create an annotation
+
+1. In the navigation menu on the left, select **Boards** (**Dashboards**).
+
+    {{< nav-icon "dashboards" >}}
+
+2. Select an existing dashboard to add the annotation to, or [create a new dashboard](/influxdb/cloud/visualize-data/dashboards/create-dashboard/), and then click the **Annotations** button.
+3. In a dashboard cell, do one of the following:
+   - Press Shift and click the graph at the time you want to annotate.
+   - To add an annotation to a time range, press Shift, click the start time, and then drag your cursor to the end time.
+4. On the **Add Annotation** page:
+
+   1. Verify the time or time range, and update if needed.
+   2. Enter a message (maximum of 255 characters) to associate with the selected time or time range.
+   3. Click **Save Annotation**. The annotation appears in the cell (dotted lines indicate the selected time or time range).
+
+## Edit an annotation
+
+1.  In the navigation menu on the left, select **Boards** (**Dashboards**).
+
+    {{< nav-icon "dashboards" >}}
+
+2. Open the dashboard with the annotation to edit, and then click the annotation to open it.
+3. Update the text (maximum of 255 characters) or timestamp, and then click **Save Annotation**.
+
+## View or hide annotations
+
+By default, annotations are visible.
+
+1.  In the navigation menu on the left, select **Boards** (**Dashboards**).
+
+    {{< nav-icon "dashboards" >}}
+
+2. Open a dashboard with annotations:
+   - To hide annotations, click the **Annotations** button. The button is gray when annotations are hidden.
+   - To show annotations, click the **Annotations** button. The button is purple when annotations are visible.
+
+## Delete an annotation
+
+1.  In the navigation menu on the left, select **Boards** (**Dashboards**).
+
+    {{< nav-icon "dashboards" >}}
+2. Open a dashboard with the annotation to delete, click the dotted annotation line, and then click **Delete Annotation**.
diff --git a/content/influxdb/v2.2/visualize-data/dashboards/_index.md b/content/influxdb/v2.2/visualize-data/dashboards/_index.md
new file mode 100644
index 000000000..ffbb62080
--- /dev/null
+++ b/content/influxdb/v2.2/visualize-data/dashboards/_index.md
@@ -0,0 +1,37 @@
+---
+title: Manage InfluxDB dashboards
+description: Create, edit, and manage custom dashboards in the InfluxDB user interface (UI).
+influxdb/v2.2/tags: [dashboards]
+menu:
+  influxdb_2_2:
+    name: Manage dashboards
+    parent: Visualize data
+weight: 102
+---
+
+Create, edit, and manage dashboards from the **Dashboards** tab in the left navigation.
+
+{{< children >}}
+
+
+## View your dashboard ID
+
+Use the InfluxDB UI or `influx` CLI to view your dashboard ID.
+
+### Dashboard ID in the UI
+
+When viewing a dashboard in the InfluxDB UI, your dashboard ID appears in the URL.
+
+<pre class="highlight">
+http://localhost:8086/orgs/03a2bbf46249a000/dashboards/<span class="bp" style="font-weight:bold;margin:0 .15rem">04b6b15034cc000</span>/...
+</pre>
+
+### Dashboard ID in the CLI
+Use [`influx dashboards`](/influxdb/v2.2/reference/cli/influx/dashboards/) to view a list of dashboards and IDs.
+
+```sh
+> influx dashboards
+ID                  Name
+03a2bbf46249a000    dashboard-1
+03ace3a859669000    dashboard-2
+```
diff --git a/content/influxdb/v2.2/visualize-data/dashboards/control-dashboard.md b/content/influxdb/v2.2/visualize-data/dashboards/control-dashboard.md
new file mode 100644
index 000000000..66c64298f
--- /dev/null
+++ b/content/influxdb/v2.2/visualize-data/dashboards/control-dashboard.md
@@ -0,0 +1,67 @@
+---
+title: Control a dashboard
+seotitle: Control an InfluxDB dashboard
+description: Control an InfluxDB dashboard in the InfluxDB user interface (UI).
+influxdb/v2.2/tags: [dashboards]
+menu:
+  influxdb_2_2:
+    name: Control a dashboard
+    parent: Manage dashboards
+weight: 203
+---
+
+## Control at the dashboard level
+
+Use dashboard controls in the upper left to update your dashboard.
+
+### Add a cell
+
+Click **{{< icon "add-cell" >}} 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.2/visualize-data/explore-metrics/).
+
+### Add a note
+
+1. Click **{{< icon "note" >}} 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.
+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**.
+
+### Select timezone
+
+Click the timezone dropdown to select a timezone to use for the dashboard. Select either the local time (default) or UTC.
+
+{{< img-hd src="/img/influxdb/2-0-controls-timezone.png" alt="Select timezone" />}}
+
+### Manually refresh dashboard
+
+Click the refresh button (**{{< icon "refresh" >}}**) to manually refresh the dashboard's data.
+
+#### Manually refresh a single dashboard cell
+
+1. Click the **{{< icon "gear" >}}** on the dashboard cell you want to refresh.
+2. Click **{{< icon "refresh" >}} Refresh**.
+
+### Select time range
+
+1. Select from the time range options in the dropdown menu.
+
+    {{< img-hd src="/img/influxdb/2-0-controls-time-range.png" alt="Select time range" />}}
+
+2. Select **Custom Time Range** to enter a custom time range with precision up to nanoseconds.
+The default time range is 5 minutes.
+
+  > The custom time range uses the selected timezone (local time or UTC).
+
+### Add variables
+
+Click **Variables** to display variables available for your dashboard. For details, see [Use and manage variables](/influxdb/v2.2/visualize-data/variables/)
+
+### 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.
+
+### Toggle dark mode and light mode
+Click the moon or sun icons to toggle your dashboard between **dark mode** and **light mode.**
+
+{{< img-hd src="/img/influxdb/2-0-controls-dark-light-mode.png" alt="Dark & light mode"/>}}
diff --git a/content/influxdb/v2.2/visualize-data/dashboards/create-dashboard.md b/content/influxdb/v2.2/visualize-data/dashboards/create-dashboard.md
new file mode 100644
index 000000000..6bc90623b
--- /dev/null
+++ b/content/influxdb/v2.2/visualize-data/dashboards/create-dashboard.md
@@ -0,0 +1,58 @@
+---
+title: Create a dashboard
+seotitle: Create an InfluxDB dashboard
+description: >
+  Create a new dashboard or import an existing dashboard in the
+  InfluxDB user interface (UI).
+influxdb/v2.2/tags: [dashboards]
+menu:
+  influxdb_2_2:
+    name: Create a dashboard
+    parent: Manage dashboards
+weight: 201
+---
+
+## Create a new dashboard
+
+1. In the navigation menu on the left, select **Boards** (**Dashboards**).
+
+    {{< nav-icon "dashboards" >}}
+
+2. Click the **{{< icon "plus" >}} 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.
+
+
+**To import an existing dashboard**:
+
+1. In the navigation menu on the left, select **Boards** (**Dashboards**).
+
+    {{< nav-icon "dashboards" >}}
+
+2. Click the **Create Dashboard** menu in the upper right and select **Import Dashboard**.
+3. In the window that appears:
+    - Select **Upload File** to drag-and-drop or select a file.
+    - Select **Paste JSON** to paste in JSON.
+4. Click **Import JSON as Dashboard**.
+
+## Clone a dashboard
+
+1. In the navigation menu on the left, select **Boards** (**Dashboards**).
+
+    {{< nav-icon "dashboards" >}}
+
+2. Hover over the dashboard and click **{{< icon "copy" >}}**.
+3. Click **Clone**. The cloned dashboard opens.
+
+#### Add data to your dashboard
+
+1. From your dashboard, click **{{< icon "add-cell" >}} Add Cell**.
+2. Create a query in the Data Explorer following the instructions in [Explore metrics](/influxdb/v2.2/visualize-data/explore-metrics).
+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.
+   You can also send data to your dashboard directly from the Data Explorer. For details, [Explore metrics](/influxdb/v2.2/visualize-data/explore-metrics).
+
+#### Add a note to your dashboard
+1. From your dashboard, click **{{< icon "note" >}} Add Note** in the upper left.
+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.
+4. Click **Save**.
diff --git a/content/influxdb/v2.2/visualize-data/dashboards/delete-dashboard.md b/content/influxdb/v2.2/visualize-data/dashboards/delete-dashboard.md
new file mode 100644
index 000000000..f6694ab05
--- /dev/null
+++ b/content/influxdb/v2.2/visualize-data/dashboards/delete-dashboard.md
@@ -0,0 +1,23 @@
+---
+title: Delete a dashboard
+seotitle: Delete an InfluxDB dashboard
+description: Delete a dashboard from the InfluxDB user interface (UI).
+influxdb/v2.2/tags: [dashboards]
+menu:
+  influxdb_2_2:
+    parent: Manage dashboards
+weight: 204
+---
+
+To delete a dashboard from the InfluxDB user interface (UI):
+
+1. In the navigation menu on the left, select **Boards** (**Dashboards**).
+
+    {{< nav-icon "dashboards" >}}
+
+2. Hover over the dashboard  in the list of dashboards  and click **{{< icon "trash" >}}**.    
+3. Click **Delete**.
+
+{{% warn %}}
+Deleting a dashboard cannot be undone.
+{{% /warn %}}
diff --git a/content/influxdb/v2.2/visualize-data/dashboards/export-dashboard.md b/content/influxdb/v2.2/visualize-data/dashboards/export-dashboard.md
new file mode 100644
index 000000000..5cdaed41a
--- /dev/null
+++ b/content/influxdb/v2.2/visualize-data/dashboards/export-dashboard.md
@@ -0,0 +1,26 @@
+---
+title: Export a dashboard
+seotitle: Export an InfluxDB dashboard
+description: >
+  Export a dashboard using the InfluxDB user interface (UI).
+influxdb/v2.2/tags: [dashboards]
+menu:
+  influxdb_2_2:
+    name: Export a dashboard
+    parent: Manage dashboards
+weight: 203
+---
+
+InfluxDB lets you export dashboards from the InfluxDB user interface (UI).
+
+1. In the navigation menu on the left, select **Boards** (**Dashboards**).
+
+    {{< nav-icon "dashboards" >}}
+
+2. Hover over a dashboard and click the gear icon (**{{< icon "gear" >}}**),
+   and then select **Export**.
+3. Review the JSON in the window that appears.
+4. Select one of the following options:
+  * **Download JSON**: Download the dashboard as a JSON file.
+  * **Save as template**: Save the JSON as a dashboard template.
+  * **Copy to Clipboard**: Copy the JSON to your clipboard.
diff --git a/content/influxdb/v2.2/visualize-data/labels.md b/content/influxdb/v2.2/visualize-data/labels.md
new file mode 100644
index 000000000..76d86fd01
--- /dev/null
+++ b/content/influxdb/v2.2/visualize-data/labels.md
@@ -0,0 +1,44 @@
+---
+title: Manage labels in the InfluxDB UI
+description: >
+  Labels are a way to add visual metadata to dashboards, tasks, and other items
+  in the InfluxDB UI. View and manage labels in the InfluxDB user interface.
+influxdb/v2.2/tags: [labels]
+menu:
+  influxdb_2_2:
+    name: Manage labels
+    parent: Visualize data
+weight: 104
+---
+
+Labels are a way to add visual metadata to dashboards, tasks, and other items in the InfluxDB UI.
+To manage labels:
+
+- In the navigation menu on the left, select **Settings** > **Labels**.
+
+    {{< nav-icon "settings" >}}
+
+
+#### Create a label
+1. Click **{{< icon "plus" >}} Create Label**.
+2. Enter a **Name** for the label.
+3. Enter a description for the label _(Optional)_.
+4. Select a **Color** for the label.
+5. Click **Create Label**.
+
+#### Edit a label
+1. In the label list view, click the name of the label you would like to edit.
+   The **Edit Label** overlay will appear.
+2. Make the desired changes to the label.
+3. Click **Save Changes**.
+
+#### Delete a label
+1. In the label list view, hover over the label you would like to delete and click **{{< icon "trash" >}}**.
+2. Click **Delete**.
+
+### 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.
+2. Click the {{< icon "add-label" >}} icon that appears below the name.
+   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.
+   Click the label you would like to add.
diff --git a/content/influxdb/v2.2/visualize-data/variables/_index.md b/content/influxdb/v2.2/visualize-data/variables/_index.md
new file mode 100644
index 000000000..a42795735
--- /dev/null
+++ b/content/influxdb/v2.2/visualize-data/variables/_index.md
@@ -0,0 +1,73 @@
+---
+title: Use and manage variables
+seotitle: Use and manage dashboard variables
+description: >
+  Dashboard variables allow you to alter specific components of cells' queries
+  without having to edit the queries, making it easy to interact with your dashboard cells and explore your data.
+menu:
+  influxdb_2_2:
+    parent: Visualize data
+weight: 103
+influxdb/v2.2/tags: [variables]
+---
+
+Dashboard variables let you alter specific components of cells' queries without having to edit the queries,
+making it easy to interact with your dashboard cells and explore your data.
+
+Variables are scoped by organization.
+
+## Use dashboard variables
+Both [predefined dashboard variables](#predefined-dashboard-variables) and [custom dashboard variables](#custom-dashboard-variables)
+are stored in a `v` record associated with each dashboard.
+Reference each variable using dot-notation (e.g. `v.variableName`).
+
+```js
+from(bucket: v.bucket)
+    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
+    |> filter(fn: (r) => r._measurement == v.measurement and r._field == v.field)
+    |> aggregateWindow(every: v.windowPeriod, fn: mean)
+```
+
+When building Flux queries for dashboard cells, view available dashboard variables
+in the **Variables** tab next to the Functions tab.
+
+{{< img-hd src="/img/influxdb/2-0-variables-data-explorer-view.png" />}}
+
+Click a variable name to add it to your query and select a value from the **Value** dropdown.
+
+## Link to dashboards with variables defined in the URL
+
+When you apply a variable to your dashboard, `&vars[variable_name]=value` is appended to the URL so you can share the link with the variables included.
+
+## Predefined dashboard variables
+The InfluxDB user interface (UI) provides the following predefined dashboard variables:
+
+#### v.timeRangeStart
+Specifies the beginning of the queried time range.
+This variable is typically used to define the [`start` parameter](/{{< latest "flux" >}}/stdlib/universe/range#start)
+of the `range()` function.
+
+The **Time Range** selector defines the value of this variable.
+
+#### v.timeRangeStop
+Specifies the end of the queried time range.
+This variable is typically used to define the [`stop` parameter](/{{< latest "flux" >}}/stdlib/universe/range#stop)
+of the `range()` function.
+
+The **Time Range** selector defines the value of this variable.
+It defaults to `now`.
+
+#### v.windowPeriod
+Specifies the period of windowed data.
+This variable is typically used to define the `every` or `period` parameters of the
+[`window()` function](/{{< latest "flux" >}}/stdlib/universe/window)
+in data aggregation operations.
+
+The value of this variable is calculated by analyzing the duration of the Flux
+query it is used within. Queries that fetch data from a longer time range will
+have a larger `v.windowPeriod` duration.
+
+## Custom dashboard variables
+Create, manage, and use custom dashboard variables in the InfluxDB user interface (UI).
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/visualize-data/variables/common-variables.md b/content/influxdb/v2.2/visualize-data/variables/common-variables.md
new file mode 100644
index 000000000..0cd0e445e
--- /dev/null
+++ b/content/influxdb/v2.2/visualize-data/variables/common-variables.md
@@ -0,0 +1,112 @@
+---
+title: Common variable queries
+description: Useful queries to use to populate values in common dashboard variable use cases.
+menu:
+  influxdb_2_2:
+    parent: Use and manage variables
+    name: Common variable queries
+weight: 208
+influxdb/v2.2/tags: [variables]
+---
+
+## List buckets
+List all buckets in the current organization.
+
+_**Flux functions:**
+[buckets()](/{{< latest "flux" >}}/stdlib/universe/buckets/),
+[rename()](/{{< latest "flux" >}}/stdlib/universe/rename/),
+[keep()](/{{< latest "flux" >}}/stdlib/universe/keep/)_
+
+```js
+buckets()
+    |> rename(columns: {"name": "_value"})
+    |> keep(columns: ["_value"])
+```
+
+## List measurements
+List all measurements in a specified bucket.
+
+_**Flux package:** [InfluxDB schema](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/)  
+**Flux functions:** [schema.measurements()](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/measurements/)_
+
+```js
+import "influxdata/influxdb/schema"
+
+schema.measurements(bucket: "bucket-name")
+```
+
+## List fields in a measurement
+List all fields in a specified bucket and measurement.
+
+_**Flux package:** [InfluxDB schema](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/)  
+**Flux functions:** [schema.measurementTagValues()](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/measurementtagvalues/)_
+
+```js
+import "influxdata/influxdb/schema"
+
+schema.measurementTagValues(
+    bucket: "bucket-name",
+    measurement: "measurement-name",
+    tag: "_field",
+)
+```
+
+## List unique tag values
+List all unique tag values for a specific tag in a specified bucket.
+The example below lists all unique values of the `host` tag.
+
+_**Flux package:** [InfluxDB schema](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/)_  
+_**Flux functions:** [schema.tagValues()](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/tagvalues/)_  
+
+```js
+import "influxdata/influxdb/schema"
+
+schema.tagValues(bucket: "bucket-name", tag: "host")
+```
+
+## List Docker containers
+List all Docker containers when using the Docker Telegraf plugin.
+
+_**Telegraf plugin:** [Docker](/{{< latest "telegraf" >}}/plugins/#input-docker)_  
+_**Flux package:** [InfluxDB schema](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/)_  
+_**Flux functions:** [schema.tagValues()](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/tagvalues/)_
+
+```js
+import "influxdata/influxdb/schema"
+
+schema.tagValues(bucket: "bucket-name", tag: "container_name")
+```
+
+## List Kubernetes pods
+List all Kubernetes pods when using the Kubernetes Telegraf plugin.
+
+_**Telegraf plugin:** [Kubernetes](/{{< latest "telegraf" >}}/plugins/#input-kubernetes)_  
+_**Flux package:** [InfluxDB schema](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/)_  
+_**Flux functions:** [schema.measurementTagValues()](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/measurementtagvalues/)_
+
+```js
+import "influxdata/influxdb/schema"
+
+schema.measurementTagValues(
+    bucket: "bucket-name",
+    measurement: "kubernetes_pod_container",
+    tag: "pod_name",
+)
+```
+
+## List Kubernetes nodes
+List all Kubernetes nodes when using the Kubernetes Telegraf plugin.
+
+_**Telegraf plugin:** [Kubernetes](/{{< latest "telegraf" >}}/plugins/#input-kubernetes)_  
+_**Flux package:** [InfluxDB schema](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/)_  
+_**Flux functions:** [schema.measurementTagValues()](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/schema/measurementtagvalues/)_
+
+```js
+import "influxdata/influxdb/schema"
+
+schema.measurementTagValues(
+    bucket: "bucket-name",
+    measurement: "kubernetes_node",
+    tag: "node_name",
+)
+```
diff --git a/content/influxdb/v2.2/visualize-data/variables/create-variable.md b/content/influxdb/v2.2/visualize-data/variables/create-variable.md
new file mode 100644
index 000000000..cc6ccf1dd
--- /dev/null
+++ b/content/influxdb/v2.2/visualize-data/variables/create-variable.md
@@ -0,0 +1,73 @@
+---
+title: Create a variable
+seotitle: Create a dashboard variable
+description: Create dashboard variables in the Data Explorer, from the Organization page, or import a variable.
+menu:
+  influxdb_2_2:
+    parent: Use and manage variables
+weight: 201
+influxdb/v2.2/tags: [variables]
+---
+
+Create dashboard variables in the Data Explorer, from the Settings section, or import a variable.
+**Variable names must be unique.**
+
+There are multiple variable types that provide different means of populating your list of variable values.
+_For information about variable types, see [Variable types](/influxdb/v2.2/visualize-data/variables/variable-types/)._
+
+{{% note %}}
+##### Variable name restrictions
+Variable names must begin with a letter or underscore (`_`).
+
+The following names cannot be used as dashboard variables because they are reserved keywords in Flux:
+`and`, `import`, `not`, `return`, `option`, `test`, `empty`, `in`, `or`, `package`, and `builtin`.
+{{% /note %}}
+
+## Create a variable in the Data Explorer
+
+{{% note %}}
+InfluxData recommends using the Data Explorer to create
+[Query dashboard variables](/influxdb/v2.2/visualize-data/variables/variable-types/#query).
+The [Table visualization type](/influxdb/v2.2/visualize-data/visualization-types/table/) and
+**View Raw Data** option to provide human-readable query results.
+{{% /note %}}
+
+1. Click the **Data Explorer** icon in the sidebar.
+
+    {{< nav-icon "data-explorer" >}}
+
+2. Use the **Query Builder** or **Script Editor** to build a query.
+3. Use the [Table visualization type](/influxdb/v2.2/visualize-data/visualization-types/table/)
+   or enable the **View Raw Data** option to view human-readable query results.
+4. Click **Save As** in the upper right.
+5. In the window that appears, select **Variable**.
+6. Enter a name for your variable in the **Name** field.
+7. Click **Create**.
+
+_For information about common Query variables, see [Common variable queries](/influxdb/v2.2/visualize-data/variables/common-variables/)._
+
+## Create a variable in the Settings section
+
+1. Click the **Settings** icon in the navigation bar.
+
+    {{< nav-icon "settings" >}}
+
+2. Select the **Variables** tab.
+3. Enter a name for your variable.
+4. Select your variable type. For details on each type, see [Variable types](/influxdb/v2.2/visualize-data/variables/variable-types/).
+5. Enter the appropriate variable information.
+6. Click **Create**.
+
+## Import a variable
+InfluxDB lets you import variables exported from InfluxDB in JSON format.
+
+1. Click the **Settings** icon in the navigation bar.
+
+    {{< nav-icon "settings" >}}
+
+2.  Select the **Variables** tab.
+3. Click the **{{< icon "plus" >}} Create Variable** drop-down menu and select **Import Variable**.
+4. In the window that appears:
+  - Select **Upload File** to drag and drop or select a file.
+  - Select **Paste JSON** to paste in JSON.
+6. Click **Import JSON as Variable**.
diff --git a/content/influxdb/v2.2/visualize-data/variables/delete-variable.md b/content/influxdb/v2.2/visualize-data/variables/delete-variable.md
new file mode 100644
index 000000000..2759585d2
--- /dev/null
+++ b/content/influxdb/v2.2/visualize-data/variables/delete-variable.md
@@ -0,0 +1,26 @@
+---
+title: Delete a variable
+seotitle: Delete a dashboard variable
+description: Delete a dashboard variable in the InfluxDB user interface.
+menu:
+  influxdb_2_2:
+    parent: Use and manage variables
+weight: 205
+influxdb/v2.2/tags: [variables]
+---
+
+Delete an existing variable in the InfluxDB user interface (UI).
+
+### Delete a variable
+
+1. Click the **Settings** icon in the navigation bar.
+
+    {{< nav-icon "settings" >}}
+
+2. Select the **Variables** tab.
+3. Hover over a variable, click the **{{< icon "trash" >}}** icon, and **Delete**.
+
+{{% warn %}}
+Once deleted, any dashboards with queries that utilize the variable will no
+longer function correctly.
+{{% /warn %}}
diff --git a/content/influxdb/v2.2/visualize-data/variables/export-variable.md b/content/influxdb/v2.2/visualize-data/variables/export-variable.md
new file mode 100644
index 000000000..c14daaa39
--- /dev/null
+++ b/content/influxdb/v2.2/visualize-data/variables/export-variable.md
@@ -0,0 +1,27 @@
+---
+title: Export a variable
+seotitle: Export a dashboard variable
+description: Export a dashboard variable in the InfluxDB user interface.
+menu:
+  influxdb_2_2:
+    parent: Use and manage variables
+weight: 204
+influxdb/v2.2/tags: [variables]
+---
+Export dashboard variables from the InfluxDB user interface (UI).
+Variables are exported as downloadable JSON files.
+
+### Export a variable
+
+1. Click the **Settings** icon in the navigation bar.
+
+    {{< nav-icon "settings" >}}
+
+2. Select the **Variables** tab.
+3. Hover over a variable in the list, then click the gear icon (**{{< icon "gear" >}}**)
+   and select **Export**.
+4. Review the JSON in the window that appears.
+5. Select one of the following options:
+  * **Download JSON**: Download the dashboard as a JSON file.
+  * **Save as template**: Save the JSON as a dashboard template.
+  * **Copy to Clipboard**: Copy the JSON to your clipboard.
diff --git a/content/influxdb/v2.2/visualize-data/variables/update-variable.md b/content/influxdb/v2.2/visualize-data/variables/update-variable.md
new file mode 100644
index 000000000..83614cd84
--- /dev/null
+++ b/content/influxdb/v2.2/visualize-data/variables/update-variable.md
@@ -0,0 +1,23 @@
+---
+title: Update a variable
+seotitle: Update a dashboard variable
+description: Update a dashboard variable in the InfluxDB user interface.
+menu:
+  influxdb_2_2:
+    parent: Use and manage variables
+weight: 203
+influxdb/v2.2/tags: [variables]
+---
+
+Update an existing dashboard variable's name or JSON content in the InfluxDB user interface (UI).
+
+### Update a variable
+
+1. Click the **Settings** icon in the navigation bar.
+
+    {{< nav-icon "settings" >}}
+
+2. Select the **Variables** tab.
+3. Click a variable's name from the list.
+4. Update the variable's name, type, and associated information.
+5. Click **Submit**.
diff --git a/content/influxdb/v2.2/visualize-data/variables/variable-types.md b/content/influxdb/v2.2/visualize-data/variables/variable-types.md
new file mode 100644
index 000000000..337939513
--- /dev/null
+++ b/content/influxdb/v2.2/visualize-data/variables/variable-types.md
@@ -0,0 +1,97 @@
+---
+title: Variable types
+seotitle: Dashboard variable types
+description: Overview of the types of dashboard variables available in InfluxDB
+menu:
+  influxdb_2_2:
+    parent: Use and manage variables
+weight: 207
+influxdb/v2.2/tags: [variables]
+---
+
+Variable types determine how a variable's list of possible values is populated.
+The following variable types are available:
+
+- [Map](#map)
+- [Query](#query)
+- [CSV](#csv)
+
+### Map
+Map variables use a list of key value pairs in CSV format to map keys to specific values.
+Keys populate the variable's value list in the InfluxDB user interface (UI), but
+values are used when actually processing the query.
+
+The most common use case for map variables is aliasing simple, human-readable keys
+to complex values.
+
+##### Map variable example
+```js
+Juanito MacNeil,"5TKl6l8i4idg15Fxxe4P"
+Astrophel Chaudhary,"bDhZbuVj5RV94NcFXZPm"
+Ochieng Benes,"YIhg6SoMKRUH8FMlHs3V"
+Mila Emile,"o61AhpOGr5aO3cYVArC0"
+```
+
+### Query
+Query variable values are populated using the `_value` column of a Flux query.
+
+##### Query variable example
+```js
+// List all buckets
+buckets()
+    |> rename(columns: {"name": "_value"})
+    |> keep(columns: ["_value"])
+```
+
+_For examples of dashboard variable queries, see [Common variable queries](/influxdb/v2.2/visualize-data/variables/common-variables)._
+
+{{% note %}}
+#### Important things to note about variable queries
+- The variable will only use values from the `_value` column.
+  If the data you’re looking for is in a column other than `_value`, use the
+  [`rename()`](/{{< latest "flux" >}}/stdlib/universe/rename/) or
+  [`map()`](/{{< latest "flux" >}}/stdlib/universe/map/) functions
+  to change the name of that column to `_value`.
+- The variable will only use the first table in the output stream.
+  Use the [`group()` function](/{{< latest "flux" >}}/stdlib/universe/group)
+  to group everything into a single table.
+- Do not use any [predefined dashboard variables](/influxdb/v2.2/visualize-data/variables/#predefined-dashboard-variables) in variable queries.
+{{% /note %}}
+
+### CSV
+CSV variables use a CSV-formatted list to populate variable values.
+A common use case is when the list of potential values is static and cannot be
+queried from InfluxDB.
+
+##### CSV variable examples
+```
+value1, value2, value3, value4
+```
+```
+value1
+value2
+value3
+value4
+```
+
+## Use custom dashboard variables
+
+Use the Flux `v` record and [dot or bracket notation](/{{< latest "flux" >}}/data-types/composite/record/#reference-values-in-a-record) to access custom dashboard variables. 
+
+For example, to use a custom dashboard variable named `exampleVar` in a query,
+reference the variable with `v.exampleVar`:
+
+```js
+from(bucket: "telegraf")
+    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
+    |> filter(fn: (r) => r._measurement == "cpu" )
+    |> filter(fn: (r) => r._field == "usage_user" )
+    |> filter(fn: (r) => r.cpu == v.exampleVar)  
+```
+
+**To select variable values:**
+
+- **In a dashboard:** Use the dashboard variable drop-down menus at the top of your dashboard.
+- **In the Script Editor:** Click the **Variables** tab on the right of the Script Editor, click the name of the variable, and then select the variable value from the drop-down menu.
+
+_For more on using dashboard variables, see [Use and manage variables](/influxdb/v2.2/visualize-data/variables/)._
diff --git a/content/influxdb/v2.2/visualize-data/variables/view-variables.md b/content/influxdb/v2.2/visualize-data/variables/view-variables.md
new file mode 100644
index 000000000..95d16fca8
--- /dev/null
+++ b/content/influxdb/v2.2/visualize-data/variables/view-variables.md
@@ -0,0 +1,31 @@
+---
+title: View variables
+seotitle: View dashboard variables
+description: View dashboard variables in the InfluxDB user interface.
+menu:
+  influxdb_2_2:
+    parent: Use and manage variables
+weight: 203
+influxdb/v2.2/tags: [variables]
+---
+
+View a list of dashboard variables in the InfluxDB user interface (UI) from an organization or from the Data Explorer.
+
+## View variables in the organization
+
+1. Click the **Settings** icon in the navigation bar.
+
+    {{< nav-icon "settings" >}}
+
+3. Select the **Variables** tab.
+
+## View variables in the Data Explorer
+
+1. Click the **Data Explorer** icon in the navigation bar.
+
+    {{< nav-icon "data-explorer" >}}
+
+2. Switch to **Script Editor**.
+3. Click the **Variables** tab to the right of the script editor.
+
+  {{< img-hd src="/img/influxdb/2-0-variables-data-explorer-view.png" />}}
diff --git a/content/influxdb/v2.2/visualize-data/visualization-types/_index.md b/content/influxdb/v2.2/visualize-data/visualization-types/_index.md
new file mode 100644
index 000000000..999975580
--- /dev/null
+++ b/content/influxdb/v2.2/visualize-data/visualization-types/_index.md
@@ -0,0 +1,17 @@
+---
+title: Visualization types
+description: >
+  The InfluxDB UI provides multiple visualization types to visualize your data in
+  a format that makes the most sense for your use case. Use the available customization
+  options to customize each visualization.
+menu:
+  influxdb_2_2:
+    parent: Visualize data
+weight: 105
+---
+
+The InfluxDB UI provides multiple visualization types to visualize your data in
+a format that makes the most sense for your use case. Use the available customization
+options to customize each visualization.
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/visualize-data/visualization-types/band.md b/content/influxdb/v2.2/visualize-data/visualization-types/band.md
new file mode 100644
index 000000000..06d47552a
--- /dev/null
+++ b/content/influxdb/v2.2/visualize-data/visualization-types/band.md
@@ -0,0 +1,174 @@
+---
+title: Band visualization
+list_title: Band
+list_image: /img/influxdb/2-0-visualizations-Band-example.png
+description:
+weight: 201
+menu:
+  influxdb_2_2:
+    name: Band
+    parent: Visualization types
+---
+
+The **Band** visualization displays the upper and lower boundaries for groups of data over time. Boundaries are determined by applying aggregate functions to your data for a specified window period, and then setting the aggregate functions for a specified upper, main, or lower boundary.
+
+## Set up the Band visualization
+
+To see bands (boundaries) in the **Band Plot** visualization, you must set up two or three boundaries for comparison.
+
+### Set up the band visualization in the Data Explorer
+
+1. Click the **Data Explorer** icon in the navigation bar.
+
+    {{< nav-icon "data-explorer" >}}
+
+2. Enter your query (see [Explore data with Flux and the Data Explorer](/influxdb/v2.2/visualize-data/explore-metrics/#explore-data-with-flux-and-the-data-explorer)). You must include the aggregate functions used to determine the Band Plot visualization boundaries in your query.
+3. Select the **Band Plot** option from the visualization dropdown in the upper left, and then click **Customize**.
+4. Under **Data**, select the following:
+   - For **X Column** and **Y Column**, select the columns to display for the x- and y- axes.
+   - For **Time Format**, select the timestamp format to display in the visualization.
+5. Under **Aggregate Functions**, select a function to determine each boundary (column) for comparison (select two or three):
+   - In the **Upper Column Name** field, select a function for the upper boundary.
+   - In the **Main Column Name** field, select a function for the main boundary.
+   - In the **Lower Column Name** field, select a function for the lower boundary.
+6. (Optional) Continue to customize your visualization, including options such as interpolation, color, hover dimension, and y-axis settings. For more information, see [Options](#options) and [Y Axis](#y-axis) below.
+
+    **Tip:** If you do not see shaded boundaries in the **Band Plot** visualization, verify the query window period includes a sufficient number of data points for the selected aggregate function. By default, the window period is automatically set to ten seconds (`10s`). To adjust your window period, select **Custom**, and then enter a supported time unit (for example nanoseconds (`ns`), microseconds (`us`), milliseconds (`ms`), seconds (`s`), or hours (`h`).
+
+{{< img-hd src="/img/influxdb/2-0-visualizations-Band-example.png" alt="Band example" />}}
+
+### Set up the band plot visualization in the Script Editor
+
+1. Click the **Data Explorer** icon in the navigation bar.
+
+    {{< nav-icon "data-explorer" >}}
+
+2. Click **Script Editor**.
+3. Select the **Band Plot** option from the visualization dropdown in the upper left.
+4. Create three aggregate functions: one for the main boundary, one for the upper boundary, and one for the lower boundary. The following example uses the [`mean()`](/{{< latest "flux" >}}/stdlib/universe/mean/), [`max()`](/{{< latest "flux" >}}/stdlib/universe/max/), and [`min()`](/{{< latest "flux" >}}/stdlib/universe/min) functions:
+
+```js
+from(bucket: "bucket_1")
+    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
+    |> filter(fn: (r) => r["_measurement"] == "cpu")
+    |> filter(fn: (r) => r["_field"] == "usage_system")
+    |> filter(fn: (r) => r["cpu"] == "cpu0" or r["cpu"] == "cpu1")
+    |> aggregateWindow(every: 15s, fn: mean, createEmpty: false)
+    |> yield(name: "mean")
+
+from(bucket: "bucket_1")
+    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
+    |> filter(fn: (r) => r["_measurement"] == "cpu")
+    |> filter(fn: (r) => r["_field"] == "usage_system")
+    |> filter(fn: (r) => r["cpu"] == "cpu0" or r["cpu"] == "cpu1")
+    |> aggregateWindow(every: 15s, fn: max, createEmpty: false)
+    |> yield(name: "max")
+
+from(bucket: "bucket_1")
+    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
+    |> filter(fn: (r) => r["_measurement"] == "cpu")
+    |> filter(fn: (r) => r["_field"] == "usage_system")
+    |> filter(fn: (r) => r["cpu"] == "cpu0" or r["cpu"] == "cpu1")
+    |> aggregateWindow(every: 15s, fn: min, createEmpty: false)
+    |> yield(name: "min")
+```
+
+5. (Optional) Customize the name of the yielded results for each function by editing the `name` parameter in the [`yield()`](/{{< latest "flux" >}}/stdlib/universe/yield/) function.
+For example, to change the name of the first function from  `mean` to `Average`, modify the last line to the following:
+  ```js
+  |> yield(name: "Average")
+  ```
+6. Click **Customize** in the upper left.
+7. Under **Aggregate Functions**, enter the functions you created to determine each boundary (column) for comparison. If you changed the `yield` name for any of the functions above, enter the modified name here instead of the function name:
+   - In the **Upper Column Name** field, enter the result set to use for the upper boundary.
+   - In the **Main Column Name** field, enter the result set to use for the main boundary.
+   - In the **Lower Column Name** field, enter the function for the lower boundary.
+7. (Optional) Continue to customize your visualization, including options such as interpolation, color, hover dimension, static legend, and y-axis settings. For more information, see [Options](#options) and [Y Axis](#y-axis) below.
+
+### Customize column names
+
+## Band behavior
+
+Like a line graph, the band visualization shows how values change over time. Additionally, it displays upper and lower "bands" for the measurements.
+
+For example, in the band chart above, the lines represent the mean `usage_system` values for the `cpu` measurement for `cpu0` and `cpu1`. The upper and lower limits of the bands are defined by the `max` and `min` aggregate functions, respectively.
+
+## Band controls
+
+To view **Band** controls, click **{{< icon "gear" >}} Customize** next to the visualization dropdown.
+
+###### Data
+
+- **X Column**: Select a column to display on the x-axis.
+- **Y Column**: Select a column to display on the y-axis.
+- **Time Format**: Select the time format. Options include:
+    {{< ui/timestamp-formats >}}
+
+###### Aggregate functions
+
+- **Upper Column Name**: Aggregate function to display for upper bounds of data.
+- **Main Column Name**: Aggregate function to display for main graph line.
+- **Lower Column Name**: Aggregate function to display for lower bounds of data.
+
+###### Options
+
+- **Interpolation**:
+  - **Linear**: Display a time series in a line graph.
+  - **Smooth**: Display a time series in a line graph with smooth point interpolation.
+  - **Step**: Display a time series in a staircase graph.
+- **Line Colors**: Select a color scheme to use for your graph.
+- **Hover Dimension**: Select the data to display in the tooltip when you hover over the graph:
+  - **auto** or **X-Axis**: Show all points with the same x value along the y-axis.
+  - **Y-Axis**: Show all points with the same y value along the x-axis.
+  - **X-Y Axis**: Show only the point being currently hovered over.
+
+###### X-Axis
+
+- **Generate X-Axis Tick Marks**: Select the method to generate x-axis tick marks:
+  - **Auto**: Select to automatically generate tick marks.
+  - **Custom**: To customize the number of x-axis tick marks, select this option, and then enter the following:
+    - **Total Tick Marks**: Enter the total number of timestamp ticks to display.
+    - **Start Tick Marks At**: Enter the time, in RFC3339 format, to start displaying ticks. Use the **Date Picker** field to automatically generate an RFC3339 formatted timestamp for this field.
+    - **Tick Mark Interval**: Enter the number of milliseconds in between each timestamp tick.
+
+###### Y-Axis
+
+- **Y Axis Label**: Enter the label for the y-axis.
+- **Y-Value Unit Prefix**: Select the prefix to add to the y-value:
+  - **None**: Select to add no prefix.
+  - **SI**: (default) Select to add an International System of Units (SI) or metric prefix.
+  - **Binary**: Select to add a binary multiple prefix.
+- **Y Axis Prefix**: Enter the prefix to add to the y-value.
+- **Y Axis Suffix**: Enter the suffix to add to the y-value.
+- **Generate Y-Axis Tick Marks**: Select the method to generate y-axis tick marks:
+  - **Auto**: Select to automatically generate tick marks.
+  - **Custom**: To customize the number of y-axis tick marks, select this option, and then enter  the following:
+    - **Total Tick Marks**: Enter the total number of ticks to display.
+    - **Start Tick Marks At**: Enter the value to start ticks at.
+    - **Tick Mark Interval**: Enter the interval in between each tick.
+- **Y Axis Domain**: Select the method to generate the y-axis value range:
+  - **Auto**: Select to automatically determine the value range based on values in the data set.
+  - **Custom**: To customize the y-axis domain, manually specify the minimum y-axis value, maximum y-axis value, or range by including both.
+    - **Min**: Enter the minimum y-axis value.
+    - **Max**: Enter the maximum y-axis value.
+
+###### Legend
+
+- **Hover Legend**:
+  - **Hide**: Hide the legend that appears upon hover.
+  - **Show**: Show the legend upon hover.
+    - **Orientation**: Select the orientation of the legend:
+      - **Horizontal**: Select to display the legend horizontally.
+      - **Vertical**: Select to display the legend vertically.
+    - **Opacity**: Adjust the hover legend opacity using the slider.
+    - **Colorize Rows**: Select to display hover legend rows in colors.
+- **Static Legend**:
+  - **Hide**: Hide the static legend.
+  - **Show**: Always show the static legend.
+    - **Orientation**: Select the orientation of the legend:
+      - **Horizontal**: Select to display the legend horizontally.
+      - **Vertical**: Select to display the legend vertically.
+    - **Opacity**: Adjust the static legend opacity using the slider.
+    - **Colorize Rows**: Select to display static legend rows in colors.
+    - **Displayed Value**: Select **Latest Y Axis** or **Latest X Axis** to determine whether the y or x axis appears on the legend.
+    - **Height**: Adjust the height of the static legend using the slider.
diff --git a/content/influxdb/v2.2/visualize-data/visualization-types/gauge.md b/content/influxdb/v2.2/visualize-data/visualization-types/gauge.md
new file mode 100644
index 000000000..ac07a71a3
--- /dev/null
+++ b/content/influxdb/v2.2/visualize-data/visualization-types/gauge.md
@@ -0,0 +1,63 @@
+---
+title: Gauge visualization
+list_title: Gauge
+list_image: /img/influxdb/2-0-visualizations-gauge-example.png
+description: >
+  The Gauge view displays the single value most recent value for a time series in a gauge view.
+weight: 201
+menu:
+  influxdb_2_2:
+    name: Gauge
+    parent: Visualization types
+---
+
+The **Gauge** visualization displays the most recent value for a time series in a gauge.
+
+{{< img-hd src="/img/influxdb/2-0-visualizations-gauge-example-8.png" alt="Gauge example" />}}
+
+Select the **Gauge** option from the visualization dropdown in the upper left.
+
+## Gauge behavior
+The gauge visualization displays a single numeric data point within a defined spectrum (_default is 0-100_).
+It uses the latest point in the first table (or series) returned by the query.
+
+{{% note %}}
+#### Queries should return one table
+Flux does not guarantee the order in which tables are returned.
+If a query returns multiple tables (or series), the table order can change between query executions
+and result in the Gauge displaying inconsistent data.
+For consistent results, the Gauge query should return a single table.
+{{% /note %}}
+
+## Gauge Controls
+To view **Gauge** controls, click **{{< icon "gear" >}} Customize** next to
+the visualization dropdown.
+
+- **Prefix**: Prefix to add to the gauge.
+- **Suffix**: Suffix to add to the gauge.
+- **Decimal Places**: The number of decimal places to display for the gauge.
+  - **Auto** or **Custom**: Enable or disable auto-setting.
+
+###### Colorized Thresholds
+- **Base Color**: Select a base or background color from the selection list.
+- **Add a Threshold**: Change the color of the gauge based on the current value.
+  - **Value is**: Enter the value at which the gauge should appear in the selected color.
+    Choose a color from the dropdown menu next to the value.
+
+## Gauge examples
+Gauge visualizations are useful for showing the current value of a metric and displaying
+where it falls within a spectrum.
+
+### Steam pressure gauge
+The following example queries sensor data that tracks the pressure of steam pipes
+in a facility and displays it as a gauge.
+
+###### Query pressure data from a specific sensor
+```js
+from(bucket: "example-bucket")
+    |> range(start: -1m)
+    |> filter(fn: (r) => r._measurement == "steam-sensors" and r._field == "psi" <INVALID_OP> r.sensorID == "a211i")
+```
+
+###### Visualization options for pressure gauge
+{{< img-hd src="/img/influxdb/2-0-visualizations-gauge-pressure-8.png" alt="Pressure guage example" />}}
diff --git a/content/influxdb/v2.2/visualize-data/visualization-types/graph-single-stat.md b/content/influxdb/v2.2/visualize-data/visualization-types/graph-single-stat.md
new file mode 100644
index 000000000..f9ec0f898
--- /dev/null
+++ b/content/influxdb/v2.2/visualize-data/visualization-types/graph-single-stat.md
@@ -0,0 +1,137 @@
+---
+title: Graph + Single Stat visualization
+list_title: Graph + Single Stat
+list_image: /img/influxdb/2-0-visualizations-line-graph-single-stat-example.png
+description: >
+  The Graph + Single Stat view displays the specified time series in a line graph
+  and overlays the single most recent value as a large numeric value.
+weight: 202
+menu:
+  influxdb_2_2:
+    name: Graph + Single Stat
+    parent: Visualization types
+related:
+  - /influxdb/v2.2/visualize-data/visualization-types/graph
+  - /influxdb/v2.2/visualize-data/visualization-types/single-stat
+---
+
+The **Graph + Single Stat** view displays the specified time series in a line graph
+and overlays the single most recent value as a large numeric value.
+
+{{< img-hd src="/img/influxdb/2-0-visualizations-line-graph-single-stat-example-8.png" alt="Line Graph + Single Stat example" />}}
+
+Select the **Graph + Single Stat** option from the visualization dropdown in the upper left.
+
+## Graph + Single Stat behavior
+The Graph visualization color codes each table (or series) in the queried data set.
+When multiple series are present, it automatically assigns colors based on the selected [Line Colors option](#options).
+
+The Single Stat visualization displays a single numeric data point.
+It uses the latest point in the first table (or series) returned by the query.
+
+{{% note %}}
+#### Queries should return one table
+Flux does not guarantee the order in which tables are returned.
+If a query returns multiple tables (or series), the table order can change between query executions
+and result in the Single Stat visualization displaying inconsistent data.
+For consistent Single Stat results, the query should return a single table.
+{{% /note %}}
+
+## Graph + Single Stat Controls
+To view **Graph + Single Stat** controls, click **{{< icon "gear" >}} Customize** next to
+the visualization dropdown.
+
+###### Data
+- **X Column**: Select a column to display on the x-axis.
+- **Y Column**: Select a column to display on the y-axis.
+- **Time Format**: Select the time format. Options include:
+    {{< ui/timestamp-formats >}}
+
+###### Options
+- **Line Colors**: Select a color scheme to use for your graph.
+- **Shade Area Below Lines**: Shade in the area below the graph lines.
+- **Hover Dimension**: Select the data to display in the tooltip when you hover over the graph:
+  - **auto** or **X Axis**: Show all points with the same x value along the y-axis.
+  - **Y Axis**: Show all points with the same y value along the x-axis.
+  - **X & Y Axis**: Show only the point currently being hovered over.
+
+###### X Axis
+- **Generate X-Axis Tick Marks**: Select the method to generate x-axis tick marks:
+  - **Auto**: Select to automatically generate tick marks.
+  - **Custom**: To customize the number of x-axis tick marks, select this option, and then enter the following:
+    - **Total Tick Marks**: Enter the total number of ticks to display.
+    - **Start Tick Marks At**: Enter the value to start ticks at.
+    - **Tick Mark Interval**: Enter the interval in between each tick.
+
+###### Y Axis
+- **Y Axis Label**: Label for the y-axis.
+- **Y Value Unit Prefix**:
+  - **None**: No prefix.
+  - **SI**: International System of Units (SI) or metric prefix.
+  - **Binary**: Binary multiple prefix.
+- **Y Axis Prefix**: Prefix to be added to y-value.
+- **Y Axis Suffix**: Suffix to be added to y-value.
+- **Generate Y-Axis Tick Marks**: Select the method to generate y-axis tick marks:
+  - **Auto**: Select to automatically generate tick marks.
+  - **Custom**: To customize the number of y-axis tick marks, select this option, and then enter  the following:
+    - **Total Tick Marks**: Enter the total number of ticks to display.
+    - **Start Tick Marks At**: Enter the value to start ticks at.
+    - **Tick Mark Interval**: Enter the interval in between each tick.
+- **Y Axis Domain**: The y-axis value range.
+  - **Auto**: Automatically determine the value range based on values in the data set.
+  - **Custom**: Manually specify the minimum y-axis value, maximum y-axis value, or range by including both.
+      - **Min**: Minimum y-axis value.
+      - **Max**: Maximum y-axis value.
+- **Positioning**:
+  - **Overlaid**: Display graph lines overlaid on each other.
+  - **Stacked**: Display graph lines stacked on top of each other.
+
+###### Customize Single-Stat  
+- **Prefix**: Prefix to be added to the single stat.
+- **Suffix**: Suffix to be added to the single stat.
+- **Decimal Places**: The number of decimal places to display for the single stat.
+  - **Auto** or **Custom**: Enable or disable auto-setting.
+
+###### Colorized Thresholds
+- **Base Color**: Select a base or background color from the selection list.
+- **Add a Threshold**: Change the color of the single stat based on the current value.
+  - **Value is**: Enter the value at which the single stat should appear in the selected color.
+    Choose a color from the dropdown menu next to the value.
+- **Colorization**: Choose **Text** for the single stat to change color based on the configured thresholds.
+  Choose **Background** for the background of the graph to change color based on the configured thresholds.
+
+###### Legend
+- **Hover Legend**:
+  - **Hide**: Hide the legend that appears upon hover.
+  - **Show**: Show the legend upon hover.
+    - **Orientation**: Select the orientation of the legend:
+      - **Horizontal**: Select to display the legend horizontally.
+      - **Vertical**: Select to display the legend vertically.
+    - **Opacity**: Adjust the hover legend opacity using the slider.
+    - **Colorize Rows**: Select to display hover legend rows in colors.
+- **Static Legend**:
+  - **Hide**: Hide the static legend.
+  - **Show**: Always show the static legend.
+    - **Orientation**: Select the orientation of the legend:
+      - **Horizontal**: Select to display the legend horizontally.
+      - **Vertical**: Select to display the legend vertically.
+    - **Opacity**: Adjust the static legend opacity using the slider.
+    - **Colorize Rows**: Select to display static legend rows in colors.
+    - **Displayed Value**: Select **Latest Y Axis** or **Latest X Axis** to determine whether the y or x axis appears on the legend.
+    - **Height**: Adjust the height of the static legend using the slider.
+
+## Graph + Single Stat examples
+The primary use case for the Graph + Single Stat visualization is to show the current or latest
+value as well as historical values.
+
+### Show current value and historical values
+The following example shows the current percentage of memory used as well as memory usage over time:
+
+###### Query memory usage percentage
+```js
+from(bucket: "example-bucket")
+    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+```
+###### Memory allocations percentage visualization with static legend
+{{< img-hd src="/img/influxdb/2-0-visualizations-graph-single-stat-mem-8.png" alt="Graph + Single Stat Memory Usage Example" />}}
diff --git a/content/influxdb/v2.2/visualize-data/visualization-types/graph.md b/content/influxdb/v2.2/visualize-data/visualization-types/graph.md
new file mode 100644
index 000000000..8938e3625
--- /dev/null
+++ b/content/influxdb/v2.2/visualize-data/visualization-types/graph.md
@@ -0,0 +1,113 @@
+---
+title: Graph visualization
+list_title: Graph
+list_image: /img/influxdb/2-0-visualizations-line-graph-example.png
+description: >
+  The Graph view lets you select from multiple graph types such as line graphs and bar graphs *(Coming)*.
+weight: 201
+menu:
+  influxdb_2_2:
+    name: Graph
+    parent: Visualization types
+---
+
+The Graph visualization provides several types of graphs, each configured through
+the [Graph controls](#graph-controls).
+
+{{< img-hd src="/img/influxdb/2-0-visualizations-line-graph-example-8.png" alt="Line Graph example" />}}
+
+Select the **Graph** option from the visualization dropdown in the upper left.
+
+## Graph behavior
+The Graph visualization color codes each table (or series) in the queried data set.
+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
+To view **Graph** controls, click **{{< icon "gear" >}} Customize** next to
+the visualization dropdown.
+
+###### Data
+- **X Column**: Select a column to display on the x-axis.
+- **Y Column**: Select a column to display on the y-axis.
+- **Time Format**: Select the time format. Options include:
+    {{< ui/timestamp-formats >}}
+
+###### Options
+- **Interpolation**: Select from the following options:
+  - **Line**: Display a time series in a line graph
+  - **Smooth**: Display a time series in a line graph with smooth point interpolation.
+  - **Step**: Display a time series in a staircase graph.
+  <!-- - **Bar**: Display the specified time series using a bar chart. -->
+  <!-- - **Stacked**: Display multiple time series bars as segments stacked on top of each other. -->
+- **Line Colors**: Select a color scheme to use for your graph.
+- **Shade Area Below Lines**: Shade in the area below the graph lines.
+- **Hover Dimension**: Select the data to display in the tooltip when you hover over the graph:
+  - **auto** or **X Axis**: Show all points with the same x value along the y-axis.
+  - **Y Axis**: Show all points with the same y value along the x-axis.
+  - **X & Y Axis**: Show only the point currently being hovered over.
+
+###### X Axis
+- **Generate X-Axis Tick Marks**: Select the method to generate x-axis tick marks:
+  - **Auto**: Select to automatically generate tick marks.
+  - **Custom**: To customize the number of x-axis tick marks, select this option, and then enter the following:
+    - **Total Tick Marks**: Enter the total number of ticks to display.
+    - **Start Tick Marks At**: Enter the value to start ticks at.
+    - **Tick Mark Interval**: Enter the interval in between each tick.
+
+###### Y Axis
+- **Y Axis Label**: Label for the y-axis.
+- **Y Axis Prefix**: Prefix to be added to y-value.
+- **Y Axis Suffix**: Suffix to be added to y-value.
+- **Generate Y-Axis Tick Marks**: Select the method to generate y-axis tick marks:
+  - **Auto**: Select to automatically generate tick marks.
+  - **Custom**: To customize the number of y-axis tick marks, select this option, and then enter  the following:
+    - **Total Tick Marks**: Enter the total number of ticks to display.
+    - **Start Tick Marks At**: Enter the value to start ticks at.
+    - **Tick Mark Interval**: Enter the interval in between each tick.
+- **Y Axis Domain**: The y-axis value range.
+  - **Auto**: Automatically determine the value range based on values in the data set.
+  - **Custom**: Manually specify the minimum y-axis value, maximum y-axis value, or range by including both.
+      - **Min**: Minimum y-axis value.
+      - **Max**: Maximum y-axis value.
+- **Positioning**:
+  - **Overlaid**: Display graph lines overlaid on each other.
+  - **Stacked**: Display graph lines stacked on top of each other.
+
+###### Legend
+- **Hover Legend**:
+  - **Hide**: Hide the legend that appears upon hover.
+  - **Show**: Show the legend upon hover.
+    - **Orientation**: Select the orientation of the legend:
+      - **Horizontal**: Select to display the legend horizontally.
+      - **Vertical**: Select to display the legend vertically.
+    - **Opacity**: Adjust the hover legend opacity using the slider.
+    - **Colorize Rows**: Select to display hover legend rows in colors.
+- **Static Legend**:
+  - **Hide**: Hide the static legend.
+  - **Show**: Always show the static legend.
+    - **Orientation**: Select the orientation of the legend:
+      - **Horizontal**: Select to display the legend horizontally.
+      - **Vertical**: Select to display the legend vertically.
+    - **Opacity**: Adjust the static legend opacity using the slider.
+    - **Colorize Rows**: Select to display static legend rows in colors.
+    - **Displayed Value**: Select **Latest Y Axis** or **Latest X Axis** to determine whether the y or x axis appears on the legend.
+    - **Height**: Adjust the height of the static legend using the slider.
+
+## Graph Examples
+
+##### Graph with linear interpolation and static legend
+{{< img-hd src="/img/influxdb/2-0-visualizations-graph-linear-static.png" alt="Line Graph example" />}}
+
+##### Graph with smooth interpolation and hover legend
+{{< img-hd src="/img/influxdb/2-0-visualizations-graph-smooth-hover.png" alt="Step-Plot Graph example" />}}
+
+##### Graph with step interpolation and no visible legend
+{{< img-hd src="/img/influxdb/2-0-visualizations-line-graph-step-example-8.png" alt="Step-Plot Graph example" />}}
+
+<!-- ##### Stacked Graph example
+{{< img-hd src="/img/2-0-visualizations-stacked-graph-example.png" alt="Stacked Graph example" />}} -->
+
+<!-- ##### Bar Graph example
+{{< img-hd src="/img/2-0-visualizations-bar-graph-example.png" alt="Bar Graph example" />}} -->
diff --git a/content/influxdb/v2.2/visualize-data/visualization-types/heatmap.md b/content/influxdb/v2.2/visualize-data/visualization-types/heatmap.md
new file mode 100644
index 000000000..ef3a08ab5
--- /dev/null
+++ b/content/influxdb/v2.2/visualize-data/visualization-types/heatmap.md
@@ -0,0 +1,127 @@
+---
+title: Heatmap visualization
+list_title: Heatmap
+list_image: /img/influxdb/2-0-visualizations-heatmap-example.png
+description: >
+  A Heatmap displays the distribution of data on an x and y axes where color
+  represents different concentrations of data points.
+weight: 202
+menu:
+  influxdb_2_2:
+    name: Heatmap
+    parent: Visualization types
+related:
+  - /influxdb/v2.2/visualize-data/visualization-types/scatter
+---
+
+A **Heatmap** displays the distribution of data on an x and y axes where color
+represents different concentrations of data points.
+
+{{< img-hd src="/img/influxdb/2-0-visualizations-heatmap-example.png" alt="Heatmap example" />}}
+
+Select the **Heatmap** option from the visualization dropdown in the upper left.
+
+## Heatmap behavior
+Heatmaps divide data points into "bins" – segments of the visualization with upper
+and lower bounds for both [X and Y axes](#data).
+The [Bin Size option](#options) determines the bounds for each bin.
+The total number of points that fall within a bin determine the its value and color.
+Warmer or brighter colors represent higher bin values or density of points within the bin.
+
+## Heatmap Controls
+To view **Heatmap** controls, click **{{< icon "gear" >}} Customize** next to
+the visualization dropdown.
+
+###### Data
+- **X Column**: Select a column to display on the x-axis.
+- **Y Column**: Select a column to display on the y-axis.
+- **Time Format**: Select the time format. Options include:
+    {{< ui/timestamp-formats >}}
+
+###### Options
+- **Color Scheme**: Select a color scheme to use for your heatmap.
+- **Bin Size**: Specify the size of each bin. Default is 10.
+
+###### X Axis
+- **X Axis Label**: Label for the x-axis.
+- **Generate X-Axis Tick Marks**: Select the method to generate x-axis tick marks:
+  - **Auto**: Select to automatically generate tick marks.
+  - **Custom**: To customize the number of x-axis tick marks, select this option, and then enter the following:
+    - **Total Tick Marks**: Enter the total number of ticks to display.
+    - **Start Tick Marks At**: Enter the value to start ticks at.
+    - **Tick Mark Interval**: Enter the interval in between each tick.
+- **X Axis Domain**: The x-axis value range.
+  - **Auto**: Automatically determine the value range based on values in the data set.
+  - **Custom**: Manually specify the minimum y-axis value, maximum y-axis value, or range by including both.
+      - **Min**: Minimum x-axis value.
+      - **Max**: Maximum x-axis value.
+
+###### Y Axis
+- **Y Axis Label**: Label for the y-axis.
+- **Y Tick Prefix**: Prefix to be added to y-value.
+- **Y Tick Suffix**: Suffix to be added to y-value.
+- **Generate Y-Axis Tick Marks**: Select the method to generate y-axis tick marks:
+  - **Auto**: Select to automatically generate tick marks.
+  - **Custom**: To customize the number of y-axis tick marks, select this option, and then enter  the following:
+    - **Total Tick Marks**: Enter the total number of ticks to display.
+    - **Start Tick Marks At**: Enter the value to start ticks at.
+    - **Tick Mark Interval**: Enter the interval in between each tick.
+- **Y Axis Domain**: The y-axis value range.
+  - **Auto**: Automatically determine the value range based on values in the data set.
+  - **Custom**: Manually specify the minimum y-axis value, maximum y-axis value, or range by including both.
+      - **Min**: Minimum y-axis value.
+      - **Max**: Maximum y-axis value.
+
+###### Legend
+- **Legend Orientation**: Select the orientation of the legend that appears upon hover:
+  - **Horizontal**: Select to display the legend horizontally.
+  - **Vertical**: Select to display the legend vertically.
+- **Opacity**: Adjust the legend opacity using the slider.
+- **Colorize Rows**: Select to display legend rows in colors.
+
+## Heatmap examples
+
+### Cross-measurement correlation
+The following example explores possible correlation between CPU and Memory usage.
+It uses data collected with the Telegraf [Mem](/{{< latest "telegraf" >}}/plugins//#mem)
+and [CPU](/{{< latest "telegraf" >}}/plugins//#cpu) input plugins.
+
+###### Join CPU and memory usage
+The following query joins CPU and memory usage on `_time`.
+Each row in the output table contains `_value_cpu` and `_value_mem` columns.
+
+```js
+cpu = from(bucket: "example-bucket")
+    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_system" and r.cpu == "cpu-total")
+
+mem = from(bucket: "example-bucket")
+    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+
+join(tables: {cpu: cpu, mem: mem}, on: ["_time"], method: "inner")
+```
+
+###### Use a heatmap to visualize correlation
+In the Heatmap visualization controls, `_value_cpu` is selected as the [X Column](#data)
+and `_value_mem` is selected as the [Y Column](#data).
+The domain for each axis is also customized to account for the scale difference
+between column values.
+
+{{< img-hd src="/img/influxdb/2-0-visualizations-heatmap-correlation.png" alt="Heatmap correlation example" />}}
+
+
+## Important notes
+
+### Differences between a heatmap and a scatter plot
+Heatmaps and [Scatter plots](/influxdb/v2.2/visualize-data/visualization-types/scatter/)
+both visualize the distribution of data points on X and Y axes.
+However, in certain cases, heatmaps provide better visibility into point density.
+
+For example, the dashboard cells below visualize the same query results:
+
+{{< img-hd src="/img/influxdb/2-0-visualizations-heatmap-vs-scatter.png" alt="Heatmap vs Scatter plot" />}}
+
+The heatmap indicates isolated high point density, which isn't visible in the scatter plot.
+In the scatter plot visualization, points that share the same X and Y coordinates
+appear as a single point.
diff --git a/content/influxdb/v2.2/visualize-data/visualization-types/histogram.md b/content/influxdb/v2.2/visualize-data/visualization-types/histogram.md
new file mode 100644
index 000000000..1ff6997ba
--- /dev/null
+++ b/content/influxdb/v2.2/visualize-data/visualization-types/histogram.md
@@ -0,0 +1,84 @@
+---
+title: Histogram visualization
+list_title: Histogram
+list_image: /img/influxdb/2-0-visualizations-histogram-example.png
+description: >
+  A histogram is a way to view the distribution of data.
+  The y-axis is dedicated to count, and the x-axis is divided into bins.
+weight: 202
+menu:
+  influxdb_2_2:
+    name: Histogram
+    parent: Visualization types
+---
+
+A histogram is a way to view the distribution of data.
+The y-axis is dedicated to count, and the X-axis is divided into bins.
+
+{{< img-hd src="/img/influxdb/2-0-visualizations-histogram-example.png" alt="Histogram example" />}}
+
+Select the **Histogram** option from the visualization dropdown in the upper left.
+
+## Histogram behavior
+The Histogram visualization is a bar graph that displays the number of data points
+that fall within "bins" – segments of the X axis with upper and lower bounds.
+Bin thresholds are determined by dividing the width of the X axis by the number
+of bins set using the [Bins option](#options).
+Data within bins can be further grouped or segmented by selecting columns in the
+[Group By option](#options).
+
+{{% note %}}
+The Histogram visualization automatically bins, segments, and counts data.
+To work properly, query results **should not** be structured as histogram data.
+{{% /note %}}
+
+## Histogram Controls
+To view **Histogram** controls, click **{{< icon "gear" >}} Customize** next to
+the visualization dropdown.
+
+###### Data
+- **X Column**: The column to select data from.
+- **Group By**: The column to group by.
+
+###### Options
+- **Color Scheme**: Select a color scheme to use for your graph.
+- **Positioning**: Select **Stacked** to stack groups in a bin on top of each other.
+  Select **Overlaid** to overlay groups in each bin.
+- **Bins**: Enter a number of bins to divide data into or select Auto to automatically
+  calculate the number of bins.
+  - **Auto** or **Custom**: Enable or disable auto-setting.
+
+###### X Axis
+- **X Axis Label**: Label for the x-axis.
+- **X Axis Domain**: The x-axis value range.
+  - **Auto**: Automatically determine the value range based on values in the data set.
+  - **Custom**: Manually specify the value range of the x-axis.
+      - **Min**: Minimum x-axis value.
+      - **Max**: Maximum x-axis value.
+
+###### Legend
+- **Legend Orientation**: Select the orientation of the legend that appears upon hover:
+  - **Horizontal**: Select to display the legend horizontally.
+  - **Vertical**: Select to display the legend vertically.
+- **Opacity**: Adjust the legend opacity using the slider.
+- **Colorize Rows**: Select to display legend rows in colors.
+
+## Histogram examples
+
+### View error counts by severity over time
+The following example uses the Histogram visualization to show the number of errors
+"binned" by time and segmented by severity.
+_It utilizes data from the [Telegraf Syslog plugin](/{{< latest "telegraf" >}}/plugins//#syslog)._
+
+##### Query for errors by severity code
+```js
+from(bucket: "example-bucket")
+    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
+    |> filter(fn: (r) => r._measurement == "syslog" and r._field == "severity_code")
+```
+
+##### Histogram settings
+In the Histogram visualization options, select `_time` as the [X Column](#data)
+and `severity` as the [Group By](#data) option:
+
+{{< img-hd src="/img/influxdb/2-0-visualizations-histogram-errors.png" alt="Errors histogram" />}}
diff --git a/content/influxdb/v2.2/visualize-data/visualization-types/mosaic.md b/content/influxdb/v2.2/visualize-data/visualization-types/mosaic.md
new file mode 100644
index 000000000..ffce50fbe
--- /dev/null
+++ b/content/influxdb/v2.2/visualize-data/visualization-types/mosaic.md
@@ -0,0 +1,76 @@
+---
+title: Mosaic visualization
+list_title: Mosaic
+list_image: /img/influxdb/2-0-visualizations-mosaic-example.png
+description: >
+  The Mosaic visualization displays state changes in your time series data.
+  This visualization type is useful when you want to show changes in string-based states over time.
+weight: 202
+menu:
+  influxdb_2_2:
+    name: Mosaic
+    parent: Visualization types
+---
+
+The **Mosaic** visualization displays state changes in your time series data.
+This visualization type is useful when you want to show changes in string-based states over time.
+
+{{< img-hd src="/img/influxdb/2-0-visualizations-mosaic-example.png" alt="Mosaic data visualization" />}}
+
+Select the **Mosaic** option from the visualization dropdown in the upper left.
+
+## Mosaic behavior
+The mosaic visualization displays colored tiles based on string values in a specified column.
+Each unique string value is represented by a different color.
+
+## Mosaic controls
+To view **Mosaic** controls, click **{{< icon "gear" >}} Customize** next to the visualization dropdown.
+
+###### Data
+- **Fill Column**: Select a column to fill in the mosaic tiles.
+- **X Column**: Select a column to display on the x-axis.
+- **Y Column**: Select one or more columns to display on the y-axis.
+- **Time Format**: Select the time format. Options include:
+    {{< ui/timestamp-formats >}}
+
+###### Options
+- **Color Scheme**: Select a color scheme to use for your graph.
+
+###### X Axis
+- **X Axis Label**: Enter a label for the x-axis.
+- **Generate X-Axis Tick Marks**: Select the method to generate x-axis tick marks:
+  - **Auto**: Select to automatically generate tick marks.
+  - **Custom**: To customize the number of x-axis tick marks, select this option, and then enter the following:
+    - **Total Tick Marks**: Enter the total number of timestamp ticks to display.
+    - **Start Tick Marks At**: Enter the time, in RFC3339 format, to start displaying ticks. Use the **Date Picker** field to automatically generate an RFC3339 formatted timestamp for this field.
+    - **Tick Mark Interval**: Enter the number of milliseconds in between each timestamp tick.
+
+###### Y Axis
+- **Y Axis Label**: Enter a label for the y-axis.
+- **Y Label Separator**: If there's more than one column on the y-axis, enter a delimiter to separate the label, such as a comma or space. If there's no separator specified, the labels are a continuous string of all y columns.
+- **Generate Y-Axis Tick Marks**: Select the method to generate y-axis tick marks:
+  - **Auto**: Select to automatically generate tick marks.
+  - **Custom**: To customize the number of y-axis tick marks, select this option, and then enter the following:
+    - **Total Tick Marks**: Enter the total number of ticks to display.
+    - **Start Tick Marks At**: Enter the value to start ticks at.
+    - **Tick Mark Interval**: Enter the interval in between each tick.
+
+###### Legend
+- **Legend Orientation**: Select the orientation of the legend that appears upon hover:
+  - **Horizontal**: Select to display the legend horizontally.
+  - **Vertical**: Select to display the legend vertically.
+- **Opacity**: Adjust the legend opacity using the slider.
+- **Colorize Rows**: Select to display legend rows in colors.
+
+## Example query
+The following query uses the [NOAA water sample data](/influxdb/v2.2/reference/sample-data/#noaa-water-sample-data)
+to display changes in water levels over time.
+Use `level description` as the **Fill Column** in the [visualization controls](#data).
+
+```js
+from(bucket: "noaa")
+    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
+    |> filter(fn: (r) => r._measurement == "h2o_feet")
+    |> filter(fn: (r) => r._field == "level description")
+    |> aggregateWindow(every: v.windowPeriod, fn: last, createEmpty: false)
+```
diff --git a/content/influxdb/v2.2/visualize-data/visualization-types/scatter.md b/content/influxdb/v2.2/visualize-data/visualization-types/scatter.md
new file mode 100644
index 000000000..253c11d52
--- /dev/null
+++ b/content/influxdb/v2.2/visualize-data/visualization-types/scatter.md
@@ -0,0 +1,124 @@
+---
+title: Scatter visualization
+list_title: Scatter
+list_image: /img/influxdb/2-0-visualizations-scatter-example.png
+description: >
+  The Scatter view uses a scatter plot to display time series data.
+weight: 202
+menu:
+  influxdb_2_2:
+    name: Scatter
+    parent: Visualization types
+related:
+  - /influxdb/v2.2/visualize-data/visualization-types/heatmap
+---
+
+The **Scatter** view uses a scatter plot to display time series data.
+
+{{< img-hd src="/img/influxdb/2-0-visualizations-scatter-example.png" alt="Scatter plot example" />}}
+
+Select the **Scatter** option from the visualization dropdown in the upper left.
+
+## Scatter behavior
+The scatter visualization maps each data point to X and Y coordinates.
+X and Y axes are specified with the [X Column](#data) and [Y Column](#data) visualization options.
+Each unique series is differentiated using fill colors and symbols.
+Use the [Symbol Column](#data) and [Fill Column](#data) options to select columns
+used to differentiate points in the visualization.
+
+## Scatter controls
+To view **Scatter** controls, click **{{< icon "gear" >}} Customize** next to
+the visualization dropdown.
+
+###### Data
+- **Symbol Column**: Define a column containing values that should be differentiated with symbols.
+- **Fill Column**: Define a column containing values that should be differentiated with fill color.
+- **X Column**: Select a column to display on the x-axis.
+- **Y Column**: Select a column to display on the y-axis.
+- **Time Format**: Select the time format. Options include:
+    {{< ui/timestamp-formats >}}
+
+###### Options
+- **Color Scheme**: Select a color scheme to use for your scatter plot.
+
+###### X Axis
+- **X Axis Label**: Label for the x-axis.
+- **Generate X-Axis Tick Marks**: Select the method to generate x-axis tick marks:
+  - **Auto**: Select to automatically generate tick marks.
+  - **Custom**: To customize the number of x-axis tick marks, select this option, and then enter the following:
+    - **Total Tick Marks**: Enter the total number of ticks to display.
+    - **Start Tick Marks At**: Enter the value to start ticks at.
+    - **Tick Mark Interval**: Enter the interval in between each tick.
+- **X Axis Domain**: The x-axis value range.
+  - **Auto**: Automatically determine the value range based on values in the data set.
+  - **Custom**: Manually specify the minimum x-axis value, maximum x-axis value, or range by including both.
+      - **Min**: Minimum x-axis value.
+      - **Max**: Maximum x-axis value.
+
+###### Y Axis
+- **Y Axis Label**: Label for the y-axis.
+- **Y Tick Prefix**: Prefix to be added to y-value.
+- **Y Tick Suffix**: Suffix to be added to y-value.
+- **Generate Y-Axis Tick Marks**: Select the method to generate y-axis tick marks:
+  - **Auto**: Select to automatically generate tick marks.
+  - **Custom**: To customize the number of y-axis tick marks, select this option, and then enter  the following:
+    - **Total Tick Marks**: Enter the total number of ticks to display.
+    - **Start Tick Marks At**: Enter the value to start ticks at.
+    - **Tick Mark Interval**: Enter the interval in between each tick.
+- **Y Axis Domain**: The y-axis value range.
+  - **Auto**: Automatically determine the value range based on values in the data set.
+  - **Custom**: Manually specify the minimum y-axis value, maximum y-axis value, or range by including both.
+      - **Min**: Minimum y-axis value.
+      - **Max**: Maximum y-axis value.
+
+###### Legend
+- **Legend Orientation**: Select the orientation of the legend that appears upon hover:
+  - **Horizontal**: Select to display the legend horizontally.
+  - **Vertical**: Select to display the legend vertically.
+- **Opacity**: Adjust the legend opacity using the slider.
+- **Colorize Rows**: Select to display legend rows in colors.
+
+## Scatter examples
+
+### Cross-measurement correlation
+The following example explores possible correlation between CPU and Memory usage.
+It uses data collected with the Telegraf [Mem](/{{< latest "telegraf" >}}/plugins//#mem)
+and [CPU](/{{< latest "telegraf" >}}/plugins//#cpu) input plugins.
+
+###### Query CPU and memory usage
+The following query creates a union of CPU and memory usage.
+It scales the CPU usage metric to better align with baseline memory usage.
+
+```js
+cpu = from(bucket: "example-bucket")
+    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
+    |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_system" and r.cpu == "cpu-total")
+    // Scale CPU usage
+    |> map(fn: (r) => ({r with _value: r._value + 60.0, _time: r._time}))
+
+mem = from(bucket: "example-bucket")
+    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+
+union(tables: [cpu, mem])
+```
+
+###### Use a scatter plot to visualize correlation
+In the Scatter visualization controls, points are differentiated based on their group keys.
+
+{{< img-hd src="/img/influxdb/2-0-visualizations-scatter-correlation.png" alt="Heatmap correlation example" />}}
+
+## Important notes
+
+### Differences between a scatter plot and a heatmap
+Scatter plots and [Heatmaps](/influxdb/v2.2/visualize-data/visualization-types/heatmap/)
+both visualize the distribution of data points on X and Y axes.
+However, in certain cases, scatterplots can "hide" points if they share the same X and Y coordinates.
+
+For example, the dashboard cells below visualize the same query results:
+
+{{< img-hd src="/img/influxdb/2-0-visualizations-heatmap-vs-scatter.png" alt="Heatmap vs Scatter plot" />}}
+
+The heatmap indicates isolated high point density, which isn't visible in the scatter plot.
+In the scatter plot visualization, points that share the same X and Y coordinates
+appear as a single point.
diff --git a/content/influxdb/v2.2/visualize-data/visualization-types/single-stat.md b/content/influxdb/v2.2/visualize-data/visualization-types/single-stat.md
new file mode 100644
index 000000000..720aa4dc5
--- /dev/null
+++ b/content/influxdb/v2.2/visualize-data/visualization-types/single-stat.md
@@ -0,0 +1,62 @@
+---
+title: Single Stat visualization
+list_title: Single stat
+list_image: /img/influxdb/2-0-visualizations-single-stat-example.png
+description: >
+  The Single Stat view displays the most recent value of the specified time series as a numerical value.
+weight: 202
+menu:
+  influxdb_2_2:
+    name: Single Stat
+    parent: Visualization types
+---
+
+The **Single Stat** view displays the most recent value of the specified time series as a numerical value.
+
+{{< img-hd src="/img/influxdb/2-0-visualizations-single-stat-example-8.png" alt="Single stat example" />}}
+
+Select the **Single Stat** option from the visualization dropdown in the upper left.
+
+## Single Stat behavior
+The Single Stat visualization displays a single numeric data point.
+It uses the latest point in the first table (or series) returned by the query.
+
+{{% note %}}
+#### Queries should return one table
+Flux does not guarantee the order in which tables are returned.
+If a query returns multiple tables (or series), the table order can change between query executions
+and result in the Single Stat visualization displaying inconsistent data.
+For consistent results, the Single Stat query should return a single table.
+{{% /note %}}
+
+## Single Stat Controls
+To view **Single Stat** controls, click **{{< icon "gear" >}} Customize** next to
+the visualization dropdown.
+
+- **Prefix**: Prefix to be added to the single stat.
+- **Suffix**: Suffix to be added to the single stat.
+- **Decimal Places**: The number of decimal places to display for the single stat.
+    - **Auto** or **Custom**: Enable or disable auto-setting.
+
+###### Colorized Thresholds
+- **Base Color**: Select a base or background color from the selection list.
+- **Add a Threshold**: Change the color of the single stat based on the current value.
+  - **Value is**: Enter the value at which the single stat should appear in the selected color.
+    Choose a color from the dropdown menu next to the value.
+- **Colorization**: Choose **Text** for the single stat to change color based on the configured thresholds.
+  Choose **Background** for the background of the graph to change color based on the configured thresholds.
+
+## Single Stat examples
+
+### Show human-readable current value
+The following example shows the current memory usage displayed has a human-readable percentage:
+
+###### Query memory usage percentage
+```js
+from(bucket: "example-bucket")
+    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+```
+
+###### Memory usage as a single stat
+{{< img-hd src="/img/influxdb/2-0-visualizations-single-stat-example-8.png" alt="Graph + Single Stat Memory Usage Example" />}}
diff --git a/content/influxdb/v2.2/visualize-data/visualization-types/table.md b/content/influxdb/v2.2/visualize-data/visualization-types/table.md
new file mode 100644
index 000000000..3a5e962b9
--- /dev/null
+++ b/content/influxdb/v2.2/visualize-data/visualization-types/table.md
@@ -0,0 +1,75 @@
+---
+title: Table visualization
+list_title: Table
+list_image: /img/influxdb/2-0-visualizations-table-example.png
+description: >
+  The Table option displays the results of queries in a tabular view, which is
+  sometimes easier to analyze than graph views of data.
+weight: 202
+menu:
+  influxdb_2_2:
+    name: Table
+    parent: Visualization types
+---
+
+The **Table** option displays the results of queries in a tabular view, which is
+sometimes easier to analyze than graph views of data.
+
+{{< img-hd src="/img/influxdb/2-0-visualizations-table-example.png" alt="Table example" />}}
+
+Select the **Table** option from the visualization dropdown in the upper left.
+
+## Table behavior
+The table visualization renders queried data in structured, easy-to-read tables.
+Columns and rows match those in the query output.
+If query results contain multiple tables, only one table is shown at a time.
+Select other output tables in the far left column of the table visualization.
+Tables are identified by their [group key](/{{< latest "flux" >}}/get-started/data-model/#group-key).
+
+## Table Controls
+To view **Table** controls, click **{{< icon "gear" >}} Customize** next to
+the visualization dropdown.
+
+###### Formatting
+- **Default Sort Field**: Select the default sort field. Default is **time**.
+- **Time Format**: Select the time format. Options include:
+    {{< ui/timestamp-formats >}}
+
+- **Decimal Places**: Enter the number of decimal places. Default (empty field) is **unlimited**.
+    - **Auto** or **Custom**: Enable or disable auto-setting.
+
+###### Colorized Thresholds
+- **Base Color**: Select a base or background color from the selection list.
+- **Add a Threshold**: Change the color of the table based on the current value.
+  - **Value is**: Enter the value at which the table should appear in the selected color.
+    Choose a color from the dropdown menu next to the value.
+
+###### Column Settings
+- **First Column**: Toggle to **Fixed** to lock the first column so that the listings are always visible.
+  Threshold settings do not apply in the first column when locked.
+- **Table Columns**:
+  - Enter a new name to rename any of the columns.
+  - Click the eye icon next to a column to hide it.
+  - [additional]: Enter name for each additional column.
+  - Change the order of the columns by dragging to the desired position.
+
+## Table examples
+Tables are helpful when displaying many human-readable metrics in a dashboard
+such as cluster statistics or log messages.
+
+### Human-readable cluster metrics
+The following example queries the latest reported memory usage from a cluster of servers.
+
+###### Query the latest memory usage from each host
+```js
+from(bucket: "example-bucket")
+    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
+    |> filter(fn: (r) => r._measurement == "mem" and r._field == "used_percent")
+    |> group(columns: ["host"])
+    |> last()
+    |> group()
+    |> keep(columns: ["_value", "host"])
+```
+
+###### Cluster metrics in a table
+{{< img-hd src="/img/influxdb/2-0-visualizations-table-human-readable.png" alt="Human readable metrics in a table" />}}
diff --git a/content/influxdb/v2.2/write-data/_index.md b/content/influxdb/v2.2/write-data/_index.md
new file mode 100644
index 000000000..bd4a599b6
--- /dev/null
+++ b/content/influxdb/v2.2/write-data/_index.md
@@ -0,0 +1,37 @@
+---
+title: Write data to InfluxDB
+list_title: Write data
+description: >
+  Collect and write time series data to InfluxDB Cloud and InfluxDB OSS.
+weight: 4
+aliases:
+  - /influxdb/v2.2/write-data/quick-start/
+  - /influxdb/v2.2/write-data/sample-data/demo-data/
+menu:
+  influxdb_2_2:
+    name: Write data
+influxdb/v2.2/tags: [write, line protocol]
+related:
+  - /influxdb/v2.2/write-data/no-code/use-telegraf/
+  - /influxdb/v2.2/api/#tag/Write, InfluxDB API /write endpoint
+  - /influxdb/v2.2/reference/syntax/line-protocol
+  - /influxdb/v2.2/reference/syntax/annotated-csv
+  - /influxdb/v2.2/reference/cli/influx/write
+  - /influxdb/v2.2/migrate-data/
+  - /resources/videos/ingest-data/, How to Ingest Data in InfluxDB (Video)
+---
+
+1. Learn the [best practices](/influxdb/v2.2/write-data/best-practices/) for writing data.
+2. Discover how to write data [without coding](/influxdb/v2.2/write-data/no-code/), by [loading data source in the UI](/influxdb/v2.2/write-data/no-code/load-data/), or using [developer tools](/influxdb/v2.2/write-data/developer-tools/).
+3. Do any of the following:
+   - [Troubleshoot the most common issues writing data](/influxdb/v2.2/write-data/troubleshoot/)
+   - [Delete data you no longer need](/influxdb/v2.2/write-data/delete-data/)
+   - [Query and explore data](/influxdb/v2.2/query-data/)
+   - [Process data](/influxdb/v2.2/process-data/)
+   - [Visualize data](/influxdb/v2.2/visualize-data/)
+   - [Migrate data](/influxdb/v2.2/migrate-data/)
+   - [Monitor and alert](/influxdb/v2.2/monitor-alert/)
+
+The following video discusses different ways to write data to InfluxDB:
+
+{{< youtube xYnFVvRTlkQ >}}
\ No newline at end of file
diff --git a/content/influxdb/v2.2/write-data/best-practices/_index.md b/content/influxdb/v2.2/write-data/best-practices/_index.md
new file mode 100644
index 000000000..c6b52c3f4
--- /dev/null
+++ b/content/influxdb/v2.2/write-data/best-practices/_index.md
@@ -0,0 +1,17 @@
+---
+title: Best practices for writing data
+seotitle: Best practices for writing data to InfluxDB
+description: >
+  Learn about the recommendations and best practices for writing data to InfluxDB.
+weight: 105
+menu:
+  influxdb_2_2:
+    name: Best practices
+    identifier: write-best-practices
+    parent: Write data
+---
+
+The following articles walk through recommendations and best practices for writing
+data to InfluxDB.
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/write-data/best-practices/duplicate-points.md b/content/influxdb/v2.2/write-data/best-practices/duplicate-points.md
new file mode 100644
index 000000000..e7e66b006
--- /dev/null
+++ b/content/influxdb/v2.2/write-data/best-practices/duplicate-points.md
@@ -0,0 +1,131 @@
+---
+title: Handle duplicate data points
+seotitle: Handle duplicate data points when writing to InfluxDB
+description: >
+  InfluxDB identifies unique data points by their measurement, tag set, and timestamp.
+  This article discusses methods for preserving data from two points with a common
+  measurement, tag set, and timestamp but a different field set.
+weight: 204
+menu:
+  influxdb_2_2:
+    name: Handle duplicate points
+    parent: write-best-practices
+influxdb/v2.2/tags: [best practices, write]
+---
+
+InfluxDB identifies unique data points by their measurement, tag set, and timestamp
+(each a part of [Line protocol](/influxdb/v2.2/reference/syntax/line-protocol) used to write data to InfluxDB).
+
+```txt
+web,host=host2,region=us_west firstByte=15.0 1559260800000000000
+--- -------------------------                -------------------
+ |               |                                    |
+Measurement   Tag set                             Timestamp
+```
+
+## Duplicate data points
+For points that have the same measurement name, tag set, and timestamp,
+InfluxDB creates a union of the old and new field sets.
+For any matching field keys, InfluxDB uses the field value of the new point.
+For example:
+
+```sh
+# Existing data point
+web,host=host2,region=us_west firstByte=24.0,dnsLookup=7.0 1559260800000000000
+
+# New data point
+web,host=host2,region=us_west firstByte=15.0 1559260800000000000
+```
+
+After you submit the new data point, InfluxDB overwrites `firstByte` with the new
+field value and leaves the field `dnsLookup` alone:
+
+```sh
+# Resulting data point
+web,host=host2,region=us_west firstByte=15.0,dnsLookup=7.0 1559260800000000000
+```
+
+```sh
+from(bucket: "example-bucket")
+  |> range(start: 2019-05-31T00:00:00Z, stop: 2019-05-31T12:00:00Z)
+  |> filter(fn: (r) => r._measurement == "web")
+
+Table: keys: [_measurement, host, region]
+               _time  _measurement   host   region  dnsLookup  firstByte
+--------------------  ------------  -----  -------  ---------  ---------
+2019-05-31T00:00:00Z           web  host2  us_west          7         15
+```
+
+## Preserve duplicate points
+To preserve both old and new field values in duplicate points, use one of the following strategies:
+
+- [Add an arbitrary tag](#add-an-arbitrary-tag)
+- [Increment the timestamp](#increment-the-timestamp)
+
+### Add an arbitrary tag
+Add an arbitrary tag with unique values so InfluxDB reads the duplicate points as unique.
+
+For example, add a `uniq` tag to each data point:
+
+```sh
+# Existing point
+web,host=host2,region=us_west,uniq=1 firstByte=24.0,dnsLookup=7.0 1559260800000000000
+
+# New point
+web,host=host2,region=us_west,uniq=2 firstByte=15.0 1559260800000000000
+```
+
+{{% note %}}
+It is not necessary to retroactively add the unique tag to the existing data point.
+Tag sets are evaluated as a whole.
+The arbitrary `uniq` tag on the new point allows InfluxDB to recognize it as a unique point.
+However, this causes the schema of the two points to differ and may lead to challenges when querying the data.
+{{% /note %}}
+
+After writing the new point to InfluxDB:
+
+```sh
+from(bucket: "example-bucket")
+  |> range(start: 2019-05-31T00:00:00Z, stop: 2019-05-31T12:00:00Z)
+  |> filter(fn: (r) => r._measurement == "web")
+
+Table: keys: [_measurement, host, region, uniq]
+               _time  _measurement   host   region  uniq  firstByte  dnsLookup
+--------------------  ------------  -----  -------  ----  ---------  ---------
+2019-05-31T00:00:00Z           web  host2  us_west     1         24          7
+
+Table: keys: [_measurement, host, region, uniq]
+               _time  _measurement   host   region  uniq  firstByte
+--------------------  ------------  -----  -------  ----  ---------
+2019-05-31T00:00:00Z           web  host2  us_west     2         15
+```
+
+### Increment the timestamp
+Increment the timestamp by a nanosecond to enforce the uniqueness of each point.
+
+```sh
+# Old data point
+web,host=host2,region=us_west firstByte=24.0,dnsLookup=7.0 1559260800000000000
+
+# New data point
+web,host=host2,region=us_west firstByte=15.0 1559260800000000001
+```
+
+After writing the new point to InfluxDB:
+
+```sh
+from(bucket: "example-bucket")
+  |> range(start: 2019-05-31T00:00:00Z, stop: 2019-05-31T12:00:00Z)
+  |> filter(fn: (r) => r._measurement == "web")
+
+Table: keys: [_measurement, host, region]
+                         _time  _measurement   host   region  firstByte  dnsLookup
+------------------------------  ------------  -----  -------  ---------  ---------
+2019-05-31T00:00:00.000000000Z           web  host2  us_west         24          7
+2019-05-31T00:00:00.000000001Z           web  host2  us_west         15
+```
+
+{{% note %}}
+The output of examples queries in this article has been modified to clearly show
+the different approaches and results for handling duplicate data.
+{{% /note %}}
diff --git a/content/influxdb/v2.2/write-data/best-practices/optimize-writes.md b/content/influxdb/v2.2/write-data/best-practices/optimize-writes.md
new file mode 100644
index 000000000..f679b6a2b
--- /dev/null
+++ b/content/influxdb/v2.2/write-data/best-practices/optimize-writes.md
@@ -0,0 +1,132 @@
+---
+title: Optimize writes to InfluxDB
+description: >
+  Simple tips to optimize performance and system overhead when writing data to InfluxDB.
+weight: 203
+menu:
+  influxdb_2_2:
+    parent: write-best-practices
+influxdb/v2.2/tags: [best practices, write]
+---
+
+Use these tips to optimize performance and system overhead when writing data to InfluxDB.
+
+- [Batch writes](#batch-writes)
+- [Sort tags by key](#sort-tags-by-key)
+- [Use the coarsest time precision possible](#use-the-coarsest-time-precision-possible)
+- [Use gzip compression](#use-gzip-compression)
+- [Synchronize hosts with NTP](#synchronize-hosts-with-ntp)
+- [Write multiple data points in one request](#write-multiple-data-points-in-one-request)
+
+{{% note %}}
+The following tools write to InfluxDB and employ _most_ write optimizations by default:
+
+- [Telegraf](/influxdb/v2.2/write-data/no-code/use-telegraf/)
+- [InfluxDB client libraries](/influxdb/v2.2/api-guide/client-libraries/)
+- [InfluxDB scrapers](/influxdb/v2.2/write-data/no-code/scrape-data/)
+{{% /note %}}
+
+## Batch writes
+
+Write data in batches to minimize network overhead when writing data to InfluxDB.
+
+{{% note %}}
+The optimal batch size is 5000 lines of line protocol.
+{{% /note %}}
+
+## Sort tags by key
+
+Before writing data points to InfluxDB, sort tags by key in lexicographic order.
+_Verify sort results match results from the [Go `bytes.Compare` function](http://golang.org/pkg/bytes/#Compare)._
+
+```sh
+# Line protocol example with unsorted tags
+measurement,tagC=therefore,tagE=am,tagA=i,tagD=i,tagB=think fieldKey=fieldValue 1562020262
+
+# Optimized line protocol example with tags sorted by key
+measurement,tagA=i,tagB=think,tagC=therefore,tagD=i,tagE=am fieldKey=fieldValue 1562020262
+```
+
+## Use the coarsest time precision possible
+
+By default, InfluxDB writes data in nanosecond precision.
+However if your data isn't collected in nanoseconds, there is no need to write at that precision.
+For better performance, use the coarsest precision possible for timestamps.
+
+_Specify timestamp precision when [writing to InfluxDB](/influxdb/v2.2/write-data/#timestamp-precision)._
+
+## Use gzip compression
+
+Use gzip compression to speed up writes to InfluxDB and reduce network bandwidth.
+Benchmarks have shown up to a 5x speed improvement when data is compressed.
+
+{{< tabs-wrapper >}}
+{{% tabs %}}
+[Telegraf](#)
+[Client libraries](#)
+[InfluxDB API](#)
+{{% /tabs %}}
+{{% tab-content %}}
+
+### Enable gzip compression in Telegraf
+
+In the `influxdb_v2` output plugin configuration in your `telegraf.conf`, set the
+`content_encoding` option to `gzip`:
+
+```toml
+[[outputs.influxdb_v2]]
+  urls = ["http://localhost:8086"]
+  # ...
+  content_encoding = "gzip"
+```
+{{% /tab-content %}}
+{{% tab-content %}}
+
+### Enable gzip compression in InfluxDB client libraries
+
+Each [InfluxDB client library](/influxdb/v2.2/api-guide/client-libraries/) provides
+options for compressing write requests or enforces compression by default.
+The method for enabling compression is different for each library.
+For specific instructions, see the [InfluxDB client libraries documentation](/influxdb/v2.2/api-guide/client-libraries/).
+{{% /tab-content %}}
+{{% tab-content %}}
+
+### Use gzip compression with the InfluxDB API
+
+When using the InfluxDB API `/write` endpoint to write data, compress the data with `gzip` and set the `Content-Encoding`
+header to `gzip`. 
+
+```sh
+{{% get-shared-text "api/v2.0/write/write-compress.sh" %}}
+```
+{{% /tab-content %}}
+{{< /tabs-wrapper >}}
+
+## Synchronize hosts with NTP
+
+Use the Network Time Protocol (NTP) to synchronize time between hosts.
+If a timestamp isn't included in line protocol, InfluxDB uses its host's local
+time (in UTC) to assign timestamps to each point.
+If a host's clocks isn't synchronized with NTP, timestamps may be inaccurate.
+
+## Write multiple data points in one request
+
+To write multiple lines in one request, each line of line protocol must be delimited by a new line (`\n`).
+
+## Rate limiting
+
+Use the [`influx write`](/influxdb/v2.2/reference/cli/influx/write/) `--rate-limit` flag to control the rate of writes.
+Use one of the following string formats to specify the rate limit:
+
+- `COUNT(B|kB|MB)`, or
+- `COUNT(B|kB|MB)/TIME(s|sec|m|min)`
+
+where `COUNT` is a decimal number and `TIME` is a positive whole number.
+Spaces in the value are ignored.
+For example: "5MB / 5min" can be also expressed as `17476.266666667Bs`, `1MB/1min`, `1MB/min`, `1MBmin` or `1MBm`.
+If the rate limit format is invalid, `influx write` prints out the format and an exact regular expression.
+The `--rate-limit` flag can be also used with [`influx write dryrun`](/influxdb/v2.2/reference/cli/influx/write/dryrun/).
+
+{{% cloud %}}
+By default, the free tier rate limit in {{< cloud-name "short" >}} is `1MB/min`.
+{{% /cloud %}}
diff --git a/content/influxdb/v2.2/write-data/best-practices/resolve-high-cardinality.md b/content/influxdb/v2.2/write-data/best-practices/resolve-high-cardinality.md
new file mode 100644
index 000000000..683b2d12a
--- /dev/null
+++ b/content/influxdb/v2.2/write-data/best-practices/resolve-high-cardinality.md
@@ -0,0 +1,133 @@
+---
+title: Resolve high series cardinality
+description: >
+  Reduce high series cardinality in InfluxDB. If reads and writes to InfluxDB have started to slow down, you may have high cardinality. Find the source of high cardinality and adjust your schema to resolve high cardinality issues.
+menu:
+  influxdb_2_2:
+    name: Resolve high cardinality
+    weight: 202
+    parent: write-best-practices
+---
+
+If reads and writes to InfluxDB have started to slow down, high [series cardinality](/influxdb/v2.1/reference/glossary/#series-cardinality) (too many series) may be causing memory issues. {{% cloud-only %}}Cardinality can also cause writes to fail if it exceeds your [plan’s adjustable service quota](/influxdb/cloud/account-management/limits/).{{% /cloud-only %}}
+
+Take steps to understand and resolve high series cardinality.
+
+1. [Learn the causes of high cardinality](#learn-the-causes-of-high-series-cardinality)
+2. [Measure series cardinality](#measure-series-cardinality)
+3. [Resolve high cardinality](#resolve-high-cardinality)
+
+## Learn the causes of high series cardinality
+
+{{% oss-only %}}
+
+  IndexDB indexes the following data elements to speed up reads:
+  - [measurement](/influxdb/v2.2/reference/glossary/#measurement)
+  - [tags](/influxdb/v2.2/reference/glossary/#tag)
+
+{{% /oss-only %}}
+{{% cloud-only %}}
+
+  IndexDB indexes the following data elements to speed up reads:
+  - [measurement](/influxdb/v2.2/reference/glossary/#measurement)
+  - [tags](/influxdb/v2.2/reference/glossary/#tag)
+  - [field keys](/influxdb/cloud/reference/glossary/#field-key)
+
+{{% /cloud-only %}}
+
+Each unique set of indexed data elements forms a [series key](/influxdb/v2.2/reference/glossary/#series-key).
+[Tags](/influxdb/v2.2/reference/glossary/#tag) containing highly variable information like unique IDs, hashes, and random strings lead to a large number of [series](/influxdb/v2.2/reference/glossary/#series), also known as high [series cardinality](/influxdb/v2.2/reference/glossary/#series-cardinality).
+High series cardinality is a primary driver of high memory usage for many database workloads.
+
+## Measure series cardinality
+
+Use the following to measure series cardinality of your buckets:
+- [`influxdb.cardinality()`](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/cardinality): Flux function that returns the number of unique [series keys](/influxdb/v2.2/reference/glossary/#series) in your data.
+
+- [`SHOW SERIES CARDINALITY`](/influxdb/v2.2/query_language/spec/#show-series-cardinality): InfluxQL command that returns the number of unique [series keys](/influxdb/v2.2/reference/glossary/#series) in your data.
+
+## Resolve high cardinality
+
+To resolve high series cardinality, complete the following steps (for multiple buckets if applicable):
+
+1. [Review tags](#review-tags).
+2. [Improve your schema](#improve-your-schema).
+3. [Delete high cardinality data](#delete-data-to-reduce-high-cardinality).
+
+## Review tags
+
+Review your tags to ensure each tag **does not contain** unique values for most entries:
+
+- Scan your tags for [common tag issues](#common-tag-issues).
+- Use the example Flux query below to [count unique tag values](#count-unique-tag-values).
+
+### Common tag issues
+
+Look for the following common issues, which often cause many unique tag values:
+
+- **Writing log messages to tags**. If a log message includes a unique timestamp, pointer value, or unique string, many unique tag values are created.
+- **Writing timestamps to tags**. Typically done by accident in client code.
+- **Unique tag values that grow over time** For example, a user ID tag may work at a small startup, but may begin to cause issues when the company grows to hundreds of thousands of users.
+
+### Count unique tag values
+
+The following example Flux query shows you which tags are contributing the most to cardinality. Look for tags with values orders of magnitude higher than others.
+
+```js
+// Count unique values for each tag in a bucket
+import "influxdata/influxdb/schema"
+
+cardinalityByTag = (bucket) => schema.tagKeys(bucket: bucket)
+    |> map(
+        fn: (r) => ({
+            tag: r._value,
+            _value: if contains(set: ["_stop", "_start"], value: r._value) then
+                0
+            else
+                (schema.tagValues(bucket: bucket, tag: r._value)
+                    |> count()
+                    |> findRecord(fn: (key) => true, idx: 0))._value,
+        }),
+    )
+    |> group(columns: ["tag"])
+    |> sum()
+
+cardinalityByTag(bucket: "example-bucket")
+```
+
+{{% note %}}
+ If you're experiencing runaway cardinality, the query above may timeout. If you experience a timeout, run the queries below—one at a time.
+{{% /note %}}
+
+1. Generate a list of tags:
+
+    ```js
+    // Generate a list of tags
+    import "influxdata/influxdb/schema"
+
+    schema.tagKeys(bucket: "example-bucket")
+    ```
+
+2. Count unique tag values for each tag:
+
+    ```js
+    // Run the following for each tag to count the number of unique tag values
+    import "influxdata/influxdb/schema"
+
+    tag = "example-tag-key"
+
+    schema.tagValues(bucket: "my-bucket", tag: tag)
+        |> count()
+    ```
+
+These queries should help identify the sources of high cardinality in each of your buckets. To determine which specific tags are growing, check the cardinality again after 24 hours to see if one or more tags have grown significantly.
+
+## Improve your schema
+
+To minimize cardinality in the future, design your schema for easy and performant querying.
+Review [best practices for schema design](/influxdb/v2.2/write-data/best-practices/schema-design/).
+
+## Delete data to reduce high cardinality
+
+Consider whether you need the data that is causing high cardinality.
+If you no longer need this data, you can [delete the whole bucket](/influxdb/v2.2/organizations/buckets/delete-bucket/) or [delete a range of data](/influxdb/v2.2/write-data/delete-data/).
diff --git a/content/influxdb/v2.2/write-data/best-practices/schema-design.md b/content/influxdb/v2.2/write-data/best-practices/schema-design.md
new file mode 100644
index 000000000..a1b19f6cb
--- /dev/null
+++ b/content/influxdb/v2.2/write-data/best-practices/schema-design.md
@@ -0,0 +1,252 @@
+---
+title: InfluxDB schema design
+description: >
+  Design your schema for simpler and more performant queries.
+menu:
+  influxdb_2_2:
+    name: Schema design
+    weight: 201
+    parent: write-best-practices
+related:
+  - /resources/videos/data-model-building-blocks/
+---
+
+Design your [schema](/influxdb/v2.2/reference/glossary/#schema) for simpler and more performant queries.
+Follow design guidelines to make your schema easy to query.
+Learn how these guidelines lead to more performant queries.
+
+- [Design to query](#design-to-query)
+  - [Keep measurements and keys simple](#keep-measurements-and-keys-simple)
+- [Use tags and fields](#use-tags-and-fields)
+  - [Use fields for unique and numeric data](#use-fields-for-unique-and-numeric-data)
+  - [Use tags to improve query performance](#use-tags-to-improve-query-performance)
+  - [Keep tags simple](#keep-tags-simple)
+
+{{% note %}}
+
+Good schema design can prevent high series cardinality, resulting in better performing queries. If you notice data reads and writes slowing down or want to learn how cardinality affects performance, see how to [resolve high cardinality](/influxdb/v2.2/write-data/best-practices/resolve-high-cardinality/).
+
+{{% /note %}}
+
+## Design to query
+
+The schemas below demonstrate [measurements](/influxdb/v2.2/reference/glossary/#measurement), [tag keys](/influxdb/v2.2/reference/glossary/#tag-key), and [field keys](/influxdb/v2.2/reference/glossary/#field-key) that are easy to query.
+
+| measurement          | tag key   | tag key | field key |  field key  |
+|----------------------|-----------|---------|-----------|-------------|
+| airSensor            | sensorId  | station | humidity  | temperature |
+| waterQualitySensor   | sensorId  | station | pH        | temperature |
+
+The `airSensor` and `waterQualitySensor` schemas illustrate the following guidelines:
+- Each measurement is a simple name that describes a schema.
+- Keys [don't repeat within a schema](#avoid-duplicate-names-for-tags-and-fields).
+- Keys [don't use reserved keywords or special characters](#avoid-keywords-and-special-characters-in-keys).
+- Tags (`sensorId` and `station`) [store metadata common across many data points](#use-tags-to-improve-query-performance).
+- Fields (`humidity`, `pH`, and `temperature`) [store numeric data](#use-fields-for-unique-and-numeric-data).
+- Fields [store unique or highly variable](#use-fields-for-unique-and-numeric-data) data.
+- Measurements and keys [don't contain data](#keep-measurements-and-keys-simple); tag values and field values will store data.
+
+The following points (formatted as line protocol) use the `airSensor` and `waterQualitySensor` schemas:
+
+```
+airSensor,sensorId=A0100,station=Harbor humidity=35.0658,temperature=21.667 1636729543000000000
+waterQualitySensor,sensorId=W0101,station=Harbor pH=6.1,temperature=16.103 1472515200000000000
+```
+
+### Keep measurements and keys simple
+
+Store data in [tag values](/influxdb/v2.2/reference/glossary/#tag-value) or [field values](/influxdb/v2.2/reference/glossary/#field-value), not in [tag keys](/influxdb/v2.2/reference/glossary/#tag-key), [field keys](/influxdb/v2.2/reference/glossary/#field-key), or [measurements](/influxdb/v2.2/reference/glossary/#measurement). If you design your schema to store data in tag and field values,
+your queries will be easier to write and more efficient.
+
+{{% oss-only %}}
+
+In addition, you'll keep cardinality low by not creating measurements and keys as you write data.
+To learn more about the performance impact of high series cardinality, see how to [resolve high cardinality](/influxdb/v2.2/write-data/best-practices/resolve-high-cardinality/).
+
+{{% /oss-only %}}
+
+#### Compare schemas
+
+Compare the following valid schemas represented by line protocol.
+
+**Recommended**: the following schema stores metadata in separate `crop`, `plot`, and `region` tags. The `temp` field contains variable numeric data.
+
+#####  {id="good-measurements-schema"}
+```
+Good Measurements schema - Data encoded in tags (recommended)
+-------------
+weather_sensor,crop=blueberries,plot=1,region=north temp=50.1 1472515200000000000
+weather_sensor,crop=blueberries,plot=2,region=midwest temp=49.8 1472515200000000000
+```
+
+**Not recommended**: the following schema stores multiple attributes (`crop`, `plot` and `region`) concatenated  (`blueberries.plot-1.north`) within the measurement, similar to Graphite metrics.
+
+#####  {id="bad-measurements-schema"}
+```
+Bad Measurements schema - Data encoded in the measurement (not recommended)
+-------------
+blueberries.plot-1.north temp=50.1 1472515200000000000
+blueberries.plot-2.midwest temp=49.8 1472515200000000000
+```
+
+**Not recommended**: the following schema stores multiple attributes (`crop`, `plot` and `region`) concatenated  (`blueberries.plot-1.north`) within the field key.
+
+#####  {id="bad-keys-schema"}
+```
+Bad Keys schema - Data encoded in field keys (not recommended)
+-------------
+weather_sensor blueberries.plot-1.north.temp=50.1 1472515200000000000
+weather_sensor blueberries.plot-2.midwest.temp=49.8 1472515200000000000
+```
+
+#### Compare queries
+
+Compare the following queries of the [_Good Measurements_](#good-measurements-schema) and [_Bad Measurements_](#bad-measurements-schema) schemas.
+The [Flux](/{{< latest "flux" >}}/) queries calculate the average `temp` for blueberries in the `north` region
+
+**Easy to query**: [_Good Measurements_](#good-measurements-schema) data is easily filtered by `region` tag values, as in the following example.
+
+```js
+// Query *Good Measurements*, data stored in separate tags (recommended)
+from(bucket:"example-bucket")
+    |> range(start:2016-08-30T00:00:00Z)
+    |> filter(fn: (r) =>  r._measurement == "weather_sensor" and r.region == "north" and r._field == "temp")
+    |> mean()
+```
+
+**Difficult to query**: [_Bad Measurements_](#bad-measurements-schema) requires regular expressions to extract `plot` and `region` from the measurement, as in the following example.
+
+```js
+// Query *Bad Measurements*, data encoded in the measurement (not recommended)
+from(bucket:"example-bucket")
+    |> range(start:2016-08-30T00:00:00Z)
+    |> filter(fn: (r) =>  r._measurement =~ /\.north$/ and r._field == "temp")
+    |> mean()
+```
+
+Complex measurements make some queries impossible. For example, calculating the average temperature of both plots is not possible with the [_Bad Measurements_](#bad-measurements-schema) schema.
+
+#### Keep keys simple
+
+In addition to keeping your keys free of data, follow these additional guidelines to make them easier to query:
+- [Avoid keywords and special characters](#avoid-keywords-and-special-characters-in-keys)
+- [Avoid duplicate names for tags and fields](#avoid-duplicate-names-for-tags-and-fields)
+
+##### Avoid keywords and special characters in keys
+
+To simplify query writing, don't include reserved keywords or special characters in tag and field keys.
+If you use [Flux keywords](/{{< latest "flux" >}}/spec/lexical-elements/#keywords) in keys,
+then you'll have to wrap the keys in double quotes.
+If you use non-alphanumeric characters in keys, then you'll have to use [bracket notation](/{{< latest "flux" >}}/data-types/composite/record/#bracket-notation) in [Flux]((/{{< latest "flux" >}}/).
+
+##### Avoid duplicate names for tags and fields
+
+Avoid using the same name for a [tag key](/influxdb/v2.2/reference/glossary/#tag-key) and a [field key](/influxdb/v2.2/reference/glossary/#field-key) within the same schema.
+Your query results may be unpredictable if you have a tag and a field with the same name.
+
+{{% cloud-only %}}
+
+{{% note %}}
+Use [explicit bucket schemas]() to enforce unique tag and field keys within a schema.
+{{% /note %}}
+
+{{% /cloud-only %}}
+
+## Use tags and fields
+
+[Tag values](/influxdb/v2.2/reference/glossary/#tag-value) are indexed and [field values](/influxdb/v2.2/reference/glossary/#field-value) aren't.
+This means that querying tags is more performant than querying fields.
+Your queries should guide what you store in tags and what you store in fields.
+
+### Use fields for unique and numeric data
+
+- Store unique or frequently changing values as field values.
+- Store numeric values as field values. ([Tags](/influxdb/v2.2/reference/glossary/#tag-value) only store strings).
+
+### Use tags to improve query performance
+
+- Store values as tag values if they can be reasonably indexed.
+- Store values as [tag values](/influxdb/v2.2/reference/glossary/#tag-value) if the values are used in [filter()]({{< latest "flux" >}}/universe/filter/) or [group()](/{{< latest "flux" >}}/universe/group/) functions.
+- Store values as tag values if the values are shared across multiple data points, i.e. metadata about the field.
+
+Because InfluxDB indexes tags, the query engine doesn't need to scan every record in a bucket to locate a tag value.
+For example, consider a bucket that stores data about thousands of users. With `userId` stored in a [field](/influxdb/v2.2/reference/glossary/#field), a query for user `abcde` requires InfluxDB to scan `userId` in every row.
+
+```js
+from(bucket: "example-bucket")
+    |> range(start: -7d)
+    |> filter(fn: (r) => r._field == "userId" and r._value == "abcde")
+```
+
+To retrieve data more quickly, filter on a tag to reduce the number of rows scanned.
+The tag should store data that can be reasonably indexed.
+The following query filters by the `company` tag to reduce the number of rows scanned for `userId`.
+
+```js
+from(bucket: "example-bucket")
+    |> range(start: -7d)
+    |> filter(fn: (r) => r.company == "Acme")
+    |> filter(fn: (r) => r._field == "userId" and r._value == "abcde")
+```
+
+### Keep tags simple
+
+Use one tag for each data attribute.
+If your source data contains multiple data attributes in a single parameter,
+split each attribute into its own tag.
+When each tag represents one attribute (not multiple concatenated attributes) of your data,
+you'll reduce the need for regular expressions in your queries.
+Without regular expressions, your queries will be easier to write and more performant.
+
+#### Compare schemas
+
+Compare the following valid schemas represented by line protocol.
+
+**Recommended**: the following schema splits location data into `plot` and `region` tags.
+
+#####  {id="good-tags-schema"}
+```
+Good Tags schema - Data encoded in multiple tags
+-------------
+weather_sensor,crop=blueberries,plot=1,region=north temp=50.1 1472515200000000000
+weather_sensor,crop=blueberries,plot=2,region=midwest temp=49.8 1472515200000000000
+```
+
+**Not recommended**: the following schema stores multiple attributes (`plot` and `region`) concatenated within the `location` tag value (`plot-1.north`).
+
+##### {id="bad-tags-schema"}
+```
+Bad Tags schema - Multiple data encoded in a single tag
+-------------
+weather_sensor,crop=blueberries,location=plot-1.north temp=50.1 1472515200000000000
+weather_sensor,crop=blueberries,location=plot-2.midwest temp=49.8 1472515200000000000
+```
+
+#### Compare queries
+
+Compare queries of the [_Good Tags_](#good-tags-schema) and [_Bad Tags_](#bad-tags-schema) schemas.
+The [Flux](/{{< latest "flux" >}}/) queries calculate the average `temp` for blueberries in the `north` region.
+
+**Easy to query**: [_Good Tags_](#good-tags-schema) data is easily filtered by `region` tag values, as in the following example.
+
+```js
+// Query *Good Tags* schema, data encoded in multiple tags
+from(bucket:"example-bucket")
+    |> range(start:2016-08-30T00:00:00Z)
+    |> filter(fn: (r) =>  r._measurement == "weather_sensor" and r.region == "north" and r._field == "temp")
+    |> mean()
+```
+
+**Difficult to query**: [_Bad Tags_](#bad-tags-schema) requires regular expressions to parse the complex `location` values, as in the following example.
+
+```js
+// Query *Bad Tags* schema, multiple data encoded in a single tag
+from(bucket:"example-bucket")
+    |> range(start:2016-08-30T00:00:00Z)
+    |> filter(fn: (r) =>  r._measurement == "weather_sensor" and r.location =~ /\.north$/ and r._field == "temp")
+    |> mean()
+```
+
+For an overview of the InfluxDB data model, watch the following video:
+
+{{< youtube 3qTTqsL27lI >}}
\ No newline at end of file
diff --git a/content/influxdb/v2.2/write-data/delete-data.md b/content/influxdb/v2.2/write-data/delete-data.md
new file mode 100644
index 000000000..e5974a19a
--- /dev/null
+++ b/content/influxdb/v2.2/write-data/delete-data.md
@@ -0,0 +1,130 @@
+---
+title: Delete data
+list_title: Delete data
+description: >
+  Use the `influx` CLI or the InfluxDB API `/api/v2/delete` endpoint to delete
+  data from an InfluxDB bucket.
+menu:
+  influxdb_2_2:
+    name: Delete data
+    parent: Write data
+weight: 107
+influxdb/v2.2/tags: [delete]
+related:
+  - /influxdb/v2.2/reference/syntax/delete-predicate/
+  - /influxdb/v2.2/reference/cli/influx/delete/
+---
+
+Use the [`influx` CLI](/influxdb/v2.2/reference/cli/influx/) or the InfluxDB API
+[`/api/v2/delete`](/influxdb/v2.2/api/#operation/PostDelete) endpoint to delete
+data from an InfluxDB bucket.
+
+- [Delete data using the influx CLI](#delete-data-using-the-influx-cli)
+- [Delete data using the API](#delete-data-using-the-api)
+
+InfluxDB {{< current-version >}} supports deleting data by the following:
+
+- time range
+- measurement (`_measurement`)
+- tag
+- {{% cloud-only %}}field (`_field`){{% /cloud-only %}}
+
+{{% oss-only %}}
+
+{{% warn %}}
+InfluxDB {{< current-version >}} does not support deleting data by field.
+{{% /warn %}}
+
+{{% /oss-only %}}
+
+Once a delete request completes successfully, the deleted data is no longer queryable,
+but will remain on disk until the compaction service runs.
+
+## Delete data using the influx CLI
+
+{{% note %}}
+Use [InfluxDB CLI connection configurations](/influxdb/v2.2/reference/cli/influx/config/)
+to provide your **InfluxDB host, organization, and API token**.
+{{% /note %}}
+
+1. Use the [`influx delete` command](/influxdb/v2.2/reference/cli/influx/delete/) to delete points from InfluxDB.
+2. Use the `--bucket` flag to specify which bucket to delete data from.
+3. Use the `--start` and `--stop` flags to define the time range to delete data from.
+   Use [RFC3339 timestamps](/influxdb/v2.2/reference/glossary/#rfc3339-timestamp).
+4. _(Optional)_ Use the `-p`, `--predicate` flag to include a [delete predicate](/influxdb/v2.2/reference/syntax/delete-predicate)
+   that identifies which points to delete.
+
+    {{% warn %}}
+Deleting data without a [delete predicate](/influxdb/v2.2/reference/syntax/delete-predicate)
+deletes all data in the specified bucket with timestamps between the specified `start` and `stop` times.
+    {{% /warn %}}
+
+### Examples
+
+##### Delete points in a specific measurement with a specific tag value
+```sh
+influx delete --bucket example-bucket \
+  --start '1970-01-01T00:00:00Z' \
+  --stop $(date +"%Y-%m-%dT%H:%M:%SZ") \
+  --predicate '_measurement="example-measurement" AND exampleTag="exampleTagValue"'
+```
+
+##### Delete all points in a specified time range
+```sh
+influx delete --bucket example-bucket \
+  --start 2020-03-01T00:00:00Z \
+  --stop 2020-11-14T00:00:00Z
+```
+
+## Delete data using the API
+Use the InfluxDB API [`/api/v2/delete` endpoint](/influxdb/v2.2/api/#operation/PostDelete)
+to delete points from InfluxDB.
+
+{{< api-endpoint method="post" endpoint="http://localhost:8086/api/v2/delete" >}}
+
+Include the following:
+
+- **Request method:** `POST`
+- **Headers:**
+  - **Authorization:** `Token` schema with your InfluxDB API token
+  - **Content-type:** `application/json`
+- **Query parameters:**
+  - **org** or **orgID:** organization name or [organization ID](/influxdb/v2.2/organizations/view-orgs/#view-your-organization-id)
+  - **bucket** or **bucketID:** bucket name or [bucket ID](/influxdb/v2.2/organizations/buckets/view-buckets/)
+- **Request body:** JSON object with the following fields:  
+  {{< req type="key" >}}
+  - {{< req "\*" >}} **start:** earliest time to delete data from ([RFC3339](/influxdb/v2.2/reference/glossary/#rfc3339-timestamp))
+  - {{< req "\*" >}} **stop:** latest time to delete data from ([RFC3339](/influxdb/v2.2/reference/glossary/#rfc3339-timestamp))
+  - **predicate:** [delete predicate](/influxdb/v2.2/reference/syntax/delete-predicate) statement
+
+       {{% warn %}}
+Deleting data without a [delete predicate](/influxdb/v2.2/reference/syntax/delete-predicate)
+deletes all data in the specified bucket with timestamps between the specified `start` and `stop` times.
+       {{% /warn %}}
+
+### Examples
+
+##### Delete points in a specific measurement with a specific tag value
+```sh
+curl --request POST http://localhost:8086/api/v2/delete?org=example-org&bucket=example-bucket \
+  --header 'Authorization: Token YOUR_API_TOKEN' \
+  --header 'Content-Type: application/json' \
+  --data '{
+    "start": "2020-03-01T00:00:00Z",
+    "stop": "2020-11-14T00:00:00Z",
+    "predicate": "_measurement=\"example-measurement\" AND exampleTag=\"exampleTagValue\""
+  }'
+```
+
+##### Delete all points in a specified time range
+```sh
+curl --request POST http://localhost:8086/api/v2/delete?org=example-org&bucket=example-bucket \
+  --header 'Authorization: Token YOUR_API_TOKEN' \
+  --header 'Content-Type: application/json' \
+  --data '{
+    "start": "2020-03-01T00:00:00Z",
+    "stop": "2020-11-14T00:00:00Z"
+  }'
+```
+
+_For more information, see the [`/api/v2/delete` endpoint documentation](/influxdb/v2.2/api/#operation/PostDelete)._
diff --git a/content/influxdb/v2.2/write-data/developer-tools/_index.md b/content/influxdb/v2.2/write-data/developer-tools/_index.md
new file mode 100644
index 000000000..5c0db0c46
--- /dev/null
+++ b/content/influxdb/v2.2/write-data/developer-tools/_index.md
@@ -0,0 +1,16 @@
+---
+title: Write data with developer tools
+seotitle: Write data to InfluxDB with developer tools
+list_title: Use developer tools
+weight: 102
+description: >
+  Use developer tools such as the InfluxDB API and `influx` CLI to write data to InfluxDB.
+menu:
+  influxdb_2_2:
+    name: Developer tools
+    parent: Write data
+---
+
+Write data to InfluxDB with developer tools.
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/write-data/developer-tools/api.md b/content/influxdb/v2.2/write-data/developer-tools/api.md
new file mode 100644
index 000000000..40810b839
--- /dev/null
+++ b/content/influxdb/v2.2/write-data/developer-tools/api.md
@@ -0,0 +1,57 @@
+---
+title: Write data with the InfluxDB API
+weight: 206
+description: >
+  Use the `/write` endpoint of the InfluxDB API to write data to InfluxDB.
+menu:
+  influxdb_2_2:
+    name: InfluxDB API
+    parent: Developer tools
+---
+Write data to InfluxDB using an HTTP request to the InfluxDB API `/write` endpoint.
+Use the `POST` request method and include the following in your request:
+
+| Requirement          | Include by                                               |
+|:-----------          |:----------                                               |
+| Organization         | Use the `org` query parameter in your request URL.       |
+| Bucket               | Use the `bucket` query parameter in your request URL.    |
+| Timestamp precision  | Use the [`precision`](/influxdb/v2.2/write-data/#timestamp-precision) query parameter in your request URL. Default is `ns`. |
+| API token | Use the `Authorization: Token YOUR_API_TOKEN` header.                   |
+| Line protocol        | Pass as plain text in your request body.                 |
+
+#### Send a write request
+
+The URL in the examples depends on the version and location of your InfluxDB {{< current-version >}} instance.
+<a href="#" class="url-trigger">Customize URLs in examples</a>
+
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[Curl](#curl)
+[Node.js](#nodejs)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```sh
+{{< get-shared-text "api/v2.0/write/write.sh" >}}
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```js
+{{< get-shared-text "api/v2.0/write/write.mjs" >}}
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+{{% note %}}
+##### Use gzip compression with the InfluxDB API
+
+When using the InfluxDB API `/write` endpoint to write data, compress the data with `gzip` and set the `Content-Encoding`
+header to `gzip`.
+Compression reduces network bandwidth, but increases server-side load.
+
+```sh
+{{% get-shared-text "api/v2.0/write/write-compress.sh" %}}
+```
+{{% /note %}}
+
+_For information about **InfluxDB API response codes**, see
+[InfluxDB API Write documentation](/influxdb/v2.2/api/#operation/PostWrite)._
diff --git a/content/influxdb/v2.2/write-data/developer-tools/client-libraries.md b/content/influxdb/v2.2/write-data/developer-tools/client-libraries.md
new file mode 100644
index 000000000..565ec667f
--- /dev/null
+++ b/content/influxdb/v2.2/write-data/developer-tools/client-libraries.md
@@ -0,0 +1,15 @@
+---
+title: Write data with client libraries
+weight: 204
+description: >
+  Use client libraries to write data to InfluxDB.
+menu:
+  influxdb_2_2:
+    name: Client libraries
+    identifier: write-client-libraries
+    parent: Developer tools
+---
+
+Use language-specific client libraries to integrate with the InfluxDB v2 API.
+
+See [Client libraries reference](/influxdb/v2.2/api-guide/client-libraries/) for more information.
diff --git a/content/influxdb/v2.2/write-data/developer-tools/csv.md b/content/influxdb/v2.2/write-data/developer-tools/csv.md
new file mode 100644
index 000000000..4185682e7
--- /dev/null
+++ b/content/influxdb/v2.2/write-data/developer-tools/csv.md
@@ -0,0 +1,601 @@
+---
+title: Write CSV data to InfluxDB
+description: >
+  Write CSV data with the [`influx write` command](/influxdb/cloud/reference/cli/influx/write/) or Flux.
+  Include annotations with the CSV data to determine how the data translates into
+  [line protocol](/influxdb/v2.2/reference/syntax/line-protocol/).
+menu:
+  influxdb_2_2:
+    name: Write CSV data
+    parent: Developer tools
+aliases:
+  - /influxdb/v2.2/write-data/csv/
+weight: 204
+related:
+  - /influxdb/v2.2/reference/syntax/line-protocol/
+  - /influxdb/v2.2/reference/syntax/annotated-csv/
+  - /influxdb/v2.2/reference/cli/influx/write/
+---
+
+Write CSV data with the following methods:
+
+- [Upload a file or manually paste data in the UI](/influxdb/cloud/write-data/no-code/load-data/#load-data-by-uploading-a-csv-or-line-protocol-file)
+- [influx write command](#influx-write-command)
+- [Telegraf](#telegraf)
+- [Flux](#flux)
+
+## influx write command
+
+Use the [`influx write` command](/influxdb/v2.2/reference/cli/influx/write/) to write CSV data
+to InfluxDB. Include [Extended annotated CSV](/influxdb/v2.2/reference/syntax/annotated-csv/extended/)
+annotations to specify how the data translates into [line protocol](/influxdb/v2.2/reference/syntax/line-protocol/).
+Include annotations in the CSV file or inject them using the `--header` flag of
+the `influx write` command.
+
+##### On this page
+- [CSV Annotations](#csv-annotations)
+- [Inject annotation headers](#inject-annotation-headers)
+- [Skip annotation headers](#skip-annotation-headers)
+- [Process input as CSV](#process-input-as-csv)
+- [Specify CSV character encoding](#specify-csv-character-encoding)
+- [Skip rows with errors](#skip-rows-with-errors)
+- [Advanced examples](#advanced-examples)
+
+##### Example write command
+```sh
+influx write -b example-bucket -f path/to/example.csv
+```
+
+##### example.csv
+```
+#datatype measurement,tag,double,dateTime:RFC3339
+m,host,used_percent,time
+mem,host1,64.23,2020-01-01T00:00:00Z
+mem,host2,72.01,2020-01-01T00:00:00Z
+mem,host1,62.61,2020-01-01T00:00:10Z
+mem,host2,72.98,2020-01-01T00:00:10Z
+mem,host1,63.40,2020-01-01T00:00:20Z
+mem,host2,73.77,2020-01-01T00:00:20Z
+```
+
+##### Resulting line protocol
+```
+mem,host=host1 used_percent=64.23 1577836800000000000
+mem,host=host2 used_percent=72.01 1577836800000000000
+mem,host=host1 used_percent=62.61 1577836810000000000
+mem,host=host2 used_percent=72.98 1577836810000000000
+mem,host=host1 used_percent=63.40 1577836820000000000
+mem,host=host2 used_percent=73.77 1577836820000000000
+```
+
+{{% note %}}
+To test the CSV to line protocol conversion process, use the `influx write dryrun`
+command to print the resulting line protocol to stdout rather than write to InfluxDB.
+{{% /note %}}
+
+{{% note %}}
+##### "too many open files" errors
+
+When attempting to write large amounts of CSV data into InfluxDB, you might see an error like the following:
+
+```
+Error: Failed to write data: unexpected error writing points to database: [shard <#>] fcntl: too many open files.
+```
+
+To fix this error on Linux or macOS, run the following command to increase the number of open files allowed:
+
+  ```
+  ulimit -n 10000
+  ```
+
+macOS users, to persist the `ulimit` setting, follow the [recommended steps](https://unix.stackexchange.com/a/221988/471569) for your operating system version.
+
+{{% /note %}}
+
+## Telegraf 
+
+Use CSV data format in Telegraf as a way to write CSV data to InfluxDB. 
+
+For more information, see: 
+
+- [CSV input data format](/telegraf/v1.19/data_formats/input/csv/)
+- [Use Telegraf to write data](/influxdb/v2.2/write-data/no-code/use-telegraf/)
+
+## CSV Annotations
+Use **CSV annotations** to specify which element of line protocol each CSV column
+represents and how to format the data. CSV annotations are rows at the beginning
+of a CSV file that describe column properties.
+
+The `influx write` command supports [Extended annotated CSV](/influxdb/v2.2/reference/syntax/annotated-csv/extended)
+which provides options for specifying how CSV data should be converted into line
+protocol and how data is formatted.
+
+To write data to InfluxDB, data must include the following:
+
+- [measurement](/influxdb/v2.2/reference/syntax/line-protocol/#measurement)
+- [field set](/influxdb/v2.2/reference/syntax/line-protocol/#field-set)
+- [timestamp](/influxdb/v2.2/reference/syntax/line-protocol/#timestamp) _(Optional but recommended)_
+- [tag set](/influxdb/v2.2/reference/syntax/line-protocol/#tag-set) _(Optional)_
+
+Use CSV annotations to specify which of these elements each column represents.
+
+## Write raw query results back to InfluxDB
+Flux returns query results in [annotated CSV](/influxdb/v2.2/reference/syntax/annotated-csv/).
+These results include all annotations necessary to write the data back to InfluxDB.
+
+## Inject annotation headers
+If the CSV data you want to write to InfluxDB does not contain the annotations
+required to properly convert the data to line protocol, use the `--header` flag
+to inject annotation rows into the CSV data.
+
+```sh
+influx write -b example-bucket \
+  -f path/to/example.csv \
+  --header "#constant measurement,birds" \
+  --header "#datatype dateTime:2006-01-02,long,tag"
+```
+
+{{< flex >}}
+{{% flex-content %}}
+##### example.csv
+```
+date,sighted,loc
+2020-01-01,12,Boise
+2020-06-01,78,Boise
+2020-01-01,54,Seattle
+2020-06-01,112,Seattle
+2020-01-01,9,Detroit
+2020-06-01,135,Detroit
+```
+{{% /flex-content %}}
+{{% flex-content %}}
+##### Resulting line protocol
+```
+birds,loc=Boise sighted=12i 1577836800000000000
+birds,loc=Boise sighted=78i 1590969600000000000
+birds,loc=Seattle sighted=54i 1577836800000000000
+birds,loc=Seattle sighted=112i 1590969600000000000
+birds,loc=Detroit sighted=9i 1577836800000000000
+birds,loc=Detroit sighted=135i 1590969600000000000
+```
+{{% /flex-content %}}
+{{< /flex >}}
+
+#### Use files to inject headers
+The `influx write` command supports importing multiple files in a single command.
+Include annotations and header rows in their own file and import them with the write command.
+Files are read in the order in which they're provided.
+
+```sh
+influx write -b example-bucket \
+  -f path/to/headers.csv \
+  -f path/to/example.csv
+```
+
+{{< flex >}}
+{{% flex-content %}}
+##### headers.csv
+```
+#constant measurement,birds
+#datatype dateTime:2006-01-02,long,tag
+```
+{{% /flex-content %}}
+{{% flex-content %}}
+##### example.csv
+```
+date,sighted,loc
+2020-01-01,12,Boise
+2020-06-01,78,Boise
+2020-01-01,54,Seattle
+2020-06-01,112,Seattle
+2020-01-01,9,Detroit
+2020-06-01,135,Detroit
+```
+{{% /flex-content %}}
+{{< /flex >}}
+
+##### Resulting line protocol
+```
+birds,loc=Boise sighted=12i 1577836800000000000
+birds,loc=Boise sighted=78i 1590969600000000000
+birds,loc=Seattle sighted=54i 1577836800000000000
+birds,loc=Seattle sighted=112i 1590969600000000000
+birds,loc=Detroit sighted=9i 1577836800000000000
+birds,loc=Detroit sighted=135i 1590969600000000000
+```
+
+## Skip annotation headers
+Some CSV data may include header rows that conflict with or lack the annotations
+necessary to write CSV data to InfluxDB.
+Use the `--skipHeader` flag to specify the **number of rows to skip** at the
+beginning of the CSV data.
+
+```sh
+influx write -b example-bucket \
+  -f path/to/example.csv \
+  --skipHeader=2
+```
+
+You can then [inject new header rows](#inject-annotation-headers) to rename columns
+and provide the necessary annotations.
+
+## Process input as CSV
+The `influx write` command automatically processes files with the `.csv` extension as CSV files.
+If your CSV file uses a different extension, use the `--format` flat to explicitly
+declare the format of the input file.
+
+```sh
+influx write -b example-bucket \
+  -f path/to/example.txt \
+  --format csv
+```
+
+{{% note %}}
+The `influx write` command assumes all input files are line protocol unless they
+include the `.csv` extension or you declare the `csv`.
+{{% /note %}}
+
+## Specify CSV character encoding
+The `influx write` command assumes CSV files contain UTF-8 encoded characters.
+If your CSV data uses different character encoding, specify the encoding
+with the `--encoding`.
+
+```sh
+influx write -b example-bucket \
+  -f path/to/example.csv \
+  --encoding "UTF-16"
+```
+
+## Skip rows with errors
+If a row in your CSV data is missing an
+[element required to write to InfluxDB](/influxdb/v2.2/reference/syntax/line-protocol/#elements-of-line-protocol)
+or data is incorrectly formatted, when processing the row, the `influx write` command
+returns an error and cancels the write request.
+To skip rows with errors, use the `--skipRowOnError` flag.
+
+```sh
+influx write -b example-bucket \
+  -f path/to/example.csv \
+  --skipRowOnError
+```
+
+{{% warn %}}
+Skipped rows are ignored and are not written to InfluxDB.
+{{% /warn %}}
+
+Use the `--errors-file` flag to record errors to a file.
+The error file identifies all rows that cannot be imported and includes error messages for debugging.
+For example:
+
+```error : line 3: column 'a': '1.1' cannot fit into long data type
+cpu,1.1
+```
+
+## Advanced examples
+
+- [Define constants](#define-constants)
+- [Annotation shorthand](#annotation-shorthand)
+- [Ignore columns](#ignore-columns)
+- [Use alternate numeric formats](#use-alternate-numeric-formats)
+- [Use alternate boolean format](#use-alternate-boolean-format)
+- [Use different timestamp formats](#use-different-timestamp-formats)
+
+---
+
+### Define constants
+Use the Extended annotated CSV [`#constant` annotation](/influxdb/v2.2/reference/syntax/annotated-csv/extended/#constant)
+to add a column and value to each row in the CSV data.
+
+{{< flex >}}
+{{% flex-content %}}
+##### CSV with constants
+```
+#constant measurement,example
+#constant tag,source,csv
+#datatype long,dateTime:RFC3339
+count,time
+1,2020-01-01T00:00:00Z
+4,2020-01-02T00:00:00Z
+9,2020-01-03T00:00:00Z
+18,2020-01-04T00:00:00Z
+```
+{{% /flex-content %}}
+{{% flex-content %}}
+##### Resulting line protocol
+```
+example,source=csv count=1 1577836800000000000
+example,source=csv count=4 1577923200000000000
+example,source=csv count=9 1578009600000000000
+example,source=csv count=18 1578096000000000000
+```
+{{% /flex-content %}}
+{{< /flex >}}
+
+---
+
+### Annotation shorthand
+Extended annotated CSV supports [annotation shorthand](/influxdb/v2.2/reference/syntax/annotated-csv/extended/#annotation-shorthand),
+which lets you define the **column label**, **datatype**, and **default value** in the column header.
+
+{{< flex >}}
+{{% flex-content %}}
+##### CSV with annotation shorthand
+```
+m|measurement,count|long|0,time|dateTime:RFC3339
+example,1,2020-01-01T00:00:00Z
+example,4,2020-01-02T00:00:00Z
+example,,2020-01-03T00:00:00Z
+example,18,2020-01-04T00:00:00Z
+```
+{{% /flex-content %}}
+{{% flex-content %}}
+##### Resulting line protocol
+```
+example count=1 1577836800000000000
+example count=4 1577923200000000000
+example count=0 1578009600000000000
+example count=18 1578096000000000000
+```
+{{% /flex-content %}}
+{{< /flex >}}
+
+#### Replace column header with annotation shorthand
+It's possible to replace the column header row in a CSV file with annotation
+shorthand without modifying the CSV file.
+This lets you define column data types and default values while writing to InfluxDB.
+
+To replace an existing column header row with annotation shorthand:
+
+1. Use the `--skipHeader` flag to ignore the existing column header row.
+2. Use the `--header` flag to inject a new column header row that uses annotation shorthand.
+
+```sh
+influx write -b example-bucket \
+  -f example.csv \
+  --skipHeader=1
+  --header="m|measurement,count|long|0,time|dateTime:RFC3339"
+```
+
+{{< flex >}}
+{{% flex-content %}}
+##### Unmodified example.csv
+```
+m,count,time
+example,1,2020-01-01T00:00:00Z
+example,4,2020-01-02T00:00:00Z
+example,,2020-01-03T00:00:00Z
+example,18,2020-01-04T00:00:00Z
+```
+{{% /flex-content %}}
+{{% flex-content %}}
+##### Resulting line protocol
+```
+example count=1i 1577836800000000000
+example count=4i 1577923200000000000
+example count=0i 1578009600000000000
+example count=18i 1578096000000000000
+```
+{{% /flex-content %}}
+{{< /flex >}}
+
+---
+
+### Ignore columns
+Use the Extended annotated CSV [`#datatype ignored` annotation](/influxdb/v2.2/reference/syntax/annotated-csv/extended/#ignored)
+to ignore columns when writing CSV data to InfluxDB.
+
+{{< flex >}}
+{{% flex-content %}}
+##### CSV data with ignored column
+```
+#datatype measurement,long,time,ignored
+m,count,time,foo
+example,1,2020-01-01T00:00:00Z,bar
+example,4,2020-01-02T00:00:00Z,bar
+example,9,2020-01-03T00:00:00Z,baz
+example,18,2020-01-04T00:00:00Z,baz
+```
+{{% /flex-content %}}
+{{% flex-content %}}
+##### Resulting line protocol
+```
+m count=1i 1577836800000000000
+m count=4i 1577923200000000000
+m count=9i 1578009600000000000
+m count=18i 1578096000000000000
+```
+{{% /flex-content %}}
+{{< /flex >}}
+
+---
+
+### Use alternate numeric formats
+If your CSV data contains numeric values that use a non-default fraction separator (`.`)
+or contain group separators, [define your numeric format](/influxdb/v2.2/reference/syntax/annotated-csv/extended/#double)
+in the `double`, `long`, and `unsignedLong` datatype annotations.
+
+{{% note %}}
+If your **numeric format separators** include a comma (`,`), wrap the column annotation in double
+quotes (`""`) to prevent the comma from being parsed as a column separator or delimiter.
+You can also [define a custom column separator](/influxdb/v2.2/reference/syntax/annotated-csv/extended/#define-custom-column-separator).
+{{% /note %}}
+
+{{< tabs-wrapper >}}
+{{% tabs %}}
+[Floats](#)
+[Integers](#)
+[Uintegers](#)
+{{% /tabs %}}
+{{% tab-content %}}
+{{< flex >}}
+{{% flex-content %}}
+##### CSV with non-default float values
+```
+#datatype measurement,"double:.,",dateTime:RFC3339
+m,lbs,time
+example,"1,280.7",2020-01-01T00:00:00Z
+example,"1,352.5",2020-01-02T00:00:00Z
+example,"1,862.8",2020-01-03T00:00:00Z
+example,"2,014.9",2020-01-04T00:00:00Z
+```
+{{% /flex-content %}}
+{{% flex-content %}}
+##### Resulting line protocol
+```
+example lbs=1280.7 1577836800000000000
+example lbs=1352.5 1577923200000000000
+example lbs=1862.8 1578009600000000000
+example lbs=2014.9 1578096000000000000
+```
+{{% /flex-content %}}
+{{< /flex >}}
+{{% /tab-content %}}
+
+{{% tab-content %}}
+{{< flex >}}
+{{% flex-content %}}
+##### CSV with non-default integer values
+```
+#datatype measurement,"long:.,",dateTime:RFC3339
+m,lbs,time
+example,"1,280.0",2020-01-01T00:00:00Z
+example,"1,352.0",2020-01-02T00:00:00Z
+example,"1,862.0",2020-01-03T00:00:00Z
+example,"2,014.9",2020-01-04T00:00:00Z
+```
+{{% /flex-content %}}
+{{% flex-content %}}
+##### Resulting line protocol
+```
+example lbs=1280i 1577836800000000000
+example lbs=1352i 1577923200000000000
+example lbs=1862i 1578009600000000000
+example lbs=2014i 1578096000000000000
+```
+{{% /flex-content %}}
+{{< /flex >}}
+{{% /tab-content %}}
+
+{{% tab-content %}}
+{{< flex >}}
+{{% flex-content %}}
+##### CSV with non-default uinteger values
+```
+#datatype measurement,"unsignedLong:.,",dateTime:RFC3339
+m,lbs,time
+example,"1,280.0",2020-01-01T00:00:00Z
+example,"1,352.0",2020-01-02T00:00:00Z
+example,"1,862.0",2020-01-03T00:00:00Z
+example,"2,014.9",2020-01-04T00:00:00Z
+```
+{{% /flex-content %}}
+{{% flex-content %}}
+##### Resulting line protocol
+```
+example lbs=1280u 1577836800000000000
+example lbs=1352u 1577923200000000000
+example lbs=1862u 1578009600000000000
+example lbs=2014u 1578096000000000000
+```
+{{% /flex-content %}}
+{{< /flex >}}
+{{% /tab-content %}}
+{{< /tabs-wrapper >}}
+
+---
+
+### Use alternate boolean format
+Line protocol supports only [specific boolean values](/influxdb/v2.2/reference/syntax/line-protocol/#boolean).
+If your CSV data contains boolean values that line protocol does not support,
+[define your boolean format](/influxdb/v2.2/reference/syntax/annotated-csv/extended/#boolean)
+in the `boolean` datatype annotation.
+
+{{< flex >}}
+{{% flex-content %}}
+##### CSV with non-default boolean values
+```
+#datatype measurement,"boolean:y,Y,1:n,N,0",dateTime:RFC3339
+m,verified,time
+example,y,2020-01-01T00:00:00Z
+example,n,2020-01-02T00:00:00Z
+example,1,2020-01-03T00:00:00Z
+example,N,2020-01-04T00:00:00Z
+```
+{{% /flex-content %}}
+{{% flex-content %}}
+##### Resulting line protocol
+```
+example verified=true 1577836800000000000
+example verified=false 1577923200000000000
+example verified=true 1578009600000000000
+example verified=false 1578096000000000000
+```
+{{% /flex-content %}}
+{{< /flex >}}
+
+---
+
+### Use different timestamp formats
+The `influx write` command automatically detects **RFC3339** and **number** formatted
+timestamps when converting CSV to line protocol.
+If using a different timestamp format, [define your timestamp format](/influxdb/v2.2/reference/syntax/annotated-csv/extended/#datetime)
+in the `dateTime` datatype annotation.
+
+{{< flex >}}
+{{% flex-content %}}
+##### CSV with non-default timestamps
+```
+#datatype measurement,dateTime:2006-01-02,field
+m,time,lbs
+example,2020-01-01,1280.7
+example,2020-01-02,1352.5
+example,2020-01-03,1862.8
+example,2020-01-04,2014.9
+```
+{{% /flex-content %}}
+{{% flex-content %}}
+##### Resulting line protocol
+```
+example lbs=1280.7 1577836800000000000
+example lbs=1352.5 1577923200000000000
+example lbs=1862.8 1578009600000000000
+example lbs=2014.9 1578096000000000000
+```
+{{% /flex-content %}}
+{{< /flex >}}
+
+## Flux
+
+Use the [csv.from()](/{{< latest "flux" >}}/stdlib/csv/from/) and [to()](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/to/) Flux functions to write an annotated CSV to the bucket of your choice.
+
+{{< youtube wPKZ9i0DulQ >}}
+
+The experimental [csv.from()](/{{< latest "flux" >}}/stdlib/csv/from/) function lets you write CSV from a URL.
+The example below writes [NOAA water sample data](/influxdb/v2.2/reference/sample-data/#noaa-water-sample-data) to an example `noaa` bucket in an example organization:
+
+```js
+import "experimental/csv"
+
+csv.from(url: "https://influx-testdata.s3.amazonaws.com/noaa.csv")
+    |> to(bucket: "noaa", org: "example-org")
+```
+
+{{% note %}}
+#### Required annotations and columns
+To write CSV data to InfluxDB with Flux, you must include _all_ of the following annotations and columns:
+
+- `datatype`
+- `group`
+- `default`
+
+See [annotations](/influxdb/v2.2/reference/syntax/annotated-csv/#annotations) for more information.
+With Flux, you must also include a comma between the annotation name and the annotation values (this differs from the `influx write` command).
+See an example of valid syntax for [annotated CSV in Flux](/influxdb/v2.2/reference/syntax/annotated-csv/#annotated-csv-in-flux).
+
+Required columns:
+
+- `_time`
+- `_measurement`
+- `_field`
+- `_value`
+{{% /note %}}
diff --git a/content/influxdb/v2.2/write-data/developer-tools/influx-cli.md b/content/influxdb/v2.2/write-data/developer-tools/influx-cli.md
new file mode 100644
index 000000000..e7a52d03e
--- /dev/null
+++ b/content/influxdb/v2.2/write-data/developer-tools/influx-cli.md
@@ -0,0 +1,56 @@
+---
+title: Write data with the influx CLI
+weight: 205
+description: >
+  Use the `influx write` command to write data to InfluxDB from the command line.
+menu:
+  influxdb_2_2:
+    name: Influx CLI
+    parent: Developer tools
+related:
+  - /influxdb/v2.2/write-data/developer-tools/csv/
+---
+
+To write data from the command line, use the [`influx write` command](/influxdb/v2.2/reference/cli/influx/write/).
+Include the following in your command:
+
+| Requirement          | Include by                                                                                         |
+|:-----------          |:----------                                                                                         |
+| Organization         | Use the `-o`,`--org`, or `--org-id` flags.                                                         |
+| Bucket               | Use the `-b`, `--bucket`, or `--bucket-id` flags.                                                  |
+| Precision            | Use the `-p`, `--precision` flag.                                                                  |
+| API token | Set the `INFLUX_TOKEN` environment variable or use the `t`, `--token` flag.                        |
+| Data                 | Write data using **line protocol** or **annotated CSV**. Pass a file with the `-f`, `--file` flag. |
+
+_See [Line protocol](/influxdb/v2.2/reference/syntax/line-protocol/) and [Annotated CSV](/influxdb/v2.2/reference/syntax/annotated-csv)_
+
+#### Example influx write commands
+
+##### Write a single line of line protocol
+```sh
+influx write \
+  -b bucketName \
+  -o orgName \
+  -p s \
+  'myMeasurement,host=myHost testField="testData" 1556896326'
+```
+
+##### Write line protocol from a file
+```sh
+influx write \
+  -b bucketName \
+  -o orgName \
+  -p s \
+  --format=lp
+  -f /path/to/line-protocol.txt
+```
+
+##### Write annotated CSV from a file
+```sh
+influx write \
+  -b bucketName \
+  -o orgName \
+  -p s \
+  --format=csv
+  -f /path/to/data.csv
+```
diff --git a/content/influxdb/v2.2/write-data/developer-tools/scrape-prometheus-metrics.md b/content/influxdb/v2.2/write-data/developer-tools/scrape-prometheus-metrics.md
new file mode 100644
index 000000000..6a5260ceb
--- /dev/null
+++ b/content/influxdb/v2.2/write-data/developer-tools/scrape-prometheus-metrics.md
@@ -0,0 +1,105 @@
+---
+title: Scrape Prometheus metrics
+seotitle: Scrape Prometheus metrics into InfluxDB
+weight: 205
+description: >
+  Use Telegraf, InfluxDB scrapers, or the `prometheus.scrape` Flux function to
+  scrape Prometheus-formatted metrics from an HTTP-accessible endpoint and store
+  them in InfluxDB.
+menu:
+  influxdb_2_2:
+    name: Scrape Prometheus metrics
+    parent: Developer tools
+related:
+  - /{{< latest "telegraf" >}}/plugins/#input-prometheus, Telegraf Prometheus input plugin
+  - /{{< latest "flux" >}}/prometheus/scrape-prometheus/, Scrape Prometheus metrics with Flux
+  - /{{< latest "flux" >}}/stdlib/experimental/prometheus/scrape/
+  - /{{< latest "flux" >}}/prometheus/metric-types/
+  - /influxdb/v2.2/reference/prometheus-metrics/
+  - /influxdb/v2.2/write-data/no-code/scrape-data/
+influxdb/v2.2/tags: [prometheus, scraper]
+---
+
+Use [Telegraf](/{{< latest "telegraf" >}}/){{% oss-only %}}, [InfluxDB scrapers](/influxdb/v2.2/write-data/no-code/scrape-data/),{{% /oss-only %}}
+or the [`prometheus.scrape` Flux function](/{{< latest "flux" >}}/stdlib/experimental/prometheus/scrape/)
+to scrape Prometheus-formatted metrics from an HTTP-accessible endpoint and store them in InfluxDB.
+
+{{% oss-only %}}
+
+- [Use Telegraf](#use-telegraf)
+- [Use an InfluxDB scraper](#use-an-influxdb-scraper)
+- [Use prometheus.scrape()](#use-prometheusscrape)
+
+{{% /oss-only %}}
+{{% cloud-only %}}
+
+- [Use Telegraf](#use-telegraf)
+- [Use prometheus.scrape()](#use-prometheusscrape)
+
+{{% /cloud-only %}}
+
+## Use Telegraf
+To use Telegraf to scrape Prometheus-formatted metrics from an HTTP-accessible
+endpoint and write them to InfluxDB{{% cloud-only %}} Cloud{{% /cloud-only %}}, follow these steps:
+
+1. Add the [Prometheus input plugin](/{{< latest "telegraf" >}}/plugins/#input-prometheus) to your Telegraf configuration file.
+    1. Set the `urls` to scrape metrics from.
+    2. Set the `metric_version` configuration option to specify which
+      [metric parsing version](/influxdb/v2.2/reference/prometheus-metrics/) to use
+      _(version `2` is recommended)_.
+2. Add the [InfluxDB v2 output plugin](/{{< latest "telegraf" >}}/plugins/#output-influxdb_v2)
+   to your Telegraf configuration file and configure it to to write to
+   InfluxDB{{% cloud-only %}} Cloud{{% /cloud-only %}}.
+  
+##### Example telegraf.conf
+```toml
+# ...
+
+## Collect Prometheus formatted metrics
+[[inputs.prometheus]]
+  urls = ["http://example.com/metrics"]
+  metric_version = 2
+
+## Write Prometheus formatted metrics to InfluxDB
+[[outputs.influxdb_v2]]
+  urls = ["http://localhost:8086"]
+  token = "$INFLUX_TOKEN"
+  organization = "example-org"
+  bucket = "example-bucket"
+
+# ...
+```
+
+{{% oss-only %}}
+
+## Use an InfluxDB scraper
+InfluxDB scrapers automatically scrape Prometheus-formatted metrics from an 
+HTTP-accessible endpoint at a regular interval.
+For information about setting up an InfluxDB scraper, see
+[Scrape data using InfluxDB scrapers](/influxdb/v2.2/write-data/no-code/scrape-data/).
+
+{{% /oss-only %}}
+
+## Use prometheus.scrape()
+To use the [`prometheus.scrape()` Flux function](/{{< latest "flux" >}}/stdlib/experimental/prometheus/scrape/)
+to scrape Prometheus-formatted metrics from an HTTP-accessible endpoint and write
+them to InfluxDB{{% cloud-only %}} Cloud{{% /cloud-only %}}, do the following in your Flux script:
+
+1. Import the [`experimental/prometheus` package](/{{< latest "flux" >}}/stdlib/experimental/prometheus/).
+2. Use `prometheus.scrape()` and provide the URL to scrape metrics from.
+3. Use [`to()`](/{{< latest "flux" >}}/stdlib/influxdata/influxdb/to/) and specify the  InfluxDB{{% cloud-only %}} Cloud{{% /cloud-only %}} bucket to write
+  the scraped metrics to.
+
+##### Example Flux script
+```js
+import "experimental/prometheus"
+
+prometheus.scrape(url: "http://example.com/metrics")
+    |> to(bucket: "example-bucket")
+```
+
+4. (Optional) To scrape Prometheus metrics at regular intervals using Flux, add your Flux
+scraping script as an [InfluxDB task](/{{< latest "influxdb" >}}/process-data/).
+
+_For information about scraping Prometheus-formatted metrics with `prometheus.scrape()`,
+see [Scrape Prometheus metrics with Flux](/{{< latest "flux" >}}/prometheus/scrape-prometheus/)._
diff --git a/content/influxdb/v2.2/write-data/developer-tools/third-party-solutions.md b/content/influxdb/v2.2/write-data/developer-tools/third-party-solutions.md
new file mode 100644
index 000000000..3130cd301
--- /dev/null
+++ b/content/influxdb/v2.2/write-data/developer-tools/third-party-solutions.md
@@ -0,0 +1,61 @@
+---
+title: Write data with third-party technologies
+weight: 103
+description: >
+  Write data to InfluxDB using third-party developer tools.
+aliases:
+menu:
+  influxdb_2_2:
+    name: Third-party developer tools
+    parent: Developer tools
+---
+
+Configure third-party technologies to send line protocol directly to InfluxDB.
+
+## AWS Lambda via CloudFormation template
+
+Write to InfluxDB with AWS Lambda, Amazon Web Services' serverless offering. This example provides a CloudFormation template that collects earthquake from the [United States Geological Survey (USGS)](https://www.usgs.gov/) every hour and outputs it as line protocol into an InfluxDB bucket.
+
+The [template](https://influxdata-lambda.s3.amazonaws.com/GeoLambda.yml) contains the following sections:
+
+- Lines 1-20: Define variables that the template asks for when it's installed.
+- Lines 21-120: Handle a quirk of Lambda deployments that requires the Lambda assets to be in your region before deployment. As there is no elegant workaround, these 100 lines create an S3 bucket in your account in the region you're creating the stack and copies in these resources.
+- Lines 121-132: Define a role with basic permission to run the Lambda.
+- Lines 133-144: Define a Python library layer. This layer packages the Python HTTP library, a Python S2 Geometry library, and the InfluxDB Python client library.
+- Lines 145-165: Define the Lambda function, a short Python script zipped up in a file called `geo_lambda.zip`.
+- Lines 166-188: Define an event rule with permission to run the Lambda every hour.
+
+### Deploy the template
+
+1. Log into your free AWS account and search for the CloudFormation service. Make sure you’re in the AWS region you want to deploy the Lambda to⁠.
+2. Click **Create Stack**.
+3. In the **Prerequisite - Prepare Template** section, select **Template is ready**.
+4. In the **Specify template** section:
+  - Under **Template source**, select **Amazon S3 URL**.
+  - In the **Amazon S3 URL** field, enter the CloudFormation template URL: `https://influxdata-lambda.s3.amazonaws.com/GeoLambda.yml`
+5. Click **Next**.  
+6. Enter a name in the **Stack name** field.  
+7. Enter the following InfluxDB details:
+  - Organization ID
+  - Bucket ID of the bucket the Lambda writes to
+  - Token with permission to write to the bucket
+  - InfluxDB URL
+8. Do not alter or add to any other fields. Click **Next**.
+9. Select the **I acknowledge that AWS CloudFormation might create IAM resources** check box.
+10. Click **Create Stack**.
+
+After a few minutes, the stack deploys to your region. To view the new Lambda, select **Services > AWS Lambda**. On the Lambda functions page, you should see your new Lambda. The `CopyZipsFunction` is the helper copy function, and the `GeoPythonLambda` does the data collection and writing work:
+
+{{< img-hd src="/img/cloudformation1.png" alt="GeoPythonLambda data in InfluxDB" />}}
+
+### Verify your setup
+
+`GeoPythonLambda` should run every hour based on the AWS Rule we set up, but you should test and confirm it works.  
+
+1. Click `GeoPythonLambda`, and then click **Test**.
+2. The test requires an input definition, but this Lambda has no input requirements, so click through and save the default dataset.
+3. If the test is successful, a green **Execution result: succeeded** message appears.
+
+With the data points written, when you log into your InfluxDB UI, you’ll be able to explore the geolocation earthquake data:
+
+{{< img-hd src="/img/cloudformation2.png" alt="GeoPythonLambda data in InfluxDB" />}}
diff --git a/content/influxdb/v2.2/write-data/no-code/_index.md b/content/influxdb/v2.2/write-data/no-code/_index.md
new file mode 100644
index 000000000..8c1fc6936
--- /dev/null
+++ b/content/influxdb/v2.2/write-data/no-code/_index.md
@@ -0,0 +1,17 @@
+---
+title: Write data to InfluxDB without coding
+weight: 101
+description: >
+  Use existing tools to write data to InfluxDB without writing code.
+aliases:
+  - /influxdb/v2.2/collect-data/advanced-telegraf
+  - /influxdb/v2.2/collect-data/use-telegraf
+menu:
+  influxdb_2_2:
+    name: No-code solutions
+    parent: Write data
+---
+
+The following options let you write data to InfluxDB without writing any code. Some options require a minimal amount of configuration.
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/write-data/no-code/load-data.md b/content/influxdb/v2.2/write-data/no-code/load-data.md
new file mode 100644
index 000000000..499fd2113
--- /dev/null
+++ b/content/influxdb/v2.2/write-data/no-code/load-data.md
@@ -0,0 +1,79 @@
+---
+title: Load data from sources in the InfluxDB user interface (UI)
+seotitle: Load data source in UI
+list_title: Load data source in UI
+weight: 101
+description: >
+  Load data from sources in the InfluxDB user interface (UI). Choose from popular client libraries (such as Python, Ruby, Scala, and more!) or load data with a Telegraf plugin (like MQTT Consumer, MySQL, File, and many more!).
+menu:
+  influxdb_2_2:
+    name: Load data source in UI
+    parent: Write data
+---
+
+Load data from the following sources in the InfluxDB user interface (UI):
+
+- [CSV or line protocol file](#load-csv-or-line-protocol-in-ui)
+- [Line protocol](#load-data-using-line-protocol)
+- [Client libraries](#load-data-from-a-client-library-in-the-ui)
+- [Telegraf plugins](#load-data-from-a-telegraf-plugin-in-the-ui)
+
+### Load CSV or line protocol in UI
+
+Load CSV or line protocol data by uploading a file or pasting the data manually into the UI.
+
+1. In the navigation menu on the left, click **Load Data** > **Sources**.
+    {{< nav-icon "data" >}}
+2. Under **File Upload**, select the type of data to upload:
+    - **Annotated CSV**. Verify your CSV file follows the supported [annotated CSV](/influxdb/cloud/reference/syntax/annotated-csv/) syntax.
+    - **Line Protocol**. Verify your line protocol file adheres to the following conventions:  
+      - Each line represents a data point.
+      - Each data point requires a:  
+         - [*measurement*](/influxdb/cloud/reference/syntax/line-protocol/#measurement)
+         - [*field set*](/influxdb/cloud/reference/syntax/line-protocol/#field-set)
+         - (Optional) [*tag set*](/influxdb/cloud/reference/syntax/line-protocol/#tag-set)
+         - [*timestamp*](/influxdb/cloud/reference/syntax/line-protocol/#timestamp)
+
+      For more information, see supported [line protocol](/influxdb/cloud/reference/syntax/line-protocol/) syntax.
+
+2. Select the bucket to write to.
+4. Select the **Precision** in the dropdown menu. By default, the precision is set to nanoseconds.
+5. Do one of the following:
+   - To upload file, drag and drop your file onto the UI, and then click **Write Data**.
+   - To enter data manually, select the **Enter Manually** tab, paste your data, and then click **Write Data**.
+
+### Load data from a client library in the UI
+
+1.  In the navigation menu on the left, click **Load Data** > **Sources**.
+    {{< nav-icon "data" >}}
+2. Do one of the following:
+   - Enter a specific client library to search for in the **Search data writing methods** field.
+   - Scroll down to browse available client libraries.
+3. Click the client library to load data from.
+4. Under **Code Sample Options**, you'll see a list of your InfluxDB [tokens](/influxdb/v2.2/reference/glossary/#token) and [buckets](/influxdb/v2.2/reference/glossary/#bucket). Select both an API token and a bucket to write your data to. The selected API token and bucket are automatically added to scripts on the page that you can use to initialize a client and write data.
+5. Click the **Copy to Clipboard** buttons under a script to easily paste the script into your terminal or save the script to reuse for automation.
+6. Run the scripts on the page to do the following as needed:
+   - Install the package, libraries, or client
+   - Write data
+   - Execute a Flux query
+
+### Load data from a Telegraf plugin in the UI
+
+1. In the navigation menu on the left, click **Load Data** > **Sources**.
+    {{< nav-icon "data" >}}
+2. Do one of the following:
+   - Enter a specific Telegraf plugin to search for in the **Search data writing methods** field.
+   - Scroll down to **Telegraf Plugins** and browse available input plugins.
+3. Click the plugin to load data from. The plugin details page opens.
+4. Select one of the options from the **Use this plugin** dropdown:
+   - **Create a new configuration**: Enter a configuration name and select an output bucket, and then click **Continue Configuring**.
+   - **Add to an existing configuration**: Select an existing Telegraf configuration to add this plugin to, and then click **Add to Existing Config**.
+5. Provide a **Telegraf Configuration Name** and an optional **Telegraf Configuration Description**.
+6. Adjust configuration settings as needed. To find configuration settings for a specific plugin, see [Telegraf plugins](/telegraf/latest/plugins/).
+7. Click **Save and Test**.
+8. The **Test Your Configuration** page provides instructions for how to start
+   Telegraf using the generated configuration.
+   _See [Start Telegraf](/influxdb/cloud/write-data/no-code/use-telegraf/auto-config/#start-telegraf) below for detailed information about what each step does._
+9. Once Telegraf is running, click **Listen for Data** to confirm Telegraf is successfully sending data to InfluxDB.
+   Once confirmed, a **Connection Found!** message appears.
+10. Click **Finish**. Your Telegraf configuration name and the associated bucket name appears in the list of Telegraf configurations.
diff --git a/content/influxdb/v2.2/write-data/no-code/scrape-data/_index.md b/content/influxdb/v2.2/write-data/no-code/scrape-data/_index.md
new file mode 100644
index 000000000..7132d26d9
--- /dev/null
+++ b/content/influxdb/v2.2/write-data/no-code/scrape-data/_index.md
@@ -0,0 +1,31 @@
+---
+title: Scrape data using InfluxDB scrapers
+weight: 103
+description: >
+  Scrape data from InfluxDB instances or remote endpoints using InfluxDB scrapers.
+  Create a scraper in the InfluxDB UI to collect metrics from a specified target.
+aliases:
+  - /influxdb/v2.2/collect-data/scraper-metrics-endpoint
+  - /influxdb/v2.2/collect-data/scrape-data
+  - /influxdb/v2.2/write-data/scrape-data
+  - /influxdb/v2.2/write-data/scrapable-endpoints
+influxdb/v2.2/tags: [scraper]
+menu:
+  influxdb_2_2:
+    name: Scrape data
+    parent: No-code solutions
+---
+
+InfluxDB scrapers collect data from specified targets at regular intervals,
+then write the scraped data to an InfluxDB bucket.
+Scrapers can collect data from any HTTP(S)-accessible endpoint that provides data
+in the [Prometheus data format](https://prometheus.io/docs/instrumenting/exposition_formats/).
+
+{{% cloud %}}
+Scrapers are not available in {{< cloud-name "short" >}}.
+{{% /cloud %}}
+
+
+The following articles provide information about creating and managing InfluxDB data scrapers:
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/write-data/no-code/scrape-data/manage-scrapers/_index.md b/content/influxdb/v2.2/write-data/no-code/scrape-data/manage-scrapers/_index.md
new file mode 100644
index 000000000..418fa22e3
--- /dev/null
+++ b/content/influxdb/v2.2/write-data/no-code/scrape-data/manage-scrapers/_index.md
@@ -0,0 +1,17 @@
+---
+title: Manage InfluxDB scrapers
+description: Create, update, and delete InfluxDB data scrapers in the InfluxDB user interface.
+aliases:
+  - /influxdb/v2.2/collect-data/scrape-data/manage-scrapers
+  - /influxdb/v2.2/write-data/scrape-data/manage-scrapers
+menu:
+  influxdb_2_2:
+    name: Manage scrapers
+    parent: Scrape data
+weight: 201
+influxdb/v2.2/tags: [scraper, prometheus]
+---
+
+The following articles walk through managing InfluxDB scrapers:
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/write-data/no-code/scrape-data/manage-scrapers/create-a-scraper.md b/content/influxdb/v2.2/write-data/no-code/scrape-data/manage-scrapers/create-a-scraper.md
new file mode 100644
index 000000000..586b828bc
--- /dev/null
+++ b/content/influxdb/v2.2/write-data/no-code/scrape-data/manage-scrapers/create-a-scraper.md
@@ -0,0 +1,31 @@
+---
+title: Create an InfluxDB scraper
+list_title: Create a scraper
+description: Create an InfluxDB scraper that collects data from InfluxDB or a remote endpoint.
+aliases:
+  - /influxdb/v2.2/collect-data/scrape-data/manage-scrapers/create-a-scraper
+  - /influxdb/v2.2/write-data/scrape-data/manage-scrapers/create-a-scraper
+menu:
+  influxdb_2_2:
+    name: Create a scraper
+    parent: Manage scrapers
+weight: 301
+---
+
+Create a new scraper in the InfluxDB user interface (UI).
+
+## Create a scraper in the InfluxDB UI
+1. In the navigation menu on the left, select **Data** (**Load Data**) > **Scrapers**.
+
+    {{< nav-icon "load data" >}}
+
+3. Click **{{< icon "plus" >}} Create Scraper**.
+4. Enter a **Name** for the scraper.
+5. Select a **Bucket** to store the scraped data.
+6. Enter the **Target URL** to scrape.
+   The default URL value is `http://localhost:8086/metrics`,
+   which provides InfluxDB-specific metrics in the [Prometheus data format](https://prometheus.io/docs/instrumenting/exposition_formats/).
+7. Click **Create**.
+
+The new scraper will begin scraping data after approximately 10 seconds,
+then continue scraping in 10 second intervals.
diff --git a/content/influxdb/v2.2/write-data/no-code/scrape-data/manage-scrapers/delete-a-scraper.md b/content/influxdb/v2.2/write-data/no-code/scrape-data/manage-scrapers/delete-a-scraper.md
new file mode 100644
index 000000000..9e812016a
--- /dev/null
+++ b/content/influxdb/v2.2/write-data/no-code/scrape-data/manage-scrapers/delete-a-scraper.md
@@ -0,0 +1,23 @@
+---
+title: Delete an InfluxDB scraper
+list_title: Delete a scraper
+description: Delete an InfluxDB scraper in the InfluxDB user interface.
+aliases:
+  - /influxdb/v2.2/collect-data/scrape-data/manage-scrapers/delete-a-scraper
+  - /influxdb/v2.2/write-data/scrape-data/manage-scrapers/delete-a-scraper
+menu:
+  influxdb_2_2:
+    name: Delete a scraper
+    parent: Manage scrapers
+weight: 303
+---
+
+Delete a scraper from the InfluxDB user interface (UI).
+
+## Delete a scraper from the InfluxDB UI
+1. In the navigation menu on the left, select **Data** (**Load Data**) > **Scrapers**.
+
+    {{< nav-icon "load data" >}}
+
+3. Hover over the scraper you want to delete and click the **{{< icon "delete" >}}** icon.
+4. Click **Delete**.
diff --git a/content/influxdb/v2.2/write-data/no-code/scrape-data/manage-scrapers/update-a-scraper.md b/content/influxdb/v2.2/write-data/no-code/scrape-data/manage-scrapers/update-a-scraper.md
new file mode 100644
index 000000000..6d080acd8
--- /dev/null
+++ b/content/influxdb/v2.2/write-data/no-code/scrape-data/manage-scrapers/update-a-scraper.md
@@ -0,0 +1,28 @@
+---
+title: Update an InfluxDB scraper
+list_title: Update a scraper
+description: Update an InfluxDB scraper that collects data from InfluxDB or a remote endpoint.
+aliases:
+  - /influxdb/v2.2/collect-data/scrape-data/manage-scrapers/update-a-scraper
+  - /influxdb/v2.2/write-data/scrape-data/manage-scrapers/update-a-scraper
+menu:
+  influxdb_2_2:
+    name: Update a scraper
+    parent: Manage scrapers
+weight: 302
+---
+
+Update a scraper in the InfluxDB user interface (UI).
+
+{{% note %}}
+Scraper **Target URLs** and **Buckets** cannot be updated.
+To modify either, [create a new scraper](/influxdb/v2.2/write-data/no-code/scrape-data/manage-scrapers/create-a-scraper).
+{{% /note %}}
+
+## Update a scraper in the InfluxDB UI
+1. In the navigation menu on the left, select **Data** (**Load Data**) > **Scrapers**.
+
+    {{< nav-icon "load data" >}}
+
+3. Hover over the scraper you would like to update and click the **{{< icon "pencil" >}}** that appears next to the scraper name.
+4. Enter a new name for the scraper. Press Return or click out of the name field to save the change.
diff --git a/content/influxdb/v2.2/write-data/no-code/scrape-data/scrapable-endpoints.md b/content/influxdb/v2.2/write-data/no-code/scrape-data/scrapable-endpoints.md
new file mode 100644
index 000000000..5ea045c49
--- /dev/null
+++ b/content/influxdb/v2.2/write-data/no-code/scrape-data/scrapable-endpoints.md
@@ -0,0 +1,45 @@
+---
+title: Create scrapable endpoints
+seotitle: Create scrapable endpoints for InfluxDB
+description: >
+  InfluxDB scrapers can collect data from any HTTP(S)-accessible endpoint that
+  returns data in the Prometheus data format.
+  This article provides links to information about the Prometheus data format
+  and tools that generate Prometheus-formatted metrics.
+aliases:
+  - /influxdb/v2.2/collect-data/scrape-data/scrapable-endpoints
+menu:
+  influxdb_2_2:
+    parent: Scrape data
+weight: 202
+influxdb/v2.2/tags: [scraper, prometheus]
+---
+
+InfluxDB scrapers can collect data from any HTTP(S)-accessible endpoint that returns data
+in the [Prometheus data format](https://prometheus.io/docs/instrumenting/exposition_formats/).
+The links below provide information about the Prometheus data format and tools
+and clients that generate Prometheus-formatted metrics.
+
+## Prometheus Node Exporter
+The [Prometheus Node Exporter](https://github.com/prometheus/node_exporter) exposes
+a wide variety of hardware- and kernel-related metrics for **\*nix** systems.
+
+##### Helpful links
+[Monitoring linux host metrics with the Node Exporter](https://prometheus.io/docs/guides/node-exporter/)  
+
+## Prometheus exporters and integrations
+[Prometheus exporters and integrations](https://prometheus.io/docs/instrumenting/exporters/)
+export Prometheus metrics from third-party systems or services.
+
+##### Helpful links
+[List of third-party exporters](https://prometheus.io/docs/instrumenting/exporters/#third-party-exporters)  
+[Write a custom Prometheus exporter](https://prometheus.io/docs/instrumenting/writing_exporters/)  
+
+## Prometheus client libraries
+[Prometheus client libraries](https://prometheus.io/docs/instrumenting/clientlibs/)
+instrument applications for each of their respective languages.
+Application metrics are output to an HTTP(S) endpoint where they can be scraped.
+
+##### Helpful links
+[Instrumenting a Go application for Prometheus](https://prometheus.io/docs/guides/go-application/)  
+[Writing Prometheus client libraries](https://prometheus.io/docs/instrumenting/writing_clientlibs/)  
diff --git a/content/influxdb/v2.2/write-data/no-code/third-party.md b/content/influxdb/v2.2/write-data/no-code/third-party.md
new file mode 100644
index 000000000..bd9b3fe16
--- /dev/null
+++ b/content/influxdb/v2.2/write-data/no-code/third-party.md
@@ -0,0 +1,92 @@
+---
+title: Write data with no-code third-party technologies
+weight: 103
+description: >
+  Write data to InfluxDB using third-party technologies that do not require coding.
+menu:
+  influxdb_2_2:
+    name: Third-party technologies
+    parent: No-code solutions
+---
+
+
+A number of third-party technologies can be configured to send line protocol directly to InfluxDB.
+
+
+If you're using any of the following technologies, check out the handy links below to configure these technologies to write data to InfluxDB (**no additional software to download or install**).
+
+{{% note %}}
+Many third-party integrations are community contributions. If there's an integration missing from the list below, please [open a docs issue](https://github.com/influxdata/docs-v2/issues/new/choose) to let us know.
+{{% /note %}}
+
+- (Write metrics and log events only) [Vector 0.9 or later](#configure-vector)
+
+- [Apache NiFi 1.8 or later](#configure-apache-nifi)
+
+- [OpenHAB 3.0 or later](#configure-openhab)
+
+- [Apache JMeter 5.2 or later](#configure-apache-jmeter)
+
+- [Apache Pulsar](#configure-apache-pulsar)
+
+- [FluentD 1.x or later](#configure-fluentd)
+
+
+#### Configure Vector
+
+1. View the **Vector documentation**:
+  - For write metrics, [InfluxDB Metrics Sink](https://vector.dev/docs/reference/sinks/influxdb_metrics/)
+  - For log events, [InfluxDB Logs Sink](https://vector.dev/docs/reference/sinks/influxdb_logs/)
+2. Under **Configuration**, click **v2** to view configuration settings.
+3. Scroll down to **How It Works** for more detail:
+  - [InfluxDB Metrics Sink – How It Works ](https://vector.dev/docs/reference/sinks/influxdb_metrics/#how-it-works)
+  - [InfluxDB Logs Sink – How It Works](https://vector.dev/docs/reference/sinks/influxdb_logs/#how-it-works)
+
+#### Configure Apache NiFi
+
+See the _[InfluxDB Processors for Apache NiFi Readme](https://github.com/influxdata/nifi-influxdb-bundle#influxdb-processors-for-apache-nifi)_ for details.
+
+#### Configure OpenHAB
+
+See the _[InfluxDB Persistence Readme](https://github.com/openhab/openhab-addons/tree/master/bundles/org.openhab.persistence.influxdb)_ for details.
+
+#### Configure Apache JMeter
+
+<!-- after doc updates are made, we can simplify to: See the _[Apache JMeter User's Manual - JMeter configuration](https://jmeter.apache.org/usermanual/realtime-results.html#jmeter-configuration)_ for details. -->
+
+To configure Apache JMeter, complete the following steps in InfluxDB and JMeter.
+
+##### In InfluxDB
+
+1. [Find the name of your organization](/influxdb/v2.2/organizations/view-orgs/) (needed to create a bucket and token).
+2. [Create a bucket using the influx CLI](/influxdb/v2.2/organizations/buckets/create-bucket/#create-a-bucket-using-the-influx-cli) and name it `jmeter`.
+3. [Create a token](/influxdb/v2.2/security/tokens/create-token/).
+
+##### In JMeter
+
+1. Create a [Backend Listener](https://jmeter.apache.org/usermanual/component_reference.html#Backend_Listener) using the _**InfluxDBBackendListenerClient**_ implementation.
+2. In the **Backend Listener implementation** field, enter:
+    ```
+    org.apache.jmeter.visualizers.backend.influxdb.influxdbBackendListenerClient
+    ```
+3. Under **Parameters**, specify the following:
+   - **influxdbMetricsSender**:
+      ```
+      org.apache.jmeter.visualizers.backend.influxdb.HttpMetricsSender
+      ```
+   - **influxdbUrl**: _(include the bucket and org you created in InfluxDB)_
+      ```
+      http://localhost:8086/api/v2/write?org=my-org&bucket=jmeter
+      ```
+   - **application**: `InfluxDB2`
+   - **influxdbToken**: _your InfluxDB API token_
+   - Include additional parameters as needed.
+4. Click **Add** to add the _**InfluxDBBackendListenerClient**_ implementation.
+
+#### Configure Apache Pulsar
+
+See _[InfluxDB sink connector](https://pulsar.apache.org/docs/en/io-influxdb-sink/)_ for details.
+
+#### Configure FluentD
+
+See the _[influxdb-plugin-fluent Readme](https://github.com/influxdata/influxdb-plugin-fluent)_ for details.
diff --git a/content/influxdb/v2.2/write-data/no-code/use-telegraf/_index.md b/content/influxdb/v2.2/write-data/no-code/use-telegraf/_index.md
new file mode 100644
index 000000000..1d30ce406
--- /dev/null
+++ b/content/influxdb/v2.2/write-data/no-code/use-telegraf/_index.md
@@ -0,0 +1,36 @@
+---
+title: Use Telegraf to write data
+seotitle: Use the Telegraf agent to collect and write data
+list_title: Use the Telegraf agent
+weight: 101
+description: >
+  Use Telegraf to collect and write data to InfluxDB v2.2.
+  Create Telegraf configurations in the InfluxDB UI or manually configure Telegraf.
+aliases:
+  - /influxdb/v2.2/collect-data/advanced-telegraf
+  - /influxdb/v2.2/collect-data/use-telegraf
+  - /influxdb/v2.2/write-data/use-telegraf/
+menu:
+  influxdb_2_2:
+    name: Telegraf (agent)
+    parent: No-code solutions
+---
+
+[Telegraf](https://www.influxdata.com/time-series-platform/telegraf/) is InfluxData's
+data collection agent for collecting and reporting metrics.
+Its vast library of input plugins and "plug-and-play" architecture lets you quickly
+and easily collect metrics from many different sources.
+This article describes how to use Telegraf to collect and store data in InfluxDB v2.2.
+
+For a list of available plugins, see [Telegraf plugins](/{{< latest "telegraf" >}}/plugins/).
+
+#### Requirements
+- **Telegraf 1.9.2 or greater**.
+  _For information about installing Telegraf, see the
+  [Telegraf Installation instructions](/{{< latest "telegraf" >}}/introduction/installation/)._
+
+## Configure Telegraf
+Telegraf input and output plugins are enabled and configured in Telegraf's configuration file (`telegraf.conf`).
+You have the following options for configuring Telegraf:
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/write-data/no-code/use-telegraf/auto-config.md b/content/influxdb/v2.2/write-data/no-code/use-telegraf/auto-config.md
new file mode 100644
index 000000000..1a338c7ea
--- /dev/null
+++ b/content/influxdb/v2.2/write-data/no-code/use-telegraf/auto-config.md
@@ -0,0 +1,136 @@
+---
+title: Automatically configure Telegraf
+seotitle: Automatically configure Telegraf for InfluxDB v2.2
+description: >
+  Use the InfluxDB UI to automatically generate a Telegraf configuration,
+  then start Telegraf using the generated configuration file.
+aliases:
+  - /influxdb/v2.2/collect-data/use-telegraf/auto-config
+  - /influxdb/v2.2/write-data/use-telegraf/auto-config
+menu:
+  influxdb_2_2:
+    parent: Telegraf (agent)
+weight: 201
+related:
+  - /influxdb/v2.2/telegraf-configs/create/
+---
+
+The InfluxDB user interface (UI) can automatically create Telegraf configuration files based on user-selected Telegraf plugins.
+This article describes how to create a Telegraf configuration in the InfluxDB UI and
+start Telegraf using the generated configuration file.
+
+{{< youtube M8KP7FAb2L0 >}}
+
+{{% note %}}
+_View the [requirements](/influxdb/v2.2/write-data/no-code/use-telegraf#requirements)
+for using Telegraf with InfluxDB v2.2._
+{{% /note %}}
+
+## Create a Telegraf configuration
+
+1. Open the InfluxDB UI _(default: [localhost:8086](http://localhost:8086))_.
+2. In the navigation menu on the left, select **Data** (**Load Data**) > **Telegraf**.
+
+    {{< nav-icon "load data" >}}
+
+4. Click **{{< icon "plus" >}} Create Configuration**.
+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**.
+7. Review the list of **Plugins to Configure** for configuration requirements.
+   Plugins listed with a <span style="color:#32B08C">{{< icon "check" >}}</span>
+   require no additional configuration.
+   To configure a plugin or access plugin documentation, click the plugin name.
+5. Provide a **Telegraf Configuration Name** and an optional **Telegraf Configuration Description**.
+6. Adjust configuration settings as needed. To find configuration settings for a specific plugin, see [Telegraf plugins](/telegraf/latest/plugins/).
+7. Click **Save and Test**.
+8. The **Test Your Configuration** page provides instructions for how to start Telegraf using the generated configuration.
+  _See [Start Telegraf](#start-telegraf) below for detailed information about what each step does._
+9. Once Telegraf is running, click **Listen for Data** to confirm Telegraf is successfully sending data to InfluxDB.
+  Once confirmed, a **Connection Found!** message appears.
+10. Click **Finish**. Your Telegraf configuration name and the associated bucket name appears in the list of Telegraf configurations.
+
+
+### Windows
+
+If you plan to monitor a Windows host using the System plugin, you must complete the following steps.
+
+1. In the list of Telegraf configurations, double-click your
+    Telegraf configuration, and then click **Download Config**.
+2. Open the downloaded Telegraf configuration file and replace the `[[inputs.processes]]` plugin with one of the following Windows plugins, depending on your Windows configuration:
+
+   - [`[[inputs.win_perf_counters]]`](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/win_perf_counters)
+   -  [`[[inputs.win_services]]`](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/win_services)
+
+3. Save the file and place it in a directory that **telegraf.exe** can access.
+
+
+## Start Telegraf
+
+Requests to the [InfluxDB v2 API](/influxdb/v2.2/reference/api/) must include an API token.
+A token identifies specific permissions to the InfluxDB instance.
+
+### Configure your token as an environment variable
+
+1. Find your API token. _For information about viewing tokens, see [View tokens](/influxdb/v2.2/security/tokens/view-tokens/)._
+
+2. To configure your API token as the `INFLUX_TOKEN` environment variable, run the command appropriate for your operating system and command-line tool:
+
+{{< tabs-wrapper >}}
+{{% tabs %}}
+[macOS or Linux](#)
+[Windows](#)
+{{% /tabs %}}
+
+{{% tab-content %}}
+```sh
+export INFLUX_TOKEN=YourAuthenticationToken
+```
+{{% /tab-content %}}
+
+{{% tab-content %}}
+
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[PowerShell](#)
+[CMD](#)
+{{% /code-tabs %}}
+
+{{% code-tab-content %}}
+```sh
+$env:INFLUX_TOKEN = "YourAuthenticationToken"
+```
+{{% /code-tab-content %}}
+
+{{% code-tab-content %}}
+```sh
+set INFLUX_TOKEN=YourAuthenticationToken
+# Make sure to include a space character at the end of this command.
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+{{% /tab-content %}}
+{{< /tabs-wrapper >}}
+
+### Start the Telegraf service
+
+Start the Telegraf service using the `-config` flag to specify the location of the generated Telegraf configuration file.
+
+- For Windows, the location is always a local file path.
+- For Linux and macOS, the location can be a local file path or URL.
+
+Telegraf starts using the Telegraf configuration pulled from InfluxDB API.
+
+{{% note %}}
+InfluxDB host URLs and ports differ between InfluxDB OSS and InfluxDB Cloud.
+For the exact command, see the Telegraf configuration **Setup Instructions** in the InfluxDB UI.
+{{% /note %}}
+
+```sh
+telegraf -config http://localhost:8086/api/v2/telegrafs/0xoX00oOx0xoX00o
+```
+
+## Manage Telegraf configurations
+
+For more information about managing Telegraf configurations in InfluxDB, see
+[Telegraf configurations](/influxdb/v2.2/telegraf-configs/).
diff --git a/content/influxdb/v2.2/write-data/no-code/use-telegraf/dual-write.md b/content/influxdb/v2.2/write-data/no-code/use-telegraf/dual-write.md
new file mode 100644
index 000000000..bba769975
--- /dev/null
+++ b/content/influxdb/v2.2/write-data/no-code/use-telegraf/dual-write.md
@@ -0,0 +1,60 @@
+---
+title: Dual write to InfluxDB OSS and InfluxDB Cloud
+description: Write data to both OSS and Cloud simultaneously.
+menu:
+  influxdb_2_2:
+    parent: Telegraf (agent)
+weight: 201
+---
+
+If you want to back up your data in two places, or if you're migrating from OSS to Cloud, you may want to set up dual write.
+
+Use Telegraf to write to both InfluxDB OSS and InfluxDB Cloud simultaneously.
+
+The sample configuration below uses:
+  - The [InfluxDB v2 output plugin](https://github.com/influxdata/telegraf/tree/master/plugins/outputs/influxdb_v2) twice: first pointing to the OSS instance and then to the cloud instance.
+  - Two different tokens, one for OSS and one for Cloud. You'll need to configure both tokens as environment variables (see [Configure your token as an environment variable](/influxdb/v2.2/write-data/no-code/use-telegraf/auto-config/#configure-your-token-as-an-environment-variable).
+
+Use the configuration below to write your data to both OSS and Cloud instances simultaneously.
+
+## Sample configuration
+
+```
+[[inputs.cpu]]
+[[inputs.mem]]
+
+## Any other inputs, processors, aggregators that you want to include in your configuration.
+
+# Send data to InfluxDB OSS v2
+[[outputs.influxdb_v2]]
+  ## The URLs of the InfluxDB instance.
+  ##
+  ## Multiple URLs can be specified for a single cluster, only ONE of the
+  ## urls will be written to each interval.
+  ## urls exp: http://127.0.0.1:9999
+  urls = ["http://localhost:8086"]
+
+  ## OSS token for authentication.
+  token = "$INFLUX_TOKEN_OSS"
+
+  ## Organization is the name of the organization you want to write to. It must already exist.
+  organization = "influxdata"
+
+  ## Destination bucket to write to.
+  bucket = "telegraf"
+
+# Send data to InfluxDB Cloud - AWS West cloud instance
+ [[outputs.influxdb_v2]]
+  ## The URLs of the InfluxDB Cloud instance.
+
+  urls = ["https://us-west-2-1.aws.cloud2.influxdata.com"]
+
+  ## Cloud token for authentication.
+  token = "$INFLUX_TOKEN_CLOUD"
+
+  ## Organization is the name of the organization you want to write to. It must already exist.
+  organization = "example@domain.com"
+
+  ## Destination bucket to write into.
+  bucket = "telegraf"
+  ```
diff --git a/content/influxdb/v2.2/write-data/no-code/use-telegraf/manual-config.md b/content/influxdb/v2.2/write-data/no-code/use-telegraf/manual-config.md
new file mode 100644
index 000000000..72d3ffe19
--- /dev/null
+++ b/content/influxdb/v2.2/write-data/no-code/use-telegraf/manual-config.md
@@ -0,0 +1,161 @@
+---
+title: Manually configure Telegraf
+seotitle: Manually configure Telegraf for InfluxDB v2.2
+description: >
+  Update existing or create new Telegraf configurations to use the `influxdb_v2`
+  output plugin to write to InfluxDB v2.2.
+  Start Telegraf using the custom configuration.
+aliases:
+  - /influxdb/v2.2/collect-data/use-telegraf/manual-config
+  - /influxdb/v2.2/write-data/use-telegraf/manual-config
+menu:
+  influxdb_2_2:
+    parent: Telegraf (agent)
+weight: 202
+influxdb/v2.2/tags: [manually, plugin, mqtt]
+related:
+  - /{{< latest "telegraf" >}}/plugins//
+  - /influxdb/v2.2/telegraf-configs/create/
+  - /influxdb/v2.2/telegraf-configs/update/
+---
+
+Use the Telegraf `influxdb_v2` output plugin to collect and write metrics into an InfluxDB v2.2 bucket.
+This article describes how to enable the `influxdb_v2` output plugin in new and existing Telegraf configurations,
+then start Telegraf using the custom configuration file.
+
+{{< youtube qFS2zANwIrc >}}
+
+{{% note %}}
+_View the [requirements](/influxdb/v2.2/write-data/no-code/use-telegraf#requirements)
+for using Telegraf with InfluxDB v2.2._
+{{% /note %}}
+
+## Configure Telegraf input and output plugins
+Configure Telegraf input and output plugins in the Telegraf configuration file (typically named `telegraf.conf`).
+Input plugins collect metrics.
+Output plugins define destinations where metrics are sent.
+
+_See [Telegraf plugins](/{{< latest "telegraf" >}}/plugins//) for a complete list of available plugins._
+
+### Manually add Telegraf plugins
+
+To manually add any of the available [Telegraf plugins](/{{< latest "telegraf" >}}/plugins//), follow the steps below.
+
+1. Find the plugin you want to enable from the complete list of available [Telegraf plugins](/{{< latest "telegraf" >}}/plugins//).
+2. Click **View** to the right of the plugin name to open the plugin page on GitHub. For example, view the MQTT plugin GitHub page [here](https://github.com/influxdata/telegraf/blob/release-1.14/plugins/inputs/mqtt_consumer/README.md).
+3. Copy and paste the example configuration into your Telegraf configuration file (typically named `telegraf.conf`).
+
+### Enable and configure the InfluxDB v2 output plugin
+
+To send data to an InfluxDB v2.2 instance, enable in the
+[`influxdb_v2` output plugin](https://github.com/influxdata/telegraf/blob/master/plugins/outputs/influxdb_v2/README.md)
+in the `telegraf.conf`.
+
+To find an example InfluxDB v2 output plugin configuration in the UI:
+
+1. In the navigation menu on the left, select **Data (Load Data)** > **Telegraf**.
+
+    {{< nav-icon "load data" >}}
+
+2. Click **InfluxDB Output Plugin**.
+3. Click **Copy to Clipboard** to copy the example configuration or **Download Config** to save a copy.
+4. Paste the example configuration into your `telegraf.conf` and specify the options below.
+
+The InfluxDB output plugin configuration contains the following options:
+
+##### urls
+An array of URLs for your InfluxDB v2.2 instances.
+See [InfluxDB URLs](/influxdb/v2.2/reference/urls/) for information about which URLs to use.
+**{{< cloud-name "short">}} requires HTTPS**.
+
+##### token
+Your InfluxDB v2.2 authorization token.
+For information about viewing tokens, see [View tokens](/influxdb/v2.2/security/tokens/view-tokens/).
+
+{{% note %}}
+###### Avoid storing tokens in `telegraf.conf`
+We recommend storing your tokens by setting the `INFLUX_TOKEN` environment variable and including the environment variable in your configuration file.
+
+{{< tabs-wrapper >}}
+{{% tabs %}}
+[macOS or Linux](#)
+[Windows](#)
+{{% /tabs %}}
+
+{{% tab-content %}}
+```sh
+export INFLUX_TOKEN=YourAuthenticationToken
+```
+{{% /tab-content %}}
+
+{{% tab-content %}}
+
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[PowerShell](#)
+[CMD](#)
+{{% /code-tabs %}}
+
+{{% code-tab-content %}}
+```sh
+$env:INFLUX_TOKEN = "YourAuthenticationToken"
+```
+{{% /code-tab-content %}}
+
+{{% code-tab-content %}}
+```sh
+set INFLUX_TOKEN=YourAuthenticationToken
+# Make sure to include a space character at the end of this command.
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+{{% /tab-content %}}
+{{< /tabs-wrapper >}}
+
+_See the [example `telegraf.conf` below](#example-influxdb_v2-configuration)._
+{{% /note %}}
+
+##### organization
+The name of the organization that owns the target bucket.
+
+##### bucket
+The name of the bucket to write data to.
+
+#### Example influxdb_v2 configuration
+The example below illustrates an `influxdb_v2` configuration.
+
+```toml
+# ...
+
+[[outputs.influxdb_v2]]
+  urls = ["http://localhost:8086"]
+  token = "$INFLUX_TOKEN"
+  organization = "example-org"
+  bucket = "example-bucket"
+
+# ...
+```
+
+{{% note %}}
+##### Write to InfluxDB v1.x and v2.2
+If a Telegraf agent is already writing to an InfluxDB v1.x database,
+enabling the InfluxDB v2 output plugin will write data to both v1.x and v2.2 instances.
+{{% /note %}}
+
+## Add a custom Telegraf configuration to InfluxDB
+To add a custom or manually configured Telegraf configuration to your collection
+of Telegraf configurations in InfluxDB, use the [`influx telegrafs create`](/influxdb/v2.2/reference/cli/influx/telegrafs/create/)
+or [`influx telegrafs update`](/influxdb/v2.2/reference/cli/influx/telegrafs/update/) commands.
+For more information, see:
+
+- [Create a Telegraf configuration](/influxdb/v2.2/telegraf-configs/create/#use-the-influx-cli)
+- [Update a Telegraf configuration](/influxdb/v2.2/telegraf-configs/update/#use-the-influx-cli)
+
+## Start Telegraf
+
+Start the Telegraf service using the `--config` flag to specify the location of your `telegraf.conf`.
+
+```sh
+telegraf --config /path/to/custom/telegraf.conf
+```
diff --git a/content/influxdb/v2.2/write-data/no-code/use-telegraf/use-telegraf-plugins/_index.md b/content/influxdb/v2.2/write-data/no-code/use-telegraf/use-telegraf-plugins/_index.md
new file mode 100644
index 000000000..86f0f1307
--- /dev/null
+++ b/content/influxdb/v2.2/write-data/no-code/use-telegraf/use-telegraf-plugins/_index.md
@@ -0,0 +1,16 @@
+---
+title: Use Telegraf plugins
+description: >
+  Use Telegraf plugins to capture and write metrics to InfluxDB.
+aliases:
+  - /influxdb/v2.2/write-data/use-telegraf/use-telegraf-plugins/
+menu:
+  influxdb_2_2:
+    name: Use Telegraf plugins
+    parent: Telegraf (agent)
+weight: 202
+---
+
+The following articles guide you through step-by-step Telegraf configuration examples:
+
+{{< children >}}
diff --git a/content/influxdb/v2.2/write-data/no-code/use-telegraf/use-telegraf-plugins/use-http-plugin.md b/content/influxdb/v2.2/write-data/no-code/use-telegraf/use-telegraf-plugins/use-http-plugin.md
new file mode 100644
index 000000000..8263e11da
--- /dev/null
+++ b/content/influxdb/v2.2/write-data/no-code/use-telegraf/use-telegraf-plugins/use-http-plugin.md
@@ -0,0 +1,119 @@
+---
+title: Use the HTTP input plugin
+seotitle: Use the Telegraf HTTP input plugin to write data to InfluxDB
+list_title: HTTP input plugin
+description: >
+  Write Citi Bike data to your InfluxDB instance with the HTTP plugin.
+aliases:
+  - /influxdb/v2.2/write-data/use-telegraf/use-telegraf-plugins/use-http-plugin/
+menu:
+  influxdb_2_2:
+    name: HTTP input plugin
+    parent: Use Telegraf plugins
+weight: 202
+---
+
+This example walks through using the Telegraf HTTP input plugin to collect live metrics on Citi Bike stations in New York City. Live station data is available in JSON format from [NYC OpenData](https://data.cityofnewyork.us/NYC-BigApps/Citi-Bike-Live-Station-Feed-JSON-/p94q-8hxh).
+
+Configure [`influxdb` output plugin](/{{< latest "telegraf" >}}/plugins//#influxdb) to write metrics to your InfluxDB {{< current-version >}} instance.
+
+## Configure the HTTP Input plugin in your Telegraf configuration file
+
+To retrieve data from the Citi Bike URL endpoint, enable the `inputs.http` input plugin in your Telegraf configuration file.
+
+Specify the following options:
+
+### `urls`
+One or more URLs to read metrics from. For this example,  use `https://gbfs.citibikenyc.com/gbfs/en/station_status.json`.
+
+### `data_format`
+The format of the data in the HTTP endpoints that Telegraf will ingest. For this example, use JSON.
+
+
+## Add parser information to your Telegraf configuration
+
+Specify the following JSON-specific options.
+
+### JSON
+
+#### `json_query`
+To parse only the relevant portion of JSON data, set the `json_query` option with a [GJSON](https://github.com/tidwall/gjson) path. The result of the query should contain a JSON object or an array of objects.
+In this case, we don't want to parse the JSON query's `executionTime` at the beginning of the data, so we'll limit this to include only the data in the `stationBeanList` array.
+
+#### `tag_keys`
+List of one or more JSON keys that should be added as tags. For this example, we'll use the tag keys `id`, `stationName`, `city`, and `postalCode`.
+
+#### `json_string_fields`
+List the keys of fields that are in string format so that they can be parsed as strings. Here, the string fields are `statusValue`, `stAddress1`, `stAddress2`, `location`, and `landMark`.
+
+#### `json_time_key`
+Key from the JSON file that creates the timestamp metric. In this case, we want to use the time that station data was last reported, or the `lastCommunicationTime`. If you don't specify a key, the time that Telegraf reads the data becomes the timestamp.
+
+#### `json_time_format`
+The format used to interpret the designated `json_time_key`. This example uses [Go reference time format](https://golang.org/pkg/time/#Time.Format). For example, `Mon Jan 2 15:04:05 MST 2006`.
+
+#### `json_timezone`
+The timezone We'll set this to the Unix TZ value where our bike data takes place, `America/New_York`.
+
+
+#### Example configuration
+
+  ```toml
+  [[inputs.http]]
+  #URL for NYC's Citi Bike station data in JSON format
+  urls = ["https://feeds.citibikenyc.com/stations/stations.json"]
+
+  #Overwrite measurement name from default `http` to `citibikenyc`
+  name_override = "citibikenyc"
+
+  #Exclude url and host items from tags
+  tagexclude = ["url", "host"]
+
+  #Data from HTTP in JSON format
+  data_format = "json"
+
+  #Parse `stationBeanList` array only
+  json_query = "stationBeanList"
+
+  #Set station metadata as tags
+  tag_keys = ["id", "stationName", "city", "postalCode"]
+
+  #Do not include station landmark data as fields
+  fielddrop = ["landMark"]
+
+  #JSON values to set as string fields
+  json_string_fields = ["statusValue", "stAddress1", "stAddress2", "location", "landMark"]
+
+  #Latest station information reported at `lastCommunicationTime`
+  json_time_key = "lastCommunicationTime"
+
+  #Time is reported in Golang "reference time" format
+  json_time_format = "2006-01-02 03:04:05 PM"
+
+  #Time is reported in Eastern Standard Time (EST)
+  json_timezone = "America/New_York"
+  ```
+
+
+
+## Start Telegraf and verify data appears
+
+[Start the Telegraf service](/telegraf/v1.14/introduction/getting-started/).
+
+To test that the data is being sent to InfluxDB, run the following (replacing `telegraf.conf` with the path to your configuration file):
+
+```
+telegraf -config ~/telegraf.conf -test
+```
+
+This command should return line protocol that looks similar to the following:
+
+
+```
+citibikenyc,id=3443,stationName=W\ 52\ St\ &\ 6\ Ave statusKey=1,location="",totalDocks=41,availableDocks=32,latitude=40.76132983124814,longitude=-73.97982001304626,availableBikes=8,stAddress2="",stAddress1="W 52 St & 6 Ave",statusValue="In Service" 1581533519000000000
+citibikenyc,id=367,stationName=E\ 53\ St\ &\ Lexington\ Ave availableBikes=8,stAddress1="E 53 St & Lexington Ave",longitude=-73.97069431,latitude=40.75828065,stAddress2="",statusKey=1,location="",statusValue="In Service",totalDocks=34,availableDocks=24 1581533492000000000
+citibikenyc,id=359,stationName=E\ 47\ St\ &\ Park\ Ave totalDocks=64,availableBikes=15,statusValue="In Service",location="",latitude=40.75510267,availableDocks=49,stAddress1="E 47 St & Park Ave",longitude=-73.97498696,statusKey=1,stAddress2="" 1581533535000000000
+citibikenyc,id=304,stationName=Broadway\ &\ Battery\ Pl statusValue="In Service",availableDocks=11,stAddress1="Broadway & Battery Pl",statusKey=1,stAddress2="",location="",totalDocks=33,latitude=40.70463334,longitude=-74.01361706,availableBikes=22 1581533499000000000
+```
+
+Now, you can explore and query the Citi Bike data in InfluxDB.
diff --git a/content/influxdb/v2.2/write-data/oss-to-cloud.md b/content/influxdb/v2.2/write-data/oss-to-cloud.md
new file mode 100644
index 000000000..1f5c24f86
--- /dev/null
+++ b/content/influxdb/v2.2/write-data/oss-to-cloud.md
@@ -0,0 +1,230 @@
+---
+title: Write data from InfluxDB OSS to InfluxDB Cloud
+description: >
+  Use `to()` or `experimental.to()` to write data from InfluxDB OSS to InfluxDB Cloud.
+  Selectively write data or process data before writing it to InfluxDB Cloud.
+menu:
+  influxdb_2_2:
+    name: Write from OSS to Cloud
+    parent: Write data
+weight: 105
+influxdb/v2.2/tags: [write]
+---
+
+To write data from InfluxDB OSS to InfluxDB Cloud, use the Flux
+[`to()`](/flux/v0.x/stdlib/influxdata/influxdb/to/) or
+[`experimental.to()`](/flux/v0.x/stdlib/experimental/to/) functions.
+Write data once with a single query execution or use [InfluxDB tasks](/influxdb/v2.2/process-data/)
+to [routinely write data to InfluxDB Cloud](#automate-writing-data-from-influxdb-oss-to-influxdb-cloud).
+
+{{% note %}}
+#### Replicate writes to InfluxDB OSS to InfluxDB Cloud
+To replicate all writes to an InfluxDB OSS instance to an InfluxDB Cloud instance,
+use [InfluxDB replication streams](/influxdb/v2.2/write-data/replication/).
+{{% /note %}}
+
+{{% cloud %}}
+#### InfluxDB Cloud rate limits
+Write requests to InfluxDB Cloud are subject to the rate limits associated with your
+[InfluxDB Cloud pricing plan](/influxdb/cloud/account-management/pricing-plans/).
+{{% /cloud %}}
+
+1.  Query data from InfluxDB OSS.
+2.  _(Optional)_ [Filter](/{{% latest "flux" %}}/stdlib/universe/filter/) or process data to write to InfluxDB Cloud.
+3.  Use `to` or `experimental.to` to write data to InfluxDB Cloud.
+    For most use cases, `to()` is the correct function to use, but depending on
+    the structure of the data you're writing, `experimental.to` may be required.
+    
+    **Use the following guidelines**:
+    
+    - **to()**: Use to write data in field keys to the `_field` column and field values to the `_value` column.
+
+    - **experimental.to()**: Use to write data in column names to corresponding field keys and column values to field values.
+
+    _See [input and output examples for `to()` functions](#input-and-output-data-for-to-functions)._
+    
+4.  Provide the following parameters to either function:
+
+    - **bucket**: InfluxDB Cloud bucket to write to
+    - **host**: InfluxDB Cloud region URL
+    - **org**: InfluxDB Cloud organization
+    - **token**: InfluxDB Cloud API Token
+      
+5.  ({{< req "Recommended" >}}) To keep your raw API token out of queries, store
+    your InfluxDB Cloud API token as an [InfluxDB secret](/influxdb/v2.2/security/secrets/)
+    in your InfluxDB OSS instance and use [`secrets.get()`](/flux/v0.x/stdlib/influxdata/influxdb/secrets/get/)
+    to retrieve the secret value as shown in the following example
+    (select the function you're using to see the correct format):
+
+
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[to()](#)
+[experimental.to()](#)
+{{% /code-tabs %}}
+{{% code-tab-content %}}
+```js
+import "influxdata/influxdb/secrets"
+
+cloudToken = secrets.get(key: "INFLUX_CLOUD_API_TOKEN")
+
+from(bucket: "example-oss-bucket")
+    |> range(start: -10m)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> to(
+        bucket: "example-cloud-bucket",
+        host: "https://cloud2.influxdata.com",
+        org: "example-org",
+        token: cloudToken,
+    )
+```
+{{% /code-tab-content %}}
+{{% code-tab-content %}}
+```js
+import "experimental"
+import "influxdata/influxdb/secrets"
+
+cloudToken = secrets.get(key: "INFLUX_CLOUD_API_TOKEN")
+
+from(bucket: "example-oss-bucket")
+    |> range(start: -10m)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> pivot(rowKey: ["_time"], columnKey: ["_field"], valueColumn: "_value")
+    |> experimental.to(
+        bucket: "example-cloud-bucket",
+        host: "https://cloud2.influxdata.com",
+        org: "example-org",
+        token: cloudToken,
+    )
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+## Input and output data for to() functions
+
+{{< tabs-wrapper >}}
+{{% tabs %}}
+[to()](#)
+[experimental.to()](#)
+{{% /tabs %}}
+{{% tab-content %}}
+
+- `to()` requires `_time`, `_measurement`, `_field`, and `_value` columns.
+- `to()` writes all other columns as tags where the column name is the tag key
+  and the column value is the tag value.
+
+#### Input data
+| _time                | _measurement | exampleTag | _field | _value |
+| :------------------- | :----------- | :--------: | :----- | -----: |
+| 2021-01-01T00:00:00Z | example-m    |     A      | temp   |   80.0 |
+| 2021-01-01T00:01:00Z | example-m    |     A      | temp   |   80.3 |
+| 2021-01-01T00:02:00Z | example-m    |     A      | temp   |   81.1 |
+
+| _time                | _measurement | exampleTag | _field | _value |
+| :------------------- | :----------- | :--------: | :----- | -----: |
+| 2021-01-01T00:00:00Z | example-m    |     A      | rpm    |   4023 |
+| 2021-01-01T00:01:00Z | example-m    |     A      | rpm    |   4542 |
+| 2021-01-01T00:02:00Z | example-m    |     A      | rpm    |   4901 |
+
+#### Output line protocol
+```
+example-m,exampleTag=A temp=80.0,rpm=4023i 1609459200000000000
+example-m,exampleTag=A temp=80.3,rpm=4542i 1609459260000000000
+example-m,exampleTag=A temp=81.1,rpm=4901i 1609459320000000000
+```
+{{% /tab-content %}}
+
+{{% tab-content %}}
+- `experimental.to()` requires `_time` and `_measurement` columns.
+- Columns **in** the [group key](/flux/v0.x/get-started/data-model/#grouop-key)
+  (other than `_measurement`) are parsed as tags where the column name is the
+  tag key and the column value is the tag value.
+- Columns **not in** the group key (other than `_time_`) are parsed as fields
+  where the column name is the field key and the column value is the field value.
+
+#### Input data {id="experimental-input-data"}
+{{< flux/group-key "[_measurement, exampleTag]">}}
+| _time                | _measurement | exampleTag | temp |  rpm |
+| :------------------- | :----------- | :--------: | ---: | ---: |
+| 2021-01-01T00:00:00Z | example-m    |     A      | 80.0 | 4023 |
+| 2021-01-01T00:01:00Z | example-m    |     A      | 80.3 | 4542 |
+| 2021-01-01T00:02:00Z | example-m    |     A      | 81.1 | 4901 |
+
+#### Output line protocol {id="experimental-output-line-protocol"}
+```
+example-m,exampleTag=A temp=80.0,rpm=4023i 1609459200000000000
+example-m,exampleTag=A temp=80.3,rpm=4542i 1609459260000000000
+example-m,exampleTag=A temp=81.1,rpm=4901i 1609459320000000000
+```
+{{% /tab-content %}}
+{{< /tabs-wrapper >}}
+
+## Examples
+
+- [Downsample and write data to InfluxDB Cloud](#downsample-and-write-data-to-influxdb-cloud)
+- [Write min, max, and mean values to InfluxDB Cloud](#write-min-max-and-mean-values-to-influxdb-cloud)
+
+#### Downsample and write data to InfluxDB Cloud
+```js
+import "influxdata/influxdb/secrets"
+
+cloudToken = secrets.get(key: "INFLUX_CLOUD_API_TOKEN")
+
+from(bucket: "example-oss-bucket")
+    |> range(start: -10m)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> aggregateWindow(every: 1m, fn: last)
+    |> to(
+        bucket: "example-cloud-bucket",
+        host: "https://cloud2.influxdata.com",
+        org: "example-org",
+        token: cloudToken,
+    )
+```
+
+#### Write min, max, and mean values to InfluxDB Cloud
+```js
+import "influxdata/influxdb/secrets"
+
+cloudToken = secrets.get(key: "INFLUX_CLOUD_API_TOKEN")
+
+data = from(bucket: "example-oss-bucket")
+    |> range(start: -30m)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+
+min = data |> aggregateWindow(every: 10m, fn: min) |> map(fn: (r) => ({ r with _field: "{$r._field}_min" }))
+max = data |> aggregateWindow(every: 10m, fn: max) |> map(fn: (r) => ({ r with _field: "{$r._field}_max" }))
+mean = data |> aggregateWindow(every: 10m, fn: mean) |> map(fn: (r) => ({ r with _field: "{$r._field}_mean" }))
+
+union(tables: [min, max, mean])
+    |> to(
+        bucket: "example-cloud-bucket",
+        host: "https://cloud2.influxdata.com",
+        org: "example-org",
+        token: cloudToken,
+    )
+```
+
+## Automate writing data from InfluxDB OSS to InfluxDB Cloud
+To automatically and routinely write data from InfluxDB OSS to InfluxDB Cloud,
+[create a task](/influxdb/v2.2/process-data/manage-tasks/create-task/) in your
+InfluxDB OSS instance that regularly queries, processes, and writes data to
+InfluxDB Cloud.
+
+```js
+import "influxdata/influxdb/tasks"
+
+option task = {name: "Downsample to InfluxDB Cloud", every: 1h}
+
+from(bucket: "example-oss-bucket")
+    |> range(start: -10m)
+    |> filter(fn: (r) => r._measurement == "example-measurement")
+    |> aggregateWindow(every: 1m, fn: last)
+    |> to(
+        bucket: "example-cloud-bucket",
+        host: "https://cloud2.influxdata.com",
+        org: "example-org",
+        token: cloudToken,
+    )
+```
+
diff --git a/content/influxdb/v2.2/write-data/replication.md b/content/influxdb/v2.2/write-data/replication.md
new file mode 100644
index 000000000..93a1e6f9f
--- /dev/null
+++ b/content/influxdb/v2.2/write-data/replication.md
@@ -0,0 +1,127 @@
+---
+title: Replicate data to a remote InfluxDB instance
+weight: 106
+description: >
+  Use InfluxDB replication streams to replicate all data written to an InfluxDB OSS
+  bucket to InfluxDB Cloud or a remote InfluxDB OSS bucket.
+menu:
+  influxdb_2_2:
+    name: Replicate data
+    parent: Write data
+influxdb/v2.2/tags: [write, replication]
+related:
+  - /influxdb/v2.2/reference/cli/influx/remote
+  - /influxdb/v2.2/reference/cli/influx/replication
+---
+
+Use InfluxDB replication streams to replicate all data written to an InfluxDB OSS
+bucket to an InfluxDB Cloud {{% oss-only %}}or a remote InfluxDB OSS{{% /oss-only %}} bucket.
+
+## Configure a replication stream
+
+1. [Download and install the `influx` CLI](/influxdb/v2.2/tools/influx-cli/).
+2. In your {{% oss-only %}}local{{% /oss-only %}} InfluxDB OSS instance, use the
+    `influx remote create` command to create a remote connection to replicate data to.
+    Provide the following:
+    
+    {{% oss-only %}}
+
+    - Remote connection name
+    - Remote InfluxDB instance URL
+    - Remote InfluxDB API token _(API token must have write access to the target bucket)_
+    - Remote InfluxDB organization ID
+
+    {{% /oss-only %}}
+    {{% cloud-only %}}
+
+    - Remote connection name
+    - [InfluxDB Cloud region URL](/influxdb/cloud/reference/regions/)
+    - InfluxDB Cloud API token _(API token must have write access to the target bucket)_
+    - InfluxDB Cloud organization ID
+
+    {{% /cloud-only %}}
+
+    ```sh
+    influx remote create \
+      --name example-remote-name \
+      --remote-url cloud2.influxdata.com \
+      --remote-api-token mYsuP3r5Ecr37t0k3n \
+      --remote-org-id 00xoXXoxXX00
+    ```
+
+    If you already have remote InfluxDB connections configured, you can use an existing connection.
+    To view existing connections, run `influx remote list`.
+
+2. In your {{% oss-only %}}local{{% /oss-only %}} InfluxDB OSS instance, use the
+    `influx replication create` command to create a replication stream.
+    Provide the following:
+
+    {{% oss-only %}}
+
+    - Replication stream name
+    - Remote connection ID
+    - Local bucket ID to replicate writes from
+    - Remote bucket ID to replicate writes to
+
+    {{% /oss-only %}}
+    {{% cloud-only %}}
+
+    - Replication stream name
+    - Remote connection ID
+    - InfluxDB OSS bucket ID to replicate writes from
+    - InfluxDB Cloud bucket ID to replicate writes to
+
+    {{% /cloud-only %}}
+
+    ```sh
+    influx replication create \
+      --name example-replication-stream-name \
+      --remote-id 00xoXXXo0X0x \
+      --local-bucket Xxxo00Xx000o \
+      --remote-bucket 0xXXx00oooXx
+    ```
+
+Once a replication stream is created, InfluxDB {{% oss-only %}}OSS{{% /oss-only %}}
+will replicate all writes to the specified bucket to the {{% oss-only %}}remote {{% /oss-only %}}
+InfluxDB {{% cloud-only %}}Cloud {{% /cloud-only %}}bucket.
+Use the `influx replication list` command to view information such as the current queue size,
+max queue size, and latest status code.
+
+{{% note %}}
+#### Important things to note
+
+- Only write operations are replicated. Other data operations (like deletes or restores) are not replicated.
+- In InfluxDB OSS, large write request bodies are written entirely.
+  When replicated, write requests are sent to the remote bucket in batches.
+  The maximum batch size is 500 kB (typically between 250 to 500 lines of line protocol).
+  This may result in scenarios where some batches succeed and others fail.
+{{% /note %}}
+
+## Replicate downsampled or processed data
+In some cases, you may not want to write raw, high-precision data to a remote InfluxDB {{% cloud-only %}}Cloud {{% /cloud-only %}} instance. To replicate only downsampled or processed data:
+
+1. Create a bucket in your InfluxDB OSS instance to store downsampled or processed data in.
+2. Create an InfluxDB task that downsamples or processes data and stores it in the new bucket. For example:
+
+    ```js
+    import "influxdata/influxdb/tasks"
+    import "types"
+
+    option task = {name: "Downsample raw data", every: 10m}
+
+    data = () => from(bucket: "example-bucket")
+        |> range(start: tasks.lastSuccess(orTime: -task.every))
+
+    numeric = data()
+        |> filter(fn: (r) => types.isType(v: r._value, type: "float") or types.isType(v: r._value, type: "int") or types.isType(v: r._value, type: "uint"))
+        |> aggregateWindow(every: -task.every, fn: mean)
+
+    nonNumeric = data()
+        |> filter(fn: (r) => types.isType(v: r._value, type: "string") or types.isType(v: r._value, type: "bool"))
+        |> aggregateWindow(every: -task.every, fn: last)
+
+    union(tables: [numeric, nonNumeric])
+        |> to(bucket: "example-downsampled-bucket"])
+    ```
+
+3. [Create a replication stream](#configure-a-replication-stream) to replicate data from the downsampled bucket to the remote InfluxDB {{% cloud-only %}}Cloud {{% /cloud-only %}}instance.
diff --git a/content/influxdb/v2.2/write-data/troubleshoot.md b/content/influxdb/v2.2/write-data/troubleshoot.md
new file mode 100644
index 000000000..03e80ff45
--- /dev/null
+++ b/content/influxdb/v2.2/write-data/troubleshoot.md
@@ -0,0 +1,84 @@
+---
+title: Troubleshoot issues writing data
+seotitle: Troubleshoot issues writing data to InfluxDB
+weight: 106
+description: >
+  Troubleshoot issues writing data. Find response codes for failed writes. Discover how writes fail, from exceeding rate or payload limits, to syntax errors and schema conflicts.
+menu:
+  influxdb_2_2:
+    name: Troubleshoot issues
+    parent: Write data
+influxdb/v2.2/tags: [write, line protocol, errors]
+related:
+  - /influxdb/v2.2/api/#tag/Write, InfluxDB API /write endpoint
+  - /influxdb/v2.2/reference/internals
+  - /influxdb/v2.2/reference/cli/influx/write
+---
+Learn how to handle and recover from errors when writing to InfluxDB.
+
+- [Discover common failure scenarios](#discover-common-failure-scenarios)
+- [Review HTTP status codes](#review-http-status-codes)
+- [Troubleshoot failures](#troubleshoot-failures)
+
+## Discover common failure scenarios
+
+Write requests made to InfluxDB may fail for a number of reasons.
+Common failure scenarios that return an HTTP `4xx` or `5xx` error status code include the following:
+
+- API token was invalid. . See how to [manage API tokens](/influxdb/v2.0/security/tokens/).
+- Payload size was too large.
+- Client or server reached a timeout threshold.
+- Data was not formatted correctly.
+
+To find the causes of a specific error, [review HTTP status codes](#review-http-status-codes).
+
+### Troubleshoot partial writes
+
+Writes may fail partially or completely even though InfluxDB returns an HTTP `2xx` status code for a valid request.
+For example, a partial write may occur when InfluxDB writes all points that conform to the bucket schema, but rejects points that have the wrong data type in a field.
+To resolve partial writes and rejected points, see [troubleshoot failures](#troubleshoot-failures).
+
+## Review HTTP status codes
+
+InfluxDB uses conventional HTTP status codes to indicate the success or failure of a request.
+Write requests return the following status codes:
+
+- `204` **Success**: InfluxDB validated the request data format and accepted the data for writing to the bucket.
+  {{% note %}}
+  `204` doesn't indicate a successful write operation since writes are asynchronous.
+  If some of your data did not write to the bucket, see how to [troubleshoot rejected points](#troubleshoot-rejected-points).
+  {{% /note %}}
+
+- `400` **Bad request**: The [line protocol](/influxdb/v2.2/reference/syntax/line-protocol/) data in the request was malformed.
+        The response body contains the first malformed line in the data. All request data was rejected and not written.
+- `401` **Unauthorized**: May indicate one of the following:
+  - [`Authorization: Token` header](/influxdb/v2.2/api-guide/api_intro/#authentication) is missing or malformed.
+  - [API token](/influxdb/v2.2/api-guide/api_intro/#authentication) value is missing from the header.
+  - API token does not have sufficient permissions to write to the organization and the bucket. For more information about token types and permissions, see [Manage API tokens](/influxdb/v2.2/security/tokens/)
+- `404` **Not found**: A requested resource (e.g. an organization or bucket) was not found. The response body contains the requested resource type, e.g. "organization", and resource name.
+- `413` **Request entity too large**: All request data was rejected and not written. InfluxDB OSS only returns this error if the [Go (golang) `ioutil.ReadAll()`](https://pkg.go.dev/io/ioutil#ReadAll) function raises an error.
+- `500` **Internal server error**: Default HTTP status for an error.
+- `503` **Service unavailable**: Server is temporarily unavailable to accept writes. The `Retry-After` header describes when to try the write again.
+
+The `message` property of the response body may contain additional details about the error.
+
+## Troubleshoot failures
+
+If you notice data is missing in your bucket, do the following:
+
+- Check the `message` property in the response body for details about the error
+- Verify all lines contain valid syntax, e.g. [line protocol](/influxdb/v2.2/reference/syntax/line-protocol/) or [CSV](/influxdb/v2.2/reference/syntax/annotated-csv/)
+- Verify the data types match other data points with the same series.
+  For example, did you attempt to write `string` data to an `int` field?
+- Verify the timestamps match the [precision parameter](/influxdb/v2.2/write-data/#timestamp-precision).
+- Minimize payload size and network errors by [optimizing writes](/influxdb/v2.2/write-data/best-practices/optimize-writes/)
+
+### Troubleshoot rejected points
+
+InfluxDB may reject points even if the HTTP request returns "Success".
+If some of your data did not write to the bucket, check for [field type](/influxdb/v2.2/reference/key-concepts/data-elements/#field-value) differences between the missing data point and other points that have the same [series](/influxdb/v2.2/reference/key-concepts/data-elements/#series).
+For example, did you attempt to write `string` data to an `int` field?
+
+InfluxDB rejects points for the following reasons:
+- The **batch** contains another point with the same series, but one of the fields has a different value type.
+- The **bucket** contains another point with the same series, but one of the fields has a different value type.
diff --git a/content/kapacitor/v1.4/about_the_project/contributing.md b/content/kapacitor/v1.4/about_the_project/contributing.md
index fcae0beac..60b747e67 100644
--- a/content/kapacitor/v1.4/about_the_project/contributing.md
+++ b/content/kapacitor/v1.4/about_the_project/contributing.md
@@ -6,5 +6,6 @@ menu:
     name: Contributing
     weight: 20
     parent: About the project
-    url: https://github.com/influxdata/kapacitor/blob/master/CONTRIBUTING.md
+    params:
+      url: https://github.com/influxdata/kapacitor/blob/master/CONTRIBUTING.md
 ---
diff --git a/content/kapacitor/v1.4/about_the_project/custom_alert.md b/content/kapacitor/v1.4/about_the_project/custom_alert.md
index 18caaaa71..22a1ef4b9 100644
--- a/content/kapacitor/v1.4/about_the_project/custom_alert.md
+++ b/content/kapacitor/v1.4/about_the_project/custom_alert.md
@@ -7,7 +7,8 @@ menu:
     name: Contributing event handler integrations
     weight: 30
     parent: About the project
-    url: https://github.com/influxdata/kapacitor/blob/master/alert/HANDLERS.md
+    params:
+      url: https://github.com/influxdata/kapacitor/blob/master/alert/HANDLERS.md
 ---
 
 This page explains how you can create event handlers for alerting within Kapacitor.
diff --git a/content/kapacitor/v1.4/about_the_project/license.md b/content/kapacitor/v1.4/about_the_project/license.md
index 54294e948..67c3d662a 100644
--- a/content/kapacitor/v1.4/about_the_project/license.md
+++ b/content/kapacitor/v1.4/about_the_project/license.md
@@ -6,5 +6,6 @@ menu:
     name: Open source license
     weight: 50
     parent: About the project
-    url: https://github.com/influxdata/kapacitor/blob/master/LICENSE
+    params:
+      url: https://github.com/influxdata/kapacitor/blob/master/LICENSE
 ---
diff --git a/content/kapacitor/v1.5/about_the_project/contributing.md b/content/kapacitor/v1.5/about_the_project/contributing.md
index 183d0a581..8075e4d46 100644
--- a/content/kapacitor/v1.5/about_the_project/contributing.md
+++ b/content/kapacitor/v1.5/about_the_project/contributing.md
@@ -6,5 +6,6 @@ menu:
     name: Contributing
     weight: 10
     parent: About the project
-    url: https://github.com/influxdata/kapacitor/blob/master/CONTRIBUTING.md
+    params:
+      url: https://github.com/influxdata/kapacitor/blob/master/CONTRIBUTING.md
 ---
diff --git a/content/kapacitor/v1.5/about_the_project/license.md b/content/kapacitor/v1.5/about_the_project/license.md
index 4117ee6d4..dad4366e4 100644
--- a/content/kapacitor/v1.5/about_the_project/license.md
+++ b/content/kapacitor/v1.5/about_the_project/license.md
@@ -6,5 +6,6 @@ menu:
     name: License
     weight: 40
     parent: About the project
-    url: https://github.com/influxdata/kapacitor/blob/master/LICENSE
+    params:
+      url: https://github.com/influxdata/kapacitor/blob/master/LICENSE
 ---
diff --git a/content/kapacitor/v1.5/working/custom_alert.md b/content/kapacitor/v1.5/working/custom_alert.md
index f70fc2767..a1176902f 100644
--- a/content/kapacitor/v1.5/working/custom_alert.md
+++ b/content/kapacitor/v1.5/working/custom_alert.md
@@ -9,5 +9,6 @@ menu:
     identifier: custom_alert
     weight: 4
     parent: work-w-kapacitor
-    url: https://github.com/influxdata/kapacitor/blob/master/alert/HANDLERS.md
+    params:
+      url: https://github.com/influxdata/kapacitor/blob/master/alert/HANDLERS.md
 ---
diff --git a/content/kapacitor/v1.6/about_the_project/contributing.md b/content/kapacitor/v1.6/about_the_project/contributing.md
index 602a7872d..4e76c24a3 100644
--- a/content/kapacitor/v1.6/about_the_project/contributing.md
+++ b/content/kapacitor/v1.6/about_the_project/contributing.md
@@ -6,5 +6,6 @@ menu:
     name: Contributing
     weight: 10
     parent: About the project
-    url: https://github.com/influxdata/kapacitor/blob/master/CONTRIBUTING.md
+    params:
+      url: https://github.com/influxdata/kapacitor/blob/master/CONTRIBUTING.md
 ---
diff --git a/content/kapacitor/v1.6/about_the_project/license.md b/content/kapacitor/v1.6/about_the_project/license.md
index 73ca67468..830ed1aa8 100644
--- a/content/kapacitor/v1.6/about_the_project/license.md
+++ b/content/kapacitor/v1.6/about_the_project/license.md
@@ -6,5 +6,6 @@ menu:
     name: License
     weight: 40
     parent: About the project
-    url: https://github.com/influxdata/kapacitor/blob/master/LICENSE
+    params:
+      url: https://github.com/influxdata/kapacitor/blob/master/LICENSE
 ---
diff --git a/content/kapacitor/v1.6/about_the_project/releasenotes-changelog.md b/content/kapacitor/v1.6/about_the_project/releasenotes-changelog.md
index c3e9bf0e2..9ea33d60d 100644
--- a/content/kapacitor/v1.6/about_the_project/releasenotes-changelog.md
+++ b/content/kapacitor/v1.6/about_the_project/releasenotes-changelog.md
@@ -7,6 +7,16 @@ menu:
     name: Release notes
 ---
 
+## v1.6.4 [2022-03-15]
+
+### Features
+
+- Add `SASL` support to `Kafka` alerts.
+
+### Bug fixes
+
+- Fully deprecate DES based ciphers, RC4 based ciphers and TLS 1.1 and 1.0 ciphers. 
+- Adjust `Flux` injected dependencies so that large data sets can be downloaded without issue.
 
 ## v1.6.3 [2022-01-25]
 
@@ -34,7 +44,6 @@ is 1000.
 
 - Add the `template-id` property to the `GET /kapacitor/v1/tasks` request response. Adding this property helps to identify tasks that were created from a [template](/kapacitor/v1.6/working/template_tasks/).
 - For alert templates, row templates, and details templates, add support for third-party services that reject standard `json` (terminated by a new line character) by compacting `json` in templates. To do this, replace `{{ json . }}` with `{{ jsonCompact . }}` in your templates. (This change also compacts Big Panda alert details to avoid Panda service error.)
-- Previously, Kapacitor used a remote `influxdb` bucket (or 1.x database) to store Flux task run logs, and you had to manually create the database or bucket to store Flux logs. Now, Kapacitor automatically creates an InfluxDB 1.x database or InfluxDB 2.x bucket for Flux task logs (by default, kapacitor_fluxtask_logs). For more information, see how to [use Flux tasks with Kapacitor](/kapacitor/v1.6/working/flux/).
 
 ### Bug fixes
 
diff --git a/content/kapacitor/v1.6/administration/configuration.md b/content/kapacitor/v1.6/administration/configuration.md
index 205ef3cff..7584025e4 100644
--- a/content/kapacitor/v1.6/administration/configuration.md
+++ b/content/kapacitor/v1.6/administration/configuration.md
@@ -29,11 +29,11 @@ Any property key can be located by following its path in the configuration file
 Values for configuration keys are declared in the configuration file.
 
 #### Kapacitor configuration file location
-Kapacitor looks for configuration files at specific locations depends on your operating system:
+Kapacitor looks for configuration files at specific locations, depending on your operating system:
 
-**Linux**: `/etc/kapacitor/kapacitor.conf`
-**macOS**: `/usr/local/etc/kapacitor.conf`
-**Windows**: _same directory as the `kapacitord.exe`._
+- **Linux**: `/etc/kapacitor/kapacitor.conf`
+- **macOS**: `/usr/local/etc/kapacitor.conf`
+- **Windows**: _same directory as `kapacitord.exe`_
 
 Define a custom location for your `kapacitor.conf` at startup with the `-config` flag.
 The path to the configuration file can also be declared using the environment variable `KAPACITOR_CONFIG_PATH`.
@@ -263,8 +263,6 @@ Use the query `SHOW DIAGNOSTICS` to see the version of Go used to build Kapacito
 Minimum version of the TLS protocol that will be negotiated.
 Valid values include: 
 
-- `tls1.0`
-- `tls1.1`
 - `tls1.2`
 - `tls1.3` _(default)_
 
@@ -273,8 +271,6 @@ Valid values include:
 Maximum version of the TLS protocol that will be negotiated. 
 Valid values include: 
 
-- `tls1.0`
-- `tls1.1`
 - `tls1.2`
 - `tls1.3` _(default)_
 
diff --git a/content/kapacitor/v1.6/administration/security.md b/content/kapacitor/v1.6/administration/security.md
index 0991f8a78..2c6474689 100644
--- a/content/kapacitor/v1.6/administration/security.md
+++ b/content/kapacitor/v1.6/administration/security.md
@@ -385,7 +385,7 @@ use the `-blacklist-cidrs` flag.
 Pass a comma-separated list of CIDRs to deny for most HTTP GET/POST operations:
 
 ```sh
-kapacitor -blacklist 10.0.0.0/8,0.0.0.0/32
+kapacitord -blacklist-cidrs 10.0.0.0/8,0.0.0.0/32
 ```
 
 ### Disable specific alert handlers
@@ -394,7 +394,7 @@ Use the `-disable-handlers` flag to disable a set of alert handlers.
 Pass a comma-separated list of [handlers](/kapacitor/v1.6/event_handlers/):
 
 ```sh
-kapacitor -disable-handlers exec,httppost
+kapacitord -disable-handlers exec,httppost
 ```
 
 
diff --git a/content/kapacitor/v1.6/event_handlers/email.md b/content/kapacitor/v1.6/event_handlers/email.md
index c3c3a631a..c269c347e 100644
--- a/content/kapacitor/v1.6/event_handlers/email.md
+++ b/content/kapacitor/v1.6/event_handlers/email.md
@@ -75,8 +75,9 @@ The following Email event handler options can be set in a
 `.email()` in a TICKscript.
 
 | Name | Type            | Description              |
-| ---- | ----            | -----------              |
+| ---- | --------------- | ------------------------ |
 | to   | list of strings | List of email addresses. |
+| toTemplate(s)  | string template| Derived email addresses. |
 
 ### Example: handler file
 ```yaml
@@ -187,3 +188,38 @@ Add the handler:
 ```bash
 kapacitor define-topic-handler email_cpu_handler.yaml
 ```
+
+### Send email alerts using the toTemplate option
+
+You can use `toTemplate` to derive email addresses directly from data instead of hardcoding them individually. 
+In the example below, we are using both the `to` option and `toTemplates` option in order to derive email addresses from a dataset and send email alerts directly to recipients. 
+Like the `to` option, the `toTemplates` option can be used more than once in a TICKscript. 
+You can combine the `to` and `toTemplates` options or use them individually depending on your use case.
+
+```js
+stream
+	|from()
+		.measurement('cpu')
+		.where(lambda: "host" == 'serverA')
+		.groupBy('host')
+	|window()
+		.period(10s)
+		.every(10s)
+	|count('value')
+	|default()
+		.field('extraemail','bob@example.com')
+		.tag('tagemail','bob2@example.com')
+	|alert()
+		.id('kapacitor.{{ .Name }}.{{ index .Tags "host" }}')
+		.details('''
+<b>{{.Message}}</b>
+Value: {{ index .Fields "count" }}
+<a href="http://graphs.example.com/host/{{index .Tags "host"}}">Details</a>
+''')
+		.info(lambda: "count" > 6.0)
+		.warn(lambda: "count" > 7.0)
+		.crit(lambda: "count" > 8.0)
+		.email()
+			.to('user1@example.com', 'user2@example.com')
+			.toTemplates('{{ index .Fields "extraemail" }}')
+```
\ No newline at end of file
diff --git a/content/kapacitor/v1.6/event_handlers/kafka.md b/content/kapacitor/v1.6/event_handlers/kafka.md
index 5ada377d2..9b4ccc103 100644
--- a/content/kapacitor/v1.6/event_handlers/kafka.md
+++ b/content/kapacitor/v1.6/event_handlers/kafka.md
@@ -32,6 +32,21 @@ Below is an example configuration:
   ssl-cert = ""
   ssl-key = ""
   insecure-skip-verify = false
+  # Optional SASL configuration
+  sasl-username = "xxxxx"
+  sasl-password = "xxxxxxxx"
+  sasl-mechanism = ""
+  sasl-version = ""
+  # Use if sasl-mechanism is GSSAPI. GSSAPI is for organizations using Kerberos.
+  sasl-gssapi-service-name = ""
+  sasl-gssapi-auth-type = "KRB5_USER_AUTH"
+  sasl-gssapi-disable-pafxfast = false
+  sasl-gssapi-kerberos-config-path = "/"
+  sasl-gssapi-key-tab-path = ""
+  sasl-gssapi-realm = "realm"
+  # Use if sasl-mechanism is `OAUTHBEARER` (experimental).
+  sasl-access-token = ""
+
 ```
 
 {{% note %}}
@@ -77,6 +92,41 @@ Path to certificate private key file.
 Use SSL but skip chain and host verification.
 _(Required if using a self-signed certificate.)_
 
+### (Optional) SASL configuration
+
+#### sasl-username
+Username to use for SASL authentication.
+
+#### sasl-password
+Password to use for SASL authentication.
+
+#### sasl-mechanism
+SASL mechanism type. Options include `GSSAPI`, `OAUTHBEARER`, `PLAIN`.
+
+#### sasl-version
+SASL protocol version.
+
+#### sasl-gssapi-service-name
+The service name for GSSAPI.
+
+#### sasl-gssapi-auth-type
+The authorization type for GSSAPI.
+
+####  sasl-gssapi-disable-pafxfast
+Set to `true` or `false`.
+
+####  sasl-gssapi-kerberos-config-path
+Path to the Kerberos config file.
+
+#### sasl-gssapi-key-tab-path
+Path to the Kerberos key tab.
+
+####  sasl-gssapi-realm
+Default Kerberos realm.
+
+#### sasl-access-token
+Used if the SASL mechanism is `OAUTHBEARER` (experimental).
+
 ## Options
 The following Kafka event handler options can be set in a
 [handler file](/kapacitor/v1.6/event_handlers/#create-a-topic-handler-with-a-handler-file) or when using
@@ -221,3 +271,29 @@ Add the handler:
 ```bash
 kapacitor define-topic-handler kafka_cpu_handler.yaml
 ```
+
+### Using SASL with Kapacitor
+
+To use an authentication method other than SSL, configure Kapacitor to use SASL. 
+An example would be using Kapacitor to authenticate directly against Kafka with a username/password. 
+Multiple configuration options are available, but the most common usage is username and password as shown in the following example:
+
+```toml
+[[kafka]]
+  enabled = true
+  id = "infra-monitoring"
+  brokers = ["123.45.67.89:9092", "123.45.67.90:9092"]
+  timeout = "10s"
+  batch-size = 100
+  batch-timeout = "1s"
+  use-ssl = true
+  ssl-ca = "/etc/ssl/certs/ca.crt"
+  ssl-cert = "/etc/ssl/certs/cert.crt"
+  ssl-key = "/etc/ssl/certs/cert-key.key"
+  insecure-skip-verify = true
+  sasl-username = "kafka"
+  sasl-password = "kafkapassword"
+```
+
+
+
diff --git a/content/kapacitor/v1.6/working/custom_alert.md b/content/kapacitor/v1.6/working/custom_alert.md
index 261e3c64c..be6e1d8f8 100644
--- a/content/kapacitor/v1.6/working/custom_alert.md
+++ b/content/kapacitor/v1.6/working/custom_alert.md
@@ -9,5 +9,6 @@ menu:
     identifier: custom_alert
     weight: 4
     parent: work-w-kapacitor
-    url: https://github.com/influxdata/kapacitor/blob/master/alert/HANDLERS.md
+    params:
+      url: https://github.com/influxdata/kapacitor/blob/master/alert/HANDLERS.md
 ---
diff --git a/content/platform/monitoring/influxdata-platform/_index.md b/content/platform/monitoring/influxdata-platform/_index.md
index 607b6d240..0c9db8b79 100644
--- a/content/platform/monitoring/influxdata-platform/_index.md
+++ b/content/platform/monitoring/influxdata-platform/_index.md
@@ -27,8 +27,8 @@ Use it as much and as long as you like within the plan’s rate-limits.
 Limits are designed to let you monitor 5-10 sensors, stacks or servers comfortably.
 Monitoring a single InfluxDB OSS instance or even a modest InfluxDB Enterprise
 cluster should easily fit within the free plan limits.
-If you exceed the plan limits because of high resolution data or longer data retention,
-upgrade to the [pay-as-you-go plan](/influxdb/cloud/account-management/pricing-plans/#usage-based-plan).
+If you exceed the plan [limits](/influxdb/cloud/account-management/limits/) because of high resolution data or longer data retention,
+upgrade to the [Usage-Based Plan](/influxdb/cloud/account-management/pricing-plans/#usage-based-plan).
 
 Start monitoring your InfluxDB instance by signing up for an [InfluxDB Cloud account](https://cloud2.influxdata.com/signup).
 
diff --git a/content/platform/monitoring/influxdata-platform/tools/measurements-internal.md b/content/platform/monitoring/influxdata-platform/tools/measurements-internal.md
index 940f29830..63b781da4 100644
--- a/content/platform/monitoring/influxdata-platform/tools/measurements-internal.md
+++ b/content/platform/monitoring/influxdata-platform/tools/measurements-internal.md
@@ -278,6 +278,12 @@ The number of remote node requests for information about the fields and associat
 #### iteratorCostReq
 The number of internal requests for iterator cost.
 
+#### openConnections
+
+Tracks the number of open connections
+being handled by the data node
+(including counting logical connections multiplexed onto a single yamux connection).
+
 #### removeShardReq
 The number of internal requests to delete a shard from this data node.
 Exclusively incremented by use of the `influxd-ctl remove shard` command.
diff --git a/content/resources/videos/_index.md b/content/resources/videos/_index.md
index c291a2720..1210eec36 100644
--- a/content/resources/videos/_index.md
+++ b/content/resources/videos/_index.md
@@ -16,5 +16,7 @@ menu:
 #### Season 2
 {{< resources/video-cards series="Meet the Developers S2" >}}
 
+#### Season 3
+{{< resources/video-cards series="Meet the Developers S3" >}}
 
 For additional product and tutorial videos, please visit our [YouTube channel](https://www.youtube.com/channel/UCnrgOD6G0y0_rcubQuICpTQ).
diff --git a/content/resources/videos/configure-telegraf-plugin.md b/content/resources/videos/configure-telegraf-plugin.md
new file mode 100644
index 000000000..5db7f798a
--- /dev/null
+++ b/content/resources/videos/configure-telegraf-plugin.md
@@ -0,0 +1,18 @@
+---
+title: Configuring a Telegraf Plugin
+description: >
+  Mya Longmire and Alan Pope discuss the structure of the Telegraf configuration file and show you how to configure a Telegraf plugin.
+menu:
+  resources:
+    parent: Videos
+weight: 134
+youtubeID: a0js7wiQEJ4
+date: 2022-03-01
+series: [Meet the Developers S3]
+metadata: [Meet the Developer Series]
+related: 
+  - /{{< latest "telegraf" >}}/introduction/getting-started/
+  - /{{< latest "telegraf" >}}/plugins/
+---
+
+{{< resources/video-content >}}
\ No newline at end of file
diff --git a/content/resources/videos/influxdb-edge.md b/content/resources/videos/influxdb-edge.md
new file mode 100644
index 000000000..172ccb575
--- /dev/null
+++ b/content/resources/videos/influxdb-edge.md
@@ -0,0 +1,18 @@
+---
+title: InfluxDB at the Edge
+description: >
+  Scott Anderson and Alan Pope discuss how InfluxDB helps efficiently collect, store and analyze vast amounts of data commonly associated with IoT and edge devices.
+menu:
+  resources:
+    parent: Videos
+weight: 132
+youtubeID: EbTGnu7xqnU
+date: 2022-03-01
+series: [Meet the Developers S3]
+metadata: [Meet the Developer Series]
+related: 
+  - /{{< latest "influxdb" >}}/get-started/
+
+---
+
+{{< resources/video-content >}}
\ No newline at end of file
diff --git a/content/resources/videos/influxql-oss-and-cloud.md b/content/resources/videos/influxql-oss-and-cloud.md
new file mode 100644
index 000000000..b6135ab01
--- /dev/null
+++ b/content/resources/videos/influxql-oss-and-cloud.md
@@ -0,0 +1,18 @@
+---
+title: InfluxQL in OSS and InfluxDB Cloud 
+description: >
+  InfluxQL is used to query time series data in both 1.x and 2.x versions of InfluxDB. 
+  Scott Anderson and Alan Pope discuss some key differences to be aware of when using InfluxQL with 2.x.
+menu:
+  resources:
+    parent: Videos
+weight: 131
+youtubeID: fSDMc1ESXf4
+date: 2022-03-01
+series: [Meet the Developers S3]
+metadata: [Meet the Developer Series]
+related: 
+  - /influxdb/v1.8/query_language/
+---
+
+{{< resources/video-content >}}
\ No newline at end of file
diff --git a/content/resources/videos/joins-in-flux.md b/content/resources/videos/joins-in-flux.md
new file mode 100644
index 000000000..bf2510403
--- /dev/null
+++ b/content/resources/videos/joins-in-flux.md
@@ -0,0 +1,20 @@
+---
+title: Joins in Flux
+description: >
+  Scott Anderson discusses the two primary use cases for joining data and how joins work in InfluxDB.
+menu:
+  resources:
+    parent: Videos
+weight: 137
+youtubeID: g-HY1Q11iGg
+date: 2022-03-01
+series: [Meet the Developers S3]
+metadata: [Meet the Developer Series]
+related: 
+  - /{{< latest "flux" >}}/stdlib/universe/join/
+  - /{{< latest "influxdb" >}}/query-data/flux/join/
+ 
+---
+
+{{< resources/video-content >}}
+
diff --git a/content/resources/videos/pivots-in-flux.md b/content/resources/videos/pivots-in-flux.md
new file mode 100644
index 000000000..854940504
--- /dev/null
+++ b/content/resources/videos/pivots-in-flux.md
@@ -0,0 +1,18 @@
+---
+title: Pivots in Flux
+description: >
+  Scott Anderson explains how to use the Flux `pivot()` function to pivot unique values in a column into individual columns on each row.
+menu:
+  resources:
+    parent: Videos
+weight: 138
+youtubeID: LuPcShbE0J4
+date: 2022-03-01
+series: [Meet the Developers S3]
+metadata: [Meet the Developer Series]
+related: 
+ - /{{< latest "flux" >}}/stdlib/universe/pivot/
+
+---
+
+{{< resources/video-content >}}
\ No newline at end of file
diff --git a/content/resources/videos/telegraf-agent-config-best-practice.md b/content/resources/videos/telegraf-agent-config-best-practice.md
new file mode 100644
index 000000000..0cd25dba9
--- /dev/null
+++ b/content/resources/videos/telegraf-agent-config-best-practice.md
@@ -0,0 +1,19 @@
+---
+title: Telegraf Agent Configuration Best Practices
+description: >
+  Alan Pope and Josh Powers discuss key configuration options to optimize data ingest for Telegraf plugins.
+menu:
+  resources:
+    parent: Videos
+weight: 136
+youtubeID: txUcAxMDBlQ
+date: 2022-03-01
+series: [Meet the Developers S3]
+metadata: [Meet the Developer Series]
+related: 
+  - /{{< latest "telegraf" >}}/introduction/getting-started/
+  - /{{< latest "telegraf" >}}/administration/configuration/
+---
+
+{{< resources/video-content >}}
+
diff --git a/content/resources/videos/telegraf-data-ingest-plugin.md b/content/resources/videos/telegraf-data-ingest-plugin.md
new file mode 100644
index 000000000..f60851741
--- /dev/null
+++ b/content/resources/videos/telegraf-data-ingest-plugin.md
@@ -0,0 +1,19 @@
+---
+title: Telegraf Data Ingest with Plugins
+description: >
+  Telegraf has hundreds of plugins that can collect data from a wide variety of sources, ranging from IoT devices to databases to endpoints.
+  Mya Longmire and Alan Pope talk about data ingest using three of Telegraf's most widely used plugins.
+menu:
+  resources:
+    parent: Videos
+weight: 135
+youtubeID: 6XJdZ_kdx14
+date: 2022-03-01
+series: [Meet the Developers S3]
+metadata: [Meet the Developer Series]
+related: 
+  - /{{< latest "telegraf" >}}/plugins/
+---
+
+{{< resources/video-content >}}
+
diff --git a/content/resources/videos/telegraf-plugin-system-overview.md b/content/resources/videos/telegraf-plugin-system-overview.md
new file mode 100644
index 000000000..fb68a44d5
--- /dev/null
+++ b/content/resources/videos/telegraf-plugin-system-overview.md
@@ -0,0 +1,22 @@
+---
+title: Telegraf Plugin System Overview
+description: >
+  Telegraf has hundreds of plugins to chose from, as well as configuration options.
+  Alan Pope and Josh Powers discuss how do you decide which ones to use.      
+menu:
+  resources:
+    parent: Videos
+weight: 133
+youtubeID: k5m7SHgXRYQ
+date: 2022-03-01
+series: [Meet the Developers S3]
+metadata: [Meet the Developer Series]
+related: 
+  - /{{< latest "telegraf" >}}/introduction/getting-started/
+  - /{{< latest "telegraf" >}}/plugins/
+---
+
+{{< resources/video-content >}}
+
+
+
diff --git a/content/telegraf/v1.10/about_the_project/release-notes-changelog.md b/content/telegraf/v1.10/about_the_project/release-notes-changelog.md
index 4372844ad..a3e4d091a 100644
--- a/content/telegraf/v1.10/about_the_project/release-notes-changelog.md
+++ b/content/telegraf/v1.10/about_the_project/release-notes-changelog.md
@@ -452,14 +452,14 @@ menu:
 
 ### New input data formats (parsers)
 
-- [csv](/telegraf/v1.8/data_formats/input/csv) - Contributed by @maxunt
-- [grok](/telegraf/v1.8/data_formats/input/grok/) - Contributed by @maxunt
-- [logfmt](/telegraf/v1.8/data_formats/input/logfmt/) - Contributed by @Ayrdrie & @maxunt
-- [wavefront](/telegraf/v1.8/data_formats/input/wavefront/) - Contributed by @puckpuck
+- [csv](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/csv) - Contributed by @maxunt
+- [grok](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/grok/) - Contributed by @maxunt
+- [logfmt](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/logfmt/) - Contributed by @Ayrdrie & @maxunt
+- [wavefront](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/wavefront/) - Contributed by @puckpuck
 
 ### New output data formats (serializers)
 
-- [splunkmetric](/telegraf/v1.8/data_formats/output/splunkmetric/) - Contributed by @ronnocol
+- [splunkmetric](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/output/splunkmetric/) - Contributed by @ronnocol
 
 ### Features
 
@@ -1240,7 +1240,7 @@ These plugins will replace [udp_listener](https://github.com/influxdata/telegraf
 - Add [DMCache input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/dmcache).
 - Add support for precision in [HTTP Listener input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/http_listener).
 - Add `message_len_max` option to the [Kafka consumer input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/kafka_consumer).
-- Add [collectd parser](/telegraf/v1.3/concepts/data_formats_input/#collectd).
+- Add [collectd parser](https://archive.docs.influxdata.com/telegraf/v1.3/concepts/data_formats_input/#collectd).
 - Simplify plugin testing without outputs.
 - Check signature in the [GitHub webhook input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/webhooks/github).
 - Add [papertrail](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/webhooks/papertrail) support to webhooks.
diff --git a/content/telegraf/v1.10/data_formats/output/graphite.md b/content/telegraf/v1.10/data_formats/output/graphite.md
index 8356882be..3afec27cb 100644
--- a/content/telegraf/v1.10/data_formats/output/graphite.md
+++ b/content/telegraf/v1.10/data_formats/output/graphite.md
@@ -10,7 +10,7 @@ menu:
 
 The Graphite data format is serialized from Telegraf metrics using either the
 template pattern or tag support method.  You can select between the two
-methods using the [`graphite_tag_support`](#graphite-tag-support) option.  When set, the tag support method is used,
+methods using the [`graphite_tag_support`](#graphite_tag_support) option.  When set, the tag support method is used,
 otherwise the [template pattern][templates]) option is used.
 
 ## Configuration
diff --git a/content/telegraf/v1.10/plugins/inputs.md b/content/telegraf/v1.10/plugins/inputs.md
index c60e9ddd0..5de209e1b 100644
--- a/content/telegraf/v1.10/plugins/inputs.md
+++ b/content/telegraf/v1.10/plugins/inputs.md
@@ -1063,7 +1063,7 @@ The [HTTP Listener input plugin](https://github.com/influxdata/telegraf/blob/rel
 Line Protocol input data format](/telegraf/v1.10/data_formats/input/influx) ONLY (other [Telegraf input data formats](/telegraf/v1.10/data_formats/input/) are not supported).
 This plugin allows Telegraf to serve as a proxy or router for the `/write` endpoint of the InfluxDB HTTP API.
 
-> DEPRECATED as of version 1.9. Use either [HTTP Listener v2](#http-listener-v2) or the [InfluxDB Listener](#influxdb-v1-x)
+> DEPRECATED as of version 1.9. Use either [HTTP Listener v2](#http-listener-v2) or the [InfluxDB Listener](#influxdb-v1x)
 
 
 ### Jolokia
diff --git a/content/telegraf/v1.11/about_the_project/release-notes-changelog.md b/content/telegraf/v1.11/about_the_project/release-notes-changelog.md
index b6dc0f5b8..ec753e3ed 100644
--- a/content/telegraf/v1.11/about_the_project/release-notes-changelog.md
+++ b/content/telegraf/v1.11/about_the_project/release-notes-changelog.md
@@ -693,14 +693,14 @@ menu:
 
 ### New input data formats (parsers)
 
-- [csv](/telegraf/v1.8/data_formats/input/csv) - Contributed by @maxunt
-- [grok](/telegraf/v1.8/data_formats/input/grok/) - Contributed by @maxunt
-- [logfmt](/telegraf/v1.8/data_formats/input/logfmt/) - Contributed by @Ayrdrie & @maxunt
-- [wavefront](/telegraf/v1.8/data_formats/input/wavefront/) - Contributed by @puckpuck
+- [csv](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/csv) - Contributed by @maxunt
+- [grok](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/grok/) - Contributed by @maxunt
+- [logfmt](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/logfmt/) - Contributed by @Ayrdrie & @maxunt
+- [wavefront](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/wavefront/) - Contributed by @puckpuck
 
 ### New output data formats (serializers)
 
-- [splunkmetric](/telegraf/v1.8/data_formats/output/splunkmetric/) - Contributed by @ronnocol
+- [splunkmetric](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/output/splunkmetric/) - Contributed by @ronnocol
 
 ### Features
 
@@ -1481,7 +1481,7 @@ These plugins will replace [udp_listener](https://github.com/influxdata/telegraf
 - Add [DMCache input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/dmcache).
 - Add support for precision in [HTTP Listener input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/http_listener).
 - Add `message_len_max` option to the [Kafka consumer input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/kafka_consumer).
-- Add [collectd parser](/telegraf/v1.3/concepts/data_formats_input/#collectd).
+- Add [collectd parser](https://archive.docs.influxdata.com/telegraf/v1.3/concepts/data_formats_input/#collectd).
 - Simplify plugin testing without outputs.
 - Check signature in the [GitHub webhook input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/webhooks/github).
 - Add [papertrail](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/webhooks/papertrail) support to webhooks.
diff --git a/content/telegraf/v1.11/data_formats/output/graphite.md b/content/telegraf/v1.11/data_formats/output/graphite.md
index 253a6d68f..79f34247d 100644
--- a/content/telegraf/v1.11/data_formats/output/graphite.md
+++ b/content/telegraf/v1.11/data_formats/output/graphite.md
@@ -10,7 +10,7 @@ menu:
 
 The Graphite data format is serialized from Telegraf metrics using either the
 template pattern or tag support method.  You can select between the two
-methods using the [`graphite_tag_support`](#graphite-tag-support) option.  When set, the tag support method is used,
+methods using the [`graphite_tag_support`](#graphite_tag_support) option.  When set, the tag support method is used,
 otherwise the [template pattern][templates]) option is used.
 
 ## Configuration
diff --git a/content/telegraf/v1.12/about_the_project/release-notes-changelog.md b/content/telegraf/v1.12/about_the_project/release-notes-changelog.md
index 0f55dbc82..bf4eee201 100644
--- a/content/telegraf/v1.12/about_the_project/release-notes-changelog.md
+++ b/content/telegraf/v1.12/about_the_project/release-notes-changelog.md
@@ -859,14 +859,14 @@ menu:
 
 ### New input data formats (parsers)
 
-- [csv](/telegraf/v1.8/data_formats/input/csv) - Contributed by @maxunt
-- [grok](/telegraf/v1.8/data_formats/input/grok/) - Contributed by @maxunt
-- [logfmt](/telegraf/v1.8/data_formats/input/logfmt/) - Contributed by @Ayrdrie & @maxunt
-- [wavefront](/telegraf/v1.8/data_formats/input/wavefront/) - Contributed by @puckpuck
+- [csv](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/csv) - Contributed by @maxunt
+- [grok](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/grok/) - Contributed by @maxunt
+- [logfmt](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/logfmt/) - Contributed by @Ayrdrie & @maxunt
+- [wavefront](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/wavefront/) - Contributed by @puckpuck
 
 ### New output data formats (serializers)
 
-- [splunkmetric](/telegraf/v1.8/data_formats/output/splunkmetric/) - Contributed by @ronnocol
+- [splunkmetric](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/output/splunkmetric/) - Contributed by @ronnocol
 
 ### Features
 
@@ -1647,7 +1647,7 @@ These plugins will replace [udp_listener](https://github.com/influxdata/telegraf
 - Add [DMCache input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/dmcache).
 - Add support for precision in [HTTP Listener input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/http_listener).
 - Add `message_len_max` option to the [Kafka consumer input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/kafka_consumer).
-- Add [collectd parser](/telegraf/v1.3/concepts/data_formats_input/#collectd).
+- Add [collectd parser](https://archive.docs.influxdata.com/telegraf/v1.3/concepts/data_formats_input/#collectd).
 - Simplify plugin testing without outputs.
 - Check signature in the [GitHub webhook input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/webhooks/github).
 - Add [papertrail](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/webhooks/papertrail) support to webhooks.
diff --git a/content/telegraf/v1.12/data_formats/output/graphite.md b/content/telegraf/v1.12/data_formats/output/graphite.md
index 1ddc1c4ec..035395bab 100644
--- a/content/telegraf/v1.12/data_formats/output/graphite.md
+++ b/content/telegraf/v1.12/data_formats/output/graphite.md
@@ -10,7 +10,7 @@ menu:
 
 The Graphite data format is serialized from Telegraf metrics using either the
 template pattern or tag support method.  You can select between the two
-methods using the [`graphite_tag_support`](#graphite-tag-support) option.  When set, the tag support method is used,
+methods using the [`graphite_tag_support`](#graphite_tag_support) option.  When set, the tag support method is used,
 otherwise the [template pattern][templates]) option is used.
 
 ## Configuration
diff --git a/content/telegraf/v1.13/about_the_project/release-notes-changelog.md b/content/telegraf/v1.13/about_the_project/release-notes-changelog.md
index 55b88f1b9..c4107a89e 100644
--- a/content/telegraf/v1.13/about_the_project/release-notes-changelog.md
+++ b/content/telegraf/v1.13/about_the_project/release-notes-changelog.md
@@ -1007,14 +1007,14 @@ for details about the mapping.
 
 ### New input data formats (parsers)
 
-- [csv](/telegraf/v1.8/data_formats/input/csv) - Contributed by @maxunt
-- [grok](/telegraf/v1.8/data_formats/input/grok/) - Contributed by @maxunt
-- [logfmt](/telegraf/v1.8/data_formats/input/logfmt/) - Contributed by @Ayrdrie & @maxunt
-- [wavefront](/telegraf/v1.8/data_formats/input/wavefront/) - Contributed by @puckpuck
+- [csv](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/csv) - Contributed by @maxunt
+- [grok](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/grok/) - Contributed by @maxunt
+- [logfmt](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/logfmt/) - Contributed by @Ayrdrie & @maxunt
+- [wavefront](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/wavefront/) - Contributed by @puckpuck
 
 ### New output data formats (serializers)
 
-- [splunkmetric](/telegraf/v1.8/data_formats/output/splunkmetric/) - Contributed by @ronnocol
+- [splunkmetric](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/output/splunkmetric/) - Contributed by @ronnocol
 
 ### Features
 
@@ -1795,7 +1795,7 @@ These plugins will replace [udp_listener](https://github.com/influxdata/telegraf
 - Add [DMCache input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/dmcache).
 - Add support for precision in [HTTP Listener input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/http_listener).
 - Add `message_len_max` option to the [Kafka consumer input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/kafka_consumer).
-- Add [collectd parser](/telegraf/v1.3/concepts/data_formats_input/#collectd).
+- Add [collectd parser](https://archive.docs.influxdata.com/telegraf/v1.3/concepts/data_formats_input/#collectd).
 - Simplify plugin testing without outputs.
 - Check signature in the [GitHub webhook input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/webhooks/github).
 - Add [papertrail](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/webhooks/papertrail) support to webhooks.
diff --git a/content/telegraf/v1.13/data_formats/output/graphite.md b/content/telegraf/v1.13/data_formats/output/graphite.md
index 380071008..c9184a3ce 100644
--- a/content/telegraf/v1.13/data_formats/output/graphite.md
+++ b/content/telegraf/v1.13/data_formats/output/graphite.md
@@ -10,7 +10,7 @@ menu:
 
 The Graphite data format is serialized from Telegraf metrics using either the
 template pattern or tag support method.  You can select between the two
-methods using the [`graphite_tag_support`](#graphite-tag-support) option.  When set, the tag support method is used,
+methods using the [`graphite_tag_support`](#graphite_tag_support) option.  When set, the tag support method is used,
 otherwise the [template pattern][templates]) option is used.
 
 ## Configuration
diff --git a/content/telegraf/v1.14/about_the_project/release-notes-changelog.md b/content/telegraf/v1.14/about_the_project/release-notes-changelog.md
index cb0587143..4a06b16da 100644
--- a/content/telegraf/v1.14/about_the_project/release-notes-changelog.md
+++ b/content/telegraf/v1.14/about_the_project/release-notes-changelog.md
@@ -1169,14 +1169,14 @@ for details about the mapping.
 
 ### New input data formats (parsers)
 
-- [csv](/telegraf/v1.8/data_formats/input/csv) - Contributed by @maxunt
-- [grok](/telegraf/v1.8/data_formats/input/grok/) - Contributed by @maxunt
-- [logfmt](/telegraf/v1.8/data_formats/input/logfmt/) - Contributed by @Ayrdrie & @maxunt
-- [wavefront](/telegraf/v1.8/data_formats/input/wavefront/) - Contributed by @puckpuck
+- [csv](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/csv) - Contributed by @maxunt
+- [grok](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/grok/) - Contributed by @maxunt
+- [logfmt](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/logfmt/) - Contributed by @Ayrdrie & @maxunt
+- [wavefront](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/wavefront/) - Contributed by @puckpuck
 
 ### New output data formats (serializers)
 
-- [splunkmetric](/telegraf/v1.8/data_formats/output/splunkmetric/) - Contributed by @ronnocol
+- [splunkmetric](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/output/splunkmetric/) - Contributed by @ronnocol
 
 ### Features
 
@@ -1957,7 +1957,7 @@ These plugins will replace [udp_listener](https://github.com/influxdata/telegraf
 - Add [DMCache input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/dmcache).
 - Add support for precision in [HTTP Listener input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/http_listener).
 - Add `message_len_max` option to the [Kafka consumer input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/kafka_consumer).
-- Add [collectd parser](/telegraf/v1.3/concepts/data_formats_input/#collectd).
+- Add [collectd parser](https://archive.docs.influxdata.com/telegraf/v1.3/concepts/data_formats_input/#collectd).
 - Simplify plugin testing without outputs.
 - Check signature in the [GitHub webhook input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/webhooks/github).
 - Add [papertrail](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/webhooks/papertrail) support to webhooks.
diff --git a/content/telegraf/v1.14/data_formats/output/graphite.md b/content/telegraf/v1.14/data_formats/output/graphite.md
index e675b9845..6bcdd4f7c 100644
--- a/content/telegraf/v1.14/data_formats/output/graphite.md
+++ b/content/telegraf/v1.14/data_formats/output/graphite.md
@@ -10,7 +10,7 @@ menu:
 
 The Graphite data format is serialized from Telegraf metrics using either the
 template pattern or tag support method.  You can select between the two
-methods using the [`graphite_tag_support`](#graphite-tag-support) option.  When set, the tag support method is used,
+methods using the [`graphite_tag_support`](#graphite_tag_support) option.  When set, the tag support method is used,
 otherwise the [template pattern][templates]) option is used.
 
 ## Configuration
diff --git a/content/telegraf/v1.15/about_the_project/release-notes-changelog.md b/content/telegraf/v1.15/about_the_project/release-notes-changelog.md
index 945605308..4c6d7c288 100644
--- a/content/telegraf/v1.15/about_the_project/release-notes-changelog.md
+++ b/content/telegraf/v1.15/about_the_project/release-notes-changelog.md
@@ -1362,14 +1362,14 @@ for details about the mapping.
 
 ### New input data formats (parsers)
 
-- [csv](/telegraf/v1.8/data_formats/input/csv) - Contributed by @maxunt
-- [grok](/telegraf/v1.8/data_formats/input/grok/) - Contributed by @maxunt
-- [logfmt](/telegraf/v1.8/data_formats/input/logfmt/) - Contributed by @Ayrdrie & @maxunt
-- [wavefront](/telegraf/v1.8/data_formats/input/wavefront/) - Contributed by @puckpuck
+- [csv](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/csv) - Contributed by @maxunt
+- [grok](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/grok/) - Contributed by @maxunt
+- [logfmt](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/logfmt/) - Contributed by @Ayrdrie & @maxunt
+- [wavefront](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/wavefront/) - Contributed by @puckpuck
 
 ### New output data formats (serializers)
 
-- [splunkmetric](/telegraf/v1.8/data_formats/output/splunkmetric/) - Contributed by @ronnocol
+- [splunkmetric](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/output/splunkmetric/) - Contributed by @ronnocol
 
 ### Features
 
@@ -2150,7 +2150,7 @@ These plugins will replace [udp_listener](https://github.com/influxdata/telegraf
 - Add [DMCache input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/dmcache).
 - Add support for precision in [HTTP Listener input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/http_listener).
 - Add `message_len_max` option to the [Kafka consumer input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/kafka_consumer).
-- Add [collectd parser](/telegraf/v1.3/concepts/data_formats_input/#collectd).
+- Add [collectd parser](https://archive.docs.influxdata.com/telegraf/v1.3/concepts/data_formats_input/#collectd).
 - Simplify plugin testing without outputs.
 - Check signature in the [GitHub webhook input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/webhooks/github).
 - Add [papertrail](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/webhooks/papertrail) support to webhooks.
diff --git a/content/telegraf/v1.15/data_formats/output/graphite.md b/content/telegraf/v1.15/data_formats/output/graphite.md
index 9d1d7ba21..3144d8bf6 100644
--- a/content/telegraf/v1.15/data_formats/output/graphite.md
+++ b/content/telegraf/v1.15/data_formats/output/graphite.md
@@ -10,7 +10,7 @@ menu:
 
 The Graphite data format is serialized from Telegraf metrics using either the
 template pattern or tag support method.  You can select between the two
-methods using the [`graphite_tag_support`](#graphite-tag-support) option.  When set, the tag support method is used,
+methods using the [`graphite_tag_support`](#graphite_tag_support) option.  When set, the tag support method is used,
 otherwise the [template pattern][templates]) option is used.
 
 ## Configuration
diff --git a/content/telegraf/v1.15/guides/using_http.md b/content/telegraf/v1.15/guides/using_http.md
index a3f538579..efc1d3a2d 100644
--- a/content/telegraf/v1.15/guides/using_http.md
+++ b/content/telegraf/v1.15/guides/using_http.md
@@ -10,7 +10,7 @@ menu:
 
 This example walks through using the Telegraf HTTP input plugin to collect live metrics on Citi Bike stations in New York City. Live station data is available in JSON format from [NYC OpenData](https://data.cityofnewyork.us/NYC-BigApps/Citi-Bike-Live-Station-Feed-JSON-/p94q-8hxh).
 
-For the following example to work, configure [`influxdb` output plugin](/telegraf/v1.15/plugins/#influxdb_v2). This plugin is what allows Telegraf to write the metrics to your InfluxDB.
+For the following example to work, configure [`influxdb` output plugin](/telegraf/v1.15/plugins/#output-influxdb_v2). This plugin is what allows Telegraf to write the metrics to your InfluxDB.
 
 ## Configure the HTTP Input plugin in your Telegraf configuration file
 
diff --git a/content/telegraf/v1.15/introduction/installation.md b/content/telegraf/v1.15/introduction/installation.md
index 265cb40b3..f6b8fc50d 100644
--- a/content/telegraf/v1.15/introduction/installation.md
+++ b/content/telegraf/v1.15/introduction/installation.md
@@ -337,7 +337,7 @@ Compare the output from this command to the hash listed on the downloads page to
 ### Configure an input plugin
 
 The Telegraf ZIP archive contains a default configuration file (`telegraf.conf`).
-In this file, the input plugin for capturing basic [Windows system metrics](/telegraf/v1.15/plugins/#win_perf_counters) is already activated.
+In this file, the input plugin for capturing basic [Windows system metrics](/telegraf/v1.15/plugins/#input-win_perf_counters) is already activated.
 With this plugin, Telegraf monitors the following defined Windows Operating System objects:
 
 - Processor
@@ -357,8 +357,8 @@ Before you start the Telegraf agent, configure an output plugin to send data to
 Choose the appropriate plugin based on the version of InfluxDB you are using.
 
 The `telegraf.conf` file included in the ZIP archive contains sections for configuring
-both the [InfluxDB v1](/telegraf/v1.15/plugins/#influxdb) and
-[InfluxDB v2](/telegraf/v1.15/plugins/#influxdb_v2) output plugins.
+both the [InfluxDB v1](/telegraf/v1.15/plugins/#output-influxdb) and
+[InfluxDB v2](/telegraf/v1.15/plugins/#output-influxdb_v2) output plugins.
 
 #### Writing data to InfluxDB 1.x
 
diff --git a/content/telegraf/v1.16/about_the_project/release-notes-changelog.md b/content/telegraf/v1.16/about_the_project/release-notes-changelog.md
index d80a21027..296d851d3 100644
--- a/content/telegraf/v1.16/about_the_project/release-notes-changelog.md
+++ b/content/telegraf/v1.16/about_the_project/release-notes-changelog.md
@@ -1484,14 +1484,14 @@ for details about the mapping.
 
 ### New input data formats (parsers)
 
-- [csv](/telegraf/v1.8/data_formats/input/csv) - Contributed by @maxunt
-- [grok](/telegraf/v1.8/data_formats/input/grok/) - Contributed by @maxunt
-- [logfmt](/telegraf/v1.8/data_formats/input/logfmt/) - Contributed by @Ayrdrie & @maxunt
-- [wavefront](/telegraf/v1.8/data_formats/input/wavefront/) - Contributed by @puckpuck
+- [csv](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/csv) - Contributed by @maxunt
+- [grok](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/grok/) - Contributed by @maxunt
+- [logfmt](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/logfmt/) - Contributed by @Ayrdrie & @maxunt
+- [wavefront](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/wavefront/) - Contributed by @puckpuck
 
 ### New output data formats (serializers)
 
-- [splunkmetric](/telegraf/v1.8/data_formats/output/splunkmetric/) - Contributed by @ronnocol
+- [splunkmetric](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/output/splunkmetric/) - Contributed by @ronnocol
 
 ### Features
 
@@ -2272,7 +2272,7 @@ These plugins will replace [udp_listener](https://github.com/influxdata/telegraf
 - Add [DMCache input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/dmcache).
 - Add support for precision in [HTTP Listener input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/http_listener).
 - Add `message_len_max` option to the [Kafka consumer input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/kafka_consumer).
-- Add [collectd parser](/telegraf/v1.3/concepts/data_formats_input/#collectd).
+- Add [collectd parser](https://archive.docs.influxdata.com/telegraf/v1.3/concepts/data_formats_input/#collectd).
 - Simplify plugin testing without outputs.
 - Check signature in the [GitHub webhook input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/webhooks/github).
 - Add [papertrail](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/webhooks/papertrail) support to webhooks.
diff --git a/content/telegraf/v1.16/data_formats/output/graphite.md b/content/telegraf/v1.16/data_formats/output/graphite.md
index 607336d21..e25e33641 100644
--- a/content/telegraf/v1.16/data_formats/output/graphite.md
+++ b/content/telegraf/v1.16/data_formats/output/graphite.md
@@ -10,7 +10,7 @@ menu:
 
 The Graphite data format is serialized from Telegraf metrics using either the
 template pattern or tag support method.  You can select between the two
-methods using the [`graphite_tag_support`](#graphite-tag-support) option.  When set, the tag support method is used,
+methods using the [`graphite_tag_support`](#graphite_tag_support) option.  When set, the tag support method is used,
 otherwise the [template pattern][templates]) option is used.
 
 ## Configuration
diff --git a/content/telegraf/v1.16/guides/using_http.md b/content/telegraf/v1.16/guides/using_http.md
index f651bfe16..25e23ff4a 100644
--- a/content/telegraf/v1.16/guides/using_http.md
+++ b/content/telegraf/v1.16/guides/using_http.md
@@ -10,7 +10,7 @@ menu:
 
 This example walks through using the Telegraf HTTP input plugin to collect live metrics on Citi Bike stations in New York City. Live station data is available in JSON format from [NYC OpenData](https://data.cityofnewyork.us/NYC-BigApps/Citi-Bike-Live-Station-Feed-JSON-/p94q-8hxh).
 
-For the following example to work, configure [`influxdb` output plugin](/telegraf/v1.15/plugins/#influxdb). This plugin is what allows Telegraf to write the metrics to your InfluxDB.
+For the following example to work, configure [`influxdb` output plugin](/telegraf/v1.15/plugins/#output-influxdb). This plugin is what allows Telegraf to write the metrics to your InfluxDB.
 
 ## Configure the HTTP Input plugin in your Telegraf configuration file
 
diff --git a/content/telegraf/v1.16/introduction/installation.md b/content/telegraf/v1.16/introduction/installation.md
index cc4632150..1c08163dd 100644
--- a/content/telegraf/v1.16/introduction/installation.md
+++ b/content/telegraf/v1.16/introduction/installation.md
@@ -337,7 +337,7 @@ Compare the output from this command to the hash listed on the downloads page to
 ### Configure an input plugin
 
 The Telegraf ZIP archive contains a default configuration file (`telegraf.conf`).
-In this file, the input plugin for capturing basic [Windows system metrics](/telegraf/v1.15/plugins/#win_perf_counters) is already activated.
+In this file, the input plugin for capturing basic [Windows system metrics](/telegraf/v1.15/plugins/#input-win_perf_counters) is already activated.
 With this plugin, Telegraf monitors the following defined Windows Operating System objects:
 
 - Processor
@@ -357,8 +357,8 @@ Before you start the Telegraf agent, configure an output plugin to send data to
 Choose the appropriate plugin based on the version of InfluxDB you are using.
 
 The `telegraf.conf` file included in the ZIP archive contains sections for configuring
-both the [InfluxDB v1](/telegraf/v1.15/plugins/#influxdb) and
-[InfluxDB v2](/telegraf/v1.15/plugins/#influxdb_v2) output plugins.
+both the [InfluxDB v1](/telegraf/v1.15/plugins/#output-influxdb) and
+[InfluxDB v2](/telegraf/v1.15/plugins/#output-influxdb_v2) output plugins.
 
 #### Writing data to InfluxDB 1.x
 
diff --git a/content/telegraf/v1.17/about_the_project/release-notes-changelog.md b/content/telegraf/v1.17/about_the_project/release-notes-changelog.md
index d40249110..5599f2d72 100644
--- a/content/telegraf/v1.17/about_the_project/release-notes-changelog.md
+++ b/content/telegraf/v1.17/about_the_project/release-notes-changelog.md
@@ -1629,14 +1629,14 @@ for details about the mapping.
 
 ### New input data formats (parsers)
 
-- [csv](/telegraf/v1.8/data_formats/input/csv) - Contributed by @maxunt
-- [grok](/telegraf/v1.8/data_formats/input/grok/) - Contributed by @maxunt
-- [logfmt](/telegraf/v1.8/data_formats/input/logfmt/) - Contributed by @Ayrdrie & @maxunt
-- [wavefront](/telegraf/v1.8/data_formats/input/wavefront/) - Contributed by @puckpuck
+- [csv](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/csv) - Contributed by @maxunt
+- [grok](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/grok/) - Contributed by @maxunt
+- [logfmt](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/logfmt/) - Contributed by @Ayrdrie & @maxunt
+- [wavefront](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/wavefront/) - Contributed by @puckpuck
 
 ### New output data formats (serializers)
 
-- [splunkmetric](/telegraf/v1.8/data_formats/output/splunkmetric/) - Contributed by @ronnocol
+- [splunkmetric](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/output/splunkmetric/) - Contributed by @ronnocol
 
 ### Features
 
@@ -2417,7 +2417,7 @@ These plugins will replace [udp_listener](https://github.com/influxdata/telegraf
 - Add [DMCache input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/dmcache).
 - Add support for precision in [HTTP Listener input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/http_listener).
 - Add `message_len_max` option to the [Kafka consumer input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/kafka_consumer).
-- Add [collectd parser](/telegraf/v1.3/concepts/data_formats_input/#collectd).
+- Add [collectd parser](https://archive.docs.influxdata.com/telegraf/v1.3/concepts/data_formats_input/#collectd).
 - Simplify plugin testing without outputs.
 - Check signature in the [GitHub webhook input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/webhooks/github).
 - Add [papertrail](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/webhooks/papertrail) support to webhooks.
diff --git a/content/telegraf/v1.17/data_formats/output/graphite.md b/content/telegraf/v1.17/data_formats/output/graphite.md
index b22c33a38..6597929fb 100644
--- a/content/telegraf/v1.17/data_formats/output/graphite.md
+++ b/content/telegraf/v1.17/data_formats/output/graphite.md
@@ -10,7 +10,7 @@ menu:
 
 The Graphite data format is serialized from Telegraf metrics using either the
 template pattern or tag support method.  You can select between the two
-methods using the [`graphite_tag_support`](#graphite-tag-support) option.  When set, the tag support method is used,
+methods using the [`graphite_tag_support`](#graphite_tag_support) option.  When set, the tag support method is used,
 otherwise the [template pattern][templates]) option is used.
 
 ## Configuration
diff --git a/content/telegraf/v1.17/guides/using_http.md b/content/telegraf/v1.17/guides/using_http.md
index 61beb7258..7cd882b2c 100644
--- a/content/telegraf/v1.17/guides/using_http.md
+++ b/content/telegraf/v1.17/guides/using_http.md
@@ -10,7 +10,7 @@ menu:
 
 This example walks through using the Telegraf HTTP input plugin to collect live metrics on Citi Bike stations in New York City. Live station data is available in JSON format from [NYC OpenData](https://data.cityofnewyork.us/NYC-BigApps/Citi-Bike-Live-Station-Feed-JSON-/p94q-8hxh).
 
-For the following example to work, configure [`influxdb` output plugin](/telegraf/v1.15/plugins/#influxdb). This plugin is what allows Telegraf to write the metrics to your InfluxDB.
+For the following example to work, configure [`influxdb` output plugin](/telegraf/v1.15/plugins/#output-influxdb). This plugin is what allows Telegraf to write the metrics to your InfluxDB.
 
 ## Configure the HTTP Input plugin in your Telegraf configuration file
 
diff --git a/content/telegraf/v1.17/introduction/installation.md b/content/telegraf/v1.17/introduction/installation.md
index 1dc06bb04..6828edc08 100644
--- a/content/telegraf/v1.17/introduction/installation.md
+++ b/content/telegraf/v1.17/introduction/installation.md
@@ -338,7 +338,7 @@ Compare the output from this command to the hash listed on the downloads page to
 ### Configure an input plugin
 
 The Telegraf ZIP archive contains a default configuration file (`telegraf.conf`).
-In this file, the input plugin for capturing basic [Windows system metrics](/telegraf/v1.17/plugins/#win_perf_counters) is already activated.
+In this file, the input plugin for capturing basic [Windows system metrics](/telegraf/v1.17/plugins/#input-win_perf_counters) is already activated.
 With this plugin, Telegraf monitors the following defined Windows Operating System objects:
 
 - Processor
@@ -358,8 +358,8 @@ Before you start the Telegraf agent, configure an output plugin to send data to
 Choose the appropriate plugin based on the version of InfluxDB you are using.
 
 The `telegraf.conf` file included in the ZIP archive contains sections for configuring
-both the [InfluxDB v1](/telegraf/v1.17/plugins/#influxdb) and
-[InfluxDB v2](/telegraf/v1.17/plugins/#influxdb_v2) output plugins.
+both the [InfluxDB v1](/telegraf/v1.17/plugins/#output-influxdb) and
+[InfluxDB v2](/telegraf/v1.17/plugins/#output-influxdb_v2) output plugins.
 
 #### Writing data to InfluxDB 1.x
 
diff --git a/content/telegraf/v1.18/about_the_project/release-notes-changelog.md b/content/telegraf/v1.18/about_the_project/release-notes-changelog.md
index c43eb5742..2013d551f 100644
--- a/content/telegraf/v1.18/about_the_project/release-notes-changelog.md
+++ b/content/telegraf/v1.18/about_the_project/release-notes-changelog.md
@@ -1761,14 +1761,14 @@ for details about the mapping.
 
 ### New input data formats (parsers)
 
-- [csv](/telegraf/v1.8/data_formats/input/csv) - Contributed by @maxunt
-- [grok](/telegraf/v1.8/data_formats/input/grok/) - Contributed by @maxunt
-- [logfmt](/telegraf/v1.8/data_formats/input/logfmt/) - Contributed by @Ayrdrie & @maxunt
-- [wavefront](/telegraf/v1.8/data_formats/input/wavefront/) - Contributed by @puckpuck
+- [csv](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/csv) - Contributed by @maxunt
+- [grok](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/grok/) - Contributed by @maxunt
+- [logfmt](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/logfmt/) - Contributed by @Ayrdrie & @maxunt
+- [wavefront](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/wavefront/) - Contributed by @puckpuck
 
 ### New output data formats (serializers)
 
-- [splunkmetric](/telegraf/v1.8/data_formats/output/splunkmetric/) - Contributed by @ronnocol
+- [splunkmetric](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/output/splunkmetric/) - Contributed by @ronnocol
 
 ### Features
 
@@ -2549,7 +2549,7 @@ These plugins will replace [udp_listener](https://github.com/influxdata/telegraf
 - Add [DMCache input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/dmcache).
 - Add support for precision in [HTTP Listener input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/http_listener).
 - Add `message_len_max` option to the [Kafka consumer input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/kafka_consumer).
-- Add [collectd parser](/telegraf/v1.3/concepts/data_formats_input/#collectd).
+- Add [collectd parser](https://archive.docs.influxdata.com/telegraf/v1.3/concepts/data_formats_input/#collectd).
 - Simplify plugin testing without outputs.
 - Check signature in the [GitHub webhook input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/webhooks/github).
 - Add [papertrail](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/webhooks/papertrail) support to webhooks.
diff --git a/content/telegraf/v1.18/data_formats/output/graphite.md b/content/telegraf/v1.18/data_formats/output/graphite.md
index 7353b95dc..398a306f7 100644
--- a/content/telegraf/v1.18/data_formats/output/graphite.md
+++ b/content/telegraf/v1.18/data_formats/output/graphite.md
@@ -10,7 +10,7 @@ menu:
 
 The Graphite data format is serialized from Telegraf metrics using either the
 template pattern or tag support method.  You can select between the two
-methods using the [`graphite_tag_support`](#graphite-tag-support) option.  When set, the tag support method is used,
+methods using the [`graphite_tag_support`](#graphite_tag_support) option.  When set, the tag support method is used,
 otherwise the [template pattern][templates]) option is used.
 
 ## Configuration
diff --git a/content/telegraf/v1.18/guides/using_http.md b/content/telegraf/v1.18/guides/using_http.md
index a72392c0f..e20edb7ad 100644
--- a/content/telegraf/v1.18/guides/using_http.md
+++ b/content/telegraf/v1.18/guides/using_http.md
@@ -10,7 +10,7 @@ menu:
 
 This example walks through using the Telegraf HTTP input plugin to collect live metrics on Citi Bike stations in New York City. Live station data is available in JSON format from [NYC OpenData](https://data.cityofnewyork.us/NYC-BigApps/Citi-Bike-Live-Station-Feed-JSON-/p94q-8hxh).
 
-For the following example to work, configure [`influxdb` output plugin](/telegraf/v1.15/plugins/#influxdb). This plugin is what allows Telegraf to write the metrics to your InfluxDB.
+For the following example to work, configure [`influxdb` output plugin](/telegraf/v1.15/plugins/#output-influxdb). This plugin is what allows Telegraf to write the metrics to your InfluxDB.
 
 ## Configure the HTTP Input plugin in your Telegraf configuration file
 
diff --git a/content/telegraf/v1.18/introduction/installation.md b/content/telegraf/v1.18/introduction/installation.md
index da39fb6dc..024b50822 100644
--- a/content/telegraf/v1.18/introduction/installation.md
+++ b/content/telegraf/v1.18/introduction/installation.md
@@ -338,7 +338,7 @@ Compare the output from this command to the hash listed on the downloads page to
 ### Configure an input plugin
 
 The Telegraf ZIP archive contains a default configuration file (`telegraf.conf`).
-In this file, the input plugin for capturing basic [Windows system metrics](/telegraf/v1.18/plugins/#win_perf_counters) is already activated.
+In this file, the input plugin for capturing basic [Windows system metrics](/telegraf/v1.18/plugins/#input-win_perf_counters) is already activated.
 With this plugin, Telegraf monitors the following defined Windows Operating System objects:
 
 - Processor
@@ -358,8 +358,8 @@ Before you start the Telegraf agent, configure an output plugin to send data to
 Choose the appropriate plugin based on the version of InfluxDB you are using.
 
 The `telegraf.conf` file included in the ZIP archive contains sections for configuring
-both the [InfluxDB v1](/telegraf/v1.18/plugins/#influxdb) and
-[InfluxDB v2](/telegraf/v1.18/plugins/#influxdb_v2) output plugins.
+both the [InfluxDB v1](/telegraf/v1.18/plugins/#output-influxdb) and
+[InfluxDB v2](/telegraf/v1.18/plugins/#output-influxdb_v2) output plugins.
 
 #### Writing data to InfluxDB 1.x
 
diff --git a/content/telegraf/v1.19/about_the_project/release-notes-changelog.md b/content/telegraf/v1.19/about_the_project/release-notes-changelog.md
index 3f1ffb36f..5fec56f96 100644
--- a/content/telegraf/v1.19/about_the_project/release-notes-changelog.md
+++ b/content/telegraf/v1.19/about_the_project/release-notes-changelog.md
@@ -1938,14 +1938,14 @@ for details about the mapping.
 
 ### New input data formats (parsers)
 
-- [csv](/telegraf/v1.8/data_formats/input/csv) - Contributed by @maxunt
-- [grok](/telegraf/v1.8/data_formats/input/grok/) - Contributed by @maxunt
-- [logfmt](/telegraf/v1.8/data_formats/input/logfmt/) - Contributed by @Ayrdrie & @maxunt
-- [wavefront](/telegraf/v1.8/data_formats/input/wavefront/) - Contributed by @puckpuck
+- [csv](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/csv) - Contributed by @maxunt
+- [grok](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/grok/) - Contributed by @maxunt
+- [logfmt](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/logfmt/) - Contributed by @Ayrdrie & @maxunt
+- [wavefront](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/wavefront/) - Contributed by @puckpuck
 
 ### New output data formats (serializers)
 
-- [splunkmetric](/telegraf/v1.8/data_formats/output/splunkmetric/) - Contributed by @ronnocol
+- [splunkmetric](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/output/splunkmetric/) - Contributed by @ronnocol
 
 ### Features
 
@@ -2726,7 +2726,7 @@ These plugins will replace [udp_listener](https://github.com/influxdata/telegraf
 - Add [DMCache input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/dmcache).
 - Add support for precision in [HTTP Listener input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/http_listener).
 - Add `message_len_max` option to the [Kafka consumer input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/kafka_consumer).
-- Add [collectd parser](/telegraf/v1.3/concepts/data_formats_input/#collectd).
+- Add [collectd parser](https://archive.docs.influxdata.com/telegraf/v1.3/concepts/data_formats_input/#collectd).
 - Simplify plugin testing without outputs.
 - Check signature in the [GitHub webhook input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/webhooks/github).
 - Add [papertrail](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/webhooks/papertrail) support to webhooks.
diff --git a/content/telegraf/v1.19/data_formats/input/prometheus-remote-write.md b/content/telegraf/v1.19/data_formats/input/prometheus-remote-write.md
index 879bdb7c6..d1ed55dec 100644
--- a/content/telegraf/v1.19/data_formats/input/prometheus-remote-write.md
+++ b/content/telegraf/v1.19/data_formats/input/prometheus-remote-write.md
@@ -19,7 +19,7 @@ For the metrics to completely align with the 1.x endpoint, add a Starlark proces
 
 ### Configuration
 
-Use the [`inputs.http_listener_v2`](/telegraf/v1.19/plugins/#http_listener_v2) plug and set `data_format = "prometheusremotewrite"`
+Use the [`inputs.http_listener_v2`](/telegraf/v1.19/plugins/#input-http_listener_v2) plug and set `data_format = "prometheusremotewrite"`
 
 ```toml
 [[inputs.http_listener_v2]]
diff --git a/content/telegraf/v1.19/data_formats/output/graphite.md b/content/telegraf/v1.19/data_formats/output/graphite.md
index 517b15f40..042258794 100644
--- a/content/telegraf/v1.19/data_formats/output/graphite.md
+++ b/content/telegraf/v1.19/data_formats/output/graphite.md
@@ -10,7 +10,7 @@ menu:
 
 The Graphite data format is serialized from Telegraf metrics using either the
 template pattern or tag support method.  You can select between the two
-methods using the [`graphite_tag_support`](#graphite-tag-support) option.  When set, the tag support method is used,
+methods using the [`graphite_tag_support`](#graphite_tag_support) option.  When set, the tag support method is used,
 otherwise the [template pattern][templates]) option is used.
 
 ## Configuration
diff --git a/content/telegraf/v1.19/external_plugins/write_external_plugin.md b/content/telegraf/v1.19/external_plugins/write_external_plugin.md
index 0bd6f3c0a..46b6d5e57 100644
--- a/content/telegraf/v1.19/external_plugins/write_external_plugin.md
+++ b/content/telegraf/v1.19/external_plugins/write_external_plugin.md
@@ -19,7 +19,7 @@ and feature development of external plugins.
    - [Processor plugins](https://github.com/influxdata/telegraf/blob/master/docs/PROCESSORS.md)
    - [Aggregator plugins](https://github.com/influxdata/telegraf/blob/master/docs/AGGREGATORS.md)
    - [Output plugins](https://github.com/influxdata/telegraf/blob/master/docs/OUTPUTS.md)
-2. If your plugin is written in Go, follow the steps for the [Execd Go Shim](/telegraf/latest/external_plugins/shim).
+2. If your plugin is written in Go, follow the steps for the [Execd Go Shim](/telegraf/v1.19/external_plugins/shim).
 3. Add usage and development instructions in the homepage of your repository for running your plugin with its respective `execd` plugin. Refer to [openvpn](https://github.com/danielnelson/telegraf-execd-openvpn#usage) and [awsalarms](https://github.com/vipinvkmenon/awsalarms#installation) for examples.
 Include the following steps:
      - How to download the release package for your platform or how to clone the binary for your external plugin
diff --git a/content/telegraf/v1.19/guides/using_http.md b/content/telegraf/v1.19/guides/using_http.md
index bfa4cf32b..4db39a5ed 100644
--- a/content/telegraf/v1.19/guides/using_http.md
+++ b/content/telegraf/v1.19/guides/using_http.md
@@ -10,7 +10,7 @@ menu:
 
 This example walks through using the Telegraf HTTP input plugin to collect live metrics on Citi Bike stations in New York City. Live station data is available in JSON format from [NYC OpenData](https://data.cityofnewyork.us/NYC-BigApps/Citi-Bike-Live-Station-Feed-JSON-/p94q-8hxh).
 
-For the following example to work, configure [`influxdb` output plugin](/telegraf/v1.15/plugins/#influxdb). This plugin is what allows Telegraf to write the metrics to your InfluxDB.
+For the following example to work, configure [`influxdb` output plugin](/telegraf/v1.15/plugins/#output-influxdb). This plugin is what allows Telegraf to write the metrics to your InfluxDB.
 
 ## Configure the HTTP Input plugin in your Telegraf configuration file
 
diff --git a/content/telegraf/v1.19/introduction/installation.md b/content/telegraf/v1.19/introduction/installation.md
index d17fa262a..4f4950d4d 100644
--- a/content/telegraf/v1.19/introduction/installation.md
+++ b/content/telegraf/v1.19/introduction/installation.md
@@ -347,7 +347,7 @@ Compare the output from this command to the hash listed on the downloads page to
 ### Configure an input plugin
 
 The Telegraf ZIP archive contains a default configuration file (`telegraf.conf`).
-In this file, the input plugin for capturing basic [Windows system metrics](/telegraf/v1.19/plugins/#win_perf_counters) is already activated.
+In this file, the input plugin for capturing basic [Windows system metrics](/telegraf/v1.19/plugins/#input-win_perf_counters) is already activated.
 With this plugin, Telegraf monitors the following defined Windows Operating System objects:
 
 - Processor
@@ -367,8 +367,8 @@ Before you start the Telegraf agent, configure an output plugin to send data to
 Choose the appropriate plugin based on the version of InfluxDB you are using.
 
 The `telegraf.conf` file included in the ZIP archive contains sections for configuring
-both the [InfluxDB v1](/telegraf/v1.19/plugins/#influxdb) and
-[InfluxDB v2](/telegraf/v1.19/plugins/#influxdb_v2) output plugins.
+both the [InfluxDB v1](/telegraf/v1.19/plugins/#output-influxdb) and
+[InfluxDB v2](/telegraf/v1.19/plugins/#output-influxdb_v2) output plugins.
 
 #### Writing data to InfluxDB 1.x
 
diff --git a/content/telegraf/v1.20/about_the_project/release-notes-changelog.md b/content/telegraf/v1.20/about_the_project/release-notes-changelog.md
index e0ed439e5..fefaa06e3 100644
--- a/content/telegraf/v1.20/about_the_project/release-notes-changelog.md
+++ b/content/telegraf/v1.20/about_the_project/release-notes-changelog.md
@@ -2098,14 +2098,14 @@ for details about the mapping.
 
 ### New input data formats (parsers)
 
-- [csv](/telegraf/v1.8/data_formats/input/csv) - Contributed by @maxunt
-- [grok](/telegraf/v1.8/data_formats/input/grok/) - Contributed by @maxunt
-- [logfmt](/telegraf/v1.8/data_formats/input/logfmt/) - Contributed by @Ayrdrie & @maxunt
-- [wavefront](/telegraf/v1.8/data_formats/input/wavefront/) - Contributed by @puckpuck
+- [csv](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/csv) - Contributed by @maxunt
+- [grok](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/grok/) - Contributed by @maxunt
+- [logfmt](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/logfmt/) - Contributed by @Ayrdrie & @maxunt
+- [wavefront](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/wavefront/) - Contributed by @puckpuck
 
 ### New output data formats (serializers)
 
-- [splunkmetric](/telegraf/v1.8/data_formats/output/splunkmetric/) - Contributed by @ronnocol
+- [splunkmetric](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/output/splunkmetric/) - Contributed by @ronnocol
 
 ### Features
 
@@ -2886,7 +2886,7 @@ These plugins will replace [udp_listener](https://github.com/influxdata/telegraf
 - Add [DMCache input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/dmcache).
 - Add support for precision in [HTTP Listener input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/http_listener).
 - Add `message_len_max` option to the [Kafka consumer input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/kafka_consumer).
-- Add [collectd parser](/telegraf/v1.3/concepts/data_formats_input/#collectd).
+- Add [collectd parser](https://archive.docs.influxdata.com/telegraf/v1.3/concepts/data_formats_input/#collectd).
 - Simplify plugin testing without outputs.
 - Check signature in the [GitHub webhook input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/webhooks/github).
 - Add [papertrail](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/webhooks/papertrail) support to webhooks.
diff --git a/content/telegraf/v1.20/data_formats/input/prometheus-remote-write.md b/content/telegraf/v1.20/data_formats/input/prometheus-remote-write.md
index 0128aa8c8..bf5817476 100644
--- a/content/telegraf/v1.20/data_formats/input/prometheus-remote-write.md
+++ b/content/telegraf/v1.20/data_formats/input/prometheus-remote-write.md
@@ -19,7 +19,7 @@ For the metrics to completely align with the 1.x endpoint, add a Starlark proces
 
 ### Configuration
 
-Use the [`inputs.http_listener_v2`](/telegraf/v1.20/plugins/#http_listener_v2) plug and set `data_format = "prometheusremotewrite"`
+Use the [`inputs.http_listener_v2`](/telegraf/v1.20/plugins/#input-http_listener_v2) plug and set `data_format = "prometheusremotewrite"`
 
 ```toml
 [[inputs.http_listener_v2]]
diff --git a/content/telegraf/v1.20/data_formats/output/graphite.md b/content/telegraf/v1.20/data_formats/output/graphite.md
index afd7443bd..8c58cd718 100644
--- a/content/telegraf/v1.20/data_formats/output/graphite.md
+++ b/content/telegraf/v1.20/data_formats/output/graphite.md
@@ -10,7 +10,7 @@ menu:
 
 The Graphite data format is serialized from Telegraf metrics using either the
 template pattern or tag support method.  You can select between the two
-methods using the [`graphite_tag_support`](#graphite-tag-support) option.  When set, the tag support method is used,
+methods using the [`graphite_tag_support`](#graphite_tag_support) option.  When set, the tag support method is used,
 otherwise the [template pattern][templates]) option is used.
 
 ## Configuration
diff --git a/content/telegraf/v1.20/external_plugins/_index.md b/content/telegraf/v1.20/external_plugins/_index.md
index 4b0085b13..909697c8e 100644
--- a/content/telegraf/v1.20/external_plugins/_index.md
+++ b/content/telegraf/v1.20/external_plugins/_index.md
@@ -14,7 +14,7 @@ more flexibility compared to internal Telegraf plugins. Benefits to using extern
 - Using licensed software (not available to open source community)
 - Including large dependencies that would otherwise bloat Telegraf
 - Using your external plugin immediately without waiting for the Telegraf team to publish
-- Easily convert plugins between internal and external using the [shim](/telegraf/latest/external_plugins/shim/)
+- Easily convert plugins between internal and external using the [shim](/telegraf/v1.20/external_plugins/shim/)
 
 
 
diff --git a/content/telegraf/v1.20/external_plugins/write_external_plugin.md b/content/telegraf/v1.20/external_plugins/write_external_plugin.md
index c40377b62..03109534d 100644
--- a/content/telegraf/v1.20/external_plugins/write_external_plugin.md
+++ b/content/telegraf/v1.20/external_plugins/write_external_plugin.md
@@ -19,7 +19,7 @@ and feature development of external plugins.
    - [Processor plugins](https://github.com/influxdata/telegraf/blob/master/docs/PROCESSORS.md)
    - [Aggregator plugins](https://github.com/influxdata/telegraf/blob/master/docs/AGGREGATORS.md)
    - [Output plugins](https://github.com/influxdata/telegraf/blob/master/docs/OUTPUTS.md)
-2. If your plugin is written in Go, follow the steps for the [Execd Go Shim](/telegraf/latest/external_plugins/shim).
+2. If your plugin is written in Go, follow the steps for the [Execd Go Shim](/telegraf/v1.20/external_plugins/shim).
 3. Add usage and development instructions in the homepage of your repository for running your plugin with its respective `execd` plugin. Refer to [openvpn](https://github.com/danielnelson/telegraf-execd-openvpn#usage) and [awsalarms](https://github.com/vipinvkmenon/awsalarms#installation) for examples.
 Include the following steps:
      - How to download the release package for your platform or how to clone the binary for your external plugin
diff --git a/content/telegraf/v1.20/guides/using_http.md b/content/telegraf/v1.20/guides/using_http.md
index c447d7c4e..0d73aa844 100644
--- a/content/telegraf/v1.20/guides/using_http.md
+++ b/content/telegraf/v1.20/guides/using_http.md
@@ -10,7 +10,7 @@ menu:
 
 This example walks through using the Telegraf HTTP input plugin to collect live metrics on Citi Bike stations in New York City. Live station data is available in JSON format from [NYC OpenData](https://data.cityofnewyork.us/NYC-BigApps/Citi-Bike-Live-Station-Feed-JSON-/p94q-8hxh).
 
-For the following example to work, configure [`influxdb` output plugin](/telegraf/v1.15/plugins/#influxdb). This plugin is what allows Telegraf to write the metrics to your InfluxDB.
+For the following example to work, configure [`influxdb` output plugin](/telegraf/v1.15/plugins/#output-influxdb). This plugin is what allows Telegraf to write the metrics to your InfluxDB.
 
 ## Configure the HTTP Input plugin in your Telegraf configuration file
 
diff --git a/content/telegraf/v1.20/introduction/installation.md b/content/telegraf/v1.20/introduction/installation.md
index e85de9f47..c7e9fe697 100644
--- a/content/telegraf/v1.20/introduction/installation.md
+++ b/content/telegraf/v1.20/introduction/installation.md
@@ -278,7 +278,7 @@ Compare the output from this command to the hash listed on the downloads page to
 ### Configure an input plugin
 
 The Telegraf ZIP archive contains a default configuration file (`telegraf.conf`).
-In this file, the input plugin for capturing basic [Windows system metrics](/telegraf/v1.20/plugins/#win_perf_counters) is already activated.
+In this file, the input plugin for capturing basic [Windows system metrics](/telegraf/v1.20/plugins/#input-win_perf_counters) is already activated.
 With this plugin, Telegraf monitors the following defined Windows Operating System objects:
 
 - Processor
@@ -298,8 +298,8 @@ Before you start the Telegraf agent, configure an output plugin to send data to
 Choose the appropriate plugin based on the version of InfluxDB you are using.
 
 The `telegraf.conf` file included in the ZIP archive contains sections for configuring
-both the [InfluxDB v1](/telegraf/v1.20/plugins/#influxdb) and
-[InfluxDB v2](/telegraf/v1.20/plugins/#influxdb_v2) output plugins.
+both the [InfluxDB v1](/telegraf/v1.20/plugins/#output-influxdb) and
+[InfluxDB v2](/telegraf/v1.20/plugins/#output-influxdb_v2) output plugins.
 
 #### Writing data to InfluxDB 1.x
 
diff --git a/content/telegraf/v1.21/about_the_project/release-notes-changelog.md b/content/telegraf/v1.21/about_the_project/release-notes-changelog.md
index 2ccbdf770..23b6c8360 100644
--- a/content/telegraf/v1.21/about_the_project/release-notes-changelog.md
+++ b/content/telegraf/v1.21/about_the_project/release-notes-changelog.md
@@ -10,6 +10,52 @@ menu:
     weight: 10
     parent: About the project
 ---
+## v1.21.4 [2022-2-16]
+
+- Update to Go 1.17.7 to address [three security issues](https://groups.google.com/g/golang-announce/c/SUsQn0aSgPQ/m/gx45t8JEAgAJ?pli=1) in the library.
+- Update all `go.opentelemetry.io` from 0.24.0 to 0.27.0.
+- Update `github.com/signalfx/golib/v3` from 3.3.38 to 3.3.43.
+- Update `github.com/aliyun/alibaba-cloud-sdk-go` from 1.61.1004 to 1.61.1483.
+- Update `github.com/denisenkom/go-mssqldb` from 0.10.0 to 0.12.0.
+- Update `github.com/gopcua/opcua` from 0.2.3 to 0.3.1.
+- Update `github.com/nats-io/nats-server/v2` from 2.6.5 to 2.7.2.
+- Update `k8s.io/client-go` from 0.22.2 to 0.23.3.
+- Update `github.com/aws/aws-sdk-go-v2/service/kinesis` from 1.6.0 to 1.13.0.
+- Update `github.com/benbjohnson/clock` from 1.1.0 to 1.3.0.
+- Update `github.com/Azure/azure-kusto-go` from 0.5.0 to 0.5.2.
+- Update `github.com/vmware/govmomi` from 0.27.2 to 0.27.3.
+- Update `github.com/prometheus/client_golang` from 1.11.0 to 1.12.1.
+- Update `go.mongodb.org/mongo-driver` from 1.7.3 to 1.8.3.
+- Update `github.com/google/go-cmp` from 0.5.6 to 0.5.7.
+- Update `go.opentelemetry.io/collector/model` from 0.39.0 to 0.43.2.
+- Update `github.com/multiplay/go-ts3` from 1.0.0 to 1.0.1.
+- Update `cloud.google.com/go/monitoring` from 0.2.0 to 1.2.0.
+- Update `github.com/vmware/govmomi` from 0.26.0 to 0.27.2.
+
+### Input plugin updates
+- Docker (`docker`): Update memory usage calculation.
+- ECS (`ecs`): Use current time as timestamp.
+- SNMP (`snmp`): Ensure folders do not get loaded more than once.
+- Windows Performance Counters (`win_perf_counters`): Add deprecated warning and version.
+
+### Output plugin updates
+- AMQP (`amqp`): Check for nil client before closing.
+- Azure Data Explorer (`azure_data_explorer`): Lower RAM usage.
+- ElasticSearch (`elasticsearch`): Add scheme to fix error in sniffing option.
+
+### Parser plugin updates
+- JSON v2 (`json_v2`):
+  - Fix timestamp change during execution.
+  - Fix incorrect handling of `timestamp_path`.
+  - Allow optional paths and handle wrong paths correctly.
+
+### Serializer updates
+- Prometheus serializer (`prometheusremotewrite`): Use correct timestamp unit.
+
+### New External Plugins
+- [apt](https://github.com/x70b1/telegraf-apt/blob/master/README.md)(`telegraf-apt`) - Contributed by [@x70b1](https://github.com/x70b1).
+- [knot](https://github.com/x70b1/telegraf-knot/blob/master/README.md)(`telegraf-knot`) - Contributed by [@x70b1](https://github.com/x70b1).
+
 ## v1.21.3 [2022-1-27]
 
 - Update `grpc` module to v1.44.0.
@@ -2284,14 +2330,14 @@ for details about the mapping.
 
 ### New input data formats (parsers)
 
-- [csv](/telegraf/v1.8/data_formats/input/csv) - Contributed by @maxunt
-- [grok](/telegraf/v1.8/data_formats/input/grok/) - Contributed by @maxunt
-- [logfmt](/telegraf/v1.8/data_formats/input/logfmt/) - Contributed by @Ayrdrie & @maxunt
-- [wavefront](/telegraf/v1.8/data_formats/input/wavefront/) - Contributed by @puckpuck
+- [csv](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/csv) - Contributed by @maxunt
+- [grok](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/grok/) - Contributed by @maxunt
+- [logfmt](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/logfmt/) - Contributed by @Ayrdrie & @maxunt
+- [wavefront](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/wavefront/) - Contributed by @puckpuck
 
 ### New output data formats (serializers)
 
-- [splunkmetric](/telegraf/v1.8/data_formats/output/splunkmetric/) - Contributed by @ronnocol
+- [splunkmetric](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/output/splunkmetric/) - Contributed by @ronnocol
 
 ### Features
 
@@ -3072,7 +3118,7 @@ These plugins will replace [udp_listener](https://github.com/influxdata/telegraf
 - Add [DMCache input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/dmcache).
 - Add support for precision in [HTTP Listener input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/http_listener).
 - Add `message_len_max` option to the [Kafka consumer input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/kafka_consumer).
-- Add [collectd parser](/telegraf/v1.3/concepts/data_formats_input/#collectd).
+- Add [collectd parser](https://archive.docs.influxdata.com/telegraf/v1.3/concepts/data_formats_input/#collectd).
 - Simplify plugin testing without outputs.
 - Check signature in the [GitHub webhook input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/webhooks/github).
 - Add [papertrail](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/webhooks/papertrail) support to webhooks.
diff --git a/content/telegraf/v1.21/administration/configuration.md b/content/telegraf/v1.21/administration/configuration.md
index 60f79aea1..074d33991 100644
--- a/content/telegraf/v1.21/administration/configuration.md
+++ b/content/telegraf/v1.21/administration/configuration.md
@@ -120,10 +120,9 @@ Maximum `flush_interval` will be `flush_interval` + `flush_jitter`
 This is primarily to avoid
 large write spikes for users running a large number of Telegraf instances.
 For example, a `flush_jitter` of 5s and `flush_interval` of 10s means flushes will happen every 10-15s.
-* **precision**: By default, precision will be set to the same timestamp order
-as the collection interval, with the maximum being 1s. Precision will NOT
-be used for service inputs, such as `logparser` and `statsd`. Valid values are
-`ns`, `us` (or `µs`), `ms`, and `s`.
+* **precision**: Collected metrics are rounded to the precision specified as an 
+`interval` (integer + unit, ex: `1ns`, `1us`, `1ms`, and `1s` . Precision will NOT
+be used for service inputs, such as `logparser` and `statsd`. 
 * **logfile**: Specify the log file name. The empty string means to log to `stderr`.
 * **debug**: Run Telegraf in debug mode.
 * **quiet**: Run Telegraf in quiet mode (error messages only).
@@ -276,7 +275,7 @@ fields which begin with `time_`.
 [[outputs.influxdb]]
   url = "http://192.168.59.103:8086" # required.
   database = "telegraf" # required.
-  precision = "s"
+  precision = "1s"
 
 # INPUTS
 [[inputs.cpu]]
@@ -412,21 +411,21 @@ Additional inputs (or outputs) of the same type can be specified by defining the
 [[outputs.influxdb]]
   urls = [ "http://localhost:8086" ]
   database = "telegraf"
-  precision = "s"
+  precision = "1s"
   # Drop all measurements that start with "aerospike"
   namedrop = ["aerospike*"]
 
 [[outputs.influxdb]]
   urls = [ "http://localhost:8086" ]
   database = "telegraf-aerospike-data"
-  precision = "s"
+  precision = "1s"
   # Only accept aerospike data:
   namepass = ["aerospike*"]
 
 [[outputs.influxdb]]
   urls = [ "http://localhost:8086" ]
   database = "telegraf-cpu0-data"
-  precision = "s"
+  precision = "1s"
   # Only store measurements where the tag "cpu" matches the value "cpu0"
   [outputs.influxdb.tagpass]
     cpu = ["cpu0"]
@@ -467,3 +466,7 @@ to the system load metrics due to the `namepass` parameter.
 [[outputs.file]]
   files = ["stdout"]
 ```
+
+To learn more about configuring the Telegraf agent, watch the following video:
+
+{{< youtube txUcAxMDBlQ >}}
diff --git a/content/telegraf/v1.21/data_formats/input/prometheus-remote-write.md b/content/telegraf/v1.21/data_formats/input/prometheus-remote-write.md
index d8c4466dc..ecc4067f2 100644
--- a/content/telegraf/v1.21/data_formats/input/prometheus-remote-write.md
+++ b/content/telegraf/v1.21/data_formats/input/prometheus-remote-write.md
@@ -21,7 +21,7 @@ For the metrics to completely align with the 1.x endpoint, add a Starlark proces
 
 ### Configuration
 
-Use the [`inputs.http_listener_v2`](/telegraf/v1.21/plugins/#http_listener_v2) plug and set `data_format = "prometheusremotewrite"`
+Use the [`inputs.http_listener_v2`](/telegraf/v1.21/plugins/#input-http_listener_v2) plug and set `data_format = "prometheusremotewrite"`
 
 ```toml
 [[inputs.http_listener_v2]]
diff --git a/content/telegraf/v1.21/data_formats/output/graphite.md b/content/telegraf/v1.21/data_formats/output/graphite.md
index ddd247535..c2aa697ce 100644
--- a/content/telegraf/v1.21/data_formats/output/graphite.md
+++ b/content/telegraf/v1.21/data_formats/output/graphite.md
@@ -11,7 +11,7 @@ menu:
 
 The Graphite data format is serialized from Telegraf metrics using either the
 template pattern or tag support method.  You can select between the two
-methods using the [`graphite_tag_support`](#graphite-tag-support) option.  When set, the tag support method is used,
+methods using the [`graphite_tag_support`](#graphite_tag_support) option.  When set, the tag support method is used,
 otherwise the [template pattern][templates]) option is used.
 
 ## Configuration
diff --git a/content/telegraf/v1.21/external_plugins/_index.md b/content/telegraf/v1.21/external_plugins/_index.md
index 9f3748257..d344277f6 100644
--- a/content/telegraf/v1.21/external_plugins/_index.md
+++ b/content/telegraf/v1.21/external_plugins/_index.md
@@ -15,7 +15,7 @@ more flexibility compared to internal Telegraf plugins. Benefits to using extern
 - Using licensed software (not available to open source community)
 - Including large dependencies that would otherwise bloat Telegraf
 - Using your external plugin immediately without waiting for the Telegraf team to publish
-- Easily convert plugins between internal and external using the [shim](/telegraf/latest/external_plugins/shim/)
+- Easily convert plugins between internal and external using the [shim](/telegraf/v1.21/external_plugins/shim/)
 
 
 
diff --git a/content/telegraf/v1.21/external_plugins/write_external_plugin.md b/content/telegraf/v1.21/external_plugins/write_external_plugin.md
index 865f8c976..5a70393c6 100644
--- a/content/telegraf/v1.21/external_plugins/write_external_plugin.md
+++ b/content/telegraf/v1.21/external_plugins/write_external_plugin.md
@@ -20,7 +20,7 @@ and feature development of external plugins.
    - [Processor plugins](https://github.com/influxdata/telegraf/blob/master/docs/PROCESSORS.md)
    - [Aggregator plugins](https://github.com/influxdata/telegraf/blob/master/docs/AGGREGATORS.md)
    - [Output plugins](https://github.com/influxdata/telegraf/blob/master/docs/OUTPUTS.md)
-2. If your plugin is written in Go, follow the steps for the [Execd Go Shim](/telegraf/latest/external_plugins/shim).
+2. If your plugin is written in Go, follow the steps for the [Execd Go Shim](/telegraf/v1.21/external_plugins/shim).
 3. Add usage and development instructions in the homepage of your repository for running your plugin with its respective `execd` plugin. Refer to [openvpn](https://github.com/danielnelson/telegraf-execd-openvpn#usage) and [awsalarms](https://github.com/vipinvkmenon/awsalarms#installation) for examples.
 Include the following steps:
      - How to download the release package for your platform or how to clone the binary for your external plugin
diff --git a/content/telegraf/v1.21/guides/using_http.md b/content/telegraf/v1.21/guides/using_http.md
index c3d842080..bbad3769b 100644
--- a/content/telegraf/v1.21/guides/using_http.md
+++ b/content/telegraf/v1.21/guides/using_http.md
@@ -9,9 +9,9 @@ menu:
     parent: Guides
 ---
 
-This example walks through using the Telegraf HTTP input plugin to collect live metrics on Citi Bike stations in New York City. Live station data is available in JSON format from [NYC OpenData](https://data.cityofnewyork.us/NYC-BigApps/Citi-Bike-Live-Station-Feed-JSON-/p94q-8hxh).
+This example walks through using the Telegraf HTTP input plugin to collect live metrics on Citi Bike stations in New York City. Live station data is available in JSON format directly from [Citi Bike](https://ride.citibikenyc.com/system-data).
 
-For the following example to work, configure [`influxdb` output plugin](/telegraf/v1.15/plugins/#influxdb). This plugin is what allows Telegraf to write the metrics to your InfluxDB.
+For the following example to work, configure [`influxdb_v2` output plugin](/telegraf/v1.21/plugins/#output-influxdb_v2). This plugin is what allows Telegraf to write the metrics to InfluxDB.
 
 ## Configure the HTTP Input plugin in your Telegraf configuration file
 
@@ -20,7 +20,7 @@ To retrieve data from the Citi Bike URL endpoint, enable the `inputs.http` input
 Specify the following options:
 
 ### `urls`
-One or more URLs to read metrics from. For this example,  use `https://feeds.citibikenyc.com/stations/stations.json`.
+One or more URLs to read metrics from. For this example,  use `https://gbfs.citibikenyc.com/gbfs/en/station_status.json`.
 
 ### `data_format`
 The format of the data in the HTTP endpoints that Telegraf will ingest. For this example, use JSON.
@@ -28,73 +28,64 @@ The format of the data in the HTTP endpoints that Telegraf will ingest. For this
 
 ## Add parser information to your Telegraf configuration
 
-Specify the following JSON-specific options.
+Specify the following JSON-specific options. In this example, we use the objects subtable to gather
+data from [JSON Objects](https://www.w3schools.com/js/js_json_objects.asp).
 
 ### JSON
 
-#### `json_query`
-To parse only the relevant portion of JSON data, set the `json_query` option with a [GJSON](https://github.com/tidwall/gjson) path. The result of the query should contain a JSON object or an array of objects.
-In this case, we don't want to parse the JSON query's `executionTime` at the beginning of the data, so we'll limit this to include only the data in the `stationBeanList` array.
+#### `path`
+To parse a JSON object, set the `path` option with a [GJSON](https://github.com/tidwall/gjson) path. The result of the query should contain a JSON object or an array of objects. The [GJSON playground](https://gjson.dev/) is a very helpful tool in checking your query.
 
-#### `tag_keys`
-List of one or more JSON keys that should be added as tags. For this example, we'll use the tag keys `id`, `stationName`, `city`, and `postalCode`.
+#### `tags`
+List of one or more JSON keys that should be added as tags. For this example, we'll use the tag key `station_id`.
 
-#### `json_string_fields`
-List the keys of fields that are in string format so that they can be parsed as strings. Here, the string fields are `statusValue`, `stAddress1`, `stAddress2`, `location`, and `landMark`.
-
-#### `json_time_key`
-Key from the JSON file that creates the timestamp metric. In this case, we want to use the time that station data was last reported, or the `lastCommunicationTime`. If you don't specify a key, the time that Telegraf reads the data becomes the timestamp.
-
-#### `json_time_format`
-The format used to interpret the designated `json_time_key`. This example uses [Go reference time format](https://golang.org/pkg/time/#Time.Format). For example, `Mon Jan 2 15:04:05 MST 2006`.
-
-#### `json_timezone`
-The timezone We'll set this to the Unix TZ value where our bike data takes place, `America/New_York`.
+#### `timestamp_key`
+Key from the JSON file that creates the timestamp metric. In this case, we want to use the time that station data was last reported, or the `last_reported`. If you don't specify a key, the time that Telegraf reads the data becomes the timestamp.
 
+#### `timestamp_format`
+The format used to interpret the designated `timestamp_key`. The `last_reported` time in this example is reported in unix format.
 
 #### Example configuration
 
   ```toml
-  [[inputs.http]]
-  #URL for NYC's Citi Bike station data in JSON format
-  urls = ["https://feeds.citibikenyc.com/stations/stations.json"]
+[[inputs.http]]
+  # URL for NYC's Citi Bike station data in JSON format
+  urls = ["https://gbfs.citibikenyc.com/gbfs/en/station_status.json"]
 
-  #Overwrite measurement name from default `http` to `citibikenyc`
-  name_override = "citibikenyc"
+  # Overwrite measurement name from default `http` to `citibikenyc`
+  name_override = "citibike"
 
-  #Exclude url and host items from tags
+  # Exclude url and host items from tags
   tagexclude = ["url", "host"]
 
-  #Data from HTTP in JSON format
+  # Data from HTTP in JSON format
   data_format = "json_v2"
 
-  #Parse `stationBeanList` array only
-  json_query = "stationBeanList"
 
-  #Set station metadata as tags
-  tag_keys = ["id", "stationName", "city", "postalCode"]
+        # Add a subtable to use the `json_v2` parser
+        [[inputs.http.json_v2]]
 
-  #Do not include station landmark data as fields
-  fielddrop = ["landMark"]
+            # Add an object subtable for to parse a JSON object
+            [[inputs.http.json_v2.object]]
 
-  #JSON values to set as string fields
-  json_string_fields = ["statusValue", "stAddress1", "stAddress2", "location", "landMark"]
+                # Parse data in `data.stations` path only
+                path = "data.stations"
 
-  #Latest station information reported at `lastCommunicationTime`
-  json_time_key = "lastCommunicationTime"
+                #Set station metadata as tags
+                tags = ["station_id"]
 
-  #Time is reported in Golang "reference time" format
-  json_time_format = "2006-01-02 03:04:05 PM"
+                # Latest station information reported at `last_reported`
+                timestamp_key = "last_reported"
 
-  #Time is reported in Eastern Standard Time (EST)
-  json_timezone = "America/New_York"
+                # Time is reported in unix timestamp format
+                timestamp_format = "unix"
   ```
 
 
 
 ## Start Telegraf and verify data appears
 
-[Start the Telegraf service](/telegraf/v1.15/introduction/getting-started/#start-telegraf-service).
+[Start the Telegraf service](/telegraf/v1.21/introduction/getting-started/#start-telegraf-service).
 
 To test that the data is being sent to InfluxDB, run the following (replacing `telegraf.conf` with the path to your configuration file):
 
@@ -104,14 +95,12 @@ telegraf -config ~/telegraf.conf -test
 
 This command should return line protocol that looks similar to the following:
 
-
 ```
-citibikenyc,id=3443,stationName=W\ 52\ St\ &\ 6\ Ave statusKey=1,location="",totalDocks=41,availableDocks=32,latitude=40.76132983124814,longitude=-73.97982001304626,availableBikes=8,stAddress2="",stAddress1="W 52 St & 6 Ave",statusValue="In Service" 1581533519000000000
-citibikenyc,id=367,stationName=E\ 53\ St\ &\ Lexington\ Ave availableBikes=8,stAddress1="E 53 St & Lexington Ave",longitude=-73.97069431,latitude=40.75828065,stAddress2="",statusKey=1,location="",statusValue="In Service",totalDocks=34,availableDocks=24 1581533492000000000
-citibikenyc,id=359,stationName=E\ 47\ St\ &\ Park\ Ave totalDocks=64,availableBikes=15,statusValue="In Service",location="",latitude=40.75510267,availableDocks=49,stAddress1="E 47 St & Park Ave",longitude=-73.97498696,statusKey=1,stAddress2="" 1581533535000000000
-citibikenyc,id=304,stationName=Broadway\ &\ Battery\ Pl statusValue="In Service",availableDocks=11,stAddress1="Broadway & Battery Pl",statusKey=1,stAddress2="",location="",totalDocks=33,latitude=40.70463334,longitude=-74.01361706,availableBikes=22 1581533499000000000
+citibike,station_id=4703 eightd_has_available_keys=false,is_installed=1,is_renting=1,is_returning=1,legacy_id="4703",num_bikes_available=6,num_bikes_disabled=2,num_docks_available=26,num_docks_disabled=0,num_ebikes_available=0,station_status="active" 1641505084000000000
+citibike,station_id=4704 eightd_has_available_keys=false,is_installed=1,is_renting=1,is_returning=1,legacy_id="4704",num_bikes_available=10,num_bikes_disabled=2,num_docks_available=36,num_docks_disabled=0,num_ebikes_available=0,station_status="active" 1641505084000000000
+citibike,station_id=4711 eightd_has_available_keys=false,is_installed=1,is_renting=1,is_returning=1,legacy_id="4711",num_bikes_available=9,num_bikes_disabled=0,num_docks_available=36,num_docks_disabled=0,num_ebikes_available=1,station_status="active" 1641505084000000000
 ```
 
-Now, you can explore and query the Citi Bike data in InfluxDB. The example below is an InfluxQL query and visualization showing the number of available bikes over the past 15 minutes at the Broadway and West 29th Street station.
+Now, you can explore and query the Citi Bike data in InfluxDB. The example below is an Flux query and visualization showing the number of available bikes over the past 15 minutes.
 
-![Citi Bike visualization](/img/telegraf/1-13-citibike_query.png)
+![Citi Bike visualization](/img/telegraf/new-citibike_query.png)
diff --git a/content/telegraf/v1.21/introduction/getting-started.md b/content/telegraf/v1.21/introduction/getting-started.md
index e2d942b0b..33da2ac19 100644
--- a/content/telegraf/v1.21/introduction/getting-started.md
+++ b/content/telegraf/v1.21/introduction/getting-started.md
@@ -149,6 +149,18 @@ Notice that the timestamps occur at rounded ten second intervals (that is, `:00`
 
 That's it! You ready to use Telegraf to collect metrics and write them to your output of choice.
 
-For an introduction to Telegraf and an overview of how it works, watch the following video:
+For an introduction to Telegraf and an overview of how it works, watch the following videos:
+
+{{< tabs-wrapper >}}
+{{% tabs "small" %}}
+[Intro to Telegraf](#)
+[Telegraf Plugin Overview](#)
+{{% /tabs %}}
+{{% tab-content %}}
+{{< youtube vGJeo3FaMds >}}
+{{% /tab-content %}}
+{{% tab-content %}}
+{{< youtube k5m7SHgXRYQ >}}
+{{% /tab-content %}}
+{{< /tabs-wrapper >}}
 
-{{< youtube vGJeo3FaMds >}}
\ No newline at end of file
diff --git a/content/telegraf/v1.21/introduction/installation.md b/content/telegraf/v1.21/introduction/installation.md
index 1352f2b36..7996e8fe0 100644
--- a/content/telegraf/v1.21/introduction/installation.md
+++ b/content/telegraf/v1.21/introduction/installation.md
@@ -279,7 +279,7 @@ Compare the output from this command to the hash listed on the downloads page to
 ### Configure an input plugin
 
 The Telegraf ZIP archive contains a default configuration file (`telegraf.conf`).
-In this file, the input plugin for capturing basic [Windows system metrics](/telegraf/v1.21/plugins/#win_perf_counters) is already activated.
+In this file, the input plugin for capturing basic [Windows system metrics](/telegraf/v1.21/plugins/#input-win_perf_counters) is already activated.
 With this plugin, Telegraf monitors the following defined Windows Operating System objects:
 
 - Processor
@@ -299,8 +299,8 @@ Before you start the Telegraf agent, configure an output plugin to send data to
 Choose the appropriate plugin based on the version of InfluxDB you are using.
 
 The `telegraf.conf` file included in the ZIP archive contains sections for configuring
-both the [InfluxDB v1](/telegraf/v1.21/plugins/#influxdb) and
-[InfluxDB v2](/telegraf/v1.21/plugins/#influxdb_v2) output plugins.
+both the [InfluxDB v1](/telegraf/v1.21/plugins/#output-influxdb) and
+[InfluxDB v2](/telegraf/v1.21/plugins/#output-influxdb_v2) output plugins.
 
 #### Writing data to InfluxDB 1.x
 
diff --git a/content/telegraf/v1.22/_index.md b/content/telegraf/v1.22/_index.md
new file mode 100644
index 000000000..9dabc5b84
--- /dev/null
+++ b/content/telegraf/v1.22/_index.md
@@ -0,0 +1,19 @@
+---
+title: Telegraf 1.22 documentation
+description: >
+  Documentation for Telegraf, the plugin-driven server agent of the InfluxData
+  time series platform, used to collect and report metrics. Telegraf supports four categories of plugins -- input, output, aggregator, and processor.
+menu:
+  telegraf_1_22:
+    name: Telegraf v1.22
+weight: 1
+related:
+  - /resources/videos/intro-to-telegraf/
+---
+
+Telegraf, a server-based agent, collects and sends metrics and events from databases, systems, and IoT sensors.
+Written in Go, Telegraf compiles into a single binary with no external dependencies--requiring very minimal memory.
+
+For an introduction to Telegraf and an overview of how it works, watch the following video:
+
+{{< youtube vGJeo3FaMds >}}
diff --git a/content/telegraf/v1.22/commands.md b/content/telegraf/v1.22/commands.md
new file mode 100644
index 000000000..47cd4d65c
--- /dev/null
+++ b/content/telegraf/v1.22/commands.md
@@ -0,0 +1,92 @@
+---
+title: Telegraf commands and flags
+description: The `telegraf` command starts and runs all the processes necessary for Telegraf to function.
+menu:
+  telegraf_1_22_ref:
+
+    name: Commands
+    weight: 20
+---
+
+The `telegraf` command starts and runs all the processes necessary for Telegraf to function.
+
+## Usage
+
+```
+telegraf [commands]
+telegraf [flags]
+```
+
+## Commands
+
+
+
+| Command   | Description                                    |
+| :-------- | :--------------------------------------------- |
+| `config`  | Print out full sample configuration to stdout. |
+| `version` | Print version to stdout.                       |
+
+## Flags {id="telegraf-command-flags"}
+
+| Flag                             | Description                                                                                                                       |
+| :------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------- |
+| `--aggregator-filter <filter>`   | Filter aggregators to enable. Separator is `:`.                                                                                   |
+| `--config <file>`                | Configuration file to load.                                                                                                       |
+| `--config-directory <directory>` | Directory containing additional `*.conf` files.                                                                                    |
+| `--deprecation-list` | Print all deprecated plugins or plugin options.                                                                                    |
+| `--watch-config`                 | Restart Telegraf on local configuration changes. Use either fs notifications (`inotify`) or polling (`poll`). Disabled by default        |
+| `--plugin-directory <directory>` | Directory containing `*.so` files to search recursively for plugins. Found plugins are loaded, tagged, and identified.            |
+| `--debug`                        | Enable debug logging.                                                                                                             |
+| `--input-filter <filter>`        | Filter input plugins to enable. Separator is `:`.                                                                                        |
+| `--input-list`                   | Print available input plugins.                                                                                                    |
+| `--output-filter`                | Filter output plugins to enable. Separator is `:`.                                                                                       |
+| `--output-list`                  | Print available output plugins.                                                                                                   |
+| `--pidfile <file>`               | File to write PID to.                                                                                                             |
+| `--pprof-addr <address>`         | pprof address to listen on. Disabled by default.                                                                                  |
+| `--processor-filter <filter>`    | Filter processor plugins to enable. Separator is `:`.                                                                                    |
+| `--quiet`                        | Run in quiet mode.                                                                                                                |
+| `--section-filter <filter>`      | Filter configuration sections to output (`agent`, `global_tags`, `outputs`, `processors`, `aggregators` and `inputs`). Separator is `:`. |
+| `--sample-config`                | Print full sample configuration.                                                                                                  |
+| `--once`                         | Gather metrics once, write them, and exit.                                                                                        |
+| `--test`                         | Gather metrics once and print them.                                                                                               |
+| `--test-wait`                    | Number of seconds to wait for service inputs to complete in test or once mode.                                                    |
+| `--usage <plugin>`               | Print plugin usage (example: `telegraf --usage mysql`).                                                                           |
+| `--version`                      | Print Telegraf version.                                                                                                            |
+
+## Examples
+
+### Generate a Telegraf configuration file
+
+```sh
+telegraf config > telegraf.conf
+```
+
+### Generate configuration with only CPU input and InfluxDB output plugins defined
+
+```sh
+telegraf --input-filter cpu --output-filter influxdb config
+```
+
+### Run a single Telegraf configuration, outputting metrics to stdout
+
+```sh
+telegraf --config telegraf.conf --test
+```
+
+### Run Telegraf with all plugins defined in configuration file**
+
+```sh
+telegraf --config telegraf.conf
+```
+
+### Run Telegraf, enabling the CPU and memory input plugins and InfluxDB output plugin**
+
+```sh
+telegraf --config telegraf.conf --input-filter cpu:mem --output-filter influxdb
+```
+
+### Run Telegraf with pprof
+
+```sh
+telegraf --config telegraf.conf --pprof-addr localhost:6060
+```
diff --git a/content/telegraf/v1.22/configure_plugins/_index.md b/content/telegraf/v1.22/configure_plugins/_index.md
new file mode 100644
index 000000000..26c5c1371
--- /dev/null
+++ b/content/telegraf/v1.22/configure_plugins/_index.md
@@ -0,0 +1,13 @@
+---
+title: Configure plugins
+description:
+menu:
+  telegraf_1_22:
+
+     name: Configure plugins
+     weight: 50
+---
+
+Telegraf is a server-based agent for collecting and sending metrics and events from databases, systems, and IoT sensors.
+
+{{< children hlevel="h2" >}}
diff --git a/content/telegraf/v1.22/configure_plugins/aggregator_processor/_index.md b/content/telegraf/v1.22/configure_plugins/aggregator_processor/_index.md
new file mode 100644
index 000000000..766c666a5
--- /dev/null
+++ b/content/telegraf/v1.22/configure_plugins/aggregator_processor/_index.md
@@ -0,0 +1,58 @@
+---
+title: Transform data with aggregator and processor plugins
+description: |
+  Aggregator and processor plugins aggregate and process metrics.
+menu:
+  telegraf_1_22:
+     name: Aggregator and processor plugins
+     weight: 50
+     parent: Configure plugins
+---
+
+
+In addition to input plugins and output plugins, Telegraf includes aggregator and processor plugins, which are used to aggregate and process metrics as they pass through Telegraf.
+
+{{< diagram >}}
+  graph TD
+  Process[Process<br/> - transform<br/> - decorate<br/> - filter]
+  Aggregate[Aggregate<br/> - transform<br/> - decorate<br/> - filter]
+
+  CPU --> Process
+  Memory --> Process
+  MySQL --> Process
+  SNMP --> Process
+  Docker --> Process
+  Process --> Aggregate
+  Aggregate --> InfluxDB
+  Aggregate --> File
+  Aggregate --> Kafka
+
+style Process text-align:left
+style Aggregate text-align:left
+{{< /diagram >}}
+
+**Processor plugins** process metrics as they pass through and immediately emit
+results based on the values they process. For example, this could be printing
+all metrics or adding a tag to all metrics that pass through.
+
+**Aggregator plugins**, on the other hand, are a bit more complicated. Aggregators
+are typically for emitting new _aggregate_ metrics, such as a running mean,
+minimum, maximum, quantiles, or standard deviation. For this reason, all _aggregator_
+plugins are configured with a `period`. The `period` is the size of the window
+of metrics that each _aggregate_ represents. In other words, the emitted
+_aggregate_ metric will be the aggregated value of the past `period` seconds.
+Since many users will only care about their aggregates and not every single metric
+gathered, there is also a `drop_original` argument, which tells Telegraf to only
+emit the aggregates and not the original metrics.
+
+{{% note %}}
+#### Behavior of processors and aggregators when used together
+When using both aggregator and processor plugins in Telegraf v1.17, processor plugins
+process data and then pass it to aggregator plugins.
+After aggregator plugins aggregate the data, they pass it back to processor plugins.
+This can have unintended consequences, such as executing mathematical operations twice.
+_See [influxdata/telegraf#7993](https://github.com/influxdata/telegraf/issues/7993)._
+
+If using custom processor scripts, they must be idempotent (repeatable, without side-effects).
+For custom processes that are not idempotent, use [namepass or namedrop](/telegraf/v1.17/administration/configuration/#input-config-namepass-and-namedrop) to avoid issues when aggregated data is processed a second time.
+{{% /note %}}
diff --git a/content/telegraf/v1.22/configure_plugins/external_plugins/_index.md b/content/telegraf/v1.22/configure_plugins/external_plugins/_index.md
new file mode 100644
index 000000000..4244c5ca2
--- /dev/null
+++ b/content/telegraf/v1.22/configure_plugins/external_plugins/_index.md
@@ -0,0 +1,23 @@
+---
+title: Integrate with external plugins
+description: |
+  External plugins are external programs that are built outside of Telegraf that can run through an `execd` plugin.
+menu:
+  telegraf_1_22:
+     name: External plugins
+     weight: 50
+     parent: Configure plugins
+---
+
+[External plugins](https://github.com/influxdata/telegraf/blob/master/EXTERNAL_PLUGINS.md) are external programs that are built outside
+of Telegraf that can run through an `execd` plugin. These external plugins allow for
+more flexibility compared to internal Telegraf plugins. Benefits to using external plugins include:
+- Access to libraries not written in Go
+- Using licensed software (not available to open source community)
+- Including large dependencies that would otherwise bloat Telegraf
+- Using your external plugin immediately without waiting for the Telegraf team to publish
+- Easily convert plugins between internal and external using the [shim](https://github.com/influxdata/telegraf/blob/master/plugins/common/shim/README.md)
+
+
+
+{{< children hlevel="h2" >}}
diff --git a/content/telegraf/v1.22/configure_plugins/external_plugins/shim.md b/content/telegraf/v1.22/configure_plugins/external_plugins/shim.md
new file mode 100644
index 000000000..219674737
--- /dev/null
+++ b/content/telegraf/v1.22/configure_plugins/external_plugins/shim.md
@@ -0,0 +1,60 @@
+---
+title: Use the `execd` shim
+description:
+menu:
+  telegraf_1_22:
+  
+     name: Use the `execd` shim
+     weight: 50
+     parent: External plugins
+---
+
+The shim makes it easy to extract an internal input,
+processor, or output plugin from the main Telegraf repo out to a stand-alone repo. This allows anyone to build and run it as a separate app using one of the
+`execd` plugins:
+- [inputs.execd](https://github.com/influxdata/telegraf/blob/master/plugins/inputs/execd)
+- [processors.execd](https://github.com/influxdata/telegraf/blob/master//plugins/processors/execd)
+- [outputs.execd](https://github.com/influxdata/telegraf/blob/master/plugins/outputs/execd)
+
+## Extract a plugin using the shim wrapper
+
+1. Move the project to an external repo. We recommend preserving the path
+  structure: for example, if your plugin was located at
+  `plugins/inputs/cpu` in the Telegraf repo, move it to `plugins/inputs/cpu`
+  in the new repo.
+2. Copy [main.go](https://github.com/influxdata/telegraf/blob/master/plugins/common/shim/example/cmd/main.go) into your project under the `cmd` folder.
+  This serves as the entry point to the plugin when run as a stand-alone program.
+  {{% note %}}
+  The shim isn't designed to run multiple plugins at the same time, so include only one plugin per repo.
+  {{% /note %}}
+3. Edit the `main.go` file to import your plugin. For example,`_ "github.com/me/my-plugin-telegraf/plugins/inputs/cpu"`. See an example of where to edit `main.go` [here](https://github.com/influxdata/telegraf/blob/7de9c5ff279e10edf7fe3fdd596f3b33902c912b/plugins/common/shim/example/cmd/main.go#L9).
+4. Add a [plugin.conf](https://github.com/influxdata/telegraf/blob/master/plugins/common/shim/example/cmd/plugin.conf) for configuration
+  specific to your plugin.
+  {{% note %}}
+  This config file must be separate from the rest of the config for Telegraf, and must not be in a shared directory with other Telegraf configs.
+  {{% /note %}}
+
+## Test and run your plugin
+
+1. Build the `cmd/main.go` using the following command with your plugin name: `go build -o plugin-name cmd/main.go`
+1. Test the binary:
+2. If you're building a processor or output, first feed valid metrics in on `STDIN`. Skip this step if you're building an input.
+3. Test out the binary by running it (for example, `./project-name -config plugin.conf`).
+  Metrics will be written to `STDOUT`. You might need to hit enter or wait for your poll duration to elapse to see data.
+4. Press `Ctrl-C` to end your test.
+5. Configure Telegraf to call your new plugin binary. For an input, this would
+  look something like:
+
+```toml
+[[inputs.execd]]
+  command = ["/path/to/rand", "-config", "/path/to/plugin.conf"]
+  signal = "none"
+```
+
+Refer to the `execd` plugin documentation for more information.
+
+## Publish your plugin
+
+Publishing your plugin to GitHub and open a Pull Request
+back to the Telegraf repo letting us know about the availability of your
+[external plugin](https://github.com/influxdata/telegraf/blob/master/EXTERNAL_PLUGINS.md).
diff --git a/content/telegraf/v1.22/configure_plugins/external_plugins/write_external_plugin.md b/content/telegraf/v1.22/configure_plugins/external_plugins/write_external_plugin.md
new file mode 100644
index 000000000..104cb7665
--- /dev/null
+++ b/content/telegraf/v1.22/configure_plugins/external_plugins/write_external_plugin.md
@@ -0,0 +1,31 @@
+---
+title: Write an external plugin
+description:
+menu:
+  telegraf_1_22:
+
+     name: Write an external plugin
+     weight: 50
+     parent: External plugins
+---
+Set up your plugin to use it with `execd`.
+
+{{% note %}}
+For listed [external plugins](/EXTERNAL_PLUGINS.md), the author of the external plugin is also responsible for the maintenance
+and feature development of external plugins.
+{{% /note %}}
+
+1. Write your Telegraf plugin. Follow InfluxData's best practices:
+   - [Input plugins](https://github.com/influxdata/telegraf/blob/master/docs/INPUTS.md)
+   - [Processor plugins](https://github.com/influxdata/telegraf/blob/master/docs/PROCESSORS.md)
+   - [Aggregator plugins](https://github.com/influxdata/telegraf/blob/master/docs/AGGREGATORS.md)
+   - [Output plugins](https://github.com/influxdata/telegraf/blob/master/docs/OUTPUTS.md)
+2. If your plugin is written in Go, follow the steps for the [Execd Go Shim](/{{< latest "telegraf" >}}/configure_plugins/external_plugins/shim).
+3. Add usage and development instructions in the homepage of your repository for running your plugin with its respective `execd` plugin. Refer to [openvpn](https://github.com/danielnelson/telegraf-execd-openvpn#usage) and [awsalarms](https://github.com/vipinvkmenon/awsalarms#installation) for examples.
+Include the following steps:
+     - How to download the release package for your platform or how to clone the binary for your external plugin
+     - Commands to build your binary
+     - Location to edit your `telegraf.conf`
+     - Configuration to run your external plugin with [inputs.execd](https://github.com/influxdata/telegraf/blob/master/plugins/inputs/execd),
+     [processors.execd](/plugins/processors/execd) or [outputs.execd](https://github.com/influxdata/telegraf/blob/master/plugins/outputs/execd)
+4. Submit your plugin by opening a PR to add your external plugin to the [/EXTERNAL_PLUGINS.md](https://github.com/influxdata/telegraf/blob/master/EXTERNAL_PLUGINS.md) list. Include the plugin name, a link to the plugin repository and a short description of the plugin.
diff --git a/content/telegraf/v1.22/configure_plugins/input_plugins/_index.md b/content/telegraf/v1.22/configure_plugins/input_plugins/_index.md
new file mode 100644
index 000000000..99e5cc643
--- /dev/null
+++ b/content/telegraf/v1.22/configure_plugins/input_plugins/_index.md
@@ -0,0 +1,14 @@
+---
+title: Collect data with input plugins
+description: |
+  Collect data from a variety of sources with Telegraf input plugins.
+menu:
+  telegraf_1_22:
+
+     name: Input plugins
+     weight: 10
+     parent: Configure plugins
+---
+For a complete list of input plugins and links to their detailed configuration options, see [input plugins](/{{< latest "telegraf" >}}/plugins/inputs/).
+
+In addition to plugin-specific data formats, Telegraf supports a set of [common data formats](/{{< latest "telegraf" >}}/data_formats/input/) available when configuring many of the Telegraf input plugins.
diff --git a/content/telegraf/v1.22/configure_plugins/input_plugins/using_http.md b/content/telegraf/v1.22/configure_plugins/input_plugins/using_http.md
new file mode 100644
index 000000000..cb9b8f2ea
--- /dev/null
+++ b/content/telegraf/v1.22/configure_plugins/input_plugins/using_http.md
@@ -0,0 +1,106 @@
+---
+title: Using the HTTP input plugin with Citi Bike data
+description: Collect live metrics on Citi Bike stations in New York City with the HTTP input plugin.
+menu:
+  telegraf_1_22:
+
+    name: Using the HTTP plugin
+    weight: 30
+    parent: Input plugins
+---
+
+This example walks through using the Telegraf HTTP input plugin to collect live metrics on Citi Bike stations in New York City. Live station data is available in JSON format directly from [Citi Bike](https://ride.citibikenyc.com/system-data).
+
+For the following example to work, configure [`influxdb_v2` output plugin](/telegraf/v1.22/plugins/#output-influxdb_v2). This plugin is what allows Telegraf to write the metrics to InfluxDB.
+
+## Configure the HTTP Input plugin in your Telegraf configuration file
+
+To retrieve data from the Citi Bike URL endpoint, enable the `inputs.http` input plugin in your Telegraf configuration file.
+
+Specify the following options:
+
+### `urls`
+One or more URLs to read metrics from. For this example,  use `https://gbfs.citibikenyc.com/gbfs/en/station_status.json`.
+
+### `data_format`
+The format of the data in the HTTP endpoints that Telegraf will ingest. For this example, use JSON.
+
+
+## Add parser information to your Telegraf configuration
+
+Specify the following JSON-specific options. In this example, we use the objects subtable to gather
+data from [JSON Objects](https://www.w3schools.com/js/js_json_objects.asp).
+
+### JSON
+
+#### `path`
+To parse a JSON object, set the `path` option with a [GJSON](https://github.com/tidwall/gjson) path. The result of the query should contain a JSON object or an array of objects. The [GJSON playground](https://gjson.dev/) is a very helpful tool in checking your query.
+
+#### `tags`
+List of one or more JSON keys that should be added as tags. For this example, we'll use the tag key `station_id`.
+
+#### `timestamp_key`
+Key from the JSON file that creates the timestamp metric. In this case, we want to use the time that station data was last reported, or the `last_reported`. If you don't specify a key, the time that Telegraf reads the data becomes the timestamp.
+
+#### `timestamp_format`
+The format used to interpret the designated `timestamp_key`. The `last_reported` time in this example is reported in unix format.
+
+#### Example configuration
+
+  ```toml
+[[inputs.http]]
+  # URL for NYC's Citi Bike station data in JSON format
+  urls = ["https://gbfs.citibikenyc.com/gbfs/en/station_status.json"]
+
+  # Overwrite measurement name from default `http` to `citibikenyc`
+  name_override = "citibike"
+
+  # Exclude url and host items from tags
+  tagexclude = ["url", "host"]
+
+  # Data from HTTP in JSON format
+  data_format = "json_v2"
+
+
+        # Add a subtable to use the `json_v2` parser
+        [[inputs.http.json_v2]]
+
+            # Add an object subtable for to parse a JSON object
+            [[inputs.http.json_v2.object]]
+
+                # Parse data in `data.stations` path only
+                path = "data.stations"
+
+                #Set station metadata as tags
+                tags = ["station_id"]
+
+                # Latest station information reported at `last_reported`
+                timestamp_key = "last_reported"
+
+                # Time is reported in unix timestamp format
+                timestamp_format = "unix"
+  ```
+
+
+
+## Start Telegraf and verify data appears
+
+[Start the Telegraf service](/telegraf/v1.22/get_started/#start-telegraf).
+
+To test that the data is being sent to InfluxDB, run the following (replacing `telegraf.conf` with the path to your configuration file):
+
+```
+telegraf -config ~/telegraf.conf -test
+```
+
+This command should return line protocol that looks similar to the following:
+
+```
+citibike,station_id=4703 eightd_has_available_keys=false,is_installed=1,is_renting=1,is_returning=1,legacy_id="4703",num_bikes_available=6,num_bikes_disabled=2,num_docks_available=26,num_docks_disabled=0,num_ebikes_available=0,station_status="active" 1641505084000000000
+citibike,station_id=4704 eightd_has_available_keys=false,is_installed=1,is_renting=1,is_returning=1,legacy_id="4704",num_bikes_available=10,num_bikes_disabled=2,num_docks_available=36,num_docks_disabled=0,num_ebikes_available=0,station_status="active" 1641505084000000000
+citibike,station_id=4711 eightd_has_available_keys=false,is_installed=1,is_renting=1,is_returning=1,legacy_id="4711",num_bikes_available=9,num_bikes_disabled=0,num_docks_available=36,num_docks_disabled=0,num_ebikes_available=1,station_status="active" 1641505084000000000
+```
+
+Now, you can explore and query the Citi Bike data in InfluxDB. The example below is an Flux query and visualization showing the number of available bikes over the past 15 minutes.
+
+![Citi Bike visualization](/img/telegraf/new-citibike_query.png)
diff --git a/content/telegraf/v1.22/configure_plugins/output_plugins/_index.md b/content/telegraf/v1.22/configure_plugins/output_plugins/_index.md
new file mode 100644
index 000000000..3272ce484
--- /dev/null
+++ b/content/telegraf/v1.22/configure_plugins/output_plugins/_index.md
@@ -0,0 +1,16 @@
+---
+title: Write data with output plugins
+description: |
+  Output plugins define where Telegraf will deliver the collected metrics. 
+menu:
+  telegraf_1_22:
+
+     name: Output plugins
+     weight: 20
+     parent: Configure plugins
+---
+Output plugins define where Telegraf will deliver the collected metrics. Send metrics to InfluxDB or to a variety of other datastores, services, and message queues, including Graphite, OpenTSDB, Datadog, Librato, Kafka, MQTT, and NSQ.
+
+For a complete list of output plugins and links to their detailed configuration options, see [output plugins](/{{< latest "telegraf" >}}/plugins/outputs/).
+
+In addition to plugin-specific data formats, Telegraf supports a set of [common data formats](/{{< latest "telegraf" >}}/data_formats/output/) available when configuring many of the Telegraf output plugins.
diff --git a/content/telegraf/v1.22/configure_plugins/troubleshoot.md b/content/telegraf/v1.22/configure_plugins/troubleshoot.md
new file mode 100644
index 000000000..50b69c04b
--- /dev/null
+++ b/content/telegraf/v1.22/configure_plugins/troubleshoot.md
@@ -0,0 +1,51 @@
+---
+title: Troubleshoot Telegraf
+description: Resolve common issues with Telegraf.
+menu:
+  telegraf_1_22:
+
+    name: Troubleshoot
+    Parent: Configure plugins
+    weight: 79
+---
+
+## Validate your Telegraf configuration with `--test`
+
+Run a single telegraf collection, outputting metrics to stdout:
+`telegraf --config telegraf.conf --test`
+
+## Use the `--once` option to single-shot execute
+
+Once tested, run `telegraf --config telegraf.conf --once` to perform a single-shot execution of all configured plugins. This sends output to partner systems specified in the `telegraf.conf` rather than writing to `stdout`.
+
+## Add `outputs.file` to read to a file or STDOUT
+
+The following step might be helpful if:
+- You're encountering issues in your output and trying to determine if it’s an issue with your configuration or connection.
+-  `-test` outputs metrics to stdout as expected and your input, parsers, processors, and aggregators are configured correctly. Note that if it's a listener plugin, `-test` wouldn't output any metrics right away.
+
+Add the `file` output plugin with the metrics reporting to STDOUT or to a file.
+```toml
+[[outputs.file]]
+  files = ["stdout"]
+```
+
+## Set `debug = true` in your settings
+
+When you set `debug = true` in global settings, Telegraf runs with debug log messages.
+
+```
+2021-06-28T19:18:00Z I! Starting Telegraf 1.19.0
+2021-06-28T19:18:00Z I! Loaded inputs: cpu disk diskio mem net processes swap system
+2021-06-28T19:18:00Z I! Loaded aggregators:
+2021-06-28T19:18:00Z I! Loaded processors:
+2021-06-28T19:18:00Z I! Loaded outputs: influxdb_v2
+2021-06-28T19:18:00Z I! Tags enabled: host=MBP15-INFLUX.local
+2021-06-28T19:18:00Z I! [agent] Config: Interval:10s, Quiet:false, Hostname:"MBP15-INFLUX.local", Flush Interval:30s
+2021-06-28T19:18:00Z D! [agent] Initializing plugins
+2021-06-28T19:18:00Z D! [agent] Connecting outputs
+2021-06-28T19:18:00Z D! [agent] Attempting connection to [outputs.influxdb_v2]
+2021-06-28T19:18:00Z D! [agent] Successfully connected to outputs.influxdb_v2
+2021
+-06-28T19:18:00Z D! [agent] Starting service inputs
+```
diff --git a/content/telegraf/v1.22/contribute.md b/content/telegraf/v1.22/contribute.md
new file mode 100644
index 000000000..fba066270
--- /dev/null
+++ b/content/telegraf/v1.22/contribute.md
@@ -0,0 +1,26 @@
+---
+title: Contribute to Telegraf
+description:
+menu:
+  telegraf_1_22_ref:
+    name: Contribute to Telegraf
+    weight: 80
+---
+
+To contribute to the Telegraf project, complete the following steps:
+
+1. [Sign the InfluxData Contributor License Agreement (CLA)](#sign-influxdata-contributor-license-agreement-cla).
+2. [Review contribution guidelines](#review-contribution-guidelines).
+3. [Review the Telegraf open source license](#review-open-source-license).
+
+## Sign InfluxData Contributor License Agreement (CLA)
+
+Before contributing to the InfluxDB OSS project, you must complete and sign the [InfluxData Contributor License Agreement (CLA)](https://www.influxdata.com/legal/cla/), available on the InfluxData website.
+
+## Review contribution guidelines
+
+To learn how you can contribute to the Telegraf project, see our [Contributing guidelines](https://github.com/influxdata/telegraf/blob/master/CONTRIBUTING.md) in the GitHub repository.
+
+## Review open source license
+
+See information about our [open source MIT license for Telegraf](https://github.com/influxdata/telegraf/blob/master/LICENSE) in GitHub.
diff --git a/content/telegraf/v1.22/data_formats/_index.md b/content/telegraf/v1.22/data_formats/_index.md
new file mode 100644
index 000000000..6dbc505b8
--- /dev/null
+++ b/content/telegraf/v1.22/data_formats/_index.md
@@ -0,0 +1,16 @@
+---
+title: Telegraf data formats
+description: Telegraf supports input data formats and output data formats for converting input and output data.
+menu:
+  telegraf_1_22_ref:
+
+     name: Data formats
+
+     weight: 50
+---
+
+This section covers the input data formats and output data formats used in the Telegraf plugin-driven server agent component of the InfluxData time series platform.
+
+{{< children hlevel="h2" >}}
+
+<!-- add table: https://github.com/influxdata/docs-v2/issues/2360 !-->
diff --git a/content/telegraf/v1.22/data_formats/input/_index.md b/content/telegraf/v1.22/data_formats/input/_index.md
new file mode 100644
index 000000000..9dc10f513
--- /dev/null
+++ b/content/telegraf/v1.22/data_formats/input/_index.md
@@ -0,0 +1,37 @@
+---
+title: Telegraf input data formats
+description: Telegraf supports parsing input data formats into Telegraf metrics.
+menu:
+  telegraf_1_22_ref:
+
+    name: Input data formats
+    weight: 1
+    parent: Data formats
+---
+
+Telegraf contains many general purpose plugins that support parsing input data
+using a configurable parser into [metrics][].  This allows, for example, the
+`kafka_consumer` input plugin to process messages in either InfluxDB Line
+Protocol or in JSON format. Telegraf supports the following input data formats:
+
+{{< children >}}
+
+Any input plugin containing the `data_format` option can use it to select the
+desired parser:
+
+```toml
+[[inputs.exec]]
+  ## Commands array
+  commands = ["/tmp/test.sh", "/usr/bin/mycollector --foo=bar"]
+
+  ## measurement name suffix (for separating different commands)
+  name_suffix = "_mycollector"
+
+  ## Data format to consume.
+  ## Each data format has its own unique set of configuration options, read
+  ## more about them here:
+  ## https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md
+  data_format = "json_v2"
+```
+
+[metrics]: /telegraf/v1.15/concepts/metrics/
diff --git a/content/telegraf/v1.22/data_formats/input/collectd.md b/content/telegraf/v1.22/data_formats/input/collectd.md
new file mode 100644
index 000000000..745bcf1ac
--- /dev/null
+++ b/content/telegraf/v1.22/data_formats/input/collectd.md
@@ -0,0 +1,49 @@
+---
+title: Collectd input data format
+description: Use the `collectd` input data format to parse the collectd network binary protocol to create tags for host, instance, type, and type instance.
+menu:
+  telegraf_1_22_ref:
+
+    name: collectd
+    weight: 10
+    parent: Input data formats
+---
+
+The collectd input data format parses the collectd network binary protocol to create tags for host, instance, type, and type instance.  All collectd values are added as float64 fields.
+
+For more information, see [binary protocol](https://collectd.org/wiki/index.php/Binary_protocol) in the collectd Wiki.
+
+You can control the cryptographic settings with parser options.  
+Create an authentication file and set `collectd_auth_file` to the path of the file, then set the desired security level in `collectd_security_level`.
+
+For more information, including client setup, see
+[Cryptographic setup](https://collectd.org/wiki/index.php/Networking_introduction#Cryptographic_setup) in the collectd Wiki.
+
+You can also change the path to the typesdb or add additional typesdb using
+`collectd_typesdb`.
+
+## Configuration
+
+```toml
+[[inputs.file]]
+  files = ["example"]
+
+  ## Data format to consume.
+  ## Each data format has its own unique set of configuration options, read
+  ## more about them here:
+  ##   https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md
+  data_format = "collectd"
+
+  ## Authentication file for cryptographic security levels
+  collectd_auth_file = "/etc/collectd/auth_file"
+  ## One of none (default), sign, or encrypt
+  collectd_security_level = "encrypt"
+  ## Path of to TypesDB specifications
+  collectd_typesdb = ["/usr/share/collectd/types.db"]
+
+  ## Multi-value plugins can be handled two ways.
+  ## "split" will parse and store the multi-value plugin data into separate measurements
+  ## "join" will parse and store the multi-value plugin as a single multi-value measurement.
+  ## "split" is the default behavior for backward compatability with previous versions of influxdb.
+  collectd_parse_multivalue = "split"
+```
diff --git a/content/telegraf/v1.22/data_formats/input/csv.md b/content/telegraf/v1.22/data_formats/input/csv.md
new file mode 100644
index 000000000..e2c00f219
--- /dev/null
+++ b/content/telegraf/v1.22/data_formats/input/csv.md
@@ -0,0 +1,112 @@
+---
+title: CSV input data format
+description: Use the `csv` input data format to parse a document containing comma-separated values into Telegraf metrics.
+menu:
+  telegraf_1_22_ref:
+
+    name: CSV
+    weight: 20
+    parent: Input data formats
+---
+
+The CSV input data format parses documents containing comma-separated values into Telegraf metrics.
+
+## Configuration
+
+```toml
+[[inputs.file]]
+  files = ["example"]
+
+  ## Data format to consume.
+  ## Each data format has its own unique set of configuration options, read
+  ## more about them here:
+  ##   https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md
+  data_format = "csv"
+
+  ## Indicates how many rows to treat as a header. By default, the parser assumes
+  ## there is no header and will parse the first row as data. If set to anything more
+  ## than 1, column names will be concatenated with the name listed in the next header row.
+  ## If `csv_column_names` is specified, the column names in header will be overridden.
+  csv_header_row_count = 0
+
+  ## For assigning custom names to columns
+  ## If this is specified, all columns should have a name
+  ## Unnamed columns will be ignored by the parser.
+  ## If `csv_header_row_count` is set to 0, this config must be used
+  csv_column_names = []
+
+  ## Indicates the number of rows to skip before looking for header information.
+  csv_skip_rows = 0
+
+  ## Indicates the number of columns to skip before looking for data to parse.
+  ## These columns will be skipped in the header as well.
+  csv_skip_columns = 0
+
+  ## The seperator between csv fields
+  ## By default, the parser assumes a comma (",")
+  csv_delimiter = ","
+
+  ## The character reserved for marking a row as a comment row
+  ## Commented rows are skipped and not parsed
+  csv_comment = ""
+
+  ## If set to true, the parser will remove leading whitespace from fields
+  ## By default, this is false
+  csv_trim_space = false
+
+  ## Columns listed here will be added as tags. Any other columns
+  ## will be added as fields.
+  csv_tag_columns = []
+
+  ## The column to extract the name of the metric from
+  csv_measurement_column = ""
+
+  ## The column to extract time information for the metric
+  ## `csv_timestamp_format` must be specified if this is used
+  csv_timestamp_column = ""
+
+  ## The format of time data extracted from `csv_timestamp_column`
+  ## this must be specified if `csv_timestamp_column` is specified
+  csv_timestamp_format = ""
+  ```
+### csv_timestamp_column, csv_timestamp_format
+
+By default the current time will be used for all created metrics, to set the
+time using the JSON document you can use the `csv_timestamp_column` and
+`csv_timestamp_format` options together to set the time to a value in the parsed
+document.
+
+The `csv_timestamp_column` option specifies the column name containing the
+time value and `csv_timestamp_format` must be set to a Go "reference time"
+which is defined to be the specific time: `Mon Jan 2 15:04:05 MST 2006`.
+
+Consult the Go [time][time parse] package for details and additional examples
+on how to set the time format.
+
+## Metrics
+
+One metric is created for each row with the columns added as fields.  The type
+of the field is automatically determined based on the contents of the value.
+
+## Examples
+
+Config:
+```
+[[inputs.file]]
+  files = ["example"]
+  data_format = "csv"
+  csv_header_row_count = 1
+  csv_timestamp_column = "time"
+  csv_timestamp_format = "2006-01-02T15:04:05Z07:00"
+```
+
+Input:
+```
+measurement,cpu,time_user,time_system,time_idle,time
+cpu,cpu0,42,42,42,2018-09-13T13:03:28Z
+```
+
+Output:
+```
+cpu cpu=cpu0,time_user=42,time_system=42,time_idle=42 1536869008000000000
+```
diff --git a/content/telegraf/v1.22/data_formats/input/dropwizard.md b/content/telegraf/v1.22/data_formats/input/dropwizard.md
new file mode 100644
index 000000000..74e39b81e
--- /dev/null
+++ b/content/telegraf/v1.22/data_formats/input/dropwizard.md
@@ -0,0 +1,180 @@
+---
+title: Dropwizard input data format
+description: Use the `dropwizard` input data format to parse Dropwizard JSON representations into Telegraf metrics.
+menu:
+  telegraf_1_22_ref:
+
+    name: Dropwizard
+    weight: 30
+    parent: Input data formats
+---
+
+The `dropwizard` data format can parse a [Dropwizard JSON representation][dropwizard] representation of a single metrics registry. By default, tags are parsed from metric names as if they were actual InfluxDB Line Protocol keys (`measurement<,tag_set>`) which can be overridden using custom [template patterns][templates]. All field value types are supported, including `string`, `number` and `boolean`.
+
+[templates]: /telegraf/v1.15/data_formats/template-patterns/
+[dropwizard]: http://metrics.dropwizard.io/3.1.0/manual/json/
+
+## Configuration
+
+```toml
+[[inputs.file]]
+  files = ["example"]
+
+  ## Data format to consume.
+  ## Each data format has its own unique set of configuration options, read
+  ## more about them here:
+  ## https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md
+  data_format = "dropwizard"
+
+  ## Used by the templating engine to join matched values when cardinality is > 1
+  separator = "_"
+
+  ## Each template line requires a template pattern. It can have an optional
+  ## filter before the template and separated by spaces. It can also have optional extra
+  ## tags following the template. Multiple tags should be separated by commas and no spaces
+  ## similar to the line protocol format. There can be only one default template.
+  ## Templates support below format:
+  ## 1. filter + template
+  ## 2. filter + template + extra tag(s)
+  ## 3. filter + template with field key
+  ## 4. default template
+  ## By providing an empty template array, templating is disabled and measurements are parsed as influxdb line protocol keys (measurement<,tag_set>)
+  templates = []
+
+  ## You may use an appropriate [gjson path](https://github.com/tidwall/gjson#path-syntax)
+  ## to locate the metric registry within the JSON document
+  # dropwizard_metric_registry_path = "metrics"
+
+  ## You may use an appropriate [gjson path](https://github.com/tidwall/gjson#path-syntax)
+  ## to locate the default time of the measurements within the JSON document
+  # dropwizard_time_path = "time"
+  # dropwizard_time_format = "2006-01-02T15:04:05Z07:00"
+
+  ## You may use an appropriate [gjson path](https://github.com/tidwall/gjson#path-syntax)
+  ## to locate the tags map within the JSON document
+  # dropwizard_tags_path = "tags"
+
+  ## You may even use tag paths per tag
+  # [inputs.exec.dropwizard_tag_paths]
+  #   tag1 = "tags.tag1"
+  #   tag2 = "tags.tag2"
+```
+
+
+## Examples
+
+A typical JSON of a dropwizard metric registry:
+
+```json
+{
+	"version": "3.0.0",
+	"counters" : {
+		"measurement,tag1=green" : {
+			"count" : 1
+		}
+	},
+	"meters" : {
+		"measurement" : {
+			"count" : 1,
+			"m15_rate" : 1.0,
+			"m1_rate" : 1.0,
+			"m5_rate" : 1.0,
+			"mean_rate" : 1.0,
+			"units" : "events/second"
+		}
+	},
+	"gauges" : {
+		"measurement" : {
+			"value" : 1
+		}
+	},
+	"histograms" : {
+		"measurement" : {
+			"count" : 1,
+			"max" : 1.0,
+			"mean" : 1.0,
+			"min" : 1.0,
+			"p50" : 1.0,
+			"p75" : 1.0,
+			"p95" : 1.0,
+			"p98" : 1.0,
+			"p99" : 1.0,
+			"p999" : 1.0,
+			"stddev" : 1.0
+		}
+	},
+	"timers" : {
+		"measurement" : {
+			"count" : 1,
+			"max" : 1.0,
+			"mean" : 1.0,
+			"min" : 1.0,
+			"p50" : 1.0,
+			"p75" : 1.0,
+			"p95" : 1.0,
+			"p98" : 1.0,
+			"p99" : 1.0,
+			"p999" : 1.0,
+			"stddev" : 1.0,
+			"m15_rate" : 1.0,
+			"m1_rate" : 1.0,
+			"m5_rate" : 1.0,
+			"mean_rate" : 1.0,
+			"duration_units" : "seconds",
+			"rate_units" : "calls/second"
+		}
+	}
+}
+```
+
+Would get translated into 4 different measurements:
+
+```
+measurement,metric_type=counter,tag1=green count=1
+measurement,metric_type=meter count=1,m15_rate=1.0,m1_rate=1.0,m5_rate=1.0,mean_rate=1.0
+measurement,metric_type=gauge value=1
+measurement,metric_type=histogram count=1,max=1.0,mean=1.0,min=1.0,p50=1.0,p75=1.0,p95=1.0,p98=1.0,p99=1.0,p999=1.0
+measurement,metric_type=timer count=1,max=1.0,mean=1.0,min=1.0,p50=1.0,p75=1.0,p95=1.0,p98=1.0,p99=1.0,p999=1.0,stddev=1.0,m15_rate=1.0,m1_rate=1.0,m5_rate=1.0,mean_rate=1.0
+```
+
+You may also parse a dropwizard registry from any JSON document which contains a dropwizard registry in some inner field.
+Eg. to parse the following JSON document:
+
+```json
+{
+	"time" : "2017-02-22T14:33:03.662+02:00",
+	"tags" : {
+		"tag1" : "green",
+		"tag2" : "yellow"
+	},
+	"metrics" : {
+		"counters" : 	{
+			"measurement" : {
+				"count" : 1
+			}
+		},
+		"meters" : {},
+		"gauges" : {},
+		"histograms" : {},
+		"timers" : {}
+	}
+}
+```
+and translate it into:
+
+```
+measurement,metric_type=counter,tag1=green,tag2=yellow count=1 1487766783662000000
+```
+
+you simply need to use the following additional configuration properties:
+
+```toml
+dropwizard_metric_registry_path = "metrics"
+dropwizard_time_path = "time"
+dropwizard_time_format = "2006-01-02T15:04:05Z07:00"
+dropwizard_tags_path = "tags"
+## tag paths per tag are supported too, eg.
+#[inputs.yourinput.dropwizard_tag_paths]
+#  tag1 = "tags.tag1"
+#  tag2 = "tags.tag2"
+```
diff --git a/content/telegraf/v1.22/data_formats/input/graphite.md b/content/telegraf/v1.22/data_formats/input/graphite.md
new file mode 100644
index 000000000..e1cf5f9e9
--- /dev/null
+++ b/content/telegraf/v1.22/data_formats/input/graphite.md
@@ -0,0 +1,56 @@
+---
+title: Graphite input data format
+description: Use the Graphite data format to translate Graphite dot buckets directly into Telegraf measurement names, with a single value field, and without any tags.
+menu:
+  telegraf_1_22_ref:
+
+    name: Graphite
+    weight: 40
+    parent: Input data formats
+---
+
+The Graphite data format translates Graphite *dot* buckets directly into
+Telegraf measurement names, with a single value field, and without any tags.
+By default, the separator is left as `.`, but this can be changed using the
+`separator` argument. For more advanced options, Telegraf supports specifying
+[templates](#templates) to translate graphite buckets into Telegraf metrics.
+
+## Configuration
+
+```toml
+[[inputs.exec]]
+  ## Commands array
+  commands = ["/tmp/test.sh", "/usr/bin/mycollector --foo=bar"]
+
+  ## measurement name suffix (for separating different commands)
+  name_suffix = "_mycollector"
+
+  ## Data format to consume.
+  ## Each data format has its own unique set of configuration options, read
+  ## more about them here:
+  ## https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md
+  data_format = "graphite"
+
+  ## This string will be used to join the matched values.
+  separator = "_"
+
+  ## Each template line requires a template pattern. It can have an optional
+  ## filter before the template and separated by spaces. It can also have optional extra
+  ## tags following the template. Multiple tags should be separated by commas and no spaces
+  ## similar to the line protocol format. There can be only one default template.
+  ## Templates support below format:
+  ## 1. filter + template
+  ## 2. filter + template + extra tag(s)
+  ## 3. filter + template with field key
+  ## 4. default template
+  templates = [
+    "*.app env.service.resource.measurement",
+    "stats.* .host.measurement* region=eu-east,agent=sensu",
+    "stats2.* .host.measurement.field",
+    "measurement*"
+  ]
+```
+
+### templates
+
+For information on creating templates, see [Template patterns](/telegraf/v1.15/data_formats/template-patterns/).
diff --git a/content/telegraf/v1.22/data_formats/input/grok.md b/content/telegraf/v1.22/data_formats/input/grok.md
new file mode 100644
index 000000000..45bb90863
--- /dev/null
+++ b/content/telegraf/v1.22/data_formats/input/grok.md
@@ -0,0 +1,227 @@
+---
+title: Grok input data format
+description: Use the grok data format to parse line-delimited data using a regular expression-like language.
+menu:
+  telegraf_1_22_ref:
+
+    name: Grok
+    weight: 40
+    parent: Input data formats
+---
+
+The grok data format parses line delimited data using a regular expression-like
+language.
+
+If you need to become familiar with grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics)
+in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok"
+patterns, using the format:
+
+```
+%{<capture_syntax>[:<semantic_name>][:<modifier>]}
+```
+
+The `capture_syntax` defines the grok pattern that is used to parse the input
+line and the `semantic_name` is used to name the field or tag.  The extension
+`modifier` controls the data type that the parsed item is converted to or
+other special handling.
+
+By default, all named captures are converted into string fields.
+Timestamp modifiers can be used to convert captures to the timestamp of the
+parsed metric.  If no timestamp is parsed the metric will be created using the
+current time.
+
+You must capture at least one field per line.
+
+- Available modifiers:
+  - string   (default if nothing is specified)
+  - int
+  - float
+  - duration (ie, 5.23ms gets converted to int nanoseconds)
+  - tag      (converts the field into a tag)
+  - drop     (drops the field completely)
+  - measurement (use the matched text as the measurement name)
+- Timestamp modifiers:
+  - ts               (This will auto-learn the timestamp format)
+  - ts-ansic         ("Mon Jan _2 15:04:05 2006")
+  - ts-unix          ("Mon Jan _2 15:04:05 MST 2006")
+  - ts-ruby          ("Mon Jan 02 15:04:05 -0700 2006")
+  - ts-rfc822        ("02 Jan 06 15:04 MST")
+  - ts-rfc822z       ("02 Jan 06 15:04 -0700")
+  - ts-rfc850        ("Monday, 02-Jan-06 15:04:05 MST")
+  - ts-rfc1123       ("Mon, 02 Jan 2006 15:04:05 MST")
+  - ts-rfc1123z      ("Mon, 02 Jan 2006 15:04:05 -0700")
+  - ts-rfc3339       ("2006-01-02T15:04:05Z07:00")
+  - ts-rfc3339nano   ("2006-01-02T15:04:05.999999999Z07:00")
+  - ts-httpd         ("02/Jan/2006:15:04:05 -0700")
+  - ts-epoch         (seconds since unix epoch, may contain decimal)
+  - ts-epochnano     (nanoseconds since unix epoch)
+  - ts-syslog        ("Jan 02 15:04:05", parsed time is set to the current year)
+  - ts-"CUSTOM"
+
+CUSTOM time layouts must be within quotes and be the representation of the
+"reference time", which is `Mon Jan 2 15:04:05 -0700 MST 2006`.
+To match a comma decimal point you can use a period.  For example `%{TIMESTAMP:timestamp:ts-"2006-01-02 15:04:05.000"}` can be used to match `"2018-01-02 15:04:05,000"`
+To match a comma decimal point you can use a period in the pattern string.
+See https://golang.org/pkg/time/#Parse for more details.
+
+Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go),
+as well as support for most of
+[logstash's builtin patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns.
+_Golang regular expressions do not support lookahead or lookbehind.
+logstash patterns that depend on these are not supported._
+
+If you need help building patterns to match your logs, the
+[Grok Debugger application](https://grokdebug.herokuapp.com) might be helpful.
+
+## Configuration
+
+```toml
+[[inputs.file]]
+  ## Files to parse each interval.
+  ## These accept standard unix glob matching rules, but with the addition of
+  ## ** as a "super asterisk". ie:
+  ##   /var/log/**.log     -> recursively find all .log files in /var/log
+  ##   /var/log/*/*.log    -> find all .log files with a parent dir in /var/log
+  ##   /var/log/apache.log -> only tail the apache log file
+  files = ["/var/log/apache/access.log"]
+
+  ## The dataformat to be read from files
+  ## Each data format has its own unique set of configuration options, read
+  ## more about them here:
+  ## https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md
+  data_format = "grok"
+
+  ## This is a list of patterns to check the given log file(s) for.
+  ## Note that adding patterns here increases processing time. The most
+  ## efficient configuration is to have one pattern.
+  ## Other common built-in patterns are:
+  ##   %{COMMON_LOG_FORMAT}   (plain apache & nginx access logs)
+  ##   %{COMBINED_LOG_FORMAT} (access logs + referrer & agent)
+  grok_patterns = ["%{COMBINED_LOG_FORMAT}"]
+
+  ## Full path(s) to custom pattern files.
+  grok_custom_pattern_files = []
+
+  ## Custom patterns can also be defined here. Put one pattern per line.
+  grok_custom_patterns = '''
+  '''
+
+  ## Timezone allows you to provide an override for timestamps that
+  ## don't already include an offset
+  ## e.g. 04/06/2016 12:41:45 data one two 5.43µs
+  ##
+  ## Default: "" which renders UTC
+  ## Options are as follows:
+  ##   1. Local             -- interpret based on machine localtime
+  ##   2. "Canada/Eastern"  -- Unix TZ values like those found in https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
+  ##   3. UTC               -- or blank/unspecified, will return timestamp in UTC
+  grok_timezone = "Canada/Eastern"
+```
+
+### Timestamp examples
+
+This example input and config parses a file using a custom timestamp conversion:
+
+```
+2017-02-21 13:10:34 value=42
+```
+
+```toml
+[[inputs.file]]
+  grok_patterns = ['%{TIMESTAMP_ISO8601:timestamp:ts-"2006-01-02 15:04:05"} value=%{NUMBER:value:int}']
+```
+
+This example input and config parses a file using a timestamp in unix time:
+
+```
+1466004605 value=42
+1466004605.123456789 value=42
+```
+
+```toml
+[[inputs.file]]
+  grok_patterns = ['%{NUMBER:timestamp:ts-epoch} value=%{NUMBER:value:int}']
+```
+
+This example parses a file using a built-in conversion and a custom pattern:
+
+```
+Wed Apr 12 13:10:34 PST 2017 value=42
+```
+
+```toml
+[[inputs.file]]
+  grok_patterns = ["%{TS_UNIX:timestamp:ts-unix} value=%{NUMBER:value:int}"]
+  grok_custom_patterns = '''
+    TS_UNIX %{DAY} %{MONTH} %{MONTHDAY} %{HOUR}:%{MINUTE}:%{SECOND} %{TZ} %{YEAR}
+  '''
+```
+
+For cases where the timestamp itself is without offset, the `timezone` config var is available
+to denote an offset. By default (with `timezone` either omit, blank or set to `"UTC"`), the times
+are processed as if in the UTC timezone. If specified as `timezone = "Local"`, the timestamp
+will be processed based on the current machine timezone configuration. Lastly, if using a
+timezone from the list of Unix [timezones](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones),
+grok will offset the timestamp accordingly.
+
+### TOML escaping
+
+When saving patterns to the configuration file, keep in mind the different TOML
+[string](https://github.com/toml-lang/toml#string) types and the escaping
+rules for each.  These escaping rules must be applied in addition to the
+escaping required by the grok syntax.  Using the Multi-line line literal
+syntax with `'''` may be useful.
+
+The following config examples will parse this input file:
+
+```
+|42|\uD83D\uDC2F|'telegraf'|
+```
+
+Since `|` is a special character in the grok language, we must escape it to
+get a literal `|`.  With a basic TOML string, special characters such as
+backslash must be escaped, requiring us to escape the backslash a second time.
+
+```toml
+[[inputs.file]]
+  grok_patterns = ["\\|%{NUMBER:value:int}\\|%{UNICODE_ESCAPE:escape}\\|'%{WORD:name}'\\|"]
+  grok_custom_patterns = "UNICODE_ESCAPE (?:\\\\u[0-9A-F]{4})+"
+```
+
+We cannot use a literal TOML string for the pattern, because we cannot match a
+`'` within it.  However, it works well for the custom pattern.
+```toml
+[[inputs.file]]
+  grok_patterns = ["\\|%{NUMBER:value:int}\\|%{UNICODE_ESCAPE:escape}\\|'%{WORD:name}'\\|"]
+  grok_custom_patterns = 'UNICODE_ESCAPE (?:\\u[0-9A-F]{4})+'
+```
+
+A multi-line literal string allows us to encode the pattern:
+```toml
+[[inputs.file]]
+  grok_patterns = ['''
+    \|%{NUMBER:value:int}\|%{UNICODE_ESCAPE:escape}\|'%{WORD:name}'\|
+  ''']
+  grok_custom_patterns = 'UNICODE_ESCAPE (?:\\u[0-9A-F]{4})+'
+```
+
+### Tips for creating patterns
+
+Writing complex patterns can be difficult, here is some advice for writing a
+new pattern or testing a pattern developed [online](https://grokdebug.herokuapp.com).
+
+Create a file output that writes to stdout, and disable other outputs while
+testing.  This will allow you to see the captured metrics.  Keep in mind that
+the file output will only print once per `flush_interval`.
+
+```toml
+[[outputs.file]]
+  files = ["stdout"]
+```
+
+- Start with a file containing only a single line of your input.
+- Remove all but the first token or piece of the line.
+- Add the section of your pattern to match this piece to your configuration file.
+- Verify that the metric is parsed successfully by running Telegraf.
+- If successful, add the next token, update the pattern and retest.
+- Continue one token at a time until the entire line is successfully parsed.
diff --git a/content/telegraf/v1.22/data_formats/input/influx.md b/content/telegraf/v1.22/data_formats/input/influx.md
new file mode 100644
index 000000000..1a0b5590a
--- /dev/null
+++ b/content/telegraf/v1.22/data_formats/input/influx.md
@@ -0,0 +1,28 @@
+---
+title: InfluxDB Line Protocol input data format
+description: Use the InfluxDB Line Protocol input data format to parse InfluxDB metrics directly into Telegraf metrics.
+menu:
+  telegraf_1_22_ref:
+
+    name: InfluxDB Line Protocol input
+    weight: 60
+    parent: Input data formats
+---
+
+There are no additional configuration options for InfluxDB [line protocol][]. The
+InfluxDB metrics are parsed directly into Telegraf metrics.
+
+[line protocol]: /{{< latest "influxdb" "v1" >}}/write_protocols/line/
+
+### Configuration
+
+```toml
+[[inputs.file]]
+  files = ["example"]
+
+  ## Data format to consume.
+  ## Each data format has its own unique set of configuration options, read
+  ## more about them here:
+  ##   https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md
+  data_format = "influx"
+```
diff --git a/content/telegraf/v1.22/data_formats/input/json.md b/content/telegraf/v1.22/data_formats/input/json.md
new file mode 100644
index 000000000..278706ac2
--- /dev/null
+++ b/content/telegraf/v1.22/data_formats/input/json.md
@@ -0,0 +1,228 @@
+---
+title: JSON input data format
+description: Use the JSON input data format to parse [JSON][json] objects, or an array of objects, into Telegraf metric fields.
+menu:
+  telegraf_1_22_ref:
+
+    name: JSON input
+    weight: 70
+    parent: Input data formats
+---
+
+{{% note %}}
+The following information applies to the legacy JSON input data format. For most cases, we recommend using the [JSON v2 input data format](/{{< latest "telegraf" >}}/data_formats/input/json_v2/) instead.
+{{% /note %}}
+
+The JSON input data format parses a [JSON][json] object or an array of objects
+into Telegraf metric fields.
+
+**NOTE:** All JSON numbers are converted to float fields.  JSON String are
+ignored unless specified in the `tag_key` or `json_string_fields` options.
+
+## Configuration
+
+```toml
+[[inputs.file]]
+  files = ["example"]
+
+  ## Data format to consume.
+  ## Each data format has its own unique set of configuration options, read
+  ## more about them here:
+  ## https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md
+  data_format = "json"
+
+  ## Query is a GJSON path that specifies a specific chunk of JSON to be
+  ## parsed, if not specified the whole document will be parsed.
+  ##
+  ## GJSON query paths are described here:
+  ##   https://github.com/tidwall/gjson#path-syntax
+  json_query = ""
+
+  ## Tag keys is an array of keys that should be added as tags.
+  tag_keys = [
+    "my_tag_1",
+    "my_tag_2"
+  ]
+
+  ## String fields is an array of keys that should be added as string fields.
+  json_string_fields = []
+
+  ## Name key is the key to use as the measurement name.
+  json_name_key = ""
+
+  ## Time key is the key containing the time that should be used to create the
+  ## metric.
+  json_time_key = ""
+
+  ## Time format is the time layout that should be used to interprete the
+  ## json_time_key.  The time must be `unix`, `unix_ms` or a time in the
+  ## "reference time".
+  ##   ex: json_time_format = "Mon Jan 2 15:04:05 -0700 MST 2006"
+  ##       json_time_format = "2006-01-02T15:04:05Z07:00"
+  ##       json_time_format = "unix"
+  ##       json_time_format = "unix_ms"
+  json_time_format = ""
+```
+
+### `json_query`
+
+The `json_query` is a [GJSON][gjson] path that can be used to limit the
+portion of the overall JSON document that should be parsed.  The result of the
+query should contain a JSON object or an array of objects.
+
+Consult the GJSON [path syntax][gjson syntax] for details and examples.
+
+### json_time_key, json_time_format
+
+By default the current time will be used for all created metrics, to set the
+time using the JSON document you can use the `json_time_key` and
+`json_time_format` options together to set the time to a value in the parsed
+document.
+
+The `json_time_key` option specifies the key containing the time value and
+`json_time_format` must be set to `unix`, `unix_ms`, or the Go "reference
+time" which is defined to be the specific time: `Mon Jan 2 15:04:05 MST 2006`.
+
+Consult the Go [time][time parse] package for details and additional examples
+on how to set the time format.
+
+## Examples
+
+### Basic parsing
+
+Config:
+```toml
+[[inputs.file]]
+  files = ["example"]
+  name_override = "myjsonmetric"
+  data_format = "json"
+```
+
+Input:
+```json
+{
+    "a": 5,
+    "b": {
+        "c": 6
+    },
+    "ignored": "I'm a string"
+}
+```
+
+Output:
+```
+myjsonmetric a=5,b_c=6
+```
+
+### Name, tags, and string fields
+
+Config:
+```toml
+[[inputs.file]]
+  files = ["example"]
+  json_name_key = "name"
+  tag_keys = ["my_tag_1"]
+  json_string_fields = ["my_field"]
+  data_format = "json"
+```
+
+Input:
+```json
+{
+    "a": 5,
+    "b": {
+        "c": 6,
+        "my_field": "description"
+    },
+    "my_tag_1": "foo",
+    "name": "my_json"
+}
+```
+
+Output:
+```
+my_json,my_tag_1=foo a=5,b_c=6,my_field="description"
+```
+
+### Arrays
+
+If the JSON data is an array, then each object within the array is parsed with
+the configured settings.
+
+Config:
+```toml
+[[inputs.file]]
+  files = ["example"]
+  data_format = "json"
+  json_time_key = "b_time"
+  json_time_format = "02 Jan 06 15:04 MST"
+```
+
+Input:
+```json
+[
+    {
+        "a": 5,
+        "b": {
+            "c": 6,
+            "time":"04 Jan 06 15:04 MST"
+        },
+    },
+    {
+        "a": 7,
+        "b": {
+            "c": 8,
+            "time":"11 Jan 07 15:04 MST"
+        },
+    }
+]
+```
+
+Output:
+```
+file a=5,b_c=6 1136387040000000000
+file a=7,b_c=8 1168527840000000000
+```
+
+### Query
+
+The `json_query` option can be used to parse a subset of the document.
+
+Config:
+```toml
+[[inputs.file]]
+  files = ["example"]
+  data_format = "json_v2"
+  tag_keys = ["first"]
+  json_string_fields = ["last"]
+  json_query = "obj.friends"
+```
+
+Input:
+```json
+{
+    "obj": {
+        "name": {"first": "Tom", "last": "Anderson"},
+        "age":37,
+        "children": ["Sara","Alex","Jack"],
+        "fav.movie": "Deer Hunter",
+        "friends": [
+            {"first": "Dale", "last": "Murphy", "age": 44},
+            {"first": "Roger", "last": "Craig", "age": 68},
+            {"first": "Jane", "last": "Murphy", "age": 47}
+        ]
+    }
+}
+```
+
+Output:
+```
+file,first=Dale last="Murphy",age=44
+file,first=Roger last="Craig",age=68
+file,first=Jane last="Murphy",age=47
+```
+
+[gjson]:        https://github.com/tidwall/gjson
+[gjson syntax]: https://github.com/tidwall/gjson#path-syntax
+[json]:         https://www.json.org/
+[time parse]:   https://golang.org/pkg/time/#Parse
diff --git a/content/telegraf/v1.22/data_formats/input/json_v2.md b/content/telegraf/v1.22/data_formats/input/json_v2.md
new file mode 100644
index 000000000..5ccea988b
--- /dev/null
+++ b/content/telegraf/v1.22/data_formats/input/json_v2.md
@@ -0,0 +1,174 @@
+---
+title: JSON v2 input data format
+description: Use the JSON v2 input data format to parse [JSON][json] objects, or an array of objects, into Telegraf metric fields.
+menu:
+  telegraf_1_22_ref:
+
+    name: JSON v2 input
+    weight: 70
+    parent: Input data formats
+---
+
+The JSON v2 input data format parses a [JSON][json] object or an array of objects into Telegraf metric fields.
+This parser takes valid JSON input and turns it into metrics.
+
+The query syntax supported is [GJSON Path Syntax](https://github.com/tidwall/gjson/blob/v1.7.5/SYNTAX.md),
+Use to [this playground](https://gjson.dev/) to test out your GJSON path.
+
+You can find multiple examples [here](https://github.com/influxdata/telegraf/tree/master/plugins/parsers/json_v2/testdata) in the Telegraf repository.
+
+<!--
+is this still true?
+{{% note %}}
+All JSON numbers are converted to float fields.  JSON String are
+ignored unless specified in the `tag_key` or `json_string_fields` options.
+{{% /note %}}
+ -->
+
+## Configuration
+
+Configure this parser by describing the metric you want by defining the fields and tags from the input.
+The configuration is divided into config sub-tables called `field`, `tag`, and `object`.
+In the example below you can see all the possible configuration keys you can define for each config table.
+In the sections that follow these configuration keys are defined in more detail.
+
+```toml
+ [[inputs.file]]
+    urls = []
+    data_format = "json_v2"
+
+    [[inputs.file.json_v2]]
+        measurement_name = "" # A string that will become the new measurement name
+        measurement_name_path = "" # A string with valid GJSON path syntax, will override measurement_name
+        timestamp_path = "" # A string with valid GJSON path syntax to a valid timestamp (single value)
+        timestamp_format = "" # A string with a valid timestamp format (see below for possible values)
+        timestamp_timezone = "" # A string with with a valid timezone (see below for possible values)
+
+        [[inputs.file.json_v2.field]]
+            path = "" # A string with valid GJSON path syntax
+            rename = "new name" # A string with a new name for the tag key
+            type = "int" # A string specifying the type (int,uint,float,string,bool)
+
+        [[inputs.file.json_v2.tag]]
+            path = "" # A string with valid GJSON path syntax
+            rename = "new name" # A string with a new name for the tag key
+
+        [[inputs.file.json_v2.object]]
+            path = "" # A string with valid GJSON path syntax
+            timestamp_key = "" # A JSON key (for a nested key, prepend the parent keys with underscores) to a valid timestamp
+            timestamp_format = "" # A string with a valid timestamp format (see below for possible values)
+            timestamp_timezone = "" # A string with with a valid timezone (see below for possible values)
+            disable_prepend_keys = false (or true, just not both)
+            included_keys = [] # List of JSON keys (for a nested key, prepend the parent keys with underscores) that should be only included in result
+            excluded_keys = [] # List of JSON keys (for a nested key, prepend the parent keys with underscores) that shouldn't be included in result
+            tags = [] # List of JSON keys (for a nested key, prepend the parent keys with underscores) to be a tag instead of a field
+            [inputs.file.json_v2.object.renames] # A map of JSON keys (for a nested key, prepend the parent keys with underscores) with a new name for the tag key
+                key = "new name"
+            [inputs.file.json_v2.object.fields] # A map of JSON keys (for a nested key, prepend the parent keys with underscores) with a type (int,uint,float,string,bool)
+                key = "int"
+```
+
+### Root configuration options
+
+* **measurement_name (OPTIONAL)**:  Will set the measurement name to the provided string.
+* **measurement_name_path (OPTIONAL)**: You can define a query with [GJSON Path Syntax](https://github.com/tidwall/gjson/blob/v1.7.5/SYNTAX.md) to set a measurement name from the JSON input.
+  The query must return a single data value or it will use the default measurement name.
+  This takes precedence over `measurement_name`.
+* **timestamp_path (OPTIONAL)**: You can define a query with [GJSON Path Syntax](https://github.com/tidwall/gjson/blob/v1.7.5/SYNTAX.md) to set a timestamp from the JSON input.
+  The query must return a single data value or it will default to the current time.
+* **timestamp_format (OPTIONAL, but REQUIRED when timestamp_query is defined**: Must be set to `unix`, `unix_ms`, `unix_us`, `unix_ns`, or
+  the Go "reference time" which is defined to be the specific time:
+  `Mon Jan 2 15:04:05 MST 2006`
+* **timestamp_timezone (OPTIONAL, but REQUIRES timestamp_query**: This option should be set to a
+  [Unix TZ value](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones),
+  such as `America/New_York`, to `Local` to utilize the system timezone, or to `UTC`.
+  Defaults to `UTC`
+
+## Arrays and Objects
+
+The following describes the high-level approach when parsing arrays and objects:
+
+- **Array**: Every element in an array is treated as a *separate* metric
+- **Object**: Every key-value in a object is treated as a *single* metric
+
+When handling nested arrays and objects, the rules above continue to apply as the parser creates metrics.
+When an object has multiple arrays as values,
+the arrays will become separate metrics containing only non-array values from the object.
+Below you can see an example of this behavior,
+with an input JSON containing an array of book objects that has a nested array of characters.
+
+**Example JSON:**
+
+```json
+{
+    "book": {
+        "title": "The Lord Of The Rings",
+        "chapters": [
+            "A Long-expected Party",
+            "The Shadow of the Past"
+        ],
+        "author": "Tolkien",
+        "characters": [
+            {
+                "name": "Bilbo",
+                "species": "hobbit"
+            },
+            {
+                "name": "Frodo",
+                "species": "hobbit"
+            }
+        ],
+        "random": [
+            1,
+            2
+        ]
+    }
+}
+
+```
+
+**Example configuration:**
+
+```toml
+[[inputs.file]]
+    files = ["./testdata/multiple_arrays_in_object/input.json"]
+    data_format = "json_v2"
+    [[inputs.file.json_v2]]
+        [[inputs.file.json_v2.object]]
+            path = "book"
+            tags = ["title"]
+            disable_prepend_keys = true
+```
+
+**Expected metrics:**
+
+```
+file,title=The\ Lord\ Of\ The\ Rings author="Tolkien",chapters="A Long-expected Party"
+file,title=The\ Lord\ Of\ The\ Rings author="Tolkien",chapters="The Shadow of the Past"
+file,title=The\ Lord\ Of\ The\ Rings author="Tolkien",name="Bilbo",species="hobbit"
+file,title=The\ Lord\ Of\ The\ Rings author="Tolkien",name="Frodo",species="hobbit"
+file,title=The\ Lord\ Of\ The\ Rings author="Tolkien",random=1
+file,title=The\ Lord\ Of\ The\ Rings author="Tolkien",random=2
+
+```
+
+You can find more complicated examples under the folder `testdata`.
+
+## Types
+
+For each field you have the option to define the types for each metric.
+The following rules are in place for this configuration:
+
+* If a type is explicitly defined, the parser will enforce this type and convert the data to the defined type if possible.
+  If the type can't be converted then the parser will fail.
+* If a type isn't defined, the parser will use the default type defined in the JSON (int, float, string)
+
+The type values you can set:
+
+* `int`, bool, floats or strings (with valid numbers) can be converted to a int.
+* `uint`, bool, floats or strings (with valid numbers) can be converted to a uint.
+* `string`, any data can be formatted as a string.
+* `float`, string values (with valid numbers) or integers can be converted to a float.
+* `bool`, the string values "true" or "false" (regardless of capitalization) or the integer values `0` or `1`  can be turned to a bool.
+
+[json]:         https://www.json.org/
diff --git a/content/telegraf/v1.22/data_formats/input/logfmt.md b/content/telegraf/v1.22/data_formats/input/logfmt.md
new file mode 100644
index 000000000..a20af3ca7
--- /dev/null
+++ b/content/telegraf/v1.22/data_formats/input/logfmt.md
@@ -0,0 +1,43 @@
+---
+title: Logfmt input data format
+description: Use the `logfmt` input data format to parse logfmt data into Telegraf metrics.
+menu:
+  telegraf_1_22_ref:
+
+    name: logfmt
+    weight: 80
+    parent: Input data formats
+---
+
+The `logfmt` data format parses [logfmt] data into Telegraf metrics.
+
+[logfmt]: https://brandur.org/logfmt
+
+## Configuration
+
+```toml
+[[inputs.file]]
+  files = ["example"]
+
+  ## Data format to consume.
+  ## Each data format has its own unique set of configuration options, read
+  ## more about them here:
+  ##   https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md
+  data_format = "logfmt"
+
+  ## Set the name of the created metric, if unset the name of the plugin will
+  ## be used.
+  metric_name = "logfmt"
+```
+
+## Metrics
+
+Each key-value pair in the line is added to a new metric as a field.  The type
+of the field is automatically determined based on the contents of the value.
+
+## Examples
+
+```
+- method=GET host=example.org ts=2018-07-24T19:43:40.275Z connect=4ms service=8ms status=200 bytes=1653
++ logfmt method="GET",host="example.org",ts="2018-07-24T19:43:40.275Z",connect="4ms",service="8ms",status=200i,bytes=1653i
+```
diff --git a/content/telegraf/v1.22/data_formats/input/nagios.md b/content/telegraf/v1.22/data_formats/input/nagios.md
new file mode 100644
index 000000000..f53cd9f04
--- /dev/null
+++ b/content/telegraf/v1.22/data_formats/input/nagios.md
@@ -0,0 +1,30 @@
+---
+title: Nagios input data format
+description: Use the Nagios input data format to parse the output of Nagios plugins into Telegraf metrics.
+menu:
+  telegraf_1_22_ref:
+
+    name: Nagios
+    weight: 90
+    parent: Input data formats
+---
+
+# Nagios
+
+The Nagios input data format parses the output of
+[Nagios plugins](https://www.nagios.org/downloads/nagios-plugins/) into
+Telegraf metrics.
+
+## Configuration
+
+```toml
+[[inputs.exec]]
+  ## Commands array
+  commands = ["/usr/lib/nagios/plugins/check_load -w 5,6,7 -c 7,8,9"]
+
+  ## Data format to consume.
+  ## Each data format has its own unique set of configuration options, read
+  ## more about them here:
+  ##   https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md
+  data_format = "nagios"
+```
diff --git a/content/telegraf/v1.22/data_formats/input/prometheus-remote-write.md b/content/telegraf/v1.22/data_formats/input/prometheus-remote-write.md
new file mode 100644
index 000000000..720acc02c
--- /dev/null
+++ b/content/telegraf/v1.22/data_formats/input/prometheus-remote-write.md
@@ -0,0 +1,62 @@
+---
+title: Prometheus Remote Write input data format
+description: |
+  Use the Prometheus Remote Write input data format to write samples directly into Telegraf metrics.
+menu:
+  telegraf_1_22_ref:
+
+    name: Prometheus Remote Write
+    weight: 40
+    parent: Input data formats
+---
+
+Use the Prometheus Remote Write plugin to convert [Prometheus Remote Write](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#remote_write) samples directly into Telegraf metrics.
+
+{{% note %}}
+If you are using InfluxDB 1.x and the [Prometheus Remote Write endpoint](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/prometheusremotewrite/README.md
+to write in metrics, you can migrate to InfluxDB 2.0 and use this parser.
+For the metrics to completely align with the 1.x endpoint, add a Starlark processor as described [here](https://github.com/influxdata/telegraf/blob/master/plugins/processors/starlark/README.md).
+
+{{% /note %}}
+
+### Configuration
+
+Use the [`inputs.http_listener_v2`](/telegraf/v1.22/plugins/#input-http_listener_v2) plug and set `data_format = "prometheusremotewrite"`
+
+```toml
+[[inputs.http_listener_v2]]
+  ## Address and port to host HTTP listener on
+  service_address = ":1234"
+  ## Path to listen to.
+  path = "/recieve"
+  ## Data format to consume.
+  data_format = "prometheusremotewrite"
+```
+
+### Example
+
+**Example Input**
+```
+prompb.WriteRequest{
+		Timeseries: []*prompb.TimeSeries{
+			{
+				Labels: []*prompb.Label{
+					{Name: "__name__", Value: "go_gc_duration_seconds"},
+					{Name: "instance", Value: "localhost:9090"},
+					{Name: "job", Value: "prometheus"},
+					{Name: "quantile", Value: "0.99"},
+				},
+				Samples: []prompb.Sample{
+					{Value: 4.63, Timestamp: time.Date(2020, 4, 1, 0, 0, 0, 0, time.UTC).UnixNano()},
+				},
+			},
+		},
+	}
+```
+
+**Example Output**
+```
+prometheus_remote_write,instance=localhost:9090,job=prometheus,quantile=0.99 go_gc_duration_seconds=4.63 1614889298859000000
+```
+
+[here]: https://github.com/influxdata/telegraf/tree/master/plugins/parsers/prometheusremotewrite#for-alignment-with-the-influxdb-v1x-prometheus-remote-write-spec
diff --git a/content/telegraf/v1.22/data_formats/input/value.md b/content/telegraf/v1.22/data_formats/input/value.md
new file mode 100644
index 000000000..bc3e8f8cc
--- /dev/null
+++ b/content/telegraf/v1.22/data_formats/input/value.md
@@ -0,0 +1,45 @@
+---
+title: Value input data format
+description: Use the `value` input data format to parse single values into Telegraf metrics.
+menu:
+  telegraf_1_22_ref:
+
+    name: Value
+    weight: 100
+    parent: Input data formats
+---
+
+
+The "value" input data format translates single values into Telegraf metrics. This
+is done by assigning a measurement name and setting a single field ("value")
+as the parsed metric.
+
+## Configuration
+
+You **must** tell Telegraf what type of metric to collect by using the
+`data_type` configuration option. Available data type options are:
+
+1. integer
+2. float or long
+3. string
+4. boolean
+
+> **Note:** It is also recommended that you set `name_override` to a measurement
+name that makes sense for your metric; otherwise, it will just be set to the
+name of the plugin.
+
+```toml
+[[inputs.exec]]
+  ## Commands array
+  commands = ["cat /proc/sys/kernel/random/entropy_avail"]
+
+  ## override the default metric name of "exec"
+  name_override = "entropy_available"
+
+  ## Data format to consume.
+  ## Each data format has its own unique set of configuration options, read
+  ## more about them here:
+  ##   https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md
+  data_format = "value"
+  data_type = "integer" # required
+```
diff --git a/content/telegraf/v1.22/data_formats/input/wavefront.md b/content/telegraf/v1.22/data_formats/input/wavefront.md
new file mode 100644
index 000000000..b4e43b1e6
--- /dev/null
+++ b/content/telegraf/v1.22/data_formats/input/wavefront.md
@@ -0,0 +1,29 @@
+---
+title: Wavefront input data format
+description: Use the Wavefront input data format to parse Wavefront data into Telegraf metrics.
+menu:
+  telegraf_1_22_ref:
+
+    name: Wavefront
+    weight: 110
+    parent: Input data formats
+---
+
+The Wavefront input data format parses Wavefront data into Telegraf metrics.
+For more information on the Wavefront native data format, see
+[Wavefront Data Format](https://docs.wavefront.com/wavefront_data_format.html) in the Wavefront documentation.
+
+## Configuration
+
+There are no additional configuration options for Wavefront Data Format line-protocol.
+
+```toml
+[[inputs.file]]
+  files = ["example"]
+
+  ## Data format to consume.
+  ## Each data format has its own unique set of configuration options, read
+  ## more about them here:
+  ##   https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md
+  data_format = "wavefront"
+```
diff --git a/content/telegraf/v1.22/data_formats/input/xml.md b/content/telegraf/v1.22/data_formats/input/xml.md
new file mode 100644
index 000000000..89ad02064
--- /dev/null
+++ b/content/telegraf/v1.22/data_formats/input/xml.md
@@ -0,0 +1,59 @@
+---
+title: XML input data format
+description: Use the XML input data format to parse XML data into Telegraf metrics.
+menu:
+  telegraf_1_22_ref:
+
+    name: XML
+    weight: 110
+    parent: Input data formats
+---
+
+The XML input data format parses XML data into Telegraf metrics.
+
+
+## Configuration
+
+```toml
+[[inputs.file]]
+  files = ["example.xml"]
+
+  ## Data format to consume.
+  ## Each data format has its own unique set of configuration options, read
+  ## more about them here:
+  ## https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md
+  data_format = "xml"
+
+  ## Multiple parsing sections are allowed
+  [[inputs.file.xml]]
+    ## Optional: XPath-query to select a subset of nodes from the XML document.
+    #metric_selection = "/Bus/child::Sensor"
+
+    ## Optional: XPath-query to set the metric (measurement) name.
+    #metric_name = "string('example')"
+
+    ## Optional: Query to extract metric timestamp.
+    ## If not specified the time of execution is used.
+    #timestamp = "/Gateway/Timestamp"
+    ## Optional: Format of the timestamp determined by the query above.
+    ## This can be any of "unix", "unix_ms", "unix_us", "unix_ns" or a valid Golang
+    ## time format. If not specified, a "unix" timestamp (in seconds) is expected.
+    #timestamp_format = "2006-01-02T15:04:05Z"
+
+    ## Tag definitions using the given XPath queries.
+    [inputs.file.xml.tags]
+      name   = "substring-after(Sensor/@name, ' ')"
+      device = "string('the ultimate sensor')"
+
+    ## Integer field definitions using XPath queries.
+    [inputs.file.xml.fields_int]
+      consumers = "Variable/@consumers"
+
+    ## Non-integer field definitions using XPath queries.
+    ## The field type is defined using XPath expressions such as number(), boolean() or string(). If no conversion is performed the field will be of type string.
+    [inputs.file.xml.fields]
+      temperature = "number(Variable/@temperature)"
+      power       = "number(Variable/@power)"
+      frequency   = "number(Variable/@frequency)"
+      ok          = "Mode != 'ok'"
+```
diff --git a/content/telegraf/v1.22/data_formats/output/_index.md b/content/telegraf/v1.22/data_formats/output/_index.md
new file mode 100644
index 000000000..029155d55
--- /dev/null
+++ b/content/telegraf/v1.22/data_formats/output/_index.md
@@ -0,0 +1,31 @@
+---
+title: Telegraf output data formats
+description: Telegraf serializes metrics into output data formats.
+menu:
+  telegraf_1_22_ref:
+
+    name: Output data formats
+    weight: 1
+    parent: Data formats
+---
+
+In addition to output-specific data formats, Telegraf supports the following set
+of common data formats that may be selected when configuring many of the Telegraf
+output plugins.
+
+{{< children >}}
+
+You will be able to identify the plugins with support by the presence of a
+`data_format` configuration option, for example, in the File (`file`) output plugin:
+
+```toml
+[[outputs.file]]
+  ## Files to write to, "stdout" is a specially handled file.
+  files = ["stdout"]
+
+  ## Data format to output.
+  ## Each data format has its own unique set of configuration options, read
+  ## more about them here:
+  ## https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_OUTPUT.md
+  data_format = "influx"
+```
diff --git a/content/telegraf/v1.22/data_formats/output/carbon2.md b/content/telegraf/v1.22/data_formats/output/carbon2.md
new file mode 100644
index 000000000..6a7507b2c
--- /dev/null
+++ b/content/telegraf/v1.22/data_formats/output/carbon2.md
@@ -0,0 +1,61 @@
+---
+title: Carbon2 output data format
+description: Use the Carbon2 output data format (serializer) to convert Telegraf metrics into  the Carbon2 format.
+menu:
+  telegraf_1_22_ref:
+
+    name: Carbon2
+    weight: 10
+    parent: Output data formats
+---
+
+The `carbon2` output data format (serializer) translates the Telegraf metric format to the [Carbon2 format](http://metrics20.org/implementations/).
+
+### Configuration
+
+```toml
+[[outputs.file]]
+  ## Files to write to, "stdout" is a specially handled file.
+  files = ["stdout", "/tmp/metrics.out"]
+
+  ## Data format to output.
+  ## Each data format has its own unique set of configuration options, read
+  ## more about them here:
+  ## https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_OUTPUT.md
+  data_format = "carbon2"
+```
+
+Standard form:
+
+```
+metric=name field=field_1 host=foo  30 1234567890
+metric=name field=field_2 host=foo  4 1234567890
+metric=name field=field_N host=foo  59 1234567890
+```
+
+### Metrics
+
+The serializer converts the metrics by creating `intrinsic_tags` using the combination of metric name and fields.  So, if one Telegraf metric has 4 fields, the `carbon2` output will be 4 separate metrics. There will be a `metric` tag that represents the name of the metric and a `field` tag to represent the field.
+
+### Example
+
+If we take the following InfluxDB Line Protocol:
+
+```
+weather,location=us-midwest,season=summer temperature=82,wind=100 1234567890
+```
+
+After serializing in Carbon2, the result would be:
+
+```
+metric=weather field=temperature location=us-midwest season=summer  82 1234567890
+metric=weather field=wind location=us-midwest season=summer  100 1234567890
+```
+
+### Fields and tags with spaces
+
+When a field key or tag key-value have spaces, spaces will be replaced with `_`.
+
+### Tags with empty values
+
+When a tag's value is empty, it will be replaced with `null`.
diff --git a/content/telegraf/v1.22/data_formats/output/graphite.md b/content/telegraf/v1.22/data_formats/output/graphite.md
new file mode 100644
index 000000000..e68579f23
--- /dev/null
+++ b/content/telegraf/v1.22/data_formats/output/graphite.md
@@ -0,0 +1,59 @@
+---
+title: Graphite output data format
+description: Use the Graphite output data format to serialize data from Telegraf metrics.
+menu:
+  telegraf_1_22_ref:
+
+    name: Graphite output
+    weight: 20
+    parent: Output data formats
+---
+
+The Graphite data format is serialized from Telegraf metrics using either the
+template pattern or tag support method.  You can select between the two
+methods using the [`graphite_tag_support`](#graphite_tag_support) option.  When set, the tag support method is used,
+otherwise the [template pattern][templates]) option is used.
+
+## Configuration
+
+```toml
+[[outputs.file]]
+  ## Files to write to, "stdout" is a specially handled file.
+  files = ["stdout", "/tmp/metrics.out"]
+
+  ## Data format to output.
+  ## Each data format has its own unique set of configuration options, read
+  ## more about them here:
+  ## https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_OUTPUT.md
+  data_format = "graphite"
+
+  ## Prefix added to each graphite bucket
+  prefix = "telegraf"
+  ## Graphite template pattern
+  template = "host.tags.measurement.field"
+
+  ## Support Graphite tags, recommended to enable when using Graphite 1.1 or later.
+  # graphite_tag_support = false
+```
+
+### graphite_tag_support
+
+When the `graphite_tag_support` option is enabled, the template pattern is not
+used.  Instead, tags are encoded using
+[Graphite tag support](http://graphite.readthedocs.io/en/latest/tags.html),
+added in Graphite 1.1.  The `metric_path` is a combination of the optional
+`prefix` option, measurement name, and field name.
+
+The tag `name` is reserved by Graphite, any conflicting tags and will be encoded as `_name`.
+
+**Example conversion**:
+```
+cpu,cpu=cpu-total,dc=us-east-1,host=tars usage_idle=98.09,usage_user=0.89 1455320660004257758
+=>
+cpu.usage_user;cpu=cpu-total;dc=us-east-1;host=tars 0.89 1455320690
+cpu.usage_idle;cpu=cpu-total;dc=us-east-1;host=tars 98.09 1455320690
+```
+
+### templates
+
+For more information on templates and template patterns, see [Template patterns](/telegraf/v1.15/data_formats/template-patterns/).
diff --git a/content/telegraf/v1.22/data_formats/output/influx.md b/content/telegraf/v1.22/data_formats/output/influx.md
new file mode 100644
index 000000000..55103ce6e
--- /dev/null
+++ b/content/telegraf/v1.22/data_formats/output/influx.md
@@ -0,0 +1,42 @@
+---
+title: InfluxDB Line Protocol output data format
+description: The `influx` data format outputs metrics into the InfluxDB Line Protocol format.
+menu:
+  telegraf_1_22_ref:
+
+    name: InfluxDB Line Protocol
+    weight: 30
+    parent: Output data formats
+---
+
+The `influx` output data format outputs metrics into [InfluxDB Line Protocol][line protocol]. InfluxData recommends this data format unless another format is required for interoperability.
+
+## Configuration
+
+```toml
+[[outputs.file]]
+  ## Files to write to, "stdout" is a specially handled file.
+  files = ["stdout", "/tmp/metrics.out"]
+
+  ## Data format to output.
+  ## Each data format has its own unique set of configuration options, read
+  ## more about them here:
+  ## https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_OUTPUT.md
+  data_format = "influx"
+
+  ## Maximum line length in bytes.  Useful only for debugging.
+  influx_max_line_bytes = 0
+
+  ## When true, fields will be output in ascending lexical order.  Enabling
+  ## this option will result in decreased performance and is only recommended
+  ## when you need predictable ordering while debugging.
+  influx_sort_fields = false
+
+  ## When true, Telegraf will output unsigned integers as unsigned values,
+  ## i.e.: `42u`.  You will need a version of InfluxDB supporting unsigned
+  ## integer values.  Enabling this option will result in field type errors if
+  ## existing data has been written.
+  influx_uint_support = false
+```
+
+[line protocol]: /{{< latest "influxdb" "v1" >}}/write_protocols/line_protocol_tutorial/
diff --git a/content/telegraf/v1.22/data_formats/output/json.md b/content/telegraf/v1.22/data_formats/output/json.md
new file mode 100644
index 000000000..13637d423
--- /dev/null
+++ b/content/telegraf/v1.22/data_formats/output/json.md
@@ -0,0 +1,90 @@
+---
+title: JSON output data format
+description: Telegraf's `json` output data format converts metrics into JSON documents.
+menu:
+  telegraf_1_22_ref:
+
+    name: JSON
+    weight: 40
+    parent: Output data formats
+---
+
+The `json` output data format serializes Telegraf metrics into JSON documents.
+
+## Configuration
+
+```toml
+[[outputs.file]]
+  ## Files to write to, "stdout" is a specially handled file.
+  files = ["stdout", "/tmp/metrics.out"]
+
+  ## Data format to output.
+  ## Each data format has its own unique set of configuration options, read
+  ## more about them here:
+  ## https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_OUTPUT.md
+  data_format = "json"
+
+  ## The resolution to use for the metric timestamp.  Must be a duration string
+  ## such as "1ns", "1us", "1ms", "10ms", "1s".  Durations are truncated to
+  ## the power of 10 less than the specified units.
+  json_timestamp_units = "1s"
+```
+
+## Examples
+
+### Standard format
+
+```json
+{
+    "fields": {
+        "field_1": 30,
+        "field_2": 4,
+        "field_N": 59,
+        "n_images": 660
+    },
+    "name": "docker",
+    "tags": {
+        "host": "raynor"
+    },
+    "timestamp": 1458229140
+}
+```
+
+### Batch format
+
+When an output plugin needs to emit multiple metrics at one time, it may use the
+batch format.  The use of batch format is determined by the plugin -- reference
+the documentation for the specific plugin.
+
+```json
+{
+    "metrics": [
+        {
+            "fields": {
+                "field_1": 30,
+                "field_2": 4,
+                "field_N": 59,
+                "n_images": 660
+            },
+            "name": "docker",
+            "tags": {
+                "host": "raynor"
+            },
+            "timestamp": 1458229140
+        },
+        {
+            "fields": {
+                "field_1": 30,
+                "field_2": 4,
+                "field_N": 59,
+                "n_images": 660
+            },
+            "name": "docker",
+            "tags": {
+                "host": "raynor"
+            },
+            "timestamp": 1458229140
+        }
+    ]
+}
+```
diff --git a/content/telegraf/v1.22/data_formats/output/messagepack.md b/content/telegraf/v1.22/data_formats/output/messagepack.md
new file mode 100644
index 000000000..9d201c126
--- /dev/null
+++ b/content/telegraf/v1.22/data_formats/output/messagepack.md
@@ -0,0 +1,49 @@
+---
+title: MessagePack output data format
+description: Use the MessagePack output data format (serializer) to convert Telegraf metrics into MessagePack format.
+menu:
+  telegraf_1_22_ref:
+
+    name: MessagePack
+    weight: 10
+    parent: Output data formats
+---
+
+The `msgpack` output data format (serializer) translates the Telegraf metric format to the [MessagePack](https://msgpack.org/). MessagePack is an efficient binary serialization format that lets you exchange data among multiple languages like JSON.
+
+### Configuration
+
+```toml
+[[outputs.file]]
+  ## Files to write to, "stdout" is a specially handled file.
+  files = ["stdout", "/tmp/metrics.out"]
+
+  ## Data format to output.
+  ## Each data format has its own unique set of configuration options, read
+  ## more about them here:
+  ## https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_OUTPUT.md
+  data_format = "msgpack"
+```
+
+
+### Example output
+
+Output of this format is MessagePack binary representation of metrics with a structure identical to the below JSON:
+
+```
+{
+   "name":"cpu",
+   "time": <TIMESTAMP>, // https://github.com/msgpack/msgpack/blob/master/spec.md#timestamp-extension-type
+   "tags":{
+      "tag_1":"host01",
+      ...
+   },
+   "fields":{
+      "field_1":30,
+      "field_2":true,
+      "field_3":"field_value"
+      "field_4":30.1
+      ...
+   }
+}
+```
diff --git a/content/telegraf/v1.22/data_formats/output/nowmetric.md b/content/telegraf/v1.22/data_formats/output/nowmetric.md
new file mode 100644
index 000000000..16d50f9a0
--- /dev/null
+++ b/content/telegraf/v1.22/data_formats/output/nowmetric.md
@@ -0,0 +1,91 @@
+---
+title: ServiceNow Metrics output data format
+description: Use the ServiceNow Metrics output data format (serializer) to output metrics in the ServiceNow Operational Intelligence format.
+menu:
+  telegraf_1_22_ref:
+
+    name: ServiceNow Metrics
+    weight: 50
+    parent: Output data formats
+---
+
+The ServiceNow Metrics output data format (serializer) outputs metrics in the [ServiceNow Operational Intelligence format](https://docs.servicenow.com/bundle/kingston-it-operations-management/page/product/event-management/reference/mid-POST-metrics.html).
+
+It can be used to write to a file using the File output plugin, or for sending metrics to a MID Server with Enable REST endpoint activated using the standard telegraf HTTP output.
+If you're using the HTTP output plugin, this serializer knows how to batch the metrics so you don't end up with an HTTP POST per metric.
+
+An example event looks like:
+
+```javascript
+[{
+    "metric_type": "Disk C: % Free Space",
+    "resource": "C:\\",
+    "node": "lnux100",
+    "value": 50,
+    "timestamp": 1473183012000,
+    "ci2metric_id": {
+        "node": "lnux100"
+    },
+    "source": “Telegraf”
+}]
+```
+
+## Using with the HTTP output plugin
+
+To send this data to a ServiceNow MID Server with Web Server extension activated, you can use the HTTP output plugin, there are some custom headers that you need to add to manage the MID Web Server authorization, here's a sample config for an HTTP output:
+
+```toml
+[[outputs.http]]
+  ## URL is the address to send metrics to
+  url = "http://<mid server fqdn or ip address>:9082/api/mid/sa/metrics"
+
+  ## Timeout for HTTP message
+  # timeout = "5s"
+
+  ## HTTP method, one of: "POST" or "PUT"
+  method = "POST"
+
+  ## HTTP Basic Auth credentials
+  username = 'evt.integration'
+  password = 'P@$$w0rd!'
+
+  ## Optional TLS Config
+  # tls_ca = "/etc/telegraf/ca.pem"
+  # tls_cert = "/etc/telegraf/cert.pem"
+  # tls_key = "/etc/telegraf/key.pem"
+  ## Use TLS but skip chain & host verification
+  # insecure_skip_verify = false
+
+  ## Data format to output.
+  ## Each data format has it's own unique set of configuration options, read
+  ## more about them here:
+  ## https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_OUTPUT.md
+  data_format = "nowmetric"
+
+  ## Additional HTTP headers
+  [outputs.http.headers]
+  #   # Should be set manually to "application/json" for json data_format
+  Content-Type = "application/json"
+  Accept = "application/json"
+```
+
+Starting with the London release, you also need to explicitly create event rule to allow binding of metric events to host CIs.
+
+https://docs.servicenow.com/bundle/london-it-operations-management/page/product/event-management/task/event-rule-bind-metrics-to-host.html
+
+## Using with the File output plugin
+
+You can use the File output plugin to output the payload in a file.
+In this case, just add the following section to your telegraf configuration file.
+
+```toml
+[[outputs.file]]
+  ## Files to write to, "stdout" is a specially handled file.
+  files = ["C:/Telegraf/metrics.out"]
+
+  ## Data format to output.
+  ## Each data format has its own unique set of configuration options, read
+  ## more about them here:
+  ## https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_OUTPUT.md
+  data_format = "nowmetric"
+```
diff --git a/content/telegraf/v1.22/data_formats/output/splunkmetric.md b/content/telegraf/v1.22/data_formats/output/splunkmetric.md
new file mode 100644
index 000000000..642f26dba
--- /dev/null
+++ b/content/telegraf/v1.22/data_formats/output/splunkmetric.md
@@ -0,0 +1,148 @@
+---
+title: SplunkMetric output data format
+description: The SplunkMetric serializer formats and outputs data in a format that can be consumed by a Splunk metrics index.
+menu:
+  telegraf_1_22_ref:
+
+    name: SplunkMetric
+    weight: 60
+    parent: Output data formats
+---
+
+The SplunkMetric serializer formats and outputs the metric data in a format that can be consumed by a Splunk metrics index.
+It can be used to write to a file using the file output, or for sending metrics to a HEC using the standard Telegraf HTTP output.
+
+If you're using the HTTP output, this serializer knows how to batch the metrics so you don't end up with an HTTP POST per metric.
+
+Th data is output in a format that conforms to the specified Splunk HEC JSON format as found here:
+[Send metrics in JSON format](http://dev.splunk.com/view/event-collector/SP-CAAAFDN).
+
+An example event looks like:
+```javascript
+{
+  "time": 1529708430,
+  "event": "metric",
+  "host": "patas-mbp",
+  "fields": {
+    "_value": 0.6,
+    "cpu": "cpu0",
+    "dc": "mobile",
+    "metric_name": "cpu.usage_user",
+    "user": "ronnocol"
+  }
+}
+```
+In the above snippet, the following keys are dimensions:
+* cpu
+* dc
+* user
+
+## Using with the HTTP output
+
+To send this data to a Splunk HEC, you can use the HTTP output, there are some custom headers that you need to add
+to manage the HEC authorization, here's a sample config for an HTTP output:
+
+```toml
+[[outputs.http]]
+   ## URL is the address to send metrics to
+   url = "https://localhost:8088/services/collector"
+
+   ## Timeout for HTTP message
+   # timeout = "5s"
+
+   ## HTTP method, one of: "POST" or "PUT"
+   # method = "POST"
+
+   ## HTTP Basic Auth credentials
+   # username = "username"
+   # password = "pa$$word"
+
+   ## Optional TLS Config
+   # tls_ca = "/etc/telegraf/ca.pem"
+   # tls_cert = "/etc/telegraf/cert.pem"
+   # tls_key = "/etc/telegraf/key.pem"
+   ## Use TLS but skip chain & host verification
+   # insecure_skip_verify = false
+
+   ## Data format to output.
+   ## Each data format has it's own unique set of configuration options, read
+   ## more about them here:
+   ## https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_OUTPUT.md
+   data_format = "splunkmetric"
+    ## Provides time, index, source overrides for the HEC
+   splunkmetric_hec_routing = true
+
+   ## Additional HTTP headers
+    [outputs.http.headers]
+   # Should be set manually to "application/json" for json data_format
+      Content-Type = "application/json"
+      Authorization = "Splunk xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
+      X-Splunk-Request-Channel = "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
+```
+
+## Overrides
+You can override the default values for the HEC token you are using by adding additional tags to the config file.
+
+The following aspects of the token can be overriden with tags:
+* index
+* source
+
+You can either use `[global_tags]` or using a more advanced configuration as documented [here](https://github.com/influxdata/telegraf/blob/master/docs/CONFIGURATION.md).
+
+Such as this example which overrides the index just on the cpu metric:
+```toml
+[[inputs.cpu]]
+  percpu = false
+  totalcpu = true
+  [inputs.cpu.tags]
+    index = "cpu_metrics"
+```
+
+## Using with the File output
+
+You can use the file output when running telegraf on a machine with a Splunk forwarder.
+
+A sample event when `hec_routing` is false (or unset) looks like:
+```javascript
+{
+    "_value": 0.6,
+    "cpu": "cpu0",
+    "dc": "mobile",
+    "metric_name": "cpu.usage_user",
+    "user": "ronnocol",
+    "time": 1529708430
+}
+```
+Data formatted in this manner can be ingested with a simple `props.conf` file that
+looks like this:
+
+```ini
+[telegraf]
+category = Metrics
+description = Telegraf Metrics
+pulldown_type = 1
+DATETIME_CONFIG =
+NO_BINARY_CHECK = true
+SHOULD_LINEMERGE = true
+disabled = false
+INDEXED_EXTRACTIONS = json
+KV_MODE = none
+TIMESTAMP_FIELDS = time
+TIME_FORMAT = %s.%3N
+```
+
+An example configuration of a file based output is:
+
+```toml
+ # Send telegraf metrics to file(s)
+[[outputs.file]]
+   ## Files to write to, "stdout" is a specially handled file.
+   files = ["/tmp/metrics.out"]
+
+   ## Data format to output.
+   ## Each data format has its own unique set of configuration options, read
+   ## more about them here:
+   ## https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_OUTPUT.md
+   data_format = "splunkmetric"
+   hec_routing = false
+```
diff --git a/content/telegraf/v1.22/data_formats/template-patterns.md b/content/telegraf/v1.22/data_formats/template-patterns.md
new file mode 100644
index 000000000..22f7e82e9
--- /dev/null
+++ b/content/telegraf/v1.22/data_formats/template-patterns.md
@@ -0,0 +1,144 @@
+---
+title: Telegraf template patterns
+description: Use template patterns to describe how dot-delimited strings should map to and from Telegraf metrics.
+menu:
+  telegraf_1_22_ref:
+
+    name: Template patterns
+    weight: 30
+    parent: Data formats
+---
+
+Template patterns are a mini language that describes how a dot delimited
+string should be mapped to and from [metrics][].
+
+A template has the form:
+```
+"host.mytag.mytag.measurement.measurement.field*"
+```
+
+Where the following keywords can be set:
+
+1. `measurement`: specifies that this section of the graphite bucket corresponds
+to the measurement name. This can be specified multiple times.
+2. `field`: specifies that this section of the graphite bucket corresponds
+to the field name. This can be specified multiple times.
+3. `measurement*`: specifies that all remaining elements of the graphite bucket
+correspond to the measurement name.
+4. `field*`: specifies that all remaining elements of the graphite bucket
+correspond to the field name.
+
+Any part of the template that is not a keyword is treated as a tag key. This
+can also be specified multiple times.
+
+**NOTE:** `field*` cannot be used in conjunction with `measurement*`.
+
+## Examples
+
+### Measurement and tag templates
+
+The most basic template is to specify a single transformation to apply to all
+incoming metrics. So the following template:
+
+```toml
+templates = [
+    "region.region.measurement*"
+]
+```
+
+would result in the following Graphite -> Telegraf transformation.
+
+```
+us.west.cpu.load 100
+=> cpu.load,region=us.west value=100
+```
+
+Multiple templates can also be specified, but these should be differentiated
+using _filters_ (see below for more details)
+
+```toml
+templates = [
+    "*.*.* region.region.measurement", # <- all 3-part measurements will match this one.
+    "*.*.*.* region.region.host.measurement", # <- all 4-part measurements will match this one.
+]
+```
+
+### Field templates
+
+The field keyword tells Telegraf to give the metric that field name.
+So the following template:
+
+```toml
+separator = "_"
+templates = [
+    "measurement.measurement.field.field.region"
+]
+```
+
+would result in the following Graphite -> Telegraf transformation.
+
+```
+cpu.usage.idle.percent.eu-east 100
+=> cpu_usage,region=eu-east idle_percent=100
+```
+
+The field key can also be derived from all remaining elements of the graphite
+bucket by specifying `field*`:
+
+```toml
+separator = "_"
+templates = [
+    "measurement.measurement.region.field*"
+]
+```
+
+which would result in the following Graphite -> Telegraf transformation.
+
+```
+cpu.usage.eu-east.idle.percentage 100
+=> cpu_usage,region=eu-east idle_percentage=100
+```
+
+### Filter templates
+
+Users can also filter the template(s) to use based on the name of the bucket,
+using glob matching, like so:
+
+```toml
+templates = [
+    "cpu.* measurement.measurement.region",
+    "mem.* measurement.measurement.host"
+]
+```
+
+which would result in the following transformation:
+
+```
+cpu.load.eu-east 100
+=> cpu_load,region=eu-east value=100
+
+mem.cached.localhost 256
+=> mem_cached,host=localhost value=256
+```
+
+### Adding Tags
+
+Additional tags can be added to a metric that don't exist on the received metric.
+You can add additional tags by specifying them after the pattern.
+Tags have the same format as the line protocol.
+Multiple tags are separated by commas.
+
+```toml
+templates = [
+    "measurement.measurement.field.region datacenter=1a"
+]
+```
+
+would result in the following Graphite -> Telegraf transformation.
+
+```
+cpu.usage.idle.eu-east 100
+=> cpu_usage,region=eu-east,datacenter=1a idle=100
+```
+
+[metrics]: /telegraf/v1.15/concepts/metrics/
diff --git a/content/telegraf/v1.22/get_started.md b/content/telegraf/v1.22/get_started.md
new file mode 100644
index 000000000..43f62a44c
--- /dev/null
+++ b/content/telegraf/v1.22/get_started.md
@@ -0,0 +1,65 @@
+---
+title: Get started
+description: Configure and start Telegraf
+menu:
+  telegraf_1_22:
+    name: Get started
+    weight: 25
+---
+
+After you've [downloaded and installed Telegraf](/telegraf/v1.22/install/), you're ready to begin collecting and sending data. To collect and send data, do the following:
+
+1. [Configure Telegraf](#configure-telegraf)
+2. [Start Telegraf](#start-telegraf)
+3. Use [plugins available in Telegraf](/telegraf/v1.22/plugins/) to gather, transform, and output data.
+
+## Configure Telegraf
+
+Define which plugins Telegraf will use in the configuration file. Each configuration file needs at least one enabled [input plugin](/telegraf/v1.22/plugins/inputs/) (where the metrics come from) and at least one enabled [output plugin](/telegraf/v1.22/plugins/outputs/) (where the metrics go).
+
+The following example generates a sample configuration file with all available plugins, then uses `filter` flags to enable specific plugins.
+
+{{% note %}}
+For details on `filter` and other flags, see [Telegraf commands and flags](/telegraf/v1.22/commands/).
+{{% /note %}}
+
+1. Run the following command to create a configuration file:
+   ```bash
+   telegraf --sample-config > telegraf.conf
+   ```
+2. Locate the configuration file. The location varies depending on your system:
+   * macOS [Homebrew](http://brew.sh/): `/usr/local/etc/telegraf.conf`
+   * Linux debian and RPM packages: `/etc/telegraf/telegraf.conf`
+   * Standalone Binary: see the next section for how to create a configuration file
+
+   > **Note:** You can also specify a remote URL endpoint to pull a configuration file from. See [Configuration file locations](/telegraf/v1.15/administration/configuration/#configuration-file-locations).
+
+3. Edit the configuration file using `vim` or a text editor. Because this example uses [InfluxDB V2 output plugin](https://github.com/influxdata/telegraf/blob/release-1.21/plugins/outputs/influxdb_v2/README.md), we need to add the InfluxDB URL, authentication token, organization, and bucket details to this section of the configuration file.
+
+4. For this example, specify two inputs (`cpu` and `mem`) with the `--input-filter` flag.
+Specify InfluxDB as the output with the `--output-filter` flag.
+
+```bash
+telegraf --sample-config --input-filter cpu:mem --output-filter influxdb_v2 > telegraf.conf
+```
+
+The resulting configuration will collect CPU and memory data and sends it to InfluxDB V2.
+
+## Start Telegraf
+
+Next, you need to start the Telegraf service and direct it to your configuration file:
+
+### macOS [Homebrew](http://brew.sh/)
+```bash
+telegraf --config telegraf.conf
+```
+
+### Linux (sysvinit and upstart installations)
+```bash
+sudo service telegraf start
+```
+
+### Linux (systemd installations)
+```bash
+systemctl start telegraf
+```
diff --git a/content/telegraf/v1.22/glossary.md b/content/telegraf/v1.22/glossary.md
new file mode 100644
index 000000000..004cc9a33
--- /dev/null
+++ b/content/telegraf/v1.22/glossary.md
@@ -0,0 +1,106 @@
+---
+title: Telegraf glossary
+description: This section includes definitions of important terms for related to Telegraf.
+menu:
+  telegraf_1_22_ref:
+
+    name: Glossary
+    weight: 79
+---
+
+## agent
+
+An agent is the core part of Telegraf that gathers metrics from the declared input plugins and sends metrics to the declared output plugins, based on the plugins enabled by the given configuration.
+
+Related entries: [input plugin](/telegraf/v1.15/concepts/glossary/#input-plugin), [output plugin](/telegraf/v1.15/concepts/glossary/#output-plugin)
+
+## aggregator plugin
+
+Aggregator plugins receive raw metrics from input plugins and create aggregate metrics from them.
+The aggregate metrics are then passed to the configured output plugins.
+
+Related entries: [input plugin](/telegraf/v1.15/concepts/glossary/#input-plugin), [output plugin](/telegraf/v1.15/concepts/glossary/#output-plugin), [processor plugin](/telegraf/v1.15/concepts/glossary/#processor-plugin)
+
+## batch size
+
+The Telegraf agent sends metrics to output plugins in batches, not individually.
+The batch size controls the size of each write batch that Telegraf sends to the output plugins.
+
+Related entries: [output plugin](/telegraf/v1.15/concepts/glossary/#output-plugin)
+
+## collection interval
+
+The default global interval for collecting data from each input plugin.
+The collection interval can be overridden by each individual input plugin's configuration.
+
+Related entries: [input plugin](/telegraf/v1.15/concepts/glossary/#input-plugin)
+
+## collection jitter
+
+Collection jitter is used to prevent every input plugin from collecting metrics simultaneously, which can have a measurable effect on the system.
+Each collection interval, every input plugin will sleep for a random time between zero and the collection jitter before collecting the metrics.
+
+Related entries: [collection interval](/telegraf/v1.15/concepts/glossary/#collection-interval), [input plugin](/telegraf/v1.15/concepts/glossary/#input-plugin)
+
+## external plugin
+
+Programs built outside of Telegraf that run through the `execd` plugin. Provides flexibility to add functionality that doesn't exist in internal Telegraf plugins.
+## flush interval
+
+The global interval for flushing data from each output plugin to its destination.
+This value should not be set lower than the collection interval.
+
+Related entries: [collection interval](/telegraf/v1.15/concepts/glossary/#collection-interval), [flush jitter](/telegraf/v1.15/concepts/glossary/#flush-jitter), [output plugin](/telegraf/v1.15/concepts/glossary/#output-plugin)
+
+## flush jitter
+
+Flush jitter is used to prevent every output plugin from sending writes simultaneously, which can overwhelm some data sinks.
+Each flush interval, every output plugin will sleep for a random time between zero and the flush jitter before emitting metrics.
+This helps smooth out write spikes when running a large number of Telegraf instances.
+
+Related entries: [flush interval](/telegraf/v1.15/concepts/glossary/#flush-interval), [output plugin](/telegraf/v1.15/concepts/glossary/#output-plugin)
+
+## input plugin
+
+Input plugins actively gather metrics and deliver them to the core agent, where aggregator, processor, and output plugins can operate on the metrics.
+In order to activate an input plugin, it needs to be enabled and configured in Telegraf's configuration file.
+
+Related entries: [aggregator plugin](/telegraf/v1.15/concepts/glossary/#aggregator-plugin), [collection interval](/telegraf/v1.15/concepts/glossary/#collection-interval), [output plugin](/telegraf/v1.15/concepts/glossary/#output-plugin), [processor plugin](/telegraf/v1.15/concepts/glossary/#processor-plugin)
+
+## metric buffer
+
+The metric buffer caches individual metrics when writes are failing for an output plugin.
+Telegraf will attempt to flush the buffer upon a successful write to the output.
+The oldest metrics are dropped first when this buffer fills.
+
+Related entries: [output plugin](/telegraf/v1.15/concepts/glossary/#output-plugin)
+
+## output plugin
+
+Output plugins deliver metrics to their configured destination. In order to activate an output plugin, it needs to be enabled and configured in Telegraf's configuration file.
+
+Related entries: [aggregator plugin](/telegraf/v1.15/concepts/glossary/#aggregator-plugin), [flush interval](/telegraf/v1.15/concepts/glossary/#flush-interval), [input plugin](/telegraf/v1.15/concepts/glossary/#input-plugin), [processor plugin](/telegraf/v1.15/concepts/glossary/#processor-plugin)
+
+## precision
+
+The precision configuration setting determines how much timestamp precision is retained in the points received from input plugins. All incoming timestamps are truncated to the given precision.
+Telegraf then pads the truncated timestamps with zeros to create a nanosecond timestamp; output plugins will emit timestamps in nanoseconds.
+Valid precisions are `ns`, `us` or `µs`, `ms`, and `s`.
+
+For example, if the precision is set to `ms`, the nanosecond epoch timestamp `1480000000123456789` would be truncated to `1480000000123` in millisecond precision and then padded with zeroes to make a new, less precise nanosecond timestamp of `1480000000123000000`.
+Output plugins do not alter the timestamp further. The precision setting is ignored for service input plugins.
+
+Related entries:  [aggregator plugin](/telegraf/v1.15/concepts/glossary/#aggregator-plugin), [input plugin](/telegraf/v1.15/concepts/glossary/#input-plugin), [output plugin](/telegraf/v1.15/concepts/glossary/#output-plugin), [processor plugin](/telegraf/v1.15/concepts/glossary/#processor-plugin), [service input plugin](/telegraf/v1.15/concepts/glossary/#service-input-plugin)
+
+## processor plugin
+
+Processor plugins transform, decorate, and/or filter metrics collected by input plugins, passing the transformed metrics to the output plugins.
+
+Related entries: [aggregator plugin](/telegraf/v1.15/concepts/glossary/#aggregator-plugin), [input plugin](/telegraf/v1.15/concepts/glossary/#input-plugin), [output plugin](/telegraf/v1.15/concepts/glossary/#output-plugin)
+
+## service input plugin
+
+Service input plugins are input plugins that run in a passive collection mode while the Telegraf agent is running.
+They listen on a socket for known protocol inputs, or apply their own logic to ingested metrics before delivering them to the Telegraf agent.
+
+Related entries: [aggregator plugin](/telegraf/v1.15/concepts/glossary/#aggregator-plugin), [input plugin](/telegraf/v1.15/concepts/glossary/#input-plugin), [output plugin](/telegraf/v1.15/concepts/glossary/#output-plugin), [processor plugin](/telegraf/v1.15/concepts/glossary/#processor-plugin)
diff --git a/content/telegraf/v1.22/install.md b/content/telegraf/v1.22/install.md
new file mode 100644
index 000000000..b48126a5d
--- /dev/null
+++ b/content/telegraf/v1.22/install.md
@@ -0,0 +1,350 @@
+---
+title: Install Telegraf
+description: Install Telegraf on your operating system.
+menu:
+  telegraf_1_22:
+
+    name: Install
+    weight: 20
+---
+
+This page provides directions for installing, starting, and configuring Telegraf. To install Telegraf, do the following:
+
+1. [Download Telegraf](#download)
+2. [Review requirements](#requirements)
+3. [Complete the installation](#installation)
+
+## Download
+
+Download the latest Telegraf release at the [InfluxData download page](https://portal.influxdata.com/downloads).
+
+## Requirements
+
+Installation of the Telegraf package may require `root` or administrator privileges in order to complete successfully. <!--check instruction for each one to clarify-->
+
+### Networking
+
+Telegraf offers multiple service [input plugins](/telegraf/v1.22/plugins/inputs/) that may
+require custom ports.
+Modify port mappings through the configuration file (`telegraf.conf`).
+
+For Linux distributions, this file is located at `/etc/telegraf` for default installations.
+
+For Windows distributions, the configuration file is located in the directory where you unzipped the Telegraf ZIP archive.
+The default location is `C:\InfluxData\telegraf`.
+
+### NTP
+
+Telegraf uses a host's local time in UTC to assign timestamps to data.
+Use the Network Time Protocol (NTP) to synchronize time between hosts. If hosts' clocks
+aren't synchronized with NTP, the timestamps on the data might be inaccurate.
+
+## Installation
+
+{{< tabs-wrapper >}}
+{{% tabs %}}
+  [Ubuntu & Debian](#)
+  [RedHat & CentOS](#)
+  [SLES & openSUSE](#)
+  [FreeBSD/PC-BSD](#)
+  [macOS](#)
+  [Windows](#)
+{{% /tabs %}}
+<!---------- BEGIN Ubuntu & Debian ---------->
+{{% tab-content %}}
+Debian and Ubuntu users can install the latest stable version of Telegraf using the `apt-get` package manager.
+
+### Ubuntu & Debian
+
+Install Telegraf from the InfluxData repository with the following commands:
+
+{{< code-tabs-wrapper >}}
+{{% code-tabs %}}
+[wget](#)
+[curl](#)
+{{% /code-tabs %}}
+
+{{% code-tab-content %}}
+```bash
+wget -qO- https://repos.influxdata.com/influxdb.key | sudo tee /etc/apt/trusted.gpg.d/influxdb.asc >/dev/null
+echo "deb https://repos.influxdata.com/debian stable main" | sudo tee /etc/apt/sources.list.d/influxdb.list
+sudo apt-get update && sudo apt-get install telegraf
+```
+{{% /code-tab-content %}}
+
+{{% code-tab-content %}}
+```bash
+curl -s https://repos.influxdata.com/influxdb.key | sudo tee /etc/apt/trusted.gpg.d/influxdb.asc >/dev/null
+echo "deb https://repos.influxdata.com/debian stable main" | sudo tee /etc/apt/sources.list.d/influxdb.list
+sudo apt-get update && sudo apt-get install telegraf
+```
+{{% /code-tab-content %}}
+{{< /code-tabs-wrapper >}}
+
+**Install from a `.deb` file**:
+
+To manually install the Debian package from a `.deb` file:
+
+1. Download the latest Telegraf `.deb` release
+   from the Telegraf section of the [downloads page](https://influxdata.com/downloads/).
+2. Run the following command (making sure to supply the correct version number for the downloaded file):
+
+   ```sh
+   sudo dpkg -i telegraf_{{< latest-patch >}}-1_amd64.deb
+   ```
+
+{{% telegraf/verify %}}
+
+## Configuration
+
+### Create a configuration file with default input and output plugins.
+
+Every plugin will be in the file, but most will be commented out.
+
+```
+telegraf config > telegraf.conf
+```
+
+### Create a configuration file with specific inputs and outputs
+```
+telegraf --input-filter <pluginname>[:<pluginname>] --output-filter <outputname>[:<outputname>] config > telegraf.conf
+```
+
+For more advanced configuration details, see the
+[configuration documentation](/telegraf/v1.22/administration/configuration/).
+{{% /tab-content %}}
+<!---------- BEGIN RedHat & CentOS ---------->
+{{% tab-content %}}
+For instructions on how to manually install the RPM package from a file, please see the [downloads page](https://influxdata.com/downloads/).
+
+**RedHat and CentOS:** Install the latest stable version of Telegraf using the `yum` package manager:
+
+```bash
+cat <<EOF | sudo tee /etc/yum.repos.d/influxdb.repo
+[influxdb]
+name = InfluxData Repository - Stable
+baseurl = https://repos.influxdata.com/stable/\$basearch/main
+enabled = 1
+gpgcheck = 1
+gpgkey = https://repos.influxdata.com/influxdb.key
+EOF
+```
+
+Install telegraf once the repository is added to the `yum` configuration:
+
+```bash
+sudo yum install telegraf
+```
+
+{{% telegraf/verify %}}
+
+## Configuration
+
+### Create a configuration file with default input and output plugins
+
+Every plugin will be in the file, but most will be commented out.
+
+```
+telegraf config > telegraf.conf
+```
+
+### Create a configuration file with specific inputs and outputs
+```
+telegraf --input-filter <pluginname>[:<pluginname>] --output-filter <outputname>[:<outputname>] config > telegraf.conf
+```
+
+For more advanced configuration details, see the
+[configuration documentation](/telegraf/v1.22/administration/configuration/).
+{{% /tab-content %}}
+<!---------- BEGIN SLES & openSUSE ---------->
+{{% tab-content %}}
+There are RPM packages provided by openSUSE Build Service for SUSE Linux users:
+
+```bash
+# add go repository
+zypper ar -f obs://devel:languages:go/ go
+# install latest telegraf
+zypper in telegraf
+```
+
+{{% telegraf/verify %}}
+
+## Configuration
+
+### Create a configuration file with default input and output plugins.
+
+Every plugin will be in the file, but most will be commented out.
+
+```
+telegraf config > telegraf.conf
+```
+
+### Create a configuration file with specific inputs and outputs
+```
+telegraf --input-filter <pluginname>[:<pluginname>] --output-filter <outputname>[:<outputname>] config > telegraf.conf
+```
+
+For more advanced configuration details, see the
+[configuration documentation](/telegraf/v1.22/administration/configuration/).
+{{% /tab-content %}}
+<!---------- BEGIN FreeBSD/PC-BSD ---------->
+{{% tab-content %}}
+Telegraf is part of the FreeBSD package system.
+It can be installed by running:
+
+```bash
+sudo pkg install telegraf
+```
+
+The configuration file is located at `/usr/local/etc/telegraf.conf` with examples in `/usr/local/etc/telegraf.conf.sample`.
+
+{{% telegraf/verify %}}
+
+## Configuration
+
+### Create a configuration file with default input and output plugins.
+
+Every plugin will be in the file, but most will be commented out.
+
+```
+telegraf config > telegraf.conf
+```
+
+### Create a configuration file with specific inputs and outputs
+```
+telegraf --input-filter <pluginname>[:<pluginname>] --output-filter <outputname>[:<outputname>] config > telegraf.conf
+```
+
+For more advanced configuration details, see the
+[configuration documentation](/telegraf/v1.22/administration/configuration/).
+{{% /tab-content %}}
+<!---------- BEGIN macOS ---------->
+{{% tab-content %}}
+Users of macOS 10.8 and higher can install Telegraf using the [Homebrew](http://brew.sh/) package manager.
+Once `brew` is installed, you can install Telegraf by running:
+
+```bash
+brew update
+brew install telegraf
+```
+
+To have launchd start telegraf at next login:
+```
+ln -sfv /usr/local/opt/telegraf/*.plist ~/Library/LaunchAgents
+```
+To load telegraf now:
+```
+launchctl load ~/Library/LaunchAgents/homebrew.mxcl.telegraf.plist
+```
+
+Or, if you don't want/need launchctl, you can just run:
+```
+telegraf -config /usr/local/etc/telegraf.conf
+```
+
+{{% telegraf/verify %}}
+
+## Configuration
+
+### Create a configuration file with default input and output plugins.
+
+Every plugin will be in the file, but most will be commented out.
+
+```
+telegraf config > telegraf.conf
+```
+
+### Create a configuration file with specific inputs and outputs
+```
+telegraf --input-filter <pluginname>[:<pluginname>] --output-filter <outputname>[:<outputname>] config > telegraf.conf
+```
+
+For more advanced configuration details, see the
+[configuration documentation](/telegraf/v1.22/administration/configuration/).
+{{% /tab-content %}}
+<!---------- BEGIN Windows ---------->
+{{% tab-content %}}
+
+#### Download and run Telegraf as a Windows service
+
+{{% note %}}
+Installing a Windows service requires administrative permissions.
+To run PowerShell as an administrator,
+see [Launch PowerShell as administrator](https://docs.microsoft.com/en-us/powershell/scripting/windows-powershell/starting-windows-powershell?view=powershell-7#with-administrative-privileges-run-as-administrator).
+{{% /note %}}
+
+In PowerShell _as an administrator_, do the following:
+
+1.  Use the following commands to download the Telegraf Windows binary
+    and extract its contents to `C:\Program Files\InfluxData\telegraf\`:
+
+    ```powershell
+    > wget https://dl.influxdata.com/telegraf/releases/telegraf-{{% latest-patch %}}_windows_amd64.zip -UseBasicParsing -OutFile telegraf-{{< latest-patch >}}_windows_amd64.zip
+    > Expand-Archive .\telegraf-{{% latest-patch %}}_windows_amd64.zip -DestinationPath 'C:\Program Files\InfluxData\telegraf\'
+    ```
+
+2.  Move the `telegraf.exe` and `telegraf.conf` files from
+    `C:\Program Files\InfluxData\telegraf\telegraf-{{% latest-patch %}}`
+    up a level to `C:\Program Files\InfluxData\telegraf`:
+
+    ```powershell
+    > cd "C:\Program Files\InfluxData\telegraf"
+    > mv .\telegraf-{{% latest-patch %}}\telegraf.* .
+    ```
+
+    Or create a [Windows symbolic link (Symlink)](https://blogs.windows.com/windowsdeveloper/2016/12/02/symlinks-windows-10/)
+    to point to this directory.
+
+    > The instructions below assume that either the `telegraf.exe` and `telegraf.conf` files are stored in `C:\Program Files\InfluxData\telegraf`, or you've created a Symlink to point to this directory.
+
+3.  Install Telegraf as a service:
+
+    ```powershell
+    > .\telegraf.exe --service install --config "C:\Program Files\InfluxData\telegraf\telegraf.conf"
+    ```
+
+    Make sure to provide the absolute path of the `telegraf.conf` configuration file,
+    otherwise the Windows service may fail to start.
+
+4.  To test that the installation works, run:
+
+    ```powershell
+    > C:\"Program Files"\InfluxData\telegraf\telegraf.exe --config C:\"Program Files"\InfluxData\telegraf\telegraf.conf --test
+    ```
+
+5.  To start collecting data, run:
+
+    ```powershell
+    telegraf.exe --service start
+    ```
+
+<!--
+#### (Optional) Specify multiple configuration files
+
+If you have multiple Telegraf configuration files, you can specify a `--config-directory` for the service to use:
+
+1. Create a directory for configuration snippets at `C:\Program Files\Telegraf\telegraf.d`.
+2. Include the `--config-directory` option when registering the service:
+   ```powershell
+   > C:\"Program Files"\Telegraf\telegraf.exe --service install --config C:\"Program Files"\Telegraf\telegraf.conf --config-directory C:\"Program Files"\Telegraf\telegraf.d
+   ```
+-->
+
+### Logging and troubleshooting
+
+When Telegraf runs as a Windows service, Telegraf logs messages to Windows event logs.
+If the Telegraf service fails to start, view error logs by selecting **Event Viewer**→**Windows Logs**→**Application**.
+
+### Windows service commands
+
+The following commands are available:
+
+| Command                            | Effect                        |
+|------------------------------------|-------------------------------|
+| `telegraf.exe --service install`   | Install telegraf as a service |
+| `telegraf.exe --service uninstall` | Remove the telegraf service   |
+| `telegraf.exe --service start`     | Start the telegraf service    |
+| `telegraf.exe --service stop`      | Stop the telegraf service     |
+
+{{< /tab-content >}}
+{{< /tabs-wrapper >}}
diff --git a/content/telegraf/v1.22/metrics.md b/content/telegraf/v1.22/metrics.md
new file mode 100644
index 000000000..71737f6cf
--- /dev/null
+++ b/content/telegraf/v1.22/metrics.md
@@ -0,0 +1,29 @@
+---
+title: Telegraf metrics
+description: Telegraf metrics are internal representations used to model data during processing and are based on InfluxDB's data model. Each metric component includes the measurement name, tags, fields, and timestamp.
+menu:
+  telegraf_1.22:
+    name: Metrics
+    weight: 10
+    parent: Concepts
+    draft: true
+---
+
+Telegraf metrics are the internal representation used to model data during
+processing.  These metrics are closely based on InfluxDB's data model and contain
+four main components:
+
+- **Measurement name**: Description and namespace for the metric.
+- **Tags**: Key/Value string pairs and usually used to identify the
+  metric.
+- **Fields**: Key/Value pairs that are typed and usually contain the
+  metric data.
+- **Timestamp**: Date and time associated with the fields.
+
+This metric type exists only in memory and must be converted to a concrete
+representation in order to be transmitted or viewed. Telegraf provides [output data formats][output data formats] (also known as *serializers*) for these conversions.  Telegraf's default serializer converts to [InfluxDB Line
+Protocol][line protocol], which provides a high performance and one-to-one
+direct mapping from Telegraf metrics.
+
+[output data formats]: /telegraf/v1.22/data_formats/output/
+[line protocol]: /telegraf/v1.22/data_formats/output/influx/
diff --git a/content/telegraf/v1.22/plugins.md b/content/telegraf/v1.22/plugins.md
new file mode 100644
index 000000000..c7057e995
--- /dev/null
+++ b/content/telegraf/v1.22/plugins.md
@@ -0,0 +1,82 @@
+---
+title: Plugin directory
+description: >
+  Telegraf is a plugin-driven agent that collects, processes, aggregates, and writes metrics.
+  It supports four categories of plugins including input, output, aggregator, and processor.
+  View and search all available Telegraf plugins.
+menu:
+  telegraf_1_22_ref:
+
+    weight: 10
+weight: 6
+aliases:
+  - /telegraf/v1.22/plugins/plugins-list/
+  - /telegraf/v1.22/plugins/aggregators/
+  - /telegraf/v1.22/plugins/inputs/
+  - /telegraf/v1.22/plugins/outputs/
+  - /telegraf/v1.22/plugins/processors/
+  - /telegraf/v1.21/plugins/plugins-list/
+  - /telegraf/v1.21/plugins/aggregators/
+  - /telegraf/v1.21/plugins/inputs/
+  - /telegraf/v1.21/plugins/outputs/
+  - /telegraf/v1.21/plugins/processors/
+  - /telegraf/v1.20/plugins/plugins-list/
+  - /telegraf/v1.20/plugins/aggregators/
+  - /telegraf/v1.20/plugins/inputs/
+  - /telegraf/v1.20/plugins/outputs/
+  - /telegraf/v1.20/plugins/processors/
+  - /telegraf/v1.19/plugins/plugins-list/
+  - /telegraf/v1.19/plugins/aggregators/
+  - /telegraf/v1.19/plugins/inputs/
+  - /telegraf/v1.19/plugins/outputs/
+  - /telegraf/v1.19/plugins/processors/
+  - /telegraf/v1.18/plugins/plugins-list/
+  - /telegraf/v1.18/plugins/aggregators/
+  - /telegraf/v1.18/plugins/inputs/
+  - /telegraf/v1.18/plugins/outputs/
+  - /telegraf/v1.18/plugins/processors/
+  - /telegraf/v1.17/plugins/plugins-list/
+  - /telegraf/v1.17/plugins/aggregators/
+  - /telegraf/v1.17/plugins/inputs/
+  - /telegraf/v1.17/plugins/outputs/
+  - /telegraf/v1.17/plugins/processors/
+---
+
+Telegraf is a plugin-driven agent that collects, processes, aggregates, and writes metrics.
+It supports four categories of plugins including input, output, aggregator, processor, and external.
+
+{{< list-filters >}}
+
+**Jump to:**
+
+- [Input plugins](#input-plugins)
+- [Output plugins](#output-plugins)
+- [Aggregator plugins](#aggregator-plugins)
+- [Processor plugins](#processor-plugins)
+- [External plugins](#external-plugins)
+
+## Input plugins
+Telegraf input plugins are used with the InfluxData time series platform to collect
+metrics from the system, services, or third-party APIs.
+
+{{< telegraf/plugins type="input" >}}
+
+## Output plugins
+Telegraf processor plugins write metrics to various destinations.
+
+{{< telegraf/plugins type="output" >}}
+
+## Aggregator plugins
+Telegraf aggregator plugins create aggregate metrics (for example, mean, min, max, quantiles, etc.)
+
+{{< telegraf/plugins type="aggregator" >}}
+
+## Processor plugins
+Telegraf output plugins transform, decorate, and filter metrics.
+
+{{< telegraf/plugins type="processor" >}}
+
+## External plugins
+External plugins are external programs that are built outside of Telegraf that can run through an `execd` plugin.
+
+{{< telegraf/plugins type="external" >}}
diff --git a/content/telegraf/v1.22/release-notes-changelog.md b/content/telegraf/v1.22/release-notes-changelog.md
new file mode 100644
index 000000000..264bd40de
--- /dev/null
+++ b/content/telegraf/v1.22/release-notes-changelog.md
@@ -0,0 +1,3813 @@
+---
+title: Telegraf 1.22 release notes
+description: Important features and changes in the latest version of Telegraf.
+alias:
+  - /telegraf/v1.21/reference/release-notes/influxdb/
+menu:
+  telegraf_1_22_ref:
+
+    name: Release notes
+    weight: 60
+---
+## v1.22.2 [2022-4-28]
+
+- Update Go to 1.18.1.
+
+### Input plugin updates
+- InfluxDB Listener (`influxdb_listener`): Remove duplicate writes with upstream parser.
+- GNMI (`gnmi`): Use external xpath parser.
+- System (`system`): Reduce log level back to original level.
+
+## v1.22.2 [2022-4-25]
+
+- Allow Makefile to work on Windows.
+- Allow zero outputs when using `test-wait` parameter.
+
+## Input plugin updates
+- Aerospike (`aerospike`): Fix statistics query bug.
+- Aliyun CMS (`aliyuncms`): Ensure metrics accept array.
+- Cisco Telemetry MDT (`cisco_telemetry_mdt`):
+  - Align the default value for message size.
+  - Remove overly verbose info message.
+- GNMI (`gnmi`):
+  - Add mutex to lookup map.
+  - Use sprint to cast to strings.
+- Consul agent (`consul_agent`): Use correct auth token.
+- MySQL (`mysql`): Add `mariadb_dialect` to address the MariaDB differences in `INNODB_METRICS`.
+- SMART (`smart`): Correctly parse various numeric forms
+- Prometheus (`prometheus`): Moved from watcher to informer.
+
+## Output plugin updates
+- InfluxDB v2 (`influxdb_v2`): Improve error message.
+
+## Dependency updates
+- Update `github.com/Azure/azure-kusto-go` from 0.5.0 to 0.60.
+- Update `opentelemetry` from v0.2.10 to v0.2.17.
+- Update `go.opentelemetry.io/collector/pdata` from v0.48.0 to v0.49.0.
+- Update `github.com/aws/aws-sdk-go-v2/config` from 1.13.1 to 1.15.3
+- Update `github.com/aws/aws-sdk-go-v2/service/cloudwatchlogs`.
+- Update `github.com/aws/aws-sdk-go-v2/credentials` from 1.8.0 to 1.11.2.
+- Update `github.com/containerd/containerd` from v1.5.9 to v1.5.11.
+- Update `github.com/miekg/dns` from 1.1.46 to 1.1.48.
+- Update `github.com/gopcua/opcua` from v0.3.1 to v0.3.3
+- Update `github.com/aws/aws-sdk-go-v2/service/dynamodb`.
+- Update `github.com/xdg/scram` from 1.0.3 to 1.0.5.
+- Update `go.mongodb.org/mongo-driver` from 1.8.3 to 1.9.0.
+- Update `starlark 7a1108eaa012->d1966c6b9fcd`.
+
+## v1.22.1 [2022-4-6]
+
+- Update `gonum.org/v1/gonum` from 0.9.3 to 0.11.0.
+- Update `github.com/golang-jwt/jwt/v4` from 4.2.0 to 4.4.1.
+- Update `gopsutil` and associated dependencies for improved OpenBSD support.
+- Fix default value for logfile rotation interval.
+
+## Input plugin updates
+- Intel PMU (`intel_pmu`): Fix slow running intel-pmu test.
+- Cloud PubSub (`cloud_pubsub`): Skip longer integration tests on `-short` mode.
+- Cloud PubSub Push (`cloud_pubsub_push`): Reduce timeouts and sleeps.
+- SQL Server (`sqlserver`): Fix inconsistencies in `sql*Requests` queries.
+- ZFS (`zfs`): Fix redundant pool tag.
+- vSphere (`vsphere`): Update debug message information.
+
+## Output plugin updates
+- Azure Monitor (`azure_monitor`): Include body in error message.
+- HTTP (`http`): Switch HTTP 100 test case values.
+
+## Processor plugin updates
+- TopK (`topk`) Clarify the `k` and `fields` parameters.
+
+## New external plugins
+- [PSI External Plugin](https://github.com/gridscale/linux-psi-telegraf-plugin/blob/main/README.md)(`external.psi`) - Contributed by [@ajfriesen](https://github.com/ajfriesen).
+
+## v1.22.0 [2022-3-22]
+
+## Features
+
+- Add `autorestart` and `restartdelay` flags to Windows service
+- Add builds for `riscv64`.
+- Add file version and icon to `win.exe`.
+- Add `systemd` notify support.
+- Check TLS configuration early to catch missing certificates.
+- Implement collection offset.
+- `common.auth`: HTTP basic auth.
+- `common.cookie`: Support headers with cookie auth.
+- `common.proxy`: Add `socks5` proxy support.
+- Improve error logging on plugin initialization.
+
+## Bug fixes
+
+- Print loaded plugins and deprecations for once and test.
+- Remove signed MacOS artifacts.
+- Run `go mod tidy`.
+- Fix `prometheusremotewrite` wrong timestamp unit.
+- Fix sudden close ccaused by OPC UA inpu.
+- Update `containerd` to 1.5.9.
+- Update `go-sensu` to v2.12.0.
+- Update `gosmi` from v0.4.3 to v0.4.4.
+- Update parsing logic of `config.duration`.
+- Update precision parameter default value.
+- Use `sha256` for rpm digest.
+- Warning output when running with `--test`.
+- Graceful shutdown of Telegraf with Windows service.
+- Add push-only updated values flag to histogram aggregator.
+- `common.cookie`: Address flaky tests in cookie_test.go and graylog_test.go.
+- `common.shim`: Linter fixes.
+- Do not save cache on i386 builds.
+- Add error msg for missing environment variables in configuration file.
+- Fix panic in parsers due to missing log for all plugins using `setparserfunc`.
+- Grab table columns more accurately.
+- Improve parser tests by using `go-cmp/cmp`.
+- Linter fixes for `config/config.go`.
+- Log error when loading mibs.
+- Fix Mac signing issue with arm64.
+
+## New plugins
+
+### Inputs
+
+- [Hashicorp Consul Agent Input Plugin](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/consul_metrics)(`consul_agent`) - Contributed by [@efbar](https://github.com/efbar).
+- [Hashicorp Nomad Input Plugin](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/nomad)(`nomad`) - Contributed by [@efbar](https://github.com/efbar).
+- [Hashicorp Vault Input Plugin](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/vault)(`vault`) - Contributed by [@efbar](https://github.com/efbar).
+- [Hugepages Input Plugin](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/hugepages)(`hugepages`) - Contributed by [@zak-pawel](https://github.com/zak-pawel).
+- [Mock Input Plugin](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/mock)(`mock`) - Contributed by [InfluxData](https://github.com/influxdata).
+- [Redis Sentinel Input Plugin](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/redis_sentinel)(`redis_sentinel`) - Contributed by [@spideyfusion](https://github.com/spideyfusion).
+- [Socketstat Input Plugin](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/socketstat)(`socketstat`) - Contributed by [@sajoupa](https://github.com/sajoupa).
+- [XtremIO Input Plugin](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/xtremio)(`xtremio`) - Contributed by [@cthiel42](https://github.com/cthiel42).
+
+### Processors
+
+- [Noise Processor](https://github.com/influxdata/telegraf/tree/master/plugins/processors/noise) (`noise`) - Contributed by [@wizarq](https://github.com/wizarq).
+
+### Input plugin updates
+
+- Aerospike (`aerospike`): Update `github.com/aerospike/aerospike-client-go` from 1.27.0 to 5.7.0.
+- Bond (`bond`): Add additional stats.
+- Directory Monitor (`directory_monitor`):
+  - Update `djherbis/times` and fix `dependabot`.
+  - Plugin restructuring.
+- Disk (`disk`): Fix missing storage in container.
+- Docker (`docker`):
+  - Keep field type of `tasks_desired` the same.
+  - Update memory usage calculation.
+  - Update client API version.
+- ECS (`ecs`): Use current time as timestamp.
+- Execd `execd`: Add newline for Prometheus parsing.
+- File (`file`): Statefull parser handling.
+- GNMI (`gnmi`): Add dynamic tagging.
+- Graylog (`graylog`):
+  - Add `toml` tags.
+  - Add `timeout-setting`.
+  - Update documentation to use current URLs.
+- HTTP (`http`): Ensure http body is empty.
+- HTTP Listener v2 (`http_listener_v2`): Revert deprecation.
+- Internet speed (`internet_speed`): Add caching.
+- IPset (`ipset`): Fix crash when command not found.
+- JSON V2 (`json_v2`):
+  - Allow multiple optional objects.
+  - Use raw values for timestamps.
+- Kibana (`kibana`): Add `heap_size_limit` field.
+- Logparser (`logparser`):
+  - Add comment.
+  - Fix panic due to missing log.
+- MDStat (`mdstat`): Fix when sync is less than 10%.
+- Memcached (`memcached`): Gather additional stats.
+- Modbus `modbus`:
+    - Make Telegraf compile on Windows with golang 1.16.2.
+    - Re-enable openbsd support.
+    - Update documentation.
+    - Add `per-request` tags.
+    - Support multiple slaves (gateway feature).
+- MQTT Consumer (`mqtt_consumer`): Topic extracting no longer requires all three fields.
+- NFS Client (`nfsclient`): Add new field.
+- NTPQ (`ntpq`): Correctly read long poll output.
+- OPCUA (`opcua`):
+  - Accept non-standard OK status by implementing a configurable workaround.
+  - Add more data to error log.
+  - Remove duplicate addition of fields.
+- OpenLDAP (`openldap`): Update go-ldap to v3.4.1.
+- OpenStack (`openstack`): Fix typo.
+- OpenWeatherMap (`openweathermap`): Add `feels_like` field.
+- PHPfpm (`phpfpm`): Ensure CI tests runs against i386.
+- PostgreSQL (`postgresql`): Add option to disable prepared statements.
+- SMART (`smart`): Add concurrency configuration option, support and lint fixes.
+- SNMP `(snmp`):
+  - Respect number of retries configured.
+  - Use the correct path when evaluating symlink.
+  - Add option to select translator.
+  - Check index before assignment.
+  - Do not require networking during tests.
+  - Ensure folders do not get loaded more than once.
+  - Fix panic due to no module.
+  - Fix errors if mibs folder doesn't exist.
+  - Optimize locking for mibs loading.
+- SNMP Trap (`snmp_trap`):
+  - Collapsed fields by calling more in-depth function.
+  - Deprecate unused timeout configuration option.
+- SQL (`sql`): Add Clickhouse driver.
+- StatsD (`statsd`): Sanitize names.
+- Syslog (`syslog`): Add rfc3164 to rfc5424 translation to docs.
+- System (`system`): Remove verbose logging.
+- Windows Performance Counter (`win_perf_counter`):
+  - Allow errors to be ignored.
+  - Implemented support for reading raw values, added tests, and  update documentation.
+- X.509 Certificate (`x509_cert`):
+  - Mark `testgatherudpcert` as an integration test.
+  - Add `exclude_root_certs` option.
+- ZFS (`zfs`): Pool detection and metrics gathering for ZFS 2.1.x.
+
+
+### Output plugin updates
+
+- AMQP (`amqp`): Check for nil client before closing.
+- ElasticSearch (`elasticsearch`):
+  - Implement `nan` and `inf` handling.
+  - Add bearer token support.
+- Graylog (`graylog`): Fix to field prefixes.
+- Groundwork (`groundwork`):
+  - Set `nextchecktime` to `lastchecktime`.
+  - Update SDK and improve logging.
+  - Process group tag.
+- InfluxDB V2 (`influxdb_v2`): Include bucket name in error messages.
+- SQL (`sql`): Fix unsigned settings.
+- Stackdriver (`stackdriver`): Cumulative interval start times.
+- Syslog (`syslog`): Correctly set trailer.
+- Timestream (`timestream`): Fix batching logic with write record and introduce concurrent requests.
+- Datadog (`datadog`): Add compression.
+- HTTP (`http`):
+  - Add optional list of non-retryable status codes.
+  - Support AWS managed service for Prometheus.
+- Websocket `websocket`: `socks5` proxy support.
+- Wavefront (`wavefront`):
+    - Flush sender on error to clean up broken connections.
+    - Run `gofmt`.
+    - Fix panic if no mibs folder is found.
+
+## Parser plugin updates
+
+- CSV (`csv`):
+  - Empty import tzdata for Windows binaries.
+  - Fix typo.
+- Ifname (`ifname`):
+  - Eliminate mib dependency.
+  - Parallelism fix.
+- JSON V2 (`parsers.json_v2`):
+  - Allow optional paths and handle wrong paths correctly.
+  - Check if gpath exists and support optional in fields/tags.
+  - Fixes to timestamp setting.
+- Nagios (`nagios`): Use real error for logging.
+- XPath (`xpath`):
+  - Handle duplicate registration of protocol-buffer files gracefully.
+  - Fix typo.
+
+### Dependency updates
+
+- Update `github.com/azure/azure-kusto-go` from 0.5.0 to 0.5.2.
+- Update `github.com/nats-io/nats-server/v2` from 2.7.3 to 2.7.4.
+- Update `github.com/shopify/sarama` from 1.29.1 to 1.32.0.
+- Update `github.com/shirou/gopsutil`/v3 from 3.21.12 to 3.22.2.
+- Update `github.com/aws/aws-sdk-go-v2/feature/ec2/imds`.
+- Update `github.com/miekg/dns` from 1.1.43 to 1.1.46.
+- Update `github.com/aws/aws-sdk-go-v2/service/dynamodb`.
+- Update `github.com/nats-io/nats-server/v2` from 2.7.2 to 2.7.3.
+- Update `github.com/aws/aws-sdk-go-v2/config` from 1.8.3 to 1.13.1.
+- Update `github.com/testcontainers/testcontainers-go`.
+- Update `github.com/aws/aws-sdk-go-v2/service/cloudwatchlogs`.
+- Update `github.com/aws/aws-sdk-go-v2/feature/ec2/imds`.
+- Update `github.com/wavefronthq/wavefront-sdk-go` from 0.9.9 to 0.9.10.
+- Update `github.com/clickhouse/clickhouse-go` from 1.5.1 to 1.5.4.
+- Update `k8s.io/api` from 0.23.3 to 0.23.4.
+- Update `cloud.google.com/go/pubsub` from 1.17.1 to 1.18.0.
+- Update `github.com/newrelic/newrelic-telemetry-sdk-go`.
+- Update `github.com/aws/aws-sdk-go-v2/service/dynamodb` from 1.5.0 to 1.13.0.
+- Update `github.com/sensu/sensu-go/api/core/v2` from 2.12.0 to 2.13.0.
+- Update `github.com/gophercloud/gophercloud` from 0.16.0 to 0.24.0.
+- Update `github.com/jackc/pgx/v4` from 4.14.1 to 4.15.0.
+- Update `github.com/aws/aws-sdk-go-v2/service/sts` from 1.7.2 to 1.14.0.
+- Update all `go.opentelemetry.io` dependencies.
+- Update `github.com/signalfx/golib/v3` from 3.3.38 to 3.3.43.
+- Update `github.com/aliyun/alibaba-cloud-sdk-go`.
+- Update `github.com/denisenkom/go-mssqldb` from 0.10.0 to 0.12.0.
+- Update `github.com/gopcua/opcua` from 0.2.3 to 0.3.1.
+- Update `github.com/nats-io/nats-server/v2` from 2.6.5 to 2.7.2.
+- Update `k8s.io/client-go` from 0.22.2 to 0.23.3.
+- Update `github.com/aws/aws-sdk-go-v2/service/kinesis` from 1.6.0 to 1.13.0.
+- Update `github.com/benbjohnson/clock` from 1.1.0 to 1.3.0.
+- Update `github.com/vmware/govmomi` from 0.27.2 to 0.27.3.
+- Update `github.com/prometheus/client_golang` from 1.11.0 to 1.12.1.
+- Update `go.mongodb.org/mongo-driver` from 1.7.3 to 1.8.3.
+- Update `github.com/google/go-cmp` from 0.5.6 to 0.5.7.
+- Update `go.opentelemetry.io/collector/model` from 0.39.0 to 0.43.2.
+- Update `github.com/multiplay/go-ts3` from 1.0.0 to 1.0.1.
+- Update `cloud.google.com/go/monitoring` from 0.2.0 to 1.2.0.
+- Update `github.com/vmware/govmomi` from 0.26.0 to 0.27.2.
+- Update `google.golang.org/api` from 0.54.0 to 0.65.0.
+- Update `github.com/antchfx/xmlquery` from 1.3.6 to 1.3.9.
+- Update `github.com/nsqio/go-nsq` from 1.0.8 to 1.1.0.
+- Update `github.com/prometheus/common` from 0.31.1 to 0.32.1.
+- Update `cloud.google.com/go/pubsub` from 1.17.0 to 1.17.1.
+- Update `github.com/influxdata/influxdb-observability/influx2otel` from 0.2.8 to 0.2.10.
+- Update `github.com/shirou/gopsutil/v3` from 3.21.10 to 3.21.12.
+- Update `github.com/jackc/pgx/v4` from 4.6.0 to 4.14.1.
+- Update `github.com/azure/azure-event-hubs-go/v3` from 3.3.13 to 3.3.17.
+- Update `github.com/gosnmp/gosnmp` from 1.33.0 to 1.34.0.
+- Update `github.com/hashicorp/consul/api` from 1.9.1 to 1.12.0.
+- Update `github.com/antchfx/xpath` from 1.1.11 to 1.2.0.
+- Update `github.com/antchfx/jsonquery` from 1.1.4 to 1.1.5.
+- Update `github.com/prometheus/procfs` from 0.6.0 to 0.7.3.
+- Update `github.com/aws/aws-sdk-go-v2/service/cloudwatchlogs` from 1.5.2 to 1.12.0.
+- Update `github.com/kardianos/service` from 1.0.0 to 1.2.1.
+- Update `github.com/couchbase/go-couchbase` from 0.1.0 to 0.1.1.
+- Update `github.com/pion/dtls/v2` from 2.0.9 to 2.0.13.
+- Update `github.com/eclipse/paho.mqtt.golang` from 1.3.0 to 1.3.5.
+
+## v1.21.4 [2022-2-16]
+
+- Update to Go 1.17.7 to address [three security issues](https://groups.google.com/g/golang-announce/c/SUsQn0aSgPQ/m/gx45t8JEAgAJ?pli=1) in the library.
+- Update all `go.opentelemetry.io` from 0.24.0 to 0.27.0.
+- Update `github.com/signalfx/golib/v3` from 3.3.38 to 3.3.43.
+- Update `github.com/aliyun/alibaba-cloud-sdk-go` from 1.61.1004 to 1.61.1483.
+- Update `github.com/denisenkom/go-mssqldb` from 0.10.0 to 0.12.0.
+- Update `github.com/gopcua/opcua` from 0.2.3 to 0.3.1.
+- Update `github.com/nats-io/nats-server/v2` from 2.6.5 to 2.7.2.
+- Update `k8s.io/client-go` from 0.22.2 to 0.23.3.
+- Update `github.com/aws/aws-sdk-go-v2/service/kinesis` from 1.6.0 to 1.13.0.
+- Update `github.com/benbjohnson/clock` from 1.1.0 to 1.3.0.
+- Update `github.com/Azure/azure-kusto-go` from 0.5.0 to 0.5.2.
+- Update `github.com/vmware/govmomi` from 0.27.2 to 0.27.3.
+- Update `github.com/prometheus/client_golang` from 1.11.0 to 1.12.1.
+- Update `go.mongodb.org/mongo-driver` from 1.7.3 to 1.8.3.
+- Update `github.com/google/go-cmp` from 0.5.6 to 0.5.7.
+- Update `go.opentelemetry.io/collector/model` from 0.39.0 to 0.43.2.
+- Update `github.com/multiplay/go-ts3` from 1.0.0 to 1.0.1.
+- Update `cloud.google.com/go/monitoring` from 0.2.0 to 1.2.0.
+- Update `github.com/vmware/govmomi` from 0.26.0 to 0.27.2.
+
+### Input plugin updates
+- Docker (`docker`): Update memory usage calculation.
+- ECS (`ecs`): Use current time as timestamp.
+- SNMP (`snmp`): Ensure folders do not get loaded more than once.
+- Windows Performance Counters (`win_perf_counters`): Add deprecated warning and version.
+
+### Output plugin updates
+- AMQP (`amqp`): Check for nil client before closing.
+- Azure Data Explorer (`azure_data_explorer`): Lower RAM usage.
+- ElasticSearch (`elasticsearch`): Add scheme to fix error in sniffing option.
+
+### Parser plugin updates
+- JSON v2 (`json_v2`):
+  - Fix timestamp change during execution.
+  - Fix incorrect handling of `timestamp_path`.
+  - Allow optional paths and handle wrong paths correctly.
+
+### Serializer updates
+- Prometheus serializer (`prometheusremotewrite`): Use correct timestamp unit.
+
+### New External Plugins
+- [apt](https://github.com/x70b1/telegraf-apt/blob/master/README.md)(`telegraf-apt`) - Contributed by [@x70b1](https://github.com/x70b1).
+- [knot](https://github.com/x70b1/telegraf-knot/blob/master/README.md)(`telegraf-knot`) - Contributed by [@x70b1](https://github.com/x70b1).
+
+## v1.21.3 [2022-1-27]
+
+- Update `grpc` module to v1.44.0.
+- Update `google.golang.org/api` module from 0.54.0 to 0.65.0.
+- Update `antchfx/xmlquery` module from 1.3.6 to 1.3.9.
+- Update `nsqio/go-nsq` module from 1.0.8 to 1.1.0.
+- Update `prometheus/common` module from 0.31.1 to 0.32.1.
+- Update `cloud.google.com/go/pubsub` module from 1.17.0 to 1.17.1.
+- Update `influxdata/influxdb-observability/influx2otel` module from 0.2.8 to 0.2.10.
+- Update `shirou/gopsutil/v3` module from 3.21.10 to 3.21.12.
+- Update `jackc/pgx/v4` module from 4.6.0 to 4.14.1.
+- Update `Azure/azure-event-hubs-go/v3` module from 3.3.13 to 3.3.17.
+- Update `gosnmp/gosnmp` module from 1.33.0 to 1.34.0.
+- Update `hashicorp/consul/api` module from 1.9.1 to 1.12.0.
+- Update `antchfx/xpath` module from 1.1.11 to 1.2.0.
+- Update `antchfx/jsonquery` module from 1.1.4 to 1.1.5.
+- Update `prometheus/procfs` module from 0.6.0 to 0.7.3.
+- Update `aws/aws-sdk-go-v2/service/cloudwatchlogs` module from 1.5.2 to 1.12.0.
+- Update `kardianos/service` module from 1.0.0 to 1.2.1.
+- Update `couchbase/go-couchbase` module from 0.1.0 to 0.1.1.
+- Update `pion/dtls/v2` module from 2.0.9 to 2.0.13.
+- Update `containerd/containerd` module to 1.5.9.
+
+### Input plugin updates
+- Execd (`execd`): Resolve a Promethues text format parsing error.
+- IPset (`ipset`): Prevent panic from occurring after startup.
+- OPC-UA (`opc_ua`): Fix issue where fields were being duplicated.
+- HTTP (`http`): Prevent server side error message.
+- SNMP (`snmp`): Fix error when a MIBs folder doesn't exist.
+- SNMP Trap (`snmp_trap`): Fix translation of partially resolved OIDs.
+
+### Output plugin updates
+- AMQP (`amqp`): Update to avoid connection leaks.
+- Timestream (`timestream`):
+  - Fix an issue with batching logic of write records.
+  - Introduce concurrent requests.
+- Stackdriver (`stackdriver`): Send correct interval start times for all counter metrics.
+- Syslog (`syslog`): Correctly set the ASCII trailer per [RFC 6587](https://datatracker.ietf.org/doc/html/rfc6587).
+
+### Parser plugin updates
+- Nagios (`nagios`): Log correct errors when executing commands to aid in debugging.
+- JSON v2 (`json_v2`): Fix timestamp precision when using `unix_ns` timestamp format.
+- Wavefront (`wavefront`): Add missing setting `wavefront_disable_prefix_conversion`.
+
+
+## v1.21.2 [2022-1-5]
+
+- Add arm64 MacOS builds for M1 devices.
+- Add RISC-V64 Linux builds.
+- Complete numerous changes to CircleCI config to ensure more timely completion and more clear execution flow.
+- Update `github.com/djherbis/times` module from v1.2.0 to v1.5.0.
+- Update `github.com/go-ldap/ldap/v3` module from v3.1.0 to v3.4.1.
+- Update `github.com/gwos/tcg/sdk` module to v0.0.0-20211223101342-35fbd1ae683c.
+
+
+### Input plugin updates
+- Disk (`disk`): Fix issue of missing disks when running Telegraf in a container.
+- DPDK (`dpdk`): Add a note to documentation about socket availability.
+- Logparser (`logparser`): Resolve  panic in the logparser plugins due to a missing `Log`.
+- SNMP (`snmp`):
+  - Resolve panic due to a missing `gosmi` module.
+  - Resolve panic to check the index before assignment where a floating `::` exists.
+  - Resolve a panic when no MIBs folder was found.
+  - Ensure the module load order to avoid an SNMP marshal error.
+  - Now more accurately grabs MIB table columns.
+  - Networking no longer required during tests.
+- SNMP Trap (`snmp_trap`): Documented deprecation of the `timeout` setting.
+
+
+### Parser plugin updates
+- CSV (`csv`): Use an empty import of `tzdata` to correctly set the time zone.
+
+
+## v1.21.1 [2021-12-16]
+
+## Bug fixes
+- Fix panic in parsers due to missing log.
+- Update `go-sensu module` to v2.12.0
+- Fix typo in OpenStack input plugin.
+
+## Features
+- Add SMART input plugin concurrency configuration option, `nvme-cli v1.14+` support, and lint fixes.
+
+## v1.21 [2021-12-15]
+
+{{% note %}}
+The signing for RPM digest has changed to use sha256 to improve security. Due to this change, RPM builds might not be compatible with RHEL6 and older releases. (Telegraf only supports releases in RHEL production.)
+{{% /note %}}
+
+- Restart Telegraf service if it's already running and upgraded via RPM.
+- Print loaded plugins and deprecations for once and test flags.
+- Update `eclipse/paho.mqtt.golang` module from 1.3.0 to 1.3.5.
+- Shutdown Telegraf gracefully on Windows Service.
+- Skip `knxlistener` when writing the sample configuration file.
+- Update `nats-sever` to support `openbsd`.
+- Revert unintented corruption of the Makefile.
+- Filter client certificates by DNS names.
+- Update `etc/telegraf.conf` and `etc/telegraf_windows.conf`.
+- Add full metadata to configuration for `common.kafka`.
+- Update `google.golang.org/grpc` module from 1.39.1 to 1.40.0.
+
+## Input plugin updates
+- Cloudwatch (`cloudwatch`): Fix metrics collection.
+- CPU (`cpu`): Update `shirou/gopsutil` from v2 to v3.
+- Directory Monitor (`directory_monitor`):
+  - Fix to when when data format is CSV and `csv_skip_rows>0` and `csv_header_row_count>=1`.
+  - Adds the ability to create and name a tag containing the filename.
+- ElasticSearch (`elasticsearch_query`): Add debug query output.
+- HTTP Listener v2: (`http_listener_v2`): Fix panic on close to check that Telegraf is closing.
+- Kubernetes Inventory (`kube_inventory`): Set TLS server name configuration properly.
+- Modbus (`modbus`): Update connection settings (serial).
+- MQTT Consumer (`mqtt_consumer`):
+  - Extracting no longer requires all three fields
+  - Enable extracting tag values from MQTT topics
+- OPC UA (`opc_ua`):
+  - Fix sudden closing of Telegraf.
+  - Allow user to select the source for the metric timestamp.
+- Prometheus (`prometheus`):
+  - Check error before defer.
+  - Add `ignore_timestamp` option.
+- Puppet (`puppetagent`): Add measurements from puppet 5.
+- SNMP (`snmp`):
+  - Update snmp plugin to respect number of retries configured.
+  - Optimize locking for SNMP MIBs loading.
+  - Update to use gosmi.
+  - Remove `snmptranslate` from READme and fix default path.
+  - Merge tables with different indexes.
+- StatsD (`statsd`): Fix parse error.
+- Sysstat (`sysstat`): Use unique temporary file.
+- Windows Performance Counters (`win_perf_counters`): Add setting to ignore localization.
+- Windows Services (`win_services`): Add exclude filter.
+- ZFS (`zfs`): Pool detection and metrics gathering for ZFS >= 2.1.x
+
+## Output plugin updates
+- Register `bigquery` to all output plugins.
+- Azure Data Explorer (`azure_data_explorer`):
+  - Add option to skip table creation.
+  - Add `json_timestamp_layout` option.
+- ElasticSearch (`elasticsearch`): Implement NaN and inf handling.
+- Graylog (`graylog`):
+  - Ensure graylog spec fields not prefixed with `_`.
+  - Failing test due to port already in use.
+  - Mute UDP/TCP tests by marking them as integration.
+  - TLS support and message format.
+  - Add TCP support.
+- HTTP (`http`): Add `use_batch_format`.
+- InfluxDB V2 (`influxdb_v2`): Add retry to 413 errors with InfluxDB output.
+- Wavefront (`wavefront`): Flush sender on error to clean up broken connections.
+
+
+## Parser plugin updates
+- XPath (`xpath`): Handle duplicate registration of protocol-buffer files gracefully
+- JSON v2 (`json_v2`):
+  - Parser timestamp setting order.
+  - Remove dead code.
+  - Support defining field/tag tables within an object table.
+
+## Processor plugin updates
+- IfName (`ifname`):
+  - Eliminate MIB dependency.
+  - Parallelism fix.
+  - Add more details to log messages.
+- Starlark (`starlark`): Example for processing `sparkplug_b` messages.
+- RegEx (`regex`): Extend to allow renaming of measurements, tags, and fields.
+
+## Aggregator plugin updates
+- Implement deprecation infrastructure
+- Add support of aggregator as Starlark script
+
+## New plugins
+
+#### Inputs
+
+- [Intel PMU Input Plugin](https://github.com/influxdata/telegraf/blob/master/plugins/inputs/intel_pmu/README.md)(`intel_pmu`) - Contributed by [@bkoltowski](https://github.com/bkotlowski).
+- [Logical Volume Manager Input Plugin](https://github.com/influxdata/telegraf/blob/master/plugins/inputs/lvm/README.md)(`lvm`) - Contributed by @InfluxData.
+- [OpenStack Input Plugin](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/openstack)(`openstack`) - Contributed by [@singamSrikar].(https://github.com/singamSrikar).
+
+### Outputs
+- [Azure Event Hubs Output Plugin](https://github.com/influxdata/telegraf/blob/master/plugins/outputs/event_hubs/README.md)(`event_hubs`) - Contributed by [@tomconte](https://github.com/tomconte).
+- [GroundWork Output Plugin](https://github.com/influxdata/telegraf/blob/master/plugins/outputs/groundwork/README.md)(`groundwork`) - Contributed by [@VladislavSenkevich)(https://github.com/VladislavSenkevich).
+- [MongoDB Output Plugin](https://github.com/influxdata/telegraf/blob/master/plugins/outputs/mongodb/README.md)(`mongodb`) - Contributed by [@bustedware](https://github.com/bustedware).
+
+#### Aggregator
+- [Starlark Aggregator](https://github.com/influxdata/telegraf/blob/master/plugins/aggregators/starlark/README.md)(`starlark`) - Contributed by [@essobedo](https://github.com/essobedo).
+
+## v1.20.4 [2021-11-17]
+
+- Update `BurntSushi/toml` from 0.3.1 to 0.4.1.
+- Update `gosnmp` module from 1.32 to 1.33.
+- Update `go.opentelemetry.io/otel` from v0.23.0 to v0.24.0.
+- Fix plugin linters.
+
+### Input plugin updates
+- Cisco Model-Driven Telemetry (`cisco_telemetry_mdt`): Move to new protobuf library.
+- InfluxDB (`influxdb`): Update input schema docs.
+- Intel RDT (`intel_rdt`): Correct the timezone to use local timezone by default instead of UTC from metrics gathered from the `pqos` tool.
+- IPMI Sensor (`ipmi`): Redact passwords in log files to maintain security.
+- Modbus (`modbus`): Do not build on OpenBSD.
+- MySQL (`mysql`):
+  - Fix type conversion follow-up.
+  - Correctly set the default paths.
+- NVIDIA SMI (`nvidia_smi`): Correctly set the default paths.
+- Proxmox (`proxmox`): Parse the column types of the server status.
+- SQL Server (`sqlserver`): Add elastic pool in supported versions.
+
+### Output plugin updates
+- Loki (`loki`): Include the metric name as a label for improved query performance and metric filtering.
+
+## v1.20.3 [2021-10-28]
+
+- Update Go to 1.17.2.
+- Update `gjson` module to v1.10.2.
+- Update Snowflake database driver module to 1.6.2.
+- Update `github.com/apache/thrift` module from 0.14.2 to 0.15.0.
+- Update `github.com/aws/aws-sdk-go-v2/config` module from 1.8.2 to 1.8.3.
+- Update `github.com/Azure/azure-kusto-go` module from 0.3.2 to 0.4.0.
+- Update `github.com/docker/docker` module from 20.10.7+incompatible to 20.10.9+incompatible.
+- Update `github.com/golang-jwt/jwt/v4` module from 4.0.0 to 4.1.0.
+- Update `github.com/jaegertracing/jaeger` module from 1.15.1 to 1.26.0.
+- Update `github.com/prometheus/common` module from 0.26.0 to 0.31.1.
+
+### Input plugin updates
+- IPMI Sensor (`ipmi_sensor`): Redact IPMI password in logs.
+- Kube Inventory (`kube_inventory`):
+  - Do not skip resources with zero s/ns timestamps.
+  - Fix segfault in ingress, persistentvolumeclaim, statefulset.
+- Procstat (`procstat`): Revert and fix tag creation.
+- SQL Server (`sqlserver`): Add integration tests.
+- Amazon CloudWatch (`cloudwatch`): Use the AWS SDK v2 library.
+- ZFS (`zfs`): Check return code of zfs command for FreeBSD.
+- Ethtool (`ethtool`): Add normalization of tags.
+- Internet Speed (`internet_speed`): Resolve missing latency field.
+- Prometheus (`prometheus`):
+  - Decode Prometheus scrape path from Kubernetes labels.
+  -  Move err check to correct place.
+- Procstat (`procstat`): Correct conversion of int with specific bit size.
+- Webhooks (`webhooks`): Provide more fields.
+- MongoDB (`mongodb`): Solve compatibility issue when using 5.x relicaset.
+- Intel RDT (`intel_rdt`): Allow sudo usage.
+- MySQL (`mysql`): Fix inconsistent metric types.
+
+### Processor plugin updates
+- Starlark (`starlark`): Pop operation for non-existing keys.
+
+### New plugins
+
+#### External
+- [IBM DB2](https://github.com/bonitoo-io/telegraf-input-db2): Contributed by @sranka.
+- [Oracle Database](https://github.com/bonitoo-io/telegraf-input-oracle): Contributed by @sranka.
+
+## v1.20.2 [2021-10-07]
+
+- Fix makefile typo that prevented i386 tar and rpm packages from being built.
+
+### Input plugin updates
+- Cloudwatch (`cloudwatch`): Use new session API.
+- Stackdriver (`stackdriver`): Migrate to `cloud.google.com/go/monitoring/apiv3/v2`.
+
+### Parser plugin updates
+- JSON V2 (`json_v2`): Duplicate line_protocol when using object and fields.
+- Influx (`influx`): Fix memory leak.
+
+## v1.20.1 [2021-10-06]
+
+- Fix output buffer never completely flushing.
+- Update `k8s.io/apimachinery` module to 0.22.2.
+- Update `consul` module to 1.11.0.
+- Update `github.com/testcontainers/testcontainers-go` module to 0.11.1.
+- Update `github.com/Azure/go-autorest/autorest/adal` module.
+- Update `github.com/Azure/go-autorest/autorest/azure/auth module` to 0.5.8.
+- Update `cloud.google.com/go/pubsub` module to 1.17.0.
+- Update `github.com/aws/smithy-go` module to 1.8.0.
+
+### Input plugin updates
+
+- ElasticSearch (`elasticsearch_query`): Add custom time/date format field.
+- OpenTelemetry (`opentelemetry`): Fix error returned to OpenTelemetry client.
+- Couchbase (`couchbase`): Fix insecure certificate validation.
+- MongoDB (`mongodb`): Fix panic due to nil dereference.
+- Intel RDT (`intel_rdt`): Prevent timeout when logging.
+- Procstat (`procstat`): Add missing tags.
+
+### Output plugin updates
+
+- Loki (`loki`): Update http_headers setting to match sample config.
+- MQTT (`mqtt`): Add "keep alive" config option and documentation around issue with eclipse/mosquito version.
+
+## v.1.20 [2021-09-16]
+
+- Update Go to 1.17.0
+- Update runc module to v1.0.0-rc95.
+- Migrate `dgrijalva/jwt-go` to `golang-jwt/jwt/v4`.
+- Update `thrift` module to 0.14.2 and `zipkin-go-opentracing` 0.4.5.
+- Update `cloud.google.com/go/pubsub` module to 1.15.0.
+- Update `github.com/tinylib/msgp` module to 1.1.6.
+
+
+### Input plugin updates
+
+- MongoDB (`mongodb`): Change command based on server version.
+- SQL (`sql`): Make timeout apply to single query.
+- SystemD Units (`systemd_units`): Add pattern support.
+- Cloudwatch (`cloudwatch`):
+  - Pull metrics from multiple AWS CloudWatch namespaces.
+  - Support AWS Web Identity Provider.
+- Modbus (`modbus`): Add support for RTU over TCP.
+- Procstat (`procstat`): Support cgroup globs and include `systemd` unit children.
+- Suricata (`suricata`): Support alert event type.
+- Prometheus (`prometheus`): Add ability to query Consul Service catalog.
+- HTTP Listener V2 (`http_listener_v2`): Allow multiple paths and add path_tag.
+- HTTP (`http`): Add cookie authentication.
+- Syslog (`syslog`): Add RFC 3164 support for BSD-style syslog messages.
+- Jenkins (`jenkins`): Add option to include nodes by name.
+- SNMP Trap (`snmp_trap`): Improve MIB lookup performance.
+- Smart (`smart`): Add power mode status.
+- New Relic (`newrelic`): Add option to override `metric_url`.
+
+
+### Output plugin updates
+
+- Dynatrace (`dynatrace`): Remove hardcoded int value.
+- InfluxDB v2 (`influxdb_v2`): Increase accepted retry-after header values.
+- SQL (`sql`): Add bool datatype.
+- Prometheus Client (`prometheus_client`): Add Landing page.
+- HTTP (`http`): Add cookie authentication.
+
+### Serializer plugin updates
+
+- Prometheus (`prometheus`): Update timestamps and expiration time as new data arrives.
+
+### Parser plugin updates
+
+- XPath (`xpath`): Add JSON, MessagePack, and Protocol-buffers format support.
+
+### New plugins
+
+#### Input
+
+- [Elasticsearch Query](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/elasticsearch_query) - Contributed by @lpic10
+- [Internet Speed Monitor](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/internet_speed) - Contributed by @ersanyamarya
+- [mdstat](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/mdstat) - Contributed by @johnseekins
+- [AMD ROCm System Management Interface (SMI)](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/amd_rocm_smi) - Contributed by @mconcas
+
+#### Output
+- [OpenTelemetry](https://github.com/influxdata/telegraf/tree/master/plugins/outputs/opentelemetry) - Contributed by @jacobmarble
+- [Azure Data Explorer](https://github.com/influxdata/telegraf/tree/master/plugins/outputs/azure_data_explorer) - Contributed by @minwal
+
+## v.1.19.3 [2021-08-19]
+
+- Update `sirupsen/logrus` module from 1.7.0 to 1.8.1.
+- Update `testcontainers/testcontainers-go` module from 0.11.0 to 0.11.1.
+- Update `golang/snappy` module from 0.0.3 to 0.0.4.
+- Update `aws/aws-sdk-go-v2` module from 1.3.2 to 1.8.0.
+- Update `sensu/go` module to v2.9.0.
+- Update `hashicorp/consul/api` module to 1.9.1.
+
+### Input plugin updates
+- Prometheus (`prometheus`): Fix Kubernetes pod discovery.
+- Redis (`redis`) Improve redis commands documentation.
+- Clickhouse (`clickhouse`): Fix panic, improve handling empty result set.
+- OPC UA: (`opcua`):
+  - Avoid closing session on a closed connection.
+  - Fix reconnection regression introduced in 1.19.1.
+  - Don't skip good quality nodes after encountering bad quality node.
+- Kubernetes Inventory (`kube_inventory`): Fix k8s nodes and pods parsing error.
+- PostgreSQL (`postgresql`): Normalize unix socket path.
+- vSphere (`vsphere`): Update `vmware/govmomi` module to v0.26.0 in order to support vSphere 7.0.
+
+### Output plugin updates
+- Loki (`loki`): Sort logs by timestamp before writing to Loki.
+- CrateDB (`cratedb`): Replace dots in tag keys with underscores.
+
+### Processor plugin updates
+- AWS (`aws`): Refactor EC2 init.
+
+## v.1.19.2 [2021-07-28]
+
+- Update Go to 1.16.6.
+- Linter fixes.
+- Update `dynatrace-metric-utils-go` module to v0.2.0.
+- Detect changes to configuration and reload Telegraf.
+
+### Input plugin updates
+- CGroup (`couchbase`): Allow for multiple keys when parsing cgroups.
+- Kubernetes (`kubernetes`): Update plugin to attach pod labels to the `kubernetes_pod_volume` and `kubernetes_pod_network` metrics.
+- Kubernetes Inventory (`kube_inventory`): Fix a segmentation fault when selector labels were not present on a persistent volume claim.
+- MongoDB (`mongodb`): Switch to official `mongo-go-driver` module to fix an SSL authentication failure.
+- NSQ Consumer (`couchbase`): Fix a connection error when attempting to connect to an empty list of servers.
+- Prometheus (`prometheus`): Fix Prometheus cAdvisor authentication.
+- SQL (`sql`): Fix issue when handling a boolean column.
+- SQL Server (`sqlserver`):
+  - Add TempDB troubleshooting stats and missing v2 query metrics.
+  - Update to provide more detailed error messaging.
+- StatsD (`statsd`): Fix a regression that didn't allow integer percentiles.
+- x509 Certificate (`x509_cert`): Fix an issue where plugin would hang indefinitely to a UDP connection.
+
+### Output plugin updates
+- Dynatrace Output (`dynatrace`):
+  - Update plugin to allow optional default dimensions.
+  - Fix a panic caused by uninitialized `loggedMetrics` map.
+- InfluxDB (`influxdb`): Fix issue where metrics were reporting as written but not actually written.
+
+### Processor plugin updates
+- IfName (`ifname`): Fix issue with SNMP empty metric name.
+
+### Parser plugin updates
+- JSON v2 (`json_v2`):
+    - Simplify how nesting is handled in parser.
+    - Add support for large uint64 and int64 numbers.
+    - Fix an issue to handle nested objects in arrays properly.
+
+
+## v.1.19.1 [2021-07-07]
+
+- Update nat-server module to v2.2.6.
+- Update apimachinary module to v0.21.1.
+- Update jwt module to v1.2.2 and jwt-go module to v3.2.3.
+- Update couchbase module to v0.1.0.
+- Update signalfx module to v3.3.34.
+- Update gjson module to v1.8.0.
+- Linter fixes.
+
+### Input plugin updates
+- SQL Server (`sqlserver`): Require authentication method to be specified.
+- Kube Inventory (`kube_inventory`): Fix segfault.
+- Couchbase (`couchbase`): Fix panic.
+- KNX (`knx_listener`): Fix nil pointer panic.
+- Procstat (`procstat`): Update gopsutil module to fix panic.
+- RabbitMQ (`rabbitmq`) Fix JSON unmarshall regression.
+- Dovecot (`dovecot`): Exclude read-timeout from being an error.
+- StatsD(`statsd`) Don't stop parsing after parsing error.
+- SNMP (`snmp`): Add a check for oid and name to prevent empty metrics.
+- (`x509_cert`):
+  - Fix 'source' tag for https.
+  - Fix SNI support.
+
+### Output plugin updates
+- (`http`): Fix toml error when parsing insecure_skip_verify.
+
+### Parser plugin updates
+- (`json_v2`): Don't require tags to be added to included_keys.
+
+## v1.19.0 [2021-06-17]
+
+- Update Go to 1.16.5.
+
+### Bug fixes
+- Update pgx to v4. <!-- https://github.com/influxdata/telegraf/pull/9182 -->
+- Fix reading configuration files starting with HTTP: <!-- https://github.com/influxdata/telegraf/pull/9275 -->
+- `serializers.prometheusremotewrite`: Update dependency and remove tags with empty values. <!-- https://github.com/influxdata/telegraf/pull/9196 -->
+- `outputs.kafka`: Don't prevent telegraf from starting when there's a connection error. <!-- https://github.com/influxdata/telegraf/pull/9051 -->
+- `parsers.prometheusremotewrite`: Update prometheus dependency to v2.21.0. <!-- https://github.com/influxdata/telegraf/pull/8795 -->
+- `outputs.dynatrace`: Use dynatrace-metric-utils. <!-- https://github.com/influxdata/telegraf/pull/9295 -->
+- Many linter fixes. (Thanks @zak-pawel and all!)
+
+### Features
+- Configuration file environment variable can now be a URL. <!-- https://github.com/influxdata/telegraf/pull/8987 -->
+- Add named timestamp formats. <!-- https://github.com/influxdata/telegraf/pull/9087 -->
+- Allow multiple `--config` and `--config-directory` flags. <!-- https://github.com/influxdata/telegraf/pull/9007 -->
+
+### Plugin updates
+
+#### Input plugin updates
+- (`aliyuncms`): Add configuration option list of regions to query. <!-- https://github.com/influxdata/telegraf/pull/9156 -->
+- (`cisco_telemetry_mdt`): Add support for events and class based query. <!-- https://github.com/influxdata/telegraf/pull/8661 -->
+- (`cloudwatch`): Add wildcard support in dimensions configuration. <!-- https://github.com/influxdata/telegraf/pull/9136 -->
+- (`couchbase`): Add ~200 more Couchbase metrics via buckets endpoint. <!-- https://github.com/influxdata/telegraf/pull/9032 -->
+- (`dovecot`): Add support for Unix domain sockets. <!-- https://github.com/influxdata/telegraf/pull/9223 -->
+- (`http_listener_v2`): Add support for snappy compression <!-- https://github.com/influxdata/telegraf/pull/8966 -->
+- (`http`): Add OAuth2 to HTTP input. <!-- https://github.com/influxdata/telegraf/pull/9138 -->
+- (`kinesis_consumer`): Add `content_encoding` option with gzip and zlib support. <!-- https://github.com/influxdata/telegraf/pull/8891 -->
+- (`logstash`): Add support for version 7 queue statistics. <!-- https://github.com/influxdata/telegraf/pull/9080 -->
+- (`mongodb`): Optionally collect top statistics. <!-- https://github.com/influxdata/telegraf/pull/8861 -->
+- (`mysql`): Gather all MySQL channels. <!-- https://github.com/influxdata/telegraf/pull/5517 -->
+- (`ping`): Add an option to specify packet size. <!-- https://github.com/influxdata/telegraf/pull/9274 -->
+- (`sqlserver`): Add an optional health metric. <!-- https://github.com/influxdata/telegraf/pull/8544 -->
+- (`sqlserver`): Added `login_name`. <!-- https://github.com/influxdata/telegraf/pull/8351 -->
+- (`sqlserver`): Enable Azure Active Directory (AAD) authentication. <!-- https://github.com/influxdata/telegraf/pull/8822 -->
+- (`sqlserver`): input/sqlserver: Add service and save connection pools. <!-- https://github.com/influxdata/telegraf/pull/8596 -->
+- (`vsphere`): Add configuration option for the historical interval duration. <!-- https://github.com/influxdata/telegraf/pull/9276 -->
+- (`x509_)cert`: Wildcard support for certificate filenames. <!-- https://github.com/influxdata/telegraf/pull/6952 -->
+
+#### Output plugin updates
+- (`datadog`): Add HTTP proxy to DataDog output. <!-- https://github.com/influxdata/telegraf/pull/9297 -->
+- (`graphite`): Allow more characters in graphite tags. <!-- https://github.com/influxdata/telegraf/pull/9249 -->
+
+#### Parser plugin updates
+- (`prometheusremotewrite`): Add Starlark script for renaming metrics. <!-- https://github.com/influxdata/telegraf/pull/9074 -->
+- (`value`): Add custom field name configuration option. <!-- https://github.com/influxdata/telegraf/pull/8979 -->
+
+#### Processor plugin updates
+- (`enum`): Support `float64`. <!-- https://github.com/influxdata/telegraf/pull/8911 -->
+- (`starlark`): Add an example showing how to obtain IOPS from `diskio` input. <!-- https://github.com/influxdata/telegraf/pull/8996 -->
+- (`starlark`): Add `math` module. <!-- https://github.com/influxdata/telegraf/pull/9042 -->
+- (`starlark`): Add `time` module. <!-- https://github.com/influxdata/telegraf/pull/9004 -->
+- (`starlark`): Support nanosecond resolution timestamp. <!-- https://github.com/influxdata/telegraf/pull/9105 -->
+- (`strings`): Add UTF-8 sanitizer. <!-- https://github.com/influxdata/telegraf/pull/9118 -->
+
+### New plugins
+
+#### Input
+- [Alibaba CloudMonitor Service (Aliyun)](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/aliyuncms) - Contributed by @i-prudnikov
+- [Intel Data Plane Development Kit (DPDK)](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/dpdk) - Contributed by @p-zak
+- [KNX](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/knx_listener) - Contributed by @DocLambda
+- [OpenTelemetry](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/opentelemetry) - Contributed by @jacobmarble
+- [SQL](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/sql) - Contributed by @srebhan
+
+#### Output
+- [AWS Cloudwatch logs](https://github.com/influxdata/telegraf/tree/master/plugins/outputs/cloudwatch_logs) - Contributed by @i-prudnikov
+- [SQL](https://github.com/influxdata/telegraf/tree/master/plugins/outputs/sql) - Contributed by @illuusio
+- [Websocket](https://github.com/influxdata/telegraf/tree/master/plugins/outputs/websocket) - Contributed by @FZambia
+
+#### Parser
+- [Prometheus Remote Write](https://github.com/influxdata/telegraf/tree/master/plugins/parsers/prometheusremotewrite) - Contributed by @influxdata
+- [JSON V2](https://github.com/influxdata/telegraf/tree/master/plugins/parsers/json_v2) - Contributed by @influxdata
+
+#### External
+- [Big Blue Button](https://github.com/SLedunois/bigbluebutton-telegraf-plugin) - Contributed by @SLedunois
+- [dnsmasq](https://github.com/machinly/dnsmasq-telegraf-plugin) - Contributed by @machinly
+- [ldap_org and ds389](https://github.com/falon/CSI-telegraf-plugins) - Contributed by @falon
+- [x509_crl](https://github.com/jcgonnard/telegraf-input-x590crl) - Contributed by @jcgonnard
+
+## v1.18.3 [2021-05-21]
+
+- Add FreeBSD ARMv7 build.
+- Dependencies:
+  - Migrate from `soniah/gosnmp` to `gosnmp/gosnmp` v1.32.0.
+  - Migrate from `docker/libnetwork/ipvs` to `moby/ipvs`.
+  - Migrate from `ericchiang/k8s` to `kubernetes/client-go`.
+  - Update `hashicorp/consul/api` module to v1.8.1.
+  - Update `shirou/gopsutil` to v3.21.3.
+  - Update `microsoft/ApplicationInsights-Go` to v0.4.4
+  - Update `gogo/protobuf` to v1.3.2.
+  - Update `Azure/go-autorest/autorest/azure/auth` to v0.5.6 and `Azure/go-autorest/autorest` to v0.11.17.
+  - Update `collectd.org` to v0.5.0.
+  - Update `nats-io/nats.go` to v1.10.0.
+  - Update `golang/protobuf` to v1.5.1.
+
+
+### Input plugin updates
+
+- [Prometheus Input](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/prometheus): Add ability to set user agent when scraping Prometheus metrics.
+- [Kinesis Input](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/kinesis_consumer): Fix repeating parser error.
+- [SQL Server Input](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/sqlserver): Remove disallowed white space from `sqlServerRingBufferCPU` query.
+
+### Output plugin updates
+
+- [Elasticsearch Output](https://github.com/influxdata/telegraf/tree/master/plugins/outputs/elasticsearch/README.md): Add ability to to enable gzip compression.
+
+
+
+## v1.18.2 [2021-04-29]
+
+- Make JSON format compatible with nulls to ensure Telegraf successfully detects null values and returns an empty metric without error.
+- Update `common.shim` by changing `NewStreamParser` to accept larger inputs from scanner.
+
+### Input plugin updates
+
+- [APCUPSD Input](https://github.com/influxdata/telegraf/blob/release-1.18/plugins/inputs/apcupsd/README.md) (`apcupsd`):
+   Resolve an 'ALARMDEL' bug in a forked repository. This fix ensures the plugin works when `no alarm` delay duration is set.
+- [NFS Client Input](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/nfsclient) (`nfsclient`): Update to successfully collect metrics other than read and write.
+- [SNMP Input](https://github.com/influxdata/telegraf/blob/release-1.18/plugins/inputs/snmp/README.md) (`snmp`): Update to log snmpv3 auth failures.
+- [VMware vSphere Input](https://github.com/influxdata/telegraf/blob/release-1.18/plugins/inputs/vsphere/README.md) (`vsphere`): Add `MetricLookback` setting to handle reporting delays in vCenter 6.7 and later.
+- [OPC UA Client Input](https://github.com/influxdata/telegraf/blob/release-1.18/plugins/inputs/opcua/README.md) (`opcua`): Fix error handling.
+
+### Output plugin updates
+
+-  [Sumo Logic Output](https://github.com/influxdata/telegraf/blob/release-1.18/plugins/outputs/sumologic/README.md) (`sumologic`): Add support to [sanitize the metric name](https://github.com/influxdata/telegraf/tree/release-1.18/plugins/serializers/carbon2#metric-name-sanitization) in Carbon2 serializer.  
+
+### Processor plugin updates
+
+- [Converter Processor](https://github.com/influxdata/telegraf/blob/release-1.18/plugins/processors/converter/README.md) (`converter`):
+   Add support for `float64` to support converting longer hexadecimal string values to a numeric type without losing in precision. Note, if a string number exceeds the size limit for `float64`, precison may be lost.
+
+## v1.18.1 [2021-04-07]
+
+- Agent: Closes running outputs when agent reloads on SIGHUP.
+
+### Input plugin updates
+
+- [Docker Input](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/docker) (`docker`):
+  Fix panic when parsing container statistics.
+- [Exec Input](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/exec) (`exec`):
+  Fix truncated messages in debug mode; debug mode now shows full messages.
+- [IPMI Sensor Input](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/ipmi_sensor) (`ipmi_sensor`):
+  Fix panic by implementing a length check to plugin.
+- [MySQL Input](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/mysql) (`mysql`):
+  Fix the ability to handle ‘binary logs’ query for MySQL version 8.0+.
+- [NFS Client Input](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/nfsclient) (`nfsclient`):
+  Fix integer overflow in fields received by mountstat.
+- [Ping Input](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/ping) (`ping`):
+  Resolve error that prevented the agent from running when an unprivileged UDP ping was sent. Now, `SetPrivileged(true)` is always true in native mode to ensure a privileged ICMP ping is sent.
+- [SNMP Input](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/snmp) (`snmp`):
+  Fix `init()` when no MIBs are installed.
+- [SQL Server Input](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/sqlserver) (`sqlserver`):
+  Fix `sqlserver_process_cpu` calculation.
+- [Tail Input](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/tail) (`tail`):
+  Added configurable option to override `path` tag.
+
+### Output plugin updates
+
+- [Azure Monitor Output](https://github.com/influxdata/telegraf/tree/master/plugins/outputs/azure_monitor) (`azure_monitor`):
+  Fix an issue to handle error when initializing the authentication object.
+- [Yandex Cloud Monitoring Output](https://github.com/influxdata/telegraf/tree/master/plugins/outputs/yandex_cloud_monitoring) (`yandex_cloud_monitoring`):
+  Fix an issue to use correct computed metadata URL to get `folder-id`.
+
+### Processor plugin updates
+
+- [ifName](https://github.com/influxdata/telegraf/tree/master/plugins/processors/ifname) (`ifname`):
+  Retrieve interface name more efficiently.
+
+
+## v1.18 [2021-3-17]
+
+### Features
+- Update to Go 1.16.2.
+- Add code signing for Windows and macOS.
+- More SNMP v3 authentication protocols, including SHA-512.
+- Add support for [DataDog distributions](https://docs.datadoghq.com/metrics/distributions/#counting-distribution-metrics) metric type.
+
+### New plugins
+
+#### Inputs
+- [Beat](https://github.com/influxdata/telegraf/blob/master/plugins/inputs/beat)(`beat`) - Contributed by [@nferch](https://github.com/nferch)
+- [CS:GO](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/csgo)(`csgo`) - Contributed by [@oofdog](https://github.com/oofdog)
+- [Directory Monitoring](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/directory_monitor)(`directory_monitor`) - Contributed by [@influxdata](https://github.com/influxdata)
+- [NFS](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/nfsclient)(`nfsclient`) - Contributed by [@pmoranga](https://github.com/pmoranga)
+- [RavenDB](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/ravendb)(`ravendb`) - Contributed by [@ml054](https://github.com/ml054) and [@bartoncasey](https://github.com/bartoncasey)
+
+#### Outputs
+- [Grafana Loki](https://github.com/influxdata/telegraf/blob/master/plugins/outputs/loki)(`loki`) - Contributed by [@eraac](https://github.com/eraac)
+- [Sensu](https://github.com/influxdata/telegraf/tree/master/plugins/outputs/sensu)(`sensu`) - Contributed by [@calebhailey](https://github.com/calebhailey)
+- [SignalFX](https://github.com/influxdata/telegraf/tree/master/plugins/outputs/signalfx)(`signalfx`) - Contributed by [@keitwb](https://github.com/keitwb)
+
+#### External
+- [GeoIP](https://github.com/a-bali/telegraf-geoip)(`geoip`) - Contributed by [@a-bali](https://github.com/a-bali)
+- [Plex Webhook](https://github.com/russorat/telegraf-webhooks-plex)(`plex`) - Contributed by [@russorat](https://github.com/russorat)
+- [SMCIPMI](https://github.com/jhpope/smc_ipmi)(`smc_ipmi`) - Contributed by [@jhpope](https://github.com/jhpope)
+
+#### Aggregators
+- [Derivative](https://github.com/influxdata/telegraf/tree/master/plugins/aggregators/derivative)(`derivative`) - Contributed by [@KarstenSchnitter](https://github.com/karstenschnitter)
+- [Quantile](https://github.com/influxdata/telegraf/tree/master/plugins/aggregators/quantile)(`quantile`) - Contributed by [@srebhan](https://github.com/srebhan)
+
+#### Processors
+- [AWS EC2 Metadata](https://github.com/influxdata/telegraf/tree/master/plugins/processors/aws/ec2)(`aws_ec2`) - Contributed by [@pmalek-sumo](https://github.com/pmalek-sumo)
+
+#### Parsers
+- [XML](https://github.com/influxdata/telegraf/tree/master/plugins/parsers/xml)(`xml`) - Contributed by [@srebhan](https://github.com/srebhan)
+
+#### Serializers
+- [MessagePack](https://github.com/influxdata/telegraf/tree/master/plugins/serializers/msgpack)(`msgpack`) - Contributed by [@dialogbox](https://github.com/dialogbox)
+
+
+## v.1.17.3 [2021-2-17]
+
+- Update to Go 1.15.8.
+
+### Input plugin updates
+
+- Filestat (`filestat`): Skip missing files.
+- MQTT Consumer (`mqtt_consumer`): Fix reconnection issues.
+- Ping (`ping`):
+  - Fix a timeout for `deadline` configuration.
+  - Update README with correct cmd for native ping on Linux.
+  - Fix percentile calculations.
+- SNMP (`snmp`): Add support to expose IPv4/IPv6 as connection-schemes.
+- x509 Certificate (`x509_cert`): Fix a timeout issue.
+-
+### Output plugin updates
+
+- InfluxDB v1.x (`influxdb`): Validate InfluxDB response after creating a database to avoid JSON parsing errors.
+- Warp10 (`warp10`): Add support for commas in tags to be URL encoded.
+
+### Miscellaneous fixes and updates
+
+- Telegraf configuration file (`telegraf.conf`): Resolve issue reading `flush_jitter` output.
+- Library updates:
+   - Update `github.com/gopcua/opcua` to 0.1.13.
+   - Update `go-ping` to latest version.
+
+## v.1.17.2 [2021-1-28]
+
+### Input plugin updates
+- `ping`:
+  - Added support to the interface in native mode using either the name or IP address.
+  - Resolved regression from 1.17.1 by adding back missing function.
+
+## v.1.17.1 [2021-1-27]
+
+### Features
+- Add Event Log support for Windows platforms.
+- Allow specifying SNI hostnames in `common.tls`.
+
+### Input plugin updates
+- `csv`:
+  - Add  ability to define an array of string skip values.
+  - Address issue of ignoring missing values.
+- `gnmi`: Metric path no longer has leading character truncated.
+- `http_listener_v2`: Fixed an issue with `stop()` when plugin fails to start.
+- `ipmi_sensor`:
+  - Add setting to enable caching.
+  - Add `hex_key` parameter.
+- `jenkins`: Add support for inclusive job list.
+- `lustre2`: No longer crashes if the field name and value are not separated.
+- `ping`: Use go-ping library when `method = "native"` in the configuration
+- `prometheus`: Use mime-type to handle protocol-buffer responses.
+- `procstat`:
+  - Provide an option to include core count when reporting `cpu_usage`
+  - Use the same timestamp for all metrics in the same `Gather()` cycle.
+- `postgresql_extensible`: Add timestamp column option to postgres_extensible to handle log-like queries.
+- `snmp`: Extended the internal SNMP wrapper to support AES-192, AES-192C, AES-256, and AES-256C.
+- `webhooks`: Use the `measurement` json field from the Particle.io webhook as the measurement name.
+- `x509_cert`: Fixed a timeout issue
+- `zookeeper`: Improve `mntr` regex expression to match user-specific keys.
+
+### Output plugin updates
+
+- `http`: Add option to control idle connection timeout.
+- `influxdb_v2`:
+  - Log no longer flooded with errors when Elasticsearch receiver is in read-only state.
+  - Add exponential backoff and respecting client error responses.
+
+### Aggregator plugin updates
+- `merge`: Performance optimization improvements.
+
+## v1.17.0 [2020-12-17]
+
+### Features
+- Update Go to 1.15.5.
+- Added support for Linux/ppc64le.
+
+### New plugins
+
+#### Inputs
+
+- [Intel Powerstat](https://github.com/influxdata/telegraf/blob/master/plugins/inputs/intel_powerstat/README.md)(`intel_powerstat`)
+- [Riemann Listener](https://github.com/influxdata/telegraf/blob/master/plugins/inputs/riemann_listener/README.md)(`riemann`)
+
+#### Outputs
+
+- [Logz.io](https://github.com/influxdata/telegraf/blob/master/plugins/outputs/logzio/README.md)(`logzio`)
+- [Yandex Cloud Monitoring](https://github.com/influxdata/telegraf/blob/master/plugins/outputs/yandex_cloud_monitoring/README.md)(`yandex_cloud_monitoring`)
+
+#### Output data formats (serializers)
+
+- [Prometheus Remote Write](https://github.com/influxdata/telegraf/blob/master/plugins/serializers/prometheusremotewrite/README.md)(`prometheusremotewrite`)
+
+#### Parsers
+
+- [Prometheus](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/prometheus/README.md)(`prometheus`)
+
+### Input plugin updates
+
+- `aerospike`: Fix edge case where unexpected hex string was converted to integer if all digits.
+- `bcache`: Fix tests for Windows.
+- `bind`: Add configurable timeout.
+- `carbon2`: Fix tests.
+-  `ecs`: Remove duplicated field from `ecs_task`.
+- `execd`: Add support for new lines in line protocol fields.
+- `github`: Add query of pull request statistics.
+- `graphite`: Parse tags.
+- `http`: Add proxy support.
+- `http_response`: Fix network test.
+- `jenkins`: Add build number field to `jenkins_job` measurement.
+- `kafka_consumer`: Enable `ztsd` compression and idempotent writes.
+- `kube_inventory`:
+    - Fix issue with missing metrics when pod has only pending containers.
+    - Update string parsing of allocatable cpu cores.
+- `modbus`: Add FLOAT64-IEEE support.
+- `monit`: Add `response_time`.
+- `mysql`: Add per user metrics.
+- `mqtt_consumer`: Fix issue with concurrent map write.
+- `opcua`Add node groups.
+- `ping`:
+  - Add percentiles.
+  - Fix potential issue with race condition.
+- `snmp`:
+  - Add support for converting hex strings to integers.
+  - Translate field values.
+- `socket_listener`: Fix crash when receiving invalid data.
+- `sqlserver`:
+  - Add tags for monitoring readable secondaries for Azure SQL MI.
+  - Add SQL Server HA/DR Availability Group queries.
+  - Remove duplicate column (`session_db_name`).
+  - Add column `measurement_db_type` to output of all queries if not empty.
+- `statsd`: Add configurable Max TTL duration.
+- `vsphere`: Fix spelling of datacenter check.
+- `win_services`: Add Glob pattern matching.
+- `zfs`: Add dataset metrics.
+
+### Output plugin updates
+
+- `kafka`: Enable `ztsd` compression and idempotent writes.
+-  `nats`: Add `name` parameter.
+
+### Processor plugin updates
+
+- `starlark`: Can now store state between runs using a global state variable.
+
+## v1.16.3 [2020-12-01]
+
+### Features
+- Update `godirwalk` to 1.16.1 for Dragonfly BSD support.
+
+### Input plugin updates
+- APCUPSD (`apcupsd`): Add driver and CUDA version.
+- CSV Parser (`csv`): Fix issue where CSV timestamp was being read as Unix instead of Go reference time.
+- gNMI (`gnmi`): Add logging of `SubscribeResponse_Error` response types.
+
+- NVIDIA SMI (`nvidia_smi`): Add driver and CUDA version.
+- PHP-FPM (`phpfpm`): Fix issue with "index out of range" error.
+- SQL Server (`sqlserver`): Fix typo in `database_name` column.
+
+### Output plugin updates
+- Wavefront (`wavefront`):
+  - Distinguish between retryable and non-retryable errors .
+  - Add debug-level logging for metric data that is not retryable.
+
+### Parser plugin updates
+- Starlark (`starlark`):
+  - Allow the processor to manage errors that occur in the `apply` function.
+  - Add support for logging.
+  - Add capability to return multiple metrics.
+
+## v1.16.2 [2020-11-13]
+
+### Input plugin updates
+
+- CSV Parser (`csv`): Fix parsing multiple CSV files with different headers.
+- DC/OS (`dcos`): Fix high-severity vulnerability in previous version of the `jwt-go` library.
+- gNMI (`gnmi`): Add support for bytes encoding for gNMI messages.
+- Proxmox ( `proxmox`):
+  - Fix a few issues with error reporting.
+  - Now ignores QEMU templates.
+- RAS (`ras`): Fix tests failing on some systems.
+- Redfish (`redfish`): Fix a parsing issue.
+- SMART (`smart`): Fix an issue to recognize all devices from the configuration.
+- SQL Server (`sqlserver`): Fix an issue with errors in on-premise instance queries.
+- Systemd Units (`systemd_units`): Add `--plain` to the command invocation to fix an issue for reporting errors for units not found.
+- vSphere (`vsphere`)
+  - Fix to how metrics were counted.
+  - Fix to metrics being skipped under in certain specific circumstances.
+
+### Output plugin updates
+
+- Dynatrace (`dynatrace`): Fix pushing metrics to separate Dynatrace environments.
+- Wavefront (`wavefront`): Add `immediate_flush` tag.
+
+## v1.16.1 [2020-10-28]
+
+### Input plugin updates
+
+- Apache Kafka Consumer (`kafka_consumer`): Add Kafka SASL-mechanism authentication support for SCRAM-SHA-256, SCRAM-SHA-512, and GSSAPI.
+- Microsoft SQL Server (`sqlserver`):
+  - Fix a syntax error in Azure queries.
+  - Remove synthetic performance counters that no longer exist from the `sqlserver_performance_counters` measurement.
+  - Add a new tag (`sql_version_desc`) to identify the readable SQL Server version.  
+- RAS (`ras`):
+  - Disable on specific Linux architectures (MIPS64, mips64le, ppc64le, riscv64).
+  - Fix an issue to properly close file handlers.
+- Processes (`processes`): Fix an issue with receiving `no such file or directory` stat error.
+- Windows Performance Counters (`win_perf_counters`): Fix an issue with the counter where a negative denominator error would cause gathering operations to fail.
+
+### Output plugin updates
+
+- Apache Kafka (`kafka`): Add Kafka SASL-mechanism authentication support for SCRAM-SHA-256, SCRAM-SHA-512, GSSAPI.
+
+## v1.16.0 [2020-10-21]
+
+### New plugins
+
+#### Inputs
+
+- [InfluxDB v2 Listener Input Plugin](https://github.com/influxdata/telegraf/blob/master/plugins/inputs/influxdb_v2_listener/README.md)(`influxdb_v2_listener`) - Contributed by [@magichair](https://github.com/magichair)
+- [Intel RDT Input Plugin](https://github.com/influxdata/telegraf/blob/master/plugins/inputs/intel_rdt/README.md)(`intel_rdt`) - Contributed by [@p-zak](https://github.com/p-zak)
+- [NSD Input Plugin](https://github.com/influxdata/telegraf/blob/master/plugins/inputs/nsd/README.md)(`nsd`) - Contributed by [@gearnode](https://github.com/gearnode)
+- [OPC UA Input Plugin](https://github.com/influxdata/telegraf/blob/master/plugins/inputs/opcua/README.md)(`opcua`) - Contributed by [@influxdata](https://github.com/influxdata)
+- [Proxmox Input Plugin](https://github.com/influxdata/telegraf/blob/master/plugins/inputs/proxmox/README.md)(`proxmox`) - Contributed by [@effitient](https://github.com/effitient)
+- [RAS Input Plugin](https://github.com/influxdata/telegraf/blob/master/plugins/inputs/ras/README.md)(`ras`)- Contributed by [@p-zak](https://github.com/p-zak)
+- [Windows Eventlog Input Plugin](https://github.com/influxdata/telegraf/blob/master/plugins/inputs/win_eventlog/README.md)(`win_eventlog`) - Contributed by [@simnv](https://github.com/simnv)
+
+#### Outputs
+
+- [Dynatrace Output Plugin](https://github.com/influxdata/telegraf/blob/master/plugins/outputs/dynatrace/README.md)(`dynatrace`) - Contributed by [@thschue](https://github.com/theschue)
+- [Sumo Logic Output Plugin](https://github.com/influxdata/telegraf/blob/master/plugins/outputs/sumologic/README.md) (`sumologic`) - Contributed by [@pmalek-sumo](https://github.com/pmalek-sumo)
+- [Timestream Output Plugin](https://github.com/influxdata/telegraf/blob/master/plugins/outputs/timestream) (`timestream`) - Contributed by [@piotrwest](https://github.com/piotrwest)
+
+
+#### External
+
+- [Amazon Cloudwatch Alarms Input Plugin](https://github.com/vipinvkmenon/awsalarms)(`awsalarms`) - Contributed by [@vipinvkmenon](https://github.com/vipinvkmenon)
+- [YouTube Input Plugin](https://github.com/inabagumi/youtube-telegraf-plugin)(`youtube`) - Contrbuted by [@inabagumi](https://github.com/inabagumi)
+- [Octoprint Input Plugin](https://github.com/sspaink/octoprint-telegraf-plugin)[`octoprint`] - Contributed by [@sspaink](https://github.com/sspaink/)
+- [Systemd Timings Input Plugin](https://github.com/pdmorrow/telegraf-execd-systemd-timings)(`systemd-timings`) - Contributed by [@pdmorrow](https://github.com/pdmorrow)
+
+
+### Input plugin updates
+
+- `aerospike`: Add set and histogram reporting.
+- `agent`:
+  - Send metrics in FIFO order.
+  - Fix issue with `execd restart_delay` being ignored.
+  - Sort plugin name lists for output.
+- `clickhouse`: Add additional metrics.
+- `cloudwatch`: Implement AWS CloudWatch Input Plugin ListMetrics API calls to use Active Metric Filter.
+- `consul`: Add `metric_version` flag.
+- `docker`: Fix vulnerabilities found in BDBA scan.
+- `execd`: Fix issue with `restart_delay` being ignored.
+- `gnmi`: Next message after send returns EOF.
+- `http_listener_v2`: Make header tags case-insensitive.
+- `http_response`: Match on status code.
+- `jenkins`: Multiple escaping occurs on at certain folder depth.
+- `kubernetes`: Add missing error check for HTTP requirement failure.
+- `modbus`: Extend support of fixed point values on input.
+- `mongodb`: Add pages written from cache metric.
+- `net`: Fix broken link to `proc.c`.
+- `snmp` Add agent host tag configuration option.
+- `smart`: Add missing NVMe attributes.
+- `sqlserver`:
+  - Database_type config to Split up sql queries by engine type
+  - Fixed query mapping
+  - New refactoring and formatting queries.
+  - Add more performance counters.
+- `tail`:
+  - Close file to ensure it has been flushed.
+  - Fix following on EOF.
+
+### Output plugin updates
+
+-  `elasticsearch`: Added `force_document_id` option to ES output enable resend data and avoid duplicated ES documents.
+- `opentsdb`: Skips NaN and Inf JSON values.
+
+### Processor plugin updates
+
+- `execd`: Increased the maximum serialized metric size in line protocol
+- `ifname`: Add `addTag` debugging.
+- `starlark`: Add JSON parsing support.
+
+### Bug fixes
+
+- Fix `darwin` package build flags.
+- `shim`:
+  - Fix bug with loading plugins with no config.
+  - Logger improvements.
+  - Fix issue with loading processor config from `execd`.
+- Initialize aggregation processors.
+- Fix arch name in `deb/rpm` builds.
+- Fix issue with `rpm /var/log/telegraf` permissions
+- Fix `docker-image make` target.
+- Remove Event field from `serializers.splunkmetric`.
+- Fix panic on streaming processors using logging
+- `ParseError.Error` panic in `parsers.influx`
+- Fix `procstat` performance regression
+- Fix serialization when using `carbon2`.
+- Fix bugs found by LGTM analysis platform.
+- Update to Go 1.15.2
+
+## v.1.15.3 [2020-09-11]
+
+### Features
+- `processors.starlark`:
+  - Improve the quality of docs by executing them as tests.
+  - Add pivot example.
+- `outputs.application_insights`: Added ability to set endpoint url.
+- `inputs.sqlserver`: Added new counter - Lock Timeouts (timeout > 0)/sec.
+
+### Bug fixes
+
+- `agent`: Fix minor error message race condition.
+- `build`: Update dockerfiles to Go 1.14.
+- `shim`:
+  - Fix bug in logger affecting `AddError`.
+  - Fix issue with `config.Duration`.
+- `inputs.eventhub_consumer`: Fix string to int conversion.
+- `inputs.http_listener_v2`: Make http header tags case-insensitive.
+- `inputs.modbus`: Extend support of fixed point values.
+- `inputs.ping`: Fix issue for FreeBSD's ping6.
+- `inputs.vsphere`: Fixed missing cluster name.
+- `outputs.opentsdb` Fix JSON handling of values `NaN` and `Inf`.
+
+## v1.15.2 [2020-07-31]
+
+### Bug Fixes
+- Fix RPM `/var/log/telegraf` permissions.
+- Fix tail following on EOF.
+
+## v1.15.1 [2020-07-22]
+
+### Bug fixes
+
+- Fix architecture in non-amd64 deb and rpm packages.
+
+## v1.15.0 [2020-07-22]
+
+{{% warn %}}
+Critical bug that impacted non-amd64 packages was introduced in 1.15.0. **Do not install this release.** Instead, install 1.15.1, which includes the features, new plugins, and bug fixes below.
+{{% /warn %}}
+
+### Breaking changes
+
+Breaking changes are updates that may cause Telegraf plugins to fail or function incorrectly. If you have one of the following plugins installed, make sure to update your plugin as needed:
+
+- **Logparser** (`logparser`) input plugin: Deprecated. Use the `tail` input with `data_format = "grok"` as a replacement.
+- **Cisco GNMI Telemetry** (`cisco_telemetry_gnmi`) input plugin: Renamed to `gnmi` to better reflect its general support for gNMI devices.
+- **Splunkmetric** (`splunkmetric`) serializer: Several fields used primarily for debugging have been removed. If you are making use of these fields, they can be added back with the `tag` option.
+
+### New plugins
+
+#### Inputs
+
+- [NGINX Stream STS Input Plugin](https://github.com/influxdata/telegraf/blob/master/plugins/inputs/nginx_sts/README.md)(`nginx_sts`) - Contributed by [@zdmytriv](https://github.com/zdmytriv)
+- [Redfish Input Plugin](https://github.com/influxdata/telegraf/blob/master/plugins/inputs/redfish/README.md)(`redfish`) - Contributed by [@sarvanikonda](https://github.com/sarvanikonda)
+
+#### Outputs
+
+- [Execd Output Plugin](https://github.com/influxdata/telegraf/blob/master/plugins/outputs/execd/README.md)(`execd`) - Contributed by [@influxdata](https://github.com/influxdata)
+- [New Relic Output Plugin](https://github.com/influxdata/telegraf/blob/master/plugins/outputs/newrelic/README.md)(`newrelic`) - Contributed by @hsingkalsi
+#### Processors
+
+- [Defaults Processor Plugin](https://github.com/influxdata/telegraf/blob/master/plugins/processors/defaults/README.md)(`defaults`) - Contributed by [@jregistr](https://github.com/jregistr)
+- [Execd Processor Plugin](https://github.com/influxdata/telegraf/blob/master/plugins/processors/execd/README.md)(`execd`) - Contributed by [@influxdata](https://github.com/influxdata)
+- [Filepath Processor Plugin](https://github.com/influxdata/telegraf/blob/master/plugins/processors/filepath/README.md)(`filepath`) - Contributed by [@kir4h](https://github.com/kir4h)
+- [Network Interface Name Processor Plugin](https://github.com/influxdata/telegraf/blob/master/plugins/processors/ifname/README.md)(`ifname`) - Contributed by [@influxdata](https://github.com/influxdata)
+- [Port Name Processor Plugin](https://github.com/influxdata/telegraf/blob/master/plugins/processors/port_name/README.md)(`port_name`) - Contributed by [@influxdata](https://github.com/influxdata)
+- [Reverse DNS Processor Plugin](https://github.com/influxdata/telegraf/blob/master/plugins/processors/reverse_dns/README.md)(`reverse_dns`) - Contributed by [@influxdata](https://github.com/influxdata)
+- [Starlark Processor Plugin](https://github.com/influxdata/telegraf/blob/master/plugins/processors/starlark/README.md)(`starlark`) - Contributed by [@influxdata](https://github.com/influxdata)
+
+### Features
+
+- Telegraf's `--test` mode runs processors and aggregators before printing metrics.
+- Official packages built with Go 1.14.5.
+- When updating the Debian package, you will no longer be prompted to merge the `telegraf.conf` file. Instead, the new version will be installed to `/etc/telegraf/telegraf.conf.sample`. The `tar` and `zip` packages now include the version in the top-level directory.
+- Allow per input overriding of `collection_jitter` and `precision`.
+- Deploy Telegraf configuration as `telegraf.conf.sample`.
+- Use Docker log timestamp as metric time.
+- Apply ping deadline to DNS lookup.
+- Support multiple templates for graphite serializers.
+- Add configurable separator graphite serializer and output.
+- Add support for SIGUSR1 to trigger flush.
+- Add support for once mode that writes to outputs and exits.
+- Run processors and aggregators during test mode.
+- Add timezone configuration to CSV parser.
+
+
+#### Input plugin updates
+
+- **Ceph Storage** (`ceph`): Add support for MDS and RGW sockets.
+- **ECS** (`ecs`): Add v3 metadata support.
+- **Fibaro** (`fibaro`): Add support for battery-level monitoring.
+- **File** (`file`):
+  - Support UTF-16.
+  - Exclude `csv_timestamp_column` and `csv_measurement_column` from fields.
+- **HTTP** (`http`): Add reading bearer token.
+- **HTTP Listener v2** (`http_listener_v2`): Add ability to specify HTTP headers as tags.
+- **HTTP Response** (`http_response`):
+  - Add authentication support.
+  - Allow collection of HTTP headers.
+  - Add ability to collect response body as field.
+- **Icinga 2** (`icinga2`):
+  - Fix source field.
+  - Add tag for server hostname.
+- **InfluxDB Listener** (`influxdb_listener`): Add option to save retention policy as tag.
+- **IPtables** (`iptables`): Extract target as a tag for each rule.
+- **Kibana** (`kibana`): Fix `json unmarshal` error.
+- **Kubernetes Inventory** (`kube_inventory`): Add ability to add selectors as tags.
+- **Mem** (`mem`): Add laundry on FreeBSD.
+- **Microsoft SQL Server** (`sqlserver`):
+  - Add `VolumeSpace` query.
+  - Add `cpu` query.
+  - Add counter type to `perfmon` collector.
+  - Improve compatibility with older server versions.
+  - Fix typo in `total_elapsed_time_ms` field.
+- **Modbus** (`modbus`):
+  - Add support for 64-bit integer types.
+  - Add retry when replica is busy.
+  - Add ability to specify measurement per register.
+- **MongoDB** (`monogdb`):
+  - Add commands stats.
+  - Add additional fields.
+  - Add cluster state integer.
+  - Add option to disable cluster status.
+  - Add additional conccurrent transaction information.
+- **NVIDIA SMI** (`nvidia_smi`): Add video codec stats.
+- **Procstat** (`procstat`):
+  - Improve performance.
+  - Fix memory leak.
+- **S.M.A.R.T.** (`smart`): Add missing `nvme` attributes.
+- **SNMP Trap** (`snmp_trap`): Add SNMPv3 trap support.
+- **System** (`system`): Fix incorrect uptime when clock is adjusted.
+- **Tail** (`tail`): Support UTF-16.
+
+#### Output plugin updates
+
+- **Enum** (`enum`): Add integer mapping support.
+
+#### Processor plugin updates
+
+- **Date** (`date`):
+  - Add field creation.
+  - Add integer unix time support.
+- **Wavefront** (`wavefront`): Add `truncate_tags` setting.
+
+
+### Bug fixes
+- Fix ability to write metrics to CloudWatch with IMDSv1 disabled.
+- Fix vSphere 6.7 missing data issue.
+- Fix gzip support in `socket_listener` with tcp sockets.
+- Fix interval drift when `round_interval` is set in agent.
+- Fix incorrect uptime when clock is adjusted.
+- Remove trailing backslash from tag keys/values in `influx` serializer.
+- Fix incorrect Azure SQL DB server properties.
+- Send metrics in FIFO order.
+
+## v1.14.5 [2020-06-30]
+
+### Bug fixes
+
+- Improve the performance of the `procstat` input.
+- Fix ping exit code handling on non-Linux operating systems.
+- Fix errors in output of the `sensors` command.
+- Prevent startup when tags have incorrect type in configuration file.
+- Fix panic with GJSON multiselect query in JSON parser.
+- Allow any key usage type on x509 certificate.
+- Allow histograms and summary types without buckets or quantiles in `prometheus_client` output.
+
+## v1.14.4 [2020-06-09]
+
+### Bug fixes
+
+- Fix the `cannot insert the value NULL` error with the `PerformanceCounters` query in the `sqlServer` input plugin.
+- Fix a typo in the naming of `the gc_cpu_fraction` field in the `influxdb` input plugin.
+- Fix a numeric to bool conversion in the `converter` processor.
+- Fix an issue with the `influx` stream parser blocking when the data is in buffer.
+
+## v1.14.3 [2020-05-19]
+
+### Bug fixes
+
+- Use same timestamp for all objects in arrays in the `json` parser.
+- Handle multiple metrics with the same timestamp in `dedup` processor.
+- Fix reconnection of timed out HTTP2 connections `influxdb` outputs.
+- Fix negative value parsing in `impi_sensor` input.
+
+## v1.14.2 [2020-04-28]
+
+### Bug fixes
+
+- Trim white space from instance tag in `sqlserver` input .
+- Use increased AWS Cloudwatch GetMetricData limit of 500 metrics per call.
+- Fix limit on dimensions in `azure_monitor` output.
+- Fix 64-bit integer to string conversion in `snmp` input.
+- Fix shard indices reporting in `elasticsearch` input plugin.
+- Ignore fields with Not a Number or Infinity floats in the JSON serializer.
+- Fix typo in name of `gc_cpu_fraction` field of the `kapacitor` input.
+- Don't retry create database when using database_tag if forbidden by the server in `influxdb` output.
+- Allow CR and FF inside of string fields in InfluxDB line protocol parser.
+
+## v1.14.1 [2020-04-14]
+
+### Bug fixes
+
+- Fix `PerformanceCounter` query performance degradation in `sqlserver` input.
+- Fix error when using the `Name` field in template processor.
+- Fix export timestamp not working for Prometheus on v2.
+- Fix exclude database and retention policy tags.
+- Fix status path when using globs in `phpfpm`.
+
+## v1.14 [2020-03-26]
+
+### Breaking changes
+
+Breaking changes are updates that may cause Telegraf plugins to fail or function incorrectly. If you have one of the following plugins installed, make sure to update your plugin as needed:
+
+- **Microsoft SQL Server** (`sqlserver`) input plugin: Renamed the `sqlserver_azurestats` measurement to `sqlserver_azure_db_resource_stats` to resolve an issue where numeric metrics were previously being reported incorrectly as strings.
+- **Date** (`date`) processor plugin: Now uses the UTC timezone when creating its tag. Previously, the local time was used.
+
+{{% note %}}
+Support for SSL v3.0 is deprecated in this release.
+Telegraf now uses the [Go TLS library](https://golang.org/pkg/crypto/tls/).
+{{% /note %}}
+
+### New plugins
+
+#### Inputs
+
+- [Arista LANZ Consumer](https://github.com/influxdata/telegraf/blob/release-1.14/plugins/inputs/lanz/README.md) - Contributed by [@timhughes](https://github.com/timhughes)
+- [ClickHouse](https://github.com/influxdata/telegraf/blob/release-1.14/plugins/inputs/clickhouse/README.md)(`clickhouse`) - Contributed by [@kshvakov](https://github.com/kshvakov)
+- [Execd](https://github.com/influxdata/telegraf/blob/release-1.14/plugins/inputs/execd/README.md)(`execd`) - Contributed by [@jgraichen](https://github.com/jgraichen)
+- [Event Hub Consumer](https://github.com/influxdata/telegraf/blob/master/plugins/inputs/eventhub_consumer/README.md)(`eventhub_consumer`) - Contributed by [@R290](https://github.com/R290)
+- [InfiniBand](https://github.com/influxdata/telegraf/blob/master/plugins/inputs/infiniband/README.md)(`infiniband`) - Contributed by [@willfurnell](https://github.com/willfurnell)
+- [Modbus](https://github.com/influxdata/telegraf/blob/master/plugins/inputs/modbus/README.md)(`modbus`) - Contributed by [@garciaolais](https://github.com/garciaolais)
+- [Monit](https://github.com/influxdata/telegraf/blob/master/plugins/inputs/monit/README.md)(`monit`) - Contributed by [@SirishaGopigiri](https://github.com/SirishaGopigiri)
+- [SFlow](https://github.com/influxdata/telegraf/blob/master/plugins/inputs/sflow/README.md)(`sflow`) - Contributed by [@influxdata](https://github.com/influxdata)
+- [Wireguard](https://github.com/influxdata/telegraf/blob/master/plugins/inputs/wireguard/README.md)(`wireguard`) - Contributed by [@LINKIWI](https://github.com/LINKIWI)
+
+#### Processors
+
+- [Dedup](https://github.com/influxdata/telegraf/blob/master/plugins/processors/dedup/README.md)(`dedup`) - Contributed by [@igomura](https://github.com/igomura)
+- [S2 Geo](https://github.com/influxdata/telegraf/blob/master/plugins/processors/s2geo/README.md)(`s2geo`) - Contributed by [@alespour](https://github.com/alespour)
+- [Template](https://github.com/influxdata/telegraf/blob/master/plugins/processors/template/README.md) (`template`) - Contributed by [@RobMalvern](https://github.com/RobMalvern)
+
+#### Outputs
+
+- [Warp10](https://github.com/influxdata/telegraf/blob/master/plugins/outputs/warp10/README.md)(`warp10`) - Contributed by [@aurrelhebert](https://github.com/aurrelhebert)
+
+### Features
+
+#### Input plugin updates
+
+- **Apache Kafka Consumer** (`kafka_consumer`): Add SASL version control to support Microsoft Azure Event Hub.
+- **Apcupsd** (`apcupsd`): Add new tag `model` and new metrics: `battery_date`, `nominal_input_voltage`, `nominal_battery_voltage`, `nominal_power`, `firmware`.
+- **Cisco Model-driven Telemetry (MDT)** (`cisco_telemetry_gnmi`) input plugin:
+  - Add support for GNMI DecimalVal type.
+  - Replace dash (`-`) with underscore (`_`) when handling embedded tags.
+- **DiskIO** (`diskio`): Add counters for merged reads and writes.
+- **IPMI Sensor** (`ipmi_sensor`): Add `use_sudo` option.
+- **Jenkins** (`jenkins`):
+  - Add `source` and `port` tags to `jenkins_job` metrics.
+  - Add new fields `total_executors` and `busy_executors`.
+- **Kubernetes** (`kubernetes`): Add ability to collect pod labels.
+- **Microsoft SQL Server** (`sqlserver`):
+  - Add RBPEX IO statistics to DatabaseIO query.
+  - Add space on disk for each file to DatabaseIO query.
+  - Calculate DB Name instead of GUID in `physical_db_name`.
+  - Add `DatabaseIO` TempDB per Azure DB.
+  - Add `query_include` option for explicitly including queries.
+  - Add `volume_mount_point` to DatabaseIO query.
+- **MongoDB** (`mongodb`):
+  - Add `page_faults` for WiredTiger storage engine.
+  - Add latency statistics.
+  - Add replica set tag (`rs_name`).
+- **NATS Consumer** (`nats_consumer`): Add support for credentials file.
+- **NGINX Plus API** (`nginx_plus_api`): Add support for new endpoints.
+- **OpenLDAP** (`openldap`): Add support for MDB database information.
+- **PHP-FPM** (`phpfpm`): Allow globs in FPM unix socket paths (`unixsocket`).
+- **Procstat** (`procstat`): Add process `created_at` time.
+- **Prometheus** (`prometheus`) input plugin: Add `label` and `field` selectors for Kubernetes service discovery.
+- **RabbitMQ** (`rabbitmq`): Add `slave_nodes` and `synchronized_slave_nodes` metrics.
+- **StatsD** (`statsd`): Add UDP internal metrics.
+- **Unbound** (`unbound`): Expose [`-c cfgfile` option of `unbound-control`](https://linux.die.net/man/8/unbound-control) and set the default unbound configuration (`config_file= "/etc/unbound/unbound.conf`) in the Telegraf configuration file.
+- **VMware vSphere** (`vsphere`): Add option to exclude resources by inventory path, including `vm_exclude`, `host_exclude`, `cluster_exclude` (for both clusters and datastores), and `datacenter_exclude`.
+- **X.509 Certificate** (`x509_cert`): Add `server_name` override.
+
+#### Output plugin updates
+
+- **Apache Kafka** (`kafka`): Add `topic_tag` and `exclude_topic_tag` options.
+- **Graylog** (`graylog`): Allow a user defined field (`short_message_field`) to be used as the `GELF short_message`.
+- **InfluxDB v1.x** (`influxdb`): Add support for setting the retention policy using a tag (`retention_policy_tag`).
+- **NATS Output** (`nats`): Add support for credentials file.
+
+#### Aggregator plugin updates
+
+- **Histogram** (`histogram`): Add non-cumulative histogram.
+
+#### Processor plugin updates
+
+- **Converter** (`converter`): Add support for converting `tag` or `field` to `measurement`.
+- **Date** (`date`): Add date offset and timezone options.
+- **Strings** (`strings`): Add support for titlecase transformation.
+
+### Bug fixes
+
+- Fix Telegraf log rotation to use actual file size instead of bytes written.
+- Fix internal Telegraf metrics to prevent output split into multiple lines.
+- **Chrony** (`chrony`) input plugin: When plugin is enabled, search for `chronyc` only.
+- **Microsoft SQL Server** (`sqlserver`) input plugin:
+  - Fix conversion to floats in AzureDBResourceStats query.
+  - Fix case sensitive collation.
+  - Fix several issues with DatabaseIO query.
+  - Fix schedulers query compatibility with pre SQL-2016.
+- **InfluxDB Listener** (`influxdb_listener`):
+  - Fix request failing with EOF.
+  - Continue parsing after error.
+  - Set headers on ping URL.
+
+## v1.13.4 [2020-02-25]
+
+### Release Notes
+Official packages now built with Go 1.13.8.
+
+### Bug fixes
+- Parse NaN values from summary types in Prometheus (`prometheus`) input plugin.
+- Fix PgBouncer (`pgbouncer`) input plugin when used with newer PgBouncer versions.
+- Support up to 8192 stats in the Ethtool (`ethtool`) input plugin.
+- Fix performance counters collection on named instances in Microsoft SQL Server (`sqlserver`) input plugin.
+- Use add time for Prometheus expiration calculation.
+- Fix inconsistency with input error counting in Telegraf v1.x (`internal`) input plugin.
+- Use the same timestamp per call if no time is provided in Prometheus (`prometheus`) input plugin.
+
+## v1.13.3 [2020-02-04]
+
+### Bug fixes
+
+- Update Kibana (`kibana`) input plugin to support Kibana 6.4 and later.
+- Prevent duplicate `TrackingIDs` from being returned in the following queue consumer input plugins:
+    - Amazon Kineses Consumer (`kinesis_consumer`)
+    - AMQP Consumer (`amqp_consumer`)
+    - Apache Consumer (`apache_consumer`)
+    - MQTT Consumer (`mqtt_consumer`)
+    - NATS Consumer (`nats_consumer`)
+    - NSQ Consumer (`nsq_consumer`)
+- Increase support for up to 4096 statistics in the Ethtool (`ethtool`) input plugin.
+- Remove expired metrics from the Prometheus Client (`prometheus_client`) output plugin. Previously, expired metrics were only removed when new metrics were added.
+
+## v1.13.2 [2020-01-21]
+
+### Bug fixes
+
+- Warn without error when Processes (`processes`) input is started on Windows.
+- Only parse certificate blocks in X.509 Certificate (`x509_cert`) input plugin.
+- Add custom attributes for all resource types in VMware vSphere (`vsphere`) input plugin.
+- Support URL agent address form with UDP in SNMP (`snmp`) input plugin.
+- Record device fields in the SMART (`smart`) input plugin when attributes is `false`.
+- Remove invalid timestamps from Kafka messages.
+- Update `json` parser to fix `json_strict` option and set `default` to `true`.
+
+## v1.13.1 [2020-01-08]
+
+### Bug fixes
+- Fix ServerProperty query stops working on Azure after failover.
+- Add leading period to OID in SNMP v1 generic traps.
+- Fix missing config fields in prometheus serializer.
+- Fix panic on connection loss with undelivered messages in MQTT Consumer
+  (`mqtt_consumer`) input plugin.
+- Encode query hash fields as hex strings in SQL Server (`sqlserver`) input plugin.
+- Invalidate diskio cache if the metadata mtime has changed.
+- Show platform not supported warning only on plugin creation.
+- Fix rabbitmq cannot complete gather after request error.
+- Fix `/sbin/init --version` executed on Telegraf startup.
+- Use last path element as field key if path fully specified in Cisco GNMI Telemetry
+  (`cisco_telemetry_gnmi`) input plugin.
+
+## v1.13 [2019-12-12]
+
+### Release Notes
+Official packages built with Go 1.13.5.
+The Prometheus Format (`prometheus`) input plugin and Prometheus Client (`prometheus_client`)
+output have a new mapping to and from Telegraf metrics, which can be enabled by setting `metric_version = 2`.
+The original mapping is deprecated. When both plugins have the same setting,
+passthrough metrics are unchanged.
+Refer to the [Prometheus input plugin](https://github.com/influxdata/telegraf/blob/release-1.13/plugins/inputs/prometheus/README.md)
+for details about the mapping.
+
+### New Inputs
+- [Azure Storage Queue](https://github.com/influxdata/telegraf/blob/release-1.13/plugins/inputs/azure_storage_queue/README.md)
+  (`azure_storage_queue`) - Contributed by [@mjiderhamn](https://github.com/mjiderhamn)
+- [Ethtool](https://github.com/influxdata/telegraf/blob/release-1.13/plugins/inputs/ethtool/README.md)
+  (`ethtool`) - Contributed by [@philippreston](https://github.com/philippreston)
+- [SNMP Trap](https://github.com/influxdata/telegraf/blob/release-1.13/plugins/inputs/snmp_trap/README.md)
+  (`snmp_trap`) - Contributed by [@influxdata](https://github.com/influxdata)
+- [Suricata](https://github.com/influxdata/telegraf/blob/release-1.13/plugins/inputs/suricata/README.md)
+  (`suricata`) - Contributed by [@satta](https://github.com/satta)
+- [Synproxy](https://github.com/influxdata/telegraf/blob/release-1.13/plugins/inputs/synproxy/README.md)
+  (`synproxy`) - Contributed by [@rfrenayworldstream](https://github.com/rfrenayworldstream)
+- [Systemd Units](https://github.com/influxdata/telegraf/blob/release-1.13/plugins/inputs/systemd_units/README.md)
+  (`systemd_units`) - Contributed by [@benschweizer](https://github.com/benschweizer)
+
+### New Processors
+- [Clone](https://github.com/influxdata/telegraf/blob/release-1.13/plugins/processors/clone/README.md)
+  (`clone`) - Contributed by [@adrianlzt](https://github.com/adrianlzt)
+
+### New Aggregators
+- [Merge](https://github.com/influxdata/telegraf/blob/release-1.13/plugins/aggregators/merge/README.md)
+  (`merge`) - Contributed by [@influxdata](https://github.com/influxdata)
+
+### Features
+- Add per node memory stats to RabbitMQ (`rabbitmq`) input plugin.
+- Add ability to read query from file to PostgreSQL (`postgresql_extensible`) input plugin.
+- Add replication metrics to the Redis (`redis`) input plugin.
+- Support NX-OS telemetry extensions in Cisco Model-driven Telemetry (`cisco_telemetry_mdt`)
+  input plugin.
+- Allow `graphite` parser to create `Inf` and `NaN` values.
+- Use prefix base detection for ints in `grok` parser.
+- Add more performance counter metrics to Microsoft SQL Server (`sqlserver`) input plugin.
+- Add millisecond unix time support to `grok` parser.
+- Add container ID as optional source tag to Docker (`docker`) and Docker Log
+  (`docker_log`) input plugins.
+- Add `lang` parameter to OpenWeatherMap (`openweathermap`) input plugin.
+- Log file open errors at debug level in Tail (`tail`) input plugin.
+- Add timeout option to Amazon CloudWatch (`cloudwatch`) input plugin.
+- Support custom success codes in HTTP (`http`) input plugin.
+- Improve IPVS (`ipvs`) input plugin error strings and logging.
+- Add strict mode to JSON parser that can be disabled to ignore invalid items.
+- Add support for Kubernetes 1.16 and remove deprecated API usage.
+- Add gathering of RabbitMQ federation link metrics.
+- Add bearer token defaults for Kubernetes plugins.
+- Add support for SNMP over TCP.
+- Add support for per output flush jitter.
+- Add a nameable file tag to File (`file`) input plugin.
+- Add Splunk MultiMetric support.
+- Add support for sending HTTP Basic Auth in InfluxDB (`influxdb`) input plugin.
+- Add ability to configure the url tag in the Prometheus Format (`prometheus`) input plugin.
+- Add Prometheus `metric_version=2` mapping to internal metrics/line protocol.
+- Add Prometheus `metric_version=2` support to Prometheus Client (`prometheus_client`) output plugin.
+- Add content_encoding compression support to Socket Listener (`socket_listener`) input plugin.
+- Add high resolution metrics support to Amazon CloudWatch (`cloudwatch`) output plugin.
+- Add `SReclaimable` and `SUnreclaim ` to Memory (`mem`) input plugin.
+- Allow multiple certificates per file in X.509 Certificate (`x509_cert`) input plugin.
+- Add additional tags to the X.509 Certificate (`x509_cert`) input plugin.
+- Add batch data format support to File (`file`) output plugin.
+- Support partition assignment strategy configuration in Apache Kafka Consumer
+  (`kafka_consumer`) input plugin.
+- Add node type tag to MongoDB (`mongodb`) input plugin.
+- Add `uptime_ns` field to MongoDB (`mongodb`) input plugin.
+- Support resolution of symlinks in Filecount (`filecount`) input plugin.
+- Set message timestamp to the metric time in Apache Kafka (`kafka`) output plugin.
+- Add base64decode operation to String (`string`) processor.
+- Add option to control collecting global variables to MySQL (`mysql`) input plugin.
+
+### Bug fixes
+- Show correct default settings in MySQL (`mysql`) sample configuration.
+- Use `1h` or `3h` rain values as appropriate in OpenWeatherMap (`openweathermap`) input plugin.
+- Fix `not a valid field` error in Windows with Nvidia SMI (`nvidia_smi`) input plugin.
+- Fix InfluxDB (`influxdb`) output serialization on connection closed.
+- Fix ping skips remaining hosts after DNS lookup error.
+- Log MongoDB oplog auth errors at debug level.
+- Remove trailing underscore trimming from json flattener.
+- Revert change causing CPU usage to be capped at 100 percent.
+- Accept any media type in the Prometheus Format (`prometheus`) input plugin.
+- Fix unix socket dial arguments in uWSGI (`uwsgi`) input plugin.
+- Replace colon characters in Prometheus (`prometheus_client`) output labels with `metric_version=1`.
+- Set TrimLeadingSpace when TrimSpace is on in CSV (`csv`) parser.
+
+## v1.12.6 [2019-11-19]
+
+### Bug fixes
+- Fix many plugin errors logged at debug logging level.
+- Use nanosecond precision in Docker Log (`docker_log`) input plugin.
+- Fix interface option with `method = native` in Ping (`ping`) input plugin.
+- Fix panic in MongoDB (`mongodb`) input plugin if shard connection pool stats are unreadable.
+
+## v1.12.5 [2019-11-12]
+
+### Bug fixes
+- Fix incorrect results in Ping (`ping`) input plugin.
+- Add missing character replacement to `sql_instance` tag.
+- Change `no metric` error message to `debug` level in CloudWatch (`cloudwatch`) input plugin.
+- Add missing `ServerProperties` query to SQLServer (`sqlserver`) input plugin documentation.
+- Fix MongoDB `connections_total_created` field loading.
+- Fix metric creation when node is offline in Jenkins (`jenkins`) input plugin.
+- Fix Docker `uptime_ns` calculation when container has been restarted.
+- Fix MySQL field type conflict in conversion of `gtid_mode` to an integer.
+- Fix MySQL field type conflict with `ssl_verify_depth` and `ssl_ctx_verify_depth`.
+
+## v1.12.4 [2019-10-23]
+
+- Build official packages with Go 1.12.12.
+
+### Bug fixes
+- Fix metric generation with Ping (`ping`) input plugin `native` method.
+- Exclude alias tag if unset from plugin internal stats.
+- Fix `socket_mode` option in PowerDNS Recursor (`powerdns_recursor`) input plugin.
+
+## v1.12.3 [2019-10-07]
+
+- Build official packages with Go 1.12.10.
+
+### Bug fixes
+- Use batch serialization format in Exec (`exec`) output plugin.
+- Use case-insensitive serial number match in S.M.A.R.T. (`smart`) input plugin.
+- Add authorization header only when environment variable is set.
+- Fix issue when running multiple MySQL and SQL Server plugin instances.
+- Fix database routing on retry with `exclude_database_tag`.
+- Fix logging panic in Exec (`exec`) input plugin with Nagios data format.
+
+## v1.12.2 [2019-09-24]
+
+### Bug fixes
+- Fix timestamp format detection in `csv` and `json` parsers.
+- Apcupsd input (`apcupsd`)
+  - Fix parsing of `BATTDATE`.
+- Keep boolean values listed in `json_string_fields`.
+- Disable Go plugin support in official builds.
+- Cisco GNMI Telemetry input (`cisco_telemetry_gnmi`)
+  - Fix path handling issues.
+
+## v1.12.1 [2019-09-10]
+
+### Bug fixes
+- Fix dependenciess on GLIBC_2.14 symbol version.
+- Filecount input (`filecount`)
+  - Fix filecount for paths with trailing slash.
+- Icinga2 input (`icinga2`)
+  - Convert check state to an integer.
+- Apache Kafka Consumer input (`kafka_consumer`)
+  - Fix could not mark message delivered error.
+- MongoDB input (`mongodb`)
+  - Skip collection stats when disabled.
+- HTTP Response input (`http_response`)
+  - Fix error reading closed response body.
+- Apcupsd input (`apcupsd`)
+  - Fix documentation to reflect plugin.
+- InfluxDB v2 output (`influxdb_v2`)
+  - Display retry log message only when retry after is received.
+
+
+## v1.12 [2019-09-03]
+
+### Release Notes
+- The cluster health related fields in the Elasticsearch input have been split out
+  from the `elasticsearch_indices` measurement into the new `elasticsearch_cluster_health_indices`
+  measurement as they were originally combined by error.
+
+### New Inputs
+- [Apcupsd](https://github.com/influxdata/telegraf/blob/master/plugins/inputs/apcupsd/README.md) (`apcupsd`) - Contributed by @jonaz
+- [Docker Log](https://github.com/influxdata/telegraf/blob/master/plugins/inputs/docker_log/README.md) (`docker_log`) - Contributed by @prashanthjbabu
+- [Fireboard](https://github.com/influxdata/telegraf/blob/master/plugins/inputs/fireboard/README.md) (`fireboard`) - Contributed by @ronnocol
+- [Logstash](https://github.com/influxdata/telegraf/blob/master/plugins/inputs/logstash/README.md) (`logstash`) - Contributed by @lkmcs @dmitryilyin @arkady-emelyanov
+- [MarkLogic](https://github.com/influxdata/telegraf/blob/master/plugins/inputs/marklogic/README.md) (`marklogic`) - Contributed by @influxdata
+- [OpenNTPD](https://github.com/influxdata/telegraf/blob/master/plugins/inputs/openntpd/README.md) (`openntpd`) - Contributed by @aromeyer
+- [uWSGI](https://github.com/influxdata/telegraf/blob/master/plugins/inputs/uwsgi) (`uwsgi`) - Contributed by @blaggacao
+
+### New Parsers
+- [From Urlencoded](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/form_urlencoded) (`form_urlencoded`) - Contributed by @byonchev
+
+### New Processors
+- [Date](https://github.com/influxdata/telegraf/blob/master/plugins/processors/date/README.md) (`date`) - Contributed by @influxdata
+- [Pivot](https://github.com/influxdata/telegraf/blob/master/plugins/processors/pivot/README.md) (`pivot`) - Contributed by @influxdata
+- [Tag Limit](https://github.com/influxdata/telegraf/blob/master/plugins/processors/tag_limit/README.md) (`tag_limit`) - Contributed by @memory
+- [Unpivot](https://github.com/influxdata/telegraf/blob/master/plugins/processors/unpivot/README.md) (`unpivot`) - Contributed by @influxdata
+
+### New Outputs
+- [Exec](https://github.com/influxdata/telegraf/blob/master/plugins/outputs/exec/README.md) (`exec`) - Contributed by @Jaeyo
+
+### Features
+- Improve performance of `wavefront` serializer.
+- Allow `regex` processor to append tag values.
+- Add `starttime` field to `phpfpm` input.
+- Add cluster name tag to elasticsearch indices.
+- Add support for interface field in `http_response` input plugin.
+- Add container uptime_ns in `docker` input plugin.
+- Add better user-facing errors for API timeouts in docker input.
+- Add TLS mutual auth support to `jti_openconfig_telemetry` input.
+- Add support for ES 7.x to `elasticsearch` output.
+- Add basic auth to `prometheus` input plugin.
+- Add node roles tag to `elasticsearch` input.
+- Support floats in `statsd` percentiles.
+- Add native Go ping method to `ping` input plugin.
+- Resume from last known offset in `tail` input when reloading Telegraf.
+- Add improved support for Azure SQL Database to `sqlserver` input.
+- Add extra attributes for NVMe devices to `smart` input.
+- Add `docker_devicemapper` measurement to `docker` input plugin.
+- Add basic auth support to `elasticsearch` input.
+- Support string field glob matching in `json` parser.
+- Update gjson to allow multipath syntax in `json` parser.
+- Add support for collecting SQL Requests to identify waits and blocking to `sqlserver` input.
+- Collect k8s endpoints, ingress, and services in `kube_inventory` plugin.
+- Add support for field/tag keys to `strings` processor.
+- Add certificate verification status to `x509_cert` input.
+- Support percentage value parsing in `redis` input.
+- Load external Go plugins from `--plugin-directory`.
+- Add ability to exclude db/bucket tag from `influxdb` outputs.
+- Gather per collections stats in `mongodb` input plugin.
+- Add TLS & credentials configuration for `nats_consumer` input plugin.
+- Add support for enterprise repos to `github` plugin.
+- Add Indices stats to `elasticsearch` input.
+- Add left function to `string` processor.
+- Add grace period for metrics late for aggregation.
+- Add `diff` and `non_negative_diff` to `basicstats` aggregator.
+- Add device tags to `smart_attributes`.
+- Collect `framework_offers` and `allocator` metrics in `mesos` input.
+- Add Telegraf and Go version to the `internal` input plugin.
+- Update the number of logical CPUs dynamically in `system` plugin.
+- Add darwin (macOS) builds to the release.
+- Add configurable timeout setting to `smart` input.
+- Add `memory_usage` field to `procstat` input plugin.
+- Add support for custom attributes to `vsphere` input.
+- Add `cmdstat` metrics to `redis` input.
+- Add `content_length` metric to `http_response` input plugin.
+- Add `database_tag` option to `influxdb_listener` to add database from query string.
+- Add capability to limit TLS versions and cipher suites.
+- Add `topic_tag` option to `mqtt_consumer`.
+- Add ability to label inputs for logging.
+- Add TLS support to `nginx_plus`, `nginx_plus_api` and `nginx_vts`.
+
+### Bug fixes
+- Fix sensor read error stops reporting of all sensors in `temp` input.
+- Fix double pct replacement in `sysstat` input.
+- Fix race in master node detection in `elasticsearch` input.
+- Fix SSPI authentication not working in `sqlserver` input.
+- Fix memory error panic in `mqtt` input.
+- Support Kafka 2.3.0 consumer groups.
+- Fix persistent session in `mqtt_consumer`.
+- Fix finder inconsistencies in `vsphere` input.
+- Fix parsing multiple metrics on the first line of tailed file.
+- Send TERM to `exec` processes before sending KILL signal.
+- Query oplog only when connected to a replica set.
+- Use environment variables to locate Program Files on Windows.
+
+## v1.11.5 [2019-08-27]
+
+### Bug fixes
+- Update `go-sql-driver/mysql` driver to 1.4.1 to address auth issues.
+- Return error status from `--test` if input plugins produce an error.
+- Fix with multiple instances only last configuration is used in smart input.
+- Build official packages with Go 1.12.9.
+- Split out `-w` argument in `iptables` input plugin.
+- Add support for parked process state on Linux.
+- Remove leading slash from rcon command.
+- Allow jobs with dashes in the name in `lustre2` input plugin.
+
+## v1.11.4 [2019-08-06]
+
+### Bug fixes
+
+#### Plugins
+- Kubernetes input (`kubernetes`)
+  - Correct typo in `logsfs_available_bytes` field.
+- Datadog output (`datadog`)
+  - Skip floats that are `NaN` or `Inf`.
+- Socket Listener input (`socket_listener`)
+  - Fix reload panic.
+
+## v1.11.3 [2019-07-23]
+
+### Bug fixes
+
+#### Agent
+
+- Treat empty array as successful parse in JSON parser.
+- Fix template pattern partial wildcard matching.
+
+#### Plugins
+
+- Bind input (`bind`)
+  - Add missing `rcode` and `zonestat`.
+- GitHub input
+  - - Fix panic.
+- Lustre2 input (`lustre2`)
+  - Fix config parse regression.
+- NVIDIA-SMI output (`nvidia-smi`)
+  - Handle unknown error.
+- StatD input (`statd`)
+  - Fix panic when processing Datadog events.
+- VMware vSphere input (`vsphere`)
+  - Fix unable to reconnect after vCenter reboot.
+
+## v1.11.2 [2019-07-09]
+
+### Bug fixes
+
+#### Plugins
+
+- Bind input (`bind`)
+  - Fix `value out of range` error on 32-bit systems.
+- Burrow input (`burrow`)
+  - Apply topic filter to partition metrics.
+- Filecount input (`filecount`)
+  - Fix path separator handling in Windows.
+- Logparser input (`logparser`)
+  - Fix stop working after reload.
+- Ping input (`ping`)
+  - Fix source address ping flag on BSD.
+- StatsD input (`statsd`)
+  - Fix panic with empty Datadog tag string.
+- Tail input (`tail`)
+  - Fix stop working after reload.
+
+## v1.11.1 [2019-06-25]
+
+### Bug fixes
+
+#### Agent
+
+- Fix panic if `pool_mode` column does not exist.
+- Add missing `container_id` field to `docker_container_status` metrics.
+- Add `device`, `serial_no`, and `wwn` tags to synthetic attributes.
+
+#### Plugins
+
+- Cisco GNMI Telemetry input (`cisco_telemetry_gnmi`)
+  - Omit keys when creating measurement names for GNMI telemetry.
+- Disk input (`disk`)
+  - Cannot set `mount_points` option.
+- NGINX Plus API input (`nginx_plus_api`)
+  - Skip 404 error reporting.
+- Procstat input (`procstat`)
+  - Don't consider `pid` of `0` when using systemd lookup.
+- StatsD input (`statsd`)
+  - Fix parsing of remote TCP address.
+- System input (`system`)
+  - Ignore error when `utmp` is missing.
+
+## v1.11.0 [2019-06-11]
+
+- System (`system`) input plugin
+  - The `uptime_format` field has been deprecated — use the `uptime` field instead.
+- Amazon Cloudwatch Statistics (`cloudwatch`) input plugin
+  - Updated to use a more efficient API and now requires `GetMetricData` permissions
+   instead of `GetMetricStatistics`.  The `units` tag is not
+   available from this API and is no longer collected.
+
+### New input plugins
+
+- [BIND 9 Nameserver Statistics (`bind`)](https://github.com/influxdata/telegraf/blob/release-1.11/plugins/inputs/bind/README.md) - Contributed by @dswarbrick & @danielllek
+- [Cisco GNMI Telemetry (`cisco_telemetry_gnmi`)](https://github.com/influxdata/telegraf/blob/release-1.11/plugins/inputs/cisco_telemetry_gnmi/README.md) - Contributed by @sbyx
+- [Cisco Model-driven Telemetry (`cisco_telemetry_mdt`)](https://github.com/influxdata/telegraf/blob/release-1.11/plugins/inputs/cisco_telemetry_mdt/README.md) - Contributed by @sbyx
+- [ECS (`ecs`)](https://github.com/influxdata/telegraf/blob/release-1.11/plugins/inputs/ecs/README.md) - Contributed by @rbtr
+- [GitHub (`github`)](https://github.com/influxdata/telegraf/blob/release-1.11/plugins/inputs/github/README.md) - Contributed by @influxdata
+- [OpenWeatherMap (`openweathermap`)](https://github.com/influxdata/telegraf/blob/release-1.11/plugins/inputs/openweathermap/README.md) - Contributed by @regel
+- [PowerDNS Recursor (`powerdns_recursor`)](https://github.com/influxdata/telegraf/blob/release-1.11/plugins/inputs/powerdns_recursor/README.md) - Contributed by @dupondje
+
+### New aggregator plugins
+
+- [Final (`final`)](https://github.com/influxdata/telegraf/blob/release-1.11/plugins/aggregators/final/README.md) - Contributed by @oplehto
+
+### New output plugins
+
+- [Syslog (`syslog`)](https://github.com/influxdata/telegraf/blob/release-1.11/plugins/outputs/syslog/README.md) - Contributed by @javicrespo
+- [Health (`health`)](https://github.com/influxdata/telegraf/blob/release-1.11/plugins/outputs/health/README.md) - Contributed by @influxdata
+
+### New output data formats (serializers)
+
+- [wavefront](https://github.com/influxdata/telegraf/blob/release-1.11/plugins/serializers/wavefront/README.md) - Contributed by @puckpuck
+
+### Features
+
+#### Agent
+
+- Add CLI support for outputting sections of the configuration.
+- Add `service-display-name` option for use with Windows service.
+- Add support for log rotation.
+- Allow env vars `${}` expansion syntax in configuration file.
+- Allow devices option to match against devlinks.
+
+### Input data formats
+
+- Nagios
+  - Add support for multiple line text and perfdata.
+
+#### Input plugins
+
+- AMQP Consumer (`amqp_consumer`)
+  - Support passive queue declaration.
+  - Add support for gzip compression.
+- Amazon Cloudwatch Statistics (`cloudwatch`)
+  - Use more efficient GetMetricData API to collect Cloudwatch metrics.
+  - Allow selection of collected statistic types in cloudwatch input.
+- Apache Solr (`solr`)
+  - Add support for HTTP basic auth.
+- Hddtemp (`hddtemp`)
+  - Add source tag.
+- InfluxDB Listener (`influxdb_listener`)
+  - Support verbose query parameter in ping endpoint.
+- NVIDIA SMI (`nvidia-smi`)
+  - Extend metrics collected from Nvidia GPUs.
+- Net (`net`)
+  - Speed up interface stat collection.
+- PHP FM (`phpfm`)
+  - Enhance HTTP connection options.
+- Ping (`ping`)
+  - Add TTL field.
+- Procstat (`procstat`)
+  - Add `cmdline` tag.
+  - Add pagefault data.
+- Prometheus (`prometheus`)
+  - Add namespace restriction.
+- SMART (`smart`)
+  - Support more drive types.
+- Socket Listener (`socket_listener`)
+  - Add option to set permissions for UNIX domain sockets.
+- StatsD (`statsd`)
+  - Add support for Datadog events.
+
+### Output plugins
+
+- AMQP (`amqp`)
+  - Add support for gzip compression.
+- File (`file`)
+  - Add file rotation support.
+- Stackdriver (`stackdriver`)
+  - Set user agent.
+-- VMware Wavefront (`wavefront`)
+  - Add option to use strict sanitization rules.
+
+### Aggregator plugins
+
+- Histogram aggregator
+  - Add option to reset buckets on flush.
+
+#### Processor plugins
+
+- Converter (`converter`)
+  - Add hexadecimal string to integer conversion.
+- Enum (`enum`)
+  - Support tags.
+
+### Bug fixes
+
+#### Agent
+
+- Create Windows service only when specified or in service manager.
+- Don't start Telegraf when stale pid file found.
+- Fix inline table support in configuration file.
+- Fix multi-line basic strings support in configuration file.
+- Fix multiple SIGHUP causes Telegraf to shutdown.
+- Fix batch fails when single metric is unserializable.
+- Log a warning on write if the metric buffer has overflowed.
+
+#### Plugins
+
+- AMQP (`amqp`) output
+  - Fix direct exchange routing key.
+- Apex Neptune (`apex_neptune`) inpur
+  - Skip invalid power times.
+- Docker (`docker`) input
+  - Fix docker input does not parse image name correctly.
+- Fibaro (`fibaro`) input
+  - Set default timeout of `5s`.
+- InfluxDB v1.x (`influxdb`) output
+  - Fix connection leak on reload.
+- InfluxDB v2 output
+  - Fix connection leak on reload.
+- Lustre 2 (`lustre2`) input
+  - Fix only one job per storage target reported.
+- Microsoft Azure Monitor (`azure_monitor`) output
+  - Fix scale set resource id.
+- Microsoft SQL Server (`sqlserver`) input
+   Fix connection closing on error.  
+- Minecraft (`minecraft`) input
+  - Support Minecraft server 1.13 and newer.
+- NGINX Upstream Check (`nginx_upstream_check`) input
+  - Fix TOML option name.
+- PgBounder (`pgbouncer`) input
+  - Fix unsupported pkt type error.
+- Procstat (`procstat`) input
+  - Verify a process passed by `pid_file` exists.
+- VMware vSphere (`vsphere`) input
+  - Fixed datastore name mapping.
+
+## v1.10.4 [2019-05-14]
+
+### Bug fixes
+
+#### Agent
+
+- Create telegraf user in pre-install RPM scriptlet.
+- Fix parse of unix timestamp with more than ns precision.
+- Fix race condition in the Wavefront parser.
+
+#### Plugins
+
+- HTTP output plugin (`http`)
+  - Fix http output cannot set Host header.
+- IPMI Sensor input (`ipmi_sensor`)
+  - Add support for hex values.
+- InfluxDB v2 output (`influxdb_v2`)
+  - Don't discard metrics on forbidden error.
+- Interrupts input (`interrupts`)
+  - Restore field name case.
+- NTPQ input (`ntpq`)
+  - Skip lines with missing `refid`.
+- VMware vSphere input (`vsphere`)
+  - Fix interval estimation.
+
+## v1.10.3 [2019-04-16]
+
+### Bug fixes
+
+#### Agent
+
+- Set log directory attributes in RPM specification.
+
+#### Plugins
+
+- Prometheus Client (`prometheus_client`) output plugin.
+  - Allow colons in metric names.
+
+## v1.10.2 [2019-04-02]
+
+### Breaking changes
+
+ Grok input data format (parser): string fields no longer have leading and trailing quotation marks removed.  
+ If you are capturing quoted strings, the patterns might need to be updated.
+
+### Bug fixes
+
+#### Agent
+
+- Fix deadlock when Telegraf is aligning aggregators.
+- Add owned directories to RPM package specification.
+- Fix drop tracking of metrics removed with aggregator `drop_original`.
+- Fix aggregator window alignment.
+- Fix panic during shutdown of multiple aggregators.
+- Fix tags applied to wrong metric on parse error.
+
+#### Plugins
+
+- Ceph (`ceph`) input
+  - Fix missing cluster stats.
+- DiskIO (`diskio`) input
+  - Fix reading major and minor block devices identifiers.
+- File (`file`) output
+  - Fix open file error handling.
+- Filecount (`filecount`) input
+  - Fix basedir check and parent dir extraction.
+- Grok (`grok`) parser
+  - Fix last character removed from string field.
+- InfluxDB v2 (`influxdb_v2`) output
+  - Fix plugin name in output logging.
+- Prometheus (`prometheus`) input
+  - Fix parsing of kube config `certificate-authority-data`.
+- Prometheus (`prometheus`) output
+  - Remove tags that would create invalid label names.
+- StatsD (`statsd`) input
+  - Listen before leaving start.
+
+## v1.10.1 [2019-03-19]
+
+#### Bug fixes
+
+- Show error when TLS configuration cannot be loaded.
+- Add base64-encoding/decoding for Google Cloud PubSub (`pubsub`) plugins.
+- Fix type compatibility in VMware vSphere (`vsphere`) input plugin with `use_int_samples` option.
+- Fix VMware vSphere (`vsphere`) input plugin shows failed task in vCenter.
+- Fix invalid measurement name and skip column in the CSV input data format parser.
+- Fix System (`system`) input plugin causing high CPU usage on Raspbian.
+
+## v1.10 [2019-03-05]
+
+#### New input plugins
+
+- [Google Cloud PubSub (`cloud_pubsub`)](https://github.com/influxdata/telegraf/blob/release-1.10/plugins/inputs/cloud_pubsub/README.md) - Contributed by @emilymye
+- [Kubernetes Inventory (`kube_inventory`)](https://github.com/influxdata/telegraf/blob/release-1.10/plugins/inputs/cloud_pubsub_push/README.md) - Contributed by @influxdata
+- [Neptune Apex (`neptune_apex`)](https://github.com/influxdata/telegraf/blob/release-1.10/plugins/inputs/neptune_apex/README.md) - Contributed by @MaxRenaud
+- [NGINX Upstream Check (`nginx_upstream_check`)](https://github.com/influxdata/telegraf/blob/release-1.10/plugins/inputs/nginx_upstream_check/README.md) - Contributed by @dmitryilyin
+- [Multifile (`multifile`)](https://github.com/influxdata/telegraf/blob/release-1.10/plugins/inputs/multifile/README.md) - Contributed by @martin2250
+
+#### New output plugins
+
+- [Google Cloud PubSub (`cloud_pubsub`)](https://github.com/influxdata/telegraf/blob/release-1.10/plugins/outputs/cloud_pubsub/README.md) - Contributed by @emilymye
+
+#### New output data formats (serializers)
+
+- [ServiceNow Metrics](/telegraf/v1.12/data_formats/output/nowmetric) - Contributed by @JefMuller
+- [Carbon2](/telegraf/v1.12/data_formats/output/carbon2) - Contributed by @frankreno
+
+#### Features
+
+- **General**
+  - Allow for force gathering ES cluster stats.
+  - Add Linux `mipsle` packages.
+- **Input plugins**
+  - Ceph (`ceph`)
+    - Add read and write op per second fields.
+  - CouchDB (`couchdb`)
+    - Add support for basic auth.
+  - DNS Query (`dns_query`)
+    - Add `rcode` tag and field.
+  - DiskIO (`diskio`)
+    - Include `DEVLINKS` in available `udev` properties.
+  - HTTP (`http`)
+    - Add support for sending a request body to `http` input.
+  - InfluxDB Listener (`influxdb_listener`)
+    - Add internal metric for line too long.
+  - Interrupts (`interrupts`)
+    - Add option to store `cpu` as a tag.
+  - Kafka Consumer (`kafka_consumer`)
+    - Add ability to tag metrics with topic.
+  - Kubernetes (`k8s`)
+  - Support passing bearer token directly.
+  - Microsoft SQL Server (`sqlserver`)
+    - Add log send and redo queue fields.
+  - MongoDB (`mongodb`)
+    - Add `flush_total_time_ns` and additional wired tiger fields.
+  - Procstat (`procstat_lookup`)
+    - Add running field.
+  - Prometheus (`prometheus`)
+    - Support passing bearer token directly.
+    - Add option to report input timestamp.
+  - VMware vSphere (`vsphere`)
+    - Improve scalability.
+    - Add resource path-based filtering.
+  - Varnish (`varnish`)
+    - Add configurable timeout.
+- **Output plugins**
+  - MQTT (`mqtt`)
+    - Add option to set retain flag on messages.
+  - Stackdriver (`stackdriver`)
+    - Add resource type and resource label support
+  - VMware Wavefront (`wavefront`)
+    - Add support for the Wavefront Direct Ingestion API.
+- **Aggregator plugins**
+  - Value Counter (`valuecounter`)
+    - Allow counting float values.
+- **Data formats**
+  - **Input data formats**
+  - CSV
+    - Support `unix_us` and `unix_ns` timestamp format.
+    - Add support for `unix` and `unix_ms` timestamps.
+  - Grok (`grok`)
+    - Allow parser to produce metrics with no fields.
+  - JSON
+    - Add micro and nanosecond unix timestamp support.
+  - **Output data formats**
+    - ServiceNow Metrics
+
+#### Bug fixes
+
+- **General**
+  - Use `systemd` in Amazon Linux 2 rpm.
+  - Fix `initscript` removes `pidfile` of restarted Telegraf process.
+- **Input plugins**
+  - Consul (`consul`)
+    - Use datacenter option spelling.
+  - InfluxDB Listener (`influxdb_listener`)
+    - Remove auth from `/ping` route.
+  - Microsoft SQL Server (`sqlserver`)
+    - Set deadlock priority.
+  - Nstat (`nstat`)
+    - Remove error log when `snmp6` directory does not exist.
+  - Ping (`ping`)
+    - Host not added when using custom arguments.
+  - X.509 Certificate
+    - Fix input stops checking certificates after first error.
+- **Output plugins**
+  - Prometheus (`prometheus`)
+    - Sort metrics by timestamp.
+  - Stackdriver (`stackdriver`)
+    - Skip string fields when writing.
+    - Send metrics in ascending time order.
+
+## v1.9.5 [2019-02-26]
+
+### Bug fixes
+
+* General
+  * Use `systemd` in Amazon Linux 2 rpm.
+* Ceph Storage (`ceph`) input plugin
+  * Add backwards compatibility fields in usage and pool statistics.
+* InfluxDB (`influxdb`) output plugin
+  * Fix UDP line splitting.  
+* Microsoft SQL Server (`sqlserver`) input plugin
+  * Set deadlock priority to low.
+  * Disable results by row in AzureDB query.
+* Nstat (`nstat`) input plugin
+  * Remove error log when `snmp6` directory does not exist.
+* Ping (`ping`) input plugin
+  * Host not added when using custom arguments.
+* Stackdriver (`stackdriver`) output plugin
+  * Skip string fields when writing to stackdriver output.
+  * Send metrics in ascending time order.
+
+## v1.9.4 [2019-02-05]
+
+### Bug fixes
+
+* General
+  * Fix `skip_rows` and `skip_columns` options in csv parser.
+  * Build official packages with Go 1.11.5.
+* Jenkins input plugin
+  * Always send basic auth in jenkins input.
+* Syslog (`syslog`) input plugin
+    * Fix definition of multiple syslog plugins.
+
+## v1.9.3 [2019-01-22]
+
+#### Bug fixes
+
+* General
+  * Fix latest metrics not sent first when output fails.
+  * Fix `internal_write buffer_size` not reset on timed writes.
+* AMQP Consumer (`amqp_consumer`) input plugin
+  - Fix `amqp_consumer` input stops consuming when it receives
+    unparsable messages.
+* Couchbase (`couchbase`) input plugin
+  * Remove `userinfo` from cluster tag in `couchbase` input.
+* Microsoft SQL Server (`sqlserver`) input plugin
+  * Fix arithmetic overflow in `sqlserver`) input.
+* Prometheus (`prometheus`) input plugin
+  * Fix `prometheus` input not detecting added and removed pods.
+
+## v1.9.2 [2019-01-08]
+
+### Bug fixes
+
+- Increase `varnishstat` timeout.
+- Remove storage calculation for non-Azure-managed instances and add server version.
+- Fix error sending empty tag value in `azure_monitor` output.
+- Fix panic with Prometheus input plugin on shutdown.
+- Support non-transparent framing of syslog messages.
+- Apply global- and plugin-level metric modifications before filtering.
+- Fix `num_remapped_pgs` field in `ceph` plugin.
+- Add `PDH_NO_DATA` to known counter error codes in `win_perf_counters`.
+- Fix `amqp_consumer` stops consuming on empty message.
+- Fix multiple replace tables not working in strings processor.
+- Allow non-local UDP connections in `net_response`.
+- Fix TOML option names in parser processor.
+- Fix panic in Docker input with bad endpoint.
+- Fix original metric modified by aggregator filters.
+
+## v1.9.1 [2018-12-11]
+
+### Bug fixes
+
+- Fix boolean handling in splunkmetric serializer.
+- Set default config values in Jenkins input.
+- Fix server connection and document stats in MongoDB input.
+- Add X-Requested-By header to Graylog input.
+- Fix metric memory not freed from the metric buffer on write.
+- Add support for client TLS certificates in PostgreSQL inputs.
+- Prevent panic when marking the offset in `kafka_consumer`.
+- Add early metrics to aggregator and honor `drop_original` setting.
+- Use `-W` flag on BSD variants in ping input.
+- Allow delta metrics in Wavefront parser.
+
+## v1.9.0 [2018-11-20]
+
+#### Release Notes
+
+- The HTTP Listener (`http_listener`) input plugin has been renamed to
+  InfluxDB Listener (`influxdb_listener`) input plugin and
+  use of the original name is deprecated.  The new name better describes the
+  intended use of the plugin as an InfluxDB relay.  For general purpose
+  transfer of metrics in any format using HTTP, InfluxData recommends using
+  HTTP Listener v2 (`http_listener_v2`) input plugin.
+
+- Input plugins are no longer limited from adding metrics when the output is
+  writing and new metrics will move into the metric buffer as needed.  This
+  will provide more robust degradation and recovery when writing to a slow
+  output at high throughput.
+
+  To avoid overconsumption when reading from queue consumers, the following
+  input plugins use the new option `max_undelivered_messages` to limit the number
+  of outstanding unwritten metrics:
+
+  * Apache Kafka Consumer (`kafka_consumer`)
+  * AMQP Consumer (`amqp_consumer`)
+  * MQTT Consumer (`mqtt_consumer`)
+  * NATS Consumer (`nats_consumer`)
+  * NSQ Consumer (`nsq_consumer`)
+
+#### New input plugins
+
+- [HTTP Listener v2 (`http_listener_v2`)](https://github.com/influxdata/telegraf/blob/release-1.9/plugins/inputs/http_listener_v2/README.md) - Contributed by @jul1u5
+- [IPVS (`ipvs`)](https://github.com/influxdata/telegraf/blob/release-1.9/plugins/inputs/ipvs/README.md) - Contributed by @amoghe
+- [Jenkins (`jenkins`)](https://github.com/influxdata/telegraf/blob/release-1.9/plugins/inputs/jenkins/README.md) - Contributed by @influxdata & @lpic10
+- [NGINX Plus API (`nginx_plus_api`)](https://github.com/influxdata/telegraf/blob/release-1.9/plugins/inputs/nginx_plus_api/README.md) - Contributed by @Bugagazavr
+- [NGINX VTS (`nginx_vts`)](https://github.com/influxdata/telegraf/blob/release-1.9/plugins/inputs/nginx_vts/README.md) - Contributed by @monder
+- [Wireless (`wireless`)](https://github.com/influxdata/telegraf/blob/release-1.9/plugins/inputs/wireless/README.md) - Contributed by @jamesmaidment
+
+#### New output plugins
+
+- [Stackdriver (stackdriver)](https://github.com/influxdata/telegraf/blob/release-1.9/plugins/outputs/stackdriver/README.md) - Contributed by @jamesmaidment
+
+#### Features
+
+- General
+  - Add ability to define a custom service name when installing as a Windows service.
+  - Add new configuration for CSV column explicit type conversion.
+  - Add Telegraf version to `User-Agent` header.
+  - Add ability to specify bytes options as strings with units.
+  - Add per output `flush_interval`, `metric_buffer_limit`, and `metric_batch_size`.
+- Amazon Kinesis (`kinesis`) output plugin
+  - Use `DescribeStreamSummary` in place of `ListStreams`.
+- DNS Query (`dns_query`) input plugin
+  - Query servers in parallel.
+- Datadog (`datadog`) output plugin
+  - Add an option to specify a custom URL.
+  - Use non-allocating field and tag accessors.
+- Filecount (`filecount`) input plugin
+  - Add per-directory file count.
+- HTTP Output (`http output`) plugin
+  - Add entity-body compression.
+- Memcached (`memcached`) input plugin
+  - Collect additional statistics.
+- NSQ (`nsq`) input plugin
+  - Add TLS configuration support.
+- Ping (`ping`) input plugin
+  - Add support for IPv6.
+- Procstat (`procstat`) input plugin
+  - Add Windows service name lookup.
+- Prometheus (`prometheus`) input plugin
+  - Add scraping for Prometheus annotation in Kubernetes.
+  - Allow connecting to Prometheus using UNIX socket.
+- Strings (`strings`) processor plugin
+  - Add `replace` function.
+- VMware vSphere (`vsphere`) input plugin
+  - Add LUN to data source translation.
+
+#### Bug fixes
+
+- Remove `time_key` from the field values in JSON parser.
+- Fix input time rounding when using a custom interval.
+- Fix potential deadlock or leaked resources on restart or reload.
+- Fix outputs block inputs when batch size is reached.
+- Fix potential missing datastore metrics in VMware vSphere (`vsphere`) input plugin.
+
+## v1.8.3 [2018-10-30]
+
+### Bug fixes
+
+- Add DN attributes as tags in X.509 Certificate (`x509_cert`) input plugin to avoid series overwrite.
+- Prevent connection leak by closing unused connections in AMQP (`amqp`) output plugin.
+- Use default partition key when tag does not exist in Amazon Kinesis (`kinesis`) output plugin.
+- Log the correct error in JTI OpenConfig Telemetry (`jti_openconfig_telemetry`) input plugin.
+- Handle panic when IMPI Sensor (`ipmi_sensor`) input plugin gets bad input.
+- Don't add unserializable fields to Jolokia2 (`jolokia2`) input plugin.
+- Fix version check in PostgreSQL Exstensible (`postgresql_extensible`) plugin.
+
+## v1.8.2 [2018-10-17]
+
+### Bug fixes
+
+* Aerospike (`aerospike`) input plugin
+  * Support uint fields.
+* Docker (`docker`) input plugin
+  * Use container name from list if no name in container stats.
+* Filecount (`filecount`) input plugin
+  * Prevent panic on error in file stat.
+* InfluxDB v2 (`influxdb_v2`) input plugin
+  * Update write path to match updated v2 API.
+* Logparser (`logparser`) input plugin
+  * Fix panic.
+* MongoDB (`mongodb`) input plugin
+  * Lower authorization errors to debug level.
+* MQTT Consumer (`mqtt_consumer`) input plugin
+  * Fix connect and reconnect.
+* Ping (`ping`) input plugin
+  * Return correct response code.
+* VMware vSphere (`vsphere`) input plugin
+  * Fix missing timeouts.
+* X.509 Certificate (`x509_cert`) input plugin
+  * Fix segfault.
+
+## v1.8.1 [2018-10-03]
+
+### Bug fixes
+
+- Fix `hardware_type` may be truncated in Microsoft SQL Server (`sqlserver`) input plugin.
+- Improve performance in Basicstats (`basicstats`) aggregator plugin.
+- Add `hostname` to TLS config for SNI support in X.509 Certicate (`x509_cert`) input plugin.
+- Don't add tags with empty values to OpenTSDB (`opentsdb`) output plugin.
+- Fix panic during network error in VMware vSphere (`vsphere`) input plugin.
+- Unify error response in HTTP Listener (`http_listener`) input plugin with InfluxDB (`influxdb`) output plugin.
+- Add `UUID` to VMs in VMware vSphere (`vsphere`) input plugin.
+- Skip tags with empty values in Amazon Cloudwatch (`cloudwatch`) output plugin.
+- Fix missing non-realtime samples in VMware vSphere (`vsphere`) input plugin.
+- Fix case of `timezone`/`grok_timezone` options in grok parser and logparser input plugin.
+
+## v1.8 [2018-09-21]
+
+### New input plugins
+
+- [ActiveMQ (`activemq`)](https://github.com/influxdata/telegraf/blob/release-1.8/plugins/inputs/activemq/README.md) - Contributed by @mlabouardy
+- [Beanstalkd (`beanstalkd`)](https://github.com/influxdata/telegraf/blob/release-1.8/plugins/inputs/beanstalkd/README.md) - Contributed by @44px
+- [File (`file`)](https://github.com/influxdata/telegraf/blob/release-1.8/plugins/inputs/file/README.md) - Contributed by @maxunt
+- [Filecount (`filecount`)](https://github.com/influxdata/telegraf/blob/release-1.8/plugins/inputs/filecount/README.md) - Contributed by @sometimesfood
+- [Icinga2 (`icinga2`)](https://github.com/influxdata/telegraf/blob/release-1.8/plugins/inputs/icinga2/README.md) - Contributed by @mlabouardy
+- [Kibana (`kibana`)](https://github.com/influxdata/telegraf/blob/release-1.8/plugins/inputs/kibana/README.md) - Contributed by @lpic10
+- [PgBouncer (`pgbouncer`)](https://github.com/influxdata/telegraf/blob/release-1.8/plugins/inputs/pgbouncer/README.md) - Contributed by @nerzhul
+- [Temp (`temp`)](https://github.com/influxdata/telegraf/blob/release-1.8/plugins/inputs/temp/README.md) - Contributed by @pytimer
+- [Tengine (`tengine`)](https://github.com/influxdata/telegraf/blob/release-1.8/plugins/inputs/tengine/README.md) - Contributed by @ertaoxu
+- [VMware vSphere (`vsphere`)](https://github.com/influxdata/telegraf/blob/release-1.8/plugins/inputs/vsphere/README.md) - Contributed by @prydin
+- [X.509 Certificate (`x509_cert`)](https://github.com/influxdata/telegraf/blob/release-1.8/plugins/inputs/x509_cert/README.md) - Contributed by @jtyr
+
+### New processor plugins
+
+- [Enum (`enum`)](https://github.com/influxdata/telegraf/blob/release-1.8/plugins/processors/enum/README.md) - Contributed by @KarstenSchnitter
+- [Parser (`parser`)](https://github.com/influxdata/telegraf/blob/release-1.8/plugins/processors/parser/README.md) - Contributed by @Ayrdrie & @maxunt
+- [Rename (`rename`)](https://github.com/influxdata/telegraf/blob/release-1.8/plugins/processors/rename/README.md) - Contributed by @goldibex
+- [Strings (`strings`)](https://github.com/influxdata/telegraf/blob/release-1.8/plugins/processors/strings/README.md) - Contributed by @bsmaldon
+
+### New aggregator plugins
+
+- [ValueCounter (`valuecounter`)](https://github.com/influxdata/telegraf/blob/release-1.8/plugins/aggregators/valuecounter/README.md) - Contributed by @piotr1212
+
+### New output plugins
+
+- [Azure Monitor (`azure_monitor`)](https://github.com/influxdata/telegraf/blob/release-1.8/plugins/outputs/azure_monitor/README.md) - Contributed by @influxdata
+- [InfluxDB v2 (`influxdb_v2`)](https://github.com/influxdata/telegraf/blob/release-1.8/plugins/outputs/influxdb_v2/README.md) - Contributed by @influxdata
+
+### New input data formats (parsers)
+
+- [csv](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/csv) - Contributed by @maxunt
+- [grok](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/grok/) - Contributed by @maxunt
+- [logfmt](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/logfmt/) - Contributed by @Ayrdrie & @maxunt
+- [wavefront](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/wavefront/) - Contributed by @puckpuck
+
+### New output data formats (serializers)
+
+- [splunkmetric](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/output/splunkmetric/) - Contributed by @ronnocol
+
+### Features
+
+- Add SSL/TLS support to Redis (`redis`) input plugin.
+- Add tengine input plugin.
+- Add power draw field to the NVIDIA SMI (`nvidia_smi`) input plugin.
+- Add support for Solr 7 to the Solr (`solr`) input plugin.
+- Add owner tag on partitions in Burrow (`burrow`) input plugin.
+- Add container status tag to Docker (`docker`) input plugin.
+- Add ValueCounter (`valuecounter`) aggregator plugin.
+- Add new measurement with results of `pgrep` lookup to Procstat (`procstat`) input plugin.
+- Add support for comma in logparser timestamp format.
+- Add path tag to Tail (`tail`) input plugin.
+- Add log message when tail is added or removed from a file.
+- Add option to use of counter time in win perf counters.
+- Add energy and power field and device id tag to Fibaro (`fibaro`) input plugin.
+- Add HTTP path configuration for OpenTSDB output.
+- Gather IPMI metrics concurrently.
+- Add mongo document and connection metrics.
+- Add enum processor plugin.
+- Add user tag to procstat input.
+- Add support for multivalue metrics to collectd parser.
+- Add support for setting kafka client id.
+- Add file input plugin and grok parser.
+- Improve cloudwatch output performance.
+- Add x509_cert input plugin.
+- Add IPSIpAddress syntax to ipaddr conversion in snmp plugin.
+- Add Filecount filecount input plugin.
+- Add support for configuring an AWS `endpoint_url`.
+- Send all messages before waiting for results in Kafka output plugin.
+- Add support for lz4 compression to Kafka output plugin.
+- Split multiple sensor keys in ipmi input.
+- Support StatisticValues in cloudwatch output plugin.
+- Add ip restriction for the prometheus_client output.
+- Add PgBouncer (`pgbouncer`) input plugin.
+- Add ActiveMQ input plugin.
+- Add wavefront parser plugin.
+- Add rename processor plugin.
+- Add message 'max_bytes' configuration to kafka input.
+- Add gopsutil meminfo fields to Mem (`mem`) input plugin.
+- Document how to parse Telegraf logs.
+- Use dep v0.5.0.
+- Add ability to set measurement from matched text in grok parser.
+- Drop message batches in Kafka (`kafka`) output plugin if too large.
+- Add support for static and random routing keys in Kafka (`kafka`) output plugin.
+- Add logfmt parser plugin.
+- Add parser processor plugin.
+- Add Icinga2 input plugin.
+- Add name, time, path and string field options to JSON parser.
+- Add forwarded records to sqlserver input.
+- Add Kibana input plugin.
+- Add csv parser plugin.
+- Add read_buffer_size option to statsd input.
+- Add azure_monitor output plugin.
+- Add queue_durability parameter to amqp_consumer input.
+- Add strings processor.
+- Add OAuth 2.0 support to HTTP output plugin.
+- Add Unix epoch timestamp support for JSON parser.
+- Add options for basic auth to haproxy input.
+- Add temp input plugin.
+- Add Beanstalkd input plugin.
+- Add means to specify server password for redis input.
+- Add Splunk Metrics serializer.
+- Add input plugin for VMware vSphere.
+- Align metrics window to interval in cloudwatch input.
+- Improve Azure Managed Instance support + more in sqlserver input.
+- Allow alternate binaries for iptables input plugin.
+- Add influxdb_v2 output plugin.
+
+### Bug fixes
+
+- Fix divide by zero in logparser input.
+- Fix instance and object name in performance counters with backslashes.
+- Reset/flush saved contents from bad metric.
+- Document all supported cli arguments.
+- Log access denied opening a service at debug level in win_services.
+- Add support for Kafka 2.0.
+- Fix nagios parser does not support ranges in performance data.
+- Fix nagios parser does not strip quotes from performance data.
+- Fix null value crash in postgresql_extensible input.
+- Remove the startup authentication check from the cloudwatch output.
+- Support tailing files created after startup in tail input.
+- Fix CSV format configuration loading.
+
+
+## v1.7.4 [2018-08-29]
+
+### Bug fixes
+
+* Continue sending write batch in UDP if a metric is unserializable in InfluxDB (`influxdb`) output plugin.
+* Fix PowerDNS (`powerdns`) input plugin tests.
+* Fix `burrow_group` offset calculation for Burrow (`burrow`) input plugin.
+* Add `result_code` value for errors running ping command.
+* Remove timeout deadline for UDP in Syslog (`syslog`) input plugin.
+* Ensure channel is closed if an error occurs in CGroup (`cgroup`) input plugin.
+* Fix sending of basic authentication credentials in HTTP `(output)` output plugin.
+* Use the correct `GOARM` value in the Linux armel package.
+
+## v1.7.3 [2018-08-07]
+
+### Bug fixes
+
+* Reduce required Docker API version.
+* Keep leading whitespace for messages in syslog input.
+* Skip bad entries on interrupt input.
+* Preserve metric type when using filters in output plugins.
+* Fix error message if URL is unparseable in InfluxDB output.
+* Use explicit `zpool` properties to fix parse error on FreeBSD 11.2.
+* Lock buffer when adding metrics.
+
+## v1.7.2 [2018-07-18]
+
+### Bug fixes
+
+* Use localhost as default server tag in Zookeeper (`zookeeper`) input plugin.
+* Don't set values when pattern doesn't match in Regex (`regex`) processor plugin.
+* Fix output format of Printer (`printer`) processor plugin.
+* Fix metric can have duplicate field.
+* Return error if NewRequest fails in HTTP (`http`) output plugin.
+* Reset read deadline for Syslog (`syslog`) input plugin.
+* Exclude cached memory on Docker (`docker`) input plugin.
+
+## v1.7.1 [2018-07-03]
+
+### Bug fixes
+
+* Treat `sigterm` as a clean shutdown signal.
+* Fix selection of tags under nested objects in the JSON parser.
+* Fix Postfix (`postfix`) input plugin handling of multilevel queues.
+* Fix Syslog (`syslog` input plugin timestamp parsing with single digit day of month.
+* Handle MySQL (`mysql`) input plugin variations in the `user_statistics` collecting.
+* Fix Minmax (`minmax`) and Basicstats (`basicstats`) aggregator plugins to use `uint64`.
+* Document Swap (`swap`) input plugin.
+* Fix incorrect precision being applied to metric in HTTP Listener (`http_listener`) input plugin.
+
+## v1.7 [2018-06-12]
+
+### Release notes
+
+- The Cassandra (`cassandra`) input plugin has been deprecated in favor of the Jolokia2 (`jolokia2`)
+  input plugin which is much more configurable and more performant.  There is
+  an [example configuration](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/jolokia2/examples) to help you
+  get started.
+
+- For plugins supporting TLS, you can now specify the certificate and keys
+  using `tls_ca`, `tls_cert`, `tls_key`.  These options behave the same as
+  the, now deprecated, `ssl` forms.
+
+### New input plugins
+
+- [Aurora (`aurora`)](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/aurora/README.md) - Contributed by @influxdata
+- [Burrow (`burrow`) input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/burrow/README.md) - Contributed by @arkady-emelyanov
+- [`fibaro`](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/fibaro/README.md) - Contributed by @dynek
+- [`jti_openconfig_telemetry`](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/jti_openconfig_telemetry/README.md) - Contributed by @ajhai
+- [`mcrouter`](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/mcrouter/README.md) - Contributed by @cthayer
+- [NVIDIA SMI (`nvidia_smi`)](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/nvidia_smi/README.md) - Contributed by @jackzampolin
+- [Syslog (`syslog`)](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/syslog/README.md) - Contributed by @influxdata
+
+### New processor plugins
+
+- [converter](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/processors/converter/README.md) - Contributed by @influxdata
+- [regex](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/processors/regex/README.md) - Contributed by @44px
+- [topk](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/processors/topk/README.md) - Contributed by @mirath
+
+### New output plugins
+
+- [HTTP (`http`)](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/outputs/http/README.md) - Contributed by @Dark0096
+- [Application Insights (`application_insights`) output plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/outputs/application_insights/README.md): Contribute by @karolz-ms
+
+### Features
+
+- Add `repl_oplog_window_sec` metric to MongoDB (`mongodb`) input plugin.
+- Add per-host shard metrics in MongoDB (`mongodb`) input plugin.
+- Skip files with leading `..` in config directory.
+- Add TLS support to `socket_writer` and `socket_listener` plugins.
+- Add `snmp` input option to strip non-fixed length index suffixes.
+- Add server version tag to the Docker (`docker`) input plugin.
+- Add support for LeoFS 1.4 to `leofs` input.
+- Add parameter to force the interval of gather for Sysstat (`sysstat`).
+- Support BusyBox ping in the Ping (`ping`) input plugin.
+- Add Mcrouter (`mcrouter`) input plugin.
+- Add TopK (`topk`) processor plugin.
+- Add cursor metrics to MongoDB (`mongodb`) input plugin.
+- Add tag/integer pair for result to Network Response (`net_response`) input plugin.
+- Add Application Insights (`application_insights`) output plugin.
+- Added several important Elasticsearch cluster health metrics.
+- Add batch mode to `mqtt` output.
+- Add Aurora (`aurora`) input plugin.
+- Add Regex (`regex`) processor plugin.
+- Add support for Graphite 1.1 tags.
+- Add timeout option to Sensors (`sensors)` input plugin.
+- Add Burrow (`burrow`) input plugin.
+- Add option to Unbound (`unbound`) input plugin to use threads as tags.
+- Add support for TLS and username/password auth to Aerospike (`aerospike`) input plugin.
+- Add special syslog timestamp parser to grok parser that uses current year.
+- Add Syslog (`syslog`) input plugin.
+- Print the enabled aggregator and processor plugins on startup.
+- Add static `routing_key` option to `amqp` output.
+- Add passive mode exchange declaration option to AMQP Consumer (`amqp_consumer`) input plugin.
+- Add counter fields to PF (`pf`) input plugin.
+
+### Bug fixes
+
+- Write to working file outputs if any files are not writeable.
+- Add all win_perf_counters fields for a series in a single metric.
+- Report results of `dns_query` instead of `0ms` on timeout.
+- Add consul service tags to metric.
+- Fix wildcards and multi instance processes in win_perf_counters.
+- Fix crash on 32-bit Windows in `win_perf_counters`.
+- Fix `win_perf_counters` not collecting at every interval.
+- Use same flags for all BSD family ping variants.
+
+
+## v1.6.4 [2018-06-05]
+
+### Bug fixes
+
+* Fix SNMP overriding of auto-configured table fields.
+* Fix uint support in CloudWatch output.
+* Fix documentation of `instance_name` option in Varnish input.
+* Revert to previous Aerospike library version due to memory leak.
+
+## v1.6.3 [2018-05-21]
+
+### Bug fixes
+
+* Fix intermittent panic in Aerospike input plugin.
+* Fix connection leak in the Jolokia agent (`Jolokia2_agent`) input plugin.
+* Fix Jolokia agent (`Jolokia2_agent`) input plugin timeout parsing.
+* Fix error parsing Dropwizard metrics.
+* Fix Librato (`librato`) output plugin support for unsigned integer (`uint`) and Boolean (`bool`).
+* Fix WaitGroup deadlock, if URL is incorrect, in Apache input plugin.
+
+## v1.6.2 [2018-05-08]
+
+### Bug fixes
+
+* Use same timestamp for fields in system input.
+* Fix handling of uint64 in Datadog (`datadog`) output.
+* Ignore UTF8 BOM in JSON parser.
+* Fix case for slave metrics in MySQL (`mysql`) input.
+* Fix uint support in CrateDB (`cratedb`) output.
+
+
+## v1.6.1 [2018-04-23]
+
+### Bug fixes
+
+* Report mem input fields as gauges instead of counters.
+* Fix Graphite outputs unsigned integers in wrong format.
+* Report available fields if `utmp` is unreadable.
+* Fix potential `no fields` error writing to outputs.
+* Fix uptime reporting in system input when ran inside docker.
+* Fix mem input `cannot allocate memory` error on FreeBSD-based systems.
+* Fix duplicate tags when overriding an existing tag.
+* Add server argument as first argument in the Unbound (`unbound`) input plugin.
+* Fix handling of floats with multiple leading zeroes.
+* Return errors in SSL/TLS configuration of MongoDB (`mongodb`) input plugin.
+
+
+## v1.6 [2018-04-16]
+
+### Release notes
+
+- The MySQL (`mysql`) input plugin has been updated fix a number of type conversion
+  issues.  This may cause a `field type error` when inserting into InfluxDB due
+  the change of types.
+
+  To address this, we have introduced a new `metric_version` option to control
+  enabling the new format.  
+  For in depth recommendations on upgrading, see [Metric version](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/mysql#metric-version) in the MySQL input plugin documentation.
+
+  You are encouraged to migrate to the new model when possible as the old version
+  is deprecated and will be removed in a future version.
+
+- The PostgreSQL (`postgresql`) input plugin now defaults to using a persistent connection to the database.
+  In environments where TCP connections are terminated, the `max_lifetime`
+  setting should be set less than the collection `interval` to prevent errors.
+
+- The SQL Server (`sqlserver`) input plugin has a new query and data model that can be enabled
+  by setting `query_version = 2`.  
+  Migrate to the new model, if possible, since the old version is deprecated and will be removed in a future version.
+
+- The OpenLDAP (`openldap`) input plugin has a new option, `reverse_metric_names = true`, that reverses metric
+  names to improve grouping.  
+  Enable this option, when possible, as the old ordering is deprecated.
+
+- The new HTTP (`http`) input plugin, when configured with `data_format = "json"`, can perform the
+  same task as the, now deprecated, HTTP JSON (`httpjson`) input plugin.
+
+
+### New input plugins
+
+- [HTTP (`http`) input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/http/README.md) - Thanks to @grange74
+- [Ipset (`ipset`) input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/ipset/README.md) - Thanks to @sajoupa
+- [NATS Server Monitoring (`nats`) input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/nats/README.md) - Thanks to @mjs and @levex
+
+### New processor plugins
+
+- [Override (`override`) processor plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/processors/override/README.md) - Thanks to @KarstenSchnitter
+
+### New parsers
+
+- [Dropwizard input data format](https://github.com/influxdata/telegraf/blob/release-1.8/docs/DATA_FORMATS_INPUT.md#dropwizard) - Thanks to @atzoum
+
+### Features
+
+* Add health status mapping from `string` to `int` in Elasticsearch (`elasticsearch`) input plugin.
+* Add control over which stats to gather in BasicStats (`basicstats`) aggregator plugin.
+* Add `messages_delivered_get` to RabbitMQ (`rabbitmq`) input plugin.
+* Add `wired` field to mem input plugin.
+* Add support for gathering exchange metrics to the RabbitMQ (`rabbitmq`) input plugin.
+* Add support for additional metrics on Linux in Zfs (`zfs`) input plugin.
+* Add `available_entropy` field to Kernel (`kernel`) input plugin.
+* Add user privilege level setting to IPMI sensors.
+* Use persistent connection to PostgreSQL database.
+* Add support for dropwizard input data format.
+* Add container health metrics to Docker (`docker`) input plugin.
+* Add support for using globs in devices list of DiskIO (`diskio`) input plugin.
+* Allow running as console application on Windows.
+* Add listener counts and node running status to RabbitMQ (`rabbitmq`) input plugin.
+* Add NATS Server Monitoring (`nats`) input plugin.
+* Add ability to select which queues will be gathered in RabbitMQ (`rabbitmq`) input plugin.
+* Add support for setting BSD source address to the ping (`ping`) input plugin.
+* Add Ipset (`ipset`) input plugin.
+* Add TLS and HTTP basic auth to Prometheus Client (`prometheus_client`) output plugin.
+* Add new sqlserver output data model.
+* Add native Go method for finding `pid` to the Procstat (`procstat`) input plugin.
+* Add additional metrics and reverse metric names option to OpenLDAP (`openldap`) input plugin.
+* Add TLS support to the Mesos (`mesos`) input plugin.
+* Add HTTP (`http`) input plugin.
+* Add keep alive support to the TCP mode of StatsD (`statsd`) input plugin .
+* Support deadline in Ping (`ping`) input plugin.
+* Add option to disable labels in the Prometheus Client (`prometheus`) output plugin for string fields.
+* Add shard server stats to the MongoDB (`mongodb`) input plugin.
+* Add server option to Unbound (`unbound`) input plugin.
+* Convert boolean metric values to float in Datadog (`datadog`) output plugin.
+* Add Solr 3 compatibility.
+* Add sum stat to BasicStats (`basicstats`) aggregator plugin.
+* Add ability to override proxy from environment in HTTP Response (`http_response`) input plugin.
+* Add host to ping timeout log message.
+* Add override processor plugin.
+* Add `status_code` and result tags and `result_type` field to HTTP Response (`http_response`) input plugin.
+* Added config flag to skip collection of network protocol metrics.
+* Add TLS support to Kapacitor (`kapacitor`) input plugin.
+* Add HTTP basic auth support to the HTTP Listener (`http_listener`) input plugin.
+* Tags in output InfluxDB Line Protocol are now sorted.
+* InfluxDB Line Protocol parser now accepts DOS line endings.
+* An option has been added to skip database creation in the InfluxDB (`influxdb`) output plugin.
+* Add support for connecting to InfluxDB over a UNIX domain socket.
+* Add optional unsigned integer support to the influx data format.
+* Add TLS support to Zookeeper (`zookeeper`) input plugin.
+* Add filters for container state to Docker (`docker`) input plugin.
+
+### Bug fixes
+
+* Fix various MySQL data type conversions.
+* Fix metric buffer limit in internal plugin after reload.
+* Fix panic in HTTP Response (`http_response`) input plugin on invalid regex.
+* Fix socket_listener setting ReadBufferSize on TCP sockets.
+* Add tag for target URL to `phpfpm` input plugin.
+* Fix cannot unmarshal object error in Mesosphere DC/OS (`dcos`) input plugin.
+* Fix InfluxDB output not able to reconnect when server address changes.
+* Fix parsing of DOS line endings in the SMART (`smart`) input plugin.
+* Fix precision truncation when no timestamp included.
+* Fix SNMPv3 connection with Cisco ASA 5515 in SNMP (`snmp`) input plugin.
+
+
+## v1.5.3 [2018-03-14]
+
+### Bug fixes
+
+* Set path to `/` if `HOST_MOUNT_PREFIX` matches full path.
+* Remove `userinfo` from `url` tag in Prometheus input plugin.
+* Fix Ping input plugin not reporting zero durations.
+* Disable `keepalive` in MQTT output plugin to prevent deadlock.
+* Fix collation difference in SQL Server (`sqlserver`) input plugin.
+* Fix uptime metric in Passenger (`passenger`) input plugin.
+* Add output of stderr in case of error to exec log message.
+
+## v1.5.2 [2018-01-30]
+
+### Bug fixes
+
+- Ignore empty lines in Graphite plaintext.
+- Fix `index out of bounds` error in Solr input plugin.
+- Reconnect before sending Graphite metrics if disconnected.
+- Align aggregator period with internal ticker to avoid skipping metrics.
+- Fix a potential deadlock when using aggregators.
+- Limit wait time for writes in MQTT (`mqtt`) output plugin.
+- Revert change in Graphite (`graphite`) output plugin where dot(`.`) in field key was replaced by underscore (`_`).
+- Add `timeout` to Wavefront output write.
+- Exclude `master_replid` fields from Redis input.
+
+## v1.5.1 [2017-01-10]
+
+### Bug fixes
+
+- Fix name error in jolokia2_agent sample config.
+- Fix DC/OS input - login expiration time.
+- Set Content-Type charset parameter in InfluxDB (`influxdb`) output plugin and allow it to be overridden.
+- Document permissions setup for Postfix (`postfix`) input plugin.
+- Fix `deliver_get` field in RabbitMQ (`rabbitmq`) input plugin.
+- Escape environment variables during config TOML parsing.
+
+## v1.5 [2017-12-14]
+
+### New plugins
+
+#### Input plugins
+- [Bond (bond)](https://github.com/influxdata/telegraf/tree/release-1.5/plugins/inputs/bond/README.md) - Thanks to @ildarsv
+- [DC/OS (dcos)](https://github.com/influxdata/telegraf/tree/release-1.5/plugins/inputs/dcos/README.md) - Thanks to @influxdata
+- [Jolokia2 (jolokia2)](https://github.com/influxdata/telegraf/tree/release-1.5/plugins/inputs/jolokia2/README.md) - Thanks to @dylanmei
+- [NGINX Plus (nginx_plus)](https://github.com/influxdata/telegraf/tree/release-1.5/plugins/inputs/nginx_plus/README.md) - Thanks to @mplonka & @poblahblahblah
+- [OpenSMTPD (opensmtpd)](https://github.com/influxdata/telegraf/tree/release-1.5/plugins/inputs/opensmtpd/README.md) - Thanks to @aromeyer
+- [Particle.io Webhooks (particle)](https://github.com/influxdata/telegraf/tree/release-1.5/plugins/inputs/webhooks/particle/README.md) - Thanks to @davidgs
+- [PF (pf)](https://github.com/influxdata/telegraf/tree/release-1.5/plugins/inputs/pf/README.md) - Thanks to @nferch
+- [Postfix (postfix)](https://github.com/influxdata/telegraf/tree/release-1.5/plugins/inputs/postfix/README.md) - Thanks to @phemmer
+- [SMART (smart)](https://github.com/influxdata/telegraf/tree/release-1.5/plugins/inputs/smart/README.md) - Thanks to @rickard-von-essen
+- [Solr (solr)](https://github.com/influxdata/telegraf/tree/release-1.5/plugins/inputs/solr/README.md) - Thanks to @ljagiello
+- [Teamspeak (teamspeak)](https://github.com/influxdata/telegraf/tree/release-1.5/plugins/inputs/teamspeak/README.md) - Thanks to @p4ddy1
+- [Unbound (unbound)](https://github.com/influxdata/telegraf/tree/release-1.5/plugins/inputs/unbound/README.md) - Thanks to @aromeyer
+
+#### Aggregator plugins
+- [BasicStats (basicstats)](https://github.com/influxdata/telegraf/tree/release-1.5/plugins/aggregators/basicstats/README.md) - Thanks to @toni-moreno
+
+#### Output plugins
+- [CrateDB (cratedb)](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/outputs/cratedb) - Thanks to @felixge
+- [Wavefront (wavefront)](https://github.com/influxdata/telegraf/tree/release-1.5/plugins/outputs/wavefront/README.md) - Thanks to @puckpuck
+
+
+### Release notes
+
+- In the Kinesis (`kinesis`) output plugin, use of the `partition_key` and
+  `use_random_partitionkey` options has been deprecated in favor of the
+  `partition` subtable.  This allows for more flexible methods to set the
+  partition key such as by metric name or by tag.
+
+- With the release of the new improved Jolokia2 (`jolokia2`) input plugin, the legacy `jolokia`
+  plugin is deprecated and will be removed in a future release.  Users of this
+  plugin are encouraged to update to the new `jolokia2` plugin.
+
+### Features
+
+- Add support for sharding based on metric name.
+- Add Kafka output plugin `topic_suffix` option.
+- Include mount mode option in disk metrics.
+- TLS and MTLS enhancements to HTTP Listener input plugin.
+- Add polling method to logparser and tail inputs.
+- Add timeout option for Kubernetes (`kubernetes`) input plugin.
+- Add support for timing sums in statsd input plugin.
+- Add resource limit monitoring to Procstat (`procstat`) input plugin.
+- Add support for k8s service DNS discovery to Prometheus Client (`prometheus`) input plugin.
+- Add configurable metrics endpoint to (`prometheus`) output plugin.
+- Add support for NSQLookupd to `nsq_consumer`.
+- Add configurable separator for metrics and fields in OpenTSDB (`opentsdb`) output plugin.
+- Add support for the rollbar occurrence webhook event.
+- Add extra wired tiger cache metrics to `mongodb` input.
+- Collect Docker Swarm service metrics in Docker (`docker`) input plugin.
+- Add cluster health level configuration to Elasticsearch (`elasticsearch`) input plugin.
+- Add ability to limit node stats in Elasticsearch (`elasticsearch`) input plugin.
+- Add UDP IPv6 support to StatsD (`statsd`) input plugin.
+- Use labels in Prometheus Client (`prometheus`) output plugin for string fields.
+- Add support for decimal timestamps to ts-epoch modifier.
+- Add histogram and summary types and use in Prometheus (`prometheus`) plugins.
+- Gather concurrently from snmp agents.
+- Perform DNS lookup before ping and report result.
+- Add instance name option to Varnish (`varnish`) plugin.
+- Add support for SSL settings to ElasticSearch (`elasticsearch`) output plugin.
+- Add modification_time field to Filestat (`filestat`) input plugin.
+- Add systemd unit pid and cgroup matching to Procstat (`procstat`) .
+- Use MAX() instead of SUM() for latency measurements in SQL Server (`sqlserver`) input plugin.
+- Add index by week number to Elasticsearch (`elasticsearch`) output plugin.
+- Add support for tags in the index name in Elasticsearch (`elasticsearch`) output plugin.
+- Add slab to mem plugin.
+- Add support for glob patterns in net input plugin.
+- Add option to AMQP (`amqp`) output plugin to publish persistent messages.
+- Support I (idle) process state on procfs+Linux.
+
+### Bug fixes
+
+- Fix webhooks input address in use during reload.
+- Unlock Statsd when stopping to prevent deadlock.
+- Fix cloudwatch output requires unneeded permissions.
+- Fix prometheus passthrough for existing value types.
+- Always ignore autofs filesystems in disk input.
+- Fail metrics parsing on unescaped quotes.
+- Whitelist allowed char classes for graphite output.
+- Use hexadecimal ids and lowercase names in zipkin input.
+- Fix snmp-tools output parsing with Windows EOLs.
+- Add shadow-utils dependency to rpm package.
+- Use deb-systemd-invoke to restart service.
+- Fix kafka_consumer outside range of offsets error.
+- Fix separation of multiple prometheus_client outputs.
+- Don't add system input uptime_format as a counter.
+
+## v1.4.5 [2017-12-01]
+
+### Bug fixes
+
+- Fix global variable collection when using interval_slow option in MySQL input.
+- Fix error getting net connections info in netstat input.
+- Fix HOST_MOUNT_PREFIX in Docker with disk input.
+
+## v1.4.4 [2017-11-08]
+
+### Bug fixes
+- Use schema specified in mqtt_consumer input.
+- Redact Datadog API key in log output.
+- Fix error getting PIDs in netstat input.
+- Support HOST_VAR envvar to locate /var in system input.
+- Use current time if Docker container read time is zero value.
+
+## v1.4.3 [2017-10-25]
+
+### Bug fixes
+
+- Fix container name filters in Docker input.
+- Fix snmpwalk address format in leofs input.
+- Fix case sensitivity issue in SQL Server query.
+- Fix CPU input plugin stuck after suspend on Linux.
+- Fix MongoDB input panic when restarting MongoDB.
+- Preserve URL path prefix in InfluxDB output.
+- Fix TELEGRAF_OPTS expansion in systemd service unit.
+- Remove warning when JSON contains null value.
+- Fix ACL token usage in consul input plugin.
+- Fix unquoting error with Tomcat 6.
+- Fix syscall panic in diskio on some Linux systems.
+
+## v1.4.2 [2017-10-10]
+
+### Bug fixes
+
+- Fix error if int larger than 32-bit in `/proc/vmstat`.
+- Fix parsing of JSON with a UTF8 BOM in `httpjson`.
+- Allow JSON data format to contain zero metrics.
+- Fix format of connection_timeout in `mqtt_consumer`.
+- Fix case sensitivity error in SQL Server input.
+- Add support for proxy environment variables to `http_response`.
+- Add support for standard proxy env vars in outputs.
+- Fix panic in CPU input if number of CPUs changes.
+- Use chunked transfer encoding in InfluxDB output.
+
+## v1.4.1 [2017-09-26]
+
+### Bug fixes
+
+- Fix MQTT input exits if Broker is not available on startup.
+- Fix optional field value conversions in fluentd input.
+- Whitelist allowed char classes for opentsdb output.
+- Fix counter and gauge metric types.
+- Fix skipped line with empty target in iptables.
+- Fix duplicate keys in perf counters sqlserver query.
+- Fix panic in statsd p100 calculation.
+- Fix arm64 packages contain 32-bit executable.
+
+## v1.4.0 [2017-09-05]
+
+### Release Notes
+
+- The `kafka_consumer` input has been updated to support Kafka 0.9 and
+  above style consumer offset handling.  The previous version of this plugin
+  supporting Kafka 0.8 and below is available as the `kafka_consumer_legacy`
+  plugin.
+- In the `aerospike` input the `node_name` field has been changed to be a tag
+  for both the `aerospike_node` and `aerospike_namespace` measurements.
+- The default prometheus_client port has been changed to 9273.
+
+### New plugins
+
+- fail2ban
+- fluentd
+- histogram
+- minecraft
+- openldap
+- salesforce
+- tomcat
+- win_services
+- zipkin
+
+### Features
+
+- Add Kafka 0.9+ consumer support.
+- Add support for self-signed certs to InfluxDB input plugin.
+- Add TCP listener for statsd input.
+- Add Docker container environment variables as tags. Only whitelisted.
+- Add timeout option to IPMI sensor plugin.
+- Add support for an optional SSL/TLS configuration to Nginx input plugin.
+- Add timezone support for logparser timestamps.
+- Add result_type field for http_response input.
+- Add include/exclude filters for docker containers.
+- Add secure connection support to graphite output.
+- Add min/max response time on linux/darwin to ping.
+- Add HTTP Proxy support to influxdb output.
+- Add standard SSL options to mysql input.
+- Add input plugin for fail2ban.
+- Support HOST_PROC in processes and linux_sysctl_fs inputs.
+- Add Minecraft input plugin.
+- Add support for RethinkDB 1.0 handshake protocol.
+- Add optional usage_active and time_active CPU metrics.
+- Change default prometheus_client port.
+- Add fluentd input plugin.
+- Add result_type field to net_response input plugin.
+- Add read timeout to socket_listener.
+- Add input plugin for OpenLDAP.
+- Add network option to dns_query.
+- Add redis_version field to redis input.
+- Add tls options to docker input.
+- Add histogram aggregator plugin.
+- Add Zipkin input plugin.
+- Add Windows Services input plugin.
+- Add path tag to logparser containing path of logfile.
+- Add Salesforce input plugin.
+- Add option to run varnish under sudo.
+- Add weighted_io_time to diskio input.
+- Add gzip content-encoding support to influxdb output.
+- Allow using system plugin in Windows.
+- Add Tomcat input plugin.
+- HTTP headers can be added to InfluxDB output.
+
+### Bug fixes
+
+- Improve logging of errors in Cassandra input.
+- [enh] set db_version at 0 if query version fails.
+- Fixed SQL Server input to work with case sensitive server collation.
+- Systemd does not see all shutdowns as failures.
+- Reuse transports in input plugins.
+- Inputs processes fails with "no such process".
+- Fix multiple plugin loading in win_perf_counters.
+- MySQL input: log and continue on field parse error.
+- Fix timeout option in Windows ping input sample configuration.
+- Fix Kinesis output plugin in govcloud.
+- Fix Aerospike input adds all nodes to a single series.
+- Improve Prometheus Client output documentation.
+- Display error message if prometheus output fails to listen.
+- Fix elasticsearch output content type detection warning.
+- Prevent possible deadlock when using aggregators.
+- Fix combined tagdrop/tagpass filtering.
+- Fix filtering when both pass and drop match an item.
+- Only report cpu usage for online cpus in docker input.
+- Start first aggregator period at startup time.
+- Fix panic in logparser if file cannot be opened.
+- Default to localhost if zookeeper has no servers set.
+- Fix docker memory and cpu reporting in Windows.
+- Allow iptable entries with trailing text.
+- Sanitize password from couchbase metric.
+- Converge to typed value in prometheus output.
+- Skip compilcation of logparser and tail on solaris.
+- Discard logging from tail library.
+- Remove log message on ping timeout.
+- Don't retry points beyond retention policy.
+- Don't start Telegraf on install in Amazon Linux.
+- Enable hddtemp input on all platforms.
+- Escape backslash within string fields.
+- Fix parsing of SHM remotes in ntpq input
+- Don't fail parsing zpool stats if pool health is UNAVAIL on FreeBSD.
+- Fix NSQ input plugin when used with version 1.0.0-compat.
+- Added CloudWatch metric constraint validation.
+- Skip non-numerical values in graphite format.
+- Fix panic when handling string fields with escapes.
+
+## v1.3.5 [2017-07-26]
+
+### Bug fixes
+
+- Fix prometheus output cannot be reloaded.
+- Fix filestat reporting exists when cannot list directory.
+- Fix ntpq parse issue when using dns_lookup.
+- Fix panic when agent.interval = "0s".
+
+## v1.3.4 [2017-07-12]
+
+### Bug fixes
+
+- Fix handling of escape characters within fields.
+- Fix chrony plugin does not track system time offset.
+- Do not allow metrics with trailing slashes.
+- Prevent Write from being called concurrently.
+
+## v1.3.3 [2017-06-28]
+
+### Bug fixes
+
+- Allow dos line endings in tail and logparser.
+- Remove label value sanitization in prometheus output.
+- Fix bug parsing default timestamps with modified precision.
+- Fix panic in elasticsearch input if cannot determine master.
+
+## v1.3.2 [2017-06-14]
+
+### Bug fixes
+
+- Fix InfluxDB UDP metric splitting.
+- Fix mongodb/leofs urls without scheme.
+- Fix inconsistent label dimensions in prometheus output.
+
+## v1.3.1 [2017-05-31]
+
+### Bug fixes
+
+- Fixed sqlserver input to work with case-sensitive server collation.
+- Reuse transports in input plugins.
+- Process input fails with `no such process`.
+- Fix InfluxDB output database quoting.
+- Fix net input on older Linux kernels.
+- Fix panic in mongo input.
+- Fix length calculation of split metric buffer.
+
+## v1.3.0 [2017-05-09]
+
+#### Changes to the Windows ping plugin
+
+Users of the windows [ping plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/ping) will need to drop or migrate their measurements to continue using the plugin.
+The reason for this is that the windows plugin was outputting a different type than the linux plugin.
+This made it impossible to use the `ping` plugin for both windows and linux machines.
+
+#### Changes to the Ceph plugin
+
+For the [Ceph plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/ceph), the `ceph_pgmap_state` metric content has been modified to use a unique field `count`, with each state expressed as a `state` tag.
+
+Telegraf < 1.3:
+
+```
+# field_name             value
+active+clean             123
+active+clean+scrubbing   3
+```
+
+Telegraf >= 1.3:
+
+```
+# field_name    value       tag
+count           123         state=active+clean
+count           3           state=active+clean+scrubbing
+```
+
+#### Rewritten Riemann plugin
+
+The [Riemann output plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/outputs/riemann) has been rewritten
+and the [previous riemann plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/outputs/riemann_legacy) is _incompatible_ with the new one.
+The reasons for this are outlined in issue [#1878](https://github.com/influxdata/telegraf/issues/1878).
+The previous Riemann output will still be available using `outputs.riemann_legacy` if needed, but that will eventually be deprecated.
+It is highly recommended that all users migrate to the new Riemann output plugin.
+
+#### New Socket Listener and Socket Writer plugins
+
+Generic [Socket Listener](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/socket_listener) and [Socket Writer](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/outputs/socket_writer) plugins have been implemented for receiving and sending UDP, TCP, unix, & unix-datagram data.
+These plugins will replace [udp_listener](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/udp_listener) and [tcp_listener](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/tcp_listener), which are still available but will be deprecated eventually.
+
+### Features
+
+- Add SASL options for the [Kafka output plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/outputs/kafka).
+- Add SSL configuration for [HAproxy input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/haproxy).
+- Add the [Interrupts input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/interrupts).
+- Add generic [Socket Listener input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/socket_listener) and [socket writer output plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/outputs/socket_writer).
+- Extend the [HTTP Response input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/http_response) to support searching for a substring in response. Return 1 if found, else 0.
+- Add userstats to the [MySQL input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/mysql).
+- Add more InnoDB metric to the [MySQL input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/mysql).
+- For the [Ceph input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/ceph), `ceph_pgmap_state` metric now uses a single field `count`, with PG state published as `state` tag.
+- Use own client for improved through-put and less allocations in the [InfluxDB output plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/outputs/influxdb).
+- Keep -config-directory when running as Windows service.
+- Rewrite the [Riemann output plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/outputs/riemann).
+- Add support for name templates and udev tags to the [DiskIO input plugin](https://github.com/influxdata/telegraf/blob/release-1.8/plugins/inputs/diskio/README.md).
+- Add integer metrics for [Consul](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/consul) check health state.
+- Add lock option to the [IPtables input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/iptables).
+- Support [ipmi_sensor input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/ipmi_sensor) querying local ipmi sensors.
+- Increment gather_errors for all errors emitted by inputs.
+- Use the official docker SDK.
+- Add [AMQP consumer input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/amqp_consumer).
+- Add pprof tool.
+- Support DEAD(X) state in the [system input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/system).
+- Add support for [MongoDB](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/mongodb) client certificates.
+- Support adding [SNMP](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/snmp) table indexes as tags.
+- Add [Elasticsearch 5.x output plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/outputs/elasticsearch).
+- Add json timestamp units configurability.
+- Add support for Linux sysctl-fs metrics.
+- Support to include/exclude docker container labels as tags.
+- Add [DMCache input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/dmcache).
+- Add support for precision in [HTTP Listener input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/http_listener).
+- Add `message_len_max` option to the [Kafka consumer input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/kafka_consumer).
+- Add [collectd parser](https://archive.docs.influxdata.com/telegraf/v1.3/concepts/data_formats_input/#collectd).
+- Simplify plugin testing without outputs.
+- Check signature in the [GitHub webhook input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/webhooks/github).
+- Add [papertrail](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/webhooks/papertrail) support to webhooks.
+- Change [jolokia input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/jolokia) to use bulk requests.
+- Add [DiskIO input plugin](https://github.com/influxdata/telegraf/blob/release-1.8/plugins/inputs/diskio/README.md) for Darwin.
+- Add use_random_partitionkey option to the [Kinesis output plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/outputs/kinesis).
+- Add tcp keep-alive to [Socket Listener input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/socket_listener) and [Socket Writer output plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/outputs/socket_writer).
+- Add [Kapacitor input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/kapacitor).
+- Use Go (golang) 1.8.1.
+- Add documentation for the [RabbitMQ input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/rabbitmq).
+- Make the [Logparser input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/logparser) check for newly-created files.
+
+### Bug fixes
+
+- Allow `@` symbol in password for the ipmi_sensor plugin.
+- Fix arithmetic overflow error converting numeric to data type int in SQL Server input.
+- Flush jitter can inhibit metric collection.
+- Add missing fields for HAproxy input.
+- Handle null startTime for stopped pods for the Kubernetes input.
+- Fix cpu input panic when /proc/stat is empty.
+- Fix telegraf swallowing panics in --test mode.
+- Create pidfile with 644 permissions & defer file deletion.
+- Fix install/remove of telegraf on non-systemd Debian/Ubuntu systems.
+- Fix for reloading telegraf freezes prometheus output.
+- Fix when empty tag value causes error on InfluxDB output.
+- buffer_size field value is negative number from "internal" plugin.
+- Missing error handling in the MySQL plugin leads to segmentation violation.
+- Fix type conflict in windows ping plugin.
+- logparser: regexp with lookahead.
+- Telegraf can crash in LoadDirectory on 0600 files.
+- Iptables input: document better that rules without a comment are ignored.
+- Fix win_perf_counters capping values at 100.
+- Exporting Ipmi.Path to be set by config.
+- Remove warning if parse empty content.
+- Update default value for Cloudwatch rate limit.
+- create /etc/telegraf/telegraf.d directory in tarball.
+- Return error on unsupported serializer data format.
+- Fix Windows Performance Counters multi instance identifier.
+- Add write timeout to Riemann output.
+- fix timestamp parsing on prometheus plugin.
+- Fix deadlock when output cannot write.
+- Fix connection leak in postgresql.
+- Set default measurement name for snmp input.
+- Improve performance of diskio with many disks.
+- The internal input plugin uses the wrong units for `heap_objects`.
+- Fix ipmi_sensor config is shared between all plugin instances.
+- Network statistics not collected when system has alias interfaces.
+- Sysstat plugin needs LANG=C or similar locale.
+- File output closes standard streams on reload.
+- AMQP output disconnect blocks all outputs.
+- Improve documentation for redis input plugin.
+
+## v1.2.1 [2017-02-01]
+
+### Bug fixes
+
+- Fix segfault on nil metrics with InfluxDB output.
+- Fix negative number handling.
+
+### Features
+
+- Go (golang) version update 1.7.4 -> 1.7.5
+
+## v1.2 [2017-01-24]
+
+### Release Notes
+
+- The StatsD plugin will now default all "delete_" config options to "true". This
+will change te default behavior for users who were not specifying these parameters
+in their config file.
+
+- The StatsD plugin will also no longer save it's state on a service reload.
+Essentially we have reverted PR [#887](https://github.com/influxdata/telegraf/pull/887).
+The reason for this is that saving the state in a global variable is not
+thread-safe (see [#1975](https://github.com/influxdata/telegraf/issues/1975) & [#2102](https://github.com/influxdata/telegraf/issues/2102)),
+and this creates issues if users want to define multiple instances
+of the statsd plugin. Saving state on reload may be considered in the future,
+but this would need to be implemented at a higher level and applied to all
+plugins, not just statsd.
+
+### Features
+
+- Fix improper calculation of CPU percentages
+- Use RFC3339 timestamps in log output.
+- Non-default HTTP timeouts for RabbitMQ plugin.
+- "Discard" output plugin added, primarily for testing purposes.
+- The JSON parser can now parse an array of objects using the same configuration.
+- Option to use device name rather than path for reporting disk stats.
+- Telegraf "internal" plugin for collecting stats on itself.
+- Update GoLang version to 1.7.4.
+- Support a metric.Split function.
+- Elasticsearch "shield" (basic auth) support doc.
+- Fix over-querying of cloudwatch metrics
+- OpenTSDB basic auth support.
+- RabbitMQ Connection metrics.
+- HAProxy session limit metric.
+- Accept strings for StatsD sets.
+- Change StatsD default "reset" behavior.
+- Enable setting ClientID in MQTT output.
+- MongoDB input plugin: Improve state data.
+- Ping input: add standard deviation field.
+- Add GC pause metric to InfluxDB input plugin.
+- Added response_timeout property to prometheus input plugin.
+- Pulling github.com/lxn/win's pdh wrapper into Telegraf.
+- Support negative statsd counters.
+- Elasticsearch cluster stats support.
+- Change Amazon Kinesis output plugin to use the built-in serializer plugins.
+- Hide username/password from elasticsearch error log messages.
+- Configurable HTTP timeouts in Jolokia plugin.
+- Allow changing jolokia attribute delimiter.
+
+### Bug fixes
+
+- Fix the Value data format not trimming null characters from input.
+- Fix windows `.net` plugin.
+- Cache & expire metrics for delivery to prometheus
+- Fix potential panic in aggregator plugin metric maker.
+- Add optional ability to define PID as a tag.
+- Fix win_perf_counters not gathering non-English counters.
+- Fix panic when file stat info cannot be collected due to permissions or other issue(s).
+- Graylog output should set short_message field.
+- Hddtemp always put the value in the field temperature.
+- Properly collect nested jolokia struct data.
+- Fix puppetagent inputs plugin to support string for config variable.
+- Fix docker input plugin tags when registry has port.
+- Fix tail input when reading from a pipe.
+- MongoDB plugin always shows 0 replication lag.
+- Consul plugin: add check_id as a tag in metrics to avoid overwrites.
+- Partial fix: logparser CLF pattern with IPv6 addresses.
+- Fix thread-safety when using multiple instances of the statsd input plugin.
+- Docker input: interface conversion panic fix.
+- SNMP: ensure proper context is present on error messages.
+- OpenTSDB: add tcp:// prefix if no scheme provided.
+- Influx parser: parse line-protocol without newlines.
+- InfluxDB output: fix field type conflict blocking output buffer.
+
+## v1.1.2 [2016-12-12]
+
+### Bug fixes
+
+- Make snmptranslate not required when using numeric OID.
+- Add a global snmp translation cache.
+
+## v1.1.1 [2016-11-14]
+
+### Bug fixes
+
+- Fix issue parsing toml durations with single quotes.
+
+## v1.1.0 [2016-11-07]
+
+### Release Notes
+
+- Telegraf now supports two new types of plugins: processors & aggregators.
+
+- On systemd Telegraf will no longer redirect it's stdout to /var/log/telegraf/telegraf.log.
+On most systems, the logs will be directed to the systemd journal and can be
+accessed by `journalctl -u telegraf.service`. Consult the systemd journal
+documentation for configuring journald. There is also a [`logfile` config option](https://github.com/influxdata/telegraf/blob/release-1.8/etc/telegraf.conf#L70)
+available in 1.1, which will allow users to easily configure telegraf to
+continue sending logs to /var/log/telegraf/telegraf.log.
+
+### Features
+
+- Processor & Aggregator plugin support.
+- Adding the tags in the graylog output plugin.
+- Telegraf systemd service, log to journal.
+- Allow numeric and non-string values for tag_keys.
+- Adding Gauge and Counter metric types.
+- Remove carraige returns from exec plugin output on Windows
+- Elasticsearch input: configurable timeout.
+- Massage metric names in Instrumental output plugin
+- Apache Mesos improvements.
+- Add Ceph Cluster Performance Statistics
+- Ability to configure response_timeout in httpjson input.
+- Add additional redis metrics.
+- Added capability to send metrics through HTTP API for OpenTSDB.
+- iptables input plugin.
+- Add filestack webhook plugin.
+- Add server hostname for each Docker measurements.
+- Add NATS output plugin.
+- HTTP service listener input plugin.
+- Add database blacklist option for Postgresql
+- Add Docker container state metrics to Docker input plugin output
+- Add support to SNMP for IP & MAC address conversion.
+- Add support to SNMP for OID index suffixes.
+- Change default arguments for SNMP plugin.
+- Apach Mesos input plugin: very high-cardinality mesos-task metrics removed.
+- Logging overhaul to centralize the logger & log levels, & provide a logfile config option.
+- HAProxy plugin socket glob matching.
+- Add Kubernetes plugin for retrieving pod metrics.
+
+### Bug fixes
+
+- Fix NATS plug-ins reconnection logic.
+- Set required default values in udp_listener & tcp_listener.
+- Fix toml unmarshal panic in Duration objects.
+- Fix handling of non-string values for JSON keys listed in tag_keys.
+- Fix mongodb input panic on version 2.2.
+- Fix statsd scientific notation parsing.
+- Sensors plugin strconv.ParseFloat: parsing "": invalid syntax.
+- Fix prometheus_client reload panic.
+- Fix Apache Kafka consumer panic when nil error is returned down errs channel.
+- Speed up statsd parsing.
+- Fix powerdns integer parse error handling.
+- Fix varnish plugin defaults not being used.
+- Fix Windows glob paths.
+- Fix issue loading config directory on Windows.
+- Windows remote management interactive service fix.
+- SQLServer, fix issue when case sensitive collation is activated.
+- Fix huge allocations in http_listener when dealing with huge payloads.
+- Fix translating SNMP fields not in MIB.
+- Fix SNMP emitting empty fields.
+- SQL Server waitstats truncation bug.
+- Fix logparser common log format: numbers in ident.
+- Fix JSON Serialization in OpenTSDB output.
+- Fix Graphite template ordering, use most specific.
+- Fix snmp table field initialization for non-automatic table.
+- cgroups path being parsed as metric.
+- Fix phpfpm fcgi client panic when URL does not exist.
+- Fix config file parse error logging.
+- Delete nil fields in the metric maker.
+- Fix MySQL special characters in DSN parsing.
+- Ping input odd timeout behavior.
+- Switch to github.com/kballard/go-shellquote.
+
+## v1.0.1 [2016-09-26]
+
+### Bug fixes
+
+- Prometheus output: Fix bug with multi-batch writes.
+- Fix unmarshal of influxdb metrics with null tags.
+- Add configurable timeout to influxdb input plugin.
+- Fix statsd no default value panic.
+
+## v1.0 [2016-09-08]
+
+### Release Notes
+
+**Breaking Change** The SNMP plugin is being deprecated in it's current form.
+There is a [new SNMP plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/snmp)
+which fixes many of the issues and confusions
+of its predecessor. For users wanting to continue to use the deprecated SNMP
+plugin, you will need to change your config file from `[[inputs.snmp]]` to
+`[[inputs.snmp_legacy]]`. The configuration of the new SNMP plugin is _not_
+backwards-compatible.
+
+**Breaking Change**: Aerospike main server node measurements have been renamed
+aerospike_node. Aerospike namespace measurements have been renamed to
+aerospike_namespace. They will also now be tagged with the node_name
+that they correspond to. This has been done to differentiate measurements
+that pertain to node vs. namespace statistics.
+
+**Breaking Change**: users of github_webhooks must change to the new
+`[[inputs.webhooks]]` plugin.
+
+This means that the default github_webhooks config:
+
+```
+# A Github Webhook Event collector
+[[inputs.github_webhooks]]
+  ## Address and port to host Webhook listener on
+  service_address = ":1618"
+```
+
+should now look like:
+
+```
+# A Webhooks Event collector
+[[inputs.webhooks]]
+  ## Address and port to host Webhook listener on
+  service_address = ":1618"
+
+  [inputs.webhooks.github]
+    path = "/"
+```
+
+- Telegraf now supports being installed as an official windows service,
+which can be installed via
+`> C:\Program Files\Telegraf\telegraf.exe --service install`
+
+- `flush_jitter` behavior has been changed. The random jitter will now be
+evaluated at every flush interval, rather than once at startup. This makes it
+consistent with the behavior of `collection_jitter`.
+
+- PostgresSQL plugins now handle oid and name typed columns seamlessly, previously they were ignored/skipped.
+
+### Features
+
+- postgresql_extensible now handles name and oid types correctly.
+- Separate container_version from container_image tag.
+- Support setting per-device and total metrics for Docker network and blockio.
+- MongoDB input plugin: adding per DB stats from db.stats()
+- Add tls support for certs to RabbitMQ input plugin.
+- Webhooks input plugin.
+- Rollbar webhook plugin.
+- Mandrill webhook plugin.
+- docker-machine/boot2docker no longer required for unit tests.
+- cgroup input plugin.
+- Add input plugin for consuming metrics from NSQD.
+- Add ability to read Redis from a socket.
+- **Breaking Change** - Redis `role` tag renamed to `replication_role` to avoid global_tags override.
+- Fetching Galera status metrics in MySQL
+- Aerospike plugin refactored to use official client library.
+- Add measurement name arg to logparser plugin.
+- logparser: change resp_code from a field to a tag.
+- Implement support for fetching hddtemp data
+- statsd: do not log every dropped metric.
+- Add precision rounding to all metrics on collection.
+- Add support for Tengine.
+- Logparser input plugin for parsing grok-style log patterns.
+- ElasticSearch: now supports connecting to ElasticSearch via SSL.
+- Add graylog input pluging.
+- Consul input plugin.
+- conntrack input plugin.
+- vmstat input plugin.
+- Standardized AWS credentials evaluation & wildcard CloudWatch dimensions.
+- Add SSL config options to http_response plugin.
+- Graphite parser: add ability to specify multiple tag keys, for consistency with influxdb parser.
+- Make DNS lookups for chrony configurable.
+- Allow wildcard filtering of varnish stats.
+- Support for glob patterns in exec plugin commands configuration.
+- RabbitMQ input: made url parameter optional by using DefaultURL (`http://localhost:15672`) if not specified.
+- Limit AWS GetMetricStatistics requests to 10 per second.
+- RabbitMQ/Apache/InfluxDB inputs: made url(s) parameter optional by using reasonable input defaults if not specified.
+- Refactor of flush_jitter argument.
+- Add inactive & active memory to mem plugin.
+- Official Windows service.
+- Forking sensors command to remove C package dependency.
+- Add a new SNMP plugin.
+
+### Bug fixes
+
+- Fix `make windows` build target.
+- Fix error race conditions and partial failures.
+- nstat: fix inaccurate config panic.
+- jolokia: fix handling multiple multi-dimensional attributes.
+- Fix prometheus character sanitizing. Sanitize more win_perf_counters characters.
+- Add diskio io_time to FreeBSD & report timing metrics as ms (as linux does).
+- Fix covering Amazon Linux for post remove flow.
+- procstat missing fields: read/write bytes & count.
+- diskio input plugin: set 'skip_serial_number = true' by default to avoid high cardinality.
+- nil metrics panic fix.
+- Fix datarace in apache input plugin.
+- Add `read_repairs` statistics to riak plugin.
+- Fix memory/connection leak in Prometheus input plugin.
+- Trim BOM from config file for Windows support.
+- Prometheus client output panic on service reload.
+- Prometheus parser, protobuf format header fix.
+- Prometheus output, metric refresh and caching fixes.
+- Panic fix for multiple graphite outputs under very high load.
+- Instrumental output has better reconnect behavior.
+- Remove PID from procstat plugin to fix cardinality issues.
+- Cassandra input: version 2.x "column family" fix.
+- Shared WaitGroup in Exec plugin.
+- logparser: honor modifiers in "pattern" config.
+- logparser: error and exit on file permissions/missing errors.
+- Make the user able to specify full path for HAproxy stats.
+- Fix Redis url, an extra "tcp://" was added.
+- Fix exec plugin panic when using single binary.
+- Fixed incorrect prometheus metrics source selection.
+- Set default Zookeeper chroot to empty string.
+- Fix overall ping timeout to be calculated based on per-ping timeout.
+- Change "default" retention policy to "".
+- Graphite output mangling '%' character.
+- Prometheus input plugin now supports x509 certs authentication.
+- Fix systemd service.
+- Fix influxdb n_shards counter.
+- Fix potential kernel plugin integer parse error.
+- Fix potential influxdb input type assertion panic.
+- Still send processes metrics if a process exited during metric collection.
+- disk plugin panic when usage grab fails.
+- Removed leaked "database" tag on redis metrics.
+- Processes plugin: fix potential error with /proc/net/stat directory.
+- Fix rare RHEL 5.2 panic in gopsutil diskio gathering function.
+- Remove IF NOT EXISTS from influxdb output database creation.
+- Fix quoting with text values in postgresql_extensible plugin.
+- Fix win_perf_counter "index out of range" panic.
+- Fix ntpq panic when field is missing.
+- Sanitize graphite output field names.
+- Fix MySQL plugin not sending 0 value fields.
diff --git a/content/telegraf/v1.9/about_the_project/release-notes-changelog.md b/content/telegraf/v1.9/about_the_project/release-notes-changelog.md
index 26b649220..ad2ff1dc4 100644
--- a/content/telegraf/v1.9/about_the_project/release-notes-changelog.md
+++ b/content/telegraf/v1.9/about_the_project/release-notes-changelog.md
@@ -260,14 +260,14 @@ menu:
 
 ### New input data formats (parsers)
 
-- [csv](/telegraf/v1.8/data_formats/input/csv) - Contributed by @maxunt
-- [grok](/telegraf/v1.8/data_formats/input/grok/) - Contributed by @maxunt
-- [logfmt](/telegraf/v1.8/data_formats/input/logfmt/) - Contributed by @Ayrdrie & @maxunt
-- [wavefront](/telegraf/v1.8/data_formats/input/wavefront/) - Contributed by @puckpuck
+- [csv](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/csv) - Contributed by @maxunt
+- [grok](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/grok/) - Contributed by @maxunt
+- [logfmt](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/logfmt/) - Contributed by @Ayrdrie & @maxunt
+- [wavefront](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/input/wavefront/) - Contributed by @puckpuck
 
 ### New output data formats (serializers)
 
-- [splunkmetric](/telegraf/v1.8/data_formats/output/splunkmetric/) - Contributed by @ronnocol
+- [splunkmetric](https://archive.docs.influxdata.com/telegraf/v1.8/data_formats/output/splunkmetric/) - Contributed by @ronnocol
 
 ### Features
 
@@ -1048,7 +1048,7 @@ These plugins will replace [udp_listener](https://github.com/influxdata/telegraf
 - Add [DMCache input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/dmcache).
 - Add support for precision in [HTTP Listener input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/http_listener).
 - Add `message_len_max` option to the [Kafka consumer input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/kafka_consumer).
-- Add [collectd parser](/telegraf/v1.3/concepts/data_formats_input/#collectd).
+- Add [collectd parser](https://archive.docs.influxdata.com/telegraf/v1.3/concepts/data_formats_input/#collectd).
 - Simplify plugin testing without outputs.
 - Check signature in the [GitHub webhook input plugin](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/webhooks/github).
 - Add [papertrail](https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/webhooks/papertrail) support to webhooks.
diff --git a/content/telegraf/v1.9/data_formats/output/graphite.md b/content/telegraf/v1.9/data_formats/output/graphite.md
index df6fe4adb..7ccd34622 100644
--- a/content/telegraf/v1.9/data_formats/output/graphite.md
+++ b/content/telegraf/v1.9/data_formats/output/graphite.md
@@ -10,7 +10,7 @@ menu:
 
 The Graphite data format is serialized from Telegraf metrics using either the
 template pattern or tag support method.  You can select between the two
-methods using the [`graphite_tag_support`](#graphite-tag-support) option.  When set, the tag support method is used,
+methods using the [`graphite_tag_support`](#graphite_tag_support) option.  When set, the tag support method is used,
 otherwise the [template pattern][templates]) option is used.
 
 ## Configuration
diff --git a/content/telegraf/v1.9/plugins/inputs.md b/content/telegraf/v1.9/plugins/inputs.md
index 8067d0904..7510f054f 100644
--- a/content/telegraf/v1.9/plugins/inputs.md
+++ b/content/telegraf/v1.9/plugins/inputs.md
@@ -1000,7 +1000,7 @@ The [HTTP Listener input plugin](https://github.com/influxdata/telegraf/blob/rel
 Line Protocol input data format](/telegraf/v1.9/data_formats/input/influx) ONLY (other [Telegraf input data formats](/telegraf/v1.9/data_formats/input/) are not supported).
 This plugin allows Telegraf to serve as a proxy or router for the `/write` endpoint of the InfluxDB HTTP API.
 
-> DEPRECATED as of version 1.9. Use either [HTTP Listener v2](#http-listener-v2) or the [InfluxDB Listener](#influxdb-v1-x)
+> DEPRECATED as of version 1.9. Use either [HTTP Listener v2](#http-listener-v2) or the [InfluxDB Listener](#influxdb-v1x)
 
 
 ### Jolokia
diff --git a/data/influxd_flags.yml b/data/influxd_flags.yml
index a8c52398a..4b634eb5e 100644
--- a/data/influxd_flags.yml
+++ b/data/influxd_flags.yml
@@ -3,6 +3,8 @@
 #
 # - flag: "--flag-name"
 #   added: InfluxDB minor version the flag was added
+#   deprecated: InfluxDB minor version the flag was deprecated
+#   removed: InfluxDB minor version the flag was removed
 #   nolink: Do not create a link to the config options doc for this flag
 # 
 
@@ -24,6 +26,9 @@
 - flag: "--flux-log-enabled"
   added: 2.0
 
+- flag: "--hardening-enabled"
+  added: 2.2
+
 - flag: "-h, --help"
   added: 2.0
   nolink: true
@@ -60,9 +65,13 @@
 
 - flag: "--nats-max-payload-bytes"
   added: 2.0
+  deprecated: 2.2
+  # removed: 2.2
 
 - flag: "--nats-port"
   added: 2.0
+  deprecated: 2.2
+  # removed: 2.2
 
 - flag: "--no-tasks"
   added: 2.0
diff --git a/data/influxdb_urls.yml b/data/influxdb_urls.yml
index c08a7e4b6..e4ca27c95 100644
--- a/data/influxdb_urls.yml
+++ b/data/influxdb_urls.yml
@@ -17,6 +17,11 @@ cloud:
         - name: US West (Oregon)
           location: Oregon, USA
           url: https://us-west-2-1.aws.cloud2.influxdata.com
+          clusters:
+            - name: us-west-2-1
+              url: https://us-west-2-1.aws.cloud2.influxdata.com
+            - name: us-west-2-2
+              url: https://us-west-2-2.aws.cloud2.influxdata.com
         - name: US East (Virginia)
           location: Virginia, USA
           url: https://us-east-1-1.aws.cloud2.influxdata.com
diff --git a/data/products.yml b/data/products.yml
index 981dedcd0..696698f72 100644
--- a/data/products.yml
+++ b/data/products.yml
@@ -3,10 +3,11 @@ influxdb:
   altname: InfluxDB OSS
   namespace: influxdb
   list_order: 2
-  versions: [v1.3, v1.4, v1.5, v1.6, v1.7, v1.8, v2.0, v2.1]
-  latest: v2.1
-  latest_override: v2.1
+  versions: [v1.3, v1.4, v1.5, v1.6, v1.7, v1.8, v2.0, v2.1, v2.2]
+  latest: v2.2
+  latest_override: v2.2
   latest_patches:
+    "2.2": 0
     "2.1": 1
     "2.0": 9
     "1.8": 10
@@ -16,6 +17,7 @@ influxdb:
     "1.4": 3
     "1.3": 9
   latest_cli:
+    "2.2": 2.3.0
     "2.1": 2.2.0
     "2.0": 2.2.0
 
@@ -32,10 +34,11 @@ telegraf:
   name: Telegraf
   namespace: telegraf
   list_order: 4
-  versions: [v1.9, v1.10, v1.11, v1.12, v1.13, v1.14, v1.15, v1.16, v1.17, v1.18, v1.19, v1.20, v1.21]
-  latest: v1.21
+  versions: [v1.9, v1.10, v1.11, v1.12, v1.13, v1.14, v1.15, v1.16, v1.17, v1.18, v1.19, v1.20, v1.21, v1.22]
+  latest: v1.22
   latest_patches:
-    "1.21": 3
+    "1.22": 2
+    "1.21": 4
     "1.20": 4
     "1.19": 3
     "1.18": 3
@@ -76,7 +79,7 @@ enterprise_influxdb:
   versions: [v1.5, v1.6, v1.7, v1.8, v1.9]
   latest: v1.9
   latest_patches:
-    "1.9": 5
+    "1.9": 6
     "1.8": 10
     "1.7": 10
     "1.6": 6
diff --git a/data/query_examples.yml b/data/query_examples.yml
index b4c124365..44f88307d 100644
--- a/data/query_examples.yml
+++ b/data/query_examples.yml
@@ -3,7 +3,7 @@ aggregate_window:
     code: |
       ```js
       data
-        |> aggregateWindow(every: 20m, fn: mean)
+          |> aggregateWindow(every: 20m, fn: mean)
       ```
     input: |
       | _time                | _value |
@@ -28,7 +28,7 @@ cumulative_sum:
     code: |
       ```js
       data
-        |> cumulativeSum()
+          |> cumulativeSum()
       ```
     input: |
       | _time                | _value |
@@ -50,7 +50,7 @@ fill_null:
     code: |
       ```js
       data
-        |> fill(usePrevious: true)
+          |> fill(usePrevious: true)
       ```
     input: |
       | _time                | _value |
@@ -72,7 +72,7 @@ fill_null:
     code: |
       ```js
       data
-        |> fill(value: 0.0)
+          |> fill(value: 0.0)
       ```
     input: |
       | _time                | _value |
@@ -96,7 +96,7 @@ first_last:
     code: |
       ```js
       data
-        |> first()
+          |> first()
       ```
     input: |
       | _time                | _value |
@@ -113,7 +113,7 @@ first_last:
     code: |
       ```js
       data
-        |> last()
+          |> last()
       ```
     input: |
       | _time                | _value |
@@ -132,7 +132,7 @@ group:
     code: |
       ```js
       data
-        |> group(columns: ["host"], mode: "by")
+          |> group(columns: ["host"], mode: "by")
       ```
     input: |
       | _time                | host  | _value |
@@ -157,12 +157,12 @@ histogram:
     code: |
       ```js
       data
-        |> histogram(
-          column: "_value",
-          upperBoundColumn: "le",
-          countColumn: "_value",
-          bins: [100.0, 200.0, 300.0, 400.0],
-        )
+          |> histogram(
+              column: "_value",
+              upperBoundColumn: "le",
+              countColumn: "_value",
+              bins: [100.0, 200.0, 300.0, 400.0],
+          )
       ```
     input: |
       | _time                | _value |
@@ -187,7 +187,7 @@ increase:
     code: |
       ```js
       data
-        |> increase()
+          |> increase()
       ```
     input: |
       | _time                | _value |
@@ -214,7 +214,7 @@ interpolate_linear:
       import "interpolate"
 
       data
-        |> interpolate.linear(every: 1d)
+          |> interpolate.linear(every: 1d)
       ```
     input: |
       | _time                | _value |
@@ -242,12 +242,12 @@ join:
     code: |
       ```js
       t1 = from(bucket: "example-bucket")
-        |> range(start: 2020-01-01T00:00:00Z)
-        |> filter(fn: (r) => r.m == "foo")
+          |> range(start: 2020-01-01T00:00:00Z)
+          |> filter(fn: (r) => r.m == "foo")
 
       t2 = from(bucket: "example-bucket")
-        |> range(start: 2020-01-01T00:00:00Z)
-        |> filter(fn: (r) => r.m == "bar")
+          |> range(start: 2020-01-01T00:00:00Z)
+          |> filter(fn: (r) => r.m == "bar")
 
       join(tables: {t1: t1, t2: t2}, on: ["_time"])
       ```
@@ -280,7 +280,7 @@ map_math:
     code: |
       ```js
       data
-        |> map(fn: (r) => ({ r with _value: r._value * r._value }))
+          |> map(fn: (r) => ({ r with _value: r._value * r._value }))
       ```
     input: |
       | _time                | _value |
@@ -302,7 +302,7 @@ median:
     code: |
       ```js
       data
-        |> median()
+          |> median()
       ```
     input: |
       | _time                | _value |
@@ -321,7 +321,7 @@ moving_average:
     code: |
       ```js
       data
-        |> movingAverage(n: 5)
+          |> movingAverage(n: 5)
       ```
     input: |
       | _time                | _value |
@@ -343,7 +343,7 @@ moving_average:
     code: |
       ```js
       data
-        |> timedMovingAverage(every: 2m, period: 4m)
+          |> timedMovingAverage(every: 2m, period: 4m)
       ```
     input: |
       | _time                | _value |
@@ -368,11 +368,13 @@ percentages:
       ```js
       data
         |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
-        |> map(fn: (r) => ({
-          _time: r._time,
-          _field: "used_percent",
-          _value: float(v: r.used) / float(v: r.total) * 100.0
-        }))
+        |> map(
+            fn: (r) => ({
+                _time: r._time,
+                _field: "used_percent",
+                _value: float(v: r.used) / float(v: r.total) * 100.0,
+            }),
+        )
       ```
     input: |
       | _time                | _field  | _value |
@@ -399,7 +401,7 @@ quantile:
     code: |
       ```js
       data
-        |> quantile(q: 0.99, method: "estimate_tdigest")
+          |> quantile(q: 0.99, method: "estimate_tdigest")
       ```
     input: |
       | _time                | _value |
@@ -418,7 +420,7 @@ rate_of_change:
     code: |
       ```js
       data
-        |> derivative(unit: 1m, nonNegative: true)
+          |> derivative(unit: 1m, nonNegative: true)
       ```
     input: |
       | _time                | _value |
@@ -445,7 +447,7 @@ rate_of_change:
       import "experimental/aggregate"
 
       data
-        |> aggregate.rate(every: 20m, unit: 1m)
+          |> aggregate.rate(every: 20m, unit: 1m)
       ```
     input: |
       | _time                | _value |
@@ -470,7 +472,7 @@ regular_expressions:
     code: |
       ```js
       data
-        |> filter(fn: (r) => r.tag =~ /^foo[1-3]/)
+          |> filter(fn: (r) => r.tag =~ /^foo[1-3]/)
       ```
     input: |
       | _time                | tag  | _value |
@@ -493,8 +495,8 @@ sort_limit:
     code: |
       ```js
       data
-        |> sort(columns: ["host", "_value"])
-        |> limit(n: 4)
+          |> sort(columns: ["host", "_value"])
+          |> limit(n: 4)
       ```
     input: |
       | _time                | host | _value |
diff --git a/data/telegraf_plugins.yml b/data/telegraf_plugins.yml
index b9356219a..dce1a8e43 100644
--- a/data/telegraf_plugins.yml
+++ b/data/telegraf_plugins.yml
@@ -157,6 +157,15 @@ input:
     introduced: 1.12.0
     tags: [linux, macos, windows, systems]
 
+  - name: APT
+    id: telegraf-apt
+    description: |
+      The APT input plugin checks Debian for package updates.
+    link: https://github.com/x70b1/telegraf-apt/blob/master/README.md
+    introduced: 1.21.4
+    tags: [debian, ubuntu]
+    external: true
+
   - name: Arista LANZ Consumer
     id: lanz
     description: |
@@ -268,7 +277,7 @@ input:
     description: |
       > The `inputs.cisco_telementry_gnmi` plugin was renamed to `inputs.gmni`
       in **Telegraf 1.15.0** to better reflect its general support for gNMI devices.
-      See the [gNMI plugin](#gnmi).
+      See the [gNMI plugin](#input-cisco_telemetry_gnmi).
 
       Cisco GNMI Telemetry input plugin consumes telemetry data similar to the GNMI specification.
       This GRPC-based protocol can utilize TLS for authentication and encryption.
@@ -608,6 +617,27 @@ input:
     introduced: 0.1.5
     tags: [linux, macos, windows, networking, web]
 
+  - name: Hashicorp Consul Agent
+    id: consul_agent
+    description: |
+      The Hashicorp Consul agent plugin grab metrics from every Nomad agent of the cluster.
+    introduced: 1.22.0
+    tags: [applications]
+
+  - name: Hashicorp Nomad
+    id: nomad
+    description: |
+      The Nomad plugin grabs metrics from every Nomad agent of the cluster.
+    introduced: 1.22.0
+    tags: [applications]
+
+  - name: Hashicorp Vault
+    id: nomad
+    description: |
+      The Vault plugin grabs metrics from every Nomad agent of the cluster.
+    introduced: 1.22.0
+    tags: [security]
+
   - name: Hddtemp
     id: hddtemp
     description: |
@@ -665,6 +695,13 @@ input:
     introduced: 0.12.1
     tags: [linux, macos, windows, servers, web]
 
+  - name: Huge Pages
+    id: hugepages
+    description: |
+      The Huge Pages input plugin gathers Huge pages measurements. Transparent Huge Pages (THP) is a Linux memory management system that reduces the overhead of Translation Lookaside Buffer (TLB) lookups on machines with large amounts of memory by using larger memory pages.
+    introduced: 1.22.0
+    tags: [linux]
+
   - name: IBM DB2
     id: db2
     description: |
@@ -911,6 +948,15 @@ input:
     introduced: 1.8.0
     tags: [linux, macos, windows, applications]
 
+  - name: Knot
+    id: knot
+    description: |
+      The Knot input plugin collect stats from [Knot DNS](https://knot.readthedocs.io/en/master/operation.html#statistics).
+    link: https://github.com/x70b1/telegraf-knot/blob/master/README.md
+    introduced: 1.21.4
+    tags: [server]
+    external: true
+
   - name: KNX
     id: knx_listener
     description: |
@@ -1081,6 +1127,13 @@ input:
     introduced: 1.4.0
     tags: [linux, macos, windows, gaming]
 
+  - name: Mock
+    id: mock
+    description: |
+      The mock input plugin generates random data based on a selection of different algorithms.
+    introduced: 1.22.0
+    tags: [build-deploy]
+
   - name: Modbus
     id: modbus
     description: |
@@ -1148,7 +1201,7 @@ input:
     id: nats
     description: |
       The NATS Server Monitoring input plugin gathers metrics when using the
-      [NATS Server monitoring server](https://www.nats.io/documentation/server/gnatsd-monitoring/).
+      [NATS Server monitoring server](https://docs.nats.io/running-a-nats-service/introduction).
     introduced: 1.6.0
     tags: [linux, macos, windows, messaging]
 
@@ -1167,7 +1220,7 @@ input:
     id: net
     description: |
       The Net input plugin gathers metrics about network interface usage (Linux only).
-    link: https://github.com/influxdata/telegraf/blob/master/plugins/inputs/net/NET_README.md
+    link: https://github.com/influxdata/telegraf/blob/master/plugins/inputs/net/README.md
     introduced: 0.1.1
     tags: [linux, macos, networking]
 
@@ -1176,7 +1229,7 @@ input:
     description: |
       The Netstat input plugin gathers TCP metrics such as established, time-wait
       and sockets counts by using `lsof`.
-    link: https://github.com/influxdata/telegraf/blob/master/plugins/inputs/net/NETSTAT_README.md
+    link: https://github.com/influxdata/telegraf/blob/master/plugins/inputs/netstat/README.md
     introduced: 0.2.0
     tags: [linux, macos, windows, networking, systems]
 
@@ -1509,6 +1562,14 @@ input:
     introduced: 1.16.0
     tags: [linux, macos, windows]
 
+  - name: PSI
+    id: psi
+    description: |
+      The PSI input plugins push pressure stall information (PSI) from the Linux Kernel to InfluxDB.
+    introduced: 1.22.1
+    tags: [linux]
+    external: true
+
   - name: Puppet Agent
     id: puppetagent
     description: |
@@ -1684,6 +1745,13 @@ input:
     introduced: 1.3.0
     tags: [linux, macos, windows, networking]
 
+  - name: Socketstat
+    id: socketstat
+    description: |
+      The Socketstat input plugin gathers indicators from established socket connections.
+    introduced: 1.22.0
+    tags: [linux]
+
   - name: SQL
     id: sql
     description: |
@@ -1975,6 +2043,13 @@ input:
     tags: [external]
     external: true
 
+  - name: XtremIO
+    id: xtremio
+    description: |
+      The Xtremio plugin gathers metrics from Dell EMC XtremIO Storage Array.
+    introduced: 1.22.0
+    tags: [networking]
+
   - name: YouTube
     id: youtube
     description: |
@@ -2135,7 +2210,7 @@ output:
     tags: [linux, macos, windows, systems]
 
   - name: Execd
-    id: exec
+    id: execd
     description: |
         The Execd output plugin runs an external program as a daemon.
     introduced: 1.15.0
@@ -2180,9 +2255,9 @@ output:
   - name: GroundWork
     id: groundwork
     description: |
-      The  Graylog output plugin writes to a [GroundWork Monitor](https://www.gwos.com/product/groundwork-monitor/) instance.
+      The  GroundWork output plugin writes to a [GroundWork Monitor](https://www.gwos.com/product/groundwork-monitor/) instance.
     introduced: 1.21.0
-    tags: [linux, macos, windows, logging]
+    tags: [linux, macos, windows, applications, messaging]
 
   - name: HTTP
     id: http
@@ -2647,6 +2722,13 @@ processor:
     introduced: 1.15.0
     tags: [linux, macos, windows]
 
+  - name: Noise
+    id: noise
+    description: |
+      The noise processor plugin  is used to add noise to numerical field values. This helps users to add some noise to sensitive data by anonymizing it and further prevent linkage attacks.
+    introduced: 1.22.0
+    tags: [security]
+
   - name: Override
     id: override
     description: |
diff --git a/deploy/edge.js b/deploy/edge.js
index ce92b5f48..b5fd49941 100644
--- a/deploy/edge.js
+++ b/deploy/edge.js
@@ -3,9 +3,9 @@
 const path = require('path');
 
 const latestVersions = {
-  'influxdb': 'v2.1',
-  'influxdbv2': 'v2.1',
-  'telegraf': 'v1.21',
+  'influxdb': 'v2.2',
+  'influxdbv2': 'v2.2',
+  'telegraf': 'v1.22',
   'chronograf': 'v1.9',
   'kapacitor': 'v1.6',
   'enterprise': 'v1.9',
diff --git a/layouts/index.html b/layouts/index.html
index 64ac687d9..a7325366e 100644
--- a/layouts/index.html
+++ b/layouts/index.html
@@ -11,21 +11,6 @@
 
 <div class="home">
 
-  <div class="section hero">
-    {{ partial "svgs/homepage-hero.svg" }}
-    <div class="half">
-      <h2>InfluxDB Cloud & <br />InfluxDB OSS 2.x</h2>
-      <p>
-        The most powerful time series database.
-        Designed to handle high write and query loads.
-        Run in the cloud with <strong>InfluxDB Cloud</strong> or on your own hardware with <strong>InfluxDB OSS {{ replaceRE "v" "" $influxdbVersionV2 }}</strong>.
-      </p>
-      <div class="actions">
-        <a class="btn" href="/influxdb/cloud/">InfluxDB Cloud Docs</a>
-        <a class="btn" href="/influxdb/{{ $influxdbVersionV2 }}/">InfluxDB OSS {{ replaceRE "v" "" $influxdbVersionV2 }} Docs</a>
-      </div>
-    </div>
-  </div>
   <div class="section search">
     <div class="sidebar--search">
       <input  class="sidebar--search-field"
@@ -41,104 +26,132 @@
     </div>
   </div>
 
-  <div id="flux" class="section row">
-    <div class="group-wrapper">
-      <div class="card">
-        <div class="card-content">
-          <h2><a href="/flux/{{ $fluxVersion }}/">Flux <span class="version">{{ $fluxVersion }}</span></a></h2>
-          <p>The functional query and data scripting language.</p>
+  <div id="influxdb" class="section group-wrapper">
+    <div class="actions">
+      <div>
+        <h2>Get started with <span class="magenta">InfluxDB</span></h2>
+        <p class="subhead">The time series platform</p>
+
+        <div id="influxdb-btn" class="exp-btn-wrapper">
+          <div class="exp-btn">
+            <p>View the InfluxDB documentation</p>
+            <ul class="exp-btn-links">
+              <li><a href="/influxdb/cloud/">InfluxDB Cloud</a></li>
+              <li><a href="/influxdb/{{ $influxdbVersionV2 }}/">InfluxDB OSS {{ replaceRE "v" "" $influxdbVersionV2 }}</a></li>
+            </ul>
+          </div>
+          <div class="close-btn">
+            <span class="icon-x"></span>
+          </div>
         </div>
       </div>
-      <div class="card cta-btns">
-          <a class="btn" href="/flux/{{ $fluxVersion }}/get-started/">Get started with Flux</a>
-          <a class="btn" href="/flux/{{ $fluxVersion }}/stdlib/">Flux standard library</a>
-      </div>
     </div>
+    <div class="hero-img"></div>
   </div>
 
-  <div id="tick-stack" class="section row">
-    <div class="group-wrapper">
-      <div id="platform" class="card quarter">
-        <div class="card-content">
-          <h2><a href="/platform/">InfluxData 1.x TICK stack</a></h2>
-          <p>The leading modern time series platform, built for metrics and events.</p>
+  <div id="api-guides" class="section group-wrapper blue flush-left">
+    <div class="padding-wrapper">
+      <div>
+        <div class="text">
+          <h3>Develop with the InfluxDB API</h3>
+          <p>Build your application using the InfluxDB Cloud and InfluxDB OSS APIs.</p>
         </div>
-        <p><a href="/platform/">Learn more</a></p>
       </div>
-      <div id="tick-cards" class="three-quarters row">
-        <div class="card telegraf">
-          <div class="card-content">
-            <h2><a href="/telegraf/{{ $telegrafVersion }}/">Telegraf <span class="version">{{ $telegrafVersion }}</span></a></h2>
-            <p>Collect metrics from stacks, sensors and systems.</p>
-          </div>
-          <p><a href="/telegraf/{{ $telegrafVersion }}/">View documentation</a></p>
+      <div id="api-guides-btn" class="exp-btn-wrapper">
+        <div class="exp-btn">
+          <p>View the InfluxDB API Dev Guides</p>
+          <ul class="exp-btn-links">
+            <li><a href="/influxdb/cloud/api-guide/">InfluxDB Cloud</a></li>
+            <li><a href="/influxdb/{{ $influxdbVersionV2 }}/api-guide/">InfluxDB OSS {{ replaceRE "v" "" $influxdbVersionV2 }}</a></li>
+          </ul>
         </div>
-        <div class="card influxdb">
-          <div class="card-content">
-            <h2><a href="/influxdb/{{ $influxdbVersionV1 }}/">InfluxDB <span class="version">{{ $influxdbVersionV1 }}</span></a></h2>
-            <p>Write and query time series data.</p>
-          </div>
-          <p><a href="/influxdb/{{ $influxdbVersionV1 }}/">View documentation</a></p>
-        </div>
-        <div class="card chronograf">
-          <div class="card-content">
-            <h2><a href="/chronograf/{{ $chronografVersion }}/">Chronograf <span class="version">{{ $chronografVersion }}</span></a></h2>
-            <p>Visualize and manage time series data.</p>
-          </div>
-          <p><a href="/chronograf/{{ $chronografVersion }}/">View documentation</a></p>
-        </div>
-        <div class="card kapacitor">
-          <div class="card-content">
-            <h2><a href="/kapacitor/{{ $kapacitorVersion }}/">Kapacitor <span class="version">{{ $kapacitorVersion }}</span></a></h2>
-            <p>Process and alert on time series data.</p>
-          </div>
-          <p><a href="/kapacitor/{{ $kapacitorVersion }}/">View documentation</a></p>
+        <div class="close-btn">
+          <span class="icon-x"></span>
         </div>
       </div>
     </div>
   </div>
 
-  <div id="enterprise" class="section row">
-    <div class="group-wrapper">
-      <div class="card quarter">
-        <div class="card-content">
-          <h2>Enterprise offerings</h2>
-          <p>Enterprise tools to meet your business needs.</p>
+  <div id="popular" class="section group-wrapper">
+    <div class="product-cards">
+      <div id="telegraf" class="card">
+        <h3>Collect data with <span class="orange">Telegraf</span></h3>
+        <!-- <p>Collect time series data from many different sources.</p> -->
+        <div class="card-links">
+          <a href="/telegraf/{{ $telegrafVersion }}/">Get started with <strong>Telegraf {{ replaceRE "v" "" $telegrafVersion }}</strong></a>
+          <a href="/telegraf/{{ $telegrafVersion }}/plugins/">View Telegraf plugins</a>
         </div>
-        <p><a href="https://www.influxdata.com/contact-sales/">Contact Sales</a></p>
       </div>
-      <div id="tick-cards" class="three-quarters row">
-        <div class="card influxdb">
-          <div class="card-content">
-            <h2><a href="/enterprise_influxdb/{{ $enterpriseVersion }}/">InfluxDB Enterprise <span class="version">{{ $enterpriseVersion }}</span></a></h2>
-            <p>A scalable InfluxDB cluster designed for heavy workloads. Run InfluxDB Enterprise on your own infrastructure—on-premises, private cloud, public cloud, or at the edge.</p>
-          </div>
-          <p><a href="/enterprise_influxdb/{{ $enterpriseVersion }}/">View documentation</a></p>
-        </div>
-        <div class="card kapacitor">
-          <div class="card-content">
-            <h2><a href="https://archive.docs.influxdata.com/enterprise_kapacitor/v1.5/" target="_blank">Kapacitor Enterprise <span class="version">v1.5</span></a></h2>
-            <p>A high availability Kapacitor cluster with alert deduplication and backend authentication. Run Kapacitor Enterprise on your own infrastructure—on-premises, private cloud, public cloud, or at the edge.</p>
-          </div>
-          <p><a href="https://archive.docs.influxdata.com/enterprise_kapacitor/v1.5/" target="_blank">View documentation archive</a></p>
+      <div id="flux" class="card">
+        <h3>Query & process data with <span class="blue">Flux</span></h3>
+        <!-- <p>The data scripting language that queries, processes, alert ons, and writes data.</p> -->
+        <div class="card-links">
+          <a href="/flux/{{ $fluxVersion }}/">Get started with <strong>Flux {{ replaceRE "v" "" $fluxVersion }}</strong></a>
+          <a href="/flux/{{ $fluxVersion }}/stdlib/">View the Flux standard library</a>
         </div>
       </div>
     </div>
+  </div> 
+
+  <div id="learn-more" class="section group-wrapper">
+    <h4>Learn more</h4>
+    <div class="learn-items">
+      <div class="item">
+        <div class="icon">{{ partial "svgs/influxdbu.svg" }}</div>
+        <h5>InfluxDB University</h5>
+        <p>Free online training for InfluxDB and more.</p>
+        <a href="https://influxdbu.com/" target="_blank">Go to InfluxDB University</a>
+      </div>
+      <div class="item">
+        <div class="icon">{{ partial "svgs/book.svg" }}</div>
+        <h5>Time to Awesome</h5>
+        <p>Free online about using InfluxDB and Flux.</p>
+        <a href="https://awesome.influxdata.com/" target="_blank">View the book</a>
+      </div>
+      <div class="item">
+        <div class="icon">{{ partial "svgs/video-arrow.svg" }}</div>
+        <h5>InfluxData Videos</h5>
+        <p>Videos on specific topics related to time series and InfluxData projects.</p>
+        <a href="/resources/videos/">View videos</a>
+      </div>
+      <div class="item">
+        <div class="icon">{{ partial "svgs/hatch.svg" }}</div>
+        <h5>Case Studies</h5>
+        <p>Learn about real world use cases and InfluxDB in the wild.</p>
+        <a href="https://www.influxdata.com/_resources/case-studies/" target="_blank">View case studies</a>
+      </div>
+    </div>
   </div>
 
-  <div id="resources" class="section row">
-    <div class="group-wrapper">
-      <div class="card">
-        <div class="card-content">
-          <h2><a href="/resources/">Additional resources</a></h2>
-          <p>View additional resources related to InfluxDB and InfluxData products.</p>
-        </div>
+  <div id="tick" class="section group-wrapper blue flush-right">
+    <div class="padding-wrapper">
+      <div class="tick-title">
+        <h4><a href="/platform/#influxdata-1x-tick-stack">The TICK stack</a></h4>
+        <p>The original time series platform</p>
       </div>
-      <div class="card cta-btns">
-        <a class="btn" href="/resources/">View additional resources</a>
+      <div class="tick-links">
+        <ul class="oss">
+          <h5>Open Source</h5>
+          <li><a href="/telegraf/{{ $telegrafVersion }}/">Telegraf {{ replaceRE "v" "" $telegrafVersion }}</a></li>
+          <li><a href="/influxdb/{{ $influxdbVersionV1 }}/">InfluxDB {{ replaceRE "v" "" $influxdbVersionV1 }}</a></li>
+          <li><a href="/chronograf/{{ $chronografVersion }}/">Chronograf {{ replaceRE "v" "" $chronografVersion }}</a></li>
+          <li><a href="/kapacitor/{{ $kapacitorVersion }}/">Kapacitor {{ replaceRE "v" "" $kapacitorVersion }}</a></li>
+        </ul>
+        <ul class="enterprise">
+          <h5>Enterprise</h5>
+          <li><a href="/enterprise_influxdb/{{ $enterpriseVersion }}/">InfluxDB Enterprise {{ replaceRE "v" "" $enterpriseVersion }}</a></li>
+          <li><a href="https://archive.docs.influxdata.com/enterprise_kapacitor/v1.5/">Kapacitor Enterprise 1.5 <span class="cf-icon export-new"></span></a></li>
+        </ul>
+      </div>
+    </div>
+  </div>
+
+  <div id="copyright" class="section group-wrapper">
+    <div class="padding-wrapper">
+
+        <p>© {{ now.Year }} InfluxData, Inc.</p>
       </div>
     </div>
   </div>
 </div>
-
 {{ partial "footer.html" . }}
diff --git a/layouts/partials/footer.html b/layouts/partials/footer.html
index 446a0db01..e2d2353aa 100644
--- a/layouts/partials/footer.html
+++ b/layouts/partials/footer.html
@@ -2,9 +2,10 @@
 {{ $product := index $productPathData 0 }}
 {{ $currentVersion := index $productPathData 1 | default "v2.0"}}
 
-  <!-- InfluxDB URL modal -->
+  <!-- Modals -->
   {{ partial "footer/influxdb-url-modal.html" . }}
   {{ partial "footer/feature-callout.html" . }}
+  {{ partial "footer/fullscreen-code.html" . }}
 
   <!-- Docsearch JS -->
   {{ partial "footer/search.html" . }}
diff --git a/layouts/partials/footer/fullscreen-code.html b/layouts/partials/footer/fullscreen-code.html
new file mode 100644
index 000000000..10541a575
--- /dev/null
+++ b/layouts/partials/footer/fullscreen-code.html
@@ -0,0 +1,4 @@
+<div class="fullscreen-code highlight">
+  <div id="fullscreen-code-placeholder"></div>
+  <a class="fullscreen-close"><span class="icon-x"></span></a>
+</div>
diff --git a/layouts/partials/footer/influxdb-url-modal.html b/layouts/partials/footer/influxdb-url-modal.html
index aeadc40cc..896129750 100644
--- a/layouts/partials/footer/influxdb-url-modal.html
+++ b/layouts/partials/footer/influxdb-url-modal.html
@@ -15,13 +15,13 @@
   {{ .Scratch.Set "modalTitle" "Select your InfluxDB Cloud region" }}
 {{ end }}
 
-{{ .Scratch.Set "modalMessage" "Select your **InfluxDB Cloud region** or your **InfluxDB OSS URL** and we'll customize code examples for you." }}
+{{ .Scratch.Set "modalMessage" "Select your **InfluxDB Cloud region and cluster** or your **InfluxDB OSS URL** and we'll customize code examples for you. _[Identify your InfluxDB Cloud cluster](/influxdb/cloud/reference/regions/#regions-with-multiple-clusters)_." }}
 {{ if $isOSS }}
   {{ .Scratch.Set "modalMessage" "Customize your **InfluxDB OSS URL** and we'll update code examples for you." }}
 {{ else if $isEnterprise }}
   {{ .Scratch.Set "modalMessage" "Customize your **InfluxDB Enterprise URL** and we'll update code examples for you." }}
 {{ else if $isCloud }}
-  {{ .Scratch.Set "modalMessage" "Select your **InfluxDB Cloud region** and we'll customize code examples for you." }}
+  {{ .Scratch.Set "modalMessage" "Select your **InfluxDB Cloud region and cluster** and we'll customize code examples for you. _[Identify your InfluxDB Cloud cluster](/influxdb/cloud/reference/regions/#regions-with-multiple-clusters)_." }}
 {{ end }}
 
 {{ .Scratch.Set "modalRefLinks" (print "[InfluxDB Cloud regions](" $CloudLink ") or [InfluxDB OSS URLs](" $OSSLink ")") }}
@@ -62,12 +62,30 @@
             <h5>{{ if .short_name}}{{ .short_name }}{{ else }}{{ .name }}{{ end }}</h5>
             <ul>
             {{ range .regions }}
-              <li>
-                <label for="{{ anchorize .name }}" {{ if .status }}class="{{ .status }}"{{ end }}>
-                  <input type="radio" name="influxdb-{{ $formID }}-url" id="{{ anchorize .name }}" value="{{ .url }}" checked>
-                  <span class="radio"></span>
-                  {{ .name }}
-                </label>
+              <li class="region-group">
+                {{ if .clusters }}
+                  <p class="region">
+                    <span class="fake-radio"></span>
+                    {{ .name }}
+                  </p>
+                  <ul class="clusters">
+                  {{ range .clusters }}
+                    <li>
+                      <label for="{{ anchorize .name }}" {{ if .status }}class="{{ .status }}"{{ end }}>
+                      <input type="radio" name="influxdb-{{ $formID }}-url" id="{{ anchorize .name }}" value="{{ .url }}" checked>
+                      <span class="radio"></span>
+                      {{ .name }}
+                    </label>
+                    </li>
+                  {{ end }}
+                  </ul>
+                {{ else }}
+                  <label for="{{ anchorize .name }}" {{ if .status }}class="{{ .status }}"{{ end }}>
+                    <input type="radio" name="influxdb-{{ $formID }}-url" id="{{ anchorize .name }}" value="{{ .url }}" checked>
+                    <span class="radio"></span>
+                    {{ .name }}
+                  </label>
+                {{ end }}
               </li>
             {{ end }}
           {{ end }}
diff --git a/layouts/partials/footer/javascript.html b/layouts/partials/footer/javascript.html
index e2ecc1bdc..910bdcf58 100644
--- a/layouts/partials/footer/javascript.html
+++ b/layouts/partials/footer/javascript.html
@@ -8,7 +8,9 @@
 {{ $keybindings := resources.Get "js/keybindings.js" }}
 {{ $fluxGroupKeys := resources.Get "js/flux-group-keys.js" }}
 {{ $fluxCurrentTime := resources.Get "js/flux-current-time.js" }}
-{{ $footerjs := slice $versionSelector $contentInteractions $searchInteractions $listFilters $influxdbURLs $featureCallouts $notifications $keybindings | resources.Concat "js/footer.bundle.js" | resources.Fingerprint }}
+{{ $fullscreenCode := resources.Get "js/fullscreen-code.js" }}
+{{ $homepageInteractions := resources.Get "js/home-interactions.js" }}
+{{ $footerjs := slice $versionSelector $contentInteractions $searchInteractions $listFilters $influxdbURLs $featureCallouts $notifications $keybindings $fullscreenCode $homepageInteractions | resources.Concat "js/footer.bundle.js" | resources.Fingerprint }}
 {{ $fluxGroupKeyjs := slice $fluxGroupKeys | resources.Concat "js/flux-group-keys.js" | resources.Fingerprint }}
 {{ $fluxCurrentTimejs := slice $fluxCurrentTime | resources.Concat "js/flux-current-time.js" | resources.Fingerprint }}
 
diff --git a/layouts/partials/header.html b/layouts/partials/header.html
index 63c36ece2..6e04ffd30 100644
--- a/layouts/partials/header.html
+++ b/layouts/partials/header.html
@@ -25,5 +25,5 @@
 
     <meta name="Copyright" content="InfluxData Inc." />
   </head>
-  <body class='{{if ne $product nil}}{{ $product }}{{ end }}{{ if in $currentVersion "v1" }} v1{{ end }}'>
+  <body class='{{if ne $product nil}}{{ $product }}{{ else }}home{{ end }}{{ if in $currentVersion "v1" }} v1{{ end }}'>
     {{ if not .Site.IsServer }}{{ partial "header/google-analytics-body.html" }}{{ end }}
diff --git a/layouts/partials/sidebar/nested-menu.html b/layouts/partials/sidebar/nested-menu.html
index abeb169e9..feceb9ea8 100644
--- a/layouts/partials/sidebar/nested-menu.html
+++ b/layouts/partials/sidebar/nested-menu.html
@@ -4,37 +4,37 @@
 {{ range $menu }}
   <li class="nav-category {{ if eq $page.RelPermalink .URL }}active{{end}}">
     {{ if .HasChildren }}<a href="#" class="children-toggle {{ if or ($page.IsMenuCurrent .Menu .) ($page.HasMenuCurrent .Menu .) }}open{{end}}"></a>{{ end }}
-    <a href="{{ .URL }}">{{ .Name }}</a>
+    <a href='{{ cond (isset .Params "url") .Params.url .URL }}'>{{ .Name }}</a>
     {{ if .HasChildren }}
       <ul class="children {{ if or ($page.IsMenuCurrent .Menu .) ($page.HasMenuCurrent .Menu .) }}open{{end}}">
       {{ range .Children }}
         <li class="nav-item {{ if eq $page.RelPermalink .URL }}active{{end}}">
           {{ if .HasChildren }}<a href="#" class="children-toggle {{ if or ($page.IsMenuCurrent .Menu .) ($page.HasMenuCurrent .Menu .) }}open{{end}}"></a>{{ end }}
-          <a href="{{ .URL }}">{{ .Name }}</a>
+          <a href='{{ cond (isset .Params "url") .Params.url .URL }}'>{{ .Name }}</a>
           {{ if .HasChildren }}
             <ul class="children {{ if or ($page.IsMenuCurrent .Menu .) ($page.HasMenuCurrent .Menu .) }}open{{end}}">
             {{ range .Children }}
               <li class="nav-item {{ if eq $page.RelPermalink .URL }}active{{end}}">
                 {{ if .HasChildren }}<a href="#" class="children-toggle {{ if or ($page.IsMenuCurrent .Menu .) ($page.HasMenuCurrent .Menu .) }}open{{end}}"></a>{{ end }}
-                <a href="{{ .URL }}">{{ .Name }}</a>
+                <a href='{{ cond (isset .Params "url") .Params.url .URL }}'>{{ .Name }}</a>
                 {{ if .HasChildren }}
                   <ul class="children {{ if or ($page.IsMenuCurrent .Menu .) ($page.HasMenuCurrent .Menu .) }}open{{end}}">
                   {{ range .Children }}
                     <li class="nav-item {{ if eq $page.RelPermalink .URL }}active{{end}}">
                       {{ if .HasChildren }}<a href="#" class="children-toggle {{ if or ($page.IsMenuCurrent .Menu .) ($page.HasMenuCurrent .Menu .) }}open{{end}}"></a>{{ end }}
-                      <a href="{{ .URL }}">{{ .Name }}</a>
+                      <a href='{{ cond (isset .Params "url") .Params.url .URL }}'>{{ .Name }}</a>
                       {{ if .HasChildren }}
                         <ul class="children {{ if or ($page.IsMenuCurrent .Menu .) ($page.HasMenuCurrent .Menu .) }}open{{end}}">
                         {{ range .Children }}
                           <li class="nav-item {{ if eq $page.RelPermalink .URL }}active{{end}}">
                             {{ if .HasChildren }}<a href="#" class="children-toggle {{ if or ($page.IsMenuCurrent .Menu .) ($page.HasMenuCurrent .Menu .) }}open{{end}}"></a>{{ end }}
-                            <a href="{{ .URL }}">{{ .Name }}</a>
+                            <a href='{{ cond (isset .Params "url") .Params.url .URL }}'>{{ .Name }}</a>
                             {{ if .HasChildren }}
                               <ul class="children {{ if or ($page.IsMenuCurrent .Menu .) ($page.HasMenuCurrent .Menu .) }}open{{end}}">
                               {{ range .Children }}
                                 <li class="nav-item {{ if eq $page.RelPermalink .URL }}active{{end}}">
                                   {{ if .HasChildren }}<a href="#" class="children-toggle {{ if or ($page.IsMenuCurrent .Menu .) ($page.HasMenuCurrent .Menu .) }}open{{end}}"></a>{{ end }}
-                                  <a href="{{ .URL }}">{{ .Name }}</a>
+                                  <a href='{{ cond (isset .Params "url") .Params.url .URL }}'>{{ .Name }}</a>
 
                                   <!-- Begin nested block -->
                                   {{ if .HasChildren }}
@@ -42,7 +42,7 @@
                                     {{ range .Children }}
                                       <li class="nav-item {{ if eq $page.RelPermalink .URL }}active{{end}}">
                                         {{ if .HasChildren }}<a href="#" class="children-toggle {{ if or ($page.IsMenuCurrent .Menu .) ($page.HasMenuCurrent .Menu .) }}open{{end}}"></a>{{ end }}
-                                        <a href="{{ .URL }}">{{ .Name }}</a>
+                                        <a href='{{ cond (isset .Params "url") .Params.url .URL }}'>{{ .Name }}</a>
                                         <!-- To add more nested layers, copy the nested block and paste it here -->
                                       </li>
                                     {{ end }}
diff --git a/layouts/partials/svgs/book.svg b/layouts/partials/svgs/book.svg
new file mode 100644
index 000000000..dfff1ad0c
--- /dev/null
+++ b/layouts/partials/svgs/book.svg
@@ -0,0 +1,13 @@
+<svg version="1.1" id="book" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"
+	 viewBox="0 0 77 74" style="enable-background:new 0 0 77 74;" xml:space="preserve">
+<path class="c1" d="M76.9,0.4L76.9,0.4L38.5,15.5L0.1,0.4l0,0L0,0.4v58h0l0,0l38.5,15.1L77,58.5l0,0h0L76.9,0.4L76.9,0.4z M5.7,54
+	V9.3l32.8,12.9L71.3,9.4V54L38.5,66.9L5.7,54z"/>
+<polygon class="c2" points="5.7,54 5.7,9.3 38.5,22.2 71.3,9.4 71.3,54 38.5,66.9 "/>
+<polygon class="c1" points="48.9,25.1 65.4,18.5 65.4,24.5 48.9,31.1 "/>
+<polygon class="c1" points="48.9,37.5 65.4,31 65.4,36.9 48.9,43.5 "/>
+<polygon class="c1" points="48.9,50 65.4,43.4 65.4,49.3 48.9,55.9 "/>
+<polygon class="magenta" points="48.9,55.9 41.9,58.8 41.9,20.9 48.9,18.2 "/>
+<polygon class="c1" points="35.7,28.1 5.7,16.2 5.7,22.1 35.7,34 "/>
+<polygon class="c1" points="35.7,40.5 11.6,31 11.6,36.9 35.7,46.5 "/>
+<polygon class="c1" points="35.7,53 11.6,43.4 11.6,49.3 35.7,58.9 "/>
+</svg>
diff --git a/layouts/partials/svgs/hatch.svg b/layouts/partials/svgs/hatch.svg
new file mode 100644
index 000000000..78caa6b83
--- /dev/null
+++ b/layouts/partials/svgs/hatch.svg
@@ -0,0 +1,7 @@
+<svg version="1.1" id="hatch" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"
+	 viewBox="0 0 73 74" style="enable-background:new 0 0 73 74;" xml:space="preserve">
+<path class="c1" d="M36.5,11.1L47.2,0.4l4.3,4.3L40.8,15.5l12.9,12.9l-4.3,4.3l-28-28l4.3-4.3L36.5,11.1z"/>
+<path class="magenta" d="M62.3,37l10.7,10.7L68.7,52L58,41.3L45.1,54.3l-4.3-4.3L68.7,22l4.3,4.3L62.3,37z"/>
+<path class="c1" d="M36.5,62.9L25.8,73.6l-4.3-4.3l10.7-10.7L19.2,45.6l4.3-4.3l27.9,27.9l-4.3,4.3L36.5,62.9z"/>
+<path class="magenta" d="M10.6,37L-0.1,26.3L4.2,22l10.7,10.7l12.9-12.9l4.3,4.3l-28,28l-4.3-4.3L10.6,37z"/>
+</svg>
diff --git a/layouts/partials/svgs/homepage-hero.svg b/layouts/partials/svgs/homepage-hero.svg
deleted file mode 100644
index 945937af6..000000000
--- a/layouts/partials/svgs/homepage-hero.svg
+++ /dev/null
@@ -1,673 +0,0 @@
-<svg version="1.1" id="hero-img" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"
-	 viewBox="0 0 600 600" style="enable-background:new 0 0 600 600;" xml:space="preserve">
-<style type="text/css">
-	.st0{opacity:0.25;fill:url(#SVGID_1_);}
-	.st1{fill:url(#SVGID_2_);}
-	.st2{fill:url(#SVGID_3_);}
-	.st3{fill:url(#SVGID_4_);}
-	.st4{fill:url(#SVGID_5_);}
-	.st5{opacity:0.51;fill:url(#SVGID_6_);}
-	.st6{opacity:0.69;fill:url(#SVGID_7_);}
-	.st7{fill:url(#SVGID_8_);}
-	.st8{fill:url(#SVGID_9_);}
-	.st9{fill:url(#SVGID_10_);}
-	.st10{fill:url(#SVGID_11_);}
-	.st11{fill:url(#SVGID_12_);}
-	.st12{fill:url(#SVGID_13_);}
-	.st13{fill:url(#SVGID_14_);}
-	.st14{fill:url(#SVGID_15_);}
-	.st15{fill:url(#SVGID_16_);}
-	.st16{fill:url(#SVGID_17_);}
-	.st17{fill:url(#SVGID_18_);}
-	.st18{opacity:0.5;fill:url(#SVGID_19_);}
-	.st19{opacity:0.65;}
-	.st20{fill:url(#SVGID_20_);}
-	.st21{opacity:0.64;}
-	.st22{fill:url(#SVGID_21_);}
-	.st23{opacity:0.54;fill:url(#SVGID_22_);}
-	.st24{opacity:0.88;}
-	.st25{opacity:0.31;}
-	.st26{fill:url(#SVGID_23_);}
-	.st27{opacity:0.3;}
-	.st28{fill:#439ED5;}
-	.st29{opacity:0.62;}
-	.st30{fill:url(#SVGID_24_);}
-	.st31{opacity:0.4;}
-	.st32{opacity:0.51;}
-	.st33{fill:url(#SVGID_25_);}
-	.st34{opacity:0.5;}
-	.st35{fill:url(#SVGID_26_);}
-	.st36{fill:url(#SVGID_27_);}
-	.st37{fill:url(#SVGID_28_);}
-	.st38{opacity:0.55;}
-	.st39{fill:url(#SVGID_29_);}
-	.st40{fill:url(#SVGID_30_);}
-	.st41{opacity:0.6;}
-	.st42{fill:url(#SVGID_31_);}
-	.st43{fill:url(#SVGID_32_);}
-	.st44{fill:url(#SVGID_33_);}
-	.st45{fill:url(#SVGID_34_);}
-	.st46{fill:url(#SVGID_35_);}
-	.st47{opacity:0.78;fill:url(#SVGID_36_);}
-	.st48{fill:url(#SVGID_37_);}
-	.st49{opacity:0.69;fill:url(#SVGID_38_);}
-	.st50{opacity:0.42;fill:url(#SVGID_39_);}
-	.st51{opacity:0.58;}
-	.st52{fill:#E5C9ED;}
-	.st53{opacity:0.59;fill:url(#SVGID_40_);}
-	.st54{opacity:0.85;fill:url(#SVGID_41_);}
-	.st55{fill:#CCEC22;}
-	.st56{fill:url(#SVGID_42_);}
-	.st57{fill:url(#SVGID_43_);}
-	.st58{fill:#292933;}
-	.st59{fill:#47BCEA;}
-	.st60{fill:url(#SVGID_44_);}
-	.st61{fill:url(#SVGID_45_);}
-	.st62{fill:url(#SVGID_46_);}
-	.st63{opacity:0.55;fill:url(#SVGID_47_);}
-	.st64{fill:#B67FEF;}
-	.st65{fill:url(#SVGID_48_);}
-	.st66{fill:#AA6FF7;}
-	.st67{fill:url(#SVGID_49_);}
-	.st68{fill:url(#SVGID_50_);}
-	.st69{fill:url(#SVGID_51_);}
-	.st70{fill:url(#SVGID_52_);}
-	.st71{fill:url(#SVGID_53_);}
-	.st72{fill:url(#SVGID_54_);}
-</style>
-<g id="back">
-</g>
-<g id="platform">
-	<g>
-
-			<radialGradient id="SVGID_1_" cx="-497.7702" cy="524.6248" r="115.4329" gradientTransform="matrix(1.8765 6.299008e-02 -6.241235e-02 0.9843 1265.2174 -21.8549)" gradientUnits="userSpaceOnUse">
-			<stop  offset="0" style="stop-color:#7A64E4"/>
-			<stop  offset="1" style="stop-color:#7A64E5;stop-opacity:0"/>
-		</radialGradient>
-		<ellipse class="st0" cx="287.2" cy="452.1" rx="245.6" ry="133.7"/>
-		<g>
-			<linearGradient id="SVGID_2_" gradientUnits="userSpaceOnUse" x1="78.8085" y1="426.2571" x2="525.5908" y2="426.2571">
-				<stop  offset="0" style="stop-color:#1D1A33"/>
-				<stop  offset="1" style="stop-color:#1D1934"/>
-			</linearGradient>
-			<path class="st1" d="M525.5,424.8v-24H508v6.5L320.5,299.2c-11.3-6.5-25.2-6.5-36.5,0L96.3,407.5v-6.8L78.8,408l0.2,18.8l0,0.6
-				c0.3,4.7,2.8,9.2,7.5,11.9l197.5,114c11.3,6.5,25.2,6.5,36.5,0l197.5-114C523.6,436.1,526,430.4,525.5,424.8z"/>
-			<linearGradient id="SVGID_3_" gradientUnits="userSpaceOnUse" x1="309.4343" y1="426.4217" x2="536.4043" y2="431.9964">
-				<stop  offset="0" style="stop-color:#1D1A33"/>
-				<stop  offset="0.809" style="stop-color:#292645"/>
-			</linearGradient>
-			<path class="st2" d="M518.1,439.3l-197.5,114c-5.5,3.2-11.7,4.8-17.9,4.9v-264c6.2,0,12.4,1.7,17.9,4.9L508,407.4v-6.5l17.5,7.1
-				v16.9C526,430.4,523.6,436.1,518.1,439.3z"/>
-		</g>
-		<g>
-
-				<linearGradient id="SVGID_4_" gradientUnits="userSpaceOnUse" x1="2204.7739" y1="525.7761" x2="2195.2732" y2="155.2478" gradientTransform="matrix(-1 0 0 1 2503.6987 0)">
-				<stop  offset="3.828044e-03" style="stop-color:#524885"/>
-				<stop  offset="1" style="stop-color:#36305F"/>
-			</linearGradient>
-			<path class="st3" d="M517.9,394.9L320.2,280.8c-11.3-6.5-25.2-6.5-36.5,0L86,394.9c-10.1,5.8-10.1,20.3,0,26.1l197.7,114.1
-				c11.3,6.5,25.2,6.5,36.5,0L517.9,421C528,415.2,528,400.7,517.9,394.9z"/>
-			<g>
-
-					<linearGradient id="SVGID_5_" gradientUnits="userSpaceOnUse" x1="2201.7529" y1="273.9655" x2="2201.7529" y2="541.9379" gradientTransform="matrix(-1 0 0 1 2503.6987 0)">
-					<stop  offset="0" style="stop-color:#36305F;stop-opacity:0"/>
-					<stop  offset="1" style="stop-color:#4C387F"/>
-				</linearGradient>
-				<path class="st4" d="M301.9,541.9c-6.6,0-13.3-1.7-19.2-5.1L85,422.7c-5.3-3.1-8.5-8.6-8.5-14.7c0-6.1,3.2-11.6,8.5-14.7
-					l197.7-114.1c11.9-6.8,26.6-6.8,38.4,0l197.7,114.1c5.3,3.1,8.5,8.6,8.5,14.7c0,6.1-3.2,11.6-8.5,14.7L321.2,536.8
-					C315.2,540.2,308.6,541.9,301.9,541.9z M301.9,277.8c-6,0-12,1.5-17.3,4.6L86.9,396.5c-4.1,2.4-6.6,6.6-6.6,11.4
-					c0,4.8,2.5,9,6.6,11.4l197.7,114.1c10.7,6.2,23.9,6.2,34.6,0l197.7-114.1c4.1-2.4,6.6-6.6,6.6-11.4c0-4.8-2.5-9-6.6-11.4
-					L319.3,282.4C313.9,279.3,307.9,277.8,301.9,277.8z"/>
-			</g>
-		</g>
-	</g>
-
-		<radialGradient id="SVGID_6_" cx="-491.2517" cy="356.4801" r="105.5277" gradientTransform="matrix(1.429 -0.1202 9.611484e-02 1.1429 1006.0948 -159.5117)" gradientUnits="userSpaceOnUse">
-		<stop  offset="0" style="stop-color:#22A4ED;stop-opacity:0.8"/>
-		<stop  offset="0.925" style="stop-color:#B62FDC;stop-opacity:0"/>
-	</radialGradient>
-	<path class="st5" d="M509.1,292.6c5.7,68.1-66.1,129.7-160.4,137.7s-175.4-40.8-181.2-108.9c-5.7-68.1,66.1-129.7,160.4-137.7
-		C422.3,175.7,503.4,224.5,509.1,292.6z"/>
-</g>
-<g id="Layer_15">
-	<g>
-		<linearGradient id="SVGID_7_" gradientUnits="userSpaceOnUse" x1="203.0987" y1="422.3886" x2="124.6965" y2="383.8019">
-			<stop  offset="0" style="stop-color:#1C1C23"/>
-			<stop  offset="0.7663" style="stop-color:#2B264C;stop-opacity:0"/>
-		</linearGradient>
-		<polygon class="st6" points="199.1,409.5 199.7,398.9 126.9,384.7 117.5,402 186.6,415.1 182.6,408.8 		"/>
-		<linearGradient id="SVGID_8_" gradientUnits="userSpaceOnUse" x1="190.1116" y1="456.9626" x2="192.0644" y2="212.8648">
-			<stop  offset="0" style="stop-color:#241F4A"/>
-			<stop  offset="1" style="stop-color:#565499"/>
-		</linearGradient>
-		<path class="st7" d="M205.8,409.8L199.4,164l-16.7,8.2l-7.5,237.6l0,0c0,2.3,1.5,4.7,4.5,6.5c6,3.6,15.7,3.6,21.7,0
-			C204.3,414.5,205.8,412.2,205.8,409.8L205.8,409.8z"/>
-		<g>
-			<linearGradient id="SVGID_9_" gradientUnits="userSpaceOnUse" x1="167.5772" y1="189.1854" x2="187.9729" y2="149.6958">
-				<stop  offset="0" style="stop-color:#565499"/>
-				<stop  offset="1" style="stop-color:#2D2E5C"/>
-			</linearGradient>
-			<path class="st8" d="M152.6,153.1c-4,13.6,22,33,46.1,41l-1.5-18l15.2-9.2C192.8,148,156.1,141.2,152.6,153.1z"/>
-
-				<linearGradient id="SVGID_10_" gradientUnits="userSpaceOnUse" x1="776.6206" y1="144.0618" x2="742.1387" y2="194.0606" gradientTransform="matrix(1 0 0 1 -547.1423 0)">
-				<stop  offset="0" style="stop-color:#6365AD"/>
-				<stop  offset="1" style="stop-color:#434280"/>
-			</linearGradient>
-			<path class="st9" d="M215.6,173.8c0,6.9-4.8,15.3-10.9,18.8c-2.8,1.6-5.3,1.9-7.2,1c-0.3-0.1-0.6-0.3-0.9-0.5
-				c-1.7-1.2-2.7-3.5-2.7-6.7c0-6.9,4.8-15.3,10.8-18.8c3.1-1.8,5.9-1.9,7.9-0.7C214.4,168,215.5,170.4,215.6,173.8z"/>
-		</g>
-		<g>
-			<linearGradient id="SVGID_11_" gradientUnits="userSpaceOnUse" x1="87.1691" y1="301.1135" x2="216.6932" y2="179.1741">
-				<stop  offset="0" style="stop-color:#241F4A"/>
-				<stop  offset="1" style="stop-color:#565499"/>
-			</linearGradient>
-			<polygon class="st10" points="76,290.7 185.7,229.3 203.4,186.1 201.5,181 			"/>
-
-				<linearGradient id="SVGID_12_" gradientUnits="userSpaceOnUse" x1="532.9785" y1="363.2299" x2="713.1932" y2="209.5273" gradientTransform="matrix(1 0 0 1 -547.1423 0)">
-				<stop  offset="0" style="stop-color:#B22FD8"/>
-				<stop  offset="0.1405" style="stop-color:#A539D9"/>
-				<stop  offset="0.3984" style="stop-color:#8453DD"/>
-				<stop  offset="0.7419" style="stop-color:#4F7DE4"/>
-				<stop  offset="1" style="stop-color:#22A0E9"/>
-			</linearGradient>
-			<polygon class="st11" points="76,290.7 70.2,286.9 201.5,181 			"/>
-			<linearGradient id="SVGID_13_" gradientUnits="userSpaceOnUse" x1="214.2197" y1="6.5763" x2="212.1984" y2="200.6273">
-				<stop  offset="0" style="stop-color:#22A0E9"/>
-				<stop  offset="0.2581" style="stop-color:#4F7DE4"/>
-				<stop  offset="0.6016" style="stop-color:#8453DD"/>
-				<stop  offset="0.8595" style="stop-color:#A539D9"/>
-				<stop  offset="1" style="stop-color:#B22FD8"/>
-			</linearGradient>
-			<polygon class="st12" points="207.9,176.1 218.6,20.9 209.8,20.9 			"/>
-
-				<linearGradient id="SVGID_14_" gradientUnits="userSpaceOnUse" x1="741.2304" y1="202.9234" x2="742.4446" y2="51.1512" gradientTransform="matrix(1 0 0 1 -547.1423 0)">
-				<stop  offset="0" style="stop-color:#565499"/>
-				<stop  offset="1" style="stop-color:#241F4A"/>
-			</linearGradient>
-			<polygon class="st13" points="204.2,179.4 180.2,153.4 209.9,20.9 207.9,176.1 			"/>
-
-				<linearGradient id="SVGID_15_" gradientUnits="userSpaceOnUse" x1="818.6823" y1="227.1644" x2="819.0865" y2="176.6261" gradientTransform="matrix(1 0 0 1 -547.1423 0)">
-				<stop  offset="0" style="stop-color:#381565"/>
-				<stop  offset="1" style="stop-color:#565499"/>
-			</linearGradient>
-			<polygon class="st14" points="210.3,176.8 243,166.3 333.2,219.8 210.5,181.3 			"/>
-			<linearGradient id="SVGID_16_" gradientUnits="userSpaceOnUse" x1="366.8544" y1="235.6086" x2="149.5577" y2="156.7754">
-				<stop  offset="0" style="stop-color:#22A0E9"/>
-				<stop  offset="0.2581" style="stop-color:#4F7DE4"/>
-				<stop  offset="0.6016" style="stop-color:#8453DD"/>
-				<stop  offset="0.8595" style="stop-color:#A539D9"/>
-				<stop  offset="1" style="stop-color:#B22FD8"/>
-			</linearGradient>
-			<polygon class="st15" points="333,226.9 333,219.8 210.5,181.3 			"/>
-			<linearGradient id="SVGID_17_" gradientUnits="userSpaceOnUse" x1="211.0598" y1="194.1226" x2="202.5837" y2="151.742">
-				<stop  offset="0" style="stop-color:#22A0E9"/>
-				<stop  offset="0.2581" style="stop-color:#4F7DE4"/>
-				<stop  offset="0.6016" style="stop-color:#8453DD"/>
-				<stop  offset="0.8595" style="stop-color:#A539D9"/>
-				<stop  offset="1" style="stop-color:#B22FD8"/>
-			</linearGradient>
-			<path class="st16" d="M218.9,182.1c-1.7-3.6-4.8-8.5-7.6-10.4c0,0-0.1,0-0.1,0c-1.3-0.7-3-0.5-4.9,0.6c-4,2.3-7.2,7.8-7.1,12.4
-				c0,2.1,0.7,3.6,1.8,4.4c0.2,0.1,0.4,0.3,0.6,0.4c0.7,0.3,1.5,0.4,2.3,0.2c0.4,0.1,0.7,0.2,1.1,0.1c7.8-0.5,10.1-0.4,12.1-2.3
-				C218.4,186.4,219.6,183.6,218.9,182.1z"/>
-		</g>
-	</g>
-	<g>
-		<linearGradient id="SVGID_18_" gradientUnits="userSpaceOnUse" x1="243.2493" y1="435.5272" x2="694.1861" y2="50.9293">
-			<stop  offset="0" style="stop-color:#22A1EA"/>
-			<stop  offset="0.2622" style="stop-color:#507DE5"/>
-			<stop  offset="0.6038" style="stop-color:#8553DE"/>
-			<stop  offset="0.8602" style="stop-color:#A639DA"/>
-			<stop  offset="1" style="stop-color:#B32FD9"/>
-		</linearGradient>
-		<path class="st17" d="M458.4,273l-10.6-6.1c0,0,0,0,0,0L429,256.1c-32.4-18.7-72.3-18.7-104.7,0l-82.7,47.7c0,0,0,0,0,0l-12.5,7.2
-			c-2.6,1.5-4.2,4.3-4.2,7.3l0.2,102.9c0,3.3,3,5.6,6,5.2c-1.4-0.9-2.3-2.5-2.3-4.3L228.6,319c0-2.1,0.8-4,2.1-5.6
-			c0.5-0.5,1-0.9,1.7-1.3l91.9-53c32.4-18.7,72.3-18.7,104.7,0l17.6,10.1c0,0.1-0.1,0.2-0.1,0.3l9.1,5.2c2.6,1.5,4.2,4.3,4.2,7.3
-			l-0.2,102.9c0,1.3-0.4,2.4-1.1,3.2c2.2-0.5,4-2.5,4-5.1l0.2-102.9C462.6,277.2,461,274.5,458.4,273z"/>
-		<linearGradient id="SVGID_19_" gradientUnits="userSpaceOnUse" x1="233.7289" y1="404.7695" x2="735.3603" y2="146.7445">
-			<stop  offset="0" style="stop-color:#22A1EA"/>
-			<stop  offset="0.2622" style="stop-color:#507DE5"/>
-			<stop  offset="0.6038" style="stop-color:#8553DE"/>
-			<stop  offset="0.8602" style="stop-color:#A639DA"/>
-			<stop  offset="1" style="stop-color:#B32FD9"/>
-		</linearGradient>
-		<path class="st18" d="M455.5,274.4L429,259.2c-32.4-18.7-72.3-18.7-104.8,0l-91.9,53c-2.6,1.5-4.2,4.3-4.2,7.3l0.2,102.9
-			c0,4,4.4,6.5,7.9,4.5l97.8-56.4c26.4-15.2,58.8-15.2,85.2,0l32.5,18.7c3.5,2,7.8-0.5,7.9-4.5l0.2-102.9
-			C459.7,278.7,458.1,275.9,455.5,274.4z"/>
-		<g class="st19">
-			<linearGradient id="SVGID_20_" gradientUnits="userSpaceOnUse" x1="240.5313" y1="439.3951" x2="447.1792" y2="263.148">
-				<stop  offset="0" style="stop-color:#22A1EA"/>
-				<stop  offset="0.2622" style="stop-color:#507DE5"/>
-				<stop  offset="0.6038" style="stop-color:#8553DE"/>
-				<stop  offset="0.8602" style="stop-color:#A639DA"/>
-				<stop  offset="1" style="stop-color:#B32FD9"/>
-			</linearGradient>
-			<path class="st20" d="M233.6,428.1c-1,0-2-0.3-2.9-0.8c-1.8-1-2.9-2.9-2.9-5l-0.2-102.9c0-3.2,1.7-6.1,4.5-7.7l91.9-53
-				c32.5-18.7,72.8-18.7,105.3,0l26.5,15.2c2.8,1.6,4.5,4.6,4.5,7.7L460,384.6c0,2.1-1.1,3.9-2.9,5c-1.8,1-4,1-5.8,0l-32.5-18.7
-				c-26.1-15.1-58.6-15.1-84.7,0l-97.8,56.4C235.5,427.8,234.5,428.1,233.6,428.1z M376.6,245.8c-18,0-36,4.6-52.1,13.9l-91.9,53
-				c-2.4,1.4-3.9,4-3.9,6.8l0.2,102.9c0,1.7,0.9,3.2,2.4,4.1c1.5,0.8,3.2,0.8,4.7,0l97.8-56.4c26.4-15.2,59.3-15.2,85.7,0l32.5,18.7
-				c1.5,0.9,3.2,0.9,4.7,0c1.5-0.8,2.4-2.4,2.4-4.1l0.2-102.9c0-2.8-1.5-5.4-3.9-6.8l-26.5-15.2
-				C412.6,250.4,394.6,245.8,376.6,245.8z"/>
-		</g>
-		<g class="st21">
-			<linearGradient id="SVGID_21_" gradientUnits="userSpaceOnUse" x1="231.373" y1="436.8676" x2="453.0688" y2="247.7862">
-				<stop  offset="0" style="stop-color:#22A1EA"/>
-				<stop  offset="0.2622" style="stop-color:#507DE5"/>
-				<stop  offset="0.6038" style="stop-color:#8553DE"/>
-				<stop  offset="0.8602" style="stop-color:#A639DA"/>
-				<stop  offset="1" style="stop-color:#B32FD9"/>
-			</linearGradient>
-			<path class="st22" d="M218.4,418.6c-1,0-1.9-0.3-2.8-0.8c-1.8-1-2.8-2.9-2.8-4.9l-0.2-102.1c0-3.1,1.7-6.1,4.4-7.6L322.5,242
-				c32.1-18.5,71.9-18.5,103.9,0l4,2.3l0,0l0,0l37.1,21.2c2.7,1.6,4.4,4.5,4.4,7.6l-0.2,102.1c0,2.1-1.1,3.9-2.8,4.9
-				c-1.8,1-3.9,1-5.7,0l-0.4-0.2c-0.2-0.1-0.3-0.5-0.2-0.7c0.1-0.2,0.5-0.3,0.7-0.2l0.4,0.2c1.5,0.8,3.2,0.8,4.6,0
-				c1.5-0.8,2.3-2.3,2.3-4l0.2-102.1c0-2.8-1.5-5.4-3.9-6.7l-14.4-8.3l-0.1,0.1l-0.1-0.1L426,242.9c-31.7-18.3-71.2-18.3-102.9,0
-				L217.5,304c-2.4,1.4-3.9,4-3.9,6.7l0.2,102.1c0,1.7,0.9,3.2,2.3,4s3.2,0.8,4.6,0l4.2-2.4c0.2-0.1,0.6-0.1,0.7,0.2
-				c0.1,0.2,0.1,0.6-0.2,0.7l-4.2,2.4C220.4,418.3,219.4,418.6,218.4,418.6z"/>
-		</g>
-	</g>
-	<linearGradient id="SVGID_22_" gradientUnits="userSpaceOnUse" x1="232.7789" y1="349.882" x2="544.8936" y2="349.882">
-		<stop  offset="0" style="stop-color:#22A3EC"/>
-		<stop  offset="0.2509" style="stop-color:#4C82E7;stop-opacity:0.5424"/>
-		<stop  offset="0.5484" style="stop-color:#8258E1;stop-opacity:0"/>
-	</linearGradient>
-	<path class="st23" d="M428.5,340.3l-13.9,6.5c-25.5-12.7-55.7-11.9-80.6,2.5l-40.8,23.5l-60.5,30.5v-60.9c0,0,32.6-12.2,39.1-14
-		c19.6-5.6,35.9,23.1,53.7,14.9c14.9-6.8,33.3-45.9,47.2-46.7C392.9,295.3,404.9,342.2,428.5,340.3z"/>
-	<g class="st24">
-		<g class="st25">
-
-				<linearGradient id="SVGID_23_" gradientUnits="userSpaceOnUse" x1="393.4461" y1="259.7773" x2="393.4461" y2="328.015" gradientTransform="matrix(-1 0 0 1 766.525 0)">
-				<stop  offset="0.3296" style="stop-color:#22A3EC;stop-opacity:0"/>
-				<stop  offset="0.7877" style="stop-color:#22A3EC"/>
-				<stop  offset="0.986" style="stop-color:#22A3EC;stop-opacity:0"/>
-			</linearGradient>
-			<polygon class="st26" points="372.7,328 372.4,259.8 373.5,259.8 373.8,328 			"/>
-		</g>
-		<g class="st27">
-
-				<rect x="372.7" y="332" transform="matrix(1 -2.849729e-03 2.849729e-03 1 -0.9499 1.065)" class="st28" width="1.1" height="3.8"/>
-		</g>
-		<g class="st29">
-
-				<linearGradient id="SVGID_24_" gradientUnits="userSpaceOnUse" x1="404.6429" y1="261.1703" x2="404.6429" y2="329.4081" gradientTransform="matrix(-1 0 0 1 766.525 0)">
-				<stop  offset="0" style="stop-color:#22A3EC;stop-opacity:0"/>
-				<stop  offset="0.7151" style="stop-color:#22A3EC"/>
-				<stop  offset="0.986" style="stop-color:#22A3EC;stop-opacity:0"/>
-			</linearGradient>
-			<polygon class="st30" points="361.5,329.4 361.2,261.2 362.3,261.2 362.6,329.4 			"/>
-		</g>
-		<g class="st31">
-
-				<rect x="361.5" y="333.4" transform="matrix(1 -2.850099e-03 2.850099e-03 1 -0.954 1.0332)" class="st28" width="1.1" height="3.8"/>
-		</g>
-		<g class="st32">
-
-				<linearGradient id="SVGID_25_" gradientUnits="userSpaceOnUse" x1="415.8265" y1="264.5849" x2="415.8265" y2="332.8227" gradientTransform="matrix(-1 0 0 1 766.525 0)">
-				<stop  offset="0" style="stop-color:#22A3EC;stop-opacity:0"/>
-				<stop  offset="0.4637" style="stop-color:#22A3EC"/>
-				<stop  offset="0.8966" style="stop-color:#22A3EC;stop-opacity:0"/>
-			</linearGradient>
-			<polygon class="st33" points="350.3,332.8 350,264.6 351.1,264.6 351.4,332.8 			"/>
-		</g>
-		<g class="st34">
-
-				<rect x="350.3" y="336.8" transform="matrix(1 -2.849729e-03 2.849729e-03 1 -0.9637 1.0012)" class="st28" width="1.1" height="3.8"/>
-		</g>
-		<g class="st32">
-
-				<linearGradient id="SVGID_26_" gradientUnits="userSpaceOnUse" x1="427.0228" y1="269.0204" x2="427.0228" y2="337.2582" gradientTransform="matrix(-1 0 0 1 766.525 0)">
-				<stop  offset="0" style="stop-color:#22A3EC;stop-opacity:0"/>
-				<stop  offset="0.2737" style="stop-color:#22A3EC"/>
-				<stop  offset="0.8575" style="stop-color:#22A3EC;stop-opacity:0"/>
-			</linearGradient>
-			<polygon class="st35" points="339.1,337.3 338.8,269 339.9,269 340.2,337.3 			"/>
-		</g>
-		<g class="st34">
-
-				<rect x="339.1" y="341.2" transform="matrix(1 -2.849729e-03 2.849729e-03 1 -0.9764 0.9693)" class="st28" width="1.1" height="3.8"/>
-		</g>
-		<g>
-
-				<linearGradient id="SVGID_27_" gradientUnits="userSpaceOnUse" x1="438.2064" y1="274.4633" x2="438.2064" y2="342.7011" gradientTransform="matrix(-1 0 0 1 766.525 0)">
-				<stop  offset="0.2011" style="stop-color:#22A3EC;stop-opacity:0"/>
-				<stop  offset="0.6313" style="stop-color:#22A3EC"/>
-				<stop  offset="0.986" style="stop-color:#22A3EC;stop-opacity:0"/>
-			</linearGradient>
-			<polygon class="st36" points="327.9,342.7 327.6,274.5 328.7,274.5 329,342.7 			"/>
-		</g>
-		<g class="st34">
-
-				<rect x="327.9" y="346.7" transform="matrix(1 -2.849729e-03 2.849729e-03 1 -0.9919 0.9375)" class="st28" width="1.1" height="3.8"/>
-		</g>
-		<g>
-
-				<linearGradient id="SVGID_28_" gradientUnits="userSpaceOnUse" x1="449.39" y1="280.9203" x2="449.39" y2="349.1581" gradientTransform="matrix(-1 0 0 1 766.525 0)">
-				<stop  offset="0.1341" style="stop-color:#22A3EC;stop-opacity:0"/>
-				<stop  offset="0.7095" style="stop-color:#22A3EC"/>
-				<stop  offset="1" style="stop-color:#22A3EC;stop-opacity:0"/>
-			</linearGradient>
-			<polygon class="st37" points="316.7,349.2 316.5,280.9 317.5,280.9 317.8,349.2 			"/>
-		</g>
-		<g class="st38">
-
-				<rect x="316.7" y="353.1" transform="matrix(1 -2.849729e-03 2.849729e-03 1 -1.0104 0.9056)" class="st28" width="1.1" height="3.8"/>
-		</g>
-		<g>
-			<linearGradient id="SVGID_29_" gradientUnits="userSpaceOnUse" x1="305.9382" y1="287.3847" x2="305.9382" y2="355.6225">
-				<stop  offset="0.2011" style="stop-color:#22A3EC;stop-opacity:0"/>
-				<stop  offset="0.6313" style="stop-color:#22A3EC"/>
-				<stop  offset="0.986" style="stop-color:#22A3EC;stop-opacity:0"/>
-			</linearGradient>
-			<polygon class="st39" points="305.5,355.6 305.3,287.4 306.3,287.4 306.6,355.6 			"/>
-		</g>
-		<g class="st38">
-
-				<rect x="305.5" y="359.6" transform="matrix(1 -2.849729e-03 2.849729e-03 1 -1.0288 0.8737)" class="st28" width="1.1" height="3.8"/>
-		</g>
-		<g>
-			<linearGradient id="SVGID_30_" gradientUnits="userSpaceOnUse" x1="294.7542" y1="293.8412" x2="294.7542" y2="362.0795">
-				<stop  offset="0" style="stop-color:#22A3EC;stop-opacity:0"/>
-				<stop  offset="0.2737" style="stop-color:#22A3EC"/>
-				<stop  offset="0.8575" style="stop-color:#22A3EC;stop-opacity:0"/>
-			</linearGradient>
-			<polygon class="st40" points="294.3,362.1 294.1,293.8 295.2,293.8 295.4,362.1 			"/>
-		</g>
-		<g class="st41">
-
-				<rect x="294.4" y="366" transform="matrix(1 -2.590665e-03 2.590665e-03 1 -0.9522 0.7652)" class="st28" width="1.1" height="3.8"/>
-		</g>
-		<g>
-
-				<linearGradient id="SVGID_31_" gradientUnits="userSpaceOnUse" x1="482.9671" y1="300.3056" x2="482.9671" y2="368.5434" gradientTransform="matrix(-1 0 0 1 766.525 0)">
-				<stop  offset="0" style="stop-color:#22A3EC;stop-opacity:0"/>
-				<stop  offset="0.4637" style="stop-color:#22A3EC"/>
-				<stop  offset="0.986" style="stop-color:#22A3EC;stop-opacity:0"/>
-			</linearGradient>
-			<polygon class="st42" points="283.2,368.5 282.9,300.3 284,300.3 284.2,368.5 			"/>
-		</g>
-		<g class="st41">
-
-				<rect x="283.2" y="372.5" transform="matrix(1 -2.849729e-03 2.849729e-03 1 -1.0657 0.81)" class="st28" width="1.1" height="3.8"/>
-		</g>
-		<linearGradient id="SVGID_32_" gradientUnits="userSpaceOnUse" x1="272.3743" y1="305.7839" x2="272.3743" y2="363.3116">
-			<stop  offset="0" style="stop-color:#CCEC22;stop-opacity:0"/>
-			<stop  offset="0.7467" style="stop-color:#CCEC22;stop-opacity:0.92"/>
-		</linearGradient>
-		<polygon class="st43" points="272,375 271.7,306.8 272.7,306.8 273,375 		"/>
-		<g class="st41">
-
-				<rect x="272" y="379" transform="matrix(1 -2.850099e-03 2.850099e-03 1 -1.0843 0.7783)" class="st28" width="1.1" height="3.8"/>
-		</g>
-		<g>
-
-				<linearGradient id="SVGID_33_" gradientUnits="userSpaceOnUse" x1="505.347" y1="313.227" x2="505.347" y2="381.4648" gradientTransform="matrix(-1 0 0 1 766.525 0)">
-				<stop  offset="0" style="stop-color:#22A3EC;stop-opacity:0"/>
-				<stop  offset="0.4637" style="stop-color:#22A3EC"/>
-				<stop  offset="0.986" style="stop-color:#22A3EC;stop-opacity:0"/>
-			</linearGradient>
-			<polygon class="st44" points="260.8,381.5 260.5,313.2 261.6,313.2 261.9,381.5 			"/>
-		</g>
-		<g class="st41">
-
-				<rect x="260.8" y="385.4" transform="matrix(1 -2.849729e-03 2.849729e-03 1 -1.1027 0.7463)" class="st28" width="1.1" height="3.8"/>
-		</g>
-		<g>
-
-				<linearGradient id="SVGID_34_" gradientUnits="userSpaceOnUse" x1="516.5311" y1="319.684" x2="516.5311" y2="387.9218" gradientTransform="matrix(-1 0 0 1 766.525 0)">
-				<stop  offset="0" style="stop-color:#22A3EC;stop-opacity:0"/>
-				<stop  offset="0.4637" style="stop-color:#22A3EC"/>
-				<stop  offset="0.986" style="stop-color:#22A3EC;stop-opacity:0"/>
-			</linearGradient>
-			<polygon class="st45" points="249.6,387.9 249.3,319.7 250.4,319.7 250.7,387.9 			"/>
-		</g>
-		<g class="st34">
-
-				<rect x="249.6" y="391.9" transform="matrix(1 -2.849729e-03 2.849729e-03 1 -1.1211 0.7144)" class="st28" width="1.1" height="3.8"/>
-		</g>
-		<g>
-
-				<linearGradient id="SVGID_35_" gradientUnits="userSpaceOnUse" x1="527.7279" y1="326.1483" x2="527.7279" y2="394.3861" gradientTransform="matrix(-1 0 0 1 766.525 0)">
-				<stop  offset="0" style="stop-color:#22A3EC;stop-opacity:0"/>
-				<stop  offset="0.4637" style="stop-color:#22A3EC"/>
-				<stop  offset="0.986" style="stop-color:#22A3EC;stop-opacity:0"/>
-			</linearGradient>
-			<polygon class="st46" points="238.4,394.4 238.1,326.2 239.2,326.1 239.5,394.4 			"/>
-		</g>
-		<g class="st34">
-
-				<rect x="238.4" y="398.3" transform="matrix(1 -2.849729e-03 2.849729e-03 1 -1.1396 0.6826)" class="st28" width="1.1" height="3.8"/>
-		</g>
-	</g>
-	<linearGradient id="SVGID_36_" gradientUnits="userSpaceOnUse" x1="237.282" y1="346.8969" x2="502.2392" y2="346.8969">
-		<stop  offset="0" style="stop-color:#22A3EC"/>
-		<stop  offset="0.3141" style="stop-color:#4C82E7;stop-opacity:0.5424"/>
-		<stop  offset="0.6865" style="stop-color:#8258E1;stop-opacity:0"/>
-	</linearGradient>
-	<path class="st47" d="M423.3,303.9v43.4l-7.6,0.1c-25.7-13.3-56.5-12.6-81.7,1.9l-46,26.5l-50.8,26.4l0.2-12c0,0,23-6.2,34.1-28.9
-		c11.2-22.7,24.5-21.4,29.5-30.4c5-9,10.9-37.5,23-39.1c12.1-1.6,18.9,10.9,27,23.3c8.1,12.4,22.6,22.4,34.4,6.6
-		C397.2,305.8,410.8,303.1,423.3,303.9z"/>
-	<g>
-		<linearGradient id="SVGID_37_" gradientUnits="userSpaceOnUse" x1="236.3896" y1="340.8758" x2="424.3628" y2="340.8758">
-			<stop  offset="0" style="stop-color:#E8CCF0;stop-opacity:0.2"/>
-			<stop  offset="0.3855" style="stop-color:#E8CCF0"/>
-			<stop  offset="0.454" style="stop-color:#E1C4EF;stop-opacity:0.8504"/>
-			<stop  offset="0.5602" style="stop-color:#CEAEEC;stop-opacity:0.6186"/>
-			<stop  offset="0.6907" style="stop-color:#AE8BE8;stop-opacity:0.3336"/>
-			<stop  offset="0.8394" style="stop-color:#8359E1;stop-opacity:9.034276e-03"/>
-			<stop  offset="0.8436" style="stop-color:#8258E1;stop-opacity:0"/>
-		</linearGradient>
-		<path class="st48" d="M237.4,391.2c-0.5,0-0.9-0.3-1-0.8c-0.2-0.6,0.2-1.1,0.7-1.3c0.2-0.1,22.6-6.4,33.5-28.3
-			c7.1-14.3,14.9-19.2,21.1-23.1c3.7-2.3,6.6-4.1,8.4-7.3c1.3-2.4,2.8-6.3,4.4-10.9c4.4-12.3,10-27.6,19.3-28.8
-			c11.8-1.5,18.7,9.3,26.1,20.8c0.6,1,1.3,2,1.9,3c5.7,8.7,12.9,14.1,19.4,14.3c4.8,0.2,9.3-2.4,13.2-7.7
-			c13.2-17.7,28.5-18.8,38.9-18.2c0.6,0,1,0.5,1,1.1c0,0.6-0.5,1-1.1,1c-9.9-0.6-24.5,0.4-37,17.3c-4.4,5.9-9.4,8.7-15,8.6
-			c-7.2-0.2-15.1-5.9-21.1-15.2c-0.6-1-1.3-2-1.9-3c-7.3-11.4-13.6-21.2-24.1-19.8c-8.1,1-13.6,16.3-17.6,27.4
-			c-1.7,4.6-3.1,8.6-4.5,11.2c-2,3.7-5.3,5.7-9.1,8.1c-6.1,3.8-13.6,8.5-20.4,22.3c-11.3,22.8-34.6,29.3-34.8,29.4
-			C237.6,391.2,237.5,391.2,237.4,391.2z"/>
-	</g>
-	<linearGradient id="SVGID_38_" gradientUnits="userSpaceOnUse" x1="342.2651" y1="479.428" x2="255.8897" y2="436.9172">
-		<stop  offset="0" style="stop-color:#1C1C23"/>
-		<stop  offset="0.7663" style="stop-color:#2B264C;stop-opacity:0"/>
-	</linearGradient>
-	<polygon class="st49" points="338.9,463.1 331.1,452.1 258.2,437.8 248.8,455.2 317.9,468.3 313.9,462 	"/>
-	<linearGradient id="SVGID_39_" gradientUnits="userSpaceOnUse" x1="432.6669" y1="459.3523" x2="350.5956" y2="418.9599">
-		<stop  offset="0" style="stop-color:#1C1C23"/>
-		<stop  offset="0.7663" style="stop-color:#2B264C;stop-opacity:0"/>
-	</linearGradient>
-	<polygon class="st50" points="429.3,444.2 427.3,435.3 363.8,425.6 343.6,436.9 	"/>
-	<g class="st51">
-		<g>
-			<path class="st52" d="M240.4,413c-0.2,0-0.4-0.1-0.5-0.3c-0.1-0.3-0.1-0.6,0.2-0.7l27.8-16c0.3-0.2,0.6-0.1,0.7,0.2
-				c0.1,0.3,0.1,0.6-0.2,0.7l-27.8,16C240.6,413,240.5,413,240.4,413z"/>
-		</g>
-		<g>
-			<path class="st52" d="M240.4,418.1c-0.2,0-0.4-0.1-0.5-0.3c0-0.1-0.1-0.2-0.1-0.3c0-0.2,0.1-0.4,0.3-0.5l17.2-9.9
-				c0.3-0.1,0.6-0.1,0.7,0.2c0,0.1,0.1,0.2,0.1,0.3c0,0.2-0.1,0.4-0.3,0.5l-17.2,9.9C240.6,418.1,240.5,418.1,240.4,418.1z"/>
-		</g>
-	</g>
-	<g class="st51">
-		<g>
-			<path class="st52" d="M451.1,282.5c-0.1,0-0.2,0-0.3-0.1l-27.8-16c-0.3-0.1-0.3-0.5-0.2-0.7c0.1-0.3,0.5-0.4,0.7-0.2l27.8,16
-				c0.3,0.1,0.3,0.5,0.2,0.7C451.5,282.4,451.3,282.5,451.1,282.5z"/>
-		</g>
-		<g>
-			<path class="st52" d="M451.1,287.6c-0.1,0-0.2,0-0.3-0.1l-17.2-9.9c-0.2-0.1-0.3-0.3-0.3-0.5c0-0.1,0-0.2,0.1-0.3
-				c0.1-0.3,0.5-0.3,0.7-0.2l17.2,9.9c0.2,0.1,0.3,0.3,0.3,0.5c0,0.1,0,0.2-0.1,0.3C451.4,287.5,451.3,287.6,451.1,287.6z"/>
-		</g>
-	</g>
-	<g>
-
-			<radialGradient id="SVGID_40_" cx="484.1053" cy="356.8961" r="14.2722" gradientTransform="matrix(-0.4933 0.8699 0.5131 0.2909 328.6372 -168.0508)" gradientUnits="userSpaceOnUse">
-			<stop  offset="0" style="stop-color:#320D4F;stop-opacity:0.5"/>
-			<stop  offset="0.1775" style="stop-color:#503946;stop-opacity:0.5887"/>
-			<stop  offset="0.5826" style="stop-color:#929833;stop-opacity:0.7913"/>
-			<stop  offset="0.8656" style="stop-color:#BCD527;stop-opacity:0.9328"/>
-			<stop  offset="1" style="stop-color:#CCEC22"/>
-		</radialGradient>
-		<path class="st53" d="M272.9,344.8c-5.8,3.4-10.5,11.5-10.5,18.2c0,6.7,4.8,9.4,10.6,6c5.8-3.4,10.5-11.5,10.5-18.2
-			C283.5,344.1,278.7,341.4,272.9,344.8L272.9,344.8z"/>
-
-			<radialGradient id="SVGID_41_" cx="484.109" cy="356.8975" r="4.638" gradientTransform="matrix(-0.5108 0.8597 0.5852 0.3477 311.3646 -183.3821)" gradientUnits="userSpaceOnUse">
-			<stop  offset="0" style="stop-color:#320D4F;stop-opacity:0.4"/>
-			<stop  offset="8.102732e-03" style="stop-color:#330F4F;stop-opacity:0.4031"/>
-			<stop  offset="0.375" style="stop-color:#746D3C;stop-opacity:0.5433"/>
-			<stop  offset="0.6723" style="stop-color:#A3B12E;stop-opacity:0.6569"/>
-			<stop  offset="0.8857" style="stop-color:#C1DC25;stop-opacity:0.7385"/>
-			<stop  offset="0.9944" style="stop-color:#CCEC22;stop-opacity:0.78"/>
-		</radialGradient>
-		<path class="st54" d="M272.9,352.3c-2.2,1.3-4,4.4-4,7c0,2.5,1.8,3.6,4,2.3c2.2-1.3,4-4.4,4-6.9C277,352,275.2,351,272.9,352.3
-			L272.9,352.3z"/>
-		<path class="st55" d="M272.9,355c0.9-0.5,1.7-0.1,1.7,1c0,1.1-0.7,2.4-1.7,2.9c-0.9,0.5-1.7,0.1-1.7-1
-			C271.3,356.8,272,355.5,272.9,355L272.9,355z"/>
-	</g>
-	<linearGradient id="SVGID_42_" gradientUnits="userSpaceOnUse" x1="444.1624" y1="354.3044" x2="400.0417" y2="278.2922">
-		<stop  offset="0" style="stop-color:#CCEC22"/>
-		<stop  offset="3.531903e-02" style="stop-color:#CADD31;stop-opacity:0.935"/>
-		<stop  offset="0.2178" style="stop-color:#C19379;stop-opacity:0.5991"/>
-		<stop  offset="0.3692" style="stop-color:#BB5DAE;stop-opacity:0.3204"/>
-		<stop  offset="0.4819" style="stop-color:#B73CCF;stop-opacity:0.113"/>
-		<stop  offset="0.5433" style="stop-color:#B52FDB;stop-opacity:0"/>
-	</linearGradient>
-	<path class="st56" d="M429.3,310.3c-8.8-5.1-15.9-1-15.9,9.1c0,10.1,7.1,22.3,15.8,27.4c8.8,5.1,15.9,1,15.9-9.1
-		C445.1,327.6,438,315.4,429.3,310.3L429.3,310.3z"/>
-	<g>
-		<linearGradient id="SVGID_43_" gradientUnits="userSpaceOnUse" x1="445.5641" y1="356.7183" x2="412.8677" y2="300.388">
-			<stop  offset="0" style="stop-color:#CCEC22"/>
-			<stop  offset="6.500638e-02" style="stop-color:#CADD31;stop-opacity:0.935"/>
-			<stop  offset="0.4009" style="stop-color:#C19379;stop-opacity:0.5991"/>
-			<stop  offset="0.6796" style="stop-color:#BB5DAE;stop-opacity:0.3204"/>
-			<stop  offset="0.887" style="stop-color:#B73CCF;stop-opacity:0.113"/>
-			<stop  offset="1" style="stop-color:#B52FDB;stop-opacity:0"/>
-		</linearGradient>
-		<path class="st57" d="M439.4,358.3c-3.2,0-6.8-1.1-10.4-3.2c-12.7-7.3-23-25.1-22.9-39.7c0-7.1,2.5-12.5,6.9-15
-			c4.5-2.6,10.4-2,16.6,1.6c12.7,7.3,23,25.1,22.9,39.7c0,7.1-2.5,12.5-6.9,15C443.7,357.8,441.6,358.3,439.4,358.3z M419.1,299.7
-			c-2.1,0-4,0.5-5.7,1.5c-4.2,2.4-6.4,7.5-6.5,14.3c0,14.3,10.1,31.8,22.5,39c6,3.4,11.5,4,15.7,1.6c4.1-2.4,6.4-7.4,6.5-14.3
-			c0-14.3-10-31.8-22.5-39l0,0C425.5,300.7,422.1,299.7,419.1,299.7z"/>
-	</g>
-	<g>
-		<path class="st58" d="M341.5,460.5c0,0,0.6,3.4-4.5,3.1c-2.7-0.2-10.1-9.5-9.5-11.2c0.6-1.7,3.8-0.8,5.2,0.3L341.5,460.5z"/>
-		<path class="st58" d="M321.7,464.5c0,0,1.5,5.3-3.5,4.3c-5.1-1.1-12.8-4.6-12.9-8.1c-0.1-3.4,8,0,8,0L321.7,464.5z"/>
-		<path class="st59" d="M284.8,365.7l-3,5.3c-2.4-1.5-5.3-3.2-6.8-3.9c-2-0.8-1-5.7-1-5.7c-0.5-0.8-2.5-4.2-2.6-4.4l3,2.3
-			C277.2,362.1,282,364.4,284.8,365.7z"/>
-		<path class="st59" d="M324.5,350.8c-0.4-2-0.6-3-0.3-5.4c0,0-7.2-4.5,0.2-12.5l8.9,5c-1.5,5.3-2.9,10.6-2.2,13.7
-			c-2.1,1.6-4.1,1.8-6.1,0.5C324.7,351.9,324.5,351.4,324.5,350.8z"/>
-		<path class="st58" d="M331.4,347.8c2.6-4.3,3.6-1.8,6.4-7.2c2.5-4.8-0.8-8.8-3.9-9.6c0,0-2.8-3.2-6.5-3.4
-			c-3.5-0.1-6.8,3.4-3.9,7.4c1.5,2-1,2.7,1,3.6c2.8,1.2,0.2,6.9,4.8,8.2L331.4,347.8z"/>
-		<linearGradient id="SVGID_44_" gradientUnits="userSpaceOnUse" x1="279.1903" y1="469.3949" x2="387.2656" y2="377.2189">
-			<stop  offset="0" style="stop-color:#22A0E9"/>
-			<stop  offset="0.2581" style="stop-color:#4F7DE4"/>
-			<stop  offset="0.6016" style="stop-color:#8453DD"/>
-			<stop  offset="0.8595" style="stop-color:#A539D9"/>
-			<stop  offset="1" style="stop-color:#B22FD8"/>
-		</linearGradient>
-		<path class="st60" d="M341.5,460.5c0,0-5.4,2.8-8.8-6.2l-0.5-9.5l-3.1-33.4l-5.2,18l-1.5,8.4c0,0-0.1,0-0.1-0.1l0.2,26.6
-			c-4.4,3.7-9.1-1.9-9.1-1.9l-1.3-31c-0.1-0.1-0.2-0.1-0.3-0.2l0.3-3.3l3-33.4l0.1,1c0,0,21,0.6,24.3-7l0.2-0.8c0,0,0,0,0,0
-			l-0.3,39.4l1.6,23.1c0,0.4,0,0.7-0.1,1L341.5,460.5z"/>
-		<linearGradient id="SVGID_45_" gradientUnits="userSpaceOnUse" x1="317.4543" y1="402.5235" x2="317.8119" y2="357.8183">
-			<stop  offset="0" style="stop-color:#282447"/>
-			<stop  offset="1" style="stop-color:#565499"/>
-		</linearGradient>
-		<path class="st61" d="M353.6,370.8c-4.8-12.3-11.2-21.7-17.9-21.8c-1.7,0-3.9,0.2-6.2,0.4c-6.5,0.8-12.9,2.5-18.8,5.3
-			c-5.3,2.5-13.6,16.6-26,10.7l-3.5,6c9.2,9.1,25.4,1.1,31.2-1.5l2.5,25.6c0,0,21,0.6,24.3-7l0.7-2.8
-			C340.1,385.7,356.6,378.6,353.6,370.8z M343.2,375.1l-2.7,2.3v-12.1l3.8,4.7C345.8,371.8,345,373.8,343.2,375.1z"/>
-	</g>
-	<g>
-		<linearGradient id="SVGID_46_" gradientUnits="userSpaceOnUse" x1="455.085" y1="341.5702" x2="430.8549" y2="299.8258">
-			<stop  offset="0" style="stop-color:#CCEC22"/>
-			<stop  offset="6.500638e-02" style="stop-color:#CADD31;stop-opacity:0.935"/>
-			<stop  offset="0.4009" style="stop-color:#C19379;stop-opacity:0.5991"/>
-			<stop  offset="0.6796" style="stop-color:#BB5DAE;stop-opacity:0.3204"/>
-			<stop  offset="0.887" style="stop-color:#B73CCF;stop-opacity:0.113"/>
-			<stop  offset="1" style="stop-color:#B52FDB;stop-opacity:0"/>
-		</linearGradient>
-		<path class="st62" d="M452,343.1C452,343.1,452,343.1,452,343.1c-0.8,0-1.4-0.6-1.4-1.4c0-14-9.8-31.1-22-38.1
-			c-0.7-0.4-0.9-1.3-0.5-1.9c0.4-0.7,1.3-0.9,1.9-0.5c13,7.5,23.5,25.7,23.4,40.6C453.4,342.5,452.8,343.1,452,343.1z"/>
-	</g>
-
-		<linearGradient id="SVGID_47_" gradientUnits="userSpaceOnUse" x1="-6456.9609" y1="385.2714" x2="-6438.8169" y2="199.292" gradientTransform="matrix(1 0 0 1 6671.7744 0)">
-		<stop  offset="0" style="stop-color:#D1F122"/>
-		<stop  offset="8.435863e-02" style="stop-color:#CFDD36"/>
-		<stop  offset="0.4133" style="stop-color:#C6937E"/>
-		<stop  offset="0.6862" style="stop-color:#BF5DB3"/>
-		<stop  offset="0.8893" style="stop-color:#BB3CD4"/>
-		<stop  offset="1" style="stop-color:#BA2FE0"/>
-	</linearGradient>
-	<path class="st63" d="M198,344.8l-0.1-31.1c0-2,1-3.9,2.5-4.9L241,283c1.9-1.2,4.3,0.3,4.3,2.8l0.1,31.1c0,2-1,3.9-2.5,4.9
-		l-40.6,25.9C200.4,348.8,198,347.3,198,344.8z"/>
-	<g>
-		<path class="st58" d="M427.2,440.9c0,0-1.2,4.2,2.7,3.3s10-3.6,10.1-6.3c0.1-2.7-6.2,0-6.2,0L427.2,440.9z"/>
-		<path class="st64" d="M432.9,338.7c0,0,3.5,0.1,6.6-1.7l-0.3-1c0,0-2.5,0.8-2.7,0.5s-0.7-2.1,5.1-5.9l-0.3-1l-5,1.8
-			c0,0-3.2-0.7-3.5,0.2l-2,3.5C432.1,336.1,432.9,337.2,432.9,338.7z"/>
-		<linearGradient id="SVGID_48_" gradientUnits="userSpaceOnUse" x1="443.4018" y1="333.7012" x2="419.1606" y2="343.47">
-			<stop  offset="0" style="stop-color:#BA2FE0"/>
-			<stop  offset="0.2167" style="stop-color:#AD3AE1"/>
-			<stop  offset="0.6122" style="stop-color:#8C56E5"/>
-			<stop  offset="1" style="stop-color:#6676EA"/>
-		</linearGradient>
-		<path class="st65" d="M431.3,333.8c0,0-11.4,6.1-17.4,7.6c0.1,0.2,0.2,0.3,0.3,0.5c0.3,0.5,0.6,1.1,0.8,1.6
-			c0.4,0.9,0.8,1.7,1.2,2.6c0.4,0.9,0.9,1.9,1.1,3c6.3-2.4,13.8-8.1,16.4-10.8C435.9,336,431.3,333.8,431.3,333.8z"/>
-		<path class="st58" d="M416.1,434.1l0.4,0.1c1.2,0.4,1.6,2,0.7,2.9c-2.3,2.4-5,4.3-8.4,5.4c-0.6,0.2-1.3,0.2-1.9,0l-1.1-0.3
-			c-1.1-0.4-1.7-1.6-1.4-2.7l1.7-1.4l8.6-3.9C415.1,434,415.6,434,416.1,434.1z"/>
-		<path class="st66" d="M412.9,414.5l-3.4,23.3c-2.1,4.1-4.7,2.5-4.7,2.5c-0.1-1.2-0.5-16.2-0.8-26.8
-			C406.8,413.9,409.8,414.3,412.9,414.5z"/>
-		<path class="st66" d="M433.2,413.9l-1.6,25.8c-0.7,1.9-2.4,2.8-4,2.1l-3.3-27C427.3,414.6,430.3,414.3,433.2,413.9z"/>
-		<path class="st64" d="M410.3,329.8c0,0,0.5,6.3-0.9,7c-1.4,0.6,7.2,1,7.2,1l0.8-4.7c0,0,6.7,1.4,4-11.4
-			C418.7,308.9,410.3,329.8,410.3,329.8z"/>
-		<linearGradient id="SVGID_49_" gradientUnits="userSpaceOnUse" x1="417.8302" y1="424.6173" x2="418.3395" y2="360.9489">
-			<stop  offset="0" style="stop-color:#282447"/>
-			<stop  offset="1" style="stop-color:#565499"/>
-		</linearGradient>
-		<path class="st67" d="M434.4,413.7c-10,1.6-20.9,1.2-30.9-0.3c-0.1-5.3-2.7-28.9-1.4-35.2c0.2-1.1,0.5-2,0.8-2.8
-			c6.8-0.5,16.4,6.6,20.1-0.4c0.7,4,2,8.4,4.1,12.9c5,10.6,6.6,18.9,6.6,18.9S434.1,409.9,434.4,413.7z"/>
-
-			<linearGradient id="SVGID_50_" gradientUnits="userSpaceOnUse" x1="228.785" y1="576.8905" x2="232.4312" y2="539.5176" gradientTransform="matrix(0.9656 -0.2599 0.2599 0.9656 46.6773 -155.8072)">
-			<stop  offset="0" style="stop-color:#D1F122"/>
-			<stop  offset="8.435863e-02" style="stop-color:#CFDD36"/>
-			<stop  offset="0.4133" style="stop-color:#C6937E"/>
-			<stop  offset="0.6862" style="stop-color:#BF5DB3"/>
-			<stop  offset="0.8893" style="stop-color:#BB3CD4"/>
-			<stop  offset="1" style="stop-color:#BA2FE0"/>
-		</linearGradient>
-		<path class="st68" d="M407.8,330.3c0,0,5.2,2.6,8.6-1.3c0,0-1.9-5.1,2.2-4.5c0,0,5.7-4.1,2.9-6.4c-2.5-2-6.3-2-9.4-0.7
-			c-0.8,0.3-1.5,0.9-2,1.6C406.8,323.2,405.5,327,407.8,330.3z"/>
-
-			<linearGradient id="SVGID_51_" gradientUnits="userSpaceOnUse" x1="220.382" y1="444.7877" x2="285.8488" y2="444.7877" gradientTransform="matrix(0.9951 -9.847216e-02 9.847216e-02 0.9951 119.2184 -61.2363)">
-			<stop  offset="0" style="stop-color:#6676EA"/>
-			<stop  offset="0.3878" style="stop-color:#8C56E5"/>
-			<stop  offset="0.7833" style="stop-color:#AD3AE1"/>
-			<stop  offset="1" style="stop-color:#BA2FE0"/>
-		</linearGradient>
-		<path class="st69" d="M424.9,345.4C424.9,345.4,424.9,345.4,424.9,345.4c0.1-1.3-0.4-2.6-1.4-3.4c-4-3.2-13-8.4-20-6
-			c-1.4,0.5-1.7,12.8-1.5,14.6c2.2,14.9,1.9,19.9,0.8,24.9c6.9-0.6,16.6,6.7,20.2-0.5c-1.6-10.1,1.4-16.9,1.4-16.9
-			S424.7,349.6,424.9,345.4z"/>
-
-			<linearGradient id="SVGID_52_" gradientUnits="userSpaceOnUse" x1="409.0752" y1="445.7468" x2="437.3948" y2="445.7468" gradientTransform="matrix(0.9951 -9.847216e-02 9.847216e-02 0.9951 -36.4767 -45.8298)">
-			<stop  offset="0" style="stop-color:#9C48E4"/>
-			<stop  offset="0.309" style="stop-color:#8F53E5"/>
-			<stop  offset="0.8737" style="stop-color:#6E6FE9"/>
-			<stop  offset="1" style="stop-color:#6676EA"/>
-		</linearGradient>
-		<path class="st70" d="M419.7,342.2c0.2-1.1,0.8-2.4,1.8-2.2c0.6,0.1,1,0.6,1.4,1.1c4.8,7.1,8.8,14.6,12.1,22.5
-			c0.9,2.2,1.7,4.7,0.5,6.8c-1.1,1.8-3.4,2.4-5.6,2.4s-4.2-0.5-6.3-0.1c0-1.3-0.1-2.7-0.1-4c1.4,0.5,3-0.3,3.6-1.6s0.4-2.9-0.4-4.1
-			c-1-1.5-2.4-1.7-3.7-2.7c-1.4-1-1.9-3.2-2.3-4.8C419.3,351.1,419,346.5,419.7,342.2z"/>
-		<path class="st64" d="M419.4,372.1c0.7,0.2,1.5,0.5,2.3,0.4c0.8-0.1,1.6-0.5,1.9-1.2c0.3-0.7,0.3-3.1-0.6-3.1
-			c-0.2,0-0.7,0.2-0.8,0.4c-0.2,0.5-0.1,1.2-0.5,1.6C420.8,371.2,419.3,370.5,419.4,372.1z"/>
-
-			<linearGradient id="SVGID_53_" gradientUnits="userSpaceOnUse" x1="-749.353" y1="117.4246" x2="-753.2183" y2="59.1229" gradientTransform="matrix(-0.988 -0.1542 -0.1542 0.988 -320.6753 122.1749)">
-			<stop  offset="0" style="stop-color:#CDED22"/>
-			<stop  offset="0.1777" style="stop-color:#C7BF4F"/>
-			<stop  offset="0.4378" style="stop-color:#C0828B"/>
-			<stop  offset="0.6588" style="stop-color:#BB55B7"/>
-			<stop  offset="0.8292" style="stop-color:#B739D2"/>
-			<stop  offset="0.9285" style="stop-color:#B62FDC"/>
-		</linearGradient>
-		<path class="st71" d="M408.8,344.9c-0.8,0.9-8.7,2.7-10-0.5c-1.3-3-0.2-4.1,1.7-5c1.7-0.9,1.4-3.6,1.1-5.5
-			c-0.5-2.5-0.4-5.7,0.9-8.5c1.7-3.6,3.6-4.2,7.1-4c3.6,0.2,2,3.4-0.1,5.1c-1.8,1.4-0.8,4.5,0.4,8.4
-			C411.5,340.2,410.1,343.5,408.8,344.9z"/>
-
-			<linearGradient id="SVGID_54_" gradientUnits="userSpaceOnUse" x1="-1380.7042" y1="326.9695" x2="-1380.6434" y2="319.3631" gradientTransform="matrix(-1 0 0 1 -970.6509 0)">
-			<stop  offset="0.1936" style="stop-color:#7D73CA"/>
-			<stop  offset="0.8746" style="stop-color:#6D6F80"/>
-		</linearGradient>
-		<path class="st72" d="M410.1,326.2c0.2-1.1-0.5-4.3-1.6-4.6c-1.1-0.3,1-0.7,1-0.7s1.7-0.9,2.2,2.2
-			C412.4,326.5,410.1,326.2,410.1,326.2z"/>
-	</g>
-</g>
-</svg>
diff --git a/layouts/partials/svgs/influxdbu.svg b/layouts/partials/svgs/influxdbu.svg
new file mode 100644
index 000000000..718ab9af2
--- /dev/null
+++ b/layouts/partials/svgs/influxdbu.svg
@@ -0,0 +1,15 @@
+<svg version="1.1" id="influxdbu" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"
+	 viewBox="0 0 77 74" style="enable-background:new 0 0 77 74;" xml:space="preserve">
+<path class="magenta" d="M77,26.8v20.4c-0.1,0.7-0.1,1.5-0.2,2.2c-0.5,2.5-1.7,4.5-3.5,6.1c-1.9,1.8-4.1,2.8-6.6,3
+	c-1.5,0.1-2.9,0-4.3,0.1v-6.6l3.1,0c0.4,0,0.7-0.1,1.1-0.1c2.3-0.5,3.8-2.4,3.8-4.8V26.8c0-0.4,0-0.7-0.1-1.1
+	c-0.5-2.2-2.4-3.6-4.8-3.6H25.3v-6.6h39.5c0.8,0,1.7,0,2.5,0.1c3.9,0.7,6.7,2.8,8.5,6.3C76.7,23.4,77,25.1,77,26.8z"/>
+<path class="magenta" d="M9.8,52.1h43v6.6H0.9c-0.1,0-0.1,0-0.3,0c-0.3,0-0.6-0.2-0.6-0.5c0-0.4,0.3-0.6,0.6-0.7
+	c1.6-0.4,2.5-1.6,2.6-3.3V20c0-1.7-0.8-2.9-2.7-3.4C0.3,16.5,0,16.4,0,16.2c0-0.3,0.1-0.7,0.7-0.7h15V22H9.8V52.1z"/>
+<path class="c1" d="M62.4,15.1v0.3h-6.6c0-0.1,0-0.1,0-0.2V12c0-0.6-0.1-1.3-0.3-1.9c-0.6-1.6-2.3-3-4.8-3H25.3V22v11.7h25.5
+	c0.3,0,0.4,0,1.1-0.1c2.1-0.3,3.8-2.1,3.9-4.3c0.1-1.5,0.1-3,0.1-4.5v-0.3h6.6V29c0,1.6-0.3,3.1-1,4.6c-0.6,1.3-1.4,2.4-2.4,3.3
+	l0.1,0.1c2.1,2.2,3.2,4.7,3.3,7.6c0.1,2.4,0,4.8,0,7.2v0.3v6.6v1.7c0,1.1,0,2.2-0.1,3.3c-0.2,2.3-1.2,4.3-2.7,6
+	c-2.3,2.5-5.3,3.8-8.8,3.8H16c-0.4,0-0.6-0.2-0.6-0.4c0-0.2,0.1-0.5,0.4-0.6c0.2-0.1,0.4-0.1,0.6-0.2c0.8-0.4,1.6-0.8,1.9-1.7
+	c0.3-0.6,0.3-1.1,0.3-1.7v-7.8h6.7V67h25.6c0.5,0,1.1-0.1,1.5-0.2c2.1-0.6,3.5-2.5,3.5-4.8V45.2c0,0,0-0.2-0.1-0.8
+	c-0.3-2.5-2.3-4.2-4.9-4.2H25.3v11.9h-6.7V4.8c-0.1-1.3-0.6-2.2-1.8-2.7c-0.3-0.1-0.9-0.3-1.1-0.4c-0.3-0.1-0.5-0.4-0.4-0.7
+	c0.1-0.4,0.6-0.4,0.5-0.4h35.4l0.1,0.1c3.2,0.1,5.8,1.4,7.9,3.5c1.9,2,2.9,4.3,3.1,6.9C62.5,12.4,62.4,13.7,62.4,15.1z"/>
+</svg>
diff --git a/layouts/partials/svgs/video-arrow.svg b/layouts/partials/svgs/video-arrow.svg
new file mode 100644
index 000000000..cd06af988
--- /dev/null
+++ b/layouts/partials/svgs/video-arrow.svg
@@ -0,0 +1,7 @@
+<svg version="1.1" id="video-arrow" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"
+	 viewBox="0 0 73 74" style="enable-background:new 0 0 73 74;" xml:space="preserve">
+<path class="c2" d="M6.1,63.7V10.6l53.2,26.5L6.1,63.7z"/>
+<path class="magenta" d="M18.2,57.6V30.2l6.1,3.1v21.4L18.2,57.6z"/>
+<path class="c1" d="M73,37.1L0,0.6v72.8L73,37.1z M59.3,37.1L18.2,57.6V30.2l6.1,3.1v14.6l21.5-10.7L12.3,20.4v40.3l-6.1,3.1V10.6
+	L59.3,37.1z"/>
+</svg>
diff --git a/layouts/shortcodes/cli/influxd-flags.html b/layouts/shortcodes/cli/influxd-flags.html
index 624c41ac8..2a9e7dd0d 100644
--- a/layouts/shortcodes/cli/influxd-flags.html
+++ b/layouts/shortcodes/cli/influxd-flags.html
@@ -5,8 +5,14 @@
 <ul>
 {{- range $flags -}}
 {{- $flagAnchor := replaceRE "--" "#" .flag -}}
-{{- if ge (float $currentVersion) .added -}}
-  <li>{{ if .nolink }}{{ .flag }}{{ else }}<a href="/influxdb/v{{ $currentVersion }}/reference/config-options/{{ $flagAnchor }}">{{ .flag }}</a>{{ end }}</li>
+{{- $removed := cond (isset . "removed") .removed 1000.0 -}}
+{{- $deprecated := cond (isset . "deprecated") true false -}}
+{{- $deprecatedVersion := cond $deprecated .deprecated 0.0 -}}
+{{- if and (ge (float $currentVersion) .added) (lt (float $currentVersion) $removed) -}}
+  <li>
+    {{ if .nolink }}{{ .flag }}{{ else }}<a href="/influxdb/v{{ $currentVersion }}/reference/config-options/{{ $flagAnchor }}">{{ .flag }}</a>{{ end }} 
+    {{ if and $deprecated (ge (float $currentVersion) $deprecatedVersion) }}<em style="opacity:.65;"> - (deprecated in InfluxDB {{ $deprecatedVersion }})</em>{{ end }}
+  </li>
 {{- end -}}
 {{- end -}}
 </ul>
diff --git a/layouts/shortcodes/cloud_regions.html b/layouts/shortcodes/cloud_regions.html
index 67798483d..dbb00a95e 100644
--- a/layouts/shortcodes/cloud_regions.html
+++ b/layouts/shortcodes/cloud_regions.html
@@ -10,17 +10,25 @@
     {{ $title := $scratch.Get "title" }}
     {{ $titleID := anchorize $title }}
     <h3 id="{{ $titleID }}">{{ $title }}</h3>
-    <table>
+    <table class="cloud-urls">
       <thead>
         <th align="left">Region</th>
         <th align="left">Location</th>
-        <th align="left">URL</th>
+        <th align="left">URL(s)</th>
       </thead>
       {{ range .regions }}
         <tr>
           <td {{ if .status }}class="{{ .status }}"{{ end }}>{{ .name }}</td>
           <td>{{ .location }}</td>
-          <td><a href="{{ .url }}">{{ .url }}</a></td>
+          <td>
+            {{ if .clusters }}
+              {{ range .clusters }}
+                <p><span class="cluster-name">{{ .name }}:</span> <a href="{{ .url }}">{{ .url }}</a></p>
+              {{ end }}
+            {{ else }}
+              <a href="{{ .url }}">{{ .url }}</a>
+            {{ end }}
+          </td>
         </tr>
       {{ end }}
     </table>
diff --git a/layouts/shortcodes/current-version-link.html b/layouts/shortcodes/current-version-link.html
new file mode 100644
index 000000000..31e0973c9
--- /dev/null
+++ b/layouts/shortcodes/current-version-link.html
@@ -0,0 +1,4 @@
+{{- $productPathData := findRE "[^/]+.*?" .Page.RelPermalink -}}
+{{- $currentVersion := index $productPathData 1 -}}
+{{- $currentVersionLink := replaceRE `\.` "%2e" $currentVersion  -}}
+{{ $currentVersionLink }}
\ No newline at end of file
diff --git a/layouts/shortcodes/current-version.html b/layouts/shortcodes/current-version.html
index 864b093cb..0fc82fe95 100644
--- a/layouts/shortcodes/current-version.html
+++ b/layouts/shortcodes/current-version.html
@@ -1,3 +1,5 @@
 {{- $productPathData := findRE "[^/]+.*?" .Page.RelPermalink -}}
 {{- $currentVersion := replaceRE "v" "" (index $productPathData 1) -}}
-{{ $currentVersion }}
\ No newline at end of file
+{{- $keep := .Get "keep" | default false -}}
+{{- $keepClass := cond ( $keep ) " keep" "" -}}
+<span class="current-version{{ $keepClass }}">{{ $currentVersion }}</span>
\ No newline at end of file
diff --git a/layouts/shortcodes/duplicate-oss.html b/layouts/shortcodes/duplicate-oss.html
index 311521e22..7f05b11f5 100644
--- a/layouts/shortcodes/duplicate-oss.html
+++ b/layouts/shortcodes/duplicate-oss.html
@@ -4,5 +4,5 @@
 
 {{ $page := .Site.GetPage $path }}
 {{ with $page }}
-  {{ .Content | replaceRE `\/influxdb\/v2\.[0-9]{1,2}\/` "/influxdb/cloud/" | safeHTML }}
+  {{ .Content | replaceRE `\/influxdb\/v2\.[0-9]{1,2}\/` "/influxdb/cloud/" | replaceRE `<span class="current-version">.*<\/span>` "Cloud" | safeHTML }}
 {{ end }}
diff --git a/layouts/shortcodes/html-diagram/data-retention.html b/layouts/shortcodes/html-diagram/data-retention.html
new file mode 100644
index 000000000..013fe3d60
--- /dev/null
+++ b/layouts/shortcodes/html-diagram/data-retention.html
@@ -0,0 +1,41 @@
+<div id="data-retention">
+  <div class="periods">
+    <p>4d</p>
+    <p>3d</p>
+    <p>2d</p>
+    <p>1d</p>
+    <p>0d</p>
+  </div>
+  <div class="timeline">
+    <div class="interval"></div>
+    <div class="interval"></div>
+    <div class="interval"></div>
+    <div class="interval"></div>
+  </div>
+  <div class="shard-groups">
+    <div class="shard-group deleted">
+      <p>Shard group</p>
+      <p class="shard">Shard</p>
+    </div>
+    <div class="shard-group">
+      <p>Shard group</p>
+      <p class="shard">Shard</p>
+    </div>
+    <div class="shard-group">
+      <p>Shard group</p>
+      <p class="shard">Shard</p>
+    </div>
+    <div class="shard-group">
+      <p>Shard group</p>
+      <p class="shard">Shard</p>
+    </div>
+  </div>
+  <div class="timeline">
+    <div class="one-quarter">
+      <p class="deleted-label all-caps">Deleted</p>
+    </div>
+    <div class="three-quarters border-left">
+      <p class=retention-label>3d retention period</p>
+    </div>
+  </div>
+</div>
\ No newline at end of file
diff --git a/layouts/shortcodes/telegraf/plugins.html b/layouts/shortcodes/telegraf/plugins.html
index c449468cb..29f1a55a9 100644
--- a/layouts/shortcodes/telegraf/plugins.html
+++ b/layouts/shortcodes/telegraf/plugins.html
@@ -13,7 +13,7 @@
   {{ if $supported }}
     <div class="plugin-card filter-item visible{{ if eq $minorVer $currentTelegrafVersion }} new{{ end }}" id="{{ .id }}" data-tags="{{ $type }} {{ lower $pluginTags }} {{ if eq $minorVer $currentTelegrafVersion }}new{{ end }} {{ if .deprecated }}deprecated{{ end }} ">
       <div class="info">
-        <h3 id="{{ .id }}">{{ .name }}</h3>
+        <h3 id="{{ $type }}-{{ .id }}">{{ .name }}</h3>
         {{ if in .tags "external"}}<p class="external">External</p>{{ end }}
         <p class="meta">
           Plugin ID: <code>{{ $type }}s.{{ .id }}</code><br/>
diff --git a/package.json b/package.json
index dc84b342e..ebcb5d9fc 100644
--- a/package.json
+++ b/package.json
@@ -6,8 +6,8 @@
   "license": "MIT",
   "devDependencies": {
     "autoprefixer": "^10.2.5",
-    "hugo-extended": "^0.83.1",
+    "hugo-extended": "^0.92.1",
     "postcss": "^8.2.13",
-    "postcss-cli": "^8.3.1"
+    "postcss-cli": "^9.1.0"
   }
 }
diff --git a/shared/text/api/v2.0/auth/oss/token-create.sh b/shared/text/api/v2.0/auth/oss/token-create.sh
index f5c106d91..3005d7665 100644
--- a/shared/text/api/v2.0/auth/oss/token-create.sh
+++ b/shared/text/api/v2.0/auth/oss/token-create.sh
@@ -13,18 +13,21 @@ curl -v --request POST \
     {
       "action": "read",
       "resource": {
+        "orgID": "'"${INFLUX_ORG_ID}"'",
         "type": "authorizations"
       }
     },
     {
       "action": "read",
       "resource": {
+        "orgID": "'"${INFLUX_ORG_ID}"'",
         "type": "buckets"
       }
     },
     {
       "action": "write",
       "resource": {
+        "orgID": "'"${INFLUX_ORG_ID}"'",
         "type": "buckets",
         "name": "iot-center" 
       }
diff --git a/shared/text/api/v2.0/auth/oss/tokens-create-with-user.sh b/shared/text/api/v2.0/auth/oss/tokens-create-with-user.sh
index 068cb8b49..2f7fda558 100644
--- a/shared/text/api/v2.0/auth/oss/tokens-create-with-user.sh
+++ b/shared/text/api/v2.0/auth/oss/tokens-create-with-user.sh
@@ -9,6 +9,7 @@
 #   c. Return the new token.
 ######################################################
 
+INFLUX_ORG_ID=YOUR_ORG_ID
 INFLUX_TOKEN=YOUR_API_TOKEN
 
 function create_token_with_user() {
@@ -25,7 +26,7 @@ function create_token_with_user() {
   
   jq --arg USER $1 '.users[0] // error("User missing")
     | {
-        "orgID": "YOUR_ORG_ID",
+        "orgID": "'"${INFLUX_ORG_ID}"'",
         "userID": .id,
         "description": $USER,
         "permissions": [
diff --git a/shared/text/bucket-schema/bucket-schema-type.sh b/shared/text/bucket-schema/bucket-schema-type.sh
index 02a07166c..9d9e807f3 100644
--- a/shared/text/bucket-schema/bucket-schema-type.sh
+++ b/shared/text/bucket-schema/bucket-schema-type.sh
@@ -1,3 +1,3 @@
 influx bucket create \
   --name my_schema_bucket \
-  --schema-type explicit
+  --schema-type explicit
\ No newline at end of file
diff --git a/static/fonts/icomoon-v2.eot b/static/fonts/icomoon-v2.eot
index dec1f1b9e..6be8b6309 100644
Binary files a/static/fonts/icomoon-v2.eot and b/static/fonts/icomoon-v2.eot differ
diff --git a/static/fonts/icomoon-v2.svg b/static/fonts/icomoon-v2.svg
index c64f3fd4b..2d78cafed 100644
--- a/static/fonts/icomoon-v2.svg
+++ b/static/fonts/icomoon-v2.svg
@@ -7,80 +7,80 @@
 <font-face units-per-em="1024" ascent="798.7800586510264" descent="-225.21994134897358" />
 <missing-glyph horiz-adv-x="1024" />
 <glyph unicode="&#x20;" horiz-adv-x="512.5004887585533" d="" />
-<glyph unicode="&#xe900;" glyph-name="influx-logo" d="M878.091 215.483l-70.863 308.513c-4.108 16.842-19.513 33.686-35.74 38.41l-323.507 99.414c-4.108 1.437-8.833 2.054-13.556 2.054-14.173 0-28.346-5.34-37.794-13.556l-232.103-215.465c-12.119-11.502-19.513-33.686-15.61-49.913l75.588-330.080c4.108-16.842 19.513-33.686 35.74-38.41l302.351-93.252c4.108-1.437 8.833-2.054 13.556-2.054 14.173 0 28.346 5.34 37.794 13.556l248.33 230.255c12.941 12.119 19.718 33.686 15.815 50.528zM481.050 588.081l221.422-68.194c8.833-2.671 8.833-6.779 0-8.833l-116.873-26.907c-8.833-2.054-20.95 2.054-26.907 8.011l-81.75 87.912c-6.572 7.394-4.725 10.887 4.108 8.011zM619.49 189.808c2.054-8.833-3.286-14.173-12.119-11.502l-239.704 74.356c-8.833 2.671-10.065 10.065-3.286 16.227l183.628 170.072c6.779 6.162 13.556 4.108 15.61-4.725l55.87-244.427zM224.503 407.945l194.516 180.959c6.779 6.162 16.842 6.162 23.621-0.617l97.977-105.371c6.162-6.779 6.162-16.842-0.617-23.621l-195.131-180.959c-6.779-6.162-16.842-6.162-23.621 0.617l-97.155 105.371c-6.367 6.779-5.545 17.459 0.41 23.621zM271.745 120.383l-51.35 226.147c-2.054 8.833 1.437 10.887 7.394 4.108l81.75-87.707c6.162-6.779 8.833-18.896 6.162-27.729l-35.123-114.819c-2.671-8.833-6.779-8.833-8.833 0zM556.638-11.279l-253.876 78.257c-8.833 2.671-13.556 12.119-10.887 20.95l42.518 137.004c2.671 8.833 12.119 13.556 20.95 10.887l253.055-78.257c8.833-2.671 13.556-12.119 10.887-20.95l-42.518-137.004c-1.849-8.833-11.297-13.556-20.13-10.887zM782.167 172.965l-170.072-157.337c-6.779-6.162-10.065-4.108-7.394 4.725l35.123 114.819c2.671 8.833 12.119 17.459 20.95 19.513l116.873 26.907c9.243 1.644 11.297-1.849 4.518-8.626zM801.065 206.856l-139.672-31.632c-8.833-2.054-17.459 3.286-19.513 12.119l-59.361 258.6c-2.054 8.833 3.286 17.459 12.119 19.513l139.672 31.632c8.833 2.054 17.459-3.286 19.513-12.119l59.361-258.6c2.054-8.833-3.286-17.664-12.119-19.513z" />
-<glyph unicode="&#xe901;" glyph-name="influx-logotype" horiz-adv-x="3001" d="M2813.175 106.826c-1.437-8.011 2.671-10.065 6.162-10.065h19.513c6.779 0 8.833 6.779 8.833 10.065v0l53.404 303.788c-38.41 14.173-82.982 21.567-113.383 21.567-88.527 0-124.267-35.123-139.672-121.599l-25.058-141.112c-1.437-8.833-2.054-16.842-2.054-24.238 0-40.464 23.004-55.253 64.906-55.253 47.242 0 94.484 22.184 132.278 54.636l-4.93-37.794zM2689.522 123.669c-20.335 0-30.4 5.34-30.4 26.292 0 5.34 0.617 11.502 2.054 19.513l23.621 134.332c12.734 72.302 36.356 94.484 97.977 94.484 26.907 0 58.744-5.34 77.025-10.887l-35.123-199.239c-42.724-37.383-93.869-64.496-135.154-64.496zM2608.594 397.879v0l4.725 21.567c1.437 6.162-1.437 5.34-4.725 5.34h-92.43l12.734 75.588c1.437 8.011-4.108 9.448-8.011 8.833v0l-20.95-2.671c-6.162-0.617-8.833-6.162-8.833-8.833v0l-12.734-72.302h-57.307c-1.437 0-6.162-0.617-7.394-5.34l-3.286-20.95c0-2.054 0-6.162 5.34-6.162h56.075l-43.134-245.66c-0.617-4.725-1.437-8.833-1.437-12.734 0-29.783 20.95-43.956 54.021-43.956 25.675 0 72.302 7.394 95.101 18.896 6.779 4.108 6.162 8.833 4.725 12.119v0l-4.725 13.556c-1.437 2.671-4.725 2.671-7.394 2.054v0c-22.184-8.833-35.123-13.556-80.928-13.556-15.61 0-22.184 3.286-22.184 16.227 0 3.286 0.617 7.394 1.437 12.119l42.518 241.758h91.815c4.313-0.617 6.367 1.437 6.984 4.108zM2274.407 106.826c-1.437-8.011 2.671-10.065 6.162-10.065h19.513c6.779 0 8.833 6.779 8.833 10.065v0l53.404 303.788c-38.41 14.173-82.982 21.567-113.383 21.567-88.527 0-124.267-35.123-139.672-121.599l-25.058-141.112c-1.437-8.833-2.054-16.842-2.054-24.238 0-40.464 23.004-55.253 64.906-55.253 47.242 0 94.484 22.184 132.278 54.636l-4.93-37.794zM2151.577 123.669c-20.335 0-30.4 5.34-30.4 26.292 0 5.34 0.617 11.502 2.054 19.513l23.621 134.332c12.734 72.302 36.356 94.484 97.977 94.484 26.907 0 58.744-5.34 77.025-10.887l-35.123-199.239c-42.724-37.383-94.074-64.496-135.154-64.496zM1941.656 106.826c-1.437-8.011 2.671-10.065 6.162-10.065h19.513c6.779 0 8.833 6.779 8.833 10.065l79.079 447.569c1.437 8.011-4.108 9.448-8.011 8.833v0l-20.95-2.671c-6.162-0.617-8.833-6.162-8.833-8.833v0l-23.004-131.046c-20.335 6.162-58.129 10.887-79.696 10.887-83.804 0-124.267-32.454-139.672-121.599l-25.058-141.112c-1.437-8.833-2.054-16.842-2.054-24.238 0-40.464 23.004-55.253 64.906-55.253 47.242 0 96.538 22.184 134.332 54.636l-5.545-37.177zM1816.158 123.669c-20.335 0-30.4 5.34-30.4 26.292 0 5.34 0.617 11.502 2.054 19.513l23.621 134.332c12.734 72.917 37.794 94.484 97.977 94.484 26.292 0 52.582-4.108 79.079-10.887l-35.123-199.239c-42.724-37.383-95.511-64.496-137.208-64.496zM1722.905 424.787h-94.484c-4.108 0-9.448-3.286-10.887-6.162l-66.755-97.155-39.231 101.263c-2.054 5.34-7.394 7.394-11.502 6.779l-82.365-12.119 70.863-155.899-130.224-164.733h88.527c6.162 0 14.173 2.671 18.896 8.011l61.415 73.534 34.508-73.534c2.054-4.108 7.394-8.011 12.734-8.011h86.473l-69.631 152.613 131.662 175.412zM1317.237 102.718l56.075 321.247c1.437 6.779-4.108 6.779-8.011 6.162l-79.079-10.887c-8.833-1.437-10.887-7.394-11.502-10.887v0l-34.508-195.131c-24.238-12.119-67.577-31.015-85.036-31.015-9.448 0-12.734 3.286-12.734 10.065 0 2.671 0.617 6.779 1.437 10.065l38.41 221.422c1.437 6.779-4.108 6.779-7.394 6.162l-78.257-10.887c-8.833-1.437-10.887-7.394-11.502-10.887v0l-37.794-214.029c-2.054-13.556-3.286-24.238-3.286-37.794 0-41.080 16.842-66.755 59.978-66.755 37.794 0 78.257 12.734 129.608 37.177l0.617-24.238c0-2.054 0.617-6.162 4.108-6.162h72.917c3.903 0.41 5.957 3.698 5.957 6.367zM969.494 111.55l79.696 453.731c1.437 6.779-2.671 6.779-6.162 6.162l-91.198-14.788c-41.080 11.502-87.707 16.227-114.819 16.227-84.419 0-112.765-28.961-126.321-104.549l-7.394-43.134h-36.356c-10.065 0-10.887-4.725-11.502-8.833v0l-10.887-63.469c-0.617-2.671 0.617-5.34 4.725-5.34h41.080l-44.572-250.384c-5.34-29.783-9.448-47.242-37.794-77.025v0c-5.34-5.34-4.108-7.394 0-10.887v0l49.913-46.626c5.34-4.725 7.394-3.286 12.734 2.054 45.805 46.626 60.798 77.642 68.194 121.599l45.805 261.271h72.917c4.108 0 5.34 0 6.779 5.34v0l17.459 66.14c1.437 4.725-3.286 6.162-6.779 6.162h-77.025l8.833 47.859c3.286 16.842 10.065 22.184 31.632 22.184 28.346 0 74.356-5.34 99.824-12.119l-64.906-371.365c-2.671-13.556-1.437-14.788 10.065-14.788h70.248c9.038-0.205 13.146-0.205 15.815 14.583zM536.098 431.566c-37.794 0-78.257-12.734-129.608-37.177l0.617 28.961c0 7.394-5.34 6.162-9.448 5.34l-61.415-10.065c-10.065-2.054-13.556-8.011-14.173-11.502l-51.967-296.393c-2.671-13.556-1.437-14.788 10.065-14.788h70.248c8.011 0 12.119 0 14.788 14.788l34.508 197.185c25.675 13.556 67.577 31.015 85.036 31.015 9.448 0 12.734-2.671 12.734-9.448 0-2.671-0.617-6.162-1.437-10.065l-36.356-208.688c-2.671-13.556-1.437-14.788 10.065-14.788h70.248c8.011 0 12.119 0 14.788 14.788l37.794 216.083c2.671 16.842 3.286 26.292 3.286 37.794 0.41 41.902-15.815 66.96-59.771 66.96zM271.541 570.622l-15.61-85.036c-2.054-10.887-4.108-10.887-11.502-12.119l-77.642-10.887c-8.833-1.437-9.448-1.437-8.011 8.833l14.173 82.365c0.617 2.671 2.671 8.833 11.502 10.065l79.079 10.887c7.394 1.232 8.626 0.617 8.011-4.108zM237.032 430.128l-78.874-10.68c-8.833-1.437-10.887-7.394-11.502-10.887v0l-52.582-299.064c-2.054-11.502-0.617-12.734 10.065-12.734h70.248c8.011 0 12.119 0 14.788 14.788v0l55.253 312.621c2.054 6.779-3.286 5.957-7.394 5.957z" />
-<glyph unicode="&#xe902;" glyph-name="alert-triangle" d="M984.213 67.852l-359.452 607.645c-17.118 29.954-47.071 51.35-81.304 59.908s-68.468 4.279-98.421-12.839c-17.118-8.557-34.232-25.675-42.793-42.793 0 0 0 0 0 0l-359.452-611.924c-34.232-59.908-12.839-141.214 47.071-175.446 17.118-12.839 38.514-17.118 59.908-17.118h727.462c34.232 0 68.468 12.839 89.864 38.514 25.675 25.675 38.514 55.629 38.514 89.864-4.279 21.396-8.557 47.071-21.396 64.189zM907.188-26.29c-8.557-8.557-21.396-12.839-29.954-12.839h-727.462c-8.557 0-12.839 0-21.396 4.279-21.396 12.839-25.675 38.514-17.118 59.908l363.732 603.366c4.279 4.279 8.557 12.839 12.839 12.839 21.396 12.839 47.071 4.279 59.908-12.839l363.732-603.366c4.279-4.279 4.279-12.839 4.279-21.396 4.279-12.839-4.279-21.396-8.557-29.954zM513.502 474.375c-25.675 0-42.793-17.118-42.793-42.793v-171.168c0-25.675 17.118-42.793 42.793-42.793s42.793 17.118 42.793 42.793v171.168c0 25.675-17.118 42.793-42.793 42.793zM483.548 119.202c-8.557-8.557-12.839-17.118-12.839-29.954s4.279-21.396 12.839-29.954c8.557-8.557 17.118-12.839 29.954-12.839s21.396 4.279 29.954 12.839c8.557 8.557 12.839 21.396 12.839 29.954s-4.279 21.396-12.839 29.954c-17.118 17.118-42.793 17.118-59.908 0z" />
-<glyph unicode="&#xe903;" glyph-name="arrow-down" d="M843 333.162c-17.118 17.118-42.793 17.118-59.908 0l-226.796-226.796v496.386c0 25.675-17.118 42.793-42.793 42.793s-42.793-17.118-42.793-42.793v-496.386l-226.796 226.796c-17.118 17.118-42.793 17.118-59.908 0s-17.118-42.793 0-59.908l299.544-299.544c4.279-4.279 8.557-8.557 12.839-8.557 4.279-4.279 12.839-4.279 17.118-4.279s12.839 0 17.118 4.279c4.279 4.279 8.557 4.279 12.839 8.557l299.544 299.544c17.118 17.118 17.118 42.793 0 59.908z" />
-<glyph unicode="&#xe904;" glyph-name="moon1" d="M515.215-7.377c-166.374 0-301.94 135.564-301.94 301.94 0.341 149.942 108.178 274.895 256.067 297.49 10.956 1.713 21.908-4.108 27.043-14.037 4.794-9.929 2.74-22.253-5.135-29.783-39.026-37.313-60.593-87.637-60.593-141.726 0-108.862 88.322-197.185 197.185-197.185 54.090 0 104.070 21.567 141.726 60.593 7.875 8.216 19.854 10.27 29.783 5.135s15.746-15.746 14.037-27.043c-23.28-147.888-148.574-255.382-298.174-255.382zM406.352 519.819c-84.9-40.394-141.385-126.321-141.726-225.257 0-137.961 112.286-250.589 250.589-250.589 98.592 0 184.519 56.485 225.257 141.042-34.577-17.8-72.917-27.043-112.97-27.043-136.934 0-248.535 111.602-248.535 248.535 0 40.053 9.584 78.738 27.388 113.313z" />
-<glyph unicode="&#xe905;" glyph-name="search" d="M470.027 95.666c-136.934 0-248.193 111.259-248.193 248.193s111.259 248.193 248.193 248.193 248.193-111.259 248.193-248.193c0-136.934-111.259-248.193-248.193-248.193zM470.027 540.702c-108.521 0-196.843-88.322-196.843-196.843s88.322-196.843 196.843-196.843 196.843 88.322 196.843 196.843c0 108.521-88.322 196.843-196.843 196.843zM779.497 8.371c-6.503 0-13.010 2.395-18.145 7.53l-147.888 148.231c-9.929 9.929-9.929 26.361 0 36.286s26.361 9.929 36.286 0l147.888-148.231c9.929-9.929 9.929-26.361 0-36.286-5.135-5.135-11.638-7.53-18.145-7.53z" />
-<glyph unicode="&#xe906;" glyph-name="sun1" d="M513.502 124.080c-92.773 0-168.428 75.657-168.428 168.428s75.657 168.428 168.428 168.428 168.428-75.657 168.428-168.428-75.657-168.428-168.428-168.428zM513.502 409.588c-64.701 0-117.078-52.377-117.078-117.078s52.377-117.078 117.078-117.078 117.078 52.377 117.078 117.078-52.377 117.078-117.078 117.078zM513.502 508.522c-14.037 0-25.675 11.638-25.675 25.675v98.251c0 14.037 11.638 25.675 25.675 25.675s25.675-11.638 25.675-25.675v-98.251c0-14.037-11.638-25.675-25.675-25.675zM342.335 438.001c-6.503 0-13.010 2.395-18.145 7.53l-69.495 69.151c-9.929 9.929-9.929 26.361 0 36.286s26.361 9.929 36.286 0l69.495-69.495c9.929-9.929 9.929-26.361 0-36.286-4.794-4.794-11.297-7.189-18.145-7.189zM271.814 266.833h-98.251c-14.037 0-25.675 11.638-25.675 25.675s11.638 25.675 25.675 25.675h98.251c14.037 0 25.675-11.638 25.675-25.675s-11.638-25.675-25.675-25.675zM273.184 26.514c-6.503 0-13.010 2.395-18.145 7.53-9.929 9.929-9.929 26.361 0 36.286l69.495 69.495c9.929 9.929 26.361 9.929 36.286 0s9.929-26.361 0-36.286l-69.495-69.495c-5.135-5.135-11.638-7.53-18.145-7.53zM513.502-73.106c-14.037 0-25.675 11.638-25.675 25.675v98.251c0 14.037 11.638 25.675 25.675 25.675s25.675-11.638 25.675-25.675v-98.251c0-14.378-11.638-25.675-25.675-25.675zM753.822 26.514c-6.503 0-13.010 2.395-18.145 7.53l-69.495 69.495c-9.929 9.929-9.929 26.361 0 36.286s26.361 9.929 36.286 0l69.495-69.495c9.929-9.929 9.929-26.361 0-36.286-4.794-5.135-11.297-7.53-18.145-7.53zM853.442 266.833h-98.251c-14.037 0-25.675 11.638-25.675 25.675s11.638 25.675 25.675 25.675h98.251c14.037 0 25.675-11.638 25.675-25.675s-11.297-25.675-25.675-25.675zM684.671 438.001c-6.503 0-13.010 2.395-18.145 7.53-9.929 9.929-9.929 26.361 0 36.286l69.495 69.495c9.929 9.929 26.361 9.929 36.286 0s9.929-26.361 0-36.286l-69.495-69.495c-5.135-5.135-11.638-7.53-18.145-7.53z" />
-<glyph unicode="&#xe907;" glyph-name="arrow-down-circle" d="M513.502 773.919c-261.031 0-470.711-209.681-470.711-470.711s209.681-470.711 470.711-470.711 470.711 209.681 470.711 470.711-209.681 470.711-470.711 470.711zM513.502-81.919c-213.96 0-385.127 171.168-385.127 385.127s171.168 385.127 385.127 385.127c213.96 0 385.127-171.168 385.127-385.127s-171.168-385.127-385.127-385.127zM654.716 333.162l-98.421-98.421v239.635c0 25.675-17.118 42.793-42.793 42.793s-42.793-17.118-42.793-42.793v-239.635l-98.421 98.421c-17.118 17.118-42.793 17.118-59.908 0s-17.118-42.793 0-59.908l171.168-171.168c4.279-4.279 8.557-8.557 12.839-8.557 4.279-4.279 12.839-4.279 17.118-4.279s12.839 0 17.118 4.279c4.279 4.279 8.557 4.279 12.839 8.557l171.168 171.168c17.118 17.118 17.118 42.793 0 59.908s-42.793 17.118-59.908 0z" />
-<glyph unicode="&#xe908;" glyph-name="arrow-down-left" d="M727.462 132.039h-325.219l355.173 355.173c17.118 17.118 17.118 42.793 0 59.908s-42.793 17.118-59.908 0l-355.173-355.173v325.219c0 25.675-17.118 42.793-42.793 42.793s-42.793-17.118-42.793-42.793v-427.919c0-4.279 0-12.839 4.279-17.118 4.279-8.557 12.839-17.118 21.396-21.396 4.279-4.279 12.839-4.279 17.118-4.279h427.919c25.675 0 42.793 17.118 42.793 42.793s-17.118 42.793-42.793 42.793z" />
-<glyph unicode="&#xe909;" glyph-name="arrow-down-right" d="M770.254 517.166c0 25.675-17.118 42.793-42.793 42.793s-42.793-17.118-42.793-42.793v-325.219l-355.173 355.173c-17.118 17.118-42.793 17.118-59.908 0s-17.118-42.793 0-59.908l355.173-355.173h-325.219c-25.675 0-42.793-17.118-42.793-42.793s17.118-42.793 42.793-42.793h427.919c4.279 0 12.839 0 17.118 4.279 8.557 4.279 17.118 12.839 21.396 21.396 4.279 4.279 4.279 12.839 4.279 17.118v427.919z" />
-<glyph unicode="&#xe90a;" glyph-name="arrow-left" d="M813.046 346h-496.386l226.796 226.796c17.118 17.118 17.118 42.793 0 59.908s-42.793 17.118-59.908 0l-299.544-299.544c-4.279-4.279-8.557-8.557-8.557-12.839-4.279-8.557-4.279-21.396 0-34.232 4.279-4.279 4.279-8.557 8.557-12.839l299.544-299.544c8.557-8.557 21.396-12.839 29.954-12.839s21.396 4.279 29.954 12.839c17.118 17.118 17.118 42.793 0 59.908l-226.796 226.796h496.386c25.675 0 42.793 17.118 42.793 42.793s-17.118 42.793-42.793 42.793z" />
-<glyph unicode="&#xe90b;" glyph-name="arrow-left-circle" d="M513.502 773.919c-261.031 0-470.711-209.681-470.711-470.711s209.681-470.711 470.711-470.711 470.711 209.681 470.711 470.711-209.681 470.711-470.711 470.711zM513.502-81.919c-213.96 0-385.127 171.168-385.127 385.127s171.168 385.127 385.127 385.127c213.96 0 385.127-171.168 385.127-385.127s-171.168-385.127-385.127-385.127zM684.671 346h-239.635l98.421 98.421c17.118 17.118 17.118 42.793 0 59.908s-42.793 17.118-59.908 0l-171.168-171.168c-4.279-4.279-8.557-8.557-8.557-12.839-4.279-8.557-4.279-21.396 0-34.232 4.279-4.279 4.279-8.557 8.557-12.839l171.168-171.168c8.557-8.557 21.396-12.839 29.954-12.839s21.396 4.279 29.954 12.839c17.118 17.118 17.118 42.793 0 59.908l-98.421 98.421h239.635c25.675 0 42.793 17.118 42.793 42.793s-17.118 42.793-42.793 42.793z" />
-<glyph unicode="&#xe90c;" glyph-name="arrow-right" d="M851.56 286.090c4.279 8.557 4.279 21.396 0 34.232-4.279 4.279-4.279 8.557-8.557 12.839l-299.544 299.544c-17.118 17.118-42.793 17.118-59.908 0s-17.118-42.793 0-59.908l226.796-226.796h-496.386c-25.675 0-42.793-17.118-42.793-42.793s17.118-42.793 42.793-42.793h496.386l-226.796-226.796c-17.118-17.118-17.118-42.793 0-59.908 8.557-8.557 21.396-12.839 29.954-12.839s21.396 4.279 29.954 12.839l299.544 299.544c4.279 4.279 8.557 8.557 8.557 12.839z" />
-<glyph unicode="&#xe90d;" glyph-name="arrow-right-circle" d="M513.502 773.919c-261.031 0-470.711-209.681-470.711-470.711s209.681-470.711 470.711-470.711 470.711 209.681 470.711 470.711-209.681 470.711-470.711 470.711zM513.502-81.919c-213.96 0-385.127 171.168-385.127 385.127s171.168 385.127 385.127 385.127c213.96 0 385.127-171.168 385.127-385.127s-171.168-385.127-385.127-385.127zM723.184 320.325c-4.279 4.279-4.279 8.557-8.557 12.839l-171.168 171.168c-17.118 17.118-42.793 17.118-59.908 0s-17.118-42.793 0-59.908l98.421-98.421h-239.635c-25.675 0-42.793-17.118-42.793-42.793s17.118-42.793 42.793-42.793h239.635l-98.421-98.421c-17.118-17.118-17.118-42.793 0-59.908 8.557-8.557 21.396-12.839 29.954-12.839s21.396 4.279 29.954 12.839l171.168 171.168c4.279 4.279 8.557 8.557 8.557 12.839 4.279 12.839 4.279 21.396 0 34.232z" />
-<glyph unicode="&#xe90e;" glyph-name="arrow-up" d="M843 333.162l-299.544 299.544c-4.279 4.279-8.557 8.557-12.839 8.557-8.557 4.279-21.396 4.279-34.232 0-4.279-4.279-8.557-4.279-12.839-8.557l-299.544-299.544c-17.118-17.118-17.118-42.793 0-59.908s42.793-17.118 59.908 0l226.796 226.796v-496.386c0-25.675 17.118-42.793 42.793-42.793s42.793 17.118 42.793 42.793v496.386l226.796-226.796c8.557-8.557 21.396-12.839 29.954-12.839s21.396 4.279 29.954 12.839c17.118 17.118 17.118 42.793 0 59.908z" />
-<glyph unicode="&#xe90f;" glyph-name="arrow-up-circle" d="M513.502 773.919c-261.031 0-470.711-209.681-470.711-470.711s209.681-470.711 470.711-470.711 470.711 209.681 470.711 470.711-209.681 470.711-470.711 470.711zM513.502-81.919c-213.96 0-385.127 171.168-385.127 385.127s171.168 385.127 385.127 385.127c213.96 0 385.127-171.168 385.127-385.127s-171.168-385.127-385.127-385.127zM543.458 504.329c-4.279 4.279-8.557 8.557-12.839 8.557-8.557 4.279-21.396 4.279-34.232 0-4.279-4.279-8.557-4.279-12.839-8.557l-171.168-171.168c-17.118-17.118-17.118-42.793 0-59.908s42.793-17.118 59.908 0l98.421 98.421v-239.635c0-25.675 17.118-42.793 42.793-42.793s42.793 17.118 42.793 42.793v239.635l98.421-98.421c8.557-8.557 21.396-12.839 29.954-12.839s21.396 4.279 29.954 12.839c17.118 17.118 17.118 42.793 0 59.908l-171.168 171.168z" />
-<glyph unicode="&#xe910;" glyph-name="arrow-up-left" d="M402.244 474.375h325.219c25.675 0 42.793 17.118 42.793 42.793s-17.118 42.793-42.793 42.793h-427.919c-4.279 0-12.839 0-17.118-4.279-8.557-4.279-17.118-12.839-21.396-21.396-4.279-4.279-4.279-12.839-4.279-17.118v-427.919c0-25.675 17.118-42.793 42.793-42.793s42.793 17.118 42.793 42.793v325.219l355.173-355.173c8.557-8.557 21.396-12.839 29.954-12.839s21.396 4.279 29.954 12.839c17.118 17.118 17.118 42.793 0 59.908l-355.173 355.173z" />
-<glyph unicode="&#xe911;" glyph-name="arrow-up-right" d="M765.975 534.284c-4.279 8.557-12.839 17.118-21.396 21.396-4.279 4.279-12.839 4.279-17.118 4.279h-427.919c-25.675 0-42.793-17.118-42.793-42.793s17.118-42.793 42.793-42.793h325.219l-355.173-355.173c-17.118-17.118-17.118-42.793 0-59.908 8.557-8.557 17.118-12.839 29.954-12.839s21.396 4.279 29.954 12.839l355.173 355.173v-325.219c0-25.675 17.118-42.793 42.793-42.793s42.793 17.118 42.793 42.793v427.919c0 4.279 0 12.839-4.279 17.118z" />
-<glyph unicode="&#xe912;" glyph-name="check" d="M885.792 589.913c-17.118 17.118-42.793 17.118-59.908 0l-440.757-440.757-184.006 184.006c-17.118 17.118-42.793 17.118-59.908 0s-17.118-42.793 0-59.908l213.96-213.96c8.557-8.557 17.118-12.839 29.954-12.839s21.396 4.279 29.954 12.839l470.711 470.711c17.118 17.118 17.118 42.793 0 59.908z" />
-<glyph unicode="&#xe913;" glyph-name="bar-chart" d="M179.375 180.595c0 12.813-10.25 25.625-25.625 25.625h-128.125c-15.375 0-25.625-12.813-25.625-25.625v-410c0-12.813 10.25-25.625 25.625-25.625h128.125c15.375 0 25.625 12.813 25.625 25.625v410zM461.25 744.346c0 15.375-12.813 25.625-25.625 25.625h-128.125c-15.375 0-25.625-10.25-25.625-25.625v-973.751c0-12.813 10.25-25.625 25.625-25.625h128.125c12.813 0 25.625 12.813 25.625 25.625v973.751zM743.126 462.47c0 15.375-12.813 25.625-25.625 25.625h-128.125c-12.813 0-25.625-10.25-25.625-25.625v-691.876c0-12.813 12.813-25.625 25.625-25.625h128.125c12.813 0 25.625 12.813 25.625 25.625v691.876zM1025.001-50.030c0 12.813-12.813 25.625-25.625 25.625h-128.125c-12.813 0-25.625-12.813-25.625-25.625v-179.375c0-12.813 12.813-25.625 25.625-25.625h128.125c12.813 0 25.625 12.813 25.625 25.625v179.375z" />
-<glyph unicode="&#xe914;" glyph-name="heart1" d="M920.026 649.822v0c-51.35 51.35-119.818 81.304-192.564 81.304v0c-72.746 0-145.493-29.954-196.843-81.304 0 0 0 0 0 0l-17.118-17.118-17.118 17.118c-51.35 51.35-119.818 81.304-196.843 81.304-72.746 0-141.214-29.954-192.564-81.304s-85.583-124.096-85.583-196.843 29.954-145.493 81.304-196.843l376.569-376.569c8.557-8.557 17.118-12.839 29.954-12.839s21.396 4.279 29.954 12.839l376.569 376.569c115.539 106.979 115.539 286.706 4.279 393.685zM860.117 316.044l-346.614-346.614-346.614 346.614c-77.025 77.025-77.025 196.843 0 273.868 34.232 38.514 85.583 55.629 132.655 55.629 51.35 0 98.421-17.118 136.934-55.629l47.071-47.071c17.118-17.118 42.793-17.118 59.908 0l42.793 47.071c0 0 0 0 0 0 38.514 34.232 85.583 55.629 141.214 55.629 0 0 0 0 0 0 51.35 0 98.421-21.396 136.934-55.629v0c34.232-38.514 55.629-85.583 55.629-136.934s-21.396-98.421-59.908-136.934z" />
-<glyph unicode="&#xe915;" glyph-name="settings" d="M513.502 474.375c-94.143 0-171.168-77.025-171.168-171.168s77.025-171.168 171.168-171.168c94.143 0 171.168 77.025 171.168 171.168s-77.025 171.168-171.168 171.168zM513.502 217.623c-47.071 0-85.583 38.514-85.583 85.583s38.514 85.583 85.583 85.583c47.071 0 85.583-38.514 85.583-85.583s-38.514-85.583-85.583-85.583zM868.675 157.714c4.279 8.557 12.839 17.118 29.954 17.118 72.746 0 128.375 55.629 128.375 128.375s-55.629 128.375-128.375 128.375h-8.557c-8.557 0-17.118 4.279-21.396 12.839 0 4.279 0 4.279-4.279 8.557-4.279 8.557-4.279 21.396 8.557 34.232 51.35 51.35 51.35 132.655 0 179.726v0c0 0 0 0 0 0-25.675 25.675-55.629 38.514-89.864 38.514 0 0 0 0 0 0-34.232 0-68.468-12.839-94.143-38.514-8.557-8.557-21.396-8.557-29.954-4.279-8.557 0-17.118 12.839-17.118 25.675 0 72.746-55.629 128.375-128.375 128.375s-128.375-55.629-128.375-128.375v-8.557c0-8.557-4.279-17.118-12.839-21.396-4.279 0-4.279 0-8.557-4.279-8.557-4.279-21.396 0-34.232 8.557-51.35 51.35-132.655 51.35-179.726 0-51.35-51.35-51.35-132.655 4.279-184.006 8.557-8.557 8.557-21.396 4.279-34.232-4.279-8.557-17.118-17.118-29.954-17.118-72.746 0-128.375-55.629-128.375-128.375s55.629-128.375 128.375-128.375h8.557c12.839 0 21.396-8.557 25.675-17.118s4.279-21.396-8.557-34.232c-25.675-25.675-38.514-55.629-38.514-89.864s12.839-64.189 38.514-89.864c0 0 0 0 0 0 51.35-51.35 132.655-51.35 184.006 4.279 8.557 8.557 21.396 8.557 34.232 4.279s17.118-12.839 17.118-29.954c0-72.746 55.629-128.375 128.375-128.375s128.375 55.629 128.375 128.375v8.557c0 12.839 8.557 21.396 17.118 25.675s21.396 4.279 34.232-8.557c51.35-51.35 132.655-51.35 179.726 0 51.35 51.35 51.35 132.655-4.279 184.006-4.279 8.557-8.557 21.396-4.279 29.954 0 0 0 0 0 0zM791.65 191.948c-17.118-42.793-8.557-89.864 25.675-128.375 8.557-8.557 12.839-17.118 12.839-29.954s-4.279-21.396-12.839-29.954c-8.557-8.557-17.118-12.839-29.954-12.839 0 0 0 0 0 0-12.839 0-21.396 4.279-34.232 17.118-34.232 34.232-81.304 42.793-124.096 21.396-42.793-17.118-68.468-59.908-68.468-102.7v-8.557c0-25.675-17.118-42.793-42.793-42.793s-42.793 17.118-42.793 42.793c0 0 0 4.279 0 4.279 0 47.071-29.954 85.583-72.746 102.7-12.839 8.557-29.954 8.557-47.071 8.557-29.954 0-59.908-12.839-81.304-34.232-17.118-17.118-42.793-17.118-59.908 0 0 0 0 0 0 0v0c-8.557 8.557-12.839 17.118-12.839 29.954s4.279 21.396 17.118 34.232c34.232 34.232 42.793 81.304 21.396 124.096-17.118 42.793-59.908 68.468-102.7 68.468h-8.557c-25.675 0-42.793 17.118-42.793 42.793s17.118 42.793 42.793 42.793c0 0 4.279 0 4.279 0 47.071 0 85.583 29.954 102.7 72.746s8.557 89.864-25.675 128.375c-17.118 17.118-17.118 42.793 0 59.908s42.793 17.118 64.189-4.279c29.954-29.954 77.025-38.514 115.539-25.675 4.279 0 8.557 0 12.839 4.279 42.793 17.118 68.468 59.908 68.468 102.7v8.557c0 25.675 17.118 42.793 42.793 42.793s42.793-17.118 42.793-47.071c0-47.071 25.675-85.583 68.468-102.7s89.864-8.557 128.375 25.675c8.557 8.557 17.118 12.839 29.954 12.839v0c12.839 0 21.396-4.279 29.954-12.839 0 0 0 0 0 0 17.118-17.118 17.118-42.793-4.279-64.189-29.954-29.954-38.514-77.025-25.675-115.539 0-4.279 0-8.557 4.279-12.839 17.118-42.793 59.908-68.468 102.7-68.468h8.557c25.675 0 42.793-17.118 42.793-42.793s-17.118-42.793-47.071-42.793c-42.793 0-85.583-25.675-102.7-68.468z" />
-<glyph unicode="&#xe916;" glyph-name="zoom-in" d="M928.585-51.965l-158.33 158.33c51.35 64.189 85.583 149.771 85.583 239.635 0 213.96-171.168 385.127-385.127 385.127s-385.127-171.168-385.127-385.127c0-213.96 171.168-385.127 385.127-385.127 89.864 0 175.446 29.954 239.635 85.583l158.33-158.33c8.557-8.557 21.396-12.839 29.954-12.839s21.396 4.279 29.954 12.839c17.118 17.118 17.118 42.793 0 59.908zM171.168 346c0 166.889 132.655 299.544 299.544 299.544s299.544-132.655 299.544-299.544c0-81.304-34.232-158.33-85.583-209.681 0 0 0 0 0 0s0 0 0 0c-55.629-55.629-128.375-85.583-209.681-85.583-171.168-4.279-303.822 128.375-303.822 295.264zM599.086 388.79h-85.583v85.583c0 25.675-17.118 42.793-42.793 42.793s-42.793-17.118-42.793-42.793v-85.583h-85.583c-25.675 0-42.793-17.118-42.793-42.793s17.118-42.793 42.793-42.793h85.583v-85.583c0-25.675 17.118-42.793 42.793-42.793s42.793 17.118 42.793 42.793v85.583h85.583c25.675 0 42.793 17.118 42.793 42.793s-17.118 42.793-42.793 42.793z" />
-<glyph unicode="&#xe917;" glyph-name="zoom-out" d="M928.585-51.965l-158.33 158.33c51.35 64.189 85.583 149.771 85.583 239.635 0 213.96-171.168 385.127-385.127 385.127s-385.127-171.168-385.127-385.127c0-213.96 171.168-385.127 385.127-385.127 89.864 0 175.446 29.954 239.635 85.583l158.33-158.33c8.557-8.557 21.396-12.839 29.954-12.839s21.396 4.279 29.954 12.839c17.118 17.118 17.118 42.793 0 59.908zM171.168 346c0 166.889 132.655 299.544 299.544 299.544s299.544-132.655 299.544-299.544c0-81.304-34.232-158.33-85.583-209.681 0 0 0 0 0 0s0 0 0 0c-55.629-55.629-128.375-85.583-209.681-85.583-171.168-4.279-303.822 128.375-303.822 295.264zM599.086 388.79h-256.751c-25.675 0-42.793-17.118-42.793-42.793s17.118-42.793 42.793-42.793h256.751c25.675 0 42.793 17.118 42.793 42.793s-17.118 42.793-42.793 42.793z" />
-<glyph unicode="&#xe918;" glyph-name="chevron-down" d="M800.209 461.537c-17.118 17.118-42.793 17.118-59.908 0l-226.796-226.796-226.796 226.796c-17.118 17.118-42.793 17.118-59.908 0s-17.118-42.793 0-59.908l256.751-256.751c8.557-8.557 21.396-12.839 29.954-12.839s21.396 4.279 29.954 12.839l256.751 256.751c17.118 17.118 17.118 42.793 0 59.908z" />
-<glyph unicode="&#xe919;" glyph-name="chevron-left" d="M445.036 303.207l226.796 226.796c17.118 17.118 17.118 42.793 0 59.908s-42.793 17.118-59.908 0l-256.751-256.751c-17.118-17.118-17.118-42.793 0-59.908l256.751-256.751c8.557-8.557 21.396-12.839 29.954-12.839s21.396 4.279 29.954 12.839c17.118 17.118 17.118 42.793 0 59.908l-226.796 226.796z" />
-<glyph unicode="&#xe91a;" glyph-name="chevron-right" d="M671.833 333.162l-256.751 256.751c-17.118 17.118-42.793 17.118-59.908 0s-17.118-42.793 0-59.908l226.796-226.796-226.796-226.796c-17.118-17.118-17.118-42.793 0-59.908 8.557-8.557 17.118-12.839 29.954-12.839s21.396 4.279 29.954 12.839l256.751 256.751c17.118 17.118 17.118 42.793 0 59.908z" />
-<glyph unicode="&#xe91b;" glyph-name="chevron-up" d="M800.209 204.786l-256.751 256.751c-17.118 17.118-42.793 17.118-59.908 0l-256.751-256.751c-17.118-17.118-17.118-42.793 0-59.908s42.793-17.118 59.908 0l226.796 226.796 226.796-226.796c8.557-8.557 21.396-12.839 29.954-12.839s21.396 4.279 29.954 12.839c17.118 17.118 17.118 42.793 0 59.908z" />
-<glyph unicode="&#xe91c;" glyph-name="menu" d="M898.631 346h-770.254c-25.675 0-42.793-17.118-42.793-42.793s17.118-42.793 42.793-42.793h770.254c25.675 0 42.793 17.118 42.793 42.793s-17.118 42.793-42.793 42.793zM128.375 517.166h770.254c25.675 0 42.793 17.118 42.793 42.793s-17.118 42.793-42.793 42.793h-770.254c-25.675 0-42.793-17.118-42.793-42.793s17.118-42.793 42.793-42.793zM898.631 89.248h-770.254c-25.675 0-42.793-17.118-42.793-42.793s17.118-42.793 42.793-42.793h770.254c25.675 0 42.793 17.118 42.793 42.793s-17.118 42.793-42.793 42.793z" />
-<glyph unicode="&#xe91d;" glyph-name="download" d="M898.631 217.623c-25.675 0-42.793-17.118-42.793-42.793v-171.168c0-25.675-17.118-42.793-42.793-42.793h-599.086c-25.675 0-42.793 17.118-42.793 42.793v171.168c0 25.675-17.118 42.793-42.793 42.793s-42.793-17.118-42.793-42.793v-171.168c0-72.746 55.629-128.375 128.375-128.375h599.086c72.746 0 128.375 55.629 128.375 128.375v171.168c0 25.675-17.118 42.793-42.793 42.793zM483.548 144.877c4.279-4.279 8.557-8.557 12.839-8.557 4.279-4.279 12.839-4.279 17.118-4.279s12.839 0 17.118 4.279c4.279 4.279 8.557 4.279 12.839 8.557l213.96 213.96c17.118 17.118 17.118 42.793 0 59.908s-42.793 17.118-59.908 0l-141.214-141.214v410.802c0 25.675-17.118 42.793-42.793 42.793s-42.793-17.118-42.793-42.793v-410.802l-141.214 141.214c-17.118 17.118-42.793 17.118-59.908 0s-17.118-42.793 0-59.908l213.96-213.96z" />
-<glyph unicode="&#xe91e;" glyph-name="minus" d="M813.046 346h-599.086c-25.675 0-42.793-17.118-42.793-42.793s17.118-42.793 42.793-42.793h599.086c25.675 0 42.793 17.118 42.793 42.793s-17.118 42.793-42.793 42.793z" />
-<glyph unicode="&#xe91f;" glyph-name="plus" d="M813.046 346h-256.751v256.751c0 25.675-17.118 42.793-42.793 42.793s-42.793-17.118-42.793-42.793v-256.751h-256.751c-25.675 0-42.793-17.118-42.793-42.793s17.118-42.793 42.793-42.793h256.751v-256.751c0-25.675 17.118-42.793 42.793-42.793s42.793 17.118 42.793 42.793v256.751h256.751c25.675 0 42.793 17.118 42.793 42.793s-17.118 42.793-42.793 42.793z" />
-<glyph unicode="&#xe920;" glyph-name="add-cell" d="M417.221 806.012h-385.127c-17.974 0-32.093-14.122-32.093-32.093v-385.127c0-17.974 14.122-32.093 32.093-32.093h385.127c17.974 0 32.093 14.122 32.093 32.093v385.127c0 17.974-14.122 32.093-32.093 32.093zM994.913 228.321h-385.127c-17.974 0-32.093-14.122-32.093-32.093v-385.127c0-17.974 14.122-32.093 32.093-32.093h385.127c17.974 0 32.093 14.122 32.093 32.093v385.127c0 17.974-14.122 32.093-32.093 32.093zM417.221 228.321h-385.127c-17.974 0-32.093-14.122-32.093-32.093v-385.127c0-17.974 14.122-32.093 32.093-32.093h385.127c17.974 0 32.093 14.122 32.093 32.093v385.127c0 17.974-14.122 32.093-32.093 32.093zM609.784 549.26h160.47v-160.47c0-17.974 14.122-32.093 32.093-32.093s32.093 14.122 32.093 32.093v160.47h160.47c17.974 0 32.093 14.122 32.093 32.093s-14.122 32.093-32.093 32.093h-160.47v160.47c0 17.974-14.122 32.093-32.093 32.093s-32.093-14.122-32.093-32.093v-160.47h-160.47c-17.974 0-32.093-14.122-32.093-32.093s14.122-32.093 32.093-32.093z" />
-<glyph unicode="&#xe921;" glyph-name="alert" d="M1008.806 3.417l-439.572 769.251c-11.427 19.999-32.696 32.342-55.73 32.342s-44.303-12.342-55.73-32.342l-439.572-769.251c-11.353-19.865-11.271-44.273 0.214-64.064s32.636-31.969 55.516-31.969h879.146c22.88 0 44.033 12.18 55.516 31.969s11.567 44.197 0.214 64.064zM577.691 35.757h-128.375v128.375h128.375v-128.375zM577.691 228.321h-128.375v256.751h128.375v-256.751z" />
-<glyph unicode="&#xe922;" glyph-name="calendar" d="M886.959 665.965h-46.682v46.682c0 23.342-23.342 46.682-46.682 46.682s-46.682-23.342-46.682-46.682v-46.682h-466.821v46.682c0 23.342-23.342 46.682-46.682 46.682s-46.682-23.342-46.682-46.682v-46.682h-46.682c-79.358 0-140.046-60.686-140.046-140.046v-606.867c0-74.692 60.686-140.046 140.046-140.046h746.913c79.358 0 140.046 65.356 140.046 140.046v606.867c0 79.358-60.686 140.046-140.046 140.046zM933.642-80.948c0-23.342-23.342-46.682-46.682-46.682h-746.913c-23.342 0-46.682 23.342-46.682 46.682v420.138h840.278v-420.138zM93.364 432.555v93.364c0 23.342 23.342 46.682 46.682 46.682h46.682v-46.682c0-23.342 23.342-46.682 46.682-46.682s46.682 23.342 46.682 46.682v46.682h466.821v-46.682c0-23.342 23.342-46.682 46.682-46.682s46.682 23.342 46.682 46.682v46.682h46.682c23.342 0 46.682-23.342 46.682-46.682v-93.364h-840.278zM373.457 245.827h93.364v-93.364h-93.364v93.364zM560.185 245.827h93.364v-93.364h-93.364v93.364zM186.728 59.098h93.364v-93.364h-93.364v93.364zM373.457 59.098h93.364v-93.364h-93.364v93.364zM560.185 59.098h93.364v-93.364h-93.364v93.364zM746.913 245.827h93.364v-93.364h-93.364v93.364z" />
-<glyph unicode="&#xe923;" glyph-name="checkmark" d="M346.614-51.539l-272.157 272.157c-33.379 33.379-38.514 89.864-7.704 128.375 35.945 38.514 94.999 38.514 130.944 2.569l169.455-169.455c5.135-5.135 12.839-5.135 15.405 0l444.18 444.18c35.945 35.945 94.999 35.945 130.944-2.569 33.379-35.945 28.244-92.43-7.704-128.375l-544.314-544.314c-15.405-20.54-43.649-20.54-59.054-2.569z" />
-<glyph unicode="&#xe924;" glyph-name="cog-thick" d="M988.492 397.777h-92.43c-7.704 30.81-20.54 61.62-35.945 89.864l64.189 64.189c15.405 15.405 15.405 41.080 0 53.919l-94.999 97.565c-15.405 15.405-41.080 15.405-53.919 0l-66.755-66.755c-28.244 15.405-56.485 28.244-87.295 35.945v94.999c0 20.54-17.974 38.514-38.514 38.514h-133.51c-20.54 0-38.514-17.974-38.514-38.514v-94.999c-30.81-7.704-61.62-20.54-87.295-35.945l-69.324 66.755c-15.405 15.405-41.080 15.405-56.485 0l-94.999-94.999c-15.405-15.405-15.405-41.080 0-56.485l64.189-64.189c-15.405-28.244-28.244-56.485-35.945-89.864h-92.43c-20.54 0-38.514-17.974-38.514-38.514v-133.51c0-20.54 17.974-38.514 38.514-38.514h92.43c7.704-30.81 20.54-61.62 35.945-89.864l-64.189-64.189c-15.405-15.405-15.405-41.080 0-53.919l94.999-97.565c15.405-15.405 41.080-15.405 53.919 0l66.755 66.755c28.244-15.405 56.485-28.244 87.295-35.945v-94.999c0-20.54 17.974-38.514 38.514-38.514h133.51c20.54 0 38.514 17.974 38.514 38.514v94.999c30.81 7.704 61.62 20.54 87.295 35.945l66.755-66.755c15.405-15.405 41.080-15.405 53.919 0l94.999 94.999c15.405 15.405 15.405 41.080 0 53.919l-64.189 64.189c15.405 28.244 28.244 56.485 35.945 89.864h92.43c20.54 0 38.514 17.974 38.514 38.514v133.51c5.135 25.675-12.839 41.080-33.379 41.080zM513.502 76.838c-118.105 0-215.671 97.565-215.671 215.671s97.565 215.671 215.671 215.671 215.671-97.565 215.671-215.671-97.565-215.671-215.671-215.671z" />
-<glyph unicode="&#xe925;" glyph-name="dashboards" horiz-adv-x="1074" d="M933.642 665.965h-793.595c-79.358 0-140.046-60.686-140.046-140.046v-466.821c0-74.692 60.686-140.046 140.046-140.046h793.595c79.358 0 140.046 65.356 140.046 140.046v466.821c0 79.358-60.686 140.046-140.046 140.046zM93.364 525.919c0 23.342 23.342 46.682 46.682 46.682h186.728v-233.41h-233.41v186.728zM140.046 12.416c-23.342 0-46.682 23.342-46.682 46.682v186.728h233.41v-233.41h-186.728zM420.138 12.416v233.41h233.41v-233.41h-233.41zM980.323 59.098c0-23.342-23.342-46.682-46.682-46.682h-186.728v233.41h233.41v-186.728zM420.138 339.19v233.41h513.502c23.342 0 46.682-23.342 46.682-46.682v-186.728h-560.185z" />
-<glyph unicode="&#xe926;" glyph-name="data-explorer" d="M934.576 428.587c-25.675 15.405-56.485 17.974-82.16 7.704l-120.674 161.754c2.569 2.569 2.569 5.135 5.135 7.704 28.244 48.784 10.27 112.97-38.514 141.214s-112.97 10.27-141.214-38.514c-25.675-43.649-12.839-100.134 25.675-130.944l-197.699-546.881c-12.839 0-23.109-2.569-35.945-5.135l-120.674 159.185c2.569 2.569 2.569 5.135 5.135 7.704 28.244 48.784 10.27 112.97-38.514 141.214s-110.404 10.27-138.645-38.514-10.27-112.97 38.514-141.214c25.675-15.405 56.485-17.974 84.729-7.704l120.674-159.185c-2.569-2.569-2.569-2.569-5.135-5.135-28.244-48.784-10.27-112.97 38.514-141.214s112.97-10.27 141.214 38.514c25.675 46.215 12.839 102.7-25.675 133.51l192.564 541.746c12.839 0 23.109 2.569 35.945 5.135l120.674-159.185c-2.569-2.569-2.569-5.135-5.135-7.704-28.244-48.784-10.27-112.97 38.514-141.214s112.97-10.27 141.214 38.514 10.27 110.404-38.514 138.645z" />
-<glyph unicode="&#xe927;" glyph-name="ui-download" d="M408.235 271.968h-125.809c-35.945 0-56.485-46.215-28.244-71.89l259.319-259.319 261.886 261.886c28.244 28.244 7.704 71.89-28.244 71.89l-128.375-2.569-5.135 431.342c0 59.054-46.215 102.7-102.7 102.7-59.054 0-102.7-46.215-102.7-102.7v-431.342zM911.467 35.757v-51.35c0-48.784-41.080-89.864-89.864-89.864h-616.204c-48.784 0-89.864 41.080-89.864 89.864v51.35c0 20.54-17.974 38.514-38.514 38.514s-38.514-17.974-38.514-38.514v-51.35c0-92.43 74.459-166.889 166.889-166.889h616.204c92.43 0 166.889 74.459 166.889 166.889v51.35c0 20.54-17.974 38.514-38.514 38.514v0c-20.54 0-38.514-17.974-38.514-38.514z" />
-<glyph unicode="&#xe928;" glyph-name="duplicate" d="M924.306 806.012h-564.854c-56.485 0-102.7-46.215-102.7-102.7v-154.050h-154.050c-56.485 0-102.7-46.215-102.7-102.7v-564.854c0-56.485 46.215-102.7 102.7-102.7h564.854c56.485 0 102.7 46.215 102.7 102.7v154.050h154.050c56.485 0 102.7 46.215 102.7 102.7v564.854c0 56.485-46.215 102.7-102.7 102.7zM693.229-118.294c0-12.839-12.839-25.675-25.675-25.675h-564.854c-12.839 0-25.675 12.839-25.675 25.675v564.854c0 12.839 12.839 25.675 25.675 25.675h154.050v-333.777c0-56.485 46.215-102.7 102.7-102.7h333.777v-154.050z" />
-<glyph unicode="&#xe929;" glyph-name="export" d="M205.401 767.498h231.076c20.54 0 38.514-17.974 38.514-38.514s-17.974-38.514-38.514-38.514h-231.076c-48.784 0-89.864-41.080-89.864-89.864v-616.204c0-48.784 41.080-89.864 89.864-89.864h616.204c48.784 0 89.864 41.080 89.864 89.864v231.076c0 20.54 17.974 38.514 38.514 38.514s38.514-17.974 38.514-38.514v-231.076c0-92.43-74.459-166.889-166.889-166.889h-616.204c-92.43 0-166.889 74.459-166.889 166.889v616.204c0 92.43 74.459 166.889 166.889 166.889zM680.391 605.746l-89.864 89.864c-25.675 25.675-7.704 71.89 30.81 71.89h369.722v-369.722c0-38.514-46.215-56.485-71.89-30.81l-89.864 89.864-251.616-251.616c-41.080-41.080-105.269-41.080-146.349 0s-41.080 105.269 0 146.349l249.049 254.184z" />
-<glyph unicode="&#xe92a;" glyph-name="fullscreen" d="M872.955 61.432c0-12.839-12.839-25.675-25.675-25.675h-667.554c-12.839 0-25.675 12.839-25.675 25.675v462.152c0 12.839 12.839 25.675 25.675 25.675h667.554c12.839 0 25.675-12.839 25.675-25.675v-462.152zM89.864 626.286h154.050c7.704 0 12.839 5.135 12.839 12.839v51.35c0 7.704-5.135 12.839-12.839 12.839h-166.889c-43.649 0-77.025-33.379-77.025-77.025v-166.889c0-7.704 5.135-12.839 12.839-12.839h51.35c7.704 0 12.839 5.135 12.839 12.839v154.050c0 7.704 5.135 12.839 12.839 12.839zM77.025-28.43v154.050c0 7.704-5.135 12.839-12.839 12.839h-51.35c-7.704 0-12.839-5.135-12.839-12.839v-166.889c0-43.649 33.379-77.025 77.025-77.025h166.889c7.704 0 12.839 5.135 12.839 12.839v51.35c0 7.704-5.135 12.839-12.839 12.839h-154.050c-7.704 0-12.839 5.135-12.839 12.839zM937.142-41.269h-154.050c-7.704 0-12.839-5.135-12.839-12.839v-51.35c0-7.704 5.135-12.839 12.839-12.839h166.889c43.649 0 77.025 33.379 77.025 77.025v166.889c0 7.704-5.135 12.839-12.839 12.839h-51.35c-7.704 0-12.839-5.135-12.839-12.839v-154.050c0-7.704-5.135-12.839-12.839-12.839zM949.981 613.448v-154.050c0-7.704 5.135-12.839 12.839-12.839h51.35c7.704 0 12.839 5.135 12.839 12.839v166.889c0 43.649-33.379 77.025-77.025 77.025h-166.889c-7.704 0-12.839-5.135-12.839-12.839v-51.35c0-7.704 5.135-12.839 12.839-12.839h154.050c7.704 0 12.839-5.135 12.839-12.839z" />
-<glyph unicode="&#xe92b;" glyph-name="influx-icon" d="M1027.006 143.127c0 0 0 0 0 0 0 9.336 0 14.006 0 18.672 0 0 0 0 0 0s0 0 0 0 0 0 0 0l-112.036 466.821c0 4.67-4.67 9.336-4.67 14.006 0 0 0 4.67-4.67 4.67-4.67 4.67-4.67 4.67-9.336 9.336 0 0 0 0 0 0-4.67 0-9.336 4.67-9.336 4.67l-466.821 140.046c-9.336 4.67-14.006 4.67-14.006 4.67s0 0 0 0c-9.336 0-14.006 0-18.672-4.67 0 0-4.67 0-4.67 0-4.67 0-9.336-4.67-14.006-9.336l-354.783-326.774c0 0 0 0 0 0s0 0 0 0 0 0 0 0c-4.67 0-4.67-4.67-9.336-9.336 0 0 0-4.67 0-4.67-4.67-4.67-4.67-9.336-4.67-14.006 0 0 0 0 0 0 0-4.67 0-9.336 0-14.006l112.036-466.821c0-4.67 0-4.67 4.67-9.336 0 0 0 0 0 0 4.67-4.67 4.67-9.336 9.336-14.006 0 0 0 0 4.67-4.67s9.336-4.67 14.006-9.336c0 0 0 0 0 0s0 0 0 0 0 0 0 0l466.821-140.046c4.67 0 9.336 0 14.006 0s9.336 0 14.006 4.67c0 0 4.67 0 4.67 0 4.67 0 4.67 4.67 9.336 4.67 0 0 0 0 0 0l354.783 326.774c4.67 4.67 4.67 4.67 9.336 9.336 0 0 0 0 0 0 4.67 4.67 4.67 9.336 9.336 18.672zM214.737-1.588l56.020 172.724 378.125-112.036-56.020-172.724-378.125 112.036zM401.466 693.975l126.042-135.378-284.761-261.42-130.71 135.378 289.429 261.42zM924.306 185.14l-182.060-42.014-88.696 378.125 182.060 42.014 88.696-378.125zM569.522 469.901l74.692-312.77-312.77 93.364 238.078 219.406zM611.535 609.947l-51.35 51.35 126.042-37.344-74.692-14.006zM130.71 273.836l56.020-56.020-23.342-74.692-32.678 130.71zM742.245 49.762l74.692 18.672-98.033-93.364 23.342 74.692z" />
-<glyph unicode="&#xe92c;" glyph-name="note" d="M1027.006 651.961c0-15.405-12.839-25.675-25.675-25.675h-539.179c-12.839 0-25.675 10.27-25.675 25.675v128.375c0 15.405 12.839 25.675 25.675 25.675h539.179c12.839 0 25.675-10.27 25.675-25.675v-128.375zM1027.006 369.535c0-12.839-12.839-25.675-25.675-25.675h-975.656c-15.405 0-25.675 12.839-25.675 25.675v128.375c0 15.405 10.27 25.675 25.675 25.675h975.656c12.839 0 25.675-10.27 25.675-25.675v-128.375zM1027.006 87.108c0-12.839-12.839-25.675-25.675-25.675h-975.656c-15.405 0-25.675 12.839-25.675 25.675v128.375c0 12.839 10.27 25.675 25.675 25.675h975.656c12.839 0 25.675-12.839 25.675-25.675v-128.375zM590.529-195.319c0-12.839-12.839-25.675-25.675-25.675h-539.179c-15.405 0-25.675 12.839-25.675 25.675v128.375c0 12.839 10.27 25.675 25.675 25.675h539.179c12.839 0 25.675-12.839 25.675-25.675v-128.375z" />
-<glyph unicode="&#xe92d;" glyph-name="organizations" horiz-adv-x="934" d="M788.927 488.574c32.678 37.344 51.35 79.358 51.35 130.71 0 102.7-84.028 186.728-186.728 186.728s-186.728-84.028-186.728-186.728c0-51.35 18.672-93.364 51.35-130.71-18.672-9.336-37.344-23.342-51.35-37.344-9.336 93.364-88.696 168.056-186.728 168.056-102.7 0-186.728-84.028-186.728-186.728 0-51.35 18.672-93.364 51.35-126.042-84.028-46.682-144.714-140.046-144.714-247.415v-186.728c0-51.35 42.014-93.364 93.364-93.364h373.457c51.35 0 93.364 42.014 93.364 93.364v93.364h280.093c51.35 0 93.364 42.014 93.364 93.364v177.392c0 107.37-56.020 205.401-144.714 252.083zM653.549 712.648c51.35 0 93.364-42.014 93.364-93.364s-42.014-93.364-93.364-93.364c-51.35 0-93.364 42.014-93.364 93.364s42.014 93.364 93.364 93.364zM186.728 432.555c0 51.35 42.014 93.364 93.364 93.364s93.364-42.014 93.364-93.364c0-51.35-42.014-93.364-93.364-93.364s-93.364 42.014-93.364 93.364zM466.821-127.63h-373.457v186.728c0 102.7 84.028 186.728 186.728 186.728s186.728-84.028 186.728-186.728v-186.728zM840.278 59.098h-280.093c0 79.358-37.344 154.050-88.696 205.401 14.006 84.028 79.358 158.72 163.387 168.056 112.036 9.336 205.401-79.358 205.401-186.728v-186.728z" />
-<glyph unicode="&#xe92e;" glyph-name="pause" d="M436.477-54.105c0-20.54-17.974-38.514-38.514-38.514h-128.375c-20.54 0-38.514 17.974-38.514 38.514v693.229c0 20.54 17.974 38.514 38.514 38.514h128.375c20.54 0 38.514-17.974 38.514-38.514v-693.229zM795.93-54.105c0-20.54-17.974-38.514-38.514-38.514h-128.375c-20.54 0-38.514 17.974-38.514 38.514v693.229c0 20.54 17.974 38.514 38.514 38.514h128.375c20.54 0 38.514-17.974 38.514-38.514v-693.229z" />
-<glyph unicode="&#xe92f;" glyph-name="pencil" horiz-adv-x="899" d="M706.067 741.823l-128.375-128.375 192.564-192.564 128.375 128.375-192.564 192.564zM0 35.757l0.691-193.127 191.873 0.565 513.502 513.502-192.564 192.564-513.502-513.502zM192.564-92.619h-128.375v128.375h64.189v-64.189h64.189v-64.189z" />
-<glyph unicode="&#xe930;" glyph-name="play" d="M785.659 320.751l-459.585 400.532c-17.974 15.405-43.649 2.569-43.649-17.974v-821.605c0-23.109 25.675-33.379 43.649-20.54l459.585 400.532c15.405 17.974 15.405 43.649 0 59.054z" />
-<glyph unicode="&#xe931;" glyph-name="ui-plus" d="M932.007 382.372h-302.967c-12.839 0-25.675 10.27-25.675 25.675v302.967c0 48.784-35.945 92.43-84.729 94.999-51.35 2.569-94.999-38.514-94.999-89.864v-308.102c0-12.839-10.27-25.675-25.675-25.675h-302.967c-48.784 0-92.43-35.945-94.999-84.729-2.569-51.35 38.514-94.999 89.864-94.999h308.102c12.839 0 25.675-10.27 25.675-25.675v-302.967c0-48.784 35.945-92.43 84.729-94.999 51.35-2.569 94.999 38.514 94.999 89.864v308.102c0 12.839 10.27 25.675 25.675 25.675h308.102c51.35 0 92.43 43.649 89.864 94.999-2.569 48.784-46.215 84.729-94.999 84.729z" />
-<glyph unicode="&#xe932;" glyph-name="refresh" d="M876.806 655.812c-77.025 77.025-176.516 127.734-285.636 144.423-135.436 20.54-270.873-12.839-381.918-93.714-110.404-81.519-182.935-200.908-203.476-336.344-5.135-35.302 18.614-68.038 53.919-73.173 3.209-0.643 6.418-0.643 9.627-0.643 31.453 0 58.411 22.466 63.546 54.559 15.405 101.417 69.964 191.28 152.767 252.258s184.861 86.012 286.278 70.607c82.16-12.196 156.619-50.708 214.387-108.478l-144.423-144.423h385.127v385.127l-150.2-150.2zM967.312 288.016c-35.302 5.135-68.038-18.614-73.173-53.919-32.093-209.895-229.151-354.959-439.045-322.865-81.519 12.196-156.619 50.708-214.387 108.478l144.423 144.423h-385.127v-385.127l150.2 150.2c77.025-77.025 177.159-127.734 285.636-144.423 26.318-3.852 51.993-5.778 77.668-5.778 249.049 0 468.572 182.294 507.084 435.836 5.778 35.302-17.974 68.038-53.276 73.173z" />
-<glyph unicode="&#xe933;" glyph-name="remove" d="M641.879 292.508l236.853 236.853c25.032 25.032 25.032 66.114 0 90.504l-37.871 37.871c-25.032 25.032-66.114 25.032-90.504 0l-236.853-236.853-236.853 236.853c-25.032 25.032-66.114 25.032-90.504 0l-37.871-37.871c-25.032-25.032-25.032-66.114 0-90.504l236.853-236.853-236.853-236.853c-25.032-25.032-25.032-66.114 0-90.504l37.871-37.871c25.032-25.032 66.114-25.032 90.504 0l236.853 236.853 236.853-236.853c25.032-25.032 66.114-25.032 90.504 0l37.871 37.871c25.032 25.032 25.032 66.114 0 90.504l-236.853 236.853z" />
-<glyph unicode="&#xe934;" glyph-name="alert-circle" d="M983.252 301.692c0 129.833-52.667 247.48-137.741 332.51s-202.679 137.741-332.51 137.741-247.48-52.667-332.51-137.741-137.741-202.679-137.741-332.51 52.667-247.48 137.741-332.51 202.679-137.741 332.51-137.741 247.48 52.667 332.51 137.741 137.741 202.679 137.741 332.51zM897.753 301.692c0-106.277-43.007-202.379-112.689-272.062s-165.785-112.689-272.062-112.689-202.379 43.007-272.062 112.689-112.689 165.785-112.689 272.062 43.007 202.379 112.689 272.062 165.785 112.689 272.062 112.689 202.379-43.007 272.062-112.689 112.689-165.785 112.689-272.062zM470.251 472.693v-171.001c0-23.598 19.153-42.751 42.751-42.751s42.751 19.153 42.751 42.751v171.001c0 23.598-19.153 42.751-42.751 42.751s-42.751-19.153-42.751-42.751zM513.001 87.942c23.598 0 42.751 19.153 42.751 42.751s-19.153 42.751-42.751 42.751-42.751-19.153-42.751-42.751 19.153-42.751 42.751-42.751z" />
-<glyph unicode="&#xe935;" glyph-name="crown" d="M187.246-95.029c-28.216 0-51.3 20.52-58.996 46.17l-125.686 492.481c-5.13 17.956 2.566 38.476 17.956 48.736 15.39 12.826 35.91 12.826 53.866 2.566l233.416-148.77 166.726 246.24c7.696 12.826 23.086 20.52 38.476 20.52s30.78-7.696 38.476-20.52l169.29-246.24 233.416 148.77c15.39 10.26 38.476 10.26 53.866-2.566s23.086-30.78 17.956-51.3l-128.25-489.916c-7.696-28.216-30.78-46.17-58.996-46.17h-651.512zM202.636-28.339v0c0 0 0 0 0 0zM200.070-18.079h625.862l105.166 407.836-182.116-117.99c-28.216-17.956-64.126-10.26-82.080 15.39l-153.9 223.156-153.9-223.156c-17.956-25.65-53.866-33.346-82.080-17.956l-182.116 117.99 105.166-405.271zM995.223 430.797v0c0 0 0 0 0 0zM76.95 461.578v0c0 0 0 0 0 0zM949.053 461.578c0 0 0 0 0 0v0zM487.351 548.788c2.566 0 2.566 0 0 0v0zM536.087 548.788v0c0 0 0 0 0 0z" />
-<glyph unicode="&#xe936;" glyph-name="trash" d="M937.142 677.637h-195.131l-66.755 110.404c-5.135 10.27-17.974 17.974-30.81 17.974h-261.886c-12.839 0-25.675-7.704-33.379-17.974l-64.189-110.404h-195.131c-20.54 0-38.514-17.974-38.514-38.514v-102.7c0-20.54 17.974-38.514 38.514-38.514h847.28c20.54 0 38.514 17.974 38.514 38.514v102.7c0 20.54-17.974 38.514-38.514 38.514zM405.667 728.987h215.671l30.81-51.35h-277.292l30.81 51.35zM860.117 446.56h-693.229c-10.27 0-20.54-5.135-28.244-12.839s-10.27-17.974-10.27-28.244l51.35-590.529c2.569-20.54 17.974-35.945 38.514-35.945h590.529c20.54 0 35.945 15.405 38.514 35.945l51.35 590.529c0 10.27-2.569 20.54-10.27 28.244s-17.974 12.839-28.244 12.839z" />
-<glyph unicode="&#xe937;" glyph-name="triangle" d="M984.213 67.852l-359.452 607.645c-17.118 29.954-47.071 51.35-81.304 59.908s-68.468 4.279-98.421-12.839c-17.118-8.557-34.232-25.675-42.793-42.793 0 0 0 0 0 0l-359.452-611.924c-34.232-59.908-12.839-141.214 47.071-175.446 17.118-12.839 38.514-17.118 59.908-17.118h727.462c34.232 0 68.468 12.839 89.864 38.514 25.675 25.675 38.514 55.629 38.514 89.864-4.279 21.396-8.557 47.071-21.396 64.189zM907.188-26.29c-8.557-8.557-21.396-12.839-29.954-12.839h-727.462c-8.557 0-12.839 0-21.396 4.279-21.396 12.839-25.675 38.514-17.118 59.908l363.732 603.366c4.279 4.279 8.557 12.839 12.839 12.839 21.396 12.839 47.071 4.279 59.908-12.839l363.732-603.366c4.279-4.279 4.279-12.839 4.279-21.396 4.279-12.839-4.279-21.396-8.557-29.954z" />
-<glyph unicode="&#xe938;" glyph-name="x" d="M573.411 303.207l226.796 226.796c17.118 17.118 17.118 42.793 0 59.908s-42.793 17.118-59.908 0l-226.796-226.796-226.796 226.796c-17.118 17.118-42.793 17.118-59.908 0s-17.118-42.793 0-59.908l226.796-226.796-226.796-226.796c-17.118-17.118-17.118-42.793 0-59.908 8.557-8.557 17.118-12.839 29.954-12.839s21.396 4.279 29.954 12.839l226.796 226.796 226.796-226.796c8.557-8.557 21.396-12.839 29.954-12.839s21.396 4.279 29.954 12.839c17.118 17.118 17.118 42.793 0 59.908l-226.796 226.796z" />
-<glyph unicode="&#xe939;" glyph-name="wrench-2" d="M200.266-190.184c-43.649 0-87.295 17.974-120.674 51.35-28.244 25.675-48.784 71.89-48.784 118.105 0 43.649 17.974 84.729 48.784 118.105l331.209 328.642c-2.569 17.974-5.135 35.945-5.135 53.919 0 161.754 133.51 295.264 295.264 295.264 35.945 0 66.755-7.704 92.43-15.405s41.080-28.244 43.649-48.784c2.569-17.974 0-35.945-10.27-51.35l-5.135-7.704-110.404-110.404c-2.569-2.569-5.135-5.135-5.135-7.704s2.569-5.135 5.135-7.704l38.514-38.514c5.135-5.135 12.839-5.135 17.974 0l107.835 107.835c12.839 17.974 38.514 25.675 59.054 20.54 20.54-2.569 41.080-17.974 48.784-41.080 7.704-28.244 15.405-59.054 15.405-94.999 0-161.754-133.51-295.264-295.264-295.264-17.974 0-35.945 2.569-53.919 5.135l-331.209-331.209c-33.379-30.81-74.459-48.784-118.105-48.784zM700.932 698.177c-120.674 0-218.239-97.565-218.239-218.239 0-20.54 2.569-35.945 7.704-59.054l5.135-20.54-359.452-359.452c-17.974-17.974-28.244-41.080-28.244-61.62 0-17.974 7.704-46.215 25.675-61.62 38.514-38.514 94.999-38.514 128.375-5.135l359.452 359.452 20.54-5.135c17.974-5.135 35.945-7.704 56.485-7.704 120.674 0 218.239 97.565 218.239 218.239 0 15.405-2.569 28.244-5.135 46.215l-89.864-92.43c-35.945-35.945-89.864-35.945-125.809 0l-38.514 38.514c-17.974 17.974-25.675 38.514-25.675 64.189 0 23.109 10.27 46.215 25.675 64.189l94.999 94.999c-20.54 2.569-35.945 5.135-51.35 5.135z" />
-<glyph unicode="&#xe93a;" glyph-name="chat" horiz-adv-x="882" d="M807.721 592.32h-734.293c-36.715 0-73.43-36.715-73.43-73.43v-440.575c0-36.715 36.715-73.43 73.43-73.43h293.717l293.717-220.288v220.288h146.858c36.715 0 73.43 36.715 73.43 73.43v440.575c0 36.715-36.715 73.43-73.43 73.43z" />
-<glyph unicode="&#xe93b;" glyph-name="bell" horiz-adv-x="964" d="M947.697 53.075l-35.337 61.038c-12.852 22.488-25.7 41.764-35.337 57.824-35.337 54.612-54.612 86.739-67.464 150.988l-44.976 215.24c-25.7 138.14-147.776 234.515-285.915 237.727h-6.424c-141.352 0-266.64-106.013-289.128-247.365l-28.912-183.114c-12.852-86.739-38.552-131.714-86.739-208.815-6.424-12.852-16.064-25.7-22.488-41.764l-22.488-41.764c-25.7-41.764-25.7-96.376 0-138.14 19.276-44.976 67.464-70.676 118.864-70.676h215.24c12.852-54.612 64.252-96.376 125.288-96.376 57.824 0 112.439 41.764 125.288 96.376h215.24c48.188 0 99.588 25.7 125.288 70.676 22.488 41.764 22.488 96.376 0 138.14zM822.408-59.363h-681.056c-32.124 0-54.612 35.337-38.552 64.252l22.488 41.764c61.038 106.013 106.013 160.627 122.076 282.703l28.912 183.114c19.276 93.164 96.376 167.052 195.964 167.052h3.212c93.164 0 173.476-67.464 189.54-157.414l44.976-215.24c19.276-106.013 57.824-147.776 115.652-240.94l35.337-61.038c16.064-28.912-6.424-64.252-38.552-64.252z" />
-<glyph unicode="&#xe93c;" glyph-name="disks-nav" d="M513.502 712.648c-163.387 0-326.774-42.014-326.774-140.046v-560.185c0-98.033 163.387-140.046 326.774-140.046s326.774 42.014 326.774 140.046v560.185c0 98.033-163.387 140.046-326.774 140.046zM746.913 390.541c-14.006-14.006-93.364-51.35-233.41-51.35s-219.406 37.344-233.41 51.35v79.358c60.686-23.342 149.383-37.344 233.41-37.344s172.724 14.006 233.41 37.344v-79.358zM746.913 203.813c-14.006-14.006-93.364-51.35-233.41-51.35s-219.406 37.344-233.41 51.35v79.358c60.686-23.342 149.383-37.344 233.41-37.344s172.724 14.006 233.41 37.344v-79.358zM513.502 619.284c130.71 0 205.401-28.008 228.742-46.682-23.342-18.672-98.033-46.682-228.742-46.682s-205.401 28.008-228.742 46.682c23.342 18.672 98.033 46.682 228.742 46.682zM513.502-34.266c-140.046 0-219.406 32.678-233.41 51.35v79.358c60.686-23.342 149.383-37.344 233.41-37.344s172.724 14.006 233.41 37.344v-79.358c-14.006-18.672-93.364-51.35-233.41-51.35z" />
-<glyph unicode="&#xe93d;" glyph-name="wrench-nav" d="M186.728-174.313c-37.344 0-74.692 14.006-98.033 42.014-56.020 56.020-56.020 144.714 0 196.064l340.779 340.779c-4.67 28.008-9.336 51.35-9.336 74.692 0 154.050 126.042 280.093 280.093 280.093 42.014 0 88.696-9.336 130.71-32.678 14.006-4.67 23.342-18.672 23.342-32.678s-4.67-28.008-14.006-42.014l-121.373-121.373 37.344-37.344 121.373 121.373c9.336 9.336 23.342 14.006 42.014 14.006 14.006-4.67 28.008-9.336 32.678-23.342 18.672-42.014 28.008-84.028 28.008-126.042 0-154.050-126.042-280.093-280.093-280.093-23.342 0-46.682 4.67-70.022 9.336l-340.779-340.779c-28.008-28.008-65.356-42.014-102.7-42.014zM700.231 665.965c-102.7 0-186.728-84.028-186.728-186.728 0-23.342 4.67-46.682 14.006-70.022 4.67-18.672 4.67-37.344-9.336-51.35l-364.121-364.121c-18.672-18.672-18.672-46.682 0-65.356s46.682-18.672 65.356 0l364.121 364.121c14.006 14.006 32.678 18.672 51.35 9.336 23.342-9.336 46.682-14.006 70.022-14.006 102.7 0 186.728 84.028 186.728 186.728 0 4.67 0 9.336 0 18.672l-98.033-98.033c-18.672-18.672-46.682-18.672-65.356 0l-102.7 102.7c-14.006 9.336-18.672 18.672-18.672 32.678s4.67 23.342 14.006 32.678l98.033 102.7c-4.67 0-14.006 0-18.672 0z" />
-<glyph unicode="&#xe93e;" glyph-name="user" d="M591.106 295.3c59.112 28.272 100.232 89.952 100.232 161.912 0 100.232-79.672 179.902-179.902 179.902s-179.902-79.672-179.902-179.902c0-71.96 41.12-131.072 100.232-161.912-84.812-20.56-177.332-120.792-177.332-233.872v-146.492c0-12.852 7.712-25.7 17.992-25.7h478.024c10.28 0 17.992 10.28 17.992 25.7v146.492c0 113.080-89.952 210.742-177.332 233.872z" />
-<glyph unicode="&#xe93f;" glyph-name="cloud" d="M838.224-50.826h-648.437c-102.8 0-189.786 86.986-189.786 197.694 0 79.077 43.491 150.248 110.709 181.878 0 7.909 0 15.814 0 23.723 0 150.248 114.663 268.864 257.002 268.864 86.986 0 166.063-43.491 213.51-118.617 23.723 7.909 47.446 11.863 71.169 11.863 102.8 0 189.786-71.169 217.463-173.971 90.941-15.814 158.154-94.893 158.154-193.741 0-110.709-83.032-197.694-189.786-197.694zM367.711 542.256c-98.847 0-177.925-86.986-177.925-189.786 0-15.814 0-27.677 3.954-43.491l7.909-39.54-35.586-7.909c-51.4-11.863-86.986-59.309-86.986-114.663 0-67.217 47.446-118.617 110.709-118.617h648.437c59.309 0 110.709 51.4 110.709 118.617s-47.446 118.617-110.709 118.617h-39.54l-3.954 35.586c-7.909 79.077-71.169 138.386-142.341 138.386-23.723 0-47.446-7.909-71.169-19.768l-39.54-23.723-19.768 39.54c-23.723 67.217-86.986 106.754-154.201 106.754z" />
-<glyph unicode="&#xe940;" glyph-name="users-trio" horiz-adv-x="1335" d="M1184.782 228.479c43.692 41.12 69.392 102.8 69.392 164.481 0 131.072-102.8 231.302-231.302 231.302-46.26 0-89.952-12.852-125.932-35.98-20.56 107.94-113.080 187.612-228.732 187.612-118.22 0-208.172-82.24-228.732-190.182-35.98 23.132-77.1 35.98-125.932 35.98-131.072 0-231.302-102.8-231.302-231.302 0-64.252 25.7-120.792 69.392-164.481-82.24-46.26-151.632-143.921-151.632-254.432v-156.772c0-35.98 25.7-66.82 56.54-66.82h511.434c33.412 0 59.112 30.84 61.68 66.82v87.38h77.1v-87.38c0-35.98 25.7-66.82 56.54-66.82h511.434c33.412 0 59.112 30.84 61.68 66.82v156.772c0 110.512-71.96 208.172-151.632 257.002zM547.416-175.014h-475.454v143.921c0 97.66 84.812 192.752 159.341 210.742 15.42 5.14 25.7 17.992 28.272 33.412s-5.14 30.84-20.56 38.552c-51.4 28.272-84.812 79.672-84.812 138.781 0 87.38 66.82 154.201 154.201 154.201s154.201-69.392 154.201-154.201c0-59.112-33.412-113.080-84.812-138.781-12.852-7.712-20.56-23.132-20.56-38.552s12.852-28.272 28.272-33.412c77.1-20.56 159.341-110.512 159.341-210.742v-143.921zM706.757-20.814h-77.1c-2.572 107.94-74.532 200.462-151.632 249.292 23.132 20.56 41.12 48.832 53.972 79.672 17.992 12.852 35.98 23.132 56.54 25.7 15.42 5.14 25.7 17.992 28.272 33.412s-5.14 30.84-20.56 38.552c-20.56 12.852-41.12 28.272-53.972 46.26-5.14 23.132-15.42 46.26-28.272 64.252-2.572 7.712-2.572 17.992-2.572 25.7 0 87.38 66.82 154.201 154.201 154.201s154.201-69.392 154.201-154.201c0-59.112-33.412-113.080-84.812-138.781-12.852-7.712-20.56-23.132-20.56-38.552s12.852-28.272 28.272-33.412c23.132-5.14 48.832-20.56 71.96-38.552 12.852-25.7 28.272-48.832 48.832-66.82-84.812-46.26-154.201-141.352-156.772-246.722zM1254.172-175.014h-475.454v143.921c0 97.66 84.812 192.752 159.341 210.742 15.42 5.14 25.7 17.992 28.272 33.412s-5.14 30.84-20.56 38.552c-51.4 28.272-84.812 79.672-84.812 138.781 0 87.38 66.82 154.201 154.201 154.201s154.201-69.392 154.201-154.201c0-59.112-33.412-113.080-84.812-138.781-12.852-7.712-20.56-23.132-20.56-38.552s12.852-28.272 28.272-33.412c77.1-20.56 159.341-110.512 159.341-210.742v-143.921z" />
-<glyph unicode="&#xe941;" glyph-name="nav-chat" d="M731.468-189.212c-7.909 0-15.814 3.954-23.723 7.909l-280.726 209.555h-276.771c-59.309 0-110.709 55.354-110.709 110.709v347.942c0 59.309 55.354 114.663 110.709 114.663h723.561c59.309 0 114.663-55.354 114.663-114.663v-347.942c0-59.309-55.354-110.709-110.709-110.709h-106.754v-177.925c0-15.814-7.909-27.677-23.723-35.586-3.954-3.954-7.909-3.954-15.814-3.954zM150.248 522.487c-11.863 0-31.632-19.768-31.632-35.586v-347.942c0-15.814 19.768-31.632 31.632-31.632h288.634c7.909 0 15.814-3.954 23.723-7.909l225.371-170.018v138.386c0 23.723 15.814 39.54 39.54 39.54h146.294c15.814 0 31.632 19.768 31.632 31.632v347.942c3.954 15.814-15.814 35.586-27.677 35.586h-727.514z" />
-<glyph unicode="&#xe94c;" glyph-name="map2" d="M673.973 581.354l-320.939 128.375-353.033-128.375v-770.254l353.033 128.375 320.939-128.375 353.033 128.375v770.254l-353.033-128.375zM385.127 627.76l256.751-102.7v-631.988l-256.751 102.698v631.99zM64.189 536.395l256.751 93.363v-633.655l-256.751-93.361v633.653zM962.817-15.565l-256.751-93.365v633.655l256.751 93.363v-633.653z" />
-<glyph unicode="&#xe956;" glyph-name="eye-closed" d="M1020.298 277.31c-41.12 77.1-100.232 143.921-172.192 192.752l-128.5-128.5c7.712-23.132 12.852-48.832 12.852-77.1 0-120.792-97.66-218.452-218.452-218.452-28.272 0-53.972 5.14-77.1 12.852l-82.24-82.24c51.4-12.852 105.372-20.56 159.341-20.56 215.882 0 408.634 113.080 506.294 292.983l7.712 12.852-7.712 15.42zM179.902 56.287l128.5 128.5c-7.712 23.132-12.852 48.832-12.852 77.1 0 120.792 97.66 218.452 218.452 218.452 28.272 0 53.972-5.14 77.1-12.852l82.24 82.24c-51.4 12.852-105.372 20.56-159.341 20.56-218.452 0-411.204-113.080-506.294-292.983l-7.712-15.42 7.712-15.42c41.12-77.1 100.232-141.352 172.192-190.182zM128.5-162.166c-10.28 0-20.56 2.572-28.272 10.28-15.42 15.42-15.42 38.552 0 53.972l771.007 771.007c15.42 15.42 38.552 15.42 53.972 0s15.42-38.552 0-53.972l-771.007-771.007c-5.14-7.712-15.42-10.28-25.7-10.28z" />
-<glyph unicode="&#xe957;" glyph-name="eye-open" d="M1020.298 277.31c-97.66 179.902-290.413 292.983-506.294 292.983-218.452 0-411.204-113.080-506.294-292.983l-7.712-15.42 7.712-15.42c97.66-179.902 290.413-292.983 506.294-292.983s408.634 113.080 506.294 292.983l7.712 15.42-7.712 15.42zM514.004 43.437c-120.792 0-218.452 97.66-218.452 218.452s97.66 218.452 218.452 218.452 218.452-97.66 218.452-218.452-97.66-218.452-218.452-218.452zM552.556 300.44c-25.7 25.7-25.7 66.82 0 89.952 25.7 25.7 66.82 25.7 89.952 0s25.7-66.82 0-89.952c-25.7-25.7-64.252-25.7-89.952 0z" />
-<glyph unicode="&#xe965;" glyph-name="book-pencil" horiz-adv-x="908" d="M895.781 468.088l-118.385 114.439c-15.784 15.784-39.462 15.784-55.246 0l-394.616-394.616c-7.893-7.893-11.839-15.784-11.839-27.623v-157.846h157.846c11.839 0 19.73 3.946 27.623 11.839l394.616 398.563c7.893 3.946 11.839 15.784 11.839 27.623 0 7.893-3.946 19.73-11.839 27.623zM457.756 81.364h-63.139v63.139l355.155 355.155 63.139-63.139-355.155-355.155zM730.041 148.449l-51.3-51.3c-3.946-3.946-7.893-11.839-7.893-19.73v-193.363c0-23.677-15.784-39.462-39.462-39.462h-473.539c-23.677 0-39.462 15.784-39.462 39.462v118.385c23.677 0 39.462 15.784 39.462 39.462s-15.784 39.462-39.462 39.462v78.923c23.677 0 39.462 15.784 39.462 39.462s-15.784 39.462-39.462 39.462v78.923c23.677 0 39.462 15.784 39.462 39.462s-15.784 39.462-39.462 39.462v78.923c23.677 0 39.462 15.784 39.462 39.462s-15.784 39.462-39.462 39.462v118.385c0 23.677 15.784 39.462 39.462 39.462h473.539c23.677 0 39.462-15.784 39.462-39.462v-31.57c23.677 19.73 51.3 31.57 78.923 31.57 0 67.085-51.3 118.385-118.385 118.385h-473.539c-67.085 0-118.385-51.3-118.385-118.385v-118.385c-23.677 0-39.462-15.784-39.462-39.462s15.784-39.462 39.462-39.462v-78.923c-23.677 0-39.462-15.784-39.462-39.462s15.784-39.462 39.462-39.462v-78.923c-23.677 0-39.462-15.784-39.462-39.462s15.784-39.462 39.462-39.462v-78.923c-23.677 0-39.462-15.784-39.462-39.462s15.784-39.462 39.462-39.462v-118.385c0-67.085 51.3-118.385 118.385-118.385h473.539c67.085 0 118.385 51.3 118.385 118.385v256.5c0 11.839-11.839 15.784-19.73 7.893z" />
-<glyph unicode="&#xe9da;" glyph-name="heart" d="M757.405 709.73c-107.945 0-200.846-87.812-243.878-179.525-43.064 91.712-135.977 179.525-243.93 179.525-148.817 0-269.597-120.794-269.597-269.621 0-302.732 305.394-382.112 513.525-681.412 196.73 297.446 513.48 388.343 513.48 681.412 0 148.827-120.784 269.621-269.601 269.621z" />
-<glyph unicode="&#xea2e;" glyph-name="loop2" d="M892.292 607.11c-93.884 102.516-228.823 166.809-378.789 166.809-283.6 0-513.502-229.903-513.502-513.502h96.282c0 230.425 186.796 417.221 417.221 417.221 123.38 0 234.228-53.574 310.605-138.711l-150.135-150.133h353.033v353.033l-134.714-134.714zM930.724 260.415c0-230.425-186.796-417.221-417.221-417.221-123.38 0-234.228 53.574-310.603 138.711l150.133 150.133h-353.033v-353.033l134.714 134.714c93.884-102.516 228.823-166.809 378.789-166.809 283.6 0 513.502 229.903 513.502 513.502h-96.282z" />
-<glyph unicode="&#xeab0;" glyph-name="github" d="M513.51 761.238c-283.568 0-513.51-229.891-513.51-513.5 0-226.878 147.135-419.36 351.164-487.262 25.661-4.753 35.094 11.143 35.094 24.704 0 12.24-0.48 52.695-0.699 95.603-142.866-31.066-173.011 60.587-173.011 60.587-23.351 59.35-57.016 75.135-57.016 75.135-46.587 31.871 3.519 31.214 3.519 31.214 51.55-3.622 78.707-52.922 78.707-52.922 45.807-78.501 120.127-55.802 149.442-42.684 4.6 33.182 17.903 55.843 32.602 68.665-114.063 12.981-233.96 57.018-233.96 253.775 0 56.063 20.064 101.871 52.916 137.831-5.331 12.939-22.92 65.164 4.967 135.898 0 0 43.132 13.791 141.254-52.643 40.956 11.381 84.885 17.087 128.53 17.285 43.631-0.198 87.592-5.904 128.632-17.285 98.022 66.439 141.069 52.643 141.069 52.643 27.953-70.735 10.38-122.96 5.051-135.898 32.916-35.961 52.85-81.772 52.85-137.831 0-197.231-120.129-240.655-234.477-253.365 18.418-15.938 34.826-47.184 34.826-95.091 0-68.709-0.599-124.007-0.599-140.92 0-13.667 9.249-29.681 35.274-24.638 203.919 67.974 350.869 260.388 350.869 487.194 0 283.61-229.907 513.5-513.494 513.5z" />
-<glyph unicode="&#xeabd;" glyph-name="tux" d="M569.322 34.839c-82.184-38.229-158.623-37.827-209.955-34.119-61.232 4.422-110.482 21.187-132.129 35.837-13.339 9.033-31.477 5.537-40.509-7.806-9.031-13.341-5.535-31.479 7.806-40.509 34.8-23.555 96.35-41.074 160.633-45.715 10.899-0.787 22.864-1.281 35.751-1.281 55.947 0 126.998 5.331 203.014 40.69 14.606 6.799 20.938 24.146 14.146 38.754-6.797 14.608-24.148 20.932-38.756 14.15zM893.564 78.065c2.795 253.429 28.846 732.349-456.306 693.642-479.002-38.556-351.994-544.562-359.133-714.040-6.326-89.648-36.083-199.231-78.124-310.755h129.478c13.305 47.26 23.093 93.996 27.313 138.555 7.806-5.443 16.156-10.704 25.066-15.745 14.5-8.542 26.962-19.901 40.157-31.927 30.834-28.099 65.782-59.949 134.105-63.938 4.584-0.262 9.201-0.394 13.715-0.394 69.097 0 116.355 30.243 154.33 54.541 18.194 11.645 33.917 21.703 48.707 26.53 42.033 13.159 78.763 34.398 106.216 61.432 4.288 4.22 8.266 8.562 11.998 12.987 15.291-56.043 36.223-119.106 59.462-182.037h276.459c-66.369 102.524-134.831 202.968-133.442 331.153zM124.474 215.933c0 0.016 0 0.030-0.002 0.046-4.761 82.705 34.812 152.278 88.384 155.391 53.568 3.115 100.854-61.408 105.613-144.114 0-0.014 0.004-0.030 0.004-0.044 0.256-4.458 0.368-8.873 0.37-13.245-16.975-4.268-32.286-10.466-46.007-17.681-0.052 0.615-0.092 1.219-0.152 1.836 0 0.008 0 0.018 0 0.026-4.582 46.948-29.659 82.4-56.017 79.189-26.358-3.213-44.009-43.879-39.427-90.825 0-0.010 0.004-0.018 0.004-0.026 1.998-20.468 7.892-38.75 16.090-52.597-2.040-1.61-7.808-5.83-14.448-10.686-4.985-3.646-11.053-8.082-18.368-13.469-19.939 26.172-33.605 63.766-36.045 106.202zM667.213 11.509c-1.906-43.715-59.082-84.841-111.909-101.341l-0.296-0.096c-21.963-7.123-41.55-19.657-62.287-32.926-34.834-22.29-70.853-45.34-122.882-45.34-3.413 0-6.915 0.104-10.356 0.296-47.655 2.787-69.946 23.101-98.168 48.82-14.887 13.565-30.28 27.595-50.123 39.238l-0.424 0.244c-42.832 24.176-69.416 54.241-71.115 80.429-0.845 13.019 4.953 24.29 17.233 33.499 26.714 20.032 44.609 33.118 56.449 41.781 13.149 9.615 17.119 12.516 20.060 15.309 2.102 1.992 4.376 4.2 6.825 6.58 24.518 23.843 65.552 63.748 128.526 63.748 38.518 0 81.135-14.842 126.54-44.031 21.387-13.92 39.999-20.346 63.566-28.484 16.204-5.593 34.57-11.938 59.166-22.47l0.396-0.164c22.946-9.431 50.043-26.642 48.804-55.094zM654.562 114.181c-4.412 2.22-9.001 4.332-13.783 6.304-22.172 9.483-39.949 15.922-54.693 21.061 8.14 15.942 13.199 35.825 13.663 57.41 0 0.010 0 0.022 0 0.030 1.129 52.527-25.363 95.175-59.17 95.255-33.809 0.078-62.133-42.437-63.262-94.965 0-0.010 0-0.018 0-0.028-0.038-1.72-0.042-3.425-0.020-5.125-20.822 9.579-41.3 16.538-61.346 20.82-0.092 1.974-0.204 3.944-0.244 5.938 0 0.016 0 0.036 0 0.050-1.944 95.691 56.767 174.902 131.138 176.92 74.368 2.020 136.227-73.916 138.177-169.606 0-0.018 0-0.038 0-0.052 0.877-43.272-10.69-83.109-30.46-114.011z" />
-<glyph unicode="&#xeabe;" glyph-name="appleinc" d="M793.821 228.229c-1.297 130.063 106.068 192.44 110.866 195.539-60.329 88.278-154.302 100.372-187.791 101.769-79.976 8.098-156.052-47.086-196.642-47.086-40.486 0-103.121 45.889-169.447 44.684-87.171-1.295-167.548-50.685-212.433-128.757-90.568-157.157-23.195-389.981 65.080-517.44 43.134-62.387 94.568-132.463 162.1-129.961 65.032 2.597 89.624 42.081 168.248 42.081s100.722-42.081 169.546-40.79c69.978 1.299 114.317 63.584 157.151 126.165 49.534 72.381 69.93 142.455 71.131 146.053-1.554 0.709-136.459 52.389-137.811 207.742zM664.507 609.916c35.843 43.484 60.037 103.815 53.436 164.002-51.628-2.102-114.212-34.392-151.253-77.778-33.238-38.49-62.331-99.918-54.533-158.901 57.634-4.496 116.47 29.291 152.35 72.677z" />
-<glyph unicode="&#xeac2;" glyph-name="windows8" d="M0.35 260.415l-0.35 312.99 385.127 52.297v-365.287zM449.315 635.029l513.374 74.701v-449.315h-513.374zM962.815 196.227l-0.126-449.315-513.374 72.227v377.088zM385.127-172.689l-384.814 52.748-0.020 316.167h384.834z" />
+<glyph unicode="&#xe900;" glyph-name="influx-logo" horiz-adv-x="1005" d="M747.683 94.113l236.844 53.406c4.644 0 6.966 2.322 9.288 4.644s4.644 4.644 6.966 6.966c2.322 2.322 2.322 6.966 4.644 11.61 0 4.644 0 6.966 0 11.61l-102.168 436.535c-2.322 6.966-6.966 13.932-13.932 16.254-6.966 4.644-13.932 4.644-20.898 2.322l-234.522-51.084c-6.966-2.322-13.932-6.966-16.254-13.932-4.644-6.966-4.644-13.932-2.322-20.898l99.846-436.535c2.322-6.966 6.966-13.932 13.932-16.254 4.644-4.644 11.61-6.966 18.576-4.644zM666.413-177.56l287.927 267.029c11.61 11.61 6.966 18.576-6.966 11.61l-197.37-44.118c-9.288-2.322-16.254-6.966-20.898-11.61-6.966-4.644-11.61-13.932-13.932-20.898l-60.372-192.726c-4.644-16.254 0-18.576 11.61-9.288zM141.642-89.324l429.569-132.354c6.966-2.322 13.932 0 20.898 4.644s11.61 9.288 13.932 16.254l71.982 232.2c0 4.644 2.322 6.966 0 11.61 0 4.644-2.322 6.966-2.322 11.61-2.322 2.322-4.644 6.966-6.966 9.288s-6.966 4.644-9.288 4.644l-429.569 127.71c-6.966 2.322-16.254 2.322-20.898-2.322-6.966-4.644-11.61-9.288-13.932-16.254l-71.982-229.878c-2.322-6.966-2.322-13.932 2.322-20.898 2.322-9.288 9.288-13.932 16.254-16.254zM2.322 384.363l88.236-383.129c2.322-13.932 9.288-13.932 13.932 0l58.050 192.726c2.322 9.288 2.322 16.254 0 25.542s-4.644 16.254-11.61 23.22l-136.998 148.608c-9.288 9.288-16.254 6.966-11.61-6.966zM339.011 793.034l-329.723-306.503c-6.966-4.644-9.288-11.61-9.288-18.576s2.322-13.932 6.966-20.898l164.862-178.794c4.644-4.644 11.61-9.288 18.576-9.288s13.932 2.322 20.898 6.966l329.723 308.825c4.644 4.644 9.288 11.61 9.288 18.576s-2.322 13.932-6.966 20.898l-164.862 178.794c-2.322 2.322-4.644 4.644-9.288 6.966-2.322 0-6.966 0-9.288 0-4.644 0-6.966 0-11.61-2.322-4.644 0-6.966-2.322-9.288-4.644zM657.125 101.079c13.932-4.644 25.542 4.644 20.898 18.576l-95.202 413.315c-4.644 13.932-16.254 18.576-27.864 9.288l-311.147-290.249c-11.61-11.61-9.288-23.22 6.966-27.864l406.349-123.066zM819.664 676.934l-376.163 116.1c-13.932 4.644-18.576-2.322-4.644-13.932l136.998-148.608c6.966-4.644 13.932-9.288 20.898-11.61 9.288-2.322 16.254-2.322 25.542 0l197.37 44.118c16.254 2.322 16.254 9.288 0 13.932z" />
+<glyph unicode="&#xe901;" glyph-name="influx-logotype" horiz-adv-x="4853" d="M90.558 523.683c-25.542 0-46.44 9.288-65.016 25.542-16.254 16.254-25.542 37.152-25.542 60.372 0 25.542 9.288 44.118 25.542 60.372 18.576 16.254 39.474 25.542 65.016 25.542s46.44-9.288 62.694-25.542 25.542-37.152 25.542-60.372-9.288-44.118-25.542-60.372c-18.576-16.254-39.474-25.542-62.694-25.542zM9.288-1.088v455.111h157.896v-455.111h-157.896zM276.317-1.088v455.111h155.574l2.322-55.728c11.61 23.22 27.864 39.474 51.084 51.084s48.762 18.576 78.948 18.576c51.084 0 90.558-16.254 116.1-48.762 27.864-32.508 39.474-78.948 39.474-141.642v-276.317h-157.896v243.81c0 53.406-20.898 81.27-60.372 81.27-20.898 0-39.474-6.966-51.084-23.22-9.288-13.932-16.254-37.152-16.254-62.694v-241.488h-157.896zM870.748-1.088v327.401h-71.982v127.71h71.982v44.118c0 69.66 16.254 123.066 51.084 162.54 34.83 37.152 83.592 58.050 146.286 58.050 18.576 0 34.83-2.322 51.084-4.644 16.254-4.644 30.186-6.966 41.796-11.61l-6.966-132.354c-6.966 2.322-13.932 4.644-23.22 6.966s-16.254 2.322-25.542 2.322c-25.542 0-44.118-6.966-55.728-20.898s-18.576-37.152-18.576-69.66v-32.508h106.812v-127.71h-106.812v-327.401l-160.218-2.322zM1207.438-1.088v712.853h157.896v-712.853h-157.896zM1623.075-15.020c-48.762 0-88.236 16.254-113.778 46.44-25.542 32.508-39.474 78.948-39.474 141.642v280.961h160.218v-248.454c0-27.864 4.644-46.44 13.932-60.372s25.542-18.576 46.44-18.576 37.152 6.966 48.762 20.898c11.61 16.254 18.576 37.152 18.576 65.016v241.488h157.896v-455.111h-155.574l-2.322 55.728c-11.61-23.22-30.186-39.474-53.406-51.084s-51.084-18.576-81.27-18.576zM1987.628-1.088l164.862 234.522-155.574 220.59h176.472l74.304-123.066 71.982 123.066h169.506l-155.574-222.912 164.862-232.2h-178.794l-83.592 136.998-81.27-136.998h-167.184zM2777.107-15.020c-39.474 0-76.626 9.288-109.134 30.186s-55.728 46.44-74.304 83.592c-18.576 34.83-27.864 76.626-27.864 120.744s9.288 83.592 27.864 118.422c20.898 34.83 46.44 65.016 78.948 83.592 32.508 20.898 69.66 32.508 111.456 32.508 32.508 0 62.694-9.288 90.558-25.542s51.084-39.474 67.338-69.66v352.943h74.304v-712.853h-71.982l-2.322 81.27c-18.576-30.186-41.796-53.406-69.66-69.66-25.542-18.576-60.372-25.542-95.202-25.542zM2795.683 52.317c30.186 0 58.050 6.966 78.948 20.898 23.22 13.932 41.796 34.83 53.406 58.050 13.932 25.542 20.898 53.406 20.898 88.236 0 32.508-6.966 62.694-20.898 88.236s-30.186 44.118-53.406 58.050-48.762 20.898-78.948 20.898-55.728-6.966-78.948-20.898-41.796-34.83-53.406-58.050c-13.932-25.542-18.576-53.406-18.576-88.236 0-32.508 6.966-62.694 18.576-88.236 13.932-25.542 32.508-44.118 53.406-58.050 23.22-13.932 48.762-20.898 78.948-20.898zM3357.605-15.020c-39.474 0-76.626 9.288-109.134 30.186s-55.728 46.44-74.304 83.592c-18.576 34.83-27.864 76.626-27.864 120.744s9.288 83.592 27.864 118.422c20.898 34.83 46.44 65.016 78.948 83.592 32.508 20.898 69.66 32.508 111.456 32.508 32.508 0 62.694-9.288 90.558-25.542s51.084-39.474 67.338-69.66l2.322 81.27h71.982v-441.179h-71.982l-2.322 81.27c-18.576-30.186-41.796-53.406-69.66-69.66-25.542-18.576-58.050-25.542-95.202-25.542zM3376.181 52.317c30.186 0 58.050 6.966 78.948 20.898 23.22 13.932 41.796 34.83 53.406 58.050 13.932 25.542 20.898 53.406 20.898 88.236 0 32.508-6.966 62.694-20.898 88.236s-30.186 44.118-53.406 58.050-48.762 20.898-78.948 20.898c-30.186 0-55.728-6.966-78.948-20.898s-41.796-34.83-53.406-58.050c-13.932-25.542-18.576-53.406-18.576-88.236 0-32.508 6.966-62.694 18.576-88.236 13.932-25.542 32.508-44.118 53.406-58.050 23.22-13.932 48.762-20.898 78.948-20.898zM3931.138-15.020c-48.762 0-85.914 13.932-109.134 39.474-23.22 27.864-34.83 69.66-34.83 125.388v225.234h-99.846v65.016h99.846v127.71h74.304v-127.71h153.252v-65.016h-153.252v-218.268c0-37.152 6.966-65.016 18.576-81.27 13.932-16.254 34.83-25.542 65.016-25.542 27.864 0 58.050 6.966 85.914 23.22l9.288-62.694c-13.932-9.288-30.186-13.932-48.762-18.576s-37.152-6.966-60.372-6.966zM4318.912-15.020c-39.474 0-76.626 9.288-109.134 30.186s-55.728 46.44-74.304 83.592c-18.576 34.83-27.864 76.626-27.864 120.744s9.288 83.592 27.864 118.422c20.898 34.83 46.44 65.016 78.948 83.592 32.508 20.898 69.66 32.508 111.456 32.508 32.508 0 62.694-9.288 90.558-25.542s51.084-39.474 67.338-69.66l2.322 81.27h71.982v-441.179h-71.982l-2.322 81.27c-18.576-30.186-41.796-53.406-69.66-69.66-25.542-18.576-58.050-25.542-95.202-25.542zM4337.488 52.317c30.186 0 58.050 6.966 78.948 20.898 23.22 13.932 41.796 34.83 53.406 58.050 13.932 25.542 20.898 53.406 20.898 88.236 0 32.508-6.966 62.694-20.898 88.236s-30.186 44.118-53.406 58.050-48.762 20.898-78.948 20.898c-30.186 0-55.728-6.966-78.948-20.898s-41.796-34.83-53.406-58.050c-13.932-25.542-18.576-53.406-18.576-88.236 0-32.508 6.966-62.694 18.576-88.236 13.932-25.542 32.508-44.118 53.406-58.050 23.22-13.932 48.762-20.898 78.948-20.898zM4743.837 500.463c-20.898 0-39.474 4.644-55.728 13.932s-30.186 23.22-39.474 39.474-13.932 34.83-13.932 55.728 4.644 39.474 13.932 55.728c9.288 16.254 23.22 30.186 39.474 39.474s34.83 13.932 55.728 13.932 39.474-4.644 55.728-13.932 30.186-23.22 39.474-39.474 13.932-34.83 13.932-55.728c0-20.898-4.644-39.474-13.932-55.728s-23.22-30.186-39.474-39.474c-16.254-9.288-34.83-13.932-55.728-13.932zM4743.837 519.039c16.254 0 32.508 4.644 44.118 11.61 13.932 6.966 23.22 18.576 32.508 32.508 6.966 13.932 11.61 30.186 11.61 46.44s-4.644 32.508-11.61 46.44-18.576 25.542-32.508 32.508c-13.932 6.966-27.864 11.61-44.118 11.61s-32.508-4.644-44.118-11.61c-13.932-6.966-23.22-18.576-32.508-32.508-6.966-13.932-11.61-27.864-11.61-46.44s4.644-32.508 11.61-46.44 18.576-23.22 32.508-32.508c11.61-6.966 27.864-11.61 44.118-11.61zM4706.685 558.512v104.49h34.83c13.932 0 23.22-2.322 30.186-9.288s11.61-13.932 11.61-25.542c0-6.966-2.322-11.61-4.644-18.576-2.322-4.644-6.966-9.288-13.932-11.61l25.542-41.796h-20.898l-23.22 37.152h-20.898v-37.152h-18.576v2.322zM4741.515 646.748h-13.932v-32.508h13.932c9.288 0 13.932 2.322 18.576 4.644 2.322 2.322 4.644 6.966 4.644 13.932-2.322 9.288-9.288 13.932-23.22 13.932z" />
+<glyph unicode="&#xe902;" glyph-name="alert-triangle" d="M985.175 69.138l-359.803 608.239c-17.135 29.983-47.117 51.4-81.383 59.967s-68.535 4.283-98.517-12.852c-17.135-8.565-34.265-25.7-42.835-42.835 0 0 0 0 0 0l-359.803-612.522c-34.265-59.967-12.852-141.352 47.117-175.618 17.135-12.852 38.552-17.135 59.967-17.135h728.173c34.265 0 68.535 12.852 89.952 38.552 25.7 25.7 38.552 55.683 38.552 89.952-4.283 21.417-8.565 47.117-21.417 64.252zM908.075-25.096c-8.565-8.565-21.417-12.852-29.983-12.852h-728.173c-8.565 0-12.852 0-21.417 4.283-21.417 12.852-25.7 38.552-17.135 59.967l364.088 603.956c4.283 4.283 8.565 12.852 12.852 12.852 21.417 12.852 47.117 4.283 59.967-12.852l364.088-603.956c4.283-4.283 4.283-12.852 4.283-21.417 4.283-12.852-4.283-21.417-8.565-29.983zM514.004 476.059c-25.7 0-42.835-17.135-42.835-42.835v-171.335c0-25.7 17.135-42.835 42.835-42.835s42.835 17.135 42.835 42.835v171.335c0 25.7-17.135 42.835-42.835 42.835zM484.021 120.538c-8.565-8.565-12.852-17.135-12.852-29.983s4.283-21.417 12.852-29.983c8.565-8.565 17.135-12.852 29.983-12.852s21.417 4.283 29.983 12.852c8.565 8.565 12.852 21.417 12.852 29.983s-4.283 21.417-12.852 29.983c-17.135 17.135-42.835 17.135-59.967 0z" />
+<glyph unicode="&#xe903;" glyph-name="arrow-down" d="M843.824 334.708c-17.135 17.135-42.835 17.135-59.967 0l-227.018-227.018v496.871c0 25.7-17.135 42.835-42.835 42.835s-42.835-17.135-42.835-42.835v-496.871l-227.018 227.018c-17.135 17.135-42.835 17.135-59.967 0s-17.135-42.835 0-59.967l299.837-299.837c4.283-4.283 8.565-8.565 12.852-8.565 4.283-4.283 12.852-4.283 17.135-4.283s12.852 0 17.135 4.283c4.283 4.283 8.565 4.283 12.852 8.565l299.837 299.837c17.135 17.135 17.135 42.835 0 59.967z" />
+<glyph unicode="&#xe904;" glyph-name="moon1" d="M515.719-6.164c-166.537 0-302.235 135.697-302.235 302.235 0.341 150.089 108.284 275.164 256.317 297.781 10.967 1.715 21.929-4.112 27.069-14.051 4.799-9.939 2.743-22.275-5.14-29.812-39.064-37.349-60.652-87.723-60.652-141.865 0-108.968 88.408-197.378 197.378-197.378 54.143 0 104.172 21.588 141.865 60.652 7.883 8.224 19.873 10.28 29.812 5.14s15.761-15.761 14.051-27.069c-23.303-148.033-148.719-255.632-298.465-255.632zM406.749 521.547c-84.983-40.433-141.523-126.444-141.865-225.477 0-138.096 112.396-250.834 250.834-250.834 98.688 0 184.699 56.54 225.477 141.18-34.611-17.817-72.988-27.069-113.080-27.069-137.068 0-248.778 111.711-248.778 248.778 0 40.092 9.593 78.815 27.415 113.424z" />
+<glyph unicode="&#xe905;" glyph-name="search" d="M470.486 96.979c-137.068 0-248.436 111.368-248.436 248.436s111.368 248.436 248.436 248.436 248.436-111.368 248.436-248.436c0-137.068-111.368-248.436-248.436-248.436zM470.486 542.45c-108.627 0-197.035-88.408-197.035-197.035s88.408-197.035 197.035-197.035 197.035 88.408 197.035 197.035c0 108.627-88.408 197.035-197.035 197.035zM780.259 9.599c-6.509 0-13.023 2.397-18.163 7.537l-148.033 148.376c-9.939 9.939-9.939 26.387 0 36.321s26.387 9.939 36.321 0l148.033-148.376c9.939-9.939 9.939-26.387 0-36.321-5.14-5.14-11.649-7.537-18.163-7.537z" />
+<glyph unicode="&#xe906;" glyph-name="sun1" d="M514.004 125.421c-92.864 0-168.593 75.731-168.593 168.593s75.731 168.593 168.593 168.593 168.593-75.731 168.593-168.593-75.731-168.593-168.593-168.593zM514.004 411.208c-64.764 0-117.192-52.428-117.192-117.192s52.428-117.192 117.192-117.192 117.192 52.428 117.192 117.192-52.428 117.192-117.192 117.192zM514.004 510.239c-14.051 0-25.7 11.649-25.7 25.7v98.347c0 14.051 11.649 25.7 25.7 25.7s25.7-11.649 25.7-25.7v-98.347c0-14.051-11.649-25.7-25.7-25.7zM342.67 439.649c-6.509 0-13.023 2.397-18.163 7.537l-69.563 69.219c-9.939 9.939-9.939 26.387 0 36.321s26.387 9.939 36.321 0l69.563-69.563c9.939-9.939 9.939-26.387 0-36.321-4.799-4.799-11.308-7.196-18.163-7.196zM272.080 268.314h-98.347c-14.051 0-25.7 11.649-25.7 25.7s11.649 25.7 25.7 25.7h98.347c14.051 0 25.7-11.649 25.7-25.7s-11.649-25.7-25.7-25.7zM273.451 27.76c-6.509 0-13.023 2.397-18.163 7.537-9.939 9.939-9.939 26.387 0 36.321l69.563 69.563c9.939 9.939 26.387 9.939 36.321 0s9.939-26.387 0-36.321l-69.563-69.563c-5.14-5.14-11.649-7.537-18.163-7.537zM514.004-71.958c-14.051 0-25.7 11.649-25.7 25.7v98.347c0 14.051 11.649 25.7 25.7 25.7s25.7-11.649 25.7-25.7v-98.347c0-14.392-11.649-25.7-25.7-25.7zM754.559 27.76c-6.509 0-13.023 2.397-18.163 7.537l-69.563 69.563c-9.939 9.939-9.939 26.387 0 36.321s26.387 9.939 36.321 0l69.563-69.563c9.939-9.939 9.939-26.387 0-36.321-4.799-5.14-11.308-7.537-18.163-7.537zM854.276 268.314h-98.347c-14.051 0-25.7 11.649-25.7 25.7s11.649 25.7 25.7 25.7h98.347c14.051 0 25.7-11.649 25.7-25.7s-11.308-25.7-25.7-25.7zM685.34 439.649c-6.509 0-13.023 2.397-18.163 7.537-9.939 9.939-9.939 26.387 0 36.321l69.563 69.563c9.939 9.939 26.387 9.939 36.321 0s9.939-26.387 0-36.321l-69.563-69.563c-5.14-5.14-11.649-7.537-18.163-7.537z" />
+<glyph unicode="&#xe907;" glyph-name="arrow-down-circle" d="M514.004 775.895c-261.286 0-471.171-209.886-471.171-471.171s209.886-471.171 471.171-471.171 471.171 209.886 471.171 471.171-209.886 471.171-471.171 471.171zM514.004-80.779c-214.169 0-385.503 171.335-385.503 385.503s171.335 385.503 385.503 385.503c214.169 0 385.503-171.335 385.503-385.503s-171.335-385.503-385.503-385.503zM655.356 334.708l-98.517-98.517v239.869c0 25.7-17.135 42.835-42.835 42.835s-42.835-17.135-42.835-42.835v-239.869l-98.517 98.517c-17.135 17.135-42.835 17.135-59.967 0s-17.135-42.835 0-59.967l171.335-171.335c4.283-4.283 8.565-8.565 12.852-8.565 4.283-4.283 12.852-4.283 17.135-4.283s12.852 0 17.135 4.283c4.283 4.283 8.565 4.283 12.852 8.565l171.335 171.335c17.135 17.135 17.135 42.835 0 59.967s-42.835 17.135-59.967 0z" />
+<glyph unicode="&#xe908;" glyph-name="arrow-down-left" d="M728.173 133.388h-325.537l355.52 355.52c17.135 17.135 17.135 42.835 0 59.967s-42.835 17.135-59.967 0l-355.52-355.52v325.537c0 25.7-17.135 42.835-42.835 42.835s-42.835-17.135-42.835-42.835v-428.337c0-4.283 0-12.852 4.283-17.135 4.283-8.565 12.852-17.135 21.417-21.417 4.283-4.283 12.852-4.283 17.135-4.283h428.337c25.7 0 42.835 17.135 42.835 42.835s-17.135 42.835-42.835 42.835z" />
+<glyph unicode="&#xe909;" glyph-name="arrow-down-right" d="M771.007 518.891c0 25.7-17.135 42.835-42.835 42.835s-42.835-17.135-42.835-42.835v-325.537l-355.52 355.52c-17.135 17.135-42.835 17.135-59.967 0s-17.135-42.835 0-59.967l355.52-355.52h-325.537c-25.7 0-42.835-17.135-42.835-42.835s17.135-42.835 42.835-42.835h428.337c4.283 0 12.852 0 17.135 4.283 8.565 4.283 17.135 12.852 21.417 21.417 4.283 4.283 4.283 12.852 4.283 17.135v428.337z" />
+<glyph unicode="&#xe90a;" glyph-name="arrow-left" d="M813.841 347.558h-496.871l227.018 227.018c17.135 17.135 17.135 42.835 0 59.967s-42.835 17.135-59.967 0l-299.837-299.837c-4.283-4.283-8.565-8.565-8.565-12.852-4.283-8.565-4.283-21.417 0-34.265 4.283-4.283 4.283-8.565 8.565-12.852l299.837-299.837c8.565-8.565 21.417-12.852 29.983-12.852s21.417 4.283 29.983 12.852c17.135 17.135 17.135 42.835 0 59.967l-227.018 227.018h496.871c25.7 0 42.835 17.135 42.835 42.835s-17.135 42.835-42.835 42.835z" />
+<glyph unicode="&#xe90b;" glyph-name="arrow-left-circle" d="M514.004 775.895c-261.286 0-471.171-209.886-471.171-471.171s209.886-471.171 471.171-471.171 471.171 209.886 471.171 471.171-209.886 471.171-471.171 471.171zM514.004-80.779c-214.169 0-385.503 171.335-385.503 385.503s171.335 385.503 385.503 385.503c214.169 0 385.503-171.335 385.503-385.503s-171.335-385.503-385.503-385.503zM685.34 347.558h-239.869l98.517 98.517c17.135 17.135 17.135 42.835 0 59.967s-42.835 17.135-59.967 0l-171.335-171.335c-4.283-4.283-8.565-8.565-8.565-12.852-4.283-8.565-4.283-21.417 0-34.265 4.283-4.283 4.283-8.565 8.565-12.852l171.335-171.335c8.565-8.565 21.417-12.852 29.983-12.852s21.417 4.283 29.983 12.852c17.135 17.135 17.135 42.835 0 59.967l-98.517 98.517h239.869c25.7 0 42.835 17.135 42.835 42.835s-17.135 42.835-42.835 42.835z" />
+<glyph unicode="&#xe90c;" glyph-name="arrow-right" d="M852.392 287.59c4.283 8.565 4.283 21.417 0 34.265-4.283 4.283-4.283 8.565-8.565 12.852l-299.837 299.837c-17.135 17.135-42.835 17.135-59.967 0s-17.135-42.835 0-59.967l227.018-227.018h-496.871c-25.7 0-42.835-17.135-42.835-42.835s17.135-42.835 42.835-42.835h496.871l-227.018-227.018c-17.135-17.135-17.135-42.835 0-59.967 8.565-8.565 21.417-12.852 29.983-12.852s21.417 4.283 29.983 12.852l299.837 299.837c4.283 4.283 8.565 8.565 8.565 12.852z" />
+<glyph unicode="&#xe90d;" glyph-name="arrow-right-circle" d="M514.004 775.895c-261.286 0-471.171-209.886-471.171-471.171s209.886-471.171 471.171-471.171 471.171 209.886 471.171 471.171-209.886 471.171-471.171 471.171zM514.004-80.779c-214.169 0-385.503 171.335-385.503 385.503s171.335 385.503 385.503 385.503c214.169 0 385.503-171.335 385.503-385.503s-171.335-385.503-385.503-385.503zM723.891 321.858c-4.283 4.283-4.283 8.565-8.565 12.852l-171.335 171.335c-17.135 17.135-42.835 17.135-59.967 0s-17.135-42.835 0-59.967l98.517-98.517h-239.869c-25.7 0-42.835-17.135-42.835-42.835s17.135-42.835 42.835-42.835h239.869l-98.517-98.517c-17.135-17.135-17.135-42.835 0-59.967 8.565-8.565 21.417-12.852 29.983-12.852s21.417 4.283 29.983 12.852l171.335 171.335c4.283 4.283 8.565 8.565 8.565 12.852 4.283 12.852 4.283 21.417 0 34.265z" />
+<glyph unicode="&#xe90e;" glyph-name="arrow-up" d="M843.824 334.708l-299.837 299.837c-4.283 4.283-8.565 8.565-12.852 8.565-8.565 4.283-21.417 4.283-34.265 0-4.283-4.283-8.565-4.283-12.852-8.565l-299.837-299.837c-17.135-17.135-17.135-42.835 0-59.967s42.835-17.135 59.967 0l227.018 227.018v-496.871c0-25.7 17.135-42.835 42.835-42.835s42.835 17.135 42.835 42.835v496.871l227.018-227.018c8.565-8.565 21.417-12.852 29.983-12.852s21.417 4.283 29.983 12.852c17.135 17.135 17.135 42.835 0 59.967z" />
+<glyph unicode="&#xe90f;" glyph-name="arrow-up-circle" d="M514.004 775.895c-261.286 0-471.171-209.886-471.171-471.171s209.886-471.171 471.171-471.171 471.171 209.886 471.171 471.171-209.886 471.171-471.171 471.171zM514.004-80.779c-214.169 0-385.503 171.335-385.503 385.503s171.335 385.503 385.503 385.503c214.169 0 385.503-171.335 385.503-385.503s-171.335-385.503-385.503-385.503zM543.989 506.042c-4.283 4.283-8.565 8.565-12.852 8.565-8.565 4.283-21.417 4.283-34.265 0-4.283-4.283-8.565-4.283-12.852-8.565l-171.335-171.335c-17.135-17.135-17.135-42.835 0-59.967s42.835-17.135 59.967 0l98.517 98.517v-239.869c0-25.7 17.135-42.835 42.835-42.835s42.835 17.135 42.835 42.835v239.869l98.517-98.517c8.565-8.565 21.417-12.852 29.983-12.852s21.417 4.283 29.983 12.852c17.135 17.135 17.135 42.835 0 59.967l-171.335 171.335z" />
+<glyph unicode="&#xe910;" glyph-name="arrow-up-left" d="M402.637 476.059h325.537c25.7 0 42.835 17.135 42.835 42.835s-17.135 42.835-42.835 42.835h-428.337c-4.283 0-12.852 0-17.135-4.283-8.565-4.283-17.135-12.852-21.417-21.417-4.283-4.283-4.283-12.852-4.283-17.135v-428.337c0-25.7 17.135-42.835 42.835-42.835s42.835 17.135 42.835 42.835v325.537l355.52-355.52c8.565-8.565 21.417-12.852 29.983-12.852s21.417 4.283 29.983 12.852c17.135 17.135 17.135 42.835 0 59.967l-355.52 355.52z" />
+<glyph unicode="&#xe911;" glyph-name="arrow-up-right" d="M766.724 536.026c-4.283 8.565-12.852 17.135-21.417 21.417-4.283 4.283-12.852 4.283-17.135 4.283h-428.337c-25.7 0-42.835-17.135-42.835-42.835s17.135-42.835 42.835-42.835h325.537l-355.52-355.52c-17.135-17.135-17.135-42.835 0-59.967 8.565-8.565 17.135-12.852 29.983-12.852s21.417 4.283 29.983 12.852l355.52 355.52v-325.537c0-25.7 17.135-42.835 42.835-42.835s42.835 17.135 42.835 42.835v428.337c0 4.283 0 12.852-4.283 17.135z" />
+<glyph unicode="&#xe912;" glyph-name="check" d="M886.658 591.71c-17.135 17.135-42.835 17.135-59.967 0l-441.188-441.188-184.186 184.186c-17.135 17.135-42.835 17.135-59.967 0s-17.135-42.835 0-59.967l214.169-214.169c8.565-8.565 17.135-12.852 29.983-12.852s21.417 4.283 29.983 12.852l471.171 471.171c17.135 17.135 17.135 42.835 0 59.967z" />
+<glyph unicode="&#xe913;" glyph-name="bar-chart" d="M179.55 181.991c0 12.826-10.26 25.65-25.65 25.65h-128.25c-15.39 0-25.65-12.826-25.65-25.65v-410.401c0-12.826 10.26-25.65 25.65-25.65h128.25c15.39 0 25.65 12.826 25.65 25.65v410.401zM461.701 746.294c0 15.39-12.826 25.65-25.65 25.65h-128.25c-15.39 0-25.65-10.26-25.65-25.65v-974.703c0-12.826 10.26-25.65 25.65-25.65h128.25c12.826 0 25.65 12.826 25.65 25.65v974.703zM743.852 464.142c0 15.39-12.826 25.65-25.65 25.65h-128.25c-12.826 0-25.65-10.26-25.65-25.65v-692.552c0-12.826 12.826-25.65 25.65-25.65h128.25c12.826 0 25.65 12.826 25.65 25.65v692.552zM1026.003-48.859c0 12.826-12.826 25.65-25.65 25.65h-128.25c-12.826 0-25.65-12.826-25.65-25.65v-179.55c0-12.826 12.826-25.65 25.65-25.65h128.25c12.826 0 25.65 12.826 25.65 25.65v179.55z" />
+<glyph unicode="&#xe914;" glyph-name="heart1" d="M920.925 651.677v0c-51.4 51.4-119.935 81.383-192.752 81.383v0c-72.817 0-145.635-29.983-197.035-81.383 0 0 0 0 0 0l-17.135-17.135-17.135 17.135c-51.4 51.4-119.935 81.383-197.035 81.383-72.817 0-141.352-29.983-192.752-81.383s-85.667-124.217-85.667-197.035 29.983-145.635 81.383-197.035l376.937-376.937c8.565-8.565 17.135-12.852 29.983-12.852s21.417 4.283 29.983 12.852l376.937 376.937c115.652 107.084 115.652 286.986 4.283 394.070zM860.958 317.573l-346.953-346.953-346.953 346.953c-77.1 77.1-77.1 197.035 0 274.136 34.265 38.552 85.667 55.683 132.785 55.683 51.4 0 98.517-17.135 137.068-55.683l47.117-47.117c17.135-17.135 42.835-17.135 59.967 0l42.835 47.117c0 0 0 0 0 0 38.552 34.265 85.667 55.683 141.352 55.683 0 0 0 0 0 0 51.4 0 98.517-21.417 137.068-55.683v0c34.265-38.552 55.683-85.667 55.683-137.068s-21.417-98.517-59.967-137.068z" />
+<glyph unicode="&#xe915;" glyph-name="settings" d="M514.004 476.059c-94.235 0-171.335-77.1-171.335-171.335s77.1-171.335 171.335-171.335c94.235 0 171.335 77.1 171.335 171.335s-77.1 171.335-171.335 171.335zM514.004 219.056c-47.117 0-85.667 38.552-85.667 85.667s38.552 85.667 85.667 85.667c47.117 0 85.667-38.552 85.667-85.667s-38.552-85.667-85.667-85.667zM869.524 159.088c4.283 8.565 12.852 17.135 29.983 17.135 72.817 0 128.5 55.683 128.5 128.5s-55.683 128.5-128.5 128.5h-8.565c-8.565 0-17.135 4.283-21.417 12.852 0 4.283 0 4.283-4.283 8.565-4.283 8.565-4.283 21.417 8.565 34.265 51.4 51.4 51.4 132.785 0 179.902v0c0 0 0 0 0 0-25.7 25.7-55.683 38.552-89.952 38.552 0 0 0 0 0 0-34.265 0-68.535-12.852-94.235-38.552-8.565-8.565-21.417-8.565-29.983-4.283-8.565 0-17.135 12.852-17.135 25.7 0 72.817-55.683 128.5-128.5 128.5s-128.5-55.683-128.5-128.5v-8.565c0-8.565-4.283-17.135-12.852-21.417-4.283 0-4.283 0-8.565-4.283-8.565-4.283-21.417 0-34.265 8.565-51.4 51.4-132.785 51.4-179.902 0-51.4-51.4-51.4-132.785 4.283-184.186 8.565-8.565 8.565-21.417 4.283-34.265-4.283-8.565-17.135-17.135-29.983-17.135-72.817 0-128.5-55.683-128.5-128.5s55.683-128.5 128.5-128.5h8.565c12.852 0 21.417-8.565 25.7-17.135s4.283-21.417-8.565-34.265c-25.7-25.7-38.552-55.683-38.552-89.952s12.852-64.252 38.552-89.952c0 0 0 0 0 0 51.4-51.4 132.785-51.4 184.186 4.283 8.565 8.565 21.417 8.565 34.265 4.283s17.135-12.852 17.135-29.983c0-72.817 55.683-128.5 128.5-128.5s128.5 55.683 128.5 128.5v8.565c0 12.852 8.565 21.417 17.135 25.7s21.417 4.283 34.265-8.565c51.4-51.4 132.785-51.4 179.902 0 51.4 51.4 51.4 132.785-4.283 184.186-4.283 8.565-8.565 21.417-4.283 29.983 0 0 0 0 0 0zM792.424 193.356c-17.135-42.835-8.565-89.952 25.7-128.5 8.565-8.565 12.852-17.135 12.852-29.983s-4.283-21.417-12.852-29.983c-8.565-8.565-17.135-12.852-29.983-12.852 0 0 0 0 0 0-12.852 0-21.417 4.283-34.265 17.135-34.265 34.265-81.383 42.835-124.217 21.417-42.835-17.135-68.535-59.967-68.535-102.8v-8.565c0-25.7-17.135-42.835-42.835-42.835s-42.835 17.135-42.835 42.835c0 0 0 4.283 0 4.283 0 47.117-29.983 85.667-72.817 102.8-12.852 8.565-29.983 8.565-47.117 8.565-29.983 0-59.967-12.852-81.383-34.265-17.135-17.135-42.835-17.135-59.967 0 0 0 0 0 0 0v0c-8.565 8.565-12.852 17.135-12.852 29.983s4.283 21.417 17.135 34.265c34.265 34.265 42.835 81.383 21.417 124.217-17.135 42.835-59.967 68.535-102.8 68.535h-8.565c-25.7 0-42.835 17.135-42.835 42.835s17.135 42.835 42.835 42.835c0 0 4.283 0 4.283 0 47.117 0 85.667 29.983 102.8 72.817s8.565 89.952-25.7 128.5c-17.135 17.135-17.135 42.835 0 59.967s42.835 17.135 64.252-4.283c29.983-29.983 77.1-38.552 115.652-25.7 4.283 0 8.565 0 12.852 4.283 42.835 17.135 68.535 59.967 68.535 102.8v8.565c0 25.7 17.135 42.835 42.835 42.835s42.835-17.135 42.835-47.117c0-47.117 25.7-85.667 68.535-102.8s89.952-8.565 128.5 25.7c8.565 8.565 17.135 12.852 29.983 12.852v0c12.852 0 21.417-4.283 29.983-12.852 0 0 0 0 0 0 17.135-17.135 17.135-42.835-4.283-64.252-29.983-29.983-38.552-77.1-25.7-115.652 0-4.283 0-8.565 4.283-12.852 17.135-42.835 59.967-68.535 102.8-68.535h8.565c25.7 0 42.835-17.135 42.835-42.835s-17.135-42.835-47.117-42.835c-42.835 0-85.667-25.7-102.8-68.535z" />
+<glyph unicode="&#xe916;" glyph-name="zoom-in" d="M929.493-50.796l-158.485 158.485c51.4 64.252 85.667 149.917 85.667 239.869 0 214.169-171.335 385.503-385.503 385.503s-385.503-171.335-385.503-385.503c0-214.169 171.335-385.503 385.503-385.503 89.952 0 175.618 29.983 239.869 85.667l158.485-158.485c8.565-8.565 21.417-12.852 29.983-12.852s21.417 4.283 29.983 12.852c17.135 17.135 17.135 42.835 0 59.967zM171.335 347.558c0 167.052 132.785 299.837 299.837 299.837s299.837-132.785 299.837-299.837c0-81.383-34.265-158.485-85.667-209.886 0 0 0 0 0 0s0 0 0 0c-55.683-55.683-128.5-85.667-209.886-85.667-171.335-4.283-304.119 128.5-304.119 295.553zM599.672 390.39h-85.667v85.667c0 25.7-17.135 42.835-42.835 42.835s-42.835-17.135-42.835-42.835v-85.667h-85.667c-25.7 0-42.835-17.135-42.835-42.835s17.135-42.835 42.835-42.835h85.667v-85.667c0-25.7 17.135-42.835 42.835-42.835s42.835 17.135 42.835 42.835v85.667h85.667c25.7 0 42.835 17.135 42.835 42.835s-17.135 42.835-42.835 42.835z" />
+<glyph unicode="&#xe917;" glyph-name="zoom-out" d="M929.493-50.796l-158.485 158.485c51.4 64.252 85.667 149.917 85.667 239.869 0 214.169-171.335 385.503-385.503 385.503s-385.503-171.335-385.503-385.503c0-214.169 171.335-385.503 385.503-385.503 89.952 0 175.618 29.983 239.869 85.667l158.485-158.485c8.565-8.565 21.417-12.852 29.983-12.852s21.417 4.283 29.983 12.852c17.135 17.135 17.135 42.835 0 59.967zM171.335 347.558c0 167.052 132.785 299.837 299.837 299.837s299.837-132.785 299.837-299.837c0-81.383-34.265-158.485-85.667-209.886 0 0 0 0 0 0s0 0 0 0c-55.683-55.683-128.5-85.667-209.886-85.667-171.335-4.283-304.119 128.5-304.119 295.553zM599.672 390.39h-257.002c-25.7 0-42.835-17.135-42.835-42.835s17.135-42.835 42.835-42.835h257.002c25.7 0 42.835 17.135 42.835 42.835s-17.135 42.835-42.835 42.835z" />
+<glyph unicode="&#xe918;" glyph-name="chevron-down" d="M800.991 463.208c-17.135 17.135-42.835 17.135-59.967 0l-227.018-227.018-227.018 227.018c-17.135 17.135-42.835 17.135-59.967 0s-17.135-42.835 0-59.967l257.002-257.002c8.565-8.565 21.417-12.852 29.983-12.852s21.417 4.283 29.983 12.852l257.002 257.002c17.135 17.135 17.135 42.835 0 59.967z" />
+<glyph unicode="&#xe919;" glyph-name="chevron-left" d="M445.471 304.723l227.018 227.018c17.135 17.135 17.135 42.835 0 59.967s-42.835 17.135-59.967 0l-257.002-257.002c-17.135-17.135-17.135-42.835 0-59.967l257.002-257.002c8.565-8.565 21.417-12.852 29.983-12.852s21.417 4.283 29.983 12.852c17.135 17.135 17.135 42.835 0 59.967l-227.018 227.018z" />
+<glyph unicode="&#xe91a;" glyph-name="chevron-right" d="M672.49 334.708l-257.002 257.002c-17.135 17.135-42.835 17.135-59.967 0s-17.135-42.835 0-59.967l227.018-227.018-227.018-227.018c-17.135-17.135-17.135-42.835 0-59.967 8.565-8.565 17.135-12.852 29.983-12.852s21.417 4.283 29.983 12.852l257.002 257.002c17.135 17.135 17.135 42.835 0 59.967z" />
+<glyph unicode="&#xe91b;" glyph-name="chevron-up" d="M800.991 206.206l-257.002 257.002c-17.135 17.135-42.835 17.135-59.967 0l-257.002-257.002c-17.135-17.135-17.135-42.835 0-59.967s42.835-17.135 59.967 0l227.018 227.018 227.018-227.018c8.565-8.565 21.417-12.852 29.983-12.852s21.417 4.283 29.983 12.852c17.135 17.135 17.135 42.835 0 59.967z" />
+<glyph unicode="&#xe91c;" glyph-name="menu" d="M899.509 347.558h-771.007c-25.7 0-42.835-17.135-42.835-42.835s17.135-42.835 42.835-42.835h771.007c25.7 0 42.835 17.135 42.835 42.835s-17.135 42.835-42.835 42.835zM128.5 518.891h771.007c25.7 0 42.835 17.135 42.835 42.835s-17.135 42.835-42.835 42.835h-771.007c-25.7 0-42.835-17.135-42.835-42.835s17.135-42.835 42.835-42.835zM899.509 90.555h-771.007c-25.7 0-42.835-17.135-42.835-42.835s17.135-42.835 42.835-42.835h771.007c25.7 0 42.835 17.135 42.835 42.835s-17.135 42.835-42.835 42.835z" />
+<glyph unicode="&#xe91d;" glyph-name="download" d="M899.509 219.056c-25.7 0-42.835-17.135-42.835-42.835v-171.335c0-25.7-17.135-42.835-42.835-42.835h-599.672c-25.7 0-42.835 17.135-42.835 42.835v171.335c0 25.7-17.135 42.835-42.835 42.835s-42.835-17.135-42.835-42.835v-171.335c0-72.817 55.683-128.5 128.5-128.5h599.672c72.817 0 128.5 55.683 128.5 128.5v171.335c0 25.7-17.135 42.835-42.835 42.835zM484.021 146.239c4.283-4.283 8.565-8.565 12.852-8.565 4.283-4.283 12.852-4.283 17.135-4.283s12.852 0 17.135 4.283c4.283 4.283 8.565 4.283 12.852 8.565l214.169 214.169c17.135 17.135 17.135 42.835 0 59.967s-42.835 17.135-59.967 0l-141.352-141.352v411.204c0 25.7-17.135 42.835-42.835 42.835s-42.835-17.135-42.835-42.835v-411.204l-141.352 141.352c-17.135 17.135-42.835 17.135-59.967 0s-17.135-42.835 0-59.967l214.169-214.169z" />
+<glyph unicode="&#xe91e;" glyph-name="minus" d="M813.841 347.558h-599.672c-25.7 0-42.835-17.135-42.835-42.835s17.135-42.835 42.835-42.835h599.672c25.7 0 42.835 17.135 42.835 42.835s-17.135 42.835-42.835 42.835z" />
+<glyph unicode="&#xe91f;" glyph-name="plus" d="M813.841 347.558h-257.002v257.002c0 25.7-17.135 42.835-42.835 42.835s-42.835-17.135-42.835-42.835v-257.002h-257.002c-25.7 0-42.835-17.135-42.835-42.835s17.135-42.835 42.835-42.835h257.002v-257.002c0-25.7 17.135-42.835 42.835-42.835s42.835 17.135 42.835 42.835v257.002h257.002c25.7 0 42.835 17.135 42.835 42.835s-17.135 42.835-42.835 42.835z" />
+<glyph unicode="&#xe920;" glyph-name="add-cell" d="M417.629 808.020h-385.503c-17.992 0-32.124-14.136-32.124-32.124v-385.503c0-17.992 14.136-32.124 32.124-32.124h385.503c17.992 0 32.124 14.136 32.124 32.124v385.503c0 17.992-14.136 32.124-32.124 32.124zM995.886 229.764h-385.503c-17.992 0-32.124-14.136-32.124-32.124v-385.503c0-17.992 14.136-32.124 32.124-32.124h385.503c17.992 0 32.124 14.136 32.124 32.124v385.503c0 17.992-14.136 32.124-32.124 32.124zM417.629 229.764h-385.503c-17.992 0-32.124-14.136-32.124-32.124v-385.503c0-17.992 14.136-32.124 32.124-32.124h385.503c17.992 0 32.124 14.136 32.124 32.124v385.503c0 17.992-14.136 32.124-32.124 32.124zM610.38 551.017h160.627v-160.627c0-17.992 14.136-32.124 32.124-32.124s32.124 14.136 32.124 32.124v160.627h160.627c17.992 0 32.124 14.136 32.124 32.124s-14.136 32.124-32.124 32.124h-160.627v160.627c0 17.992-14.136 32.124-32.124 32.124s-32.124-14.136-32.124-32.124v-160.627h-160.627c-17.992 0-32.124-14.136-32.124-32.124s14.136-32.124 32.124-32.124z" />
+<glyph unicode="&#xe921;" glyph-name="alert" d="M1009.792 4.64l-440.002 770.003c-11.438 20.019-32.728 32.374-55.784 32.374s-44.346-12.354-55.784-32.374l-440.002-770.003c-11.364-19.884-11.282-44.316 0.214-64.127s32.668-32 55.57-32h880.005c22.902 0 44.076 12.192 55.57 32s11.578 44.24 0.214 64.127zM578.256 37.012h-128.5v128.5h128.5v-128.5zM578.256 229.764h-128.5v257.002h128.5v-257.002z" />
+<glyph unicode="&#xe922;" glyph-name="calendar" d="M887.826 667.836h-46.728v46.728c0 23.365-23.365 46.728-46.728 46.728s-46.728-23.365-46.728-46.728v-46.728h-467.277v46.728c0 23.365-23.365 46.728-46.728 46.728s-46.728-23.365-46.728-46.728v-46.728h-46.728c-79.436 0-140.183-60.745-140.183-140.183v-607.46c0-74.765 60.745-140.183 140.183-140.183h747.643c79.436 0 140.183 65.42 140.183 140.183v607.46c0 79.436-60.745 140.183-140.183 140.183zM934.555-79.807c0-23.365-23.365-46.728-46.728-46.728h-747.643c-23.365 0-46.728 23.365-46.728 46.728v420.549h841.099v-420.549zM93.455 434.198v93.455c0 23.365 23.365 46.728 46.728 46.728h46.728v-46.728c0-23.365 23.365-46.728 46.728-46.728s46.728 23.365 46.728 46.728v46.728h467.277v-46.728c0-23.365 23.365-46.728 46.728-46.728s46.728 23.365 46.728 46.728v46.728h46.728c23.365 0 46.728-23.365 46.728-46.728v-93.455h-841.099zM373.822 247.287h93.455v-93.455h-93.455v93.455zM560.733 247.287h93.455v-93.455h-93.455v93.455zM186.911 60.376h93.455v-93.455h-93.455v93.455zM373.822 60.376h93.455v-93.455h-93.455v93.455zM560.733 60.376h93.455v-93.455h-93.455v93.455zM747.643 247.287h93.455v-93.455h-93.455v93.455z" />
+<glyph unicode="&#xe923;" glyph-name="checkmark" d="M346.953-50.369l-272.423 272.423c-33.412 33.412-38.552 89.952-7.712 128.5 35.98 38.552 95.092 38.552 131.072 2.572l169.621-169.621c5.14-5.14 12.852-5.14 15.42 0l444.614 444.614c35.98 35.98 95.092 35.98 131.072-2.572 33.412-35.98 28.272-92.52-7.712-128.5l-544.846-544.846c-15.42-20.56-43.692-20.56-59.112-2.572z" />
+<glyph unicode="&#xe924;" glyph-name="cog-thick" d="M989.458 399.386h-92.52c-7.712 30.84-20.56 61.68-35.98 89.952l64.252 64.252c15.42 15.42 15.42 41.12 0 53.972l-95.092 97.66c-15.42 15.42-41.12 15.42-53.972 0l-66.82-66.82c-28.272 15.42-56.54 28.272-87.38 35.98v95.092c0 20.56-17.992 38.552-38.552 38.552h-133.641c-20.56 0-38.552-17.992-38.552-38.552v-95.092c-30.84-7.712-61.68-20.56-87.38-35.98l-69.392 66.82c-15.42 15.42-41.12 15.42-56.54 0l-95.092-95.092c-15.42-15.42-15.42-41.12 0-56.54l64.252-64.252c-15.42-28.272-28.272-56.54-35.98-89.952h-92.52c-20.56 0-38.552-17.992-38.552-38.552v-133.641c0-20.56 17.992-38.552 38.552-38.552h92.52c7.712-30.84 20.56-61.68 35.98-89.952l-64.252-64.252c-15.42-15.42-15.42-41.12 0-53.972l95.092-97.66c15.42-15.42 41.12-15.42 53.972 0l66.82 66.82c28.272-15.42 56.54-28.272 87.38-35.98v-95.092c0-20.56 17.992-38.552 38.552-38.552h133.641c20.56 0 38.552 17.992 38.552 38.552v95.092c30.84 7.712 61.68 20.56 87.38 35.98l66.82-66.82c15.42-15.42 41.12-15.42 53.972 0l95.092 95.092c15.42 15.42 15.42 41.12 0 53.972l-64.252 64.252c15.42 28.272 28.272 56.54 35.98 89.952h92.52c20.56 0 38.552 17.992 38.552 38.552v133.641c5.14 25.7-12.852 41.12-33.412 41.12zM514.004 78.133c-118.22 0-215.882 97.66-215.882 215.882s97.66 215.882 215.882 215.882 215.882-97.66 215.882-215.882-97.66-215.882-215.882-215.882z" />
+<glyph unicode="&#xe925;" glyph-name="dashboards" horiz-adv-x="1075" d="M934.555 667.836h-794.371c-79.436 0-140.183-60.745-140.183-140.183v-467.277c0-74.765 60.745-140.183 140.183-140.183h794.371c79.436 0 140.183 65.42 140.183 140.183v467.277c0 79.436-60.745 140.183-140.183 140.183zM93.455 527.653c0 23.365 23.365 46.728 46.728 46.728h186.911v-233.638h-233.638v186.911zM140.183 13.648c-23.365 0-46.728 23.365-46.728 46.728v186.911h233.638v-233.638h-186.911zM420.549 13.648v233.638h233.638v-233.638h-233.638zM981.281 60.376c0-23.365-23.365-46.728-46.728-46.728h-186.911v233.638h233.638v-186.911zM420.549 340.742v233.638h514.004c23.365 0 46.728-23.365 46.728-46.728v-186.911h-560.733z" />
+<glyph unicode="&#xe926;" glyph-name="data-explorer" d="M935.49 430.226c-25.7 15.42-56.54 17.992-82.24 7.712l-120.792 161.912c2.572 2.572 2.572 5.14 5.14 7.712 28.272 48.832 10.28 113.080-38.552 141.352s-113.080 10.28-141.352-38.552c-25.7-43.692-12.852-100.232 25.7-131.072l-197.892-547.416c-12.852 0-23.132-2.572-35.98-5.14l-120.792 159.341c2.572 2.572 2.572 5.14 5.14 7.712 28.272 48.832 10.28 113.080-38.552 141.352s-110.512 10.28-138.781-38.552-10.28-113.080 38.552-141.352c25.7-15.42 56.54-17.992 84.812-7.712l120.792-159.341c-2.572-2.572-2.572-2.572-5.14-5.14-28.272-48.832-10.28-113.080 38.552-141.352s113.080-10.28 141.352 38.552c25.7 46.26 12.852 102.8-25.7 133.641l192.752 542.276c12.852 0 23.132 2.572 35.98 5.14l120.792-159.341c-2.572-2.572-2.572-5.14-5.14-7.712-28.272-48.832-10.28-113.080 38.552-141.352s113.080-10.28 141.352 38.552 10.28 110.512-38.552 138.781z" />
+<glyph unicode="&#xe927;" glyph-name="ui-download" d="M408.634 273.454h-125.932c-35.98 0-56.54-46.26-28.272-71.96l259.572-259.572 262.142 262.142c28.272 28.272 7.712 71.96-28.272 71.96l-128.5-2.572-5.14 431.764c0 59.112-46.26 102.8-102.8 102.8-59.112 0-102.8-46.26-102.8-102.8v-431.764zM912.358 37.012v-51.4c0-48.832-41.12-89.952-89.952-89.952h-616.806c-48.832 0-89.952 41.12-89.952 89.952v51.4c0 20.56-17.992 38.552-38.552 38.552s-38.552-17.992-38.552-38.552v-51.4c0-92.52 74.532-167.052 167.052-167.052h616.806c92.52 0 167.052 74.532 167.052 167.052v51.4c0 20.56-17.992 38.552-38.552 38.552v0c-20.56 0-38.552-17.992-38.552-38.552z" />
+<glyph unicode="&#xe928;" glyph-name="duplicate" d="M925.21 808.020h-565.406c-56.54 0-102.8-46.26-102.8-102.8v-154.201h-154.201c-56.54 0-102.8-46.26-102.8-102.8v-565.406c0-56.54 46.26-102.8 102.8-102.8h565.406c56.54 0 102.8 46.26 102.8 102.8v154.201h154.201c56.54 0 102.8 46.26 102.8 102.8v565.406c0 56.54-46.26 102.8-102.8 102.8zM693.907-117.19c0-12.852-12.852-25.7-25.7-25.7h-565.406c-12.852 0-25.7 12.852-25.7 25.7v565.406c0 12.852 12.852 25.7 25.7 25.7h154.201v-334.103c0-56.54 46.26-102.8 102.8-102.8h334.103v-154.201z" />
+<glyph unicode="&#xe929;" glyph-name="export" d="M205.602 769.468h231.302c20.56 0 38.552-17.992 38.552-38.552s-17.992-38.552-38.552-38.552h-231.302c-48.832 0-89.952-41.12-89.952-89.952v-616.806c0-48.832 41.12-89.952 89.952-89.952h616.806c48.832 0 89.952 41.12 89.952 89.952v231.302c0 20.56 17.992 38.552 38.552 38.552s38.552-17.992 38.552-38.552v-231.302c0-92.52-74.532-167.052-167.052-167.052h-616.806c-92.52 0-167.052 74.532-167.052 167.052v616.806c0 92.52 74.532 167.052 167.052 167.052zM681.056 607.558l-89.952 89.952c-25.7 25.7-7.712 71.96 30.84 71.96h370.083v-370.083c0-38.552-46.26-56.54-71.96-30.84l-89.952 89.952-251.862-251.862c-41.12-41.12-105.372-41.12-146.492 0s-41.12 105.372 0 146.492l249.292 254.432z" />
+<glyph unicode="&#xe92a;" glyph-name="fullscreen" d="M873.808 62.712c0-12.852-12.852-25.7-25.7-25.7h-668.207c-12.852 0-25.7 12.852-25.7 25.7v462.604c0 12.852 12.852 25.7 25.7 25.7h668.207c12.852 0 25.7-12.852 25.7-25.7v-462.604zM89.952 628.118h154.201c7.712 0 12.852 5.14 12.852 12.852v51.4c0 7.712-5.14 12.852-12.852 12.852h-167.052c-43.692 0-77.1-33.412-77.1-77.1v-167.052c0-7.712 5.14-12.852 12.852-12.852h51.4c7.712 0 12.852 5.14 12.852 12.852v154.201c0 7.712 5.14 12.852 12.852 12.852zM77.1-27.238v154.201c0 7.712-5.14 12.852-12.852 12.852h-51.4c-7.712 0-12.852-5.14-12.852-12.852v-167.052c0-43.692 33.412-77.1 77.1-77.1h167.052c7.712 0 12.852 5.14 12.852 12.852v51.4c0 7.712-5.14 12.852-12.852 12.852h-154.201c-7.712 0-12.852 5.14-12.852 12.852zM938.058-40.089h-154.201c-7.712 0-12.852-5.14-12.852-12.852v-51.4c0-7.712 5.14-12.852 12.852-12.852h167.052c43.692 0 77.1 33.412 77.1 77.1v167.052c0 7.712-5.14 12.852-12.852 12.852h-51.4c-7.712 0-12.852-5.14-12.852-12.852v-154.201c0-7.712-5.14-12.852-12.852-12.852zM950.91 615.268v-154.201c0-7.712 5.14-12.852 12.852-12.852h51.4c7.712 0 12.852 5.14 12.852 12.852v167.052c0 43.692-33.412 77.1-77.1 77.1h-167.052c-7.712 0-12.852-5.14-12.852-12.852v-51.4c0-7.712 5.14-12.852 12.852-12.852h154.201c7.712 0 12.852-5.14 12.852-12.852z" />
+<glyph unicode="&#xe92b;" glyph-name="influx-icon" d="M1028.010 144.487c0 0 0 0 0 0 0 9.345 0 14.020 0 18.69 0 0 0 0 0 0s0 0 0 0 0 0 0 0l-112.146 467.277c0 4.675-4.675 9.345-4.675 14.020 0 0 0 4.675-4.675 4.675-4.675 4.675-4.675 4.675-9.345 9.345 0 0 0 0 0 0-4.675 0-9.345 4.675-9.345 4.675l-467.277 140.183c-9.345 4.675-14.020 4.675-14.020 4.675s0 0 0 0c-9.345 0-14.020 0-18.69-4.675 0 0-4.675 0-4.675 0-4.675 0-9.345-4.675-14.020-9.345l-355.13-327.093c0 0 0 0 0 0s0 0 0 0 0 0 0 0c-4.675 0-4.675-4.675-9.345-9.345 0 0 0-4.675 0-4.675-4.675-4.675-4.675-9.345-4.675-14.020 0 0 0 0 0 0 0-4.675 0-9.345 0-14.020l112.146-467.277c0-4.675 0-4.675 4.675-9.345 0 0 0 0 0 0 4.675-4.675 4.675-9.345 9.345-14.020 0 0 0 0 4.675-4.675s9.345-4.675 14.020-9.345c0 0 0 0 0 0s0 0 0 0 0 0 0 0l467.277-140.183c4.675 0 9.345 0 14.020 0s9.345 0 14.020 4.675c0 0 4.675 0 4.675 0 4.675 0 4.675 4.675 9.345 4.675 0 0 0 0 0 0l355.13 327.093c4.675 4.675 4.675 4.675 9.345 9.345 0 0 0 0 0 0 4.675 4.675 4.675 9.345 9.345 18.69zM214.947-0.37l56.075 172.893 378.495-112.146-56.075-172.893-378.495 112.146zM401.858 695.873l126.165-135.51-285.039-261.676-130.838 135.51 289.712 261.676zM925.21 186.541l-182.238-42.055-88.783 378.495 182.238 42.055 88.783-378.495zM570.079 471.58l74.765-313.076-313.076 93.455 238.311 219.62zM612.133 611.763l-51.4 51.4 126.165-37.381-74.765-14.020zM130.838 275.324l56.075-56.075-23.365-74.765-32.71 130.838zM742.971 51.031l74.765 18.69-98.129-93.455 23.365 74.765z" />
+<glyph unicode="&#xe92c;" glyph-name="note" d="M1028.010 653.818c0-15.42-12.852-25.7-25.7-25.7h-539.706c-12.852 0-25.7 10.28-25.7 25.7v128.5c0 15.42 12.852 25.7 25.7 25.7h539.706c12.852 0 25.7-10.28 25.7-25.7v-128.5zM1028.010 371.116c0-12.852-12.852-25.7-25.7-25.7h-976.61c-15.42 0-25.7 12.852-25.7 25.7v128.5c0 15.42 10.28 25.7 25.7 25.7h976.61c12.852 0 25.7-10.28 25.7-25.7v-128.5zM1028.010 88.413c0-12.852-12.852-25.7-25.7-25.7h-976.61c-15.42 0-25.7 12.852-25.7 25.7v128.5c0 12.852 10.28 25.7 25.7 25.7h976.61c12.852 0 25.7-12.852 25.7-25.7v-128.5zM591.106-194.29c0-12.852-12.852-25.7-25.7-25.7h-539.706c-15.42 0-25.7 12.852-25.7 25.7v128.5c0 12.852 10.28 25.7 25.7 25.7h539.706c12.852 0 25.7-12.852 25.7-25.7v-128.5z" />
+<glyph unicode="&#xe92d;" glyph-name="organizations" horiz-adv-x="935" d="M789.698 490.272c32.71 37.381 51.4 79.436 51.4 130.838 0 102.8-84.11 186.911-186.911 186.911s-186.911-84.11-186.911-186.911c0-51.4 18.69-93.455 51.4-130.838-18.69-9.345-37.381-23.365-51.4-37.381-9.345 93.455-88.783 168.22-186.911 168.22-102.8 0-186.911-84.11-186.911-186.911 0-51.4 18.69-93.455 51.4-126.165-84.11-46.728-144.855-140.183-144.855-247.657v-186.911c0-51.4 42.055-93.455 93.455-93.455h373.822c51.4 0 93.455 42.055 93.455 93.455v93.455h280.367c51.4 0 93.455 42.055 93.455 93.455v177.565c0 107.475-56.075 205.602-144.855 252.329zM654.188 714.565c51.4 0 93.455-42.055 93.455-93.455s-42.055-93.455-93.455-93.455c-51.4 0-93.455 42.055-93.455 93.455s42.055 93.455 93.455 93.455zM186.911 434.198c0 51.4 42.055 93.455 93.455 93.455s93.455-42.055 93.455-93.455c0-51.4-42.055-93.455-93.455-93.455s-93.455 42.055-93.455 93.455zM467.277-126.535h-373.822v186.911c0 102.8 84.11 186.911 186.911 186.911s186.911-84.11 186.911-186.911v-186.911zM841.099 60.376h-280.367c0 79.436-37.381 154.201-88.783 205.602 14.020 84.11 79.436 158.875 163.547 168.22 112.146 9.345 205.602-79.436 205.602-186.911v-186.911z" />
+<glyph unicode="&#xe92e;" glyph-name="pause" d="M436.904-52.938c0-20.56-17.992-38.552-38.552-38.552h-128.5c-20.56 0-38.552 17.992-38.552 38.552v693.907c0 20.56 17.992 38.552 38.552 38.552h128.5c20.56 0 38.552-17.992 38.552-38.552v-693.907zM796.708-52.938c0-20.56-17.992-38.552-38.552-38.552h-128.5c-20.56 0-38.552 17.992-38.552 38.552v693.907c0 20.56 17.992 38.552 38.552 38.552h128.5c20.56 0 38.552-17.992 38.552-38.552v-693.907z" />
+<glyph unicode="&#xe92f;" glyph-name="pencil" horiz-adv-x="900" d="M706.757 743.768l-128.5-128.5 192.752-192.752 128.5 128.5-192.752 192.752zM0 37.012l0.692-193.316 192.061 0.566 514.004 514.004-192.752 192.752-514.004-514.004zM192.752-91.49h-128.5v128.5h64.252v-64.252h64.252v-64.252z" />
+<glyph unicode="&#xe930;" glyph-name="play" d="M786.427 322.284l-460.034 400.924c-17.992 15.42-43.692 2.572-43.692-17.992v-822.408c0-23.132 25.7-33.412 43.692-20.56l460.034 400.924c15.42 17.992 15.42 43.692 0 59.112z" />
+<glyph unicode="&#xe931;" glyph-name="ui-plus" d="M932.918 383.966h-303.263c-12.852 0-25.7 10.28-25.7 25.7v303.263c0 48.832-35.98 92.52-84.812 95.092-51.4 2.572-95.092-38.552-95.092-89.952v-308.403c0-12.852-10.28-25.7-25.7-25.7h-303.263c-48.832 0-92.52-35.98-95.092-84.812-2.572-51.4 38.552-95.092 89.952-95.092h308.403c12.852 0 25.7-10.28 25.7-25.7v-303.263c0-48.832 35.98-92.52 84.812-95.092 51.4-2.572 95.092 38.552 95.092 89.952v308.403c0 12.852 10.28 25.7 25.7 25.7h308.403c51.4 0 92.52 43.692 89.952 95.092-2.572 48.832-46.26 84.812-95.092 84.812z" />
+<glyph unicode="&#xe932;" glyph-name="refresh" d="M877.663 657.673c-77.1 77.1-176.689 127.859-285.915 144.564-135.568 20.56-271.138-12.852-382.291-93.806-110.512-81.599-183.114-201.104-203.675-336.673-5.14-35.337 18.632-68.105 53.972-73.245 3.212-0.644 6.424-0.644 9.636-0.644 31.484 0 58.468 22.488 63.608 54.612 15.42 101.516 70.032 191.467 152.916 252.505s185.042 86.096 286.558 70.676c82.24-12.208 156.772-50.758 214.597-108.584l-144.564-144.564h385.503v385.503l-150.347-150.347zM968.258 289.517c-35.337 5.14-68.105-18.632-73.245-53.972-32.124-210.1-229.375-355.306-439.474-323.181-81.599 12.208-156.772 50.758-214.597 108.584l144.564 144.564h-385.503v-385.503l150.347 150.347c77.1-77.1 177.332-127.859 285.915-144.564 26.344-3.856 52.044-5.784 77.744-5.784 249.292 0 469.030 182.472 507.58 436.262 5.784 35.337-17.992 68.105-53.328 73.245z" />
+<glyph unicode="&#xe933;" glyph-name="remove" d="M642.506 294.014l237.085 237.085c25.056 25.056 25.056 66.179 0 90.592l-37.908 37.908c-25.056 25.056-66.179 25.056-90.592 0l-237.085-237.085-237.085 237.085c-25.056 25.056-66.179 25.056-90.592 0l-37.908-37.908c-25.056-25.056-25.056-66.179 0-90.592l237.085-237.085-237.085-237.085c-25.056-25.056-25.056-66.179 0-90.592l37.908-37.908c25.056-25.056 66.179-25.056 90.592 0l237.085 237.085 237.085-237.085c25.056-25.056 66.179-25.056 90.592 0l37.908 37.908c25.056 25.056 25.056 66.179 0 90.592l-237.085 237.085z" />
+<glyph unicode="&#xe934;" glyph-name="alert-circle" d="M984.213 303.207c0 129.96-52.718 247.722-137.876 332.835s-202.877 137.876-332.835 137.876-247.722-52.718-332.835-137.876-137.876-202.877-137.876-332.835 52.718-247.722 137.876-332.835 202.877-137.876 332.835-137.876 247.722 52.718 332.835 137.876 137.876 202.877 137.876 332.835zM898.631 303.207c0-106.381-43.049-202.577-112.799-272.328s-165.947-112.799-272.328-112.799-202.577 43.049-272.328 112.799-112.799 165.947-112.799 272.328 43.049 202.577 112.799 272.328 165.947 112.799 272.328 112.799 202.577-43.049 272.328-112.799 112.799-165.947 112.799-272.328zM470.711 474.375v-171.168c0-23.621 19.172-42.793 42.793-42.793s42.793 19.172 42.793 42.793v171.168c0 23.621-19.172 42.793-42.793 42.793s-42.793-19.172-42.793-42.793zM513.502 89.248c23.621 0 42.793 19.172 42.793 42.793s-19.172 42.793-42.793 42.793-42.793-19.172-42.793-42.793 19.172-42.793 42.793-42.793z" />
+<glyph unicode="&#xe935;" glyph-name="crown" d="M187.429-93.902c-28.244 0-51.35 20.54-59.054 46.215l-125.809 492.962c-5.135 17.974 2.569 38.514 17.974 48.784 15.405 12.839 35.945 12.839 53.919 2.569l233.644-148.915 166.889 246.481c7.704 12.839 23.109 20.54 38.514 20.54s30.81-7.704 38.514-20.54l169.455-246.481 233.644 148.915c15.405 10.27 38.514 10.27 53.919-2.569s23.109-30.81 17.974-51.35l-128.375-490.395c-7.704-28.244-30.81-46.215-59.054-46.215h-652.149zM202.834-27.147v0c0 0 0 0 0 0zM200.266-16.877h626.474l105.269 408.235-182.294-118.105c-28.244-17.974-64.189-10.27-82.16 15.405l-154.050 223.374-154.050-223.374c-17.974-25.675-53.919-33.379-82.16-17.974l-182.294 118.105 105.269-405.667zM996.196 432.438v0c0 0 0 0 0 0zM77.025 463.249v0c0 0 0 0 0 0zM949.981 463.249c0 0 0 0 0 0v0zM487.827 550.544c2.569 0 2.569 0 0 0v0zM536.611 550.544v0c0 0 0 0 0 0z" />
+<glyph unicode="&#xe936;" glyph-name="trash" d="M938.058 679.519h-195.322l-66.82 110.512c-5.14 10.28-17.992 17.992-30.84 17.992h-262.142c-12.852 0-25.7-7.712-33.412-17.992l-64.252-110.512h-195.322c-20.56 0-38.552-17.992-38.552-38.552v-102.8c0-20.56 17.992-38.552 38.552-38.552h848.108c20.56 0 38.552 17.992 38.552 38.552v102.8c0 20.56-17.992 38.552-38.552 38.552zM406.064 730.92h215.882l30.84-51.4h-277.563l30.84 51.4zM860.958 448.216h-693.907c-10.28 0-20.56-5.14-28.272-12.852s-10.28-17.992-10.28-28.272l51.4-591.106c2.572-20.56 17.992-35.98 38.552-35.98h591.106c20.56 0 35.98 15.42 38.552 35.98l51.4 591.106c0 10.28-2.572 20.56-10.28 28.272s-17.992 12.852-28.272 12.852z" />
+<glyph unicode="&#xe937;" glyph-name="triangle" d="M985.175 69.138l-359.803 608.239c-17.135 29.983-47.117 51.4-81.383 59.967s-68.535 4.283-98.517-12.852c-17.135-8.565-34.265-25.7-42.835-42.835 0 0 0 0 0 0l-359.803-612.522c-34.265-59.967-12.852-141.352 47.117-175.618 17.135-12.852 38.552-17.135 59.967-17.135h728.173c34.265 0 68.535 12.852 89.952 38.552 25.7 25.7 38.552 55.683 38.552 89.952-4.283 21.417-8.565 47.117-21.417 64.252zM908.075-25.096c-8.565-8.565-21.417-12.852-29.983-12.852h-728.173c-8.565 0-12.852 0-21.417 4.283-21.417 12.852-25.7 38.552-17.135 59.967l364.088 603.956c4.283 4.283 8.565 12.852 12.852 12.852 21.417 12.852 47.117 4.283 59.967-12.852l364.088-603.956c4.283-4.283 4.283-12.852 4.283-21.417 4.283-12.852-4.283-21.417-8.565-29.983z" />
+<glyph unicode="&#xe938;" glyph-name="x" d="M573.972 304.723l227.018 227.018c17.135 17.135 17.135 42.835 0 59.967s-42.835 17.135-59.967 0l-227.018-227.018-227.018 227.018c-17.135 17.135-42.835 17.135-59.967 0s-17.135-42.835 0-59.967l227.018-227.018-227.018-227.018c-17.135-17.135-17.135-42.835 0-59.967 8.565-8.565 17.135-12.852 29.983-12.852s21.417 4.283 29.983 12.852l227.018 227.018 227.018-227.018c8.565-8.565 21.417-12.852 29.983-12.852s21.417 4.283 29.983 12.852c17.135 17.135 17.135 42.835 0 59.967l-227.018 227.018z" />
+<glyph unicode="&#xe939;" glyph-name="wrench-2" d="M200.462-189.15c-43.692 0-87.38 17.992-120.792 51.4-28.272 25.7-48.832 71.96-48.832 118.22 0 43.692 17.992 84.812 48.832 118.22l331.533 328.963c-2.572 17.992-5.14 35.98-5.14 53.972 0 161.912 133.641 295.553 295.553 295.553 35.98 0 66.82-7.712 92.52-15.42s41.12-28.272 43.692-48.832c2.572-17.992 0-35.98-10.28-51.4l-5.14-7.712-110.512-110.512c-2.572-2.572-5.14-5.14-5.14-7.712s2.572-5.14 5.14-7.712l38.552-38.552c5.14-5.14 12.852-5.14 17.992 0l107.94 107.94c12.852 17.992 38.552 25.7 59.112 20.56 20.56-2.572 41.12-17.992 48.832-41.12 7.712-28.272 15.42-59.112 15.42-95.092 0-161.912-133.641-295.553-295.553-295.553-17.992 0-35.98 2.572-53.972 5.14l-331.533-331.533c-33.412-30.84-74.532-48.832-118.22-48.832zM701.617 700.079c-120.792 0-218.452-97.66-218.452-218.452 0-20.56 2.572-35.98 7.712-59.112l5.14-20.56-359.803-359.803c-17.992-17.992-28.272-41.12-28.272-61.68 0-17.992 7.712-46.26 25.7-61.68 38.552-38.552 95.092-38.552 128.5-5.14l359.803 359.803 20.56-5.14c17.992-5.14 35.98-7.712 56.54-7.712 120.792 0 218.452 97.66 218.452 218.452 0 15.42-2.572 28.272-5.14 46.26l-89.952-92.52c-35.98-35.98-89.952-35.98-125.932 0l-38.552 38.552c-17.992 17.992-25.7 38.552-25.7 64.252 0 23.132 10.28 46.26 25.7 64.252l95.092 95.092c-20.56 2.572-35.98 5.14-51.4 5.14z" />
+<glyph unicode="&#xe93a;" glyph-name="chat" horiz-adv-x="883" d="M808.511 594.119h-735.011c-36.751 0-73.502-36.751-73.502-73.502v-441.006c0-36.751 36.751-73.502 73.502-73.502h294.004l294.004-220.503v220.503h147.002c36.751 0 73.502 36.751 73.502 73.502v441.006c0 36.751-36.751 73.502-73.502 73.502z" />
+<glyph unicode="&#xe93b;" glyph-name="bell" horiz-adv-x="965" d="M948.623 54.347l-35.372 61.098c-12.865 22.51-25.725 41.805-35.372 57.881-35.372 54.665-54.665 86.824-67.53 151.136l-45.020 215.45c-25.725 138.275-147.92 234.744-286.194 237.959h-6.43c-141.49 0-266.901-106.117-289.411-247.607l-28.94-183.293c-12.865-86.824-38.59-131.843-86.824-209.019-6.43-12.865-16.080-25.725-22.51-41.805l-22.51-41.805c-25.725-41.805-25.725-96.47 0-138.275 19.295-45.020 67.53-70.745 118.98-70.745h215.45c12.865-54.665 64.315-96.47 125.41-96.47 57.881 0 112.549 41.805 125.41 96.47h215.45c48.235 0 99.685 25.725 125.41 70.745 22.51 41.805 22.51 96.47 0 138.275zM823.212-58.201h-681.722c-32.155 0-54.665 35.372-38.59 64.315l22.51 41.805c61.098 106.117 106.117 160.784 122.195 282.979l28.94 183.293c19.295 93.255 96.47 167.215 196.156 167.215h3.215c93.255 0 173.646-67.53 189.725-157.568l45.020-215.45c19.295-106.117 57.881-147.92 115.765-241.176l35.372-61.098c16.080-28.94-6.43-64.315-38.59-64.315z" />
+<glyph unicode="&#xe93c;" glyph-name="disks-nav" d="M514.004 714.565c-163.547 0-327.093-42.055-327.093-140.183v-560.733c0-98.129 163.547-140.183 327.093-140.183s327.093 42.055 327.093 140.183v560.733c0 98.129-163.547 140.183-327.093 140.183zM747.643 392.143c-14.020-14.020-93.455-51.4-233.638-51.4s-219.62 37.381-233.638 51.4v79.436c60.745-23.365 149.529-37.381 233.638-37.381s172.893 14.020 233.638 37.381v-79.436zM747.643 205.232c-14.020-14.020-93.455-51.4-233.638-51.4s-219.62 37.381-233.638 51.4v79.436c60.745-23.365 149.529-37.381 233.638-37.381s172.893 14.020 233.638 37.381v-79.436zM514.004 621.109c130.838 0 205.602-28.035 228.966-46.728-23.365-18.69-98.129-46.728-228.966-46.728s-205.602 28.035-228.966 46.728c23.365 18.69 98.129 46.728 228.966 46.728zM514.004-33.080c-140.183 0-219.62 32.71-233.638 51.4v79.436c60.745-23.365 149.529-37.381 233.638-37.381s172.893 14.020 233.638 37.381v-79.436c-14.020-18.69-93.455-51.4-233.638-51.4z" />
+<glyph unicode="&#xe93d;" glyph-name="wrench-nav" d="M186.911-173.263c-37.381 0-74.765 14.020-98.129 42.055-56.075 56.075-56.075 144.855 0 196.256l341.112 341.112c-4.675 28.035-9.345 51.4-9.345 74.765 0 154.201 126.165 280.367 280.367 280.367 42.055 0 88.783-9.345 130.838-32.71 14.020-4.675 23.365-18.69 23.365-32.71s-4.675-28.035-14.020-42.055l-121.492-121.492 37.381-37.381 121.492 121.492c9.345 9.345 23.365 14.020 42.055 14.020 14.020-4.675 28.035-9.345 32.71-23.365 18.69-42.055 28.035-84.11 28.035-126.165 0-154.201-126.165-280.367-280.367-280.367-23.365 0-46.728 4.675-70.090 9.345l-341.112-341.112c-28.035-28.035-65.42-42.055-102.8-42.055zM700.915 667.836c-102.8 0-186.911-84.11-186.911-186.911 0-23.365 4.675-46.728 14.020-70.090 4.675-18.69 4.675-37.381-9.345-51.4l-364.477-364.477c-18.69-18.69-18.69-46.728 0-65.42s46.728-18.69 65.42 0l364.477 364.477c14.020 14.020 32.71 18.69 51.4 9.345 23.365-9.345 46.728-14.020 70.090-14.020 102.8 0 186.911 84.11 186.911 186.911 0 4.675 0 9.345 0 18.69l-98.129-98.129c-18.69-18.69-46.728-18.69-65.42 0l-102.8 102.8c-14.020 9.345-18.69 18.69-18.69 32.71s4.675 23.365 14.020 32.71l98.129 102.8c-4.675 0-14.020 0-18.69 0z" />
+<glyph unicode="&#xe93e;" glyph-name="user" d="M591.684 296.809c59.17 28.3 100.33 90.040 100.33 162.070 0 100.33-79.75 180.078-180.078 180.078s-180.078-79.75-180.078-180.078c0-72.030 41.16-131.2 100.33-162.070-84.895-20.58-177.505-120.91-177.505-234.101v-146.635c0-12.865 7.72-25.725 18.010-25.725h478.491c10.29 0 18.010 10.29 18.010 25.725v146.635c0 113.191-90.040 210.948-177.505 234.101z" />
+<glyph unicode="&#xe93f;" glyph-name="cloud" d="M839.043-49.656h-649.071c-102.9 0-189.972 87.071-189.972 197.887 0 79.154 43.534 150.395 110.817 182.056 0 7.917 0 15.829 0 23.746 0 150.395 114.775 269.127 257.253 269.127 87.071 0 166.225-43.534 213.719-118.733 23.746 7.917 47.492 11.875 71.239 11.875 102.9 0 189.972-71.239 217.676-174.141 91.030-15.829 158.309-94.986 158.309-193.93 0-110.817-83.113-197.887-189.972-197.887zM368.070 544.006c-98.944 0-178.099-87.071-178.099-189.972 0-15.829 0-27.704 3.958-43.534l7.917-39.579-35.621-7.917c-51.45-11.875-87.071-59.367-87.071-114.775 0-67.283 47.492-118.733 110.817-118.733h649.071c59.367 0 110.817 51.45 110.817 118.733s-47.492 118.733-110.817 118.733h-39.579l-3.958 35.621c-7.917 79.154-71.239 138.521-142.48 138.521-23.746 0-47.492-7.917-71.239-19.787l-39.579-23.746-19.787 39.579c-23.746 67.283-87.071 106.858-154.352 106.858z" />
+<glyph unicode="&#xe940;" glyph-name="users-trio" horiz-adv-x="1336" d="M1185.94 229.922c43.735 41.16 69.46 102.9 69.46 164.642 0 131.2-102.9 231.528-231.528 231.528-46.305 0-90.040-12.865-126.055-36.015-20.58 108.046-113.191 187.795-228.956 187.795-118.336 0-208.375-82.32-228.956-190.368-36.015 23.155-77.175 36.015-126.055 36.015-131.2 0-231.528-102.9-231.528-231.528 0-64.315 25.725-120.91 69.46-164.642-82.32-46.305-151.78-144.062-151.78-254.681v-156.925c0-36.015 25.725-66.885 56.595-66.885h511.934c33.445 0 59.17 30.87 61.74 66.885v87.465h77.175v-87.465c0-36.015 25.725-66.885 56.595-66.885h511.934c33.445 0 59.17 30.87 61.74 66.885v156.925c0 110.62-72.030 208.375-151.78 257.253zM547.951-173.965h-475.919v144.062c0 97.755 84.895 192.94 159.497 210.948 15.435 5.145 25.725 18.010 28.3 33.445s-5.145 30.87-20.58 38.59c-51.45 28.3-84.895 79.75-84.895 138.917 0 87.465 66.885 154.352 154.352 154.352s154.352-69.46 154.352-154.352c0-59.17-33.445-113.191-84.895-138.917-12.865-7.72-20.58-23.155-20.58-38.59s12.865-28.3 28.3-33.445c77.175-20.58 159.497-110.62 159.497-210.948v-144.062zM707.448-19.614h-77.175c-2.575 108.046-74.605 200.658-151.78 249.536 23.155 20.58 41.16 48.88 54.025 79.75 18.010 12.865 36.015 23.155 56.595 25.725 15.435 5.145 25.725 18.010 28.3 33.445s-5.145 30.87-20.58 38.59c-20.58 12.865-41.16 28.3-54.025 46.305-5.145 23.155-15.435 46.305-28.3 64.315-2.575 7.72-2.575 18.010-2.575 25.725 0 87.465 66.885 154.352 154.352 154.352s154.352-69.46 154.352-154.352c0-59.17-33.445-113.191-84.895-138.917-12.865-7.72-20.58-23.155-20.58-38.59s12.865-28.3 28.3-33.445c23.155-5.145 48.88-20.58 72.030-38.59 12.865-25.725 28.3-48.88 48.88-66.885-84.895-46.305-154.352-141.49-156.925-246.963zM1255.398-173.965h-475.919v144.062c0 97.755 84.895 192.94 159.497 210.948 15.435 5.145 25.725 18.010 28.3 33.445s-5.145 30.87-20.58 38.59c-51.45 28.3-84.895 79.75-84.895 138.917 0 87.465 66.885 154.352 154.352 154.352s154.352-69.46 154.352-154.352c0-59.17-33.445-113.191-84.895-138.917-12.865-7.72-20.58-23.155-20.58-38.59s12.865-28.3 28.3-33.445c77.175-20.58 159.497-110.62 159.497-210.948v-144.062z" />
+<glyph unicode="&#xe941;" glyph-name="nav-chat" d="M732.183-188.177c-7.917 0-15.829 3.958-23.746 7.917l-281 209.76h-277.042c-59.367 0-110.817 55.408-110.817 110.817v348.282c0 59.367 55.408 114.775 110.817 114.775h724.268c59.367 0 114.775-55.408 114.775-114.775v-348.282c0-59.367-55.408-110.817-110.817-110.817h-106.858v-178.099c0-15.829-7.917-27.704-23.746-35.621-3.958-3.958-7.917-3.958-15.829-3.958zM150.395 524.218c-11.875 0-31.663-19.787-31.663-35.621v-348.282c0-15.829 19.787-31.663 31.663-31.663h288.916c7.917 0 15.829-3.958 23.746-7.917l225.591-170.184v138.521c0 23.746 15.829 39.579 39.579 39.579h146.437c15.829 0 31.663 19.787 31.663 31.663v348.282c3.958 15.829-15.829 35.621-27.704 35.621h-728.225z" />
+<glyph unicode="&#xe94c;" glyph-name="map2" d="M674.632 583.142l-321.253 128.5-353.378-128.5v-771.007l353.378 128.5 321.253-128.5 353.378 128.5v771.007l-353.378-128.5zM385.503 629.594l257.002-102.8v-632.606l-257.002 102.798v632.608zM64.252 538.139l257.002 93.454v-634.274l-257.002-93.452v634.272zM963.758-14.36l-257.002-93.456v634.274l257.002 93.454v-634.272z" />
+<glyph unicode="&#xe956;" glyph-name="eye-closed" d="M1021.295 278.801c-41.16 77.175-100.33 144.062-172.36 192.94l-128.626-128.626c7.72-23.155 12.865-48.88 12.865-77.175 0-120.91-97.755-218.666-218.666-218.666-28.3 0-54.025 5.145-77.175 12.865l-82.32-82.32c51.45-12.865 105.475-20.58 159.497-20.58 216.093 0 409.033 113.191 506.789 293.269l7.72 12.865-7.72 15.435zM180.078 57.562l128.626 128.626c-7.72 23.155-12.865 48.88-12.865 77.175 0 120.91 97.755 218.666 218.666 218.666 28.3 0 54.025-5.145 77.175-12.865l82.32 82.32c-51.45 12.865-105.475 20.58-159.497 20.58-218.666 0-411.606-113.191-506.789-293.269l-7.72-15.435 7.72-15.435c41.16-77.175 100.33-141.49 172.36-190.368zM128.626-161.105c-10.29 0-20.58 2.575-28.3 10.29-15.435 15.435-15.435 38.59 0 54.025l771.761 771.761c15.435 15.435 38.59 15.435 54.025 0s15.435-38.59 0-54.025l-771.761-771.761c-5.145-7.72-15.435-10.29-25.725-10.29z" />
+<glyph unicode="&#xe957;" glyph-name="eye-open" d="M1021.295 278.801c-97.755 180.078-290.697 293.269-506.789 293.269-218.666 0-411.606-113.191-506.789-293.269l-7.72-15.435 7.72-15.435c97.755-180.078 290.697-293.269 506.789-293.269s409.033 113.191 506.789 293.269l7.72 15.435-7.72 15.435zM514.506 44.699c-120.91 0-218.666 97.755-218.666 218.666s97.755 218.666 218.666 218.666 218.666-97.755 218.666-218.666-97.755-218.666-218.666-218.666zM553.096 301.954c-25.725 25.725-25.725 66.885 0 90.040 25.725 25.725 66.885 25.725 90.040 0s25.725-66.885 0-90.040c-25.725-25.725-64.315-25.725-90.040 0z" />
+<glyph unicode="&#xe965;" glyph-name="book-pencil" horiz-adv-x="909" d="M896.657 469.766l-118.501 114.551c-15.799 15.799-39.501 15.799-55.3 0l-395.002-395.002c-7.901-7.901-11.851-15.799-11.851-27.65v-158h158c11.851 0 19.749 3.95 27.65 11.851l395.002 398.953c7.901 3.95 11.851 15.799 11.851 27.65 0 7.901-3.95 19.749-11.851 27.65zM458.203 82.663h-63.201v63.201l355.502 355.502 63.201-63.201-355.502-355.502zM730.755 149.814l-51.35-51.35c-3.95-3.95-7.901-11.851-7.901-19.749v-193.552c0-23.7-15.799-39.501-39.501-39.501h-474.002c-23.7 0-39.501 15.799-39.501 39.501v118.501c23.7 0 39.501 15.799 39.501 39.501s-15.799 39.501-39.501 39.501v79c23.7 0 39.501 15.799 39.501 39.501s-15.799 39.501-39.501 39.501v79c23.7 0 39.501 15.799 39.501 39.501s-15.799 39.501-39.501 39.501v79c23.7 0 39.501 15.799 39.501 39.501s-15.799 39.501-39.501 39.501v118.501c0 23.7 15.799 39.501 39.501 39.501h474.002c23.7 0 39.501-15.799 39.501-39.501v-31.601c23.7 19.749 51.35 31.601 79 31.601 0 67.151-51.35 118.501-118.501 118.501h-474.002c-67.151 0-118.501-51.35-118.501-118.501v-118.501c-23.7 0-39.501-15.799-39.501-39.501s15.799-39.501 39.501-39.501v-79c-23.7 0-39.501-15.799-39.501-39.501s15.799-39.501 39.501-39.501v-79c-23.7 0-39.501-15.799-39.501-39.501s15.799-39.501 39.501-39.501v-79c-23.7 0-39.501-15.799-39.501-39.501s15.799-39.501 39.501-39.501v-118.501c0-67.151 51.35-118.501 118.501-118.501h474.002c67.151 0 118.501 51.35 118.501 118.501v256.751c0 11.851-11.851 15.799-19.749 7.901z" />
+<glyph unicode="&#xe9da;" glyph-name="heart" d="M758.145 711.644c-108.051 0-201.042-87.898-244.116-179.7-43.106 91.802-136.11 179.7-244.168 179.7-148.962 0-269.861-120.912-269.861-269.885 0-303.028 305.693-382.486 514.027-682.078 196.922 297.737 513.982 388.723 513.982 682.078 0 148.972-120.902 269.885-269.865 269.885z" />
+<glyph unicode="&#xea2e;" glyph-name="loop2" d="M893.164 608.923c-93.976 102.616-229.047 166.972-379.159 166.972-283.877 0-514.004-230.128-514.004-514.004h96.376c0 230.65 186.979 417.629 417.629 417.629 123.501 0 234.457-53.626 310.909-138.847l-150.282-150.28h353.378v353.378l-134.846-134.846zM931.634 261.89c0-230.65-186.979-417.629-417.629-417.629-123.501 0-234.457 53.626-310.907 138.847l150.28 150.28h-353.378v-353.378l134.846 134.846c93.976-102.616 229.047-166.972 379.159-166.972 283.877 0 514.004 230.128 514.004 514.004h-96.376z" />
+<glyph unicode="&#xeab0;" glyph-name="github" d="M514.012 763.202c-283.845 0-514.012-230.116-514.012-514.002 0-227.1 147.279-419.77 351.507-487.738 25.686-4.758 35.128 11.154 35.128 24.728 0 12.252-0.48 52.747-0.7 95.696-143.006-31.096-173.18 60.646-173.18 60.646-23.374 59.408-57.072 75.208-57.072 75.208-46.633 31.902 3.522 31.245 3.522 31.245 51.6-3.626 78.784-52.974 78.784-52.974 45.852-78.578 120.244-55.857 149.588-42.726 4.604 33.214 17.921 55.898 32.634 68.732-114.174 12.994-234.189 57.074-234.189 254.023 0 56.118 20.084 101.971 52.968 137.966-5.336 12.952-22.942 65.228 4.972 136.031 0 0 43.174 13.804 141.392-52.694 40.996 11.392 84.968 17.104 128.656 17.302 43.674-0.198 87.678-5.91 128.758-17.302 98.118 66.504 141.207 52.694 141.207 52.694 27.98-70.804 10.39-123.080 5.056-136.031 32.948-35.996 52.902-81.852 52.902-137.966 0-197.424-120.246-240.89-234.706-253.613 18.436-15.954 34.86-47.23 34.86-95.184 0-68.776-0.6-124.128-0.6-141.058 0-13.68 9.258-29.71 35.308-24.662 204.118 68.040 351.212 260.643 351.212 487.67 0 283.887-230.132 514.002-513.996 514.002z" />
+<glyph unicode="&#xeabd;" glyph-name="tux" d="M569.879 36.093c-82.264-38.266-158.778-37.864-210.16-34.152-61.292 4.426-110.59 21.208-132.258 35.872-13.352 9.042-31.508 5.542-40.549-7.814-9.040-13.354-5.54-31.51 7.814-40.549 34.834-23.578 96.444-41.114 160.79-45.76 10.91-0.788 22.886-1.282 35.786-1.282 56.002 0 127.122 5.336 203.212 40.73 14.62 6.806 20.958 24.17 14.16 38.792-6.804 14.622-24.172 20.952-38.794 14.164zM894.437 79.361c2.798 253.677 28.874 733.065-456.752 694.32-479.47-38.594-352.338-545.094-359.484-714.738-6.332-89.736-36.118-199.426-78.2-311.059h129.605c13.318 47.306 23.116 94.088 27.34 138.69 7.814-5.448 16.172-10.714 25.091-15.76 14.514-8.55 26.988-19.92 40.196-31.958 30.864-28.126 65.846-60.008 134.236-64.001 4.588-0.262 9.21-0.394 13.728-0.394 69.165 0 116.469 30.273 154.481 54.594 18.212 11.656 33.95 21.724 48.755 26.556 42.074 13.172 78.84 34.432 106.32 61.492 4.292 4.224 8.274 8.57 12.010 13 15.306-56.098 36.258-119.222 59.52-182.215h276.729c-66.434 102.624-134.963 203.166-133.572 331.477zM124.596 217.364c0 0.016 0 0.030-0.002 0.046-4.766 82.786 34.846 152.427 88.47 155.543 53.62 3.118 100.953-61.468 105.716-144.255 0-0.014 0.004-0.030 0.004-0.044 0.256-4.462 0.368-8.882 0.37-13.258-16.992-4.272-32.318-10.476-46.052-17.698-0.052 0.616-0.092 1.22-0.152 1.838 0 0.008 0 0.018 0 0.026-4.586 46.994-29.688 82.481-56.072 79.266-26.384-3.216-44.052-43.922-39.466-90.914 0-0.010 0.004-0.018 0.004-0.026 2-20.488 7.9-38.788 16.106-52.648-2.042-1.612-7.816-5.836-14.462-10.696-4.99-3.65-11.064-8.090-18.386-13.482-19.958 26.198-33.638 63.828-36.080 106.306zM667.865 12.74c-1.908-43.758-59.14-84.924-112.018-101.44l-0.296-0.096c-21.984-7.13-41.591-19.676-62.348-32.958-34.868-22.312-70.922-45.384-123.002-45.384-3.416 0-6.922 0.104-10.366 0.296-47.702 2.79-70.014 23.124-98.264 48.868-14.902 13.578-30.31 27.622-50.172 39.276l-0.424 0.244c-42.874 24.2-69.484 54.294-71.185 80.508-0.846 13.032 4.958 24.314 17.25 33.532 26.74 20.052 44.653 33.15 56.504 41.822 13.162 9.624 17.136 12.528 20.080 15.324 2.104 1.994 4.38 4.204 6.832 6.586 24.542 23.866 65.616 63.81 128.652 63.81 38.556 0 81.214-14.857 126.664-44.074 21.408-13.934 40.038-20.366 63.628-28.512 16.22-5.598 34.604-11.95 59.224-22.492l0.396-0.164c22.968-9.44 50.092-26.668 48.852-55.148zM655.202 115.513c-4.416 2.222-9.010 4.336-13.796 6.31-22.194 9.492-39.988 15.938-54.746 21.082 8.148 15.958 13.212 35.86 13.676 57.466 0 0.010 0 0.022 0 0.030 1.13 52.578-25.388 95.268-59.228 95.348-33.842 0.078-62.194-42.478-63.324-95.058 0-0.010 0-0.018 0-0.028-0.038-1.722-0.042-3.428-0.020-5.13-20.842 9.588-41.34 16.554-61.406 20.84-0.092 1.976-0.204 3.948-0.244 5.944 0 0.016 0 0.036 0 0.050-1.946 95.785 56.822 175.073 131.266 177.093 74.441 2.022 136.36-73.988 138.312-169.772 0-0.018 0-0.038 0-0.052 0.878-43.314-10.7-83.19-30.49-114.122z" />
+<glyph unicode="&#xeabe;" glyph-name="appleinc" d="M794.597 229.672c-1.298 130.19 106.172 192.628 110.974 195.73-60.388 88.364-154.453 100.47-187.975 101.868-80.054 8.106-156.205-47.132-196.834-47.132-40.526 0-103.222 45.934-169.613 44.728-87.256-1.296-167.712-50.735-212.641-128.883-90.657-157.311-23.218-390.362 65.144-517.946 43.176-62.448 94.66-132.592 162.258-130.088 65.096 2.6 89.712 42.122 168.412 42.122s100.82-42.122 169.712-40.83c70.046 1.3 114.429 63.646 157.305 126.288 49.582 72.452 69.998 142.594 71.201 146.196-1.556 0.71-136.592 52.44-137.946 207.945zM665.157 611.732c35.878 43.527 60.096 103.916 53.488 164.162-51.678-2.104-114.324-34.426-151.401-77.854-33.27-38.528-62.392-100.016-54.586-159.056 57.69-4.5 116.584 29.32 152.499 72.748z" />
+<glyph unicode="&#xeac2;" glyph-name="windows8" d="M0.35 261.89l-0.35 313.296 385.503 52.348v-365.644zM449.754 636.87l513.876 74.774v-449.754h-513.876zM963.756 197.639l-0.126-449.754-513.876 72.298v377.457zM385.503-171.638l-385.19 52.8-0.020 316.476h385.21z" />
 </font></defs></svg>
\ No newline at end of file
diff --git a/static/fonts/icomoon-v2.ttf b/static/fonts/icomoon-v2.ttf
index dd7991a36..6965427e0 100644
Binary files a/static/fonts/icomoon-v2.ttf and b/static/fonts/icomoon-v2.ttf differ
diff --git a/static/fonts/icomoon-v2.woff b/static/fonts/icomoon-v2.woff
index daae72396..02db64219 100644
Binary files a/static/fonts/icomoon-v2.woff and b/static/fonts/icomoon-v2.woff differ
diff --git a/static/fonts/proxima-nova-bold.otf b/static/fonts/proxima-nova-bold.otf
new file mode 100644
index 000000000..b477a4656
Binary files /dev/null and b/static/fonts/proxima-nova-bold.otf differ
diff --git a/static/fonts/proxima-nova-medium.otf b/static/fonts/proxima-nova-medium.otf
new file mode 100644
index 000000000..ca1363c86
Binary files /dev/null and b/static/fonts/proxima-nova-medium.otf differ
diff --git a/static/fonts/proxima-nova-semibold.otf b/static/fonts/proxima-nova-semibold.otf
new file mode 100644
index 000000000..6cc9bf2ae
Binary files /dev/null and b/static/fonts/proxima-nova-semibold.otf differ
diff --git a/static/fonts/proxima-nova.otf b/static/fonts/proxima-nova.otf
new file mode 100644
index 000000000..43132265f
Binary files /dev/null and b/static/fonts/proxima-nova.otf differ
diff --git a/static/img/favicon.png b/static/img/favicon.png
index 2c2ea940f..07b99465e 100644
Binary files a/static/img/favicon.png and b/static/img/favicon.png differ
diff --git a/static/img/hero-bg-light-1-diamond.png b/static/img/hero-bg-light-1-diamond.png
new file mode 100644
index 000000000..3b2db6b0e
Binary files /dev/null and b/static/img/hero-bg-light-1-diamond.png differ
diff --git a/static/img/influxdb/2-1-migration-dashboard.png b/static/img/influxdb/2-1-migration-dashboard.png
new file mode 100644
index 000000000..a1a6b7b67
Binary files /dev/null and b/static/img/influxdb/2-1-migration-dashboard.png differ
diff --git a/static/img/telegraf/new-citibike-query.png b/static/img/telegraf/new-citibike-query.png
new file mode 100644
index 000000000..c8287eb3c
Binary files /dev/null and b/static/img/telegraf/new-citibike-query.png differ
diff --git a/static/img/wind-turbine.jpg b/static/img/wind-turbine.jpg
new file mode 100644
index 000000000..80ed59133
Binary files /dev/null and b/static/img/wind-turbine.jpg differ
diff --git a/static/svgs/home-bg-circle-left.svg b/static/svgs/home-bg-circle-left.svg
new file mode 100644
index 000000000..d4f42ae9a
--- /dev/null
+++ b/static/svgs/home-bg-circle-left.svg
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- Generator: Adobe Illustrator 26.1.0, SVG Export Plug-In . SVG Version: 6.00 Build 0)  -->
+<svg version="1.1" id="circle" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"
+	 viewBox="0 0 1100 185" style="enable-background:new 0 0 1100 185;" xml:space="preserve">
+<style type="text/css">
+	.st0{fill:#1C0F65;}
+</style>
+<g>
+	<path class="st0" d="M424.7,185H0L0,0l791.9,0C684.8,84.7,560.3,148.5,424.7,185z"/>
+</g>
+</svg>
diff --git a/static/svgs/home-bg-circle-right.svg b/static/svgs/home-bg-circle-right.svg
new file mode 100644
index 000000000..a5b24afde
--- /dev/null
+++ b/static/svgs/home-bg-circle-right.svg
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- Generator: Adobe Illustrator 26.1.0, SVG Export Plug-In . SVG Version: 6.00 Build 0)  -->
+<svg version="1.1" id="circle" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"
+	 viewBox="0 0 1100 185" style="enable-background:new 0 0 1100 185;" xml:space="preserve">
+<style type="text/css">
+	.st0{fill:#1C0F65;}
+</style>
+<g>
+	<path class="st0" d="M675.3,185H1100V0H308.1C415.2,84.7,539.7,148.5,675.3,185z"/>
+</g>
+</svg>
diff --git a/yarn.lock b/yarn.lock
index c93dc2650..0ebb09a78 100644
--- a/yarn.lock
+++ b/yarn.lock
@@ -2,6 +2,27 @@
 # yarn lockfile v1
 
 
+"@babel/code-frame@^7.0.0":
+  version "7.16.7"
+  resolved "https://registry.yarnpkg.com/@babel/code-frame/-/code-frame-7.16.7.tgz#44416b6bd7624b998f5b1af5d470856c40138789"
+  integrity sha512-iAXqUn8IIeBTNd72xsFlgaXHkMBMt6y4HJp1tIaK465CWLT/fG1aqB7ykr95gHHmlBdGbFeWWfyB4NJJ0nmeIg==
+  dependencies:
+    "@babel/highlight" "^7.16.7"
+
+"@babel/helper-validator-identifier@^7.16.7":
+  version "7.16.7"
+  resolved "https://registry.yarnpkg.com/@babel/helper-validator-identifier/-/helper-validator-identifier-7.16.7.tgz#e8c602438c4a8195751243da9031d1607d247cad"
+  integrity sha512-hsEnFemeiW4D08A5gUAZxLBTXpZ39P+a+DGDsHw1yxqyQ/jzFEnxf5uTEGp+3bzAbNOxU1paTgYS4ECU/IgfDw==
+
+"@babel/highlight@^7.16.7":
+  version "7.16.10"
+  resolved "https://registry.yarnpkg.com/@babel/highlight/-/highlight-7.16.10.tgz#744f2eb81579d6eea753c227b0f570ad785aba88"
+  integrity sha512-5FnTQLSLswEj6IkgVw5KusNUUFY9ZGqe/TRFnP/BKYHYgfh7tc+C7mwiy95/yNP7Dh9x580Vv8r7u7ZfTBFxdw==
+  dependencies:
+    "@babel/helper-validator-identifier" "^7.16.7"
+    chalk "^2.0.0"
+    js-tokens "^4.0.0"
+
 "@nodelib/fs.scandir@2.1.5":
   version "2.1.5"
   resolved "https://registry.yarnpkg.com/@nodelib/fs.scandir/-/fs.scandir-2.1.5.tgz#7619c2eb21b25483f6d167548b4cfd5a7488c3d5"
@@ -23,17 +44,78 @@
     "@nodelib/fs.scandir" "2.1.5"
     fastq "^1.6.0"
 
-"@sindresorhus/is@^0.7.0":
-  version "0.7.0"
-  resolved "https://registry.yarnpkg.com/@sindresorhus/is/-/is-0.7.0.tgz#9a06f4f137ee84d7df0460c1fdb1135ffa6c50fd"
-  integrity sha512-ONhaKPIufzzrlNbqtWFFd+jlnemX6lJAgq9ZeiZtS7I1PIf/la7CW4m83rTXRnVnsMbW2k56pGYu7AUFJD9Pow==
+"@sindresorhus/is@^4.0.0":
+  version "4.4.0"
+  resolved "https://registry.yarnpkg.com/@sindresorhus/is/-/is-4.4.0.tgz#e277e5bdbdf7cb1e20d320f02f5e2ed113cd3185"
+  integrity sha512-QppPM/8l3Mawvh4rn9CNEYIU9bxpXUCRMaX9yUpvBk1nMKusLKpfXGDEKExKaPhLzcn3lzil7pR6rnJ11HgeRQ==
+
+"@szmarczak/http-timer@^4.0.5":
+  version "4.0.6"
+  resolved "https://registry.yarnpkg.com/@szmarczak/http-timer/-/http-timer-4.0.6.tgz#b4a914bb62e7c272d4e5989fe4440f812ab1d807"
+  integrity sha512-4BAffykYOgO+5nzBWYwE3W90sBgLJoUPRWWcL8wlyiM8IB8ipJz3UMJ9KXQd1RKQXpKp8Tutn80HZtWsu2u76w==
+  dependencies:
+    defer-to-connect "^2.0.0"
+
+"@types/cacheable-request@^6.0.1":
+  version "6.0.2"
+  resolved "https://registry.yarnpkg.com/@types/cacheable-request/-/cacheable-request-6.0.2.tgz#c324da0197de0a98a2312156536ae262429ff6b9"
+  integrity sha512-B3xVo+dlKM6nnKTcmm5ZtY/OL8bOAOd2Olee9M1zft65ox50OzjEHW91sDiU9j6cvW8Ejg1/Qkf4xd2kugApUA==
+  dependencies:
+    "@types/http-cache-semantics" "*"
+    "@types/keyv" "*"
+    "@types/node" "*"
+    "@types/responselike" "*"
+
+"@types/http-cache-semantics@*":
+  version "4.0.1"
+  resolved "https://registry.yarnpkg.com/@types/http-cache-semantics/-/http-cache-semantics-4.0.1.tgz#0ea7b61496902b95890dc4c3a116b60cb8dae812"
+  integrity sha512-SZs7ekbP8CN0txVG2xVRH6EgKmEm31BOxA07vkFaETzZz1xh+cbt8BcI0slpymvwhx5dlFnQG2rTlPVQn+iRPQ==
+
+"@types/keyv@*":
+  version "3.1.3"
+  resolved "https://registry.yarnpkg.com/@types/keyv/-/keyv-3.1.3.tgz#1c9aae32872ec1f20dcdaee89a9f3ba88f465e41"
+  integrity sha512-FXCJgyyN3ivVgRoml4h94G/p3kY+u/B86La+QptcqJaWtBWtmc6TtkNfS40n9bIvyLteHh7zXOtgbobORKPbDg==
+  dependencies:
+    "@types/node" "*"
+
+"@types/node@*":
+  version "17.0.14"
+  resolved "https://registry.yarnpkg.com/@types/node/-/node-17.0.14.tgz#33b9b94f789a8fedd30a68efdbca4dbb06b61f20"
+  integrity sha512-SbjLmERksKOGzWzPNuW7fJM7fk3YXVTFiZWB/Hs99gwhk+/dnrQRPBQjPW9aO+fi1tAffi9PrwFvsmOKmDTyng==
+
+"@types/normalize-package-data@^2.4.1":
+  version "2.4.1"
+  resolved "https://registry.yarnpkg.com/@types/normalize-package-data/-/normalize-package-data-2.4.1.tgz#d3357479a0fdfdd5907fe67e17e0a85c906e1301"
+  integrity sha512-Gj7cI7z+98M282Tqmp2K5EIsoouUEzbBJhQQzDE3jSIRk6r9gsz0oUokqIUR4u1R3dMHo0pDHM7sNOHyhulypw==
+
+"@types/responselike@*", "@types/responselike@^1.0.0":
+  version "1.0.0"
+  resolved "https://registry.yarnpkg.com/@types/responselike/-/responselike-1.0.0.tgz#251f4fe7d154d2bad125abe1b429b23afd262e29"
+  integrity sha512-85Y2BjiufFzaMIlvJDvTTB8Fxl2xfLo4HgmHzVBz08w4wDePCTjYw66PdrolO0kzli3yam/YCgRufyo1DdQVTA==
+  dependencies:
+    "@types/node" "*"
+
+aggregate-error@^3.0.0:
+  version "3.1.0"
+  resolved "https://registry.yarnpkg.com/aggregate-error/-/aggregate-error-3.1.0.tgz#92670ff50f5359bdb7a3e0d40d0ec30c5737687a"
+  integrity sha512-4I7Td01quW/RpocfNayFdFVk1qSuoh0E7JrbRJ16nH01HhKFQ88INq9Sd+nd72zqRySlr9BmDA8xlEJ6vJMrYA==
+  dependencies:
+    clean-stack "^2.0.0"
+    indent-string "^4.0.0"
 
 ansi-regex@^5.0.1:
   version "5.0.1"
   resolved "https://registry.yarnpkg.com/ansi-regex/-/ansi-regex-5.0.1.tgz#082cb2c89c9fe8659a311a53bd6a4dc5301db304"
   integrity sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==
 
-ansi-styles@^4.0.0, ansi-styles@^4.1.0:
+ansi-styles@^3.2.1:
+  version "3.2.1"
+  resolved "https://registry.yarnpkg.com/ansi-styles/-/ansi-styles-3.2.1.tgz#41fbb20243e50b12be0f04b8dedbf07520ce841d"
+  integrity sha512-VT0ZI6kZRdTh8YyJw3SMbYm/u+NqfsAxEpWO0Pf9sq8/e94WxxOpPKx9FR1FlyCtOVDNOQ+8ntlqFxiRc+r5qA==
+  dependencies:
+    color-convert "^1.9.0"
+
+ansi-styles@^4.0.0:
   version "4.3.0"
   resolved "https://registry.yarnpkg.com/ansi-styles/-/ansi-styles-4.3.0.tgz#edd803628ae71c04c85ae7a0906edad34b648937"
   integrity sha512-zbB9rCJAT1rbjiVDb2hqKFHNYLxgtk8NURxZ3IZwD3F6NtxbXZQCnnSi1Lkx+IDohdPlFp222wVALIheZJQSEg==
@@ -48,82 +130,38 @@ anymatch@~3.1.2:
     normalize-path "^3.0.0"
     picomatch "^2.0.4"
 
-arch@^2.1.0:
-  version "2.2.0"
-  resolved "https://registry.yarnpkg.com/arch/-/arch-2.2.0.tgz#1bc47818f305764f23ab3306b0bfc086c5a29d11"
-  integrity sha512-Of/R0wqp83cgHozfIYLbBMnej79U/SVGOOyuB3VVFv1NRM/PSFMK12x9KVtiYzJqmnU5WR2qp0Z5rHb7sWGnFQ==
-
-archive-type@^4.0.0:
-  version "4.0.0"
-  resolved "https://registry.yarnpkg.com/archive-type/-/archive-type-4.0.0.tgz#f92e72233056dfc6969472749c267bdb046b1d70"
-  integrity sha1-+S5yIzBW38aWlHJ0nCZ72wRrHXA=
-  dependencies:
-    file-type "^4.2.0"
-
 array-union@^2.1.0:
   version "2.1.0"
   resolved "https://registry.yarnpkg.com/array-union/-/array-union-2.1.0.tgz#b798420adbeb1de828d84acd8a2e23d3efe85e8d"
   integrity sha512-HGyxoOTYUyCM6stUe6EJgnd4EoewAI7zMdfqO+kGjnlZmBDz/cR5pf8r/cR4Wq60sL/p0IkcjUEEPwS3GFrIyw==
 
-at-least-node@^1.0.0:
-  version "1.0.0"
-  resolved "https://registry.yarnpkg.com/at-least-node/-/at-least-node-1.0.0.tgz#602cd4b46e844ad4effc92a8011a3c46e0238dc2"
-  integrity sha512-+q/t7Ekv1EDY2l6Gda6LLiX14rU9TV20Wa3ofeQmwPFZbOMo9DXrLbOjFaaclkXKWidIaopwAObQDqwWtGUjqg==
+array-union@^3.0.1:
+  version "3.0.1"
+  resolved "https://registry.yarnpkg.com/array-union/-/array-union-3.0.1.tgz#da52630d327f8b88cfbfb57728e2af5cd9b6b975"
+  integrity sha512-1OvF9IbWwaeiM9VhzYXVQacMibxpXOMYVNIvMtKRyX9SImBXpKcFr8XvFDeEslCyuH/t6KRt7HEO94AlP8Iatw==
 
 autoprefixer@^10.2.5:
-  version "10.3.7"
-  resolved "https://registry.yarnpkg.com/autoprefixer/-/autoprefixer-10.3.7.tgz#cef2562058406bd378c94aacda36bb46a97b3186"
-  integrity sha512-EmGpu0nnQVmMhX8ROoJ7Mx8mKYPlcUHuxkwrRYEYMz85lu7H09v8w6R1P0JPdn/hKU32GjpLBFEOuIlDWCRWvg==
+  version "10.4.2"
+  resolved "https://registry.yarnpkg.com/autoprefixer/-/autoprefixer-10.4.2.tgz#25e1df09a31a9fba5c40b578936b90d35c9d4d3b"
+  integrity sha512-9fOPpHKuDW1w/0EKfRmVnxTDt8166MAnLI3mgZ1JCnhNtYWxcJ6Ud5CO/AVOZi/AvFa8DY9RTy3h3+tFBlrrdQ==
   dependencies:
-    browserslist "^4.17.3"
-    caniuse-lite "^1.0.30001264"
-    fraction.js "^4.1.1"
+    browserslist "^4.19.1"
+    caniuse-lite "^1.0.30001297"
+    fraction.js "^4.1.2"
     normalize-range "^0.1.2"
-    picocolors "^0.2.1"
-    postcss-value-parser "^4.1.0"
+    picocolors "^1.0.0"
+    postcss-value-parser "^4.2.0"
+
+balanced-match@^1.0.0:
+  version "1.0.2"
+  resolved "https://registry.yarnpkg.com/balanced-match/-/balanced-match-1.0.2.tgz#e83e3a7e3f300b34cb9d87f615fa0cbf357690ee"
+  integrity sha512-3oSeUO0TMV67hN1AmbXsK4yaqU7tjiHlbxRDZOpH0KW9+CeX4bRAaX0Anxt0tx2MrpRpWwQaPwIlISEJhYU5Pw==
 
 base64-js@^1.3.1:
   version "1.5.1"
   resolved "https://registry.yarnpkg.com/base64-js/-/base64-js-1.5.1.tgz#1b1b440160a5bf7ad40b650f095963481903930a"
   integrity sha512-AKpaYlHn8t4SVbOHCy+b5+KKgvR4vrsD8vbvrbiQJps7fKDTkjkDry6ji0rUJjC0kzbNePLwzxq8iypo41qeWA==
 
-bin-check@^4.1.0:
-  version "4.1.0"
-  resolved "https://registry.yarnpkg.com/bin-check/-/bin-check-4.1.0.tgz#fc495970bdc88bb1d5a35fc17e65c4a149fc4a49"
-  integrity sha512-b6weQyEUKsDGFlACWSIOfveEnImkJyK/FGW6FAG42loyoquvjdtOIqO6yBFzHyqyVVhNgNkQxxx09SFLK28YnA==
-  dependencies:
-    execa "^0.7.0"
-    executable "^4.1.0"
-
-bin-version-check@^4.0.0:
-  version "4.0.0"
-  resolved "https://registry.yarnpkg.com/bin-version-check/-/bin-version-check-4.0.0.tgz#7d819c62496991f80d893e6e02a3032361608f71"
-  integrity sha512-sR631OrhC+1f8Cvs8WyVWOA33Y8tgwjETNPyyD/myRBXLkfS/vl74FmH/lFcRl9KY3zwGh7jFhvyk9vV3/3ilQ==
-  dependencies:
-    bin-version "^3.0.0"
-    semver "^5.6.0"
-    semver-truncate "^1.1.2"
-
-bin-version@^3.0.0:
-  version "3.1.0"
-  resolved "https://registry.yarnpkg.com/bin-version/-/bin-version-3.1.0.tgz#5b09eb280752b1bd28f0c9db3f96f2f43b6c0839"
-  integrity sha512-Mkfm4iE1VFt4xd4vH+gx+0/71esbfus2LsnCGe8Pi4mndSPyT+NGES/Eg99jx8/lUGWfu3z2yuB/bt5UB+iVbQ==
-  dependencies:
-    execa "^1.0.0"
-    find-versions "^3.0.0"
-
-bin-wrapper@^4.1.0:
-  version "4.1.0"
-  resolved "https://registry.yarnpkg.com/bin-wrapper/-/bin-wrapper-4.1.0.tgz#99348f2cf85031e3ef7efce7e5300aeaae960605"
-  integrity sha512-hfRmo7hWIXPkbpi0ZltboCMVrU+0ClXR/JgbCKKjlDjQf6igXa7OwdqNcFWQZPZTgiY7ZpzE3+LjjkLiTN2T7Q==
-  dependencies:
-    bin-check "^4.1.0"
-    bin-version-check "^4.0.0"
-    download "^7.1.0"
-    import-lazy "^3.1.0"
-    os-filter-obj "^2.0.0"
-    pify "^4.0.1"
-
 binary-extensions@^2.0.0:
   version "2.2.0"
   resolved "https://registry.yarnpkg.com/binary-extensions/-/binary-extensions-2.2.0.tgz#75f502eeaf9ffde42fc98829645be4ea76bd9e2d"
@@ -137,6 +175,14 @@ bl@^1.0.0:
     readable-stream "^2.3.5"
     safe-buffer "^5.1.1"
 
+brace-expansion@^1.1.7:
+  version "1.1.11"
+  resolved "https://registry.yarnpkg.com/brace-expansion/-/brace-expansion-1.1.11.tgz#3c7fcbf529d87226f3d2f52b966ff5271eb441dd"
+  integrity sha512-iCuPHDFgrHX7H2vEI/5xpz07zSHB00TpugqhmYtVmMO6518mCuRMoOYFldEBl0g187ufozdaHgWKcYFb61qGiA==
+  dependencies:
+    balanced-match "^1.0.0"
+    concat-map "0.0.1"
+
 braces@^3.0.1, braces@~3.0.2:
   version "3.0.2"
   resolved "https://registry.yarnpkg.com/braces/-/braces-3.0.2.tgz#3454e1a462ee8d599e236df336cd9ea4f8afe107"
@@ -144,16 +190,16 @@ braces@^3.0.1, braces@~3.0.2:
   dependencies:
     fill-range "^7.0.1"
 
-browserslist@^4.17.3:
-  version "4.17.3"
-  resolved "https://registry.yarnpkg.com/browserslist/-/browserslist-4.17.3.tgz#2844cd6eebe14d12384b0122d217550160d2d624"
-  integrity sha512-59IqHJV5VGdcJZ+GZ2hU5n4Kv3YiASzW6Xk5g9tf5a/MAzGeFwgGWU39fVzNIOVcgB3+Gp+kiQu0HEfTVU/3VQ==
+browserslist@^4.19.1:
+  version "4.19.1"
+  resolved "https://registry.yarnpkg.com/browserslist/-/browserslist-4.19.1.tgz#4ac0435b35ab655896c31d53018b6dd5e9e4c9a3"
+  integrity sha512-u2tbbG5PdKRTUoctO3NBD8FQ5HdPh1ZXPHzp1rwaa5jTc+RV9/+RlWiAIKmjRPQF+xbGM9Kklj5bZQFa2s/38A==
   dependencies:
-    caniuse-lite "^1.0.30001264"
-    electron-to-chromium "^1.3.857"
+    caniuse-lite "^1.0.30001286"
+    electron-to-chromium "^1.4.17"
     escalade "^3.1.1"
-    node-releases "^1.1.77"
-    picocolors "^0.2.1"
+    node-releases "^2.0.1"
+    picocolors "^1.0.0"
 
 buffer-alloc-unsafe@^1.1.0:
   version "1.1.0"
@@ -186,46 +232,59 @@ buffer@^5.2.1:
     base64-js "^1.3.1"
     ieee754 "^1.1.13"
 
-cacheable-request@^2.1.1:
-  version "2.1.4"
-  resolved "https://registry.yarnpkg.com/cacheable-request/-/cacheable-request-2.1.4.tgz#0d808801b6342ad33c91df9d0b44dc09b91e5c3d"
-  integrity sha1-DYCIAbY0KtM8kd+dC0TcCbkeXD0=
+cacheable-lookup@^5.0.3:
+  version "5.0.4"
+  resolved "https://registry.yarnpkg.com/cacheable-lookup/-/cacheable-lookup-5.0.4.tgz#5a6b865b2c44357be3d5ebc2a467b032719a7005"
+  integrity sha512-2/kNscPhpcxrOigMZzbiWF7dz8ilhb/nIHU3EyZiXWXpeq/au8qJ8VhdftMkty3n7Gj6HIGalQG8oiBNB3AJgA==
+
+cacheable-request@^7.0.2:
+  version "7.0.2"
+  resolved "https://registry.yarnpkg.com/cacheable-request/-/cacheable-request-7.0.2.tgz#ea0d0b889364a25854757301ca12b2da77f91d27"
+  integrity sha512-pouW8/FmiPQbuGpkXQ9BAPv/Mo5xDGANgSNXzTzJ8DrKGuXOssM4wIQRjfanNRh3Yu5cfYPvcorqbhg2KIJtew==
   dependencies:
-    clone-response "1.0.2"
-    get-stream "3.0.0"
-    http-cache-semantics "3.8.1"
-    keyv "3.0.0"
-    lowercase-keys "1.0.0"
-    normalize-url "2.0.1"
-    responselike "1.0.2"
+    clone-response "^1.0.2"
+    get-stream "^5.1.0"
+    http-cache-semantics "^4.0.0"
+    keyv "^4.0.0"
+    lowercase-keys "^2.0.0"
+    normalize-url "^6.0.1"
+    responselike "^2.0.0"
 
-caniuse-lite@^1.0.30001264:
-  version "1.0.30001264"
-  resolved "https://registry.yarnpkg.com/caniuse-lite/-/caniuse-lite-1.0.30001264.tgz#88f625a60efb6724c7c62ac698bc8dbd9757e55b"
-  integrity sha512-Ftfqqfcs/ePiUmyaySsQ4PUsdcYyXG2rfoBVsk3iY1ahHaJEw65vfb7Suzqm+cEkwwPIv/XWkg27iCpRavH4zA==
+caniuse-lite@^1.0.30001286, caniuse-lite@^1.0.30001297:
+  version "1.0.30001306"
+  resolved "https://registry.yarnpkg.com/caniuse-lite/-/caniuse-lite-1.0.30001306.tgz#582592afe243bad2223081b8abab07bf289cc699"
+  integrity sha512-Wd1OuggRzg1rbnM5hv1wXs2VkxJH/AA+LuudlIqvZiCvivF+wJJe2mgBZC8gPMgI7D76PP5CTx8Luvaqc1V6OQ==
 
-caw@^2.0.1:
+careful-downloader@^2.0.1:
   version "2.0.1"
-  resolved "https://registry.yarnpkg.com/caw/-/caw-2.0.1.tgz#6c3ca071fc194720883c2dc5da9b074bfc7e9e95"
-  integrity sha512-Cg8/ZSBEa8ZVY9HspcGUYaK63d/bN7rqS3CYCzEGUxuYv6UlmcjzDUz2fCFFHyTvUW5Pk0I+3hkA3iXlIj6guA==
+  resolved "https://registry.yarnpkg.com/careful-downloader/-/careful-downloader-2.0.1.tgz#2e2ad890108ba881895837f01865de978a9e1b91"
+  integrity sha512-nSvCrtMhl3Mtkif2RyOdswyvWQpgPO03fAym/5p0g84YWKf4gpulAjxPwiDfT8BRuoIVRBXUJtVTNnWI2jC0ig==
   dependencies:
-    get-proxy "^2.0.0"
-    isurl "^1.0.0-alpha5"
-    tunnel-agent "^0.6.0"
-    url-to-options "^1.0.1"
+    debug "^4.3.2"
+    decompress "^4.2.1"
+    fs-extra "^10.0.0"
+    got "^11.8.2"
+    is-path-inside "^4.0.0"
+    tempy "^2.0.0"
 
-chalk@^4.0.0:
-  version "4.1.2"
-  resolved "https://registry.yarnpkg.com/chalk/-/chalk-4.1.2.tgz#aac4e2b7734a740867aeb16bf02aad556a1e7a01"
-  integrity sha512-oKnbhFyRIXpUuez8iBMmyEa4nbj4IOQyuhc/wy9kY7/WVPcwIO9VA668Pu8RkO7+0G76SLROeyw9CpQ061i4mA==
+chalk@^2.0.0:
+  version "2.4.2"
+  resolved "https://registry.yarnpkg.com/chalk/-/chalk-2.4.2.tgz#cd42541677a54333cf541a49108c1432b44c9424"
+  integrity sha512-Mti+f9lpJNcwF4tWV8/OrTTtF1gZi+f8FqlyAdouralcFWFQWF2+NgCHShjkCb+IFBLq9buZwE1xckQU4peSuQ==
   dependencies:
-    ansi-styles "^4.1.0"
-    supports-color "^7.1.0"
+    ansi-styles "^3.2.1"
+    escape-string-regexp "^1.0.5"
+    supports-color "^5.3.0"
+
+chalk@^5.0.0:
+  version "5.0.0"
+  resolved "https://registry.yarnpkg.com/chalk/-/chalk-5.0.0.tgz#bd96c6bb8e02b96e08c0c3ee2a9d90e050c7b832"
+  integrity sha512-/duVOqst+luxCQRKEo4bNxinsOQtMP80ZYm7mMqzuh5PociNL0PvmHFvREJ9ueYL2TxlHjBcmLCdmocx9Vg+IQ==
 
 chokidar@^3.3.0:
-  version "3.5.2"
-  resolved "https://registry.yarnpkg.com/chokidar/-/chokidar-3.5.2.tgz#dba3976fcadb016f66fd365021d91600d01c1e75"
-  integrity sha512-ekGhOnNVPgT77r4K/U3GDhu+FQ2S8TnK/s2KbIGXi0SZWuwkZ2QNyfWdZW+TVfn84DpEP7rLeCt2UI6bJ8GwbQ==
+  version "3.5.3"
+  resolved "https://registry.yarnpkg.com/chokidar/-/chokidar-3.5.3.tgz#1cf37c8707b932bd1af1ae22c0432e2acd1903bd"
+  integrity sha512-Dr3sfKRP6oTcjf2JmUmFJfeVMvXBdegxB0iVQ5eb2V10uFJUCAS8OByZdVAyVb8xXNz3GjjTgj9kLWsZTqE6kw==
   dependencies:
     anymatch "~3.1.2"
     braces "~3.0.2"
@@ -237,6 +296,11 @@ chokidar@^3.3.0:
   optionalDependencies:
     fsevents "~2.3.2"
 
+clean-stack@^2.0.0:
+  version "2.2.0"
+  resolved "https://registry.yarnpkg.com/clean-stack/-/clean-stack-2.2.0.tgz#ee8472dbb129e727b31e8a10a427dee9dfe4008b"
+  integrity sha512-4diC9HaTE+KRAMWhDhrGOECgWZxoevMc5TlkObMqNSsVU62PYzXZ/SMTjzyGAFF1YusgxGcSWTEXBhp0CPwQ1A==
+
 cliui@^7.0.2:
   version "7.0.4"
   resolved "https://registry.yarnpkg.com/cliui/-/cliui-7.0.4.tgz#a0265ee655476fc807aea9df3df8df7783808b4f"
@@ -246,13 +310,20 @@ cliui@^7.0.2:
     strip-ansi "^6.0.0"
     wrap-ansi "^7.0.0"
 
-clone-response@1.0.2:
+clone-response@^1.0.2:
   version "1.0.2"
   resolved "https://registry.yarnpkg.com/clone-response/-/clone-response-1.0.2.tgz#d1dc973920314df67fbeb94223b4ee350239e96b"
   integrity sha1-0dyXOSAxTfZ/vrlCI7TuNQI56Ws=
   dependencies:
     mimic-response "^1.0.0"
 
+color-convert@^1.9.0:
+  version "1.9.3"
+  resolved "https://registry.yarnpkg.com/color-convert/-/color-convert-1.9.3.tgz#bb71850690e1f136567de629d2d5471deda4c1e8"
+  integrity sha512-QfAUtd+vFdAtFQcC8CCyYt1fYWxSqAiK2cSD6zDB8N3cpsEBAvRxp9zOGg6G/SHHJYAT88/az/IuDGALsNVbGg==
+  dependencies:
+    color-name "1.1.3"
+
 color-convert@^2.0.1:
   version "2.0.1"
   resolved "https://registry.yarnpkg.com/color-convert/-/color-convert-2.0.1.tgz#72d3a68d598c9bdb3af2ad1e84f21d896abd4de3"
@@ -260,6 +331,11 @@ color-convert@^2.0.1:
   dependencies:
     color-name "~1.1.4"
 
+color-name@1.1.3:
+  version "1.1.3"
+  resolved "https://registry.yarnpkg.com/color-name/-/color-name-1.1.3.tgz#a7d0558bd89c42f795dd42328f740831ca53bc25"
+  integrity sha1-p9BVi9icQveV3UIyj3QIMcpTvCU=
+
 color-name@~1.1.4:
   version "1.1.4"
   resolved "https://registry.yarnpkg.com/color-name/-/color-name-1.1.4.tgz#c2a09a87acbde69543de6f63fa3995c826c536a2"
@@ -270,57 +346,36 @@ commander@^2.8.1:
   resolved "https://registry.yarnpkg.com/commander/-/commander-2.20.3.tgz#fd485e84c03eb4881c20722ba48035e8531aeb33"
   integrity sha512-GpVkmM8vF2vQUkj2LvZmD35JxeJOLCwJ9cUkugyk2nuhbv3+mJvpLYYt+0+USMxE+oj+ey/lJEnhZw75x/OMcQ==
 
-config-chain@^1.1.11:
-  version "1.1.13"
-  resolved "https://registry.yarnpkg.com/config-chain/-/config-chain-1.1.13.tgz#fad0795aa6a6cdaff9ed1b68e9dff94372c232f4"
-  integrity sha512-qj+f8APARXHrM0hraqXYb2/bOVSV4PvJQlNZ/DVj0QrmNM2q2euizkeuVckQ57J+W0mRH6Hvi+k50M4Jul2VRQ==
-  dependencies:
-    ini "^1.3.4"
-    proto-list "~1.2.1"
-
-content-disposition@^0.5.2:
-  version "0.5.3"
-  resolved "https://registry.yarnpkg.com/content-disposition/-/content-disposition-0.5.3.tgz#e130caf7e7279087c5616c2007d0485698984fbd"
-  integrity sha512-ExO0774ikEObIAEV9kDo50o+79VCUdEB6n6lzKgGwupcVeRlhrj3qGAfwq8G6uBJjkqLrhT0qEYFcWng8z1z0g==
-  dependencies:
-    safe-buffer "5.1.2"
+concat-map@0.0.1:
+  version "0.0.1"
+  resolved "https://registry.yarnpkg.com/concat-map/-/concat-map-0.0.1.tgz#d8a96bd77fd68df7793a73036a3ba0d5405d477b"
+  integrity sha1-2Klr13/Wjfd5OnMDajug1UBdR3s=
 
 core-util-is@~1.0.0:
   version "1.0.3"
   resolved "https://registry.yarnpkg.com/core-util-is/-/core-util-is-1.0.3.tgz#a6042d3634c2b27e9328f837b965fac83808db85"
   integrity sha512-ZQBvi1DcpJ4GDqanjucZ2Hj3wEO5pZDS89BWbkcrvdxksJorwUDDZamX9ldFkp9aw2lmBDLgkObEA4DWNJ9FYQ==
 
-cross-spawn@^5.0.1:
-  version "5.1.0"
-  resolved "https://registry.yarnpkg.com/cross-spawn/-/cross-spawn-5.1.0.tgz#e8bd0efee58fcff6f8f94510a0a554bbfa235449"
-  integrity sha1-6L0O/uWPz/b4+UUQoKVUu/ojVEk=
+crypto-random-string@^4.0.0:
+  version "4.0.0"
+  resolved "https://registry.yarnpkg.com/crypto-random-string/-/crypto-random-string-4.0.0.tgz#5a3cc53d7dd86183df5da0312816ceeeb5bb1fc2"
+  integrity sha512-x8dy3RnvYdlUcPOjkEHqozhiwzKNSq7GcPuXFbnyMOCHxX8V3OgIg/pYuabl2sbUPfIJaeAQB7PMOK8DFIdoRA==
   dependencies:
-    lru-cache "^4.0.1"
-    shebang-command "^1.2.0"
-    which "^1.2.9"
+    type-fest "^1.0.1"
 
-cross-spawn@^6.0.0:
-  version "6.0.5"
-  resolved "https://registry.yarnpkg.com/cross-spawn/-/cross-spawn-6.0.5.tgz#4a5ec7c64dfae22c3a14124dbacdee846d80cbc4"
-  integrity sha512-eTVLrBSt7fjbDygz805pMnstIs2VTBNkRm0qxZd+M7A5XDdxVRWO5MxGBXZhjY4cqLYLdtrGqRf8mBPmzwSpWQ==
+debug@^4.3.2:
+  version "4.3.3"
+  resolved "https://registry.yarnpkg.com/debug/-/debug-4.3.3.tgz#04266e0b70a98d4462e6e288e38259213332b664"
+  integrity sha512-/zxw5+vh1Tfv+4Qn7a5nsbcJKPaSvCDhojn6FEl9vupwK2VCSDtEiEtqr8DFtzYFOdz63LBkxec7DYuc2jon6Q==
   dependencies:
-    nice-try "^1.0.4"
-    path-key "^2.0.1"
-    semver "^5.5.0"
-    shebang-command "^1.2.0"
-    which "^1.2.9"
+    ms "2.1.2"
 
-decode-uri-component@^0.2.0:
-  version "0.2.0"
-  resolved "https://registry.yarnpkg.com/decode-uri-component/-/decode-uri-component-0.2.0.tgz#eb3913333458775cb84cd1a1fae062106bb87545"
-  integrity sha1-6zkTMzRYd1y4TNGh+uBiEGu4dUU=
-
-decompress-response@^3.3.0:
-  version "3.3.0"
-  resolved "https://registry.yarnpkg.com/decompress-response/-/decompress-response-3.3.0.tgz#80a4dd323748384bfa248083622aedec982adff3"
-  integrity sha1-gKTdMjdIOEv6JICDYirt7Jgq3/M=
+decompress-response@^6.0.0:
+  version "6.0.0"
+  resolved "https://registry.yarnpkg.com/decompress-response/-/decompress-response-6.0.0.tgz#ca387612ddb7e104bd16d85aab00d5ecf09c66fc"
+  integrity sha512-aW35yZM6Bb/4oJlZncMH2LCoZtJXTRxES17vE3hoRiowU2kWHaJKFkSBDnDR+cm9J+9QhXmREyIfv0pji9ejCQ==
   dependencies:
-    mimic-response "^1.0.0"
+    mimic-response "^3.1.0"
 
 decompress-tar@^4.0.0, decompress-tar@^4.1.0, decompress-tar@^4.1.1:
   version "4.1.1"
@@ -361,7 +416,7 @@ decompress-unzip@^4.0.1:
     pify "^2.3.0"
     yauzl "^2.4.2"
 
-decompress@^4.2.0:
+decompress@^4.2.1:
   version "4.2.1"
   resolved "https://registry.yarnpkg.com/decompress/-/decompress-4.2.1.tgz#007f55cc6a62c055afa37c07eb6a4ee1b773f118"
   integrity sha512-e48kc2IjU+2Zw8cTb6VZcJQ3lgVbS4uuB1TfCHbiZIP/haNXm+SVyhu+87jts5/3ROpd82GSVCoNs/z8l4ZOaQ==
@@ -375,10 +430,29 @@ decompress@^4.2.0:
     pify "^2.3.0"
     strip-dirs "^2.0.0"
 
-dependency-graph@^0.9.0:
-  version "0.9.0"
-  resolved "https://registry.yarnpkg.com/dependency-graph/-/dependency-graph-0.9.0.tgz#11aed7e203bc8b00f48356d92db27b265c445318"
-  integrity sha512-9YLIBURXj4DJMFALxXw9K3Y3rwb5Fk0X5/8ipCzaN84+gKxoHK43tVKRNakCQbiEx07E8Uwhuq21BpUagFhZ8w==
+defer-to-connect@^2.0.0:
+  version "2.0.1"
+  resolved "https://registry.yarnpkg.com/defer-to-connect/-/defer-to-connect-2.0.1.tgz#8016bdb4143e4632b77a3449c6236277de520587"
+  integrity sha512-4tvttepXG1VaYGrRibk5EwJd1t4udunSOVMdLSAL6mId1ix438oPwPZMALY41FCijukO1L0twNcGsdzS7dHgDg==
+
+del@^6.0.0:
+  version "6.0.0"
+  resolved "https://registry.yarnpkg.com/del/-/del-6.0.0.tgz#0b40d0332cea743f1614f818be4feb717714c952"
+  integrity sha512-1shh9DQ23L16oXSZKB2JxpL7iMy2E0S9d517ptA1P8iw0alkPtQcrKH7ru31rYtKwF499HkTu+DRzq3TCKDFRQ==
+  dependencies:
+    globby "^11.0.1"
+    graceful-fs "^4.2.4"
+    is-glob "^4.0.1"
+    is-path-cwd "^2.2.0"
+    is-path-inside "^3.0.2"
+    p-map "^4.0.0"
+    rimraf "^3.0.2"
+    slash "^3.0.0"
+
+dependency-graph@^0.11.0:
+  version "0.11.0"
+  resolved "https://registry.yarnpkg.com/dependency-graph/-/dependency-graph-0.11.0.tgz#ac0ce7ed68a54da22165a85e97a01d53f5eb2e27"
+  integrity sha512-JeMq7fEshyepOWDfcfHK06N3MhyPhz++vtqWhMT5O9A3K42rdsEDpfdVqjaqaAhsw6a+ZqeDvQVtD0hFHQWrzg==
 
 dir-glob@^3.0.1:
   version "3.0.1"
@@ -387,33 +461,10 @@ dir-glob@^3.0.1:
   dependencies:
     path-type "^4.0.0"
 
-download@^7.1.0:
-  version "7.1.0"
-  resolved "https://registry.yarnpkg.com/download/-/download-7.1.0.tgz#9059aa9d70b503ee76a132897be6dec8e5587233"
-  integrity sha512-xqnBTVd/E+GxJVrX5/eUJiLYjCGPwMpdL+jGhGU57BvtcA7wwhtHVbXBeUk51kOpW3S7Jn3BQbN9Q1R1Km2qDQ==
-  dependencies:
-    archive-type "^4.0.0"
-    caw "^2.0.1"
-    content-disposition "^0.5.2"
-    decompress "^4.2.0"
-    ext-name "^5.0.0"
-    file-type "^8.1.0"
-    filenamify "^2.0.0"
-    get-stream "^3.0.0"
-    got "^8.3.1"
-    make-dir "^1.2.0"
-    p-event "^2.1.0"
-    pify "^3.0.0"
-
-duplexer3@^0.1.4:
-  version "0.1.4"
-  resolved "https://registry.yarnpkg.com/duplexer3/-/duplexer3-0.1.4.tgz#ee01dd1cac0ed3cbc7fdbea37dc0a8f1ce002ce2"
-  integrity sha1-7gHdHKwO08vH/b6jfcCo8c4ALOI=
-
-electron-to-chromium@^1.3.857:
-  version "1.3.859"
-  resolved "https://registry.yarnpkg.com/electron-to-chromium/-/electron-to-chromium-1.3.859.tgz#4e0abc918e1c22b306ba13b4c3649f78295f5937"
-  integrity sha512-gXRXKNWedfdiKIzwr0Mg/VGCvxXzy+4SuK9hp1BDvfbCwx0O5Ot+2f4CoqQkqEJ3Zj/eAV/GoAFgBVFgkBLXuQ==
+electron-to-chromium@^1.4.17:
+  version "1.4.64"
+  resolved "https://registry.yarnpkg.com/electron-to-chromium/-/electron-to-chromium-1.4.64.tgz#8b1b5372f77ca208f2c498c6490da0e51176bd81"
+  integrity sha512-8mec/99xgLUZCIZZq3wt61Tpxg55jnOSpxGYapE/1Ma9MpFEYYaz4QNYm0CM1rrnCo7i3FRHhbaWjeCLsveGjQ==
 
 emoji-regex@^8.0.0:
   version "8.0.0"
@@ -427,68 +478,27 @@ end-of-stream@^1.0.0, end-of-stream@^1.1.0:
   dependencies:
     once "^1.4.0"
 
+error-ex@^1.3.1:
+  version "1.3.2"
+  resolved "https://registry.yarnpkg.com/error-ex/-/error-ex-1.3.2.tgz#b4ac40648107fdcdcfae242f428bea8a14d4f1bf"
+  integrity sha512-7dFHNmqeFSEt2ZBsCriorKnn3Z2pj+fd9kmI6QoWw4//DL+icEBfc0U7qJCisqrTsKTjw4fNFy2pW9OqStD84g==
+  dependencies:
+    is-arrayish "^0.2.1"
+
 escalade@^3.1.1:
   version "3.1.1"
   resolved "https://registry.yarnpkg.com/escalade/-/escalade-3.1.1.tgz#d8cfdc7000965c5a0174b4a82eaa5c0552742e40"
   integrity sha512-k0er2gUkLf8O0zKJiAhmkTnJlTvINGv7ygDNPbeIsX/TJjGJZHuh9B2UxbsaEkmlEo9MfhrSzmhIlhRlI2GXnw==
 
-escape-string-regexp@^1.0.2:
+escape-string-regexp@^1.0.5:
   version "1.0.5"
   resolved "https://registry.yarnpkg.com/escape-string-regexp/-/escape-string-regexp-1.0.5.tgz#1b61c0562190a8dff6ae3bb2cf0200ca130b86d4"
   integrity sha1-G2HAViGQqN/2rjuyzwIAyhMLhtQ=
 
-execa@^0.7.0:
-  version "0.7.0"
-  resolved "https://registry.yarnpkg.com/execa/-/execa-0.7.0.tgz#944becd34cc41ee32a63a9faf27ad5a65fc59777"
-  integrity sha1-lEvs00zEHuMqY6n68nrVpl/Fl3c=
-  dependencies:
-    cross-spawn "^5.0.1"
-    get-stream "^3.0.0"
-    is-stream "^1.1.0"
-    npm-run-path "^2.0.0"
-    p-finally "^1.0.0"
-    signal-exit "^3.0.0"
-    strip-eof "^1.0.0"
-
-execa@^1.0.0:
-  version "1.0.0"
-  resolved "https://registry.yarnpkg.com/execa/-/execa-1.0.0.tgz#c6236a5bb4df6d6f15e88e7f017798216749ddd8"
-  integrity sha512-adbxcyWV46qiHyvSp50TKt05tB4tK3HcmF7/nxfAdhnox83seTDbwnaqKO4sXRy7roHAIFqJP/Rw/AuEbX61LA==
-  dependencies:
-    cross-spawn "^6.0.0"
-    get-stream "^4.0.0"
-    is-stream "^1.1.0"
-    npm-run-path "^2.0.0"
-    p-finally "^1.0.0"
-    signal-exit "^3.0.0"
-    strip-eof "^1.0.0"
-
-executable@^4.1.0:
-  version "4.1.1"
-  resolved "https://registry.yarnpkg.com/executable/-/executable-4.1.1.tgz#41532bff361d3e57af4d763b70582db18f5d133c"
-  integrity sha512-8iA79xD3uAch729dUG8xaaBBFGaEa0wdD2VkYLFHwlqosEj/jT66AzcreRDSgV7ehnNLBW2WR5jIXwGKjVdTLg==
-  dependencies:
-    pify "^2.2.0"
-
-ext-list@^2.0.0:
-  version "2.2.2"
-  resolved "https://registry.yarnpkg.com/ext-list/-/ext-list-2.2.2.tgz#0b98e64ed82f5acf0f2931babf69212ef52ddd37"
-  integrity sha512-u+SQgsubraE6zItfVA0tBuCBhfU9ogSRnsvygI7wht9TS510oLkBRXBsqopeUG/GBOIQyKZO9wjTqIu/sf5zFA==
-  dependencies:
-    mime-db "^1.28.0"
-
-ext-name@^5.0.0:
-  version "5.0.0"
-  resolved "https://registry.yarnpkg.com/ext-name/-/ext-name-5.0.0.tgz#70781981d183ee15d13993c8822045c506c8f0a6"
-  integrity sha512-yblEwXAbGv1VQDmow7s38W77hzAgJAO50ztBLMcUyUBfxv1HC+LGwtiEN+Co6LtlqT/5uwVOxsD4TNIilWhwdQ==
-  dependencies:
-    ext-list "^2.0.0"
-    sort-keys-length "^1.0.0"
-
-fast-glob@^3.1.1:
-  version "3.2.7"
-  resolved "https://registry.yarnpkg.com/fast-glob/-/fast-glob-3.2.7.tgz#fd6cb7a2d7e9aa7a7846111e85a196d6b2f766a1"
-  integrity sha512-rYGMRwip6lUMvYD3BTScMwT1HtAs2d71SMv66Vrxs0IekGZEjhM0pcMfjQPnknBt2zeCwQMEupiN02ZP4DiT1Q==
+fast-glob@^3.2.7, fast-glob@^3.2.9:
+  version "3.2.11"
+  resolved "https://registry.yarnpkg.com/fast-glob/-/fast-glob-3.2.11.tgz#a1172ad95ceb8a16e20caa5c5e56480e5129c1d9"
+  integrity sha512-xrO3+1bxSo3ZVHAnqzyuewYT6aMFHRAd4Kcs92MAonjwQZLsK9d0SF1IyQ3k5PoirxTW0Oe/RqFgMQ6TcNE5Ew==
   dependencies:
     "@nodelib/fs.stat" "^2.0.2"
     "@nodelib/fs.walk" "^1.2.3"
@@ -515,11 +525,6 @@ file-type@^3.8.0:
   resolved "https://registry.yarnpkg.com/file-type/-/file-type-3.9.0.tgz#257a078384d1db8087bc449d107d52a52672b9e9"
   integrity sha1-JXoHg4TR24CHvESdEH1SpSZyuek=
 
-file-type@^4.2.0:
-  version "4.4.0"
-  resolved "https://registry.yarnpkg.com/file-type/-/file-type-4.4.0.tgz#1b600e5fca1fbdc6e80c0a70c71c8dba5f7906c5"
-  integrity sha1-G2AOX8ofvcboDApwxxyNul95BsU=
-
 file-type@^5.2.0:
   version "5.2.0"
   resolved "https://registry.yarnpkg.com/file-type/-/file-type-5.2.0.tgz#2ddbea7c73ffe36368dfae49dc338c058c2b8ad6"
@@ -530,25 +535,6 @@ file-type@^6.1.0:
   resolved "https://registry.yarnpkg.com/file-type/-/file-type-6.2.0.tgz#e50cd75d356ffed4e306dc4f5bcf52a79903a919"
   integrity sha512-YPcTBDV+2Tm0VqjybVd32MHdlEGAtuxS3VAYsumFokDSMG+ROT5wawGlnHDoz7bfMcMDt9hxuXvXwoKUx2fkOg==
 
-file-type@^8.1.0:
-  version "8.1.0"
-  resolved "https://registry.yarnpkg.com/file-type/-/file-type-8.1.0.tgz#244f3b7ef641bbe0cca196c7276e4b332399f68c"
-  integrity sha512-qyQ0pzAy78gVoJsmYeNgl8uH8yKhr1lVhW7JbzJmnlRi0I4R2eEDEJZVKG8agpDnLpacwNbDhLNG/LMdxHD2YQ==
-
-filename-reserved-regex@^2.0.0:
-  version "2.0.0"
-  resolved "https://registry.yarnpkg.com/filename-reserved-regex/-/filename-reserved-regex-2.0.0.tgz#abf73dfab735d045440abfea2d91f389ebbfa229"
-  integrity sha1-q/c9+rc10EVECr/qLZHzieu/oik=
-
-filenamify@^2.0.0:
-  version "2.1.0"
-  resolved "https://registry.yarnpkg.com/filenamify/-/filenamify-2.1.0.tgz#88faf495fb1b47abfd612300002a16228c677ee9"
-  integrity sha512-ICw7NTT6RsDp2rnYKVd8Fu4cr6ITzGy3+u4vUujPkabyaz+03F24NWEX7fs5fp+kBonlaqPH8fAO2NM+SXt/JA==
-  dependencies:
-    filename-reserved-regex "^2.0.0"
-    strip-outer "^1.0.0"
-    trim-repeated "^1.0.0"
-
 fill-range@^7.0.1:
   version "7.0.1"
   resolved "https://registry.yarnpkg.com/fill-range/-/fill-range-7.0.1.tgz#1919a6a7c75fe38b2c7c77e5198535da9acdda40"
@@ -556,67 +542,57 @@ fill-range@^7.0.1:
   dependencies:
     to-regex-range "^5.0.1"
 
-find-versions@^3.0.0:
-  version "3.2.0"
-  resolved "https://registry.yarnpkg.com/find-versions/-/find-versions-3.2.0.tgz#10297f98030a786829681690545ef659ed1d254e"
-  integrity sha512-P8WRou2S+oe222TOCHitLy8zj+SIsVJh52VP4lvXkaFVnOFFdoWv1H1Jjvel1aI6NCFOAaeAVm8qrI0odiLcww==
+find-up@^6.2.0:
+  version "6.2.0"
+  resolved "https://registry.yarnpkg.com/find-up/-/find-up-6.2.0.tgz#f3b81d633fa83bebe64f83a8bab357f86d5914be"
+  integrity sha512-yWHzMzXCaFoABSnFTCPKNFlYoq4mSga9QLRRKOCLSJ33hSkzROB14ITbAWW0QDQDyuzsPQ33S1DsOWQb/oW1yA==
   dependencies:
-    semver-regex "^2.0.0"
+    locate-path "^7.0.0"
+    path-exists "^5.0.0"
 
-fraction.js@^4.1.1:
-  version "4.1.1"
-  resolved "https://registry.yarnpkg.com/fraction.js/-/fraction.js-4.1.1.tgz#ac4e520473dae67012d618aab91eda09bcb400ff"
-  integrity sha512-MHOhvvxHTfRFpF1geTK9czMIZ6xclsEor2wkIGYYq+PxcQqT7vStJqjhe6S1TenZrMZzo+wlqOufBDVepUEgPg==
-
-from2@^2.1.1:
-  version "2.3.0"
-  resolved "https://registry.yarnpkg.com/from2/-/from2-2.3.0.tgz#8bfb5502bde4a4d36cfdeea007fcca21d7e382af"
-  integrity sha1-i/tVAr3kpNNs/e6gB/zKIdfjgq8=
-  dependencies:
-    inherits "^2.0.1"
-    readable-stream "^2.0.0"
+fraction.js@^4.1.2:
+  version "4.1.2"
+  resolved "https://registry.yarnpkg.com/fraction.js/-/fraction.js-4.1.2.tgz#13e420a92422b6cf244dff8690ed89401029fbe8"
+  integrity sha512-o2RiJQ6DZaR/5+Si0qJUIy637QMRudSi9kU/FFzx9EZazrIdnBgpU+3sEWCxAVhH2RtxW2Oz+T4p2o8uOPVcgA==
 
 fs-constants@^1.0.0:
   version "1.0.0"
   resolved "https://registry.yarnpkg.com/fs-constants/-/fs-constants-1.0.0.tgz#6be0de9be998ce16af8afc24497b9ee9b7ccd9ad"
   integrity sha512-y6OAwoSIf7FyjMIv94u+b5rdheZEjzR63GTyZJm5qh4Bi+2YgwLCcI/fPFZkL5PSixOt6ZNKm+w+Hfp/Bciwow==
 
-fs-extra@^9.0.0:
-  version "9.1.0"
-  resolved "https://registry.yarnpkg.com/fs-extra/-/fs-extra-9.1.0.tgz#5954460c764a8da2094ba3554bf839e6b9a7c86d"
-  integrity sha512-hcg3ZmepS30/7BSFqRvoo3DOMQu7IjqxO5nCDt+zM9XWjb33Wg7ziNT+Qvqbuc3+gWpzO02JubVyk2G4Zvo1OQ==
+fs-extra@^10.0.0:
+  version "10.0.0"
+  resolved "https://registry.yarnpkg.com/fs-extra/-/fs-extra-10.0.0.tgz#9ff61b655dde53fb34a82df84bb214ce802e17c1"
+  integrity sha512-C5owb14u9eJwizKGdchcDUQeFtlSHHthBk8pbX9Vc1PFZrLombudjDnNns88aYslCyF6IY5SUw3Roz6xShcEIQ==
   dependencies:
-    at-least-node "^1.0.0"
     graceful-fs "^4.2.0"
     jsonfile "^6.0.1"
     universalify "^2.0.0"
 
+fs.realpath@^1.0.0:
+  version "1.0.0"
+  resolved "https://registry.yarnpkg.com/fs.realpath/-/fs.realpath-1.0.0.tgz#1504ad2523158caa40db4a2787cb01411994ea4f"
+  integrity sha1-FQStJSMVjKpA20onh8sBQRmU6k8=
+
 fsevents@~2.3.2:
   version "2.3.2"
   resolved "https://registry.yarnpkg.com/fsevents/-/fsevents-2.3.2.tgz#8a526f78b8fdf4623b709e0b975c52c24c02fd1a"
   integrity sha512-xiqMQR4xAeHTuB9uWm+fFRcIOgKBMiOBP+eXiyT7jsgVCq1bkVygt00oASowB7EdtpOHaaPgKt812P9ab+DDKA==
 
+function-bind@^1.1.1:
+  version "1.1.1"
+  resolved "https://registry.yarnpkg.com/function-bind/-/function-bind-1.1.1.tgz#a56899d3ea3c9bab874bb9773b7c5ede92f4895d"
+  integrity sha512-yIovAzMX49sF8Yl58fSCWJ5svSLuaibPxXQJFLmBObTuCr0Mf1KiPopGM9NiFjiYBCbfaa2Fh6breQ6ANVTI0A==
+
 get-caller-file@^2.0.5:
   version "2.0.5"
   resolved "https://registry.yarnpkg.com/get-caller-file/-/get-caller-file-2.0.5.tgz#4f94412a82db32f36e3b0b9741f8a97feb031f7e"
   integrity sha512-DyFP3BM/3YHTQOCUL/w0OZHR0lpKeGrxotcHWcqNEdnltqFwXVfhEBQ94eIo34AfQpo0rGki4cyIiftY06h2Fg==
 
-get-proxy@^2.0.0:
-  version "2.1.0"
-  resolved "https://registry.yarnpkg.com/get-proxy/-/get-proxy-2.1.0.tgz#349f2b4d91d44c4d4d4e9cba2ad90143fac5ef93"
-  integrity sha512-zmZIaQTWnNQb4R4fJUEp/FC51eZsc6EkErspy3xtIYStaq8EB/hDIWipxsal+E8rz0qD7f2sL/NA9Xee4RInJw==
-  dependencies:
-    npm-conf "^1.1.0"
-
-get-stdin@^8.0.0:
-  version "8.0.0"
-  resolved "https://registry.yarnpkg.com/get-stdin/-/get-stdin-8.0.0.tgz#cbad6a73feb75f6eeb22ba9e01f89aa28aa97a53"
-  integrity sha512-sY22aA6xchAzprjyqmSEQv4UbAAzRN0L2dQB0NlN5acTTK9Don6nhoc3eAbUnpZiCANAMfd/+40kVdKfFygohg==
-
-get-stream@3.0.0, get-stream@^3.0.0:
-  version "3.0.0"
-  resolved "https://registry.yarnpkg.com/get-stream/-/get-stream-3.0.0.tgz#8e943d1358dc37555054ecbe2edb05aa174ede14"
-  integrity sha1-jpQ9E1jcN1VQVOy+LtsFqhdO3hQ=
+get-stdin@^9.0.0:
+  version "9.0.0"
+  resolved "https://registry.yarnpkg.com/get-stdin/-/get-stdin-9.0.0.tgz#3983ff82e03d56f1b2ea0d3e60325f39d703a575"
+  integrity sha512-dVKBjfWisLAicarI2Sf+JuBE/DghV4UzNAVe9yhEJuzeREd3JhOTE9cUaJTeSa77fsbQUK3pcOpJfM59+VKZaA==
 
 get-stream@^2.2.0:
   version "2.3.1"
@@ -626,10 +602,10 @@ get-stream@^2.2.0:
     object-assign "^4.0.1"
     pinkie-promise "^2.0.0"
 
-get-stream@^4.0.0:
-  version "4.1.0"
-  resolved "https://registry.yarnpkg.com/get-stream/-/get-stream-4.1.0.tgz#c1b255575f3dc21d59bfc79cd3d2b46b1c3a54b5"
-  integrity sha512-GMat4EJ5161kIy2HevLlr4luNjBgvmj413KaQA7jt4V8B4RDsfpHk7WQ9GVqfYyyx8OS/L66Kox+rJRNklLK7w==
+get-stream@^5.1.0:
+  version "5.2.0"
+  resolved "https://registry.yarnpkg.com/get-stream/-/get-stream-5.2.0.tgz#4966a1795ee5ace65e706c4b7beb71257d6e22d3"
+  integrity sha512-nBF+F1rAZVCu/p7rjzgA+Yb4lfYXrpl7a6VmJrU8wF9I1CKvP/QwPNZHnOlwbTkY6dvtFIzFMSyQXbLoTQPRpA==
   dependencies:
     pump "^3.0.0"
 
@@ -640,121 +616,137 @@ glob-parent@^5.1.2, glob-parent@~5.1.2:
   dependencies:
     is-glob "^4.0.1"
 
-globby@^11.0.0:
-  version "11.0.4"
-  resolved "https://registry.yarnpkg.com/globby/-/globby-11.0.4.tgz#2cbaff77c2f2a62e71e9b2813a67b97a3a3001a5"
-  integrity sha512-9O4MVG9ioZJ08ffbcyVYyLOJLk5JQ688pJ4eMGLpdWLHq/Wr1D9BlriLQyL0E+jbkuePVZXYFj47QM/v093wHg==
+glob@^7.1.3:
+  version "7.2.0"
+  resolved "https://registry.yarnpkg.com/glob/-/glob-7.2.0.tgz#d15535af7732e02e948f4c41628bd910293f6023"
+  integrity sha512-lmLf6gtyrPq8tTjSmrO94wBeQbFR3HbLHbuyD69wuyQkImp2hWqMGB47OX65FBkPffO641IP9jWa1z4ivqG26Q==
+  dependencies:
+    fs.realpath "^1.0.0"
+    inflight "^1.0.4"
+    inherits "2"
+    minimatch "^3.0.4"
+    once "^1.3.0"
+    path-is-absolute "^1.0.0"
+
+globby@^11.0.1:
+  version "11.1.0"
+  resolved "https://registry.yarnpkg.com/globby/-/globby-11.1.0.tgz#bd4be98bb042f83d796f7e3811991fbe82a0d34b"
+  integrity sha512-jhIXaOzy1sb8IyocaruWSn1TjmnBVs8Ayhcy83rmxNJ8q2uWKCAj3CnJY+KpGSXCueAPc0i05kVvVKtP1t9S3g==
   dependencies:
     array-union "^2.1.0"
     dir-glob "^3.0.1"
-    fast-glob "^3.1.1"
-    ignore "^5.1.4"
-    merge2 "^1.3.0"
+    fast-glob "^3.2.9"
+    ignore "^5.2.0"
+    merge2 "^1.4.1"
     slash "^3.0.0"
 
-got@^8.3.1:
-  version "8.3.2"
-  resolved "https://registry.yarnpkg.com/got/-/got-8.3.2.tgz#1d23f64390e97f776cac52e5b936e5f514d2e937"
-  integrity sha512-qjUJ5U/hawxosMryILofZCkm3C84PLJS/0grRIpjAwu+Lkxxj5cxeCU25BG0/3mDSpXKTyZr8oh8wIgLaH0QCw==
+globby@^12.0.0:
+  version "12.2.0"
+  resolved "https://registry.yarnpkg.com/globby/-/globby-12.2.0.tgz#2ab8046b4fba4ff6eede835b29f678f90e3d3c22"
+  integrity sha512-wiSuFQLZ+urS9x2gGPl1H5drc5twabmm4m2gTR27XDFyjUHJUNsS8o/2aKyIF6IoBaR630atdher0XJ5g6OMmA==
   dependencies:
-    "@sindresorhus/is" "^0.7.0"
-    cacheable-request "^2.1.1"
-    decompress-response "^3.3.0"
-    duplexer3 "^0.1.4"
-    get-stream "^3.0.0"
-    into-stream "^3.1.0"
-    is-retry-allowed "^1.1.0"
-    isurl "^1.0.0-alpha5"
-    lowercase-keys "^1.0.0"
-    mimic-response "^1.0.0"
-    p-cancelable "^0.4.0"
-    p-timeout "^2.0.1"
-    pify "^3.0.0"
-    safe-buffer "^5.1.1"
-    timed-out "^4.0.1"
-    url-parse-lax "^3.0.0"
-    url-to-options "^1.0.1"
+    array-union "^3.0.1"
+    dir-glob "^3.0.1"
+    fast-glob "^3.2.7"
+    ignore "^5.1.9"
+    merge2 "^1.4.1"
+    slash "^4.0.0"
 
-graceful-fs@^4.1.10, graceful-fs@^4.1.6, graceful-fs@^4.2.0:
-  version "4.2.8"
-  resolved "https://registry.yarnpkg.com/graceful-fs/-/graceful-fs-4.2.8.tgz#e412b8d33f5e006593cbd3cee6df9f2cebbe802a"
-  integrity sha512-qkIilPUYcNhJpd33n0GBXTB1MMPp14TxEsEs0pTrsSVucApsYzW5V+Q8Qxhik6KU3evy+qkAAowTByymK0avdg==
-
-has-flag@^4.0.0:
-  version "4.0.0"
-  resolved "https://registry.yarnpkg.com/has-flag/-/has-flag-4.0.0.tgz#944771fd9c81c81265c4d6941860da06bb59479b"
-  integrity sha512-EykJT/Q1KjTWctppgIAgfSO0tKVuZUjhgMr17kqTumMl6Afv3EISleU7qZUzoXDFTAHTDC4NOoG/ZxU3EvlMPQ==
-
-has-symbol-support-x@^1.4.1:
-  version "1.4.2"
-  resolved "https://registry.yarnpkg.com/has-symbol-support-x/-/has-symbol-support-x-1.4.2.tgz#1409f98bc00247da45da67cee0a36f282ff26455"
-  integrity sha512-3ToOva++HaW+eCpgqZrCfN51IPB+7bJNVT6CUATzueB5Heb8o6Nam0V3HG5dlDvZU1Gn5QLcbahiKw/XVk5JJw==
-
-has-to-string-tag-x@^1.2.0:
-  version "1.4.1"
-  resolved "https://registry.yarnpkg.com/has-to-string-tag-x/-/has-to-string-tag-x-1.4.1.tgz#a045ab383d7b4b2012a00148ab0aa5f290044d4d"
-  integrity sha512-vdbKfmw+3LoOYVr+mtxHaX5a96+0f3DljYd8JOqvOLsf5mw2Otda2qCDT9qRqLAhrjyQ0h7ual5nOiASpsGNFw==
+got@^11.8.2:
+  version "11.8.3"
+  resolved "https://registry.yarnpkg.com/got/-/got-11.8.3.tgz#f496c8fdda5d729a90b4905d2b07dbd148170770"
+  integrity sha512-7gtQ5KiPh1RtGS9/Jbv1ofDpBFuq42gyfEib+ejaRBJuj/3tQFeR5+gw57e4ipaU8c/rCjvX6fkQz2lyDlGAOg==
   dependencies:
-    has-symbol-support-x "^1.4.1"
+    "@sindresorhus/is" "^4.0.0"
+    "@szmarczak/http-timer" "^4.0.5"
+    "@types/cacheable-request" "^6.0.1"
+    "@types/responselike" "^1.0.0"
+    cacheable-lookup "^5.0.3"
+    cacheable-request "^7.0.2"
+    decompress-response "^6.0.0"
+    http2-wrapper "^1.0.0-beta.5.2"
+    lowercase-keys "^2.0.0"
+    p-cancelable "^2.0.0"
+    responselike "^2.0.0"
 
-http-cache-semantics@3.8.1:
-  version "3.8.1"
-  resolved "https://registry.yarnpkg.com/http-cache-semantics/-/http-cache-semantics-3.8.1.tgz#39b0e16add9b605bf0a9ef3d9daaf4843b4cacd2"
-  integrity sha512-5ai2iksyV8ZXmnZhHH4rWPoxxistEexSi5936zIQ1bnNTW5VnA85B6P/VpXiRM017IgRvb2kKo1a//y+0wSp3w==
+graceful-fs@^4.1.10, graceful-fs@^4.1.6, graceful-fs@^4.2.0, graceful-fs@^4.2.4:
+  version "4.2.9"
+  resolved "https://registry.yarnpkg.com/graceful-fs/-/graceful-fs-4.2.9.tgz#041b05df45755e587a24942279b9d113146e1c96"
+  integrity sha512-NtNxqUcXgpW2iMrfqSfR73Glt39K+BLwWsPs94yR63v45T0Wbej7eRmL5cWfwEgqXnmjQp3zaJTshdRW/qC2ZQ==
 
-hugo-extended@^0.83.1:
-  version "0.83.1"
-  resolved "https://registry.yarnpkg.com/hugo-extended/-/hugo-extended-0.83.1.tgz#49e8e682c6cb137a3c7684a783937494e82b1b85"
-  integrity sha512-t2PoRPvDdLyScmyyV09bKxOO5ZqdhzjglQ09dh+doaBrkKUN6j7HcmD0Ou+nPUsDLdV24MnAKVUROohlSpG1Kg==
+has-flag@^3.0.0:
+  version "3.0.0"
+  resolved "https://registry.yarnpkg.com/has-flag/-/has-flag-3.0.0.tgz#b5d454dc2199ae225699f3467e5a07f3b955bafd"
+  integrity sha1-tdRU3CGZriJWmfNGfloH87lVuv0=
+
+has@^1.0.3:
+  version "1.0.3"
+  resolved "https://registry.yarnpkg.com/has/-/has-1.0.3.tgz#722d7cbfc1f6aa8241f16dd814e011e1f41e8796"
+  integrity sha512-f2dvO0VU6Oej7RkWJGrehjbzMAjFp5/VKPp5tTpWIV4JHHZK1/BxbFRtf/siA2SWTe09caDmVtYYzWEIbBS4zw==
   dependencies:
-    bin-wrapper "^4.1.0"
+    function-bind "^1.1.1"
+
+hosted-git-info@^4.0.1:
+  version "4.1.0"
+  resolved "https://registry.yarnpkg.com/hosted-git-info/-/hosted-git-info-4.1.0.tgz#827b82867e9ff1c8d0c4d9d53880397d2c86d224"
+  integrity sha512-kyCuEOWjJqZuDbRHzL8V93NzQhwIB71oFWSyzVo+KPZI+pnQPPxucdkrOZvkLRnrf5URsQM+IJ09Dw29cRALIA==
+  dependencies:
+    lru-cache "^6.0.0"
+
+http-cache-semantics@^4.0.0:
+  version "4.1.0"
+  resolved "https://registry.yarnpkg.com/http-cache-semantics/-/http-cache-semantics-4.1.0.tgz#49e91c5cbf36c9b94bcfcd71c23d5249ec74e390"
+  integrity sha512-carPklcUh7ROWRK7Cv27RPtdhYhUsela/ue5/jKzjegVvXDqM2ILE9Q2BGn9JZJh1g87cp56su/FgQSzcWS8cQ==
+
+http2-wrapper@^1.0.0-beta.5.2:
+  version "1.0.3"
+  resolved "https://registry.yarnpkg.com/http2-wrapper/-/http2-wrapper-1.0.3.tgz#b8f55e0c1f25d4ebd08b3b0c2c079f9590800b3d"
+  integrity sha512-V+23sDMr12Wnz7iTcDeJr3O6AIxlnvT/bmaAAAP/Xda35C90p9599p0F1eHR/N1KILWSoWVAiOMFjBBXaXSMxg==
+  dependencies:
+    quick-lru "^5.1.1"
+    resolve-alpn "^1.0.0"
+
+hugo-extended@^0.92.1:
+  version "0.92.1"
+  resolved "https://registry.yarnpkg.com/hugo-extended/-/hugo-extended-0.92.1.tgz#aa82964fbbff7d02379168ea7ed0e3b12ed38a13"
+  integrity sha512-e/G4KcdvZOH//wiIy8f7DgqAp9yPJIgN23fPoOne1MhZcWKRutqSTNuUWt7NKXI7kDxAYzbsXSbsvvkN9pfpRQ==
+  dependencies:
+    careful-downloader "^2.0.1"
+    log-symbols "^5.1.0"
+    read-pkg-up "^9.0.0"
 
 ieee754@^1.1.13:
   version "1.2.1"
   resolved "https://registry.yarnpkg.com/ieee754/-/ieee754-1.2.1.tgz#8eb7a10a63fff25d15a57b001586d177d1b0d352"
   integrity sha512-dcyqhDvX1C46lXZcVqCpK+FtMRQVdIMN6/Df5js2zouUsqG7I6sFxitIC+7KYK29KdXOLHdu9zL4sFnoVQnqaA==
 
-ignore@^5.1.4:
-  version "5.1.8"
-  resolved "https://registry.yarnpkg.com/ignore/-/ignore-5.1.8.tgz#f150a8b50a34289b33e22f5889abd4d8016f0e57"
-  integrity sha512-BMpfD7PpiETpBl/A6S498BaIJ6Y/ABT93ETbby2fP00v4EbvPBXWEoaR1UBPKs3iR53pJY7EtZk5KACI57i1Uw==
+ignore@^5.1.9, ignore@^5.2.0:
+  version "5.2.0"
+  resolved "https://registry.yarnpkg.com/ignore/-/ignore-5.2.0.tgz#6d3bac8fa7fe0d45d9f9be7bac2fc279577e345a"
+  integrity sha512-CmxgYGiEPCLhfLnpPp1MoRmifwEIOgjcHXxOBjv7mY96c+eWScsOP9c112ZyLdWHi0FxHjI+4uVhKYp/gcdRmQ==
 
-import-cwd@^3.0.0:
-  version "3.0.0"
-  resolved "https://registry.yarnpkg.com/import-cwd/-/import-cwd-3.0.0.tgz#20845547718015126ea9b3676b7592fb8bd4cf92"
-  integrity sha512-4pnzH16plW+hgvRECbDWpQl3cqtvSofHWh44met7ESfZ8UZOWWddm8hEyDTqREJ9RbYHY8gi8DqmaelApoOGMg==
+indent-string@^4.0.0:
+  version "4.0.0"
+  resolved "https://registry.yarnpkg.com/indent-string/-/indent-string-4.0.0.tgz#624f8f4497d619b2d9768531d58f4122854d7251"
+  integrity sha512-EdDDZu4A2OyIK7Lr/2zG+w5jmbuk1DVBnEwREQvBzspBJkCEbRa8GxU1lghYcaGJCnRWibjDXlq779X1/y5xwg==
+
+inflight@^1.0.4:
+  version "1.0.6"
+  resolved "https://registry.yarnpkg.com/inflight/-/inflight-1.0.6.tgz#49bd6331d7d02d0c09bc910a1075ba8165b56df9"
+  integrity sha1-Sb1jMdfQLQwJvJEKEHW6gWW1bfk=
   dependencies:
-    import-from "^3.0.0"
+    once "^1.3.0"
+    wrappy "1"
 
-import-from@^3.0.0:
-  version "3.0.0"
-  resolved "https://registry.yarnpkg.com/import-from/-/import-from-3.0.0.tgz#055cfec38cd5a27d8057ca51376d7d3bf0891966"
-  integrity sha512-CiuXOFFSzkU5x/CR0+z7T91Iht4CXgfCxVOFRhh2Zyhg5wOpWvvDLQUsWl+gcN+QscYBjez8hDCt85O7RLDttQ==
-  dependencies:
-    resolve-from "^5.0.0"
-
-import-lazy@^3.1.0:
-  version "3.1.0"
-  resolved "https://registry.yarnpkg.com/import-lazy/-/import-lazy-3.1.0.tgz#891279202c8a2280fdbd6674dbd8da1a1dfc67cc"
-  integrity sha512-8/gvXvX2JMn0F+CDlSC4l6kOmVaLOO3XLkksI7CI3Ud95KDYJuYur2b9P/PUt/i/pDAMd/DulQsNbbbmRRsDIQ==
-
-inherits@^2.0.1, inherits@~2.0.3:
+inherits@2, inherits@~2.0.3:
   version "2.0.4"
   resolved "https://registry.yarnpkg.com/inherits/-/inherits-2.0.4.tgz#0fa2c64f932917c3433a0ded55363aae37416b7c"
   integrity sha512-k/vGaX4/Yla3WzyMCvTQOXYeIHvqOKtnqBduzTHpzpQZzAskKMhZ2K+EnBiSM9zGSoIFeMpXKxa4dYeZIQqewQ==
 
-ini@^1.3.4:
-  version "1.3.8"
-  resolved "https://registry.yarnpkg.com/ini/-/ini-1.3.8.tgz#a29da425b48806f34767a4efce397269af28432c"
-  integrity sha512-JV/yugV2uzW5iMRSiZAyDtQd+nxtUnjeLt0acNdw98kKLrvuRVyB80tsREOE7yvGVgalhZ6RNXCmEHkUKBKxew==
-
-into-stream@^3.1.0:
-  version "3.1.0"
-  resolved "https://registry.yarnpkg.com/into-stream/-/into-stream-3.1.0.tgz#96fb0a936c12babd6ff1752a17d05616abd094c6"
-  integrity sha1-lvsKk2wSur1v8XUqF9BWFqvQlMY=
-  dependencies:
-    from2 "^2.1.1"
-    p-is-promise "^1.1.0"
+is-arrayish@^0.2.1:
+  version "0.2.1"
+  resolved "https://registry.yarnpkg.com/is-arrayish/-/is-arrayish-0.2.1.tgz#77c99840527aa8ecb1a8ba697b80645a7a926a9d"
+  integrity sha1-d8mYQFJ6qOyxqLppe4BkWnqSap0=
 
 is-binary-path@~2.1.0:
   version "2.1.0"
@@ -763,6 +755,13 @@ is-binary-path@~2.1.0:
   dependencies:
     binary-extensions "^2.0.0"
 
+is-core-module@^2.5.0:
+  version "2.8.1"
+  resolved "https://registry.yarnpkg.com/is-core-module/-/is-core-module-2.8.1.tgz#f59fdfca701d5879d0a6b100a40aa1560ce27211"
+  integrity sha512-SdNCUs284hr40hFTFP6l0IfZ/RSrMXF3qgoRHd3/79unUTvrFO/JoXwkGm+5J/Oe3E/b5GsnG330uUNgRpu1PA==
+  dependencies:
+    has "^1.0.3"
+
 is-extglob@^2.1.1:
   version "2.1.1"
   resolved "https://registry.yarnpkg.com/is-extglob/-/is-extglob-2.1.1.tgz#a88c02535791f02ed37c76a1b9ea9773c833f8c2"
@@ -790,48 +789,55 @@ is-number@^7.0.0:
   resolved "https://registry.yarnpkg.com/is-number/-/is-number-7.0.0.tgz#7535345b896734d5f80c4d06c50955527a14f12b"
   integrity sha512-41Cifkg6e8TylSpdtTpeLVMqvSBEVzTttHvERD741+pnZ8ANv0004MRL43QKPDlK9cGvNp6NZWZUBlbGXYxxng==
 
-is-object@^1.0.1:
-  version "1.0.2"
-  resolved "https://registry.yarnpkg.com/is-object/-/is-object-1.0.2.tgz#a56552e1c665c9e950b4a025461da87e72f86fcf"
-  integrity sha512-2rRIahhZr2UWb45fIOuvZGpFtz0TyOZLf32KxBbSoUCeZR495zCKlWUKKUByk3geS2eAs7ZAABt0Y/Rx0GiQGA==
+is-path-cwd@^2.2.0:
+  version "2.2.0"
+  resolved "https://registry.yarnpkg.com/is-path-cwd/-/is-path-cwd-2.2.0.tgz#67d43b82664a7b5191fd9119127eb300048a9fdb"
+  integrity sha512-w942bTcih8fdJPJmQHFzkS76NEP8Kzzvmw92cXsazb8intwLqPibPPdXf4ANdKV3rYMuuQYGIWtvz9JilB3NFQ==
 
-is-plain-obj@^1.0.0:
-  version "1.1.0"
-  resolved "https://registry.yarnpkg.com/is-plain-obj/-/is-plain-obj-1.1.0.tgz#71a50c8429dfca773c92a390a4a03b39fcd51d3e"
-  integrity sha1-caUMhCnfync8kqOQpKA7OfzVHT4=
+is-path-inside@^3.0.2:
+  version "3.0.3"
+  resolved "https://registry.yarnpkg.com/is-path-inside/-/is-path-inside-3.0.3.tgz#d231362e53a07ff2b0e0ea7fed049161ffd16283"
+  integrity sha512-Fd4gABb+ycGAmKou8eMftCupSir5lRxqf4aD/vd0cD2qc4HL07OjCeuHMr8Ro4CoMaeCKDB0/ECBOVWjTwUvPQ==
 
-is-retry-allowed@^1.1.0:
-  version "1.2.0"
-  resolved "https://registry.yarnpkg.com/is-retry-allowed/-/is-retry-allowed-1.2.0.tgz#d778488bd0a4666a3be8a1482b9f2baafedea8b4"
-  integrity sha512-RUbUeKwvm3XG2VYamhJL1xFktgjvPzL0Hq8C+6yrWIswDy3BIXGqCxhxkc30N9jqK311gVU137K8Ei55/zVJRg==
+is-path-inside@^4.0.0:
+  version "4.0.0"
+  resolved "https://registry.yarnpkg.com/is-path-inside/-/is-path-inside-4.0.0.tgz#805aeb62c47c1b12fc3fd13bfb3ed1e7430071db"
+  integrity sha512-lJJV/5dYS+RcL8uQdBDW9c9uWFLLBNRyFhnAKXw5tVqLlKZ4RMGZKv+YQ/IA3OhD+RpbJa1LLFM1FQPGyIXvOA==
 
 is-stream@^1.1.0:
   version "1.1.0"
   resolved "https://registry.yarnpkg.com/is-stream/-/is-stream-1.1.0.tgz#12d4a3dd4e68e0b79ceb8dbc84173ae80d91ca44"
   integrity sha1-EtSj3U5o4Lec6428hBc66A2RykQ=
 
+is-stream@^3.0.0:
+  version "3.0.0"
+  resolved "https://registry.yarnpkg.com/is-stream/-/is-stream-3.0.0.tgz#e6bfd7aa6bef69f4f472ce9bb681e3e57b4319ac"
+  integrity sha512-LnQR4bZ9IADDRSkvpqMGvt/tEJWclzklNgSw48V5EAaAeDd6qGvN8ei6k5p0tvxSR171VmGyHuTiAOfxAbr8kA==
+
+is-unicode-supported@^1.1.0:
+  version "1.1.0"
+  resolved "https://registry.yarnpkg.com/is-unicode-supported/-/is-unicode-supported-1.1.0.tgz#9127b71f9fa82f52ca5c20e982e7bec0ee31ee1e"
+  integrity sha512-lDcxivp8TJpLG75/DpatAqNzOpDPSpED8XNtrpBHTdQ2InQ1PbW78jhwSxyxhhu+xbVSast2X38bwj8atwoUQA==
+
 isarray@~1.0.0:
   version "1.0.0"
   resolved "https://registry.yarnpkg.com/isarray/-/isarray-1.0.0.tgz#bb935d48582cba168c06834957a54a3e07124f11"
   integrity sha1-u5NdSFgsuhaMBoNJV6VKPgcSTxE=
 
-isexe@^2.0.0:
-  version "2.0.0"
-  resolved "https://registry.yarnpkg.com/isexe/-/isexe-2.0.0.tgz#e8fbf374dc556ff8947a10dcb0572d633f2cfa10"
-  integrity sha1-6PvzdNxVb/iUehDcsFctYz8s+hA=
+js-tokens@^4.0.0:
+  version "4.0.0"
+  resolved "https://registry.yarnpkg.com/js-tokens/-/js-tokens-4.0.0.tgz#19203fb59991df98e3a287050d4647cdeaf32499"
+  integrity sha512-RdJUflcE3cUzKiMqQgsCu06FPu9UdIJO0beYbPhHN4k6apgJtifcoCtT9bcxOpYBtpD2kCM6Sbzg4CausW/PKQ==
 
-isurl@^1.0.0-alpha5:
-  version "1.0.0"
-  resolved "https://registry.yarnpkg.com/isurl/-/isurl-1.0.0.tgz#b27f4f49f3cdaa3ea44a0a5b7f3462e6edc39d67"
-  integrity sha512-1P/yWsxPlDtn7QeRD+ULKQPaIaN6yF368GZ2vDfv0AL0NwpStafjWCDDdn0k8wgFMWpVAqG7oJhxHnlud42i9w==
-  dependencies:
-    has-to-string-tag-x "^1.2.0"
-    is-object "^1.0.1"
+json-buffer@3.0.1:
+  version "3.0.1"
+  resolved "https://registry.yarnpkg.com/json-buffer/-/json-buffer-3.0.1.tgz#9338802a30d3b6605fbe0613e094008ca8c05a13"
+  integrity sha512-4bV5BfR2mqfQTJm+V5tPPdf+ZpuhiIvTuAB5g8kcrXOZpTT/QwwVRWBywX1ozr6lEuPdbHxwaJlm9G6mI2sfSQ==
 
-json-buffer@3.0.0:
-  version "3.0.0"
-  resolved "https://registry.yarnpkg.com/json-buffer/-/json-buffer-3.0.0.tgz#5b1f397afc75d677bde8bcfc0e47e1f9a3d9a898"
-  integrity sha1-Wx85evx11ne96Lz8Dkfh+aPZqJg=
+json-parse-even-better-errors@^2.3.0:
+  version "2.3.1"
+  resolved "https://registry.yarnpkg.com/json-parse-even-better-errors/-/json-parse-even-better-errors-2.3.1.tgz#7c47805a94319928e05777405dc12e1f7a4ee02d"
+  integrity sha512-xyFwyhro/JEof6Ghe2iz2NcXoj2sloNsWr/XsERDK/oiPCfaNhl5ONfp+jQdAZRQQ0IJWNzH9zIZF7li91kh2w==
 
 jsonfile@^6.0.1:
   version "6.1.0"
@@ -842,69 +848,58 @@ jsonfile@^6.0.1:
   optionalDependencies:
     graceful-fs "^4.1.6"
 
-keyv@3.0.0:
-  version "3.0.0"
-  resolved "https://registry.yarnpkg.com/keyv/-/keyv-3.0.0.tgz#44923ba39e68b12a7cec7df6c3268c031f2ef373"
-  integrity sha512-eguHnq22OE3uVoSYG0LVWNP+4ppamWr9+zWBe1bsNcovIMy6huUJFPgy4mGwCd/rnl3vOLGW1MTlu4c57CT1xA==
+keyv@^4.0.0:
+  version "4.1.0"
+  resolved "https://registry.yarnpkg.com/keyv/-/keyv-4.1.0.tgz#8ab5ca4ae6a34e05c629531d9a7f871575af0d5b"
+  integrity sha512-YsY3wr6HabE11/sscee+3nZ03XjvkrPWGouAmJFBdZoK92wiOlJCzI5/sDEIKdJhdhHO144ei45U9gXfbu14Uw==
   dependencies:
-    json-buffer "3.0.0"
+    json-buffer "3.0.1"
 
-lilconfig@^2.0.3:
-  version "2.0.3"
-  resolved "https://registry.yarnpkg.com/lilconfig/-/lilconfig-2.0.3.tgz#68f3005e921dafbd2a2afb48379986aa6d2579fd"
-  integrity sha512-EHKqr/+ZvdKCifpNrJCKxBTgk5XupZA3y/aCPY9mxfgBzmgh93Mt/WqjjQ38oMxXuvDokaKiM3lAgvSH2sjtHg==
+lilconfig@^2.0.4:
+  version "2.0.4"
+  resolved "https://registry.yarnpkg.com/lilconfig/-/lilconfig-2.0.4.tgz#f4507d043d7058b380b6a8f5cb7bcd4b34cee082"
+  integrity sha512-bfTIN7lEsiooCocSISTWXkiWJkRqtL9wYtYy+8EK3Y41qh3mpwPU0ycTOgjdY9ErwXCc8QyrQp82bdL0Xkm9yA==
 
-lodash.difference@^4.5.0:
-  version "4.5.0"
-  resolved "https://registry.yarnpkg.com/lodash.difference/-/lodash.difference-4.5.0.tgz#9ccb4e505d486b91651345772885a2df27fd017c"
-  integrity sha1-nMtOUF1Ia5FlE0V3KIWi3yf9AXw=
+lines-and-columns@^1.1.6:
+  version "1.2.4"
+  resolved "https://registry.yarnpkg.com/lines-and-columns/-/lines-and-columns-1.2.4.tgz#eca284f75d2965079309dc0ad9255abb2ebc1632"
+  integrity sha512-7ylylesZQ/PV29jhEDl3Ufjo6ZX7gCqJr5F7PKrqc93v7fzSymt1BpwEU8nAUXs8qzzvqhbjhK5QZg6Mt/HkBg==
 
-lodash.forown@^4.4.0:
-  version "4.4.0"
-  resolved "https://registry.yarnpkg.com/lodash.forown/-/lodash.forown-4.4.0.tgz#85115cf04f73ef966eced52511d3893cc46683af"
-  integrity sha1-hRFc8E9z75ZuztUlEdOJPMRmg68=
-
-lodash.get@^4.4.2:
-  version "4.4.2"
-  resolved "https://registry.yarnpkg.com/lodash.get/-/lodash.get-4.4.2.tgz#2d177f652fa31e939b4438d5341499dfa3825e99"
-  integrity sha1-LRd/ZS+jHpObRDjVNBSZ36OCXpk=
-
-lodash.groupby@^4.6.0:
-  version "4.6.0"
-  resolved "https://registry.yarnpkg.com/lodash.groupby/-/lodash.groupby-4.6.0.tgz#0b08a1dcf68397c397855c3239783832df7403d1"
-  integrity sha1-Cwih3PaDl8OXhVwyOXg4Mt90A9E=
-
-lodash.sortby@^4.7.0:
-  version "4.7.0"
-  resolved "https://registry.yarnpkg.com/lodash.sortby/-/lodash.sortby-4.7.0.tgz#edd14c824e2cc9c1e0b0a1b42bb5210516a42438"
-  integrity sha1-7dFMgk4sycHgsKG0K7UhBRakJDg=
-
-lowercase-keys@1.0.0:
-  version "1.0.0"
-  resolved "https://registry.yarnpkg.com/lowercase-keys/-/lowercase-keys-1.0.0.tgz#4e3366b39e7f5457e35f1324bdf6f88d0bfc7306"
-  integrity sha1-TjNms55/VFfjXxMkvfb4jQv8cwY=
-
-lowercase-keys@^1.0.0:
-  version "1.0.1"
-  resolved "https://registry.yarnpkg.com/lowercase-keys/-/lowercase-keys-1.0.1.tgz#6f9e30b47084d971a7c820ff15a6c5167b74c26f"
-  integrity sha512-G2Lj61tXDnVFFOi8VZds+SoQjtQC3dgokKdDG2mTm1tx4m50NUHBOZSBwQQHyy0V12A0JTG4icfZQH+xPyh8VA==
-
-lru-cache@^4.0.1:
-  version "4.1.5"
-  resolved "https://registry.yarnpkg.com/lru-cache/-/lru-cache-4.1.5.tgz#8bbe50ea85bed59bc9e33dcab8235ee9bcf443cd"
-  integrity sha512-sWZlbEP2OsHNkXrMl5GYk/jKk70MBng6UU4YI/qGDYbgf6YbP4EvmqISbXCoJiRKs+1bSpFHVgQxvJ17F2li5g==
+locate-path@^7.0.0:
+  version "7.0.0"
+  resolved "https://registry.yarnpkg.com/locate-path/-/locate-path-7.0.0.tgz#f0a60c8dd7ef0f737699eb9461b9567a92bc97da"
+  integrity sha512-+cg2yXqDUKfo4hsFxwa3G1cBJeA+gs1vD8FyV9/odWoUlQe/4syxHQ5DPtKjtfm6gnKbZzjCqzX03kXosvZB1w==
   dependencies:
-    pseudomap "^1.0.2"
-    yallist "^2.1.2"
+    p-locate "^6.0.0"
 
-make-dir@^1.0.0, make-dir@^1.2.0:
+log-symbols@^5.1.0:
+  version "5.1.0"
+  resolved "https://registry.yarnpkg.com/log-symbols/-/log-symbols-5.1.0.tgz#a20e3b9a5f53fac6aeb8e2bb22c07cf2c8f16d93"
+  integrity sha512-l0x2DvrW294C9uDCoQe1VSU4gf529FkSZ6leBl4TiqZH/e+0R7hSfHQBNut2mNygDgHwvYHfFLn6Oxb3VWj2rA==
+  dependencies:
+    chalk "^5.0.0"
+    is-unicode-supported "^1.1.0"
+
+lowercase-keys@^2.0.0:
+  version "2.0.0"
+  resolved "https://registry.yarnpkg.com/lowercase-keys/-/lowercase-keys-2.0.0.tgz#2603e78b7b4b0006cbca2fbcc8a3202558ac9479"
+  integrity sha512-tqNXrS78oMOE73NMxK4EMLQsQowWf8jKooH9g7xPavRT706R6bkQJ6DY2Te7QukaZsulxa30wQ7bk0pm4XiHmA==
+
+lru-cache@^6.0.0:
+  version "6.0.0"
+  resolved "https://registry.yarnpkg.com/lru-cache/-/lru-cache-6.0.0.tgz#6d6fe6570ebd96aaf90fcad1dafa3b2566db3a94"
+  integrity sha512-Jo6dJ04CmSjuznwJSS3pUeWmd/H0ffTlkXXgwZi+eq1UCmqQwCh+eLsYOYCwY991i2Fah4h1BEMCx4qThGbsiA==
+  dependencies:
+    yallist "^4.0.0"
+
+make-dir@^1.0.0:
   version "1.3.0"
   resolved "https://registry.yarnpkg.com/make-dir/-/make-dir-1.3.0.tgz#79c1033b80515bd6d24ec9933e860ca75ee27f0c"
   integrity sha512-2w31R7SJtieJJnQtGc7RVL2StM2vGYVfqUOvUDxH6bC6aJTxPxTF0GnIgCyu7tjockiUWAYQRbxa7vKn34s5sQ==
   dependencies:
     pify "^3.0.0"
 
-merge2@^1.3.0:
+merge2@^1.3.0, merge2@^1.4.1:
   version "1.4.1"
   resolved "https://registry.yarnpkg.com/merge2/-/merge2-1.4.1.tgz#4368892f885e907455a6fd7dc55c0c9d404990ae"
   integrity sha512-8q7VEgMJW4J8tcfVPy8g09NcQwZdbwFEqhe/WZkoIzjn/3TGDwtOCYtXGxA3O8tPzpczCCDgv+P2P5y00ZJOOg==
@@ -917,35 +912,47 @@ micromatch@^4.0.4:
     braces "^3.0.1"
     picomatch "^2.2.3"
 
-mime-db@^1.28.0:
-  version "1.50.0"
-  resolved "https://registry.yarnpkg.com/mime-db/-/mime-db-1.50.0.tgz#abd4ac94e98d3c0e185016c67ab45d5fde40c11f"
-  integrity sha512-9tMZCDlYHqeERXEHO9f/hKfNXhre5dK2eE/krIvUjZbS2KPcqGDfNShIWS1uW9XOTKQKqK6qbeOci18rbfW77A==
-
 mimic-response@^1.0.0:
   version "1.0.1"
   resolved "https://registry.yarnpkg.com/mimic-response/-/mimic-response-1.0.1.tgz#4923538878eef42063cb8a3e3b0798781487ab1b"
   integrity sha512-j5EctnkH7amfV/q5Hgmoal1g2QHFJRraOtmx0JpIqkxhBhI/lJSl1nMpQ45hVarwNETOoWEimndZ4QK0RHxuxQ==
 
-nanocolors@^0.2.6:
-  version "0.2.12"
-  resolved "https://registry.yarnpkg.com/nanocolors/-/nanocolors-0.2.12.tgz#4d05932e70116078673ea4cc6699a1c56cc77777"
-  integrity sha512-SFNdALvzW+rVlzqexid6epYdt8H9Zol7xDoQarioEFcFN0JHo4CYNztAxmtfgGTVRCmFlEOqqhBpoFGKqSAMug==
+mimic-response@^3.1.0:
+  version "3.1.0"
+  resolved "https://registry.yarnpkg.com/mimic-response/-/mimic-response-3.1.0.tgz#2d1d59af9c1b129815accc2c46a022a5ce1fa3c9"
+  integrity sha512-z0yWI+4FDrrweS8Zmt4Ej5HdJmky15+L2e6Wgn3+iK5fWzb6T3fhNFq2+MeTRb064c6Wr4N/wv0DzQTjNzHNGQ==
 
-nanoid@^3.1.28:
+minimatch@^3.0.4:
+  version "3.0.4"
+  resolved "https://registry.yarnpkg.com/minimatch/-/minimatch-3.0.4.tgz#5166e286457f03306064be5497e8dbb0c3d32083"
+  integrity sha512-yJHVQEhyqPLUTgt9B83PXu6W3rx4MvvHvSUvToogpwoGDOUQ+yDrR0HRot+yOCdCO7u4hX3pWft6kWBBcqh0UA==
+  dependencies:
+    brace-expansion "^1.1.7"
+
+ms@2.1.2:
+  version "2.1.2"
+  resolved "https://registry.yarnpkg.com/ms/-/ms-2.1.2.tgz#d09d1f357b443f493382a8eb3ccd183872ae6009"
+  integrity sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==
+
+nanoid@^3.2.0:
   version "3.2.0"
   resolved "https://registry.yarnpkg.com/nanoid/-/nanoid-3.2.0.tgz#62667522da6673971cca916a6d3eff3f415ff80c"
   integrity sha512-fmsZYa9lpn69Ad5eDn7FMcnnSR+8R34W9qJEijxYhTbfOWzr22n1QxCMzXLK+ODyW2973V3Fux959iQoUxzUIA==
 
-nice-try@^1.0.4:
-  version "1.0.5"
-  resolved "https://registry.yarnpkg.com/nice-try/-/nice-try-1.0.5.tgz#a3378a7696ce7d223e88fc9b764bd7ef1089e366"
-  integrity sha512-1nh45deeb5olNY7eX82BkPO7SSxR5SSYJiPTrTdFUVYwAl8CKMA5N9PjTYkHiRjisVcxcQ1HXdLhx2qxxJzLNQ==
+node-releases@^2.0.1:
+  version "2.0.1"
+  resolved "https://registry.yarnpkg.com/node-releases/-/node-releases-2.0.1.tgz#3d1d395f204f1f2f29a54358b9fb678765ad2fc5"
+  integrity sha512-CqyzN6z7Q6aMeF/ktcMVTzhAHCEpf8SOarwpzpf8pNBY2k5/oM34UHldUwp8VKI7uxct2HxSRdJjBaZeESzcxA==
 
-node-releases@^1.1.77:
-  version "1.1.77"
-  resolved "https://registry.yarnpkg.com/node-releases/-/node-releases-1.1.77.tgz#50b0cfede855dd374e7585bf228ff34e57c1c32e"
-  integrity sha512-rB1DUFUNAN4Gn9keO2K1efO35IDK7yKHCdCaIMvFO7yUYmmZYeDjnGKle26G4rwj+LKRQpjyUUvMkPglwGCYNQ==
+normalize-package-data@^3.0.2:
+  version "3.0.3"
+  resolved "https://registry.yarnpkg.com/normalize-package-data/-/normalize-package-data-3.0.3.tgz#dbcc3e2da59509a0983422884cd172eefdfa525e"
+  integrity sha512-p2W1sgqij3zMMyRC067Dg16bfzVH+w7hyegmpIvZ4JNjqtGOVAIvLmjBx3yP7YTe9vKJgkoNOPjwQGogDoMXFA==
+  dependencies:
+    hosted-git-info "^4.0.1"
+    is-core-module "^2.5.0"
+    semver "^7.3.4"
+    validate-npm-package-license "^3.0.1"
 
 normalize-path@^3.0.0, normalize-path@~3.0.0:
   version "3.0.0"
@@ -957,82 +964,68 @@ normalize-range@^0.1.2:
   resolved "https://registry.yarnpkg.com/normalize-range/-/normalize-range-0.1.2.tgz#2d10c06bdfd312ea9777695a4d28439456b75942"
   integrity sha1-LRDAa9/TEuqXd2laTShDlFa3WUI=
 
-normalize-url@2.0.1:
-  version "2.0.1"
-  resolved "https://registry.yarnpkg.com/normalize-url/-/normalize-url-2.0.1.tgz#835a9da1551fa26f70e92329069a23aa6574d7e6"
-  integrity sha512-D6MUW4K/VzoJ4rJ01JFKxDrtY1v9wrgzCX5f2qj/lzH1m/lW6MhUZFKerVsnyjOhOsYzI9Kqqak+10l4LvLpMw==
-  dependencies:
-    prepend-http "^2.0.0"
-    query-string "^5.0.1"
-    sort-keys "^2.0.0"
+normalize-url@^6.0.1:
+  version "6.1.0"
+  resolved "https://registry.yarnpkg.com/normalize-url/-/normalize-url-6.1.0.tgz#40d0885b535deffe3f3147bec877d05fe4c5668a"
+  integrity sha512-DlL+XwOy3NxAQ8xuC0okPgK46iuVNAK01YN7RueYBqqFeGsBjV9XmCAzAdgt+667bCl5kPh9EqKKDwnaPG1I7A==
 
-npm-conf@^1.1.0:
-  version "1.1.3"
-  resolved "https://registry.yarnpkg.com/npm-conf/-/npm-conf-1.1.3.tgz#256cc47bd0e218c259c4e9550bf413bc2192aff9"
-  integrity sha512-Yic4bZHJOt9RCFbRP3GgpqhScOY4HH3V2P8yBj6CeYq118Qr+BLXqT2JvpJ00mryLESpgOxf5XlFv4ZjXxLScw==
-  dependencies:
-    config-chain "^1.1.11"
-    pify "^3.0.0"
-
-npm-run-path@^2.0.0:
-  version "2.0.2"
-  resolved "https://registry.yarnpkg.com/npm-run-path/-/npm-run-path-2.0.2.tgz#35a9232dfa35d7067b4cb2ddf2357b1871536c5f"
-  integrity sha1-NakjLfo11wZ7TLLd8jV7GHFTbF8=
-  dependencies:
-    path-key "^2.0.0"
-
-object-assign@^4.0.1, object-assign@^4.1.0:
+object-assign@^4.0.1:
   version "4.1.1"
   resolved "https://registry.yarnpkg.com/object-assign/-/object-assign-4.1.1.tgz#2109adc7965887cfc05cbbd442cac8bfbb360863"
   integrity sha1-IQmtx5ZYh8/AXLvUQsrIv7s2CGM=
 
-once@^1.3.1, once@^1.4.0:
+once@^1.3.0, once@^1.3.1, once@^1.4.0:
   version "1.4.0"
   resolved "https://registry.yarnpkg.com/once/-/once-1.4.0.tgz#583b1aa775961d4b113ac17d9c50baef9dd76bd1"
   integrity sha1-WDsap3WWHUsROsF9nFC6753Xa9E=
   dependencies:
     wrappy "1"
 
-os-filter-obj@^2.0.0:
-  version "2.0.0"
-  resolved "https://registry.yarnpkg.com/os-filter-obj/-/os-filter-obj-2.0.0.tgz#1c0b62d5f3a2442749a2d139e6dddee6e81d8d16"
-  integrity sha512-uksVLsqG3pVdzzPvmAHpBK0wKxYItuzZr7SziusRPoz67tGV8rL1szZ6IdeUrbqLjGDwApBtN29eEE3IqGHOjg==
+p-cancelable@^2.0.0:
+  version "2.1.1"
+  resolved "https://registry.yarnpkg.com/p-cancelable/-/p-cancelable-2.1.1.tgz#aab7fbd416582fa32a3db49859c122487c5ed2cf"
+  integrity sha512-BZOr3nRQHOntUjTrH8+Lh54smKHoHyur8We1V8DSMVrl5A2malOOwuJRnKRDjSnkoeBh4at6BwEnb5I7Jl31wg==
+
+p-limit@^4.0.0:
+  version "4.0.0"
+  resolved "https://registry.yarnpkg.com/p-limit/-/p-limit-4.0.0.tgz#914af6544ed32bfa54670b061cafcbd04984b644"
+  integrity sha512-5b0R4txpzjPWVw/cXXUResoD4hb6U/x9BH08L7nw+GN1sezDzPdxeRvpc9c433fZhBan/wusjbCsqwqm4EIBIQ==
   dependencies:
-    arch "^2.1.0"
+    yocto-queue "^1.0.0"
 
-p-cancelable@^0.4.0:
-  version "0.4.1"
-  resolved "https://registry.yarnpkg.com/p-cancelable/-/p-cancelable-0.4.1.tgz#35f363d67d52081c8d9585e37bcceb7e0bbcb2a0"
-  integrity sha512-HNa1A8LvB1kie7cERyy21VNeHb2CWJJYqyyC2o3klWFfMGlFmWv2Z7sFgZH8ZiaYL95ydToKTFVXgMV/Os0bBQ==
-
-p-event@^2.1.0:
-  version "2.3.1"
-  resolved "https://registry.yarnpkg.com/p-event/-/p-event-2.3.1.tgz#596279ef169ab2c3e0cae88c1cfbb08079993ef6"
-  integrity sha512-NQCqOFhbpVTMX4qMe8PF8lbGtzZ+LCiN7pcNrb/413Na7+TRoe1xkKUzuWa/YEJdGQ0FvKtj35EEbDoVPO2kbA==
+p-locate@^6.0.0:
+  version "6.0.0"
+  resolved "https://registry.yarnpkg.com/p-locate/-/p-locate-6.0.0.tgz#3da9a49d4934b901089dca3302fa65dc5a05c04f"
+  integrity sha512-wPrq66Llhl7/4AGC6I+cqxT07LhXvWL08LNXz1fENOw0Ap4sRZZ/gZpTTJ5jpurzzzfS2W/Ge9BY3LgLjCShcw==
   dependencies:
-    p-timeout "^2.0.1"
+    p-limit "^4.0.0"
 
-p-finally@^1.0.0:
-  version "1.0.0"
-  resolved "https://registry.yarnpkg.com/p-finally/-/p-finally-1.0.0.tgz#3fbcfb15b899a44123b34b6dcc18b724336a2cae"
-  integrity sha1-P7z7FbiZpEEjs0ttzBi3JDNqLK4=
-
-p-is-promise@^1.1.0:
-  version "1.1.0"
-  resolved "https://registry.yarnpkg.com/p-is-promise/-/p-is-promise-1.1.0.tgz#9c9456989e9f6588017b0434d56097675c3da05e"
-  integrity sha1-nJRWmJ6fZYgBewQ01WCXZ1w9oF4=
-
-p-timeout@^2.0.1:
-  version "2.0.1"
-  resolved "https://registry.yarnpkg.com/p-timeout/-/p-timeout-2.0.1.tgz#d8dd1979595d2dc0139e1fe46b8b646cb3cdf038"
-  integrity sha512-88em58dDVB/KzPEx1X0N3LwFfYZPyDc4B6eF38M1rk9VTZMbxXXgjugz8mmwpS9Ox4BDZ+t6t3QP5+/gazweIA==
+p-map@^4.0.0:
+  version "4.0.0"
+  resolved "https://registry.yarnpkg.com/p-map/-/p-map-4.0.0.tgz#bb2f95a5eda2ec168ec9274e06a747c3e2904d2b"
+  integrity sha512-/bjOqmgETBYB5BoEeGVea8dmvHb2m9GLy1E9W43yeyfP6QQCZGFNa+XRceJEuDB6zqr+gKpIAmlLebMpykw/MQ==
   dependencies:
-    p-finally "^1.0.0"
+    aggregate-error "^3.0.0"
 
-path-key@^2.0.0, path-key@^2.0.1:
-  version "2.0.1"
-  resolved "https://registry.yarnpkg.com/path-key/-/path-key-2.0.1.tgz#411cadb574c5a140d3a4b1910d40d80cc9f40b40"
-  integrity sha1-QRyttXTFoUDTpLGRDUDYDMn0C0A=
+parse-json@^5.2.0:
+  version "5.2.0"
+  resolved "https://registry.yarnpkg.com/parse-json/-/parse-json-5.2.0.tgz#c76fc66dee54231c962b22bcc8a72cf2f99753cd"
+  integrity sha512-ayCKvm/phCGxOkYRSCM82iDwct8/EonSEgCSxWxD7ve6jHggsFl4fZVQBPRNgQoKiuV/odhFrGzQXZwbifC8Rg==
+  dependencies:
+    "@babel/code-frame" "^7.0.0"
+    error-ex "^1.3.1"
+    json-parse-even-better-errors "^2.3.0"
+    lines-and-columns "^1.1.6"
+
+path-exists@^5.0.0:
+  version "5.0.0"
+  resolved "https://registry.yarnpkg.com/path-exists/-/path-exists-5.0.0.tgz#a6aad9489200b21fab31e49cf09277e5116fb9e7"
+  integrity sha512-RjhtfwJOxzcFmNOi6ltcbcu4Iu+FL3zEj83dk4kAS+fVpTxXLO1b38RvJgT/0QwvV/L3aY9TAnyv0EOqW4GoMQ==
+
+path-is-absolute@^1.0.0:
+  version "1.0.1"
+  resolved "https://registry.yarnpkg.com/path-is-absolute/-/path-is-absolute-1.0.1.tgz#174b9268735534ffbc7ace6bf53a5a9e1b5c5f5f"
+  integrity sha1-F0uSaHNVNP+8es5r9TpanhtcX18=
 
 path-type@^4.0.0:
   version "4.0.0"
@@ -1044,17 +1037,17 @@ pend@~1.2.0:
   resolved "https://registry.yarnpkg.com/pend/-/pend-1.2.0.tgz#7a57eb550a6783f9115331fcf4663d5c8e007a50"
   integrity sha1-elfrVQpng/kRUzH89GY9XI4AelA=
 
-picocolors@^0.2.1:
-  version "0.2.1"
-  resolved "https://registry.yarnpkg.com/picocolors/-/picocolors-0.2.1.tgz#570670f793646851d1ba135996962abad587859f"
-  integrity sha512-cMlDqaLEqfSaW8Z7N5Jw+lyIW869EzT73/F5lhtY9cLGoVxSXznfgfXMO0Z5K0o0Q2TkTXq+0KFsdnSe3jDViA==
+picocolors@^1.0.0:
+  version "1.0.0"
+  resolved "https://registry.yarnpkg.com/picocolors/-/picocolors-1.0.0.tgz#cb5bdc74ff3f51892236eaf79d68bc44564ab81c"
+  integrity sha512-1fygroTLlHu66zi26VoTDv8yRgm0Fccecssto+MhsZ0D/DGW2sm8E8AjW7NU5VVTRt5GxbeZ5qBuJr+HyLYkjQ==
 
 picomatch@^2.0.4, picomatch@^2.2.1, picomatch@^2.2.3:
-  version "2.3.0"
-  resolved "https://registry.yarnpkg.com/picomatch/-/picomatch-2.3.0.tgz#f1f061de8f6a4bf022892e2d128234fb98302972"
-  integrity sha512-lY1Q/PiJGC2zOv/z391WOTD+Z02bCgsFfvxoXXf6h7kv9o+WmsmzYqrAwY63sNgOxE4xEdq0WyUnXfKeBrSvYw==
+  version "2.3.1"
+  resolved "https://registry.yarnpkg.com/picomatch/-/picomatch-2.3.1.tgz#3ba3833733646d9d3e4995946c1365a67fb07a42"
+  integrity sha512-JU3teHTNjmE2VCGFzuY8EXzCDVwEqB2a8fsIvwaStHhAWJEeVd1o1QD80CU6+ZdEXXSLbSsuLwJjkCBWqRQUVA==
 
-pify@^2.2.0, pify@^2.3.0:
+pify@^2.3.0:
   version "2.3.0"
   resolved "https://registry.yarnpkg.com/pify/-/pify-2.3.0.tgz#ed141a6ac043a849ea588498e7dca8b15330e90c"
   integrity sha1-7RQaasBDqEnqWISY59yosVMw6Qw=
@@ -1064,11 +1057,6 @@ pify@^3.0.0:
   resolved "https://registry.yarnpkg.com/pify/-/pify-3.0.0.tgz#e5a4acd2c101fdf3d9a4d07f0dbc4db49dd28176"
   integrity sha1-5aSs0sEB/fPZpNB/DbxNtJ3SgXY=
 
-pify@^4.0.1:
-  version "4.0.1"
-  resolved "https://registry.yarnpkg.com/pify/-/pify-4.0.1.tgz#4b2cd25c50d598735c50292224fd8c6df41e3231"
-  integrity sha512-uB80kBFb/tfd68bVleG9T5GGsGPjJrLAUpR5PZIrhBnIaRTQRjqdJSsIKkOP6OAIFbj7GOrcudc5pNjZ+geV2g==
-
 pinkie-promise@^2.0.0:
   version "2.0.1"
   resolved "https://registry.yarnpkg.com/pinkie-promise/-/pinkie-promise-2.0.1.tgz#2135d6dfa7a358c069ac9b178776288228450ffa"
@@ -1081,63 +1069,53 @@ pinkie@^2.0.0:
   resolved "https://registry.yarnpkg.com/pinkie/-/pinkie-2.0.4.tgz#72556b80cfa0d48a974e80e77248e80ed4f7f870"
   integrity sha1-clVrgM+g1IqXToDnckjoDtT3+HA=
 
-postcss-cli@^8.3.1:
-  version "8.3.1"
-  resolved "https://registry.yarnpkg.com/postcss-cli/-/postcss-cli-8.3.1.tgz#865dad08300ac59ae9cecb7066780aa81c767a77"
-  integrity sha512-leHXsQRq89S3JC9zw/tKyiVV2jAhnfQe0J8VI4eQQbUjwIe0XxVqLrR+7UsahF1s9wi4GlqP6SJ8ydf44cgF2Q==
+postcss-cli@^9.1.0:
+  version "9.1.0"
+  resolved "https://registry.yarnpkg.com/postcss-cli/-/postcss-cli-9.1.0.tgz#1a86404cbe848e370127b4bdf5cd2be83bc45ebe"
+  integrity sha512-zvDN2ADbWfza42sAnj+O2uUWyL0eRL1V+6giM2vi4SqTR3gTYy8XzcpfwccayF2szcUif0HMmXiEaDv9iEhcpw==
   dependencies:
-    chalk "^4.0.0"
     chokidar "^3.3.0"
-    dependency-graph "^0.9.0"
-    fs-extra "^9.0.0"
-    get-stdin "^8.0.0"
-    globby "^11.0.0"
+    dependency-graph "^0.11.0"
+    fs-extra "^10.0.0"
+    get-stdin "^9.0.0"
+    globby "^12.0.0"
+    picocolors "^1.0.0"
     postcss-load-config "^3.0.0"
     postcss-reporter "^7.0.0"
     pretty-hrtime "^1.0.3"
     read-cache "^1.0.0"
-    slash "^3.0.0"
-    yargs "^16.0.0"
+    slash "^4.0.0"
+    yargs "^17.0.0"
 
 postcss-load-config@^3.0.0:
-  version "3.1.0"
-  resolved "https://registry.yarnpkg.com/postcss-load-config/-/postcss-load-config-3.1.0.tgz#d39c47091c4aec37f50272373a6a648ef5e97829"
-  integrity sha512-ipM8Ds01ZUophjDTQYSVP70slFSYg3T0/zyfII5vzhN6V57YSxMgG5syXuwi5VtS8wSf3iL30v0uBdoIVx4Q0g==
+  version "3.1.1"
+  resolved "https://registry.yarnpkg.com/postcss-load-config/-/postcss-load-config-3.1.1.tgz#2f53a17f2f543d9e63864460af42efdac0d41f87"
+  integrity sha512-c/9XYboIbSEUZpiD1UQD0IKiUe8n9WHYV7YFe7X7J+ZwCsEKkUJSFWjS9hBU1RR9THR7jMXst8sxiqP0jjo2mg==
   dependencies:
-    import-cwd "^3.0.0"
-    lilconfig "^2.0.3"
+    lilconfig "^2.0.4"
     yaml "^1.10.2"
 
 postcss-reporter@^7.0.0:
-  version "7.0.3"
-  resolved "https://registry.yarnpkg.com/postcss-reporter/-/postcss-reporter-7.0.3.tgz#c37f81c9a30ab773df72789ea7ceeb3beb442b59"
-  integrity sha512-WoYHwtStmiR74UQDO3vZMbkhOBXSXyteWnhMCVbAK6KRRKLTS0EnTZxOxvbUEnQiMZ+3xRG04x41HhHnLBtQfA==
+  version "7.0.5"
+  resolved "https://registry.yarnpkg.com/postcss-reporter/-/postcss-reporter-7.0.5.tgz#e55bd0fdf8d17e4f25fb55e9143fcd79349a2ceb"
+  integrity sha512-glWg7VZBilooZGOFPhN9msJ3FQs19Hie7l5a/eE6WglzYqVeH3ong3ShFcp9kDWJT1g2Y/wd59cocf9XxBtkWA==
   dependencies:
-    lodash.difference "^4.5.0"
-    lodash.forown "^4.4.0"
-    lodash.get "^4.4.2"
-    lodash.groupby "^4.6.0"
-    lodash.sortby "^4.7.0"
-    nanocolors "^0.2.6"
+    picocolors "^1.0.0"
+    thenby "^1.3.4"
 
-postcss-value-parser@^4.1.0:
-  version "4.1.0"
-  resolved "https://registry.yarnpkg.com/postcss-value-parser/-/postcss-value-parser-4.1.0.tgz#443f6a20ced6481a2bda4fa8532a6e55d789a2cb"
-  integrity sha512-97DXOFbQJhk71ne5/Mt6cOu6yxsSfM0QGQyl0L25Gca4yGWEGJaig7l7gbCX623VqTBNGLRLaVUCnNkcedlRSQ==
+postcss-value-parser@^4.2.0:
+  version "4.2.0"
+  resolved "https://registry.yarnpkg.com/postcss-value-parser/-/postcss-value-parser-4.2.0.tgz#723c09920836ba6d3e5af019f92bc0971c02e514"
+  integrity sha512-1NNCs6uurfkVbeXG4S8JFT9t19m45ICnif8zWLd5oPSZ50QnwMfK+H3jv408d4jw/7Bttv5axS5IiHoLaVNHeQ==
 
 postcss@^8.2.13:
-  version "8.3.9"
-  resolved "https://registry.yarnpkg.com/postcss/-/postcss-8.3.9.tgz#98754caa06c4ee9eb59cc48bd073bb6bd3437c31"
-  integrity sha512-f/ZFyAKh9Dnqytx5X62jgjhhzttjZS7hMsohcI7HEI5tjELX/HxCy3EFhsRxyzGvrzFF+82XPvCS8T9TFleVJw==
+  version "8.4.6"
+  resolved "https://registry.yarnpkg.com/postcss/-/postcss-8.4.6.tgz#c5ff3c3c457a23864f32cb45ac9b741498a09ae1"
+  integrity sha512-OovjwIzs9Te46vlEx7+uXB0PLijpwjXGKXjVGGPIGubGpq7uh5Xgf6D6FiJ/SzJMBosHDp6a2hiXOS97iBXcaA==
   dependencies:
-    nanoid "^3.1.28"
-    picocolors "^0.2.1"
-    source-map-js "^0.6.2"
-
-prepend-http@^2.0.0:
-  version "2.0.0"
-  resolved "https://registry.yarnpkg.com/prepend-http/-/prepend-http-2.0.0.tgz#e92434bfa5ea8c19f41cdfd401d741a3c819d897"
-  integrity sha1-6SQ0v6XqjBn0HN/UAddBo8gZ2Jc=
+    nanoid "^3.2.0"
+    picocolors "^1.0.0"
+    source-map-js "^1.0.2"
 
 pretty-hrtime@^1.0.3:
   version "1.0.3"
@@ -1149,16 +1127,6 @@ process-nextick-args@~2.0.0:
   resolved "https://registry.yarnpkg.com/process-nextick-args/-/process-nextick-args-2.0.1.tgz#7820d9b16120cc55ca9ae7792680ae7dba6d7fe2"
   integrity sha512-3ouUOpQhtgrbOa17J7+uxOTpITYWaGP7/AhoR3+A+/1e9skrzelGi/dXzEYyvbxubEF6Wn2ypscTKiKJFFn1ag==
 
-proto-list@~1.2.1:
-  version "1.2.4"
-  resolved "https://registry.yarnpkg.com/proto-list/-/proto-list-1.2.4.tgz#212d5bfe1318306a420f6402b8e26ff39647a849"
-  integrity sha1-IS1b/hMYMGpCD2QCuOJv85ZHqEk=
-
-pseudomap@^1.0.2:
-  version "1.0.2"
-  resolved "https://registry.yarnpkg.com/pseudomap/-/pseudomap-1.0.2.tgz#f052a28da70e618917ef0a8ac34c1ae5a68286b3"
-  integrity sha1-8FKijacOYYkX7wqKw0wa5aaChrM=
-
 pump@^3.0.0:
   version "3.0.0"
   resolved "https://registry.yarnpkg.com/pump/-/pump-3.0.0.tgz#b4a2116815bde2f4e1ea602354e8c75565107a64"
@@ -1167,20 +1135,16 @@ pump@^3.0.0:
     end-of-stream "^1.1.0"
     once "^1.3.1"
 
-query-string@^5.0.1:
-  version "5.1.1"
-  resolved "https://registry.yarnpkg.com/query-string/-/query-string-5.1.1.tgz#a78c012b71c17e05f2e3fa2319dd330682efb3cb"
-  integrity sha512-gjWOsm2SoGlgLEdAGt7a6slVOk9mGiXmPFMqrEhLQ68rhQuBnpfs3+EmlvqKyxnCo9/PPlF+9MtY02S1aFg+Jw==
-  dependencies:
-    decode-uri-component "^0.2.0"
-    object-assign "^4.1.0"
-    strict-uri-encode "^1.0.0"
-
 queue-microtask@^1.2.2:
   version "1.2.3"
   resolved "https://registry.yarnpkg.com/queue-microtask/-/queue-microtask-1.2.3.tgz#4929228bbc724dfac43e0efb058caf7b6cfb6243"
   integrity sha512-NuaNSa6flKT5JaSYQzJok04JzTL1CA6aGhv5rfLW3PgqA+M2ChpZQnAC8h8i4ZFkBS8X5RqkDBHA7r4hej3K9A==
 
+quick-lru@^5.1.1:
+  version "5.1.1"
+  resolved "https://registry.yarnpkg.com/quick-lru/-/quick-lru-5.1.1.tgz#366493e6b3e42a3a6885e2e99d18f80fb7a8c932"
+  integrity sha512-WuyALRjWPDGtt/wzJiadO5AXY+8hZ80hVpe6MyivgraREW751X3SbhRvG3eLKOYN+8VEvqLcf3wdnt44Z4S4SA==
+
 read-cache@^1.0.0:
   version "1.0.0"
   resolved "https://registry.yarnpkg.com/read-cache/-/read-cache-1.0.0.tgz#e664ef31161166c9751cdbe8dbcf86b5fb58f774"
@@ -1188,7 +1152,26 @@ read-cache@^1.0.0:
   dependencies:
     pify "^2.3.0"
 
-readable-stream@^2.0.0, readable-stream@^2.3.0, readable-stream@^2.3.5:
+read-pkg-up@^9.0.0:
+  version "9.0.0"
+  resolved "https://registry.yarnpkg.com/read-pkg-up/-/read-pkg-up-9.0.0.tgz#2f03ba3e1430c56f8f0a4da73274c6d26c283b45"
+  integrity sha512-7dNMZVru/9QQYnYYjboVqpaqT/e24MuhovJWjZHFBmUnCKVz5ZVFNLbd+fJCUsH7uIgkYbX9yQJvab2nc6P7Nw==
+  dependencies:
+    find-up "^6.2.0"
+    read-pkg "^7.0.0"
+    type-fest "^2.5.0"
+
+read-pkg@^7.0.0:
+  version "7.0.0"
+  resolved "https://registry.yarnpkg.com/read-pkg/-/read-pkg-7.0.0.tgz#7009094a9cd58c7efc325d31f1f6cfce1928fa00"
+  integrity sha512-oG2cKegOo2gjy/hrAM+KFHD9IqKdQvWcpWBBxuHbaucziM9PY45EuF6YbenLF7tL9ekXgB6Lfruo9hwdHQZUrA==
+  dependencies:
+    "@types/normalize-package-data" "^2.4.1"
+    normalize-package-data "^3.0.2"
+    parse-json "^5.2.0"
+    type-fest "^2.0.0"
+
+readable-stream@^2.3.0, readable-stream@^2.3.5:
   version "2.3.7"
   resolved "https://registry.yarnpkg.com/readable-stream/-/readable-stream-2.3.7.tgz#1eca1cf711aef814c04f62252a36a62f6cb23b57"
   integrity sha512-Ebho8K4jIbHAxnuxi7o42OrZgF/ZTNcsZj6nRKyUmkhLFq8CHItp/fy6hQZuZmP/n3yZ9VBUbp4zz/mX8hmYPw==
@@ -1213,23 +1196,30 @@ require-directory@^2.1.1:
   resolved "https://registry.yarnpkg.com/require-directory/-/require-directory-2.1.1.tgz#8c64ad5fd30dab1c976e2344ffe7f792a6a6df42"
   integrity sha1-jGStX9MNqxyXbiNE/+f3kqam30I=
 
-resolve-from@^5.0.0:
-  version "5.0.0"
-  resolved "https://registry.yarnpkg.com/resolve-from/-/resolve-from-5.0.0.tgz#c35225843df8f776df21c57557bc087e9dfdfc69"
-  integrity sha512-qYg9KP24dD5qka9J47d0aVky0N+b4fTU89LN9iDnjB5waksiC49rvMB0PrUJQGoTmH50XPiqOvAjDfaijGxYZw==
+resolve-alpn@^1.0.0:
+  version "1.2.1"
+  resolved "https://registry.yarnpkg.com/resolve-alpn/-/resolve-alpn-1.2.1.tgz#b7adbdac3546aaaec20b45e7d8265927072726f9"
+  integrity sha512-0a1F4l73/ZFZOakJnQ3FvkJ2+gSTQWz/r2KE5OdDY0TxPm5h4GkqkWWfM47T7HsbnOtcJVEF4epCVy6u7Q3K+g==
 
-responselike@1.0.2:
-  version "1.0.2"
-  resolved "https://registry.yarnpkg.com/responselike/-/responselike-1.0.2.tgz#918720ef3b631c5642be068f15ade5a46f4ba1e7"
-  integrity sha1-kYcg7ztjHFZCvgaPFa3lpG9Loec=
+responselike@^2.0.0:
+  version "2.0.0"
+  resolved "https://registry.yarnpkg.com/responselike/-/responselike-2.0.0.tgz#26391bcc3174f750f9a79eacc40a12a5c42d7723"
+  integrity sha512-xH48u3FTB9VsZw7R+vvgaKeLKzT6jOogbQhEe/jewwnZgzPcnyWui2Av6JpoYZF/91uueC+lqhWqeURw5/qhCw==
   dependencies:
-    lowercase-keys "^1.0.0"
+    lowercase-keys "^2.0.0"
 
 reusify@^1.0.4:
   version "1.0.4"
   resolved "https://registry.yarnpkg.com/reusify/-/reusify-1.0.4.tgz#90da382b1e126efc02146e90845a88db12925d76"
   integrity sha512-U9nH88a3fc/ekCF1l0/UP1IosiuIjyTh7hBvXVMHYgVcfGvt897Xguj2UOLDeI5BG2m7/uwyaLVT6fbtCwTyzw==
 
+rimraf@^3.0.2:
+  version "3.0.2"
+  resolved "https://registry.yarnpkg.com/rimraf/-/rimraf-3.0.2.tgz#f1a5402ba6220ad52cc1282bac1ae3aa49fd061a"
+  integrity sha512-JZkJMZkAGFFPP2YqXZXPbMlMBgsxzE8ILs4lMIX/2o0L9UBw9O/Y3o6wFw/i9YLapcUJWwqbi3kdxIPdC62TIA==
+  dependencies:
+    glob "^7.1.3"
+
 run-parallel@^1.1.9:
   version "1.2.0"
   resolved "https://registry.yarnpkg.com/run-parallel/-/run-parallel-1.2.0.tgz#66d1368da7bdf921eb9d95bd1a9229e7f21a43ee"
@@ -1237,16 +1227,16 @@ run-parallel@^1.1.9:
   dependencies:
     queue-microtask "^1.2.2"
 
-safe-buffer@5.1.2, safe-buffer@~5.1.0, safe-buffer@~5.1.1:
-  version "5.1.2"
-  resolved "https://registry.yarnpkg.com/safe-buffer/-/safe-buffer-5.1.2.tgz#991ec69d296e0313747d59bdfd2b745c35f8828d"
-  integrity sha512-Gd2UZBJDkXlY7GbJxfsE8/nvKkUEU1G38c1siN6QP6a9PT9MmHB8GnpscSmMJSoF8LOIrt8ud/wPtojys4G6+g==
-
-safe-buffer@^5.0.1, safe-buffer@^5.1.1:
+safe-buffer@^5.1.1:
   version "5.2.1"
   resolved "https://registry.yarnpkg.com/safe-buffer/-/safe-buffer-5.2.1.tgz#1eaf9fa9bdb1fdd4ec75f58f9cdb4e6b7827eec6"
   integrity sha512-rp3So07KcdmmKbGvgaNxQSJr7bGVSVk5S9Eq1F+ppbRo70+YeaDxkw5Dd8NPN+GD6bjnYm2VuPuCXmpuYvmCXQ==
 
+safe-buffer@~5.1.0, safe-buffer@~5.1.1:
+  version "5.1.2"
+  resolved "https://registry.yarnpkg.com/safe-buffer/-/safe-buffer-5.1.2.tgz#991ec69d296e0313747d59bdfd2b745c35f8828d"
+  integrity sha512-Gd2UZBJDkXlY7GbJxfsE8/nvKkUEU1G38c1siN6QP6a9PT9MmHB8GnpscSmMJSoF8LOIrt8ud/wPtojys4G6+g==
+
 seek-bzip@^1.0.5:
   version "1.0.6"
   resolved "https://registry.yarnpkg.com/seek-bzip/-/seek-bzip-1.0.6.tgz#35c4171f55a680916b52a07859ecf3b5857f21c4"
@@ -1254,77 +1244,55 @@ seek-bzip@^1.0.5:
   dependencies:
     commander "^2.8.1"
 
-semver-regex@^2.0.0:
-  version "2.0.0"
-  resolved "https://registry.yarnpkg.com/semver-regex/-/semver-regex-2.0.0.tgz#a93c2c5844539a770233379107b38c7b4ac9d338"
-  integrity sha512-mUdIBBvdn0PLOeP3TEkMH7HHeUP3GjsXCwKarjv/kGmUFOYg1VqEemKhoQpWMu6X2I8kHeuVdGibLGkVK+/5Qw==
-
-semver-truncate@^1.1.2:
-  version "1.1.2"
-  resolved "https://registry.yarnpkg.com/semver-truncate/-/semver-truncate-1.1.2.tgz#57f41de69707a62709a7e0104ba2117109ea47e8"
-  integrity sha1-V/Qd5pcHpicJp+AQS6IRcQnqR+g=
+semver@^7.3.4:
+  version "7.3.5"
+  resolved "https://registry.yarnpkg.com/semver/-/semver-7.3.5.tgz#0b621c879348d8998e4b0e4be94b3f12e6018ef7"
+  integrity sha512-PoeGJYh8HK4BTO/a9Tf6ZG3veo/A7ZVsYrSA6J8ny9nb3B1VrpkuN+z9OE5wfE5p6H4LchYZsegiQgbJD94ZFQ==
   dependencies:
-    semver "^5.3.0"
-
-semver@^5.3.0, semver@^5.5.0, semver@^5.6.0:
-  version "5.7.1"
-  resolved "https://registry.yarnpkg.com/semver/-/semver-5.7.1.tgz#a954f931aeba508d307bbf069eff0c01c96116f7"
-  integrity sha512-sauaDf/PZdVgrLTNYHRtpXa1iRiKcaebiKQ1BJdpQlWH2lCvexQdX55snPFyK7QzpudqbCI0qXFfOasHdyNDGQ==
-
-shebang-command@^1.2.0:
-  version "1.2.0"
-  resolved "https://registry.yarnpkg.com/shebang-command/-/shebang-command-1.2.0.tgz#44aac65b695b03398968c39f363fee5deafdf1ea"
-  integrity sha1-RKrGW2lbAzmJaMOfNj/uXer98eo=
-  dependencies:
-    shebang-regex "^1.0.0"
-
-shebang-regex@^1.0.0:
-  version "1.0.0"
-  resolved "https://registry.yarnpkg.com/shebang-regex/-/shebang-regex-1.0.0.tgz#da42f49740c0b42db2ca9728571cb190c98efea3"
-  integrity sha1-2kL0l0DAtC2yypcoVxyxkMmO/qM=
-
-signal-exit@^3.0.0:
-  version "3.0.5"
-  resolved "https://registry.yarnpkg.com/signal-exit/-/signal-exit-3.0.5.tgz#9e3e8cc0c75a99472b44321033a7702e7738252f"
-  integrity sha512-KWcOiKeQj6ZyXx7zq4YxSMgHRlod4czeBQZrPb8OKcohcqAXShm7E20kEMle9WBt26hFcAf0qLOcp5zmY7kOqQ==
+    lru-cache "^6.0.0"
 
 slash@^3.0.0:
   version "3.0.0"
   resolved "https://registry.yarnpkg.com/slash/-/slash-3.0.0.tgz#6539be870c165adbd5240220dbe361f1bc4d4634"
   integrity sha512-g9Q1haeby36OSStwb4ntCGGGaKsaVSjQ68fBxoQcutl5fS1vuY18H3wSt3jFyFtrkx+Kz0V1G85A4MyAdDMi2Q==
 
-sort-keys-length@^1.0.0:
-  version "1.0.1"
-  resolved "https://registry.yarnpkg.com/sort-keys-length/-/sort-keys-length-1.0.1.tgz#9cb6f4f4e9e48155a6aa0671edd336ff1479a188"
-  integrity sha1-nLb09OnkgVWmqgZx7dM2/xR5oYg=
+slash@^4.0.0:
+  version "4.0.0"
+  resolved "https://registry.yarnpkg.com/slash/-/slash-4.0.0.tgz#2422372176c4c6c5addb5e2ada885af984b396a7"
+  integrity sha512-3dOsAHXXUkQTpOYcoAxLIorMTp4gIQr5IW3iVb7A7lFIp0VHhnynm9izx6TssdrIcVIESAlVjtnO2K8bg+Coew==
+
+source-map-js@^1.0.2:
+  version "1.0.2"
+  resolved "https://registry.yarnpkg.com/source-map-js/-/source-map-js-1.0.2.tgz#adbc361d9c62df380125e7f161f71c826f1e490c"
+  integrity sha512-R0XvVJ9WusLiqTCEiGCmICCMplcCkIwwR11mOSD9CR5u+IXYdiseeEuXCVAjS54zqwkLcPNnmU4OeJ6tUrWhDw==
+
+spdx-correct@^3.0.0:
+  version "3.1.1"
+  resolved "https://registry.yarnpkg.com/spdx-correct/-/spdx-correct-3.1.1.tgz#dece81ac9c1e6713e5f7d1b6f17d468fa53d89a9"
+  integrity sha512-cOYcUWwhCuHCXi49RhFRCyJEK3iPj1Ziz9DpViV3tbZOwXD49QzIN3MpOLJNxh2qwq2lJJZaKMVw9qNi4jTC0w==
   dependencies:
-    sort-keys "^1.0.0"
+    spdx-expression-parse "^3.0.0"
+    spdx-license-ids "^3.0.0"
 
-sort-keys@^1.0.0:
-  version "1.1.2"
-  resolved "https://registry.yarnpkg.com/sort-keys/-/sort-keys-1.1.2.tgz#441b6d4d346798f1b4e49e8920adfba0e543f9ad"
-  integrity sha1-RBttTTRnmPG05J6JIK37oOVD+a0=
+spdx-exceptions@^2.1.0:
+  version "2.3.0"
+  resolved "https://registry.yarnpkg.com/spdx-exceptions/-/spdx-exceptions-2.3.0.tgz#3f28ce1a77a00372683eade4a433183527a2163d"
+  integrity sha512-/tTrYOC7PPI1nUAgx34hUpqXuyJG+DTHJTnIULG4rDygi4xu/tfgmq1e1cIRwRzwZgo4NLySi+ricLkZkw4i5A==
+
+spdx-expression-parse@^3.0.0:
+  version "3.0.1"
+  resolved "https://registry.yarnpkg.com/spdx-expression-parse/-/spdx-expression-parse-3.0.1.tgz#cf70f50482eefdc98e3ce0a6833e4a53ceeba679"
+  integrity sha512-cbqHunsQWnJNE6KhVSMsMeH5H/L9EpymbzqTQ3uLwNCLZ1Q481oWaofqH7nO6V07xlXwY6PhQdQ2IedWx/ZK4Q==
   dependencies:
-    is-plain-obj "^1.0.0"
+    spdx-exceptions "^2.1.0"
+    spdx-license-ids "^3.0.0"
 
-sort-keys@^2.0.0:
-  version "2.0.0"
-  resolved "https://registry.yarnpkg.com/sort-keys/-/sort-keys-2.0.0.tgz#658535584861ec97d730d6cf41822e1f56684128"
-  integrity sha1-ZYU1WEhh7JfXMNbPQYIuH1ZoQSg=
-  dependencies:
-    is-plain-obj "^1.0.0"
+spdx-license-ids@^3.0.0:
+  version "3.0.11"
+  resolved "https://registry.yarnpkg.com/spdx-license-ids/-/spdx-license-ids-3.0.11.tgz#50c0d8c40a14ec1bf449bae69a0ea4685a9d9f95"
+  integrity sha512-Ctl2BrFiM0X3MANYgj3CkygxhRmr9mi6xhejbdO960nF6EDJApTYpn0BQnDKlnNBULKiCN1n3w9EBkHK8ZWg+g==
 
-source-map-js@^0.6.2:
-  version "0.6.2"
-  resolved "https://registry.yarnpkg.com/source-map-js/-/source-map-js-0.6.2.tgz#0bb5de631b41cfbda6cfba8bd05a80efdfd2385e"
-  integrity sha512-/3GptzWzu0+0MBQFrDKzw/DvvMTUORvgY6k6jd/VS6iCR4RDTKWH6v6WPwQoUO8667uQEf9Oe38DxAYWY5F/Ug==
-
-strict-uri-encode@^1.0.0:
-  version "1.1.0"
-  resolved "https://registry.yarnpkg.com/strict-uri-encode/-/strict-uri-encode-1.1.0.tgz#279b225df1d582b1f54e65addd4352e18faa0713"
-  integrity sha1-J5siXfHVgrH1TmWt3UNS4Y+qBxM=
-
-string-width@^4.1.0, string-width@^4.2.0:
+string-width@^4.1.0, string-width@^4.2.0, string-width@^4.2.3:
   version "4.2.3"
   resolved "https://registry.yarnpkg.com/string-width/-/string-width-4.2.3.tgz#269c7117d27b05ad2e536830a8ec895ef9c6d010"
   integrity sha512-wKyQRQpjJ0sIp62ErSZdGsjMJWsap5oRNihHhu6G7JVO/9jIB6UyevL+tXuOqrng8j/cxKTWyWUwvSTriiZz/g==
@@ -1354,24 +1322,12 @@ strip-dirs@^2.0.0:
   dependencies:
     is-natural-number "^4.0.1"
 
-strip-eof@^1.0.0:
-  version "1.0.0"
-  resolved "https://registry.yarnpkg.com/strip-eof/-/strip-eof-1.0.0.tgz#bb43ff5598a6eb05d89b59fcd129c983313606bf"
-  integrity sha1-u0P/VZim6wXYm1n80SnJgzE2Br8=
-
-strip-outer@^1.0.0:
-  version "1.0.1"
-  resolved "https://registry.yarnpkg.com/strip-outer/-/strip-outer-1.0.1.tgz#b2fd2abf6604b9d1e6013057195df836b8a9d631"
-  integrity sha512-k55yxKHwaXnpYGsOzg4Vl8+tDrWylxDEpknGjhTiZB8dFRU5rTo9CAzeycivxV3s+zlTKwrs6WxMxR95n26kwg==
+supports-color@^5.3.0:
+  version "5.5.0"
+  resolved "https://registry.yarnpkg.com/supports-color/-/supports-color-5.5.0.tgz#e2e69a44ac8772f78a1ec0b35b689df6530efc8f"
+  integrity sha512-QjVjwdXIt408MIiAqCX4oUKsgU2EqAGzs2Ppkm4aQYbjm+ZEWEcW4SfFNTr4uMNZma0ey4f5lgLrkB0aX0QMow==
   dependencies:
-    escape-string-regexp "^1.0.2"
-
-supports-color@^7.1.0:
-  version "7.2.0"
-  resolved "https://registry.yarnpkg.com/supports-color/-/supports-color-7.2.0.tgz#1b7dcdcb32b8138801b3e478ba6a51caa89648da"
-  integrity sha512-qpCAvRl9stuOHveKsn7HncJRvv501qIacKzQlO/+Lwxc9+0q2wLyv4Dfvt80/DPn2pqOBsJdDiogXGR9+OvwRw==
-  dependencies:
-    has-flag "^4.0.0"
+    has-flag "^3.0.0"
 
 tar-stream@^1.5.2:
   version "1.6.2"
@@ -1386,16 +1342,32 @@ tar-stream@^1.5.2:
     to-buffer "^1.1.1"
     xtend "^4.0.0"
 
+temp-dir@^2.0.0:
+  version "2.0.0"
+  resolved "https://registry.yarnpkg.com/temp-dir/-/temp-dir-2.0.0.tgz#bde92b05bdfeb1516e804c9c00ad45177f31321e"
+  integrity sha512-aoBAniQmmwtcKp/7BzsH8Cxzv8OL736p7v1ihGb5e9DJ9kTwGWHrQrVB5+lfVDzfGrdRzXch+ig7LHaY1JTOrg==
+
+tempy@^2.0.0:
+  version "2.0.0"
+  resolved "https://registry.yarnpkg.com/tempy/-/tempy-2.0.0.tgz#c434b89486e112151d5e91ef25592c8ee6fec4f6"
+  integrity sha512-m+QReZVhpa0Y56fmfoLFRZN4aDFdd3qVd8a9k3RfyTw/1utVYNg+Ar4BY6l4/TlkhYCCJFfhYWt9uy0127buJg==
+  dependencies:
+    del "^6.0.0"
+    is-stream "^3.0.0"
+    temp-dir "^2.0.0"
+    type-fest "^2.0.0"
+    unique-string "^3.0.0"
+
+thenby@^1.3.4:
+  version "1.3.4"
+  resolved "https://registry.yarnpkg.com/thenby/-/thenby-1.3.4.tgz#81581f6e1bb324c6dedeae9bfc28e59b1a2201cc"
+  integrity sha512-89Gi5raiWA3QZ4b2ePcEwswC3me9JIg+ToSgtE0JWeCynLnLxNr/f9G+xfo9K+Oj4AFdom8YNJjibIARTJmapQ==
+
 through@^2.3.8:
   version "2.3.8"
   resolved "https://registry.yarnpkg.com/through/-/through-2.3.8.tgz#0dd4c9ffaabc357960b1b724115d7e0e86a2e1f5"
   integrity sha1-DdTJ/6q8NXlgsbckEV1+Doai4fU=
 
-timed-out@^4.0.1:
-  version "4.0.1"
-  resolved "https://registry.yarnpkg.com/timed-out/-/timed-out-4.0.1.tgz#f32eacac5a175bea25d7fab565ab3ed8741ef56f"
-  integrity sha1-8y6srFoXW+ol1/q1Zas+2HQe9W8=
-
 to-buffer@^1.1.1:
   version "1.1.1"
   resolved "https://registry.yarnpkg.com/to-buffer/-/to-buffer-1.1.1.tgz#493bd48f62d7c43fcded313a03dcadb2e1213a80"
@@ -1408,19 +1380,15 @@ to-regex-range@^5.0.1:
   dependencies:
     is-number "^7.0.0"
 
-trim-repeated@^1.0.0:
-  version "1.0.0"
-  resolved "https://registry.yarnpkg.com/trim-repeated/-/trim-repeated-1.0.0.tgz#e3646a2ea4e891312bf7eace6cfb05380bc01c21"
-  integrity sha1-42RqLqTokTEr9+rObPsFOAvAHCE=
-  dependencies:
-    escape-string-regexp "^1.0.2"
+type-fest@^1.0.1:
+  version "1.4.0"
+  resolved "https://registry.yarnpkg.com/type-fest/-/type-fest-1.4.0.tgz#e9fb813fe3bf1744ec359d55d1affefa76f14be1"
+  integrity sha512-yGSza74xk0UG8k+pLh5oeoYirvIiWo5t0/o3zHHAO2tRDiZcxWP7fywNlXhqb6/r6sWvwi+RsyQMWhVLe4BVuA==
 
-tunnel-agent@^0.6.0:
-  version "0.6.0"
-  resolved "https://registry.yarnpkg.com/tunnel-agent/-/tunnel-agent-0.6.0.tgz#27a5dea06b36b04a0a9966774b290868f0fc40fd"
-  integrity sha1-J6XeoGs2sEoKmWZ3SykIaPD8QP0=
-  dependencies:
-    safe-buffer "^5.0.1"
+type-fest@^2.0.0, type-fest@^2.5.0:
+  version "2.11.1"
+  resolved "https://registry.yarnpkg.com/type-fest/-/type-fest-2.11.1.tgz#04ddf5c0dbbd403fb8270d98ad1b4857e7ff7b24"
+  integrity sha512-fPcV5KLAqFfmhHobtAUwEpbpfYhVF7wSLVgbG/7mIGe/Pete7ky/bPAPRkzbWdrj0/EkswFAAR2feJCgigkUKg==
 
 unbzip2-stream@^1.0.9:
   version "1.4.3"
@@ -1430,34 +1398,30 @@ unbzip2-stream@^1.0.9:
     buffer "^5.2.1"
     through "^2.3.8"
 
+unique-string@^3.0.0:
+  version "3.0.0"
+  resolved "https://registry.yarnpkg.com/unique-string/-/unique-string-3.0.0.tgz#84a1c377aff5fd7a8bc6b55d8244b2bd90d75b9a"
+  integrity sha512-VGXBUVwxKMBUznyffQweQABPRRW1vHZAbadFZud4pLFAqRGvv/96vafgjWFqzourzr8YonlQiPgH0YCJfawoGQ==
+  dependencies:
+    crypto-random-string "^4.0.0"
+
 universalify@^2.0.0:
   version "2.0.0"
   resolved "https://registry.yarnpkg.com/universalify/-/universalify-2.0.0.tgz#75a4984efedc4b08975c5aeb73f530d02df25717"
   integrity sha512-hAZsKq7Yy11Zu1DE0OzWjw7nnLZmJZYTDZZyEFHZdUhV8FkH5MCfoU1XMaxXovpyW5nq5scPqq0ZDP9Zyl04oQ==
 
-url-parse-lax@^3.0.0:
-  version "3.0.0"
-  resolved "https://registry.yarnpkg.com/url-parse-lax/-/url-parse-lax-3.0.0.tgz#16b5cafc07dbe3676c1b1999177823d6503acb0c"
-  integrity sha1-FrXK/Afb42dsGxmZF3gj1lA6yww=
-  dependencies:
-    prepend-http "^2.0.0"
-
-url-to-options@^1.0.1:
-  version "1.0.1"
-  resolved "https://registry.yarnpkg.com/url-to-options/-/url-to-options-1.0.1.tgz#1505a03a289a48cbd7a434efbaeec5055f5633a9"
-  integrity sha1-FQWgOiiaSMvXpDTvuu7FBV9WM6k=
-
 util-deprecate@~1.0.1:
   version "1.0.2"
   resolved "https://registry.yarnpkg.com/util-deprecate/-/util-deprecate-1.0.2.tgz#450d4dc9fa70de732762fbd2d4a28981419a0ccf"
   integrity sha1-RQ1Nyfpw3nMnYvvS1KKJgUGaDM8=
 
-which@^1.2.9:
-  version "1.3.1"
-  resolved "https://registry.yarnpkg.com/which/-/which-1.3.1.tgz#a45043d54f5805316da8d62f9f50918d3da70b0a"
-  integrity sha512-HxJdYWq1MTIQbJ3nw0cqssHoTNU267KlrDuGZ1WYlxDStUtKUhOaJmh112/TZmHxxUfuJqPXSOm7tDyas0OSIQ==
+validate-npm-package-license@^3.0.1:
+  version "3.0.4"
+  resolved "https://registry.yarnpkg.com/validate-npm-package-license/-/validate-npm-package-license-3.0.4.tgz#fc91f6b9c7ba15c857f4cb2c5defeec39d4f410a"
+  integrity sha512-DpKm2Ui/xN7/HQKCtpZxoRWBhZ9Z0kqtygG8XCgNQ8ZlDnxuQmWhj566j8fN4Cu3/JmbhsDo7fcAJq4s9h27Ew==
   dependencies:
-    isexe "^2.0.0"
+    spdx-correct "^3.0.0"
+    spdx-expression-parse "^3.0.0"
 
 wrap-ansi@^7.0.0:
   version "7.0.0"
@@ -1483,33 +1447,33 @@ y18n@^5.0.5:
   resolved "https://registry.yarnpkg.com/y18n/-/y18n-5.0.8.tgz#7f4934d0f7ca8c56f95314939ddcd2dd91ce1d55"
   integrity sha512-0pfFzegeDWJHJIAmTLRP2DwHjdF5s7jo9tuztdQxAhINCdvS+3nGINqPd00AphqJR/0LhANUS6/+7SCb98YOfA==
 
-yallist@^2.1.2:
-  version "2.1.2"
-  resolved "https://registry.yarnpkg.com/yallist/-/yallist-2.1.2.tgz#1c11f9218f076089a47dd512f93c6699a6a81d52"
-  integrity sha1-HBH5IY8HYImkfdUS+TxmmaaoHVI=
+yallist@^4.0.0:
+  version "4.0.0"
+  resolved "https://registry.yarnpkg.com/yallist/-/yallist-4.0.0.tgz#9bb92790d9c0effec63be73519e11a35019a3a72"
+  integrity sha512-3wdGidZyq5PB084XLES5TpOSRA3wjXAlIWMhum2kRcv/41Sn2emQ0dycQW4uZXLejwKvg6EsvbdlVL+FYEct7A==
 
 yaml@^1.10.2:
   version "1.10.2"
   resolved "https://registry.yarnpkg.com/yaml/-/yaml-1.10.2.tgz#2301c5ffbf12b467de8da2333a459e29e7920e4b"
   integrity sha512-r3vXyErRCYJ7wg28yvBY5VSoAF8ZvlcW9/BwUzEtUsjvX/DKs24dIkuwjtuprwJJHsbyUbLApepYTR1BN4uHrg==
 
-yargs-parser@^20.2.2:
-  version "20.2.9"
-  resolved "https://registry.yarnpkg.com/yargs-parser/-/yargs-parser-20.2.9.tgz#2eb7dc3b0289718fc295f362753845c41a0c94ee"
-  integrity sha512-y11nGElTIV+CT3Zv9t7VKl+Q3hTQoT9a1Qzezhhl6Rp21gJ/IVTW7Z3y9EWXhuUBC2Shnf+DX0antecpAwSP8w==
+yargs-parser@^21.0.0:
+  version "21.0.0"
+  resolved "https://registry.yarnpkg.com/yargs-parser/-/yargs-parser-21.0.0.tgz#a485d3966be4317426dd56bdb6a30131b281dc55"
+  integrity sha512-z9kApYUOCwoeZ78rfRYYWdiU/iNL6mwwYlkkZfJoyMR1xps+NEBX5X7XmRpxkZHhXJ6+Ey00IwKxBBSW9FIjyA==
 
-yargs@^16.0.0:
-  version "16.2.0"
-  resolved "https://registry.yarnpkg.com/yargs/-/yargs-16.2.0.tgz#1c82bf0f6b6a66eafce7ef30e376f49a12477f66"
-  integrity sha512-D1mvvtDG0L5ft/jGWkLpG1+m0eQxOfaBvTNELraWj22wSVUMWxZUvYgJYcKh6jGGIkJFhH4IZPQhR4TKpc8mBw==
+yargs@^17.0.0:
+  version "17.3.1"
+  resolved "https://registry.yarnpkg.com/yargs/-/yargs-17.3.1.tgz#da56b28f32e2fd45aefb402ed9c26f42be4c07b9"
+  integrity sha512-WUANQeVgjLbNsEmGk20f+nlHgOqzRFpiGWVaBrYGYIGANIIu3lWjoyi0fNlFmJkvfhCZ6BXINe7/W2O2bV4iaA==
   dependencies:
     cliui "^7.0.2"
     escalade "^3.1.1"
     get-caller-file "^2.0.5"
     require-directory "^2.1.1"
-    string-width "^4.2.0"
+    string-width "^4.2.3"
     y18n "^5.0.5"
-    yargs-parser "^20.2.2"
+    yargs-parser "^21.0.0"
 
 yauzl@^2.4.2:
   version "2.10.0"
@@ -1518,3 +1482,8 @@ yauzl@^2.4.2:
   dependencies:
     buffer-crc32 "~0.2.3"
     fd-slicer "~1.1.0"
+
+yocto-queue@^1.0.0:
+  version "1.0.0"
+  resolved "https://registry.yarnpkg.com/yocto-queue/-/yocto-queue-1.0.0.tgz#7f816433fb2cbc511ec8bf7d263c3b58a1a3c251"
+  integrity sha512-9bnSc/HEW2uRy67wc+T8UwauLuPJVn28jb+GtJY16iiKWyvmYJRXVT4UamsAEGQfPohgr2q4Tq0sQbQlxTfi1g==