Tag Archives: monitoring

LiteLLM: Metrics, Traces, and VictoriaMetrics Stack Integration
0 (0)

9 July 2026

Third part on running LiteLLM – AI Gateway or LLM Proxy, and finally we’re getting to monitoring. In the first part we got familiar with LiteLLM in general (see LiteLLM: AI Gateway for LLMs – overview of features), and in the second one we deployed it in Kubernetes and hooked up VictoriaTraces and VictoriaMetrics to… Read More: LiteLLM: Metrics, Traces, and VictoriaMetrics Stack Integration0 (0) »

Loading

Claude Code: Monitoring with OpenTelemetry and VictoriaMetrics
0 (0)

18 June 2026

While working on LiteLLM (see LiteLLM: AI Gateway for LLMs – features overview), I had an idea: besides services like our Backend API, why not also monitor the Claude Code developers? Just out of curiosity – to see what’s going on there in general and how everyone uses our Anthropic Organization, because a lot of… Read More: Claude Code: Monitoring with OpenTelemetry and VictoriaMetrics0 (0) »

Loading

OpenTelemetry: OTel Collectors in Kubernetes and VictoriaMetrics Stack integration
0 (0)

16 May 2026

Today let’s talk about how to run OpenTelemetry in Kubernetes and integrate it with the VictoriaMetrics stack – VictoriaMetrics for metrics, VictoriaLogs for logs, and VictoriaTraces for traces. Actually, this post wasn’t planned at all, and once a draft did appear – it was supposed to be the third in the series, but in the… Read More: OpenTelemetry: OTel Collectors in Kubernetes and VictoriaMetrics Stack integration0 (0) »

Loading

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: VictoriaMetrics: using vmalert and query() in alerts for different $value… »

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: Glance: setting up a self-hosted home page for your browser0… »

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: ilert: an alternative to Opsgenie – first impressions, Alertmanager, Slack5… »

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: VictoriaMetrics: Recording rules for AWS Load Balancer logs0 (0) »

Loading

Golang: creating OpenAI Exporter for VictoriaMetrics
0 (0)

23 November 2025

Got a new task to monitor costs on OpenAI – to see how much each project spends per day, and send alerts to Slack if costs exceed a set threshold. I tried several existing exporters for the OpenAI API, but none provided cost metrics per project – so we’ll build one ourselves. To create the… Read More: Golang: creating OpenAI Exporter for VictoriaMetrics0 (0) »

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: VictoriaMetrics: Churn Rate, High cardinality, metrics, and IndexDB0 (0) »

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: VictoriaLogs: “rate limit exceeded” and monitoring ingested logs0 (0) »

Loading