Abstract: Persistent storage may contain a list of discovery commands, the discovery commands respectively associated with lists of network addresses. A discovery validation application, when executed by one or more processors, may be configured to: read, from the persistent storage, the list of discovery commands and the lists of network addresses; for each discovery command in the list of discovery commands, transmit, by way of one or more proxy servers deployed external to the system, the discovery command to each network address in the respectively associated list of network addresses; receive, by way of the one or more proxy servers, discovery results respectively corresponding to each of the discovery commands that were transmitted, wherein the discovery results either indicate success or failure of the discovery commands; and write, to the persistent storage, the discovery results.

Abstract: A first type of service map may be converted to a second type of a service map by adding a conversion tag to a set of configuration items (CIs) presented by the service map. The conversion tag includes data that may be used to link historical information associated with the service map of the first type, such as information related to incidents, alerts, change requests, and other events, to the second type. A second service map may be generated using the conversion tags and/or tag-based filtering processes such that the second service map displays different CIs as compared to the first service map.

Abstract: Persistent storage may contain an input discovery payload that contains entries representing configuration items and relationships therebetween, wherein the configuration items contain attributes defining devices, components, or applications on a network.

Abstract: A computational instance may includes a set of computing devices and a configuration management database (CMDB), wherein the CMDB contains a representation of a service deployed on a managed network, wherein the representation of the service includes metadata, service group membership, and an entry point, and wherein the computational instance is configured to: receive an instruction to export the representation of the service to a file; copy, to a metadata object in the file, the metadata; determine a hierarchical subset of the service groups that are related to the service; write, to one or more service group objects in the file, the hierarchical subset of the service groups; determine, from a list of entry points of the managed network, that the entry point is of the service; and write, to an entry point object in the file, the entry point.

Abstract: Systems, methods, and media are presented that are used to recompute a service model to match data in a configuration management database. Recomputing includes detecting a change to a configuration item in a configuration management database and marking a recomputing environment indicating a recomputing environment to be recomputed based on the change. Using a recomputation job, a service environment database is queried and a response is received from the service environment indicating at least the recomputing environment. The recomputation job then recomputes the service environment to match a service model to the change in the configuration management database.

Abstract: Attributes of a configuration item record of a configuration management database (CMDB) are received. Based on the received attributes, a determination is made that the configuration item record belongs to a new child class and no longer belongs to a previously identified child class. While maintaining a same identifier in the configuration item record, a classification of the configuration item record is changed to the new child class including by adding one or more attributes of the new child class to the configuration item record and removing one or more attributes of the previously identified child class from the configuration item record.

Abstract: Systems, methods, and media for utilizing a discovery pattern affinity table are disclosed herein. The pattern affinity table includes one or more discovery patterns and associated data. The pattern affinity table is updated upon execution of a new or existing discovery pattern to reflect near real-time data associated with the discovery patterns. The pattern affinity table reduces an amount of time and computing resources needed to perform a discovery process by executing the discovery patterns stored in the affinity table.

Abstract: Attributes of a configuration item record of a configuration management database (CMDB) are received. Based on the received attributes, a determination is made that the configuration item record belongs to a new child class and no longer belongs to a previously identified child class. While maintaining a same identifier in the configuration item record, a classification of the configuration item record is changed to the new child class including by adding one or more attributes of the new child class to the configuration item record and removing one or more attributes of the previously identified child class from the configuration item record.

Abstract: A computational instance of a remote network management platform includes a database that contains a plurality of CI records corresponding to a set of computing devices, a set of software applications, and a network-based service. The database also contains a definition of a service model that represents the set of computing devices, the set of software applications, and relationships therebetween that facilitate providing the network-based service. The computational instance also includes one or more server devices configured: to receive an indication of a change to a CI record of the plurality of CI record; add, to a change record table, a change record corresponding to the change to the CI record; select, for the service layer based on a change type specified in the change record, a service model re-computation mode; and re-compute a service layer in accordance with the service model re-computation mode.

Abstract: A computational instance may includes a set of computing devices and a configuration management database (CMDB), wherein the CMDB contains a representation of a service deployed on a managed network, wherein the representation of the service includes metadata, service group membership, and an entry point, and wherein the computational instance is configured to: receive an instruction to export the representation of the service to a file; copy, to a metadata object in the file, the metadata; determine a hierarchical subset of the service groups that are related to the service; write, to one or more service group objects in the file, the hierarchical subset of the service groups; determine, from a list of entry points of the managed network, that the entry point is of the service; and write, to an entry point object in the file, the entry point.

