OpenSRE queries Honeycomb to surface distributed traces during alert investigations — identifying slow spans, high-error services, and query patterns correlated with incidents.Documentation Index
Fetch the complete documentation index at: https://opensre.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites
- Honeycomb account (classic or environments-based)
- API key with query access
Setup
Option 1: Interactive CLI
Option 2: Environment variables
Add to your.env:
| Variable | Default | Description |
|---|---|---|
HONEYCOMB_API_KEY | — | Required. Honeycomb API key |
HONEYCOMB_DATASET | __all__ | Dataset to query (classic) or __all__ for environments |
HONEYCOMB_API_URL | https://api.honeycomb.io | Override for EU region or proxies |
Option 3: Persistent store
Creating an API key
- In Honeycomb, go to Account → API Keys
- Click Create API Key
- Set the environment and enable Query Data permission
- Copy the key
Verify
Troubleshooting
| Symptom | Fix |
|---|---|
| 401 Unauthorized | Confirm the API key is correct and has Query Data permission |
| Dataset not found | Use __all__ or check the exact dataset name in Honeycomb |
| EU account unreachable | Set HONEYCOMB_API_URL=https://api.eu1.honeycomb.io |
Security best practices
- Use a dedicated read-only API key scoped to query access.
- Store the API key in
.env, not in source code.
Tracer