Not planning to do this module? You can skip to the next one. However, even if you plan to monitor only your vCenter Server, there are some important concepts covered in this module that are as applicable to your instances as they are to physical servers. Even if you do not perform the steps in this module, consider following along to learn more about agent- and WMI-based data collection.
This module consists of the following exercises:
Install an Agent on a Server
|Install an agent script on a server for enhanced metric collection.||1 slice|
|Configure Global Agent Collection||Configure up.time to use a standard set of properties to add agent-based servers with Auto Discovery.||½ slice|
|Configure Global WMI Collection||Configure up.time with details about your WMI implementation, to add Windows-based servers with Auto Discovery.||½ slice|
|Add Agent and WMI Servers Using Auto Discovery||Use Auto Discovery to detect different server platforms.||1 slice|
|Review Your Current Inventory||Review your discovered inventory so far. Learn how to view performance and system information for an Element.||1 slice|
Although there are up.time agents for various platforms including Linux, UNIX, and Windows, in this module, you will be installing an agent on a Linux server.
Although agents will be installed, they require minimal configuration and management, and have a small resource footprint. They are a low-cost way to get more detailed metrics from, and greater control over, a monitored system. For example, a VM that is part of a vCenter Server can be monitored based on the metrics provided by that vCenter Server; however, an agent will allow you to see what is happening at the service/application level.
uptimeagent-6.0.0-linux-x86_64.rpm), and transferred it to the server
rpm -i uptimeagent-6.0.0-linux-x86_64.rpm
xinetd, and verifying dependencies such as
Although this procedure was very hands-on, naturally for an actual, large-scale deployment, you can consider a deployment solution such as Puppet, or BigFix for Windows agent installations.
Now that you have installed an agent on a server, you could add it to up.time by using its host name. However, in a more realistic deployment, you would likely be installing agents on many servers. In this scenario, using auto discovery can expedite the process if you tell up.time how to find all servers with an agent installed.
Validation Step: Test the global setting by entering the hostname of the Linux server you installed the agent on during the previous exercise.
This Linux server is now ready to be added to up.time as an agent-based Element. Before doing this, let's take a look at how enhanced metrics can similarly be collected for Windows-based servers.
As an alternative to the Windows up.time agent, Windows Management Instrumentation can provide deeper metrics for up.time that is similar with agent-based data collection. The advantage is that it makes use of your existing infrastructure, negating the need for agent deployment. All you need to do is provide the WMI administrator information to the up.time Monitoring Station, so that it is able to access Windows-based servers.
As with global agent settings, the WMI Agentless Global Credentials section of the Global Element Settings page lets you input WMI information once at a central point:
Configure the settings similar to those shown above:
Validation Step: Test the global setting by entering a Windows host that the Monitoring Station can see in the Test Configuration section.
You are now ready to find an agent-based Linux server, and WMI Windows server.
Enter the subnet or IP address range, similar to above.
Although we are keeping things simple, and using a single subnet or IP address range as shown above, there are other ways to point up.time at subnets and subnet ranges to expedite the Auto-Discovery process. See Using Auto Discovery for more information.
Click Next to start the Auto-Discovery process.
After adding servers and closing the Auto Discovery window in the previous exercise, the main up.time UI window is at the My Infrastructure view. Refresh the page (or click My Infrastructure) to ensure the latest additions appear immediately:
If you followed the vCenter Server track, your inventory already included the vCenter Server Element and Infrastructure Groups created over those exercises. In addition, you will now see the Linux server and WMI-managed Windows server you added in the previous exercise. Your inventory is now a mixed virtual-physical, multi-platform mix (although a small one). Also note the platform-specific icons beside each Element type.
Validation Step: Click a newly added server's gear icon. Then in the pop-up menu, click Graph Performance to go to its Quick Snapshot.
In the VMware vCenter Server track, you viewed Quick Snapshots for the vCenter Server element, and a VM-type Element. Compared to the latter, the Quick Snapshot for an agent- or WMI-based server includes more detail, such as process information, which can be acted upon by up.time (for example, up.time's action scripts can restart a service as a follow-up remedy to an outage).
Because performance metrics are being gathered in real time by the up.time agent or via WMI, there is nothing yet to display in the Quick Snapshot graphs. After moving through more of this Getting Started Guide, we will return to this Quick Snapshot to view some data.
Verify how many license spots are free by clicking Config, then clicking License Info in the left pane. The number of used licenses is displayed in the License Information section.
In this Getting Started Guide, the next track has you adding network devices. If you plan on following this track, you need to anticipate the number of network devices you plan to add. At minimum, you'll need at least 1.
If you have run out of license spots, it's likely you have added a vCenter Server. The easiest way to free up space is to manually ignore VMs; each VM you ignore opens a license spot for a new Element. Return to the Inventory Detail view for the vCenter (My Infrastructure > gear icon > View > Inventory Detail). Select VMs, ESX hosts, or even an entire cluster, then click Add Selected Elements to Ignore. That number of spots will be freed up in your license, which you can verify by clicking Config > License Info.