-
Documentation task
-
Resolution: Unresolved
-
Trivial
-
7.0.0
-
Sprint candidates
-
0.25
There is a difference in behaviour of zabbix_get between 6.4 and 7.0:
$ cat compose.yaml
services:
agent-7.0:
image: zabbix/zabbix-agent:ubuntu-7.0-latest
environment:
ZBX_PASSIVESERVERS: 127.0.0.1,::1
agent-6.4:
image: zabbix/zabbix-agent:ubuntu-6.4-latest
environment:
ZBX_PASSIVESERVERS: 127.0.0.1,::1
$ docker compose up -d
...
$ docker-compose exec agent-6.4 zabbix_get -s localhost -k agent.pong
ZBX_NOTSUPPORTED: Unsupported item key.
$ echo $?
0
$ docker-compose exec agent-7.0 zabbix_get -s localhost -k agent.pong
ZBX_NOTSUPPORTED: Unsupported item key.
$ echo $?
1
I suppose it is related to ZBXNEXT-8854.
If the change is intentional, it has to be documented in Upgrade Notes.
Meaning of exit codes should be documented in zabbix_get man page.
- caused by
-
ZBXNEXT-8854 New JSON protocol for passive agent checks
-
- Closed
-
