System and method for alert insight in configuration management databases (CMDBs)

CROSS-REFERENCE TO RELATED APPLICATION

0001This application is a continuation of U.S. patent application Ser. No. 15/943,490, filed Apr. 2, 2018, issuing as U.S. Pat. No. 10,824,616 on Nov. 3, 2020, which is incorporated herein by reference in its entirety.

BACKGROUND

0002The present disclosure relates generally to configuration management databases (CMDB s) and, more particularly, to providing enhanced alert insight by using related configuration items (CIs) in CMDBs.

0003This section is intended to introduce the reader to various aspects of art that may be related to various aspects of the present disclosure, which are described and/or claimed below. This discussion is believed to be helpful in providing the reader with background information to facilitate a better understanding of the various aspects of the present disclosure. Accordingly, it should be understood that these statements are to be read in this light, and not as admissions of prior art.

0004Cloud computing relates to the sharing of computing resources that are generally accessed via the Internet. In particular, a cloud computing infrastructure allows users, such as individuals and/or enterprises, to access a shared pool of computing resources, such as servers, storage devices, networks, applications, and/or other computing based services. By doing so, users are able to access computing resources on demand that are located at remote locations, which resources may be used to perform a variety computing functions (e.g., storing and/or processing large quantities of computing data). For enterprise and other organization users, cloud computing provides flexibility in accessing cloud computing resources without accruing large up-front costs, such as purchasing expensive network equipment or investing large amounts of time in establishing a private network infrastructure. Instead, by utilizing cloud computing resources, users are able redirect their resources to focus on their enterprise's core functions.

0005In modern communication networks, examples of cloud computing services a user may utilize include so-called software as a service (SaaS) and platform as a service (PaaS) technologies. SaaS is a delivery model that provides software as a service rather than an end product. Instead of utilizing a local network or individual software installations, software is typically licensed on a subscription basis, hosted on a remote machine, and accessed by client customers as needed. For example, users are generally able to access a variety of enterprise and/or information technology (IT)-related software via a web browser. PaaS acts an extension of SaaS that goes beyond providing software services by offering customizability and expandability features to meet a user's needs. For example, PaaS can provide a cloud-based developmental platform for users to develop, modify, and/or customize applications and/or automating enterprise operations without maintaining network infrastructure and/or allocating computing resources normally associated with these functions.

