Software Metering NQL examples
Users and devices can be removed from Nexthink Infinity. When this occurs, software metering data may remain without an associated user or device. Refer to the Understanding Key Data Platform Concepts – Data Resolution and Retention documentation for more information about data retention for Inventory objects.
Querying the software metering data
Use Nexthink Query Language (NQL) in the Investigations module to access software metering data and other relevant information.
NQL data structure
The software_metering.events
table contains software usage data. Each event has a resolution of 1 week. The retention of this data is 90 days.
Timeframe alignment between Software Metering and other tables in NQL
When using NQL to query Software Metering data, be aware that these events are grouped into 7-day periods. This means each event spans a full week, not a single day. The start of every software_metering.event
is always Monday at 00:00 UTC.
Why it matters
Because of this weekly grouping, mismatched timeframes can lead to:
Missing data,
Including partial results, or
Incorrect comparisons—especially when combining with events such as
execution.events
, which use finer time granularity.
For example, these two queries will return the same results because both start retrieving data on a Monday at 00:00 UTC:
software_metering.events from 2025-08-04 00:00:00 to 2025-08-08 10:00:00
| where application.name == "Firefox"
| summarize number_of_users = user.count()
execution.events from 2025-08-04 00:00:00 to 2025-08-08 10:00:00
| where application.name == "Firefox"
| summarize number_of_users = user.count()
Examples of NQL queries
Last updated
Was this helpful?