Merge branch 'master' into flux-0.37
Scott Anderson
commit
2fb5231fc2
|
|
@ -66,12 +66,11 @@
|
|||
|
||||
.btn {
|
||||
display: inline-block;
|
||||
padding: .85rem 1.5rem;
|
||||
padding: .65rem 2.5rem;
|
||||
color: $g20-white;
|
||||
font-weight: bold;
|
||||
background: rgba($g20-white, .25);
|
||||
border: 2px solid rgba($g20-white, .5);
|
||||
border-radius: $radius;
|
||||
background: rgba($g20-white, .2);
|
||||
border: 2px solid $g20-white;
|
||||
transition: background-color .2s, color .2s;
|
||||
|
||||
&:hover {
|
||||
|
|
@ -80,6 +79,28 @@
|
|||
}
|
||||
}
|
||||
}
|
||||
&#cloud {
|
||||
position: relative;
|
||||
margin-bottom: 1px;
|
||||
padding: 1.25rem 2rem 2.5rem;
|
||||
// background: rgba($g20-white, .15);
|
||||
background: linear-gradient(20deg, rgba($landing-cloud-gradient-left, .35), rgba($landing-cloud-gradient-right, .75) );
|
||||
|
||||
h2 {
|
||||
font-size: 1.75rem;
|
||||
margin: 1rem 1.5rem .5rem;
|
||||
}
|
||||
|
||||
a {
|
||||
color: $g20-white;
|
||||
font-weight: $medium;
|
||||
font-style: italic;
|
||||
|
||||
&:hover {
|
||||
color: $b-pool;
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
|
|
|
|||
|
|
@ -168,5 +168,7 @@ $error-page-btn-hover-text: $b-dodger;
|
|||
// Landing Page colors
|
||||
$landing-lg-gradient-left: $wp-violentdark;
|
||||
$landing-lg-gradient-right: $cp-minsk;
|
||||
$landing-cloud-gradient-left: $m-magenta;
|
||||
$landing-cloud-gradient-right: $cp-minsk;
|
||||
$landing-sm-gradient-overlay: $b-dodger;
|
||||
$landing-artwork-color: $cp-minsk;
|
||||
|
|
|
|||
|
|
@ -169,5 +169,7 @@ $error-page-btn-hover-text: $g20-white !default;
|
|||
// Landing Page colors
|
||||
$landing-lg-gradient-left: $cp-marguerite !default;
|
||||
$landing-lg-gradient-right: $b-pool !default;
|
||||
$landing-cloud-gradient-left: $wp-heart !default;
|
||||
$landing-cloud-gradient-right: $wp-seance !default;
|
||||
$landing-sm-gradient-overlay: $cp-blueviolet !default;
|
||||
$landing-artwork-color: rgba($g20-white, .15) !default;
|
||||
|
|
|
|||
|
|
@ -1,12 +0,0 @@
|
|||
---
|
||||
title: About InfluxDB Cloud 2.0
|
||||
description: Important information about InfluxDB Cloud 2.0 including release notes and known issues.
|
||||
weight: 10
|
||||
menu:
|
||||
v2_0_cloud:
|
||||
name: About InfluxDB Cloud
|
||||
---
|
||||
|
||||
Important information about InfluxDB Cloud 2.0 including known issues and release notes.
|
||||
|
||||
{{< children >}}
|
||||
|
|
@ -1,15 +0,0 @@
|
|||
---
|
||||
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
|
||||
---
|
||||
|
||||
The following issues currently exist in {{< cloud-name >}}:
|
||||
|
||||
- IDPE 2868: Users can delete a token with an active Telegraf configuration pointed to it.
|
||||
- [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.
|
||||
|
|
@ -0,0 +1,12 @@
|
|||
---
|
||||
title: Manage your InfluxDB Cloud 2.0 Account
|
||||
description: >
|
||||
View and manage information related to your InfluxDB Cloud 2.0 account such as
|
||||
pricing plans, data usage, account cancelation, etc.
|
||||
weight: 3
|
||||
menu:
|
||||
v2_0_cloud:
|
||||
name: Account management
|
||||
---
|
||||
|
||||
{{< children >}}
|
||||
|
|
@ -0,0 +1,49 @@
|
|||
---
|
||||
title: View InfluxDB Cloud data usage
|
||||
list_title: View data usage
|
||||
description: >
|
||||
View your InfluxDB Cloud 2.0 data usage and rate limit notifications.
|
||||
weight: 103
|
||||
menu:
|
||||
v2_0_cloud:
|
||||
parent: Account management
|
||||
name: View data usage
|
||||
---
|
||||
|
||||
To view your {{< cloud-name >}} data usage, hover over the **Usage** icon in the
|
||||
left navigation bar and select **Usage**.
|
||||
|
||||
{{< nav-icon "usage" >}}
|
||||
|
||||
The usage page provides data usage information for time frame specified in the
|
||||
drop-down at the top of the Usage page.
|
||||
|
||||
- **Writes:** Total data in MB written to your {{< cloud-name "short" >}} instance.
|
||||
- **Reads:** Total data in MB sent as responses to queries from your {{< cloud-name "short" >}} instance.
|
||||
- **Query Duration:** Total time spent processing queries in seconds.
|
||||
- **Storage Usage:** Total disk usage in gigabytes.
|
||||
- **API Request Count:** The total number of query and write API requests received
|
||||
during the specified time frame.
|
||||
- **Usage over the specified time period:** A line graph that visualizes usage over the specified time period.
|
||||
- **Rate Limits over the specified time period:** A list of rate limit events over
|
||||
the specified time period.
|
||||
|
||||
{{< img-hd src="/img/2-0-cloud-usage.png" />}}
|
||||
|
||||
## Exceeded rate limits
|
||||
If you exceed your plan's [rate limits](/v2.0/cloud/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 Pay As You Go Plan](/v2.0/cloud/account-management/upgrade-to-payg/)._
|
||||
|
||||
### Rate-limited HTTP response code
|
||||
When a request exceeds your plan's rate limit, the InfluxDB API returns the following response:
|
||||
|
||||
```
|
||||
HTTP 429 “Too Many Requests”
|
||||
Retry-After: xxx (seconds to wait before retrying the request)
|
||||
```
|
||||
|
|
@ -0,0 +1,53 @@
|
|||
---
|
||||
title: Cancel your InfluxDB Cloud subscription
|
||||
description: >
|
||||
Cancel your InfluxDB Cloud 2.0 account at any time by stopping all read and write
|
||||
requests, backing up data, and contacting InfluxData Support.
|
||||
weight: 104
|
||||
menu:
|
||||
v2_0_cloud:
|
||||
parent: Account management
|
||||
name: Cancel InfluxDB Cloud
|
||||
---
|
||||
|
||||
You can cancel your {{< cloud-name >}} account at any time. To do so, follow the steps below.
|
||||
|
||||
### 1. Stop reading and writing data to {{< cloud-name >}}
|
||||
|
||||
To stop being charged for {{< cloud-name "short" >}}, you'll first need to pause all your writes and queries.
|
||||
|
||||
### 2. Export your data and other artifacts
|
||||
|
||||
To export data and artifacts, follow the steps below.
|
||||
|
||||
{{% note %}}
|
||||
Exported data and artifacts can be used in an InfluxDB OSS instance.
|
||||
{{% /note %}}
|
||||
|
||||
#### Export tasks
|
||||
|
||||
For details, see [Export a task](/v2.0/process-data/manage-tasks/export-task/).
|
||||
|
||||
#### Export dashboards
|
||||
|
||||
For details, see [Export a dashboard](v2.0/visualize-data/dashboards/export-dashboard/).
|
||||
|
||||
#### Telegraf configurations
|
||||
|
||||
**To save a Telegraf configuration:**
|
||||
|
||||
1. Click in the **Organizations** icon in the navigation bar.
|
||||
|
||||
{{< nav-icon "orgs" >}}
|
||||
|
||||
2. Select the **Telegraf** tab. A list of existing Telegraf configurations appears.
|
||||
3. Click on the name of a Telegraf configuration.
|
||||
4. Click **Download Config** to save.
|
||||
|
||||
#### Data backups
|
||||
|
||||
To request a backup of data in your {{< cloud-name "short" >}} instance, contact [InfluxData Support](mailto:support@influxdata.com).
|
||||
|
||||
### 3. Contact Support
|
||||
|
||||
To cancel your subscription, reach out to [InfluxData Support](mailto:support@influxdata.com). Your payment method is charged your final balance immediately upon cancelation of service.
|
||||
|
|
@ -0,0 +1,30 @@
|
|||
---
|
||||
title: Upgrade to a Pay As You Go Plan
|
||||
description: >
|
||||
Upgrade to a Pay As You Go Plan to remove rate limits from your InfluxDB Cloud 2.0 account.
|
||||
weight: 102
|
||||
menu:
|
||||
v2_0_cloud:
|
||||
parent: Account management
|
||||
name: Upgrade to Pay As You Go
|
||||
---
|
||||
|
||||
To upgrade to a Pay As You Go Plan:
|
||||
|
||||
1. Hover over the **Usage** icon in the left navigation bar and select **Billing**.
|
||||
|
||||
{{< nav-icon "usage" >}}
|
||||
|
||||
2. Click **Upgrade to Pay As You Go**.
|
||||
3. Review the terms and pricing associated with the Pay As You Go Plan.
|
||||
4. Click **Sounds Good To Me**.
|
||||
5. Enter your contact information.
|
||||
Traditionally this would be "shipping" information, but InfluxData does not ship anything.
|
||||
This information should be the primary location where the service is consumed.
|
||||
All service updates, security notifications and other important information are
|
||||
sent using the information you provide.
|
||||
The address is used to determine any applicable sales tax.
|
||||
security notifications, etc.
|
||||
6. Enter your payment information and click **Add Card**.
|
||||
7. Review the plan details, contact information, and credit card information.
|
||||
8. Click **Confirm & Order**.
|
||||
|
|
@ -1,94 +1,142 @@
|
|||
---
|
||||
title: Get started with InfluxDB Cloud 2.0 Beta
|
||||
title: Get started with InfluxDB Cloud 2.0
|
||||
description: >
|
||||
Sign up for and get started with InfluxDB Cloud 2.0 Beta.
|
||||
Sign up now, sign in, and get started exploring and using the InfluxDB Cloud 2.0 time series platform.
|
||||
weight: 1
|
||||
menu:
|
||||
v2_0_cloud:
|
||||
name: Get started with InfluxDB Cloud
|
||||
---
|
||||
|
||||
{{< cloud-name >}} is a fully managed and hosted version of the InfluxDB 2.0.
|
||||
To get started, complete the tasks below.
|
||||
{{< cloud-name >}} is a fully managed, hosted, multi-tenanted version of the
|
||||
InfluxDB 2.0 time series data platform.
|
||||
The core of {{< cloud-name "short" >}} is built on the foundation of the open source
|
||||
version of InfluxDB 2.0, which is much more than a database.
|
||||
It is a time series data platform that collects, stores, processes and visualizes metrics and events.
|
||||
|
||||
{{% cloud-msg %}}
|
||||
InfluxDB v2.0 alpha documentation applies to {{< cloud-name "short" >}} unless otherwise specified.
|
||||
{{% /cloud-msg %}}
|
||||
_See the differences between {{< cloud-name "short">}} and InfluxDB OSS
|
||||
[below](#differences-between-influxdb-cloud-and-influxdb-oss)._
|
||||
|
||||
## Start for free
|
||||
Start using {{< cloud-name >}} at no cost with the [Free Plan](/v2.0/cloud/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.
|
||||
Once you're ready to grow, [upgrade to the Pay As You Go Plan](/v2.0/cloud/account-management/upgrade-to-payg/).
|
||||
|
||||
## Sign up
|
||||
|
||||
1. Go to [InfluxDB Cloud 2.0]({{< cloud-link >}}), enter your email and password,
|
||||
and then click **Sign Up**.
|
||||
1. Go to [InfluxDB Cloud 2.0]({{< cloud-link >}}), enter your email address and password,
|
||||
and click **Sign Up**.
|
||||
2. InfluxDB Cloud requires email verification to complete the sign up process.
|
||||
Verify your email address by opening the email sent to the address you provided
|
||||
and clicking **Verify Your Email**.
|
||||
3. Select a region for you {{< cloud-name >}} instance.
|
||||
Currently, {{< cloud-name >}} AWS - US West (Oregon) is the only region available.
|
||||
_To suggest regions to add, click **Let us know** under Regions._
|
||||
4. Review the terms of the agreement, and then select
|
||||
**I have viewed and agree to InfluxDB Cloud 2.0 Services Subscription Agreement
|
||||
and InfluxData Global Data Processing Agreement.**.
|
||||
|
||||
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.
|
||||
For details on the agreements, see the [InfluxDB Cloud 2.0: Services Subscription Agreement](https://www.influxdata.com/legal/terms-of-use/)
|
||||
and the [InfluxData Global Data Processing Agreement](https://www.influxdata.com/legal/influxdata-global-data-processing-agreement/).
|
||||
|
||||
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.
|
||||
5. Click **Continue**. {{< cloud-name >}} opens with a default organization
|
||||
and bucket (both created from your email address).
|
||||
|
||||
4. Review the terms of the beta agreement, and then select
|
||||
**I viewed and agree to InfluxDB Cloud 2.0 Beta Agreement**.
|
||||
_To update organization and bucket names, see [Update an organtization](/v2.0/organizations/update-org/)
|
||||
and [Update a bucket](/v2.0/organizations/buckets/update-bucket/#update-a-bucket-s-name-in-the-influxdb-ui)._
|
||||
|
||||
5. Click **Continue**. InfluxDB Cloud 2.0 opens with a default organization
|
||||
(created from your email) and bucket (created from your email local-part).
|
||||
{{% cloud-msg %}}
|
||||
All InfluxDB 2.0 documentation applies to {{< cloud-name "short" >}} unless otherwise specified.
|
||||
References to the InfluxDB user interface (UI) or localhost:9999 refer to your
|
||||
{{< cloud-name >}} UI.
|
||||
{{% /cloud-msg %}}
|
||||
|
||||
## Log in
|
||||
Log in to [InfluxDB Cloud 2.0](https://us-west-2-1.aws.cloud2.influxdata.com) using the credentials created above.
|
||||
## Sign in
|
||||
|
||||
Sign in to [InfluxDB Cloud 2.0](https://cloud2.influxdata.com) using your email address and password.
|
||||
|
||||
<a class="btn" href="https://cloud2.influxdata.com">Sign in to InfluxDB Cloud 2.0 now</a>
|
||||
|
||||
## Collect and write data
|
||||
Collect and write data to InfluxDB using Telegraf, the InfluxDB v2 API, `influx`
|
||||
command line interface (CLI), the InfluxDB user interface (UI), or client libraries.
|
||||
|
||||
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.0), 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 UI or manually update an
|
||||
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](/v2.0/write-data/use-telegraf/auto-config/#create-a-telegraf-configuration)
|
||||
and [Manually update Telegraf configurations](/v2.0/write-data/use-telegraf/manual-config/).
|
||||
|
||||
### API, CLI, and client libraries
|
||||
For information about using the InfluxDB API, CLI, and client libraries to write data,
|
||||
|
||||
For information about using the InfluxDB v2 API, `influx` CLI, and client libraries to write data,
|
||||
see [Write data to InfluxDB](/v2.0/write-data/).
|
||||
|
||||
{{% note %}}
|
||||
|
||||
#### InfluxDB Cloud instance endpoint
|
||||
When using Telegraf, the API, CLI, or client libraries to interact with your {{< cloud-name "short" >}}
|
||||
|
||||
When using Telegraf, the InfluxDB v2 API, the `influx` CLI, or the client libraries to interact with your {{< cloud-name "short" >}}
|
||||
instance, extract the "host" or "endpoint" of your instance from your {{< cloud-name "short" >}} UI URL.
|
||||
For example:
|
||||
|
||||
```
|
||||
https://us-west-2-1.aws.cloud2.influxdata.com
|
||||
```
|
||||
|
||||
{{% /note %}}
|
||||
|
||||
## Query and visualize data
|
||||
|
||||
Once you've set up {{< cloud-name "short" >}} to collect data, you can do the following:
|
||||
|
||||
- Query data using Flux, the UI, and the `influx` command line interface. See [Query data](/v2.0/query-data/).
|
||||
- Build custom dashboards to visualize your data. See [Visualize data](/v2.0/visualize-data/).
|
||||
- Query data using Flux, the UI, and the `influx` command line interface.
|
||||
See [Query data](/v2.0/query-data/).
|
||||
- Build custom dashboards to visualize your data.
|
||||
See [Visualize data](/v2.0/visualize-data/).
|
||||
|
||||
## Process data
|
||||
|
||||
Use InfluxDB tasks to process and downsample data. See [Process data](/v2.0/process-data/).
|
||||
|
||||
## View data usage
|
||||
Once you've set up {{< cloud-name "short" >}} to collect data, view your data usage, including:
|
||||
|
||||
- **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.
|
||||
Once you're up and running with {{< cloud-name "short" >}}, [monitor your data usage in
|
||||
your {{< cloud-name "short" >}} UI](/v2.0/cloud/account-management/data-usage/).
|
||||
|
||||
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.
|
||||
## Differences between InfluxDB Cloud and InfluxDB OSS
|
||||
{{< cloud-name >}} is API-compatible and functionally compatible with InfluxDB OSS 2.0.
|
||||
The primary differences between InfluxDB OSS 2.0 and InfluxDB Cloud 2.0 are:
|
||||
|
||||
{{< img-hd src="/img/2-0-cloud-usage.png" />}}
|
||||
- [InfluxDB scrapers](/v2.0/write-data/scrape-data/) that collect data from specified
|
||||
targets are not available in {{< cloud-name "short" >}}.
|
||||
- {{< cloud-name "short" >}} instances are currently limited to a single organization with a single user.
|
||||
- Retrieving data from a file based CSV source using the `file` parameter of the
|
||||
[`csv.from()`](/v2/reference/flux/functions/csv/from) function is not supported;
|
||||
however you can use raw CSV data with the `csv` parameter.
|
||||
- Multi-organization accounts and multi-user organizations are currently not
|
||||
available in {{< cloud-name >}}.
|
||||
|
||||
## 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.
|
||||
### New features in InfluxDB Cloud 2.0
|
||||
|
||||
To upgrade to Paid tier for free, discuss use cases, or increase rate limits,
|
||||
reach out to <a href="mailto:cloudbeta@influxdata.com?subject={{< cloud-name >}} 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 %}}
|
||||
- **Free Plan (rate-limited)**: Skip downloading and installing InfluxDB 2.0 and
|
||||
jump right in to exploring InfluxDB 2.0 technology.
|
||||
The Free Plan is designed for getting started with InfluxDB and for small hobby projects.
|
||||
- **Flux support**: [Flux](/v2.0/query-data/get-started/) is a standalone data
|
||||
scripting and query language that increases productivity and code reuse.
|
||||
It is the primary language for working with data within InfluxDB 2.0.
|
||||
Flux can be used with other data sources as well.
|
||||
This allows users to work with data where it resides.
|
||||
- **Unified API**: Everything in InfluxDB (ingest, query, storage, and visualization)
|
||||
is now accessible using a unified [InfluxDB v2 API](/v2.0/reference/api/) that
|
||||
enables seamless movement between open source and cloud.
|
||||
- **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 [The Pay As You Go Plan](/v2.0/cloud/pricing-plans/#pay-as-you-go-plan)
|
||||
offers more flexibility and ensures that you only pay for what you use.
|
||||
|
|
|
|||
|
|
@ -0,0 +1,50 @@
|
|||
---
|
||||
title: InfluxDB Cloud 2.0 pricing plans
|
||||
description: >
|
||||
InfluxDB Cloud 2.0 provides two pricing plans to fit your needs – the rate-limited
|
||||
Free Plan and the Pay As You Go Plan.
|
||||
aliases:
|
||||
- /v2.0/cloud/rate-limits/
|
||||
weight: 2
|
||||
menu:
|
||||
v2_0_cloud:
|
||||
name: Pricing plans
|
||||
---
|
||||
|
||||
InfluxDB Cloud 2.0 offers two pricing plans:
|
||||
|
||||
- [Free Plan](#free-plan)
|
||||
- [Pay As You Go Plan](#pay-as-you-go-plan)
|
||||
|
||||
## Free Plan
|
||||
All new {{< cloud-name >}} accounts start with a rate-limited Free Plan.
|
||||
Use it as much and as long as you want within the Free Plan rate limits:
|
||||
|
||||
#### Free Plan rate limits
|
||||
- **Writes:** 3MB every 5 minutes
|
||||
- **Query:** 30MB every 5 minutes
|
||||
- **Storage:** 72-hour data retention
|
||||
- **Create:**
|
||||
- Up to 5 dashboards
|
||||
- Up to 5 tasks
|
||||
- Up to 2 buckets
|
||||
|
||||
_To remove rate limits, [upgrade to a Pay As You Go Plan](/v2.0/cloud/account-management/upgrade-to-payg/)._
|
||||
|
||||
## Pay As You Go Plan
|
||||
Pay As You Go Plans offer more flexibility and ensure you only pay for what you use.
|
||||
|
||||
#### Pay As You Go Plan rate limits
|
||||
In order to protect against any intentional or unintentional harm,
|
||||
Pay As You Go Plans include soft rate limits:
|
||||
|
||||
- **Writes:** 300MB every 5 minutes
|
||||
- **Queries:** 3000MB every 5 minutes
|
||||
- **Storage:** Unlimited retention
|
||||
- **Create:**
|
||||
- Unlimited dashboards
|
||||
- Unlimited tasks
|
||||
- Unlimited buckets
|
||||
- Unlimited users
|
||||
|
||||
_To request higher rate limits, contact [InfluxData Support](mailto:support@influxdata.com)._
|
||||
|
|
@ -1,36 +0,0 @@
|
|||
---
|
||||
title: InfluxDB Cloud 2.0 rate limits
|
||||
description: Rate limits for Free tier users optimize InfluxDB Cloud 2.0 services.
|
||||
weight: 2
|
||||
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
|
||||
|
||||
## View data usage
|
||||
To view data usage, click **Usage** in the left navigation bar.
|
||||
|
||||
{{< nav-icon "usage" >}}
|
||||
|
||||
## 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)
|
||||
|
|
@ -58,9 +58,30 @@ logarithmicBins(start: 1.0, factor: 2.0, count: 10, infinty: true)
|
|||
// Generated list: [1, 2, 4, 8, 16, 32, 64, 128, 256, 512, +Inf]
|
||||
```
|
||||
|
||||
## Histogram visualization
|
||||
The [Histogram visualization type](/v2.0/visualize-data/visualization-types/histogram/)
|
||||
creates histograms by automatically generating bins and groups within bins using
|
||||
columns available in query results.
|
||||
|
||||
{{< img-hd src="/img/2-0-visualizations-histogram-example.png" alt="Histogram visualization" />}}
|
||||
|
||||
[Histogram visualization controls](/v2.0/visualize-data/visualization-types/histogram/#histogram-controls)
|
||||
let you specify the number of bins and how to define groups within bins.
|
||||
|
||||
### Histogram visualization data structure
|
||||
Because the Histogram visualization creates bins and bin segments based on settings
|
||||
specified in the visualization controls, query results **should not** be structured
|
||||
as histogram data.
|
||||
|
||||
{{% note %}}
|
||||
Output of the [`histogram()` function](#histogram-function) is **not** compatible
|
||||
with the Histogram visualization type.
|
||||
View the example [below](#visualize-error-counts-by-severity-over-time).
|
||||
{{% /note %}}
|
||||
|
||||
## Examples
|
||||
|
||||
### Generating a histogram with linear bins
|
||||
### Generate a histogram with linear bins
|
||||
```js
|
||||
from(bucket:"example-bucket")
|
||||
|> range(start: -5m)
|
||||
|
|
@ -105,7 +126,7 @@ Table: keys: [_start, _stop, _field, _measurement, host]
|
|||
2018-11-07T22:19:58.423358000Z 2018-11-07T22:24:58.423358000Z used_percent mem Scotts-MacBook-Pro.local 75 30
|
||||
```
|
||||
|
||||
### Generating a histogram with logarithmic bins
|
||||
### Generate a histogram with logarithmic bins
|
||||
```js
|
||||
from(bucket:"example-bucket")
|
||||
|> range(start: -5m)
|
||||
|
|
@ -139,3 +160,21 @@ Table: keys: [_start, _stop, _field, _measurement, host]
|
|||
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 error counts by severity over time
|
||||
Use the [Telegraf Syslog plugin](Telegraf Syslog plugin) 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/2-0-visualizations-histogram-errors.png" alt="Logs by severity histogram" />}}
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ A bin is defined by an upper bound where all data points that are less than or e
|
|||
The bin counts are cumulative.
|
||||
|
||||
Each input table is converted into a single output table representing a single histogram.
|
||||
The output table has a the same group key as the input table.
|
||||
The output table has the same group key as the input table.
|
||||
Columns not part of the group key are removed and an upper bound column and a count column are added.
|
||||
|
||||
_**Function type:** Transformation_
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: strings.strlen() function
|
||||
description: >
|
||||
The strings.strlen() function returns the length of the a string.
|
||||
The strings.strlen() function returns the length of a string.
|
||||
String length is determined by the number of UTF code points a string contains.
|
||||
menu:
|
||||
v2_0_ref:
|
||||
|
|
|
|||
|
|
@ -38,7 +38,7 @@ Related entries: [function](#function), [selector](#selector), [transformation](
|
|||
|
||||
### bar graph
|
||||
|
||||
A visual representation 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.
|
||||
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)
|
||||
|
||||
|
|
@ -57,6 +57,10 @@ Batch size controls the size of each write batch that Telegraf sends to the outp
|
|||
|
||||
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:
|
||||
|
|
@ -64,8 +68,8 @@ In Flux, a block is a possibly empty sequence of statements within matching brac
|
|||
- Explicit blocks in the source code, for example:
|
||||
|
||||
```
|
||||
Block = "{" StatementList "}
|
||||
StatementList = { Statement }
|
||||
Block = "{" StatementList "}
|
||||
StatementList = { Statement }
|
||||
```
|
||||
|
||||
- Implicit blocks, including:
|
||||
|
|
@ -186,6 +190,12 @@ Stores time series data and handles writes and queries.
|
|||
|
||||
Related entries: [data node](#data-node)
|
||||
|
||||
### 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.
|
||||
|
|
@ -341,8 +351,7 @@ A visual representation of statistical information that uses rectangles to show
|
|||
### identifier
|
||||
|
||||
Identifiers are tokens that refer to task names, bucket names, field keys,
|
||||
measurement names, subscription names, tag keys, and
|
||||
user names.
|
||||
measurement names, tag keys, and user names.
|
||||
For examples and rules, see [Flux language lexical elements](/v2.0/reference/flux/language/lexical-elements/#identifiers).
|
||||
|
||||
Related entries:
|
||||
|
|
@ -482,14 +491,13 @@ 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
|
||||
|
||||
|
|
@ -573,12 +581,9 @@ An operator (`|>`) used in Flux to chain operations together. Specifies the outp
|
|||
|
||||
### point
|
||||
|
||||
A point in the InfluxDB data structure that consists of a single collection of fields in a series. Each point is uniquely identified by its series and timestamp. In a series, you cannot store more than one point with the same timestamp.
|
||||
When you write a new 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.
|
||||
InfluxDB stores points. A single line of text in line protocol format represents one point in InfluxDB, and includes a collection of fields in a series. Each point has four components: a measurement, a tag set, a field set, and a timestamp. A point is uniquely identified by its series and timestamp. In a series, you cannot store more than one point with the same 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: [field set](#field-set), [series](/influxdb/v1.7/concepts/glossary/#series), [timestamp](/influxdb/v1.7/concepts/glossary/#timestamp)
|
||||
-->
|
||||
Related entries: [measurement](#measurement), [tag set](#tag set), [field set](#field set), [timestamp](#timestamp)
|
||||
|
||||
### precision
|
||||
|
||||
|
|
@ -629,14 +634,26 @@ A tuple of named values represented using an object type.
|
|||
|
||||
Regular expressions (regex or regexp) are patterns used to match character combinations in strings.
|
||||
|
||||
<!--### 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 a duration of time that each data point persists. Retention policies are specified in a bucket.
|
||||
|
||||
<!--Retention polices describe how many copies of the data is stored in the cluster (replication factor), and the time range covered by shard groups (shard group duration). Retention policies are unique per bucket.
|
||||
-->
|
||||
|
||||
Related entries: [duration](#duration), [measurement](#measurement), [replication factor](#replication-factor), [series](#series), [shard duration](#shard-duration), [tag set](#tag-set)
|
||||
|
||||
-->
|
||||
|
||||
## S
|
||||
|
||||
### schema
|
||||
|
|
@ -646,7 +663,7 @@ How data is organized in InfluxDB. The fundamentals of the InfluxDB schema are b
|
|||
<!-- See [Schema Design](/influxdb/v1.7/concepts/schema_and_data_layout/) for more information.
|
||||
should we replace this with influxd generate help-schema link? -->
|
||||
|
||||
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)
|
||||
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
|
||||
|
||||
|
|
@ -663,7 +680,7 @@ Related entries: [aggregation](#aggregation), [function](#function), [transforma
|
|||
|
||||
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)
|
||||
Related entries: [field set](#field-set), [measurement](#measurement),<!-- [retention policy](/#retention-policy-rp), --> [tag set](#tag-set)
|
||||
|
||||
### series cardinality
|
||||
|
||||
|
|
@ -705,12 +722,10 @@ Related entries: [field key](#field-key),[measurement](#measurement), [tag key](
|
|||
|
||||
### server
|
||||
|
||||
A computer, virtual or physical, running InfluxDB. <!--still valid There should only be one InfluxDB process per server. -->
|
||||
A computer, virtual or physical, running InfluxDB. <!--is this still valid for 2.0: There should only be one InfluxDB process per server. -->
|
||||
|
||||
Related entries: [node](#node)
|
||||
|
||||
<!-- ### service -->
|
||||
|
||||
### service input plugin
|
||||
|
||||
Telegraf input plugins that run in a passive collection mode while the Telegraf agent is running.
|
||||
|
|
@ -718,7 +733,7 @@ Service input plugins listen on a socket for known protocol inputs, or apply the
|
|||
|
||||
Related entries: [aggregator plugin](#aggregator-plugin), [input plugin](#input-plugin), [output plugin](#output-plugin), [processor plugin](#processor-plugin)
|
||||
|
||||
<!--### shard - in development
|
||||
<!--### shard
|
||||
|
||||
A shard contains encoded and compressed data. Shards are represented by a TSM file on disk.
|
||||
Every shard belongs to one and only one shard group.
|
||||
|
|
@ -750,48 +765,55 @@ Related entries: [database](#database), [retention policy](#retention-policy-rp)
|
|||
|
||||
-->
|
||||
|
||||
<!--### Single Stat
|
||||
### 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
|
||||
|
||||
### source
|
||||
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.
|
||||
|
||||
### stacked graph
|
||||
<!-- in development ### stacked graph
|
||||
|
||||
### statement
|
||||
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
|
||||
|
||||
In InfluxDB 1.x, a [step-plot graph](https://docs.influxdata.com/chronograf/v1.7/guides/visualization-types/#step-plot-graph) displays time series data in a staircase graph. In InfluxDB 2.0, generate a similar graph using the step interpolation option for [line graphs](https://v2.docs.influxdata.com/v2.0/visualize-data/visualization-types/graph/#options).
|
||||
|
||||
### stream
|
||||
|
||||
"stream of tables"
|
||||
|
||||
-->
|
||||
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.
|
||||
|
||||
<!-- how does this work in 2.0? ### subscription
|
||||
|
||||
Subscriptions allow [Kapacitor](/kapacitor/latest/) to receive data from InfluxDB in a push model rather than the pull model based on querying data.
|
||||
When Kapacitor is configured to work with InfluxDB, the subscription will automatically push every write for the subscribed database from InfluxDB to Kapacitor.
|
||||
Subscriptions can use TCP or UDP for transmitting the writes.
|
||||
|
||||
-->
|
||||
|
||||
## T
|
||||
|
||||
<!--### TCP
|
||||
### TCP
|
||||
|
||||
InfluxDB uses Transmission Control Protocol (TCP) port 9999 for client-server communication over the InfluxDB HTTP API.
|
||||
|
||||
<!--ports for InfluxDB Enterprise -->
|
||||
|
||||
### 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)
|
||||
|
||||
### TSM file
|
||||
|
||||
|
||||
### 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.
|
||||
|
|
@ -823,10 +845,14 @@ 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
|
||||
### task
|
||||
|
||||
### Telegraf
|
||||
-->
|
||||
|
||||
A plugin-driven agent that collects, processes, aggregates, and writes metrics.
|
||||
|
||||
Related entries: [Automatically configure Telegraf](https://v2.docs.influxdata.com/v2.0/write-data/use-telegraf/auto-config/), [Manually configure Telegraf](https://v2.docs.influxdata.com/v2.0/write-data/use-telegraf/manual-config/), [Telegraf plugins](https://v2.docs.influxdata.com/v2.0/reference/telegraf-plugins/), [Use Telegraf to collect data](https://v2.docs.influxdata.com/v2.0/write-data/use-telegraf/), [View a Telegraf configuration](https://v2.docs.influxdata.com/v2.0/write-data/use-telegraf/auto-config/view-telegraf-config/)
|
||||
|
||||
|
||||
### time (data type)
|
||||
|
||||
|
|
@ -848,8 +874,17 @@ Related entries: [point](#point)
|
|||
|
||||
### token
|
||||
|
||||
Tokens verify user and organization permissions in InfluxDB.
|
||||
|
||||
Related entries: [Create a token](https://v2.docs.influxdata.com/v2.0/security/tokens/create-token/).
|
||||
|
||||
### tracing
|
||||
|
||||
By default, tracing is disabled in InfluxDB. To enable tracing or set other InfluxDB configuration options, see (https://v2.docs.influxdata.com/v2.0/reference/config-options/).
|
||||
|
||||
<!-- any info here still relevant? https://docs.influxdata.com/influxdb/v1.7/administration/logs/#finding-all-trace-log-entries-for-an-influxdb-operation
|
||||
-->
|
||||
|
||||
### 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.
|
||||
|
|
@ -857,15 +892,21 @@ See [InfluxQL Functions](/influxdb/v1.7/query_language/functions/#transformation
|
|||
|
||||
Related entries: [aggregation](/influxdb/v1.7/concepts/glossary/#aggregation), [function](/influxdb/v1.7/concepts/glossary/#function), [selector](/influxdb/v1.7/concepts/glossary/#selector)
|
||||
|
||||
## tsm (Time Structured Merge tree) - in 1.x - obsolete?
|
||||
## TSM (Time Structured Merge tree)
|
||||
|
||||
The purpose-built data storage format for InfluxDB. TSM allows for greater compaction and higher write and read throughput than existing B+ or LSM tree implementations. See [Storage Engine](http://docs.influxdata.com/influxdb/v1.7/concepts/storage_engine/) for more.
|
||||
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](http://docs.influxdata.com/influxdb/v1.7/concepts/storage_engine/).
|
||||
|
||||
Related entries: [TSI](#TSI)
|
||||
|
||||
## 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.
|
||||
|
||||
## 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.
|
||||
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
|
||||
|
||||
|
|
@ -895,8 +936,9 @@ 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
|
||||
## 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.
|
||||
|
|
@ -904,7 +946,8 @@ The temporary cache for recently written points. To reduce the frequency that pe
|
|||
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
|
||||
|
||||
The process of partitioning data based on equal windows of time.
|
||||
Grouping data based on specified time intervals. For information about how to window in Flux, see [Window and aggregate data with Flux](https://v2.docs.influxdata.com/v2.0/query-data/guides/window-aggregate/).
|
||||
|
|
|
|||
|
|
@ -4,6 +4,6 @@ enterprise:
|
|||
link: "#"
|
||||
|
||||
cloud:
|
||||
name: "InfluxDB Cloud 2.0 Beta"
|
||||
name: "InfluxDB Cloud 2.0"
|
||||
shortname: "InfluxDB Cloud"
|
||||
link: "https://cloud2.influxdata.com/beta/signup"
|
||||
|
|
|
|||
|
|
@ -13,6 +13,10 @@
|
|||
<a class="btn" href="get-started">Get Started</a>
|
||||
</div>
|
||||
{{ partial "svgs/hive.svg" }}
|
||||
<div class="card full" id="cloud">
|
||||
<h2>InfluxDB Cloud 2.0</h2>
|
||||
<a href="cloud/get-started/">Get started in the cloud</a>
|
||||
</div>
|
||||
<div class="group">
|
||||
|
||||
<a class="card quarter" href="write-data">
|
||||
|
|
|
|||
|
|
@ -1,8 +1,18 @@
|
|||
{{ $cloudName := .Site.Data.products.cloud.name }}
|
||||
{{ $cloudNameShort := .Site.Data.products.cloud.shortname }}
|
||||
<hr/>
|
||||
<div class="feedback block">
|
||||
<h4>{{ $cloudName }} Bug Reports and Feedback</h4>
|
||||
<h4>{{ $cloudName }} Support</h4>
|
||||
<p>
|
||||
To provide feedback or report a bug, send an email to <a href="mailto:cloudbeta@influxdata.com?subject={{ $cloudName }} Feedback">cloudbeta@influxdata.com</a>.
|
||||
The following resources are available when you need help with {{ $cloudNameShort }}:
|
||||
</p>
|
||||
<h5>Free Plan</h5>
|
||||
<ul>
|
||||
<li>Reach out in the <a href="https://community.influxdata.com/">InfluxData Community</a>.</li>
|
||||
</ul>
|
||||
<h5>Pay As You Go Plan</h5>
|
||||
<ul>
|
||||
<li>Reach out in the <a href="https://community.influxdata.com/">InfluxData Community</a>.</li>
|
||||
<li>Contact <a href="mailto:support@influxdata.com" target="_blank">InfluxData Support</a>.</li>
|
||||
</ul>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@
|
|||
{{ end }}
|
||||
<meta name="description" content="{{ if .Description }}{{ .Description | markdownify | plainify }}{{else}}{{ .Summary | markdownify | plainify }}{{ end }}">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1">
|
||||
<link rel="shortcut icon" href="/img/favicon.png" type="image/png">
|
||||
<link rel="shortcut icon" href="/img/favicon.png" type="image/png" sizes="32x32">
|
||||
|
||||
{{ partial "header/canonical.html" . }}
|
||||
{{ partial "header/stylesheets.html" }}
|
||||
|
|
|
|||
Binary file not shown.
|
Before Width: | Height: | Size: 185 KiB After Width: | Height: | Size: 36 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 4.2 KiB After Width: | Height: | Size: 13 KiB |
Loading…
Reference in New Issue