Log File Management

[PaulTMS]

Here is the proposal to have the services manage the log files for the service and for operator actions. Please identify and add those features discussed but not included here.

1) add a path to the INI file to point to the service archive folder 2) add a lifetime duration (days to live) parameter for service log files (30 days) 3) add a lifetime duration (days to live) parameter for operator log files (2555 days) 4) once/day write service log to the local service log folder. Delete expired files. 5) once/day write operator log to the local operator log folder. a) write operator log to the service archive folder as read-only. b) delete expired files in the local folder IFF the file exists in the archive folder. 6) Once / year, manually delete operator log files from the archive and submit record destruction paperwork.

In this way, TMS will have access to a small number of files (managed by the service, not some human) and the file archive will have a complete set of files (managed by some human for destruction& restoration as needed). TMS operations will be more self-reliant and more consistent across the regions.

Here is a list of the operator log files that are covered by this proposal:

ATM_OPER_YYYYmmDD.log AUTH_OPER_YYYYmmDD.log CAMOPER YYYYmmDD.log NG_ContactOperator YYYYmmDD.log GCOPER YYYYmmDD.log RMDCOPER YYYYmmDD.log HARSOPER YYYYmmDD.log CLIENTOPER YYYYmmDD.log SERVEROPER YYYYmmDD.log NGINCOPER YYYYmmDD.log Operator_ YYYYmmDD.log VMSOPER YYYYmmDD.log Weather_Operator_YYYY-mm-DD.log

Service log files are all the other log files created by the service that do not have long term value.

[PaulTMS]

Duplicate

[PaulTMS]

Run this by records retention. Service and device comm log are transistory. Talk to Dave Richards how log retention is handled.

[PaulTMS]

Email notification of logs ready to be destroyed