Skip to content
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

Include process RSS on Busy page #4717

Closed
mperham opened this issue Oct 14, 2020 · 2 comments
Closed

Include process RSS on Busy page #4717

mperham opened this issue Oct 14, 2020 · 2 comments

Comments

@mperham
Copy link
Collaborator

mperham commented Oct 14, 2020

Seeing the process RSS can be really helpful in determining at a glance if a Sidekiq process is "healthy" or not. If RSS is high, one click on the Stop button can fix it.

While nice, things like sparklines or historical data or graphs are not in scope. This issue does not aim to compete with NewRelic or DataDog.

@mperham
Copy link
Collaborator Author

mperham commented Oct 14, 2020

Screen Shot 2020-10-14 at 2 52 52 PM

@TALlama
Copy link

TALlama commented Feb 26, 2021

We use a multi-tenant architecture where each tenant is run as its own Rails app, on shared app and db servers. The sidekiq workers follow that same pattern: each tenant gets its own worker on the shared box, and its own queues, but they all share a Redis db so that we can monitor them all from one place.

Today we got an alert that the worker box was low on memory, and we used the Sidekiq Web UI to quickly identify which tenant was having the problem, allowing us to easily find the offending job.

(the underlying bug, for the curious: the bulk download created by the job in a question was doing a FileMagic scan to identify the file type of the ZIP file it had just created, which apparently involves FileMagic reading the entire 14GB file into memory. Needless to say this didn’t work out; we made that job skip the scan and assume that our zip creation code does indeed create zip files)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants