Licensing & Reporting
Licensing & Reporting
Cloudhouse's license and reporting features enables you to ensure you are compliant with your End User Licensing Terms & Conditions, as well as helping you understand application usage patterns within your business; this includes Information around how many people are using each application, on what OS, when and how often.
Please note, while user and machine name information is collected, it is automatically hashed using SHA256 algorithm before it is sent over HTTPS, or written to a file on a local fileshare. Hashing the data ensures that it remains private to the customer, and only the customer - no user, or machine identifiable information is ever sent to Cloudhouse in usage data.
Deployment Event Reporting
A deployment reporting event is recorded each time the Cloudhouse.Container.Deployment.exe is triggered, whether it is by command line, script or deployment tool. The Deployment event will attempt to log each deploy and uninstall event up to three times, if the connection to the fileshare or the https://containers.cloudhouse.com fails, then deployment will stop and record an error in the Windows Application log.
- Deploy type will be either machine or user.
- Event types will be either deploy or uninstall.
Note, for a deployment that uses a fileshare to report usage, the path to the fileshare is provided on the command line when the Container is deployed, refer to Deploying Containers for details. The reporting location is recorded in the server, or desktop's registry and not within the Container's configuration, so that the same Container can be deployed to different servers and desktops and report usage to different data stores if so required.
If the Container is deployed into a Gold Image, and machines are then created from this Gold Image, only a single deployment event will be recorded when the Container is deployed into the Gold Image - deployment events will not be reported when the image is cloned.
Usage Event Reporting
An asynchronous usage event is recorded each time the Cloudhouse.Container.Run.exe is triggered during an application start and stop event. The Run event will attempt to log each start and stop event up to three times, if the connection to https://containers.cloudhouse.com, or fileshare, is unavailable or in-use then it will stop, and record an error in the Windows Application log. Stop events will include the application terminating unexpectedly.
Automated HTTPS Usage Reporting
By default, Containers will report usage over HTTPS (Port 443) to https://containers.cloudhouse.com. A valid reporting token must be placed into the Container's root folder. A Container without a valid token will not deploy successfully. Please contact your Cloudhouse representative to arrange the issuing of your token. The https usage event is approximately 1700 bytes.
Manual File-based Usage Reporting
Containers can be deployed to record deployment and usage events in comma separated value (CSV) files, on a centrally located fileshare on the Customer's network. This format is used so that the data can be imported into a customer’s existing 3rd party reporting system, and submitted to Cloudhouse for License and Billing purposes - refer to Submitting Licensing Data for more information.
Each recorded event is approximately 260 bytes, and it is written to the file Hashed$UserSID$MachineID_usage.csv
Please note, in order to create a valid file name, special characters that are not supported by the file system will be removed from the hash that is generated for the User SID and Machine SID.
The following data is written to the CSV file
UTC_TimeStamp, UsageId, PackageId, Event, Operating_System, CPU_Core_Count, Deploytype, UserSidHash, MachineSidHash
Submitting Usage Reporting Data
To comply with your License Terms & Conditions, you will need to manually submit your locally collected usage data to Cloudhouse, please refer to Submitting Licensing Data for further details.
Backup & Archiving
Under License usage terms, Cloudhouse has the right to audit customers for up to three years, for this reason Cloudhouse recommend maintaining back ups, and archives of the data for up to 3 years. All data on the file share should be backed up as part of your company's standard backup and archiving policies. Once data has been submitted to Cloudhouse it can be stored in the archive, until then Cloudhouse recommends keeping the data on the file share. Cloudhouse has designed the system to require minimal disk space, although exact requirements will depend on the scale of your deployment and usage.