In these posts, I talk about the steps I took in order to monitor some aspects of a microservice application deployed on Kubernetes cluster. I’m aggregating data about 1.the number and server-side response time for each endpoint. 2. The allocated resource to each microservice at each moment and 3. resource utilization (only CPU for now) of each microservice. This first part only focuses on storing and retrieving information about the incoming requests.
What I did is highly inspired by this.
Telegraf and InfluxDB
InfluxDB is a time-series database. As the website mentions, Telegraf is the open-source server agent to help…
I’ve been using and learning k8s for a couple of months now. For a project which involves a huge amount of resource monitoring and planning I needed to record the CPU and memory utilization of every pod. I will write about how I did that using InfluxDB, Telegraf and visualized it Grafana later. Before that I had this (silly) problem with monitoring resource usage in k8s which definitely was rooted in my lack of knowledge. Hopefully this could help other nubs like me.
The first part of the following article talks about metric server in Kubernetes and the second part…
Have you ever deployed a stack in Docker Swarm and wanted to run tcpdump to monitor packets that are passing between different network components? I have.
If you run the tcpdump command directly on the host you won’t monitor most of the packets that are moving between different services can containers. You need to somehow go inside the networks and runt it.
When you run a docker stack, you will have one ingress network and one overlay network. They each have their role. You can read about them here.
So how to run tcpdump in Docker Swarm and monitor the…
Vahid Mostofi
Computer Programmer with passion for new stuff in the tech world. Mostly focused on backend design and architecture.
