Abstract: A system may involve persistent storage containing a configuration management database (CMDB) and a non-CMDB table, wherein the CMDB contains configuration items that represent software, devices, or services deployed within a network, and wherein the non-CMDB table contains entries related to operation of the network. The system may also involve one or more processors configured to provide a representation of a graphical user interface (GUI), wherein the GUI contains a first selectable tab that displays classes of the configuration items, a second selectable tab that displays the non-CMDB table, and a canvas for visually depicting query expressions, wherein the classes are selectable to place class GUI elements thereof onto the canvas, wherein the non-CMDB table is selectable to place a table GUI element thereof onto the canvas, and wherein the table GUI element and a particular class GUI element are connectable by a link on the canvas.

Abstract: A system may involve persistent storage containing a configuration management database (CMDB) and a non-CMDB table, wherein the CMDB contains configuration items that represent software, devices, or services deployed within a network, and wherein the non-CMDB table contains entries related to operation of the network. The system may also involve one or more processors configured to provide a representation of a graphical user interface (GUI), wherein the GUI contains a first selectable tab that displays classes of the configuration items, a second selectable tab that displays the non-CMDB table, and a canvas for visually depicting query expressions, wherein the classes are selectable to place class GUI elements thereof onto the canvas, wherein the non-CMDB table is selectable to place a table GUI element thereof onto the canvas, and wherein the table GUI element and a particular class GUI element are connectable by a link on the canvas.

Abstract: Systems and methods for a data synchronization architecture to synchronize provide a forward synchronization of data from a helper instance to a customer facing instance and reverse synchronization of customer configuration data changes to the helper instance are disclosed. Helper instances may be configured to provide an upgrade or maintenance path for a customer facing instance. Helper instances may be a different version and have a different schema than the primary customer facing instance. Database triggers and business rules may be used to manipulate data calculated or discovered by a helper instance prior to synchronization to the primary instance. Database triggers and business rules may fire in the primary instance after each synchronization to perform necessary recalculations or adjust data associations based on data provided from the helper instance. Helper instances may queue data over time and then perform a synchronization of data from the queue.

Abstract: A system may involve persistent storage containing a configuration management database (CMDB) and a non-CMDB table, wherein the CMDB contains configuration items that represent software, devices, or services deployed within a network, and wherein the non-CMDB table contains entries related to operation of the network. The system may also involve one or more processors configured to provide a representation of a graphical user interface (GUI), wherein the GUI contains a first selectable tab that displays classes of the configuration items, a second selectable tab that displays the non-CMDB table, and a canvas for visually depicting query expressions, wherein the classes are selectable to place class GUI elements thereof onto the canvas, wherein the non-CMDB table is selectable to place a table GUI element thereof onto the canvas, and wherein the table GUI element and a particular class GUI element are connectable by a link on the canvas.

Abstract: Systems and methods for a data synchronization architecture to synchronize provide a forward synchronization of data from a helper instance to a customer facing instance and reverse synchronization of customer configuration data changes to the helper instance are disclosed. Helper instances may be configured to provide an upgrade or maintenance path for a customer facing instance. Helper instances may be a different version and have a different schema than the primary customer facing instance. Database triggers and business rules may be used to manipulate data calculated or discovered by a helper instance prior to synchronization to the primary instance. Database triggers and business rules may fire in the primary instance after each synchronization to perform necessary recalculations or adjust data associations based on data provided from the helper instance. Helper instances may queue data over time and then perform a synchronization of data from the queue.