Abstract: In one aspect, a computerized method for federated data procurement using probabilistic information matching via domain specific heuristics. The method includes implementing procurement of the data from a plurality of online data sources. Each online data source comprises a plurality of measures. The method includes matching and validating the data. The method includes associating a plurality of weights with the plurality of set of domain specific heuristics that are optimized on an ongoing basis as newer data sources are identified. The method includes detecting that new information is collected and adding a plurality of additional heuristics to the domain specific heuristic frameworks.

Abstract: When multiple backup database instances most recently experienced an update is determined. If a most recently updated backup database instance was updated within a defined time period of one or more other backup database instances, a source instance for cloning is selected as the backup database instance that satisfies at least one of a physical or logical proximity criteria relative to a designated database instance. If a difference in update times is greater than the defined time period, e.g., for the two most recent backup database instances, the source instance for cloning is selected to be the most recently updated backup database instance. Cloning to a target instance is performed using the selected backup database instance as a source instance as long as preparatory operations all pass. If not, the source databases are used for the cloning while still being accessible to clients.

Abstract: A method can include storing information about the business service in one or more template type layers; storing information about an instance of the business service in one or more instance type layers; wherein the template type layers include one or more checkpoints that reference information stored in a content addressable store that defines an expected structure of the business service, wherein at least one checkpoint of the template type layers includes a timestamp and a hash value associated with an entry in the content addressable store; and wherein the instance type layers include one or more checkpoints that reference information stored in the content addressable store that defines attributes of the instance of the business service, wherein at least one checkpoint of the instance type layers includes a timestamp and a hash value associated with an entry in the content addressable store.

Abstract: Implementations of a system, method and apparatus described herein receive, for a configuration item in a configuration management database, status indicating an operational state and an automation state associated with the configuration item, and determine whether a conflict will occur with at least one of the operational state or the automation state of the configuration item as a result of a process affecting the configuration item. When the conflict will not occur, a change is made to at least one of the operational state or the automation state of the configuration item in accordance with the process. Upon a conclusion of the process, the change is removed. If the conflict will occur, the process not allowed to continue.

Abstract: Disclosed are methods, apparatuses and systems for collecting transactional and dimensional data. One implementation includes a configuration management database, a first data collection agent operating on a first monitored server to collect metadata associated with the first monitored server from the configuration management database using the first data collection agent, collect metric data from the first monitored server regarding operation of the first monitored server, wherein the metric data includes at least one metric collected from at least one application executing on the first monitored server; and assemble the collected metric data and at least part of the collected metadata into a packet for transmission from the first monitored server to a message bus; and a distributed database configured to receive the packet from the message bus and to store the collected metric data and metadata included in the packet.

Abstract: A failure resistant distributed computing system includes primary and secondary datacenters each comprising a plurality of computerized servers. A control center selects orchestrations from a predefined list and transmits the orchestrations to the datacenters. Transmitted orchestrations include less than all machine-readable actions necessary to execute the orchestrations. The datacenters execute each received orchestration by referencing a full set of actions corresponding to the received orchestration as previously stored or programmed into the computerized server and executing the referenced full set of actions. At least one of the orchestrations comprises a failover operation from the primary datacenter to the secondary datacenter.

Abstract: Disclosed herein are various systems, methods, and apparatuses for providing a system independent Configuration Management Database identification system. In an implementation, a dynamic identification system correlates records of an originating system with records of an Authoritative Configuration Management Database (CMDB) including a set of one or more identifying rules that define a minimum amount of information in order to generate an identifying signature that serves as a common reference between a record of the originating system with a matching Configuration Item (CI) record of the ACMDB, receiving, from the originating system, information to generate an identifying signature, determining that the generated first identifying signature matches a stored identifying signature, and correlating the first record of the originating system corresponding with the generated first identifying signature with the one of the CI records of the ACMDB corresponding with the matching one of the identifying signatures.

Abstract: Disclosed are methods, apparatuses and systems for collecting transactional and dimensional data. One implementation includes a configuration management database, a first data collection agent operating on a first monitored server to collect metadata associated with the first monitored server from the configuration management database using the first data collection agent, collect metric data from the first monitored server regarding operation of the first monitored server, wherein the metric data includes at least one metric collected from at least one application executing on the first monitored server; and assemble the collected metric data and at least part of the collected metadata into a packet for transmission from the first monitored server to a message bus; and a distributed database configured to receive the packet from the message bus and to store the collected metric data and metadata included in the packet.

Abstract: Implementations of a system, method and apparatus described herein receive, for a configuration item in a configuration management database, status indicating an operational state and an automation state associated with the configuration item, and determine whether a conflict will occur with at least one of the operational state or the automation state of the configuration item as a result of a process affecting the configuration item. When the conflict will not occur, a change is made to at least one of the operational state or the automation state of the configuration item in accordance with the process. Upon a conclusion of the process, the change is removed. If the conflict will occur, the process not allowed to continue.

Abstract: A method includes determining that an agent configured an identified node of a computer system, obtaining a definition of the agent that configured the identified node, identifying a configuration item associated with the identified node based at least in part on the definition of the agent that configured the identified node, and updating a service model database with the identified configuration item.

