Configurate API to keep flag analytics data but drop API traffic.

[landonjs]

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

[dabeeeenster]

I'm not sure what the best way to configure this is? Maybe as a ENV VAR configurable list that defaults to [tasks.track_request, tasks.track_feature_evaluation,...]

[landonjs]

That would work 👍

[matthewelwell]

I'm not sure what the best way to configure this is? Maybe as a ENV VAR configurable list that defaults to [tasks.track_request, tasks.track_feature_evaluation,...]

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.

[sumit-158]

Can I work on this?

[matthewelwell]

@sumit-158 yes, please feel free!