What you’ll get: ewake can query your Loki instance to retrieve logs from any service, correlate log patterns with alerts, and surface relevant log lines during investigations, without requiring manual LogQL queries.
Prerequisites
- A Loki instance (Grafana Cloud or self-hosted)
- Your Loki endpoint URL
- An API key or bearer token if your instance requires authentication
Configuration
1
Get your Loki endpoint URL
Grafana Cloud: Go to your Grafana Cloud portal → My Account → Grafana Cloud Stack → Loki details. Copy the URL under Loki Logs URL.Self-hosted: Your Loki URL follows the format
http://loki.your-domain.com:3100.2
Generate an API key (Grafana Cloud)
In Grafana Cloud, go to My Account → Access Policies → Create access policy.Grant it
logs:read scope, then generate a token and copy it immediately.For self-hosted Loki with no authentication, leave the API Key field empty.
3
Open the Loki integration in ewake
In your ewake dashboard, go to Integrations → Loki → click Connect with API key.
4
Enter your credentials
5
Test and save
Click Test connection to verify the connection, then click Save.
Loki is connected. Ewake can now query your logs 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 queries logs in read-only mode using LogQL. It never writes to or modifies your Loki instance.