We need an API endpoint to read the stats out of solitude and return them to monolith. The endpoint should return a list of stats and allow monolith to paginate through them etc. The endpoint should allow a deletion of the stats, by id. So monolith can tell us explicitly which ones it has to delete. It's important that the endpoint is protected by a permission. Since this is not a public api. We should make a permission 'Statistics', 'Collect' or similar.
Monolith will be asking for data that's stored between two dates (start_date and end_date). I'm not sure we should ask for deletion per id, since it may generate a lot of traffic, rather than that, monolith could be able to ACK the receival and treatment of some data to the API, with the same request it made earlier. For instance, if I ask for the data between d1 and d2; I can send another request saying to delete the data between these two dates (and not for every item returned). IOW, we want batch deletion here. For the authentication and the permission, are you thinking about a particular scheme?
I think we should paginate the data between those two dates in case the data gets large. Agreed we will do the deletion by batch. Could you send all the ids you want to delete in one request? Or the first and last id for example. I'd rather not just use dates as the ranges if possible, I've seen that go wrong a few times :)
EU team talked a bit: We agreed on doing any sort of aggregation / summing up on the monolith side. So the API can export individual records for each download or any other tracked metric.
OS: Mac OS X → All
Hardware: x86 → All
Whiteboard: [u=dev c=mkt-statistics p=2]
oops, de-assigning myself. I thought this was for the API on the zamboni side, whereas it's on the solitude side.
Assignee: alexis → nobody
Summary: Create an API endpoint → Create an API endpoint in solitude
I typod in the comment 0. It is zamboni, my mistake.
Summary: Create an API endpoint in solitude → Create an API endpoint in zamboni
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.