diff --git a/content/v2.0/account-management/billing.md b/content/v2.0/account-management/billing.md index 1634d4e12..9b63bba0c 100644 --- a/content/v2.0/account-management/billing.md +++ b/content/v2.0/account-management/billing.md @@ -45,7 +45,7 @@ Add your payment method and view billing information in the {{< cloud-name "shor - If you subscribed to an InfluxDB Cloud 2.0 plan through **InfluxData**, complete the following procedures as needed: - - [Add or update your {{< cloud-name >}} payment method](#add-or-update-your-influxdb-cloud-2-0-payment-method) + - [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) @@ -99,7 +99,7 @@ On the **Billing page**, view the total limits available for the Free Plan. ## Exceeded rate limits -If you exceed your plan's [rate limits](/v2.0/cloud/pricing-plans/), {{< cloud-name >}} provides a notification in the {{< cloud-name "short" >}} user interface (UI) and adds a rate limit event to your **Usage** page for review. +If you exceed your plan's [rate limits](/v2.0/account-management/pricing-plans/), {{< cloud-name >}} provides a notification in the {{< cloud-name "short" >}} user interface (UI) and adds a rate limit event to your **Usage** page for review. All rate-limited requests are rejected; including both read and write requests. _Rate-limited requests are **not** queued._ diff --git a/content/v2.0/account-management/data-usage.md b/content/v2.0/account-management/data-usage.md index 5c5f1984a..c7973ecc3 100644 --- a/content/v2.0/account-management/data-usage.md +++ b/content/v2.0/account-management/data-usage.md @@ -32,14 +32,14 @@ Find data usage information for the time frame specified in the drop-down at the ## Exceeded rate limits -If you exceed your plan's [rate limits](/v2.0/cloud/pricing-plans/), {{< cloud-name >}} +If you exceed your plan's [rate limits](/v2.0/account-management/pricing-plans/), {{< cloud-name >}} will provide a notification in the {{< cloud-name "short" >}} user interface (UI) and add a rate limit event to your **Usage** page for review. All rate-limited requests are rejected; including both read and write requests. _Rate-limited requests are **not** queued._ -_To remove rate limits, [upgrade to a Usage-based Plan](/v2.0/cloud/account-management/upgrade-to-usage-based-plan/)._ +_To remove rate limits, [upgrade to a Usage-based Plan](/v2.0/account-management/billing/#upgrade-to-usage-based-plan)._ ### Rate-limited HTTP response code When a request exceeds your plan's rate limit, the InfluxDB API returns the following response: diff --git a/content/v2.0/account-management/pricing-plans.md b/content/v2.0/account-management/pricing-plans.md index 2a27ec996..0c3f9de56 100644 --- a/content/v2.0/account-management/pricing-plans.md +++ b/content/v2.0/account-management/pricing-plans.md @@ -19,7 +19,7 @@ InfluxDB Cloud 2.0 offers two pricing plans: - [Free Plan](#free-plan) - [Usage-based Plan](#usage-based-plan) - + ## Free Plan @@ -44,11 +44,11 @@ Data retention is determined by the time at which data is written to InfluxDB; n - Unlimited Slack notification endpoints -_To remove rate limits, [upgrade to a Usage-based Plan](/v2.0/cloud/account-management/upgrade-to-usage-based-plan/)._ +_To remove rate limits, [upgrade to a Usage-based Plan](/v2.0/account-management/billing/#upgrade-to-usage-based-plan)._ ## Usage-based Plan -The Usage-based Plan offers more flexibility and ensures you only pay for what you [use](/v2.0/cloud/account-management/data-usage/). +The Usage-based Plan offers more flexibility and ensures you only pay for what you [use](/v2.0/account-management/data-usage/). #### Usage-based Plan rate limits diff --git a/content/v2.0/get-started.md b/content/v2.0/get-started.md index 793bd04e0..1d4bbde06 100644 --- a/content/v2.0/get-started.md +++ b/content/v2.0/get-started.md @@ -29,7 +29,7 @@ _See [Differences between InfluxDB Cloud and InfluxDB OSS](#differences-between- ### Start for free -Start using {{< cloud-name >}} at no cost with the [Free Plan](/v2.0/cloud/pricing-plans/#free-plan). +Start using {{< cloud-name >}} at no cost with the [Free Plan](/v2.0/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. @@ -40,7 +40,7 @@ Limits are designed to let you monitor 5-10 sensors, stacks or servers comfortab To subscribe to an InfluxDB Cloud 2.0 **Free Plan** through InfluxData, go to [InfluxDB Cloud 2.0]({{< cloud-link >}}), enter your credentials, and then click **Start your Free Plan now**. - When you're ready to grow, [upgrade to the Usage-Based Plan](/v2.0/cloud/account-management/upgrade-to-usage-based-plan/). + When you're ready to grow, [upgrade to the Usage-Based Plan](/v2.0/account-management/billing/#upgrade-to-usage-based-plan). - **Subscribe through a cloud provider** To subscribe to an InfluxDB Cloud **Usage-Based** plan and pay through your **Amazon Web Services (AWS)** or **Google Cloud Platform (GCP)** account: @@ -496,5 +496,5 @@ The primary differences between InfluxDB OSS 2.0 and InfluxDB Cloud 2.0 are: - **Integrated visualization and dashboards**: Based on the pioneering Chronograf project, the new user interface (InfluxDB UI) offers quick and effortless onboarding, richer user experiences, and significantly quicker results. -- **Usage-based pricing**: The [Usage-based Plan](/v2.0/cloud/pricing-plans/#usage-based-plan) +- **Usage-based pricing**: The [Usage-based Plan](/v2.0/account-management/pricing-plans/#usage-based-plan) offers more flexibility and ensures that you only pay for what you use. diff --git a/content/v2.0/reference/flux/stdlib/experimental/join.md b/content/v2.0/reference/flux/stdlib/experimental/join.md index 26c0d8765..7297b4420 100644 --- a/content/v2.0/reference/flux/stdlib/experimental/join.md +++ b/content/v2.0/reference/flux/stdlib/experimental/join.md @@ -18,7 +18,7 @@ Use the [`fn` parameter](#fn) to map new output tables using values from input t To join streams of tables with different fields or measurements, use [`group()`](/v2.0/reference/flux/stdlib/built-in/transformations/group/) or [`drop()`](/v2.0/reference/flux/stdlib/built-in/transformations/drop/) to remove `_field` and `_measurement` from the group key before joining. -_See an example [below](#join-two-streams-of-tables-with-different-fields)._ +_See an example [below](#join-two-streams-of-tables-with-different-fields-and-measurements)._ {{% /note %}} _**Function type:** Transformation_ diff --git a/content/v2.0/visualize-data/other-tools/grafana.md b/content/v2.0/visualize-data/other-tools/grafana.md index 52b653fcc..f2770ee41 100644 --- a/content/v2.0/visualize-data/other-tools/grafana.md +++ b/content/v2.0/visualize-data/other-tools/grafana.md @@ -19,7 +19,7 @@ The **Grafana Flux Data Source plugin** is currently in beta. {{% /warn %}} 1. [Sign up for {{< cloud-name >}}](/v2.0/get-started/) or - [Start InfluxDB 2.0 OSS](/v2.0/get-started/#start-using-influxdb-oss). + [Start InfluxDB 2.0 OSS](/v2.0/get-started/#start-with-influxdb-oss). 2. [Download and install Grafana](https://grafana.com/grafana/download). 3. Install the **Grafana Flux Data Source plugin** manually or with `grafana-cli` (installed with Grafana). diff --git a/content/v2.0/write-data/use-telegraf/use-telegraf-plugins/use-http-plugin.md b/content/v2.0/write-data/use-telegraf/use-telegraf-plugins/use-http-plugin.md index d668a2c61..c0717a2d2 100644 --- a/content/v2.0/write-data/use-telegraf/use-telegraf-plugins/use-http-plugin.md +++ b/content/v2.0/write-data/use-telegraf/use-telegraf-plugins/use-http-plugin.md @@ -13,7 +13,7 @@ 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](telegraf/v1.13/plugins/plugin-list/#influxdb) to write metrics to your InfluxDB 2.0 instance. +Configure [`influxdb` output plugin](/v2.0/reference/telegraf-plugins/#influxdb) to write metrics to your InfluxDB 2.0 instance. ## Configure the HTTP Input plugin in your Telegraf configuration file