This reviewer's identity has been verified by our review moderation team. They have asked not to show their name, job title, or picture.
While I greatly appreciate the cost savings aspect of ScaleOps, I find it as one of my go-to tools for general observability/monitoring of our system. It provides me with an easy way to see potential issues and misconfigurations within our system. We have unearthed many "skeletons" from ScaleOps. Finally, I would be remiss without calling out the support from the ScaleOps team. On multiple occasions, we had issues in the system and the ScaleOps team helped us analyze and remediate. The issue was NOT caused by ScaleOps tooling, but they were patient and dedicated enough to walk us through the real root cause. Review collected by and hosted on G2.com.
I wouldn't call it a dislike, but I would like to see continued feature enrichment on the node management and host side. I can see what ScaleOps wants to do, but I have a difficult time following Karpenter's decision making. I would like to see this in a fully integrated view to understand pod and node movement. Additionally, I have specialized nodes running their own host applications, outside the purview of Kubernetes and sometimes impacting resource management. It would be incredible to have ScaleOps be aware of those system resource usage and factor that into kubelet/system reserved capacity. Review collected by and hosted on G2.com.
The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user.
Validated through a business email account
This reviewer was offered a nominal incentive as thanks for completing this review.
Invitation from a seller or affiliate. This reviewer was offered a nominal incentive as thanks for completing this review.




