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

Consider other 2xx response codes as success for the streaming export

XMLWordPrintable

    • Icon: Change Request Change Request
    • Resolution: Fixed
    • Icon: Trivial Trivial
    • 7.0.0rc1, 7.0 (plan)
    • 6.4.12, 7.0.0beta2
    • Server (S)
    • None
    • S24-W20/21
    • 0.125

      In 6.4 and 7.0, there is possibility to stream data to other systems:
      "Administration" => "General" => "Connectors"
      https://www.zabbix.com/documentation/6.4/en/manual/config/export/streaming

      Currently, it only considers a 200 response code as success and everything else is failure. A lot of systems send response codes like 201, 202, 204 as response codes for success.

      It’ll be good to either consider all 2x codes as success or allow users to define what is considered success while setting up the Connector.

      Use case:

      The integration has been made with New Relic logs product:
      https://docs.newrelic.com/docs/logs/log-api/introduction-log-api/

      The logs API sends back a 202 response code so although the data reaches the New Relic side correctly, it’s still considered a failure on the Zabbix end.

      I’ve seen a few other cases where 201 is used within the New Relic platform when the API is used to create new components etc.

            sasha Alexander Vladishev
            aigars.kadikis Aigars Kadikis
            Team C
            Votes:
            1 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - Not Specified
                Remaining:
                Remaining Estimate - Not Specified
                Logged:
                Time Spent - Not Specified
                Not Specified