Foglight vs. Percona Operator

It really depends on why my colleague is evaluating Foglight. If it is for Database monitoring and management, I highly recommend it. If it is for anything else, I would encourage them to look at others in this space.

Incentivized

Production ready, robust DB solution built for Kubernetes envs, we was able, for the first time, to ship production db workloads inside k8s. Be sure to check differences with "traditional" MySQL and other clustering solutions. Also be sure to match it with proper k8s storage solutions.

• VMWare Monitoring
• Custom use of scripts and dashboard
• Performance Analysis for Database
• Remote Monitoring for Linux and Windows.

Incentivized

• Easy and fast deployment.
• A reliable, fully automated, high-available db lifecycle management solution.
• Exaustive documentation.
• Production ready.

• Foglight allows detecting and diagnosing performance problems simplifying hybrid environments, it is a solution that has perfect features which work in a flexible and intuitive way, it allows database performance in a safe and fast way. It works perfectly with nothing else to add.

Incentivized

• Some differences compared to "traditional" MySQL solution.
• Had some hard times trying to use it combined with pre-existing techs like WordPress, Magento, etc.
• The specific k8s environment features can have an impact on it, like the storage solutions offered by the cloud vendor.

Easy and fast deployment. A reliable, fully automated, high-available db lifecycle management solution. It requires a bit of learning time for people new to operators ecosystem.

Well documented, there was no need to contact support.

Foglight was chosen years ago as a replacement for Groundwork. After 2.5 years of implementing Groundwork things were still not complete and the decision to go with a more formalized solution was made. Foglight installed easily and quickly nearly across the board and the full implementation for complex infrastructure was completed (with no Professional Services) by us in under 4 months. Nagios is a wonderful toolkit but you have to be ready to build what you need. It's flexibility and breadth are excellent features but with that comes the need to define things very tightly lest you embark on the project that never ends (see above about Groundwork). Dynatrace is an excellent APM tool and has advanced analytics but as a general infrastructure monitoring tool it is actually very expensive and to be honest does not have the same focus and full feature set that it does on it's APM (which to be fair is it's wheelhouse). vROPs (we also have) is a wonderful tool but focused (and rightly so) on satisfying the VMware engineers in the crowd and doesn't put itself out there too far to make things palatable for the non-engineering crowd.

Incentivized

For a long time we struggled finding a viable solution to migrate our existing db workloads inside Kubernetes. Before "operators era" proper db workloads required manual management, of course that easily raised administrative overhead. Then the future started to be brighter with the introduction of operators and the "official" Oracle's MySQL Operator, then Presslab's one, finally Percona's operator. Compared to other operators, the last one allowed us to ship production db workloads inside k8s.

• Positive - near instant alerts help combat potential problems quickly
• Positive - minimizes business interruption
• Positive - limits disruptions to productivity

Incentivized

• It allowed us to use k8s on our entire infrastructure.
• Decreased administrative overhead around our db services.
• As it is an open source technology, it cut down our db pricings.