1os_mon(7)                Erlang Application Definition               os_mon(7)
2
3
4

NAME

6       os_mon - OS Monitoring Application
7

DESCRIPTION

9       The operating system monitor, OS_Mon, provides the following services:
10
11         * cpu_sup CPU load and utilization supervision (Unix)
12
13         * disksup Disk supervision(Unix, Windows)
14
15         * memsup Memory supervision (Unix, Windows, VxWorks)
16
17         * os_sup Interface to OS system messages (Solaris, Windows)
18
19       To  simplify  usage  of OS_Mon on distributed Erlang systems, it is not
20       considered an error trying to use a service at a node where it  is  not
21       available (either because OS_Mon is not running, or because the service
22       is not available for that OS, or because the service is  not  started).
23       Instead, a warning message is issued via error_logger and a dummy value
24       is returned, which one is specified in the man pages for the respective
25       services.
26

CONFIGURATION

28       When  OS_Mon  is started, by default all services available for the OS,
29       except os_sup, are automatically started.  This  configuration  can  be
30       changed using the following application configuration parameters:
31
32         start_cpu_sup = bool():
33           Specifies if cpu_sup should be started. Defaults to true.
34
35         start_disksup = bool():
36           Specifies if disksup should be started. Defaults to true.
37
38         start_memsup = bool():
39           Specifies if memsup should be started. Defaults to true.
40
41         start_os_sup = bool():
42           Specifies if os_sup should be started. Defaults to false.
43
44       Configuration  parameters  effecting  the different OS_Mon services are
45       described in the respective man pages.
46
47       See config(4) for information about how to change the value of configu‐
48       ration parameters.
49

SNMP MIBS

51       The following MIBs are defined in OS_Mon:
52
53         OTP-OS-MON-MIB:
54           This  MIB  contains objects for instrumentation of disk, memory and
55           CPU usage of the nodes in the system.
56
57       The MIB is stored in the mibs directory. It is defined  in  SNMPv2  SMI
58       syntax. An SNMPv1 version of the MIB is delivered in the mibs/v1 direc‐
59       tory.
60
61       The compiled MIB is located under priv/mibs,  and  the  generated  .hrl
62       file  under  the  include  directory. To compile a MIB that IMPORTS the
63       OTP-OS-MON-MIB, give the option {il, ["os_mon/priv/mibs"]} to  the  MIB
64       compiler.
65
66       If  the  MIB  should  be  used in a system, it should be loaded into an
67       agent with a call to os_mon_mib:load(Agent), where Agent is the pid  or
68       registered  name  of  an  SNMP  agent.  Use os_mon_mib:unload(Agent) to
69       unload the MIB. The implementation of this MIB uses Mnesia to  store  a
70       cache  with  data  needed,  which implicates that Mnesia must be up and
71       running. The MIB also use functions defined for the OTP-MIB, thus  that
72       MIB must be loaded as well.
73

SEE ALSO

75       cpu_sup(3), disksup(3), memsup(3), os_sup(3), nteventlog(3), snmp(3).
76
77
78
79Ericsson AB                      os_mon 2.4.4                        os_mon(7)
Impressum