# ScyllaDB Monitoring has no data in the charts **URL:** https://forum.scylladb.com/t/scylladb-monitoring-has-no-data-in-the-charts/54 **Category:** Knowledge Base **Created:** [November 7, 2022, 10:17am UTC](https://forum.scylladb.com/t/scylladb-monitoring-has-no-data-in-the-charts/54 "2022-11-07T10:17:05Z") **Posts on this page:** 1 **Page:** 1
### Author: ![Guy](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/guy/32/9_2.png) [@Guy](https://forum.scylladb.com/u/Guy) #### Post date: [November 7, 2022, 10:17am UTC](https://forum.scylladb.com/t/scylladb-monitoring-has-no-data-in-the-charts/54/1 "2022-11-07T10:17:05Z")
The most common reason for seeing no data about your cluster after installing the [ScyllaDB Monitoring](https://monitoring.docs.scylladb.com/) stack is an issue with the connection to Prometheus. To check this: 1. Login to the Prometheus console by pointing your browser to http://{ip}:9090, where {ip} is the Prometheus IP address. 2. Go to the target tabs: http://{ip}:9090/targets and see if any of the targets are down and if there are any error messages. Other things to check: - Make sure you are not using the local network for the local IP range when using Docker containers. By default, the local IP range (127.0.0.X) is inside the Docker container. If you are trying to connect to a target via the local IP range from a Docker container, you need to use the -l flag to enable the local network stack. - Verify that Prometheus is pointing to the correct target by checking prometheus/scylla\_servers.yml. - Make sure that your dashboard and Scylla versions are aligned. If, for example, you are running Scylla 5.1, you can specify a specific version with the -v flag when starting the monitoring stack: ./start-all.sh -v 5.1 Additional Resources: - The [ScyllaDB Monitoring stack](https://monitoring.docs.scylladb.com/stable/) on ScyllaDB Docs - [ScyllaDB Monitoring lesson](https://university.scylladb.com/courses/scylla-operations/lessons/scylla-monitoring/) on ScyllaDB University