0006Within the context of cloud computing solutions for CMDBs, users may be asked to deal with ever increasing amounts of data, e.g., with respect to the number of Configuration Items (CIs) stored in the CMDB (including such CIs' relevant metadata, such as manufacturer, vendor, location, etc.), as well as the alerts, service metrics, and maintenance status information related to such CIs. In fact, the amount of data collected and stored in today's cloud computing solutions, such as CMDBs, may be orders of magnitude greater than what was historically collected and stored. Users tasked with automating and/or troubleshooting enterprise, IT, and/or other organization-related functions (e.g., incident tracking and/or help desk-related functions) navigate ever increasing amounts of data to properly and efficiently perform their job functions.

0007In a logical sense, CIs of a CMDB can be related in a number of ways. For example, a first CI may host or execute a second CI, the first CI may operate in parallel with the second CI, the first CI may be a part of a hierarchy that include the second CI, and so forth. As such, in the absence of present disclosure, it is recognized that a widely accepted definition for relationships between CIs of a CMDB is lacking in the field. As such, when an issue arises with a particular CI of a CMDB, traditional CMDBs lack a feature that enables the user to identify related CIs or determine how the issue has historically affected the related CIs. With this in mind, the following embodiments are directed to defining relationships between CIs and enhancing user experience by enabling the user to compare issues experienced by a particular CI with issues experienced by related CIs of the CMDB.

SUMMARY

0008A summary of certain embodiments disclosed herein is set forth below. It should be understood that these aspects are presented merely to provide the reader with a brief summary of these certain embodiments and that these aspects are not intended to limit the scope of this disclosure. Indeed, this disclosure may encompass a variety of aspects that may not be set forth below.

0009Present embodiments are directed toward improving a user's ability to explore and determine a root cause and/or a solution for a particular alert associated with a particular CI of a CMDB. To do this, present embodiments include instructions that enable a client instance to determine CIs that are related to a particular CI. In particular, present embodiments include a method of determining CIs that are related to a particular CI based on a combination of a topological relationship and an alert group relationship between the particular CI and the other CIs associated with the client instance. Accordingly, after the particular CI has been associated with the particular alert, present embodiments enable the client instance to determine how frequently the CI has been associated with the particular and other issues (e.g., INTs, CHGs, PRBs), as well as how frequently related CI have experienced the particular alert and other issues. Additionally, present embodiments include a graphical user interface (GUI) designed to concurrently present data indicating the frequency at which the particular CI has historically experienced issues alongside data indicating the frequency at which the related CIs have historically experienced issues.

0010In an example embodiment, a client instance associated with a CMDB platform is executed by a computing system. The client instance is configured to receive a request identifying a particular CI and a particular alert. Using the particular CI identified in the request, the client instance determines a respective combined score for each of a plurality of CIs by combining a respective topological relationship score and a respective alert group relationship score of each CI relative to the particular CI. The client instance determines that CIs in the plurality of CIs having a respective combined score that is greater than a predetermined threshold value are related to the particular CI. The client instance determines frequency data for issues (e.g., alerts, INTs, CHGs, and PRBs) associated with the particular CI, as well as frequency data for issues (e.g., alerts, INTs, CHGs, and PRBs) associated with the related CIs, and provides this information to the client device for concurrent presentation on the client device.

BRIEF DESCRIPTION OF THE DRAWINGS

0011Various aspects of this disclosure may be better understood upon reading the following detailed description and upon reference to the drawings in which:

0012<figref idref="DRAWINGS">FIG. <b>1</b></figref> is a block diagram of an embodiment of a cloud computing system in which embodiments of the present disclosure may operate;

0013<figref idref="DRAWINGS">FIG. <b>2</b></figref> is a block diagram of an embodiment of a multi-instance cloud architecture in which embodiments of the present disclosure may operate;

0014<figref idref="DRAWINGS">FIG. <b>3</b></figref> is a block diagram of an alert insight system that is associated with a CMDB platform, in accordance with embodiments of the present technique;

0015<figref idref="DRAWINGS">FIG. <b>4</b></figref> is a flow diagram of a process whereby a client instance associated with the CMDB platform handles a request to explore a particular issue for a particular CI, in accordance with embodiments of the present technique;

0016<figref idref="DRAWINGS">FIG. <b>5</b></figref> is a flow diagram of a process whereby the client instance determines CIs that are related to a particular CI as part of handling the request to explore the particular issue for the particular CI, in accordance with embodiments of the present technique; and

0017<figref idref="DRAWINGS">FIG. <b>6</b></figref> is a simulated screenshot of an embodiment of a graphical user interface (GUI) that may operate in conjunction with the client instance to provide information to a client device for presentation to a user, in accordance with embodiments of the present technique.

DETAILED DESCRIPTION OF SPECIFIC EMBODIMENTS

0018One or more specific embodiments will be described below. In an effort to provide a concise description of these embodiments, not all features of an actual implementation are described in the specification. It should be appreciated that in the development of any such actual implementation, as in any engineering or design project, numerous implementation-specific decisions must be made to achieve the developers' specific goals, such as compliance with system-related and enterprise-related constraints, which may vary from one implementation to another. Moreover, it should be appreciated that such a development effort might be complex and time consuming, but would nevertheless be a routine undertaking of design, fabrication, and manufacture for those of ordinary skill having the benefit of this disclosure.

0019As used herein, the term “computing system” refers to a single electronic computing device that includes, but is not limited to a single computer, virtual machine, virtual container, host, server, laptop, and/or mobile device, or to a plurality of electronic computing devices working together to perform the function described as being performed on or by the computing system. As used herein, the term “medium” refers to one or more non-transitory, computer-readable physical media that together store the contents described as being stored thereon. Embodiments may include non-volatile secondary storage, read-only memory (ROM), and/or random-access memory (RAM). As used herein, the term “application” refers to one or more computing modules, programs, processes, workloads, threads and/or a set of computing instructions executed by a computing system. Example embodiments of an application include software modules, software objects, software instances and/or other types of executable code. As used herein, the term “configuration item” or “CI” refers to a record for any component (e.g., computer, device, piece of software, database table, script, webpage, piece of metadata, and so forth) in an enterprise network, for which all relevant data, such as manufacturer, vendor, location, or similar data, is stored in a CMDB. As used herein, the terms alerts, incidents (INTs), changes (CHGs), and problems (PRBs) are used in accordance with the generally accepted use of the terminology for CMDBs. Moreover, the term “issues” with respect to a CI of a CMDB collectively refers to alerts, INTs, CHGs, and PRBs associated with the CI.

0020Present embodiments are directed toward an alert insight system of a CMDB platform that enables client instances to determine which CIs are related to a particular CI, such that frequency data for various issues (e.g., alerts, INTs, CHGs, and PRBs) associated with the particular CI and related CIs can be generated for presentation to a user. In particular, present embodiments include a method of determining CIs that are related to a particular CI in a client instance of a CMDB platform based on a combination of a topological relationship and an alert group relationship between the particular CI and other CIs of the client instance. As discussed, for a particular alert associated with a particular CI, present embodiments enable the client instance to determine how frequently the particular CI generates the particular alert and other issues (e.g., INTs, CHGs, and PRBs) associated with the particular CI. Further, present embodiments enable the client instance to determine how frequently related CIs generate the particular alert and other issues (e.g., INTs, CHGs, and PRBs) associated with the related CIs. Additionally, present embodiments include a graphical user interface (GUI) designed to present frequency data for issues associated with the particular CI and related CIs in a concise and organized format, which enables a user to more quickly and easily explore and determine a root cause and/or a solution for the particular CI generating the particular alert.

0021Turning now to <figref idref="DRAWINGS">FIG. <b>1</b></figref>, a schematic diagram of an embodiment of a computing system <b>10</b>, such as a cloud computing system, where embodiments of the present disclosure may operate, is illustrated. Computing system <b>10</b> may include a client network <b>12</b>, network <b>18</b> (e.g., the Internet), and CMDB platform <b>20</b>. In one embodiment, the client network <b>12</b> may be a local private network, such as local area network (LAN) that includes a variety of network devices that include, but are not limited to, switches, servers, and routers. In another embodiment, the client network <b>12</b> represents an enterprise network that could include one or more LANs, virtual networks, data centers <b>22</b>, and/or other remote networks. As shown in <figref idref="DRAWINGS">FIG. <b>1</b></figref>, the client network <b>12</b> is able to connect to one or more client devices <b>14</b>A, <b>14</b>B, and <b>14</b>C so that the client devices are able to communicate with each other and/or with the network hosting the CMDB platform <b>20</b>. The client devices <b>14</b>A-C may be computing systems and/or other types of computing devices generally referred to as Internet of Things (IoT) devices that access cloud computing services, for example, via a web browser application or via an edge device <b>16</b> that may act as a gateway between the client devices and the CMDB platform <b>20</b>. <figref idref="DRAWINGS">FIG. <b>1</b></figref> also illustrates that the client network <b>12</b> includes a management, instrumentation, and discovery (MID) server <b>17</b> that facilitates communication of data between the network hosting the CMDB platform <b>20</b>, other external applications, data sources, and services, and the client network <b>12</b>. Although not specifically illustrated in <figref idref="DRAWINGS">FIG. <b>1</b></figref>, the client network <b>12</b> may also include a connecting network device (e.g., a gateway or router) or a combination of devices that implement a customer firewall or intrusion protection system.

0022For the illustrated embodiment, <figref idref="DRAWINGS">FIG. <b>1</b></figref> illustrates that client network <b>12</b> is coupled to a network <b>18</b>. The network <b>18</b> may include one or more computing networks, such as other LANs, wide area networks (WAN), the Internet, and/or other remote networks, in order to transfer data between the client devices <b>14</b>A-C and the network hosting the CMDB platform <b>20</b>. Each of the computing networks within network <b>18</b> may contain wired and/or wireless programmable devices that operate in the electrical and/or optical domain. For example, network <b>18</b> may include wireless networks, such as cellular networks (e.g., Global System for Mobile Communications (GSM) based cellular network), WiFi® networks (WIFI is a registered trademark owned by Wi-Fi Alliance Corporation), and/or other suitable radio-based networks. The network <b>18</b> may also employ any number of network communication protocols, such as Transmission Control Protocol (TCP) and Internet Protocol (IP). Although not explicitly shown in <figref idref="DRAWINGS">FIG. <b>1</b></figref>, network <b>18</b> may include a variety of network devices, such as servers, routers, network switches, and/or other network hardware devices configured to transport data over the network <b>18</b>.

0023In <figref idref="DRAWINGS">FIG. <b>1</b></figref>, the network hosting the CMDB platform <b>20</b> may be a remote network (e.g., a cloud network) that is able to communicate with the client devices <b>14</b>A-C via the client network <b>12</b> and network <b>18</b>. The network hosting the CMDB platform <b>20</b> provides additional computing resources to the client devices <b>14</b>A-C and/or client network <b>12</b>. For example, by utilizing the network hosting the CMDB platform <b>20</b>, users of client devices <b>14</b>A-C are able to build and execute applications, such as CMDBs or other automated processes for various enterprise, IT, and/or other organization-related functions, such as alert processing and handling. In one embodiment, the network hosting the CMDB platform <b>20</b> includes one or more data centers <b>22</b>, where each data center could correspond to a different geographic location. Each of the data centers <b>22</b> includes a plurality of server instances <b>24</b> (also referred to herein as application instances or application server instances), where each server instance can be implemented on a physical computing system, such as a single electronic computing device (e.g., a single physical hardware server) or could be in the form a multi-computing device (e.g., multiple physical hardware servers). Examples of server instances <b>24</b> include, but are not limited to a web server instance (e.g., a unitary Apache installation), an application server instance (e.g., unitary Java® Virtual Machine), and/or a database server instance, e.g., a unitary MySQL® catalog (MySQL® is a registered trademark owned by MySQL AB A COMPANY).

0024To utilize computing resources within the CMDB platform <b>20</b>, network operators may choose to configure the data centers <b>22</b> using a variety of computing infrastructures. In one embodiment, one or more of the data centers <b>22</b> are configured using a multi-tenant cloud architecture, such that one of the server instances <b>24</b> handles requests and serves multiple customers. In other words, data centers with multi-tenant cloud architecture commingle and store data from multiple customers, where multiple customer instances are assigned to one of the server instances <b>24</b>. In a multi-tenant cloud architecture, the particular server instance of the server instances <b>24</b> distinguishes between and segregates data and other information of the various customers. For example, a multi-tenant cloud architecture could assign a particular identifier for each customer in order to identify and segregate the data from each customer. Generally, implementing a multi-tenant cloud architecture may suffer from various drawbacks, such as a failure to a particular one of the server instances <b>24</b> causing outages for all customers allocated to the particular server instance.

0025In another embodiment, one or more of the data centers <b>22</b> are configured using a multi-instance cloud architecture to provide every customer its own unique customer instance. For example, a multi-instance cloud architecture could provide each customer instance with its own dedicated application server and dedicated database server. In other examples, the multi-instance cloud architecture could deploy a single server instance and/or other combinations of server instances <b>24</b>, such as one or more dedicated web server instances, one or more dedicated application server instances, and one or more database server instances, for each customer instance. In a multi-instance cloud architecture, multiple customer instances could be installed on a single physical hardware server, where each customer instance is allocated certain portions of the physical server resources, such as computing memory, storage, and processing power. By doing so, each customer instance has its own unique software stack that provides the benefit of data isolation, relatively less downtime for customers to access the CMDB platform <b>20</b>, and customer-driven upgrade schedules. An example of implementing a customer instance within a multi-instance cloud architecture will be discussed in more detail below with reference to <figref idref="DRAWINGS">FIG. <b>2</b></figref>.

0026<figref idref="DRAWINGS">FIG. <b>2</b></figref> is a schematic diagram of an embodiment of a multi-instance cloud architecture <b>40</b> where embodiments of the present disclosure may operate. <figref idref="DRAWINGS">FIG. <b>2</b></figref> illustrates that the multi-instance cloud architecture <b>40</b> includes the client network <b>12</b> and the network <b>18</b> that connect to two data centers <b>22</b>A and <b>22</b>B. Data centers <b>22</b>A and <b>22</b>B can correspond to data centers <b>22</b> illustrated in <figref idref="DRAWINGS">FIG. <b>1</b></figref> as located within the CMDB platform <b>20</b>. Using <figref idref="DRAWINGS">FIG. <b>2</b></figref> as an example, network environment and service provider cloud infrastructure client instance <b>42</b> (also referred to herein as a simply client instance <b>42</b>) is comprised of four dedicated application server instances <b>24</b>A, <b>24</b>B, <b>24</b>C, and <b>24</b>D and two dedicated database server instances <b>44</b>A and <b>44</b>B. Stated another way, the application server instances <b>24</b>A-<b>24</b>D and database server instances <b>44</b>A and <b>44</b>B are not shared with other client instances. Other embodiments of the multi-instance cloud architecture <b>40</b> could include other types of dedicated server instances, such as a web server instance. For example, the client instance <b>42</b> could include the four dedicated application server instances <b>24</b>A-<b>24</b>D, two dedicated database server instances <b>44</b>A and <b>44</b>B, and four dedicated web server instances (not shown in <figref idref="DRAWINGS">FIG. <b>2</b></figref>).

0027To facilitate higher availability of the client instance <b>42</b>, the application server instances <b>24</b>A-<b>24</b>D and database server instances <b>44</b>A and <b>44</b>B are allocated to two different data centers <b>22</b>A and <b>22</b>B, where one of the data centers <b>22</b> acts as a backup data center. In reference to <figref idref="DRAWINGS">FIG. <b>2</b></figref>, data center <b>22</b>A acts as a primary data center <b>22</b>A that includes a primary pair of application server instances <b>24</b>A and <b>24</b>B and the primary database server instance <b>44</b>A for the client instance <b>42</b>, and data center <b>22</b>B acts as a secondary data center <b>22</b>B to back up the primary data center <b>22</b>A for the client instance <b>42</b>. To back up the primary data center <b>22</b>A for the client instance <b>42</b>, the secondary data center <b>22</b> includes a secondary pair of application server instances <b>24</b>C and <b>24</b>D and a secondary database server instance <b>44</b>B. The primary database server instance <b>44</b>A is able to replicate data to the secondary database server instance <b>44</b>B.

0028As shown in <figref idref="DRAWINGS">FIG. <b>2</b></figref>, the primary database server instance <b>44</b>A may replicate data to the secondary database server instance <b>44</b>B using, e.g., a Master-Master MySQL Binlog replication operation. The replication of data between data could be implemented by performing full backups weekly and daily incremental backups in both data centers <b>22</b>A and <b>22</b>B. Having both a primary data center <b>22</b>A and secondary data center <b>22</b>B allows data traffic that typically travels to the primary data center <b>22</b>A for the client instance <b>42</b> to be diverted to the second data center <b>22</b>B during a failure and/or maintenance scenario. Using <figref idref="DRAWINGS">FIG. <b>2</b></figref> as an example, if the application server instances <b>24</b>A and <b>24</b>B and/or primary data server instance <b>44</b>A fails and/or is under maintenance, data traffic for client instances <b>42</b> can be diverted to the secondary application server instances <b>24</b>C and the secondary database server instance <b>44</b>B for processing.

0029Although <figref idref="DRAWINGS">FIGS. <b>1</b> and <b>2</b></figref> illustrate specific embodiments of a cloud computing system <b>10</b> and a multi-instance cloud architecture <b>40</b>, respectively, the disclosure is not limited to the specific embodiments illustrated in <figref idref="DRAWINGS">FIGS. <b>1</b> and <b>2</b></figref>. For instance, although <figref idref="DRAWINGS">FIG. <b>1</b></figref> illustrates that the CMDB platform <b>20</b> is implemented using data centers, other embodiments of the of the CMDB platform <b>20</b> are not limited to data centers and can utilize other types of remote network infrastructures. Moreover, other embodiments of the present disclosure may combine one or more different server instance into a single server instance. Using <figref idref="DRAWINGS">FIG. <b>2</b></figref> as an example, the application server instances <b>24</b>A-D and database server instances <b>44</b>A and <b>44</b>B may be combined into a single server instance. The use and discussion of <figref idref="DRAWINGS">FIGS. <b>1</b> and <b>2</b></figref> are only examples to facilitate ease of description and explanation and are not intended to limit the disclosure to the specific examples illustrated therein.

0030As mentioned, present embodiments are directed to an embodiment of the CMDB platform <b>20</b> having functionality that enables the client instance <b>42</b> to determine which CIs are related to a particular CI. Using this functionality, the client instance <b>42</b> is able to identify issues (e.g., alerts, INTs, CHGs, and PRBs) associated with the particular CI and related CIs, as well as determine frequency data for these issues. Additionally, client instance <b>42</b> includes a graphical user interface (GUI) that is designed to present frequency data for issues associated with the particular CI and associated with related CIs. As discussed below, the GUI may include a plurality of widgets, wherein each widget is configured to present frequency data an issue (e.g., alerts, INTs, CHGs, PRBs) associated with particular CI, and to present frequency data for issues associated with related CIs, enabling the user to effectively explore root causes and/or solutions associated with the particular alert and particular CI.

0031With the foregoing in mind, <figref idref="DRAWINGS">FIG. <b>3</b></figref> illustrates an alert insight system <b>60</b>, in accordance with embodiments of the present technique. More specifically, <figref idref="DRAWINGS">FIG. <b>3</b></figref> is a block diagram <b>62</b> illustrating an embodiment the client instance <b>42</b> that may be used to support the alert insight system <b>60</b>, according to one or more disclosed embodiments. Block diagram <b>62</b> illustrates an example of a portion of a service provider cloud infrastructure, including the CMDB platform <b>20</b> discussed above. The CMDB platform <b>20</b> is connected to a client device <b>14</b>D via the network <b>18</b> to provide a user interface to network applications executing within the client instance <b>42</b> (e.g., via a web browser of the client device <b>14</b>D). Client instance <b>42</b> includes cloud resources and server instances similar to those explained with respect to <figref idref="DRAWINGS">FIG. <b>2</b></figref>, and is illustrated here to show support for an alert insight capability within the client instance <b>42</b>. Cloud provider infrastructures are generally configured to support a plurality of end-user devices, such as client device <b>14</b>D, concurrently, wherein each end-user device is in communication with the single client instance <b>42</b>. Also, cloud provider infrastructures may be configured to support any number of client instances, such as client instance <b>42</b>, concurrently, with each of the instances in communication with one or more end-user devices. As mentioned above, an end-user may also interface with client instance <b>42</b> using an application that is executed within a web browser.

0032For the embodiment of the alert insight system <b>60</b> illustrated in <figref idref="DRAWINGS">FIG. <b>3</b></figref>, the client instance <b>42</b> includes (e.g., hosts, stores) at least one CI table <b>64</b> that generally includes any suitable number of fields storing information related to CIs associated with the client instance <b>42</b>. The client instance <b>42</b> also includes at least one alert table <b>66</b>, INT table <b>68</b>, CHG table <b>70</b>, and PRB table <b>72</b>, which respectively store alerts, INTs, CHGs, and PRBs associated with CIs of the client instance <b>42</b> of the CMDB platform <b>20</b>. As such, for the illustrated embodiment, each of the alert table <b>66</b>, the INT table <b>68</b>, the CHG table <b>70</b>, and the PRB table <b>72</b> includes at least one field that refers to the CI table <b>64</b> (e.g., a foreign key value that points to the primary key of the CI table <b>64</b>). For example, in certain embodiments, a CI field of the alert table <b>66</b>, INT table <b>68</b>, CHG table <b>70</b>, and/or PRB table <b>72</b> may store a value (e.g., a JavaScript Object Notation (JSON) string) that uniquely identifies a particular CI associated with the client instance <b>42</b> from the CI table <b>64</b>. Additionally, other relationships may exist between tables of the client instance <b>42</b>. For example, in certain embodiments, one or more of the INT table <b>68</b>, the CHG table <b>70</b>, and the PRB <b>72</b> may include at least one field that refers to the alert table <b>66</b> (e.g., a foreign key value that points to the primary key of the alert table <b>66</b>) to store a relationship between alerts and INTs/CHGs/PRBs of the client instance <b>42</b>.

0033Additionally, the illustrated client instance <b>42</b> includes an insight engine <b>74</b>, which is an application that includes instructions that are executed by at least one suitable processor of the computer system to enable the client instance <b>42</b> to generate (e.g., determine, identify, select) suitable data regarding issues (e.g., alerts, INTs, CHGs, and PRBs) associated with CIs of the client instance <b>42</b> in response to client requests. That is, the insight engine <b>74</b> is configured to access or query the aforementioned CI table <b>64</b>, the alert table <b>66</b>, the INT table <b>68</b>, the CHG table <b>70</b>, and the PRB table <b>72</b> to assemble data to be presented to the client device <b>14</b>D in response to a client request <b>76</b>.

0034In particular, for the embodiment illustrated in <figref idref="DRAWINGS">FIG. <b>3</b></figref>, the client device <b>14</b>D provides the request <b>76</b> to the client instance <b>42</b>, via the network <b>18</b>, to explore or gain insight with respect to a particular alert and a particular CI. In response to receiving this request <b>76</b>, the insight engine <b>74</b> of the client instance <b>42</b> determines which CIs are related to the particular CI, as discussed below. The insight engine <b>74</b> also determines frequency data (e.g., total counts within a predefined time window) for issues associated with the particular CI, as well as frequency data for issues of the related CIs. Finally, the client instance <b>42</b> provides a response <b>78</b>, via the network <b>18</b>, to the client device <b>14</b>D that includes frequency data for issues (e.g., for alerts, INTs, CHGs, and PRBs) associated with the particular CI, as well as frequency data for issues associated with CIs related to the particular CI. Additionally, in certain embodiments, the response <b>78</b> includes details (e.g., an identifier, timestamp, description, severity, priority, state, source, etc.) pertaining to the issues associated with the particular CI and related CIs to be presented to the user along with the aforementioned frequency data.

0035<figref idref="DRAWINGS">FIG. <b>4</b></figref> is a flow diagram illustrating an embodiment of a process <b>80</b> whereby a client instance <b>42</b> (e.g., the insight engine <b>74</b> of the client instance <b>42</b>) handles the request <b>76</b> to explore the particular alert for the particular CI, in accordance with the present technique. The process <b>80</b> may be in the form of an application that includes instructions that are executed by at least one suitable processor of the computer system as part of the client instance <b>42</b> (e.g., as part of the insight engine <b>74</b> of <figref idref="DRAWINGS">FIG. <b>3</b></figref>). The illustrated process <b>80</b> is merely provided as an example, and in other embodiments, certain illustrated steps of the process <b>80</b> may be performed in other orders, skipped, or repeated, in accordance with the present disclosure.

0036For the illustrated embodiment, the process <b>80</b> begins with the client instance <b>42</b> receiving (block <b>82</b>) the request <b>76</b> from the client device <b>14</b>D indicating a particular alert and a particular CI. For example, the request <b>76</b> from the client device <b>14</b>D may include a value (e.g., a JSON string representing a CI identifier) that uniquely identifies the particular CI stored within the CI table <b>64</b> of the client instance <b>42</b>. Additionally, the request <b>76</b> may include a value (e.g., a JSON string representing an alert identifier) that uniquely identifies the particular alert within the alert table <b>66</b> of the client instance <b>42</b>. The client instance <b>42</b> then identifies (block <b>84</b>) related CIs based on the particular CI indicated in the request received in block <b>82</b>. An example of a process by which the client instance <b>42</b> identifies related CIs is discussed in greater detail with respect to <figref idref="DRAWINGS">FIG. <b>5</b></figref>.

0037Continuing through the illustrated embodiment of the process <b>80</b>, once the client instance <b>42</b> has identified CIs related to the particular CI, then the client instance <b>42</b> identifies or selects (block <b>86</b>) issues (e.g., alerts, INTs, CHGs, and PRBs) associated with the particular CI, as well as issues associated with the related CIs. It may be noted that, in certain embodiments, certain issues (e.g., INTs, CHGs, and/or PRBs) may further be limited to those that are associated with both the related CIs and the particular alert. For example, in certain embodiments, the client instance <b>42</b> specifically identifies or selects INTs that are associated with the related CIs and the particular alert received in block <b>82</b>.

0038Continuing through the illustrated embodiment of the process <b>80</b>, the client instance <b>42</b> determines (block <b>88</b>) frequency data for the issues associated with the particular CI and frequency data for the issues associated with the related CIs. In certain embodiments, the client instance <b>42</b> may first query each of the alert table <b>66</b>, the INT table <b>68</b>, the CHG table <b>70</b>, and the PRB table <b>72</b> to identify the issues associated with the particular CI and with the related CIs over a specified period of time (e.g., days, weeks, months), and then may separately count (e.g., sum, total) the issues from the results of the query to determine the frequency data for the particular CI and for the related CIs. In other embodiments, the client instance <b>42</b> may instead generate a query that both selects and separately sums the appropriate issues associated with the particular CI and with the related CIs from the alert table <b>66</b>, the INT table <b>68</b>, the CHG table <b>70</b>, and the PRB table <b>72</b> to generate the desired frequency data of block <b>88</b>.

0039Continuing through the embodiment illustrated in <figref idref="DRAWINGS">FIG. <b>4</b></figref>, the process <b>80</b> concludes with the client instance <b>42</b> sending (block <b>90</b>) the response <b>78</b> to the client device <b>14</b>D. As mentioned, the response <b>78</b> includes the frequency data for the issues associated with the particular CI, as well as the frequency data for the issues associated with the related CIs. More specifically, the frequency data for the alerts, INTs, CHGs, and PRBs associated with the particular CI and the frequency data for the alerts, INTs, CHGs, and PRBs associated with the related CIs are provided to the client device <b>14</b>D to be concurrently presented on a display of the client device <b>14</b>D. Additionally, as noted, in certain embodiments, the response <b>78</b> may include additional details (e.g., an identifier, timestamp, description, severity, priority, state, source, etc.) for each of the issues associated with the particular CI and/or the related CIs to be presented on the display of the client device <b>14</b>D concurrently with the frequency data.

0040<figref idref="DRAWINGS">FIG. <b>5</b></figref> is a flow diagram illustrating an embodiment of a process <b>100</b> whereby the client instance <b>42</b> (e.g., the insight engine <b>74</b> of the client instance <b>42</b> of <figref idref="DRAWINGS">FIG. <b>3</b></figref>) determines CIs that are related to a particular CI, in accordance with the present technique. The process <b>100</b> may be in the form of an application that includes instructions executed by at least one suitable processor of the computer system as part of the client instance <b>42</b> (e.g., as part of the insight engine <b>74</b>). The illustrated process <b>100</b> is merely provided as an example, and in other embodiments, certain illustrated steps of the process <b>100</b> may be performed in other orders, skipped, or repeated, in accordance with the present disclosure. The process <b>100</b> is described below with reference to Tables 1, 2, and 3.

0041For the embodiment illustrated in <figref idref="DRAWINGS">FIG. <b>5</b></figref>, the process <b>100</b> begins with the client instance <b>42</b> identifying and scoring (block <b>102</b>) a first group of CIs based on a topological relationship with the particular CI. As used herein, a “topological relationship” describes to how two CIs associated with a client instance of a CMDB platform operate with respect to one another to perform their intended enterprise functions. For example, a topological relationship may include a first CI “hosting” a second CI, wherein the reciprocal topological relationship includes the second CI being “contained by” the first CI. In addition to “hosting” and “contained by” topological relationships, a first CI may be related to a second CI within an application flow, such that the first CI is “dependent on” the second CI with respect to a particular service, or vice versa. It may be appreciated that the topological relationship data may be defined in and gleaned from metadata relationships and service mappings of the client instance <b>42</b>.

0042Accordingly, in block <b>102</b>, the client instance <b>42</b> determines a respective topological relationship score for each CI of the first group of CIs based on the topological relationship between the CI and the particular CI. For example, in an embodiment, the client instance <b>42</b> first determines whether any CIs are “hosting” or “contained by” the particular CI, whether any CIs are “dependent on” the particular CI, or whether the particular CI is “dependent on” any other CIs. Any CI falling into these categories comprise CIs having a first level topological relationship with the particular CI.

0043<tables id="TABLE-US-00001" num="00001"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217pt" align="center" /><thead><row><entry namest="1" nameend="1" rowsep="1">TABLE 1</entry></row></thead><tbody valign="top"><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Example of topological relationship scoring.</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="1" colwidth="84pt" align="center" /><colspec colname="2" colwidth="70pt" align="center" /><colspec colname="3" colwidth="63pt" align="center" /><tbody valign="top"><row><entry>Configuration Item (CI)</entry><entry>Topological</entry><entry>Topological</entry></row><row><entry>Identifier</entry><entry>Relationship Level</entry><entry>Relationship Score</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row><row><entry><CI 1></entry><entry>1</entry><entry>3</entry></row><row><entry><CI 2></entry><entry>1</entry><entry>3</entry></row><row><entry><CI 3></entry><entry>2</entry><entry>2</entry></row><row><entry><CI 4></entry><entry>3</entry><entry>1</entry></row><row><entry><CI 5></entry><entry>3</entry><entry>1</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

0044An example of the topological scoring of block <b>102</b> is indicated in Table 1. Each record in the Table 1 includes a respective value for a CI identifier field that uniquely identifies a CI in the CI table <b>64</b>, wherein “<CI 1>” represents a unique identifier (e.g., a JSON string representing a CI identifier) corresponding to a first CI, “<CI 2>” represents a unique identifier (e.g., a JSON string representing a CI identifier) corresponding to a second CI, and so forth. Each record in Table 1 also includes a topological relationship score field storing a positive integer value that is indicative of a strength of the topological relationship between the indicated CI and the particular CI. Each of the CIs having first level topological relationship with the particular CI receives a topological relationship score that is relatively higher than other CIs having distant or absent topological relationship with the particular CI. In the example indicated in Table 1, two CIs are identified as having a first level topological relationship with the particular CI and are assigned a relatively higher (or highest) topological relationship score (e.g., 3).

0045Once CIs having a first level topological relationship with the particular CI have been identified and scored, the topological scoring process may then be repeated using each CI in the first level. Any CI having a “hosting”, “contained by”, or “dependent on” relationship with a CI that, in turn, has a first level topological relationship with the particular CI, is identified as having a second level topological relationship with the particular CI. As such, each of these CIs are assigned a median topological relationship score, which is relatively lower topological relationship score compared to CIs having the first level topological relationship with the particular CI. For the example indicated in Table 1, a single CI is identified as having a second level topological relationship with the particular CI. As such, the CI is assigned a relatively lower topological relationship score (e.g., 2), compared to CIs having a first level topological relationship with the particular CI.

0046Once the second level of CIs is identified and scored, the topological scoring process may then be repeated for each CI having a second level topological relationship with the particular CI. Any CI having a “hosting”, “contained by”, or “dependent on” relationship with a CI that, in turn, has a second level topological relationship with the particular CI is identified as having a third level topological relationship with the particular CI. Each of the CIs having the third level topological relationship with the particular CI are assigned a relatively lower topological relationship score, compared to CIs having a first or second level topological relationship with the particular CI. For the example illustrated in Table 1, two CIs are identified as having a third level topological relationship with the particular CI, and are assigned a relatively lower topological relationship score (e.g., 1), compared to CIs having a first or second level topological relationship with the particular CI. It may be noted that, while in the present example, the topological analysis of block <b>102</b> proceeds through three levels of topological relationships, in other embodiments, the topological analysis of block <b>102</b> may include any suitable number of levels (e.g., 4, 5, 6, 7, 8, or more). Furthermore, in other embodiments, different CIs within the same topological level may receive a different topological relationship score based on the nature of the relationship (e.g., “hosting” and “contained by” relationships are awarded higher scores than “dependent on” relationships, or vice versa).

0047For the embodiment illustrated in <figref idref="DRAWINGS">FIG. <b>5</b></figref>, the process <b>100</b> continues with the client instance <b>42</b> identifying and scoring (block <b>104</b>) a second group of CIs having an alert group relationship with the particular alert. As used herein, an “alert group relationship” is a relationship between an alert group associated with the particular alert and an alert group associated with CIs of the CMDB. For example, within the client instance <b>42</b> associated with the CMDB platform <b>20</b>, an alert and/or CI can be associated an alert group, wherein each alert group has a type, such as “rule-based”, “automated”, “manual”, or “CMDB”. Rule-based alert group types are grouped according to compliance with alert correlation rules, while automated alert groups are automatically aggregated and include a virtual alert that is created and added as the primary alert of the group. Manual alert group types are manually grouped (e.g., based on instructions by an authorized user). CMDB alert group types are group based on CI relationship in the CMDB and are used to group alerts generated by CIs that lack historical data. Accordingly, when the particular alert is determined to belong to a particular alert group, the client instance <b>42</b> identifies all CIs that also belong to this alert group, regardless of the alert group type. Additionally, it may be appreciated that, in certain embodiments, alert group relationships can be used to enable temporal correlations between alerts and CIs.

0048As indicated in block <b>104</b>, the client instance <b>42</b> determines a respective alert group relationship score for each CI of the second group of CIs based on an alert group of the CI and an alert group of the particular alert. An example of the second group is indicated by Table 2. Accordingly, each record in Table 2 includes an alert group relationship score field storing a positive integer value that is indicative the strength of the alert group relationship between the indicated CI and the particular CI). For the example illustrated in Table 2, a four CIs are identified as being in the same alert group as the particular alert and are assigned the same alert group relationship score (e.g., 2).

