Here™ Core logs
Here™ Core maintains two distinct logs associated with the Here™ Core environment:
-
Runtime Log |
debug.log -
RVM Log |
rvm.log
These logs can help diagnose unexpected behaviors with an app or platform running in the Here™ Core environment.
Runtime log
The file debug.log contains output log messages from both the Runtime and corresponding programs (unless configured not to) leveraging that Runtime version. The messages in these logs are a combination of Chromium, Electron, Here™ Core and your program's console messages.
Runtime log default location
Runtime logs are located in:
%localappdata%\OpenFin\cache\<runtime version>\debug.log
When a security realm is used, it is part of the path to the runtime logs:
%localappdata%\OpenFin\cache\<security realm>*\<runtime version>\debug.log
Runtime log configuration
Available options for Runtime logs:
Runtime log Lifecycle
Runtime debug logs are created on Runtime startup from a program launch. Log messages are written to the file debug.log until that Runtime instance has closed down. On Runtime close, the debug log file name is updated with a timestamp. The last 7 debug logs for that Runtime version are retained on the local file system.
Format of runtime log entries
Prior to version 26, the format of log entries in the Runtime debug log was:
[YYYY-MM-DD HH:mm:ss.ms]-[TYPE:filename.ext(line#)] log message
Starting in version 26, log entries contain the process's identifier at the beginning of the line:
[processID:MMDD/HHmmss.ms:TYPE:filename.ext(line#)] log message
The process ID enables you to determine which log entries were emitted by various subprocesses of the Here™ Core Runtime. You can check these values against information from Task Manager or Process Explorer to determine exactly which subprocesses the IDs are associated with.
For example, prior to v26, it was difficult to detect "delegated launches" in the log. That is, in cases where two Here™ Core apps or platforms specify the same Runtime version, the second one that starts generates a short-lived runtime that delegates to the first-launched runtime instance and then closes. Starting in v26, you can see this situation in the log, via multiple log entries where the message is the same but the process ID is different; the duplicate entries are created by the second runtime instance. Following them is an entry from the first runtime process with the message handling delegated launch with the following args; the next entry contains the arguments that the second runtime was launched with, which are now being handled by the first runtime.
RVM log
The file rvm.log contains output log messages from the RVM. These messages consist of Network, Here™ Core Environment and program start up. RVM logs can be useful in detecting environmental and desktop variables impacting a program during its start up sequence.
RVM log default location
RVM logs are located in:
%LocalAppData%\openfin\logs\rvm.log
RVM log configuration
Available options for RVM logs:
RVM log lifecycle
RVM logs are created when a program launches. Log messages are written to the file rvm.log until the RVM has exited. This occurs when the last Runtime instance has closed. On RVM close, the RVM log file is zipped and stored in the OpenFin\logs\archive\ folder with a timestamp. The last 10 RVM logs are retained on the local file system.
Program logs
Program logs (app.log) are created on program startup and periodically written to log by the Runtime. In the RVM’s installation directory in the app’s subfolder. More Information
Program log default location
Program logs can be found in
%LocalAppData%\openfin\apps\<app>\app.log.
Archived program logs can be found in
%LocalAppData%\openfin\apps\<app>\archive\.
Program log configuration
Available options for program logs:
Log Uploader tool
Starting in version 40, you can use the Log Uploader tool to retrieve logs from end-user systems.