From 509936a60bf2c3d9fcecf69aa463406e2298e155 Mon Sep 17 00:00:00 2001 From: Rachel Elledge <86307637+rrelledge@users.noreply.github.com> Date: Thu, 2 Jan 2025 16:04:51 -0600 Subject: [PATCH 1/3] DOC-4594 Mention Prometheus v1 metrics issues resolved by v2 in release notes (#1017) Signed-off-by: NAM UK KIM --- .../release-notes/rs-7-8-releases/rs-7-8-2-34.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/content/operate/rs/release-notes/rs-7-8-releases/rs-7-8-2-34.md b/content/operate/rs/release-notes/rs-7-8-releases/rs-7-8-2-34.md index 64b0049195..094c9c0203 100644 --- a/content/operate/rs/release-notes/rs-7-8-releases/rs-7-8-2-34.md +++ b/content/operate/rs/release-notes/rs-7-8-releases/rs-7-8-2-34.md @@ -83,6 +83,22 @@ This version offers: - V1 Prometheus metrics are deprecated but still available. To transition to the new metrics stream engine, either migrate your existing dashboards using [Prometheus v1 metrics and equivalent v2 PromQL]({{}}) now, or wait to use new preconfigured dashboards when they become available in a future release. + - The new metrics stream engine resolved some known issues and bugs: + + - RS31923: Added missing types to Prometheus metrics. + + - RS80626: Added DMC thread utilization metrics to the metrics exporter. + + - RS113028: Upgraded the node exporter dependency to version 1.7.0. + + - RS103537: Fixed an issue with missing indications when a node went down. You can see the node's metrics up until it went down and can monitor `node_metrics_up` to get an indication that it is down. + + - RS103251: Metrics are now available during state machine operations. + + - RS74732: Fixed an issue where a replica CRDB's stats were missing after removing and then re-adding the replica CRDB instance. + + - RS65948: Fixed an issue where the metrics exporter generated duplicate stats headers when the cluster had both regular databases and Active-Active databases. + - [Rebalance shard placement REST API request]({{}}), which distributes the database's shards across nodes based on the database's shard placement policy. See [Shard placement policy]({{}}) for more information about shard placement and available policies. - [Shard failover REST API requests]({{}}), which perform failover on specified primary shards and promotes their replicas to primary shards. From 2358b74f4940290b2e05f9faa2e61797d436406e Mon Sep 17 00:00:00 2001 From: NAM UK KIM Date: Sat, 4 Jan 2025 01:02:34 +0900 Subject: [PATCH 2/3] Update quick-start.md Signed-off-by: NAM UK KIM --- content/operate/kubernetes/deployment/quick-start.md | 1 + 1 file changed, 1 insertion(+) diff --git a/content/operate/kubernetes/deployment/quick-start.md b/content/operate/kubernetes/deployment/quick-start.md index c3686b86d5..681ec095c2 100644 --- a/content/operate/kubernetes/deployment/quick-start.md +++ b/content/operate/kubernetes/deployment/quick-start.md @@ -27,6 +27,7 @@ To deploy Redis Enterprise for Kubernetes, you'll need: - minimum of three worker nodes - Kubernetes client (kubectl) - access to DockerHub, RedHat Container Catalog, or a private repository that can hold the required images. +NOTE: If you are applying version 7.8.2-6 or above, check if the [OS](https://redis.io/docs/latest/operate/kubernetes/release-notes/7-8-2-releases/7-8-2-6-nov24/#breaking-changes) installed on the node is supported. ### Create a new namespace From 78415eedbccabc33de75ee4207d547a672979896 Mon Sep 17 00:00:00 2001 From: NAM UK KIM Date: Sun, 18 May 2025 08:32:12 +0900 Subject: [PATCH 3/3] Update acl.md Signed-off-by: NAM UK KIM --- content/operate/oss_and_stack/management/security/acl.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/content/operate/oss_and_stack/management/security/acl.md b/content/operate/oss_and_stack/management/security/acl.md index 75c6a8a81f..c4aa3e2372 100644 --- a/content/operate/oss_and_stack/management/security/acl.md +++ b/content/operate/oss_and_stack/management/security/acl.md @@ -304,7 +304,7 @@ The following is a list of command categories and their meanings: * **json** - Data type: all JSON related commands. * **keyspace** - Writing or reading from keys, databases, or their metadata in a type agnostic way. Includes [`DEL`](/commands/del), [`RESTORE`](/commands/restore), [`DUMP`](/commands/dump), [`RENAME`](/commands/rename), [`EXISTS`](/commands/exists), [`DBSIZE`](/commands/dbsize), - [`KEYS`](/commands/keys), [`EXPIRE`](/commands/expire), [`TTL`](/commands/ttl), [`FLUSHALL`](/commands/flushall), etc. Commands that may modify the keyspace, + [`KEYS`](/commands/keys), [`SCAN`](/commands/scan), [`EXPIRE`](/commands/expire), [`TTL`](/commands/ttl), [`FLUSHALL`](/commands/flushall), etc. Commands that may modify the keyspace, key, or metadata will also have the `write` category. Commands that only read the keyspace, key, or metadata will have the `read` category. * **list** - Data type: all list related commands. @@ -323,7 +323,8 @@ The following is a list of command categories and their meanings: * **transaction** - [`WATCH`](/commands/watch) / [`MULTI`](/commands/multi) / [`EXEC`](/commands/exec) related commands. * **write** - Writing to keys (values or metadata). Note that commands that don't interact with keys, will not have either `read` or `write`. -Redis can also show you a list of all categories and the exact commands each category includes using the Redis [`ACL CAT`](/commands/acl-cat) command. It can be used in two forms: +NOTE: Redis can also show you a list of all categories and the exact commands each category includes using the Redis [`ACL CAT`](/commands/acl-cat) command. +It can be used in two forms: ACL CAT -- Will just list all the categories available ACL CAT -- Will list all the commands inside the category