...
The Monitoring window is used to display information from the log database. It consists of three parts - on the left side there is a hiding panel for filtering monitored system events displayed in a table that forms the central part of the window. In the right part of the window, after double-clicking on the table row, a panel with detailed information of about the selected monitored event will be displayed. The filter configuration, as well as the table settings, are automatically saved in the computer's registers when the window for the given user is closed. Therefore, when reopened, this window will open in the state in which it was closed by the user.
...
After opening the monitoring window, the data in the table will not be displayed automatically, but it is necessary to press any button with a magnifying glass icon to display the data. The reason for this exception is because that reading data from the log database may take longer (log database may be safe, for example), which could unnecessarily slow down the user if the record filter is not set according to his ideals.
...
If the first character in the mask is an exclamation mark (!), the mask will be evaluated as a Perl compatible regular expression. For example, the expression Hexpression H..CESA* AND (*.TEPL.* OR *.TEPL_* OR *_TEPL_*) can be written as !^H\.\.CESA.*((\.TEPL\.)|(\.TEPL_)|(_TEPL_)). In monitoring, it is not possible to filter records using a mask with AND and OR operators. However, by transcribing into a regular expression , this can be achieved under certain circumstances.
...
| Alarm | All changes of alarm states - origin, vanishing, acknowledgement, etc. |
| System | Start and stop of the system or events that do not fall under another category. |
| Process | All process state changes - start, stop and crash. |
| Communication | Communication errors. |
| Operator intervention | Operator interventions in the D2000 HI process or other events caused by user activity. |
| Event | Event entries. |
| Login / Logout | Login and logout of the operator in individual processes of the system. |
| Data export | Export of data from monitored tables. |
| Spontaneous value change | Spontaneous change of the value of the object type switch, disconnector without operator intervention (circuit breaker tripping). |
| Time recorder | Special data from communication. |
...
| Column | Column contents | ||||||
|---|---|---|---|---|---|---|---|
| Name | The name of the D2000 system object to which the event relates + a graphic symbol representing the group of monitored events. | ||||||
| Description | Description of the event. | ||||||
| Alarm status (the column is initially hidden in the monitoring window) | Object alarm status after an event (only if the event is of the alarm type) | ||||||
| Event formation time | Formation date and time of the event. If the msec option is checked, the column displays time data to the nearest millisecond. | ||||||
| Priority | Priority indicates the severity of the event. The following five priority levels are implemented in the system (in order from smallest to largest):
| ||||||
The cause of the event | The cause of the monitored event. In the case of an event of type *LOG* New value *Logon* - i.e. the user's login contains:
For example: | ||||||
| User | The name of the operator logged in at the time of the event (for processes, "Connect" or "Disconnect" is listed in this column).
| ||||||
| Old value | The value of the object before the event. | ||||||
New value | The value of the object after the event. | ||||||
| Event type | Type of monitored event:
| ||||||
| Object Id (hidden column) | HOBJ identifier of the event object | ||||||
| Note (hidden column) | The text of the note entered by the user for the event | ||||||
| Note time (hidden column) | Timestamp of the last modification of the note | ||||||
| Author's notes (hidden column) | Author of the last modification of the note | ||||||
| Columns of attribute logical groups (hidden columns) | Logical groups marked as attributes automatically become columns of this table as well. The names of logical groups that are descendants of this attribute logical group (child in the tree) are displayed in the rows of individual monitored records of those objects that belong to these logical groups. |
In the list, you can arrange the data by any column, but by default, it is the Event Formation Time column. New values are added for ascending order to the incomplete last page and for descending to the first page of the list
...