Changes for page Event Log
Last modified by Scott Kohlmann on 2023/04/21 14:08
From version 6.1
edited by Mark Kohlmann
on 2022/02/04 03:04
on 2022/02/04 03:04
Change comment:
There is no comment for this version
To version 15.1
edited by Scott Kohlmann
on 2023/04/21 14:08
on 2023/04/21 14:08
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Parent
-
... ... @@ -1,1 +1,1 @@ 1 -SHOWRUNNER™ UserGuide& Wiki.Troubleshooting.WebHome1 +SHOWRUNNER™ Setup Guide.Troubleshooting Guide.Advanced Tools.WebHome - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. mark\.kohlmann@chiefintegrations\.com1 +XWiki.scott\.kohlmann@chiefintegrations\.com - Content
-
... ... @@ -1,4 +1,4 @@ 1 -S HOWRUNNER™'s event log logs system activities to text files and/or the console. The event log is disabled by default but it can be enabled if desired. We do not recommend leaving logging on unless necessary.1 +ShowRunnerCLC™'s event log logs system activities to text files and/or the console. The event log is disabled by default but it can be enabled if desired. We do not recommend leaving logging on unless necessary. 2 2 3 3 The "Trace" function allows the trigger of an event to be tracked throughout the event's execution. Trace logs the originating event and tags each eventlog entry with the identifying information on the originating device/control point. Trace creates a small additional burden on the system, not recommended on larger 3-series systems. 4 4 ... ... @@ -11,7 +11,7 @@ 11 11 ** Enable Logging to File: ##sr eventlog file true## 12 12 * Enable event log: ##sr eventlog true## 13 13 * Enable Trace: ##sr eventlog trace true## 14 -* Files are saved by default to: ##\RM\sr\log\event Log##14 +* Files are saved by default to: ##\RM\sr\log\eventlog (processor) or /opt/crestron/virtualcontrol/RunningPrograms/ROOMID/User/sr/log (VC-4)## 15 15 * ((( 16 16 View the Event Log Status: ##sr eventlog status## 17 17 ))) ... ... @@ -28,7 +28,7 @@ 28 28 +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+ 29 29 ~| Log to File | False | 30 30 +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+ 31 -~| Log File Path | \RM\sr\log\event Log |31 +~| Log File Path | \RM\sr\log\eventlog | 32 32 +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+ 33 33 ~| Enable Trace | True | 34 34 +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+## ... ... @@ -39,12 +39,13 @@ 39 39 * File is saved in a csv (comma separated values) format 40 40 * Files are saved incrementally: ##EventLog_2020-02-21T11-56-21_~#~##.csv## where 2020-02-21T11-56-21 is the program start time and ~#~## is the index of the file, starting at 000. 41 41 * Once the file reaches 2MB it will automatically be zipped and a new file will be created and the index will be incremented. 42 -* Text qualifieris not used.42 +* Quote (") is used as a text qualifer 43 43 * Columns: 44 -##AppID,Timestamp,Trigger,Type,GlobalId,Name,Message,Value## 44 +##AppID,Timestamp,Level,Trigger,Type,GlobalId,Name,Message,Value## 45 45 ** AppID - The app number on the control system that logged the message 46 46 ** Timestamp - Timestamp of the log entry in YYYY-MM-DDTHH:MM:SSTZ format. Example: 2020-02-21T11:57:21-06:00 47 -** Trigger - Empty unless Enable Trace is true. The object that triggered the event. Version 3.014 or later. Multiple possible triggers. Additional triggers may be added in the future. 47 +** Level - Level of logging (Trace, Debug, Information, Warning, Error, Critical) 48 +** Trigger - Empty unless Enable Trace is true. The object that triggered the event. **Version 3.014 or later.** Multiple possible triggers. Additional triggers may be added in the future. 48 48 *** BACNET:X - BACnet instance that triggered the event. X is the BACnet name. 49 49 *** FUSION:XX - Crestron Fusion triggered the event. XX is the IP-ID. 50 50 *** GID:N - Triggered by a ShowRunner object. N is the GlobalId of the object. ... ... @@ -62,11 +62,11 @@ 62 62 63 63 * Before removing the SD card stop the event log: ##sr eventlog off## 64 64 * There is no automatic deletion of files. Please be aware of available disk space on the SD card. 65 -* DO NOTsetup thefilepath to writeto theinternalSD card.66 +* The eventlog is written 66 66 67 67 === Examples === 68 68 69 69 * [[Area Occupancy and Scene (Power BI)>>attach:ShowRunner_LogAnalysis.pbix]] 70 -* [[Log Entries with Trace>>Log Entries with Trace]] 71 +* [[Log Entries with Trace>>SHOWRUNNER™ Setup Guide.Troubleshooting Guide.Advanced Tools.Event Log.Log Entries with Trace.WebHome]] 71 71 72 72