Plugin settings
Everything the plugin needs to configure lives on one screen: Tools → helloLOG in WP-admin, in the Settings tab (the same page also has a Logs tab — see Reading logs in WP-admin). Settings has three tabs.
Connection
Where the site key lives.
- API key — paste the key from the dashboard
and click Save API key. The field shows the last four characters of
whatever's currently stored (
••••ab12); leaving it blank on save keeps the existing key. - Send test event — fires a one-off event straight to the backend, bypassing the queue. This is the only thing that flips a saved key to active — saving alone stores it but leaves sensors detached until a test event succeeds.
- Remove API key — clears the stored key and detaches sensors immediately. Asks for confirmation first, since every event from the site is rejected until a new key is saved.
WP-CLI equivalents: wp hellolog set-token <token>, wp hellolog test,
wp hellolog clear-token — see the full command reference.
Filters
What gets recorded.
- Anonymize client IPs — strips the lowest byte before an IP leaves
the site (
/24for IPv4,/48for IPv6). Off by default. - Sensors — every registered sensor, toggled individually. Turning one off means its hooks never even register, not just that events get discarded afterward. A search box filters the list by key or label.
WP-CLI equivalents: wp hellolog sensors (list, with enabled state),
wp hellolog enable-sensor <key> / wp hellolog disable-sensor <key>.
IP anonymization has no CLI toggle — it's Settings-only.
Diagnostics
Read-only view of the local queue: current counts for Pending (waiting for the next flush), Sending (claimed by the worker, not yet acknowledged) and Dead (hit max retries or a permanent failure), plus a reminder that the queue table drains every 60 seconds on its own.
There's no button here to act on a dead pile — that's a CLI-only
operation:
wp hellolog status # same counts, from the terminal
wp hellolog requeue-dead # dead -> pending
wp hellolog flush # send them now instead of waiting
See Troubleshooting for the full recovery walkthrough.
Updates
The plugin updates itself from our
GitHub releases:
when a new version is published, it shows up on the Plugins screen
like any other plugin update — one click and you're current. The check
runs against the latest release at most twice a day and only ever
installs the official release asset from the
hellolog-io/hellolog-plugin repository.
Turning the built-in updater off
Managed setups that deploy plugins from version control or a central
tool can disable the updater entirely with one filter (in a mu-plugin
or your theme's functions.php):
add_filter( 'hellolog_self_update', '__return_false' );
With the filter in place the plugin no longer offers updates anywhere — the site has deliberately lost that capability. The Diagnostics tab then shows a direct link to the newest build so manual installs stay a download away:
https://github.com/hellolog-io/hellolog-plugin/releases/latest/download/hellolog.zip
That URL always points at the latest release's zip, ready for
Plugins → Add New → Upload Plugin or unzipping into
wp-content/plugins/.