You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After updating from 22.11.0 to 23.6.0 we are experiencing 100% CPU load on a single core.
It seems that setting collectors.general.scrapeTime = 0 doesn't work anymore as the following messages are spammed after starting the container:
2023-06-15 08:21:48.979 | {"level":"info","caller":"collector/collector.go:339","msg":"finished metrics collection, next run in 0s","collector":"general","duration":0.000018939,"nextRun":"2023-06-15T06:21:48.979Z"}
2023-06-15 08:21:48.979 | {"level":"info","caller":"collector/collector.go:339","msg":"finished metrics collection, next run in 0s","collector":"general","duration":0.000018653,"nextRun":"2023-06-15T06:21:48.979Z"}
2023-06-15 08:21:48.979 | {"level":"info","caller":"collector/collector.go:339","msg":"finished metrics collection, next run in 0s","collector":"general","duration":0.000021911,"nextRun":"2023-06-15T06:21:48.979Z"}
2023-06-15 08:21:48.979 | {"level":"info","caller":"collector/collector.go:339","msg":"finished metrics collection, next run in 0s","collector":"general","duration":0.000019355,"nextRun":"2023-06-15T06:21:48.979Z"}
2023-06-15 08:21:48.979 | {"level":"info","caller":"collector/collector.go:339","msg":"finished metrics collection, next run in 0s","collector":"general","duration":0.000018812,"nextRun":"2023-06-15T06:21:48.979Z"}
This is how our config in 23.6.0 looks like:
config.yaml:
azure:
subscriptions: ["SUBSCRIPTION ID"]locations: ["germanywestcentral"]collectors:
# set general.scrapeTime to 0 to deactivate all scrapers by default.general:
scrapeTime: "0"quota:
scrapeTime: "5m"
After updating from 22.11.0 to 23.6.0 we are experiencing 100% CPU load on a single core.
It seems that setting collectors.general.scrapeTime = 0 doesn't work anymore as the following messages are spammed after starting the container:
This is how our config in 23.6.0 looks like:
config.yaml:
Commandline args:
In version 22.11.0 it looked like this and was working just fine:
The text was updated successfully, but these errors were encountered: