I left some example command outputs using the hostname hetzner-nbg1-01
since they don't impact procedures.

service/prometheus.md

@@ -2044,7 +2044,7 @@ statistics. Here are the equivalent fields:
 
 [#41070]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/41070
 [Grafana graph showing Prometheus disk usage]: https://grafana.torproject.org/d/000000012/prometheus-2-0-stats?orgId=1&refresh=1m&viewPanel=40&from=now-1y&to=now
-[disk usage graphic]: https://grafana.torproject.org/d/zbCoGRjnz/disk-usage?orgId=1&var-class=All&var-instance=hetzner-nbg1-01.torproject.org&from=now-3d&to=now&viewPanel=2
+[disk usage graphic]: https://grafana.torproject.org/d/zbCoGRjnz/disk-usage?orgId=1&var-class=All&var-instance=prometheus-03.torproject.org&from=now-3d&to=now&viewPanel=2
 [upstream Storage documentation]: https://prometheus.io/docs/prometheus/1.8/storage/
 [advice on long-term storage]: https://prometheus.io/docs/prometheus/1.8/storage/#settings-for-very-long-retention-time
 [This guide from Alexandre Vazquez]: https://alexandre-vazquez.com/how-it-optimize-the-disk-usage-in-the-prometheus-database/
@@ -2940,7 +2940,7 @@ Prometheus stores data in its own custom "time-series database"
 
 Metrics are held for about a year or less, depending on the
 server. Look at [this dashboard for current disk usage of the
-Prometheus servers](https://grafana.torproject.org/d/zbCoGRjnz/disk-usage?orgId=1&from=now-1y&to=now&timezone=utc&var-class=$__all&var-instance=hetzner-nbg1-01.torproject.org&var-instance=hetzner-nbg1-02.torproject.org&var-Filters&refresh=auto).
+Prometheus servers](https://grafana.torproject.org/d/zbCoGRjnz/disk-usage?orgId=1&from=now-1y&to=now&timezone=utc&var-class=$__all&var-instance=hetzner-nbg1-02.torproject.org&var-instance=prometheus-03.torproject.org&var-Filters=true&refresh=auto).
 
 The actual disk usage depends on: