jupiter: add VictoriaMetrics monitoring #1
@@ -14,7 +14,7 @@
|
|||||||
listenAddress = ":8428";
|
listenAddress = ":8428";
|
||||||
|
|
||||||
prometheusConfig = {
|
prometheusConfig = {
|
||||||
global.scrape_interval = "60s";
|
global.scrape_interval = "5s";
|
||||||
|
luna marked this conversation as resolved
|
|||||||
|
|
||||||
scrape_configs = [
|
scrape_configs = [
|
||||||
{
|
{
|
||||||
@@ -36,6 +36,10 @@
|
|||||||
targets = [ "mercury.orbit.sol:9100" ];
|
targets = [ "mercury.orbit.sol:9100" ];
|
||||||
labels.host = "mercury";
|
labels.host = "mercury";
|
||||||
}
|
}
|
||||||
|
{
|
||||||
|
targets = [ "terra.orbit.sol:9100" ];
|
||||||
|
labels.host = "terra";
|
||||||
|
}
|
||||||
];
|
];
|
||||||
}
|
}
|
||||||
{
|
{
|
||||||
|
|||||||
Reference in New Issue
Block a user
With no
scrape_timeoutset, 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.