Chat now with support
Chat with Support

Foglight for Hyper-V 6.3.0 - User Guide (Lite version)

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.

1
Locate the Hyper-V, SCVMM, or SoFS Agent Data Collection Scheduler properties.
Click Collection Config, and from the list that appears, select a collection list.

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.
a
Click the Edit button on the right of Collector Config.
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.
d
Save your changes to the list by clicking Save Changes in the dialog box.

Managing certificates

In order to successfully make use of the Foglight commands in your monitoring environment, review the syntax conventions before getting started. The syntax conventions are as follows:

<foglight_home> is a placeholder that represents the path to the Foglight Management Server installation.
<foglight_agent_mgr_home> is a placeholder that represents the path to the Foglight Agent Manager installation. This can be the location of the Foglight Agent Manager installation on a monitored host, or the home directory of the Foglight Agent Manager that comes embedded with the Foglight Management Server. For example:

Foglight Evolve agents use Foglight Agent Manager (FglAM) to manage certificates for SSL encryption connection.

All the certificate-related command line options require that FglAM be up and running.

bin/fglam --add-certificate "user alias 1"=/path/to/certificate/file

The alias is required and is used in the list and delete operations to refer to the certificate. It can be anything.

bin/fglam --list-certificates

Print out a list of certificates and the aliases that refer to them.

Refer to the example output below:

Remove a certificate referred to by an alias.

bin/fglam --delete-certificate "user alias 1"

Use the keytool utility shipped with Foglight to create, import, or export certificates. This utility can be found at: <foglight_home>\jre\bin\keytool.

There are two FMS running modes:

The KeyStore Foglight used under non-FIPS mode is located at: <foglight_home>/jre/lib/security/cacerts (default password: changeit)

Use the keytool command in FMS JRE located in <foglight>/jre/bin

keytool -import -trustcacerts -alias "<alias>" -file "<certificate path>" -keystore <foglight_home>/jre/lib/security/cacerts -storepass changeit

<alias>: The alias is required and is used in the list and delete operations to refer to the certificate. It can be anything.
<foglight_home>: The folder path where the Foglight is installed.
<certificate path>: Your custom certificate path.

keytool -list -keystore <foglight_home>/jre/lib/security/cacerts -storepass changeit

Remove a certificate referred to by an alias.

keytool -delete -alias <alias> -keystore <foglight_home>/jre/lib/security/cacerts -storepass changeit

The KeyStore Foglight used in FIPS-compliant mode is located at: <foglight_home>/config/security/trust.fips.keystore (default password: nitrogen)

Use the keytool command in FMS JRE located in <foglight>/jre/bin.

keytool -import -trustcacerts -alias "<alias>" -file "<certificate path>" -keystore "<Foglight_home>/config/security/trust.fips.keystore" -deststoretype BCFKS -provider org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider -providerpath "<Foglight_home>/server/core/bc-fips.jar" -storepass nitrogen

<alias>: The alias is required and is used in the list and delete operations to refer to the certificate. It can be anything.
<Foglight_home>: The folder path where Foglight is installed.
<certificate path>: Your custom certificate path.

keytool -list -keystore "<Foglight_home>/config/security/trust.fips.keystore" -deststoretype BCFKS -provider org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider -providerpath "<Foglight_home>/server/core/bc-fips.jar" -storepass nitrogen

Prints out a list of certificates and the aliases that refer to them.

Refer to the example output below:

Remove a certificate referred to by an alias.

keytool -delete -alias <alias> -keystore "<Foglight_home>/config/security/trust.fips.keystore" -deststoretype BCFKS -provider org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider -providerpath "<Foglight_home>/server/core/bc-fips.jar" -storepass nitrogen

C:\Quest\Foglight\jre\bin>keytool -import -trustcacerts -alias "Evolve-Test" -file "D:/Evolve-test.crt" -keystore "C:/Quest/Foglight/config/security/trust.fips.keystore" -deststoretype BCFKS -provider org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider -providerpath "C:/Quest/Foglight/server/core/bc-fips.jar" -storepass nitrogen

Owner: CN=CA, DC=ca, DC=local

Issuer: CN=CA, DC=ca, DC=local

Serial number: xxxx

Valid from: Sun Jan 06 23:07:06 CST 2019 until: Wed Apr 06 23:07:06 CST 2022

Certificate fingerprints:

...

 

Extensions:

...

Trust this certificate? [no]: yes

Certificate was added to keystore

Reviewing object instances and deleting expired data

Foglight Evolve Cloud™ 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. Hyper-V Monitoring in Foglight Evolve Cloud includes a set of topology object types and their definitions. When Foglight Evolve Cloud collects data from your Hyper-V environment, it builds the topology model that consists of the instances of the object types defined by Hyper-V Monitoring in Foglight Evolve Cloud. 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 Agent Administration dashboard, click Review Instances and Limits.

Figure 10. 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 Evolve Cloud, see the Administration and Configuration Help.

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

The Expired Data View and Removal dialog box appears.
2
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.
3
Click Next.
The Expired Data View and Removal dialog box refreshes, showing the object instances that meet the specified requirements.
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.
The Expired Data View and Removal dialog box refreshes.
6
Click Finish.

Instances and Limits view

This view displays the list of the existing Hyper-V object types. This information can give you insight into the size of your database and whether additional adjustments are required to improve your system performance.

Instance Count. The current number of object instances of this type.
Instance Limit. The maximum number of object instances of this type that can be instantiated.
Object Type. The type of the topology object.
Status. The current status representing the highest severity level associated with an instance of that type.
Utilized. The percentage of the object limit instance that is currently utilized.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating