Skip to content
This repository has been archived by the owner on Feb 22, 2023. It is now read-only.

Remove the analytics service #579

Closed
1 task
zackkrida opened this issue Mar 21, 2022 · 0 comments · Fixed by #618
Closed
1 task

Remove the analytics service #579

zackkrida opened this issue Mar 21, 2022 · 0 comments · Fixed by #618
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing user-facing feature 🟨 priority: medium Not blocking but should be addressed soon
Projects
Openverse

Comments

@zackkrida
Copy link
Member

Problem

Currently, the analytics service isn't enabled in the production frontend, and we feel that most of the things we are collecting can be gleaned from the API request logs. As discussed previously we have concerns about the Analytics server modifying the API database (#484). Additionally, we'd like any telemetry/analytics of this kind to be opt-in and very transparent to our users, which will require time to build out UI elements for.

Description

We should remove the analytics service entirely from this repo.

Additional context

Alongside efforts to deprecate the ingestion server and replace it with a DAG, this would help the API repository to cease being monorepo-esque, which should ease maintenance.

Implementation

  • 🙋 I would be interested in implementing this feature.
@zackkrida zackkrida added 🟩 priority: low Low priority and doesn't need to be rushed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work ✨ goal: improvement Improvement to an existing user-facing feature 💻 aspect: code Concerns the software code in the repository labels Mar 21, 2022
@dhruvkb dhruvkb added this to Backlog in Openverse Mar 21, 2022
@zackkrida zackkrida added 🟨 priority: medium Not blocking but should be addressed soon 🟩 priority: low Low priority and doesn't need to be rushed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work and removed 🟩 priority: low Low priority and doesn't need to be rushed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Mar 21, 2022
@sarayourfriend sarayourfriend removed 🟩 priority: low Low priority and doesn't need to be rushed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Mar 21, 2022
@dhruvkb dhruvkb moved this from Backlog to To do in Openverse Mar 22, 2022
@AetherUnbound AetherUnbound moved this from To do to Backlog in Openverse Mar 29, 2022
@sarayourfriend sarayourfriend mentioned this issue Apr 4, 2022
Closed
@obulat obulat mentioned this issue Apr 4, 2022
Merged
7 tasks
@openverse-bot openverse-bot moved this from Backlog to In progress in Openverse Apr 4, 2022
Openverse automation moved this from In progress to Done! Apr 4, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing user-facing feature 🟨 priority: medium Not blocking but should be addressed soon
Projects
No open projects
Openverse
  
Done!
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Remove analytics server WordPress/openverse-api
2 participants
@zackkrida @sarayourfriend