Loki
Loki is where Opriven goes to read what your systems actually said as they failed. Opriven reaches Loki through your Grafana connection, so if Loki is wired into Grafana as a data source it comes online with it — there's no separate Loki integration to configure.
#What Opriven does with Loki
- Search logs with LogQL across the window around an alert
- Pull the error and stack trace behind a failure signature
- Compare log volume and content before and after a deploy
- Tie log lines back to the trace and metric series they belong to
#Connecting Loki
Loki is connected through Grafana. Follow the Grafana setup and Opriven picks up Loki automatically as one of its data sources.
Prerequisites
- Loki configured as a data source in Grafana Cloud or a self-hosted Grafana instance
-
Connect Grafana
Follow the Grafana setup for whichever deployment you run. Opriven queries the data sources wired into Grafana, so no Loki-specific credential is needed.
-
Make a self-hosted instance reachable
If Loki and Grafana run inside your own network, review the self-hosted requirements — Opriven needs an HTTPS endpoint and a read-only token to query it.
#Permissions and access
Opriven reads Loki through Grafana using the same read-only credential. It issues queries only — no writes or ingestion.
All tenant data is processed in isolated environments. See security and compliance for details.
Contact us via Slack or at support@opriven.com.
Related integrations
Grafana
Monitoring & ObservabilityDashboards, alerting, Prometheus, Loki, OnCall, and incidents.
Prometheus
Monitoring & ObservabilityUse metrics to explain system behavior.
Tempo
Monitoring & ObservabilityFollow traces across services.