立即与支持人员聊天
与支持团队交流

Foglight APM for Real User Experience 5.9.10 - Installation and Setup Guide

Installation overview Installing physical appliances Installing virtual appliances Setting up appliances Working with appliance-hosted Management Servers Setting up server-hosted Management Servers Maintaining appliances Backing up and restoring physical appliances Appendix: Troubleshooting

Installing Foglight APM cartridges

Foglight APM cartridge is called EndUser-x_x_x.car (where x_x_x refers to the current version number). The Foglight APM cartridge depends on functionality included in the Foglight for Application Operations cartridge. If a supported version of Foglight for Application Operations is not currently installed, you need to install it before you install the Foglight APM cartridge. See the Foglight APM Release Notes for the supported cartridge version numbers.
Install the cartridges in the same way you installed your other Foglight cartridges. There is no agent component to install; the Sniffer takes the place of an agent. If you need help, open the action panel and click the Help tab.
To install Foglight APM on a server-hosted Management Server:
1
Log in to Foglight on the server-hosted Management Server. For instructions, see Launching Foglight.
2
On the navigation panel, under Dashboards, click Administration > Cartridges > Cartridge Inventory.
3
Verify that a supported version of the Foglight for Application Operations cartridge is installed and enabled. If it is not installed, install the Foglight for Application Operations cartridge. Verify that the cartridge installed successfully and is enabled.
4
Install the EndUser-x_x_x.car. Verify that the cartridge installed successfully and is enabled.

Communicating with Sniffer and Archiver appliances

The installation and set up instructions for Sniffer and Archiver appliances remain the same. See the instructions in one of these sections:
•
Installing physical appliances
•
Installing virtual appliances
Set up the appliances as described in Setting up appliances. When you come to the procedures called Launching Foglight and Configuring software components, complete the steps from your server-hosted Management Server.
 
* 
TIP: If the performance of the APM dashboards is slow, check the NetBIOS over TCP/IP setting. When enabled, this setting may cause delays when Windows® negotiates SSL handshakes with the Linux® operating system embedded on the appliances.

Configuring Federated Children

Federation addresses the needs of customers who monitor large-scale environments that are naturally partitioned into logical units. With federation, you define one Management Server as a Federation Master and other Management Servers as Federated Children. The Master collects, synchronizes, and displays information from all its Children. For example, a Master can summarize alarms, track SLAs, and generate reports. For a fuller description of federation and its capabilities, see the Foglight Federation Field Guide.
The Federation Master must be a server-hosted Management Server. Both server-hosted and appliance-hosted Management Servers can be designated as Federated Children. The following procedure covers both scenarios.
To set up Management Servers with Foglight APM in a federated environment:
1
Appliance-hosted Management Servers only — On each appliance-hosted Management Server, enable the federation feature.
a
Log into the Console program. For instructions, see Logging in to the Console Program.
b
From the main menu, select Network Settings, and verify that the Hostname has a value other than localhost.
c
Select Back to return to the main menu.
d
Select Advanced Options, then Access Shell.
A console window opens, displaying a command prompt in the user’s home directory.
e
Open the /opt/quest/foglight/config.appliance/appliance.config file, remove the comment symbol (#) from in front of the following statement, and save the file:
server.federatedchild = "true";
f
Run /opt/quest/foglight/config.appliance/configure_appliance.sh.
g
To leave the shell, enter Exit.
h
Exit the Console Program.
2
On the Federation Master server, do the following:
a
Edit your system’s hosts file to include the IP and hostname of the Federated Child.
b
Edit the federation.config file to include the IP address of the Federated Child.
JndiURLs = (
"jnp://<IP_ADDRESS>:1099",
);
c
Install the EndUser-x_x_x.car cartridge and its dependencies. For instructions, see Installing Foglight APM cartridges.
3
Connect each appliance-hosted and server-hosted Management Server to the Master the same way that you connect other Federated Children. For instructions, see “Setting up a federated environment” in the Foglight Federation Field Guide.
4
Log in to Foglight on the Master, and verify that you can see Foglight APM metrics using the following dashboards:
•
APM > Web Sites and Endpoints dashboard
•
APM > Support > Appliance Health dashboard
5
Verify that you can see Foglight APM alarms on the Master.

Enabling High Availability mode

A High Availability (HA) cluster consists of multiple Management Servers, where one server is designated as the primary server and the others are standby servers. If the primary server stops responding, one of the standby servers in the HA cluster takes over as the new primary server. For more information about high availability, see the Foglight High Availability Field Guide.
 
* 
NOTE: All Management Servers in an HA cluster need to use an external database. Because the external database option is not available for appliance-hosted Management Servers running on physical or virtual appliances, you must use server-hosted Management Servers if you want Foglight APM to work in an HA cluster.
To run server-hosted Management Servers with Foglight APM in HA mode:
1
Enable HA mode on each of the Management Servers. This process requires multiple steps, such as defining ports and server options. For instructions, see the Foglight High Availability Field Guide.
2
Configure a shared network location for the EndUser data directory, and enable read and write access to this directory for all the Management Servers.
3
In the server.config file for each of the Management Servers, add the following command:
server.vm.option0="-Dfoglight.cartridge.enduser.data.directory=
<NETWORK_SHARE_LOCATION>;
where <NETWORK_SHARE_LOCATION> can be any of the following types of values:
 
Table 11. NETWORK_SHARE_LOCATION values
OS
NETWORK_SHARE_LOCATION
Notes
Windows®
\\\\SHARED_HOST\\EndUser
Substitute the name of your shared host and include all slashes as shown
Windows
Z:
Where Z is mapped to a directory on a network share location
Linux®
/mnt/sharedhost/enduser/
Where the mount point is a directory on a network share location
4
After the HA cluster is configured, verify it.
a
Log in to Foglight on the primary Management Server.
b
On the navigation panel, under Dashboards, click Administration.
c
In the High Availability view, verify all standby Management Servers are listed as peers.
5
Install the EndUser-x_x_x.car cartridge and its dependencies on the primary server and on each standby Management Server in the HA cluster. For instructions, see Installing Foglight APM cartridges.
6
Verify that failover works.
a
Shut down the primary Management Server. A standby Management Server becomes the new primary Management Server.
b
Log in to Foglight on the new primary Management Server.
c
On the navigation panel, under Dashboards:
•
Click APM > Traffic Capture > Sniffers. Verify that all the Sniffers are registered.
•
Click APM > Traffic Capture > Archivers. Verify that all the Archivers are registered.
•
Click APM > Traffic Capture > Capture Groups. Click Test. Assess any errors.
•
Click APM > Web Sites and Endpoints. Verify that you can see metrics.
•
Click APM > Support > Appliance Health. Verify that you can see health data.
•
Click APM > Search > Hits. Click Search. Verify that the search returns results.
 
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级