---
title: "Automated HTTPS usage reporting (deprecated)"
description: "Deprecated: how older Compatibility Packages reported usage automatically over HTTPS."
product: "Alchemy"
edition: "Public"
type: "reference"
url: "https://docs.cloudhouse.com/public/licensing-and-reporting/deprecated/deprecated-alchemy-automated/"
---
# Automated HTTPS usage reporting (deprecated)

Applies to: `Alchemy`

!!! warning

    This article refers to deprecated automated Usage Reporting functionality which is retained for those customers running earlier releases of Usage Reporting.
    For current versions of Cloudhouse Alchemy Compatibility Packages, please refer to [Licensing and Usage Reporting](https://docs.cloudhouse.com/public/licensing-and-reporting/licensing-and-usage-reporting-overview/index.md) for the most up-to-date information.

By default, Alchemy Compatibility Packages report usage over **HTTPS** to both:

- https://containers.cloudhouse.com
- https://auth.cloudhouse.com

A valid Usage Reporting token must be placed in the Compatibility Package's root folder. A Compatibility Package without a valid token will not deploy successfully. Please contact your Cloudhouse representative to arrange for your token to be issued.

A Usage Reporting token enables the Compatibility Package to establish a connection to our reporting service and submit usage data. The data is linked to the partner and customer for billing purposes. Prior to deployment, the token is a plain text file with a `.token` extension.

Once the Compatibility Package has been deployed, it is encrypted using Microsoft's Data Protection API (**DPAPI**) and given the extension `.stoken.`

In order for usage to be reported correctly, the following entries need to be present in the `chmetadata.json` file in the Compatibility Package (these should be present by default):

```
"AuthUrl": "https://auth.cloudhouse.com/oauth/token",
"UsageReportingUrl": "https://containers.cloudhouse.com/api/UsageEvents"
```

The following data is collected when usage is reported and sent securely over HTTPS:

```
UTC_TimeStamp, UsageId, PackageId, Event, Operating_System, CPU_Core_Count, Deploytype, UserSidHash, MachineSidHash, AAV Version, Deployment Version
```