How Monitors are to be configured
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2019 06:01 AM
Hi All, In our organization, we are NOT able to discover monitors using Discovery. Hence we need to upload information manually. However, the default Monitor product category does not have an associated CI class. It only has an Asset class = Hardware [alm_hardware]. But I also see there is a 'cmdb_ci_display_hardware' class available to be used in CMDB. Why is this for? Hence I am not sure should we map Monitor in only in Asset using OOTB Monitor product category or Create new monitor category and add CMDB class as well??
- Labels:
-
Enterprise Asset Management

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2019 06:15 AM
In short, in most organizations, monitors don't matter.
Discovery and Service Mapping find devices that are IP addressable. I haven't found a monitor yet that is discoverable, but my experience doesn't cover all use cases.
That being said, monitors generally aren't part of a service so dependencies don't matter. They don't trigger alerts, they can be off (or dead) without impacting a business service, and most of all, they aren't considered assets (they don't depreciate in value as the computer or server they are attached to would.) They are considered consumables - more like keyboards and mice.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2020 10:12 AM
I have the same requirement. Would like to know the approach if you have found a solution for the same.
Thank you