Overview of Logging
To effectively manage the CentraSite registry/repository, it is necessary to get feedback about the activity and performance of the registry/repository. The CentraSite registry/repository provides comprehensive and flexible logging functionality for tracking design/change-time and run-time events in CentraSite Control. CentraSite stores the log and monitoring data of all registry objects (for example, policies, assets, and so on) as log records in the CentraSite Log Database.
As your logs grow, you may want to purge log records to avoid performance degradation. CentraSite provides the ability to purge log records and back them up to another location. You can purge log records manually (on demand) or automatically on a scheduled basis.
By understanding and using the log files, you can:
Gather and Analyze
Run-time performance data posted by a gateway (that is, a policy enforcement point (PEP) or a run-time monitoring component such as Insight).
Run-time event data (transaction events, policy violation events, and so on) posted by a gateway.
Approval history data.
Design/change-time policy data.
Audit data.
Federation job queue data.
Consumer Registration data.
Troubleshoot Problems
For example, if your CentraSite needs to add more disk storage due to an increase in the number of assets, you can use Audit log files to see what percentage the asset activities has increased by and plan for the amount of new disk storage you need.
