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
|
The protocol for agents (remote or local monitor scripts)
to deliver failures to the mon server:
Trap consists of tag/value pairs which are separated by newlines. The
first tag must be "pro", which is the protocol version.
Tags which are understood are:
#
# MON-specific tags
# pro protocol
# aut auth
# typ type (0=mon, 1=snmpv1)
# spc specific type (TRAP_*)
# seq sequence
# grp group
# svc service
# hst host
# sta status (opstatus)
# tsp timestamp as time(2) value
# sum summary output
# dtl detail (terminated by \n.\n)
#
# SNMP-specific tags
# ent enterprise OID
# agt agent address
# gtp generic trap type
# stp enterprise-specific trap type
# tmp sysUptime timestamp
# vbl varbindlist (OID = value)
#
If an alert for a watch or service is delivered to a mon server and
its configuration does not include that watch or service, it will use
the default watch/service "default" to deliver the alert. If "default"
is not defined in the mon.cf, the alert will be logged and then discarded.
watch default
service default
period wd {Sun-Sat}
alert default.alert
monitors are called with these env vars set:
MON_WATCH
MON_SERVICE
There will be a special alert script called "remote.alert" which
delivers a failure detected locally to a remote mon process. This
allows centralization of alert handling, and it allows distributed
mon processes.
|
