Getting Started
See the fastest path from sign-up to first value in Logger: run one sample or upload, review failure groups, save a report, and only then expand into integrations or teammates.
The first activation milestone is creating one useful analysis from `/analyses/new`. Open a sample analysis or use one representative incident window so failure groups, summaries, and optional advanced comparison become immediately visible.
The fastest proof of value is opening one failure-group detail and then saving a report or export once the failure groups look right. That turns the first analysis into a reusable report instead of a one-time upload.
If the product is new to the team, it helps to see a completed analysis before you decide whether the product fits. Use the example below as a reference for what a useful first result should actually look like.
After the first analysis is useful, connect Slack, Jira, GitHub, or webhook automation and invite a teammate so the workspace becomes operational. Those are strong second-step actions, but the core first-run goal is still one clear analysis and one reusable output.
Evidence-first incident analysis for teams that need failure groups fast.