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: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:Option 3: Persistent store
Finding your OpenObserve credentials
- Log in to your OpenObserve instance
- Navigate to your user or organization settings
- Create or retrieve an access token
- Copy your OpenObserve URL
- Note the organization name you want OpenSRE to query
- 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.