Chat now with support
Chat with Support

Foglight for Microsoft DOT NET 5.9.7.5 - Installation and Configuration Guide

Installing and Configuring Foglight for Microsoft .NET Managing .NET Agent Configurations

Final Platform Support Notice

Support for the following platforms will be discontinued in the next major release:
•
Solaris 8 and 9
•
All 32-bit versions of Oracle Solaris SPARC
•
Windows XP SP1+
•
Red Hat AS/ES/WS 4.x
•
SuSE 9

Before You Begin the Installation Process

If you intend to use the default Nexus running in the embedded Foglight for Microsoft .NET Agent Manager, you must adjust the Agent Manager disk cache settings before installing and configuring Foglight for Microsoft .NET. The default Nexus is created as part of the installation process.

Adjusting the Agent Manager Settings for the Nexus

The Agent Manager accumulates messages that are destined to be sent either upstream or downstream in queues between connections. This prevents messages from getting lost in the event of a disconnection.
Increase the Agent Manager disk cache size to ensure that data submissions from the Java EE agent or the .NET agent are not discarded. See the documentation in the fglam.config.xml file for detailed descriptions of the options.
 
* 
NOTE: This procedure is recommended for all installations.
To adjust the Agent Manager settings for use with the Nexus:
1
Navigate to your Agent Manager config folder. For example: C:\Quest_Software\Foglight_Agent_Manager\state\default\config.
2
Open the vm.config file in an editor.
 
* 
IMPORTANT: In Agent Manager versions 5.6.10 and later, this file is called baseline.jvmargs.config.
3
Uncomment and set the following setting to:
vmparameter.0 = "-Xmx1024m";
4
Save and close the .config file.
5
In the same config directory, open the fglam.config.xml file in an editor.
6
Edit the config:queue-sizes and max-disk-space settings as follows:
<config:queue-sizes>
    <config:upstream max-queue-size="-1" max-disk-space="100000" max-batch-size="-1"/>
    <config:upstream-verified max-queue-size="-1" max-disk-space="100000" max-batch-size="-1"/>
    <config:downstream max-queue-size="-1" max-disk-space="1024" max-batch-size="500"/>
</config:queue-sizes>
This sets the max-disk-cache size to 100 MB for the upstream and upstream-verified queues (normal and verified submissions).
7
Save and close the fglam.config.xml file.
8
Restart the Agent Manager.
If the Nexus is running in a non-embedded Agent Manager, the Agent Manager service must be restarted. This is the more common case.
If the Nexus is running in the embedded Agent Manager (for example, if you are using the default Nexus), do one of the following:
•
Restart the Management Server.
or
•
Go to <server>/jmx-console (e.g. http://torrdv288:8080/jmx-console/) and click: service=EmbeddedFglAm.
Invoke the Stop() operation, and then invoke the start() operation.
If you still find warnings in the Agent Manager log about the disk cache being too small, increase the max-disk-space values for the upstream and upstream-verified queues.
After you have adjusted the settings and restarted the Agent Manager, continue with Installing Foglight for Microsoft .NET.

Installing Foglight for Microsoft .NET

Foglight for Microsoft .NET is distributed in a cartridge (.car) file, ApplicationServers‑DotNET‑<version>.car. Installing and enabling the cartridge file on the Management Server adds the capabilities for monitoring Microsoft .NET systems to your Foglight for Microsoft .NET environment.
The installation process is common to all Foglight cartridges. For details, see “Installing Foglight cartridges” in the Administration and Configuration Help.
Next, create a .NET monitoring agent. For more information, see Creating .NET Agent Instances.
 
* 
TIP: Unlike with previous versions, you do not need to manually deploy the agent package to the hosts. The agent creation process now manages this step.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating