Use of graph databases for replicating topology and enriching monitoring data streams in complex information technology systems

A computer program product to connect information technology (IT) tools to provide a unified view of an IT system, the computer program product being tangibly embodied on a non-transitory computer-readable medium and including executable code that, when executed, is configured to cause a computing device to:

• store topology from each of a plurality of source tools as a plurality of source subgraphs in a graph database using a source schema that mirrors a source topology model for each of the plurality of source tools;
• transform each of the plurality of source subgraphs in the graph database to a plurality of destination subgraphs using a destination schema and transformation rules that mirror a destination topology model for each of a plurality of destination tools;
• store the plurality of destination subgraphs in the graph database;
• deliver the topology to each of the plurality of destination tools by traversing the plurality of destination subgraphs in the graph database and invoking application programming interfaces (APIs) for each of the plurality of destination tools in the destination subgraphs in the graph database;
• and
• generate and output a graph visualization of the topology for each of the plurality of destination tools to provide the unified view of the IT system.

A system to connect information technology (IT) tools to provide a unified view of an IT system, the system comprising:

• at least one processor;
• and
• a non-transitory computer-readable medium comprising instructions that, when executed by the at least one processor, cause the system to:
• store topology from each of a plurality of source tools as a plurality of source subgraphs in a graph database using a source schema that mirrors a source topology model for each of the plurality of source tools;
• transform each of the plurality of source subgraphs in the graph database to a plurality of destination subgraphs using a destination schema and transformation rules that mirror a destination topology model for each of a plurality of destination tools;
• store the plurality of destination subgraphs in the graph database;
• deliver the topology to each of the plurality of destination tools by traversing the plurality of destination subgraphs in the graph database and invoking application programming interfaces (APIs) for each of the plurality of destination tools in the destination subgraphs in the graph database;
• and
• generate and output a graph visualization of the topology for each of the plurality of destination tools to provide the unified view of the IT system.