CSV File Formats for Data Export Reports

A unique identifier assigned to a specific tenant (software vendor) during the vendor's deployment in the Thales-hosted cloud.

A unique identifier that is randomly generated during the licensed application's execution and is used to identify each login, logout, detach, and cancel detach call.

A unique number that is associated with a given vendor code and batch code (namespace).

The identifier of the Sentinel protection key.

Reserved for future use.

The unique product identifier defined by the vendor in Sentinel EMS.

The product name assigned in Sentinel EMS.

The version number associated with the usage data for the events schema, such as version 1, when the schema was initially introduced.

The Sentinel Licensing API library version.

The unique customer identifier that is automatically generated by Sentinel EMS in the background when a customer is created. This identifier is different from the one that vendors assign to customers.

Thales recommends ignoring this auto-generated identifier unless you have two customers with the same name, and you need to differentiate between their usage data. To determine which customer is being named, use Sentinel EMS REST API - Get Customer. This endpoint retrieves a specific customer based on the specified unique identifier.

The name of the customer in Sentinel EMS.

A custom-defined, unique identifier for a specific feature stored in a Sentinel protection key. This is the number passed to the Login function to establish access to the feature.

The name of the feature in Sentinel EMS.

The license model of the Sentinel protection key.

The total pool of executions for the licensed software.

The number of used executions for the licensed software.

The expiration date and time of a license. For example, 2025-01-01T23:59:59.000Z, which represents January 1, 2025, at 11:59:59 PM UTC. This applies to:

> Time from First Use licenses, where the expiration date and time are assigned based on first use and license duration.

> Expiration Date licenses, where the expiration date and time are assigned based on the expiration date set.

>The start date and time of a license. For example, 2024-09-05T07:34:41.000Z, which represents September 5, 2024 at 7:34:41 AM UTC. This applies to Time from First Use licenses. The expiration date and time are assigned on the basis of first use.

>The placeholder value 1970-01-01T00:00:00.000Z, which represents January 1, 1970, at 12:00:00 AM UTC is used under the following scenarios:

•For Perpetual and Execution Count licenses as the feature start date and time do not apply.

•For Expiration Date licenses when the feature start date and time is not defined.

>For Trial licenses, both the feature start date and time and feature expiration date and time are assigned on the basis of first login.

The total duration (in seconds) for which the Time from First Use license is valid.

The maximum number of concurrent instances permitted to run the licensed software.

The current number of concurrent instances running the licensed software.

A unique 7-character identity code, which is part of the full identity string required by remote machines to access the cloud license.

The name of the person or entity for whom the cloud license was generated.

The unique identifier of the customer's user, as defined in Sentinel EMS.

Reserved for future use.

The date and time on which the client identity expires. For example, 2025-01-01T23:59:59.000Z, which represents January 1, 2025, at 23:59:59 (11:59:59 PM) in UTC. "Never Expires" is displayed when the identity string does not have an expiration date.

The maximum number of remote client devices allowed to use the given identity string to access the cloud license.

A value of 0 (zero) means there is no limit to the number of remote client devices permitted.

The current number of remote client devices that have registered to use the given identity string to access the cloud license.

The application name specified by the software vendor.

The application version that corresponds to the application name specified by the software vendor.

The unique session ID.

The status codes related to the operation of the Sentinel Licensing API functions.

Note that not all errors returned by the hasp_login API are logged in the login events report. For example, the following errors are not logged: 88 (HASP_IDENTITY_UNAUTHENTICATED), 89 (HASP_IDENTITY_DISABLED), and 103 (HASP_IDENTITY_EXPIRED). This occurs because identity validation is processed before the login request is handled.

The number of executions that were consumed for a single login.

The creation date and time of the event data. For example, 2025-01-01T23:59:59.000Z, which represents January 1, 2025, at 11:59:59 PM in UTC.

The domain name of the logged-in machine.

The host name of the logged-in machine.

The user name of the logged-in machine.

Reserved for future use.

The virtual machine information for the logged-in machine.

A unique identifier assigned to a specific tenant (software vendor) during the vendor's deployment in the Thales-hosted cloud.

A unique identifier that is randomly generated during the licensed application's execution and is used to identify each login, logout, detach, and cancel detach call.

A unique number that is associated with a given vendor code and batch code (namespace).