0049<tables id="TABLE-US-00002" num="00002"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217pt" align="center" /><thead><row><entry namest="1" nameend="1" rowsep="1">TABLE 2</entry></row></thead><tbody valign="top"><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Example of alert group relationship scoring.</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="1" colwidth="28pt" align="left" /><colspec colname="2" colwidth="70pt" align="center" /><colspec colname="3" colwidth="119pt" align="center" /><tbody valign="top"><row><entry /><entry>Configuration Item (CI)</entry><entry>Alert Group Relationship</entry></row><row><entry /><entry>Identifier</entry><entry>Score</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row><row><entry /><entry><CI 1></entry><entry>2</entry></row><row><entry /><entry><CI 6></entry><entry>2</entry></row><row><entry /><entry><CI 7></entry><entry>2</entry></row><row><entry /><entry><CI 5></entry><entry>2</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

0050Continuing through the embodiment of the process <b>100</b> illustrated in <figref idref="DRAWINGS">FIG. <b>5</b></figref>, the client instance <b>42</b> subsequently combines or sums (block <b>106</b>) the respective first score and the respective second score for corresponding CIs of the first and second groups of CIs to generate a third group of CIs, each having a respective combined score. It may be appreciated that, in certain embodiments, the first group and the second group may include different CIs associated with the CMDB, and as such, there may not be a one-to-one correspondence between CIs in the first group and CIs in the second group. For the example indicated in Tables 1 and 2, while both tables reference CI 1 and CI 5, the first group indicated in Table 1 does not include an identifier for CI 6 or CI 7, while the second group indicated in Table 2 does not include an identifier for CI 2, CI 3, or CI 4.

