Since ZBX-11528 has been included in Zabbix 3.2.3, the zabbix_get_jmx script (found at https://www.zabbix.org/wiki/Docs/howto/zabbix_get_jmx) no longer works, which still worked in Zabbix 3.2.2.
Now I just get the following response with that script:
Where the '7B 22 72 65 71' HEX translates to '{"req' in ASCII.
I've tried my best to encode the key in binary, but I simply cannot get it to work with zabbix_get app any more, but I did succeed in getting it to work with the standard 'nc' app.
See my attached zabbix_get_jmx.txt file on how I've encoded the binary <HEADER><DATALEN> fields as documented in https://www.zabbix.com/documentation.../activepassive
Any ideas on how to make use of zabbix_get now, because I simply cannot manage to pass the \x01 and the datalen binary fields for the '-k' argument...
Now I just get the following response with that script:
Code:
{"response":"failed","error":"bad protocol header: 7B 22 72 65 71"}
I've tried my best to encode the key in binary, but I simply cannot get it to work with zabbix_get app any more, but I did succeed in getting it to work with the standard 'nc' app.
See my attached zabbix_get_jmx.txt file on how I've encoded the binary <HEADER><DATALEN> fields as documented in https://www.zabbix.com/documentation.../activepassive
Any ideas on how to make use of zabbix_get now, because I simply cannot manage to pass the \x01 and the datalen binary fields for the '-k' argument...
( Already few up of this thing
Comment