DBMS Base

The nep-dbms-base provides common objects and basic behavior to monitor DBMS Server, DBMS Instances and Databases.

Remember: This package only provides basic objects, therefore it must used on conjunction with other DBMS-related NEPs to monitor a specific DBMS family.

Terminology

Term	Definition
DBMS Binary	Binary files for the specific DBMS engine
DBMS Server	The server running the DBMS Binaries; each server can host multiple DBMS engines
DBMS Instances	A DBMS Server can run multiple copies of DBMS binaries; some DBMS call each copy an Instance, making it an optional concept
DBMS Database	The actual database; it can be hosted by a DBMS Server or by a DBMS Instance

DBMS Monitoring architecture

Architecture of DBMS vary from vendor to vendor. NEP tries to model all the most used scenarios on the entire IT. This leads to the definition of 3 main concepts:

• DBMS Server, which is a running copy of DBMS Binaries, making a running DBMS engine

• DBMS Database, which is the actual container of the database

• DBMS Instance, an optional component, that can be used whenever a DBMS explicitly defines the concept of multiple copy of the same DBMS Engine running on the same Server

The three objects are linked in a sort of chain, where the middle one is an optional piece

# Model with DBMS Instances
DBMS Server
├─ DBMS Instance
|  ├─ Database
|  ├─ Database
|  ...
├─ DBMS Instance
|  ├─ Database
...

# Model without DBMS Instances
DBMS Server
├─ Database
├─ Database
|  ...

These object can naturally linked with a parent-child relationship: in case the hosting DBMS Server stops or goes down, monitoring the hosted DBMS Databases/Instances is not possible.

This structure can used to describe more or less almost all DBMS in the world, therefore can be used as a base to build NEP with specific capabilities to monitor a specific DBMS Server.

DBMS Virtual Objects

DBMS Instances and DBMS Databases are implemented as children of nx-ht-virtual. Because of the way Icinga2 implements monitoring, it is useful to represent each service that can be hosted multiple times on a single server as a separated Host Object, but DBMS Instances and Databases are not really a Host. Therefore the concept of Virtual Host is being used, helping in describing them as a Host Objects that have no real corresponding (real) entity in the Host hierarchy.

Minimum supported environment

This package can be installed on systems running the software described below. Systems with equivalent components are also suitable for installation.

Required software	Requirements
NetEye	Version 4.23+
NetEye modules	Core

Package requirements

Objects shipped with package nep-dbms-base require the following nep:

• nep-common

Setup instructions

To setup Package nep-dbms-base, just use the Setup Utility:

nep-setup install nep-dbms-base

After the installation is complete, add the support for the required DBMS Server by installing the related NEP.

Available Objects

This section contains a description of all the Objects from this package that can be used to build your own monitoring environment.

Icinga2 Objects

Icinga2 Objects are Objects provided directly using Icinga2 Configuration files. This package contains the following Icinga2 Objects:

Dependencies

The following Dependencies are used to change the behavior of Host Objects and Service Objects in case a specific Parent Object has a problem.

Object name	Description
nx-disable-notifications-on-parent-dbms-server-down	Disable Notifications on Host Objects when their Parent DBMS Server is Down while marking them as Unreachable
nx-disable-notifications-on-parent-dbms-instance-down	Disable Notifications on Host Objects when their Parent DBMS Instance is Down while marking them as Unreachable

These dependencies can be used by all Host Objects implementing Host Templates nx-ht-dbms-instance or nx-ht-dbms-database. To set their parent, select it using the Data Field [NX] Parent DBMS Server or [NX] Parent DBMS Instance, whichever is available. It is suggested to deactivate all other Dependencies for this kind of Objects. In case default Parent-Child dependencies provided by nep-common are used, please deactivate them. To deactivate them, set Data Field [NX] Parent Hosts value to Disabled.

Package’s objects list

Object Type	Object Name	Editable	Containing File
Director Host Template	nx-ht-dbms-database	Yes	baskets/import/nep-dbms-base-01-host.json
Director Host Template	nx-ht-dbms-instance	Yes	baskets/import/nep-dbms-base-01-host.json
Director Host Template	nx-ht-dbms-instance-database	Yes	baskets/import/nep-dbms-base-01-host.json
Director Host Template	nx-ht-dbms-server	Yes	baskets/import/nep-dbms-base-01-host.json
Director Host Template	nx-ht-dbms-server-database	Yes	baskets/import/nep-dbms-base-01-host.json
Icinga2 Dependency	nx-disable-notifications-on-parent-dbms-instance-down	Yes	custom_files/neteye_shared_root/icinga2/conf.d/nx-dependency-dbms-parent.conf
Icinga2 Dependency	nx-disable-notifications-on-parent-dbms-server-down	Yes	custom_files/neteye_shared_root/icinga2/conf.d/nx-dependency-dbms-parent.conf