The following is a quick guide to where the Aloha POS implementation of the Punchh Loyalty system applications create log files and a general description of the source/purpose of the Punchh component that creates each log file.
ALOHA INSTALL GUIDE
OUTLINE OF EACH LOG FILE LOCATION AND IT'S PROGRAM SOURCE
LOG FILE LOCATION - Aloha BOH
c:\program files (x86)\Punchh\AlohaPunchhSVC_YYYYMMDD.log
Log file for the Aloha Punch Service (AlohaPunchhsvc.exe) Windows service. This service connects to the punchh.freshservers.net server and downloads the site's configuration, the site's assigned Aloha EXE package and also updates the Punchh Aloha programs. It performs the updates when a site needs an updated version of the Punchh application files by stopping the Aloha Punchh Service Windows service and also selected online ordering services that would prevent the update of files in use.
c:\program files (x86)\Punchh\bin\logs\YYYY-MMDD-######.log
Log file for the Punchh PROXY Service (punchh.exe) Windows service AKA Punchh Proxy service. This is the application that relays all transaction communication from the POS terminals to the Punchh loyalty API endpoint services and uploads the site log files to the Punchh AWS log file repository (poslogs.punchh.com).
c:\program files (x86)\Punchh\bin\logs\*
At EOD, all terminal Punchh log files are pushed from the POS FOH terminals and sent to the AlohaBOH PC by communicating to the Aloha Punchh Monitor (punchhmonitor.exe), renamed to reflect the POS terminal and then saved into this folder. Depending upon the site's or brand's POS integration logging level, these files are uploaded and aggregated to the Punchh POS Log files Amazon S3 buckets (poslogs.punchh.com) where they are preserved for 90 days before they are purged. If log files are not able to be uploaded to the Punchh Log file repository, they are purges to maintain only the past 7 days of current logs.
The log files are saved in the following naming format on the AlohaBOH Server:
alohapunchh_YYYYMMDD_T#.log
PunchhInter_YYYYMMDD_T#.log
T# refers to the terminal ID number which is assigned when the files or relayed from the FOH
For each POS terminal there are two Punchh log files:
alohapunchh_YYYYMMDD_T#.log ← Logging by the Punchh GUI On FOH (alohapunchh.exe)
PunchhInter_YYYYMMDD_T#.log ← Logging by Punchh printer intercept in background (PunchhInter.dll & PunchhPrt.dll)
If there is Online ordering active at the site (An Aloha Interface Terminal is running on thew AlohaBOH) there will be a log file in BOH Aloha/TMP directory
%iberdir%\TMP\PunchhInter_YYYYMMDD.log
Logging by the Punchh Printing intercept portion of the application (PunchhPrt.dll & PunchhInter.dll application on the Aloha Online Ordering Interface Terminal). This log file is only created if a site is using Online Ordering and running the Aloha Interface terminal on the BOH PC:
The Punchh Terminal application purges all but the last 10 days of these log files
LOCATION - Terminals
%localdir%\TMP\AlohaPunch_YYYYMMDD.log
Logging by the Punchh GUI portion of the application (AlohaPunchh.exe) application on the terminals)
%localdir%\TMP\PunchhInter_YYYYMMDD.log
Logging by the Punchh Printing intercept portion of the application (PunchhPrt.dll & PunchhInter.dll) application on the terminals)
The Punchh Terminal application purges all but the last 10 days of these log files
Additional useful Terminal log file:
%localdir%\TMP\fohadm.log
Not specific to Punchh but has the results of the FOHADM.BAT file's execution of the registration of the PunchhInter.dll & PunchhPrt.dll on the terminal.
FOHADM.BAT Punchh specific commands:
%windir%\Microsoft.NET\framework\v2.0.50727\regasm.exe %localdir%\bin\PunchhPrt.dll
%windir%\Microsoft.NET\framework\v2.0.50727\regasm.exe %localdir%\bin\PunchhInter.dll