Previous Topic: Replication SettingsNext Topic: External Logging Settings


Logging Settings

CA DataMinder maintains logs for all product components to record significant activity or events. For log files controlled or generated by the CA DataMinder infrastructure, machine policy settings control which infrastructure operations are logged.

General Log Configuration

You can edit these settings in the Infrastructure > Logging policy folder:

Maximum Number of Log Files

Specifies the maximum number of log files. This limit applies separately to each type of log (that is, for each type of logfile you can generate files up to the maximum number). When this maximum number is exceeded, the oldest log file is deleted.

Maximum Size of Log Files

Specifies the maximum size (in KB) for each log file. When the current log file reaches its maximum size, CA DataMinder creates a new log file.

Note that this size limit does not apply to Account Import log files.

Write to Windows Event Log

Specifies the default handling for copying CA DataMinder log entries to the Windows Application log.

Write to Syslog Server

Specifies the default handling for copying CA DataMinder log entries to a Syslog server such as ArcSight.

Activity Log Configuration

In the Infrastructure > Logging  > Activity subfolder, you can optionally record the following activities:

Machine and User Logins

You can record login and logout times and, for user logins, you can also record failed account creation attempts.

Machine and User Administration Changes

These changes include accounts being created, modified or deleted. You can also record this information in the User Administration log file.

Policy Changes

These include any saved changes to user or machine policies.

Cache Actions

These include cache changing and purge activity involving the temporary object store, and plus cache preload and clear down operations associated with the internal user cache and e-mail address cache (used to optimize event processing).

Storage Connector Events

These refer to events associated with third party object stores. CA DataMinder uses storage connectors to integrate with third party object storage solutions. The range of logged events includes object store connections and disconnections, storage queue activity and data retrieval.

Policy Incident Log Configuration

(Only available in the CMS machine policy.)

These logs are created on the CMS only. In the Infrastructure > Logging > Policy Incidents subfolder, you can optionally record the outcome each time a user policy trigger fires. The log includes both event-level and trigger-level entries. Edit these settings:

Log Policy Incidents Locally To File

If enabled, CA DataMinder writes entries to the policy incident log on the CMS.

iConsole Address

Set this to the fully qualified domain name or IP address of a machine hosting the iConsole application server. For example:

CMS-HARDY.unipraxis.com

This address is incorporated into the event URL in each log entry (see below). Administrators can browse to this URL to view the associated incident in an iConsole.

Format of Event URL

You do not normally need to edit this policy setting. It specifies the format of the event URL included in the log message. Users can browse to this URL to view the event in the iConsole.

Replication Log Configuration

In the Infrastructure > Logging  > Replication subfolder, you can optionally record when a CA DataMinder machine receives replicated data. In all cases, you can choose to record summary information (when replication starts and completes, and how many objects were successfully replicated) or you can record detailed information (log entries for each successfully replicated object). Edit these settings:

Captured Data

This can include captured or imported e-mails, Web pages, IM events, file events, and so on, plus any associated trigger details, event attributes, and policy actions.

Infrastructure Data

This includes changes to user and machine accounts or policy updates.

Critical Data

This typically includes data recorded for diagnostic purposes. For example, when a machine becomes suspended a notification is replicated to the CMS.

System Log Configuration

In the Infrastructure, Logging, System subfolder, you can optionally record any infrastructure errors while the CA DataMinder service is running. Under normal conditions, this log is empty.

Note: Any errors detected when the CA DataMinder service starts up are written to the file wgninfra.out. Find this file in the same folder as the System log.

User Administration Log Configuration

In the Infrastructure, Logging, User Administration subfolder, you can optionally record changes made to user accounts or groups. You can also record these changes in the Activity log; see above.

External Logging

Settings in the Infrastructure, Logging, External Logging subfolder enable CA DataMinder to copy log entries to the local Windows Application log and to Syslog servers.

More information:

Overview

External Logging Settings