mirror of
https://github.com/keycloak/keycloak.git
synced 2026-01-10 15:32:05 -03:30
Update observability metrics guides to reference single and multi-cluster architectures
Closes #41938 Signed-off-by: Ryan Emerson <remerson@ibm.com>
This commit is contained in:
parent
dd7ad5b866
commit
cd42a503d2
@ -20,9 +20,9 @@ include::../partials/concepts/perf_recommendations.adoc[]
|
||||
<#include "/high-availability/partials/concepts/perf_measuring_running_instance.adoc" />
|
||||
|
||||
[#multi-cluster-single-site-calculation]
|
||||
=== Calculation example (single site)
|
||||
=== Calculation example (single cluster)
|
||||
|
||||
include::../partials/concepts/perf_single_site_calculation.adoc[]
|
||||
include::../partials/concepts/perf_single_cluster_calculation.adoc[]
|
||||
|
||||
=== Sizing a multi cluster setup
|
||||
|
||||
|
||||
@ -22,7 +22,7 @@ Follow these steps to remove a site from the load balancer so that no traffic ca
|
||||
+
|
||||
<#include "/high-availability/partials/accelerator/nlb-arn.adoc" />
|
||||
+
|
||||
. Update the Accelerator EndpointGroup to only include a single site
|
||||
. Update the Accelerator EndpointGroup to only include a single cluster
|
||||
+
|
||||
<#include "/high-availability/partials/accelerator/endpoint-group.adoc" />
|
||||
+
|
||||
|
||||
@ -20,8 +20,8 @@ include::../partials/concepts/perf_recommendations.adoc[]
|
||||
<#include "/high-availability/partials/concepts/perf_measuring_running_instance.adoc" />
|
||||
|
||||
[#single-cluster-single-site-calculation]
|
||||
=== Calculation example (single site)
|
||||
=== Calculation example (single cluster)
|
||||
|
||||
include::../partials/concepts/perf_single_site_calculation.adoc[]
|
||||
include::../partials/concepts/perf_single_cluster_calculation.adoc[]
|
||||
|
||||
</@tmpl.guide>
|
||||
|
||||
@ -17,8 +17,8 @@ tileVisible="false"
|
||||
Deploying multiple {project_name} nodes allows the load to be distributed amongst them, but this requires communication between the nodes.
|
||||
This section describes metrics that are useful for monitoring the communication between {project_name} in order to identify possible faults.
|
||||
|
||||
NOTE: This is relevant only for single site deployments.
|
||||
When multiple sites are used, as described in <@links.ha id="introduction"/>, {project_name} nodes are not clustered together and therefore there is no communication between them directly.
|
||||
NOTE: This is relevant only for single cluster deployments.
|
||||
When multiple clusters are used, as described in <@links.ha id="multi-cluster-introduction"/>, {project_name} nodes are not clustered together and therefore there is no communication between them directly.
|
||||
|
||||
include::partials/jgrp_metrics.adoc[leveloffset=+1]
|
||||
|
||||
|
||||
@ -17,6 +17,6 @@ include::partials/ispn_metrics.adoc[leveloffset=+1]
|
||||
|
||||
== Next steps
|
||||
|
||||
Return back to the <@links.observability id="metrics-for-troubleshooting"/> or proceed to <@links.observability id="metrics-for-troubleshooting-external-infinispan-multi-site"/>.
|
||||
Return back to the <@links.observability id="metrics-for-troubleshooting"/> or proceed to <@links.observability id="metrics-for-troubleshooting-external-infinispan-multi-cluster"/>.
|
||||
|
||||
</@tmpl.guide>
|
||||
@ -82,7 +82,7 @@ include::partials/histogram_note_http.adoc[]
|
||||
|
||||
Return back to the <@links.observability id="metrics-for-troubleshooting"/> or,
|
||||
|
||||
* For single site deployments proceed to <@links.observability id="metrics-for-troubleshooting-clustering-and-network"/>,
|
||||
* and for multiple sites deployments proceed to <@links.observability id="metrics-for-troubleshooting-embedded-caches-multi-site"/>
|
||||
* For single cluster deployments proceed to <@links.observability id="metrics-for-troubleshooting-clustering-and-network"/>,
|
||||
* and for multi cluster deployments proceed to <@links.observability id="metrics-for-troubleshooting-embedded-caches-multi-cluster"/>
|
||||
|
||||
</@tmpl.guide>
|
||||
|
||||
@ -50,11 +50,11 @@ Grafana dashboards for the metrics below can be found in <@links.observability i
|
||||
* <@links.observability id="metrics-for-troubleshooting-jvm"/>
|
||||
* <@links.observability id="metrics-for-troubleshooting-database"/>
|
||||
* <@links.observability id="metrics-for-troubleshooting-http"/>
|
||||
* Single site metrics (without external {jdgserver_name})
|
||||
* <@links.ha id="single-cluster-introduction" /> metrics
|
||||
** <@links.observability id="metrics-for-troubleshooting-clustering-and-network"/>
|
||||
** <@links.observability id="metrics-for-troubleshooting-embedded-caches"/>
|
||||
* Multiple sites metrics (as described in <@links.ha id="introduction"/>)
|
||||
** <@links.observability id="metrics-for-troubleshooting-embedded-caches-multi-site"/>
|
||||
** <@links.observability id="metrics-for-troubleshooting-external-infinispan-multi-site"/>
|
||||
* <@links.ha id="multi-cluster-introduction" /> metrics
|
||||
** <@links.observability id="metrics-for-troubleshooting-embedded-caches-multi-cluster"/>
|
||||
** <@links.observability id="metrics-for-troubleshooting-external-infinispan-multi-cluster"/>
|
||||
|
||||
</@tmpl.guide>
|
||||
|
||||
@ -9,8 +9,8 @@ metrics-for-troubleshooting-database
|
||||
metrics-for-troubleshooting-http
|
||||
metrics-for-troubleshooting-clustering-and-network
|
||||
metrics-for-troubleshooting-embedded-caches
|
||||
metrics-for-troubleshooting-embedded-caches-multi-site
|
||||
metrics-for-troubleshooting-external-infinispan-multi-site
|
||||
metrics-for-troubleshooting-embedded-caches-multi-cluster
|
||||
metrics-for-troubleshooting-external-infinispan-multi-cluster
|
||||
tracing
|
||||
grafana-dashboards
|
||||
exemplars
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user