Software Usage Metrics on the CI Record: Install vs. Usage
A configuration management database (CMDB) shows what is installed across the estate, on every server and endpoint. Each configuration item (CI) records the software installed on it. How much of that software runs on each machine often sits outside the record.
Install data shows what is on a machine. Run time data shows how much of it runs. Renewals, license counts, cleanup decisions, and patch priorities often get decided on install counts alone.
Virima 6.1.5, released September 3, 2026, adds View Software Usage Metrics to the CI record. Administrators can see how long monitored software runs on a machine, directly from that machine’s CI. Details are in the Virima 6.1.5 release notes.
What the Feature Is and How It Works
From release 6.1.5, administrators can see how long monitored software runs on a machine, directly from its CI record. Open any CI record, select Other Actions, then select View Software Usage Metrics. The report opens in a popup.
Summary view and session view
The summary view lists one row per monitored software title, with Total Used Time and Usage Percentage. Select a title to open the session view, which shows each session, including:
- Day
- Start and end time
- Used time
- Time zone
- Process ID
- User
Time ranges are Last 24 hours, Last 30 days, Last 365 days, or custom dates.
The Usage Report on a Software record shows one title across all CIs. View Software Usage Metrics shows all monitored software on one CI. The two views answer different questions: how one title runs across the estate, and what runs on one machine.
How Usage Data Gets Recorded
The Discovery Agent checks running programs every minute and records when a monitored program starts and stops. Coverage includes Windows and Linux machines running the Discovery Agent.
The agent sends its data once a day at midnight machine time, so usage appears the next day. Usage is recorded per operating system user, and every Admin can see all users’ usage.
How This Benefits Virima Users
Install data and run time data sit in the same record, next to the CI’s relationships and lifecycle status. Administrators get these benefits from the CI itself:
- One view per machine: all monitored software on a CI appears together, with Total Used Time and Usage Percentage for each title.
- Session-level detail: the day, start and end time, user, and process ID answer follow-up questions from the same popup.
- Cleanup and decommission decisions: run time data supports the decision to keep or remove installed software.
- Renewal and license conversations: run time evidence gives these discussions a starting point beyond install counts.
- Patch and vulnerability priority: software that runs on a machine can move up the patch order.
These views build on the CMDB feature page capabilities already in the platform.
What Admins Can Decide From the Data
Users with the Admin role can open the report. Each function below works from the same CI-level view.
IT asset management and procurement
IT asset management (ITAM) teams can see which monitored titles show a low Usage Percentage on a CI. Procurement can bring run time evidence into renewal discussions.
IT operations
IT operations teams can see which installed software is a candidate for removal from a machine.
Security and patch priority
Security teams can see which installed software runs on a machine and deserves patch priority.
Setting Up Usage Monitoring
Usage data records when these four conditions are met:
- A Discovery Agent is installed on the machine and linked to the CI, and its Discovery Application is connected.
- The software is set up under Admin > Major Software with Monitor Software Usage set to Yes and a process name to monitor.
- The software is recorded as installed on the CI, with a matching version if one is set.
- The CI remains unarchived.
What the Metrics Represent
Matching uses the process name. Each metric reflects the monitored program running on the machine. Each running process appears as a separate session, with a 24-hour cap per day. Data is recorded while the Discovery Agent and the machine are running.
History starts on the day monitoring is turned on.
Conclusion
Virima 6.1.5 puts install data and run time data in the same CI record, so each machine’s software list comes with the run time behind it. Request a free trial to see View Software Usage Metrics on your own CIs.
Frequently Asked Questions
Who can open View Software Usage Metrics?
Users with the Admin role. Every Admin can see all users’ usage.
Which machines and data sources are covered?
Windows and Linux machines running the Discovery Agent. Usage data comes from the agent.
How soon does usage appear?
The agent sends data once a day at midnight machine time, so usage recorded today shows up in the report the next day.
What does a session represent?
A monitored process running on the machine. Each running process is logged as a separate session, with a 24-hour cap per day.
How does this differ from the Usage Report on a Software record?
The Software record report covers one title across every CI that has it installed. This view covers every monitored title on one CI.
