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 Using Scylla Monitoring Stack Scylla Monitoring Stack Advisor

Caution

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

Scylla Monitoring Stack Advisor¶

The Scylla Monitoring Stack Advisor is an element of the Scylla Monitoring Stack that recognize bad practices, bad configurations, and potential problems and advises on how to solve them.

The Advisor section¶

../../_images/advisor_panel.png

The Advisor section¶

The Advisor section is located on the Overview dashboard and consists of two parts:

On the left, is the Advisor issues table. Each issue has a category, a link to jump to a relevant dashboard, and a description of the issue.

For example, the Advisor could warn about using large cells. Large cells in the data usually indicate a problem with the data model or a problem with the client code, and can impact system performance.

On the right, is the system balance section. This section notifies you about an imbalance between shards or nodes. An imbalanced system may indicate a potential problem.

For example, when a single, hot partition gets most of the requests, making one shard a bottleneck, the balance section will indicate that the latency and cache hits are imbalanced between shards.

Each Advisor issue is explained in detail:

  • 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

  • Some queries use reverse order

  • 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

Was this page helpful?

PREVIOUS
The CQL Optimization
NEXT
Some queries use ALLOW FILTERING
  • Create an issue
  • Edit this page

On this page

  • Scylla Monitoring Stack Advisor
    • The Advisor section
ScyllaDB Monitoring
  • 3.7
    • 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
  • 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
      • Some queries use reverse order
      • 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
  • Download and Install
    • Install
    • The start-all.sh script
    • Deploy without Docker
    • Docker Compose
    • System Recommendations
    • Using Thanos
  • Procedures
    • Alert Manager
      • Alerting
    • Adding and Modifying Dashboards
    • Upgrade Guide
  • Troubleshooting
    • Troubleshooting
    • Troubleshooting Guide for Scylla Manager and Scylla Monitor Integration
  • Reference
    • Support Matrix
    • Interfaces
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