In this story I will show you my way of maintaining helm charts that are used to bootstrap infrastructure. Most of the developers I know face the issue with versioning and keeping helm charts up to date. What is a typical way to deploy a helm chart? Clone the chart…

In the First part I described how errors in NestJS could be made more informative and unified. In this story, I will show you how to convert your errors not only to log lines by also to Prometheus metrics. If you haven’t read the first part of the story, I…

I would like to share my ideas on how error handling could be improved for your service. What would we like to achieve? Easily search and reference occurred errors Enrich and categorize service errors Expose our errors as metrics Find a link to the full source code at the end…

In this story, I will describe how to set up monitoring of external services using Prometheus Blackbox Exporter. The blackbox exporter allows blackbox probing of endpoints over HTTP, HTTPS, DNS, TCP and ICMP. Prerequisites: Existing k8s cluster helm installed (if not, see Installing Helm) Install Grafana / Prometheus I suggest using kube-prometheus-stack as it…

Did you know that you can create fancy tables using UTF-8 symbols? It might be useful, e.g. for drawing structured data in terminal output. Example for light borders: ┌──────┬──────┐ │ col1 │ col2 │ ├──────┼──────┤ │ val1 │ val2 │ └──────┴──────┘ And here is for heavy borders: ┏━━━━━━┳━━━━━━┓ ┃ col1 ┃ col2 ┃ ┣━━━━━━╋━━━━━━┫ ┃ val1 ┃ val2 ┃ ┗━━━━━━┻━━━━━━┛ Double-lined border: ╔══════╦══════╗ ║ col1 ║ col2 ║ ╠══════╬══════╣ ║ val1 ║ val2 ║ ╚══════╩══════╝

Let’s say you have a Terraform configuration only for default workspace and you would like to split it into dev/staging environments. In order to create a new workspace in Terraform you can simply execute: $ terraform workspace new dev Created and switched to workspace "dev"! You're now on a new…

And voila! Happy time & eyes saving!

PATCHing data in ElasticSearch with Logstash. Let’s imaging you are trying to aggregate certain data about entity in ElasticSearch (ES further). The naive way to do it is to use Elasticsearch output with update action. But suddenly you realize that entities got overridden after each requests resulting with null values…