Edit Observability guide

Close #39572


(cherry picked from commit 36ef8f7ca3b45c5a13b511c4402656011e791153)

Signed-off-by: AndyMunro <amunro@redhat.com>
This commit is contained in:
andymunro 2025-05-09 09:41:41 -04:00 committed by GitHub
parent e6c08fc8ba
commit bd7dcad940
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 2 additions and 2 deletions

View File

@ -6,7 +6,7 @@ title="Visualizing activities in dashboards"
summary="Install the {project_name} Grafana dashboards to visualize the metrics that capture the status and activities of your deployment.">
{project_name} provides metrics to observe what is happening inside the deployment.
To understand how metrics evolve over time, it is helpful to collect them and visualize in graphs.
To understand how metrics evolve over time, it is helpful to collect and visualize them in graphs.
This guide provides instructions on how to visualize collected {project_name} metrics in a running Grafana instance.

View File

@ -179,6 +179,6 @@ You can filter out the required traces in your tracing backend based on their ta
{project_name} Operator automatically sets the `KC_TRACING_SERVICE_NAME` and `KC_TRACING_RESOURCE_ATTRIBUTES` environment variables for each {project_name} container included in pods it manages.
NOTE: The `KC_TRACING_RESOURCE_ATTRIBUTES` variable always contains (if not overridden) the `k8s.namespace.name` attribute representing current namespace.
NOTE: The `KC_TRACING_RESOURCE_ATTRIBUTES` variable always contains (if not overridden) the `k8s.namespace.name` attribute representing the current namespace.
</@tmpl.guide>