Abstract: An example system includes (i) a software product having a plurality of code units that accesses a database, (ii) a processor, and (iii) a non-transitory computer readable storage medium having stored thereon software tests and instructions that cause the processor to: execute the software tests on a first version of the software product; determine a first mapping between each respective software test and one or more of the code units; determine a second mapping between each respective software test and one or more data units in the database; determine that, between a second version and the first version of the software product, a particular code and data unit have changed; select, from the first and the second mappings, a set of software tests with mappings to the particular code unit or data unit; and execute the set of software tests on the second version of the software product.

Abstract: Systems and methods for processing alerts indicative of conditions of nodes of a computing infrastructure are herein disclosed as comprising, in an implementation, generating a node hierarchy comprising nodes associated with a service model, wherein relationships between the nodes are based on impact rules, identifying alerts related to the node hierarchy, wherein the alerts are indicative of impairments affecting at least a portion of the node hierarchy, and performing impact calculation for nodes of the node hierarchy based on the identified alerts. In an implementation, the impact values may be calculated in parallel for nodes indicated for processing. In an implementation, the nodes associated with the service model represent infrastructure or applicative resources and comprise nodes included in the service model and nodes related to, but not included in, the service model.

Abstract: A remote network management platform software application containing application programming interfaces (APIs) may be configured to facilitate the use of plugin software. A particular API may be associated with logic configured to check whether a toggle variable is active or inactive. A first unit of program code may be configured to execute when the toggle variable is inactive, and a second unit of program code may be configured to execute when the toggle variable is active. First plugin software may be implemented in a scripting language. The first plugin software, whether enabled or disabled, might not affect the toggle variable. Second plugin software may also be implemented in the scripting language. The second plugin software, when enabled, is configured to set the toggle variable as active.

Abstract: Various embodiments are disclosed herein that provide users of a cloud computing system with the ability to display, prioritize, and/or handle enterprise alerts, e.g., in the form of a sorted list. In some embodiments, these alerts may be ranked according to a ‘smart priority’ calculation. The ‘smart priority’ calculation may take into account a number of factors related to given alert, e.g.: severity level, business criticality level, role, number of affected system components, types of affected system components, etc. These factors may be combined in the ‘smart priority’ calculation in a hierarchical fashion, e.g., based on a predetermined (or user-customized ranking) of the importance and/or weighting of the various factors. By seeing the historical and status metadata information relating to the alerts, users may more quickly understand which alerts to address first—and what possible solutions may be employed in order to close out the open alerts in the system.

Abstract: The present approach relates to event monitoring and management of an instance using a generated service map, allowing monitoring of CIs (e.g., applications) and connections that are currently active in a user's specific instance. A self-monitoring solution is generated for a user (e.g., via an application) that depicts status, configuration, and errors related to the user's instance. In certain implementations, the present techniques involve applying internal knowledge of the working of a user's instance and applications to perform the self-monitoring, and determine when an alert should be generated. Further, the present techniques may involve making a determination to provide a user with a self-help solution in addition or based on the self-monitoring of the user's instance.

Abstract: Systems and methods for generating a graphical display region including a synchronized display of alert data and impact data indicative of conditions of a computing infrastructure are herein disclosed as comprising, in an implementation, identifying alerts, each alert having a timestamp indicative of a first time at which it was identified, performing an impact calculation to generate the impact data based on alerts valid as of a second time proximate to an impact calculation start time, and generating a graphical display region including impact data valid as of a display time and alert data indicative of the alerts valid as of the second time.

Abstract: Messages indicative of events are transmitted from a computer network to a management system using an agent device. The agent device receives a web service event collector from the management system. The web service event collector includes event message transformation instructions and an endpoint definition. After the web service event collector is initialized, an event message transmitted from an event source is received using the web service event collector. The event message indicates an event associated with the computer network. Using the event message transformation instructions, the event message is transformed into a format usable by the management system. The transformed event message is then transmitted to the management system.

Abstract: Systems and methods for generating a graphical display region including a synchronized display of alert data and impact data indicative of conditions of a computing infrastructure are herein disclosed as comprising, in an implementation, identifying alerts, each alert having a timestamp indicative of a first time at which it was identified, performing an impact calculation to generate the impact data based on alerts valid as of a second time proximate to an impact calculation start time, and generating a graphical display region including impact data valid as of a display time and alert data indicative of the alerts valid as of the second time.

Abstract: An application monitoring infrastructure that enables application configuration changes on multiple machines across multiple OS types to be tracked by identifying data containers that are to be monitored for changes, detecting a change to a monitored data container, and storing data representative of a changed version of the monitored data container responsive to detecting that the monitored container was changed. The data containers that are to be monitored for changes are identified from templates, and a unique template is provisioned for each of the applications.

