Abstract: Embodiments of the present disclosure include techniques for automating the migration of software constructs between sources and targets. In one embodiment, software stacks are migrated between versions or system using an automated bot. The bot accesses a front end and backend of a system and loads software stacks that reside on the front and back ends. The bot may access a table comprising a batch of stories to be migrated. The bot is configured to invoke actions on the front end to automatically perform the migration process. Results of the migration are stored in the table, including whether or not the migration was successful and information about the results.

Abstract: The present disclosure provides techniques and solutions for analyzing failed computing tasks (or “jobs”) for resubmission. Computing jobs can include requests to generate recurring reports according to a schedule. Information regarding failed jobs can be submitted to a job resubmission framework. Various parameters can be extracted from the failed job information and used to determine whether a job should be submitted for reexecution. Jobs that are to be submitted for reexecution can be placed in a queue or released according to a schedule. Determining whether a job should be submitted for reexecution can include determining a relative priority of reexecuting a particular job compared with other jobs to be reexecuted. Disclosed techniques can help ensure that more important jobs are executed before lower priority jobs, as well as helping to avoid overloading a computing system with job reexecution processes.

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.