[ZBXNEXT-6958] Support of loading of Agent2 plugins at startup Created: 2021 Sep 29 Updated: 2024 Apr 10 Resolved: 2022 Jan 25 |
|
Status: | Closed |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Agent2 plugin (N) |
Affects Version/s: | None |
Fix Version/s: | 6.0.0beta2, 6.0 (plan) |
Type: | Change Request | Priority: | Trivial |
Reporter: | Aleksandrs Larionovs (Inactive) | Assignee: | Eriks Sneiders |
Resolution: | Fixed | Votes: | 1 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Attachments: | wait4.diff | ||||||||
Issue Links: |
|
||||||||
Team: | Team INT | ||||||||
Sprint: | Sprint 80 (Sep 2021), Sprint 81 (Oct 2021), Sprint 82 (Nov 2021), Sprint 83 (Dec 2021), Sprint 84 (Jan 2022) | ||||||||
Story Points: | 4 |
Description |
Currently Agent2 plugins must be compiled in, there is no way of loading new plugins at startup. It should be supported to allow extra flexibility, easier development and additional security. |
Comments |
Comment by Eriks Sneiders [ 2021 Dec 28 ] |
Available in:
|
Comment by Andris Zeila [ 2022 Jan 06 ] |
Released
Documentation updated: |
Comment by Glebs Ivanovskis [ 2022 Feb 21 ] |
Plugin Guidelines say:
...but then also say:
...where highlighted link points to main Zabbix repository. What's new claims:
Management of externally loaded plugins is indeed easier, but I don't see how creation/development of external plugins is any easier. As I understand, developer still has to have Zabbix source code tree to build plugin, that "shared Zabbix agent 2 package" is not available on https://pkg.go.dev. Or is it? To be honest, I expected this feature to be implemented properly, with example plugins hosted as separate repositories in Zabbix organization on GitHub (perhaps, even as template repositories). |
Comment by Andris Zeila [ 2022 Mar 02 ] |
This is the first step providing the technical implementation of external plugins. The rest is still under investigation/development. |