Tag Archives: monitoring

Prometheus: Alertmanager Web UI alerts Silence
0 (0)

26 January 2021

Active alerts sending frequency via Alertmanager is configured via the repeat_interval in the /etc/alertmanager/config.yml file. We have this interval set to 15 minutes, and as result, we have notifications about alerts in our Slack each fifteen minutes. Still, some alerts are such a “known issues”, when we already started the investigation or fixing it, but… Read More: Prometheus: Alertmanager Web UI alerts Silence0 (0) »

Loading

Kubernetes: a cluster’s monitoring with the Prometheus Operator
0 (0)

13 August 2020

Continuing with the Kubernetes: monitoring with Prometheus – exporters, a Service Discovery, and its roles, where we configured Prometheus manually to see how it’s working – now, let’s try to use Prometheus Operator installed via Helm chart. So, the task is spin up a Prometheus server and all necessary exporter in an AWS Elastic Kubernetes… Read More: Kubernetes: a cluster’s monitoring with the Prometheus Operator0 (0) »

Loading

Kubernetes: HorizontalPodAutoscaler – an overview with examples
0 (0)

12 August 2020

Kubernetes HorizontalPodAutoscaler automatically scales Kubernetes Pods under ReplicationController, Deployment, or ReplicaSet controllers basing on its CPU, memory, or other metrics. It was shortly discussed in the Kubernetes: running metrics-server in AWS EKS for a Kubernetes Pod AutoScaler post, now let’s go deeper to check all options available for scaling. For HPA you can use three… Read More: Kubernetes: HorizontalPodAutoscaler – an overview with examples0 (0) »

Loading

Kubernetes: monitoring with Prometheus – exporters, a Service Discovery, and its roles
0 (0)

26 April 2020

The next task with our Kubernetes cluster is to set up its monitoring with Prometheus. This task is complicated by the fact, that there is the whole bunch of resources needs to be monitored: from the infrastructure side – ЕС2 WokerNodes instances, their CPU, memory, network, disks, etc key services of Kubernetes itself – its… Read More: Kubernetes: monitoring with Prometheus – exporters, a Service Discovery, and… »

Loading

Kubernetes: running metrics-server in AWS EKS for a Kubernetes Pod AutoScaler
0 (0)

15 February 2020

Assuming, we already have an AWS EKS cluster with worker nodes. In this post – we will connect to a newly created cluster, will create a test deployment with an HPA – Kubernetes Horizontal Pod AutoScaler and will try to get information about resources usage using kubectl top. Kubernetes cluster Create a test cluster using… Read More: Kubernetes: running metrics-server in AWS EKS for a Kubernetes Pod… »

Loading

Grafana: Loki – the LogQL’s Prometheus-like counters, aggregation functions and dnsmasq’s requests graphs
0 (0)

17 November 2019

The last time I configured Loki for logs collecting and monitoring was in February 2019 – almost a year ago, see the Grafana Labs: Loki – logs collecting and monitoring system post, when Loki was in its Beta state. Now we faced with outgoing traffic issues in our Production environments and can’t find who guilty for… Read More: Grafana: Loki – the LogQL’s Prometheus-like counters, aggregation functions and… »

Loading

Debian: logrotate won’t rotate logs with an “unknown group ‘syslog'” error
0 (0)

9 October 2019

We have an AWS EC2 with Debian and logrotate. One day its root partition was exhausted and when I started investigating it – found, that we have a bunch of files like /var/log/syslog.N.gz. At the same time by default logrotate creates a config file to rotate syslog log files: [simterm] root@monitoring-dev:~# cat /etc/logrotate.d/syslog # Ansible… Read More: Debian: logrotate won’t rotate logs with an “unknown group ‘syslog'”… »

Loading

Sentry: running self-hosted errors tracking system on an AWS EC2
0 (0)

18 May 2019

Previously we used cloud-based Sentry version but then reached emails limit and our backend-team left without those notifications which are critical for their work. A self-hosted version was planned a long time ago so now we have a chance to spin it up. The post below describes how to start self-hosted Sentry on an AWS… Read More: Sentry: running self-hosted errors tracking system on an AWS EC20… »

Loading

Prometheus: Alertmanager’s alerts receivers and routing based on severity level and tags
0 (0)

26 March 2019

We have three working environments – Dev, Stage, Production. Also, there are a bunch of alerts with different severities – info, warning и critical. For example: … – name: SSLexpiry.rules rules: – alert: SSLCertExpiring30days expr: probe_ssl_earliest_cert_expiry{job=”blackbox”} – time() < 86400 * 30 for: 10m labels: severity: info annotations: summary: “SSL certificate warning” description: “SSL certificate… Read More: Prometheus: Alertmanager’s alerts receivers and routing based on severity level… »

Loading