# Events

The users can check the event status of ProSync events that occurred on a per-diagram basis.

<figure><img src="https://content.gitbook.com/content/08GFwBtHMB3iRBV0LNAw/blobs/vxtkWsmX2b1GfmrX0Jrb/image.png" alt=""><figcaption></figcaption></figure>

## Events area

### Setting **Email Notification**&#x20;

* The users can set up email alerts for events that occur.
* Event notifications are based on notifications via email, and the protocol used is the SMTP protocol.

### Setting Event Search duration

* The users can set a time period to see events that occurred during that time period.
* Custom allows users to set the time period they want to search for, and in addition to the current time period, users can choose from 1 day, 1 week, 2 weeks, 1 month, 3 months, 6 months, and 1 year ago.

### **Filtering** area

* The users can search for events that have occurred by filtering by specific Instance and Event Status.
* The left side shows the items used for filtering, which can be removed from filtering via the x button to the right of each filter tag or reset with the Filtering Reset button. These items can be specified via the filter button on the right.

### Setting **Event Delete** interval

* The users can control the history of an event by deleting it by setting the interval in which the users want to delete it.

### Event Table

This is a table where the users can see a list of events with both the Event Search period and filtering applied.

<table><thead><tr><th width="194">Item</th><th>Description</th></tr></thead><tbody><tr><td>Stream Name</td><td>The name of the Stream that the Instance in which the event occurred belongs to.</td></tr><tr><td>Instance Name</td><td>The name of the Instance in which the event occurred.</td></tr><tr><td>Occurence Time</td><td>The time at which the event occurred.</td></tr><tr><td>Event Level</td><td>The Status of the event.</td></tr><tr><td>Message</td><td>The message about the event.</td></tr><tr><td>Affector</td><td>The entity that caused the event, such as Admin, Web, or Scheduler.</td></tr></tbody></table>

###

***

## Event Filtering

The users can utilize these filters when searching the Event table for more sophisticated searches.

<figure><img src="https://content.gitbook.com/content/08GFwBtHMB3iRBV0LNAw/blobs/Vjds8qMJoMK1xkw2eXjA/image.png" alt=""><figcaption></figcaption></figure>

### Replication Diagram area

* The users can see a list of Streams - Instances that belong to the Diagram specified in the Diagram Filter in the header of the page.
* Select the Instances the users want to select/clear by the filtering criteria. Select Stream if the users want to select/clear all instances in a Stream, or Diagram if the users want to select/clear all instances in the current Diagram.

### Event Status area

* All of the status types available on the Events page.
* The Label, which is resolved to a level such as 'All', is the parent status for common grouping of statuses, and the Intended Status is the status that is actually checked and used.

<table><thead><tr><th width="177">Status</th><th width="408">Description</th><th>Parents status<select><option value="NYU0X1T1OZlz" label="Warning" color="blue"></option><option value="fQNeVD26SWp8" label="Long Transaction" color="blue"></option><option value="xX9ZSaRg7C3l" label="Error" color="blue"></option><option value="Tl3vmDa05DmM" label="Paused" color="blue"></option><option value="M7fgfv7ev8iJ" label="Running" color="blue"></option></select></th></tr></thead><tbody><tr><td>Running</td><td>Instance is synchronizing normally.</td><td><span data-option="M7fgfv7ev8iJ">Running</span></td></tr><tr><td>Issue Log</td><td>Status that [E]/[F] logs are generated in the proxy. If this status occurs, the users can check the detailed logs through the Issue Log modal with the +more button in the Message item.</td><td><span data-option="NYU0X1T1OZlz">Warning</span></td></tr><tr><td>Delayed</td><td>The synchronization is delayed, and the delay criteria is the Diff set specified by the user in each Instance.</td><td><span data-option="NYU0X1T1OZlz">Warning</span></td></tr><tr><td>Network Unstable</td><td>The connection between the ProSync and the ProSync Manager is unstable.</td><td><span data-option="NYU0X1T1OZlz">Warning</span></td></tr><tr><td>Long Tx Start</td><td>The time when a transaction comes in and the ProSync creates a Part File. If this condition occurs, the users can check the detailed log through the Long Tx modal with the +more button in the Message item.</td><td><span data-option="fQNeVD26SWp8">Long Transaction</span></td></tr><tr><td>Appended</td><td>Additional Long Transaction information has been appended to the created Part File.</td><td><span data-option="fQNeVD26SWp8">Long Transaction</span></td></tr><tr><td>Rollbakced</td><td>A problem occurred during the reflection of a Long Transaction and it was rolled back.</td><td><span data-option="fQNeVD26SWp8">Long Transaction</span></td></tr><tr><td>Skipped</td><td>A Transaction with a value before the Last Committed TSN was received and skipped.</td><td><span data-option="fQNeVD26SWp8">Long Transaction</span></td></tr><tr><td>Replay</td><td>Long Transaction has been transferred to the replay thread and is being reflected.</td><td><span data-option="fQNeVD26SWp8">Long Transaction</span></td></tr><tr><td>End</td><td>Long Transaction has ended.</td><td><span data-option="fQNeVD26SWp8">Long Transaction</span></td></tr><tr><td>Stopped</td><td>Processes in the ProSync are stopped.</td><td><span data-option="xX9ZSaRg7C3l">Error</span></td></tr><tr><td>DB Disconnected</td><td>The connection between each SRC and TAR DB in the ProSync Manager is disconnected.</td><td><span data-option="xX9ZSaRg7C3l">Error</span></td></tr><tr><td>Agent Down</td><td>The Agent process in the ProSync is down.</td><td><span data-option="xX9ZSaRg7C3l">Error</span></td></tr><tr><td>Paused</td><td>The Ext process in the ProSync is paused.</td><td><span data-option="Tl3vmDa05DmM">Paused</span></td></tr></tbody></table>

