[Enhancement] Introduce active checks executed on behalf of the parent host (host prototypes)

XMLWordPrintable

    • Type: Change Request
    • Resolution: Unresolved
    • Priority: Medium
    • None
    • Affects Version/s: None
    • None

      Good evening,

      thank you for giving this proposal a thought and considering the quality of life aspect of it.

       

      [Simple scenario]

      Active agent on a Linux server running couple of Oracle database instances. Logical separation between the OS related entries (items, triggers, ...) and Oracle ones is desired.

       

      [Approaches and difficulties]

      Using LLD along with host prototypes to represent Oracle instances seems to be a practical way to achieve that task.

      Unfortunately, hosts created from prototypes are unable to obtain results for their agent active items from the parent host's agent unless their technical host name has been added to the agent config and the agent restarted.

      I can think of two ways to tackle that with what is available in the current LTS (7.0):

      a) create a discovery script that also composes Oracle instance hostnames, writes them to agent config if a change is detected and restarts the agent after every such update

      b) create agent active items from item prototypes on the parent host that would use UserParameter to call zabbix_get and zabbix_sender to deliver the Oracle related output to the particular instance host, where a trapper item would be awaiting the data

       

      Neither of these two solutions appear smooth and ideal.

       

      [Proposed enhancement]

      Since hosts created from host prototypes seem to inherit the current encryption from the parent host by default, it should make sense to not have to include their technical host name in the agent's config for the active checks to work.

      I was thinking about the following approach:

      1. Active agent with single host name in it's config requests a list of active checks from the Zabbix server
      2. Server looks up agent active items from the host and also agent active items from it's child hosts, complete list is responded with
      3. Agent parses the response and introduces host name override for items related to child hosts, same item keys do not matter if receiving host name differs
      4. Active checks are executed and the output is sent to the Zabbix server and delivered to the appropriate host

            Assignee:
            Vladislavs Sokurenko
            Reporter:
            Vaclav Svarc
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: