MongoDB is a popular NoSQL database that supports large as well as small size of datasets. Just like any other database standalone setup, MongoDB is straightforward but we have to make a replicated or shared cluster of MongoDB, and there we have certain complications. Especially if we are doing these kinds of setups in orchestration tools like Kubernetes.
There is a lot of complexity in setting up MongoDB on Kubernetes that people(including me) have faced for a long time which I would like to highlight:-
Standalone setup is pretty straightforward but for replicated and sharded clusters additional mongo configurations are required.
In the replicated scenario, separate configurations need to be managed for the leader and follower.
Monitoring and access management of MongoDB inside Kubernetes is a little tricky part to handle.
Let’s start with a scenario, whenever any application builds, we generally do have 3 environments on the basis of resources – dev for developers resources, test for testers resources, and prod for production resources. Likewise, we used to have a separate IT-Operational Team having strategies to maintain their environment resources. It was very time-consuming and many human resources were required.
We are in the microservices era where we follow the DevOps Methodology. The DevOps Team brings all the environment and strategies to maintain resources in one go. Resources are the ones who decide the behavior of your applications. We can apply the criteria to resources, so how can our application behave? To do this we can give the name to our resources, we can give the resources quota to the application, and can give resource ranges to the application.
Kubernetes has become the new norm for container orchestration. But with this, its management brings in profound challenges for enterprises and DevOps teams planning to implement Kubernetes architecture within their organization. Here are 3 tools to manage a Kubernetes cluster. Take a look!
Kubernetes usage appears to be a popular pattern being adopted by enterprises these days. As per the 2021 Cloud-Native Survey, Kubernetes, the dominant container orchestration program has reached its highest level ever, with 96% of organizations using or evaluating the technology.
Enterprises going cloud-native consider Kubernetes as one of the important elements contributing to the success of implementing a cloud-first strategy. Kubernetes is a system that helps with the deployment, scaling and management of containerized applications.
If you’re planning to shift your business architecture to Kubernetes, then I’m sure Kubernetes management is the first thing that would come to your mind. So, let’s take a look at some of the popular Kubernetes management tools, here in this blog.
As we know alerting is the most crucial part of any infrastructure, and it becomes even more challenging when our infrastructure grows since we cannot monitor everything every time. Every client wants to get notified by their own alerting system before their customer reaches out to them and informs “Hey this service is not working or I am not able to access XYZ service“.
Alerting helps to ensure that the system remains healthy, responsive, and secure. It’s an important part of any system that makes performance, availability, and efficiency high. An operator might need to be notified of the event that triggers the alert.
We can set up alerts in many ways, but in this blog, I will be focussing on setting up alerting through azure logic apps.
Azure provides multiple options to send an alert to the end user, maybe through email, Slack, Pagerduty, SMS, etc. In this blog, I will be explaining the way to send an alert through email, Slack, and Pagerduty.
Praeco is an open-source tool for alerting Elasticsearch. It can build the alert for elasticsearch in an interactive query builder. A preview of the result will be shown in charts. This tool has an easy installation & configuration process which we will learn further in this blog. We can receive alerts on commonly used channels like slack, email, and many more.
This will have two parts- first, we install & configure the Praeco; in the second part, we learn – how to create an alert?
Why do we use this over others?
In terms of open-source tools which are used for alerting in elasticsearch the most popular option is elastalert. In this creating an alert is a very hectic process because one has to write YAML which can be sometimes frustrating for those who don’t know the syntax.
Now we have to search for other options, which leads us to Praeco. This provides an interactive GUI to create the alert condition and hassle-free integration with alert channels.