0051An example of the third group of CIs is indicated in Table 3. Like Tables 1 and 2, each record in the Table 3 includes a respective value for a CI identifier field that uniquely identifies a CI in the CI table <b>64</b>. Table 3 includes a combined score field that stores a positive integer value that is indicative of the combined strength of the topological and the alert group relationship between the indicated CI and the particular CI. Since there is not a one-to-one correspondence between CIs in the first group and CIs in the second group for the illustrated example, certain CIs of Table 3 only have a topological relationship score, certain CIs only have an alert group relationship score, and certain CIs have both a topological and an alert group relationship score.

0052<tables id="TABLE-US-00003" num="00003"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217pt" align="center" /><thead><row><entry namest="1" nameend="1" rowsep="1">TABLE 3</entry></row></thead><tbody valign="top"><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Example of combined relationship scoring.</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="1" colwidth="84pt" align="center" /><colspec colname="2" colwidth="70pt" align="center" /><colspec colname="3" colwidth="63pt" align="center" /><tbody valign="top"><row><entry>Configuration Item (CI)</entry><entry>Combined Relationship</entry><entry>Related to</entry></row><row><entry>Identifier</entry><entry>Score</entry><entry>Particular CI</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row><row><entry><CI 1></entry><entry>3 + 2 = 5</entry><entry>TRUE</entry></row><row><entry><CI 2></entry><entry>3 + 0 = 3</entry><entry>TRUE</entry></row><row><entry><CI 3></entry><entry>2 + 0 = 2</entry><entry>FALSE</entry></row><row><entry><CI 4></entry><entry>1 + 0 = 1</entry><entry>FALSE</entry></row><row><entry><CI 5></entry><entry>1 + 2 = 3</entry><entry>TRUE</entry></row><row><entry><CI 6></entry><entry>0 + 2 = 2</entry><entry>FALSE</entry></row><row><entry><CI 7></entry><entry>0 + 2 = 2</entry><entry>FALSE</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