###

***

## Event Delete&#x20;

The users can set the time period for which the users want to delete event history.

<figure><img src="https://content.gitbook.com/content/08GFwBtHMB3iRBV0LNAw/blobs/A6Idc0Wb8t8xuM4SIZMn/image.png" alt=""><figcaption></figcaption></figure>

###

***

## Email Notification Setting

ProSync Manager requires the users to set up the settings for SMTP in the UI and then send emails through that server.

The users should contact the mail server administrator for SMTP configuration details, as they may vary depending on the environment in which ProSync Manager is running. In particular, if the users want to send mail via SSL/TLS protocol, the server must be able to communicate in both directions.

<figure><img src="https://content.gitbook.com/content/08GFwBtHMB3iRBV0LNAw/blobs/PM2puhexDHb0bQbNSsov/image.png" alt=""><figcaption></figcaption></figure>

#### 1. Set SMTP

Before setting up Email Notification, the users need to set up the SMTP protocol.

#### 2. Set Email Notification

Set and delete event alarms via email.

#### 3. Email Notification table

<table><thead><tr><th width="195.37176513671875">Item</th><th>Description</th></tr></thead><tbody><tr><td>Setting Name</td><td>The name that identifies the Email Alarm.</td></tr><tr><td>Target instance</td><td>The number of Instances that are set to receive event alarms.</td></tr><tr><td>DB Disconnected<br>Agent Down<br>Process Down<br>Nework Unstable<br>Delayed<br>Issue Log</td><td>The time, in minutes, that the users set for each state to receive an email alert.</td></tr><tr><td>Notification</td><td>Enable/disable button for the created alarm.</td></tr></tbody></table>

{% hint style="info" %}
**Note**

If the users have a Mail Transfer Agent (MTA) running on port 25 on their local host (e.g., postFix), the users can send mail without authentication by entering the IP/PORT of the agent.

However, this may end up in the recipient's spam folder, so the users'll need to change this in the recipient's mail account settings.
{% endhint %}

#### 4-1. Set SMTP

<figure><img src="https://content.gitbook.com/content/08GFwBtHMB3iRBV0LNAw/blobs/Pn6JpbObpGluxSzeheNv/image.png" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="271">Item</th><th>Description</th></tr></thead><tbody><tr><td>SMTP Server Host</td><td>Enter the HOST address of the server on which the users are setting up SMTP. (Required)</td></tr><tr><td>SMTP Server Port Number</td><td>Enter the port number of the SMTP server. (Required) </td></tr><tr><td>SMTP Email Sender</td><td>Enter the email address of the sender. The name of the actual email sender is displayed as ProsyncManager. (Required)</td></tr><tr><td>Athenticatation Required</td><td><p>This is the part where the users can enter the authentication related to SMTP Email. If authentication is required, check the appropriate item and enter it.</p><p>- Password: The password of the SMTP account to be set up.</p><p>- Protocol: Select the protocol to be used for secure communication. </p><p></p><p>[Caution]</p><p>Since this is an account used for SMTP servers that require authentication, mail will not be sent if an account that does not actually exist is used.</p></td></tr><tr><td>Send a Test Email</td><td><p>Available to send a test email to check if the account you want to send SMTP from is set up properly.</p><p>- To: Enter the email address of the person to receive the test email. (Required) </p><p>- Subject: Enter the subject of the test email. (Required) </p><p>- Contents: Enter a brief description of the test email. (Required) </p><p>- Initialize/Send: Click the Initialize/Send button to initialize or send the entered test email value.</p></td></tr></tbody></table>

#### 4-2. Set Email Notification &#x20;

**A. Enter Basic Info**

<figure><img src="https://content.gitbook.com/content/08GFwBtHMB3iRBV0LNAw/blobs/iZSuXqFR7lQzqo8yIZzW/image.png" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="159">Item</th><th width="406">Description</th><th>Required Item</th></tr></thead><tbody><tr><td>Setting Name</td><td>Teh name to identify the email alarm.</td><td>Y</td></tr><tr><td>Target Instance</td><td>Select the target instance to track events through the email alarm.</td><td>Y</td></tr></tbody></table>

**B. Set Notification Conditions**

Set the status the users want to track with Email Alarm and the duration of the status.

<figure><img src="https://content.gitbook.com/content/08GFwBtHMB3iRBV0LNAw/blobs/outNq8l8VNME9QWRriVU/image.png" alt=""><figcaption></figcaption></figure>

**C. Set Notification Targets**

Set the users the users want to receive this email alert.

<figure><img src="https://content.gitbook.com/content/08GFwBtHMB3iRBV0LNAw/blobs/NU1MOsfmYanLx6Fu5Mu6/image.png" alt=""><figcaption></figcaption></figure>

###
