How to set logging levels for different environments running Blue Prism processes
How to set logging levels for different environments running Blue Prism processes
It is recommended that logging levels be set in accordance with the environment in which the Processes and Objects will be running.
In a Development and Testing environment the logging level may be set quite high, as it would be expected that issues would need to be surfaced and then dealt with in such environments. In a User Acceptance Test or Production environment the logging levels would be significantly reduced such that they captured only errors and record key stages of the Process.
Blue Prism session logging can generate a very large amount of data in the Session Log table. When preparing a Process for use in a Production environment best practice is to do the following:
- Turn off as much logging in your process as possible
- Only leave enough logging turned on to be able to easily trace the route each case worked has taken through your process flow.
- Logging is usually left turned on for Decision and Choice stages.
- Turn off any logging on Stages that use customer data. It is important that customer data is not stored in session logs.
- Turn off logging anywhere that might generate large amounts of log data. Look for:-
- Loops which use large data sets
- Stages with lots of input or output parameters
NOTE: Collection data items are typically large and their results and parameters will be logged.
See this document for more guidance on Process Design best practise advice: 'Guide to Creating a Blue Prism Process'..
It's really a nice experience to read your post. Thank you for sharing this useful information. If you are looking for more about rpa training in chennai
ReplyDelete