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.

Sign up for GitHub

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

Jump to bottom

Implement and surface value-based deferred metrics #3944

Closed
dhruvkb opened this issue Mar 20, 2024 · 3 comments
Closed

Implement and surface value-based deferred metrics #3944

dhruvkb opened this issue Mar 20, 2024 · 3 comments
Labels
💻 aspect: code Concerns the software code in the repository 🌟 goal: addition Addition of new feature 🟩 priority: low Low priority and doesn't need to be rushed 🧱 stack: api Related to the Django API
Milestone
Content moderatio...

Comments

@dhruvkb
Copy link
Member

dhruvkb commented Mar 20, 2024 •
edited
Loading

Description

Implement functions to compute the deferred metrics and cache them in Redis with appropriate TTL. This issues only includes metrics that are single numerical values.

  • total reports
  • report accuracy
  • report duplication
  • average decision time
  • P99 decision time

These metrics must be surfaced in the Django admin by customising the admin template for ImageReport and AudioReport models.

Additional context
@dhruvkb dhruvkb added 🟨 priority: medium Not blocking but should be addressed soon 🌟 goal: addition Addition of new feature 💻 aspect: code Concerns the software code in the repository 🧱 stack: api Related to the Django API labels Mar 20, 2024
@openverse-bot openverse-bot moved this to 📋 Backlog in Openverse Backlog Mar 20, 2024
@dhruvkb dhruvkb changed the title Implement value-based deferred metrics Implement and surface value-based deferred metrics Mar 20, 2024
@dhruvkb
Copy link
Member Author

dhruvkb commented Mar 20, 2024

The surfacing of the metrics depends on the Django admin views (https://github.com/WordPress/openverse/milestone/22) to be ready.

@dhruvkb dhruvkb added the ⛔ status: blocked Blocked & therefore, not ready for work label Mar 20, 2024
@openverse-bot openverse-bot moved this from 📋 Backlog to ⛔ Blocked in Openverse Backlog Mar 20, 2024
@obulat obulat removed the ⛔ status: blocked Blocked & therefore, not ready for work label Jun 5, 2024
@obulat obulat moved this from ⛔ Blocked to 📅 To Do in Openverse Backlog Jun 5, 2024
@openverse-bot openverse-bot moved this from 📅 To Do to 📋 Backlog in Openverse Backlog Jun 5, 2024
@sarayourfriend sarayourfriend added 🟩 priority: low Low priority and doesn't need to be rushed and removed 🟨 priority: medium Not blocking but should be addressed soon labels Jun 5, 2024
@sarayourfriend
Copy link
Collaborator

Reprioritised as per #383 (comment)

@sarayourfriend
Copy link
Collaborator

Closing as won't do as per #383 (comment)

@openverse-bot openverse-bot moved this from 📋 Backlog to ✅ Done in Openverse Backlog Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
💻 aspect: code Concerns the software code in the repository 🌟 goal: addition Addition of new feature 🟩 priority: low Low priority and doesn't need to be rushed 🧱 stack: api Related to the Django API
Projects
Openverse Backlog
Archived in project
Milestone
Content moderation metrification
Development

No branches or pull requests
3 participants
@obulat @dhruvkb @sarayourfriend