<?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 BP Process Log size in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/BP-Process-Log-size/m-p/80044#M31834</link>
    <description>Some of the process logs are clogging the database in production environment and it is becoming painful job to clean up those logs for creating DB space. We are looking for a way to get statistics around log size of each process execution to identify processes contributing to this issue.&amp;nbsp;

Are there any DB (log) queries (SQL) available to find the log data size at the process level?</description>
    <pubDate>Tue, 05 Jun 2018 01:17:00 GMT</pubDate>
    <dc:creator>Prabhakara_Kuma</dc:creator>
    <dc:date>2018-06-05T01:17:00Z</dc:date>
    <item>
      <title>BP Process Log size</title>
      <link>https://community.blueprism.com/t5/Product-Forum/BP-Process-Log-size/m-p/80044#M31834</link>
      <description>Some of the process logs are clogging the database in production environment and it is becoming painful job to clean up those logs for creating DB space. We are looking for a way to get statistics around log size of each process execution to identify processes contributing to this issue.&amp;nbsp;

Are there any DB (log) queries (SQL) available to find the log data size at the process level?</description>
      <pubDate>Tue, 05 Jun 2018 01:17:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/BP-Process-Log-size/m-p/80044#M31834</guid>
      <dc:creator>Prabhakara_Kuma</dc:creator>
      <dc:date>2018-06-05T01:17:00Z</dc:date>
    </item>
    <item>
      <title>Logs will almost always form…</title>
      <link>https://community.blueprism.com/t5/Product-Forum/BP-Process-Log-size/m-p/80045#M31835</link>
      <description>Logs will almost always form the bulk of a BP DB and it's vital to have logging and archiving policies to control DB growth. Ideally you want to arrive at a logging level that provides&amp;nbsp;a level of audit&amp;nbsp;but not so much that storage becomes a burden. It's also a good idea to avoid very long running sessions (&amp;gt;24h) so as not to create huge individual session logs that become difficult to archive. Logs are grouped by session, and sessions are recorded in the BPASession table.
&lt;A href="https://portal.blueprism.com/documents/logging-best-practice" target="test_blank"&gt;https://portal.blueprism.com/documents/logging-best-practice&lt;/A&gt;
&lt;A href="https://portal.blueprism.com/documents/logging-configuration-policy-template" target="test_blank"&gt;https://portal.blueprism.com/documents/logging-configuration-policy-template&lt;/A&gt;
&lt;A href="https://portal.blueprism.com/documents/archive-and-backup-policy" target="test_blank"&gt;https://portal.blueprism.com/documents/archive-and-backup-policy&lt;/A&gt;</description>
      <pubDate>Tue, 05 Jun 2018 13:27:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/BP-Process-Log-size/m-p/80045#M31835</guid>
      <dc:creator>John__Carter</dc:creator>
      <dc:date>2018-06-05T13:27:00Z</dc:date>
    </item>
  </channel>
</rss>

