Chatee ahora con Soporte
Chat con el soporte

Foglight for Java EE Technologies 5.9.13 - 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.

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

The Nexus is supported on the following OS platforms:

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

Support for the following platforms will be discontinued in the next major release:

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.

1
On the navigation panel, under Dashboards, click Application Servers > Administration.

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:

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.

1
On the navigation panel, under Dashboards, click Application Servers > Administration.
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.
a
Click the arrow to the left of Advanced Settings to expand the advanced settings section.

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

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.

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.

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).

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.

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.

9

Related topics:

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación