Chat now with support
Chat with Support

Foglight for Microsoft DOT NET 5.9.13 - Application Servers Administration and Configuration Guide

Adjusting the Agent Manager settings for the Nexus

The Foglight for Application Servers 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 Java EE or .Net agents:
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 named 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="500" max-disk-space="100000" max-batch-size="500" allow-runtime-change="false"/>
    <config:upstream-verified max-queue-size="250" max-disk-space="50000" max-batch-size="250" allow-runtime-change="false"/>
    <config:downstream max-queue-size="500" max-disk-space="1024" max-batch-size="500" allow-runtime-change="false"/>
</config:queue-sizes>
This sets the max-disk-cache size to 100MB 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-embeded 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 (for example, http://myserver: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.

Creating Nexuses

Foglight creates a default Nexus when you install either Foglight for Java EE Technologies or Foglight for Microsoft .NET. You can create additional Nexuses at any time after the installation is complete.

Ensure that you have read and followed the instructions in Adjusting the Agent Manager settings for the Nexus before creating additional Nexuses.

 
* 
IMPORTANT: Agent Managers and Nexuses have a one-to-one relationship. You cannot create more than one Nexus on an Agent Manager. Keep this in mind when planning agent and Nexus deployment.
To create a Nexus:
1
On the navigation panel, under Dashboards, click Application Servers > Administration.
2
On the Application Servers Administration dashboard, click the Nexuses tab.
3
On the Nexuses table, click Create Nexus.
The Create Nexus wizard opens.
4
On the Agent Host page, select the Agent Manager to host the Nexus.
 
* 
IMPORTANT: Each Agent Manager can host only one Nexus. Agent Managers that are already hosting Nexuses appear dimmed and cannot be selected.
Click Next.
5
Optional — On the Host and Port page, change the address and port where the Nexus listens for connections.
a
In the Listen Port box, type the port number that the Nexus should listen on. By default, the port number is 41705.
b
By default, the Nexus listens on all network interfaces.
If you want the Nexus to listen on a specific network interface, select Listen on the following network interface, and type the IP address or host name in the box below.
 
* 
TIP: Using a host name or IP address for the value (for example, "192.162.0.1"), makes the Nexus listen for connections on only that IP address. This is useful if you have multiple network cards on the Nexus machine and you want to only allow connections to the Nexus through one card.
c
Click Next.
6
On the Recording Settings page, select the recording settings to use.
 
* 
IMPORTANT: You can create additional recording settings at anytime from the Recording Settings tab of the Nexus Administration dashboard. For more information, see Managing Nexus Recording Settings .
Click Next.
7
On the Review page, review the summary of the configuration settings. If necessary, click Previous to go back and correct information.
8
Type a name for your new Nexus in the box. By default, this name is Nexus@<host>, where <host> is the Agent Manager host you selected.
9
To activate the Nexus after it is created, leave the Activate Nexus check box selected.
If you clear this check box, you must activate the Nexus manually.
10
Click Finish.
A progress box opens. When the Nexus creation is finished, a message is displayed.
11
Click Close to close the progress box.
The table on the Nexus Administration page refreshes and the new Nexus appears in the list.
Next steps:
•
Click the name of the Nexus to view the list of options for activating and managing the Nexus. For more information, see Using the Nexus Administration page .
•
For information about setting or editing recording settings, see Managing Nexus Recording Settings .

 

Managing Nexus Recording Settings

The Nexus recording settings are contained in the recording.config file. This file contains all the configuration information for the Nexus, such as the request sampling rules and the collection details.

In earlier versions of Foglight for Java EE Technologies, these settings were edited through the Agent Properties page. To simplify the Nexus configuration process, these settings have been surfaced through a new GUI editor that is accessible from the Nexus Administration page.

Editing the Nexus recording settings

You can edit the Nexus to create request sampling rules, modify collection details, and control other recording-related settings.

* 
NOTE: If you prefer to edit the settings manually, see Using the text editor.
To edit Nexus recording settings:
1
On the navigation panel, under Dashboards, click Application Servers > Administration.
2
On the Application Servers Administration dashboard, click the Nexuses tab.
3
On the Nexus view, do one of the following:
•
On the Agents tab, click the name of the Nexus that is using the configuration you want to edit. Click Edit recording settings to edit the settings through the configuration editor.
Or
•
On the Recording Settings tab, click the name of the configuration you want to edit. Click Edit to edit the settings.
The Edit - Nexus Recording dialog box opens.
 
* 
TIP: To understand how a setting is used, click the info icon .

For more information about the settings available on each of the tabs in this editor, see the following topics:

•
Request sampling
•
Collection details
•
Advanced settings
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating