Manage usage reporting
Review default aggregate reporting and inspect or change the preference.
LogForge · Runs in your infrastructure
Before you begin
On by default: the LogForge server sends aggregate product usage to
https://usage.logforge.dev/v1/reports. Reporting can begin before initial setup finishes.
If your policy forbids outbound reporting, arrange the network restriction before startup. There is no reporting setting in operator.env.
| Included | Excluded |
|---|---|
| Generated installation ID, product version, platform, architecture, agent/workload counts, feature counters | Names, customer logs, queries, files, terminal input/output, secrets |
To inspect or change the preference, sign in to LogForge in your browser as Owner or Admin. No host shell is needed.
Inspect and change reporting
- Open Settings > Account > Usage reporting.
- Check Reporting, Delivery, Queued reports, and Last delivery.
- Open Inspect a report preview to see the local payload. Previewing does not send it.
- To disable reporting, enter a Reason for changing reporting of at least three characters. Choose Turn reporting off.
- Wait for Reporting preference saved. Confirm Reporting: Off, then reload to check it persisted.
Check: the reloaded preference is Off. A failed save does not turn reporting off.
Effect: turning reporting off clears local reporting counters and queued reports. It keeps workload monitoring, saved logs, metrics, and alerts running. It does not delete reports already received by LogForge.
To resume, enter a reason, choose Turn reporting on, and check the saved preference. Delivery can take time; current and recent reports retry if the receiver is unavailable.
If the change fails
Problem: saving fails or delivery keeps retrying.
Why it matters: saving the preference and delivering reports are separate operations.
Next step:
- Confirm Owner/Admin access and a reason of at least three characters.
- Read the error and reload the saved preference before retrying.
- For delivery failures, check approved outbound connectivity. Keep credentials out of the receiver URL; do not reinstall the LogForge server.
Continue with your first workload or Data and recovery.