...
- Click My Infrastructure to view the inventory you added in the first module:
- Click any Element's gear icon, then in the pop-up menu, click View to display its General Information page.
Since Because you have associated the Service Group to all Elements (by way of the My Infrastructure Element Group), the service monitor will be attacked is attached to any Element. - In the left pane, click the Services tab to display any services attached to, and monitoring, this Element.
You can see that by creating a Service Group (pingable), and linking it to an Element Group to which this Element belongs (My Infrastructure), this Element now uses this service monitor. Some things to note using the above screenshot:- the pingTest service monitor has a (member) suffix to indicate it is "attached" to this Element via a Service Group, meaning the properties of this service monitor can only be edited at the Service Group level (it is possible to "detach" a service monitor to make it editable at an Element level, but this is not a best practice)
- the pingTest service monitor status may be shown as UNKNOWN because it is recently added, and a full monitoring interval has not yet passed
- to view how long a monitoring interval is for a particular Element, click its Info tab, then look in the Data Collection section of the General Information page
...
In the first exercise, you created a basic Service Group and assigned it to all of your Elements via the My Infrastructure Element Group. Let's create another Service Group that demonstrates inheritance. To do this, we will make use of the Production parent Element Group we created in the previous exercise. But first, let's create a service monitor that will be a is part of the Service Group. Since Because it will be is assigned to Elements in the Production Element group, this service monitor should be something appropriate for all servers in a production environment.
...