Google Cloud Managed Service for Prometheus

[DazWilkin]

In order for PromLens to work with Google Cloud Managed Service for Prometheus (GMP), (Prometheus) API requests must be authenticated (and the identity must be authorized).

I hacked together a basic proxy (promlens-gmp-token-proxy) that should¹ be run on same host as PromLens, functions as a proxy including adding an Authorization header to PromLens requests to authenticate to GMP.

There's an explanation here: Authenticating PromLens to Google Managed Prometheus

¹ -- For simplicity the proxy provides a non-TLS (!) HTTP endpoint to PromLens even though it uses TLS to make requests to GMP.

[holmesb]

Hi @DazWilkin, not sure if you wrote this and your blog prior to Google creating\documenting their own frontend proxy? Pointing PromLens at URL of frontend proxy (which has authn token mounted) seems to allow it to access data fine. Can auto-complete metrics and graph them, but the table tab errors ‘Error: Missing “data” field in response JSON’:

Have you ever hit this error? Debug logs show nothing. On promlens v0.3.0.

[DazWilkin]

Are you able to determine the underlying API call using the browser's DevTools?

I've not looked at this for some time, but I revisited https://demo.promlens.com/ and, Table uses /api/v1/query whereas e.g. Graph uses /api/v1/query_range.

PromLens occasionally adds refresh parameter to the query string for /api/v1/query and GMP (used to!?) balk at this (Google IssueTracker Issue 264655965)