In order to make complete RCA determinations we require logs from the culprit - the node that encountered or triggered the issue. When the Operator behaves correctly it removes the culprit, replacing it with a clean, healthy node. In such circumstances the logs from removed node are unattainable which inhibits our ability to fully understand and explain the sequence of events.
Is there a method (perhaps a feature enhancement or best practice configuration) that will allow end-users to capture these logs so we can perform full RCA in these circumstances.
Clearly there are circumstances where the node was removed because it truly vanished - but there are other circumstances where a node may be considered unhealthy enough to remove but still able to perform a cbcollect.