From 5b1296246358c91d82eb8e44953b55514972d8a6 Mon Sep 17 00:00:00 2001 From: Daniel Date: Sat, 20 Jul 2024 05:54:19 -0300 Subject: [PATCH] docs: data transfer updates --- content/docs/introduction/monitor-usage.md | 2 +- content/docs/introduction/plans.md | 2 +- content/docs/introduction/usage-metrics.md | 10 ++++++++-- content/docs/reference/glossary.md | 4 ++-- 4 files changed, 12 insertions(+), 6 deletions(-) diff --git a/content/docs/introduction/monitor-usage.md b/content/docs/introduction/monitor-usage.md index 1a10fee936..39e71362c3 100644 --- a/content/docs/introduction/monitor-usage.md +++ b/content/docs/introduction/monitor-usage.md @@ -64,7 +64,7 @@ The **Usage** widget on the Neon Dashboard shows a snapshot of project usage. Usage metrics include: - **Storage**: The total volume of data and history for your project, measured in gibibytes (GiB). Data refers to the logical data size. History consists of Write-Ahead Logging (WAL) records capturing the data’s change history that is used to enable branching-related features. -- **Data transfer**: The total volume of data transferred out of Neon (known as "egress") during the current billing period. The Free Tier has an egress limit of 5 GiB per month. +- **Data transfer**: The total volume of data transferred out of Neon (known as "egress") during the current billing period. The [Free Tier](/docs/introduction/plans#free-tier) has a data transfer limit of 5 GiB per month. - **Written data**: The total volume of data written from compute to storage during the current billing period, measured in gigibytes (GiB). - **Compute**: The total number of [compute hours](/docs/reference/glossary#compute-hours) used during the current billing period. - **Active computes**: The current number of active computes in your project. diff --git a/content/docs/introduction/plans.md b/content/docs/introduction/plans.md index 010b40f6bd..aa66f90192 100644 --- a/content/docs/introduction/plans.md +++ b/content/docs/introduction/plans.md @@ -42,7 +42,7 @@ The Free Tier includes the following usage allowances: | **Databases** | Unlimited | | **Storage** | 0.5 GiB | | **Compute** | Always-available default branch compute, 5 compute hours (20 _active hours_)/month on branch computes. Free Tier computes have 0.25 vCPU with 1GB RAM. | -| **Data Transfer (Egress)** | 5 GiB per month | +| **Data transfer (Egress)** | 5 GiB per month | diff --git a/content/docs/introduction/usage-metrics.md b/content/docs/introduction/usage-metrics.md index 57f94e899f..e0b18ffef0 100644 --- a/content/docs/introduction/usage-metrics.md +++ b/content/docs/introduction/usage-metrics.md @@ -189,9 +189,15 @@ To estimate what your compute hour usage might be per month: ## Data Transfer -Data transfer usage refers to the total volume of data transferred out of Neon (known as "egress") during a given billing period. Neon does not charge for egress data, but we do limit the amount of egress available on Free Tier projects to 5 GiB per month. The project's compute endpoint is suspended if the data transfer allowance is exceeded. Data transfer is tracked per Neon user account. +Data transfer usage refers to the total volume of data transferred out of Neon (known as "egress") during a given billing period. Neon does not charge for egress data, but we do limit the amount of egress available on Free Tier projects to 5 GiB per month. The project's compute endpoint is suspended if the data transfer allowance is exceeded, and the following error message will be reported: -For all other plans, Neon maintains a reasonable usage policy. This means there is no set limit on data transfers, but usage is expected to stay within a range typical for standard operations. If your usage significantly exceeds this expected range, Neon may reach out to discuss your pattern and possible plan adjustments. +```text shouldWrap +Your project has exceeded the data transfer quota. Upgrade your plan to increase limits. +``` + +Data transfer is tracked per Neon user account. + +For all other plans, Neon maintains a reasonable usage policy. This means there is no set limit on data transfer, but usage is expected to stay within a range typical for standard operations. If your usage significantly exceeds this expected range, Neon may reach out to discuss your usage and possible plan adjustments. ## Projects diff --git a/content/docs/reference/glossary.md b/content/docs/reference/glossary.md index 0ce61216fb..0701164a42 100644 --- a/content/docs/reference/glossary.md +++ b/content/docs/reference/glossary.md @@ -172,7 +172,7 @@ A method of storing inactive data that converts plaintext data into a coded form ## Data transfer -A usage metric that measures the total volume of data transferred out of Neon (known as "egress") during a given billing period. +A usage metric that measures the total volume of data transferred out of Neon (known as "egress") during a given billing period. Neon does not charge for egress data, but we limit the amount of egress available on Free Tier projects to 5 GiB per month. See [Data tranfser](/docs/introduction/usage-metrics#data-transfer). ## Database @@ -204,7 +204,7 @@ A string that identifies a Neon compute endpoint. Neon Endpoint IDs are generate ## Egress -The data transferred out of the Neon service to an external destination. +The data transferred out of the Neon service to an external destination. See [Data transfer](#data-transfer). ## Enterprise plan