Publish details about ZKAP over-spending. For example, a 1 MiB-month ZKAP may be spent for a 512 KiB file. Reflect this in the metric somehow. Consider breaking this down, also, by size as with the raw numbers.

[exarkun]

No description provided.

[exarkun]

One thing we could do here is count the number of bytes clients could have uploaded with the ZKAPs they spent but didn't.

Another thing we could do is make this a gauge that counts up for the above reason and down when more storage is allocated by mutable operations in such a way as to cause more ZKAP value to be consumed.

It would be good if the unit on this counter/gauge were storage-time. Maybe that's straightforward? Alternatively, we could forget about this metric entirely and just fix the accounting system so there isn't overspending.

[hacklschorsch]

@exarkun and me one a videocall right now: This can wait until we have a good idea for a metric to capture this. Preferred way would be to solve overspending altogether instead.