The communication originates from the Zabbix server and requires port 10050 ( These ports can be customized as we will show later.) to open on the FileMaker Server to allow that incoming traffic. In Passive mode, the agent does not do anything at all until it is asked to do something by the Zabbix server. Zabbix Agent – memory Active or Passive Agent and Firewall PortsĪgents can operate in two modes – active or passive – and the difference can matter to you in terms of whether you are comfortable with opening an extra port on the FileMaker Server. Over the course of three months, the processor time for the Zabbix agent did not exceed 1% and used about 20MB of memory. As an example, the screenshots below are from one of our Zabbix servers that monitors four development FileMaker Servers. These agents exist for all three of the platforms that matter for us: Windows, macOS, and CentOS (FileMaker Cloud).
It is designed to be lightweight so that its monitoring activity does not affect the host that it is monitoring. The agent is a small piece of software that runs completely in the background as a service/daemon. While Zabbix server can monitor servers and devices without the presence of an agent on the host, the amount of data you can collect, and its relevance, would be much less. Zabbix agents collect data from the monitored host (FileMaker Server). Part 7: Maintaining Your Zabbix Server and Agents.Part 4: Installing Zabbix Agent (this post).Part 2: Installing Zabbix as an Appliance.This post is one in a series of guides that walk you through installing, configuring, and using Zabbix to monitor your FileMaker servers:
0 kommentar(er)
