On a practical level, doing these exercises will get you accustomed to using the up.time Uptime Infrastructure Monitor interface to create different types of groups, and assign service monitors to Elements. At a conceptual level, you will learn how inheritance occurs in groups in up.timeUptime Infrastructure Monitor, and gain an understanding about how you can focus on structuring your monitored inventory, while up.time Uptime Infrastructure Monitor takes care of tracking Element-level relationships.
|Create a Service Monitor and Service Group||Learn about service monitors in upUptime Infrastructure Monitor. time. Create one as the foundation to a Service Group. Learn how Service Groups work by linking one to all of your Elements in one step.||1 slice|
|Create Element Groups||Begin organizing your monitored inventory by creating an Element Group and a pair of child Element Groups.||1 slice|
|Learn About Inheritance||Create a new Service Group (including a service monitor) and assign it to a top-level Element Group. Examine the services of an Element in a child group to learn about inheritance.||1 slice|
As a default way to report server uptime, for every server-type Element that is added to up.timeUptime Infrastructure Monitor's inventory, a Ping service monitor is also created and assigned to it, in a one-to-one relationship. In this exercise, we will replicate this functionality, but instead using a single service monitor. We will be able to create a one-to-many relationship between a service monitor and all of your Elements using a Service Group. A Service Group is a group of service monitors that can be assigned to Elements or groups of Elements.
While we are viewing this Element's Status page (if you have clicked the Info tab, return to the Status page by clicking the Services tab), let's learn a few more things about service monitors and Elements using the example screenshot above, which is of a server-type Element with an up.time Uptime Infrastructure Monitor agent installed on it:
- as with server-type Elements, upon addition to the up.time Uptime Infrastructure Monitor inventory, a Ping service monitor was created and assigned to the Element called PING-<hostname>
- server-type Elements that have the up.time Uptime Infrastructure Monitor agent installed will also have an UPTIME-<hostname> service monitor assigned to it
- if you click Host Check in the left pane, you can see which service up.time Uptime Infrastructure Monitor is using to monitor that particular Element's status (which applies to most Elements except for VMware vCenter Servers)
- if you click Manage Services, you will see other service monitors attached to the Element that aren't necessarily related to status
- Configuration Update Gatherer: collects any configuration changes for the monitored Element every 24 hours
- Platform Performance Gatherer: collects basic performance metrics from the monitored Element using the up.time Uptime Infrastructure Monitor Agent or WMI, and feeds them into up.timeUptime Infrastructure Monitor; its metrics can be used with a performance-related service monitor such as Performance Check
Create Element Groups
As you add Elements to up.timeUptime Infrastructure Monitor, by default, they end up at the top of the My Infrastructure hierarchy. Unless you are monitoring a small number of Elements, it's best practice to keep your monitored inventory well organized. Doing so helps both administrators and end users, which we will see in this exercise.
The important thing to note is it's more efficient to manage not at the Element level, but at the object level, whether that object is a Service Group, Element Group, or other up.time Uptime Infrastructure Monitor construct you will learn about; if you focus on Element Groups and Service Groups, everything else lines up and falls into place. Well managed arrangements of Element Groups and Service Groups can result in powerful cascading configurations.