Converse agora com nosso suporte
Chat com o suporte

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

Understanding the default Nexus

Foglight creates a default Nexus as part of the installation process for Foglight for Java EE Technologies and Foglight for Microsoft .NET. The Nexus behaves as an agent: you can activate and deactivate it, start and stop its data collection, view its properties, assign a profile that contains recording settings to it, or delete it.

The default Nexus controls all agent data correlation and submission unless you create and assign another Nexus. You can copy settings from the default Nexus, or any existing Nexus, to use as the basis for a new Nexus. For more information, see Creating Nexuses.

The default Nexus contains basic recording settings for request sampling and collection details. These settings are contained in a profile. You can modify the Nexus profile through the Nexus Administration dashboard. For more information, see Managing Nexus Recording Settings.

Nexus requirements

The Nexus runs on Foglight Agent Manager version 5.6.7.2 or later.

 
* 
IMPORTANT: The Agent Manager heap requires at least 1 Gb of memory for the Nexus. Depending on the monitored application, this heap requirement may increase to as much as 4 Gb.

The Nexus requires Oracle (Sun) Java SE JDK 1.6, 1.7, or 1.8

The Nexus is supported on the following OS platforms:

 
Table 1. Supported OS platforms for the Nexus.
OS version
Architecture

Solaris 8, 9

SPARC

Solaris 10, 11

SPARC, x86-64

Windows XP SP1+, Server 2003, Server 2008

ia32, x86-64

Windows Server 2008 R2, Server 2012, Server 2012 R2, Server 2012 R2 Core

x86-64

Red Hat AS/ES/WS 4, 5, 6, 7

ia32, x86-64

SuSE 9, 10, 11, 12

ia32, x86-64

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

Using the Nexus Administration page

Use the Nexus Administration page to create, configure, and control Nexuses and their recording settings. The bottom portion of the page displays the recent Task history.

To access the Nexus Administration page:
1
On the navigation panel, under Dashboards, click Application Servers > Administration.
2
On the Application Servers Administration dashboard, click the Nexuses tab.

The Nexuses table lists all Nexuses, their versions and upgrade status, current health and data collection status, the Agent Manager hosting them, and the assigned recording settings.

Click the name of any Nexus agent in the table to open a menu.

From this menu, you can:

•
Start or stop data collection.
•
Activate or deactivate the Nexus agent.
•
Get log — open or save a copy of the Nexus activity log.
•
Edit the recording settings — through the UI or in a text editor. For more information, see Managing Nexus Recording Settings.
•
Switch the recording settings — assign a different profile to the selected Nexus.
•
Delete the Nexus.
•
Upgrade the Nexus.
•
View and edit the Nexus properties — including the listen port and address. For more information, see Editing Nexus properties.

Editing Nexus properties

If you have multiple network cards on the Nexus host and you want to allow connections to the Nexus only through one card, you can use a host name or IP address as the listen address to force the Nexus to listen only on that one IP address.

To edit the properties of a Nexus agent:
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 the name of the Nexus you want to edit.
4
In the menu that opens, click Properties.
The Nexus Properties dialog box opens.
5
Review the read-only information in the top section of the dialog box to ensure that you are editing the correct Nexus.
6
To change the port number on which the Nexus listens for connections, type a new value in the Listen Port box.
7
To change the address on which the Nexus listens for connections, select Listen on the following network interface, and type a host name or IP address in the box below.
8
Optional — adjust the Advanced Settings.
The Advanced Settings are hidden by default. It is recommended that you do not change these settings unless instructed to do so by Quest Support for troubleshooting purposes.
a
Click the arrow to the left of Advanced Settings to expand the advanced settings section.
b
Click the information icon to view an explanation of the setting for the selected option. Adjust the setting as necessary based on the information provided in the explanation.
 
Table 2. Descriptions of Advanced Settings.
Setting
Description
Debug Level

The Nexus uses this debug level when logging. Values between 0 and 3 are typical.

Agent Order Level

Specifies how often the Nexus places request sample orders with the agents. It is recommended that you do not change this value. The value is specified in milliseconds. The default is 2 seconds.

Commit Timeout

The amount of time the Nexus tracks a Service Request before committing it to the session data file. Whenever a Request Fragment for a Service Request is received, this timer is reset.

The value is specified in milliseconds. The default is 4 seconds.

Message Traffic Timeout

Some firewalls and NAT devices automatically close connections after a certain period of inactivity. This optional setting configures both endpoints of a Nexus connection to ensure that the idle timeout is not exceeded. A connection is closed if it is idle for longer than this timeout.

The value specified for this setting should be equivalent to the firewall's timeout for idle connections. This setting can be set to zero if the firewall does not close idle connections or if no firewall exists between the Nexus and agents.

This value is specified in milliseconds. By default, it is set to approximately two minutes (2 minutes 11 milliseconds).

Agent Status Interval

The Nexus periodically provides Foglight for Application Servers with a list of agents that are connected to it. Foglight for Application Servers uses this list to drive Application Server state rules. This value specifies how often the Nexus provides that list. For large systems, increasing this value may decrease Nexus and Management Server overhead at the risk of longer delays before being alerted that an Application Server has disconnected.

The value is specified in milliseconds. The default is 30 seconds.

Agent Status Activation Delay

This value specifies how long after activation the Nexus waits before sending the list of agents for the first time. This value should be slightly longer than the longest Connection Retry Interval specified in the Nexus Connection settings for any agent in the system; to give every alive agent time to reconnect.

The value is specified in milliseconds. The default of 22000 ms is 10% longer than the default Connection Retry Interval of 20000 ms.

NOTE: For more information about the Nexus Connection settings, see the installation guide for the application server agent you are using.
9
Click OK.
The dialog box closes, and the Nexus settings are updated.

Related topics:

•
Adjusting the Agent Manager settings for the Nexus
•
Editing Nexus properties
•
Request sampling
•
Collection details
•
Advanced settings
•
Managing advanced configuration settings for all Nexuses
Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação