Over the last four modules, you have populated your monitored inventory with some sample Elements, got to know the main areas of the Uptime Infrastructure Monitor UI, and learned about how the intersecting properties of Elements and Element Groups, service monitors and Service Groups, Users, and Views allows you to configure Uptime Infrastructure Monitor for every type of user in your organization. While doing these modules, you've hopefully used up enough time to allow some data collection cycles to happen, meaning there can be data in reports.
This module consists of the following exercises:
|generate a hot spot report||drawing from now-collected metric data for your Elements, identify which are performance hotspots||1 slice|
|generate a server up time report||explore the default up time reports that help you assess your infrastructure immediately upon installation||1 slice|
|Revisit the Quick Snapshot pages|
|When you first added the virtual server Element in Track 1 of the first module, you examined the (empty) contents of the Hyper-V or vCenter Server's Quick Snapshot, and a random VM's Quick Snapshot. Let's revisit these pages to see what they look like with a little more data on them.|
The results of the report depends on the activity and performance of your Elements, but hopefully there is enough activity for resource hot spots to be listed, such as in the following example:
The opening Top Resource Consumers Summary lists Elements regardless of your configured thresholds; subsequent sections list any hot-spot Elements.
When Uptime Infrastructure Monitor is first installed, a few broad-coverage, quick-value reports are created out of the box for the admin user. One of these is the Server Uptime report, which is ideal for all the ESX hosts and VMs that are managed by your VMware vCenter Server Element.
Click the play icon to print the Server Uptime Report to screen.
The pre-configured options for this report include all of your Elements (by the report configuration, the Infrastructure Element Group, as well as its subgroups), and whether they met a target uptime threshold of 95%. This is reported for the last seven days. If you have completed all of this guide in the same sitting, unless you are very slow, you won't have a week's worth of data to display. Uptime Infrastructure Monitor reports with however much data it has collected, which in this case is likely a day's worth. The following example shows a full week of meeting up-time targets, with a modest number of outages:
Now that you've touched on a couple of reports, let's go back to what are essentially a real-time status report, the Quick Snapshot.
In the first module, specifically the first track, you added a VMware vCenter Server to your monitored inventory. In the final exercise, you viewed the Quick Snapshot for both the vCenter Server Element and one of its VMs. Because the vCenter Server was just added, there was no data in the graphs. Because the graphs show the last 24 hours of activity, you only need to wait overnight to fully populate them, but even a handful of data-collection cycles can suffice. Let's revisit these pages.
Expand the Discovered Virtual Machines Infrastructure Group, and click the gear icon for any of the VMs (preferably the same one you selected back in the first module). In the pop-up menu, again, click Graph Performance to display that Element's Quick Snapshot.
The key performance and resource metrics for the VM should now show some usage and baselines.