Zabbix Documentation 4.2

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
manual:concepts:sender [2014/09/25 15:14]
sasha Links adapted because of a move operation
manual:concepts:sender [2019/04/04 07:06] (current)
martins-v more precise wording
Line 1: Line 1:
-==== - #6 Sender ====+==== Sender ====
  
 === Overview === === Overview ===
Line 6: Line 6:
  
 The utility is usually used in long running user scripts for periodical sending of availability and performance data. The utility is usually used in long running user scripts for periodical sending of availability and performance data.
 +
 +For sending results directly to Zabbix server or proxy, a [[:​manual/​config/​items/​itemtypes/​trapper|trapper item]] type must be configured.
  
 === Running Zabbix sender === === Running Zabbix sender ===
Line 17: Line 19:
  
   * 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 [[manpages:​zabbix_sender|Zabbix sender manpage]] for more information.+<note important>​Options that contain whitespaces,​ 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. 
 + 
 +If a configuration file is specified, Zabbix sender uses all addresses defined in the agent ServerActive configuration parameter for sending data. If sending to one address fails, the sender tries sending to the other addresses. If sending of batch data fails to one address, the following batches are not sent to this address.  
 + 
 +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 31: Line 37:
 Since Zabbix 1.8.4, zabbix_sender realtime sending scenarios have been improved to gather multiple values passed to it in close succession and send them to the server in a single connection. A value that is not further apart from the previous value than 0.2 seconds can be put in the same stack, but maximum pooling time still is 1 second. Since Zabbix 1.8.4, zabbix_sender realtime sending scenarios have been improved to gather multiple values passed to it in close succession and send them to the server in a single connection. A value that is not further apart from the previous value than 0.2 seconds can be put in the same stack, but maximum pooling time still is 1 second.
  
-If sending many values from an input file, Zabbix sender will batch them at 250 values in one go (all values will be processed), for example: +<​note>​Zabbix sender will terminate if invalid (not following //​parameter=value//​ notation) parameter entry is present in the specified configuration file.</​note>​
- +
-  # zabbix_sender -z 127.0.0.1 -i /​tmp/​traptest.txt  +
-  Info from server: "​Processed 250 Failed 0 Total 250 Seconds spent 0.002668"​ +
-  Info from server: "​Processed 50 Failed 0 Total 50 Seconds spent 0.000540"​ +
-  sent: 300; skipped: 0; total: 300 +
- +
-All entries from an input file are sent in a sequential order top-down.  +
- +
-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>​+