What Just Happened
During onboarding, the Sailfish team configured your system end-to-end. Here's what's now running:
Your System Is Now...
Capturing issues — Every user session, exception, network failure, and console error is being recorded. When a customer hits a problem, Sailfish already has the full context before anyone reports it.
Analyzing impact — As issues are detected, Sailfish automatically identifies how many users are affected, how severe the impact is, and whether it's getting worse. No manual investigation required.
Routing actions — Workflows you configured during onboarding are actively monitoring your application. When conditions are met, alerts fire to the right channels and tickets are created automatically.
What's Connected
| System | What It Does |
|---|---|
| Your application (via SDK) | Captures frontend interactions, backend traces, exceptions, and network requests |
| Customer sources (Zendesk, Salesforce, Pylon) | Pulls in customer reports and links them to technical context |
| Engineering tools (GitHub, Jira/Linear) | Creates tickets with full reproduction context, enables auto-fix PRs |
| Messaging (Slack, Email) | Sends alerts when workflows trigger |
What You Don't Need to Do
- No manual log searching — Sailfish already correlated the data
- No reproduction attempts — The full execution context is captured automatically
- No guessing who's affected — Impact is calculated in real time
- No building dashboards — Mission Control is your single pane of glass
If something looks off or a connection seems down, check the Settings → Integrations page in the Sailfish dashboard, or reach out to the Sailfish team.