Change monitoring->observability

A lot of our metrics-related docs are labeled as
"monitoring" which is a bit misleading even though
that's what Google calls it.

IMHO "observability" is a good overall name to
indicate how a user can observe their deployment
generally, and we can specific sections around
enabling logs, metrics, (or WAF logs in the
future).

Author: puneetsarna

content/includes/nginxaas-google/logging-config-access-logs.md

@@ -1,7 +1,7 @@
 ---
 f5-product: NGOOGL
 f5-files:
-- content/nginxaas-google/monitoring/enable-nginx-logs.md
+- content/nginxaas-google/observability/enable-logs.md
 ---
 
 NGINX access logs are disabled by default. You can enable access logs by adding **access_log** directives to your NGINX configuration to specify the location of the logs and formats. The log path should always be configured to be inside **/var/log/nginx**.

content/includes/nginxaas-google/logging-config-error-logs.md

@@ -1,7 +1,7 @@
 ---
 f5-product: NGOOGL
 f5-files:
-- content/nginxaas-google/monitoring/enable-nginx-logs.md
+- content/nginxaas-google/observability/enable-logs.md
 ---
 
 NGINX error logs are disabled by default. You can enable error logs by adding **error_log** directives to your NGINX configuration to specify the location of the logs and formats. The log path should always be configured to be inside **/var/log/nginx**.

content/nginxaas-google/getting-started/access-management.md

@@ -113,5 +113,5 @@ In the NGINXaaS Console,
 
 ## What's next
 
-- [Monitor your deployment]({{< ref "/nginxaas-google/monitoring/enable-monitoring.md" >}})
-- [Enable NGINX Logs]({{< ref "/nginxaas-google/monitoring/enable-nginx-logs.md" >}})
+- [Monitor your deployment]({{< ref "/nginxaas-google/observability/enable-metrics.md" >}})
+- [Enable NGINX Logs]({{< ref "/nginxaas-google/observability/enable-logs.md" >}})

content/nginxaas-google/getting-started/create-deployment/deploy-console.md

