Use Tag Clouds to Visualize Components Related to an Event

• US 20100293270A1
• Filed: 03/26/2010
• Published: 11/18/2010
• Est. Priority Date: 05/18/2009
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Erdmenger, Joerg, Oldengott, Hans-Ulrich, Augenstein, Oliver, Prause, Thomas, Raitza, Martin
• Granted Patent: US 8,516,106 B2
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: G06F 11/324 Display of status information
• CPC Class Codes: G06F 11/3466 Performance evaluation by tracing or monitoring
• CPC Class Codes: G06F 11/3476 Data logging G06F11/14, G06F11/2205 take precedence
• CPC Class Codes: G06F 15/173 using an interconnection network, e.g. matrix, shuffle, pyramid, star, snowflake
• CPC Class Codes: G06F 2201/86 Event-based monitoring
• CPC Class Codes: G06F 2201/865 Monitoring of software
• CPC Class Codes: G06F 2201/875 Monitoring of systems including the internet

Abstract

A method, system, and computer program product for displaying components assigned to events produced by resources, includes: registering a new resource by generating a label to which is associated a system specific device identifier used by the new resource within a computing environment; storing in a mapping table the generated label identifying the registered new resource together with an associated system specific device identifier; and updating the mapping table by associating to the label any other system specific device identifier used by the new resource within the computing environment; receiving events produced by resources when being executed within the computing environment, each event being associated with a list of labels for the resources relevant for the generation of the event; and maintaining a tag cloud including different tags, the different tags including labels for the resources associated with the received events to be displayed as components.

Claims

1. A computer implemented method for displaying components assigned to events produced by resources, the resources being executed within a computing environment, the method comprising:

registering a new resource by generating a label to which is associated a system specific device identifier used by the new resource within the computing environment;

storing in a mapping table the generated label identifying the registered new resource together with the new resource'"'"'s associated system specific device identifier;

updating the mapping table by associating to the generated label any other system specific device identifier used by the new resource within the computing environment;

receiving events produced by resources when being executed within the computing environment, each event being associated with a list of labels for the resources relevant for the generation of that event; and

maintaining a tag cloud comprising different tags, the different tags comprising labels for the resources associated with the received events to be displayed as components.

2. The method according to claim 1, wherein each of the different tags are weighted according an occurrence of a respective resource within the received events.

3. The method according to claim 1, wherein the registering the new resource by generating the label to which is associated the system specific device identifier used by the new resource within the computing environment comprises:

determining if all resources depending on the new resource are already registered with an appropriate label; and

in response to determining that not all resources to which the new resource depends on is already registered;

generating a new label to which is associated a system specific device identifier used by the new resource; and

firing a reconciliation event with the new label and the associated system specific device identifier used by the new resource, the reconciliation event to be checked by a control instance.

4. The method according to claim 3, wherein in response to determining that the reconciliation event corresponds to the new resource that is not already registered:

storing the new label in the mapping table together with the associated system specific device identifier used by the new resource; and

updating the mapping table by associating with the new label any other system specific device identifiers used by the new resource within the computing environment.

5. The method according to claim 3, wherein in response to determining that the reconciliation event corresponds to the new resource already registered with a different label, using an alias table to associate the system specific device identifier used by the new resource with the different label.

6. The method according to claim 1, whereby resource classes are predefined and associated with a specific event-to-event names table.

7. The method according to claim 5, whereby when aliases for resources are required, predefined aliases for the new resource are taken from a configuration management database.

8. A computer program product for displaying components assigned to events produced by resources, the computer program product comprising:

a computer readable storage medium having computer readable program code embodied therewith, the computer readable program code comprising;

computer readable program code configured to;

register a new resource by generating a label to which is associated a system specific device identifier used by the resource within the computing environment;

store the generated label identifying the registered new resource in a mapping table together with the new resource'"'"'s associated system specific device identifier;

update the mapping table by associating to the generated label any other system specific device identifier used by the new resource within the computing environment;

receiving events produced by resources when being executed within a computing environment, each event being associated with a list of labels for the resources relevant for the generation of the event; and

maintain a tag cloud comprising different tags, the different tags comprising labels for the resources associated with the received events to be displayed as components.

9. The computer program product according to claim 8, wherein the computer readable program code is further configured to:

weigh each of the different tags according to an occurrence of a respective resource within the received events.

10. The computer program product according to claim 8, wherein the computer readable program code for registering the new resource by generating a label to which is associated the system specific device identifier used by the resource within the computing environment is further configured to:

determine if all resources depending on the new resource are already registered with an appropriate label, and in response to determining that not all resources to which the new resource depends on is already registered,

generate a new label to which is associated a system specific device identifier used by the new resource; and

fire a reconciliation event with the new label and the associated system specific device identifier used by the new resource, the reconciliation event to be checked by a control instance.

11. The computer program product according to claim 10, wherein the computer readable program code is further configured to:

store the new label in the mapping table together with the associated system specific device identifier used by the new resource, in response to determining that the reconciliation event corresponds to the new resource that is not already registered; and

update the mapping table by associating to the new label any other system specific device identifiers used by the new resource within the computing environment.

12. The computer program product according to claim 10, wherein the computer readable program code is further configured to:

use an alias table to associate the system specific device identifier used by the new resource to a different label, in response to determining that the reconciliation event corresponds to the new resource is already registered with the different label.

13. The computer program product according to claim 8, wherein the computer readable program code is further configured to:

allow predefined resource classes to be associated with a specific event-to-event names table.

14. The computer program product according to claim 12, wherein the computer readable program code is further configured to:

choose required aliases for resources from predefined aliases within a configuration management database.

15. A system, comprising:

a plurality of resources comprising a new resource; and

a monitoring computer for;

registering the new resource by generating a label to which is associated a system specific device identifier used by the new resource within the system;

storing in a mapping table the generated label identifying the registered new resource together with the new resource'"'"'s associated system specific device identifier;

updating the mapping table by associating to the generated label any other system specific device identifier used by the new resource within the system;

receiving events produced by the plurality of resources when being executed within the system, each event being associated with a list of labels for the resources relevant for the generation of that event; and

maintaining a tag cloud comprising different tags, the different tags comprising labels for the plurality of resources associated with the received events to be displayed as components.

16. The system according to claim 15, wherein each of the different tags are weighted according an occurrence of a respective resource within the received events.

17. The system according to claim 15, wherein the registering the new resource by generating the label to which is associated the system specific device identifier used by the new resource within the system comprises:

determining if all resources depending on the new resource are already registered with an appropriate label; and

in response to determining that not all resources to which the new resource depends on is already registered;

generating a new label to which is associated a system specific device identifier used by the new resource; and

firing a reconciliation event with the new label and the associated system specific device identifier used by the new resource, the reconciliation event to be checked by a control instance.

18. The system according to claim 17, wherein in response to determining that the reconciliation event corresponds to the new resource that is not already registered:

storing the new label in the mapping table together with the associated system specific device identifier used by the new resource; and

updating the mapping table by associating with the new label any other system specific device identifiers used by the new resource within the computing environment.

19. The system according to claim 17, wherein in response to determining that the reconciliation event corresponds to the new resource already registered with a different label, using an alias table to associate the system specific device identifier used by the new resource with the different label.

20. The system according to claim 15, whereby resource classes are predefined and associated with a specific event-to-event names table.

21. The system according to claim 19, whereby when aliases for resources are required, predefined aliases for the new resource are taken from a configuration management database.