The logging of a profile job can be done in a separate log pool. Very login-intensive profiles, for example, can use their own log pool. By default, the log pool STANDARD is assigned to a profile. You can then select a specific log pool in the Control Center to view those logs. More log pools can be added via the context menu.
Settings
(1) Name: The name of the log pool.
(2) Retain time: The retention period of the logs (in table dw_log_sum) in days for this log pool. NOTE The value -1 is allowed. In that case, the default value from parameter retainDaysForStatistic in configuration file ./etc/startup.xml is used at runtime. See also: Retention periods of backup files, logs, crashed jobs.
(3) DataCockpit/Portal replication: Defines whether the logs of this log pool should also be replicated for the DataCockpit module (and therefore be visible there).
(4) Burger menu: More options and CSV export.
Configuration file
Alternatively, you can manually create an additional log pool in the configuration file ./etc/startup.xml.
<Call name="addApplication">
<Arg>
<New class="com.ebd.hub.datawizard.app.DataWizardSetup">
<Call name="setConfiguration">
<Arg>
<New class="com.ebd.hub.datawizard.app.DataWizard">
...
...
<!-- Sample for log pools: STANDARD is always created,
add another pool 'Bulk ' with retain days of 1, no replication for Web Monitor,
pool 'Webmonitor' with 10 days and replication for Web Monitor
pool 'Support' with 30 days, no replication for Web Monitor -->
<Call name="addLogPool">
<Arg>Bulk</Arg>
<Arg type="int">1</Arg>
<Arg type="boolean">false</Arg>
</Call>
<Call name="addLogPool">
<Arg>Webmonitor</Arg>
<Arg type="int">10</Arg>
<Arg type="boolean">true</Arg>
</Call>
<Call name="addLogPool">
<Arg>Support</Arg>
<Arg type="int">30</Arg>
<Arg type="boolean">false</Arg>
</Call>
...
...
</New>
</Arg>
</Call>
</New>
</Arg>
</Call>