Skip to Content
  •  +49 (861) 88 00 32 00
COD powered by extocode GmbH
  • 0
  • Sign in
  • English (US) Français Deutsch Español Türkçe
  • Open the demo
  • Home
  • COD Overview
    Platform
    OverviewPlatform: tenants and brandFeaturesProblems & SolutionsArchitectureDocumentationIntegrationsPricing
    Operations & Network
    MonitoringNetworkNetwork Access Control (NAC)TACACS+Captive PortalFirewall
    Security & Resilience
    Governance, Risk & ComplianceBackupHypervisorOTPPasskeeprAutomation
    Solutions & More
    NIS2 & CompliancecodPassAI documentation (InfraScan add-on)Open the demoReferencesDownloadsFAQ
  • Pricing
  • News
    • Blog
    • Roadmap
  • FAQ
  • About us
    • About us
    • Careers
    • Partners
    • References
  • Academy
  • Contact
COD powered by extocode GmbH
  • 0
    • Home
    • COD Overview
    • Pricing
    • News
      • Blog
      • Roadmap
    • FAQ
    • About us
      • About us
      • Careers
      • Partners
      • References
    • Academy
    • Contact
  •  +49 (861) 88 00 32 00
  • English (US) Français Deutsch Español Türkçe
  • Sign in
  • Open the demo
  1. Home
  2. Documentation
  3. Modules
  4. Monitoring

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

ItemValue
PurposeA view of an existing Zabbix instance: dashboard, hosts, templates, problems, Unlinked Assets. Acknowledge problems, create and change hosts from the asset
Zabbixyou bring it. Zabbix is not part of COD’s delivery
Connection and directionCOD server to the Zabbix API through the configured API URL. Zabbix or a Zabbix proxy polls the devices, not COD
CredentialsAPI URL and API token per location, optionally a filter on host groups
Alertingstays with Zabbix. COD does not alert
Firewall rulesCustomers and partners receive the list of connections and firewall rules as part of the project.

Requirements

In Zabbix

RequirementWhy
API token with write access only to your own server groupsHost creation and acknowledging. COD needs no further rights
Host groups created in ZabbixCOD does not create host groups
Hostname in Zabbix equals the asset name in CODThe sync compares full names
API URL reachable from the COD server, HTTPS recommendedAll 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

  1. Create the host groups for the location in Zabbix.
  2. Create a user for COD in Zabbix and generate an API token. Give the user write access only to these host groups.
  3. Enable the module with the Manager account under “Admin Area > Tenant > Modules”. Then log out and log in again.
  4. Enter API URL and API token in the location’s “Monitoring Config”.
  5. Select the host groups the location should see.
  6. Check the “Unlinked Assets” list. It names assets without a Zabbix host.
  7. Create missing hosts from the asset: “Monitoring” tab on the asset, with hostname, templates, host groups and interface.

Technical details

ItemValue
InterfaceZabbix API (JSON-RPC) through the configured API URL
Syncnightly. COD links assets and Zabbix hosts by the full name
Filterper location through Zabbix host groups, selected by multi-select
Host creation from the assetinterface Zabbix agent or SNMP v2c. Address by IP or DNS
SNMP v2c for host creationcommunity preset as the macro {$SNMP_COMMUNITY}, bulk on, max repetitions 10
Monitored by“Monitored by”: server, proxy or proxy group
Acknowledgingfrom COD. COD adds the acknowledging user to the comment on the server side
Turning monitoring off on the assetCOD only removes its own link. The host stays in Zabbix
AssetThe “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

LimitWhat you can do
COD does not alert on its ownSet up alerts in Zabbix
COD never deletes Zabbix hostsDelete hosts in Zabbix
If you rename a host in Zabbix, the link dissolves at the nightly syncChange names in COD and Zabbix at the same time
Matching needs exactly identical namesOne name for each device in all systems
Host creation from the asset only with Zabbix agent or SNMP v2cCreate other interfaces in Zabbix
COD does not create host groupsCreate the groups in Zabbix
The host group filter does not apply to templates and proxy listsName templates and proxies so that the assignment is clear
Zabbix is not part of the deliveryRun 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.
← Previous: Captive PortalNext: Backup →
Folgen Sie uns
​
  • COD Overview
  • Features
  • Demo
  • Pricing
  • Integrations
  • NIS2
  • codPass
  • References

Help

  • FAQ
  • Documentation
  • Downloads
  • Contact

Kotzinger Straße 21 • 83278 Traunstein • Deutschland

  • ​+49 (861) 88 00 32 00
  • ​info@extocode.com
Datenschutz Impressum ​
Copyright © extocode GmbH
English (US) Français Deutsch Español Türkçe

We use cookies to provide you a better user experience on this website. Privacy Policy

Decline Accept