Uploaded image for project: 'ZABBIX FEATURE REQUESTS'
  1. ZABBIX FEATURE REQUESTS
  2. ZBXNEXT-9617

Implement HTTP host discovery

XMLWordPrintable

    • Icon: New Feature Request New Feature Request
    • Resolution: Unresolved
    • Icon: Medium Medium
    • None
    • None
    • Proxy (P), Server (S)

      With the recent Zabbix versions the low-level discovery became very powerful and flexible. But the host discovery is still limited to a network scan. Therefore I'd suggest to add more useful options here.

      Especially an HTTP discovery which connects to an API to get a list of devices would be very helpful. This list could for example be a JSON like in the following example:

      [
        {
          "name": "hs1",
          "ip": "10.0.0.101",
          "model": "U7HD",
          "adopted": true,
          "site_id": "5dcc0f6hjdf3fd42f",
          "mac": "18:e8:29:47:aa:e1"
        },
        {
          "name": "hs2",
          "ip": "10.0.0.102",
          "model": "U7HD",
          "adopted": true,
          "site_id": "5dcc0f6hjdf3fd42f",
          "mac": "18:e8:29:47:aa:e2"
        },
        {
          "name": "hs3",
          "ip": "10.0.0.103",
          "model": "U7HD",
          "adopted": true,
          "site_id": "5dcc0f6hjdf3fd42f",
          "mac": "18:e8:29:47:aa:e3"
        }
      ]

      Each host's data contains a number of information which could then be used in the action conditions. The simple solution would be providing each host's top-level property. But using JSONPath would be a much better and more flexible alternative.

      For maximum compatibility it would be also important to enable preprocessing rules which could help to transform the data into the expected form.

            wiper Andris Zeila
            pu Pascal Uhlmann
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: