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

[BLOCKED by 1249] programmatically report on all objects with audit failures #1261

Closed
ndushay opened this issue Dec 12, 2019 · 3 comments
Closed

Comments

@ndushay
Copy link
Contributor

ndushay commented Dec 12, 2019

Before #1249 (ReST endpoint for audit details), this would merely give out druids for objects with not "ok" status, so perhaps not useful until #1249 is done.

Idea: someone should be concerned with failing audit checks; being able to generate a report of all objects failing audits, and the audit failure details, would be super helpful in trying to figure out what to do.

This could be an "on demand" thing, or run by a cron job.

We would also need to know WHO would be getting this and treating it as actionable rather than noise.

@jmartin-sul
Copy link
Member

jmartin-sul commented Dec 14, 2019

@ndushay, assigning this to you just so someone doesn't pick it up if you're already working on it. i got the impression you intended to tackle this along with #1249 -- if that's a mistake (like if i was the one that pulled it into the "In Progress" column but i forgot), feel free to unassign and move back to "Ready".

@jmartin-sul
Copy link
Member

jmartin-sul commented Dec 16, 2019

discussed F2F, un-assigning since naomi's not working on this right now, but marking blocked since we prob want #1249 to be done before this is started. naomi may or may not pick this one up next.

@jmartin-sul jmartin-sul changed the title programmatically report on all objects with audit failures [BLOCKED by 1249] programmatically report on all objects with audit failures Dec 16, 2019
@ndushay
Copy link
Contributor Author

ndushay commented Feb 13, 2020

this is probably going to be addressed via #1324 and #1363

@ndushay ndushay closed this as completed Feb 13, 2020
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