From 3d312c3ecd2d4ef222f66a4a09196537039690d2 Mon Sep 17 00:00:00 2001 From: Brian Ehlert Date: Wed, 18 Jan 2023 13:29:16 -0800 Subject: [PATCH 1/2] clarify deep service insight --- .../logging-and-monitoring/service-insight.md | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/docs/content/logging-and-monitoring/service-insight.md b/docs/content/logging-and-monitoring/service-insight.md index 9073e633b1..5867c9363c 100644 --- a/docs/content/logging-and-monitoring/service-insight.md +++ b/docs/content/logging-and-monitoring/service-insight.md @@ -11,14 +11,16 @@ docs: "DOCS-000" --- -The Ingress Controller exposes an endpoint and provides host statistics for Virtual Servers (VS) and Transport Servers (TS). +The Ingress Controller exposes an endpoint and provides host statistics for services exposed using the VirtualServer (VS) and TransportServer (TS) resource objects. It exposes data in JSON format and returns HTTP status codes. The response body holds information about the total, down and the unhealthy number of -upstreams associated with the hostname. -Returned HTTP codes indicate the health of the upstreams (service). +upstream pods associated with the configured hostname. +Returned HTTP codes indicate the health of the service. -The service is not healthy (HTTP response code different than 200 OK) if all upstreams are unhealthy. -The service is healthy if at least one upstream is healthy. In this case, the endpoint returns HTTP code 200 OK. +The service is indicated as not healthy (HTTP response code different than 200 OK) if all upstreams (pods) are determined unhealthy by NGINX Plus. +The service is healthy if at least one upstream pod is healthy as determined by NGINX Plus. In this case, the endpoint returns HTTP code 200 OK. + +NGINX Plus determination of healthy can be tuned using advanced health checks, and also dynamically relate to pods responses and responsiveness. See Upstream Healthcheck https://docs.nginx.com/nginx-ingress-controller/configuration/virtualserver-and-virtualserverroute-resources/#upstream ## Enabling Service Insight Endpoint @@ -39,9 +41,9 @@ If you're using *Helm* to install the Ingress Controller, to enable Service Insi The Service Insight provides the following statistics: -* Total number of VS and TS -* Number of VS and TS in 'Up' state -* Number of VS and TS in 'Unhealthy' state +* Total number of VS or TS pods +* Number of VS or TS pods in 'Up' state +* Number of VS or TS pods in 'Unhealthy' state These statistics are returned as JSON: From 9f2eaef1992f857818a2661b27c141302f9ade41 Mon Sep 17 00:00:00 2001 From: "pre-commit-ci[bot]" <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Wed, 18 Jan 2023 21:31:46 +0000 Subject: [PATCH 2/2] [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci --- docs/content/logging-and-monitoring/service-insight.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/logging-and-monitoring/service-insight.md b/docs/content/logging-and-monitoring/service-insight.md index 5867c9363c..d75dbcb618 100644 --- a/docs/content/logging-and-monitoring/service-insight.md +++ b/docs/content/logging-and-monitoring/service-insight.md @@ -20,7 +20,7 @@ Returned HTTP codes indicate the health of the service. The service is indicated as not healthy (HTTP response code different than 200 OK) if all upstreams (pods) are determined unhealthy by NGINX Plus. The service is healthy if at least one upstream pod is healthy as determined by NGINX Plus. In this case, the endpoint returns HTTP code 200 OK. -NGINX Plus determination of healthy can be tuned using advanced health checks, and also dynamically relate to pods responses and responsiveness. See Upstream Healthcheck https://docs.nginx.com/nginx-ingress-controller/configuration/virtualserver-and-virtualserverroute-resources/#upstream +NGINX Plus determination of healthy can be tuned using advanced health checks, and also dynamically relate to pods responses and responsiveness. See Upstream Healthcheck https://docs.nginx.com/nginx-ingress-controller/configuration/virtualserver-and-virtualserverroute-resources/#upstream ## Enabling Service Insight Endpoint