0053Continuing through the embodiment illustrated in <figref idref="DRAWINGS">FIG. <b>5</b></figref>, the client instance <b>42</b> then identifies or selects (block <b>108</b>) related CIs from the third group of CIs based on the respective combined score of each CI in the third group. For example, in certain embodiments, the client instance <b>42</b> determines that all CIs having a score greater than a threshold value are related to the particular CI. For the example indicated in Tables 1-3, the client instance <b>42</b> determines that all CIs of the third group having a total or combined score that is greater than or equal to a predetermined value (e.g., <b>3</b>) are related to the particular CI, while CIs that are not in the third group, or that are in the third group and have a score that is below the predetermined value, are determined to not be related to the particular CI. To better illustrate this selection, Table 3 includes a “related to particular CI” field that stores a Boolean value that is indicative of whether the indicated CI is related to the particular CI.

0054<figref idref="DRAWINGS">FIG. <b>6</b></figref> is a simulated screenshot of an embodiment of a graphical user interface (GUI) <b>110</b> that may operate in conjunction with the client instance <b>42</b> to provide information to the client device <b>14</b>D for presentation to a user. In certain embodiments, the GUI <b>110</b> may be generated by the client instance <b>42</b>, or generated by the client device <b>14</b>D based on information received from the client instance <b>42</b>, or a combination thereof. For example, the GUI <b>110</b> may be presented to the user of the client device <b>14</b>D in response to the user selecting a particular CI and a particular alert, and then selecting an option for “Alert Insight.” The illustrated GUI <b>110</b> includes an alert tab <b>112</b> (which is not in focus in <figref idref="DRAWINGS">FIG. <b>6</b></figref>) that is designed to provide information regarding a particular alert, and an insight tab <b>114</b> (which is in focus in <figref idref="DRAWINGS">FIG. <b>6</b></figref>) that presents the frequency data discussed above. It may be appreciated that the information presented on the insight tab <b>114</b> of the GUI <b>110</b> may be generated by the client instance <b>42</b> according to the process <b>80</b> of <figref idref="DRAWINGS">FIG. <b>4</b></figref>, discussed above.

