This article covers loggers related to Tag history that were introduced in Ignition version 7.8.X.
Loggers in this article:
History.Tags.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.
- 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:
History.Tags.PartitionManager.{DatabaseConnectionName}_PMgr
- Monitors the creation, reading, and removal of tag history partition tables.
- 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:
Created Tag history partition sqlt_data_1_1634051427
Closing previous partition 'sqlt_data_1_2021_10'
- 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:
-
- 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:
(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]]
- 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:
Partition 'sqlt_data_1_2019_10' deleted successfully.
Partition 'sqlt_data_1_2019_11' deleted successfully.
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:
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:
History.Tags.QueryExecutor[{DatabaseConnectionName}]
- Monitors the entire process of retrieving data for all running historical bindings and active components used for historical trending.
- 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 and 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:
(id=e4c1c3aa) Initializing history loader. Data source: 'MSSQL' System: 'ignition-su-2c8rz12-ws' Read seed values: 'true' Read SCE: 'true'
...
(id=e4c1c3aa) Tag information took 0 ms to load. Registered 4 ids for 1 tag paths.
(id=e4c1c3aa) Scan class execution records took 0 ms to load.
(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]
(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}]
...
(id=e4c1c3aa) Running special value query against table: sqlt_data_1_2021_10
…
(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]]
…
(id=e4c1c3aa) Loaded 0 of 0 post values in 1 ms. Values: []
(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
(id=e4c1c3aa) Partition read took 0 ms.
…
(id=e4c1c3aa) Finished providing seed values.
…
Finished loading data values.
- 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 and 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
(id=e4c1c3aa) Loading driver ids: SELECT "id", "name", "provider" FROM sqlth_drv WHERE "name"=?
ORDER BY "provider" ASC [ignition-su-2c8rz12-ws]
...
(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]]
...
(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]]
...
(id=e4c1c3aa) Loaded value 5056@[86, Good, Tue Oct 12 07:36:07 PDT 2021 (1634049367714),0]
…
(id=e4c1c3aa) Loaded value 5056@[95, Good, Tue Oct 12 07:36:17 PDT 2021 (1634049377716),0]
(id=e4c1c3aa) Loaded value 5056@[85, Good, Tue Oct 12 07:36:27 PDT 2021 (1634049387717),0]
(id=e4c1c3aa) Loaded value 5056@[51, Good, Tue Oct 12 07:36:37 PDT 2021 (1634049397717),0]
(id=e4c1c3aa) Loaded value 5056@[44, Good, Tue Oct 12 07:36:47 PDT 2021 (1634049407717),0]
(id=e4c1c3aa) Loaded value 5056@[55, Good, Tue Oct 12 07:36:57 PDT 2021 (1634049417719),0]
(id=e4c1c3aa) Loaded value 5056@[24, Good, Tue Oct 12 07:37:07 PDT 2021 (1634049427721),0]
- 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
History.{StoreAndForwardProfile}.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. {StoreAndForwardProfile} is denoted as the name of the specific store and forward profile being used for 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.