Page History

...

Although agents will be are 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 allows you to see what is happening at the service/application level.

Prerequisites

• you have identified on which test Linux server you will be installing want to install the agent on
• an RPM utility has been is installed (and is in path) on the test Linux server
• xinetd is installed on the test Linux server
• you have downloaded the agent for this platform (uptimeagent-6.0.0-linux-x86_64.rpm), and transferred it to the server

1. Log into the system as user root.
2. Run the following command: 
   rpm -i uptimeagent-6.0.0-linux-x86_64.rpm
   The agent install process will perform performs various steps, such as restarting xinetd, and verifying dependencies such as netstat and vmstat exist.
3. Confirm via the command-line feedback that the installation has been completedis complete.

...

• Windows Domain: The Windows domain in which WMI has been is implemented.
• Username: The name of the account with access to WMI on the Windows domain.
• Password: The password for the account with access to WMI on the windows domain.

...

1. Click My Infrastructure, then click Auto Discovery in the left pane.
2. In the Auto Discovery pop-up, confirm that the selection is Discover Servers and Network Devices on your network, and click Next.
3. In the next step, select Servers with up.time Agent, and Servers with Windows Management Instrumentation (WMI). In both cases, select the Use [...] Global Configuration option that you have defined in the last two exercises:
   

4. Enter the subnet or IP address range, similar to above.

   Info
   title Pro Tip
   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.

5. Click Next to start the Auto-Discovery process.

   

6. When all servers on the subnet or IP address range have been are detected, you will be able to can make selections to add to your up.time inventory. Select the Linux server that's using the up.time agent, and select any WMI-managed Windows server.
   
7. Scroll to the bottom of the Auto Discovery list, and click Add. As a final step, you will receive confirmation that these are now part of your monitored inventory.
   

8. Click Done.

...

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. 

...

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.