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

API endpoint for getting failed content keys #297

Open
mrferris opened this issue Jul 2, 2024 · 1 comment
Open

API endpoint for getting failed content keys #297

mrferris opened this issue Jul 2, 2024 · 1 comment

Comments

@mrferris
Copy link
Collaborator

mrferris commented Jul 2, 2024

Glados should have an API endpoint and a simple web dashboard feature for getting a list of content keys that had failed recently. This is useful for both manual debugging and for feeding into a bridge node to intelligently plug holes in the dataset.

Previously I made a script for nick to do this for manually debugging:

ssh glados "psql postgres://postgres:password@localhost:5432/glados -c \"\\copy (SELECT DISTINCT c.content_key FROM content c JOIN content_audit ca ON c.id = ca.content_key WHERE ca.result = 0 AND ca.strategy_used = 5 AND ca.created_at >= CURRENT_TIMESTAMP - INTERVAL '24 hours') TO '/home/devops/failed_4444s.txt';\"" && scp glados:/home/devops/failed_4444s.txt ~/failed_4444s.txt

@mrferris mrferris added this to Glados Jul 2, 2024
@mrferris mrferris converted this from a draft issue Jul 2, 2024
@Ktl-XV
Copy link
Contributor

Ktl-XV commented Oct 22, 2024

@mrferris can I take this issue?

@mrferris mrferris moved this from Prioritized Feature Backlog to In Review in Glados Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Review
Development

No branches or pull requests

2 participants