[ZBXNEXT-4310] HTTP encapsulated ZBX for agent/server communication Created: 2018 Jan 03 Updated: 2021 Jun 09 |
|
| Status: | Open |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | Agent (G), Server (S) |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature Request | Priority: | Trivial |
| Reporter: | Spiros Ioannou | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 5 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Description |
|
In many cases the agent can only reach the server through a local LAN HTTP proxy for security reasons. This is the case where e.g. the agent monitors a remote facility which mandates outgoing traffic only through a VPN HTTP proxy, and the server resides in the cloud. For that reason we have used a set of simple scripts to encapsulate ZBX inside HTTP: https://bitbucket.org/sivann/zabbix_http_gateway/overview But it would be great if zabbix could have that functionality inherently. I've seen several tickets requesting AMQP, MQTT, etc, if encryption, and compession are of interest I would suggest HTTP/2 which is bidirectional, proxyable, widely deployed, and covers most of the other protocol benefits. |
| Comments |
| Comment by Hari Vittal [ 2021 May 14 ] |
|
Agreed and most other SaaS monitoring agents support this... when we look to get off them and into Zabbix this is issue in one of the blockers. I think this feature will aid more adoption of Zabbix. |