Feature request: Package template auxillary files as RPM/Deb etc
Hi there,
I'm in the process of setting up a PostgreSQL DB for Zabbix and I wish to monitor it with Zabbix as well.
First some deetz:
Zabbix version: 6.0
OS: RHEL 8
We're using Agent 1 and all default Zabbix templates that came with the 6.0 installation.
I noticed that in order to make the PostgreSQL template work, the agent needs some extra configuration files, which in the case of psql are located here: https://git.zabbix.com/projects/ZBX/...db/postgresql/
However, as of right now it's a bit of a pain to extract the required files from the git repo and deploy them to our DB server with Ansible (as we'd need to download the entire git repo just to extract 10 or so files from it).
Would it be possible to have all these extra files (I'd just put all of them in the same package) available via either the agent package or perhaps a additional package?
EDIT: Or would this be the moment for us to move to Agent 2? (We haven't deployed it anywhere yet, mainly due to it being a bit of weird situation as I'm not fully sure about what direction the agent in general would go, as I would think that agent2 was somesort of a fast-track or so which eventually will replace agent)
I'm in the process of setting up a PostgreSQL DB for Zabbix and I wish to monitor it with Zabbix as well.
First some deetz:
Zabbix version: 6.0
OS: RHEL 8
We're using Agent 1 and all default Zabbix templates that came with the 6.0 installation.
I noticed that in order to make the PostgreSQL template work, the agent needs some extra configuration files, which in the case of psql are located here: https://git.zabbix.com/projects/ZBX/...db/postgresql/
However, as of right now it's a bit of a pain to extract the required files from the git repo and deploy them to our DB server with Ansible (as we'd need to download the entire git repo just to extract 10 or so files from it).
Would it be possible to have all these extra files (I'd just put all of them in the same package) available via either the agent package or perhaps a additional package?
EDIT: Or would this be the moment for us to move to Agent 2? (We haven't deployed it anywhere yet, mainly due to it being a bit of weird situation as I'm not fully sure about what direction the agent in general would go, as I would think that agent2 was somesort of a fast-track or so which eventually will replace agent)