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

Collect error rate data for tools #134

Open
abretaud opened this issue Jun 25, 2024 · 2 comments
Open

Collect error rate data for tools #134

abretaud opened this issue Jun 25, 2024 · 2 comments

Comments

@abretaud
Copy link
Contributor

It would nice to identify tools that are probably bugged: we can (somehow) look into the job exit codes on different usegalaxy.* servers, and tag tools with a "to fix" label when we see most of the jobs are failing.

I guess a tool can fail on a specific server and work fine on another one, not sure how to handle that (only tag when it fails everywhere? warn specific server admin where it fails?)

I recall @neoformit had some magic sql queries to identify problematic tools, maybe it could be used somehow?

@neoformit
Copy link
Collaborator

neoformit commented Jun 25, 2024

We did work on these scripts that enumerate jobs states and perform some crude clustering in an attempt to enumerate each tool-error. Maybe you can find them useful:

https://github.com/usegalaxy-au/tools-au/tree/master/scripts/broken-tools (check the README)

After some discussion at last GCC it seemed like the Galaxy Sentry server should be taken advantage of for this purpose. It seemed like modifying the sentry handler a little could provide most of the functionality above.

@paulzierep
Copy link
Collaborator

Thanks for the hint @neoformit that looks very interesting !!

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

3 participants