Zabbix Documentation 2.4

3.04.05.0 (current)| In development:5.2 (devel)| Unsupported:1.82.02.22.43.23.44.24.4Guidelines

User Tools

Site Tools


manual:concepts:sender

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
manual:concepts:sender [2015/11/25 13:54]
martins-v host name -> technical host name
manual:concepts:sender [2016/07/07 06:54]
martins-v byte order mark is not suported in sender input files
Line 1: Line 1:
-==== - #6 Sender ====+==== 6 Sender ====
  
 === Overview === === Overview ===
Line 23: Line 23:
 <note important>​If objects have whitespaces,​ these objects must be quoted using double quotes.</​note>​ <note important>​If objects have whitespaces,​ these objects must be quoted using double quotes.</​note>​
  
-See [[manpages:​zabbix_sender|Zabbix sender manpage]] for more information.+Zabbix sender can be used to send multiple values from an input file. See the [[manpages:​zabbix_sender|Zabbix sender manpage]] for more information.
  
-Zabbix sender accepts strings in UTF-8 encoding (for both UNIX-like systems and Windows).+Zabbix sender accepts strings in UTF-8 encoding (for both UNIX-like systems and Windows) ​without byte order mark (BOM) first in the file.
  
 Zabbix sender on Windows can be run similarly: Zabbix sender on Windows can be run similarly:
Line 44: Line 44:
 If the target item has triggers referencing it, all timestamps in an input file must be in an increasing order, otherwise event calculation will not be correct. ​ If the target item has triggers referencing it, all timestamps in an input file must be in an increasing order, otherwise event calculation will not be correct. ​
  
-<​note>​Zabbix sender will terminate if invalid (not following //​parameter=value//​ notation) parameter entry is present in specified configuration file.</​note>​+<​note>​Zabbix sender will terminate if invalid (not following //​parameter=value//​ notation) parameter entry is present in the specified configuration file.</​note>​