Locate logs/events of Management of Change (MoC) data changes
- Last UpdatedApr 24, 2025
- 2 minute read
Management of Change (MoC) data changes are logged according to the logging activity and available logging mechanism.
Note: If MoC is enabled when any process modifies configuration fields without supplying a changeset, the untracked configuration changes will be logged in a process-specific log and stored by the MOCOrchestrator service. Process logs are written at the warning level. Use the toggleDebug utility to raise the default logging level of a process. For more information related to the toggleDebug utility, refer to the RealTime Administrator documentation.
The following table outlines the type and location of logs/events for the MoC data changes audit trail:
|
MoC Component |
Log/Event Type |
Log/Event Location |
|---|---|---|
|
DNAChangeset Tool |
The DNAChangeset command line tool errors. |
These errors are output to the command line interface. |
|
Errors related to connecting with the RealTime database (RTDB) or display database. |
These errors are located in the oasErrLog.log file in the %DNADataRoot%\Shared\log folder of the system where the DNAChangeset tool is run. |
|
|
DNAPackage Tool |
The DNAPackage command line tool errors. |
These errors are output to the command line interface. |
|
Auditing events related to the management of packages. |
These events are located in the AuditLogEntries table of the ManagementOfChange Database centrally located on the Orchestrator. |
|
|
Errors related to connecting to the package store. |
These errors are located in the oasErrLog.log file in the %DNADataRoot%\Shared\log folder of the system where the DNAPackage Tool is run. |
|
|
AVEVA Workflow Management |
AVEVA Workflow Management has the ability for the user to configure workflow notifications. |
For more information, refer to "Notification Activity" in the AVEVA Workflow Management documentation. |
|
AVEVA Workflow Management includes business monitoring and reports in the Enterprise Console. |
For more information, refer to "Business Activity Monitoring and Reports" in the AVEVA Workflow Management documentation. |
|
|
AVEVA Workflow Management log files are located in the <Install Drive>:\Program Files\Wonderware\Workflow Management\Logs folder on the system where AVEVA Workflow Management is installed. |
For more information, refer to "Viewing Message Log Files" in the AVEVA Workflow Management documentation. |
|
|
RTDB Changeset |
Auditing events related to the installation or rolling back of individual changesets. |
These events are located in the AuditLogEntries table of the ManagementOfChange Database centrally located on the Orchestratror. |
|
Errors encountered during the installation or creation of RTDB (realtime) changesets. |
These errors are located in the oasErrLog.log file in the %DNADataRoot%\Shared\log folder of the system where realtime changesets are being created or installed. |
|
|
MOCAgent service |
Errors encountered during the installation or creation of realtime changesets. |
These errors are located in the oasErrLog.log file in the %DNADataRoot%\Shared\log folder of the system where the MOCAgent service is being run. |
|
MOCOrchestrator service |
Errors related to the operation of the package store. |
These errors are located in the oasErrLog.log file in the %DNADataRoot%\Shared\log folder of the system running the MOCOrchestrator service. |
|
Additional data. |
Additional data is located in the packagestore_<processID>.log file in the %DNADataRoot%\ManagementOfChange\log folder of the system running the MOCOrchestrator service. |
|
|
RabbitMQ |
Status information of the RabbitMQ instance. |
The status information is located in the RabbitMQ management console. For more information, refer to RabbitMQ documentation at https://www.rabbitmq.com/documentation.html. |
|
User configurable RabbitMQ log files. |
Log files are available through the management console. For more information, refer to RabbitMQ documentation at https://www.rabbitmq.com/documentation.html. |