Regresar
-
Título
after HA failover of web monitor fglam, graphs for many (not all) Transactions lost historical data -
Descripción
graphs for many (not all) Transactions lost historical data when we had a fail over on our webmonitor fglam.
The High Availability (HA) failover didn't really transfer the webmonitor agent in a seamless way. We needed to restart the webmonitor agent. (And it appeared in the logs to be a newly created webmonitor agent. The agent was new to that particular fglam machine to which it had failed over). -
Causa
WebMonitor Agent does not support High Availability (HA). The web monitor agent may not work fine after getting transferred over to the other fglam. -
Resolución
The historical data will be present on the other webmonitor agent on the original fglam. Revert back to that one.
To keep the historical data synced up (prevent splitting off into a new topology object and starting a new data series), across the two different fglams, you need to have the 'URL' name identical and the 'Display Name' be identical between the webmonitor two agents. You can use a different 'Transaction Name' and still have the data sync up.Note: This will not mean WebMonitorAgent supports HA. It still won't automatically fail over seamlessly to the other webmonitor agent and fglam running on the other machine.)