forked from ganglia/ganglia-nagios-bridge
-
Notifications
You must be signed in to change notification settings - Fork 0
/
ganglia-nagios-bridge.conf
executable file
·87 lines (81 loc) · 2.68 KB
/
ganglia-nagios-bridge.conf
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
gmetad_host = '127.0.0.1'
gmetad_port = 8649
# This overrides the DMAX attribute from all metrics in all hosts
# If DMAX > 0 and TN > DMAX, then a metric state is considered
# UNKNOWN and Nagios will potentially send an alert
force_dmax = 0
# Every collection group in gmond.conf defines a time_threshold
# This value appears as TMAX in the XML.
# The gmond process should normally send every metric again before
# the value timer TN > TMAX.
# If ganglia-nagios-bridge is polling a gmond collector
# then a very small tmax_grace period (perhaps 5 seconds) is used.
# If ganglia-nagios-bridge is polling a gmetad server then
# tmax_grace should be set higher than the polling interval configured
# in gmetad.
tmax_grace = 30
# Ganglia XML typically contains FQDNs for all hosts, as it obtains
# the hostnames using reverse DNS lookups. Nagios, on the other hand,
# is often configured with just the hostname and no domain. Setting
# strip_domains = True will ensure that the domain part is stripped from
# the hostname before passing it to Nagios.
strip_domains = True
# This is the directory where Nagios expects to read checkresults
# submitted in batch
nagios_result_dir = '/var/lib/nagios3/spool/checkresults'
# This is where we select the metrics that we want to map from
# Ganglia to Nagios service names
# Any metric not matched in the configuration will be ignored and
# not passed to Nagios.
# Defintion for multiple clusters and their hosts to be monitored
# along with their metrics is added in a nested format
#
# Format overview :
# cluster definiton specifying the clustername and hostnames and
# associated metrics to be monitored
#
# can add mutliple cluster names
# [cluster_name]
# Add comma separated host name(s) and and the common metrics to be monitored
# [[hostname(s) separated by ,]]
# Metric name of the metric to be monitored for the hostnames
# [[[metric name]]]
# metric attributes: corresponding service name and threshold values
# service_name =
# warn_above/below =
# crit_above/below =
# Sample configuration
[cluster_name]
[[host_01, host_02]]
[[[proc_total]]]
service_name = Total Processes
warn_above = 180
crit_above = 200
[[[load_one]]]
service_name = Current Load
warn_above = 0.1
crit_above = 0.3
[[host_02]]
[[[cpu_idle]]]
service_name = CPU IDLE
warn_above = 85
crit_above = 90
[[[disk_free]]]
service_name = DISK FREE
warn_below = 5
crit_below = 2
[[[cpu_speed]]]
service_name = CPU SPEED
warn_below = 2112
crit_below = 2000
[Production1]
[[host3, host12]]
[[[disk_free]]]
service_name = DISK FREE
warn_below = 10
crit_below = 5
[[host1]]
[[[cpu_speed]]]
service_name = CPU SPEED
warn_below = 2000
crit_below = 1890