[ZBXNEXT-246] Log or report failed items using zabbix_sender Created: 2010 Feb 22 Updated: 2022 Jun 09 Resolved: 2014 Dec 10 |
|
Status: | Closed |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Agent (G) |
Affects Version/s: | 1.8.2 |
Fix Version/s: | None |
Type: | New Feature Request | Priority: | Major |
Reporter: | Johan Fischer | Assignee: | Unassigned |
Resolution: | Duplicate | Votes: | 14 |
Labels: | consistency, patch, sender | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Attachments: | ZBXNEXT-246-log-failed-items.patch ZBXNEXT-246-log-failed-items.patch | ||||||||
Issue Links: |
|
Description |
It's not really an Agent Issue, but there is no zabbix_sender component.... Basically, we have a daemon transforming JAVA JMX metric into Zabbix values and send it Zabbix with the Sender protocol. The problem is that the Server will process the values and report an overall success ratio (40 success, 60 failed), without logging on the server side (checked trunk and branch 1.8) or reporting to the sender (tcpdump shows no detail returned) the exact list of items that failed. That feature would be extremely helpful in finding out what Items was missed in the configuration of the template in Zabbix and the completion of the Monitoring. Eventually, we'd like to obtain a 100% success ratio on the Zabbix Sender. I'm unsure if it would be better to log the failed item on the server side (could be noisy, and it's technically the client's fault for sending something incorrect), or sending that list to the Sender as Text after the summary report so the Sender can parse it and log it locally. |
Comments |
Comment by Johan Fischer [ 2010 Apr 21 ] |
FYI, I'm using the following patch in my installation now. |
Comment by richlv [ 2010 Oct 16 ] |
other issues related to sender output : |
Comment by João Figueiredo [ 2010 Nov 03 ] |
Hi agree with this being much more useful than the standard "Processed 48 Failed 22 Total 70..." It should at least return the offending item line. |
Comment by Henning Block [ 2012 Apr 24 ] |
Hi Johan. |
Comment by Johan Fischer [ 2012 Apr 25 ] |
This is the patch currently used on 1.8.12. I believe only the line changed. |
Comment by Marc [ 2013 Jul 28 ] |
I'd leave the default behavior like it is for performance/efficiency reasons, but optionally allow to request a more detailed confirmation on demand. This option might be given globally per bulk transaction or individually per send item. |
Comment by richlv [ 2014 Dec 10 ] |
in general seems to be the same as ZBXNEXT-38 - closing as a duplicate. if you had voted on this issue, you might want to vote on ZBXNEXT-38, too |
Comment by Andrey Shibanov [ 2020 Mar 03 ] |
any updates for 6 years? |
Comment by Andrey Shibanov [ 2022 Jun 09 ] |
It's actual |