Ad Widget

Collapse

The Case for the Agentless Host config

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • djohnson
    Junior Member
    • Jun 2023
    • 3

    #1

    The Case for the Agentless Host config


    I've been adding many hosts to our zabbix config: primarily snmp agents and zabbix agents, and to a lesser extent a handful of hosts with basic checks either snmp or some basic tcp checks.

    Now I'm at the point where I'd like to go back all hosts and scan common tcp ports on all the hosts and have zabbix monitor any tcp port that is up and running.

    Zabbix seems to want me to put the hosts with simple tcp service checks on a "zabbix agent". And with that zabbix agent IP, I can set as "127.0.0.1" (the zabbix server itself) provided the monitored host's IP is specified in the tcp service checks.

    This may work on a case by case basis, but how would I go about adding tcp service checks on all the hosts?

    I think Zabbix wants me to create a template for hosts that have snmp as a way to monitor to have one method there, and then have another template for zabbix.

    I would think I could create a single template for simple service(s) to do checks on hosts that may have snmp or zabbix or no agent at all. (and why isn't there one already??)

    So, if zabbix had a "No Agent" config option when setting up hosts as a monitoring type, and that would then rely soley on the zabbix server.

    Low level discovery for this could come in the form of a tcp port scan of a prescribed list that I could specify, ie : 21,22,23,25,80,389,443,8080.

    If the ports from the prescribed list of the discovery are there, start monitoring.

    This would be so much better than trying to come up with the "network discovery" rules for all the subnets. In fact, I want network discovery to ping the ip, and then put it into a "no agent" tcp config and then have the "no agent" start pinigng and monitoring tcp ports automatically.

    A nice benefit too is that for the several hosts that are "no agent" wouldn't have a red zabbix icon for availability.

    This will allow me to have a single template "Monitor common TCP ports automatically" that I could apply to most of my hosts.

    It should layer nicely against the other agent types (snmp/ipmi/zabbix)

    Other than it would require a "core" change to zabbix to have "Agentless" IP, what am I missing?
Working...