Dar 390 contact support (#5003)
* chore(cloud): Remove support from billing (https://github.com/influxdata/DAR/issues/390) * chore(cloud): Remove support from limits (https://github.com/influxdata/DAR/issues/390) * fix(serverless): Add related and fix aliases. * chore(cloud): Remove and update Support contact (https://github.com/influxdata/DAR/issues/390) * chore(serverless): Remove and update Support contact (https://github.com/influxdata/DAR/issues/390) * fix(serverless): Alternatives to deleting data, update measurement/table entries in glossary. * chore: Update Support footer. * hotfix: cloud-only tags in glossary * chore(docs): Update storage-limits to remove directions to contact support (#4996) * chore(docs): Update storage-limits to remove directions to contact support Support are not able to increase these limits on the serverless product. If customers need higher limits they should speak to sales about a dedicated solution in the first instance. * chore: fix hyperlink to sales --------- Co-authored-by: Jason Stirnaman <stirnamanj@gmail.com> * Update content/influxdb/cloud-serverless/admin/billing/_index.md Co-authored-by: Ben Tasker <88340935+btasker@users.noreply.github.com> * Update content/influxdb/cloud/account-management/billing.md Co-authored-by: Ben Tasker <88340935+btasker@users.noreply.github.com> * fix(serverless): measurement suggestions Co-authored-by: Ben Tasker <88340935+btasker@users.noreply.github.com> * Update content/influxdb/cloud-serverless/reference/internals/storage-limits.md --------- Co-authored-by: Will Cooke <will@whizzy.org> Co-authored-by: Ben Tasker <88340935+btasker@users.noreply.github.com>pull/5004/head
Jason Stirnaman
GitHub
parent
8feddb16e5
commit
ec4afbd259
|
|
@ -12,6 +12,7 @@ menu:
|
|||
influxdb_cloud_serverless:
|
||||
parent: Manage accounts
|
||||
name: Cancel InfluxDB Cloud
|
||||
alt_engine: /influxdb/cloud/account-management/offboarding/
|
||||
---
|
||||
|
||||
To cancel your InfluxDB Cloud Serverless subscription, complete the following steps:
|
||||
|
|
@ -49,12 +50,6 @@ Cloud to InfluxDB OSS, see: [Migrate data from InfluxDB Cloud to InfluxDB OSS](/
|
|||
|
||||
## Cancel service
|
||||
|
||||
{{% note %}}
|
||||
Cancelling your usage-based plan will delete your organization.
|
||||
However, those in multi-user organizations must contact
|
||||
[InfluxData Support](https://support.influxdata.com) to delete your organization.
|
||||
{{% /note %}}
|
||||
|
||||
1. Click the account name in the header of your InfluxDB Cloud Serverless
|
||||
user interface (UI) and select **Billing**.
|
||||
|
||||
|
|
|
|||
|
|
@ -109,11 +109,7 @@ On the **Billing page**, view the total limits available for the Free Plan.
|
|||
|
||||
If you exceed your plan's [adjustable quotas or limits](/influxdb/cloud-serverless/account-management/limits/), you'll receive a notification in the {{< cloud-name "short" >}} user interface (UI) **Usage** page.
|
||||
|
||||
To raise your oranization's rate limits:
|
||||
|
||||
- **Usage-Based plan**: Contact [InfluxData Support](https://support.influxdata.com)
|
||||
to request higher rate limits.
|
||||
- **Free plan**: [Upgrade to a Usage-based Plan](#upgrade-to-usage-based-plan).
|
||||
If using the **Free plan**, [upgrade to a Usage-based Plan](#upgrade-to-usage-based-plan) to raise your organization's rate limits.
|
||||
|
||||
#### Write and query limits (HTTP response code)
|
||||
|
||||
|
|
@ -134,5 +130,5 @@ Billing occurs on the first day of the month for the previous month. For example
|
|||
| :--------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| **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](https://support.influxdata.com) to process your payment and enable your account. |
|
||||
| **21 days later** | Account suspended. Contact [support.influxdata.com](https://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. |
|
||||
| **10-14 days later** | Account completely disabled. During this period, you must contact [InfluxData Support](https://support.influxdata.com/) to process your payment and enable your account. |
|
||||
| **21 days later** | Account suspended. Contact [InfluxData Support](https://support.influxdata.com/) to settle your final bill and discuss options for resuming service|
|
||||
|
|
|
|||
|
|
@ -37,8 +37,6 @@ Review adjustable service quotas and global limits to plan for your bandwidth ne
|
|||
To reduce the chance of unexpected charges and protect the service for all users,
|
||||
InfluxDB Cloud Serverless 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)
|
||||
|
|
|
|||
|
|
@ -19,8 +19,7 @@ updated_in: CLI v2.0.2
|
|||
|
||||
The `influx backup` command works with **InfluxDB OSS 2.x**, but does not work with **InfluxDB Cloud**.
|
||||
For information about backing up data in InfluxDB Cloud, see
|
||||
[InfluxDB Cloud Serverless durability](/influxdb/cloud/reference/internals/durability/) or
|
||||
[contact InfluxData Support](mailto:support@influxdata.com).
|
||||
[InfluxDB Cloud Serverless durability](/influxdb/cloud/reference/internals/durability/).
|
||||
{{% /note %}}
|
||||
|
||||
{{< duplicate-oss >}}
|
||||
|
|
|
|||
|
|
@ -18,8 +18,7 @@ updated_in: CLI v2.0.7
|
|||
|
||||
The `influx restore` command works with **InfluxDB OSS 2.x**, but does not work with **InfluxDB Cloud**.
|
||||
For information about restoring data in InfluxDB Cloud, see
|
||||
[InfluxDB Cloud durability](/influxdb/cloud/reference/internals/durability/) and
|
||||
[contact InfluxData Support](mailto:support@influxdata.com).
|
||||
[InfluxDB Cloud durability](/influxdb/cloud/reference/internals/durability/).
|
||||
{{% /note %}}
|
||||
|
||||
{{< duplicate-oss >}}
|
||||
|
|
@ -7,6 +7,8 @@ menu:
|
|||
name: IOx storage limits
|
||||
parent: InfluxDB Cloud internals
|
||||
weight: 201
|
||||
related:
|
||||
- /influxdb/cloud-serverless/write-data/best-practices/
|
||||
---
|
||||
|
||||
The InfluxDB IOx storage enforces specific limits on the storage level.
|
||||
|
|
@ -29,8 +31,7 @@ The IOx storage engine enforces the following storage-level limits:
|
|||
- **Maximum number of columns per table**: 200
|
||||
|
||||
{{% note %}}
|
||||
IOx storage service-level limits are configurable per _namespace_.
|
||||
To adjust your service-level limits, [contact InfluxData Support](https://support.influxdata.com).
|
||||
If you need higher limits than those show above, [contact InfluxData Sales](https://www.influxdata.com/contact-sales/).
|
||||
{{% /note %}}
|
||||
|
||||
## Error messages
|
||||
|
|
@ -48,9 +49,9 @@ number of columns allowed in a table.
|
|||
|
||||
#### Potential solutions
|
||||
|
||||
- Consider storing new fields in a new measurement.
|
||||
- [Contact InfluxData Support](https://support.influxdata.com) to delete any
|
||||
unnecessary data.
|
||||
- Consider storing new fields in a new [measurement](/influxdb/cloud-serverless/reference/glossary/#measurement) (not to exceed the [maximum number of tables](#maximum-number-of-tables-reached)).
|
||||
- Review [InfluxDB schema design recommendations](/influxdb/cloud-serverless/write-data/best-practices/schema-design/).
|
||||
- Customers with an annual or support contract can contact [InfluxData Support](https://support.influxdata.com) to request a review of their database schema.
|
||||
|
||||
### Maximum number of tables reached
|
||||
|
||||
|
|
@ -60,4 +61,4 @@ tables, applying this write would result in <N+> columns, limit is 500
|
|||
```
|
||||
|
||||
This error is returned for any write request that would exceed the maximum
|
||||
number of tables allowed in a namespace.
|
||||
number of tables (measurements) allowed in a namespace.
|
||||
|
|
|
|||
|
|
@ -9,9 +9,10 @@ menu:
|
|||
name: Best practices
|
||||
identifier: write-best-practices
|
||||
parent: Write data
|
||||
related:
|
||||
- /influxdb/cloud-serverless/reference/internals/storage-limits/
|
||||
aliases:
|
||||
- /influxdb/cloud-serverless/write-data/best-practices/optimize-writes/
|
||||
- /influxdb/cloud-serverless/write-data/troubleshoot/
|
||||
- /influxdb/cloud-serverless/write-data/troubleshoot/
|
||||
---
|
||||
|
||||
The following articles walk through recommendations and best practices for writing
|
||||
|
|
|
|||
|
|
@ -1,21 +1,29 @@
|
|||
---
|
||||
title: Delete data
|
||||
description: >
|
||||
To delete data from an InfluxDB Cloud Serverless bucket, please contact
|
||||
[InfluxData support](https://support.influxdata.com).
|
||||
Use measurements, tags, and timestamp columns to avoid querying unwanted data.
|
||||
menu:
|
||||
influxdb_cloud_serverless:
|
||||
name: Delete data
|
||||
parent: Write data
|
||||
weight: 107
|
||||
influxdb/cloud-serverless/tags: [delete]
|
||||
# related:
|
||||
# - /influxdb/cloud-serverless/reference/syntax/delete-predicate/
|
||||
# - /influxdb/cloud-serverless/reference/cli/influx/delete/
|
||||
---
|
||||
|
||||
The InfluxDB `/api/v2/delete` API endpoint has been disabled for InfluxDB
|
||||
Cloud Serverless organizations. To delete data from an bucket, please
|
||||
contact InfluxData Support.
|
||||
Cloud Serverless organizations.
|
||||
Currently, you can't delete data from an InfluxDB Cloud Serverless bucket.
|
||||
|
||||
<a class="btn" href="https://support.influxdata.com">Contact InfluxData Support</a>
|
||||
To avoid querying expired or unwanted data, use tags and timestamps for filtering.
|
||||
|
||||
When writing data:
|
||||
|
||||
- [Use a new measurement name when your schema changes](/influxdb/cloud-serverless/write-data/best-practices/schema-design/#measurement-schemas-should-be-homogenous).
|
||||
- [Include a tag](/influxdb/cloud-serverless/write-data/best-practices/schema-design/#tags-versus-fields) or tags for versioning your data.
|
||||
|
||||
When querying:
|
||||
|
||||
- [Filter for tag values](/influxdb/cloud-serverless/query-data/sql/basic-query/#query-fields-based-on-tag-values) in your version tags.
|
||||
- [Use time boundaries](/influxdb/cloud-serverless/query-data/sql/basic-query/#query-data-within-time-boundaries) that exclude old data.
|
||||
|
||||
_To delete a bucket and **all** its data, use the [InfluxDB `/api/v2/buckets` API endpoint](/influxdb/cloud-serverless/api/#operation/DeleteBucketsID)._
|
||||
|
|
|
|||
|
|
@ -103,7 +103,6 @@ If you exceed your plan's [adjustable quotas or limits](/influxdb/cloud/account-
|
|||
|
||||
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/).
|
||||
- **Free plan**: To raise rate limits, [upgrade to a Usage-based Plan](#upgrade-to-usage-based-plan).
|
||||
|
||||
|
|
@ -126,5 +125,5 @@ Billing occurs on the first day of the month for the previous month. For example
|
|||
|:----------------------------|:------------------------------------------------------------------------------------------------------------------------|
|
||||
| **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.|
|
||||
| **10-14 days later** | Account completely disabled. During this period, you must contact [InfluxData Support](https://support.influxdata.com/) to process your payment and enable your account. |
|
||||
| **21 days later** | Account suspended. Contact [InfluxData Support](https://support.influxdata.com/) to settle your final bill and discuss options for resuming service.|
|
||||
|
|
|
|||
|
|
@ -33,8 +33,6 @@ Review adjustable service quotas and global limits to plan for your bandwidth ne
|
|||
|
||||
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)
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
title: Cancel your InfluxDB Cloud subscription
|
||||
description: >
|
||||
Cancel your InfluxDB Cloud account at any time by stopping all read and write
|
||||
requests, backing up data, and contacting InfluxData Support.
|
||||
requests, and backing up data.
|
||||
weight: 106
|
||||
aliases:
|
||||
- /influxdb/v2.0/account-management/offboarding
|
||||
|
|
@ -62,8 +62,6 @@ Cloud to InfluxDB OSS, see: [Migrate data from InfluxDB Cloud to InfluxDB OSS](/
|
|||
|
||||
{{% note %}}
|
||||
Cancelling your usage-based plan will delete your organization.
|
||||
However, those in multi-user organizations must contact
|
||||
[InfluxData Support](mailto:support@influxdata.com) to delete your organization.
|
||||
{{% /note %}}
|
||||
|
||||
1. Click the account name in the header of your {{< cloud-name "short" >}}
|
||||
|
|
|
|||
|
|
@ -181,4 +181,4 @@ Send a notification to PagerDuty or HTTP endpoints (other webhooks) by [upgradin
|
|||
|
||||
For InfluxDB Enterprise customers, Insights and Aware are free services that can monitor your data. InfluxDB Insights sends your data to a private Cloud account and will be monitored with the help of the support team. InfluxDB Aware is a similar service, but you monitor your data yourself.
|
||||
|
||||
To apply for this service, please contact the [InfluxData Support team](mailto:support@influxdata.com).
|
||||
To apply for this service, contact [InfluxData Support](https://support.influxdata.com/).
|
||||
|
|
|
|||
|
|
@ -31,10 +31,6 @@ To delete an organization using the **Free plan**, do the following:
|
|||
5. Provide the requested information and then select **I understand and agree to these conditions**.
|
||||
6. Click **{{< caps >}}Delete organization{{< /caps >}}**.
|
||||
|
||||
{{% note %}}
|
||||
**Note:** If you belong to multiple organizations, you will need to contact InfluxData Support via the [Support Portal](https://support.influxdata.com/) or email support@influxdata.com to have the organization deleted.
|
||||
{{% /note %}}
|
||||
|
||||
## Usage-based plan
|
||||
|
||||
1. [Export your data and cancel your subscription](/influxdb/cloud/account-management/offboarding/).
|
||||
|
|
|
|||
|
|
@ -16,10 +16,10 @@ updated_in: CLI v2.0.2
|
|||
|
||||
{{% note %}}
|
||||
#### Works with InfluxDB OSS 2.x
|
||||
|
||||
The `influx backup` command works with **InfluxDB OSS 2.x**, but does not work with **InfluxDB Cloud**.
|
||||
For information about backing up data in InfluxDB Cloud, see
|
||||
[InfluxDB Cloud durability](/influxdb/cloud/reference/internals/durability/) or
|
||||
[contact InfluxData Support](mailto:support@influxdata.com).
|
||||
[InfluxDB Cloud durability](/influxdb/cloud/reference/internals/durability/).
|
||||
{{% /note %}}
|
||||
|
||||
{{< duplicate-oss >}}
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ updated_in: CLI v2.0.7
|
|||
The `influx restore` command works with **InfluxDB OSS 2.x**, but does not work with **InfluxDB Cloud**.
|
||||
For information about restoring data in InfluxDB Cloud, see
|
||||
[InfluxDB Cloud durability](/influxdb/cloud/reference/internals/durability/) and
|
||||
[contact InfluxData Support](mailto:support@influxdata.com).
|
||||
contact [InfluxData Support](https://support.influxdata.com/).
|
||||
{{% /note %}}
|
||||
|
||||
{{< duplicate-oss >}}
|
||||
|
|
@ -14,7 +14,7 @@ alias:
|
|||
---
|
||||
|
||||
To upload a large amount **(10GB or greater)** of previously existing *historical*
|
||||
data into InfluxDB Cloud, [contact InfluxData Support](https://support.influxdata.com) for assistance.
|
||||
data into InfluxDB Cloud, contact [InfluxData Support](https://support.influxdata.com/) for assistance.
|
||||
We’ll review your ingest rate limits, volume, and existing
|
||||
[data schema](/influxdb/cloud/reference/key-concepts/data-schema) to ensure the
|
||||
most efficient migration.
|
||||
|
|
|
|||
|
|
@ -591,7 +591,9 @@ See [line protocol](/influxdb/v2.7/reference/syntax/line-protocol/).
|
|||
The part of InfluxDB's structure that describes the data stored in the associated fields.
|
||||
Measurements are strings.
|
||||
|
||||
Related entries: [field](#field), [series](#series)
|
||||
{{% cloud-only %}}With **InfluxDB v3**, a time series measurement equates to a relational database table with fields, tags, and timestamp as columns.{{% /cloud-only %}}
|
||||
|
||||
Related entries: [field](#field), [series](#series), [table](#table)
|
||||
|
||||
### member
|
||||
|
||||
|
|
@ -1071,8 +1073,14 @@ InfluxDB uses Transmission Control Protocol (TCP) port 8086 for client-server co
|
|||
|
||||
### table
|
||||
|
||||
{{% oss-only %}}
|
||||
Flux processes a series of tables for a specified time series.
|
||||
These tables in sequence result in a stream of data.
|
||||
{{% /oss-only %}}
|
||||
|
||||
{{% cloud-only %}}With **InfluxDB v3**, a time series measurement equates to a relational database table with fields, tags, and timestamp as columns.{{% /cloud-only %}}
|
||||
|
||||
Related entries: [measurement](#measurement)
|
||||
|
||||
### tag
|
||||
|
||||
|
|
|
|||
|
|
@ -58,7 +58,7 @@
|
|||
<li><a class="slack" href="https://influxdata.com/slack" target="_blank">InfluxDB Community Slack</a></li>
|
||||
</ul>
|
||||
{{ if not (in $supportBlacklist $product) }}
|
||||
<p><strong>InfluxDB Cloud{{ if eq $product "influxdb" }} and InfluxDB Enterprise{{ end }} customers</strong> can <a href="mailto:support@influxdata.com" target="_blank">contact InfluxData Support</a>.</p>
|
||||
<p><strong>Customers with an annual or support contract</strong> can <a href="https://support.influxdata.com/">contact InfluxData Support</a>.</p>
|
||||
{{ end }}
|
||||
</div>
|
||||
<div class="actions">
|
||||
|
|
|
|||
Loading…
Reference in New Issue