The problem
You keep retesting edge cases by hand and losing the context that explains behavior. Environments drift, and it’s hard to compare by version, feature flag, or test run.
The solution
Define tag rules that apply during capture. Use tags to label environment, version, scenario, or test run. With the upcoming connectors feature, you can further enrich requests/responses or emit events to external systems (like Slack, data warehouse or custom webhooks).
Who it helps
- QA labeling scenarios and test runs for consistent comparisons
- Developers adding env/version/feature context to traffic
- Integrations with exporting enriched data to other tools
Outcomes
- Consistent, queryable context across request, events and sessions
- Faster triage with tags for version, environment, and scenario
- Zero‑code enrichment via optional connectors (upcoming)
Ready to dive in?
Explore the Rules Engine
Related capability
Expose Local APIs to Remote Clients & Webhooks
Level 2