Abstract: When multiple backup database instances most recently experienced an update is determined. If a most recently updated backup database instance was updated within a defined time period of one or more other backup database instances, a source instance for cloning is selected as the backup database instance that satisfies at least one of a physical or logical proximity criteria relative to a designated database instance. If a difference in update times is greater than the defined time period, e.g., for the two most recent backup database instances, the source instance for cloning is selected to be the most recently updated backup database instance. Cloning to a target instance is performed using the selected backup database instance as a source instance as long as preparatory operations all pass. If not, the source databases are used for the cloning while still being accessible to clients.

Abstract: A method can include storing information about the business service in one or more template type layers; storing information about an instance of the business service in one or more instance type layers; wherein the template type layers include one or more checkpoints that reference information stored in a content addressable store that defines an expected structure of the business service, wherein at least one checkpoint of the template type layers includes a timestamp and a hash value associated with an entry in the content addressable store; and wherein the instance type layers include one or more checkpoints that reference information stored in the content addressable store that defines attributes of the instance of the business service, wherein at least one checkpoint of the instance type layers includes a timestamp and a hash value associated with an entry in the content addressable store.

Abstract: When multiple backup database instances most recently experienced an update is determined. If a most recently updated backup database instance was updated within a defined time period of one or more other backup database instances, a source instance for cloning is selected as the backup database instance that satisfies at least one of a physical or logical proximity criteria relative to a designated database instance. If a difference in update times is greater than the defined time period, e.g., for the two most recent backup database instances, the source instance for cloning is selected to be the most recently updated backup database instance. Cloning to a target instance is performed using the selected backup database instance as a source instance as long as preparatory operations all pass. If not, the source databases are used for the cloning while still being accessible to clients.

Abstract: Implementations of a system, method and apparatus described herein receive, for a configuration item in a configuration management database, status indicating an operational state and an automation state associated with the configuration item, and determine whether a conflict will occur with at least one of the operational state or the automation state of the configuration item as a result of a process affecting the configuration item. When the conflict will not occur, a change is made to at least one of the operational state or the automation state of the configuration item in accordance with the process. Upon a conclusion of the process, the change is removed. If the conflict will occur, the process not allowed to continue.

Abstract: A failure resistant distributed computing system includes primary and secondary datacenters each comprising a plurality of computerized servers. A control center selects orchestrations from a predefined list and transmits the orchestrations to the datacenters. Transmitted orchestrations include less than all machine-readable actions necessary to execute the orchestrations. The datacenters execute each received orchestration by referencing a full set of actions corresponding to the received orchestration as previously stored or programmed into the computerized server and executing the referenced full set of actions. At least one of the orchestrations comprises a failover operation from the primary datacenter to the secondary datacenter.

Abstract: Disclosed herein are various systems, methods, and apparatuses for providing a system independent Configuration Management Database identification system. In an implementation, a dynamic identification system correlates records of an originating system with records of an Authoritative Configuration Management Database (CMDB) including a set of one or more identifying rules that define a minimum amount of information in order to generate an identifying signature that serves as a common reference between a record of the originating system with a matching Configuration Item (CI) record of the ACMDB, receiving, from the originating system, information to generate an identifying signature, determining that the generated first identifying signature matches a stored identifying signature, and correlating the first record of the originating system corresponding with the generated first identifying signature with the one of the CI records of the ACMDB corresponding with the matching one of the identifying signatures.

Abstract: A method can include storing information about the business service in one or more template type layers; storing information about an instance of the business service in one or more instance type layers; wherein the template type layers include one or more checkpoints that reference information stored in a content addressable store that defines an expected structure of the business service, wherein at least one checkpoint of the template type layers includes a timestamp and a hash value associated with an entry in the content addressable store; and wherein the instance type layers include one or more checkpoints that reference information stored in the content addressable store that defines attributes of the instance of the business service, wherein at least one checkpoint of the instance type layers includes a timestamp and a hash value associated with an entry in the content addressable store.

Abstract: A failure resistant distributed computing system includes primary and secondary datacenters each comprising a plurality of computerized servers. A control center selects orchestrations from a predefined list and transmits the orchestrations to the datacenters. Transmitted orchestrations include less than all machine-readable actions necessary to execute the orchestrations. The datacenters execute each received orchestration by referencing a full set of actions corresponding to the received orchestration as previously stored or programmed into the computerized server and executing the referenced full set of actions. At least one of the orchestrations comprises a failover operation from the primary datacenter to the secondary datacenter.

Abstract: Implementations of a system, method and apparatus described herein receive, for a configuration item in a configuration management database, status indicating an operational state and an automation state associated with the configuration item, and determine whether a conflict will occur with at least one of the operational state or the automation state of the configuration item as a result of a process affecting the configuration item. When the conflict will not occur, a change is made to at least one of the operational state or the automation state of the configuration item in accordance with the process. Upon a conclusion of the process, the change is removed. If the conflict will occur, the process not allowed to continue.

Abstract: Disclosed herein are various systems, methods, and apparatuses for providing a system independent Configuration Management Database identification system. In an implementation, a dynamic identification system correlates records of an originating system with records of an Authoritative Configuration Management Database (CMDB) including a set of one or more identifying rules that define a minimum amount of information in order to generate an identifying signature that serves as a common reference between a record of the originating system with a matching Configuration Item (CI) record of the ACMDB, receiving, from the originating system, information to generate an identifying signature, determining that the generated first identifying signature matches a stored identifying signature, and correlating the first record of the originating system corresponding with the generated first identifying signature with the one of the CI records of the ACMDB corresponding with the matching one of the identifying signatures.