Skip to content

Activity Log ​

Activity Log answers who changed what, and when. It includes actions taken while impersonating a client, so work done on a customer's behalf is attributed to the administrator who did it.

Overview ​

URL: /admin/activity-logs

The Activity Log tab of Logs

Open Logs in the sidebar, then the Activity Log tab, the second tab after Executions. Since panel 1.9.3 the activity log is a tab of Logs instead of a second sidebar entry under Logs, and Logs stays highlighted in the sidebar while you are on it. The address is unchanged.

ColumnMeaning
TimeWhen the action happened.
ActorWho did it.
EventWhat kind of change it was, for example created, updated, or deleted.
ObjectWhat was changed.
DescriptionThe detail of the change.
ResellerThe reseller the change belongs to, when it applies to one.

The administrator API ​

Since panel 1.9.4, the administrator REST API reads this log:

Method and pathWhat it does
GET /api/admin/activity-logThe entries, newest first, with the filters of this page.
GET /api/admin/activity-log/{id}One entry, with the new and previous values its detail view shows.
GET /api/admin/activity-log/filter-optionsThe values the event, subject_type, and causer_type filters take.

Secrets were replaced with [redacted] when the entry was written. Resellers read the log of their own accounts on the reseller API; see the reseller Activity Log.

Activity Log or Logs? ​

The two pages answer different questions and it is worth keeping them apart:

  • Activity Log is about people. Someone changed a setting, created an account, or deleted a domain.
  • Logs is about the server. An action ran, a service wrote to its log file, a certificate was requested.

If you are investigating "why did this setting change", start here. If you are investigating "why did this action fail", start in Logs.

Impersonation ​

When an administrator signs in to a client account to help with something, the entries stay attributed to the administrator. The client's own record does not absorb changes an administrator made.

Certificate private keys ​

Since panel 1.9.4, each time a client opens or downloads the private key of a certificate with Show private key or Download private key on the client SSL Certificates page, or reads it over the client API, an entry records it: "Private key of the SSL certificate for domain revealed", with the channel (panel or API). A request the server could not answer is recorded as "requested, not available". The key itself is never recorded.

Since panel 1.9.5, each admin panel sign-in link an API key asks for with POST /api/admin/generate-sso-token adds an entry, "Admin API: admin panel login link issued". The entry names the key by its id and name, the administrator the link signs in as, and the address the call came from; open the entry, or read it with GET /api/admin/activity-log/{id}, to see them. The link itself is never recorded, and a link whose entry cannot be written is withdrawn. See Admin panel sign-in links.

Granting or revoking Allow writes that run commands as root on a key over the API adds an entry as well, with the key that made the change. See The permission over the API.