Skip to content

[redis_enterprise_prometheus] Fix dashboard queries and collect two missing metrics #3193

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
slorello89 wants to merge 2 commits into
base: master
Choose a base branch
from
Open

[redis_enterprise_prometheus] Fix dashboard queries and collect two missing metrics #3193

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1a2e8d9
Fix redis_enterprise_prometheus dashboard queries and collect two mis…
slorello89 Aug 26, 2026
9c24d1f
Merge branch 'master' into redis-enterprise-prometheus-dashboard-metr…
slorello89 Sep 1, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions redis_enterprise_prometheus/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,23 @@
# CHANGELOG - Redis Enterprise Prometheus

## 1.2.0 / 2026-08-26

***Added***:

* Collect `rdse2.node_uname_info` and `rdse2.node_config`. Both were already documented in `metadata.csv` but were missing from the check's metric map, so they were never emitted. `node_uname_info` carries the per-node `nodename` label (the internal hostname) and `node_config` carries `rs_version`. [#3136](https://github.com/DataDog/integrations-extras/pull/3136)

***Fixed***:

* Point the Database List widgets at `rdse2.db_config` instead of `rdse2.database_syncer_config`. The latter is a configuration-label placeholder that only exists on Active-Active deployments and lives in the opt-in `REDIS2.REPLICATION` group, so the widget was empty on a default install. [#3136](https://github.com/DataDog/integrations-extras/pull/3136)
* Add the missing `.count` suffix to the `rdse2.endpoint_ingress` / `rdse2.endpoint_egress` queries in the Database Input/Output widget. These are Prometheus counters, which the OpenMetrics v2 check emits as `.count`. [#3136](https://github.com/DataDog/integrations-extras/pull/3136)
* Compute current connections from the `.total` gauges and subtract `rdse2.endpoint_proxy_disconnections.total`, rather than differencing two monotonic `.count` deltas. [#3136](https://github.com/DataDog/integrations-extras/pull/3136)
* Stop dividing by time twice in the Database Input/Output, Shard Process CPU, and Proxy Threads CLI Session widgets, which wrapped an already-rated (`.as_rate()`) query in `per_second()` / `derivative()`. [#3136](https://github.com/DataDog/integrations-extras/pull/3136)
* Un-swap the ingress and egress series labels (and the accompanying note text) in the Database Input/Output widget. [#3136](https://github.com/DataDog/integrations-extras/pull/3136)
* Rebuild the Node Latency widget as a calculated field over the `endpoint_*_requests_latency_histogram` sum/count pairs. It previously queried `rdse.node_avg_latency`, a V1-only metric under the wrong namespace. [#3136](https://github.com/DataDog/integrations-extras/pull/3136)
* Group the Cluster Nodes widget by `nodename` from `rdse2.node_uname_info` instead of the non-existent `internal-hostname` tag. [#3136](https://github.com/DataDog/integrations-extras/pull/3136)
* Remove the Node Network Traffic widget; both `rdse.node_egress_bytes_median` and `rdse.node_ingress_bytes_median` are V1-only metrics with no V2 equivalent. [#3136](https://github.com/DataDog/integrations-extras/pull/3136)
* Remove `title` from `note` widgets, folding it into the note content as a markdown heading. The Dashboards API rejects `title` on notes, which made the dashboard assets fail to import. [#3136](https://github.com/DataDog/integrations-extras/pull/3136)

## 1.1.0 / 2026-07-29

***Deprecated***:
Expand Down
3 changes: 1 addition & 2 deletions redis_enterprise_prometheus/assets/dashboards/redis_enterprise-prometheus_active-active.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -231,8 +231,7 @@
"id": 6950044907570933,
"definition": {
"type": "note",
"title": "About This Active Active Dashboard",
"content": "The Redis Enterprise Shard Dashboard is used to visualize metrics at the shard level. In Redis Enterprise Software, the shard is the lowest single level of abstraction tracked by metrics. Key metrics such as memory usage, connection count, cpu utilization are all tracked by this dashboard.\n \nPlease note, in order to view the metrics in this dashboard you must enable `REDIS2.REPLICATION` in the `extra_metrics` section of the integration configuration.",
"content": "## About This Active Active Dashboard\n\nThe Redis Enterprise Shard Dashboard is used to visualize metrics at the shard level. In Redis Enterprise Software, the shard is the lowest single level of abstraction tracked by metrics. Key metrics such as memory usage, connection count, cpu utilization are all tracked by this dashboard.\n \nPlease note, in order to view the metrics in this dashboard you must enable `REDIS2.REPLICATION` in the `extra_metrics` section of the integration configuration.",
"background_color": "white",
"font_size": "14",
"text_align": "left",
Expand Down
18 changes: 12 additions & 6 deletions redis_enterprise_prometheus/assets/dashboards/redis_enterprise-prometheus_database.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,8 +15,7 @@
"id": 6906627780487202,
"definition": {
"type": "note",
"title": "About The Database Dashboard",
"content": "The Database dashboard provides a visualization of metrics at the Redis Enterprise database level. In Redis Enterprise, a database is an abstraction over a collection of Redis Shards fronted by a single endpoint (or several when using the OSS cluster API). Key metrics such as memory usage, connections and latency are observable at the Database level.",
"content": "## About The Database Dashboard\n\nThe Database dashboard provides a visualization of metrics at the Redis Enterprise database level. In Redis Enterprise, a database is an abstraction over a collection of Redis Shards fronted by a single endpoint (or several when using the OSS cluster API). Key metrics such as memory usage, connections and latency are observable at the Database level.",
"background_color": "vivid_purple",
"font_size": "16",
"text_align": "left",
Expand Down Expand Up @@ -120,7 +119,7 @@
{
"data_source": "metrics",
"name": "query1",
"query": "avg:rdse2.database_syncer_config{*} by {cluster,db_name,db}",
"query": "avg:rdse2.db_config{*} by {cluster,db_name,db}",
"aggregator": "avg"
}
],
Expand Down Expand Up @@ -285,19 +284,26 @@
{
"data_source": "metrics",
"name": "query1",
"query": "sum:rdse2.endpoint_client_connections{$cluster,$database}",
"query": "sum:rdse2.endpoint_client_connections.total{$cluster,$database}",
"aggregator": "last"
},
{
"data_source": "metrics",
"name": "query2",
"query": "sum:rdse2.endpoint_client_disconnections{$cluster,$database}",
"query": "sum:rdse2.endpoint_client_disconnections.total{$cluster,$database}",
"aggregator": "last"
},
{
"data_source": "metrics",
"name": "query3",
"query": "sum:rdse2.endpoint_proxy_disconnections.total{$cluster,$database}",
"aggregator": "last"
}
],
"formulas": [
{
"formula": "query1 - query2"
"formula": "query1 - query2 - query3",
"alias": "current connections"
}
]
}
Expand Down
110 changes: 43 additions & 67 deletions redis_enterprise_prometheus/assets/dashboards/redis_enterprise-prometheus_node.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,8 +15,7 @@
"id": 6906627780487202,
"definition": {
"type": "note",
"title": "About The Node Dashboard",
"content": "This Dashboard provides visualization of metrics at the Redis Enterprise Node level. In Redis Enterprise, a node is a single server with the Redis Enterprise Software installed on it. Memory usage, cpu usage, as well as key shard details per node are all visualized in the Node dashboard.",
"content": "## About The Node Dashboard\n\nThis Dashboard provides visualization of metrics at the Redis Enterprise Node level. In Redis Enterprise, a node is a single server with the Redis Enterprise Software installed on it. Memory usage, cpu usage, as well as key shard details per node are all visualized in the Node dashboard.",
"background_color": "vivid_purple",
"font_size": "16",
"text_align": "left",
Expand Down Expand Up @@ -115,7 +114,7 @@
{
"data_source": "metrics",
"name": "query1",
"query": "avg:rdse2.node_os_info{$cluster, $node} by {internal-hostname,node}",
"query": "avg:rdse2.node_uname_info{$cluster, $node} by {node,nodename}",
"aggregator": "avg"
}
],
Expand Down Expand Up @@ -207,24 +206,58 @@
"title": "Node Latency",
"title_size": "16",
"title_align": "left",
"time": {
"hide_incomplete_cost_data": true
},
"type": "query_value",
"requests": [
{
"response_format": "scalar",
"queries": [
{
"data_source": "metrics",
"aggregator": "sum",
"name": "query1",
"query": "avg:rdse.node_avg_latency{$cluster, $node}",
"aggregator": "avg"
"query": "sum:rdse2.endpoint_read_requests_latency_histogram.sum{$cluster, $node}.as_rate()"
},
{
"data_source": "metrics",
"aggregator": "sum",
"name": "query2",
"query": "sum:rdse2.endpoint_read_requests_latency_histogram.count{$cluster, $node}.as_rate()"
},
{
"data_source": "metrics",
"aggregator": "sum",
"name": "query3",
"query": "sum:rdse2.endpoint_write_requests_latency_histogram.sum{$cluster, $node}.as_rate()"
},
{
"data_source": "metrics",
"aggregator": "sum",
"name": "query4",
"query": "sum:rdse2.endpoint_write_requests_latency_histogram.count{$cluster, $node}.as_rate()"
},
{
"data_source": "metrics",
"aggregator": "sum",
"name": "query5",
"query": "sum:rdse2.endpoint_other_requests_latency_histogram.sum{$cluster, $node}.as_rate()"
},
{
"data_source": "metrics",
"aggregator": "sum",
"name": "query6",
"query": "sum:rdse2.endpoint_other_requests_latency_histogram.count{$cluster, $node}.as_rate()"
}
],
"formulas": [
{
"formula": "query1"
"formula": "(query1 + query3 + query5) / (query2 + query4 + query6) / 1000",
"alias": "avg latency",
"number_format": {
"unit": {
"type": "canonical_unit",
"unit_name": "millisecond"
}
}
}
]
}
Expand Down Expand Up @@ -709,63 +742,6 @@
"type": "group",
"layout_type": "ordered",
"widgets": [
{
"id": 7788477609382880,
"definition": {
"title": "Node Network Traffic",
"title_size": "16",
"title_align": "left",
"show_legend": true,
"legend_layout": "auto",
"legend_columns": [
"avg",
"min",
"max",
"value",
"sum"
],
"type": "timeseries",
"requests": [
{
"formulas": [
{
"alias": "egress",
"formula": "query1"
},
{
"alias": "ingress",
"formula": "query2"
}
],
"queries": [
{
"data_source": "metrics",
"name": "query1",
"query": "avg:rdse.node_egress_bytes_median{$cluster, $node}"
},
{
"data_source": "metrics",
"name": "query2",
"query": "avg:rdse.node_ingress_bytes_median{$cluster, $node}"
}
],
"response_format": "timeseries",
"style": {
"palette": "blue",
"line_type": "solid",
"line_width": "normal"
},
"display_type": "line"
}
]
},
"layout": {
"x": 0,
"y": 0,
"width": 12,
"height": 4
}
},
{
"id": 4265268039928674,
"definition": {
Expand Down Expand Up @@ -1000,4 +976,4 @@
"layout_type": "ordered",
"notify_list": [],
"reflow_type": "fixed"
}
}
Loading
Loading