Synchronization Audit
Windows event logs and G-SIM audit entries are implemented for Global synchronization, namely for the periodic and manual pull of Global changes and the force push of the local setup.
Windows Event Log
Every performed Global synchronization and every G-SIM Server prerequisite errors are written to the Windows event log.
Global Synchronization
Every start and end of the pull of Global changes and the force push of the local setup is written to the Windows event log.
Source: GSSSyncClient
|
Event ID |
Event |
Description |
|---|---|---|
|
1102
|
GSS: Start periodic pull of global changes at {DateTime}. |
Event log for the start of the periodic pull of Global changes (see Periodic Pull of Global Changes). |
|
Start the manual pull of global changes at {DateTime}. |
Event log for the start of the manual pull of Global changes (see Manual Pull of Global Changes). |
|
|
1103
|
GSS: Finished periodic pull of global changes at {DateTime}. |
Event log for the end of the periodic pull of Global changes (see Periodic Pull of Global Changes). |
|
Finished the manual pull of global changes at {DateTime}. |
Event log for the end of the manual pull of Global changes (see Manual Pull of Global Changes). |
|
|
1100 |
GSS: Force push local setup (resync) to the Event Store was started at {DateTime} because of manually triggered. |
Event log for the start of the forced push of the local setup (see Force Push of Local Setup). |
|
1101 |
GSS: Force push local setup (resync) to the Event Store was finished at {DateTime} because of manually triggered. |
Event log for the end of the forced push of the local setup (see Force Push of Local Setup). |
|
1104 |
GSS: This server is not allowed to be part of Global environment. |
Event log if the Allow Global Server Connections license is deactivated (see Allow Global Server Connections). |
G-SIM Server Prerequisite Errors
G-SIM Server prerequisite errors are checked when the G-SIM server is started and written to the Windows event log. The event text contains details about the error.
Source: GSIMServer
|
Event ID |
Description |
|---|---|
|
1002 |
The connection to the G-SIM server database cannot be established. |
|
1003 |
The connections to the G-SIM server databases are not configured. |
|
1004 |
Another instance of the G-SIM server is already running. |
|
1005 |
Unknown error. |
G-SIM Audit
Every performed Global synchronization is written to the G-SIM audit.
In the filter dialog of the Audit tab in the Operator Console, you can search for audits that relate to the Global synchronization. To do this, select the Type of Event and Global Sync related filter.
Every start and end of the pull of Global changes and the force push of the local setup is written to the G-SIM audit.
|
Event |
Action |
Description |
|---|---|---|
|
GSS: Start periodic pull of global changes at {DateTime}. |
Started |
Audit log for the start of the periodic pull of Global changes (see Periodic Pull of Global Changes). |
|
GSS: Finished periodic pull of global changes at {DateTime}. |
Stopped |
Audit log for the end of the periodic pull of Global changes (see Periodic Pull of Global Changes). |
|
{User} Start the manual pull of global changes at {DateTime}. |
Started |
Audit log for the start of the manual pull of Global changes (see Manual Pull of Global Changes). |
|
{User} Finished the manual pull of global changes at {DateTime}. |
Stopped |
Audit log for the end of the manual pull of Global changes (see Manual Pull of Global Changes). |
|
GSS: Force push local setup (resync) to the Event Store was started at {DateTime} because of manually triggered. |
Started |
Audit log for the start of the forced push of the local setup (see Force Push of Local Setup). |
|
GSS: Force push local setup (resync) to the Event Store was finished at {DateTime} because of manually triggered. |
Stopped |
Audit log for the end of the forced push of the local setup (see Force Push of Local Setup). |