Abstract: Techniques are disclosed for automatic remediation of application performance degradations caused by configuration changes. In one embodiment, a learning module keeps track of application configuration changes and subsequent effects on the application's performance. The learning module creates new potential remediation rules based on correlations between such configuration changes and performance degradations or improvements. The learning module affirms such potential rules if the correlation between the configuration changes and degradations or improvements are repeatedly observed, and vice versa.

Abstract: An application monitoring infrastructure enables application configuration changes on multiple machines across multiple OS types to be tracked, and correlated to performance degradation and outages by receiving change event data associated with change events occurring at each computer in the computer system, each change event data including an identifier for the associated change event, a path to a data container that was changed, a time stamp representative of when the data container was changed, an identifier for an application that is affected by the change to the data container, and the time stamp representative of when the monitored data container was changed, determining a time at which correlation is to be carried out and a target application for which correlation is to be carried out, and identifying change events associated with the target application that have time stamps that are within a predetermined proximity to the determined time.

Abstract: Systems and methods for processing alerts indicative of conditions of nodes of a computing infrastructure are herein disclosed as comprising, in an implementation, generating a node hierarchy comprising nodes associated with a service model, wherein relationships between the nodes are based on impact rules, identifying alerts related to the node hierarchy, wherein the alerts are indicative of impairments affecting at least a portion of the node hierarchy, and performing impact calculation for nodes of the node hierarchy based on the identified alerts. In an implementation, the impact values may be calculated in parallel for nodes indicated for processing. In an implementation, the nodes associated with the service model represent infrastructure or applicative resources and comprise nodes included in the service model and nodes related to, but not included in, the service model.

Abstract: Systems and methods for generating a graphical display region including a synchronized display of alert data and impact data indicative of conditions of a computing infrastructure are herein disclosed as comprising, in an implementation, identifying alerts, each alert having a timestamp indicative of a first time at which it was identified, performing an impact calculation to generate the impact data based on alerts valid as of a second time proximate to an impact calculation start time, and generating a graphical display region including impact data valid as of a display time and alert data indicative of the alerts valid as of the second time.

Abstract: An application monitoring infrastructure that enables application configuration changes on multiple machines across multiple OS types to be tracked by identifying data containers that are to be monitored for changes, detecting a change to a monitored data container, and storing data representative of a changed version of the monitored data container responsive to detecting that the monitored container was changed. The data containers that are to be monitored for changes are identified from templates, and a unique template is provisioned for each of the applications.

Abstract: An application monitoring infrastructure that enables application configuration changes on multiple machines across multiple OS types to be tracked by identifying data containers that are to be monitored for changes, detecting a change to a monitored data container, and storing data representative of a changed version of the monitored data container responsive to detecting that the monitored container was changed. The data containers that are to be monitored for changes are identified from templates, and a unique template is provisioned for each of the applications.

Abstract: Techniques are disclosed for automatic remediation of application performance degradations caused by configuration changes. In one embodiment, a learning module keeps track of application configuration changes and subsequent effects on the application's performance. The learning module creates new potential remediation rules based on correlations between such configuration changes and performance degradations or improvements. The learning module affirms such potential rules if the correlation between the configuration changes and degradations or improvements are repeatedly observed, and vice versa.

Abstract: An application monitoring infrastructure that enables application configuration changes on multiple machines across multiple OS types to be tracked by identifying data containers that are to be monitored for changes, detecting a change to a monitored data container, and storing data representative of a changed version of the monitored data container responsive to detecting that the monitored container was changed. The data containers that are to be monitored for changes are identified from templates, and a unique template is provisioned for each of the applications.

Abstract: An application monitoring infrastructure that enables application configuration changes on multiple machines across multiple OS types to be tracked by identifying data containers that are to be monitored for changes, detecting a change to a monitored data container, and storing data representative of a changed version of the monitored data container responsive to detecting that the monitored container was changed. The data containers that are to be monitored for changes are identified from templates, and a unique template is provisioned for each of the applications.

Abstract: An application monitoring infrastructure that enables application configuration changes on multiple machines across multiple OS types to be tracked by identifying data containers that are to be monitored for changes, detecting a change to a monitored data container, and storing data representative of a changed version of the monitored data container responsive to detecting that the monitored container was changed. The data containers that are to be monitored for changes are identified from templates, and a unique template is provisioned for each of the applications.

Abstract: An application monitoring infrastructure enables application configuration changes on multiple machines across multiple OS types to be tracked, and correlated to performance degradation and outages by receiving change event data associated with change events occurring at each computer in the computer system, each change event data including an identifier for the associated change event, a path to a data container that was changed, a time stamp representative of when the data container was changed, an identifier for an application that is affected by the change to the data container, and the time stamp representative of when the monitored data container was changed, determining a time at which correlation is to be carried out and a target application for which correlation is to be carried out, and identifying change events associated with the target application that have time stamps that are within a predetermined proximity to the determined time.