-
-
Notifications
You must be signed in to change notification settings - Fork 78
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
[feature] Add optional clean insights data collection #360
Labels
Comments
pandafy
added a commit
that referenced
this issue
Nov 29, 2023
6 tasks
pandafy
added a commit
that referenced
this issue
Dec 1, 2023
pandafy
added a commit
that referenced
this issue
Feb 2, 2024
pandafy
added a commit
that referenced
this issue
Feb 19, 2024
pandafy
added a commit
that referenced
this issue
Feb 23, 2024
nemesifier
pushed a commit
that referenced
this issue
Feb 24, 2024
nemesifier
added a commit
that referenced
this issue
Feb 27, 2024
pandafy
added a commit
that referenced
this issue
Mar 1, 2024
nemesifier
added a commit
that referenced
this issue
Mar 4, 2024
…es) #360 - Fixed mocking of request library in MockRequestPostRunner - Do not send metrics on post_migrate if no module is upgraded Related to #360 --------- Co-authored-by: Federico Capoano <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Depends on #273
We can collect this info when the application starts, maybe we should restrict this to the application server process only (no celery) and ensure it's performed only once, we should use a thread to avoid slowing down startup.
We need a setting to control whether this is enabled or not, it shall be disabled by default.
Let's add a section in the README which explains what data is collected and why.
We can test this in staging with the clean insights staging/prod system.
The text was updated successfully, but these errors were encountered: