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

feat: toggle failed queues only #742

Closed

Conversation

tsirilson
Copy link

Added a toggle to filter out non-failing queues.

Why?

When using Bull Board for production monitoring purposes, it's very useful when you want to know about failing jobs (not as a substitute for alerts).

In my case, I'm displaying it on a TV in my company's office and we have 20 different queues currently, which makes it hard to follow if any of them have failures, especially if one of the queues has a lot of successful jobs, so it's easy to miss that there's one failed job out of a thousand successful ones.

Filtering successful ones out should help us focus on the board only when we notice that there are any failing queues.

image

@tsirilson tsirilson force-pushed the tsirilson/failedOnlyQueues branch from 2a87f69 to 26afc00 Compare May 15, 2024 14:37
@felixmosh
Copy link
Owner

@tsirilson thank you for this PR,
It looks like a overview page feature, so it probably should be implemented inside it.
In addition, this feature can't be tailor only for your needs, but should be more general, so maybe creating a modal that let's you to choose which statuses should be filtered by, and then the overview page will show queues with those statuses.

Will you be able to update your PR?

@tsirilson
Copy link
Author

@felixmosh Great point. What if instead of a modal, I convert the status names into clickable "buttons" that toggle the status on and off? It will also be less intrusive and won't require creating a modal for this feature only. There can also be a tooltip when hovering a status name that hints what will happen if you click it.

What do you think?

@manfe
Copy link

manfe commented May 17, 2024

@tsirilson @felixmosh

Instead of creating a setting for that. I would create a route to receive a status as a parameter and then only show the queues with that status on that page.

on App.tsx would create:

<Route path="/queue/by-status/:status" render={() => <QueueByStatusPageLazy />} />

It would be a copy of OverviewPage but filtering the queues by the corresponding status.

Also the statuses on Overview page could be turned into links, redirecting to this page.

@felixmosh
Copy link
Owner

@felixmosh Great point. What if instead of a modal, I convert the status names into clickable "buttons" that toggle the status on and off? It will also be less intrusive and won't require creating a modal for this feature only. There can also be a tooltip when hovering a status name that hints what will happen if you click it.

What do you think?

Sounds good to me 🙏🏼

@tsirilson
Copy link
Author

@manfe Interesting approach. Direct links is something I would also prefer, the option to link to a specific job is something I find very useful since it was added.

@felixmosh which do you think would benefit users the most? Same page filters or dedicated routes?

@felixmosh
Copy link
Owner

It can be both, it is a matter of implementation.
Overview page can a query param with a list of statuses to show, by default shows all.

Copy link

stale bot commented Aug 15, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label Aug 15, 2024
@tsirilson tsirilson closed this Aug 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants