The audit log for Microsoft® Provisioning Framework (MPF) contains a user-defined subset of transaction data that is stored for data mining, error checking, and other reporting and analysis purposes. For example, data on failed transactions, failed procedures, and execution times is often used for performance analysis.
MPF setup installs the audit log. An MPF installation can have only one audit log database.
The audit log receives transaction data from transaction logs via the auditing and recovery manager service. Since the number of transactions in a data center can become very large, logging all information about every transaction, procedure, and error would require excessively large databases. Using Provisioning Manager, you can reduce the size of the databases by specifying which information to save to the audit log, limiting it to only the required information. The Audit Level property in Provisioning Servers, Provisioning Engines determines which transactions are saved to the audit log and what kinds of data to pass for these transactions. For more information, see Provisioning Engines.
Depending on the reporting purpose, it may be necessary to modify the audit log database. To add rows of data to the database or execute custom stored procedures, use Custom Audit::Audit.
Top of Page
© 1999-2002 Microsoft Corporation. All rights reserved.