[ZBXNEXT-9103] Consider other 2xx response codes as success for the streaming export Created: 2024 Mar 25 Updated: 2024 Jun 14 Resolved: 2024 Jun 12 |
|
Status: | Closed |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Server (S) |
Affects Version/s: | 6.4.12, 7.0.0beta2 |
Fix Version/s: | 7.0.0rc1, 7.0 (plan) |
Type: | Change Request | Priority: | Trivial |
Reporter: | Aigars Kadikis | Assignee: | Alexander Vladishev |
Resolution: | Fixed | Votes: | 1 |
Labels: | None | ||
Remaining Estimate: | |||
Time Spent: | Not Specified | ||
Original Estimate: |
Issue Links: |
|
||||||||
Team: | |||||||||
Sprint: | S24-W20/21 | ||||||||
Story Points: | 0.125 |
Description |
In 6.4 and 7.0, there is possibility to stream data to other systems: 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: 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. |
Comments |
Comment by Martins Valkovskis [ 2024 Jun 06 ] |
Updated documentation:
|