Your First 24 Hours
Here's what to expect and what to check in the first day after go-live.
Welcome Dashboard
The first thing you see after logging in is the Welcome Dashboard. It shows key activity metrics for your application:
- Issues reported — Total issues detected in the last 7 days
- Unique users impacted — How many distinct users encountered at least one issue
- Daily active users — User activity trend over the last 7 days
These numbers start populating as soon as sessions begin flowing in. Use them to get a quick pulse on your application's health each time you log in.
Status Page
The Status Page is your go-to for verifying that Sailfish is receiving data correctly. Navigate to it from the dashboard or the left sidebar.
Service Status Indicators
The Status Page shows connection status for each component:
| Status | Meaning |
|---|---|
| Connected | Data is flowing. Last recording received within the expected window |
| Stale | Data was received previously but the most recent recording is older than expected. Check that your SDK is still running in production |
| Disconnected | No data has been received. Verify SDK installation and network connectivity |
What to Check
- Frontend service — Confirms the frontend SDK is sending session data
- Backend service — Confirms the backend SDK is sending function spans and logs
- Last recording timestamp — Shows exactly when the most recent data was received
- Backend-to-frontend linkage — If you see a warning about the
X-Sf3-Ridheader, your backend responses are not including the correlation header. See Instrument Your Code to configure this
The Status Page auto-refreshes every 30 seconds so you can keep it open while verifying a deployment.
Bookmark the Status Page during your first week. It's the fastest way to confirm everything is working after a deployment.
What You Should See
Within the first hour:
- Sessions appearing in the Recordings timeline
- Console logs, exceptions, and network requests flowing in
- User identities showing up (if
identify()is configured)
Within the first 4 hours:
- At least one workflow triggered (if you configured alerting workflows)
- Issues detected — even if minor (this means the system is working)
- Impact data populating on detected issues
Within 24 hours:
- Teams interacting with the system — Support linking reports, Product reviewing impact, Engineering investigating issues
- A clear picture of your application's health across users and sessions
What to Check
Telemetry is flowing
Open the Sailfish dashboard and navigate to Recordings. You should see a steady stream of user sessions. If the timeline is empty:
- Verify your SDK is initialized in the deployed environment
- Check that the API key is correct
- Confirm network requests to
api-service.sailfish.aiare not blocked
Workflows are running
Navigate to Workflows. Active workflows should show a "Normal" or "Firing" status. If a workflow shows "Inactive," it may need to be enabled.
User identification is working
Click into any session in Recordings. You should see the user's email or identifier (set via the identify() call). If sessions show as anonymous, check your frontend integration.
Alerts are arriving
Trigger a known error in a staging environment and verify that:
- The issue appears in Sailfish
- Any matching workflow fires
- The alert arrives in Slack or email
Common First-Day Questions
"I don't see any issues — is that normal?" Possibly. If your application is stable, there may be no issues to detect yet. Check that telemetry is flowing (sessions should still appear). You can test by intentionally triggering an error.
"There are too many alerts." Tune your workflow conditions. Tighten thresholds or add filters to reduce noise. The Sailfish team can help optimize this.
"My team isn't sure where to look." Share the How Teams Work Together page. It defines exactly what each role does in Sailfish.
Need Help?
The Sailfish team is available during your first week post-go-live. Reach out via your dedicated Slack channel or email support@sailfishqa.com.