[ZBXNEXT-8500] Move proxies to a separate database table Created: 2023 Jun 14  Updated: 2024 Jun 27  Resolved: 2023 Sep 12

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Proxy (P), Server (S)
Affects Version/s: None
Fix Version/s: 7.0.0alpha4, 7.0 (plan)

Type: New Feature Request Priority: Trivial
Reporter: Alex Kalimulin Assignee: Dmitrijs Goloscapovs
Resolution: Fixed Votes: 5
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: PNG File queue-proxy.png    
Issue Links:
Causes
causes ZBX-24209 Zabbix API method proxy.get doesn't r... Closed
Sub-task
part of ZBXNEXT-1096 Configurable Timeout per item (host i... Closed
Sub-Tasks:
Key
 Summary
 Type
 Status
 Assignee
ZBXNEXT-8506 Frontend changes to move proxies to a... Change Request (Sub-task) Closed Dmitrijs Fofanovs  
Epic Link: Zabbix 7.0
Team: Team A
Sprint: Sprint 101 (Jun 2023), Sprint 102 (Jul 2023), Sprint 103 (Aug 2023), Sprint 104 (Sep 2023)
Story Points: 5

 Description   

Currently, proxies are stored in table hosts. The reasons are purely histrorical. We need to separate proxies from hosts just because proxies are not the same as hosts and not even similar entities. The further features (such as configurable timeouts and proxy load balancing) will likely require more properties to be added to proxies so now is the best time for separation.

 Comments   
Comment by Dmitrijs Goloscapovs [ 2023 Aug 15 ]

Available in versions:

Comment by Dmitrijs Fofanovs [ 2023 Aug 31 ]

Documentation updated:

Generated at Fri Mar 21 04:34:37 EET 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.