The audit log behavior on startup of the mongos or mongod is as such. Assume the audit log file specified through the server parameters is audit.log. If a file called audit.log exists in the directory, the node should move the existing file to a file called audit.log_

is the current time. If a file does not exist on startup, the node should create the file.

However, the behavior observed in BF-22988 is that when the file does not exist, the node creates a file, rotates it to the name audit.log_

, and then creates a new file audit.log and starts writing to this file. This causes unnecessary file clutter in a user's directory, so we should fix this behavior.