Please consider adding complex relationships in the CI explorer.
Using a hierarchy with levels only works for simple scenarios and doesn’t faithfully represent reality and can even obfuscate relationships between CI by adding a new representation of an existing CI instead of linking to the existing representation.
I’ve created a mockup of how a more complex configuration might look in the CI explorer. The mockup is far from complete and I’ve even omitted multiple CI on purpose to keep the illustration easier to follow.
Following the relationships from, for example, an application that isn’t working to the next CI, and then the next, and so on is an invaluable tool for troubleshooting. Having to select a new root node to continue exploring is clunky and makes back tracking much harder.
There are many other scenarios where it’s almost a must to be able to explore “indefinitely” through the CI.
