Foglight vs. Kubernetes

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

Along with all the best features and support by k8s, the automatic container scheduling to worker nodes and also self-healing containers which is what I like the most. On the other side, when I was installing the k8s cluster on CentOS 8, it was quite difficult for me, but never mind it is working as we expected and it is a one-time effort. Especially, in my case, there are more than 7 application containers required to run and communicate with each other, so for us, Kubernetes is an optimal solution.

Incentivized

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

Incentivized

• Complex cluster management can be done with simple commands with strong authentication and authorization schemes
• Exhaustive documentation and open community smoothens the learning process
• As a user a few concepts like pod, deployment and service are sufficient to go a long way

Incentivized

• 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

• Local development, Kubernetes does tend to be a bit complicated and unnecessary in environments where all development is done locally.
• The need for add-ons, Helm is almost required when running Kubernetes. This brings a whole new tool to manage and learn before a developer can really start to use Kubernetes effectively.
• Finicy configmap schemes. Kubernetes configmaps often have environment breaking hangups. The fail safes surrounding configmaps are sadly lacking.

Incentivized

The Kubernetes is going to be highly likely renewed as the technologies that will be placed on top of it are long term as of planning. There shouldn't be any last minute changes in the adoption and I do not anticipate sudden change of the core underlying technology. It is just that the slow process of technology adoption that makes it hard to switch to something else.

It is an eminently usable platform. However, its popularity is overshadowed by its complexity. To properly leverage the capabilities and possibilities of Kubernetes as a platform, you need to have excellent understanding of your use case, even better understanding of whether you even need Kubernetes, and if yes - be ready to invest in good engineering support for the platform itself

Incentivized

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

As I said earlier also - - K8s manage the workloads better as compared to OpenStack in terms of reliability, observability & reachability. - K8s is not limited to only a single networking or storage solution as compared to OpenStack. - Networking (which is a key concept) is much simpler in K8s as compared to OpenStack. - It is possible to upgrade your applications without downtime in K8s but in OpenStack, you either have to divert the traffic or face an outage because you have to delete the whole stack & then recreate it.

Incentivized

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

Incentivized

• Because of microservices, Kubernetes makes it easy to find the cost of each application easily.
• Like every new technology, initially, it took more resources to educate ourselves but over a period of time, I believe it's going to be worth it.

Incentivized