So deletion logs.. currently (without custom code) we cannot tell who deleted a document and what document they deleted in which database. With v10 deletion logging is now a standard trigger on the database that creates an entry in a delete.log file in the IBM_TECHNICAL_SUPPORT directory detailing every deletion activity.
So how does it work?
Deletion logging is enabled via the compact task on an individual database basis. The option -dl is used when compacting a database along with the fields in that database you want to be part of the log. For example if I wanted to turn it on for my mail file I might do
load compact mail\gdavis.nsf -dl on subject,posteddate,sendto,recipient
Every deletion after that point would then be logged as a single CSV entry in delete.log. Note there are standard values that are always logged in addition to the custom fields I requested
“from”,”””New Relic” –
“<email@example.com>”, “sendto”,”firstname.lastname@example.org”, “deliveredDate”,”02/10/2018 21:05:05”, “posteddate”,”02/10/2018 16:15:18″
There are several interesting aspects to this approach but I see it being particularly powerful for audit purposes, as it shows not only the message but the timestamp of the deletion and who did it. Note that the server name in the log entry here tells me my Traveler server did the deletion so it was done from my phone, if it had been deleted in the Notes client it would have my name there as the person who did the deletion.
The delete.log itself rolls over each time the server is restarted but obviously depending on the size of your environment and how widely you deploy deletion logging that’s a CSV file you are going to want to have a strategy for.
7 days and counting