Kubernetes is an open-source container cluster manager.
N/A
OpsGenie
Score 8.5 out of 10
N/A
OpsGenie is an IT monitoring and incident response platform for development and operations teams, providing alerts and schedule management escalations. OpsGenie is now part of Atlassian since the late 2018 acquisition.
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.
Well suited for cases where you just need to alert relevant team members when alerts and incidents come in and make sure that nothing falls through the cracks. Generally OpsGenie just forwards the alerts it receives and allows you to schedule team members to be on-call. It's good for that simple use case and extra helpful if you have Jira or Atlassian Open DevOps since it has nice integrations with those platforms and you can easily monitor ticket progress. If you don't have those, it would be good to check and see if they integrate with whatever you use to track tickets or bugs. The dashboarding and analytics are relatively basic so if you're looking for extensive and highly customizable analytics, this might not be the right solution.
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.
OpsGenie New Jira design has made it difficult for those not familiar with that style.
OpsGenie could benefit from nested escalation flows for team schedules. Creating a product alert that uses and Tech Schedule as well as an Incident Manager Schedule that already exists would create less overhead and ease management.
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.
We also looked at PagerDuty but decided to go with OpsGenie as it had more features on the plan we needed compared to PagerDuty which would have required us to spend a lot more for what we felt were non-premium features. Everything felt like an add-on - automation for an additional $20 a user per month seemed like a lot on top of the base plan