The version number associated with the usage data for the events schema, such as version 1, when the schema was initially introduced.

The Sentinel Licensing API library version.

The unique session ID.

Duration of a login session (in seconds).

The status codes related to the operation of the Sentinel Licensing API functions.

A unique identifier assigned to a specific tenant (software vendor) during the vendor's deployment in the Thales-hosted cloud.

A unique identifier that is randomly generated during the licensed application's execution and is used to identify each login, logout, detach, and cancel detach call.

A unique number that is associated with a given vendor code and batch code (namespace).

The unique product identifier defined by the vendor in Sentinel EMS.

The product name assigned in Sentinel EMS.

The total number of seats that can be detached concurrently for the product from the cloud license manager server.

The version number associated with the usage data for the events schema, such as version 1, when the schema was initially introduced.

The Sentinel Licensing API library version.

NOTE   In certain cases, the value may not be fully accurate. Improvements are planned for future releases.

A unique 7-character identity code, which is part of the full identity string required by remote machines to access the cloud license.

The name of the person or entity for whom the cloud license was generated.

The unique identifier of the customer's user, as defined in Sentinel EMS.

Reserved for future use.

The date and time on which the client identity expires. For example, 2025-01-01T23:59:59.000Z, which represents January 1, 2025, at 23:59:59 (11:59:59 PM) in UTC. "Never Expires" is displayed when the identity string does not have an expiration date.

The maximum number of remote client devices allowed to use the given identity string to access the cloud license.

A value of 0 (zero) means there is no limit to the number of remote client devices permitted.

Reserved for future use.

Reserved for future use.

The total number of seats currently detached from the cloud license manager server.

The expiration date and time for the detached licenses. For example, 2025-01-01T23:59:59.000Z, which represents January 1, 2025, at 11:59:59 PM in UTC.

The number of days that seats (licenses) were detached from the cloud license manager server during the report period.

The total number of seats for the product that were not detached from the cloud license manager server when the report was generated.

NOTE   In certain cases, the value may not be fully accurate. Improvements are planned for future releases.

The status codes related to the operation of the Sentinel Licensing API functions.

The creation date and time of the event data. For example, 2025-01-01T23:59:59.000Z, which represents January 1, 2025, at 11:59:59 PM in UTC.

The domain name of the logged-in machine.

The host name of the logged-in machine.

The user name of the logged-in machine.

Reserved for future use.

The virtual machine information for the logged-in machine.

A unique identifier assigned to a specific tenant (software vendor) during the vendor's deployment in the Thales-hosted cloud.

A unique identifier that is randomly generated during the licensed application's execution and is used to identify each login, logout, detach, and cancel detach call.

A unique number that is associated with a given vendor code and batch code (namespace).

The unique product identifier defined by the vendor in Sentinel EMS.

The product name assigned in Sentinel EMS.

The version number associated with the usage data for the events schema, such as version 1, when the schema was initially introduced.

The expiration date and time for the detached licenses. For example, 2025-01-01T23:59:59.000Z, which represents January 1, 2025, at 11:59:59 PM in UTC.

The status codes related to the operation of the Sentinel Licensing API functions.

The usage count per feature.

The identifier that identifies the customer.

The name of the feature.

The version of the feature.

Name of the end user who consumed the license.

Start date of the period for which the usage is collected on the cloud.

End date of the period for which the usage is collected on the cloud.

IP address of the machine where the license is consumed.

The information related to the software vendor.

The identifier that identifies an entitlement.

The identifier that identifies a product key.

The name of the product.

Date on which the usage is created on client machines.

Date on which the usage is collected to the cloud.

Type of transaction, such as login, logout, or refresh.

The identifier that identifies an entitlement.

The identifier that identifies a product key.

 The identifier that identifies a customer.

The name of the product.

The version of the product.

The name of the feature.

The version of the feature.

The name of the user.

The usage count that was consumed for the session.

The number of users who consumed the licensed software.

The unique identifier for a session. 

The information related to the software vendor.

An automatically generated unique ID that is assigned to the feature.

The name of the feature.

The feature version.

An automatically generated unique ID that is assigned to features.

The name of the feature.

The feature version.

An automatically generated unique ID that is assigned to features.

The name of the feature.

An automatically generated unique ID that is assigned to the user.

An automatically generated unique ID that is assigned to features.

The name of the feature.

The feature version.