Foglight for Hyper-V 5.7.7 - User and Reference Guide

Setting the SOFS Agent Configuration properties

To monitor a desired SOFS server, ensure the SOFS Agent’s Configuration properties are set up as required.

Figure 6. SOFS Agent Configuration properties

To set the SOFS Agent Configuration properties:

Locate the SOFS Agent’s Configuration properties.

Set the Configuration properties as follows:

•

Host Name: Type the fully qualified host name of the machine on which the monitored Hyper-V Server is running.

•

Collect CPU metrics: Select this option if you want to collect CPU metrics from the monitored SOFS environment.

•

Collect disk metrics: Select this option if you want to collect disk metrics from the monitored SOFS environment.

•

Collect memory metrics: Select this option if you want to collect memory metrics from the monitored SOFS environment.

•

Collect network metrics: Select this option if you want to collect network metrics from the monitored SOFS environment.

•

Enable Storage Space Direct Collection. Select this option if you want to collect Storage Space Direct (S2D) metrics from the monitored Hyper-V environment.

•

Connection Type. Specify the connection type. Quest recommends using WinRM as the connection type, as DCOM will be removed in future release.

•

WinRM port. Type the port number of WinRM.

•

Use Https. Select this option if you want to use the HTTPS protocol.

•

Update request timeout (sec): Type the number of seconds after a collection times out.

Setting the Hyper-V/SCVMM/SOFSAgent Data Collection Scheduler properties

Use the Data Collection Scheduler properties to adjust how frequently the Hyper-V, SCVMM, or SOFS Agent collects data from the monitored server.

Figure 7. Data Collection Scheduler properties

To set the Data Collection Scheduler properties:

Locate the Hyper-V, SCVMM, or SoFS Agent Data Collection Scheduler properties.

Select the collection configuration list that you want to use.

Click Collection Config, and from the list that appears, select a collection list.


	TIP: The Inventory Collection process does not submit data back to the Management Server, it is used entirely to support the Essential and Resource metric collections. If you want to clone a list and associate it with the agent instance whose properties you are editing, select it and click Clone. When prompted, enter a name for the cloned list. For more information on cloning, see the Administration and Configuration Help.

The default Data Collection entry appears in the list. This collector is responsible for obtaining Hyper-V metrics from the monitored system.

Update the selected collection configuration list.

Click the Edit button on the right of Collector Config.

A dialog box appears.

Edit the entries in the list, as required.

To edit a value in the table, double-click the table cell, and enter the required value. Each list has the following values:

•

Collector Name: Contains the name of the default collector, Data Collection.

•

Default Collection Interval: Contains the length of the default collection interval.

•

Time Unit: Contains the time unit for measuring the default collection interval: milliseconds, seconds, minutes, hours, or days.

•

Fast-Mode Collection Interval: Contains the length of the collection interval when the agent is running in fast mode.

•

Fast-Mode Time Unit: Contains the length of the collection interval when the agent is running in fast mode.

•

Fast-Mode Max Count: Contains the maximum count of entries when the agent is running in fast mode.

Save your changes to the list by clicking Save Changes in the dialog box.

The dialog box closes.

In the display area, click Save.

Reviewing object instances and deleting expired data

Foglight™ collects data from monitored environments and creates a data model in real-time. The resulting topology model consists of nodes where each node is an object instance of a particular object type. Each type of monitoring environment can have a unique set of object types. Foglight for Hyper-V includes a set of topology object types and their definitions. When Foglight collects data from your Hyper-V environment, it builds the topology model that consists of the instances of the object types defined by Foglight for Hyper-V. By default, a monitored environment can result in up to 50,000 object instances being created by a single object type. This value is controlled by the foglight.limit.instances registry variable.

Registry variables have a global default value and type-specific scoped values. This means that different object types can have different instance limits.

Explore the Instances and Limits view to see the existing Hyper-V object types. To access this view, on the Hyper-V Environment dashboard, open the Administration tab, and click Review Instances and Limits.

Figure 8. Instances and Limits view

The Instances and Limits view displays the list of the existing Hyper-V object types, and for each type it shows the type name, instance limit, instance count, instance limit utilization, and the type status given as the highest severity level associated with an instance of that type. This information can give you insight into the size of your database and whether additional adjustments are required to improve your system performance. For example, if an object type results in a high number of object instances, this may result in performance bottlenecks. To prevent them, check if any of these are updated recently and, if not, delete them from the database, as described below.

To view the list of existing registry variables or to edit them, click Edit Registry Variable in the top-left corner. For complete information about registry variables in Foglight, see the Administration and Configuration Help.

For reference information about this view, see Instances and Limits view .

To review and delete expired data:

On the Hyper-V Environment dashboard, open the Administration tab.

On the Administration tab, click Review Expired Data.

The Expired Data View and Removal dialog box appears.

In the Expired Data View and Removal dialog box, select a category of object type that you want to review, and type the number of days during which the object instances were not updated.

For example, to view the object instances that are not updated in 30 days and are created when monitoring virtual machines, select HPVVirtual Machine, and in the Minimum days since last updated box, type 30.

Click Next.

The Expired Data View and Removal dialog box refreshes, showing the object instances that meet the specified requirements.

Observe the results.

•

If you want to delete all of the object instances, click Next.

•

If you want to modify your search, click Previous, make your changes, and observe your results again. For example, to show fewer instances, click Previous, and increase the time period. When satisfied, click Next.

•

If you do not want to delete any objects, click Next.

The Expired Data View and Removal dialog box refreshes.