jupiter: add VictoriaMetrics monitoring #1

Merged
darman merged 8 commits from feat/mars-victoriametrics into master 2026-08-24 04:48:46 +02:00
Showing only changes of commit 5764e6c644 - Show all commits
+5 -1
View File
1
@@ -14,7 +14,7 @@
listenAddress = ":8428";
prometheusConfig = {
global.scrape_interval = "60s";
global.scrape_interval = "5s";
luna marked this conversation as resolved
Review

With no scrape_timeout set, this inherits the 10s default — which is longer than the 5s interval. VictoriaMetrics resolves that by clamping the timeout down to the interval, so it silently becomes 5s.

That is fine for the wired hosts, but mercury is a Pi scraped over the tailnet. Anything slower than 5s becomes a gap in the series rather than a late sample, and you will not get an obvious error for it — just missing points.

Either set an explicit scrape_timeout, or give mercury its own job with a longer interval and leave 5s for the rest.

With no `scrape_timeout` set, this inherits the 10s default — which is longer than the 5s interval. VictoriaMetrics resolves that by clamping the timeout down to the interval, so it silently becomes 5s. That is fine for the wired hosts, but mercury is a Pi scraped over the tailnet. Anything slower than 5s becomes a gap in the series rather than a late sample, and you will not get an obvious error for it — just missing points. Either set an explicit `scrape_timeout`, or give mercury its own job with a longer interval and leave 5s for the rest.
scrape_configs = [
{
1
@@ -36,6 +36,10 @@
targets = [ "mercury.orbit.sol:9100" ];
labels.host = "mercury";
}
{
targets = [ "terra.orbit.sol:9100" ];
labels.host = "terra";
}
];
}
{