diff --git a/content/influxdb/cloud/account-management/billing.md b/content/influxdb/cloud/account-management/billing.md index 533fdd0bc..4785ce212 100644 --- a/content/influxdb/cloud/account-management/billing.md +++ b/content/influxdb/cloud/account-management/billing.md @@ -104,7 +104,7 @@ If exceed the series cardinality limit, InfluxDB adds a rate limit event to your - **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/). -- **Free plan**: To remove rate limits, [upgrade to a Usage-based Plan](#upgrade-to-usage-based-plan). +- **Free plan**: To raise rate limits, [upgrade to a Usage-based Plan](#upgrade-to-usage-based-plan). #### Write and query limits (HTTP response code) @@ -123,8 +123,8 @@ Billing occurs on the first day of the month for the previous month. For example | Timeline | Action | |:----------------------------|:------------------------------------------------------------------------------------------------------------------------| -| **Initial declined payment**| We'll retry charge every 72 hours. During this period, update your payment method to successfully process your payment. | -| **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.| +| **Initial declined payment**| We'll retry charge every 72 hours. During this period, update your payment method to successfully process your payment. | +| **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 4df6b3dad..50be0d543 100644 --- a/content/influxdb/cloud/account-management/data-usage.md +++ b/content/influxdb/cloud/account-management/data-usage.md @@ -32,16 +32,17 @@ Find data usage information for the time frame specified in the drop-down at the If you exceed your [plan's rate limits](/influxdb/cloud/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. InfluxDB Cloud plans include the following rate limits: -- If **write or read requests exceed** the specified limit within a five-minute window, InfluxDB retries the request after that five-minute interval. The UI displays `event_type_limited_query` or `event_type_limited_write` as fields. -- If the **series cardinality exceeds** the limit, requests are rejected and **not** queued. The UI displays `event_type_limited_cardinality` as a field. +- If **write or read requests or series cardinality exceed** the specified limit within a five-minute window, the request is rejected and the UI displays `event_type_limited_query` or `event_type_limited_write` or `event_type_limited_cardinality` as fields. -_To remove rate limits, [upgrade to a Usage-based Plan](/influxdb/cloud/account-management/billing/#upgrade-to-usage-based-plan)._ +_To raise these rate limits, [upgrade to a Usage-based Plan](/influxdb/cloud/account-management/billing/#upgrade-to-usage-based-plan)._ + +- If **delete requests exceed** the specified limit within a five-minute window, the request is rejected and the UI displays `event_type_limited_delete_rate` as the field. ### InfluxDB API: HTTP rate limit responses The InfluxDB API returns the following responses: -- When a **read or write request exceeds** your plan's limit: +- When a **read or write or delete request exceeds** limits: ``` HTTP 429 “Too Many Requests” diff --git a/content/influxdb/cloud/account-management/pricing-plans.md b/content/influxdb/cloud/account-management/pricing-plans.md index 87c4cb2d5..60e0fec89 100644 --- a/content/influxdb/cloud/account-management/pricing-plans.md +++ b/content/influxdb/cloud/account-management/pricing-plans.md @@ -45,7 +45,7 @@ To write historical data older than 30 days or retain data for more than 30 days - 2 notification rules - Unlimited Slack notification endpoints -_To remove rate limits, [upgrade to a Usage-based Plan](/influxdb/cloud/account-management/billing/#upgrade-to-usage-based-plan)._ +_To raise rate limits, [upgrade to a Usage-based Plan](/influxdb/cloud/account-management/billing/#upgrade-to-usage-based-plan)._ ## Usage-Based Plan @@ -58,7 +58,7 @@ The following vectors determine pricing: - **Data out** is the total sum of the data (measured in GB) returned to the user to answer a query, also known as data transfer costs. - **Query count** is the total number of individual query operations: - Each individual operation—including queries, tasks, alerts, notifications, and Data Explorer activity—is one billable query operation. - - Refreshing a dashboard with multiple cells will incur multiple query operations. + - Refreshing a dashboard with multiple cells will incur multiple query operations. - Failed operations aren’t counted. - **Data In** is the amount of data you’re writing into InfluxDB (measured in MB/second). - **Storage** is the amount of data you’re storing in InfluxDB (measured in GB/hour). diff --git a/content/influxdb/cloud/reference/release-notes/cloud-updates.md b/content/influxdb/cloud/reference/release-notes/cloud-updates.md index 82289ec47..1456b5082 100644 --- a/content/influxdb/cloud/reference/release-notes/cloud-updates.md +++ b/content/influxdb/cloud/reference/release-notes/cloud-updates.md @@ -14,18 +14,19 @@ 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/). -## August 2021 +## August 2021 - Add support for [explicit bucket schemas](/influxdb/cloud/organizations/buckets/bucket-schema/), which lets you enforce explicit schemas for each InfluxDB measurement, including column names, tags, fields, and data types. +- Add delete requests per organization rate limit. -## July 2021 +## July 2021 - Add new [Asia Pacific (Australia) region](https://ap-southeast-2-1.aws.cloud2.influxdata.com). -- Redesign the View Raw Data table in Data Explorer. Group keys and data types are now easily identifiable underneath column headings. -- Dashboard improvements: - - Add ability to add an [annotation to a specific time range](/influxdb/cloud/visualize-data/annotations/). - - Add ability to [automatically refresh dashboard](/influxdb/cloud/visualize-data/dashboards/control-dashboard/#automatically-refresh-dashboard). - - Add new static legend to Graph and Band Plot visualizations. +- Redesign the View Raw Data table in Data Explorer. Group keys and data types are now easily identifiable underneath column headings. +- Dashboard improvements: + - Add ability to add an [annotation to a specific time range](/influxdb/cloud/visualize-data/annotations/). + - Add ability to [automatically refresh dashboard](/influxdb/cloud/visualize-data/dashboards/control-dashboard/#automatically-refresh-dashboard). + - Add new static legend to Graph and Band Plot visualizations. ## May 2021