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

Implement a web UI to show the queue status #438

Open
msm-cert opened this issue Nov 18, 2024 · 0 comments · May be fixed by #446
Open

Implement a web UI to show the queue status #438

msm-cert opened this issue Nov 18, 2024 · 0 comments · May be fixed by #446
Assignees
Labels
next-sprint Scheduled for work (CERT.PL internal) type:feature Add a new feature zone:frontend Frontend oriented tasks
Milestone

Comments

@msm-cert
Copy link
Member

After implementing #437 it would be nice to show the current indexing queue status somewhere.

I think the easiest solution would be to put this information in the status subpage (/status). It will be only visible to admin that way, but I don't think this feature warrants a new separate subpage (but if you think differently it's OK too).

The UI should show a list of queues (i.e. all ursadb instances with at least one file pending) and a number of pending files. Maybe also some other data, like oldest and newest file in each queue.

The UI should also have a button to remove all files (clear the queue).

@msm-cert msm-cert added type:feature Add a new feature next-sprint Scheduled for work (CERT.PL internal) zone:frontend Frontend oriented tasks labels Nov 18, 2024
mickol34 added a commit that referenced this issue Jan 29, 2025
@mickol34 mickol34 linked a pull request Jan 29, 2025 that will close this issue
4 tasks
@msm-cert msm-cert added this to the v1.7.0 milestone Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
next-sprint Scheduled for work (CERT.PL internal) type:feature Add a new feature zone:frontend Frontend oriented tasks
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants