-
Problem report
-
Resolution: Fixed
-
Trivial
-
5.2.0beta2
-
None
-
Sprint 69 (Oct 2020), Sprint 70 (Nov 2020)
-
0.25
It's difficult to debug configuration problems when trapper refuses to accept messages from zabbix_sender because zabbix server log doesn't give any hints about what went wrong:
9233:20201009:131234.187 trapper got '{"request":"sender data","data":[{"host":"Host1","key":"discover.cpu","value":"{
\n\t\"data\": [\n\t\t\t{\n\t\t\t\t\"{#CPU}\": \"7\"\n\t\t\t},\n\t\t\t{\n\t\t\t\t\"{#CPU}\": \"8\"\n\t\t\t}\n\t\t]\n}"}]}
' 9233:20201009:131234.187 In recv_senderhistory()
9233:20201009:131234.187 In process_client_history_data()
9233:20201009:131234.187 In parse_history_data()
9233:20201009:131234.187 End of parse_history_data():SUCCEED processed:1/1
9233:20201009:131234.187 In process_history_data()
9233:20201009:131234.187 End of process_history_data() processed:0
9233:20201009:131234.187 End of process_client_history_data():SUCCEED
9233:20201009:131234.187 In zbx_send_response_ext()
9233:20201009:131234.187 zbx_send_response_ext() '{"response":"success","info":"processed: 0; failed: 1; total: 1; sec
onds spent: 0.000426"}'
9233:20201009:131234.187 End of zbx_send_response_ext():SUCCEED
Trapper should be more verbose in debug or trace log levels and inform the user about the error(s).
