manual:concepts:sender
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous 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 [2017/09/14 07:33] (current) martins-v trapper item is required to send in data with zabbix_sender |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ==== - #6 Sender ==== | + | ==== 5 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 [[:2.4/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. |
| + | |||
| + | 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 35: | ||
| 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> | + | |