From a29a8efabb3f7d5a74a120d65002335308fc1818 Mon Sep 17 00:00:00 2001 From: KimberlyFields <46325568+KimberlyFields@users.noreply.github.com> Date: Tue, 3 Dec 2024 14:29:52 -0500 Subject: [PATCH 1/3] DOC-4819 Update metrics.adoc --- modules/ROOT/pages/metrics.adoc | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/modules/ROOT/pages/metrics.adoc b/modules/ROOT/pages/metrics.adoc index 6a06da29..f4b734f5 100644 --- a/modules/ROOT/pages/metrics.adoc +++ b/modules/ROOT/pages/metrics.adoc @@ -51,18 +51,20 @@ This is configured by the {zdm-automation} through the variable `primary_cluster ** Cache Misses: meaning, a prepared statement was sent to the {zdm-proxy}, but it wasn't on its cache, so the proxy returned an `UNPREPARED` response to make the driver send the `PREPARE` request again. ** Number of cached prepared statements. -* Request Failure Rates: number of request failures per interval. -You can set the interval via the `Error Rate interval` dashboard variable at the top. -** Read Failure Rate: one `cluster` label with two settings: `origin` and `target`. -The label that contains data depends on which cluster is currently considered the primary (same as the latency and throughput metrics explained above). -** Write Failure Rate: one `failed_on` label with three settings: `origin`, `target` and `both`. +* Request Failure Rates: the number of request failures per interval. +You can set the interval in the `Error Rate interval` dashboard variable at the top. +** Connect Failure Rate: one `cluster` label with two settings, `origin` and `target`, that represent the cluster to which the connection attempt failed. +** Read Failure Rate: one `cluster` label with two settings, `origin` and `target`. +The label that contains data depends on which cluster is currently considered the primary, the same as the latency and throughput metrics explained above. +** Write Failure Rate: one `failed_on` label with three settings, `origin`, `target` and `both`. *** `failed_on=origin`: the write request failed on Origin ONLY. *** `failed_on=target`: the write request failed on Target ONLY. *** `failed_on=both`: the write request failed on BOTH clusters. * Request Failure Counters: Number of total request failures (resets when the {zdm-proxy} instance is restarted) -** Read Failure Counters: same labels as read failure rate. -** Write Failure Counters: same labels as write failure rate. +** Connect Failure Counters: the same labels as the connect failure rate. +** Read Failure Counters: the same labels as the read failure rate. +** Write Failure Counters: the same labels as the write failure rate. To see error metrics by error type, see the node-level error metrics on the next section. From 1f9bca39a308017ebbb6e7d1c46e499bb84800e7 Mon Sep 17 00:00:00 2001 From: KimberlyFields <46325568+KimberlyFields@users.noreply.github.com> Date: Wed, 4 Dec 2024 11:55:18 -0500 Subject: [PATCH 2/3] Update modules/ROOT/pages/metrics.adoc Co-authored-by: brian-f --- modules/ROOT/pages/metrics.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/metrics.adoc b/modules/ROOT/pages/metrics.adoc index f4b734f5..14a988d5 100644 --- a/modules/ROOT/pages/metrics.adoc +++ b/modules/ROOT/pages/metrics.adoc @@ -56,7 +56,7 @@ You can set the interval in the `Error Rate interval` dashboard variable at the ** Connect Failure Rate: one `cluster` label with two settings, `origin` and `target`, that represent the cluster to which the connection attempt failed. ** Read Failure Rate: one `cluster` label with two settings, `origin` and `target`. The label that contains data depends on which cluster is currently considered the primary, the same as the latency and throughput metrics explained above. -** Write Failure Rate: one `failed_on` label with three settings, `origin`, `target` and `both`. +** Write Failure Rate: one `failed_on` label with three settings, `origin`, `target`, and `both`. *** `failed_on=origin`: the write request failed on Origin ONLY. *** `failed_on=target`: the write request failed on Target ONLY. *** `failed_on=both`: the write request failed on BOTH clusters. From 3dd5005425b066a24793077d8bdd434344388f6e Mon Sep 17 00:00:00 2001 From: KimberlyFields <46325568+KimberlyFields@users.noreply.github.com> Date: Wed, 4 Dec 2024 11:55:33 -0500 Subject: [PATCH 3/3] Update modules/ROOT/pages/metrics.adoc Co-authored-by: brian-f --- modules/ROOT/pages/metrics.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/metrics.adoc b/modules/ROOT/pages/metrics.adoc index 14a988d5..e86e6d37 100644 --- a/modules/ROOT/pages/metrics.adoc +++ b/modules/ROOT/pages/metrics.adoc @@ -53,7 +53,7 @@ This is configured by the {zdm-automation} through the variable `primary_cluster * Request Failure Rates: the number of request failures per interval. You can set the interval in the `Error Rate interval` dashboard variable at the top. -** Connect Failure Rate: one `cluster` label with two settings, `origin` and `target`, that represent the cluster to which the connection attempt failed. +** Connect Failure Rate: one `cluster` label with two settings, `origin` and `target`, which represent the cluster to which the connection attempt failed. ** Read Failure Rate: one `cluster` label with two settings, `origin` and `target`. The label that contains data depends on which cluster is currently considered the primary, the same as the latency and throughput metrics explained above. ** Write Failure Rate: one `failed_on` label with three settings, `origin`, `target`, and `both`.