-
Incident report
-
Resolution: Won't fix
-
Blocker
-
None
-
2.4.3
When an active log item becomes unsupported, agent v. 2.2.2 used to send the following:
[{
"request":"agent data",
"data":[
{
"host":"Zabbix server",
"key":"log[\/tmp\/log]",
"value":null,
"lastlogsize":8,
"clock":1423565589,
"ns":834122853}],
"clock":1423565590,
"ns":836189375}]
and value null meant that item became unsupported. .
2.4 agent sends a new field "state":1, meaning that the item is unsupported:
[{
"request":"agent data",
"data":[
{
"host":"Zabbix server",
"key":"log[/tmp/log]",
"value":"Cannot obtain information for file \"/tmp/log\": [2] No such file or directory",
"state":1,
"lastlogsize":8,
"clock":1423566013,
"ns":559885559}],
"clock":1423566014,
"ns":562135683}]
But when 2.4 server receives packet of 2.2.2 agent, it perceives "value":null as a normal value, since there is no state field.
- duplicates
-
-
- Closed
-