Not showing up in Sidekiq Web UI

[raysegantii]

Does Exq show up in Sidekiq Web UI?

Normally when I start a Sidekiq worker, it shows up in the Busy tab (under the Processes table), and it lists what queues it's listening to.

When I starts the Exq, it is picking up jobs off the queues I configured, but it doesn't show any thing in that page.

Is it supported or just I miss any particular configuration?

[akira]

@raysegantii Exq by default is set to the "exq" namespace in the config. You can set it to the root ( namespace: "") namespace in config.exs for Sidekiq to pick it up.

Also, FYI, the workers will not show up until there is a job performed, as they are spawned on demand.

[raysegantii]

Thank you @akira. I've set the namespace: nil, perhaps it caused the issue. I'll test again with empty string.

[akira]

Actually that should have worked as well. Was a worker actually in progress when you checked? (Can try putting a sleep into it to make sure). Let me know if this doesn't work and I can take a look, perhaps the format we are using has changed a bit for sidekiq.

…

On Sun, Nov 27, 2016 at 5:55 PM Ray Cheung ***@***.***> wrote: Thank you @akira <https://github.com/akira>. I've set the namespace: nil, perhaps it caused the issue. I'll test again with empty string. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#222 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AACrquSK3jdF6429tJ2gUkI4j57X_ZqHks5rCgp6gaJpZM4K5NHO> .

[raysegantii]

@akira It still doesn't work with namespace: "", I suppose there is compatibility issue with sidekiq 4.2.6 now. Please help investigating, thank you very much.

[raysegantii]

To be clear, Exq does picking up jobs from Sidekiq (and re-enqueue on failure, etc.), so functionally it works perfectly, just that it doesn't show up in the Sidekiq UI in the Busy tab, making it like a phantom rogue daemon in the background.

[ondrejbartas]

@raysegantii same issue here. I was looking into redis, and there is no information in processes key.

[j-mcnally]

We probably aren't writing the key for the process to the correct place if i had to guess.

…

On Tue, Oct 10, 2017 at 11:11 AM Ondřej Bartas ***@***.***> wrote: @raysegantii <https://github.com/raysegantii> same issue here. I was looking into redis, and there is no information in processes key. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#222 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA2d3sGz-ZVdYt7MR_Dm6V6sVT9wQap9ks5sq5dKgaJpZM4K5NHO> .

[ondrejbartas]

I was investigating the problem and found that sidekiq has diiferent structure how it stores in redis processes and busy workers. I have created working version in PPCBee#1 but maybe I will need help with it. I need to somehow get identifier of started process which is running workers, because the difference is:

is sidekiq:
1 process mas several workers/threads

but in exq you were adding 1 worker as process.

[worace]

Not sure if this is related, but I have been running the sidekiq UI against a redis instance being queued by Exq, and have found that the "Busy" workers don't seem to show up. Retries, dead, failed, and processed do all show correctly.

[ananthakumaran]

This should be fixed on master by #458