updates for cloud public beta
Kelly
parent
eb13003f3b
commit
861a21f732
|
|
@ -3,16 +3,13 @@ title: Known issues in InfluxDB Cloud
|
|||
description: Information related to known issues in InfluxDB Cloud 2.
|
||||
weight: 102
|
||||
menu:
|
||||
v2_0_cloud:
|
||||
name: Known issues
|
||||
parent: About InfluxDB Cloud
|
||||
v2_0_cloud:
|
||||
name: Known issues
|
||||
parent: About InfluxDB Cloud
|
||||
---
|
||||
|
||||
The following issues currently exist in {{< cloud-name >}}:
|
||||
|
||||
- IDPE 2868: Users can delete a token with an active Telegraf configuration pointed to it.
|
||||
- IDPE 3388: Users can delete themselves from their Cloud 2.0 account.
|
||||
- IDPE 3392: Free tier users bucket retention is unlimited and should be set to 72 hours.
|
||||
- IDPE 3393: Retention period for buckets in free tier can be changed by users.
|
||||
- [TELEGRAF-5600](https://github.com/influxdata/telegraf/issues/5600): Improve error message in Telegraf when the bucket it's reporting to is not found.
|
||||
- [INFLUXDB-12687](https://github.com/influxdata/influxdb/issues/12687): Create organization button should only be displayed for users with permissions to create an organization.
|
||||
|
|
|
|||
|
|
@ -3,14 +3,34 @@ title: InfluxDB Cloud release notes
|
|||
description: Important changes and notes introduced in each InfluxDB Cloud 2.0 update.
|
||||
weight: 101
|
||||
menu:
|
||||
v2_0_cloud:
|
||||
parent: About InfluxDB Cloud
|
||||
name: Release notes
|
||||
v2_0_cloud:
|
||||
parent: About InfluxDB Cloud
|
||||
name: Release notes
|
||||
---
|
||||
|
||||
## 2019-05-06 _Public Beta_
|
||||
|
||||
### Features
|
||||
|
||||
- Add rate limiting for Free tier users.
|
||||
- Add client libraries for Go and JS.
|
||||
|
||||
### Bug fixes
|
||||
|
||||
- Users cannot delete themselves from their Cloud 2.0 account.
|
||||
- The bucket retention period for Free tier users is set to 72 hours.
|
||||
- Free tier users cannot change a bucket's retention period.
|
||||
|
||||
---
|
||||
|
||||
## 2019-05-02
|
||||
|
||||
### Bug Fixes
|
||||
### Features
|
||||
|
||||
- **InfluxDB 2.0 alpha-9** –
|
||||
_See the [alpha-9 release notes](/v2.0/reference/release-notes/#v2-0-0-alpha-9-2019-05-01) for details._
|
||||
|
||||
### Bug fixes
|
||||
|
||||
- Usage statistics on the Usage page show correct values.
|
||||
- Existing tasks with duration specified in nanoseconds no longer need to be resubmitted.
|
||||
|
|
@ -18,14 +38,16 @@ menu:
|
|||
- Cloud users can use CLI tools to interact with their Cloud tenant.
|
||||
|
||||
|
||||
---
|
||||
|
||||
## 2019-04-05
|
||||
|
||||
### Features
|
||||
|
||||
- **InfluxDB 2.0 alpha-7** –
|
||||
_See the [alpha-7 release notes](/v2.0/reference/release-notes/#v2-0-0-alpha-7-2019-03-28) for details._
|
||||
_See the [alpha-7 release notes](/v2.0/reference/release-notes/#v2-0-0-alpha-7-2019-03-28) for details._
|
||||
|
||||
### Bug Fixes
|
||||
### Bug fixes
|
||||
|
||||
- Logout works in InfluxDB Cloud 2.0 UI.
|
||||
- Single sign-on works between https://cloud2.influxdata.com and https://us-west-2-1.aws.cloud2.influxdata.com.
|
||||
|
|
|
|||
|
|
@ -1,14 +1,14 @@
|
|||
---
|
||||
title: Get started with InfluxDB Cloud 2.0 Beta
|
||||
description: >
|
||||
Sign up for and get started with InfluxDB Cloud 2.0 Beta.
|
||||
Sign up for and get started with InfluxDB Cloud 2.0 Beta.
|
||||
weight: 1
|
||||
menu:
|
||||
v2_0_cloud:
|
||||
name: Get started with InfluxDB Cloud
|
||||
v2_0_cloud:
|
||||
name: Get started with InfluxDB Cloud
|
||||
|
||||
---
|
||||
{{< cloud-name >}} is a fully managed and hosted version of the [InfluxDB v2 API](/v2.0/reference/api/).
|
||||
{{< cloud-name >}} is a fully managed and hosted version of the [InfluxDB 2.0].
|
||||
To get started, complete the tasks below.
|
||||
|
||||
{{% cloud-msg %}}
|
||||
|
|
@ -21,11 +21,10 @@ InfluxDB v2.0 alpha documentation applies to {{< cloud-name "short" >}} unless o
|
|||
|
||||
2. Open email from cloudbeta@influxdata.com (subject: Please verify your email for InfluxDB Cloud), and then click **Verify Your Email**. The Welcome to InfluxDB Cloud 2.0 page is displayed.
|
||||
|
||||
3. Currently, {{< cloud-name >}} us-west-2 region is the only region available. To suggest regions to add, click the **Let us know** link under Regions.
|
||||
3. Currently, {{< cloud-name >}} us-west-2 region is the only region available. To suggest regions to add, click the **Let us know** link under Regions.
|
||||
|
||||
3. Click **View cloud beta agreement** to review the terms, and then select **I viewed and agree to InfluxDB Cloud 2.0 Beta Agreement**. (You must open the agreement before you can accept the terms.)
|
||||
|
||||
4. Click **Continue**. InfluxDB Cloud 2.0 opens with a default organization and bucket (created from your email local-part).
|
||||
4. Click **View cloud beta agreement** to review the terms, and then select **I viewed and agree to InfluxDB Cloud 2.0 Beta Agreement**. (You must open the agreement before you can accept the terms.)
|
||||
5. Click **Continue**. InfluxDB Cloud 2.0 opens with a default organization and bucket (created from your email local-part).
|
||||
|
||||
## Log in
|
||||
|
||||
|
|
@ -44,16 +43,28 @@ Once you've set up {{< cloud-name "short" >}} to collect data with Telegraf, you
|
|||
- Query data using Flux, the UI, and the `influx` command line interface. See [Query data](https://v2.docs.influxdata.com/v2.0/query-data/).
|
||||
- Build custom dashboards to visualize your data. See [Visualize data](https://v2.docs.influxdata.com/v2.0/visualize-data/).
|
||||
|
||||
## Monitor usage
|
||||
## View data usage
|
||||
|
||||
Once you've set up {{< cloud-name "short" >}} to collect data, monitor your data usage, including:
|
||||
Once you've set up {{< cloud-name "short" >}} to collect data, view your data usage, including:
|
||||
|
||||
- Writes: Total bytes ingested in the past 24 hours.
|
||||
- Reads: Total bytes sent out for responses to queries in the past 24 hours.
|
||||
- Total Query Duration: Sum of time spent processing all queries in the past 24 hours.
|
||||
- Storage: Average disk usage every hour, over the past 24 hrs.
|
||||
- Writes: Total kilobytes ingested.
|
||||
- Reads: Total kilobytes sent out for responses to queries.
|
||||
- Total Query Duration: Sum of time spent processing queries in seconds.
|
||||
- Storage: Average disk usage in gigabytes.
|
||||
|
||||
You'll see sparkline data over the past 4 hours and a single value that shows usage in the last 5 minutes. To view your data, click **Usage** in the left navigation menu.
|
||||
|
||||
{{< img-hd src="/img/2-0-cloud-usage.png" />}}
|
||||
|
||||
## Review rate limits
|
||||
|
||||
To optimize InfluxDB Cloud 2.0 services, [rate limits](/v2.0/cloud/rate-limits/) are in place for Free tier users. During beta, you can check out our Paid tier for free.
|
||||
|
||||
To upgrade to Paid tier for free, discuss use cases, or increase rate limits, reach out to <a href="mailto:cloudbeta@influxdata.com?subject={{ $cloudName }} Feedback">cloudbeta@influxdata.com</a>.
|
||||
|
||||
{{% note %}}
|
||||
#### Known issues and disabled features
|
||||
_See [Known issues](/v2.0/cloud/about/known-issues/) for information regarding all known issues in InfluxDB Cloud._
|
||||
{{% /note %}}
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -0,0 +1,49 @@
|
|||
---
|
||||
title: Rate limits
|
||||
description: Rate limits for Free tier users optimize InfluxDB Cloud 2.0 services.
|
||||
weight: 10
|
||||
menu:
|
||||
v2_0_cloud:
|
||||
name: Rate limits
|
||||
---
|
||||
|
||||
To optimize InfluxDB Cloud 2.0 services, the following rate limits are in place for Free tier users. To increase your rate limits, contact <a href="mailto:cloudbeta@influxdata.com?subject={{ $cloudName }} Feedback">cloudbeta@influxdata.com</a>.
|
||||
|
||||
- `write` endpoint:
|
||||
- 5 concurrent API calls
|
||||
- 3000 KB (10 KB/s) of data written in a 5 minute window
|
||||
|
||||
- `query` endpoint:
|
||||
- 20 concurrent API calls
|
||||
- 3000 MB (10 MB/s) of data returned in a 5 minute window
|
||||
|
||||
- 5 dashboards
|
||||
- 5 tasks
|
||||
- 2 buckets
|
||||
- 72 hour retention period
|
||||
|
||||
## HTTP response codes
|
||||
|
||||
When a request exceeds the rate limit for the endpoint, the InfluxDB API returns:
|
||||
|
||||
- HTTP 429 “Too Many Requests”
|
||||
- Retry-After: xxx (seconds to wait before retrying the request)
|
||||
|
||||
For information about the InfluxDB API, see the [Influx API Service docs](http://localhost:9999/docs).
|
||||
|
||||
<!-- potential information to add moving forward?
|
||||
|
||||
Use HTTP headers to review the following:
|
||||
|
||||
?: the rate limit ceiling for a given endpoint
|
||||
?: the number of requests remaining in the 4 hour window (will we provide functionality to change this window?)
|
||||
?: time remaining before the rate limit resets, in <precision> seconds
|
||||
|
||||
## Rate limit messaging
|
||||
|
||||
When a request exceeds the rate limit for a given API endpoint, the API returns the following errors in the response body:
|
||||
|
||||
{ "errors": [ { "code": ??, "message": "??" } ] }
|
||||
|
||||
-->
|
||||
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 549 KiB |
Loading…
Reference in New Issue