How Does LAMUM Gather Data?

You may be wondering how does LAMUM gather data. Here we discuss how LAMUM collects data for Inventory/Asset, Renewal and Vendor and Usage data (for the various license types).

Inventory/Asset, Renewal and Vendor data:

Quickly import (anything in an Excel spreadsheet). Manual entry also is fast and easy. GUI is very intuitive and it takes less than 5 minutes to enter a Line Item, including daemon and license server information. For faster or repetitive entry the “Clone” command is useful.

Usage Data (depends on License Manager type):

For FlexLM licenses, there are two ways. First, “lmstat” collects checkout information every 10 minutes. This provides Current Checkout Reports (Overview Table, Gas Gauges, and User Details). User Detail reports have Active Directory link for User ID, and a “Remove” button is available to reclaim a license and move it into the pool.

Flex Debug Logs provide Denials and Short Checkout information. Log files are parsed daily. Denials Report available numerous ways – Denials Detail by daemon, Comprehensive Denials Detail across all daemons, Denials by user, Denials by Group, Denials by Tool Graph, and Denials Heatmap. Denial Details can be filtered by Denials Code to get True Denials only..

Reprise, DSLS, LM-X have similar commands to Flex to gather data every 10 minutes. Reprise and DSLS can also report Denials by parsing the related Debug Log.

Sentinel RMS, Sentinel HASP, Altium, Atlassian, Windchill all have a Checkouts Log file, which can be parsed daily to collect historical usage data, for historical usage reports.

Have further questions? Our Support team would be happy to answer.

Leave a Reply

%d bloggers like this: