Is your feature request related to a problem? Please describe.
Some time ago, in an effort to identify users with too many docs, we added the replication-count log (#6251). However, this has a severe limitation where it requires the replication request to succeed in order to log anything.
This means that the largest most broken users that can never log in are never captured, and these were the ones we were trying to detect and guard.
Describe the solution you'd like
This work should be expanded to also log failed replications. We will not know the number of documents, but we might know some data that can be useful for troubleshooting.
Additional context
Seeing replication-count logs with 500.000 users, which means that at least one request succeeded.
Is your feature request related to a problem? Please describe.
Some time ago, in an effort to identify users with too many docs, we added the
replication-countlog (#6251). However, this has a severe limitation where it requires the replication request to succeed in order to log anything.This means that the largest most broken users that can never log in are never captured, and these were the ones we were trying to detect and guard.
Describe the solution you'd like
This work should be expanded to also log failed replications. We will not know the number of documents, but we might know some data that can be useful for troubleshooting.
Additional context
Seeing replication-count logs with 500.000 users, which means that at least one request succeeded.