Logging

Every operation performed via Adaxes service is logged. No matter whether an operation involves an Active Directory object, such as a user or group, or an Adaxes configuration object, such as a Business Rule or a Property Pattern, Adaxes will create a log record containing detailed information about the event: what was done, by whom and when. Operations performed by Adaxes service itself are also logged. For example, actions performed as a part of a Business Rule triggered by an operation will be logged additionally in separate log records.

Log records created by Adaxes are logically grouped into the following logs:

General Log: contains all operations performed via Adaxes.
Management History: contains a log of operations performed on a specific object.
Management Activity: contains a log of operations performed by a specific user.
Activity History: contains a log of operations performed by a Scheduled Task.

To be able to view logs, users need to be granted appropriate permissions. For details, see Permissions to View Logs

Where are Log Records Stored?

By default, Adaxes stores log records in a built-in SQLite database located on the computer where Adaxes service is installed. Alternatively, you can configure Adaxes to store log records in an external Microsoft SQL Server database. For more information, see Database for Logging.

What Can I Configure?

To avoid unnecessary logging and reduce the size of the logging database, you can configure Adaxes to log only the operations you need. For example, if you don't want a log message to be created each time an e-mail or SMS message is sent via Adaxes, you can exclude the Send e-mail notification and Send SMS operations from logging. You can also exclude from logging certain types of objects operations on which you don't want to trace.

By default, log records are kept in the local log database only for 30 days. The period can be customized to cover an interval long enough as required by your company's audit and security policies.

What Information Does a Log Record Contain?

A record of each operation performed via Adaxes service contains the following information:

Information	Description
Operation	General description of the operation.
Initiator	The person who performed the operation.
Initiator Host	The host from which the operation was performed. For operations performed via Adaxes Web Interface, Initiator Host contains the host where the Web interface is installed.
Start/Complete Time	The time when the execution of the operation was started/completed.
Target Object	The object on which the operation was performed.
Operation Type(s)	The type of the operation that the log record represents. For example, when an object is created, the operation type will be create. Some log records represent multiple operation types. For instance, when an object is renamed, the operation types will be rename and set properties. List of possible operation types *.
Operation Sender	The type of the operation initiator: Client - the operation was initiated by a user. Server - the operation was initiated by Adaxes service as a part of a Business Rule, Custom Command or Scheduled Task.
Operation State	Failed - the operation execution failed. Completed - the operation was successfully executed. Suspended - the operation execution was delayed, for example, because it awaits for an approval.
Operation Execution Log	Contains errors, warnings and information messages generated by the operation, and also actions executed by Business Rules. For more information, see Execution Log.