Use outcome analysis and reports
Use Service Desk, Security Ops, People Ops, FinOps, and Executive views to inspect the records behind operational measures.
Before you start
- A verified session in the intended organization.
- Relevant agent, alert, ticket, or external source records for the selected view.
- Administrator status and permitted workforce analytics access for People Ops.
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 an analysis view
Expand Insights → Outcome analysis. The navigation above the page switches between Service Desk, Security Ops, People Ops where available, FinOps, and Executive. Each view uses its own sources and time periods.
What you should see: The title and source panels match the question you want to answer.
Review Service Desk outcomes for a selected window
Choose Service Desk, then set Analysis window to the last 7, 30, or 90 days. Read the ticket linkage count, median recorded alert resolution time, and distinct devices alerting.
| Field or control | What to do |
|---|---|
| Alerts linked to tickets | The proportion of alerts with a ticket link among alerts raised in the selected window. Use View all alerts in this window to inspect individual records. |
| Median alert resolution time | The median time between trigger and recorded resolution for the resolved alert records in the period. |
| Rule and OU groups | The top ten groups by alert count, grouped by rule name and the device’s current organizational unit. Use this to identify where to investigate. |
| DEX change after legacy automation runs | A before/after score comparison for eligible matched legacy runs. Read the matching window beneath the heading before interpreting a change. |
Compare patch observations across sites
Choose Security Ops. Read each site’s observation date, device bucket, and historical mean. Click Inspect [site] history to expand its returned dates. Select Patch management to continue into current patch posture and deployment work.
Read permitted workforce observations
Choose People Ops when your administrator has enabled the required access. Rapport records access before loading the workforce panels. Inspect Utilization by team, category time, application foreground time, and Digital friction by team.
- Use Category assumptions to understand the productive/neutral classification attached to categories.
- Read units carefully: some after-hours figures are per reporting device per week.
- Use team aggregates to identify support needs and validate the contributing source data before drawing conclusions about work.
Inspect asset, warranty, and license data
Choose FinOps. Open Inspect asset records and source dates to see purchase amounts, warranty dates, sources, and update times. Use Inspect device to open a specific asset’s endpoint.
| Field or control | What to do |
|---|---|
| Warranty coverage | Groups the returned lifecycle records into expired, expiring, later, and unknown dates as of the displayed UTC date. |
| Friction scenario assumptions / Friction cost scenario | Requires recorded rates and currency, complete lifecycle and eligible daily friction observations. Refresh these panels independently when an input is stale. |
| Reliability by model | Compares recorded crashes per 100 cohort devices on each displayed observation date. |
| License cost & renewals | Shows recorded seats, unit cost, billing period, renewal date, source, and update time. Currency-free source records are displayed as recorded units. |
Use Executive to navigate to the evidence
Choose Executive and select the card matching your decision: overview, endpoints, experience, patches, alerts, operations, or a specialist analysis. Read the destination’s scope and measurement window after navigating.
What you should see: You reach the underlying operational or analytical view used to make the decision.
Refresh a source and retain its context
Each source panel has its own Refresh or Retry button. Refresh a stale source, then record the displayed time window, returned-record coverage, and observation dates with any value you share. When a panel has failed, retry that panel before using its result.
What you should see: A report can be traced to a specific source, period, and set of records.
If something doesn’t work
People Ops is hidden or access cannot be recorded
An administrator must check your organization role and workforce analytics permission in Members and Workforce Privacy. If permission is already granted, reconnect and select Retry workforce access.
FinOps has no purchase totals or the cost scenario is unavailable
Inspect source records for missing currencies, rates, lifecycle coverage, or friction measurements. The cost scenario also requires its three input panels to be refreshed within five minutes. Current connector availability is described in the Connectors guide.
Different views show different counts
Compare each view’s stated population and window. Current fleet counts, historical site observations, alert-trigger windows, and returned asset records answer different questions.