# US 2017/0286189 A1 · Graph-enhanced event management > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2017/0286189 A1 - Document ID: US20170286189A1 - Status: Published application - Kind: A1 - Application number: 15/084,872 - Filed: 2016-03-30 - Published: 2017-10-05 - Earliest claimed: 2016-03-30 - Assignees: CA, Inc. - Applicants: CA, Inc. - Inventors: Serge Mankovskii; Victor Muntés-Mulero; Marc Solé Simó - Web page: https://patentgrep.com/patent/US20170286189A1 ## CPC - G06F 9/542: {Event management; Broadcasting; Multicasting; Notifications} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A first event notification is received. The first event notification is associated with a first event. Criteria is determined based, at least in part, on the first event notification. A first component is identified based, at least in part, on the criteria a component graph. An operational status associated with the first component is determined. It is determined not to generate a second event notification based, at least in part, on the operational status. ## Claims ### Claim 1 A method comprising: receiving a first event notification, wherein the first event notification is associated with a first event at a first component; determining criteria based, at least in part, on the first event notification; identifying a second component based, at least in part, on the criteria and a component graph indicating a relationship between the first component and the second component; determining an operational status associated with the first second component; and determining not to generate a second event notification for the first component based, at least in part, on the operational status associated with the second component. ### Claim 2 (depends on 1) The method of claim 1, wherein determining the criteria comprises: determining a relationship type for the relationship between the first and the second components. ### Claim 3 (depends on 2) The method of claim 2, wherein the relationship type is determined based, at least in part, on an event characteristic associated with the first event. ### Claim 4 (depends on 2) The method of claim 2, wherein identifying the second component comprises: determining a path in the component graph based, at least in part, on the relationship type and the first component. ### Claim 5 (depends on 4) The method of claim 4, wherein determining the path in the component graph comprises: identifying a first node of the component graph, wherein the first node is associated with the first component; and identifying an edge associated with the first node, wherein the edge is associated with the relationship type. ### Claim 6 (depends on 4) The method of claim 4 further comprising: identifying a third component; wherein determining the path in the component graph comprises identifying a path between a first node corresponding to the first component and a second node corresponding to the third component, wherein the path between the first node and the second node comprises edges associated with the relationship type. ### Claim 7 (depends on 4) The method of claim 4, wherein identifying the second component further comprises: identifying a node along the path, wherein the node is associated with the second component. ### Claim 8 (depends on 1) The method of claim 1, wherein determining not to generate the second event notification comprises determining that there is an association between the first event and the operational status. ### Claim 9 (depends on 1) The method of claim 1, wherein determining not to generate the second event notification comprises determining that the operation status indicates that the second component is not operational. ### Claim 10 One or more machine readable storage media having program code stored therein, the program code comprising program code to: receive a first event notification, wherein the first event notification is associated with a first event at a first component; determine criteria based, at least in part, on the first event notification; identify a second component based, at least in part, on the criteria and a component graph, wherein the component graph indicates a relationship between the first component and the second component; determine an operational status associated with the second component; and determine not to generate a second event notification for the first component based, at least in part, on the operational status. ### Claim 11 (depends on 10) The one or more machine readable storage media of claim 10, wherein the program code to determine the criteria comprises program code to: identify a first node of the component graph that corresponds to the first component; identify a second node of the component graph that corresponds to a third component; and determine a relationship type for the first component and the third component based, at least in part, on the first event notification. ### Claim 12 (depends on 11) The one or more machine readable storage media of claim 11, wherein the program code to identify the second component comprises program code to: identify a path in the component graph between the first node and the second node, wherein the path comprises edges associated with the relationship type; and determine that the path comprises a third node corresponding to the second component. ### Claim 13 (depends on 11) The one or more machine readable storage media of claim 11, wherein the first event notification indicates that the second component is not accessible, wherein the second component is a network device that communicatively couples the first component and the third component. ### Claim 14 (depends on 13) The one or more machine readable storage media of claim 13, wherein the program code to determine not to generate the second event notification for the first component comprises program code to determine that the operational status indicates that communications sent from the third component to the first component via the second component would not reach the first component. ### Claim 15 An apparatus comprising: a processor; and a machine readable medium having program code stored thereon, the program code comprising program code executable by the processor to cause the apparatus to, receive a first event notification, wherein the first event notification is associated with a first event at a first component; determine criteria based, at least in part, on the first event notification; identify a second component based, at least in part, on the criteria and a component graph indicating a relationship between the first component and the second component; determine an operational status associated with the first second component; and determine not to generate a second event notification for the first component based, at least in part, on the operational status associated with the second component. ### Claim 16 (depends on 15) The apparatus of claim 15, wherein the program code executable by the processor to cause the apparatus to determine the criteria comprises program code executable by the processor to cause the apparatus to: identify a first node of the component graph that corresponds to the first component; identify a second node of the component graph that corresponds to a third component; and determine a relationship type for the first component and the third component based, at least in part, on the first event notification. ### Claim 17 (depends on 16) The apparatus of claim 16, wherein the program code executable by the processor to cause the apparatus to identify the second component comprises program code executable by the processor to cause the apparatus to: identify a path in the component graph between the first node and the second node, wherein the path comprises edges associated with the relationship type; and determine that the path comprises a third node corresponding to the second component. ### Claim 18 (depends on 16) The apparatus of claim 16, wherein the first event notification indicates that the second component is not accessible, wherein the second component is a network device that communicatively couples the first component and the third component. ### Claim 19 (depends on 18) The apparatus of claim 18, wherein the program code executable by the processor to cause the apparatus to determine not to generate the second event notification for the first component comprises program code executable by the processor to cause the apparatus to determine that the operational status indicates that communications sent from the third component to the first component via the second component would not reach the first component. ### Claim 20 (depends on 15) The apparatus of claim 15, wherein the program code further comprises program code executable by the processor to cause the apparatus to: receive a third event notification, wherein the third event notification is associated with a second event; determine second criteria based, at least in part, on the third event notification; identify a third component based, at least in part, on the second criteria and the component graph; determine an operational status associated with the third component; determine to generate a fourth event notification based, at least in part, on the operational status; and in response to the determination to generate the fourth event notification, generate the fourth event notification.