2 Replies Latest reply: Mar 15, 2017 8:14 AM by dlevine4
Here is an answer from Anthony Foster
"So there are three ways I see to tackle this.
- They need to redefine why they are using reports. Reports are a point in time “everything is good” check list. You shouldn’t be using them for monitoring you should be using them to show auditors and suites that stuff is happening.
- They need PS to come and build valid dashboards for what they are concerned about. vROPS supports it but it doesn’t sound like they are using it. In other words, hide all the stuff that is working and only show stuff that’s out of range or broken (been broke, just broke, will break). If there is stuff that is out of range / broken that they don’t want to see because they are already aware of it, then there needs to be a conversation about why they ignore things the system is flagging as abnormal. Both vROPS and ViPR use intelligent algorithms to calculate ‘normal.’ (if anyone took stats in college think two standard deviations out and add some Bollinger Bands.)
- If the intelligence that vROPS and ViPR provide aren’t enough for what they are wanting to do and they need to scale up to something like SIOS. Or they need to pay someone to build a deep learning system for them similar to what I describe in my blog post about using deep learning to manage a data center. https://www.wondernerd.net/blog/deep-learing-in-virtual-data-center-management/ (I keep wanting to build it but haven’t had the time or the TB log files to train a system.)"