Abstract: Techniques are described relating to coordinating asynchronous communication among a plurality of client microservices in a managed services domain of a cloud computing environment. An associated computer-implemented method includes receiving at a single request topic queue of a message broker application programming interface (API) at least one message associated with a topic from at least one publisher microservice among the plurality of client microservices. The method further includes identifying an authorization identification parameter included in each of the at least one message. The method further includes publishing each of the at least one message to a respective bucket within a single response topic queue of the message broker API, the respective bucket corresponding to one of at least one subscriber microservice among the plurality of client microservices associated with the authorization identification parameter included in the message.

Abstract: Techniques are described relating to coordinating asynchronous communication among a plurality of client microservices in a managed services domain of a cloud computing environment. An associated computer-implemented method includes receiving at a single request topic queue of a message broker application programming interface (API) at least one message associated with a topic from at least one publisher microservice among the plurality of client microservices. The method further includes identifying an authorization identification parameter included in each of the at least one message. The method further includes publishing each of the at least one message to a respective bucket within a single response topic queue of the message broker API, the respective bucket corresponding to one of at least one subscriber microservice among the plurality of client microservices associated with the authorization identification parameter included in the message.

Abstract: A first score associated with matching between entity records of a plurality of entities of master data of an MDM system is received. A set of entity records with a first score above a lower threshold score and below an upper threshold score is identified as unresolved; neither confirmed as matched or unmatched. A second score associated with relationships between entity records is generated. Overall scores for pairs of the set of entity records are determined by combining the first matching score with the second relationship score. The overall score of respective pairs of the set of entities is compared to the upper threshold, and if the upper threshold is exceeded, then the information of the pair of entity records of the set of entity records are combined into a single record, and redundant entity records are removed from the MDM system.

Abstract: A first score associated with matching between entity records of a plurality of entities of master data of an MDM system is received. A set of entity records with a first score above a lower threshold score and below an upper threshold score is identified as unresolved; neither confirmed as matched or unmatched. A second score associated with relationships between entity records is generated. Overall scores for pairs of the set of entity records are determined by combining the first matching score with the second relationship score. The overall score of respective pairs of the set of entities is compared to the upper threshold, and if the upper threshold is exceeded, then the information of the pair of entity records of the set of entity records are combined into a single record, and redundant entity records are removed from the MDM system.

Abstract: Alerting a service provider of failed network connectivity includes determining, by a modem device, a loss of connectivity of the modem device with a network. The modem device sends a first notification of the loss of connectivity to a service provider using a first communication. A second notification of a type of the loss of connectivity and a resolution time for the loss of connectivity is received using a second communication. The second communication includes an out-of-band communication. The second communication is sent by the service provider and received by a first device associated with a user.

Abstract: A method for finding the cause of an error or unexpected behavior of a software application includes providing a list of steps to be executed in order to achieve a certain behavior of the application in a usage scenario and providing a decision tree corresponding with the usage scenario. The decision tree comprises decision nodes that correspond with the steps in the sequence of steps to be executed and leaf nodes indicating one or more possible solutions. The method includes scanning log files to determine whether a step in the list of steps to be executed has not been executed and traversing the decision tree when a step in the list of steps has not been executed. A leaf node of the decision tree that corresponds to a non-executed step is determined and a solution is extracted from the determined leaf node.

Abstract: Alerting a service provider of failed network connectivity includes determining, by a modem device, a loss of connectivity of the modem device with a network. The modem device sends a first notification of the loss of connectivity to a service provider using a first communication. A second notification of a type of the loss of connectivity and a resolution time for the loss of connectivity is received using a second communication. The second communication includes an out-of-band communication. The second communication is sent by the service provider and received by a first device associated with a user.

Abstract: A method finding the root cause of errors and/or unexpected behavior of a monitored software application, the method comprising: providing a decision tree corresponding to an error and/or unexpected behavior of a software application, wherein the decision tree comprising multiple nodes, wherein the decision tree further comprising one or more leaf nodes, wherein the leaf nodes indicates at least one reason and one or more possible solutions for the error and/or unexpected behavior; scanning one or more log-files of a software application; determining, based on the decision tree and the scanned log files which step has been not performed by the software application, wherein the non-performed step being indicative for an error and/or unexpected behavior of the software application; determining a leaf node based on the determined non-performed step; extracting information from the leaf node; and providing a reason and/or a solution of the error and/or unexpected behavior.

Abstract: A method for finding the cause of an error or unexpected behavior of a software application includes providing a list of steps to be executed in order to achieve a certain behavior of the application in a usage scenario and providing a decision tree corresponding with the usage scenario. The decision tree comprises decision nodes that correspond with the steps in the sequence of steps to be executed and leaf nodes indicating one or more possible solutions. The method includes scanning log files to determine whether a step in the list of steps to be executed has not been executed and traversing the decision tree when a step in the list of steps has not been executed. A leaf node of the decision tree that corresponds to a non-executed step is determined and a solution is extracted from the determined leaf node.

Abstract: A method finding the root cause of errors and/or unexpected behavior of a monitored software application, the method comprising: providing a decision tree corresponding to an error and/or unexpected behavior of a software application, wherein the decision tree comprising multiple nodes, wherein the decision tree further comprising one or more leaf nodes, wherein the leaf nodes indicates at least one reason and one or more possible solutions for the error and/or unexpected behavior; scanning one or more log-files of a software application; determining, based on the decision tree and the scanned log files which step has been not performed by the software application, wherein the non-performed step being indicative for an error and/or unexpected behavior of the software application; determining a leaf node based on the determined non-performed step; extracting information from the leaf node; and providing a reason and/or a solution of the error and/or unexpected behavior.

Abstract: A method finding the root cause of errors and/or unexpected behavior of a monitored software application, the method comprising: providing a decision tree corresponding to an error and/or unexpected behavior of a software application, wherein the decision tree comprising multiple nodes, wherein the decision tree further comprising one or more leaf nodes, wherein the leaf nodes indicates at least one reason and one or more possible solutions for the error and/or unexpected behavior; scanning one or more log-files of a software application; determining, based on the decision tree and the scanned log files which step has been not performed by the software application, wherein the non-performed step being indicative for an error and/or unexpected behavior of the software application; determining a leaf node based on the determined non-performed step; extracting information from the leaf node; and providing a reason and/or a solution of the error and/or unexpected behavior.

Abstract: A method finding the root cause of errors and/or unexpected behavior of a monitored software application, the method comprising: providing a decision tree corresponding to an error and/or unexpected behavior of a software application, wherein the decision tree comprising multiple nodes, wherein the decision tree further comprising one or more leaf nodes, wherein the leaf nodes indicates at least one reason and one or more possible solutions for the error and/or unexpected behavior; scanning one or more log-files of a software application; determining, based on the decision tree and the scanned log files which step has been not performed by the software application, wherein the non-performed step being indicative for an error and/or unexpected behavior of the software application; determining a leaf node based on the determined non-performed step; extracting information from the leaf node; and providing a reason and/or a solution of the error and/or unexpected behavior.