0055More specifically, the embodiment of the GUI <b>110</b> illustrated in <figref idref="DRAWINGS">FIG. <b>6</b></figref> has a number of widgets, including: an alert widget <b>116</b>, an INT widget <b>118</b>, a CHG widget <b>120</b>, and a PRB widget <b>122</b>. Widgets <b>116</b>, <b>118</b>, <b>120</b>, and <b>122</b> are configured to present frequency data for alerts, INTs, CHGs, and PRBs, respectively, associated with either the particular CI or for related CIs. Accordingly, for the illustrated embodiment, the alert widget <b>116</b> includes a first field <b>124</b> (e.g., displaying a value of 5) that indicates a number of times that the particular CI has been associated with the particular alert during a predetermined time window (e.g., previous 7-14 days). The alert widget <b>116</b> also includes a second field <b>126</b> (e.g., displaying a value of 199) that indicates a number of times that related CIs have been associated with the particular alert within the same predetermined time window (e.g., previous 7-14 days). Additionally, for the illustrated embodiment, the first field <b>124</b> has been selected by the user (e.g., via a previous user input, such as mouse click), and as such an issue detail section <b>130</b> of the GUI <b>110</b> includes a table <b>132</b> that presents details (e.g., number, description, severity, priority, state, source, and so forth) regarding the 5 alerts (only 4 alerts illustrated) that correspond to both the particular alert and the particular CI. When the second field <b>126</b> of the alert widget <b>116</b> is selected, the table <b>132</b> in the issue detail section <b>130</b> of the GUI <b>110</b> is configured to present details regarding the 199 alerts that correspond to both the particular alert and the related CIs.

