-
Notifications
You must be signed in to change notification settings - Fork 129
/
Copy pathTemplate Module Zabbix agent.xml
144 lines (144 loc) · 5.56 KB
/
Template Module Zabbix agent.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
<?xml version="1.0" encoding="UTF-8"?>
<zabbix_export>
<version>5.0</version>
<groups>
<group>
<name>Templates/Modules</name>
</group>
</groups>
<templates>
<template>
<template>Template Module Zabbix agent</template>
<name>Template Module Zabbix agent</name>
<description>Use this template for agents reachable from Zabbix server/proxy (passive mode).
Template tooling version used: 0.34</description>
<groups>
<group>
<name>Templates/Modules</name>
</group>
</groups>
<applications>
<application>
<name>Monitoring agent</name>
</application>
<application>
<name>Status</name>
</application>
</applications>
<items>
<item>
<name>Host name of Zabbix agent running</name>
<key>agent.hostname</key>
<delay>1h</delay>
<history>7d</history>
<trends>0</trends>
<value_type>CHAR</value_type>
<applications>
<application>
<name>Monitoring agent</name>
</application>
</applications>
<preprocessing>
<step>
<type>DISCARD_UNCHANGED_HEARTBEAT</type>
<params>1d</params>
</step>
</preprocessing>
</item>
<item>
<name>Zabbix agent ping</name>
<key>agent.ping</key>
<history>7d</history>
<description>The agent always returns 1 for this item. It could be used in combination with nodata() for availability check.</description>
<applications>
<application>
<name>Monitoring agent</name>
</application>
</applications>
<valuemap>
<name>Zabbix agent ping status</name>
</valuemap>
</item>
<item>
<name>Version of Zabbix agent running</name>
<key>agent.version</key>
<delay>1h</delay>
<history>7d</history>
<trends>0</trends>
<value_type>CHAR</value_type>
<applications>
<application>
<name>Monitoring agent</name>
</application>
</applications>
<preprocessing>
<step>
<type>DISCARD_UNCHANGED_HEARTBEAT</type>
<params>1d</params>
</step>
</preprocessing>
</item>
<item>
<name>Zabbix agent availability</name>
<type>INTERNAL</type>
<key>zabbix[host,agent,available]</key>
<history>7d</history>
<description>Monitoring agent availability status</description>
<applications>
<application>
<name>Status</name>
</application>
</applications>
<valuemap>
<name>zabbix.host.available</name>
</valuemap>
<triggers>
<trigger>
<expression>{max({$AGENT.TIMEOUT})}=0</expression>
<name>Zabbix agent is not available (for {$AGENT.TIMEOUT})</name>
<priority>AVERAGE</priority>
<description>For passive only agents, host availability is used with {$AGENT.TIMEOUT} as time threshold.</description>
<manual_close>YES</manual_close>
</trigger>
</triggers>
</item>
</items>
<macros>
<macro>
<macro>{$AGENT.TIMEOUT}</macro>
<value>3m</value>
<description>Timeout after which agent is considered unavailable. Works only for agents reachable from Zabbix server/proxy (passive mode).</description>
</macro>
</macros>
</template>
</templates>
<value_maps>
<value_map>
<name>zabbix.host.available</name>
<mappings>
<mapping>
<value>0</value>
<newvalue>not available</newvalue>
</mapping>
<mapping>
<value>1</value>
<newvalue>available</newvalue>
</mapping>
<mapping>
<value>2</value>
<newvalue>unknown</newvalue>
</mapping>
</mappings>
</value_map>
<value_map>
<name>Zabbix agent ping status</name>
<mappings>
<mapping>
<value>1</value>
<newvalue>Up</newvalue>
</mapping>
</mappings>
</value_map>
</value_maps>
</zabbix_export>