From dec0c62effc1c5fdeda8de37744b9401e4ebcdc0 Mon Sep 17 00:00:00 2001 From: Paulin Todev Date: Mon, 2 Dec 2024 20:21:46 +0000 Subject: [PATCH] Update docs/sources/reference/http/_index.md Co-authored-by: Clayton Cornell <131809008+clayton-cornell@users.noreply.github.com> --- docs/sources/reference/http/_index.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/sources/reference/http/_index.md b/docs/sources/reference/http/_index.md index 374e0e0386..7ed2ac1fe1 100644 --- a/docs/sources/reference/http/_index.md +++ b/docs/sources/reference/http/_index.md @@ -44,12 +44,12 @@ unhealthy components: math.add ``` {{< admonition type="note" >}} -The `/-/healthy` endpoint is not suitable for a [Kubernetes liveness probe][k8s-liveness]. +The `/-/healthy` endpoint isn't suitable for a [Kubernetes liveness probe][k8s-liveness]. -An Alloy instance which reports as unhealthy should not necessarily be restarted. -For example, a component may be unhealthy due to invalid configuration or due to an unavailable external resource. +An {{< param "PRODUCT_NAME" >}} instance that reports as unhealthy should not necessarily be restarted. +For example, a component may be unhealthy due to an invalid configuration or an unavailable external resource. In this case, restarting {{< param "PRODUCT_NAME" >}} would not fix the problem. -A restart may even make it worse, because it would could stop the flow of telemetry in healthy pipelines. +A restart may make it worse, because it would could stop the flow of telemetry in healthy pipelines. [k8s-liveness]: https://kubernetes.io/docs/concepts/configuration/liveness-readiness-startup-probes/ {{< /admonition >}}