One of the main challenges when consolidating your IT landscape is to understand where your software is running. Often, identifying fragmented data centers and hosting shows great potential for cost savings. This tutorial shows how to get started.
Please make sure to read our documentation on how to Import & Export your Data as well, if you haven't done so already.
In this example, we look at database servers. It is good practice to use a Tech. Stack (see What is a Fact Sheet?) to group your software, as well as to use a Tag Group (see Use Tags for more powerful insights) to mark the recommendation whether to use the software or not, e.g. with a Candidate, Leading, Exception, Sunset model.
Next, we import the information on server and remote data center locations. Again, it's good practice to assign a Tech. Stack.
The IT Component Landscape Report gives you a great overview on the imported IT Components group by Technology Stack. As one example, we can use the created Tag Group to display the software recommendation. Learn more about reports here: Insights through Reports.
Also, the IT Component Location report provides a nice overview where your servers are located:
Now it's time to link the Applications. For a first view, it's sufficient to create a link to a software and to a server. Later, you can also consider to link software and server, e.g. via a requires relation.
Diagrams allow you to get a nice overview of the created relations. Start with the application, and use the show dependency, drill down and roll up options to display the relation.
Now you can put the pieces together. Use the Application Landscape to find out where a certain data center location affects your business.
Use the Application Sourcing Report to find out where Applications using certain Software versions are hosted.
Or just use the table view in the Inventory to make the dependencies transparent.
Updated about a month ago