Kubernetes vs. LogicMonitor

K8s should be avoided - If your application works well without being converted into microservices-based architecture & fits correctly in a VM, needs less scaling, have a fixed traffic pattern then it is better to keep away from Kubernetes. Otherwise, the operational challenges & technical expertise will add a lot to the OPEX. Also, if you're the one who thinks that containers consume fewer resources as compared to VMs then this is not true. As soon as you convert your application to a microservice-based architecture, a lot of components will add up, shooting your resource consumption even higher than VMs so, please beware. Kubernetes is a good choice - When the application needs quick scaling, is already in microservice-based architecture, has no fixed traffic pattern, most of the employees already have desired skills.

Incentivized

The example I will give will explain my rating for it. One employee left our company due to a personal issue, and at that time, our team was working on a highly secure project. He wanted to take revenge on our company, so he began hacking our systems from the outside. Since it appears that someone without authorization is attempting to access our systems, LogicMonitor simultaneously alerted our team to the problem. We stopped that threat with LogicMonitor.

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

• It shows us system issues right away so we can fix them fast.
• It finds new devices on its own, so we do not miss anything.
• It alerts us only when something really unusual happens.
• Its dashboards make it easy for everyone to see system health.
• It helps us see trends so we are ready for busy times.

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

• Segmentation at an instance level not just the resource when clients are sharing the same device but shouldn't see each other's relevant data
• ARM CPU support for collectors to allow for a lighter weight appliance deployment
• WMI collection with a Linux collector so a windows collector would not be needed or a virtual appliance template that can be used to deploy collectors

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.

This product has met virtually all of our needs. It was easy to implement and has been simple to support. Customization has been intuitive with many options available. They keep adding features and expanding available options. The future of LogicMonitor looks even better than it is today which is very promising. The management and support teams at LogicMonitor are always helpful

Incentivized

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

Set up is super easy. Just stand up a small Linux or Windows server to act as a collector. There are no agents to install on monitored devices and all you need is SNMP or WMI access. When creating dashboards, all you have to do is find the widget on the device you want to show up and choose the menu option to add it.

Incentivized

The sales team support we received was top notch. They worked hand in hand to make sure the product met all expectations. So far we have not really had to work with support that much; we have worked with setup team after purchase to deploy product fully. No issues so far and we are four weeks in.

Incentivized

Add good training

Incentivized

The training is good but room to improve

Incentivized

I did not truly dedicate myself to implementing LogicMonitor. However, I overheard the IT team members explain that "LogicMonitor is perfect for us as it has made most of the work automated, and implementation and training sessions were perfect for us." Thus, I can state that everything went smoothly with our implementation.

Incentivized

Most of the required features for any orchestration tool or framework, which is provided by Kubernetes. After understanding all modules and features of the K8S, it is the best fit for us as compared with others out there.

Incentivized

Basically, we did not have any idea about it and how to choose, but we asked one of our former bosses, as they were very experienced with it, so they helped us by clarifying a few things between New Relic and LogicMonitor, as they told us that if you are looking for an automated option, then there is no better option than LogicMonitor.

Incentivized

Pricing seems to be getting more and more aggressive, I worry that it's going to turn into ServiceNow or SAP and everything minor feature will be an extreme cost that prices out us and our customers

Incentivized

Haven't really used it but our initial onboarding PS was disappointing. Felt like we were being told what we needed to cover as opposed to what we wanted to cover. In addition, we were pushed into using the PS in tight time frames and we were not ready to do so.

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

• We Eliminated an on-prem monitoring tool which was in excess of 25 servers
• A decrease in time to response from our Network Operations Center resulted in a more consistent client experience
• Dynamic alert thresholds helped reduce alerting by about 10 to 15% as soon as we turned it on for volatile metrics like CPU and memory

Incentivized