May 28 updates part 3

Author: mjang

content/includes/use-cases/monitoring/n1c-dashboard-overview.md

@@ -0,0 +1,39 @@
+---
+docs:
+files:
+  - content/nginx-one/metrics/enable-metrics.md
+  - content/nginx-one/getting-started.md
+---
+
+Navigating the dashboard:
+
+- **Drill down into specifics**: For in-depth information on a specific metric, like expiring certificates, click on the relevant link in the metric's card to go to a detailed overview page.
+- **Refine metric timeframe**: Metrics show the last hour's data by default. To view data from a different period, select the time interval you want from the drop-down menu.
+
+<span style="display: inline-block; margin-top: 20px; margin-bottom: 50px;">
+{{< img src="nginx-one/images/nginx-one-dashboard.png">}}
+</span>
+
+{{<bootstrap-table "table table-striped table-bordered">}}
+**NGINX One dashboard metrics**
+| Metric | Description | Details |
+|---|---|---|
+| <i class="fas fa-heartbeat"></i> **Instance availability** | Understand the operational status of your NGINX instances. | - **Online**: The NGINX instance is actively connected and functioning properly. <br> - **Offline**: NGINX Agent is connected but the NGINX instance isn't running, isn't installed, or can't communicate with NGINX Agent. <br> - **Unavailable**: The connection between NGINX Agent and NGINX One has been lost or the instance has been decommissioned. <br> - **Unknown**: The current state can't be determined at the moment. |
+| <i class="fas fa-code-branch"></i> **NGINX versions by instance** | See which NGINX versions are in use across your instances. | |
+| <i class="fas fa-desktop"></i> **Operating systems** | Find out which operating systems your instances are running on. | |
+| <i class="fas fa-certificate"></i> **Certificates** | Monitor the status of your SSL certificates to know which are expiring soon and which are still valid. | |
+| <i class="fas fa-cogs"></i> **Config recommendations** | Get configuration recommendations to optimize your instances' settings. | |
+| <i class="fas fa-shield-alt"></i> **CVEs (Common Vulnerabilities and Exposures)** | Evaluate the severity and number of potential security threats in your instances. | - **Major**: Indicates a high-severity threat that needs immediate attention. <br> - **Medium**: Implies a moderate threat level. <br> - **Minor** and **Low**: Represent less critical issues that still require monitoring. <br> - **Other**: Encompasses any threats that don't fit the standard categories. |
+| <i class="fas fa-microchip"></i> **CPU utilization** | Track CPU usage trends and pinpoint instances with high CPU demand. | |
+| <i class="fas fa-memory"></i> **Memory utilization** | Watch memory usage patterns to identify instances using significant memory. | |
+| <i class="fas fa-hdd"></i> **Disk space utilization** | Monitor how much disk space your instances are using and identify those nearing capacity. | |
+| <i class="fas fa-exclamation-triangle"></i> **Unsuccessful response codes** | Look for instances with a high number of HTTP server errors and investigate their error codes. | |
+| <i class="fas fa-tachometer-alt"></i> **Top network usage** | Review the network usage and bandwidth consumption of your instances. | |
+
+{{</bootstrap-table>}}
+
+
+
+
+
+

content/nginx-one/getting-started.md

@@ -24,12 +24,10 @@ To get started using NGINX One, enable the service on F5 Distributed Cloud.
 
 Next, add your NGINX instances to NGINX One. You'll need to create a data plane key and then install NGINX Agent on each instance you want to monitor.
 
-### Add an instance
-
-Depending on whether this is your first time using NGINX One Console or you've used it before, follow the appropriate steps to add an instance:
+The following instructions include minimal information, sufficient to "get started." See the following links for detailed instructions:
 
-- **For first-time users:** On the welcome screen, select **Add Instance**.
-- **For returning users:** If you've added instances previously and want to add more, select **Instances** on the left menu, then select **Add Instance**.
+- [Create and manage data plane keys]({{< ref "nginx-one/connect-instances/data-plane-keys/create-manage-data-plane-keys.md" >}})
+- [Add an NGINX instance]({{< ref "nginx-one/nginx-configs/add-instance.md" >}})
 
 ### Generate a data plane key {#generate-data-plane-key}
 
@@ -48,6 +46,13 @@ Data plane keys expire after one year. You can change this expiration date later
 [Revoking a data plane key]({{< ref "nginx-one/connect-instances/data-plane-keys/create-manage-data-plane-keys.md#revoke-data-plane-key" >}}) disconnects all instances that were registered with that key.
 {{</call-out>}}
 
+### Add an instance
+
+Depending on whether this is your first time using NGINX One Console or you've used it before, follow the appropriate steps to add an instance:
+
+- **For first-time users:** On the welcome screen, select **Add Instance**.
+- **For returning users:** If you've added instances previously and want to add more, select **Instances** on the left menu, then select **Add Instance**.
+
 
 ### Install NGINX Agent
 