0056For the embodiment illustrated in <figref idref="DRAWINGS">FIG. <b>6</b></figref>, the INT widget <b>118</b> includes a first field <b>134</b> (e.g., displaying a value of 6) that indicates a number of times that an INT has been associated with the particular CI and the particular alert within a predetermined time window (e.g., previous 30-60 days). The INT widget <b>118</b> also includes a second field <b>136</b> (e.g., displaying a value of 51) that indicates a number of times that the related CIs have been associated with INTs that are also associated with the particular alert within the predetermined time window (e.g., previous 30-60 days). When the first field <b>134</b> of the INT widget <b>118</b> is selected, the table <b>132</b> in the issue detail section <b>130</b> of the GUI <b>110</b> is configured to present details regarding the 6 INTs that correspond to both the particular alert and the particular CI. When the second field <b>136</b> of the INT widget <b>118</b> is selected, the table <b>132</b> in the issue detail section <b>130</b> of the GUI <b>110</b> is configured to present details regarding the 51 INTs that correspond to both the particular alert and the related CIs.

0057The CHG widget <b>120</b> includes a first field <b>138</b> (e.g., displaying a value of 115) that indicates a number of CHGs associated with the particular CI within a predetermined time window (e.g., previous 30-60 days). The CHG widget <b>120</b> also includes a second field <b>140</b> (e.g., displaying a value of 213) that indicates a number of CHGs associated with the related CIs within the predetermined time window (e.g., previous 30-60 days). When the first field <b>138</b> of the CHG widget <b>120</b> is selected, the table <b>132</b> in the issue detail section <b>130</b> of the GUI <b>110</b> is configured to present details regarding the <b>115</b> CHGs that correspond to the particular CI. When the second field <b>140</b> of the CHG widget <b>120</b> is selected, the table <b>132</b> in the issue detail section <b>130</b> of the GUI <b>110</b> is configured to present details regarding the 213 CHGs that correspond to the related CIs.

