How does message routing work?
Behind the scenes, each
FactoryTalk
product and service categorizes the messages that it generates using a matrix of severity
options (Error, Warning, Information, and Audit) together with audience
options (Operator, Engineer, Developer, and Secure). For example, a product might generate a series of security messages classified as Operator-Audit and Operator-Information, and also generate a series of communication messages classified as Operator-Warning, Engineer-Warning, and Developer-Error.Routing messages from multiple products
Multiple
FactoryTalk
products may be routing messages to the same log on a single computer. For example, FactoryTalk View SE
and FactoryTalk Alarms and Events
might both be sending messages to the Local Log on your computer. Use these options, presented in the Message categories
matrix, to filter the types of messages you want to send to each logging destination on this computer.For example, to zero in on a problem, a plant manager might configure the Local Log on his computer to log only "Error" and "Warning" messages and ignore "Information" and "Audit" messages. On another computer, an automation system developer might want to configure the Local Log to log only messages categorized as "Engineer" messages.
Message categories
The definitions below, with the exception of "Secure," are only suggestions. Each
FactoryTalk
product and service classifies its own set of messages and defines the meaning of the options to fit its own purposes. The "Secure" category of messages is reserved for audit messages that are logged by the FactoryTalk AssetCentre
software.Audience options:
Audience | Description |
|---|---|
Operator | Typically, this option is assigned to messages that confirm the success or failure of an action initiated by people who are operating or using the FactoryTalk product or service. |
Engineer | Typically, this option is assigned to messages useful to control system designers, application engineers, and administrators for testing and troubleshooting FactoryTalk products and services. |
Developer | Typically, this option is assigned to messages useful to systems software developers for testing and troubleshooting software components and subsystems. |
Secure | Reserved for messages which need to be protected and retained based on
specifications for storing electronic records, such as US FDA 21 CFR Part 11. |
Severity options:
Severity | Description |
|---|---|
Error | Typically, this option is assigned to the most serious kind of error message, triggered by significant problems. |
Warning | Typically, this option is assigned to messages triggered by problems that are not necessarily critical, but which may cause future problems. |
Information | Typically, this option is assigned to messages that document the essential purpose of the FactoryTalk product or service, and which supplement and add more detail to "Audit" messages. |
Audit | Typically, this option is assigned to messages that indicate user activities
which are essential to the technology or purpose of the product or service. Note
that, Audit messages with this severity are not generated if the audit policy
called "Audit changes to configuration and control system" is disabled. Use
FactoryTalk Administration Console to configure audit policies. |
Beginning with FactoryTalk Services Platform version 6.50.00, these messages with the
Secure audience and Audit severity can be routed to:
- FactoryTalk AssetCentre log
- An ODBC database
- A Syslog Collector
Accept messages from Windows CE devices
If
FactoryTalk Diagnostics
support for Microsoft
Windows
CE devices is installed on your computer, configure each logging destination to either accept or not accept CE-based messages. To accept CE-based messages, select the check box.Provide Feedback