Monitoring
This page describes how COD connects your existing Zabbix instance, what you need to set up in Zabbix and COD and where the limits are.
What the module does is described on the module page.
As of: November 2026, COD 3.8.6
Documentation contents
- Overview
- Getting started
- Requirements
- Names and addresses
- Network devices
- Time and DNS
- Installation
- Deployment shapes
- Initial setup
- Updates
- Modules
- Network and MikroTik
- Automation
- NAC
- TACACS+
- Firewall
- Captive Portal
- Monitoring
- Backup
- Hypervisor
- OTP
- Passkeepr
- GRC
- Inventory and CMDB import
- Troubleshooting
- Security
- Versions
- Version history
- Support
Documentation
- Overview
- Getting started
- Requirements
- Names and addresses
- Network devices
- Time and DNS
- Installation
- Deployment shapes
- Initial setup
- Updates
- Modules
- Network and MikroTik
- Automation
- NAC
- TACACS+
- Firewall
- Captive Portal
- Monitoring
- Backup
- Hypervisor
- OTP
- Passkeepr
- GRC
- Inventory and CMDB import
- Troubleshooting
- Security
- Versions
- Version history
- Support
Overview
| Item | Value |
|---|---|
| Purpose | A view of an existing Zabbix instance: dashboard, hosts, templates, problems, Unlinked Assets. Acknowledge problems, create and change hosts from the asset |
| Zabbix | you bring it. Zabbix is not part of COD’s delivery |
| Connection and direction | COD server to the Zabbix API through the configured API URL. Zabbix or a Zabbix proxy polls the devices, not COD |
| Credentials | API URL and API token per location, optionally a filter on host groups |
| Alerting | stays with Zabbix. COD does not alert |
| Firewall rules | Customers and partners receive the list of connections and firewall rules as part of the project. |
Requirements
In Zabbix
| Requirement | Why |
|---|---|
| API token with write access only to your own server groups | Host creation and acknowledging. COD needs no further rights |
| Host groups created in Zabbix | COD does not create host groups |
| Hostname in Zabbix equals the asset name in COD | The sync compares full names |
| API URL reachable from the COD server, HTTPS recommended | All queries come from the COD server |
Recommendation: One Zabbix proxy per location has proven itself in practice. It polls the devices on site.
In COD
- Monitoring module enabled for the tenant.
- “Monitoring Config” setting per location: API URL, API token, optionally host groups.
- Asset names follow the naming scheme. See Names and addresses.
Setup
- Create the host groups for the location in Zabbix.
- Create a user for COD in Zabbix and generate an API token. Give the user write access only to these host groups.
- Enable the module with the Manager account under “Admin Area > Tenant > Modules”. Then log out and log in again.
- Enter API URL and API token in the location’s “Monitoring Config”.
- Select the host groups the location should see.
- Check the “Unlinked Assets” list. It names assets without a Zabbix host.
- Create missing hosts from the asset: “Monitoring” tab on the asset, with hostname, templates, host groups and interface.
Technical details
| Item | Value |
|---|---|
| Interface | Zabbix API (JSON-RPC) through the configured API URL |
| Sync | nightly. COD links assets and Zabbix hosts by the full name |
| Filter | per location through Zabbix host groups, selected by multi-select |
| Host creation from the asset | interface Zabbix agent or SNMP v2c. Address by IP or DNS |
| SNMP v2c for host creation | community preset as the macro {$SNMP_COMMUNITY}, bulk on, max repetitions 10 |
| Monitored by | “Monitored by”: server, proxy or proxy group |
| Acknowledging | from COD. COD adds the acknowledging user to the comment on the server side |
| Turning monitoring off on the asset | COD only removes its own link. The host stays in Zabbix |
| Asset | The “References” tab shows the Zabbix host next to firewall, voucher and tasks |
What COD does not do
- COD does not detect problems and does not alert. Triggers, thresholds and alerting stay in Zabbix.
- COD never deletes Zabbix hosts. Deleting is reserved for the Zabbix interface.
- The reachability check for firewalls belongs to the Firewall module, not to Monitoring.
Known limits
| Limit | What you can do |
|---|---|
| COD does not alert on its own | Set up alerts in Zabbix |
| COD never deletes Zabbix hosts | Delete hosts in Zabbix |
| If you rename a host in Zabbix, the link dissolves at the nightly sync | Change names in COD and Zabbix at the same time |
| Matching needs exactly identical names | One name for each device in all systems |
| Host creation from the asset only with Zabbix agent or SNMP v2c | Create other interfaces in Zabbix |
| COD does not create host groups | Create the groups in Zabbix |
| The host group filter does not apply to templates and proxy lists | Name templates and proxies so that the assignment is clear |
| Zabbix is not part of the delivery | Run your own Zabbix instance |
Further reading
- Monitoring module page
- What your network needs for Monitoring
- Names and addresses
- Firewall: reachability check
- Troubleshooting
- Questions about the modules
- Support: your partner is your first point of contact. Technical questions to extocode go through the helpdesk form.