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

Deleting High Availability configurations

To delete a High Availability configuration:
1
From the High Availability page, select the check box beside the configuration that you want to delete.
2
Click Delete to remove the configuration.

Aggregation of metrics and configuration

Multi-appliance configurations are, for the most part, transparent to the end user. When viewing and building report sets, end users are never exposed to the concept of portals or probes. Any exceptions are outlined in Storing report sets. Appliance administrators should have an understanding of how multiple appliances share metric data and configuration settings, and in what ways the multi-appliance concept is hidden from end users.

For more information, see these topics:

•
Aggregating metrics
•
Configuration settings
•
Storing report sets

Aggregating metrics

In a multi-appliance cluster, all metrics collected by probes are pushed to the portal at the end of each five-minute interval. The portal then aggregates the data in real-time and stores it in its database. This architecture guarantees that there is always a single set of consolidated data that represents all of the traffic that was collected by the probes in the cluster.

Figure 14. Aggregating metrics

Metrics are aggregated in a multi-appliance cluster using the following procedure:

1
Probes analyze network traffic and generate metrics.
2
Every five minutes, all probes push their metrics and alarms up to the portal.
3
On the portal, a process called the consolidator responds and verifies that each of the probes have communicated with the portal as expected. If one or more of the probes, have not reported in, the portal delays consolidating the data for an additional five minutes. This safeguard is built-in to ensure that temporary interruptions of communications do not affect the aggregated data saved on the portal.
4
When the metrics from all the probes have been collected, the metrics are merged by the consolidator and stored in the local database on the portal. A subset of this merged, or unified, data is also then exported to Foglight by the Cartridge for FxM.
 
* 
IMPORTANT: If the portal is off-line for any period of time, the data collected by probes during that time may be lost. Gaps can appear in reports generated in the portal's web console.

Configuration settings

End users who browse the web console of the portal see a unified set of data representing the traffic collected by all of the probes in the cluster. This notion of the central data portal for end users does not always apply to the configuration settings for the portal and probes in the cluster.

While most of the configuration settings are shared by all appliances in the cluster, there are some settings that are specific to each probe:

•
The servers that are monitored
(configured on the Configure > Monitoring >Servers page).
•
The ports used by protocols including HTTP and HTTPS protocols
(configured on the Configure > Monitoring > Protocols page).
•
All network settings
(configured on the Configure > Appliance > Network Settings page).
•
All user account settings
(configured on the Configure > Appliance > User Accounts page).
•
The backup configuration settings
(configured on the Configure > Appliance > Backup & Restore page).
•
All security settings
(configured on the Configure > Appliance > Security page).
•
The Foglight Experience Viewer settings
(configured on the Configure > Appliance > Network Settings page).

For all other configuration settings, administrators can connect to any appliance, including the portal, to make changes to those settings.

 
* 
NOTE: Auto-discovery functions that are present in a number of areas in the configuration are not available on the portal since these require a live feed of network traffic to work.

All configuration settings, whether shared or probe-specific, are stored in a MySQL® database on the portal that is accessed by the probes using the MySQL protocol.

Figure 15. Configuration settings sharing

No matter where configuration settings are made, they are shared across the cluster. As shown in the diagram above, probes poll the configuration database on the portal every five minutes to receive any changes that have been made. This means that there could be up to a 10 minutes delay before configuration changes are reflected in the collected metrics.

If the portal goes offline, the probes utilize a local cached copy of the configuration database that reflects the last known state of the centralized configuration database on the portal. The probes can even be rebooted when a portal is down, and continue to use their own respective local copies of the configuration.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating