4 ms·
The problem becomes if you make a mistake or aggregate in the wrong way you end up losing the ability to do later analysis. If I had thrown out my logs I would
by danieltillett 9y ago
The problem becomes if you make a mistake or aggregate in the wrong way you end up losing the ability to do later analysis. If I had thrown out my logs I would have provided my customers with a worse experience.
I am supportive of the intent of the GDPR and we have always gone out of our way to minimise the data we collect, but as currently written the law has a whole lot of very negative downstream effects.
Really the law seems to have been written to catch a few bad players and has ended up netting everyone in the world.
- e12e 9y agoRe: "Where usage growth was coming from" sounds like the kind of things a log of performance data pr server might also answer. Can't argue with the fact that storing less and corner grained data will make certain ad hoc queries harder. That's kinda the point.
- danieltillett 9y agoPerformance data is not going to tell me where the users are located. Yes it was only because I had the logs was I able to do this analysis. The issue is not over these sort of analyses which I am sure nobody would object to, but that GDPR casts such a wide net.
- e12e 9y agoYou implied you already had "local" servers - it sounded like bandwidth/load information might indicate the area were load was increasing.
- danieltillett 9y agoLocal to the market - actually they are regional. The complication is that I have a client-based fallover where when one server becomes overloaded the client is switched automatically over to a different server (client based load balancing). This make it hard to sort out where the load is coming from without looking at the IP address.