Log the unsupported Go runtime metrics on startup instead, so the user is aware of unsupported metrics. The solution for removing the log lines is to upgrade Go builder. Reduce the minimum supported Go version at go.mod from Go1.20 to Go1.16, where the runtime/metrics package has been added. See https://tip.golang.org/doc/go1.16#runtime Updates https://github.com/VictoriaMetrics/metrics/issues/59 Updates https://github.com/VictoriaMetrics/metrics/pull/60
* process_metrics: adds metrics for windows OS * windows: fixes build constraints * bumps github ci go to 1.20 version * bumps go version at go.mod * go mod vendor
This should reduce memory usage when big number of Summary metrics are in use while small number of these metrics are updated