@@ -134,37 +139,11 @@ If you followed the [Installation and upgrade](https://docs.nginx.com/nginx-agen
 
 ---
 
-## Enable NGINX metrics reporting
-
 The NGINX One Console dashboard relies on APIs for NGINX Plus and NGINX Open Source Stub Status to report traffic and system metrics. The following sections show you how to enable those metrics.
 
 ### Enable NGINX Plus API
 
-<!-- possible future include: "/use-cases/monitoring/enable-nginx-plus-api.md" -->
-To collect metrics for NGINX Plus, add the following to your NGINX Plus configuration file:
-
-```nginx
-# Enable the /api/ location with appropriate access control
-# to use the NGINX Plus API.
-#
-location /api/ {
-    api write=on;
-    allow 127.0.0.1;
-    deny all;
-}
-```
-
-This configuration:
-
-- Enables the NGINX Plus API.
-- Allows requests only from `127.0.0.1` (localhost).
-- Blocks all other requests for security.
-
-After saving the changes, reload NGINX to apply the new configuration:
-
-```shell
-nginx -s reload
-```
+{{< include "/use-cases/monitoring/enable-nginx-plus-api.md" >}}
 
 ### Enable NGINX Open Source Stub Status API
 
@@ -183,6 +162,8 @@ After connecting your NGINX instances to NGINX One, you can monitor their perfor
 
 ### Overview of the NGINX One dashboard
 
+{{< include "/use-cases/monitoring/n1c-dashboard-overview.md" >}}
+
 Navigating the dashboard:
 
 - **Drill down into specifics**: For in-depth information on a specific metric, like expiring certificates, click on the relevant link in the metric's card to go to a detailed overview page.

content/nginx-one/metrics/_index.md

@@ -0,0 +1,6 @@
+---
+description:
+title: Set up metrics
+weight: 300
+url: /nginx-one/metrics/
+---

content/nginx-one/metrics/enable-metrics.md

@@ -0,0 +1,23 @@
+---
+# We use sentence case and present imperative tone
+title: "Enable metrics"
+# Weights are assigned in increments of 100: determines sorting order
+weight: i00
+# Creates a table of contents and sidebar, useful for large documents
+toc: true
+# Types have a 1:1 relationship with Hugo archetypes, so you shouldn't need to change this
+nd-content-type: tutorial
+# Intended for internal catalogue and search, case sensitive:
+# Agent, N4Azure, NIC, NIM, NGF, NAP-DOS, NAP-WAF, NGINX One, NGINX+, Solutions, Unit
+nd-product: NGINX One
+---
+
+The NGINX One Console dashboard relies on APIs for NGINX Plus and NGINX Open Source Stub Status to report traffic and system metrics. The following sections show you how to enable those metrics.
+
+### Enable NGINX Plus API
+
+{{< include "/use-cases/monitoring/enable-nginx-plus-api.md" >}}
+
+### Enable NGINX Open Source Stub Status API 
+
+{{< include "/use-cases/monitoring/enable-nginx-oss-stub-status.md" >}}

content/nginx-one/metrics/review-metrics.md

@@ -0,0 +1,23 @@
+---
+# We use sentence case and present imperative tone
+title: "Review metrics on the NGINX One dashboard"
+# Weights are assigned in increments of 100: determines sorting order
+weight: i00
+# Creates a table of contents and sidebar, useful for large documents
+toc: true
+# Types have a 1:1 relationship with Hugo archetypes, so you shouldn't need to change this
+nd-content-type: how-to
+# Intended for internal catalogue and search, case sensitive:
+# Agent, N4Azure, NIC, NIM, NGF, NAP-DOS, NAP-WAF, NGINX One, NGINX+, Solutions, Unit
+nd-product: NGINX One
+---
+
+After connecting your NGINX instances to NGINX One, you can monitor their performance and health. The NGINX One dashboard is designed for this purpose, offering an easy-to-use interface.
+
+### Log in to NGINX One
+
+1. Log in to [F5 Distributed Console](https://www.f5.com/cloud/products/distributed-cloud-console).
+1. Select **NGINX One > Visit Service**.
+
+{{< include "/use-cases/monitoring/n1c-dashboard-overview.md" >}}
+

layouts/partials/list-main.html

@@ -58,6 +58,9 @@ <h3 class="card-title" style="display: flex; align-items: center; gap: 5px;">
                             {{ if and (eq $PageTitle "F5 NGINX One Console") (eq .Title "Connect your instances to the console") }}
                                 <p style="padding-bottom: 10px;">Work with data plane keys, containers, and proxy servers </p> 
                             {{ end }}
+                            {{ if and (eq $PageTitle "F5 NGINX One Console") (eq .Title "Set up metrics") }}
+                                <p style="padding-bottom: 10px;">Review your deployments in a dashboard </p> 
+                            {{ end }}
                             {{ if and (eq $PageTitle "F5 NGINX One Console") (eq .Title "API")}}
                                 <p style="padding-bottom: 10px;">These are API docs</p> <!-- Added text here -->
                                 <ul style="padding-top: 10px;">