Federation synchronization issues (multiple causes) (4319754)

The Federator Master is not showing data from multiple Child servers.

Federated server not in sync with Child.

Monitored targets that are no longer listed in Child servers are still present in the Master server.

Host metrics on Foglight federator server are not up-to-date or missing.

The federated server does not show accurate information on a few of the dashboards. The data does not seem to sync in a timely manner.

CAUSE 1

No child servers are configured in the Master server.

CAUSE 2

Federation Master is unable to connect to the Child servers.

CAUSE 3

High alarm count on Child servers; queries for alarms are causing slowness in syncing the alarms in the dashboards.

CAUSE 4

Data is not being collected on Child servers.

CAUSE 5

A blackout is configured on the Child server which includes the problematic host.

CAUSE 6

Topology object instance limit reached.

CAUSE 7

Stale topology objects in the Child servers.

CAUSE 8

Different server and/or cartridge versions.

CAUSE 9

The entry in the TopologyQueries list in the Federation configuration is commented out. The list contains topology queries that identify topology objects to be merged into the federated topology model.

CAUSE 10

Obsolete objects not cleaned up due to Child servers configured for High Availability.

RESOLUTION 1

Add child servers to the FederationURLs property in the [FMS_HOME]/federation.config configuration file. For additional information refer to Setting up a federated environment in the Foglight - Federation Field Guide.

RESOLUTION 2

Verify the Federation Master can connect to the configured Child servers on ports 1099 and 4444.

RESOLUTION 3

Review and perform cleanup of alarms on Child servers; for more information refer to How to Purge Alarms? How to schedule purging of Alarms? (4289502).

RESOLUTION 4

Review Child servers for collections or connections issues on affected agents.

RESOLUTION 5

Please wait until the blackout ends or remove the host from the blackout (if possible).

Once the blackout ends wait a bit until the federator is fully synchronized with child server again.

RESOLUTION 6

Increase the limit of topology object instances; for more information refer to How to increase Foglight topology instance limits? (4311089).

RESOLUTION 7

Database objects may have not been removed after agents were deleted; for information on deleting a database agent from Child servers refer to How to delete a database agent (4295623).

RESOLUTION 8

Upgrade servers and/or cartridges for versions to match in the Federation environment. For more information on upgrading a federated environment refer to the Foglight - Upgrade Guide.

RESOLUTION 9

Uncomment the topology query entries in the Federation configuration file [$FMS_HOME]/config/federation.config on the Federation Master.

The default value is:

TopologyQueries  = (
	"!TopologyObject",
);

RESOLUTION 10

Force object purge by completing the steps in Federator does not remove obsolete topology objects when children are in HA (4375274).