Page History

...

...

Although agents 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 Hyper-V host or vCenter Server can be monitored based on the metrics provided by that vCenter Serverserver; however, an agent allows you to see what is happening at the service/application level.

...

Now that you have installed an agent on a server, you could add it to Uptime Infrastructure Monitor 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 Auto Discovery can expedite the process if you tell Uptime Infrastructure Monitor how to find all servers with an agent installed.  

1. In the Uptime Infrastructure Monitor Web interface, begin by clicking Config, then click Global Element Credentials Settings in the left pane. 
   On this page are configuration fields that let you define properties of different metric collection methods, allowing you to auto automatically discover large groups that share the same properties.
2. In the Uptime Agent Global Configuration section, click Edit Configuration on the far right. The port used to communicate with is 9998. By default, SSL is not enabled.
   Image Modified
3. Click Save.

...

As with global agent settings, the WMI Agentless Global Credentials section of the Global Element Credentials Settings page lets you input WMI information once at a central point:

Image Modified

Configure the settings similar to those shown above:

...

Add Agent and WMI Servers Using Auto Discovery

1. Click My Click 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 Uptime 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 Uptime Infrastructure Monitor 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 are detected, you can make selections to add to your Uptime Infrastructure Monitor inventory. Select the Linux server that's using the Uptime Infrastructure Monitor 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 receive confirmation that these are now part of your monitored inventory.
   

8. Click Done.

...

After adding servers and closing the Auto Discovery window in the previous exercise, the main Uptime Infrastructure Monitor UI window is at the My the Infrastructure view. Refresh the page (or click My click Infrastructure) to ensure the latest additions appear immediately:Image Removed.

If you followed the Hyper-V or vCenter Server track, your inventory already included the vCenter Server virtual server Element and Infrastructure Groups created over those exercises. In addition, you 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. 

...

 Save

Save

Save