Issue Summary

When audit logging silently fails and stops running, there is an "AuditLogSaveThread" logged out to the Bamboo Server log as denotehd in bug ticket BAM-18855 – Improve audit log handling code but nothing else explicitly indicates this error.

Expected or Wished Behavior

The fact that audit log is no more running in Bamboo should show up in Bamboo's healty check. By that, a Bamboo user with Admin permissions can see that, clearly written out, and already start planning for, worst case, a required restart of Bamboo Server.

It should also be possible that Bamboo adds a monitoring thread for the audit log thread and on audit thread getting killed or stuck / unresponsive for a certain amount of time (or e.g. by signal reception on the audit log thread termination not in the context of a Bamboo shutdown) possibly something like an "AuditLogRecoveryThread" could be started and automatically restart audit logging and load back the original and saved logs.

Even after a successful audit log recovery, this incidence should be logged out, e.g. to Bamboo's health check registry.

Workaround

As of the bug mentioned above, the only known workaround and thus the only measure to re-activate Bamboo's audit log is a Bamboo Server restart.