Monitoring
The Monitoring section in the MDM Web App Admin Center allows you to:
-
Browse the details of task execution, event publishing, and load operations.
-
Download logs related to the database and database configuration.
-
Change several logging settings.
Task Execution
Displays a list of all running, queued, and finished data processing actions, including user actions.
From here you can cancel or stop a task, or view task details. For task details, select the task ID or View Detail.
Cancel task
From the Task Execution tab, you can also cancel a queued task (task status WAITING).
This removes the task from the queue and updates the task status first to CANCELING and then to CANCELED.
Select Cancel, then confirm your choice when prompted.
Stop task
To stop a running task, select Stop task, then confirm your choice when prompted.
This reverts all transactions that have not yet been committed and updates the task status first to STOPPING and then to STOPPED.
In addition, it also stops any running transformation plans and database interactions related to the given task.
Task status
A task can be in one of the following states.
| Status | Description |
|---|---|
WAITING |
Waiting in the processing queue. |
RUNNING |
Currently being executed. |
FINISHED_OK |
Successfully completed. |
FINISHED_FAILURE |
Completed with a failure. |
ABORTING |
In the process of being stopped but not yet fully terminated. Occurs when high availability (HA) RW-RO mode is used. |
ABORTED |
Successfully stopped and no longer running. Occurs when high availability (HA) RW-RO mode is used. |
STOPPING |
In the process of being stopped but not yet fully terminated. |
STOPPED |
Successfully stopped and no longer running. |
CANCELING |
In the process of being canceled by a user before it could be executed. |
CANCELED |
Canceled by a user before it could be executed. |
To get a better idea of how tasks transition between different statuses, see the following diagram. The Task Result Code in the diagram represents the final status of the task, while Task Process Status refers to the status of the process that is executing the task.
Task details
The task detail screen provides further information, including the list of subtasks, their start and finish times, the number of processed records per second, and the subtask result.
From here, you can also export and save the task execution details in a single HTML file.
Select Download this page.
The file name is nme-task-report-{taskID}.html.
At the bottom of the page, you can find a list of related instances of event publishing.
Subtask result examples
| Result | Description |
|---|---|
|
Number of changed records, total number of incoming records (change detection) |
|
Number of records at the start of a task (cleanse, validate, commit) |
|
Related records processing |
|
Number of records at the start of a task + number of records affected by processing (match, aggregate, copyColumns) |
|
Number of records at the start of a task + number of records affected by processing → number of record at the end of the task (merge) |
|
Task was not executed. |
Event publishing
Displays a list of running and previously run instances of event handler publishing. For details, select the processing ID in the first column or View Detail. To view the parent task, select the Task ID.
Event publishing status
| Status | Description |
|---|---|
RECEIVING |
Receiving events from an ongoing transaction. |
READY |
Ready for publishing. |
PUBLISHING |
Ongoing publishing process. |
PUBLISHED |
Publishing is finished. |
CORRUPTED |
Temporary files are corrupted. |
CRASHED_RECEIVING |
MDM processing or Event Handler failed - temporary files will be removed. |
CRASHED_ PUBLISHING |
Publishing was not successful - when a publisher is activated, publishing continues. |
Operation Plan
Shows the order of load operations defined in the Model used as an internal workflow of the MDM engine. You can also download the operations list for using Executor by clicking the link at the top of the page.
Column description:
-
Operation: Name of the operation.
-
Provides: Refers to the result of the operation.
-
Requires: Refers to the result of entity processing that must be completed before processing the current one.
-
Locks: Similar to database locks; useful for parallel processing (Read or ReadWrite access shown as well).
Database
In this section, you can download all predefined database settings and configure several log settings.
Database logs and configurations
On the database tab, you can download the ZIP file containing all available information about your database, which includes the following:
-
Database monitoring logs.
-
Hikari configuration.
-
Information about the database version.
-
DDL script.
-
Information about table sizes.
-
README file that describes what type of information was downloaded.
This feature can be useful for debugging and fixing performance issues.
| The output might be limited based on the availability of the specific plugin and the database version. |
Temporary log settings
This section allows you to temporarily change the following logging settings:
-
Show SQL request parameters.
-
Set a minimum duration of a logged SQL request.
This configuration remains in effect until the next server reboot.
To change the settings permanently, you need to adjust the application.properties file accordingly (see MDM Server Application Properties, section Database performance).
Resources
View the Java properties configured for your MDM Server.
Was this page useful?