And don’t mess up – we are talking about a Host name, not about a Visible name. So remember, the Host names must match and they are case sensitive. Otherwise, you will have your items in the front end, Zabbix server, Zabbix agent up and running without any strange error messages but still, you will not see the latest data in the front end. It is case-sensitive: if you have an upper case S in the front end, then it must be also upper case in the configuration file. And then, IP or DNS name to which agent will send the data.Ģ) Host name (must match the Host name in the front end). This will be the IP or the DNS name to which the agent, first of all, will connect and request the configuration like “ What do I need to monitor?” It will be a log file, in this case. Remember, in the agent config file which is located in /etc/zabbix/zabbix_nf we basically need to use two parameters:ġ) Server Active which is the IP or DNS name of your Zabbix server or the proxy if this agent is monitored by the proxy. The version is the recent one - 4.2.1, and I have CLI. I already have my Zabbix Series host in the front end. Let’s quickly remind ourselves what we need to keep in mind for our agent active checks to actually work. It is not possible to use the log items and do log file monitoring with Zabbix agent passive item types. But what’s most important is that you must use Zabbix agent active mode. The topic for today will be log file monitoring on Windows or Linux machines.īefore we start, remember that native log file monitoring is achieved with Zabbix agent. Previously, we talked about quite a lot of stuff – the installation of Zabbix server and proxy, Docker, Timescale, Prometheus, XPath, inventory, templates, and item agent configurations.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |