[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: File wait4.diff    
Issue Links:
Causes
causes ZBX-20453 Agent2 compilation broken on macOS Closed
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 ZBXNEXT-6958 in:

  • pre-6.0.0beta2 d69651bc4e

Documentation updated:

Comment by Glebs Ivanovskis [ 2022 Feb 21 ]

Dear esneiders and wiper,

Plugin Guidelines say:

External Zabbix agent 2 plugins are supported since Zabbix 6.0.0. Such plugins are kept in a separate repository, but use a shared with Zabbix agent 2 package.

...but then also say:

Several external plugins are available in Zabbix source code and can be used as examples.

...where highlighted link points to main Zabbix repository.

What's new claims:

Now, with the addition of the external plugin loader, plugins don't have to be integrated into the agent 2 directly and can be added as separate external add-ons, thus making the creation process of additional plugins for gathering new monitoring metrics easier.

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.

Generated at Tue Jan 07 22:20:15 EET 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.