System Log Reports

System Log Reports

System Log Reports

This article provides an overview of the various reports available in RTS under Reports > System Log.

These reports include an assortment of system-related logs that track how the software is being used and offer insight into behind-the-scenes processes.
They are particularly useful for diagnostics, accountability, and monitoring user or system activity.

Drink Log

  1. Reports > System Log > Drink Log
The Drink Limit Log Viewer provides detailed tracking of alcoholic drink counts for customers over a selected date range.
This tool is primarily used to ensure that customers are not being overserved, helping maintain compliance with alcohol service regulations.
  1. Key Features:
    1. Date Range Filtering: View drink logs for a specific period to track consumption over time.
    2. Search Filters: Narrow down results to find specific customer entries or transactions.
    3. Overserving Prevention: Helps staff monitor drink limits and maintain responsible service.
This report is an essential tool for theatres serving alcohol, ensuring accountability and safety in beverage service.



Internet Credit Card Log

  1. Reports > System Log > Internet Ticketing Credit Cards
The Internet Ticketing Credit Cards Log displays a detailed list of all credit card transactions attempted through your online ticketing system.
Each entry includes information about whether the transaction was successful or failed.
  1. Key Uses:
    1. Troubleshooting failed online transactions.
    2. Reviewing successful charges for confirmation or reconciliation.
    3. Monitoring transaction trends for online ticket sales.
Warning
Important Note: This log does not apply if you are using Secure Card Processing through your payment processor or a third-party API website integrator, as those systems handle and log transactions independently.



Ping Log

  1. Reports > System Log > Ping Log
The Ping Log provides a record of network connectivity signal tests performed on the system where the log is run. 
  1. It is a valuable tool for diagnosing network-related issues such as:
    1. Spikes in network instability
    2. Periods of heavy network traffic
    3. Interruptions or drops in connectivity
  2. Use Case:
    1. This log helps identify when and how often the system experienced network interruptions, making it useful for troubleshooting issues related to slow system performance, failed transactions, or connection drops.
By reviewing this log, users can determine if network problems are impacting theatre operations and take appropriate steps to resolve or report the issue.



Hold Seats Log

  1. Reports > System Log > Hold Seats
The Hold Seats Log displays a record of all held seat actions performed through the selling screen.
It provides detailed information about which seats were held, when they were held, and by whom.
  1. Use Case:
    1. Cashiers can hold seats for customers during a transaction. If a movie uses reserved seating, this function is accessible through the reserved seating layout.
  2. How to Hold Seats:
    1. Navigate to the selling screen.
    2. Select a show with reserved seating.
    3. Open the seating layout.
    4. Under the Menu, choose Hold Seats to select and hold specific seats.
All held seats from this process are recorded in the Hold Seats Log for tracking and review.