-
Notifications
You must be signed in to change notification settings - Fork 429
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
Configurate API to keep flag analytics data but drop API traffic. #2580
Comments
I'm not sure what the best way to configure this is? Maybe as a ENV VAR configurable list that defaults to |
That would work 👍 |
We would need to do the configuration at a slightly higher level as there is more logic than just the tasks here, but an env var to control which pieces of analytics are enabled would likely be the best option, yes. |
Can I work on this? |
@sumit-158 yes, please feel free! |
Can you guide more about the problem and the file location? |
There should be enough information in the description and the comments already? Perhaps you can make sure you've read and understood those and ask any specific questions you might have? Here are some files that will likely need modification: https://github.com/Flagsmith/flagsmith/blob/main/api/app_analytics/tasks.py |
Hey @sumit-158 , are you still working on this issue. If not, please let me know, I want to give it a try |
@SD-13 sure go ahead! |
Is your feature request related to a problem? Please describe.
All of our API requests to Flagsmith come from internal dapr calls so all the requests are the same. The data isn't useful and generates millions of requests a day.
Describe the solution you'd like
We would like the ability to not keep API requests but still track features and audits. This would keep the DB table smaller and free up cycles in the task processor.
Additional context
Add any other context or screenshots about the feature request here.
https://discord.com/channels/517647859495993347/517647859966017541/threads/1136724109103992912
The text was updated successfully, but these errors were encountered: