What you’ll get: ewake can query your Prometheus instance using PromQL to retrieve metrics, detect anomalies, and correlate data points with alerts and deployments, without requiring manual query construction.
Prerequisites
- A Prometheus instance (self-hosted or Grafana Cloud Mimir)
- Your Prometheus endpoint URL
- A bearer token if your instance requires authentication
Configuration
1
Get your Prometheus endpoint URL
Self-hosted: Your Prometheus HTTP API is accessible at
http://prometheus.your-domain.com:9090.Grafana Cloud (Mimir): Go to your Grafana Cloud portal → My Account → Grafana Cloud Stack → Prometheus details. Copy the Remote Read URL.2
Generate an API key (Grafana Cloud)
In Grafana Cloud, go to My Account → Access Policies → Create access policy.Grant it
metrics:read scope, then generate a token and copy it immediately.For self-hosted Prometheus with no authentication, leave the API Key field empty.
3
Open the Prometheus integration in ewake
In your ewake dashboard, go to Integrations → Prometheus → click Connect with API key.
4
Enter your credentials
5
Test and save
Click Test connection to verify the connection, then click Save.
Prometheus is connected. Ewake can now query your metrics during investigations.
Behind Cloudflare Access or a proxy
If your Grafana instance sits behind an authenticating proxy, add the credentials it expects under Custom headers in the same dialog. For a Cloudflare Access service token that means two headers:
Ewake sends these with every request. Values are stored encrypted, and are not shown again after saving, leaving the fields empty when you edit the connection keeps the headers you already saved.
Without this, a connection test against a proxied endpoint fails with an authentication or redirect error even though the URL and API key are both correct. It’s the most common cause of a test failing on a working instance.
Ewake uses read-only PromQL queries. It never writes metrics or modifies your Prometheus configuration.