Database Reference
In-Depth Information
•
Development:
Both composite instance and payload information are collec-
ted. Though this option provides the most detail, it is the worst performing
of all the audit levels. It is recommended to set this in development environ-
ments for debugging purposes, but not in production environments, except
for transactions that specifically require that degree of auditing.
•
Production:
Although composite instance information is collected, most
payload details are not. This is the typical setting for production environ-
ments and provides the best balance between performance and visibility. If
payload details need to be captured, it is best to consider setting the audit
level to
development
only for specific composites, components, or ser-
vices, as we shall describe later.
•
Inherit:
Audit levels are inherited from the parent level (we will describe this
shortly).
To view the instance details, you should click on the composite on the navigator
on the left, click on the
Instances
tab, then click on the instance ID. A pop-up
window will reveal the details of this instance, including the audit trails. The fol-
lowing screenshots show the difference between the
development
and
pro-
duction
audit levels:
