Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-4955

trigger.get: does not return hostIDs or hostnames

XMLWordPrintable

    • Icon: Incident report Incident report
    • Resolution: Fixed
    • Icon: Minor Minor
    • None
    • 2.0.0rc3
    • API (A)
    • the Virtualbox (.vmdk) appliance on Zabbix 2.0 RC3

      API call: trigger.get
      Request:
      {"auth":"260df4afaa8fe4e10cb218af9f8f4288","method":"trigger.get","id":1,"params":{"monitored":1,"output":"extend","select_hosts":"extend","min_severity":2,"filter":

      {"value":1}

      ,"withLastEventUnacknowledged":1},"jsonrpc":"2.0"}

      This returns:
      {"jsonrpc":"2.0","result":[{"triggerid":"13022","expression":"

      {12191}

      >0","description":"Some items are not supported","url":"","status":"0","value":"1","priority":"2","lastchange":"1336408794","comments":"Unsupported items pollute Zabbix server logfile and reduce performance. They usually indicate a configuration problem.","error":"","templateid":"13021","type":"0","value_flags":"0","flags":"0"},{"triggerid":"13024","expression":"

      {12193}

      >0","description":"There are items missing data for more than 10 minutes","url":"","status":"0","value":"1","priority":"2","lastchange":"1336408820","comments":"zabbix[queue] item is collecting data about how many items are missing data for more than 10 minutes (next parameter)","error":"","templateid":"13023","type":"0","value_flags":"0","flags":"0"}],"id":1}

      However: seeing as the "select_hosts = extend" parameter is given, this should also include the hostname or hostID. At least, according to the 1.8 API docs (ref: http://www.zabbix.com/documentation/1.8/api/trigger/get).
      In 2.0 RC3 however, it only returns a templateID, but it's at first glance impossible to determine what host this linked to?

            Unassigned Unassigned
            mattiasgeniar Mattias Geniar
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: