- What to find: describe the behavior in plain words. It does not have to be a failure.
- Sampling %: run over a slice of your traces instead of all of them, to keep cost and time down.
- Trace-name regex: limit the search to traces whose name matches a pattern.
- Model quality: pick Cheapest, Balanced, or High-quality. Use a cost-efficient built-in system model to look for simpler patterns, or High-quality mode to catch issues that can be very hard to find.
- Explanations: optionally get a short reason, with citations from the trace, for why each trace matched. Off by default since it costs more.
Next steps
Tracking
Pin the patterns worth watching and get notified when they come back

