Tag Archives: monitoring

VictoriaMetrics: using vmalert and query() in alerts for different $value values
0 (0)

26 March 2026

Just a quick note, because I’ve needed to do something like this fairly often – and only today discovered how elegantly it’s done with vmalert. So, sometimes in an alert you want to display multiple $value entries, for example: – alert: OpenAI Budget Usage expr: | openai_budget_used_usd / openai_budget_total_usd * 100 > 80 … annotations:… Read More »

Loading

Glance: setting up a self-hosted home page for your browser
0 (0)

13 March 2026

There’s this cool thing called self-hosted home pages. I saw them somewhere on Reddit a while back, saved them to bookmarks, and now that I have all this self-hosted stuff with NAS (see FreeBSD: Home NAS, part 1), Grafana, and other useful things for work and daily life – I thought it would be nice… Read More »

Loading

ilert: an alternative to Opsgenie – first impressions, Alertmanager, Slack
5 (2)

24 February 2026

I think all Opsgenie users are aware that Atlassian is killing is shutting down the project. I’ve been using Opsgenie since 2018, got used to it, and overall it had everything I needed from an alerting system – a bit rough around the edges in places, but the necessary integrations worked and were easy enough… Read More »

Loading

VictoriaMetrics: Recording rules for AWS Load Balancer logs
0 (0)

6 December 2025

Continuing the topic of AWS Load Balancer logs: in the previous post, Golang: recording AWS Load Balancer logs to VictoriaLogs, we collected logs using our own logs collector in Golang. Now we need to get something useful out of these logs. Previously, when I had Loki on my project, we used its RecordingRules to create… Read More »

Loading

VictoriaMetrics: Churn Rate, High cardinality, metrics, and IndexDB
0 (0)

3 November 2025

One day I received one of the default VictoriaMetrics alerts that are generated during the deployment of the Helm chart victoria-metrics-k8s-stack: I thought about writing a short post like “What is Churn Rate and how to fix it,” but in the end, I ended up diving deep into how VictoriaMetrics works with data in general… Read More »

Loading

VictoriaLogs: “rate limit exceeded” and monitoring ingested logs
0 (0)

13 September 2025

We use two systems for collecting logs in the project: Grafana Loki and VictoriaLogs, to which Promtail simultaneously writes all collected logs. We cannot get rid of Loki: although developers have long since switched to VictoriaLogs, some alerts are still created from metrics generated by Loki, so it is still present in the system. And… Read More »

Loading

PostgreSQL: using EXPLAIN and setting up “auto_explain” in AWS RDS
0 (0)

12 February 2025

I have already mentioned the EXPLAIN feature in the PostgreSQL: AWS RDS Performance and monitoring blog post, but this is such an interesting and useful thing that it’s worth talking about it separately. In addition, AWS RDS for PostgreSQL has the ability to enable Execution Plans logging with EXPLAIN, which is also useful for monitoring… Read More »

Loading

PostgreSQL: AWS RDS Performance and monitoring
0 (0)

10 February 2025

We are migrating our Backend API from DynamoDB to AWS RDS PostgreSQL, and several times RDS crashed. Actually, given that we took db.t3.small with two vCPUs and two gigabytes of memory to save money, it was quite expected, but I wondered why everything was crashing. A few days later, I started to debug the issue,… Read More »

Loading

VictoriaLogs: creating Recording Rules with VMAlert
0 (0)

11 January 2025

We continue the migration from Grafana Loki to VictoriaLogs, and the next task is to transfer Recording Rules from Loki to VictoriaLogs and update the alerts. Recording Rules and integration with VMAlert were brought to VictoriaLogs relatively recently, and I haven’t tested this scheme yet. Therefore, we will first do everything by hand to see… Read More »

Loading