[ZBX-2510] no sample configuration file for zabbix_sender Created: 2010 Jun 04  Updated: 2017 May 30  Resolved: 2012 Jun 19

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Agent (G), Documentation (D)
Affects Version/s: None
Fix Version/s: 2.0.1

Type: Incident report Priority: Minor
Reporter: Aleksandrs Saveljevs Assignee: Martins Valkovskis
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

zabbix_sender supports reading SourceIP, Server, ServerPort, Hostname from configuration file, but there is no sample configuration file for zabbix_sender in misc/conf/, neither it is documented at http://www.zabbix.com/documentation/1.8/manual/processes/zabbix_sender which parameters are supported.

 Comments   
Comment by richlv [ 2010 Aug 19 ]

usually sender is simply used with agent daemon config file.
documenting which params are supported would be good, though - are all the ones listed above supported ?
question remains what should it do with params it does not understand - it would be much better to error out in such cases, but that would also require a functionality where sender would be able to verify all agentd config file keywords, even if it would be discarding most of them

Comment by richlv [ 2012 Jun 18 ]

let's use this issue to document which params the sender supports.
this is even more important since ServerActive was added, as it would be rather confusing for users

Comment by richlv [ 2012 Jun 19 ]

clarified supported params in r28346 in svn://svn.zabbix.com/branches/dev/ZBX-5166

Comment by richlv [ 2012 Jun 19 ]

manpage contents will be added to the 2.0 doc branch after recent changes have been reviewed; this issue can be closed after that

Comment by Alexander Vladishev [ 2012 Jun 19 ]

Great! Please review my fix in r28365.

<richlv> looks good, CLOSED

Comment by richlv [ 2012 Jul 23 ]

2.0 manpages have been added at http://www.zabbix.com/documentation/2.0/manpages

Generated at Sat Apr 27 06:13:30 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.