Automated license utilization reporting

This page provides information on the data HashiCorp collects to monitor Enterprise product usage and license utilization. Learn how to enable or opt out of automatic reporting. Review sample payloads and logs.

Introduction

Automated reporting sends product and license utilization data to HashiCorp without requiring you to manually collect and report them.

It shares data required to validate license utilization as defined in our contracts. The detailed product usage metrics also inform our feature roadmap. They consist of computed metrics and never contain Personal Identifiable Information (PII) or other sensitive information, which you can verify by reviewing the full list of metrics. Inform your account manager if you have concerns with any of the data.

Automated reporting shares the data with HashiCorp using a secure, unidirectional HTTPS API and makes an auditable record in the product logs each time it submits a report. The reporting process is GDPR compliant and submits reports roughly once every 24 hours.

Enable automated reporting

To enable automated reporting, you need to make sure that outbound network traffic is configured correctly and upgrade your enterprise product to a version that supports it. If your installation is air-gapped or network settings are not in place, automated reporting will not work.

1. Allow outbound HTTPS traffic on port 443

Make sure that your network allows HTTPS egress on port 443 from https://reporting.hashicorp.services by allow-listing the following IP addresses:

• 100.20.70.12
• 35.166.5.222
• 23.95.85.111
• 44.215.244.1

2. Upgrade

Upgrade to a release that supports license utilization reporting. These releases include:

• Nomad v1.7.0 and later

3. Check logs

Automatic license utilization reporting will start sending data within roughly 24 hours. Check the product logs for records that the data sent successfully.

Instructions on how to check logs.

[DEBUG] core.reporting: beginning snapshot export
[DEBUG] core.reporting: creating payload
[DEBUG] core.reporting: marshalling payload to json
[DEBUG] core.reporting: generating authentication headers
[DEBUG] core.reporting: creating request
[DEBUG] core.reporting: sending request
[DEBUG] core.reporting: performing request: method=POST url=https://reporting.hashicorp.services
[DEBUG] core.reporting: recording audit record
[INFO]  reporting: Report sent: auditRecord={"payload":{"payload_version":"1","license_id":"d2cdd857-4202-5a45-70a6-e4b531050c34","product":"nomad","product_version":"1.6.0","export_timestamp":"2023-05-26T20:09:13.753921087Z","snapshots":[{"snapshot_version":1,"snapshot_id":"0001J724F90F4XWQDSAA76ZQWA","process_id":"01H1CTJPC1S8H7Q45MKTJ689ZW","timestamp":"2023-05-26T20:09:13.753513962Z","schema_version":"1.0.0","service":"nomad","metrics":{"nomad.billable.nodes":{"key":"nomad.billable.nodes","kind":"counter","mode":"write","value":33}}}]}}
[DEBUG] completed recording audit record
[DEBUG] core.reporting: export finished successfully

If your installation is air-gapped or your network doesn’t allow the correct egress, logs will show an error.

[DEBUG] core.reporting: beginning snapshot export
[DEBUG] core.reporting: creating payload
[DEBUG] core.reporting: marshalling payload to json
[DEBUG] core.reporting: generating authentication headers
[DEBUG] core.reporting: creating request
[DEBUG] core.reporting: sending request
[DEBUG] core.reporting: performing request: method=POST url=https://reporting.hashicorp.services
[DEBUG] core.reporting: error status code received: statusCode=403

In this case, reconfigure your network to allow egress and check back in 24 hours.

Opt out

If your installation is air-gapped or you want to manually collect and report on the same license utilization metrics, you can opt-out of automated reporting.

Manually reporting these metrics can be time consuming. Opting out of automated reporting does not mean that you also opt out from sending license utilization metrics. Customers who opt out of automated reporting are still required to manually collect and send license utilization metrics to HashiCorp by using the nomad operator utilization command.

You may disable product usage metrics separately from license utilization reporting, so your automated license reporting can exclude product usage metrics, or you can include product usage metrics in offline reports.

You have two ways to opt out of automated reporting: HCL configuration or environment variables.

For HCL configuration, use the reporting block in your Nomad server agent config file.

reporting {
  license {
    enabled = false
  }
}

The reporting.license.enabled option toggles automated reporting. Nomad still gathers license utilization data for manual reporting.

To disable detailed product usage metrics for both automated and offline reporting, use the reporting.disable_product_usage_reporting option.

reporting {
  disable_product_usage_reporting = true
}

Alternatively, you can use the following environment variables in your Nomad server agent's environment.

export OPTOUT_LICENSE_REPORTING=true
export OPTOUT_PRODUCT_USAGE_REPORTING=true

If your configuration file and environment variable differ, the environment variable takes precedence.

After changing configuration, follow the "Run an agent" instructions to restart your Nomad server and apply your changes.

The Nomad agent emits logs at startup confirming your settings. This example shows automated reporting enabled, but without product usage metrics.

[INFO]  nomad.reporting: reporting agent is enabled and configured
[DEBUG] nomad.reporting: product usage reporting disabled via agent configuration
[INFO]  nomad.reporting: product usage reporting is disabled; usage metrics data will not be collected

You can also check your product logs roughly 24 hours after opting out to make sure that the system isn’t trying to send reports, or that the detailed usage metrics are all reporting 0.

Full list of metrics

This table lists all the metrics that we collect.

Only nomad.billable.* metrics are collected if product usage metrics are disabled.

The values are all integers for pre-determined values. We do not collect any strings that might identify proprietary information.

Example payload

HashiCorp collects utilization data in the following JSON format.

{
  "version": "2",
  "mode": "manual",
  "timestamp": "2025-09-26T17:20:41.189292719Z",
  "signature": "...",
  "checksum": ...,
  "snapshots": [
    {
      "snapshot_version": 2,
      "id": "0001MDDJT442VWX01R4K21A22D",
      "timestamp": "2025-09-26T13:20:04.598859749-04:00",
      "schema_version": "2.1.0",
      "product": "nomad",
      "process_id": "01K63GH92XVS1V95RM7509N303",
      "metrics": {
        ...
        "nomad.billable.clients": {
          "key": "nomad.billable.clients",
          "value": 25,
          "mode": "write"
        },
        ...
      },
      "product_version": "1.10.6",
      "license_id": "...",
      "checksum": ...,
      "metadata": {}
    }
  ]
}

You can inspect the full payload in the server logs, or by running the nomad operator utilization command.