Process session
To see how long applications run and how much of that time is idle, open the Process session report. It tracks process run times, idle times, and session durations across hosts, users, and process names. Use it to identify resource utilization, idle license consumption, and system usage patterns to support optimization.
The following screenshot shows the charts of process-level session durations and idle times:
The Process session report shows process-level license session durations, idle times, and user-machine activity.
To see the underlying sessions row by row, open Process Sessions. Process Manager also embeds this dashboard on its own Dashboard page.
Visualizations
The report has the following visualizations:
- Total Session Duration by Host Name: Use this bar chart to see which machines have the longest running processes. It shows the total accumulated session duration in days for each host name. Values displayed:
- Host Name
- Session Duration in Days
- Total Idle Time and Session Duration by Process Name: Use this dual-axis chart (bar and line) to spot efficiency or waste in application usage. It shows total session duration versus idle time for each process name. Values displayed:
- Process Name
- Session Duration in Days
- Idle Time in Days
- Total Idle Time and Session Duration by Username: Use this area and line chart to detect idle usage trends at the user level. It compares session durations and idle times across different users. Values displayed:
- Username
- Session Duration in Days
- Idle Time in Days
- Process Session Details Table: A detailed table of each process session's metadata, including process name, dynamic link library (DLL) file, version, agent status, and start and end times. Values displayed:
- Process Name: Name of the running application or process.
- DLL Name: The DLL file used by the process.
- Version: Software version of the process.
- Agent Status: Whether the monitoring agent is online or offline.
- Session Start Time: Start time of the process session.
- Session End Time: End time of the process session.
- Session Duration in Minutes: The duration between session start and end times (minutes).
- Shutdown Reason: The reason for the shutdown of the process session.
- Total Idle Time (Minutes): Idle duration in minutes for the session.
- Username
- Host Name
To narrow the report, use these filters:
- Process Start Time: A relative date filter. It defaults to Last 14 days and prints the resolved range underneath (for example,
2026/07/11 to 2026/07/24). Select another preset, or a custom start and end date, to change the reporting period. - Process Name: Select specific process names to focus the report.
- DLL Name: Filter by the DLL file name associated with the process.
- Host Name: Select specific host machines.
- User Name: Filter by username to view individual usage sessions.
- Child Username: OpenLM Platform combines usage under a parent user account, so User Name shows the combined total for that person. Select a child username here to drill down into a single account merged under the parent. See User aliases for how OpenLM Platform builds the mapping.
Interpreting this report
Use these points to read the report:
- This report covers processes, not licenses. It comes from the Workstation Agent watching applications run, which is how it can measure what license reports cannot: time an application was open against time it was in active use.
- Idle time against session duration per process is the case for reclaiming licenses. A process averaging hours open with most of it idle is exactly where idle-time policies (or user habits) have room to reclaim capacity. Identify the users and machines in the details table.
- Shutdown Reason distinguishes closed from killed. Sessions ending abnormally on the same host pattern point at instability that also inflates license churn in Session details.
- Agent Status matters for trust. Rows from an offline agent are stale by definition, so check it before reading low activity as low usage.
The documentation team might draft this page using a large language model. A technical writer reviews every page and verifies it against the product before publishing it. A human makes the final decision.