Get Zabbix API version information.

This tool retrieves the current version of the Zabbix API you are connecting to. This is useful for understanding API capabilities and ensuring compatibility with specific features that may be version-dependent.

Returns: dict: Contains 'version' key with the API version string (e.g., "6.0.10"). On error, contains 'error' key with the error message.

Get hosts from Zabbix with optional filtering.

Retrieves a list of monitored hosts from Zabbix. You can filter by host IDs, groups, templates, proxies, or use search criteria. This is useful for discovering which hosts are available in your monitoring system.

Create a new host in Zabbix.

Adds a new monitored host to Zabbix. This is essential for starting to monitor a new server or device. You must specify at least a host name and groups. You can optionally configure interfaces (for agent/SNMP communication) and link templates.

Update an existing host in Zabbix.

Modifies properties of an existing host. You can change the technical name, visible name, status (enable/disable monitoring), or description. Only specify the fields you want to change.

Delete hosts from Zabbix.

Permanently removes one or more hosts from Zabbix. This will delete all associated data including history and alerts. Use with caution as this is a destructive operation.

Get host groups from Zabbix.

Retrieves host groups with optional filtering. Host groups are used to organize and manage hosts collectively, applying templates, permissions, and maintenance windows to multiple hosts at once.

Create a new host group in Zabbix.

Host groups serve as containers for organizing hosts. They're essential for applying permissions, templates, and maintenance windows to multiple hosts at once.

Update an existing host group in Zabbix.

Modifies properties of an existing host group. You can change the group's name. Only specify the fields you want to change.

Delete host groups from Zabbix.

Permanently removes one or more host groups. Hosts in deleted groups will no longer be members of that group (though the hosts themselves remain unless explicitly deleted).

Get templates from Zabbix.

Templates are reusable collections of items, triggers, and graphs that can be applied to hosts. They standardize monitoring across multiple servers with the same role.

Create a new template in Zabbix.

Templates define the monitoring configuration (items, triggers, graphs) that can be reused across multiple hosts. Creating custom templates enables standardized monitoring for specific applications or server types.

Update an existing template in Zabbix.

Modifies properties of an existing template. You can change the name or description. Only specify the fields you want to change.

Delete templates from Zabbix.

Permanently removes one or more templates. Hosts that have the deleted templates applied will lose those template's items, triggers, and graphs. The hosts themselves remain unchanged.

Get items (metrics) from Zabbix.

Items are the data sources in Zabbix - they define what metrics are collected and how (protocol, interval, etc.). Each item produces a stream of values over time.

Create a new item in Zabbix.

Items define what data is collected from a host. Each item specifies the metric name, how to collect it (agent, SNMP, etc.), what interval to use, and what data type to store.

Update an existing item in Zabbix.

Modifies properties of an existing monitoring item. You can change the name, collection interval, units, or status. Only specify the fields you want to change.

Delete items from Zabbix.

Permanently removes one or more items from monitoring. The item's historical data is typically removed as part of cleanup, though this depends on Zabbix configuration.

Get item prototypes from Zabbix.

Item prototypes are template items created by discovery rules that generate actual items dynamically based on discovered entities.

Get triggers from Zabbix.

Triggers are rules that define when a problem occurs based on item values. They evaluate expressions against collected metrics and transition between problem and normal states.

Create a new trigger in Zabbix.

Triggers define the conditions under which problems are detected. They use expressions to evaluate item values and determine when to transition from normal to problem state.

Update an existing trigger in Zabbix.

Modifies properties of an existing trigger. You can change the description, expression, priority, status, or comments. Only specify fields you want to change.

Delete triggers from Zabbix.

Permanently removes one or more triggers. Hosts will no longer generate alerts for these conditions. Historical trigger data and associated problems are typically retained.

Get problems from Zabbix.

Problems are active trigger states that indicate issues with monitored infrastructure. Each problem is associated with a trigger and can be acknowledged by operators.

Get events from Zabbix.

Events represent state changes in the system - when triggers transition from normal to problem and back, or recovery events. Each event has a timestamp, trigger, and can be acknowledged to show operators have seen the alert.

Acknowledge events in Zabbix.

Mark events (problems/alerts) as acknowledged to show that operations staff are aware of and working on the issue. Acknowledged events can also be closed if resolved.

Get history data from Zabbix.

Retrieves the raw metric values collected by items. History contains all individual collected data points with timestamps, allowing detailed analysis of system behavior over time.

Get trend data from Zabbix.

