Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
08-02-21 09:46 AM
find out how to check which process is creating more log in blue prism ?
Answered! Go to Answer.
1 BEST ANSWER
Helpful Answers
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
08-02-21 09:51 AM
Logs are held in the BPASessionLog_NonUnicode table, so a basic check would be to see how many rows each session created. However be mindful that all some rows can contain more data than others, eg if a row contains XML representing input/output parameters.
There is a tile called Largest Database Tables that you could inspect before and after running processes to get a feel (the tile doesn't show individual sessions) for which processes grow the table more.
It's also Best Practice to ensure that a review of logging is made part of the delivery methodology, so that no process can be implemented without its session logs being reviewed and approved. Volume is an obvious concern, but depending on the project, it may be necessary to ensure that sensitive data is not recorded in Production logs. A common approach is to reduce logging over time, eg when a process first goes live, the logging level is high in order to provide a trace while the process settles down. As the process stabilises, logging is reduced to 'comfortable minimum'.
There is a tile called Largest Database Tables that you could inspect before and after running processes to get a feel (the tile doesn't show individual sessions) for which processes grow the table more.
It's also Best Practice to ensure that a review of logging is made part of the delivery methodology, so that no process can be implemented without its session logs being reviewed and approved. Volume is an obvious concern, but depending on the project, it may be necessary to ensure that sensitive data is not recorded in Production logs. A common approach is to reduce logging over time, eg when a process first goes live, the logging level is high in order to provide a trace while the process settles down. As the process stabilises, logging is reduced to 'comfortable minimum'.
1 REPLY 1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
08-02-21 09:51 AM
Logs are held in the BPASessionLog_NonUnicode table, so a basic check would be to see how many rows each session created. However be mindful that all some rows can contain more data than others, eg if a row contains XML representing input/output parameters.
There is a tile called Largest Database Tables that you could inspect before and after running processes to get a feel (the tile doesn't show individual sessions) for which processes grow the table more.
It's also Best Practice to ensure that a review of logging is made part of the delivery methodology, so that no process can be implemented without its session logs being reviewed and approved. Volume is an obvious concern, but depending on the project, it may be necessary to ensure that sensitive data is not recorded in Production logs. A common approach is to reduce logging over time, eg when a process first goes live, the logging level is high in order to provide a trace while the process settles down. As the process stabilises, logging is reduced to 'comfortable minimum'.
There is a tile called Largest Database Tables that you could inspect before and after running processes to get a feel (the tile doesn't show individual sessions) for which processes grow the table more.
It's also Best Practice to ensure that a review of logging is made part of the delivery methodology, so that no process can be implemented without its session logs being reviewed and approved. Volume is an obvious concern, but depending on the project, it may be necessary to ensure that sensitive data is not recorded in Production logs. A common approach is to reduce logging over time, eg when a process first goes live, the logging level is high in order to provide a trace while the process settles down. As the process stabilises, logging is reduced to 'comfortable minimum'.
