Loggers - Tag History

This article covers loggers related to Tag History that were introduced in Ignition version 8.1.X.

Loggers in this article:

• GatewayNetwork.Local.Services.TagHistoryStorage

• tags.history.InternalHistorian.HistorianSyncable

• sync.SyncableRunner

• tags.execution.actors.history

GatewayNetwork.Local.Services.TagHistoryStorage

• Monitors storage of tag history being received through a gateway network connection and then being passed to a local datasource. This logger is relevant for gateways receiving historical data from edge gateways using Tag History Sync. {RemoteGatewaySystemID}/{TagProvider} can be denoted as the remote gateway and it's local tag provider containing the historical tags. {DatasourceName} can be denoted as the datasource profile name from the local gateway receiving the historical data. Replaced 7.9's GatewayNetwork.LocalServices.TagHistoryStorage
  • DEBUG log reporting two separate batches being received from a remote gateway and being passed to a local datasource:

    Storing data set from '_0:0:{RemoteGatewaySystemID}/{TagProvider}' to '{DatasourceName}', 3 values over 3 tags.   Storing data set from '_0:0:{RemoteGatewaySystemID}/{TagProvider}' to '{DatasourceName}', 1 values over 1 tags.

• • TRACE log reporting more details on the tag objects being received by the remote gateway:  

    systemId: "{RemoteGatewaySystemID}" providerId: "{TagProvider}" tags { tagPath: "[edge]Random/RandomInteger1" mode: ANALOG timesrc: VALUE } tags { tagPath: "[edge]Random/RandomShort1" mode: ANALOG timesrc: VALUE } tags { tagPath: "[edge]Random/RandomInteger2" mode: ANALOG timesrc: VALUE } values { key: 0 value { values { tstamp: 1650920372413 quality: 192 ival: 73 } } } values { key: 1 value { values { tstamp: 1650920368734 quality: 192 ival: 64 } } } values { key: 2 value { values { tstamp: 1650920372926 quality: 192 ival: 55 } } } targetHistorian: "{DatasourceName}"   systemId: "{RemoteGatewaySystemID}" providerId: "{TagProvider}" tags { tagPath: "[edge]Random/RandomInteger2" mode: ANALOG timesrc: VALUE } values { key: 0 value { values { tstamp: 1650920373452 quality: 192 ival: 72 } } } targetHistorian: "{DatasourceName}"

Back to top

tags.history.InternalHistorian.HistorianSyncable

• Monitors the process of syncing a set of values being passed through a gateway network connection to a remote datasource. This logger is relevant for historical data being set from edge gateways using Tag History Sync. The output of this logger precedes the result of the logger sync.SyncableRunner.
  • DEBUG log stating that a set of values will be attempted for a tag history sync to a remote datasource:

    Attempting to sync 12 set(s)   ..   Attempting to sync 10 set(s)   ..   Attempting to sync 11 set(s)

• • TRACE log stating more information on the process of attempting an individual value set's sync to a remote data source:

    Syncing set 1 of 11 Syncing set 2 of 11 Syncing set 3 of 11 Syncing set 4 of 11 Syncing set 5 of 11 Syncing set 6 of 11 Syncing set 7 of 11 Syncing set 8 of 11 Syncing set 9 of 11 Syncing set 10 of 11 Syncing set 11 of 11

     

Back to top

sync.SyncableRunner

• Monitors the result of syncing tag history being passed through a gateway network connection to a remote datasource. This logger is relevant for historical data being set from edge gateways using Tag History Sync. Will provide a specific sync id for each value set being synced.
  • DEBUG log showing a count of values being synced to a remote data source where each value set has it's own specific sync id. Here we can see the sync id being incremented by the count of synced values. Will also mention the next requested sync id:

    Attempted to sync 12 value(s) starting from syncid 52495, syncable requested sync ID be adjusted to 52507   ...   Attempted to sync 10 value(s) starting from syncid 52507, syncable requested sync ID be adjusted to 52517   ...   Attempted to sync 11 value(s) starting from syncid 52517, syncable requested sync ID be adjusted to 52528

• • TRACE log monitoring the current sync id. This will appear after each attempt to sync a set of values indicated in the DEBUG log above:

    Last sync ID: 52495   ...   Last sync ID: 52507   ...   Last sync ID: 52517

Back to top

tags.execution.actors.history

• Provides monitoring for the creation and execution of historical logging defined on existing tags. Replaced 7.9’s History.Collection.
  • DEBUG log showing the creation of an “evaluation group”. This occurs when a historical tag is created in a provider for the first time with a unique database and historical tag group:

    Created new evaluation group 'Multikey[[default, MSSQL, TagGroup, Default Historical]]' provider=default

• • DEBUG log showing the creation of a new historical tag:

    Historizer configured, path=[default]Testing/Bindings/Random/RandomInteger2, compressor=no-deadband, maxAge=age-ms=[max: 0, min: 1000] provider=default

• • DEBUG log notifying the gateway of a single execution for a historical tag. At this point, the qualified value shown below is ready to be passed to the configured store and forward/database:

    Sending for storage to MSSQL, from provider: default, values=[{[default]Testing/Bindings/Random/RandomInteger1, [36, Good, Thu Oct 07 14:49:12 PDT 2021 (1633643352674)], 0}]

• • TRACE log showing the request for storing a new historical record of a single historical tag:

    Process value, raw = [36, Good, Thu Oct 07 14:49:12 PDT 2021 (1633643352674)], result = [{[default]Testing/Bindings/Random/RandomInteger1, [36, Good, Thu Oct 07 14:49:12 PDT 2021 (1633643352674)], 0}] Queuing for storage to MSSQL, from provider: default, values=[{[default]Testing/Bindings/Random/RandomInteger1, [36, Good, Thu Oct 07 14:49:12 PDT 2021 (1633643352674)], 0}]

Back to top