mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-12-15 00:13:30 +01:00
b6d6a3a530
Previously the /service-discovery page didn't show targets dropped because of sharding ( https://docs.victoriametrics.com/vmagent.html#scraping-big-number-of-targets ). Show also the reason why every target is dropped at /service-discovery page. This should improve debuging why particular targets are dropped. While at it, do not remove dropped targets from the list at /service-discovery page until the total number of targets exceeds the limit passed to -promscrape.maxDroppedTargets . Previously the list was cleaned up every 10 minutes from the entries, which weren't updated for the last minute. This could complicate debugging of dropped targets. Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5389 |
||
|---|---|---|
| .. | ||
| discovery | ||
| discoveryutils | ||
| testdata | ||
| client.go | ||
| config_test.go | ||
| config_timing_test.go | ||
| config.go | ||
| relabel_debug.go | ||
| scraper.go | ||
| scrapework_test.go | ||
| scrapework_timing_test.go | ||
| scrapework.go | ||
| statconn_test.go | ||
| statconn.go | ||
| targetstatus.go | ||
| targetstatus.qtpl | ||
| targetstatus.qtpl.go | ||