Description
As we roadmap enhancements for s3parq it will be killer to have real anon statistics of how the package is actually used. To catch this, we want an anon external logging handler that pipes to a central data store.
Defs of Done:
- opt-in / out via config file in the root
- points to some storage somewhere... s3? or other? need to decide who and where.
- 100% anon statistics, maybe allow the source and a contact to be opt-in provided
- data types, df shapes, partition sizes, run times with run time details
-error logging with scrubbed stack traces?
Description
As we roadmap enhancements for s3parq it will be killer to have real anon statistics of how the package is actually used. To catch this, we want an anon external logging handler that pipes to a central data store.
Defs of Done:
-error logging with scrubbed stack traces?