Tag-based service maps are taking a bottom up approach
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
6 hours ago - last edited 6 hours ago
We are creating tag traversal rules for mainframe components brought through Ironstream. This is the relationships we have in the cmdb_rel_ci table. We have tags on Programs, Channel, MQ Queue, DB2 Database.
An architecture that should have looked like this below , now looks bottom up, because the Region, MQ Manager and DB2 subsystem have a Runs on::Runs relationship with LPAR. It is therefore bringing all untagged CI's as well which have a relationship with LPAR. How can this map be made top-down with the map starting from LPAR and consisting only of the Tagged CIs.
0 REPLIES 0