Differences between Auditing and Trace Logging

Trace settings do not determine whether auditing is performed or the amount of data that is written to the Audit table. Within the CampaignServer trace file, there is an "Audit" trace topic that affects the verbosity of audit log messages in trace logs (vwrlogs) used by Customer Care and Developers. Audit messages are written to trace logs only if the Audit trace topic is set to "Status" or higher. The trace topic level is checked when Dialer Manager is opened so that the level is not retrieved numerous times. If the trace level is too low, no audit changes are written to trace logs.

Trace settings have no effect upon Configuration Change Auditing. However, trace logs can be useful in support situations. For example, a customer can send trace logs to Customer Care, so that a representative can analyze audit information without having to query the customer's database.

For the most part, customers should concern themselves with the "Enabled" setting on the Enable Configuration Change Auditing tab page of the Global Dialer Settings view. This setting is written to the dialer_config.xml file that is shared between the different Outbound Dialer machines. Since there is only one audit setting in dialer_config.xml, Auditing is either ON or OFF for all servers. When Auditing is turned on, database entries will be generated for the audit entries, regardless of the trace levels.