Abstract: Systems, methods, and media are presented that are used to recompute a service model to match data in a configuration management database. Recomputing includes detecting a change to a configuration item in a configuration management database and marking a recomputing environment indicating a recomputing environment to be recomputed based on the change. Using a recomputation job, a service environment database is queried and a response is received from the service environment indicating at least the recomputing environment. The recomputation job then recomputes the service environment to match a service model to the change in the configuration management database.

Abstract: Systems, methods, and media for tracking configuration file changes are presented. Tracking configuration file changes include receiving a definition of a pattern used to identify a configuration file to be tracked. Horizontal discovery is performed using the pattern to discover the configuration file based at least in part on the pattern. If an entry in a configuration management database corresponds to a previously discovered configuration file has not been discovered during the horizontal discovery, the entry is deleted from the configuration management database. With discovered configuration files, the configuration management database is updated with the discovered configuration file as a configuration item. Using the configuration management database changes to the configuration file are tracked and displayed in a timeline and history of the discovered configuration file.

Abstract: A computational instance may includes a set of computing devices and a configuration management database (CMDB), wherein the CMDB contains a representation of a service deployed on a managed network, wherein the representation of the service includes metadata, service group membership, and an entry point, and wherein the computational instance is configured to: receive an instruction to export the representation of the service to a file; copy, to a metadata object in the file, the metadata; determine a hierarchical subset of the service groups that are related to the service; write, to one or more service group objects in the file, the hierarchical subset of the service groups; determine, from a list of entry points of the managed network, that the entry point is of the service; and write, to an entry point object in the file, the entry point.

Abstract: A computational instance of a remote network management platform includes a database that contains a plurality of CI records corresponding to a set of computing devices, a set of software applications, and a network-based service. The database also contains a definition of a service model that represents the set of computing devices, the set of software applications, and relationships therebetween that facilitate providing the network-based service. The computational instance also includes one or more server devices configured: to receive an indication of a change to a CI record of the plurality of CI record; add, to a change record table, a change record corresponding to the change to the CI record; select, for the service layer based on a change type specified in the change record, a service model re-computation mode; and re-compute a service layer in accordance with the service model re-computation mode.

Abstract: Systems, methods, and media are presented that are used to recompute a service model to match data in a configuration management database. Recomputing includes detecting a change to a configuration item in a configuration management database and marking a recomputing environment indicating a recomputing environment to be recomputed based on the change. Using a recomputation job, a service environment database is queried and a response is received from the service environment indicating at least the recomputing environment. The recomputation job then recomputes the service environment to match a service model to the change in the configuration management database.

Abstract: Systems, methods, and media for tracking configuration file changes are presented. Tracking configuration file changes include receiving a definition of a pattern used to identify a configuration file to be tracked. Horizontal discovery is performed using the pattern to discover the configuration file based at least in part on the pattern. If an entry in a configuration management database corresponds to a previously discovered configuration file has not been discovered during the horizontal discovery, the entry is deleted from the configuration management database. With discovered configuration files, the configuration management database is updated with the discovered configuration file as a configuration item. Using the configuration management database changes to the configuration file are tracked and displayed in a timeline and history of the discovered configuration file.

Abstract: Systems, methods, and media are presented that are used to recompute a service model to match data in a configuration management database. Recomputing includes detecting a change to a configuration item in a configuration management database and marking a recomputing environment indicating a recomputing environment to be recomputed based on the change. Using a recomputation job, a service environment database is queried and a response is received from the service environment indicating at least the recomputing environment. The recomputation job then recomputes the service environment to match a service model to the change in the configuration management database.

Abstract: Systems, methods, and media for tracking configuration file changes are presented. Tracking configuration file changes include receiving a definition of a pattern used to identify a configuration file to be tracked. Horizontal discovery is performed using the pattern to discover the configuration file based at least in part on the pattern. If an entry in a configuration management database corresponds to a previously discovered configuration file has not been discovered during the horizontal discovery, the entry is deleted from the configuration management database. With discovered configuration files, the configuration management database is updated with the discovered configuration file as a configuration item. Using the configuration management database changes to the configuration file are tracked and displayed in a timeline and history of the discovered configuration file.

Abstract: Systems, methods, and media for tracking configuration file changes are presented. Tracking configuration file changes include receiving a definition of a pattern used to identify a configuration file to be tracked. Horizontal discovery is performed using the pattern to discover the configuration file based at least in part on the pattern. If an entry in a configuration management database corresponds to a previously discovered configuration file has not been discovered during the horizontal discovery, the entry is deleted from the configuration management database. With discovered configuration files, the configuration management database is updated with the discovered configuration file as a configuration item. Using the configuration management database changes to the configuration file are tracked and displayed in a timeline and history of the discovered configuration file.