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

HTTP GET/POST Media type

    XMLWordPrintable

    Details

      Description

      The current list of media types is fantastic but the ability to POST alert content to third party HTTP/S APIs would be a fantastic addition.

      For complex scripts that broker between external ticketing systems, etc. this would enable "scripts" to run as daemons and listen for simple RESTful style requests from Zabbix and process them concurrently, without Zabbix causing a fork. Or simple POST requests could be entered directly in a NoSQL DB or message bus that support HTTP methods.

      I see this working with a new Media Type called "HTTP/S API" with the following options:

      URL: The HTTP end point
      Method: GET/POST/PUT/etc.
      Format: JSON/XML/text
      Expected response code: numeric (201, 202, nil, etc.)

      The body of the request should include the standard fields, title, description and contact (and macros?? please! ZBXNEXT-2712).

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            ryan.armstrong Ryan Armstrong
            Votes:
            7 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: