Summary
The Agent writes most of it’s its interactions with local devices and ClinSpark interfaces to a local ‘log’ file for troubleshooting purposes.
...
| Code Block |
|---|
C:\Users\<user>\AppData\Roaming\ClinSparkAgent.log
|
Note
Screenshots provided below shows user specific file names, directories, etc. as relative examples to locate the log file.
...
Often it’s useful to reference the log file for constant review while testing certain workflows. This can give insight into what statements are being written to the log file immediately as actions are performed. Depending on the operating environment of the Agent, and the user who is accessing the log file for this kind of review, it may be helpful to consider real-time monitoring capabilities through the use of a terminal command similar to ‘tail’.
Within a Windows operation operating environment, ‘tail’ style commands can be easily be called through a number of tools. Built directly into most Windows installations is a command prompt tool called PowerShell. Within PowerShell, the Get-Content cmdlet supports a ‘tail’ parameter that can print out the most recently written lines in a given file. Specifically, this command can monitor a log file and print out a console line each time something is written:
...
Short video demonstrating this functionality in Visual Studio Code can be found here:
...
...
‘Core Dump’ log files
A core dump or a crash dump is a memory snapshot of a running process. A core dump can be created when a fatal or unhandled error (for example, signal or system exception) occurs.
...
| Code Block |
|---|
C:\Program Files\Foundry Health\ClinSparkAgent
|
...
If present, they will have a generated filename something like this: hs_err_pid5160.log
...