Activity Log

The Activity Log screen lives at Logify > Activity Logs and lists every event recorded by the plugin, newest first.

Columns

Date — when the event happened (in your site's timezone).
Severity — a colour-coded badge: Info, Notice, Warning, Alert, High, Critical, Emergency.
IP Address — the request's source IP.
User — who took the action, or "System" for unattended events.
Event — the event category (user, post, plugin, and so on).
Object — what was acted on (post title, plugin name, user login, …).
Action — the specific action (created, updated, login, deleted, …).
Description — a human-readable summary of the event.

Click View Details in any row to open a modal showing the full event payload, including metadata, request URI, user agent, and session ID.

Filtering

Above the list table you'll find a filter bar with:

Event Type — show only user, post, plugin, and so on.
User — narrow to a specific user.
Severity — show only events at or above the chosen severity.
Date From / Date To — restrict to a date range.
Search — match against description, object name, IP, or username.

Click Filter to apply, or Reset to clear.

Quick CSV Export

The filter bar has an Export CSV button that downloads whatever you're currently looking at — the same filters apply to the export. Useful for sending an auditor "the user activity for last week" without leaving the screen.

For more formats (JSON, HTML, plain text, PDF) use Tools → Export Logs.

Bulk Delete

Tick the checkboxes on the left, choose Delete selected from the Bulk actions dropdown, and click Apply. The action requires the manage_options capability and a valid nonce.

Sorting

Click the Date or Severity column header to sort. The default order is most recent first.

Notes

All event timestamps are stored in GMT but displayed in your site's timezone on this screen.
Logify excludes WooCommerce post types and nav menu items from post tracking by default to keep the log readable. Use the kc_lf_trackable_object_types and related filters to adjust.
Brute-force login attempts are aggregated automatically — the first few failures are logged individually, then a single "Brute-Force Detected" event is recorded for the remainder of the window.