<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Hi Graeme - thanks for the in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/Specify-logging-requirement-at-Run-Time/m-p/54893#M9313</link>
    <description>Hi Graeme - thanks for the good suggestion. You can also affect logging at machine level in System &amp;gt; Resources &amp;gt; Management &amp;gt; right click
And yes, logging can slow you down (round trips to the DB) and you should always consider the amount, usefulness and sensitivity of data recorded in logs. As I'm sure you know, full logging can create a lot of junk and give you compliance problems. It's worthwhile making logging part of the solution design agreed by all parties. Ditto the overarching archiving policy.
John</description>
    <pubDate>Thu, 30 Nov 2017 18:31:00 GMT</pubDate>
    <dc:creator>John__Carter</dc:creator>
    <dc:date>2017-11-30T18:31:00Z</dc:date>
    <item>
      <title>Specify logging requirement at 'Run Time'</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Specify-logging-requirement-at-Run-Time/m-p/54892#M9312</link>
      <description>Would be good if you could specify what logging is required at execution time. I'm thinking you would specify it like a start-up variable and the options would be:

Disable        - No logging is done at all
Enable All    - Everything is logged
Enable         - Same as currently happens i.e. logging is done as specified on each stage/action
Errors Only  - Stages/Actions would only log in an error scenario
Default         - Use default logging setting for each stage/action, which are specified in the System Settings (i.e. you may want Start, End to be enabled, all others to be Errors only)

This would mean you wouldn't need to amend the process/objects, just to stop it logging.

We've found that having logging on makes the process run so much slower.</description>
      <pubDate>Thu, 30 Nov 2017 13:24:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Specify-logging-requirement-at-Run-Time/m-p/54892#M9312</guid>
      <dc:creator>Graeme__Tacon</dc:creator>
      <dc:date>2017-11-30T13:24:00Z</dc:date>
    </item>
    <item>
      <title>Hi Graeme - thanks for the</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Specify-logging-requirement-at-Run-Time/m-p/54893#M9313</link>
      <description>Hi Graeme - thanks for the good suggestion. You can also affect logging at machine level in System &amp;gt; Resources &amp;gt; Management &amp;gt; right click
And yes, logging can slow you down (round trips to the DB) and you should always consider the amount, usefulness and sensitivity of data recorded in logs. As I'm sure you know, full logging can create a lot of junk and give you compliance problems. It's worthwhile making logging part of the solution design agreed by all parties. Ditto the overarching archiving policy.
John</description>
      <pubDate>Thu, 30 Nov 2017 18:31:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Specify-logging-requirement-at-Run-Time/m-p/54893#M9313</guid>
      <dc:creator>John__Carter</dc:creator>
      <dc:date>2017-11-30T18:31:00Z</dc:date>
    </item>
  </channel>
</rss>

