Thanks for this video Dave. There’s two types of logging you can do. One is based on debugging to find out the root cause of exceptions. The other is for audit purposes. For the later, it might be required that you log parameters on collections so that you can do operational tracking on transactions. What we do in our production environnement is to log what we need to log, but then at the end of the process, we export the logs to a network drive. We also have a process that runs daily which cleans the logging in the environnement and keeps only two months of logs. We always have the exported logs to go back to if auditors ask questions.
Thanks for this video Dave.
There’s two types of logging you can do. One is based on debugging to find out the root cause of exceptions. The other is for audit purposes. For the later, it might be required that you log parameters on collections so that you can do operational tracking on transactions.
What we do in our production environnement is to log what we need to log, but then at the end of the process, we export the logs to a network drive. We also have a process that runs daily which cleans the logging in the environnement and keeps only two months of logs. We always have the exported logs to go back to if auditors ask questions.
@@gatesv1326 We do similar where we keep only session logs in blue prism for the last 90 days and the rest gets archived out into files.