-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sidekiq Stats Collector Memory Leak #240
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello there,
we have Investigated an Issue with one of our prometheus_exporter Setups which stopped working.
After a certain perioud of runtime the collector started to report collector_working with Value 0 and all our Instrumentation Metrics went missing.
The only difference we found to another Setup of our which has no issues was the usage of the SideKiqStats Instrumentation so we looked into that.
It seems that here new observations are added to the sidekiq_metrics object which results in it getting bigger and bigger.
After a certain amount of time the Collector is not able to generate the Metric Text withing the configured default Timeout of 2 Seconds and we start seeing the above mentioned behavior.
As a comparison the SidekiqQueueCollector seems to have a mechanism to clean up older Observations.
Our guess would be that the SidekiqStatsCollector would need something like that too.
The text was updated successfully, but these errors were encountered: