[Debug]CategoryFilter

Allows you to filter the logging messages sent to the tracelog.dat file by component category.

The [Debug]CategoryFilterMode parameter indicates whether messages of the specified categories will be included or excluded from the log.

Note: By default, the setting for [Debug]CategoryFilterMode will exclude the categories specified by [Debug]CategoryFilter.

Allowable Values:

Zero or more of the following categories specified as a comma-separated string:

• AlarmClient - traces events from the display layer of the alarm client

• AlarmClientAdaptor - traces events from the adapter layer of the alarm client that marshals between the old and new alarm system

• AlarmClientComms - traces events from the client side of alarm communications

• AlarmClientModel - traces events from the model layer of the alarm client

• AlarmFilterParse - alarm filter parsing logging

• AlarmServer - traces events from the Alarm Server

• AlarmServerAdaptor - traces events from the adapter layer of the alarm server that marshals between the old and new alarm system

• AlarmServerComms - traces events from the server side of alarm communications

• AlarmServerModel - traces events from the model layer of the alarm server

• CSAToPSI - traces events from the interface between the Client-Side Adapter (CSA) and the Publisher-Subscriber Infrastructure (PSI)

• DataSource - traces setup and cache changes for data sources on the server side

• Instrumentation - traces information from the instrumentation components

• Logging - traces events from the logging subsystem

• ManagedUtil - traces information from the managed utility module

• OpcDaServerComApi - enables tracing of calls at a COM API level

• OpcDaBrowse205 - enables tracing related to OPC DA v2.05 item browsing

• OpcDaBrowse300 - enables tracing related to OPC DA v3.00 item browsing

• OpcDaServer - enables extensive tracing of OPC DA Server object APIs

• OpcDaGroup - enables extensive tracing of OPC DA Server object APIs

• PlatformHost - traces events from the Plant SCADA platform components that are hosted by runtime

• PSIClient - traces events from the client-side handling of tag requests

• PSIInterfaces - traces events from the PSI interfaces

• PSIServer - traces events from the server-side handling of tags requests

• RuntimeManager - traces events from the Runtime Manager

• TaskFramework - traces events from the framework that handles the scheduling and execution of work tasks at runtime

• TagBrowsing - traces events from the client and server handling of tag browsing requests

• Transport - traces events from the platform networking subsystem

• XmlUtils - traces information from the XML utilities module

Default Value:

Empty string, that is, no categories excluded or included depending on [Debug]CategoryFilterMode.

Example

The following setting will trace tag requests to the point where the data originates:

[DEBUG]

CategoryFilter=CSAToPSI,PSIClient,PSIServer,DataSource

CategoryFilterMode=0

When combined with the implementation of [Debug]DriverTrace, [PubSub]LogDevice and [PubSub]LogLevel, this provides a top to bottom data flow trace.

Note: You can adjust this parameter during runtime using the SetLogging() function. For more information, search the Plant SCADA Help for the topic Adjusting Logging During Runtime.

See Also

Debug Parameters