Historian Monitor

Overview

This Historian Module relies on other modules to store Tags' data. For instance, the Dataset External Tags execute the data insertion for SQL targets. Meanwhile, to save data in external databases, such as Canary or External Tags Historian, the third-party system will save the data.

As the Historian module only manages the process, many potential issues regarding data storage are out of the module's scope. Problems usually relate to the 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 from Module Information and the Trace Window tool to monitor the Historian module.

On this page:

Local Diagnostic Tools

Module Information: Historian properties

The diagnostic tool from the Information module updates in real-time information about the execution of the Historian module. Therefore, you can use this solution to monitor the state of connected databases.

By running the ModuleInformation.exe tool, the section Historian updates the following properties:

Module Information - Historian properties
Property	Example Value
Tables	2
Items	6
OpenStatusMessage	OK
IsDeleting	False
StoreAndForward.IsEnabled	0
UseStoreAndForwardDatabaseAlways	False
HasPairRedudantStoreAndForwardPending	False
Redundancy.LastSyncMessage
Redundancy.LastSyncTimestamp
Redundancy.LastSyncErrorMessage
Redundancy.LastSyncErrorTimestamp
StoreAndForward.IsFixingDatabase	False
StoreAndForward.FixDatabaseMessage
StoreAndForward.FixDatabasePercent	0
StoreAndForward.FixDatabaseElapsedTime	00:00:00

The names of properties are self-explanatory, but in many cases, its exact meaning requires a deeper understanding of the implementation of the module. Contact technical support sending the contents of the table for specific analysis.

When selecting one Specific HistorianTable in the Tree under Historian, the following information is available:

Module Information - Historian Table properties
Item	Value Example
Table Name	SystemMonitoring
Number of History Items	6
Number of Rows	842
InitializationMessage	OK
Target
Disable	False
TimeDeadband	00:00:01
LifeTime	31
SaveOnChange	True
SaveQuality	False
Normalized	False
Deleting	False
LastStoredTimeStamp	7/29/2022 11:48:04 PM -03:00
LastStoredErrorMessage
LastDeletedTimeStamp
LastDeletedErrorMessage
LastSamplesSaved	ID: 842, UTCTimestamp_Ticks: 637947460841150000[7/29/2022 11:48:04.115 PM], LogType: 1, NotSync: False, ServerMonitorInfo_TServer__Memory: 155.2265625, ServerMonitorInfo_TServer__CPU: 0, ServerMonitorInfo_TRichClient_Memory: 60.98046875, ServerMonitorInfo_TRichClient_CPU: 0, ServerMonitorInfo_AllModules_Memory: 69.78515625, ServerMonitorInfo_AllModules_CPU: 0
LastStepDuringSaving	Update samples: OK
ErrorCount	0
SuccessCount	603
StoreAndForward.IsActive	False
StoreAndForward.NumberOfRows	0
StoreAndForward.LastStartedTimeStamp
StoreAndForward.LastSyncTimeStamp

Historian TraceWindow

The TraceWindow diagnostic tool provides real-time logging of events connected with the Historian 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.
Debug	Use debugging tools to inspect the state of the application at runtime

Properties Reference