OMD uses a normal linux filesystem layout for etc, lib, var… except everything is relative to the sites home folder.
/omd
├── apache
├── sites
│ ├── site_a
│ ├── site_b
│ └── site_...
└── versions
├── 2.80-labs-edition
├── 2.90-labs-edition
├── 3.00-labs-edition
└── default -> /etc/alternatives/omd
Global directories are created automatically and must to be changed. New sites
folders are created on omd create
command. New versions are installed by the
package manager of your system.
The apache folder contains the reverse proxy configuration for the system apache.
It is possible to install and use multiple OMD version side by side. It is
also possible to upgrade legacy OMD installation to OMD-Labs with the omd update
command.
Keep a few things in mind:
omd update
.omd config
. /omd/sites/example
├── bin -> version/bin
├── etc
│ ├── apache
│ ├── ...
│ ├── cron.d
│ ├── init.d
│ ├── init-hooks.d
│ ├── logrotate.d
│ ├── mail-templates
│ ├── rc.d
│ └── xinetd.d
├── include -> version/include
├── lib -> version/lib
├── local
│ ├── bin *put scripts here*
│ └── lib
│ └── monitoring-plugins *put your own plugins here*
├── share -> version/share
├── tmp
├── var
│ ├── log *logfiles can be found here*
│ └── www
└── version -> ../../versions/2.10-labs-edition
OMD makes it very easy to separate your own written or downloaded plugins from
the standard plugins kit. The standard plugins are located in ./lib/monitoring-plugins
which can be accessed by the $USER1$ macro in nagios. Your own plugins should stay
in ./local/lib/monitoring-plugins
with the macro $USER2$.