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

Collect data on API usage #754

Closed
obulat opened this issue Apr 21, 2021 · 3 comments
Closed

Collect data on API usage #754

obulat opened this issue Apr 21, 2021 · 3 comments
Labels
💻 aspect: code Concerns the software code in the repository 🌟 goal: addition Addition of new feature 🟨 priority: medium Not blocking but should be addressed soon 🧱 stack: api Related to the Django API

Comments

@obulat
Copy link
Contributor

obulat commented Apr 21, 2021 •
edited
Loading

This issue has been migrated from the CC Search API repository

Author: kgodey
Date: Fri Apr 10 2020
Labels: ✨ goal: improvement,🏷 status: label work required,🙅 status: discontinued

Problem Description

We should collect data on how our API is being used. We should be able to create reports of non-CC Search API usage

  • by API key
  • from unauthenticated users (per user, anonymized)

Solution Description

Append API keys (when available) to uwsgi logs.
@prikshit-1103
Copy link

@dhruvkb I would like to contribute to bus issue also if possible could u assign this one to me also .

@dhruvkb
Copy link
Member

dhruvkb commented Sep 10, 2022

@prikshit-1103 this issue is a bit contrived and needs significant planning before it can be addressed. Furthermore this issue has not yet been triaged and might be planned for the long-term future in our roadmap.

Could you find a different issue to work on? Thanks!

@dhruvkb dhruvkb added the 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work label Sep 10, 2022
@krysal krysal 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 and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Sep 13, 2022
@obulat obulat mentioned this issue Feb 16, 2023
Closed
26 tasks
@obulat obulat transferred this issue from WordPress/openverse-api Feb 22, 2023
@github-project-automation github-project-automation bot moved this to 📋 Backlog in Openverse Backlog Feb 23, 2023
@AetherUnbound AetherUnbound added 🧱 stack: api Related to the Django API and removed 🧱 stack: backend labels May 15, 2023
@AetherUnbound AetherUnbound changed the title Collect data on API usage (original #476) Collect data on API usage Oct 12, 2023
@AetherUnbound
Copy link
Collaborator

Based on the solution criteria here:

Append API keys (when available) to uwsgi logs.

I believe this was #3369 and can be closed!

@openverse-bot openverse-bot moved this from 📋 Backlog to ✅ Done in Openverse Backlog Dec 27, 2023
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: medium Not blocking but should be addressed soon 🧱 stack: api Related to the Django API
Projects
Openverse Backlog
Archived in project
Milestone
No milestone
Development

No branches or pull requests
5 participants
@krysal @AetherUnbound @obulat @dhruvkb @prikshit-1103