Auditing Levels
ActiveMatrix BPM enables you to configure which of the messages produced by the system are audited: that is, which messages are collected and stored centrally by the Event Collector component.
For more information about levels of auditing, see the section about configuring ActiveMatrix BPM auditing in the TIBCO ActiveMatrix BPM Administration guide.
Setting up full auditing will of course mean that many more messages are collected centrally than if you use the default lesser level of auditing provided, with correspondingly more use of system resources. The section about editing the event probe rules file (ec-probe-rules.xml) in the TIBCO ActiveMatrix BPM Administration guide describes how you can tailor the level of auditing to include or exclude individual message IDs. If your monitoring of the system shows that the volume of audit messages is causing a problem, you could try excluding more message IDs. Note that:
- The use of system resources is governed by the number of messages that are audited, not by the number of message IDs listed. One message type that is generated frequently may cause more traffic than a list of a dozen rarely-used types.
- Some messages occur in pairs, one saying that an activity has started, the other saying that it has finished. For example:
- DAC_COMPONENT_ENT_START — Starting Deadline and Calendar
- DAC_COMPONENT_EX_START — Deadline and Calendar Started
The first message indicates that a Start operation is beginning, the second that it has been carried out.
In some cases, you might find it useful to exclude the first message of such a pair, thus reducing the number of messages but still being informed when the operation has taken place.