Open topic with navigation

Event Log (Administrator)

The Event Log tab lists events that take place on the Core for a given design. The log for a design, while it is running on the Core, stays with that design on the Core until you upload a new design, or different version of the running design. You can save the logged events on your hard drive by saving the running design.

If you upload a new design to the Core, the events of the running design are lost unless you save the running design before uploading the new design.

The Event Log is purged when the file reaches 100 MB, or is stored for 31 days. One day at a time is deleted until the log is under 100 MB, and nothing is older than 31 days.

IMPORTANT:   When you make any changes in the Administrator, you must Update the Administrator for the changes to take effect. After making a change in a dialog box in the Administrator, and exiting the dialog box, a red banner displays across the top of the interface with an Update button, and a Cancel button.

Viewing the Event Log

In the Administrator, click the Event Log tab. The current log information is displayed. By default, the list displays all of the events with no filtering. You can filter the list by Severity, Category or Date. Once a filter is set, it remains set until you change it, or you close the Administrator.

NOTE:  The Event Log is always sorted by date, with the most recent date at the top.

Reload

The Reload button refreshes the display adding any new events from today.

Clear Log

The Clear Log button clears the log of all events.

Filtering

You can filter the log file by Severity, Category, and Date. You can select a one or more filters.

Security

Click the down arrow in the Severity column header to filter the events by Normal or Error. Errors are displayed in red.

Category

Click the down arrow in the Category column header to filter the events by the following categories.

Connect

The log records any connections made to the Core by an External Control system (including Telnet). Included in the log are the IP Address of the system making the connection, and the time and date of connection. In addition, the log records the same information when a connection is closed.

Connections made by Q-SYS Designer, or a UCI (UCI Viewer, TSC-8, Apple iOS) are not logged.

Control

Not available as of this release.

Hardware

The status of the Core, peripherals, amplifiers and loudspeakers are written to the event log.The status states are:

• OK
• Compromised
• Fault
• Missing
• Initializing.

The status is included in the Message field and can contain information such as, PageStation-1 has been Missing since 4:07:28PM today, IOFrame-44f4 is in Fault because Output stream dropout, and Core is OK.

Paging

When a page is made, the log records the:

• success/failure
• Command used
• Page Station making the page
• description of the page
• Priority
• PA Zones to which the page was made.

In addition, the log records any changes made to the configuration of the Paging system, including:

• PA Global Settings
• Page Stations
• PA Zones
• Commands
• Command Schedule

Schedule

The log records the event's execution time, date, and name of the scheduled event.

Security

Not available as of this release.

System

• Design Start - when a design is started on the Core; the event is logged for the newly-started design. The log records the date, time and design name.
• Event Log Open - when a design is started on the Core, the Event Log for that design is opened, and the event logged. The log records the date, time, and Q-SYS Designer version number.
• Event Log Cleared - If you click the Clear Log button, the log includes the date and time the log was cleared for the design running on the Core.

User

User entries currently come from events that take place as a result of a Lua script. The information includes time, date and a description of the event. For example, Begin playback of MyFile.mp3.

Date

Click the down arrow in the Date column header to select a starting date. All data, starting with the selected date, and up to today's date, displays. Use the left and right arrows to move back or ahead by month.

Saving the Logged Information

The Event Log is purged when the file reaches 100 MB, or is stored for 31 days. When the log reaches 100 MB, the data is purged as needed starting with the oldest data. If the data reaches 31 days old, at midnight of the 31st day, the system purges the oldest day. There are two ways to save the logged information:

Tab Delimited File

1. Select the lines of the log you wish to save. You can use Ctrl+A to select all lines in the current view, Ctrl+click to save multiple non-contiguous lines, and Shift-click to save a contiguous series of lines.
2. Copy the information. Use Ctrl+C or main menu > Edit > Copy.
3. Open a suitable program such as Microsoft Excel, or Notepad, then paste the information into the open file.
4. Save the file as desired.

Q-SYS Design File

1. Open Q-SYS Designer, and from the main menu select File > Load from Core and Connect...
2. Select the design you want to load and click OK.
3. From the main menu select File > Save, or Save As.
4. Select a location and give the file a name if necessary. Click OK. The design file, along with the logged data (and current control settings) is saved to the file and location specified.
5. To view the saved log data, you must load the design onto a Core, then access the Event Log through Q-SYS Administrator.

TIP:   If you are planning to save the logs for extended periods, include the date or date range of the log in the file name.

You can now load a different design to the Core, or the system can purge the log, without losing any logged information.

Event Logging Logic

The following logic is used to decide when log events are written:

• If the status is OK within a minute of the design starting, nothing is logged.
• If the status is not OK after a minute, The Error event is logged.
• Any time the device status gets worse, an event is logged about 10 seconds later.
• If the status then gets even worse before the first 10 seconds are up, the intermediate status won't be logged, but the final status will be logged after another 10 seconds. Here is an example log message: "pagestation-h is in Fault because Input stream dropout"
• Any time the status gets better, an event is logged after a minute. If the status gets better then turns bad again before the minute has expired, nothing will be logged. The minute wait is to prevent unnecessary information being logged.
• If a problem persists after it is initially logged, a message will be logged again after 10 minutes, 1 hour, 6 hours, 12 hours and every 12 hours thereafter as a reminder that the problem still exists. This message indicates when the problem initially occurred. This way you never need to look back in the log more than half a day to see if something is bad. Here is an example: "pagestation-g has been in Fault since 3:34:55PM today because Microphone missing"