Trends are aggregated (summarized) historical data providing min/max/average values at hour-long intervals. Trends use less storage than raw history while preserving statistical information for long-term analysis.

Get users from Zabbix.

Users represent people with access to the Zabbix system. Each user has authentication credentials and permission level determining what they can view and modify.

Create a new user in Zabbix.

Creates a new user account with specified credentials and group membership. New users inherit permissions from their assigned user groups.

Update an existing user in Zabbix.

Modifies properties of an existing user account. You can change name, surname, password, or user type. Only specify the fields you want to change.

Delete users from Zabbix.

Permanently removes user accounts from the system. The user's access will be immediately revoked. Historical data and previous actions by the user are retained for audit purposes.

Get proxies from Zabbix.

Proxies act as data collection points for Zabbix, allowing monitoring of remote networks without direct connectivity. Proxies collect data locally and report to the Zabbix server.

Create a new proxy in Zabbix.

Proxies allow distributed monitoring by collecting data from remote networks and reporting to the central Zabbix server. Useful for firewall-separated networks or high-latency connections.

Update an existing proxy in Zabbix.

Modifies properties of an existing proxy. You can change the name, operating mode, or description. Only specify the fields you want to change.

Delete proxies from Zabbix.

Permanently removes proxy definitions. Hosts assigned to deleted proxies will need to be reassigned to other proxies or the server. Data from deleted proxies is typically retained.

Get maintenance periods from Zabbix.

Maintenance windows define periods when monitoring is paused for planned upgrades, maintenance, or testing. Alerts are suppressed during maintenance periods.

Create a new maintenance period in Zabbix.

Schedules a maintenance window when monitoring alerts are suppressed. Useful for planned upgrades, patching, or system maintenance without triggering false alarms.

Update an existing maintenance period in Zabbix.

Modifies properties of an existing maintenance window. You can change the name, start time, end time, or description. Only specify the fields you want to change.

Delete maintenance periods from Zabbix.

Cancels maintenance windows immediately, resuming alert generation. If the maintenance period has already passed, historical event suppression is retained.

Get actions from Zabbix.

Actions define automated responses to problems/triggers. They specify what happens when problems occur - sending notifications, executing remote commands, etc.

Get media types from Zabbix.

Media types define communication channels for sending notifications (email, SMS, webhooks, etc.). Actions use media types to deliver alerts to users and integrations.

Get graphs from Zabbix.

Graphs visualize item data over time, displaying metric values in line/bar/pie charts. Graphs can be included in dashboards, reports, and custom views for data analysis.

Get discovery rules from Zabbix.

Discovery rules automatically detect items, triggers, and interfaces from network resources. They enable dynamic host and item management without manual configuration.

Get network discovery rules from Zabbix.

Network discovery (drule) rules perform network scanning to discover hosts and services. They can scan for active devices, open ports, and available services in CIDR ranges.

Export Zabbix configurations.

Exports monitored hosts, templates, and their complete configurations to JSON, XML, or YAML format. Useful for backup, migration, disaster recovery, or sharing configurations.

When you export templates or hosts, the export includes:

• All associated items (metrics/data sources)

• All triggers and their dependencies

• Discovery rules and prototypes

• Graphs and visualizations

• Macros and variable definitions

• Host groups and interfaces (for hosts)

• Inventory data (for hosts)

• And all other configuration elements

Import configurations into Zabbix.

Imports hosts, templates, and other configurations from JSON or XML format. Useful for migration, cloning, or restoring configurations.

Get SLAs from Zabbix.

Service Level Agreements (SLAs) define uptime and availability targets for services. They track compliance with service objectives and generate reports on availability.

Get services from Zabbix.

Services represent business capabilities or applications (e.g., 'Web Application', 'Database'). Services can depend on other services, creating hierarchies for tracking dependencies.

Get scripts from Zabbix.

Scripts are custom automation routines that can be executed on monitored hosts or the server. They can be triggered manually or by actions to automate remediation or configuration tasks.

Execute a script on a host in Zabbix.

Runs a custom script on a specified host. Used for executing remediation tasks, configuration changes, or diagnostic commands remotely.

Get user macros from Zabbix.

User macros are variables that can be referenced in items, triggers, and scripts. They allow parameterization of monitoring configurations with custom values.

Create a new host macro in Zabbix.

Host macros define custom variables for specific hosts. They can be referenced in items and triggers using {$MACRO_NAME} syntax, allowing dynamic configuration without editing items.

Delete host macros from Zabbix.

Permanently removes host-level macro definitions. Items and triggers using this macro will no longer be able to reference it, potentially causing parsing errors.