This article covers loggers related to Tag History that were introduced in Ignition version 7.9.X.
Loggers in this article:
GatewayNetwork.LocalServices.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.
- 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.
- DEBUG log reporting two separate batches being received from a remote gateway and being passed to a local datasource:
-
- 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}"
- TRACE log reporting more details on the tag objects being received by the remote gateway:
Tags.History.LocalHistorian.Engine
- Monitors both the batching of historical data points recorded on an Edge gateway and tag history sync load requests. The examples below were captured to match the log events shown under the logger GatewayNetwork.LocalServices.TagHistoryStorage.
- DEBUG log monitoring the creation of storage groups for sets of tag data, submission of batches containing those storage groups, and the completion of sync data load requests for those storage groups:
Initialized storage session with batch size '10000'Created new storage group due to back fill data [tagpath=[edge]Random/RandomShort1, time=1650920368734]
Created new storage group due to repeat tag path.
...
Submitted 4 points across 1 batches in 13 ms
...
Sync data load request for id '11522' finished in 1 ms, with 3 points for sync id 11522
Sync data load request for id '11523' finished in 1 ms, with 1 points for sync id 11523
- TRACE log providing more details on the creation of storage groups to hold tag objects with a specific batch size:
Initialized storage session with batch size '10000'
Added value: [[edge]Random/RandomShort1/3, v=64, q=192, ts=1650920368734, syncid=11522]
Added value: [[edge]Random/RandomInteger1/10, v=73, q=192, ts=1650920372413, syncid=11522]
Added value: [[edge]Random/RandomInteger2/4, v=55, q=192, ts=1650920372926, syncid=11522]
Added value: [[edge]Random/RandomInteger2/4, v=72, q=192, ts=1650920373452, syncid=11523]
...
Added batch of 4 values
Skipping maintenance, too soon.
- DEBUG log monitoring the creation of storage groups for sets of tag data, submission of batches containing those storage groups, and the completion of sync data load requests for those storage groups:
Tags.History.Collection
- Monitors all tag subscriptions with tag historian settings enabled. This simply reports a log each time the Tag Historian module poll detects a valid value change that needs to be queried. Will report at the rate of value changes and the historical tag group / scan class. Replaced 7.8’s Tags.Collection.
- TRACE log reporting value change detected within the historical tag group / scan class:
[[default]Testing/Bindings/Random/RandomInteger1] Queued value:
{[default]Testing/Bindings/Random/RandomInteger1, [95, Good, Thu Sep 09 09:09:17 PDT 2021], 48}
- TRACE log reporting value change detected within the historical tag group / scan class:
Tags.History.Query
A series of loggers monitoring the access of historical data for tags. {DatabaseConnectionName} is denoted as the name of the database connection / historical provider defined in Ignition config.
Tags.History.Query.PartitionManager
- Monitors the creation, reading, and removal of tag history partition tables. Replaced 7.8’s History.Tags.PartitionManager.{DatabaseConnectionName}_PMgr
- DEBUG log showing the creation of a new tag history partition. In this example, the historical provider settings were changed from a monthly partition to one being created every minute, then changed back to monthly. Here, a specific store and forward profile MSSQL is being utilized:
{DatabaseConnectionName} Created Tag history partition sqlt_data_1_1634051427 store-forward-name=MSSQL
{DatabaseConnectionName} Closing previous partition 'sqlt_data_1_2021_10' store-forward-name=MSSQL
- DEBUG log showing the creation of a new tag history partition. In this example, the historical provider settings were changed from a monthly partition to one being created every minute, then changed back to monthly. Here, a specific store and forward profile MSSQL is being utilized:
-
- DEBUG log showing the read access to a partition table for a vision client’s tag history binding. Expect this to log at the polling rate of historical bindings or at least each time a tag history query is executed:
{DatabaseConnectionName} (id=c7c4e944) Partition query returning result set:
[sqlt_data_1_2021_10 [Fri Oct 01 00:00:00 PDT 2021-Mon Nov 01 00:00:00 PDT 2021 @ 0]] Query:
'SELECT "pname", "start_time", "end_time", "blocksize", "flags"
FROM sqlth_partitions
WHERE "drvid"=? and "start_time"<=? and "end_time">=? and ("blocksize" is NULL or "blocksize"<=?)
ORDER BY "start_time" ASC' Params: [[1, 1634049431072, 1634049371072, 0]] request-origin=10.100.60.1, session-user=admin,
session-project=Test, session-id=DB905E3E, queryid=c7c4e944
- DEBUG log showing the read access to a partition table for a vision client’s tag history binding. Expect this to log at the polling rate of historical bindings or at least each time a tag history query is executed:
-
- DEBUG log showing the deletion of existing tag history partition tables that exceed the prune age limit. Expect this logger to respond every 10 minutes for new deletions when pruning is enabled:
{DatabaseConnectionName} Partition 'sqlt_data_1_2019_10' deleted successfully.
{DatabaseConnectionName} Partition 'sqlt_data_1_2019_11' deleted successfully.
{DatabaseConnectionName} Partition 'sqlt_data_1_2019_12' deleted successfully.
...
- DEBUG log showing the deletion of existing tag history partition tables that exceed the prune age limit. Expect this logger to respond every 10 minutes for new deletions when pruning is enabled:
-
- DEBUG log notifying the gateway that no current partitions are exceeding the prune age limit. Expect this logger to respond every 10 minutes for new deletions when pruning is enabled:
{DatabaseConnectionName} Tag History maintenance task ran and did not delete anything.
- DEBUG log notifying the gateway that no current partitions are exceeding the prune age limit. Expect this logger to respond every 10 minutes for new deletions when pruning is enabled:
Tags.History.Query.dataloader.DB
- Monitors the entire process of retrieving data for all running historical bindings and active components used for historical trending. Replaced 7.8’s History.Tags.QueryExecutor[{DatabaseConnectionName}]
- DEBUG log monitoring a tag history binding applied for a single tag on a power table. Here we can track the historical tag being queried, the client/session making this request. Expect this to log at the polling rate of historical bindings or at least each time a tag history query is executed:
default (id=e4c1c3aa) Initializing history loader. Data source: 'MSSQL' System: 'ignition-su-2c8rz12-ws' Read seed values:
'true' Read SCE: 'true' request-origin=10.100.60.1, session-user=admin, session-project=Test, session-id=DB905E3E, queryid=e4c1c3aa
...
default (id=e4c1c3aa) Tag information took 0 ms to load. Registered 4 ids for 1 tag paths.
request-origin=10.100.60.1, session-user=admin, session-project=Test, session-id=DB905E3E, queryid=e4c1c3aa
default (id=e4c1c3aa) Scan class execution records took 0 ms to load.
request-origin=10.100.60.1, session-user=admin, session-project=Test, session-id=DB905E3E, queryid=e4c1c3aa
default (id=e4c1c3aa) System downtime timeline generated:
[Wed Dec 31 16:00:00 PST 1969 -> Tue Oct 12 07:25:26 PDT 2021, Tue Oct 12 07:37:07 PDT 2021 -> Sat Aug 16 23:12:55 PST 292278994]
request-origin=10.100.60.1, session-user=admin, session-project=Test, session-id=DB905E3E, queryid=e4c1c3aa
default (id=e4c1c3aa) Tag info loaded for 'testing/bindings/random/randominteger1'. Values:
[{id=5056, scid=2, provid=null, mode=Discrete, datatype=Integer, created=1633472331024, retired=0}]
request-origin=10.100.60.1, session-user=admin, session-project=Test, session-id=DB905E3E, queryid=e4c1c3aa
...
default (id=e4c1c3aa) Running special value query against table:
sqlt_data_1_2021_10 request-origin=10.100.60.1, session-user=admin, session-project=Test, session-id=DB905E3E, queryid=e4c1c3aa
…
default (id=e4c1c3aa) Loaded 1 of 1 seed values in 0 ms. Values:
[5056@[86, Good, Tue Oct 12 07:36:07 PDT 2021 (1634049367714),0]]
request-origin=10.100.60.1, session-user=admin, session-project=Test, session-id=DB905E3E, queryid=e4c1c3aa
…
default (id=e4c1c3aa) Loaded 0 of 0 post values in 1 ms. Values:
[] request-origin=10.100.60.1, session-user=admin, session-project=Test, session-id=DB905E3E, queryid=e4c1c3aa
default (id=e4c1c3aa) Reading partition sqlt_data_1_2021_10 for 1 minutes, 0 seconds of data
[Tue Oct 12 07:36:10 PDT 2021,Tue Oct 12 07:37:10 PDT 2021], for 1 tag ids request-origin=10.100.60.1,
session-user=admin, session-project=Test, session-id=DB905E3E, queryid=e4c1c3aa
default (id=e4c1c3aa) Partition read took 0 ms. request-origin=10.100.60.1, session-user=admin, session-project=Test,
session-id=DB905E3E, queryid=e4c1c3aa
…
default (id=e4c1c3aa) Finished providing seed values. request-origin=10.100.60.1, session-user=admin,
session-project=Test, session-id=DB905E3E, queryid=e4c1c3aa
…
Finished loading data values. request-origin=10.100.60.1, session-user=admin, session-project=Test, session-id=DB905E3E, queryid=e4c1c3aa
- DEBUG log monitoring a tag history binding applied for a single tag on a power table. Here we can track the historical tag being queried, the client/session making this request. Expect this to log at the polling rate of historical bindings or at least each time a tag history query is executed:
-
- TRACE log providing additional information when monitoring a tag history binding applied for a single tag on a power table. Here we can track the associated tables being queried and the values being returned for a binding / trend. Expect this to log at the polling rate of historical bindings or at least each time a tag history query is executed:
default (id=e4c1c3aa) Loading driver ids: SELECT "id", "name", "provider"
FROM sqlth_drv WHERE "name"=?
ORDER BY "provider" ASC [ignition-su-2c8rz12-ws] request-origin=10.100.60.1, session-user=admin, session-project=Test,
session-id=DB905E3E, queryid=e4c1c3aa
...
default (id=e4c1c3aa) Loading tag information:
[SELECT a."id",a."tagpath",a."datatype",a."scid",a."querymode",a."created",a."retired"
FROM sqlth_te a,sqlth_scinfo b
WHERE (a."tagpath"=?) AND (a."scid"=0 OR a."scid"=b."id" AND (b."drvid"=? OR b."drvid"=?))
ORDER BY a."retired" DESC],[[testing/bindings/random/randominteger1],[1, 2]] request-origin=10.100.60.1,
session-user=admin, session-project=Test, session-id=DB905E3E, queryid=e4c1c3aa
...
default (id=e4c1c3aa) Running seed value query:
SELECT "tagid","intvalue","floatvalue","stringvalue","datevalue","t_stamp","dataintegrity"
FROM sqlt_data_1_2021_10
WHERE "tagid" IN (?) and "t_stamp"<?
ORDER BY "t_stamp" DESC [[5056, 1634049370039]] request-origin=10.100.60.1, session-user=admin,
session-project=Test, session-id=DB905E3E, queryid=e4c1c3aa
...
default (id=e4c1c3aa) Loaded value 5056@[86, Good, Tue Oct 12 07:36:07 PDT 2021 (1634049367714),0]
request-origin=10.100.60.1, session-user=admin, session-project=Test, session-id=DB905E3E, queryid=e4c1c3aa
…
default (id=e4c1c3aa) Loaded value 5056@[95, Good, Tue Oct 12 07:36:17 PDT 2021 (1634049377716),0]
request-origin=10.100.60.1, session-user=admin, session-project=Test, session-id=DB905E3E, queryid=e4c1c3aa
default (id=e4c1c3aa) Loaded value 5056@[85, Good, Tue Oct 12 07:36:27 PDT 2021 (1634049387717),0]
request-origin=10.100.60.1, session-user=admin, session-project=Test, session-id=DB905E3E, queryid=e4c1c3aa
default (id=e4c1c3aa) Loaded value 5056@[51, Good, Tue Oct 12 07:36:37 PDT 2021 (1634049397717),0]
request-origin=10.100.60.1, session-user=admin, session-project=Test, session-id=DB905E3E, queryid=e4c1c3aa
default (id=e4c1c3aa) Loaded value 5056@[44, Good, Tue Oct 12 07:36:47 PDT 2021 (1634049407717),0]
request-origin=10.100.60.1, session-user=admin, session-project=Test, session-id=DB905E3E, queryid=e4c1c3aa
default (id=e4c1c3aa) Loaded value 5056@[55, Good, Tue Oct 12 07:36:57 PDT 2021 (1634049417719),0]
request-origin=10.100.60.1, session-user=admin, session-project=Test, session-id=DB905E3E, queryid=e4c1c3aa
default (id=e4c1c3aa) Loaded value 5056@[24, Good, Tue Oct 12 07:37:07 PDT 2021 (1634049427721),0]
request-origin=10.100.60.1, session-user=admin, session-project=Test, session-id=DB905E3E, queryid=e4c1c3aa
- TRACE log providing additional information when monitoring a tag history binding applied for a single tag on a power table. Here we can track the associated tables being queried and the values being returned for a binding / trend. Expect this to log at the polling rate of historical bindings or at least each time a tag history query is executed:
Comments
0 comments
Article is closed for comments.