GDM monitoring

Dawid Kaczmarek Updated by Dawid Kaczmarek

The purpose of the GDM monitoring workspace is mainly to have a dashboard where GDM administrators can view status and follow up on synchronization issues more efficiently. The various tiles and lists in the workspace provide statistics and filtered lists of synchronization issues which needs to be addressed. The user can navigate directly from these work lists to the specific records to solve issues, and then push them directly from the workspace after to see the result.

A log table stores the history of warnings and errors from failing synchronization attempts for records, and these are also available for review and follow-up from the workspace. The logging in the monitoring workspace is disabled by default, but can be enabled from the Logging enabled parameter in GDM parameters.

The workspace tiles indicates the total number of Synchronized records, and also how many Waiting records which are quede for next synchronization. The Failing records counts the number of synchronization issues, and all tiles can be used to navigate to the Record updates form filtered for each tile:

Synchronized records: All synchronized records where Foreign record ID is inserted
  • Waiting records: All records where either Modified flag is enabled, or where Foreign record ID is blank.
  • Failing records: Records which have been attempted to synchronize, and where a new error or warning has been logged in the monitoring log table after last successful synchronization

-

All record updates: All record updates

All record updates: All record updates

A set of lists for follow-up of issues are added to the main section of the workspace. The Failing record updates is the first list and the most important one to efficiently handle any obstacles which may occur and prevent correct synchronization of a record. This lists the records which has been part of a synchronization, but which could not be pushed as usual. From the Show events button above the list, the specific synchronization error and message can be displayed. The user can navigate directly to the global record for corrections by the Go to global button, and also use the Go to local button to navigate to the local record if the record is previously pushed to the local company. After any adjustment or correction, the record(s) can be selected in the list and synchronized directly by the Push data button.

The following tabs provides some insights and statistics for synchronization and status of the GDM, and includes the following lists:

  • Failing record updates per table/company: Statistics of failing records grouped by table and company
  • Synchronized record updates per table/company: Statistics of synchronized records grouped by table and company
  • Waiting record updates per table/company: Statistics of waiting records grouped by table and company
All record updates: Similar list as the Failing record updates, with no filtering
  • Error log: Displays the infolog for failing records per company, including reference to Global record ID

A new maintenance job is added to be able to remove old and obsolete data from the monitoring log table. The Cleanup event log is available from the Periodic group in the Global data management menu, and also from the GDM monitoring workspace. In this job it is possible to specify the Number of days to keep the log data, and by processing the job all data older than the specified number of days will be deleted.

Embedded Image

Embedded Image

How did we do?

Contact