Intelligent Management: binary trace facility custom properties

You can modify trace dynamically and persistently by setting a cell custom property.

Set cell custom property with the following form for name and value:

Table 1. Trace custom property with cell scope
Value	Description
Scope	Cell
Name	trace.<scopeName>
Valid values	[<condition>;;;]<traceSpec>

Examples of changing trace dynamically

You can modify trace dynamically and persistently by setting a cell custom property. For example, to trace HTTP affinity processing and load balancing, use the following settings:

Table 2. Trace HTTP affinity processing and load balancing
Value	Description
Scope	Cell
Name	trace.http
Valid values	http.request.affinity,http.request.loadBalance

Or, to trace server weight changes (which are traced by default), specify the following settings:

Table 3. Trace server weight changes
Value	Description
Scope	Cell
Name	trace.ODCEvent
Valid values	propertyType = 'server:weight';;;ODC.event

The ODC language supports a nodeType operand, propertyType operand which returns <nodeTypeName>:<propertyName>, and edgeType operand which returns <parentNodeType>:<childNodeType>. All ODC events are in the group ODC.event, so as long as they pass the condition test, they will be traced.

To enable all HTTP trace except load balancing, turn on all HTTP trace, then turn off http.request.loadBalance trace with a trace level of 0, as shown in the following table:

Table 4. Trace HTTP without load balancing
Value	Description
Scope	Cell
Name	trace.http
Valid values	http,http.request.loadBalance=0

To trace all SIP messages that take longer than 100 milliseconds to be processed by the on demand router (ODR), specify the following settings:

Table 5. Trace SIP messages that take longer than 100 milliseconds to process
Value	Description
Scope	Cell
Name	trace.sip
Valid values	sip.message.slow=100

Specifying these settings traces all SIP messages that take longer than 100 milliseconds to be processed by the ODR. Note that in this case, the trace level field is used as a time threshold field that controls when the message is traced. The record description describes how the level value is used in this case: A SIP message took longer than the level (in milliseconds) to be processed by the ODR. The default level is 300. Record descriptions should be clear in describing how the level is used and what each level means for the record.