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

Next revision
Previous revision
Last revision Both sides next revision
manual:concepts:sender [2014/09/25 14:42]
sasha Page moved from 2.4:manual:concepts:sender to manual:concepts:sender
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 17: Line 17:
  
   * z - Zabbix server host (IP address can be used as well)   * z - Zabbix server host (IP address can be used as well)
-  * s - monitored host name (as registered in Zabbix frontend)+  * s - technical name of monitored host (as registered in Zabbix frontend)
   * k - item key   * k - item key
   * o - value to send   * o - value to send
  
-See [[:2.4/manpages/​zabbix_sender|Zabbix sender manpage]] for more information.+<note important>​If objects have whitespaces,​ these objects must be quoted using double quotes.</note>
  
-Zabbix sender accepts strings in UTF-8 encoding (for both UNIX-like systems and Windows).+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) ​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 42: 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>​