Audit Log

A chronological log of every state-changing API call that hit the MAC api-server — who, when, what method, which path, and the HTTP status it returned. The page is cluster-scoped (the node picker has no effect here). Read-only operations (GET) are not recorded.

Columns

Column	Notes
Time	Local timestamp of the request
User	<username>(<role>) of the operator; unknown for failed logins
Method	HTTP method (POST, PUT, PATCH, DELETE)
Path	API path that was invoked
Status	HTTP response code (200, 202, 401, 502, …)
Details	Free-form details associated with the entry (when present)

Filters

Three filters sit above the table:

• Filter by username — free-text match (substring) against the actor column
• Method dropdown — All methods, POST, PUT, PATCH, DELETE
• Filter by path — free-text match against the API path

Results are paginated; the page footer shows Page N of M with next / previous controls. The page header shows the total entry count (e.g. API operations history (174 total entries)) so you can see at a glance how active the cluster has been.

Export to CSV

The Export CSV button in the upper right serializes the current filtered view to a .csv file — used during compliance reviews and post-incident reports.

What's Captured

Every state-changing request (writes, power actions, login attempts) is recorded with the caller's identity. Failed logins are included with (unknown) as the role, which makes this page useful for catching brute-force attempts as well as for normal change audits.