You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Historically, we included resident size as a billing metric. This is not actually used in billing, but was consumed by some other systems (admin console https://github.com/neondatabase/cloud/issues/15821, and some business analytics).
It has been inaccurate since we rolled out sharding, since it only reflects the resident size of shard zero.
Since the total resident size of a tenant is already available via our collective prometheus output, let's remove this from what we send in billing metrics.
The text was updated successfully, but these errors were encountered:
Related:
Historically, we included resident size as a billing metric. This is not actually used in billing, but was consumed by some other systems (admin console https://github.com/neondatabase/cloud/issues/15821, and some business analytics).
It has been inaccurate since we rolled out sharding, since it only reflects the resident size of shard zero.
Since the total resident size of a tenant is already available via our collective prometheus output, let's remove this from what we send in billing metrics.
The text was updated successfully, but these errors were encountered: