Skip to main content
When something breaks, you want to know why — and logs tell that story. OpenSRE connects to OpenObserve to retrieve log and trace data that helps explain what was happening when an alert fired, making it easier to correlate errors, anomalies, and service interactions during investigations.

What you need

  • An OpenObserve instance (self-hosted or cloud-hosted)
  • An OpenObserve access token
  • The URL of your OpenObserve deployment
  • Access to the organization you want OpenSRE to query

Getting set up

Guided setup

Start here if you want step-by-step guidance:
Select OpenObserve and enter your OpenObserve credentials when prompted.

Manual setup with environment variables

Or add these to your .env file:

Alternative authentication

If your OpenObserve deployment uses username/password authentication instead of tokens, you can configure:
Use either token-based authentication or username/password authentication depending on your OpenObserve deployment.

Option 3: Persistent store

Finding your OpenObserve credentials

  1. Log in to your OpenObserve instance
  2. Navigate to your user or organization settings
  3. Create or retrieve an access token
  4. Copy your OpenObserve URL
  5. Note the organization name you want OpenSRE to query
  6. Add these values to your OpenSRE configuration

What OpenSRE can query

Once connected, OpenSRE can search across:
  • Logs — Search by timestamp, service name, log level, and message content
  • Traces — Investigate spans, follow distributed traces, and analyze latency
  • Metrics — Query observability metrics stored in OpenObserve
Use a token with the minimum permissions required for investigation workflows whenever possible.

Test your connection

Make sure everything is configured correctly:
Expected output:

Troubleshooting