Cannot include autogenerated MID server CI's in a service map
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
We have activated the ServiceNow self help monitors for event managment, and it has autogenerated CI records in a new class 'cmdb_ci_appl_now_mid', howver we seem to be unable to include these in a service map.
We currently use tag based maps for our Discovery Service Instance, and the VMs and windows servers that host our MIDs appear fine in the service maps.
We added manually a runs on relationship from the autogenerated MID record to the host windows server, and in theory as a child class of cmdb_ci_appl the records in cmdb_ci_appl_now_mid should be incldued in the service map (and thus alert on them appear against Discovery in our service dashboard in SOW).
I've also tried making a manual depends on relationship from a draft service instance to the MID record and making that a calculated application service, but that also fails to include the MID record in the assocation table.
I cant find any documentation about this but I assume somewhere there is a system property blockign these CI's from being included in servicemaps.
Has anyone ele come across this?
Note that I know they appear in event management, but we want to see alerts on discovery mids seprate from the rest of the MIDs as they are managed by a different team.