How to Control SharePoint Auditing
Auditing is primarily controlled at the site collection (you can also customize
auditing for specific libraries and lists).
In native SharePoint, there is no way to define a farm-wide audit policy and you
must remember to configure audit policy each time new site collection is created
which can especially be an issue in self- service site creations scenarios. (LOGbinder for SharePoint
allows you to define a default audit policy
for the entire site which applies to all site collections, including new ones, until
and if you configure a site specific audit policy.)
To enable auditing you must be a site collection administrator. From the Site Settings
page, look under Site Collection Administration, as pictured here, for “Site collection
audit settings”.
That link displays the page you see to the right where you can configure
audit log trimming, and more to the point, the audit policy for the site collection.
Once you enable auditing, SharePoint will begin logging events to the
internal SharePoint audit log.
The audit policies defined here apply to all objects in the entire site collection
so be careful what you enable. In particular, auditing view access at the site collection
level will generate a large amount of audit events including 1 to 2 events for every
page view. Learn how to
enable auditing on specific libraries or lists.
The check boxes shown above do not correspond directly to the more granular audit
flags exposed programmatically through the SharePoint object model.
LOGbinder for SharePoint
allows you to configure auditing at this more granular level. The table below maps
the check boxes provided by SharePoint site collection administration to the actual
audit flags inside SharePoint and exposed by
LOGbinder for SharePoint.