[RELEASE] ScyllaDB Monitoring Stack 4.6.0

Release Notes
,
1

The ScyllaDB team is pleased to announce the release of ScyllaDB Monitoring Stack 4.6.0

ScyllaDB Monitoring Stack is an open-source stack for monitoring ScyllaDB Enterprise and ScyllaDB Open Source, based on Prometheus and Grafana. ScyllaDB Monitoring Stack 4.6.0 supports:

  • ScyllaDB Open Source versions 5.0, 5.1, 5.2, and 5.4.
  • ScyllaDB Enterprise versions 2022.x, 2023.1 and the upcoming 2024.1 release
  • ScyllaDB Manager 3.0.x, 3.1.x, 3.2.x

Related Links

Versions updates for ScyllaDB Monitoring Stack 4.6.0

  • Prometheus upgraded to version 2.48.1
  • Grafana upgraded to version 10.2.2

New Information in ScyllaDB Dashboards

Overview Dashboard Change

  • Added a description to the ‘Timeouts’ panel, timeouts are now both reads and writes #2056

Detailed Dashboard Change

  • Added a section that shows all priority groups on the same graph #2121

1600×417 103 KB

CQL Dashboard Change

  • Added a “CQL Connections creation rate” graph #2053

  • Added logged/unlogged batches graphs #2081

1441×290 102 KB

Per-Table Dashboard Change

  • Added cache hit rate, total disk space, live disk space, and live SSTable per table #285

1600×216 49.3 KB

Bug Fixes

  • The By-Instance filter is broken on Grafana 10.2.2 #2138
  • “Request Shed” is supposed to be in the “Coordinator” section #2124
  • Request/Response payload sizes units are wrong #2083
  • CPU and memory panels are not clear #2141

Operational Changes

  • support IPv6 without specifying ports #2136
  • Prometheus 2.48 fails to start when running the container as root and using external directory #2134
  • Experimental - Use compose to start the monitoring stack #2123
  • You can override the default node_exporter ports when specifying the ports number in a file #2092

Deprecation warning

There was a long inconsistency when adding ports to the Prometheus target files, which
is now resolved.

Most users use the default port numbers for: ScyllaDB, node_exporter, and ScyllaDB manager agents and only use one target file. If that is your case, you do not need to change anything.

Scylla Monitoring will take the port numbers from the files if the files are set explicitly and contain ports.

For example, if you are specifying explicitly the node_exporter file (the -n flag to start-all.sh), you should ensure there are only IPs in the file with no ports or that you are using the correct node_exporter port number (by default, 9100).

So, if you just copy the scylla_servers file and use that with the ScyllaDB ports, it would no longer work.

$ cat node_exporter_servers.yml

  • labels:

cluster: my-cluster

dc: datacenter1

targets:

  • 172.17.0.8:9180 # Remove or change the ports part in your target

Important Note

Most likely, you can use a single target file for scylla_server and do not need to explicitly add a node_exporter or ScyllaDB manager agent file.

IPv6 Users

IPv6 users no longer need to add port numbers to the target files. It is recommended to use a single file (do not explicitly set the node_exporter file) without ports.