Hello!
I would like to leave a suggestion for the Zabbix team.
Actually, Zabbix have two types of macros: {$MACRO} (user-defined macro) and {#MACRO} (LLD Macro).
My suggestion would be creating a third type (for example {%MACRO}) for what would be a "macro" (behave like a macro), but in fact would be a reference for the data obtained by some item. This way, if I obtain certain item data and want to embed it on a script or discovery rule, I can do it.
So, I would need to have a way to attach this macro to a certain collected item data, in the same way I put a text value on an user macro. This way, if I want to put that collected data inside a script, that would make this operation easy.
If I want to interact with a web API informing collected data in order to obtain a certain result, I can obtain this item data (for example, from an internal server) and put it into this suggested macro so I can build a script to send to some external API and monitor the result.
This would bring more power and flexibility to Zabbix platform, reducing the need to rely on external scripts, and would increase the third-party Zabbix integration possibilities.
I really ask myself how Zabbix still doesn't have this possibility yet.
I would like to leave a suggestion for the Zabbix team.
Actually, Zabbix have two types of macros: {$MACRO} (user-defined macro) and {#MACRO} (LLD Macro).
My suggestion would be creating a third type (for example {%MACRO}) for what would be a "macro" (behave like a macro), but in fact would be a reference for the data obtained by some item. This way, if I obtain certain item data and want to embed it on a script or discovery rule, I can do it.
So, I would need to have a way to attach this macro to a certain collected item data, in the same way I put a text value on an user macro. This way, if I want to put that collected data inside a script, that would make this operation easy.
If I want to interact with a web API informing collected data in order to obtain a certain result, I can obtain this item data (for example, from an internal server) and put it into this suggested macro so I can build a script to send to some external API and monitor the result.
This would bring more power and flexibility to Zabbix platform, reducing the need to rely on external scripts, and would increase the third-party Zabbix integration possibilities.
I really ask myself how Zabbix still doesn't have this possibility yet.
Comment