While investigating T184942: Deprecate python varnish cachestats we've ran into the fact that maps runs on cache upload, and the ATS migration for upload has been completed, and we don't have per-backend metrics (latency, status code, etc) from ATS. Ideally we have at least the same metrics we're collecting from varnishlog + mtail available from ATS, although I don't know the specifics of what's possible.
In terms of dashboards, we're looking at replacing varnish_backend_requests and varnish_backend_timing in dashboards and possibly alerts. The latter is a subset of the former, so we should be able to rewrite _timing in terms of _requests.
varnish_backend_requests
Matched db/api-frontend-summary (API frontend summary)
Matched db/maps-performances-filippo-t184942 (Maps performances Filippo T184942)
Matched db/wikidata-query-service-frontend (Wikidata Query Service Frontend)
varnish_backend_timing
Matched db/apache-backend-timing (Apache Backend-Timing)