tie idrac monitoring to its host, not a separate device | Archive

mnagel · 2018-09-26T17:19:41Z

I have brought this up with our CSM previously, but I thought maybe it would help to note the issue here as well. Currently, iDRAC monitoring requires consumption of a second device slot in addition to the device itself. This is a non-starter for most people due to the cost factor (especially if they have hundreds of servers), so they just don't bother. There is really no reason the datasources could not be adjusted to use something like drac.ip, etc. to monitor as an element of the host. The only glitch would be the network interfaces, which I think would be fine to leave out. Technically, I understand why the DS authors went this way, but it is an unnecessary cost burden to customers. Thanks, Mark

MoreDiscussions

tie idrac monitoring to its host, not a separate device | Archive | LogicMonitor Community