ScyllaDB University Live | Free Virtual Training Event
Learn more
ScyllaDB Documentation Logo Documentation
  • Server
  • Cloud
  • Tools
    • ScyllaDB Manager
    • ScyllaDB Monitoring Stack
    • ScyllaDB Operator
  • Drivers
    • CQL Drivers
    • DynamoDB Drivers
  • Resources
    • ScyllaDB University
    • Community Forum
    • Tutorials
Download
ScyllaDB Docs ScyllaDB Monitoring ScyllaDB Monitoring Stack Procedures Upgrade Scylla Monitoring Stack Upgrade Guide - Scylla Monitoring 2.x to Scylla Monitoring 3.x

Caution

You're viewing documentation for a previous version of ScyllaDB Monitoring. Switch to the latest stable version.

Upgrade Guide - Scylla Monitoring 2.x to Scylla Monitoring 3.x¶

This document is a step by step procedure for upgrading ScyllaDB Monitoring Stack from version 2.x to 3.x

Switching from Scylla Monitoring 2.x to Scylla Monitoring 3.x is not fully backward compatible. The changes affect dashboards’ names and metrics.

Upgrade Procedure¶

1. Validate node_exporter version¶

Scylla Monitoring uses the node_exporter utility to collect OS-related metrics. By default, Scylla will install node_exporter version 0.17. If you upgrade in the past from the older Scylla version (before Scylla 2.3), you should verify that you are running the correct node_exporter. You can do that by running node_exporter –version on the machines running Scylla.

If you are running an older version of node_exporter you can use the helper script node_exporter_install –force that shipped with Scylla to force upgrade.

2. Install the new monitoring stack¶

  1. Download the 3.x version from the release page.

  2. Unzip it into a different directory.

  3. Copy the targets files from the old stack to the new one, located on the prometheus/ sub-directory:

    • scylla_servers.yml (for example cp /path/to/old/monitor/prometheus/scylla_servers.yml prometheus/)

    • scylla_manager_servers.yml

    Note

    The targets files are no longer part of the release, make sure to copy them or the monitoring stack will not start.

  4. Stop the old monitoring stack

    ./kill-all.sh
    
  5. Start the new monitoring stack

    ./start-all.sh -d /prometheus-data-path
    

Validate the upgrade¶

You should be able to see the graphs on the new stack. Make sure you see the graphs’ history.

Because of the metrics, name change graphs will display correctly but with a different color as of the time of the upgrade. This is only true for the transition phase.

Rollback¶

To rollback, simply kill the new stack, change to the old monitoring stack directory, and start it.

Related Links¶

  • Upgrade

Was this page helpful?

PREVIOUS
Upgrade Guide - Scylla Monitoring 3.x to Scylla Monitoring 3.y
NEXT
Upgrade Guide - Scylla Monitoring 2.x to Scylla Monitoring 2.y
  • Create an issue
  • Edit this page

On this page

  • Upgrade Guide - Scylla Monitoring 2.x to Scylla Monitoring 3.x
    • Upgrade Procedure
      • 1. Validate node_exporter version
      • 2. Install the new monitoring stack
      • Validate the upgrade
    • Rollback
    • Related Links
ScyllaDB Monitoring
  • 4.8
    • 4.9
    • 4.8
    • 4.7
    • 4.6
    • 4.5
    • 4.4
    • 4.3
    • 4.2
    • 4.1
    • 4.0
    • 3.10
    • 3.9
    • 3.8
    • 3.7
    • 3.6
    • 3.5
  • Introduction
  • Download and Install
    • Install
    • The start-all.sh script
    • Deploy without Docker
    • Docker Compose
    • System Recommendations
    • Using Thanos
  • User Guide
    • CQL Optimization Dashboard
    • Advisor
      • Some queries use ALLOW FILTERING
      • Some queries use Consistency Level: ALL
      • Some queries use Consistency Level: ANY
      • Some queries are not token-aware
      • Some SELECT queries are non-paged
      • Some queries are non-prepared
      • Compaction takes lots of memory and CPU
      • Some operation failed due to unsatisfied consistency level
      • I/O Errors can indicate a node with a faulty disk
      • Some operations failed on the replica side
      • CQL queries are not balanced among shards
      • Prepared statements cache eviction
      • System Overload
  • Procedures
    • Cloud Users Datadog integration
    • Datadog Integration
    • Alert Manager
      • Alerting
    • Adding and Modifying Dashboards
    • Upgrade Guides
      • Monitoring 4.x to 4.y
      • Monitoring 3.x to 4.y
      • Monitoring 3.x to 3.y
      • Monitoring 2.x to 3.y
      • Monitoring 2.x to 2.y
      • Monitoring 1.x to 2.x
  • Upgrade
    • Monitoring 4.x to 4.y
    • Monitoring 3.x to 4.y
    • Monitoring 3.x to 3.y
    • Monitoring 2.x to 3.y
    • Monitoring 2.x to 2.y
    • Monitoring 1.x to 2.x
  • Troubleshooting
    • Troubleshooting
    • Troubleshooting Guide for Scylla Manager and Scylla Monitor Integration
  • Reference
    • Support Matrix
    • Interfaces
  • GitHub Project
Docs Tutorials University Contact Us About Us
© 2025, ScyllaDB. All rights reserved. | Terms of Service | Privacy Policy | ScyllaDB, and ScyllaDB Cloud, are registered trademarks of ScyllaDB, Inc.
Last updated on 04 May 2025.
Powered by Sphinx 7.4.7 & ScyllaDB Theme 1.8.6