Objects are all the elements that are involved in the monitoring and notification logic. Types of objects include:
- Service Groups
- Host Groups
- Contact Groups
- Time Periods
- Notification Escalations
- Notification and Execution Dependencies
More information on what objects are and how they relate to each other can be found below.
When you follow the Quickstart installation guide, several sample object configuration files are placed in “/etc/shinken/”. Every object has now is own directory. You can use these sample files to see how object inheritance works and learn how to define your own object definitions.
Objects are defined in a flexible template format, which can make it much easier to manage your Shinken configuration in the long term. Basic information on how to define objects in your configuration files can be found here.
Once you get familiar with the basics of how to define objects, you should read up on object inheritance, as it will make your configuration more robust for the future. Seasoned users can exploit some advanced features of object definitions as described in the documentation on object tricks.
Some of the main object types are explained in greater detail below...
Hosts are one of the central objects in the monitoring logic. Important attributes of hosts are as follows:
- Hosts are usually physical devices on your network (servers, workstations, routers, switches, printers, etc).
- Hosts have an address of some kind (e.g. an IP or MAC address).
- Hosts have one or more more services associated with them.
- Hosts can have parent/child relationships with other hosts, often representing real-world network connections, which is used in the network reachability logic.
Services are one of the central objects in the monitoring logic. Services are associated with hosts and can be:
- Attributes of a host (CPU load, disk usage, uptime, etc.)
- Services provided by the host (“HTTP”, “POP3”, “FTP”, “SSH”, etc.)
- Other things associated with the host (“DNS” records, etc.)
Contacts are people involved in the notification process:
- Contacts have one or more notification methods (cellphone, pager, email, instant messaging, etc.)
- Contacts receive notifications for hosts and service they are responsible for
Contact Groups are groups of one or more contacts. Contact groups can make it easier to define all the people who get notified when certain host or service problems occur.
Timeperiods are are used to control:
- When hosts and services can be monitored
- When contacts can receive notifications
Information on how timeperiods work can be found here.