Skip to content

Commit cc6e992

Browse files
puneetsarnapuneetsarna
committed
Update docs to point towards Standard V2
Now that we have the Standard plan officially retired, we should update our docs with the same information and point users to migrate over to it.
1 parent 6ad874d commit cc6e992

File tree

6 files changed

+25
-26
lines changed

6 files changed

+25
-26
lines changed

Diff for: ‎content/nginxaas-azure/billing/overview.md

-9
Original file line numberDiff line numberDiff line change
@@ -33,15 +33,6 @@ The SKU for the Basic pricing plan is `basic_Monthly`.
3333
{{< note >}}The costs for your plan will appear on the Azure Portal Cost Analysis page and the Azure Consumption APIs. There may be a 24h delay before usage is visible.{{< /note >}}
3434

3535

36-
### Standard plan (deprecated)
37-
38-
The Standard plan is comparable to the Standard V2 plan except that it doesn't support some features like NGINX App Protect WAF.
39-
40-
The SKU to use for the Standard pricing plan is `standard_Monthly`.
41-
42-
{{< note >}} Standard plan is now deprecated in favor of Standard V2 plan.{{< /note >}}
43-
44-
4536
## NGINX Capacity Unit (NCU)
4637

4738
{{< include "/nginxaas-azure/ncu-description.md" >}}

Diff for: ‎content/nginxaas-azure/changelog.md

