Call Internal Event API instead of RedisHLL for tracking on the FE
What does this MR do and why?
Implements #415337 (closed)
Currently, we are using trackRedisHLL API for internal events. Instead we would use internal events specific api.
API was implemented in !124561 (merged) MR
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
- In GDK go to
http://127.0.0.1:3000/admin/dev_ops_reports
- Click on the
dev
tab, instead of/increment_unique_users
,/usage_data/track_event
will be called with 200.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Ankit Panchal