forked from fernandobrunelli/Zabbix-Templates
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Template Module Zabbix agent active.xml
115 lines (115 loc) · 4.53 KB
/
Template Module Zabbix agent active.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
<?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 active</template>
<name>Template Module Zabbix agent active</name>
<description>Use this template instead of 'Template Module Zabbix agent' for agents running in active mode only.
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>
<type>ZABBIX_ACTIVE</type>
<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>
<type>ZABBIX_ACTIVE</type>
<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>Status</name>
</application>
</applications>
<valuemap>
<name>Zabbix agent ping status</name>
</valuemap>
<triggers>
<trigger>
<expression>{nodata({$AGENT.NODATA_TIMEOUT})}=1</expression>
<name>Zabbix agent is not available (or nodata for {$AGENT.NODATA_TIMEOUT})</name>
<priority>AVERAGE</priority>
<description>For active agents, nodata() with agent.ping is used with {$AGENT.NODATA_TIMEOUT} as time threshold.</description>
<manual_close>YES</manual_close>
</trigger>
</triggers>
</item>
<item>
<name>Version of Zabbix agent running</name>
<type>ZABBIX_ACTIVE</type>
<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>
</items>
<macros>
<macro>
<macro>{$AGENT.NODATA_TIMEOUT}</macro>
<value>30m</value>
<description>No data timeout for active agents. Consider to keep it relatively high.</description>
</macro>
</macros>
</template>
</templates>
<value_maps>
<value_map>
<name>Zabbix agent ping status</name>
<mappings>
<mapping>
<value>1</value>
<newvalue>Up</newvalue>
</mapping>
</mappings>
</value_map>
</value_maps>
</zabbix_export>