As a pod provider I'd like to see aggregated histories of access attempts to pods I host so that I can manage hotspots, charge per usage, prevent DoS attacks, etc.

[pmcb55]

This may raise issues of privacy (e.g. for individual pod owners), but I think this needs to be balanced with the legitimate needs of the pod provider to effectively manage the infrastructure they provide for pod hosting (hence I mention in the title the possibly of the provider only having 'aggregated histories' of access, and perhaps not the level of detail that the individual pod owners may have). Perhaps a pod provider could offer differing levels of infrastructure support to pod owners based on the degree of visibility the pod owner consents to provide to the pod-hosting provider. #11

[dsebastien]

I imagine that there could be different granularity levels for such a feature. A pod provider could be interested in how much traffic there is towards a specific pod, without necessarily implying visibility over which part of the pod / content is being requested/accessed.

I feel like for the most part, the contents of the pod and who accessed what should remain a black box to the provider.

I think that we can observe how big cloud providers deal with private networks and private storage on AWS and the like and take inspiration from that. They provide high confidence to their clients into the fact that they can't/won't access the data.

In addition, to me, this kind of "observability" feature could be enabled by integrating event sourcing right into solid, as I've proposed in #22. I'll post an update there to provide some more ideas around that.

[Mitzi-Laszlo]

added to readme

[megoth]

Opening this as part of moving all user stories into issues again.