@@ -64,7 +64,7 @@ Next, create a new NGINXaaS deployment using the NGINXaaS Console:
    - Select a **Configuration Version** from the list.
    - In the Cloud Details section, enter the network attachment ID that [you created earlier](#create-a-network-attachment) or select it in the  **Network attachment** list.
       - The network attachment ID is formatted like the following example: `projects/my-google-project/regions/us-east1/networkAttachments/my-network-attachment`.
-   - Select **Managed Public Endpoint** or **Private Endpoint** under Service Frontend. 
+   - Select **Managed Public Endpoint** or **Private Endpoint** under Service Frontend.
       - Refer to the [Service Frontend]({{< ref "/nginxaas-google/overview.md#service-frontend" >}}) documentation for more information on these two frontend types.
    - Select **Submit** to begin the deployment process.
 
@@ -79,15 +79,15 @@ In the NGINXaaS Console,
 1. To open the details of your deployment, select its name from the list of deployments.
    - You can view the details of your deployment, including the status, region, network attachment, NGINX configuration, and more.
 1. Select **Edit** to modify the deployment description, and NCU Capacity.
-   - You can also configure monitoring from here. Detailed instructions can be found in [Enable Monitoring]({{< ref "/nginxaas-google/monitoring/enable-monitoring.md" >}})
+   - You can also configure monitoring from here. Detailed instructions can be found in [Enable Monitoring]({{< ref "/nginxaas-google/observability/enable-metrics.md" >}})
 1. Select **Update** to save your changes.
 1. Select the Configuration tab to view the current NGINX configuration associated with the deployment.
 1. Select **Update Configuration** to change the NGINX configuration associated with the deployment.
 1. To modify the contents of the NGINX configuration, see [Update an NGINX Configuration]({{< ref "/nginxaas-google/getting-started/nginx-configuration/nginx-configuration-console.md#update-an-nginx-configuration" >}}).
 
 ## Set up connectivity (Private Endpoint only)
 
-If you selected **Private Endpoint** as the service frontend type, complete the following steps to allow client access. If you selected **Managed Public Endpoint**, skip this section.**
+If you selected service frontend of type **Managed Public Endpoint**, skip this section.** If you selected **Private Endpoint** as the service frontend type, complete the following steps to allow client access.
 
 ### Internal traffic
 

content/nginxaas-google/getting-started/nginx-configuration/nginx-configuration-console.md

@@ -34,4 +34,4 @@ You can apply an NGINX configuration to your F5 NGINXaaS for Google Cloud (NGINX
 1. Confirm that you want to delete the configuration.
 
 ## What's next
-[Monitor your deployment]({{< ref "/nginxaas-google/monitoring/enable-monitoring.md" >}})
+[Monitor your deployment]({{< ref "/nginxaas-google/observability/enable-metrics.md" >}})

content/nginxaas-google/monitoring/_index.md

@@ -0,0 +1,5 @@
+---
+title: Observability
+weight: 300
+url: /nginxaas/google/observability/
+---

content/nginxaas-google/observability/_index.md

@@ -1,9 +1,9 @@
 ---
-title: Enable NGINX logs
+title: Enable Logs
 weight: 350
 toc: true
 f5-docs: DOCS-000
-url: /nginxaas/google/monitoring/enable-nginx-logs/
+url: /nginxaas/google/observability/enable-logs/
 f5-content-type: how-to
 f5-product: NGOOGL
 ---

…s-google/monitoring/enable-nginx-logs.md …xaas-google/observability/enable-logs.mdcontent/nginxaas-google/monitoring/enable-nginx-logs.md renamed to content/nginxaas-google/observability/enable-logs.md content/nginxaas-google/monitoring/enable-nginx-logs.md renamed to content/nginxaas-google/observability/enable-logs.md

@@ -1,9 +1,9 @@
 ---
-title: Enable monitoring
+title: Enable Metrics
 weight: 200
 toc: true
 f5-docs: DOCS-000
-url: /nginxaas/google/monitoring/enable-monitoring/
+url: /nginxaas/google/observability/enable-metrics/
 f5-content-type: how-to
 f5-product: NGOOGL
 ---
@@ -17,9 +17,9 @@ Monitoring your application's performance is crucial for maintaining its reliabi
 - Grant your principal access to one of the following IAM roles depending on your needs:
   - `roles/monitoring.viewer` — View metrics in Cloud Monitoring (read-only access)
   - `roles/monitoring.editor` — View metrics and create or import dashboards
-  
+
   See [Google's documentation on controlling access to Cloud Monitoring with IAM](https://cloud.google.com/monitoring/access-control) for more information.
-- Configure the [`status_zone`](https://nginx.org/en/docs/http/ngx_http_status_module.html#status_zone) directive in your `server` blocks and the [`zone`](https://nginx.org/en/docs/http/ngx_http_upstream_module.html#zone) directive in your `upstream` blocks to collect HTTP request and response statistics, stream connection metrics, upstream statistics, and memory statistics. See the [Metrics Catalog]({{< ref "/nginxaas-google/monitoring/metrics-catalog.md" >}}) for configuration requirements.
+- Configure the [`status_zone`](https://nginx.org/en/docs/http/ngx_http_status_module.html#status_zone) directive in your `server` blocks and the [`zone`](https://nginx.org/en/docs/http/ngx_http_upstream_module.html#zone) directive in your `upstream` blocks to collect HTTP request and response statistics, stream connection metrics, upstream statistics, and memory statistics. See the [Metrics Catalog]({{< ref "/nginxaas-google/observability/metrics-catalog.md" >}}) for configuration requirements.
 
 ## Export NGINXaaS metrics to a Google Cloud Project
 
@@ -32,7 +32,7 @@ To enable sending metrics to your desired Google Cloud project, you must specify
 
 ## View NGINXaaS metrics in Google Cloud Monitoring
 
-See the [Metrics Catalog]({{< ref "/nginxaas-google/monitoring/metrics-catalog.md" >}}) for a full list of metrics NGINXaaS provides.
+See the [Metrics Catalog]({{< ref "/nginxaas-google/observability/metrics-catalog.md" >}}) for a full list of metrics NGINXaaS provides.
 
 ### Google Cloud Console's Metrics Explorer
 

…s-google/monitoring/enable-monitoring.md …s-google/observability/enable-metrics.mdcontent/nginxaas-google/monitoring/enable-monitoring.md renamed to content/nginxaas-google/observability/enable-metrics.md content/nginxaas-google/monitoring/enable-monitoring.md renamed to content/nginxaas-google/observability/enable-metrics.md

@@ -3,7 +3,7 @@ title: Metrics catalog
 weight: 400
 toc: false
 f5-docs: DOCS-000
-url: /nginxaas/google/monitoring/metrics-catalog/
+url: /nginxaas/google/observability/metrics-catalog/
 f5-content-type: reference
 f5-product: NGOOGL
 ---
@@ -19,7 +19,7 @@ F5 NGINXaaS for Google Cloud (NGINXaaS) provides a rich set of metrics that you
   - [NGINX requests and response statistics](#nginx-requests-and-response-statistics)
   - [NGINX SSL statistics](#nginx-ssl-statistics)
   - [NGINX cache statistics](#nginx-cache-statistics)
-  - [NGINX worker statistics](#nginx-worker-statistics)
+  - [NGINX memory statistics](#nginx-memory-statistics)
   - [NGINX upstream statistics](#nginx-upstream-statistics)
   - [NGINX stream statistics](#nginx-stream-statistics)
 
@@ -63,7 +63,7 @@ Example:
 server {
     listen 80;
     status_zone my_server_zone;
-    
+
     location / {
         proxy_pass http://backend;
     }
@@ -119,7 +119,7 @@ Example:
 ```nginx
 http {
     proxy_cache_path /var/cache/nginx levels=1:2 keys_zone=my_cache:10m;
-    
+
     server {
         location / {
             proxy_cache my_cache;
@@ -215,7 +215,7 @@ stream {
         status_zone tcp_server;
         proxy_pass backend_stream;
     }
-    
+
     upstream backend_stream {
         zone stream_backend 64k;
         server 10.0.0.1:12345;