Overview
This Historian module relies on other modules to store Tags' data. Therefore, the Historian Monitor provides exclusive information regarding the Historian system that manages the process of storing Tags' information storing process. Therefore, the Historian Monitor will not provide information regarding the databases database's operation status.
As a result, many potential issues regarding data storage are out of the module's scope. Problems are usually related to external database repository, which requires specific tools to diagnose the problem. Despite being out of the Historian module scope, you can use the Diagnostic Tool, such as Module Information and Trace Window, to acquire additional information regarding the Historian module operation.
On this page:
| Table of Contents | ||||
|---|---|---|---|---|
|
Historian module
The Historian Monitor menu provides a way to monitor real-time information related to the Historian module operation. As the Historian Monitor has a monitoring-only function, you will not be able to can't edit or interact with Historian Tags, Historian Tables, or Archive Locations.
The information available when you you access the Historian Monitor is described in the table below.
Monitor information | Description |
|---|---|
ID | Historian Table unique identifier. |
Name Space | Specifies the namespace the item belongs to. |
Name | Historian Table's name |
Rows Count | The total number of rows of |
data stored in the Historian Table. | |
Success Count | The total number of times the system successfully |
stored data | |
in the database. [NOT SURE ABOUT THIS ONE] | |
Error Count | Records the number of times the system failed to save data into the database. [NOT SURE ABOUT THIS ONE] |
Last Stored Time Stamp | |
Informs the timestamp of the last data entry stored in the database. | |
Last Stored Error Message | Logs the last error message encountered. |
| Info | ||
|---|---|---|
| ||
To Your solution must be running to have access to the Historian Monitor information, your solution must be running. Use the Runtime to start the solution. |
Local Diagnostic Tools
As the Historian Monitor is not capable of providing cannot provide additional information regarding the connected databases, you can use the Diagnostics toll for it. You will use acquire additional information from the Module Information and the Trace Window to acquire additional information. To access these the Diagnostic tolltolls, access Runtime → Runtime Diagnostics.
| Info | ||
|---|---|---|
| ||
You can only access these toll tolls while your solution is running. Use the Runtime to start the solution. |
Module Information
The diagnostic tool from the Information module updates in real-time information about the execution of the several modulemodules. To verify the Historian information, access the Module Information (info icon) and select the Historian option in the tree. By doing this, you can monitor the state of connected databases. The following table describe describes each available information when you select the Historian.
| Property | Description |
|---|---|
| Tables | The total number of Historian Tables. |
| Items | NOT SURE ABOUT THIS ONE |
| OpenStatusMessage | NOT SURE ABOUT THIS ONE |
| IsDeleting | NOT SURE ABOUT THIS ONE |
| StoreAndForward.IsEnabled | Specify if the system is using the Store and Forward feature. |
| UseStoreAndForwardDatabaseAlways | NOT SURE ABOUT THIS ONE |
| HasPairRedudantStoreAndForwardPending | Indicates if a Forward process to update the database is waiting due to connection issues. |
| Redundancy.LastSyncMessage | The last message received after synchronizing data with the database. |
| Redundancy.LastSyncTimestamp | Specify when the last synchronization happened. |
| Redundancy.LastSyncErrorMessage | Inform the last error message received when the synchronization failledfailed. |
| Redundancy.LastSyncErrorTimestamp | Specify when the last failled failed synchronization happened. |
| StoreAndForward.IsFixingDatabase | Inform if the system is currently fixing the database data after facing issues synchronizing data. |
| StoreAndForward.FixDatabaseMessageMessage describing the origin problem when synchronization failed. | NOT SURE ABOUT THIS ONE |
| StoreAndForward.FixDatabasePercent | The total percentage already fixed from the database (Archive Location). |
| StoreAndForward.FixDatabaseElapsedTime | The amount of time spent since the Store and Forward has have started. |
If you select one specific Historian Table in the tree under Historian, additional information, described in the following table, will be available:
Property | Description |
|---|---|
| Table Name | The Historian Table's name. |
| Number of History Items | NOT SURE ABOUT THIS ONE |
| Number of Rows | The total number of rows of row's data stored in the Historian Table. |
| Initialization Message | Message The message provided when stating the Historian Table. |
| Target | NOT SURE ABOUT THIS ONE |
| Disable | Inform if the Historan Historian Table was disabled by the user before or while running the solution. You can control this option by accessing accessing Runtime → Runtime Diagnostics. |
| Time Deadband | The dead band time defined configured for the Historian Table. For additional information, access Historian Tables. |
| Life Time | The duration in days for retaining records on the Archive Location. The system automatically deletes data older than the specified value. |
| Save On Change | Inform if the Historian Table is using uses the Save On Change configuration to store new data. If true, whenever Tag's value change changes, it triggers an event to store the new data. |
| Save Quality | Inform if the Historian Table is using the Save Quality feature. For more Access Historian Tables for additional information related to the Save Quality, access Historian Tables. |
| Normalized | Informe if the Historian Table is using uses the Normalize table schema for SQL databases. For more information on SQL database schemes, refer to the Archiving Process. |
| Deleting | NOT SURE ABOUT THIS ONE |
| Last Stored Time Stamp | The date and time of the last previous data stored into in the database. |
| Last Stored Error Message | Message informing the problem related to the last previous problem preventing data to be from being stored. |
| Last Deleted Time Stamp | The date and time of the last time data was removed from the database. |
| Last Deleted Error Message | Message informing the problem related to the last previous problem preventing data to be from being removed from the database. |
| Last Samples Saved | NOT SURE ABOUT THIS ONE |
| Last Step During Saving | NOT SURE ABOUT THIS ONE |
| Error Count | Total number of errors related to the Historian Table operation. |
| Success Count | Total The total number of sucessfull successful data storage actions. |
| StoreAndForward.IsActive | Inform if the Historian Table is using the Store And Forward feature. NOT SURE ABOUT THIS ONE |
| StoreAndForward.NumberOfRows | NOT SURE ABOUT THIS ONE |
| StoreAndForward.LastStartedTimeStamp | Inform the last time the Store And Forward process was started to synchonize synchronized data with the database. |
| StoreAndForward.LastSyncTimeStamp | Inform the last time the database data was synchonizedwas synchronized. |
Note that some information available when selecting the Historian Table from the Module Information are the same ones you can access when using the Historian Monitor.
Historian TraceWindowTrace Window
The TraceWindow diagnostic tool provides real-time logging of Trace Window logs events connected with the Historian Module module execution.
Four level of message can be enabled.
Module Information - Historian properties
Diagnostic Level
Types of messages included
Info
Examples of events captured by this level:
Info > PropertyWatch > User logged.
Info > Module Information > User logged.
Info > RichClient > admin > User logged.
Info > Device > modbus > TRunModule.exe for channel modbus is stopped.
Info > TModules.OPCServer > User logged.
Warning
Review the application logs for any warnings.
Error
Review the application logs for any error messages.
The Trace Window logs can have four message levels:
- Info: Report actions related to the usage of the Historian module.
- Warning: Alert you to potential issues not currently blocking the system but may require your attention.
- Error: Report problems blocking one or more features from working properly, such as a database connection issue.
- Debug: Generated when you use
Debug
- debugging tools to inspect the state of
- an application at
- Runtime.
In this section:
| Page Tree | ||||
|---|---|---|---|---|
|