Documentation

Find assistant sessions and review usage

Locate a conversation that needs review, open its device transcript, and interpret session analytics using the correct time and filter scope.

Access An MFA-verified console user with access to the organization’s session insights.Console path /rmm/agent-sessions

Before you start

  • At least one on-device assistant session must have been recorded in the selected organization.
  • Use the device Agent workspace to inspect the actual conversation behind an analytics row.

Screenshots show the Rapport interface with example data. Use your organization’s devices and values. Select an image to view it at full size.

Choose the session creation window

Open Agent Sessions and select 7d, 30d, or 90d. On Sessions, read the source retrieval time, creation cutoff, and matching-row count. The list applies its filters before a maximum of 500 returned rows.

Choose a time window, then use list filters to find a request. Device and request links open the device workspace where the conversation can be reviewed.

What you should see: You know the creation window and whether the returned list is partial.

Find a conversation that needs attention

Type into Search by request or device…, choose Session status, and optionally select Has approval steps or No approval steps. Click Turns, Tokens, Duration, or When to sort; click again to reverse direction.

Fields and controls for Find a conversation that needs attention
Field or controlWhat to do
Session statusAny status, Queued, Running, Waiting for user, Needs approval, Completed, Failed, or Cancelled.
Search wildcards% or * matches any characters; _ matches one character.
Approval stepsSelects sessions with or without recorded approval steps. Such steps can include automatic decisions; they do not necessarily mean a human intervened.
Started byShows the requester name when available, otherwise its recorded user ID or Requester not recorded.

Open the device and inspect the actual thread

Follow the request title or device link. In Agent workspace, choose the matching conversation and read its request, tools, responses, and approval cards. The fleet link opens the device record, not a transcript filtered to the analytics window. Use the conversation list to locate the intended thread.

What you should see: You can inspect the exact steps behind a session status or approval count.

Switch to Analytics for the whole selected window

Select Analytics and read its time-window note. Search, status, approval-step filters, and list sorting do not apply to this tab. Analytics includes all organization sessions in the selected server creation window, which can differ slightly from the list’s elapsed-hour cutoff.

Fields and controls for Switch to Analytics for the whole selected window
Field or controlWhat to do
Sessions / Without approval stepsSession count and the share with no recorded approval steps. This is not a verified remediation-success rate.
Awaiting approvalRecorded waiting status for sessions created in the selected window, not every outstanding approval in the organization.
Median recorded durationEnd time minus creation time for sessions with an end time; this does not measure time to verified device recovery.
TokensRecorded input and output token usage, with a per-session value when the denominator is available.
Analytics summarizes all sessions in the chosen creation window. It does not inherit the request, status, or approval filters from the session list.

Use charts to choose what to inspect next

Review Sessions per creation day, Recorded session status, Recorded tool results, and Recorded approval decisions by action. Tool-result counts include failed results. Approval-action groups combine arguments and are a bounded source subset. Use Devices with the most sessions to open devices that merit a closer review.

Refresh the relevant source before reporting

Use Refresh in the Sessions or Analytics panel to reload that source. If requester names fail separately, use Retry requester names. Report the selected window, whether the list was partial, and which tab supplied the figures so another operator can reproduce the result.

What you should see: Session review and usage reporting refer to clearly identified records and time scopes.

If something doesn’t work

The list and Analytics totals differ.

List filters affect only Sessions. Analytics uses all sessions in its server creation window; the list uses its own elapsed-hour cutoff and can be capped at 500 matches.

The session says Completed but the issue remains.

Open the device workspace and review the actual result and later device evidence. Session completion is not a device recovery verdict.

A request needs approval but is absent from the current list.

Widen the creation window and clear filters. This list is not a complete queue of all outstanding command approvals; use Approvals for command decisions.

All documentation