You want to understand satellite obstruction with the following PromQL that shows a measure of obstruction in 12 30-degree wedges around Dishy. Monitor starlink connection: Troubleshooting Metrics
#GRAFANA INTERNET UPTIME MONITOR HOW TO#
Want to dig deeper into PromQL? Read our getting started with PromQL guide to learn how Prometheus stores data, and how to use PromQL functions and operators. Sum by (cause) (sum_over_time(starlink_dish_outage_duration))
Use this PromQL query if you are interested in understanding the cause of outages you can use the following PromQL to review all outages over the past 24 hours: Monitor starlink connection: Stability Metrics You can also quickly see the latency between Starlink Dishy, Satellite, and Ground Station by using starlink_dish_pop_ping_latency_seconds. You can review metrics for throughput utilization by using the following: starlink_dish_downlink_throughput_bytes and starlink_dish_uplink_throughput_bytes. Now that both containers are running, you can access Prometheus ( and look at the available metrics coming from Starlink Dishy ( Monitor starlink connection: Performance Metrics Monitor starlink connection with Prometheus dashboards Now, from the same directory as your docker-compose.yml and prometheus.yml, you can launch the containers with the following command: '-config.file=/etc/prometheus/prometheus.yml' prometheus.yml:/etc/prometheus/prometheus.yml Image: sysdigdan/starlink_exporter:v0.1.3 Next, launch the Prometheus and Starlink Exporter containers using Docker Compose and the following YAML (save this as docker-compose.yml in the same location as your prometheus.yml above): Scrape_timeout: 10s # By default, it is set to the global default (10s). Scrape_interval: 10s # By default, scrape targets every 15 seconds.Įvaluation_interval: 10s # By default, scrape targets every 15 seconds. Create a prometheus folder and add the configuration file prometheus.yml as seen below: In this example, you’ll monitor starlink connection using the Starlink Exporter to talk to Starlink Dishy via gRPC, and expose metrics in a format Prometheus will understand.Ĭonfigure Prometheus and Launching Containersįirst, you need to configure Prometheus to scrape the Starlink Exporter.
If you are using the Starlink Wi-Fi router this should be reachable by default. The Starlink Dishy is contactable at 192.168.100.1 on port 9200 for gRPC. Also, we sent a PR to the exporter maintainers To monitor starlink connection, we decided to fork the Starlink Prometheus Exporter project and create a PR that updates the Starlink gRPC bindings using the latest Starlink firmware to provide some additional metrics from Starlink Dishy. We encourage you to look at his other project Starlink Monitoring System if you are interested in a pre-packaged solution. There are several great projects available from the open-source community, but the one we settled on using for the basis of our project was the Starlink Prometheus Exporter from Daniel Willcocks.
Currently, there are around 1,800 Starlink satellites in orbit. It’s also expected that there will be brief periods of no connectivity at all. During the beta, Starlink expects users to see data speeds vary from 50Mb/s to 150Mb/s and latency from 20ms to 40ms. SpaceX’s Starlink uses satellites in low-earth orbit to provide high-speed Internet services to most of the planet. In this article, you’ll learn how Starlink works in a domestic environment, and how to monitor Starlink connection with Prometheus. Security and visibility for cloud applications