[ZBXNEXT-8854] New JSON protocol for passive agent checks Created: 2023 Nov 28 Updated: 2024 Nov 13 Resolved: 2024 Jan 11 |
|
Status: | Closed |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Agent (G), Proxy (P), Server (S) |
Affects Version/s: | None |
Fix Version/s: | 7.0.0alpha9, 7.0 (plan) |
Type: | New Feature Request | Priority: | Blocker |
Reporter: | Alex Kalimulin | Assignee: | Vladislavs Sokurenko |
Resolution: | Fixed | Votes: | 1 |
Labels: | None | ||
Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
Attachments: |
![]() |
||||||||||||||||
Issue Links: |
|
||||||||||||||||
Sub-Tasks: |
|
||||||||||||||||
Epic Link: | Zabbix 7.0 | ||||||||||||||||
Team: | |||||||||||||||||
Sprint: | S2401-1 | ||||||||||||||||
Story Points: | 7 |
Description |
The agent protocol for passive checks is simple and efficient, but at the same time it's very difficult to extend. Especially, when it comes to preserving compatibility with some very old agents. We should create a better, JSON-based protocol for passive checks (used by the new agents in 7.0) but keep support for the old protocol intact. One way to do it is to replace item key with the new JSON struct but fall back to the old proptocol if the agent returns error about invalid key format. |
Comments |
Comment by Vladislavs Sokurenko [ 2023 Dec 15 ] |
Implemented in:
|
Comment by Martins Valkovskis [ 2024 Jan 02 ] |
Updated documentation:
|
Comment by Markku Leiniö [ 2024 May 05 ] |
I see the request data is a list of items, and so is the response from the agent. But there are no item keys in the response list. Is it expected that data for multiple items is returned in the same order as requested, or is it expected that only one item is ever requested, even though it is a list? |
Comment by Vladislavs Sokurenko [ 2024 May 09 ] |
It's for future use markkul |
Comment by Glebs Ivanovskis [ 2024 Jun 06 ] |
I guess this change caused |
Comment by Marina Generalova [ 2024 Nov 13 ] |
Currently, documentation does not mention that as a result of this change, Zabbix get utility now returns the exit code 1 for unsupported item keys. The documentation will be updated in |