New Ideas
While configuring opmanager, and I'm still in that phase, I thought up some features that would be helpful that weren't included.
#1. Add ability for event log rules to exclude particular event IDs (or any other attribute for that matter)
#2. Event logs need a way to say "only if source was the servername", I couldn't find a way.
#3. Allow a script to get a folder name for folder monitors. IIS keeps track of its folder locations in the metabase, which can be queried, but this value can be different or event change. It would be nice if the folder monitor could keep track of new locations.
#4. Each monitor can have thresholds that you set, and it then has a severity. But it only has 1. We may want a critical severity at 90% CPU, and trouble at 75%, and attention at 50%, I can find no way to do this within your application.
#5. I honestly can't see how anybody would want to track each CPU individually, I modified your CPU.VBS to track the average between all CPUs, so its a single value, ya'll may want to give that as an option.
#6. Templates only support service/port monitors. What about URL/folder/windows service/etc, basically ALL kinds of monitors, this prevents needless and duplicate configuration of multiple devices with the same monitors required.
#7. The map view editor is, well, crap, on so many levels, making it nearly impossible to use.
#8. More granular user permissions. I may want users to only be able to enable/disable/acknowledge alerts, not modify monitors, and with just Read-Only/Full Control as options prevents that.
And not really an idea, and I know that twitter is popular, but just having it there looks extremely unprofessional, as no self-respecting company would ever want their alerts going out over twitter. Heck, for security reasons alone that is a serious flaw. Perhaps just obfuscate it a bit more, making it a notification rule only.
Thanks,
Eric Smith
#1. Add ability for event log rules to exclude particular event IDs (or any other attribute for that matter)
#2. Event logs need a way to say "only if source was the servername", I couldn't find a way.
#3. Allow a script to get a folder name for folder monitors. IIS keeps track of its folder locations in the metabase, which can be queried, but this value can be different or event change. It would be nice if the folder monitor could keep track of new locations.
#4. Each monitor can have thresholds that you set, and it then has a severity. But it only has 1. We may want a critical severity at 90% CPU, and trouble at 75%, and attention at 50%, I can find no way to do this within your application.
#5. I honestly can't see how anybody would want to track each CPU individually, I modified your CPU.VBS to track the average between all CPUs, so its a single value, ya'll may want to give that as an option.
#6. Templates only support service/port monitors. What about URL/folder/windows service/etc, basically ALL kinds of monitors, this prevents needless and duplicate configuration of multiple devices with the same monitors required.
#7. The map view editor is, well, crap, on so many levels, making it nearly impossible to use.
#8. More granular user permissions. I may want users to only be able to enable/disable/acknowledge alerts, not modify monitors, and with just Read-Only/Full Control as options prevents that.
And not really an idea, and I know that twitter is popular, but just having it there looks extremely unprofessional, as no self-respecting company would ever want their alerts going out over twitter. Heck, for security reasons alone that is a serious flaw. Perhaps just obfuscate it a bit more, making it a notification rule only.
Thanks,
Eric Smith