The Failure of OpManager Discovery, Hardware Changes and Applications Services
Unless support was mistaken, the scenario is this:
1. I add more disk space or memory to a server.
2. OpManager does not automatically detect the additional space or hardware.
3. I have to perform a re-discovery of the device for my monitors to reflect the new space.
So, to ensure my devices always have the proper values for the monitors, I need to (at least) create a daily schedule that rescans my devices.
The other behavior is this: When DISCOVERY is performed, OpManager automatically detects the OS and applies one of the built-in Device Templates Types for that OS. So if it detects Server 2012, it automatically applies the Windows 2012 R2 built-in template.
Within each OS template, a category is assigned with the default being the SERVER category. You can create other custom categories but you only get one category for each Built In OS Device Template.
When the discovery is done, the device TYPE is updated and the CATEGORY is updated.
So, I can practically NEVER use a custom category AND I can never use a Custom CATEGORY in a dashboard because those devices will get removed when a discovery occurs.
Unless there is a work-around, this type of thing should not happen having it break Categories and Dashboards.
The other problem with Discovery is that is ALSO auto-detects applications such as EXCHANGE and automatically assigns a bunch of junk monitors and services to it. There is no option to turn that off. The type of thing should ONLY be a part of the RULE ENGINE Selections. I can't delete all the junk monitors because they will just be rediscovered next schedule.
The following should be in place:
1. I shouldn't need to run a re-discovery job when hardware changes on a target device. The hardware (such as Disk, Memory, process) should update at the next polling interval.
2. Categories need to be separated from Device Templates otherwise Custom Categories are rendered pointless when you use regular re-discovery to address #1.
3. Application Services should only be option through the Rule Engine during discovery. It shouldn't force monitors to be created if it isn't a part of a template or rule engine.
Hopefully someone has an option for this and I don't have to wait for a software update to fix this.
1. I add more disk space or memory to a server.
2. OpManager does not automatically detect the additional space or hardware.
3. I have to perform a re-discovery of the device for my monitors to reflect the new space.
So, to ensure my devices always have the proper values for the monitors, I need to (at least) create a daily schedule that rescans my devices.
The other behavior is this: When DISCOVERY is performed, OpManager automatically detects the OS and applies one of the built-in Device Templates Types for that OS. So if it detects Server 2012, it automatically applies the Windows 2012 R2 built-in template.
Within each OS template, a category is assigned with the default being the SERVER category. You can create other custom categories but you only get one category for each Built In OS Device Template.
When the discovery is done, the device TYPE is updated and the CATEGORY is updated.
So, I can practically NEVER use a custom category AND I can never use a Custom CATEGORY in a dashboard because those devices will get removed when a discovery occurs.
Unless there is a work-around, this type of thing should not happen having it break Categories and Dashboards.
The other problem with Discovery is that is ALSO auto-detects applications such as EXCHANGE and automatically assigns a bunch of junk monitors and services to it. There is no option to turn that off. The type of thing should ONLY be a part of the RULE ENGINE Selections. I can't delete all the junk monitors because they will just be rediscovered next schedule.
The following should be in place:
1. I shouldn't need to run a re-discovery job when hardware changes on a target device. The hardware (such as Disk, Memory, process) should update at the next polling interval.
2. Categories need to be separated from Device Templates otherwise Custom Categories are rendered pointless when you use regular re-discovery to address #1.
3. Application Services should only be option through the Rule Engine during discovery. It shouldn't force monitors to be created if it isn't a part of a template or rule engine.
Hopefully someone has an option for this and I don't have to wait for a software update to fix this.