Possibly out of scope, but I think it's essential that Zabbix become more integrated with the network at a layer2/3 level, rather than just the applications /daemons operating at layer4/5. This is something I'm working towards already, as I work for an ISP on a tight budget.
- Monitoring of availability, latency, packet loss using multiple packets is essential
- Full processing of v2c/3 SNMP traps
- Integration with Cisco IP SLA/SAA/RTR would be great (as in, tests get defined in Zabbix, Zabbix connects to the router, configures tests via SNMP and starts polling for data from those tests)
Back on the other side of the extreme, proper application level checks are necessary, you CANNOT just rely on establishing a connection to say a POP3 server, it needs to be able to authenticate, and verify if the mailbox can be read. Checks and dependencies need to be setup such that a failure at point during the check can trigger the checking of a particular dependency.
An example of this is one of our iMail servers that backs onto an MSSQL database for authentication information, if the MSSQL database is unresponsive or Windows 2003 just decides to stop talking on the interface necessary in order to connect to said MSSQL database, it will prompt for username, and accept it, but it will stall and timeout after the password is entered. Linux with @mail is in the works as a replacement of course, but even then we will need the ability to verify authentication and mailbox retrieval.
- Monitoring of availability, latency, packet loss using multiple packets is essential
- Full processing of v2c/3 SNMP traps
- Integration with Cisco IP SLA/SAA/RTR would be great (as in, tests get defined in Zabbix, Zabbix connects to the router, configures tests via SNMP and starts polling for data from those tests)
Back on the other side of the extreme, proper application level checks are necessary, you CANNOT just rely on establishing a connection to say a POP3 server, it needs to be able to authenticate, and verify if the mailbox can be read. Checks and dependencies need to be setup such that a failure at point during the check can trigger the checking of a particular dependency.
An example of this is one of our iMail servers that backs onto an MSSQL database for authentication information, if the MSSQL database is unresponsive or Windows 2003 just decides to stop talking on the interface necessary in order to connect to said MSSQL database, it will prompt for username, and accept it, but it will stall and timeout after the password is entered. Linux with @mail is in the works as a replacement of course, but even then we will need the ability to verify authentication and mailbox retrieval.
Comment