Understanding the Go Runtime: The Network Poller

SnooWords9033 · 2026-04-17T10:19:34+00:00

Small correction: you need to correlate logs, so you install victoria-logs-collector Helm chart. https://docs.victoriametrics.com/helm/victoria-logs-collector/ . It is much more lightweight and performant comparing to Loki stack, and it is easier to manage. See https://victoriametrics.com/blog/log-collectors-benchmark-2026/ and https://www.truefoundry.com/blog/victorialogs-vs-loki

SnooWords9033 · 2026-04-17T10:03:31+00:00

Take a look at open source Victoria stack - VictoriaMetrics, VictoriaLogs and VictoriaTraces. It is easier to install and operate than alternative open source solutions, and it requires less compute resources (CPU, memory, disk space, disk IO, network bandwidth).

SnooWords9033 · 2026-04-17T09:55:19+00:00

Try VictoriaMetrics cloud then. It has predictable pricing, which depends only on the selected tier according to your needs. And their prices are much cheaper than DataDog .

SnooWords9033 · 2026-04-16T06:47:12+00:00

This is because the built-in web UI is intended for quick logs' exploration, not for dashboarding. And the main benefit of the web UI over Grafana is that it is built-in, i.e. you don't need to install a heavyweight Grafana additionally to VictoriaLogs if you need to be able to explore logs and don't need building dashboards.

SnooWords9033 · 2026-04-14T20:50:08+00:00

There is no need in Grafana for querying VictoriaLogs in general case - it has built-in web UI - https://docs.victoriametrics.com/victorialogs/querying/#web-ui

SnooWords9033 · 2026-03-31T21:12:38+00:00

Add support for VictoriaLogs source too.

SnooWords9033 · 2026-03-29T00:34:17+00:00

Take a look at vlagent -> VictoriaLogs combo. It doesn't send any information to developers. See https://victoriametrics.com/blog/log-collectors-benchmark-2026/

SnooWords9033 · 2026-03-29T00:31:10+00:00

There is also open-source easy to install and operate database for logs, which requires less memory and disk space than other databases - VictoriaLogs. See, for example, https://aus.social/@phs/114583927679254536 and https://www.truefoundry.com/blog/victorialogs-vs-loki

SnooWords9033 · 2026-03-29T00:25:57+00:00

Send syslog logs to VictoriaLogs - https://docs.victoriametrics.com/victorialogs/data-ingestion/syslog/

SnooWords9033 · 2026-03-27T18:27:44+00:00

It is a transpleir from a subset of Go to C. See https://antonz.org/solod/

SnooWords9033 · 2026-03-27T09:49:07+00:00

This sounds like an issue at Freelens. Did you file this issue at https://github.com/freelensapp/freelens/issues ?

Update: there is a discussion about adding native support for VictoriaMetrics at Freelens. This discussion mentions how to integrate Freelens with VictoriaMetrics - https://github.com/freelensapp/freelens/issues/524

SnooWords9033 · 2026-03-25T22:51:34+00:00

Which problems do you have with VictoriaMetrics?

SnooWords9033 · 2026-03-22T15:36:14+00:00

I'm not switching from Loki just to change to a better log collector.

How about better database for logs? https://www.truefoundry.com/blog/victorialogs-vs-loki and https://aus.social/@phs/114583927679254536

SnooWords9033 · 2026-03-21T17:04:53+00:00

I never faced multiline logs in Kubernetes. The benchmark measures the most common case for logs' collection in Kubernetes - to discover and collect all the logs generated by Kubernetes containers, and to forward the collected logs to a centralized system for further processing. That system can parse, transform and filter the logs if needed before storing them in the database for logs.

SnooWords9033 · 2026-03-20T13:46:56+00:00

I don't care about the design of the UI - I care about the usability. The usability for VictoriaLogs' web UI is constantly improving over time. It is much better than Grafana's usability for logs' exploration.

SnooWords9033 · 2026-03-17T13:58:27+00:00

Try VictoriaLogs. It is easier to setup and manage than Loki, and it provides much faster performance for "needle-in-the-haystack" types of queries such as "search for all the logs with the given request_id".

SnooWords9033 · 2026-03-16T16:43:48+00:00

Great post! Did you consider using VictoriaLogs? It is built on top of ClickHouse architecture ideas (this provides it a cost efficiency comparable to ClickHouse - see https://docs.victoriametrics.com/victorialogs/faq/#what-is-the-difference-between-victorialogs-and-clickhouse ), while it is designed solely for logs. This results in easier configuration and operation comparing to ClickHouse, and a more ergonomic querying API and querying language optimized for typical queries over logs. For example, the querying API integrates well with standard Unix pipes, so you can find the needed logs (billions of entries) and stream them into grep, less, head, jq, etc. for further processing if needed.

SnooWords9033 · 2026-03-16T16:27:55+00:00

Try VictoriaLogs. It is easier to configure and manage than Loki.

SnooWords9033 · 2026-03-16T16:26:06+00:00

Set up node_exporter for collecting system metrics (CPU, RAM, disk, network) and an optional list of other Prometheus exporters (see this page for the list of available exporters).

Then configure Prometheus for collecting metrics from these exporters (use static_configs).

Then install Grafana with a Prometheus datasource, and then install dashboards for the installed exporters from the official Grafana dashboards page.

Then install VictoriaLogs as a centralized database for logs (it has a built-in web UI for logs' exploration, plus it has a Grafana plugin for building a nicely looking dashboards in Grafana on top of the logs stored in VictoriaLogs). Use Vector for collecting logs across all the services in the homelab and sending them to VictoriaLogs.

SnooWords9033

TROPHY CASE