HPE OneView vs. Splunk Infrastructure Monitoring

HPE Oneview has come along way. When they first put it out it was next to useless. Over the years and versions, they listened to feedback and have made OneView into a truly enterprise-level robust management product. It is now a far better product than the old C7000 Blade OAs, and HP SIM. It makes management of hardware easy and makes much of the maintenance easier and safer than before. For the storage side it does a great job and is intuitive to use, but the very versatility of how you can do things can lead to issues if multiple engineers do things differently.

Incentivized

Splunk Infrastructure Monitoring is well suited for any complicated environment where you have apps and servers across multiple clouds and platforms and products. If you have a data centre where all your apps and servers are in one single network, you could probably get away with older solutions. But for any modern, complex, hybrid-cloud microservices environment, Splunk Infrastructure Monitoring is a must-have.

Incentivized

• Managing the overall Blade profiles and the ability to have access to all equipment from one central repository.

Incentivized

• SignalFX handles historical metric aggregation exceptionally well, providing a multifaceted approach to event detection based on anomalies.
• SignalFX's cost is incredibly flexible with their pricing model of DPM (data-point per minute) vs the traditional "per host" model that most monitoring SaaS use.
• SignalFX support is responsive and knowledgeable, very eager to help solve your immediate problems.
• SignalFX integrations is vast and constantly growing, making adoption easy even when multiple different open-source technologies are used in your stack.

Incentivized

• Managing the 3Pard Oneview will allow you to do things like reuse LUN IDs and setup multiple export groups with the same volume. This can cause performance issues, or worse. They could do a better job of protecting you from yourself...
• Complicated initial configuration

Incentivized

• Better integration with our clients (native mobile clients SDKs will be great).
• A way to easily tag filters and move them across metrics/formula.
• Alert system to easy false [alarm] and hard to configure.
• Be able to have group more dimensions (and have more values on each).

Incentivized

Good: Stable system with low error rate Easy to use for simple use cases Bad: UI is not very clear for complex usage Mobile view (when logged in from phone) is bad No library for .net

Incentivized

I find that learning the interface can take some time. We need a better show-and-tell on how the Teams pages, Dashboard Groups, Dashboards and charts delay. Advance SignalFlow is sometimes hard to build. Some better samples of advanced SignalFlow would be helpful. For example, Splunk SPL has a vast resource of examples.

Incentivized

Support and training when we implemented OneView were excellent. We haven't required any additional support since we put it in and configured it for our systems. The OneView systems have been stable through updates and HPE documentation is excellent.

Incentivized

If you are using modern HPE equipment there really are no alternatives.

Incentivized

They’re not for the same purpose but we’re using NewRelic and Honeycomb for monitoring purposes. NewRelic is used for HTTP client monitoring for system related throughput, error, database and external client monitoring. Honeycomb is used to monitor actual HTTP request/response values. Splunk [Infrastructure Monitoring] is used for real-time application related throughout and error monitoring.

Incentivized

• No impact one way or the other for us.

Incentivized

• Reduced downtime.
• Caused us to get a lot of spam when we redeployed apps and old instances stopped sending metrics. Muting alerts solves this, but people often forget to do it or do it incorrectly.
• Helped us find historical info about instances/apps.

Incentivized