mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-12-18 14:40:26 +01:00
6d237da3f3
- Clarify that the -promscrape.maxScrapeSize value is used for limiting the maximum scrape size if max_scrape_size option isn't set at https://docs.victoriametrics.com/sd_configs/#scrape_configs - Fix query example for scrape_response_size_bytes metric at https://docs.victoriametrics.com/vmagent/#automatically-generated-metrics - Mention about max_scrape_size option at the -help description for -promscrape.maxScrapeSize command-line flag - Treat zero value for max_scrape_size option as 'no scrape size limit' - Change float64 to int type for scrapeResponseSize struct fields and function args, since response size cannot be fractional - Optimize isAutoMetric() function a bit - Sort auto metrics in alphabetical order in isAutoMetric() and in scrapeWork.addAutoMetrics() functions for better maintainability in the future Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/6434 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/6429 |
||
|---|---|---|
| .. | ||
| 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 | ||
| targetstatus.go | ||
| targetstatus.qtpl | ||
| targetstatus.qtpl.go | ||