docs: Update license utilization reporting topic (#3491)
This commit is contained in:
1 parent
28de3d712b
commit
736f45574b
1 file changed
+4
-4
@@ -9,7 +9,7 @@ description: >-
|
||||
|
||||
Automated license utilization reporting sends license utilization data to HashiCorp without requiring you to manually collect and report them. It also lets you review your license usage with the monitoring solution you already use (for example Splunk, Datadog, or others) so you can optimize and manage your deployments. Use these reports to understand how much more you can deploy under your current contract, protect against overutilization, and budget for predicted consumption.
|
||||
|
||||
Automated reporting shares the minimum data required to validate license utilization as defined in our contracts. They consist of mostly computed metrics and will never contain Personal Identifiable Information (PII) or other sensitive information. 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.
|
||||
Automated reporting shares the minimum data required to validate license utilization as defined in our contracts. They consist of mostly computed metrics and will never contain Personal Identifiable Information (PII) or other sensitive information. 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. This process is GDPR compliant.
|
||||
|
||||
## Enable automated reporting
|
||||
|
||||
@@ -30,7 +30,7 @@ Upgrade to a release that supports license utilization reporting. These releases
|
||||
|
||||
### 3. Check logs
|
||||
|
||||
Automatic license utilization reporting will start sending data within 24 hours. Check the product logs for records that the data sent successfully.
|
||||
Automatic license utilization reporting will start sending data within roughly 24 hours. Check the product logs for records that the data sent successfully.
|
||||
The records are sent as system events.
|
||||
You can use [`file sync`](/boundary/docs/configuration/events/file) to configure a file where Boundary logs events.
|
||||
|
||||
@@ -77,7 +77,7 @@ If your installation is air-gapped or your network doesn’t allow the correct e
|
||||
}
|
||||
```
|
||||
|
||||
In this case, reconfigure your network to allow egress and check back in 24 hours.
|
||||
In this case, reconfigure your network to allow egress and check back in roughly 24 hours.
|
||||
|
||||
## Opt out
|
||||
|
||||
@@ -111,7 +111,7 @@ $ export OPTOUT_LICENSE_REPORTING=true
|
||||
|
||||
Now restart your system.
|
||||
|
||||
Check your product logs 24 hours after opting out to make sure that the system isn’t trying to send reports.
|
||||
Check your product logs roughly 24 hours after opting out to make sure that the system isn’t trying to send reports.
|
||||
|
||||
If your configuration file and environment variable differ, the environment variable setting will take precedence.
|
||||
|
||||
|
||||
Reference in new issue
Block a user