This article covers loggers related to Perspective that were introduced in Ignition version 8.1.X.
Loggers in this article:
perspective.ClientSession
- Monitors all active Perspective sessions and their individual page instances.
- INFO log showing an initialized Perspective Session, then later closed. In this example, three separate pages are opened under a single Session, then later closed one by one:
Socket connected to session. pageId=2cf1388a session-project=Test
…
Socket connected to session. pageId=3619187b session-project=Test
...
Socket connected to session. pageId=236870e session-project=Test
…
WebSocket disconnected from session. session-project=Test
…
WebSocket disconnected from session. session-project=Test
WebSocket disconnected from session. session-project=Tes
- INFO log showing an initialized Perspective Session, then later closed. In this example, three separate pages are opened under a single Session, then later closed one by one:
-
- DEBUG log showing more details for an initialized Perspective session. In this example, three separate pages are opened under a single session, then later closed one by one. When all pages are closed, the Perspective session will eventually time out. {ProjectViewName} is denoted as the initial view being opened for a Perspective session's page:
Removing access token '(websocket,z47b49-bmDzMt7eAZGJkub8GhOI39Es9rWsF6qhvLFY)=null' from cache: EXPLICIT session-project=Test
…
View '{ProjectViewName}@C' starting... protocol=view-start, session-project=Test
…
Skipping keepalive message, channel not connected. session-project=Test
Skipping keepalive message, channel not connected. session-project=Test
Skipping keepalive message, channel not connected. session-project=Test
Session timed out. project-name=Test, session-project=Test
- DEBUG log showing more details for an initialized Perspective session. In this example, three separate pages are opened under a single session, then later closed one by one. When all pages are closed, the Perspective session will eventually time out. {ProjectViewName} is denoted as the initial view being opened for a Perspective session's page:
-
- DEBUG log monitoring active pages for a Perspective session. Pages that are still open for a session will send a Keepalive request every 30 seconds by default:
Keepalive. page=3619187b, roundtrip=32
project-name=Test, route-group=perspective, route-path=/keepalive/:project/:page/:ts, session-project=Test
Keepalive. page=1d63011f, roundtrip=37
project-name=Test, route-group=perspective, route-path=/keepalive/:project/:page/:ts, session-project=Test
…
- DEBUG log monitoring active pages for a Perspective session. Pages that are still open for a session will send a Keepalive request every 30 seconds by default:
-
- TRACE log providing additional details for an initialized page of a Perspective session. This output will appear for each new page:
Received message. payload='ClientStartMsg' protocol=client-start, session-project=Test
Client Starting. Project='Test'. protocol=client-start, session-project=Test
Received message. payload='WriteSpecialMsg' protocol=write-special, session-project=Test
Received message. payload='WriteSpecialMsg' protocol=write-special, session-project=Test
Received message. payload='PropertySyncMsg' protocol=sync, session-project=Test
Received message. payload='ViewStartMsg' protocol=view-start, session-project=Test
…
- TRACE log providing additional details for an initialized page of a Perspective session. This output will appear for each new page:
perspective.binding
A series of loggers that monitor active bindings for every running Perspective Session.
perspective.binding.AbstractPolling
- Monitors the poll execution of HTTP bindings.
- TRACE log showing a single request and response on a HTTP binding. Scheduling execution in 2999 ms provides the defined poll rate for the binding. In this case, it was set to 3 seconds:
Attempting to schedule now pollingRate=3000000000, state=SCHEDULED, lastRun=1119360156087100
Debounce period is satisfied, running now pollingRate=3000000000, state=RUNNING, lastRun=1119360156087100
Execution took 57 ms view=Main View@D, project-name=Test, component=root/Label_0, lastRun=1119360156087100,
pollingRate=3000000000, state=RUNNING, target=props.text
No values changed while executing. view=Main View@D, project-name=Test, component=root/Label_0, lastRun=1119363214025999,
pollingRate=3000000000, state=IDLE, target=props.text
Scheduling next execution view=Main View@D, project-name=Test, component=root/Label_0, lastRun=1119363214025999,
pollingRate=3000000000, state=IDLE, target=props.text
Scheduling execution in 2999 ms view=Main View@D, project-name=Test, component=root/Label_0, lastRun=1119363214025999,
pollingRate=3000000000, state=IDLE, target=props.text
Last scheduled execution: null view=Main View@D, project-name=Test, component=root/Label_0, lastRun=1119363214025999,
pollingRate=3000000000, state=SCHEDULED, target=props.text
- TRACE log showing a single request and response on a HTTP binding. Scheduling execution in 2999 ms provides the defined poll rate for the binding. In this case, it was set to 3 seconds:
perspective.binding.AbstractTagHistory
- Monitors the poll execution of Tag history bindings from a specific Perspective session. view, project-name, and the component is provided.
- TRACE log showing a single poll for new values on a Tag history binding:
Executing tag history binding: RealtimeTagHistoryQueryParams[intervalLengthMs=0, rangeLength=1, rangeUnits=HOUR,
returnSizeForInterval=<null>, aggregationMode=MinMax,aggregationModes={<null>}, aliases={RandomInteger1}, endDate=<null>, paths={[default]Testing/Bindings/Random/RandomInteger1}, queryFlags=Flags[4], returnFormat=Wide, returnSize=100, startDate=<null>]
view=Main View@D, project-name=Test, component=root/Table_0, target=props.data
- TRACE log showing a single poll for new values on a Tag history binding:
perspective.binding.DirectTag
- Monitors read and writes for tag bindings from Perspective sessions.
- DEBUG showing a detected tag write from an active Perspective Session. Tag writes due to bidirectional binding only provide view name and project used. No details of the specific Perspective Session or specific component are shown per log:
Writing [default]Testing/Bindings/CompactLogix/STATUS = 2 view=Main View@D, project-name=Test
Write of value 2 to [default]Testing/Bindings/CompactLogix/STATUS succeeded
- DEBUG showing a detected tag write from an active Perspective Session. Tag writes due to bidirectional binding only provide view name and project used. No details of the specific Perspective Session or specific component are shown per log:
-
- TRACE showing a detected value change from an active Perspective Session. No details of the specific Perspective Session, project or specific component are shown per log:
Got tag change event 'TagChangeEvent[indexes=<null>,initial=false,tagPath=[default]Testing/Bindings/CompactLogix/STATUS,
value=[2, Good, Tue Oct 19 08:03:17 PDT 2021 (1634655797899)]]'
Got tag change event 'TagChangeEvent[indexes=<null>,initial=false,tagPath=[default]Testing/Bindings/CompactLogix/STATUS,
value=[2, Good, Tue Oct 19 08:03:17 PDT 2021 (1634655797899)]]'
- TRACE showing a detected value change from an active Perspective Session. No details of the specific Perspective Session, project or specific component are shown per log:
perspective.binding.expr
- Monitors when an Expression binding has been started or stopped due to opening a Perspective Session or when a project save has been pushed to the session. This does not provide any information about it’s execution or value/quality changes.
- TRACE log showing the refresh of an Expression binding after a project has been saved. We can also expect the second log shown below to appear from a session startup:
Shutting down project-name=Test, view=Main View@C, component=root/Label, target=props.text
Starting up project-name=Test, view=Main View@C, component=root/Label, target=props.text
- TRACE log showing the refresh of an Expression binding after a project has been saved. We can also expect the second log shown below to appear from a session startup:
Comments
0 comments
Article is closed for comments.