0058The PRB widget <b>122</b> includes a first field <b>142</b> (e.g., displaying a value of 45) that indicates a number of PRBs associated with the particular CI within a predetermined time window (e.g., previous 30-60 days). The PRB widget <b>122</b> also includes a second field <b>144</b> (e.g., displaying a value of 213) that indicates a number of PRBs associated with the related CIs within the predetermined time window (e.g., previous 30-60 days). When the first field <b>142</b> of the PRB widget <b>122</b> is selected, the table <b>132</b> in the issue detail section <b>130</b> of the GUI <b>110</b> is configured to present details regarding the <b>45</b> PRBs that correspond to the particular CI. When the second field <b>144</b> of the PRB widget <b>122</b> is selected, the table <b>132</b> in the issue detail section <b>130</b> of the GUI <b>110</b> is configured to present details regarding the 213 PRBs that correspond to the related CIs.

0059The technical effects of the present disclosure include improving a user's ability to explore a root cause, as well as determine a solution for, a particular alert associated with a particular CI of a CMDB. Present embodiments include instructions that enable a client instance to determine CIs that are related to a particular CI, for example, based on a combination of a topological relationship and an alert group relationship between the particular CI and the other CIs associated with the client instance. Accordingly, when the particular CI experiences the particular alert, present embodiments enable the client instance to determine how frequently the CI has experienced potentially relevant issues, as well as how frequently related CI have experienced other potentially relevant issues, wherein the relevant issues may be helpful to the user in understanding and/or resolving the particular alert for the particular CI. Additionally, present embodiments include a GUI designed to concurrently present frequency data for issues associated with the particular CI and related CIs.

0060The specific embodiments described above have been shown by way of example, and it should be understood that these embodiments may be susceptible to various modifications and alternative forms. It should be further understood that the claims are not intended to be limited to the particular forms disclosed, but rather to cover all modifications, equivalents, and alternatives falling within the spirit and scope of this disclosure.

0061The techniques presented and claimed herein are referenced and applied to material objects and concrete examples of a practical nature that demonstrably improve the present technical field and, as such, are not abstract, intangible or purely theoretical. Further, if any claims appended to the end of this specification contain one or more elements designated as “means for [perform]ing [a function] . . . ” or “step for [perform]ing [a function] . . . ”, it is intended that such elements are to be interpreted under 35 U.S.C. 112(f). However, for any claims containing elements designated in any other manner, it is intended that such elements are not to be interpreted under 35 U.S.C. 112(f).