This article covers loggers related to Store and Forward that were introduced in Ignition version 7.8.X.
Loggers in this article:
StoreAndForward.{StoreAndForwardProfileName}
A series of loggers for monitoring the execution of existing Store and Forward profiles. {StoreAndForwardProfileName} can be denoted as the name of an existing Store and Forward profile being monitored.
StoreAndForward.{StoreAndForwardProfileName}.MemoryStore.MemoryForwardTransaction
- Provides a response each time the Store and Forward attempts to forward records into a data source
-
DEBUG log stating the result of a successful forwarding of records into a data source:
Historical forward transaction completed successfully.
-
DEBUG log stating the result of a successful forwarding of records into a data source:
StoreAndForward.{StoreAndForwardProfileName}.MultiStageStore
- Will monitor both the retrieval data from SQL inserts utilizing Store and Forward that will be passed into the memory buffer and the forwarding of those inserts into the datastore:
-
TRACE log stating that a record is being passed into the memory store successfully:
Historical data of size 1 stored in 0 ms
Historical data of size 1 stored in 0 ms
-
TRACE log stating that a record is being passed into the memory store successfully:
-
-
DEBUG log stating steps after a data has been passed into the memory store. Records are being prepared for forwarding to the data source. The Primary count or number of data points should match with the number of TRACE logs stated above:
Taking data for forward. Primary count: 2, secondary count: 0
Providing transaction set of 2 data points [2 transactions of 25 requested] for forward.
-
DEBUG log stating steps after a data has been passed into the memory store. Records are being prepared for forwarding to the data source. The Primary count or number of data points should match with the number of TRACE logs stated above:
StoreAndForward.{StoreAndForwardProfileName}.PrimarySFEngine
- Provides a summary of a single Store and Forward transaction.
-
DEBUG log stating a summary of a successful store and forward transaction. This result summarizes the execution stated in {StoreAndForwardProfileName}.MultiStageStore:
[MultiStageStore->AggregateSink] Forward of 2 transactions/2 datapoints took 2 ms. 0 transactions/0 datapoints failed.
-
DEBUG log stating a summary of a successful store and forward transaction. This result summarizes the execution stated in {StoreAndForwardProfileName}.MultiStageStore:
StoreAndForward.{StoreAndForwardProfileName}.TagHistoryDatasourceSink
- Monitors all Tag history queries that will be sent to a specific Store and Forward profile. Will log at the rate of all existing historical Tag Groups/Scan Classes applied to historical Tags.
-
DEBUG log reporting each time the historical Tag Group/Scan Class polls for values. Will either report a count of inserts each historical poll or report 0. The Tag Group/Scan Class name and the execution time will also be provided each execution:
Inserted 1 values for scan class 'Default Historical' in 2 ms
Inserted 0 values for scan class '_exempt_' in 0 ms
-
DEBUG log reporting each time the historical Tag Group/Scan Class polls for values. Will either report a count of inserts each historical poll or report 0. The Tag Group/Scan Class name and the execution time will also be provided each execution:
-
-
TRACE log providing information about successful historical write. The second line Will not store value to optimized table engine does not appear to indicate any table errors:
Storing value to tag history: {[default]Testing/Bindings/Random/RandomInteger1, [24, Good, Thu Sep 09 09:23:07 PDT 2021], 48}
Will not store value to optimized table engine: the engine is not configured, or is not accepting data.
-
TRACE log providing information about successful historical write. The second line Will not store value to optimized table engine does not appear to indicate any table errors:
Comments
0 comments
Article is closed for comments.