Chat now with support
Chat with Support

Foglight Experience Monitor 5.8.1 - Installation and Administration Guide

Installing and configuring Multi-appliance clusters Configuring the appliance Specifying monitored web traffic Transforming monitored URLs Managing applications Foglight components and the appliance Using the console program Troubleshooting the appliance Appendix: Third party software Appendix: Dell PowerEdge system appliance

Storing report sets

Unlike most configuration settings, report sets are not aggregated at a central location, they are stored on the appliance on which they were created or modified by the appliance user. This means that a user who creates a report set locally on a particular probe does not see it if they log in to another probe or the portal.

Generally, this should not be a concern since users should always be directed to use the portal to access metrics collected by the cluster. In the event that a user unknowingly creates report sets on a probe, and is reluctant to manually rebuild them all on the portal, you can use report packages to migrate the user’s report sets.

To migrate report sets:
1
Log in to the probe where you want to move the report sets.
2
Navigate to the Monitoring > Customize Report Sets page.
3
Click Distribute All Report Sets, located at the bottom of the page.
4
From the list of users, select the check box beside the users to whom you want to distribute your reports.
5
Click Done.
6
From the Customize Report Sets, click Create Report Set Package.
The Create Report Set Package window appears, displaying a package file link.
7
Right-click the link, and save the file to your system.
8
Log in to the portal.
9
Go to Customize Report Sets page.
10
Click Reset Report Sets.
11
In the Reset Report Sets window, select the use a report package option, and locate the file you saved in step 7.
12
Click Submit.
For more information about report sets, see the “Distributing report sets” and “Resetting and copying a report set” in the Foglight Experience Monitor User Guide.

Switching from stand-alone to clusters

You may need to switch from a stand-alone machine to a probe as part of a cluster. There are two likely reasons why you might need to make this change:

•
You are using a single stand-alone appliance. Due to growth in your server farm and web traffic, you wish to upgrade to a multi-appliance cluster.
•
You are using a multi-appliance cluster, and also have a few stand-alone appliances deployed on your network. You would like to take an existing stand-alone appliance, and promote it into the multi-appliance cluster.

The following section (Creating a cluster from a stand-alone appliance) describes the steps you must take to ensure the best possible outcome for your existing metric data and configuration settings.

Creating a cluster from a stand-alone appliance

When converting a stand-alone appliance deployment into a multi-appliance deployment, you can promote the stand-alone to a portal. Metrics are retained during this process but the configuration is not retained. If you want to retain the configuration, follow these steps:

1
Back up your configuration settings (see Backing up and restoring data).
2
Change the appliance type from stand-alone to portal (see Configuring the Appliance Type).
3
Restore the stand-alone configuration settings on the newly created portal (see Restoring a backup).

Once your portal is completely established with the original configuration settings, and after you have installed the two new appliances as probes, the configuration settings propagate throughout the cluster.

Merging a stand-alone appliance with an existing cluster

If you are transitioning a stand-alone appliance into an existing cluster, you will lose all of its configuration settings. In most cases, this consequence is irrelevant since the stand-alone appliance’s transition into the cluster implies the destination cluster’s settings and data collection policies take precedence over what currently exists on the stand-alone appliance.

The stand-alone appliance’s metrics are preserved, and are available through the web console. However, they do not reflect the configuration settings of the cluster and will likely have some inconsistencies. For this reason, it is recommended that you purge metrics at this time. See Database configuration.

After you change the appliance type to probe, and link it with the existing portal, all cluster-wide configuration settings are accessed from the central database. See Configuring the Appliance Type.

Some appliance settings are not global, and therefore are not shared from the central portal’s MySQL® database. These settings (ports and servers) are unique to each probe, and need to be configured. For more information, see Specifying monitored web traffic.

Configuring the appliance

The following chapter covers configuration options that affect the appliance itself, as well as how it functions as a part of your network environment.

For more information, see these topics:

•
Network settings
•
User accounts
•
Security settings on the appliance
•
Report settings
•
Database configuration
•
Appliance integrity
•
Updating the appliance
•
Backing up and restoring data
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating