Closed ryanrazsa closed 11 months ago
Hi! I can say that this version also doesn't work with go v1.18
I think that we can skip these metrics for previous versions of golang
I will prepare PR for this issue
I think that we have the simplest solution for this case I propose to remove panic in this case
@ryanrazsa , thanks for the bugreport! @jombG , thanks for the initial attempt to fix the issue at https://github.com/VictoriaMetrics/metrics/pull/60 !
The issue has been fixed in the commit 447d235cbb84d47adde5cd96943eb0d0d44a8836 . This commit logs unsupported Go runtime metrics at startup, so the user could remove these log lines by upgrading Go builder. The commit also lowers the minimum supported Go version from Go1.20 to Go1.16. This commit has been included in the tag v1.25.4. Closing the issue as fixed then.
New runtime metrics were added in this PR.
Specifically the metric
"/gc/gomemlimit:bytes", "go_memlimit_bytes"
is not available ingo 1.20
. It was added in this commit.Using
go 1.20
causes the following panic:Steps to reproduce:
Using
go 1.20
This same test passes using
go 1.21