AdminBolt usage statistics ​
Since panel 1.9.5, each AdminBolt server reports to AdminBolt which AdminBolt software and services it runs, how it is set up, and how its panel updates went. The reports carry versions, settings, and counts only, and nothing that identifies a customer. AdminBolt uses them to choose which combinations of operating system, CloudLinux, web server, PHP versions, and modules to test before a release, and to learn about a failed update without waiting for a support ticket.
AdminBolt usage statistics shows what is sent and what is never sent, the last report, and the switch that stops the reports.
Overview ​
URL: /admin/settings/usage-statistics
Open it from Settings > System > AdminBolt usage statistics in the sidebar. The page subheading reads "What this server reports to AdminBolt, and the switch that stops it."
The reports are on by default, on new servers and on servers updated to 1.9.5. A server installed with the installer's --no-telemetry option starts with them off.
On a server updated to 1.9.5 with the reports on, every administrator gets a notification once: This server now sends AdminBolt usage statistics, with a link to this page.
What is sent ​
The page lists it under What is sent:
Once a day and after every update or change: the versions of AdminBolt, the operating system, CloudLinux, the web server, PHP, the main services and the modules, the hardware size, the update, backup and cluster settings, the number of accounts, domains, databases and resellers, and the result of every update. AdminBolt uses it to choose what to test before a release and to learn about failed updates.
In more detail:
- The server's environment, once a day at a time each server picks at random, and after every panel update, web server switch, and module, application, or PHP version change. It includes the versions of AdminBolt, bolt-agent, the operating system and its kernel, CloudLinux, the web server, PHP, the main services, and the modules, the kind of platform the server runs on, such as a cloud provider or a virtual machine, the number of CPU cores, the memory and disk size, whether the server is a standalone server, a hub, or a node, settings such as automatic updates, backups, and the DNS cluster as yes or no, and the number of accounts, domains, databases, and resellers.
- The result of every panel update, shortly after it ends: whether it succeeded, how long it took, the versions before and after, and, for a failure, the phase and the reason, and the names of the packages, modules, and upgrade steps that failed.
Every value is a version, a fixed choice, a yes or no, or a number. The server is known by a random Server ID, which the page shows, and not by its name or address.
What is never sent ​
The page lists it under What is never sent:
Hostnames, IP addresses, domain names, user names, e-mail addresses, licence keys, file paths, configuration files, log lines and command output.
What AdminBolt keeps ​
When a report arrives, AdminBolt looks up the hosting provider and the country of the server once, from the address the report comes from. That address is not stored.
For each Server ID, AdminBolt keeps when the server was first and last seen, its latest report, the hosting provider, and the country. Earlier reports are kept only where a value changed, so the history is a list of changes. That history and the record of each panel update are kept for 12 months.
The page ​

| Field | What it shows |
|---|---|
| Send usage statistics | Whether the server sends the reports. |
| Server ID | The random ID the reports carry, or Not created yet. |
| Last report | When the last report was sent, in UTC, or Not sent yet. |
Save stores the switch, with the notification "Usage statistics are on." or "Usage statistics are off."
Show last report opens Last report: "The exact report this server last sent, as AdminBolt received it.", with the time it was sent and its full content.

Turning the reports off ​
Turn Send usage statistics off and click Save. The server then:
- sends no more reports, and drops the reports waiting to be sent,
- stops the report about installs as well, the one the installer's
--no-telemetryoption turns off, - keeps its Server ID and the last report, so Show last report still shows what was sent before.
Turning the switch off does not remove reports AdminBolt has already received. Turning it on again schedules a new report.
When the setting cannot be saved, the notification says so: "The setting could not be saved. Check that /etc/bolt/bolt-config.ini is writable."
When AdminBolt cannot be reached ​
The panel works as if the reports did not exist. Reports are sent in the background and tried again later, and they are put off while the server is busy. Nothing is shown to administrators or customers. Reports that cannot be delivered wait for up to 7 days and are then dropped.
Related pages ​
- System Updates - the updates whose results are reported.
- Installing AdminBolt - the
--no-telemetryoption.