Has anyone else’s Grafana Cloud Fly dashboard(s) stopped working when trying to open/load (note: if the dashboard is already loaded in your browser it’s probably working ok)? and are you able to to Explore your Fly Prometheus source(s) from Grafana Cloud?
Putting aside the specifics of the dashboard problem, where is seems to fail to fetch the region/host/app details, I’ve also noticed that Explore doesn’t appear to work ("! Unexpected Error") .
As far as I’m aware my (Fly) Prometheus sources haven’t changed within Grafana Cloud and have been working well for quite some time. Another existing (not the Fly) dashboard I have in Grafana Cloud using a Fly Prometheus source is also working ok.
kurt - are you able to Explore your Fly Prometheus source(s) from within Grafana Cloud? and also, are you loading your Dashboard(s) afresh (e.g. new tab) as opposed to looking at a Dashboard(s) that you already have open (which I suspect are still ok)?
Try this one? That buildinfo path is not supported in VictoriaMetrics (what we use under the covers). It’s normal for that to error. This should return something though:
That’s the path to the first error. Grafana is showing a 401, though, which is what you get when you’re not authenticated. Can you try re-inputing your auth token in the Grafana source?
Just did. The metrics and my dashboards work but the query builder & explorer doesn’t work (same error). So the auth token works for scraping the metrics but not for the other endpoints?
Not sure if related, but I stopped getting metrics from AMS and SJC at 9:20am PT today although the instances are still healthy and serving traffic. My project’s other region (HKG) is still getting metrics in Grafana. I have a separate project in AMS (same organization) that still has metrics.
Edit: fly restart fixed it, but a bit worrisome that metrics just stopped from some instances.
Having now reverse proxied the Grafana Cloud>Fly API Prometheus requests, I believe I can see the problem… Grafana Cloud does send the authorization: header when clicking Save & Test on the Prometheus source. It doesn’t however send the authorization: header when fetching the list of Metrics with Explore (and as a result Fly responds with a HTTP 401).
If, on the reverse proxy, I force the authorization: Bearer <fly auth token> into the requests - it then works (HTTP 200 from Fly).
With no knowledge of what is “normal” for Prometheus requests (i.e. are some available without authentication?) I don’t know if a request (without the authorization: header) for:
GET /prometheus/<orgname>/api/v1/rules
Would normally be responded to with a HTTP 200.
If Prometheus requests, or at least some paths, are usually allowed (or have previously been allowed by Fly, i.e. prior to late last week) - without an authorization: header - then this may be resolvable by Fly.
If however authorization: has always been required by Fly for all Prometheus paths - then I can only assume Grafana Cloud have made a breaking change .