+6
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,12 @@ To see a list of currently active issues, visit the [Known issues]({{< relref "/
1111

1212
To review older entries, visit the [Changelog archive]({{< relref "/nginxaas-azure/changelog-archive" >}}) section.
1313

14+
## March 5, 2025
15+
16+
- {{% icon-info %}} **Retirement of Standard Plan**
17+
18+
The `Standard` plan for NGINXaaS for Azure has been retired, and users cannot create new deployments with it anymore. If you have a deployment running on the `Standard` plan, consider [migrating]({{< relref "/nginxaas-azure/troubleshooting/migrate-from-standard.md">}}) it to the [`Standard V2 plan`]({{< relref "/nginxaas-azure/billing/overview.md#standard-v2-plan" >}}) without incurring downtime, and to access new features such as NGINX App Protect WAF and additional listen ports.
19+
1420
## February 10, 2025
1521

1622
- {{% icon-feature %}} **NGINXaaS Load Balancer for Kubernetes is now Generally Available**

Diff for: ‎content/nginxaas-azure/getting-started/nginx-configuration/overview.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ Some directives cannot be overridden by the user provided configuration.
6262
|------------------ | ----------------------- | -----------------|
6363
| `user` | `nginx` | The `nginx` user has the correct permissions for accessing certificates, policy files and other auxfiles. |
6464
| `worker_processes` | `auto` | Set to `auto` to automatically set `worker_processes` to the number of CPU cores. |
65-
| `worker_connections` | <ul><li>standard plan `4000`</li><li>basic plan `3000`</li></ul> | To ensure reasonable performance of the NGINXaaS deployment for standard plan the `worker_connections` is fixed at 400/NCU; for basic plan this is set lower. |
65+
| `worker_connections` | <ul><li>Standard V2 plan `4000`</li><li>basic plan `3000`</li></ul> | To ensure reasonable performance of the NGINXaaS deployment for Standard V2 plan, the `worker_connections` is fixed at 400/NCU; for basic plan this is set lower. |
6666
| `pid` | `/run/nginx/nginx.pid` | Set to this value to allow NGINXaaS to automatically manage the NGINX master process. |
6767
| `daemon` | `on` | Automatically set to `on` to allow NGINXaaS to manage the NGINX master process. |
6868
| `master_process` | `on` | This directive is intended for NGINX developers. |

Diff for: ‎content/nginxaas-azure/monitoring/metrics-catalog.md

+15-13
Original file line numberDiff line numberDiff line change
@@ -11,16 +11,18 @@ F5 NGINX as a Service for Azure (NGINXaaS) provides a rich set of metrics that y
1111

1212
## Available metrics
1313

14-
- [NGINXaaS Statistics](#nginxaas-statistics)
15-
- [NGINX connections statistics](#nginx-connections-statistics)
16-
- [NGINX requests and response statistics](#nginx-requests-and-response-statistics)
17-
- [NGINX SSL Statistics](#nginx-ssl-statistics)
18-
- [NGINX Cache Statistics](#nginx-cache-statistics)
19-
- [NGINX Worker Statistics](#nginx-worker-statistics)
20-
- [NGINX Upstream Statistics](#nginx-upstream-statistics)
21-
- [NGINX System Statistics](#nginx-system-statistics)
22-
- [NGINX Stream Statistics](#nginx-stream-statistics)
23-
- [NGINX Resolver Statistics](#nginx-resolver-statistics)
14+
- [Available metrics](#available-metrics)
15+
- [Metrics](#metrics)
16+
- [NGINXaaS statistics](#nginxaas-statistics)
17+
- [NGINX connections statistics](#nginx-connections-statistics)
18+
- [NGINX requests and response statistics](#nginx-requests-and-response-statistics)
19+
- [NGINX SSL statistics](#nginx-ssl-statistics)
20+
- [NGINX cache statistics](#nginx-cache-statistics)
21+
- [NGINX worker statistics](#nginx-worker-statistics)
22+
- [NGINX upstream statistics](#nginx-upstream-statistics)
23+
- [NGINX system statistics](#nginx-system-statistics)
24+
- [NGINX stream statistics](#nginx-stream-statistics)
25+
- [NGINX resolver statistics](#nginx-resolver-statistics)
2426

2527
## Metrics
2628

@@ -33,9 +35,9 @@ The metrics are categorized by the namespace used in Azure Monitor. The dimensio
3335

3436
| **Metric** | **Dimensions** | **Type** | **Description** | **Roll-up per** |
3537
| --------------------- | -------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- |
36-
| ncu.provisioned | | count | The number of successfully provisioned NCUs during the aggregation interval. During scaling events, this may lag behind `ncu.requested` as the system works to achieve the request. Available for Standard plan deployments. | deployment |
37-
| ncu.requested | | count | The requested number of NCUs during the aggregation interval. Describes the goal state of the system. Available for Standard plan deployments. | deployment |
38-
| ncu.consumed | | count | The estimated number of NCUs used to handle the current traffic. This may burst above the `ncu.provisioned`. This can be used to guide scaling out or in to match your workload. See [Scaling Guidance]({{< relref "/nginxaas-azure/quickstart/scaling.md#iterative-approach" >}}) for details. Available for Standard plan deployments. | deployment |
38+
| ncu.provisioned | | count | The number of successfully provisioned NCUs during the aggregation interval. During scaling events, this may lag behind `ncu.requested` as the system works to achieve the request. Available for Standard V2 plan deployments. | deployment |
39+
| ncu.requested | | count | The requested number of NCUs during the aggregation interval. Describes the goal state of the system. Available for Standard V2 plan deployments. | deployment |
40+
| ncu.consumed | | count | The estimated number of NCUs used to handle the current traffic. This may burst above the `ncu.provisioned`. This can be used to guide scaling out or in to match your workload. See [Scaling Guidance]({{< relref "/nginxaas-azure/quickstart/scaling.md#iterative-approach" >}}) for details. Available for Standard V2 plan deployments. | deployment |
3941
| system.worker_connections | pid process_name | count | The number of nginx worker connections used on the dataplane. This metric is one of the factors which determines the deployment's consumed NCU value. | deployment |
4042
| nginxaas.certificates | name status | count | The number of certificates added to the NGINXaaS deployment dimensioned by the name of the certificate and its status. Refer to [Certificate Health]({{< relref "/nginxaas-azure/getting-started/ssl-tls-certificates/overview.md#monitor-certificates" >}}) to learn more about the status dimension. | deployment |
4143
| nginxaas.maxmind | status | count | The status of any MaxMind license in use for downloading geoip2 databases. Refer to [License Health]({{< relref "/nginxaas-azure/quickstart/geoip2.md#monitoring" >}}) to learn more about the status dimension. | deployment |

Diff for: ‎content/nginxaas-azure/overview/overview.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ NGINXaaS for Azure is supported in the following regions:
4646

4747
### Redundancy
4848

49-
With the Standard Plan, NGINXaaS uses the following redundancy features to keep your service available.
49+
With the Standard V2 Plan, NGINXaaS uses the following redundancy features to keep your service available.
5050

5151
- We run _at least_ two NGINX Plus instances for each deployment in an active-active pattern
5252
- NGINX Plus is constantly monitored for health. Any unhealthy instances are replaced with new ones

Diff for: ‎content/nginxaas-azure/quickstart/scaling.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ url: /nginxaas/azure/quickstart/scaling/
99

1010
F5 NGINX as a Service for Azure (NGINXaaS) supports manual and automatic scaling of your deployment, allowing you to adapt to application traffic demands while controlling cost.
1111

12-
{{<note>}}Scaling requires the Standard plan.{{</note>}}
12+
{{<note>}}Scaling requires the Standard V2 plan.{{</note>}}
1313

1414
An NGINXaaS deployment can be scaled out to increase the capacity (increasing the cost) or scaled in to decrease the capacity (reducing the cost). Capacity is measured in [NGINX Capacity Units (NCU)](#nginx-capacity-unit-ncu).
1515

@@ -65,7 +65,7 @@ The following table outlines constraints on the specified capacity based on the
6565
{{<bootstrap-table "table table-striped table-bordered">}}
6666
| **Marketplace Plan** | **Minimum Capacity (NCUs)** | **Maximum Capacity (NCUs)** | **Multiple of** |
6767
|------------------------------|-----------------------------|-----------------------------|----------------------------|
68-
| Standard | 10 | 500 | 10 |
68+
| Standard V2 | 10 | 500 | 10 |
6969
{{</bootstrap-table>}}
7070

7171
{{< note >}}If you need a higher maximum capacity, please [open a request](https://my.f5.com/manage/s/) and specify the Resource ID of your NGINXaaS deployment, the region, and the desired maximum capacity you wish to scale to.{{< /note >}}

0 commit comments

Comments
 (0)