![]() ![]() Port 10050 is the default port on the Agent-side to listen to those incoming requests. The Zabbix server DNS name or IP address will be used to inform the agent where to send data and as a security measure so that the agent will only respond to incoming traffic (passive requests for data, remote commands) from the Zabbix server(s) listed. You can change the default host name Zabbix Server DNS name or IP address The Host Name will be shown on the Zabbix server dashboard and is used when you set up a new host to monitor on your Zabbix server. ![]() You can change it to something meaningful, provided that it is unique. The Host Name gets set by default to the hostname of your Windows machine. The choices you make on the next screen can all be modified in the Zabbix agent config file as will be shown later in this guide. The Zabbix agent for Windows comes as a standard installer with the usual wizard that will walk you through some of the needed basic configuration details. There is no functional difference between the choices. In that sense, you can pick whichever one you prefer. The main reason for offering different encryption engine options is so that if a vulnerability were to be discovered in one encryption platform, we can fairly seamlessly switch to another. Note that you have multiple choices per platform depending on the encryption engine (GnuTLS, OpenSSL, no encryption). For FileMaker Cloud, you complete the installation through the CentOS software manager command line. Installing the Agentįor macOS and Windows, you can download the agent from the Zabbix download page. Allow traffic in both directionsīased on your security requirements, you can decide to forego some of the functionality around triggering remote actions and opt for a more locked-down deployment. To use all of Zabbix’s functionality, including the ability for Zabbix server to send remote commands to your FileMaker Server (for instance to restart the scripting engine), you’ll need to allow traffic in both directions. The Zabbix port 10051 needs to be open on the Zabbix server to accept the incoming data. In this scenario all communication originates from the FileMaker Server no ports need to be opened on the FileMaker Server. In Active mode, the agent collects all of the required data on its own (based on the interval set for each item it collects data for) and sends that data to the Zabbix server. 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).
0 Comments
Leave a Reply. |