Sessions

Sessions group log events by session ID so you can see the full sequence of events for a single user visit — errors, warnings, and all.

What you’ll need

• Events ingested with a session_id field (added by the ScryWatch SDK or set manually)
• See Getting Started if you haven’t sent any events yet

Step 1: Open Sessions

Click Sessions in the left sidebar. You’ll see a table of sessions, most recent first.

Each row shows:

• Session ID — the unique identifier for this session
• Events — total event count for this session
• Errors — how many error-level events occurred
• Warnings — how many warn-level events occurred
• Crashes — how many crash-type events occurred
• Device — device type if detected (web, mobile, etc.)
• Service — the service that logged events for this session
• Last seen — when the most recent event in this session arrived

Step 2: Filter sessions

Use the filter dropdowns at the top to narrow down by:

• Environment — production, staging, etc.
• Service — filter to a specific service
• Device type — web, mobile, server, etc.

Sessions with errors will appear at the top when sorted by error count.

Step 3: Identify problematic sessions

Look for sessions with a high Errors or Crashes count. These are users who experienced something going wrong.

Tip: A session with errors: 0, crashes: 1 often indicates an unhandled exception that terminated the session. A session with many errors suggests a recurring issue during that user’s visit.

Step 4: Open a session

Click any session row to expand it and view the full event timeline for that session.

You’ll see all events in chronological order, including:

• The exact message for each event
• The level (info, warn, error, crash)
• The timestamp
• Any metadata fields sent with the event

Use this view to reconstruct exactly what happened during that user’s session — what they were doing when the error occurred, what preceded it, and what happened after.

Step 5: Jump to Log Explorer

From the session detail, click View in Log Explorer to jump to the Log Explorer pre-filtered to events from this session. You can then search, filter, and inspect individual events in detail.

You’re done

You now know how to:

• Read the sessions table and identify sessions with errors or crashes
• Filter sessions by environment, service, and device type
• View the complete event timeline for a session

Related docs

Sessions are populated automatically when your events include a session_id field. The ScryWatch JavaScript and Flutter SDKs set this automatically.