Abstract: In an example embodiment, a solution is provided to build a generic service failover framework that can be packaged as a library and implemented by many different microservices, whether on-premises or in the cloud. Each application can implement/add/hook this service to obtain the benefits of handling failover gracefully, as well as coming with some customizable options to provide a complete failover framework.

Abstract: In an example embodiment, a solution is provided to build a generic service failover framework that can be packaged as a library and implemented by many different microservices, whether on-premises or in the cloud. Each application can implement/add/hook this service to obtain the benefits of handling failover gracefully, as well as coming with some customizable options to provide a complete failover framework.

Abstract: Techniques and solutions are described for detecting event server failure and taking one or more actions in response to such detection. A plurality of events are registered with a first event server. If it is determined that the first event server is not operational, a notification can be provided, such as to a user through an administrator console. At least a portion of the events can be sent to a second event server for processing. In some cases, events that are sent to the second event server for processing can have summary records updated to remap or re-register the events with the second event server. In other cases, the events sent to the second event server do not have their summary records remapped or registered with the second event server.

Abstract: Techniques and solutions are described for detecting event server failure and taking one or more actions in response to such detection. A plurality of events are registered with a first event server. If it is determined that the first event server is not operational, a notification can be provided, such as to a user through an administrator console. At least a portion of the events can be sent to a second event server for processing. In some cases, events that are sent to the second event server for processing can have summary records updated to remap or re-register the events with the second event server. In other cases, the events sent to the second event server do not have their summary records remapped or registered with the second event server.