Event Log

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.

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.

Setup

• If saving to files, insert an SD card or use a USB memory card
• Connect to the text console (SSH Recommended)
• Enable event log methods
  • Enable Logging to Console: sr eventlog console true
  • Enable Logging to File: sr eventlog file true
• Enable event log: sr eventlog true
• Enable Trace: sr eventlog trace true
• Files are saved by default to: \RM\sr\log\eventlog (processor) or /opt/crestron/virtualcontrol/RunningPrograms/ROOMID/User/sr/log (VC-4)

• View the Event Log Status: sr eventlog status

File Format

• File is saved in a csv (comma separated values) format
• 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.
• Once the file reaches 2MB it will automatically be zipped and a new file will be created and the index will be incremented.
• Quote (") is used as a text qualifer
• Columns:
  AppID,Timestamp,Level,Trigger,Type,GlobalId,Name,Message,Value
  • AppID - The app number on the control system that logged the message
  • Timestamp - Timestamp of the log entry in YYYY-MM-DDTHH:MM:SSTZ format. Example: 2020-02-21T11:57:21-06:00
  • Level - Level of logging (Trace, Debug, Information, Warning, Error, Critical)
  • 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.
    • BACNET:X - BACnet instance that triggered the event. X is the BACnet name.
    • FUSION:XX - Crestron Fusion triggered the event.  XX is the IP-ID.
    • GID:N - Triggered by a ShowRunner object.  N is the GlobalId of the object.
    • TCP:X - TCP Listener triggered the event.  X is the IP Address of the host that triggered the event.
    • UDP:X - UCP Listener triggered the event.  X is the IP Address of the host that triggered the event.
    • WEBSESSION-USER:X [Y] - Triggered from REST API/LWAPI. X is the SessionId, Y is the username associated with the session OR if username is not available
    • WEBSESSION-HOST:X [Y] - Triggered from REST API/LWAPI. X is the SessionId, Y is the IP Address associated with the session.
  • Type - Type of object logging the message
  • GlobalId - Unique Id of the object logging the message
  • Name - Name of the object logging the message
  • Message - Type of value to expect
  • Value - Current state of the type

Notes

• Before removing the SD card stop the event log: sr eventlog off
• There is no automatic deletion of files.  Please be aware of available disk space on the SD card.
• The eventlog is written 

Examples

• Area Occupancy and Scene (Power BI)
• Log Entries with Trace