auditlog_get
Read-only
Retrieve Zabbix audit log entries to review configuration changes and login events for security, compliance, and forensic investigations; filter by time window or user to narrow results.
Instructions
Retrieve audit log entries (read-only). The audit log records every configuration change and login/logout event in Zabbix, including who made the change, when, what object was affected, and the old/new values. Essential for security auditing, compliance, and forensic investigation. Use time_from/time_till to limit the time window and userids to focus on a specific user's activity. Results can be large -- always use limit or time filters. The newest entries come first unless a sort is given, so 'limit' keeps the latest ones.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of results to return. | |
| filter | No | Return only results whose properties exactly match the given values (a single value or a list of values per key). Example: {"status": 0} or {"status": [0, 1]}. Keys: action, auditid, clock, ip, recordsetid (6.0+), resource_cuid (7.0+), resourceid, resourcename, resourcetype, userid, username (6.0+). Text properties cannot be filtered; use 'search' for them. | |
| output | No | Properties of the auditlog object to return. Pass 'extend' for all, 'count' for the number of matches only, or a list of property names. Default when omitted: auditid, userid, action, resourcetype, clock. Properties: action, auditid, clock, details (6.0+), ip, recordsetid (6.0+), resource_cuid (7.0+), resourceid, resourcename, resourcetype, userid, username (6.0+). | |
| search | No | Return results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: details (6.0+), ip, resourcename, username (6.0+). | |
| server | No | Target Zabbix server. Available: default. Defaults to 'default' if omitted. | |
| userids | No | Return only audit log entries for actions performed by these user IDs. | |
| auditids | No | Return only audit log entries with the given IDs. | |
| raw_json | No | Strips the security disclaimer preamble from the response so it is pure JSON. Default: false. Requires the bearer token to have 'allow_raw_json' explicitly enabled by an operator in the admin portal - tokens without that policy receive a PolicyError instead. WARNING: setting true bypasses the prompt-injection mitigation marker that wraps untrusted Zabbix data (host names, item descriptions, problem text). LLM clients (Claude, GPT, Cursor, ...) should leave this false; only programmatic non-LLM consumers (Python scripts, n8n workflows that json.loads the result) should set true. | |
| sortfield | No | Sort by one or more of: auditid, userid, clock (a list for several; pair with 'sortorder'). No other property is sortable. When omitted, the result is sorted by auditid with the newest first. | |
| sortorder | No | Sort order: 'ASC' (ascending) or 'DESC' (descending). 'DESC' while 'sortfield' is omitted (newest first); 'ASC' alone returns the oldest first. | |
| time_from | No | Return only audit log entries created after this time (Unix timestamp, ISO 8601 date-time such as 2026-04-01T08:00:00Z, or a relative time such as now-1h, now/d or now-7d/d; a value without a zone is read in the zone resolved for the call) (inclusive). Use for scoping queries to a specific time window. | |
| time_till | No | Return only audit log entries created before this time (Unix timestamp, ISO 8601 date-time such as 2026-04-01T08:00:00Z, or a relative time such as now-1h, now/d or now-7d/d; a value without a zone is read in the zone resolved for the call) (inclusive). | |
| countOutput | No | Return the count of matching results instead of the actual data. | |
| searchByAny | No | If true, return results matching ANY search field (OR). Default is ALL fields (AND). | |
| extra_params | No | Other native auditlog.get parameters, merged into the request as-is. Sub-object selects (value 'extend', 'count' or a list of property names): . Any other key is refused here, because Zabbix would silently ignore it. For a parameter you are sure exists on your release but is not listed, use zabbix_raw_api_call. | |
| searchWildcardsEnabled | No | If true, enable * and ? wildcards in search patterns. |