Abstract: An apparatus comprises at least one processing device configured to monitor, by a first service in a service chain, a first set of processing queues comprising two or more different processing queues associated with two or more different priority levels. The processing device is also configured to process, by the first service, a given portion of data stored in at least one of the two or more different processing queues in the first set of processing queues. The processing device is further configured to determine prioritization information associated with the given portion of the data and to select, based on the prioritization information, a given one of two or more different processing queues in a second set of processing queues associated with a second service in the service chain, and to store the given portion of the data in the given processing queue in the second set of processing queues.

Abstract: An apparatus comprises at least one processing device configured to monitor, by a first service in a service chain, a first set of processing queues comprising two or more different processing queues associated with two or more different priority levels. The processing device is also configured to process, by the first service, a given portion of data stored in at least one of the two or more different processing queues in the first set of processing queues. The processing device is further configured to determine prioritization information associated with the given portion of the data and to select, based on the prioritization information, a given one of two or more different processing queues in a second set of processing queues associated with a second service in the service chain, and to store the given portion of the data in the given processing queue in the second set of processing queues.

Abstract: A system and method mitigate configuration change risk for a managed service in a customer environment. Reconfiguration commands sent to a management interface are intercepted and provided to a mitigation service executing in the customer environment. The mitigation service computes a risk rating for each such command based on a wide variety of factors. If the risk is low, then the mitigation service passes the command transparently to the management interface for execution. However, if the risk is too high, then the mitigation service requests an authorization code before the command can be executed. The acceptable level of risk may be set jointly by the customer and the managed service provider according to a service level agreement. Authorization codes can confirm performance of many mitigation actions, including approval by the customer or a supervising manager, studying relevant documentation, and clean execution of the command in a testing environment.